WEBVTT Kind: captions Language: en 00:00:04.620 --> 00:00:14.900 align:start position:0% [Music] 00:00:14.900 --> 00:00:14.910 align:start position:0% 00:00:14.910 --> 00:00:16.310 align:start position:0% [Music] 00:00:16.310 --> 00:00:16.320 align:start position:0% [Music] 00:00:16.320 --> 00:00:18.310 align:start position:0% [Music] okay<00:00:16.600> thank<00:00:16.760> you<00:00:17.000> Ming<00:00:17.560> and<00:00:17.800> thank<00:00:17.960> you<00:00:18.080> for 00:00:18.310 --> 00:00:18.320 align:start position:0% okay thank you Ming and thank you for 00:00:18.320 --> 00:00:21.630 align:start position:0% okay thank you Ming and thank you for having<00:00:18.640> me<00:00:19.640> um<00:00:19.880> I'm<00:00:20.039> going<00:00:20.160> to<00:00:20.400> talk<00:00:20.720> about 00:00:21.630 --> 00:00:21.640 align:start position:0% having me um I'm going to talk about 00:00:21.640 --> 00:00:25.710 align:start position:0% having me um I'm going to talk about digital<00:00:22.199> identity<00:00:23.199> the<00:00:23.560> the<00:00:23.920> uh<00:00:24.840> uh<00:00:25.560> my 00:00:25.710 --> 00:00:25.720 align:start position:0% digital identity the the uh uh my 00:00:25.720 --> 00:00:27.589 align:start position:0% digital identity the the uh uh my original<00:00:26.199> topic<00:00:26.439> was<00:00:26.560> to<00:00:26.720> talk<00:00:26.920> about<00:00:27.160> digital 00:00:27.589 --> 00:00:27.599 align:start position:0% original topic was to talk about digital 00:00:27.599 --> 00:00:31.070 align:start position:0% original topic was to talk about digital identity<00:00:28.359> and<00:00:29.320> publicy<00:00:30.119> structure<00:00:30.599> but<00:00:30.960> you 00:00:31.070 --> 00:00:31.080 align:start position:0% identity and publicy structure but you 00:00:31.080 --> 00:00:32.950 align:start position:0% identity and publicy structure but you know<00:00:31.240> there's<00:00:31.439> only<00:00:31.679> 20<00:00:31.960> minutes<00:00:32.480> and<00:00:32.719> who<00:00:32.840> am 00:00:32.950 --> 00:00:32.960 align:start position:0% know there's only 20 minutes and who am 00:00:32.960 --> 00:00:38.510 align:start position:0% know there's only 20 minutes and who am I<00:00:33.440> kidding<00:00:34.440> so<00:00:35.360> let's<00:00:36.239> uh<00:00:36.480> launch<00:00:37.040> right<00:00:37.239> in<00:00:37.520> it 00:00:38.510 --> 00:00:38.520 align:start position:0% I kidding so let's uh launch right in it 00:00:38.520 --> 00:00:42.790 align:start position:0% I kidding so let's uh launch right in it so<00:00:39.320> what<00:00:39.600> is<00:00:39.920> digital<00:00:40.680> identity<00:00:41.680> so 00:00:42.790 --> 00:00:42.800 align:start position:0% so what is digital identity so 00:00:42.800 --> 00:00:46.709 align:start position:0% so what is digital identity so conceptually<00:00:43.800> it's<00:00:44.039> a<00:00:44.719> digital<00:00:45.280> object<00:00:46.280> that 00:00:46.709 --> 00:00:46.719 align:start position:0% conceptually it's a digital object that 00:00:46.719 --> 00:00:50.670 align:start position:0% conceptually it's a digital object that maps<00:00:47.199> onto<00:00:47.800> a<00:00:48.239> physical<00:00:49.199> entity<00:00:50.199> normally 00:00:50.670 --> 00:00:50.680 align:start position:0% maps onto a physical entity normally 00:00:50.680 --> 00:00:52.750 align:start position:0% maps onto a physical entity normally when<00:00:50.840> we<00:00:51.000> talk<00:00:51.239> about<00:00:51.520> this<00:00:51.840> stuff<00:00:52.480> uh<00:00:52.600> we're 00:00:52.750 --> 00:00:52.760 align:start position:0% when we talk about this stuff uh we're 00:00:52.760 --> 00:00:55.709 align:start position:0% when we talk about this stuff uh we're talking<00:00:53.039> about<00:00:53.680> people<00:00:54.680> but<00:00:55.079> it<00:00:55.199> can<00:00:55.440> also 00:00:55.709 --> 00:00:55.719 align:start position:0% talking about people but it can also 00:00:55.719 --> 00:00:59.430 align:start position:0% talking about people but it can also mean<00:00:56.320> a<00:00:57.079> uh<00:00:57.199> a<00:00:57.359> company<00:00:57.760> a<00:00:58.039> corporation<00:00:59.039> or<00:00:59.239> a 00:00:59.430 --> 00:00:59.440 align:start position:0% mean a uh a company a corporation or a 00:00:59.440 --> 00:01:03.229 align:start position:0% mean a uh a company a corporation or a device<00:01:00.399> so<00:01:00.760> the<00:01:01.039> the<00:01:01.440> common<00:01:02.440> saying<00:01:02.879> is<00:01:03.079> that 00:01:03.229 --> 00:01:03.239 align:start position:0% device so the the common saying is that 00:01:03.239 --> 00:01:04.950 align:start position:0% device so the the common saying is that on<00:01:03.440> the<00:01:03.559> blockchain<00:01:04.040> nobody<00:01:04.360> knows<00:01:04.559> your 00:01:04.950 --> 00:01:04.960 align:start position:0% on the blockchain nobody knows your 00:01:04.960 --> 00:01:07.630 align:start position:0% on the blockchain nobody knows your fridge<00:01:05.880> and<00:01:06.080> so<00:01:06.880> they're<00:01:07.119> they're<00:01:07.360> talking 00:01:07.630 --> 00:01:07.640 align:start position:0% fridge and so they're they're talking 00:01:07.640 --> 00:01:09.310 align:start position:0% fridge and so they're they're talking about<00:01:07.880> digital 00:01:09.310 --> 00:01:09.320 align:start position:0% about digital 00:01:09.320 --> 00:01:13.990 align:start position:0% about digital identity<00:01:10.479> um<00:01:11.479> why<00:01:12.159> do<00:01:12.400> we<00:01:13.000> want<00:01:13.520> digital 00:01:13.990 --> 00:01:14.000 align:start position:0% identity um why do we want digital 00:01:14.000 --> 00:01:17.630 align:start position:0% identity um why do we want digital identity<00:01:15.000> so<00:01:15.439> we<00:01:15.560> want<00:01:15.720> to<00:01:16.080> tie<00:01:16.680> actors<00:01:17.280> in<00:01:17.439> the 00:01:17.630 --> 00:01:17.640 align:start position:0% identity so we want to tie actors in the 00:01:17.640 --> 00:01:21.749 align:start position:0% identity so we want to tie actors in the physical<00:01:18.119> world<00:01:18.680> to<00:01:19.040> the<00:01:19.640> digital<00:01:20.159> world<00:01:20.759> so 00:01:21.749 --> 00:01:21.759 align:start position:0% physical world to the digital world so 00:01:21.759 --> 00:01:24.310 align:start position:0% physical world to the digital world so this<00:01:21.960> is<00:01:22.680> for<00:01:22.920> instance<00:01:23.439> good<00:01:23.720> because<00:01:24.159> it 00:01:24.310 --> 00:01:24.320 align:start position:0% this is for instance good because it 00:01:24.320 --> 00:01:27.670 align:start position:0% this is for instance good because it allows<00:01:24.960> actors<00:01:25.880> with<00:01:26.119> some<00:01:26.479> Authority<00:01:27.320> in<00:01:27.479> the 00:01:27.670 --> 00:01:27.680 align:start position:0% allows actors with some Authority in the 00:01:27.680 --> 00:01:29.990 align:start position:0% allows actors with some Authority in the physical<00:01:28.079> world<00:01:28.439> to<00:01:28.720> express<00:01:29.240> that<00:01:29.400> Authority 00:01:29.990 --> 00:01:30.000 align:start position:0% physical world to express that Authority 00:01:30.000 --> 00:01:32.749 align:start position:0% physical world to express that Authority on<00:01:30.119> the<00:01:30.320> blockchain<00:01:31.320> so<00:01:31.600> you<00:01:31.720> can<00:01:31.960> imagine<00:01:32.479> a 00:01:32.749 --> 00:01:32.759 align:start position:0% on the blockchain so you can imagine a 00:01:32.759 --> 00:01:36.030 align:start position:0% on the blockchain so you can imagine a form<00:01:33.079> of<00:01:33.759> proof<00:01:34.040> of<00:01:34.280> birth<00:01:34.640> or<00:01:34.840> proof<00:01:35.079> of<00:01:35.320> death 00:01:36.030 --> 00:01:36.040 align:start position:0% form of proof of birth or proof of death 00:01:36.040 --> 00:01:39.950 align:start position:0% form of proof of birth or proof of death as<00:01:36.520> a<00:01:37.520> uh<00:01:38.040> digital<00:01:38.680> attestation<00:01:39.240> or<00:01:39.479> signature 00:01:39.950 --> 00:01:39.960 align:start position:0% as a uh digital attestation or signature 00:01:39.960 --> 00:01:45.630 align:start position:0% as a uh digital attestation or signature by<00:01:40.119> a<00:01:40.680> doctor<00:01:41.680> uh<00:01:42.079> also<00:01:43.079> digital<00:01:43.560> kyc<00:01:44.560> is<00:01:44.880> is<00:01:45.119> a 00:01:45.630 --> 00:01:45.640 align:start position:0% by a doctor uh also digital kyc is is a 00:01:45.640 --> 00:01:48.950 align:start position:0% by a doctor uh also digital kyc is is a uh<00:01:46.079> common<00:01:46.399> use<00:01:46.759> case<00:01:46.960> where<00:01:47.119> a<00:01:47.360> bank<00:01:48.280> attests 00:01:48.950 --> 00:01:48.960 align:start position:0% uh common use case where a bank attests 00:01:48.960 --> 00:01:51.429 align:start position:0% uh common use case where a bank attests that<00:01:49.119> they've<00:01:49.360> done<00:01:49.640> certain<00:01:50.040> checks<00:01:51.000> and<00:01:51.159> now 00:01:51.429 --> 00:01:51.439 align:start position:0% that they've done certain checks and now 00:01:51.439 --> 00:01:53.870 align:start position:0% that they've done certain checks and now that<00:01:51.640> attestation<00:01:52.320> can<00:01:52.479> be<00:01:52.680> used<00:01:53.520> on<00:01:53.680> a 00:01:53.870 --> 00:01:53.880 align:start position:0% that attestation can be used on a 00:01:53.880 --> 00:01:57.109 align:start position:0% that attestation can be used on a blockchain<00:01:54.280> in<00:01:54.399> a<00:01:54.520> smart<00:01:55.000> contract<00:01:56.119> doing 00:01:57.109 --> 00:01:57.119 align:start position:0% blockchain in a smart contract doing 00:01:57.119 --> 00:02:01.029 align:start position:0% blockchain in a smart contract doing crowdfunding<00:01:57.960> or<00:01:58.200> or<00:01:58.399> what<00:01:58.560> have<00:01:58.759> you<00:01:59.719> uh<00:02:00.039> um 00:02:01.029 --> 00:02:01.039 align:start position:0% crowdfunding or or what have you uh um 00:02:01.039 --> 00:02:03.389 align:start position:0% crowdfunding or or what have you uh um it<00:02:01.320> also<00:02:01.600> allows<00:02:02.079> mapping<00:02:02.680> of<00:02:02.920> social 00:02:03.389 --> 00:02:03.399 align:start position:0% it also allows mapping of social 00:02:03.399 --> 00:02:06.429 align:start position:0% it also allows mapping of social structures<00:02:04.399> into<00:02:04.840> the<00:02:05.079> digital<00:02:05.479> realm<00:02:06.159> and 00:02:06.429 --> 00:02:06.439 align:start position:0% structures into the digital realm and 00:02:06.439 --> 00:02:10.309 align:start position:0% structures into the digital realm and kind<00:02:06.600> of<00:02:07.479> enhancing<00:02:08.479> um<00:02:09.360> social<00:02:09.720> structures 00:02:10.309 --> 00:02:10.319 align:start position:0% kind of enhancing um social structures 00:02:10.319 --> 00:02:13.750 align:start position:0% kind of enhancing um social structures through<00:02:11.000> smart<00:02:11.400> contracts<00:02:12.239> so<00:02:12.640> this<00:02:12.800> is<00:02:13.560> for 00:02:13.750 --> 00:02:13.760 align:start position:0% through smart contracts so this is for 00:02:13.760 --> 00:02:15.949 align:start position:0% through smart contracts so this is for instance<00:02:14.440> uh<00:02:15.000> Community 00:02:15.949 --> 00:02:15.959 align:start position:0% instance uh Community 00:02:15.959 --> 00:02:18.229 align:start position:0% instance uh Community formation<00:02:16.959> uh<00:02:17.239> we<00:02:17.400> have<00:02:17.519> a<00:02:17.680> dab<00:02:17.959> called 00:02:18.229 --> 00:02:18.239 align:start position:0% formation uh we have a dab called 00:02:18.239 --> 00:02:22.309 align:start position:0% formation uh we have a dab called inflect<00:02:19.200> that<00:02:19.560> that<00:02:19.800> uses<00:02:20.280> this<00:02:21.319> also 00:02:22.309 --> 00:02:22.319 align:start position:0% inflect that that uses this also 00:02:22.319 --> 00:02:24.470 align:start position:0% inflect that that uses this also reputation<00:02:23.000> systems<00:02:23.360> are<00:02:23.560> anchored<00:02:24.000> in<00:02:24.200> this 00:02:24.470 --> 00:02:24.480 align:start position:0% reputation systems are anchored in this 00:02:24.480 --> 00:02:28.110 align:start position:0% reputation systems are anchored in this notion<00:02:25.080> of<00:02:25.560> uh<00:02:26.440> uh<00:02:26.599> digital<00:02:27.040> identity<00:02:27.680> because 00:02:28.110 --> 00:02:28.120 align:start position:0% notion of uh uh digital identity because 00:02:28.120 --> 00:02:30.869 align:start position:0% notion of uh uh digital identity because digital<00:02:28.840> identities<00:02:29.920> say<00:02:30.239> stuff<00:02:30.519> about<00:02:30.760> each 00:02:30.869 --> 00:02:30.879 align:start position:0% digital identities say stuff about each 00:02:30.879 --> 00:02:33.710 align:start position:0% digital identities say stuff about each other<00:02:31.280> and<00:02:31.480> and<00:02:31.680> that's<00:02:32.000> forms<00:02:32.640> reputation<00:02:33.640> uh 00:02:33.710 --> 00:02:33.720 align:start position:0% other and and that's forms reputation uh 00:02:33.720 --> 00:02:35.990 align:start position:0% other and and that's forms reputation uh there's<00:02:33.959> also<00:02:34.200> the<00:02:34.400> humanitarian<00:02:35.160> side<00:02:35.680> a<00:02:35.840> lot 00:02:35.990 --> 00:02:36.000 align:start position:0% there's also the humanitarian side a lot 00:02:36.000 --> 00:02:40.670 align:start position:0% there's also the humanitarian side a lot of<00:02:37.000> um<00:02:38.000> refugees<00:02:38.959> or<00:02:39.680> uh<00:02:39.879> victims<00:02:40.200> of<00:02:40.400> human 00:02:40.670 --> 00:02:40.680 align:start position:0% of um refugees or uh victims of human 00:02:40.680 --> 00:02:43.110 align:start position:0% of um refugees or uh victims of human trafficking<00:02:41.159> often<00:02:41.959> lack<00:02:42.720> paper 00:02:43.110 --> 00:02:43.120 align:start position:0% trafficking often lack paper 00:02:43.120 --> 00:02:45.350 align:start position:0% trafficking often lack paper documentation<00:02:43.640> altogether<00:02:44.640> and<00:02:44.800> if<00:02:44.920> we<00:02:45.080> can 00:02:45.350 --> 00:02:45.360 align:start position:0% documentation altogether and if we can 00:02:45.360 --> 00:02:48.990 align:start position:0% documentation altogether and if we can have<00:02:45.959> a<00:02:46.239> system<00:02:46.720> where<00:02:47.519> you<00:02:47.800> have<00:02:48.200> a<00:02:48.599> digital 00:02:48.990 --> 00:02:49.000 align:start position:0% have a system where you have a digital 00:02:49.000 --> 00:02:51.869 align:start position:0% have a system where you have a digital identity<00:02:49.560> system<00:02:50.200> maybe<00:02:51.080> coupled<00:02:51.519> with 00:02:51.869 --> 00:02:51.879 align:start position:0% identity system maybe coupled with 00:02:51.879 --> 00:02:55.270 align:start position:0% identity system maybe coupled with Biometrics<00:02:52.879> run<00:02:53.239> by<00:02:53.400> ngos<00:02:54.080> Etc<00:02:54.599> this<00:02:55.040> this 00:02:55.270 --> 00:02:55.280 align:start position:0% Biometrics run by ngos Etc this this 00:02:55.280 --> 00:02:56.869 align:start position:0% Biometrics run by ngos Etc this this might<00:02:55.640> help<00:02:55.840> a<00:02:55.959> lot<00:02:56.080> of 00:02:56.869 --> 00:02:56.879 align:start position:0% might help a lot of 00:02:56.879 --> 00:03:01.270 align:start position:0% might help a lot of people<00:02:57.879> uh<00:02:58.879> how<00:02:59.599> how<00:02:59.840> how<00:02:59.959> do<00:03:00.040> we<00:03:00.239> map<00:03:00.959> from 00:03:01.270 --> 00:03:01.280 align:start position:0% people uh how how how do we map from 00:03:01.280 --> 00:03:04.550 align:start position:0% people uh how how how do we map from digital<00:03:01.680> to<00:03:01.920> physical<00:03:02.920> the<00:03:03.120> most<00:03:03.519> common<00:03:03.879> form 00:03:04.550 --> 00:03:04.560 align:start position:0% digital to physical the most common form 00:03:04.560 --> 00:03:09.710 align:start position:0% digital to physical the most common form is<00:03:05.519> by<00:03:05.760> using<00:03:06.280> a<00:03:07.239> secret<00:03:08.239> that<00:03:08.480> only<00:03:09.040> the 00:03:09.710 --> 00:03:09.720 align:start position:0% is by using a secret that only the 00:03:09.720 --> 00:03:13.509 align:start position:0% is by using a secret that only the physical<00:03:10.239> entity<00:03:10.840> knows<00:03:11.840> so<00:03:12.720> for<00:03:12.920> instance<00:03:13.200> on 00:03:13.509 --> 00:03:13.519 align:start position:0% physical entity knows so for instance on 00:03:13.519 --> 00:03:15.949 align:start position:0% physical entity knows so for instance on ethereum<00:03:14.519> you<00:03:14.680> have<00:03:14.799> an<00:03:14.959> ethereum<00:03:15.480> account<00:03:15.840> or 00:03:15.949 --> 00:03:15.959 align:start position:0% ethereum you have an ethereum account or 00:03:15.959 --> 00:03:18.309 align:start position:0% ethereum you have an ethereum account or an<00:03:16.159> address<00:03:17.040> that<00:03:17.239> has<00:03:17.400> an<00:03:17.599> Associated 00:03:18.309 --> 00:03:18.319 align:start position:0% an address that has an Associated 00:03:18.319 --> 00:03:20.990 align:start position:0% an address that has an Associated private<00:03:18.720> key<00:03:19.720> and<00:03:19.959> anyone<00:03:20.319> who<00:03:20.560> has<00:03:20.760> that 00:03:20.990 --> 00:03:21.000 align:start position:0% private key and anyone who has that 00:03:21.000 --> 00:03:23.470 align:start position:0% private key and anyone who has that private<00:03:21.319> key<00:03:21.599> can<00:03:22.200> send<00:03:22.640> transactions 00:03:23.470 --> 00:03:23.480 align:start position:0% private key can send transactions 00:03:23.480 --> 00:03:26.830 align:start position:0% private key can send transactions interact<00:03:23.920> with<00:03:24.159> contracts<00:03:24.720> Etc<00:03:25.720> and<00:03:25.840> so<00:03:26.200> the 00:03:26.830 --> 00:03:26.840 align:start position:0% interact with contracts Etc and so the 00:03:26.840 --> 00:03:30.070 align:start position:0% interact with contracts Etc and so the the<00:03:27.040> assumption<00:03:27.560> is<00:03:27.879> there<00:03:28.599> that<00:03:29.599> uh<00:03:29.959> the 00:03:30.070 --> 00:03:30.080 align:start position:0% the assumption is there that uh the 00:03:30.080 --> 00:03:31.509 align:start position:0% the assumption is there that uh the holder<00:03:30.439> of<00:03:30.560> the<00:03:30.720> private<00:03:31.040> key<00:03:31.239> is<00:03:31.360> the 00:03:31.509 --> 00:03:31.519 align:start position:0% holder of the private key is the 00:03:31.519 --> 00:03:36.350 align:start position:0% holder of the private key is the physical<00:03:32.159> entity<00:03:33.159> and<00:03:33.480> it<00:03:33.799> it<00:03:34.120> Maps<00:03:35.120> uh<00:03:35.920> onto 00:03:36.350 --> 00:03:36.360 align:start position:0% physical entity and it it Maps uh onto 00:03:36.360 --> 00:03:39.070 align:start position:0% physical entity and it it Maps uh onto the<00:03:36.640> blockchain<00:03:37.640> another<00:03:38.040> example<00:03:38.480> is<00:03:38.799> is 00:03:39.070 --> 00:03:39.080 align:start position:0% the blockchain another example is is 00:03:39.080 --> 00:03:42.670 align:start position:0% the blockchain another example is is Facebook<00:03:40.080> if<00:03:40.239> someone<00:03:40.799> has<00:03:41.319> my<00:03:41.879> password<00:03:42.400> to 00:03:42.670 --> 00:03:42.680 align:start position:0% Facebook if someone has my password to 00:03:42.680 --> 00:03:44.710 align:start position:0% Facebook if someone has my password to Facebook<00:03:43.239> they<00:03:43.360> can<00:03:43.599> post<00:03:43.840> on<00:03:44.000> my<00:03:44.200> wall<00:03:44.519> and 00:03:44.710 --> 00:03:44.720 align:start position:0% Facebook they can post on my wall and 00:03:44.720 --> 00:03:48.550 align:start position:0% Facebook they can post on my wall and they<00:03:44.840> can<00:03:45.760> kind<00:03:45.959> of<00:03:46.799> act<00:03:47.200> as<00:03:47.439> me<00:03:47.959> in<00:03:48.200> in<00:03:48.319> the 00:03:48.550 --> 00:03:48.560 align:start position:0% they can kind of act as me in in the 00:03:48.560 --> 00:03:52.670 align:start position:0% they can kind of act as me in in the context<00:03:49.159> of<00:03:49.280> the<00:03:49.439> Facebook<00:03:50.319> platform<00:03:51.360> um<00:03:52.360> so 00:03:52.670 --> 00:03:52.680 align:start position:0% context of the Facebook platform um so 00:03:52.680 --> 00:03:54.589 align:start position:0% context of the Facebook platform um so lastly<00:03:53.120> here 00:03:54.589 --> 00:03:54.599 align:start position:0% lastly here 00:03:54.599 --> 00:03:57.830 align:start position:0% lastly here this<00:03:55.599> a<00:03:55.840> digital<00:03:56.280> signature<00:03:56.959> is<00:03:57.319> proof<00:03:57.599> of 00:03:57.830 --> 00:03:57.840 align:start position:0% this a digital signature is proof of 00:03:57.840 --> 00:04:00.429 align:start position:0% this a digital signature is proof of knowledge<00:03:58.360> of<00:03:58.480> a<00:03:58.680> secret<00:03:59.360> without<00:03:59.879> revealing 00:04:00.429 --> 00:04:00.439 align:start position:0% knowledge of a secret without revealing 00:04:00.439 --> 00:04:04.470 align:start position:0% knowledge of a secret without revealing the<00:04:00.640> secret<00:04:01.400> so<00:04:01.799> this<00:04:01.920> is<00:04:02.720> why<00:04:03.720> uh<00:04:04.079> digital 00:04:04.470 --> 00:04:04.480 align:start position:0% the secret so this is why uh digital 00:04:04.480 --> 00:04:08.750 align:start position:0% the secret so this is why uh digital signatures<00:04:05.000> are<00:04:05.200> so<00:04:06.079> important<00:04:06.879> for<00:04:07.760> for<00:04:08.439> uh 00:04:08.750 --> 00:04:08.760 align:start position:0% signatures are so important for for uh 00:04:08.760 --> 00:04:13.030 align:start position:0% signatures are so important for for uh blockchains<00:04:09.879> because<00:04:10.879> it<00:04:11.879> uh<00:04:12.120> authenticates 00:04:13.030 --> 00:04:13.040 align:start position:0% blockchains because it uh authenticates 00:04:13.040 --> 00:04:14.990 align:start position:0% blockchains because it uh authenticates that<00:04:13.200> you<00:04:13.360> know<00:04:13.680> the<00:04:13.959> secret<00:04:14.680> and<00:04:14.840> that 00:04:14.990 --> 00:04:15.000 align:start position:0% that you know the secret and that 00:04:15.000 --> 00:04:16.830 align:start position:0% that you know the secret and that creates<00:04:15.319> the<00:04:15.439> mapping<00:04:15.760> to<00:04:15.879> the<00:04:16.000> physical 00:04:16.830 --> 00:04:16.840 align:start position:0% creates the mapping to the physical 00:04:16.840 --> 00:04:20.150 align:start position:0% creates the mapping to the physical entity<00:04:17.840> so<00:04:18.440> uh<00:04:18.560> the<00:04:18.720> most<00:04:18.959> common<00:04:19.320> form<00:04:19.680> of 00:04:20.150 --> 00:04:20.160 align:start position:0% entity so uh the most common form of 00:04:20.160 --> 00:04:22.350 align:start position:0% entity so uh the most common form of digital<00:04:20.600> identity<00:04:21.079> today<00:04:21.600> is<00:04:21.759> what<00:04:21.880> we<00:04:22.040> call 00:04:22.350 --> 00:04:22.360 align:start position:0% digital identity today is what we call 00:04:22.360 --> 00:04:24.790 align:start position:0% digital identity today is what we call Federated<00:04:23.080> identity<00:04:24.000> so<00:04:24.240> this<00:04:24.400> means<00:04:24.639> that 00:04:24.790 --> 00:04:24.800 align:start position:0% Federated identity so this means that 00:04:24.800 --> 00:04:27.990 align:start position:0% Federated identity so this means that you<00:04:25.040> have<00:04:25.320> a<00:04:25.600> third-party<00:04:26.479> identity 00:04:27.990 --> 00:04:28.000 align:start position:0% you have a third-party identity 00:04:28.000 --> 00:04:30.270 align:start position:0% you have a third-party identity provider<00:04:29.000> uh<00:04:29.240> that<00:04:29.400> hand<00:04:29.720> handles<00:04:30.080> this 00:04:30.270 --> 00:04:30.280 align:start position:0% provider uh that hand handles this 00:04:30.280 --> 00:04:32.629 align:start position:0% provider uh that hand handles this mapping<00:04:30.720> from<00:04:30.960> the<00:04:31.120> digital<00:04:31.520> to<00:04:31.720> the<00:04:31.880> physical 00:04:32.629 --> 00:04:32.639 align:start position:0% mapping from the digital to the physical 00:04:32.639 --> 00:04:38.310 align:start position:0% mapping from the digital to the physical and<00:04:32.840> so<00:04:33.759> whenever<00:04:34.280> you<00:04:34.840> act<00:04:35.840> as<00:04:36.400> your<00:04:37.400> um 00:04:38.310 --> 00:04:38.320 align:start position:0% and so whenever you act as your um 00:04:38.320 --> 00:04:41.870 align:start position:0% and so whenever you act as your um digital<00:04:39.080> Identity<00:04:40.080> On<00:04:40.199> A<00:04:40.360> blockchain<00:04:40.800> or<00:04:40.960> in<00:04:41.039> a 00:04:41.870 --> 00:04:41.880 align:start position:0% digital Identity On A blockchain or in a 00:04:41.880 --> 00:04:44.830 align:start position:0% digital Identity On A blockchain or in a digital<00:04:42.360> space<00:04:43.080> you<00:04:43.280> do<00:04:43.479> so<00:04:43.880> through<00:04:44.320> this 00:04:44.830 --> 00:04:44.840 align:start position:0% digital space you do so through this 00:04:44.840 --> 00:04:47.310 align:start position:0% digital space you do so through this centralized<00:04:45.639> intermediary<00:04:46.639> so<00:04:46.880> I'm<00:04:46.960> sure<00:04:47.199> you 00:04:47.310 --> 00:04:47.320 align:start position:0% centralized intermediary so I'm sure you 00:04:47.320 --> 00:04:49.909 align:start position:0% centralized intermediary so I'm sure you all<00:04:47.560> have<00:04:47.800> seen<00:04:48.800> uh<00:04:48.919> log<00:04:49.160> in<00:04:49.400> with<00:04:49.560> Facebook 00:04:49.909 --> 00:04:49.919 align:start position:0% all have seen uh log in with Facebook 00:04:49.919 --> 00:04:53.310 align:start position:0% all have seen uh log in with Facebook log<00:04:50.160> in<00:04:50.320> with<00:04:50.520> Google<00:04:51.440> this<00:04:51.560> is<00:04:52.520> Facebook 00:04:53.310 --> 00:04:53.320 align:start position:0% log in with Google this is Facebook 00:04:53.320 --> 00:04:56.510 align:start position:0% log in with Google this is Facebook acting<00:04:54.320> or<00:04:54.680> you<00:04:55.120> acting<00:04:55.600> through 00:04:56.510 --> 00:04:56.520 align:start position:0% acting or you acting through 00:04:56.520 --> 00:05:01.790 align:start position:0% acting or you acting through Facebook<00:04:58.000> um<00:04:59.000> as<00:04:59.080> a<00:04:59.240> digital<00:05:00.080> identity 00:05:01.790 --> 00:05:01.800 align:start position:0% Facebook um as a digital identity 00:05:01.800 --> 00:05:04.430 align:start position:0% Facebook um as a digital identity so<00:05:02.800> what<00:05:03.000> we<00:05:03.120> want<00:05:03.280> to<00:05:03.440> try<00:05:03.600> and<00:05:03.720> move<00:05:03.960> towards 00:05:04.430 --> 00:05:04.440 align:start position:0% so what we want to try and move towards 00:05:04.440 --> 00:05:06.909 align:start position:0% so what we want to try and move towards is<00:05:04.639> this<00:05:04.840> notion<00:05:05.240> of<00:05:05.800> self<00:05:06.280> Sovereign 00:05:06.909 --> 00:05:06.919 align:start position:0% is this notion of self Sovereign 00:05:06.919 --> 00:05:10.189 align:start position:0% is this notion of self Sovereign identity<00:05:07.919> so<00:05:08.400> uh<00:05:08.600> this<00:05:09.120> this<00:05:09.400> image<00:05:09.759> came<00:05:09.960> up 00:05:10.189 --> 00:05:10.199 align:start position:0% identity so uh this this image came up 00:05:10.199 --> 00:05:12.950 align:start position:0% identity so uh this this image came up when<00:05:10.360> I<00:05:10.560> when<00:05:10.720> I<00:05:10.880> Googled<00:05:11.320> self<00:05:11.800> Sovereign<00:05:12.400> and 00:05:12.950 --> 00:05:12.960 align:start position:0% when I when I Googled self Sovereign and 00:05:12.960 --> 00:05:14.350 align:start position:0% when I when I Googled self Sovereign and isn't<00:05:13.199> it<00:05:13.400> so 00:05:14.350 --> 00:05:14.360 align:start position:0% isn't it so 00:05:14.360 --> 00:05:18.670 align:start position:0% isn't it so empowering<00:05:15.360> um<00:05:16.240> so<00:05:16.639> so<00:05:16.880> this<00:05:17.000> is<00:05:17.160> the<00:05:17.360> idea<00:05:17.800> of 00:05:18.670 --> 00:05:18.680 align:start position:0% empowering um so so this is the idea of 00:05:18.680 --> 00:05:21.510 align:start position:0% empowering um so so this is the idea of having<00:05:19.039> the<00:05:19.240> user<00:05:20.120> actually<00:05:20.479> be<00:05:20.759> in<00:05:21.039> control 00:05:21.510 --> 00:05:21.520 align:start position:0% having the user actually be in control 00:05:21.520 --> 00:05:26.510 align:start position:0% having the user actually be in control of<00:05:21.680> their<00:05:21.880> own<00:05:22.639> identity<00:05:23.639> uh<00:05:24.520> if<00:05:24.680> we<00:05:24.880> use<00:05:25.560> a<00:05:26.000> a<00:05:26.360> a 00:05:26.510 --> 00:05:26.520 align:start position:0% of their own identity uh if we use a a a 00:05:26.520 --> 00:05:28.830 align:start position:0% of their own identity uh if we use a a a platform<00:05:26.919> like<00:05:27.080> ethereum<00:05:27.759> then<00:05:28.400> smart 00:05:28.830 --> 00:05:28.840 align:start position:0% platform like ethereum then smart 00:05:28.840 --> 00:05:32.150 align:start position:0% platform like ethereum then smart contract<00:05:29.440> can<00:05:29.720> can<00:05:30.120> do<00:05:30.600> a<00:05:30.759> lot<00:05:31.039> of<00:05:31.319> what<00:05:31.560> the 00:05:32.150 --> 00:05:32.160 align:start position:0% contract can can do a lot of what the 00:05:32.160 --> 00:05:35.110 align:start position:0% contract can can do a lot of what the central<00:05:32.639> identity<00:05:33.199> provider<00:05:33.720> like<00:05:33.919> Facebook 00:05:35.110 --> 00:05:35.120 align:start position:0% central identity provider like Facebook 00:05:35.120 --> 00:05:38.309 align:start position:0% central identity provider like Facebook does<00:05:36.120> uh<00:05:36.319> while<00:05:36.639> being<00:05:37.080> a<00:05:37.240> a<00:05:37.360> shared<00:05:37.840> resource 00:05:38.309 --> 00:05:38.319 align:start position:0% does uh while being a a shared resource 00:05:38.319 --> 00:05:42.029 align:start position:0% does uh while being a a shared resource owned<00:05:38.720> by<00:05:39.360> no<00:05:39.560> one<00:05:39.720> and<00:05:40.199> everyone 00:05:42.029 --> 00:05:42.039 align:start position:0% owned by no one and everyone 00:05:42.039 --> 00:05:44.749 align:start position:0% owned by no one and everyone uh<00:05:43.039> the<00:05:43.199> idea<00:05:43.560> here<00:05:43.759> is<00:05:43.960> that<00:05:44.240> the<00:05:44.360> user 00:05:44.749 --> 00:05:44.759 align:start position:0% uh the idea here is that the user 00:05:44.759 --> 00:05:47.150 align:start position:0% uh the idea here is that the user controls<00:05:45.240> their<00:05:45.479> private<00:05:45.880> Keys<00:05:46.440> when 00:05:47.150 --> 00:05:47.160 align:start position:0% controls their private Keys when 00:05:47.160 --> 00:05:51.070 align:start position:0% controls their private Keys when interacting<00:05:48.160> uh<00:05:48.600> with<00:05:48.759> the<00:05:49.240> blockchain<00:05:50.240> but 00:05:51.070 --> 00:05:51.080 align:start position:0% interacting uh with the blockchain but 00:05:51.080 --> 00:05:53.550 align:start position:0% interacting uh with the blockchain but critically<00:05:52.080> the<00:05:52.199> user<00:05:52.479> can<00:05:52.680> also<00:05:52.960> choose<00:05:53.360> to 00:05:53.550 --> 00:05:53.560 align:start position:0% critically the user can also choose to 00:05:53.560 --> 00:05:56.350 align:start position:0% critically the user can also choose to let<00:05:53.840> a<00:05:54.000> third<00:05:54.360> party<00:05:55.240> control<00:05:55.639> the<00:05:55.800> keys<00:05:56.039> for 00:05:56.350 --> 00:05:56.360 align:start position:0% let a third party control the keys for 00:05:56.360 --> 00:06:01.070 align:start position:0% let a third party control the keys for them<00:05:56.720> so<00:05:56.919> we<00:05:57.080> can<00:05:57.960> have<00:05:58.960> uh<00:05:59.840> all<00:06:00.080> the<00:06:00.280> benefits 00:06:01.070 --> 00:06:01.080 align:start position:0% them so we can have uh all the benefits 00:06:01.080 --> 00:06:04.350 align:start position:0% them so we can have uh all the benefits of<00:06:01.440> of<00:06:01.840> the<00:06:01.960> Federated<00:06:02.720> identity<00:06:03.160> model<00:06:04.039> in 00:06:04.350 --> 00:06:04.360 align:start position:0% of of the Federated identity model in 00:06:04.360 --> 00:06:06.029 align:start position:0% of of the Federated identity model in the<00:06:04.560> The<00:06:04.720> Sovereign<00:06:05.319> self-<00:06:05.680> Sovereign 00:06:06.029 --> 00:06:06.039 align:start position:0% the The Sovereign self- Sovereign 00:06:06.039 --> 00:06:07.990 align:start position:0% the The Sovereign self- Sovereign identity 00:06:07.990 --> 00:06:08.000 align:start position:0% identity 00:06:08.000 --> 00:06:12.230 align:start position:0% identity model<00:06:09.000> so<00:06:09.280> how<00:06:09.680> how<00:06:09.840> do<00:06:10.000> we<00:06:10.400> build<00:06:11.400> uh<00:06:12.000> a 00:06:12.230 --> 00:06:12.240 align:start position:0% model so how how do we build uh a 00:06:12.240 --> 00:06:15.309 align:start position:0% model so how how do we build uh a digital<00:06:13.039> identity<00:06:13.599> system<00:06:14.479> with<00:06:14.880> self- 00:06:15.309 --> 00:06:15.319 align:start position:0% digital identity system with self- 00:06:15.319 --> 00:06:19.350 align:start position:0% digital identity system with self- sovereignty<00:06:15.919> at<00:06:16.080> the<00:06:16.319> core<00:06:17.599> so<00:06:18.599> the<00:06:18.759> starting 00:06:19.350 --> 00:06:19.360 align:start position:0% sovereignty at the core so the starting 00:06:19.360 --> 00:06:22.469 align:start position:0% sovereignty at the core so the starting point<00:06:20.319> is<00:06:21.080> the<00:06:21.280> notion 00:06:22.469 --> 00:06:22.479 align:start position:0% point is the notion 00:06:22.479 --> 00:06:27.670 align:start position:0% point is the notion of<00:06:23.479> uh<00:06:23.919> a<00:06:24.360> public<00:06:24.880> key<00:06:25.919> so<00:06:26.919> with<00:06:27.080> every<00:06:27.360> public 00:06:27.670 --> 00:06:27.680 align:start position:0% of uh a public key so with every public 00:06:27.680 --> 00:06:30.589 align:start position:0% of uh a public key so with every public key<00:06:27.919> comes<00:06:28.120> an<00:06:28.319> Associated<00:06:29.039> private<00:06:29.360> key 00:06:30.589 --> 00:06:30.599 align:start position:0% key comes an Associated private key 00:06:30.599 --> 00:06:32.670 align:start position:0% key comes an Associated private key and<00:06:30.720> the<00:06:30.919> public<00:06:31.280> key<00:06:31.560> then<00:06:31.800> becomes<00:06:32.400> this 00:06:32.670 --> 00:06:32.680 align:start position:0% and the public key then becomes this 00:06:32.680 --> 00:06:36.790 align:start position:0% and the public key then becomes this digital<00:06:33.280> object<00:06:34.240> that<00:06:34.440> is<00:06:34.680> mapped<00:06:35.360> to<00:06:35.960> the 00:06:36.790 --> 00:06:36.800 align:start position:0% digital object that is mapped to the 00:06:36.800 --> 00:06:40.110 align:start position:0% digital object that is mapped to the private<00:06:37.160> key<00:06:37.440> holder<00:06:38.440> which<00:06:38.639> lives<00:06:39.000> in<00:06:39.360> in<00:06:39.599> the 00:06:40.110 --> 00:06:40.120 align:start position:0% private key holder which lives in in the 00:06:40.120 --> 00:06:44.469 align:start position:0% private key holder which lives in in the uh<00:06:40.680> uh<00:06:40.840> Physical<00:06:41.319> Realm<00:06:42.000> so<00:06:42.319> examples<00:06:43.360> is<00:06:44.360> uh 00:06:44.469 --> 00:06:44.479 align:start position:0% uh uh Physical Realm so examples is uh 00:06:44.479 --> 00:06:48.150 align:start position:0% uh uh Physical Realm so examples is uh an<00:06:44.680> ethereum<00:06:45.240> address<00:06:46.240> a<00:06:46.520> Bitcoin<00:06:47.160> address 00:06:48.150 --> 00:06:48.160 align:start position:0% an ethereum address a Bitcoin address 00:06:48.160 --> 00:06:51.309 align:start position:0% an ethereum address a Bitcoin address something<00:06:48.479> like<00:06:48.680> a<00:06:48.919> a<00:06:49.479> a<00:06:49.599> minilock<00:06:50.280> ID<00:06:50.800> if<00:06:51.080> if 00:06:51.309 --> 00:06:51.319 align:start position:0% something like a a a minilock ID if if 00:06:51.319 --> 00:06:53.790 align:start position:0% something like a a a minilock ID if if anyone<00:06:51.800> has<00:06:52.120> used<00:06:52.479> or<00:06:52.639> heard<00:06:52.880> of 00:06:53.790 --> 00:06:53.800 align:start position:0% anyone has used or heard of 00:06:53.800 --> 00:06:58.430 align:start position:0% anyone has used or heard of minilock<00:06:55.199> um<00:06:56.199> the<00:06:56.960> this<00:06:57.080> is<00:06:57.400> like<00:06:57.560> a<00:06:57.759> very 00:06:58.430 --> 00:06:58.440 align:start position:0% minilock um the this is like a very 00:06:58.440 --> 00:07:00.309 align:start position:0% minilock um the this is like a very onedimensional 00:07:00.309 --> 00:07:00.319 align:start position:0% onedimensional 00:07:00.319 --> 00:07:03.909 align:start position:0% onedimensional um<00:07:01.240> Atomic<00:07:01.919> object<00:07:02.840> but<00:07:03.080> but<00:07:03.440> sometimes<00:07:03.759> this 00:07:03.909 --> 00:07:03.919 align:start position:0% um Atomic object but but sometimes this 00:07:03.919 --> 00:07:08.629 align:start position:0% um Atomic object but but sometimes this is<00:07:04.160> enough<00:07:05.080> like<00:07:05.280> if<00:07:05.479> I<00:07:05.680> go<00:07:06.199> on<00:07:07.199> um<00:07:07.639> ujo<00:07:08.199> music 00:07:08.629 --> 00:07:08.639 align:start position:0% is enough like if I go on um ujo music 00:07:08.639 --> 00:07:11.589 align:start position:0% is enough like if I go on um ujo music for<00:07:08.840> instance<00:07:09.280> and<00:07:09.400> I<00:07:09.520> want<00:07:09.680> to<00:07:10.319> buy<00:07:11.080> imin 00:07:11.589 --> 00:07:11.599 align:start position:0% for instance and I want to buy imin 00:07:11.599 --> 00:07:16.710 align:start position:0% for instance and I want to buy imin heap's<00:07:12.319> latest<00:07:13.240> song<00:07:14.240> uh<00:07:15.240> imagin<00:07:16.240> might<00:07:16.479> not 00:07:16.710 --> 00:07:16.720 align:start position:0% heap's latest song uh imagin might not 00:07:16.720 --> 00:07:20.550 align:start position:0% heap's latest song uh imagin might not even<00:07:17.039> care<00:07:17.800> who<00:07:18.039> I<00:07:18.319> am<00:07:19.319> she<00:07:19.599> only<00:07:19.960> know<00:07:20.360> she 00:07:20.550 --> 00:07:20.560 align:start position:0% even care who I am she only know she 00:07:20.560 --> 00:07:24.270 align:start position:0% even care who I am she only know she only<00:07:20.879> cares<00:07:21.599> that<00:07:22.599> uh<00:07:23.000> that<00:07:23.160> she<00:07:23.319> gets<00:07:23.680> paid 00:07:24.270 --> 00:07:24.280 align:start position:0% only cares that uh that she gets paid 00:07:24.280 --> 00:07:28.110 align:start position:0% only cares that uh that she gets paid and<00:07:24.720> so<00:07:25.840> the<00:07:26.840> the<00:07:27.000> only<00:07:27.360> information<00:07:27.919> she 00:07:28.110 --> 00:07:28.120 align:start position:0% and so the the only information she 00:07:28.120 --> 00:07:30.430 align:start position:0% and so the the only information she needs<00:07:28.440> is<00:07:28.639> that<00:07:29.080> there<00:07:29.240> is<00:07:29.599> some<00:07:29.960> kind<00:07:30.160> of 00:07:30.430 --> 00:07:30.440 align:start position:0% needs is that there is some kind of 00:07:30.440 --> 00:07:32.790 align:start position:0% needs is that there is some kind of identity<00:07:31.039> here<00:07:31.479> and<00:07:31.800> I<00:07:31.960> got<00:07:32.160> paid<00:07:32.440> by<00:07:32.599> that 00:07:32.790 --> 00:07:32.800 align:start position:0% identity here and I got paid by that 00:07:32.800 --> 00:07:36.950 align:start position:0% identity here and I got paid by that identity<00:07:33.440> so<00:07:34.199> sometimes<00:07:35.000> this<00:07:35.120> is<00:07:35.400> all<00:07:35.639> that's 00:07:36.950 --> 00:07:36.960 align:start position:0% identity so sometimes this is all that's 00:07:36.960 --> 00:07:41.070 align:start position:0% identity so sometimes this is all that's needed<00:07:38.319> uh<00:07:39.319> most<00:07:39.560> of<00:07:39.720> the<00:07:39.919> time<00:07:40.319> though<00:07:40.759> you 00:07:41.070 --> 00:07:41.080 align:start position:0% needed uh most of the time though you 00:07:41.080 --> 00:07:44.950 align:start position:0% needed uh most of the time though you want<00:07:41.479> some<00:07:41.759> more<00:07:42.759> uh<00:07:43.000> information<00:07:43.919> so<00:07:44.680> what<00:07:44.840> we 00:07:44.950 --> 00:07:44.960 align:start position:0% want some more uh information so what we 00:07:44.960 --> 00:07:48.430 align:start position:0% want some more uh information so what we want<00:07:45.080> to<00:07:45.199> try<00:07:45.479> and<00:07:45.680> do<00:07:46.199> is<00:07:47.199> tie<00:07:47.800> some<00:07:48.120> data 00:07:48.430 --> 00:07:48.440 align:start position:0% want to try and do is tie some data 00:07:48.440 --> 00:07:52.270 align:start position:0% want to try and do is tie some data cryptographically<00:07:49.199> to<00:07:49.440> this<00:07:49.960> key<00:07:50.960> and<00:07:51.840> we<00:07:52.039> can 00:07:52.270 --> 00:07:52.280 align:start position:0% cryptographically to this key and we can 00:07:52.280 --> 00:07:55.430 align:start position:0% cryptographically to this key and we can do<00:07:52.599> so<00:07:53.280> using<00:07:54.280> uh<00:07:54.440> smart 00:07:55.430 --> 00:07:55.440 align:start position:0% do so using uh smart 00:07:55.440 --> 00:07:58.469 align:start position:0% do so using uh smart contracts<00:07:56.440> or<00:07:56.720> in<00:07:56.919> other<00:07:57.199> systems<00:07:58.159> uh<00:07:58.360> you 00:07:58.469 --> 00:07:58.479 align:start position:0% contracts or in other systems uh you 00:07:58.479 --> 00:08:00.550 align:start position:0% contracts or in other systems uh you might<00:07:58.639> be<00:07:58.720> able<00:07:58.919> to<00:07:59.000> do<00:07:59.159> it<00:07:59.720> using<00:08:00.159> digital 00:08:00.550 --> 00:08:00.560 align:start position:0% might be able to do it using digital 00:08:00.560 --> 00:08:05.029 align:start position:0% might be able to do it using digital signatures<00:08:01.479> so<00:08:02.479> some<00:08:03.000> basic<00:08:03.440> stuff<00:08:03.800> we<00:08:03.960> can<00:08:04.840> we 00:08:05.029 --> 00:08:05.039 align:start position:0% signatures so some basic stuff we can we 00:08:05.039 --> 00:08:09.270 align:start position:0% signatures so some basic stuff we can we can<00:08:05.720> attribute<00:08:06.720> to<00:08:07.080> the<00:08:07.479> to<00:08:07.639> the<00:08:07.800> key<00:08:08.159> is<00:08:09.000> uh<00:08:09.120> a 00:08:09.270 --> 00:08:09.280 align:start position:0% can attribute to the to the key is uh a 00:08:09.280 --> 00:08:14.149 align:start position:0% can attribute to the to the key is uh a name<00:08:09.879> maybe<00:08:10.240> a<00:08:10.520> profile<00:08:11.120> picture<00:08:12.120> email<00:08:13.159> Etc 00:08:14.149 --> 00:08:14.159 align:start position:0% name maybe a profile picture email Etc 00:08:14.159 --> 00:08:17.230 align:start position:0% name maybe a profile picture email Etc uh<00:08:14.440> in<00:08:15.360> cases<00:08:15.720> of<00:08:15.960> Corporations<00:08:16.840> you<00:08:17.039> might 00:08:17.230 --> 00:08:17.240 align:start position:0% uh in cases of Corporations you might 00:08:17.240 --> 00:08:22.029 align:start position:0% uh in cases of Corporations you might have<00:08:17.400> some<00:08:17.960> tax<00:08:18.440> information<00:08:19.560> Etc<00:08:20.560> uh<00:08:20.759> or<00:08:21.680> for 00:08:22.029 --> 00:08:22.039 align:start position:0% have some tax information Etc uh or for 00:08:22.039 --> 00:08:25.230 align:start position:0% have some tax information Etc uh or for the<00:08:22.759> balance<00:08:23.759> three<00:08:24.520> uh<00:08:24.639> triple<00:08:24.960> entry 00:08:25.230 --> 00:08:25.240 align:start position:0% the balance three uh triple entry 00:08:25.240 --> 00:08:27.270 align:start position:0% the balance three uh triple entry accounting<00:08:25.599> system<00:08:26.080> you<00:08:26.280> have<00:08:26.759> an<00:08:26.960> accounting 00:08:27.270 --> 00:08:27.280 align:start position:0% accounting system you have an accounting 00:08:27.280 --> 00:08:30.029 align:start position:0% accounting system you have an accounting Ledger<00:08:28.120> that's<00:08:28.400> attached<00:08:28.800> to<00:08:29.000> your<00:08:29.199> to<00:08:29.560> your 00:08:30.029 --> 00:08:30.039 align:start position:0% Ledger that's attached to your to your 00:08:30.039 --> 00:08:32.630 align:start position:0% Ledger that's attached to your to your digital<00:08:30.720> identity<00:08:31.720> uh<00:08:31.879> here<00:08:32.039> we<00:08:32.200> could<00:08:32.399> also 00:08:32.630 --> 00:08:32.640 align:start position:0% digital identity uh here we could also 00:08:32.640 --> 00:08:35.870 align:start position:0% digital identity uh here we could also bootstrap<00:08:33.320> other<00:08:33.560> services<00:08:34.240> so<00:08:34.399> you<00:08:34.519> can<00:08:35.279> uh 00:08:35.870 --> 00:08:35.880 align:start position:0% bootstrap other services so you can uh 00:08:35.880 --> 00:08:39.589 align:start position:0% bootstrap other services so you can uh you<00:08:36.039> can<00:08:36.680> attri<00:08:37.479> you<00:08:37.560> can<00:08:37.680> have<00:08:37.800> an<00:08:38.080> attribute 00:08:39.589 --> 00:08:39.599 align:start position:0% you can attri you can have an attribute 00:08:39.599 --> 00:08:42.630 align:start position:0% you can attri you can have an attribute attribute<00:08:40.599> attribute<00:08:41.360> yeah<00:08:41.560> that's<00:08:41.839> one<00:08:42.479> you 00:08:42.630 --> 00:08:42.640 align:start position:0% attribute attribute yeah that's one you 00:08:42.640 --> 00:08:45.550 align:start position:0% attribute attribute yeah that's one you you<00:08:42.719> can<00:08:42.880> have<00:08:43.000> an<00:08:43.159> attribute<00:08:43.719> which<00:08:43.959> is<00:08:44.560> your 00:08:45.550 --> 00:08:45.560 align:start position:0% you can have an attribute which is your 00:08:45.560 --> 00:08:48.190 align:start position:0% you can have an attribute which is your uh<00:08:45.920> Twitter<00:08:46.399> account<00:08:46.760> your<00:08:47.000> Facebook<00:08:47.519> account 00:08:48.190 --> 00:08:48.200 align:start position:0% uh Twitter account your Facebook account 00:08:48.200 --> 00:08:49.269 align:start position:0% uh Twitter account your Facebook account GitHub 00:08:49.269 --> 00:08:49.279 align:start position:0% GitHub 00:08:49.279 --> 00:08:52.829 align:start position:0% GitHub Etc<00:08:50.279> um<00:08:50.720> so<00:08:51.600> here<00:08:51.839> is<00:08:52.080> kind<00:08:52.200> of<00:08:52.399> what<00:08:52.519> it<00:08:52.640> can 00:08:52.829 --> 00:08:52.839 align:start position:0% Etc um so here is kind of what it can 00:08:52.839 --> 00:08:56.269 align:start position:0% Etc um so here is kind of what it can look<00:08:53.320> like<00:08:54.320> do<00:08:54.480> we<00:08:54.600> have<00:08:54.760> the<00:08:54.920> laser<00:08:55.440> thing<00:08:55.800> is 00:08:56.269 --> 00:08:56.279 align:start position:0% look like do we have the laser thing is 00:08:56.279 --> 00:09:00.630 align:start position:0% look like do we have the laser thing is this<00:08:57.279> no<00:08:58.120> anyway<00:08:58.839> I'll<00:08:59.000> just<00:08:59.160> point<00:08:59.880> um<00:09:00.320> so<00:09:00.519> we 00:09:00.630 --> 00:09:00.640 align:start position:0% this no anyway I'll just point um so we 00:09:00.640 --> 00:09:02.670 align:start position:0% this no anyway I'll just point um so we have<00:09:00.839> this<00:09:01.040> public<00:09:01.399> key<00:09:02.079> which<00:09:02.200> is<00:09:02.360> kind<00:09:02.480> of 00:09:02.670 --> 00:09:02.680 align:start position:0% have this public key which is kind of 00:09:02.680 --> 00:09:04.910 align:start position:0% have this public key which is kind of the<00:09:02.880> core<00:09:03.760> of<00:09:04.040> of<00:09:04.240> the 00:09:04.910 --> 00:09:04.920 align:start position:0% the core of of the 00:09:04.920 --> 00:09:07.630 align:start position:0% the core of of the identity<00:09:05.920> uh<00:09:06.480> the<00:09:06.720> corresponding<00:09:07.279> private 00:09:07.630 --> 00:09:07.640 align:start position:0% identity uh the corresponding private 00:09:07.640 --> 00:09:10.990 align:start position:0% identity uh the corresponding private key<00:09:07.920> can<00:09:08.279> can<00:09:08.560> create<00:09:09.120> and<00:09:09.440> control<00:09:10.440> a<00:09:10.600> smart 00:09:10.990 --> 00:09:11.000 align:start position:0% key can can create and control a smart 00:09:11.000 --> 00:09:13.310 align:start position:0% key can can create and control a smart contract<00:09:11.720> that<00:09:12.120> that<00:09:12.399> contains<00:09:13.120> the 00:09:13.310 --> 00:09:13.320 align:start position:0% contract that that contains the 00:09:13.320 --> 00:09:15.389 align:start position:0% contract that that contains the attributes<00:09:14.000> so<00:09:14.480> the<00:09:14.640> attributes<00:09:15.079> could<00:09:15.240> be 00:09:15.389 --> 00:09:15.399 align:start position:0% attributes so the attributes could be 00:09:15.399 --> 00:09:17.230 align:start position:0% attributes so the attributes could be stored<00:09:15.680> on<00:09:15.760> the<00:09:15.880> blockchain<00:09:16.320> but<00:09:16.480> normally<00:09:17.000> we 00:09:17.230 --> 00:09:17.240 align:start position:0% stored on the blockchain but normally we 00:09:17.240 --> 00:09:21.230 align:start position:0% stored on the blockchain but normally we we<00:09:17.399> use<00:09:17.800> a<00:09:18.040> system<00:09:18.440> like<00:09:19.160> ipfs<00:09:20.160> that<00:09:20.519> Juan 00:09:21.230 --> 00:09:21.240 align:start position:0% we use a system like ipfs that Juan 00:09:21.240 --> 00:09:25.630 align:start position:0% we use a system like ipfs that Juan mentioned<00:09:22.240> uh<00:09:22.560> and<00:09:22.800> we<00:09:22.920> can<00:09:23.440> have<00:09:24.440> hashes<00:09:25.440> that 00:09:25.630 --> 00:09:25.640 align:start position:0% mentioned uh and we can have hashes that 00:09:25.640 --> 00:09:30.949 align:start position:0% mentioned uh and we can have hashes that that<00:09:25.839> corresponds<00:09:26.560> to<00:09:27.160> uh<00:09:27.480> to<00:09:27.920> objects<00:09:28.760> and<00:09:29.600> in 00:09:30.949 --> 00:09:30.959 align:start position:0% that corresponds to uh to objects and in 00:09:30.959 --> 00:09:33.590 align:start position:0% that corresponds to uh to objects and in ipfs<00:09:31.959> um<00:09:32.320> a<00:09:32.519> second<00:09:32.800> thing<00:09:33.000> that<00:09:33.120> we<00:09:33.240> want<00:09:33.360> to 00:09:33.590 --> 00:09:33.600 align:start position:0% ipfs um a second thing that we want to 00:09:33.600 --> 00:09:35.230 align:start position:0% ipfs um a second thing that we want to have<00:09:33.920> is 00:09:35.230 --> 00:09:35.240 align:start position:0% have is 00:09:35.240 --> 00:09:38.430 align:start position:0% have is attestations<00:09:36.240> so<00:09:36.480> what<00:09:36.640> this<00:09:36.800> is<00:09:37.120> that<00:09:38.040> we<00:09:38.240> can 00:09:38.430 --> 00:09:38.440 align:start position:0% attestations so what this is that we can 00:09:38.440 --> 00:09:39.829 align:start position:0% attestations so what this is that we can let<00:09:38.760> other 00:09:39.829 --> 00:09:39.839 align:start position:0% let other 00:09:39.839 --> 00:09:42.949 align:start position:0% let other identities<00:09:40.839> attest<00:09:41.360> to<00:09:41.560> the<00:09:41.720> validity<00:09:42.360> of<00:09:42.720> the 00:09:42.949 --> 00:09:42.959 align:start position:0% identities attest to the validity of the 00:09:42.959 --> 00:09:45.670 align:start position:0% identities attest to the validity of the attributes<00:09:43.680> that<00:09:43.800> you<00:09:44.440> uh<00:09:44.600> connected<00:09:45.079> to<00:09:45.360> your 00:09:45.670 --> 00:09:45.680 align:start position:0% attributes that you uh connected to your 00:09:45.680 --> 00:09:50.069 align:start position:0% attributes that you uh connected to your public<00:09:46.399> key<00:09:47.399> uh<00:09:47.800> this<00:09:48.800> can<00:09:49.079> lend<00:09:49.440> credibility 00:09:50.069 --> 00:09:50.079 align:start position:0% public key uh this can lend credibility 00:09:50.079 --> 00:09:52.790 align:start position:0% public key uh this can lend credibility to<00:09:50.279> the<00:09:50.640> attributes<00:09:51.640> uh<00:09:52.000> while<00:09:52.240> at<00:09:52.360> the<00:09:52.480> same 00:09:52.790 --> 00:09:52.800 align:start position:0% to the attributes uh while at the same 00:09:52.800 --> 00:09:55.949 align:start position:0% to the attributes uh while at the same time<00:09:53.760> letting<00:09:54.160> the<00:09:54.320> user<00:09:55.200> have<00:09:55.440> control<00:09:55.800> of 00:09:55.949 --> 00:09:55.959 align:start position:0% time letting the user have control of 00:09:55.959 --> 00:09:58.030 align:start position:0% time letting the user have control of their<00:09:56.079> own<00:09:56.360> identities<00:09:57.040> so<00:09:57.600> this<00:09:57.760> could<00:09:57.880> be 00:09:58.030 --> 00:09:58.040 align:start position:0% their own identities so this could be 00:09:58.040 --> 00:10:01.069 align:start position:0% their own identities so this could be for<00:09:58.200> instance<00:09:58.680> a<00:09:59.040> a<00:09:59.440> government<00:10:00.440> verifying 00:10:01.069 --> 00:10:01.079 align:start position:0% for instance a a government verifying 00:10:01.079 --> 00:10:05.150 align:start position:0% for instance a a government verifying your<00:10:01.320> date<00:10:01.480> of<00:10:01.640> birth<00:10:02.279> so<00:10:03.279> you<00:10:04.120> yourself<00:10:04.800> claim 00:10:05.150 --> 00:10:05.160 align:start position:0% your date of birth so you yourself claim 00:10:05.160 --> 00:10:07.670 align:start position:0% your date of birth so you yourself claim that<00:10:05.320> your<00:10:05.440> date<00:10:05.600> of<00:10:05.760> birth<00:10:06.079> is<00:10:06.920> uh<00:10:07.120> January 00:10:07.670 --> 00:10:07.680 align:start position:0% that your date of birth is uh January 00:10:07.680 --> 00:10:08.829 align:start position:0% that your date of birth is uh January 1st 00:10:08.829 --> 00:10:08.839 align:start position:0% 1st 00:10:08.839 --> 00:10:11.230 align:start position:0% 1st 1980<00:10:09.839> and<00:10:10.079> the<00:10:10.240> government<00:10:10.640> can<00:10:10.800> come<00:10:10.959> in<00:10:11.079> and 00:10:11.230 --> 00:10:11.240 align:start position:0% 1980 and the government can come in and 00:10:11.240 --> 00:10:14.550 align:start position:0% 1980 and the government can come in and say<00:10:12.000> yes<00:10:12.399> we<00:10:12.839> we<00:10:13.279> verify<00:10:13.760> that<00:10:13.959> this<00:10:14.079> is<00:10:14.240> true 00:10:14.550 --> 00:10:14.560 align:start position:0% say yes we we verify that this is true 00:10:14.560 --> 00:10:16.590 align:start position:0% say yes we we verify that this is true because<00:10:14.760> we<00:10:14.880> saw<00:10:15.160> the<00:10:15.760> the<00:10:15.920> birth<00:10:16.160> record<00:10:16.440> or 00:10:16.590 --> 00:10:16.600 align:start position:0% because we saw the the birth record or 00:10:16.600 --> 00:10:17.990 align:start position:0% because we saw the the birth record or something<00:10:16.920> and<00:10:17.040> they<00:10:17.160> can<00:10:17.279> do<00:10:17.440> a<00:10:17.640> digital 00:10:17.990 --> 00:10:18.000 align:start position:0% something and they can do a digital 00:10:18.000 --> 00:10:21.430 align:start position:0% something and they can do a digital signature<00:10:19.000> and<00:10:19.200> now<00:10:19.480> you<00:10:19.800> have<00:10:20.760> uh<00:10:21.079> on<00:10:21.279> the 00:10:21.430 --> 00:10:21.440 align:start position:0% signature and now you have uh on the 00:10:21.440 --> 00:10:23.190 align:start position:0% signature and now you have uh on the blockchain<00:10:21.959> a<00:10:22.160> very 00:10:23.190 --> 00:10:23.200 align:start position:0% blockchain a very 00:10:23.200 --> 00:10:28.230 align:start position:0% blockchain a very strong<00:10:24.240> um<00:10:25.240> a<00:10:25.720> very<00:10:26.279> strong<00:10:27.240> certificate<00:10:28.120> if 00:10:28.230 --> 00:10:28.240 align:start position:0% strong um a very strong certificate if 00:10:28.240 --> 00:10:30.949 align:start position:0% strong um a very strong certificate if you<00:10:28.360> will<00:10:28.839> that<00:10:29.120> that<00:10:29.480> this<00:10:30.040> is<00:10:30.320> correct<00:10:30.839> at 00:10:30.949 --> 00:10:30.959 align:start position:0% you will that that this is correct at 00:10:30.959 --> 00:10:32.509 align:start position:0% you will that that this is correct at least<00:10:31.160> according<00:10:31.440> to<00:10:31.600> this<00:10:31.800> government 00:10:32.509 --> 00:10:32.519 align:start position:0% least according to this government 00:10:32.519 --> 00:10:35.550 align:start position:0% least according to this government another<00:10:32.839> one<00:10:33.040> is<00:10:33.360> is<00:10:33.920> uh<00:10:34.079> in<00:10:34.200> the<00:10:34.399> banks<00:10:35.399> uh 00:10:35.550 --> 00:10:35.560 align:start position:0% another one is is uh in the banks uh 00:10:35.560 --> 00:10:38.069 align:start position:0% another one is is uh in the banks uh they<00:10:35.680> can<00:10:35.959> verify<00:10:36.560> that<00:10:36.760> you<00:10:37.040> have<00:10:37.800> an 00:10:38.069 --> 00:10:38.079 align:start position:0% they can verify that you have an 00:10:38.079 --> 00:10:41.190 align:start position:0% they can verify that you have an accredited<00:10:38.639> investor<00:10:39.600> status<00:10:40.600> and<00:10:40.839> so<00:10:41.079> this 00:10:41.190 --> 00:10:41.200 align:start position:0% accredited investor status and so this 00:10:41.200 --> 00:10:43.509 align:start position:0% accredited investor status and so this means<00:10:41.440> you<00:10:41.600> have<00:10:41.720> to<00:10:41.880> have<00:10:42.600> more<00:10:42.839> than 00:10:43.509 --> 00:10:43.519 align:start position:0% means you have to have more than 00:10:43.519 --> 00:10:45.910 align:start position:0% means you have to have more than $250,000<00:10:44.519> in<00:10:44.639> an<00:10:44.839> account<00:10:45.120> or<00:10:45.399> something<00:10:45.680> like 00:10:45.910 --> 00:10:45.920 align:start position:0% $250,000 in an account or something like 00:10:45.920 --> 00:10:50.350 align:start position:0% $250,000 in an account or something like this<00:10:46.680> um<00:10:47.639> more<00:10:47.920> advanced<00:10:48.560> is<00:10:49.040> uh<00:10:49.240> reputational 00:10:50.350 --> 00:10:50.360 align:start position:0% this um more advanced is uh reputational 00:10:50.360 --> 00:10:53.030 align:start position:0% this um more advanced is uh reputational attestations<00:10:51.360> which<00:10:51.519> we'll<00:10:51.839> hear<00:10:52.639> uh<00:10:52.800> more 00:10:53.030 --> 00:10:53.040 align:start position:0% attestations which we'll hear uh more 00:10:53.040 --> 00:10:55.509 align:start position:0% attestations which we'll hear uh more about<00:10:53.560> later<00:10:54.320> by 00:10:55.509 --> 00:10:55.519 align:start position:0% about later by 00:10:55.519 --> 00:10:59.069 align:start position:0% about later by Andre<00:10:56.519> uh<00:10:56.839> so<00:10:57.320> this<00:10:57.480> would<00:10:57.760> be<00:10:58.560> you<00:10:58.680> know<00:10:58.880> not 00:10:59.069 --> 00:10:59.079 align:start position:0% Andre uh so this would be you know not 00:10:59.079 --> 00:11:00.790 align:start position:0% Andre uh so this would be you know not just<00:10:59.519> saying<00:10:59.839> that<00:11:00.040> this<00:11:00.200> information<00:11:00.600> is 00:11:00.790 --> 00:11:00.800 align:start position:0% just saying that this information is 00:11:00.800 --> 00:11:03.509 align:start position:0% just saying that this information is correct<00:11:01.120> or<00:11:01.279> not<00:11:01.560> but<00:11:01.920> kind<00:11:02.040> of<00:11:02.360> like<00:11:03.200> you<00:11:03.320> know 00:11:03.509 --> 00:11:03.519 align:start position:0% correct or not but kind of like you know 00:11:03.519 --> 00:11:07.069 align:start position:0% correct or not but kind of like you know more<00:11:03.800> fuzzy<00:11:04.279> things<00:11:04.639> like<00:11:04.880> I<00:11:05.440> bought<00:11:06.440> uh<00:11:06.639> socks 00:11:07.069 --> 00:11:07.079 align:start position:0% more fuzzy things like I bought uh socks 00:11:07.079 --> 00:11:09.590 align:start position:0% more fuzzy things like I bought uh socks from<00:11:07.360> this<00:11:07.600> person<00:11:08.320> and<00:11:08.560> it<00:11:08.680> was<00:11:08.959> good<00:11:09.279> so<00:11:09.480> I 00:11:09.590 --> 00:11:09.600 align:start position:0% from this person and it was good so I 00:11:09.600 --> 00:11:12.990 align:start position:0% from this person and it was good so I get<00:11:09.839> five<00:11:10.480> stars<00:11:11.480> um<00:11:11.880> so<00:11:12.120> this<00:11:12.240> is<00:11:12.639> what<00:11:12.760> it<00:11:12.839> can 00:11:12.990 --> 00:11:13.000 align:start position:0% get five stars um so this is what it can 00:11:13.000 --> 00:11:15.990 align:start position:0% get five stars um so this is what it can look<00:11:13.200> like<00:11:13.399> in<00:11:13.600> in<00:11:14.000> that<00:11:15.000> case<00:11:15.480> you<00:11:15.600> know<00:11:15.800> you 00:11:15.990 --> 00:11:16.000 align:start position:0% look like in in that case you know you 00:11:16.000 --> 00:11:17.990 align:start position:0% look like in in that case you know you have<00:11:16.600> two<00:11:16.839> of<00:11:17.040> these 00:11:17.990 --> 00:11:18.000 align:start position:0% have two of these 00:11:18.000 --> 00:11:23.430 align:start position:0% have two of these identities<00:11:19.399> and<00:11:20.399> uh<00:11:21.399> the<00:11:21.600> first<00:11:21.880> one<00:11:22.360> has<00:11:22.600> some 00:11:23.430 --> 00:11:23.440 align:start position:0% identities and uh the first one has some 00:11:23.440 --> 00:11:25.269 align:start position:0% identities and uh the first one has some this<00:11:23.560> one<00:11:23.760> has<00:11:23.920> two<00:11:24.160> attributes<00:11:24.800> that<00:11:24.920> one<00:11:25.120> has 00:11:25.269 --> 00:11:25.279 align:start position:0% this one has two attributes that one has 00:11:25.279 --> 00:11:27.150 align:start position:0% this one has two attributes that one has one<00:11:25.480> attribute<00:11:26.320> and<00:11:26.480> one<00:11:26.680> can<00:11:26.839> do<00:11:27.000> an 00:11:27.150 --> 00:11:27.160 align:start position:0% one attribute and one can do an 00:11:27.160 --> 00:11:29.470 align:start position:0% one attribute and one can do an attestation<00:11:27.760> of<00:11:27.959> the<00:11:28.079> other<00:11:28.639> so<00:11:28.800> it's<00:11:29.000> it's<00:11:29.360> a 00:11:29.470 --> 00:11:29.480 align:start position:0% attestation of the other so it's it's a 00:11:29.480 --> 00:11:32.949 align:start position:0% attestation of the other so it's it's a very<00:11:30.160> abstract<00:11:30.920> concept<00:11:31.920> but<00:11:32.160> in<00:11:32.360> general<00:11:32.760> you 00:11:32.949 --> 00:11:32.959 align:start position:0% very abstract concept but in general you 00:11:32.959 --> 00:11:36.069 align:start position:0% very abstract concept but in general you get<00:11:33.399> things<00:11:33.760> like<00:11:34.480> you<00:11:34.600> know<00:11:35.079> certified 00:11:36.069 --> 00:11:36.079 align:start position:0% get things like you know certified 00:11:36.079 --> 00:11:38.629 align:start position:0% get things like you know certified things<00:11:36.600> by<00:11:36.839> authorities<00:11:37.760> but<00:11:37.920> you<00:11:38.079> also<00:11:38.440> have 00:11:38.629 --> 00:11:38.639 align:start position:0% things by authorities but you also have 00:11:38.639 --> 00:11:42.110 align:start position:0% things by authorities but you also have the<00:11:38.800> notion<00:11:39.200> of<00:11:39.560> of<00:11:40.320> web<00:11:40.600> of<00:11:40.839> trust<00:11:41.720> where<00:11:42.000> you 00:11:42.110 --> 00:11:42.120 align:start position:0% the notion of of web of trust where you 00:11:42.120 --> 00:11:46.790 align:start position:0% the notion of of web of trust where you can<00:11:42.880> build<00:11:44.040> um<00:11:45.040> you<00:11:45.279> can<00:11:45.600> build<00:11:46.160> reputation 00:11:46.790 --> 00:11:46.800 align:start position:0% can build um you can build reputation 00:11:46.800 --> 00:11:49.110 align:start position:0% can build um you can build reputation Etc<00:11:47.200> from<00:11:47.320> the<00:11:47.480> attestation<00:11:48.160> of<00:11:48.360> of<00:11:48.519> your 00:11:49.110 --> 00:11:49.120 align:start position:0% Etc from the attestation of of your 00:11:49.120 --> 00:11:53.430 align:start position:0% Etc from the attestation of of your friends<00:11:50.120> um<00:11:50.839> so<00:11:51.120> this<00:11:51.560> is<00:11:52.560> you<00:11:52.720> know<00:11:53.279> this 00:11:53.430 --> 00:11:53.440 align:start position:0% friends um so this is you know this 00:11:53.440 --> 00:11:57.550 align:start position:0% friends um so this is you know this sounds<00:11:53.800> pretty<00:11:54.240> good<00:11:55.240> uh<00:11:55.880> there's<00:11:56.160> a<00:11:57.160> big 00:11:57.550 --> 00:11:57.560 align:start position:0% sounds pretty good uh there's a big 00:11:57.560 --> 00:12:00.110 align:start position:0% sounds pretty good uh there's a big problem<00:11:58.040> though<00:11:58.560> and<00:11:59.079> it's<00:11:59.279> it's<00:11:59.959> the 00:12:00.110 --> 00:12:00.120 align:start position:0% problem though and it's it's the 00:12:00.120 --> 00:12:03.430 align:start position:0% problem though and it's it's the following<00:12:00.680> that<00:12:01.079> vitalic<00:12:02.000> brought<00:12:02.360> up<00:12:03.000> uh 00:12:03.430 --> 00:12:03.440 align:start position:0% following that vitalic brought up uh 00:12:03.440 --> 00:12:06.910 align:start position:0% following that vitalic brought up uh during<00:12:04.120> the<00:12:04.800> uh<00:12:05.240> uh<00:12:05.399> web<00:12:05.639> of<00:12:05.800> trust<00:12:06.200> conference 00:12:06.910 --> 00:12:06.920 align:start position:0% during the uh uh web of trust conference 00:12:06.920 --> 00:12:10.110 align:start position:0% during the uh uh web of trust conference in<00:12:07.240> in<00:12:07.399> San<00:12:08.000> Francisco<00:12:09.000> and 00:12:10.110 --> 00:12:10.120 align:start position:0% in in San Francisco and 00:12:10.120 --> 00:12:12.670 align:start position:0% in in San Francisco and and<00:12:11.120> the<00:12:11.279> thing<00:12:11.560> is<00:12:12.000> you<00:12:12.120> know<00:12:12.320> what<00:12:12.480> if<00:12:12.560> you 00:12:12.670 --> 00:12:12.680 align:start position:0% and the thing is you know what if you 00:12:12.680 --> 00:12:13.829 align:start position:0% and the thing is you know what if you lose<00:12:12.880> your<00:12:13.040> private 00:12:13.829 --> 00:12:13.839 align:start position:0% lose your private 00:12:13.839 --> 00:12:18.750 align:start position:0% lose your private key<00:12:15.279> and<00:12:16.279> you<00:12:16.600> kind<00:12:16.800> of<00:12:17.480> don't<00:12:17.760> want<00:12:17.959> a<00:12:18.199> system 00:12:18.750 --> 00:12:18.760 align:start position:0% key and you kind of don't want a system 00:12:18.760 --> 00:12:21.310 align:start position:0% key and you kind of don't want a system where<00:12:19.240> if<00:12:19.360> you<00:12:19.519> lose<00:12:19.800> your<00:12:19.959> private<00:12:20.320> key<00:12:21.120> which 00:12:21.310 --> 00:12:21.320 align:start position:0% where if you lose your private key which 00:12:21.320 --> 00:12:23.790 align:start position:0% where if you lose your private key which people<00:12:21.560> do<00:12:21.800> all<00:12:21.959> the<00:12:22.320> time<00:12:23.320> H<00:12:23.440> you<00:12:23.560> don't<00:12:23.680> want 00:12:23.790 --> 00:12:23.800 align:start position:0% people do all the time H you don't want 00:12:23.800 --> 00:12:26.990 align:start position:0% people do all the time H you don't want to<00:12:24.000> lose<00:12:24.440> your<00:12:25.040> identity<00:12:26.040> because<00:12:26.360> that's<00:12:26.839> you 00:12:26.990 --> 00:12:27.000 align:start position:0% to lose your identity because that's you 00:12:27.000 --> 00:12:29.710 align:start position:0% to lose your identity because that's you know<00:12:27.240> that's<00:12:27.600> too<00:12:27.880> much<00:12:28.279> to 00:12:29.710 --> 00:12:29.720 align:start position:0% know that's too much to 00:12:29.720 --> 00:12:32.629 align:start position:0% know that's too much to uh<00:12:29.920> too<00:12:30.160> much<00:12:31.040> power<00:12:31.360> to<00:12:31.560> put<00:12:31.800> in<00:12:31.959> in<00:12:32.160> this<00:12:32.320> one 00:12:32.629 --> 00:12:32.639 align:start position:0% uh too much power to put in in this one 00:12:32.639 --> 00:12:36.829 align:start position:0% uh too much power to put in in this one thing<00:12:33.560> um<00:12:34.920> so<00:12:35.920> we<00:12:36.079> need<00:12:36.240> to<00:12:36.399> be<00:12:36.519> able<00:12:36.680> to 00:12:36.829 --> 00:12:36.839 align:start position:0% thing um so we need to be able to 00:12:36.839 --> 00:12:40.710 align:start position:0% thing um so we need to be able to recover<00:12:37.360> from<00:12:37.720> Key<00:12:38.000> loss<00:12:38.760> which<00:12:38.959> is<00:12:39.760> I<00:12:39.920> have<00:12:40.160> my 00:12:40.710 --> 00:12:40.720 align:start position:0% recover from Key loss which is I have my 00:12:40.720 --> 00:12:43.069 align:start position:0% recover from Key loss which is I have my key<00:12:40.920> on<00:12:41.079> my<00:12:41.240> phone<00:12:41.560> I<00:12:41.680> lose<00:12:41.959> my<00:12:42.120> phone<00:12:42.800> what<00:12:42.959> do 00:12:43.069 --> 00:12:43.079 align:start position:0% key on my phone I lose my phone what do 00:12:43.079 --> 00:12:47.470 align:start position:0% key on my phone I lose my phone what do I<00:12:43.199> do<00:12:43.480> and<00:12:43.680> key<00:12:44.040> compromise<00:12:44.880> which<00:12:45.360> is<00:12:46.360> uh<00:12:46.920> some 00:12:47.470 --> 00:12:47.480 align:start position:0% I do and key compromise which is uh some 00:12:47.480 --> 00:12:50.389 align:start position:0% I do and key compromise which is uh some attacker<00:12:48.360> gets<00:12:48.639> my<00:12:48.880> key<00:12:49.199> and<00:12:49.399> starts<00:12:50.040> acting 00:12:50.389 --> 00:12:50.399 align:start position:0% attacker gets my key and starts acting 00:12:50.399 --> 00:12:51.990 align:start position:0% attacker gets my key and starts acting in<00:12:50.600> my 00:12:51.990 --> 00:12:52.000 align:start position:0% in my 00:12:52.000 --> 00:12:56.189 align:start position:0% in my name<00:12:53.040> so<00:12:54.040> how<00:12:54.160> do<00:12:54.320> we<00:12:54.480> do<00:12:54.839> this 00:12:56.189 --> 00:12:56.199 align:start position:0% name so how do we do this 00:12:56.199 --> 00:12:59.790 align:start position:0% name so how do we do this well<00:12:57.199> uh<00:12:57.800> the<00:12:58.399> the<00:12:58.600> way<00:12:58.920> that<00:12:59.360> the<00:12:59.519> we've 00:12:59.790 --> 00:12:59.800 align:start position:0% well uh the the way that the we've 00:12:59.800 --> 00:13:01.990 align:start position:0% well uh the the way that the we've approached<00:13:00.199> it<00:13:00.519> is<00:13:01.079> we<00:13:01.199> want<00:13:01.399> to<00:13:01.519> allow<00:13:01.839> the 00:13:01.990 --> 00:13:02.000 align:start position:0% approached it is we want to allow the 00:13:02.000 --> 00:13:06.710 align:start position:0% approached it is we want to allow the user<00:13:02.560> to<00:13:03.560> uh<00:13:03.959> revoke<00:13:04.560> and<00:13:04.800> replace<00:13:05.279> a<00:13:05.519> key<00:13:06.440> that 00:13:06.710 --> 00:13:06.720 align:start position:0% user to uh revoke and replace a key that 00:13:06.720 --> 00:13:10.550 align:start position:0% user to uh revoke and replace a key that they<00:13:07.279> suspect<00:13:08.040> might<00:13:08.279> be<00:13:09.240> uh<00:13:09.480> compromised<00:13:10.320> so 00:13:10.550 --> 00:13:10.560 align:start position:0% they suspect might be uh compromised so 00:13:10.560 --> 00:13:12.790 align:start position:0% they suspect might be uh compromised so let's<00:13:10.720> say<00:13:10.920> I<00:13:11.040> lose<00:13:11.399> my<00:13:11.560> phone<00:13:12.199> but<00:13:12.360> I<00:13:12.480> have<00:13:12.600> a 00:13:12.790 --> 00:13:12.800 align:start position:0% let's say I lose my phone but I have a 00:13:12.800 --> 00:13:15.310 align:start position:0% let's say I lose my phone but I have a backup<00:13:13.560> okay<00:13:13.760> someone<00:13:14.160> could<00:13:14.399> maybe<00:13:14.680> find<00:13:15.000> my 00:13:15.310 --> 00:13:15.320 align:start position:0% backup okay someone could maybe find my 00:13:15.320 --> 00:13:18.189 align:start position:0% backup okay someone could maybe find my phone<00:13:16.199> and<00:13:16.480> get<00:13:16.720> that<00:13:16.959> key<00:13:17.360> so<00:13:17.639> I<00:13:17.720> want<00:13:17.839> to<00:13:18.040> make 00:13:18.189 --> 00:13:18.199 align:start position:0% phone and get that key so I want to make 00:13:18.199 --> 00:13:20.750 align:start position:0% phone and get that key so I want to make sure<00:13:19.040> I<00:13:19.240> replace<00:13:19.720> that<00:13:19.880> key<00:13:20.040> so<00:13:20.240> they<00:13:20.399> can't 00:13:20.750 --> 00:13:20.760 align:start position:0% sure I replace that key so they can't 00:13:20.760 --> 00:13:24.030 align:start position:0% sure I replace that key so they can't start<00:13:21.079> acting<00:13:21.360> in<00:13:21.519> my<00:13:21.880> name<00:13:22.880> um<00:13:23.240> and<00:13:23.440> then<00:13:23.720> if<00:13:23.839> I 00:13:24.030 --> 00:13:24.040 align:start position:0% start acting in my name um and then if I 00:13:24.040 --> 00:13:25.710 align:start position:0% start acting in my name um and then if I lose<00:13:24.680> complete 00:13:25.710 --> 00:13:25.720 align:start position:0% lose complete 00:13:25.720 --> 00:13:30.949 align:start position:0% lose complete control<00:13:26.720> I<00:13:26.880> could<00:13:27.160> have<00:13:27.760> a<00:13:28.760> uh<00:13:29.519> a<00:13:30.240> smart 00:13:30.949 --> 00:13:30.959 align:start position:0% control I could have a uh a smart 00:13:30.959 --> 00:13:33.910 align:start position:0% control I could have a uh a smart contract<00:13:31.959> that<00:13:32.160> I<00:13:32.440> delegate<00:13:33.000> the<00:13:33.160> authority 00:13:33.910 --> 00:13:33.920 align:start position:0% contract that I delegate the authority 00:13:33.920 --> 00:13:38.470 align:start position:0% contract that I delegate the authority to<00:13:34.680> to<00:13:35.440> uh<00:13:35.920> regain<00:13:36.399> control<00:13:36.760> for<00:13:37.079> the<00:13:37.199> user<00:13:38.160> so 00:13:38.470 --> 00:13:38.480 align:start position:0% to to uh regain control for the user so 00:13:38.480 --> 00:13:41.069 align:start position:0% to to uh regain control for the user so a<00:13:38.720> specific<00:13:39.160> case<00:13:39.320> of<00:13:39.519> this<00:13:39.720> is<00:13:39.959> that<00:13:40.560> you<00:13:40.720> can 00:13:41.069 --> 00:13:41.079 align:start position:0% a specific case of this is that you can 00:13:41.079 --> 00:13:45.069 align:start position:0% a specific case of this is that you can have<00:13:41.760> a<00:13:42.399> multi-<00:13:43.320> setup<00:13:43.880> where<00:13:44.040> you<00:13:44.720> where<00:13:44.839> you 00:13:45.069 --> 00:13:45.079 align:start position:0% have a multi- setup where you where you 00:13:45.079 --> 00:13:47.110 align:start position:0% have a multi- setup where you where you have<00:13:45.320> three<00:13:45.519> of<00:13:45.639> your<00:13:45.839> friends<00:13:46.600> and<00:13:46.760> then<00:13:46.920> two 00:13:47.110 --> 00:13:47.120 align:start position:0% have three of your friends and then two 00:13:47.120 --> 00:13:50.749 align:start position:0% have three of your friends and then two of<00:13:47.279> them<00:13:47.399> are<00:13:47.560> needed<00:13:47.920> to<00:13:48.360> to<00:13:49.079> regain<00:13:50.079> uh 00:13:50.749 --> 00:13:50.759 align:start position:0% of them are needed to to regain uh 00:13:50.759 --> 00:13:54.030 align:start position:0% of them are needed to to regain uh control<00:13:51.759> for<00:13:52.079> me<00:13:52.440> so<00:13:52.759> so<00:13:53.000> they<00:13:53.160> would 00:13:54.030 --> 00:13:54.040 align:start position:0% control for me so so they would 00:13:54.040 --> 00:13:57.990 align:start position:0% control for me so so they would basically<00:13:55.040> uh<00:13:55.399> be<00:13:55.600> able<00:13:55.920> to<00:13:56.839> override<00:13:57.759> the 00:13:57.990 --> 00:13:58.000 align:start position:0% basically uh be able to override the 00:13:58.000 --> 00:14:01.870 align:start position:0% basically uh be able to override the current<00:13:58.399> key<00:13:59.279> and<00:13:59.519> say<00:14:00.320> here<00:14:00.560> is<00:14:01.560> here<00:14:01.680> is 00:14:01.870 --> 00:14:01.880 align:start position:0% current key and say here is here is 00:14:01.880 --> 00:14:03.870 align:start position:0% current key and say here is here is another<00:14:02.240> key<00:14:02.560> that<00:14:02.680> is<00:14:02.880> now<00:14:03.079> in<00:14:03.240> control<00:14:03.639> of 00:14:03.870 --> 00:14:03.880 align:start position:0% another key that is now in control of 00:14:03.880 --> 00:14:08.030 align:start position:0% another key that is now in control of this<00:14:04.839> uh<00:14:05.839> of<00:14:06.079> this<00:14:06.680> smart 00:14:08.030 --> 00:14:08.040 align:start position:0% this uh of this smart 00:14:08.040 --> 00:14:12.550 align:start position:0% this uh of this smart contract<00:14:09.040> uh<00:14:09.600> so<00:14:09.920> let<00:14:10.120> me<00:14:11.120> talk<00:14:11.480> about<00:14:12.360> what 00:14:12.550 --> 00:14:12.560 align:start position:0% contract uh so let me talk about what 00:14:12.560 --> 00:14:15.629 align:start position:0% contract uh so let me talk about what we've<00:14:12.759> been<00:14:12.920> doing<00:14:13.279> at<00:14:13.800> consensus<00:14:14.800> uh<00:14:15.279> with 00:14:15.629 --> 00:14:15.639 align:start position:0% we've been doing at consensus uh with 00:14:15.639 --> 00:14:21.269 align:start position:0% we've been doing at consensus uh with the<00:14:16.720> ort<00:14:17.720> initiative<00:14:18.720> so<00:14:19.240> this<00:14:19.560> is 00:14:21.269 --> 00:14:21.279 align:start position:0% the ort initiative so this is 00:14:21.279 --> 00:14:24.189 align:start position:0% the ort initiative so this is basically<00:14:22.279> um<00:14:22.560> trying<00:14:22.839> to<00:14:23.079> take<00:14:23.320> these<00:14:23.519> IDs 00:14:24.189 --> 00:14:24.199 align:start position:0% basically um trying to take these IDs 00:14:24.199 --> 00:14:28.030 align:start position:0% basically um trying to take these IDs and<00:14:24.480> and<00:14:24.680> make<00:14:25.160> a<00:14:25.720> uh<00:14:26.440> functioning<00:14:27.440> product 00:14:28.030 --> 00:14:28.040 align:start position:0% and and make a uh functioning product 00:14:28.040 --> 00:14:29.910 align:start position:0% and and make a uh functioning product out<00:14:28.199> of<00:14:28.360> it 00:14:29.910 --> 00:14:29.920 align:start position:0% out of it 00:14:29.920 --> 00:14:31.710 align:start position:0% out of it So 00:14:31.710 --> 00:14:31.720 align:start position:0% So 00:14:31.720 --> 00:14:35.350 align:start position:0% So currently<00:14:32.720> uh<00:14:33.240> the<00:14:33.440> current<00:14:33.839> status<00:14:34.360> is<00:14:35.120> is 00:14:35.350 --> 00:14:35.360 align:start position:0% currently uh the current status is is 00:14:35.360 --> 00:14:39.269 align:start position:0% currently uh the current status is is the<00:14:35.759> following<00:14:36.759> we<00:14:37.079> have<00:14:37.560> this<00:14:37.800> kind<00:14:38.000> of<00:14:38.639> core 00:14:39.269 --> 00:14:39.279 align:start position:0% the following we have this kind of core 00:14:39.279 --> 00:14:43.069 align:start position:0% the following we have this kind of core identity<00:14:39.839> model<00:14:40.600> where<00:14:40.839> you<00:14:41.120> have<00:14:41.639> a<00:14:42.639> uh<00:14:42.880> a 00:14:43.069 --> 00:14:43.079 align:start position:0% identity model where you have a uh a 00:14:43.079 --> 00:14:46.629 align:start position:0% identity model where you have a uh a controlling<00:14:43.680> key<00:14:44.639> that<00:14:44.800> controls<00:14:45.759> your 00:14:46.629 --> 00:14:46.639 align:start position:0% controlling key that controls your 00:14:46.639 --> 00:14:51.189 align:start position:0% controlling key that controls your identity<00:14:47.639> which<00:14:48.199> is<00:14:49.199> um<00:14:50.199> attached<00:14:50.600> to 00:14:51.189 --> 00:14:51.199 align:start position:0% identity which is um attached to 00:14:51.199 --> 00:14:54.269 align:start position:0% identity which is um attached to attributes<00:14:52.199> uh<00:14:52.320> we<00:14:52.440> use<00:14:52.680> ipfs<00:14:53.440> to<00:14:53.800> to<00:14:53.959> store 00:14:54.269 --> 00:14:54.279 align:start position:0% attributes uh we use ipfs to to store 00:14:54.279 --> 00:14:57.110 align:start position:0% attributes uh we use ipfs to to store these<00:14:54.759> attributes<00:14:55.759> uh<00:14:56.120> we<00:14:56.279> have<00:14:56.399> a<00:14:56.560> registry 00:14:57.110 --> 00:14:57.120 align:start position:0% these attributes uh we have a registry 00:14:57.120 --> 00:15:00.389 align:start position:0% these attributes uh we have a registry where<00:14:57.279> you<00:14:57.440> can<00:14:58.399> where<00:14:58.519> you<00:14:58.639> can<00:14:58.759> look<00:14:59.240> up<00:15:00.000> uh 00:15:00.389 --> 00:15:00.399 align:start position:0% where you can where you can look up uh 00:15:00.399 --> 00:15:03.470 align:start position:0% where you can where you can look up uh the<00:15:01.279> um<00:15:02.279> the 00:15:03.470 --> 00:15:03.480 align:start position:0% the um the 00:15:03.480 --> 00:15:05.949 align:start position:0% the um the uh<00:15:04.480> uh<00:15:04.880> you<00:15:05.000> can<00:15:05.160> look<00:15:05.320> up<00:15:05.440> the<00:15:05.560> key<00:15:05.759> in<00:15:05.800> a 00:15:05.949 --> 00:15:05.959 align:start position:0% uh uh you can look up the key in a 00:15:05.959 --> 00:15:08.629 align:start position:0% uh uh you can look up the key in a registry<00:15:06.440> and<00:15:06.600> get<00:15:06.759> the<00:15:07.000> corresponding 00:15:08.629 --> 00:15:08.639 align:start position:0% registry and get the corresponding 00:15:08.639 --> 00:15:11.590 align:start position:0% registry and get the corresponding attributes<00:15:09.639> uh<00:15:10.079> this<00:15:10.279> is<00:15:10.680> currently<00:15:11.160> used 00:15:11.590 --> 00:15:11.600 align:start position:0% attributes uh this is currently used 00:15:11.600 --> 00:15:15.189 align:start position:0% attributes uh this is currently used inhouse<00:15:12.480> in<00:15:13.040> a<00:15:13.560> uh<00:15:13.720> a<00:15:13.880> number<00:15:14.360> of<00:15:14.639> other 00:15:15.189 --> 00:15:15.199 align:start position:0% inhouse in a uh a number of other 00:15:15.199 --> 00:15:18.749 align:start position:0% inhouse in a uh a number of other consensus<00:15:16.279> projects<00:15:17.279> so<00:15:17.959> balance<00:15:18.360> three<00:15:18.639> the 00:15:18.749 --> 00:15:18.759 align:start position:0% consensus projects so balance three the 00:15:18.759 --> 00:15:21.350 align:start position:0% consensus projects so balance three the triple<00:15:19.000> entry<00:15:19.320> accounting<00:15:19.759> system<00:15:20.639> the<00:15:21.079> uh 00:15:21.350 --> 00:15:21.360 align:start position:0% triple entry accounting system the uh 00:15:21.360 --> 00:15:22.550 align:start position:0% triple entry accounting system the uh registry 00:15:22.550 --> 00:15:22.560 align:start position:0% registry 00:15:22.560 --> 00:15:25.829 align:start position:0% registry Builder<00:15:23.560> uh<00:15:23.800> the<00:15:24.279> I<00:15:24.399> mentioned<00:15:24.759> inflect<00:15:25.560> the 00:15:25.829 --> 00:15:25.839 align:start position:0% Builder uh the I mentioned inflect the 00:15:25.839 --> 00:15:28.670 align:start position:0% Builder uh the I mentioned inflect the event<00:15:26.160> and<00:15:26.360> Community<00:15:26.920> Management<00:15:27.519> tool<00:15:28.480> and 00:15:28.670 --> 00:15:28.680 align:start position:0% event and Community Management tool and 00:15:28.680 --> 00:15:32.790 align:start position:0% event and Community Management tool and the<00:15:29.279> read<00:15:29.519> it<00:15:29.759> like<00:15:30.120> a<00:15:30.360> discussion<00:15:31.000> platform 00:15:32.790 --> 00:15:32.800 align:start position:0% the read it like a discussion platform 00:15:32.800 --> 00:15:36.509 align:start position:0% the read it like a discussion platform nonsense<00:15:33.800> um<00:15:34.360> so<00:15:34.720> here<00:15:35.160> here<00:15:35.319> is<00:15:36.040> kind<00:15:36.199> of<00:15:36.399> like 00:15:36.509 --> 00:15:36.519 align:start position:0% nonsense um so here here is kind of like 00:15:36.519 --> 00:15:39.350 align:start position:0% nonsense um so here here is kind of like a<00:15:36.639> screenshot<00:15:37.440> from<00:15:37.759> from<00:15:38.040> balance 00:15:39.350 --> 00:15:39.360 align:start position:0% a screenshot from from balance 00:15:39.360 --> 00:15:42.110 align:start position:0% a screenshot from from balance 3<00:15:40.360> uh<00:15:40.720> where<00:15:40.959> where<00:15:41.079> we<00:15:41.240> see<00:15:41.519> in<00:15:41.680> the<00:15:41.839> in<00:15:41.920> the 00:15:42.110 --> 00:15:42.120 align:start position:0% 3 uh where where we see in the in the 00:15:42.120 --> 00:15:45.949 align:start position:0% 3 uh where where we see in the in the top<00:15:42.360> right<00:15:42.600> corner<00:15:43.120> kind<00:15:43.240> of<00:15:43.759> the<00:15:44.759> a<00:15:44.959> very 00:15:45.949 --> 00:15:45.959 align:start position:0% top right corner kind of the a very 00:15:45.959 --> 00:15:50.150 align:start position:0% top right corner kind of the a very familiar<00:15:46.959> like<00:15:47.319> user<00:15:48.000> badge<00:15:48.600> thing<00:15:49.519> and<00:15:49.920> that 00:15:50.150 --> 00:15:50.160 align:start position:0% familiar like user badge thing and that 00:15:50.160 --> 00:15:54.710 align:start position:0% familiar like user badge thing and that information<00:15:50.920> is<00:15:51.720> is<00:15:52.199> stored<00:15:53.199> in<00:15:53.560> ipfs<00:15:54.399> and<00:15:54.560> and 00:15:54.710 --> 00:15:54.720 align:start position:0% information is is stored in ipfs and and 00:15:54.720 --> 00:15:57.710 align:start position:0% information is is stored in ipfs and and retrieve<00:15:55.279> via<00:15:55.560> this<00:15:55.959> smart<00:15:56.319> contract 00:15:57.710 --> 00:15:57.720 align:start position:0% retrieve via this smart contract 00:15:57.720 --> 00:15:59.590 align:start position:0% retrieve via this smart contract system<00:15:58.720> uh 00:15:59.590 --> 00:15:59.600 align:start position:0% system uh 00:15:59.600 --> 00:16:00.949 align:start position:0% system uh future 00:16:00.949 --> 00:16:00.959 align:start position:0% future 00:16:00.959 --> 00:16:04.110 align:start position:0% future directions<00:16:01.959> instead<00:16:02.319> of<00:16:02.839> having<00:16:03.240> it<00:16:03.639> be<00:16:03.839> tied 00:16:04.110 --> 00:16:04.120 align:start position:0% directions instead of having it be tied 00:16:04.120 --> 00:16:06.430 align:start position:0% directions instead of having it be tied to<00:16:04.240> a<00:16:04.360> single<00:16:04.639> private<00:16:04.959> key<00:16:05.399> we<00:16:05.560> want<00:16:05.680> to<00:16:05.920> tie 00:16:06.430 --> 00:16:06.440 align:start position:0% to a single private key we want to tie 00:16:06.440 --> 00:16:09.949 align:start position:0% to a single private key we want to tie the<00:16:07.120> identity<00:16:07.639> to<00:16:07.959> a<00:16:08.759> uh<00:16:08.920> unique 00:16:09.949 --> 00:16:09.959 align:start position:0% the identity to a uh unique 00:16:09.959 --> 00:16:13.470 align:start position:0% the identity to a uh unique identifier<00:16:10.959> so<00:16:11.240> that<00:16:11.399> we<00:16:11.560> can<00:16:11.920> have<00:16:12.880> uh<00:16:13.240> the 00:16:13.470 --> 00:16:13.480 align:start position:0% identifier so that we can have uh the 00:16:13.480 --> 00:16:16.509 align:start position:0% identifier so that we can have uh the type<00:16:13.680> of<00:16:13.920> key<00:16:14.160> rotation<00:16:14.839> key<00:16:15.199> revocation<00:16:16.199> uh 00:16:16.509 --> 00:16:16.519 align:start position:0% type of key rotation key revocation uh 00:16:16.519 --> 00:16:18.550 align:start position:0% type of key rotation key revocation uh features<00:16:17.240> that<00:16:17.440> that<00:16:17.519> we<00:16:17.680> talk<00:16:17.959> about<00:16:18.399> and 00:16:18.550 --> 00:16:18.560 align:start position:0% features that that we talk about and 00:16:18.560 --> 00:16:19.949 align:start position:0% features that that we talk about and also<00:16:18.880> key 00:16:19.949 --> 00:16:19.959 align:start position:0% also key 00:16:19.959 --> 00:16:23.670 align:start position:0% also key recovery<00:16:20.959> uh<00:16:21.680> we<00:16:21.800> want<00:16:21.959> to<00:16:22.079> be<00:16:22.240> able<00:16:22.560> to<00:16:23.319> have 00:16:23.670 --> 00:16:23.680 align:start position:0% recovery uh we want to be able to have 00:16:23.680 --> 00:16:25.870 align:start position:0% recovery uh we want to be able to have the<00:16:24.319> attributes 00:16:25.870 --> 00:16:25.880 align:start position:0% the attributes 00:16:25.880 --> 00:16:28.550 align:start position:0% the attributes encrypted<00:16:26.880> so<00:16:27.160> that<00:16:27.480> you<00:16:27.600> can<00:16:27.759> have<00:16:28.000> private 00:16:28.550 --> 00:16:28.560 align:start position:0% encrypted so that you can have private 00:16:28.560 --> 00:16:31.870 align:start position:0% encrypted so that you can have private uh<00:16:29.079> attributes<00:16:30.079> and<00:16:30.480> to<00:16:30.639> be<00:16:30.800> able<00:16:31.040> to<00:16:31.720> uh 00:16:31.870 --> 00:16:31.880 align:start position:0% uh attributes and to be able to uh 00:16:31.880 --> 00:16:36.389 align:start position:0% uh attributes and to be able to uh selectively<00:16:32.480> disclose<00:16:33.079> those<00:16:33.319> to<00:16:33.720> to<00:16:34.319> uh<00:16:35.399> um 00:16:36.389 --> 00:16:36.399 align:start position:0% selectively disclose those to to uh um 00:16:36.399 --> 00:16:42.870 align:start position:0% selectively disclose those to to uh um to<00:16:36.720> your<00:16:37.560> uh<00:16:38.560> friends<00:16:39.120> or<00:16:39.639> whoever<00:16:40.639> uh<00:16:41.680> also<00:16:42.680> uh 00:16:42.870 --> 00:16:42.880 align:start position:0% to your uh friends or whoever uh also uh 00:16:42.880 --> 00:16:45.990 align:start position:0% to your uh friends or whoever uh also uh integrating<00:16:43.880> our<00:16:44.279> our<00:16:44.880> reputation<00:16:45.480> system<00:16:45.839> is 00:16:45.990 --> 00:16:46.000 align:start position:0% integrating our our reputation system is 00:16:46.000 --> 00:16:50.350 align:start position:0% integrating our our reputation system is also<00:16:46.279> on<00:16:46.440> the<00:16:46.560> road<00:16:46.880> map<00:16:47.839> so<00:16:48.839> uh<00:16:49.040> this<00:16:49.199> is<00:16:49.480> the 00:16:50.350 --> 00:16:50.360 align:start position:0% also on the road map so uh this is the 00:16:50.360 --> 00:16:54.069 align:start position:0% also on the road map so uh this is the team<00:16:51.160> for<00:16:52.319> uport 00:16:54.069 --> 00:16:54.079 align:start position:0% team for uport 00:16:54.079 --> 00:16:56.790 align:start position:0% team for uport and<00:16:55.079> that's<00:16:55.319> it<00:16:56.000> I<00:16:56.079> don't<00:16:56.240> know<00:16:56.399> if<00:16:56.519> I<00:16:56.639> have 00:16:56.790 --> 00:16:56.800 align:start position:0% and that's it I don't know if I have 00:16:56.800 --> 00:17:00.990 align:start position:0% and that's it I don't know if I have time<00:16:56.959> for<00:16:57.199> questions<00:16:58.079> uh<00:16:58.519> there 00:17:00.990 --> 00:17:01.000 align:start position:0% 00:17:01.000 --> 00:17:03.269 align:start position:0% sorry<00:17:02.000> uh<00:17:02.240> sorry<00:17:02.639> I<00:17:02.759> I<00:17:02.839> shouldn't<00:17:03.120> have 00:17:03.269 --> 00:17:03.279 align:start position:0% sorry uh sorry I I shouldn't have 00:17:03.279 --> 00:17:05.630 align:start position:0% sorry uh sorry I I shouldn't have written<00:17:03.560> that<00:17:04.360> but<00:17:04.559> anyway<00:17:05.199> thank<00:17:05.360> you<00:17:05.480> so 00:17:05.630 --> 00:17:05.640 align:start position:0% written that but anyway thank you so 00:17:05.640 --> 00:17:14.140 align:start position:0% written that but anyway thank you so much 00:17:14.140 --> 00:17:14.150 align:start position:0% 00:17:14.150 --> 00:17:18.479 align:start position:0% [Music]