WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:19.420 align:start position:0% [Music] 00:00:19.420 --> 00:00:19.430 align:start position:0% 00:00:19.430 --> 00:00:21.920 align:start position:0% hello<00:00:20.760> my<00:00:20.910> name<00:00:21.060> is<00:00:21.119> Ruben<00:00:21.390> I'm<00:00:21.600> here<00:00:21.810> with 00:00:21.920 --> 00:00:21.930 align:start position:0% hello my name is Ruben I'm here with 00:00:21.930 --> 00:00:23.019 align:start position:0% hello my name is Ruben I'm here with Christian<00:00:22.290> and 00:00:23.019 --> 00:00:23.029 align:start position:0% Christian and 00:00:23.029 --> 00:00:25.670 align:start position:0% Christian and we<00:00:24.029> both<00:00:24.180> work<00:00:24.390> at<00:00:24.480> consensus<00:00:24.930> and<00:00:25.140> we<00:00:25.470> want<00:00:25.619> to 00:00:25.670 --> 00:00:25.680 align:start position:0% we both work at consensus and we want to 00:00:25.680 --> 00:00:27.950 align:start position:0% we both work at consensus and we want to give<00:00:25.830> you<00:00:25.920> an<00:00:26.010> update<00:00:26.250> on<00:00:26.279> you<00:00:26.640> port<00:00:26.910> usually<00:00:27.750> I 00:00:27.950 --> 00:00:27.960 align:start position:0% give you an update on you port usually I 00:00:27.960 --> 00:00:30.679 align:start position:0% give you an update on you port usually I start<00:00:28.350> this<00:00:28.500> talks<00:00:28.910> telling<00:00:29.910> about<00:00:30.000> identity 00:00:30.679 --> 00:00:30.689 align:start position:0% start this talks telling about identity 00:00:30.689 --> 00:00:32.359 align:start position:0% start this talks telling about identity in<00:00:30.869> general<00:00:31.170> and<00:00:31.289> how<00:00:31.410> important<00:00:31.770> it<00:00:31.860> is<00:00:31.920> but<00:00:32.309> I 00:00:32.359 --> 00:00:32.369 align:start position:0% in general and how important it is but I 00:00:32.369 --> 00:00:34.220 align:start position:0% in general and how important it is but I think<00:00:32.460> for<00:00:32.790> for<00:00:33.059> this<00:00:33.120> crowd<00:00:33.390> I<00:00:33.600> skipped<00:00:34.199> that 00:00:34.220 --> 00:00:34.230 align:start position:0% think for for this crowd I skipped that 00:00:34.230 --> 00:00:37.160 align:start position:0% think for for this crowd I skipped that part<00:00:34.590> and<00:00:34.790> obviously<00:00:35.790> identity<00:00:36.720> in<00:00:36.840> all<00:00:37.020> the 00:00:37.160 --> 00:00:37.170 align:start position:0% part and obviously identity in all the 00:00:37.170 --> 00:00:39.500 align:start position:0% part and obviously identity in all the kind<00:00:37.739> of<00:00:37.770> forms<00:00:38.040> like<00:00:38.190> for<00:00:38.370> people<00:00:38.699> for<00:00:39.059> tools 00:00:39.500 --> 00:00:39.510 align:start position:0% kind of forms like for people for tools 00:00:39.510 --> 00:00:41.830 align:start position:0% kind of forms like for people for tools for<00:00:39.690> everything<00:00:40.080> it's<00:00:40.920> super<00:00:41.220> important 00:00:41.830 --> 00:00:41.840 align:start position:0% for everything it's super important 00:00:41.840 --> 00:00:44.150 align:start position:0% for everything it's super important today<00:00:42.840> I<00:00:42.960> want<00:00:43.230> to<00:00:43.290> focus<00:00:43.350> on<00:00:43.739> the<00:00:44.010> challenges 00:00:44.150 --> 00:00:44.160 align:start position:0% today I want to focus on the challenges 00:00:44.160 --> 00:00:46.700 align:start position:0% today I want to focus on the challenges I<00:00:44.730> think<00:00:45.090> the<00:00:45.150> community<00:00:45.540> here<00:00:45.780> is<00:00:46.500> dealing 00:00:46.700 --> 00:00:46.710 align:start position:0% I think the community here is dealing 00:00:46.710 --> 00:00:49.430 align:start position:0% I think the community here is dealing with<00:00:46.860> mostly<00:00:47.300> obviously<00:00:48.300> key<00:00:48.449> management<00:00:48.930> we 00:00:49.430 --> 00:00:49.440 align:start position:0% with mostly obviously key management we 00:00:49.440 --> 00:00:50.869 align:start position:0% with mostly obviously key management we spoke<00:00:49.650> about<00:00:49.680> user<00:00:50.070> experience<00:00:50.159> for<00:00:50.760> the 00:00:50.869 --> 00:00:50.879 align:start position:0% spoke about user experience for the 00:00:50.879 --> 00:00:53.840 align:start position:0% spoke about user experience for the average<00:00:50.970> show<00:00:51.269> and<00:00:51.979> mobile<00:00:52.979> and<00:00:53.250> I<00:00:53.580> think<00:00:53.790> we 00:00:53.840 --> 00:00:53.850 align:start position:0% average show and mobile and I think we 00:00:53.850 --> 00:00:55.820 align:start position:0% average show and mobile and I think we had<00:00:53.970> already<00:00:54.089> in<00:00:54.330> the<00:00:54.420> last<00:00:54.570> three<00:00:55.260> days<00:00:55.409> quite 00:00:55.820 --> 00:00:55.830 align:start position:0% had already in the last three days quite 00:00:55.830 --> 00:00:58.009 align:start position:0% had already in the last three days quite some<00:00:56.370> interesting<00:00:56.820> projects<00:00:57.360> with<00:00:57.540> meta<00:00:57.750> mask 00:00:58.009 --> 00:00:58.019 align:start position:0% some interesting projects with meta mask 00:00:58.019 --> 00:01:00.530 align:start position:0% some interesting projects with meta mask with<00:00:58.379> mists<00:00:59.010> and<00:00:59.190> others<00:00:59.549> light<00:01:00.210> lines<00:01:00.449> I 00:01:00.530 --> 00:01:00.540 align:start position:0% with mists and others light lines I 00:01:00.540 --> 00:01:01.610 align:start position:0% with mists and others light lines I think<00:01:00.690> there's<00:01:00.839> a<00:01:00.870> lot<00:01:00.989> of<00:01:01.080> things<00:01:01.229> happening 00:01:01.610 --> 00:01:01.620 align:start position:0% think there's a lot of things happening 00:01:01.620 --> 00:01:03.799 align:start position:0% think there's a lot of things happening and<00:01:02.220> I<00:01:02.280> think<00:01:02.489> we<00:01:02.580> have<00:01:02.729> something<00:01:02.940> which<00:01:03.210> is<00:01:03.390> a 00:01:03.799 --> 00:01:03.809 align:start position:0% and I think we have something which is a 00:01:03.809 --> 00:01:05.570 align:start position:0% and I think we have something which is a little<00:01:04.140> bit<00:01:04.379> different<00:01:04.799> and<00:01:04.979> very 00:01:05.570 --> 00:01:05.580 align:start position:0% little bit different and very 00:01:05.580 --> 00:01:06.980 align:start position:0% little bit different and very complementarity<00:01:06.420> those<00:01:06.570> things<00:01:06.780> which 00:01:06.980 --> 00:01:06.990 align:start position:0% complementarity those things which 00:01:06.990 --> 00:01:09.020 align:start position:0% complementarity those things which already<00:01:07.170> people<00:01:08.100> are<00:01:08.190> working<00:01:08.400> on<00:01:08.580> so<00:01:08.909> it's 00:01:09.020 --> 00:01:09.030 align:start position:0% already people are working on so it's 00:01:09.030 --> 00:01:10.180 align:start position:0% already people are working on so it's pretty<00:01:09.120> exciting 00:01:10.180 --> 00:01:10.190 align:start position:0% pretty exciting 00:01:10.190 --> 00:01:12.410 align:start position:0% pretty exciting identity<00:01:11.190> and<00:01:11.460> data<00:01:11.850> ownership<00:01:12.120> is<00:01:12.390> a 00:01:12.410 --> 00:01:12.420 align:start position:0% identity and data ownership is a 00:01:12.420 --> 00:01:14.960 align:start position:0% identity and data ownership is a obviously<00:01:13.260> huge<00:01:13.530> topic<00:01:13.890> and<00:01:14.040> we<00:01:14.729> will<00:01:14.820> touch 00:01:14.960 --> 00:01:14.970 align:start position:0% obviously huge topic and we will touch 00:01:14.970 --> 00:01:16.700 align:start position:0% obviously huge topic and we will touch on<00:01:15.060> this<00:01:15.240> to<00:01:15.780> certain<00:01:16.080> extent<00:01:16.409> but<00:01:16.530> will<00:01:16.650> not 00:01:16.700 --> 00:01:16.710 align:start position:0% on this to certain extent but will not 00:01:16.710 --> 00:01:18.710 align:start position:0% on this to certain extent but will not completely<00:01:17.369> cover<00:01:17.580> this<00:01:17.790> because<00:01:18.090> ten 00:01:18.710 --> 00:01:18.720 align:start position:0% completely cover this because ten 00:01:18.720 --> 00:01:20.090 align:start position:0% completely cover this because ten minutes<00:01:18.930> is<00:01:18.990> a<00:01:19.020> bit<00:01:19.200> short<00:01:19.590> for<00:01:19.650> some<00:01:19.950> other 00:01:20.090 --> 00:01:20.100 align:start position:0% minutes is a bit short for some other 00:01:20.100 --> 00:01:22.480 align:start position:0% minutes is a bit short for some other stuff<00:01:20.310> so<00:01:20.940> again<00:01:21.150> want<00:01:21.600> to<00:01:21.660> go 00:01:22.480 --> 00:01:22.490 align:start position:0% stuff so again want to go 00:01:22.490 --> 00:01:25.070 align:start position:0% stuff so again want to go first<00:01:23.490> to<00:01:23.850> explain<00:01:24.090> a<00:01:24.240> little<00:01:24.330> bit<00:01:24.480> about<00:01:24.840> the 00:01:25.070 --> 00:01:25.080 align:start position:0% first to explain a little bit about the 00:01:25.080 --> 00:01:28.700 align:start position:0% first to explain a little bit about the design<00:01:25.740> principles<00:01:26.420> from<00:01:27.420> you<00:01:27.570> party<00:01:27.900> class 00:01:28.700 --> 00:01:28.710 align:start position:0% design principles from you party class 00:01:28.710 --> 00:01:32.210 align:start position:0% design principles from you party class and<00:01:29.270> the<00:01:30.270> core<00:01:30.540> things<00:01:30.810> we<00:01:31.020> we<00:01:31.320> believe<00:01:31.470> self 00:01:32.210 --> 00:01:32.220 align:start position:0% and the core things we we believe self 00:01:32.220 --> 00:01:34.250 align:start position:0% and the core things we we believe self seven<00:01:32.550> identity<00:01:32.970> is<00:01:33.090> the<00:01:33.600> solution<00:01:33.900> we<00:01:34.140> need 00:01:34.250 --> 00:01:34.260 align:start position:0% seven identity is the solution we need 00:01:34.260 --> 00:01:37.160 align:start position:0% seven identity is the solution we need to<00:01:34.410> we<00:01:34.740> need<00:01:34.770> to<00:01:35.010> achieve<00:01:35.930> it's<00:01:36.930> really 00:01:37.160 --> 00:01:37.170 align:start position:0% to we need to achieve it's really 00:01:37.170 --> 00:01:39.170 align:start position:0% to we need to achieve it's really important<00:01:37.530> that<00:01:37.560> it's<00:01:37.770> used<00:01:38.250> like<00:01:38.520> easy<00:01:38.880> to 00:01:39.170 --> 00:01:39.180 align:start position:0% important that it's used like easy to 00:01:39.180 --> 00:01:41.390 align:start position:0% important that it's used like easy to use<00:01:39.390> so<00:01:40.200> we<00:01:40.350> have<00:01:40.440> we<00:01:40.590> spend<00:01:40.800> a<00:01:40.830> lot<00:01:40.950> of<00:01:41.010> time<00:01:41.220> on 00:01:41.390 --> 00:01:41.400 align:start position:0% use so we have we spend a lot of time on 00:01:41.400 --> 00:01:43.930 align:start position:0% use so we have we spend a lot of time on thinking<00:01:41.580> about<00:01:42.020> usability<00:01:43.020> and 00:01:43.930 --> 00:01:43.940 align:start position:0% thinking about usability and 00:01:43.940 --> 00:01:46.100 align:start position:0% thinking about usability and ultimately<00:01:44.940> if<00:01:45.120> you<00:01:45.210> want<00:01:45.360> to<00:01:45.420> do<00:01:45.510> anything<00:01:45.720> in 00:01:46.100 --> 00:01:46.110 align:start position:0% ultimately if you want to do anything in 00:01:46.110 --> 00:01:48.280 align:start position:0% ultimately if you want to do anything in the<00:01:46.410> in<00:01:46.980> the<00:01:47.280> digital<00:01:47.580> world 00:01:48.280 --> 00:01:48.290 align:start position:0% the in the digital world 00:01:48.290 --> 00:01:51.020 align:start position:0% the in the digital world reputation<00:01:49.290> and<00:01:49.500> Trust<00:01:49.920> is<00:01:50.220> really<00:01:50.640> important 00:01:51.020 --> 00:01:51.030 align:start position:0% reputation and Trust is really important 00:01:51.030 --> 00:01:52.960 align:start position:0% reputation and Trust is really important so<00:01:51.180> we<00:01:51.690> spend<00:01:51.900> a<00:01:51.930> lot<00:01:52.020> of<00:01:52.050> time<00:01:52.260> thinking<00:01:52.470> about 00:01:52.960 --> 00:01:52.970 align:start position:0% so we spend a lot of time thinking about 00:01:52.970 --> 00:01:55.430 align:start position:0% so we spend a lot of time thinking about attestations<00:01:53.970> and<00:01:54.360> how<00:01:54.420> we<00:01:54.480> we<00:01:54.930> built<00:01:55.110> a 00:01:55.430 --> 00:01:55.440 align:start position:0% attestations and how we we built a 00:01:55.440 --> 00:01:58.450 align:start position:0% attestations and how we we built a platform<00:01:56.280> which<00:01:56.850> can<00:01:57.210> establish<00:01:57.720> this<00:01:58.020> trust 00:01:58.450 --> 00:01:58.460 align:start position:0% platform which can establish this trust 00:01:58.460 --> 00:02:01.960 align:start position:0% platform which can establish this trust so<00:01:59.460> the<00:01:59.580> three<00:02:00.030> main<00:02:00.060> element<00:02:00.570> is 00:02:01.960 --> 00:02:01.970 align:start position:0% so the three main element is 00:02:01.970 --> 00:02:05.090 align:start position:0% so the three main element is how<00:02:02.970> do<00:02:03.030> we<00:02:03.210> recover<00:02:03.600> keys<00:02:04.050> what's<00:02:04.710> an<00:02:04.890> easy 00:02:05.090 --> 00:02:05.100 align:start position:0% how do we recover keys what's an easy 00:02:05.100 --> 00:02:07.430 align:start position:0% how do we recover keys what's an easy way<00:02:05.400> to<00:02:05.460> do<00:02:05.760> this<00:02:05.790> without<00:02:06.360> relying<00:02:06.900> on<00:02:07.140> a 00:02:07.430 --> 00:02:07.440 align:start position:0% way to do this without relying on a 00:02:07.440 --> 00:02:09.440 align:start position:0% way to do this without relying on a company<00:02:07.920> or<00:02:08.039> someone<00:02:08.310> else<00:02:08.429> to<00:02:08.519> do<00:02:08.700> this<00:02:08.819> and 00:02:09.440 --> 00:02:09.450 align:start position:0% company or someone else to do this and 00:02:09.450 --> 00:02:10.850 align:start position:0% company or someone else to do this and we<00:02:09.599> have<00:02:09.629> some<00:02:09.869> interesting<00:02:10.409> ideas<00:02:10.500> on<00:02:10.769> this 00:02:10.850 --> 00:02:10.860 align:start position:0% we have some interesting ideas on this 00:02:10.860 --> 00:02:13.160 align:start position:0% we have some interesting ideas on this we<00:02:11.519> need<00:02:11.700> a<00:02:11.730> new<00:02:11.909> persistent<00:02:12.239> identifier<00:02:12.930> so<00:02:13.140> I 00:02:13.160 --> 00:02:13.170 align:start position:0% we need a new persistent identifier so I 00:02:13.170 --> 00:02:14.509 align:start position:0% we need a new persistent identifier so I think<00:02:13.260> that's<00:02:13.500> something<00:02:13.590> at<00:02:14.220> the<00:02:14.400> moment 00:02:14.509 --> 00:02:14.519 align:start position:0% think that's something at the moment 00:02:14.519 --> 00:02:16.850 align:start position:0% think that's something at the moment people<00:02:14.700> to<00:02:14.879> use<00:02:15.000> public<00:02:15.870> keys<00:02:16.230> that's<00:02:16.620> kind<00:02:16.800> of 00:02:16.850 --> 00:02:16.860 align:start position:0% people to use public keys that's kind of 00:02:16.860 --> 00:02:18.140 align:start position:0% people to use public keys that's kind of your<00:02:17.069> identifier<00:02:17.580> and<00:02:17.760> that's<00:02:17.909> what<00:02:18.030> people 00:02:18.140 --> 00:02:18.150 align:start position:0% your identifier and that's what people 00:02:18.150 --> 00:02:20.869 align:start position:0% your identifier and that's what people use<00:02:18.360> but<00:02:18.870> what<00:02:18.989> happens<00:02:19.290> if<00:02:19.409> you<00:02:19.620> use<00:02:20.489> your<00:02:20.670> key 00:02:20.869 --> 00:02:20.879 align:start position:0% use but what happens if you use your key 00:02:20.879 --> 00:02:23.270 align:start position:0% use but what happens if you use your key or<00:02:21.120> you<00:02:21.330> it's<00:02:21.750> kids<00:02:22.140> gets<00:02:22.560> compromised<00:02:22.980> and 00:02:23.270 --> 00:02:23.280 align:start position:0% or you it's kids gets compromised and 00:02:23.280 --> 00:02:24.979 align:start position:0% or you it's kids gets compromised and then<00:02:23.730> you<00:02:23.849> start<00:02:24.090> from<00:02:24.180> scratch<00:02:24.359> so<00:02:24.719> I<00:02:24.780> think 00:02:24.979 --> 00:02:24.989 align:start position:0% then you start from scratch so I think 00:02:24.989 --> 00:02:28.360 align:start position:0% then you start from scratch so I think we<00:02:25.620> have<00:02:25.739> now<00:02:25.950> given<00:02:26.129> to<00:02:26.609> Piper<00:02:27.329> our<00:02:27.510> our<00:02:27.780> key 00:02:28.360 --> 00:02:28.370 align:start position:0% we have now given to Piper our our key 00:02:28.370 --> 00:02:30.460 align:start position:0% we have now given to Piper our our key and<00:02:28.489> let's<00:02:28.640> see<00:02:28.730> what<00:02:28.849> happens<00:02:29.180> if<00:02:29.360> things<00:02:29.780> get 00:02:30.460 --> 00:02:30.470 align:start position:0% and let's see what happens if things get 00:02:30.470 --> 00:02:32.110 align:start position:0% and let's see what happens if things get lost<00:02:30.650> so<00:02:31.310> I<00:02:31.340> think<00:02:31.430> it's<00:02:31.640> really<00:02:31.790> important 00:02:32.110 --> 00:02:32.120 align:start position:0% lost so I think it's really important 00:02:32.120 --> 00:02:34.210 align:start position:0% lost so I think it's really important that<00:02:32.150> we<00:02:32.360> find<00:02:32.510> a<00:02:32.660> way<00:02:32.690> and<00:02:33.019> I<00:02:33.769> think<00:02:33.860> we<00:02:34.069> found 00:02:34.210 --> 00:02:34.220 align:start position:0% that we find a way and I think we found 00:02:34.220 --> 00:02:36.160 align:start position:0% that we find a way and I think we found at<00:02:34.430> least<00:02:34.489> a<00:02:34.730> good<00:02:35.000> idea<00:02:35.239> how<00:02:35.450> we<00:02:35.510> can<00:02:35.720> tackle 00:02:36.160 --> 00:02:36.170 align:start position:0% at least a good idea how we can tackle 00:02:36.170 --> 00:02:37.800 align:start position:0% at least a good idea how we can tackle this<00:02:36.379> problem<00:02:36.590> and 00:02:37.800 --> 00:02:37.810 align:start position:0% this problem and 00:02:37.810 --> 00:02:41.619 align:start position:0% this problem and attestations<00:02:38.810> and<00:02:39.730> attributes<00:02:40.730> there's<00:02:41.599> a 00:02:41.619 --> 00:02:41.629 align:start position:0% attestations and attributes there's a 00:02:41.629 --> 00:02:43.210 align:start position:0% attestations and attributes there's a key<00:02:41.900> element<00:02:42.200> to<00:02:42.230> this<00:02:42.410> so<00:02:42.590> once<00:02:42.980> you<00:02:43.069> have<00:02:43.160> an 00:02:43.210 --> 00:02:43.220 align:start position:0% key element to this so once you have an 00:02:43.220 --> 00:02:46.119 align:start position:0% key element to this so once you have an identifier<00:02:43.700> can<00:02:44.030> now<00:02:44.620> claim<00:02:45.620> certain 00:02:46.119 --> 00:02:46.129 align:start position:0% identifier can now claim certain 00:02:46.129 --> 00:02:48.160 align:start position:0% identifier can now claim certain attributes<00:02:46.580> and<00:02:46.760> go<00:02:46.910> and<00:02:47.180> get<00:02:47.569> data<00:02:47.690> stations 00:02:48.160 --> 00:02:48.170 align:start position:0% attributes and go and get data stations 00:02:48.170 --> 00:02:51.220 align:start position:0% attributes and go and get data stations from<00:02:48.349> institutions<00:02:49.220> from<00:02:49.700> I<00:02:50.450> know<00:02:50.930> whether 00:02:51.220 --> 00:02:51.230 align:start position:0% from institutions from I know whether 00:02:51.230 --> 00:02:52.660 align:start position:0% from institutions from I know whether it's<00:02:51.349> a<00:02:51.440> bank<00:02:51.620> whether<00:02:51.799> your<00:02:51.950> employer<00:02:52.340> your 00:02:52.660 --> 00:02:52.670 align:start position:0% it's a bank whether your employer your 00:02:52.670 --> 00:02:54.640 align:start position:0% it's a bank whether your employer your landlord<00:02:53.120> whatever<00:02:53.390> this<00:02:53.510> and<00:02:53.720> over<00:02:54.260> time<00:02:54.440> you 00:02:54.640 --> 00:02:54.650 align:start position:0% landlord whatever this and over time you 00:02:54.650 --> 00:02:56.710 align:start position:0% landlord whatever this and over time you build<00:02:54.799> and<00:02:55.640> connect<00:02:56.060> it<00:02:56.150> to<00:02:56.180> your<00:02:56.299> identity 00:02:56.710 --> 00:02:56.720 align:start position:0% build and connect it to your identity 00:02:56.720 --> 00:02:59.229 align:start position:0% build and connect it to your identity more<00:02:57.019> and<00:02:57.110> more<00:02:57.489> elements<00:02:58.489> which<00:02:58.970> you<00:02:59.090> can 00:02:59.229 --> 00:02:59.239 align:start position:0% more and more elements which you can 00:02:59.239 --> 00:03:01.960 align:start position:0% more and more elements which you can then<00:02:59.420> share<00:02:59.660> selectively<00:03:00.549> to<00:03:01.549> relevant 00:03:01.960 --> 00:03:01.970 align:start position:0% then share selectively to relevant 00:03:01.970 --> 00:03:04.240 align:start position:0% then share selectively to relevant parties<00:03:02.299> and<00:03:02.480> you<00:03:02.540> build<00:03:02.720> up<00:03:02.810> a<00:03:02.950> like<00:03:03.950> really 00:03:04.240 --> 00:03:04.250 align:start position:0% parties and you build up a like really 00:03:04.250 --> 00:03:05.680 align:start position:0% parties and you build up a like really strong<00:03:04.549> reputation<00:03:04.880> and<00:03:05.299> therefore<00:03:05.630> the 00:03:05.680 --> 00:03:05.690 align:start position:0% strong reputation and therefore the 00:03:05.690 --> 00:03:07.420 align:start position:0% strong reputation and therefore the trust<00:03:05.930> you<00:03:06.110> need<00:03:06.290> to<00:03:06.769> interact<00:03:07.069> with<00:03:07.280> digital 00:03:07.420 --> 00:03:07.430 align:start position:0% trust you need to interact with digital 00:03:07.430 --> 00:03:09.280 align:start position:0% trust you need to interact with digital services<00:03:07.970> and<00:03:08.180> Christian<00:03:08.900> will<00:03:08.989> I'll<00:03:09.110> tell 00:03:09.280 --> 00:03:09.290 align:start position:0% services and Christian will I'll tell 00:03:09.290 --> 00:03:11.640 align:start position:0% services and Christian will I'll tell you<00:03:09.440> how<00:03:09.799> we<00:03:09.860> solved<00:03:10.849> it 00:03:11.640 --> 00:03:11.650 align:start position:0% you how we solved it 00:03:11.650 --> 00:03:15.330 align:start position:0% you how we solved it exactly<00:03:12.650> so<00:03:12.950> the<00:03:13.940> way<00:03:14.090> we<00:03:14.269> deal<00:03:14.510> with 00:03:15.330 --> 00:03:15.340 align:start position:0% exactly so the way we deal with 00:03:15.340 --> 00:03:18.520 align:start position:0% exactly so the way we deal with key<00:03:16.340> management<00:03:16.849> first<00:03:17.060> is<00:03:17.360> that<00:03:17.660> you<00:03:18.260> know<00:03:18.349> in 00:03:18.520 --> 00:03:18.530 align:start position:0% key management first is that you know in 00:03:18.530 --> 00:03:20.920 align:start position:0% key management first is that you know in order<00:03:18.650> to<00:03:18.829> interact<00:03:19.730> with<00:03:19.849> aetherium<00:03:20.360> you 00:03:20.920 --> 00:03:20.930 align:start position:0% order to interact with aetherium you 00:03:20.930 --> 00:03:23.949 align:start position:0% order to interact with aetherium you need<00:03:21.110> to<00:03:21.349> have<00:03:21.769> a<00:03:22.150> system<00:03:23.150> for<00:03:23.180> managing<00:03:23.450> keys 00:03:23.949 --> 00:03:23.959 align:start position:0% need to have a system for managing keys 00:03:23.959 --> 00:03:25.199 align:start position:0% need to have a system for managing keys so 00:03:25.199 --> 00:03:25.209 align:start position:0% so 00:03:25.209 --> 00:03:27.910 align:start position:0% so normally<00:03:26.209> what<00:03:26.390> this<00:03:26.569> has<00:03:26.720> been<00:03:26.900> is<00:03:27.110> you<00:03:27.709> have 00:03:27.910 --> 00:03:27.920 align:start position:0% normally what this has been is you have 00:03:27.920 --> 00:03:30.940 align:start position:0% normally what this has been is you have a<00:03:27.950> key<00:03:28.519> maybe<00:03:28.930> encrypted<00:03:29.930> in<00:03:30.079> a<00:03:30.140> file<00:03:30.410> and<00:03:30.829> then 00:03:30.940 --> 00:03:30.950 align:start position:0% a key maybe encrypted in a file and then 00:03:30.950 --> 00:03:32.440 align:start position:0% a key maybe encrypted in a file and then you<00:03:31.129> need<00:03:31.280> to<00:03:31.430> make<00:03:31.760> sure<00:03:31.790> you<00:03:32.090> don't<00:03:32.299> lose 00:03:32.440 --> 00:03:32.450 align:start position:0% you need to make sure you don't lose 00:03:32.450 --> 00:03:35.280 align:start position:0% you need to make sure you don't lose that<00:03:32.630> file<00:03:32.930> or<00:03:33.170> maybe<00:03:33.440> you<00:03:33.620> have<00:03:33.829> a 00:03:35.280 --> 00:03:35.290 align:start position:0% that file or maybe you have a 00:03:35.290 --> 00:03:38.289 align:start position:0% that file or maybe you have a 12<00:03:36.290> word<00:03:36.530> seed<00:03:36.859> or<00:03:37.130> mnemonic<00:03:37.670> then<00:03:38.030> you<00:03:38.150> need 00:03:38.289 --> 00:03:38.299 align:start position:0% 12 word seed or mnemonic then you need 00:03:38.299 --> 00:03:39.729 align:start position:0% 12 word seed or mnemonic then you need to<00:03:38.420> write<00:03:38.600> it<00:03:38.720> down<00:03:38.750> but<00:03:39.260> you<00:03:39.350> need<00:03:39.470> to<00:03:39.590> write 00:03:39.729 --> 00:03:39.739 align:start position:0% to write it down but you need to write 00:03:39.739 --> 00:03:42.670 align:start position:0% to write it down but you need to write it<00:03:39.859> down<00:03:39.889> securely<00:03:40.569> etc<00:03:41.569> so<00:03:41.780> we're<00:03:42.200> taking<00:03:42.410> a 00:03:42.670 --> 00:03:42.680 align:start position:0% it down securely etc so we're taking a 00:03:42.680 --> 00:03:45.180 align:start position:0% it down securely etc so we're taking a slightly<00:03:42.950> different<00:03:43.190> view<00:03:43.609> so 00:03:45.180 --> 00:03:45.190 align:start position:0% slightly different view so 00:03:45.190 --> 00:03:49.390 align:start position:0% slightly different view so mobile<00:03:46.190> devices<00:03:46.730> today<00:03:47.200> especially<00:03:48.400> those 00:03:49.390 --> 00:03:49.400 align:start position:0% mobile devices today especially those 00:03:49.400 --> 00:03:52.690 align:start position:0% mobile devices today especially those with<00:03:49.870> secure<00:03:50.870> enclaves<00:03:51.440> can<00:03:52.130> provide<00:03:52.430> a<00:03:52.489> very 00:03:52.690 --> 00:03:52.700 align:start position:0% with secure enclaves can provide a very 00:03:52.700 --> 00:03:54.940 align:start position:0% with secure enclaves can provide a very safe<00:03:53.000> environment<00:03:53.329> for<00:03:53.599> a<00:03:54.139> private<00:03:54.500> key<00:03:54.680> so 00:03:54.940 --> 00:03:54.950 align:start position:0% safe environment for a private key so 00:03:54.950 --> 00:03:57.490 align:start position:0% safe environment for a private key so what<00:03:55.849> we're<00:03:55.970> doing<00:03:56.000> is<00:03:56.420> we<00:03:57.109> have<00:03:57.230> a<00:03:57.260> private 00:03:57.490 --> 00:03:57.500 align:start position:0% what we're doing is we have a private 00:03:57.500 --> 00:03:59.800 align:start position:0% what we're doing is we have a private key<00:03:57.829> it's<00:03:58.130> in<00:03:58.489> the<00:03:58.609> secure<00:03:58.910> Enclave<00:03:59.090> and<00:03:59.540> it's 00:03:59.800 --> 00:03:59.810 align:start position:0% key it's in the secure Enclave and it's 00:03:59.810 --> 00:04:01.800 align:start position:0% key it's in the secure Enclave and it's never<00:03:59.959> supposed<00:04:00.380> to<00:04:00.650> leave<00:04:00.829> the<00:04:00.980> device 00:04:01.800 --> 00:04:01.810 align:start position:0% never supposed to leave the device 00:04:01.810 --> 00:04:05.199 align:start position:0% never supposed to leave the device so<00:04:02.810> in<00:04:03.319> order<00:04:03.980> for<00:04:04.130> this<00:04:04.280> you<00:04:04.639> have<00:04:04.790> a<00:04:04.819> problem 00:04:05.199 --> 00:04:05.209 align:start position:0% so in order for this you have a problem 00:04:05.209 --> 00:04:07.210 align:start position:0% so in order for this you have a problem what<00:04:05.329> happens<00:04:05.690> if<00:04:05.810> you<00:04:05.900> lose<00:04:06.049> your<00:04:06.290> device<00:04:06.410> the 00:04:07.210 --> 00:04:07.220 align:start position:0% what happens if you lose your device the 00:04:07.220 --> 00:04:10.210 align:start position:0% what happens if you lose your device the idea<00:04:07.519> there<00:04:07.819> is<00:04:07.849> to<00:04:08.450> have<00:04:08.900> a<00:04:09.230> key<00:04:09.889> recovery 00:04:10.210 --> 00:04:10.220 align:start position:0% idea there is to have a key recovery 00:04:10.220 --> 00:04:13.569 align:start position:0% idea there is to have a key recovery system<00:04:10.819> where<00:04:11.239> you<00:04:11.329> can<00:04:11.540> tell<00:04:12.230> your<00:04:12.590> friends 00:04:13.569 --> 00:04:13.579 align:start position:0% system where you can tell your friends 00:04:13.579 --> 00:04:17.289 align:start position:0% system where you can tell your friends or<00:04:13.790> other<00:04:14.209> delegates<00:04:15.200> that<00:04:15.889> they<00:04:16.789> can<00:04:17.030> go<00:04:17.150> in 00:04:17.289 --> 00:04:17.299 align:start position:0% or other delegates that they can go in 00:04:17.299 --> 00:04:19.870 align:start position:0% or other delegates that they can go in and<00:04:17.599> actually<00:04:17.900> have<00:04:18.229> authority<00:04:18.349> to<00:04:18.880> restore 00:04:19.870 --> 00:04:19.880 align:start position:0% and actually have authority to restore 00:04:19.880 --> 00:04:23.770 align:start position:0% and actually have authority to restore your<00:04:20.389> identity<00:04:20.900> if<00:04:21.079> if<00:04:21.829> you<00:04:22.039> need<00:04:22.220> to<00:04:22.340> and<00:04:22.780> so 00:04:23.770 --> 00:04:23.780 align:start position:0% your identity if if you need to and so 00:04:23.780 --> 00:04:26.920 align:start position:0% your identity if if you need to and so in<00:04:23.900> order<00:04:24.050> to<00:04:24.200> do<00:04:24.500> this<00:04:24.740> we<00:04:25.430> use<00:04:25.729> a<00:04:26.030> what<00:04:26.840> we 00:04:26.920 --> 00:04:26.930 align:start position:0% in order to do this we use a what we 00:04:26.930 --> 00:04:29.350 align:start position:0% in order to do this we use a what we call<00:04:26.960> a<00:04:27.139> proxy<00:04:27.530> contract<00:04:28.010> as<00:04:28.250> your<00:04:28.849> core 00:04:29.350 --> 00:04:29.360 align:start position:0% call a proxy contract as your core 00:04:29.360 --> 00:04:32.800 align:start position:0% call a proxy contract as your core identity<00:04:30.039> construct<00:04:31.039> so<00:04:31.460> the<00:04:31.760> address<00:04:32.539> of<00:04:32.720> the 00:04:32.800 --> 00:04:32.810 align:start position:0% identity construct so the address of the 00:04:32.810 --> 00:04:36.659 align:start position:0% identity construct so the address of the proxy<00:04:33.530> contract<00:04:34.039> is<00:04:34.190> your<00:04:34.400> identifier 00:04:36.659 --> 00:04:36.669 align:start position:0% proxy contract is your identifier 00:04:36.669 --> 00:04:39.790 align:start position:0% proxy contract is your identifier whenever<00:04:37.669> you<00:04:38.360> want<00:04:38.599> to<00:04:38.719> interact<00:04:39.020> with<00:04:39.590> an 00:04:39.790 --> 00:04:39.800 align:start position:0% whenever you want to interact with an 00:04:39.800 --> 00:04:42.690 align:start position:0% whenever you want to interact with an app<00:04:40.420> Asian<00:04:40.690> contract<00:04:41.140> what<00:04:41.980> you<00:04:42.100> do<00:04:42.220> is<00:04:42.430> you 00:04:42.690 --> 00:04:42.700 align:start position:0% app Asian contract what you do is you 00:04:42.700 --> 00:04:44.300 align:start position:0% app Asian contract what you do is you send<00:04:42.940> a<00:04:43.000> transaction 00:04:44.300 --> 00:04:44.310 align:start position:0% send a transaction 00:04:44.310 --> 00:04:47.040 align:start position:0% send a transaction from<00:04:45.310> your<00:04:45.580> phone<00:04:45.820> you<00:04:46.090> sign<00:04:46.630> it<00:04:46.780> with<00:04:46.930> your 00:04:47.040 --> 00:04:47.050 align:start position:0% from your phone you sign it with your 00:04:47.050 --> 00:04:49.410 align:start position:0% from your phone you sign it with your key<00:04:47.260> but<00:04:47.920> you<00:04:48.040> send<00:04:48.280> it<00:04:48.370> through<00:04:48.520> a<00:04:48.610> controller 00:04:49.410 --> 00:04:49.420 align:start position:0% key but you send it through a controller 00:04:49.420 --> 00:04:52.200 align:start position:0% key but you send it through a controller contract<00:04:50.130> through<00:04:51.130> the<00:04:51.280> proxy<00:04:51.640> contract<00:04:52.060> and 00:04:52.200 --> 00:04:52.210 align:start position:0% contract through the proxy contract and 00:04:52.210 --> 00:04:55.230 align:start position:0% contract through the proxy contract and to<00:04:52.420> the<00:04:52.570> application<00:04:53.170> the<00:04:53.800> application<00:04:54.240> uses 00:04:55.230 --> 00:04:55.240 align:start position:0% to the application the application uses 00:04:55.240 --> 00:04:57.870 align:start position:0% to the application the application uses the<00:04:55.510> message<00:04:56.410> dots<00:04:56.800> under<00:04:57.160> construct<00:04:57.670> in 00:04:57.870 --> 00:04:57.880 align:start position:0% the message dots under construct in 00:04:57.880 --> 00:05:00.750 align:start position:0% the message dots under construct in solidity<00:04:58.780> and<00:04:59.110> it<00:04:59.740> sees<00:04:59.980> the<00:05:00.130> proxy<00:05:00.430> country 00:05:00.750 --> 00:05:00.760 align:start position:0% solidity and it sees the proxy country 00:05:00.760 --> 00:05:04.200 align:start position:0% solidity and it sees the proxy country the<00:05:00.880> address<00:05:01.120> as<00:05:01.330> the<00:05:01.780> as<00:05:02.320> the<00:05:02.680> sender<00:05:03.060> so<00:05:04.060> what 00:05:04.200 --> 00:05:04.210 align:start position:0% the address as the as the sender so what 00:05:04.210 --> 00:05:07.280 align:start position:0% the address as the as the sender so what this<00:05:04.300> means<00:05:04.360> is<00:05:04.750> that<00:05:04.810> we<00:05:05.590> can<00:05:05.620> extract<00:05:06.580> the 00:05:07.280 --> 00:05:07.290 align:start position:0% this means is that we can extract the 00:05:07.290 --> 00:05:11.580 align:start position:0% this means is that we can extract the the<00:05:08.290> access<00:05:08.680> control<00:05:09.040> logic<00:05:09.220> in<00:05:10.090> a<00:05:10.590> controller 00:05:11.580 --> 00:05:11.590 align:start position:0% the access control logic in a controller 00:05:11.590 --> 00:05:14.100 align:start position:0% the access control logic in a controller contract<00:05:12.130> that<00:05:13.090> is<00:05:13.240> accessed<00:05:13.630> by<00:05:13.690> the<00:05:13.810> device 00:05:14.100 --> 00:05:14.110 align:start position:0% contract that is accessed by the device 00:05:14.110 --> 00:05:17.400 align:start position:0% contract that is accessed by the device key<00:05:14.380> but<00:05:14.590> it<00:05:14.710> also<00:05:14.890> has<00:05:15.250> a<00:05:15.960> multi-sig<00:05:16.960> recovery 00:05:17.400 --> 00:05:17.410 align:start position:0% key but it also has a multi-sig recovery 00:05:17.410 --> 00:05:20.970 align:start position:0% key but it also has a multi-sig recovery feature<00:05:17.700> so<00:05:18.700> this<00:05:19.330> allows<00:05:19.690> you<00:05:19.900> to<00:05:19.930> if<00:05:20.470> you 00:05:20.970 --> 00:05:20.980 align:start position:0% feature so this allows you to if you 00:05:20.980 --> 00:05:23.460 align:start position:0% feature so this allows you to if you lose<00:05:21.130> your<00:05:21.310> phone<00:05:21.490> you<00:05:22.210> get<00:05:22.330> a<00:05:22.390> new<00:05:22.600> phone<00:05:22.630> you 00:05:23.460 --> 00:05:23.470 align:start position:0% lose your phone you get a new phone you 00:05:23.470 --> 00:05:26.190 align:start position:0% lose your phone you get a new phone you can<00:05:23.650> regenerate<00:05:24.280> a<00:05:24.550> key<00:05:24.820> but<00:05:25.570> your<00:05:25.780> recovery 00:05:26.190 --> 00:05:26.200 align:start position:0% can regenerate a key but your recovery 00:05:26.200 --> 00:05:29.430 align:start position:0% can regenerate a key but your recovery friends<00:05:26.500> can<00:05:26.680> can<00:05:27.070> recover<00:05:27.340> you<00:05:27.610> so<00:05:28.440> that's 00:05:29.430 --> 00:05:29.440 align:start position:0% friends can can recover you so that's 00:05:29.440 --> 00:05:30.780 align:start position:0% friends can can recover you so that's the<00:05:29.620> background<00:05:29.800> and<00:05:30.280> now<00:05:30.460> we're<00:05:30.610> going<00:05:30.730> to 00:05:30.780 --> 00:05:30.790 align:start position:0% the background and now we're going to 00:05:30.790 --> 00:05:36.980 align:start position:0% the background and now we're going to show<00:05:31.000> a<00:05:31.030> demo<00:05:31.690> if<00:05:32.650> it<00:05:32.800> works 00:05:36.980 --> 00:05:36.990 align:start position:0% 00:05:36.990 --> 00:05:40.380 align:start position:0% so<00:05:37.990> this<00:05:38.170> is<00:05:38.380> integration<00:05:38.920> with<00:05:39.310> the<00:05:39.550> gnosis 00:05:40.380 --> 00:05:40.390 align:start position:0% so this is integration with the gnosis 00:05:40.390 --> 00:05:42.740 align:start position:0% so this is integration with the gnosis platform<00:05:41.320> that<00:05:41.620> Martin<00:05:42.160> just<00:05:42.370> talked<00:05:42.550> about 00:05:42.740 --> 00:05:42.750 align:start position:0% platform that Martin just talked about 00:05:42.750 --> 00:05:46.310 align:start position:0% platform that Martin just talked about here<00:05:43.750> we<00:05:43.840> go 00:05:46.310 --> 00:05:46.320 align:start position:0% 00:05:46.320 --> 00:05:49.890 align:start position:0% so<00:05:47.320> basically<00:05:47.830> what<00:05:48.280> you<00:05:48.400> see<00:05:48.430> here<00:05:48.910> on<00:05:49.090> the<00:05:49.750> on 00:05:49.890 --> 00:05:49.900 align:start position:0% so basically what you see here on the on 00:05:49.900 --> 00:05:52.650 align:start position:0% so basically what you see here on the on the<00:05:49.990> phone<00:05:50.170> it's<00:05:51.040> very<00:05:51.280> simple<00:05:51.610> my<00:05:52.330> phone<00:05:52.540> up 00:05:52.650 --> 00:05:52.660 align:start position:0% the phone it's very simple my phone up 00:05:52.660 --> 00:05:56.430 align:start position:0% the phone it's very simple my phone up and<00:05:52.920> you<00:05:53.920> download<00:05:54.100> it<00:05:54.310> and<00:05:54.610> it<00:05:55.120> is<00:05:55.780> very<00:05:55.960> like 00:05:56.430 --> 00:05:56.440 align:start position:0% and you download it and it is very like 00:05:56.440 --> 00:05:57.900 align:start position:0% and you download it and it is very like it's<00:05:56.590> generates<00:05:57.010> automatically<00:05:57.460> the<00:05:57.580> private 00:05:57.900 --> 00:05:57.910 align:start position:0% it's generates automatically the private 00:05:57.910 --> 00:06:01.010 align:start position:0% it's generates automatically the private key<00:05:58.090> it<00:05:58.480> automatically<00:05:59.110> generates<00:05:59.650> the 00:06:01.010 --> 00:06:01.020 align:start position:0% key it automatically generates the 00:06:01.020 --> 00:06:03.150 align:start position:0% key it automatically generates the smart<00:06:02.020> contracts<00:06:02.320> Kristin<00:06:02.620> just<00:06:02.710> mentioned 00:06:03.150 --> 00:06:03.160 align:start position:0% smart contracts Kristin just mentioned 00:06:03.160 --> 00:06:05.310 align:start position:0% smart contracts Kristin just mentioned and<00:06:04.000> what<00:06:04.150> we're<00:06:04.300> going<00:06:04.480> to<00:06:04.510> show<00:06:04.780> you<00:06:04.840> now<00:06:05.110> is 00:06:05.310 --> 00:06:05.320 align:start position:0% and what we're going to show you now is 00:06:05.320 --> 00:06:06.900 align:start position:0% and what we're going to show you now is an<00:06:05.470> interaction<00:06:05.860> like<00:06:06.100> what's<00:06:06.250> the<00:06:06.400> usability 00:06:06.900 --> 00:06:06.910 align:start position:0% an interaction like what's the usability 00:06:06.910 --> 00:06:09.630 align:start position:0% an interaction like what's the usability for<00:06:07.210> for<00:06:07.870> you<00:06:07.960> if<00:06:08.170> you<00:06:08.320> if<00:06:08.560> you<00:06:08.680> use<00:06:08.890> this<00:06:09.100> so 00:06:09.630 --> 00:06:09.640 align:start position:0% for for you if you if you use this so 00:06:09.640 --> 00:06:11.180 align:start position:0% for for you if you if you use this so let<00:06:09.820> me<00:06:09.970> see<00:06:10.120> whether<00:06:10.360> it<00:06:10.450> works 00:06:11.180 --> 00:06:11.190 align:start position:0% let me see whether it works 00:06:11.190 --> 00:06:13.620 align:start position:0% let me see whether it works so<00:06:12.190> what<00:06:12.310> you<00:06:12.400> see<00:06:12.580> is<00:06:12.640> this<00:06:13.210> is<00:06:13.270> just<00:06:13.510> the 00:06:13.620 --> 00:06:13.630 align:start position:0% so what you see is this is just the 00:06:13.630 --> 00:06:16.650 align:start position:0% so what you see is this is just the profile<00:06:14.320> app<00:06:14.470> you<00:06:15.340> scan<00:06:15.850> the<00:06:15.970> QR<00:06:16.300> code<00:06:16.480> on<00:06:16.540> the 00:06:16.650 --> 00:06:16.660 align:start position:0% profile app you scan the QR code on the 00:06:16.660 --> 00:06:18.030 align:start position:0% profile app you scan the QR code on the app<00:06:16.780> so<00:06:16.900> there's<00:06:17.050> nothing<00:06:17.260> installed<00:06:17.800> on<00:06:17.890> this 00:06:18.030 --> 00:06:18.040 align:start position:0% app so there's nothing installed on this 00:06:18.040 --> 00:06:19.310 align:start position:0% app so there's nothing installed on this on<00:06:18.220> this 00:06:19.310 --> 00:06:19.320 align:start position:0% on this 00:06:19.320 --> 00:06:22.050 align:start position:0% on this browser<00:06:20.320> you<00:06:21.100> just<00:06:21.280> go<00:06:21.400> to<00:06:21.460> the<00:06:21.610> app<00:06:21.730> to<00:06:22.030> the 00:06:22.050 --> 00:06:22.060 align:start position:0% browser you just go to the app to the 00:06:22.060 --> 00:06:24.330 align:start position:0% browser you just go to the app to the gnosis<00:06:22.300> page<00:06:22.960> in<00:06:23.140> this<00:06:23.230> case<00:06:23.470> you<00:06:24.010> see<00:06:24.220> the 00:06:24.330 --> 00:06:24.340 align:start position:0% gnosis page in this case you see the 00:06:24.340 --> 00:06:26.610 align:start position:0% gnosis page in this case you see the identifier<00:06:24.790> it's<00:06:25.600> the<00:06:25.720> same<00:06:25.930> you<00:06:26.110> you<00:06:26.410> have 00:06:26.610 --> 00:06:26.620 align:start position:0% identifier it's the same you you have 00:06:26.620 --> 00:06:29.070 align:start position:0% identifier it's the same you you have here<00:06:27.040> you<00:06:27.520> should<00:06:27.940> see<00:06:27.970> your<00:06:28.300> balance<00:06:28.660> it's<00:06:28.990> a 00:06:29.070 --> 00:06:29.080 align:start position:0% here you should see your balance it's a 00:06:29.080 --> 00:06:31.500 align:start position:0% here you should see your balance it's a little<00:06:29.290> bit<00:06:29.380> small<00:06:29.710> maybe<00:06:30.060> which<00:06:31.060> is<00:06:31.180> the<00:06:31.300> same 00:06:31.500 --> 00:06:31.510 align:start position:0% little bit small maybe which is the same 00:06:31.510 --> 00:06:33.300 align:start position:0% little bit small maybe which is the same address<00:06:31.840> and<00:06:32.140> you<00:06:32.380> see<00:06:32.560> your<00:06:32.740> your<00:06:33.100> past 00:06:33.300 --> 00:06:33.310 align:start position:0% address and you see your your past 00:06:33.310 --> 00:06:35.550 align:start position:0% address and you see your your past transaction<00:06:33.790> so<00:06:33.940> the<00:06:34.390> login<00:06:34.720> process<00:06:34.930> is<00:06:35.320> very 00:06:35.550 --> 00:06:35.560 align:start position:0% transaction so the login process is very 00:06:35.560 --> 00:06:38.060 align:start position:0% transaction so the login process is very simple<00:06:35.890> we<00:06:36.070> just<00:06:36.280> hand<00:06:36.490> over<00:06:36.610> the<00:06:37.020> identifier 00:06:38.060 --> 00:06:38.070 align:start position:0% simple we just hand over the identifier 00:06:38.070 --> 00:06:40.380 align:start position:0% simple we just hand over the identifier well<00:06:39.070> now<00:06:39.190> we're<00:06:39.340> going<00:06:39.490> to<00:06:39.550> show<00:06:39.730> you<00:06:39.760> signing 00:06:40.380 --> 00:06:40.390 align:start position:0% well now we're going to show you signing 00:06:40.390 --> 00:06:43.680 align:start position:0% well now we're going to show you signing a<00:06:40.510> transaction<00:06:40.990> so<00:06:41.310> we<00:06:42.310> go<00:06:42.490> and<00:06:42.730> purchase<00:06:43.390> some 00:06:43.680 --> 00:06:43.690 align:start position:0% a transaction so we go and purchase some 00:06:43.690 --> 00:06:47.070 align:start position:0% a transaction so we go and purchase some chairs<00:06:43.960> and<00:06:44.550> doing<00:06:45.550> so<00:06:45.730> we<00:06:46.060> just<00:06:46.720> enter<00:06:46.990> the 00:06:47.070 --> 00:06:47.080 align:start position:0% chairs and doing so we just enter the 00:06:47.080 --> 00:06:48.780 align:start position:0% chairs and doing so we just enter the amount 00:06:48.780 --> 00:06:48.790 align:start position:0% amount 00:06:48.790 --> 00:06:51.420 align:start position:0% amount and<00:06:48.900> whatever<00:06:49.900> we<00:06:49.960> want<00:06:50.110> to<00:06:50.170> do<00:06:50.290> and<00:06:50.560> after<00:06:51.340> we 00:06:51.420 --> 00:06:51.430 align:start position:0% and whatever we want to do and after we 00:06:51.430 --> 00:06:53.370 align:start position:0% and whatever we want to do and after we confirm<00:06:51.880> this<00:06:52.150> it<00:06:52.420> will<00:06:52.600> generate<00:06:52.930> a<00:06:52.990> QR<00:06:53.230> code 00:06:53.370 --> 00:06:53.380 align:start position:0% confirm this it will generate a QR code 00:06:53.380 --> 00:06:55.620 align:start position:0% confirm this it will generate a QR code again<00:06:53.800> that's<00:06:54.430> not<00:06:54.760> let's<00:06:55.060> at<00:06:55.240> the<00:06:55.330> moment<00:06:55.540> as 00:06:55.620 --> 00:06:55.630 align:start position:0% again that's not let's at the moment as 00:06:55.630 --> 00:06:57.330 align:start position:0% again that's not let's at the moment as MEP<00:06:56.050> said<00:06:56.260> we<00:06:56.410> have<00:06:56.530> some<00:06:56.680> other<00:06:56.830> ideas<00:06:57.130> how<00:06:57.280> we 00:06:57.330 --> 00:06:57.340 align:start position:0% MEP said we have some other ideas how we 00:06:57.340 --> 00:06:59.760 align:start position:0% MEP said we have some other ideas how we can<00:06:57.580> make<00:06:57.730> this<00:06:58.030> more<00:06:58.240> user<00:06:58.780> friendly<00:06:58.870> but<00:06:59.650> we 00:06:59.760 --> 00:06:59.770 align:start position:0% can make this more user friendly but we 00:06:59.770 --> 00:07:01.550 align:start position:0% can make this more user friendly but we do<00:06:59.980> now<00:07:00.190> we<00:07:00.550> scan 00:07:01.550 --> 00:07:01.560 align:start position:0% do now we scan 00:07:01.560 --> 00:07:04.790 align:start position:0% do now we scan the<00:07:02.580> theorem<00:07:03.580> and 00:07:04.790 --> 00:07:04.800 align:start position:0% the theorem and 00:07:04.800 --> 00:07:07.620 align:start position:0% the theorem and call<00:07:05.800> and<00:07:06.160> you<00:07:06.490> will<00:07:06.640> see<00:07:06.850> now<00:07:06.880> automatic<00:07:07.540> we 00:07:07.620 --> 00:07:07.630 align:start position:0% call and you will see now automatic we 00:07:07.630 --> 00:07:10.740 align:start position:0% call and you will see now automatic we recognize<00:07:08.470> it's<00:07:08.950> a<00:07:09.010> buy<00:07:09.190> shares<00:07:09.570> activity<00:07:10.570> and 00:07:10.740 --> 00:07:10.750 align:start position:0% recognize it's a buy shares activity and 00:07:10.750 --> 00:07:12.930 align:start position:0% recognize it's a buy shares activity and now<00:07:11.140> to<00:07:11.200> use<00:07:11.740> it<00:07:11.920> and<00:07:12.040> sign<00:07:12.250> it<00:07:12.400> needs<00:07:12.700> to 00:07:12.930 --> 00:07:12.940 align:start position:0% now to use it and sign it needs to 00:07:12.940 --> 00:07:14.970 align:start position:0% now to use it and sign it needs to private<00:07:13.300> key<00:07:13.480> so<00:07:13.660> it<00:07:13.780> asks<00:07:13.960> for<00:07:14.170> the<00:07:14.380> for<00:07:14.920> the 00:07:14.970 --> 00:07:14.980 align:start position:0% private key so it asks for the for the 00:07:14.980 --> 00:07:16.980 align:start position:0% private key so it asks for the for the biometrics<00:07:15.580> and<00:07:15.790> what<00:07:16.210> it<00:07:16.300> does<00:07:16.420> now<00:07:16.600> it<00:07:16.720> sends 00:07:16.980 --> 00:07:16.990 align:start position:0% biometrics and what it does now it sends 00:07:16.990 --> 00:07:19.590 align:start position:0% biometrics and what it does now it sends it<00:07:17.080> to<00:07:17.200> in<00:07:17.290> Fuhrer<00:07:17.620> to<00:07:18.490> relay<00:07:19.000> the<00:07:19.180> message<00:07:19.210> and 00:07:19.590 --> 00:07:19.600 align:start position:0% it to in Fuhrer to relay the message and 00:07:19.600 --> 00:07:22.560 align:start position:0% it to in Fuhrer to relay the message and we<00:07:19.690> sent<00:07:19.870> back<00:07:20.080> this<00:07:20.850> transaction<00:07:21.850> hash<00:07:22.150> to 00:07:22.560 --> 00:07:22.570 align:start position:0% we sent back this transaction hash to 00:07:22.570 --> 00:07:24.090 align:start position:0% we sent back this transaction hash to the<00:07:22.720> application<00:07:23.320> so<00:07:23.680> it<00:07:23.770> can<00:07:23.920> immediately 00:07:24.090 --> 00:07:24.100 align:start position:0% the application so it can immediately 00:07:24.100 --> 00:07:25.590 align:start position:0% the application so it can immediately react<00:07:24.550> so<00:07:24.760> it's<00:07:24.880> not<00:07:25.030> like<00:07:25.210> waiting<00:07:25.570> for 00:07:25.590 --> 00:07:25.600 align:start position:0% react so it's not like waiting for 00:07:25.600 --> 00:07:28.350 align:start position:0% react so it's not like waiting for fifteen<00:07:25.990> seconds<00:07:26.350> you<00:07:26.830> see<00:07:27.070> the<00:07:27.670> hash<00:07:27.880> here<00:07:28.180> as 00:07:28.350 --> 00:07:28.360 align:start position:0% fifteen seconds you see the hash here as 00:07:28.360 --> 00:07:30.930 align:start position:0% fifteen seconds you see the hash here as that<00:07:28.660> hey<00:07:29.050> something<00:07:29.380> has<00:07:29.650> happened<00:07:29.740> but<00:07:30.520> it's 00:07:30.930 --> 00:07:30.940 align:start position:0% that hey something has happened but it's 00:07:30.940 --> 00:07:32.640 align:start position:0% that hey something has happened but it's still<00:07:31.120> processing<00:07:31.420> it<00:07:31.840> so<00:07:32.050> because<00:07:32.350> it<00:07:32.470> needs 00:07:32.640 --> 00:07:32.650 align:start position:0% still processing it so because it needs 00:07:32.650 --> 00:07:34.980 align:start position:0% still processing it so because it needs to<00:07:32.770> mine<00:07:32.980> and<00:07:33.280> for<00:07:34.000> the<00:07:34.090> next<00:07:34.270> block<00:07:34.450> and<00:07:34.690> once 00:07:34.980 --> 00:07:34.990 align:start position:0% to mine and for the next block and once 00:07:34.990 --> 00:07:36.930 align:start position:0% to mine and for the next block and once the<00:07:35.200> once<00:07:35.380> the<00:07:35.500> block<00:07:35.710> is<00:07:35.860> mind<00:07:36.070> which<00:07:36.730> hasn't 00:07:36.930 --> 00:07:36.940 align:start position:0% the once the block is mind which hasn't 00:07:36.940 --> 00:07:38.400 align:start position:0% the once the block is mind which hasn't been<00:07:37.090> watched<00:07:37.360> so<00:07:37.600> that's<00:07:37.750> kind<00:07:37.930> of<00:07:37.990> what<00:07:38.290> we 00:07:38.400 --> 00:07:38.410 align:start position:0% been watched so that's kind of what we 00:07:38.410 --> 00:07:40.770 align:start position:0% been watched so that's kind of what we think<00:07:38.530> is<00:07:38.710> in<00:07:38.830> like<00:07:39.190> much<00:07:39.610> nicer<00:07:40.060> interaction 00:07:40.770 --> 00:07:40.780 align:start position:0% think is in like much nicer interaction 00:07:40.780 --> 00:07:42.570 align:start position:0% think is in like much nicer interaction with<00:07:40.960> with<00:07:41.800> this<00:07:41.860> mark<00:07:42.100> on<00:07:42.220> tech<00:07:42.340> we<00:07:42.460> use 00:07:42.570 --> 00:07:42.580 align:start position:0% with with this mark on tech we use 00:07:42.580 --> 00:07:47.370 align:start position:0% with with this mark on tech we use already<00:07:43.080> the<00:07:44.080> four<00:07:44.290> byte<00:07:44.730> directory<00:07:45.730> and<00:07:46.350> ERC 00:07:47.370 --> 00:07:47.380 align:start position:0% already the four byte directory and ERC 00:07:47.380 --> 00:07:50.810 align:start position:0% already the four byte directory and ERC 67<00:07:48.340> so<00:07:48.700> this<00:07:49.030> Laura<00:07:49.240> already<00:07:49.960> happening 00:07:50.810 --> 00:07:50.820 align:start position:0% 67 so this Laura already happening 00:07:50.820 --> 00:07:53.430 align:start position:0% 67 so this Laura already happening so<00:07:51.820> don't<00:07:51.970> you<00:07:52.120> see<00:07:52.360> what<00:07:52.510> I<00:07:52.540> can<00:07:52.720> go<00:07:52.840> back<00:07:52.990> so 00:07:53.430 --> 00:07:53.440 align:start position:0% so don't you see what I can go back so 00:07:53.440 --> 00:07:58.480 align:start position:0% so don't you see what I can go back so thanks<00:07:53.890> to<00:07:53.920> Piper<00:07:54.370> Miriam 00:07:58.480 --> 00:07:58.490 align:start position:0% 00:07:58.490 --> 00:08:03.960 align:start position:0% [Applause] 00:08:03.960 --> 00:08:03.970 align:start position:0% [Applause] 00:08:03.970 --> 00:08:07.480 align:start position:0% [Applause] so<00:08:04.990> we<00:08:05.990> have<00:08:06.230> not<00:08:06.440> enough<00:08:06.650> time<00:08:06.830> today<00:08:07.040> so<00:08:07.190> we 00:08:07.480 --> 00:08:07.490 align:start position:0% so we have not enough time today so we 00:08:07.490 --> 00:08:09.430 align:start position:0% so we have not enough time today so we just<00:08:07.640> briefly<00:08:08.060> this<00:08:08.600> is<00:08:08.660> how<00:08:08.840> it<00:08:08.960> looks<00:08:09.110> if<00:08:09.350> you 00:08:09.430 --> 00:08:09.440 align:start position:0% just briefly this is how it looks if you 00:08:09.440 --> 00:08:10.930 align:start position:0% just briefly this is how it looks if you do<00:08:09.560> is<00:08:09.650> on<00:08:09.710> a<00:08:09.770> mobile<00:08:10.250> so<00:08:10.340> it<00:08:10.490> works<00:08:10.730> already 00:08:10.930 --> 00:08:10.940 align:start position:0% do is on a mobile so it works already 00:08:10.940 --> 00:08:13.750 align:start position:0% do is on a mobile so it works already today's<00:08:11.300> you<00:08:11.540> can<00:08:11.750> open<00:08:12.740> it<00:08:12.830> like<00:08:13.130> our<00:08:13.490> test 00:08:13.750 --> 00:08:13.760 align:start position:0% today's you can open it like our test 00:08:13.760 --> 00:08:16.300 align:start position:0% today's you can open it like our test app<00:08:14.000> in<00:08:14.210> the<00:08:14.630> moment<00:08:14.930> you<00:08:14.990> say<00:08:15.170> connect<00:08:16.040> it 00:08:16.300 --> 00:08:16.310 align:start position:0% app in the moment you say connect it 00:08:16.310 --> 00:08:18.730 align:start position:0% app in the moment you say connect it opens<00:08:16.730> up<00:08:16.880> instead<00:08:17.720> of<00:08:17.780> a<00:08:17.900> QR<00:08:18.200> code<00:08:18.410> it<00:08:18.560> just 00:08:18.730 --> 00:08:18.740 align:start position:0% opens up instead of a QR code it just 00:08:18.740 --> 00:08:20.770 align:start position:0% opens up instead of a QR code it just says<00:08:18.920> it's<00:08:19.250> jumps<00:08:19.580> to<00:08:19.700> the<00:08:19.790> app<00:08:19.910> you<00:08:20.210> say 00:08:20.770 --> 00:08:20.780 align:start position:0% says it's jumps to the app you say 00:08:20.780 --> 00:08:22.720 align:start position:0% says it's jumps to the app you say authorize<00:08:21.350> and<00:08:21.710> it<00:08:22.160> comes<00:08:22.310> back<00:08:22.490> to<00:08:22.550> the 00:08:22.720 --> 00:08:22.730 align:start position:0% authorize and it comes back to the 00:08:22.730 --> 00:08:24.430 align:start position:0% authorize and it comes back to the application<00:08:23.270> and<00:08:23.390> you<00:08:23.480> are<00:08:23.660> identified<00:08:24.410> with 00:08:24.430 --> 00:08:24.440 align:start position:0% application and you are identified with 00:08:24.440 --> 00:08:26.980 align:start position:0% application and you are identified with with<00:08:24.980> your<00:08:25.160> address<00:08:25.610> it's<00:08:26.450> pretty<00:08:26.750> simple 00:08:26.980 --> 00:08:26.990 align:start position:0% with your address it's pretty simple 00:08:26.990 --> 00:08:29.050 align:start position:0% with your address it's pretty simple same<00:08:27.380> works<00:08:27.590> with<00:08:27.800> signing<00:08:28.460> a<00:08:28.520> contract<00:08:28.760> so 00:08:29.050 --> 00:08:29.060 align:start position:0% same works with signing a contract so 00:08:29.060 --> 00:08:31.960 align:start position:0% same works with signing a contract so it's<00:08:29.210> kind<00:08:29.420> of<00:08:29.510> a<00:08:29.780> neat<00:08:30.400> our<00:08:31.400> social<00:08:31.790> recovery 00:08:31.960 --> 00:08:31.970 align:start position:0% it's kind of a neat our social recovery 00:08:31.970 --> 00:08:33.310 align:start position:0% it's kind of a neat our social recovery which<00:08:32.210> Christie<00:08:32.510> mentioned<00:08:32.780> so<00:08:32.870> the 00:08:33.310 --> 00:08:33.320 align:start position:0% which Christie mentioned so the 00:08:33.320 --> 00:08:34.930 align:start position:0% which Christie mentioned so the controller<00:08:33.800> and<00:08:34.100> what<00:08:34.220> we<00:08:34.310> have<00:08:34.430> built<00:08:34.610> for 00:08:34.930 --> 00:08:34.940 align:start position:0% controller and what we have built for 00:08:34.940 --> 00:08:37.330 align:start position:0% controller and what we have built for now<00:08:35.060> is<00:08:35.330> just<00:08:35.390> to<00:08:35.750> start<00:08:36.020> and<00:08:36.320> the<00:08:37.010> idea<00:08:37.250> is 00:08:37.330 --> 00:08:37.340 align:start position:0% now is just to start and the idea is 00:08:37.340 --> 00:08:39.190 align:start position:0% now is just to start and the idea is here<00:08:37.700> you<00:08:38.120> have<00:08:38.210> a<00:08:38.270> contact<00:08:38.600> list<00:08:38.810> of<00:08:39.080> your 00:08:39.190 --> 00:08:39.200 align:start position:0% here you have a contact list of your 00:08:39.200 --> 00:08:40.690 align:start position:0% here you have a contact list of your friends<00:08:39.320> and<00:08:39.740> you<00:08:39.860> just<00:08:40.040> pick<00:08:40.190> in<00:08:40.340> this<00:08:40.490> case 00:08:40.690 --> 00:08:40.700 align:start position:0% friends and you just pick in this case 00:08:40.700 --> 00:08:43.030 align:start position:0% friends and you just pick in this case three<00:08:41.330> individuals<00:08:41.960> you<00:08:42.410> say<00:08:42.590> this<00:08:42.860> is<00:08:43.010> my 00:08:43.030 --> 00:08:43.040 align:start position:0% three individuals you say this is my 00:08:43.040 --> 00:08:45.490 align:start position:0% three individuals you say this is my recovery<00:08:43.430> key<00:08:43.760> it<00:08:44.000> will<00:08:44.390> set<00:08:44.600> up<00:08:44.810> basically 00:08:45.490 --> 00:08:45.500 align:start position:0% recovery key it will set up basically 00:08:45.500 --> 00:08:47.530 align:start position:0% recovery key it will set up basically like<00:08:45.920> a<00:08:45.950> multi-sig<00:08:46.550> but<00:08:46.790> the<00:08:47.030> user<00:08:47.270> doesn't 00:08:47.530 --> 00:08:47.540 align:start position:0% like a multi-sig but the user doesn't 00:08:47.540 --> 00:08:49.540 align:start position:0% like a multi-sig but the user doesn't even<00:08:47.660> know<00:08:47.840> that<00:08:47.870> he<00:08:48.320> that<00:08:48.500> is<00:08:48.650> involved<00:08:49.130> we 00:08:49.540 --> 00:08:49.550 align:start position:0% even know that he that is involved we 00:08:49.550 --> 00:08:51.520 align:start position:0% even know that he that is involved we keep<00:08:49.730> it<00:08:49.820> really<00:08:50.030> really<00:08:50.180> simple<00:08:50.300> the<00:08:51.260> flow 00:08:51.520 --> 00:08:51.530 align:start position:0% keep it really really simple the flow 00:08:51.530 --> 00:08:53.470 align:start position:0% keep it really really simple the flow how<00:08:51.710> it<00:08:51.800> looks<00:08:52.010> like<00:08:52.100> and<00:08:52.280> I<00:08:52.370> need<00:08:52.880> to<00:08:53.000> jump 00:08:53.470 --> 00:08:53.480 align:start position:0% how it looks like and I need to jump 00:08:53.480 --> 00:08:54.940 align:start position:0% how it looks like and I need to jump down<00:08:53.660> a<00:08:53.690> little<00:08:53.780> bit<00:08:53.930> faster<00:08:54.260> you<00:08:54.710> click 00:08:54.940 --> 00:08:54.950 align:start position:0% down a little bit faster you click 00:08:54.950 --> 00:08:56.980 align:start position:0% down a little bit faster you click instead<00:08:55.220> of<00:08:55.340> creating<00:08:55.670> a<00:08:55.790> new<00:08:55.820> you<00:08:56.600> port<00:08:56.870> at 00:08:56.980 --> 00:08:56.990 align:start position:0% instead of creating a new you port at 00:08:56.990 --> 00:08:59.620 align:start position:0% instead of creating a new you port at entity<00:08:57.290> you<00:08:57.440> say<00:08:57.620> recover<00:08:57.980> you<00:08:58.670> will<00:08:58.820> generate 00:08:59.620 --> 00:08:59.630 align:start position:0% entity you say recover you will generate 00:08:59.630 --> 00:09:01.720 align:start position:0% entity you say recover you will generate a<00:08:59.690> new<00:08:59.930> key<00:08:59.960> it<00:09:00.470> would<00:09:00.680> show<00:09:00.920> this<00:09:01.160> this<00:09:01.460> is<00:09:01.580> now 00:09:01.720 --> 00:09:01.730 align:start position:0% a new key it would show this this is now 00:09:01.730 --> 00:09:05.140 align:start position:0% a new key it would show this this is now your<00:09:01.970> new<00:09:02.000> one<00:09:02.510> it<00:09:02.780> will<00:09:03.350> use<00:09:04.280> this<00:09:04.520> connecting 00:09:05.140 --> 00:09:05.150 align:start position:0% your new one it will use this connecting 00:09:05.150 --> 00:09:07.210 align:start position:0% your new one it will use this connecting to<00:09:05.360> other<00:09:05.510> to<00:09:06.440> your<00:09:06.530> friends<00:09:06.860> they<00:09:06.950> need<00:09:07.070> to 00:09:07.210 --> 00:09:07.220 align:start position:0% to other to your friends they need to 00:09:07.220 --> 00:09:09.040 align:start position:0% to other to your friends they need to scan<00:09:07.460> this<00:09:07.610> and<00:09:07.790> say<00:09:07.940> oh<00:09:07.970> this<00:09:08.300> is<00:09:08.360> this<00:09:08.600> person 00:09:09.040 --> 00:09:09.050 align:start position:0% scan this and say oh this is this person 00:09:09.050 --> 00:09:10.660 align:start position:0% scan this and say oh this is this person they<00:09:09.710> send<00:09:10.010> a<00:09:10.070> transaction<00:09:10.370> to<00:09:10.640> the 00:09:10.660 --> 00:09:10.670 align:start position:0% they send a transaction to the 00:09:10.670 --> 00:09:12.700 align:start position:0% they send a transaction to the controller<00:09:11.120> to<00:09:11.570> enable<00:09:11.960> and<00:09:12.050> I'll<00:09:12.170> unlock<00:09:12.500> you 00:09:12.700 --> 00:09:12.710 align:start position:0% controller to enable and I'll unlock you 00:09:12.710 --> 00:09:14.800 align:start position:0% controller to enable and I'll unlock you and<00:09:12.920> reconnect<00:09:13.670> you<00:09:13.820> back<00:09:14.030> to<00:09:14.210> the<00:09:14.330> identity<00:09:14.660> F 00:09:14.800 --> 00:09:14.810 align:start position:0% and reconnect you back to the identity F 00:09:14.810 --> 00:09:16.960 align:start position:0% and reconnect you back to the identity F perform<00:09:15.200> that's<00:09:16.040> the<00:09:16.160> position<00:09:16.310> identify 00:09:16.960 --> 00:09:16.970 align:start position:0% perform that's the position identify 00:09:16.970 --> 00:09:23.010 align:start position:0% perform that's the position identify which<00:09:17.150> we<00:09:17.270> I<00:09:17.300> think<00:09:17.420> is<00:09:17.570> really<00:09:17.720> important 00:09:23.010 --> 00:09:23.020 align:start position:0% 00:09:23.020 --> 00:09:26.100 align:start position:0% I<00:09:23.050> think<00:09:24.010> we<00:09:24.130> need<00:09:24.310> to<00:09:24.490> skip<00:09:24.760> out<00:09:24.880> okay<00:09:25.480> so<00:09:25.690> just 00:09:26.100 --> 00:09:26.110 align:start position:0% I think we need to skip out okay so just 00:09:26.110 --> 00:09:28.620 align:start position:0% I think we need to skip out okay so just briefly<00:09:26.350> and<00:09:26.709> running<00:09:27.670> out<00:09:27.730> of<00:09:27.760> time<00:09:27.850> so<00:09:28.029> we 00:09:28.620 --> 00:09:28.630 align:start position:0% briefly and running out of time so we 00:09:28.630 --> 00:09:30.240 align:start position:0% briefly and running out of time so we have<00:09:28.750> a<00:09:28.779> lot<00:09:28.990> of<00:09:29.020> Martius<00:09:29.560> like<00:09:29.770> how<00:09:29.920> we<00:09:29.980> can 00:09:30.240 --> 00:09:30.250 align:start position:0% have a lot of Martius like how we can 00:09:30.250 --> 00:09:32.070 align:start position:0% have a lot of Martius like how we can use<00:09:30.490> different<00:09:30.760> keys<00:09:31.089> of<00:09:31.270> different<00:09:31.630> levels 00:09:32.070 --> 00:09:32.080 align:start position:0% use different keys of different levels 00:09:32.080 --> 00:09:34.019 align:start position:0% use different keys of different levels to<00:09:32.260> indicate<00:09:32.950> Hardware<00:09:33.399> wallets<00:09:33.700> to<00:09:33.910> make 00:09:34.019 --> 00:09:34.029 align:start position:0% to indicate Hardware wallets to make 00:09:34.029 --> 00:09:35.720 align:start position:0% to indicate Hardware wallets to make this<00:09:34.149> much<00:09:34.360> work<00:09:34.600> I<00:09:34.750> think<00:09:34.899> we<00:09:35.020> have<00:09:35.110> a<00:09:35.170> robust 00:09:35.720 --> 00:09:35.730 align:start position:0% this much work I think we have a robust 00:09:35.730 --> 00:09:37.860 align:start position:0% this much work I think we have a robust foundation<00:09:36.730> but<00:09:37.240> there's<00:09:37.390> a<00:09:37.450> lot<00:09:37.570> of<00:09:37.690> things 00:09:37.860 --> 00:09:37.870 align:start position:0% foundation but there's a lot of things 00:09:37.870 --> 00:09:40.170 align:start position:0% foundation but there's a lot of things we<00:09:38.020> want<00:09:38.050> to<00:09:38.350> target<00:09:38.709> come<00:09:39.399> find<00:09:39.640> us<00:09:39.700> later<00:09:39.940> we 00:09:40.170 --> 00:09:40.180 align:start position:0% we want to target come find us later we 00:09:40.180 --> 00:09:41.389 align:start position:0% we want to target come find us later we can<00:09:40.300> talk<00:09:40.360> about<00:09:40.660> some<00:09:40.959> of<00:09:40.990> the<00:09:41.140> vision 00:09:41.389 --> 00:09:41.399 align:start position:0% can talk about some of the vision 00:09:41.399 --> 00:09:43.889 align:start position:0% can talk about some of the vision elements<00:09:42.399> a<00:09:42.550> Christian<00:09:43.180> needs<00:09:43.270> to<00:09:43.420> tell<00:09:43.720> you 00:09:43.889 --> 00:09:43.899 align:start position:0% elements a Christian needs to tell you 00:09:43.899 --> 00:09:46.110 align:start position:0% elements a Christian needs to tell you know<00:09:44.050> how<00:09:44.350> you<00:09:44.410> can<00:09:44.649> use<00:09:44.800> it<00:09:44.950> yeah<00:09:45.700> so<00:09:45.940> this<00:09:46.060> is 00:09:46.110 --> 00:09:46.120 align:start position:0% know how you can use it yeah so this is 00:09:46.120 --> 00:09:49.680 align:start position:0% know how you can use it yeah so this is the<00:09:46.350> as<00:09:47.350> a<00:09:47.550> developer<00:09:48.550> how<00:09:48.910> do<00:09:48.970> you<00:09:49.209> integrate 00:09:49.680 --> 00:09:49.690 align:start position:0% the as a developer how do you integrate 00:09:49.690 --> 00:09:51.540 align:start position:0% the as a developer how do you integrate with<00:09:49.930> you<00:09:50.200> port<00:09:50.500> so<00:09:50.649> we<00:09:50.709> have<00:09:50.950> open<00:09:51.339> source 00:09:51.540 --> 00:09:51.550 align:start position:0% with you port so we have open source 00:09:51.550 --> 00:09:54.180 align:start position:0% with you port so we have open source libraries<00:09:52.060> they<00:09:52.510> you<00:09:53.260> write<00:09:53.470> your<00:09:53.649> app<00:09:53.800> using 00:09:54.180 --> 00:09:54.190 align:start position:0% libraries they you write your app using 00:09:54.190 --> 00:09:57.660 align:start position:0% libraries they you write your app using a<00:09:54.220> standard<00:09:54.640> web<00:09:54.670> 3<00:09:55.260> paradigm<00:09:56.260> as<00:09:56.670> fabian 00:09:57.660 --> 00:09:57.670 align:start position:0% a standard web 3 paradigm as fabian 00:09:57.670 --> 00:10:01.170 align:start position:0% a standard web 3 paradigm as fabian talked<00:09:58.180> about<00:09:58.420> we<00:09:59.020> have<00:09:59.320> a<00:09:59.620> you<00:10:00.459> port<00:10:00.760> web<00:10:00.940> 3 00:10:01.170 --> 00:10:01.180 align:start position:0% talked about we have a you port web 3 00:10:01.180 --> 00:10:04.290 align:start position:0% talked about we have a you port web 3 provider<00:10:01.540> that<00:10:02.110> you<00:10:02.260> can<00:10:02.380> just<00:10:02.560> drop<00:10:03.160> in<00:10:03.430> the 00:10:04.290 --> 00:10:04.300 align:start position:0% provider that you can just drop in the 00:10:04.300 --> 00:10:06.510 align:start position:0% provider that you can just drop in the when<00:10:05.170> you<00:10:05.200> do<00:10:05.440> the<00:10:05.589> get<00:10:05.709> accounts<00:10:06.220> it<00:10:06.370> will 00:10:06.510 --> 00:10:06.520 align:start position:0% when you do the get accounts it will 00:10:06.520 --> 00:10:09.540 align:start position:0% when you do the get accounts it will trigger<00:10:06.790> the<00:10:07.120> you<00:10:07.600> port<00:10:07.870> connect<00:10:08.200> feature<00:10:08.890> the 00:10:09.540 --> 00:10:09.550 align:start position:0% trigger the you port connect feature the 00:10:09.550 --> 00:10:12.540 align:start position:0% trigger the you port connect feature the scanning<00:10:10.300> a<00:10:10.480> QR<00:10:10.510> code<00:10:10.779> the<00:10:11.740> same<00:10:12.190> transaction 00:10:12.540 --> 00:10:12.550 align:start position:0% scanning a QR code the same transaction 00:10:12.550 --> 00:10:16.680 align:start position:0% scanning a QR code the same transaction or<00:10:13.000> doing<00:10:13.360> a<00:10:13.540> contract<00:10:14.320> call<00:10:14.620> will<00:10:15.690> will 00:10:16.680 --> 00:10:16.690 align:start position:0% or doing a contract call will will 00:10:16.690 --> 00:10:18.960 align:start position:0% or doing a contract call will will trigger<00:10:16.930> the<00:10:17.230> transaction<00:10:18.010> signing<00:10:18.339> flow<00:10:18.520> it 00:10:18.960 --> 00:10:18.970 align:start position:0% trigger the transaction signing flow it 00:10:18.970 --> 00:10:21.870 align:start position:0% trigger the transaction signing flow it will<00:10:19.810> by<00:10:20.740> default<00:10:20.800> it<00:10:21.279> will<00:10:21.339> take<00:10:21.550> care<00:10:21.730> of 00:10:21.870 --> 00:10:21.880 align:start position:0% will by default it will take care of 00:10:21.880 --> 00:10:23.579 align:start position:0% will by default it will take care of generating<00:10:22.330> all<00:10:22.450> the<00:10:22.570> QR<00:10:22.870> codes<00:10:23.110> and<00:10:23.380> stuff 00:10:23.579 --> 00:10:23.589 align:start position:0% generating all the QR codes and stuff 00:10:23.589 --> 00:10:26.490 align:start position:0% generating all the QR codes and stuff like<00:10:23.709> that<00:10:23.920> but<00:10:24.459> you<00:10:24.670> can<00:10:24.850> also<00:10:25.000> customize<00:10:25.990> it 00:10:26.490 --> 00:10:26.500 align:start position:0% like that but you can also customize it 00:10:26.500 --> 00:10:31.160 align:start position:0% like that but you can also customize it if<00:10:26.680> you<00:10:26.830> want<00:10:27.070> more<00:10:27.520> specific<00:10:28.120> integration<00:10:29.100> so 00:10:31.160 --> 00:10:31.170 align:start position:0% if you want more specific integration so 00:10:31.170 --> 00:10:34.949 align:start position:0% if you want more specific integration so thanks<00:10:32.170> you<00:10:32.350> can<00:10:32.649> find<00:10:33.160> our<00:10:33.630> libraries<00:10:34.630> open 00:10:34.949 --> 00:10:34.959 align:start position:0% thanks you can find our libraries open 00:10:34.959 --> 00:10:38.100 align:start position:0% thanks you can find our libraries open source<00:10:35.320> libraries<00:10:35.770> on<00:10:36.089> github<00:10:37.089> we<00:10:37.959> have<00:10:38.079> a 00:10:38.100 --> 00:10:38.110 align:start position:0% source libraries on github we have a 00:10:38.110 --> 00:10:41.430 align:start position:0% source libraries on github we have a wave<00:10:38.290> white<00:10:38.920> paper<00:10:39.190> on<00:10:39.550> our<00:10:40.180> website<00:10:41.050> you<00:10:41.260> pour 00:10:41.430 --> 00:10:41.440 align:start position:0% wave white paper on our website you pour 00:10:41.440 --> 00:10:42.889 align:start position:0% wave white paper on our website you pour toute<00:10:41.589> me<00:10:41.770> and 00:10:42.889 --> 00:10:42.899 align:start position:0% toute me and 00:10:42.899 --> 00:10:47.430 align:start position:0% toute me and if<00:10:43.899> you<00:10:44.380> want<00:10:44.410> to<00:10:44.950> have<00:10:45.730> a<00:10:45.760> taste<00:10:46.029> of<00:10:46.270> the<00:10:46.570> app 00:10:47.430 --> 00:10:47.440 align:start position:0% if you want to have a taste of the app 00:10:47.440 --> 00:10:50.519 align:start position:0% if you want to have a taste of the app you<00:10:47.800> can<00:10:48.160> go<00:10:48.339> to<00:10:48.399> you<00:10:48.880> port<00:10:49.120> open<00:10:49.420> a<00:10:49.450> slash<00:10:49.839> def 00:10:50.519 --> 00:10:50.529 align:start position:0% you can go to you port open a slash def 00:10:50.529 --> 00:10:53.550 align:start position:0% you can go to you port open a slash def beta<00:10:50.860> for<00:10:51.310> the<00:10:51.399> iOS<00:10:51.790> app<00:10:52.029> or<00:10:52.300> Android<00:10:53.020> app<00:10:53.350> is 00:10:53.550 --> 00:10:53.560 align:start position:0% beta for the iOS app or Android app is 00:10:53.560 --> 00:10:55.920 align:start position:0% beta for the iOS app or Android app is coming<00:10:53.920> soon<00:10:54.190> you<00:10:54.459> can<00:10:54.670> email<00:10:54.970> us<00:10:55.300> at<00:10:55.510> Android 00:10:55.920 --> 00:10:55.930 align:start position:0% coming soon you can email us at Android 00:10:55.930 --> 00:10:58.139 align:start position:0% coming soon you can email us at Android at<00:10:56.200> you<00:10:56.470> port<00:10:56.740> of<00:10:56.829> me<00:10:56.980> to<00:10:57.399> hear<00:10:57.790> more<00:10:58.000> news 00:10:58.139 --> 00:10:58.149 align:start position:0% at you port of me to hear more news 00:10:58.149 --> 00:10:59.730 align:start position:0% at you port of me to hear more news about<00:10:58.329> that<00:10:58.450> great<00:10:58.839> thank<00:10:59.170> you<00:10:59.230> very<00:10:59.350> much 00:10:59.730 --> 00:10:59.740 align:start position:0% about that great thank you very much 00:10:59.740 --> 00:11:01.000 align:start position:0% about that great thank you very much Christian<00:11:00.250> and<00:11:00.430> Reuben 00:11:01.000 --> 00:11:01.010 align:start position:0% Christian and Reuben 00:11:01.010 --> 00:11:02.140 align:start position:0% Christian and Reuben [Applause] 00:11:02.140 --> 00:11:02.150 align:start position:0% [Applause] 00:11:02.150 --> 00:11:03.480 align:start position:0% [Applause] [Music] 00:11:03.480 --> 00:11:03.490 align:start position:0% [Music] 00:11:03.490 --> 00:11:07.270 align:start position:0% [Music] you 00:11:07.270 --> 00:11:07.280 align:start position:0% 00:11:07.280 --> 00:11:10.620 align:start position:0% [Music]