WEBVTT Kind: captions Language: en 00:00:14.740 --> 00:00:17.680 align:start position:0% great<00:00:15.789> thanks<00:00:16.789> for<00:00:16.820> hanging<00:00:17.119> with<00:00:17.150> us<00:00:17.300> on<00:00:17.510> day 00:00:17.680 --> 00:00:17.690 align:start position:0% great thanks for hanging with us on day 00:00:17.690 --> 00:00:21.490 align:start position:0% great thanks for hanging with us on day three<00:00:18.110> and<00:00:18.350> we're<00:00:19.070> you<00:00:19.250> port<00:00:20.140> so<00:00:21.140> it's<00:00:21.350> great 00:00:21.490 --> 00:00:21.500 align:start position:0% three and we're you port so it's great 00:00:21.500 --> 00:00:22.750 align:start position:0% three and we're you port so it's great to<00:00:21.590> be<00:00:21.650> back<00:00:21.710> on<00:00:21.950> stage<00:00:22.070> in<00:00:22.340> front<00:00:22.430> of<00:00:22.610> all<00:00:22.730> of 00:00:22.750 --> 00:00:22.760 align:start position:0% to be back on stage in front of all of 00:00:22.760 --> 00:00:25.000 align:start position:0% to be back on stage in front of all of our<00:00:22.940> friends<00:00:23.270> again<00:00:23.510> so<00:00:23.990> much<00:00:24.770> has<00:00:24.890> happened 00:00:25.000 --> 00:00:25.010 align:start position:0% our friends again so much has happened 00:00:25.010 --> 00:00:27.160 align:start position:0% our friends again so much has happened since<00:00:25.250> last<00:00:25.460> year<00:00:25.970> and<00:00:26.150> we're<00:00:26.810> excited<00:00:27.050> to 00:00:27.160 --> 00:00:27.170 align:start position:0% since last year and we're excited to 00:00:27.170 --> 00:00:28.870 align:start position:0% since last year and we're excited to have<00:00:27.290> the<00:00:27.380> opportunity<00:00:27.950> to<00:00:28.010> share<00:00:28.250> an<00:00:28.640> update 00:00:28.870 --> 00:00:28.880 align:start position:0% have the opportunity to share an update 00:00:28.880 --> 00:00:32.260 align:start position:0% have the opportunity to share an update with<00:00:29.270> you<00:00:29.480> about<00:00:30.380> what<00:00:30.560> we've<00:00:30.680> been<00:00:30.710> doing 00:00:32.260 --> 00:00:32.270 align:start position:0% with you about what we've been doing 00:00:32.270 --> 00:00:35.680 align:start position:0% with you about what we've been doing I'm<00:00:32.660> Michael<00:00:33.020> Sena<00:00:33.460> I'm<00:00:34.460> product<00:00:35.300> lead<00:00:35.450> for 00:00:35.680 --> 00:00:35.690 align:start position:0% I'm Michael Sena I'm product lead for 00:00:35.690 --> 00:00:37.240 align:start position:0% I'm Michael Sena I'm product lead for you<00:00:35.780> port<00:00:36.020> I'm<00:00:36.200> a<00:00:36.260> company<00:00:36.530> by<00:00:36.710> Reuben<00:00:37.070> heck 00:00:37.240 --> 00:00:37.250 align:start position:0% you port I'm a company by Reuben heck 00:00:37.250 --> 00:00:39.010 align:start position:0% you port I'm a company by Reuben heck project<00:00:38.090> lead<00:00:38.270> in<00:00:38.390> Pelle<00:00:38.570> brain<00:00:38.780> guard 00:00:39.010 --> 00:00:39.020 align:start position:0% project lead in Pelle brain guard 00:00:39.020 --> 00:00:41.800 align:start position:0% project lead in Pelle brain guard technical<00:00:39.440> lead<00:00:39.590> and<00:00:40.520> we<00:00:40.880> will<00:00:41.090> spend<00:00:41.720> the 00:00:41.800 --> 00:00:41.810 align:start position:0% technical lead and we will spend the 00:00:41.810 --> 00:00:44.050 align:start position:0% technical lead and we will spend the next<00:00:41.930> 20<00:00:42.260> minutes<00:00:42.489> sharing<00:00:43.489> our<00:00:43.730> progress 00:00:44.050 --> 00:00:44.060 align:start position:0% next 20 minutes sharing our progress 00:00:44.060 --> 00:00:46.030 align:start position:0% next 20 minutes sharing our progress with<00:00:44.270> you<00:00:44.420> so<00:00:45.050> if<00:00:45.200> there's<00:00:45.380> one<00:00:45.710> thing<00:00:45.980> that 00:00:46.030 --> 00:00:46.040 align:start position:0% with you so if there's one thing that 00:00:46.040 --> 00:00:49.350 align:start position:0% with you so if there's one thing that you<00:00:46.399> take<00:00:46.430> away<00:00:46.640> from<00:00:47.140> this<00:00:48.140> presentation 00:00:49.350 --> 00:00:49.360 align:start position:0% you take away from this presentation 00:00:49.360 --> 00:00:52.120 align:start position:0% you take away from this presentation it's<00:00:50.360> that<00:00:50.660> we've<00:00:51.079> built<00:00:51.290> a<00:00:51.530> theorems<00:00:51.890> user 00:00:52.120 --> 00:00:52.130 align:start position:0% it's that we've built a theorems user 00:00:52.130 --> 00:00:55.270 align:start position:0% it's that we've built a theorems user platform<00:00:52.610> so<00:00:52.940> we've<00:00:53.090> been<00:00:53.210> working<00:00:53.360> on<00:00:54.280> we're 00:00:55.270 --> 00:00:55.280 align:start position:0% platform so we've been working on we're 00:00:55.280 --> 00:00:57.729 align:start position:0% platform so we've been working on we're hoping<00:00:55.579> to<00:00:55.640> answer<00:00:55.970> the<00:00:56.120> question<00:00:56.710> what<00:00:57.710> is 00:00:57.729 --> 00:00:57.739 align:start position:0% hoping to answer the question what is 00:00:57.739 --> 00:00:59.590 align:start position:0% hoping to answer the question what is you<00:00:57.980> port<00:00:58.220> we've<00:00:58.730> heard<00:00:58.880> it<00:00:58.970> from<00:00:59.059> so<00:00:59.300> many<00:00:59.420> of 00:00:59.590 --> 00:00:59.600 align:start position:0% you port we've heard it from so many of 00:00:59.600 --> 00:01:04.079 align:start position:0% you port we've heard it from so many of you<00:00:59.809> and<00:00:59.989> it's<00:01:00.710> about<00:01:00.890> time<00:01:01.160> we<00:01:01.790> share<00:01:02.000> it<00:01:02.120> so 00:01:04.079 --> 00:01:04.089 align:start position:0% you and it's about time we share it so 00:01:04.089 --> 00:01:08.980 align:start position:0% you and it's about time we share it so thanks<00:01:05.089> so<00:01:05.799> if<00:01:06.799> you're<00:01:07.520> building<00:01:07.729> an<00:01:08.540> etherium 00:01:08.980 --> 00:01:08.990 align:start position:0% thanks so if you're building an etherium 00:01:08.990 --> 00:01:10.719 align:start position:0% thanks so if you're building an etherium application<00:01:09.530> and<00:01:09.799> your<00:01:09.890> goal<00:01:10.040> is<00:01:10.190> to<00:01:10.220> have<00:01:10.400> end 00:01:10.719 --> 00:01:10.729 align:start position:0% application and your goal is to have end 00:01:10.729 --> 00:01:14.200 align:start position:0% application and your goal is to have end users<00:01:11.170> we<00:01:12.170> should<00:01:12.350> talk<00:01:12.670> because<00:01:13.670> building 00:01:14.200 --> 00:01:14.210 align:start position:0% users we should talk because building 00:01:14.210 --> 00:01:18.820 align:start position:0% users we should talk because building user<00:01:15.200> friendly<00:01:15.710> etherium<00:01:16.100> apps<00:01:16.280> is<00:01:16.460> hard<00:01:17.830> you 00:01:18.820 --> 00:01:18.830 align:start position:0% user friendly etherium apps is hard you 00:01:18.830 --> 00:01:20.590 align:start position:0% user friendly etherium apps is hard you know<00:01:18.950> you<00:01:19.580> need<00:01:19.729> to<00:01:19.820> solve<00:01:20.060> account 00:01:20.590 --> 00:01:20.600 align:start position:0% know you need to solve account 00:01:20.600 --> 00:01:22.240 align:start position:0% know you need to solve account management<00:01:20.900> and<00:01:21.200> login<00:01:21.650> so<00:01:22.010> account 00:01:22.240 --> 00:01:22.250 align:start position:0% management and login so account 00:01:22.250 --> 00:01:25.210 align:start position:0% management and login so account management<00:01:22.640> for<00:01:23.030> users<00:01:23.530> in<00:01:24.530> a<00:01:24.710> way<00:01:24.890> that 00:01:25.210 --> 00:01:25.220 align:start position:0% management for users in a way that 00:01:25.220 --> 00:01:27.640 align:start position:0% management for users in a way that begins<00:01:25.820> to<00:01:26.090> protect<00:01:26.780> their<00:01:26.900> privacy<00:01:27.260> or 00:01:27.640 --> 00:01:27.650 align:start position:0% begins to protect their privacy or 00:01:27.650 --> 00:01:29.109 align:start position:0% begins to protect their privacy or protects<00:01:28.100> them<00:01:28.250> from<00:01:28.400> themselves<00:01:28.580> and<00:01:28.970> bad 00:01:29.109 --> 00:01:29.119 align:start position:0% protects them from themselves and bad 00:01:29.119 --> 00:01:32.200 align:start position:0% protects them from themselves and bad behavior<00:01:29.570> as<00:01:30.470> an<00:01:30.619> extension<00:01:30.920> of<00:01:31.130> that<00:01:31.189> we<00:01:32.060> have 00:01:32.200 --> 00:01:32.210 align:start position:0% behavior as an extension of that we have 00:01:32.210 --> 00:01:33.820 align:start position:0% behavior as an extension of that we have key<00:01:32.510> management<00:01:32.960> solutions<00:01:33.380> to<00:01:33.530> help<00:01:33.680> your 00:01:33.820 --> 00:01:33.830 align:start position:0% key management solutions to help your 00:01:33.830 --> 00:01:38.560 align:start position:0% key management solutions to help your users<00:01:34.240> avoid<00:01:35.240> danger<00:01:36.220> also<00:01:37.220> we<00:01:38.150> can<00:01:38.299> handle 00:01:38.560 --> 00:01:38.570 align:start position:0% users avoid danger also we can handle 00:01:38.570 --> 00:01:40.870 align:start position:0% users avoid danger also we can handle things<00:01:38.780> like<00:01:39.049> onboarding<00:01:39.680> new<00:01:40.400> users<00:01:40.760> without 00:01:40.870 --> 00:01:40.880 align:start position:0% things like onboarding new users without 00:01:40.880 --> 00:01:44.560 align:start position:0% things like onboarding new users without ether<00:01:41.390> or<00:01:41.420> gas<00:01:42.040> also<00:01:43.060> sort<00:01:44.060> of<00:01:44.090> abstracting 00:01:44.560 --> 00:01:44.570 align:start position:0% ether or gas also sort of abstracting 00:01:44.570 --> 00:01:46.359 align:start position:0% ether or gas also sort of abstracting the<00:01:44.600> concept<00:01:45.020> of<00:01:45.110> gas<00:01:45.320> from<00:01:45.560> end<00:01:45.740> users<00:01:46.070> in 00:01:46.359 --> 00:01:46.369 align:start position:0% the concept of gas from end users in 00:01:46.369 --> 00:01:49.660 align:start position:0% the concept of gas from end users in general<00:01:46.720> we<00:01:47.720> can<00:01:47.869> also<00:01:48.020> do<00:01:48.770> things<00:01:48.979> like<00:01:49.159> know 00:01:49.660 --> 00:01:49.670 align:start position:0% general we can also do things like know 00:01:49.670 --> 00:01:52.480 align:start position:0% general we can also do things like know your<00:01:49.820> user<00:01:50.060> kyc<00:01:50.540> and<00:01:51.409> reputation<00:01:51.740> system<00:01:52.310> so 00:01:52.480 --> 00:01:52.490 align:start position:0% your user kyc and reputation system so 00:01:52.490 --> 00:01:54.609 align:start position:0% your user kyc and reputation system so if<00:01:52.640> you're<00:01:52.759> building<00:01:53.060> an<00:01:53.180> app<00:01:53.720> and<00:01:54.229> your<00:01:54.470> goal 00:01:54.609 --> 00:01:54.619 align:start position:0% if you're building an app and your goal 00:01:54.619 --> 00:01:56.770 align:start position:0% if you're building an app and your goal is<00:01:54.710> to<00:01:54.770> have<00:01:54.860> end<00:01:55.100> users<00:01:55.450> you<00:01:56.450> should<00:01:56.600> probably 00:01:56.770 --> 00:01:56.780 align:start position:0% is to have end users you should probably 00:01:56.780 --> 00:01:59.410 align:start position:0% is to have end users you should probably think<00:01:56.990> about<00:01:57.259> solving<00:01:57.740> these<00:01:57.920> and<00:01:58.759> we<00:01:59.270> have<00:01:59.299> a 00:01:59.410 --> 00:01:59.420 align:start position:0% think about solving these and we have a 00:01:59.420 --> 00:02:03.789 align:start position:0% think about solving these and we have a comprehensive<00:01:59.990> solution<00:02:02.470> and<00:02:03.470> so<00:02:03.650> at<00:02:03.710> a<00:02:03.770> high 00:02:03.789 --> 00:02:03.799 align:start position:0% comprehensive solution and so at a high 00:02:03.799 --> 00:02:04.240 align:start position:0% comprehensive solution and so at a high level 00:02:04.240 --> 00:02:04.250 align:start position:0% level 00:02:04.250 --> 00:02:06.960 align:start position:0% level you<00:02:04.549> port<00:02:04.790> makes<00:02:04.939> a<00:02:05.060> theorem<00:02:05.360> easy<00:02:05.680> you<00:02:06.680> port 00:02:06.960 --> 00:02:06.970 align:start position:0% you port makes a theorem easy you port 00:02:06.970 --> 00:02:10.660 align:start position:0% you port makes a theorem easy you port aetherium<00:02:07.970> today<00:02:08.239> is<00:02:08.420> not<00:02:08.929> really<00:02:09.289> easy<00:02:09.670> you 00:02:10.660 --> 00:02:10.670 align:start position:0% aetherium today is not really easy you 00:02:10.670 --> 00:02:12.850 align:start position:0% aetherium today is not really easy you need<00:02:10.789> to<00:02:10.849> be<00:02:10.970> pretty<00:02:11.180> technical<00:02:11.470> you<00:02:12.470> have<00:02:12.650> to 00:02:12.850 --> 00:02:12.860 align:start position:0% need to be pretty technical you have to 00:02:12.860 --> 00:02:16.380 align:start position:0% need to be pretty technical you have to have<00:02:13.400> an<00:02:13.489> on-ramp<00:02:13.880> to<00:02:14.060> acquire<00:02:14.510> ether<00:02:14.900> or 00:02:16.380 --> 00:02:16.390 align:start position:0% have an on-ramp to acquire ether or 00:02:16.390 --> 00:02:18.210 align:start position:0% have an on-ramp to acquire ether or you<00:02:16.750> need<00:02:16.900> to<00:02:17.050> interact<00:02:17.620> with<00:02:17.890> too<00:02:18.129> many 00:02:18.210 --> 00:02:18.220 align:start position:0% you need to interact with too many 00:02:18.220 --> 00:02:20.520 align:start position:0% you need to interact with too many low-level<00:02:18.819> things<00:02:19.030> in<00:02:19.690> a<00:02:19.780> non<00:02:19.959> user-friendly 00:02:20.520 --> 00:02:20.530 align:start position:0% low-level things in a non user-friendly 00:02:20.530 --> 00:02:22.559 align:start position:0% low-level things in a non user-friendly way<00:02:20.650> so<00:02:20.980> we<00:02:21.069> built<00:02:21.250> four<00:02:21.459> components<00:02:22.030> the 00:02:22.559 --> 00:02:22.569 align:start position:0% way so we built four components the 00:02:22.569 --> 00:02:26.280 align:start position:0% way so we built four components the first<00:02:22.599> are<00:02:23.019> all<00:02:23.590> aetherium<00:02:24.489> app<00:02:24.819> accounts<00:02:25.450> are 00:02:26.280 --> 00:02:26.290 align:start position:0% first are all aetherium app accounts are 00:02:26.290 --> 00:02:28.199 align:start position:0% first are all aetherium app accounts are in<00:02:26.530> one<00:02:26.680> central<00:02:27.010> place<00:02:27.040> for<00:02:27.190> the<00:02:27.430> user<00:02:27.580> that's 00:02:28.199 --> 00:02:28.209 align:start position:0% in one central place for the user that's 00:02:28.209 --> 00:02:31.020 align:start position:0% in one central place for the user that's easy<00:02:28.420> for<00:02:28.540> them<00:02:28.750> to<00:02:28.780> manage<00:02:29.640> users<00:02:30.640> can<00:02:30.819> create 00:02:31.020 --> 00:02:31.030 align:start position:0% easy for them to manage users can create 00:02:31.030 --> 00:02:32.580 align:start position:0% easy for them to manage users can create a<00:02:31.090> complete<00:02:31.420> user<00:02:31.599> profile<00:02:32.049> that<00:02:32.260> they<00:02:32.379> take 00:02:32.580 --> 00:02:32.590 align:start position:0% a complete user profile that they take 00:02:32.590 --> 00:02:33.690 align:start position:0% a complete user profile that they take with<00:02:32.709> them<00:02:32.890> throughout<00:02:33.129> the<00:02:33.280> web<00:02:33.430> as<00:02:33.580> they 00:02:33.690 --> 00:02:33.700 align:start position:0% with them throughout the web as they 00:02:33.700 --> 00:02:36.589 align:start position:0% with them throughout the web as they interact<00:02:34.090> with<00:02:34.150> various<00:02:34.540> applications<00:02:35.190> third 00:02:36.589 --> 00:02:36.599 align:start position:0% interact with various applications third 00:02:36.599 --> 00:02:39.449 align:start position:0% interact with various applications third you<00:02:37.599> port<00:02:37.840> enables<00:02:38.200> the<00:02:38.590> storage<00:02:38.980> the<00:02:39.310> user 00:02:39.449 --> 00:02:39.459 align:start position:0% you port enables the storage the user 00:02:39.459 --> 00:02:41.580 align:start position:0% you port enables the storage the user center<00:02:39.819> storage<00:02:40.090> of<00:02:40.420> credentials<00:02:40.989> and<00:02:41.230> other 00:02:41.580 --> 00:02:41.590 align:start position:0% center storage of credentials and other 00:02:41.590 --> 00:02:45.150 align:start position:0% center storage of credentials and other pieces<00:02:42.340> of<00:02:42.519> sign<00:02:42.849> data<00:02:43.530> that<00:02:44.530> enable<00:02:44.830> a<00:02:44.890> shared 00:02:45.150 --> 00:02:45.160 align:start position:0% pieces of sign data that enable a shared 00:02:45.160 --> 00:02:48.870 align:start position:0% pieces of sign data that enable a shared user<00:02:45.519> centric<00:02:45.849> data<00:02:46.120> platform<00:02:47.040> fourth<00:02:48.040> we 00:02:48.870 --> 00:02:48.880 align:start position:0% user centric data platform fourth we 00:02:48.880 --> 00:02:50.339 align:start position:0% user centric data platform fourth we offer<00:02:49.030> mobile<00:02:49.299> factor<00:02:49.660> authentication<00:02:49.930> and 00:02:50.339 --> 00:02:50.349 align:start position:0% offer mobile factor authentication and 00:02:50.349 --> 00:02:52.460 align:start position:0% offer mobile factor authentication and signatures<00:02:50.739> for<00:02:50.920> everything<00:02:51.310> so<00:02:51.790> basically 00:02:52.460 --> 00:02:52.470 align:start position:0% signatures for everything so basically 00:02:52.470 --> 00:02:56.009 align:start position:0% signatures for everything so basically user<00:02:53.470> clicks<00:02:53.769> a<00:02:53.860> button<00:02:53.890> on<00:02:54.220> your<00:02:54.250> app<00:02:54.549> and<00:02:55.019> we 00:02:56.009 --> 00:02:56.019 align:start position:0% user clicks a button on your app and we 00:02:56.019 --> 00:02:58.470 align:start position:0% user clicks a button on your app and we have<00:02:56.140> a<00:02:56.170> mobile<00:02:56.440> signer<00:02:56.650> so<00:02:57.640> I'll<00:02:58.060> pass<00:02:58.299> it 00:02:58.470 --> 00:02:58.480 align:start position:0% have a mobile signer so I'll pass it 00:02:58.480 --> 00:03:00.300 align:start position:0% have a mobile signer so I'll pass it over<00:02:58.540> to<00:02:58.720> groov<00:02:59.500> an<00:02:59.620> impeller<00:02:59.799> to<00:02:59.920> explain 00:03:00.300 --> 00:03:00.310 align:start position:0% over to groov an impeller to explain 00:03:00.310 --> 00:03:01.650 align:start position:0% over to groov an impeller to explain some<00:03:00.549> more<00:03:00.579> of<00:03:00.790> the<00:03:00.879> technical<00:03:01.239> details<00:03:01.569> and 00:03:01.650 --> 00:03:01.660 align:start position:0% some more of the technical details and 00:03:01.660 --> 00:03:02.940 align:start position:0% some more of the technical details and actually<00:03:01.989> how<00:03:02.079> we<00:03:02.140> implement<00:03:02.650> some<00:03:02.739> of<00:03:02.799> these 00:03:02.940 --> 00:03:02.950 align:start position:0% actually how we implement some of these 00:03:02.950 --> 00:03:05.640 align:start position:0% actually how we implement some of these things<00:03:03.190> but<00:03:03.930> yeah<00:03:04.930> looking<00:03:05.349> forward<00:03:05.530> to 00:03:05.640 --> 00:03:05.650 align:start position:0% things but yeah looking forward to 00:03:05.650 --> 00:03:09.690 align:start position:0% things but yeah looking forward to working<00:03:05.769> with<00:03:05.860> all<00:03:06.010> of<00:03:06.040> you<00:03:07.920> hi<00:03:08.920> so<00:03:09.459> I'm<00:03:09.549> gonna 00:03:09.690 --> 00:03:09.700 align:start position:0% working with all of you hi so I'm gonna 00:03:09.700 --> 00:03:11.819 align:start position:0% working with all of you hi so I'm gonna talk<00:03:10.060> a<00:03:10.269> little<00:03:10.510> bit<00:03:10.750> about<00:03:10.959> how<00:03:11.349> you<00:03:11.410> port 00:03:11.819 --> 00:03:11.829 align:start position:0% talk a little bit about how you port 00:03:11.829 --> 00:03:16.440 align:start position:0% talk a little bit about how you port manages<00:03:12.400> your<00:03:12.640> users<00:03:13.030> accounts<00:03:15.269> au<00:03:16.269> port 00:03:16.440 --> 00:03:16.450 align:start position:0% manages your users accounts au port 00:03:16.450 --> 00:03:20.220 align:start position:0% manages your users accounts au port account<00:03:16.900> is<00:03:17.349> a<00:03:18.569> it's<00:03:19.569> something<00:03:19.930> that<00:03:20.079> we 00:03:20.220 --> 00:03:20.230 align:start position:0% account is a it's something that we 00:03:20.230 --> 00:03:22.710 align:start position:0% account is a it's something that we wanted<00:03:20.590> to<00:03:20.650> create<00:03:21.190> a<00:03:21.519> form<00:03:22.120> of<00:03:22.239> permanence 00:03:22.710 --> 00:03:22.720 align:start position:0% wanted to create a form of permanence 00:03:22.720 --> 00:03:26.640 align:start position:0% wanted to create a form of permanence with<00:03:23.380> and<00:03:24.630> what<00:03:25.630> that<00:03:25.750> means<00:03:26.019> that<00:03:26.290> it<00:03:26.500> is 00:03:26.640 --> 00:03:26.650 align:start position:0% with and what that means that it is 00:03:26.650 --> 00:03:28.559 align:start position:0% with and what that means that it is something<00:03:26.889> that<00:03:27.100> just<00:03:27.670> because<00:03:28.180> you<00:03:28.299> change 00:03:28.559 --> 00:03:28.569 align:start position:0% something that just because you change 00:03:28.569 --> 00:03:31.190 align:start position:0% something that just because you change devices<00:03:29.200> or<00:03:29.380> you<00:03:29.500> lose<00:03:29.680> your<00:03:29.859> phone<00:03:30.069> or 00:03:31.190 --> 00:03:31.200 align:start position:0% devices or you lose your phone or 00:03:31.200 --> 00:03:33.509 align:start position:0% devices or you lose your phone or anything<00:03:32.200> else<00:03:32.470> happens<00:03:32.950> that<00:03:33.190> you<00:03:33.340> should 00:03:33.509 --> 00:03:33.519 align:start position:0% anything else happens that you should 00:03:33.519 --> 00:03:35.900 align:start position:0% anything else happens that you should not<00:03:33.639> lose<00:03:33.880> access<00:03:34.359> to<00:03:34.510> this<00:03:34.660> so<00:03:35.019> we<00:03:35.170> have<00:03:35.380> a 00:03:35.900 --> 00:03:35.910 align:start position:0% not lose access to this so we have a 00:03:35.910 --> 00:03:40.530 align:start position:0% not lose access to this so we have a fairly<00:03:36.910> simple<00:03:37.420> architecture<00:03:38.200> with<00:03:38.440> a<00:03:39.540> your 00:03:40.530 --> 00:03:40.540 align:start position:0% fairly simple architecture with a your 00:03:40.540 --> 00:03:43.199 align:start position:0% fairly simple architecture with a your identity<00:03:41.049> itself<00:03:41.319> represented<00:03:42.010> by<00:03:42.220> a<00:03:42.519> very 00:03:43.199 --> 00:03:43.209 align:start position:0% identity itself represented by a very 00:03:43.209 --> 00:03:46.190 align:start position:0% identity itself represented by a very simple<00:03:43.540> smart<00:03:43.780> contract<00:03:44.260> called<00:03:44.769> a<00:03:45.069> proxy 00:03:46.190 --> 00:03:46.200 align:start position:0% simple smart contract called a proxy 00:03:46.200 --> 00:03:48.659 align:start position:0% simple smart contract called a proxy this<00:03:47.200> is<00:03:47.410> ultimately<00:03:47.950> controlled<00:03:48.459> by<00:03:48.639> a 00:03:48.659 --> 00:03:48.669 align:start position:0% this is ultimately controlled by a 00:03:48.669 --> 00:03:51.089 align:start position:0% this is ultimately controlled by a user's<00:03:49.150> device<00:03:49.419> where<00:03:50.230> the<00:03:50.319> private<00:03:50.530> keys<00:03:50.889> are 00:03:51.089 --> 00:03:51.099 align:start position:0% user's device where the private keys are 00:03:51.099 --> 00:03:53.309 align:start position:0% user's device where the private keys are stored<00:03:51.340> and<00:03:51.700> these<00:03:52.269> private<00:03:52.630> keys<00:03:52.780> never<00:03:53.049> ever 00:03:53.309 --> 00:03:53.319 align:start position:0% stored and these private keys never ever 00:03:53.319 --> 00:03:56.250 align:start position:0% stored and these private keys never ever leave<00:03:53.620> the<00:03:53.799> device<00:03:54.280> in<00:03:54.910> between<00:03:55.180> then<00:03:55.870> there 00:03:56.250 --> 00:03:56.260 align:start position:0% leave the device in between then there 00:03:56.260 --> 00:03:59.039 align:start position:0% leave the device in between then there we<00:03:56.530> have<00:03:56.709> an<00:03:56.859> upgradable<00:03:57.660> access<00:03:58.660> control 00:03:59.039 --> 00:03:59.049 align:start position:0% we have an upgradable access control 00:03:59.049 --> 00:04:01.080 align:start position:0% we have an upgradable access control system<00:03:59.530> a<00:03:59.769> spark<00:04:00.190> contract<00:04:00.609> that<00:04:00.730> we<00:04:00.849> call<00:04:01.000> the 00:04:01.080 --> 00:04:01.090 align:start position:0% system a spark contract that we call the 00:04:01.090 --> 00:04:06.690 align:start position:0% system a spark contract that we call the controller<00:04:02.459> and<00:04:03.459> to<00:04:04.209> handle<00:04:04.480> recovery<00:04:05.700> we 00:04:06.690 --> 00:04:06.700 align:start position:0% controller and to handle recovery we 00:04:06.700 --> 00:04:08.490 align:start position:0% controller and to handle recovery we don't<00:04:06.910> want<00:04:07.180> as<00:04:07.480> I<00:04:07.630> say<00:04:07.750> we<00:04:07.870> don't<00:04:07.989> want<00:04:08.200> people 00:04:08.490 --> 00:04:08.500 align:start position:0% don't want as I say we don't want people 00:04:08.500 --> 00:04:10.920 align:start position:0% don't want as I say we don't want people to<00:04:08.620> lose<00:04:08.739> access<00:04:09.190> to<00:04:09.310> their<00:04:09.459> identities<00:04:09.940> so<00:04:10.359> we 00:04:10.920 --> 00:04:10.930 align:start position:0% to lose access to their identities so we 00:04:10.930 --> 00:04:14.339 align:start position:0% to lose access to their identities so we have<00:04:11.200> this<00:04:11.549> smart<00:04:12.549> contract<00:04:13.090> layer<00:04:13.389> to<00:04:13.959> be 00:04:14.339 --> 00:04:14.349 align:start position:0% have this smart contract layer to be 00:04:14.349 --> 00:04:17.580 align:start position:0% have this smart contract layer to be able<00:04:14.440> to<00:04:14.560> handle<00:04:15.060> recovery<00:04:16.060> of<00:04:16.359> your<00:04:17.229> users 00:04:17.580 --> 00:04:17.590 align:start position:0% able to handle recovery of your users 00:04:17.590 --> 00:04:19.770 align:start position:0% able to handle recovery of your users accounts<00:04:18.010> and<00:04:18.130> identities<00:04:18.609> this<00:04:19.329> allows<00:04:19.570> us 00:04:19.770 --> 00:04:19.780 align:start position:0% accounts and identities this allows us 00:04:19.780 --> 00:04:23.120 align:start position:0% accounts and identities this allows us to<00:04:19.930> do<00:04:20.320> things<00:04:20.470> like<00:04:20.650> social<00:04:21.160> recovery<00:04:21.459> and 00:04:23.120 --> 00:04:23.130 align:start position:0% to do things like social recovery and 00:04:23.130 --> 00:04:28.170 align:start position:0% to do things like social recovery and many<00:04:24.130> other<00:04:24.370> future<00:04:24.760> kinds<00:04:25.150> of<00:04:25.240> recovery 00:04:28.170 --> 00:04:28.180 align:start position:0% 00:04:28.180 --> 00:04:32.219 align:start position:0% so<00:04:28.870> last<00:04:29.320> year<00:04:29.470> we<00:04:30.340> presented<00:04:30.910> a<00:04:31.030> much<00:04:31.780> simpler 00:04:32.219 --> 00:04:32.229 align:start position:0% so last year we presented a much simpler 00:04:32.229 --> 00:04:35.520 align:start position:0% so last year we presented a much simpler model<00:04:32.620> there<00:04:33.220> was<00:04:33.340> one<00:04:33.940> good<00:04:34.750> test<00:04:35.080> network 00:04:35.520 --> 00:04:35.530 align:start position:0% model there was one good test network 00:04:35.530 --> 00:04:37.760 align:start position:0% model there was one good test network Rob<00:04:35.860> stone<00:04:36.130> we<00:04:36.910> had<00:04:37.030> one<00:04:37.240> account 00:04:37.760 --> 00:04:37.770 align:start position:0% Rob stone we had one account 00:04:37.770 --> 00:04:40.469 align:start position:0% Rob stone we had one account representing<00:04:38.770> a<00:04:38.860> users<00:04:39.160> identity<00:04:39.610> you<00:04:40.240> use 00:04:40.469 --> 00:04:40.479 align:start position:0% representing a users identity you use 00:04:40.479 --> 00:04:41.909 align:start position:0% representing a users identity you use this<00:04:40.690> for<00:04:40.900> interacting<00:04:41.530> with<00:04:41.560> all<00:04:41.800> the 00:04:41.909 --> 00:04:41.919 align:start position:0% this for interacting with all the 00:04:41.919 --> 00:04:44.249 align:start position:0% this for interacting with all the different<00:04:42.250> apps<00:04:42.460> and<00:04:42.850> this<00:04:43.600> was<00:04:43.780> a<00:04:43.810> great<00:04:44.080> way 00:04:44.249 --> 00:04:44.259 align:start position:0% different apps and this was a great way 00:04:44.259 --> 00:04:46.200 align:start position:0% different apps and this was a great way to<00:04:44.289> get<00:04:44.590> started<00:04:44.800> lots<00:04:45.280> of<00:04:45.400> developers<00:04:45.910> used 00:04:46.200 --> 00:04:46.210 align:start position:0% to get started lots of developers used 00:04:46.210 --> 00:04:49.200 align:start position:0% to get started lots of developers used it<00:04:47.250> but<00:04:48.250> we<00:04:48.400> started<00:04:48.699> seeing<00:04:48.940> a<00:04:49.060> lot<00:04:49.180> of 00:04:49.200 --> 00:04:49.210 align:start position:0% it but we started seeing a lot of 00:04:49.210 --> 00:04:53.420 align:start position:0% it but we started seeing a lot of changes<00:04:49.600> happening<00:04:49.720> in<00:04:50.020> the<00:04:50.139> etherium<00:04:50.560> world 00:04:53.420 --> 00:04:53.430 align:start position:0% 00:04:53.430 --> 00:04:55.650 align:start position:0% so<00:04:54.430> first<00:04:54.970> of<00:04:55.090> all<00:04:55.150> there<00:04:55.330> are<00:04:55.389> a<00:04:55.449> lot<00:04:55.630> more 00:04:55.650 --> 00:04:55.660 align:start position:0% so first of all there are a lot more 00:04:55.660 --> 00:04:58.110 align:start position:0% so first of all there are a lot more different<00:04:56.320> test<00:04:57.280> networks<00:04:57.669> right<00:04:57.880> now 00:04:58.110 --> 00:04:58.120 align:start position:0% different test networks right now 00:04:58.120 --> 00:04:59.960 align:start position:0% different test networks right now there's<00:04:58.419> also<00:04:58.630> a<00:04:58.720> lot<00:04:58.840> of<00:04:58.960> private<00:04:59.380> chains 00:04:59.960 --> 00:04:59.970 align:start position:0% there's also a lot of private chains 00:04:59.970 --> 00:05:02.430 align:start position:0% there's also a lot of private chains users<00:05:00.970> started<00:05:01.330> having<00:05:01.630> different<00:05:01.960> accounts 00:05:02.430 --> 00:05:02.440 align:start position:0% users started having different accounts 00:05:02.440 --> 00:05:05.189 align:start position:0% users started having different accounts or<00:05:02.560> a<00:05:02.590> lot<00:05:02.740> of<00:05:02.860> more<00:05:03.010> apps<00:05:03.240> in<00:05:04.240> it<00:05:04.510> so<00:05:04.900> this<00:05:05.020> was 00:05:05.189 --> 00:05:05.199 align:start position:0% or a lot of more apps in it so this was 00:05:05.199 --> 00:05:06.570 align:start position:0% or a lot of more apps in it so this was a<00:05:05.229> problem<00:05:05.710> that<00:05:05.740> we<00:05:05.919> couldn't<00:05:06.160> just<00:05:06.370> solve 00:05:06.570 --> 00:05:06.580 align:start position:0% a problem that we couldn't just solve 00:05:06.580 --> 00:05:09.090 align:start position:0% a problem that we couldn't just solve having<00:05:07.000> a<00:05:07.150> single<00:05:07.600> account<00:05:08.199> identity<00:05:08.800> on<00:05:09.070> a 00:05:09.090 --> 00:05:09.100 align:start position:0% having a single account identity on a 00:05:09.100 --> 00:05:13.230 align:start position:0% having a single account identity on a single<00:05:09.789> chain<00:05:11.070> so<00:05:12.070> our<00:05:12.160> new<00:05:12.400> architecture 00:05:13.230 --> 00:05:13.240 align:start position:0% single chain so our new architecture 00:05:13.240 --> 00:05:16.200 align:start position:0% single chain so our new architecture supports<00:05:14.280> multiple<00:05:15.280> accounts<00:05:15.669> and<00:05:15.789> multiple 00:05:16.200 --> 00:05:16.210 align:start position:0% supports multiple accounts and multiple 00:05:16.210 --> 00:05:20.250 align:start position:0% supports multiple accounts and multiple chains<00:05:16.479> and<00:05:17.910> it<00:05:18.910> supports<00:05:19.360> is<00:05:19.599> roughly<00:05:20.139> the 00:05:20.250 --> 00:05:20.260 align:start position:0% chains and it supports is roughly the 00:05:20.260 --> 00:05:23.430 align:start position:0% chains and it supports is roughly the same<00:05:21.389> smart<00:05:22.389> contract<00:05:22.840> structure<00:05:23.199> that<00:05:23.320> we 00:05:23.430 --> 00:05:23.440 align:start position:0% same smart contract structure that we 00:05:23.440 --> 00:05:24.800 align:start position:0% same smart contract structure that we had<00:05:23.590> before<00:05:23.770> but<00:05:24.190> we<00:05:24.340> have<00:05:24.460> obviously 00:05:24.800 --> 00:05:24.810 align:start position:0% had before but we have obviously 00:05:24.810 --> 00:05:27.029 align:start position:0% had before but we have obviously improved<00:05:25.810> our<00:05:25.990> smart<00:05:26.259> contracts<00:05:26.770> they're<00:05:26.919> way 00:05:27.029 --> 00:05:27.039 align:start position:0% improved our smart contracts they're way 00:05:27.039 --> 00:05:29.279 align:start position:0% improved our smart contracts they're way more<00:05:27.250> efficient<00:05:27.699> right<00:05:28.360> now<00:05:28.539> so<00:05:29.020> we<00:05:29.169> can 00:05:29.279 --> 00:05:29.289 align:start position:0% more efficient right now so we can 00:05:29.289 --> 00:05:32.550 align:start position:0% more efficient right now so we can support<00:05:29.650> easily<00:05:30.099> support<00:05:30.490> having<00:05:31.000> a<00:05:31.560> separate 00:05:32.550 --> 00:05:32.560 align:start position:0% support easily support having a separate 00:05:32.560 --> 00:05:35.070 align:start position:0% support easily support having a separate account<00:05:32.979> for<00:05:33.370> each<00:05:33.550> DAP<00:05:34.360> that<00:05:34.720> wants<00:05:34.960> to 00:05:35.070 --> 00:05:35.080 align:start position:0% account for each DAP that wants to 00:05:35.080 --> 00:05:39.029 align:start position:0% account for each DAP that wants to integrate<00:05:35.349> with<00:05:35.740> us<00:05:35.880> per<00:05:36.880> user<00:05:37.150> and<00:05:37.919> we<00:05:38.919> can 00:05:39.029 --> 00:05:39.039 align:start position:0% integrate with us per user and we can 00:05:39.039 --> 00:05:47.279 align:start position:0% integrate with us per user and we can support<00:05:39.340> this<00:05:39.520> over<00:05:39.789> multiple<00:05:40.180> networks<00:05:46.289> the 00:05:47.279 --> 00:05:47.289 align:start position:0% support this over multiple networks the 00:05:47.289 --> 00:05:50.010 align:start position:0% support this over multiple networks the other<00:05:47.440> thing<00:05:47.680> that<00:05:47.710> we<00:05:47.979> learnt<00:05:48.599> over<00:05:49.599> the<00:05:49.900> last 00:05:50.010 --> 00:05:50.020 align:start position:0% other thing that we learnt over the last 00:05:50.020 --> 00:05:52.920 align:start position:0% other thing that we learnt over the last year<00:05:50.380> is<00:05:50.560> that<00:05:50.610> users<00:05:51.610> really<00:05:51.940> want<00:05:52.240> to<00:05:52.599> manage 00:05:52.920 --> 00:05:52.930 align:start position:0% year is that users really want to manage 00:05:52.930 --> 00:05:54.360 align:start position:0% year is that users really want to manage their<00:05:53.110> interactions<00:05:53.740> and<00:05:53.889> for<00:05:54.099> all<00:05:54.220> the 00:05:54.360 --> 00:05:54.370 align:start position:0% their interactions and for all the 00:05:54.370 --> 00:05:57.540 align:start position:0% their interactions and for all the different<00:05:54.699> apps<00:05:54.880> in<00:05:55.389> one<00:05:56.110> place<00:05:56.550> regardless 00:05:57.540 --> 00:05:57.550 align:start position:0% different apps in one place regardless 00:05:57.550 --> 00:06:01.040 align:start position:0% different apps in one place regardless where<00:05:57.820> the<00:05:57.909> app<00:05:58.030> logics<00:05:58.449> run<00:05:58.659> and<00:05:59.099> what<00:06:00.099> this 00:06:01.040 --> 00:06:01.050 align:start position:0% where the app logics run and what this 00:06:01.050 --> 00:06:03.540 align:start position:0% where the app logics run and what this what<00:06:02.050> I'm<00:06:02.169> trying<00:06:02.470> to<00:06:02.500> say<00:06:02.680> with<00:06:02.830> this<00:06:02.979> is<00:06:03.220> a 00:06:03.540 --> 00:06:03.550 align:start position:0% what I'm trying to say with this is a 00:06:03.550 --> 00:06:06.420 align:start position:0% what I'm trying to say with this is a pelagic<00:06:04.090> isn't<00:06:04.630> just<00:06:04.840> run<00:06:05.080> on<00:06:05.320> in<00:06:05.770> the<00:06:05.949> browser 00:06:06.420 --> 00:06:06.430 align:start position:0% pelagic isn't just run on in the browser 00:06:06.430 --> 00:06:10.890 align:start position:0% pelagic isn't just run on in the browser or<00:06:07.860> on<00:06:08.860> multiple<00:06:09.520> aetherium<00:06:09.940> chains<00:06:10.210> they're 00:06:10.890 --> 00:06:10.900 align:start position:0% or on multiple aetherium chains they're 00:06:10.900 --> 00:06:12.450 align:start position:0% or on multiple aetherium chains they're still<00:06:11.229> web<00:06:11.949> 2o 00:06:12.450 --> 00:06:12.460 align:start position:0% still web 2o 00:06:12.460 --> 00:06:14.730 align:start position:0% still web 2o server<00:06:13.090> style<00:06:13.449> apps<00:06:13.690> and<00:06:14.139> there's<00:06:14.470> a<00:06:14.500> lot<00:06:14.620> of 00:06:14.730 --> 00:06:14.740 align:start position:0% server style apps and there's a lot of 00:06:14.740 --> 00:06:17.159 align:start position:0% server style apps and there's a lot of hybrid<00:06:15.159> apps<00:06:15.400> as<00:06:15.610> well<00:06:15.789> in<00:06:15.970> between<00:06:16.360> a<00:06:16.630> new 00:06:17.159 --> 00:06:17.169 align:start position:0% hybrid apps as well in between a new 00:06:17.169 --> 00:06:19.260 align:start position:0% hybrid apps as well in between a new port<00:06:17.440> actually<00:06:17.680> manages<00:06:18.370> account<00:06:18.909> management 00:06:19.260 --> 00:06:19.270 align:start position:0% port actually manages account management 00:06:19.270 --> 00:06:21.750 align:start position:0% port actually manages account management for<00:06:19.659> all<00:06:19.810> of<00:06:19.990> these<00:06:20.139> and<00:06:20.530> it's<00:06:21.400> particularly 00:06:21.750 --> 00:06:21.760 align:start position:0% for all of these and it's particularly 00:06:21.760 --> 00:06:23.969 align:start position:0% for all of these and it's particularly useful<00:06:21.940> for<00:06:22.479> the<00:06:22.570> hybrid<00:06:23.080> solution<00:06:23.740> in<00:06:23.889> the 00:06:23.969 --> 00:06:23.979 align:start position:0% useful for the hybrid solution in the 00:06:23.979 --> 00:06:29.250 align:start position:0% useful for the hybrid solution in the middle<00:06:26.909> so<00:06:27.909> we<00:06:28.300> do<00:06:28.419> this<00:06:28.599> by<00:06:28.810> having<00:06:28.990> the 00:06:29.250 --> 00:06:29.260 align:start position:0% middle so we do this by having the 00:06:29.260 --> 00:06:33.270 align:start position:0% middle so we do this by having the mobile<00:06:29.949> app<00:06:30.900> maintain<00:06:31.900> all<00:06:32.530> the<00:06:32.949> different 00:06:33.270 --> 00:06:33.280 align:start position:0% mobile app maintain all the different 00:06:33.280 --> 00:06:35.279 align:start position:0% mobile app maintain all the different accounts<00:06:33.789> it's<00:06:34.210> a<00:06:34.300> glue<00:06:34.539> that<00:06:34.750> works<00:06:35.020> for 00:06:35.279 --> 00:06:35.289 align:start position:0% accounts it's a glue that works for 00:06:35.289 --> 00:06:40.260 align:start position:0% accounts it's a glue that works for integrating<00:06:36.210> the<00:06:37.210> different<00:06:37.539> apps<00:06:38.969> so<00:06:39.969> for<00:06:40.240> a 00:06:40.260 --> 00:06:40.270 align:start position:0% integrating the different apps so for a 00:06:40.270 --> 00:06:42.800 align:start position:0% integrating the different apps so for a traditional<00:06:40.990> web<00:06:41.229> 3 00:06:42.800 --> 00:06:42.810 align:start position:0% traditional web 3 00:06:42.810 --> 00:06:46.410 align:start position:0% traditional web 3 you<00:06:43.810> write<00:06:44.290> your<00:06:44.530> your<00:06:45.010> app<00:06:45.640> just<00:06:45.700> like<00:06:46.300> you 00:06:46.410 --> 00:06:46.420 align:start position:0% you write your your app just like you 00:06:46.420 --> 00:06:48.600 align:start position:0% you write your your app just like you would<00:06:46.600> normally<00:06:47.050> using<00:06:47.410> web<00:06:47.590> 3<00:06:47.890> or<00:06:48.070> any<00:06:48.160> of<00:06:48.400> the 00:06:48.600 --> 00:06:48.610 align:start position:0% would normally using web 3 or any of the 00:06:48.610 --> 00:06:51.600 align:start position:0% would normally using web 3 or any of the cool<00:06:49.600> new<00:06:49.840> developing<00:06:50.410> developers<00:06:51.220> library 00:06:51.600 --> 00:06:51.610 align:start position:0% cool new developing developers library 00:06:51.610 --> 00:06:54.210 align:start position:0% cool new developing developers library set<00:06:51.790> out<00:06:51.910> there<00:06:52.230> we<00:06:53.230> have<00:06:53.440> au<00:06:53.680> port<00:06:53.860> connect 00:06:54.210 --> 00:06:54.220 align:start position:0% set out there we have au port connect 00:06:54.220 --> 00:06:55.890 align:start position:0% set out there we have au port connect library<00:06:54.670> that<00:06:54.850> automatically<00:06:55.480> takes<00:06:55.750> your 00:06:55.890 --> 00:06:55.900 align:start position:0% library that automatically takes your 00:06:55.900 --> 00:06:57.900 align:start position:0% library that automatically takes your web<00:06:56.050> 3<00:06:56.290> code<00:06:56.530> sends<00:06:57.100> transactions<00:06:57.730> to<00:06:57.880> the 00:06:57.900 --> 00:06:57.910 align:start position:0% web 3 code sends transactions to the 00:06:57.910 --> 00:07:03.180 align:start position:0% web 3 code sends transactions to the phone<00:06:58.860> for<00:06:59.860> web<00:07:00.070> -<00:07:00.280> oh<00:07:00.750> the<00:07:01.750> process<00:07:02.350> is<00:07:02.560> very 00:07:03.180 --> 00:07:03.190 align:start position:0% phone for web - oh the process is very 00:07:03.190 --> 00:07:06.840 align:start position:0% phone for web - oh the process is very similar<00:07:03.760> to<00:07:03.910> say<00:07:04.810> a<00:07:04.840> Facebook<00:07:05.350> connects<00:07:05.850> the 00:07:06.840 --> 00:07:06.850 align:start position:0% similar to say a Facebook connects the 00:07:06.850 --> 00:07:08.880 align:start position:0% similar to say a Facebook connects the only<00:07:07.060> difference<00:07:07.450> of<00:07:07.600> course<00:07:07.780> is<00:07:08.050> that<00:07:08.350> there 00:07:08.880 --> 00:07:08.890 align:start position:0% only difference of course is that there 00:07:08.890 --> 00:07:11.670 align:start position:0% only difference of course is that there are<00:07:08.950> no<00:07:09.010> centralized<00:07:09.520> servers<00:07:09.940> that<00:07:10.690> you 00:07:11.670 --> 00:07:11.680 align:start position:0% are no centralized servers that you 00:07:11.680 --> 00:07:14.340 align:start position:0% are no centralized servers that you interact<00:07:12.130> with<00:07:12.220> and<00:07:12.940> the<00:07:13.600> identity<00:07:14.050> is<00:07:14.110> always 00:07:14.340 --> 00:07:14.350 align:start position:0% interact with and the identity is always 00:07:14.350 --> 00:07:19.850 align:start position:0% interact with and the identity is always under<00:07:14.710> the<00:07:14.800> control<00:07:15.100> of<00:07:15.130> the<00:07:15.400> end<00:07:15.550> user 00:07:19.850 --> 00:07:19.860 align:start position:0% 00:07:19.860 --> 00:07:22.860 align:start position:0% finally<00:07:20.860> a<00:07:21.250> problem<00:07:22.090> that<00:07:22.210> we<00:07:22.330> tried<00:07:22.540> to<00:07:22.660> solve 00:07:22.860 --> 00:07:22.870 align:start position:0% finally a problem that we tried to solve 00:07:22.870 --> 00:07:26.090 align:start position:0% finally a problem that we tried to solve was<00:07:23.520> onboarding<00:07:24.520> of<00:07:24.640> new<00:07:24.790> users<00:07:25.030> a<00:07:25.390> lot<00:07:25.540> of 00:07:26.090 --> 00:07:26.100 align:start position:0% was onboarding of new users a lot of 00:07:26.100 --> 00:07:28.770 align:start position:0% was onboarding of new users a lot of non-technical<00:07:27.100> users<00:07:27.580> and<00:07:27.850> even<00:07:28.210> technical 00:07:28.770 --> 00:07:28.780 align:start position:0% non-technical users and even technical 00:07:28.780 --> 00:07:30.420 align:start position:0% non-technical users and even technical users<00:07:29.080> not<00:07:29.230> familiar<00:07:29.590> with<00:07:29.740> aetherium<00:07:30.220> that 00:07:30.420 --> 00:07:30.430 align:start position:0% users not familiar with aetherium that 00:07:30.430 --> 00:07:32.700 align:start position:0% users not familiar with aetherium that coming<00:07:30.760> in<00:07:31.480> and<00:07:31.810> want<00:07:31.960> to<00:07:32.080> try<00:07:32.290> all<00:07:32.350> of<00:07:32.560> these 00:07:32.700 --> 00:07:32.710 align:start position:0% coming in and want to try all of these 00:07:32.710 --> 00:07:36.660 align:start position:0% coming in and want to try all of these new<00:07:32.890> things<00:07:33.330> and<00:07:34.330> they<00:07:35.230> at<00:07:35.920> the<00:07:36.040> moment<00:07:36.370> we 00:07:36.660 --> 00:07:36.670 align:start position:0% new things and they at the moment we 00:07:36.670 --> 00:07:39.200 align:start position:0% new things and they at the moment we have<00:07:36.880> to<00:07:37.060> every<00:07:37.750> single<00:07:37.930> time<00:07:38.170> explain<00:07:38.650> about 00:07:39.200 --> 00:07:39.210 align:start position:0% have to every single time explain about 00:07:39.210 --> 00:07:41.790 align:start position:0% have to every single time explain about the<00:07:40.210> difference<00:07:40.510> between<00:07:40.570> main<00:07:41.050> net<00:07:41.320> covin 00:07:41.790 --> 00:07:41.800 align:start position:0% the difference between main net covin 00:07:41.800 --> 00:07:42.390 align:start position:0% the difference between main net covin rinkeby 00:07:42.390 --> 00:07:42.400 align:start position:0% rinkeby 00:07:42.400 --> 00:07:44.100 align:start position:0% rinkeby what's<00:07:43.000> gasps<00:07:43.270> how<00:07:43.570> do<00:07:43.630> you<00:07:43.780> fund<00:07:43.990> your 00:07:44.100 --> 00:07:44.110 align:start position:0% what's gasps how do you fund your 00:07:44.110 --> 00:07:46.380 align:start position:0% what's gasps how do you fund your accounts<00:07:44.980> all<00:07:45.160> of<00:07:45.190> these<00:07:45.400> things<00:07:45.640> these<00:07:46.210> are 00:07:46.380 --> 00:07:46.390 align:start position:0% accounts all of these things these are 00:07:46.390 --> 00:07:48.630 align:start position:0% accounts all of these things these are huge<00:07:46.630> problems<00:07:47.050> for<00:07:47.140> most<00:07:47.410> developers<00:07:47.920> when 00:07:48.630 --> 00:07:48.640 align:start position:0% huge problems for most developers when 00:07:48.640 --> 00:07:52.650 align:start position:0% huge problems for most developers when their<00:07:48.790> apps<00:07:48.970> hit<00:07:49.240> real<00:07:49.420> users<00:07:51.090> so<00:07:52.090> the<00:07:52.240> first 00:07:52.650 --> 00:07:52.660 align:start position:0% their apps hit real users so the first 00:07:52.660 --> 00:07:54.120 align:start position:0% their apps hit real users so the first thing<00:07:52.900> that<00:07:52.930> we're<00:07:53.170> doing<00:07:53.200> to<00:07:53.500> solve<00:07:53.680> this<00:07:53.890> is 00:07:54.120 --> 00:07:54.130 align:start position:0% thing that we're doing to solve this is 00:07:54.130 --> 00:07:58.140 align:start position:0% thing that we're doing to solve this is by<00:07:54.190> having<00:07:54.670> a<00:07:54.880> a<00:07:56.190> much<00:07:57.190> smarter<00:07:57.430> login<00:07:57.940> flow 00:07:58.140 --> 00:07:58.150 align:start position:0% by having a a much smarter login flow 00:07:58.150 --> 00:08:00.270 align:start position:0% by having a a much smarter login flow that<00:07:58.390> our<00:07:58.540> first<00:07:58.720> version<00:07:58.990> so<00:07:59.650> a<00:07:59.680> developer 00:08:00.270 --> 00:08:00.280 align:start position:0% that our first version so a developer 00:08:00.280 --> 00:08:03.630 align:start position:0% that our first version so a developer can<00:08:00.430> go<00:08:00.580> in<00:08:00.760> and<00:08:01.410> specify<00:08:02.410> what<00:08:02.950> network<00:08:03.430> that 00:08:03.630 --> 00:08:03.640 align:start position:0% can go in and specify what network that 00:08:03.640 --> 00:08:06.120 align:start position:0% can go in and specify what network that they<00:08:03.760> want<00:08:03.910> account<00:08:04.240> created<00:08:04.720> on<00:08:04.840> and<00:08:05.290> then<00:08:05.860> if 00:08:06.120 --> 00:08:06.130 align:start position:0% they want account created on and then if 00:08:06.130 --> 00:08:08.760 align:start position:0% they want account created on and then if the<00:08:06.460> user<00:08:06.730> already<00:08:06.850> has<00:08:07.240> an<00:08:07.420> accounts<00:08:07.930> for 00:08:08.760 --> 00:08:08.770 align:start position:0% the user already has an accounts for 00:08:08.770 --> 00:08:10.710 align:start position:0% the user already has an accounts for your<00:08:08.980> particular<00:08:09.310> tap<00:08:09.790> on<00:08:10.150> this<00:08:10.360> particular 00:08:10.710 --> 00:08:10.720 align:start position:0% your particular tap on this particular 00:08:10.720 --> 00:08:14.370 align:start position:0% your particular tap on this particular network<00:08:11.290> that<00:08:11.950> will<00:08:12.100> always<00:08:12.340> be<00:08:12.490> returned<00:08:13.380> if 00:08:14.370 --> 00:08:14.380 align:start position:0% network that will always be returned if 00:08:14.380 --> 00:08:16.440 align:start position:0% network that will always be returned if not<00:08:14.680> a<00:08:14.980> new<00:08:15.190> account<00:08:15.520> will<00:08:15.700> be<00:08:15.730> created<00:08:16.030> on<00:08:16.330> the 00:08:16.440 --> 00:08:16.450 align:start position:0% not a new account will be created on the 00:08:16.450 --> 00:08:19.110 align:start position:0% not a new account will be created on the fly<00:08:16.570> and<00:08:17.530> this<00:08:18.130> means<00:08:18.340> that<00:08:18.460> the<00:08:18.640> user<00:08:18.820> never 00:08:19.110 --> 00:08:19.120 align:start position:0% fly and this means that the user never 00:08:19.120 --> 00:08:21.360 align:start position:0% fly and this means that the user never has<00:08:19.360> to<00:08:19.510> worry<00:08:19.690> about<00:08:19.770> whether<00:08:20.770> your<00:08:21.040> app<00:08:21.160> is 00:08:21.360 --> 00:08:21.370 align:start position:0% has to worry about whether your app is 00:08:21.370 --> 00:08:23.580 align:start position:0% has to worry about whether your app is on<00:08:21.520> rinkeby<00:08:21.850> kovin<00:08:22.390> maenette<00:08:22.840> or<00:08:23.050> even 00:08:23.580 --> 00:08:23.590 align:start position:0% on rinkeby kovin maenette or even 00:08:23.590 --> 00:08:29.240 align:start position:0% on rinkeby kovin maenette or even private<00:08:23.980> networks<00:08:27.120> the<00:08:28.120> other<00:08:28.360> big<00:08:28.570> issue<00:08:28.810> is 00:08:29.240 --> 00:08:29.250 align:start position:0% private networks the other big issue is 00:08:29.250 --> 00:08:34.200 align:start position:0% private networks the other big issue is fuel<00:08:30.930> gas<00:08:31.930> is<00:08:32.310> an<00:08:33.310> obvious<00:08:33.670> thing<00:08:33.700> that<00:08:34.030> we<00:08:34.120> all 00:08:34.200 --> 00:08:34.210 align:start position:0% fuel gas is an obvious thing that we all 00:08:34.210 --> 00:08:35.969 align:start position:0% fuel gas is an obvious thing that we all have<00:08:34.420> to<00:08:34.570> pay<00:08:34.750> for<00:08:35.080> our<00:08:35.380> aetherium 00:08:35.969 --> 00:08:35.979 align:start position:0% have to pay for our aetherium 00:08:35.979 --> 00:08:39.570 align:start position:0% have to pay for our aetherium transactions<00:08:36.610> and<00:08:37.770> it's<00:08:38.770> a<00:08:38.950> stumbling<00:08:39.340> block 00:08:39.570 --> 00:08:39.580 align:start position:0% transactions and it's a stumbling block 00:08:39.580 --> 00:08:42.060 align:start position:0% transactions and it's a stumbling block that<00:08:39.610> you<00:08:40.330> know<00:08:41.200> it's<00:08:41.320> very<00:08:41.500> difficult<00:08:41.890> you 00:08:42.060 --> 00:08:42.070 align:start position:0% that you know it's very difficult you 00:08:42.070 --> 00:08:43.860 align:start position:0% that you know it's very difficult you want<00:08:42.280> to<00:08:42.340> get<00:08:42.490> people<00:08:42.820> onto<00:08:42.970> your<00:08:43.270> new<00:08:43.390> app<00:08:43.599> and 00:08:43.860 --> 00:08:43.870 align:start position:0% want to get people onto your new app and 00:08:43.870 --> 00:08:46.590 align:start position:0% want to get people onto your new app and try<00:08:44.050> it<00:08:44.200> but<00:08:44.560> first<00:08:44.740> I<00:08:44.920> need<00:08:45.100> gas<00:08:45.370> they<00:08:46.180> need<00:08:46.360> a 00:08:46.590 --> 00:08:46.600 align:start position:0% try it but first I need gas they need a 00:08:46.600 --> 00:08:49.020 align:start position:0% try it but first I need gas they need a theory<00:08:46.840> or<00:08:46.930> either<00:08:47.170> to<00:08:47.470> pay<00:08:47.770> for<00:08:48.040> pay<00:08:48.760> for<00:08:48.940> the 00:08:49.020 --> 00:08:49.030 align:start position:0% theory or either to pay for pay for the 00:08:49.030 --> 00:08:51.390 align:start position:0% theory or either to pay for pay for the contracts<00:08:49.570> that<00:08:49.780> alone<00:08:50.770> is<00:08:50.980> a<00:08:51.010> big<00:08:51.100> issue 00:08:51.390 --> 00:08:51.400 align:start position:0% contracts that alone is a big issue 00:08:51.400 --> 00:08:55.350 align:start position:0% contracts that alone is a big issue there's<00:08:52.090> also<00:08:52.270> the<00:08:52.480> less<00:08:52.660> obvious<00:08:52.900> issue<00:08:53.410> of 00:08:55.350 --> 00:08:55.360 align:start position:0% there's also the less obvious issue of 00:08:55.360 --> 00:08:58.200 align:start position:0% there's also the less obvious issue of lots<00:08:55.960> of<00:08:56.550> non-technical<00:08:57.550> end-users 00:08:58.200 --> 00:08:58.210 align:start position:0% lots of non-technical end-users 00:08:58.210 --> 00:09:00.300 align:start position:0% lots of non-technical end-users following<00:08:58.600> links<00:08:58.900> on<00:08:59.050> Twitter 00:09:00.300 --> 00:09:00.310 align:start position:0% following links on Twitter 00:09:00.310 --> 00:09:02.820 align:start position:0% following links on Twitter sending<00:09:01.030> main<00:09:01.270> net<00:09:01.510> eath<00:09:01.720> to<00:09:02.050> a<00:09:02.080> Kovan<00:09:02.500> account 00:09:02.820 --> 00:09:02.830 align:start position:0% sending main net eath to a Kovan account 00:09:02.830 --> 00:09:07.080 align:start position:0% sending main net eath to a Kovan account or<00:09:03.130> Kovan<00:09:03.730> smart<00:09:04.120> contract<00:09:05.250> so<00:09:06.250> this<00:09:06.880> is 00:09:07.080 --> 00:09:07.090 align:start position:0% or Kovan smart contract so this is 00:09:07.090 --> 00:09:09.270 align:start position:0% or Kovan smart contract so this is obviously<00:09:07.450> a<00:09:07.540> really<00:09:07.720> bad<00:09:07.900> experience<00:09:08.280> so 00:09:09.270 --> 00:09:09.280 align:start position:0% obviously a really bad experience so 00:09:09.280 --> 00:09:11.340 align:start position:0% obviously a really bad experience so we're<00:09:09.430> solving<00:09:09.640> this<00:09:09.880> by<00:09:09.940> having<00:09:10.300> a<00:09:10.630> all<00:09:11.140> the 00:09:11.340 --> 00:09:11.350 align:start position:0% we're solving this by having a all the 00:09:11.350 --> 00:09:13.320 align:start position:0% we're solving this by having a all the transactions<00:09:12.070> that<00:09:12.250> go<00:09:12.310> through<00:09:12.670> you<00:09:13.030> port 00:09:13.320 --> 00:09:13.330 align:start position:0% transactions that go through you port 00:09:13.330 --> 00:09:16.410 align:start position:0% transactions that go through you port are<00:09:14.400> automatically<00:09:15.400> fueled<00:09:15.820> by<00:09:15.970> our 00:09:16.410 --> 00:09:16.420 align:start position:0% are automatically fueled by our 00:09:16.420 --> 00:09:19.290 align:start position:0% are automatically fueled by our transaction<00:09:16.870> fuelling<00:09:17.410> service<00:09:17.740> and<00:09:18.300> neither 00:09:19.290 --> 00:09:19.300 align:start position:0% transaction fuelling service and neither 00:09:19.300 --> 00:09:20.790 align:start position:0% transaction fuelling service and neither you<00:09:19.540> nor<00:09:19.720> your<00:09:19.780> users<00:09:20.230> have<00:09:20.350> to<00:09:20.410> worry<00:09:20.680> about 00:09:20.790 --> 00:09:20.800 align:start position:0% you nor your users have to worry about 00:09:20.800 --> 00:09:23.610 align:start position:0% you nor your users have to worry about that<00:09:21.070> and<00:09:21.190> again<00:09:21.370> in<00:09:21.550> the<00:09:21.640> future<00:09:22.440> and<00:09:23.440> I<00:09:23.500> would 00:09:23.610 --> 00:09:23.620 align:start position:0% that and again in the future and I would 00:09:23.620 --> 00:09:33.870 align:start position:0% that and again in the future and I would like<00:09:23.740> to<00:09:23.770> give<00:09:23.980> it<00:09:24.070> over<00:09:24.160> to<00:09:24.280> Reuben<00:09:32.640> I'm<00:09:33.640> going 00:09:33.870 --> 00:09:33.880 align:start position:0% like to give it over to Reuben I'm going 00:09:33.880 --> 00:09:36.770 align:start position:0% like to give it over to Reuben I'm going to<00:09:34.000> talk<00:09:34.240> about<00:09:34.390> user<00:09:34.990> credentials<00:09:35.380> and<00:09:35.830> I 00:09:36.770 --> 00:09:36.780 align:start position:0% to talk about user credentials and I 00:09:36.780 --> 00:09:38.640 align:start position:0% to talk about user credentials and I think<00:09:37.780> it's<00:09:37.900> to<00:09:37.960> my<00:09:38.110> concern 00:09:38.640 --> 00:09:38.650 align:start position:0% think it's to my concern 00:09:38.650 --> 00:09:41.970 align:start position:0% think it's to my concern so<00:09:38.980> for<00:09:39.340> users<00:09:40.080> after<00:09:41.080> after<00:09:41.440> defconn<00:09:41.740> when<00:09:41.890> I 00:09:41.970 --> 00:09:41.980 align:start position:0% so for users after after defconn when I 00:09:41.980 --> 00:09:44.220 align:start position:0% so for users after after defconn when I represented<00:09:42.550> you<00:09:42.910> put<00:09:43.090> in<00:09:43.270> in<00:09:43.660> the<00:09:43.780> role<00:09:43.960> from 00:09:44.220 --> 00:09:44.230 align:start position:0% represented you put in in the role from 00:09:44.230 --> 00:09:47.010 align:start position:0% represented you put in in the role from from<00:09:45.040> today<00:09:45.250> and<00:09:45.430> we<00:09:45.970> realized<00:09:46.360> that<00:09:46.540> because 00:09:47.010 --> 00:09:47.020 align:start position:0% from today and we realized that because 00:09:47.020 --> 00:09:50.310 align:start position:0% from today and we realized that because of<00:09:47.200> a<00:09:47.260> feedback<00:09:47.650> off<00:09:48.000> from<00:09:49.000> the<00:09:49.090> community<00:09:49.510> how 00:09:50.310 --> 00:09:50.320 align:start position:0% of a feedback off from the community how 00:09:50.320 --> 00:09:52.050 align:start position:0% of a feedback off from the community how to<00:09:50.380> interact<00:09:50.860> and<00:09:51.190> make<00:09:51.340> it<00:09:51.460> much<00:09:51.670> more<00:09:51.850> user 00:09:52.050 --> 00:09:52.060 align:start position:0% to interact and make it much more user 00:09:52.060 --> 00:09:54.660 align:start position:0% to interact and make it much more user friendly<00:09:52.180> for<00:09:52.990> for<00:09:53.200> users<00:09:53.470> and<00:09:53.620> more<00:09:54.040> personal 00:09:54.660 --> 00:09:54.670 align:start position:0% friendly for for users and more personal 00:09:54.670 --> 00:09:57.360 align:start position:0% friendly for for users and more personal so<00:09:54.820> when<00:09:55.270> you<00:09:55.360> log<00:09:55.540> on<00:09:55.720> to<00:09:55.960> adapt<00:09:56.620> and<00:09:56.860> like<00:09:57.070> a 00:09:57.360 --> 00:09:57.370 align:start position:0% so when you log on to adapt and like a 00:09:57.370 --> 00:10:00.000 align:start position:0% so when you log on to adapt and like a simple<00:09:57.880> thing<00:09:58.000> like<00:09:58.060> a<00:09:58.410> nickname<00:09:59.410> or<00:09:59.830> some 00:10:00.000 --> 00:10:00.010 align:start position:0% simple thing like a nickname or some 00:10:00.010 --> 00:10:02.370 align:start position:0% simple thing like a nickname or some photo<00:10:00.400> make<00:10:01.000> it<00:10:01.120> a<00:10:01.150> bit<00:10:01.270> more<00:10:01.300> personal<00:10:01.510> so 00:10:02.370 --> 00:10:02.380 align:start position:0% photo make it a bit more personal so 00:10:02.380 --> 00:10:03.870 align:start position:0% photo make it a bit more personal so it's<00:10:02.530> all<00:10:02.650> about<00:10:02.860> like<00:10:03.040> how<00:10:03.400> can<00:10:03.610> we<00:10:03.730> give 00:10:03.870 --> 00:10:03.880 align:start position:0% it's all about like how can we give 00:10:03.880 --> 00:10:06.750 align:start position:0% it's all about like how can we give badges<00:10:04.360> or<00:10:04.450> information<00:10:05.100> from<00:10:06.100> a<00:10:06.160> user<00:10:06.430> back 00:10:06.750 --> 00:10:06.760 align:start position:0% badges or information from a user back 00:10:06.760 --> 00:10:08.220 align:start position:0% badges or information from a user back to<00:10:06.790> the<00:10:07.060> user<00:10:07.210> because<00:10:07.540> we<00:10:07.810> don't<00:10:07.960> want<00:10:08.140> to 00:10:08.220 --> 00:10:08.230 align:start position:0% to the user because we don't want to 00:10:08.230 --> 00:10:10.290 align:start position:0% to the user because we don't want to store<00:10:08.500> them<00:10:08.680> centrally<00:10:09.070> so<00:10:09.970> that's<00:10:10.120> something 00:10:10.290 --> 00:10:10.300 align:start position:0% store them centrally so that's something 00:10:10.300 --> 00:10:12.390 align:start position:0% store them centrally so that's something we<00:10:10.540> explored<00:10:11.380> and<00:10:11.590> we<00:10:11.650> talked<00:10:11.830> a<00:10:11.920> lot<00:10:12.010> with<00:10:12.220> the 00:10:12.390 --> 00:10:12.400 align:start position:0% we explored and we talked a lot with the 00:10:12.400 --> 00:10:14.940 align:start position:0% we explored and we talked a lot with the identity<00:10:13.150> community<00:10:13.600> and<00:10:13.870> we<00:10:14.590> realized 00:10:14.940 --> 00:10:14.950 align:start position:0% identity community and we realized 00:10:14.950 --> 00:10:16.620 align:start position:0% identity community and we realized there's<00:10:15.160> a<00:10:15.250> lot<00:10:15.370> of<00:10:15.460> opportunities<00:10:16.090> to<00:10:16.120> use 00:10:16.620 --> 00:10:16.630 align:start position:0% there's a lot of opportunities to use 00:10:16.630 --> 00:10:19.140 align:start position:0% there's a lot of opportunities to use the<00:10:16.930> identity<00:10:17.380> from<00:10:18.100> you<00:10:18.280> as<00:10:18.520> an<00:10:18.670> individual 00:10:19.140 --> 00:10:19.150 align:start position:0% the identity from you as an individual 00:10:19.150 --> 00:10:21.140 align:start position:0% the identity from you as an individual as<00:10:19.300> well<00:10:19.510> as<00:10:19.630> from<00:10:19.780> the<00:10:19.900> table<00:10:20.050> to<00:10:20.260> create 00:10:21.140 --> 00:10:21.150 align:start position:0% as well as from the table to create 00:10:21.150 --> 00:10:24.090 align:start position:0% as well as from the table to create credentials<00:10:22.150> in<00:10:22.630> form<00:10:22.900> from<00:10:23.020> badges<00:10:23.470> or<00:10:23.740> actor 00:10:24.090 --> 00:10:24.100 align:start position:0% credentials in form from badges or actor 00:10:24.100 --> 00:10:26.160 align:start position:0% credentials in form from badges or actor stations<00:10:24.460> to<00:10:24.670> the<00:10:24.790> users<00:10:25.060> that<00:10:25.090> come<00:10:25.570> some 00:10:26.160 --> 00:10:26.170 align:start position:0% stations to the users that come some 00:10:26.170 --> 00:10:28.290 align:start position:0% stations to the users that come some form<00:10:26.350> of<00:10:26.440> like<00:10:26.590> verify<00:10:26.980> the<00:10:27.040> claims<00:10:27.370> so<00:10:28.150> what 00:10:28.290 --> 00:10:28.300 align:start position:0% form of like verify the claims so what 00:10:28.300 --> 00:10:33.690 align:start position:0% form of like verify the claims so what we<00:10:28.360> did<00:10:28.510> thanks<00:10:29.370> what<00:10:30.370> we<00:10:30.460> did<00:10:30.610> is<00:10:30.850> we<00:10:32.400> built<00:10:33.400> an 00:10:33.690 --> 00:10:33.700 align:start position:0% we did thanks what we did is we built an 00:10:33.700 --> 00:10:36.120 align:start position:0% we did thanks what we did is we built an ability<00:10:34.360> for<00:10:34.600> the<00:10:35.170> user<00:10:35.260> to<00:10:35.410> make<00:10:35.860> this<00:10:35.950> very 00:10:36.120 --> 00:10:36.130 align:start position:0% ability for the user to make this very 00:10:36.130 --> 00:10:37.980 align:start position:0% ability for the user to make this very very<00:10:36.220> easy<00:10:36.520> so<00:10:36.850> we<00:10:37.270> have<00:10:37.360> libraries<00:10:37.750> now<00:10:37.930> to 00:10:37.980 --> 00:10:37.990 align:start position:0% very easy so we have libraries now to 00:10:37.990 --> 00:10:39.930 align:start position:0% very easy so we have libraries now to issue<00:10:38.470> these<00:10:38.710> kind<00:10:38.950> of<00:10:38.980> attestation<00:10:39.370> to<00:10:39.550> the 00:10:39.930 --> 00:10:39.940 align:start position:0% issue these kind of attestation to the 00:10:39.940 --> 00:10:43.620 align:start position:0% issue these kind of attestation to the users<00:10:40.650> this<00:10:41.650> can<00:10:42.190> be<00:10:42.340> in<00:10:42.550> form<00:10:42.910> of<00:10:42.970> on<00:10:43.180> train<00:10:43.390> as 00:10:43.620 --> 00:10:43.630 align:start position:0% users this can be in form of on train as 00:10:43.630 --> 00:10:45.870 align:start position:0% users this can be in form of on train as well<00:10:43.840> as<00:10:43.900> off<00:10:44.110> train<00:10:44.350> stuff<00:10:44.590> we<00:10:45.250> had<00:10:45.370> the 00:10:45.870 --> 00:10:45.880 align:start position:0% well as off train stuff we had the 00:10:45.880 --> 00:10:47.280 align:start position:0% well as off train stuff we had the conversation<00:10:46.060> we're<00:10:46.660> building<00:10:46.900> an<00:10:46.990> identity 00:10:47.280 --> 00:10:47.290 align:start position:0% conversation we're building an identity 00:10:47.290 --> 00:10:48.840 align:start position:0% conversation we're building an identity platform<00:10:47.530> so<00:10:47.890> a<00:10:47.920> lot<00:10:48.130> of<00:10:48.160> the<00:10:48.250> information<00:10:48.730> you 00:10:48.840 --> 00:10:48.850 align:start position:0% platform so a lot of the information you 00:10:48.850 --> 00:10:51.270 align:start position:0% platform so a lot of the information you get<00:10:49.000> a<00:10:49.270> nickname<00:10:49.930> is<00:10:50.110> maybe<00:10:50.290> less<00:10:50.470> critical 00:10:51.270 --> 00:10:51.280 align:start position:0% get a nickname is maybe less critical 00:10:51.280 --> 00:10:53.280 align:start position:0% get a nickname is maybe less critical but<00:10:51.730> there's<00:10:51.880> a<00:10:51.940> lot<00:10:52.090> of<00:10:52.210> information<00:10:52.870> about 00:10:53.280 --> 00:10:53.290 align:start position:0% but there's a lot of information about 00:10:53.290 --> 00:10:55.770 align:start position:0% but there's a lot of information about my<00:10:53.740> name<00:10:53.920> my<00:10:54.160> birthday<00:10:54.640> that<00:10:55.210> I<00:10:55.270> have<00:10:55.450> a 00:10:55.770 --> 00:10:55.780 align:start position:0% my name my birthday that I have a 00:10:55.780 --> 00:10:58.740 align:start position:0% my name my birthday that I have a certain<00:10:56.500> degree<00:10:56.650> or<00:10:57.100> maybe<00:10:57.820> have<00:10:58.060> achieved<00:10:58.630> a 00:10:58.740 --> 00:10:58.750 align:start position:0% certain degree or maybe have achieved a 00:10:58.750 --> 00:11:00.240 align:start position:0% certain degree or maybe have achieved a certain<00:10:58.780> certificate<00:10:59.680> and<00:10:59.950> because<00:11:00.220> I 00:11:00.240 --> 00:11:00.250 align:start position:0% certain certificate and because I 00:11:00.250 --> 00:11:01.800 align:start position:0% certain certificate and because I achieved<00:11:00.760> an<00:11:00.880> online<00:11:01.150> course<00:11:01.360> or<00:11:01.570> something 00:11:01.800 --> 00:11:01.810 align:start position:0% achieved an online course or something 00:11:01.810 --> 00:11:03.510 align:start position:0% achieved an online course or something else<00:11:01.960> all<00:11:02.290> of<00:11:02.560> this<00:11:02.650> data<00:11:02.890> is<00:11:03.130> something<00:11:03.310> you 00:11:03.510 --> 00:11:03.520 align:start position:0% else all of this data is something you 00:11:03.520 --> 00:11:05.400 align:start position:0% else all of this data is something you don't<00:11:03.670> really<00:11:03.970> want<00:11:04.120> to<00:11:04.180> have<00:11:04.300> unchain<00:11:04.750> Eve 00:11:05.400 --> 00:11:05.410 align:start position:0% don't really want to have unchain Eve 00:11:05.410 --> 00:11:07.830 align:start position:0% don't really want to have unchain Eve not<00:11:05.680> encrypted<00:11:06.280> so<00:11:07.000> we<00:11:07.090> spend<00:11:07.330> a<00:11:07.390> lot<00:11:07.510> of<00:11:07.540> time 00:11:07.830 --> 00:11:07.840 align:start position:0% not encrypted so we spend a lot of time 00:11:07.840 --> 00:11:08.700 align:start position:0% not encrypted so we spend a lot of time in<00:11:08.020> our<00:11:08.110> focus 00:11:08.700 --> 00:11:08.710 align:start position:0% in our focus 00:11:08.710 --> 00:11:10.980 align:start position:0% in our focus during<00:11:08.980> this<00:11:09.160> was<00:11:10.060> off<00:11:10.240> chain<00:11:10.540> attestations 00:11:10.980 --> 00:11:10.990 align:start position:0% during this was off chain attestations 00:11:10.990 --> 00:11:13.890 align:start position:0% during this was off chain attestations in<00:11:11.260> a<00:11:11.350> very<00:11:11.500> very<00:11:11.680> easy<00:11:11.830> way<00:11:12.390> last<00:11:13.390> year<00:11:13.660> we<00:11:13.780> had 00:11:13.890 --> 00:11:13.900 align:start position:0% in a very very easy way last year we had 00:11:13.900 --> 00:11:16.910 align:start position:0% in a very very easy way last year we had an<00:11:13.990> experiment<00:11:14.530> here<00:11:15.060> Piper<00:11:16.060> was<00:11:16.330> doing<00:11:16.600> this 00:11:16.910 --> 00:11:16.920 align:start position:0% an experiment here Piper was doing this 00:11:16.920 --> 00:11:20.340 align:start position:0% an experiment here Piper was doing this DEFCON<00:11:17.920> 2<00:11:18.760> attendance<00:11:19.300> where<00:11:19.840> people<00:11:20.110> went<00:11:20.260> to 00:11:20.340 --> 00:11:20.350 align:start position:0% DEFCON 2 attendance where people went to 00:11:20.350 --> 00:11:23.490 align:start position:0% DEFCON 2 attendance where people went to him<00:11:20.590> gave<00:11:20.860> him<00:11:20.980> the<00:11:21.070> theorem<00:11:21.340> address<00:11:21.630> and<00:11:22.630> he 00:11:23.490 --> 00:11:23.500 align:start position:0% him gave him the theorem address and he 00:11:23.500 --> 00:11:25.080 align:start position:0% him gave him the theorem address and he was<00:11:23.680> basically<00:11:23.800> recording<00:11:24.490> this<00:11:24.610> in<00:11:24.790> form<00:11:25.030> of 00:11:25.080 --> 00:11:25.090 align:start position:0% was basically recording this in form of 00:11:25.090 --> 00:11:27.690 align:start position:0% was basically recording this in form of an<00:11:25.470> smart<00:11:26.470> contact<00:11:26.800> and<00:11:27.070> we<00:11:27.220> tried<00:11:27.430> to<00:11:27.550> do<00:11:27.670> a 00:11:27.690 --> 00:11:27.700 align:start position:0% an smart contact and we tried to do a 00:11:27.700 --> 00:11:29.730 align:start position:0% an smart contact and we tried to do a little<00:11:27.910> experiment<00:11:28.780> later<00:11:29.170> let's<00:11:29.470> see<00:11:29.620> how 00:11:29.730 --> 00:11:29.740 align:start position:0% little experiment later let's see how 00:11:29.740 --> 00:11:31.560 align:start position:0% little experiment later let's see how the<00:11:29.800> Wi-Fi<00:11:30.160> works<00:11:30.310> but<00:11:30.580> and<00:11:30.970> if<00:11:31.180> you<00:11:31.300> have<00:11:31.420> you 00:11:31.560 --> 00:11:31.570 align:start position:0% the Wi-Fi works but and if you have you 00:11:31.570 --> 00:11:34.110 align:start position:0% the Wi-Fi works but and if you have you ports<00:11:31.900> the<00:11:32.140> light<00:11:32.290> is<00:11:32.410> app<00:11:32.590> you<00:11:33.280> will<00:11:33.490> see<00:11:33.520> QR 00:11:34.110 --> 00:11:34.120 align:start position:0% ports the light is app you will see QR 00:11:34.120 --> 00:11:35.430 align:start position:0% ports the light is app you will see QR code<00:11:34.270> at<00:11:34.390> the<00:11:34.480> end<00:11:34.510> of<00:11:34.840> the<00:11:34.990> talk<00:11:35.200> and 00:11:35.430 --> 00:11:35.440 align:start position:0% code at the end of the talk and 00:11:35.440 --> 00:11:37.380 align:start position:0% code at the end of the talk and hopefully<00:11:35.980> get<00:11:36.130> an<00:11:36.220> attestation<00:11:36.460> about<00:11:37.000> being 00:11:37.380 --> 00:11:37.390 align:start position:0% hopefully get an attestation about being 00:11:37.390 --> 00:11:43.020 align:start position:0% hopefully get an attestation about being a<00:11:37.480> tenant<00:11:37.840> or<00:11:38.050> having<00:11:38.650> eternity<00:11:39.780> so<00:11:42.030> obviously 00:11:43.020 --> 00:11:43.030 align:start position:0% a tenant or having eternity so obviously 00:11:43.030 --> 00:11:46.020 align:start position:0% a tenant or having eternity so obviously after<00:11:43.920> your<00:11:44.920> credentials<00:11:45.370> have<00:11:45.400> been<00:11:45.490> issued 00:11:46.020 --> 00:11:46.030 align:start position:0% after your credentials have been issued 00:11:46.030 --> 00:11:48.330 align:start position:0% after your credentials have been issued and<00:11:46.300> stored<00:11:46.960> with<00:11:47.140> the<00:11:47.260> user<00:11:47.410> we<00:11:47.980> need<00:11:48.130> to<00:11:48.190> make 00:11:48.330 --> 00:11:48.340 align:start position:0% and stored with the user we need to make 00:11:48.340 --> 00:11:51.180 align:start position:0% and stored with the user we need to make it<00:11:48.460> as<00:11:48.550> well<00:11:48.700> easy<00:11:48.940> for<00:11:49.560> the<00:11:50.560> developers<00:11:51.010> to 00:11:51.180 --> 00:11:51.190 align:start position:0% it as well easy for the developers to 00:11:51.190 --> 00:11:53.040 align:start position:0% it as well easy for the developers to receive<00:11:51.550> this<00:11:51.730> beta<00:11:51.970> data<00:11:52.240> back<00:11:52.450> so<00:11:52.810> what<00:11:52.930> we 00:11:53.040 --> 00:11:53.050 align:start position:0% receive this beta data back so what we 00:11:53.050 --> 00:11:56.460 align:start position:0% receive this beta data back so what we built<00:11:53.550> is<00:11:54.550> a<00:11:54.850> library<00:11:55.300> that<00:11:55.630> you<00:11:56.110> can<00:11:56.290> easily 00:11:56.460 --> 00:11:56.470 align:start position:0% built is a library that you can easily 00:11:56.470 --> 00:11:58.980 align:start position:0% built is a library that you can easily receive<00:11:56.950> the<00:11:57.100> credentials<00:11:58.030> and<00:11:58.270> can<00:11:58.660> validate 00:11:58.980 --> 00:11:58.990 align:start position:0% receive the credentials and can validate 00:11:58.990 --> 00:12:00.810 align:start position:0% receive the credentials and can validate them<00:11:59.230> and<00:11:59.500> that's<00:11:59.950> a<00:12:00.040> very<00:12:00.160> critical<00:12:00.460> and<00:12:00.730> very 00:12:00.810 --> 00:12:00.820 align:start position:0% them and that's a very critical and very 00:12:00.820 --> 00:12:03.120 align:start position:0% them and that's a very critical and very interesting<00:12:01.420> part<00:12:02.020> because<00:12:02.080> what<00:12:02.710> we<00:12:02.890> allow 00:12:03.120 --> 00:12:03.130 align:start position:0% interesting part because what we allow 00:12:03.130 --> 00:12:05.790 align:start position:0% interesting part because what we allow now<00:12:03.340> to<00:12:03.400> do<00:12:03.670> is<00:12:03.760> that<00:12:03.910> anyone<00:12:04.510> can<00:12:04.570> issue<00:12:04.990> that 00:12:05.790 --> 00:12:05.800 align:start position:0% now to do is that anyone can issue that 00:12:05.800 --> 00:12:08.430 align:start position:0% now to do is that anyone can issue that say<00:12:05.980> kyc<00:12:06.820> attestation<00:12:07.480> so<00:12:07.780> there<00:12:07.960> are<00:12:08.080> enough 00:12:08.430 --> 00:12:08.440 align:start position:0% say kyc attestation so there are enough 00:12:08.440 --> 00:12:11.010 align:start position:0% say kyc attestation so there are enough companies<00:12:09.040> in<00:12:09.490> the<00:12:09.610> world<00:12:09.790> who<00:12:10.180> have<00:12:10.300> done<00:12:10.480> kyc 00:12:11.010 --> 00:12:11.020 align:start position:0% companies in the world who have done kyc 00:12:11.020 --> 00:12:13.170 align:start position:0% companies in the world who have done kyc before<00:12:11.380> and<00:12:11.590> they<00:12:11.980> can<00:12:12.160> issue<00:12:12.280> this<00:12:12.580> form<00:12:12.880> to 00:12:13.170 --> 00:12:13.180 align:start position:0% before and they can issue this form to 00:12:13.180 --> 00:12:15.270 align:start position:0% before and they can issue this form to me<00:12:13.300> now<00:12:13.450> in<00:12:13.630> an<00:12:13.780> in<00:12:14.320> an<00:12:14.530> acrid<00:12:14.800> n<00:12:14.920> Chelan 00:12:15.270 --> 00:12:15.280 align:start position:0% me now in an in an acrid n Chelan 00:12:15.280 --> 00:12:17.130 align:start position:0% me now in an in an acrid n Chelan attestation<00:12:15.790> which<00:12:16.120> is<00:12:16.630> signed<00:12:16.840> from<00:12:17.050> the 00:12:17.130 --> 00:12:17.140 align:start position:0% attestation which is signed from the 00:12:17.140 --> 00:12:18.720 align:start position:0% attestation which is signed from the issuer<00:12:17.440> that<00:12:17.620> can<00:12:17.770> be<00:12:17.920> a<00:12:17.950> bank<00:12:18.190> that<00:12:18.430> can<00:12:18.550> be<00:12:18.700> a 00:12:18.720 --> 00:12:18.730 align:start position:0% issuer that can be a bank that can be a 00:12:18.730 --> 00:12:21.450 align:start position:0% issuer that can be a bank that can be a crypto<00:12:19.120> exchange<00:12:19.540> or<00:12:20.110> anyone<00:12:20.410> else<00:12:20.590> we're<00:12:21.340> now 00:12:21.450 --> 00:12:21.460 align:start position:0% crypto exchange or anyone else we're now 00:12:21.460 --> 00:12:23.400 align:start position:0% crypto exchange or anyone else we're now working<00:12:21.640> on<00:12:21.970> an<00:12:22.060> integration<00:12:22.510> of<00:12:22.630> a<00:12:22.870> couple<00:12:23.320> of 00:12:23.400 --> 00:12:23.410 align:start position:0% working on an integration of a couple of 00:12:23.410 --> 00:12:25.650 align:start position:0% working on an integration of a couple of like<00:12:23.590> kyc<00:12:24.250> providers<00:12:24.640> at<00:12:24.760> 12<00:12:25.000> so<00:12:25.390> it's<00:12:25.510> more 00:12:25.650 --> 00:12:25.660 align:start position:0% like kyc providers at 12 so it's more 00:12:25.660 --> 00:12:28.980 align:start position:0% like kyc providers at 12 so it's more native<00:12:26.080> as<00:12:26.770> part<00:12:27.070> of<00:12:27.100> this<00:12:27.220> and<00:12:27.430> now<00:12:27.970> what<00:12:28.840> you 00:12:28.980 --> 00:12:28.990 align:start position:0% native as part of this and now what you 00:12:28.990 --> 00:12:30.990 align:start position:0% native as part of this and now what you can<00:12:29.140> do<00:12:29.320> if<00:12:29.560> you<00:12:29.950> have<00:12:29.980> done<00:12:30.310> this<00:12:30.460> once<00:12:30.730> you<00:12:30.880> go 00:12:30.990 --> 00:12:31.000 align:start position:0% can do if you have done this once you go 00:12:31.000 --> 00:12:32.610 align:start position:0% can do if you have done this once you go through<00:12:31.030> this<00:12:31.240> process<00:12:31.450> and<00:12:31.660> now<00:12:31.870> you<00:12:31.930> go<00:12:32.110> to<00:12:32.170> a 00:12:32.610 --> 00:12:32.620 align:start position:0% through this process and now you go to a 00:12:32.620 --> 00:12:34.770 align:start position:0% through this process and now you go to a token<00:12:33.190> a<00:12:33.490> launch<00:12:33.970> platform<00:12:34.180> and<00:12:34.690> you<00:12:34.750> can 00:12:34.770 --> 00:12:34.780 align:start position:0% token a launch platform and you can 00:12:34.780 --> 00:12:37.710 align:start position:0% token a launch platform and you can reissue<00:12:35.350> this<00:12:35.620> information<00:12:36.220> so<00:12:36.760> it's<00:12:37.450> a<00:12:37.540> very 00:12:37.710 --> 00:12:37.720 align:start position:0% reissue this information so it's a very 00:12:37.720 --> 00:12:39.360 align:start position:0% reissue this information so it's a very very<00:12:37.960> easy<00:12:38.020> much<00:12:38.440> more<00:12:38.620> user-friendly<00:12:38.890> way<00:12:39.310> to 00:12:39.360 --> 00:12:39.370 align:start position:0% very easy much more user-friendly way to 00:12:39.370 --> 00:12:41.760 align:start position:0% very easy much more user-friendly way to to<00:12:39.970> get<00:12:40.150> this<00:12:40.270> validation<00:12:40.660> and<00:12:40.990> can<00:12:41.530> rely<00:12:41.740> on 00:12:41.760 --> 00:12:41.770 align:start position:0% to get this validation and can rely on 00:12:41.770 --> 00:12:45.540 align:start position:0% to get this validation and can rely on this<00:12:42.010> as<00:12:42.160> a<00:12:42.870> developer<00:12:43.870> as<00:12:44.710> long<00:12:44.980> as<00:12:45.130> you<00:12:45.280> trust 00:12:45.540 --> 00:12:45.550 align:start position:0% this as a developer as long as you trust 00:12:45.550 --> 00:12:48.660 align:start position:0% this as a developer as long as you trust the<00:12:46.330> issuing<00:12:46.690> parties<00:12:47.110> I<00:12:47.380> think<00:12:48.220> that's<00:12:48.550> a 00:12:48.660 --> 00:12:48.670 align:start position:0% the issuing parties I think that's a 00:12:48.670 --> 00:12:50.520 align:start position:0% the issuing parties I think that's a very<00:12:48.790> like<00:12:49.150> nice<00:12:49.450> way<00:12:49.630> because<00:12:49.900> now<00:12:50.260> we<00:12:50.320> get<00:12:50.500> a 00:12:50.520 --> 00:12:50.530 align:start position:0% very like nice way because now we get a 00:12:50.530 --> 00:12:52.020 align:start position:0% very like nice way because now we get a lot<00:12:50.680> of<00:12:50.710> feedback<00:12:50.890> in<00:12:51.250> the<00:12:51.460> community<00:12:51.850> that 00:12:52.020 --> 00:12:52.030 align:start position:0% lot of feedback in the community that 00:12:52.030 --> 00:12:53.490 align:start position:0% lot of feedback in the community that people<00:12:52.450> want<00:12:52.690> to<00:12:52.720> use<00:12:52.870> this<00:12:52.990> for<00:12:53.170> many<00:12:53.320> other 00:12:53.490 --> 00:12:53.500 align:start position:0% people want to use this for many other 00:12:53.500 --> 00:12:56.010 align:start position:0% people want to use this for many other tabs<00:12:53.770> so<00:12:54.130> whether<00:12:54.730> it's<00:12:54.970> Mountain<00:12:55.810> Port 00:12:56.010 --> 00:12:56.020 align:start position:0% tabs so whether it's Mountain Port 00:12:56.020 --> 00:12:57.420 align:start position:0% tabs so whether it's Mountain Port because<00:12:56.350> you've<00:12:56.530> managed<00:12:56.860> certain<00:12:57.100> assets 00:12:57.420 --> 00:12:57.430 align:start position:0% because you've managed certain assets 00:12:57.430 --> 00:12:59.400 align:start position:0% because you've managed certain assets whether<00:12:57.670> it's<00:12:57.850> a<00:12:58.120> poker<00:12:58.510> platform<00:12:59.110> or<00:12:59.260> whether 00:12:59.400 --> 00:12:59.410 align:start position:0% whether it's a poker platform or whether 00:12:59.410 --> 00:13:01.650 align:start position:0% whether it's a poker platform or whether it's<00:12:59.590> gnosis<00:13:00.580> there's<00:13:01.150> like<00:13:01.300> multiple 00:13:01.650 --> 00:13:01.660 align:start position:0% it's gnosis there's like multiple 00:13:01.660 --> 00:13:03.420 align:start position:0% it's gnosis there's like multiple reasons<00:13:01.840> why<00:13:02.170> you<00:13:02.230> want<00:13:02.440> to<00:13:02.560> know<00:13:02.710> something 00:13:03.420 --> 00:13:03.430 align:start position:0% reasons why you want to know something 00:13:03.430 --> 00:13:04.890 align:start position:0% reasons why you want to know something about<00:13:03.670> the<00:13:03.880> user<00:13:04.030> there<00:13:04.510> just<00:13:04.660> can<00:13:04.780> be 00:13:04.890 --> 00:13:04.900 align:start position:0% about the user there just can be 00:13:04.900 --> 00:13:06.600 align:start position:0% about the user there just can be abstract<00:13:05.380> it<00:13:05.530> can<00:13:05.650> be<00:13:05.770> he's<00:13:06.310> older<00:13:06.580> than 00:13:06.600 --> 00:13:06.610 align:start position:0% abstract it can be he's older than 00:13:06.610 --> 00:13:08.940 align:start position:0% abstract it can be he's older than eighteen<00:13:07.030> or<00:13:07.360> he<00:13:07.900> lives<00:13:08.230> in<00:13:08.350> a<00:13:08.410> certain<00:13:08.560> state 00:13:08.940 --> 00:13:08.950 align:start position:0% eighteen or he lives in a certain state 00:13:08.950 --> 00:13:10.890 align:start position:0% eighteen or he lives in a certain state or<00:13:09.250> not<00:13:09.640> in<00:13:09.850> a<00:13:09.940> certain<00:13:10.180> country<00:13:10.330> there's<00:13:10.840> a 00:13:10.890 --> 00:13:10.900 align:start position:0% or not in a certain country there's a 00:13:10.900 --> 00:13:12.150 align:start position:0% or not in a certain country there's a lot<00:13:11.080> of<00:13:11.200> value<00:13:11.500> in<00:13:11.530> these<00:13:11.740> kind<00:13:11.980> of<00:13:12.010> add 00:13:12.150 --> 00:13:12.160 align:start position:0% lot of value in these kind of add 00:13:12.160 --> 00:13:14.370 align:start position:0% lot of value in these kind of add stations<00:13:12.520> and<00:13:12.670> it's<00:13:13.330> all<00:13:13.540> like<00:13:14.020> digitally 00:13:14.370 --> 00:13:14.380 align:start position:0% stations and it's all like digitally 00:13:14.380 --> 00:13:16.170 align:start position:0% stations and it's all like digitally signed<00:13:14.680> to<00:13:15.070> my<00:13:15.220> identity<00:13:15.610> so<00:13:15.760> it's<00:13:15.910> very 00:13:16.170 --> 00:13:16.180 align:start position:0% signed to my identity so it's very 00:13:16.180 --> 00:13:20.820 align:start position:0% signed to my identity so it's very secure<00:13:16.840> and<00:13:16.960> powerful<00:13:18.510> so<00:13:19.510> ultimately<00:13:20.230> what 00:13:20.820 --> 00:13:20.830 align:start position:0% secure and powerful so ultimately what 00:13:20.830 --> 00:13:22.620 align:start position:0% secure and powerful so ultimately what we<00:13:20.980> built<00:13:21.340> was<00:13:21.550> this<00:13:21.700> is<00:13:21.850> really<00:13:21.880> the 00:13:22.620 --> 00:13:22.630 align:start position:0% we built was this is really the 00:13:22.630 --> 00:13:24.480 align:start position:0% we built was this is really the foundation<00:13:23.140> that<00:13:23.260> you<00:13:23.290> create<00:13:24.070> an<00:13:24.160> identity 00:13:24.480 --> 00:13:24.490 align:start position:0% foundation that you create an identity 00:13:24.490 --> 00:13:26.760 align:start position:0% foundation that you create an identity which<00:13:24.730> is<00:13:24.850> not<00:13:25.000> just<00:13:25.240> a<00:13:25.420> random<00:13:26.110> number<00:13:26.410> like<00:13:26.740> a 00:13:26.760 --> 00:13:26.770 align:start position:0% which is not just a random number like a 00:13:26.770 --> 00:13:28.860 align:start position:0% which is not just a random number like a random<00:13:27.130> address<00:13:27.490> it<00:13:27.940> is<00:13:28.270> now<00:13:28.630> the<00:13:28.690> ability 00:13:28.860 --> 00:13:28.870 align:start position:0% random address it is now the ability 00:13:28.870 --> 00:13:30.560 align:start position:0% random address it is now the ability that<00:13:29.320> you<00:13:29.380> have<00:13:29.470> a<00:13:29.860> privacy-preserving 00:13:30.560 --> 00:13:30.570 align:start position:0% that you have a privacy-preserving 00:13:30.570 --> 00:13:35.490 align:start position:0% that you have a privacy-preserving ability<00:13:31.890> to<00:13:32.890> use<00:13:33.580> as<00:13:33.850> a<00:13:33.880> user<00:13:34.500> interacting 00:13:35.490 --> 00:13:35.500 align:start position:0% ability to use as a user interacting 00:13:35.500 --> 00:13:37.550 align:start position:0% ability to use as a user interacting with<00:13:35.650> adapt<00:13:35.920> so<00:13:36.550> you<00:13:36.610> build<00:13:36.850> the<00:13:36.970> trust 00:13:37.550 --> 00:13:37.560 align:start position:0% with adapt so you build the trust 00:13:37.560 --> 00:13:39.780 align:start position:0% with adapt so you build the trust without<00:13:38.560> revealing<00:13:39.070> too<00:13:39.310> much<00:13:39.430> information 00:13:39.780 --> 00:13:39.790 align:start position:0% without revealing too much information 00:13:39.790 --> 00:13:43.800 align:start position:0% without revealing too much information and<00:13:40.300> that's<00:13:41.230> a<00:13:41.410> very<00:13:41.800> powerful<00:13:42.810> foundation 00:13:43.800 --> 00:13:43.810 align:start position:0% and that's a very powerful foundation 00:13:43.810 --> 00:13:46.290 align:start position:0% and that's a very powerful foundation anyway<00:13:44.320> and<00:13:44.530> also<00:13:45.250> the<00:13:45.610> foundation<00:13:45.880> for<00:13:46.150> any 00:13:46.290 --> 00:13:46.300 align:start position:0% anyway and also the foundation for any 00:13:46.300 --> 00:13:47.970 align:start position:0% anyway and also the foundation for any reputation<00:13:46.570> system<00:13:47.170> because<00:13:47.620> think<00:13:47.800> about 00:13:47.970 --> 00:13:47.980 align:start position:0% reputation system because think about 00:13:47.980 --> 00:13:49.980 align:start position:0% reputation system because think about this<00:13:48.130> if<00:13:48.610> you<00:13:48.850> are<00:13:48.880> issuing<00:13:49.120> to<00:13:49.510> a<00:13:49.540> user<00:13:49.750> that 00:13:49.980 --> 00:13:49.990 align:start position:0% this if you are issuing to a user that 00:13:49.990 --> 00:13:52.590 align:start position:0% this if you are issuing to a user that in<00:13:50.170> your<00:13:50.320> decentralized<00:13:50.950> IBM<00:13:51.790> be<00:13:51.940> he<00:13:52.450> was<00:13:52.570> a 00:13:52.590 --> 00:13:52.600 align:start position:0% in your decentralized IBM be he was a 00:13:52.600 --> 00:13:55.680 align:start position:0% in your decentralized IBM be he was a good<00:13:52.780> host<00:13:52.990> and<00:13:53.410> he<00:13:53.980> has<00:13:54.160> a<00:13:54.190> I<00:13:54.880> know<00:13:55.330> he<00:13:55.510> can 00:13:55.680 --> 00:13:55.690 align:start position:0% good host and he has a I know he can 00:13:55.690 --> 00:13:57.120 align:start position:0% good host and he has a I know he can drive<00:13:55.960> a<00:13:55.990> car<00:13:56.230> because<00:13:56.320> the<00:13:56.530> driver<00:13:56.800> license 00:13:57.120 --> 00:13:57.130 align:start position:0% drive a car because the driver license 00:13:57.130 --> 00:13:59.580 align:start position:0% drive a car because the driver license other<00:13:57.610> things<00:13:57.970> all<00:13:58.330> these<00:13:58.660> things<00:13:58.900> are<00:13:59.110> part 00:13:59.580 --> 00:13:59.590 align:start position:0% other things all these things are part 00:13:59.590 --> 00:14:02.670 align:start position:0% other things all these things are part of<00:13:59.830> a<00:14:00.340> very<00:14:00.910> good<00:14:01.690> foundation<00:14:02.200> for<00:14:02.230> any<00:14:02.470> type 00:14:02.670 --> 00:14:02.680 align:start position:0% of a very good foundation for any type 00:14:02.680 --> 00:14:04.620 align:start position:0% of a very good foundation for any type of<00:14:02.710> reputation<00:14:03.370> so<00:14:03.820> if<00:14:03.910> you<00:14:03.970> go<00:14:04.120> in<00:14:04.300> on<00:14:04.600> a 00:14:04.620 --> 00:14:04.630 align:start position:0% of reputation so if you go in on a 00:14:04.630 --> 00:14:06.300 align:start position:0% of reputation so if you go in on a certain<00:14:04.870> website<00:14:05.170> the<00:14:05.440> next<00:14:05.650> time<00:14:05.830> and<00:14:06.070> you 00:14:06.300 --> 00:14:06.310 align:start position:0% certain website the next time and you 00:14:06.310 --> 00:14:08.840 align:start position:0% certain website the next time and you can<00:14:06.460> issue<00:14:07.050> transaction<00:14:08.050> of<00:14:08.170> the<00:14:08.200> last<00:14:08.440> 100 00:14:08.840 --> 00:14:08.850 align:start position:0% can issue transaction of the last 100 00:14:08.850 --> 00:14:11.640 align:start position:0% can issue transaction of the last 100 interactions<00:14:09.850> with<00:14:10.030> I<00:14:10.210> know<00:14:10.330> you're<00:14:11.230> a<00:14:11.260> baby 00:14:11.640 --> 00:14:11.650 align:start position:0% interactions with I know you're a baby 00:14:11.650 --> 00:14:14.130 align:start position:0% interactions with I know you're a baby platform<00:14:12.400> you<00:14:12.730> can<00:14:12.910> just<00:14:13.090> take<00:14:13.570> this<00:14:13.720> anywhere 00:14:14.130 --> 00:14:14.140 align:start position:0% platform you can just take this anywhere 00:14:14.140 --> 00:14:17.040 align:start position:0% platform you can just take this anywhere and<00:14:14.380> issue<00:14:14.830> this<00:14:15.210> to<00:14:16.210> this<00:14:16.360> new<00:14:16.510> job<00:14:16.720> and<00:14:16.870> that 00:14:17.040 --> 00:14:17.050 align:start position:0% and issue this to this new job and that 00:14:17.050 --> 00:14:18.930 align:start position:0% and issue this to this new job and that will<00:14:17.230> make<00:14:17.410> it<00:14:17.560> much<00:14:17.710> much<00:14:17.890> easier<00:14:17.950> to<00:14:18.280> build 00:14:18.930 --> 00:14:18.940 align:start position:0% will make it much much easier to build 00:14:18.940 --> 00:14:21.330 align:start position:0% will make it much much easier to build digital<00:14:19.180> interaction<00:14:19.900> so<00:14:20.890> what<00:14:21.010> I<00:14:21.040> will<00:14:21.160> show 00:14:21.330 --> 00:14:21.340 align:start position:0% digital interaction so what I will show 00:14:21.340 --> 00:14:25.020 align:start position:0% digital interaction so what I will show you<00:14:21.400> now<00:14:21.640> hopefully<00:14:22.180> if<00:14:22.270> the<00:14:22.420> Wi-Fi<00:14:22.810> works<00:14:24.030> how 00:14:25.020 --> 00:14:25.030 align:start position:0% you now hopefully if the Wi-Fi works how 00:14:25.030 --> 00:14:26.790 align:start position:0% you now hopefully if the Wi-Fi works how did<00:14:25.240> your<00:14:25.390> signatures<00:14:25.810> work<00:14:25.990> so<00:14:26.170> that's 00:14:26.790 --> 00:14:26.800 align:start position:0% did your signatures work so that's 00:14:26.800 --> 00:14:29.070 align:start position:0% did your signatures work so that's something<00:14:26.980> we<00:14:27.160> demoed<00:14:27.400> last<00:14:27.610> year<00:14:27.820> ready<00:14:28.080> so 00:14:29.070 --> 00:14:29.080 align:start position:0% something we demoed last year ready so 00:14:29.080 --> 00:14:31.230 align:start position:0% something we demoed last year ready so we<00:14:29.200> all<00:14:29.320> know<00:14:29.530> that<00:14:29.770> to<00:14:30.700> do<00:14:30.820> any<00:14:31.000> kind<00:14:31.150> of 00:14:31.230 --> 00:14:31.240 align:start position:0% we all know that to do any kind of 00:14:31.240 --> 00:14:33.030 align:start position:0% we all know that to do any kind of interactions<00:14:31.810> with<00:14:31.960> the<00:14:32.080> blockchain<00:14:32.320> or<00:14:32.740> with 00:14:33.030 --> 00:14:33.040 align:start position:0% interactions with the blockchain or with 00:14:33.040 --> 00:14:34.950 align:start position:0% interactions with the blockchain or with aetherium<00:14:33.370> is<00:14:33.520> you<00:14:34.330> need<00:14:34.510> to<00:14:34.630> have<00:14:34.750> an<00:14:34.810> ability 00:14:34.950 --> 00:14:34.960 align:start position:0% aetherium is you need to have an ability 00:14:34.960 --> 00:14:36.600 align:start position:0% aetherium is you need to have an ability for<00:14:35.200> signing<00:14:35.650> so<00:14:35.770> pay<00:14:35.980> Laurie<00:14:36.160> mentioned<00:14:36.550> it 00:14:36.600 --> 00:14:36.610 align:start position:0% for signing so pay Laurie mentioned it 00:14:36.610 --> 00:14:39.780 align:start position:0% for signing so pay Laurie mentioned it the<00:14:37.030> the<00:14:37.720> phone<00:14:37.960> has<00:14:38.740> the<00:14:39.010> private<00:14:39.340> key<00:14:39.490> and<00:14:39.700> we 00:14:39.780 --> 00:14:39.790 align:start position:0% the the phone has the private key and we 00:14:39.790 --> 00:14:41.550 align:start position:0% the the phone has the private key and we have<00:14:39.910> our<00:14:40.060> architecture<00:14:40.690> which<00:14:41.230> were<00:14:41.350> smart 00:14:41.550 --> 00:14:41.560 align:start position:0% have our architecture which were smart 00:14:41.560 --> 00:14:43.650 align:start position:0% have our architecture which were smart phone<00:14:41.710> networks<00:14:41.980> but<00:14:42.610> I<00:14:42.640> will<00:14:42.790> try<00:14:43.000> to<00:14:43.030> do<00:14:43.330> and 00:14:43.650 --> 00:14:43.660 align:start position:0% phone networks but I will try to do and 00:14:43.660 --> 00:14:45.180 align:start position:0% phone networks but I will try to do and let's<00:14:43.840> see<00:14:43.960> how<00:14:44.080> that<00:14:44.110> works<00:14:44.440> with<00:14:44.590> the 00:14:45.180 --> 00:14:45.190 align:start position:0% let's see how that works with the 00:14:45.190 --> 00:14:48.180 align:start position:0% let's see how that works with the connectivity<00:14:45.730> here<00:14:45.940> is<00:14:46.570> to<00:14:46.900> show<00:14:47.140> you<00:14:47.200> how 00:14:48.180 --> 00:14:48.190 align:start position:0% connectivity here is to show you how 00:14:48.190 --> 00:14:52.320 align:start position:0% connectivity here is to show you how this<00:14:48.400> could<00:14:48.670> look<00:14:48.700> like<00:14:49.950> so<00:14:50.950> and<00:14:51.700> I<00:14:51.940> do<00:14:52.000> it<00:14:52.150> live 00:14:52.320 --> 00:14:52.330 align:start position:0% this could look like so and I do it live 00:14:52.330 --> 00:14:57.060 align:start position:0% this could look like so and I do it live so<00:14:52.630> I<00:14:52.930> hope<00:14:53.380> it<00:14:53.800> works<00:14:55.320> so<00:14:56.320> what<00:14:56.410> you<00:14:56.530> see<00:14:56.710> here 00:14:57.060 --> 00:14:57.070 align:start position:0% so I hope it works so what you see here 00:14:57.070 --> 00:14:58.860 align:start position:0% so I hope it works so what you see here first<00:14:58.030> of<00:14:58.180> all<00:14:58.360> I'll<00:14:58.510> show<00:14:58.540> you<00:14:58.750> the 00:14:58.860 --> 00:14:58.870 align:start position:0% first of all I'll show you the 00:14:58.870 --> 00:15:01.470 align:start position:0% first of all I'll show you the application<00:14:59.200> itself<00:14:59.560> it's<00:15:00.190> very<00:15:00.370> simple<00:15:00.730> it 00:15:01.470 --> 00:15:01.480 align:start position:0% application itself it's very simple it 00:15:01.480 --> 00:15:03.240 align:start position:0% application itself it's very simple it has<00:15:01.660> at<00:15:02.200> the<00:15:02.290> moment<00:15:02.410> a<00:15:02.770> couple<00:15:03.190> of 00:15:03.240 --> 00:15:03.250 align:start position:0% has at the moment a couple of 00:15:03.250 --> 00:15:05.610 align:start position:0% has at the moment a couple of information<00:15:03.700> about<00:15:03.850> yourself<00:15:04.320> so<00:15:05.320> in<00:15:05.530> this 00:15:05.610 --> 00:15:05.620 align:start position:0% information about yourself so in this 00:15:05.620 --> 00:15:07.170 align:start position:0% information about yourself so in this case<00:15:05.800> we<00:15:05.950> just<00:15:05.980> have<00:15:06.190> us<00:15:06.700> and<00:15:06.940> a<00:15:06.970> phone<00:15:07.150> number 00:15:07.170 --> 00:15:07.180 align:start position:0% case we just have us and a phone number 00:15:07.180 --> 00:15:09.090 align:start position:0% case we just have us and a phone number this<00:15:07.780> is<00:15:07.840> data<00:15:08.170> which<00:15:08.380> is<00:15:08.500> taught<00:15:08.680> on<00:15:08.710> my<00:15:08.890> phone 00:15:09.090 --> 00:15:09.100 align:start position:0% this is data which is taught on my phone 00:15:09.100 --> 00:15:10.350 align:start position:0% this is data which is taught on my phone this<00:15:09.370> is<00:15:09.490> not<00:15:09.610> stored<00:15:09.880> anywhere<00:15:10.000> else 00:15:10.350 --> 00:15:10.360 align:start position:0% this is not stored anywhere else 00:15:10.360 --> 00:15:13.080 align:start position:0% this is not stored anywhere else we<00:15:11.320> have<00:15:11.440> verifications<00:15:12.100> this<00:15:12.640> is<00:15:12.790> the<00:15:12.880> stuff 00:15:13.080 --> 00:15:13.090 align:start position:0% we have verifications this is the stuff 00:15:13.090 --> 00:15:14.760 align:start position:0% we have verifications this is the stuff which<00:15:13.300> we<00:15:13.420> hopefully<00:15:13.600> can<00:15:13.810> give<00:15:14.080> you<00:15:14.230> as<00:15:14.380> part 00:15:14.760 --> 00:15:14.770 align:start position:0% which we hopefully can give you as part 00:15:14.770 --> 00:15:16.770 align:start position:0% which we hopefully can give you as part of<00:15:14.890> this<00:15:15.070> experiment<00:15:15.850> or<00:15:16.240> at<00:15:16.390> least<00:15:16.540> for<00:15:16.660> some 00:15:16.770 --> 00:15:16.780 align:start position:0% of this experiment or at least for some 00:15:16.780 --> 00:15:18.750 align:start position:0% of this experiment or at least for some of<00:15:16.810> you<00:15:16.990> and<00:15:17.650> you<00:15:17.830> see<00:15:17.980> that<00:15:18.190> you<00:15:18.610> haven't 00:15:18.750 --> 00:15:18.760 align:start position:0% of you and you see that you haven't 00:15:18.760 --> 00:15:20.550 align:start position:0% of you and you see that you haven't batch<00:15:19.030> you<00:15:19.270> have<00:15:19.360> attended<00:15:19.630> this<00:15:19.930> conference 00:15:20.550 --> 00:15:20.560 align:start position:0% batch you have attended this conference 00:15:20.560 --> 00:15:22.290 align:start position:0% batch you have attended this conference so<00:15:21.040> that<00:15:21.550> might<00:15:21.730> be<00:15:21.880> an<00:15:21.940> interesting<00:15:22.030> thing 00:15:22.290 --> 00:15:22.300 align:start position:0% so that might be an interesting thing 00:15:22.300 --> 00:15:24.480 align:start position:0% so that might be an interesting thing for<00:15:22.630> next<00:15:22.900> time<00:15:23.050> if<00:15:23.200> you<00:15:23.380> go<00:15:23.980> somewhere<00:15:24.400> and 00:15:24.480 --> 00:15:24.490 align:start position:0% for next time if you go somewhere and 00:15:24.490 --> 00:15:26.160 align:start position:0% for next time if you go somewhere and you<00:15:24.610> want<00:15:24.760> to<00:15:24.850> demonstrate<00:15:25.240> this<00:15:25.780> that<00:15:26.020> you 00:15:26.160 --> 00:15:26.170 align:start position:0% you want to demonstrate this that you 00:15:26.170 --> 00:15:27.630 align:start position:0% you want to demonstrate this that you and<00:15:26.410> I<00:15:26.500> have<00:15:26.680> a<00:15:26.710> certain<00:15:26.980> experience<00:15:27.340> oh<00:15:27.550> you 00:15:27.630 --> 00:15:27.640 align:start position:0% and I have a certain experience oh you 00:15:27.640 --> 00:15:30.240 align:start position:0% and I have a certain experience oh you have<00:15:27.730> learned<00:15:27.970> something<00:15:28.560> or<00:15:29.560> get<00:15:29.800> a<00:15:29.830> discount 00:15:30.240 --> 00:15:30.250 align:start position:0% have learned something or get a discount 00:15:30.250 --> 00:15:32.010 align:start position:0% have learned something or get a discount for<00:15:30.340> for<00:15:30.760> other<00:15:30.940> other<00:15:31.390> means<00:15:31.570> so<00:15:31.690> that's<00:15:31.870> kind 00:15:32.010 --> 00:15:32.020 align:start position:0% for for other other means so that's kind 00:15:32.020 --> 00:15:34.650 align:start position:0% for for other other means so that's kind of<00:15:32.050> the<00:15:32.230> the<00:15:33.130> verifications<00:15:33.820> as<00:15:34.390> peda 00:15:34.650 --> 00:15:34.660 align:start position:0% of the the verifications as peda 00:15:34.660 --> 00:15:36.030 align:start position:0% of the the verifications as peda mentioned<00:15:35.020> there<00:15:35.140> multiple<00:15:35.350> accounts<00:15:35.890> your 00:15:36.030 --> 00:15:36.040 align:start position:0% mentioned there multiple accounts your 00:15:36.040 --> 00:15:36.569 align:start position:0% mentioned there multiple accounts your support<00:15:36.339> now 00:15:36.569 --> 00:15:36.579 align:start position:0% support now 00:15:36.579 --> 00:15:38.039 align:start position:0% support now so<00:15:36.639> in<00:15:36.759> this<00:15:36.850> demo<00:15:37.059> I<00:15:37.209> just<00:15:37.480> have<00:15:37.660> at<00:15:37.809> the<00:15:37.899> Mona 00:15:38.039 --> 00:15:38.049 align:start position:0% so in this demo I just have at the Mona 00:15:38.049 --> 00:15:40.169 align:start position:0% so in this demo I just have at the Mona riekki<00:15:38.199> account<00:15:38.679> on<00:15:38.829> this<00:15:38.980> and<00:15:39.459> what<00:15:39.939> I<00:15:39.970> show 00:15:40.169 --> 00:15:40.179 align:start position:0% riekki account on this and what I show 00:15:40.179 --> 00:15:43.679 align:start position:0% riekki account on this and what I show you<00:15:40.239> now<00:15:40.480> is<00:15:40.660> a<00:15:41.910> mobile<00:15:42.910> phone<00:15:43.029> app<00:15:43.209> so<00:15:43.420> what<00:15:43.569> we 00:15:43.679 --> 00:15:43.689 align:start position:0% you now is a mobile phone app so what we 00:15:43.689 --> 00:15:46.739 align:start position:0% you now is a mobile phone app so what we have<00:15:43.839> here<00:15:44.170> is<00:15:44.369> the<00:15:45.369> Mobile<00:15:45.610> Safari<00:15:45.759> it's<00:15:46.569> just 00:15:46.739 --> 00:15:46.749 align:start position:0% have here is the Mobile Safari it's just 00:15:46.749 --> 00:15:49.590 align:start position:0% have here is the Mobile Safari it's just a<00:15:46.809> simple<00:15:47.170> dab<00:15:47.350> and<00:15:47.790> what<00:15:48.790> I<00:15:48.819> do<00:15:48.999> is<00:15:49.119> I<00:15:49.269> connect 00:15:49.590 --> 00:15:49.600 align:start position:0% a simple dab and what I do is I connect 00:15:49.600 --> 00:15:53.249 align:start position:0% a simple dab and what I do is I connect now<00:15:49.809> my<00:15:50.079> you<00:15:50.139> port<00:15:50.470> with<00:15:51.119> which<00:15:52.119> to<00:15:52.239> stop<00:15:52.449> so 00:15:53.249 --> 00:15:53.259 align:start position:0% now my you port with which to stop so 00:15:53.259 --> 00:15:55.530 align:start position:0% now my you port with which to stop so what<00:15:53.470> it<00:15:53.589> does<00:15:53.679> it<00:15:53.949> jumps<00:15:54.489> like<00:15:54.639> the<00:15:55.179> Facebook 00:15:55.530 --> 00:15:55.540 align:start position:0% what it does it jumps like the Facebook 00:15:55.540 --> 00:16:00.150 align:start position:0% what it does it jumps like the Facebook connect<00:15:55.809> into<00:15:56.819> doesn't<00:15:57.819> work<00:15:57.910> into<00:15:58.809> the<00:15:59.160> into 00:16:00.150 --> 00:16:00.160 align:start position:0% connect into doesn't work into the into 00:16:00.160 --> 00:16:02.340 align:start position:0% connect into doesn't work into the into the<00:16:00.279> app<00:16:00.399> it<00:16:00.970> pulls<00:16:01.329> now<00:16:01.689> information<00:16:02.199> about 00:16:02.340 --> 00:16:02.350 align:start position:0% the app it pulls now information about 00:16:02.350 --> 00:16:04.789 align:start position:0% the app it pulls now information about the<00:16:02.439> so<00:16:02.529> you<00:16:02.619> see<00:16:02.769> the<00:16:02.889> logo<00:16:03.069> you<00:16:03.879> see<00:16:04.089> the 00:16:04.789 --> 00:16:04.799 align:start position:0% the so you see the logo you see the 00:16:04.799 --> 00:16:06.989 align:start position:0% the so you see the logo you see the details<00:16:05.799> which<00:16:06.100> are<00:16:06.220> requested<00:16:06.699> from<00:16:06.819> this 00:16:06.989 --> 00:16:06.999 align:start position:0% details which are requested from this 00:16:06.999 --> 00:16:09.569 align:start position:0% details which are requested from this application<00:16:07.149> and<00:16:07.749> now<00:16:08.110> I<00:16:08.139> can<00:16:08.470> confirm<00:16:09.399> this 00:16:09.569 --> 00:16:09.579 align:start position:0% application and now I can confirm this 00:16:09.579 --> 00:16:11.609 align:start position:0% application and now I can confirm this what<00:16:09.730> you<00:16:09.850> see<00:16:09.999> on<00:16:10.179> the<00:16:10.269> bottom<00:16:10.420> is<00:16:10.779> is<00:16:11.170> a<00:16:11.230> first 00:16:11.609 --> 00:16:11.619 align:start position:0% what you see on the bottom is is a first 00:16:11.619 --> 00:16:13.470 align:start position:0% what you see on the bottom is is a first attempt<00:16:12.040> to<00:16:12.129> build<00:16:12.429> some<00:16:12.699> trust<00:16:12.910> into<00:16:13.389> this 00:16:13.470 --> 00:16:13.480 align:start position:0% attempt to build some trust into this 00:16:13.480 --> 00:16:15.059 align:start position:0% attempt to build some trust into this whole<00:16:13.689> inject<00:16:14.410> me<00:16:14.529> what<00:16:14.679> you<00:16:14.739> see 00:16:15.059 --> 00:16:15.069 align:start position:0% whole inject me what you see 00:16:15.069 --> 00:16:17.819 align:start position:0% whole inject me what you see I've<00:16:15.249> done<00:16:15.610> this<00:16:15.730> already<00:16:15.910> 67<00:16:16.569> times<00:16:16.829> that's 00:16:17.819 --> 00:16:17.829 align:start position:0% I've done this already 67 times that's 00:16:17.829 --> 00:16:19.350 align:start position:0% I've done this already 67 times that's important<00:16:18.220> because<00:16:18.309> there's<00:16:18.939> so<00:16:19.059> many<00:16:19.149> web 00:16:19.350 --> 00:16:19.360 align:start position:0% important because there's so many web 00:16:19.360 --> 00:16:22.139 align:start position:0% important because there's so many web sites<00:16:19.509> which<00:16:19.749> suddenly<00:16:20.230> get<00:16:20.529> spoofed<00:16:21.519> also<00:16:21.759> it 00:16:22.139 --> 00:16:22.149 align:start position:0% sites which suddenly get spoofed also it 00:16:22.149 --> 00:16:23.729 align:start position:0% sites which suddenly get spoofed also it gives<00:16:22.329> you<00:16:22.480> an<00:16:22.569> additional<00:16:22.809> level<00:16:23.350> of<00:16:23.559> trust 00:16:23.729 --> 00:16:23.739 align:start position:0% gives you an additional level of trust 00:16:23.739 --> 00:16:26.249 align:start position:0% gives you an additional level of trust as<00:16:23.980> love<00:16:24.220> is<00:16:24.369> not<00:16:24.610> the<00:16:25.179> final<00:16:25.480> version<00:16:25.689> but 00:16:26.249 --> 00:16:26.259 align:start position:0% as love is not the final version but 00:16:26.259 --> 00:16:28.229 align:start position:0% as love is not the final version but that's<00:16:26.559> the<00:16:26.860> first<00:16:27.069> start<00:16:27.279> so<00:16:27.850> what<00:16:27.939> you<00:16:28.029> do<00:16:28.149> is 00:16:28.229 --> 00:16:28.239 align:start position:0% that's the first start so what you do is 00:16:28.239 --> 00:16:31.439 align:start position:0% that's the first start so what you do is you<00:16:28.480> log<00:16:28.660> in<00:16:28.869> and<00:16:29.230> now<00:16:29.739> what<00:16:30.549> it<00:16:30.670> does<00:16:30.699> if<00:16:31.299> the 00:16:31.439 --> 00:16:31.449 align:start position:0% you log in and now what it does if the 00:16:31.449 --> 00:16:33.749 align:start position:0% you log in and now what it does if the network<00:16:31.749> is<00:16:31.899> not<00:16:32.139> fast<00:16:32.350> enough<00:16:32.410> it<00:16:32.889> will<00:16:33.399> show 00:16:33.749 --> 00:16:33.759 align:start position:0% network is not fast enough it will show 00:16:33.759 --> 00:16:36.960 align:start position:0% network is not fast enough it will show my<00:16:34.149> name<00:16:34.860> and<00:16:35.860> just<00:16:36.129> a<00:16:36.189> photo<00:16:36.429> that's 00:16:36.960 --> 00:16:36.970 align:start position:0% my name and just a photo that's 00:16:36.970 --> 00:16:38.249 align:start position:0% my name and just a photo that's something<00:16:37.269> which<00:16:37.389> is<00:16:37.509> just<00:16:37.540> local<00:16:37.899> there's 00:16:38.249 --> 00:16:38.259 align:start position:0% something which is just local there's 00:16:38.259 --> 00:16:39.960 align:start position:0% something which is just local there's not<00:16:38.499> need<00:16:38.739> to<00:16:38.889> be<00:16:38.980> store<00:16:39.189> because<00:16:39.549> it's<00:16:39.670> a<00:16:39.730> tap 00:16:39.960 --> 00:16:39.970 align:start position:0% not need to be store because it's a tap 00:16:39.970 --> 00:16:41.609 align:start position:0% not need to be store because it's a tap it's<00:16:40.179> only<00:16:40.449> a<00:16:40.569> metaphor<00:16:40.809> but<00:16:41.230> it<00:16:41.350> gives<00:16:41.499> the 00:16:41.609 --> 00:16:41.619 align:start position:0% it's only a metaphor but it gives the 00:16:41.619 --> 00:16:43.319 align:start position:0% it's only a metaphor but it gives the user<00:16:41.769> right<00:16:42.069> it<00:16:42.489> could<00:16:42.639> use<00:16:42.790> experience<00:16:43.209> that 00:16:43.319 --> 00:16:43.329 align:start position:0% user right it could use experience that 00:16:43.329 --> 00:16:45.299 align:start position:0% user right it could use experience that he's<00:16:43.569> now<00:16:43.779> locked<00:16:44.019> in<00:16:44.199> and<00:16:44.410> not<00:16:44.649> your<00:16:44.949> friend 00:16:45.299 --> 00:16:45.309 align:start position:0% he's now locked in and not your friend 00:16:45.309 --> 00:16:46.829 align:start position:0% he's now locked in and not your friend or<00:16:45.429> someone<00:16:45.610> else<00:16:45.699> what<00:16:46.299> they're<00:16:46.389> doing<00:16:46.569> hours 00:16:46.829 --> 00:16:46.839 align:start position:0% or someone else what they're doing hours 00:16:46.839 --> 00:16:49.409 align:start position:0% or someone else what they're doing hours very<00:16:47.529> simple<00:16:47.949> and<00:16:48.279> what<00:16:48.790> we<00:16:48.879> have<00:16:49.029> in<00:16:49.209> years 00:16:49.409 --> 00:16:49.419 align:start position:0% very simple and what we have in years 00:16:49.419 --> 00:16:51.210 align:start position:0% very simple and what we have in years you<00:16:49.600> can<00:16:49.809> buy<00:16:50.019> a<00:16:50.049> certain<00:16:50.619> set<00:16:50.829> of<00:16:50.860> shares 00:16:51.210 --> 00:16:51.220 align:start position:0% you can buy a certain set of shares 00:16:51.220 --> 00:16:53.100 align:start position:0% you can buy a certain set of shares which<00:16:51.790> just<00:16:52.059> like<00:16:52.329> an<00:16:52.480> example<00:16:52.929> of<00:16:53.019> an 00:16:53.100 --> 00:16:53.110 align:start position:0% which just like an example of an 00:16:53.110 --> 00:16:55.409 align:start position:0% which just like an example of an interaction<00:16:53.470> with<00:16:53.799> a<00:16:53.860> smart<00:16:54.189> contact<00:16:54.579> so<00:16:55.299> if<00:16:55.360> I 00:16:55.409 --> 00:16:55.419 align:start position:0% interaction with a smart contact so if I 00:16:55.419 --> 00:16:57.600 align:start position:0% interaction with a smart contact so if I click<00:16:55.600> on<00:16:55.720> buy<00:16:56.439> shares<00:16:56.679> what<00:16:57.189> it<00:16:57.279> does<00:16:57.429> it 00:16:57.600 --> 00:16:57.610 align:start position:0% click on buy shares what it does it 00:16:57.610 --> 00:16:59.009 align:start position:0% click on buy shares what it does it jumps<00:16:57.850> back<00:16:57.910> into<00:16:58.179> the<00:16:58.329> application<00:16:58.449> and<00:16:58.929> now 00:16:59.009 --> 00:16:59.019 align:start position:0% jumps back into the application and now 00:16:59.019 --> 00:17:00.989 align:start position:0% jumps back into the application and now what<00:16:59.259> you<00:16:59.379> see<00:16:59.559> here<00:16:59.799> is<00:16:59.949> a<00:17:00.549> transaction 00:17:00.989 --> 00:17:00.999 align:start position:0% what you see here is a transaction 00:17:00.999 --> 00:17:03.210 align:start position:0% what you see here is a transaction screen<00:17:01.509> and<00:17:01.689> that's<00:17:01.749> very<00:17:02.110> important<00:17:02.470> so<00:17:02.499> and 00:17:03.210 --> 00:17:03.220 align:start position:0% screen and that's very important so and 00:17:03.220 --> 00:17:05.610 align:start position:0% screen and that's very important so and what<00:17:03.669> you<00:17:03.790> see<00:17:03.939> is<00:17:03.999> the<00:17:04.870> smart<00:17:05.139> contact<00:17:05.439> you 00:17:05.610 --> 00:17:05.620 align:start position:0% what you see is the smart contact you 00:17:05.620 --> 00:17:07.559 align:start position:0% what you see is the smart contact you are<00:17:05.679> interacting<00:17:05.949> with<00:17:06.220> it<00:17:07.059> gives<00:17:07.269> you<00:17:07.419> what 00:17:07.559 --> 00:17:07.569 align:start position:0% are interacting with it gives you what 00:17:07.569 --> 00:17:09.240 align:start position:0% are interacting with it gives you what kind<00:17:07.779> of<00:17:07.839> function<00:17:08.319> call<00:17:08.529> you're<00:17:08.679> doing<00:17:08.889> and 00:17:09.240 --> 00:17:09.250 align:start position:0% kind of function call you're doing and 00:17:09.250 --> 00:17:12.120 align:start position:0% kind of function call you're doing and as<00:17:09.610> well<00:17:09.789> the<00:17:10.209> 56<00:17:10.809> shares<00:17:11.500> I<00:17:11.649> just<00:17:11.860> requested 00:17:12.120 --> 00:17:12.130 align:start position:0% as well the 56 shares I just requested 00:17:12.130 --> 00:17:14.340 align:start position:0% as well the 56 shares I just requested to<00:17:12.429> buy<00:17:12.579> and<00:17:12.939> that's<00:17:13.539> just<00:17:13.779> important<00:17:14.260> because 00:17:14.340 --> 00:17:14.350 align:start position:0% to buy and that's just important because 00:17:14.350 --> 00:17:16.439 align:start position:0% to buy and that's just important because at<00:17:14.829> the<00:17:14.919> moment<00:17:14.980> how<00:17:15.250> do<00:17:15.309> you<00:17:15.459> know<00:17:15.730> where<00:17:16.389> the 00:17:16.439 --> 00:17:16.449 align:start position:0% at the moment how do you know where the 00:17:16.449 --> 00:17:18.000 align:start position:0% at the moment how do you know where the Tyrian<00:17:16.750> that<00:17:17.169> what<00:17:17.380> you're<00:17:17.529> about<00:17:17.679> to<00:17:17.740> sign 00:17:18.000 --> 00:17:18.010 align:start position:0% Tyrian that what you're about to sign 00:17:18.010 --> 00:17:20.399 align:start position:0% Tyrian that what you're about to sign and<00:17:18.309> I<00:17:18.699> think<00:17:18.880> that's<00:17:19.029> kind<00:17:19.209> of<00:17:19.240> the<00:17:19.449> the<00:17:19.990> user 00:17:20.399 --> 00:17:20.409 align:start position:0% and I think that's kind of the the user 00:17:20.409 --> 00:17:22.259 align:start position:0% and I think that's kind of the the user experience<00:17:20.799> we<00:17:20.889> want<00:17:21.069> to<00:17:21.130> build<00:17:21.220> in<00:17:21.429> that<00:17:22.000> can 00:17:22.259 --> 00:17:22.269 align:start position:0% experience we want to build in that can 00:17:22.269 --> 00:17:23.819 align:start position:0% experience we want to build in that can be<00:17:22.389> in<00:17:22.600> the<00:17:22.659> future<00:17:22.959> maybe<00:17:23.110> more<00:17:23.350> customized 00:17:23.819 --> 00:17:23.829 align:start position:0% be in the future maybe more customized 00:17:23.829 --> 00:17:25.289 align:start position:0% be in the future maybe more customized screens<00:17:24.159> and<00:17:24.459> they<00:17:24.610> will<00:17:24.760> look<00:17:24.880> a<00:17:25.000> bit<00:17:25.120> more 00:17:25.289 --> 00:17:25.299 align:start position:0% screens and they will look a bit more 00:17:25.299 --> 00:17:26.909 align:start position:0% screens and they will look a bit more beautiful<00:17:25.449> but<00:17:26.199> for<00:17:26.380> now<00:17:26.439> this<00:17:26.620> is<00:17:26.679> the 00:17:26.909 --> 00:17:26.919 align:start position:0% beautiful but for now this is the 00:17:26.919 --> 00:17:30.330 align:start position:0% beautiful but for now this is the starting<00:17:27.850> point<00:17:28.000> so<00:17:28.440> what<00:17:29.440> I<00:17:29.470> do<00:17:29.620> now<00:17:29.799> in<00:17:30.039> the 00:17:30.330 --> 00:17:30.340 align:start position:0% starting point so what I do now in the 00:17:30.340 --> 00:17:32.789 align:start position:0% starting point so what I do now in the moment<00:17:30.639> I<00:17:30.700> do<00:17:30.760> prove<00:17:31.210> I<00:17:31.510> need<00:17:31.990> now<00:17:32.200> to<00:17:32.260> use<00:17:32.590> my 00:17:32.789 --> 00:17:32.799 align:start position:0% moment I do prove I need now to use my 00:17:32.799 --> 00:17:34.500 align:start position:0% moment I do prove I need now to use my private<00:17:33.039> key<00:17:33.309> therefore<00:17:33.730> I<00:17:33.760> need<00:17:33.880> to<00:17:34.000> put<00:17:34.330> my 00:17:34.500 --> 00:17:34.510 align:start position:0% private key therefore I need to put my 00:17:34.510 --> 00:17:37.169 align:start position:0% private key therefore I need to put my finger<00:17:35.019> on<00:17:35.049> it<00:17:35.169> and<00:17:35.590> to<00:17:36.190> unlock<00:17:36.399> the<00:17:36.820> key<00:17:37.059> which 00:17:37.169 --> 00:17:37.179 align:start position:0% finger on it and to unlock the key which 00:17:37.179 --> 00:17:39.000 align:start position:0% finger on it and to unlock the key which is<00:17:37.299> in<00:17:37.389> the<00:17:37.450> secure<00:17:37.750> Enclave<00:17:37.899> and<00:17:38.260> do<00:17:38.889> the 00:17:39.000 --> 00:17:39.010 align:start position:0% is in the secure Enclave and do the 00:17:39.010 --> 00:17:40.769 align:start position:0% is in the secure Enclave and do the signing<00:17:39.250> now<00:17:39.519> and<00:17:39.789> now<00:17:40.149> it<00:17:40.240> will<00:17:40.330> take<00:17:40.389> a<00:17:40.570> few 00:17:40.769 --> 00:17:40.779 align:start position:0% signing now and now it will take a few 00:17:40.779 --> 00:17:42.810 align:start position:0% signing now and now it will take a few seconds<00:17:41.320> obviously<00:17:41.649> so<00:17:41.860> that's<00:17:42.370> kind<00:17:42.580> of<00:17:42.610> what 00:17:42.810 --> 00:17:42.820 align:start position:0% seconds obviously so that's kind of what 00:17:42.820 --> 00:17:44.820 align:start position:0% seconds obviously so that's kind of what you<00:17:42.940> guys<00:17:43.059> know<00:17:43.240> so<00:17:44.080> back<00:17:44.529> to<00:17:44.559> the 00:17:44.820 --> 00:17:44.830 align:start position:0% you guys know so back to the 00:17:44.830 --> 00:17:47.850 align:start position:0% you guys know so back to the presentation<00:17:45.899> so<00:17:46.899> what<00:17:47.289> we<00:17:47.409> did<00:17:47.559> just 00:17:47.850 --> 00:17:47.860 align:start position:0% presentation so what we did just 00:17:47.860 --> 00:17:50.840 align:start position:0% presentation so what we did just recently<00:17:48.279> was<00:17:48.940> in<00:17:48.970> the<00:17:49.270> city<00:17:49.450> of<00:17:49.600> soup 00:17:50.840 --> 00:17:50.850 align:start position:0% recently was in the city of soup 00:17:50.850 --> 00:17:53.870 align:start position:0% recently was in the city of soup a<00:17:50.880> little<00:17:51.300> project<00:17:51.900> with<00:17:52.230> them<00:17:52.350> and<00:17:52.590> it<00:17:53.010> is<00:17:53.220> a 00:17:53.870 --> 00:17:53.880 align:start position:0% a little project with them and it is a 00:17:53.880 --> 00:17:55.970 align:start position:0% a little project with them and it is a four-step<00:17:54.660> thanks<00:17:54.900> to<00:17:54.990> you<00:17:55.110> best<00:17:55.440> if<00:17:55.620> you<00:17:55.710> down 00:17:55.970 --> 00:17:55.980 align:start position:0% four-step thanks to you best if you down 00:17:55.980 --> 00:17:59.210 align:start position:0% four-step thanks to you best if you down it<00:17:56.160> your<00:17:56.400> mobile<00:17:56.910> application<00:17:58.040> generate<00:17:59.040> your 00:17:59.210 --> 00:17:59.220 align:start position:0% it your mobile application generate your 00:17:59.220 --> 00:18:02.240 align:start position:0% it your mobile application generate your additional<00:17:59.820> identity<00:18:00.210> and<00:18:00.420> you<00:18:01.080> go<00:18:01.230> and<00:18:01.590> to<00:18:02.190> a 00:18:02.240 --> 00:18:02.250 align:start position:0% additional identity and you go and to a 00:18:02.250 --> 00:18:04.460 align:start position:0% additional identity and you go and to a portal<00:18:02.700> on<00:18:02.910> this<00:18:03.600> portal<00:18:03.900> you<00:18:03.960> can<00:18:04.110> enter<00:18:04.320> like 00:18:04.460 --> 00:18:04.470 align:start position:0% portal on this portal you can enter like 00:18:04.470 --> 00:18:05.690 align:start position:0% portal on this portal you can enter like a<00:18:04.500> certain<00:18:04.860> set<00:18:04.980> of<00:18:05.010> information<00:18:05.280> about 00:18:05.690 --> 00:18:05.700 align:start position:0% a certain set of information about 00:18:05.700 --> 00:18:09.050 align:start position:0% a certain set of information about yourself<00:18:05.790> your<00:18:06.390> name<00:18:06.570> and<00:18:07.380> your<00:18:07.830> ID<00:18:08.220> card<00:18:08.640> this 00:18:09.050 --> 00:18:09.060 align:start position:0% yourself your name and your ID card this 00:18:09.060 --> 00:18:10.460 align:start position:0% yourself your name and your ID card this is<00:18:09.240> only<00:18:09.390> stuff<00:18:09.750> which<00:18:09.930> you<00:18:10.050> would<00:18:10.230> give<00:18:10.440> to 00:18:10.460 --> 00:18:10.470 align:start position:0% is only stuff which you would give to 00:18:10.470 --> 00:18:13.040 align:start position:0% is only stuff which you would give to the<00:18:10.980> city<00:18:11.160> of<00:18:11.310> soup<00:18:11.730> as<00:18:11.940> a<00:18:11.970> portal<00:18:12.390> and<00:18:12.510> then 00:18:13.040 --> 00:18:13.050 align:start position:0% the city of soup as a portal and then 00:18:13.050 --> 00:18:14.420 align:start position:0% the city of soup as a portal and then the<00:18:13.170> second<00:18:13.470> step<00:18:13.620> you<00:18:13.680> go<00:18:13.920> into<00:18:14.190> the<00:18:14.310> office 00:18:14.420 --> 00:18:14.430 align:start position:0% the second step you go into the office 00:18:14.430 --> 00:18:19.280 align:start position:0% the second step you go into the office there<00:18:15.110> with<00:18:16.110> your<00:18:16.320> ID<00:18:16.620> card<00:18:16.920> and<00:18:17.600> prove<00:18:18.600> that 00:18:19.280 --> 00:18:19.290 align:start position:0% there with your ID card and prove that 00:18:19.290 --> 00:18:21.320 align:start position:0% there with your ID card and prove that you<00:18:19.500> are<00:18:19.650> the<00:18:19.740> person<00:18:20.100> who<00:18:20.130> claims<00:18:20.910> to<00:18:21.090> be<00:18:21.120> this 00:18:21.320 --> 00:18:21.330 align:start position:0% you are the person who claims to be this 00:18:21.330 --> 00:18:23.440 align:start position:0% you are the person who claims to be this so<00:18:21.930> it's<00:18:22.050> an<00:18:22.140> out<00:18:22.260> like<00:18:22.500> a<00:18:22.530> real<00:18:22.770> in<00:18:23.160> life 00:18:23.440 --> 00:18:23.450 align:start position:0% so it's an out like a real in life 00:18:23.450 --> 00:18:26.840 align:start position:0% so it's an out like a real in life validation<00:18:24.450> and<00:18:24.900> what<00:18:25.190> the<00:18:26.190> clerk<00:18:26.490> then<00:18:26.700> can 00:18:26.840 --> 00:18:26.850 align:start position:0% validation and what the clerk then can 00:18:26.850 --> 00:18:29.210 align:start position:0% validation and what the clerk then can do<00:18:27.000> is<00:18:27.120> they<00:18:27.300> go<00:18:27.480> to<00:18:27.510> their<00:18:28.350> internal<00:18:28.770> portal 00:18:29.210 --> 00:18:29.220 align:start position:0% do is they go to their internal portal 00:18:29.220 --> 00:18:32.240 align:start position:0% do is they go to their internal portal and<00:18:29.400> click<00:18:30.150> one<00:18:30.810> button<00:18:30.840> and<00:18:31.290> it<00:18:31.740> pushed<00:18:32.040> a 00:18:32.240 --> 00:18:32.250 align:start position:0% and click one button and it pushed a 00:18:32.250 --> 00:18:34.820 align:start position:0% and click one button and it pushed a notification<00:18:32.970> back<00:18:33.120> to<00:18:33.330> you<00:18:33.420> as<00:18:33.540> a<00:18:33.570> user<00:18:33.830> this 00:18:34.820 --> 00:18:34.830 align:start position:0% notification back to you as a user this 00:18:34.830 --> 00:18:37.520 align:start position:0% notification back to you as a user this information<00:18:35.370> now<00:18:35.550> contains<00:18:36.000> that<00:18:36.300> does<00:18:37.290> your 00:18:37.520 --> 00:18:37.530 align:start position:0% information now contains that does your 00:18:37.530 --> 00:18:40.610 align:start position:0% information now contains that does your name<00:18:37.710> you're<00:18:38.400> a<00:18:38.850> citizen<00:18:39.300> of<00:18:39.540> the<00:18:39.660> city<00:18:39.870> and 00:18:40.610 --> 00:18:40.620 align:start position:0% name you're a citizen of the city and 00:18:40.620 --> 00:18:42.380 align:start position:0% name you're a citizen of the city and someone<00:18:41.040> has<00:18:41.160> validated<00:18:41.670> so<00:18:41.880> suddenly<00:18:42.210> we 00:18:42.380 --> 00:18:42.390 align:start position:0% someone has validated so suddenly we 00:18:42.390 --> 00:18:43.910 align:start position:0% someone has validated so suddenly we create<00:18:42.690> this<00:18:42.870> a<00:18:43.080> connection<00:18:43.500> between<00:18:43.650> your 00:18:43.910 --> 00:18:43.920 align:start position:0% create this a connection between your 00:18:43.920 --> 00:18:46.610 align:start position:0% create this a connection between your theorem<00:18:44.610> address<00:18:44.910> and<00:18:45.660> your<00:18:45.870> real<00:18:46.050> person<00:18:46.500> and 00:18:46.610 --> 00:18:46.620 align:start position:0% theorem address and your real person and 00:18:46.620 --> 00:18:48.650 align:start position:0% theorem address and your real person and someone<00:18:46.890> has<00:18:47.100> validated<00:18:47.430> and<00:18:47.970> if<00:18:48.180> you<00:18:48.330> trust 00:18:48.650 --> 00:18:48.660 align:start position:0% someone has validated and if you trust 00:18:48.660 --> 00:18:50.810 align:start position:0% someone has validated and if you trust that<00:18:48.750> the<00:18:48.960> city<00:18:49.140> of<00:18:49.260> Suk's<00:18:49.610> process<00:18:50.610> all<00:18:50.730> the 00:18:50.810 --> 00:18:50.820 align:start position:0% that the city of Suk's process all the 00:18:50.820 --> 00:18:52.190 align:start position:0% that the city of Suk's process all the clerk's<00:18:51.090> are<00:18:51.270> doing<00:18:51.480> that<00:18:51.570> only<00:18:51.810> if<00:18:52.020> it's 00:18:52.190 --> 00:18:52.200 align:start position:0% clerk's are doing that only if it's 00:18:52.200 --> 00:18:54.350 align:start position:0% clerk's are doing that only if it's right<00:18:52.710> you<00:18:53.160> can<00:18:53.340> never<00:18:53.490> trust<00:18:53.790> this<00:18:54.090> at<00:18:54.240> the 00:18:54.350 --> 00:18:54.360 align:start position:0% right you can never trust this at the 00:18:54.360 --> 00:18:56.180 align:start position:0% right you can never trust this at the station<00:18:54.690> or<00:18:54.780> this<00:18:54.900> badge<00:18:55.170> from<00:18:55.800> the<00:18:55.890> city<00:18:56.130> of 00:18:56.180 --> 00:18:56.190 align:start position:0% station or this badge from the city of 00:18:56.190 --> 00:18:58.310 align:start position:0% station or this badge from the city of soup<00:18:56.430> so<00:18:57.120> we<00:18:57.240> are<00:18:57.300> working<00:18:57.540> with<00:18:57.780> a<00:18:57.810> couple<00:18:58.200> of 00:18:58.310 --> 00:18:58.320 align:start position:0% soup so we are working with a couple of 00:18:58.320 --> 00:18:59.870 align:start position:0% soup so we are working with a couple of integrations<00:18:58.860> like<00:18:58.980> using<00:18:59.190> this<00:18:59.460> sort<00:18:59.670> thing 00:18:59.870 --> 00:18:59.880 align:start position:0% integrations like using this sort thing 00:18:59.880 --> 00:19:02.720 align:start position:0% integrations like using this sort thing now<00:19:00.000> for<00:19:00.530> the<00:19:01.530> city<00:19:01.710> itself<00:19:02.010> for<00:19:02.280> like<00:19:02.400> simply 00:19:02.720 --> 00:19:02.730 align:start position:0% now for the city itself for like simply 00:19:02.730 --> 00:19:04.760 align:start position:0% now for the city itself for like simply a<00:19:02.880> voting<00:19:03.270> so<00:19:03.720> they<00:19:03.840> don't<00:19:04.020> do<00:19:04.140> like<00:19:04.260> voting 00:19:04.760 --> 00:19:04.770 align:start position:0% a voting so they don't do like voting 00:19:04.770 --> 00:19:07.310 align:start position:0% a voting so they don't do like voting voting<00:19:04.920> against<00:19:05.190> Malak<00:19:05.870> opening<00:19:06.870> times<00:19:07.080> of 00:19:07.310 --> 00:19:07.320 align:start position:0% voting against Malak opening times of 00:19:07.320 --> 00:19:08.810 align:start position:0% voting against Malak opening times of the<00:19:07.410> swimming<00:19:07.680> pool<00:19:07.860> or<00:19:07.980> something<00:19:08.070> else<00:19:08.370> as<00:19:08.550> a 00:19:08.810 --> 00:19:08.820 align:start position:0% the swimming pool or something else as a 00:19:08.820 --> 00:19:10.850 align:start position:0% the swimming pool or something else as a testbed<00:19:09.150> but<00:19:09.750> it's<00:19:09.900> a<00:19:10.020> it's<00:19:10.050> a<00:19:10.290> start<00:19:10.560> and<00:19:10.770> as 00:19:10.850 --> 00:19:10.860 align:start position:0% testbed but it's a it's a start and as 00:19:10.860 --> 00:19:12.230 align:start position:0% testbed but it's a it's a start and as well<00:19:11.070> we<00:19:11.220> are<00:19:11.310> working<00:19:11.580> with<00:19:11.790> mountain<00:19:12.030> port 00:19:12.230 --> 00:19:12.240 align:start position:0% well we are working with mountain port 00:19:12.240 --> 00:19:13.610 align:start position:0% well we are working with mountain port and<00:19:12.390> others<00:19:12.600> to<00:19:12.810> integrate<00:19:13.260> this<00:19:13.410> information 00:19:13.610 --> 00:19:13.620 align:start position:0% and others to integrate this information 00:19:13.620 --> 00:19:17.090 align:start position:0% and others to integrate this information now<00:19:14.130> into<00:19:14.940> our<00:19:15.500> into<00:19:16.500> into<00:19:16.740> their<00:19:16.890> platform 00:19:17.090 --> 00:19:17.100 align:start position:0% now into our into into their platform 00:19:17.100 --> 00:19:19.310 align:start position:0% now into our into into their platform which<00:19:17.880> allows<00:19:18.000> them<00:19:18.240> to<00:19:18.300> trust<00:19:18.600> immediately 00:19:19.310 --> 00:19:19.320 align:start position:0% which allows them to trust immediately 00:19:19.320 --> 00:19:22.670 align:start position:0% which allows them to trust immediately there's<00:19:19.590> eternity<00:19:20.010> much<00:19:20.340> more<00:19:20.840> so<00:19:21.840> now<00:19:22.050> and 00:19:22.670 --> 00:19:22.680 align:start position:0% there's eternity much more so now and 00:19:22.680 --> 00:19:24.170 align:start position:0% there's eternity much more so now and that's<00:19:23.310> that's<00:19:23.520> the<00:19:23.910> end<00:19:23.940> of<00:19:24.090> the 00:19:24.170 --> 00:19:24.180 align:start position:0% that's that's the end of the 00:19:24.180 --> 00:19:26.420 align:start position:0% that's that's the end of the presentation<00:19:24.540> this<00:19:24.900> is<00:19:25.050> the<00:19:25.170> QR<00:19:25.470> code<00:19:25.710> if<00:19:25.950> you 00:19:26.420 --> 00:19:26.430 align:start position:0% presentation this is the QR code if you 00:19:26.430 --> 00:19:29.090 align:start position:0% presentation this is the QR code if you have<00:19:26.550> you<00:19:26.700> port<00:19:27.170> try<00:19:28.170> to<00:19:28.230> scan<00:19:28.530> it<00:19:28.710> I<00:19:28.860> don't 00:19:29.090 --> 00:19:29.100 align:start position:0% have you port try to scan it I don't 00:19:29.100 --> 00:19:30.080 align:start position:0% have you port try to scan it I don't know<00:19:29.190> it<00:19:29.280> was<00:19:29.370> the<00:19:29.490> network<00:19:29.790> connectivity 00:19:30.080 --> 00:19:30.090 align:start position:0% know it was the network connectivity 00:19:30.090 --> 00:19:32.360 align:start position:0% know it was the network connectivity here<00:19:30.570> whether<00:19:31.020> it<00:19:31.140> works<00:19:31.350> and<00:19:31.650> now<00:19:32.160> we<00:19:32.220> have 00:19:32.360 --> 00:19:32.370 align:start position:0% here whether it works and now we have 00:19:32.370 --> 00:19:33.860 align:start position:0% here whether it works and now we have live<00:19:32.550> streams<00:19:32.880> so<00:19:33.000> it's<00:19:33.150> not<00:19:33.300> technically 00:19:33.860 --> 00:19:33.870 align:start position:0% live streams so it's not technically 00:19:33.870 --> 00:19:35.510 align:start position:0% live streams so it's not technically attendance<00:19:34.380> but<00:19:34.560> let's<00:19:34.770> say<00:19:34.890> you<00:19:34.950> listen<00:19:35.400> to 00:19:35.510 --> 00:19:35.520 align:start position:0% attendance but let's say you listen to 00:19:35.520 --> 00:19:36.980 align:start position:0% attendance but let's say you listen to this<00:19:35.640> life<00:19:35.850> because<00:19:36.240> in<00:19:36.360> five<00:19:36.540> minutes<00:19:36.900> we 00:19:36.980 --> 00:19:36.990 align:start position:0% this life because in five minutes we 00:19:36.990 --> 00:19:39.470 align:start position:0% this life because in five minutes we were<00:19:37.080> turned<00:19:37.260> off<00:19:37.470> what<00:19:38.130> happens<00:19:38.460> now<00:19:38.640> you<00:19:38.910> go 00:19:39.470 --> 00:19:39.480 align:start position:0% were turned off what happens now you go 00:19:39.480 --> 00:19:41.660 align:start position:0% were turned off what happens now you go on<00:19:39.600> this<00:19:39.780> it<00:19:39.960> will<00:19:40.140> ask<00:19:40.380> you<00:19:40.710> whether<00:19:41.340> you<00:19:41.490> are 00:19:41.660 --> 00:19:41.670 align:start position:0% on this it will ask you whether you are 00:19:41.670 --> 00:19:45.440 align:start position:0% on this it will ask you whether you are willing<00:19:42.510> to<00:19:42.720> give<00:19:42.980> us<00:19:43.980> right<00:19:44.880> to<00:19:45.120> send<00:19:45.330> you<00:19:45.420> a 00:19:45.440 --> 00:19:45.450 align:start position:0% willing to give us right to send you a 00:19:45.450 --> 00:19:47.270 align:start position:0% willing to give us right to send you a push<00:19:45.600> notification<00:19:45.690> it's<00:19:46.650> a<00:19:46.800> service<00:19:47.100> via 00:19:47.270 --> 00:19:47.280 align:start position:0% push notification it's a service via 00:19:47.280 --> 00:19:49.310 align:start position:0% push notification it's a service via operate<00:19:47.730> at<00:19:48.030> the<00:19:48.210> moment<00:19:48.480> and<00:19:48.660> what<00:19:49.110> it<00:19:49.200> does 00:19:49.310 --> 00:19:49.320 align:start position:0% operate at the moment and what it does 00:19:49.320 --> 00:19:52.340 align:start position:0% operate at the moment and what it does is<00:19:49.530> basically<00:19:49.920> sends<00:19:50.340> a<00:19:50.370> request<00:19:50.520> and<00:19:51.030> in<00:19:51.930> five 00:19:52.340 --> 00:19:52.350 align:start position:0% is basically sends a request and in five 00:19:52.350 --> 00:19:54.230 align:start position:0% is basically sends a request and in five seconds<00:19:52.770> or<00:19:52.830> so<00:19:52.980> after<00:19:53.280> that<00:19:53.310> and<00:19:53.940> we<00:19:54.090> would 00:19:54.230 --> 00:19:54.240 align:start position:0% seconds or so after that and we would 00:19:54.240 --> 00:19:56.570 align:start position:0% seconds or so after that and we would send<00:19:54.480> we<00:19:54.780> will<00:19:54.810> sign<00:19:55.140> a<00:19:55.170> signature<00:19:55.560> or<00:19:55.860> service 00:19:56.570 --> 00:19:56.580 align:start position:0% send we will sign a signature or service 00:19:56.580 --> 00:19:58.700 align:start position:0% send we will sign a signature or service sign<00:19:56.820> a<00:19:57.060> piece<00:19:57.390> of<00:19:57.420> data<00:19:57.750> and<00:19:57.990> they<00:19:58.410> send<00:19:58.650> it 00:19:58.700 --> 00:19:58.710 align:start position:0% sign a piece of data and they send it 00:19:58.710 --> 00:20:00.590 align:start position:0% sign a piece of data and they send it back<00:19:59.010> to<00:19:59.040> you<00:19:59.400> as<00:19:59.640> a<00:19:59.670> personification<00:20:00.180> and 00:20:00.590 --> 00:20:00.600 align:start position:0% back to you as a personification and 00:20:00.600 --> 00:20:02.540 align:start position:0% back to you as a personification and that's<00:20:00.990> the<00:20:01.200> badge<00:20:01.380> of<00:20:01.650> attending<00:20:01.950> here<00:20:02.370> in 00:20:02.540 --> 00:20:02.550 align:start position:0% that's the badge of attending here in 00:20:02.550 --> 00:20:03.310 align:start position:0% that's the badge of attending here in DEFCON 00:20:03.310 --> 00:20:03.320 align:start position:0% DEFCON 00:20:03.320 --> 00:20:06.100 align:start position:0% DEFCON and<00:20:03.770> with<00:20:04.520> that<00:20:04.670> I'm<00:20:05.270> closing<00:20:05.660> and<00:20:05.810> please 00:20:06.100 --> 00:20:06.110 align:start position:0% and with that I'm closing and please 00:20:06.110 --> 00:20:07.660 align:start position:0% and with that I'm closing and please visit<00:20:06.290> our<00:20:06.470> website<00:20:06.830> and<00:20:07.100> look<00:20:07.490> into 00:20:07.660 --> 00:20:07.670 align:start position:0% visit our website and look into 00:20:07.670 --> 00:20:11.650 align:start position:0% visit our website and look into integrating<00:20:08.480> us<00:20:08.540> thank<00:20:09.050> you 00:20:11.650 --> 00:20:11.660 align:start position:0% 00:20:11.660 --> 00:20:15.900 align:start position:0% [Applause] 00:20:15.900 --> 00:20:15.910 align:start position:0% 00:20:15.910 --> 00:20:23.489 align:start position:0% [Music]