WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:14.110 align:start position:0% [Applause] 00:00:14.110 --> 00:00:14.120 align:start position:0% 00:00:14.120 --> 00:00:18.890 align:start position:0% thank<00:00:15.120> you<00:00:15.240> very<00:00:15.270> much<00:00:15.450> for<00:00:15.750> being<00:00:15.960> here<00:00:16.020> I<00:00:17.900> am 00:00:18.890 --> 00:00:18.900 align:start position:0% thank you very much for being here I am 00:00:18.900 --> 00:00:21.440 align:start position:0% thank you very much for being here I am product<00:00:19.140> manager<00:00:19.619> of<00:00:19.830> the<00:00:20.040> car<00:00:20.250> I'm<00:00:21.119> going<00:00:21.360> to 00:00:21.440 --> 00:00:21.450 align:start position:0% product manager of the car I'm going to 00:00:21.450 --> 00:00:24.080 align:start position:0% product manager of the car I'm going to give<00:00:21.660> a<00:00:21.689> quick<00:00:22.020> introduction<00:00:22.380> to<00:00:23.070> what<00:00:23.760> is<00:00:23.850> T 00:00:24.080 --> 00:00:24.090 align:start position:0% give a quick introduction to what is T 00:00:24.090 --> 00:00:26.929 align:start position:0% give a quick introduction to what is T card<00:00:24.330> and<00:00:24.689> then<00:00:25.259> on<00:00:25.560> Turin<00:00:25.860> Italy<00:00:26.099> which<00:00:26.730> are 00:00:26.929 --> 00:00:26.939 align:start position:0% card and then on Turin Italy which are 00:00:26.939 --> 00:00:28.819 align:start position:0% card and then on Turin Italy which are what<00:00:27.300> the<00:00:27.419> developers<00:00:27.990> 40<00:00:28.290> cars<00:00:28.529> are<00:00:28.650> going<00:00:28.740> to 00:00:28.819 --> 00:00:28.829 align:start position:0% what the developers 40 cars are going to 00:00:28.829 --> 00:00:32.810 align:start position:0% what the developers 40 cars are going to be<00:00:28.950> in<00:00:29.700> a<00:00:29.820> hands-on<00:00:30.180> approach<00:00:30.360> and<00:00:30.960> scope<00:00:31.820> this 00:00:32.810 --> 00:00:32.820 align:start position:0% be in a hands-on approach and scope this 00:00:32.820 --> 00:00:34.400 align:start position:0% be in a hands-on approach and scope this is<00:00:32.970> supposed<00:00:33.239> to<00:00:33.270> be<00:00:33.329> a<00:00:33.450> very<00:00:33.690> hands-on 00:00:34.400 --> 00:00:34.410 align:start position:0% is supposed to be a very hands-on 00:00:34.410 --> 00:00:37.300 align:start position:0% is supposed to be a very hands-on workshop<00:00:34.920> you<00:00:35.520> can<00:00:35.550> get<00:00:35.880> your<00:00:36.030> computer<00:00:36.270> ready 00:00:37.300 --> 00:00:37.310 align:start position:0% workshop you can get your computer ready 00:00:37.310 --> 00:00:40.040 align:start position:0% workshop you can get your computer ready we<00:00:38.310> have<00:00:38.430> key<00:00:38.579> cards<00:00:38.610> for<00:00:39.000> you<00:00:39.180> we<00:00:39.960> have 00:00:40.040 --> 00:00:40.050 align:start position:0% we have key cards for you we have 00:00:40.050 --> 00:00:44.960 align:start position:0% we have key cards for you we have Twitter's<00:00:40.500> what<00:00:41.130> you're<00:00:41.310> less<00:00:41.550> than<00:00:43.970> 40 00:00:44.960 --> 00:00:44.970 align:start position:0% Twitter's what you're less than 40 00:00:44.970 --> 00:00:53.950 align:start position:0% Twitter's what you're less than 40 meters<00:00:48.740> that's<00:00:49.740> not<00:00:49.920> enough<00:00:50.160> you<00:00:50.370> can<00:00:50.730> maybe 00:00:53.950 --> 00:00:53.960 align:start position:0% 00:00:53.960 --> 00:00:58.760 align:start position:0% so<00:00:56.390> quick<00:00:57.390> introduction<00:00:58.020> to<00:00:58.050> what<00:00:58.320> is<00:00:58.410> keep<00:00:58.620> on 00:00:58.760 --> 00:00:58.770 align:start position:0% so quick introduction to what is keep on 00:00:58.770 --> 00:01:01.340 align:start position:0% so quick introduction to what is keep on very<00:00:59.250> quickly<00:00:59.370> and<00:00:59.940> then<00:01:00.240> we<00:01:00.450> can<00:01:00.630> get<00:01:00.780> on<00:01:01.140> to 00:01:01.340 --> 00:01:01.350 align:start position:0% very quickly and then we can get on to 00:01:01.350 --> 00:01:10.300 align:start position:0% very quickly and then we can get on to the<00:01:01.530> hands<00:01:02.250> on<00:01:02.370> the<00:01:02.570> workshop<00:01:03.860> so<00:01:08.720> this<00:01:09.720> is 00:01:10.300 --> 00:01:10.310 align:start position:0% the hands on the workshop so this is 00:01:10.310 --> 00:01:14.990 align:start position:0% the hands on the workshop so this is very<00:01:11.310> steep<00:01:11.750> it's<00:01:12.860> 32<00:01:13.890> yeah<00:01:14.550> she<00:01:14.850> called 00:01:14.990 --> 00:01:15.000 align:start position:0% very steep it's 32 yeah she called 00:01:15.000 --> 00:01:17.120 align:start position:0% very steep it's 32 yeah she called attorney<00:01:15.360> stick<00:01:15.720> out<00:01:16.320> when<00:01:16.590> we<00:01:16.740> left<00:01:16.890> on<00:01:17.040> a 00:01:17.120 --> 00:01:17.130 align:start position:0% attorney stick out when we left on a 00:01:17.130 --> 00:01:18.260 align:start position:0% attorney stick out when we left on a small<00:01:17.400> car 00:01:18.260 --> 00:01:18.270 align:start position:0% small car 00:01:18.270 --> 00:01:20.710 align:start position:0% small car [Music] 00:01:20.710 --> 00:01:20.720 align:start position:0% [Music] 00:01:20.720 --> 00:01:23.330 align:start position:0% [Music] it's<00:01:21.720> open<00:01:21.990> source<00:01:22.200> and<00:01:22.530> it's<00:01:22.890> running<00:01:23.159> on 00:01:23.330 --> 00:01:23.340 align:start position:0% it's open source and it's running on 00:01:23.340 --> 00:01:26.899 align:start position:0% it's open source and it's running on shall<00:01:23.580> account<00:01:24.500> what<00:01:25.500> it's<00:01:25.620> not<00:01:25.830> it's<00:01:26.640> not<00:01:26.850> a 00:01:26.899 --> 00:01:26.909 align:start position:0% shall account what it's not it's not a 00:01:26.909 --> 00:01:32.270 align:start position:0% shall account what it's not it's not a simple<00:01:27.479> NFC<00:01:28.200> tag<00:01:29.510> that<00:01:30.510> you<00:01:31.020> that<00:01:31.860> you<00:01:32.070> would 00:01:32.270 --> 00:01:32.280 align:start position:0% simple NFC tag that you that you would 00:01:32.280 --> 00:01:37.700 align:start position:0% simple NFC tag that you that you would use<00:01:32.580> as<00:01:33.000> a<00:01:33.540> QR<00:01:34.140> code<00:01:34.170> or<00:01:34.740> the<00:01:35.010> name<00:01:35.040> 15<00:01:36.530> that<00:01:37.530> I 00:01:37.700 --> 00:01:37.710 align:start position:0% use as a QR code or the name 15 that I 00:01:37.710 --> 00:01:38.440 align:start position:0% use as a QR code or the name 15 that I need 00:01:38.440 --> 00:01:38.450 align:start position:0% need 00:01:38.450 --> 00:01:44.679 align:start position:0% need NFC<00:01:39.229> it's<00:01:39.680> actually<00:01:40.299> a<00:01:41.680> small<00:01:42.680> computer<00:01:43.689> key 00:01:44.679 --> 00:01:44.689 align:start position:0% NFC it's actually a small computer key 00:01:44.689 --> 00:01:47.109 align:start position:0% NFC it's actually a small computer key card<00:01:44.960> is<00:01:45.740> an<00:01:45.920> applet<00:01:46.280> that<00:01:46.430> runs<00:01:46.759> on<00:01:46.939> there 00:01:47.109 --> 00:01:47.119 align:start position:0% card is an applet that runs on there 00:01:47.119 --> 00:01:50.289 align:start position:0% card is an applet that runs on there it's<00:01:47.509> open<00:01:47.630> source<00:01:47.960> so<00:01:48.320> you<00:01:48.979> can<00:01:49.130> check<00:01:49.610> it<00:01:49.670> you 00:01:50.289 --> 00:01:50.299 align:start position:0% it's open source so you can check it you 00:01:50.299 --> 00:01:52.810 align:start position:0% it's open source so you can check it you can<00:01:50.330> edit<00:01:50.750> it<00:01:50.960> and<00:01:51.290> tweak<00:01:51.860> it<00:01:51.890> everywhere<00:01:52.700> you 00:01:52.810 --> 00:01:52.820 align:start position:0% can edit it and tweak it everywhere you 00:01:52.820 --> 00:01:56.200 align:start position:0% can edit it and tweak it everywhere you want<00:01:52.939> for<00:01:53.720> your<00:01:53.810> own<00:01:53.899> application<00:01:54.049> and<00:01:55.210> it 00:01:56.200 --> 00:01:56.210 align:start position:0% want for your own application and it 00:01:56.210 --> 00:01:58.420 align:start position:0% want for your own application and it runs<00:01:56.479> on<00:01:56.720> very<00:01:57.170> standard<00:01:57.619> web<00:01:57.979> hardware 00:01:58.420 --> 00:01:58.430 align:start position:0% runs on very standard web hardware 00:01:58.430 --> 00:02:00.609 align:start position:0% runs on very standard web hardware actually<00:01:59.000> all<00:01:59.180> of<00:01:59.210> you<00:01:59.450> here<00:01:59.780> you<00:01:59.960> have<00:02:00.470> to 00:02:00.609 --> 00:02:00.619 align:start position:0% actually all of you here you have to 00:02:00.619 --> 00:02:02.590 align:start position:0% actually all of you here you have to have<00:02:00.770> a<00:02:00.799> card<00:02:01.070> on<00:02:01.189> yourself<00:02:01.640> right<00:02:01.880> now<00:02:01.909> most 00:02:02.590 --> 00:02:02.600 align:start position:0% have a card on yourself right now most 00:02:02.600 --> 00:02:27.250 align:start position:0% have a card on yourself right now most probably<00:02:02.899> because<00:02:03.850> every<00:02:17.500> one<00:02:18.500> of<00:02:18.530> the<00:02:26.170> and<00:02:27.170> it 00:02:27.250 --> 00:02:27.260 align:start position:0% probably because every one of the and it 00:02:27.260 --> 00:02:28.600 align:start position:0% probably because every one of the and it has<00:02:27.410> a<00:02:27.440> very<00:02:27.620> high<00:02:27.830> level<00:02:27.890> of<00:02:28.190> physical 00:02:28.600 --> 00:02:28.610 align:start position:0% has a very high level of physical 00:02:28.610 --> 00:02:32.020 align:start position:0% has a very high level of physical security<00:02:28.940> any<00:02:29.510> be<00:02:30.230> very<00:02:30.590> expensive 00:02:32.020 --> 00:02:32.030 align:start position:0% security any be very expensive 00:02:32.030 --> 00:02:38.800 align:start position:0% security any be very expensive physically<00:02:32.870> to<00:02:33.080> get<00:02:33.260> private<00:02:34.250> keys<00:02:37.630> the<00:02:38.630> key 00:02:38.800 --> 00:02:38.810 align:start position:0% physically to get private keys the key 00:02:38.810 --> 00:02:39.610 align:start position:0% physically to get private keys the key card 00:02:39.610 --> 00:02:39.620 align:start position:0% card 00:02:39.620 --> 00:02:42.309 align:start position:0% card we<00:02:40.100> are<00:02:40.250> providing<00:02:40.819> here<00:02:41.420> and<00:02:41.690> the<00:02:41.900> one<00:02:42.080> we 00:02:42.309 --> 00:02:42.319 align:start position:0% we are providing here and the one we 00:02:42.319 --> 00:02:44.440 align:start position:0% we are providing here and the one we produce<00:02:42.530> the<00:02:42.859> status<00:02:43.280> that<00:02:43.519> we've<00:02:44.209> integrated 00:02:44.440 --> 00:02:44.450 align:start position:0% produce the status that we've integrated 00:02:44.450 --> 00:02:47.199 align:start position:0% produce the status that we've integrated with<00:02:44.780> instead<00:02:45.410> of<00:02:45.560> stairs<00:02:46.040> as<00:02:46.640> to<00:02:46.910> type<00:02:47.090> of 00:02:47.199 --> 00:02:47.209 align:start position:0% with instead of stairs as to type of 00:02:47.209 --> 00:02:49.890 align:start position:0% with instead of stairs as to type of interfaces<00:02:47.870> it<00:02:48.079> was<00:02:48.290> contactless<00:02:48.799> with<00:02:49.489> NFC 00:02:49.890 --> 00:02:49.900 align:start position:0% interfaces it was contactless with NFC 00:02:49.900 --> 00:02:52.900 align:start position:0% interfaces it was contactless with NFC so<00:02:50.900> that<00:02:51.049> you<00:02:51.200> can<00:02:51.410> integrate<00:02:51.739> with<00:02:52.250> either 00:02:52.900 --> 00:02:52.910 align:start position:0% so that you can integrate with either 00:02:52.910 --> 00:02:57.330 align:start position:0% so that you can integrate with either Android<00:02:53.359> or<00:02:53.540> iOS<00:02:53.959> mobile<00:02:54.620> applications<00:02:55.340> and 00:02:57.330 --> 00:02:57.340 align:start position:0% Android or iOS mobile applications and 00:02:57.340 --> 00:03:00.849 align:start position:0% Android or iOS mobile applications and it's<00:02:58.340> also<00:02:58.519> got<00:02:59.120> a<00:02:59.450> physical<00:02:59.930> interface<00:03:00.620> like 00:03:00.849 --> 00:03:00.859 align:start position:0% it's also got a physical interface like 00:03:00.859 --> 00:03:03.550 align:start position:0% it's also got a physical interface like that<00:03:01.040> meaning<00:03:02.000> you<00:03:02.209> can<00:03:02.420> meet<00:03:02.660> the<00:03:02.840> materials 00:03:03.550 --> 00:03:03.560 align:start position:0% that meaning you can meet the materials 00:03:03.560 --> 00:03:05.560 align:start position:0% that meaning you can meet the materials that<00:03:03.739> we've<00:03:03.980> distributed<00:03:04.250> connected<00:03:05.060> to 00:03:05.560 --> 00:03:05.570 align:start position:0% that we've distributed connected to 00:03:05.570 --> 00:03:10.420 align:start position:0% that we've distributed connected to desktop<00:03:06.260> application<00:03:08.109> so<00:03:09.109> that's<00:03:09.950> key<00:03:10.190> card 00:03:10.420 --> 00:03:10.430 align:start position:0% desktop application so that's key card 00:03:10.430 --> 00:03:21.190 align:start position:0% desktop application so that's key card what<00:03:10.760> can<00:03:10.940> you<00:03:11.060> build<00:03:11.480> with<00:03:11.989> key<00:03:12.170> card<00:03:20.079> it's<00:03:21.079> a 00:03:21.190 --> 00:03:21.200 align:start position:0% what can you build with key card it's a 00:03:21.200 --> 00:03:22.780 align:start position:0% what can you build with key card it's a hardware<00:03:21.470> wallet<00:03:21.769> so<00:03:22.220> you<00:03:22.250> can<00:03:22.400> either 00:03:22.780 --> 00:03:22.790 align:start position:0% hardware wallet so you can either 00:03:22.790 --> 00:03:26.080 align:start position:0% hardware wallet so you can either generate<00:03:23.060> a<00:03:23.359> secret<00:03:23.950> within<00:03:24.950> the<00:03:25.250> card<00:03:25.489> or<00:03:25.910> you 00:03:26.080 --> 00:03:26.090 align:start position:0% generate a secret within the card or you 00:03:26.090 --> 00:03:29.110 align:start position:0% generate a secret within the card or you can<00:03:26.269> import<00:03:26.720> a<00:03:27.049> secret<00:03:27.530> let's<00:03:28.430> say<00:03:28.609> the<00:03:28.760> secret 00:03:29.110 --> 00:03:29.120 align:start position:0% can import a secret let's say the secret 00:03:29.120 --> 00:03:30.030 align:start position:0% can import a secret let's say the secret is<00:03:29.239> a<00:03:29.329> sea 00:03:30.030 --> 00:03:30.040 align:start position:0% is a sea 00:03:30.040 --> 00:03:33.180 align:start position:0% is a sea then<00:03:30.910> you<00:03:31.420> can<00:03:31.660> make<00:03:31.870> any<00:03:32.050> derivation<00:03:32.500> for<00:03:33.010> any 00:03:33.180 --> 00:03:33.190 align:start position:0% then you can make any derivation for any 00:03:33.190 --> 00:03:36.060 align:start position:0% then you can make any derivation for any prostitute<00:03:34.000> on<00:03:34.660> DC<00:03:35.080> within<00:03:35.500> the<00:03:35.620> card<00:03:35.860> and 00:03:36.060 --> 00:03:36.070 align:start position:0% prostitute on DC within the card and 00:03:36.070 --> 00:03:38.580 align:start position:0% prostitute on DC within the card and then<00:03:36.250> the<00:03:36.370> card<00:03:36.600> he's<00:03:37.600> doing<00:03:37.930> the<00:03:38.080> trend<00:03:38.350> the 00:03:38.580 --> 00:03:38.590 align:start position:0% then the card he's doing the trend the 00:03:38.590 --> 00:03:41.100 align:start position:0% then the card he's doing the trend the second<00:03:39.130> signature<00:03:39.460> ECB<00:03:40.120> is<00:03:40.210> a<00:03:40.360> signature<00:03:40.690> of 00:03:41.100 --> 00:03:41.110 align:start position:0% second signature ECB is a signature of 00:03:41.110 --> 00:03:43.380 align:start position:0% second signature ECB is a signature of the<00:03:41.680> transaction<00:03:42.160> at<00:03:42.280> least<00:03:42.460> capacitor<00:03:43.180> part 00:03:43.380 --> 00:03:43.390 align:start position:0% the transaction at least capacitor part 00:03:43.390 --> 00:03:46.560 align:start position:0% the transaction at least capacitor part so<00:03:44.140> your<00:03:44.350> application<00:03:44.470> is<00:03:45.130> passing<00:03:45.580> once<00:03:46.420> it's 00:03:46.560 --> 00:03:46.570 align:start position:0% so your application is passing once it's 00:03:46.570 --> 00:03:48.810 align:start position:0% so your application is passing once it's set<00:03:46.750> up<00:03:46.780> and<00:03:47.140> the<00:03:47.530> secrets<00:03:47.860> are<00:03:47.980> here<00:03:48.220> they 00:03:48.810 --> 00:03:48.820 align:start position:0% set up and the secrets are here they 00:03:48.820 --> 00:03:52.500 align:start position:0% set up and the secrets are here they never<00:03:49.120> leave<00:03:49.360> the<00:03:49.510> card<00:03:49.720> and<00:03:51.510> your 00:03:52.500 --> 00:03:52.510 align:start position:0% never leave the card and your 00:03:52.510 --> 00:03:54.180 align:start position:0% never leave the card and your application<00:03:53.020> is<00:03:53.170> passing<00:03:53.560> the<00:03:53.680> transaction 00:03:54.180 --> 00:03:54.190 align:start position:0% application is passing the transaction 00:03:54.190 --> 00:03:59.340 align:start position:0% application is passing the transaction to<00:03:54.700> the<00:03:54.970> hash<00:03:55.150> of<00:03:55.270> the<00:03:55.390> transaction<00:03:55.900> and<00:03:58.350> and 00:03:59.340 --> 00:03:59.350 align:start position:0% to the hash of the transaction and and 00:03:59.350 --> 00:04:03.060 align:start position:0% to the hash of the transaction and and passing<00:04:01.380> that's<00:04:02.380> what<00:04:02.530> it<00:04:02.620> does 00:04:03.060 --> 00:04:03.070 align:start position:0% passing that's what it does 00:04:03.070 --> 00:04:07.370 align:start position:0% passing that's what it does why<00:04:03.700> does<00:04:03.880> it<00:04:03.910> have<00:04:05.700> security<00:04:06.700> or<00:04:06.880> Christie 00:04:07.370 --> 00:04:07.380 align:start position:0% why does it have security or Christie 00:04:07.380 --> 00:04:10.740 align:start position:0% why does it have security or Christie it's<00:04:08.380> air<00:04:08.650> gaps<00:04:08.920> it's<00:04:09.430> offline<00:04:09.940> that's<00:04:10.510> not 00:04:10.740 --> 00:04:10.750 align:start position:0% it's air gaps it's offline that's not 00:04:10.750 --> 00:04:12.360 align:start position:0% it's air gaps it's offline that's not where<00:04:10.900> what<00:04:11.080> is<00:04:11.200> your<00:04:11.650> project<00:04:12.040> you'll<00:04:12.190> never 00:04:12.360 --> 00:04:12.370 align:start position:0% where what is your project you'll never 00:04:12.370 --> 00:04:17.100 align:start position:0% where what is your project you'll never leave<00:04:12.960> and<00:04:13.960> with<00:04:14.770> intoxication<00:04:15.370> provides<00:04:16.180> the 00:04:17.100 --> 00:04:17.110 align:start position:0% leave and with intoxication provides the 00:04:17.110 --> 00:04:19.170 align:start position:0% leave and with intoxication provides the other<00:04:17.260> thing<00:04:17.500> is<00:04:17.620> price<00:04:17.950> order<00:04:18.220> of<00:04:19.030> the 00:04:19.170 --> 00:04:19.180 align:start position:0% other thing is price order of the 00:04:19.180 --> 00:04:20.910 align:start position:0% other thing is price order of the private<00:04:19.510> keys<00:04:19.720> an<00:04:19.930> end<00:04:20.080> user<00:04:20.260> this<00:04:20.799> is 00:04:20.910 --> 00:04:20.920 align:start position:0% private keys an end user this is 00:04:20.920 --> 00:04:29.930 align:start position:0% private keys an end user this is tangible<00:04:21.310> the<00:04:21.970> private<00:04:22.240> keys<00:04:22.480> are<00:04:22.660> here<00:04:22.870> and 00:04:29.930 --> 00:04:29.940 align:start position:0% 00:04:29.940 --> 00:04:36.270 align:start position:0% education<00:04:32.820> lot<00:04:33.820> of<00:04:33.940> things<00:04:34.620> most<00:04:35.620> of<00:04:35.740> us<00:04:35.980> are 00:04:36.270 --> 00:04:36.280 align:start position:0% education lot of things most of us are 00:04:36.280 --> 00:04:40.050 align:start position:0% education lot of things most of us are aware<00:04:36.490> what<00:04:36.850> it's<00:04:38.490> all<00:04:39.490> this<00:04:39.640> top<00:04:39.820> of<00:04:39.940> my 00:04:40.050 --> 00:04:40.060 align:start position:0% aware what it's all this top of my 00:04:40.060 --> 00:04:40.530 align:start position:0% aware what it's all this top of my wallet 00:04:40.530 --> 00:04:40.540 align:start position:0% wallet 00:04:40.540 --> 00:04:45.450 align:start position:0% wallet sorry<00:04:42.690> mobile<00:04:43.690> or<00:04:43.900> desktop<00:04:43.960> well<00:04:44.500> it<00:04:44.620> is<00:04:45.250> can 00:04:45.450 --> 00:04:45.460 align:start position:0% sorry mobile or desktop well it is can 00:04:45.460 --> 00:04:48.090 align:start position:0% sorry mobile or desktop well it is can be<00:04:45.490> used<00:04:45.640> to<00:04:46.060> store<00:04:46.240> the<00:04:46.300> keys<00:04:46.570> for<00:04:47.530> identity 00:04:48.090 --> 00:04:48.100 align:start position:0% be used to store the keys for identity 00:04:48.100 --> 00:04:51.210 align:start position:0% be used to store the keys for identity systems<00:04:48.840> this<00:04:49.840> car<00:04:50.080> is<00:04:50.170> very<00:04:50.200> convenient<00:04:50.830> as 00:04:51.210 --> 00:04:51.220 align:start position:0% systems this car is very convenient as 00:04:51.220 --> 00:04:52.480 align:start position:0% systems this car is very convenient as good<00:04:51.520> right 00:04:52.480 --> 00:04:52.490 align:start position:0% good right 00:04:52.490 --> 00:04:58.120 align:start position:0% good right users<00:04:53.030> of<00:04:53.270> our<00:04:53.569> any<00:04:53.750> identification<00:04:57.130> so 00:04:58.120 --> 00:04:58.130 align:start position:0% users of our any identification so 00:04:58.130 --> 00:05:00.279 align:start position:0% users of our any identification so that's<00:04:58.610> what<00:04:58.940> speaker<00:04:59.360> than<00:04:59.569> what<00:04:59.810> you<00:05:00.080> can 00:05:00.279 --> 00:05:00.289 align:start position:0% that's what speaker than what you can 00:05:00.289 --> 00:05:06.040 align:start position:0% that's what speaker than what you can deal<00:05:00.560> with<00:05:00.590> it<00:05:02.710> so<00:05:04.180> we'd<00:05:05.180> like<00:05:05.360> this<00:05:05.810> to<00:05:05.870> be 00:05:06.040 --> 00:05:06.050 align:start position:0% deal with it so we'd like this to be 00:05:06.050 --> 00:05:11.170 align:start position:0% deal with it so we'd like this to be hands-on<00:05:08.740> suppose<00:05:09.740> we<00:05:10.039> just<00:05:10.069> arrived<00:05:10.610> you<00:05:11.150> can 00:05:11.170 --> 00:05:11.180 align:start position:0% hands-on suppose we just arrived you can 00:05:11.180 --> 00:05:15.730 align:start position:0% hands-on suppose we just arrived you can get<00:05:11.810> some<00:05:12.050> new<00:05:12.289> cards<00:05:13.330> and<00:05:14.330> to<00:05:15.259> connect<00:05:15.590> them 00:05:15.730 --> 00:05:15.740 align:start position:0% get some new cards and to connect them 00:05:15.740 --> 00:05:19.930 align:start position:0% get some new cards and to connect them to<00:05:15.889> your<00:05:16.039> your<00:05:17.000> PC<00:05:18.009> you<00:05:19.009> need<00:05:19.039> some<00:05:19.550> inventive 00:05:19.930 --> 00:05:19.940 align:start position:0% to your your PC you need some inventive 00:05:19.940 --> 00:05:22.960 align:start position:0% to your your PC you need some inventive readers<00:05:20.240> we've<00:05:20.569> already<00:05:20.750> destroyed<00:05:21.319> some<00:05:21.970> and 00:05:22.960 --> 00:05:22.970 align:start position:0% readers we've already destroyed some and 00:05:22.970 --> 00:06:14.430 align:start position:0% readers we've already destroyed some and they<00:05:23.449> are<00:05:23.569> not<00:05:23.720> enough<00:05:23.960> maybe<00:05:24.349> you<00:05:24.560> can 00:06:14.430 --> 00:06:14.440 align:start position:0% 00:06:14.440 --> 00:06:19.740 align:start position:0% [Music] 00:06:19.740 --> 00:06:19.750 align:start position:0% 00:06:19.750 --> 00:06:50.990 align:start position:0% I'm<00:06:20.750> working 00:06:50.990 --> 00:06:51.000 align:start position:0% 00:06:51.000 --> 00:06:53.040 align:start position:0% you<00:06:52.000> might<00:06:52.180> need<00:06:52.330> two<00:06:52.569> things 00:06:53.040 --> 00:06:53.050 align:start position:0% you might need two things 00:06:53.050 --> 00:06:55.320 align:start position:0% you might need two things Tokaji<00:06:53.560> console<00:06:54.129> but<00:06:54.280> tons<00:06:54.550> of<00:06:54.729> them<00:06:54.910> everyone 00:06:55.320 --> 00:06:55.330 align:start position:0% Tokaji console but tons of them everyone 00:06:55.330 --> 00:07:00.450 align:start position:0% Tokaji console but tons of them everyone can<00:06:55.569> get<00:06:55.720> one<00:06:56.099> I<00:06:58.650> mean<00:06:59.650> let's<00:07:00.099> make<00:07:00.310> small 00:07:00.450 --> 00:07:00.460 align:start position:0% can get one I mean let's make small 00:07:00.460 --> 00:07:03.300 align:start position:0% can get one I mean let's make small groups<00:07:00.970> we've<00:07:01.300> already<00:07:01.479> readers<00:07:02.080> our<00:07:02.770> lease 00:07:03.300 --> 00:07:03.310 align:start position:0% groups we've already readers our lease 00:07:03.310 --> 00:07:40.470 align:start position:0% groups we've already readers our lease without<00:07:14.789> my<00:07:15.789> mom<00:07:16.060> here 00:07:40.470 --> 00:07:40.480 align:start position:0% 00:07:40.480 --> 00:07:43.450 align:start position:0% the<00:07:41.480> hobby<00:07:41.690> is<00:07:41.990> that<00:07:42.230> way<00:07:42.470> working<00:07:43.010> because<00:07:43.250> I 00:07:43.450 --> 00:07:43.460 align:start position:0% the hobby is that way working because I 00:07:43.460 --> 00:08:31.310 align:start position:0% the hobby is that way working because I mean<00:07:43.610> you<00:07:43.760> don't<00:07:43.850> know 00:08:31.310 --> 00:08:31.320 align:start position:0% 00:08:31.320 --> 00:08:48.740 align:start position:0% [Music] 00:08:48.740 --> 00:08:48.750 align:start position:0% 00:08:48.750 --> 00:09:07.030 align:start position:0% -<00:08:50.519> trainees 00:09:07.030 --> 00:09:07.040 align:start position:0% 00:09:07.040 --> 00:09:49.470 align:start position:0% I<00:09:43.630> waited 00:09:49.470 --> 00:09:49.480 align:start position:0% 00:09:49.480 --> 00:09:52.600 align:start position:0% it<00:09:50.480> is<00:09:50.720> never<00:09:51.019> in<00:09:51.259> the<00:09:51.410> dark<00:09:51.440> so<00:09:52.160> you<00:09:52.220> when<00:09:52.550> you 00:09:52.600 --> 00:09:52.610 align:start position:0% it is never in the dark so you when you 00:09:52.610 --> 00:09:55.120 align:start position:0% it is never in the dark so you when you are<00:09:52.730> signing<00:09:53.060> with<00:09:53.360> the<00:09:53.569> without<00:09:54.319> polish<00:09:54.889> the 00:09:55.120 --> 00:09:55.130 align:start position:0% are signing with the without polish the 00:09:55.130 --> 00:09:56.889 align:start position:0% are signing with the without polish the signal<00:09:55.459> will<00:09:55.639> speak<00:09:55.880> to<00:09:56.029> the<00:09:56.180> on<00:09:56.480> the<00:09:56.660> car 00:09:56.889 --> 00:09:56.899 align:start position:0% signal will speak to the on the car 00:09:56.899 --> 00:10:02.829 align:start position:0% signal will speak to the on the car which<00:09:57.319> really<00:09:57.920> is<00:09:58.130> a<00:10:01.449> reminder<00:10:02.449> of<00:10:02.660> this 00:10:02.829 --> 00:10:02.839 align:start position:0% which really is a reminder of this 00:10:02.839 --> 00:10:06.550 align:start position:0% which really is a reminder of this aspect<00:10:03.110> and<00:10:04.329> the<00:10:05.329> communicator<00:10:05.930> of<00:10:06.139> the<00:10:06.199> in 00:10:06.550 --> 00:10:06.560 align:start position:0% aspect and the communicator of the in 00:10:06.560 --> 00:10:10.150 align:start position:0% aspect and the communicator of the in that<00:10:06.709> car<00:10:07.100> and<00:10:07.370> the<00:10:08.680> device<00:10:09.680> that<00:10:09.709> you're 00:10:10.150 --> 00:10:10.160 align:start position:0% that car and the device that you're 00:10:10.160 --> 00:10:11.319 align:start position:0% that car and the device that you're using<00:10:10.220> is<00:10:10.759> encrypted 00:10:11.319 --> 00:10:11.329 align:start position:0% using is encrypted 00:10:11.329 --> 00:10:13.990 align:start position:0% using is encrypted this<00:10:11.449> is<00:10:11.709> protocol<00:10:12.709> that<00:10:12.860> we<00:10:13.100> implemented 00:10:13.990 --> 00:10:14.000 align:start position:0% this is protocol that we implemented 00:10:14.000 --> 00:10:15.850 align:start position:0% this is protocol that we implemented above<00:10:14.839> the<00:10:15.110> standard<00:10:15.620> communication 00:10:15.850 --> 00:10:15.860 align:start position:0% above the standard communication 00:10:15.860 --> 00:10:20.350 align:start position:0% above the standard communication protocol<00:10:16.850> it<00:10:17.690> was<00:10:18.490> the<00:10:19.490> use<00:10:19.670> case<00:10:19.940> of<00:10:20.149> this 00:10:20.350 --> 00:10:20.360 align:start position:0% protocol it was the use case of this 00:10:20.360 --> 00:10:22.840 align:start position:0% protocol it was the use case of this kind<00:10:20.569> of<00:10:20.720> cars<00:10:21.019> is<00:10:21.230> you<00:10:21.380> confuse<00:10:21.889> the<00:10:22.519> device 00:10:22.840 --> 00:10:22.850 align:start position:0% kind of cars is you confuse the device 00:10:22.850 --> 00:10:27.759 align:start position:0% kind of cars is you confuse the device sales<00:10:25.180> but<00:10:26.180> in<00:10:26.389> our<00:10:26.510> case<00:10:26.839> you<00:10:26.899> can<00:10:27.380> use<00:10:27.410> except 00:10:27.759 --> 00:10:27.769 align:start position:0% sales but in our case you can use except 00:10:27.769 --> 00:10:29.680 align:start position:0% sales but in our case you can use except any<00:10:27.949> device<00:10:28.339> so<00:10:28.519> we<00:10:28.760> have<00:10:28.850> this<00:10:29.000> a<00:10:29.180> layer<00:10:29.449> of 00:10:29.680 --> 00:10:29.690 align:start position:0% any device so we have this a layer of 00:10:29.690 --> 00:10:33.129 align:start position:0% any device so we have this a layer of aluminum<00:10:29.810> tops<00:10:30.620> which<00:10:31.339> protects<00:10:31.850> many<00:10:32.810> within 00:10:33.129 --> 00:10:33.139 align:start position:0% aluminum tops which protects many within 00:10:33.139 --> 00:10:35.769 align:start position:0% aluminum tops which protects many within the<00:10:33.560> vehicles<00:10:34.190> even<00:10:34.610> if<00:10:34.819> they<00:10:34.970> are<00:10:35.060> quite<00:10:35.389> hard 00:10:35.769 --> 00:10:35.779 align:start position:0% the vehicles even if they are quite hard 00:10:35.779 --> 00:10:38.000 align:start position:0% the vehicles even if they are quite hard to<00:10:35.899> convey<00:10:36.440> out<00:10:36.740> of<00:10:37.130> the<00:10:37.220> spend<00:10:37.430> over 00:10:38.000 --> 00:10:38.010 align:start position:0% to convey out of the spend over 00:10:38.010 --> 00:10:43.400 align:start position:0% to convey out of the spend over over<00:10:38.670> the<00:10:38.910> way<00:10:39.950> and<00:10:40.950> it<00:10:41.550> also<00:10:41.670> prevents<00:10:42.450> random 00:10:43.400 --> 00:10:43.410 align:start position:0% over the way and it also prevents random 00:10:43.410 --> 00:10:46.280 align:start position:0% over the way and it also prevents random device<00:10:43.740> is<00:10:44.100> sending<00:10:44.670> omens<00:10:45.300> with<00:10:45.660> a<00:10:45.780> car<00:10:45.990> I 00:10:46.280 --> 00:10:46.290 align:start position:0% device is sending omens with a car I 00:10:46.290 --> 00:10:49.700 align:start position:0% device is sending omens with a car I mean<00:10:46.650> it<00:10:46.980> as<00:10:47.100> a<00:10:47.130> team<00:10:47.430> for<00:10:47.670> example<00:10:48.170> and<00:10:49.170> you 00:10:49.700 --> 00:10:49.710 align:start position:0% mean it as a team for example and you 00:10:49.710 --> 00:10:51.800 align:start position:0% mean it as a team for example and you could<00:10:49.860> send<00:10:50.190> three<00:10:50.370> time<00:10:50.550> the<00:10:50.700> wrong<00:10:50.880> pin<00:10:51.180> it 00:10:51.800 --> 00:10:51.810 align:start position:0% could send three time the wrong pin it 00:10:51.810 --> 00:10:54.560 align:start position:0% could send three time the wrong pin it cost<00:10:52.110> a<00:10:52.260> car<00:10:52.500> it<00:10:53.130> would<00:10:53.160> be<00:10:53.490> inconvenient<00:10:54.300> if 00:10:54.560 --> 00:10:54.570 align:start position:0% cost a car it would be inconvenient if 00:10:54.570 --> 00:10:57.350 align:start position:0% cost a car it would be inconvenient if ideologically<00:10:55.230> hope<00:10:55.470> doctor<00:10:55.890> so<00:10:56.700> if<00:10:57.180> you 00:10:57.350 --> 00:10:57.360 align:start position:0% ideologically hope doctor so if you 00:10:57.360 --> 00:11:11.080 align:start position:0% ideologically hope doctor so if you don't<00:10:57.630> if<00:10:57.900> you<00:10:58.770> are<00:10:59.150> authorized<00:11:00.150> to<00:11:00.390> even<00:11:00.870> send 00:11:11.080 --> 00:11:11.090 align:start position:0% 00:11:11.090 --> 00:11:14.360 align:start position:0% installation<00:11:12.090> this<00:11:12.660> one<00:11:12.990> is<00:11:13.290> done<00:11:13.560> to<00:11:14.130> park 00:11:14.360 --> 00:11:14.370 align:start position:0% installation this one is done to park 00:11:14.370 --> 00:11:16.760 align:start position:0% installation this one is done to park sorry<00:11:14.670> when<00:11:15.090> so<00:11:15.300> when<00:11:15.450> you<00:11:15.570> ship<00:11:15.750> a<00:11:15.900> true<00:11:16.590> key 00:11:16.760 --> 00:11:16.770 align:start position:0% sorry when so when you ship a true key 00:11:16.770 --> 00:11:19.970 align:start position:0% sorry when so when you ship a true key cards<00:11:17.100> show<00:11:18.050> is<00:11:19.050> already<00:11:19.230> installed 00:11:19.970 --> 00:11:19.980 align:start position:0% cards show is already installed 00:11:19.980 --> 00:11:21.830 align:start position:0% cards show is already installed when<00:11:20.160> double<00:11:20.490> pistol<00:11:20.940> it<00:11:21.030> doesn't<00:11:21.360> have<00:11:21.630> any 00:11:21.830 --> 00:11:21.840 align:start position:0% when double pistol it doesn't have any 00:11:21.840 --> 00:11:23.420 align:start position:0% when double pistol it doesn't have any secret<00:11:22.230> because<00:11:22.500> in<00:11:22.650> Tel<00:11:22.770> Aviv<00:11:22.800> it<00:11:23.310> was 00:11:23.420 --> 00:11:23.430 align:start position:0% secret because in Tel Aviv it was 00:11:23.430 --> 00:11:25.370 align:start position:0% secret because in Tel Aviv it was intended<00:11:23.730> to<00:11:23.820> and<00:11:24.630> it<00:11:24.750> doesn't<00:11:25.050> help<00:11:25.170> the 00:11:25.370 --> 00:11:25.380 align:start position:0% intended to and it doesn't help the 00:11:25.380 --> 00:11:26.750 align:start position:0% intended to and it doesn't help the painting<00:11:25.710> toes<00:11:25.890> which<00:11:26.130> is<00:11:26.280> needed<00:11:26.460> to 00:11:26.750 --> 00:11:26.760 align:start position:0% painting toes which is needed to 00:11:26.760 --> 00:11:30.310 align:start position:0% painting toes which is needed to increase<00:11:27.090> the<00:11:27.210> channel<00:11:28.100> so<00:11:29.100> it's<00:11:29.280> really<00:11:29.550> gone 00:11:30.310 --> 00:11:30.320 align:start position:0% increase the channel so it's really gone 00:11:30.320 --> 00:11:33.260 align:start position:0% increase the channel so it's really gone and<00:11:31.320> then<00:11:31.800> with<00:11:32.070> the<00:11:32.280> installation<00:11:33.060> phase 00:11:33.260 --> 00:11:33.270 align:start position:0% and then with the installation phase 00:11:33.270 --> 00:11:36.020 align:start position:0% and then with the installation phase where<00:11:33.750> you<00:11:34.050> don't<00:11:34.950> the<00:11:35.250> still<00:11:35.490> create<00:11:35.790> a 00:11:36.020 --> 00:11:36.030 align:start position:0% where you don't the still create a 00:11:36.030 --> 00:11:38.690 align:start position:0% where you don't the still create a wallet<00:11:36.420> you<00:11:36.840> just<00:11:36.870> to<00:11:37.380> define<00:11:37.740> your<00:11:38.010> own<00:11:38.220> pin 00:11:38.690 --> 00:11:38.700 align:start position:0% wallet you just to define your own pin 00:11:38.700 --> 00:11:41.390 align:start position:0% wallet you just to define your own pin through<00:11:39.060> and<00:11:39.510> creating<00:11:40.230> hood<00:11:40.410> which<00:11:40.830> is<00:11:40.980> this 00:11:41.390 --> 00:11:41.400 align:start position:0% through and creating hood which is this 00:11:41.400 --> 00:11:45.390 align:start position:0% through and creating hood which is this way<00:11:41.700> so<00:11:42.330> we<00:11:42.510> don't<00:11:43.230> know<00:11:43.470> the<00:11:43.740> problem<00:11:44.310> of<00:11:44.490> the 00:11:45.390 --> 00:11:45.400 align:start position:0% way so we don't know the problem of the 00:11:45.400 --> 00:11:48.600 align:start position:0% way so we don't know the problem of the in<00:11:45.490> addition<00:11:46.180> a<00:11:46.360> separate<00:11:46.990> envelope<00:11:47.230> cord<00:11:48.130> or 00:11:48.600 --> 00:11:48.610 align:start position:0% in addition a separate envelope cord or 00:11:48.610 --> 00:11:51.240 align:start position:0% in addition a separate envelope cord or a<00:11:48.940> scratch<00:11:49.270> coat<00:11:49.570> which<00:11:49.870> can<00:11:50.140> be<00:11:50.350> abandoned<00:11:51.100> in 00:11:51.240 --> 00:11:51.250 align:start position:0% a scratch coat which can be abandoned in 00:11:51.250 --> 00:11:53.850 align:start position:0% a scratch coat which can be abandoned in your<00:11:51.430> inference<00:11:51.910> you<00:11:52.630> do<00:11:52.780> it<00:11:52.900> yourself<00:11:53.410> on 00:11:53.850 --> 00:11:53.860 align:start position:0% your inference you do it yourself on 00:11:53.860 --> 00:11:57.660 align:start position:0% your inference you do it yourself on your<00:11:54.100> audio<00:11:54.550> device<00:11:54.910> you<00:11:55.540> say<00:11:56.370> then<00:11:57.370> there<00:11:57.550> is 00:11:57.660 --> 00:11:57.670 align:start position:0% your audio device you say then there is 00:11:57.670 --> 00:11:59.700 align:start position:0% your audio device you say then there is the<00:11:57.820> key<00:11:58.000> generation<00:11:58.450> step<00:11:58.870> and<00:11:59.050> disconnected 00:11:59.700 --> 00:11:59.710 align:start position:0% the key generation step and disconnected 00:11:59.710 --> 00:12:02.310 align:start position:0% the key generation step and disconnected in<00:11:59.950> different<00:12:00.340> ways<00:12:00.550> because<00:12:01.540> of<00:12:01.840> course<00:12:02.080> we 00:12:02.310 --> 00:12:02.320 align:start position:0% in different ways because of course we 00:12:02.320 --> 00:12:05.010 align:start position:0% in different ways because of course we want<00:12:02.350> people<00:12:02.860> to<00:12:03.040> be<00:12:03.160> able<00:12:03.370> to<00:12:03.550> import<00:12:04.020> the 00:12:05.010 --> 00:12:05.020 align:start position:0% want people to be able to import the 00:12:05.020 --> 00:12:07.860 align:start position:0% want people to be able to import the emitter<00:12:05.470> p9c<00:12:06.100> sprays<00:12:06.460> or<00:12:06.820> for<00:12:07.210> a<00:12:07.240> Vedic<00:12:07.540> system 00:12:07.860 --> 00:12:07.870 align:start position:0% emitter p9c sprays or for a Vedic system 00:12:07.870 --> 00:12:12.960 align:start position:0% emitter p9c sprays or for a Vedic system is<00:12:09.030> you<00:12:10.030> can<00:12:10.060> go<00:12:10.420> the<00:12:10.630> key<00:12:11.310> see<00:12:12.310> the<00:12:12.370> binary 00:12:12.960 --> 00:12:12.970 align:start position:0% is you can go the key see the binary 00:12:12.970 --> 00:12:20.790 align:start position:0% is you can go the key see the binary still<00:12:14.010> just<00:12:15.010> the<00:12:15.130> keeper<00:12:15.730> even<00:12:16.540> without<00:12:19.800> and 00:12:20.790 --> 00:12:20.800 align:start position:0% still just the keeper even without and 00:12:20.800 --> 00:12:26.970 align:start position:0% still just the keeper even without and then<00:12:21.460> you<00:12:21.670> can<00:12:21.850> stop<00:12:22.060> sign<00:12:22.270> is<00:12:22.420> a<00:12:22.590> sign<00:12:23.590> it<00:12:25.980> is 00:12:26.970 --> 00:12:26.980 align:start position:0% then you can stop sign is a sign it is 00:12:26.980 --> 00:12:29.310 align:start position:0% then you can stop sign is a sign it is something<00:12:27.640> that<00:12:28.030> you<00:12:28.270> can<00:12:28.540> go<00:12:28.690> only<00:12:28.900> up<00:12:29.110> to 00:12:29.310 --> 00:12:29.320 align:start position:0% something that you can go only up to 00:12:29.320 --> 00:12:31.830 align:start position:0% something that you can go only up to drop<00:12:29.530> arise<00:12:29.830> with<00:12:30.400> the<00:12:30.520> B<00:12:30.670> so<00:12:31.210> this<00:12:31.330> ends<00:12:31.600> the 00:12:31.830 --> 00:12:31.840 align:start position:0% drop arise with the B so this ends the 00:12:31.840 --> 00:12:36.260 align:start position:0% drop arise with the B so this ends the publisher<00:12:32.230> pin<00:12:32.500> like<00:12:32.790> regular<00:12:34.140> in<00:12:35.140> the<00:12:35.320> end 00:12:36.260 --> 00:12:36.270 align:start position:0% publisher pin like regular in the end 00:12:36.270 --> 00:12:39.250 align:start position:0% publisher pin like regular in the end when<00:12:37.270> you<00:12:37.360> want<00:12:37.570> to<00:12:37.630> sign<00:12:37.960> in 00:12:39.250 --> 00:12:39.260 align:start position:0% when you want to sign in 00:12:39.260 --> 00:12:45.140 align:start position:0% when you want to sign in insert<00:12:40.260> the<00:12:40.410> beep<00:12:40.650> and<00:12:42.170> they<00:12:43.170> take<00:12:43.440> card<00:12:44.150> since 00:12:45.140 --> 00:12:45.150 align:start position:0% insert the beep and they take card since 00:12:45.150 --> 00:12:48.350 align:start position:0% insert the beep and they take card since the<00:12:45.390> edge<00:12:45.600> of<00:12:46.080> the<00:12:46.500> transaction<00:12:47.360> transaction 00:12:48.350 --> 00:12:48.360 align:start position:0% the edge of the transaction transaction 00:12:48.360 --> 00:12:50.570 align:start position:0% the edge of the transaction transaction because<00:12:48.720> it<00:12:48.990> doesn't<00:12:49.770> make<00:12:49.890> is<00:12:50.190> not<00:12:50.370> very 00:12:50.570 --> 00:12:50.580 align:start position:0% because it doesn't make is not very 00:12:50.580 --> 00:12:53.570 align:start position:0% because it doesn't make is not very efficient<00:12:51.150> first<00:12:51.870> and<00:12:52.620> second<00:12:53.010> about<00:12:53.220> doesn't 00:12:53.570 --> 00:12:53.580 align:start position:0% efficient first and second about doesn't 00:12:53.580 --> 00:12:56.150 align:start position:0% efficient first and second about doesn't technically<00:12:54.060> to<00:12:54.390> show<00:12:54.600> you<00:12:54.660> the<00:12:55.350> devalue<00:12:55.980> so 00:12:56.150 --> 00:12:56.160 align:start position:0% technically to show you the devalue so 00:12:56.160 --> 00:12:58.940 align:start position:0% technically to show you the devalue so it<00:12:56.310> doesn't<00:12:56.610> make<00:12:56.970> any<00:12:57.270> sense<00:12:57.390> and<00:12:58.050> then<00:12:58.890> you 00:12:58.940 --> 00:12:58.950 align:start position:0% it doesn't make any sense and then you 00:12:58.950 --> 00:13:01.610 align:start position:0% it doesn't make any sense and then you give<00:12:59.250> us<00:12:59.490> the<00:12:59.610> signal<00:13:00.000> repair<00:13:00.450> and<00:13:01.170> the<00:13:01.380> port 00:13:01.610 --> 00:13:01.620 align:start position:0% give us the signal repair and the port 00:13:01.620 --> 00:13:06.400 align:start position:0% give us the signal repair and the port and<00:13:01.830> the<00:13:02.040> device<00:13:02.550> users<00:13:02.970> can<00:13:03.150> submit<00:13:03.420> this 00:13:06.400 --> 00:13:06.410 align:start position:0% 00:13:06.410 --> 00:13:17.720 align:start position:0% basically<00:13:15.020> ok<00:13:16.020> so<00:13:16.080> in<00:13:16.410> this<00:13:16.529> sense<00:13:16.800> the<00:13:17.040> kicker 00:13:17.720 --> 00:13:17.730 align:start position:0% basically ok so in this sense the kicker 00:13:17.730 --> 00:13:28.610 align:start position:0% basically ok so in this sense the kicker is<00:13:18.260> one<00:13:19.260> interface<00:13:20.180> so<00:13:25.460> yet<00:13:26.460> so<00:13:27.260> you<00:13:28.260> can<00:13:28.440> use 00:13:28.610 --> 00:13:28.620 align:start position:0% is one interface so yet so you can use 00:13:28.620 --> 00:13:31.730 align:start position:0% is one interface so yet so you can use it<00:13:28.890> with<00:13:29.339> NFC<00:13:29.610> and<00:13:30.210> it's<00:13:30.540> maybe<00:13:30.810> the<00:13:31.080> best<00:13:31.529> way 00:13:31.730 --> 00:13:31.740 align:start position:0% it with NFC and it's maybe the best way 00:13:31.740 --> 00:13:32.410 align:start position:0% it with NFC and it's maybe the best way to<00:13:31.770> use 00:13:32.410 --> 00:13:32.420 align:start position:0% to use 00:13:32.420 --> 00:13:36.820 align:start position:0% to use he<00:13:32.540> used<00:13:33.260> to<00:13:33.350> be<00:13:33.500> alive 00:13:36.820 --> 00:13:36.830 align:start position:0% 00:13:36.830 --> 00:13:40.070 align:start position:0% solenoids<00:13:37.830> and<00:13:38.070> that<00:13:38.820> means<00:13:39.060> that<00:13:39.510> you<00:13:39.720> just 00:13:40.070 --> 00:13:40.080 align:start position:0% solenoids and that means that you just 00:13:40.080 --> 00:13:44.060 align:start position:0% solenoids and that means that you just need<00:13:40.500> to<00:13:40.650> talk<00:13:40.830> to<00:13:40.890> be<00:13:41.400> like<00:13:42.240> right<00:13:43.080> you<00:13:43.350> just 00:13:44.060 --> 00:13:44.070 align:start position:0% need to talk to be like right you just 00:13:44.070 --> 00:13:47.770 align:start position:0% need to talk to be like right you just need<00:13:44.310> to<00:13:44.460> top<00:13:44.700> and<00:13:45.060> it's<00:13:45.900> easy<00:13:46.110> to<00:13:46.350> use 00:13:47.770 --> 00:13:47.780 align:start position:0% need to top and it's easy to use 00:13:47.780 --> 00:13:50.420 align:start position:0% need to top and it's easy to use otherwise<00:13:48.780> it's<00:13:49.020> also<00:13:49.140> contact<00:13:49.710> so<00:13:50.400> we 00:13:50.420 --> 00:13:50.430 align:start position:0% otherwise it's also contact so we 00:13:50.430 --> 00:13:54.200 align:start position:0% otherwise it's also contact so we distribute<00:13:51.000> now<00:13:51.390> the<00:13:52.130> USB<00:13:53.130> reader<00:13:53.730> and<00:13:54.060> you 00:13:54.200 --> 00:13:54.210 align:start position:0% distribute now the USB reader and you 00:13:54.210 --> 00:13:57.520 align:start position:0% distribute now the USB reader and you can<00:13:54.420> just<00:13:54.660> use<00:13:54.900> it<00:13:55.110> also<00:13:55.290> in<00:13:55.530> with<00:13:56.100> a<00:13:56.190> lot<00:13:56.340> and 00:13:57.520 --> 00:13:57.530 align:start position:0% can just use it also in with a lot and 00:13:57.530 --> 00:14:03.080 align:start position:0% can just use it also in with a lot and so<00:13:58.760> we<00:13:59.760> released<00:14:00.090> like<00:14:00.330> the<00:14:01.400> Java<00:14:02.400> so<00:14:02.910> for 00:14:03.080 --> 00:14:03.090 align:start position:0% so we released like the Java so for 00:14:03.090 --> 00:14:07.100 align:start position:0% so we released like the Java so for Android<00:14:03.830> SDKs<00:14:04.830> a<00:14:05.070> months<00:14:05.310> ago<00:14:05.520> already<00:14:05.930> in<00:14:06.930> the 00:14:07.100 --> 00:14:07.110 align:start position:0% Android SDKs a months ago already in the 00:14:07.110 --> 00:14:08.960 align:start position:0% Android SDKs a months ago already in the last<00:14:07.700> weeks 00:14:08.960 --> 00:14:08.970 align:start position:0% last weeks 00:14:08.970 --> 00:14:13.700 align:start position:0% last weeks we<00:14:09.120> developed<00:14:09.570> the<00:14:10.530> u.s.<00:14:12.080> sophisticated<00:14:13.080> with 00:14:13.700 --> 00:14:13.710 align:start position:0% we developed the u.s. sophisticated with 00:14:13.710 --> 00:14:19.070 align:start position:0% we developed the u.s. sophisticated with the<00:14:13.740> newest<00:14:14.750> us<00:14:15.750> 13<00:14:17.150> it's<00:14:18.150> possible<00:14:18.750> like<00:14:18.900> to 00:14:19.070 --> 00:14:19.080 align:start position:0% the newest us 13 it's possible like to 00:14:19.080 --> 00:14:22.260 align:start position:0% the newest us 13 it's possible like to send<00:14:19.320> a<00:14:19.530> video<00:14:20.720> hello 00:14:22.260 --> 00:14:22.270 align:start position:0% send a video hello 00:14:22.270 --> 00:14:25.110 align:start position:0% send a video hello [Music] 00:14:25.110 --> 00:14:25.120 align:start position:0% [Music] 00:14:25.120 --> 00:14:29.110 align:start position:0% [Music] yeah<00:14:26.120> so<00:14:26.450> so<00:14:26.750> before<00:14:27.170> yes<00:14:28.010> 13<00:14:28.640> it<00:14:28.910> was 00:14:29.110 --> 00:14:29.120 align:start position:0% yeah so so before yes 13 it was 00:14:29.120 --> 00:14:32.560 align:start position:0% yeah so so before yes 13 it was impossible<00:14:29.420> to<00:14:29.810> send<00:14:30.280> all<00:14:31.280> the<00:14:31.370> kinds<00:14:31.670> of<00:14:31.760> APD 00:14:32.560 --> 00:14:32.570 align:start position:0% impossible to send all the kinds of APD 00:14:32.570 --> 00:14:35.530 align:start position:0% impossible to send all the kinds of APD with<00:14:32.960> so<00:14:33.560> many<00:14:34.160> almonds<00:14:34.760> it's<00:14:35.000> being<00:14:35.180> that<00:14:35.450> you 00:14:35.530 --> 00:14:35.540 align:start position:0% with so many almonds it's being that you 00:14:35.540 --> 00:14:38.710 align:start position:0% with so many almonds it's being that you needed<00:14:35.750> and<00:14:36.080> now<00:14:37.010> it's<00:14:37.160> possible<00:14:37.340> so<00:14:37.880> I<00:14:38.240> think 00:14:38.710 --> 00:14:38.720 align:start position:0% needed and now it's possible so I think 00:14:38.720 --> 00:14:41.400 align:start position:0% needed and now it's possible so I think the<00:14:38.990> first<00:14:39.260> application<00:14:40.010> that<00:14:40.250> was<00:14:40.700> really 00:14:41.400 --> 00:14:41.410 align:start position:0% the first application that was really 00:14:41.410 --> 00:14:44.650 align:start position:0% the first application that was really supports<00:14:42.410> the<00:14:42.590> kicker<00:14:43.220> is<00:14:43.460> gnosis<00:14:44.180> that<00:14:44.390> was 00:14:44.650 --> 00:14:44.660 align:start position:0% supports the kicker is gnosis that was 00:14:44.660 --> 00:14:46.990 align:start position:0% supports the kicker is gnosis that was raised<00:14:44.990> yesterday<00:14:45.320> and<00:14:45.860> also<00:14:46.400> safe<00:14:46.700> and 00:14:46.990 --> 00:14:47.000 align:start position:0% raised yesterday and also safe and 00:14:47.000 --> 00:14:49.600 align:start position:0% raised yesterday and also safe and integrating<00:14:47.960> like<00:14:48.140> the<00:14:48.380> tikka<00:14:49.280> bizarre 00:14:49.600 --> 00:14:49.610 align:start position:0% integrating like the tikka bizarre 00:14:49.610 --> 00:14:51.670 align:start position:0% integrating like the tikka bizarre two-factor<00:14:50.120> authentication<00:14:50.360> system<00:14:51.170> and 00:14:51.670 --> 00:14:51.680 align:start position:0% two-factor authentication system and 00:14:51.680 --> 00:14:55.540 align:start position:0% two-factor authentication system and thank<00:14:52.400> you<00:14:52.640> thank<00:14:53.240> them<00:14:54.170> because<00:14:54.380> they<00:14:54.860> helped 00:14:55.540 --> 00:14:55.550 align:start position:0% thank you thank them because they helped 00:14:55.550 --> 00:14:59.320 align:start position:0% thank you thank them because they helped other<00:14:56.020> development<00:14:57.020> and<00:14:57.550> so<00:14:58.550> now<00:14:58.790> if<00:14:59.120> you<00:14:59.300> want 00:14:59.320 --> 00:14:59.330 align:start position:0% other development and so now if you want 00:14:59.330 --> 00:15:01.990 align:start position:0% other development and so now if you want to<00:14:59.600> try<00:14:59.840> something<00:15:00.400> maybe<00:15:01.400> doing<00:15:01.700> something 00:15:01.990 --> 00:15:02.000 align:start position:0% to try something maybe doing something 00:15:02.000 --> 00:15:05.510 align:start position:0% to try something maybe doing something mobile<00:15:02.420> will<00:15:03.230> be<00:15:03.490> longer<00:15:04.490> because<00:15:04.880> we<00:15:05.060> need<00:15:05.330> to 00:15:05.510 --> 00:15:05.520 align:start position:0% mobile will be longer because we need to 00:15:05.520 --> 00:15:06.600 align:start position:0% mobile will be longer because we need to [Music] 00:15:06.600 --> 00:15:06.610 align:start position:0% [Music] 00:15:06.610 --> 00:15:11.920 align:start position:0% [Music] buy<00:15:07.610> a<00:15:07.910> pilot's<00:15:08.420> and<00:15:08.860> the<00:15:09.860> points<00:15:10.840> to<00:15:11.840> the 00:15:11.920 --> 00:15:11.930 align:start position:0% buy a pilot's and the points to the 00:15:11.930 --> 00:15:15.280 align:start position:0% buy a pilot's and the points to the phone<00:15:12.170> so<00:15:12.500> we<00:15:13.310> also<00:15:14.000> develop<00:15:14.510> this<00:15:14.750> kick-ass 00:15:15.280 --> 00:15:15.290 align:start position:0% phone so we also develop this kick-ass 00:15:15.290 --> 00:15:18.070 align:start position:0% phone so we also develop this kick-ass CLI<00:15:15.710> so<00:15:16.550> we<00:15:16.670> can<00:15:16.850> basically<00:15:17.090> try<00:15:17.360> to<00:15:17.690> use<00:15:18.050> it 00:15:18.070 --> 00:15:18.080 align:start position:0% CLI so we can basically try to use it 00:15:18.080 --> 00:15:21.400 align:start position:0% CLI so we can basically try to use it and<00:15:18.640> see<00:15:19.640> basically<00:15:20.090> all<00:15:20.210> the<00:15:20.450> comments<00:15:20.900> that 00:15:21.400 --> 00:15:21.410 align:start position:0% and see basically all the comments that 00:15:21.410 --> 00:15:23.230 align:start position:0% and see basically all the comments that you<00:15:21.530> can<00:15:21.710> use<00:15:22.160> to<00:15:22.490> interact<00:15:22.790> with<00:15:23.150> the 00:15:23.230 --> 00:15:23.240 align:start position:0% you can use to interact with the 00:15:23.240 --> 00:15:25.720 align:start position:0% you can use to interact with the kicker's<00:15:23.630> from<00:15:23.960> scratch<00:15:24.440> to<00:15:24.860> sign<00:15:25.460> with 00:15:25.720 --> 00:15:25.730 align:start position:0% kicker's from scratch to sign with 00:15:25.730 --> 00:15:28.660 align:start position:0% kicker's from scratch to sign with signature<00:15:26.180> and<00:15:26.660> signing<00:15:27.500> the<00:15:27.670> transaction 00:15:28.660 --> 00:15:28.670 align:start position:0% signature and signing the transaction 00:15:28.670 --> 00:15:31.300 align:start position:0% signature and signing the transaction and<00:15:28.850> then<00:15:29.780> basically<00:15:30.110> that<00:15:30.230> the<00:15:30.560> same<00:15:30.800> concept 00:15:31.300 --> 00:15:31.310 align:start position:0% and then basically that the same concept 00:15:31.310 --> 00:15:32.700 align:start position:0% and then basically that the same concept you<00:15:31.460> can<00:15:31.520> apply<00:15:31.940> them 00:15:32.700 --> 00:15:32.710 align:start position:0% you can apply them 00:15:32.710 --> 00:15:35.389 align:start position:0% you can apply them [Music] 00:15:35.389 --> 00:15:35.399 align:start position:0% [Music] 00:15:35.399 --> 00:15:42.530 align:start position:0% [Music] so<00:15:35.970> I<00:15:36.240> took<00:15:36.300> my<00:15:36.450> things<00:15:40.670> before<00:15:41.670> so<00:15:42.149> the<00:15:42.269> first 00:15:42.530 --> 00:15:42.540 align:start position:0% so I took my things before so the first 00:15:42.540 --> 00:15:47.900 align:start position:0% so I took my things before so the first one<00:15:42.779> so<00:15:43.470> this<00:15:43.649> is<00:15:43.800> the<00:15:45.140> keycard<00:15:46.140> outlets<00:15:46.910> and 00:15:47.900 --> 00:15:47.910 align:start position:0% one so this is the keycard outlets and 00:15:47.910 --> 00:15:49.460 align:start position:0% one so this is the keycard outlets and it's<00:15:48.209> basically<00:15:48.570> the<00:15:48.810> software<00:15:49.230> this<00:15:49.410> is 00:15:49.460 --> 00:15:49.470 align:start position:0% it's basically the software this is 00:15:49.470 --> 00:15:53.780 align:start position:0% it's basically the software this is finding<00:15:50.029> the<00:15:51.029> kicker<00:15:51.329> and<00:15:52.190> its<00:15:53.190> resources 00:15:53.780 --> 00:15:53.790 align:start position:0% finding the kicker and its resources 00:15:53.790 --> 00:15:59.720 align:start position:0% finding the kicker and its resources here<00:15:54.149> it<00:15:54.899> is<00:15:55.050> I<00:15:55.230> am<00:15:55.730> salacious<00:15:57.680> and<00:15:58.680> train<00:15:59.070> the 00:15:59.720 --> 00:15:59.730 align:start position:0% here it is I am salacious and train the 00:15:59.730 --> 00:16:03.280 align:start position:0% here it is I am salacious and train the CLI<00:16:00.149> says<00:16:00.540> is<00:16:00.870> within<00:16:01.170> go<00:16:01.500> and<00:16:01.769> you<00:16:02.430> can 00:16:03.280 --> 00:16:03.290 align:start position:0% CLI says is within go and you can 00:16:03.290 --> 00:16:19.030 align:start position:0% CLI says is within go and you can [Music] 00:16:19.030 --> 00:16:19.040 align:start position:0% 00:16:19.040 --> 00:17:18.350 align:start position:0% yeah<00:17:14.750> okay<00:17:15.750> so<00:17:15.810> if<00:17:16.050> you<00:17:16.230> have<00:17:16.410> the<00:17:16.680> GST<00:17:17.459> running 00:17:18.350 --> 00:17:18.360 align:start position:0% yeah okay so if you have the GST running 00:17:18.360 --> 00:17:21.770 align:start position:0% yeah okay so if you have the GST running until<00:17:19.020> the<00:17:20.089> end<00:17:21.089> you<00:17:21.180> don't<00:17:21.390> know<00:17:21.510> that<00:17:21.690> the 00:17:21.770 --> 00:17:21.780 align:start position:0% until the end you don't know that the 00:17:21.780 --> 00:17:24.829 align:start position:0% until the end you don't know that the key<00:17:21.930> card<00:17:22.170> which<00:17:22.920> dominancy<00:17:23.790> right<00:17:23.970> you<00:17:24.660> can 00:17:24.829 --> 00:17:24.839 align:start position:0% key card which dominancy right you can 00:17:24.839 --> 00:17:27.560 align:start position:0% key card which dominancy right you can just<00:17:24.870> run<00:17:25.260> ticket<00:17:25.740> in<00:17:25.949> focus<00:17:26.510> and<00:17:27.510> you 00:17:27.560 --> 00:17:27.570 align:start position:0% just run ticket in focus and you 00:17:27.570 --> 00:17:31.280 align:start position:0% just run ticket in focus and you basically<00:17:28.910> know<00:17:29.910> like<00:17:30.510> something<00:17:30.900> about<00:17:31.020> the 00:17:31.280 --> 00:17:31.290 align:start position:0% basically know like something about the 00:17:31.290 --> 00:17:34.029 align:start position:0% basically know like something about the card<00:17:31.530> gives<00:17:31.860> you<00:17:32.070> certain 00:17:34.029 --> 00:17:34.039 align:start position:0% card gives you certain 00:17:34.039 --> 00:17:42.370 align:start position:0% card gives you certain so<00:17:34.669> few<00:17:38.440> can<00:17:39.440> see<00:17:39.620> here<00:17:39.860> so<00:17:40.360> it<00:17:41.360> says<00:17:42.020> if<00:17:42.320> the 00:17:42.370 --> 00:17:42.380 align:start position:0% so few can see here so it says if the 00:17:42.380 --> 00:17:47.140 align:start position:0% so few can see here so it says if the Outlands<00:17:43.370> is<00:17:43.580> resistant<00:17:45.010> shall<00:17:46.010> I<00:17:46.100> fix<00:17:46.850> it<00:17:47.030> let 00:17:47.140 --> 00:17:47.150 align:start position:0% Outlands is resistant shall I fix it let 00:17:47.150 --> 00:17:50.110 align:start position:0% Outlands is resistant shall I fix it let me<00:17:47.179> see<00:17:47.450> later<00:17:47.750> but<00:17:48.049> it's<00:17:48.530> not<00:17:48.679> useful<00:17:48.860> yet<00:17:49.309> so 00:17:50.110 --> 00:17:50.120 align:start position:0% me see later but it's not useful yet so 00:17:50.120 --> 00:17:54.720 align:start position:0% me see later but it's not useful yet so we<00:17:50.240> can<00:17:50.390> use<00:17:50.570> all<00:17:50.840> the<00:17:51.320> key<00:17:51.980> card<00:17:52.280> installed<00:17:52.970> to 00:17:54.720 --> 00:17:54.730 align:start position:0% we can use all the key card installed to 00:17:54.730 --> 00:18:04.299 align:start position:0% we can use all the key card installed to pay<00:17:55.730> comments<00:17:56.450> or<00:17:56.630> we<00:17:57.049> can<00:17:57.230> use<00:17:57.380> also<00:18:03.130> you<00:18:04.130> can 00:18:04.299 --> 00:18:04.309 align:start position:0% pay comments or we can use also you can 00:18:04.309 --> 00:18:10.720 align:start position:0% pay comments or we can use also you can use<00:18:04.549> the<00:18:05.110> kicker<00:18:07.600> shell<00:18:08.770> comment<00:18:09.770> and<00:18:10.400> you<00:18:10.549> can 00:18:10.720 --> 00:18:10.730 align:start position:0% use the kicker shell comment and you can 00:18:10.730 --> 00:18:14.740 align:start position:0% use the kicker shell comment and you can justify<00:18:11.030> or<00:18:11.630> direct<00:18:12.400> a<00:18:13.400> list<00:18:13.940> of<00:18:14.150> comments<00:18:14.630> and 00:18:14.740 --> 00:18:14.750 align:start position:0% justify or direct a list of comments and 00:18:14.750 --> 00:18:17.409 align:start position:0% justify or direct a list of comments and in<00:18:14.990> this<00:18:15.230> specific<00:18:15.679> case<00:18:15.909> there's<00:18:16.909> a<00:18:17.000> list<00:18:17.210> of 00:18:17.409 --> 00:18:17.419 align:start position:0% in this specific case there's a list of 00:18:17.419 --> 00:18:24.190 align:start position:0% in this specific case there's a list of like<00:18:18.730> video<00:18:19.730> comments<00:18:21.789> to<00:18:23.049> install<00:18:24.049> the 00:18:24.190 --> 00:18:24.200 align:start position:0% like video comments to install the 00:18:24.200 --> 00:18:26.799 align:start position:0% like video comments to install the updates<00:18:24.500> so<00:18:25.159> when<00:18:25.520> you<00:18:25.640> receive<00:18:25.789> the<00:18:26.179> decals 00:18:26.799 --> 00:18:26.809 align:start position:0% updates so when you receive the decals 00:18:26.809 --> 00:18:29.409 align:start position:0% updates so when you receive the decals of<00:18:27.020> the<00:18:27.169> blue<00:18:27.440> key<00:18:27.620> of<00:18:27.830> it<00:18:27.980> you<00:18:28.070> can<00:18:28.220> buy<00:18:28.419> the 00:18:29.409 --> 00:18:29.419 align:start position:0% of the blue key of it you can buy the 00:18:29.419 --> 00:18:32.200 align:start position:0% of the blue key of it you can buy the applet<00:18:29.690> is<00:18:29.840> already<00:18:30.080> closed<00:18:30.860> so<00:18:31.280> you<00:18:32.000> don't 00:18:32.200 --> 00:18:32.210 align:start position:0% applet is already closed so you don't 00:18:32.210 --> 00:18:34.720 align:start position:0% applet is already closed so you don't need<00:18:32.330> some<00:18:32.539> of<00:18:32.659> these<00:18:32.780> I've<00:18:33.490> gotta<00:18:34.490> pick 00:18:34.720 --> 00:18:34.730 align:start position:0% need some of these I've gotta pick 00:18:34.730 --> 00:18:36.909 align:start position:0% need some of these I've gotta pick something<00:18:35.570> for<00:18:35.870> the<00:18:35.960> key<00:18:36.110> and<00:18:36.320> you<00:18:36.440> want<00:18:36.740> to 00:18:36.909 --> 00:18:36.919 align:start position:0% something for the key and you want to 00:18:36.919 --> 00:18:41.230 align:start position:0% something for the key and you want to upgrade<00:18:37.520> or<00:18:38.260> install<00:18:39.260> the<00:18:39.470> updates<00:18:39.919> or<00:18:40.190> not<00:18:41.000> do 00:18:41.230 --> 00:18:41.240 align:start position:0% upgrade or install the updates or not do 00:18:41.240 --> 00:18:44.190 align:start position:0% upgrade or install the updates or not do something<00:18:41.659> else<00:18:42.100> you<00:18:43.100> need<00:18:43.250> this<00:18:43.429> kind<00:18:43.700> of 00:18:44.190 --> 00:18:44.200 align:start position:0% something else you need this kind of 00:18:44.200 --> 00:18:49.529 align:start position:0% something else you need this kind of comments<00:18:45.200> so<00:18:45.380> that's<00:18:47.590> another<00:18:48.590> thing<00:18:48.740> is<00:18:49.010> it's 00:18:49.529 --> 00:18:49.539 align:start position:0% comments so that's another thing is it's 00:18:49.539 --> 00:18:52.570 align:start position:0% comments so that's another thing is it's in<00:18:50.539> a<00:18:50.720> smart<00:18:50.960> car<00:18:51.020> you<00:18:51.289> can<00:18:51.440> also<00:18:51.590> use<00:18:52.340> so 00:18:52.570 --> 00:18:52.580 align:start position:0% in a smart car you can also use so 00:18:52.580 --> 00:18:55.990 align:start position:0% in a smart car you can also use so multiple<00:18:53.090> instances<00:18:53.539> of<00:18:53.600> the<00:18:53.809> key<00:18:54.470> cut<00:18:54.909> so<00:18:55.909> it 00:18:55.990 --> 00:18:56.000 align:start position:0% multiple instances of the key cut so it 00:18:56.000 --> 00:18:56.960 align:start position:0% multiple instances of the key cut so it means<00:18:56.179> that<00:18:56.419> you<00:18:56.510> can<00:18:56.659> have 00:18:56.960 --> 00:18:56.970 align:start position:0% means that you can have 00:18:56.970 --> 00:19:00.020 align:start position:0% means that you can have five<00:18:57.630> different<00:18:57.929> HD<00:18:58.679> wallets<00:18:59.130> along<00:18:59.760> with<00:18:59.940> a 00:19:00.020 --> 00:19:00.030 align:start position:0% five different HD wallets along with a 00:19:00.030 --> 00:19:02.690 align:start position:0% five different HD wallets along with a different<00:19:00.360> master<00:19:00.539> key<00:19:00.840> and<00:19:01.080> then<00:19:01.620> you<00:19:02.490> just 00:19:02.690 --> 00:19:02.700 align:start position:0% different master key and then you just 00:19:02.700 --> 00:19:09.980 align:start position:0% different master key and then you just select<00:19:06.530> so<00:19:07.530> in<00:19:07.620> this<00:19:07.710> case<00:19:07.950> it's<00:19:08.190> a<00:19:08.309> if<00:19:09.000> I<00:19:09.360> run 00:19:09.980 --> 00:19:09.990 align:start position:0% select so in this case it's a if I run 00:19:09.990 --> 00:19:16.220 align:start position:0% select so in this case it's a if I run this<00:19:10.230> I<00:19:11.039> also<00:19:12.650> put<00:19:13.650> right<00:19:13.890> about<00:19:14.250> here<00:19:15.049> and<00:19:16.049> you 00:19:16.220 --> 00:19:16.230 align:start position:0% this I also put right about here and you 00:19:16.230 --> 00:19:18.140 align:start position:0% this I also put right about here and you can<00:19:16.380> see<00:19:16.590> all<00:19:16.770> the<00:19:17.010> video<00:19:17.460> comments<00:19:17.940> at<00:19:18.030> the 00:19:18.140 --> 00:19:18.150 align:start position:0% can see all the video comments at the 00:19:18.150 --> 00:19:19.940 align:start position:0% can see all the video comments at the same<00:19:18.360> so<00:19:18.750> they<00:19:19.049> can<00:19:19.230> you<00:19:19.320> cannot<00:19:19.620> have<00:19:19.740> these 00:19:19.940 --> 00:19:19.950 align:start position:0% same so they can you cannot have these 00:19:19.950 --> 00:19:22.909 align:start position:0% same so they can you cannot have these bytes<00:19:20.549> that<00:19:20.940> are<00:19:21.780> basically<00:19:22.260> sent<00:19:22.590> to<00:19:22.770> the 00:19:22.909 --> 00:19:22.919 align:start position:0% bytes that are basically sent to the 00:19:22.919 --> 00:19:27.240 align:start position:0% bytes that are basically sent to the cards<00:19:23.510> each<00:19:24.510> one<00:19:24.809> is<00:19:24.990> a<00:19:25.020> set<00:19:25.530> of<00:19:25.799> classified 00:19:27.240 --> 00:19:27.250 align:start position:0% cards each one is a set of classified 00:19:27.250 --> 00:19:28.870 align:start position:0% cards each one is a set of classified [Music] 00:19:28.870 --> 00:19:28.880 align:start position:0% [Music] 00:19:28.880 --> 00:19:31.399 align:start position:0% [Music] instruction<00:19:29.880> by<00:19:30.059> some<00:19:30.570> parameters<00:19:31.080> and<00:19:31.230> some 00:19:31.399 --> 00:19:31.409 align:start position:0% instruction by some parameters and some 00:19:31.409 --> 00:19:33.919 align:start position:0% instruction by some parameters and some data<00:19:31.679> so<00:19:32.549> in<00:19:32.789> this<00:19:32.909> case<00:19:33.150> it's<00:19:33.330> long<00:19:33.510> because 00:19:33.919 --> 00:19:33.929 align:start position:0% data so in this case it's long because 00:19:33.929 --> 00:19:36.890 align:start position:0% data so in this case it's long because it's<00:19:34.110> like<00:19:34.440> uploading<00:19:35.070> the<00:19:36.059> output<00:19:36.390> and<00:19:36.600> after 00:19:36.890 --> 00:19:36.900 align:start position:0% it's like uploading the output and after 00:19:36.900 --> 00:19:40.430 align:start position:0% it's like uploading the output and after this<00:19:37.049> you<00:19:37.830> basically<00:19:38.340> have<00:19:38.960> this<00:19:39.960> math<00:19:40.230> curve 00:19:40.430 --> 00:19:40.440 align:start position:0% this you basically have this math curve 00:19:40.440 --> 00:19:43.669 align:start position:0% this you basically have this math curve in<00:19:40.650> the<00:19:40.740> same<00:19:40.919> state<00:19:41.840> of<00:19:42.840> the<00:19:43.110> one<00:19:43.350> that<00:19:43.559> you 00:19:43.669 --> 00:19:43.679 align:start position:0% in the same state of the one that you 00:19:43.679 --> 00:19:46.190 align:start position:0% in the same state of the one that you received<00:19:44.039> when<00:19:44.280> when<00:19:45.240> you<00:19:45.330> buy<00:19:45.510> one<00:19:45.539> so<00:19:46.020> it's 00:19:46.190 --> 00:19:46.200 align:start position:0% received when when you buy one so it's 00:19:46.200 --> 00:19:48.799 align:start position:0% received when when you buy one so it's restored<00:19:46.620> a<00:19:46.860> lot<00:19:47.070> in<00:19:47.220> choice<00:19:47.570> which<00:19:48.570> means 00:19:48.799 --> 00:19:48.809 align:start position:0% restored a lot in choice which means 00:19:48.809 --> 00:19:51.649 align:start position:0% restored a lot in choice which means that<00:19:49.080> it's<00:19:49.830> ready<00:19:50.100> to<00:19:50.250> be<00:19:50.490> used<00:19:50.539> but<00:19:51.539> it 00:19:51.649 --> 00:19:51.659 align:start position:0% that it's ready to be used but it 00:19:51.659 --> 00:19:55.850 align:start position:0% that it's ready to be used but it doesn't<00:19:51.990> have<00:19:52.460> a<00:19:53.460> second<00:19:54.179> unit<00:19:54.650> since<00:19:55.650> the 00:19:55.850 --> 00:19:55.860 align:start position:0% doesn't have a second unit since the 00:19:55.860 --> 00:20:00.980 align:start position:0% doesn't have a second unit since the running<00:19:56.280> game<00:19:56.460> like<00:19:58.130> we<00:19:59.130> won<00:19:59.940> before<00:20:00.090> so<00:20:00.780> now 00:20:00.980 --> 00:20:00.990 align:start position:0% running game like we won before so now 00:20:00.990 --> 00:20:06.110 align:start position:0% running game like we won before so now it<00:20:01.500> says<00:20:01.559> that 00:20:06.110 --> 00:20:06.120 align:start position:0% 00:20:06.120 --> 00:20:09.180 align:start position:0% so<00:20:07.120> now<00:20:07.270> it's<00:20:07.420> installed<00:20:07.810> it's<00:20:08.590> not 00:20:09.180 --> 00:20:09.190 align:start position:0% so now it's installed it's not 00:20:09.190 --> 00:20:11.790 align:start position:0% so now it's installed it's not initialized<00:20:09.670> meaning<00:20:10.120> there's<00:20:10.330> no<00:20:10.800> steam 00:20:11.790 --> 00:20:11.800 align:start position:0% initialized meaning there's no steam 00:20:11.800 --> 00:20:16.040 align:start position:0% initialized meaning there's no steam it's<00:20:12.640> not<00:20:12.850> ready<00:20:13.090> to<00:20:13.300> be<00:20:13.450> paired<00:20:13.690> with<00:20:14.670> device 00:20:16.040 --> 00:20:16.050 align:start position:0% it's not ready to be paired with device 00:20:16.050 --> 00:20:19.050 align:start position:0% it's not ready to be paired with device there's<00:20:17.050> no<00:20:17.200> key<00:20:17.410> so<00:20:17.710> there's<00:20:17.920> no<00:20:18.070> you<00:20:18.580> ain't 00:20:19.050 --> 00:20:19.060 align:start position:0% there's no key so there's no you ain't 00:20:19.060 --> 00:20:23.460 align:start position:0% there's no key so there's no you ain't and<00:20:19.440> this<00:20:20.440> just<00:20:21.300> keep<00:20:22.300> that<00:20:22.600> it's<00:20:22.840> used<00:20:23.230> like 00:20:23.460 --> 00:20:23.470 align:start position:0% and this just keep that it's used like 00:20:23.470 --> 00:20:29.690 align:start position:0% and this just keep that it's used like full<00:20:23.800> of<00:20:23.950> service<00:20:24.250> solution<00:20:25.140> so<00:20:26.140> after<00:20:26.470> this 00:20:29.690 --> 00:20:29.700 align:start position:0% 00:20:29.700 --> 00:20:33.000 align:start position:0% are<00:20:30.700> you<00:20:30.880> trying<00:20:31.360> something<00:20:31.630> so<00:20:31.930> it<00:20:32.350> granny<00:20:32.800> if 00:20:33.000 --> 00:20:33.010 align:start position:0% are you trying something so it granny if 00:20:33.010 --> 00:20:45.530 align:start position:0% are you trying something so it granny if it's<00:20:33.160> not<00:20:33.370> working<00:20:41.910> okay<00:20:42.910> so 00:20:45.530 --> 00:20:45.540 align:start position:0% 00:20:45.540 --> 00:20:47.630 align:start position:0% whatever<00:20:46.320> saying<00:20:46.740> when<00:20:47.070> you<00:20:47.220> know<00:20:47.340> whenever 00:20:47.630 --> 00:20:47.640 align:start position:0% whatever saying when you know whenever 00:20:47.640 --> 00:20:50.000 align:start position:0% whatever saying when you know whenever say<00:20:47.910> I<00:20:48.060> thought<00:20:48.240> it's<00:20:48.450> not<00:20:48.510> ready<00:20:48.900> to<00:20:49.200> I<00:20:49.650> mean 00:20:50.000 --> 00:20:50.010 align:start position:0% say I thought it's not ready to I mean 00:20:50.010 --> 00:20:51.650 align:start position:0% say I thought it's not ready to I mean it's<00:20:50.190> ready<00:20:50.400> to<00:20:50.490> be<00:20:50.700> used<00:20:50.820> but<00:20:51.150> you<00:20:51.210> need<00:20:51.480> to 00:20:51.650 --> 00:20:51.660 align:start position:0% it's ready to be used but you need to 00:20:51.660 --> 00:20:54.710 align:start position:0% it's ready to be used but you need to initialize<00:20:52.650> it<00:20:52.800> and<00:20:53.220> this<00:20:53.910> means<00:20:54.240> basically 00:20:54.710 --> 00:20:54.720 align:start position:0% initialize it and this means basically 00:20:54.720 --> 00:20:57.440 align:start position:0% initialize it and this means basically creating<00:20:55.380> the<00:20:55.530> signature<00:20:56.040> so<00:20:56.730> the<00:20:56.970> secrets 00:20:57.440 --> 00:20:57.450 align:start position:0% creating the signature so the secrets 00:20:57.450 --> 00:21:00.080 align:start position:0% creating the signature so the secrets that<00:20:57.570> you<00:20:57.750> have<00:20:58.140> to<00:20:58.530> use<00:20:58.800> to<00:20:59.010> to<00:20:59.520> use<00:20:59.700> it<00:20:59.730> later 00:21:00.080 --> 00:21:00.090 align:start position:0% that you have to use to to use it later 00:21:00.090 --> 00:21:03.020 align:start position:0% that you have to use to to use it later so<00:21:00.510> in<00:21:00.870> this<00:21:01.020> case<00:21:01.320> our<00:21:01.590> so<00:21:02.160> the<00:21:02.310> first<00:21:02.550> one<00:21:02.790> is 00:21:03.020 --> 00:21:03.030 align:start position:0% so in this case our so the first one is 00:21:03.030 --> 00:21:10.310 align:start position:0% so in this case our so the first one is the<00:21:06.140> the<00:21:07.140> pin<00:21:07.380> the<00:21:07.920> second<00:21:08.280> one<00:21:08.430> is<00:21:08.580> the<00:21:09.320> third 00:21:10.310 --> 00:21:10.320 align:start position:0% the the pin the second one is the third 00:21:10.320 --> 00:21:13.880 align:start position:0% the the pin the second one is the third one<00:21:10.620> is<00:21:10.980> a<00:21:11.190> parent<00:21:11.580> password<00:21:12.320> so<00:21:13.320> in<00:21:13.500> this<00:21:13.620> case 00:21:13.880 --> 00:21:13.890 align:start position:0% one is a parent password so in this case 00:21:13.890 --> 00:21:18.700 align:start position:0% one is a parent password so in this case if<00:21:14.160> you<00:21:14.370> want<00:21:14.750> to<00:21:15.750> do<00:21:16.020> the<00:21:16.290> same<00:21:16.500> shell<00:21:17.210> scripts 00:21:18.700 --> 00:21:18.710 align:start position:0% if you want to do the same shell scripts 00:21:18.710 --> 00:21:30.530 align:start position:0% if you want to do the same shell scripts going<00:21:20.810> to<00:21:21.810> wrap<00:21:21.960> this<00:21:22.080> up<00:21:22.320> all<00:21:23.010> the<00:21:23.460> scripts<00:21:29.540> if 00:21:30.530 --> 00:21:30.540 align:start position:0% going to wrap this up all the scripts if 00:21:30.540 --> 00:21:39.110 align:start position:0% going to wrap this up all the scripts if you<00:21:30.660> want<00:21:30.840> to<00:21:31.020> secure<00:21:31.770> saying<00:21:37.970> comments<00:21:38.970> you 00:21:39.110 --> 00:21:39.120 align:start position:0% you want to secure saying comments you 00:21:39.120 --> 00:21:43.100 align:start position:0% you want to secure saying comments you know<00:21:39.420> the<00:21:40.020> you<00:21:40.440> have<00:21:40.860> obviously<00:21:41.870> this<00:21:42.870> one 00:21:43.100 --> 00:21:43.110 align:start position:0% know the you have obviously this one 00:21:43.110 --> 00:21:49.370 align:start position:0% know the you have obviously this one thing<00:21:44.660> that's<00:21:45.770> here<00:21:46.770> in<00:21:47.130> the<00:21:47.630> description<00:21:48.630> the 00:21:49.370 --> 00:21:49.380 align:start position:0% thing that's here in the description the 00:21:49.380 --> 00:21:49.980 align:start position:0% thing that's here in the description the first<00:21:49.410> one 00:21:49.980 --> 00:21:49.990 align:start position:0% first one 00:21:49.990 --> 00:21:54.240 align:start position:0% first one -<00:21:50.140> still<00:21:50.710> the<00:21:50.860> office<00:21:52.530> still<00:21:53.530> the<00:21:53.679> instrument 00:21:54.240 --> 00:21:54.250 align:start position:0% - still the office still the instrument 00:21:54.250 --> 00:22:02.700 align:start position:0% - still the office still the instrument between<00:21:54.370> just<00:21:59.580> okay<00:22:00.580> so<00:22:00.640> this<00:22:01.059> one<00:22:01.330> has<00:22:01.660> a<00:22:01.710> hard 00:22:02.700 --> 00:22:02.710 align:start position:0% between just okay so this one has a hard 00:22:02.710 --> 00:22:06.900 align:start position:0% between just okay so this one has a hard coded<00:22:02.950> like<00:22:03.340> path<00:22:04.179> to<00:22:04.690> the<00:22:04.830> bell<00:22:05.830> plaits<00:22:06.190> the 00:22:06.900 --> 00:22:06.910 align:start position:0% coded like path to the bell plaits the 00:22:06.910 --> 00:22:19.530 align:start position:0% coded like path to the bell plaits the little<00:22:07.179> before<00:22:08.040> changes<00:22:13.980> so<00:22:14.980> what<00:22:18.420> it's<00:22:19.420> an 00:22:19.530 --> 00:22:19.540 align:start position:0% little before changes so what it's an 00:22:19.540 --> 00:22:25.440 align:start position:0% little before changes so what it's an arm<00:22:19.750> right<00:22:20.010> second<00:22:21.010> script<00:22:22.590> so<00:22:23.940> this<00:22:24.940> one<00:22:25.210> is 00:22:25.440 --> 00:22:25.450 align:start position:0% arm right second script so this one is 00:22:25.450 --> 00:22:29.040 align:start position:0% arm right second script so this one is basically<00:22:25.809> and<00:22:26.320> so<00:22:26.830> he<00:22:27.010> can<00:22:27.190> sell<00:22:27.400> in<00:22:28.000> here<00:22:28.270> if 00:22:29.040 --> 00:22:29.050 align:start position:0% basically and so he can sell in here if 00:22:29.050 --> 00:22:31.650 align:start position:0% basically and so he can sell in here if I<00:22:29.200> go<00:22:29.380> back<00:22:29.559> to<00:22:29.590> install<00:22:30.429> you<00:22:31.179> can<00:22:31.330> see<00:22:31.480> that 00:22:31.650 --> 00:22:31.660 align:start position:0% I go back to install you can see that 00:22:31.660 --> 00:22:34.620 align:start position:0% I go back to install you can see that the<00:22:32.230> some<00:22:32.850> comments<00:22:33.850> there<00:22:33.880> are<00:22:34.179> starting 00:22:34.620 --> 00:22:34.630 align:start position:0% the some comments there are starting 00:22:34.630 --> 00:22:37.830 align:start position:0% the some comments there are starting with<00:22:34.750> GP<00:22:35.550> another<00:22:36.550> woody<00:22:36.820> cancer<00:22:37.420> to<00:22:37.630> please 00:22:37.830 --> 00:22:37.840 align:start position:0% with GP another woody cancer to please 00:22:37.840 --> 00:22:41.840 align:start position:0% with GP another woody cancer to please like<00:22:38.700> means<00:22:39.700> global<00:22:40.059> platform<00:22:40.540> since<00:22:40.809> these 00:22:41.840 --> 00:22:41.850 align:start position:0% like means global platform since these 00:22:41.850 --> 00:22:44.600 align:start position:0% like means global platform since these standards 00:22:44.600 --> 00:22:44.610 align:start position:0% standards 00:22:44.610 --> 00:22:48.410 align:start position:0% standards communicate<00:22:45.270> with<00:22:45.570> received<00:22:46.760> become<00:22:47.760> manager 00:22:48.410 --> 00:22:48.420 align:start position:0% communicate with received become manager 00:22:48.420 --> 00:22:50.570 align:start position:0% communicate with received become manager application<00:22:49.170> on<00:22:49.290> the<00:22:49.470> card<00:22:49.740> so<00:22:50.070> is<00:22:50.190> the<00:22:50.370> one 00:22:50.570 --> 00:22:50.580 align:start position:0% application on the card so is the one 00:22:50.580 --> 00:22:52.970 align:start position:0% application on the card so is the one that<00:22:50.850> allows<00:22:51.210> is<00:22:51.600> building<00:22:52.080> without<00:22:52.620> this 00:22:52.970 --> 00:22:52.980 align:start position:0% that allows is building without this 00:22:52.980 --> 00:22:55.419 align:start position:0% that allows is building without this from<00:22:53.250> the<00:22:53.400> cart<00:22:53.670> and<00:22:53.880> is<00:22:54.360> independent<00:22:54.870> from 00:22:55.419 --> 00:22:55.429 align:start position:0% from the cart and is independent from 00:22:55.429 --> 00:22:58.850 align:start position:0% from the cart and is independent from it's<00:22:57.080> implemented<00:22:58.080> in<00:22:58.170> the<00:22:58.320> dark<00:22:58.559> side 00:22:58.850 --> 00:22:58.860 align:start position:0% it's implemented in the dark side 00:22:58.860 --> 00:23:05.600 align:start position:0% it's implemented in the dark side equity<00:22:59.600> yes<00:23:00.600> we<00:23:03.110> -<00:23:04.110> it's<00:23:04.290> all<00:23:04.530> set<00:23:04.860> of<00:23:05.100> comments 00:23:05.600 --> 00:23:05.610 align:start position:0% equity yes we - it's all set of comments 00:23:05.610 --> 00:23:09.020 align:start position:0% equity yes we - it's all set of comments general<00:23:06.390> to<00:23:06.740> interact<00:23:07.740> with<00:23:07.830> monitored<00:23:08.340> and 00:23:09.020 --> 00:23:09.030 align:start position:0% general to interact with monitored and 00:23:09.030 --> 00:23:11.570 align:start position:0% general to interact with monitored and escape<00:23:09.510> which<00:23:09.840> is<00:23:09.870> based<00:23:10.260> because<00:23:10.440> we<00:23:10.770> use<00:23:11.130> we 00:23:11.570 --> 00:23:11.580 align:start position:0% escape which is based because we use we 00:23:11.580 --> 00:23:14.030 align:start position:0% escape which is based because we use we are<00:23:11.610> not<00:23:12.230> interacting<00:23:13.230> yet<00:23:13.410> with<00:23:13.710> the<00:23:13.830> King 00:23:14.030 --> 00:23:14.040 align:start position:0% are not interacting yet with the King 00:23:14.040 --> 00:23:17.330 align:start position:0% are not interacting yet with the King adopted<00:23:14.520> and<00:23:15.150> then<00:23:15.540> we<00:23:15.900> have<00:23:16.110> some<00:23:16.440> key<00:23:16.950> cards 00:23:17.330 --> 00:23:17.340 align:start position:0% adopted and then we have some key cards 00:23:17.340 --> 00:23:20.570 align:start position:0% adopted and then we have some key cards so<00:23:18.090> stuck<00:23:18.299> even<00:23:18.419> think<00:23:18.750> of<00:23:18.870> comments<00:23:19.710> that<00:23:19.890> are 00:23:20.570 --> 00:23:20.580 align:start position:0% so stuck even think of comments that are 00:23:20.580 --> 00:23:27.400 align:start position:0% so stuck even think of comments that are basically<00:23:21.030> just<00:23:21.360> like<00:23:21.960> replacing<00:23:22.650> the<00:23:25.400> X<00:23:26.400> I 00:23:27.400 --> 00:23:27.410 align:start position:0% basically just like replacing the X I 00:23:27.410 --> 00:23:33.220 align:start position:0% basically just like replacing the X I its<00:23:29.660> composition<00:23:30.660> and<00:23:31.500> in<00:23:32.130> this<00:23:32.250> case<00:23:32.490> like 00:23:33.220 --> 00:23:33.230 align:start position:0% its composition and in this case like 00:23:33.230 --> 00:23:37.340 align:start position:0% its composition and in this case like selecting<00:23:35.270> the<00:23:36.270> outlets<00:23:36.630> the<00:23:36.870> keeper<00:23:37.140> gotta 00:23:37.340 --> 00:23:37.350 align:start position:0% selecting the outlets the keeper gotta 00:23:37.350 --> 00:23:39.230 align:start position:0% selecting the outlets the keeper gotta say<00:23:38.010> what<00:23:38.130> you<00:23:38.220> said<00:23:38.400> you<00:23:38.640> can<00:23:38.850> have<00:23:39.000> like 00:23:39.230 --> 00:23:39.240 align:start position:0% say what you said you can have like 00:23:39.240 --> 00:23:42.289 align:start position:0% say what you said you can have like wicked<00:23:39.690> outlets<00:23:40.110> and<00:23:40.320> then<00:23:41.030> like<00:23:42.030> with<00:23:42.179> these 00:23:42.289 --> 00:23:42.299 align:start position:0% wicked outlets and then like with these 00:23:42.299 --> 00:23:45.470 align:start position:0% wicked outlets and then like with these updates<00:23:42.840> something<00:23:43.679> else<00:23:43.860> something<00:23:44.480> special 00:23:45.470 --> 00:23:45.480 align:start position:0% updates something else something special 00:23:45.480 --> 00:23:49.280 align:start position:0% updates something else something special and<00:23:46.040> then<00:23:47.040> we<00:23:47.250> send<00:23:47.970> like<00:23:48.179> the<00:23:48.299> secret<00:23:48.660> so<00:23:49.260> we 00:23:49.280 --> 00:23:49.290 align:start position:0% and then we send like the secret so we 00:23:49.290 --> 00:23:52.130 align:start position:0% and then we send like the secret so we can<00:23:49.530> just<00:23:49.890> for<00:23:50.490> testing<00:23:51.000> using<00:23:51.960> this 00:23:52.130 --> 00:23:52.140 align:start position:0% can just for testing using this 00:23:52.140 --> 00:23:56.900 align:start position:0% can just for testing using this otherwise<00:23:52.710> you<00:23:52.919> can<00:23:53.130> just<00:23:53.960> not<00:23:54.960> specify 00:23:56.900 --> 00:23:56.910 align:start position:0% otherwise you can just not specify 00:23:56.910 --> 00:23:58.130 align:start position:0% otherwise you can just not specify [Music] 00:23:58.130 --> 00:23:58.140 align:start position:0% [Music] 00:23:58.140 --> 00:24:01.340 align:start position:0% [Music] and<00:23:58.290> then<00:23:58.650> he<00:23:59.010> Kathleen<00:23:59.340> eat<00:24:00.140> which<00:24:01.140> is 00:24:01.340 --> 00:24:01.350 align:start position:0% and then he Kathleen eat which is 00:24:01.350 --> 00:24:03.410 align:start position:0% and then he Kathleen eat which is initialized<00:24:01.890> so<00:24:02.370> it's<00:24:02.640> basically<00:24:03.090> saying 00:24:03.410 --> 00:24:03.420 align:start position:0% initialized so it's basically saying 00:24:03.420 --> 00:24:06.340 align:start position:0% initialized so it's basically saying okay<00:24:03.810> so<00:24:04.170> starting<00:24:05.040> from<00:24:05.160> now<00:24:05.430> these<00:24:06.000> are<00:24:06.210> the 00:24:06.340 --> 00:24:06.350 align:start position:0% okay so starting from now these are the 00:24:06.350 --> 00:24:10.790 align:start position:0% okay so starting from now these are the secret<00:24:07.350> and<00:24:08.210> you<00:24:09.210> can<00:24:09.390> use<00:24:09.540> this<00:24:09.720> card<00:24:09.960> only<00:24:10.620> if 00:24:10.790 --> 00:24:10.800 align:start position:0% secret and you can use this card only if 00:24:10.800 --> 00:24:12.650 align:start position:0% secret and you can use this card only if you<00:24:10.950> know<00:24:11.070> deceiver<00:24:11.580> and<00:24:11.850> we<00:24:11.970> prepared<00:24:12.390> with 00:24:12.650 --> 00:24:12.660 align:start position:0% you know deceiver and we prepared with 00:24:12.660 --> 00:24:16.160 align:start position:0% you know deceiver and we prepared with the<00:24:12.750> password<00:24:13.500> in<00:24:13.770> you<00:24:14.460> need<00:24:14.640> to<00:24:14.880> use<00:24:15.780> the<00:24:15.960> pin 00:24:16.160 --> 00:24:16.170 align:start position:0% the password in you need to use the pin 00:24:16.170 --> 00:24:28.280 align:start position:0% the password in you need to use the pin for<00:24:16.530> any<00:24:17.210> signature<00:24:18.210> example<00:24:25.220> so<00:24:27.230> okay<00:24:28.230> so 00:24:28.280 --> 00:24:28.290 align:start position:0% for any signature example so okay so 00:24:28.290 --> 00:24:30.290 align:start position:0% for any signature example so okay so after<00:24:28.560> this 00:24:30.290 --> 00:24:30.300 align:start position:0% after this 00:24:30.300 --> 00:24:33.980 align:start position:0% after this so<00:24:30.750> the<00:24:30.870> key<00:24:31.020> card<00:24:31.260> can<00:24:31.530> be<00:24:31.650> paired<00:24:31.920> with<00:24:32.990> five 00:24:33.980 --> 00:24:33.990 align:start position:0% so the key card can be paired with five 00:24:33.990 --> 00:24:37.520 align:start position:0% so the key card can be paired with five devices<00:24:34.350> five<00:24:34.830> body<00:24:35.250> but<00:24:36.410> certain<00:24:37.410> is<00:24:37.500> that 00:24:37.520 --> 00:24:37.530 align:start position:0% devices five body but certain is that 00:24:37.530 --> 00:24:43.610 align:start position:0% devices five body but certain is that every<00:24:38.100> time<00:24:38.280> you<00:24:38.390> want<00:24:39.390> to<00:24:42.620> interactivity 00:24:43.610 --> 00:24:43.620 align:start position:0% every time you want to interactivity 00:24:43.620 --> 00:24:46.270 align:start position:0% every time you want to interactivity card<00:24:43.860> you<00:24:44.040> need<00:24:44.190> to<00:24:44.340> pair<00:24:44.550> them<00:24:44.820> to<00:24:45.630> be<00:24:45.750> able<00:24:45.840> to 00:24:46.270 --> 00:24:46.280 align:start position:0% card you need to pair them to be able to 00:24:46.280 --> 00:24:50.180 align:start position:0% card you need to pair them to be able to start<00:24:47.280> the<00:24:47.430> pairing<00:24:48.380> comments<00:24:49.380> you<00:24:49.800> need<00:24:50.010> to 00:24:50.180 --> 00:24:50.190 align:start position:0% start the pairing comments you need to 00:24:50.190 --> 00:24:52.370 align:start position:0% start the pairing comments you need to know<00:24:50.370> the<00:24:50.580> the<00:24:50.940> pairing<00:24:51.300> of<00:24:51.330> this<00:24:51.990> one<00:24:52.200> so 00:24:52.370 --> 00:24:52.380 align:start position:0% know the the pairing of this one so 00:24:52.380 --> 00:24:55.730 align:start position:0% know the the pairing of this one so preparing<00:24:52.710> a<00:24:53.390> password<00:24:54.390> and<00:24:54.600> after<00:24:55.260> that<00:24:55.440> you 00:24:55.730 --> 00:24:55.740 align:start position:0% preparing a password and after that you 00:24:55.740 --> 00:24:58.970 align:start position:0% preparing a password and after that you can<00:24:55.980> prepare<00:24:57.140> then<00:24:58.140> opening<00:24:58.530> a<00:24:58.710> secure 00:24:58.970 --> 00:24:58.980 align:start position:0% can prepare then opening a secure 00:24:58.980 --> 00:25:02.210 align:start position:0% can prepare then opening a secure channel<00:24:59.490> and<00:24:59.670> then<00:25:00.420> doing<00:25:01.020> something<00:25:01.110> so<00:25:01.740> this 00:25:02.210 --> 00:25:02.220 align:start position:0% channel and then doing something so this 00:25:02.220 --> 00:25:04.190 align:start position:0% channel and then doing something so this skill<00:25:02.520> is<00:25:02.790> basically<00:25:03.150> not<00:25:03.420> doing<00:25:03.660> anything<00:25:03.930> so 00:25:04.190 --> 00:25:04.200 align:start position:0% skill is basically not doing anything so 00:25:04.200 --> 00:25:06.680 align:start position:0% skill is basically not doing anything so it's<00:25:04.350> pairing<00:25:04.770> open<00:25:05.580> a<00:25:05.760> secure<00:25:05.940> channel<00:25:06.510> and 00:25:06.680 --> 00:25:06.690 align:start position:0% it's pairing open a secure channel and 00:25:06.690 --> 00:25:09.620 align:start position:0% it's pairing open a secure channel and then<00:25:07.080> I'm<00:25:07.440> paying<00:25:07.830> and<00:25:08.160> I'm<00:25:08.640> doing<00:25:09.450> this 00:25:09.620 --> 00:25:09.630 align:start position:0% then I'm paying and I'm doing this 00:25:09.630 --> 00:25:11.540 align:start position:0% then I'm paying and I'm doing this unfair<00:25:10.200> just<00:25:10.560> because<00:25:10.860> otherwise<00:25:11.100> I 00:25:11.540 --> 00:25:11.550 align:start position:0% unfair just because otherwise I 00:25:11.550 --> 00:25:13.910 align:start position:0% unfair just because otherwise I basically<00:25:12.090> used<00:25:12.420> one<00:25:12.750> of<00:25:12.780> the<00:25:13.140> swats<00:25:13.530> for<00:25:13.830> the 00:25:13.910 --> 00:25:13.920 align:start position:0% basically used one of the swats for the 00:25:13.920 --> 00:25:14.840 align:start position:0% basically used one of the swats for the parent 00:25:14.840 --> 00:25:14.850 align:start position:0% parent 00:25:14.850 --> 00:25:17.530 align:start position:0% parent time<00:25:15.060> you<00:25:15.690> use<00:25:15.900> another<00:25:16.230> one<00:25:16.410> another<00:25:16.710> five 00:25:17.530 --> 00:25:17.540 align:start position:0% time you use another one another five 00:25:17.540 --> 00:25:21.860 align:start position:0% time you use another one another five you<00:25:18.540> know<00:25:18.690> a<00:25:18.960> bourbon<00:25:19.680> in<00:25:19.800> there<00:25:20.300> and<00:25:21.300> then<00:25:21.600> I'm 00:25:21.860 --> 00:25:21.870 align:start position:0% you know a bourbon in there and then I'm 00:25:21.870 --> 00:25:25.700 align:start position:0% you know a bourbon in there and then I'm just<00:25:21.930> using<00:25:22.170> verify<00:25:22.860> thing<00:25:23.070> because<00:25:23.430> for<00:25:24.710> some 00:25:25.700 --> 00:25:25.710 align:start position:0% just using verify thing because for some 00:25:25.710 --> 00:25:27.980 align:start position:0% just using verify thing because for some comments<00:25:26.220> verified<00:25:27.030> opinion<00:25:27.480> for<00:25:27.630> example 00:25:27.980 --> 00:25:27.990 align:start position:0% comments verified opinion for example 00:25:27.990 --> 00:25:30.050 align:start position:0% comments verified opinion for example before<00:25:28.290> signing<00:25:28.800> a<00:25:29.010> transaction<00:25:29.610> or<00:25:29.760> in 00:25:30.050 --> 00:25:30.060 align:start position:0% before signing a transaction or in 00:25:30.060 --> 00:25:35.960 align:start position:0% before signing a transaction or in general<00:25:31.880> so<00:25:33.530> of<00:25:34.530> course<00:25:34.740> when<00:25:34.980> you<00:25:35.130> you<00:25:35.730> don't 00:25:35.960 --> 00:25:35.970 align:start position:0% general so of course when you you don't 00:25:35.970 --> 00:25:38.360 align:start position:0% general so of course when you you don't need<00:25:36.180> to<00:25:36.330> pair<00:25:36.570> every<00:25:36.750> time<00:25:37.110> you<00:25:37.350> use<00:25:38.190> the 00:25:38.360 --> 00:25:38.370 align:start position:0% need to pair every time you use the 00:25:38.370 --> 00:25:40.880 align:start position:0% need to pair every time you use the kicker<00:25:38.810> for<00:25:39.810> example<00:25:40.200> when<00:25:40.350> you<00:25:40.500> when<00:25:40.800> you 00:25:40.880 --> 00:25:40.890 align:start position:0% kicker for example when you when you 00:25:40.890 --> 00:25:45.380 align:start position:0% kicker for example when you when you have<00:25:41.130> a<00:25:43.100> lighter<00:25:44.100> foundation<00:25:44.310> we<00:25:44.940> just<00:25:45.150> felt 00:25:45.380 --> 00:25:45.390 align:start position:0% have a lighter foundation we just felt 00:25:45.390 --> 00:25:48.950 align:start position:0% have a lighter foundation we just felt the<00:25:45.480> first<00:25:45.660> time<00:25:45.810> and<00:25:46.260> then<00:25:47.330> with<00:25:48.330> the<00:25:48.480> pairing 00:25:48.950 --> 00:25:48.960 align:start position:0% the first time and then with the pairing 00:25:48.960 --> 00:25:51.710 align:start position:0% the first time and then with the pairing essentially<00:25:49.800> making<00:25:50.670> a<00:25:50.940> key<00:25:51.120> and<00:25:51.390> that<00:25:51.420> key 00:25:51.710 --> 00:25:51.720 align:start position:0% essentially making a key and that key 00:25:51.720 --> 00:25:53.720 align:start position:0% essentially making a key and that key you<00:25:52.410> can<00:25:52.560> store<00:25:52.830> it<00:25:52.920> in<00:25:53.010> the<00:25:53.160> phone<00:25:53.370> and<00:25:53.550> you 00:25:53.720 --> 00:25:53.730 align:start position:0% you can store it in the phone and you 00:25:53.730 --> 00:26:00.080 align:start position:0% you can store it in the phone and you use<00:25:53.940> it<00:25:53.970> at<00:25:54.270> the<00:25:54.390> time<00:25:58.640> so<00:25:59.640> it's<00:25:59.790> basically 00:26:00.080 --> 00:26:00.090 align:start position:0% use it at the time so it's basically 00:26:00.090 --> 00:26:02.150 align:start position:0% use it at the time so it's basically once<00:26:00.540> for<00:26:01.020> each<00:26:01.050> device<00:26:01.500> that<00:26:01.800> you<00:26:01.890> want<00:26:01.980> to 00:26:02.150 --> 00:26:02.160 align:start position:0% once for each device that you want to 00:26:02.160 --> 00:26:10.130 align:start position:0% once for each device that you want to pair<00:26:03.050> and<00:26:04.820> yeah<00:26:05.820> so<00:26:06.120> these<00:26:07.020> are<00:26:08.600> scripted<00:26:09.600> runs 00:26:10.130 --> 00:26:10.140 align:start position:0% pair and yeah so these are scripted runs 00:26:10.140 --> 00:26:20.030 align:start position:0% pair and yeah so these are scripted runs this<00:26:11.070> one<00:26:11.310> is<00:26:11.460> the<00:26:11.760> number<00:26:14.570> this<00:26:18.740> and<00:26:19.740> it's 00:26:20.030 --> 00:26:20.040 align:start position:0% this one is the number this and it's 00:26:20.040 --> 00:26:25.190 align:start position:0% this one is the number this and it's just<00:26:20.130> getting<00:26:20.610> the<00:26:21.000> stages<00:26:21.510> of<00:26:21.780> the<00:26:24.200> same 00:26:25.190 --> 00:26:25.200 align:start position:0% just getting the stages of the same 00:26:25.200 --> 00:26:27.860 align:start position:0% just getting the stages of the same thing<00:26:25.440> that<00:26:25.470> we<00:26:25.830> had<00:26:26.340> before<00:26:26.640> so<00:26:27.450> if<00:26:27.690> it's 00:26:27.860 --> 00:26:27.870 align:start position:0% thing that we had before so if it's 00:26:27.870 --> 00:26:29.600 align:start position:0% thing that we had before so if it's installed<00:26:28.290> it's<00:26:28.620> initialized<00:26:29.250> and 00:26:29.600 --> 00:26:29.610 align:start position:0% installed it's initialized and 00:26:29.610 --> 00:26:32.210 align:start position:0% installed it's initialized and everything<00:26:29.970> and<00:26:30.120> we<00:26:30.630> can<00:26:30.870> still<00:26:31.200> the<00:26:31.800> parent 00:26:32.210 --> 00:26:32.220 align:start position:0% everything and we can still the parent 00:26:32.220 --> 00:26:37.280 align:start position:0% everything and we can still the parent which<00:26:32.670> is<00:26:32.850> the<00:26:33.000> one<00:26:33.180> gets<00:26:33.450> really<00:26:33.750> used 00:26:37.280 --> 00:26:37.290 align:start position:0% 00:26:37.290 --> 00:26:40.700 align:start position:0% in<00:26:37.350> session<00:26:38.280> and<00:26:38.520> then<00:26:38.880> the<00:26:39.480> pilots<00:26:39.929> ride 00:26:40.700 --> 00:26:40.710 align:start position:0% in session and then the pilots ride 00:26:40.710 --> 00:26:43.600 align:start position:0% in session and then the pilots ride so<00:26:41.130> it<00:26:41.280> I<00:26:41.429> designed<00:26:41.820> you<00:26:42.000> so<00:26:42.570> you<00:26:42.660> can<00:26:42.870> you<00:26:43.200> can 00:26:43.600 --> 00:26:43.610 align:start position:0% so it I designed you so you can you can 00:26:43.610 --> 00:26:46.400 align:start position:0% so it I designed you so you can you can put<00:26:44.610> their<00:26:44.760> own<00:26:44.880> pitiful<00:26:45.419> times<00:26:45.750> otherwise 00:26:46.400 --> 00:26:46.410 align:start position:0% put their own pitiful times otherwise 00:26:46.410 --> 00:26:49.430 align:start position:0% put their own pitiful times otherwise then<00:26:46.790> you<00:26:47.790> need<00:26:47.910> to<00:26:48.030> use<00:26:48.179> the<00:26:48.390> book<00:26:48.570> to<00:26:48.600> read 00:26:49.430 --> 00:26:49.440 align:start position:0% then you need to use the book to read 00:26:49.440 --> 00:26:55.159 align:start position:0% then you need to use the book to read Isha<00:26:49.710> lies<00:26:49.860> the<00:26:50.010> pain<00:26:50.220> and<00:26:51.770> so<00:26:52.770> if<00:26:52.950> we<00:26:54.020> so<00:26:55.020> at 00:26:55.159 --> 00:26:55.169 align:start position:0% Isha lies the pain and so if we so at 00:26:55.169 --> 00:26:59.530 align:start position:0% Isha lies the pain and so if we so at this<00:26:55.290> point<00:26:56.690> the<00:26:57.690> key<00:26:58.320> card<00:26:58.559> is<00:26:58.679> initialized 00:26:59.530 --> 00:26:59.540 align:start position:0% this point the key card is initialized 00:26:59.540 --> 00:27:02.000 align:start position:0% this point the key card is initialized but<00:27:00.540> it<00:27:00.690> doesn't<00:27:00.990> tell<00:27:01.140> the<00:27:01.260> master<00:27:01.559> key 00:27:02.000 --> 00:27:02.010 align:start position:0% but it doesn't tell the master key 00:27:02.010 --> 00:27:04.940 align:start position:0% but it doesn't tell the master key so<00:27:02.669> there's<00:27:03.030> another<00:27:03.270> comment<00:27:03.630> that<00:27:04.049> you<00:27:04.770> use 00:27:04.940 --> 00:27:04.950 align:start position:0% so there's another comment that you use 00:27:04.950 --> 00:27:08.390 align:start position:0% so there's another comment that you use which<00:27:05.460> is<00:27:05.669> generate<00:27:06.210> the<00:27:06.330> key<00:27:06.450> and<00:27:07.220> this<00:27:08.220> one 00:27:08.390 --> 00:27:08.400 align:start position:0% which is generate the key and this one 00:27:08.400 --> 00:27:11.150 align:start position:0% which is generate the key and this one is<00:27:08.460> basically<00:27:08.820> generating<00:27:09.419> the<00:27:09.540> key<00:27:10.160> inside 00:27:11.150 --> 00:27:11.160 align:start position:0% is basically generating the key inside 00:27:11.160 --> 00:27:13.820 align:start position:0% is basically generating the key inside the<00:27:11.280> card<00:27:11.490> and<00:27:12.120> then<00:27:12.929> which<00:27:13.410> is<00:27:13.559> basically 00:27:13.820 --> 00:27:13.830 align:start position:0% the card and then which is basically 00:27:13.830 --> 00:27:17.210 align:start position:0% the card and then which is basically diversity<00:27:14.429> there<00:27:15.390> are<00:27:15.510> the<00:27:15.750> wage<00:27:15.929> man<00:27:16.260> so<00:27:16.980> here 00:27:17.210 --> 00:27:17.220 align:start position:0% diversity there are the wage man so here 00:27:17.220 --> 00:27:20.990 align:start position:0% diversity there are the wage man so here like<00:27:17.460> a<00:27:17.520> Misaki<00:27:18.210> in<00:27:18.270> the<00:27:18.390> card<00:27:19.760> majority<00:27:20.760> on 00:27:20.990 --> 00:27:21.000 align:start position:0% like a Misaki in the card majority on 00:27:21.000 --> 00:27:21.620 align:start position:0% like a Misaki in the card majority on the<00:27:21.150> card 00:27:21.620 --> 00:27:21.630 align:start position:0% the card 00:27:21.630 --> 00:27:24.470 align:start position:0% the card cuff<00:27:22.049> but<00:27:22.470> you<00:27:22.559> can<00:27:22.799> upload<00:27:23.130> it<00:27:23.340> or<00:27:23.580> you<00:27:24.240> cannot 00:27:24.470 --> 00:27:24.480 align:start position:0% cuff but you can upload it or you cannot 00:27:24.480 --> 00:27:29.020 align:start position:0% cuff but you can upload it or you cannot blow<00:27:24.720> they<00:27:24.929> think<00:27:25.260> the<00:27:25.530> indexes<00:27:26.100> of<00:27:26.130> a<00:27:26.400> pbs39 00:27:29.020 --> 00:27:29.030 align:start position:0% blow they think the indexes of a pbs39 00:27:29.030 --> 00:27:32.330 align:start position:0% blow they think the indexes of a pbs39 phrase<00:27:30.030> and<00:27:30.600> then<00:27:31.350> the<00:27:31.500> card<00:27:31.710> is<00:27:31.860> told<00:27:32.130> in<00:27:32.309> the 00:27:32.330 --> 00:27:32.340 align:start position:0% phrase and then the card is told in the 00:27:32.340 --> 00:27:35.810 align:start position:0% phrase and then the card is told in the in<00:27:33.000> the<00:27:33.620> card<00:27:34.620> and<00:27:34.830> then<00:27:35.010> you<00:27:35.070> can<00:27:35.309> start<00:27:35.640> using 00:27:35.810 --> 00:27:35.820 align:start position:0% in the card and then you can start using 00:27:35.820 --> 00:27:41.360 align:start position:0% in the card and then you can start using it<00:27:36.559> so<00:27:38.780> yeah<00:27:39.780> you<00:27:39.929> have<00:27:39.990> any<00:27:40.290> question<00:27:40.620> also 00:27:41.360 --> 00:27:41.370 align:start position:0% it so yeah you have any question also 00:27:41.370 --> 00:27:54.500 align:start position:0% it so yeah you have any question also like<00:27:41.640> if<00:27:41.880> you<00:27:42.030> have<00:27:42.120> problems 00:27:54.500 --> 00:27:54.510 align:start position:0% 00:27:54.510 --> 00:28:02.090 align:start position:0% [Music] 00:28:02.090 --> 00:28:02.100 align:start position:0% 00:28:02.100 --> 00:28:23.340 align:start position:0% it's<00:28:03.100> not<00:28:20.310> all<00:28:21.310> the<00:28:21.760> ships<00:28:22.270> on<00:28:22.600> the<00:28:22.840> market 00:28:23.340 --> 00:28:23.350 align:start position:0% it's not all the ships on the market 00:28:23.350 --> 00:28:26.370 align:start position:0% it's not all the ships on the market they<00:28:23.980> support<00:28:24.490> the<00:28:25.090> course<00:28:25.420> defined<00:28:25.960> in<00:28:26.200> the 00:28:26.370 --> 00:28:26.380 align:start position:0% they support the course defined in the 00:28:26.380 --> 00:28:29.390 align:start position:0% they support the course defined in the Java<00:28:26.650> car<00:28:26.860> specification<00:28:27.700> and<00:28:28.390> so<00:28:28.810> they 00:28:29.390 --> 00:28:29.400 align:start position:0% Java car specification and so they 00:28:29.400 --> 00:28:33.660 align:start position:0% Java car specification and so they define<00:28:30.400> the<00:28:31.030> FP<00:28:31.600> course<00:28:32.200> and<00:28:32.500> like<00:28:32.920> the<00:28:33.220> SEC 00:28:33.660 --> 00:28:33.670 align:start position:0% define the FP course and like the SEC 00:28:33.670 --> 00:28:37.920 align:start position:0% define the FP course and like the SEC the<00:28:33.970> Tongass<00:28:34.420> for<00:28:35.290> ATM<00:28:35.860> yes<00:28:36.360> because<00:28:37.360> of<00:28:37.750> the 00:28:37.920 --> 00:28:37.930 align:start position:0% the Tongass for ATM yes because of the 00:28:37.930 --> 00:28:51.800 align:start position:0% the Tongass for ATM yes because of the policies<00:28:38.320> of<00:28:38.440> habit<00:28:38.770> you<00:28:38.920> know 00:28:51.800 --> 00:28:51.810 align:start position:0% 00:28:51.810 --> 00:29:06.400 align:start position:0% [Music] 00:29:06.400 --> 00:29:06.410 align:start position:0% 00:29:06.410 --> 00:29:48.350 align:start position:0% because<00:29:07.410> of<00:29:07.620> the<00:29:09.620> I<00:29:10.620> mean<00:29:27.770> because<00:29:47.360> before 00:29:48.350 --> 00:29:48.360 align:start position:0% because of the I mean because before 00:29:48.360 --> 00:29:50.750 align:start position:0% because of the I mean because before this<00:29:48.860> for<00:29:49.860> months 00:29:50.750 --> 00:29:50.760 align:start position:0% this for months 00:29:50.760 --> 00:29:53.480 align:start position:0% this for months something<00:29:51.390> that<00:29:51.630> didn't<00:29:52.380> put<00:29:52.650> accent<00:29:53.190> is<00:29:53.370> that 00:29:53.480 --> 00:29:53.490 align:start position:0% something that didn't put accent is that 00:29:53.490 --> 00:29:56.870 align:start position:0% something that didn't put accent is that there<00:29:53.850> is<00:29:54.440> also<00:29:55.440> a<00:29:55.650> sort<00:29:56.040> of<00:29:56.070> acetyl<00:29:56.490> channel 00:29:56.870 --> 00:29:56.880 align:start position:0% there is also a sort of acetyl channel 00:29:56.880 --> 00:30:00.080 align:start position:0% there is also a sort of acetyl channel and<00:29:57.120> it<00:29:57.240> has<00:29:57.360> a<00:29:57.390> key<00:29:57.830> the<00:29:58.830> issue<00:29:59.370> of<00:29:59.610> nose 00:30:00.080 --> 00:30:00.090 align:start position:0% and it has a key the issue of nose 00:30:00.090 --> 00:30:02.299 align:start position:0% and it has a key the issue of nose deceive<00:30:00.540> what's<00:30:00.780> the<00:30:00.900> toy<00:30:01.020> so<00:30:01.800> when<00:30:02.010> they<00:30:02.130> sell 00:30:02.299 --> 00:30:02.309 align:start position:0% deceive what's the toy so when they sell 00:30:02.309 --> 00:30:05.090 align:start position:0% deceive what's the toy so when they sell you<00:30:02.460> the<00:30:02.610> card<00:30:02.850> you<00:30:03.000> don't<00:30:03.179> know<00:30:03.360> the<00:30:04.040> so<00:30:05.040> you 00:30:05.090 --> 00:30:05.100 align:start position:0% you the card you don't know the so you 00:30:05.100 --> 00:30:12.150 align:start position:0% you the card you don't know the so you cannot<00:30:05.490> but<00:30:06.559> is<00:30:07.559> actually<00:30:08.010> not<00:30:10.250> really 00:30:12.150 --> 00:30:12.160 align:start position:0% cannot but is actually not really 00:30:12.160 --> 00:30:16.110 align:start position:0% cannot but is actually not really I'm<00:30:12.790> out<00:30:12.940> this<00:30:14.730> yep<00:30:15.730> it<00:30:15.910> with 00:30:16.110 --> 00:30:16.120 align:start position:0% I'm out this yep it with 00:30:16.120 --> 00:30:19.770 align:start position:0% I'm out this yep it with the<00:30:16.330> one<00:30:16.540> that<00:30:17.020> we<00:30:17.310> distributed<00:30:18.310> now<00:30:18.630> so<00:30:19.630> they 00:30:19.770 --> 00:30:19.780 align:start position:0% the one that we distributed now so they 00:30:19.780 --> 00:30:25.380 align:start position:0% the one that we distributed now so they have<00:30:19.990> the<00:30:20.170> test<00:30:20.410> keys<00:30:22.560> the<00:30:23.560> one<00:30:24.490> blue<00:30:24.790> that<00:30:25.150> we 00:30:25.380 --> 00:30:25.390 align:start position:0% have the test keys the one blue that we 00:30:25.390 --> 00:30:28.440 align:start position:0% have the test keys the one blue that we combine<00:30:25.960> they<00:30:26.950> have<00:30:27.220> a<00:30:27.250> different<00:30:27.880> key<00:30:28.120> but<00:30:28.420> I 00:30:28.440 --> 00:30:28.450 align:start position:0% combine they have a different key but I 00:30:28.450 --> 00:30:30.660 align:start position:0% combine they have a different key but I still<00:30:28.690> know<00:30:28.900> having<00:30:29.380> things<00:30:29.620> like<00:30:30.160> the<00:30:30.370> key 00:30:30.660 --> 00:30:30.670 align:start position:0% still know having things like the key 00:30:30.670 --> 00:30:34.320 align:start position:0% still know having things like the key card<00:30:30.910> keys<00:30:31.500> offender<00:30:32.500> I<00:30:32.740> mean<00:30:33.070> for<00:30:33.640> the<00:30:33.790> final 00:30:34.320 --> 00:30:34.330 align:start position:0% card keys offender I mean for the final 00:30:34.330 --> 00:30:37.410 align:start position:0% card keys offender I mean for the final release<00:30:34.510> maybe<00:30:35.410> we<00:30:35.650> would<00:30:35.860> generate<00:30:36.700> as<00:30:37.180> no 00:30:37.410 --> 00:30:37.420 align:start position:0% release maybe we would generate as no 00:30:37.420 --> 00:30:51.140 align:start position:0% release maybe we would generate as no random<00:30:37.810> key<00:30:38.020> so<00:30:38.860> that<00:30:38.890> it's<00:30:39.490> possible<00:30:40.210> to 00:30:51.140 --> 00:30:51.150 align:start position:0% 00:30:51.150 --> 00:31:12.510 align:start position:0% change<00:30:53.190> on<00:30:54.190> your<00:30:54.340> device<00:31:10.860> remaining<00:31:11.860> because 00:31:12.510 --> 00:31:12.520 align:start position:0% change on your device remaining because 00:31:12.520 --> 00:31:15.390 align:start position:0% change on your device remaining because actually<00:31:13.150> the<00:31:13.480> Yubikey<00:31:14.440> uses<00:31:14.980> the<00:31:15.190> same 00:31:15.390 --> 00:31:15.400 align:start position:0% actually the Yubikey uses the same 00:31:15.400 --> 00:31:17.100 align:start position:0% actually the Yubikey uses the same protocol<00:31:15.970> so<00:31:16.300> the<00:31:16.480> same<00:31:16.750> communication 00:31:17.100 --> 00:31:17.110 align:start position:0% protocol so the same communication 00:31:17.110 --> 00:31:20.580 align:start position:0% protocol so the same communication protocol<00:31:17.980> so<00:31:18.550> actually<00:31:19.060> it's<00:31:19.590> implementation 00:31:20.580 --> 00:31:20.590 align:start position:0% protocol so actually it's implementation 00:31:20.590 --> 00:31:23.700 align:start position:0% protocol so actually it's implementation will<00:31:20.770> be<00:31:20.920> done<00:31:21.100> for<00:31:21.310> Java<00:31:21.640> path<00:31:21.940> but<00:31:22.710> porting 00:31:23.700 --> 00:31:23.710 align:start position:0% will be done for Java path but porting 00:31:23.710 --> 00:31:26.130 align:start position:0% will be done for Java path but porting this<00:31:24.010> to<00:31:24.310> the<00:31:24.430> UPR<00:31:24.910> clearly<00:31:25.450> did<00:31:25.630> something 00:31:26.130 --> 00:31:26.140 align:start position:0% this to the UPR clearly did something 00:31:26.140 --> 00:31:31.290 align:start position:0% this to the UPR clearly did something which<00:31:26.260> is<00:31:26.590> no<00:31:29.460> no<00:31:30.460> question<00:31:30.820> is<00:31:30.940> programmed 00:31:31.290 --> 00:31:31.300 align:start position:0% which is no no question is programmed 00:31:31.300 --> 00:31:32.850 align:start position:0% which is no no question is programmed with<00:31:31.360> like<00:31:31.630> mmm 00:31:32.850 --> 00:31:32.860 align:start position:0% with like mmm 00:31:32.860 --> 00:31:36.090 align:start position:0% with like mmm he<00:31:33.010> carved<00:31:33.490> our<00:31:34.950> personal 00:31:36.090 --> 00:31:36.100 align:start position:0% he carved our personal 00:31:36.100 --> 00:31:39.670 align:start position:0% he carved our personal [Music] 00:31:39.670 --> 00:31:39.680 align:start position:0% 00:31:39.680 --> 00:31:47.520 align:start position:0% [Applause] 00:31:47.520 --> 00:31:47.530 align:start position:0% 00:31:47.530 --> 00:31:50.970 align:start position:0% I<00:31:47.850> don't<00:31:48.850> know<00:31:48.970> so<00:31:49.480> if<00:31:49.570> you<00:31:49.780> can<00:31:50.470> use<00:31:50.620> the<00:31:50.770> same 00:31:50.970 --> 00:31:50.980 align:start position:0% I don't know so if you can use the same 00:31:50.980 --> 00:31:56.250 align:start position:0% I don't know so if you can use the same applet<00:31:51.400> on<00:31:52.180> that<00:31:52.690> card<00:31:53.610> and<00:31:54.750> if<00:31:55.750> it's<00:31:56.050> like 00:31:56.250 --> 00:31:56.260 align:start position:0% applet on that card and if it's like 00:31:56.260 --> 00:31:58.020 align:start position:0% applet on that card and if it's like something<00:31:56.500> over<00:31:56.890> so<00:31:57.100> so<00:31:57.370> at<00:31:57.550> least<00:31:57.760> that<00:31:57.910> you 00:31:58.020 --> 00:31:58.030 align:start position:0% something over so so at least that you 00:31:58.030 --> 00:32:00.600 align:start position:0% something over so so at least that you can<00:31:58.270> know<00:31:58.540> that<00:31:58.620> as<00:31:59.620> far<00:31:59.860> as<00:31:59.890> I<00:32:00.040> know<00:32:00.190> we<00:32:00.310> can't 00:32:00.600 --> 00:32:00.610 align:start position:0% can know that as far as I know we can't 00:32:00.610 --> 00:32:03.080 align:start position:0% can know that as far as I know we can't extract<00:32:01.420> the<00:32:01.690> private<00:32:02.350> key<00:32:02.560> from<00:32:02.950> the 00:32:03.080 --> 00:32:03.090 align:start position:0% extract the private key from the 00:32:03.090 --> 00:32:05.640 align:start position:0% extract the private key from the Estonian<00:32:04.090> citizenship<00:32:04.870> program<00:32:05.290> like<00:32:05.500> the 00:32:05.640 --> 00:32:05.650 align:start position:0% Estonian citizenship program like the 00:32:05.650 --> 00:32:08.310 align:start position:0% Estonian citizenship program like the government<00:32:06.040> knows<00:32:06.160> it<00:32:06.340> but<00:32:06.490> you<00:32:06.520> can't<00:32:07.320> damage 00:32:08.310 --> 00:32:08.320 align:start position:0% government knows it but you can't damage 00:32:08.320 --> 00:32:11.160 align:start position:0% government knows it but you can't damage it<00:32:09.090> so<00:32:10.090> they<00:32:10.210> are<00:32:10.240> you<00:32:10.390> can<00:32:10.630> run<00:32:10.870> but<00:32:11.110> you 00:32:11.160 --> 00:32:11.170 align:start position:0% it so they are you can run but you 00:32:11.170 --> 00:32:16.710 align:start position:0% it so they are you can run but you cannot<00:32:11.590> play<00:32:12.130> with<00:32:12.160> the<00:32:12.550> keys<00:32:14.520> so<00:32:15.520> is<00:32:15.790> there<00:32:16.060> a 00:32:16.710 --> 00:32:16.720 align:start position:0% cannot play with the keys so is there a 00:32:16.720 --> 00:32:23.130 align:start position:0% cannot play with the keys so is there a ah<00:32:19.380> this<00:32:20.380> is<00:32:20.530> secure<00:32:20.920> element<00:32:21.070> this<00:32:22.140> basically 00:32:23.130 --> 00:32:23.140 align:start position:0% ah this is secure element this basically 00:32:23.140 --> 00:32:29.919 align:start position:0% ah this is secure element this basically is<00:32:23.320> what<00:32:23.680> is<00:32:23.860> useful 00:32:29.919 --> 00:32:29.929 align:start position:0% 00:32:29.929 --> 00:32:35.000 align:start position:0% all<00:32:30.929> this<00:32:31.580> happens<00:32:32.750> the<00:32:33.750> applets<00:32:34.110> are<00:32:34.320> emitted 00:32:35.000 --> 00:32:35.010 align:start position:0% all this happens the applets are emitted 00:32:35.010 --> 00:32:37.280 align:start position:0% all this happens the applets are emitted by<00:32:35.250> the<00:32:35.309> when<00:32:36.150> the<00:32:36.270> chips<00:32:36.510> over<00:32:36.780> it<00:32:36.990> but<00:32:37.260> a 00:32:37.280 --> 00:32:37.290 align:start position:0% by the when the chips over it but a 00:32:37.290 --> 00:32:47.600 align:start position:0% by the when the chips over it but a model<00:32:37.559> itself<00:32:44.600> the<00:32:45.600> key<00:32:45.840> as<00:32:46.559> we<00:32:46.799> say<00:32:47.040> the<00:32:47.100> key 00:32:47.600 --> 00:32:47.610 align:start position:0% model itself the key as we say the key 00:32:47.610 --> 00:32:51.850 align:start position:0% model itself the key as we say the key is<00:32:47.809> fixed<00:32:48.809> so<00:32:49.169> it's<00:32:49.320> actually<00:32:49.650> a<00:32:50.309> user<00:32:50.700> notice 00:32:51.850 --> 00:32:51.860 align:start position:0% is fixed so it's actually a user notice 00:32:51.860 --> 00:32:54.799 align:start position:0% is fixed so it's actually a user notice but<00:32:52.860> then<00:32:53.160> the<00:32:53.340> user<00:32:53.520> can<00:32:53.669> change<00:32:54.090> it<00:32:54.330> so<00:32:54.660> they 00:32:54.799 --> 00:32:54.809 align:start position:0% but then the user can change it so they 00:32:54.809 --> 00:32:58.610 align:start position:0% but then the user can change it so they can<00:32:55.080> change<00:32:55.590> the<00:32:55.799> key<00:32:56.370> to<00:32:56.669> load<00:32:56.940> applets<00:32:57.620> that 00:32:58.610 --> 00:32:58.620 align:start position:0% can change the key to load applets that 00:32:58.620 --> 00:33:00.770 align:start position:0% can change the key to load applets that nobody<00:32:58.980> else<00:32:59.160> can<00:32:59.520> they<00:33:00.090> move<00:33:00.299> towards 00:33:00.770 --> 00:33:00.780 align:start position:0% nobody else can they move towards 00:33:00.780 --> 00:33:03.740 align:start position:0% nobody else can they move towards Columbus<00:33:01.110> on<00:33:01.530> their<00:33:01.710> chart<00:33:02.040> step<00:33:02.419> so<00:33:03.419> we<00:33:03.540> don't 00:33:03.740 --> 00:33:03.750 align:start position:0% Columbus on their chart step so we don't 00:33:03.750 --> 00:33:06.440 align:start position:0% Columbus on their chart step so we don't want<00:33:03.929> to<00:33:04.350> manage<00:33:04.710> this<00:33:05.090> centrally<00:33:06.090> on<00:33:06.270> our 00:33:06.440 --> 00:33:06.450 align:start position:0% want to manage this centrally on our 00:33:06.450 --> 00:33:08.419 align:start position:0% want to manage this centrally on our side<00:33:06.900> we<00:33:07.290> want<00:33:07.470> that<00:33:07.740> the<00:33:07.860> user<00:33:08.040> has<00:33:08.280> the 00:33:08.419 --> 00:33:08.429 align:start position:0% side we want that the user has the 00:33:08.429 --> 00:33:11.110 align:start position:0% side we want that the user has the ability<00:33:08.490> to<00:33:09.090> load<00:33:09.270> other<00:33:09.510> oppressed<00:33:10.169> them 00:33:11.110 --> 00:33:11.120 align:start position:0% ability to load other oppressed them 00:33:11.120 --> 00:33:30.230 align:start position:0% ability to load other oppressed them what<00:33:12.120> they<00:33:12.270> what<00:33:12.480> they<00:33:12.600> won't<00:33:12.809> be 00:33:30.230 --> 00:33:30.240 align:start position:0% 00:33:30.240 --> 00:33:48.749 align:start position:0% okay<00:33:31.590> do<00:33:32.590> you<00:33:32.620> have<00:33:32.740> any<00:33:32.919> other<00:33:33.039> question<00:33:47.759> okay 00:33:48.749 --> 00:33:48.759 align:start position:0% okay do you have any other question okay 00:33:48.759 --> 00:33:51.149 align:start position:0% okay do you have any other question okay so<00:33:48.789> now<00:33:49.179> we<00:33:50.019> came<00:33:50.139> to<00:33:50.200> the<00:33:50.409> read<00:33:50.529> the<00:33:50.649> key<00:33:50.830> so<00:33:51.070> we 00:33:51.149 --> 00:33:51.159 align:start position:0% so now we came to the read the key so we 00:33:51.159 --> 00:33:54.600 align:start position:0% so now we came to the read the key so we can<00:33:51.340> still<00:33:52.090> use<00:33:52.120> the<00:33:52.570> che<00:33:53.110> comments<00:33:53.710> and<00:33:53.919> use 00:33:54.600 --> 00:33:54.610 align:start position:0% can still use the che comments and use 00:33:54.610 --> 00:33:57.960 align:start position:0% can still use the che comments and use the<00:33:55.110> script<00:33:56.110> number<00:33:56.440> five<00:33:56.740> and<00:33:57.370> it's 00:33:57.960 --> 00:33:57.970 align:start position:0% the script number five and it's 00:33:57.970 --> 00:34:00.090 align:start position:0% the script number five and it's basically<00:33:58.269> just<00:33:58.389> doing<00:33:58.929> the<00:33:59.049> same<00:33:59.259> that<00:33:59.559> we<00:33:59.710> do 00:34:00.090 --> 00:34:00.100 align:start position:0% basically just doing the same that we do 00:34:00.100 --> 00:34:03.110 align:start position:0% basically just doing the same that we do before<00:34:00.309> so<00:34:01.090> it's<00:34:01.500> selecting<00:34:02.500> the<00:34:02.620> applets 00:34:03.110 --> 00:34:03.120 align:start position:0% before so it's selecting the applets 00:34:03.120 --> 00:34:06.350 align:start position:0% before so it's selecting the applets setting<00:34:04.120> their<00:34:04.299> secrets<00:34:04.870> to<00:34:04.990> be<00:34:05.409> able<00:34:05.500> to 00:34:06.350 --> 00:34:06.360 align:start position:0% setting their secrets to be able to 00:34:06.360 --> 00:34:08.970 align:start position:0% setting their secrets to be able to pairing<00:34:07.360> and<00:34:07.629> open<00:34:07.960> the<00:34:08.200> secure<00:34:08.500> channel 00:34:08.970 --> 00:34:08.980 align:start position:0% pairing and open the secure channel 00:34:08.980 --> 00:34:13.290 align:start position:0% pairing and open the secure channel verified<00:34:09.339> to<00:34:09.639> be<00:34:09.669> tipping<00:34:10.619> so<00:34:11.619> that<00:34:12.300> because 00:34:13.290 --> 00:34:13.300 align:start position:0% verified to be tipping so that because 00:34:13.300 --> 00:34:15.720 align:start position:0% verified to be tipping so that because it's<00:34:13.480> it's<00:34:13.929> like<00:34:14.319> regenerating<00:34:15.250> that<00:34:15.399> the<00:34:15.520> key 00:34:15.720 --> 00:34:15.730 align:start position:0% it's it's like regenerating that the key 00:34:15.730 --> 00:34:18.809 align:start position:0% it's it's like regenerating that the key is<00:34:15.940> already<00:34:16.149> there<00:34:16.839> this<00:34:17.200> case<00:34:17.800> it<00:34:18.010> was<00:34:18.190> empty 00:34:18.809 --> 00:34:18.819 align:start position:0% is already there this case it was empty 00:34:18.819 --> 00:34:20.909 align:start position:0% is already there this case it was empty so<00:34:19.000> it's<00:34:19.179> generate<00:34:19.569> the<00:34:19.780> key<00:34:19.960> and<00:34:20.260> leather<00:34:20.589> bag 00:34:20.909 --> 00:34:20.919 align:start position:0% so it's generate the key and leather bag 00:34:20.919 --> 00:34:24.450 align:start position:0% so it's generate the key and leather bag so<00:34:21.339> from<00:34:22.270> this<00:34:22.389> point<00:34:22.629> you<00:34:23.440> can<00:34:23.770> start<00:34:24.220> right 00:34:24.450 --> 00:34:24.460 align:start position:0% so from this point you can start right 00:34:24.460 --> 00:34:25.890 align:start position:0% so from this point you can start right using<00:34:24.849> it<00:34:24.940> so<00:34:25.060> you<00:34:25.300> can<00:34:25.480> sell 00:34:25.890 --> 00:34:25.900 align:start position:0% using it so you can sell 00:34:25.900 --> 00:34:30.160 align:start position:0% using it so you can sell transactional<00:34:26.900> sending<00:34:27.260> data<00:34:27.850> so<00:34:28.870> one<00:34:29.870> point 00:34:30.160 --> 00:34:30.170 align:start position:0% transactional sending data so one point 00:34:30.170 --> 00:34:34.420 align:start position:0% transactional sending data so one point with<00:34:30.560> the<00:34:31.840> cart<00:34:32.840> actually<00:34:33.500> as<00:34:33.620> a<00:34:33.650> true<00:34:34.010> random 00:34:34.420 --> 00:34:34.430 align:start position:0% with the cart actually as a true random 00:34:34.430 --> 00:34:36.850 align:start position:0% with the cart actually as a true random number<00:34:34.790> generator<00:34:35.270> on<00:34:35.540> board<00:34:35.810> so<00:34:36.260> generating 00:34:36.850 --> 00:34:36.860 align:start position:0% number generator on board so generating 00:34:36.860 --> 00:34:45.310 align:start position:0% number generator on board so generating the<00:34:37.010> Keystone<00:34:37.370> cart<00:34:37.670> is<00:34:37.940> really<00:34:38.600> secure<00:34:44.320> okay 00:34:45.310 --> 00:34:45.320 align:start position:0% the Keystone cart is really secure okay 00:34:45.320 --> 00:34:55.030 align:start position:0% the Keystone cart is really secure okay so<00:34:46.900> yeah<00:34:51.820> it's<00:34:52.820> it's<00:34:53.300> in<00:34:53.750> the<00:34:53.870> cheapest<00:34:54.290> assess 00:34:55.030 --> 00:34:55.040 align:start position:0% so yeah it's it's in the cheapest assess 00:34:55.040 --> 00:35:08.470 align:start position:0% so yeah it's it's in the cheapest assess if<00:34:55.220> I<00:34:55.370> do<00:35:04.300> okay<00:35:05.300> so<00:35:05.360> now<00:35:06.610> yes<00:35:07.640> now<00:35:07.970> there's<00:35:08.240> the 00:35:08.470 --> 00:35:08.480 align:start position:0% if I do okay so now yes now there's the 00:35:08.480 --> 00:35:11.680 align:start position:0% if I do okay so now yes now there's the kicad<00:35:09.080> stein<00:35:09.670> comment<00:35:10.670> and<00:35:11.120> it's<00:35:11.330> basically 00:35:11.680 --> 00:35:11.690 align:start position:0% kicad stein comment and it's basically 00:35:11.690 --> 00:35:16.450 align:start position:0% kicad stein comment and it's basically accepting<00:35:12.410> like<00:35:12.590> 32<00:35:13.520> bytes<00:35:13.760> of<00:35:14.030> data<00:35:14.740> and<00:35:15.740> the 00:35:16.450 --> 00:35:16.460 align:start position:0% accepting like 32 bytes of data and the 00:35:16.460 --> 00:35:18.870 align:start position:0% accepting like 32 bytes of data and the descriptive<00:35:17.030> like<00:35:17.180> same<00:35:17.630> thing<00:35:17.870> an<00:35:17.960> empty 00:35:18.870 --> 00:35:18.880 align:start position:0% descriptive like same thing an empty 00:35:18.880 --> 00:35:23.790 align:start position:0% descriptive like same thing an empty life<00:35:19.880> and<00:35:20.530> the<00:35:21.530> same<00:35:21.740> the<00:35:21.890> usual<00:35:22.660> selecting 00:35:23.790 --> 00:35:23.800 align:start position:0% life and the same the usual selecting 00:35:23.800 --> 00:35:26.050 align:start position:0% life and the same the usual selecting opening<00:35:24.800> the<00:35:25.040> secures<00:35:25.400> channel<00:35:25.790> verified 00:35:26.050 --> 00:35:26.060 align:start position:0% opening the secures channel verified 00:35:26.060 --> 00:35:27.900 align:start position:0% opening the secures channel verified would<00:35:26.390> be<00:35:26.480> because<00:35:26.780> it's<00:35:26.900> required<00:35:27.080> before 00:35:27.900 --> 00:35:27.910 align:start position:0% would be because it's required before 00:35:27.910 --> 00:35:31.930 align:start position:0% would be because it's required before signing<00:35:28.910> and<00:35:29.360> then<00:35:30.020> appendix<00:35:30.650> so<00:35:30.860> if<00:35:30.980> I<00:35:31.190> use<00:35:31.700> it 00:35:31.930 --> 00:35:31.940 align:start position:0% signing and then appendix so if I use it 00:35:31.940 --> 00:35:38.440 align:start position:0% signing and then appendix so if I use it and<00:35:32.900> then<00:35:33.140> do<00:35:33.790> this<00:35:35.290> so<00:35:36.290> the<00:35:36.440> output<00:35:36.920> is<00:35:37.450> giving 00:35:38.440 --> 00:35:38.450 align:start position:0% and then do this so the output is giving 00:35:38.450 --> 00:35:49.350 align:start position:0% and then do this so the output is giving me<00:35:38.570> like<00:35:38.810> the<00:35:39.320> signature 00:35:49.350 --> 00:35:49.360 align:start position:0% 00:35:49.360 --> 00:35:55.360 align:start position:0% and<00:35:52.240> what<00:35:53.240> does<00:35:53.720> the<00:35:53.930> sign<00:35:54.530> message<00:35:55.010> which<00:35:55.340> is 00:35:55.360 --> 00:35:55.370 align:start position:0% and what does the sign message which is 00:35:55.370 --> 00:35:58.270 align:start position:0% and what does the sign message which is actually<00:35:56.140> directing<00:35:57.140> this<00:35:57.320> Eli<00:35:57.680> but<00:35:57.950> it's<00:35:58.130> not 00:35:58.270 --> 00:35:58.280 align:start position:0% actually directing this Eli but it's not 00:35:58.280 --> 00:36:03.520 align:start position:0% actually directing this Eli but it's not really<00:36:00.280> this<00:36:01.280> case<00:36:01.640> and<00:36:02.570> then<00:36:03.320> there's 00:36:03.520 --> 00:36:03.530 align:start position:0% really this case and then there's 00:36:03.530 --> 00:36:07.830 align:start position:0% really this case and then there's another<00:36:03.650> concept<00:36:04.340> about<00:36:04.880> the<00:36:05.170> penis<00:36:06.170> bath<00:36:06.530> so 00:36:07.830 --> 00:36:07.840 align:start position:0% another concept about the penis bath so 00:36:07.840 --> 00:36:14.730 align:start position:0% another concept about the penis bath so so<00:36:08.840> every<00:36:09.140> so<00:36:09.920> now<00:36:12.100> every<00:36:13.100> time<00:36:13.310> you<00:36:13.490> want<00:36:13.760> to 00:36:14.730 --> 00:36:14.740 align:start position:0% so every so now every time you want to 00:36:14.740 --> 00:36:18.480 align:start position:0% so every so now every time you want to interact<00:36:15.740> with<00:36:16.070> a<00:36:16.250> ticket<00:36:16.610> you<00:36:17.150> need<00:36:17.390> to<00:36:17.570> know 00:36:18.480 --> 00:36:18.490 align:start position:0% interact with a ticket you need to know 00:36:18.490 --> 00:36:22.180 align:start position:0% interact with a ticket you need to know the<00:36:19.490> parent<00:36:20.270> password<00:36:20.690> so<00:36:21.440> the<00:36:21.740> first<00:36:21.980> time 00:36:22.180 --> 00:36:22.190 align:start position:0% the parent password so the first time 00:36:22.190 --> 00:36:27.100 align:start position:0% the parent password so the first time you<00:36:22.220> use<00:36:22.910> it<00:36:24.310> like<00:36:25.310> the<00:36:25.460> parent<00:36:25.880> and<00:36:26.570> then 00:36:27.100 --> 00:36:27.110 align:start position:0% you use it like the parent and then 00:36:27.110 --> 00:36:31.030 align:start position:0% you use it like the parent and then every<00:36:27.320> time<00:36:27.530> you<00:36:27.650> want<00:36:27.860> to<00:36:28.040> sign<00:36:29.830> some<00:36:30.830> data 00:36:31.030 --> 00:36:31.040 align:start position:0% every time you want to sign some data 00:36:31.040 --> 00:36:33.880 align:start position:0% every time you want to sign some data you<00:36:32.030> need<00:36:32.210> to<00:36:32.330> verify<00:36:32.480> your<00:36:32.720> pitch<00:36:33.050> it's 00:36:33.880 --> 00:36:33.890 align:start position:0% you need to verify your pitch it's 00:36:33.890 --> 00:36:35.590 align:start position:0% you need to verify your pitch it's always<00:36:34.070> something<00:36:34.430> that<00:36:34.670> you<00:36:34.850> get<00:36:35.330> you<00:36:35.480> need 00:36:35.590 --> 00:36:35.600 align:start position:0% always something that you get you need 00:36:35.600 --> 00:36:39.310 align:start position:0% always something that you get you need to<00:36:35.860> service<00:36:36.940> your<00:36:37.940> only<00:36:38.360> you<00:36:38.660> know<00:36:38.780> the<00:36:38.990> owner 00:36:39.310 --> 00:36:39.320 align:start position:0% to service your only you know the owner 00:36:39.320 --> 00:36:41.760 align:start position:0% to service your only you know the owner of<00:36:39.530> the<00:36:39.740> garden<00:36:40.160> the<00:36:40.580> only<00:36:40.730> one<00:36:40.880> its<00:36:41.060> opinions 00:36:41.760 --> 00:36:41.770 align:start position:0% of the garden the only one its opinions 00:36:41.770 --> 00:36:45.010 align:start position:0% of the garden the only one its opinions so<00:36:42.770> in<00:36:42.890> general<00:36:43.190> you<00:36:43.670> you<00:36:43.940> only<00:36:44.090> used<00:36:44.390> the 00:36:45.010 --> 00:36:45.020 align:start position:0% so in general you you only used the 00:36:45.020 --> 00:36:50.440 align:start position:0% so in general you you only used the clicking<00:36:45.380> with<00:36:45.560> your<00:36:45.590> own<00:36:46.450> trust<00:36:47.450> device<00:36:49.450> we 00:36:50.440 --> 00:36:50.450 align:start position:0% clicking with your own trust device we 00:36:50.450 --> 00:36:55.870 align:start position:0% clicking with your own trust device we can<00:36:51.190> set<00:36:52.190> a<00:36:52.370> specific<00:36:52.460> path<00:36:53.030> of<00:36:53.650> HD<00:36:54.650> words<00:36:55.070> that 00:36:55.870 --> 00:36:55.880 align:start position:0% can set a specific path of HD words that 00:36:55.880 --> 00:36:59.230 align:start position:0% can set a specific path of HD words that can<00:36:56.120> be<00:36:56.150> used<00:36:56.620> with<00:36:57.620> an<00:36:57.770> trusted<00:36:58.160> device<00:36:58.430> so 00:36:59.230 --> 00:36:59.240 align:start position:0% can be used with an trusted device so 00:36:59.240 --> 00:37:01.660 align:start position:0% can be used with an trusted device so it's<00:36:59.450> for<00:37:00.020> many<00:37:00.590> things<00:37:00.860> so<00:37:01.220> you<00:37:01.280> can<00:37:01.520> be 00:37:01.660 --> 00:37:01.670 align:start position:0% it's for many things so you can be 00:37:01.670 --> 00:37:04.600 align:start position:0% it's for many things so you can be creative<00:37:02.380> so<00:37:03.380> we<00:37:03.410> can<00:37:03.620> be<00:37:03.800> like<00:37:04.040> just<00:37:04.310> to<00:37:04.520> open 00:37:04.600 --> 00:37:04.610 align:start position:0% creative so we can be like just to open 00:37:04.610 --> 00:37:08.860 align:start position:0% creative so we can be like just to open the<00:37:04.970> door<00:37:05.210> yeah<00:37:05.690> so<00:37:06.260> the<00:37:07.480> key<00:37:08.480> that<00:37:08.690> you're 00:37:08.860 --> 00:37:08.870 align:start position:0% the door yeah so the key that you're 00:37:08.870 --> 00:37:14.140 align:start position:0% the door yeah so the key that you're actually<00:37:09.440> using<00:37:09.980> for<00:37:10.270> your<00:37:12.010> wallet<00:37:13.030> when<00:37:14.030> you 00:37:14.140 --> 00:37:14.150 align:start position:0% actually using for your wallet when you 00:37:14.150 --> 00:37:16.400 align:start position:0% actually using for your wallet when you are<00:37:14.240> still<00:37:14.630> of 00:37:16.400 --> 00:37:16.410 align:start position:0% are still of 00:37:16.410 --> 00:37:20.839 align:start position:0% are still of is<00:37:16.769> all<00:37:17.190> you<00:37:17.579> can<00:37:17.759> do<00:37:17.970> something<00:37:19.849> something 00:37:20.839 --> 00:37:20.849 align:start position:0% is all you can do something something 00:37:20.849 --> 00:37:24.230 align:start position:0% is all you can do something something like<00:37:20.970> paying<00:37:22.009> point-of-sale<00:37:23.009> and<00:37:23.339> with<00:37:24.119> the 00:37:24.230 --> 00:37:24.240 align:start position:0% like paying point-of-sale and with the 00:37:24.240 --> 00:37:27.970 align:start position:0% like paying point-of-sale and with the risk<00:37:24.420> of<00:37:24.779> other<00:37:25.410> experiment<00:37:26.190> ahead<00:37:26.490> but 00:37:27.970 --> 00:37:27.980 align:start position:0% risk of other experiment ahead but 00:37:27.980 --> 00:37:31.460 align:start position:0% risk of other experiment ahead but basically<00:37:28.980> these<00:37:29.279> have<00:37:29.759> just<00:37:30.029> a<00:37:30.150> few<00:37:30.470> tokens 00:37:31.460 --> 00:37:31.470 align:start position:0% basically these have just a few tokens 00:37:31.470 --> 00:37:34.910 align:start position:0% basically these have just a few tokens on<00:37:31.650> the<00:37:31.680> path<00:37:32.160> in<00:37:32.460> just<00:37:32.970> a<00:37:33.210> bit 00:37:34.910 --> 00:37:34.920 align:start position:0% on the path in just a bit 00:37:34.920 --> 00:37:37.490 align:start position:0% on the path in just a bit let's<00:37:35.309> visit<00:37:35.460> so<00:37:36.329> the<00:37:36.480> way<00:37:36.630> you<00:37:36.690> do<00:37:37.020> it<00:37:37.170> is<00:37:37.349> by 00:37:37.490 --> 00:37:37.500 align:start position:0% let's visit so the way you do it is by 00:37:37.500 --> 00:37:42.079 align:start position:0% let's visit so the way you do it is by this<00:37:38.460> set<00:37:39.240> previous<00:37:39.690> path<00:37:39.930> Department<00:37:40.470> and<00:37:41.089> to 00:37:42.079 --> 00:37:42.089 align:start position:0% this set previous path Department and to 00:37:42.089 --> 00:37:44.380 align:start position:0% this set previous path Department and to use<00:37:42.270> it<00:37:42.540> you<00:37:42.720> need<00:37:42.930> to<00:37:42.960> of<00:37:43.260> course<00:37:43.290> pairing<00:37:44.130> and 00:37:44.380 --> 00:37:44.390 align:start position:0% use it you need to of course pairing and 00:37:44.390 --> 00:37:47.510 align:start position:0% use it you need to of course pairing and verify<00:37:45.390> the<00:37:45.450> pin<00:37:45.809> and<00:37:46.079> then<00:37:46.559> you<00:37:46.799> just<00:37:47.309> pass 00:37:47.510 --> 00:37:47.520 align:start position:0% verify the pin and then you just pass 00:37:47.520 --> 00:37:50.510 align:start position:0% verify the pin and then you just pass like<00:37:47.849> the<00:37:48.000> path<00:37:48.210> of<00:37:48.559> bass<00:37:49.559> to<00:37:49.799> what<00:37:49.980> its<00:37:50.130> people 00:37:50.510 --> 00:37:50.520 align:start position:0% like the path of bass to what its people 00:37:50.520 --> 00:37:55.960 align:start position:0% like the path of bass to what its people to<00:37:50.670> use<00:37:50.930> and<00:37:51.930> after<00:37:52.079> this 00:37:55.960 --> 00:37:55.970 align:start position:0% 00:37:55.970 --> 00:38:08.530 align:start position:0% [Music] 00:38:08.530 --> 00:38:08.540 align:start position:0% 00:38:08.540 --> 00:38:10.530 align:start position:0% yes 00:38:10.530 --> 00:38:10.540 align:start position:0% yes 00:38:10.540 --> 00:38:14.340 align:start position:0% yes okay<00:38:11.110> so<00:38:11.290> after<00:38:11.440> this<00:38:11.940> we<00:38:12.940> we<00:38:13.270> set<00:38:13.570> with<00:38:13.960> this 00:38:14.340 --> 00:38:14.350 align:start position:0% okay so after this we we set with this 00:38:14.350 --> 00:38:19.890 align:start position:0% okay so after this we we set with this path<00:38:15.900> in<00:38:16.900> the<00:38:16.990> stuff<00:38:17.230> and<00:38:18.360> basically<00:38:19.360> what<00:38:19.780> we 00:38:19.890 --> 00:38:19.900 align:start position:0% path in the stuff and basically what we 00:38:19.900 --> 00:38:24.990 align:start position:0% path in the stuff and basically what we consume<00:38:20.260> is<00:38:20.790> timing<00:38:23.100> so<00:38:24.100> as<00:38:24.220> you<00:38:24.340> can<00:38:24.490> see<00:38:24.550> here 00:38:24.990 --> 00:38:25.000 align:start position:0% consume is timing so as you can see here 00:38:25.000 --> 00:38:26.970 align:start position:0% consume is timing so as you can see here so<00:38:25.420> the<00:38:25.510> script<00:38:25.780> is<00:38:25.960> really<00:38:26.260> into<00:38:26.470> common<00:38:26.830> so 00:38:26.970 --> 00:38:26.980 align:start position:0% so the script is really into common so 00:38:26.980 --> 00:38:29.580 align:start position:0% so the script is really into common so one<00:38:27.190> is<00:38:27.340> just<00:38:27.870> selecting<00:38:28.870> and<00:38:29.110> the<00:38:29.230> other<00:38:29.350> one 00:38:29.580 --> 00:38:29.590 align:start position:0% one is just selecting and the other one 00:38:29.590 --> 00:38:35.250 align:start position:0% one is just selecting and the other one is<00:38:29.740> like<00:38:31.560> signing<00:38:32.560> something<00:38:32.980> and<00:38:33.900> here<00:38:34.900> so 00:38:35.250 --> 00:38:35.260 align:start position:0% is like signing something and here so 00:38:35.260 --> 00:38:38.810 align:start position:0% is like signing something and here so the<00:38:35.410> example<00:38:36.010> is<00:38:36.040> like<00:38:37.170> these<00:38:38.170> other<00:38:38.350> things 00:38:38.810 --> 00:38:38.820 align:start position:0% the example is like these other things 00:38:38.820 --> 00:38:43.650 align:start position:0% the example is like these other things and<00:38:40.320> nothing<00:38:41.320> that<00:38:41.350> is<00:38:41.830> another<00:38:42.660> simple 00:38:43.650 --> 00:38:43.660 align:start position:0% and nothing that is another simple 00:38:43.660 --> 00:38:49.080 align:start position:0% and nothing that is another simple example<00:38:45.360> funky<00:38:46.360> and<00:38:47.250> an<00:38:48.250> example<00:38:48.820> is 00:38:49.080 --> 00:38:49.090 align:start position:0% example funky and an example is 00:38:49.090 --> 00:38:52.710 align:start position:0% example funky and an example is basically<00:38:49.480> doing<00:38:49.690> everything<00:38:50.050> and<00:38:51.330> yes<00:38:52.330> this 00:38:52.710 --> 00:38:52.720 align:start position:0% basically doing everything and yes this 00:38:52.720 --> 00:38:59.600 align:start position:0% basically doing everything and yes this one<00:38:54.510> just<00:38:55.510> so<00:38:56.020> if<00:38:56.140> not<00:38:56.380> developing<00:38:58.470> by<00:38:59.470> the 00:38:59.600 --> 00:38:59.610 align:start position:0% one just so if not developing by the 00:38:59.610 --> 00:39:03.870 align:start position:0% one just so if not developing by the application<00:39:00.610> this<00:39:00.880> interacts<00:39:01.270> with<00:39:01.450> the<00:39:02.880> CLI 00:39:03.870 --> 00:39:03.880 align:start position:0% application this interacts with the CLI 00:39:03.880 --> 00:39:06.270 align:start position:0% application this interacts with the CLI can<00:39:04.120> be<00:39:04.330> useful<00:39:05.320> so<00:39:05.530> that<00:39:05.710> you<00:39:05.860> can<00:39:06.040> easily 00:39:06.270 --> 00:39:06.280 align:start position:0% can be useful so that you can easily 00:39:06.280 --> 00:39:09.840 align:start position:0% can be useful so that you can easily like<00:39:06.760> restore<00:39:07.830> inchaallah<00:39:08.830> expansion<00:39:09.670> to<00:39:09.820> the 00:39:09.840 --> 00:39:09.850 align:start position:0% like restore inchaallah expansion to the 00:39:09.850 --> 00:39:14.180 align:start position:0% like restore inchaallah expansion to the earth<00:39:10.180> and<00:39:10.480> everything<00:39:10.750> and<00:39:11.460> then<00:39:12.460> the<00:39:13.090> main 00:39:14.180 --> 00:39:14.190 align:start position:0% earth and everything and then the main 00:39:14.190 --> 00:39:19.460 align:start position:0% earth and everything and then the main is<00:39:15.140> basically<00:39:16.140> the<00:39:16.710> one<00:39:17.670> for<00:39:18.030> joy<00:39:18.450> one<00:39:19.230> for 00:39:19.460 --> 00:39:19.470 align:start position:0% is basically the one for joy one for 00:39:19.470 --> 00:39:23.350 align:start position:0% is basically the one for joy one for advice<00:39:19.800> and<00:39:20.100> they<00:39:21.030> basically<00:39:21.570> have<00:39:21.840> the<00:39:22.050> same 00:39:23.350 --> 00:39:23.360 align:start position:0% advice and they basically have the same 00:39:23.360 --> 00:39:30.920 align:start position:0% advice and they basically have the same common<00:39:24.360> sense<00:39:24.390> and<00:39:25.520> inside<00:39:27.080> the<00:39:29.720> statists<00:39:30.750> key 00:39:30.920 --> 00:39:30.930 align:start position:0% common sense and inside the statists key 00:39:30.930 --> 00:39:34.610 align:start position:0% common sense and inside the statists key capture<00:39:31.820> this<00:39:32.820> so<00:39:33.570> does<00:39:33.780> the<00:39:33.960> package<00:39:34.470> of 00:39:34.610 --> 00:39:34.620 align:start position:0% capture this so does the package of 00:39:34.620 --> 00:39:38.180 align:start position:0% capture this so does the package of Juniper<00:39:35.100> Java<00:39:35.400> and<00:39:36.290> Android<00:39:37.290> and<00:39:37.680> then<00:39:37.920> this 00:39:38.180 --> 00:39:38.190 align:start position:0% Juniper Java and Android and then this 00:39:38.190 --> 00:39:52.100 align:start position:0% Juniper Java and Android and then this there's<00:39:39.120> a<00:39:39.210> bit<00:39:39.540> more<00:39:41.630> I'll<00:39:42.630> I<00:39:42.930> can<00:39:43.140> try<00:39:51.110> so 00:39:52.100 --> 00:39:52.110 align:start position:0% there's a bit more I'll I can try so 00:39:52.110 --> 00:39:55.460 align:start position:0% there's a bit more I'll I can try so it's<00:39:52.230> basically<00:39:52.620> a<00:39:53.070> Cena<00:39:54.000> so<00:39:54.990> the<00:39:55.200> way<00:39:55.410> it 00:39:55.460 --> 00:39:55.470 align:start position:0% it's basically a Cena so the way it 00:39:55.470 --> 00:40:00.440 align:start position:0% it's basically a Cena so the way it works<00:39:55.560> is<00:39:55.980> like<00:39:56.010> a<00:39:56.780> lot<00:39:57.780> of<00:39:57.960> gels<00:39:58.440> and<00:39:58.620> then<00:39:59.550> you 00:40:00.440 --> 00:40:00.450 align:start position:0% works is like a lot of gels and then you 00:40:00.450 --> 00:40:02.840 align:start position:0% works is like a lot of gels and then you basically<00:40:00.690> initialize<00:40:01.530> a<00:40:01.560> common<00:40:02.280> sense<00:40:02.550> and 00:40:02.840 --> 00:40:02.850 align:start position:0% basically initialize a common sense and 00:40:02.850 --> 00:40:06.560 align:start position:0% basically initialize a common sense and then<00:40:03.500> you<00:40:04.500> basically<00:40:04.710> have<00:40:05.030> the<00:40:06.030> same<00:40:06.060> common 00:40:06.560 --> 00:40:06.570 align:start position:0% then you basically have the same common 00:40:06.570 --> 00:40:09.450 align:start position:0% then you basically have the same common that<00:40:06.840> we<00:40:06.990> had<00:40:07.170> before 00:40:09.450 --> 00:40:09.460 align:start position:0% that we had before 00:40:09.460 --> 00:40:12.660 align:start position:0% that we had before is<00:40:09.520> a<00:40:09.580> method<00:40:10.300> of<00:40:10.510> the<00:40:10.890> common<00:40:11.890> separately<00:40:12.490> so 00:40:12.660 --> 00:40:12.670 align:start position:0% is a method of the common separately so 00:40:12.670 --> 00:40:18.240 align:start position:0% is a method of the common separately so selecting<00:40:13.300> and<00:40:13.690> then<00:40:15.030> let's<00:40:16.030> see<00:40:16.890> if<00:40:17.890> there's 00:40:18.240 --> 00:40:18.250 align:start position:0% selecting and then let's see if there's 00:40:18.250 --> 00:40:20.940 align:start position:0% selecting and then let's see if there's something<00:40:18.670> that<00:40:18.700> it's<00:40:19.060> really<00:40:19.500> same<00:40:20.500> so<00:40:20.800> like 00:40:20.940 --> 00:40:20.950 align:start position:0% something that it's really same so like 00:40:20.950 --> 00:40:26.730 align:start position:0% something that it's really same so like pairing<00:40:21.520> and<00:40:21.940> then<00:40:24.210> gifting<00:40:25.210> the<00:40:25.740> individual 00:40:26.730 --> 00:40:26.740 align:start position:0% pairing and then gifting the individual 00:40:26.740 --> 00:40:31.440 align:start position:0% pairing and then gifting the individual town<00:40:27.010> so<00:40:27.430> it<00:40:27.849> it's<00:40:28.420> based<00:40:28.750> to<00:40:29.109> to<00:40:29.880> to<00:40:30.880> read<00:40:31.060> and 00:40:31.440 --> 00:40:31.450 align:start position:0% town so it it's based to to to read and 00:40:31.450 --> 00:40:33.960 align:start position:0% town so it it's based to to to read and it's<00:40:32.320> basically<00:40:32.650> so<00:40:32.890> if<00:40:33.070> this<00:40:33.250> day<00:40:33.550> wants 00:40:33.960 --> 00:40:33.970 align:start position:0% it's basically so if this day wants 00:40:33.970 --> 00:40:36.960 align:start position:0% it's basically so if this day wants basically<00:40:34.570> preventing<00:40:35.530> anything<00:40:35.980> you<00:40:36.339> need 00:40:36.960 --> 00:40:36.970 align:start position:0% basically preventing anything you need 00:40:36.970 --> 00:40:41.430 align:start position:0% basically preventing anything you need to<00:40:37.089> have<00:40:37.270> study<00:40:37.630> it's<00:40:37.960> easily<00:40:38.200> to<00:40:38.440> copy<00:40:39.390> it<00:40:40.440> you 00:40:41.430 --> 00:40:41.440 align:start position:0% to have study it's easily to copy it you 00:40:41.440 --> 00:40:43.170 align:start position:0% to have study it's easily to copy it you know<00:40:41.680> sorry<00:40:41.920> you<00:40:42.070> mentioned<00:40:42.369> I<00:40:42.520> us<00:40:42.790> what<00:40:43.030> is 00:40:43.170 --> 00:40:43.180 align:start position:0% know sorry you mentioned I us what is 00:40:43.180 --> 00:40:48.810 align:start position:0% know sorry you mentioned I us what is the<00:40:43.420> status<00:40:43.960> of<00:40:44.080> virus<00:40:45.660> yeah<00:40:46.690> so<00:40:47.140> let<00:40:47.349> me<00:40:47.380> also 00:40:48.810 --> 00:40:48.820 align:start position:0% the status of virus yeah so let me also 00:40:48.820 --> 00:40:54.670 align:start position:0% the status of virus yeah so let me also [Music] 00:40:54.670 --> 00:40:54.680 align:start position:0% 00:40:54.680 --> 00:41:08.150 align:start position:0% [Music] 00:41:08.150 --> 00:41:08.160 align:start position:0% 00:41:08.160 --> 00:41:12.390 align:start position:0% yes<00:41:09.160> okay<00:41:09.640> so<00:41:10.090> before 00:41:12.390 --> 00:41:12.400 align:start position:0% yes okay so before 00:41:12.400 --> 00:41:21.320 align:start position:0% yes okay so before [Music] 00:41:21.320 --> 00:41:21.330 align:start position:0% 00:41:21.330 --> 00:41:25.080 align:start position:0% okay<00:41:22.330> so<00:41:22.390> saying<00:41:22.840> so<00:41:23.620> with<00:41:23.800> the<00:41:24.010> solar<00:41:24.700> virus 00:41:25.080 --> 00:41:25.090 align:start position:0% okay so saying so with the solar virus 00:41:25.090 --> 00:41:28.740 align:start position:0% okay so saying so with the solar virus 13<00:41:25.890> which<00:41:26.890> is<00:41:26.920> the<00:41:27.130> event<00:41:27.550> they<00:41:28.300> prevented 00:41:28.740 --> 00:41:28.750 align:start position:0% 13 which is the event they prevented 00:41:28.750 --> 00:41:35.820 align:start position:0% 13 which is the event they prevented everything<00:41:30.360> API<00:41:31.860> the<00:41:32.860> C<00:41:33.520> core<00:41:34.500> so<00:41:35.500> you<00:41:35.530> can 00:41:35.820 --> 00:41:35.830 align:start position:0% everything API the C core so you can 00:41:35.830 --> 00:41:38.040 align:start position:0% everything API the C core so you can basically<00:41:36.040> send<00:41:36.610> a<00:41:36.820> receive<00:41:37.180> all<00:41:37.510> the<00:41:37.690> videos 00:41:38.040 --> 00:41:38.050 align:start position:0% basically send a receive all the videos 00:41:38.050 --> 00:41:41.280 align:start position:0% basically send a receive all the videos so<00:41:38.520> so<00:41:39.520> so<00:41:40.120> you<00:41:40.180> can<00:41:40.420> have<00:41:40.570> a<00:41:40.600> full<00:41:40.870> interaction 00:41:41.280 --> 00:41:41.290 align:start position:0% so so so you can have a full interaction 00:41:41.290 --> 00:41:45.120 align:start position:0% so so so you can have a full interaction and<00:41:41.800> before<00:41:42.730> that<00:41:42.870> it<00:41:43.870> was<00:41:44.080> like<00:41:44.260> only<00:41:44.530> reading 00:41:45.120 --> 00:41:45.130 align:start position:0% and before that it was like only reading 00:41:45.130 --> 00:41:48.450 align:start position:0% and before that it was like only reading the<00:41:45.390> in-depth<00:41:46.390> tag<00:41:46.720> so<00:41:47.320> it<00:41:47.410> was<00:41:47.560> only<00:41:47.740> for<00:41:48.070> you 00:41:48.450 --> 00:41:48.460 align:start position:0% the in-depth tag so it was only for you 00:41:48.460 --> 00:41:54.860 align:start position:0% the in-depth tag so it was only for you know 00:41:54.860 --> 00:41:54.870 align:start position:0% 00:41:54.870 --> 00:42:09.040 align:start position:0% [Music] 00:42:09.040 --> 00:42:09.050 align:start position:0% 00:42:09.050 --> 00:42:14.500 align:start position:0% okay<00:42:09.650> so<00:42:09.710> there's<00:42:11.740> this<00:42:12.740> year<00:42:13.180> kicker<00:42:14.180> Swift 00:42:14.500 --> 00:42:14.510 align:start position:0% okay so there's this year kicker Swift 00:42:14.510 --> 00:42:18.820 align:start position:0% okay so there's this year kicker Swift SDK<00:42:15.290> and<00:42:15.850> then<00:42:17.320> there's<00:42:18.320> an<00:42:18.440> example 00:42:18.820 --> 00:42:18.830 align:start position:0% SDK and then there's an example 00:42:18.830 --> 00:42:25.660 align:start position:0% SDK and then there's an example application<00:42:19.580> the<00:42:20.300> Moses<00:42:22.150> repository<00:42:23.150> and<00:42:24.670> the 00:42:25.660 --> 00:42:25.670 align:start position:0% application the Moses repository and the 00:42:25.670 --> 00:42:28.450 align:start position:0% application the Moses repository and the common<00:42:26.000> set<00:42:26.210> is<00:42:26.330> basically<00:42:26.690> the<00:42:26.870> same<00:42:27.460> jacket 00:42:28.450 --> 00:42:28.460 align:start position:0% common set is basically the same jacket 00:42:28.460 --> 00:42:31.330 align:start position:0% common set is basically the same jacket ends<00:42:28.940> with<00:42:29.770> basically<00:42:30.770> anything<00:42:30.980> about<00:42:31.190> your 00:42:31.330 --> 00:42:31.340 align:start position:0% ends with basically anything about your 00:42:31.340 --> 00:42:34.240 align:start position:0% ends with basically anything about your common<00:42:31.640> sense<00:42:31.670> away<00:42:32.150> and<00:42:33.080> now<00:42:33.500> I<00:42:33.860> don't<00:42:34.010> know<00:42:34.220> I 00:42:34.240 --> 00:42:34.250 align:start position:0% common sense away and now I don't know I 00:42:34.250 --> 00:42:36.580 align:start position:0% common sense away and now I don't know I mean<00:42:34.490> we<00:42:34.730> we<00:42:35.120> saw<00:42:35.570> everything<00:42:36.080> so<00:42:36.260> if<00:42:36.350> you<00:42:36.470> have 00:42:36.580 --> 00:42:36.590 align:start position:0% mean we we saw everything so if you have 00:42:36.590 --> 00:42:39.270 align:start position:0% mean we we saw everything so if you have questions<00:42:37.100> or<00:42:37.310> if<00:42:37.400> you<00:42:37.880> want<00:42:38.060> to<00:42:38.120> play<00:42:38.420> with 00:42:39.270 --> 00:42:39.280 align:start position:0% questions or if you want to play with 00:42:39.280 --> 00:42:42.570 align:start position:0% questions or if you want to play with card<00:42:40.280> with<00:42:40.640> the<00:42:40.820> CLI<00:42:41.300> or<00:42:41.660> if<00:42:41.810> you<00:42:41.960> want<00:42:42.230> to 00:42:42.570 --> 00:42:42.580 align:start position:0% card with the CLI or if you want to 00:42:42.580 --> 00:42:48.520 align:start position:0% card with the CLI or if you want to install<00:42:43.580> the<00:42:45.520> demo<00:42:46.520> app<00:42:46.760> for<00:42:47.210> Android<00:42:48.050> and<00:42:48.380> iOS 00:42:48.520 --> 00:42:48.530 align:start position:0% install the demo app for Android and iOS 00:42:48.530 --> 00:42:52.360 align:start position:0% install the demo app for Android and iOS and<00:42:49.010> try<00:42:49.160> to<00:42:50.140> compile<00:42:51.140> them<00:42:51.440> the<00:42:51.650> point<00:42:51.950> and 00:42:52.360 --> 00:42:52.370 align:start position:0% and try to compile them the point and 00:42:52.370 --> 00:42:54.880 align:start position:0% and try to compile them the point and we're<00:42:53.120> here<00:42:53.360> to<00:42:53.570> help<00:42:53.600> and<00:42:54.260> there's<00:42:54.560> a 00:42:54.880 --> 00:42:54.890 align:start position:0% we're here to help and there's a 00:42:54.890 --> 00:43:02.680 align:start position:0% we're here to help and there's a question<00:42:55.250> I<00:43:00.370> never<00:43:01.370> just<00:43:01.610> speak<00:43:01.820> up<00:43:01.940> so<00:43:02.660> I 00:43:02.680 --> 00:43:02.690 align:start position:0% question I never just speak up so I 00:43:02.690 --> 00:43:03.850 align:start position:0% question I never just speak up so I missed<00:43:03.110> the<00:43:03.260> beginning<00:43:03.380> of<00:43:03.740> the 00:43:03.850 --> 00:43:03.860 align:start position:0% missed the beginning of the 00:43:03.860 --> 00:43:05.890 align:start position:0% missed the beginning of the presentations<00:43:04.670> are<00:43:04.820> loud<00:43:05.000> that<00:43:05.210> it<00:43:05.330> already 00:43:05.890 --> 00:43:05.900 align:start position:0% presentations are loud that it already 00:43:05.900 --> 00:43:12.420 align:start position:0% presentations are loud that it already mentioned<00:43:06.470> but<00:43:07.690> overall<00:43:09.700> it<00:43:10.700> status<00:43:11.120> keycard 00:43:12.420 --> 00:43:12.430 align:start position:0% mentioned but overall it status keycard 00:43:12.430 --> 00:43:14.800 align:start position:0% mentioned but overall it status keycard compared<00:43:13.430> to<00:43:13.760> something<00:43:14.090> like<00:43:14.210> a<00:43:14.360> dress<00:43:14.660> or 00:43:14.800 --> 00:43:14.810 align:start position:0% compared to something like a dress or 00:43:14.810 --> 00:43:23.710 align:start position:0% compared to something like a dress or one<00:43:15.020> in<00:43:15.380> security<00:43:21.310> so<00:43:22.310> in<00:43:22.820> general<00:43:23.330> compared 00:43:23.710 --> 00:43:23.720 align:start position:0% one in security so in general compared 00:43:23.720 --> 00:43:28.660 align:start position:0% one in security so in general compared to<00:43:23.870> the<00:43:23.990> other<00:43:24.170> our<00:43:24.500> wallets<00:43:27.100> so<00:43:28.100> the<00:43:28.280> keycard 00:43:28.660 --> 00:43:28.670 align:start position:0% to the other our wallets so the keycard 00:43:28.670 --> 00:43:31.690 align:start position:0% to the other our wallets so the keycard us<00:43:28.880> every<00:43:29.330> cycle<00:43:30.140> storage<00:43:30.560> places<00:43:30.920> it<00:43:31.280> is<00:43:31.460> the 00:43:31.690 --> 00:43:31.700 align:start position:0% us every cycle storage places it is the 00:43:31.700 --> 00:43:33.370 align:start position:0% us every cycle storage places it is the same<00:43:31.910> cigarette<00:43:32.540> more<00:43:32.810> or<00:43:32.900> less<00:43:33.080> the<00:43:33.230> same 00:43:33.370 --> 00:43:33.380 align:start position:0% same cigarette more or less the same 00:43:33.380 --> 00:43:37.480 align:start position:0% same cigarette more or less the same thing<00:43:33.620> could<00:43:33.740> elevate<00:43:33.920> like<00:43:34.370> the<00:43:34.550> letter<00:43:36.490> it 00:43:37.480 --> 00:43:37.490 align:start position:0% thing could elevate like the letter it 00:43:37.490 --> 00:43:39.280 align:start position:0% thing could elevate like the letter it doesn't<00:43:37.850> tempt<00:43:38.000> additional<00:43:38.780> part 00:43:39.280 --> 00:43:39.290 align:start position:0% doesn't tempt additional part 00:43:39.290 --> 00:43:40.870 align:start position:0% doesn't tempt additional part controlling<00:43:39.830> the<00:43:39.950> screen<00:43:40.250> and<00:43:40.430> the<00:43:40.520> Baptist 00:43:40.870 --> 00:43:40.880 align:start position:0% controlling the screen and the Baptist 00:43:40.880 --> 00:43:44.100 align:start position:0% controlling the screen and the Baptist because<00:43:41.300> it<00:43:41.570> doesn't<00:43:41.900> have<00:43:42.050> a<00:43:42.080> screen<00:43:42.230> buttons 00:43:44.100 --> 00:43:44.110 align:start position:0% because it doesn't have a screen buttons 00:43:44.110 --> 00:43:48.450 align:start position:0% because it doesn't have a screen buttons so<00:43:45.110> it's<00:43:45.230> very<00:43:45.650> simple<00:43:45.980> storage<00:43:46.420> it<00:43:47.420> is 00:43:48.450 --> 00:43:48.460 align:start position:0% so it's very simple storage it is 00:43:48.460 --> 00:43:51.640 align:start position:0% so it's very simple storage it is inexpensive<00:43:49.460> this<00:43:50.030> and<00:43:50.420> this<00:43:51.020> standard 00:43:51.640 --> 00:43:51.650 align:start position:0% inexpensive this and this standard 00:43:51.650 --> 00:43:55.390 align:start position:0% inexpensive this and this standard artwork<00:43:52.280> so<00:43:52.550> we<00:43:53.200> the<00:43:54.200> Pope<00:43:54.440> one<00:43:54.620> of<00:43:54.770> the<00:43:54.950> points 00:43:55.390 --> 00:43:55.400 align:start position:0% artwork so we the Pope one of the points 00:43:55.400 --> 00:43:59.020 align:start position:0% artwork so we the Pope one of the points is<00:43:55.520> that<00:43:55.730> you<00:43:55.940> we<00:43:56.660> don't<00:43:57.020> have<00:43:57.470> a<00:43:58.280> product<00:43:58.610> to 00:43:59.020 --> 00:43:59.030 align:start position:0% is that you we don't have a product to 00:43:59.030 --> 00:44:04.250 align:start position:0% is that you we don't have a product to sell<00:43:59.210> and<00:44:00.010> it<00:44:01.010> is<00:44:01.220> no<00:44:01.640> that<00:44:02.510> is 00:44:04.250 --> 00:44:04.260 align:start position:0% sell and it is no that is 00:44:04.260 --> 00:44:06.560 align:start position:0% sell and it is no that is close<00:44:04.530> the<00:44:04.890> soul<00:44:05.100> because<00:44:05.490> and<00:44:05.880> giving<00:44:06.180> even 00:44:06.560 --> 00:44:06.570 align:start position:0% close the soul because and giving even 00:44:06.570 --> 00:44:08.390 align:start position:0% close the soul because and giving even if<00:44:06.690> it's<00:44:06.840> open<00:44:07.170> source<00:44:07.350> the<00:44:07.590> schematics<00:44:08.220> we 00:44:08.390 --> 00:44:08.400 align:start position:0% if it's open source the schematics we 00:44:08.400 --> 00:44:10.340 align:start position:0% if it's open source the schematics we still<00:44:08.940> are<00:44:09.090> not<00:44:09.300> going<00:44:09.540> to<00:44:09.750> make<00:44:09.960> it<00:44:10.140> yourself 00:44:10.340 --> 00:44:10.350 align:start position:0% still are not going to make it yourself 00:44:10.350 --> 00:44:13.130 align:start position:0% still are not going to make it yourself but<00:44:10.890> these<00:44:11.250> cards<00:44:11.670> you<00:44:11.910> can<00:44:12.240> find<00:44:12.510> them<00:44:12.720> Israel 00:44:13.130 --> 00:44:13.140 align:start position:0% but these cards you can find them Israel 00:44:13.140 --> 00:44:15.200 align:start position:0% but these cards you can find them Israel we<00:44:13.410> bought<00:44:13.740> these<00:44:13.950> white<00:44:14.220> cards<00:44:14.700> and<00:44:15.090> we 00:44:15.200 --> 00:44:15.210 align:start position:0% we bought these white cards and we 00:44:15.210 --> 00:44:17.630 align:start position:0% we bought these white cards and we stopped<00:44:15.480> the<00:44:15.630> output<00:44:15.960> so<00:44:16.260> there<00:44:16.470> can<00:44:16.740> be<00:44:16.770> many 00:44:17.630 --> 00:44:17.640 align:start position:0% stopped the output so there can be many 00:44:17.640 --> 00:44:22.190 align:start position:0% stopped the output so there can be many different<00:44:18.060> of<00:44:18.720> this<00:44:19.280> there<00:44:20.280> can<00:44:20.460> be<00:44:21.200> endless 00:44:22.190 --> 00:44:22.200 align:start position:0% different of this there can be endless 00:44:22.200 --> 00:44:24.260 align:start position:0% different of this there can be endless combinations<00:44:22.470> with<00:44:23.250> different<00:44:23.820> features 00:44:24.260 --> 00:44:24.270 align:start position:0% combinations with different features 00:44:24.270 --> 00:44:26.630 align:start position:0% combinations with different features multiple<00:44:24.570> offers<00:44:25.230> on<00:44:25.380> the<00:44:25.500> same<00:44:25.740> card<00:44:26.040> so<00:44:26.460> from 00:44:26.630 --> 00:44:26.640 align:start position:0% multiple offers on the same card so from 00:44:26.640 --> 00:44:28.970 align:start position:0% multiple offers on the same card so from a<00:44:26.730> security<00:44:27.060> point<00:44:27.540> of<00:44:27.720> view<00:44:27.780> is<00:44:28.200> the<00:44:28.710> same 00:44:28.970 --> 00:44:28.980 align:start position:0% a security point of view is the same 00:44:28.980 --> 00:44:31.550 align:start position:0% a security point of view is the same based<00:44:29.340> basic<00:44:30.030> of<00:44:30.180> what<00:44:30.210> is<00:44:30.510> in<00:44:30.869> a<00:44:30.930> ledger<00:44:31.230> the 00:44:31.550 --> 00:44:31.560 align:start position:0% based basic of what is in a ledger the 00:44:31.560 --> 00:44:33.710 align:start position:0% based basic of what is in a ledger the same<00:44:31.890> secure<00:44:32.220> element<00:44:32.369> of<00:44:33.060> course<00:44:33.359> you<00:44:33.540> don't 00:44:33.710 --> 00:44:33.720 align:start position:0% same secure element of course you don't 00:44:33.720 --> 00:44:35.510 align:start position:0% same secure element of course you don't have<00:44:33.840> a<00:44:33.900> screen<00:44:34.320> and<00:44:34.650> you<00:44:34.710> don't<00:44:34.890> have<00:44:35.010> buttons 00:44:35.510 --> 00:44:35.520 align:start position:0% have a screen and you don't have buttons 00:44:35.520 --> 00:44:38.240 align:start position:0% have a screen and you don't have buttons so<00:44:35.790> it's<00:44:35.940> a<00:44:36.030> compromise<00:44:36.600> you<00:44:36.930> were<00:44:37.260> to<00:44:37.950> trust 00:44:38.240 --> 00:44:38.250 align:start position:0% so it's a compromise you were to trust 00:44:38.250 --> 00:44:42.070 align:start position:0% so it's a compromise you were to trust the<00:44:38.400> device<00:44:38.730> we<00:44:39.119> solved<00:44:39.480> this<00:44:39.630> in<00:44:40.440> part<00:44:40.880> by 00:44:42.070 --> 00:44:42.080 align:start position:0% the device we solved this in part by 00:44:42.080 --> 00:44:44.570 align:start position:0% the device we solved this in part by implementing<00:44:43.080> this<00:44:43.440> secure<00:44:44.070> channel 00:44:44.570 --> 00:44:44.580 align:start position:0% implementing this secure channel 00:44:44.580 --> 00:44:47.900 align:start position:0% implementing this secure channel protocol<00:44:45.240> which<00:44:46.140> at<00:44:46.890> least<00:44:47.190> allows<00:44:47.520> you<00:44:47.760> to 00:44:47.900 --> 00:44:47.910 align:start position:0% protocol which at least allows you to 00:44:47.910 --> 00:44:49.880 align:start position:0% protocol which at least allows you to pair<00:44:48.180> with<00:44:48.480> a<00:44:48.540> specific<00:44:49.170> device<00:44:49.470> that<00:44:49.770> you 00:44:49.880 --> 00:44:49.890 align:start position:0% pair with a specific device that you 00:44:49.890 --> 00:44:53.990 align:start position:0% pair with a specific device that you want<00:44:50.070> to<00:44:50.250> use<00:44:50.430> up<00:44:50.700> to<00:44:51.000> five<00:44:52.040> so<00:44:53.040> you<00:44:53.520> don't<00:44:53.850> have 00:44:53.990 --> 00:44:54.000 align:start position:0% want to use up to five so you don't have 00:44:54.000 --> 00:44:56.380 align:start position:0% want to use up to five so you don't have random<00:44:54.270> devices<00:44:54.930> interacting<00:44:55.530> with<00:44:55.650> the<00:44:55.770> card 00:44:56.380 --> 00:44:56.390 align:start position:0% random devices interacting with the card 00:44:56.390 --> 00:45:02.770 align:start position:0% random devices interacting with the card the<00:44:57.390> card<00:44:57.500> as<00:44:59.030> the<00:45:00.030> advantage<00:45:00.660> of<00:45:00.920> being<00:45:01.920> very 00:45:02.770 --> 00:45:02.780 align:start position:0% the card as the advantage of being very 00:45:02.780 --> 00:45:05.510 align:start position:0% the card as the advantage of being very practical<00:45:03.780> because<00:45:04.230> every<00:45:04.770> phone<00:45:04.950> has<00:45:04.980> an<00:45:05.220> NFC 00:45:05.510 --> 00:45:05.520 align:start position:0% practical because every phone has an NFC 00:45:05.520 --> 00:45:10.970 align:start position:0% practical because every phone has an NFC reader<00:45:05.910> so<00:45:06.890> compare<00:45:07.890> the<00:45:08.130> two<00:45:08.420> USB<00:45:09.980> solutions 00:45:10.970 --> 00:45:10.980 align:start position:0% reader so compare the two USB solutions 00:45:10.980 --> 00:45:13.670 align:start position:0% reader so compare the two USB solutions they<00:45:11.340> can<00:45:11.520> be<00:45:11.700> also<00:45:11.910> used<00:45:12.119> but<00:45:12.630> it's<00:45:12.810> not<00:45:13.470> as 00:45:13.670 --> 00:45:13.680 align:start position:0% they can be also used but it's not as 00:45:13.680 --> 00:45:17.060 align:start position:0% they can be also used but it's not as straightforward<00:45:14.100> and<00:45:15.230> it<00:45:16.230> can<00:45:16.440> be<00:45:16.619> used<00:45:16.800> also 00:45:17.060 --> 00:45:17.070 align:start position:0% straightforward and it can be used also 00:45:17.070 --> 00:45:21.400 align:start position:0% straightforward and it can be used also with<00:45:18.170> USB<00:45:19.170> card<00:45:19.680> readers<00:45:20.040> which<00:45:20.250> are<00:45:20.460> also 00:45:21.400 --> 00:45:21.410 align:start position:0% with USB card readers which are also 00:45:21.410 --> 00:45:24.890 align:start position:0% with USB card readers which are also quite<00:45:22.410> common<00:45:22.440> to<00:45:22.920> find<00:45:23.100> actually<00:45:23.609> so<00:45:24.600> it<00:45:24.750> is 00:45:24.890 --> 00:45:24.900 align:start position:0% quite common to find actually so it is 00:45:24.900 --> 00:45:27.050 align:start position:0% quite common to find actually so it is the<00:45:25.830> second<00:45:26.130> thing<00:45:26.310> is<00:45:26.490> for<00:45:26.700> me<00:45:26.790> to<00:45:27.030> be 00:45:27.050 --> 00:45:27.060 align:start position:0% the second thing is for me to be 00:45:27.060 --> 00:45:31.340 align:start position:0% the second thing is for me to be convenient<00:45:27.720> and<00:45:28.140> secure<00:45:29.100> and<00:45:29.960> for<00:45:30.960> purpose 00:45:31.340 --> 00:45:31.350 align:start position:0% convenient and secure and for purpose 00:45:31.350 --> 00:45:32.260 align:start position:0% convenient and secure and for purpose limits 00:45:32.260 --> 00:45:32.270 align:start position:0% limits 00:45:32.270 --> 00:45:35.480 align:start position:0% limits that's<00:45:33.270> my<00:45:33.810> answer<00:45:34.320> your<00:45:34.530> question<00:45:34.890> and<00:45:35.340> also 00:45:35.480 --> 00:45:35.490 align:start position:0% that's my answer your question and also 00:45:35.490 --> 00:45:37.970 align:start position:0% that's my answer your question and also products<00:45:36.240> because<00:45:36.540> it's<00:45:36.720> like<00:45:36.960> something 00:45:37.970 --> 00:45:37.980 align:start position:0% products because it's like something 00:45:37.980 --> 00:45:41.990 align:start position:0% products because it's like something she<00:45:38.220> that<00:45:38.820> you<00:45:38.910> came<00:45:39.090> by<00:45:40.160> yep<00:45:41.160> it's<00:45:41.490> easier<00:45:41.760> to 00:45:41.990 --> 00:45:42.000 align:start position:0% she that you came by yep it's easier to 00:45:42.000 --> 00:45:46.010 align:start position:0% she that you came by yep it's easier to buy<00:45:42.210> five<00:45:42.480> of<00:45:42.690> your<00:45:42.869> friends<00:45:43.730> so<00:45:44.730> I<00:45:44.760> mean<00:45:45.020> for 00:45:46.010 --> 00:45:46.020 align:start position:0% buy five of your friends so I mean for 00:45:46.020 --> 00:45:47.330 align:start position:0% buy five of your friends so I mean for the<00:45:46.140> physics<00:45:46.410> on<00:45:46.590> sorry<00:45:46.740> that<00:45:46.920> something's 00:45:47.330 --> 00:45:47.340 align:start position:0% the physics on sorry that something's 00:45:47.340 --> 00:45:49.310 align:start position:0% the physics on sorry that something's kind<00:45:47.460> of<00:45:47.700> music<00:45:47.940> on<00:45:48.060> the<00:45:48.150> security<00:45:48.630> so<00:45:49.140> there's 00:45:49.310 --> 00:45:49.320 align:start position:0% kind of music on the security so there's 00:45:49.320 --> 00:45:51.890 align:start position:0% kind of music on the security so there's the<00:45:49.530> software<00:45:49.830> and<00:45:50.340> the<00:45:50.430> hardware<00:45:50.460> itself<00:45:51.180> not 00:45:51.890 --> 00:45:51.900 align:start position:0% the software and the hardware itself not 00:45:51.900 --> 00:45:54.500 align:start position:0% the software and the hardware itself not very<00:45:52.140> pretty<00:45:52.380> open<00:45:52.680> source<00:45:52.950> so<00:45:53.160> it's<00:45:53.480> can<00:45:54.480> be 00:45:54.500 --> 00:45:54.510 align:start position:0% very pretty open source so it's can be 00:45:54.510 --> 00:45:57.380 align:start position:0% very pretty open source so it's can be edited<00:45:54.720> and<00:45:55.380> the<00:45:56.100> hardware<00:45:56.520> which<00:45:56.790> is<00:45:56.820> secure 00:45:57.380 --> 00:45:57.390 align:start position:0% edited and the hardware which is secure 00:45:57.390 --> 00:46:01.460 align:start position:0% edited and the hardware which is secure elements<00:45:57.810> is<00:45:58.140> I<00:45:58.890> mean<00:45:59.510> these<00:46:00.510> have<00:46:00.780> accounts 00:46:01.460 --> 00:46:01.470 align:start position:0% elements is I mean these have accounts 00:46:01.470 --> 00:46:04.609 align:start position:0% elements is I mean these have accounts usually<00:46:02.340> certified<00:46:03.119> meet<00:46:03.480> the<00:46:03.990> hardware<00:46:04.350> prod 00:46:04.609 --> 00:46:04.619 align:start position:0% usually certified meet the hardware prod 00:46:04.619 --> 00:46:06.590 align:start position:0% usually certified meet the hardware prod products<00:46:05.369> these<00:46:05.490> ones<00:46:05.760> are<00:46:05.910> from<00:46:06.030> any<00:46:06.330> speed 00:46:06.590 --> 00:46:06.600 align:start position:0% products these ones are from any speed 00:46:06.600 --> 00:46:09.349 align:start position:0% products these ones are from any speed for<00:46:06.720> instance<00:46:07.020> from<00:46:07.619> whom<00:46:07.800> any<00:46:08.250> speed<00:46:08.640> yeah 00:46:09.349 --> 00:46:09.359 align:start position:0% for instance from whom any speed yeah 00:46:09.359 --> 00:46:11.480 align:start position:0% for instance from whom any speed yeah which<00:46:09.869> is<00:46:10.050> one<00:46:10.530> of<00:46:10.619> the<00:46:10.740> main<00:46:10.920> supplier<00:46:11.340> of 00:46:11.480 --> 00:46:11.490 align:start position:0% which is one of the main supplier of 00:46:11.490 --> 00:46:14.900 align:start position:0% which is one of the main supplier of Java<00:46:11.880> cause<00:46:12.800> they<00:46:13.800> are<00:46:13.950> the<00:46:14.580> Faro 00:46:14.900 --> 00:46:14.910 align:start position:0% Java cause they are the Faro 00:46:14.910 --> 00:46:16.490 align:start position:0% Java cause they are the Faro certification<00:46:15.840> program 00:46:16.490 --> 00:46:16.500 align:start position:0% certification program 00:46:16.500 --> 00:46:21.020 align:start position:0% certification program this<00:46:16.920> one<00:46:17.130> is<00:46:17.280> Yale<00:46:17.670> a<00:46:18.410> l5<00:46:19.410> +<00:46:19.650> certified<00:46:20.310> so 00:46:21.020 --> 00:46:21.030 align:start position:0% this one is Yale a l5 + certified so 00:46:21.030 --> 00:46:24.410 align:start position:0% this one is Yale a l5 + certified so that<00:46:21.330> follows<00:46:21.660> a<00:46:22.070> list<00:46:23.070> of<00:46:23.220> tests<00:46:23.670> to<00:46:24.119> test<00:46:24.300> the 00:46:24.410 --> 00:46:24.420 align:start position:0% that follows a list of tests to test the 00:46:24.420 --> 00:46:26.890 align:start position:0% that follows a list of tests to test the hardware<00:46:24.660> security<00:46:24.930> how<00:46:25.410> hard<00:46:25.650> it<00:46:25.859> is<00:46:25.980> with<00:46:26.250> a 00:46:26.890 --> 00:46:26.900 align:start position:0% hardware security how hard it is with a 00:46:26.900 --> 00:46:30.830 align:start position:0% hardware security how hard it is with a microscope<00:46:27.900> with<00:46:29.030> side-channel<00:46:30.030> attacks<00:46:30.060> to 00:46:30.830 --> 00:46:30.840 align:start position:0% microscope with side-channel attacks to 00:46:30.840 --> 00:46:32.870 align:start position:0% microscope with side-channel attacks to get<00:46:31.050> the<00:46:31.170> secret<00:46:31.500> out<00:46:31.530> so<00:46:31.980> the<00:46:32.100> awkward<00:46:32.640> price 00:46:32.870 --> 00:46:32.880 align:start position:0% get the secret out so the awkward price 00:46:32.880 --> 00:46:37.000 align:start position:0% get the secret out so the awkward price themselves<00:46:33.450> are<00:46:33.950> qualified<00:46:34.950> in<00:46:35.160> country<00:46:36.030> also 00:46:37.000 --> 00:46:37.010 align:start position:0% themselves are qualified in country also 00:46:37.010 --> 00:46:40.400 align:start position:0% themselves are qualified in country also thank<00:46:38.010> you<00:46:38.240> you<00:46:39.240> see<00:46:39.420> the<00:46:39.570> expensive<00:46:40.140> how 00:46:40.400 --> 00:46:40.410 align:start position:0% thank you you see the expensive how 00:46:40.410 --> 00:46:44.560 align:start position:0% thank you you see the expensive how expensive<00:46:41.390> how<00:46:42.390> inexpensive<00:46:42.840> is<00:46:43.170> a<00:46:43.290> card<00:46:43.560> yes 00:46:44.560 --> 00:46:44.570 align:start position:0% expensive how inexpensive is a card yes 00:46:44.570 --> 00:46:48.080 align:start position:0% expensive how inexpensive is a card yes it<00:46:45.570> really<00:46:45.810> depends<00:46:46.200> I<00:46:46.290> mean<00:46:46.880> like<00:46:47.880> we<00:46:48.000> were 00:46:48.080 --> 00:46:48.090 align:start position:0% it really depends I mean like we were 00:46:48.090 --> 00:46:49.880 align:start position:0% it really depends I mean like we were seeing<00:46:48.270> at<00:46:48.420> the<00:46:48.510> beginning 00:46:49.880 --> 00:46:49.890 align:start position:0% seeing at the beginning 00:46:49.890 --> 00:46:52.070 align:start position:0% seeing at the beginning several<00:46:50.430> parts<00:46:50.609> are<00:46:50.790> produced<00:46:50.940> by<00:46:51.300> millions<00:46:51.780> I 00:46:52.070 --> 00:46:52.080 align:start position:0% several parts are produced by millions I 00:46:52.080 --> 00:46:54.140 align:start position:0% several parts are produced by millions I mean<00:46:52.410> there<00:46:52.800> are<00:46:52.830> in<00:46:52.950> every<00:46:53.160> phones<00:46:53.580> and 00:46:54.140 --> 00:46:54.150 align:start position:0% mean there are in every phones and 00:46:54.150 --> 00:46:56.690 align:start position:0% mean there are in every phones and everything<00:46:54.240> that<00:46:54.750> is<00:46:55.020> a<00:46:55.140> car<00:46:55.380> so<00:46:56.220> they<00:46:56.369> can<00:46:56.520> be 00:46:56.690 --> 00:46:56.700 align:start position:0% everything that is a car so they can be 00:46:56.700 --> 00:46:58.880 align:start position:0% everything that is a car so they can be really<00:46:57.000> inexpensive<00:46:57.300> when<00:46:57.990> you<00:46:58.080> do<00:46:58.230> volumes<00:46:58.619> I 00:46:58.880 --> 00:46:58.890 align:start position:0% really inexpensive when you do volumes I 00:46:58.890 --> 00:47:00.560 align:start position:0% really inexpensive when you do volumes I mean<00:46:59.010> okay<00:46:59.250> the<00:46:59.609> question<00:47:00.000> of<00:47:00.119> the<00:47:00.210> price<00:47:00.420> is 00:47:00.560 --> 00:47:00.570 align:start position:0% mean okay the question of the price is 00:47:00.570 --> 00:47:01.880 align:start position:0% mean okay the question of the price is more<00:47:00.720> depending<00:47:01.109> on<00:47:01.200> your<00:47:01.290> relationship<00:47:01.859> with 00:47:01.880 --> 00:47:01.890 align:start position:0% more depending on your relationship with 00:47:01.890 --> 00:47:03.530 align:start position:0% more depending on your relationship with your<00:47:02.160> supplier<00:47:02.520> yeah 00:47:03.530 --> 00:47:03.540 align:start position:0% your supplier yeah 00:47:03.540 --> 00:47:05.540 align:start position:0% your supplier yeah but<00:47:03.900> roughly<00:47:04.380> I<00:47:04.440> mean<00:47:04.619> these<00:47:04.859> things<00:47:04.920> when<00:47:05.520> you 00:47:05.540 --> 00:47:05.550 align:start position:0% but roughly I mean these things when you 00:47:05.550 --> 00:47:07.640 align:start position:0% but roughly I mean these things when you manufacture<00:47:05.849> a<00:47:06.690> couple<00:47:07.140> of<00:47:07.230> thousands<00:47:07.619> you 00:47:07.640 --> 00:47:07.650 align:start position:0% manufacture a couple of thousands you 00:47:07.650 --> 00:47:10.070 align:start position:0% manufacture a couple of thousands you know<00:47:08.030> couple<00:47:09.030> of<00:47:09.150> dollars<00:47:09.510> and<00:47:09.930> your 00:47:10.070 --> 00:47:10.080 align:start position:0% know couple of dollars and your 00:47:10.080 --> 00:47:12.470 align:start position:0% know couple of dollars and your beautifies<00:47:10.500> dollars<00:47:10.859> for<00:47:11.190> such<00:47:11.640> an<00:47:11.790> hour<00:47:11.880> okay 00:47:12.470 --> 00:47:12.480 align:start position:0% beautifies dollars for such an hour okay 00:47:12.480 --> 00:47:16.010 align:start position:0% beautifies dollars for such an hour okay it's<00:47:12.990> quite<00:47:13.170> simple<00:47:14.300> is<00:47:15.300> it<00:47:15.450> possible<00:47:15.839> to 00:47:16.010 --> 00:47:16.020 align:start position:0% it's quite simple is it possible to 00:47:16.020 --> 00:47:18.140 align:start position:0% it's quite simple is it possible to source<00:47:16.320> different<00:47:16.830> form<00:47:17.099> factors<00:47:17.490> yeah<00:47:18.119> I 00:47:18.140 --> 00:47:18.150 align:start position:0% source different form factors yeah I 00:47:18.150 --> 00:47:20.839 align:start position:0% source different form factors yeah I mean<00:47:18.420> then<00:47:19.160> usually<00:47:20.160> down<00:47:20.369> these<00:47:20.609> form 00:47:20.839 --> 00:47:20.849 align:start position:0% mean then usually down these form 00:47:20.849 --> 00:47:22.609 align:start position:0% mean then usually down these form factors<00:47:21.180> or<00:47:21.510> they<00:47:21.599> can<00:47:21.750> be<00:47:21.869> just<00:47:21.900> this<00:47:22.170> single 00:47:22.609 --> 00:47:22.619 align:start position:0% factors or they can be just this single 00:47:22.619 --> 00:47:24.920 align:start position:0% factors or they can be just this single sim<00:47:22.980> card<00:47:23.250> without<00:47:23.430> the<00:47:23.670> antenna<00:47:24.089> for<00:47:24.660> phones 00:47:24.920 --> 00:47:24.930 align:start position:0% sim card without the antenna for phones 00:47:24.930 --> 00:47:30.230 align:start position:0% sim card without the antenna for phones but<00:47:25.250> some<00:47:26.250> suppliers<00:47:27.030> do<00:47:27.300> rings<00:47:29.030> some<00:47:30.030> do 00:47:30.230 --> 00:47:30.240 align:start position:0% but some suppliers do rings some do 00:47:30.240 --> 00:47:31.910 align:start position:0% but some suppliers do rings some do things<00:47:30.510> that<00:47:30.599> you<00:47:30.690> can<00:47:30.839> attach<00:47:31.230> to<00:47:31.260> physical 00:47:31.910 --> 00:47:31.920 align:start position:0% things that you can attach to physical 00:47:31.920 --> 00:47:34.820 align:start position:0% things that you can attach to physical objects<00:47:33.080> then<00:47:34.080> it's<00:47:34.230> settled 00:47:34.820 --> 00:47:34.830 align:start position:0% objects then it's settled 00:47:34.830 --> 00:47:38.270 align:start position:0% objects then it's settled the<00:47:35.640> guys<00:47:35.820> that<00:47:35.970> manufacture<00:47:36.510> is<00:47:38.130> up 00:47:38.270 --> 00:47:38.280 align:start position:0% the guys that manufacture is up 00:47:38.280 --> 00:47:41.690 align:start position:0% the guys that manufacture is up to<00:47:38.970> this<00:47:39.390> so<00:47:39.960> this<00:47:40.200> the<00:47:40.650> chip<00:47:40.920> that<00:47:41.160> is<00:47:41.310> here 00:47:41.690 --> 00:47:41.700 align:start position:0% to this so this the chip that is here 00:47:41.700 --> 00:47:43.910 align:start position:0% to this so this the chip that is here behind<00:47:41.910> this<00:47:42.270> is<00:47:42.450> from<00:47:42.750> one<00:47:42.960> manufacturer<00:47:43.619> and 00:47:43.910 --> 00:47:43.920 align:start position:0% behind this is from one manufacturer and 00:47:43.920 --> 00:47:46.310 align:start position:0% behind this is from one manufacturer and the<00:47:44.490> body<00:47:44.760> of<00:47:44.970> the<00:47:45.150> car<00:47:45.330> with<00:47:45.540> their<00:47:45.810> ten<00:47:46.109> nice 00:47:46.310 --> 00:47:46.320 align:start position:0% the body of the car with their ten nice 00:47:46.320 --> 00:47:48.829 align:start position:0% the body of the car with their ten nice meet<00:47:46.560> by<00:47:47.160> another<00:47:47.460> manufacturer<00:47:48.030> so<00:47:48.420> this<00:47:48.630> can 00:47:48.829 --> 00:47:48.839 align:start position:0% meet by another manufacturer so this can 00:47:48.839 --> 00:47:53.829 align:start position:0% meet by another manufacturer so this can be<00:47:48.869> even<00:47:49.290> embedded<00:47:49.830> in<00:47:50.810> electronic<00:47:51.810> devices 00:47:53.829 --> 00:47:53.839 align:start position:0% be even embedded in electronic devices 00:47:53.839 --> 00:47:56.329 align:start position:0% be even embedded in electronic devices last<00:47:54.839> question<00:47:55.230> I<00:47:55.349> was<00:47:55.589> late<00:47:55.859> can<00:47:56.099> I<00:47:56.160> still 00:47:56.329 --> 00:47:56.339 align:start position:0% last question I was late can I still 00:47:56.339 --> 00:48:01.130 align:start position:0% last question I was late can I still have<00:47:56.400> our<00:47:56.640> either<00:47:58.849> them<00:47:59.849> think<00:48:00.480> there<00:48:01.020> are 00:48:01.130 --> 00:48:01.140 align:start position:0% have our either them think there are 00:48:01.140 --> 00:48:07.350 align:start position:0% have our either them think there are more<00:48:01.349> thank<00:48:01.890> you<00:48:02.070> it's<00:48:02.339> a<00:48:02.430> key 00:48:07.350 --> 00:48:07.360 align:start position:0% 00:48:07.360 --> 00:48:09.210 align:start position:0% [Music] 00:48:09.210 --> 00:48:09.220 align:start position:0% [Music] 00:48:09.220 --> 00:48:12.250 align:start position:0% [Music] it's<00:48:10.220> not<00:48:10.820> just<00:48:11.090> today<00:48:11.360> I<00:48:11.690> always<00:48:11.840> just<00:48:12.050> gonna 00:48:12.250 --> 00:48:12.260 align:start position:0% it's not just today I always just gonna 00:48:12.260 --> 00:48:15.460 align:start position:0% it's not just today I always just gonna ask<00:48:12.380> about<00:48:12.530> maybe<00:48:12.770> batteries<00:48:13.340> and<00:48:13.550> like<00:48:14.470> where 00:48:15.460 --> 00:48:15.470 align:start position:0% ask about maybe batteries and like where 00:48:15.470 --> 00:48:19.900 align:start position:0% ask about maybe batteries and like where where<00:48:15.890> can<00:48:16.040> i<00:48:16.190> source<00:48:16.520> these<00:48:17.410> in<00:48:18.410> volume<00:48:18.910> so 00:48:19.900 --> 00:48:19.910 align:start position:0% where can i source these in volume so 00:48:19.910 --> 00:48:22.840 align:start position:0% where can i source these in volume so there<00:48:20.750> are<00:48:20.870> so<00:48:21.290> different<00:48:21.650> actors<00:48:22.220> first<00:48:22.670> you 00:48:22.840 --> 00:48:22.850 align:start position:0% there are so different actors first you 00:48:22.850 --> 00:48:24.880 align:start position:0% there are so different actors first you need<00:48:22.970> to<00:48:23.000> find<00:48:23.330> a<00:48:23.480> chipset<00:48:23.840> provider<00:48:24.170> because 00:48:24.880 --> 00:48:24.890 align:start position:0% need to find a chipset provider because 00:48:24.890 --> 00:48:27.750 align:start position:0% need to find a chipset provider because that<00:48:25.160> manufacturer<00:48:25.700> the<00:48:25.850> cheaper<00:48:26.090> per<00:48:26.660> se<00:48:26.900> so 00:48:27.750 --> 00:48:27.760 align:start position:0% that manufacturer the cheaper per se so 00:48:27.760 --> 00:48:31.210 align:start position:0% that manufacturer the cheaper per se so downloads<00:48:28.900> such<00:48:29.900> a<00:48:29.930> big<00:48:30.260> number<00:48:30.440> this<00:48:30.860> is<00:48:30.920> an 00:48:31.210 --> 00:48:31.220 align:start position:0% downloads such a big number this is an 00:48:31.220 --> 00:48:38.410 align:start position:0% downloads such a big number this is an HP<00:48:32.050> engineer<00:48:34.330> and<00:48:36.010> has<00:48:37.010> been<00:48:37.420> eating 00:48:38.410 --> 00:48:38.420 align:start position:0% HP engineer and has been eating 00:48:38.420 --> 00:48:40.060 align:start position:0% HP engineer and has been eating something<00:48:38.810> yeah 00:48:40.060 --> 00:48:40.070 align:start position:0% something yeah 00:48:40.070 --> 00:48:42.460 align:start position:0% something yeah so<00:48:40.250> though<00:48:40.400> maybe<00:48:40.730> and<00:48:41.300> then<00:48:41.510> you<00:48:42.200> need<00:48:42.350> to 00:48:42.460 --> 00:48:42.470 align:start position:0% so though maybe and then you need to 00:48:42.470 --> 00:48:44.950 align:start position:0% so though maybe and then you need to find<00:48:42.710> a<00:48:42.920> manufacturer<00:48:43.400> that's<00:48:43.880> gonna<00:48:44.180> do<00:48:44.930> the 00:48:44.950 --> 00:48:44.960 align:start position:0% find a manufacturer that's gonna do the 00:48:44.960 --> 00:48:46.330 align:start position:0% find a manufacturer that's gonna do the process<00:48:45.440> that<00:48:45.530> week<00:48:45.680> they<00:48:45.800> describe<00:48:46.220> that 00:48:46.330 --> 00:48:46.340 align:start position:0% process that week they describe that 00:48:46.340 --> 00:48:49.030 align:start position:0% process that week they describe that bias<00:48:46.880> these<00:48:47.090> chipset<00:48:47.510> and<00:48:47.690> then<00:48:47.840> put<00:48:48.500> them<00:48:48.710> in 00:48:49.030 --> 00:48:49.040 align:start position:0% bias these chipset and then put them in 00:48:49.040 --> 00:48:51.700 align:start position:0% bias these chipset and then put them in the<00:48:49.340> physical<00:48:50.210> card<00:48:50.450> and<00:48:50.690> this<00:48:51.050> type<00:48:51.680> of 00:48:51.700 --> 00:48:51.710 align:start position:0% the physical card and this type of 00:48:51.710 --> 00:48:54.040 align:start position:0% the physical card and this type of scenario<00:48:51.950> there<00:48:52.340> are<00:48:52.400> hundreds<00:48:52.960> hundreds<00:48:53.960> I 00:48:54.040 --> 00:48:54.050 align:start position:0% scenario there are hundreds hundreds I 00:48:54.050 --> 00:48:57.010 align:start position:0% scenario there are hundreds hundreds I mean<00:48:54.370> how<00:48:55.370> self<00:48:55.670> man<00:48:55.880> factor<00:48:56.180> we<00:48:56.330> want<00:48:56.450> Europe 00:48:57.010 --> 00:48:57.020 align:start position:0% mean how self man factor we want Europe 00:48:57.020 --> 00:48:59.410 align:start position:0% mean how self man factor we want Europe New<00:48:57.230> York<00:48:57.500> France<00:48:58.100> actually<00:48:58.550> but<00:48:59.150> there<00:48:59.360> are 00:48:59.410 --> 00:48:59.420 align:start position:0% New York France actually but there are 00:48:59.420 --> 00:49:01.840 align:start position:0% New York France actually but there are tons<00:48:59.630> of<00:48:59.810> guys<00:48:59.990> that<00:49:00.170> know<00:49:00.380> how<00:49:00.530> to<00:49:00.820> create<00:49:01.820> a 00:49:01.840 --> 00:49:01.850 align:start position:0% tons of guys that know how to create a 00:49:01.850 --> 00:49:04.210 align:start position:0% tons of guys that know how to create a car<00:49:02.180> and<00:49:02.840> then<00:49:03.290> the<00:49:03.560> other<00:49:03.680> thing<00:49:03.950> you<00:49:04.070> can 00:49:04.210 --> 00:49:04.220 align:start position:0% car and then the other thing you can 00:49:04.220 --> 00:49:05.860 align:start position:0% car and then the other thing you can consider<00:49:04.640> is<00:49:04.820> the<00:49:04.940> level<00:49:05.180> of<00:49:05.270> security 00:49:05.860 --> 00:49:05.870 align:start position:0% consider is the level of security 00:49:05.870 --> 00:49:09.280 align:start position:0% consider is the level of security depending<00:49:06.470> on<00:49:06.530> what<00:49:06.740> you<00:49:07.010> download<00:49:08.140> at<00:49:09.140> the 00:49:09.280 --> 00:49:09.290 align:start position:0% depending on what you download at the 00:49:09.290 --> 00:49:12.100 align:start position:0% depending on what you download at the factory<00:49:09.590> level<00:49:09.650> in<00:49:10.490> the<00:49:10.640> car<00:49:10.850> the<00:49:11.780> level<00:49:12.020> of 00:49:12.100 --> 00:49:12.110 align:start position:0% factory level in the car the level of 00:49:12.110 --> 00:49:14.080 align:start position:0% factory level in the car the level of security<00:49:12.320> you<00:49:12.740> want<00:49:12.950> in<00:49:13.040> a<00:49:13.130> factory<00:49:13.430> what<00:49:13.910> we 00:49:14.080 --> 00:49:14.090 align:start position:0% security you want in a factory what we 00:49:14.090 --> 00:49:16.180 align:start position:0% security you want in a factory what we choose<00:49:14.330> to<00:49:14.390> ourselves<00:49:14.810> when<00:49:15.590> we<00:49:15.740> manufacture 00:49:16.180 --> 00:49:16.190 align:start position:0% choose to ourselves when we manufacture 00:49:16.190 --> 00:49:17.710 align:start position:0% choose to ourselves when we manufacture that<00:49:16.340> is<00:49:16.490> that<00:49:16.610> there's<00:49:16.760> not<00:49:16.910> any<00:49:16.970> secret<00:49:17.480> in 00:49:17.710 --> 00:49:17.720 align:start position:0% that is that there's not any secret in 00:49:17.720 --> 00:49:22.210 align:start position:0% that is that there's not any secret in the<00:49:17.840> car<00:49:18.020> minions<00:49:18.970> and<00:49:19.970> so<00:49:20.830> we<00:49:21.830> don't<00:49:21.980> want<00:49:22.130> to 00:49:22.210 --> 00:49:22.220 align:start position:0% the car minions and so we don't want to 00:49:22.220 --> 00:49:23.890 align:start position:0% the car minions and so we don't want to rely<00:49:22.370> on<00:49:22.460> the<00:49:22.610> security<00:49:23.060> of<00:49:23.090> the<00:49:23.330> manufacturer 00:49:23.890 --> 00:49:23.900 align:start position:0% rely on the security of the manufacturer 00:49:23.900 --> 00:49:25.270 align:start position:0% rely on the security of the manufacturer or<00:49:24.500> the<00:49:24.650> process 00:49:25.270 --> 00:49:25.280 align:start position:0% or the process 00:49:25.280 --> 00:49:28.000 align:start position:0% or the process the<00:49:25.430> cars<00:49:25.640> are<00:49:25.790> initialized<00:49:26.330> with<00:49:26.810> the<00:49:27.010> with 00:49:28.000 --> 00:49:28.010 align:start position:0% the cars are initialized with the with 00:49:28.010 --> 00:49:33.140 align:start position:0% the cars are initialized with the with the<00:49:28.160> with<00:49:28.370> the<00:49:28.490> phone 00:49:33.140 --> 00:49:33.150 align:start position:0% 00:49:33.150 --> 00:49:37.980 align:start position:0% you<00:49:34.150> intend<00:49:34.720> to<00:49:34.870> publish<00:49:35.830> an<00:49:36.130> application<00:49:36.990> to 00:49:37.980 --> 00:49:37.990 align:start position:0% you intend to publish an application to 00:49:37.990 --> 00:49:41.750 align:start position:0% you intend to publish an application to deter<00:49:38.320> intercultural<00:49:39.100> performing<00:49:39.930> yes 00:49:41.750 --> 00:49:41.760 align:start position:0% deter intercultural performing yes 00:49:41.760 --> 00:49:45.260 align:start position:0% deter intercultural performing yes establish<00:49:42.760> quiet<00:49:43.120> is<00:49:43.710> implementing<00:49:44.710> now 00:49:45.260 --> 00:49:45.270 align:start position:0% establish quiet is implementing now 00:49:45.270 --> 00:49:50.130 align:start position:0% establish quiet is implementing now Akita<00:49:46.270> and<00:49:46.480> it<00:49:47.170> is<00:49:47.290> also<00:49:47.500> so<00:49:48.400> not<00:49:49.140> statuses 00:49:50.130 --> 00:49:50.140 align:start position:0% Akita and it is also so not statuses 00:49:50.140 --> 00:49:51.870 align:start position:0% Akita and it is also so not statuses from<00:49:50.380> us<00:49:50.530> of<00:49:50.710> course<00:49:50.920> and<00:49:51.250> then<00:49:51.400> there<00:49:51.730> are 00:49:51.870 --> 00:49:51.880 align:start position:0% from us of course and then there are 00:49:51.880 --> 00:49:54.030 align:start position:0% from us of course and then there are third-party<00:49:52.590> application<00:49:53.590> which<00:49:53.740> also 00:49:54.030 --> 00:49:54.040 align:start position:0% third-party application which also 00:49:54.040 --> 00:49:56.190 align:start position:0% third-party application which also integrates<00:49:54.490> of<00:49:54.700> the<00:49:54.820> most<00:49:54.970> is<00:49:55.150> safe<00:49:55.720> and 00:49:56.190 --> 00:49:56.200 align:start position:0% integrates of the most is safe and 00:49:56.200 --> 00:50:01.350 align:start position:0% integrates of the most is safe and bullied<00:49:58.980> then<00:49:59.980> this<00:50:00.190> one<00:50:00.490> are<00:50:00.670> released<00:50:01.000> and 00:50:01.350 --> 00:50:01.360 align:start position:0% bullied then this one are released and 00:50:01.360 --> 00:50:13.760 align:start position:0% bullied then this one are released and then<00:50:01.750> there<00:50:01.900> are<00:50:02.370> people's<00:50:03.370> writing<00:50:11.460> system 00:50:13.760 --> 00:50:13.770 align:start position:0% then there are people's writing system 00:50:13.770 --> 00:50:17.520 align:start position:0% then there are people's writing system cost<00:50:14.770> the<00:50:15.610> cost<00:50:15.940> given<00:50:16.780> a<00:50:16.810> path<00:50:16.990> because<00:50:17.350> of 00:50:17.520 --> 00:50:17.530 align:start position:0% cost the cost given a path because of 00:50:17.530 --> 00:50:20.660 align:start position:0% cost the cost given a path because of the<00:50:17.710> operating<00:50:18.010> system<00:50:18.630> the<00:50:19.630> operating 00:50:20.660 --> 00:50:20.670 align:start position:0% the operating system the operating 00:50:20.670 --> 00:50:25.700 align:start position:0% the operating system the operating system<00:50:23.070> no<00:50:24.070> no<00:50:24.280> the<00:50:24.580> operating<00:50:25.120> system<00:50:25.510> is 00:50:25.700 --> 00:50:25.710 align:start position:0% system no no the operating system is 00:50:25.710 --> 00:50:28.290 align:start position:0% system no no the operating system is developed<00:50:26.710> by<00:50:26.830> an<00:50:26.980> XP<00:50:27.340> or<00:50:27.610> I<00:50:27.670> don't<00:50:27.850> know<00:50:28.030> maybe 00:50:28.290 --> 00:50:28.300 align:start position:0% developed by an XP or I don't know maybe 00:50:28.300 --> 00:50:31.860 align:start position:0% developed by an XP or I don't know maybe an<00:50:28.630> XP<00:50:28.930> buys<00:50:29.140> it<00:50:29.350> from<00:50:30.060> someone<00:50:31.060> else<00:50:31.240> but<00:50:31.510> they 00:50:31.860 --> 00:50:31.870 align:start position:0% an XP buys it from someone else but they 00:50:31.870 --> 00:50:33.660 align:start position:0% an XP buys it from someone else but they have<00:50:32.110> shipped<00:50:32.590> already<00:50:32.950> on<00:50:33.130> that<00:50:33.340> you<00:50:33.490> bought 00:50:33.660 --> 00:50:33.670 align:start position:0% have shipped already on that you bought 00:50:33.670 --> 00:50:37.590 align:start position:0% have shipped already on that you bought my<00:50:33.820> sauce<00:50:34.090> no<00:50:34.960> no<00:50:35.080> no<00:50:35.940> this<00:50:36.940> there<00:50:37.300> is<00:50:37.390> this 00:50:37.590 --> 00:50:37.600 align:start position:0% my sauce no no no this there is this 00:50:37.600 --> 00:50:38.190 align:start position:0% my sauce no no no this there is this thing 00:50:38.190 --> 00:50:38.200 align:start position:0% thing 00:50:38.200 --> 00:50:40.440 align:start position:0% thing so<00:50:38.590> the<00:50:38.740> Java<00:50:38.980> card<00:50:39.280> upland<00:50:39.730> that<00:50:39.880> we<00:50:40.030> wrote<00:50:40.270> is 00:50:40.440 --> 00:50:40.450 align:start position:0% so the Java card upland that we wrote is 00:50:40.450 --> 00:50:42.390 align:start position:0% so the Java card upland that we wrote is fully<00:50:40.750> open<00:50:41.020> source<00:50:41.050> and<00:50:41.830> it<00:50:42.100> can<00:50:42.250> be 00:50:42.390 --> 00:50:42.400 align:start position:0% fully open source and it can be 00:50:42.400 --> 00:50:44.790 align:start position:0% fully open source and it can be installed<00:50:42.490> on<00:50:42.910> any<00:50:43.030> Java<00:50:43.720> car<00:50:43.990> on<00:50:44.170> any<00:50:44.350> java 00:50:44.790 --> 00:50:44.800 align:start position:0% installed on any Java car on any java 00:50:44.800 --> 00:50:48.810 align:start position:0% installed on any Java car on any java craft<00:50:45.070> OS<00:50:45.870> platform<00:50:46.870> but<00:50:47.680> this<00:50:48.310> specification 00:50:48.810 --> 00:50:48.820 align:start position:0% craft OS platform but this specification 00:50:48.820 --> 00:50:52.410 align:start position:0% craft OS platform but this specification of<00:50:49.270> the<00:50:49.480> chips<00:50:50.160> under<00:50:51.160> NDA<00:50:51.520> and<00:50:51.820> we<00:50:52.000> don't<00:50:52.210> even 00:50:52.410 --> 00:50:52.420 align:start position:0% of the chips under NDA and we don't even 00:50:52.420 --> 00:50:55.040 align:start position:0% of the chips under NDA and we don't even ever<00:50:52.630> we<00:50:53.590> don't<00:50:53.770> you<00:50:54.070> don't<00:50:54.100> need<00:50:54.430> to<00:50:54.760> use<00:50:54.940> it 00:50:55.040 --> 00:50:55.050 align:start position:0% ever we don't you don't need to use it 00:50:55.050 --> 00:50:59.430 align:start position:0% ever we don't you don't need to use it and<00:50:56.070> to<00:50:57.070> rise<00:50:57.310> is<00:50:57.700> so<00:50:58.090> always<00:50:58.720> so<00:50:59.020> they<00:50:59.230> need 00:50:59.430 --> 00:50:59.440 align:start position:0% and to rise is so always so they need 00:50:59.440 --> 00:51:01.350 align:start position:0% and to rise is so always so they need the<00:50:59.560> specifications<00:51:00.490> and<00:51:00.640> so<00:51:00.790> they<00:51:01.000> are<00:51:01.090> all 00:51:01.350 --> 00:51:01.360 align:start position:0% the specifications and so they are all 00:51:01.360 --> 00:51:04.500 align:start position:0% the specifications and so they are all closed<00:51:01.810> source<00:51:02.430> by<00:51:03.430> default<00:51:03.970> and<00:51:04.210> engine 00:51:04.500 --> 00:51:04.510 align:start position:0% closed source by default and engine 00:51:04.510 --> 00:51:16.140 align:start position:0% closed source by default and engine there<00:51:04.750> is<00:51:04.780> no<00:51:05.050> other<00:51:05.110> way<00:51:11.730> no<00:51:13.620> no<00:51:14.620> because<00:51:15.150> if 00:51:16.140 --> 00:51:16.150 align:start position:0% there is no other way no no because if 00:51:16.150 --> 00:51:18.840 align:start position:0% there is no other way no no because if you<00:51:16.480> we<00:51:17.080> have<00:51:17.110> told<00:51:17.530> that<00:51:17.860> it's<00:51:18.460> better<00:51:18.670> to 00:51:18.840 --> 00:51:18.850 align:start position:0% you we have told that it's better to 00:51:18.850 --> 00:51:21.690 align:start position:0% you we have told that it's better to make<00:51:19.210> pinless<00:51:19.890> interaction<00:51:20.890> with<00:51:21.040> the<00:51:21.250> point 00:51:21.690 --> 00:51:21.700 align:start position:0% make pinless interaction with the point 00:51:21.700 --> 00:51:24.360 align:start position:0% make pinless interaction with the point of<00:51:21.850> sale<00:51:22.090> because<00:51:23.020> the<00:51:23.470> point<00:51:23.770> of<00:51:23.920> sale<00:51:24.100> is<00:51:24.220> on 00:51:24.360 --> 00:51:24.370 align:start position:0% of sale because the point of sale is on 00:51:24.370 --> 00:51:24.870 align:start position:0% of sale because the point of sale is on trust 00:51:24.870 --> 00:51:24.880 align:start position:0% trust 00:51:24.880 --> 00:51:26.610 align:start position:0% trust so<00:51:25.030> if<00:51:25.180> you<00:51:25.390> enter<00:51:25.810> your<00:51:25.840> field<00:51:26.350> you<00:51:26.590> are 00:51:26.610 --> 00:51:26.620 align:start position:0% so if you enter your field you are 00:51:26.620 --> 00:51:29.280 align:start position:0% so if you enter your field you are giving<00:51:27.040> you<00:51:27.100> a<00:51:27.250> secret<00:51:27.660> -<00:51:28.660> and<00:51:28.840> a<00:51:28.900> trusted 00:51:29.280 --> 00:51:29.290 align:start position:0% giving you a secret - and a trusted 00:51:29.290 --> 00:51:31.770 align:start position:0% giving you a secret - and a trusted device<00:51:29.350> so<00:51:30.280> it's<00:51:30.430> better<00:51:30.670> to<00:51:31.000> have<00:51:31.090> a<00:51:31.330> separate 00:51:31.770 --> 00:51:31.780 align:start position:0% device so it's better to have a separate 00:51:31.780 --> 00:51:34.140 align:start position:0% device so it's better to have a separate wallet<00:51:32.200> with<00:51:32.530> as<00:51:32.710> little<00:51:33.130> funds<00:51:33.640> and<00:51:33.940> you<00:51:34.030> know 00:51:34.140 --> 00:51:34.150 align:start position:0% wallet with as little funds and you know 00:51:34.150 --> 00:51:35.970 align:start position:0% wallet with as little funds and you know it's<00:51:34.300> cash<00:51:34.570> money<00:51:34.600> and<00:51:35.140> we<00:51:35.620> are<00:51:35.710> thinking 00:51:35.970 --> 00:51:35.980 align:start position:0% it's cash money and we are thinking 00:51:35.980 --> 00:51:40.170 align:start position:0% it's cash money and we are thinking about<00:51:36.310> ways<00:51:36.700> on<00:51:37.030> how<00:51:37.060> to<00:51:37.240> mitigate<00:51:39.180> trout 00:51:40.170 --> 00:51:40.180 align:start position:0% about ways on how to mitigate trout 00:51:40.180 --> 00:51:42.780 align:start position:0% about ways on how to mitigate trout today's<00:51:40.570> current<00:51:41.050> things<00:51:41.200> like<00:51:41.380> this<00:51:41.640> but<00:51:42.640> at 00:51:42.780 --> 00:51:42.790 align:start position:0% today's current things like this but at 00:51:42.790 --> 00:51:44.790 align:start position:0% today's current things like this but at least<00:51:42.970> you<00:51:43.210> don't<00:51:43.240> give<00:51:43.570> any<00:51:43.750> secret<00:51:44.260> it<00:51:44.650> was 00:51:44.790 --> 00:51:44.800 align:start position:0% least you don't give any secret it was 00:51:44.800 --> 00:51:46.650 align:start position:0% least you don't give any secret it was giving<00:51:45.100> them<00:51:45.220> in<00:51:45.460> maybe<00:51:45.850> you<00:51:45.910> are<00:51:46.030> giving<00:51:46.360> also 00:51:46.650 --> 00:51:46.660 align:start position:0% giving them in maybe you are giving also 00:51:46.660 --> 00:51:54.220 align:start position:0% giving them in maybe you are giving also pattern<00:51:47.110> to<00:51:47.290> your<00:51:47.440> other<00:51:47.590> pins<00:51:48.010> and<00:51:48.370> that's 00:51:54.220 --> 00:51:54.230 align:start position:0% 00:51:54.230 --> 00:51:57.550 align:start position:0% are<00:51:55.190> there<00:51:55.370> any<00:51:55.760> such<00:51:56.180> chips<00:51:56.480> on<00:51:56.990> the<00:51:57.140> market 00:51:57.550 --> 00:51:57.560 align:start position:0% are there any such chips on the market 00:51:57.560 --> 00:51:59.980 align:start position:0% are there any such chips on the market or<00:51:57.740> wherever<00:51:58.310> in<00:51:58.460> the<00:51:58.520> world<00:51:58.640> that<00:51:59.330> are<00:51:59.540> open 00:51:59.980 --> 00:51:59.990 align:start position:0% or wherever in the world that are open 00:51:59.990 --> 00:52:01.930 align:start position:0% or wherever in the world that are open sourced<00:52:00.380> out<00:52:00.590> to<00:52:00.800> the<00:52:00.920> lowest<00:52:01.670> level 00:52:01.930 --> 00:52:01.940 align:start position:0% sourced out to the lowest level 00:52:01.940 --> 00:52:03.940 align:start position:0% sourced out to the lowest level unfortunately<00:52:02.840> not 00:52:03.940 --> 00:52:03.950 align:start position:0% unfortunately not 00:52:03.950 --> 00:52:08.470 align:start position:0% unfortunately not I'm<00:52:05.140> having<00:52:06.140> a<00:52:06.260> close<00:52:06.530> look<00:52:06.980> to<00:52:07.670> the<00:52:07.850> base<00:52:08.150> 5 00:52:08.470 --> 00:52:08.480 align:start position:0% I'm having a close look to the base 5 00:52:08.480 --> 00:52:11.830 align:start position:0% I'm having a close look to the base 5 initiative<00:52:09.380> because<00:52:10.270> actually<00:52:11.270> this<00:52:11.780> thing 00:52:11.830 --> 00:52:11.840 align:start position:0% initiative because actually this thing 00:52:11.840 --> 00:52:14.770 align:start position:0% initiative because actually this thing is<00:52:12.290> an<00:52:12.530> article<00:52:12.890> controller<00:52:13.490> with<00:52:14.300> a<00:52:14.330> secure 00:52:14.770 --> 00:52:14.780 align:start position:0% is an article controller with a secure 00:52:14.780 --> 00:52:19.330 align:start position:0% is an article controller with a secure storage<00:52:15.080> and<00:52:16.240> if<00:52:17.240> you<00:52:17.570> order<00:52:18.140> our<00:52:18.500> accelerator 00:52:19.330 --> 00:52:19.340 align:start position:0% storage and if you order our accelerator 00:52:19.340 --> 00:52:21.330 align:start position:0% storage and if you order our accelerator for<00:52:19.960> photography 00:52:21.330 --> 00:52:21.340 align:start position:0% for photography 00:52:21.340 --> 00:52:25.900 align:start position:0% for photography the<00:52:22.390> cool<00:52:23.390> thing<00:52:23.840> what<00:52:24.200> make<00:52:24.380> this<00:52:24.590> secure<00:52:25.280> why 00:52:25.900 --> 00:52:25.910 align:start position:0% the cool thing what make this secure why 00:52:25.910 --> 00:52:28.060 align:start position:0% the cool thing what make this secure why an<00:52:26.180> ARM<00:52:26.330> chip<00:52:26.570> is<00:52:26.720> not<00:52:26.750> securing<00:52:27.380> this<00:52:27.560> one<00:52:27.770> is 00:52:28.060 --> 00:52:28.070 align:start position:0% an ARM chip is not securing this one is 00:52:28.070 --> 00:52:32.230 align:start position:0% an ARM chip is not securing this one is is<00:52:28.760> the<00:52:29.060> topology<00:52:29.600> of<00:52:30.200> the<00:52:30.700> transistor<00:52:31.700> is 00:52:32.230 --> 00:52:32.240 align:start position:0% is the topology of the transistor is 00:52:32.240 --> 00:52:36.220 align:start position:0% is the topology of the transistor is randomized<00:52:32.870> so<00:52:33.260> if<00:52:33.380> you<00:52:34.000> is<00:52:35.000> all<00:52:35.420> scaled<00:52:35.840> let's 00:52:36.220 --> 00:52:36.230 align:start position:0% randomized so if you is all scaled let's 00:52:36.230 --> 00:52:39.370 align:start position:0% randomized so if you is all scaled let's say<00:52:36.350> so<00:52:36.680> so<00:52:37.160> if<00:52:37.250> you<00:52:37.400> take<00:52:37.580> a<00:52:37.900> microscope<00:52:38.900> and 00:52:39.370 --> 00:52:39.380 align:start position:0% say so so if you take a microscope and 00:52:39.380 --> 00:52:44.410 align:start position:0% say so so if you take a microscope and you<00:52:39.490> open<00:52:40.490> whatever<00:52:41.060> in<00:52:41.690> the<00:52:41.840> cup<00:52:43.060> in<00:52:44.060> a 00:52:44.410 --> 00:52:44.420 align:start position:0% you open whatever in the cup in a 00:52:44.420 --> 00:52:46.300 align:start position:0% you open whatever in the cup in a microcontroller<00:52:44.900> you<00:52:45.320> can<00:52:45.500> see<00:52:45.650> exactly<00:52:46.070> okay 00:52:46.300 --> 00:52:46.310 align:start position:0% microcontroller you can see exactly okay 00:52:46.310 --> 00:52:47.890 align:start position:0% microcontroller you can see exactly okay this<00:52:46.460> is<00:52:46.610> the<00:52:46.790> ROM<00:52:46.940> this<00:52:47.150> is<00:52:47.330> the<00:52:47.480> roll 00:52:47.890 --> 00:52:47.900 align:start position:0% this is the ROM this is the roll 00:52:47.900 --> 00:52:50.050 align:start position:0% this is the ROM this is the roll you<00:52:48.740> open<00:52:49.040> this<00:52:49.190> one<00:52:49.400> that<00:52:49.580> you<00:52:49.670> don't<00:52:49.820> see 00:52:50.050 --> 00:52:50.060 align:start position:0% you open this one that you don't see 00:52:50.060 --> 00:52:54.280 align:start position:0% you open this one that you don't see anything<00:52:51.190> so<00:52:52.190> it's<00:52:52.340> so<00:52:53.240> yeah<00:52:53.630> I'm<00:52:53.840> looking<00:52:54.200> at 00:52:54.280 --> 00:52:54.290 align:start position:0% anything so it's so yeah I'm looking at 00:52:54.290 --> 00:52:56.170 align:start position:0% anything so it's so yeah I'm looking at the<00:52:54.440> risk<00:52:54.590> by<00:52:54.800> initiative<00:52:55.280> because<00:52:55.670> it<00:52:55.850> could 00:52:56.170 --> 00:52:56.180 align:start position:0% the risk by initiative because it could 00:52:56.180 --> 00:52:58.240 align:start position:0% the risk by initiative because it could be<00:52:56.360> used<00:52:56.540> at<00:52:56.750> the<00:52:56.900> basis<00:52:57.320> but<00:52:57.590> there<00:52:57.740> is<00:52:57.890> a<00:52:57.920> lot 00:52:58.240 --> 00:52:58.250 align:start position:0% be used at the basis but there is a lot 00:52:58.250 --> 00:53:02.320 align:start position:0% be used at the basis but there is a lot of<00:52:59.020> development<00:53:00.020> cost<00:53:00.790> to<00:53:01.790> bring<00:53:02.030> the<00:53:02.150> same 00:53:02.320 --> 00:53:02.330 align:start position:0% of development cost to bring the same 00:53:02.330 --> 00:53:07.620 align:start position:0% of development cost to bring the same level<00:53:02.390> of<00:53:02.750> security<00:53:03.280> so<00:53:04.280> to<00:53:04.340> make<00:53:04.580> this<00:53:04.730> really 00:53:07.620 --> 00:53:07.630 align:start position:0% 00:53:07.630 --> 00:53:10.390 align:start position:0% important<00:53:08.800> yes 00:53:10.390 --> 00:53:10.400 align:start position:0% important yes 00:53:10.400 --> 00:53:13.600 align:start position:0% important yes [Music] 00:53:13.600 --> 00:53:13.610 align:start position:0% [Music] 00:53:13.610 --> 00:53:15.910 align:start position:0% [Music] so<00:53:14.150> you<00:53:14.210> can<00:53:14.510> in<00:53:14.720> poverty<00:53:15.260> but<00:53:15.410> you<00:53:15.560> cannot 00:53:15.910 --> 00:53:15.920 align:start position:0% so you can in poverty but you cannot 00:53:15.920 --> 00:53:18.150 align:start position:0% so you can in poverty but you cannot make<00:53:16.160> strategy<00:53:16.850> all<00:53:17.360> right<00:53:17.600> even<00:53:17.810> with 00:53:18.150 --> 00:53:18.160 align:start position:0% make strategy all right even with 00:53:18.160 --> 00:53:21.130 align:start position:0% make strategy all right even with acetabular<00:53:19.160> backup<00:53:19.700> even<00:53:20.270> with<00:53:20.600> passport 00:53:21.130 --> 00:53:21.140 align:start position:0% acetabular backup even with passport 00:53:21.140 --> 00:53:23.830 align:start position:0% acetabular backup even with passport there<00:53:21.860> is<00:53:22.010> a<00:53:22.310> small<00:53:22.730> image<00:53:23.030> you<00:53:23.450> can<00:53:23.630> never 00:53:23.830 --> 00:53:23.840 align:start position:0% there is a small image you can never 00:53:23.840 --> 00:53:27.940 align:start position:0% there is a small image you can never export<00:53:24.380> the<00:53:24.560> master<00:53:25.160> key<00:53:26.200> but<00:53:27.200> that's<00:53:27.710> the 00:53:27.940 --> 00:53:27.950 align:start position:0% export the master key but that's the 00:53:27.950 --> 00:53:30.580 align:start position:0% export the master key but that's the master<00:53:28.310> key<00:53:28.520> generated<00:53:29.030> on<00:53:29.480> the<00:53:29.510> cadre<00:53:29.870> yes 00:53:30.580 --> 00:53:30.590 align:start position:0% master key generated on the cadre yes 00:53:30.590 --> 00:53:37.120 align:start position:0% master key generated on the cadre yes yeah<00:53:33.970> no<00:53:34.970> but<00:53:35.870> if<00:53:36.080> you<00:53:36.230> add<00:53:36.380> this<00:53:36.560> is<00:53:36.770> crazy 00:53:37.120 --> 00:53:37.130 align:start position:0% yeah no but if you add this is crazy 00:53:37.130 --> 00:53:44.530 align:start position:0% yeah no but if you add this is crazy already<00:53:42.370> but<00:53:43.370> if<00:53:43.430> you<00:53:43.490> have<00:53:43.640> an<00:53:43.790> expert<00:53:44.150> box<00:53:44.360> in 00:53:44.530 --> 00:53:44.540 align:start position:0% already but if you have an expert box in 00:53:44.540 --> 00:53:46.540 align:start position:0% already but if you have an expert box in the<00:53:44.720> API<00:53:44.990> for<00:53:45.380> some<00:53:45.590> yes<00:53:45.800> and<00:53:46.100> I<00:53:46.250> want<00:53:46.430> to 00:53:46.540 --> 00:53:46.550 align:start position:0% the API for some yes and I want to 00:53:46.550 --> 00:53:49.210 align:start position:0% the API for some yes and I want to display<00:53:46.880> NIT<00:53:47.120> export<00:53:48.050> function<00:53:48.590> allows<00:53:49.010> its 00:53:49.210 --> 00:53:49.220 align:start position:0% display NIT export function allows its 00:53:49.220 --> 00:53:53.560 align:start position:0% display NIT export function allows its port<00:53:49.460> in<00:53:49.610> public<00:53:50.000> keys<00:53:50.210> and<00:53:51.880> private<00:53:52.880> keys<00:53:53.150> but 00:53:53.560 --> 00:53:53.570 align:start position:0% port in public keys and private keys but 00:53:53.570 --> 00:53:55.990 align:start position:0% port in public keys and private keys but only<00:53:53.900> under<00:53:54.200> a<00:53:54.410> specific<00:53:54.680> sub<00:53:55.220> tree<00:53:55.460> as<00:53:55.970> a 00:53:55.990 --> 00:53:56.000 align:start position:0% only under a specific sub tree as a 00:53:56.000 --> 00:53:59.580 align:start position:0% only under a specific sub tree as a subtree<00:53:56.570> which<00:53:57.020> we<00:53:57.470> have<00:53:57.560> defined<00:53:57.710> with<00:53:58.130> a 00:53:59.580 --> 00:53:59.590 align:start position:0% subtree which we have defined with a 00:53:59.590 --> 00:54:25.330 align:start position:0% subtree which we have defined with a which<00:54:00.590> should<00:54:01.010> not<00:54:01.220> be<00:54:03.850> used<00:54:06.040> in<00:54:24.340> this 00:54:25.330 --> 00:54:25.340 align:start position:0% which should not be used in this 00:54:25.340 --> 00:54:28.480 align:start position:0% which should not be used in this application<00:54:26.140> system<00:54:27.140> but<00:54:27.620> I<00:54:27.830> think<00:54:28.160> we<00:54:28.400> are 00:54:28.480 --> 00:54:28.490 align:start position:0% application system but I think we are 00:54:28.490 --> 00:54:31.750 align:start position:0% application system but I think we are going<00:54:28.790> to<00:54:29.000> remove<00:54:29.240> it<00:54:29.360> because<00:54:30.350> actually<00:54:31.220> the 00:54:31.750 --> 00:54:31.760 align:start position:0% going to remove it because actually the 00:54:31.760 --> 00:54:35.710 align:start position:0% going to remove it because actually the better<00:54:32.000> way<00:54:32.320> is<00:54:33.320> probably<00:54:33.920> to<00:54:34.220> use<00:54:34.520> TC<00:54:35.330> wallet 00:54:35.710 --> 00:54:35.720 align:start position:0% better way is probably to use TC wallet 00:54:35.720 --> 00:54:37.540 align:start position:0% better way is probably to use TC wallet where<00:54:35.930> you<00:54:36.050> can<00:54:36.230> just<00:54:36.470> change<00:54:36.680> a<00:54:37.040> couple<00:54:37.070> so 00:54:37.540 --> 00:54:37.550 align:start position:0% where you can just change a couple so 00:54:37.550 --> 00:54:41.410 align:start position:0% where you can just change a couple so see<00:54:37.700> the<00:54:37.880> we<00:54:38.000> need 00:54:41.410 --> 00:54:41.420 align:start position:0% 00:54:41.420 --> 00:54:45.420 align:start position:0% you<00:54:41.869> always<00:54:42.140> have<00:54:42.380> to<00:54:42.730> war<00:54:43.730> against<00:54:44.299> God<00:54:44.599> and 00:54:45.420 --> 00:54:45.430 align:start position:0% you always have to war against God and 00:54:45.430 --> 00:54:51.550 align:start position:0% you always have to war against God and pray<00:54:46.430> together 00:54:51.550 --> 00:54:51.560 align:start position:0% 00:54:51.560 --> 00:54:59.960 align:start position:0% [Music] 00:54:59.960 --> 00:54:59.970 align:start position:0% 00:54:59.970 --> 00:55:06.369 align:start position:0% [Applause]