WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:12.610 align:start position:0% [Music] 00:00:12.610 --> 00:00:12.620 align:start position:0% 00:00:12.620 --> 00:00:14.810 align:start position:0% good<00:00:13.620> afternoon 00:00:14.810 --> 00:00:14.820 align:start position:0% good afternoon 00:00:14.820 --> 00:00:15.589 align:start position:0% good afternoon um 00:00:15.589 --> 00:00:15.599 align:start position:0% um 00:00:15.599 --> 00:00:18.109 align:start position:0% um I'm<00:00:15.960> here<00:00:16.139> to<00:00:16.320> talk<00:00:16.440> about<00:00:16.560> Spruce<00:00:17.160> its 00:00:18.109 --> 00:00:18.119 align:start position:0% I'm here to talk about Spruce its 00:00:18.119 --> 00:00:20.689 align:start position:0% I'm here to talk about Spruce its Mission<00:00:18.300> sign<00:00:18.779> in<00:00:19.020> with<00:00:19.140> ethereum<00:00:19.619> and<00:00:20.400> how 00:00:20.689 --> 00:00:20.699 align:start position:0% Mission sign in with ethereum and how 00:00:20.699 --> 00:00:22.790 align:start position:0% Mission sign in with ethereum and how the<00:00:20.880> concept<00:00:21.180> came<00:00:21.420> about<00:00:21.600> its<00:00:22.020> being<00:00:22.140> and 00:00:22.790 --> 00:00:22.800 align:start position:0% the concept came about its being and 00:00:22.800 --> 00:00:24.970 align:start position:0% the concept came about its being and especially<00:00:23.039> where<00:00:23.279> we<00:00:23.400> go<00:00:23.520> from<00:00:23.699> here 00:00:24.970 --> 00:00:24.980 align:start position:0% especially where we go from here 00:00:24.980 --> 00:00:27.349 align:start position:0% especially where we go from here this<00:00:25.980> is<00:00:26.279> my<00:00:26.519> third<00:00:26.640> time<00:00:26.880> in<00:00:27.060> this<00:00:27.180> country 00:00:27.349 --> 00:00:27.359 align:start position:0% this is my third time in this country 00:00:27.359 --> 00:00:29.390 align:start position:0% this is my third time in this country and<00:00:27.720> I'm<00:00:27.840> really<00:00:28.019> excited<00:00:28.439> to<00:00:28.619> be<00:00:28.920> in<00:00:29.039> Bogota 00:00:29.390 --> 00:00:29.400 align:start position:0% and I'm really excited to be in Bogota 00:00:29.400 --> 00:00:31.429 align:start position:0% and I'm really excited to be in Bogota and<00:00:30.000> looking<00:00:30.240> forward<00:00:30.480> to<00:00:30.779> exploring<00:00:31.140> more<00:00:31.320> of 00:00:31.429 --> 00:00:31.439 align:start position:0% and looking forward to exploring more of 00:00:31.439 --> 00:00:33.410 align:start position:0% and looking forward to exploring more of Bogota 00:00:33.410 --> 00:00:33.420 align:start position:0% Bogota 00:00:33.420 --> 00:00:35.090 align:start position:0% Bogota um before<00:00:33.660> we<00:00:33.899> jump<00:00:34.079> into<00:00:34.260> the<00:00:34.500> all<00:00:34.800> the<00:00:34.980> fun 00:00:35.090 --> 00:00:35.100 align:start position:0% um before we jump into the all the fun 00:00:35.100 --> 00:00:37.130 align:start position:0% um before we jump into the all the fun stuff<00:00:35.340> about<00:00:35.700> Spruce<00:00:36.239> and<00:00:36.660> sign<00:00:36.840> in<00:00:37.020> with 00:00:37.130 --> 00:00:37.140 align:start position:0% stuff about Spruce and sign in with 00:00:37.140 --> 00:00:39.049 align:start position:0% stuff about Spruce and sign in with ethereum<00:00:37.620> I'd<00:00:38.280> like<00:00:38.460> to<00:00:38.579> give<00:00:38.700> a<00:00:38.880> quick 00:00:39.049 --> 00:00:39.059 align:start position:0% ethereum I'd like to give a quick 00:00:39.059 --> 00:00:41.510 align:start position:0% ethereum I'd like to give a quick introduction<00:00:39.540> about<00:00:39.780> myself 00:00:41.510 --> 00:00:41.520 align:start position:0% introduction about myself 00:00:41.520 --> 00:00:44.450 align:start position:0% introduction about myself I<00:00:42.000> am<00:00:42.120> anukriti<00:00:42.840> Kumar<00:00:43.200> uh<00:00:44.040> I'm<00:00:44.160> a<00:00:44.340> product 00:00:44.450 --> 00:00:44.460 align:start position:0% I am anukriti Kumar uh I'm a product 00:00:44.460 --> 00:00:46.250 align:start position:0% I am anukriti Kumar uh I'm a product manager<00:00:44.879> with<00:00:45.059> Spruce 00:00:46.250 --> 00:00:46.260 align:start position:0% manager with Spruce 00:00:46.260 --> 00:00:47.090 align:start position:0% manager with Spruce um 00:00:47.090 --> 00:00:47.100 align:start position:0% um 00:00:47.100 --> 00:00:49.190 align:start position:0% um before<00:00:47.579> joining<00:00:47.940> Spruce<00:00:48.300> I<00:00:48.480> was<00:00:48.600> working<00:00:48.780> as<00:00:49.020> a 00:00:49.190 --> 00:00:49.200 align:start position:0% before joining Spruce I was working as a 00:00:49.200 --> 00:00:50.930 align:start position:0% before joining Spruce I was working as a data<00:00:49.500> program<00:00:49.620> manager 00:00:50.930 --> 00:00:50.940 align:start position:0% data program manager 00:00:50.940 --> 00:00:53.090 align:start position:0% data program manager um<00:00:51.000> with<00:00:51.239> an<00:00:51.360> airline<00:00:51.719> in<00:00:51.899> New<00:00:52.079> York<00:00:52.200> City<00:00:52.379> I'm 00:00:53.090 --> 00:00:53.100 align:start position:0% um with an airline in New York City I'm 00:00:53.100 --> 00:00:55.310 align:start position:0% um with an airline in New York City I'm a<00:00:53.280> computer<00:00:53.399> science<00:00:53.700> engineer<00:00:54.300> so<00:00:54.899> I 00:00:55.310 --> 00:00:55.320 align:start position:0% a computer science engineer so I 00:00:55.320 --> 00:00:57.229 align:start position:0% a computer science engineer so I understand<00:00:55.520> technology<00:00:56.520> a<00:00:56.820> little<00:00:56.879> bit<00:00:57.059> and 00:00:57.229 --> 00:00:57.239 align:start position:0% understand technology a little bit and 00:00:57.239 --> 00:01:00.170 align:start position:0% understand technology a little bit and code<00:00:57.420> a<00:00:57.719> little<00:00:57.840> bit<00:00:58.020> as<00:00:58.199> well 00:01:00.170 --> 00:01:00.180 align:start position:0% code a little bit as well 00:01:00.180 --> 00:01:02.150 align:start position:0% code a little bit as well um<00:01:00.300> I<00:01:00.719> started<00:01:01.079> my<00:01:01.260> web<00:01:01.440> free<00:01:01.680> Journey 00:01:02.150 --> 00:01:02.160 align:start position:0% um I started my web free Journey 00:01:02.160 --> 00:01:05.390 align:start position:0% um I started my web free Journey probably<00:01:02.820> 11<00:01:03.359> months<00:01:03.840> back<00:01:04.019> and<00:01:04.920> two<00:01:05.100> months 00:01:05.390 --> 00:01:05.400 align:start position:0% probably 11 months back and two months 00:01:05.400 --> 00:01:07.730 align:start position:0% probably 11 months back and two months back<00:01:05.519> I<00:01:06.060> took<00:01:06.360> the<00:01:06.540> plunge<00:01:06.960> and<00:01:07.380> started 00:01:07.730 --> 00:01:07.740 align:start position:0% back I took the plunge and started 00:01:07.740 --> 00:01:10.370 align:start position:0% back I took the plunge and started working<00:01:07.860> 100<00:01:08.100> in<00:01:08.700> the<00:01:08.880> space<00:01:09.060> and<00:01:09.600> there 00:01:10.370 --> 00:01:10.380 align:start position:0% working 100 in the space and there 00:01:10.380 --> 00:01:11.929 align:start position:0% working 100 in the space and there hasn't<00:01:10.680> been<00:01:10.799> any<00:01:10.979> looking<00:01:11.220> back<00:01:11.520> and<00:01:11.820> I'm 00:01:11.929 --> 00:01:11.939 align:start position:0% hasn't been any looking back and I'm 00:01:11.939 --> 00:01:13.850 align:start position:0% hasn't been any looking back and I'm enjoying<00:01:12.360> every<00:01:12.540> bit<00:01:12.720> of<00:01:12.900> it 00:01:13.850 --> 00:01:13.860 align:start position:0% enjoying every bit of it 00:01:13.860 --> 00:01:15.469 align:start position:0% enjoying every bit of it so 00:01:15.469 --> 00:01:15.479 align:start position:0% so 00:01:15.479 --> 00:01:18.649 align:start position:0% so and<00:01:16.080> outside<00:01:16.260> of<00:01:16.619> work<00:01:16.860> I<00:01:17.460> love<00:01:17.640> dogs<00:01:17.939> and<00:01:18.479> I'm 00:01:18.649 --> 00:01:18.659 align:start position:0% and outside of work I love dogs and I'm 00:01:18.659 --> 00:01:20.450 align:start position:0% and outside of work I love dogs and I'm really<00:01:18.780> passionate<00:01:19.200> about<00:01:19.320> them<00:01:19.619> and<00:01:20.220> my 00:01:20.450 --> 00:01:20.460 align:start position:0% really passionate about them and my 00:01:20.460 --> 00:01:22.310 align:start position:0% really passionate about them and my husband<00:01:20.580> and<00:01:20.759> I<00:01:20.939> we<00:01:21.119> try<00:01:21.299> to<00:01:21.479> Foster<00:01:21.840> one<00:01:22.080> dog 00:01:22.310 --> 00:01:22.320 align:start position:0% husband and I we try to Foster one dog 00:01:22.320 --> 00:01:24.649 align:start position:0% husband and I we try to Foster one dog probably<00:01:22.740> every<00:01:22.920> two<00:01:23.280> months<00:01:23.580> because<00:01:23.820> we<00:01:24.479> are 00:01:24.649 --> 00:01:24.659 align:start position:0% probably every two months because we are 00:01:24.659 --> 00:01:26.870 align:start position:0% probably every two months because we are not<00:01:24.780> yet<00:01:24.960> ready<00:01:25.200> for<00:01:25.380> the<00:01:25.500> commitment 00:01:26.870 --> 00:01:26.880 align:start position:0% not yet ready for the commitment 00:01:26.880 --> 00:01:32.030 align:start position:0% not yet ready for the commitment so<00:01:27.600> let's<00:01:28.320> jump<00:01:28.560> on<00:01:28.680> to<00:01:28.860> the<00:01:28.979> fun<00:01:29.100> part<00:01:29.340> now 00:01:32.030 --> 00:01:32.040 align:start position:0% 00:01:32.040 --> 00:01:34.730 align:start position:0% oh<00:01:32.460> yes<00:01:32.640> so<00:01:32.939> Spruce<00:01:33.900> um<00:01:33.960> I'll<00:01:34.200> talk<00:01:34.380> more<00:01:34.560> about 00:01:34.730 --> 00:01:34.740 align:start position:0% oh yes so Spruce um I'll talk more about 00:01:34.740 --> 00:01:36.649 align:start position:0% oh yes so Spruce um I'll talk more about Spruce<00:01:35.159> but<00:01:35.460> it's<00:01:35.759> a<00:01:35.880> two-year-old<00:01:36.360> company 00:01:36.649 --> 00:01:36.659 align:start position:0% Spruce but it's a two-year-old company 00:01:36.659 --> 00:01:40.069 align:start position:0% Spruce but it's a two-year-old company and<00:01:37.320> we<00:01:37.560> are<00:01:37.680> working<00:01:37.920> a<00:01:38.520> bunch<00:01:38.759> of<00:01:39.479> use<00:01:39.720> cases 00:01:40.069 --> 00:01:40.079 align:start position:0% and we are working a bunch of use cases 00:01:40.079 --> 00:01:43.249 align:start position:0% and we are working a bunch of use cases of<00:01:40.619> data<00:01:41.340> and<00:01:41.520> identity 00:01:43.249 --> 00:01:43.259 align:start position:0% of data and identity 00:01:43.259 --> 00:01:45.230 align:start position:0% of data and identity and<00:01:43.799> that's<00:01:43.979> the<00:01:44.159> team<00:01:44.340> there 00:01:45.230 --> 00:01:45.240 align:start position:0% and that's the team there 00:01:45.240 --> 00:01:48.950 align:start position:0% and that's the team there um<00:01:45.299> we<00:01:45.600> are<00:01:45.780> 17<00:01:46.200> to<00:01:46.500> 18<00:01:46.740> people<00:01:47.100> company<00:01:47.939> and<00:01:48.600> I 00:01:48.950 --> 00:01:48.960 align:start position:0% um we are 17 to 18 people company and I 00:01:48.960 --> 00:01:51.649 align:start position:0% um we are 17 to 18 people company and I love<00:01:49.140> working<00:01:49.439> with<00:01:49.680> these<00:01:49.920> folks 00:01:51.649 --> 00:01:51.659 align:start position:0% love working with these folks 00:01:51.659 --> 00:01:55.249 align:start position:0% love working with these folks okay<00:01:52.200> so<00:01:52.560> this<00:01:52.920> is<00:01:53.040> we<00:01:53.220> are<00:01:53.720> all<00:01:54.720> this<00:01:54.899> we<00:01:55.140> are 00:01:55.249 --> 00:01:55.259 align:start position:0% okay so this is we are all this we are 00:01:55.259 --> 00:01:57.230 align:start position:0% okay so this is we are all this we are going<00:01:55.320> to<00:01:55.439> cover<00:01:55.619> today<00:01:55.979> probably<00:01:56.460> next<00:01:56.820> 20<00:01:57.060> to 00:01:57.230 --> 00:01:57.240 align:start position:0% going to cover today probably next 20 to 00:01:57.240 --> 00:01:59.330 align:start position:0% going to cover today probably next 20 to 25<00:01:57.479> minutes<00:01:57.960> so 00:01:59.330 --> 00:01:59.340 align:start position:0% 25 minutes so 00:01:59.340 --> 00:02:01.609 align:start position:0% 25 minutes so jumping<00:01:59.939> into<00:02:00.119> the<00:02:00.360> decentralized<00:02:01.079> identity 00:02:01.609 --> 00:02:01.619 align:start position:0% jumping into the decentralized identity 00:02:01.619 --> 00:02:04.850 align:start position:0% jumping into the decentralized identity where<00:02:02.159> Spruce<00:02:02.640> functions<00:02:03.360> in<00:02:03.600> so<00:02:04.320> just<00:02:04.560> giving 00:02:04.850 --> 00:02:04.860 align:start position:0% where Spruce functions in so just giving 00:02:04.860 --> 00:02:06.350 align:start position:0% where Spruce functions in so just giving a<00:02:05.159> quick<00:02:05.280> background<00:02:05.640> of<00:02:05.939> what<00:02:06.180> is 00:02:06.350 --> 00:02:06.360 align:start position:0% a quick background of what is 00:02:06.360 --> 00:02:09.770 align:start position:0% a quick background of what is decentralized<00:02:07.079> identity 00:02:09.770 --> 00:02:09.780 align:start position:0% 00:02:09.780 --> 00:02:12.890 align:start position:0% so<00:02:10.200> decentralized<00:02:11.039> identity<00:02:11.520> is<00:02:12.239> an<00:02:12.720> open 00:02:12.890 --> 00:02:12.900 align:start position:0% so decentralized identity is an open 00:02:12.900 --> 00:02:15.710 align:start position:0% so decentralized identity is an open identity<00:02:13.500> framework<00:02:14.099> where<00:02:14.879> you<00:02:15.300> own<00:02:15.480> the 00:02:15.710 --> 00:02:15.720 align:start position:0% identity framework where you own the 00:02:15.720 --> 00:02:17.869 align:start position:0% identity framework where you own the data<00:02:16.080> and<00:02:16.620> it's<00:02:16.920> all<00:02:17.220> open<00:02:17.459> and 00:02:17.869 --> 00:02:17.879 align:start position:0% data and it's all open and 00:02:17.879 --> 00:02:20.150 align:start position:0% data and it's all open and self-controlled 00:02:20.150 --> 00:02:20.160 align:start position:0% self-controlled 00:02:20.160 --> 00:02:24.410 align:start position:0% self-controlled um<00:02:20.280> think<00:02:20.700> of<00:02:20.879> decentralized<00:02:21.599> identity<00:02:22.140> as 00:02:24.410 --> 00:02:24.420 align:start position:0% um think of decentralized identity as 00:02:24.420 --> 00:02:27.110 align:start position:0% um think of decentralized identity as statements<00:02:25.200> about<00:02:25.319> reality<00:02:25.860> and<00:02:26.760> these 00:02:27.110 --> 00:02:27.120 align:start position:0% statements about reality and these 00:02:27.120 --> 00:02:29.449 align:start position:0% statements about reality and these statements<00:02:27.420> about<00:02:27.540> reality<00:02:28.140> could<00:02:28.560> be<00:02:28.800> on 00:02:29.449 --> 00:02:29.459 align:start position:0% statements about reality could be on 00:02:29.459 --> 00:02:32.150 align:start position:0% statements about reality could be on chain<00:02:29.640> as<00:02:30.060> well<00:02:30.180> as<00:02:30.360> off<00:02:30.599> chain<00:02:30.840> and<00:02:31.800> they<00:02:31.980> can 00:02:32.150 --> 00:02:32.160 align:start position:0% chain as well as off chain and they can 00:02:32.160 --> 00:02:35.150 align:start position:0% chain as well as off chain and they can range<00:02:32.459> from<00:02:32.819> anything<00:02:33.239> such<00:02:34.140> as<00:02:34.379> where<00:02:34.860> do<00:02:35.040> I 00:02:35.150 --> 00:02:35.160 align:start position:0% range from anything such as where do I 00:02:35.160 --> 00:02:37.610 align:start position:0% range from anything such as where do I live<00:02:35.340> which<00:02:36.060> university<00:02:36.300> did<00:02:36.720> I<00:02:36.840> go<00:02:37.020> to<00:02:37.140> how 00:02:37.610 --> 00:02:37.620 align:start position:0% live which university did I go to how 00:02:37.620 --> 00:02:39.770 align:start position:0% live which university did I go to how much<00:02:37.680> ethereum<00:02:38.160> transaction<00:02:38.580> I<00:02:38.819> made<00:02:39.000> in<00:02:39.480> last 00:02:39.770 --> 00:02:39.780 align:start position:0% much ethereum transaction I made in last 00:02:39.780 --> 00:02:43.309 align:start position:0% much ethereum transaction I made in last one<00:02:40.020> hour<00:02:40.260> what<00:02:41.220> doubt<00:02:41.640> do<00:02:41.879> I<00:02:42.060> work<00:02:42.180> for<00:02:42.420> so<00:02:43.080> all 00:02:43.309 --> 00:02:43.319 align:start position:0% one hour what doubt do I work for so all 00:02:43.319 --> 00:02:45.830 align:start position:0% one hour what doubt do I work for so all they<00:02:43.560> all<00:02:43.980> those<00:02:44.160> statements<00:02:44.700> are 00:02:45.830 --> 00:02:45.840 align:start position:0% they all those statements are 00:02:45.840 --> 00:02:47.809 align:start position:0% they all those statements are statements<00:02:46.379> about<00:02:46.500> reality<00:02:47.040> in<00:02:47.400> some<00:02:47.519> way<00:02:47.700> or 00:02:47.809 --> 00:02:47.819 align:start position:0% statements about reality in some way or 00:02:47.819 --> 00:02:48.770 align:start position:0% statements about reality in some way or the<00:02:48.060> other 00:02:48.770 --> 00:02:48.780 align:start position:0% the other 00:02:48.780 --> 00:02:50.270 align:start position:0% the other and 00:02:50.270 --> 00:02:50.280 align:start position:0% and 00:02:50.280 --> 00:02:52.610 align:start position:0% and I<00:02:50.819> said<00:02:51.060> that<00:02:51.300> it<00:02:51.420> could<00:02:51.599> be<00:02:51.720> on<00:02:51.959> chain<00:02:52.200> as<00:02:52.500> well 00:02:52.610 --> 00:02:52.620 align:start position:0% I said that it could be on chain as well 00:02:52.620 --> 00:02:54.710 align:start position:0% I said that it could be on chain as well as<00:02:52.739> off<00:02:53.040> chain<00:02:53.280> and<00:02:53.700> on-chain<00:02:54.120> example<00:02:54.480> could 00:02:54.710 --> 00:02:54.720 align:start position:0% as off chain and on-chain example could 00:02:54.720 --> 00:02:57.650 align:start position:0% as off chain and on-chain example could be<00:02:54.959> that<00:02:55.980> an<00:02:56.400> ethereum<00:02:56.819> transaction<00:02:57.239> happened 00:02:57.650 --> 00:02:57.660 align:start position:0% be that an ethereum transaction happened 00:02:57.660 --> 00:03:00.170 align:start position:0% be that an ethereum transaction happened a<00:02:58.200> signature<00:02:58.620> was<00:02:58.860> involved<00:02:59.400> and<00:03:00.060> if 00:03:00.170 --> 00:03:00.180 align:start position:0% a signature was involved and if 00:03:00.180 --> 00:03:01.729 align:start position:0% a signature was involved and if something<00:03:00.420> happens<00:03:00.840> the<00:03:01.379> ethereum 00:03:01.729 --> 00:03:01.739 align:start position:0% something happens the ethereum 00:03:01.739 --> 00:03:04.309 align:start position:0% something happens the ethereum blockchain<00:03:02.160> can<00:03:02.519> attest<00:03:02.940> to<00:03:03.120> the<00:03:03.540> state<00:03:04.080> of 00:03:04.309 --> 00:03:04.319 align:start position:0% blockchain can attest to the state of 00:03:04.319 --> 00:03:06.589 align:start position:0% blockchain can attest to the state of itself<00:03:04.680> and<00:03:05.640> of<00:03:05.879> course<00:03:06.000> it's<00:03:06.300> fully 00:03:06.589 --> 00:03:06.599 align:start position:0% itself and of course it's fully 00:03:06.599 --> 00:03:07.970 align:start position:0% itself and of course it's fully verifiable 00:03:07.970 --> 00:03:07.980 align:start position:0% verifiable 00:03:07.980 --> 00:03:09.949 align:start position:0% verifiable and 00:03:09.949 --> 00:03:09.959 align:start position:0% and 00:03:09.959 --> 00:03:12.290 align:start position:0% and the<00:03:10.440> off-chain<00:03:10.860> example<00:03:11.220> could<00:03:11.459> be 00:03:12.290 --> 00:03:12.300 align:start position:0% the off-chain example could be 00:03:12.300 --> 00:03:14.930 align:start position:0% the off-chain example could be the<00:03:12.959> second<00:03:13.500> line<00:03:13.860> is 00:03:14.930 --> 00:03:14.940 align:start position:0% the second line is 00:03:14.940 --> 00:03:17.149 align:start position:0% the second line is it<00:03:15.239> could<00:03:15.420> refer<00:03:15.780> to<00:03:15.840> as<00:03:16.080> a<00:03:16.200> Json<00:03:16.440> signature 00:03:17.149 --> 00:03:17.159 align:start position:0% it could refer to as a Json signature 00:03:17.159 --> 00:03:19.970 align:start position:0% it could refer to as a Json signature and<00:03:18.000> an<00:03:18.420> ethereum<00:03:18.840> address<00:03:19.080> associated<00:03:19.739> with 00:03:19.970 --> 00:03:19.980 align:start position:0% and an ethereum address associated with 00:03:19.980 --> 00:03:23.990 align:start position:0% and an ethereum address associated with a<00:03:20.159> Twitter<00:03:20.280> account<00:03:20.640> or<00:03:21.060> a<00:03:21.180> Google<00:03:21.360> account<00:03:21.659> so 00:03:23.990 --> 00:03:24.000 align:start position:0% a Twitter account or a Google account so 00:03:24.000 --> 00:03:26.089 align:start position:0% a Twitter account or a Google account so but<00:03:24.840> there's<00:03:25.200> a<00:03:25.440> difference<00:03:25.500> between<00:03:25.800> the 00:03:26.089 --> 00:03:26.099 align:start position:0% but there's a difference between the 00:03:26.099 --> 00:03:27.949 align:start position:0% but there's a difference between the on-chain<00:03:26.519> and<00:03:26.700> the<00:03:26.760> off<00:03:26.879> chain<00:03:27.120> as<00:03:27.599> said<00:03:27.780> off 00:03:27.949 --> 00:03:27.959 align:start position:0% on-chain and the off chain as said off 00:03:27.959 --> 00:03:29.930 align:start position:0% on-chain and the off chain as said off chain<00:03:28.200> is<00:03:28.440> fully<00:03:28.739> verifiable<00:03:29.220> and<00:03:29.580> there<00:03:29.760> will 00:03:29.930 --> 00:03:29.940 align:start position:0% chain is fully verifiable and there will 00:03:29.940 --> 00:03:32.390 align:start position:0% chain is fully verifiable and there will be<00:03:30.060> cryptographic<00:03:30.840> evidence<00:03:31.200> for<00:03:32.040> you<00:03:32.220> to 00:03:32.390 --> 00:03:32.400 align:start position:0% be cryptographic evidence for you to 00:03:32.400 --> 00:03:34.729 align:start position:0% be cryptographic evidence for you to prove<00:03:32.640> that<00:03:32.879> this<00:03:33.060> is<00:03:33.239> true<00:03:33.480> whereas<00:03:34.319> for<00:03:34.560> off 00:03:34.729 --> 00:03:34.739 align:start position:0% prove that this is true whereas for off 00:03:34.739 --> 00:03:36.890 align:start position:0% prove that this is true whereas for off chain<00:03:34.980> if<00:03:35.340> someone<00:03:35.519> says<00:03:36.060> my<00:03:36.360> Twitter<00:03:36.540> account 00:03:36.890 --> 00:03:36.900 align:start position:0% chain if someone says my Twitter account 00:03:36.900 --> 00:03:38.570 align:start position:0% chain if someone says my Twitter account is<00:03:37.200> associated<00:03:37.620> with<00:03:37.860> my<00:03:38.040> ethereum<00:03:38.340> account 00:03:38.570 --> 00:03:38.580 align:start position:0% is associated with my ethereum account 00:03:38.580 --> 00:03:42.110 align:start position:0% is associated with my ethereum account it<00:03:39.000> may<00:03:39.120> or<00:03:39.360> may<00:03:39.599> not<00:03:39.720> be<00:03:39.900> true<00:03:40.140> so 00:03:42.110 --> 00:03:42.120 align:start position:0% it may or may not be true so 00:03:42.120 --> 00:03:44.690 align:start position:0% it may or may not be true so it<00:03:42.840> all<00:03:43.080> depends<00:03:43.500> on<00:03:43.799> who<00:03:44.099> is<00:03:44.280> making<00:03:44.459> the 00:03:44.690 --> 00:03:44.700 align:start position:0% it all depends on who is making the 00:03:44.700 --> 00:03:47.509 align:start position:0% it all depends on who is making the claim<00:03:45.060> what<00:03:45.840> evidence<00:03:46.200> is<00:03:46.620> being<00:03:46.799> provided<00:03:47.220> in 00:03:47.509 --> 00:03:47.519 align:start position:0% claim what evidence is being provided in 00:03:47.519 --> 00:03:50.570 align:start position:0% claim what evidence is being provided in that<00:03:47.640> statement<00:03:48.200> and<00:03:49.200> what<00:03:49.920> how<00:03:50.220> are<00:03:50.400> you 00:03:50.570 --> 00:03:50.580 align:start position:0% that statement and what how are you 00:03:50.580 --> 00:03:52.910 align:start position:0% that statement and what how are you interpreting<00:03:51.299> that<00:03:51.540> evidence<00:03:51.900> of 00:03:52.910 --> 00:03:52.920 align:start position:0% interpreting that evidence of 00:03:52.920 --> 00:03:56.330 align:start position:0% interpreting that evidence of um<00:03:52.980> statement<00:03:53.400> so<00:03:54.299> for<00:03:54.540> example<00:03:54.959> if<00:03:55.860> I<00:03:56.159> give 00:03:56.330 --> 00:03:56.340 align:start position:0% um statement so for example if I give 00:03:56.340 --> 00:03:58.850 align:start position:0% um statement so for example if I give you<00:03:56.519> a<00:03:56.879> driving<00:03:57.060> license<00:03:57.420> and<00:03:58.379> you<00:03:58.560> get<00:03:58.680> caught 00:03:58.850 --> 00:03:58.860 align:start position:0% you a driving license and you get caught 00:03:58.860 --> 00:04:01.190 align:start position:0% you a driving license and you get caught by<00:03:59.099> a<00:03:59.280> police<00:03:59.400> officer<00:04:00.000> and<00:04:00.540> you<00:04:00.659> show<00:04:00.900> that 00:04:01.190 --> 00:04:01.200 align:start position:0% by a police officer and you show that 00:04:01.200 --> 00:04:04.250 align:start position:0% by a police officer and you show that driving<00:04:01.560> license<00:04:01.860> it<00:04:02.580> has<00:04:02.700> no<00:04:02.879> value<00:04:03.120> so<00:04:03.959> it 00:04:04.250 --> 00:04:04.260 align:start position:0% driving license it has no value so it 00:04:04.260 --> 00:04:05.809 align:start position:0% driving license it has no value so it has<00:04:04.379> to<00:04:04.500> be<00:04:04.620> given<00:04:04.920> to<00:04:05.040> you<00:04:05.159> by<00:04:05.400> a<00:04:05.580> transport 00:04:05.809 --> 00:04:05.819 align:start position:0% has to be given to you by a transport 00:04:05.819 --> 00:04:09.770 align:start position:0% has to be given to you by a transport Authority<00:04:06.360> in<00:04:06.780> the<00:04:06.900> U.S<00:04:07.200> we<00:04:07.560> use<00:04:07.680> DMV<00:04:08.340> so<00:04:08.819> DMV 00:04:09.770 --> 00:04:09.780 align:start position:0% Authority in the U.S we use DMV so DMV 00:04:09.780 --> 00:04:11.750 align:start position:0% Authority in the U.S we use DMV so DMV has<00:04:10.019> to<00:04:10.140> give<00:04:10.260> you<00:04:10.439> the<00:04:10.739> driving<00:04:10.980> license<00:04:11.280> and 00:04:11.750 --> 00:04:11.760 align:start position:0% has to give you the driving license and 00:04:11.760 --> 00:04:13.729 align:start position:0% has to give you the driving license and only<00:04:11.879> then<00:04:12.180> it<00:04:12.480> would<00:04:12.659> be<00:04:12.900> a<00:04:13.319> verify 00:04:13.729 --> 00:04:13.739 align:start position:0% only then it would be a verify 00:04:13.739 --> 00:04:20.870 align:start position:0% only then it would be a verify verifiable<00:04:14.519> credential 00:04:20.870 --> 00:04:20.880 align:start position:0% 00:04:20.880 --> 00:04:23.570 align:start position:0% so<00:04:21.419> how<00:04:21.660> does<00:04:21.840> this<00:04:22.019> happen<00:04:22.199> off<00:04:22.560> chain<00:04:22.800> so 00:04:23.570 --> 00:04:23.580 align:start position:0% so how does this happen off chain so 00:04:23.580 --> 00:04:25.490 align:start position:0% so how does this happen off chain so let's<00:04:23.699> try<00:04:23.880> and<00:04:24.060> decode<00:04:24.419> this<00:04:24.780> diagram<00:04:25.139> a 00:04:25.490 --> 00:04:25.500 align:start position:0% let's try and decode this diagram a 00:04:25.500 --> 00:04:27.170 align:start position:0% let's try and decode this diagram a little<00:04:25.560> bit<00:04:25.740> so 00:04:27.170 --> 00:04:27.180 align:start position:0% little bit so 00:04:27.180 --> 00:04:30.230 align:start position:0% little bit so what<00:04:27.780> I<00:04:28.020> I<00:04:28.259> explained<00:04:28.740> previously<00:04:29.400> that<00:04:29.880> it's 00:04:30.230 --> 00:04:30.240 align:start position:0% what I I explained previously that it's 00:04:30.240 --> 00:04:32.990 align:start position:0% what I I explained previously that it's a<00:04:30.419> trusted<00:04:30.780> framework<00:04:31.259> who's<00:04:31.620> issuing<00:04:32.220> the 00:04:32.990 --> 00:04:33.000 align:start position:0% a trusted framework who's issuing the 00:04:33.000 --> 00:04:35.810 align:start position:0% a trusted framework who's issuing the statement<00:04:33.419> and<00:04:34.380> who<00:04:34.740> is<00:04:34.860> verifying<00:04:35.340> it<00:04:35.460> this 00:04:35.810 --> 00:04:35.820 align:start position:0% statement and who is verifying it this 00:04:35.820 --> 00:04:39.469 align:start position:0% statement and who is verifying it this is<00:04:35.940> what<00:04:36.180> happens<00:04:36.540> here<00:04:36.900> so<00:04:37.860> this 00:04:39.469 --> 00:04:39.479 align:start position:0% is what happens here so this 00:04:39.479 --> 00:04:41.749 align:start position:0% is what happens here so this um<00:04:39.600> this<00:04:40.020> model<00:04:40.199> is<00:04:40.740> known<00:04:40.979> as<00:04:41.220> verify 00:04:41.749 --> 00:04:41.759 align:start position:0% um this model is known as verify 00:04:41.759 --> 00:04:43.969 align:start position:0% um this model is known as verify credential<00:04:42.180> model<00:04:42.479> it<00:04:43.080> is<00:04:43.199> a<00:04:43.320> global<00:04:43.560> data 00:04:43.969 --> 00:04:43.979 align:start position:0% credential model it is a global data 00:04:43.979 --> 00:04:47.030 align:start position:0% credential model it is a global data standard<00:04:44.340> issued<00:04:44.820> by<00:04:45.000> w3c<00:04:45.780> and<00:04:46.560> if<00:04:46.800> you<00:04:46.919> were 00:04:47.030 --> 00:04:47.040 align:start position:0% standard issued by w3c and if you were 00:04:47.040 --> 00:04:48.770 align:start position:0% standard issued by w3c and if you were to<00:04:47.160> work<00:04:47.340> in<00:04:47.520> the<00:04:47.639> decentralized<00:04:48.300> identity 00:04:48.770 --> 00:04:48.780 align:start position:0% to work in the decentralized identity 00:04:48.780 --> 00:04:52.310 align:start position:0% to work in the decentralized identity world<00:04:48.960> you<00:04:49.320> hear<00:04:49.560> about<00:04:49.800> this<00:04:50.220> a<00:04:50.940> lot<00:04:51.060> so<00:04:51.780> and 00:04:52.310 --> 00:04:52.320 align:start position:0% world you hear about this a lot so and 00:04:52.320 --> 00:04:54.650 align:start position:0% world you hear about this a lot so and we<00:04:52.440> like<00:04:52.620> to<00:04:52.800> call<00:04:52.979> it<00:04:53.100> at<00:04:53.400> Spruce<00:04:53.759> issuer 00:04:54.650 --> 00:04:54.660 align:start position:0% we like to call it at Spruce issuer 00:04:54.660 --> 00:04:57.830 align:start position:0% we like to call it at Spruce issuer holder<00:04:55.259> and<00:04:55.440> verifier<00:04:55.979> so<00:04:56.820> issuer<00:04:57.540> for 00:04:57.830 --> 00:04:57.840 align:start position:0% holder and verifier so issuer for 00:04:57.840 --> 00:05:00.830 align:start position:0% holder and verifier so issuer for example<00:04:58.080> could<00:04:58.440> be<00:04:58.620> a<00:04:58.919> university<00:04:59.240> and<00:05:00.240> where 00:05:00.830 --> 00:05:00.840 align:start position:0% example could be a university and where 00:05:00.840 --> 00:05:02.930 align:start position:0% example could be a university and where the<00:05:01.080> holder<00:05:01.500> completed<00:05:01.979> their<00:05:02.280> masters<00:05:02.699> from 00:05:02.930 --> 00:05:02.940 align:start position:0% the holder completed their masters from 00:05:02.940 --> 00:05:05.629 align:start position:0% the holder completed their masters from and<00:05:03.540> the<00:05:03.780> verifier<00:05:04.199> could<00:05:04.560> be<00:05:04.800> an<00:05:05.100> employer 00:05:05.629 --> 00:05:05.639 align:start position:0% and the verifier could be an employer 00:05:05.639 --> 00:05:07.850 align:start position:0% and the verifier could be an employer who<00:05:06.300> wants<00:05:06.540> to<00:05:06.600> know<00:05:06.780> that<00:05:07.139> whether<00:05:07.560> the 00:05:07.850 --> 00:05:07.860 align:start position:0% who wants to know that whether the 00:05:07.860 --> 00:05:09.530 align:start position:0% who wants to know that whether the holder<00:05:08.220> actually<00:05:08.460> completed<00:05:08.940> their<00:05:09.120> masters 00:05:09.530 --> 00:05:09.540 align:start position:0% holder actually completed their masters 00:05:09.540 --> 00:05:12.770 align:start position:0% holder actually completed their masters from<00:05:09.900> the<00:05:10.380> issuer<00:05:10.919> so<00:05:11.699> in<00:05:11.940> this<00:05:12.060> case<00:05:12.300> the 00:05:12.770 --> 00:05:12.780 align:start position:0% from the issuer so in this case the 00:05:12.780 --> 00:05:15.710 align:start position:0% from the issuer so in this case the issuer<00:05:13.259> will<00:05:13.820> issue<00:05:14.820> the<00:05:14.940> credentials<00:05:15.419> to<00:05:15.540> the 00:05:15.710 --> 00:05:15.720 align:start position:0% issuer will issue the credentials to the 00:05:15.720 --> 00:05:18.050 align:start position:0% issuer will issue the credentials to the holder<00:05:16.080> which<00:05:16.680> will<00:05:16.919> live<00:05:17.160> in<00:05:17.520> holder's 00:05:18.050 --> 00:05:18.060 align:start position:0% holder which will live in holder's 00:05:18.060 --> 00:05:21.530 align:start position:0% holder which will live in holder's wallet<00:05:18.440> and<00:05:19.440> once<00:05:20.280> the<00:05:20.460> verifier<00:05:21.060> wants<00:05:21.419> to 00:05:21.530 --> 00:05:21.540 align:start position:0% wallet and once the verifier wants to 00:05:21.540 --> 00:05:24.890 align:start position:0% wallet and once the verifier wants to see<00:05:21.720> okay<00:05:22.020> I<00:05:22.440> want<00:05:22.620> to<00:05:22.800> verify<00:05:23.580> whether<00:05:24.000> the 00:05:24.890 --> 00:05:24.900 align:start position:0% see okay I want to verify whether the 00:05:24.900 --> 00:05:26.689 align:start position:0% see okay I want to verify whether the holder<00:05:25.380> completed<00:05:25.919> the<00:05:26.100> masters<00:05:26.400> from 00:05:26.689 --> 00:05:26.699 align:start position:0% holder completed the masters from 00:05:26.699 --> 00:05:28.610 align:start position:0% holder completed the masters from particular<00:05:27.120> University<00:05:27.539> the<00:05:28.020> holder<00:05:28.440> will 00:05:28.610 --> 00:05:28.620 align:start position:0% particular University the holder will 00:05:28.620 --> 00:05:31.490 align:start position:0% particular University the holder will send<00:05:28.979> the<00:05:29.280> credential<00:05:29.639> to<00:05:29.880> the<00:05:30.000> verifier<00:05:30.500> so 00:05:31.490 --> 00:05:31.500 align:start position:0% send the credential to the verifier so 00:05:31.500 --> 00:05:34.909 align:start position:0% send the credential to the verifier so we<00:05:32.100> want<00:05:32.280> to<00:05:32.400> move<00:05:32.580> to<00:05:32.880> a<00:05:33.060> space<00:05:33.419> of<00:05:34.020> user<00:05:34.680> and 00:05:34.909 --> 00:05:34.919 align:start position:0% we want to move to a space of user and 00:05:34.919 --> 00:05:37.909 align:start position:0% we want to move to a space of user and wallet<00:05:35.340> centricity<00:05:35.940> where<00:05:36.720> the<00:05:37.080> user<00:05:37.380> decides 00:05:37.909 --> 00:05:37.919 align:start position:0% wallet centricity where the user decides 00:05:37.919 --> 00:05:40.490 align:start position:0% wallet centricity where the user decides what<00:05:38.520> data<00:05:38.759> to<00:05:38.820> to<00:05:39.300> share<00:05:39.539> to<00:05:39.840> be<00:05:39.960> shared<00:05:40.380> and 00:05:40.490 --> 00:05:40.500 align:start position:0% what data to to share to be shared and 00:05:40.500 --> 00:05:46.129 align:start position:0% what data to to share to be shared and with<00:05:40.680> whom<00:05:40.919> so<00:05:41.780> a<00:05:42.780> small<00:05:43.139> example<00:05:43.500> of<00:05:43.740> this<00:05:44.100> is 00:05:46.129 --> 00:05:46.139 align:start position:0% with whom so a small example of this is 00:05:46.139 --> 00:05:48.710 align:start position:0% with whom so a small example of this is you<00:05:46.620> have<00:05:46.740> these<00:05:46.919> social<00:05:47.160> media<00:05:47.520> websites<00:05:48.060> and 00:05:48.710 --> 00:05:48.720 align:start position:0% you have these social media websites and 00:05:48.720 --> 00:05:51.290 align:start position:0% you have these social media websites and let's<00:05:49.500> say<00:05:49.680> you<00:05:50.039> have<00:05:50.100> a<00:05:50.280> page<00:05:50.520> there<00:05:50.759> you<00:05:51.120> have 00:05:51.290 --> 00:05:51.300 align:start position:0% let's say you have a page there you have 00:05:51.300 --> 00:05:54.409 align:start position:0% let's say you have a page there you have 100<00:05:51.539> people<00:05:51.960> who<00:05:52.320> follow<00:05:52.500> you<00:05:52.740> and<00:05:53.639> 50<00:05:53.880> posts 00:05:54.409 --> 00:05:54.419 align:start position:0% 100 people who follow you and 50 posts 00:05:54.419 --> 00:05:56.629 align:start position:0% 100 people who follow you and 50 posts and<00:05:54.600> you<00:05:54.720> have<00:05:54.840> several<00:05:55.199> likes<00:05:55.500> on<00:05:55.680> them<00:05:55.860> so 00:05:56.629 --> 00:05:56.639 align:start position:0% and you have several likes on them so 00:05:56.639 --> 00:05:59.150 align:start position:0% and you have several likes on them so that's<00:05:56.940> one<00:05:57.300> part<00:05:57.479> of<00:05:57.660> the<00:05:57.780> data<00:05:58.139> and<00:05:58.740> then<00:05:58.860> the 00:05:59.150 --> 00:05:59.160 align:start position:0% that's one part of the data and then the 00:05:59.160 --> 00:06:01.610 align:start position:0% that's one part of the data and then the analytics<00:05:59.639> are<00:05:59.820> associated<00:06:00.360> that<00:06:00.900> few<00:06:01.380> people 00:06:01.610 --> 00:06:01.620 align:start position:0% analytics are associated that few people 00:06:01.620 --> 00:06:05.150 align:start position:0% analytics are associated that few people like<00:06:01.919> every<00:06:02.340> of<00:06:02.520> your<00:06:02.699> post<00:06:03.380> uh<00:06:04.380> one<00:06:04.979> of<00:06:05.100> the 00:06:05.150 --> 00:06:05.160 align:start position:0% like every of your post uh one of the 00:06:05.160 --> 00:06:07.249 align:start position:0% like every of your post uh one of the reels<00:06:05.400> got<00:06:05.580> maximum<00:06:06.060> engagement<00:06:06.419> where<00:06:07.080> does 00:06:07.249 --> 00:06:07.259 align:start position:0% reels got maximum engagement where does 00:06:07.259 --> 00:06:08.629 align:start position:0% reels got maximum engagement where does this<00:06:07.380> data<00:06:07.740> live<00:06:07.919> now 00:06:08.629 --> 00:06:08.639 align:start position:0% this data live now 00:06:08.639 --> 00:06:11.150 align:start position:0% this data live now this<00:06:09.240> lives<00:06:09.600> on<00:06:10.020> the<00:06:10.199> intermediary<00:06:10.740> or<00:06:10.979> the 00:06:11.150 --> 00:06:11.160 align:start position:0% this lives on the intermediary or the 00:06:11.160 --> 00:06:13.310 align:start position:0% this lives on the intermediary or the social<00:06:11.280> media's<00:06:11.759> website<00:06:12.060> we<00:06:12.840> want<00:06:13.020> to<00:06:13.139> move 00:06:13.310 --> 00:06:13.320 align:start position:0% social media's website we want to move 00:06:13.320 --> 00:06:16.790 align:start position:0% social media's website we want to move to<00:06:13.560> a<00:06:13.800> world<00:06:14.039> where<00:06:14.759> you<00:06:15.660> own<00:06:16.080> all<00:06:16.380> this<00:06:16.500> data 00:06:16.790 --> 00:06:16.800 align:start position:0% to a world where you own all this data 00:06:16.800 --> 00:06:18.590 align:start position:0% to a world where you own all this data the<00:06:17.039> information<00:06:17.160> and<00:06:17.759> the<00:06:17.940> data<00:06:18.180> analytics 00:06:18.590 --> 00:06:18.600 align:start position:0% the information and the data analytics 00:06:18.600 --> 00:06:21.230 align:start position:0% the information and the data analytics associated<00:06:19.139> with<00:06:19.440> it<00:06:19.620> and<00:06:20.340> hold<00:06:20.580> it<00:06:20.820> in<00:06:21.060> your 00:06:21.230 --> 00:06:21.240 align:start position:0% associated with it and hold it in your 00:06:21.240 --> 00:06:22.670 align:start position:0% associated with it and hold it in your data<00:06:21.720> world 00:06:22.670 --> 00:06:22.680 align:start position:0% data world 00:06:22.680 --> 00:06:25.969 align:start position:0% data world so 00:06:25.969 --> 00:06:25.979 align:start position:0% 00:06:25.979 --> 00:06:28.129 align:start position:0% so<00:06:26.340> this<00:06:26.699> is<00:06:26.880> this<00:06:27.419> is<00:06:27.539> what<00:06:27.780> is<00:06:27.900> happening 00:06:28.129 --> 00:06:28.139 align:start position:0% so this is this is what is happening 00:06:28.139 --> 00:06:30.409 align:start position:0% so this is this is what is happening here 00:06:30.409 --> 00:06:30.419 align:start position:0% here 00:06:30.419 --> 00:06:33.469 align:start position:0% here so<00:06:30.960> today<00:06:31.259> is<00:06:31.680> you<00:06:32.460> are<00:06:32.580> the<00:06:32.759> user<00:06:33.120> the 00:06:33.469 --> 00:06:33.479 align:start position:0% so today is you are the user the 00:06:33.479 --> 00:06:35.689 align:start position:0% so today is you are the user the application<00:06:33.960> and<00:06:34.500> the<00:06:34.740> database<00:06:35.100> sits<00:06:35.639> with 00:06:35.689 --> 00:06:35.699 align:start position:0% application and the database sits with 00:06:35.699 --> 00:06:38.390 align:start position:0% application and the database sits with them<00:06:35.880> but<00:06:36.780> we<00:06:37.080> want<00:06:37.199> to<00:06:37.380> move<00:06:37.620> Spruce<00:06:38.160> mission 00:06:38.390 --> 00:06:38.400 align:start position:0% them but we want to move Spruce mission 00:06:38.400 --> 00:06:40.850 align:start position:0% them but we want to move Spruce mission is<00:06:38.759> to<00:06:38.940> let<00:06:39.120> users<00:06:39.660> control<00:06:39.960> the<00:06:40.199> data<00:06:40.500> across 00:06:40.850 --> 00:06:40.860 align:start position:0% is to let users control the data across 00:06:40.860 --> 00:06:44.450 align:start position:0% is to let users control the data across the<00:06:41.039> web<00:06:41.419> and<00:06:42.419> we<00:06:42.780> like<00:06:42.960> to<00:06:43.139> think<00:06:43.380> that 00:06:44.450 --> 00:06:44.460 align:start position:0% the web and we like to think that 00:06:44.460 --> 00:06:47.570 align:start position:0% the web and we like to think that if<00:06:44.940> platform<00:06:45.419> instead<00:06:45.960> of<00:06:46.020> user<00:06:46.560> going<00:06:47.160> to<00:06:47.400> the 00:06:47.570 --> 00:06:47.580 align:start position:0% if platform instead of user going to the 00:06:47.580 --> 00:06:49.670 align:start position:0% if platform instead of user going to the platform<00:06:48.000> and 00:06:49.670 --> 00:06:49.680 align:start position:0% platform and 00:06:49.680 --> 00:06:51.710 align:start position:0% platform and resting<00:06:50.340> all<00:06:50.520> the<00:06:50.639> control<00:06:50.819> of<00:06:51.120> the<00:06:51.300> data<00:06:51.539> with 00:06:51.710 --> 00:06:51.720 align:start position:0% resting all the control of the data with 00:06:51.720 --> 00:06:54.110 align:start position:0% resting all the control of the data with the<00:06:51.900> platform<00:06:52.199> we<00:06:52.560> want<00:06:52.740> the<00:06:53.100> platform<00:06:53.520> to 00:06:54.110 --> 00:06:54.120 align:start position:0% the platform we want the platform to 00:06:54.120 --> 00:06:56.150 align:start position:0% the platform we want the platform to come<00:06:54.360> to<00:06:54.479> the<00:06:54.660> day<00:06:54.780> come<00:06:55.080> to<00:06:55.259> the<00:06:55.440> user<00:06:55.740> and 00:06:56.150 --> 00:06:56.160 align:start position:0% come to the day come to the user and 00:06:56.160 --> 00:06:58.610 align:start position:0% come to the day come to the user and access<00:06:56.400> the<00:06:56.819> user's<00:06:57.300> Data<00:06:57.600> Vault<00:06:57.780> and<00:06:58.500> that's 00:06:58.610 --> 00:06:58.620 align:start position:0% access the user's Data Vault and that's 00:06:58.620 --> 00:07:01.189 align:start position:0% access the user's Data Vault and that's what's<00:06:58.919> happening<00:06:59.220> over<00:06:59.520> there<00:06:59.759> the<00:07:00.660> database 00:07:01.189 --> 00:07:01.199 align:start position:0% what's happening over there the database 00:07:01.199 --> 00:07:07.790 align:start position:0% what's happening over there the database is<00:07:01.620> with<00:07:01.919> the<00:07:02.100> user 00:07:07.790 --> 00:07:07.800 align:start position:0% 00:07:07.800 --> 00:07:09.469 align:start position:0% so<00:07:08.400> Spruce 00:07:09.469 --> 00:07:09.479 align:start position:0% so Spruce 00:07:09.479 --> 00:07:12.230 align:start position:0% so Spruce um<00:07:09.539> we<00:07:10.139> like<00:07:10.259> to<00:07:10.380> think<00:07:10.560> of<00:07:10.800> ourselves<00:07:11.220> as<00:07:11.759> user 00:07:12.230 --> 00:07:12.240 align:start position:0% um we like to think of ourselves as user 00:07:12.240 --> 00:07:14.469 align:start position:0% um we like to think of ourselves as user control<00:07:12.419> maximalist<00:07:13.139> we<00:07:13.680> want<00:07:13.800> to<00:07:13.919> provide 00:07:14.469 --> 00:07:14.479 align:start position:0% control maximalist we want to provide 00:07:14.479 --> 00:07:17.570 align:start position:0% control maximalist we want to provide maximum<00:07:15.479> user<00:07:15.840> control<00:07:16.139> to<00:07:16.860> all<00:07:17.160> the<00:07:17.280> holders 00:07:17.570 --> 00:07:17.580 align:start position:0% maximum user control to all the holders 00:07:17.580 --> 00:07:20.230 align:start position:0% maximum user control to all the holders of<00:07:17.819> their<00:07:18.000> data<00:07:18.419> and<00:07:19.259> we<00:07:19.560> believe<00:07:19.740> in 00:07:20.230 --> 00:07:20.240 align:start position:0% of their data and we believe in 00:07:20.240 --> 00:07:22.430 align:start position:0% of their data and we believe in self-sovereign<00:07:21.240> identity<00:07:21.720> and<00:07:22.080> that's<00:07:22.199> where 00:07:22.430 --> 00:07:22.440 align:start position:0% self-sovereign identity and that's where 00:07:22.440 --> 00:07:27.409 align:start position:0% self-sovereign identity and that's where we<00:07:22.620> want<00:07:22.740> to<00:07:22.860> move<00:07:23.099> to 00:07:27.409 --> 00:07:27.419 align:start position:0% 00:07:27.419 --> 00:07:30.890 align:start position:0% okay<00:07:27.840> so<00:07:28.740> cue<00:07:29.580> cue<00:07:30.120> is<00:07:30.419> signed<00:07:30.720> in<00:07:30.780> with 00:07:30.890 --> 00:07:30.900 align:start position:0% okay so cue cue is signed in with 00:07:30.900 --> 00:07:33.710 align:start position:0% okay so cue cue is signed in with ethereum<00:07:31.440> that<00:07:31.919> solves<00:07:32.280> a<00:07:32.520> big<00:07:32.639> problem<00:07:32.940> and 00:07:33.710 --> 00:07:33.720 align:start position:0% ethereum that solves a big problem and 00:07:33.720 --> 00:07:35.270 align:start position:0% ethereum that solves a big problem and I'd<00:07:33.840> like<00:07:33.960> for<00:07:34.259> us<00:07:34.380> to<00:07:34.680> understand<00:07:34.919> the 00:07:35.270 --> 00:07:35.280 align:start position:0% I'd like for us to understand the 00:07:35.280 --> 00:07:37.670 align:start position:0% I'd like for us to understand the problem<00:07:35.460> first<00:07:35.940> the<00:07:36.840> problem 00:07:37.670 --> 00:07:37.680 align:start position:0% problem first the problem 00:07:37.680 --> 00:07:39.770 align:start position:0% problem first the problem not<00:07:38.280> really<00:07:38.400> a<00:07:38.639> problem<00:07:38.819> but<00:07:39.240> what<00:07:39.599> is 00:07:39.770 --> 00:07:39.780 align:start position:0% not really a problem but what is 00:07:39.780 --> 00:07:41.870 align:start position:0% not really a problem but what is happening<00:07:40.080> today<00:07:40.259> the<00:07:40.979> big<00:07:41.099> login 00:07:41.870 --> 00:07:41.880 align:start position:0% happening today the big login 00:07:41.880 --> 00:07:44.390 align:start position:0% happening today the big login so<00:07:42.479> when<00:07:42.960> you<00:07:43.259> want<00:07:43.380> to<00:07:43.500> sign<00:07:43.680> into<00:07:43.860> a<00:07:44.160> popular 00:07:44.390 --> 00:07:44.400 align:start position:0% so when you want to sign into a popular 00:07:44.400 --> 00:07:47.029 align:start position:0% so when you want to sign into a popular service<00:07:44.819> you<00:07:45.599> will<00:07:45.720> ideally<00:07:46.080> a<00:07:46.380> user<00:07:46.680> idly 00:07:47.029 --> 00:07:47.039 align:start position:0% service you will ideally a user idly 00:07:47.039 --> 00:07:50.029 align:start position:0% service you will ideally a user idly will<00:07:47.340> use<00:07:47.639> a<00:07:48.180> identity<00:07:48.660> provider<00:07:49.259> which<00:07:49.860> is 00:07:50.029 --> 00:07:50.039 align:start position:0% will use a identity provider which is 00:07:50.039 --> 00:07:52.969 align:start position:0% will use a identity provider which is mostly<00:07:50.460> centralized<00:07:51.180> and<00:07:51.780> has<00:07:52.199> control<00:07:52.500> of 00:07:52.969 --> 00:07:52.979 align:start position:0% mostly centralized and has control of 00:07:52.979 --> 00:07:55.249 align:start position:0% mostly centralized and has control of all<00:07:53.220> the<00:07:53.400> users<00:07:53.699> identifier 00:07:55.249 --> 00:07:55.259 align:start position:0% all the users identifier 00:07:55.259 --> 00:07:57.890 align:start position:0% all the users identifier while<00:07:55.919> they<00:07:56.639> might<00:07:56.819> come<00:07:56.940> with<00:07:57.120> a<00:07:57.300> problem<00:07:57.479> but 00:07:57.890 --> 00:07:57.900 align:start position:0% while they might come with a problem but 00:07:57.900 --> 00:08:00.230 align:start position:0% while they might come with a problem but I<00:07:58.199> think<00:07:58.319> they<00:07:58.919> also<00:07:59.220> have<00:07:59.400> solved<00:07:59.880> for<00:08:00.000> a 00:08:00.230 --> 00:08:00.240 align:start position:0% I think they also have solved for a 00:08:00.240 --> 00:08:02.870 align:start position:0% I think they also have solved for a great<00:08:00.360> user<00:08:00.840> experience<00:08:01.259> case<00:08:02.099> in<00:08:02.340> point<00:08:02.580> a 00:08:02.870 --> 00:08:02.880 align:start position:0% great user experience case in point a 00:08:02.880 --> 00:08:05.570 align:start position:0% great user experience case in point a forgot<00:08:03.180> password<00:08:03.479> I<00:08:04.440> use<00:08:04.620> forgot<00:08:04.979> password<00:08:05.220> on 00:08:05.570 --> 00:08:05.580 align:start position:0% forgot password I use forgot password on 00:08:05.580 --> 00:08:07.070 align:start position:0% forgot password I use forgot password on a<00:08:05.699> regular<00:08:05.880> basis<00:08:06.180> and<00:08:06.360> I'm<00:08:06.539> sure<00:08:06.720> a<00:08:06.960> lot<00:08:07.020> of 00:08:07.070 --> 00:08:07.080 align:start position:0% a regular basis and I'm sure a lot of 00:08:07.080 --> 00:08:09.830 align:start position:0% a regular basis and I'm sure a lot of people<00:08:07.259> here<00:08:07.620> but<00:08:08.280> what<00:08:09.060> if<00:08:09.240> there<00:08:09.539> are<00:08:09.660> few 00:08:09.830 --> 00:08:09.840 align:start position:0% people here but what if there are few 00:08:09.840 --> 00:08:11.870 align:start position:0% people here but what if there are few users<00:08:10.259> sitting<00:08:10.620> here<00:08:10.800> and<00:08:11.039> out<00:08:11.280> there<00:08:11.460> who 00:08:11.870 --> 00:08:11.880 align:start position:0% users sitting here and out there who 00:08:11.880 --> 00:08:14.330 align:start position:0% users sitting here and out there who want<00:08:12.120> to<00:08:12.240> have<00:08:12.419> the<00:08:12.780> option<00:08:13.560> where<00:08:13.979> they<00:08:14.220> want 00:08:14.330 --> 00:08:14.340 align:start position:0% want to have the option where they want 00:08:14.340 --> 00:08:16.730 align:start position:0% want to have the option where they want to<00:08:14.460> have<00:08:14.639> the<00:08:15.000> responsibility<00:08:15.599> or<00:08:16.500> full 00:08:16.730 --> 00:08:16.740 align:start position:0% to have the responsibility or full 00:08:16.740 --> 00:08:19.490 align:start position:0% to have the responsibility or full control<00:08:16.979> over<00:08:17.460> their<00:08:17.759> own<00:08:18.000> data<00:08:18.479> set<00:08:18.599> and<00:08:19.379> that 00:08:19.490 --> 00:08:19.500 align:start position:0% control over their own data set and that 00:08:19.500 --> 00:08:21.650 align:start position:0% control over their own data set and that is<00:08:19.620> what<00:08:19.860> not<00:08:20.039> happens<00:08:20.460> with<00:08:20.879> big<00:08:21.000> logins<00:08:21.539> as 00:08:21.650 --> 00:08:21.660 align:start position:0% is what not happens with big logins as 00:08:21.660 --> 00:08:24.770 align:start position:0% is what not happens with big logins as of<00:08:21.840> today 00:08:24.770 --> 00:08:24.780 align:start position:0% 00:08:24.780 --> 00:08:27.529 align:start position:0% so<00:08:25.620> we<00:08:26.160> want<00:08:26.280> to<00:08:26.460> move<00:08:26.639> from 00:08:27.529 --> 00:08:27.539 align:start position:0% so we want to move from 00:08:27.539 --> 00:08:29.809 align:start position:0% so we want to move from not<00:08:28.080> your<00:08:28.319> keys<00:08:28.620> not<00:08:28.860> your<00:08:28.979> crypto<00:08:29.340> to<00:08:29.520> not 00:08:29.809 --> 00:08:29.819 align:start position:0% not your keys not your crypto to not 00:08:29.819 --> 00:08:32.149 align:start position:0% not your keys not your crypto to not your<00:08:29.940> keys<00:08:30.240> not<00:08:30.419> your<00:08:30.599> identifier<00:08:31.199> or<00:08:31.979> this 00:08:32.149 --> 00:08:32.159 align:start position:0% your keys not your identifier or this 00:08:32.159 --> 00:08:34.310 align:start position:0% your keys not your identifier or this could<00:08:32.279> be<00:08:32.459> not<00:08:32.640> your<00:08:32.820> keys<00:08:33.180> not<00:08:33.419> your<00:08:33.599> data<00:08:34.140> as 00:08:34.310 --> 00:08:34.320 align:start position:0% could be not your keys not your data as 00:08:34.320 --> 00:08:36.829 align:start position:0% could be not your keys not your data as well 00:08:36.829 --> 00:08:36.839 align:start position:0% 00:08:36.839 --> 00:08:38.510 align:start position:0% so<00:08:37.320> I<00:08:37.680> like<00:08:37.800> to<00:08:37.919> do<00:08:38.099> a<00:08:38.219> quick<00:08:38.339> thought 00:08:38.510 --> 00:08:38.520 align:start position:0% so I like to do a quick thought 00:08:38.520 --> 00:08:41.029 align:start position:0% so I like to do a quick thought experiment<00:08:39.060> really<00:08:39.360> to<00:08:39.719> the<00:08:39.839> big<00:08:39.959> login 00:08:41.029 --> 00:08:41.039 align:start position:0% experiment really to the big login 00:08:41.039 --> 00:08:43.130 align:start position:0% experiment really to the big login um<00:08:41.099> I<00:08:41.820> have<00:08:41.940> a<00:08:42.060> Gmail<00:08:42.180> account<00:08:42.479> let's<00:08:42.899> say 00:08:43.130 --> 00:08:43.140 align:start position:0% um I have a Gmail account let's say 00:08:43.140 --> 00:08:45.410 align:start position:0% um I have a Gmail account let's say tomorrow<00:08:43.440> I<00:08:43.919> lose<00:08:44.159> all<00:08:44.700> the<00:08:44.820> access<00:08:44.940> to<00:08:45.240> my 00:08:45.410 --> 00:08:45.420 align:start position:0% tomorrow I lose all the access to my 00:08:45.420 --> 00:08:48.590 align:start position:0% tomorrow I lose all the access to my Gmail<00:08:45.540> account<00:08:45.920> what<00:08:46.920> all<00:08:47.160> will<00:08:47.459> I<00:08:47.640> use<00:08:47.880> the 00:08:48.590 --> 00:08:48.600 align:start position:0% Gmail account what all will I use the 00:08:48.600 --> 00:08:50.810 align:start position:0% Gmail account what all will I use the access<00:08:48.839> to<00:08:49.140> it's<00:08:49.440> not<00:08:49.680> just<00:08:49.860> my<00:08:50.160> emails<00:08:50.580> it 00:08:50.810 --> 00:08:50.820 align:start position:0% access to it's not just my emails it 00:08:50.820 --> 00:08:52.730 align:start position:0% access to it's not just my emails it will<00:08:50.940> be<00:08:51.120> everything<00:08:51.420> that<00:08:52.019> I<00:08:52.200> use<00:08:52.320> my<00:08:52.620> Gmail 00:08:52.730 --> 00:08:52.740 align:start position:0% will be everything that I use my Gmail 00:08:52.740 --> 00:08:55.070 align:start position:0% will be everything that I use my Gmail identifier<00:08:53.459> with<00:08:53.760> for<00:08:54.420> me<00:08:54.540> personally<00:08:54.839> it 00:08:55.070 --> 00:08:55.080 align:start position:0% identifier with for me personally it 00:08:55.080 --> 00:08:56.329 align:start position:0% identifier with for me personally it could<00:08:55.260> be<00:08:55.380> Amazon 00:08:56.329 --> 00:08:56.339 align:start position:0% could be Amazon 00:08:56.339 --> 00:08:58.509 align:start position:0% could be Amazon Etsy<00:08:56.580> uh<00:08:57.360> Uber 00:08:58.509 --> 00:08:58.519 align:start position:0% Etsy uh Uber 00:08:58.519 --> 00:09:03.050 align:start position:0% Etsy uh Uber Airbnb<00:08:59.519> so<00:09:00.420> I<00:09:01.019> am<00:09:01.200> giving<00:09:01.500> a<00:09:02.160> lot<00:09:02.220> of<00:09:02.399> power<00:09:02.640> to 00:09:03.050 --> 00:09:03.060 align:start position:0% Airbnb so I am giving a lot of power to 00:09:03.060 --> 00:09:05.269 align:start position:0% Airbnb so I am giving a lot of power to this<00:09:03.300> another<00:09:03.600> identity<00:09:04.200> I'm<00:09:04.500> at<00:09:04.740> the<00:09:04.860> behest 00:09:05.269 --> 00:09:05.279 align:start position:0% this another identity I'm at the behest 00:09:05.279 --> 00:09:07.850 align:start position:0% this another identity I'm at the behest of<00:09:05.700> this<00:09:05.880> another<00:09:06.120> identity<00:09:06.779> which<00:09:07.380> is 00:09:07.850 --> 00:09:07.860 align:start position:0% of this another identity which is 00:09:07.860 --> 00:09:10.490 align:start position:0% of this another identity which is controlling<00:09:08.279> a<00:09:08.459> lot<00:09:08.580> of<00:09:08.700> my<00:09:08.940> data<00:09:09.240> and<00:09:09.959> who<00:09:10.260> may 00:09:10.490 --> 00:09:10.500 align:start position:0% controlling a lot of my data and who may 00:09:10.500 --> 00:09:12.949 align:start position:0% controlling a lot of my data and who may or<00:09:10.740> may<00:09:10.920> not<00:09:11.100> be<00:09:11.339> incentive<00:09:11.880> and<00:09:12.060> aligned<00:09:12.899> with 00:09:12.949 --> 00:09:12.959 align:start position:0% or may not be incentive and aligned with 00:09:12.959 --> 00:09:14.750 align:start position:0% or may not be incentive and aligned with me<00:09:13.140> all<00:09:13.380> the<00:09:13.560> time 00:09:14.750 --> 00:09:14.760 align:start position:0% me all the time 00:09:14.760 --> 00:09:18.050 align:start position:0% me all the time but<00:09:15.480> if<00:09:15.779> it<00:09:15.899> was<00:09:16.200> Key<00:09:16.620> Management<00:09:16.920> I<00:09:17.880> would 00:09:18.050 --> 00:09:18.060 align:start position:0% but if it was Key Management I would 00:09:18.060 --> 00:09:20.090 align:start position:0% but if it was Key Management I would easily<00:09:18.540> probably<00:09:19.320> learn<00:09:19.680> about<00:09:19.860> key 00:09:20.090 --> 00:09:20.100 align:start position:0% easily probably learn about key 00:09:20.100 --> 00:09:21.829 align:start position:0% easily probably learn about key management<00:09:20.339> or<00:09:21.000> deploy<00:09:21.360> a<00:09:21.540> key<00:09:21.660> management 00:09:21.829 --> 00:09:21.839 align:start position:0% management or deploy a key management 00:09:21.839 --> 00:09:23.810 align:start position:0% management or deploy a key management system<00:09:22.260> and<00:09:22.740> then<00:09:22.860> I'll<00:09:23.160> be<00:09:23.339> able<00:09:23.519> to<00:09:23.640> control 00:09:23.810 --> 00:09:23.820 align:start position:0% system and then I'll be able to control 00:09:23.820 --> 00:09:28.130 align:start position:0% system and then I'll be able to control all<00:09:24.240> my<00:09:24.420> data 00:09:28.130 --> 00:09:28.140 align:start position:0% 00:09:28.140 --> 00:09:31.070 align:start position:0% okay<00:09:28.620> so<00:09:29.220> these<00:09:29.640> are<00:09:29.700> few<00:09:29.880> factual<00:09:30.360> points<00:09:31.080> um 00:09:31.070 --> 00:09:31.080 align:start position:0% okay so these are few factual points um 00:09:31.080 --> 00:09:34.009 align:start position:0% okay so these are few factual points um metamask<00:09:31.680> has<00:09:31.980> done<00:09:32.220> a<00:09:32.519> great<00:09:32.640> job 00:09:34.009 --> 00:09:34.019 align:start position:0% metamask has done a great job 00:09:34.019 --> 00:09:36.410 align:start position:0% metamask has done a great job um<00:09:34.080> last<00:09:34.560> it<00:09:34.980> was<00:09:35.100> seen<00:09:35.339> that<00:09:35.519> we<00:09:35.700> have<00:09:35.880> 21 00:09:36.410 --> 00:09:36.420 align:start position:0% um last it was seen that we have 21 00:09:36.420 --> 00:09:38.509 align:start position:0% um last it was seen that we have 21 million<00:09:36.959> users<00:09:37.380> that's<00:09:37.800> monthly<00:09:38.220> active 00:09:38.509 --> 00:09:38.519 align:start position:0% million users that's monthly active 00:09:38.519 --> 00:09:41.990 align:start position:0% million users that's monthly active users<00:09:38.880> on<00:09:39.180> metamask<00:09:39.720> but<00:09:40.620> as<00:09:40.800> of<00:09:40.980> today<00:09:41.160> we 00:09:41.990 --> 00:09:42.000 align:start position:0% users on metamask but as of today we 00:09:42.000 --> 00:09:44.329 align:start position:0% users on metamask but as of today we just<00:09:42.660> use<00:09:43.019> the<00:09:43.500> transaction<00:09:43.920> the<00:09:44.220> connect 00:09:44.329 --> 00:09:44.339 align:start position:0% just use the transaction the connect 00:09:44.339 --> 00:09:47.030 align:start position:0% just use the transaction the connect wallet<00:09:44.940> to<00:09:45.720> do<00:09:46.140> the<00:09:46.320> transaction<00:09:46.680> the 00:09:47.030 --> 00:09:47.040 align:start position:0% wallet to do the transaction the 00:09:47.040 --> 00:09:48.769 align:start position:0% wallet to do the transaction the financial<00:09:47.220> transactions<00:09:48.060> and<00:09:48.360> that's<00:09:48.540> that's 00:09:48.769 --> 00:09:48.779 align:start position:0% financial transactions and that's that's 00:09:48.779 --> 00:09:52.610 align:start position:0% financial transactions and that's that's about<00:09:49.019> it 00:09:52.610 --> 00:09:52.620 align:start position:0% 00:09:52.620 --> 00:09:55.250 align:start position:0% so<00:09:53.399> how<00:09:53.700> can<00:09:53.880> we<00:09:54.060> better<00:09:54.360> do<00:09:54.959> the<00:09:55.140> connect 00:09:55.250 --> 00:09:55.260 align:start position:0% so how can we better do the connect 00:09:55.260 --> 00:09:57.590 align:start position:0% so how can we better do the connect wallet<00:09:55.800> part 00:09:57.590 --> 00:09:57.600 align:start position:0% wallet part 00:09:57.600 --> 00:09:59.329 align:start position:0% wallet part and<00:09:58.080> that<00:09:58.200> is<00:09:58.260> where<00:09:58.440> sign<00:09:58.680> in<00:09:58.800> with<00:09:58.920> ethereum 00:09:59.329 --> 00:09:59.339 align:start position:0% and that is where sign in with ethereum 00:09:59.339 --> 00:10:02.810 align:start position:0% and that is where sign in with ethereum comes<00:09:59.760> and<00:10:00.480> if<00:10:01.320> you've<00:10:01.620> logged<00:10:01.920> into<00:10:02.100> your 00:10:02.810 --> 00:10:02.820 align:start position:0% comes and if you've logged into your 00:10:02.820 --> 00:10:05.269 align:start position:0% comes and if you've logged into your passport<00:10:03.300> site<00:10:03.720> on<00:10:04.140> Defcon<00:10:04.560> you<00:10:04.980> have<00:10:05.100> the 00:10:05.269 --> 00:10:05.279 align:start position:0% passport site on Defcon you have the 00:10:05.279 --> 00:10:07.009 align:start position:0% passport site on Defcon you have the option<00:10:05.459> of<00:10:05.640> logging<00:10:05.940> in<00:10:06.060> with<00:10:06.180> your<00:10:06.360> email<00:10:06.600> and 00:10:07.009 --> 00:10:07.019 align:start position:0% option of logging in with your email and 00:10:07.019 --> 00:10:09.230 align:start position:0% option of logging in with your email and with<00:10:07.200> sign<00:10:07.440> in<00:10:07.560> with<00:10:07.740> ethereum<00:10:08.160> that<00:10:08.820> is<00:10:08.940> what 00:10:09.230 --> 00:10:09.240 align:start position:0% with sign in with ethereum that is what 00:10:09.240 --> 00:10:11.150 align:start position:0% with sign in with ethereum that is what Spruce<00:10:09.660> uh<00:10:10.320> sign<00:10:10.440> in<00:10:10.620> with<00:10:10.740> ethereum 00:10:11.150 --> 00:10:11.160 align:start position:0% Spruce uh sign in with ethereum 00:10:11.160 --> 00:10:14.329 align:start position:0% Spruce uh sign in with ethereum compliant<00:10:11.640> is 00:10:14.329 --> 00:10:14.339 align:start position:0% 00:10:14.339 --> 00:10:16.730 align:start position:0% so<00:10:14.820> a<00:10:14.940> quick<00:10:15.060> history<00:10:15.360> of<00:10:15.779> how<00:10:16.260> Simon<00:10:16.680> with 00:10:16.730 --> 00:10:16.740 align:start position:0% so a quick history of how Simon with 00:10:16.740 --> 00:10:18.470 align:start position:0% so a quick history of how Simon with ethereum<00:10:17.100> came<00:10:17.339> into<00:10:17.459> being 00:10:18.470 --> 00:10:18.480 align:start position:0% ethereum came into being 00:10:18.480 --> 00:10:21.110 align:start position:0% ethereum came into being um I<00:10:18.720> think<00:10:18.839> summer<00:10:19.080> of<00:10:19.320> 2021<00:10:20.120> ethereum 00:10:21.110 --> 00:10:21.120 align:start position:0% um I think summer of 2021 ethereum 00:10:21.120 --> 00:10:24.889 align:start position:0% um I think summer of 2021 ethereum foundation<00:10:21.600> and<00:10:21.959> ens<00:10:22.440> Dao<00:10:22.800> released<00:10:23.160> RFP<00:10:24.060> and 00:10:24.889 --> 00:10:24.899 align:start position:0% foundation and ens Dao released RFP and 00:10:24.899 --> 00:10:27.290 align:start position:0% foundation and ens Dao released RFP and called<00:10:25.080> for<00:10:25.380> proposals<00:10:26.100> on 00:10:27.290 --> 00:10:27.300 align:start position:0% called for proposals on 00:10:27.300 --> 00:10:30.230 align:start position:0% called for proposals on and<00:10:27.779> requesting<00:10:28.380> for<00:10:28.920> spec<00:10:29.339> which<00:10:29.820> included 00:10:30.230 --> 00:10:30.240 align:start position:0% and requesting for spec which included 00:10:30.240 --> 00:10:33.110 align:start position:0% and requesting for spec which included reference<00:10:30.660> implementation<00:10:31.320> of<00:10:32.220> JavaScript 00:10:33.110 --> 00:10:33.120 align:start position:0% reference implementation of JavaScript 00:10:33.120 --> 00:10:35.870 align:start position:0% reference implementation of JavaScript and<00:10:33.959> backwards<00:10:34.440> compati<00:10:34.920> compatibility<00:10:35.519> mode 00:10:35.870 --> 00:10:35.880 align:start position:0% and backwards compati compatibility mode 00:10:35.880 --> 00:10:40.009 align:start position:0% and backwards compati compatibility mode with<00:10:36.600> open<00:10:37.380> ID<00:10:37.740> connect<00:10:38.279> and<00:10:38.760> oauth<00:10:39.360> so<00:10:39.779> that 00:10:40.009 --> 00:10:40.019 align:start position:0% with open ID connect and oauth so that 00:10:40.019 --> 00:10:42.350 align:start position:0% with open ID connect and oauth so that people<00:10:40.560> or<00:10:40.860> users<00:10:41.220> on<00:10:41.399> the<00:10:41.519> webto<00:10:41.820> world<00:10:42.000> can 00:10:42.350 --> 00:10:42.360 align:start position:0% people or users on the webto world can 00:10:42.360 --> 00:10:45.470 align:start position:0% people or users on the webto world can also<00:10:42.720> use<00:10:43.019> sign<00:10:43.440> in<00:10:43.620> with<00:10:43.800> ethereum 00:10:45.470 --> 00:10:45.480 align:start position:0% also use sign in with ethereum 00:10:45.480 --> 00:10:47.210 align:start position:0% also use sign in with ethereum and<00:10:45.839> this<00:10:45.959> was<00:10:46.079> right<00:10:46.380> after<00:10:46.560> the<00:10:46.800> vitalik 00:10:47.210 --> 00:10:47.220 align:start position:0% and this was right after the vitalik 00:10:47.220 --> 00:10:49.130 align:start position:0% and this was right after the vitalik stock<00:10:47.399> at<00:10:47.579> ECC<00:10:47.940> where<00:10:48.360> he<00:10:48.540> talked<00:10:48.779> about<00:10:48.839> the 00:10:49.130 --> 00:10:49.140 align:start position:0% stock at ECC where he talked about the 00:10:49.140 --> 00:10:51.350 align:start position:0% stock at ECC where he talked about the importance<00:10:49.440> of<00:10:49.620> identity<00:10:50.160> and<00:10:50.940> that<00:10:51.060> is<00:10:51.180> when 00:10:51.350 --> 00:10:51.360 align:start position:0% importance of identity and that is when 00:10:51.360 --> 00:10:52.910 align:start position:0% importance of identity and that is when people<00:10:51.540> realized<00:10:52.140> there<00:10:52.440> could<00:10:52.620> be<00:10:52.680> a<00:10:52.800> bunch 00:10:52.910 --> 00:10:52.920 align:start position:0% people realized there could be a bunch 00:10:52.920 --> 00:10:55.250 align:start position:0% people realized there could be a bunch of<00:10:53.040> use<00:10:53.220> cases<00:10:53.519> with<00:10:53.820> sign<00:10:54.000> in<00:10:54.180> with<00:10:54.300> ethereum 00:10:55.250 --> 00:10:55.260 align:start position:0% of use cases with sign in with ethereum 00:10:55.260 --> 00:10:57.670 align:start position:0% of use cases with sign in with ethereum there<00:10:55.800> was<00:10:55.920> a<00:10:56.040> call<00:10:56.160> of<00:10:56.459> a<00:10:56.820> lot<00:10:56.880> of<00:10:57.000> RFP 00:10:57.670 --> 00:10:57.680 align:start position:0% there was a call of a lot of RFP 00:10:57.680 --> 00:11:00.170 align:start position:0% there was a call of a lot of RFP proposals<00:10:58.680> and<00:10:59.220> a<00:10:59.339> bunch<00:10:59.459> of<00:10:59.519> proposals<00:11:00.000> was 00:11:00.170 --> 00:11:00.180 align:start position:0% proposals and a bunch of proposals was 00:11:00.180 --> 00:11:01.670 align:start position:0% proposals and a bunch of proposals was submitted<00:11:00.540> and<00:11:00.660> Spruce<00:11:00.899> was<00:11:01.140> lucky<00:11:01.320> enough<00:11:01.500> to 00:11:01.670 --> 00:11:01.680 align:start position:0% submitted and Spruce was lucky enough to 00:11:01.680 --> 00:11:05.990 align:start position:0% submitted and Spruce was lucky enough to be<00:11:01.800> picked<00:11:02.100> up 00:11:05.990 --> 00:11:06.000 align:start position:0% 00:11:06.000 --> 00:11:08.630 align:start position:0% so<00:11:06.480> we<00:11:06.660> developed<00:11:07.019> sign<00:11:07.200> in<00:11:07.320> with<00:11:07.500> ethereum<00:11:08.040> in 00:11:08.630 --> 00:11:08.640 align:start position:0% so we developed sign in with ethereum in 00:11:08.640 --> 00:11:11.030 align:start position:0% so we developed sign in with ethereum in the<00:11:08.820> open<00:11:08.940> on<00:11:09.540> in<00:11:09.899> public<00:11:10.140> there<00:11:10.620> were<00:11:10.740> ton<00:11:10.920> of 00:11:11.030 --> 00:11:11.040 align:start position:0% the open on in public there were ton of 00:11:11.040 --> 00:11:12.769 align:start position:0% the open on in public there were ton of community<00:11:11.279> calls<00:11:11.820> it<00:11:12.000> took<00:11:12.240> seven<00:11:12.420> to<00:11:12.600> eight 00:11:12.769 --> 00:11:12.779 align:start position:0% community calls it took seven to eight 00:11:12.779 --> 00:11:14.810 align:start position:0% community calls it took seven to eight months<00:11:13.079> to<00:11:13.200> develop<00:11:13.560> these<00:11:14.339> specifications 00:11:14.810 --> 00:11:14.820 align:start position:0% months to develop these specifications 00:11:14.820 --> 00:11:18.110 align:start position:0% months to develop these specifications and<00:11:15.300> the<00:11:15.360> whole<00:11:15.540> core<00:11:16.200> libraries<00:11:16.820> and<00:11:17.820> we 00:11:18.110 --> 00:11:18.120 align:start position:0% and the whole core libraries and we 00:11:18.120 --> 00:11:20.030 align:start position:0% and the whole core libraries and we worked<00:11:18.480> with<00:11:18.660> a<00:11:18.959> lot<00:11:19.079> of<00:11:19.140> dabs<00:11:19.560> with<00:11:19.680> a<00:11:19.860> lot<00:11:19.920> of 00:11:20.030 --> 00:11:20.040 align:start position:0% worked with a lot of dabs with a lot of 00:11:20.040 --> 00:11:22.009 align:start position:0% worked with a lot of dabs with a lot of wallets<00:11:20.399> and<00:11:20.940> you<00:11:21.060> can<00:11:21.180> go<00:11:21.300> and<00:11:21.480> check<00:11:21.660> it<00:11:21.839> out 00:11:22.009 --> 00:11:22.019 align:start position:0% wallets and you can go and check it out 00:11:22.019 --> 00:11:25.910 align:start position:0% wallets and you can go and check it out it's<00:11:22.440> called<00:11:22.680> eip4361 00:11:25.910 --> 00:11:25.920 align:start position:0% 00:11:25.920 --> 00:11:28.130 align:start position:0% um that's<00:11:26.220> ethereum<00:11:26.820> Improvement<00:11:27.480> program 00:11:28.130 --> 00:11:28.140 align:start position:0% um that's ethereum Improvement program 00:11:28.140 --> 00:11:29.930 align:start position:0% um that's ethereum Improvement program 4361 00:11:29.930 --> 00:11:29.940 align:start position:0% 4361 00:11:29.940 --> 00:11:32.630 align:start position:0% 4361 and<00:11:30.660> it's<00:11:31.200> very<00:11:31.440> close<00:11:31.620> to<00:11:31.800> be<00:11:32.100> getting 00:11:32.630 --> 00:11:32.640 align:start position:0% and it's very close to be getting 00:11:32.640 --> 00:11:35.389 align:start position:0% and it's very close to be getting approved 00:11:35.389 --> 00:11:35.399 align:start position:0% 00:11:35.399 --> 00:11:38.810 align:start position:0% okay<00:11:36.019> so<00:11:37.019> how<00:11:37.980> do<00:11:38.040> you<00:11:38.160> interact<00:11:38.399> with<00:11:38.579> the<00:11:38.700> web 00:11:38.810 --> 00:11:38.820 align:start position:0% okay so how do you interact with the web 00:11:38.820 --> 00:11:40.190 align:start position:0% okay so how do you interact with the web 3<00:11:39.000> world<00:11:39.240> today 00:11:40.190 --> 00:11:40.200 align:start position:0% 3 world today 00:11:40.200 --> 00:11:42.470 align:start position:0% 3 world today um you<00:11:40.560> go<00:11:40.860> to<00:11:40.980> metamask<00:11:41.399> connect<00:11:41.700> click<00:11:42.420> on 00:11:42.470 --> 00:11:42.480 align:start position:0% um you go to metamask connect click on 00:11:42.480 --> 00:11:44.569 align:start position:0% um you go to metamask connect click on connect<00:11:42.660> wallet<00:11:43.200> and<00:11:43.980> you<00:11:44.279> are<00:11:44.399> there 00:11:44.569 --> 00:11:44.579 align:start position:0% connect wallet and you are there 00:11:44.579 --> 00:11:46.970 align:start position:0% connect wallet and you are there exploring<00:11:45.060> the<00:11:45.180> web<00:11:45.360> 3<00:11:45.600> ecosystem<00:11:46.079> that's 00:11:46.970 --> 00:11:46.980 align:start position:0% exploring the web 3 ecosystem that's 00:11:46.980 --> 00:11:49.730 align:start position:0% exploring the web 3 ecosystem that's about<00:11:47.160> it<00:11:47.399> nothing<00:11:48.060> happens<00:11:48.420> there<00:11:48.899> you<00:11:49.500> are 00:11:49.730 --> 00:11:49.740 align:start position:0% about it nothing happens there you are 00:11:49.740 --> 00:11:51.949 align:start position:0% about it nothing happens there you are proving<00:11:50.040> that<00:11:50.220> you<00:11:50.399> own<00:11:50.579> the<00:11:50.760> public<00:11:50.940> key<00:11:51.300> but 00:11:51.949 --> 00:11:51.959 align:start position:0% proving that you own the public key but 00:11:51.959 --> 00:11:55.250 align:start position:0% proving that you own the public key but not<00:11:52.140> verifying<00:11:52.680> your<00:11:52.740> identity 00:11:55.250 --> 00:11:55.260 align:start position:0% not verifying your identity 00:11:55.260 --> 00:11:56.990 align:start position:0% not verifying your identity so<00:11:55.620> connect<00:11:55.800> wallet<00:11:56.279> you<00:11:56.459> are<00:11:56.579> just<00:11:56.700> proving 00:11:56.990 --> 00:11:57.000 align:start position:0% so connect wallet you are just proving 00:11:57.000 --> 00:11:58.910 align:start position:0% so connect wallet you are just proving to<00:11:57.120> be<00:11:57.240> the<00:11:57.360> account<00:11:57.540> holder<00:11:58.200> without<00:11:58.560> any 00:11:58.910 --> 00:11:58.920 align:start position:0% to be the account holder without any 00:11:58.920 --> 00:12:01.670 align:start position:0% to be the account holder without any proof 00:12:01.670 --> 00:12:01.680 align:start position:0% 00:12:01.680 --> 00:12:03.410 align:start position:0% and<00:12:02.100> that<00:12:02.220> is<00:12:02.339> where<00:12:02.459> sign<00:12:02.700> in<00:12:02.820> with<00:12:02.940> ethereum 00:12:03.410 --> 00:12:03.420 align:start position:0% and that is where sign in with ethereum 00:12:03.420 --> 00:12:06.470 align:start position:0% and that is where sign in with ethereum comes<00:12:03.779> so<00:12:04.380> sign<00:12:05.100> in<00:12:05.339> with<00:12:05.459> ethereum<00:12:06.000> is<00:12:06.240> a 00:12:06.470 --> 00:12:06.480 align:start position:0% comes so sign in with ethereum is a 00:12:06.480 --> 00:12:08.690 align:start position:0% comes so sign in with ethereum is a specification<00:12:07.019> that<00:12:07.440> includes<00:12:07.980> both 00:12:08.690 --> 00:12:08.700 align:start position:0% specification that includes both 00:12:08.700 --> 00:12:12.050 align:start position:0% specification that includes both elements<00:12:09.240> of<00:12:09.779> identity<00:12:10.560> and<00:12:11.399> signing<00:12:11.820> to 00:12:12.050 --> 00:12:12.060 align:start position:0% elements of identity and signing to 00:12:12.060 --> 00:12:13.970 align:start position:0% elements of identity and signing to enable<00:12:12.360> users<00:12:12.720> to<00:12:13.019> take<00:12:13.140> full<00:12:13.440> control<00:12:13.680> over 00:12:13.970 --> 00:12:13.980 align:start position:0% enable users to take full control over 00:12:13.980 --> 00:12:16.310 align:start position:0% enable users to take full control over their<00:12:14.220> data<00:12:14.399> using<00:12:14.940> their<00:12:15.300> ethereum<00:12:15.839> profile 00:12:16.310 --> 00:12:16.320 align:start position:0% their data using their ethereum profile 00:12:16.320 --> 00:12:20.090 align:start position:0% their data using their ethereum profile and<00:12:17.100> ens<00:12:17.880> profile<00:12:18.360> and<00:12:19.320> of<00:12:19.500> course<00:12:19.620> this<00:12:19.980> is 00:12:20.090 --> 00:12:20.100 align:start position:0% and ens profile and of course this is 00:12:20.100 --> 00:12:22.130 align:start position:0% and ens profile and of course this is all<00:12:20.339> open<00:12:20.519> source<00:12:21.060> and<00:12:21.300> that<00:12:21.540> can<00:12:21.660> be<00:12:21.839> checked 00:12:22.130 --> 00:12:22.140 align:start position:0% all open source and that can be checked 00:12:22.140 --> 00:12:24.230 align:start position:0% all open source and that can be checked out 00:12:24.230 --> 00:12:24.240 align:start position:0% out 00:12:24.240 --> 00:12:27.829 align:start position:0% out so<00:12:24.899> Siri<00:12:25.260> has<00:12:25.620> been<00:12:25.800> going<00:12:26.100> on<00:12:26.459> for<00:12:26.880> a<00:12:27.000> while 00:12:27.829 --> 00:12:27.839 align:start position:0% so Siri has been going on for a while 00:12:27.839 --> 00:12:29.449 align:start position:0% so Siri has been going on for a while um<00:12:27.899> I<00:12:28.320> think<00:12:28.440> people<00:12:28.620> have<00:12:28.860> been<00:12:29.040> trying<00:12:29.279> to 00:12:29.449 --> 00:12:29.459 align:start position:0% um I think people have been trying to 00:12:29.459 --> 00:12:31.009 align:start position:0% um I think people have been trying to work<00:12:29.579> with<00:12:29.760> authentication<00:12:30.300> flows<00:12:30.839> on 00:12:31.009 --> 00:12:31.019 align:start position:0% work with authentication flows on 00:12:31.019 --> 00:12:34.910 align:start position:0% work with authentication flows on blockchain<00:12:31.440> accounts<00:12:31.920> since<00:12:32.700> 2016<00:12:33.360> 2017 00:12:34.910 --> 00:12:34.920 align:start position:0% blockchain accounts since 2016 2017 00:12:34.920 --> 00:12:36.829 align:start position:0% blockchain accounts since 2016 2017 and<00:12:35.519> what<00:12:35.820> we've<00:12:36.060> done<00:12:36.240> is<00:12:36.420> we've 00:12:36.829 --> 00:12:36.839 align:start position:0% and what we've done is we've 00:12:36.839 --> 00:12:38.990 align:start position:0% and what we've done is we've standardized<00:12:37.560> the<00:12:37.860> message<00:12:38.160> when<00:12:38.640> you<00:12:38.820> sign 00:12:38.990 --> 00:12:39.000 align:start position:0% standardized the message when you sign 00:12:39.000 --> 00:12:40.730 align:start position:0% standardized the message when you sign in<00:12:39.180> with<00:12:39.300> ethereum<00:12:39.720> it's<00:12:40.019> a<00:12:40.200> standardized 00:12:40.730 --> 00:12:40.740 align:start position:0% in with ethereum it's a standardized 00:12:40.740 --> 00:12:42.949 align:start position:0% in with ethereum it's a standardized message<00:12:41.040> I<00:12:41.940> can<00:12:42.060> show<00:12:42.240> you<00:12:42.300> how<00:12:42.540> it<00:12:42.660> looks<00:12:42.899> like 00:12:42.949 --> 00:12:42.959 align:start position:0% message I can show you how it looks like 00:12:42.959 --> 00:12:45.290 align:start position:0% message I can show you how it looks like in<00:12:43.200> a<00:12:43.320> second<00:12:43.440> and 00:12:45.290 --> 00:12:45.300 align:start position:0% in a second and 00:12:45.300 --> 00:12:47.329 align:start position:0% in a second and sign<00:12:45.660> in<00:12:45.839> with<00:12:45.959> ethereum<00:12:46.500> was<00:12:46.800> developed 00:12:47.329 --> 00:12:47.339 align:start position:0% sign in with ethereum was developed 00:12:47.339 --> 00:12:50.870 align:start position:0% sign in with ethereum was developed heavily<00:12:48.120> with<00:12:48.420> Json<00:12:49.260> web<00:12:49.560> tokens<00:12:50.040> which<00:12:50.579> is<00:12:50.700> of 00:12:50.870 --> 00:12:50.880 align:start position:0% heavily with Json web tokens which is of 00:12:50.880 --> 00:12:52.730 align:start position:0% heavily with Json web tokens which is of course<00:12:51.000> live<00:12:51.240> in<00:12:51.420> production<00:12:51.779> and<00:12:52.320> used<00:12:52.500> by 00:12:52.730 --> 00:12:52.740 align:start position:0% course live in production and used by 00:12:52.740 --> 00:12:57.050 align:start position:0% course live in production and used by billions<00:12:53.100> of<00:12:53.279> users 00:12:57.050 --> 00:12:57.060 align:start position:0% 00:12:57.060 --> 00:12:59.090 align:start position:0% so<00:12:57.600> these<00:12:57.959> are<00:12:58.019> the<00:12:58.139> examples<00:12:58.500> of<00:12:58.860> what 00:12:59.090 --> 00:12:59.100 align:start position:0% so these are the examples of what 00:12:59.100 --> 00:13:01.850 align:start position:0% so these are the examples of what happens<00:12:59.220> as<00:12:59.579> of<00:12:59.760> today<00:12:59.880> you<00:13:00.839> see<00:13:01.019> a<00:13:01.500> random 00:13:01.850 --> 00:13:01.860 align:start position:0% happens as of today you see a random 00:13:01.860 --> 00:13:03.170 align:start position:0% happens as of today you see a random nonce 00:13:03.170 --> 00:13:03.180 align:start position:0% nonce 00:13:03.180 --> 00:13:04.910 align:start position:0% nonce um when<00:13:03.420> you<00:13:03.600> sign<00:13:03.779> in<00:13:03.959> or<00:13:04.200> probably<00:13:04.440> a<00:13:04.620> random 00:13:04.910 --> 00:13:04.920 align:start position:0% um when you sign in or probably a random 00:13:04.920 --> 00:13:06.769 align:start position:0% um when you sign in or probably a random hash<00:13:05.160> which<00:13:05.579> has<00:13:05.760> no<00:13:05.940> meaning<00:13:06.120> to<00:13:06.360> a<00:13:06.480> webto 00:13:06.769 --> 00:13:06.779 align:start position:0% hash which has no meaning to a webto 00:13:06.779 --> 00:13:10.310 align:start position:0% hash which has no meaning to a webto user<00:13:07.200> or<00:13:08.160> sign<00:13:08.459> into<00:13:08.639> my<00:13:09.060> my<00:13:09.300> website<00:13:09.779> or 00:13:10.310 --> 00:13:10.320 align:start position:0% user or sign into my my website or 00:13:10.320 --> 00:13:12.470 align:start position:0% user or sign into my my website or there's<00:13:10.560> a<00:13:10.740> there's<00:13:10.980> a<00:13:11.100> small<00:13:11.339> message<00:13:11.579> but 00:13:12.470 --> 00:13:12.480 align:start position:0% there's a there's a small message but 00:13:12.480 --> 00:13:14.750 align:start position:0% there's a there's a small message but what<00:13:12.720> we've<00:13:12.959> done<00:13:13.139> is<00:13:13.380> we've<00:13:13.860> given<00:13:14.279> a 00:13:14.750 --> 00:13:14.760 align:start position:0% what we've done is we've given a 00:13:14.760 --> 00:13:17.569 align:start position:0% what we've done is we've given a standardized<00:13:15.300> message<00:13:15.899> and<00:13:16.560> a<00:13:16.800> rigid<00:13:17.160> grammar 00:13:17.569 --> 00:13:17.579 align:start position:0% standardized message and a rigid grammar 00:13:17.579 --> 00:13:20.750 align:start position:0% standardized message and a rigid grammar which<00:13:18.180> where<00:13:18.600> there<00:13:19.260> will<00:13:19.500> be<00:13:19.620> no<00:13:20.040> malicious 00:13:20.750 --> 00:13:20.760 align:start position:0% which where there will be no malicious 00:13:20.760 --> 00:13:22.730 align:start position:0% which where there will be no malicious statements<00:13:21.240> can<00:13:21.420> be<00:13:21.540> injected<00:13:21.959> into<00:13:22.200> this<00:13:22.440> and 00:13:22.730 --> 00:13:22.740 align:start position:0% statements can be injected into this and 00:13:22.740 --> 00:13:28.670 align:start position:0% statements can be injected into this and we've<00:13:23.040> purposefully<00:13:23.639> made<00:13:23.940> it<00:13:24.060> that<00:13:24.300> way 00:13:28.670 --> 00:13:28.680 align:start position:0% 00:13:28.680 --> 00:13:33.829 align:start position:0% so 00:13:33.829 --> 00:13:33.839 align:start position:0% 00:13:33.839 --> 00:13:35.750 align:start position:0% so<00:13:34.139> basically<00:13:34.620> we've<00:13:34.980> standardized<00:13:35.519> the 00:13:35.750 --> 00:13:35.760 align:start position:0% so basically we've standardized the 00:13:35.760 --> 00:13:38.629 align:start position:0% so basically we've standardized the message<00:13:36.000> to<00:13:36.839> give<00:13:37.019> the<00:13:37.260> user<00:13:37.560> a<00:13:37.860> great<00:13:37.920> ux 00:13:38.629 --> 00:13:38.639 align:start position:0% message to give the user a great ux 00:13:38.639 --> 00:13:40.790 align:start position:0% message to give the user a great ux experience<00:13:39.000> user<00:13:39.480> experience<00:13:39.779> but<00:13:40.500> we've 00:13:40.790 --> 00:13:40.800 align:start position:0% experience user experience but we've 00:13:40.800 --> 00:13:43.670 align:start position:0% experience user experience but we've also<00:13:41.040> added<00:13:41.339> few<00:13:41.579> security<00:13:41.940> features<00:13:42.720> and<00:13:43.380> one 00:13:43.670 --> 00:13:43.680 align:start position:0% also added few security features and one 00:13:43.680 --> 00:13:45.290 align:start position:0% also added few security features and one of<00:13:43.740> the<00:13:43.860> most<00:13:44.040> important<00:13:44.459> security<00:13:44.700> features 00:13:45.290 --> 00:13:45.300 align:start position:0% of the most important security features 00:13:45.300 --> 00:13:48.710 align:start position:0% of the most important security features is<00:13:45.779> domain<00:13:46.320> binding<00:13:46.800> so<00:13:47.459> by<00:13:47.639> domain<00:13:48.000> binding<00:13:48.420> I 00:13:48.710 --> 00:13:48.720 align:start position:0% is domain binding so by domain binding I 00:13:48.720 --> 00:13:50.750 align:start position:0% is domain binding so by domain binding I mean<00:13:48.839> when<00:13:49.620> you're<00:13:49.800> trying<00:13:49.980> to<00:13:50.160> collect<00:13:50.399> to<00:13:50.579> a 00:13:50.750 --> 00:13:50.760 align:start position:0% mean when you're trying to collect to a 00:13:50.760 --> 00:13:53.629 align:start position:0% mean when you're trying to collect to a wallet<00:13:51.180> and<00:13:51.779> it<00:13:52.260> says<00:13:52.500> your<00:13:52.680> wallet<00:13:53.040> says<00:13:53.399> that 00:13:53.629 --> 00:13:53.639 align:start position:0% wallet and it says your wallet says that 00:13:53.639 --> 00:13:56.750 align:start position:0% wallet and it says your wallet says that domain<00:13:54.180> for<00:13:54.540> example<00:13:55.279> example.org<00:13:56.279> is<00:13:56.579> trying 00:13:56.750 --> 00:13:56.760 align:start position:0% domain for example example.org is trying 00:13:56.760 --> 00:13:59.269 align:start position:0% domain for example example.org is trying to<00:13:56.940> connect<00:13:57.060> your<00:13:57.360> wallet<00:13:57.720> the<00:13:58.560> wallet<00:13:58.980> will 00:13:59.269 --> 00:13:59.279 align:start position:0% to connect your wallet the wallet will 00:13:59.279 --> 00:14:01.970 align:start position:0% to connect your wallet the wallet will now<00:13:59.519> actually<00:14:00.000> be<00:14:00.660> able<00:14:00.959> to<00:14:01.019> see<00:14:01.320> or<00:14:01.800> the 00:14:01.970 --> 00:14:01.980 align:start position:0% now actually be able to see or the 00:14:01.980 --> 00:14:03.949 align:start position:0% now actually be able to see or the wallet<00:14:02.279> has<00:14:02.519> the<00:14:02.820> opportunity<00:14:03.300> to<00:14:03.779> check 00:14:03.949 --> 00:14:03.959 align:start position:0% wallet has the opportunity to check 00:14:03.959 --> 00:14:06.530 align:start position:0% wallet has the opportunity to check whether<00:14:04.459> example.org<00:14:05.459> is<00:14:05.639> an<00:14:05.820> actual<00:14:06.120> website 00:14:06.530 --> 00:14:06.540 align:start position:0% whether example.org is an actual website 00:14:06.540 --> 00:14:08.949 align:start position:0% whether example.org is an actual website and<00:14:07.500> the<00:14:07.800> request<00:14:08.160> is<00:14:08.339> coming<00:14:08.579> from 00:14:08.949 --> 00:14:08.959 align:start position:0% and the request is coming from 00:14:08.959 --> 00:14:12.530 align:start position:0% and the request is coming from example.org<00:14:10.160> this<00:14:11.160> happens<00:14:11.339> over<00:14:11.760> a<00:14:12.000> TLS 00:14:12.530 --> 00:14:12.540 align:start position:0% example.org this happens over a TLS 00:14:12.540 --> 00:14:15.110 align:start position:0% example.org this happens over a TLS connection<00:14:12.779> so<00:14:13.500> the<00:14:13.800> wallet<00:14:14.100> can<00:14:14.279> say<00:14:14.579> with 00:14:15.110 --> 00:14:15.120 align:start position:0% connection so the wallet can say with 00:14:15.120 --> 00:14:17.810 align:start position:0% connection so the wallet can say with pretty<00:14:15.600> con<00:14:16.440> with<00:14:17.100> pretty<00:14:17.279> much<00:14:17.399> confidence 00:14:17.810 --> 00:14:17.820 align:start position:0% pretty con with pretty much confidence 00:14:17.820 --> 00:14:19.850 align:start position:0% pretty con with pretty much confidence that<00:14:18.300> this<00:14:18.779> is<00:14:18.899> not<00:14:19.079> a<00:14:19.200> phishing<00:14:19.500> site<00:14:19.680> an 00:14:19.850 --> 00:14:19.860 align:start position:0% that this is not a phishing site an 00:14:19.860 --> 00:14:24.290 align:start position:0% that this is not a phishing site an example.org<00:14:20.700> is<00:14:20.880> an<00:14:21.060> actual<00:14:21.360> site 00:14:24.290 --> 00:14:24.300 align:start position:0% 00:14:24.300 --> 00:14:25.730 align:start position:0% so 00:14:25.730 --> 00:14:25.740 align:start position:0% so 00:14:25.740 --> 00:14:30.470 align:start position:0% so and<00:14:26.279> this<00:14:26.459> is<00:14:26.579> this<00:14:26.880> is<00:14:26.940> the<00:14:27.120> example<00:14:27.480> of<00:14:27.720> that 00:14:30.470 --> 00:14:30.480 align:start position:0% 00:14:30.480 --> 00:14:32.870 align:start position:0% and<00:14:30.959> the<00:14:31.139> wallet<00:14:31.620> will<00:14:31.800> keep<00:14:32.040> on<00:14:32.160> popping<00:14:32.700> up 00:14:32.870 --> 00:14:32.880 align:start position:0% and the wallet will keep on popping up 00:14:32.880 --> 00:14:34.850 align:start position:0% and the wallet will keep on popping up messages<00:14:33.120> give<00:14:33.779> will<00:14:34.079> give<00:14:34.260> you<00:14:34.440> messages 00:14:34.850 --> 00:14:34.860 align:start position:0% messages give will give you messages 00:14:34.860 --> 00:14:37.009 align:start position:0% messages give will give you messages probably<00:14:35.339> three<00:14:35.639> or<00:14:35.880> four<00:14:36.000> times<00:14:36.240> to<00:14:36.600> warn<00:14:36.959> you 00:14:37.009 --> 00:14:37.019 align:start position:0% probably three or four times to warn you 00:14:37.019 --> 00:14:39.490 align:start position:0% probably three or four times to warn you that<00:14:37.200> this<00:14:37.380> is<00:14:37.500> a<00:14:37.620> phishing<00:14:37.860> site<00:14:38.160> in<00:14:38.880> case 00:14:39.490 --> 00:14:39.500 align:start position:0% that this is a phishing site in case 00:14:39.500 --> 00:14:44.990 align:start position:0% that this is a phishing site in case example.org<00:14:40.500> is<00:14:41.040> not<00:14:41.220> what<00:14:41.459> it<00:14:41.579> claims<00:14:41.880> to<00:14:42.000> be 00:14:44.990 --> 00:14:45.000 align:start position:0% 00:14:45.000 --> 00:14:47.629 align:start position:0% so<00:14:45.300> that's<00:14:45.600> how<00:14:45.899> it<00:14:46.139> will<00:14:46.260> look<00:14:46.440> like<00:14:46.680> the<00:14:47.399> sign 00:14:47.629 --> 00:14:47.639 align:start position:0% so that's how it will look like the sign 00:14:47.639 --> 00:14:50.870 align:start position:0% so that's how it will look like the sign in<00:14:47.880> with<00:14:48.000> ethereum<00:14:48.480> and<00:14:49.019> if<00:14:49.380> you<00:14:49.620> were<00:14:50.279> signing 00:14:50.870 --> 00:14:50.880 align:start position:0% in with ethereum and if you were signing 00:14:50.880 --> 00:14:53.329 align:start position:0% in with ethereum and if you were signing on<00:14:51.120> the<00:14:51.240> Defcon<00:14:51.660> app<00:14:52.079> using<00:14:52.920> sign<00:14:53.040> in<00:14:53.220> with 00:14:53.329 --> 00:14:53.339 align:start position:0% on the Defcon app using sign in with 00:14:53.339 --> 00:14:54.769 align:start position:0% on the Defcon app using sign in with ethereum<00:14:53.699> that<00:14:53.880> is<00:14:54.000> what<00:14:54.180> it<00:14:54.360> will<00:14:54.480> look<00:14:54.660> like 00:14:54.769 --> 00:14:54.779 align:start position:0% ethereum that is what it will look like 00:14:54.779 --> 00:14:59.350 align:start position:0% ethereum that is what it will look like as<00:14:55.079> of<00:14:55.260> today 00:14:59.350 --> 00:14:59.360 align:start position:0% 00:14:59.360 --> 00:15:02.509 align:start position:0% so<00:15:00.360> as<00:15:01.079> as<00:15:01.260> mentioned<00:15:01.620> before<00:15:01.860> we've 00:15:02.509 --> 00:15:02.519 align:start position:0% so as as mentioned before we've 00:15:02.519 --> 00:15:05.030 align:start position:0% so as as mentioned before we've developed<00:15:03.000> Coe<00:15:03.720> out<00:15:04.019> in<00:15:04.199> the<00:15:04.320> open<00:15:04.380> with<00:15:04.860> all 00:15:05.030 --> 00:15:05.040 align:start position:0% developed Coe out in the open with all 00:15:05.040 --> 00:15:07.430 align:start position:0% developed Coe out in the open with all the<00:15:05.160> community<00:15:05.480> uh<00:15:06.480> with<00:15:06.720> a<00:15:06.839> lot<00:15:06.959> of<00:15:07.079> wallets 00:15:07.430 --> 00:15:07.440 align:start position:0% the community uh with a lot of wallets 00:15:07.440 --> 00:15:09.590 align:start position:0% the community uh with a lot of wallets and<00:15:07.740> devs<00:15:08.100> and<00:15:08.459> these<00:15:08.699> are<00:15:08.820> our<00:15:09.060> initial 00:15:09.590 --> 00:15:09.600 align:start position:0% and devs and these are our initial 00:15:09.600 --> 00:15:12.110 align:start position:0% and devs and these are our initial partners<00:15:10.139> and<00:15:11.040> we<00:15:11.279> will<00:15:11.459> be<00:15:11.579> working<00:15:11.760> very 00:15:12.110 --> 00:15:12.120 align:start position:0% partners and we will be working very 00:15:12.120 --> 00:15:13.850 align:start position:0% partners and we will be working very closely<00:15:12.360> with<00:15:12.600> them<00:15:12.779> in<00:15:13.019> coming<00:15:13.139> months<00:15:13.620> and 00:15:13.850 --> 00:15:13.860 align:start position:0% closely with them in coming months and 00:15:13.860 --> 00:15:16.970 align:start position:0% closely with them in coming months and weeks 00:15:16.970 --> 00:15:16.980 align:start position:0% 00:15:16.980 --> 00:15:22.009 align:start position:0% so<00:15:17.519> what<00:15:17.880> Where<00:15:18.180> Do<00:15:18.360> We<00:15:18.480> Go<00:15:18.600> From<00:15:18.779> Here<00:15:19.019> Siri<00:15:19.560> is 00:15:22.009 --> 00:15:22.019 align:start position:0% so what Where Do We Go From Here Siri is 00:15:22.019 --> 00:15:25.009 align:start position:0% so what Where Do We Go From Here Siri is a<00:15:22.260> basic<00:15:22.980> library<00:15:23.279> that<00:15:23.820> will<00:15:24.000> enable<00:15:24.360> great 00:15:25.009 --> 00:15:25.019 align:start position:0% a basic library that will enable great 00:15:25.019 --> 00:15:26.930 align:start position:0% a basic library that will enable great user<00:15:25.620> experience<00:15:26.040> and<00:15:26.399> will<00:15:26.579> provide 00:15:26.930 --> 00:15:26.940 align:start position:0% user experience and will provide 00:15:26.940 --> 00:15:29.449 align:start position:0% user experience and will provide security<00:15:27.180> features<00:15:27.899> but<00:15:28.620> we<00:15:28.800> are<00:15:28.980> trying<00:15:29.160> to 00:15:29.449 --> 00:15:29.459 align:start position:0% security features but we are trying to 00:15:29.459 --> 00:15:32.629 align:start position:0% security features but we are trying to work<00:15:29.639> with<00:15:30.120> on<00:15:30.779> a<00:15:31.139> bunch<00:15:31.260> of<00:15:31.440> products 00:15:32.629 --> 00:15:32.639 align:start position:0% work with on a bunch of products 00:15:32.639 --> 00:15:33.710 align:start position:0% work with on a bunch of products um<00:15:32.760> where 00:15:33.710 --> 00:15:33.720 align:start position:0% um where 00:15:33.720 --> 00:15:35.629 align:start position:0% um where the<00:15:34.199> data<00:15:34.500> are<00:15:34.620> can<00:15:34.800> be<00:15:34.920> brought<00:15:35.100> in<00:15:35.220> by<00:15:35.459> the 00:15:35.629 --> 00:15:35.639 align:start position:0% the data are can be brought in by the 00:15:35.639 --> 00:15:37.790 align:start position:0% the data are can be brought in by the user<00:15:36.000> so<00:15:36.540> you<00:15:37.079> have<00:15:37.199> Twitter<00:15:37.440> account 00:15:37.790 --> 00:15:37.800 align:start position:0% user so you have Twitter account 00:15:37.800 --> 00:15:39.470 align:start position:0% user so you have Twitter account associated<00:15:38.459> with<00:15:38.699> your<00:15:38.820> ethereum<00:15:39.240> account 00:15:39.470 --> 00:15:39.480 align:start position:0% associated with your ethereum account 00:15:39.480 --> 00:15:41.689 align:start position:0% associated with your ethereum account and<00:15:40.139> you<00:15:40.320> can<00:15:40.440> bring<00:15:40.620> that<00:15:40.920> wherever<00:15:41.339> you<00:15:41.579> want 00:15:41.689 --> 00:15:41.699 align:start position:0% and you can bring that wherever you want 00:15:41.699 --> 00:15:43.730 align:start position:0% and you can bring that wherever you want to<00:15:41.820> it<00:15:42.240> doesn't<00:15:42.600> necessarily<00:15:43.079> have<00:15:43.260> to<00:15:43.440> be<00:15:43.560> on 00:15:43.730 --> 00:15:43.740 align:start position:0% to it doesn't necessarily have to be on 00:15:43.740 --> 00:15:46.610 align:start position:0% to it doesn't necessarily have to be on one<00:15:43.980> side<00:15:44.160> you<00:15:45.000> want<00:15:45.120> to<00:15:45.240> go<00:15:45.480> on<00:15:45.839> uni<00:15:46.199> swap<00:15:46.440> you 00:15:46.610 --> 00:15:46.620 align:start position:0% one side you want to go on uni swap you 00:15:46.620 --> 00:15:48.110 align:start position:0% one side you want to go on uni swap you can<00:15:46.680> you<00:15:46.860> can<00:15:46.980> take<00:15:47.100> your<00:15:47.339> Twitter<00:15:47.519> account<00:15:47.760> or 00:15:48.110 --> 00:15:48.120 align:start position:0% can you can take your Twitter account or 00:15:48.120 --> 00:15:50.269 align:start position:0% can you can take your Twitter account or Facebook<00:15:48.300> account<00:15:48.660> with<00:15:49.079> you<00:15:49.260> so<00:15:49.920> that's<00:15:50.100> your 00:15:50.269 --> 00:15:50.279 align:start position:0% Facebook account with you so that's your 00:15:50.279 --> 00:15:53.629 align:start position:0% Facebook account with you so that's your bring<00:15:50.639> your<00:15:50.820> own<00:15:51.000> data<00:15:51.420> workflow<00:15:52.320> and<00:15:53.040> we<00:15:53.459> are 00:15:53.629 --> 00:15:53.639 align:start position:0% bring your own data workflow and we are 00:15:53.639 --> 00:15:56.030 align:start position:0% bring your own data workflow and we are also<00:15:53.880> working<00:15:54.120> on<00:15:54.420> core<00:15:54.660> libraries<00:15:55.320> and<00:15:55.800> some 00:15:56.030 --> 00:15:56.040 align:start position:0% also working on core libraries and some 00:15:56.040 --> 00:15:59.170 align:start position:0% also working on core libraries and some products<00:15:56.639> where<00:15:57.060> Coe<00:15:57.899> functionality<00:15:58.440> will<00:15:58.800> be 00:15:59.170 --> 00:15:59.180 align:start position:0% products where Coe functionality will be 00:15:59.180 --> 00:16:03.230 align:start position:0% products where Coe functionality will be enhanced<00:16:00.180> and<00:16:01.199> um<00:16:01.320> and<00:16:01.860> being<00:16:02.639> able<00:16:02.880> to<00:16:03.060> work 00:16:03.230 --> 00:16:03.240 align:start position:0% enhanced and um and being able to work 00:16:03.240 --> 00:16:08.509 align:start position:0% enhanced and um and being able to work with<00:16:03.420> wallets<00:16:03.839> and<00:16:03.959> apps<00:16:04.320> very<00:16:04.560> closely 00:16:08.509 --> 00:16:08.519 align:start position:0% 00:16:08.519 --> 00:16:11.030 align:start position:0% so<00:16:09.300> if<00:16:09.540> I<00:16:09.720> were<00:16:09.839> to<00:16:09.959> leave<00:16:10.139> you<00:16:10.380> with<00:16:10.740> few 00:16:11.030 --> 00:16:11.040 align:start position:0% so if I were to leave you with few 00:16:11.040 --> 00:16:13.129 align:start position:0% so if I were to leave you with few thoughts<00:16:12.000> um<00:16:12.000> sign<00:16:12.360> in<00:16:12.600> with<00:16:12.720> in<00:16:12.959> with 00:16:13.129 --> 00:16:13.139 align:start position:0% thoughts um sign in with in with 00:16:13.139 --> 00:16:15.710 align:start position:0% thoughts um sign in with in with ethereum<00:16:13.620> provides<00:16:14.279> with<00:16:14.639> you<00:16:15.240> with<00:16:15.540> a<00:16:15.600> great 00:16:15.710 --> 00:16:15.720 align:start position:0% ethereum provides with you with a great 00:16:15.720 --> 00:16:17.449 align:start position:0% ethereum provides with you with a great user<00:16:16.079> experience<00:16:16.380> so<00:16:16.620> if<00:16:16.800> you<00:16:16.920> are<00:16:17.040> a<00:16:17.160> wallet 00:16:17.449 --> 00:16:17.459 align:start position:0% user experience so if you are a wallet 00:16:17.459 --> 00:16:19.310 align:start position:0% user experience so if you are a wallet or<00:16:17.639> dab<00:16:17.940> you<00:16:18.360> definitely<00:16:18.660> want<00:16:18.839> to<00:16:19.019> use<00:16:19.139> it 00:16:19.310 --> 00:16:19.320 align:start position:0% or dab you definitely want to use it 00:16:19.320 --> 00:16:21.769 align:start position:0% or dab you definitely want to use it because<00:16:19.500> it<00:16:19.740> will<00:16:19.860> help<00:16:20.100> the<00:16:20.399> user<00:16:20.820> especially 00:16:21.769 --> 00:16:21.779 align:start position:0% because it will help the user especially 00:16:21.779 --> 00:16:23.990 align:start position:0% because it will help the user especially a<00:16:21.959> web<00:16:22.079> to<00:16:22.260> user<00:16:22.620> get<00:16:22.800> onboarded<00:16:23.399> onto<00:16:23.820> your 00:16:23.990 --> 00:16:24.000 align:start position:0% a web to user get onboarded onto your 00:16:24.000 --> 00:16:27.050 align:start position:0% a web to user get onboarded onto your wallet<00:16:24.360> or<00:16:24.600> your<00:16:24.779> dab<00:16:25.079> pretty<00:16:25.500> easily<00:16:26.040> and<00:16:26.820> it 00:16:27.050 --> 00:16:27.060 align:start position:0% wallet or your dab pretty easily and it 00:16:27.060 --> 00:16:29.030 align:start position:0% wallet or your dab pretty easily and it provides<00:16:27.480> security<00:16:27.720> for<00:16:28.139> the<00:16:28.320> user<00:16:28.620> as<00:16:28.860> well 00:16:29.030 --> 00:16:29.040 align:start position:0% provides security for the user as well 00:16:29.040 --> 00:16:30.889 align:start position:0% provides security for the user as well so<00:16:29.459> you<00:16:29.760> can<00:16:29.880> definitely<00:16:30.060> avoid<00:16:30.480> the<00:16:30.600> phishing 00:16:30.889 --> 00:16:30.899 align:start position:0% so you can definitely avoid the phishing 00:16:30.899 --> 00:16:34.009 align:start position:0% so you can definitely avoid the phishing aspect<00:16:31.260> and<00:16:32.160> we<00:16:32.399> are<00:16:32.579> trying<00:16:32.940> to<00:16:33.240> build<00:16:33.420> cue 00:16:34.009 --> 00:16:34.019 align:start position:0% aspect and we are trying to build cue 00:16:34.019 --> 00:16:36.350 align:start position:0% aspect and we are trying to build cue and<00:16:34.320> its<00:16:34.620> components<00:16:35.100> more<00:16:35.279> so<00:16:35.760> if<00:16:36.060> you<00:16:36.180> want 00:16:36.350 --> 00:16:36.360 align:start position:0% and its components more so if you want 00:16:36.360 --> 00:16:37.970 align:start position:0% and its components more so if you want to<00:16:36.480> work<00:16:36.660> with<00:16:36.839> us<00:16:37.019> we<00:16:37.259> build<00:16:37.440> in<00:16:37.740> the<00:16:37.860> open 00:16:37.970 --> 00:16:37.980 align:start position:0% to work with us we build in the open 00:16:37.980 --> 00:16:40.129 align:start position:0% to work with us we build in the open please<00:16:38.759> reach<00:16:39.120> out<00:16:39.180> to<00:16:39.360> us 00:16:40.129 --> 00:16:40.139 align:start position:0% please reach out to us 00:16:40.139 --> 00:16:42.230 align:start position:0% please reach out to us um<00:16:40.199> that's<00:16:40.440> my<00:16:40.620> Twitter<00:16:40.740> handle<00:16:41.279> or<00:16:41.699> feel<00:16:42.120> free 00:16:42.230 --> 00:16:42.240 align:start position:0% um that's my Twitter handle or feel free 00:16:42.240 --> 00:16:44.150 align:start position:0% um that's my Twitter handle or feel free to<00:16:42.420> reach<00:16:42.660> out<00:16:42.779> to<00:16:42.959> anyone<00:16:43.380> in<00:16:43.620> the<00:16:43.740> team<00:16:43.860> we 00:16:44.150 --> 00:16:44.160 align:start position:0% to reach out to anyone in the team we 00:16:44.160 --> 00:16:46.670 align:start position:0% to reach out to anyone in the team we are<00:16:44.339> pretty<00:16:44.519> responsive<00:16:45.120> and<00:16:45.839> we'd<00:16:46.440> love<00:16:46.500> to 00:16:46.670 --> 00:16:46.680 align:start position:0% are pretty responsive and we'd love to 00:16:46.680 --> 00:16:48.829 align:start position:0% are pretty responsive and we'd love to work<00:16:46.800> with<00:16:46.980> you<00:16:47.160> guys<00:16:47.399> so<00:16:48.120> yeah<00:16:48.300> thank<00:16:48.720> you 00:16:48.829 --> 00:16:48.839 align:start position:0% work with you guys so yeah thank you 00:16:48.839 --> 00:16:50.899 align:start position:0% work with you guys so yeah thank you everyone