WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:20.100 align:start position:0% [Music] 00:00:20.100 --> 00:00:20.110 align:start position:0% 00:00:20.110 --> 00:00:22.560 align:start position:0% quick<00:00:20.770> quickly<00:00:21.070> about<00:00:21.460> me<00:00:21.730> you<00:00:22.000> just<00:00:22.180> heard<00:00:22.420> it 00:00:22.560 --> 00:00:22.570 align:start position:0% quick quickly about me you just heard it 00:00:22.570 --> 00:00:26.220 align:start position:0% quick quickly about me you just heard it but<00:00:23.410> I<00:00:23.470> built<00:00:23.770> these<00:00:23.980> things<00:00:24.310> and<00:00:25.230> recently 00:00:26.220 --> 00:00:26.230 align:start position:0% but I built these things and recently 00:00:26.230 --> 00:00:28.710 align:start position:0% but I built these things and recently also<00:00:26.370> initiated<00:00:27.370> the<00:00:27.490> ESC<00:00:27.970> 20<00:00:28.360> tokens 00:00:28.710 --> 00:00:28.720 align:start position:0% also initiated the ESC 20 tokens 00:00:28.720 --> 00:00:33.450 align:start position:0% also initiated the ESC 20 tokens standard<00:00:29.340> work<00:00:30.340> italic<00:00:30.850> and<00:00:31.830> it<00:00:32.830> became<00:00:33.130> a<00:00:33.190> lot 00:00:33.450 --> 00:00:33.460 align:start position:0% standard work italic and it became a lot 00:00:33.460 --> 00:00:40.890 align:start position:0% standard work italic and it became a lot bigger<00:00:33.910> than<00:00:34.410> expected<00:00:39.750> yeah 00:00:40.890 --> 00:00:40.900 align:start position:0% bigger than expected yeah 00:00:40.900 --> 00:00:43.110 align:start position:0% bigger than expected yeah so<00:00:41.080> one<00:00:41.650> wee<00:00:41.800> thing<00:00:41.980> about<00:00:42.160> identity<00:00:42.640> and<00:00:42.760> this 00:00:43.110 --> 00:00:43.120 align:start position:0% so one wee thing about identity and this 00:00:43.120 --> 00:00:45.210 align:start position:0% so one wee thing about identity and this talk<00:00:43.330> is<00:00:43.360> about<00:00:43.660> identity<00:00:44.110> and<00:00:44.500> it's<00:00:44.830> also<00:00:45.010> an 00:00:45.210 --> 00:00:45.220 align:start position:0% talk is about identity and it's also an 00:00:45.220 --> 00:00:49.290 align:start position:0% talk is about identity and it's also an EOC<00:00:46.710> what<00:00:47.710> is<00:00:47.890> identity<00:00:48.340> right<00:00:48.640> so<00:00:48.970> if<00:00:49.180> you 00:00:49.290 --> 00:00:49.300 align:start position:0% EOC what is identity right so if you 00:00:49.300 --> 00:00:53.670 align:start position:0% EOC what is identity right so if you think<00:00:49.480> about<00:00:49.540> identity<00:00:50.080> today<00:00:52.170> mine<00:00:53.170> doesn't 00:00:53.670 --> 00:00:53.680 align:start position:0% think about identity today mine doesn't 00:00:53.680 --> 00:00:57.990 align:start position:0% think about identity today mine doesn't work<00:00:55.710> like<00:00:56.710> it<00:00:56.770> could<00:00:57.130> be<00:00:57.310> for<00:00:57.460> example<00:00:57.850> your 00:00:57.990 --> 00:00:58.000 align:start position:0% work like it could be for example your 00:00:58.000 --> 00:01:00.420 align:start position:0% work like it could be for example your physical<00:00:58.890> attributions<00:00:59.890> right<00:01:00.100> like<00:01:00.340> it 00:01:00.420 --> 00:01:00.430 align:start position:0% physical attributions right like it 00:01:00.430 --> 00:01:02.310 align:start position:0% physical attributions right like it could<00:01:00.579> be<00:01:00.670> how<00:01:00.850> you<00:01:00.910> look<00:01:01.180> or<00:01:01.420> your<00:01:01.570> biometric 00:01:02.310 --> 00:01:02.320 align:start position:0% could be how you look or your biometric 00:01:02.320 --> 00:01:04.229 align:start position:0% could be how you look or your biometric data<00:01:02.500> and<00:01:02.890> some<00:01:03.430> kind<00:01:03.610> of<00:01:03.640> like<00:01:03.850> physical 00:01:04.229 --> 00:01:04.239 align:start position:0% data and some kind of like physical 00:01:04.239 --> 00:01:06.920 align:start position:0% data and some kind of like physical properties<00:01:05.070> attached<00:01:06.070> to<00:01:06.369> your<00:01:06.520> physical 00:01:06.920 --> 00:01:06.930 align:start position:0% properties attached to your physical 00:01:06.930 --> 00:01:10.590 align:start position:0% properties attached to your physical person<00:01:08.250> and<00:01:09.250> your<00:01:09.580> body<00:01:09.729> for<00:01:10.030> example<00:01:10.420> right 00:01:10.590 --> 00:01:10.600 align:start position:0% person and your body for example right 00:01:10.600 --> 00:01:13.109 align:start position:0% person and your body for example right but<00:01:11.140> an<00:01:11.320> identity<00:01:11.710> could<00:01:11.920> also<00:01:12.130> be<00:01:12.399> the<00:01:12.729> group 00:01:13.109 --> 00:01:13.119 align:start position:0% but an identity could also be the group 00:01:13.119 --> 00:01:15.060 align:start position:0% but an identity could also be the group you<00:01:13.330> belong<00:01:13.660> to<00:01:13.840> like<00:01:14.320> the<00:01:14.530> country<00:01:14.920> you 00:01:15.060 --> 00:01:15.070 align:start position:0% you belong to like the country you 00:01:15.070 --> 00:01:17.430 align:start position:0% you belong to like the country you belong<00:01:15.340> to<00:01:15.550> or<00:01:15.580> even<00:01:16.240> the<00:01:16.360> history<00:01:16.540> over<00:01:17.140> time 00:01:17.430 --> 00:01:17.440 align:start position:0% belong to or even the history over time 00:01:17.440 --> 00:01:19.560 align:start position:0% belong to or even the history over time like<00:01:17.830> the<00:01:17.979> reputation<00:01:18.220> over<00:01:18.759> time<00:01:19.119> or<00:01:19.450> the 00:01:19.560 --> 00:01:19.570 align:start position:0% like the reputation over time or the 00:01:19.570 --> 00:01:21.330 align:start position:0% like the reputation over time or the things<00:01:19.840> you<00:01:20.080> experience<00:01:20.649> or<00:01:20.830> your<00:01:20.950> ancestors 00:01:21.330 --> 00:01:21.340 align:start position:0% things you experience or your ancestors 00:01:21.340 --> 00:01:23.160 align:start position:0% things you experience or your ancestors experience<00:01:21.850> and<00:01:21.970> so<00:01:22.060> on<00:01:22.149> and<00:01:22.390> this<00:01:22.840> is<00:01:22.960> all 00:01:23.160 --> 00:01:23.170 align:start position:0% experience and so on and this is all 00:01:23.170 --> 00:01:25.889 align:start position:0% experience and so on and this is all what<00:01:23.380> we<00:01:23.500> kind<00:01:23.710> of<00:01:23.830> aggregate<00:01:24.280> to<00:01:24.899> our 00:01:25.889 --> 00:01:25.899 align:start position:0% what we kind of aggregate to our 00:01:25.899 --> 00:01:30.779 align:start position:0% what we kind of aggregate to our identity<00:01:27.690> today<00:01:28.690> obviously<00:01:29.410> identity<00:01:30.009> mostly 00:01:30.779 --> 00:01:30.789 align:start position:0% identity today obviously identity mostly 00:01:30.789 --> 00:01:32.609 align:start position:0% identity today obviously identity mostly like<00:01:31.000> some<00:01:31.240> kind<00:01:31.420> of<00:01:31.479> like<00:01:31.810> forms<00:01:32.350> and 00:01:32.609 --> 00:01:32.619 align:start position:0% like some kind of like forms and 00:01:32.619 --> 00:01:34.889 align:start position:0% like some kind of like forms and certifications<00:01:33.399> we<00:01:34.209> get<00:01:34.450> from<00:01:34.720> our 00:01:34.889 --> 00:01:34.899 align:start position:0% certifications we get from our 00:01:34.899 --> 00:01:37.650 align:start position:0% certifications we get from our government<00:01:35.380> or<00:01:35.709> we<00:01:36.190> get<00:01:36.340> from<00:01:36.670> like<00:01:37.240> all<00:01:37.420> kind 00:01:37.650 --> 00:01:37.660 align:start position:0% government or we get from like all kind 00:01:37.660 --> 00:01:39.930 align:start position:0% government or we get from like all kind of<00:01:37.750> other<00:01:37.929> places<00:01:38.310> for<00:01:39.310> example<00:01:39.700> we<00:01:39.850> have 00:01:39.930 --> 00:01:39.940 align:start position:0% of other places for example we have 00:01:39.940 --> 00:01:41.850 align:start position:0% of other places for example we have Social<00:01:40.360> Security<00:01:40.780> numbers<00:01:41.140> we<00:01:41.319> have<00:01:41.410> plastic 00:01:41.850 --> 00:01:41.860 align:start position:0% Social Security numbers we have plastic 00:01:41.860 --> 00:01:45.960 align:start position:0% Social Security numbers we have plastic cards<00:01:42.720> we<00:01:43.720> have<00:01:43.810> passports<00:01:44.440> and<00:01:44.530> so<00:01:44.709> on<00:01:44.970> this 00:01:45.960 --> 00:01:45.970 align:start position:0% cards we have passports and so on this 00:01:45.970 --> 00:01:48.540 align:start position:0% cards we have passports and so on this kind<00:01:46.240> of<00:01:46.360> like<00:01:46.539> is<00:01:46.750> what<00:01:46.929> we<00:01:47.080> think<00:01:47.590> our 00:01:48.540 --> 00:01:48.550 align:start position:0% kind of like is what we think our 00:01:48.550 --> 00:01:50.190 align:start position:0% kind of like is what we think our identity<00:01:49.119> is<00:01:49.209> today<00:01:49.509> and<00:01:49.660> this<00:01:49.750> is<00:01:49.810> what<00:01:50.050> we 00:01:50.190 --> 00:01:50.200 align:start position:0% identity is today and this is what we 00:01:50.200 --> 00:01:51.859 align:start position:0% identity is today and this is what we use<00:01:50.440> in<00:01:50.619> the<00:01:50.649> world<00:01:50.950> to<00:01:51.160> represent<00:01:51.610> ourselves 00:01:51.859 --> 00:01:51.869 align:start position:0% use in the world to represent ourselves 00:01:51.869 --> 00:01:54.540 align:start position:0% use in the world to represent ourselves so<00:01:52.869> when<00:01:53.259> we<00:01:53.380> think<00:01:53.530> about<00:01:53.649> the<00:01:53.890> passport<00:01:54.399> for 00:01:54.540 --> 00:01:54.550 align:start position:0% so when we think about the passport for 00:01:54.550 --> 00:01:56.880 align:start position:0% so when we think about the passport for example<00:01:54.970> what<00:01:55.479> is<00:01:55.720> it<00:01:55.899> really<00:01:56.170> right<00:01:56.470> what<00:01:56.770> is 00:01:56.880 --> 00:01:56.890 align:start position:0% example what is it really right what is 00:01:56.890 --> 00:01:59.520 align:start position:0% example what is it really right what is a<00:01:56.920> passport<00:01:57.520> it's<00:01:58.149> basically<00:01:58.599> the<00:01:58.899> fact<00:01:59.229> that 00:01:59.520 --> 00:01:59.530 align:start position:0% a passport it's basically the fact that 00:01:59.530 --> 00:02:02.430 align:start position:0% a passport it's basically the fact that there<00:01:59.679> was<00:01:59.860> a<00:02:00.009> government<00:02:00.520> agency<00:02:01.440> bureaucrat 00:02:02.430 --> 00:02:02.440 align:start position:0% there was a government agency bureaucrat 00:02:02.440 --> 00:02:05.100 align:start position:0% there was a government agency bureaucrat sitting<00:02:03.099> somewhere<00:02:03.459> and<00:02:03.759> I<00:02:04.119> came<00:02:04.420> along<00:02:04.599> with 00:02:05.100 --> 00:02:05.110 align:start position:0% sitting somewhere and I came along with 00:02:05.110 --> 00:02:07.580 align:start position:0% sitting somewhere and I came along with a<00:02:05.140> birth<00:02:05.440> certificate<00:02:05.709> and<00:02:06.250> a<00:02:06.580> photo<00:02:06.880> and 00:02:07.580 --> 00:02:07.590 align:start position:0% a birth certificate and a photo and 00:02:07.590 --> 00:02:10.350 align:start position:0% a birth certificate and a photo and maybe<00:02:08.590> dementia<00:02:09.099> of<00:02:09.160> my<00:02:09.280> biometric<00:02:09.729> data<00:02:09.940> and 00:02:10.350 --> 00:02:10.360 align:start position:0% maybe dementia of my biometric data and 00:02:10.360 --> 00:02:12.540 align:start position:0% maybe dementia of my biometric data and they<00:02:10.750> figured<00:02:11.230> out<00:02:11.260> yet<00:02:11.530> makes<00:02:11.950> sense 00:02:12.540 --> 00:02:12.550 align:start position:0% they figured out yet makes sense 00:02:12.550 --> 00:02:15.979 align:start position:0% they figured out yet makes sense it's<00:02:13.480> all<00:02:13.720> matching<00:02:14.230> I<00:02:14.440> give<00:02:14.980> you<00:02:15.099> a<00:02:15.130> passport 00:02:15.979 --> 00:02:15.989 align:start position:0% it's all matching I give you a passport 00:02:15.989 --> 00:02:19.640 align:start position:0% it's all matching I give you a passport so<00:02:16.989> basically<00:02:17.410> it's<00:02:17.590> a<00:02:17.650> collection<00:02:18.010> of<00:02:18.220> things 00:02:19.640 --> 00:02:19.650 align:start position:0% so basically it's a collection of things 00:02:19.650 --> 00:02:22.680 align:start position:0% so basically it's a collection of things and<00:02:20.650> what<00:02:20.830> it<00:02:20.980> is<00:02:21.160> is<00:02:21.430> actually<00:02:22.090> collection<00:02:22.630> of 00:02:22.680 --> 00:02:22.690 align:start position:0% and what it is is actually collection of 00:02:22.690 --> 00:02:25.410 align:start position:0% and what it is is actually collection of claims<00:02:23.160> because<00:02:24.160> what<00:02:24.489> I'm<00:02:24.610> having<00:02:24.849> here<00:02:25.239> is<00:02:25.390> I 00:02:25.410 --> 00:02:25.420 align:start position:0% claims because what I'm having here is I 00:02:25.420 --> 00:02:28.680 align:start position:0% claims because what I'm having here is I have<00:02:25.569> a<00:02:25.989> claim<00:02:26.760> the<00:02:27.760> birth<00:02:27.970> certificate<00:02:28.480> which 00:02:28.680 --> 00:02:28.690 align:start position:0% have a claim the birth certificate which 00:02:28.690 --> 00:02:30.510 align:start position:0% have a claim the birth certificate which somebody<00:02:28.930> gave<00:02:29.200> me<00:02:29.380> when<00:02:29.740> I<00:02:29.770> was<00:02:29.830> born<00:02:30.280> right 00:02:30.510 --> 00:02:30.520 align:start position:0% somebody gave me when I was born right 00:02:30.520 --> 00:02:32.610 align:start position:0% somebody gave me when I was born right it's<00:02:30.790> already<00:02:30.940> claimed<00:02:31.420> but<00:02:31.690> that<00:02:31.870> person<00:02:32.380> who 00:02:32.610 --> 00:02:32.620 align:start position:0% it's already claimed but that person who 00:02:32.620 --> 00:02:33.600 align:start position:0% it's already claimed but that person who was<00:02:32.890> there<00:02:33.130> maybe 00:02:33.600 --> 00:02:33.610 align:start position:0% was there maybe 00:02:33.610 --> 00:02:35.340 align:start position:0% was there maybe the<00:02:33.730> doctor<00:02:34.120> or<00:02:34.240> maybe<00:02:34.360> was<00:02:34.690> the<00:02:34.840> hospital 00:02:35.340 --> 00:02:35.350 align:start position:0% the doctor or maybe was the hospital 00:02:35.350 --> 00:02:38.580 align:start position:0% the doctor or maybe was the hospital that<00:02:36.310> I<00:02:36.340> was<00:02:36.670> born<00:02:36.940> there<00:02:37.240> then<00:02:38.200> I<00:02:38.230> take<00:02:38.560> a 00:02:38.580 --> 00:02:38.590 align:start position:0% that I was born there then I take a 00:02:38.590 --> 00:02:40.350 align:start position:0% that I was born there then I take a physical<00:02:39.070> claim<00:02:39.310> which<00:02:39.580> is<00:02:39.610> basically<00:02:40.240> a 00:02:40.350 --> 00:02:40.360 align:start position:0% physical claim which is basically a 00:02:40.360 --> 00:02:42.300 align:start position:0% physical claim which is basically a photocopy<00:02:40.930> or<00:02:41.200> maybe<00:02:41.380> it's<00:02:41.620> some<00:02:41.830> biometric 00:02:42.300 --> 00:02:42.310 align:start position:0% photocopy or maybe it's some biometric 00:02:42.310 --> 00:02:45.300 align:start position:0% photocopy or maybe it's some biometric data<00:02:42.490> scanned<00:02:42.940> and<00:02:43.240> then<00:02:43.620> it<00:02:44.620> creates<00:02:44.980> a<00:02:45.100> new 00:02:45.300 --> 00:02:45.310 align:start position:0% data scanned and then it creates a new 00:02:45.310 --> 00:02:48.210 align:start position:0% data scanned and then it creates a new claim<00:02:45.580> now<00:02:46.360> done<00:02:46.930> by<00:02:47.140> this<00:02:47.200> guy<00:02:47.590> here 00:02:48.210 --> 00:02:48.220 align:start position:0% claim now done by this guy here 00:02:48.220 --> 00:02:52.680 align:start position:0% claim now done by this guy here there's<00:02:49.090> no<00:02:49.240> laser<00:02:49.450> pointer<00:02:50.020> yeah<00:02:50.350> and<00:02:51.690> this 00:02:52.680 --> 00:02:52.690 align:start position:0% there's no laser pointer yeah and this 00:02:52.690 --> 00:02:56.820 align:start position:0% there's no laser pointer yeah and this creates<00:02:53.020> now<00:02:53.170> this<00:02:53.320> new<00:02:53.470> claim<00:02:53.680> a<00:02:53.950> passport<00:02:55.830> so 00:02:56.820 --> 00:02:56.830 align:start position:0% creates now this new claim a passport so 00:02:56.830 --> 00:03:01.020 align:start position:0% creates now this new claim a passport so basically<00:02:57.790> almost<00:02:58.240> everything<00:02:59.610> it's<00:03:00.610> just<00:03:00.910> a 00:03:01.020 --> 00:03:01.030 align:start position:0% basically almost everything it's just a 00:03:01.030 --> 00:03:03.300 align:start position:0% basically almost everything it's just a lot<00:03:01.300> of<00:03:01.330> like<00:03:01.720> attestation<00:03:02.260> we<00:03:02.620> get<00:03:02.860> from<00:03:03.130> each 00:03:03.300 --> 00:03:03.310 align:start position:0% lot of like attestation we get from each 00:03:03.310 --> 00:03:04.920 align:start position:0% lot of like attestation we get from each other<00:03:03.520> and<00:03:03.760> we<00:03:03.850> give<00:03:04.060> to<00:03:04.270> each<00:03:04.390> other<00:03:04.600> right 00:03:04.920 --> 00:03:04.930 align:start position:0% other and we give to each other right 00:03:04.930 --> 00:03:06.330 align:start position:0% other and we give to each other right for<00:03:05.140> something<00:03:05.350> we<00:03:05.500> could<00:03:05.650> look<00:03:05.770> at<00:03:05.920> here<00:03:06.190> this 00:03:06.330 --> 00:03:06.340 align:start position:0% for something we could look at here this 00:03:06.340 --> 00:03:08.220 align:start position:0% for something we could look at here this use<00:03:06.550> case<00:03:06.640> I<00:03:06.820> have<00:03:07.060> passports<00:03:07.330> or<00:03:07.870> I<00:03:07.900> get 00:03:08.220 --> 00:03:08.230 align:start position:0% use case I have passports or I get 00:03:08.230 --> 00:03:12.300 align:start position:0% use case I have passports or I get driver's<00:03:08.650> licenses<00:03:09.810> here<00:03:10.810> or<00:03:11.110> for<00:03:11.920> example<00:03:11.980> I 00:03:12.300 --> 00:03:12.310 align:start position:0% driver's licenses here or for example I 00:03:12.310 --> 00:03:14.910 align:start position:0% driver's licenses here or for example I have<00:03:12.459> a<00:03:12.580> university<00:03:13.209> degree<00:03:13.390> and<00:03:13.840> this<00:03:14.500> is<00:03:14.650> in 00:03:14.910 --> 00:03:14.920 align:start position:0% have a university degree and this is in 00:03:14.920 --> 00:03:16.170 align:start position:0% have a university degree and this is in the<00:03:15.160> first<00:03:15.310> place<00:03:15.580> issued<00:03:15.970> by<00:03:16.090> a<00:03:16.120> government 00:03:16.170 --> 00:03:16.180 align:start position:0% the first place issued by a government 00:03:16.180 --> 00:03:18.840 align:start position:0% the first place issued by a government to<00:03:16.870> a<00:03:16.900> person<00:03:17.290> who<00:03:17.380> can<00:03:17.530> issue<00:03:17.680> that<00:03:18.010> degrees 00:03:18.840 --> 00:03:18.850 align:start position:0% to a person who can issue that degrees 00:03:18.850 --> 00:03:20.880 align:start position:0% to a person who can issue that degrees to<00:03:19.150> in<00:03:19.270> universities<00:03:19.930> itself<00:03:20.260> and<00:03:20.590> they<00:03:20.680> don't 00:03:20.880 --> 00:03:20.890 align:start position:0% to in universities itself and they don't 00:03:20.890 --> 00:03:23.220 align:start position:0% to in universities itself and they don't issue<00:03:21.040> a<00:03:21.520> degree<00:03:22.239> and<00:03:22.480> this<00:03:22.630> is<00:03:22.690> really<00:03:23.050> hot 00:03:23.220 --> 00:03:23.230 align:start position:0% issue a degree and this is really hot 00:03:23.230 --> 00:03:27.060 align:start position:0% issue a degree and this is really hot here<00:03:23.500> to<00:03:24.459> do<00:03:25.000> another<00:03:25.239> person<00:03:25.840> right<00:03:26.110> so<00:03:26.380> it's 00:03:27.060 --> 00:03:27.070 align:start position:0% here to do another person right so it's 00:03:27.070 --> 00:03:29.910 align:start position:0% here to do another person right so it's a<00:03:27.190> lot<00:03:27.400> of<00:03:27.550> claims<00:03:27.880> on<00:03:28.810> the<00:03:29.020> end<00:03:29.170> it's<00:03:29.620> all 00:03:29.910 --> 00:03:29.920 align:start position:0% a lot of claims on the end it's all 00:03:29.920 --> 00:03:32.580 align:start position:0% a lot of claims on the end it's all claims<00:03:30.250> it's<00:03:31.239> a<00:03:31.390> humongous<00:03:31.780> network<00:03:32.410> of 00:03:32.580 --> 00:03:32.590 align:start position:0% claims it's a humongous network of 00:03:32.590 --> 00:03:34.199 align:start position:0% claims it's a humongous network of claims<00:03:32.950> and<00:03:33.250> we<00:03:33.400> came<00:03:33.610> up<00:03:33.760> with<00:03:33.880> a<00:03:34.000> lot<00:03:34.180> of 00:03:34.199 --> 00:03:34.209 align:start position:0% claims and we came up with a lot of 00:03:34.209 --> 00:03:36.300 align:start position:0% claims and we came up with a lot of different<00:03:34.660> type<00:03:34.840> of<00:03:35.020> claims<00:03:35.320> secrete 00:03:36.300 --> 00:03:36.310 align:start position:0% different type of claims secrete 00:03:36.310 --> 00:03:38.280 align:start position:0% different type of claims secrete certificates<00:03:37.000> and<00:03:37.239> whatnot<00:03:37.570> and<00:03:37.600> we<00:03:37.870> collect 00:03:38.280 --> 00:03:38.290 align:start position:0% certificates and whatnot and we collect 00:03:38.290 --> 00:03:40.710 align:start position:0% certificates and whatnot and we collect them<00:03:38.440> over<00:03:38.739> time<00:03:38.980> and<00:03:39.370> it's<00:03:39.910> kind<00:03:40.090> of<00:03:40.209> like<00:03:40.420> how 00:03:40.710 --> 00:03:40.720 align:start position:0% them over time and it's kind of like how 00:03:40.720 --> 00:03:42.949 align:start position:0% them over time and it's kind of like how we<00:03:40.780> represent<00:03:41.049> ourselves<00:03:41.530> in<00:03:42.040> the<00:03:42.130> world 00:03:42.949 --> 00:03:42.959 align:start position:0% we represent ourselves in the world 00:03:42.959 --> 00:03:45.330 align:start position:0% we represent ourselves in the world maybe<00:03:43.959> not<00:03:44.230> necessarily<00:03:44.380> with<00:03:44.799> our<00:03:44.920> friends 00:03:45.330 --> 00:03:45.340 align:start position:0% maybe not necessarily with our friends 00:03:45.340 --> 00:03:46.890 align:start position:0% maybe not necessarily with our friends with<00:03:45.700> our<00:03:45.820> friends<00:03:46.120> we<00:03:46.180> might<00:03:46.330> use<00:03:46.540> social 00:03:46.890 --> 00:03:46.900 align:start position:0% with our friends we might use social 00:03:46.900 --> 00:03:48.360 align:start position:0% with our friends we might use social networks<00:03:47.230> which<00:03:47.500> is<00:03:47.620> also<00:03:47.799> kind<00:03:48.070> of<00:03:48.160> like<00:03:48.250> a 00:03:48.360 --> 00:03:48.370 align:start position:0% networks which is also kind of like a 00:03:48.370 --> 00:03:52.320 align:start position:0% networks which is also kind of like a collection<00:03:48.850> of<00:03:48.910> claims<00:03:50.400> but<00:03:51.400> if<00:03:51.549> we<00:03:51.730> go<00:03:51.940> to<00:03:52.000> any 00:03:52.320 --> 00:03:52.330 align:start position:0% collection of claims but if we go to any 00:03:52.330 --> 00:03:55.050 align:start position:0% collection of claims but if we go to any kind<00:03:52.630> of<00:03:52.690> like<00:03:52.980> company<00:03:53.980> corporation<00:03:54.790> we<00:03:54.910> make 00:03:55.050 --> 00:03:55.060 align:start position:0% kind of like company corporation we make 00:03:55.060 --> 00:03:56.580 align:start position:0% kind of like company corporation we make it<00:03:55.150> interview<00:03:55.570> or<00:03:55.720> whatever<00:03:55.810> we<00:03:56.200> just<00:03:56.230> take 00:03:56.580 --> 00:03:56.590 align:start position:0% it interview or whatever we just take 00:03:56.590 --> 00:03:57.960 align:start position:0% it interview or whatever we just take all<00:03:56.739> of<00:03:56.890> these<00:03:57.040> claims<00:03:57.280> you<00:03:57.549> know<00:03:57.580> we<00:03:57.790> show 00:03:57.960 --> 00:03:57.970 align:start position:0% all of these claims you know we show 00:03:57.970 --> 00:03:59.729 align:start position:0% all of these claims you know we show them<00:03:58.150> here<00:03:58.360> look<00:03:58.600> at<00:03:58.840> all<00:03:59.019> of<00:03:59.200> these<00:03:59.380> titles 00:03:59.729 --> 00:03:59.739 align:start position:0% them here look at all of these titles 00:03:59.739 --> 00:04:02.789 align:start position:0% them here look at all of these titles and<00:04:00.220> it<00:04:00.310> isn't<00:04:00.700> this<00:04:00.940> and<00:04:01.150> that<00:04:01.299> and<00:04:01.799> this 00:04:02.789 --> 00:04:02.799 align:start position:0% and it isn't this and that and this 00:04:02.799 --> 00:04:05.430 align:start position:0% and it isn't this and that and this basically<00:04:03.250> tells<00:04:03.910> the<00:04:04.120> other<00:04:04.299> person<00:04:04.690> a<00:04:04.810> yeah 00:04:05.430 --> 00:04:05.440 align:start position:0% basically tells the other person a yeah 00:04:05.440 --> 00:04:07.620 align:start position:0% basically tells the other person a yeah trust<00:04:05.980> this<00:04:06.130> university<00:04:06.820> it's<00:04:07.060> a<00:04:07.180> big<00:04:07.390> one 00:04:07.620 --> 00:04:07.630 align:start position:0% trust this university it's a big one 00:04:07.630 --> 00:04:10.820 align:start position:0% trust this university it's a big one looks<00:04:08.410> like<00:04:08.590> a<00:04:08.709> real<00:04:08.920> thing<00:04:09.040> here<00:04:09.670> what<00:04:09.880> he<00:04:09.970> has 00:04:10.820 --> 00:04:10.830 align:start position:0% looks like a real thing here what he has 00:04:10.830 --> 00:04:13.259 align:start position:0% looks like a real thing here what he has here<00:04:11.830> I<00:04:11.860> might<00:04:12.130> just<00:04:12.310> hire<00:04:12.519> him<00:04:12.730> for<00:04:12.760> example 00:04:13.259 --> 00:04:13.269 align:start position:0% here I might just hire him for example 00:04:13.269 --> 00:04:15.870 align:start position:0% here I might just hire him for example right<00:04:13.890> the<00:04:14.890> problem<00:04:15.310> with<00:04:15.430> the<00:04:15.580> current 00:04:15.870 --> 00:04:15.880 align:start position:0% right the problem with the current 00:04:15.880 --> 00:04:17.969 align:start position:0% right the problem with the current systems<00:04:16.269> is<00:04:16.450> that<00:04:16.690> we<00:04:16.810> have<00:04:17.019> these<00:04:17.680> huge 00:04:17.969 --> 00:04:17.979 align:start position:0% systems is that we have these huge 00:04:17.979 --> 00:04:22.290 align:start position:0% systems is that we have these huge institutions<00:04:18.930> which<00:04:19.930> issue<00:04:20.169> claims<00:04:20.590> and<00:04:21.300> I'm 00:04:22.290 --> 00:04:22.300 align:start position:0% institutions which issue claims and I'm 00:04:22.300 --> 00:04:24.360 align:start position:0% institutions which issue claims and I'm the<00:04:22.960> tiny<00:04:23.200> little<00:04:23.470> guy<00:04:23.680> and<00:04:23.950> I<00:04:24.010> will<00:04:24.070> receive 00:04:24.360 --> 00:04:24.370 align:start position:0% the tiny little guy and I will receive 00:04:24.370 --> 00:04:27.030 align:start position:0% the tiny little guy and I will receive these<00:04:24.580> claims<00:04:25.000> and<00:04:25.419> I<00:04:25.900> kind<00:04:26.710> of<00:04:26.770> like<00:04:26.950> the 00:04:27.030 --> 00:04:27.040 align:start position:0% these claims and I kind of like the 00:04:27.040 --> 00:04:34.680 align:start position:0% these claims and I kind of like the power<00:04:27.280> sits<00:04:27.640> in<00:04:27.820> these<00:04:27.910> institutions<00:04:32.250> and<00:04:33.690> it 00:04:34.680 --> 00:04:34.690 align:start position:0% power sits in these institutions and it 00:04:34.690 --> 00:04:36.840 align:start position:0% power sits in these institutions and it sits<00:04:34.900> in<00:04:35.020> the<00:04:35.169> humungous<00:04:35.680> data<00:04:35.919> walls<00:04:36.250> right 00:04:36.840 --> 00:04:36.850 align:start position:0% sits in the humungous data walls right 00:04:36.850 --> 00:04:40.250 align:start position:0% sits in the humungous data walls right so<00:04:37.660> identity<00:04:38.440> claims<00:04:38.800> today<00:04:39.250> is<00:04:39.310> basically 00:04:40.250 --> 00:04:40.260 align:start position:0% so identity claims today is basically 00:04:40.260 --> 00:04:43.350 align:start position:0% so identity claims today is basically not<00:04:41.260> necessarily<00:04:41.800> with<00:04:42.010> me<00:04:42.280> I<00:04:42.550> mean<00:04:43.030> it's<00:04:43.210> it 00:04:43.350 --> 00:04:43.360 align:start position:0% not necessarily with me I mean it's it 00:04:43.360 --> 00:04:46.140 align:start position:0% not necessarily with me I mean it's it with<00:04:43.479> the<00:04:43.630> papers<00:04:44.020> I<00:04:44.110> carry<00:04:44.560> around<00:04:44.940> but<00:04:45.940> it's 00:04:46.140 --> 00:04:46.150 align:start position:0% with the papers I carry around but it's 00:04:46.150 --> 00:04:46.909 align:start position:0% with the papers I carry around but it's kind<00:04:46.450> of 00:04:46.909 --> 00:04:46.919 align:start position:0% kind of 00:04:46.919 --> 00:04:52.249 align:start position:0% kind of more<00:04:47.849> like<00:04:48.000> monopolized<00:04:49.159> ecosystem<00:04:51.259> whatever 00:04:52.249 --> 00:04:52.259 align:start position:0% more like monopolized ecosystem whatever 00:04:52.259 --> 00:04:55.939 align:start position:0% more like monopolized ecosystem whatever could<00:04:52.560> be<00:04:52.879> centralized<00:04:53.879> all<00:04:54.210> the<00:04:54.449> things<00:04:54.949> we 00:04:55.939 --> 00:04:55.949 align:start position:0% could be centralized all the things we 00:04:55.949 --> 00:04:58.640 align:start position:0% could be centralized all the things we could<00:04:56.129> just<00:04:56.340> take<00:04:56.610> that<00:04:56.639> and<00:04:57.439> distribute<00:04:58.439> that 00:04:58.640 --> 00:04:58.650 align:start position:0% could just take that and distribute that 00:04:58.650 --> 00:05:02.450 align:start position:0% could just take that and distribute that power<00:04:59.270> and<00:05:00.270> an<00:05:00.419> ability<00:05:00.629> to<00:05:01.069> claim<00:05:02.069> things 00:05:02.450 --> 00:05:02.460 align:start position:0% power and an ability to claim things 00:05:02.460 --> 00:05:05.959 align:start position:0% power and an ability to claim things about<00:05:02.759> each<00:05:02.909> other<00:05:03.090> and<00:05:04.639> why<00:05:05.639> do<00:05:05.699> I<00:05:05.759> have<00:05:05.849> to 00:05:05.959 --> 00:05:05.969 align:start position:0% about each other and why do I have to 00:05:05.969 --> 00:05:16.879 align:start position:0% about each other and why do I have to point<00:05:06.150> have<00:05:06.360> to<00:05:06.419> point<00:05:06.599> this<00:05:06.810> way<00:05:15.680> so<00:05:16.680> for 00:05:16.879 --> 00:05:16.889 align:start position:0% point have to point this way so for 00:05:16.889 --> 00:05:20.899 align:start position:0% point have to point this way so for example<00:05:17.280> when<00:05:17.460> we<00:05:17.550> think<00:05:17.699> about<00:05:19.909> standards 00:05:20.899 --> 00:05:20.909 align:start position:0% example when we think about standards 00:05:20.909 --> 00:05:23.029 align:start position:0% example when we think about standards right<00:05:21.180> so<00:05:21.509> what<00:05:21.750> our<00:05:21.900> standards<00:05:22.289> good<00:05:22.469> for<00:05:22.740> and 00:05:23.029 --> 00:05:23.039 align:start position:0% right so what our standards good for and 00:05:23.039 --> 00:05:25.269 align:start position:0% right so what our standards good for and I<00:05:23.400> initiated<00:05:24.060> together<00:05:24.479> with<00:05:24.629> Vitalik 00:05:25.269 --> 00:05:25.279 align:start position:0% I initiated together with Vitalik 00:05:25.279 --> 00:05:27.709 align:start position:0% I initiated together with Vitalik basically<00:05:26.279> I<00:05:26.340> proposed<00:05:26.789> it<00:05:27.029> centered<00:05:27.479> and<00:05:27.629> it 00:05:27.709 --> 00:05:27.719 align:start position:0% basically I proposed it centered and it 00:05:27.719 --> 00:05:28.939 align:start position:0% basically I proposed it centered and it was<00:05:27.840> a<00:05:27.870> huge<00:05:28.080> debate<00:05:28.259> and<00:05:28.620> on<00:05:28.710> the<00:05:28.830> end 00:05:28.939 --> 00:05:28.949 align:start position:0% was a huge debate and on the end 00:05:28.949 --> 00:05:30.260 align:start position:0% was a huge debate and on the end everybody<00:05:29.310> started<00:05:29.729> like<00:05:29.879> using<00:05:30.090> this 00:05:30.260 --> 00:05:30.270 align:start position:0% everybody started like using this 00:05:30.270 --> 00:05:32.929 align:start position:0% everybody started like using this standard<00:05:30.650> it<00:05:31.650> really<00:05:31.979> helped<00:05:32.250> foster<00:05:32.550> few 00:05:32.929 --> 00:05:32.939 align:start position:0% standard it really helped foster few 00:05:32.939 --> 00:05:34.879 align:start position:0% standard it really helped foster few things<00:05:33.240> for<00:05:33.569> example<00:05:33.659> if<00:05:34.020> we<00:05:34.110> look<00:05:34.289> at<00:05:34.710> the 00:05:34.879 --> 00:05:34.889 align:start position:0% things for example if we look at the 00:05:34.889 --> 00:05:36.800 align:start position:0% things for example if we look at the token<00:05:35.279> example<00:05:35.789> right<00:05:35.909> the<00:05:36.029> token<00:05:36.360> standard 00:05:36.800 --> 00:05:36.810 align:start position:0% token example right the token standard 00:05:36.810 --> 00:05:40.519 align:start position:0% token example right the token standard and<00:05:37.020> how<00:05:37.229> it<00:05:37.349> kind<00:05:37.860> of<00:05:37.979> came<00:05:38.819> to<00:05:39.060> be<00:05:39.210> is<00:05:39.509> we<00:05:40.319> had 00:05:40.519 --> 00:05:40.529 align:start position:0% and how it kind of came to be is we had 00:05:40.529 --> 00:05:42.980 align:start position:0% and how it kind of came to be is we had already<00:05:40.680> things<00:05:41.189> like<00:05:41.520> Bitcoin<00:05:41.759> and<00:05:42.300> then 00:05:42.980 --> 00:05:42.990 align:start position:0% already things like Bitcoin and then 00:05:42.990 --> 00:05:44.719 align:start position:0% already things like Bitcoin and then people<00:05:43.349> came<00:05:43.469> with<00:05:43.500> this<00:05:43.770> idea<00:05:43.889> hey<00:05:44.250> mate 00:05:44.719 --> 00:05:44.729 align:start position:0% people came with this idea hey mate 00:05:44.729 --> 00:05:47.420 align:start position:0% people came with this idea hey mate let's<00:05:45.000> make<00:05:45.150> colored<00:05:45.479> coins<00:05:45.750> and<00:05:46.250> then<00:05:47.250> there 00:05:47.420 --> 00:05:47.430 align:start position:0% let's make colored coins and then there 00:05:47.430 --> 00:05:49.670 align:start position:0% let's make colored coins and then there was<00:05:47.550> this<00:05:47.699> project<00:05:48.270> master<00:05:48.810> coin<00:05:49.020> out<00:05:49.379> of<00:05:49.560> it 00:05:49.670 --> 00:05:49.680 align:start position:0% was this project master coin out of it 00:05:49.680 --> 00:05:52.100 align:start position:0% was this project master coin out of it later<00:05:49.919> split<00:05:50.520> it<00:05:50.639> off<00:05:50.870> counterparty<00:05:51.870> and 00:05:52.100 --> 00:05:52.110 align:start position:0% later split it off counterparty and 00:05:52.110 --> 00:05:53.659 align:start position:0% later split it off counterparty and what's<00:05:52.680> the<00:05:52.770> idea<00:05:53.099> is<00:05:53.190> that<00:05:53.219> we<00:05:53.520> came 00:05:53.659 --> 00:05:53.669 align:start position:0% what's the idea is that we came 00:05:53.669 --> 00:05:55.640 align:start position:0% what's the idea is that we came basically<00:05:53.909> create<00:05:54.419> coins<00:05:54.750> on<00:05:54.960> top<00:05:55.110> of<00:05:55.229> Bitcoin 00:05:55.640 --> 00:05:55.650 align:start position:0% basically create coins on top of Bitcoin 00:05:55.650 --> 00:05:57.920 align:start position:0% basically create coins on top of Bitcoin we<00:05:56.219> have<00:05:56.370> the<00:05:56.520> same<00:05:56.699> security<00:05:57.240> like<00:05:57.389> like<00:05:57.810> the 00:05:57.920 --> 00:05:57.930 align:start position:0% we have the same security like like the 00:05:57.930 --> 00:06:00.170 align:start position:0% we have the same security like like the Bitcoin<00:05:58.289> network<00:05:58.400> but<00:05:59.400> we<00:05:59.669> can<00:05:59.849> create<00:06:00.029> new 00:06:00.170 --> 00:06:00.180 align:start position:0% Bitcoin network but we can create new 00:06:00.180 --> 00:06:01.999 align:start position:0% Bitcoin network but we can create new coins<00:06:00.629> and<00:06:01.020> then<00:06:01.139> company<00:06:01.469> suddenly<00:06:01.680> can 00:06:01.999 --> 00:06:02.009 align:start position:0% coins and then company suddenly can 00:06:02.009 --> 00:06:03.680 align:start position:0% coins and then company suddenly can issue<00:06:02.190> their<00:06:02.460> own<00:06:02.490> coins<00:06:02.879> and<00:06:03.210> that<00:06:03.240> was<00:06:03.509> all 00:06:03.680 --> 00:06:03.690 align:start position:0% issue their own coins and that was all 00:06:03.690 --> 00:06:06.079 align:start position:0% issue their own coins and that was all really<00:06:03.870> nice<00:06:04.199> and<00:06:04.440> neat<00:06:04.560> and<00:06:05.250> it<00:06:05.520> was<00:06:05.639> kind<00:06:05.969> of 00:06:06.079 --> 00:06:06.089 align:start position:0% really nice and neat and it was kind of 00:06:06.089 --> 00:06:08.570 align:start position:0% really nice and neat and it was kind of used<00:06:06.300> but<00:06:06.569> not<00:06:07.020> really<00:06:07.319> big<00:06:07.560> then<00:06:08.279> the<00:06:08.370> theme 00:06:08.570 --> 00:06:08.580 align:start position:0% used but not really big then the theme 00:06:08.580 --> 00:06:11.209 align:start position:0% used but not really big then the theme came<00:06:08.849> along<00:06:09.180> and<00:06:09.500> also<00:06:10.500> people<00:06:10.919> started 00:06:11.209 --> 00:06:11.219 align:start position:0% came along and also people started 00:06:11.219 --> 00:06:13.309 align:start position:0% came along and also people started issuing<00:06:11.370> tokens<00:06:12.120> inventing<00:06:12.719> their<00:06:12.870> own<00:06:12.900> ideas 00:06:13.309 --> 00:06:13.319 align:start position:0% issuing tokens inventing their own ideas 00:06:13.319 --> 00:06:15.439 align:start position:0% issuing tokens inventing their own ideas of<00:06:13.349> how<00:06:13.560> a<00:06:13.589> token<00:06:13.919> can<00:06:14.039> look<00:06:14.219> like<00:06:14.400> and<00:06:15.029> we<00:06:15.330> had 00:06:15.439 --> 00:06:15.449 align:start position:0% of how a token can look like and we had 00:06:15.449 --> 00:06:17.269 align:start position:0% of how a token can look like and we had things<00:06:15.599> like<00:06:15.719> big<00:06:16.080> eggs<00:06:16.289> the<00:06:16.589> gold<00:06:16.800> token 00:06:17.269 --> 00:06:17.279 align:start position:0% things like big eggs the gold token 00:06:17.279 --> 00:06:19.610 align:start position:0% things like big eggs the gold token which<00:06:18.150> was<00:06:18.330> kind<00:06:18.509> of<00:06:18.539> like<00:06:18.719> the<00:06:19.199> first<00:06:19.409> at 00:06:19.610 --> 00:06:19.620 align:start position:0% which was kind of like the first at 00:06:19.620 --> 00:06:22.730 align:start position:0% which was kind of like the first at least<00:06:19.770> I<00:06:19.979> know<00:06:20.039> of<00:06:20.490> rather<00:06:21.060> bigger<00:06:21.740> custom 00:06:22.730 --> 00:06:22.740 align:start position:0% least I know of rather bigger custom 00:06:22.740 --> 00:06:25.700 align:start position:0% least I know of rather bigger custom token<00:06:23.270> but<00:06:24.270> what<00:06:24.449> really<00:06:24.719> actually<00:06:25.319> made<00:06:25.529> this 00:06:25.700 --> 00:06:25.710 align:start position:0% token but what really actually made this 00:06:25.710 --> 00:06:28.309 align:start position:0% token but what really actually made this very<00:06:26.129> interesting<00:06:26.550> and<00:06:27.089> very<00:06:27.120> powerful<00:06:27.629> is 00:06:28.309 --> 00:06:28.319 align:start position:0% very interesting and very powerful is 00:06:28.319 --> 00:06:31.070 align:start position:0% very interesting and very powerful is when<00:06:29.310> you<00:06:29.400> come<00:06:29.550> up<00:06:29.669> with<00:06:29.699> a<00:06:29.879> standard<00:06:30.120> like<00:06:30.900> if 00:06:31.070 --> 00:06:31.080 align:start position:0% when you come up with a standard like if 00:06:31.080 --> 00:06:33.529 align:start position:0% when you come up with a standard like if you<00:06:31.199> say<00:06:31.379> hey<00:06:31.589> a<00:06:31.919> simple<00:06:32.370> set<00:06:32.520> of<00:06:32.550> rules<00:06:32.669> you 00:06:33.529 --> 00:06:33.539 align:start position:0% you say hey a simple set of rules you 00:06:33.539 --> 00:06:35.269 align:start position:0% you say hey a simple set of rules you basically<00:06:33.779> say<00:06:33.960> hey<00:06:34.199> let's<00:06:34.439> make<00:06:34.680> these<00:06:34.949> three 00:06:35.269 --> 00:06:35.279 align:start position:0% basically say hey let's make these three 00:06:35.279 --> 00:06:37.999 align:start position:0% basically say hey let's make these three four<00:06:35.550> or<00:06:35.639> five<00:06:35.699> functions<00:06:36.560> let's<00:06:37.560> all<00:06:37.740> use 00:06:37.999 --> 00:06:38.009 align:start position:0% four or five functions let's all use 00:06:38.009 --> 00:06:40.490 align:start position:0% four or five functions let's all use this<00:06:38.159> function<00:06:38.639> as<00:06:38.759> the<00:06:39.289> operator<00:06:40.289> the 00:06:40.490 --> 00:06:40.500 align:start position:0% this function as the operator the 00:06:40.500 --> 00:06:43.249 align:start position:0% this function as the operator the interface<00:06:41.009> towards<00:06:41.580> the<00:06:41.699> token<00:06:42.120> and<00:06:42.330> suddenly 00:06:43.249 --> 00:06:43.259 align:start position:0% interface towards the token and suddenly 00:06:43.259 --> 00:06:45.529 align:start position:0% interface towards the token and suddenly we<00:06:43.379> can<00:06:43.560> have<00:06:43.680> wallets<00:06:44.150> exchanges<00:06:45.150> other 00:06:45.529 --> 00:06:45.539 align:start position:0% we can have wallets exchanges other 00:06:45.539 --> 00:06:47.149 align:start position:0% we can have wallets exchanges other contracts<00:06:46.110> interacting<00:06:46.620> with<00:06:46.710> those<00:06:46.889> tokens 00:06:47.149 --> 00:06:47.159 align:start position:0% contracts interacting with those tokens 00:06:47.159 --> 00:06:52.880 align:start position:0% contracts interacting with those tokens and<00:06:47.689> suddenly<00:06:48.689> you<00:06:48.779> have<00:06:48.839> a<00:06:48.930> complete<00:06:49.529> mess 00:06:52.880 --> 00:06:52.890 align:start position:0% 00:06:52.890 --> 00:06:57.060 align:start position:0% yeah<00:06:55.110> yeah<00:06:56.110> and<00:06:56.320> this<00:06:56.470> is<00:06:56.530> actually<00:06:56.920> what 00:06:57.060 --> 00:06:57.070 align:start position:0% yeah yeah and this is actually what 00:06:57.070 --> 00:07:00.510 align:start position:0% yeah yeah and this is actually what spurred<00:06:57.400> all<00:06:57.670> this<00:06:57.910> this<00:06:58.870> craziness<00:06:59.710> let's 00:07:00.510 --> 00:07:00.520 align:start position:0% spurred all this this craziness let's 00:07:00.520 --> 00:07:04.020 align:start position:0% spurred all this this craziness let's say<00:07:01.050> because<00:07:02.050> suddenly<00:07:02.290> we<00:07:03.160> have<00:07:03.370> a<00:07:03.550> rather 00:07:04.020 --> 00:07:04.030 align:start position:0% say because suddenly we have a rather 00:07:04.030 --> 00:07:05.940 align:start position:0% say because suddenly we have a rather simple<00:07:04.630> standard<00:07:05.170> which<00:07:05.500> doesn't<00:07:05.860> really 00:07:05.940 --> 00:07:05.950 align:start position:0% simple standard which doesn't really 00:07:05.950 --> 00:07:08.550 align:start position:0% simple standard which doesn't really even<00:07:06.220> determine<00:07:06.850> much<00:07:07.030> but<00:07:07.960> it<00:07:08.050> allows<00:07:08.290> so 00:07:08.550 --> 00:07:08.560 align:start position:0% even determine much but it allows so 00:07:08.560 --> 00:07:11.550 align:start position:0% even determine much but it allows so much<00:07:08.710> flexibility<00:07:09.370> still<00:07:09.850> inside<00:07:10.360> that<00:07:11.290> all 00:07:11.550 --> 00:07:11.560 align:start position:0% much flexibility still inside that all 00:07:11.560 --> 00:07:13.410 align:start position:0% much flexibility still inside that all of<00:07:11.800> this<00:07:11.920> experimentation<00:07:12.610> all<00:07:13.060> of<00:07:13.240> this 00:07:13.410 --> 00:07:13.420 align:start position:0% of this experimentation all of this 00:07:13.420 --> 00:07:16.560 align:start position:0% of this experimentation all of this crazy<00:07:14.320> new<00:07:14.590> ways<00:07:14.830> of<00:07:15.010> how<00:07:15.130> using<00:07:15.580> it<00:07:15.760> became 00:07:16.560 --> 00:07:16.570 align:start position:0% crazy new ways of how using it became 00:07:16.570 --> 00:07:19.170 align:start position:0% crazy new ways of how using it became possible<00:07:16.840> and<00:07:17.380> that's<00:07:18.010> why<00:07:18.280> it<00:07:18.340> took<00:07:18.640> off<00:07:18.910> so 00:07:19.170 --> 00:07:19.180 align:start position:0% possible and that's why it took off so 00:07:19.180 --> 00:07:21.570 align:start position:0% possible and that's why it took off so big<00:07:19.450> and<00:07:19.750> it's<00:07:20.140> still<00:07:20.350> like<00:07:20.650> obviously<00:07:21.250> in<00:07:21.460> the 00:07:21.570 --> 00:07:21.580 align:start position:0% big and it's still like obviously in the 00:07:21.580 --> 00:07:26.370 align:start position:0% big and it's still like obviously in the rocket<00:07:21.850> ship<00:07:21.880> flying<00:07:22.660> whatever<00:07:24.150> so<00:07:25.380> it's 00:07:26.370 --> 00:07:26.380 align:start position:0% rocket ship flying whatever so it's 00:07:26.380 --> 00:07:28.980 align:start position:0% rocket ship flying whatever so it's actually<00:07:26.860> all<00:07:27.040> about<00:07:27.070> standards<00:07:27.790> if<00:07:28.120> we<00:07:28.780> have 00:07:28.980 --> 00:07:28.990 align:start position:0% actually all about standards if we have 00:07:28.990 --> 00:07:30.570 align:start position:0% actually all about standards if we have standards<00:07:29.530> it<00:07:29.740> allows<00:07:30.010> us<00:07:30.040> to<00:07:30.400> basically 00:07:30.570 --> 00:07:30.580 align:start position:0% standards it allows us to basically 00:07:30.580 --> 00:07:32.550 align:start position:0% standards it allows us to basically interoperate<00:07:31.390> and<00:07:31.420> be<00:07:31.690> compatible<00:07:32.080> and 00:07:32.550 --> 00:07:32.560 align:start position:0% interoperate and be compatible and 00:07:32.560 --> 00:07:36.210 align:start position:0% interoperate and be compatible and especially<00:07:33.340> in<00:07:33.550> a<00:07:34.180> platform<00:07:35.080> like<00:07:35.220> aetherium 00:07:36.210 --> 00:07:36.220 align:start position:0% especially in a platform like aetherium 00:07:36.220 --> 00:07:39.000 align:start position:0% especially in a platform like aetherium where<00:07:36.580> you<00:07:37.450> have<00:07:37.690> an<00:07:37.900> endless<00:07:38.500> amount<00:07:38.650> of 00:07:39.000 --> 00:07:39.010 align:start position:0% where you have an endless amount of 00:07:39.010 --> 00:07:41.160 align:start position:0% where you have an endless amount of possibilities<00:07:39.940> of<00:07:40.120> what<00:07:40.240> you<00:07:40.300> can<00:07:40.420> do<00:07:40.810> and<00:07:41.080> how 00:07:41.160 --> 00:07:41.170 align:start position:0% possibilities of what you can do and how 00:07:41.170 --> 00:07:43.100 align:start position:0% possibilities of what you can do and how you<00:07:41.230> can<00:07:41.470> interact<00:07:41.740> and<00:07:42.130> what<00:07:42.250> you<00:07:42.370> can<00:07:42.520> create 00:07:43.100 --> 00:07:43.110 align:start position:0% you can interact and what you can create 00:07:43.110 --> 00:07:46.440 align:start position:0% you can interact and what you can create standards<00:07:44.110> are<00:07:44.260> really<00:07:44.410> the<00:07:44.650> key<00:07:44.950> to<00:07:45.940> make<00:07:46.180> a 00:07:46.440 --> 00:07:46.450 align:start position:0% standards are really the key to make a 00:07:46.450 --> 00:07:50.730 align:start position:0% standards are really the key to make a viable<00:07:46.840> ecosystem<00:07:47.770> flourish<00:07:48.960> so<00:07:49.960> I<00:07:50.380> thought 00:07:50.730 --> 00:07:50.740 align:start position:0% viable ecosystem flourish so I thought 00:07:50.740 --> 00:07:54.060 align:start position:0% viable ecosystem flourish so I thought about<00:07:50.890> like<00:07:51.220> a<00:07:51.250> few<00:07:51.490> years<00:07:51.730> about<00:07:52.890> two<00:07:53.890> years 00:07:54.060 --> 00:07:54.070 align:start position:0% about like a few years about two years 00:07:54.070 --> 00:07:55.620 align:start position:0% about like a few years about two years about<00:07:54.190> like<00:07:54.580> kind<00:07:54.820> of<00:07:54.910> like<00:07:55.060> how<00:07:55.210> I<00:07:55.240> then<00:07:55.540> it 00:07:55.620 --> 00:07:55.630 align:start position:0% about like kind of like how I then it 00:07:55.630 --> 00:07:57.950 align:start position:0% about like kind of like how I then it could<00:07:55.840> look<00:07:55.960> like<00:07:56.020> was<00:07:56.920> working<00:07:57.340> back<00:07:57.460> then 00:07:57.950 --> 00:07:57.960 align:start position:0% could look like was working back then 00:07:57.960 --> 00:08:00.330 align:start position:0% could look like was working back then with<00:07:58.960> a<00:07:58.990> client<00:07:59.500> and<00:07:59.710> thinking<00:08:00.100> about<00:08:00.250> this 00:08:00.330 --> 00:08:00.340 align:start position:0% with a client and thinking about this 00:08:00.340 --> 00:08:02.220 align:start position:0% with a client and thinking about this idea<00:08:00.520> and<00:08:00.940> it<00:08:01.030> kind<00:08:01.210> of<00:08:01.270> like<00:08:01.390> had<00:08:01.930> this<00:08:02.050> idea 00:08:02.220 --> 00:08:02.230 align:start position:0% idea and it kind of like had this idea 00:08:02.230 --> 00:08:04.440 align:start position:0% idea and it kind of like had this idea okay<00:08:02.680> should<00:08:03.160> be<00:08:03.310> a<00:08:03.340> smart<00:08:03.640> contract<00:08:04.150> and 00:08:04.440 --> 00:08:04.450 align:start position:0% okay should be a smart contract and 00:08:04.450 --> 00:08:07.050 align:start position:0% okay should be a smart contract and should<00:08:04.870> work<00:08:05.050> sent<00:08:05.440> you<00:08:05.620> and<00:08:05.950> lalala<00:08:06.490> and<00:08:06.730> I 00:08:07.050 --> 00:08:07.060 align:start position:0% should work sent you and lalala and I 00:08:07.060 --> 00:08:09.240 align:start position:0% should work sent you and lalala and I thought<00:08:07.210> about<00:08:07.360> it<00:08:07.660> and<00:08:07.840> really<00:08:08.770> until<00:08:09.070> now<00:08:09.220> I 00:08:09.240 --> 00:08:09.250 align:start position:0% thought about it and really until now I 00:08:09.250 --> 00:08:11.610 align:start position:0% thought about it and really until now I didn't<00:08:09.700> came<00:08:09.850> up<00:08:10.030> with<00:08:10.150> any<00:08:10.390> way<00:08:11.350> different 00:08:11.610 --> 00:08:11.620 align:start position:0% didn't came up with any way different 00:08:11.620 --> 00:08:16.190 align:start position:0% didn't came up with any way different solution<00:08:12.400> and<00:08:12.550> the<00:08:12.670> one<00:08:12.790> I<00:08:12.820> had<00:08:13.030> back<00:08:13.240> then<00:08:13.480> and 00:08:16.190 --> 00:08:16.200 align:start position:0% 00:08:16.200 --> 00:08:18.330 align:start position:0% actually<00:08:17.200> almost<00:08:17.470> expecting<00:08:17.980> to<00:08:18.070> somebody 00:08:18.330 --> 00:08:18.340 align:start position:0% actually almost expecting to somebody 00:08:18.340 --> 00:08:20.040 align:start position:0% actually almost expecting to somebody else<00:08:18.520> would<00:08:18.640> came<00:08:18.850> up<00:08:19.000> with<00:08:19.210> a<00:08:19.480> standard<00:08:19.870> and 00:08:20.040 --> 00:08:20.050 align:start position:0% else would came up with a standard and 00:08:20.050 --> 00:08:23.070 align:start position:0% else would came up with a standard and Meaghan<00:08:20.320> DRC<00:08:20.710> which<00:08:21.490> didn't<00:08:21.820> happen<00:08:22.120> so<00:08:22.570> I<00:08:22.780> did 00:08:23.070 --> 00:08:23.080 align:start position:0% Meaghan DRC which didn't happen so I did 00:08:23.080 --> 00:08:27.000 align:start position:0% Meaghan DRC which didn't happen so I did it<00:08:24.180> so<00:08:25.180> I<00:08:25.210> created<00:08:25.660> this<00:08:25.840> standard<00:08:26.680> how<00:08:26.980> I 00:08:27.000 --> 00:08:27.010 align:start position:0% it so I created this standard how I 00:08:27.010 --> 00:08:29.820 align:start position:0% it so I created this standard how I initiated<00:08:27.580> it<00:08:28.200> you<00:08:29.200> know<00:08:29.320> in<00:08:29.380> the<00:08:29.470> end<00:08:29.590> it<00:08:29.740> will 00:08:29.820 --> 00:08:29.830 align:start position:0% initiated it you know in the end it will 00:08:29.830 --> 00:08:31.430 align:start position:0% initiated it you know in the end it will only<00:08:30.070> become<00:08:30.310> a<00:08:30.460> standard<00:08:30.790> if<00:08:30.910> everybody 00:08:31.430 --> 00:08:31.440 align:start position:0% only become a standard if everybody 00:08:31.440 --> 00:08:33.480 align:start position:0% only become a standard if everybody participates<00:08:32.440> and<00:08:32.620> everybody<00:08:32.920> agrees<00:08:33.220> but 00:08:33.480 --> 00:08:33.490 align:start position:0% participates and everybody agrees but 00:08:33.490 --> 00:08:35.130 align:start position:0% participates and everybody agrees but that's<00:08:33.730> the<00:08:33.880> whole<00:08:33.970> point<00:08:34.180> of<00:08:34.330> a<00:08:34.420> standard<00:08:34.810> and 00:08:35.130 --> 00:08:35.140 align:start position:0% that's the whole point of a standard and 00:08:35.140 --> 00:08:38.780 align:start position:0% that's the whole point of a standard and it<00:08:35.980> now<00:08:36.100> has<00:08:36.340> the<00:08:36.370> number<00:08:36.730> seven<00:08:37.060> to<00:08:37.240> five<00:08:37.560> and 00:08:38.780 --> 00:08:38.790 align:start position:0% it now has the number seven to five and 00:08:38.790 --> 00:08:41.460 align:start position:0% it now has the number seven to five and I<00:08:39.790> graded<00:08:40.000> this<00:08:40.240> standard<00:08:40.990> which<00:08:41.140> basically 00:08:41.460 --> 00:08:41.470 align:start position:0% I graded this standard which basically 00:08:41.470 --> 00:08:43.500 align:start position:0% I graded this standard which basically defines<00:08:41.830> a<00:08:42.370> smart<00:08:42.730> contract<00:08:42.940> which 00:08:43.500 --> 00:08:43.510 align:start position:0% defines a smart contract which 00:08:43.510 --> 00:08:46.470 align:start position:0% defines a smart contract which represents<00:08:44.230> you<00:08:44.920> right<00:08:45.580> I<00:08:45.610> represents<00:08:46.330> not 00:08:46.470 --> 00:08:46.480 align:start position:0% represents you right I represents not 00:08:46.480 --> 00:08:48.270 align:start position:0% represents you right I represents not even<00:08:46.750> a<00:08:46.810> person<00:08:47.170> it<00:08:47.260> could<00:08:47.380> also<00:08:47.590> represent<00:08:47.830> a 00:08:48.270 --> 00:08:48.280 align:start position:0% even a person it could also represent a 00:08:48.280 --> 00:08:52.830 align:start position:0% even a person it could also represent a machine<00:08:48.880> or<00:08:49.120> even<00:08:49.930> could<00:08:50.260> represent<00:08:50.470> a<00:08:51.840> item 00:08:52.830 --> 00:08:52.840 align:start position:0% machine or even could represent a item 00:08:52.840 --> 00:08:59.070 align:start position:0% machine or even could represent a item an<00:08:53.020> object<00:08:53.700> or<00:08:54.700> a<00:08:54.760> company<00:08:57.030> so<00:08:58.030> this<00:08:58.480> identity 00:08:59.070 --> 00:08:59.080 align:start position:0% an object or a company so this identity 00:08:59.080 --> 00:09:01.350 align:start position:0% an object or a company so this identity is<00:08:59.110> standard<00:08:59.710> basically<00:09:00.270> consists<00:09:01.270> out<00:09:01.300> of 00:09:01.350 --> 00:09:01.360 align:start position:0% is standard basically consists out of 00:09:01.360 --> 00:09:04.889 align:start position:0% is standard basically consists out of three<00:09:01.660> components<00:09:02.320> so<00:09:03.070> it<00:09:03.280> itself<00:09:03.970> is<00:09:04.210> a<00:09:04.270> smart 00:09:04.889 --> 00:09:04.899 align:start position:0% three components so it itself is a smart 00:09:04.899 --> 00:09:08.069 align:start position:0% three components so it itself is a smart contract<00:09:05.259> which<00:09:06.249> is<00:09:06.720> representing<00:09:07.720> you<00:09:07.839> and 00:09:08.069 --> 00:09:08.079 align:start position:0% contract which is representing you and 00:09:08.079 --> 00:09:10.019 align:start position:0% contract which is representing you and it<00:09:08.680> has<00:09:08.800> these<00:09:09.009> three<00:09:09.249> components<00:09:09.670> it<00:09:09.999> has 00:09:10.019 --> 00:09:10.029 align:start position:0% it has these three components it has 00:09:10.029 --> 00:09:14.220 align:start position:0% it has these three components it has keys<00:09:10.509> which<00:09:11.470> are<00:09:11.619> your<00:09:11.800> operators<00:09:12.600> either<00:09:13.600> can 00:09:14.220 --> 00:09:14.230 align:start position:0% keys which are your operators either can 00:09:14.230 --> 00:09:15.989 align:start position:0% keys which are your operators either can execute<00:09:14.589> so<00:09:14.949> you<00:09:15.009> can<00:09:15.129> actually<00:09:15.339> act<00:09:15.699> on<00:09:15.879> the 00:09:15.989 --> 00:09:15.999 align:start position:0% execute so you can actually act on the 00:09:15.999 --> 00:09:20.609 align:start position:0% execute so you can actually act on the blockchain<00:09:16.209> su<00:09:16.839> and<00:09:17.079> it<00:09:18.069> has<00:09:18.279> claims<00:09:19.589> so<00:09:20.589> I 00:09:20.609 --> 00:09:20.619 align:start position:0% blockchain su and it has claims so I 00:09:20.619 --> 00:09:22.819 align:start position:0% blockchain su and it has claims so I will<00:09:20.800> explain<00:09:21.160> these<00:09:21.459> three<00:09:21.639> pieces<00:09:22.029> here<00:09:22.509> and 00:09:22.819 --> 00:09:22.829 align:start position:0% will explain these three pieces here and 00:09:22.829 --> 00:09:25.590 align:start position:0% will explain these three pieces here and then<00:09:23.829> show<00:09:24.279> some<00:09:24.309> examples<00:09:24.610> of<00:09:25.119> how<00:09:25.240> this<00:09:25.389> can 00:09:25.590 --> 00:09:25.600 align:start position:0% then show some examples of how this can 00:09:25.600 --> 00:09:28.619 align:start position:0% then show some examples of how this can work<00:09:26.519> the<00:09:27.519> idea<00:09:27.759> is<00:09:27.850> basically<00:09:28.059> that<00:09:28.449> you<00:09:28.600> have 00:09:28.619 --> 00:09:28.629 align:start position:0% work the idea is basically that you have 00:09:28.629 --> 00:09:30.600 align:start position:0% work the idea is basically that you have these<00:09:28.929> keys<00:09:29.230> and<00:09:29.499> this<00:09:29.649> is<00:09:29.800> how<00:09:30.009> you<00:09:30.069> act<00:09:30.399> in 00:09:30.600 --> 00:09:30.610 align:start position:0% these keys and this is how you act in 00:09:30.610 --> 00:09:32.460 align:start position:0% these keys and this is how you act in the<00:09:30.699> world<00:09:30.879> right<00:09:31.389> so<00:09:31.839> for<00:09:31.959> example<00:09:32.230> you<00:09:32.319> can 00:09:32.460 --> 00:09:32.470 align:start position:0% the world right so for example you can 00:09:32.470 --> 00:09:34.079 align:start position:0% the world right so for example you can make<00:09:32.889> transactions<00:09:33.490> obviously<00:09:33.879> on<00:09:33.999> the 00:09:34.079 --> 00:09:34.089 align:start position:0% make transactions obviously on the 00:09:34.089 --> 00:09:35.910 align:start position:0% make transactions obviously on the blockchain<00:09:34.329> you<00:09:34.629> can<00:09:34.839> send<00:09:35.079> money<00:09:35.230> around<00:09:35.589> and 00:09:35.910 --> 00:09:35.920 align:start position:0% blockchain you can send money around and 00:09:35.920 --> 00:09:38.579 align:start position:0% blockchain you can send money around and then<00:09:36.129> you<00:09:36.279> can<00:09:36.309> prove<00:09:37.269> with<00:09:37.540> that<00:09:37.809> that<00:09:38.410> if 00:09:38.579 --> 00:09:38.589 align:start position:0% then you can prove with that that if 00:09:38.589 --> 00:09:39.929 align:start position:0% then you can prove with that that if this<00:09:38.740> is<00:09:38.920> one<00:09:39.129> of<00:09:39.279> your<00:09:39.429> keys<00:09:39.639> in<00:09:39.819> your 00:09:39.929 --> 00:09:39.939 align:start position:0% this is one of your keys in your 00:09:39.939 --> 00:09:42.359 align:start position:0% this is one of your keys in your identity<00:09:40.119> that<00:09:40.449> it<00:09:40.749> obviously<00:09:40.959> must<00:09:41.470> be<00:09:41.589> done 00:09:42.359 --> 00:09:42.369 align:start position:0% identity that it obviously must be done 00:09:42.369 --> 00:09:42.989 align:start position:0% identity that it obviously must be done by<00:09:42.579> you 00:09:42.989 --> 00:09:42.999 align:start position:0% by you 00:09:42.999 --> 00:09:46.230 align:start position:0% by you I<00:09:43.110> can<00:09:44.110> also<00:09:44.290> assign<00:09:44.769> any<00:09:45.160> kind<00:09:45.399> of<00:09:45.490> documents 00:09:46.230 --> 00:09:46.240 align:start position:0% I can also assign any kind of documents 00:09:46.240 --> 00:09:48.389 align:start position:0% I can also assign any kind of documents or<00:09:46.420> I<00:09:46.449> can<00:09:46.720> send<00:09:46.899> assign<00:09:47.259> any<00:09:47.439> kind<00:09:47.649> of<00:09:47.740> proofs 00:09:48.389 --> 00:09:48.399 align:start position:0% or I can send assign any kind of proofs 00:09:48.399 --> 00:09:50.790 align:start position:0% or I can send assign any kind of proofs or<00:09:48.639> messages<00:09:49.209> in<00:09:49.360> the<00:09:49.449> real<00:09:49.600> world<00:09:49.869> proving 00:09:50.790 --> 00:09:50.800 align:start position:0% or messages in the real world proving 00:09:50.800 --> 00:09:51.960 align:start position:0% or messages in the real world proving that<00:09:51.040> it<00:09:51.279> was<00:09:51.309> me 00:09:51.960 --> 00:09:51.970 align:start position:0% that it was me 00:09:51.970 --> 00:09:54.569 align:start position:0% that it was me doing<00:09:52.420> that<00:09:52.629> as<00:09:53.410> long<00:09:53.709> as<00:09:53.860> I<00:09:53.889> attach<00:09:54.339> my 00:09:54.569 --> 00:09:54.579 align:start position:0% doing that as long as I attach my 00:09:54.579 --> 00:09:57.150 align:start position:0% doing that as long as I attach my identity<00:09:55.029> to<00:09:55.059> it<00:09:55.329> the<00:09:55.959> person<00:09:56.439> seeing<00:09:56.980> the 00:09:57.150 --> 00:09:57.160 align:start position:0% identity to it the person seeing the 00:09:57.160 --> 00:09:59.280 align:start position:0% identity to it the person seeing the signature<00:09:57.670> can<00:09:57.939> verify<00:09:58.179> the<00:09:58.420> signature<00:09:58.990> and 00:09:59.280 --> 00:09:59.290 align:start position:0% signature can verify the signature and 00:09:59.290 --> 00:10:01.799 align:start position:0% signature can verify the signature and can<00:09:59.499> assume<00:09:59.860> very<00:10:00.249> high<00:10:00.910> likelihood<00:10:01.240> that<00:10:01.600> it 00:10:01.799 --> 00:10:01.809 align:start position:0% can assume very high likelihood that it 00:10:01.809 --> 00:10:07.619 align:start position:0% can assume very high likelihood that it was<00:10:01.929> me<00:10:04.949> so<00:10:05.949> actually<00:10:06.939> the<00:10:07.119> list<00:10:07.329> is<00:10:07.480> like 00:10:07.619 --> 00:10:07.629 align:start position:0% was me so actually the list is like 00:10:07.629 --> 00:10:09.449 align:start position:0% was me so actually the list is like unlimited<00:10:07.959> because<00:10:08.529> what<00:10:08.769> could<00:10:09.100> do<00:10:09.279> with 00:10:09.449 --> 00:10:09.459 align:start position:0% unlimited because what could do with 00:10:09.459 --> 00:10:11.910 align:start position:0% unlimited because what could do with these<00:10:09.639> kind<00:10:09.850> of<00:10:09.910> things<00:10:10.410> it's<00:10:11.410> like<00:10:11.589> not<00:10:11.889> very 00:10:11.910 --> 00:10:11.920 align:start position:0% these kind of things it's like not very 00:10:11.920 --> 00:10:14.879 align:start position:0% these kind of things it's like not very limited<00:10:12.670> in<00:10:12.819> this<00:10:13.179> sense<00:10:13.449> the<00:10:13.990> idea<00:10:14.350> is<00:10:14.499> and 00:10:14.879 --> 00:10:14.889 align:start position:0% limited in this sense the idea is and 00:10:14.889 --> 00:10:17.639 align:start position:0% limited in this sense the idea is and it's<00:10:15.279> the<00:10:15.490> beauty<00:10:15.850> of<00:10:16.050> public<00:10:17.050> private<00:10:17.259> key 00:10:17.639 --> 00:10:17.649 align:start position:0% it's the beauty of public private key 00:10:17.649 --> 00:10:19.980 align:start position:0% it's the beauty of public private key cryptography<00:10:18.069> is<00:10:18.610> that<00:10:19.149> we<00:10:19.269> can<00:10:19.509> have<00:10:19.749> this 00:10:19.980 --> 00:10:19.990 align:start position:0% cryptography is that we can have this 00:10:19.990 --> 00:10:22.590 align:start position:0% cryptography is that we can have this kind<00:10:20.290> of<00:10:20.410> control<00:10:21.189> over<00:10:21.220> we<00:10:22.089> can<00:10:22.209> basically 00:10:22.590 --> 00:10:22.600 align:start position:0% kind of control over we can basically 00:10:22.600 --> 00:10:25.019 align:start position:0% kind of control over we can basically like<00:10:22.839> validate<00:10:23.470> ourselves<00:10:24.279> in<00:10:24.399> in<00:10:24.670> the<00:10:24.850> real 00:10:25.019 --> 00:10:25.029 align:start position:0% like validate ourselves in in the real 00:10:25.029 --> 00:10:28.619 align:start position:0% like validate ourselves in in the real world<00:10:25.300> and<00:10:25.870> others<00:10:26.199> can<00:10:26.379> probably<00:10:27.629> validate 00:10:28.619 --> 00:10:28.629 align:start position:0% world and others can probably validate 00:10:28.629 --> 00:10:30.480 align:start position:0% world and others can probably validate this<00:10:28.749> this<00:10:29.230> as<00:10:29.379> well<00:10:29.589> they<00:10:29.829> can<00:10:29.860> check<00:10:30.279> that 00:10:30.480 --> 00:10:30.490 align:start position:0% this this as well they can check that 00:10:30.490 --> 00:10:33.360 align:start position:0% this this as well they can check that this<00:10:30.670> is<00:10:30.730> correct<00:10:30.879> without<00:10:31.839> ever<00:10:32.410> I<00:10:32.860> ever<00:10:33.129> have 00:10:33.360 --> 00:10:33.370 align:start position:0% this is correct without ever I ever have 00:10:33.370 --> 00:10:35.790 align:start position:0% this is correct without ever I ever have to<00:10:33.519> reveal<00:10:33.819> my<00:10:34.029> password<00:10:34.569> or<00:10:34.809> my<00:10:34.990> secrets<00:10:35.679> or 00:10:35.790 --> 00:10:35.800 align:start position:0% to reveal my password or my secrets or 00:10:35.800 --> 00:10:39.629 align:start position:0% to reveal my password or my secrets or whatever<00:10:36.269> and<00:10:37.269> I<00:10:38.139> think<00:10:38.410> we<00:10:38.559> are<00:10:38.769> just<00:10:39.399> getting 00:10:39.629 --> 00:10:39.639 align:start position:0% whatever and I think we are just getting 00:10:39.639 --> 00:10:43.769 align:start position:0% whatever and I think we are just getting started<00:10:40.269> into<00:10:40.389> the<00:10:40.569> h<00:10:40.809> of<00:10:41.670> key<00:10:42.670> signing<00:10:43.480> right 00:10:43.769 --> 00:10:43.779 align:start position:0% started into the h of key signing right 00:10:43.779 --> 00:10:45.869 align:start position:0% started into the h of key signing right so<00:10:44.110> what<00:10:44.290> we<00:10:44.379> do<00:10:44.499> this<00:10:44.649> in<00:10:44.800> all<00:10:45.040> the<00:10:45.100> time<00:10:45.670> for 00:10:45.869 --> 00:10:45.879 align:start position:0% so what we do this in all the time for 00:10:45.879 --> 00:10:48.660 align:start position:0% so what we do this in all the time for basically<00:10:46.149> everything<00:10:46.889> and<00:10:47.889> a<00:10:48.309> really<00:10:48.519> simple 00:10:48.660 --> 00:10:48.670 align:start position:0% basically everything and a really simple 00:10:48.670 --> 00:10:50.280 align:start position:0% basically everything and a really simple use<00:10:48.939> case<00:10:49.149> for<00:10:49.179> this<00:10:49.389> for<00:10:49.870> example<00:10:49.899> would<00:10:50.230> be 00:10:50.280 --> 00:10:50.290 align:start position:0% use case for this for example would be 00:10:50.290 --> 00:10:53.910 align:start position:0% use case for this for example would be logins<00:10:50.829> right<00:10:51.160> I<00:10:51.189> can<00:10:51.519> simply<00:10:52.499> sign<00:10:53.499> a<00:10:53.529> message 00:10:53.910 --> 00:10:53.920 align:start position:0% logins right I can simply sign a message 00:10:53.920 --> 00:10:55.799 align:start position:0% logins right I can simply sign a message I<00:10:54.100> want<00:10:54.279> to<00:10:54.370> go<00:10:54.459> into<00:10:54.670> your<00:10:54.819> website<00:10:55.240> and<00:10:55.269> they 00:10:55.799 --> 00:10:55.809 align:start position:0% I want to go into your website and they 00:10:55.809 --> 00:10:57.689 align:start position:0% I want to go into your website and they can<00:10:55.990> prove<00:10:56.199> that<00:10:56.259> maybe<00:10:56.860> even<00:10:57.220> check<00:10:57.670> my 00:10:57.689 --> 00:10:57.699 align:start position:0% can prove that maybe even check my 00:10:57.699 --> 00:10:59.730 align:start position:0% can prove that maybe even check my identity<00:10:58.329> and<00:10:58.629> do<00:10:59.319> some<00:10:59.499> kind<00:10:59.679> of 00:10:59.730 --> 00:10:59.740 align:start position:0% identity and do some kind of 00:10:59.740 --> 00:11:01.739 align:start position:0% identity and do some kind of verification<00:11:00.009> process<00:11:00.730> and<00:11:01.119> they<00:11:01.299> can<00:11:01.329> let<00:11:01.569> me 00:11:01.739 --> 00:11:01.749 align:start position:0% verification process and they can let me 00:11:01.749 --> 00:11:03.689 align:start position:0% verification process and they can let me in<00:11:01.779> and<00:11:02.199> I<00:11:02.319> never<00:11:02.619> send<00:11:02.920> my<00:11:03.009> password<00:11:03.399> over<00:11:03.519> the 00:11:03.689 --> 00:11:03.699 align:start position:0% in and I never send my password over the 00:11:03.699 --> 00:11:05.970 align:start position:0% in and I never send my password over the wire<00:11:03.879> or<00:11:04.629> anything<00:11:05.049> and<00:11:05.350> I<00:11:05.379> could<00:11:05.529> even<00:11:05.679> use<00:11:05.949> a 00:11:05.970 --> 00:11:05.980 align:start position:0% wire or anything and I could even use a 00:11:05.980 --> 00:11:10.139 align:start position:0% wire or anything and I could even use a third<00:11:06.339> party<00:11:06.369> to<00:11:07.360> fact<00:11:07.660> education<00:11:08.290> device<00:11:09.149> the 00:11:10.139 --> 00:11:10.149 align:start position:0% third party to fact education device the 00:11:10.149 --> 00:11:12.989 align:start position:0% third party to fact education device the other<00:11:10.329> part<00:11:10.689> is<00:11:10.959> and<00:11:11.490> because<00:11:12.490> it's<00:11:12.759> a<00:11:12.819> smart 00:11:12.989 --> 00:11:12.999 align:start position:0% other part is and because it's a smart 00:11:12.999 --> 00:11:15.780 align:start position:0% other part is and because it's a smart contract<00:11:13.509> I<00:11:13.660> can<00:11:13.959> execute<00:11:14.350> so<00:11:14.949> this<00:11:15.370> standard 00:11:15.780 --> 00:11:15.790 align:start position:0% contract I can execute so this standard 00:11:15.790 --> 00:11:18.900 align:start position:0% contract I can execute so this standard has<00:11:15.819> a<00:11:16.240> execute<00:11:16.990> function<00:11:17.309> which<00:11:18.309> allows<00:11:18.519> you 00:11:18.900 --> 00:11:18.910 align:start position:0% has a execute function which allows you 00:11:18.910 --> 00:11:22.410 align:start position:0% has a execute function which allows you to<00:11:19.089> act<00:11:19.329> as<00:11:19.769> yourself<00:11:20.769> on<00:11:21.009> the<00:11:21.100> blockchain<00:11:21.420> so 00:11:22.410 --> 00:11:22.420 align:start position:0% to act as yourself on the blockchain so 00:11:22.420 --> 00:11:24.539 align:start position:0% to act as yourself on the blockchain so you<00:11:22.509> could<00:11:22.779> either<00:11:22.990> use<00:11:23.139> the<00:11:23.499> keys<00:11:23.740> to<00:11:24.429> do 00:11:24.539 --> 00:11:24.549 align:start position:0% you could either use the keys to do 00:11:24.549 --> 00:11:25.710 align:start position:0% you could either use the keys to do actions<00:11:24.879> on<00:11:24.970> the<00:11:25.059> blockchain<00:11:25.299> and<00:11:25.480> then 00:11:25.710 --> 00:11:25.720 align:start position:0% actions on the blockchain and then 00:11:25.720 --> 00:11:28.169 align:start position:0% actions on the blockchain and then somehow<00:11:25.959> like<00:11:26.519> point<00:11:27.519> the<00:11:27.759> people<00:11:27.939> you 00:11:28.169 --> 00:11:28.179 align:start position:0% somehow like point the people you 00:11:28.179 --> 00:11:29.819 align:start position:0% somehow like point the people you interact<00:11:28.480> with<00:11:28.779> to<00:11:29.049> your<00:11:29.170> identity<00:11:29.649> so<00:11:29.799> they 00:11:29.819 --> 00:11:29.829 align:start position:0% interact with to your identity so they 00:11:29.829 --> 00:11:32.369 align:start position:0% interact with to your identity so they can<00:11:30.040> check<00:11:30.189> things<00:11:30.490> about<00:11:30.759> you<00:11:30.970> or<00:11:31.870> you<00:11:32.199> can 00:11:32.369 --> 00:11:32.379 align:start position:0% can check things about you or you can 00:11:32.379 --> 00:11:34.199 align:start position:0% can check things about you or you can actually<00:11:32.529> act<00:11:33.100> directly<00:11:33.699> through<00:11:33.970> your 00:11:34.199 --> 00:11:34.209 align:start position:0% actually act directly through your 00:11:34.209 --> 00:11:38.340 align:start position:0% actually act directly through your contract<00:11:34.689> and<00:11:36.089> the<00:11:37.089> important<00:11:37.809> thing<00:11:37.839> is<00:11:38.110> that 00:11:38.340 --> 00:11:38.350 align:start position:0% contract and the important thing is that 00:11:38.350 --> 00:11:40.739 align:start position:0% contract and the important thing is that you<00:11:38.529> can<00:11:38.769> add<00:11:38.980> other<00:11:39.220> claims<00:11:39.669> to<00:11:40.540> other 00:11:40.739 --> 00:11:40.749 align:start position:0% you can add other claims to other 00:11:40.749 --> 00:11:43.530 align:start position:0% you can add other claims to other identities<00:11:41.529> although<00:11:42.129> other<00:11:42.339> people<00:11:42.540> objects 00:11:43.530 --> 00:11:43.540 align:start position:0% identities although other people objects 00:11:43.540 --> 00:11:45.239 align:start position:0% identities although other people objects or<00:11:43.749> even<00:11:43.990> other<00:11:44.139> smart<00:11:44.529> contracts<00:11:45.100> which 00:11:45.239 --> 00:11:45.249 align:start position:0% or even other smart contracts which 00:11:45.249 --> 00:11:48.179 align:start position:0% or even other smart contracts which might<00:11:45.459> just<00:11:45.699> be<00:11:45.819> code<00:11:46.029> and<00:11:46.709> you<00:11:47.709> can<00:11:47.889> claim 00:11:48.179 --> 00:11:48.189 align:start position:0% might just be code and you can claim 00:11:48.189 --> 00:11:50.159 align:start position:0% might just be code and you can claim that<00:11:48.490> for<00:11:48.699> example<00:11:49.059> you<00:11:49.149> verified<00:11:49.660> them<00:11:49.899> or 00:11:50.159 --> 00:11:50.169 align:start position:0% that for example you verified them or 00:11:50.169 --> 00:11:52.379 align:start position:0% that for example you verified them or maybe<00:11:50.889> you're<00:11:51.160> an<00:11:51.220> issuer<00:11:51.579> about<00:11:52.059> claims 00:11:52.379 --> 00:11:52.389 align:start position:0% maybe you're an issuer about claims 00:11:52.389 --> 00:11:54.689 align:start position:0% maybe you're an issuer about claims maybe<00:11:52.720> a<00:11:52.839> government<00:11:53.350> and<00:11:53.589> you<00:11:53.620> can<00:11:54.370> attach 00:11:54.689 --> 00:11:54.699 align:start position:0% maybe a government and you can attach 00:11:54.699 --> 00:11:57.650 align:start position:0% maybe a government and you can attach claims<00:11:55.120> and<00:11:55.449> it's<00:11:55.600> very<00:11:55.809> probably<00:11:56.639> coming 00:11:57.650 --> 00:11:57.660 align:start position:0% claims and it's very probably coming 00:11:57.660 --> 00:12:02.699 align:start position:0% claims and it's very probably coming from<00:11:58.660> that<00:11:58.929> identity<00:12:00.480> and<00:12:01.480> the<00:12:02.199> third<00:12:02.439> part 00:12:02.699 --> 00:12:02.709 align:start position:0% from that identity and the third part 00:12:02.709 --> 00:12:04.460 align:start position:0% from that identity and the third part and<00:12:02.889> that's<00:12:03.009> actually<00:12:03.189> the<00:12:03.399> important<00:12:03.879> part 00:12:04.460 --> 00:12:04.470 align:start position:0% and that's actually the important part 00:12:04.470 --> 00:12:08.309 align:start position:0% and that's actually the important part which<00:12:05.470> is<00:12:05.679> its<00:12:05.919> own<00:12:06.160> ERC<00:12:07.169> after<00:12:08.169> some 00:12:08.309 --> 00:12:08.319 align:start position:0% which is its own ERC after some 00:12:08.319 --> 00:12:11.069 align:start position:0% which is its own ERC after some discussion<00:12:08.439> we<00:12:09.309> decided<00:12:09.509> moving<00:12:10.509> it<00:12:10.629> out<00:12:10.809> in 00:12:11.069 --> 00:12:11.079 align:start position:0% discussion we decided moving it out in 00:12:11.079 --> 00:12:15.210 align:start position:0% discussion we decided moving it out in ESC<00:12:11.529> seven<00:12:12.100> three<00:12:12.399> five<00:12:12.699> and<00:12:14.220> basically 00:12:15.210 --> 00:12:15.220 align:start position:0% ESC seven three five and basically 00:12:15.220 --> 00:12:16.799 align:start position:0% ESC seven three five and basically making<00:12:15.370> it<00:12:15.549> substandard<00:12:16.120> after<00:12:16.449> seven<00:12:16.689> to 00:12:16.799 --> 00:12:16.809 align:start position:0% making it substandard after seven to 00:12:16.809 --> 00:12:20.939 align:start position:0% making it substandard after seven to five<00:12:17.049> and<00:12:17.889> the<00:12:18.339> idea<00:12:18.639> is<00:12:18.790> really<00:12:19.029> to<00:12:19.679> have<00:12:20.679> a 00:12:20.939 --> 00:12:20.949 align:start position:0% five and the idea is really to have a 00:12:20.949 --> 00:12:23.579 align:start position:0% five and the idea is really to have a way<00:12:21.160> to<00:12:21.220> attach<00:12:21.790> claims<00:12:22.419> to<00:12:22.779> a<00:12:22.809> smart<00:12:23.110> contract 00:12:23.579 --> 00:12:23.589 align:start position:0% way to attach claims to a smart contract 00:12:23.589 --> 00:12:25.919 align:start position:0% way to attach claims to a smart contract and<00:12:23.860> now<00:12:24.279> we<00:12:24.339> have<00:12:24.610> all<00:12:24.850> to<00:12:25.029> debate<00:12:25.299> exactly 00:12:25.919 --> 00:12:25.929 align:start position:0% and now we have all to debate exactly 00:12:25.929 --> 00:12:27.929 align:start position:0% and now we have all to debate exactly how<00:12:26.049> this<00:12:26.199> can<00:12:26.379> look<00:12:26.559> like<00:12:26.589> and<00:12:27.249> I<00:12:27.610> have<00:12:27.790> an 00:12:27.929 --> 00:12:27.939 align:start position:0% how this can look like and I have an 00:12:27.939 --> 00:12:29.819 align:start position:0% how this can look like and I have an initial<00:12:28.299> craft<00:12:28.600> up<00:12:28.870> their<00:12:29.110> hardest<00:12:29.529> can<00:12:29.679> look 00:12:29.819 --> 00:12:29.829 align:start position:0% initial craft up their hardest can look 00:12:29.829 --> 00:12:32.999 align:start position:0% initial craft up their hardest can look like<00:12:29.980> and<00:12:30.160> how<00:12:30.249> it<00:12:30.370> can<00:12:30.490> work<00:12:31.019> the<00:12:32.019> benefit<00:12:32.980> of 00:12:32.999 --> 00:12:33.009 align:start position:0% like and how it can work the benefit of 00:12:33.009 --> 00:12:36.600 align:start position:0% like and how it can work the benefit of claims<00:12:33.540> in<00:12:34.540> your<00:12:35.319> own<00:12:35.439> identity<00:12:35.679> it<00:12:36.249> can<00:12:36.279> be 00:12:36.600 --> 00:12:36.610 align:start position:0% claims in your own identity it can be 00:12:36.610 --> 00:12:38.970 align:start position:0% claims in your own identity it can be added<00:12:36.850> by<00:12:36.879> anyone<00:12:37.419> but<00:12:37.959> I<00:12:38.019> always<00:12:38.350> have<00:12:38.829> to 00:12:38.970 --> 00:12:38.980 align:start position:0% added by anyone but I always have to 00:12:38.980 --> 00:12:41.159 align:start position:0% added by anyone but I always have to prove<00:12:39.220> it<00:12:39.399> right<00:12:39.610> if<00:12:39.910> it's<00:12:40.089> my<00:12:40.269> identity<00:12:40.899> I 00:12:41.159 --> 00:12:41.169 align:start position:0% prove it right if it's my identity I 00:12:41.169 --> 00:12:43.739 align:start position:0% prove it right if it's my identity I want<00:12:41.829> to<00:12:41.949> need<00:12:42.100> to<00:12:42.129> know<00:12:42.490> I<00:12:42.939> want<00:12:43.360> to<00:12:43.509> be<00:12:43.629> able 00:12:43.739 --> 00:12:43.749 align:start position:0% want to need to know I want to be able 00:12:43.749 --> 00:12:45.299 align:start position:0% want to need to know I want to be able to<00:12:43.990> approve<00:12:44.259> it<00:12:44.470> because<00:12:44.620> I<00:12:44.829> don't<00:12:44.889> want<00:12:45.160> that 00:12:45.299 --> 00:12:45.309 align:start position:0% to approve it because I don't want that 00:12:45.309 --> 00:12:47.970 align:start position:0% to approve it because I don't want that things<00:12:45.549> are<00:12:45.759> attached<00:12:46.029> to<00:12:46.209> my<00:12:46.360> identity<00:12:46.980> which 00:12:47.970 --> 00:12:47.980 align:start position:0% things are attached to my identity which 00:12:47.980 --> 00:12:49.650 align:start position:0% things are attached to my identity which I<00:12:48.069> don't<00:12:48.249> really<00:12:48.519> agree<00:12:48.730> to<00:12:48.999> this<00:12:49.509> is 00:12:49.650 --> 00:12:49.660 align:start position:0% I don't really agree to this is 00:12:49.660 --> 00:12:51.960 align:start position:0% I don't really agree to this is especially<00:12:49.990> important<00:12:50.559> if<00:12:50.620> I'm<00:12:50.769> a<00:12:50.860> person<00:12:51.100> if 00:12:51.960 --> 00:12:51.970 align:start position:0% especially important if I'm a person if 00:12:51.970 --> 00:12:53.850 align:start position:0% especially important if I'm a person if I'm<00:12:52.240> a<00:12:52.360> smart<00:12:52.629> contract<00:12:53.079> maybe<00:12:53.350> an<00:12:53.529> approval 00:12:53.850 --> 00:12:53.860 align:start position:0% I'm a smart contract maybe an approval 00:12:53.860 --> 00:12:55.829 align:start position:0% I'm a smart contract maybe an approval is<00:12:53.949> not<00:12:54.100> even<00:12:54.309> needed<00:12:54.610> maybe<00:12:55.329> a<00:12:55.480> smartphone 00:12:55.829 --> 00:12:55.839 align:start position:0% is not even needed maybe a smartphone 00:12:55.839 --> 00:12:58.980 align:start position:0% is not even needed maybe a smartphone you<00:12:56.019> can<00:12:56.049> just<00:12:56.350> like<00:12:56.499> get<00:12:57.189> a<00:12:57.249> bunch<00:12:57.610> of<00:12:57.990> claims 00:12:58.980 --> 00:12:58.990 align:start position:0% you can just like get a bunch of claims 00:12:58.990 --> 00:13:03.389 align:start position:0% you can just like get a bunch of claims and<00:12:59.350> randomly<00:12:59.949> people<00:13:00.309> can<00:13:00.429> do<00:13:00.610> that<00:13:01.769> and<00:13:02.769> it 00:13:03.389 --> 00:13:03.399 align:start position:0% and randomly people can do that and it 00:13:03.399 --> 00:13:05.989 align:start position:0% and randomly people can do that and it can't<00:13:03.669> be<00:13:03.790> changed<00:13:03.819> without<00:13:04.360> my<00:13:04.660> permission 00:13:05.989 --> 00:13:05.999 align:start position:0% can't be changed without my permission 00:13:05.999 --> 00:13:08.220 align:start position:0% can't be changed without my permission now<00:13:06.999> I<00:13:07.029> can<00:13:07.329> be<00:13:07.449> changed<00:13:07.809> without<00:13:07.929> my 00:13:08.220 --> 00:13:08.230 align:start position:0% now I can be changed without my 00:13:08.230 --> 00:13:10.650 align:start position:0% now I can be changed without my permission<00:13:08.470> so<00:13:08.860> basically<00:13:09.209> the<00:13:10.209> person<00:13:10.629> who 00:13:10.650 --> 00:13:10.660 align:start position:0% permission so basically the person who 00:13:10.660 --> 00:13:13.559 align:start position:0% permission so basically the person who issued<00:13:11.079> to<00:13:11.230> claim<00:13:11.529> about<00:13:11.860> me<00:13:12.129> on<00:13:12.910> my<00:13:13.120> identity 00:13:13.559 --> 00:13:13.569 align:start position:0% issued to claim about me on my identity 00:13:13.569 --> 00:13:15.150 align:start position:0% issued to claim about me on my identity once<00:13:13.779> I<00:13:13.929> approved<00:13:14.290> it<00:13:14.529> they<00:13:14.709> are<00:13:14.799> technically 00:13:15.150 --> 00:13:15.160 align:start position:0% once I approved it they are technically 00:13:15.160 --> 00:13:17.600 align:start position:0% once I approved it they are technically in<00:13:15.279> control<00:13:15.669> because<00:13:16.209> they<00:13:16.389> issued<00:13:16.809> it<00:13:16.990> right 00:13:17.600 --> 00:13:17.610 align:start position:0% in control because they issued it right 00:13:17.610 --> 00:13:19.949 align:start position:0% in control because they issued it right but<00:13:18.610> if<00:13:18.759> I<00:13:18.850> don't<00:13:19.029> focus<00:13:19.240> I<00:13:19.389> have<00:13:19.569> to<00:13:19.660> change 00:13:19.949 --> 00:13:19.959 align:start position:0% but if I don't focus I have to change 00:13:19.959 --> 00:13:21.840 align:start position:0% but if I don't focus I have to change something<00:13:20.259> about<00:13:20.499> the<00:13:20.740> claim<00:13:21.009> and<00:13:21.279> I'm<00:13:21.669> not 00:13:21.840 --> 00:13:21.850 align:start position:0% something about the claim and I'm not 00:13:21.850 --> 00:13:23.399 align:start position:0% something about the claim and I'm not agreeing<00:13:21.970> I<00:13:22.509> could<00:13:22.720> always<00:13:22.870> remove<00:13:23.230> it 00:13:23.399 --> 00:13:23.409 align:start position:0% agreeing I could always remove it 00:13:23.409 --> 00:13:25.740 align:start position:0% agreeing I could always remove it because<00:13:24.129> it's<00:13:24.429> on<00:13:24.549> my<00:13:24.579> identity<00:13:25.209> so<00:13:25.449> I<00:13:25.480> can 00:13:25.740 --> 00:13:25.750 align:start position:0% because it's on my identity so I can 00:13:25.750 --> 00:13:27.809 align:start position:0% because it's on my identity so I can allow<00:13:25.990> it<00:13:26.169> to<00:13:26.289> add<00:13:26.470> but<00:13:26.620> I<00:13:26.679> can<00:13:26.829> also<00:13:26.980> take<00:13:27.669> it 00:13:27.809 --> 00:13:27.819 align:start position:0% allow it to add but I can also take it 00:13:27.819 --> 00:13:30.029 align:start position:0% allow it to add but I can also take it off<00:13:27.939> any<00:13:28.120> time<00:13:28.419> if<00:13:28.839> I<00:13:28.959> disagree<00:13:29.439> with<00:13:29.470> a<00:13:29.679> change 00:13:30.029 --> 00:13:30.039 align:start position:0% off any time if I disagree with a change 00:13:30.039 --> 00:13:31.269 align:start position:0% off any time if I disagree with a change or<00:13:30.250> for<00:13:30.399> example<00:13:30.490> if<00:13:30.759> the<00:13:30.879> change 00:13:31.269 --> 00:13:31.279 align:start position:0% or for example if the change 00:13:31.279 --> 00:13:35.889 align:start position:0% or for example if the change the<00:13:31.339> data<00:13:31.600> hash<00:13:32.600> and<00:13:33.040> I<00:13:34.040> never<00:13:34.430> really<00:13:34.850> was<00:13:35.629> in 00:13:35.889 --> 00:13:35.899 align:start position:0% the data hash and I never really was in 00:13:35.899 --> 00:13:39.879 align:start position:0% the data hash and I never really was in their<00:13:36.019> office<00:13:36.319> again<00:13:36.589> or<00:13:36.769> whatever<00:13:37.480> and<00:13:38.889> the 00:13:39.879 --> 00:13:39.889 align:start position:0% their office again or whatever and the 00:13:39.889 --> 00:13:41.199 align:start position:0% their office again or whatever and the important<00:13:40.310> thing<00:13:40.370> about<00:13:40.519> the<00:13:40.970> claim 00:13:41.199 --> 00:13:41.209 align:start position:0% important thing about the claim 00:13:41.209 --> 00:13:45.179 align:start position:0% important thing about the claim structure<00:13:41.870> in<00:13:42.139> this<00:13:42.550> standard<00:13:43.550> is<00:13:43.730> that<00:13:44.149> the 00:13:45.179 --> 00:13:45.189 align:start position:0% structure in this standard is that the 00:13:45.189 --> 00:13:47.619 align:start position:0% structure in this standard is that the claim<00:13:46.189> itself<00:13:46.519> contains<00:13:47.060> an<00:13:47.240> actual 00:13:47.619 --> 00:13:47.629 align:start position:0% claim itself contains an actual 00:13:47.629 --> 00:13:51.069 align:start position:0% claim itself contains an actual signature<00:13:48.019> and<00:13:49.059> the<00:13:50.059> beauty<00:13:50.389> about<00:13:50.480> having<00:13:50.930> it 00:13:51.069 --> 00:13:51.079 align:start position:0% signature and the beauty about having it 00:13:51.079 --> 00:13:52.389 align:start position:0% signature and the beauty about having it in<00:13:51.230> the<00:13:51.350> smart<00:13:51.649> Condor<00:13:51.949> and<00:13:52.040> having<00:13:52.309> a 00:13:52.389 --> 00:13:52.399 align:start position:0% in the smart Condor and having a 00:13:52.399 --> 00:13:54.129 align:start position:0% in the smart Condor and having a signature<00:13:52.819> that<00:13:53.120> this<00:13:53.300> could<00:13:53.509> be<00:13:53.660> any<00:13:53.809> kind<00:13:54.019> of 00:13:54.129 --> 00:13:54.139 align:start position:0% signature that this could be any kind of 00:13:54.139 --> 00:13:56.439 align:start position:0% signature that this could be any kind of signature<00:13:54.759> the<00:13:55.759> difference<00:13:56.149> here<00:13:56.329> for 00:13:56.439 --> 00:13:56.449 align:start position:0% signature the difference here for 00:13:56.449 --> 00:13:58.030 align:start position:0% signature the difference here for example<00:13:56.660> if<00:13:56.870> you<00:13:56.959> would<00:13:57.110> make<00:13:57.290> a<00:13:57.319> registry<00:13:57.920> of 00:13:58.030 --> 00:13:58.040 align:start position:0% example if you would make a registry of 00:13:58.040 --> 00:14:00.699 align:start position:0% example if you would make a registry of claims<00:13:58.339> then<00:13:59.120> it's<00:13:59.329> always<00:13:59.689> they<00:13:59.839> always<00:14:00.259> have 00:14:00.699 --> 00:14:00.709 align:start position:0% claims then it's always they always have 00:14:00.709 --> 00:14:03.160 align:start position:0% claims then it's always they always have to<00:14:00.860> be<00:14:00.980> an<00:14:01.160> aetherium<00:14:01.870> signature<00:14:02.870> it's<00:14:03.019> and 00:14:03.160 --> 00:14:03.170 align:start position:0% to be an aetherium signature it's and 00:14:03.170 --> 00:14:04.569 align:start position:0% to be an aetherium signature it's and theorem<00:14:03.439> transaction<00:14:04.040> and<00:14:04.220> this<00:14:04.370> month 00:14:04.569 --> 00:14:04.579 align:start position:0% theorem transaction and this month 00:14:04.579 --> 00:14:06.189 align:start position:0% theorem transaction and this month conduct<00:14:04.879> registry<00:14:05.329> will<00:14:05.569> determine<00:14:05.870> how 00:14:06.189 --> 00:14:06.199 align:start position:0% conduct registry will determine how 00:14:06.199 --> 00:14:08.769 align:start position:0% conduct registry will determine how these<00:14:06.439> claims<00:14:07.339> are<00:14:07.490> added<00:14:07.850> but<00:14:08.420> this<00:14:08.600> is<00:14:08.749> a 00:14:08.769 --> 00:14:08.779 align:start position:0% these claims are added but this is a 00:14:08.779 --> 00:14:11.499 align:start position:0% these claims are added but this is a really<00:14:09.110> open<00:14:09.439> container<00:14:09.829> because<00:14:10.670> it<00:14:11.209> can<00:14:11.389> be 00:14:11.499 --> 00:14:11.509 align:start position:0% really open container because it can be 00:14:11.509 --> 00:14:13.119 align:start position:0% really open container because it can be all<00:14:11.629> kind<00:14:11.870> of<00:14:11.899> different<00:14:12.290> type<00:14:12.559> of<00:14:12.589> signatures 00:14:13.119 --> 00:14:13.129 align:start position:0% all kind of different type of signatures 00:14:13.129 --> 00:14:14.290 align:start position:0% all kind of different type of signatures in<00:14:13.249> the<00:14:13.279> future<00:14:13.610> doesn't<00:14:13.910> need<00:14:13.999> to<00:14:14.089> be<00:14:14.180> in<00:14:14.240> a 00:14:14.290 --> 00:14:14.300 align:start position:0% in the future doesn't need to be in a 00:14:14.300 --> 00:14:18.759 align:start position:0% in the future doesn't need to be in a theorem<00:14:14.569> 1<00:14:14.749> it<00:14:14.870> could<00:14:14.990> be<00:14:15.050> anything<00:14:15.589> and<00:14:17.769> it 00:14:18.759 --> 00:14:18.769 align:start position:0% theorem 1 it could be anything and it 00:14:18.769 --> 00:14:20.519 align:start position:0% theorem 1 it could be anything and it obviously<00:14:19.189> contains<00:14:19.579> the<00:14:19.819> actual<00:14:19.970> claim 00:14:20.519 --> 00:14:20.529 align:start position:0% obviously contains the actual claim 00:14:20.529 --> 00:14:23.470 align:start position:0% obviously contains the actual claim reference<00:14:21.529> or<00:14:22.370> claim<00:14:22.759> data<00:14:22.999> it<00:14:23.329> really 00:14:23.470 --> 00:14:23.480 align:start position:0% reference or claim data it really 00:14:23.480 --> 00:14:25.689 align:start position:0% reference or claim data it really depends<00:14:23.899> on<00:14:23.959> what<00:14:24.079> kind<00:14:24.319> of<00:14:24.350> claim<00:14:24.620> it<00:14:24.769> is<00:14:24.920> most 00:14:25.689 --> 00:14:25.699 align:start position:0% depends on what kind of claim it is most 00:14:25.699 --> 00:14:27.790 align:start position:0% depends on what kind of claim it is most of<00:14:25.939> the<00:14:26.120> cases<00:14:26.149> you<00:14:26.540> don't<00:14:26.809> want<00:14:26.990> to<00:14:27.139> store<00:14:27.559> any 00:14:27.790 --> 00:14:27.800 align:start position:0% of the cases you don't want to store any 00:14:27.800 --> 00:14:29.650 align:start position:0% of the cases you don't want to store any kind<00:14:28.100> of<00:14:28.220> actual<00:14:28.730> data<00:14:29.029> on<00:14:29.300> the<00:14:29.420> blockchain 00:14:29.650 --> 00:14:29.660 align:start position:0% kind of actual data on the blockchain 00:14:29.660 --> 00:14:31.150 align:start position:0% kind of actual data on the blockchain you<00:14:29.930> don't<00:14:30.110> want<00:14:30.259> to<00:14:30.350> store<00:14:30.559> an<00:14:30.620> extra<00:14:30.709> claim 00:14:31.150 --> 00:14:31.160 align:start position:0% you don't want to store an extra claim 00:14:31.160 --> 00:14:35.019 align:start position:0% you don't want to store an extra claim like<00:14:31.490> it<00:14:31.639> may<00:14:31.759> be<00:14:31.819> here<00:14:32.180> your<00:14:33.550> the<00:14:34.550> bytes<00:14:34.790> of 00:14:35.019 --> 00:14:35.029 align:start position:0% like it may be here your the bytes of 00:14:35.029 --> 00:14:37.569 align:start position:0% like it may be here your the bytes of your<00:14:35.240> photo<00:14:35.480> or<00:14:35.980> maybe<00:14:36.980> your<00:14:37.189> actually 00:14:37.569 --> 00:14:37.579 align:start position:0% your photo or maybe your actually 00:14:37.579 --> 00:14:40.090 align:start position:0% your photo or maybe your actually address<00:14:37.939> you<00:14:38.449> only<00:14:38.629> want<00:14:38.899> to<00:14:38.990> claim<00:14:39.319> at<00:14:40.040> the 00:14:40.090 --> 00:14:40.100 align:start position:0% address you only want to claim at the 00:14:40.100 --> 00:14:43.090 align:start position:0% address you only want to claim at the claim<00:14:40.670> with<00:14:40.910> the<00:14:41.059> reference<00:14:41.649> to<00:14:42.649> the<00:14:42.769> actual 00:14:43.090 --> 00:14:43.100 align:start position:0% claim with the reference to the actual 00:14:43.100 --> 00:14:45.369 align:start position:0% claim with the reference to the actual data<00:14:43.250> so<00:14:44.089> the<00:14:44.240> actual<00:14:44.509> data<00:14:44.750> will<00:14:44.959> still<00:14:44.990> sit 00:14:45.369 --> 00:14:45.379 align:start position:0% data so the actual data will still sit 00:14:45.379 --> 00:14:47.199 align:start position:0% data so the actual data will still sit somewhere<00:14:45.680> else<00:14:45.860> and<00:14:46.160> this<00:14:46.309> is<00:14:46.459> to<00:14:46.610> be<00:14:46.759> debated 00:14:47.199 --> 00:14:47.209 align:start position:0% somewhere else and this is to be debated 00:14:47.209 --> 00:14:50.019 align:start position:0% somewhere else and this is to be debated this<00:14:47.480> could<00:14:47.689> be<00:14:47.839> sitting<00:14:48.110> in<00:14:48.350> swarm<00:14:48.769> ipfs<00:14:49.519> or 00:14:50.019 --> 00:14:50.029 align:start position:0% this could be sitting in swarm ipfs or 00:14:50.029 --> 00:14:51.639 align:start position:0% this could be sitting in swarm ipfs or this<00:14:50.360> could<00:14:50.509> be<00:14:50.660> sitting<00:14:50.899> with<00:14:51.110> the<00:14:51.170> company 00:14:51.639 --> 00:14:51.649 align:start position:0% this could be sitting with the company 00:14:51.649 --> 00:14:55.119 align:start position:0% this could be sitting with the company directly<00:14:52.100> still<00:14:53.379> but<00:14:54.379> in<00:14:54.500> some<00:14:54.649> cases<00:14:54.860> even 00:14:55.119 --> 00:14:55.129 align:start position:0% directly still but in some cases even 00:14:55.129 --> 00:14:57.639 align:start position:0% directly still but in some cases even maybe<00:14:55.699> you<00:14:55.939> want<00:14:56.120> to<00:14:56.180> have<00:14:56.360> a<00:14:56.509> bit<00:14:56.930> mask<00:14:57.199> or 00:14:57.639 --> 00:14:57.649 align:start position:0% maybe you want to have a bit mask or 00:14:57.649 --> 00:14:59.019 align:start position:0% maybe you want to have a bit mask or something<00:14:58.129> which<00:14:58.279> actually<00:14:58.699> says<00:14:59.000> something 00:14:59.019 --> 00:14:59.029 align:start position:0% something which actually says something 00:14:59.029 --> 00:15:02.470 align:start position:0% something which actually says something about<00:14:59.569> you<00:15:00.430> right<00:15:01.430> in<00:15:01.639> the<00:15:01.670> bytes<00:15:02.029> of<00:15:02.300> the 00:15:02.470 --> 00:15:02.480 align:start position:0% about you right in the bytes of the 00:15:02.480 --> 00:15:07.139 align:start position:0% about you right in the bytes of the claim<00:15:02.720> where<00:15:03.529> there's<00:15:03.829> more<00:15:04.160> detailed<00:15:06.069> claim 00:15:07.139 --> 00:15:07.149 align:start position:0% claim where there's more detailed claim 00:15:07.149 --> 00:15:11.259 align:start position:0% claim where there's more detailed claim details<00:15:08.149> so<00:15:08.389> to<00:15:08.449> say<00:15:08.720> in<00:15:08.779> it<00:15:09.610> so<00:15:10.610> basically<00:15:11.059> how 00:15:11.259 --> 00:15:11.269 align:start position:0% details so to say in it so basically how 00:15:11.269 --> 00:15:13.119 align:start position:0% details so to say in it so basically how this<00:15:11.449> could<00:15:11.629> look<00:15:11.750> like<00:15:11.809> in<00:15:12.139> detail<00:15:12.529> how<00:15:12.949> it's 00:15:13.119 --> 00:15:13.129 align:start position:0% this could look like in detail how it's 00:15:13.129 --> 00:15:15.460 align:start position:0% this could look like in detail how it's currently<00:15:13.279> in<00:15:14.240> the<00:15:14.449> in<00:15:14.720> the<00:15:14.809> standard<00:15:15.259> and 00:15:15.460 --> 00:15:15.470 align:start position:0% currently in the in the standard and 00:15:15.470 --> 00:15:17.259 align:start position:0% currently in the in the standard and because<00:15:15.860> it's<00:15:16.009> a<00:15:16.069> smart<00:15:16.250> context<00:15:16.699> and<00:15:16.819> up<00:15:16.970> it's 00:15:17.259 --> 00:15:17.269 align:start position:0% because it's a smart context and up it's 00:15:17.269 --> 00:15:20.650 align:start position:0% because it's a smart context and up it's obviously<00:15:17.750> code<00:15:18.670> we<00:15:19.670> have<00:15:19.819> a<00:15:19.850> claim<00:15:20.149> type<00:15:20.420> and 00:15:20.650 --> 00:15:20.660 align:start position:0% obviously code we have a claim type and 00:15:20.660 --> 00:15:22.900 align:start position:0% obviously code we have a claim type and the<00:15:20.720> claim<00:15:20.899> type<00:15:21.079> for<00:15:21.230> example<00:15:21.259> says<00:15:21.910> maybe 00:15:22.900 --> 00:15:22.910 align:start position:0% the claim type for example says maybe 00:15:22.910 --> 00:15:25.569 align:start position:0% the claim type for example says maybe it's<00:15:23.029> a<00:15:23.149> claim<00:15:23.329> type<00:15:23.569> 0<00:15:23.929> 1<00:15:24.230> 2<00:15:24.379> 3<00:15:24.529> 4<00:15:24.740> 5<00:15:24.920> maybe<00:15:25.339> we 00:15:25.569 --> 00:15:25.579 align:start position:0% it's a claim type 0 1 2 3 4 5 maybe we 00:15:25.579 --> 00:15:28.960 align:start position:0% it's a claim type 0 1 2 3 4 5 maybe we say<00:15:25.759> 0<00:15:26.209> is<00:15:26.509> the<00:15:26.809> claim<00:15:27.110> for<00:15:27.790> biometric<00:15:28.790> data 00:15:28.960 --> 00:15:28.970 align:start position:0% say 0 is the claim for biometric data 00:15:28.970 --> 00:15:32.739 align:start position:0% say 0 is the claim for biometric data and<00:15:29.329> 1<00:15:30.259> could<00:15:30.529> be<00:15:30.589> the<00:15:30.829> claim<00:15:31.069> for<00:15:31.519> an<00:15:32.240> address 00:15:32.739 --> 00:15:32.749 align:start position:0% and 1 could be the claim for an address 00:15:32.749 --> 00:15:35.470 align:start position:0% and 1 could be the claim for an address so<00:15:33.199> if<00:15:33.350> I<00:15:33.499> see<00:15:33.769> you<00:15:34.459> on<00:15:34.639> your<00:15:34.790> smart<00:15:35.059> conduct 00:15:35.470 --> 00:15:35.480 align:start position:0% so if I see you on your smart conduct 00:15:35.480 --> 00:15:39.189 align:start position:0% so if I see you on your smart conduct you<00:15:35.990> have<00:15:36.230> a<00:15:36.889> claim<00:15:37.399> type<00:15:37.790> 0<00:15:38.269> and<00:15:38.660> a<00:15:38.809> claim<00:15:39.019> type 00:15:39.189 --> 00:15:39.199 align:start position:0% you have a claim type 0 and a claim type 00:15:39.199 --> 00:15:44.350 align:start position:0% you have a claim type 0 and a claim type 1<00:15:39.470> and<00:15:40.000> both<00:15:41.000> issued<00:15:41.629> by<00:15:42.139> an<00:15:42.439> issue<00:15:42.860> I<00:15:42.920> trust 00:15:44.350 --> 00:15:44.360 align:start position:0% 1 and both issued by an issue I trust 00:15:44.360 --> 00:15:46.449 align:start position:0% 1 and both issued by an issue I trust is<00:15:44.600> the<00:15:44.720> German<00:15:45.079> government<00:15:45.529> and<00:15:45.800> maybe<00:15:46.339> it's 00:15:46.449 --> 00:15:46.459 align:start position:0% is the German government and maybe it's 00:15:46.459 --> 00:15:47.800 align:start position:0% is the German government and maybe it's the<00:15:46.519> Deutsche<00:15:46.790> Post<00:15:46.820> which<00:15:47.390> knows<00:15:47.630> your 00:15:47.800 --> 00:15:47.810 align:start position:0% the Deutsche Post which knows your 00:15:47.810 --> 00:15:49.930 align:start position:0% the Deutsche Post which knows your address<00:15:47.899> and<00:15:48.410> I<00:15:49.070> trust<00:15:49.430> them 00:15:49.930 --> 00:15:49.940 align:start position:0% address and I trust them 00:15:49.940 --> 00:15:51.759 align:start position:0% address and I trust them then<00:15:50.480> the<00:15:50.600> only<00:15:50.720> thing<00:15:50.870> I<00:15:51.079> have<00:15:51.200> to<00:15:51.230> check<00:15:51.320> is 00:15:51.759 --> 00:15:51.769 align:start position:0% then the only thing I have to check is 00:15:51.769 --> 00:15:56.590 align:start position:0% then the only thing I have to check is the<00:15:52.279> signature<00:15:52.880> actually<00:15:53.480> contains<00:15:55.600> contains 00:15:56.590 --> 00:15:56.600 align:start position:0% the signature actually contains contains 00:15:56.600 --> 00:15:58.780 align:start position:0% the signature actually contains contains actually<00:15:57.079> holder<00:15:57.380> address<00:15:57.709> which<00:15:57.860> issue<00:15:58.220> at 00:15:58.780 --> 00:15:58.790 align:start position:0% actually holder address which issue at 00:15:58.790 --> 00:16:01.449 align:start position:0% actually holder address which issue at the<00:15:58.940> address<00:15:59.240> of<00:15:59.390> the<00:15:59.570> of<00:15:59.899> me<00:16:00.110> in<00:16:00.440> this<00:16:00.860> case<00:16:01.070> it 00:16:01.449 --> 00:16:01.459 align:start position:0% the address of the of me in this case it 00:16:01.459 --> 00:16:03.430 align:start position:0% the address of the of me in this case it contains<00:16:02.060> this<00:16:02.269> number<00:16:02.660> here<00:16:02.839> the<00:16:03.019> claim<00:16:03.200> type 00:16:03.430 --> 00:16:03.440 align:start position:0% contains this number here the claim type 00:16:03.440 --> 00:16:06.400 align:start position:0% contains this number here the claim type and<00:16:03.709> it<00:16:03.800> contains<00:16:04.130> this<00:16:04.310> little<00:16:04.640> data<00:16:05.269> and<00:16:05.690> it 00:16:06.400 --> 00:16:06.410 align:start position:0% and it contains this little data and it 00:16:06.410 --> 00:16:08.560 align:start position:0% and it contains this little data and it comes<00:16:06.680> out<00:16:06.829> to<00:16:06.890> an<00:16:07.250> address<00:16:07.700> which<00:16:08.089> is<00:16:08.120> still 00:16:08.560 --> 00:16:08.570 align:start position:0% comes out to an address which is still 00:16:08.570 --> 00:16:11.019 align:start position:0% comes out to an address which is still owned<00:16:08.839> by<00:16:09.320> the<00:16:09.829> Deutsche<00:16:10.190> Post<00:16:10.220> or<00:16:10.670> the<00:16:10.760> German 00:16:11.019 --> 00:16:11.029 align:start position:0% owned by the Deutsche Post or the German 00:16:11.029 --> 00:16:13.060 align:start position:0% owned by the Deutsche Post or the German state<00:16:11.269> didn't<00:16:12.110> know<00:16:12.260> that<00:16:12.649> claim<00:16:12.920> was 00:16:13.060 --> 00:16:13.070 align:start position:0% state didn't know that claim was 00:16:13.070 --> 00:16:15.100 align:start position:0% state didn't know that claim was actually<00:16:13.430> issued<00:16:13.550> by<00:16:13.790> the<00:16:14.000> Deutsche<00:16:14.630> Post<00:16:14.750> or 00:16:15.100 --> 00:16:15.110 align:start position:0% actually issued by the Deutsche Post or 00:16:15.110 --> 00:16:16.810 align:start position:0% actually issued by the Deutsche Post or the<00:16:15.140> German<00:16:15.410> state<00:16:15.680> and<00:16:15.950> as<00:16:16.250> long<00:16:16.399> as<00:16:16.459> any 00:16:16.810 --> 00:16:16.820 align:start position:0% the German state and as long as any 00:16:16.820 --> 00:16:21.910 align:start position:0% the German state and as long as any external<00:16:17.329> party<00:16:17.810> trust<00:16:18.769> that<00:16:19.149> issue<00:16:20.149> oh<00:16:20.920> he 00:16:21.910 --> 00:16:21.920 align:start position:0% external party trust that issue oh he 00:16:21.920 --> 00:16:23.590 align:start position:0% external party trust that issue oh he can<00:16:22.070> be<00:16:22.100> completely<00:16:22.370> confident<00:16:23.149> that<00:16:23.329> you 00:16:23.590 --> 00:16:23.600 align:start position:0% can be completely confident that you 00:16:23.600 --> 00:16:25.720 align:start position:0% can be completely confident that you have<00:16:23.810> an<00:16:23.959> address<00:16:24.320> and<00:16:24.560> that<00:16:25.160> you<00:16:25.310> are<00:16:25.430> human 00:16:25.720 --> 00:16:25.730 align:start position:0% have an address and that you are human 00:16:25.730 --> 00:16:28.600 align:start position:0% have an address and that you are human or<00:16:26.200> maybe<00:16:27.200> some<00:16:27.470> kind<00:16:27.589> of<00:16:27.680> flesh<00:16:27.980> thing<00:16:28.250> right 00:16:28.600 --> 00:16:28.610 align:start position:0% or maybe some kind of flesh thing right 00:16:28.610 --> 00:16:32.110 align:start position:0% or maybe some kind of flesh thing right if<00:16:29.029> you<00:16:29.240> have<00:16:29.329> primary<00:16:29.510> data<00:16:30.160> and<00:16:31.160> that<00:16:31.910> might 00:16:32.110 --> 00:16:32.120 align:start position:0% if you have primary data and that might 00:16:32.120 --> 00:16:34.060 align:start position:0% if you have primary data and that might be<00:16:32.300> fully<00:16:32.630> enough<00:16:32.959> to<00:16:33.200> allow<00:16:33.440> you<00:16:33.500> access<00:16:33.829> to 00:16:34.060 --> 00:16:34.070 align:start position:0% be fully enough to allow you access to 00:16:34.070 --> 00:16:36.910 align:start position:0% be fully enough to allow you access to something<00:16:34.459> to<00:16:34.760> issue<00:16:34.970> credit<00:16:35.390> or<00:16:35.839> to<00:16:36.050> issue<00:16:36.290> an 00:16:36.910 --> 00:16:36.920 align:start position:0% something to issue credit or to issue an 00:16:36.920 --> 00:16:38.920 align:start position:0% something to issue credit or to issue an account<00:16:37.370> or<00:16:37.670> whatever<00:16:37.970> you<00:16:38.329> want<00:16:38.510> to<00:16:38.600> do<00:16:38.720> in<00:16:38.839> an 00:16:38.920 --> 00:16:38.930 align:start position:0% account or whatever you want to do in an 00:16:38.930 --> 00:16:42.930 align:start position:0% account or whatever you want to do in an automated<00:16:39.230> process<00:16:40.120> so<00:16:41.120> it's<00:16:41.390> all<00:16:41.600> about 00:16:42.930 --> 00:16:42.940 align:start position:0% automated process so it's all about 00:16:42.940 --> 00:16:46.269 align:start position:0% automated process so it's all about basically<00:16:43.940> trusting<00:16:44.690> the<00:16:45.230> claim<00:16:45.470> issuers<00:16:46.010> and 00:16:46.269 --> 00:16:46.279 align:start position:0% basically trusting the claim issuers and 00:16:46.279 --> 00:16:48.340 align:start position:0% basically trusting the claim issuers and it's<00:16:46.880> obviously<00:16:47.180> that<00:16:47.300> depends<00:16:47.660> on<00:16:47.839> what<00:16:48.320> kind 00:16:48.340 --> 00:16:48.350 align:start position:0% it's obviously that depends on what kind 00:16:48.350 --> 00:16:50.380 align:start position:0% it's obviously that depends on what kind of<00:16:48.680> like<00:16:48.829> issues<00:16:48.980> this<00:16:49.370> could<00:16:49.519> be<00:16:49.670> and<00:16:49.880> in<00:16:50.269> the 00:16:50.380 --> 00:16:50.390 align:start position:0% of like issues this could be and in the 00:16:50.390 --> 00:16:51.850 align:start position:0% of like issues this could be and in the beginning<00:16:50.510> this<00:16:50.779> probably<00:16:51.290> will<00:16:51.500> be<00:16:51.649> big 00:16:51.850 --> 00:16:51.860 align:start position:0% beginning this probably will be big 00:16:51.860 --> 00:16:53.860 align:start position:0% beginning this probably will be big institutions<00:16:52.519> but<00:16:53.209> in<00:16:53.329> the<00:16:53.420> future<00:16:53.750> this 00:16:53.860 --> 00:16:53.870 align:start position:0% institutions but in the future this 00:16:53.870 --> 00:16:55.780 align:start position:0% institutions but in the future this could<00:16:54.050> also<00:16:54.290> be<00:16:54.440> peer-to-peer<00:16:54.800> networks<00:16:55.399> or 00:16:55.780 --> 00:16:55.790 align:start position:0% could also be peer-to-peer networks or 00:16:55.790 --> 00:16:58.329 align:start position:0% could also be peer-to-peer networks or other<00:16:56.449> kind<00:16:57.019> of<00:16:57.110> reputation<00:16:57.350> systems<00:16:58.100> or 00:16:58.329 --> 00:16:58.339 align:start position:0% other kind of reputation systems or 00:16:58.339 --> 00:17:01.660 align:start position:0% other kind of reputation systems or whatever<00:16:58.940> the<00:16:59.149> claim<00:16:59.890> can<00:17:00.890> be<00:17:01.070> it's 00:17:01.660 --> 00:17:01.670 align:start position:0% whatever the claim can be it's 00:17:01.670 --> 00:17:05.530 align:start position:0% whatever the claim can be it's completely<00:17:02.300> open<00:17:02.449> right<00:17:03.939> so<00:17:04.939> how<00:17:05.179> would<00:17:05.240> the 00:17:05.530 --> 00:17:05.540 align:start position:0% completely open right so how would the 00:17:05.540 --> 00:17:06.880 align:start position:0% completely open right so how would the process<00:17:05.809> look<00:17:06.260> like<00:17:06.290> and<00:17:06.589> I<00:17:06.620> have<00:17:06.679> three 00:17:06.880 --> 00:17:06.890 align:start position:0% process look like and I have three 00:17:06.890 --> 00:17:09.370 align:start position:0% process look like and I have three minutes<00:17:07.130> so<00:17:07.189> I<00:17:07.220> have<00:17:07.250> to<00:17:07.400> go<00:17:07.520> faster<00:17:08.380> for 00:17:09.370 --> 00:17:09.380 align:start position:0% minutes so I have to go faster for 00:17:09.380 --> 00:17:12.159 align:start position:0% minutes so I have to go faster for example<00:17:09.679> like<00:17:09.829> a<00:17:10.220> off<00:17:10.790> chain<00:17:11.150> example<00:17:11.990> could 00:17:12.159 --> 00:17:12.169 align:start position:0% example like a off chain example could 00:17:12.169 --> 00:17:14.370 align:start position:0% example like a off chain example could be<00:17:12.319> here<00:17:12.650> I'm<00:17:12.829> walking<00:17:13.100> around<00:17:13.459> with<00:17:13.669> my 00:17:14.370 --> 00:17:14.380 align:start position:0% be here I'm walking around with my 00:17:14.380 --> 00:17:17.289 align:start position:0% be here I'm walking around with my smartphone<00:17:15.380> simple<00:17:16.189> use<00:17:16.339> case<00:17:16.459> I<00:17:16.610> want<00:17:17.059> to<00:17:17.150> get 00:17:17.289 --> 00:17:17.299 align:start position:0% smartphone simple use case I want to get 00:17:17.299 --> 00:17:20.590 align:start position:0% smartphone simple use case I want to get into<00:17:17.569> a<00:17:17.750> disco<00:17:18.500> and<00:17:18.880> the<00:17:19.880> guy<00:17:20.030> has<00:17:20.240> to<00:17:20.390> prove 00:17:20.590 --> 00:17:20.600 align:start position:0% into a disco and the guy has to prove 00:17:20.600 --> 00:17:23.500 align:start position:0% into a disco and the guy has to prove that<00:17:20.660> I'm<00:17:20.990> over<00:17:21.350> 18<00:17:21.380> or<00:17:21.829> whatever<00:17:21.919> so<00:17:22.760> he<00:17:23.360> would 00:17:23.500 --> 00:17:23.510 align:start position:0% that I'm over 18 or whatever so he would 00:17:23.510 --> 00:17:25.270 align:start position:0% that I'm over 18 or whatever so he would basically<00:17:23.689> send<00:17:24.230> me<00:17:24.350> from<00:17:24.589> his<00:17:24.829> phone<00:17:25.069> a 00:17:25.270 --> 00:17:25.280 align:start position:0% basically send me from his phone a 00:17:25.280 --> 00:17:28.179 align:start position:0% basically send me from his phone a random<00:17:25.669> string<00:17:26.000> and<00:17:26.329> this<00:17:27.230> random<00:17:27.410> string<00:17:27.679> is 00:17:28.179 --> 00:17:28.189 align:start position:0% random string and this random string is 00:17:28.189 --> 00:17:29.890 align:start position:0% random string and this random string is something<00:17:28.580> I<00:17:28.700> can<00:17:28.910> sign<00:17:29.179> and<00:17:29.480> I<00:17:29.540> would<00:17:29.720> sign 00:17:29.890 --> 00:17:29.900 align:start position:0% something I can sign and I would sign 00:17:29.900 --> 00:17:31.930 align:start position:0% something I can sign and I would sign this<00:17:30.020> random<00:17:30.350> string<00:17:30.470> plus<00:17:31.070> my<00:17:31.429> identity 00:17:31.930 --> 00:17:31.940 align:start position:0% this random string plus my identity 00:17:31.940 --> 00:17:34.510 align:start position:0% this random string plus my identity address<00:17:32.299> and<00:17:32.540> send<00:17:32.990> it<00:17:33.110> back<00:17:33.140> to<00:17:33.320> him<00:17:33.650> he<00:17:34.340> would 00:17:34.510 --> 00:17:34.520 align:start position:0% address and send it back to him he would 00:17:34.520 --> 00:17:37.390 align:start position:0% address and send it back to him he would be<00:17:34.549> able<00:17:34.970> to<00:17:35.120> verify<00:17:35.710> ok<00:17:36.710> this<00:17:36.860> was<00:17:37.040> signed<00:17:37.250> by 00:17:37.390 --> 00:17:37.400 align:start position:0% be able to verify ok this was signed by 00:17:37.400 --> 00:17:40.120 align:start position:0% be able to verify ok this was signed by this<00:17:37.460> key<00:17:37.850> and<00:17:38.230> he<00:17:39.230> signed<00:17:39.500> my<00:17:39.650> random<00:17:39.860> string 00:17:40.120 --> 00:17:40.130 align:start position:0% this key and he signed my random string 00:17:40.130 --> 00:17:42.039 align:start position:0% this key and he signed my random string so<00:17:40.280> obviously<00:17:40.610> he<00:17:40.790> could<00:17:41.000> he<00:17:41.419> had<00:17:41.570> to<00:17:41.720> private 00:17:42.039 --> 00:17:42.049 align:start position:0% so obviously he could he had to private 00:17:42.049 --> 00:17:44.320 align:start position:0% so obviously he could he had to private key<00:17:42.230> he<00:17:42.380> could<00:17:42.559> sign<00:17:42.770> it<00:17:42.830> properly<00:17:43.220> and<00:17:43.730> yes 00:17:44.320 --> 00:17:44.330 align:start position:0% key he could sign it properly and yes 00:17:44.330 --> 00:17:47.230 align:start position:0% key he could sign it properly and yes the<00:17:44.720> address<00:17:45.230> is<00:17:45.679> identity<00:17:46.070> so<00:17:46.400> he<00:17:46.520> goes<00:17:46.730> check 00:17:47.230 --> 00:17:47.240 align:start position:0% the address is identity so he goes check 00:17:47.240 --> 00:17:49.570 align:start position:0% the address is identity so he goes check on<00:17:47.390> the<00:17:47.480> blockchain<00:17:47.710> gets<00:17:48.710> the<00:17:48.980> claim<00:17:49.280> he 00:17:49.570 --> 00:17:49.580 align:start position:0% on the blockchain gets the claim he 00:17:49.580 --> 00:17:52.480 align:start position:0% on the blockchain gets the claim he needs<00:17:50.150> or<00:17:50.630> whatever<00:17:51.410> claim<00:17:51.799> that<00:17:51.980> is<00:17:52.130> right 00:17:52.480 --> 00:17:52.490 align:start position:0% needs or whatever claim that is right 00:17:52.490 --> 00:17:55.720 align:start position:0% needs or whatever claim that is right maybe<00:17:52.910> it's<00:17:53.150> the<00:17:53.360> age<00:17:53.600> whatever<00:17:54.280> or<00:17:55.280> an<00:17:55.520> age 00:17:55.720 --> 00:17:55.730 align:start position:0% maybe it's the age whatever or an age 00:17:55.730 --> 00:17:58.030 align:start position:0% maybe it's the age whatever or an age certificate<00:17:56.510> that's<00:17:56.720> over<00:17:57.080> 18<00:17:57.470> says 00:17:58.030 --> 00:17:58.040 align:start position:0% certificate that's over 18 says 00:17:58.040 --> 00:18:03.280 align:start position:0% certificate that's over 18 says that's<00:17:58.610> over<00:17:58.790> Tina<00:17:59.150> zone<00:18:01.930> he<00:18:02.930> basically 00:18:03.280 --> 00:18:03.290 align:start position:0% that's over Tina zone he basically 00:18:03.290 --> 00:18:05.650 align:start position:0% that's over Tina zone he basically checks<00:18:03.590> the<00:18:03.740> claim<00:18:03.980> and<00:18:04.280> this<00:18:05.150> means<00:18:05.390> he 00:18:05.650 --> 00:18:05.660 align:start position:0% checks the claim and this means he 00:18:05.660 --> 00:18:09.100 align:start position:0% checks the claim and this means he checks<00:18:05.960> the<00:18:06.110> signature<00:18:06.590> and<00:18:07.600> goes<00:18:08.600> and<00:18:08.900> checks 00:18:09.100 --> 00:18:09.110 align:start position:0% checks the signature and goes and checks 00:18:09.110 --> 00:18:10.480 align:start position:0% checks the signature and goes and checks on<00:18:09.320> the<00:18:09.410> SmartConnect<00:18:09.860> of<00:18:10.010> the<00:18:10.130> issue<00:18:10.250> that 00:18:10.480 --> 00:18:10.490 align:start position:0% on the SmartConnect of the issue that 00:18:10.490 --> 00:18:12.310 align:start position:0% on the SmartConnect of the issue that actually<00:18:10.730> the<00:18:11.030> key<00:18:11.300> he's<00:18:11.570> designed<00:18:12.020> what<00:18:12.200> was 00:18:12.310 --> 00:18:12.320 align:start position:0% actually the key he's designed what was 00:18:12.320 --> 00:18:14.200 align:start position:0% actually the key he's designed what was still<00:18:12.560> there<00:18:12.860> so<00:18:13.190> this<00:18:13.460> would<00:18:13.700> be<00:18:13.790> the<00:18:13.910> power 00:18:14.200 --> 00:18:14.210 align:start position:0% still there so this would be the power 00:18:14.210 --> 00:18:16.750 align:start position:0% still there so this would be the power for<00:18:14.630> the<00:18:14.690> issue<00:18:14.810> to<00:18:15.080> remove<00:18:15.680> the<00:18:15.830> claim<00:18:16.100> even 00:18:16.750 --> 00:18:16.760 align:start position:0% for the issue to remove the claim even 00:18:16.760 --> 00:18:19.510 align:start position:0% for the issue to remove the claim even though<00:18:16.940> that<00:18:17.300> I<00:18:17.330> might<00:18:17.930> not<00:18:18.080> agree<00:18:18.290> to<00:18:18.400> so<00:18:19.400> as 00:18:19.510 --> 00:18:19.520 align:start position:0% though that I might not agree to so as 00:18:19.520 --> 00:18:22.140 align:start position:0% though that I might not agree to so as long<00:18:19.700> as<00:18:19.880> the<00:18:20.000> signature<00:18:20.420> is<00:18:20.720> correct<00:18:21.140> and 00:18:22.140 --> 00:18:22.150 align:start position:0% long as the signature is correct and 00:18:22.150 --> 00:18:25.900 align:start position:0% long as the signature is correct and returns<00:18:23.150> a<00:18:23.480> address<00:18:24.170> still<00:18:24.920> owned<00:18:25.250> by<00:18:25.730> the 00:18:25.900 --> 00:18:25.910 align:start position:0% returns a address still owned by the 00:18:25.910 --> 00:18:31.390 align:start position:0% returns a address still owned by the issuer<00:18:26.410> this<00:18:27.410> person<00:18:28.180> here<00:18:29.650> the<00:18:30.650> bouncer<00:18:31.130> can 00:18:31.390 --> 00:18:31.400 align:start position:0% issuer this person here the bouncer can 00:18:31.400 --> 00:18:34.270 align:start position:0% issuer this person here the bouncer can be<00:18:32.020> confident<00:18:33.020> that<00:18:33.140> this<00:18:33.350> person<00:18:33.890> is 00:18:34.270 --> 00:18:34.280 align:start position:0% be confident that this person is 00:18:34.280 --> 00:18:37.060 align:start position:0% be confident that this person is whatever<00:18:34.910> the<00:18:35.180> claim<00:18:35.390> sensitive<00:18:35.960> does<00:18:36.260> and<00:18:36.950> it 00:18:37.060 --> 00:18:37.070 align:start position:0% whatever the claim sensitive does and it 00:18:37.070 --> 00:18:38.860 align:start position:0% whatever the claim sensitive does and it might<00:18:37.190> be<00:18:37.220> a<00:18:37.370> very<00:18:37.580> abstract<00:18:37.940> information 00:18:38.860 --> 00:18:38.870 align:start position:0% might be a very abstract information 00:18:38.870 --> 00:18:42.010 align:start position:0% might be a very abstract information maybe<00:18:39.590> just<00:18:39.980> over<00:18:40.310> 18<00:18:40.610> it<00:18:41.180> doesn't<00:18:41.450> even<00:18:41.510> mean 00:18:42.010 --> 00:18:42.020 align:start position:0% maybe just over 18 it doesn't even mean 00:18:42.020 --> 00:18:45.460 align:start position:0% maybe just over 18 it doesn't even mean he's<00:18:42.230> 20<00:18:42.680> 30<00:18:43.100> or<00:18:43.310> 50<00:18:43.610> or<00:18:43.640> 110<00:18:44.300> it<00:18:45.110> just<00:18:45.320> says 00:18:45.460 --> 00:18:45.470 align:start position:0% he's 20 30 or 50 or 110 it just says 00:18:45.470 --> 00:18:50.440 align:start position:0% he's 20 30 or 50 or 110 it just says it's<00:18:45.650> over<00:18:45.800> 18<00:18:46.280> or<00:18:47.170> he's<00:18:48.170> allowed<00:18:48.470> to<00:18:48.620> just<00:18:49.450> go 00:18:50.440 --> 00:18:50.450 align:start position:0% it's over 18 or he's allowed to just go 00:18:50.450 --> 00:18:53.440 align:start position:0% it's over 18 or he's allowed to just go in<00:18:50.630> for<00:18:51.080> whatever<00:18:51.230> reason<00:18:51.650> right<00:18:52.390> so<00:18:53.390> you 00:18:53.440 --> 00:18:53.450 align:start position:0% in for whatever reason right so you 00:18:53.450 --> 00:18:55.270 align:start position:0% in for whatever reason right so you could<00:18:54.080> do<00:18:54.200> this<00:18:54.320> in<00:18:54.560> the<00:18:54.590> off<00:18:54.800> ten<00:18:55.040> world 00:18:55.270 --> 00:18:55.280 align:start position:0% could do this in the off ten world 00:18:55.280 --> 00:18:56.950 align:start position:0% could do this in the off ten world basically<00:18:55.610> by<00:18:55.820> going<00:18:56.120> around<00:18:56.240> in<00:18:56.600> signing 00:18:56.950 --> 00:18:56.960 align:start position:0% basically by going around in signing 00:18:56.960 --> 00:18:58.720 align:start position:0% basically by going around in signing messages<00:18:57.440> all<00:18:57.590> the<00:18:57.710> time<00:18:57.950> and<00:18:58.220> then<00:18:58.520> people 00:18:58.720 --> 00:18:58.730 align:start position:0% messages all the time and then people 00:18:58.730 --> 00:19:00.490 align:start position:0% messages all the time and then people can<00:18:58.910> always<00:18:59.120> go<00:18:59.390> to<00:18:59.420> your<00:18:59.690> block<00:18:59.900> 10<00:19:00.050> identity 00:19:00.490 --> 00:19:00.500 align:start position:0% can always go to your block 10 identity 00:19:00.500 --> 00:19:03.580 align:start position:0% can always go to your block 10 identity and<00:19:00.680> check<00:19:00.950> hey<00:19:01.220> who<00:19:02.090> is<00:19:02.240> that<00:19:02.270> person<00:19:02.930> does<00:19:03.440> he 00:19:03.580 --> 00:19:03.590 align:start position:0% and check hey who is that person does he 00:19:03.590 --> 00:19:05.380 align:start position:0% and check hey who is that person does he have<00:19:03.770> to<00:19:03.920> write<00:19:04.100> requirements<00:19:04.550> and<00:19:05.150> you<00:19:05.240> can 00:19:05.380 --> 00:19:05.390 align:start position:0% have to write requirements and you can 00:19:05.390 --> 00:19:08.680 align:start position:0% have to write requirements and you can verify<00:19:05.630> these<00:19:06.140> kind<00:19:06.380> of<00:19:06.650> requirements<00:19:07.370> if<00:19:08.300> I 00:19:08.680 --> 00:19:08.690 align:start position:0% verify these kind of requirements if I 00:19:08.690 --> 00:19:11.290 align:start position:0% verify these kind of requirements if I do<00:19:08.750> this<00:19:08.930> on<00:19:09.020> the<00:19:09.140> blockchain<00:19:09.350> I<00:19:10.300> basically 00:19:11.290 --> 00:19:11.300 align:start position:0% do this on the blockchain I basically 00:19:11.300 --> 00:19:13.480 align:start position:0% do this on the blockchain I basically can<00:19:11.480> act<00:19:11.690> through<00:19:11.780> my<00:19:12.110> identity<00:19:12.680> I<00:19:12.710> can<00:19:13.010> call<00:19:13.280> a 00:19:13.480 --> 00:19:13.490 align:start position:0% can act through my identity I can call a 00:19:13.490 --> 00:19:15.700 align:start position:0% can act through my identity I can call a function<00:19:13.790> on<00:19:14.270> another<00:19:14.570> smart<00:19:14.870> contract<00:19:15.320> and 00:19:15.700 --> 00:19:15.710 align:start position:0% function on another smart contract and 00:19:15.710 --> 00:19:18.790 align:start position:0% function on another smart contract and this<00:19:16.580> could<00:19:16.790> be<00:19:16.820> their<00:19:17.030> super<00:19:17.330> important<00:19:17.840> who 00:19:18.790 --> 00:19:18.800 align:start position:0% this could be their super important who 00:19:18.800 --> 00:19:21.460 align:start position:0% this could be their super important who a<00:19:19.430> smart<00:19:19.910> contract<00:19:20.060> and<00:19:20.570> I<00:19:20.930> really<00:19:21.200> want<00:19:21.380> to 00:19:21.460 --> 00:19:21.470 align:start position:0% a smart contract and I really want to 00:19:21.470 --> 00:19:22.840 align:start position:0% a smart contract and I really want to use<00:19:21.620> that<00:19:21.650> function<00:19:22.280> but<00:19:22.430> this<00:19:22.610> function 00:19:22.840 --> 00:19:22.850 align:start position:0% use that function but this function 00:19:22.850 --> 00:19:25.510 align:start position:0% use that function but this function requires<00:19:23.320> to<00:19:24.320> check<00:19:24.620> some<00:19:24.830> identity<00:19:25.280> stuff 00:19:25.510 --> 00:19:25.520 align:start position:0% requires to check some identity stuff 00:19:25.520 --> 00:19:28.900 align:start position:0% requires to check some identity stuff otherwise<00:19:26.240> it<00:19:26.390> can't<00:19:26.630> be<00:19:26.750> used<00:19:27.520> so<00:19:28.520> the<00:19:28.700> smart 00:19:28.900 --> 00:19:28.910 align:start position:0% otherwise it can't be used so the smart 00:19:28.910 --> 00:19:30.400 align:start position:0% otherwise it can't be used so the smart content<00:19:29.150> will<00:19:29.360> automatically<00:19:29.900> you<00:19:30.050> realize 00:19:30.400 --> 00:19:30.410 align:start position:0% content will automatically you realize 00:19:30.410 --> 00:19:32.830 align:start position:0% content will automatically you realize okay<00:19:30.590> an<00:19:30.980> identity<00:19:31.520> is<00:19:31.700> calling<00:19:32.090> me<00:19:32.210> so<00:19:32.480> I<00:19:32.510> get 00:19:32.830 --> 00:19:32.840 align:start position:0% okay an identity is calling me so I get 00:19:32.840 --> 00:19:34.270 align:start position:0% okay an identity is calling me so I get the<00:19:32.990> claim<00:19:33.200> from<00:19:33.410> this<00:19:33.590> identity<00:19:33.800> smart 00:19:34.270 --> 00:19:34.280 align:start position:0% the claim from this identity smart 00:19:34.280 --> 00:19:37.150 align:start position:0% the claim from this identity smart conduct<00:19:34.610> back<00:19:34.820> I<00:19:35.150> will<00:19:36.140> verify<00:19:36.380> the<00:19:36.680> signature 00:19:37.150 --> 00:19:37.160 align:start position:0% conduct back I will verify the signature 00:19:37.160 --> 00:19:40.450 align:start position:0% conduct back I will verify the signature right<00:19:37.370> in<00:19:37.520> the<00:19:37.640> smart<00:19:37.910> contract<00:19:39.100> go<00:19:40.100> to<00:19:40.160> the 00:19:40.450 --> 00:19:40.460 align:start position:0% right in the smart contract go to the 00:19:40.460 --> 00:19:42.820 align:start position:0% right in the smart contract go to the issues<00:19:40.790> smart<00:19:41.420> corner<00:19:41.630> and<00:19:41.930> check<00:19:42.170> that<00:19:42.470> key 00:19:42.820 --> 00:19:42.830 align:start position:0% issues smart corner and check that key 00:19:42.830 --> 00:19:44.470 align:start position:0% issues smart corner and check that key is<00:19:42.890> still<00:19:43.190> there<00:19:43.400> I<00:19:43.670> know<00:19:43.820> the<00:19:44.090> key<00:19:44.270> still 00:19:44.470 --> 00:19:44.480 align:start position:0% is still there I know the key still 00:19:44.480 --> 00:19:46.600 align:start position:0% is still there I know the key still there<00:19:44.660> so<00:19:44.870> it's<00:19:45.020> a<00:19:45.110> valid<00:19:45.440> claim<00:19:46.100> still 00:19:46.600 --> 00:19:46.610 align:start position:0% there so it's a valid claim still 00:19:46.610 --> 00:19:47.440 align:start position:0% there so it's a valid claim still attached<00:19:46.940> here 00:19:47.440 --> 00:19:47.450 align:start position:0% attached here 00:19:47.450 --> 00:19:50.260 align:start position:0% attached here I<00:19:47.480> trust<00:19:48.380> the<00:19:48.560> issuer<00:19:48.890> I<00:19:49.220> don't<00:19:49.850> even<00:19:49.940> need<00:19:50.120> to 00:19:50.260 --> 00:19:50.270 align:start position:0% I trust the issuer I don't even need to 00:19:50.270 --> 00:19:52.120 align:start position:0% I trust the issuer I don't even need to know<00:19:50.390> the<00:19:50.570> actually<00:19:50.870> data<00:19:51.020> most<00:19:51.770> of<00:19:51.890> the<00:19:51.980> time 00:19:52.120 --> 00:19:52.130 align:start position:0% know the actually data most of the time 00:19:52.130 --> 00:19:53.740 align:start position:0% know the actually data most of the time we<00:19:52.220> don't<00:19:52.370> care<00:19:52.610> about<00:19:52.940> the<00:19:53.240> extra<00:19:53.480> data<00:19:53.630> I 00:19:53.740 --> 00:19:53.750 align:start position:0% we don't care about the extra data I 00:19:53.750 --> 00:19:55.990 align:start position:0% we don't care about the extra data I don't<00:19:53.990> know<00:19:54.140> care<00:19:54.770> how<00:19:54.980> what<00:19:55.250> your<00:19:55.400> name<00:19:55.580> is<00:19:55.610> or 00:19:55.990 --> 00:19:56.000 align:start position:0% don't know care how what your name is or 00:19:56.000 --> 00:19:58.450 align:start position:0% don't know care how what your name is or how<00:19:56.150> you<00:19:56.210> look<00:19:56.450> like<00:19:56.690> until<00:19:57.200> as<00:19:58.040> long<00:19:58.250> as<00:19:58.430> I 00:19:58.450 --> 00:19:58.460 align:start position:0% how you look like until as long as I 00:19:58.460 --> 00:20:01.210 align:start position:0% how you look like until as long as I know<00:19:58.640> that<00:19:59.000> you<00:19:59.210> are<00:19:59.510> a<00:19:59.540> person<00:19:59.960> and<00:20:00.410> that<00:20:01.190> you 00:20:01.210 --> 00:20:01.220 align:start position:0% know that you are a person and that you 00:20:01.220 --> 00:20:03.100 align:start position:0% know that you are a person and that you have<00:20:01.460> maybe<00:20:01.730> a<00:20:01.880> residence<00:20:02.420> somewhere<00:20:02.840> where 00:20:03.100 --> 00:20:03.110 align:start position:0% have maybe a residence somewhere where 00:20:03.110 --> 00:20:05.380 align:start position:0% have maybe a residence somewhere where it's<00:20:03.260> where<00:20:04.160> maybe<00:20:04.520> it's<00:20:04.700> the<00:20:04.820> country<00:20:05.240> or 00:20:05.380 --> 00:20:05.390 align:start position:0% it's where maybe it's the country or 00:20:05.390 --> 00:20:07.000 align:start position:0% it's where maybe it's the country or whatever<00:20:05.540> or<00:20:05.960> maybe<00:20:06.320> it's<00:20:06.470> just<00:20:06.530> enough<00:20:06.860> to 00:20:07.000 --> 00:20:07.010 align:start position:0% whatever or maybe it's just enough to 00:20:07.010 --> 00:20:09.720 align:start position:0% whatever or maybe it's just enough to know<00:20:07.160> that<00:20:07.340> you<00:20:07.430> have<00:20:07.640> been<00:20:07.670> residents<00:20:08.300> at<00:20:08.450> all 00:20:09.720 --> 00:20:09.730 align:start position:0% know that you have been residents at all 00:20:09.730 --> 00:20:11.289 align:start position:0% know that you have been residents at all and<00:20:10.730> that's<00:20:10.970> it 00:20:11.289 --> 00:20:11.299 align:start position:0% and that's it 00:20:11.299 --> 00:20:13.869 align:start position:0% and that's it I<00:20:11.360> can<00:20:11.779> continue<00:20:12.559> with<00:20:12.710> the<00:20:12.830> execution<00:20:13.460> of<00:20:13.639> the 00:20:13.869 --> 00:20:13.879 align:start position:0% I can continue with the execution of the 00:20:13.879 --> 00:20:16.779 align:start position:0% I can continue with the execution of the super<00:20:14.600> cool<00:20:14.749> function<00:20:15.200> in<00:20:15.679> this<00:20:15.799> case<00:20:15.919> so<00:20:16.700> you 00:20:16.779 --> 00:20:16.789 align:start position:0% super cool function in this case so you 00:20:16.789 --> 00:20:18.639 align:start position:0% super cool function in this case so you can't<00:20:17.119> do<00:20:17.269> this<00:20:17.419> you<00:20:17.659> can<00:20:17.809> use<00:20:17.960> this<00:20:18.110> on<00:20:18.350> chain 00:20:18.639 --> 00:20:18.649 align:start position:0% can't do this you can use this on chain 00:20:18.649 --> 00:20:20.919 align:start position:0% can't do this you can use this on chain and<00:20:18.860> you<00:20:18.980> can<00:20:19.009> use<00:20:19.279> it<00:20:19.429> off<00:20:19.580> chain<00:20:19.909> and<00:20:20.360> my<00:20:20.720> time 00:20:20.919 --> 00:20:20.929 align:start position:0% and you can use it off chain and my time 00:20:20.929 --> 00:20:24.940 align:start position:0% and you can use it off chain and my time is<00:20:21.049> off<00:20:21.200> and<00:20:22.869> you<00:20:23.869> can<00:20:24.169> basically<00:20:24.350> do<00:20:24.799> this 00:20:24.940 --> 00:20:24.950 align:start position:0% is off and you can basically do this 00:20:24.950 --> 00:20:27.729 align:start position:0% is off and you can basically do this really<00:20:25.100> simple<00:20:25.489> steps<00:20:25.789> of<00:20:26.559> actually<00:20:27.559> two 00:20:27.729 --> 00:20:27.739 align:start position:0% really simple steps of actually two 00:20:27.739 --> 00:20:29.680 align:start position:0% really simple steps of actually two three<00:20:28.070> steps<00:20:28.460> to<00:20:28.730> completely<00:20:29.059> verify<00:20:29.629> the 00:20:29.680 --> 00:20:29.690 align:start position:0% three steps to completely verify the 00:20:29.690 --> 00:20:31.989 align:start position:0% three steps to completely verify the claim<00:20:30.049> and<00:20:30.320> it's<00:20:30.830> attached<00:20:31.100> to<00:20:31.369> my<00:20:31.489> identity 00:20:31.989 --> 00:20:31.999 align:start position:0% claim and it's attached to my identity 00:20:31.999 --> 00:20:35.649 align:start position:0% claim and it's attached to my identity so<00:20:32.119> I'm<00:20:32.269> full<00:20:32.570> and<00:20:32.600> control<00:20:33.049> and<00:20:34.389> this<00:20:35.389> allows 00:20:35.649 --> 00:20:35.659 align:start position:0% so I'm full and control and this allows 00:20:35.659 --> 00:20:36.999 align:start position:0% so I'm full and control and this allows basically<00:20:36.139> all<00:20:36.259> of<00:20:36.289> these<00:20:36.559> interesting 00:20:36.999 --> 00:20:37.009 align:start position:0% basically all of these interesting 00:20:37.009 --> 00:20:39.489 align:start position:0% basically all of these interesting things<00:20:37.309> and<00:20:37.639> it<00:20:37.850> combines<00:20:38.149> these<00:20:38.600> these<00:20:38.929> two 00:20:39.489 --> 00:20:39.499 align:start position:0% things and it combines these these two 00:20:39.499 --> 00:20:42.729 align:start position:0% things and it combines these these two little<00:20:39.980> rather<00:20:40.580> simple<00:20:41.029> standards<00:20:41.509> and<00:20:41.869> it 00:20:42.729 --> 00:20:42.739 align:start position:0% little rather simple standards and it 00:20:42.739 --> 00:20:44.470 align:start position:0% little rather simple standards and it gives<00:20:42.919> enough<00:20:43.220> flexibility<00:20:43.820> that<00:20:44.059> all<00:20:44.210> kind 00:20:44.470 --> 00:20:44.480 align:start position:0% gives enough flexibility that all kind 00:20:44.480 --> 00:20:46.029 align:start position:0% gives enough flexibility that all kind of<00:20:44.539> experimentation<00:20:45.080> can<00:20:45.350> happen<00:20:45.679> so<00:20:45.830> we<00:20:45.919> can 00:20:46.029 --> 00:20:46.039 align:start position:0% of experimentation can happen so we can 00:20:46.039 --> 00:20:47.470 align:start position:0% of experimentation can happen so we can figure<00:20:46.220> out<00:20:46.369> what<00:20:46.609> kind<00:20:46.789> of<00:20:46.820> claims<00:20:47.059> we<00:20:47.210> trust 00:20:47.470 --> 00:20:47.480 align:start position:0% figure out what kind of claims we trust 00:20:47.480 --> 00:20:49.119 align:start position:0% figure out what kind of claims we trust how<00:20:47.779> these<00:20:47.960> claims<00:20:48.200> can<00:20:48.379> look<00:20:48.529> like<00:20:48.649> in<00:20:48.710> detail 00:20:49.119 --> 00:20:49.129 align:start position:0% how these claims can look like in detail 00:20:49.129 --> 00:20:51.369 align:start position:0% how these claims can look like in detail where<00:20:49.730> they<00:20:49.820> are<00:20:49.940> stored<00:20:50.269> how<00:20:50.869> could<00:20:51.109> you<00:20:51.230> even 00:20:51.369 --> 00:20:51.379 align:start position:0% where they are stored how could you even 00:20:51.379 --> 00:20:53.440 align:start position:0% where they are stored how could you even verify<00:20:51.739> the<00:20:52.039> claims<00:20:52.429> actually<00:20:52.730> Conda<00:20:53.239> maybe 00:20:53.440 --> 00:20:53.450 align:start position:0% verify the claims actually Conda maybe 00:20:53.450 --> 00:20:56.710 align:start position:0% verify the claims actually Conda maybe in<00:20:53.629> SEK<00:20:54.080> snark<00:20:54.739> proof<00:20:55.700> outside<00:20:56.480> of<00:20:56.600> the 00:20:56.710 --> 00:20:56.720 align:start position:0% in SEK snark proof outside of the 00:20:56.720 --> 00:20:59.320 align:start position:0% in SEK snark proof outside of the blockchain<00:20:57.669> people<00:20:58.669> can<00:20:58.820> come<00:20:58.999> up<00:20:59.090> with<00:20:59.119> all 00:20:59.320 --> 00:20:59.330 align:start position:0% blockchain people can come up with all 00:20:59.330 --> 00:21:01.389 align:start position:0% blockchain people can come up with all kind<00:20:59.509> of<00:20:59.539> systems<00:20:59.960> they<00:21:00.109> want<00:21:00.259> to<00:21:00.379> claim<00:21:01.220> about 00:21:01.389 --> 00:21:01.399 align:start position:0% kind of systems they want to claim about 00:21:01.399 --> 00:21:03.220 align:start position:0% kind of systems they want to claim about each<00:21:01.639> other<00:21:01.850> and<00:21:02.210> as<00:21:02.539> long<00:21:02.690> as<00:21:02.720> we<00:21:02.929> follow<00:21:03.139> the 00:21:03.220 --> 00:21:03.230 align:start position:0% each other and as long as we follow the 00:21:03.230 --> 00:21:04.749 align:start position:0% each other and as long as we follow the simple<00:21:03.679> standard<00:21:04.100> we<00:21:04.340> have<00:21:04.549> that 00:21:04.749 --> 00:21:04.759 align:start position:0% simple standard we have that 00:21:04.759 --> 00:21:06.849 align:start position:0% simple standard we have that interoperability<00:21:05.299> which<00:21:06.019> can<00:21:06.259> create<00:21:06.470> all<00:21:06.679> of 00:21:06.849 --> 00:21:06.859 align:start position:0% interoperability which can create all of 00:21:06.859 --> 00:21:09.190 align:start position:0% interoperability which can create all of this<00:21:07.009> network<00:21:07.429> effect<00:21:07.789> we<00:21:07.999> see<00:21:08.179> with<00:21:08.450> USC<00:21:08.869> 20 00:21:09.190 --> 00:21:09.200 align:start position:0% this network effect we see with USC 20 00:21:09.200 --> 00:21:12.609 align:start position:0% this network effect we see with USC 20 for<00:21:09.350> example<00:21:09.850> so<00:21:10.850> it's<00:21:11.359> all<00:21:11.509> about<00:21:11.619> discussing 00:21:12.609 --> 00:21:12.619 align:start position:0% for example so it's all about discussing 00:21:12.619 --> 00:21:15.039 align:start position:0% for example so it's all about discussing and<00:21:13.149> coming<00:21:14.149> to<00:21:14.269> an<00:21:14.330> agreement<00:21:14.600> what<00:21:14.869> makes 00:21:15.039 --> 00:21:15.049 align:start position:0% and coming to an agreement what makes 00:21:15.049 --> 00:21:17.379 align:start position:0% and coming to an agreement what makes sense<00:21:15.289> start<00:21:15.679> playing<00:21:16.009> around<00:21:16.159> and<00:21:16.580> making<00:21:17.239> a 00:21:17.379 --> 00:21:17.389 align:start position:0% sense start playing around and making a 00:21:17.389 --> 00:21:27.560 align:start position:0% sense start playing around and making a huge<00:21:17.539> experimentation<00:21:18.169> around<00:21:18.559> it 00:21:27.560 --> 00:21:27.570 align:start position:0% 00:21:27.570 --> 00:21:34.140 align:start position:0% [Applause] 00:21:34.140 --> 00:21:34.150 align:start position:0% 00:21:34.150 --> 00:21:41.729 align:start position:0% [Music]