WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:35.670 align:start position:0% [Applause] 00:00:35.670 --> 00:00:35.680 align:start position:0% 00:00:35.680 --> 00:00:38.910 align:start position:0% today<00:00:36.430> topic<00:00:36.790> how<00:00:37.629> do<00:00:37.690> we<00:00:37.900> make<00:00:38.050> well<00:00:38.739> as 00:00:38.910 --> 00:00:38.920 align:start position:0% today topic how do we make well as 00:00:38.920 --> 00:00:41.490 align:start position:0% today topic how do we make well as secure<00:00:39.250> as<00:00:39.370> much<00:00:39.610> change<00:00:39.820> so<00:00:40.150> before<00:00:40.989> I<00:00:41.020> go 00:00:41.490 --> 00:00:41.500 align:start position:0% secure as much change so before I go 00:00:41.500 --> 00:00:44.520 align:start position:0% secure as much change so before I go into<00:00:41.710> application<00:00:42.840> let's<00:00:43.840> remind<00:00:44.140> will<00:00:44.379> be 00:00:44.520 --> 00:00:44.530 align:start position:0% into application let's remind will be 00:00:44.530 --> 00:00:47.220 align:start position:0% into application let's remind will be hundred<00:00:44.980> and<00:00:45.250> end<00:00:46.000> up<00:00:46.180> here<00:00:46.420> how<00:00:47.170> many 00:00:47.220 --> 00:00:47.230 align:start position:0% hundred and end up here how many 00:00:47.230 --> 00:00:50.910 align:start position:0% hundred and end up here how many security<00:00:48.000> web<00:00:49.000> apps<00:00:49.210> and<00:00:50.140> connect<00:00:50.440> web<00:00:50.739> and 00:00:50.910 --> 00:00:50.920 align:start position:0% security web apps and connect web and 00:00:50.920 --> 00:00:55.229 align:start position:0% security web apps and connect web and what<00:00:51.039> energy<00:00:51.629> so<00:00:52.649> what<00:00:53.649> was<00:00:54.250> very<00:00:54.519> pretty<00:00:54.699> much 00:00:55.229 --> 00:00:55.239 align:start position:0% what energy so what was very pretty much 00:00:55.239 --> 00:01:03.060 align:start position:0% what energy so what was very pretty much talking<00:00:55.570> as<00:00:59.219> far<00:01:00.219> as<00:01:00.370> much<00:01:01.120> progress<00:01:01.359> so<00:01:02.320> we 00:01:03.060 --> 00:01:03.070 align:start position:0% talking as far as much progress so we 00:01:03.070 --> 00:01:06.170 align:start position:0% talking as far as much progress so we spend<00:01:03.309> on<00:01:03.429> JavaScript<00:01:04.050> context 00:01:06.170 --> 00:01:06.180 align:start position:0% spend on JavaScript context 00:01:06.180 --> 00:01:23.850 align:start position:0% spend on JavaScript context okay<00:01:08.100> so<00:01:15.330> then<00:01:16.330> you<00:01:18.900> can<00:01:19.900> access<00:01:22.710> it<00:01:23.710> was 00:01:23.850 --> 00:01:23.860 align:start position:0% okay so then you can access it was 00:01:23.860 --> 00:01:28.710 align:start position:0% okay so then you can access it was Polina<00:01:27.300> stop 00:01:28.710 --> 00:01:28.720 align:start position:0% Polina stop 00:01:28.720 --> 00:01:32.580 align:start position:0% Polina stop well<00:01:29.190> every<00:01:30.190> time<00:01:30.570> and<00:01:31.570> then<00:01:31.750> continue<00:01:32.440> from 00:01:32.580 --> 00:01:32.590 align:start position:0% well every time and then continue from 00:01:32.590 --> 00:01:36.180 align:start position:0% well every time and then continue from there<00:01:32.800> we<00:01:33.520> have<00:01:33.670> me<00:01:34.440> confused<00:01:35.440> interceptions 00:01:36.180 --> 00:01:36.190 align:start position:0% there we have me confused interceptions 00:01:36.190 --> 00:01:37.920 align:start position:0% there we have me confused interceptions functional<00:01:36.910> pattern<00:01:37.210> user<00:01:37.420> don't<00:01:37.570> know<00:01:37.720> there 00:01:37.920 --> 00:01:37.930 align:start position:0% functional pattern user don't know there 00:01:37.930 --> 00:01:40.470 align:start position:0% functional pattern user don't know there sighing<00:01:38.260> so<00:01:38.830> what<00:01:38.950> we<00:01:39.040> do<00:01:39.190> right<00:01:39.430> here<00:01:39.700> says<00:01:39.910> if 00:01:40.470 --> 00:01:40.480 align:start position:0% sighing so what we do right here says if 00:01:40.480 --> 00:01:42.000 align:start position:0% sighing so what we do right here says if you're<00:01:40.660> following<00:01:40.780> us<00:01:41.170> a<00:01:41.350> transaction<00:01:41.890> is 00:01:42.000 --> 00:01:42.010 align:start position:0% you're following us a transaction is 00:01:42.010 --> 00:01:45.030 align:start position:0% you're following us a transaction is kind<00:01:42.250> of<00:01:42.340> comprehendible<00:01:42.940> and<00:01:43.570> then<00:01:44.170> with<00:01:45.010> a 00:01:45.030 --> 00:01:45.040 align:start position:0% kind of comprehendible and then with a 00:01:45.040 --> 00:01:47.370 align:start position:0% kind of comprehendible and then with a lot<00:01:45.250> of<00:01:45.360> variation<00:01:46.360> of<00:01:46.450> this<00:01:46.570> wonders<00:01:47.080> what<00:01:47.230> we 00:01:47.370 --> 00:01:47.380 align:start position:0% lot of variation of this wonders what we 00:01:47.380 --> 00:01:50.850 align:start position:0% lot of variation of this wonders what we do<00:01:47.470> we<00:01:47.590> like<00:01:47.710> for<00:01:47.950> us<00:01:48.070> now<00:01:49.060> we<00:01:49.120> have<00:01:49.360> the<00:01:49.860> tokens 00:01:50.850 --> 00:01:50.860 align:start position:0% do we like for us now we have the tokens 00:01:50.860 --> 00:01:51.930 align:start position:0% do we like for us now we have the tokens that<00:01:50.920> are<00:01:51.100> more<00:01:51.340> complicated<00:01:51.670> than 00:01:51.930 --> 00:01:51.940 align:start position:0% that are more complicated than 00:01:51.940 --> 00:01:53.040 align:start position:0% that are more complicated than traditionally<00:01:52.510> are<00:01:52.660> see<00:01:52.840> we<00:01:52.930> have 00:01:53.040 --> 00:01:53.050 align:start position:0% traditionally are see we have 00:01:53.050 --> 00:01:54.840 align:start position:0% traditionally are see we have competitive<00:01:53.470> they<00:01:53.920> actually<00:01:54.220> have<00:01:54.340> color<00:01:54.610> the 00:01:54.840 --> 00:01:54.850 align:start position:0% competitive they actually have color the 00:01:54.850 --> 00:01:57.780 align:start position:0% competitive they actually have color the usual<00:01:55.180> eyes<00:01:55.630> I<00:01:55.990> saw<00:01:56.320> a<00:01:56.650> high<00:01:56.980> special<00:01:57.430> and<00:01:57.670> it's 00:01:57.780 --> 00:01:57.790 align:start position:0% usual eyes I saw a high special and it's 00:01:57.790 --> 00:01:59.400 align:start position:0% usual eyes I saw a high special and it's what<00:01:58.000> we<00:01:58.120> do<00:01:58.240> it<00:01:58.360> hard<00:01:58.780> code<00:01:58.930> them<00:01:59.110> into<00:01:59.320> the 00:01:59.400 --> 00:01:59.410 align:start position:0% what we do it hard code them into the 00:01:59.410 --> 00:02:01.050 align:start position:0% what we do it hard code them into the browser<00:01:59.590> so<00:02:00.280> this<00:02:00.400> is<00:02:00.520> how<00:02:00.640> we<00:02:00.700> ended<00:02:00.910> up<00:02:01.000> here 00:02:01.050 --> 00:02:01.060 align:start position:0% browser so this is how we ended up here 00:02:01.060 --> 00:02:05.040 align:start position:0% browser so this is how we ended up here so<00:02:01.840> this<00:02:02.260> is<00:02:02.470> what<00:02:02.710> I<00:02:02.740> call<00:02:03.810> this<00:02:04.810> process 00:02:05.040 --> 00:02:05.050 align:start position:0% so this is what I call this process 00:02:05.050 --> 00:02:07.260 align:start position:0% so this is what I call this process everything<00:02:05.620> the<00:02:05.920> property<00:02:06.460> and<00:02:06.910> solving 00:02:07.260 --> 00:02:07.270 align:start position:0% everything the property and solving 00:02:07.270 --> 00:02:08.969 align:start position:0% everything the property and solving immediately<00:02:07.840> within<00:02:08.050> the<00:02:08.350> most<00:02:08.649> ready 00:02:08.969 --> 00:02:08.979 align:start position:0% immediately within the most ready 00:02:08.979 --> 00:02:11.790 align:start position:0% immediately within the most ready solution<00:02:09.280> voice<00:02:10.410> recording<00:02:11.410> the<00:02:11.500> design 00:02:11.790 --> 00:02:11.800 align:start position:0% solution voice recording the design 00:02:11.800 --> 00:02:17.000 align:start position:0% solution voice recording the design space<00:02:12.330> so<00:02:13.330> it's<00:02:14.110> like<00:02:14.739> there's<00:02:15.450> somewhere<00:02:16.450> a 00:02:17.000 --> 00:02:17.010 align:start position:0% space so it's like there's somewhere a 00:02:17.010 --> 00:02:21.900 align:start position:0% space so it's like there's somewhere a merest<00:02:18.010> accident<00:02:18.360> somewhere<00:02:19.360> else<00:02:19.590> it<00:02:20.760> is<00:02:21.760> our 00:02:21.900 --> 00:02:21.910 align:start position:0% merest accident somewhere else it is our 00:02:21.910 --> 00:02:24.720 align:start position:0% merest accident somewhere else it is our topic<00:02:22.300> is<00:02:22.830> hearing<00:02:23.830> the<00:02:23.920> better<00:02:24.100> way<00:02:24.280> which<00:02:24.580> is 00:02:24.720 --> 00:02:24.730 align:start position:0% topic is hearing the better way which is 00:02:24.730 --> 00:02:26.520 align:start position:0% topic is hearing the better way which is an<00:02:25.060> outward<00:02:25.270> probably<00:02:25.870> learn<00:02:26.050> how<00:02:26.200> to<00:02:26.230> solve 00:02:26.520 --> 00:02:26.530 align:start position:0% an outward probably learn how to solve 00:02:26.530 --> 00:02:40.040 align:start position:0% an outward probably learn how to solve so<00:02:28.800> the<00:02:29.800> problem<00:02:30.160> what 00:02:40.040 --> 00:02:40.050 align:start position:0% 00:02:40.050 --> 00:02:44.100 align:start position:0% test<00:02:41.430> people<00:02:42.430> wants<00:02:42.730> to<00:02:42.760> because<00:02:43.630> Webster<00:02:44.020> is 00:02:44.100 --> 00:02:44.110 align:start position:0% test people wants to because Webster is 00:02:44.110 --> 00:02:46.700 align:start position:0% test people wants to because Webster is a<00:02:44.290> centralized<00:02:44.680> blockchain<00:02:44.860> connected<00:02:45.550> and 00:02:46.700 --> 00:02:46.710 align:start position:0% a centralized blockchain connected and 00:02:46.710 --> 00:02:49.680 align:start position:0% a centralized blockchain connected and people<00:02:47.710> wants<00:02:48.070> to<00:02:48.220> see<00:02:48.400> the<00:02:48.490> truth<00:02:48.700> he<00:02:49.480> wants 00:02:49.680 --> 00:02:49.690 align:start position:0% people wants to see the truth he wants 00:02:49.690 --> 00:02:51.270 align:start position:0% people wants to see the truth he wants to<00:02:49.780> see<00:02:49.930> which<00:02:50.140> bit<00:02:50.380> of<00:02:50.500> information<00:02:50.710> on<00:02:51.070> what 00:02:51.270 --> 00:02:51.280 align:start position:0% to see which bit of information on what 00:02:51.280 --> 00:02:54.240 align:start position:0% to see which bit of information on what is<00:02:51.520> actually<00:02:51.760> under<00:02:52.360> my<00:02:53.200> cot<00:02:53.440> witness<00:02:53.830> they 00:02:54.240 --> 00:02:54.250 align:start position:0% is actually under my cot witness they 00:02:54.250 --> 00:02:56.130 align:start position:0% is actually under my cot witness they have<00:02:54.370> been<00:02:54.580> to<00:02:54.760> trust<00:02:55.030> the<00:02:55.150> way<00:02:55.300> the<00:02:56.020> other 00:02:56.130 --> 00:02:56.140 align:start position:0% have been to trust the way the other 00:02:56.140 --> 00:02:58.949 align:start position:0% have been to trust the way the other thing<00:02:56.260> is<00:02:56.610> operability<00:02:57.750> it's<00:02:58.750> quite 00:02:58.949 --> 00:02:58.959 align:start position:0% thing is operability it's quite 00:02:58.959 --> 00:03:01.620 align:start position:0% thing is operability it's quite important<00:02:59.410> because<00:02:59.850> traditionally<00:03:00.850> whether 00:03:01.620 --> 00:03:01.630 align:start position:0% important because traditionally whether 00:03:01.630 --> 00:03:03.870 align:start position:0% important because traditionally whether what<00:03:02.140> system<00:03:02.440> is<00:03:02.560> a<00:03:02.620> giant<00:03:02.980> and<00:03:03.520> nobody<00:03:03.760> help 00:03:03.870 --> 00:03:03.880 align:start position:0% what system is a giant and nobody help 00:03:03.880 --> 00:03:05.190 align:start position:0% what system is a giant and nobody help you<00:03:03.940> centralize<00:03:04.270> components<00:03:04.870> but<00:03:04.990> users 00:03:05.190 --> 00:03:05.200 align:start position:0% you centralize components but users 00:03:05.200 --> 00:03:07.620 align:start position:0% you centralize components but users expectation<00:03:06.010> is<00:03:06.160> to<00:03:06.280> buy<00:03:07.000> one<00:03:07.180> serving<00:03:07.570> a 00:03:07.620 --> 00:03:07.630 align:start position:0% expectation is to buy one serving a 00:03:07.630 --> 00:03:09.060 align:start position:0% expectation is to buy one serving a level<00:03:07.930> of<00:03:07.990> service<00:03:08.140> that<00:03:08.320> can<00:03:08.590> be<00:03:08.680> provided<00:03:08.890> by 00:03:09.060 --> 00:03:09.070 align:start position:0% level of service that can be provided by 00:03:09.070 --> 00:03:10.949 align:start position:0% level of service that can be provided by the<00:03:09.790> Hollywood<00:03:10.270> is<00:03:10.630> decentralized 00:03:10.949 --> 00:03:10.959 align:start position:0% the Hollywood is decentralized 00:03:10.959 --> 00:03:13.740 align:start position:0% the Hollywood is decentralized components<00:03:11.770> work<00:03:11.950> together<00:03:12.100> and<00:03:13.000> then<00:03:13.600> we 00:03:13.740 --> 00:03:13.750 align:start position:0% components work together and then we 00:03:13.750 --> 00:03:15.900 align:start position:0% components work together and then we have<00:03:13.870> the<00:03:13.959> policy<00:03:14.260> that<00:03:14.739> fewer<00:03:15.280> users<00:03:15.640> are 00:03:15.900 --> 00:03:15.910 align:start position:0% have the policy that fewer users are 00:03:15.910 --> 00:03:18.540 align:start position:0% have the policy that fewer users are always<00:03:16.060> active<00:03:16.780> expecting<00:03:17.770> that<00:03:17.950> Westar<00:03:18.400> is<00:03:18.520> a 00:03:18.540 --> 00:03:18.550 align:start position:0% always active expecting that Westar is a 00:03:18.550 --> 00:03:21.090 align:start position:0% always active expecting that Westar is a new<00:03:18.850> product<00:03:19.209> but<00:03:19.480> something<00:03:20.470> that<00:03:20.680> the<00:03:20.800> user 00:03:21.090 --> 00:03:21.100 align:start position:0% new product but something that the user 00:03:21.100 --> 00:03:23.670 align:start position:0% new product but something that the user is<00:03:21.400> able<00:03:21.520> to<00:03:21.730> catch<00:03:22.120> when<00:03:22.420> they<00:03:22.570> want<00:03:22.750> to<00:03:22.900> do 00:03:23.670 --> 00:03:23.680 align:start position:0% is able to catch when they want to do 00:03:23.680 --> 00:03:25.920 align:start position:0% is able to catch when they want to do without<00:03:23.950> giving<00:03:24.310> away<00:03:24.400> their<00:03:24.670> parasites<00:03:25.030> haha 00:03:25.920 --> 00:03:25.930 align:start position:0% without giving away their parasites haha 00:03:25.930 --> 00:03:28.470 align:start position:0% without giving away their parasites haha and<00:03:26.680> then<00:03:26.800> finally<00:03:27.220> you<00:03:27.280> have<00:03:27.310> security<00:03:27.820> which 00:03:28.470 --> 00:03:28.480 align:start position:0% and then finally you have security which 00:03:28.480 --> 00:03:30.870 align:start position:0% and then finally you have security which means<00:03:28.720> you<00:03:28.930> know<00:03:29.230> together<00:03:29.440> we<00:03:29.950> have<00:03:30.160> only<00:03:30.760> the 00:03:30.870 --> 00:03:30.880 align:start position:0% means you know together we have only the 00:03:30.880 --> 00:03:32.400 align:start position:0% means you know together we have only the custodian<00:03:31.360> of<00:03:31.390> their<00:03:31.570> asset<00:03:31.840> because<00:03:32.170> to<00:03:32.260> know 00:03:32.400 --> 00:03:32.410 align:start position:0% custodian of their asset because to know 00:03:32.410 --> 00:03:33.810 align:start position:0% custodian of their asset because to know what<00:03:32.560> they<00:03:32.620> are<00:03:32.680> doing<00:03:32.800> with<00:03:33.010> their<00:03:33.130> pet<00:03:33.370> the 00:03:33.810 --> 00:03:33.820 align:start position:0% what they are doing with their pet the 00:03:33.820 --> 00:03:35.580 align:start position:0% what they are doing with their pet the Sun<00:03:33.970> concession<00:03:34.600> there's<00:03:35.050> a<00:03:35.140> new<00:03:35.260> transaction 00:03:35.580 --> 00:03:35.590 align:start position:0% Sun concession there's a new transaction 00:03:35.590 --> 00:03:37.199 align:start position:0% Sun concession there's a new transaction which<00:03:36.190> we<00:03:36.340> have<00:03:36.430> any<00:03:36.610> other<00:03:36.820> questions 00:03:37.199 --> 00:03:37.209 align:start position:0% which we have any other questions 00:03:37.209 --> 00:03:39.030 align:start position:0% which we have any other questions detective<00:03:37.870> they<00:03:38.200> are<00:03:38.290> not<00:03:38.410> attending<00:03:38.739> to<00:03:38.830> be 00:03:39.030 --> 00:03:39.040 align:start position:0% detective they are not attending to be 00:03:39.040 --> 00:03:45.300 align:start position:0% detective they are not attending to be giving<00:03:39.250> away<00:03:40.920> now<00:03:41.920> given<00:03:42.700> this<00:03:43.239> is<00:03:44.310> that 00:03:45.300 --> 00:03:45.310 align:start position:0% giving away now given this is that 00:03:45.310 --> 00:03:49.860 align:start position:0% giving away now given this is that werster<00:03:45.519> is<00:03:45.760> going<00:03:45.970> to<00:03:46.060> solve<00:03:46.500> I<00:03:47.500> was<00:03:48.430> nervous 00:03:49.860 --> 00:03:49.870 align:start position:0% werster is going to solve I was nervous 00:03:49.870 --> 00:03:52.770 align:start position:0% werster is going to solve I was nervous to<00:03:50.290> analyze<00:03:50.700> how<00:03:51.700> well<00:03:51.879> it's<00:03:52.090> a<00:03:52.300> public 00:03:52.770 --> 00:03:52.780 align:start position:0% to analyze how well it's a public 00:03:52.780 --> 00:03:57.150 align:start position:0% to analyze how well it's a public assault<00:03:53.260> this<00:03:53.860> is<00:03:54.010> one<00:03:54.220> example<00:03:55.209> I<00:03:56.160> imagined 00:03:57.150 --> 00:03:57.160 align:start position:0% assault this is one example I imagined 00:03:57.160 --> 00:03:59.820 align:start position:0% assault this is one example I imagined it<00:03:57.280> is<00:03:57.940> called<00:03:58.300> teaching<00:03:58.989> in<00:03:59.140> the<00:03:59.200> garden<00:03:59.560> what 00:03:59.820 --> 00:03:59.830 align:start position:0% it is called teaching in the garden what 00:03:59.830 --> 00:04:03.420 align:start position:0% it is called teaching in the garden what it<00:03:59.920> does<00:04:00.069> is<00:04:00.220> it<00:04:01.120> draws<00:04:02.010> property<00:04:03.010> if<00:04:03.250> you<00:04:03.340> have 00:04:03.420 --> 00:04:03.430 align:start position:0% it does is it draws property if you have 00:04:03.430 --> 00:04:05.280 align:start position:0% it does is it draws property if you have a<00:04:03.459> property<00:04:03.790> at<00:04:04.120> any<00:04:04.209> point<00:04:04.540> then<00:04:04.930> he<00:04:05.080> was<00:04:05.170> to<00:04:05.260> a 00:04:05.280 --> 00:04:05.290 align:start position:0% a property at any point then he was to a 00:04:05.290 --> 00:04:08.190 align:start position:0% a property at any point then he was to a garden<00:04:05.650> network<00:04:06.010> that's<00:04:06.549> all<00:04:06.700> still<00:04:07.690> on<00:04:07.870> it<00:04:08.049> as 00:04:08.190 --> 00:04:08.200 align:start position:0% garden network that's all still on it as 00:04:08.200 --> 00:04:11.220 align:start position:0% garden network that's all still on it as a<00:04:08.700> tokenized<00:04:09.700> version<00:04:10.180> of<00:04:10.360> hello<00:04:10.569> world<00:04:10.629> they 00:04:11.220 --> 00:04:11.230 align:start position:0% a tokenized version of hello world they 00:04:11.230 --> 00:04:15.379 align:start position:0% a tokenized version of hello world they need<00:04:11.410> to<00:04:11.500> see<00:04:11.709> a<00:04:12.280> family<00:04:12.940> in<00:04:13.420> some<00:04:13.959> complex 00:04:15.379 --> 00:04:15.389 align:start position:0% need to see a family in some complex 00:04:15.389 --> 00:04:24.240 align:start position:0% need to see a family in some complex now<00:04:18.030> traditionally<00:04:21.870> earning<00:04:23.010> money<00:04:24.010> this 00:04:24.240 --> 00:04:24.250 align:start position:0% now traditionally earning money this 00:04:24.250 --> 00:04:26.640 align:start position:0% now traditionally earning money this region<00:04:24.760> this<00:04:24.910> is<00:04:24.970> hard<00:04:25.330> to<00:04:25.540> awakes<00:04:25.810> use 00:04:26.640 --> 00:04:26.650 align:start position:0% region this is hard to awakes use 00:04:26.650 --> 00:04:29.820 align:start position:0% region this is hard to awakes use request<00:04:27.160> data<00:04:27.340> and<00:04:28.120> web<00:04:28.330> service<00:04:28.830> JavaScript 00:04:29.820 --> 00:04:29.830 align:start position:0% request data and web service JavaScript 00:04:29.830 --> 00:04:33.090 align:start position:0% request data and web service JavaScript and<00:04:30.010> America<00:04:30.520> and<00:04:31.229> these<00:04:32.229> tiles<00:04:32.590> finish<00:04:32.919> name 00:04:33.090 --> 00:04:33.100 align:start position:0% and America and these tiles finish name 00:04:33.100 --> 00:04:35.100 align:start position:0% and America and these tiles finish name and<00:04:33.250> our<00:04:33.370> end<00:04:33.610> users<00:04:34.000> browser<00:04:34.270> search<00:04:34.479> access 00:04:35.100 --> 00:04:35.110 align:start position:0% and our end users browser search access 00:04:35.110 --> 00:04:38.000 align:start position:0% and our end users browser search access in<00:04:35.380> general<00:04:35.820> get<00:04:36.820> information<00:04:37.150> on<00:04:37.690> the<00:04:37.840> total 00:04:38.000 --> 00:04:38.010 align:start position:0% in general get information on the total 00:04:38.010 --> 00:04:41.070 align:start position:0% in general get information on the total SS<00:04:39.010> in<00:04:39.160> smartphones<00:04:39.639> that<00:04:39.820> functions<00:04:40.270> getting 00:04:41.070 --> 00:04:41.080 align:start position:0% SS in smartphones that functions getting 00:04:41.080 --> 00:04:43.500 align:start position:0% SS in smartphones that functions getting the<00:04:41.139> color<00:04:41.320> 50<00:04:41.800> painting<00:04:42.789> is<00:04:42.880> not<00:04:43.030> hat<00:04:43.240> and 00:04:43.500 --> 00:04:43.510 align:start position:0% the color 50 painting is not hat and 00:04:43.510 --> 00:04:47.240 align:start position:0% the color 50 painting is not hat and roll<00:04:43.750> it<00:04:43.900> a<00:04:44.080> really<00:04:44.380> nice<00:04:45.030> now<00:04:46.030> let's<00:04:46.870> look<00:04:47.020> at 00:04:47.240 --> 00:04:47.250 align:start position:0% roll it a really nice now let's look at 00:04:47.250 --> 00:04:50.129 align:start position:0% roll it a really nice now let's look at trusting<00:04:48.250> opportunity<00:04:49.060> promising<00:04:49.690> security 00:04:50.129 --> 00:04:50.139 align:start position:0% trusting opportunity promising security 00:04:50.139 --> 00:04:53.040 align:start position:0% trusting opportunity promising security so<00:04:51.010> stick<00:04:51.280> it<00:04:51.370> was<00:04:51.460> first<00:04:51.639> how<00:04:52.360> does<00:04:52.419> you<00:04:52.750> know 00:04:53.040 --> 00:04:53.050 align:start position:0% so stick it was first how does you know 00:04:53.050 --> 00:04:55.770 align:start position:0% so stick it was first how does you know that<00:04:53.919> the<00:04:54.580> Kentucky<00:04:55.030> team<00:04:55.090> is<00:04:55.570> actually 00:04:55.770 --> 00:04:55.780 align:start position:0% that the Kentucky team is actually 00:04:55.780 --> 00:04:58.740 align:start position:0% that the Kentucky team is actually rendered<00:04:56.410> using<00:04:56.800> the<00:04:57.010> data<00:04:57.570> but<00:04:58.570> this 00:04:58.740 --> 00:04:58.750 align:start position:0% rendered using the data but this 00:04:58.750 --> 00:05:02.370 align:start position:0% rendered using the data but this quantity<00:04:58.870> all<00:04:59.669> whether<00:05:00.669> or<00:05:00.760> not<00:05:00.910> the<00:05:01.389> the<00:05:02.050> web 00:05:02.370 --> 00:05:02.380 align:start position:0% quantity all whether or not the the web 00:05:02.380 --> 00:05:03.990 align:start position:0% quantity all whether or not the the web server<00:05:02.590> is<00:05:02.710> doing<00:05:02.950> that<00:05:03.130> in<00:05:03.250> JavaScript<00:05:03.460> to 00:05:03.990 --> 00:05:04.000 align:start position:0% server is doing that in JavaScript to 00:05:04.000 --> 00:05:06.779 align:start position:0% server is doing that in JavaScript to inquire<00:05:04.570> get<00:05:05.260> information<00:05:05.560> and<00:05:06.099> not<00:05:06.280> the 00:05:06.779 --> 00:05:06.789 align:start position:0% inquire get information and not the 00:05:06.789 --> 00:05:09.180 align:start position:0% inquire get information and not the balance<00:05:07.000> of<00:05:07.270> the<00:05:07.360> entire<00:05:07.450> contract<00:05:08.190> for 00:05:09.180 --> 00:05:09.190 align:start position:0% balance of the entire contract for 00:05:09.190 --> 00:05:12.420 align:start position:0% balance of the entire contract for another<00:05:09.340> and<00:05:09.820> then<00:05:10.389> we<00:05:10.660> offer<00:05:10.870> ability<00:05:11.380> so<00:05:12.039> if 00:05:12.420 --> 00:05:12.430 align:start position:0% another and then we offer ability so if 00:05:12.430 --> 00:05:15.120 align:start position:0% another and then we offer ability so if in<00:05:12.880> this<00:05:13.000> case<00:05:13.060> it<00:05:13.330> has<00:05:13.419> is<00:05:13.539> duty<00:05:14.050> to 00:05:15.120 --> 00:05:15.130 align:start position:0% in this case it has is duty to 00:05:15.130 --> 00:05:16.830 align:start position:0% in this case it has is duty to they're<00:05:15.460> the<00:05:15.910> new<00:05:16.030> one<00:05:16.210> is<00:05:16.330> sometimes<00:05:16.660> that 00:05:16.830 --> 00:05:16.840 align:start position:0% they're the new one is sometimes that 00:05:16.840 --> 00:05:20.790 align:start position:0% they're the new one is sometimes that players<00:05:17.110> flying<00:05:18.300> events<00:05:19.300> so<00:05:19.900> I<00:05:19.930> suppose<00:05:20.260> could 00:05:20.790 --> 00:05:20.800 align:start position:0% players flying events so I suppose could 00:05:20.800 --> 00:05:22.350 align:start position:0% players flying events so I suppose could be<00:05:20.860> keeping<00:05:21.190> a<00:05:21.280> daily<00:05:21.340> functions<00:05:21.970> like<00:05:22.120> this 00:05:22.350 --> 00:05:22.360 align:start position:0% be keeping a daily functions like this 00:05:22.360 --> 00:05:25.200 align:start position:0% be keeping a daily functions like this you<00:05:23.110> get<00:05:23.320> is<00:05:23.470> that<00:05:24.190> they<00:05:24.340> made<00:05:24.790> a<00:05:24.820> function<00:05:25.120> of 00:05:25.200 --> 00:05:25.210 align:start position:0% you get is that they made a function of 00:05:25.210 --> 00:05:28.410 align:start position:0% you get is that they made a function of X<00:05:25.360> it<00:05:25.840> is<00:05:25.960> here<00:05:26.410> is<00:05:26.620> if<00:05:26.770> you<00:05:26.890> have<00:05:26.920> a<00:05:27.220> them<00:05:27.420> then 00:05:28.410 --> 00:05:28.420 align:start position:0% X it is here is if you have a them then 00:05:28.420 --> 00:05:30.960 align:start position:0% X it is here is if you have a them then how<00:05:28.840> do<00:05:28.900> you<00:05:29.020> know<00:05:29.130> this<00:05:30.130> moving<00:05:30.550> part<00:05:30.760> of<00:05:30.850> the 00:05:30.960 --> 00:05:30.970 align:start position:0% how do you know this moving part of the 00:05:30.970 --> 00:05:32.550 align:start position:0% how do you know this moving part of the centralized<00:05:31.330> components<00:05:31.930> how<00:05:32.080> do<00:05:32.140> we<00:05:32.230> know<00:05:32.380> if 00:05:32.550 --> 00:05:32.560 align:start position:0% centralized components how do we know if 00:05:32.560 --> 00:05:34.500 align:start position:0% centralized components how do we know if the<00:05:32.740> website<00:05:32.920> has<00:05:33.220> updated<00:05:33.670> our<00:05:33.880> code<00:05:34.090> to<00:05:34.390> do 00:05:34.500 --> 00:05:34.510 align:start position:0% the website has updated our code to do 00:05:34.510 --> 00:05:36.420 align:start position:0% the website has updated our code to do this<00:05:34.630> functions<00:05:35.050> that's<00:05:35.590> it<00:05:35.860> all<00:05:36.010> fertility 00:05:36.420 --> 00:05:36.430 align:start position:0% this functions that's it all fertility 00:05:36.430 --> 00:05:40.310 align:start position:0% this functions that's it all fertility and<00:05:37.300> then<00:05:37.450> we<00:05:37.600> have<00:05:37.720> privacy<00:05:38.080> so<00:05:38.910> apparently 00:05:40.310 --> 00:05:40.320 align:start position:0% and then we have privacy so apparently 00:05:40.320 --> 00:05:41.730 align:start position:0% and then we have privacy so apparently in<00:05:41.320> charge 00:05:41.730 --> 00:05:41.740 align:start position:0% in charge 00:05:41.740 --> 00:05:44.190 align:start position:0% in charge and<00:05:42.100> what's<00:05:42.250> that<00:05:42.310> gets<00:05:42.610> the<00:05:42.700> data<00:05:43.110> from<00:05:44.110> the 00:05:44.190 --> 00:05:44.200 align:start position:0% and what's that gets the data from the 00:05:44.200 --> 00:05:46.200 align:start position:0% and what's that gets the data from the blockchain<00:05:44.410> and<00:05:44.770> rendered<00:05:45.160> on<00:05:45.340> web<00:05:45.550> but<00:05:46.030> what 00:05:46.200 --> 00:05:46.210 align:start position:0% blockchain and rendered on web but what 00:05:46.210 --> 00:05:49.290 align:start position:0% blockchain and rendered on web but what is<00:05:46.330> there<00:05:47.290> is<00:05:47.380> a<00:05:47.410> now<00:05:47.620> another<00:05:48.250> arrow<00:05:48.610> coming 00:05:49.290 --> 00:05:49.300 align:start position:0% is there is a now another arrow coming 00:05:49.300 --> 00:05:52.980 align:start position:0% is there is a now another arrow coming from<00:05:49.600> this<00:05:50.280> website<00:05:51.280> which<00:05:52.030> things<00:05:52.300> back<00:05:52.600> that 00:05:52.980 --> 00:05:52.990 align:start position:0% from this website which things back that 00:05:52.990 --> 00:05:57.000 align:start position:0% from this website which things back that have<00:05:53.230> to<00:05:53.350> do<00:05:53.440> a<00:05:53.470> self<00:05:54.600> so<00:05:55.600> the<00:05:56.110> user<00:05:56.830> doesn't 00:05:57.000 --> 00:05:57.010 align:start position:0% have to do a self so the user doesn't 00:05:57.010 --> 00:05:58.590 align:start position:0% have to do a self so the user doesn't know<00:05:57.190> how<00:05:57.370> much<00:05:57.490> what<00:05:57.760> serves<00:05:58.000> what<00:05:58.210> says<00:05:58.420> what 00:05:58.590 --> 00:05:58.600 align:start position:0% know how much what serves what says what 00:05:58.600 --> 00:06:01.770 align:start position:0% know how much what serves what says what I<00:05:58.720> can<00:05:58.960> learn<00:05:59.140> as<00:05:59.830> well<00:05:59.980> and<00:06:00.820> then<00:06:01.120> we<00:06:01.390> have<00:06:01.600> the 00:06:01.770 --> 00:06:01.780 align:start position:0% I can learn as well and then we have the 00:06:01.780 --> 00:06:04.410 align:start position:0% I can learn as well and then we have the final<00:06:02.440> the<00:06:02.890> security<00:06:03.370> issue<00:06:03.970> issues 00:06:04.410 --> 00:06:04.420 align:start position:0% final the security issue issues 00:06:04.420 --> 00:06:06.510 align:start position:0% final the security issue issues influence<00:06:04.960> and<00:06:05.200> transaction<00:06:05.770> essentially 00:06:06.510 --> 00:06:06.520 align:start position:0% influence and transaction essentially 00:06:06.520 --> 00:06:07.950 align:start position:0% influence and transaction essentially transaction<00:06:06.940> is<00:06:07.000> assembled<00:06:07.420> by<00:06:07.480> a<00:06:07.570> call<00:06:07.840> you 00:06:07.950 --> 00:06:07.960 align:start position:0% transaction is assembled by a call you 00:06:07.960 --> 00:06:09.660 align:start position:0% transaction is assembled by a call you don't<00:06:08.110> know<00:06:08.320> who<00:06:08.770> wrote<00:06:08.800> of<00:06:09.190> an<00:06:09.370> amount<00:06:09.580> of 00:06:09.660 --> 00:06:09.670 align:start position:0% don't know who wrote of an amount of 00:06:09.670 --> 00:06:14.730 align:start position:0% don't know who wrote of an amount of trust<00:06:10.380> so<00:06:11.520> in<00:06:12.520> fact<00:06:12.880> it<00:06:13.570> was<00:06:13.810> this<00:06:13.960> open<00:06:14.200> area 00:06:14.730 --> 00:06:14.740 align:start position:0% trust so in fact it was this open area 00:06:14.740 --> 00:06:18.810 align:start position:0% trust so in fact it was this open area that<00:06:15.450> this<00:06:16.450> model<00:06:16.750> is<00:06:17.110> move<00:06:17.410> on<00:06:17.610> this<00:06:18.610> model 00:06:18.810 --> 00:06:18.820 align:start position:0% that this model is move on this model 00:06:18.820 --> 00:06:20.940 align:start position:0% that this model is move on this model user<00:06:19.420> request<00:06:20.080> data<00:06:20.260> from<00:06:20.410> the<00:06:20.650> web<00:06:20.800> server 00:06:20.940 --> 00:06:20.950 align:start position:0% user request data from the web server 00:06:20.950 --> 00:06:22.380 align:start position:0% user request data from the web server what<00:06:21.310> somebody's<00:06:21.670> newsletters<00:06:22.240> about 00:06:22.380 --> 00:06:22.390 align:start position:0% what somebody's newsletters about 00:06:22.390 --> 00:06:23.560 align:start position:0% what somebody's newsletters about JavaScript 00:06:23.560 --> 00:06:23.570 align:start position:0% JavaScript 00:06:23.570 --> 00:06:25.770 align:start position:0% JavaScript I'm<00:06:24.050> sure<00:06:24.290> the<00:06:24.380> best<00:06:24.560> users<00:06:24.980> in<00:06:25.130> here<00:06:25.280> address 00:06:25.770 --> 00:06:25.780 align:start position:0% I'm sure the best users in here address 00:06:25.780 --> 00:06:31.720 align:start position:0% I'm sure the best users in here address user<00:06:27.940> human<00:06:28.940> then<00:06:29.810> gives<00:06:30.290> the<00:06:30.470> him<00:06:30.680> address<00:06:30.980> to 00:06:31.720 --> 00:06:31.730 align:start position:0% user human then gives the him address to 00:06:31.730 --> 00:06:33.730 align:start position:0% user human then gives the him address to the<00:06:31.820> server<00:06:32.060> and<00:06:32.360> certain<00:06:32.750> can<00:06:32.900> go<00:06:33.080> look<00:06:33.620> at 00:06:33.730 --> 00:06:33.740 align:start position:0% the server and certain can go look at 00:06:33.740 --> 00:06:36.040 align:start position:0% the server and certain can go look at the<00:06:33.860> kitten<00:06:34.130> data<00:06:34.310> results<00:06:34.940> there's<00:06:35.660> no<00:06:35.810> need 00:06:36.040 --> 00:06:36.050 align:start position:0% the kitten data results there's no need 00:06:36.050 --> 00:06:38.740 align:start position:0% the kitten data results there's no need for<00:06:36.440> the<00:06:37.310> users<00:06:37.640> and<00:06:37.790> have<00:06:38.030> had<00:06:38.180> access<00:06:38.510> to<00:06:38.570> be 00:06:38.740 --> 00:06:38.750 align:start position:0% for the users and have had access to be 00:06:38.750 --> 00:06:39.640 align:start position:0% for the users and have had access to be very<00:06:38.960> watchable 00:06:39.640 --> 00:06:39.650 align:start position:0% very watchable 00:06:39.650 --> 00:06:41.560 align:start position:0% very watchable if<00:06:39.890> user<00:06:40.220> doesn't<00:06:40.400> have<00:06:40.520> access<00:06:40.970> to<00:06:41.240> learn 00:06:41.560 --> 00:06:41.570 align:start position:0% if user doesn't have access to learn 00:06:41.570 --> 00:06:43.750 align:start position:0% if user doesn't have access to learn about<00:06:41.660> channel<00:06:42.230> how<00:06:42.590> does<00:06:42.740> user<00:06:42.950> know<00:06:43.190> any 00:06:43.750 --> 00:06:43.760 align:start position:0% about channel how does user know any 00:06:43.760 --> 00:06:45.670 align:start position:0% about channel how does user know any informations<00:06:44.270> true<00:06:44.420> in<00:06:44.570> fact<00:06:44.870> you<00:06:45.530> can 00:06:45.670 --> 00:06:45.680 align:start position:0% informations true in fact you can 00:06:45.680 --> 00:06:47.560 align:start position:0% informations true in fact you can produce<00:06:45.860> this<00:06:46.190> in<00:06:46.430> with<00:06:46.610> just<00:06:46.880> the<00:06:46.940> picture<00:06:47.300> a 00:06:47.560 --> 00:06:47.570 align:start position:0% produce this in with just the picture a 00:06:47.570 --> 00:06:49.890 align:start position:0% produce this in with just the picture a screenshot<00:06:48.200> of<00:06:48.560> the<00:06:48.740> kitten<00:06:49.010> sitting<00:06:49.130> on<00:06:49.430> the 00:06:49.890 --> 00:06:49.900 align:start position:0% screenshot of the kitten sitting on the 00:06:49.900 --> 00:06:53.050 align:start position:0% screenshot of the kitten sitting on the family<00:06:50.900> pattern<00:06:51.260> and<00:06:51.500> the<00:06:52.250> user<00:06:52.490> but<00:06:52.730> have<00:06:52.850> no 00:06:53.050 --> 00:06:53.060 align:start position:0% family pattern and the user but have no 00:06:53.060 --> 00:06:55.080 align:start position:0% family pattern and the user but have no way<00:06:53.210> to<00:06:53.240> know<00:06:53.390> if<00:06:53.930> this<00:06:54.140> is<00:06:54.260> his<00:06:54.410> kitchen<00:06:54.800> table 00:06:55.080 --> 00:06:55.090 align:start position:0% way to know if this is his kitchen table 00:06:55.090 --> 00:07:02.140 align:start position:0% way to know if this is his kitchen table not<00:06:57.550> so<00:06:59.110> the<00:07:00.110> solution<00:07:00.530> would<00:07:00.650> be<00:07:01.030> in<00:07:02.030> this 00:07:02.140 --> 00:07:02.150 align:start position:0% not so the solution would be in this 00:07:02.150 --> 00:07:03.790 align:start position:0% not so the solution would be in this very<00:07:02.360> simple<00:07:02.570> example<00:07:02.660> is<00:07:03.260> to<00:07:03.380> build<00:07:03.530> a<00:07:03.650> long 00:07:03.790 --> 00:07:03.800 align:start position:0% very simple example is to build a long 00:07:03.800 --> 00:07:07.630 align:start position:0% very simple example is to build a long time<00:07:04.040> nothing<00:07:04.790> is<00:07:05.150> an<00:07:05.300> area<00:07:05.750> secured<00:07:06.170> area<00:07:06.680> in 00:07:07.630 --> 00:07:07.640 align:start position:0% time nothing is an area secured area in 00:07:07.640 --> 00:07:10.870 align:start position:0% time nothing is an area secured area in an<00:07:07.790> open<00:07:08.060> space<00:07:08.150> that<00:07:08.540> it's<00:07:09.380> used<00:07:09.620> however<00:07:09.880> but 00:07:10.870 --> 00:07:10.880 align:start position:0% an open space that it's used however but 00:07:10.880 --> 00:07:16.110 align:start position:0% an open space that it's used however but independent<00:07:11.420> on<00:07:11.570> the<00:07:11.690> web<00:07:14.110> so<00:07:15.110> officially 00:07:16.110 --> 00:07:16.120 align:start position:0% independent on the web so officially 00:07:16.120 --> 00:07:18.430 align:start position:0% independent on the web so officially anomaly<00:07:17.120> I<00:07:17.150> probably<00:07:17.330> look<00:07:17.510> like<00:07:17.540> this<00:07:17.900> so 00:07:18.430 --> 00:07:18.440 align:start position:0% anomaly I probably look like this so 00:07:18.440 --> 00:07:20.440 align:start position:0% anomaly I probably look like this so normally<00:07:19.130> just<00:07:19.370> look<00:07:19.520> like<00:07:19.640> it<00:07:19.880> in<00:07:20.030> front<00:07:20.330> of 00:07:20.440 --> 00:07:20.450 align:start position:0% normally just look like it in front of 00:07:20.450 --> 00:07:28.350 align:start position:0% normally just look like it in front of others 00:07:28.350 --> 00:07:28.360 align:start position:0% 00:07:28.360 --> 00:07:31.720 align:start position:0% so<00:07:29.360> if<00:07:30.020> user<00:07:30.290> move<00:07:30.530> mouse<00:07:30.830> over<00:07:31.190> this<00:07:31.310> type 00:07:31.720 --> 00:07:31.730 align:start position:0% so if user move mouse over this type 00:07:31.730 --> 00:07:33.130 align:start position:0% so if user move mouse over this type which<00:07:32.090> shows<00:07:32.360> that<00:07:32.390> there's<00:07:32.780> our<00:07:32.930> wine 00:07:33.130 --> 00:07:33.140 align:start position:0% which shows that there's our wine 00:07:33.140 --> 00:07:35.080 align:start position:0% which shows that there's our wine Enclave<00:07:33.500> on<00:07:33.650> the<00:07:33.740> web<00:07:33.890> then<00:07:34.490> this<00:07:34.670> clicking<00:07:34.880> is 00:07:35.080 --> 00:07:35.090 align:start position:0% Enclave on the web then this clicking is 00:07:35.090 --> 00:07:36.340 align:start position:0% Enclave on the web then this clicking is highlighted<00:07:35.570> so<00:07:35.690> you<00:07:35.870> don't<00:07:36.110> know<00:07:36.170> this 00:07:36.340 --> 00:07:36.350 align:start position:0% highlighted so you don't know this 00:07:36.350 --> 00:07:38.830 align:start position:0% highlighted so you don't know this palette<00:07:36.710> omission<00:07:37.160> is<00:07:37.610> an<00:07:37.850> outlier<00:07:38.210> this<00:07:38.450> is 00:07:38.830 --> 00:07:38.840 align:start position:0% palette omission is an outlier this is 00:07:38.840 --> 00:07:40.480 align:start position:0% palette omission is an outlier this is salt<00:07:39.410> from<00:07:39.590> watching<00:07:39.950> truth 00:07:40.480 --> 00:07:40.490 align:start position:0% salt from watching truth 00:07:40.490 --> 00:07:44.500 align:start position:0% salt from watching truth so<00:07:41.180> with<00:07:42.140> this<00:07:42.350> boundary<00:07:42.980> construct<00:07:43.910> the 00:07:44.500 --> 00:07:44.510 align:start position:0% so with this boundary construct the 00:07:44.510 --> 00:07:46.780 align:start position:0% so with this boundary construct the partner<00:07:44.810> will<00:07:44.900> be<00:07:44.990> like<00:07:45.260> this<00:07:45.460> the<00:07:46.460> website 00:07:46.780 --> 00:07:46.790 align:start position:0% partner will be like this the website 00:07:46.790 --> 00:07:49.750 align:start position:0% partner will be like this the website request<00:07:47.270> through<00:07:47.480> healthy<00:07:48.320> team<00:07:48.500> this<00:07:49.430> time 00:07:49.750 --> 00:07:49.760 align:start position:0% request through healthy team this time 00:07:49.760 --> 00:07:51.430 align:start position:0% request through healthy team this time the<00:07:49.880> what<00:07:50.030> does<00:07:50.210> not<00:07:50.420> wasn't<00:07:50.870> enough<00:07:51.110> provide 00:07:51.430 --> 00:07:51.440 align:start position:0% the what does not wasn't enough provide 00:07:51.440 --> 00:07:53.050 align:start position:0% the what does not wasn't enough provide direct<00:07:51.920> instructions<00:07:52.430> that<00:07:52.550> have<00:07:52.700> got<00:07:52.940> this 00:07:53.050 --> 00:07:53.060 align:start position:0% direct instructions that have got this 00:07:53.060 --> 00:07:55.420 align:start position:0% direct instructions that have got this information<00:07:53.330> is<00:07:53.780> in<00:07:54.350> that<00:07:54.410> meditative<00:07:54.980> hold 00:07:55.420 --> 00:07:55.430 align:start position:0% information is in that meditative hold 00:07:55.430 --> 00:07:59.740 align:start position:0% information is in that meditative hold resonance<00:07:56.360> secure<00:07:56.660> complain<00:07:57.080> and<00:07:58.750> secure 00:07:59.740 --> 00:07:59.750 align:start position:0% resonance secure complain and secure 00:07:59.750 --> 00:08:03.160 align:start position:0% resonance secure complain and secure college<00:08:00.080> from<00:08:00.470> patrons<00:08:01.160> dream<00:08:01.810> sign<00:08:02.810> code 00:08:03.160 --> 00:08:03.170 align:start position:0% college from patrons dream sign code 00:08:03.170 --> 00:08:06.580 align:start position:0% college from patrons dream sign code provided<00:08:04.130> by<00:08:04.430> retro<00:08:04.940> huge<00:08:05.420> of<00:08:05.900> trustees 00:08:06.580 --> 00:08:06.590 align:start position:0% provided by retro huge of trustees 00:08:06.590 --> 00:08:09.559 align:start position:0% provided by retro huge of trustees forces<00:08:06.940> that 00:08:09.559 --> 00:08:09.569 align:start position:0% forces that 00:08:09.569 --> 00:08:11.869 align:start position:0% forces that a<00:08:09.599> cutie<00:08:10.199> privacy<00:08:11.159> is<00:08:11.219> protected<00:08:11.399> here 00:08:11.869 --> 00:08:11.879 align:start position:0% a cutie privacy is protected here 00:08:11.879 --> 00:08:13.609 align:start position:0% a cutie privacy is protected here because<00:08:12.210> he<00:08:12.389> does<00:08:12.539> not<00:08:12.569> ask<00:08:12.839> for<00:08:12.929> anything<00:08:13.289> so 00:08:13.609 --> 00:08:13.619 align:start position:0% because he does not ask for anything so 00:08:13.619 --> 00:08:15.230 align:start position:0% because he does not ask for anything so asking<00:08:14.369> you<00:08:14.429> the<00:08:14.550> truth<00:08:14.729> which<00:08:14.939> pretty<00:08:15.119> much 00:08:15.230 --> 00:08:15.240 align:start position:0% asking you the truth which pretty much 00:08:15.240 --> 00:08:17.089 align:start position:0% asking you the truth which pretty much familiar<00:08:15.719> to<00:08:16.020> know<00:08:16.169> whatever<00:08:16.589> no<00:08:16.889> need<00:08:17.009> to 00:08:17.089 --> 00:08:17.099 align:start position:0% familiar to know whatever no need to 00:08:17.099 --> 00:08:17.570 align:start position:0% familiar to know whatever no need to know 00:08:17.570 --> 00:08:17.580 align:start position:0% know 00:08:17.580 --> 00:08:19.879 align:start position:0% know now<00:08:17.789> you<00:08:17.849> haven't<00:08:18.059> you<00:08:18.240> and<00:08:18.709> what<00:08:19.709> is<00:08:19.800> the 00:08:19.879 --> 00:08:19.889 align:start position:0% now you haven't you and what is the 00:08:19.889 --> 00:08:21.279 align:start position:0% now you haven't you and what is the color<00:08:20.099> that<00:08:20.399> was<00:08:20.459> haven't<00:08:20.759> they<00:08:20.819> asked 00:08:21.279 --> 00:08:21.289 align:start position:0% color that was haven't they asked 00:08:21.289 --> 00:08:24.109 align:start position:0% color that was haven't they asked doesn't<00:08:22.289> even<00:08:22.439> talk<00:08:22.589> bankrupt<00:08:23.069> and<00:08:23.309> the 00:08:24.109 --> 00:08:24.119 align:start position:0% doesn't even talk bankrupt and the 00:08:24.119 --> 00:08:28.399 align:start position:0% doesn't even talk bankrupt and the kitchen<00:08:24.949> the<00:08:25.949> clean<00:08:26.729> side<00:08:27.149> Nicole<00:08:27.539> reading 00:08:28.399 --> 00:08:28.409 align:start position:0% kitchen the clean side Nicole reading 00:08:28.409 --> 00:08:30.019 align:start position:0% kitchen the clean side Nicole reading the<00:08:28.589> security<00:08:28.979> unveiled<00:08:29.339> provide 00:08:30.019 --> 00:08:30.029 align:start position:0% the security unveiled provide 00:08:30.029 --> 00:08:38.300 align:start position:0% the security unveiled provide information<00:08:32.899> then<00:08:33.899> recover<00:08:36.560> and<00:08:37.560> this<00:08:38.130> week 00:08:38.300 --> 00:08:38.310 align:start position:0% information then recover and this week 00:08:38.310 --> 00:08:42.889 align:start position:0% information then recover and this week post<00:08:39.380> with<00:08:40.380> a<00:08:40.409> security<00:08:40.829> company<00:08:41.449> so<00:08:42.449> that's 00:08:42.889 --> 00:08:42.899 align:start position:0% post with a security company so that's 00:08:42.899 --> 00:08:47.240 align:start position:0% post with a security company so that's really<00:08:43.310> listening<00:08:44.310> exit<00:08:45.060> game<00:08:45.209> first<00:08:45.959> so<00:08:46.709> the 00:08:47.240 --> 00:08:47.250 align:start position:0% really listening exit game first so the 00:08:47.250 --> 00:08:54.350 align:start position:0% really listening exit game first so the user<00:08:50.089> access<00:08:51.259> parity<00:08:52.259> it<00:08:52.470> doesn't<00:08:53.360> sacrifice 00:08:54.350 --> 00:08:54.360 align:start position:0% user access parity it doesn't sacrifice 00:08:54.360 --> 00:08:57.139 align:start position:0% user access parity it doesn't sacrifice anything<00:08:54.930> so<00:08:55.500> user<00:08:55.709> knows<00:08:55.980> insecure<00:08:56.819> today 00:08:57.139 --> 00:08:57.149 align:start position:0% anything so user knows insecure today 00:08:57.149 --> 00:09:00.439 align:start position:0% anything so user knows insecure today because<00:08:58.139> participated<00:08:59.100> so<00:09:00.000> that<00:09:00.180> we've<00:09:00.329> got 00:09:00.439 --> 00:09:00.449 align:start position:0% because participated so that we've got 00:09:00.449 --> 00:09:02.900 align:start position:0% because participated so that we've got trust<00:09:00.660> and<00:09:01.170> then<00:09:01.350> then<00:09:01.920> it<00:09:02.040> opportunity<00:09:02.730> if 00:09:02.900 --> 00:09:02.910 align:start position:0% trust and then then it opportunity if 00:09:02.910 --> 00:09:06.379 align:start position:0% trust and then then it opportunity if the<00:09:03.060> Kentucky<00:09:04.019> team<00:09:04.170> is<00:09:04.410> also<00:09:05.009> a<00:09:05.519> very<00:09:06.089> sleek 00:09:06.379 --> 00:09:06.389 align:start position:0% the Kentucky team is also a very sleek 00:09:06.389 --> 00:09:09.650 align:start position:0% the Kentucky team is also a very sleek is<00:09:06.980> okay<00:09:08.009> and<00:09:08.670> we<00:09:08.790> can<00:09:08.940> update<00:09:09.060> their<00:09:09.480> zone 00:09:09.650 --> 00:09:09.660 align:start position:0% is okay and we can update their zone 00:09:09.660 --> 00:09:12.499 align:start position:0% is okay and we can update their zone very<00:09:10.380> cold<00:09:10.920> to<00:09:11.399> manage<00:09:11.699> security<00:09:11.819> none<00:09:12.180> table 00:09:12.499 --> 00:09:12.509 align:start position:0% very cold to manage security none table 00:09:12.509 --> 00:09:13.939 align:start position:0% very cold to manage security none table was<00:09:12.690> happy<00:09:12.899> medium<00:09:13.380> because<00:09:13.620> what's<00:09:13.800> that 00:09:13.939 --> 00:09:13.949 align:start position:0% was happy medium because what's that 00:09:13.949 --> 00:09:16.550 align:start position:0% was happy medium because what's that only<00:09:14.220> care<00:09:14.399> about<00:09:14.430> what<00:09:14.850> we<00:09:14.939> regard<00:09:15.089> as<00:09:15.560> what's 00:09:16.550 --> 00:09:16.560 align:start position:0% only care about what we regard as what's 00:09:16.560 --> 00:09:20.420 align:start position:0% only care about what we regard as what's up<00:09:16.939> hours<00:09:17.939> or<00:09:18.630> keeping<00:09:18.930> garden<00:09:19.290> and<00:09:19.709> then<00:09:20.250> get 00:09:20.420 --> 00:09:20.430 align:start position:0% up hours or keeping garden and then get 00:09:20.430 --> 00:09:23.120 align:start position:0% up hours or keeping garden and then get pretty<00:09:20.930> as<00:09:21.930> I<00:09:22.110> demonstrated<00:09:22.620> like<00:09:22.889> you<00:09:23.040> are 00:09:23.120 --> 00:09:23.130 align:start position:0% pretty as I demonstrated like you are 00:09:23.130 --> 00:09:25.819 align:start position:0% pretty as I demonstrated like you are sparking<00:09:23.459> as<00:09:23.610> you<00:09:23.850> give<00:09:24.120> you<00:09:24.209> names<00:09:24.480> idea<00:09:25.439> to 00:09:25.819 --> 00:09:25.829 align:start position:0% sparking as you give you names idea to 00:09:25.829 --> 00:09:28.820 align:start position:0% sparking as you give you names idea to tell<00:09:26.160> you<00:09:26.250> locality<00:09:26.939> security<00:09:27.870> Ontario<00:09:27.990> has 00:09:28.820 --> 00:09:28.830 align:start position:0% tell you locality security Ontario has 00:09:28.830 --> 00:09:31.579 align:start position:0% tell you locality security Ontario has interprets<00:09:29.279> protect<00:09:29.790> me<00:09:29.940> forever<00:09:30.240> and<00:09:30.720> then 00:09:31.579 --> 00:09:31.589 align:start position:0% interprets protect me forever and then 00:09:31.589 --> 00:09:33.740 align:start position:0% interprets protect me forever and then we<00:09:31.680> will<00:09:31.769> get<00:09:31.860> security<00:09:32.490> said<00:09:32.700> if<00:09:33.089> any 00:09:33.740 --> 00:09:33.750 align:start position:0% we will get security said if any 00:09:33.750 --> 00:09:35.600 align:start position:0% we will get security said if any transaction<00:09:34.080> has<00:09:34.350> to<00:09:34.380> be<00:09:34.589> signed<00:09:34.740> it<00:09:35.490> is 00:09:35.600 --> 00:09:35.610 align:start position:0% transaction has to be signed it is 00:09:35.610 --> 00:09:37.759 align:start position:0% transaction has to be signed it is started<00:09:36.029> for<00:09:36.149> me<00:09:36.269> but<00:09:36.480> asking<00:09:37.290> certain<00:09:37.589> things 00:09:37.759 --> 00:09:37.769 align:start position:0% started for me but asking certain things 00:09:37.769 --> 00:09:39.440 align:start position:0% started for me but asking certain things to<00:09:37.920> be<00:09:37.950> done<00:09:38.190> and<00:09:38.459> that<00:09:38.550> action<00:09:39.209> is<00:09:39.300> performed 00:09:39.440 --> 00:09:39.450 align:start position:0% to be done and that action is performed 00:09:39.450 --> 00:09:43.310 align:start position:0% to be done and that action is performed in<00:09:39.959> gunplay<00:09:40.290> as<00:09:40.800> actually<00:09:42.230> following<00:09:43.230> the 00:09:43.310 --> 00:09:43.320 align:start position:0% in gunplay as actually following the 00:09:43.320 --> 00:09:45.079 align:start position:0% in gunplay as actually following the route<00:09:43.560> is<00:09:43.769> permissible 00:09:45.079 --> 00:09:45.089 align:start position:0% route is permissible 00:09:45.089 --> 00:09:51.819 align:start position:0% route is permissible so<00:09:45.329> this<00:09:45.510> will<00:09:46.310> separate<00:09:48.740> into<00:09:49.740> a<00:09:50.040> common<00:09:50.579> web 00:09:51.819 --> 00:09:51.829 align:start position:0% so this will separate into a common web 00:09:51.829 --> 00:09:56.030 align:start position:0% so this will separate into a common web now<00:09:52.829> if<00:09:53.519> you<00:09:53.670> ran<00:09:53.850> this<00:09:54.000> technology<00:09:54.890> you<00:09:55.890> need 00:09:56.030 --> 00:09:56.040 align:start position:0% now if you ran this technology you need 00:09:56.040 --> 00:09:59.180 align:start position:0% now if you ran this technology you need a<00:09:56.519> way<00:09:56.970> to<00:09:57.000> deliver<00:09:57.570> clean<00:09:57.899> signed<00:09:58.380> code<00:09:58.740> to 00:09:59.180 --> 00:09:59.190 align:start position:0% a way to deliver clean signed code to 00:09:59.190 --> 00:10:00.980 align:start position:0% a way to deliver clean signed code to the<00:09:59.279> security<00:09:59.610> company<00:09:59.730> and<00:10:00.720> that's<00:10:00.870> the 00:10:00.980 --> 00:10:00.990 align:start position:0% the security company and that's the 00:10:00.990 --> 00:10:03.530 align:start position:0% the security company and that's the technology<00:10:01.220> we<00:10:02.220> have<00:10:02.370> been<00:10:02.490> working<00:10:02.760> on<00:10:02.850> in 00:10:03.530 --> 00:10:03.540 align:start position:0% technology we have been working on in 00:10:03.540 --> 00:10:09.380 align:start position:0% technology we have been working on in spirit 00:10:09.380 --> 00:10:09.390 align:start position:0% 00:10:09.390 --> 00:10:12.829 align:start position:0% what<00:10:09.839> it<00:10:09.930> does<00:10:10.110> is<00:10:10.440> it<00:10:10.860> has<00:10:11.010> tokenization<00:10:11.839> like 00:10:12.829 --> 00:10:12.839 align:start position:0% what it does is it has tokenization like 00:10:12.839 --> 00:10:15.949 align:start position:0% what it does is it has tokenization like many<00:10:13.339> positions<00:10:14.339> and<00:10:14.700> things<00:10:14.910> what<00:10:15.720> you<00:10:15.810> are 00:10:15.949 --> 00:10:15.959 align:start position:0% many positions and things what you are 00:10:15.959 --> 00:10:17.930 align:start position:0% many positions and things what you are seeing<00:10:16.170> doesn't<00:10:16.529> come<00:10:16.649> home<00:10:16.940> Allegra 00:10:17.930 --> 00:10:17.940 align:start position:0% seeing doesn't come home Allegra 00:10:17.940 --> 00:10:19.940 align:start position:0% seeing doesn't come home Allegra attributes<00:10:18.480> like<00:10:18.660> how<00:10:18.870> to<00:10:18.930> get<00:10:19.290> colors<00:10:19.649> eye 00:10:19.940 --> 00:10:19.950 align:start position:0% attributes like how to get colors eye 00:10:19.950 --> 00:10:22.699 align:start position:0% attributes like how to get colors eye color<00:10:20.459> already<00:10:20.730> tea<00:10:21.120> and<00:10:21.450> then<00:10:22.050> in<00:10:22.560> their 00:10:22.699 --> 00:10:22.709 align:start position:0% color already tea and then in their 00:10:22.709 --> 00:10:24.319 align:start position:0% color already tea and then in their transactions<00:10:23.250> that<00:10:23.399> what<00:10:23.640> transactions<00:10:24.180> are 00:10:24.319 --> 00:10:24.329 align:start position:0% transactions that what transactions are 00:10:24.329 --> 00:10:31.690 align:start position:0% transactions that what transactions are possibility<00:10:25.200> anything<00:10:25.920> comment<00:10:26.390> can 00:10:31.690 --> 00:10:31.700 align:start position:0% 00:10:31.700 --> 00:10:33.940 align:start position:0% and<00:10:32.240> secured<00:10:32.660> rezoning<00:10:33.050> like<00:10:33.200> what<00:10:33.680> kind<00:10:33.890> of 00:10:33.940 --> 00:10:33.950 align:start position:0% and secured rezoning like what kind of 00:10:33.950 --> 00:10:37.000 align:start position:0% and secured rezoning like what kind of information<00:10:34.220> is<00:10:34.700> accept<00:10:35.320> and<00:10:36.320> secure<00:10:36.740> Enclave 00:10:37.000 --> 00:10:37.010 align:start position:0% information is accept and secure Enclave 00:10:37.010 --> 00:10:39.040 align:start position:0% information is accept and secure Enclave which<00:10:37.640> website<00:10:38.030> whether<00:10:38.780> or<00:10:38.870> not 00:10:39.040 --> 00:10:39.050 align:start position:0% which website whether or not 00:10:39.050 --> 00:10:42.460 align:start position:0% which website whether or not attestations<00:10:39.980> will<00:10:40.460> help<00:10:40.820> under<00:10:41.690> Montana<00:10:41.990> can 00:10:42.460 --> 00:10:42.470 align:start position:0% attestations will help under Montana can 00:10:42.470 --> 00:10:45.250 align:start position:0% attestations will help under Montana can be<00:10:42.620> forwarded<00:10:42.950> to<00:10:43.160> the<00:10:43.250> cyber<00:10:43.610> security<00:10:44.260> and 00:10:45.250 --> 00:10:45.260 align:start position:0% be forwarded to the cyber security and 00:10:45.260 --> 00:10:47.950 align:start position:0% be forwarded to the cyber security and then<00:10:45.440> we<00:10:45.650> have<00:10:45.860> permits<00:10:46.700> so<00:10:47.510> we<00:10:47.600> have<00:10:47.720> cars 00:10:47.950 --> 00:10:47.960 align:start position:0% then we have permits so we have cars 00:10:47.960 --> 00:10:52.090 align:start position:0% then we have permits so we have cars cars<00:10:48.830> a<00:10:49.280> visual<00:10:50.270> renderable<00:10:50.960> pattern<00:10:51.440> so<00:10:51.830> if<00:10:51.980> I 00:10:52.090 --> 00:10:52.100 align:start position:0% cars a visual renderable pattern so if I 00:10:52.100 --> 00:10:54.130 align:start position:0% cars a visual renderable pattern so if I have<00:10:52.250> a<00:10:52.280> key<00:10:52.430> card<00:10:52.700> much<00:10:53.270> too<00:10:53.510> short<00:10:53.660> in<00:10:53.930> email 00:10:54.130 --> 00:10:54.140 align:start position:0% have a key card much too short in email 00:10:54.140 --> 00:10:58.290 align:start position:0% have a key card much too short in email and<00:10:55.040> then<00:10:55.250> we<00:10:55.550> have<00:10:55.880> very<00:10:56.090> actions<00:10:56.600> actions 00:10:58.290 --> 00:10:58.300 align:start position:0% and then we have very actions actions 00:10:58.300 --> 00:11:02.320 align:start position:0% and then we have very actions actions other<00:10:59.300> things<00:10:59.720> that<00:11:00.620> perceptions<00:11:01.340> users<00:11:02.000> can 00:11:02.320 --> 00:11:02.330 align:start position:0% other things that perceptions users can 00:11:02.330 --> 00:11:06.100 align:start position:0% other things that perceptions users can compile<00:11:02.870> for<00:11:03.740> this<00:11:04.120> program<00:11:05.120> and<00:11:05.360> understand 00:11:06.100 --> 00:11:06.110 align:start position:0% compile for this program and understand 00:11:06.110 --> 00:11:08.680 align:start position:0% compile for this program and understand believes<00:11:06.410> this<00:11:07.190> actions<00:11:07.790> might<00:11:08.000> not<00:11:08.300> entirely 00:11:08.680 --> 00:11:08.690 align:start position:0% believes this actions might not entirely 00:11:08.690 --> 00:11:09.730 align:start position:0% believes this actions might not entirely provided<00:11:09.110> our<00:11:09.230> killer 00:11:09.730 --> 00:11:09.740 align:start position:0% provided our killer 00:11:09.740 --> 00:11:10.900 align:start position:0% provided our killer for<00:11:09.950> example<00:11:10.220> if<00:11:10.340> you<00:11:10.400> send<00:11:10.550> them<00:11:10.670> somewhere 00:11:10.900 --> 00:11:10.910 align:start position:0% for example if you send them somewhere 00:11:10.910 --> 00:11:13.240 align:start position:0% for example if you send them somewhere my<00:11:11.360> dear<00:11:11.540> let's<00:11:12.260> clarify<00:11:12.500> history<00:11:13.130> and 00:11:13.240 --> 00:11:13.250 align:start position:0% my dear let's clarify history and 00:11:13.250 --> 00:11:15.130 align:start position:0% my dear let's clarify history and provided<00:11:13.940> better<00:11:14.150> addition<00:11:14.660> contractor 00:11:15.130 --> 00:11:15.140 align:start position:0% provided better addition contractor 00:11:15.140 --> 00:11:18.280 align:start position:0% provided better addition contractor product<00:11:15.530> by<00:11:15.680> DIRECTV<00:11:16.460> then<00:11:17.150> you<00:11:17.870> has<00:11:18.260> a 00:11:18.280 --> 00:11:18.290 align:start position:0% product by DIRECTV then you has a 00:11:18.290 --> 00:11:20.470 align:start position:0% product by DIRECTV then you has a collateralizing<00:11:18.950> contract<00:11:19.520> author<00:11:19.820> can 00:11:20.470 --> 00:11:20.480 align:start position:0% collateralizing contract author can 00:11:20.480 --> 00:11:23.410 align:start position:0% collateralizing contract author can provide<00:11:20.750> an<00:11:20.900> action<00:11:21.170> that<00:11:21.290> is<00:11:21.670> apply<00:11:22.670> word<00:11:22.910> to 00:11:23.410 --> 00:11:23.420 align:start position:0% provide an action that is apply word to 00:11:23.420 --> 00:11:25.660 align:start position:0% provide an action that is apply word to use<00:11:23.630> its<00:11:24.320> best<00:11:24.500> actually<00:11:24.920> but<00:11:25.220> finally<00:11:25.580> you 00:11:25.660 --> 00:11:25.670 align:start position:0% use its best actually but finally you 00:11:25.670 --> 00:11:27.610 align:start position:0% use its best actually but finally you have<00:11:25.910> the<00:11:26.090> signatures<00:11:26.900> the<00:11:27.140> reason<00:11:27.350> I<00:11:27.410> put 00:11:27.610 --> 00:11:27.620 align:start position:0% have the signatures the reason I put 00:11:27.620 --> 00:11:29.740 align:start position:0% have the signatures the reason I put water<00:11:27.800> person<00:11:28.160> shows<00:11:28.400> up<00:11:28.610> here<00:11:28.880> is<00:11:29.360> because 00:11:29.740 --> 00:11:29.750 align:start position:0% water person shows up here is because 00:11:29.750 --> 00:11:31.780 align:start position:0% water person shows up here is because your<00:11:30.050> might<00:11:30.260> need<00:11:30.500> it<00:11:31.400> there<00:11:31.610> might<00:11:31.760> be 00:11:31.780 --> 00:11:31.790 align:start position:0% your might need it there might be 00:11:31.790 --> 00:11:33.520 align:start position:0% your might need it there might be multiple<00:11:32.090> source<00:11:32.510> of<00:11:32.660> trust<00:11:32.900> in<00:11:33.050> it<00:11:33.230> so<00:11:33.500> just 00:11:33.520 --> 00:11:33.530 align:start position:0% multiple source of trust in it so just 00:11:33.530 --> 00:11:36.520 align:start position:0% multiple source of trust in it so just as<00:11:33.800> I<00:11:33.920> was<00:11:34.010> explained<00:11:34.580> the<00:11:35.390> kitty<00:11:35.690> is<00:11:36.080> drawn<00:11:36.350> in 00:11:36.520 --> 00:11:36.530 align:start position:0% as I was explained the kitty is drawn in 00:11:36.530 --> 00:11:38.350 align:start position:0% as I was explained the kitty is drawn in with<00:11:36.680> code<00:11:36.980> assignment<00:11:37.370> by<00:11:37.670> echo<00:11:37.940> to<00:11:38.060> hit<00:11:38.210> him 00:11:38.350 --> 00:11:38.360 align:start position:0% with code assignment by echo to hit him 00:11:38.360 --> 00:11:40.600 align:start position:0% with code assignment by echo to hit him but<00:11:38.810> collateralization<00:11:39.320> of<00:11:39.710> Nikita<00:11:40.070> as<00:11:40.340> an 00:11:40.600 --> 00:11:40.610 align:start position:0% but collateralization of Nikita as an 00:11:40.610 --> 00:11:41.860 align:start position:0% but collateralization of Nikita as an action<00:11:40.910> that<00:11:40.970> can<00:11:41.030> be<00:11:41.240> done<00:11:41.360> in<00:11:41.540> teams<00:11:41.690> that 00:11:41.860 --> 00:11:41.870 align:start position:0% action that can be done in teams that 00:11:41.870 --> 00:11:44.020 align:start position:0% action that can be done in teams that might<00:11:42.020> be<00:11:42.170> signed<00:11:42.350> by<00:11:42.530> someone<00:11:42.740> else<00:11:42.980> so<00:11:43.910> this 00:11:44.020 --> 00:11:44.030 align:start position:0% might be signed by someone else so this 00:11:44.030 --> 00:11:46.540 align:start position:0% might be signed by someone else so this will<00:11:44.270> be<00:11:44.390> basically<00:11:44.750> a<00:11:44.960> file<00:11:45.230> structure<00:11:45.740> top 00:11:46.540 --> 00:11:46.550 align:start position:0% will be basically a file structure top 00:11:46.550 --> 00:11:48.610 align:start position:0% will be basically a file structure top expert<00:11:46.930> so 00:11:48.610 --> 00:11:48.620 align:start position:0% expert so 00:11:48.620 --> 00:11:51.520 align:start position:0% expert so given<00:11:49.190> we<00:11:49.310> have<00:11:49.520> a<00:11:49.930> brief<00:11:50.930> understanding<00:11:51.050> of 00:11:51.520 --> 00:11:51.530 align:start position:0% given we have a brief understanding of 00:11:51.530 --> 00:11:54.450 align:start position:0% given we have a brief understanding of what<00:11:51.710> we<00:11:51.890> could<00:11:52.190> solve<00:11:52.640> the<00:11:52.820> problem 00:11:54.450 --> 00:11:54.460 align:start position:0% what we could solve the problem 00:11:54.460 --> 00:11:57.280 align:start position:0% what we could solve the problem I'd<00:11:55.460> like<00:11:55.640> to<00:11:55.760> move<00:11:55.850> forward<00:11:56.150> to<00:11:56.660> show<00:11:56.840> you<00:11:56.900> a 00:11:57.280 --> 00:11:57.290 align:start position:0% I'd like to move forward to show you a 00:11:57.290 --> 00:11:59.680 align:start position:0% I'd like to move forward to show you a little<00:11:57.500> word<00:11:57.740> open<00:11:58.160> house<00:11:59.090> workers<00:11:59.330> will<00:11:59.480> be 00:11:59.680 --> 00:11:59.690 align:start position:0% little word open house workers will be 00:11:59.690 --> 00:12:01.270 align:start position:0% little word open house workers will be applied<00:11:59.990> that's<00:12:00.470> going<00:12:00.740> to<00:12:00.800> be<00:12:00.920> more 00:12:01.270 --> 00:12:01.280 align:start position:0% applied that's going to be more 00:12:01.280 --> 00:12:04.920 align:start position:0% applied that's going to be more complicated<00:12:01.520> as<00:12:01.940> two<00:12:02.150> days<00:12:02.330> and<00:12:02.540> same<00:12:02.720> to<00:12:02.930> me 00:12:04.920 --> 00:12:04.930 align:start position:0% complicated as two days and same to me 00:12:04.930 --> 00:12:07.570 align:start position:0% complicated as two days and same to me imagine<00:12:05.930> with<00:12:06.110> me<00:12:06.140> that<00:12:06.620> you 00:12:07.570 --> 00:12:07.580 align:start position:0% imagine with me that you 00:12:07.580 --> 00:12:10.650 align:start position:0% imagine with me that you a<00:12:07.610> token<00:12:08.150> that<00:12:08.600> represents<00:12:09.140> Ankara<00:12:09.440> will<00:12:09.680> show 00:12:10.650 --> 00:12:10.660 align:start position:0% a token that represents Ankara will show 00:12:10.660 --> 00:12:14.380 align:start position:0% a token that represents Ankara will show you<00:12:11.660> get<00:12:12.290> the<00:12:12.410> token<00:12:12.560> to<00:12:12.740> my<00:12:12.950> car<00:12:13.220> I'd<00:12:13.910> imagine 00:12:14.380 --> 00:12:14.390 align:start position:0% you get the token to my car I'd imagine 00:12:14.390 --> 00:12:16.180 align:start position:0% you get the token to my car I'd imagine that<00:12:14.510> you<00:12:14.900> have<00:12:15.080> insured<00:12:15.440> part<00:12:15.770> which<00:12:16.160> is 00:12:16.180 --> 00:12:16.190 align:start position:0% that you have insured part which is 00:12:16.190 --> 00:12:19.330 align:start position:0% that you have insured part which is another<00:12:16.490> fulfillment<00:12:17.120> you<00:12:17.960> get<00:12:18.170> when<00:12:19.100> you<00:12:19.160> pay 00:12:19.330 --> 00:12:19.340 align:start position:0% another fulfillment you get when you pay 00:12:19.340 --> 00:12:21.520 align:start position:0% another fulfillment you get when you pay the<00:12:19.490> insurance<00:12:19.900> together<00:12:20.900> the<00:12:21.050> department 00:12:21.520 --> 00:12:21.530 align:start position:0% the insurance together the department 00:12:21.530 --> 00:12:24.130 align:start position:0% the insurance together the department and<00:12:22.400> here<00:12:22.670> on<00:12:23.000> this<00:12:23.150> interface<00:12:23.420> there<00:12:24.020> are 00:12:24.130 --> 00:12:24.140 align:start position:0% and here on this interface there are 00:12:24.140 --> 00:12:28.810 align:start position:0% and here on this interface there are multiple<00:12:24.560> tokens<00:12:26.140> of<00:12:27.400> highlighted<00:12:28.400> ones<00:12:28.610> the 00:12:28.810 --> 00:12:28.820 align:start position:0% multiple tokens of highlighted ones the 00:12:28.820 --> 00:12:31.360 align:start position:0% multiple tokens of highlighted ones the trust<00:12:29.290> fund<00:12:30.290> is<00:12:30.380> messed<00:12:30.620> up<00:12:30.770> but<00:12:31.010> it<00:12:31.160> really 00:12:31.360 --> 00:12:31.370 align:start position:0% trust fund is messed up but it really 00:12:31.370 --> 00:12:34.000 align:start position:0% trust fund is messed up but it really sure<00:12:31.760> about<00:12:31.880> equity<00:12:32.360> and<00:12:32.510> religion<00:12:33.200> they 00:12:34.000 --> 00:12:34.010 align:start position:0% sure about equity and religion they 00:12:34.010 --> 00:12:35.350 align:start position:0% sure about equity and religion they don't<00:12:34.190> make<00:12:34.340> them<00:12:34.520> perfect<00:12:34.910> this<00:12:35.120> is<00:12:35.240> the 00:12:35.350 --> 00:12:35.360 align:start position:0% don't make them perfect this is the 00:12:35.360 --> 00:12:38.200 align:start position:0% don't make them perfect this is the character<00:12:35.810> how<00:12:36.560> did<00:12:36.710> it<00:12:36.980> end<00:12:37.160> up<00:12:37.400> later 00:12:38.200 --> 00:12:38.210 align:start position:0% character how did it end up later 00:12:38.210 --> 00:12:41.980 align:start position:0% character how did it end up later well<00:12:38.750> let's<00:12:39.470> imagine<00:12:40.000> with<00:12:41.000> this<00:12:41.180> new 00:12:41.980 --> 00:12:41.990 align:start position:0% well let's imagine with this new 00:12:41.990 --> 00:12:46.020 align:start position:0% well let's imagine with this new insurance<00:12:42.590> token<00:12:43.660> what<00:12:44.660> you<00:12:44.750> can<00:12:44.930> do<00:12:45.080> with<00:12:45.230> it 00:12:46.020 --> 00:12:46.030 align:start position:0% insurance token what you can do with it 00:12:46.030 --> 00:12:48.310 align:start position:0% insurance token what you can do with it imagine<00:12:47.030> a<00:12:47.090> business<00:12:47.270> or<00:12:47.600> car<00:12:47.870> next<00:12:48.050> door 00:12:48.310 --> 00:12:48.320 align:start position:0% imagine a business or car next door 00:12:48.320 --> 00:12:51.130 align:start position:0% imagine a business or car next door actually<00:12:48.980> there's<00:12:49.220> actually<00:12:49.340> a<00:12:49.790> similarly<00:12:50.300> if 00:12:51.130 --> 00:12:51.140 align:start position:0% actually there's actually a similarly if 00:12:51.140 --> 00:12:54.730 align:start position:0% actually there's actually a similarly if that<00:12:51.350> allows<00:12:51.650> you<00:12:51.920> to<00:12:52.060> enter<00:12:53.060> car<00:12:53.480> be<00:12:54.200> rented 00:12:54.730 --> 00:12:54.740 align:start position:0% that allows you to enter car be rented 00:12:54.740 --> 00:13:00.130 align:start position:0% that allows you to enter car be rented by<00:12:56.440> strangers<00:12:57.440> and<00:12:57.850> you<00:12:58.850> just<00:12:59.120> get<00:12:59.330> a<00:12:59.390> dollar<00:13:00.080> a 00:13:00.130 --> 00:13:00.140 align:start position:0% by strangers and you just get a dollar a 00:13:00.140 --> 00:13:01.660 align:start position:0% by strangers and you just get a dollar a day<00:13:00.350> when<00:13:00.710> you<00:13:00.860> come<00:13:01.010> into<00:13:01.160> your<00:13:01.370> pocket 00:13:01.660 --> 00:13:01.670 align:start position:0% day when you come into your pocket 00:13:01.670 --> 00:13:04.390 align:start position:0% day when you come into your pocket automatically<00:13:02.180> when<00:13:02.990> a<00:13:03.050> car<00:13:03.260> is<00:13:03.400> modified 00:13:04.390 --> 00:13:04.400 align:start position:0% automatically when a car is modified 00:13:04.400 --> 00:13:06.400 align:start position:0% automatically when a car is modified sell<00:13:04.610> for<00:13:05.120> you<00:13:05.210> that's<00:13:05.450> that's<00:13:05.660> that<00:13:05.690> idea<00:13:05.930> and 00:13:06.400 --> 00:13:06.410 align:start position:0% sell for you that's that's that idea and 00:13:06.410 --> 00:13:09.250 align:start position:0% sell for you that's that's that idea and in<00:13:07.220> order<00:13:07.820> to<00:13:07.880> do<00:13:08.060> this<00:13:08.240> service<00:13:08.660> you<00:13:09.050> need<00:13:09.170> to 00:13:09.250 --> 00:13:09.260 align:start position:0% in order to do this service you need to 00:13:09.260 --> 00:13:11.590 align:start position:0% in order to do this service you need to have<00:13:09.350> is<00:13:09.470> we<00:13:09.560> need<00:13:09.680> a<00:13:09.710> shortcut<00:13:10.120> so<00:13:11.120> the 00:13:11.590 --> 00:13:11.600 align:start position:0% have is we need a shortcut so the 00:13:11.600 --> 00:13:13.840 align:start position:0% have is we need a shortcut so the insurance<00:13:11.900> token<00:13:12.560> would<00:13:12.770> be<00:13:12.920> the<00:13:13.040> enabler<00:13:13.580> of 00:13:13.840 --> 00:13:13.850 align:start position:0% insurance token would be the enabler of 00:13:13.850 --> 00:13:18.760 align:start position:0% insurance token would be the enabler of this<00:13:14.540> new<00:13:15.230> shake<00:13:16.040> country<00:13:16.430> style<00:13:16.880> and<00:13:17.770> when 00:13:18.760 --> 00:13:18.770 align:start position:0% this new shake country style and when 00:13:18.770 --> 00:13:22.060 align:start position:0% this new shake country style and when you<00:13:18.860> use<00:13:19.070> the<00:13:19.370> insurance<00:13:19.670> token<00:13:20.410> for<00:13:21.410> this<00:13:21.560> new 00:13:22.060 --> 00:13:22.070 align:start position:0% you use the insurance token for this new 00:13:22.070 --> 00:13:25.210 align:start position:0% you use the insurance token for this new chain<00:13:22.730> economy<00:13:23.180> we<00:13:23.600> had<00:13:23.810> a<00:13:23.990> rental<00:13:24.590> car<00:13:24.920> list 00:13:25.210 --> 00:13:25.220 align:start position:0% chain economy we had a rental car list 00:13:25.220 --> 00:13:27.670 align:start position:0% chain economy we had a rental car list important<00:13:25.850> which<00:13:26.660> which<00:13:27.050> is<00:13:27.290> the<00:13:27.410> source<00:13:27.590> of 00:13:27.670 --> 00:13:27.680 align:start position:0% important which which is the source of 00:13:27.680 --> 00:13:29.080 align:start position:0% important which which is the source of revenue<00:13:28.040> that<00:13:28.160> comes<00:13:28.280> to<00:13:28.490> you<00:13:28.580> from<00:13:28.640> time<00:13:28.940> to 00:13:29.080 --> 00:13:29.090 align:start position:0% revenue that comes to you from time to 00:13:29.090 --> 00:13:31.010 align:start position:0% revenue that comes to you from time to time<00:13:29.120> I<00:13:29.570> represent<00:13:30.440> is<00:13:30.530> that 00:13:31.010 --> 00:13:31.020 align:start position:0% time I represent is that 00:13:31.020 --> 00:13:33.470 align:start position:0% time I represent is that you<00:13:31.140> have<00:13:31.350> salsify<00:13:32.430> if<00:13:32.580> you<00:13:32.670> want<00:13:32.820> to<00:13:32.910> live<00:13:33.060> to 00:13:33.470 --> 00:13:33.480 align:start position:0% you have salsify if you want to live to 00:13:33.480 --> 00:13:35.150 align:start position:0% you have salsify if you want to live to a<00:13:33.510> secure<00:13:33.750> Anatomy<00:13:34.140> it's<00:13:34.320> not<00:13:34.500> a<00:13:34.529> story 00:13:35.150 --> 00:13:35.160 align:start position:0% a secure Anatomy it's not a story 00:13:35.160 --> 00:13:37.190 align:start position:0% a secure Anatomy it's not a story we'll<00:13:35.790> just<00:13:35.910> imagine<00:13:36.029> that<00:13:36.480> this<00:13:36.630> is<00:13:36.690> possible 00:13:37.190 --> 00:13:37.200 align:start position:0% we'll just imagine that this is possible 00:13:37.200 --> 00:13:39.860 align:start position:0% we'll just imagine that this is possible to<00:13:37.830> have<00:13:37.980> a<00:13:38.010> static<00:13:38.399> for<00:13:39.029> car<00:13:39.240> got<00:13:39.390> stolen<00:13:39.570> with 00:13:39.860 --> 00:13:39.870 align:start position:0% to have a static for car got stolen with 00:13:39.870 --> 00:13:42.230 align:start position:0% to have a static for car got stolen with other<00:13:40.020> students<00:13:40.440> so<00:13:41.370> the<00:13:41.580> process<00:13:41.910> will<00:13:42.060> look 00:13:42.230 --> 00:13:42.240 align:start position:0% other students so the process will look 00:13:42.240 --> 00:13:44.180 align:start position:0% other students so the process will look at<00:13:42.420> this<00:13:42.600> first<00:13:43.020> this<00:13:43.290> is<00:13:43.350> serious<00:13:43.709> business 00:13:44.180 --> 00:13:44.190 align:start position:0% at this first this is serious business 00:13:44.190 --> 00:13:46.010 align:start position:0% at this first this is serious business what<00:13:44.339> time<00:13:44.490> you<00:13:44.640> say<00:13:44.790> do<00:13:45.510> actually<00:13:45.870> only 00:13:46.010 --> 00:13:46.020 align:start position:0% what time you say do actually only 00:13:46.020 --> 00:13:48.380 align:start position:0% what time you say do actually only insurance<00:13:46.380> now<00:13:47.339> the<00:13:47.399> work<00:13:47.760> that<00:13:47.970> was<00:13:48.089> to<00:13:48.240> learn 00:13:48.380 --> 00:13:48.390 align:start position:0% insurance now the work that was to learn 00:13:48.390 --> 00:13:51.590 align:start position:0% insurance now the work that was to learn something<00:13:48.630> and<00:13:49.020> the<00:13:49.709> Conclave<00:13:50.459> has<00:13:50.580> to<00:13:50.940> paly 00:13:51.590 --> 00:13:51.600 align:start position:0% something and the Conclave has to paly 00:13:51.600 --> 00:13:53.000 align:start position:0% something and the Conclave has to paly say<00:13:51.839> that<00:13:52.020> okay<00:13:52.350> actually<00:13:52.529> I<00:13:52.740> can<00:13:52.890> do<00:13:52.980> a 00:13:53.000 --> 00:13:53.010 align:start position:0% say that okay actually I can do a 00:13:53.010 --> 00:13:55.389 align:start position:0% say that okay actually I can do a witness<00:13:53.339> Commission<00:13:53.730> this<00:13:54.600> is<00:13:54.720> my<00:13:54.839> policy 00:13:55.389 --> 00:13:55.399 align:start position:0% witness Commission this is my policy 00:13:55.399 --> 00:13:58.040 align:start position:0% witness Commission this is my policy destination<00:13:56.399> and<00:13:56.970> then<00:13:57.060> once<00:13:57.180> that<00:13:57.330> goes<00:13:57.510> to 00:13:58.040 --> 00:13:58.050 align:start position:0% destination and then once that goes to 00:13:58.050 --> 00:14:00.500 align:start position:0% destination and then once that goes to the<00:13:58.140> back<00:13:58.320> of<00:13:58.860> the<00:13:59.040> website<00:13:59.339> and<00:13:59.670> ask<00:14:00.209> me<00:14:00.480> if 00:14:00.500 --> 00:14:00.510 align:start position:0% the back of the website and ask me if 00:14:00.510 --> 00:14:04.060 align:start position:0% the back of the website and ask me if you<00:14:00.720> know<00:14:00.959> if<00:14:01.500> this<00:14:01.709> policy<00:14:02.220> as<00:14:02.820> a<00:14:02.880> cover<00:14:03.180> or 00:14:04.060 --> 00:14:04.070 align:start position:0% you know if this policy as a cover or 00:14:04.070 --> 00:14:07.130 align:start position:0% you know if this policy as a cover or own<00:14:05.070> virus<00:14:05.490> which<00:14:05.670> is<00:14:05.730> condition<00:14:06.209> and<00:14:06.510> it's 00:14:07.130 --> 00:14:07.140 align:start position:0% own virus which is condition and it's 00:14:07.140 --> 00:14:09.530 align:start position:0% own virus which is condition and it's not<00:14:07.290> conscious<00:14:07.589> and<00:14:07.770> every<00:14:08.100> list<00:14:08.310> this<00:14:09.120> is<00:14:09.330> one 00:14:09.530 --> 00:14:09.540 align:start position:0% not conscious and every list this is one 00:14:09.540 --> 00:14:12.199 align:start position:0% not conscious and every list this is one of<00:14:09.570> the<00:14:09.810> infusion<00:14:10.140> where<00:14:10.500> the<00:14:11.010> user<00:14:11.220> behind 00:14:12.199 --> 00:14:12.209 align:start position:0% of the infusion where the user behind 00:14:12.209 --> 00:14:15.560 align:start position:0% of the infusion where the user behind security<00:14:12.660> Enclave<00:14:13.050> and<00:14:13.520> the<00:14:14.520> website<00:14:14.880> using 00:14:15.560 --> 00:14:15.570 align:start position:0% security Enclave and the website using 00:14:15.570 --> 00:14:17.510 align:start position:0% security Enclave and the website using there's<00:14:15.750> their<00:14:16.200> own<00:14:16.350> own<00:14:16.589> establish<00:14:17.279> trust 00:14:17.510 --> 00:14:17.520 align:start position:0% there's their own own establish trust 00:14:17.520 --> 00:14:20.389 align:start position:0% there's their own own establish trust between<00:14:17.700> each<00:14:17.880> other<00:14:18.060> so<00:14:18.980> you<00:14:19.980> know<00:14:20.190> we<00:14:20.310> don't 00:14:20.389 --> 00:14:20.399 align:start position:0% between each other so you know we don't 00:14:20.399 --> 00:14:22.280 align:start position:0% between each other so you know we don't previously<00:14:20.880> in<00:14:20.970> the<00:14:21.060> car<00:14:21.510> kitchen<00:14:21.810> garden<00:14:22.200> the 00:14:22.280 --> 00:14:22.290 align:start position:0% previously in the car kitchen garden the 00:14:22.290 --> 00:14:24.040 align:start position:0% previously in the car kitchen garden the website<00:14:22.589> that<00:14:22.709> we<00:14:22.800> may<00:14:22.980> need<00:14:23.100> to<00:14:23.190> access<00:14:23.370> the 00:14:24.040 --> 00:14:24.050 align:start position:0% website that we may need to access the 00:14:24.050 --> 00:14:27.230 align:start position:0% website that we may need to access the third<00:14:25.050> option<00:14:25.350> is<00:14:25.709> alive<00:14:26.100> about<00:14:26.310> having<00:14:26.820> that 00:14:27.230 --> 00:14:27.240 align:start position:0% third option is alive about having that 00:14:27.240 --> 00:14:29.120 align:start position:0% third option is alive about having that kitten<00:14:27.709> is 00:14:29.120 --> 00:14:29.130 align:start position:0% kitten is 00:14:29.130 --> 00:14:33.020 align:start position:0% kitten is and<00:14:30.470> to<00:14:31.470> this<00:14:31.560> point<00:14:31.650> behind<00:14:32.100> is<00:14:32.490> that<00:14:32.550> visual 00:14:33.020 --> 00:14:33.030 align:start position:0% and to this point behind is that visual 00:14:33.030 --> 00:14:35.210 align:start position:0% and to this point behind is that visual trust<00:14:33.270> and<00:14:33.960> the<00:14:34.020> website<00:14:34.350> was<00:14:34.530> an<00:14:34.710> information 00:14:35.210 --> 00:14:35.220 align:start position:0% trust and the website was an information 00:14:35.220 --> 00:14:37.790 align:start position:0% trust and the website was an information okay<00:14:35.520> send<00:14:36.180> send<00:14:36.600> a<00:14:36.690> transaction<00:14:37.080> to<00:14:37.290> get<00:14:37.620> your 00:14:37.790 --> 00:14:37.800 align:start position:0% okay send send a transaction to get your 00:14:37.800 --> 00:14:40.940 align:start position:0% okay send send a transaction to get your car<00:14:38.130> distant<00:14:38.520> and<00:14:39.300> here<00:14:39.660> kiss<00:14:40.140> telescope<00:14:40.680> this 00:14:40.940 --> 00:14:40.950 align:start position:0% car distant and here kiss telescope this 00:14:40.950 --> 00:14:44.150 align:start position:0% car distant and here kiss telescope this telescope<00:14:41.010> is<00:14:41.700> a<00:14:41.790> new<00:14:42.030> one<00:14:42.530> this<00:14:43.530> telescope<00:14:44.010> is 00:14:44.150 --> 00:14:44.160 align:start position:0% telescope is a new one this telescope is 00:14:44.160 --> 00:14:46.160 align:start position:0% telescope is a new one this telescope is issued<00:14:44.640> by<00:14:44.880> connects<00:14:45.300> polish<00:14:45.660> a<00:14:45.810> company 00:14:46.160 --> 00:14:46.170 align:start position:0% issued by connects polish a company 00:14:46.170 --> 00:14:48.500 align:start position:0% issued by connects polish a company company<00:14:46.350> and<00:14:47.340> it<00:14:47.460> contains<00:14:47.760> the<00:14:47.910> rules<00:14:48.090> how<00:14:48.480> to 00:14:48.500 --> 00:14:48.510 align:start position:0% company and it contains the rules how to 00:14:48.510 --> 00:14:50.900 align:start position:0% company and it contains the rules how to get<00:14:48.870> a<00:14:49.140> transaction<00:14:49.890> of<00:14:50.400> the<00:14:50.460> sample 00:14:50.900 --> 00:14:50.910 align:start position:0% get a transaction of the sample 00:14:50.910 --> 00:14:52.760 align:start position:0% get a transaction of the sample transaction<00:14:51.510> to<00:14:52.050> get<00:14:52.200> your<00:14:52.410> rental<00:14:52.740> car 00:14:52.760 --> 00:14:52.770 align:start position:0% transaction to get your rental car 00:14:52.770 --> 00:14:58.340 align:start position:0% transaction to get your rental car disdainfully<00:14:54.020> so<00:14:55.020> what<00:14:55.980> we<00:14:56.130> have<00:14:56.340> now<00:14:56.370> is<00:14:57.350> in 00:14:58.340 --> 00:14:58.350 align:start position:0% disdainfully so what we have now is in 00:14:58.350 --> 00:15:01.460 align:start position:0% disdainfully so what we have now is in the<00:14:58.470> security<00:14:58.830> unplayed<00:14:59.480> the<00:15:00.480> environment<00:15:01.320> in 00:15:01.460 --> 00:15:01.470 align:start position:0% the security unplayed the environment in 00:15:01.470 --> 00:15:04.370 align:start position:0% the security unplayed the environment in which<00:15:02.180> evolutionary<00:15:03.180> signatures<00:15:03.630> good<00:15:03.900> is 00:15:04.370 --> 00:15:04.380 align:start position:0% which evolutionary signatures good is 00:15:04.380 --> 00:15:07.030 align:start position:0% which evolutionary signatures good is usually<00:15:04.770> from<00:15:04.890> time<00:15:05.130> next<00:15:05.370> or<00:15:05.490> bottom<00:15:05.850> and 00:15:07.030 --> 00:15:07.040 align:start position:0% usually from time next or bottom and 00:15:07.040 --> 00:15:09.260 align:start position:0% usually from time next or bottom and many<00:15:08.040> we<00:15:08.220> acquired<00:15:08.610> didn't<00:15:08.940> know<00:15:09.060> that 00:15:09.260 --> 00:15:09.270 align:start position:0% many we acquired didn't know that 00:15:09.270 --> 00:15:11.480 align:start position:0% many we acquired didn't know that actually<00:15:09.660> is<00:15:10.020> the<00:15:10.080> total<00:15:10.440> missionary<00:15:10.890> from 00:15:11.480 --> 00:15:11.490 align:start position:0% actually is the total missionary from 00:15:11.490 --> 00:15:13.370 align:start position:0% actually is the total missionary from comfort<00:15:11.880> zone<00:15:12.030> that<00:15:12.060> were<00:15:12.300> in<00:15:12.450> toast<00:15:12.720> is 00:15:13.370 --> 00:15:13.380 align:start position:0% comfort zone that were in toast is 00:15:13.380 --> 00:15:15.800 align:start position:0% comfort zone that were in toast is talking<00:15:13.770> spiritual<00:15:14.130> and<00:15:14.490> the<00:15:15.000> sermon<00:15:15.630> that 00:15:15.800 --> 00:15:15.810 align:start position:0% talking spiritual and the sermon that 00:15:15.810 --> 00:15:17.450 align:start position:0% talking spiritual and the sermon that will<00:15:16.080> come<00:15:16.200> magazine<00:15:16.650> distance<00:15:17.250> will<00:15:17.430> be 00:15:17.450 --> 00:15:17.460 align:start position:0% will come magazine distance will be 00:15:17.460 --> 00:15:19.910 align:start position:0% will come magazine distance will be genuine<00:15:17.880> and<00:15:17.970> not<00:15:18.090> devote<00:15:18.420> as<00:15:19.140> awkward<00:15:19.350> and 00:15:19.910 --> 00:15:19.920 align:start position:0% genuine and not devote as awkward and 00:15:19.920 --> 00:15:23.510 align:start position:0% genuine and not devote as awkward and the<00:15:20.730> user<00:15:20.910> will<00:15:21.210> get<00:15:21.420> this<00:15:21.870> which<00:15:22.830> is<00:15:23.190> a 00:15:23.510 --> 00:15:23.520 align:start position:0% the user will get this which is a 00:15:23.520 --> 00:15:25.880 align:start position:0% the user will get this which is a transaction<00:15:24.270> losers<00:15:24.750> in<00:15:24.930> the<00:15:25.020> same<00:15:25.200> sense 00:15:25.880 --> 00:15:25.890 align:start position:0% transaction losers in the same sense 00:15:25.890 --> 00:15:27.770 align:start position:0% transaction losers in the same sense that<00:15:26.010> we're<00:15:26.550> talking<00:15:26.820> I'm<00:15:26.940> going<00:15:27.150> to<00:15:27.270> lose<00:15:27.450> by 00:15:27.770 --> 00:15:27.780 align:start position:0% that we're talking I'm going to lose by 00:15:27.780 --> 00:15:28.510 align:start position:0% that we're talking I'm going to lose by transaction 00:15:28.510 --> 00:15:28.520 align:start position:0% transaction 00:15:28.520 --> 00:15:30.320 align:start position:0% transaction we're<00:15:29.520> talking<00:15:29.790> about<00:15:29.850> would<00:15:30.030> use 00:15:30.320 --> 00:15:30.330 align:start position:0% we're talking about would use 00:15:30.330 --> 00:15:32.990 align:start position:0% we're talking about would use intersection<00:15:31.250> characteristics<00:15:32.250> dependency 00:15:32.990 --> 00:15:33.000 align:start position:0% intersection characteristics dependency 00:15:33.000 --> 00:15:36.710 align:start position:0% intersection characteristics dependency and<00:15:34.160> what<00:15:35.160> kind<00:15:35.640> of<00:15:35.940> again<00:15:36.210> which<00:15:36.570> is 00:15:36.710 --> 00:15:36.720 align:start position:0% and what kind of again which is 00:15:36.720 --> 00:15:39.890 align:start position:0% and what kind of again which is car<00:15:36.990> rental<00:15:37.320> when<00:15:38.190> a<00:15:38.310> car<00:15:38.460> is<00:15:38.490> Tito<00:15:38.850> and<00:15:39.240> it's 00:15:39.890 --> 00:15:39.900 align:start position:0% car rental when a car is Tito and it's 00:15:39.900 --> 00:15:41.840 align:start position:0% car rental when a car is Tito and it's green<00:15:40.050> great<00:15:40.320> color<00:15:40.530> because<00:15:40.950> doesn't<00:15:41.580> exist 00:15:41.840 --> 00:15:41.850 align:start position:0% green great color because doesn't exist 00:15:41.850 --> 00:15:44.120 align:start position:0% green great color because doesn't exist yet<00:15:42.090> it's<00:15:42.810> created<00:15:43.320> on<00:15:43.710> the<00:15:43.830> moment 00:15:44.120 --> 00:15:44.130 align:start position:0% yet it's created on the moment 00:15:44.130 --> 00:15:47.990 align:start position:0% yet it's created on the moment accessible<00:15:45.030> transaction<00:15:45.620> so<00:15:46.620> this<00:15:47.550> is<00:15:47.730> what 00:15:47.990 --> 00:15:48.000 align:start position:0% accessible transaction so this is what 00:15:48.000 --> 00:15:51.800 align:start position:0% accessible transaction so this is what generated<00:15:49.310> from<00:15:50.310> the<00:15:50.640> security<00:15:51.150> on<00:15:51.270> trade<00:15:51.510> and 00:15:51.800 --> 00:15:51.810 align:start position:0% generated from the security on trade and 00:15:51.810 --> 00:15:54.260 align:start position:0% generated from the security on trade and not<00:15:52.470> by<00:15:52.680> website<00:15:53.070> what<00:15:53.610> has<00:15:53.760> me<00:15:53.880> to<00:15:53.970> say<00:15:54.120> that 00:15:54.260 --> 00:15:54.270 align:start position:0% not by website what has me to say that 00:15:54.270 --> 00:15:56.240 align:start position:0% not by website what has me to say that leads<00:15:54.540> to<00:15:54.780> changes<00:15:55.110> a<00:15:55.230> transaction<00:15:55.620> and<00:15:56.010> what 00:15:56.240 --> 00:15:56.250 align:start position:0% leads to changes a transaction and what 00:15:56.250 --> 00:15:57.020 align:start position:0% leads to changes a transaction and what I'm<00:15:56.550> telling<00:15:56.790> you 00:15:57.020 --> 00:15:57.030 align:start position:0% I'm telling you 00:15:57.030 --> 00:15:59.900 align:start position:0% I'm telling you and<00:15:58.010> hello<00:15:59.010> word<00:15:59.220> here<00:15:59.430> we<00:15:59.580> had<00:15:59.730> beautiful 00:15:59.900 --> 00:15:59.910 align:start position:0% and hello word here we had beautiful 00:15:59.910 --> 00:16:02.570 align:start position:0% and hello word here we had beautiful team<00:16:00.270> here<00:16:00.420> in<00:16:01.050> the<00:16:01.140> security<00:16:01.620> vampire<00:16:02.220> we 00:16:02.570 --> 00:16:02.580 align:start position:0% team here in the security vampire we 00:16:02.580 --> 00:16:06.240 align:start position:0% team here in the security vampire we have<00:16:02.730> insurance 00:16:06.240 --> 00:16:06.250 align:start position:0% 00:16:06.250 --> 00:16:13.200 align:start position:0% I<00:16:06.810> totally<00:16:08.190> this<00:16:09.190> is<00:16:09.250> Hollywood<00:16:10.529> so<00:16:11.880> yeah<00:16:12.880> what 00:16:13.200 --> 00:16:13.210 align:start position:0% I totally this is Hollywood so yeah what 00:16:13.210 --> 00:16:14.940 align:start position:0% I totally this is Hollywood so yeah what do<00:16:13.270> you<00:16:13.330> say<00:16:13.480> security<00:16:13.810> on<00:16:13.990> a<00:16:14.080> place<00:16:14.290> that's<00:16:14.500> on 00:16:14.940 --> 00:16:14.950 align:start position:0% do you say security on a place that's on 00:16:14.950 --> 00:16:16.680 align:start position:0% do you say security on a place that's on a<00:16:15.010> physical<00:16:15.460> device<00:16:15.520> without<00:16:15.880> software<00:16:16.270> I 00:16:16.680 --> 00:16:16.690 align:start position:0% a physical device without software I 00:16:16.690 --> 00:16:18.329 align:start position:0% a physical device without software I should<00:16:17.050> use<00:16:17.140> itself<00:16:17.320> that<00:16:17.529> concept<00:16:17.830> okay<00:16:18.279> so 00:16:18.329 --> 00:16:18.339 align:start position:0% should use itself that concept okay so 00:16:18.339 --> 00:16:20.579 align:start position:0% should use itself that concept okay so where<00:16:18.640> is<00:16:18.790> that<00:16:18.910> software<00:16:19.300> running<00:16:19.510> is<00:16:20.290> in<00:16:20.470> the 00:16:20.579 --> 00:16:20.589 align:start position:0% where is that software running is in the 00:16:20.589 --> 00:16:23.340 align:start position:0% where is that software running is in the users<00:16:20.830> browser<00:16:21.600> so<00:16:22.600> they<00:16:22.720> are<00:16:22.839> never<00:16:23.050> this 00:16:23.340 --> 00:16:23.350 align:start position:0% users browser so they are never this 00:16:23.350 --> 00:16:25.949 align:start position:0% users browser so they are never this much<00:16:23.500> relevant<00:16:24.040> because<00:16:24.250> we<00:16:24.700> will<00:16:25.480> have<00:16:25.510> a<00:16:25.720> 1 00:16:25.949 --> 00:16:25.959 align:start position:0% much relevant because we will have a 1 00:16:25.959 --> 00:16:27.720 align:start position:0% much relevant because we will have a 1 in<00:16:26.080> it<00:16:26.110> even<00:16:26.290> when<00:16:26.589> it<00:16:26.709> isn't<00:16:27.100> money<00:16:27.459> power 00:16:27.720 --> 00:16:27.730 align:start position:0% in it even when it isn't money power 00:16:27.730 --> 00:16:30.060 align:start position:0% in it even when it isn't money power will<00:16:27.970> it<00:16:28.089> to<00:16:28.510> have<00:16:28.720> this<00:16:28.870> thing<00:16:29.110> but<00:16:29.740> normally 00:16:30.060 --> 00:16:30.070 align:start position:0% will it to have this thing but normally 00:16:30.070 --> 00:16:34.610 align:start position:0% will it to have this thing but normally you<00:16:30.190> mean<00:16:30.490> a<00:16:30.730> new<00:16:31.120> kind<00:16:31.720> of<00:16:31.810> processor<00:16:33.180> maybe 00:16:34.610 --> 00:16:34.620 align:start position:0% you mean a new kind of processor maybe 00:16:34.620 --> 00:16:39.210 align:start position:0% you mean a new kind of processor maybe yeah<00:16:35.649> so<00:16:35.980> this<00:16:36.130> is<00:16:36.250> the<00:16:36.339> focus<00:16:37.709> so<00:16:38.709> arts<00:16:39.040> you 00:16:39.210 --> 00:16:39.220 align:start position:0% yeah so this is the focus so arts you 00:16:39.220 --> 00:16:40.769 align:start position:0% yeah so this is the focus so arts you create<00:16:39.550> a<00:16:39.580> browser<00:16:39.910> that<00:16:40.120> competes<00:16:40.690> with 00:16:40.769 --> 00:16:40.779 align:start position:0% create a browser that competes with 00:16:40.779 --> 00:16:42.269 align:start position:0% create a browser that competes with brain<00:16:41.140> it's<00:16:41.380> a<00:16:41.470> new<00:16:41.589> browser<00:16:41.770> it's<00:16:42.100> got<00:16:42.250> a 00:16:42.269 --> 00:16:42.279 align:start position:0% brain it's a new browser it's got a 00:16:42.279 --> 00:16:44.340 align:start position:0% brain it's a new browser it's got a security<00:16:42.700> Enclave<00:16:43.089> running<00:16:43.390> in<00:16:43.480> software<00:16:43.930> how 00:16:44.340 --> 00:16:44.350 align:start position:0% security Enclave running in software how 00:16:44.350 --> 00:16:48.000 align:start position:0% security Enclave running in software how do<00:16:44.410> you<00:16:44.560> trust<00:16:44.830> the<00:16:45.010> hardware<00:16:46.140> so<00:16:47.140> this<00:16:47.860> is<00:16:47.980> a 00:16:48.000 --> 00:16:48.010 align:start position:0% do you trust the hardware so this is a 00:16:48.010 --> 00:16:49.740 align:start position:0% do you trust the hardware so this is a different<00:16:48.310> level<00:16:48.399> I<00:16:48.700> think<00:16:48.760> we<00:16:49.240> may<00:16:49.330> be<00:16:49.360> great 00:16:49.740 --> 00:16:49.750 align:start position:0% different level I think we may be great 00:16:49.750 --> 00:16:51.000 align:start position:0% different level I think we may be great to<00:16:49.899> the<00:16:49.930> security<00:16:50.410> on<00:16:50.500> the<00:16:50.589> play<00:16:50.709> actually 00:16:51.000 --> 00:16:51.010 align:start position:0% to the security on the play actually 00:16:51.010 --> 00:16:52.530 align:start position:0% to the security on the play actually events<00:16:51.399> in<00:16:51.490> the<00:16:51.580> rules<00:16:51.760> that<00:16:51.880> he<00:16:52.000> was<00:16:52.120> model<00:16:52.450> is 00:16:52.530 --> 00:16:52.540 align:start position:0% events in the rules that he was model is 00:16:52.540 --> 00:16:55.320 align:start position:0% events in the rules that he was model is that<00:16:52.570> we<00:16:52.750> validate<00:16:53.260> but<00:16:53.950> I<00:16:54.250> think<00:16:55.000> this<00:16:55.180> is 00:16:55.320 --> 00:16:55.330 align:start position:0% that we validate but I think this is 00:16:55.330 --> 00:16:57.210 align:start position:0% that we validate but I think this is them<00:16:55.510> something<00:16:55.899> we<00:16:56.050> can<00:16:56.230> progress<00:16:56.410> to<00:16:56.589> our 00:16:57.210 --> 00:16:57.220 align:start position:0% them something we can progress to our 00:16:57.220 --> 00:17:01.110 align:start position:0% them something we can progress to our good<00:16:57.310> friend<00:16:58.500> so<00:16:59.500> actually<00:17:00.250> this<00:17:00.580> is<00:17:00.730> hot<00:17:00.880> oven 00:17:01.110 --> 00:17:01.120 align:start position:0% good friend so actually this is hot oven 00:17:01.120 --> 00:17:03.269 align:start position:0% good friend so actually this is hot oven script<00:17:01.390> boost<00:17:01.720> all<00:17:01.959> security<00:17:02.860> on<00:17:02.950> their<00:17:03.070> own 00:17:03.269 --> 00:17:03.279 align:start position:0% script boost all security on their own 00:17:03.279 --> 00:17:07.350 align:start position:0% script boost all security on their own web<00:17:03.580> decentralized<00:17:04.150> web<00:17:04.360> 3<00:17:04.569> so<00:17:05.850> we<00:17:06.850> have<00:17:07.000> more 00:17:07.350 --> 00:17:07.360 align:start position:0% web decentralized web 3 so we have more 00:17:07.360 --> 00:17:12.000 align:start position:0% web decentralized web 3 so we have more time<00:17:07.420> for<00:17:07.569> question<00:17:10.260> and<00:17:11.260> we<00:17:11.530> got<00:17:11.679> a<00:17:11.709> bunch<00:17:11.920> of 00:17:12.000 --> 00:17:12.010 align:start position:0% time for question and we got a bunch of 00:17:12.010 --> 00:17:16.150 align:start position:0% time for question and we got a bunch of questions 00:17:16.150 --> 00:17:16.160 align:start position:0% 00:17:16.160 --> 00:17:21.860 align:start position:0% the<00:17:17.160> other<00:17:18.090> question<00:17:19.370> has<00:17:20.370> not<00:17:20.520> occurred<00:17:20.880> and 00:17:21.860 --> 00:17:21.870 align:start position:0% the other question has not occurred and 00:17:21.870 --> 00:17:29.990 align:start position:0% the other question has not occurred and the<00:17:22.080> usual<00:17:22.320> has<00:17:22.500> user<00:17:22.680> no<00:17:22.890> right<00:17:24.770> as<00:17:29.000> so 00:17:29.990 --> 00:17:30.000 align:start position:0% the usual has user no right as so 00:17:30.000 --> 00:17:31.700 align:start position:0% the usual has user no right as so they're<00:17:30.630> kind<00:17:30.870> of<00:17:30.960> talk<00:17:31.050> of<00:17:31.170> you<00:17:31.320> assumptions 00:17:31.700 --> 00:17:31.710 align:start position:0% they're kind of talk of you assumptions 00:17:31.710 --> 00:17:34.700 align:start position:0% they're kind of talk of you assumptions being<00:17:31.890> five<00:17:32.160> years<00:17:32.490> so<00:17:32.910> for<00:17:33.420> example<00:17:33.780> most 00:17:34.700 --> 00:17:34.710 align:start position:0% being five years so for example most 00:17:34.710 --> 00:17:37.430 align:start position:0% being five years so for example most contributors<00:17:35.310> computer<00:17:36.000> movie<00:17:36.180> a<00:17:36.330> was<00:17:36.570> based 00:17:37.430 --> 00:17:37.440 align:start position:0% contributors computer movie a was based 00:17:37.440 --> 00:17:38.810 align:start position:0% contributors computer movie a was based on<00:17:37.590> idea<00:17:37.920> that<00:17:38.160> we<00:17:38.310> don't<00:17:38.340> have<00:17:38.640> physical 00:17:38.810 --> 00:17:38.820 align:start position:0% on idea that we don't have physical 00:17:38.820 --> 00:17:41.330 align:start position:0% on idea that we don't have physical advice<00:17:39.480> and<00:17:39.990> I<00:17:40.140> should<00:17:40.320> personally<00:17:40.590> store<00:17:40.980> it 00:17:41.330 --> 00:17:41.340 align:start position:0% advice and I should personally store it 00:17:41.340 --> 00:17:42.950 align:start position:0% advice and I should personally store it what<00:17:41.580> if<00:17:41.670> you<00:17:41.730> have<00:17:41.910> version<00:17:42.450> windows<00:17:42.630> that 00:17:42.950 --> 00:17:42.960 align:start position:0% what if you have version windows that 00:17:42.960 --> 00:17:46.310 align:start position:0% what if you have version windows that show<00:17:43.170> you<00:17:43.820> everything<00:17:44.820> so<00:17:45.660> the<00:17:45.780> assumption<00:17:46.170> is 00:17:46.310 --> 00:17:46.320 align:start position:0% show you everything so the assumption is 00:17:46.320 --> 00:17:48.560 align:start position:0% show you everything so the assumption is the<00:17:46.830> user<00:17:47.040> have<00:17:47.370> capacity<00:17:47.880> to<00:17:47.910> security 00:17:48.560 --> 00:17:48.570 align:start position:0% the user have capacity to security 00:17:48.570 --> 00:17:51.470 align:start position:0% the user have capacity to security advice<00:17:48.840> but<00:17:49.590> even<00:17:50.280> with<00:17:50.430> the<00:17:50.580> suction<00:17:50.790> that 00:17:51.470 --> 00:17:51.480 align:start position:0% advice but even with the suction that 00:17:51.480 --> 00:17:53.720 align:start position:0% advice but even with the suction that like<00:17:52.050> this<00:17:52.200> and<00:17:52.410> relaxed<00:17:52.680> assumption<00:17:53.160> own 00:17:53.720 --> 00:17:53.730 align:start position:0% like this and relaxed assumption own 00:17:53.730 --> 00:17:56.210 align:start position:0% like this and relaxed assumption own security<00:17:54.270> models<00:17:54.660> do<00:17:54.810> not<00:17:54.960> help<00:17:55.380> so<00:17:55.950> we<00:17:56.070> need 00:17:56.210 --> 00:17:56.220 align:start position:0% security models do not help so we need 00:17:56.220 --> 00:17:59.540 align:start position:0% security models do not help so we need new<00:17:56.430> security<00:17:56.910> token<00:17:57.810> script<00:17:58.110> I<00:17:58.530> still<00:17:59.400> with 00:17:59.540 --> 00:17:59.550 align:start position:0% new security token script I still with 00:17:59.550 --> 00:18:06.320 align:start position:0% new security token script I still with the<00:17:59.610> same<00:18:00.800> license<00:18:01.800> agreement<00:18:04.400> yes 00:18:06.320 --> 00:18:06.330 align:start position:0% the same license agreement yes 00:18:06.330 --> 00:18:09.170 align:start position:0% the same license agreement yes token<00:18:06.690> script<00:18:06.960> open<00:18:07.080> source<00:18:07.440> ok<00:18:08.160> this<00:18:08.340> is<00:18:08.490> some 00:18:09.170 --> 00:18:09.180 align:start position:0% token script open source ok this is some 00:18:09.180 --> 00:18:10.970 align:start position:0% token script open source ok this is some token<00:18:09.540> scooped<00:18:09.720> up<00:18:09.840> always<00:18:10.050> hungry<00:18:10.530> it's 00:18:10.970 --> 00:18:10.980 align:start position:0% token scooped up always hungry it's 00:18:10.980 --> 00:18:13.310 align:start position:0% token scooped up always hungry it's Paschal<00:18:11.550> icing<00:18:11.850> and<00:18:12.060> there's<00:18:12.750> a<00:18:12.960> tech 00:18:13.310 --> 00:18:13.320 align:start position:0% Paschal icing and there's a tech 00:18:13.320 --> 00:18:16.550 align:start position:0% Paschal icing and there's a tech knowledge<00:18:13.680> that<00:18:13.920> is<00:18:14.010> being<00:18:14.040> standardized<00:18:15.560> by 00:18:16.550 --> 00:18:16.560 align:start position:0% knowledge that is being standardized by 00:18:16.560 --> 00:18:18.320 align:start position:0% knowledge that is being standardized by if<00:18:17.280> M<00:18:17.430> information<00:18:17.910> and<00:18:18.090> we're<00:18:18.210> in<00:18:18.270> the 00:18:18.320 --> 00:18:18.330 align:start position:0% if M information and we're in the 00:18:18.330 --> 00:18:21.200 align:start position:0% if M information and we're in the process<00:18:18.530> sometimes<00:18:19.530> is<00:18:19.950> are<00:18:20.340> submitting<00:18:21.090> each 00:18:21.200 --> 00:18:21.210 align:start position:0% process sometimes is are submitting each 00:18:21.210 --> 00:18:23.900 align:start position:0% process sometimes is are submitting each other<00:18:21.390> to<00:18:21.600> since<00:18:21.900> then<00:18:22.050> there<00:18:22.170> is<00:18:22.830> this<00:18:22.980> oasis 00:18:23.900 --> 00:18:23.910 align:start position:0% other to since then there is this oasis 00:18:23.910 --> 00:18:25.040 align:start position:0% other to since then there is this oasis in<00:18:24.030> our<00:18:24.120> nation<00:18:24.570> we<00:18:24.690> should<00:18:24.720> producers 00:18:25.040 --> 00:18:25.050 align:start position:0% in our nation we should producers 00:18:25.050 --> 00:18:26.990 align:start position:0% in our nation we should producers produced<00:18:25.530> open<00:18:25.980> document<00:18:26.340> format<00:18:26.370> in<00:18:26.910> order 00:18:26.990 --> 00:18:27.000 align:start position:0% produced open document format in order 00:18:27.000 --> 00:18:30.260 align:start position:0% produced open document format in order of<00:18:27.600> office<00:18:28.050> so<00:18:28.650> tell<00:18:29.310> me<00:18:29.670> something<00:18:30.090> anything 00:18:30.260 --> 00:18:30.270 align:start position:0% of office so tell me something anything 00:18:30.270 --> 00:18:34.460 align:start position:0% of office so tell me something anything I<00:18:30.690> hope<00:18:30.930> I<00:18:31.050> get<00:18:31.170> guests<00:18:31.470> and<00:18:31.680> vice<00:18:31.890> versa<00:18:33.470> the 00:18:34.460 --> 00:18:34.470 align:start position:0% I hope I get guests and vice versa the 00:18:34.470 --> 00:18:35.660 align:start position:0% I hope I get guests and vice versa the second<00:18:34.830> question<00:18:35.010> what's<00:18:35.340> the<00:18:35.400> current 00:18:35.660 --> 00:18:35.670 align:start position:0% second question what's the current 00:18:35.670 --> 00:18:38.750 align:start position:0% second question what's the current status<00:18:35.970> or<00:18:36.360> like<00:18:37.070> can<00:18:38.070> we<00:18:38.100> already<00:18:38.520> start 00:18:38.750 --> 00:18:38.760 align:start position:0% status or like can we already start 00:18:38.760 --> 00:18:39.490 align:start position:0% status or like can we already start using<00:18:38.940> it 00:18:39.490 --> 00:18:39.500 align:start position:0% using it 00:18:39.500 --> 00:18:41.710 align:start position:0% using it yes<00:18:40.130> a<00:18:40.250> director<00:18:40.580> Cory<00:18:40.789> was<00:18:40.940> also<00:18:41.210> discouraged 00:18:41.710 --> 00:18:41.720 align:start position:0% yes a director Cory was also discouraged 00:18:41.720 --> 00:18:43.779 align:start position:0% yes a director Cory was also discouraged odd<00:18:42.080> however<00:18:42.350> so<00:18:43.100> though<00:18:43.220> the<00:18:43.340> script<00:18:43.549> works 00:18:43.779 --> 00:18:43.789 align:start position:0% odd however so though the script works 00:18:43.789 --> 00:18:46.990 align:start position:0% odd however so though the script works in<00:18:43.970> with<00:18:44.450> a<00:18:44.480> concept<00:18:44.870> for<00:18:44.990> a<00:18:45.200> context<00:18:45.830> so<00:18:46.490> let's 00:18:46.990 --> 00:18:47.000 align:start position:0% in with a concept for a context so let's 00:18:47.000 --> 00:18:48.490 align:start position:0% in with a concept for a context so let's say<00:18:47.120> the<00:18:47.270> token<00:18:47.570> mean<00:18:47.690> look<00:18:47.990> differently 00:18:48.490 --> 00:18:48.500 align:start position:0% say the token mean look differently 00:18:48.500 --> 00:18:50.649 align:start position:0% say the token mean look differently it<00:18:48.650> is<00:18:48.770> no.18<00:18:49.190> what<00:18:49.490> if<00:18:49.580> it's<00:18:49.730> a<00:18:49.789> better<00:18:50.090> or 00:18:50.649 --> 00:18:50.659 align:start position:0% it is no.18 what if it's a better or 00:18:50.659 --> 00:18:52.840 align:start position:0% it is no.18 what if it's a better or token<00:18:51.500> that's<00:18:51.950> the<00:18:52.130> current<00:18:52.460> okay 00:18:52.840 --> 00:18:52.850 align:start position:0% token that's the current okay 00:18:52.850 --> 00:18:55.180 align:start position:0% token that's the current okay you<00:18:53.000> look<00:18:53.539> differently<00:18:53.960> if<00:18:54.470> you<00:18:54.650> are<00:18:54.830> the<00:18:55.010> poor 00:18:55.180 --> 00:18:55.190 align:start position:0% you look differently if you are the poor 00:18:55.190 --> 00:18:58.299 align:start position:0% you look differently if you are the poor in<00:18:55.789> many<00:18:56.059> different<00:18:56.630> contexts<00:18:57.169> result<00:18:57.950> token 00:18:58.299 --> 00:18:58.309 align:start position:0% in many different contexts result token 00:18:58.309 --> 00:19:00.850 align:start position:0% in many different contexts result token vendor<00:18:58.760> differently<00:18:59.270> by<00:18:59.600> dream<00:18:59.870> logic<00:19:00.020> so 00:19:00.850 --> 00:19:00.860 align:start position:0% vendor differently by dream logic so 00:19:00.860 --> 00:19:03.730 align:start position:0% vendor differently by dream logic so currently<00:19:01.520> they<00:19:02.030> are<00:19:02.059> anyways<00:19:02.740> haulage 00:19:03.730 --> 00:19:03.740 align:start position:0% currently they are anyways haulage 00:19:03.740 --> 00:19:06.370 align:start position:0% currently they are anyways haulage company<00:19:04.010> and<00:19:04.880> open<00:19:05.659> source<00:19:05.840> of<00:19:05.929> what<00:19:06.049> has<00:19:06.260> been 00:19:06.370 --> 00:19:06.380 align:start position:0% company and open source of what has been 00:19:06.380 --> 00:19:06.970 align:start position:0% company and open source of what has been helpful 00:19:06.970 --> 00:19:06.980 align:start position:0% helpful 00:19:06.980 --> 00:19:08.740 align:start position:0% helpful but<00:19:07.220> it<00:19:07.340> only<00:19:07.460> worked<00:19:07.820> with<00:19:08.000> one<00:19:08.210> context 00:19:08.740 --> 00:19:08.750 align:start position:0% but it only worked with one context 00:19:08.750 --> 00:19:12.310 align:start position:0% but it only worked with one context which<00:19:09.020> is<00:19:09.049> for<00:19:09.580> wallet<00:19:10.580> context<00:19:10.970> so<00:19:11.690> to<00:19:12.140> make 00:19:12.310 --> 00:19:12.320 align:start position:0% which is for wallet context so to make 00:19:12.320 --> 00:19:12.940 align:start position:0% which is for wallet context so to make it<00:19:12.440> really<00:19:12.679> hard 00:19:12.940 --> 00:19:12.950 align:start position:0% it really hard 00:19:12.950 --> 00:19:14.710 align:start position:0% it really hard welcome<00:19:13.340> to<00:19:13.460> a<00:19:13.520> secure<00:19:13.820> Enclave<00:19:14.059> in<00:19:14.570> the 00:19:14.710 --> 00:19:14.720 align:start position:0% welcome to a secure Enclave in the 00:19:14.720 --> 00:19:16.270 align:start position:0% welcome to a secure Enclave in the browser<00:19:14.900> this<00:19:15.380> is<00:19:15.500> something<00:19:15.830> looking<00:19:16.130> at 00:19:16.270 --> 00:19:16.280 align:start position:0% browser this is something looking at 00:19:16.280 --> 00:19:19.090 align:start position:0% browser this is something looking at promoting<00:19:16.490> progress<00:19:17.500> as<00:19:18.500> a<00:19:18.559> context<00:19:19.010> based 00:19:19.090 --> 00:19:19.100 align:start position:0% promoting progress as a context based 00:19:19.100 --> 00:19:24.340 align:start position:0% promoting progress as a context based concept<00:19:20.059> concept<00:19:22.809> because<00:19:23.809> we<00:19:23.840> have<00:19:24.140> one 00:19:24.340 --> 00:19:24.350 align:start position:0% concept concept because we have one 00:19:24.350 --> 00:19:32.980 align:start position:0% concept concept because we have one major<00:19:24.500> cat<00:19:25.600> good<00:19:26.600> question<00:19:31.210> okay<00:19:32.210> assume<00:19:32.840> of 00:19:32.980 --> 00:19:32.990 align:start position:0% major cat good question okay assume of 00:19:32.990 --> 00:19:35.169 align:start position:0% major cat good question okay assume of the<00:19:33.169> public<00:19:33.620> or<00:19:33.799> private<00:19:34.010> key<00:19:34.429> pairs<00:19:34.730> and<00:19:35.120> you 00:19:35.169 --> 00:19:35.179 align:start position:0% the public or private key pairs and you 00:19:35.179 --> 00:19:37.000 align:start position:0% the public or private key pairs and you are<00:19:35.330> specific<00:19:36.289> does<00:19:36.440> it<00:19:36.500> have<00:19:36.590> to<00:19:36.710> be<00:19:36.770> like<00:19:36.980> a 00:19:37.000 --> 00:19:37.010 align:start position:0% are specific does it have to be like a 00:19:37.010 --> 00:19:38.950 align:start position:0% are specific does it have to be like a JSON<00:19:37.460> blob<00:19:37.700> or<00:19:37.730> can<00:19:38.000> be<00:19:38.120> a<00:19:38.150> Harvard<00:19:38.510> wallet<00:19:38.840> or 00:19:38.950 --> 00:19:38.960 align:start position:0% JSON blob or can be a Harvard wallet or 00:19:38.960 --> 00:19:40.570 align:start position:0% JSON blob or can be a Harvard wallet or that<00:19:39.080> kind<00:19:39.289> of<00:19:39.350> interact<00:19:39.830> with<00:19:39.950> the<00:19:40.070> keys<00:19:40.280> or 00:19:40.570 --> 00:19:40.580 align:start position:0% that kind of interact with the keys or 00:19:40.580 --> 00:19:43.000 align:start position:0% that kind of interact with the keys or is<00:19:40.700> it<00:19:40.820> just<00:19:40.850> better<00:19:41.210> mousetrap<00:19:41.690> okay<00:19:42.500> so<00:19:42.559> if 00:19:43.000 --> 00:19:43.010 align:start position:0% is it just better mousetrap okay so if 00:19:43.010 --> 00:19:44.350 align:start position:0% is it just better mousetrap okay so if you<00:19:43.100> want<00:19:43.309> to<00:19:43.370> kind<00:19:43.640> of<00:19:43.730> find<00:19:43.940> another<00:19:44.120> layer 00:19:44.350 --> 00:19:44.360 align:start position:0% you want to kind of find another layer 00:19:44.360 --> 00:19:46.000 align:start position:0% you want to kind of find another layer behind<00:19:44.659> open<00:19:45.080> script<00:19:45.350> let's<00:19:45.530> say<00:19:45.710> every<00:19:45.890> time 00:19:46.000 --> 00:19:46.010 align:start position:0% behind open script let's say every time 00:19:46.010 --> 00:19:47.680 align:start position:0% behind open script let's say every time the<00:19:46.159> transaction<00:19:46.520> is<00:19:46.940> going<00:19:47.150> to<00:19:47.210> be<00:19:47.330> signed 00:19:47.680 --> 00:19:47.690 align:start position:0% the transaction is going to be signed 00:19:47.690 --> 00:19:50.529 align:start position:0% the transaction is going to be signed assigning<00:19:48.350> doesn't<00:19:48.710> happen<00:19:48.830> means<00:19:49.159> in 00:19:50.529 --> 00:19:50.539 align:start position:0% assigning doesn't happen means in 00:19:50.539 --> 00:19:53.360 align:start position:0% assigning doesn't happen means in so<00:19:51.539> I<00:19:51.750> kept<00:19:51.960> thoroughly<00:19:52.440> at<00:19:52.559> device<00:19:52.799> that's 00:19:53.360 --> 00:19:53.370 align:start position:0% so I kept thoroughly at device that's 00:19:53.370 --> 00:19:54.260 align:start position:0% so I kept thoroughly at device that's something<00:19:53.669> a<00:19:53.700> little<00:19:53.940> different<00:19:54.210> here 00:19:54.260 --> 00:19:54.270 align:start position:0% something a little different here 00:19:54.270 --> 00:19:56.000 align:start position:0% something a little different here different<00:19:55.080> layout 00:19:56.000 --> 00:19:56.010 align:start position:0% different layout 00:19:56.010 --> 00:19:57.500 align:start position:0% different layout yeah<00:19:56.279> the<00:19:56.460> Thomas<00:19:56.730> put<00:19:56.850> that<00:19:56.970> we<00:19:57.059> take<00:19:57.270> care<00:19:57.390> of 00:19:57.500 --> 00:19:57.510 align:start position:0% yeah the Thomas put that we take care of 00:19:57.510 --> 00:19:59.899 align:start position:0% yeah the Thomas put that we take care of this<00:19:57.630> layer<00:19:57.840> could<00:19:58.230> be<00:19:58.289> careful<00:19:58.830> about<00:19:59.760> this 00:19:59.899 --> 00:19:59.909 align:start position:0% this layer could be careful about this 00:19:59.909 --> 00:20:00.200 align:start position:0% this layer could be careful about this layer 00:20:00.200 --> 00:20:00.210 align:start position:0% layer 00:20:00.210 --> 00:20:04.710 align:start position:0% layer alright<00:20:00.770> so<00:20:01.770> yeah<00:20:02.010> thank<00:20:02.399> you<00:20:02.460> very<00:20:02.610> much 00:20:04.710 --> 00:20:04.720 align:start position:0% alright so yeah thank you very much 00:20:04.720 --> 00:20:12.060 align:start position:0% alright so yeah thank you very much [Applause]