WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.849 align:start position:0% I'm<00:00:00.719> Sanjay<00:00:01.290> I<00:00:02.010> work<00:00:02.790> at<00:00:02.970> Intel<00:00:03.149> and<00:00:03.859> another 00:00:04.849 --> 00:00:04.859 align:start position:0% I'm Sanjay I work at Intel and another 00:00:04.859 --> 00:00:08.089 align:start position:0% I'm Sanjay I work at Intel and another at<00:00:05.640> Intel<00:00:06.000> I<00:00:06.259> constantly<00:00:07.259> think<00:00:07.440> around<00:00:07.919> like 00:00:08.089 --> 00:00:08.099 align:start position:0% at Intel I constantly think around like 00:00:08.099 --> 00:00:10.160 align:start position:0% at Intel I constantly think around like you<00:00:08.189> know<00:00:08.280> how<00:00:08.400> we<00:00:08.460> can<00:00:08.960> contribute<00:00:09.960> to 00:00:10.160 --> 00:00:10.170 align:start position:0% you know how we can contribute to 00:00:10.170 --> 00:00:14.589 align:start position:0% you know how we can contribute to etherium<00:00:11.120> and<00:00:12.120> I'm<00:00:12.540> one<00:00:12.750> of<00:00:12.900> the<00:00:13.080> co-chairs<00:00:14.040> at 00:00:14.589 --> 00:00:14.599 align:start position:0% etherium and I'm one of the co-chairs at 00:00:14.599 --> 00:00:18.439 align:start position:0% etherium and I'm one of the co-chairs at enterprises<00:00:15.599> Hyrum<00:00:15.870> Alliance<00:00:16.199> and<00:00:17.240> as<00:00:18.240> part 00:00:18.439 --> 00:00:18.449 align:start position:0% enterprises Hyrum Alliance and as part 00:00:18.449 --> 00:00:21.019 align:start position:0% enterprises Hyrum Alliance and as part of<00:00:18.539> that<00:00:18.600> we<00:00:19.470> released<00:00:19.859> the<00:00:20.430> clients<00:00:20.820> back 00:00:21.019 --> 00:00:21.029 align:start position:0% of that we released the clients back 00:00:21.029 --> 00:00:23.929 align:start position:0% of that we released the clients back which<00:00:21.890> you<00:00:22.890> know<00:00:23.010> requirements<00:00:23.760> for 00:00:23.929 --> 00:00:23.939 align:start position:0% which you know requirements for 00:00:23.939 --> 00:00:27.470 align:start position:0% which you know requirements for enterprise<00:00:24.390> clients<00:00:25.550> you<00:00:26.550> know<00:00:26.640> enterprise 00:00:27.470 --> 00:00:27.480 align:start position:0% enterprise clients you know enterprise 00:00:27.480 --> 00:00:30.620 align:start position:0% enterprise clients you know enterprise atheneum<00:00:27.900> clients<00:00:28.230> as<00:00:28.769> well<00:00:29.010> as<00:00:29.630> for 00:00:30.620 --> 00:00:30.630 align:start position:0% atheneum clients as well as for 00:00:30.630 --> 00:00:34.340 align:start position:0% atheneum clients as well as for scalability<00:00:31.410> and<00:00:31.769> things<00:00:31.949> and<00:00:32.610> privacy<00:00:33.350> which 00:00:34.340 --> 00:00:34.350 align:start position:0% scalability and things and privacy which 00:00:34.350 --> 00:00:37.010 align:start position:0% scalability and things and privacy which are<00:00:34.469> very<00:00:34.590> important<00:00:35.100> in<00:00:35.219> that<00:00:35.370> space<00:00:35.840> we<00:00:36.840> are 00:00:37.010 --> 00:00:37.020 align:start position:0% are very important in that space we are 00:00:37.020 --> 00:00:39.979 align:start position:0% are very important in that space we are exploring<00:00:37.380> various<00:00:37.590> solutions<00:00:38.250> and<00:00:38.899> one<00:00:39.899> of 00:00:39.979 --> 00:00:39.989 align:start position:0% exploring various solutions and one of 00:00:39.989 --> 00:00:42.260 align:start position:0% exploring various solutions and one of the<00:00:40.110> solutions<00:00:40.260> that<00:00:40.649> we<00:00:41.550> are<00:00:41.670> exploring<00:00:42.030> is 00:00:42.260 --> 00:00:42.270 align:start position:0% the solutions that we are exploring is 00:00:42.270 --> 00:00:46.310 align:start position:0% the solutions that we are exploring is around<00:00:42.570> trusted<00:00:43.020> compute<00:00:43.440> and<00:00:44.780> we<00:00:45.780> I<00:00:46.020> believe 00:00:46.310 --> 00:00:46.320 align:start position:0% around trusted compute and we I believe 00:00:46.320 --> 00:00:50.240 align:start position:0% around trusted compute and we I believe the<00:00:46.980> e<00:00:47.010> has<00:00:47.640> released<00:00:48.059> an<00:00:48.899> early<00:00:49.500> version<00:00:49.890> of 00:00:50.240 --> 00:00:50.250 align:start position:0% the e has released an early version of 00:00:50.250 --> 00:00:54.260 align:start position:0% the e has released an early version of that<00:00:50.879> spec<00:00:51.300> and<00:00:51.570> we<00:00:52.410> just<00:00:52.649> wanna<00:00:52.890> eight<00:00:53.270> today 00:00:54.260 --> 00:00:54.270 align:start position:0% that spec and we just wanna eight today 00:00:54.270 --> 00:00:57.290 align:start position:0% that spec and we just wanna eight today introduce<00:00:55.199> that<00:00:55.530> briefly<00:00:56.010> and<00:00:56.280> then<00:00:56.969> also 00:00:57.290 --> 00:00:57.300 align:start position:0% introduce that briefly and then also 00:00:57.300 --> 00:01:02.180 align:start position:0% introduce that briefly and then also give<00:00:57.989> a<00:00:58.160> perspective<00:00:59.160> on<00:01:00.469> the<00:01:01.469> work<00:01:01.710> that's 00:01:02.180 --> 00:01:02.190 align:start position:0% give a perspective on the work that's 00:01:02.190 --> 00:01:04.609 align:start position:0% give a perspective on the work that's happening<00:01:02.699> in<00:01:03.000> the<00:01:03.120> ecosystem<00:01:03.840> by<00:01:04.260> various 00:01:04.609 --> 00:01:04.619 align:start position:0% happening in the ecosystem by various 00:01:04.619 --> 00:01:08.120 align:start position:0% happening in the ecosystem by various partners<00:01:05.400> on<00:01:05.729> using<00:01:06.600> trusted<00:01:06.930> compute<00:01:07.350> so 00:01:08.120 --> 00:01:08.130 align:start position:0% partners on using trusted compute so 00:01:08.130 --> 00:01:09.620 align:start position:0% partners on using trusted compute so that<00:01:08.280> like<00:01:08.490> you<00:01:08.640> know<00:01:08.760> connecting<00:01:09.330> the<00:01:09.450> dots 00:01:09.620 --> 00:01:09.630 align:start position:0% that like you know connecting the dots 00:01:09.630 --> 00:01:14.060 align:start position:0% that like you know connecting the dots for<00:01:09.930> people<00:01:10.970> you<00:01:11.970> know<00:01:12.030> between<00:01:12.960> what<00:01:13.920> is 00:01:14.060 --> 00:01:14.070 align:start position:0% for people you know between what is 00:01:14.070 --> 00:01:15.620 align:start position:0% for people you know between what is trusted<00:01:14.400> compute<00:01:14.760> and<00:01:14.909> what<00:01:15.090> kind<00:01:15.299> of<00:01:15.390> things 00:01:15.620 --> 00:01:15.630 align:start position:0% trusted compute and what kind of things 00:01:15.630 --> 00:01:17.690 align:start position:0% trusted compute and what kind of things it's<00:01:15.810> being<00:01:16.020> used<00:01:16.200> for<00:01:16.350> so<00:01:17.009> we<00:01:17.189> have<00:01:17.340> a<00:01:17.369> packed 00:01:17.690 --> 00:01:17.700 align:start position:0% it's being used for so we have a packed 00:01:17.700 --> 00:01:21.200 align:start position:0% it's being used for so we have a packed session<00:01:18.150> roughly<00:01:18.689> six<00:01:18.930> presentations<00:01:19.799> and<00:01:20.210> a 00:01:21.200 --> 00:01:21.210 align:start position:0% session roughly six presentations and a 00:01:21.210 --> 00:01:25.010 align:start position:0% session roughly six presentations and a panel<00:01:21.600> and<00:01:22.549> hopefully<00:01:23.549> it'll<00:01:23.700> be<00:01:23.790> fun<00:01:24.030> as<00:01:24.750> we 00:01:25.010 --> 00:01:25.020 align:start position:0% panel and hopefully it'll be fun as we 00:01:25.020 --> 00:01:30.410 align:start position:0% panel and hopefully it'll be fun as we go<00:01:25.140> through<00:01:25.350> this<00:01:27.619> so<00:01:28.619> also<00:01:28.950> as<00:01:29.729> I<00:01:29.850> said<00:01:30.060> I<00:01:30.210> will 00:01:30.410 --> 00:01:30.420 align:start position:0% go through this so also as I said I will 00:01:30.420 --> 00:01:33.620 align:start position:0% go through this so also as I said I will just<00:01:30.600> talk<00:01:31.380> about<00:01:31.909> the<00:01:32.909> work<00:01:33.090> that<00:01:33.119> we<00:01:33.479> have 00:01:33.620 --> 00:01:33.630 align:start position:0% just talk about the work that we have 00:01:33.630 --> 00:01:36.830 align:start position:0% just talk about the work that we have done<00:01:33.659> briefly<00:01:34.170> and<00:01:34.439> then<00:01:35.150> you<00:01:36.150> know<00:01:36.270> call<00:01:36.600> it<00:01:36.750> a 00:01:36.830 --> 00:01:36.840 align:start position:0% done briefly and then you know call it a 00:01:36.840 --> 00:01:44.719 align:start position:0% done briefly and then you know call it a presenter<00:01:37.590> so<00:01:37.860> one<00:01:38.040> by<00:01:38.159> one<00:01:41.360> so<00:01:42.360> like<00:01:43.009> so<00:01:44.009> just 00:01:44.719 --> 00:01:44.729 align:start position:0% presenter so one by one so like so just 00:01:44.729 --> 00:01:47.300 align:start position:0% presenter so one by one so like so just a<00:01:45.119> brief<00:01:45.360> you<00:01:46.110> know<00:01:46.290> what<00:01:46.890> is<00:01:47.009> the<00:01:47.100> enterprise 00:01:47.300 --> 00:01:47.310 align:start position:0% a brief you know what is the enterprise 00:01:47.310 --> 00:01:51.800 align:start position:0% a brief you know what is the enterprise aetherium<00:01:48.200> in<00:01:49.200> case<00:01:49.530> people<00:01:50.070> here<00:01:50.430> are<00:01:50.640> not<00:01:51.299> up 00:01:51.800 --> 00:01:51.810 align:start position:0% aetherium in case people here are not up 00:01:51.810 --> 00:01:52.910 align:start position:0% aetherium in case people here are not up to<00:01:51.869> it 00:01:52.910 --> 00:01:52.920 align:start position:0% to it 00:01:52.920 --> 00:01:56.810 align:start position:0% to it Enterprise<00:01:53.820> aetherium<00:01:54.210> was<00:01:54.619> a<00:01:55.619> year-plus<00:01:56.430> ago 00:01:56.810 --> 00:01:56.820 align:start position:0% Enterprise aetherium was a year-plus ago 00:01:56.820 --> 00:01:58.850 align:start position:0% Enterprise aetherium was a year-plus ago several<00:01:57.540> of<00:01:57.750> us<00:01:57.899> got<00:01:58.110> together<00:01:58.290> and<00:01:58.590> we 00:01:58.850 --> 00:01:58.860 align:start position:0% several of us got together and we 00:01:58.860 --> 00:02:01.940 align:start position:0% several of us got together and we realized<00:01:59.399> that<00:01:59.490> you<00:01:59.729> know<00:02:00.469> there<00:02:01.469> are<00:02:01.500> lot<00:02:01.799> of 00:02:01.940 --> 00:02:01.950 align:start position:0% realized that you know there are lot of 00:02:01.950 --> 00:02:05.480 align:start position:0% realized that you know there are lot of demand<00:02:02.369> from<00:02:02.939> enterprises<00:02:03.890> using<00:02:04.890> aetherium 00:02:05.480 --> 00:02:05.490 align:start position:0% demand from enterprises using aetherium 00:02:05.490 --> 00:02:08.719 align:start position:0% demand from enterprises using aetherium based<00:02:05.810> in<00:02:06.810> a<00:02:06.930> blockchain<00:02:07.170> for<00:02:07.979> for<00:02:08.310> enterprise 00:02:08.719 --> 00:02:08.729 align:start position:0% based in a blockchain for for enterprise 00:02:08.729 --> 00:02:10.790 align:start position:0% based in a blockchain for for enterprise applications<00:02:09.390> there<00:02:10.200> were<00:02:10.289> several<00:02:10.470> clients 00:02:10.790 --> 00:02:10.800 align:start position:0% applications there were several clients 00:02:10.800 --> 00:02:11.710 align:start position:0% applications there were several clients and 00:02:11.710 --> 00:02:11.720 align:start position:0% and 00:02:11.720 --> 00:02:14.170 align:start position:0% and what<00:02:12.590> we<00:02:12.710> were<00:02:12.830> seeing<00:02:13.040> is<00:02:13.220> like<00:02:13.370> some<00:02:13.850> kind<00:02:13.880> of 00:02:14.170 --> 00:02:14.180 align:start position:0% what we were seeing is like some kind of 00:02:14.180 --> 00:02:17.280 align:start position:0% what we were seeing is like some kind of fragmentation<00:02:14.720> and<00:02:15.370> things<00:02:16.370> like<00:02:16.550> that<00:02:16.610> and 00:02:17.280 --> 00:02:17.290 align:start position:0% fragmentation and things like that and 00:02:17.290 --> 00:02:20.590 align:start position:0% fragmentation and things like that and not<00:02:18.290> a<00:02:18.350> not<00:02:18.620> a<00:02:18.680> cohesive<00:02:19.520> way<00:02:19.670> to<00:02:20.240> address 00:02:20.590 --> 00:02:20.600 align:start position:0% not a not a cohesive way to address 00:02:20.600 --> 00:02:22.930 align:start position:0% not a not a cohesive way to address enterprise<00:02:21.350> requirements<00:02:21.920> so<00:02:22.460> that's<00:02:22.670> where 00:02:22.930 --> 00:02:22.940 align:start position:0% enterprise requirements so that's where 00:02:22.940 --> 00:02:24.520 align:start position:0% enterprise requirements so that's where this<00:02:23.150> enterprise 00:02:24.520 --> 00:02:24.530 align:start position:0% this enterprise 00:02:24.530 --> 00:02:35.700 align:start position:0% this enterprise Alliance<00:02:25.130> game<00:02:25.370> came<00:02:25.970> about<00:02:26.270> and<00:02:27.490> and<00:02:33.010> so 00:02:35.700 --> 00:02:35.710 align:start position:0% Alliance game came about and and so 00:02:35.710 --> 00:02:39.340 align:start position:0% Alliance game came about and and so early<00:02:36.710> morning<00:02:37.070> so<00:02:37.910> so<00:02:38.840> the<00:02:38.960> thing<00:02:39.110> is<00:02:39.170> like 00:02:39.340 --> 00:02:39.350 align:start position:0% early morning so so the thing is like 00:02:39.350 --> 00:02:40.780 align:start position:0% early morning so so the thing is like you<00:02:39.440> know<00:02:39.500> there<00:02:39.980> are<00:02:40.070> four<00:02:40.250> things<00:02:40.550> about 00:02:40.780 --> 00:02:40.790 align:start position:0% you know there are four things about 00:02:40.790 --> 00:02:43.480 align:start position:0% you know there are four things about this<00:02:40.970> enterprise<00:02:41.770> Alliance<00:02:42.770> really<00:02:43.160> is<00:02:43.280> that 00:02:43.480 --> 00:02:43.490 align:start position:0% this enterprise Alliance really is that 00:02:43.490 --> 00:02:47.199 align:start position:0% this enterprise Alliance really is that the<00:02:44.150> one<00:02:44.390> is<00:02:44.540> defining<00:02:45.700> standards<00:02:46.700> around 00:02:47.199 --> 00:02:47.209 align:start position:0% the one is defining standards around 00:02:47.209 --> 00:02:50.949 align:start position:0% the one is defining standards around like<00:02:47.690> you<00:02:47.840> know<00:02:47.959> how<00:02:48.170> enterprise<00:02:48.890> clients<00:02:49.959> you 00:02:50.949 --> 00:02:50.959 align:start position:0% like you know how enterprise clients you 00:02:50.959 --> 00:02:53.710 align:start position:0% like you know how enterprise clients you know<00:02:51.110> work<00:02:51.880> interoperate<00:02:52.880> and<00:02:53.090> things<00:02:53.570> like 00:02:53.710 --> 00:02:53.720 align:start position:0% know work interoperate and things like 00:02:53.720 --> 00:02:56.080 align:start position:0% know work interoperate and things like that<00:02:54.040> address<00:02:55.040> specifically<00:02:55.520> some<00:02:55.760> of<00:02:55.790> the 00:02:56.080 --> 00:02:56.090 align:start position:0% that address specifically some of the 00:02:56.090 --> 00:02:58.180 align:start position:0% that address specifically some of the requirements<00:02:57.050> of<00:02:57.140> enterprise<00:02:57.530> clients<00:02:57.770> and<00:02:58.100> I 00:02:58.180 --> 00:02:58.190 align:start position:0% requirements of enterprise clients and I 00:02:58.190 --> 00:03:01.080 align:start position:0% requirements of enterprise clients and I will<00:02:58.400> talk<00:02:58.550> about<00:02:58.580> them<00:02:59.000> in<00:02:59.330> the<00:02:59.390> next<00:02:59.660> slide 00:03:01.080 --> 00:03:01.090 align:start position:0% will talk about them in the next slide 00:03:01.090 --> 00:03:06.460 align:start position:0% will talk about them in the next slide we<00:03:02.090> want<00:03:03.050> to<00:03:03.440> leverage<00:03:04.070> build<00:03:04.580> upon<00:03:05.170> all<00:03:06.170> the 00:03:06.460 --> 00:03:06.470 align:start position:0% we want to leverage build upon all the 00:03:06.470 --> 00:03:09.070 align:start position:0% we want to leverage build upon all the work<00:03:06.650> that<00:03:06.950> is<00:03:07.160> happening<00:03:07.190> within<00:03:08.120> public<00:03:08.780> III 00:03:09.070 --> 00:03:09.080 align:start position:0% work that is happening within public III 00:03:09.080 --> 00:03:13.260 align:start position:0% work that is happening within public III amount<00:03:09.550> scalability<00:03:10.550> privacy<00:03:11.209> and<00:03:12.010> you<00:03:13.010> know 00:03:13.260 --> 00:03:13.270 align:start position:0% amount scalability privacy and you know 00:03:13.270 --> 00:03:16.060 align:start position:0% amount scalability privacy and you know embraced<00:03:14.270> all<00:03:14.570> of<00:03:14.720> that<00:03:14.900> and<00:03:15.170> extend<00:03:15.650> that<00:03:15.800> and 00:03:16.060 --> 00:03:16.070 align:start position:0% embraced all of that and extend that and 00:03:16.070 --> 00:03:18.310 align:start position:0% embraced all of that and extend that and we'll<00:03:17.030> talk<00:03:17.209> briefly<00:03:17.450> about<00:03:17.720> that<00:03:18.080> and 00:03:18.310 --> 00:03:18.320 align:start position:0% we'll talk briefly about that and 00:03:18.320 --> 00:03:22.620 align:start position:0% we'll talk briefly about that and finally<00:03:19.130> you<00:03:19.400> know<00:03:20.019> great<00:03:21.130> interoperability 00:03:22.620 --> 00:03:22.630 align:start position:0% finally you know great interoperability 00:03:22.630 --> 00:03:26.170 align:start position:0% finally you know great interoperability and<00:03:23.630> certification<00:03:24.380> at<00:03:24.709> all<00:03:24.950> places<00:03:25.550> where<00:03:25.820> it 00:03:26.170 --> 00:03:26.180 align:start position:0% and certification at all places where it 00:03:26.180 --> 00:03:29.580 align:start position:0% and certification at all places where it makes<00:03:26.450> sense<00:03:27.459> so<00:03:28.459> so<00:03:28.820> with<00:03:29.000> that<00:03:29.150> quick 00:03:29.580 --> 00:03:29.590 align:start position:0% makes sense so so with that quick 00:03:29.590 --> 00:03:32.770 align:start position:0% makes sense so so with that quick overview<00:03:30.590> of<00:03:30.620> that<00:03:31.450> when<00:03:32.450> we<00:03:32.570> talk<00:03:32.750> about 00:03:32.770 --> 00:03:32.780 align:start position:0% overview of that when we talk about 00:03:32.780 --> 00:03:37.080 align:start position:0% overview of that when we talk about enterprise<00:03:34.330> etherium<00:03:35.590> there<00:03:36.590> are<00:03:36.680> several 00:03:37.080 --> 00:03:37.090 align:start position:0% enterprise etherium there are several 00:03:37.090 --> 00:03:41.009 align:start position:0% enterprise etherium there are several call<00:03:38.090> it<00:03:38.239> challenges<00:03:38.780> call<00:03:39.019> it<00:03:39.140> requirements 00:03:41.009 --> 00:03:41.019 align:start position:0% call it challenges call it requirements 00:03:41.019 --> 00:03:44.530 align:start position:0% call it challenges call it requirements privacy<00:03:42.340> is<00:03:43.340> very<00:03:43.549> important<00:03:44.120> in<00:03:44.269> the<00:03:44.390> sense 00:03:44.530 --> 00:03:44.540 align:start position:0% privacy is very important in the sense 00:03:44.540 --> 00:03:48.190 align:start position:0% privacy is very important in the sense that<00:03:44.840> you<00:03:45.709> might<00:03:45.890> have<00:03:46.130> you<00:03:46.519> know<00:03:46.670> for<00:03:47.450> as<00:03:47.989> an 00:03:48.190 --> 00:03:48.200 align:start position:0% that you might have you know for as an 00:03:48.200 --> 00:03:51.940 align:start position:0% that you might have you know for as an example<00:03:48.530> participating<00:03:49.280> banks<00:03:49.930> on<00:03:50.930> a<00:03:50.989> on<00:03:51.650> same 00:03:51.940 --> 00:03:51.950 align:start position:0% example participating banks on a on same 00:03:51.950 --> 00:03:53.890 align:start position:0% example participating banks on a on same chain<00:03:52.250> but<00:03:52.760> the<00:03:52.880> transactions<00:03:53.420> between<00:03:53.570> two 00:03:53.890 --> 00:03:53.900 align:start position:0% chain but the transactions between two 00:03:53.900 --> 00:03:55.720 align:start position:0% chain but the transactions between two banks<00:03:54.080> don't<00:03:54.799> need<00:03:55.070> to<00:03:55.190> be<00:03:55.310> disclosed<00:03:55.700> to 00:03:55.720 --> 00:03:55.730 align:start position:0% banks don't need to be disclosed to 00:03:55.730 --> 00:03:59.410 align:start position:0% banks don't need to be disclosed to other<00:03:56.480> two<00:03:56.690> banks<00:03:57.340> so<00:03:58.340> that's<00:03:58.519> a<00:03:58.850> requirement 00:03:59.410 --> 00:03:59.420 align:start position:0% other two banks so that's a requirement 00:03:59.420 --> 00:04:03.250 align:start position:0% other two banks so that's a requirement a<00:03:59.570> scalability<00:04:00.820> more<00:04:01.820> much<00:04:02.060> more<00:04:02.269> than<00:04:02.540> you 00:04:03.250 --> 00:04:03.260 align:start position:0% a scalability more much more than you 00:04:03.260 --> 00:04:05.830 align:start position:0% a scalability more much more than you know<00:04:03.670> just<00:04:04.670> the<00:04:05.180> sheer<00:04:05.360> amount<00:04:05.600> of 00:04:05.830 --> 00:04:05.840 align:start position:0% know just the sheer amount of 00:04:05.840 --> 00:04:07.900 align:start position:0% know just the sheer amount of transactions<00:04:06.410> we<00:04:06.680> need<00:04:06.920> higher<00:04:07.160> scalability 00:04:07.900 --> 00:04:07.910 align:start position:0% transactions we need higher scalability 00:04:07.910 --> 00:04:11.590 align:start position:0% transactions we need higher scalability and<00:04:08.980> 15<00:04:09.980> transactions<00:04:10.519> doesn't<00:04:10.850> do<00:04:10.970> it<00:04:11.120> for<00:04:11.450> us 00:04:11.590 --> 00:04:11.600 align:start position:0% and 15 transactions doesn't do it for us 00:04:11.600 --> 00:04:14.620 align:start position:0% and 15 transactions doesn't do it for us or<00:04:11.750> 10<00:04:12.019> transactions<00:04:12.640> but<00:04:13.640> you<00:04:13.910> know<00:04:14.030> we<00:04:14.420> are 00:04:14.620 --> 00:04:14.630 align:start position:0% or 10 transactions but you know we are 00:04:14.630 --> 00:04:16.240 align:start position:0% or 10 transactions but you know we are trying<00:04:14.750> to<00:04:14.989> do<00:04:15.080> our<00:04:15.200> work<00:04:15.440> and<00:04:15.500> build<00:04:15.980> upon 00:04:16.240 --> 00:04:16.250 align:start position:0% trying to do our work and build upon 00:04:16.250 --> 00:04:17.690 align:start position:0% trying to do our work and build upon whatever<00:04:16.640> the 00:04:17.690 --> 00:04:17.700 align:start position:0% whatever the 00:04:17.700 --> 00:04:20.390 align:start position:0% whatever the Foundation<00:04:18.450> does<00:04:18.600> and<00:04:18.980> permissioning<00:04:19.980> in<00:04:20.250> the 00:04:20.390 --> 00:04:20.400 align:start position:0% Foundation does and permissioning in the 00:04:20.400 --> 00:04:22.880 align:start position:0% Foundation does and permissioning in the sense<00:04:20.610> that<00:04:21.170> being<00:04:22.170> an<00:04:22.380> enterprise<00:04:22.860> network 00:04:22.880 --> 00:04:22.890 align:start position:0% sense that being an enterprise network 00:04:22.890 --> 00:04:24.860 align:start position:0% sense that being an enterprise network there<00:04:23.580> is<00:04:23.730> this<00:04:23.880> requirement<00:04:24.240> in<00:04:24.570> the<00:04:24.660> sense 00:04:24.860 --> 00:04:24.870 align:start position:0% there is this requirement in the sense 00:04:24.870 --> 00:04:28.940 align:start position:0% there is this requirement in the sense like<00:04:26.270> we<00:04:27.270> see<00:04:27.480> hybrid<00:04:27.870> networks<00:04:28.290> in<00:04:28.590> the<00:04:28.770> sense 00:04:28.940 --> 00:04:28.950 align:start position:0% like we see hybrid networks in the sense 00:04:28.950 --> 00:04:30.740 align:start position:0% like we see hybrid networks in the sense that<00:04:29.100> there<00:04:29.250> are<00:04:29.400> certain<00:04:29.820> actors<00:04:30.270> that<00:04:30.540> will 00:04:30.740 --> 00:04:30.750 align:start position:0% that there are certain actors that will 00:04:30.750 --> 00:04:33.650 align:start position:0% that there are certain actors that will be<00:04:30.900> permissioned<00:04:31.770> and<00:04:32.070> have<00:04:32.730> roles<00:04:33.030> in<00:04:33.480> terms 00:04:33.650 --> 00:04:33.660 align:start position:0% be permissioned and have roles in terms 00:04:33.660 --> 00:04:36.140 align:start position:0% be permissioned and have roles in terms of<00:04:33.870> maybe<00:04:34.770> there<00:04:35.130> are<00:04:35.190> certain<00:04:35.370> substitue<00:04:35.970> can 00:04:36.140 --> 00:04:36.150 align:start position:0% of maybe there are certain substitue can 00:04:36.150 --> 00:04:37.940 align:start position:0% of maybe there are certain substitue can deploy<00:04:36.450> smart<00:04:36.780> contacts<00:04:37.380> there's<00:04:37.620> certain 00:04:37.940 --> 00:04:37.950 align:start position:0% deploy smart contacts there's certain 00:04:37.950 --> 00:04:40.760 align:start position:0% deploy smart contacts there's certain subsets<00:04:38.370> who<00:04:38.490> can<00:04:38.700> you<00:04:39.210> know<00:04:39.770> initiate 00:04:40.760 --> 00:04:40.770 align:start position:0% subsets who can you know initiate 00:04:40.770 --> 00:04:43.400 align:start position:0% subsets who can you know initiate certain<00:04:41.100> transactions<00:04:41.640> but<00:04:42.240> then<00:04:42.450> there<00:04:43.110> are 00:04:43.400 --> 00:04:43.410 align:start position:0% certain transactions but then there are 00:04:43.410 --> 00:04:45.770 align:start position:0% certain transactions but then there are in<00:04:44.220> case<00:04:44.400> of<00:04:44.520> hybrid<00:04:44.880> networks<00:04:45.240> we<00:04:45.390> do<00:04:45.600> see 00:04:45.770 --> 00:04:45.780 align:start position:0% in case of hybrid networks we do see 00:04:45.780 --> 00:04:48.050 align:start position:0% in case of hybrid networks we do see like<00:04:46.170> you<00:04:46.260> know<00:04:46.380> certain<00:04:47.220> people<00:04:47.760> from<00:04:47.850> the 00:04:48.050 --> 00:04:48.060 align:start position:0% like you know certain people from the 00:04:48.060 --> 00:04:49.460 align:start position:0% like you know certain people from the public<00:04:48.360> side<00:04:48.510> of<00:04:48.660> the<00:04:48.750> world<00:04:48.900> interacting 00:04:49.460 --> 00:04:49.470 align:start position:0% public side of the world interacting 00:04:49.470 --> 00:04:52.070 align:start position:0% public side of the world interacting with<00:04:49.620> this<00:04:50.100> so<00:04:50.550> we<00:04:50.730> have<00:04:50.760> this<00:04:51.180> to<00:04:51.690> figure<00:04:51.930> out 00:04:52.070 --> 00:04:52.080 align:start position:0% with this so we have this to figure out 00:04:52.080 --> 00:04:55.310 align:start position:0% with this so we have this to figure out what<00:04:52.320> what<00:04:53.040> the<00:04:53.130> identities<00:04:53.730> are<00:04:53.940> and<00:04:54.270> how<00:04:54.420> how 00:04:55.310 --> 00:04:55.320 align:start position:0% what what the identities are and how how 00:04:55.320 --> 00:04:57.470 align:start position:0% what what the identities are and how how they<00:04:55.500> you<00:04:55.860> know<00:04:56.040> are<00:04:56.070> enrolled<00:04:56.850> into<00:04:57.240> the 00:04:57.470 --> 00:04:57.480 align:start position:0% they you know are enrolled into the 00:04:57.480 --> 00:05:00.490 align:start position:0% they you know are enrolled into the system<00:04:58.160> the<00:04:59.160> other<00:04:59.340> part<00:04:59.670> of<00:04:59.790> it<00:04:59.940> is<00:05:00.000> like 00:05:00.490 --> 00:05:00.500 align:start position:0% system the other part of it is like 00:05:00.500 --> 00:05:02.620 align:start position:0% system the other part of it is like [Music] 00:05:02.620 --> 00:05:02.630 align:start position:0% [Music] 00:05:02.630 --> 00:05:05.240 align:start position:0% [Music] interacting<00:05:03.630> with<00:05:03.780> the<00:05:03.840> external<00:05:04.290> world<00:05:04.950> in 00:05:05.240 --> 00:05:05.250 align:start position:0% interacting with the external world in 00:05:05.250 --> 00:05:07.880 align:start position:0% interacting with the external world in the<00:05:05.850> sense<00:05:05.970> to<00:05:06.210> initiate<00:05:06.660> transactions<00:05:07.380> you 00:05:07.880 --> 00:05:07.890 align:start position:0% the sense to initiate transactions you 00:05:07.890 --> 00:05:11.000 align:start position:0% the sense to initiate transactions you have<00:05:07.920> to<00:05:08.310> make<00:05:08.910> sure<00:05:09.150> that<00:05:09.390> your<00:05:09.720> wallet<00:05:10.680> or 00:05:11.000 --> 00:05:11.010 align:start position:0% have to make sure that your wallet or 00:05:11.010 --> 00:05:14.000 align:start position:0% have to make sure that your wallet or the<00:05:11.220> keys<00:05:11.970> that<00:05:12.210> are<00:05:12.270> used<00:05:12.450> to<00:05:13.010> generate 00:05:14.000 --> 00:05:14.010 align:start position:0% the keys that are used to generate 00:05:14.010 --> 00:05:17.930 align:start position:0% the keys that are used to generate transactions<00:05:14.700> are<00:05:14.850> very<00:05:15.150> protected<00:05:16.760> from<00:05:17.760> the 00:05:17.930 --> 00:05:17.940 align:start position:0% transactions are very protected from the 00:05:17.940 --> 00:05:19.730 align:start position:0% transactions are very protected from the enterprise<00:05:18.120> perspective<00:05:18.900> because<00:05:19.170> you<00:05:19.590> are 00:05:19.730 --> 00:05:19.740 align:start position:0% enterprise perspective because you are 00:05:19.740 --> 00:05:22.130 align:start position:0% enterprise perspective because you are basically<00:05:20.060> representing<00:05:21.060> someone<00:05:21.330> when<00:05:21.960> you 00:05:22.130 --> 00:05:22.140 align:start position:0% basically representing someone when you 00:05:22.140 --> 00:05:25.420 align:start position:0% basically representing someone when you are<00:05:22.310> initiating<00:05:23.310> a<00:05:23.400> transaction<00:05:23.970> and<00:05:24.840> then 00:05:25.420 --> 00:05:25.430 align:start position:0% are initiating a transaction and then 00:05:25.430 --> 00:05:28.400 align:start position:0% are initiating a transaction and then other<00:05:26.430> aspect<00:05:26.910> of<00:05:27.030> the<00:05:27.270> connecting<00:05:28.200> to<00:05:28.320> the 00:05:28.400 --> 00:05:28.410 align:start position:0% other aspect of the connecting to the 00:05:28.410 --> 00:05:30.680 align:start position:0% other aspect of the connecting to the outside<00:05:28.710> world<00:05:28.920> is<00:05:29.150> you<00:05:30.150> know<00:05:30.270> bringing 00:05:30.680 --> 00:05:30.690 align:start position:0% outside world is you know bringing 00:05:30.690 --> 00:05:33.950 align:start position:0% outside world is you know bringing information<00:05:31.440> from<00:05:32.120> from<00:05:33.120> various<00:05:33.420> Oracle's 00:05:33.950 --> 00:05:33.960 align:start position:0% information from from various Oracle's 00:05:33.960 --> 00:05:36.770 align:start position:0% information from from various Oracle's into<00:05:34.260> the<00:05:34.410> system<00:05:34.800> beat<00:05:35.730> price<00:05:36.300> of<00:05:36.570> the 00:05:36.770 --> 00:05:36.780 align:start position:0% into the system beat price of the 00:05:36.780 --> 00:05:40.550 align:start position:0% into the system beat price of the commodity<00:05:37.080> or<00:05:37.710> you<00:05:38.670> know<00:05:38.960> whether<00:05:39.960> in<00:05:40.230> certain 00:05:40.550 --> 00:05:40.560 align:start position:0% commodity or you know whether in certain 00:05:40.560 --> 00:05:43.550 align:start position:0% commodity or you know whether in certain place<00:05:41.060> whatever<00:05:42.060> that<00:05:42.270> might<00:05:42.480> be<00:05:42.540> so<00:05:43.050> how<00:05:43.500> do 00:05:43.550 --> 00:05:43.560 align:start position:0% place whatever that might be so how do 00:05:43.560 --> 00:05:45.470 align:start position:0% place whatever that might be so how do we<00:05:43.680> bring<00:05:43.920> all<00:05:44.100> of<00:05:44.250> that<00:05:44.430> in<00:05:44.610> an<00:05:44.880> atrocity<00:05:45.150> to<00:05:45.450> a 00:05:45.470 --> 00:05:45.480 align:start position:0% we bring all of that in an atrocity to a 00:05:45.480 --> 00:05:50.120 align:start position:0% we bring all of that in an atrocity to a straight<00:05:46.200> away<00:05:46.350> into<00:05:46.980> this<00:05:49.010> into<00:05:50.010> the 00:05:50.120 --> 00:05:50.130 align:start position:0% straight away into this into the 00:05:50.130 --> 00:05:55.750 align:start position:0% straight away into this into the implementation<00:05:50.340> into<00:05:51.090> deployments<00:05:51.630> so 00:05:55.750 --> 00:05:55.760 align:start position:0% 00:05:55.760 --> 00:05:59.540 align:start position:0% scalability<00:05:56.760> right<00:05:57.950> you<00:05:58.950> guys<00:05:59.130> probably<00:05:59.400> have 00:05:59.540 --> 00:05:59.550 align:start position:0% scalability right you guys probably have 00:05:59.550 --> 00:06:02.180 align:start position:0% scalability right you guys probably have heard<00:06:00.420> all<00:06:00.690> of<00:06:00.840> these<00:06:00.990> things<00:06:01.290> so<00:06:01.920> I'm<00:06:02.040> not 00:06:02.180 --> 00:06:02.190 align:start position:0% heard all of these things so I'm not 00:06:02.190 --> 00:06:05.630 align:start position:0% heard all of these things so I'm not going<00:06:02.370> to<00:06:02.490> repeat<00:06:03.650> so<00:06:04.650> the<00:06:04.770> point<00:06:05.040> really<00:06:05.430> here 00:06:05.630 --> 00:06:05.640 align:start position:0% going to repeat so the point really here 00:06:05.640 --> 00:06:10.540 align:start position:0% going to repeat so the point really here is<00:06:05.820> that<00:06:06.560> we<00:06:07.560> are<00:06:08.270> you<00:06:09.270> know<00:06:09.390> going<00:06:09.840> to<00:06:10.050> use 00:06:10.540 --> 00:06:10.550 align:start position:0% is that we are you know going to use 00:06:10.550 --> 00:06:14.560 align:start position:0% is that we are you know going to use these<00:06:11.550> you<00:06:12.210> know<00:06:12.330> very<00:06:13.050> excited<00:06:13.590> to<00:06:13.710> see<00:06:13.860> this 00:06:14.560 --> 00:06:14.570 align:start position:0% these you know very excited to see this 00:06:14.570 --> 00:06:18.170 align:start position:0% these you know very excited to see this aetherium<00:06:15.570> to<00:06:15.720> rot<00:06:15.870> or<00:06:16.050> serenity<00:06:16.770> as<00:06:17.610> Vitalik 00:06:18.170 --> 00:06:18.180 align:start position:0% aetherium to rot or serenity as Vitalik 00:06:18.180 --> 00:06:22.160 align:start position:0% aetherium to rot or serenity as Vitalik talked<00:06:18.390> about<00:06:18.630> it<00:06:18.780> yesterday<00:06:19.130> and<00:06:21.170> so 00:06:22.160 --> 00:06:22.170 align:start position:0% talked about it yesterday and so 00:06:22.170 --> 00:06:24.770 align:start position:0% talked about it yesterday and so wherever<00:06:22.530> we<00:06:23.370> can<00:06:23.520> use<00:06:23.760> the<00:06:24.060> beacon<00:06:24.420> chain<00:06:24.600> is 00:06:24.770 --> 00:06:24.780 align:start position:0% wherever we can use the beacon chain is 00:06:24.780 --> 00:06:26.580 align:start position:0% wherever we can use the beacon chain is very<00:06:24.810> exciting 00:06:26.580 --> 00:06:26.590 align:start position:0% very exciting 00:06:26.590 --> 00:06:28.710 align:start position:0% very exciting we<00:06:26.680> will<00:06:26.800> use<00:06:26.980> these<00:06:27.220> showering<00:06:27.850> plasma<00:06:28.480> very 00:06:28.710 --> 00:06:28.720 align:start position:0% we will use these showering plasma very 00:06:28.720 --> 00:06:31.110 align:start position:0% we will use these showering plasma very well<00:06:29.050> when<00:06:29.350> they<00:06:29.500> become<00:06:29.800> more<00:06:30.010> you<00:06:31.000> know 00:06:31.110 --> 00:06:31.120 align:start position:0% well when they become more you know 00:06:31.120 --> 00:06:35.970 align:start position:0% well when they become more you know robust<00:06:31.540> defined<00:06:31.990> very<00:06:32.950> possible<00:06:33.430> and<00:06:34.980> but 00:06:35.970 --> 00:06:35.980 align:start position:0% robust defined very possible and but 00:06:35.980 --> 00:06:38.540 align:start position:0% robust defined very possible and but what<00:06:36.190> we<00:06:36.340> are<00:06:36.370> saying<00:06:36.610> really<00:06:36.820> is<00:06:37.000> that<00:06:37.530> we 00:06:38.540 --> 00:06:38.550 align:start position:0% what we are saying really is that we 00:06:38.550 --> 00:06:40.890 align:start position:0% what we are saying really is that we have<00:06:39.550> defined<00:06:39.790> another<00:06:40.180> one<00:06:40.450> based<00:06:40.690> on<00:06:40.840> a 00:06:40.890 --> 00:06:40.900 align:start position:0% have defined another one based on a 00:06:40.900 --> 00:06:43.560 align:start position:0% have defined another one based on a trusted<00:06:41.350> compute<00:06:41.800> that<00:06:42.310> that<00:06:43.030> we<00:06:43.210> are<00:06:43.360> working 00:06:43.560 --> 00:06:43.570 align:start position:0% trusted compute that that we are working 00:06:43.570 --> 00:06:45.360 align:start position:0% trusted compute that that we are working through<00:06:43.930> and<00:06:44.170> and<00:06:44.530> that's<00:06:45.010> what<00:06:45.190> we<00:06:45.310> are 00:06:45.360 --> 00:06:45.370 align:start position:0% through and and that's what we are 00:06:45.370 --> 00:06:47.790 align:start position:0% through and and that's what we are trying<00:06:45.520> to<00:06:45.640> connect<00:06:45.940> here<00:06:46.150> with<00:06:46.360> the<00:06:46.650> rest<00:06:47.650> of 00:06:47.790 --> 00:06:47.800 align:start position:0% trying to connect here with the rest of 00:06:47.800 --> 00:06:55.500 align:start position:0% trying to connect here with the rest of the<00:06:48.690> receptor<00:06:49.690> foundation<00:06:51.630> so<00:06:52.630> like<00:06:54.270> so<00:06:55.270> it's 00:06:55.500 --> 00:06:55.510 align:start position:0% the receptor foundation so like so it's 00:06:55.510 --> 00:06:58.530 align:start position:0% the receptor foundation so like so it's a<00:06:55.570> little<00:06:55.750> bit<00:06:55.990> about<00:06:56.230> a<00:06:57.100> trusted<00:06:58.090> computer 00:06:58.530 --> 00:06:58.540 align:start position:0% a little bit about a trusted computer 00:06:58.540 --> 00:07:03.470 align:start position:0% a little bit about a trusted computer level<00:06:59.290> set<00:07:00.360> you<00:07:01.360> know<00:07:01.480> what<00:07:01.690> what<00:07:02.170> it<00:07:02.290> is 00:07:03.470 --> 00:07:03.480 align:start position:0% level set you know what what it is 00:07:03.480 --> 00:07:06.380 align:start position:0% level set you know what what it is because<00:07:04.480> like<00:07:04.660> at<00:07:04.960> least<00:07:05.140> in<00:07:05.350> my<00:07:05.500> experience 00:07:06.380 --> 00:07:06.390 align:start position:0% because like at least in my experience 00:07:06.390 --> 00:07:09.480 align:start position:0% because like at least in my experience many<00:07:07.390> people<00:07:07.780> have<00:07:08.410> different<00:07:08.620> notions<00:07:09.340> of 00:07:09.480 --> 00:07:09.490 align:start position:0% many people have different notions of 00:07:09.490 --> 00:07:11.370 align:start position:0% many people have different notions of what<00:07:09.760> trusted<00:07:10.120> computers<00:07:10.690> so<00:07:11.080> I<00:07:11.110> will<00:07:11.260> tell 00:07:11.370 --> 00:07:11.380 align:start position:0% what trusted computers so I will tell 00:07:11.380 --> 00:07:13.290 align:start position:0% what trusted computers so I will tell you<00:07:11.470> my<00:07:11.650> definition<00:07:12.520> based<00:07:12.700> on<00:07:12.880> which<00:07:13.060> you 00:07:13.290 --> 00:07:13.300 align:start position:0% you my definition based on which you 00:07:13.300 --> 00:07:15.990 align:start position:0% you my definition based on which you know<00:07:13.720> at<00:07:13.870> least<00:07:13.900> I<00:07:14.470> have<00:07:14.710> been<00:07:14.800> working<00:07:15.130> it<00:07:15.640> is 00:07:15.990 --> 00:07:16.000 align:start position:0% know at least I have been working it is 00:07:16.000 --> 00:07:19.380 align:start position:0% know at least I have been working it is really<00:07:16.450> a<00:07:16.480> place<00:07:17.430> what<00:07:18.430> we<00:07:18.550> say<00:07:18.700> is<00:07:18.760> where<00:07:19.060> you 00:07:19.380 --> 00:07:19.390 align:start position:0% really a place what we say is where you 00:07:19.390 --> 00:07:22.260 align:start position:0% really a place what we say is where you can<00:07:19.600> execute<00:07:20.410> a<00:07:20.680> piece<00:07:20.830> of<00:07:20.980> software<00:07:21.340> without 00:07:22.260 --> 00:07:22.270 align:start position:0% can execute a piece of software without 00:07:22.270 --> 00:07:27.570 align:start position:0% can execute a piece of software without any<00:07:22.600> external<00:07:24.330> influence<00:07:25.470> interference<00:07:26.580> so 00:07:27.570 --> 00:07:27.580 align:start position:0% any external influence interference so 00:07:27.580 --> 00:07:29.640 align:start position:0% any external influence interference so what<00:07:27.730> that<00:07:27.850> means<00:07:28.150> is<00:07:28.300> like<00:07:28.480> you<00:07:29.110> can<00:07:29.290> divide<00:07:29.620> a 00:07:29.640 --> 00:07:29.650 align:start position:0% what that means is like you can divide a 00:07:29.650 --> 00:07:32.280 align:start position:0% what that means is like you can divide a system<00:07:30.220> be<00:07:30.520> it<00:07:30.550> a<00:07:30.760> PC<00:07:31.150> or<00:07:31.300> a<00:07:31.330> server<00:07:31.660> into<00:07:32.140> an 00:07:32.280 --> 00:07:32.290 align:start position:0% system be it a PC or a server into an 00:07:32.290 --> 00:07:35.850 align:start position:0% system be it a PC or a server into an trusted<00:07:33.160> part<00:07:33.370> and<00:07:33.580> an<00:07:33.670> untrusted<00:07:34.180> part<00:07:34.480> so<00:07:35.170> in 00:07:35.850 --> 00:07:35.860 align:start position:0% trusted part and an untrusted part so in 00:07:35.860 --> 00:07:38.370 align:start position:0% trusted part and an untrusted part so in this<00:07:36.040> picture<00:07:36.220> the<00:07:36.790> trusted<00:07:37.750> part<00:07:37.960> is<00:07:38.140> in<00:07:38.260> the 00:07:38.370 --> 00:07:38.380 align:start position:0% this picture the trusted part is in the 00:07:38.380 --> 00:07:41.970 align:start position:0% this picture the trusted part is in the blue<00:07:38.560> and<00:07:39.270> and<00:07:40.270> around<00:07:41.050> it<00:07:41.410> the<00:07:41.590> white<00:07:41.770> is<00:07:41.950> the 00:07:41.970 --> 00:07:41.980 align:start position:0% blue and and around it the white is the 00:07:41.980 --> 00:07:44.400 align:start position:0% blue and and around it the white is the antacid<00:07:42.520> part<00:07:42.760> so<00:07:43.270> what<00:07:43.780> we<00:07:43.930> are<00:07:43.990> saying<00:07:44.170> is 00:07:44.400 --> 00:07:44.410 align:start position:0% antacid part so what we are saying is 00:07:44.410 --> 00:07:46.110 align:start position:0% antacid part so what we are saying is that<00:07:44.500> if<00:07:44.770> there<00:07:44.980> is<00:07:45.100> something<00:07:45.310> executing 00:07:46.110 --> 00:07:46.120 align:start position:0% that if there is something executing 00:07:46.120 --> 00:07:50.610 align:start position:0% that if there is something executing inside<00:07:46.480> that<00:07:46.660> blue<00:07:48.420> it<00:07:49.480> it<00:07:50.050> is<00:07:50.200> integrity 00:07:50.610 --> 00:07:50.620 align:start position:0% inside that blue it it is integrity 00:07:50.620 --> 00:07:52.500 align:start position:0% inside that blue it it is integrity protected<00:07:51.130> means<00:07:51.280> meaning<00:07:51.670> like<00:07:51.910> you<00:07:51.940> know<00:07:52.150> if 00:07:52.500 --> 00:07:52.510 align:start position:0% protected means meaning like you know if 00:07:52.510 --> 00:07:54.750 align:start position:0% protected means meaning like you know if you<00:07:52.720> do<00:07:52.870> one<00:07:53.080> plus<00:07:53.350> one<00:07:53.500> inside<00:07:53.890> that<00:07:53.920> blue<00:07:54.280> you 00:07:54.750 --> 00:07:54.760 align:start position:0% you do one plus one inside that blue you 00:07:54.760 --> 00:07:58.080 align:start position:0% you do one plus one inside that blue you know<00:07:54.910> exactly<00:07:55.360> one<00:07:55.600> plus<00:07:55.840> one<00:07:56.020> happened<00:07:57.090> why 00:07:58.080 --> 00:07:58.090 align:start position:0% know exactly one plus one happened why 00:07:58.090 --> 00:08:00.330 align:start position:0% know exactly one plus one happened why because<00:07:58.480> the<00:07:59.110> underlying<00:07:59.380> system<00:07:59.890> is<00:08:00.070> giving 00:08:00.330 --> 00:08:00.340 align:start position:0% because the underlying system is giving 00:08:00.340 --> 00:08:03.300 align:start position:0% because the underlying system is giving you<00:08:00.460> those<00:08:00.640> guarantees<00:08:01.450> the<00:08:02.200> other<00:08:02.710> aspect<00:08:03.160> of 00:08:03.300 --> 00:08:03.310 align:start position:0% you those guarantees the other aspect of 00:08:03.310 --> 00:08:05.810 align:start position:0% you those guarantees the other aspect of it<00:08:03.430> is<00:08:03.580> like<00:08:03.730> if<00:08:03.880> you<00:08:03.910> have<00:08:04.030> any<00:08:04.360> keys<00:08:04.690> in<00:08:05.470> there 00:08:05.810 --> 00:08:05.820 align:start position:0% it is like if you have any keys in there 00:08:05.820 --> 00:08:08.400 align:start position:0% it is like if you have any keys in there you<00:08:06.820> can<00:08:07.000> pretty<00:08:07.180> much<00:08:07.300> be<00:08:07.570> sure<00:08:07.600> even<00:08:08.170> if<00:08:08.290> you 00:08:08.400 --> 00:08:08.410 align:start position:0% you can pretty much be sure even if you 00:08:08.410 --> 00:08:10.830 align:start position:0% you can pretty much be sure even if you may<00:08:08.560> have<00:08:08.640> malware<00:08:09.640> running<00:08:10.270> in<00:08:10.540> the<00:08:10.660> white 00:08:10.830 --> 00:08:10.840 align:start position:0% may have malware running in the white 00:08:10.840 --> 00:08:14.160 align:start position:0% may have malware running in the white part<00:08:11.170> the<00:08:11.710> antacid<00:08:12.130> part<00:08:12.370> your<00:08:12.810> keys<00:08:13.810> will<00:08:14.050> be 00:08:14.160 --> 00:08:14.170 align:start position:0% part the antacid part your keys will be 00:08:14.170 --> 00:08:17.190 align:start position:0% part the antacid part your keys will be protected<00:08:14.680> and<00:08:14.890> cannot<00:08:15.190> be<00:08:15.400> you<00:08:16.300> know 00:08:17.190 --> 00:08:17.200 align:start position:0% protected and cannot be you know 00:08:17.200 --> 00:08:20.190 align:start position:0% protected and cannot be you know stolen<00:08:17.860> and<00:08:18.730> as<00:08:18.970> a<00:08:19.000> result<00:08:19.450> if<00:08:19.690> there<00:08:19.930> is<00:08:20.020> any 00:08:20.190 --> 00:08:20.200 align:start position:0% stolen and as a result if there is any 00:08:20.200 --> 00:08:22.320 align:start position:0% stolen and as a result if there is any data<00:08:20.470> that<00:08:20.650> is<00:08:21.010> sent<00:08:21.160> encrypted<00:08:21.400> into<00:08:22.150> this 00:08:22.320 --> 00:08:22.330 align:start position:0% data that is sent encrypted into this 00:08:22.330 --> 00:08:26.490 align:start position:0% data that is sent encrypted into this blue<00:08:22.930> box<00:08:23.200> from<00:08:23.530> outside<00:08:23.950> it<00:08:24.760> cannot<00:08:25.120> be<00:08:25.500> you 00:08:26.490 --> 00:08:26.500 align:start position:0% blue box from outside it cannot be you 00:08:26.500 --> 00:08:28.770 align:start position:0% blue box from outside it cannot be you know<00:08:26.620> decrypted<00:08:27.160> outside<00:08:27.550> yes<00:08:28.330> you<00:08:28.450> can<00:08:28.630> do 00:08:28.770 --> 00:08:28.780 align:start position:0% know decrypted outside yes you can do 00:08:28.780 --> 00:08:30.270 align:start position:0% know decrypted outside yes you can do Dass<00:08:28.990> attacks<00:08:29.350> in<00:08:29.500> the<00:08:29.620> sense<00:08:29.800> like<00:08:29.890> you<00:08:30.130> can 00:08:30.270 --> 00:08:30.280 align:start position:0% Dass attacks in the sense like you can 00:08:30.280 --> 00:08:31.710 align:start position:0% Dass attacks in the sense like you can drop<00:08:30.460> the<00:08:30.640> packets<00:08:31.030> and<00:08:31.180> things<00:08:31.360> like<00:08:31.510> that 00:08:31.710 --> 00:08:31.720 align:start position:0% drop the packets and things like that 00:08:31.720 --> 00:08:35.040 align:start position:0% drop the packets and things like that but<00:08:32.140> you<00:08:32.290> cannot<00:08:32.560> fake<00:08:32.890> the<00:08:33.630> fake<00:08:34.630> it<00:08:34.810> into 00:08:35.040 --> 00:08:35.050 align:start position:0% but you cannot fake the fake it into 00:08:35.050 --> 00:08:38.730 align:start position:0% but you cannot fake the fake it into thinking<00:08:35.380> thinking<00:08:35.830> otherwise<00:08:36.070> and<00:08:36.990> lasting 00:08:38.730 --> 00:08:38.740 align:start position:0% thinking thinking otherwise and lasting 00:08:38.740 --> 00:08:43.440 align:start position:0% thinking thinking otherwise and lasting about<00:08:39.100> this<00:08:39.280> container<00:08:40.180> is<00:08:40.270> that<00:08:42.330> you<00:08:43.330> know 00:08:43.440 --> 00:08:43.450 align:start position:0% about this container is that you know 00:08:43.450 --> 00:08:45.990 align:start position:0% about this container is that you know you<00:08:43.510> get<00:08:43.780> an<00:08:43.930> attestation<00:08:44.770> at<00:08:45.400> the<00:08:45.610> end<00:08:45.730> of<00:08:45.850> it 00:08:45.990 --> 00:08:46.000 align:start position:0% you get an attestation at the end of it 00:08:46.000 --> 00:08:48.060 align:start position:0% you get an attestation at the end of it what<00:08:46.360> what<00:08:46.750> has<00:08:46.900> happened<00:08:47.260> what<00:08:47.680> code<00:08:47.920> I 00:08:48.060 --> 00:08:48.070 align:start position:0% what what has happened what code I 00:08:48.070 --> 00:08:52.260 align:start position:0% what what has happened what code I executed<00:08:48.730> what<00:08:50.040> inputs<00:08:51.040> I<00:08:51.190> got<00:08:51.430> and<00:08:51.700> what<00:08:52.150> are 00:08:52.260 --> 00:08:52.270 align:start position:0% executed what inputs I got and what are 00:08:52.270 --> 00:08:55.680 align:start position:0% executed what inputs I got and what are my<00:08:52.420> outputs<00:08:52.870> so<00:08:53.290> you<00:08:53.380> get<00:08:53.530> that<00:08:53.740> kind<00:08:54.250> of<00:08:54.310> a<00:08:54.690> you 00:08:55.680 --> 00:08:55.690 align:start position:0% my outputs so you get that kind of a you 00:08:55.690 --> 00:08:59.610 align:start position:0% my outputs so you get that kind of a you know<00:08:56.190> response<00:08:57.190> so<00:08:58.110> there<00:08:59.110> are<00:08:59.230> various<00:08:59.470> types 00:08:59.610 --> 00:08:59.620 align:start position:0% know response so there are various types 00:08:59.620 --> 00:09:01.650 align:start position:0% know response so there are various types of<00:08:59.830> trusted<00:09:00.190> compute<00:09:00.550> that<00:09:00.700> are<00:09:00.970> comprehended 00:09:01.650 --> 00:09:01.660 align:start position:0% of trusted compute that are comprehended 00:09:01.660 --> 00:09:04.770 align:start position:0% of trusted compute that are comprehended in<00:09:01.900> the<00:09:02.020> spec<00:09:02.290> one<00:09:02.680> is<00:09:02.970> does<00:09:03.970> it<00:09:04.120> computes<00:09:04.480> like 00:09:04.770 --> 00:09:04.780 align:start position:0% in the spec one is does it computes like 00:09:04.780 --> 00:09:09.000 align:start position:0% in the spec one is does it computes like Intel<00:09:05.500> SGX<00:09:05.650> and<00:09:06.330> then<00:09:07.330> there<00:09:07.570> are<00:09:07.600> other<00:09:08.010> ones 00:09:09.000 --> 00:09:09.010 align:start position:0% Intel SGX and then there are other ones 00:09:09.010 --> 00:09:11.640 align:start position:0% Intel SGX and then there are other ones too<00:09:09.370> like<00:09:09.580> software<00:09:10.240> based<00:09:10.480> based<00:09:10.750> on<00:09:10.960> Zeke 00:09:11.640 --> 00:09:11.650 align:start position:0% too like software based based on Zeke 00:09:11.650 --> 00:09:15.090 align:start position:0% too like software based based on Zeke approves<00:09:12.010> MPC<00:09:12.640> so<00:09:13.510> in<00:09:13.750> the<00:09:13.870> spec<00:09:14.140> that<00:09:14.170> I<00:09:14.860> will 00:09:15.090 --> 00:09:15.100 align:start position:0% approves MPC so in the spec that I will 00:09:15.100 --> 00:09:18.210 align:start position:0% approves MPC so in the spec that I will share<00:09:15.340> in<00:09:15.490> a<00:09:15.580> little<00:09:15.850> bit<00:09:16.710> these<00:09:17.710> we<00:09:18.190> are 00:09:18.210 --> 00:09:18.220 align:start position:0% share in a little bit these we are 00:09:18.220 --> 00:09:20.970 align:start position:0% share in a little bit these we are comprehending<00:09:19.060> all<00:09:19.450> of<00:09:19.960> these<00:09:20.140> because<00:09:20.590> we<00:09:20.620> do 00:09:20.970 --> 00:09:20.980 align:start position:0% comprehending all of these because we do 00:09:20.980 --> 00:09:24.180 align:start position:0% comprehending all of these because we do believe<00:09:21.280> that<00:09:21.490> it's<00:09:21.760> not<00:09:22.710> one<00:09:23.710> thing<00:09:23.890> is<00:09:24.010> not<00:09:24.160> a 00:09:24.180 --> 00:09:24.190 align:start position:0% believe that it's not one thing is not a 00:09:24.190 --> 00:09:26.460 align:start position:0% believe that it's not one thing is not a silver<00:09:24.490> bullet<00:09:25.150> to<00:09:25.210> it<00:09:25.450> there<00:09:26.320> will<00:09:26.410> be 00:09:26.460 --> 00:09:26.470 align:start position:0% silver bullet to it there will be 00:09:26.470 --> 00:09:29.010 align:start position:0% silver bullet to it there will be situations<00:09:26.740> wherein<00:09:27.420> you<00:09:28.420> may<00:09:28.570> even<00:09:28.840> have<00:09:28.990> to 00:09:29.010 --> 00:09:29.020 align:start position:0% situations wherein you may even have to 00:09:29.020 --> 00:09:31.110 align:start position:0% situations wherein you may even have to have<00:09:29.380> an<00:09:29.560> heterogenous<00:09:29.950> deployment<00:09:30.760> where<00:09:30.940> in 00:09:31.110 --> 00:09:31.120 align:start position:0% have an heterogenous deployment where in 00:09:31.120 --> 00:09:33.030 align:start position:0% have an heterogenous deployment where in a<00:09:31.210> single<00:09:31.510> deployment<00:09:31.990> he<00:09:32.080> use<00:09:32.290> MPC<00:09:32.860> for 00:09:33.030 --> 00:09:33.040 align:start position:0% a single deployment he use MPC for 00:09:33.040 --> 00:09:33.630 align:start position:0% a single deployment he use MPC for certain<00:09:33.370> things 00:09:33.630 --> 00:09:33.640 align:start position:0% certain things 00:09:33.640 --> 00:09:35.510 align:start position:0% certain things does<00:09:34.090> it<00:09:34.240> compute<00:09:34.570> for<00:09:34.750> something<00:09:35.080> else<00:09:35.260> and 00:09:35.510 --> 00:09:35.520 align:start position:0% does it compute for something else and 00:09:35.520 --> 00:09:38.540 align:start position:0% does it compute for something else and so<00:09:36.520> we<00:09:36.670> are<00:09:36.790> comprehending<00:09:37.330> all<00:09:37.540> those 00:09:38.540 --> 00:09:38.550 align:start position:0% so we are comprehending all those 00:09:38.550 --> 00:09:44.960 align:start position:0% so we are comprehending all those permutation<00:09:39.550> combinations<00:09:41.340> so<00:09:42.340> just<00:09:42.610> quick 00:09:44.960 --> 00:09:44.970 align:start position:0% permutation combinations so just quick 00:09:44.970 --> 00:09:50.100 align:start position:0% permutation combinations so just quick perspective<00:09:45.970> on<00:09:46.360> like<00:09:46.540> you<00:09:46.660> know<00:09:47.580> how<00:09:49.110> about 00:09:50.100 --> 00:09:50.110 align:start position:0% perspective on like you know how about 00:09:50.110 --> 00:09:55.980 align:start position:0% perspective on like you know how about the<00:09:50.230> ecosystem<00:09:50.470> of<00:09:50.950> the<00:09:54.210> about<00:09:55.210> the<00:09:55.330> ecosystem 00:09:55.980 --> 00:09:55.990 align:start position:0% the ecosystem of the about the ecosystem 00:09:55.990 --> 00:09:59.570 align:start position:0% the ecosystem of the about the ecosystem of<00:09:56.440> the<00:09:57.360> around<00:09:58.360> trusted<00:09:58.780> compute<00:09:59.110> so 00:09:59.570 --> 00:09:59.580 align:start position:0% of the around trusted compute so 00:09:59.580 --> 00:10:01.770 align:start position:0% of the around trusted compute so generally<00:10:00.580> the<00:10:00.730> what<00:10:01.030> I<00:10:01.090> want<00:10:01.330> to<00:10:01.420> say<00:10:01.540> here<00:10:01.750> is 00:10:01.770 --> 00:10:01.780 align:start position:0% generally the what I want to say here is 00:10:01.780 --> 00:10:05.400 align:start position:0% generally the what I want to say here is like<00:10:02.100> it's<00:10:03.100> been<00:10:03.250> fairly<00:10:03.400> active<00:10:03.610> a<00:10:04.540> lots<00:10:05.230> of 00:10:05.400 --> 00:10:05.410 align:start position:0% like it's been fairly active a lots of 00:10:05.410 --> 00:10:08.040 align:start position:0% like it's been fairly active a lots of people<00:10:05.680> have<00:10:05.860> been<00:10:06.400> working<00:10:06.910> on<00:10:07.180> in<00:10:07.870> this 00:10:08.040 --> 00:10:08.050 align:start position:0% people have been working on in this 00:10:08.050 --> 00:10:11.460 align:start position:0% people have been working on in this space<00:10:08.320> and<00:10:09.270> several<00:10:10.270> of<00:10:10.420> them<00:10:11.170> you<00:10:11.290> will<00:10:11.410> see 00:10:11.460 --> 00:10:11.470 align:start position:0% space and several of them you will see 00:10:11.470 --> 00:10:16.980 align:start position:0% space and several of them you will see talk<00:10:11.890> about<00:10:12.190> in<00:10:12.990> right<00:10:13.990> after<00:10:14.350> I'm<00:10:15.220> done<00:10:15.960> so<00:10:16.960> a 00:10:16.980 --> 00:10:16.990 align:start position:0% talk about in right after I'm done so a 00:10:16.990 --> 00:10:20.940 align:start position:0% talk about in right after I'm done so a slide<00:10:17.320> on<00:10:18.150> trusted<00:10:19.150> compute<00:10:19.510> so<00:10:20.050> it<00:10:20.740> was<00:10:20.920> a 00:10:20.940 --> 00:10:20.950 align:start position:0% slide on trusted compute so it was a 00:10:20.950 --> 00:10:23.790 align:start position:0% slide on trusted compute so it was a very<00:10:21.220> interesting<00:10:21.430> experience<00:10:22.590> within<00:10:23.590> the 00:10:23.790 --> 00:10:23.800 align:start position:0% very interesting experience within the 00:10:23.800 --> 00:10:28.410 align:start position:0% very interesting experience within the forum<00:10:24.490> going<00:10:25.000> through<00:10:25.210> this<00:10:25.360> because<00:10:26.640> we<00:10:27.640> got 00:10:28.410 --> 00:10:28.420 align:start position:0% forum going through this because we got 00:10:28.420 --> 00:10:30.090 align:start position:0% forum going through this because we got to<00:10:28.540> know<00:10:28.720> several<00:10:29.320> perspectives<00:10:29.590> of<00:10:29.980> the 00:10:30.090 --> 00:10:30.100 align:start position:0% to know several perspectives of the 00:10:30.100 --> 00:10:33.660 align:start position:0% to know several perspectives of the people<00:10:30.460> and<00:10:31.210> the<00:10:32.140> idea<00:10:32.440> of<00:10:32.590> this<00:10:32.740> one<00:10:32.980> was<00:10:33.160> to 00:10:33.660 --> 00:10:33.670 align:start position:0% people and the idea of this one was to 00:10:33.670 --> 00:10:36.150 align:start position:0% people and the idea of this one was to put<00:10:34.210> it<00:10:34.300> out<00:10:34.480> say<00:10:35.350> that<00:10:35.560> trusted<00:10:35.890> completely 00:10:36.150 --> 00:10:36.160 align:start position:0% put it out say that trusted completely 00:10:36.160 --> 00:10:38.970 align:start position:0% put it out say that trusted completely is<00:10:37.020> use<00:10:38.020> it<00:10:38.200> in<00:10:38.320> the<00:10:38.410> sense<00:10:38.590> like<00:10:38.650> you<00:10:38.800> know 00:10:38.970 --> 00:10:38.980 align:start position:0% is use it in the sense like you know 00:10:38.980 --> 00:10:40.440 align:start position:0% is use it in the sense like you know you're<00:10:39.130> off<00:10:39.370> chaining<00:10:39.790> you<00:10:39.940> have<00:10:40.120> the<00:10:40.240> chain 00:10:40.440 --> 00:10:40.450 align:start position:0% you're off chaining you have the chain 00:10:40.450 --> 00:10:42.660 align:start position:0% you're off chaining you have the chain and<00:10:40.690> you<00:10:40.750> are<00:10:41.380> going<00:10:41.680> to<00:10:41.740> off<00:10:41.980> chain<00:10:42.310> and<00:10:42.550> take 00:10:42.660 --> 00:10:42.670 align:start position:0% and you are going to off chain and take 00:10:42.670 --> 00:10:45.810 align:start position:0% and you are going to off chain and take the<00:10:42.820> take<00:10:43.330> computation<00:10:44.320> off<00:10:44.620> the<00:10:44.830> chain<00:10:45.040> be<00:10:45.760> it 00:10:45.810 --> 00:10:45.820 align:start position:0% the take computation off the chain be it 00:10:45.820 --> 00:10:48.750 align:start position:0% the take computation off the chain be it for<00:10:46.060> scalability<00:10:46.510> because<00:10:46.840> the<00:10:47.430> task<00:10:48.430> is 00:10:48.750 --> 00:10:48.760 align:start position:0% for scalability because the task is 00:10:48.760 --> 00:10:51.930 align:start position:0% for scalability because the task is complex<00:10:49.450> or<00:10:49.720> or<00:10:50.500> you<00:10:51.130> have<00:10:51.310> some<00:10:51.460> private<00:10:51.790> data 00:10:51.930 --> 00:10:51.940 align:start position:0% complex or or you have some private data 00:10:51.940 --> 00:10:52.540 align:start position:0% complex or or you have some private data that<00:10:52.210> you<00:10:52.330> can 00:10:52.540 --> 00:10:52.550 align:start position:0% that you can 00:10:52.550 --> 00:10:54.280 align:start position:0% that you can share<00:10:52.790> on<00:10:52.940> the<00:10:53.060> chain<00:10:53.269> and<00:10:53.300> you<00:10:53.600> do<00:10:54.019> all<00:10:54.260> of 00:10:54.280 --> 00:10:54.290 align:start position:0% share on the chain and you do all of 00:10:54.290 --> 00:10:56.730 align:start position:0% share on the chain and you do all of that<00:10:54.410> processing<00:10:54.980> inside<00:10:55.850> trusted<00:10:56.209> computer 00:10:56.730 --> 00:10:56.740 align:start position:0% that processing inside trusted computer 00:10:56.740 --> 00:11:00.759 align:start position:0% that processing inside trusted computer so<00:10:57.880> so<00:10:58.880> we<00:10:59.120> have<00:10:59.300> several<00:10:59.779> objectives<00:11:00.050> in 00:11:00.759 --> 00:11:00.769 align:start position:0% so so we have several objectives in 00:11:00.769 --> 00:11:03.490 align:start position:0% so so we have several objectives in terms<00:11:01.070> of<00:11:01.390> private<00:11:02.390> transactions<00:11:02.930> I<00:11:03.140> gave<00:11:03.410> an 00:11:03.490 --> 00:11:03.500 align:start position:0% terms of private transactions I gave an 00:11:03.500 --> 00:11:06.519 align:start position:0% terms of private transactions I gave an example<00:11:03.950> of<00:11:04.070> that<00:11:04.250> you<00:11:04.430> know<00:11:04.550> for<00:11:04.760> banks<00:11:05.529> you 00:11:06.519 --> 00:11:06.529 align:start position:0% example of that you know for banks you 00:11:06.529 --> 00:11:08.980 align:start position:0% example of that you know for banks you know<00:11:06.680> in<00:11:06.980> a<00:11:07.070> console<00:11:07.399> on<00:11:07.820> a<00:11:07.850> chain<00:11:08.180> two<00:11:08.810> are 00:11:08.980 --> 00:11:08.990 align:start position:0% know in a console on a chain two are 00:11:08.990 --> 00:11:10.840 align:start position:0% know in a console on a chain two are doing<00:11:09.170> transaction<00:11:09.829> rather<00:11:10.190> who<00:11:10.490> should<00:11:10.700> not 00:11:10.840 --> 00:11:10.850 align:start position:0% doing transaction rather who should not 00:11:10.850 --> 00:11:13.840 align:start position:0% doing transaction rather who should not know<00:11:11.029> so<00:11:11.240> that's<00:11:11.420> one<00:11:11.630> example<00:11:12.399> the<00:11:13.399> other<00:11:13.579> one 00:11:13.840 --> 00:11:13.850 align:start position:0% know so that's one example the other one 00:11:13.850 --> 00:11:17.470 align:start position:0% know so that's one example the other one is<00:11:14.029> like<00:11:14.750> you<00:11:14.810> know<00:11:15.399> two<00:11:16.399> banks<00:11:16.820> have<00:11:17.029> data 00:11:17.470 --> 00:11:17.480 align:start position:0% is like you know two banks have data 00:11:17.480 --> 00:11:19.840 align:start position:0% is like you know two banks have data sets<00:11:17.810> that<00:11:18.079> they<00:11:18.380> both<00:11:18.649> want<00:11:18.950> to<00:11:19.010> combine<00:11:19.279> and 00:11:19.840 --> 00:11:19.850 align:start position:0% sets that they both want to combine and 00:11:19.850 --> 00:11:22.150 align:start position:0% sets that they both want to combine and derive<00:11:20.630> some<00:11:20.839> inference<00:11:21.260> from<00:11:21.440> that<00:11:21.529> but<00:11:22.040> they 00:11:22.150 --> 00:11:22.160 align:start position:0% derive some inference from that but they 00:11:22.160 --> 00:11:25.840 align:start position:0% derive some inference from that but they don't<00:11:22.339> wanna<00:11:22.519> give<00:11:23.480> up<00:11:23.600> the<00:11:23.779> control<00:11:24.140> or<00:11:24.850> early 00:11:25.840 --> 00:11:25.850 align:start position:0% don't wanna give up the control or early 00:11:25.850 --> 00:11:28.720 align:start position:0% don't wanna give up the control or early or<00:11:26.350> you<00:11:27.350> know<00:11:27.470> keep<00:11:27.740> the<00:11:27.860> confidentiality<00:11:28.459> of 00:11:28.720 --> 00:11:28.730 align:start position:0% or you know keep the confidentiality of 00:11:28.730 --> 00:11:31.930 align:start position:0% or you know keep the confidentiality of the<00:11:29.029> data<00:11:29.209> that<00:11:29.839> they<00:11:29.990> have<00:11:30.170> so<00:11:30.649> you<00:11:30.709> could<00:11:31.220> you 00:11:31.930 --> 00:11:31.940 align:start position:0% the data that they have so you could you 00:11:31.940 --> 00:11:34.000 align:start position:0% the data that they have so you could you know<00:11:32.089> use<00:11:32.839> trusted<00:11:33.410> computer<00:11:33.769> in<00:11:33.860> that 00:11:34.000 --> 00:11:34.010 align:start position:0% know use trusted computer in that 00:11:34.010 --> 00:11:37.720 align:start position:0% know use trusted computer in that setting<00:11:34.430> the<00:11:35.269> other<00:11:36.110> so<00:11:37.040> these<00:11:37.190> are<00:11:37.399> the<00:11:37.519> two 00:11:37.720 --> 00:11:37.730 align:start position:0% setting the other so these are the two 00:11:37.730 --> 00:11:40.329 align:start position:0% setting the other so these are the two that<00:11:37.940> we<00:11:38.209> have<00:11:38.450> some<00:11:38.959> extent<00:11:39.350> comprehended<00:11:40.040> in 00:11:40.329 --> 00:11:40.339 align:start position:0% that we have some extent comprehended in 00:11:40.339 --> 00:11:42.880 align:start position:0% that we have some extent comprehended in the<00:11:40.550> current<00:11:40.850> version<00:11:41.029> the<00:11:41.899> work<00:11:42.380> that<00:11:42.680> we 00:11:42.880 --> 00:11:42.890 align:start position:0% the current version the work that we 00:11:42.890 --> 00:11:46.889 align:start position:0% the current version the work that we have<00:11:43.160> to<00:11:43.399> do<00:11:43.579> is<00:11:43.820> around<00:11:44.680> the<00:11:45.680> foundation<00:11:46.070> is 00:11:46.889 --> 00:11:46.899 align:start position:0% have to do is around the foundation is 00:11:46.899 --> 00:11:49.120 align:start position:0% have to do is around the foundation is you<00:11:47.899> know<00:11:48.050> will<00:11:48.230> support<00:11:48.529> this<00:11:48.649> attested 00:11:49.120 --> 00:11:49.130 align:start position:0% you know will support this attested 00:11:49.130 --> 00:11:50.980 align:start position:0% you know will support this attested Oracle's<00:11:49.640> but<00:11:49.880> we<00:11:50.060> have<00:11:50.240> to<00:11:50.420> do<00:11:50.540> that<00:11:50.750> and 00:11:50.980 --> 00:11:50.990 align:start position:0% Oracle's but we have to do that and 00:11:50.990 --> 00:11:52.630 align:start position:0% Oracle's but we have to do that and that's<00:11:51.170> in<00:11:51.440> the<00:11:51.529> upcoming<00:11:51.829> versions<00:11:52.339> we<00:11:52.490> will 00:11:52.630 --> 00:11:52.640 align:start position:0% that's in the upcoming versions we will 00:11:52.640 --> 00:11:56.889 align:start position:0% that's in the upcoming versions we will address<00:11:53.180> that<00:11:53.589> we<00:11:54.589> are<00:11:55.130> also<00:11:55.459> looked<00:11:56.300> at 00:11:56.889 --> 00:11:56.899 align:start position:0% address that we are also looked at 00:11:56.899 --> 00:12:01.329 align:start position:0% address that we are also looked at identities<00:11:57.649> and<00:11:59.170> besides<00:12:00.170> we<00:12:00.560> had<00:12:00.740> a<00:12:01.070> good 00:12:01.329 --> 00:12:01.339 align:start position:0% identities and besides we had a good 00:12:01.339 --> 00:12:03.449 align:start position:0% identities and besides we had a good conversation<00:12:01.550> around<00:12:02.000> should<00:12:02.329> it<00:12:02.450> be 00:12:03.449 --> 00:12:03.459 align:start position:0% conversation around should it be 00:12:03.459 --> 00:12:06.610 align:start position:0% conversation around should it be identities<00:12:04.459> based<00:12:04.640> on<00:12:05.079> just<00:12:06.079> the<00:12:06.230> etherium 00:12:06.610 --> 00:12:06.620 align:start position:0% identities based on just the etherium 00:12:06.620 --> 00:12:08.380 align:start position:0% identities based on just the etherium addresses<00:12:07.040> or<00:12:07.279> should<00:12:07.490> it<00:12:07.520> be<00:12:07.640> decentralized 00:12:08.380 --> 00:12:08.390 align:start position:0% addresses or should it be decentralized 00:12:08.390 --> 00:12:10.960 align:start position:0% addresses or should it be decentralized identities<00:12:08.930> as<00:12:09.140> defined<00:12:09.620> by<00:12:09.970> recently 00:12:10.960 --> 00:12:10.970 align:start position:0% identities as defined by recently 00:12:10.970 --> 00:12:14.019 align:start position:0% identities as defined by recently identity<00:12:11.510> foundation<00:12:12.020> so<00:12:12.560> generally<00:12:13.000> we<00:12:14.000> are 00:12:14.019 --> 00:12:14.029 align:start position:0% identity foundation so generally we are 00:12:14.029 --> 00:12:16.930 align:start position:0% identity foundation so generally we are going<00:12:14.390> to<00:12:14.510> explore<00:12:15.170> that<00:12:15.410> we<00:12:15.770> are<00:12:16.339> supporting 00:12:16.930 --> 00:12:16.940 align:start position:0% going to explore that we are supporting 00:12:16.940 --> 00:12:20.139 align:start position:0% going to explore that we are supporting what<00:12:17.270> the<00:12:17.899> ID<00:12:18.079> work<00:12:18.470> is<00:12:18.649> being<00:12:18.860> done<00:12:18.920> in<00:12:19.910> the 00:12:20.139 --> 00:12:20.149 align:start position:0% what the ID work is being done in the 00:12:20.149 --> 00:12:23.889 align:start position:0% what the ID work is being done in the industry<00:12:20.540> so<00:12:20.959> more<00:12:21.220> you<00:12:22.220> know<00:12:22.810> discussions<00:12:23.810> on 00:12:23.889 --> 00:12:23.899 align:start position:0% industry so more you know discussions on 00:12:23.899 --> 00:12:26.079 align:start position:0% industry so more you know discussions on that<00:12:23.930> will<00:12:24.230> be<00:12:24.380> upcoming<00:12:24.579> and<00:12:25.579> then<00:12:25.820> the<00:12:25.910> other 00:12:26.079 --> 00:12:26.089 align:start position:0% that will be upcoming and then the other 00:12:26.089 --> 00:12:30.069 align:start position:0% that will be upcoming and then the other one<00:12:26.329> is<00:12:26.480> this<00:12:27.790> this<00:12:28.790> version<00:12:29.029> if<00:12:29.630> you<00:12:29.779> look<00:12:29.959> at 00:12:30.069 --> 00:12:30.079 align:start position:0% one is this this version if you look at 00:12:30.079 --> 00:12:32.110 align:start position:0% one is this this version if you look at this<00:12:30.230> back<00:12:30.529> you<00:12:30.770> can<00:12:30.980> see<00:12:31.430> that<00:12:31.459> some<00:12:31.880> of<00:12:31.910> the 00:12:32.110 --> 00:12:32.120 align:start position:0% this back you can see that some of the 00:12:32.120 --> 00:12:34.329 align:start position:0% this back you can see that some of the api's<00:12:32.510> are<00:12:32.839> not<00:12:33.110> something<00:12:33.860> that<00:12:33.980> you<00:12:34.160> would 00:12:34.329 --> 00:12:34.339 align:start position:0% api's are not something that you would 00:12:34.339 --> 00:12:36.970 align:start position:0% api's are not something that you would use<00:12:34.579> them<00:12:35.029> on<00:12:35.260> publicly<00:12:36.260> theorem<00:12:36.649> because 00:12:36.970 --> 00:12:36.980 align:start position:0% use them on publicly theorem because 00:12:36.980 --> 00:12:40.960 align:start position:0% use them on publicly theorem because they<00:12:37.370> do<00:12:37.430> consume<00:12:38.209> high<00:12:38.870> gas<00:12:39.170> and<00:12:39.470> that's<00:12:40.190> one 00:12:40.960 --> 00:12:40.970 align:start position:0% they do consume high gas and that's one 00:12:40.970 --> 00:12:44.439 align:start position:0% they do consume high gas and that's one of<00:12:41.000> our<00:12:41.620> upcoming<00:12:42.620> objectives<00:12:43.430> in<00:12:43.610> the<00:12:43.760> next 00:12:44.439 --> 00:12:44.449 align:start position:0% of our upcoming objectives in the next 00:12:44.449 --> 00:12:46.329 align:start position:0% of our upcoming objectives in the next version<00:12:44.779> is<00:12:44.899> to<00:12:45.140> actually<00:12:45.320> go<00:12:45.890> through<00:12:46.130> those 00:12:46.329 --> 00:12:46.339 align:start position:0% version is to actually go through those 00:12:46.339 --> 00:12:50.350 align:start position:0% version is to actually go through those and<00:12:46.990> clean<00:12:47.990> up<00:12:48.199> and<00:12:48.550> have<00:12:49.550> them<00:12:49.790> aligned<00:12:50.120> with 00:12:50.350 --> 00:12:50.360 align:start position:0% and clean up and have them aligned with 00:12:50.360 --> 00:12:52.569 align:start position:0% and clean up and have them aligned with what<00:12:50.540> is<00:12:50.660> expected<00:12:51.199> on<00:12:51.320> the<00:12:51.350> public<00:12:52.220> aetherium 00:12:52.569 --> 00:12:52.579 align:start position:0% what is expected on the public aetherium 00:12:52.579 --> 00:12:56.769 align:start position:0% what is expected on the public aetherium side<00:12:53.019> and<00:12:54.019> the<00:12:54.709> other<00:12:54.980> side<00:12:55.100> of<00:12:55.430> the<00:12:55.610> api's<00:12:56.449> is 00:12:56.769 --> 00:12:56.779 align:start position:0% side and the other side of the api's is 00:12:56.779 --> 00:13:01.000 align:start position:0% side and the other side of the api's is we<00:12:57.649> are<00:12:58.449> making<00:12:59.449> sure<00:12:59.810> that<00:13:00.170> it<00:13:00.800> doesn't 00:13:01.000 --> 00:13:01.010 align:start position:0% we are making sure that it doesn't 00:13:01.010 --> 00:13:05.050 align:start position:0% we are making sure that it doesn't design<00:13:01.430> anyone<00:13:01.880> out<00:13:03.160> beatbeat<00:13:04.160> different 00:13:05.050 --> 00:13:05.060 align:start position:0% design anyone out beatbeat different 00:13:05.060 --> 00:13:06.910 align:start position:0% design anyone out beatbeat different deployment<00:13:05.420> ations<00:13:05.660> of<00:13:05.779> classic 00:13:06.910 --> 00:13:06.920 align:start position:0% deployment ations of classic 00:13:06.920 --> 00:13:09.130 align:start position:0% deployment ations of classic you<00:13:07.100> know<00:13:07.220> te<00:13:07.760> or<00:13:08.180> different<00:13:08.510> implementations 00:13:09.130 --> 00:13:09.140 align:start position:0% you know te or different implementations 00:13:09.140 --> 00:13:14.290 align:start position:0% you know te or different implementations of<00:13:09.790> ZK<00:13:10.790> so<00:13:11.330> we're<00:13:11.540> trying<00:13:12.260> to<00:13:12.470> do<00:13:13.300> that's 00:13:14.290 --> 00:13:14.300 align:start position:0% of ZK so we're trying to do that's 00:13:14.300 --> 00:13:16.600 align:start position:0% of ZK so we're trying to do that's definitely<00:13:14.930> one<00:13:15.710> of<00:13:15.740> our<00:13:15.950> objectives<00:13:16.100> and 00:13:16.600 --> 00:13:16.610 align:start position:0% definitely one of our objectives and 00:13:16.610 --> 00:13:21.120 align:start position:0% definitely one of our objectives and also<00:13:17.030> to<00:13:17.330> comprehend<00:13:17.900> all<00:13:18.650> the<00:13:18.830> three<00:13:19.040> forms 00:13:21.120 --> 00:13:21.130 align:start position:0% also to comprehend all the three forms 00:13:21.130 --> 00:13:25.210 align:start position:0% also to comprehend all the three forms so<00:13:22.130> so<00:13:23.030> this<00:13:23.240> spec<00:13:23.540> was<00:13:23.840> actually<00:13:24.410> you<00:13:25.190> know 00:13:25.210 --> 00:13:25.220 align:start position:0% so so this spec was actually you know 00:13:25.220 --> 00:13:27.100 align:start position:0% so so this spec was actually you know early<00:13:25.850> version<00:13:26.150> point<00:13:26.360> five<00:13:26.630> version<00:13:26.930> of<00:13:26.990> the 00:13:27.100 --> 00:13:27.110 align:start position:0% early version point five version of the 00:13:27.110 --> 00:13:33.670 align:start position:0% early version point five version of the spec<00:13:27.320> was<00:13:28.360> announced<00:13:29.360> yesterday<00:13:30.550> and<00:13:32.140> we<00:13:33.140> do 00:13:33.670 --> 00:13:33.680 align:start position:0% spec was announced yesterday and we do 00:13:33.680 --> 00:13:36.250 align:start position:0% spec was announced yesterday and we do you<00:13:34.460> know<00:13:34.580> our<00:13:34.790> hope<00:13:35.390> is<00:13:35.570> that<00:13:35.600> you<00:13:35.900> guys<00:13:36.080> will 00:13:36.250 --> 00:13:36.260 align:start position:0% you know our hope is that you guys will 00:13:36.260 --> 00:13:38.350 align:start position:0% you know our hope is that you guys will go<00:13:36.710> check<00:13:36.890> it<00:13:37.070> out<00:13:37.250> from<00:13:37.430> your<00:13:37.550> perspective 00:13:38.350 --> 00:13:38.360 align:start position:0% go check it out from your perspective 00:13:38.360 --> 00:13:44.260 align:start position:0% go check it out from your perspective and<00:13:39.370> provide<00:13:40.370> feedback<00:13:41.020> into<00:13:42.020> the<00:13:42.140> spec<00:13:43.270> our 00:13:44.260 --> 00:13:44.270 align:start position:0% and provide feedback into the spec our 00:13:44.270 --> 00:13:48.400 align:start position:0% and provide feedback into the spec our our<00:13:45.200> desire<00:13:45.980> or<00:13:46.370> our<00:13:46.580> object<00:13:47.060> to<00:13:47.150> is<00:13:47.410> the 00:13:48.400 --> 00:13:48.410 align:start position:0% our desire or our object to is the 00:13:48.410 --> 00:13:51.340 align:start position:0% our desire or our object to is the version<00:13:48.620> point<00:13:49.100> by<00:13:49.280> that<00:13:49.310> we<00:13:50.170> announced<00:13:51.170> like 00:13:51.340 --> 00:13:51.350 align:start position:0% version point by that we announced like 00:13:51.350 --> 00:13:54.390 align:start position:0% version point by that we announced like this<00:13:51.680> week<00:13:51.860> we<00:13:52.670> will<00:13:52.820> take<00:13:53.030> it<00:13:53.180> to<00:13:53.210> one<00:13:53.510> dot<00:13:53.720> oh 00:13:54.390 --> 00:13:54.400 align:start position:0% this week we will take it to one dot oh 00:13:54.400 --> 00:13:58.450 align:start position:0% this week we will take it to one dot oh by<00:13:55.400> you<00:13:56.180> know<00:13:56.330> at<00:13:56.660> q2<00:13:57.140> of<00:13:57.320> next<00:13:57.980> year<00:13:58.130> when 00:13:58.450 --> 00:13:58.460 align:start position:0% by you know at q2 of next year when 00:13:58.460 --> 00:14:01.450 align:start position:0% by you know at q2 of next year when there<00:13:58.700> when<00:13:59.150> there<00:13:59.330> will<00:13:59.390> be<00:13:59.480> next<00:14:00.310> update<00:14:01.310> of 00:14:01.450 --> 00:14:01.460 align:start position:0% there when there will be next update of 00:14:01.460 --> 00:14:04.570 align:start position:0% there when there will be next update of the<00:14:01.580> spec<00:14:02.020> as<00:14:03.020> well<00:14:03.260> as<00:14:03.380> work<00:14:03.980> on<00:14:04.160> some<00:14:04.490> other 00:14:04.570 --> 00:14:04.580 align:start position:0% the spec as well as work on some other 00:14:04.580 --> 00:14:07.090 align:start position:0% the spec as well as work on some other new<00:14:05.150> features<00:14:05.540> that<00:14:05.780> we<00:14:06.050> have<00:14:06.080> you<00:14:06.710> know<00:14:06.830> not 00:14:07.090 --> 00:14:07.100 align:start position:0% new features that we have you know not 00:14:07.100 --> 00:14:13.090 align:start position:0% new features that we have you know not really<00:14:07.490> had<00:14:08.030> time<00:14:08.240> to<00:14:08.770> explore<00:14:10.390> so<00:14:11.390> so<00:14:12.100> that's 00:14:13.090 --> 00:14:13.100 align:start position:0% really had time to explore so so that's 00:14:13.100 --> 00:14:15.700 align:start position:0% really had time to explore so so that's what<00:14:13.370> I<00:14:13.400> was<00:14:13.640> trying<00:14:14.240> to<00:14:14.410> hopefully<00:14:15.410> give<00:14:15.590> you 00:14:15.700 --> 00:14:15.710 align:start position:0% what I was trying to hopefully give you 00:14:15.710 --> 00:14:18.820 align:start position:0% what I was trying to hopefully give you a<00:14:15.740> little<00:14:15.950> bit<00:14:16.450> insight<00:14:17.450> into<00:14:17.690> what<00:14:18.110> has<00:14:18.320> what 00:14:18.820 --> 00:14:18.830 align:start position:0% a little bit insight into what has what 00:14:18.830 --> 00:14:22.900 align:start position:0% a little bit insight into what has what we<00:14:18.980> have<00:14:19.100> been<00:14:19.220> doing<00:14:19.310> at<00:14:19.490> EA<00:14:19.730> and<00:14:21.010> now<00:14:22.010> you 00:14:22.900 --> 00:14:22.910 align:start position:0% we have been doing at EA and now you 00:14:22.910 --> 00:14:25.870 align:start position:0% we have been doing at EA and now you know<00:14:23.170> we<00:14:24.170> will<00:14:24.380> have<00:14:24.410> like<00:14:24.890> five<00:14:25.640> more 00:14:25.870 --> 00:14:25.880 align:start position:0% know we will have like five more 00:14:25.880 --> 00:14:29.170 align:start position:0% know we will have like five more presentations<00:14:26.630> to<00:14:27.350> talk<00:14:28.310> from<00:14:28.640> a<00:14:28.880> perspective 00:14:29.170 --> 00:14:29.180 align:start position:0% presentations to talk from a perspective 00:14:29.180 --> 00:14:31.180 align:start position:0% presentations to talk from a perspective various<00:14:29.810> EA<00:14:30.050> members<00:14:30.500> like<00:14:30.770> you<00:14:30.890> know<00:14:31.010> how 00:14:31.180 --> 00:14:31.190 align:start position:0% various EA members like you know how 00:14:31.190 --> 00:14:33.130 align:start position:0% various EA members like you know how they<00:14:31.370> have<00:14:31.580> been<00:14:31.670> using<00:14:31.940> trusted<00:14:32.480> compute<00:14:32.930> and 00:14:33.130 --> 00:14:33.140 align:start position:0% they have been using trusted compute and 00:14:33.140 --> 00:14:35.410 align:start position:0% they have been using trusted compute and and<00:14:34.130> things<00:14:34.370> like<00:14:34.550> that<00:14:34.730> or<00:14:34.850> how<00:14:35.000> they<00:14:35.180> plan<00:14:35.390> to 00:14:35.410 --> 00:14:35.420 align:start position:0% and things like that or how they plan to 00:14:35.420 --> 00:14:40.030 align:start position:0% and things like that or how they plan to use<00:14:35.600> it<00:14:35.930> and<00:14:36.080> then<00:14:36.590> finally<00:14:36.980> we<00:14:37.520> will<00:14:38.980> you<00:14:39.980> know 00:14:40.030 --> 00:14:40.040 align:start position:0% use it and then finally we will you know 00:14:40.040 --> 00:14:43.360 align:start position:0% use it and then finally we will you know also<00:14:40.370> have<00:14:40.610> a<00:14:40.670> panel<00:14:41.030> and<00:14:41.660> see<00:14:42.350> and<00:14:42.890> hopefully 00:14:43.360 --> 00:14:43.370 align:start position:0% also have a panel and see and hopefully 00:14:43.370 --> 00:14:45.850 align:start position:0% also have a panel and see and hopefully make<00:14:43.550> it<00:14:43.580> more<00:14:43.930> you<00:14:44.930> know<00:14:44.960> bi-directional<00:14:45.800> at 00:14:45.850 --> 00:14:45.860 align:start position:0% make it more you know bi-directional at 00:14:45.860 --> 00:14:51.400 align:start position:0% make it more you know bi-directional at that<00:14:46.040> point<00:14:46.870> so<00:14:47.870> at<00:14:48.170> this<00:14:48.410> point<00:14:48.710> I<00:14:49.670> will<00:14:50.410> I 00:14:51.400 --> 00:14:51.410 align:start position:0% that point so at this point I will I 00:14:51.410 --> 00:14:57.130 align:start position:0% that point so at this point I will I think<00:14:52.280> Nicholas<00:14:54.760> so<00:14:55.760> Nick<00:14:56.630> Rebecca<00:14:56.990> comes 00:14:57.130 --> 00:14:57.140 align:start position:0% think Nicholas so Nick Rebecca comes 00:14:57.140 --> 00:15:00.070 align:start position:0% think Nicholas so Nick Rebecca comes with<00:14:57.380> you<00:14:57.560> and<00:14:57.830> coughin<00:14:58.160> the<00:14:58.310> Fletcher<00:14:59.050> so<00:15:00.050> I 00:15:00.070 --> 00:15:00.080 align:start position:0% with you and coughin the Fletcher so I 00:15:00.080 --> 00:15:02.080 align:start position:0% with you and coughin the Fletcher so I can<00:15:00.530> I<00:15:00.860> will<00:15:01.040> tell<00:15:01.220> you<00:15:01.340> a<00:15:01.370> bit<00:15:01.610> how<00:15:01.820> we<00:15:01.970> have 00:15:02.080 --> 00:15:02.090 align:start position:0% can I will tell you a bit how we have 00:15:02.090 --> 00:15:04.150 align:start position:0% can I will tell you a bit how we have been<00:15:02.240> using<00:15:02.450> trusted<00:15:03.230> computing<00:15:03.590> during<00:15:03.950> the 00:15:04.150 --> 00:15:04.160 align:start position:0% been using trusted computing during the 00:15:04.160 --> 00:15:06.460 align:start position:0% been using trusted computing during the past<00:15:04.370> year<00:15:04.580> so<00:15:05.090> we<00:15:05.330> have<00:15:05.450> a<00:15:05.480> use<00:15:05.750> case<00:15:05.990> which<00:15:06.260> is 00:15:06.460 --> 00:15:06.470 align:start position:0% past year so we have a use case which is 00:15:06.470 --> 00:15:08.590 align:start position:0% past year so we have a use case which is a<00:15:06.500> bit<00:15:06.770> original<00:15:07.370> or<00:15:07.640> untested<00:15:07.970> compute 00:15:08.590 --> 00:15:08.600 align:start position:0% a bit original or untested compute 00:15:08.600 --> 00:15:11.530 align:start position:0% a bit original or untested compute because<00:15:09.070> lecture<00:15:10.070> has<00:15:10.220> been<00:15:10.250> mostly<00:15:11.210> known<00:15:11.510> as 00:15:11.530 --> 00:15:11.540 align:start position:0% because lecture has been mostly known as 00:15:11.540 --> 00:15:14.050 align:start position:0% because lecture has been mostly known as a<00:15:11.780> hardware<00:15:12.140> wallet<00:15:12.470> provider<00:15:12.830> so<00:15:13.100> far<00:15:13.340> but<00:15:13.880> we 00:15:14.050 --> 00:15:14.060 align:start position:0% a hardware wallet provider so far but we 00:15:14.060 --> 00:15:16.480 align:start position:0% a hardware wallet provider so far but we realized<00:15:14.450> that<00:15:14.690> the<00:15:14.840> main<00:15:15.050> problem<00:15:15.920> the<00:15:16.340> main 00:15:16.480 --> 00:15:16.490 align:start position:0% realized that the main problem the main 00:15:16.490 --> 00:15:18.430 align:start position:0% realized that the main problem the main issue<00:15:16.760> when<00:15:17.270> people<00:15:17.690> wanted<00:15:18.080> to<00:15:18.230> use<00:15:18.410> a 00:15:18.430 --> 00:15:18.440 align:start position:0% issue when people wanted to use a 00:15:18.440 --> 00:15:19.190 align:start position:0% issue when people wanted to use a hardware 00:15:19.190 --> 00:15:19.200 align:start position:0% hardware 00:15:19.200 --> 00:15:21.860 align:start position:0% hardware is<00:15:19.590> that<00:15:20.130> well<00:15:20.580> they<00:15:20.850> have<00:15:20.970> to<00:15:21.180> buy<00:15:21.630> its 00:15:21.860 --> 00:15:21.870 align:start position:0% is that well they have to buy its 00:15:21.870 --> 00:15:24.080 align:start position:0% is that well they have to buy its inaudible<00:15:22.110> wallet<00:15:22.560> so<00:15:22.860> trusted<00:15:23.370> computer<00:15:23.850> in 00:15:24.080 --> 00:15:24.090 align:start position:0% inaudible wallet so trusted computer in 00:15:24.090 --> 00:15:26.930 align:start position:0% inaudible wallet so trusted computer in our<00:15:24.710> computer<00:15:25.710> for<00:15:25.830> us<00:15:25.980> is<00:15:26.160> a<00:15:26.190> way<00:15:26.280> to<00:15:26.490> think 00:15:26.930 --> 00:15:26.940 align:start position:0% our computer for us is a way to think 00:15:26.940 --> 00:15:29.780 align:start position:0% our computer for us is a way to think about<00:15:27.240> how<00:15:27.780> we<00:15:27.840> can<00:15:28.230> basically<00:15:28.890> change<00:15:29.490> that 00:15:29.780 --> 00:15:29.790 align:start position:0% about how we can basically change that 00:15:29.790 --> 00:15:31.820 align:start position:0% about how we can basically change that and<00:15:30.030> if<00:15:30.390> there<00:15:30.840> is<00:15:30.960> a<00:15:30.990> way<00:15:31.230> for<00:15:31.470> people<00:15:31.500> to 00:15:31.820 --> 00:15:31.830 align:start position:0% and if there is a way for people to 00:15:31.830 --> 00:15:33.710 align:start position:0% and if there is a way for people to don't<00:15:32.190> know<00:15:32.340> the<00:15:32.400> hardware<00:15:32.730> wallet<00:15:33.180> on<00:15:33.390> their 00:15:33.710 --> 00:15:33.720 align:start position:0% don't know the hardware wallet on their 00:15:33.720 --> 00:15:36.740 align:start position:0% don't know the hardware wallet on their existing<00:15:34.140> computers<00:15:34.670> so<00:15:35.670> we<00:15:35.880> spent<00:15:36.240> one<00:15:36.720> year 00:15:36.740 --> 00:15:36.750 align:start position:0% existing computers so we spent one year 00:15:36.750 --> 00:15:39.080 align:start position:0% existing computers so we spent one year thinking<00:15:36.960> about<00:15:37.800> the<00:15:37.980> different<00:15:38.430> security 00:15:39.080 --> 00:15:39.090 align:start position:0% thinking about the different security 00:15:39.090 --> 00:15:41.090 align:start position:0% thinking about the different security threat<00:15:39.360> that<00:15:39.600> could<00:15:39.930> that<00:15:40.710> we<00:15:40.830> could<00:15:40.980> have 00:15:41.090 --> 00:15:41.100 align:start position:0% threat that could that we could have 00:15:41.100 --> 00:15:43.100 align:start position:0% threat that could that we could have entrusted<00:15:41.520> computer<00:15:42.090> and<00:15:42.210> see<00:15:42.450> how<00:15:42.750> we<00:15:42.810> could 00:15:43.100 --> 00:15:43.110 align:start position:0% entrusted computer and see how we could 00:15:43.110 --> 00:15:45.080 align:start position:0% entrusted computer and see how we could visualize<00:15:43.680> as<00:15:43.920> much<00:15:44.130> as<00:15:44.280> possible<00:15:44.430> hollow 00:15:45.080 --> 00:15:45.090 align:start position:0% visualize as much as possible hollow 00:15:45.090 --> 00:15:47.720 align:start position:0% visualize as much as possible hollow wallet<00:15:45.390> so<00:15:46.080> if<00:15:46.410> we<00:15:46.560> look<00:15:46.740> at<00:15:46.860> water<00:15:47.160> Hardware 00:15:47.720 --> 00:15:47.730 align:start position:0% wallet so if we look at water Hardware 00:15:47.730 --> 00:15:49.580 align:start position:0% wallet so if we look at water Hardware wallet<00:15:48.000> is<00:15:48.150> doing<00:15:48.420> today<00:15:48.600> I<00:15:48.780> will<00:15:48.990> see<00:15:49.260> that<00:15:49.290> we 00:15:49.580 --> 00:15:49.590 align:start position:0% wallet is doing today I will see that we 00:15:49.590 --> 00:15:52.520 align:start position:0% wallet is doing today I will see that we have<00:15:49.700> four<00:15:50.700> different<00:15:50.730> properties<00:15:51.540> so<00:15:52.110> how<00:15:52.470> do 00:15:52.520 --> 00:15:52.530 align:start position:0% have four different properties so how do 00:15:52.530 --> 00:15:54.260 align:start position:0% have four different properties so how do our<00:15:52.650> wallets<00:15:53.010> should<00:15:53.430> be<00:15:53.610> able<00:15:53.700> to<00:15:53.910> protect 00:15:54.260 --> 00:15:54.270 align:start position:0% our wallets should be able to protect 00:15:54.270 --> 00:15:56.150 align:start position:0% our wallets should be able to protect first<00:15:54.840> it<00:15:55.050> should<00:15:55.200> be<00:15:55.290> able<00:15:55.380> to<00:15:55.500> protect<00:15:55.740> keys 00:15:56.150 --> 00:15:56.160 align:start position:0% first it should be able to protect keys 00:15:56.160 --> 00:15:58.640 align:start position:0% first it should be able to protect keys so<00:15:56.490> when<00:15:56.700> we<00:15:56.850> do<00:15:57.000> an<00:15:57.120> operation<00:15:57.420> and<00:15:57.720> key<00:15:57.960> an 00:15:58.640 --> 00:15:58.650 align:start position:0% so when we do an operation and key an 00:15:58.650 --> 00:16:00.350 align:start position:0% so when we do an operation and key an attacker<00:15:59.010> shouldn't<00:15:59.550> be<00:15:59.610> able<00:15:59.700> to<00:15:59.880> access<00:16:00.090> the 00:16:00.350 --> 00:16:00.360 align:start position:0% attacker shouldn't be able to access the 00:16:00.360 --> 00:16:02.390 align:start position:0% attacker shouldn't be able to access the keys<00:16:00.600> so<00:16:00.840> that's<00:16:01.050> one<00:16:01.290> of<00:16:01.410> the<00:16:01.560> most<00:16:01.980> important 00:16:02.390 --> 00:16:02.400 align:start position:0% keys so that's one of the most important 00:16:02.400 --> 00:16:05.000 align:start position:0% keys so that's one of the most important properties<00:16:02.850> one<00:16:03.750> difference<00:16:04.230> here<00:16:04.320> is<00:16:04.740> that<00:16:04.800> a 00:16:05.000 --> 00:16:05.010 align:start position:0% properties one difference here is that a 00:16:05.010 --> 00:16:06.740 align:start position:0% properties one difference here is that a hardware<00:16:05.460> wallet<00:16:05.760> should<00:16:06.210> be<00:16:06.450> able<00:16:06.570> to 00:16:06.740 --> 00:16:06.750 align:start position:0% hardware wallet should be able to 00:16:06.750 --> 00:16:08.450 align:start position:0% hardware wallet should be able to protect<00:16:07.080> against<00:16:07.620> a<00:16:07.800> physical<00:16:08.190> attacker 00:16:08.450 --> 00:16:08.460 align:start position:0% protect against a physical attacker 00:16:08.460 --> 00:16:11.360 align:start position:0% protect against a physical attacker while<00:16:09.300> we<00:16:10.110> cannot<00:16:10.410> really<00:16:10.740> guarantee<00:16:11.010> that 00:16:11.360 --> 00:16:11.370 align:start position:0% while we cannot really guarantee that 00:16:11.370 --> 00:16:12.800 align:start position:0% while we cannot really guarantee that with<00:16:11.640> trusted<00:16:12.000> computer<00:16:12.420> so<00:16:12.540> that's 00:16:12.800 --> 00:16:12.810 align:start position:0% with trusted computer so that's 00:16:12.810 --> 00:16:14.960 align:start position:0% with trusted computer so that's something<00:16:13.050> we<00:16:13.470> are<00:16:13.590> okay<00:16:13.920> with<00:16:14.070> I<00:16:14.340> mean<00:16:14.580> if<00:16:14.760> an 00:16:14.960 --> 00:16:14.970 align:start position:0% something we are okay with I mean if an 00:16:14.970 --> 00:16:17.410 align:start position:0% something we are okay with I mean if an attacker<00:16:15.240> a<00:16:15.360> physical<00:16:15.990> access<00:16:16.260> to<00:16:16.320> the<00:16:16.560> device 00:16:17.410 --> 00:16:17.420 align:start position:0% attacker a physical access to the device 00:16:17.420 --> 00:16:19.330 align:start position:0% attacker a physical access to the device we<00:16:18.420> are<00:16:18.540> ok<00:16:18.780> with<00:16:18.930> that 00:16:19.330 --> 00:16:19.340 align:start position:0% we are ok with that 00:16:19.340 --> 00:16:22.610 align:start position:0% we are ok with that now<00:16:20.340> after<00:16:20.760> that<00:16:21.210> so<00:16:21.510> another<00:16:21.840> property<00:16:22.350> is 00:16:22.610 --> 00:16:22.620 align:start position:0% now after that so another property is 00:16:22.620 --> 00:16:24.230 align:start position:0% now after that so another property is that<00:16:22.920> hardware<00:16:23.490> wallet<00:16:23.730> should<00:16:23.910> be<00:16:24.060> flexible 00:16:24.230 --> 00:16:24.240 align:start position:0% that hardware wallet should be flexible 00:16:24.240 --> 00:16:27.380 align:start position:0% that hardware wallet should be flexible so<00:16:25.050> if<00:16:25.410> we<00:16:25.770> have<00:16:25.920> well<00:16:26.520> at<00:16:26.670> some<00:16:26.910> buried<00:16:27.180> in<00:16:27.300> a 00:16:27.380 --> 00:16:27.390 align:start position:0% so if we have well at some buried in a 00:16:27.390 --> 00:16:29.180 align:start position:0% so if we have well at some buried in a trusted<00:16:27.720> computer<00:16:28.140> environment<00:16:28.230> we<00:16:28.950> should 00:16:29.180 --> 00:16:29.190 align:start position:0% trusted computer environment we should 00:16:29.190 --> 00:16:31.970 align:start position:0% trusted computer environment we should be<00:16:29.400> we<00:16:30.150> should<00:16:30.180> be<00:16:30.420> able<00:16:30.750> to<00:16:30.960> update<00:16:31.530> a<00:16:31.560> wallet 00:16:31.970 --> 00:16:31.980 align:start position:0% be we should be able to update a wallet 00:16:31.980 --> 00:16:34.640 align:start position:0% be we should be able to update a wallet in<00:16:32.250> all<00:16:32.850> kind<00:16:33.120> of<00:16:33.210> situations<00:16:33.840> so<00:16:33.930> even<00:16:34.410> if<00:16:34.530> the 00:16:34.640 --> 00:16:34.650 align:start position:0% in all kind of situations so even if the 00:16:34.650 --> 00:16:36.710 align:start position:0% in all kind of situations so even if the device<00:16:34.800> is<00:16:35.070> compromised<00:16:35.610> or<00:16:35.880> even<00:16:36.360> if<00:16:36.450> we<00:16:36.480> have 00:16:36.710 --> 00:16:36.720 align:start position:0% device is compromised or even if we have 00:16:36.720 --> 00:16:39.050 align:start position:0% device is compromised or even if we have a<00:16:36.750> new<00:16:36.990> tab<00:16:37.230> we<00:16:37.980> should<00:16:38.190> be<00:16:38.340> able<00:16:38.430> to<00:16:38.580> load<00:16:38.850> that 00:16:39.050 --> 00:16:39.060 align:start position:0% a new tab we should be able to load that 00:16:39.060 --> 00:16:41.120 align:start position:0% a new tab we should be able to load that that<00:16:39.300> in<00:16:39.600> the<00:16:39.660> environment<00:16:40.350> and<00:16:40.590> we<00:16:40.800> should<00:16:40.980> be 00:16:41.120 --> 00:16:41.130 align:start position:0% that in the environment and we should be 00:16:41.130 --> 00:16:44.210 align:start position:0% that in the environment and we should be able<00:16:41.220> to<00:16:41.370> well<00:16:41.940> I<00:16:42.290> should<00:16:43.290> be<00:16:43.410> able<00:16:43.500> to<00:16:43.650> update 00:16:44.210 --> 00:16:44.220 align:start position:0% able to well I should be able to update 00:16:44.220 --> 00:16:46.820 align:start position:0% able to well I should be able to update the<00:16:45.180> wallet<00:16:45.480> to<00:16:45.720> work<00:16:45.930> with<00:16:46.140> a<00:16:46.170> new<00:16:46.380> use<00:16:46.590> case 00:16:46.820 --> 00:16:46.830 align:start position:0% the wallet to work with a new use case 00:16:46.830 --> 00:16:48.740 align:start position:0% the wallet to work with a new use case that<00:16:46.860> we<00:16:47.220> have<00:16:47.340> so<00:16:47.760> that's<00:16:47.910> very<00:16:48.150> important 00:16:48.740 --> 00:16:48.750 align:start position:0% that we have so that's very important 00:16:48.750 --> 00:16:50.600 align:start position:0% that we have so that's very important for<00:16:48.840> IT<00:16:49.200> reom<00:16:49.410> because<00:16:49.890> we<00:16:50.160> have<00:16:50.280> a<00:16:50.310> lot<00:16:50.460> of 00:16:50.600 --> 00:16:50.610 align:start position:0% for IT reom because we have a lot of 00:16:50.610 --> 00:16:52.330 align:start position:0% for IT reom because we have a lot of tabs<00:16:50.850> as<00:16:51.120> they<00:16:51.630> all<00:16:51.780> have<00:16:52.050> a<00:16:52.080> different 00:16:52.330 --> 00:16:52.340 align:start position:0% tabs as they all have a different 00:16:52.340 --> 00:16:54.890 align:start position:0% tabs as they all have a different interaction<00:16:53.340> with<00:16:53.520> the<00:16:53.610> user<00:16:53.820> and<00:16:54.120> we<00:16:54.600> want<00:16:54.780> to 00:16:54.890 --> 00:16:54.900 align:start position:0% interaction with the user and we want to 00:16:54.900 --> 00:16:56.720 align:start position:0% interaction with the user and we want to make<00:16:55.050> sure<00:16:55.080> that<00:16:55.500> the<00:16:55.650> malware<00:16:55.830> will<00:16:56.310> not<00:16:56.550> be 00:16:56.720 --> 00:16:56.730 align:start position:0% make sure that the malware will not be 00:16:56.730 --> 00:16:58.790 align:start position:0% make sure that the malware will not be able<00:16:56.850> to<00:16:57.030> make<00:16:57.330> you<00:16:57.510> do<00:16:57.720> something<00:16:57.750> else<00:16:58.380> with 00:16:58.790 --> 00:16:58.800 align:start position:0% able to make you do something else with 00:16:58.800 --> 00:17:00.710 align:start position:0% able to make you do something else with your<00:16:58.980> dad<00:16:59.130> so<00:16:59.160> basically<00:16:59.910> sign<00:17:00.180> some<00:17:00.480> things 00:17:00.710 --> 00:17:00.720 align:start position:0% your dad so basically sign some things 00:17:00.720 --> 00:17:03.260 align:start position:0% your dad so basically sign some things that<00:17:00.870> you<00:17:00.990> didn't<00:17:01.260> want<00:17:01.440> to<00:17:01.560> do<00:17:01.710> and<00:17:02.000> well<00:17:03.000> use 00:17:03.260 --> 00:17:03.270 align:start position:0% that you didn't want to do and well use 00:17:03.270 --> 00:17:06.350 align:start position:0% that you didn't want to do and well use your<00:17:03.450> funds<00:17:03.690> to<00:17:03.870> do<00:17:03.990> something<00:17:04.320> else<00:17:05.120> then<00:17:06.120> we 00:17:06.350 --> 00:17:06.360 align:start position:0% your funds to do something else then we 00:17:06.360 --> 00:17:09.020 align:start position:0% your funds to do something else then we want<00:17:06.930> to<00:17:07.050> make<00:17:07.380> sure<00:17:07.410> that<00:17:07.980> on<00:17:08.310> the<00:17:08.370> hardware 00:17:09.020 --> 00:17:09.030 align:start position:0% want to make sure that on the hardware 00:17:09.030 --> 00:17:11.329 align:start position:0% want to make sure that on the hardware wallet<00:17:09.360> we<00:17:09.660> get<00:17:09.839> a<00:17:09.870> user<00:17:10.140> confirmation<00:17:10.620> so 00:17:11.329 --> 00:17:11.339 align:start position:0% wallet we get a user confirmation so 00:17:11.339 --> 00:17:13.430 align:start position:0% wallet we get a user confirmation so that<00:17:11.610> was<00:17:11.850> something<00:17:12.329> that<00:17:12.360> was<00:17:12.630> missing<00:17:12.810> from 00:17:13.430 --> 00:17:13.440 align:start position:0% that was something that was missing from 00:17:13.440 --> 00:17:16.370 align:start position:0% that was something that was missing from our<00:17:14.010> stack<00:17:14.430> before<00:17:14.730> and<00:17:15.120> I<00:17:15.720> will<00:17:15.870> tell<00:17:16.110> after 00:17:16.370 --> 00:17:16.380 align:start position:0% our stack before and I will tell after 00:17:16.380 --> 00:17:17.960 align:start position:0% our stack before and I will tell after that<00:17:16.560> a<00:17:16.589> little<00:17:16.949> bit<00:17:17.100> more<00:17:17.310> how<00:17:17.579> another 00:17:17.960 --> 00:17:17.970 align:start position:0% that a little bit more how another 00:17:17.970 --> 00:17:21.020 align:start position:0% that a little bit more how another intelli<00:17:18.390> P<00:17:18.540> I<00:17:18.570> helped<00:17:19.050> us<00:17:19.199> to<00:17:19.740> solve<00:17:19.980> that<00:17:20.130> but 00:17:21.020 --> 00:17:21.030 align:start position:0% intelli P I helped us to solve that but 00:17:21.030 --> 00:17:23.329 align:start position:0% intelli P I helped us to solve that but today<00:17:21.480> if<00:17:21.600> you<00:17:21.750> want<00:17:21.990> to<00:17:22.260> come<00:17:22.589> is<00:17:22.890> user 00:17:23.329 --> 00:17:23.339 align:start position:0% today if you want to come is user 00:17:23.339 --> 00:17:25.490 align:start position:0% today if you want to come is user confirmation<00:17:23.790> is<00:17:24.180> paramount<00:17:24.600> when<00:17:24.900> you<00:17:25.410> are 00:17:25.490 --> 00:17:25.500 align:start position:0% confirmation is paramount when you are 00:17:25.500 --> 00:17:27.350 align:start position:0% confirmation is paramount when you are spending<00:17:25.680> money<00:17:26.010> because<00:17:26.280> you<00:17:26.670> must<00:17:26.910> click 00:17:27.350 --> 00:17:27.360 align:start position:0% spending money because you must click 00:17:27.360 --> 00:17:29.890 align:start position:0% spending money because you must click and<00:17:27.630> you<00:17:27.720> must<00:17:27.959> make<00:17:28.530> sure<00:17:28.560> that<00:17:29.040> the<00:17:29.520> user 00:17:29.890 --> 00:17:29.900 align:start position:0% and you must make sure that the user 00:17:29.900 --> 00:17:32.870 align:start position:0% and you must make sure that the user cannot<00:17:30.900> be<00:17:31.230> faked<00:17:32.070> by<00:17:32.430> a<00:17:32.460> man 00:17:32.870 --> 00:17:32.880 align:start position:0% cannot be faked by a man 00:17:32.880 --> 00:17:34.880 align:start position:0% cannot be faked by a man so<00:17:33.120> that<00:17:33.270> this<00:17:33.419> click<00:17:33.990> cannot<00:17:34.350> be<00:17:34.500> faked<00:17:34.679> by<00:17:34.860> a 00:17:34.880 --> 00:17:34.890 align:start position:0% so that this click cannot be faked by a 00:17:34.890 --> 00:17:38.600 align:start position:0% so that this click cannot be faked by a malware<00:17:35.130> and<00:17:35.780> well<00:17:36.780> I<00:17:37.020> add<00:17:37.260> another<00:17:37.740> point<00:17:38.070> so 00:17:38.600 --> 00:17:38.610 align:start position:0% malware and well I add another point so 00:17:38.610 --> 00:17:41.390 align:start position:0% malware and well I add another point so I'm<00:17:39.179> trying<00:17:39.600> to<00:17:39.690> remember<00:17:40.049> it<00:17:40.350> because<00:17:40.530> not 00:17:41.390 --> 00:17:41.400 align:start position:0% I'm trying to remember it because not 00:17:41.400 --> 00:17:43.039 align:start position:0% I'm trying to remember it because not the<00:17:41.429> right<00:17:41.669> version<00:17:42.000> of<00:17:42.090> the<00:17:42.210> slides<00:17:42.480> but<00:17:42.750> if<00:17:42.960> I 00:17:43.039 --> 00:17:43.049 align:start position:0% the right version of the slides but if I 00:17:43.049 --> 00:17:46.810 align:start position:0% the right version of the slides but if I think<00:17:43.260> about<00:17:43.500> it<00:17:43.679> I<00:17:43.799> will<00:17:43.980> tell<00:17:44.850> it<00:17:44.970> later 00:17:46.810 --> 00:17:46.820 align:start position:0% think about it I will tell it later 00:17:46.820 --> 00:17:49.430 align:start position:0% think about it I will tell it later so<00:17:47.820> on<00:17:48.120> the<00:17:48.330> things<00:17:48.600> that<00:17:48.750> we<00:17:48.900> have<00:17:49.020> done<00:17:49.230> we 00:17:49.430 --> 00:17:49.440 align:start position:0% so on the things that we have done we 00:17:49.440 --> 00:17:51.289 align:start position:0% so on the things that we have done we managed<00:17:49.740> to<00:17:49.770> guarantee<00:17:50.400> this<00:17:50.549> possibility 00:17:51.289 --> 00:17:51.299 align:start position:0% managed to guarantee this possibility 00:17:51.299 --> 00:17:53.720 align:start position:0% managed to guarantee this possibility between<00:17:51.780> hardware<00:17:52.200> wallets<00:17:52.620> and<00:17:52.890> let<00:17:53.160> compute 00:17:53.720 --> 00:17:53.730 align:start position:0% between hardware wallets and let compute 00:17:53.730 --> 00:17:55.580 align:start position:0% between hardware wallets and let compute by<00:17:53.940> using<00:17:54.120> an<00:17:54.360> architecture<00:17:54.960> which<00:17:54.990> makes<00:17:55.440> an 00:17:55.580 --> 00:17:55.590 align:start position:0% by using an architecture which makes an 00:17:55.590 --> 00:17:58.640 align:start position:0% by using an architecture which makes an abstraction<00:17:55.980> of<00:17:56.400> the<00:17:57.240> stack<00:17:57.480> so<00:17:57.750> today<00:17:58.470> when 00:17:58.640 --> 00:17:58.650 align:start position:0% abstraction of the stack so today when 00:17:58.650 --> 00:18:00.680 align:start position:0% abstraction of the stack so today when you<00:17:58.770> write<00:17:58.980> an<00:17:59.280> application<00:17:59.880> for<00:18:00.330> let<00:18:00.539> your 00:18:00.680 --> 00:18:00.690 align:start position:0% you write an application for let your 00:18:00.690 --> 00:18:02.480 align:start position:0% you write an application for let your products<00:18:01.080> you<00:18:01.260> write<00:18:01.410> your<00:18:01.590> application<00:18:02.100> in<00:18:02.220> C 00:18:02.480 --> 00:18:02.490 align:start position:0% products you write your application in C 00:18:02.490 --> 00:18:05.600 align:start position:0% products you write your application in C we<00:18:03.000> consider<00:18:03.419> that<00:18:03.750> C<00:18:04.200> is<00:18:04.890> portable<00:18:05.280> enough 00:18:05.600 --> 00:18:05.610 align:start position:0% we consider that C is portable enough 00:18:05.610 --> 00:18:07.250 align:start position:0% we consider that C is portable enough for<00:18:05.970> people<00:18:06.299> to<00:18:06.510> work<00:18:06.690> in<00:18:07.020> several 00:18:07.250 --> 00:18:07.260 align:start position:0% for people to work in several 00:18:07.260 --> 00:18:09.649 align:start position:0% for people to work in several environments<00:18:07.980> so<00:18:08.549> either<00:18:08.820> you<00:18:09.179> are<00:18:09.299> working 00:18:09.649 --> 00:18:09.659 align:start position:0% environments so either you are working 00:18:09.659 --> 00:18:11.419 align:start position:0% environments so either you are working in<00:18:09.750> a<00:18:09.840> native<00:18:10.169> environment<00:18:10.740> like<00:18:10.980> a<00:18:11.010> secure 00:18:11.419 --> 00:18:11.429 align:start position:0% in a native environment like a secure 00:18:11.429 --> 00:18:12.980 align:start position:0% in a native environment like a secure element<00:18:11.520> and<00:18:12.000> in<00:18:12.090> this<00:18:12.240> case<00:18:12.510> you<00:18:12.659> are<00:18:12.690> cross 00:18:12.980 --> 00:18:12.990 align:start position:0% element and in this case you are cross 00:18:12.990 --> 00:18:15.169 align:start position:0% element and in this case you are cross compiling<00:18:13.350> to<00:18:13.500> arm<00:18:13.799> if<00:18:14.220> you<00:18:14.429> are<00:18:14.730> working<00:18:15.059> with 00:18:15.169 --> 00:18:15.179 align:start position:0% compiling to arm if you are working with 00:18:15.179 --> 00:18:17.060 align:start position:0% compiling to arm if you are working with an<00:18:15.299> enclave<00:18:15.690> like<00:18:15.990> this<00:18:16.169> one<00:18:16.409> we<00:18:16.830> cross 00:18:17.060 --> 00:18:17.070 align:start position:0% an enclave like this one we cross 00:18:17.070 --> 00:18:19.909 align:start position:0% an enclave like this one we cross compile<00:18:17.520> to<00:18:17.820> a<00:18:18.059> virtual<00:18:18.870> CPU<00:18:19.289> called<00:18:19.559> Moxie 00:18:19.909 --> 00:18:19.919 align:start position:0% compile to a virtual CPU called Moxie 00:18:19.919 --> 00:18:22.250 align:start position:0% compile to a virtual CPU called Moxie which<00:18:20.580> has<00:18:20.730> been<00:18:20.909> well<00:18:21.299> studied<00:18:21.510> in<00:18:22.020> the 00:18:22.250 --> 00:18:22.260 align:start position:0% which has been well studied in the 00:18:22.260 --> 00:18:24.380 align:start position:0% which has been well studied in the Bitcoin<00:18:22.770> environment<00:18:22.919> already<00:18:23.490> and<00:18:23.880> the 00:18:24.380 --> 00:18:24.390 align:start position:0% Bitcoin environment already and the 00:18:24.390 --> 00:18:26.450 align:start position:0% Bitcoin environment already and the virtual<00:18:24.690> machine<00:18:24.990> is<00:18:25.110> very<00:18:25.289> simple<00:18:25.710> and<00:18:25.950> so 00:18:26.450 --> 00:18:26.460 align:start position:0% virtual machine is very simple and so 00:18:26.460 --> 00:18:28.100 align:start position:0% virtual machine is very simple and so you<00:18:26.520> can<00:18:26.909> guarantee<00:18:27.179> that<00:18:27.630> the<00:18:27.809> virtual 00:18:28.100 --> 00:18:28.110 align:start position:0% you can guarantee that the virtual 00:18:28.110 --> 00:18:30.230 align:start position:0% you can guarantee that the virtual machine<00:18:28.440> can<00:18:28.679> be<00:18:28.830> can<00:18:29.159> be<00:18:29.309> tested<00:18:29.520> and<00:18:29.880> can<00:18:30.120> be 00:18:30.230 --> 00:18:30.240 align:start position:0% machine can be can be tested and can be 00:18:30.240 --> 00:18:32.390 align:start position:0% machine can be can be tested and can be certified<00:18:30.750> even<00:18:31.080> if<00:18:31.260> you<00:18:31.770> have<00:18:31.890> some<00:18:32.100> if<00:18:32.370> you 00:18:32.390 --> 00:18:32.400 align:start position:0% certified even if you have some if you 00:18:32.400 --> 00:18:35.480 align:start position:0% certified even if you have some if you feel<00:18:32.700> the<00:18:32.880> need<00:18:33.000> a<00:18:33.059> bit<00:18:33.270> later<00:18:33.950> so<00:18:34.950> now<00:18:35.130> moving 00:18:35.480 --> 00:18:35.490 align:start position:0% feel the need a bit later so now moving 00:18:35.490 --> 00:18:39.710 align:start position:0% feel the need a bit later so now moving back<00:18:35.789> to<00:18:36.720> where<00:18:37.080> we<00:18:37.440> were<00:18:37.470> in<00:18:37.950> 2017<00:18:38.880> so<00:18:39.210> we<00:18:39.450> did 00:18:39.710 --> 00:18:39.720 align:start position:0% back to where we were in 2017 so we did 00:18:39.720 --> 00:18:42.230 align:start position:0% back to where we were in 2017 so we did an<00:18:40.020> initial<00:18:40.260> release<00:18:40.740> which<00:18:41.700> was<00:18:41.909> not<00:18:42.210> very 00:18:42.230 --> 00:18:42.240 align:start position:0% an initial release which was not very 00:18:42.240 --> 00:18:44.360 align:start position:0% an initial release which was not very successful<00:18:42.630> because<00:18:43.380> one<00:18:43.620> of<00:18:43.650> the<00:18:43.860> problem<00:18:44.250> of 00:18:44.360 --> 00:18:44.370 align:start position:0% successful because one of the problem of 00:18:44.370 --> 00:18:46.370 align:start position:0% successful because one of the problem of this<00:18:44.490> release<00:18:44.820> is<00:18:45.030> that<00:18:45.059> all<00:18:45.750> code<00:18:46.020> that<00:18:46.260> you 00:18:46.370 --> 00:18:46.380 align:start position:0% this release is that all code that you 00:18:46.380 --> 00:18:48.049 align:start position:0% this release is that all code that you developed<00:18:46.770> for<00:18:47.070> your<00:18:47.190> hardware<00:18:47.580> wallet<00:18:47.880> so 00:18:48.049 --> 00:18:48.059 align:start position:0% developed for your hardware wallet so 00:18:48.059 --> 00:18:49.700 align:start position:0% developed for your hardware wallet so for<00:18:48.270> your<00:18:48.390> new<00:18:48.570> application<00:18:49.140> running<00:18:49.409> and 00:18:49.700 --> 00:18:49.710 align:start position:0% for your new application running and 00:18:49.710 --> 00:18:52.399 align:start position:0% for your new application running and trusted<00:18:50.159> compute<00:18:50.549> and<00:18:50.669> SGX<00:18:51.120> had<00:18:51.870> to<00:18:52.020> be<00:18:52.140> signed 00:18:52.399 --> 00:18:52.409 align:start position:0% trusted compute and SGX had to be signed 00:18:52.409 --> 00:18:54.890 align:start position:0% trusted compute and SGX had to be signed by<00:18:52.500> letter<00:18:52.770> and<00:18:53.270> we<00:18:54.270> want<00:18:54.450> to<00:18:54.570> have<00:18:54.690> something 00:18:54.890 --> 00:18:54.900 align:start position:0% by letter and we want to have something 00:18:54.900 --> 00:18:56.840 align:start position:0% by letter and we want to have something completely<00:18:55.500> decentralized<00:18:55.830> so<00:18:56.370> we<00:18:56.549> want<00:18:56.760> to 00:18:56.840 --> 00:18:56.850 align:start position:0% completely decentralized so we want to 00:18:56.850 --> 00:18:58.220 align:start position:0% completely decentralized so we want to have<00:18:56.970> something<00:18:57.179> is<00:18:57.450> recruiting<00:18:57.840> securely 00:18:58.220 --> 00:18:58.230 align:start position:0% have something is recruiting securely 00:18:58.230 --> 00:19:00.320 align:start position:0% have something is recruiting securely that<00:18:58.710> you<00:18:58.830> can<00:18:58.980> sign<00:18:59.190> yourself<00:18:59.340> on<00:18:59.850> which<00:19:00.210> you 00:19:00.320 --> 00:19:00.330 align:start position:0% that you can sign yourself on which you 00:19:00.330 --> 00:19:02.210 align:start position:0% that you can sign yourself on which you can<00:19:00.450> trust<00:19:00.690> you<00:19:00.809> certificate<00:19:01.110> and<00:19:01.740> that's<00:19:02.010> not 00:19:02.210 --> 00:19:02.220 align:start position:0% can trust you certificate and that's not 00:19:02.220 --> 00:19:04.580 align:start position:0% can trust you certificate and that's not something<00:19:02.610> we<00:19:02.700> were<00:19:02.850> able<00:19:03.150> to<00:19:03.179> do<00:19:03.480> because<00:19:04.049> we 00:19:04.580 --> 00:19:04.590 align:start position:0% something we were able to do because we 00:19:04.590 --> 00:19:07.010 align:start position:0% something we were able to do because we had<00:19:04.710> no<00:19:04.919> way<00:19:04.950> to<00:19:05.130> gather<00:19:05.760> user<00:19:06.240> improvement<00:19:06.900> to 00:19:07.010 --> 00:19:07.020 align:start position:0% had no way to gather user improvement to 00:19:07.020 --> 00:19:09.049 align:start position:0% had no way to gather user improvement to make<00:19:07.140> sure<00:19:07.350> that<00:19:07.500> user<00:19:07.740> input<00:19:08.130> was<00:19:08.370> executed 00:19:09.049 --> 00:19:09.059 align:start position:0% make sure that user input was executed 00:19:09.059 --> 00:19:12.380 align:start position:0% make sure that user input was executed correctly<00:19:09.650> then<00:19:10.650> we<00:19:10.980> heard<00:19:11.520> about<00:19:11.640> a<00:19:11.820> new<00:19:12.090> API 00:19:12.380 --> 00:19:12.390 align:start position:0% correctly then we heard about a new API 00:19:12.390 --> 00:19:14.390 align:start position:0% correctly then we heard about a new API from<00:19:12.750> it<00:19:12.929> are<00:19:13.169> called<00:19:13.470> protected<00:19:13.950> transaction 00:19:14.390 --> 00:19:14.400 align:start position:0% from it are called protected transaction 00:19:14.400 --> 00:19:17.600 align:start position:0% from it are called protected transaction display<00:19:14.809> that<00:19:15.809> we<00:19:16.080> used<00:19:16.490> typically<00:19:17.490> for 00:19:17.600 --> 00:19:17.610 align:start position:0% display that we used typically for 00:19:17.610 --> 00:19:19.460 align:start position:0% display that we used typically for several<00:19:18.150> things<00:19:18.360> so<00:19:18.720> the<00:19:18.870> first<00:19:19.110> thing<00:19:19.320> is 00:19:19.460 --> 00:19:19.470 align:start position:0% several things so the first thing is 00:19:19.470 --> 00:19:21.080 align:start position:0% several things so the first thing is that<00:19:19.620> with<00:19:19.799> protected<00:19:20.250> transaction<00:19:20.700> display 00:19:21.080 --> 00:19:21.090 align:start position:0% that with protected transaction display 00:19:21.090 --> 00:19:24.080 align:start position:0% that with protected transaction display you<00:19:21.750> can<00:19:21.929> get<00:19:22.200> user<00:19:22.650> you<00:19:23.100> can<00:19:23.250> display<00:19:23.700> things 00:19:24.080 --> 00:19:24.090 align:start position:0% you can get user you can display things 00:19:24.090 --> 00:19:26.240 align:start position:0% you can get user you can display things to<00:19:24.360> the<00:19:24.480> users<00:19:24.840> that<00:19:24.870> are<00:19:25.350> hard<00:19:25.559> to<00:19:25.620> fake<00:19:25.919> and 00:19:26.240 --> 00:19:26.250 align:start position:0% to the users that are hard to fake and 00:19:26.250 --> 00:19:28.700 align:start position:0% to the users that are hard to fake and you<00:19:26.549> can<00:19:26.730> gather<00:19:27.000> user<00:19:27.390> inputs<00:19:27.900> in<00:19:28.230> a<00:19:28.350> trusted 00:19:28.700 --> 00:19:28.710 align:start position:0% you can gather user inputs in a trusted 00:19:28.710 --> 00:19:30.980 align:start position:0% you can gather user inputs in a trusted way<00:19:28.950> so<00:19:29.340> today<00:19:29.640> so<00:19:30.150> user<00:19:30.330> input<00:19:30.720> you<00:19:30.840> can 00:19:30.980 --> 00:19:30.990 align:start position:0% way so today so user input you can 00:19:30.990 --> 00:19:32.870 align:start position:0% way so today so user input you can gather<00:19:31.200> a<00:19:31.380> pretty<00:19:31.710> simple<00:19:32.159> so<00:19:32.400> you<00:19:32.460> have<00:19:32.610> a<00:19:32.640> PIN 00:19:32.870 --> 00:19:32.880 align:start position:0% gather a pretty simple so you have a PIN 00:19:32.880 --> 00:19:35.390 align:start position:0% gather a pretty simple so you have a PIN pad<00:19:33.120> and<00:19:33.419> the<00:19:33.510> PIN<00:19:33.690> pad<00:19:33.870> is<00:19:34.020> what<00:19:34.440> on<00:19:34.710> screen<00:19:35.070> so 00:19:35.390 --> 00:19:35.400 align:start position:0% pad and the PIN pad is what on screen so 00:19:35.400 --> 00:19:37.520 align:start position:0% pad and the PIN pad is what on screen so you<00:19:35.460> can't<00:19:35.789> really<00:19:36.090> know<00:19:36.270> what<00:19:37.080> the<00:19:37.230> user<00:19:37.380> has 00:19:37.520 --> 00:19:37.530 align:start position:0% you can't really know what the user has 00:19:37.530 --> 00:19:39.919 align:start position:0% you can't really know what the user has selected<00:19:37.799> if<00:19:38.220> you<00:19:38.340> are<00:19:38.460> malware<00:19:38.820> but<00:19:39.360> if<00:19:39.750> you 00:19:39.919 --> 00:19:39.929 align:start position:0% selected if you are malware but if you 00:19:39.929 --> 00:19:41.750 align:start position:0% selected if you are malware but if you want<00:19:40.110> Enclave<00:19:40.500> you<00:19:40.770> are<00:19:40.890> going<00:19:41.100> to<00:19:41.250> get<00:19:41.400> the 00:19:41.750 --> 00:19:41.760 align:start position:0% want Enclave you are going to get the 00:19:41.760 --> 00:19:44.060 align:start position:0% want Enclave you are going to get the right<00:19:41.909> thing<00:19:42.179> that<00:19:42.210> the<00:19:42.510> user<00:19:42.690> types<00:19:43.049> so<00:19:43.409> it's 00:19:44.060 --> 00:19:44.070 align:start position:0% right thing that the user types so it's 00:19:44.070 --> 00:19:46.730 align:start position:0% right thing that the user types so it's a<00:19:44.250> clean<00:19:44.549> and<00:19:44.850> it's<00:19:45.210> an<00:19:45.419> easy<00:19:45.750> solution<00:19:46.110> to<00:19:46.440> get 00:19:46.730 --> 00:19:46.740 align:start position:0% a clean and it's an easy solution to get 00:19:46.740 --> 00:19:48.950 align:start position:0% a clean and it's an easy solution to get seeker<00:19:47.070> user<00:19:47.250> input<00:19:47.669> and<00:19:47.880> we<00:19:48.450> are<00:19:48.539> using<00:19:48.840> it 00:19:48.950 --> 00:19:48.960 align:start position:0% seeker user input and we are using it 00:19:48.960 --> 00:19:50.870 align:start position:0% seeker user input and we are using it for<00:19:48.990> two<00:19:49.289> things<00:19:49.500> so<00:19:49.860> we<00:19:50.100> are<00:19:50.190> using<00:19:50.340> it<00:19:50.580> first 00:19:50.870 --> 00:19:50.880 align:start position:0% for two things so we are using it first 00:19:50.880 --> 00:19:52.880 align:start position:0% for two things so we are using it first to<00:19:51.179> get<00:19:51.330> a<00:19:51.360> user<00:19:51.659> confirmation<00:19:52.380> if<00:19:52.559> the<00:19:52.679> code 00:19:52.880 --> 00:19:52.890 align:start position:0% to get a user confirmation if the code 00:19:52.890 --> 00:19:55.279 align:start position:0% to get a user confirmation if the code is<00:19:52.919> not<00:19:53.250> signed<00:19:53.490> by<00:19:53.669> letter<00:19:53.909> so<00:19:54.750> thus<00:19:54.990> we<00:19:55.260> are 00:19:55.279 --> 00:19:55.289 align:start position:0% is not signed by letter so thus we are 00:19:55.289 --> 00:19:56.930 align:start position:0% is not signed by letter so thus we are solving<00:19:55.679> the<00:19:55.799> first<00:19:55.950> problem<00:19:56.340> we<00:19:56.520> can<00:19:56.700> run 00:19:56.930 --> 00:19:56.940 align:start position:0% solving the first problem we can run 00:19:56.940 --> 00:19:59.060 align:start position:0% solving the first problem we can run unsigned<00:19:57.240> code<00:19:57.630> we<00:19:57.960> can<00:19:58.140> run<00:19:58.440> code<00:19:58.740> that<00:19:58.950> we 00:19:59.060 --> 00:19:59.070 align:start position:0% unsigned code we can run code that we 00:19:59.070 --> 00:20:01.669 align:start position:0% unsigned code we can run code that we didn't<00:19:59.370> trust<00:19:59.610> that<00:20:00.000> we<00:20:00.149> don't<00:20:00.360> trust<00:20:00.600> and<00:20:00.840> we 00:20:01.669 --> 00:20:01.679 align:start position:0% didn't trust that we don't trust and we 00:20:01.679 --> 00:20:03.860 align:start position:0% didn't trust that we don't trust and we can<00:20:01.919> limit<00:20:02.220> the<00:20:02.370> features<00:20:02.970> that<00:20:03.000> this<00:20:03.480> code<00:20:03.750> is 00:20:03.860 --> 00:20:03.870 align:start position:0% can limit the features that this code is 00:20:03.870 --> 00:20:06.110 align:start position:0% can limit the features that this code is going<00:20:04.020> to<00:20:04.140> run<00:20:04.230> if<00:20:04.559> it's<00:20:04.710> not<00:20:04.890> signed<00:20:05.159> by<00:20:05.370> us<00:20:05.549> so 00:20:06.110 --> 00:20:06.120 align:start position:0% going to run if it's not signed by us so 00:20:06.120 --> 00:20:08.299 align:start position:0% going to run if it's not signed by us so here<00:20:06.600> we<00:20:07.440> talked<00:20:07.679> about<00:20:07.770> the<00:20:08.070> attestation 00:20:08.299 --> 00:20:08.309 align:start position:0% here we talked about the attestation 00:20:08.309 --> 00:20:10.430 align:start position:0% here we talked about the attestation before<00:20:09.029> we<00:20:09.419> can<00:20:09.630> have<00:20:09.720> an<00:20:09.840> ANSI<00:20:10.049> station 00:20:10.430 --> 00:20:10.440 align:start position:0% before we can have an ANSI station 00:20:10.440 --> 00:20:13.100 align:start position:0% before we can have an ANSI station saying<00:20:10.710> okay<00:20:11.130> the<00:20:11.340> code<00:20:11.549> is<00:20:11.669> running<00:20:12.029> the<00:20:12.990> code 00:20:13.100 --> 00:20:13.110 align:start position:0% saying okay the code is running the code 00:20:13.110 --> 00:20:14.720 align:start position:0% saying okay the code is running the code is<00:20:13.260> trusted<00:20:13.590> by<00:20:13.620> later<00:20:13.950> running<00:20:14.399> into<00:20:14.700> a 00:20:14.720 --> 00:20:14.730 align:start position:0% is trusted by later running into a 00:20:14.730 --> 00:20:16.970 align:start position:0% is trusted by later running into a platform<00:20:15.390> if<00:20:15.630> the<00:20:15.870> code<00:20:16.049> is<00:20:16.080> signed<00:20:16.409> by<00:20:16.559> us<00:20:16.740> if 00:20:16.970 --> 00:20:16.980 align:start position:0% platform if the code is signed by us if 00:20:16.980 --> 00:20:19.399 align:start position:0% platform if the code is signed by us if it's<00:20:17.399> not<00:20:17.610> signed<00:20:17.820> by<00:20:18.029> us<00:20:18.210> it<00:20:18.390> can<00:20:18.690> still<00:20:19.169> use 00:20:19.399 --> 00:20:19.409 align:start position:0% it's not signed by us it can still use 00:20:19.409 --> 00:20:21.620 align:start position:0% it's not signed by us it can still use all<00:20:19.649> properties<00:20:20.309> of<00:20:20.549> a<00:20:21.000> secure<00:20:21.419> environment 00:20:21.620 --> 00:20:21.630 align:start position:0% all properties of a secure environment 00:20:21.630 --> 00:20:23.450 align:start position:0% all properties of a secure environment without<00:20:22.200> the<00:20:22.440> attestation<00:20:22.679> so<00:20:23.159> that's<00:20:23.340> an 00:20:23.450 --> 00:20:23.460 align:start position:0% without the attestation so that's an 00:20:23.460 --> 00:20:25.190 align:start position:0% without the attestation so that's an example<00:20:23.730> about<00:20:24.330> that<00:20:24.659> some<00:20:24.809> things<00:20:25.020> that's 00:20:25.190 --> 00:20:25.200 align:start position:0% example about that some things that's 00:20:25.200 --> 00:20:27.380 align:start position:0% example about that some things that's very<00:20:25.409> customizable<00:20:25.919> and<00:20:26.220> the<00:20:26.549> end<00:20:26.760> result<00:20:27.240> is 00:20:27.380 --> 00:20:27.390 align:start position:0% very customizable and the end result is 00:20:27.390 --> 00:20:29.180 align:start position:0% very customizable and the end result is that<00:20:27.600> people<00:20:27.960> will<00:20:28.140> be<00:20:28.260> able<00:20:28.500> to<00:20:28.649> design<00:20:28.980> their 00:20:29.180 --> 00:20:29.190 align:start position:0% that people will be able to design their 00:20:29.190 --> 00:20:31.370 align:start position:0% that people will be able to design their own<00:20:29.340> code<00:20:29.700> without<00:20:30.029> getting<00:20:30.990> a<00:20:31.080> signature 00:20:31.370 --> 00:20:31.380 align:start position:0% own code without getting a signature 00:20:31.380 --> 00:20:34.519 align:start position:0% own code without getting a signature from<00:20:31.710> nature<00:20:32.010> before<00:20:32.610> and<00:20:32.880> the<00:20:33.870> other<00:20:33.990> obvious 00:20:34.519 --> 00:20:34.529 align:start position:0% from nature before and the other obvious 00:20:34.529 --> 00:20:36.080 align:start position:0% from nature before and the other obvious use<00:20:34.740> case<00:20:34.980> of<00:20:35.130> trusted<00:20:35.460> computer 00:20:36.080 --> 00:20:36.090 align:start position:0% use case of trusted computer 00:20:36.090 --> 00:20:38.480 align:start position:0% use case of trusted computer sorry<00:20:36.779> of<00:20:36.990> BT's<00:20:37.440> of<00:20:37.649> protected<00:20:38.070> tradition 00:20:38.480 --> 00:20:38.490 align:start position:0% sorry of BT's of protected tradition 00:20:38.490 --> 00:20:40.880 align:start position:0% sorry of BT's of protected tradition display<00:20:38.880> is<00:20:39.299> that<00:20:39.690> we<00:20:39.870> can<00:20:40.020> use<00:20:40.200> it<00:20:40.350> to<00:20:40.380> display 00:20:40.880 --> 00:20:40.890 align:start position:0% display is that we can use it to display 00:20:40.890 --> 00:20:42.740 align:start position:0% display is that we can use it to display so<00:20:41.309> the<00:20:41.520> transaction<00:20:41.820> so<00:20:42.330> when<00:20:42.600> you're 00:20:42.740 --> 00:20:42.750 align:start position:0% so the transaction so when you're 00:20:42.750 --> 00:20:44.510 align:start position:0% so the transaction so when you're interacting<00:20:43.020> with<00:20:43.409> a<00:20:43.440> smart<00:20:43.740> contract<00:20:44.159> we<00:20:44.370> can 00:20:44.510 --> 00:20:44.520 align:start position:0% interacting with a smart contract we can 00:20:44.520 --> 00:20:45.950 align:start position:0% interacting with a smart contract we can display<00:20:44.970> the<00:20:45.000> transactions<00:20:45.630> that<00:20:45.720> you<00:20:45.779> are 00:20:45.950 --> 00:20:45.960 align:start position:0% display the transactions that you are 00:20:45.960 --> 00:20:49.220 align:start position:0% display the transactions that you are sending<00:20:46.320> and<00:20:46.529> then<00:20:47.250> we<00:20:47.399> can<00:20:47.580> use<00:20:47.820> this<00:20:48.630> as<00:20:48.929> well 00:20:49.220 --> 00:20:49.230 align:start position:0% sending and then we can use this as well 00:20:49.230 --> 00:20:52.610 align:start position:0% sending and then we can use this as well to<00:20:49.529> load<00:20:49.740> new<00:20:50.270> UI<00:20:51.270> is<00:20:51.480> if<00:20:51.779> you<00:20:51.990> are<00:20:52.110> using<00:20:52.140> a<00:20:52.470> new 00:20:52.610 --> 00:20:52.620 align:start position:0% to load new UI is if you are using a new 00:20:52.620 --> 00:20:55.430 align:start position:0% to load new UI is if you are using a new tab<00:20:52.830> so<00:20:53.130> today<00:20:53.929> when<00:20:54.929> you<00:20:55.110> are<00:20:55.200> interacting 00:20:55.430 --> 00:20:55.440 align:start position:0% tab so today when you are interacting 00:20:55.440 --> 00:20:58.730 align:start position:0% tab so today when you are interacting with<00:20:55.799> it<00:20:56.039> up<00:20:56.250> and<00:20:56.520> meta<00:20:56.789> mask<00:20:57.120> and<00:20:57.419> also<00:20:58.320> wallet 00:20:58.730 --> 00:20:58.740 align:start position:0% with it up and meta mask and also wallet 00:20:58.740 --> 00:21:01.490 align:start position:0% with it up and meta mask and also wallet you<00:20:59.279> are<00:20:59.309> getting<00:20:59.820> if<00:21:00.690> you<00:21:00.750> send<00:21:01.140> some<00:21:01.320> data 00:21:01.490 --> 00:21:01.500 align:start position:0% you are getting if you send some data 00:21:01.500 --> 00:21:04.220 align:start position:0% you are getting if you send some data you're<00:21:01.919> going<00:21:02.520> to<00:21:02.850> see<00:21:03.059> that<00:21:03.240> you<00:21:03.390> are<00:21:03.419> signing 00:21:04.220 --> 00:21:04.230 align:start position:0% you're going to see that you are signing 00:21:04.230 --> 00:21:05.779 align:start position:0% you're going to see that you are signing a<00:21:04.320> blob<00:21:04.529> so<00:21:04.830> you<00:21:04.890> don't<00:21:05.130> know<00:21:05.279> what<00:21:05.429> this<00:21:05.580> blob 00:21:05.779 --> 00:21:05.789 align:start position:0% a blob so you don't know what this blob 00:21:05.789 --> 00:21:07.399 align:start position:0% a blob so you don't know what this blob is<00:21:05.940> doing<00:21:06.270> and<00:21:06.419> you<00:21:06.510> need<00:21:06.630> some<00:21:06.899> kind<00:21:06.929> of 00:21:07.399 --> 00:21:07.409 align:start position:0% is doing and you need some kind of 00:21:07.409 --> 00:21:10.549 align:start position:0% is doing and you need some kind of author<00:21:07.710> another<00:21:08.399> UI<00:21:08.669> to<00:21:09.630> confirm<00:21:10.110> and<00:21:10.320> to<00:21:10.350> make 00:21:10.549 --> 00:21:10.559 align:start position:0% author another UI to confirm and to make 00:21:10.559 --> 00:21:11.840 align:start position:0% author another UI to confirm and to make sure<00:21:10.590> that<00:21:10.919> you<00:21:11.039> are<00:21:11.159> doing<00:21:11.370> the<00:21:11.460> right<00:21:11.610> thing 00:21:11.840 --> 00:21:11.850 align:start position:0% sure that you are doing the right thing 00:21:11.850 --> 00:21:14.210 align:start position:0% sure that you are doing the right thing and<00:21:12.029> PTD<00:21:12.870> will<00:21:13.110> allow<00:21:13.440> you<00:21:13.500> to<00:21:13.770> solve<00:21:13.980> that 00:21:14.210 --> 00:21:14.220 align:start position:0% and PTD will allow you to solve that 00:21:14.220 --> 00:21:16.669 align:start position:0% and PTD will allow you to solve that along<00:21:14.820> with<00:21:14.850> a<00:21:15.000> platform<00:21:15.510> like<00:21:15.690> ours<00:21:15.840> as<00:21:16.230> I 00:21:16.669 --> 00:21:16.679 align:start position:0% along with a platform like ours as I 00:21:16.679 --> 00:21:18.380 align:start position:0% along with a platform like ours as I thought<00:21:16.830> you<00:21:16.980> run<00:21:17.370> that<00:21:18.029> you<00:21:18.149> load 00:21:18.380 --> 00:21:18.390 align:start position:0% thought you run that you load 00:21:18.390 --> 00:21:20.450 align:start position:0% thought you run that you load dynamically<00:21:19.080> your<00:21:19.289> new<00:21:19.409> code<00:21:19.679> for<00:21:20.100> your<00:21:20.250> tabs 00:21:20.450 --> 00:21:20.460 align:start position:0% dynamically your new code for your tabs 00:21:20.460 --> 00:21:22.580 align:start position:0% dynamically your new code for your tabs so<00:21:20.909> you<00:21:20.940> could<00:21:21.270> have<00:21:21.390> one<00:21:21.419> small<00:21:22.230> piece<00:21:22.529> of 00:21:22.580 --> 00:21:22.590 align:start position:0% so you could have one small piece of 00:21:22.590 --> 00:21:24.560 align:start position:0% so you could have one small piece of code<00:21:22.950> one<00:21:23.190> small<00:21:23.429> piece<00:21:23.610> of<00:21:23.669> script<00:21:24.149> for<00:21:24.419> all 00:21:24.560 --> 00:21:24.570 align:start position:0% code one small piece of script for all 00:21:24.570 --> 00:21:27.440 align:start position:0% code one small piece of script for all your<00:21:25.200> new<00:21:25.350> tabs<00:21:25.590> and<00:21:25.830> this<00:21:26.640> way<00:21:26.850> we<00:21:27.029> solve<00:21:27.270> all 00:21:27.440 --> 00:21:27.450 align:start position:0% your new tabs and this way we solve all 00:21:27.450 --> 00:21:30.799 align:start position:0% your new tabs and this way we solve all kind<00:21:27.779> of<00:21:28.429> usability<00:21:29.429> problems<00:21:30.090> and<00:21:30.360> security 00:21:30.799 --> 00:21:30.809 align:start position:0% kind of usability problems and security 00:21:30.809 --> 00:21:33.500 align:start position:0% kind of usability problems and security problems<00:21:31.169> at<00:21:31.289> the<00:21:31.380> same<00:21:31.559> time<00:21:31.799> so<00:21:32.520> that<00:21:33.210> was<00:21:33.480> a 00:21:33.500 --> 00:21:33.510 align:start position:0% problems at the same time so that was a 00:21:33.510 --> 00:21:35.120 align:start position:0% problems at the same time so that was a short<00:21:33.899> presentation<00:21:34.049> of<00:21:34.529> where<00:21:34.740> we<00:21:34.860> are<00:21:34.950> today 00:21:35.120 --> 00:21:35.130 align:start position:0% short presentation of where we are today 00:21:35.130 --> 00:21:37.760 align:start position:0% short presentation of where we are today I<00:21:35.760> wanted<00:21:36.390> to<00:21:36.480> publish<00:21:36.779> some<00:21:36.990> code<00:21:37.289> but<00:21:37.590> we 00:21:37.760 --> 00:21:37.770 align:start position:0% I wanted to publish some code but we 00:21:37.770 --> 00:21:39.590 align:start position:0% I wanted to publish some code but we want<00:21:37.980> to<00:21:38.100> make<00:21:38.220> sure<00:21:38.250> that<00:21:38.640> security<00:21:38.820> wise<00:21:39.360> we 00:21:39.590 --> 00:21:39.600 align:start position:0% want to make sure that security wise we 00:21:39.600 --> 00:21:41.810 align:start position:0% want to make sure that security wise we feel<00:21:39.809> comfortable<00:21:39.960> with<00:21:40.470> letting<00:21:40.919> people<00:21:41.159> put 00:21:41.810 --> 00:21:41.820 align:start position:0% feel comfortable with letting people put 00:21:41.820 --> 00:21:45.350 align:start position:0% feel comfortable with letting people put real<00:21:42.419> money<00:21:42.450> on<00:21:42.840> it<00:21:42.960> and<00:21:43.200> test<00:21:43.980> it<00:21:44.130> so<00:21:44.850> what<00:21:45.330> we 00:21:45.350 --> 00:21:45.360 align:start position:0% real money on it and test it so what we 00:21:45.360 --> 00:21:47.419 align:start position:0% real money on it and test it so what we will<00:21:45.600> do<00:21:45.809> is<00:21:46.049> that<00:21:46.230> in<00:21:46.409> the<00:21:46.559> coming<00:21:46.890> months<00:21:47.220> we 00:21:47.419 --> 00:21:47.429 align:start position:0% will do is that in the coming months we 00:21:47.429 --> 00:21:50.090 align:start position:0% will do is that in the coming months we will<00:21:47.730> first<00:21:48.059> do<00:21:48.419> it<00:21:48.690> yet<00:21:48.960> so<00:21:49.350> we<00:21:49.529> will<00:21:49.679> publish 00:21:50.090 --> 00:21:50.100 align:start position:0% will first do it yet so we will publish 00:21:50.100 --> 00:21:52.250 align:start position:0% will first do it yet so we will publish some<00:21:50.399> code<00:21:50.669> with<00:21:50.940> some<00:21:51.240> material<00:21:51.779> in<00:21:51.929> it<00:21:52.049> and 00:21:52.250 --> 00:21:52.260 align:start position:0% some code with some material in it and 00:21:52.260 --> 00:21:55.370 align:start position:0% some code with some material in it and we<00:21:52.380> will<00:21:52.529> let<00:21:52.679> people<00:21:53.039> try<00:21:53.309> to<00:21:53.370> get<00:21:54.120> there<00:21:54.600> so 00:21:55.370 --> 00:21:55.380 align:start position:0% we will let people try to get there so 00:21:55.380 --> 00:21:57.529 align:start position:0% we will let people try to get there so the<00:21:55.590> good<00:21:55.919> thing<00:21:56.190> is<00:21:56.639> that<00:21:56.669> they<00:21:56.970> shouldn't<00:21:57.389> be 00:21:57.529 --> 00:21:57.539 align:start position:0% the good thing is that they shouldn't be 00:21:57.539 --> 00:21:58.279 align:start position:0% the good thing is that they shouldn't be able<00:21:57.600> to<00:21:57.750> do<00:21:57.960> it 00:21:58.279 --> 00:21:58.289 align:start position:0% able to do it 00:21:58.289 --> 00:21:59.410 align:start position:0% able to do it so<00:21:58.559> if<00:21:58.830> people 00:21:59.410 --> 00:21:59.420 align:start position:0% so if people 00:21:59.420 --> 00:22:02.170 align:start position:0% so if people to<00:21:59.720> do<00:21:59.840> it<00:21:59.990> then<00:22:00.230> we<00:22:00.410> will<00:22:00.560> iterate<00:22:01.030> we<00:22:02.030> will 00:22:02.170 --> 00:22:02.180 align:start position:0% to do it then we will iterate we will 00:22:02.180 --> 00:22:04.570 align:start position:0% to do it then we will iterate we will publish<00:22:02.450> a<00:22:02.660> very<00:22:03.020> detailed<00:22:03.320> test<00:22:03.920> report<00:22:04.370> of 00:22:04.570 --> 00:22:04.580 align:start position:0% publish a very detailed test report of 00:22:04.580 --> 00:22:06.340 align:start position:0% publish a very detailed test report of everything<00:22:05.120> we<00:22:05.240> did<00:22:05.360> with<00:22:05.660> the<00:22:05.750> wallet<00:22:05.960> and 00:22:06.340 --> 00:22:06.350 align:start position:0% everything we did with the wallet and 00:22:06.350 --> 00:22:08.110 align:start position:0% everything we did with the wallet and when<00:22:06.710> we<00:22:06.860> are<00:22:06.950> comfortable<00:22:07.400> with<00:22:07.610> that<00:22:07.820> so 00:22:08.110 --> 00:22:08.120 align:start position:0% when we are comfortable with that so 00:22:08.120 --> 00:22:10.750 align:start position:0% when we are comfortable with that so that<00:22:08.330> should<00:22:08.510> be<00:22:08.540> during<00:22:09.320> q1<00:22:09.560> of<00:22:09.710> next<00:22:10.100> year<00:22:10.250> we 00:22:10.750 --> 00:22:10.760 align:start position:0% that should be during q1 of next year we 00:22:10.760 --> 00:22:12.940 align:start position:0% that should be during q1 of next year we will<00:22:10.880> release<00:22:11.180> our<00:22:11.300> SDK<00:22:12.020> and<00:22:12.260> that<00:22:12.560> will<00:22:12.770> let 00:22:12.940 --> 00:22:12.950 align:start position:0% will release our SDK and that will let 00:22:12.950 --> 00:22:15.670 align:start position:0% will release our SDK and that will let people<00:22:13.400> download<00:22:14.110> how<00:22:15.110> do<00:22:15.170> our<00:22:15.290> wallets 00:22:15.670 --> 00:22:15.680 align:start position:0% people download how do our wallets 00:22:15.680 --> 00:22:17.530 align:start position:0% people download how do our wallets technically<00:22:16.400> and<00:22:16.610> play<00:22:17.180> with<00:22:17.360> their<00:22:17.480> own 00:22:17.530 --> 00:22:17.540 align:start position:0% technically and play with their own 00:22:17.540 --> 00:22:28.210 align:start position:0% technically and play with their own applications<00:22:18.850> so<00:22:19.850> that's<00:22:20.180> it<00:22:20.330> for<00:22:20.510> me<00:22:20.660> I<00:22:27.220> have 00:22:28.210 --> 00:22:28.220 align:start position:0% applications so that's it for me I have 00:22:28.220 --> 00:22:33.670 align:start position:0% applications so that's it for me I have a<00:22:28.250> question<00:22:28.760> so<00:22:30.340> using<00:22:31.340> this<00:22:31.580> PTD<00:22:32.150> API<00:22:32.680> how 00:22:33.670 --> 00:22:33.680 align:start position:0% a question so using this PTD API how 00:22:33.680 --> 00:22:35.500 align:start position:0% a question so using this PTD API how does<00:22:33.860> the<00:22:34.010> user<00:22:34.190> now<00:22:34.520> that<00:22:34.910> whatever<00:22:35.180> is 00:22:35.500 --> 00:22:35.510 align:start position:0% does the user now that whatever is 00:22:35.510 --> 00:22:37.930 align:start position:0% does the user now that whatever is displayed<00:22:35.930> on<00:22:35.960> the<00:22:36.140> screen<00:22:36.350> this<00:22:37.040> chef<00:22:37.460> outfit 00:22:37.930 --> 00:22:37.940 align:start position:0% displayed on the screen this chef outfit 00:22:37.940 --> 00:22:40.330 align:start position:0% displayed on the screen this chef outfit PIN<00:22:38.390> pad<00:22:38.570> as<00:22:38.750> I<00:22:38.840> understand<00:22:39.380> how<00:22:40.040> does<00:22:40.100> the 00:22:40.330 --> 00:22:40.340 align:start position:0% PIN pad as I understand how does the 00:22:40.340 --> 00:22:42.040 align:start position:0% PIN pad as I understand how does the user<00:22:40.460> now<00:22:40.700> it<00:22:40.880> really<00:22:41.090> is<00:22:41.210> displayed<00:22:41.870> by 00:22:42.040 --> 00:22:42.050 align:start position:0% user now it really is displayed by 00:22:42.050 --> 00:22:45.340 align:start position:0% user now it really is displayed by either<00:22:42.170> just<00:22:42.830> a<00:22:42.950> tank<00:22:43.130> life<00:22:43.400> so<00:22:44.180> so<00:22:45.110> how<00:22:45.290> does 00:22:45.340 --> 00:22:45.350 align:start position:0% either just a tank life so so how does 00:22:45.350 --> 00:22:47.830 align:start position:0% either just a tank life so so how does the<00:22:45.530> unit<00:22:45.860> know<00:22:46.130> that<00:22:46.430> that<00:22:47.270> the<00:22:47.390> screen<00:22:47.690> is 00:22:47.830 --> 00:22:47.840 align:start position:0% the unit know that that the screen is 00:22:47.840 --> 00:22:49.510 align:start position:0% the unit know that that the screen is really<00:22:47.870> I<00:22:48.410> mean<00:22:48.530> that's<00:22:48.740> what<00:22:49.010> is<00:22:49.160> this<00:22:49.310> place 00:22:49.510 --> 00:22:49.520 align:start position:0% really I mean that's what is this place 00:22:49.520 --> 00:22:51.280 align:start position:0% really I mean that's what is this place we<00:22:49.760> display<00:22:50.120> by<00:22:50.270> the<00:22:50.330> drive<00:22:50.690> you<00:22:50.810> don't<00:22:51.020> really 00:22:51.280 --> 00:22:51.290 align:start position:0% we display by the drive you don't really 00:22:51.290 --> 00:22:53.020 align:start position:0% we display by the drive you don't really have<00:22:51.560> a<00:22:51.620> way<00:22:51.830> to<00:22:51.860> know<00:22:52.160> that<00:22:52.190> because<00:22:52.730> this<00:22:52.880> can 00:22:53.020 --> 00:22:53.030 align:start position:0% have a way to know that because this can 00:22:53.030 --> 00:22:55.330 align:start position:0% have a way to know that because this can still<00:22:53.270> be<00:22:53.330> food<00:22:53.690> by<00:22:53.870> food<00:22:54.350> by<00:22:54.530> malware<00:22:54.980> so<00:22:55.190> the 00:22:55.330 --> 00:22:55.340 align:start position:0% still be food by food by malware so the 00:22:55.340 --> 00:22:57.160 align:start position:0% still be food by food by malware so the idea<00:22:55.640> that<00:22:55.670> you<00:22:55.970> will<00:22:56.060> asks<00:22:56.540> the<00:22:56.660> user<00:22:56.810> to 00:22:57.160 --> 00:22:57.170 align:start position:0% idea that you will asks the user to 00:22:57.170 --> 00:22:59.350 align:start position:0% idea that you will asks the user to confirm<00:22:57.590> back<00:22:58.040> something<00:22:58.460> that<00:22:58.670> is<00:22:59.000> displayed 00:22:59.350 --> 00:22:59.360 align:start position:0% confirm back something that is displayed 00:22:59.360 --> 00:23:01.480 align:start position:0% confirm back something that is displayed on<00:22:59.390> screen<00:22:59.780> so<00:23:00.350> for<00:23:00.560> example<00:23:00.890> if<00:23:00.980> you<00:23:01.100> display 00:23:01.480 --> 00:23:01.490 align:start position:0% on screen so for example if you display 00:23:01.490 --> 00:23:03.550 align:start position:0% on screen so for example if you display an<00:23:01.610> amount<00:23:01.910> you<00:23:02.180> will<00:23:02.300> ask<00:23:02.510> the<00:23:02.870> user<00:23:02.900> to<00:23:03.200> type 00:23:03.550 --> 00:23:03.560 align:start position:0% an amount you will ask the user to type 00:23:03.560 --> 00:23:05.710 align:start position:0% an amount you will ask the user to type the<00:23:03.800> amount<00:23:04.070> again<00:23:04.310> using<00:23:04.760> the<00:23:04.940> rat<00:23:05.150> pin<00:23:05.480> pad 00:23:05.710 --> 00:23:05.720 align:start position:0% the amount again using the rat pin pad 00:23:05.720 --> 00:23:08.020 align:start position:0% the amount again using the rat pin pad so<00:23:05.960> using<00:23:06.260> the<00:23:06.380> scramble<00:23:06.770> pin<00:23:06.920> pad<00:23:07.160> and<00:23:07.370> you 00:23:08.020 --> 00:23:08.030 align:start position:0% so using the scramble pin pad and you 00:23:08.030 --> 00:23:09.940 align:start position:0% so using the scramble pin pad and you will<00:23:08.180> collect<00:23:08.600> that<00:23:08.660> back<00:23:09.050> on<00:23:09.230> the<00:23:09.380> Enclave<00:23:09.740> so 00:23:09.940 --> 00:23:09.950 align:start position:0% will collect that back on the Enclave so 00:23:09.950 --> 00:23:11.860 align:start position:0% will collect that back on the Enclave so if<00:23:10.130> the<00:23:10.370> user<00:23:10.520> is<00:23:10.820> able<00:23:10.940> to<00:23:11.180> type<00:23:11.390> that<00:23:11.600> it 00:23:11.860 --> 00:23:11.870 align:start position:0% if the user is able to type that it 00:23:11.870 --> 00:23:13.990 align:start position:0% if the user is able to type that it means<00:23:12.110> that<00:23:12.290> well<00:23:12.920> what<00:23:13.370> is<00:23:13.520> displayed<00:23:13.700> is 00:23:13.990 --> 00:23:14.000 align:start position:0% means that well what is displayed is 00:23:14.000 --> 00:23:15.730 align:start position:0% means that well what is displayed is correct<00:23:14.330> basically<00:23:14.870> so<00:23:15.080> you<00:23:15.110> will<00:23:15.380> ask<00:23:15.530> the 00:23:15.730 --> 00:23:15.740 align:start position:0% correct basically so you will ask the 00:23:15.740 --> 00:23:17.950 align:start position:0% correct basically so you will ask the user<00:23:15.920> to<00:23:16.040> confirm<00:23:16.580> back<00:23:16.820> by<00:23:17.330> entering<00:23:17.840> again 00:23:17.950 --> 00:23:17.960 align:start position:0% user to confirm back by entering again 00:23:17.960 --> 00:23:22.330 align:start position:0% user to confirm back by entering again what<00:23:18.380> was<00:23:18.560> displayed<00:23:18.920> on<00:23:19.040> screen<00:23:19.310> but<00:23:21.220> just<00:23:22.220> to 00:23:22.330 --> 00:23:22.340 align:start position:0% what was displayed on screen but just to 00:23:22.340 --> 00:23:26.050 align:start position:0% what was displayed on screen but just to clarify<00:23:22.520> do<00:23:23.030> you<00:23:23.270> also<00:23:23.480> use<00:23:24.370> additional<00:23:25.370> LCD 00:23:26.050 --> 00:23:26.060 align:start position:0% clarify do you also use additional LCD 00:23:26.060 --> 00:23:28.060 align:start position:0% clarify do you also use additional LCD screen<00:23:26.390> on<00:23:26.600> your<00:23:26.750> letter<00:23:27.050> no<00:23:27.530> you<00:23:27.590> don't<00:23:27.950> you 00:23:28.060 --> 00:23:28.070 align:start position:0% screen on your letter no you don't you 00:23:28.070 --> 00:23:29.740 align:start position:0% screen on your letter no you don't you just<00:23:28.220> use<00:23:28.400> you<00:23:28.820> just<00:23:29.000> everything<00:23:29.420> cuz<00:23:29.600> in 00:23:29.740 --> 00:23:29.750 align:start position:0% just use you just everything cuz in 00:23:29.750 --> 00:23:33.970 align:start position:0% just use you just everything cuz in software<00:23:30.200> correct<00:23:30.680> in<00:23:31.250> this<00:23:31.460> picture<00:23:31.850> so<00:23:32.980> host 00:23:33.970 --> 00:23:33.980 align:start position:0% software correct in this picture so host 00:23:33.980 --> 00:23:36.310 align:start position:0% software correct in this picture so host can<00:23:34.340> intercept<00:23:34.970> your<00:23:35.090> keyboard<00:23:35.630> as<00:23:35.930> well<00:23:35.990> as 00:23:36.310 --> 00:23:36.320 align:start position:0% can intercept your keyboard as well as 00:23:36.320 --> 00:23:39.040 align:start position:0% can intercept your keyboard as well as your<00:23:36.500> display<00:23:36.980> yes<00:23:37.520> so<00:23:38.270> I<00:23:38.300> don't<00:23:38.570> see<00:23:38.840> how<00:23:38.990> you 00:23:39.040 --> 00:23:39.050 align:start position:0% your display yes so I don't see how you 00:23:39.050 --> 00:23:41.320 align:start position:0% your display yes so I don't see how you can<00:23:39.260> use<00:23:39.440> either<00:23:40.220> way<00:23:40.580> to<00:23:40.640> verify<00:23:41.060> the 00:23:41.320 --> 00:23:41.330 align:start position:0% can use either way to verify the 00:23:41.330 --> 00:23:44.590 align:start position:0% can use either way to verify the correctness<00:23:41.930> of<00:23:42.140> the<00:23:42.290> other<00:23:42.410> one<00:23:42.650> so<00:23:43.390> the<00:23:44.390> host 00:23:44.590 --> 00:23:44.600 align:start position:0% correctness of the other one so the host 00:23:44.600 --> 00:23:47.320 align:start position:0% correctness of the other one so the host and<00:23:44.930> the<00:23:45.260> host<00:23:45.290> can<00:23:45.770> inter<00:23:46.370> in<00:23:46.580> in<00:23:46.970> that<00:23:47.120> case 00:23:47.320 --> 00:23:47.330 align:start position:0% and the host can inter in in that case 00:23:47.330 --> 00:23:49.090 align:start position:0% and the host can inter in in that case the<00:23:47.510> host<00:23:47.660> can<00:23:47.840> intercept<00:23:48.320> the<00:23:48.440> display<00:23:48.830> so 00:23:49.090 --> 00:23:49.100 align:start position:0% the host can intercept the display so 00:23:49.100 --> 00:23:51.220 align:start position:0% the host can intercept the display so the<00:23:49.250> host<00:23:49.430> cannot<00:23:49.760> the<00:23:50.180> ID<00:23:50.360> that<00:23:50.630> the<00:23:50.780> host<00:23:51.020> can 00:23:51.220 --> 00:23:51.230 align:start position:0% the host cannot the ID that the host can 00:23:51.230 --> 00:23:53.440 align:start position:0% the host cannot the ID that the host can display<00:23:51.680> something<00:23:51.920> on<00:23:52.250> top<00:23:52.520> of<00:23:52.730> on<00:23:52.970> what<00:23:53.300> is 00:23:53.440 --> 00:23:53.450 align:start position:0% display something on top of on what is 00:23:53.450 --> 00:23:55.930 align:start position:0% display something on top of on what is displayed<00:23:53.930> but<00:23:54.500> with<00:23:54.710> PTT<00:23:55.160> the<00:23:55.220> host<00:23:55.610> cannot 00:23:55.930 --> 00:23:55.940 align:start position:0% displayed but with PTT the host cannot 00:23:55.940 --> 00:23:59.620 align:start position:0% displayed but with PTT the host cannot see<00:23:56.330> what<00:23:56.720> is<00:23:56.870> displayed<00:23:57.400> so<00:23:58.400> you<00:23:58.460> can<00:23:58.790> prevent 00:23:59.620 --> 00:23:59.630 align:start position:0% see what is displayed so you can prevent 00:23:59.630 --> 00:24:02.710 align:start position:0% see what is displayed so you can prevent the<00:23:59.810> house<00:24:00.020> from<00:24:00.370> simulating<00:24:01.370> everything<00:24:02.000> you 00:24:02.710 --> 00:24:02.720 align:start position:0% the house from simulating everything you 00:24:02.720 --> 00:24:04.690 align:start position:0% the house from simulating everything you can<00:24:02.930> so<00:24:03.140> you<00:24:03.170> can<00:24:03.530> simulate<00:24:03.800> everything<00:24:04.490> but 00:24:04.690 --> 00:24:04.700 align:start position:0% can so you can simulate everything but 00:24:04.700 --> 00:24:06.790 align:start position:0% can so you can simulate everything but since<00:24:05.300> the<00:24:05.510> host<00:24:05.810> can't<00:24:06.230> know<00:24:06.470> what<00:24:06.680> is 00:24:06.790 --> 00:24:06.800 align:start position:0% since the host can't know what is 00:24:06.800 --> 00:24:07.330 align:start position:0% since the host can't know what is displayed 00:24:07.330 --> 00:24:07.340 align:start position:0% displayed 00:24:07.340 --> 00:24:08.740 align:start position:0% displayed let's<00:24:07.460> say<00:24:07.610> you<00:24:07.670> display<00:24:08.120> the<00:24:08.300> mount<00:24:08.480> for 00:24:08.740 --> 00:24:08.750 align:start position:0% let's say you display the mount for 00:24:08.750 --> 00:24:11.080 align:start position:0% let's say you display the mount for example<00:24:09.140> in<00:24:09.950> that<00:24:10.010> case<00:24:10.220> the<00:24:10.610> host<00:24:10.820> can 00:24:11.080 --> 00:24:11.090 align:start position:0% example in that case the host can 00:24:11.090 --> 00:24:12.140 align:start position:0% example in that case the host can display<00:24:11.510> another<00:24:11.840> one 00:24:12.140 --> 00:24:12.150 align:start position:0% display another one 00:24:12.150 --> 00:24:14.330 align:start position:0% display another one so<00:24:12.450> the<00:24:12.600> host<00:24:12.810> can<00:24:13.080> say<00:24:13.350> okay<00:24:13.680> you<00:24:13.740> wanted<00:24:14.220> to 00:24:14.330 --> 00:24:14.340 align:start position:0% so the host can say okay you wanted to 00:24:14.340 --> 00:24:18.320 align:start position:0% so the host can say okay you wanted to pay<00:24:14.550> $1<00:24:15.420> I'm<00:24:15.780> 180<00:24:16.530> sorry<00:24:16.980> I'm<00:24:17.700> going<00:24:17.940> to<00:24:18.090> tell 00:24:18.320 --> 00:24:18.330 align:start position:0% pay $1 I'm 180 sorry I'm going to tell 00:24:18.330 --> 00:24:20.990 align:start position:0% pay $1 I'm 180 sorry I'm going to tell you<00:24:18.450> are<00:24:18.570> going<00:24:18.780> to<00:24:18.900> pay<00:24:19.080> 1000<00:24:19.650> theta<00:24:19.850> so<00:24:20.850> the 00:24:20.990 --> 00:24:21.000 align:start position:0% you are going to pay 1000 theta so the 00:24:21.000 --> 00:24:23.240 align:start position:0% you are going to pay 1000 theta so the horse<00:24:21.210> can<00:24:21.270> do<00:24:21.540> that<00:24:21.720> but<00:24:22.380> in<00:24:22.620> this<00:24:22.830> case<00:24:22.890> you 00:24:23.240 --> 00:24:23.250 align:start position:0% horse can do that but in this case you 00:24:23.250 --> 00:24:26.690 align:start position:0% horse can do that but in this case you can<00:24:23.400> ask<00:24:23.640> the<00:24:24.510> user<00:24:24.810> to<00:24:25.350> type<00:24:25.650> it<00:24:25.890> back<00:24:26.130> using 00:24:26.690 --> 00:24:26.700 align:start position:0% can ask the user to type it back using 00:24:26.700 --> 00:24:28.790 align:start position:0% can ask the user to type it back using those<00:24:27.000> using<00:24:27.420> those<00:24:27.570> converting<00:24:28.110> pad<00:24:28.320> so<00:24:28.560> that 00:24:28.790 --> 00:24:28.800 align:start position:0% those using those converting pad so that 00:24:28.800 --> 00:24:31.550 align:start position:0% those using those converting pad so that host<00:24:29.370> cannot<00:24:29.700> read<00:24:30.060> either<00:24:30.360> because<00:24:31.200> in<00:24:31.380> the 00:24:31.550 --> 00:24:31.560 align:start position:0% host cannot read either because in the 00:24:31.560 --> 00:24:33.380 align:start position:0% host cannot read either because in the host<00:24:32.010> cannot<00:24:32.310> read<00:24:32.580> what's<00:24:32.790> in<00:24:32.940> the<00:24:33.060> display 00:24:33.380 --> 00:24:33.390 align:start position:0% host cannot read what's in the display 00:24:33.390 --> 00:24:35.450 align:start position:0% host cannot read what's in the display so<00:24:33.930> if<00:24:34.110> you<00:24:34.290> have<00:24:34.410> a<00:24:34.440> stronger<00:24:34.680> PIN<00:24:34.980> pad<00:24:35.190> and 00:24:35.450 --> 00:24:35.460 align:start position:0% so if you have a stronger PIN pad and 00:24:35.460 --> 00:24:38.180 align:start position:0% so if you have a stronger PIN pad and you<00:24:35.550> ask<00:24:35.790> the<00:24:36.420> user<00:24:36.660> to<00:24:36.780> type<00:24:37.170> back<00:24:37.470> basically 00:24:38.180 --> 00:24:38.190 align:start position:0% you ask the user to type back basically 00:24:38.190 --> 00:24:41.480 align:start position:0% you ask the user to type back basically that<00:24:38.550> the<00:24:38.670> amount<00:24:38.970> was<00:24:39.180> one<00:24:39.420> and<00:24:39.750> not<00:24:39.990> 1,000<00:24:40.590> if 00:24:41.480 --> 00:24:41.490 align:start position:0% that the amount was one and not 1,000 if 00:24:41.490 --> 00:24:44.480 align:start position:0% that the amount was one and not 1,000 if the<00:24:41.760> user<00:24:41.970> type<00:24:42.300> one<00:24:43.020> and<00:24:43.230> confirm<00:24:43.770> I<00:24:44.010> mean<00:24:44.310> you 00:24:44.480 --> 00:24:44.490 align:start position:0% the user type one and confirm I mean you 00:24:44.490 --> 00:24:46.990 align:start position:0% the user type one and confirm I mean you know<00:24:44.670> that<00:24:44.910> well<00:24:45.420> you<00:24:45.690> are<00:24:45.810> paying<00:24:46.050> one 00:24:46.990 --> 00:24:47.000 align:start position:0% know that well you are paying one 00:24:47.000 --> 00:24:49.460 align:start position:0% know that well you are paying one another<00:24:48.000> question<00:24:48.330> do<00:24:48.690> you<00:24:48.810> use<00:24:48.930> remote<00:24:49.290> at 00:24:49.460 --> 00:24:49.470 align:start position:0% another question do you use remote at 00:24:49.470 --> 00:24:52.850 align:start position:0% another question do you use remote at the<00:24:49.560> station<00:24:49.980> at<00:24:50.130> all<00:24:50.310> for<00:24:50.670> your<00:24:50.790> solution<00:24:51.860> we 00:24:52.850 --> 00:24:52.860 align:start position:0% the station at all for your solution we 00:24:52.860 --> 00:24:54.260 align:start position:0% the station at all for your solution we are<00:24:52.950> using<00:24:53.100> remote<00:24:53.520> attestation<00:24:53.910> to 00:24:54.260 --> 00:24:54.270 align:start position:0% are using remote attestation to 00:24:54.270 --> 00:24:55.850 align:start position:0% are using remote attestation to guarantee<00:24:54.690> that<00:24:54.720> the<00:24:54.960> on<00:24:55.050> drive<00:24:55.290> is<00:24:55.470> genuine 00:24:55.850 --> 00:24:55.860 align:start position:0% guarantee that the on drive is genuine 00:24:55.860 --> 00:24:58.690 align:start position:0% guarantee that the on drive is genuine yes<00:24:56.130> okay<00:24:56.610> so<00:24:56.720> what<00:24:57.720> do<00:24:57.810> you<00:24:57.900> think<00:24:58.140> about 00:24:58.690 --> 00:24:58.700 align:start position:0% yes okay so what do you think about 00:24:58.700 --> 00:25:01.910 align:start position:0% yes okay so what do you think about Intel<00:24:59.700> forcing<00:25:00.660> you<00:25:00.840> to<00:25:00.900> use<00:25:01.200> the<00:25:01.380> centralized 00:25:01.910 --> 00:25:01.920 align:start position:0% Intel forcing you to use the centralized 00:25:01.920 --> 00:25:04.910 align:start position:0% Intel forcing you to use the centralized service<00:25:02.760> for<00:25:02.970> remote<00:25:03.210> attestation<00:25:03.660> so<00:25:04.500> for 00:25:04.910 --> 00:25:04.920 align:start position:0% service for remote attestation so for 00:25:04.920 --> 00:25:06.950 align:start position:0% service for remote attestation so for the<00:25:05.040> time<00:25:05.280> being<00:25:05.310> we<00:25:05.700> will<00:25:05.730> I<00:25:05.970> we<00:25:06.330> rely<00:25:06.600> on<00:25:06.630> it 00:25:06.950 --> 00:25:06.960 align:start position:0% the time being we will I we rely on it 00:25:06.960 --> 00:25:09.230 align:start position:0% the time being we will I we rely on it then<00:25:07.680> we<00:25:07.860> will<00:25:07.980> Ino<00:25:08.370> on<00:25:08.610> attestation<00:25:09.030> which 00:25:09.230 --> 00:25:09.240 align:start position:0% then we will Ino on attestation which 00:25:09.240 --> 00:25:11.510 align:start position:0% then we will Ino on attestation which can<00:25:09.570> be<00:25:09.720> very<00:25:09.930> fine<00:25:10.110> on<00:25:10.260> chain<00:25:10.530> I<00:25:10.770> think<00:25:11.400> that 00:25:11.510 --> 00:25:11.520 align:start position:0% can be very fine on chain I think that 00:25:11.520 --> 00:25:13.280 align:start position:0% can be very fine on chain I think that Intel<00:25:11.880> is<00:25:12.000> working<00:25:12.360> on<00:25:12.480> more<00:25:12.660> flexibility 00:25:13.280 --> 00:25:13.290 align:start position:0% Intel is working on more flexibility 00:25:13.290 --> 00:25:15.410 align:start position:0% Intel is working on more flexibility station<00:25:13.680> schemes<00:25:14.010> that<00:25:14.610> will<00:25:14.790> not<00:25:15.000> be<00:25:15.180> that 00:25:15.410 --> 00:25:15.420 align:start position:0% station schemes that will not be that 00:25:15.420 --> 00:25:17.810 align:start position:0% station schemes that will not be that summarized<00:25:16.050> in<00:25:16.230> the<00:25:16.350> future<00:25:16.680> which<00:25:17.520> would<00:25:17.700> you 00:25:17.810 --> 00:25:17.820 align:start position:0% summarized in the future which would you 00:25:17.820 --> 00:25:20.900 align:start position:0% summarized in the future which would you said<00:25:18.060> is<00:25:18.210> critical<00:25:18.780> for<00:25:18.960> you<00:25:19.110> to<00:25:19.140> have<00:25:19.440> is<00:25:19.910> this 00:25:20.900 --> 00:25:20.910 align:start position:0% said is critical for you to have is this 00:25:20.910 --> 00:25:25.220 align:start position:0% said is critical for you to have is this decentralized<00:25:23.180> like<00:25:24.180> I<00:25:24.390> would<00:25:24.630> like<00:25:24.840> to<00:25:25.020> see 00:25:25.220 --> 00:25:25.230 align:start position:0% decentralized like I would like to see 00:25:25.230 --> 00:25:26.690 align:start position:0% decentralized like I would like to see centralized<00:25:25.920> but<00:25:26.160> for<00:25:26.370> the<00:25:26.460> time<00:25:26.670> being 00:25:26.690 --> 00:25:26.700 align:start position:0% centralized but for the time being 00:25:26.700 --> 00:25:29.480 align:start position:0% centralized but for the time being relying<00:25:27.420> on<00:25:27.570> IES<00:25:28.260> also<00:25:28.680> puts<00:25:28.860> weapons<00:25:29.310> and 00:25:29.480 --> 00:25:29.490 align:start position:0% relying on IES also puts weapons and 00:25:29.490 --> 00:25:31.520 align:start position:0% relying on IES also puts weapons and relying<00:25:29.790> on<00:25:29.970> our<00:25:30.120> own<00:25:30.360> a<00:25:30.390> decision<00:25:30.900> scheme<00:25:31.230> for 00:25:31.520 --> 00:25:31.530 align:start position:0% relying on our own a decision scheme for 00:25:31.530 --> 00:25:33.200 align:start position:0% relying on our own a decision scheme for our<00:25:31.800> scripts<00:25:32.340> that<00:25:32.370> we<00:25:32.670> execute<00:25:32.880> in<00:25:33.180> the 00:25:33.200 --> 00:25:33.210 align:start position:0% our scripts that we execute in the 00:25:33.210 --> 00:25:39.140 align:start position:0% our scripts that we execute in the Enclave<00:25:33.660> is<00:25:33.810> good<00:25:33.990> enough<00:25:37.460> thanks<00:25:38.460> Nicholas<00:25:38.850> I 00:25:39.140 --> 00:25:39.150 align:start position:0% Enclave is good enough thanks Nicholas I 00:25:39.150 --> 00:25:45.310 align:start position:0% Enclave is good enough thanks Nicholas I think<00:25:39.830> we're<00:25:40.830> done<00:25:40.950> with<00:25:41.010> the<00:25:41.220> time<00:25:41.400> thank<00:25:42.360> you 00:25:45.310 --> 00:25:45.320 align:start position:0% 00:25:45.320 --> 00:25:54.470 align:start position:0% so<00:25:46.320> the<00:25:46.440> next<00:25:46.910> up<00:25:47.910> is<00:25:48.410> Sid<00:25:49.550> from<00:25:50.550> we've<00:25:53.480> seen 00:25:54.470 --> 00:25:54.480 align:start position:0% so the next up is Sid from we've seen 00:25:54.480 --> 00:25:57.170 align:start position:0% so the next up is Sid from we've seen you<00:25:54.870> can<00:25:55.020> call<00:25:55.200> me<00:25:55.290> sir<00:25:55.440> as<00:25:55.590> well<00:25:56.030> the<00:25:57.030> lead 00:25:57.170 --> 00:25:57.180 align:start position:0% you can call me sir as well the lead 00:25:57.180 --> 00:26:00.200 align:start position:0% you can call me sir as well the lead bench<00:25:57.420> architect<00:25:57.930> with<00:25:58.050> we've<00:25:58.460> it's<00:25:59.460> a<00:25:59.580> it's<00:26:00.120> a 00:26:00.200 --> 00:26:00.210 align:start position:0% bench architect with we've it's a it's a 00:26:00.210 --> 00:26:03.800 align:start position:0% bench architect with we've it's a it's a deep<00:26:00.360> tech<00:26:00.570> company<00:26:00.990> out<00:26:01.200> of<00:26:01.380> Berlin<00:26:02.190> and<00:26:02.810> we 00:26:03.800 --> 00:26:03.810 align:start position:0% deep tech company out of Berlin and we 00:26:03.810 --> 00:26:06.500 align:start position:0% deep tech company out of Berlin and we are<00:26:04.580> revolving<00:26:05.580> around<00:26:05.670> the<00:26:05.940> technologies<00:26:06.480> of 00:26:06.500 --> 00:26:06.510 align:start position:0% are revolving around the technologies of 00:26:06.510 --> 00:26:09.520 align:start position:0% are revolving around the technologies of data<00:26:07.470> attestation<00:26:07.980> data<00:26:08.430> validation<00:26:09.090> and 00:26:09.520 --> 00:26:09.530 align:start position:0% data attestation data validation and 00:26:09.530 --> 00:26:13.040 align:start position:0% data attestation data validation and data<00:26:10.530> communication<00:26:11.750> using<00:26:12.750> the<00:26:12.840> powerful 00:26:13.040 --> 00:26:13.050 align:start position:0% data communication using the powerful 00:26:13.050 --> 00:26:15.670 align:start position:0% data communication using the powerful paradigms<00:26:13.740> of<00:26:14.070> IOT<00:26:14.550> and<00:26:14.760> blockchain 00:26:15.670 --> 00:26:15.680 align:start position:0% paradigms of IOT and blockchain 00:26:15.680 --> 00:26:20.060 align:start position:0% paradigms of IOT and blockchain unfortunately<00:26:17.450> my<00:26:18.450> CTO<00:26:18.920> professor<00:26:19.920> Sebastian 00:26:20.060 --> 00:26:20.070 align:start position:0% unfortunately my CTO professor Sebastian 00:26:20.070 --> 00:26:20.720 align:start position:0% unfortunately my CTO professor Sebastian gyq 00:26:20.720 --> 00:26:20.730 align:start position:0% gyq 00:26:20.730 --> 00:26:22.400 align:start position:0% gyq he<00:26:21.300> was<00:26:21.420> supposed<00:26:21.750> to<00:26:21.780> give<00:26:21.960> the<00:26:22.080> talk<00:26:22.230> today 00:26:22.400 --> 00:26:22.410 align:start position:0% he was supposed to give the talk today 00:26:22.410 --> 00:26:24.860 align:start position:0% he was supposed to give the talk today he<00:26:22.620> couldn't<00:26:22.860> come<00:26:22.950> in<00:26:23.100> so<00:26:23.310> I'm<00:26:23.730> replacing<00:26:24.420> him 00:26:24.860 --> 00:26:24.870 align:start position:0% he couldn't come in so I'm replacing him 00:26:24.870 --> 00:26:25.670 align:start position:0% he couldn't come in so I'm replacing him today 00:26:25.670 --> 00:26:25.680 align:start position:0% today 00:26:25.680 --> 00:26:29.720 align:start position:0% today and<00:26:26.450> the<00:26:27.450> the<00:26:27.900> premise<00:26:28.110> of<00:26:28.680> my<00:26:29.070> talk<00:26:29.490> today 00:26:29.720 --> 00:26:29.730 align:start position:0% and the the premise of my talk today 00:26:29.730 --> 00:26:32.480 align:start position:0% and the the premise of my talk today lies<00:26:30.150> in<00:26:30.870> the<00:26:31.080> foundation<00:26:31.680> of<00:26:31.830> the<00:26:32.130> future<00:26:32.460> I 00:26:32.480 --> 00:26:32.490 align:start position:0% lies in the foundation of the future I 00:26:32.490 --> 00:26:35.060 align:start position:0% lies in the foundation of the future I think<00:26:32.580> we<00:26:32.850> all<00:26:33.000> believe<00:26:33.300> in<00:26:33.560> so<00:26:34.560> it's<00:26:34.800> it's 00:26:35.060 --> 00:26:35.070 align:start position:0% think we all believe in so it's it's 00:26:35.070 --> 00:26:38.240 align:start position:0% think we all believe in so it's it's it's<00:26:35.340> revolving<00:26:35.850> around<00:26:36.620> the<00:26:37.620> building<00:26:37.980> of<00:26:38.130> a 00:26:38.240 --> 00:26:38.250 align:start position:0% it's revolving around the building of a 00:26:38.250 --> 00:26:40.520 align:start position:0% it's revolving around the building of a decentralized<00:26:38.940> machine-to-machine<00:26:39.780> economy 00:26:40.520 --> 00:26:40.530 align:start position:0% decentralized machine-to-machine economy 00:26:40.530 --> 00:26:42.590 align:start position:0% decentralized machine-to-machine economy autonomous<00:26:41.490> machine-to-machine<00:26:41.880> economy 00:26:42.590 --> 00:26:42.600 align:start position:0% autonomous machine-to-machine economy 00:26:42.600 --> 00:26:46.280 align:start position:0% autonomous machine-to-machine economy and<00:26:42.810> how<00:26:43.710> can<00:26:43.770> we<00:26:43.980> use<00:26:44.570> trusted<00:26:45.570> IOT<00:26:45.870> Oracle's 00:26:46.280 --> 00:26:46.290 align:start position:0% and how can we use trusted IOT Oracle's 00:26:46.290 --> 00:26:48.590 align:start position:0% and how can we use trusted IOT Oracle's for<00:26:46.440> that<00:26:46.560> so<00:26:47.340> for<00:26:47.520> starters<00:26:47.940> since<00:26:48.360> we<00:26:48.510> are 00:26:48.590 --> 00:26:48.600 align:start position:0% for that so for starters since we are 00:26:48.600 --> 00:26:52.100 align:start position:0% for that so for starters since we are here<00:26:48.720> so<00:26:49.320> for<00:26:49.470> the<00:26:49.530> etherium<00:26:49.860> Network<00:26:51.110> I'll 00:26:52.100 --> 00:26:52.110 align:start position:0% here so for the etherium Network I'll 00:26:52.110 --> 00:26:58.000 align:start position:0% here so for the etherium Network I'll dive<00:26:52.380> right<00:26:52.920> into<00:26:53.190> it<00:26:53.810> ok<00:26:54.810> so<00:26:55.940> we<00:26:56.940> believe<00:26:57.630> that 00:26:58.000 --> 00:26:58.010 align:start position:0% dive right into it ok so we believe that 00:26:58.010 --> 00:27:01.910 align:start position:0% dive right into it ok so we believe that IOT<00:26:59.010> devices<00:27:00.050> can<00:27:01.050> be<00:27:01.080> good<00:27:01.470> data 00:27:01.910 --> 00:27:01.920 align:start position:0% IOT devices can be good data 00:27:01.920 --> 00:27:06.170 align:start position:0% IOT devices can be good data Oracle's<00:27:02.370> for<00:27:03.150> the<00:27:03.240> etherium<00:27:03.540> network<00:27:05.180> but 00:27:06.170 --> 00:27:06.180 align:start position:0% Oracle's for the etherium network but 00:27:06.180 --> 00:27:07.250 align:start position:0% Oracle's for the etherium network but there<00:27:06.390> are<00:27:06.570> there<00:27:06.780> are<00:27:06.810> two<00:27:06.930> fundamental 00:27:07.250 --> 00:27:07.260 align:start position:0% there are there are two fundamental 00:27:07.260 --> 00:27:10.660 align:start position:0% there are there are two fundamental problems<00:27:08.040> in<00:27:08.160> that<00:27:08.220> there's<00:27:08.670> there's<00:27:09.000> lots<00:27:09.210> of 00:27:10.660 --> 00:27:10.670 align:start position:0% problems in that there's there's lots of 00:27:10.670 --> 00:27:13.790 align:start position:0% problems in that there's there's lots of compromises<00:27:11.670> right<00:27:11.880> now<00:27:12.090> in<00:27:12.660> how<00:27:12.930> IOT<00:27:13.500> devices 00:27:13.790 --> 00:27:13.800 align:start position:0% compromises right now in how IOT devices 00:27:13.800 --> 00:27:17.480 align:start position:0% compromises right now in how IOT devices are<00:27:14.250> so<00:27:15.240> there's<00:27:15.420> lots<00:27:15.660> of<00:27:15.890> attacks<00:27:16.890> possible 00:27:17.480 --> 00:27:17.490 align:start position:0% are so there's lots of attacks possible 00:27:17.490 --> 00:27:19.780 align:start position:0% are so there's lots of attacks possible man-in-the-middle<00:27:18.060> attacks<00:27:18.510> buffer<00:27:19.140> attacks 00:27:19.780 --> 00:27:19.790 align:start position:0% man-in-the-middle attacks buffer attacks 00:27:19.790 --> 00:27:22.430 align:start position:0% man-in-the-middle attacks buffer attacks which<00:27:20.790> which<00:27:21.120> really<00:27:21.630> do<00:27:21.930> not<00:27:22.050> make<00:27:22.320> it 00:27:22.430 --> 00:27:22.440 align:start position:0% which which really do not make it 00:27:22.440 --> 00:27:23.930 align:start position:0% which which really do not make it possible<00:27:22.860> at<00:27:22.950> this<00:27:23.130> moment<00:27:23.310> to<00:27:23.580> make<00:27:23.700> them 00:27:23.930 --> 00:27:23.940 align:start position:0% possible at this moment to make them 00:27:23.940 --> 00:27:27.080 align:start position:0% possible at this moment to make them good<00:27:24.290> Oracle's<00:27:25.290> for<00:27:25.650> the<00:27:25.800> for<00:27:26.670> the<00:27:26.790> blockchain 00:27:27.080 --> 00:27:27.090 align:start position:0% good Oracle's for the for the blockchain 00:27:27.090 --> 00:27:30.140 align:start position:0% good Oracle's for the for the blockchain or<00:27:27.450> for<00:27:27.630> cloud<00:27:27.810> applications<00:27:28.530> and<00:27:28.910> once<00:27:29.910> the 00:27:30.140 --> 00:27:30.150 align:start position:0% or for cloud applications and once the 00:27:30.150 --> 00:27:32.780 align:start position:0% or for cloud applications and once the data<00:27:30.330> has<00:27:30.480> been<00:27:30.660> produced<00:27:31.280> the<00:27:32.280> second<00:27:32.670> layer 00:27:32.780 --> 00:27:32.790 align:start position:0% data has been produced the second layer 00:27:32.790 --> 00:27:34.730 align:start position:0% data has been produced the second layer that<00:27:33.210> the<00:27:33.360> integrity<00:27:33.840> of<00:27:33.960> the<00:27:34.140> data<00:27:34.320> itself 00:27:34.730 --> 00:27:34.740 align:start position:0% that the integrity of the data itself 00:27:34.740 --> 00:27:38.480 align:start position:0% that the integrity of the data itself data<00:27:35.520> itself<00:27:35.940> is<00:27:36.320> not<00:27:37.320> so<00:27:37.530> secure<00:27:37.830> it<00:27:38.130> can<00:27:38.340> be 00:27:38.480 --> 00:27:38.490 align:start position:0% data itself is not so secure it can be 00:27:38.490 --> 00:27:40.340 align:start position:0% data itself is not so secure it can be easily<00:27:38.700> manipulated<00:27:39.150> it<00:27:39.600> can<00:27:39.780> be<00:27:39.930> faked 00:27:40.340 --> 00:27:40.350 align:start position:0% easily manipulated it can be faked 00:27:40.350 --> 00:27:44.210 align:start position:0% easily manipulated it can be faked which<00:27:41.250> again<00:27:41.400> proves<00:27:41.820> a<00:27:41.940> problem<00:27:42.300> to<00:27:43.290> make<00:27:43.530> IOT 00:27:44.210 --> 00:27:44.220 align:start position:0% which again proves a problem to make IOT 00:27:44.220 --> 00:27:45.710 align:start position:0% which again proves a problem to make IOT devices<00:27:44.550> good<00:27:45.360> data 00:27:45.710 --> 00:27:45.720 align:start position:0% devices good data 00:27:45.720 --> 00:27:49.520 align:start position:0% devices good data Oracle's<00:27:46.280> so<00:27:47.280> imagine<00:27:48.270> a<00:27:48.540> hybrid<00:27:49.320> car 00:27:49.520 --> 00:27:49.530 align:start position:0% Oracle's so imagine a hybrid car 00:27:49.530 --> 00:27:52.490 align:start position:0% Oracle's so imagine a hybrid car charging<00:27:50.520> and<00:27:51.150> charging<00:27:51.180> using<00:27:52.020> an<00:27:52.230> induction 00:27:52.490 --> 00:27:52.500 align:start position:0% charging and charging using an induction 00:27:52.500 --> 00:27:54.440 align:start position:0% charging and charging using an induction loop<00:27:52.650> at<00:27:52.920> a<00:27:52.950> red<00:27:53.130> light<00:27:53.160> crossing<00:27:53.730> and<00:27:53.880> the 00:27:54.440 --> 00:27:54.450 align:start position:0% loop at a red light crossing and the 00:27:54.450 --> 00:27:57.020 align:start position:0% loop at a red light crossing and the wallet<00:27:54.630> needs<00:27:54.900> to<00:27:55.050> pay<00:27:55.580> the<00:27:56.580> amount<00:27:56.880> of 00:27:57.020 --> 00:27:57.030 align:start position:0% wallet needs to pay the amount of 00:27:57.030 --> 00:27:58.970 align:start position:0% wallet needs to pay the amount of kilowatt<00:27:57.450> hours<00:27:57.660> of<00:27:57.810> energy<00:27:57.930> which<00:27:58.710> flew<00:27:58.890> in 00:27:58.970 --> 00:27:58.980 align:start position:0% kilowatt hours of energy which flew in 00:27:58.980 --> 00:28:00.770 align:start position:0% kilowatt hours of energy which flew in the<00:27:59.100> car<00:27:59.280> and<00:27:59.580> the<00:27:59.820> equivalent<00:28:00.420> amount<00:28:00.630> of 00:28:00.770 --> 00:28:00.780 align:start position:0% the car and the equivalent amount of 00:28:00.780 --> 00:28:02.450 align:start position:0% the car and the equivalent amount of money<00:28:00.990> but<00:28:01.200> then<00:28:01.350> the<00:28:01.620> the<00:28:01.950> car<00:28:02.160> wallet 00:28:02.450 --> 00:28:02.460 align:start position:0% money but then the the car wallet 00:28:02.460 --> 00:28:05.120 align:start position:0% money but then the the car wallet doesn't<00:28:02.730> really<00:28:02.850> know<00:28:03.060> how<00:28:03.720> much<00:28:03.930> or<00:28:04.680> doesn't 00:28:05.120 --> 00:28:05.130 align:start position:0% doesn't really know how much or doesn't 00:28:05.130 --> 00:28:07.100 align:start position:0% doesn't really know how much or doesn't really<00:28:05.250> know<00:28:05.460> but<00:28:06.240> doesn't<00:28:06.690> really<00:28:06.810> have<00:28:07.080> the 00:28:07.100 --> 00:28:07.110 align:start position:0% really know but doesn't really have the 00:28:07.110 --> 00:28:08.540 align:start position:0% really know but doesn't really have the guarantee<00:28:07.380> that<00:28:07.650> this<00:28:07.920> was<00:28:08.100> the<00:28:08.220> amount<00:28:08.430> of 00:28:08.540 --> 00:28:08.550 align:start position:0% guarantee that this was the amount of 00:28:08.550 --> 00:28:10.880 align:start position:0% guarantee that this was the amount of kilowatt<00:28:08.940> of<00:28:09.260> energy<00:28:10.260> which<00:28:10.380> flew<00:28:10.620> into<00:28:10.770> the 00:28:10.880 --> 00:28:10.890 align:start position:0% kilowatt of energy which flew into the 00:28:10.890 --> 00:28:13.340 align:start position:0% kilowatt of energy which flew into the car<00:28:11.100> and<00:28:11.630> there<00:28:12.630> needs<00:28:12.810> to<00:28:12.870> be<00:28:12.960> a<00:28:13.110> good 00:28:13.340 --> 00:28:13.350 align:start position:0% car and there needs to be a good 00:28:13.350 --> 00:28:15.830 align:start position:0% car and there needs to be a good attestation<00:28:14.330> such<00:28:15.330> that<00:28:15.510> the<00:28:15.660> wallet 00:28:15.830 --> 00:28:15.840 align:start position:0% attestation such that the wallet 00:28:15.840 --> 00:28:17.750 align:start position:0% attestation such that the wallet recognizes<00:28:16.560> this<00:28:16.740> and<00:28:17.070> pays 00:28:17.750 --> 00:28:17.760 align:start position:0% recognizes this and pays 00:28:17.760 --> 00:28:20.420 align:start position:0% recognizes this and pays acquiring<00:28:18.360> for<00:28:18.630> that<00:28:18.780> so<00:28:19.050> the<00:28:19.890> problem<00:28:20.310> really 00:28:20.420 --> 00:28:20.430 align:start position:0% acquiring for that so the problem really 00:28:20.430 --> 00:28:24.100 align:start position:0% acquiring for that so the problem really is<00:28:20.610> how<00:28:20.880> do<00:28:20.940> we<00:28:21.060> ensure<00:28:22.250> the<00:28:23.250> truthfulness<00:28:23.700> of 00:28:24.100 --> 00:28:24.110 align:start position:0% is how do we ensure the truthfulness of 00:28:24.110 --> 00:28:29.150 align:start position:0% is how do we ensure the truthfulness of this<00:28:25.160> of<00:28:26.160> this<00:28:26.340> value<00:28:26.700> chain<00:28:26.940> and<00:28:27.860> the<00:28:28.860> value 00:28:29.150 --> 00:28:29.160 align:start position:0% this of this value chain and the value 00:28:29.160 --> 00:28:32.150 align:start position:0% this of this value chain and the value chain<00:28:29.310> which<00:28:29.520> we<00:28:30.440> do<00:28:31.440> believe<00:28:31.620> is<00:28:31.890> in<00:28:32.040> that 00:28:32.150 --> 00:28:32.160 align:start position:0% chain which we do believe is in that 00:28:32.160 --> 00:28:35.810 align:start position:0% chain which we do believe is in that we've<00:28:32.430> elevated<00:28:33.150> data<00:28:34.190> from<00:28:35.190> a<00:28:35.220> resource<00:28:35.580> to 00:28:35.810 --> 00:28:35.820 align:start position:0% we've elevated data from a resource to 00:28:35.820 --> 00:28:39.289 align:start position:0% we've elevated data from a resource to to<00:28:36.120> a<00:28:36.150> digital<00:28:36.630> asset<00:28:36.840> and<00:28:37.370> we<00:28:38.370> believe<00:28:38.610> that 00:28:39.289 --> 00:28:39.299 align:start position:0% to a digital asset and we believe that 00:28:39.299 --> 00:28:41.570 align:start position:0% to a digital asset and we believe that it<00:28:39.779> could<00:28:40.019> be<00:28:40.169> any<00:28:40.649> asset<00:28:41.070> in<00:28:41.159> the<00:28:41.249> physical 00:28:41.570 --> 00:28:41.580 align:start position:0% it could be any asset in the physical 00:28:41.580 --> 00:28:43.519 align:start position:0% it could be any asset in the physical world<00:28:41.789> we<00:28:41.940> first<00:28:42.210> when<00:28:42.570> we<00:28:42.720> pay<00:28:42.869> for<00:28:43.080> the<00:28:43.200> asset 00:28:43.519 --> 00:28:43.529 align:start position:0% world we first when we pay for the asset 00:28:43.529 --> 00:28:45.529 align:start position:0% world we first when we pay for the asset we<00:28:43.649> kind<00:28:43.860> of<00:28:44.009> have<00:28:44.549> the<00:28:44.789> guarantee<00:28:44.940> that<00:28:45.239> this 00:28:45.529 --> 00:28:45.539 align:start position:0% we kind of have the guarantee that this 00:28:45.539 --> 00:28:47.509 align:start position:0% we kind of have the guarantee that this asset<00:28:45.809> which<00:28:46.080> we<00:28:46.200> are<00:28:46.289> paying<00:28:46.470> for<00:28:46.559> has<00:28:47.279> either 00:28:47.509 --> 00:28:47.519 align:start position:0% asset which we are paying for has either 00:28:47.519 --> 00:28:49.159 align:start position:0% asset which we are paying for has either been<00:28:47.669> verified<00:28:47.970> or<00:28:48.480> the<00:28:48.570> quality<00:28:48.960> has<00:28:49.110> been 00:28:49.159 --> 00:28:49.169 align:start position:0% been verified or the quality has been 00:28:49.169 --> 00:28:52.190 align:start position:0% been verified or the quality has been assured<00:28:50.009> by<00:28:50.070> some<00:28:50.399> agency<00:28:50.879> but<00:28:51.690> that's<00:28:51.869> that's 00:28:52.190 --> 00:28:52.200 align:start position:0% assured by some agency but that's that's 00:28:52.200 --> 00:28:53.330 align:start position:0% assured by some agency but that's that's not<00:28:52.379> the<00:28:52.590> case<00:28:52.769> of<00:28:52.919> the<00:28:52.950> current 00:28:53.330 --> 00:28:53.340 align:start position:0% not the case of the current 00:28:53.340 --> 00:28:54.919 align:start position:0% not the case of the current infrastructure<00:28:53.820> setup<00:28:54.239> of<00:28:54.360> how<00:28:54.389> data<00:28:54.749> is 00:28:54.919 --> 00:28:54.929 align:start position:0% infrastructure setup of how data is 00:28:54.929 --> 00:28:58.940 align:start position:0% infrastructure setup of how data is being<00:28:55.850> produced<00:28:56.850> and<00:28:57.119> traded<00:28:57.450> and<00:28:58.350> even<00:28:58.619> if<00:28:58.739> in 00:28:58.940 --> 00:28:58.950 align:start position:0% being produced and traded and even if in 00:28:58.950 --> 00:29:00.080 align:start position:0% being produced and traded and even if in the<00:28:59.039> future<00:28:59.159> we<00:28:59.340> do<00:28:59.549> have<00:28:59.730> sort<00:29:00.029> of 00:29:00.080 --> 00:29:00.090 align:start position:0% the future we do have sort of 00:29:00.090 --> 00:29:02.359 align:start position:0% the future we do have sort of regulations<00:29:00.779> and<00:29:01.070> infrastructures<00:29:02.070> in<00:29:02.190> place 00:29:02.359 --> 00:29:02.369 align:start position:0% regulations and infrastructures in place 00:29:02.369 --> 00:29:05.359 align:start position:0% regulations and infrastructures in place which<00:29:02.580> makes<00:29:02.850> makes<00:29:03.360> makes<00:29:03.600> makes<00:29:03.989> it<00:29:04.169> easy<00:29:05.039> to 00:29:05.359 --> 00:29:05.369 align:start position:0% which makes makes makes makes it easy to 00:29:05.369 --> 00:29:07.450 align:start position:0% which makes makes makes makes it easy to pay<00:29:06.149> for<00:29:06.480> the<00:29:06.600> data<00:29:06.749> which<00:29:06.989> you<00:29:07.019> are<00:29:07.139> consuming 00:29:07.450 --> 00:29:07.460 align:start position:0% pay for the data which you are consuming 00:29:07.460 --> 00:29:11.629 align:start position:0% pay for the data which you are consuming there's<00:29:08.460> still<00:29:08.700> very<00:29:10.159> still<00:29:11.159> be<00:29:11.279> too<00:29:11.460> many 00:29:11.629 --> 00:29:11.639 align:start position:0% there's still very still be too many 00:29:11.639 --> 00:29:14.599 align:start position:0% there's still very still be too many difficulties<00:29:12.269> in<00:29:12.330> post<00:29:12.840> transaction<00:29:13.710> data 00:29:14.599 --> 00:29:14.609 align:start position:0% difficulties in post transaction data 00:29:14.609 --> 00:29:16.460 align:start position:0% difficulties in post transaction data settlement<00:29:15.179> because<00:29:15.389> just<00:29:15.600> the<00:29:15.720> sheer<00:29:16.230> volume 00:29:16.460 --> 00:29:16.470 align:start position:0% settlement because just the sheer volume 00:29:16.470 --> 00:29:18.259 align:start position:0% settlement because just the sheer volume or<00:29:16.889> the<00:29:16.919> velocity<00:29:17.220> of<00:29:17.639> the<00:29:17.759> data<00:29:17.909> which<00:29:18.119> would 00:29:18.259 --> 00:29:18.269 align:start position:0% or the velocity of the data which would 00:29:18.269 --> 00:29:19.940 align:start position:0% or the velocity of the data which would be<00:29:18.389> flowing<00:29:18.600> it's<00:29:19.259> very<00:29:19.499> difficult<00:29:19.830> to 00:29:19.940 --> 00:29:19.950 align:start position:0% be flowing it's very difficult to 00:29:19.950 --> 00:29:23.379 align:start position:0% be flowing it's very difficult to regulate<00:29:20.340> it<00:29:20.489> after<00:29:20.820> that<00:29:20.970> so<00:29:21.899> so<00:29:22.320> the<00:29:22.440> whole 00:29:23.379 --> 00:29:23.389 align:start position:0% regulate it after that so so the whole 00:29:23.389 --> 00:29:26.779 align:start position:0% regulate it after that so so the whole problem<00:29:24.389> comes<00:29:24.840> when<00:29:25.169> we<00:29:25.499> have<00:29:25.559> to<00:29:25.649> attest<00:29:26.639> the 00:29:26.779 --> 00:29:26.789 align:start position:0% problem comes when we have to attest the 00:29:26.789 --> 00:29:28.369 align:start position:0% problem comes when we have to attest the data<00:29:26.940> from<00:29:27.210> source<00:29:27.480> and<00:29:27.749> this<00:29:27.840> is<00:29:27.899> this<00:29:28.259> is 00:29:28.369 --> 00:29:28.379 align:start position:0% data from source and this is this is 00:29:28.379 --> 00:29:31.129 align:start position:0% data from source and this is this is what<00:29:28.999> Sanjay<00:29:29.999> and<00:29:30.090> his<00:29:30.239> team<00:29:30.419> at<00:29:30.659> Intel<00:29:31.019> are 00:29:31.129 --> 00:29:31.139 align:start position:0% what Sanjay and his team at Intel are 00:29:31.139 --> 00:29:34.310 align:start position:0% what Sanjay and his team at Intel are also<00:29:31.289> doing<00:29:31.710> so<00:29:31.859> like<00:29:32.039> having<00:29:33.139> good<00:29:34.139> data 00:29:34.310 --> 00:29:34.320 align:start position:0% also doing so like having good data 00:29:34.320 --> 00:29:36.200 align:start position:0% also doing so like having good data Oracle's<00:29:34.919> but<00:29:35.220> then<00:29:35.429> to<00:29:35.700> have<00:29:35.879> good<00:29:36.059> data 00:29:36.200 --> 00:29:36.210 align:start position:0% Oracle's but then to have good data 00:29:36.210 --> 00:29:38.359 align:start position:0% Oracle's but then to have good data Oracle's<00:29:36.720> we<00:29:36.869> need<00:29:37.019> trusted<00:29:37.679> data<00:29:37.799> flowing<00:29:38.159> in 00:29:38.359 --> 00:29:38.369 align:start position:0% Oracle's we need trusted data flowing in 00:29:38.369 --> 00:29:41.629 align:start position:0% Oracle's we need trusted data flowing in these<00:29:38.519> Oracle's<00:29:38.820> and<00:29:39.210> to<00:29:39.720> have<00:29:40.009> trust<00:29:41.009> data<00:29:41.309> we 00:29:41.629 --> 00:29:41.639 align:start position:0% these Oracle's and to have trust data we 00:29:41.639 --> 00:29:45.320 align:start position:0% these Oracle's and to have trust data we first<00:29:41.879> need<00:29:42.149> trusted<00:29:42.960> computing<00:29:43.639> and<00:29:44.639> which 00:29:45.320 --> 00:29:45.330 align:start position:0% first need trusted computing and which 00:29:45.330 --> 00:29:47.359 align:start position:0% first need trusted computing and which is<00:29:45.450> why<00:29:45.600> we<00:29:45.840> kind<00:29:46.019> of<00:29:46.169> follow<00:29:46.649> the<00:29:46.859> analogy<00:29:47.340> of 00:29:47.359 --> 00:29:47.369 align:start position:0% is why we kind of follow the analogy of 00:29:47.369 --> 00:29:50.289 align:start position:0% is why we kind of follow the analogy of data<00:29:47.669> as<00:29:47.940> a<00:29:47.970> as<00:29:48.330> a<00:29:48.529> asset<00:29:49.529> which<00:29:49.679> has<00:29:49.830> been 00:29:50.289 --> 00:29:50.299 align:start position:0% data as a as a asset which has been 00:29:50.299 --> 00:29:53.269 align:start position:0% data as a as a asset which has been harvested<00:29:51.299> from<00:29:51.989> source<00:29:52.320> harvested<00:29:53.100> in<00:29:53.220> a 00:29:53.269 --> 00:29:53.279 align:start position:0% harvested from source harvested in a 00:29:53.279 --> 00:29:55.310 align:start position:0% harvested from source harvested in a manner<00:29:53.460> such<00:29:53.669> that<00:29:53.850> it<00:29:53.970> can<00:29:54.090> be<00:29:54.119> trusted<00:29:54.659> then 00:29:55.310 --> 00:29:55.320 align:start position:0% manner such that it can be trusted then 00:29:55.320 --> 00:29:57.859 align:start position:0% manner such that it can be trusted then processed<00:29:55.799> then<00:29:56.190> transported<00:29:56.909> then<00:29:57.509> assess 00:29:57.859 --> 00:29:57.869 align:start position:0% processed then transported then assess 00:29:57.869 --> 00:30:04.310 align:start position:0% processed then transported then assess and<00:29:58.109> then<00:29:58.139> commercialized<00:30:02.600> so<00:30:03.600> this<00:30:03.749> is<00:30:03.929> in 00:30:04.310 --> 00:30:04.320 align:start position:0% and then commercialized so this is in 00:30:04.320 --> 00:30:07.279 align:start position:0% and then commercialized so this is in brief<00:30:04.879> the<00:30:05.879> technology<00:30:06.539> stack<00:30:06.809> we<00:30:07.019> had<00:30:07.139> we 00:30:07.279 --> 00:30:07.289 align:start position:0% brief the technology stack we had we 00:30:07.289 --> 00:30:10.570 align:start position:0% brief the technology stack we had we were<00:30:07.440> building<00:30:07.769> so<00:30:07.950> we<00:30:08.070> built<00:30:08.850> on<00:30:09.210> top<00:30:09.809> of<00:30:09.869> the 00:30:10.570 --> 00:30:10.580 align:start position:0% were building so we built on top of the 00:30:10.580 --> 00:30:13.639 align:start position:0% were building so we built on top of the on<00:30:11.580> top<00:30:11.850> of<00:30:11.999> arms<00:30:12.419> Hardware<00:30:12.899> extension<00:30:13.529> the 00:30:13.639 --> 00:30:13.649 align:start position:0% on top of arms Hardware extension the 00:30:13.649 --> 00:30:15.979 align:start position:0% on top of arms Hardware extension the trust<00:30:13.889> zone<00:30:13.980> a<00:30:14.399> lightweight<00:30:15.149> trusted 00:30:15.979 --> 00:30:15.989 align:start position:0% trust zone a lightweight trusted 00:30:15.989 --> 00:30:17.450 align:start position:0% trust zone a lightweight trusted execution<00:30:16.529> environment<00:30:17.070> and<00:30:17.220> a<00:30:17.309> build 00:30:17.450 --> 00:30:17.460 align:start position:0% execution environment and a build 00:30:17.460 --> 00:30:19.999 align:start position:0% execution environment and a build operating<00:30:17.909> system<00:30:18.299> which<00:30:19.200> enables<00:30:19.679> the<00:30:19.830> data 00:30:19.999 --> 00:30:20.009 align:start position:0% operating system which enables the data 00:30:20.009 --> 00:30:24.769 align:start position:0% operating system which enables the data to<00:30:20.249> be<00:30:20.369> attested<00:30:20.940> at<00:30:21.570> source<00:30:22.019> and<00:30:22.759> then<00:30:23.779> the 00:30:24.769 --> 00:30:24.779 align:start position:0% to be attested at source and then the 00:30:24.779 --> 00:30:27.190 align:start position:0% to be attested at source and then the the<00:30:25.080> OS<00:30:25.350> of<00:30:25.499> course<00:30:25.710> has<00:30:25.859> certain<00:30:26.220> properties 00:30:27.190 --> 00:30:27.200 align:start position:0% the OS of course has certain properties 00:30:27.200 --> 00:30:30.369 align:start position:0% the OS of course has certain properties which<00:30:28.200> allows<00:30:28.590> the<00:30:29.369> sheer 00:30:30.369 --> 00:30:30.379 align:start position:0% which allows the sheer 00:30:30.379 --> 00:30:33.470 align:start position:0% which allows the sheer compartmentalization<00:30:31.379> of<00:30:31.859> of<00:30:32.129> the<00:30:33.029> the 00:30:33.470 --> 00:30:33.480 align:start position:0% compartmentalization of of the the 00:30:33.480 --> 00:30:35.330 align:start position:0% compartmentalization of of the the secure<00:30:33.960> world<00:30:34.200> and<00:30:34.470> the<00:30:34.529> normal<00:30:34.859> world<00:30:35.039> so<00:30:35.279> you 00:30:35.330 --> 00:30:35.340 align:start position:0% secure world and the normal world so you 00:30:35.340 --> 00:30:37.789 align:start position:0% secure world and the normal world so you can<00:30:35.549> have<00:30:35.700> all<00:30:35.730> your<00:30:36.289> cryptographic<00:30:37.289> keys 00:30:37.789 --> 00:30:37.799 align:start position:0% can have all your cryptographic keys 00:30:37.799 --> 00:30:39.349 align:start position:0% can have all your cryptographic keys your<00:30:38.070> cryptographic<00:30:38.369> materials<00:30:39.090> in<00:30:39.269> the 00:30:39.349 --> 00:30:39.359 align:start position:0% your cryptographic materials in the 00:30:39.359 --> 00:30:41.419 align:start position:0% your cryptographic materials in the secure<00:30:39.659> world<00:30:39.869> and<00:30:40.169> your<00:30:40.649> everyday<00:30:40.980> running 00:30:41.419 --> 00:30:41.429 align:start position:0% secure world and your everyday running 00:30:41.429 --> 00:30:43.789 align:start position:0% secure world and your everyday running operations<00:30:41.999> in<00:30:42.779> the<00:30:42.899> normal<00:30:43.230> world<00:30:43.350> so<00:30:43.559> even 00:30:43.789 --> 00:30:43.799 align:start position:0% operations in the normal world so even 00:30:43.799 --> 00:30:47.480 align:start position:0% operations in the normal world so even if<00:30:43.919> your<00:30:44.639> your<00:30:45.119> wallet<00:30:45.299> or<00:30:46.200> your<00:30:47.039> normal<00:30:47.340> world 00:30:47.480 --> 00:30:47.490 align:start position:0% if your your wallet or your normal world 00:30:47.490 --> 00:30:48.950 align:start position:0% if your your wallet or your normal world is<00:30:47.669> hacked<00:30:47.879> your<00:30:48.059> secure<00:30:48.450> world<00:30:48.659> remains 00:30:48.950 --> 00:30:48.960 align:start position:0% is hacked your secure world remains 00:30:48.960 --> 00:30:51.430 align:start position:0% is hacked your secure world remains secure<00:30:49.679> and 00:30:51.430 --> 00:30:51.440 align:start position:0% secure and 00:30:51.440 --> 00:30:54.789 align:start position:0% secure and your<00:30:51.590> keys<00:30:52.039> are<00:30:52.210> protected<00:30:53.210> basically<00:30:53.799> then 00:30:54.789 --> 00:30:54.799 align:start position:0% your keys are protected basically then 00:30:54.799 --> 00:30:56.919 align:start position:0% your keys are protected basically then then<00:30:55.129> we<00:30:55.309> have<00:30:55.490> the<00:30:55.820> secure<00:30:56.269> communication 00:30:56.919 --> 00:30:56.929 align:start position:0% then we have the secure communication 00:30:56.929 --> 00:30:59.019 align:start position:0% then we have the secure communication protocol<00:30:57.289> so<00:30:57.470> traditionally<00:30:58.399> IOT<00:30:58.730> devices 00:30:59.019 --> 00:30:59.029 align:start position:0% protocol so traditionally IOT devices 00:30:59.029 --> 00:31:02.110 align:start position:0% protocol so traditionally IOT devices have<00:30:59.269> used<00:30:59.480> the<00:30:59.690> mqtt<00:31:00.409> protocol<00:31:00.889> which<00:31:01.129> which 00:31:02.110 --> 00:31:02.120 align:start position:0% have used the mqtt protocol which which 00:31:02.120 --> 00:31:03.730 align:start position:0% have used the mqtt protocol which which which<00:31:02.360> has<00:31:02.570> around<00:31:02.809> seven<00:31:03.139> communication 00:31:03.730 --> 00:31:03.740 align:start position:0% which has around seven communication 00:31:03.740 --> 00:31:06.730 align:start position:0% which has around seven communication rounds<00:31:04.129> and<00:31:05.000> you<00:31:05.059> put<00:31:05.360> TLS<00:31:05.750> as<00:31:05.899> well<00:31:06.110> on<00:31:06.379> top<00:31:06.559> of 00:31:06.730 --> 00:31:06.740 align:start position:0% rounds and you put TLS as well on top of 00:31:06.740 --> 00:31:10.480 align:start position:0% rounds and you put TLS as well on top of it<00:31:06.970> then<00:31:07.970> it<00:31:08.120> just<00:31:08.570> doesn't<00:31:08.840> become<00:31:09.490> usable 00:31:10.480 --> 00:31:10.490 align:start position:0% it then it just doesn't become usable 00:31:10.490 --> 00:31:12.340 align:start position:0% it then it just doesn't become usable enough<00:31:10.940> for<00:31:11.210> this<00:31:11.419> this<00:31:11.720> sheer<00:31:11.990> volume<00:31:12.139> of 00:31:12.340 --> 00:31:12.350 align:start position:0% enough for this this sheer volume of 00:31:12.350 --> 00:31:14.940 align:start position:0% enough for this this sheer volume of data<00:31:12.409> flowing<00:31:12.860> for<00:31:13.159> IOT<00:31:13.490> devices<00:31:13.820> or<00:31:14.299> IOT<00:31:14.509> data 00:31:14.940 --> 00:31:14.950 align:start position:0% data flowing for IOT devices or IOT data 00:31:14.950 --> 00:31:17.440 align:start position:0% data flowing for IOT devices or IOT data so<00:31:15.950> we've<00:31:16.129> tried<00:31:16.309> integrating<00:31:17.000> some<00:31:17.179> sort<00:31:17.389> of 00:31:17.440 --> 00:31:17.450 align:start position:0% so we've tried integrating some sort of 00:31:17.450 --> 00:31:21.460 align:start position:0% so we've tried integrating some sort of a<00:31:18.159> simple<00:31:19.159> secure<00:31:20.149> messaging<00:31:20.750> protocol<00:31:21.169> on 00:31:21.460 --> 00:31:21.470 align:start position:0% a simple secure messaging protocol on 00:31:21.470 --> 00:31:23.799 align:start position:0% a simple secure messaging protocol on top<00:31:21.649> of<00:31:21.799> em<00:31:21.919> qtd<00:31:22.250> says<00:31:22.519> that<00:31:22.700> it's<00:31:23.210> it's<00:31:23.480> a<00:31:23.600> bit 00:31:23.799 --> 00:31:23.809 align:start position:0% top of em qtd says that it's it's a bit 00:31:23.809 --> 00:31:25.899 align:start position:0% top of em qtd says that it's it's a bit more<00:31:23.960> low<00:31:24.169> latency<00:31:24.710> it<00:31:25.070> just<00:31:25.250> requires<00:31:25.700> three 00:31:25.899 --> 00:31:25.909 align:start position:0% more low latency it just requires three 00:31:25.909 --> 00:31:28.539 align:start position:0% more low latency it just requires three communication<00:31:26.509> rounds<00:31:27.009> then<00:31:28.009> the<00:31:28.129> next<00:31:28.370> step 00:31:28.539 --> 00:31:28.549 align:start position:0% communication rounds then the next step 00:31:28.549 --> 00:31:31.539 align:start position:0% communication rounds then the next step is<00:31:28.700> to<00:31:28.909> have<00:31:29.090> have<00:31:29.629> a<00:31:29.659> testimony<00:31:30.549> the 00:31:31.539 --> 00:31:31.549 align:start position:0% is to have have a testimony the 00:31:31.549 --> 00:31:33.220 align:start position:0% is to have have a testimony the testimony<00:31:31.580> kind<00:31:32.360> of<00:31:32.480> proves<00:31:32.809> that<00:31:33.080> the 00:31:33.220 --> 00:31:33.230 align:start position:0% testimony kind of proves that the 00:31:33.230 --> 00:31:34.930 align:start position:0% testimony kind of proves that the program<00:31:33.620> was<00:31:33.799> executed<00:31:34.399> in<00:31:34.490> the<00:31:34.610> manner<00:31:34.820> that 00:31:34.930 --> 00:31:34.940 align:start position:0% program was executed in the manner that 00:31:34.940 --> 00:31:37.720 align:start position:0% program was executed in the manner that was<00:31:35.210> supposed<00:31:35.600> to<00:31:35.659> be<00:31:35.779> executed<00:31:35.899> in<00:31:36.490> and<00:31:37.490> then 00:31:37.720 --> 00:31:37.730 align:start position:0% was supposed to be executed in and then 00:31:37.730 --> 00:31:39.519 align:start position:0% was supposed to be executed in and then finally<00:31:38.179> you<00:31:38.299> can<00:31:38.480> transport<00:31:38.990> the<00:31:39.139> data<00:31:39.320> to 00:31:39.519 --> 00:31:39.529 align:start position:0% finally you can transport the data to 00:31:39.529 --> 00:31:41.289 align:start position:0% finally you can transport the data to the<00:31:39.559> blockchain<00:31:39.830> layer<00:31:40.220> or<00:31:40.519> the<00:31:40.789> cloud<00:31:41.120> layer 00:31:41.289 --> 00:31:41.299 align:start position:0% the blockchain layer or the cloud layer 00:31:41.299 --> 00:31:42.789 align:start position:0% the blockchain layer or the cloud layer and<00:31:41.570> then<00:31:41.659> where<00:31:41.870> it<00:31:41.899> can<00:31:42.139> be<00:31:42.259> finally 00:31:42.789 --> 00:31:42.799 align:start position:0% and then where it can be finally 00:31:42.799 --> 00:31:45.369 align:start position:0% and then where it can be finally realized<00:31:43.190> that<00:31:43.639> this<00:31:43.970> this<00:31:44.269> data<00:31:44.480> is<00:31:44.750> now 00:31:45.369 --> 00:31:45.379 align:start position:0% realized that this this data is now 00:31:45.379 --> 00:31:47.169 align:start position:0% realized that this this data is now truthful<00:31:45.980> and<00:31:46.250> it<00:31:46.399> can<00:31:46.549> be<00:31:46.669> traded<00:31:47.029> or 00:31:47.169 --> 00:31:47.179 align:start position:0% truthful and it can be traded or 00:31:47.179 --> 00:31:50.490 align:start position:0% truthful and it can be traded or commercialized<00:31:47.809> or<00:31:48.730> utilizing<00:31:49.730> some 00:31:50.490 --> 00:31:50.500 align:start position:0% commercialized or utilizing some 00:31:50.500 --> 00:31:56.590 align:start position:0% commercialized or utilizing some intelligent<00:31:51.500> manner<00:31:55.029> so<00:31:56.029> these<00:31:56.330> are<00:31:56.480> just 00:31:56.590 --> 00:31:56.600 align:start position:0% intelligent manner so these are just 00:31:56.600 --> 00:31:59.320 align:start position:0% intelligent manner so these are just some<00:31:56.720> brief<00:31:57.460> features<00:31:58.460> we<00:31:58.669> think<00:31:59.029> are 00:31:59.320 --> 00:31:59.330 align:start position:0% some brief features we think are 00:31:59.330 --> 00:32:02.999 align:start position:0% some brief features we think are important<00:32:00.049> that's<00:32:00.200> why<00:32:00.379> we<00:32:00.529> use<00:32:00.740> the<00:32:01.809> zone 00:32:02.999 --> 00:32:03.009 align:start position:0% important that's why we use the zone 00:32:03.009 --> 00:32:05.740 align:start position:0% important that's why we use the zone extension<00:32:04.009> at<00:32:04.129> the<00:32:04.159> moment<00:32:04.580> in<00:32:05.240> the<00:32:05.330> future<00:32:05.629> we 00:32:05.740 --> 00:32:05.750 align:start position:0% extension at the moment in the future we 00:32:05.750 --> 00:32:07.810 align:start position:0% extension at the moment in the future we plan<00:32:05.779> to<00:32:06.139> be<00:32:06.259> compatible<00:32:06.799> with<00:32:07.070> with<00:32:07.490> Intel 00:32:07.810 --> 00:32:07.820 align:start position:0% plan to be compatible with with Intel 00:32:07.820 --> 00:32:10.180 align:start position:0% plan to be compatible with with Intel SGX<00:32:07.970> although<00:32:08.960> which<00:32:09.110> it's<00:32:09.350> it's<00:32:09.649> it's<00:32:09.950> a<00:32:10.039> bit 00:32:10.180 --> 00:32:10.190 align:start position:0% SGX although which it's it's it's a bit 00:32:10.190 --> 00:32:11.830 align:start position:0% SGX although which it's it's it's a bit more<00:32:10.370> compatible<00:32:10.879> for<00:32:11.029> cloud<00:32:11.210> architectures 00:32:11.830 --> 00:32:11.840 align:start position:0% more compatible for cloud architectures 00:32:11.840 --> 00:32:13.389 align:start position:0% more compatible for cloud architectures at<00:32:11.960> the<00:32:12.080> moment<00:32:12.409> not<00:32:12.529> so<00:32:12.590> much<00:32:12.889> for<00:32:13.039> embedded 00:32:13.389 --> 00:32:13.399 align:start position:0% at the moment not so much for embedded 00:32:13.399 --> 00:32:17.139 align:start position:0% at the moment not so much for embedded systems<00:32:13.570> which<00:32:14.570> is<00:32:14.690> where<00:32:14.809> we<00:32:14.929> use<00:32:16.149> precision 00:32:17.139 --> 00:32:17.149 align:start position:0% systems which is where we use precision 00:32:17.149 --> 00:32:19.299 align:start position:0% systems which is where we use precision X<00:32:17.509> extension<00:32:18.470> at<00:32:18.559> the<00:32:18.590> moment<00:32:18.919> so<00:32:18.980> it<00:32:19.070> allows 00:32:19.299 --> 00:32:19.309 align:start position:0% X extension at the moment so it allows 00:32:19.309 --> 00:32:22.269 align:start position:0% X extension at the moment so it allows us<00:32:19.460> to<00:32:19.610> isolate<00:32:19.850> programs<00:32:21.070> shield<00:32:22.070> the 00:32:22.269 --> 00:32:22.279 align:start position:0% us to isolate programs shield the 00:32:22.279 --> 00:32:25.779 align:start position:0% us to isolate programs shield the cryptographic<00:32:23.230> material<00:32:24.230> and<00:32:24.549> also<00:32:25.549> it<00:32:25.639> has<00:32:25.759> a 00:32:25.779 --> 00:32:25.789 align:start position:0% cryptographic material and also it has a 00:32:25.789 --> 00:32:29.169 align:start position:0% cryptographic material and also it has a secure<00:32:26.149> boot<00:32:26.299> process<00:32:26.860> plus<00:32:27.909> something<00:32:28.909> we 00:32:29.169 --> 00:32:29.179 align:start position:0% secure boot process plus something we 00:32:29.179 --> 00:32:31.210 align:start position:0% secure boot process plus something we like<00:32:29.299> to<00:32:29.450> call<00:32:29.600> the<00:32:29.720> snags<00:32:29.990> which<00:32:30.919> basically 00:32:31.210 --> 00:32:31.220 align:start position:0% like to call the snags which basically 00:32:31.220 --> 00:32:33.100 align:start position:0% like to call the snags which basically proves<00:32:31.610> that<00:32:31.759> the<00:32:31.879> program<00:32:32.210> was<00:32:32.389> executed<00:32:32.990> in 00:32:33.100 --> 00:32:33.110 align:start position:0% proves that the program was executed in 00:32:33.110 --> 00:32:38.440 align:start position:0% proves that the program was executed in a<00:32:33.200> certain<00:32:33.500> way<00:32:37.120> that's<00:32:38.120> the<00:32:38.330> brief 00:32:38.440 --> 00:32:38.450 align:start position:0% a certain way that's the brief 00:32:38.450 --> 00:32:41.440 align:start position:0% a certain way that's the brief architecture<00:32:39.519> of<00:32:40.519> the<00:32:40.759> normal<00:32:41.120> operating 00:32:41.440 --> 00:32:41.450 align:start position:0% architecture of the normal operating 00:32:41.450 --> 00:32:44.190 align:start position:0% architecture of the normal operating system<00:32:41.870> the<00:32:42.860> secure<00:32:43.159> operating<00:32:43.490> system 00:32:44.190 --> 00:32:44.200 align:start position:0% system the secure operating system 00:32:44.200 --> 00:32:46.930 align:start position:0% system the secure operating system there's<00:32:45.200> also<00:32:45.379> a<00:32:45.500> 60<00:32:45.980> page<00:32:46.129> white<00:32:46.399> paper<00:32:46.639> I<00:32:46.730> can 00:32:46.930 --> 00:32:46.940 align:start position:0% there's also a 60 page white paper I can 00:32:46.940 --> 00:32:48.759 align:start position:0% there's also a 60 page white paper I can I<00:32:47.029> can<00:32:47.179> have<00:32:47.750> it<00:32:47.870> distributed<00:32:48.110> so<00:32:48.500> you<00:32:48.590> can 00:32:48.759 --> 00:32:48.769 align:start position:0% I can have it distributed so you can 00:32:48.769 --> 00:32:51.190 align:start position:0% I can have it distributed so you can find<00:32:49.100> all<00:32:49.370> the<00:32:49.940> readings<00:32:50.299> as<00:32:50.539> to<00:32:50.779> what<00:32:50.990> each 00:32:51.190 --> 00:32:51.200 align:start position:0% find all the readings as to what each 00:32:51.200 --> 00:32:58.029 align:start position:0% find all the readings as to what each element<00:32:51.710> does<00:32:52.960> after<00:32:53.960> the<00:32:54.049> talk<00:32:56.919> so<00:32:57.919> yeah 00:32:58.029 --> 00:32:58.039 align:start position:0% element does after the talk so yeah 00:32:58.039 --> 00:33:01.600 align:start position:0% element does after the talk so yeah finally<00:32:58.690> the<00:32:59.690> vivo<00:33:00.139> s<00:33:00.320> it<00:33:01.039> has<00:33:01.190> some<00:33:01.369> built-in 00:33:01.600 --> 00:33:01.610 align:start position:0% finally the vivo s it has some built-in 00:33:01.610 --> 00:33:04.710 align:start position:0% finally the vivo s it has some built-in functionalities<00:33:02.409> so<00:33:03.409> crypto<00:33:03.980> API 00:33:04.710 --> 00:33:04.720 align:start position:0% functionalities so crypto API 00:33:04.720 --> 00:33:07.710 align:start position:0% functionalities so crypto API keoki<00:33:05.140> storage<00:33:05.530> secure<00:33:06.429> food<00:33:06.720> communication 00:33:07.710 --> 00:33:07.720 align:start position:0% keoki storage secure food communication 00:33:07.720 --> 00:33:09.299 align:start position:0% keoki storage secure food communication protocol<00:33:08.110> MQ<00:33:08.380> DDS<00:33:08.710> which<00:33:08.890> is<00:33:09.010> the<00:33:09.100> lightweight 00:33:09.299 --> 00:33:09.309 align:start position:0% protocol MQ DDS which is the lightweight 00:33:09.309 --> 00:33:12.360 align:start position:0% protocol MQ DDS which is the lightweight protocol<00:33:09.880> I<00:33:09.909> mentioned<00:33:10.860> then<00:33:11.860> the<00:33:12.010> etherium 00:33:12.360 --> 00:33:12.370 align:start position:0% protocol I mentioned then the etherium 00:33:12.370 --> 00:33:14.159 align:start position:0% protocol I mentioned then the etherium wallet<00:33:12.700> it's<00:33:12.880> an<00:33:13.030> extension<00:33:13.419> to<00:33:13.780> basically 00:33:14.159 --> 00:33:14.169 align:start position:0% wallet it's an extension to basically 00:33:14.169 --> 00:33:17.730 align:start position:0% wallet it's an extension to basically allow<00:33:15.120> these<00:33:16.120> wallets<00:33:16.390> to<00:33:16.690> pay<00:33:16.900> once<00:33:17.350> the<00:33:17.559> data 00:33:17.730 --> 00:33:17.740 align:start position:0% allow these wallets to pay once the data 00:33:17.740 --> 00:33:20.940 align:start position:0% allow these wallets to pay once the data has<00:33:17.830> been<00:33:18.010> attested<00:33:18.990> automatically<00:33:19.990> and<00:33:20.799> then 00:33:20.940 --> 00:33:20.950 align:start position:0% has been attested automatically and then 00:33:20.950 --> 00:33:26.100 align:start position:0% has been attested automatically and then of<00:33:21.039> course<00:33:21.070> the<00:33:21.630> testimony<00:33:24.480> so<00:33:25.480> the<00:33:25.600> testimony 00:33:26.100 --> 00:33:26.110 align:start position:0% of course the testimony so the testimony 00:33:26.110 --> 00:33:28.039 align:start position:0% of course the testimony so the testimony in<00:33:26.380> in<00:33:26.650> simple<00:33:27.070> terms<00:33:27.250> is<00:33:27.429> basically 00:33:28.039 --> 00:33:28.049 align:start position:0% in in simple terms is basically 00:33:28.049 --> 00:33:30.539 align:start position:0% in in simple terms is basically snapshotting<00:33:29.049> microinstructions<00:33:29.860> at 00:33:30.539 --> 00:33:30.549 align:start position:0% snapshotting microinstructions at 00:33:30.549 --> 00:33:32.549 align:start position:0% snapshotting microinstructions at regular<00:33:30.940> intervals<00:33:31.330> and<00:33:31.570> I'm<00:33:32.140> telling 00:33:32.549 --> 00:33:32.559 align:start position:0% regular intervals and I'm telling 00:33:32.559 --> 00:33:36.539 align:start position:0% regular intervals and I'm telling telling<00:33:33.340> the<00:33:33.520> user<00:33:33.640> that<00:33:34.000> the<00:33:34.799> the<00:33:35.799> data<00:33:36.280> which 00:33:36.539 --> 00:33:36.549 align:start position:0% telling the user that the the data which 00:33:36.549 --> 00:33:39.539 align:start position:0% telling the user that the the data which came<00:33:37.210> in<00:33:37.390> and<00:33:37.690> which<00:33:38.080> is<00:33:38.200> going<00:33:38.440> out<00:33:38.650> if<00:33:39.250> it's 00:33:39.539 --> 00:33:39.549 align:start position:0% came in and which is going out if it's 00:33:39.549 --> 00:33:41.190 align:start position:0% came in and which is going out if it's being<00:33:39.760> snapshotted<00:33:40.360> at<00:33:40.450> regular<00:33:40.840> intervals 00:33:41.190 --> 00:33:41.200 align:start position:0% being snapshotted at regular intervals 00:33:41.200 --> 00:33:43.680 align:start position:0% being snapshotted at regular intervals it<00:33:41.350> can<00:33:41.530> be<00:33:41.620> then<00:33:41.770> verified<00:33:42.280> later<00:33:42.580> on<00:33:42.820> when<00:33:43.480> it 00:33:43.680 --> 00:33:43.690 align:start position:0% it can be then verified later on when it 00:33:43.690 --> 00:33:47.460 align:start position:0% it can be then verified later on when it has<00:33:43.870> to<00:33:44.020> be<00:33:44.110> verified<00:33:44.530> basically<00:33:46.140> so<00:33:47.140> we<00:33:47.289> have 00:33:47.460 --> 00:33:47.470 align:start position:0% has to be verified basically so we have 00:33:47.470 --> 00:33:50.970 align:start position:0% has to be verified basically so we have the<00:33:47.650> github<00:33:47.830> code<00:33:48.130> there<00:33:48.669> and<00:33:49.679> of<00:33:50.679> course<00:33:50.890> we 00:33:50.970 --> 00:33:50.980 align:start position:0% the github code there and of course we 00:33:50.980 --> 00:33:52.980 align:start position:0% the github code there and of course we have<00:33:51.070> their<00:33:51.159> own<00:33:51.280> Gator<00:33:51.460> as<00:33:51.640> well<00:33:51.820> if<00:33:52.720> you<00:33:52.840> want 00:33:52.980 --> 00:33:52.990 align:start position:0% have their own Gator as well if you want 00:33:52.990 --> 00:33:54.330 align:start position:0% have their own Gator as well if you want to<00:33:53.049> have<00:33:53.169> a<00:33:53.200> chat<00:33:53.470> with<00:33:53.500> with<00:33:53.890> our<00:33:54.039> team<00:33:54.190> of 00:33:54.330 --> 00:33:54.340 align:start position:0% to have a chat with with our team of 00:33:54.340 --> 00:33:58.130 align:start position:0% to have a chat with with our team of developers<00:33:54.490> as<00:33:55.000> well<00:33:55.030> from<00:33:55.330> Berlin<00:33:56.700> yeah<00:33:57.700> I 00:33:58.130 --> 00:33:58.140 align:start position:0% developers as well from Berlin yeah I 00:33:58.140 --> 00:34:06.110 align:start position:0% developers as well from Berlin yeah I guess<00:33:59.140> that's<00:33:59.470> all<00:33:59.620> thank<00:33:59.950> you<00:34:00.039> so<00:34:00.159> much<00:34:00.309> guys 00:34:06.110 --> 00:34:06.120 align:start position:0% 00:34:06.120 --> 00:34:10.079 align:start position:0% could<00:34:07.120> you<00:34:07.179> please<00:34:07.390> explain<00:34:07.990> a<00:34:08.820> little<00:34:09.820> bit 00:34:10.079 --> 00:34:10.089 align:start position:0% could you please explain a little bit 00:34:10.089 --> 00:34:13.109 align:start position:0% could you please explain a little bit more<00:34:10.659> in<00:34:10.780> deep<00:34:11.310> like<00:34:12.310> Audie<00:34:12.609> attestation 00:34:13.109 --> 00:34:13.119 align:start position:0% more in deep like Audie attestation 00:34:13.119 --> 00:34:15.359 align:start position:0% more in deep like Audie attestation system<00:34:13.629> works<00:34:13.869> like<00:34:14.169> who<00:34:14.649> are<00:34:14.800> we<00:34:14.980> exactly 00:34:15.359 --> 00:34:15.369 align:start position:0% system works like who are we exactly 00:34:15.369 --> 00:34:18.180 align:start position:0% system works like who are we exactly trusting<00:34:16.000> here<00:34:16.619> because<00:34:17.619> it<00:34:17.710> was<00:34:17.889> quite 00:34:18.180 --> 00:34:18.190 align:start position:0% trusting here because it was quite 00:34:18.190 --> 00:34:20.099 align:start position:0% trusting here because it was quite obvious<00:34:18.550> that<00:34:18.580> we<00:34:19.359> are<00:34:19.419> trusting<00:34:19.810> whoever 00:34:20.099 --> 00:34:20.109 align:start position:0% obvious that we are trusting whoever 00:34:20.109 --> 00:34:23.280 align:start position:0% obvious that we are trusting whoever he's<00:34:20.919> manufacturing<00:34:21.159> the<00:34:21.730> chip<00:34:21.909> and<00:34:22.270> the<00:34:23.080> arm 00:34:23.280 --> 00:34:23.290 align:start position:0% he's manufacturing the chip and the arm 00:34:23.290 --> 00:34:26.399 align:start position:0% he's manufacturing the chip and the arm trusts<00:34:23.679> on<00:34:23.770> architecture<00:34:24.720> but<00:34:25.720> where<00:34:26.080> does 00:34:26.399 --> 00:34:26.409 align:start position:0% trusts on architecture but where does 00:34:26.409 --> 00:34:29.369 align:start position:0% trusts on architecture but where does the<00:34:26.770> attestation<00:34:27.760> come<00:34:28.240> from<00:34:28.450> because<00:34:29.139> this 00:34:29.369 --> 00:34:29.379 align:start position:0% the attestation come from because this 00:34:29.379 --> 00:34:30.750 align:start position:0% the attestation come from because this is<00:34:29.530> not<00:34:29.710> something<00:34:30.070> that<00:34:30.099> trusts<00:34:30.550> on<00:34:30.669> the 00:34:30.750 --> 00:34:30.760 align:start position:0% is not something that trusts on the 00:34:30.760 --> 00:34:33.510 align:start position:0% is not something that trusts on the files<00:34:31.200> yeah<00:34:32.200> so<00:34:32.379> the<00:34:32.500> trust<00:34:32.770> own<00:34:32.950> doesn't<00:34:33.220> do 00:34:33.510 --> 00:34:33.520 align:start position:0% files yeah so the trust own doesn't do 00:34:33.520 --> 00:34:35.040 align:start position:0% files yeah so the trust own doesn't do that<00:34:33.669> that's<00:34:33.940> why<00:34:34.089> we<00:34:34.119> build<00:34:34.450> this<00:34:34.720> this 00:34:35.040 --> 00:34:35.050 align:start position:0% that that's why we build this this 00:34:35.050 --> 00:34:37.050 align:start position:0% that that's why we build this this operating<00:34:35.470> system<00:34:35.589> on<00:34:36.099> top<00:34:36.280> which<00:34:36.550> has<00:34:36.730> the 00:34:37.050 --> 00:34:37.060 align:start position:0% operating system on top which has the 00:34:37.060 --> 00:34:39.440 align:start position:0% operating system on top which has the the<00:34:37.389> testimony<00:34:37.780> and<00:34:38.169> the<00:34:38.230> testimony<00:34:38.710> takes 00:34:39.440 --> 00:34:39.450 align:start position:0% the testimony and the testimony takes 00:34:39.450 --> 00:34:43.200 align:start position:0% the testimony and the testimony takes continuous<00:34:40.450> snapshots<00:34:40.990> of<00:34:41.320> the<00:34:42.010> data<00:34:42.210> which 00:34:43.200 --> 00:34:43.210 align:start position:0% continuous snapshots of the data which 00:34:43.210 --> 00:34:45.089 align:start position:0% continuous snapshots of the data which enters<00:34:43.540> the<00:34:43.690> sensors<00:34:44.080> or<00:34:44.260> the<00:34:44.379> processors<00:34:44.859> and 00:34:45.089 --> 00:34:45.099 align:start position:0% enters the sensors or the processors and 00:34:45.099 --> 00:34:49.280 align:start position:0% enters the sensors or the processors and this<00:34:45.399> is<00:34:45.580> where<00:34:45.810> the<00:34:46.810> attestation<00:34:47.770> comes<00:34:48.190> in 00:34:49.280 --> 00:34:49.290 align:start position:0% this is where the attestation comes in 00:34:49.290 --> 00:34:54.480 align:start position:0% this is where the attestation comes in so<00:34:50.290> so<00:34:51.070> next<00:34:51.399> up<00:34:51.669> so<00:34:52.740> these<00:34:53.740> two<00:34:53.889> presentations 00:34:54.480 --> 00:34:54.490 align:start position:0% so so next up so these two presentations 00:34:54.490 --> 00:34:57.480 align:start position:0% so so next up so these two presentations were<00:34:54.639> more<00:34:54.879> like<00:34:55.119> you<00:34:55.240> know<00:34:56.369> getting<00:34:57.369> the 00:34:57.480 --> 00:34:57.490 align:start position:0% were more like you know getting the 00:34:57.490 --> 00:35:00.329 align:start position:0% were more like you know getting the external<00:34:58.119> data<00:34:58.930> either<00:34:59.710> into<00:35:00.010> the<00:35:00.130> chain 00:35:00.329 --> 00:35:00.339 align:start position:0% external data either into the chain 00:35:00.339 --> 00:35:02.579 align:start position:0% external data either into the chain through<00:35:00.609> a<00:35:00.670> transaction<00:35:01.240> or<00:35:01.330> through<00:35:01.630> the 00:35:02.579 --> 00:35:02.589 align:start position:0% through a transaction or through the 00:35:02.589 --> 00:35:05.790 align:start position:0% through a transaction or through the Oracles<00:35:03.210> the<00:35:04.210> next<00:35:04.599> one<00:35:04.810> is<00:35:05.080> around<00:35:05.349> like<00:35:05.650> it 00:35:05.790 --> 00:35:05.800 align:start position:0% Oracles the next one is around like it 00:35:05.800 --> 00:35:09.510 align:start position:0% Oracles the next one is around like it all<00:35:05.920> may<00:35:06.580> be<00:35:06.609> privacy<00:35:07.089> and<00:35:07.510> it's<00:35:08.410> guy<00:35:08.770> here<00:35:09.130> guy 00:35:09.510 --> 00:35:09.520 align:start position:0% all may be privacy and it's guy here guy 00:35:09.520 --> 00:35:12.590 align:start position:0% all may be privacy and it's guy here guy from<00:35:09.790> enigma 00:35:12.590 --> 00:35:12.600 align:start position:0% 00:35:12.600 --> 00:35:15.640 align:start position:0% hello<00:35:13.560> everyone<00:35:13.860> I'm<00:35:14.460> guys<00:35:15.000> this<00:35:15.240> Kent 00:35:15.640 --> 00:35:15.650 align:start position:0% hello everyone I'm guys this Kent 00:35:15.650 --> 00:35:19.790 align:start position:0% hello everyone I'm guys this Kent co-founder<00:35:16.650> and<00:35:16.770> CEO<00:35:16.950> of<00:35:17.160> enigma<00:35:17.660> and<00:35:18.660> I<00:35:19.530> want 00:35:19.790 --> 00:35:19.800 align:start position:0% co-founder and CEO of enigma and I want 00:35:19.800 --> 00:35:20.900 align:start position:0% co-founder and CEO of enigma and I want to<00:35:19.860> tell<00:35:20.010> you<00:35:20.130> about<00:35:20.220> privacy-preserving 00:35:20.900 --> 00:35:20.910 align:start position:0% to tell you about privacy-preserving 00:35:20.910 --> 00:35:23.510 align:start position:0% to tell you about privacy-preserving smart<00:35:21.540> contracts<00:35:22.280> specifically<00:35:23.280> today 00:35:23.510 --> 00:35:23.520 align:start position:0% smart contracts specifically today 00:35:23.520 --> 00:35:25.100 align:start position:0% smart contracts specifically today there's<00:35:24.420> a<00:35:24.480> much<00:35:24.690> longer<00:35:25.080> conversation 00:35:25.100 --> 00:35:25.110 align:start position:0% there's a much longer conversation 00:35:25.110 --> 00:35:27.140 align:start position:0% there's a much longer conversation tomorrow<00:35:26.010> when<00:35:26.190> I'm<00:35:26.310> gonna<00:35:26.460> go<00:35:26.700> much<00:35:26.970> more 00:35:27.140 --> 00:35:27.150 align:start position:0% tomorrow when I'm gonna go much more 00:35:27.150 --> 00:35:29.630 align:start position:0% tomorrow when I'm gonna go much more deeply<00:35:27.600> into<00:35:27.810> the<00:35:27.960> architecture<00:35:28.500> but<00:35:28.710> today<00:35:29.580> I 00:35:29.630 --> 00:35:29.640 align:start position:0% deeply into the architecture but today I 00:35:29.640 --> 00:35:31.400 align:start position:0% deeply into the architecture but today I want<00:35:29.850> to<00:35:29.910> talk<00:35:30.060> to<00:35:30.210> you<00:35:30.300> about<00:35:30.410> some 00:35:31.400 --> 00:35:31.410 align:start position:0% want to talk to you about some 00:35:31.410 --> 00:35:33.110 align:start position:0% want to talk to you about some applications<00:35:32.130> especially<00:35:32.550> those<00:35:33.090> that 00:35:33.110 --> 00:35:33.120 align:start position:0% applications especially those that 00:35:33.120 --> 00:35:35.420 align:start position:0% applications especially those that relate<00:35:33.510> to<00:35:33.570> identity<00:35:34.080> and<00:35:34.380> I'm<00:35:35.100> going<00:35:35.250> to<00:35:35.310> give 00:35:35.420 --> 00:35:35.430 align:start position:0% relate to identity and I'm going to give 00:35:35.430 --> 00:35:37.100 align:start position:0% relate to identity and I'm going to give just<00:35:35.550> a<00:35:35.700> basic<00:35:36.030> overview<00:35:36.150> of<00:35:36.480> the<00:35:36.660> platform 00:35:37.100 --> 00:35:37.110 align:start position:0% just a basic overview of the platform 00:35:37.110 --> 00:35:39.350 align:start position:0% just a basic overview of the platform but<00:35:37.230> again<00:35:37.440> tomorrow<00:35:37.860> is<00:35:38.220> a<00:35:38.250> talk<00:35:38.520> where<00:35:38.790> we're 00:35:39.350 --> 00:35:39.360 align:start position:0% but again tomorrow is a talk where we're 00:35:39.360 --> 00:35:44.570 align:start position:0% but again tomorrow is a talk where we're really<00:35:39.750> deep<00:35:40.020> dive<00:35:40.260> into<00:35:40.470> this<00:35:42.380> so<00:35:43.580> this 00:35:44.570 --> 00:35:44.580 align:start position:0% really deep dive into this so this 00:35:44.580 --> 00:35:45.680 align:start position:0% really deep dive into this so this should<00:35:44.700> be<00:35:44.730> obvious<00:35:44.940> to<00:35:45.180> everyone<00:35:45.480> in<00:35:45.630> this 00:35:45.680 --> 00:35:45.690 align:start position:0% should be obvious to everyone in this 00:35:45.690 --> 00:35:47.930 align:start position:0% should be obvious to everyone in this room<00:35:45.930> block<00:35:46.860> shares<00:35:47.100> are<00:35:47.220> public<00:35:47.520> Ledger's 00:35:47.930 --> 00:35:47.940 align:start position:0% room block shares are public Ledger's 00:35:47.940 --> 00:35:49.880 align:start position:0% room block shares are public Ledger's that<00:35:48.360> means<00:35:48.570> that<00:35:48.780> all<00:35:48.990> data<00:35:49.230> that<00:35:49.470> you<00:35:49.590> put<00:35:49.740> in 00:35:49.880 --> 00:35:49.890 align:start position:0% that means that all data that you put in 00:35:49.890 --> 00:35:51.980 align:start position:0% that means that all data that you put in a<00:35:49.980> smart<00:35:50.220> contract<00:35:50.570> anything<00:35:51.570> that<00:35:51.720> you<00:35:51.810> want 00:35:51.980 --> 00:35:51.990 align:start position:0% a smart contract anything that you want 00:35:51.990 --> 00:35:53.180 align:start position:0% a smart contract anything that you want to<00:35:52.050> process<00:35:52.200> on<00:35:52.470> the<00:35:52.560> blockchain<00:35:52.770> is 00:35:53.180 --> 00:35:53.190 align:start position:0% to process on the blockchain is 00:35:53.190 --> 00:35:55.280 align:start position:0% to process on the blockchain is completely<00:35:54.030> public<00:35:54.420> for<00:35:54.660> everyone<00:35:54.780> to<00:35:55.110> see 00:35:55.280 --> 00:35:55.290 align:start position:0% completely public for everyone to see 00:35:55.290 --> 00:35:57.110 align:start position:0% completely public for everyone to see that<00:35:55.530> means<00:35:56.460> that<00:35:56.670> if<00:35:56.790> you<00:35:56.880> have<00:35:57.000> an 00:35:57.110 --> 00:35:57.120 align:start position:0% that means that if you have an 00:35:57.120 --> 00:35:59.150 align:start position:0% that means that if you have an application<00:35:57.780> that<00:35:57.930> needs<00:35:58.140> to<00:35:58.320> process<00:35:58.530> let's 00:35:59.150 --> 00:35:59.160 align:start position:0% application that needs to process let's 00:35:59.160 --> 00:36:01.880 align:start position:0% application that needs to process let's say<00:35:59.340> your<00:36:00.000> credit<00:36:00.420> card<00:36:00.600> information<00:36:00.890> that's 00:36:01.880 --> 00:36:01.890 align:start position:0% say your credit card information that's 00:36:01.890 --> 00:36:04.100 align:start position:0% say your credit card information that's going<00:36:02.070> to<00:36:02.130> be<00:36:02.190> made<00:36:02.640> available<00:36:02.970> to<00:36:03.690> everyone 00:36:04.100 --> 00:36:04.110 align:start position:0% going to be made available to everyone 00:36:04.110 --> 00:36:06.230 align:start position:0% going to be made available to everyone in<00:36:04.590> the<00:36:04.770> world<00:36:04.800> and<00:36:05.280> that's<00:36:05.670> obviously 00:36:06.230 --> 00:36:06.240 align:start position:0% in the world and that's obviously 00:36:06.240 --> 00:36:09.470 align:start position:0% in the world and that's obviously unacceptable<00:36:07.280> which<00:36:08.280> greatly<00:36:09.000> limit<00:36:09.390> the 00:36:09.470 --> 00:36:09.480 align:start position:0% unacceptable which greatly limit the 00:36:09.480 --> 00:36:10.790 align:start position:0% unacceptable which greatly limit the type<00:36:09.660> of<00:36:09.780> applications<00:36:10.410> that<00:36:10.470> you<00:36:10.560> can 00:36:10.790 --> 00:36:10.800 align:start position:0% type of applications that you can 00:36:10.800 --> 00:36:12.920 align:start position:0% type of applications that you can actually<00:36:11.010> do<00:36:11.400> on<00:36:11.430> the<00:36:11.580> blockchain<00:36:11.820> and<00:36:12.750> I 00:36:12.920 --> 00:36:12.930 align:start position:0% actually do on the blockchain and I 00:36:12.930 --> 00:36:15.560 align:start position:0% actually do on the blockchain and I would<00:36:13.110> even<00:36:13.200> go<00:36:13.650> further<00:36:13.980> and<00:36:14.160> say<00:36:14.490> that<00:36:14.570> there 00:36:15.560 --> 00:36:15.570 align:start position:0% would even go further and say that there 00:36:15.570 --> 00:36:17.690 align:start position:0% would even go further and say that there are<00:36:15.660> only<00:36:15.780> I'd<00:36:16.380> say<00:36:16.590> maybe<00:36:16.860> a<00:36:16.980> couple<00:36:17.430> of<00:36:17.550> good 00:36:17.690 --> 00:36:17.700 align:start position:0% are only I'd say maybe a couple of good 00:36:17.700 --> 00:36:19.820 align:start position:0% are only I'd say maybe a couple of good applications<00:36:18.270> that<00:36:18.390> I<00:36:18.570> can<00:36:18.870> think<00:36:19.020> of<00:36:19.320> that 00:36:19.820 --> 00:36:19.830 align:start position:0% applications that I can think of that 00:36:19.830 --> 00:36:22.520 align:start position:0% applications that I can think of that make<00:36:20.070> sense<00:36:20.490> on<00:36:21.150> the<00:36:21.450> blockchain<00:36:21.780> without 00:36:22.520 --> 00:36:22.530 align:start position:0% make sense on the blockchain without 00:36:22.530 --> 00:36:27.230 align:start position:0% make sense on the blockchain without solving<00:36:22.950> for<00:36:23.130> privacy<00:36:23.490> so<00:36:26.090> that's<00:36:27.090> really 00:36:27.230 --> 00:36:27.240 align:start position:0% solving for privacy so that's really 00:36:27.240 --> 00:36:29.870 align:start position:0% solving for privacy so that's really where<00:36:27.450> enigma<00:36:28.080> comes<00:36:28.470> in<00:36:28.650> our<00:36:29.340> goal<00:36:29.640> is<00:36:29.850> really 00:36:29.870 --> 00:36:29.880 align:start position:0% where enigma comes in our goal is really 00:36:29.880 --> 00:36:32.630 align:start position:0% where enigma comes in our goal is really to<00:36:30.210> allow<00:36:30.720> nodes<00:36:31.380> in<00:36:31.740> a<00:36:31.830> distributed<00:36:32.280> network 00:36:32.630 --> 00:36:32.640 align:start position:0% to allow nodes in a distributed network 00:36:32.640 --> 00:36:35.900 align:start position:0% to allow nodes in a distributed network to<00:36:33.270> operate<00:36:33.810> over<00:36:34.050> encrypted<00:36:34.560> data<00:36:34.910> that 00:36:35.900 --> 00:36:35.910 align:start position:0% to operate over encrypted data that 00:36:35.910 --> 00:36:38.330 align:start position:0% to operate over encrypted data that gives<00:36:36.150> us<00:36:36.270> the<00:36:36.390> privacy<00:36:36.650> we<00:36:37.650> essentially<00:36:38.070> want 00:36:38.330 --> 00:36:38.340 align:start position:0% gives us the privacy we essentially want 00:36:38.340 --> 00:36:41.330 align:start position:0% gives us the privacy we essentially want to<00:36:38.460> upgrade<00:36:38.760> smart<00:36:39.540> contracts<00:36:40.230> into<00:36:40.650> secret 00:36:41.330 --> 00:36:41.340 align:start position:0% to upgrade smart contracts into secret 00:36:41.340 --> 00:36:43.400 align:start position:0% to upgrade smart contracts into secret contracts<00:36:41.910> secret<00:36:42.630> contracts<00:36:43.110> are<00:36:43.200> just 00:36:43.400 --> 00:36:43.410 align:start position:0% contracts secret contracts are just 00:36:43.410 --> 00:36:45.230 align:start position:0% contracts secret contracts are just plain<00:36:43.920> smart<00:36:44.280> contracts<00:36:44.760> but<00:36:44.880> they<00:36:45.030> also 00:36:45.230 --> 00:36:45.240 align:start position:0% plain smart contracts but they also 00:36:45.240 --> 00:36:51.620 align:start position:0% plain smart contracts but they also protect<00:36:46.200> data<00:36:46.730> in<00:36:47.730> transit<00:36:48.330> any<00:36:48.660> news<00:36:50.510> if<00:36:51.510> you 00:36:51.620 --> 00:36:51.630 align:start position:0% protect data in transit any news if you 00:36:51.630 --> 00:36:53.990 align:start position:0% protect data in transit any news if you want<00:36:51.810> to<00:36:51.870> be<00:36:51.960> a<00:36:51.990> bit<00:36:52.200> more<00:36:52.790> technical<00:36:53.790> about 00:36:53.990 --> 00:36:54.000 align:start position:0% want to be a bit more technical about 00:36:54.000 --> 00:36:56.090 align:start position:0% want to be a bit more technical about these<00:36:54.350> smart<00:36:55.350> contracts<00:36:55.800> provide 00:36:56.090 --> 00:36:56.100 align:start position:0% these smart contracts provide 00:36:56.100 --> 00:36:58.010 align:start position:0% these smart contracts provide correctness<00:36:56.610> that's<00:36:57.180> really<00:36:57.510> what<00:36:57.690> excites 00:36:58.010 --> 00:36:58.020 align:start position:0% correctness that's really what excites 00:36:58.020 --> 00:36:59.420 align:start position:0% correctness that's really what excites us<00:36:58.620> in<00:36:58.830> blockchains 00:36:59.420 --> 00:36:59.430 align:start position:0% us in blockchains 00:36:59.430 --> 00:37:02.210 align:start position:0% us in blockchains the<00:36:59.610> fact<00:36:59.880> that<00:37:00.110> if<00:37:01.110> you<00:37:01.380> put<00:37:01.710> the<00:37:01.830> code<00:37:02.010> on<00:37:02.040> the 00:37:02.210 --> 00:37:02.220 align:start position:0% the fact that if you put the code on the 00:37:02.220 --> 00:37:04.250 align:start position:0% the fact that if you put the code on the blockchain<00:37:02.520> and<00:37:02.820> it<00:37:03.180> sends<00:37:03.390> some<00:37:03.570> data<00:37:03.810> into 00:37:04.250 --> 00:37:04.260 align:start position:0% blockchain and it sends some data into 00:37:04.260 --> 00:37:06.560 align:start position:0% blockchain and it sends some data into it<00:37:04.410> you're<00:37:04.950> gonna<00:37:05.130> get<00:37:05.430> the<00:37:05.910> correct<00:37:06.360> result 00:37:06.560 --> 00:37:06.570 align:start position:0% it you're gonna get the correct result 00:37:06.570 --> 00:37:09.320 align:start position:0% it you're gonna get the correct result and<00:37:07.050> you<00:37:07.860> know<00:37:07.980> no<00:37:08.280> one<00:37:08.430> can<00:37:08.460> tamper<00:37:08.850> with<00:37:09.150> it 00:37:09.320 --> 00:37:09.330 align:start position:0% and you know no one can tamper with it 00:37:09.330 --> 00:37:13.430 align:start position:0% and you know no one can tamper with it assuming<00:37:09.930> you<00:37:10.020> trust<00:37:10.290> the<00:37:10.470> the<00:37:11.210> the<00:37:12.210> model<00:37:12.510> so 00:37:13.430 --> 00:37:13.440 align:start position:0% assuming you trust the the the model so 00:37:13.440 --> 00:37:14.870 align:start position:0% assuming you trust the the the model so that's<00:37:13.680> great<00:37:13.860> and<00:37:14.010> that's<00:37:14.250> why<00:37:14.430> we're 00:37:14.870 --> 00:37:14.880 align:start position:0% that's great and that's why we're 00:37:14.880 --> 00:37:16.670 align:start position:0% that's great and that's why we're excited<00:37:14.970> about<00:37:15.270> blockchains<00:37:15.870> but<00:37:16.470> these 00:37:16.670 --> 00:37:16.680 align:start position:0% excited about blockchains but these 00:37:16.680 --> 00:37:18.680 align:start position:0% excited about blockchains but these doesn't<00:37:17.010> protect<00:37:17.250> privacy<00:37:17.640> and<00:37:18.030> that's<00:37:18.420> where 00:37:18.680 --> 00:37:18.690 align:start position:0% doesn't protect privacy and that's where 00:37:18.690 --> 00:37:23.090 align:start position:0% doesn't protect privacy and that's where secret<00:37:19.170> contracts<00:37:19.680> coming 00:37:23.090 --> 00:37:23.100 align:start position:0% 00:37:23.100 --> 00:37:25.940 align:start position:0% so<00:37:24.060> we<00:37:24.180> have<00:37:24.300> a<00:37:24.330> nygma<00:37:24.630> discovery<00:37:25.110> discovery 00:37:25.940 --> 00:37:25.950 align:start position:0% so we have a nygma discovery discovery 00:37:25.950 --> 00:37:28.670 align:start position:0% so we have a nygma discovery discovery is<00:37:26.040> meant<00:37:26.280> to<00:37:26.400> be<00:37:26.550> the<00:37:26.850> first<00:37:27.120> network<00:37:27.680> that 00:37:28.670 --> 00:37:28.680 align:start position:0% is meant to be the first network that 00:37:28.680 --> 00:37:30.980 align:start position:0% is meant to be the first network that we're<00:37:28.860> releasing<00:37:29.100> we<00:37:30.060> have<00:37:30.270> a<00:37:30.300> version<00:37:30.600> out 00:37:30.980 --> 00:37:30.990 align:start position:0% we're releasing we have a version out 00:37:30.990 --> 00:37:33.110 align:start position:0% we're releasing we have a version out right<00:37:31.260> now<00:37:31.440> it's<00:37:31.770> public<00:37:32.100> the<00:37:32.610> code<00:37:32.790> is<00:37:32.970> open 00:37:33.110 --> 00:37:33.120 align:start position:0% right now it's public the code is open 00:37:33.120 --> 00:37:36.560 align:start position:0% right now it's public the code is open we<00:37:34.050> have<00:37:34.080> several<00:37:34.770> companies<00:37:35.220> that<00:37:35.730> are<00:37:36.210> very 00:37:36.560 --> 00:37:36.570 align:start position:0% we have several companies that are very 00:37:36.570 --> 00:37:38.710 align:start position:0% we have several companies that are very well-known<00:37:36.780> in<00:37:36.960> the<00:37:37.200> space<00:37:37.440> building<00:37:37.950> on<00:37:38.250> us 00:37:38.710 --> 00:37:38.720 align:start position:0% well-known in the space building on us 00:37:38.720 --> 00:37:41.690 align:start position:0% well-known in the space building on us using<00:37:39.720> our<00:37:39.840> technologies<00:37:40.350> and<00:37:40.700> we're 00:37:41.690 --> 00:37:41.700 align:start position:0% using our technologies and we're 00:37:41.700 --> 00:37:42.980 align:start position:0% using our technologies and we're actually<00:37:41.850> making<00:37:42.120> some<00:37:42.570> more<00:37:42.750> improvements 00:37:42.980 --> 00:37:42.990 align:start position:0% actually making some more improvements 00:37:42.990 --> 00:37:47.590 align:start position:0% actually making some more improvements and<00:37:43.590> we<00:37:43.680> really<00:37:43.890> release<00:37:44.220> I'd<00:37:44.850> say<00:37:45.090> discovery 00:37:47.590 --> 00:37:47.600 align:start position:0% and we really release I'd say discovery 00:37:47.600 --> 00:37:50.720 align:start position:0% and we really release I'd say discovery 2.0<00:37:48.600> in<00:37:49.080> the<00:37:49.290> next<00:37:49.500> couple<00:37:49.800> of<00:37:49.860> months<00:37:50.250> with<00:37:50.520> a 00:37:50.720 --> 00:37:50.730 align:start position:0% 2.0 in the next couple of months with a 00:37:50.730 --> 00:37:53.390 align:start position:0% 2.0 in the next couple of months with a lot<00:37:50.970> more<00:37:51.180> features<00:37:51.360> and<00:37:52.190> discovery<00:37:53.190> really 00:37:53.390 --> 00:37:53.400 align:start position:0% lot more features and discovery really 00:37:53.400 --> 00:37:56.540 align:start position:0% lot more features and discovery really means<00:37:53.760> that<00:37:54.140> all<00:37:55.140> nodes<00:37:55.530> in<00:37:55.710> the<00:37:55.800> network<00:37:56.220> have 00:37:56.540 --> 00:37:56.550 align:start position:0% means that all nodes in the network have 00:37:56.550 --> 00:37:59.840 align:start position:0% means that all nodes in the network have to<00:37:56.670> run<00:37:56.790> Intel<00:37:57.090> HD<00:37:57.180> X<00:37:58.400> intelligence<00:37:59.400> provides 00:37:59.840 --> 00:37:59.850 align:start position:0% to run Intel HD X intelligence provides 00:37:59.850 --> 00:38:03.260 align:start position:0% to run Intel HD X intelligence provides us<00:38:00.120> the<00:38:00.600> infrastructure<00:38:01.410> where<00:38:02.190> we<00:38:02.400> can<00:38:02.730> run 00:38:03.260 --> 00:38:03.270 align:start position:0% us the infrastructure where we can run 00:38:03.270 --> 00:38:06.440 align:start position:0% us the infrastructure where we can run code<00:38:03.690> securely<00:38:04.620> both<00:38:05.370> for<00:38:05.640> correctness<00:38:06.060> and 00:38:06.440 --> 00:38:06.450 align:start position:0% code securely both for correctness and 00:38:06.450 --> 00:38:09.500 align:start position:0% code securely both for correctness and privacy<00:38:07.260> and<00:38:07.650> I<00:38:08.490> do<00:38:08.550> I'm<00:38:08.940> not<00:38:09.090> going<00:38:09.270> to<00:38:09.360> get 00:38:09.500 --> 00:38:09.510 align:start position:0% privacy and I do I'm not going to get 00:38:09.510 --> 00:38:11.540 align:start position:0% privacy and I do I'm not going to get into<00:38:09.840> that<00:38:09.960> here<00:38:10.170> but<00:38:10.380> we<00:38:10.500> don't<00:38:10.950> just<00:38:11.280> rely<00:38:11.520> on 00:38:11.540 --> 00:38:11.550 align:start position:0% into that here but we don't just rely on 00:38:11.550 --> 00:38:15.010 align:start position:0% into that here but we don't just rely on IntelliJ<00:38:12.180> X<00:38:12.390> we<00:38:13.170> rely<00:38:13.440> on<00:38:13.470> other<00:38:13.950> things<00:38:14.070> like 00:38:15.010 --> 00:38:15.020 align:start position:0% IntelliJ X we rely on other things like 00:38:15.020 --> 00:38:18.080 align:start position:0% IntelliJ X we rely on other things like a<00:38:16.020> female<00:38:16.230> for<00:38:16.560> consensus<00:38:17.100> but<00:38:17.760> the<00:38:17.880> main<00:38:18.060> idea 00:38:18.080 --> 00:38:18.090 align:start position:0% a female for consensus but the main idea 00:38:18.090 --> 00:38:21.380 align:start position:0% a female for consensus but the main idea for<00:38:18.420> that<00:38:18.840> for<00:38:19.170> privacy<00:38:19.590> right<00:38:20.100> now<00:38:20.310> we<00:38:21.240> get 00:38:21.380 --> 00:38:21.390 align:start position:0% for that for privacy right now we get 00:38:21.390 --> 00:38:24.470 align:start position:0% for that for privacy right now we get data<00:38:22.080> from<00:38:22.260> a<00:38:22.350> CX<00:38:22.640> other<00:38:23.640> properties<00:38:24.240> that<00:38:24.360> are 00:38:24.470 --> 00:38:24.480 align:start position:0% data from a CX other properties that are 00:38:24.480 --> 00:38:26.660 align:start position:0% data from a CX other properties that are interesting<00:38:25.020> and<00:38:25.290> this<00:38:25.890> is<00:38:26.070> the<00:38:26.280> first 00:38:26.660 --> 00:38:26.670 align:start position:0% interesting and this is the first 00:38:26.670 --> 00:38:29.690 align:start position:0% interesting and this is the first network<00:38:27.090> of<00:38:27.240> its<00:38:27.360> kind<00:38:27.600> is<00:38:27.960> that<00:38:28.580> discovery<00:38:29.580> is 00:38:29.690 --> 00:38:29.700 align:start position:0% network of its kind is that discovery is 00:38:29.700 --> 00:38:32.300 align:start position:0% network of its kind is that discovery is completely<00:38:30.150> permissionless<00:38:31.070> anyone<00:38:32.070> can 00:38:32.300 --> 00:38:32.310 align:start position:0% completely permissionless anyone can 00:38:32.310 --> 00:38:35.690 align:start position:0% completely permissionless anyone can join<00:38:32.520> can<00:38:32.880> become<00:38:33.180> a<00:38:33.240> node<00:38:33.830> and<00:38:34.830> get<00:38:35.160> rewards 00:38:35.690 --> 00:38:35.700 align:start position:0% join can become a node and get rewards 00:38:35.700 --> 00:38:38.960 align:start position:0% join can become a node and get rewards it's<00:38:36.660> completely<00:38:37.200> economically<00:38:37.970> incentivize 00:38:38.960 --> 00:38:38.970 align:start position:0% it's completely economically incentivize 00:38:38.970 --> 00:38:43.100 align:start position:0% it's completely economically incentivize it<00:38:39.780> uses<00:38:40.230> some<00:38:40.410> kind<00:38:40.680> of<00:38:40.740> POS<00:38:41.220> model<00:38:41.640> and<00:38:42.110> I 00:38:43.100 --> 00:38:43.110 align:start position:0% it uses some kind of POS model and I 00:38:43.110 --> 00:38:44.570 align:start position:0% it uses some kind of POS model and I think<00:38:43.470> what's<00:38:43.620> mostly<00:38:43.980> interesting<00:38:44.430> for 00:38:44.570 --> 00:38:44.580 align:start position:0% think what's mostly interesting for 00:38:44.580 --> 00:38:47.120 align:start position:0% think what's mostly interesting for developers<00:38:45.210> in<00:38:45.690> this<00:38:45.990> conference<00:38:46.470> is<00:38:46.770> that 00:38:47.120 --> 00:38:47.130 align:start position:0% developers in this conference is that 00:38:47.130 --> 00:38:49.790 align:start position:0% developers in this conference is that it's<00:38:47.850> a<00:38:48.090> hundred<00:38:48.450> percent<00:38:48.650> compatible<00:38:49.650> with 00:38:49.790 --> 00:38:49.800 align:start position:0% it's a hundred percent compatible with 00:38:49.800 --> 00:38:52.520 align:start position:0% it's a hundred percent compatible with the<00:38:49.890> film<00:38:50.370> that<00:38:51.120> means<00:38:51.420> that<00:38:51.780> you<00:38:52.110> know<00:38:52.230> if<00:38:52.260> you 00:38:52.520 --> 00:38:52.530 align:start position:0% the film that means that you know if you 00:38:52.530 --> 00:38:54.350 align:start position:0% the film that means that you know if you want<00:38:52.770> to<00:38:52.860> enjoy<00:38:53.190> the<00:38:53.340> security<00:38:53.850> of<00:38:53.880> aetherium 00:38:54.350 --> 00:38:54.360 align:start position:0% want to enjoy the security of aetherium 00:38:54.360 --> 00:38:56.540 align:start position:0% want to enjoy the security of aetherium if<00:38:54.480> you<00:38:54.540> want<00:38:54.750> to<00:38:54.840> continue<00:38:55.500> to<00:38:56.070> develop<00:38:56.220> a 00:38:56.540 --> 00:38:56.550 align:start position:0% if you want to continue to develop a 00:38:56.550 --> 00:38:58.340 align:start position:0% if you want to continue to develop a decentralized<00:38:57.120> applications<00:38:57.270> on<00:38:57.840> aetherium 00:38:58.340 --> 00:38:58.350 align:start position:0% decentralized applications on aetherium 00:38:58.350 --> 00:39:00.650 align:start position:0% decentralized applications on aetherium that's<00:38:59.070> fine<00:38:59.400> by<00:38:59.610> all<00:38:59.790> means<00:38:59.820> we're<00:39:00.540> not 00:39:00.650 --> 00:39:00.660 align:start position:0% that's fine by all means we're not 00:39:00.660 --> 00:39:03.440 align:start position:0% that's fine by all means we're not trying<00:39:01.100> we're<00:39:02.100> not<00:39:02.250> trying<00:39:02.520> to<00:39:02.580> compete<00:39:02.820> or<00:39:03.300> to 00:39:03.440 --> 00:39:03.450 align:start position:0% trying we're not trying to compete or to 00:39:03.450 --> 00:39:05.600 align:start position:0% trying we're not trying to compete or to change<00:39:03.690> your<00:39:03.870> habits<00:39:04.020> but<00:39:04.920> if<00:39:05.160> there<00:39:05.400> are 00:39:05.600 --> 00:39:05.610 align:start position:0% change your habits but if there are 00:39:05.610 --> 00:39:07.880 align:start position:0% change your habits but if there are portions<00:39:06.360> of<00:39:06.690> your<00:39:06.840> applications<00:39:07.500> that<00:39:07.680> need 00:39:07.880 --> 00:39:07.890 align:start position:0% portions of your applications that need 00:39:07.890 --> 00:39:10.100 align:start position:0% portions of your applications that need to<00:39:08.040> process<00:39:08.310> sensitive<00:39:08.910> data<00:39:09.120> where<00:39:09.900> we 00:39:10.100 --> 00:39:10.110 align:start position:0% to process sensitive data where we 00:39:10.110 --> 00:39:12.530 align:start position:0% to process sensitive data where we provided<00:39:10.500> the<00:39:10.740> means<00:39:10.920> to<00:39:11.190> actually<00:39:11.370> go<00:39:12.330> from 00:39:12.530 --> 00:39:12.540 align:start position:0% provided the means to actually go from 00:39:12.540 --> 00:39:16.220 align:start position:0% provided the means to actually go from aetherium<00:39:13.140> to<00:39:13.830> securely<00:39:14.610> compute<00:39:15.420> on<00:39:15.720> enigma 00:39:16.220 --> 00:39:16.230 align:start position:0% aetherium to securely compute on enigma 00:39:16.230 --> 00:39:18.230 align:start position:0% aetherium to securely compute on enigma and<00:39:16.410> then<00:39:16.650> back<00:39:16.890> to<00:39:16.920> a<00:39:17.100> theorem<00:39:17.490> and<00:39:17.700> we<00:39:18.060> make 00:39:18.230 --> 00:39:18.240 align:start position:0% and then back to a theorem and we make 00:39:18.240 --> 00:39:20.180 align:start position:0% and then back to a theorem and we make that<00:39:18.270> very<00:39:18.630> easy<00:39:18.960> for<00:39:19.200> developers<00:39:19.350> and<00:39:20.010> very 00:39:20.180 --> 00:39:20.190 align:start position:0% that very easy for developers and very 00:39:20.190 --> 00:39:26.900 align:start position:0% that very easy for developers and very seamless<00:39:20.700> for<00:39:20.940> the<00:39:21.060> users<00:39:25.790> so<00:39:26.790> the 00:39:26.900 --> 00:39:26.910 align:start position:0% seamless for the users so the 00:39:26.910 --> 00:39:29.390 align:start position:0% seamless for the users so the architecture<00:39:27.330> at<00:39:28.020> a<00:39:28.050> very<00:39:28.380> high<00:39:28.680> level<00:39:28.860> is 00:39:29.390 --> 00:39:29.400 align:start position:0% architecture at a very high level is 00:39:29.400 --> 00:39:31.970 align:start position:0% architecture at a very high level is very<00:39:29.790> similar<00:39:30.090> to<00:39:30.450> how<00:39:30.630> blockers<00:39:31.620> work<00:39:31.830> today 00:39:31.970 --> 00:39:31.980 align:start position:0% very similar to how blockers work today 00:39:31.980 --> 00:39:35.690 align:start position:0% very similar to how blockers work today you<00:39:32.760> have<00:39:33.110> not<00:39:34.110> shown<00:39:34.350> here<00:39:34.410> you<00:39:34.740> have<00:39:34.950> smart 00:39:35.690 --> 00:39:35.700 align:start position:0% you have not shown here you have smart 00:39:35.700 --> 00:39:36.470 align:start position:0% you have not shown here you have smart you<00:39:35.880> have<00:39:35.910> developed 00:39:36.470 --> 00:39:36.480 align:start position:0% you have developed 00:39:36.480 --> 00:39:39.500 align:start position:0% you have developed who<00:39:37.170> basically<00:39:37.380> write<00:39:37.950> secret<00:39:38.790> contracts<00:39:39.359> and 00:39:39.500 --> 00:39:39.510 align:start position:0% who basically write secret contracts and 00:39:39.510 --> 00:39:41.690 align:start position:0% who basically write secret contracts and deployed<00:39:40.200> that<00:39:40.440> to<00:39:40.589> the<00:39:40.710> Enigma<00:39:41.040> network<00:39:41.430> and 00:39:41.690 --> 00:39:41.700 align:start position:0% deployed that to the Enigma network and 00:39:41.700 --> 00:39:45.260 align:start position:0% deployed that to the Enigma network and then<00:39:42.240> you<00:39:42.359> have<00:39:42.540> users<00:39:43.140> that<00:39:44.270> communicate 00:39:45.260 --> 00:39:45.270 align:start position:0% then you have users that communicate 00:39:45.270 --> 00:39:47.270 align:start position:0% then you have users that communicate with<00:39:45.990> those<00:39:46.200> secret<00:39:46.560> contracts<00:39:47.040> from<00:39:47.160> the 00:39:47.270 --> 00:39:47.280 align:start position:0% with those secret contracts from the 00:39:47.280 --> 00:39:50.900 align:start position:0% with those secret contracts from the outside<00:39:48.200> by<00:39:49.200> sending<00:39:49.710> tasks<00:39:50.220> tasks<00:39:50.670> for 00:39:50.900 --> 00:39:50.910 align:start position:0% outside by sending tasks tasks for 00:39:50.910 --> 00:39:52.970 align:start position:0% outside by sending tasks tasks for basically<00:39:51.240> special<00:39:51.690> transactions<00:39:52.380> that 00:39:52.970 --> 00:39:52.980 align:start position:0% basically special transactions that 00:39:52.980 --> 00:39:56.680 align:start position:0% basically special transactions that include<00:39:53.430> encrypted<00:39:54.390> inputs<00:39:55.290> as<00:39:55.530> payload<00:39:55.859> and 00:39:56.680 --> 00:39:56.690 align:start position:0% include encrypted inputs as payload and 00:39:56.690 --> 00:39:59.960 align:start position:0% include encrypted inputs as payload and that's<00:39:57.690> really<00:39:57.900> and<00:39:58.619> in<00:39:58.829> the<00:39:58.980> middle<00:39:59.369> that's 00:39:59.960 --> 00:39:59.970 align:start position:0% that's really and in the middle that's 00:39:59.970 --> 00:40:03.290 align:start position:0% that's really and in the middle that's really<00:40:00.270> where<00:40:00.450> all<00:40:00.599> the<00:40:00.750> magic<00:40:00.900> happens<00:40:02.300> in 00:40:03.290 --> 00:40:03.300 align:start position:0% really where all the magic happens in 00:40:03.300 --> 00:40:08.450 align:start position:0% really where all the magic happens in our<00:40:03.510> network<00:40:03.900> so<00:40:06.740> I<00:40:07.740> think<00:40:08.040> this<00:40:08.310> is<00:40:08.430> a 00:40:08.450 --> 00:40:08.460 align:start position:0% our network so I think this is a 00:40:08.460 --> 00:40:10.760 align:start position:0% our network so I think this is a statement<00:40:08.760> everyone<00:40:09.540> would<00:40:09.690> agree<00:40:09.780> modern 00:40:10.760 --> 00:40:10.770 align:start position:0% statement everyone would agree modern 00:40:10.770 --> 00:40:11.930 align:start position:0% statement everyone would agree modern applications<00:40:11.339> require<00:40:11.640> the<00:40:11.790> use<00:40:11.880> of 00:40:11.930 --> 00:40:11.940 align:start position:0% applications require the use of 00:40:11.940 --> 00:40:13.940 align:start position:0% applications require the use of sensitive<00:40:12.420> data<00:40:12.570> that's<00:40:13.079> not<00:40:13.349> something<00:40:13.800> we 00:40:13.940 --> 00:40:13.950 align:start position:0% sensitive data that's not something we 00:40:13.950 --> 00:40:15.859 align:start position:0% sensitive data that's not something we can<00:40:14.099> debate<00:40:14.280> or<00:40:14.730> change<00:40:15.030> or<00:40:15.329> even<00:40:15.480> want<00:40:15.780> to 00:40:15.859 --> 00:40:15.869 align:start position:0% can debate or change or even want to 00:40:15.869 --> 00:40:18.859 align:start position:0% can debate or change or even want to change<00:40:16.579> and<00:40:17.579> I'm<00:40:18.089> gonna<00:40:18.329> talk<00:40:18.599> to<00:40:18.750> you<00:40:18.810> about 00:40:18.859 --> 00:40:18.869 align:start position:0% change and I'm gonna talk to you about 00:40:18.869 --> 00:40:21.710 align:start position:0% change and I'm gonna talk to you about one<00:40:19.230> specific<00:40:19.920> example<00:40:20.369> in<00:40:21.030> the<00:40:21.089> identity 00:40:21.710 --> 00:40:21.720 align:start position:0% one specific example in the identity 00:40:21.720 --> 00:40:23.780 align:start position:0% one specific example in the identity space<00:40:21.839> that<00:40:22.770> we've<00:40:22.980> been<00:40:23.160> working<00:40:23.670> on 00:40:23.780 --> 00:40:23.790 align:start position:0% space that we've been working on 00:40:23.790 --> 00:40:25.940 align:start position:0% space that we've been working on together<00:40:24.540> with<00:40:24.839> a<00:40:24.900> company<00:40:25.410> called<00:40:25.440> data 00:40:25.940 --> 00:40:25.950 align:start position:0% together with a company called data 00:40:25.950 --> 00:40:29.870 align:start position:0% together with a company called data wallet<00:40:26.900> so<00:40:27.900> it's<00:40:28.710> pretty<00:40:28.859> common<00:40:29.190> today<00:40:29.430> on 00:40:29.870 --> 00:40:29.880 align:start position:0% wallet so it's pretty common today on 00:40:29.880 --> 00:40:30.710 align:start position:0% wallet so it's pretty common today on the<00:40:30.060> Internet 00:40:30.710 --> 00:40:30.720 align:start position:0% the Internet 00:40:30.720 --> 00:40:33.170 align:start position:0% the Internet that<00:40:31.140> you<00:40:31.530> know<00:40:31.619> before<00:40:31.980> you<00:40:32.190> subscribe<00:40:32.820> to<00:40:33.089> an 00:40:33.170 --> 00:40:33.180 align:start position:0% that you know before you subscribe to an 00:40:33.180 --> 00:40:34.819 align:start position:0% that you know before you subscribe to an application<00:40:33.570> before<00:40:34.050> you<00:40:34.170> can<00:40:34.380> use<00:40:34.589> some<00:40:34.800> kind 00:40:34.819 --> 00:40:34.829 align:start position:0% application before you can use some kind 00:40:34.829 --> 00:40:37.700 align:start position:0% application before you can use some kind of<00:40:35.070> application<00:40:35.700> you<00:40:36.270> have<00:40:36.300> a<00:40:36.510> gateway<00:40:36.810> that 00:40:37.700 --> 00:40:37.710 align:start position:0% of application you have a gateway that 00:40:37.710 --> 00:40:39.800 align:start position:0% of application you have a gateway that Gateway<00:40:38.280> needs<00:40:38.550> to<00:40:38.700> make<00:40:38.849> sure<00:40:39.089> that<00:40:39.450> you<00:40:39.720> know 00:40:39.800 --> 00:40:39.810 align:start position:0% Gateway needs to make sure that you know 00:40:39.810 --> 00:40:41.690 align:start position:0% Gateway needs to make sure that you know you're<00:40:39.990> not<00:40:40.079> trying<00:40:40.290> to<00:40:40.619> game<00:40:40.859> the<00:40:40.890> system<00:40:41.099> and 00:40:41.690 --> 00:40:41.700 align:start position:0% you're not trying to game the system and 00:40:41.700 --> 00:40:44.450 align:start position:0% you're not trying to game the system and that<00:40:42.569> you're<00:40:42.750> not<00:40:42.839> trying<00:40:43.109> to<00:40:43.349> mount<00:40:44.160> some 00:40:44.450 --> 00:40:44.460 align:start position:0% that you're not trying to mount some 00:40:44.460 --> 00:40:46.760 align:start position:0% that you're not trying to mount some Sybil<00:40:44.790> attack<00:40:45.089> it<00:40:45.780> needs<00:40:46.050> to<00:40:46.200> verify<00:40:46.410> that 00:40:46.760 --> 00:40:46.770 align:start position:0% Sybil attack it needs to verify that 00:40:46.770 --> 00:40:50.089 align:start position:0% Sybil attack it needs to verify that you're<00:40:47.220> a<00:40:47.250> person<00:40:47.579> and<00:40:48.119> your<00:40:49.109> one<00:40:49.800> unique 00:40:50.089 --> 00:40:50.099 align:start position:0% you're a person and your one unique 00:40:50.099 --> 00:40:51.500 align:start position:0% you're a person and your one unique person<00:40:50.490> that<00:40:50.640> you're<00:40:50.760> not<00:40:50.880> creating<00:40:51.329> let's 00:40:51.500 --> 00:40:51.510 align:start position:0% person that you're not creating let's 00:40:51.510 --> 00:40:54.319 align:start position:0% person that you're not creating let's say<00:40:51.660> a<00:40:51.690> thousand<00:40:52.380> fake<00:40:52.589> accounts<00:40:53.329> that's 00:40:54.319 --> 00:40:54.329 align:start position:0% say a thousand fake accounts that's 00:40:54.329 --> 00:40:57.200 align:start position:0% say a thousand fake accounts that's prevalent<00:40:54.660> in<00:40:55.550> centralized<00:40:56.550> systems<00:40:56.940> but 00:40:57.200 --> 00:40:57.210 align:start position:0% prevalent in centralized systems but 00:40:57.210 --> 00:40:59.510 align:start position:0% prevalent in centralized systems but also<00:40:57.270> decentralized<00:40:58.200> ones<00:40:58.410> so<00:40:59.220> we're<00:40:59.369> working 00:40:59.510 --> 00:40:59.520 align:start position:0% also decentralized ones so we're working 00:40:59.520 --> 00:41:01.670 align:start position:0% also decentralized ones so we're working on<00:40:59.760> data<00:40:59.970> wallet<00:41:00.480> to<00:41:00.810> produce<00:41:01.020> that<00:41:01.380> and 00:41:01.670 --> 00:41:01.680 align:start position:0% on data wallet to produce that and 00:41:01.680 --> 00:41:03.710 align:start position:0% on data wallet to produce that and working<00:41:02.280> on<00:41:02.400> or<00:41:02.670> to<00:41:02.910> produce<00:41:03.060> that<00:41:03.450> in<00:41:03.660> a 00:41:03.710 --> 00:41:03.720 align:start position:0% working on or to produce that in a 00:41:03.720 --> 00:41:07.670 align:start position:0% working on or to produce that in a privacy-preserving<00:41:04.230> way<00:41:06.200> that<00:41:07.200> is<00:41:07.319> provably 00:41:07.670 --> 00:41:07.680 align:start position:0% privacy-preserving way that is provably 00:41:07.680 --> 00:41:12.230 align:start position:0% privacy-preserving way that is provably correct<00:41:10.190> so<00:41:11.190> let's<00:41:11.220> see<00:41:11.520> how<00:41:11.910> this<00:41:12.060> works 00:41:12.230 --> 00:41:12.240 align:start position:0% correct so let's see how this works 00:41:12.240 --> 00:41:15.140 align:start position:0% correct so let's see how this works today<00:41:12.630> and<00:41:13.349> this<00:41:13.710> kind<00:41:13.980> of<00:41:14.040> contract<00:41:14.609> exists 00:41:15.140 --> 00:41:15.150 align:start position:0% today and this kind of contract exists 00:41:15.150 --> 00:41:18.050 align:start position:0% today and this kind of contract exists today<00:41:16.020> if<00:41:16.560> you<00:41:17.069> want<00:41:17.220> to<00:41:17.369> use<00:41:17.550> some<00:41:17.790> kind<00:41:17.819> of 00:41:18.050 --> 00:41:18.060 align:start position:0% today if you want to use some kind of 00:41:18.060 --> 00:41:20.329 align:start position:0% today if you want to use some kind of gateway<00:41:18.300> like<00:41:18.599> that<00:41:18.839> or<00:41:19.349> that<00:41:19.619> gate<00:41:19.920> we<00:41:20.130> may 00:41:20.329 --> 00:41:20.339 align:start position:0% gateway like that or that gate we may 00:41:20.339 --> 00:41:23.000 align:start position:0% gateway like that or that gate we may ask<00:41:20.579> you<00:41:20.819> to<00:41:21.180> provide<00:41:21.540> some<00:41:21.720> solver<00:41:22.560> personal 00:41:23.000 --> 00:41:23.010 align:start position:0% ask you to provide some solver personal 00:41:23.010 --> 00:41:24.910 align:start position:0% ask you to provide some solver personal information<00:41:23.579> like<00:41:24.030> your<00:41:24.240> facebook<00:41:24.630> data 00:41:24.910 --> 00:41:24.920 align:start position:0% information like your facebook data 00:41:24.920 --> 00:41:27.470 align:start position:0% information like your facebook data right<00:41:25.920> you're<00:41:26.190> gonna<00:41:26.369> send<00:41:26.730> that<00:41:26.970> in<00:41:27.240> the 00:41:27.470 --> 00:41:27.480 align:start position:0% right you're gonna send that in the 00:41:27.480 --> 00:41:31.040 align:start position:0% right you're gonna send that in the clear<00:41:27.780> to<00:41:28.770> the<00:41:29.160> to<00:41:29.730> that<00:41:30.329> service<00:41:30.690> provider 00:41:31.040 --> 00:41:31.050 align:start position:0% clear to the to that service provider 00:41:31.050 --> 00:41:33.770 align:start position:0% clear to the to that service provider that<00:41:31.490> service<00:41:32.490> provider<00:41:32.819> is<00:41:33.119> going<00:41:33.480> to<00:41:33.630> run 00:41:33.770 --> 00:41:33.780 align:start position:0% that service provider is going to run 00:41:33.780 --> 00:41:36.109 align:start position:0% that service provider is going to run some<00:41:34.109> algorithm<00:41:34.800> we<00:41:35.099> call<00:41:35.310> it<00:41:35.460> you<00:41:35.579> know<00:41:35.640> part 00:41:36.109 --> 00:41:36.119 align:start position:0% some algorithm we call it you know part 00:41:36.119 --> 00:41:38.990 align:start position:0% some algorithm we call it you know part or<00:41:36.300> not<00:41:36.480> which<00:41:37.290> simply<00:41:37.920> run<00:41:38.099> some<00:41:38.339> statistical 00:41:38.990 --> 00:41:39.000 align:start position:0% or not which simply run some statistical 00:41:39.000 --> 00:41:41.059 align:start position:0% or not which simply run some statistical algorithm<00:41:39.540> that<00:41:39.780> checks<00:41:40.109> whether<00:41:40.710> you're<00:41:41.040> a 00:41:41.059 --> 00:41:41.069 align:start position:0% algorithm that checks whether you're a 00:41:41.069 --> 00:41:44.900 align:start position:0% algorithm that checks whether you're a real<00:41:41.400> person<00:41:41.910> or<00:41:42.119> not<00:41:42.770> but<00:41:43.770> you<00:41:44.609> have<00:41:44.640> to 00:41:44.900 --> 00:41:44.910 align:start position:0% real person or not but you have to 00:41:44.910 --> 00:41:46.880 align:start position:0% real person or not but you have to completely<00:41:45.329> trust<00:41:45.599> that<00:41:45.839> service<00:41:46.260> in<00:41:46.470> both 00:41:46.880 --> 00:41:46.890 align:start position:0% completely trust that service in both 00:41:46.890 --> 00:41:49.730 align:start position:0% completely trust that service in both ways<00:41:47.160> first<00:41:48.000> of<00:41:48.210> all<00:41:48.359> they<00:41:48.720> can<00:41:48.750> censor<00:41:49.349> you 00:41:49.730 --> 00:41:49.740 align:start position:0% ways first of all they can censor you 00:41:49.740 --> 00:41:51.140 align:start position:0% ways first of all they can censor you right<00:41:49.920> if<00:41:50.130> they<00:41:50.280> don't<00:41:50.490> like<00:41:50.730> you<00:41:50.910> if<00:41:51.030> they 00:41:51.140 --> 00:41:51.150 align:start position:0% right if they don't like you if they 00:41:51.150 --> 00:41:53.030 align:start position:0% right if they don't like you if they don't<00:41:51.270> like<00:41:51.450> what<00:41:51.630> they<00:41:51.780> see<00:41:51.810> they<00:41:52.590> can<00:41:52.619> say 00:41:53.030 --> 00:41:53.040 align:start position:0% don't like what they see they can say 00:41:53.040 --> 00:41:55.340 align:start position:0% don't like what they see they can say you<00:41:53.790> know<00:41:53.940> what<00:41:54.119> we're<00:41:54.540> not<00:41:54.570> we're<00:41:54.900> not<00:41:55.020> giving 00:41:55.340 --> 00:41:55.350 align:start position:0% you know what we're not we're not giving 00:41:55.350 --> 00:41:57.320 align:start position:0% you know what we're not we're not giving you<00:41:55.410> the<00:41:55.619> stamp<00:41:55.920> of<00:41:56.040> approval<00:41:56.130> and<00:41:56.700> you<00:41:57.030> cannot 00:41:57.320 --> 00:41:57.330 align:start position:0% you the stamp of approval and you cannot 00:41:57.330 --> 00:41:59.780 align:start position:0% you the stamp of approval and you cannot continue<00:41:57.810> to<00:41:58.320> use<00:41:58.740> whatever<00:41:59.130> other<00:41:59.340> service 00:41:59.780 --> 00:41:59.790 align:start position:0% continue to use whatever other service 00:41:59.790 --> 00:42:01.730 align:start position:0% continue to use whatever other service you<00:41:59.940> want<00:42:00.060> to<00:42:00.150> use<00:42:00.360> and<00:42:00.630> what's<00:42:01.260> even<00:42:01.380> worse 00:42:01.730 --> 00:42:01.740 align:start position:0% you want to use and what's even worse 00:42:01.740 --> 00:42:04.370 align:start position:0% you want to use and what's even worse and<00:42:02.160> more<00:42:02.369> likely<00:42:02.580> is<00:42:02.970> that<00:42:03.540> you<00:42:03.930> give<00:42:04.200> them 00:42:04.370 --> 00:42:04.380 align:start position:0% and more likely is that you give them 00:42:04.380 --> 00:42:07.370 align:start position:0% and more likely is that you give them your<00:42:04.680> social<00:42:04.980> information<00:42:05.880> in<00:42:06.810> the<00:42:07.080> clear 00:42:07.370 --> 00:42:07.380 align:start position:0% your social information in the clear 00:42:07.380 --> 00:42:10.220 align:start position:0% your social information in the clear that<00:42:07.980> data<00:42:08.250> then<00:42:08.640> they<00:42:09.180> get<00:42:09.450> it<00:42:09.630> they<00:42:10.080> usually 00:42:10.220 --> 00:42:10.230 align:start position:0% that data then they get it they usually 00:42:10.230 --> 00:42:12.920 align:start position:0% that data then they get it they usually store<00:42:10.830> it<00:42:10.980> and<00:42:11.190> you<00:42:11.700> have<00:42:11.910> no<00:42:12.150> control<00:42:12.390> over 00:42:12.920 --> 00:42:12.930 align:start position:0% store it and you have no control over 00:42:12.930 --> 00:42:16.940 align:start position:0% store it and you have no control over what's<00:42:13.470> going<00:42:13.530> on<00:42:13.830> with<00:42:14.010> this<00:42:15.590> so<00:42:16.590> we<00:42:16.710> want<00:42:16.890> to 00:42:16.940 --> 00:42:16.950 align:start position:0% what's going on with this so we want to 00:42:16.950 --> 00:42:20.900 align:start position:0% what's going on with this so we want to do<00:42:17.070> better<00:42:17.690> and<00:42:18.690> what<00:42:19.500> we<00:42:19.830> suggest<00:42:20.010> and<00:42:20.730> the 00:42:20.900 --> 00:42:20.910 align:start position:0% do better and what we suggest and the 00:42:20.910 --> 00:42:23.620 align:start position:0% do better and what we suggest and the way<00:42:21.030> this<00:42:21.630> application<00:42:22.200> works<00:42:22.410> here<00:42:22.680> is 00:42:23.620 --> 00:42:23.630 align:start position:0% way this application works here is 00:42:23.630 --> 00:42:26.240 align:start position:0% way this application works here is essentially<00:42:24.630> just<00:42:25.050> put<00:42:25.440> everything<00:42:25.770> on 00:42:26.240 --> 00:42:26.250 align:start position:0% essentially just put everything on 00:42:26.250 --> 00:42:29.630 align:start position:0% essentially just put everything on enigma<00:42:26.820> in<00:42:27.090> a<00:42:27.570> in<00:42:27.869> an<00:42:27.990> encrypted<00:42:28.320> form<00:42:28.640> where 00:42:29.630 --> 00:42:29.640 align:start position:0% enigma in a in an encrypted form where 00:42:29.640 --> 00:42:31.670 align:start position:0% enigma in a in an encrypted form where you<00:42:30.150> know<00:42:30.270> that<00:42:30.510> creates<00:42:30.869> a<00:42:30.930> neutral<00:42:31.410> safe 00:42:31.670 --> 00:42:31.680 align:start position:0% you know that creates a neutral safe 00:42:31.680 --> 00:42:34.370 align:start position:0% you know that creates a neutral safe ground<00:42:32.119> the<00:42:33.119> one<00:42:33.240> of<00:42:33.420> these<00:42:33.540> works<00:42:33.840> is<00:42:34.140> that 00:42:34.370 --> 00:42:34.380 align:start position:0% ground the one of these works is that 00:42:34.380 --> 00:42:38.200 align:start position:0% ground the one of these works is that the<00:42:35.330> Gateway<00:42:36.330> that<00:42:36.720> the<00:42:36.900> developer<00:42:37.500> they 00:42:38.200 --> 00:42:38.210 align:start position:0% the Gateway that the developer they 00:42:38.210 --> 00:42:40.970 align:start position:0% the Gateway that the developer they deploy<00:42:39.210> their<00:42:39.540> algorithm<00:42:40.140> as<00:42:40.320> a<00:42:40.530> secret 00:42:40.970 --> 00:42:40.980 align:start position:0% deploy their algorithm as a secret 00:42:40.980 --> 00:42:43.790 align:start position:0% deploy their algorithm as a secret contract<00:42:41.550> to<00:42:42.180> the<00:42:42.300> Enigma<00:42:42.630> network<00:42:42.990> and<00:42:43.530> on 00:42:43.790 --> 00:42:43.800 align:start position:0% contract to the Enigma network and on 00:42:43.800 --> 00:42:46.850 align:start position:0% contract to the Enigma network and on the<00:42:43.920> other<00:42:44.070> hand<00:42:44.369> the<00:42:44.880> user<00:42:45.119> submits<00:42:45.900> their 00:42:46.850 --> 00:42:46.860 align:start position:0% the other hand the user submits their 00:42:46.860 --> 00:42:50.359 align:start position:0% the other hand the user submits their encrypted<00:42:47.400> data<00:42:47.840> into<00:42:48.840> the<00:42:48.960> network<00:42:49.350> and<00:42:49.650> then 00:42:50.359 --> 00:42:50.369 align:start position:0% encrypted data into the network and then 00:42:50.369 --> 00:42:52.070 align:start position:0% encrypted data into the network and then all<00:42:50.730> of<00:42:50.790> these<00:42:50.970> computations<00:42:51.300> happen<00:42:51.900> in<00:42:51.990> the 00:42:52.070 --> 00:42:52.080 align:start position:0% all of these computations happen in the 00:42:52.080 --> 00:42:54.440 align:start position:0% all of these computations happen in the network<00:42:52.440> over<00:42:52.710> encrypted<00:42:53.220> data<00:42:53.430> the<00:42:54.180> only 00:42:54.440 --> 00:42:54.450 align:start position:0% network over encrypted data the only 00:42:54.450 --> 00:42:56.330 align:start position:0% network over encrypted data the only place<00:42:54.720> where<00:42:54.930> the<00:42:55.050> data<00:42:55.260> is<00:42:55.500> ever<00:42:55.650> decrypted 00:42:56.330 --> 00:42:56.340 align:start position:0% place where the data is ever decrypted 00:42:56.340 --> 00:42:59.900 align:start position:0% place where the data is ever decrypted is<00:42:56.550> obviously<00:42:57.390> inside<00:42:58.020> of<00:42:58.280> SGX<00:42:59.280> enclaves 00:42:59.900 --> 00:42:59.910 align:start position:0% is obviously inside of SGX enclaves 00:42:59.910 --> 00:43:02.840 align:start position:0% is obviously inside of SGX enclaves where<00:43:00.720> even<00:43:01.680> the<00:43:01.800> host<00:43:01.950> cannot<00:43:02.310> really<00:43:02.550> probe 00:43:02.840 --> 00:43:02.850 align:start position:0% where even the host cannot really probe 00:43:02.850 --> 00:43:08.120 align:start position:0% where even the host cannot really probe in<00:43:03.030> and<00:43:03.330> see<00:43:03.570> the<00:43:03.660> data<00:43:06.350> so<00:43:07.350> in<00:43:07.740> a<00:43:07.859> bit<00:43:08.010> more 00:43:08.120 --> 00:43:08.130 align:start position:0% in and see the data so in a bit more 00:43:08.130 --> 00:43:10.340 align:start position:0% in and see the data so in a bit more detail<00:43:08.490> about<00:43:08.580> how<00:43:08.790> this<00:43:09.359> was<00:43:09.690> actually<00:43:10.109> built 00:43:10.340 --> 00:43:10.350 align:start position:0% detail about how this was actually built 00:43:10.350 --> 00:43:13.070 align:start position:0% detail about how this was actually built we<00:43:11.340> have<00:43:11.520> data<00:43:11.790> wallet<00:43:12.270> who<00:43:12.540> developed<00:43:13.020> the 00:43:13.070 --> 00:43:13.080 align:start position:0% we have data wallet who developed the 00:43:13.080 --> 00:43:15.230 align:start position:0% we have data wallet who developed the front-end<00:43:13.590> that's<00:43:14.130> basically<00:43:14.670> some<00:43:14.910> kind<00:43:14.940> of 00:43:15.230 --> 00:43:15.240 align:start position:0% front-end that's basically some kind of 00:43:15.240 --> 00:43:16.580 align:start position:0% front-end that's basically some kind of mobile<00:43:15.450> app<00:43:15.690> that<00:43:15.720> you<00:43:16.050> have<00:43:16.080> on<00:43:16.290> your<00:43:16.380> phone 00:43:16.580 --> 00:43:16.590 align:start position:0% mobile app that you have on your phone 00:43:16.590 --> 00:43:20.690 align:start position:0% mobile app that you have on your phone it<00:43:17.040> allows<00:43:17.609> you<00:43:17.880> to<00:43:18.230> take<00:43:19.230> out<00:43:19.470> your<00:43:20.400> social 00:43:20.690 --> 00:43:20.700 align:start position:0% it allows you to take out your social 00:43:20.700 --> 00:43:23.090 align:start position:0% it allows you to take out your social information<00:43:21.359> from<00:43:21.480> Facebook<00:43:21.800> and<00:43:22.800> you<00:43:22.920> get 00:43:23.090 --> 00:43:23.100 align:start position:0% information from Facebook and you get 00:43:23.100 --> 00:43:27.050 align:start position:0% information from Facebook and you get that<00:43:23.250> locally<00:43:23.760> then<00:43:24.570> using<00:43:24.960> our<00:43:25.140> library<00:43:26.130> they 00:43:27.050 --> 00:43:27.060 align:start position:0% that locally then using our library they 00:43:27.060 --> 00:43:29.480 align:start position:0% that locally then using our library they can<00:43:27.330> with<00:43:27.570> a<00:43:27.600> click<00:43:27.840> of<00:43:27.930> a<00:43:28.050> button<00:43:28.490> actually 00:43:29.480 --> 00:43:29.490 align:start position:0% can with a click of a button actually 00:43:29.490 --> 00:43:31.670 align:start position:0% can with a click of a button actually encrypt<00:43:30.000> the<00:43:30.150> data<00:43:30.180> with<00:43:31.050> the<00:43:31.080> key<00:43:31.320> that<00:43:31.500> only 00:43:31.670 --> 00:43:31.680 align:start position:0% encrypt the data with the key that only 00:43:31.680 --> 00:43:34.280 align:start position:0% encrypt the data with the key that only exists<00:43:32.369> in<00:43:32.490> enclaves<00:43:32.910> in<00:43:33.420> our<00:43:33.690> network<00:43:34.109> and 00:43:34.280 --> 00:43:34.290 align:start position:0% exists in enclaves in our network and 00:43:34.290 --> 00:43:37.940 align:start position:0% exists in enclaves in our network and then<00:43:35.280> that<00:43:35.609> encrypted<00:43:36.210> data<00:43:36.450> is<00:43:36.840> being<00:43:37.530> sent 00:43:37.940 --> 00:43:37.950 align:start position:0% then that encrypted data is being sent 00:43:37.950 --> 00:43:40.970 align:start position:0% then that encrypted data is being sent to<00:43:38.430> the<00:43:38.850> network<00:43:39.240> to<00:43:39.630> an<00:43:39.750> enclave<00:43:40.140> or<00:43:40.619> actually 00:43:40.970 --> 00:43:40.980 align:start position:0% to the network to an enclave or actually 00:43:40.980 --> 00:43:44.359 align:start position:0% to the network to an enclave or actually to<00:43:41.070> server<00:43:41.280> enclaves<00:43:41.790> and<00:43:42.530> only<00:43:43.530> then<00:43:43.800> only 00:43:44.359 --> 00:43:44.369 align:start position:0% to server enclaves and only then only 00:43:44.369 --> 00:43:46.720 align:start position:0% to server enclaves and only then only then<00:43:44.820> the<00:43:45.240> information<00:43:45.480> is<00:43:45.900> being<00:43:46.140> decrypted 00:43:46.720 --> 00:43:46.730 align:start position:0% then the information is being decrypted 00:43:46.730 --> 00:43:49.160 align:start position:0% then the information is being decrypted inside<00:43:47.730> the<00:43:47.880> Enclave<00:43:48.330> and<00:43:48.600> the<00:43:48.869> archive 00:43:49.160 --> 00:43:49.170 align:start position:0% inside the Enclave and the archive 00:43:49.170 --> 00:43:52.490 align:start position:0% inside the Enclave and the archive itself<00:43:49.470> runs<00:43:50.340> the<00:43:50.700> secret<00:43:51.240> contract<00:43:51.810> in<00:43:51.990> this 00:43:52.490 --> 00:43:52.500 align:start position:0% itself runs the secret contract in this 00:43:52.500 --> 00:43:55.280 align:start position:0% itself runs the secret contract in this case<00:43:52.770> it's<00:43:53.040> the<00:43:53.220> bot<00:43:53.640> or<00:43:53.850> not<00:43:54.060> algorithm<00:43:55.050> and 00:43:55.280 --> 00:43:55.290 align:start position:0% case it's the bot or not algorithm and 00:43:55.290 --> 00:43:57.800 align:start position:0% case it's the bot or not algorithm and then<00:43:55.980> it<00:43:56.100> returns<00:43:56.430> the<00:43:56.580> result<00:43:56.910> so<00:43:57.540> the<00:43:57.660> only 00:43:57.800 --> 00:43:57.810 align:start position:0% then it returns the result so the only 00:43:57.810 --> 00:43:59.510 align:start position:0% then it returns the result so the only thing<00:43:58.020> that<00:43:58.050> really<00:43:58.350> leaves<00:43:58.710> the<00:43:58.920> network<00:43:59.070> and 00:43:59.510 --> 00:43:59.520 align:start position:0% thing that really leaves the network and 00:43:59.520 --> 00:44:02.270 align:start position:0% thing that really leaves the network and leaks<00:43:59.850> is<00:44:00.150> the<00:44:00.900> result<00:44:01.290> which<00:44:01.680> is<00:44:01.859> just<00:44:02.130> like 00:44:02.270 --> 00:44:02.280 align:start position:0% leaks is the result which is just like 00:44:02.280 --> 00:44:03.589 align:start position:0% leaks is the result which is just like one<00:44:02.550> bit<00:44:02.760> whether<00:44:03.000> you're<00:44:03.300> above 00:44:03.589 --> 00:44:03.599 align:start position:0% one bit whether you're above 00:44:03.599 --> 00:44:10.450 align:start position:0% one bit whether you're above or<00:44:03.839> not<00:44:03.989> but<00:44:04.200> it's<00:44:04.410> a<00:44:04.499> fake<00:44:04.680> account<00:44:04.859> or<00:44:05.369> not 00:44:10.450 --> 00:44:10.460 align:start position:0% 00:44:10.460 --> 00:44:13.249 align:start position:0% now<00:44:11.460> this<00:44:11.729> is<00:44:11.880> just<00:44:12.029> really<00:44:12.299> touching<00:44:12.989> the 00:44:13.249 --> 00:44:13.259 align:start position:0% now this is just really touching the 00:44:13.259 --> 00:44:16.069 align:start position:0% now this is just really touching the surface<00:44:13.970> there's<00:44:14.970> a<00:44:15.089> lot<00:44:15.390> of<00:44:15.509> companies<00:44:15.960> in 00:44:16.069 --> 00:44:16.079 align:start position:0% surface there's a lot of companies in 00:44:16.079 --> 00:44:19.999 align:start position:0% surface there's a lot of companies in the<00:44:16.109> space<00:44:16.259> building<00:44:17.009> a<00:44:18.710> host<00:44:19.710> of 00:44:19.999 --> 00:44:20.009 align:start position:0% the space building a host of 00:44:20.009 --> 00:44:22.219 align:start position:0% the space building a host of applications<00:44:20.880> that<00:44:21.210> are<00:44:21.660> needed<00:44:21.989> for<00:44:22.109> the 00:44:22.219 --> 00:44:22.229 align:start position:0% applications that are needed for the 00:44:22.229 --> 00:44:24.140 align:start position:0% applications that are needed for the space<00:44:22.470> we're<00:44:22.739> talking<00:44:23.150> decentralized 00:44:24.140 --> 00:44:24.150 align:start position:0% space we're talking decentralized 00:44:24.150 --> 00:44:26.329 align:start position:0% space we're talking decentralized governance<00:44:24.539> we<00:44:24.869> talking<00:44:25.229> auctions<00:44:25.710> we're 00:44:26.329 --> 00:44:26.339 align:start position:0% governance we talking auctions we're 00:44:26.339 --> 00:44:30.440 align:start position:0% governance we talking auctions we're talking<00:44:26.869> protecting<00:44:27.869> States<00:44:28.349> and<00:44:28.650> games<00:44:29.450> this 00:44:30.440 --> 00:44:30.450 align:start position:0% talking protecting States and games this 00:44:30.450 --> 00:44:32.900 align:start position:0% talking protecting States and games this was<00:44:30.690> an<00:44:30.839> example<00:44:30.989> about<00:44:31.529> identity<00:44:32.489> and<00:44:32.609> cyber 00:44:32.900 --> 00:44:32.910 align:start position:0% was an example about identity and cyber 00:44:32.910 --> 00:44:36.529 align:start position:0% was an example about identity and cyber prevention<00:44:34.759> we<00:44:35.759> have<00:44:35.940> work<00:44:36.210> done<00:44:36.239> on 00:44:36.529 --> 00:44:36.539 align:start position:0% prevention we have work done on 00:44:36.539 --> 00:44:38.809 align:start position:0% prevention we have work done on decentralized<00:44:37.289> credit<00:44:37.739> and<00:44:38.009> other<00:44:38.460> machine 00:44:38.809 --> 00:44:38.819 align:start position:0% decentralized credit and other machine 00:44:38.819 --> 00:44:41.059 align:start position:0% decentralized credit and other machine learning<00:44:39.029> applications<00:44:39.690> it's<00:44:40.410> it's<00:44:40.769> really 00:44:41.059 --> 00:44:41.069 align:start position:0% learning applications it's it's really 00:44:41.069 --> 00:44:43.039 align:start position:0% learning applications it's it's really the<00:44:41.190> sky<00:44:41.430> discard<00:44:41.999> the<00:44:42.150> limit<00:44:42.509> if<00:44:42.749> you<00:44:42.869> can 00:44:43.039 --> 00:44:43.049 align:start position:0% the sky discard the limit if you can 00:44:43.049 --> 00:44:45.920 align:start position:0% the sky discard the limit if you can really<00:44:43.289> protect<00:44:43.470> privacy<00:44:44.039> and<00:44:44.809> tomorrow<00:44:45.809> I'm 00:44:45.920 --> 00:44:45.930 align:start position:0% really protect privacy and tomorrow I'm 00:44:45.930 --> 00:44:48.109 align:start position:0% really protect privacy and tomorrow I'm going<00:44:46.109> to<00:44:46.200> go<00:44:46.349> much<00:44:46.619> more<00:44:46.829> deeply<00:44:47.339> into<00:44:47.670> the 00:44:48.109 --> 00:44:48.119 align:start position:0% going to go much more deeply into the 00:44:48.119 --> 00:44:50.960 align:start position:0% going to go much more deeply into the architecture<00:44:48.989> and<00:44:49.140> these<00:44:49.680> use<00:44:49.890> cases<00:44:49.979> and<00:44:50.670> I'm 00:44:50.960 --> 00:44:50.970 align:start position:0% architecture and these use cases and I'm 00:44:50.970 --> 00:44:52.370 align:start position:0% architecture and these use cases and I'm going<00:44:51.119> to<00:44:51.150> mention<00:44:51.359> some<00:44:51.539> real<00:44:51.900> names<00:44:52.140> and 00:44:52.370 --> 00:44:52.380 align:start position:0% going to mention some real names and 00:44:52.380 --> 00:44:54.769 align:start position:0% going to mention some real names and share<00:44:52.499> real<00:44:52.710> code<00:44:52.979> and<00:44:53.220> examples<00:44:53.789> of<00:44:53.999> partners 00:44:54.769 --> 00:44:54.779 align:start position:0% share real code and examples of partners 00:44:54.779 --> 00:44:57.979 align:start position:0% share real code and examples of partners are<00:44:54.930> working<00:44:55.079> with<00:44:55.789> so<00:44:56.789> I<00:44:56.819> do<00:44:57.089> suggest<00:44:57.359> if 00:44:57.979 --> 00:44:57.989 align:start position:0% are working with so I do suggest if 00:44:57.989 --> 00:44:59.269 align:start position:0% are working with so I do suggest if you're<00:44:58.170> interested<00:44:58.559> in<00:44:58.650> this<00:44:58.769> you<00:44:58.829> attend 00:44:59.269 --> 00:44:59.279 align:start position:0% you're interested in this you attend 00:44:59.279 --> 00:45:02.650 align:start position:0% you're interested in this you attend tomorrow<00:44:59.670> it's<00:44:59.940> going<00:45:00.089> to<00:45:00.150> be<00:45:00.529> here<00:45:01.529> at<00:45:01.710> 12:30 00:45:02.650 --> 00:45:02.660 align:start position:0% tomorrow it's going to be here at 12:30 00:45:02.660 --> 00:45:12.859 align:start position:0% tomorrow it's going to be here at 12:30 so<00:45:03.660> you're<00:45:03.809> welcome<00:45:04.109> thank<00:45:05.039> you<00:45:11.719> thank<00:45:12.719> you 00:45:12.859 --> 00:45:12.869 align:start position:0% so you're welcome thank you thank you 00:45:12.869 --> 00:45:14.239 align:start position:0% so you're welcome thank you thank you they'll<00:45:13.049> be<00:45:13.229> gather<00:45:13.380> a<00:45:13.440> question<00:45:13.920> how<00:45:14.190> does 00:45:14.239 --> 00:45:14.249 align:start position:0% they'll be gather a question how does 00:45:14.249 --> 00:45:16.099 align:start position:0% they'll be gather a question how does the<00:45:14.400> application<00:45:14.579> now<00:45:15.239> it<00:45:15.479> actually<00:45:15.660> uploads 00:45:16.099 --> 00:45:16.109 align:start position:0% the application now it actually uploads 00:45:16.109 --> 00:45:20.719 align:start position:0% the application now it actually uploads the<00:45:16.410> data<00:45:16.579> to<00:45:17.579> Ana<00:45:17.940> and<00:45:18.410> 2d<00:45:19.410> and<00:45:19.619> clave<00:45:19.890> that 00:45:20.719 --> 00:45:20.729 align:start position:0% the data to Ana and 2d and clave that 00:45:20.729 --> 00:45:23.479 align:start position:0% the data to Ana and 2d and clave that the<00:45:21.089> application<00:45:21.630> wants<00:45:21.779> to<00:45:21.960> trust<00:45:22.259> right<00:45:23.249> so 00:45:23.479 --> 00:45:23.489 align:start position:0% the application wants to trust right so 00:45:23.489 --> 00:45:25.640 align:start position:0% the application wants to trust right so basically<00:45:23.759> what<00:45:24.509> happens<00:45:24.869> is<00:45:25.049> that<00:45:25.319> we<00:45:25.499> have<00:45:25.529> a 00:45:25.640 --> 00:45:25.650 align:start position:0% basically what happens is that we have a 00:45:25.650 --> 00:45:27.859 align:start position:0% basically what happens is that we have a registration<00:45:26.309> process<00:45:26.759> for<00:45:26.789> every<00:45:27.299> worker<00:45:27.719> in 00:45:27.859 --> 00:45:27.869 align:start position:0% registration process for every worker in 00:45:27.869 --> 00:45:31.339 align:start position:0% registration process for every worker in an<00:45:27.989> airport<00:45:28.319> that<00:45:29.219> worker<00:45:29.729> basically<00:45:30.390> creates 00:45:31.339 --> 00:45:31.349 align:start position:0% an airport that worker basically creates 00:45:31.349 --> 00:45:34.039 align:start position:0% an airport that worker basically creates a<00:45:31.529> new<00:45:31.769> key<00:45:32.069> inside<00:45:32.969> in<00:45:33.119> fav<00:45:33.359> that<00:45:33.569> they<00:45:33.719> sign 00:45:34.039 --> 00:45:34.049 align:start position:0% a new key inside in fav that they sign 00:45:34.049 --> 00:45:36.849 align:start position:0% a new key inside in fav that they sign they<00:45:34.829> that<00:45:35.460> go<00:45:35.700> through<00:45:35.969> the<00:45:36.089> IAS<00:45:36.539> and 00:45:36.849 --> 00:45:36.859 align:start position:0% they that go through the IAS and 00:45:36.859 --> 00:45:40.880 align:start position:0% they that go through the IAS and providers<00:45:37.969> so<00:45:38.969> you<00:45:39.089> rely<00:45:39.809> on<00:45:39.839> IAS<00:45:40.410> and<00:45:40.440> remote 00:45:40.880 --> 00:45:40.890 align:start position:0% providers so you rely on IAS and remote 00:45:40.890 --> 00:45:41.569 align:start position:0% providers so you rely on IAS and remote at<00:45:41.009> the<00:45:41.069> station 00:45:41.569 --> 00:45:41.579 align:start position:0% at the station 00:45:41.579 --> 00:45:43.849 align:start position:0% at the station how<00:45:42.119> does<00:45:42.329> it<00:45:42.479> not<00:45:42.900> concern<00:45:43.079> you<00:45:43.469> that<00:45:43.499> this 00:45:43.849 --> 00:45:43.859 align:start position:0% how does it not concern you that this 00:45:43.859 --> 00:45:46.549 align:start position:0% how does it not concern you that this introduces<00:45:44.670> centralization<00:45:45.539> to<00:45:45.719> Europe<00:45:45.989> how 00:45:46.549 --> 00:45:46.559 align:start position:0% introduces centralization to Europe how 00:45:46.559 --> 00:45:48.229 align:start position:0% introduces centralization to Europe how does<00:45:46.769> it<00:45:46.920> not<00:45:47.099> concern<00:45:47.369> you<00:45:47.880> that<00:45:48.089> this 00:45:48.229 --> 00:45:48.239 align:start position:0% does it not concern you that this 00:45:48.239 --> 00:45:50.930 align:start position:0% does it not concern you that this creates<00:45:48.660> a<00:45:48.869> centralized<00:45:49.499> point<00:45:49.799> for<00:45:50.099> you<00:45:50.249> what 00:45:50.930 --> 00:45:50.940 align:start position:0% creates a centralized point for you what 00:45:50.940 --> 00:45:52.910 align:start position:0% creates a centralized point for you what we<00:45:51.119> do<00:45:51.299> is<00:45:51.539> we<00:45:51.900> do<00:45:52.109> it<00:45:52.259> only<00:45:52.499> in<00:45:52.710> a<00:45:52.769> good 00:45:52.910 --> 00:45:52.920 align:start position:0% we do is we do it only in a good 00:45:52.920 --> 00:45:54.289 align:start position:0% we do is we do it only in a good stopping<00:45:53.160> place<00:45:53.369> so<00:45:53.549> there's<00:45:53.729> a<00:45:53.819> registration 00:45:54.289 --> 00:45:54.299 align:start position:0% stopping place so there's a registration 00:45:54.299 --> 00:45:57.769 align:start position:0% stopping place so there's a registration you<00:45:55.019> go<00:45:55.229> to<00:45:55.289> iose<00:45:55.799> once<00:45:56.099> you<00:45:56.910> you<00:45:57.299> know<00:45:57.420> you<00:45:57.479> get 00:45:57.769 --> 00:45:57.779 align:start position:0% you go to iose once you you know you get 00:45:57.779 --> 00:46:00.650 align:start position:0% you go to iose once you you know you get they<00:45:58.589> signed<00:45:58.920> the<00:45:59.069> report<00:45:59.400> that<00:46:00.089> goes<00:46:00.329> on<00:46:00.539> the 00:46:00.650 --> 00:46:00.660 align:start position:0% they signed the report that goes on the 00:46:00.660 --> 00:46:02.599 align:start position:0% they signed the report that goes on the change<00:46:00.900> and<00:46:01.380> this<00:46:01.680> is<00:46:01.829> right<00:46:01.979> now<00:46:02.160> the<00:46:02.219> best<00:46:02.460> we 00:46:02.599 --> 00:46:02.609 align:start position:0% change and this is right now the best we 00:46:02.609 --> 00:46:04.099 align:start position:0% change and this is right now the best we can<00:46:02.759> do<00:46:02.910> we<00:46:03.089> would<00:46:03.269> love<00:46:03.299> to<00:46:03.450> see<00:46:03.690> the<00:46:03.839> central 00:46:04.099 --> 00:46:04.109 align:start position:0% can do we would love to see the central 00:46:04.109 --> 00:46:06.559 align:start position:0% can do we would love to see the central as<00:46:04.259> is<00:46:04.710> but<00:46:05.309> beyond<00:46:05.729> that<00:46:05.849> process<00:46:06.359> if<00:46:06.479> you 00:46:06.559 --> 00:46:06.569 align:start position:0% as is but beyond that process if you 00:46:06.569 --> 00:46:18.030 align:start position:0% as is but beyond that process if you trust<00:46:06.839> the<00:46:07.049> Transit<00:46:07.559> Center<00:46:10.460> okay<00:46:11.489> thanks<00:46:12.329> guy 00:46:18.030 --> 00:46:18.040 align:start position:0% 00:46:18.040 --> 00:46:22.450 align:start position:0% so<00:46:19.040> at<00:46:19.400> the<00:46:19.760> next<00:46:20.480> up<00:46:21.100> to<00:46:22.100> give<00:46:22.310> its 00:46:22.450 --> 00:46:22.460 align:start position:0% so at the next up to give its 00:46:22.460 --> 00:46:25.320 align:start position:0% so at the next up to give its perspective<00:46:22.880> on<00:46:23.240> this<00:46:23.420> one<00:46:23.720> is<00:46:24.020> Noah<00:46:24.530> from 00:46:25.320 --> 00:46:25.330 align:start position:0% perspective on this one is Noah from 00:46:25.330 --> 00:46:30.190 align:start position:0% perspective on this one is Noah from Oasis<00:46:26.330> labs<00:46:27.820> everyone<00:46:28.820> so<00:46:29.510> my<00:46:29.720> name<00:46:29.870> is<00:46:29.990> Noah 00:46:30.190 --> 00:46:30.200 align:start position:0% Oasis labs everyone so my name is Noah 00:46:30.200 --> 00:46:32.410 align:start position:0% Oasis labs everyone so my name is Noah Johnson<00:46:30.440> I<00:46:30.890> am<00:46:31.040> with<00:46:31.550> Oasis<00:46:31.910> labs<00:46:32.150> and<00:46:32.330> I'm 00:46:32.410 --> 00:46:32.420 align:start position:0% Johnson I am with Oasis labs and I'm 00:46:32.420 --> 00:46:33.430 align:start position:0% Johnson I am with Oasis labs and I'm going<00:46:32.570> to<00:46:32.600> talk<00:46:32.750> about<00:46:32.870> what<00:46:33.230> we're<00:46:33.320> building 00:46:33.430 --> 00:46:33.440 align:start position:0% going to talk about what we're building 00:46:33.440 --> 00:46:37.420 align:start position:0% going to talk about what we're building at<00:46:33.860> Oasis<00:46:34.460> so<00:46:35.650> of<00:46:36.650> course<00:46:36.770> blockchain<00:46:37.160> is<00:46:37.190> an 00:46:37.420 --> 00:46:37.430 align:start position:0% at Oasis so of course blockchain is an 00:46:37.430 --> 00:46:39.070 align:start position:0% at Oasis so of course blockchain is an exciting<00:46:37.850> technology<00:46:38.360> that<00:46:38.570> provides<00:46:38.720> a 00:46:39.070 --> 00:46:39.080 align:start position:0% exciting technology that provides a 00:46:39.080 --> 00:46:41.260 align:start position:0% exciting technology that provides a number<00:46:39.710> of<00:46:39.860> unique<00:46:40.250> properties<00:46:41.150> and 00:46:41.260 --> 00:46:41.270 align:start position:0% number of unique properties and 00:46:41.270 --> 00:46:43.720 align:start position:0% number of unique properties and capabilities<00:46:41.780> like<00:46:41.830> you<00:46:42.830> know<00:46:42.950> openness 00:46:43.720 --> 00:46:43.730 align:start position:0% capabilities like you know openness 00:46:43.730 --> 00:46:45.300 align:start position:0% capabilities like you know openness decentralization 00:46:45.300 --> 00:46:45.310 align:start position:0% decentralization 00:46:45.310 --> 00:46:49.000 align:start position:0% decentralization integrity<00:46:46.310> guarantees<00:46:46.810> but<00:46:47.810> as<00:46:48.050> has<00:46:48.800> been 00:46:49.000 --> 00:46:49.010 align:start position:0% integrity guarantees but as has been 00:46:49.010 --> 00:46:51.700 align:start position:0% integrity guarantees but as has been well<00:46:49.370> motivated<00:46:49.580> today<00:46:50.560> blockchain<00:46:51.560> by 00:46:51.700 --> 00:46:51.710 align:start position:0% well motivated today blockchain by 00:46:51.710 --> 00:46:53.380 align:start position:0% well motivated today blockchain by itself<00:46:51.920> doesn't<00:46:52.190> provide<00:46:52.550> privacy<00:46:52.940> right<00:46:53.240> and 00:46:53.380 --> 00:46:53.390 align:start position:0% itself doesn't provide privacy right and 00:46:53.390 --> 00:46:55.510 align:start position:0% itself doesn't provide privacy right and this<00:46:53.480> is<00:46:53.630> very<00:46:53.870> limiting<00:46:54.620> this<00:46:54.830> severely 00:46:55.510 --> 00:46:55.520 align:start position:0% this is very limiting this severely 00:46:55.520 --> 00:46:57.040 align:start position:0% this is very limiting this severely restricts<00:46:56.060> the<00:46:56.180> sorts<00:46:56.360> of<00:46:56.420> applications<00:46:56.990> that 00:46:57.040 --> 00:46:57.050 align:start position:0% restricts the sorts of applications that 00:46:57.050 --> 00:46:59.170 align:start position:0% restricts the sorts of applications that you<00:46:57.200> can<00:46:57.380> run<00:46:57.590> on<00:46:57.920> today's<00:46:58.670> blockchain 00:46:59.170 --> 00:46:59.180 align:start position:0% you can run on today's blockchain 00:46:59.180 --> 00:47:00.970 align:start position:0% you can run on today's blockchain platforms<00:46:59.660> and<00:46:59.870> so<00:47:00.200> what<00:47:00.350> we're<00:47:00.470> building<00:47:00.590> at 00:47:00.970 --> 00:47:00.980 align:start position:0% platforms and so what we're building at 00:47:00.980 --> 00:47:04.380 align:start position:0% platforms and so what we're building at Oasis<00:47:01.490> is<00:47:01.760> a<00:47:02.150> platform<00:47:02.990> that<00:47:03.050> protects<00:47:03.590> data 00:47:04.380 --> 00:47:04.390 align:start position:0% Oasis is a platform that protects data 00:47:04.390 --> 00:47:06.970 align:start position:0% Oasis is a platform that protects data protected<00:47:05.390> data<00:47:05.600> and<00:47:05.900> smart<00:47:06.320> contract<00:47:06.740> state 00:47:06.970 --> 00:47:06.980 align:start position:0% protected data and smart contract state 00:47:06.980 --> 00:47:09.670 align:start position:0% protected data and smart contract state and<00:47:07.940> provides<00:47:08.270> privacy<00:47:08.720> at<00:47:08.900> every<00:47:09.230> layer<00:47:09.410> of 00:47:09.670 --> 00:47:09.680 align:start position:0% and provides privacy at every layer of 00:47:09.680 --> 00:47:11.950 align:start position:0% and provides privacy at every layer of the<00:47:09.800> stack<00:47:10.010> so<00:47:10.220> at<00:47:10.430> the<00:47:10.550> application<00:47:11.180> layer<00:47:11.360> we 00:47:11.950 --> 00:47:11.960 align:start position:0% the stack so at the application layer we 00:47:11.960 --> 00:47:13.690 align:start position:0% the stack so at the application layer we have<00:47:12.080> a<00:47:12.110> set<00:47:12.320> of<00:47:12.410> tools<00:47:12.590> and<00:47:12.920> libraries<00:47:13.670> that 00:47:13.690 --> 00:47:13.700 align:start position:0% have a set of tools and libraries that 00:47:13.700 --> 00:47:17.380 align:start position:0% have a set of tools and libraries that allow<00:47:14.540> developers<00:47:14.600> to<00:47:15.290> safely<00:47:16.090> analyze<00:47:17.090> and 00:47:17.380 --> 00:47:17.390 align:start position:0% allow developers to safely analyze and 00:47:17.390 --> 00:47:19.930 align:start position:0% allow developers to safely analyze and compute<00:47:17.960> on<00:47:18.110> sensitive<00:47:19.010> data<00:47:19.190> with 00:47:19.930 --> 00:47:19.940 align:start position:0% compute on sensitive data with 00:47:19.940 --> 00:47:21.280 align:start position:0% compute on sensitive data with guarantees<00:47:20.390> that<00:47:20.420> the<00:47:20.750> results<00:47:21.080> of<00:47:21.140> those 00:47:21.280 --> 00:47:21.290 align:start position:0% guarantees that the results of those 00:47:21.290 --> 00:47:22.750 align:start position:0% guarantees that the results of those computations<00:47:21.530> actually<00:47:22.250> don't<00:47:22.520> violate 00:47:22.750 --> 00:47:22.760 align:start position:0% computations actually don't violate 00:47:22.760 --> 00:47:25.690 align:start position:0% computations actually don't violate privacy<00:47:23.170> at<00:47:24.170> the<00:47:24.320> platform<00:47:24.710> layer<00:47:24.860> we<00:47:25.220> have<00:47:25.430> a 00:47:25.690 --> 00:47:25.700 align:start position:0% privacy at the platform layer we have a 00:47:25.700 --> 00:47:28.060 align:start position:0% privacy at the platform layer we have a system<00:47:26.330> for<00:47:26.390> ensuring<00:47:27.320> that<00:47:27.350> workers<00:47:27.770> can't 00:47:28.060 --> 00:47:28.070 align:start position:0% system for ensuring that workers can't 00:47:28.070 --> 00:47:30.310 align:start position:0% system for ensuring that workers can't view<00:47:28.400> the<00:47:28.460> data<00:47:28.760> or<00:47:29.000> steal<00:47:29.300> the<00:47:29.480> data<00:47:29.630> and<00:47:29.930> then 00:47:30.310 --> 00:47:30.320 align:start position:0% view the data or steal the data and then 00:47:30.320 --> 00:47:31.870 align:start position:0% view the data or steal the data and then we<00:47:30.350> have<00:47:30.530> a<00:47:30.560> scalability<00:47:31.040> architecture<00:47:31.760> that 00:47:31.870 --> 00:47:31.880 align:start position:0% we have a scalability architecture that 00:47:31.880 --> 00:47:34.600 align:start position:0% we have a scalability architecture that allows<00:47:31.970> the<00:47:32.660> entire<00:47:32.930> system<00:47:33.320> to<00:47:33.350> support<00:47:33.920> much 00:47:34.600 --> 00:47:34.610 align:start position:0% allows the entire system to support much 00:47:34.610 --> 00:47:36.460 align:start position:0% allows the entire system to support much more<00:47:34.820> complex<00:47:35.420> sorts<00:47:35.780> of<00:47:35.840> applications<00:47:36.410> that 00:47:36.460 --> 00:47:36.470 align:start position:0% more complex sorts of applications that 00:47:36.470 --> 00:47:39.010 align:start position:0% more complex sorts of applications that you<00:47:36.620> could<00:47:36.830> run<00:47:36.980> today<00:47:37.640> so<00:47:38.180> this<00:47:38.600> is<00:47:38.660> really<00:47:38.990> a 00:47:39.010 --> 00:47:39.020 align:start position:0% you could run today so this is really a 00:47:39.020 --> 00:47:40.870 align:start position:0% you could run today so this is really a top-to-bottom<00:47:39.680> approach<00:47:40.010> all<00:47:40.250> of<00:47:40.520> which<00:47:40.670> I 00:47:40.870 --> 00:47:40.880 align:start position:0% top-to-bottom approach all of which I 00:47:40.880 --> 00:47:42.610 align:start position:0% top-to-bottom approach all of which I think<00:47:41.210> is<00:47:41.330> necessary<00:47:41.510> to<00:47:41.900> provide<00:47:42.140> and<00:47:42.440> and 00:47:42.610 --> 00:47:42.620 align:start position:0% think is necessary to provide and and 00:47:42.620 --> 00:47:44.290 align:start position:0% think is necessary to provide and and privacy<00:47:43.130> it's<00:47:43.220> not<00:47:43.340> sufficient<00:47:44.180> to<00:47:44.210> just 00:47:44.290 --> 00:47:44.300 align:start position:0% privacy it's not sufficient to just 00:47:44.300 --> 00:47:47.170 align:start position:0% privacy it's not sufficient to just protect<00:47:45.110> the<00:47:45.170> data<00:47:45.350> on<00:47:45.560> the<00:47:45.680> workers<00:47:46.070> if<00:47:46.910> it's 00:47:47.170 --> 00:47:47.180 align:start position:0% protect the data on the workers if it's 00:47:47.180 --> 00:47:48.790 align:start position:0% protect the data on the workers if it's trivial<00:47:47.630> to<00:47:47.780> write<00:47:47.960> a<00:47:47.990> smart<00:47:48.260> contract<00:47:48.680> that 00:47:48.790 --> 00:47:48.800 align:start position:0% trivial to write a smart contract that 00:47:48.800 --> 00:47:51.790 align:start position:0% trivial to write a smart contract that actually<00:47:49.190> leaks<00:47:50.090> out<00:47:50.270> sensitive<00:47:50.750> data<00:47:50.930> so 00:47:51.790 --> 00:47:51.800 align:start position:0% actually leaks out sensitive data so 00:47:51.800 --> 00:47:54.040 align:start position:0% actually leaks out sensitive data so this<00:47:51.950> is<00:47:52.070> our<00:47:52.220> approach<00:47:52.310> our<00:47:52.880> use<00:47:53.210> of<00:47:53.240> trusted 00:47:54.040 --> 00:47:54.050 align:start position:0% this is our approach our use of trusted 00:47:54.050 --> 00:47:55.930 align:start position:0% this is our approach our use of trusted compute<00:47:54.470> and<00:47:55.040> secure<00:47:55.340> hardware's<00:47:55.640> at<00:47:55.790> this 00:47:55.930 --> 00:47:55.940 align:start position:0% compute and secure hardware's at this 00:47:55.940 --> 00:47:58.210 align:start position:0% compute and secure hardware's at this layer<00:47:56.150> so<00:47:56.960> this<00:47:57.140> is<00:47:57.290> specifically<00:47:57.770> concerned 00:47:58.210 --> 00:47:58.220 align:start position:0% layer so this is specifically concerned 00:47:58.220 --> 00:47:59.890 align:start position:0% layer so this is specifically concerned with<00:47:58.370> the<00:47:58.460> problem<00:47:58.820> of<00:47:58.940> you<00:47:59.390> know<00:47:59.480> given<00:47:59.780> an 00:47:59.890 --> 00:47:59.900 align:start position:0% with the problem of you know given an 00:47:59.900 --> 00:48:01.510 align:start position:0% with the problem of you know given an open<00:48:00.140> network<00:48:00.350> and<00:48:00.710> workers<00:48:01.100> whom<00:48:01.250> you<00:48:01.370> may 00:48:01.510 --> 00:48:01.520 align:start position:0% open network and workers whom you may 00:48:01.520 --> 00:48:04.120 align:start position:0% open network and workers whom you may not<00:48:01.700> trust<00:48:01.940> if<00:48:02.930> those<00:48:03.260> workers<00:48:03.500> are<00:48:03.770> computing 00:48:04.120 --> 00:48:04.130 align:start position:0% not trust if those workers are computing 00:48:04.130 --> 00:48:05.470 align:start position:0% not trust if those workers are computing on<00:48:04.220> sensitive<00:48:04.550> data<00:48:04.790> how<00:48:05.060> do<00:48:05.120> you<00:48:05.270> make<00:48:05.450> sure 00:48:05.470 --> 00:48:05.480 align:start position:0% on sensitive data how do you make sure 00:48:05.480 --> 00:48:07.600 align:start position:0% on sensitive data how do you make sure that<00:48:05.660> they<00:48:05.960> can't<00:48:06.200> actually<00:48:06.440> leak<00:48:07.250> the<00:48:07.400> data 00:48:07.600 --> 00:48:07.610 align:start position:0% that they can't actually leak the data 00:48:07.610 --> 00:48:09.610 align:start position:0% that they can't actually leak the data and<00:48:07.850> so<00:48:08.420> what<00:48:08.900> we're<00:48:09.020> aiming<00:48:09.200> for<00:48:09.410> is 00:48:09.610 --> 00:48:09.620 align:start position:0% and so what we're aiming for is 00:48:09.620 --> 00:48:12.510 align:start position:0% and so what we're aiming for is essentially<00:48:10.250> a<00:48:10.690> model<00:48:11.690> called 00:48:12.510 --> 00:48:12.520 align:start position:0% essentially a model called 00:48:12.520 --> 00:48:14.680 align:start position:0% essentially a model called confidentiality<00:48:13.520> preserving<00:48:14.390> smart 00:48:14.680 --> 00:48:14.690 align:start position:0% confidentiality preserving smart 00:48:14.690 --> 00:48:16.930 align:start position:0% confidentiality preserving smart contract<00:48:15.050> execution<00:48:15.500> and<00:48:15.830> and<00:48:16.430> the<00:48:16.640> general 00:48:16.930 --> 00:48:16.940 align:start position:0% contract execution and and the general 00:48:16.940 --> 00:48:19.150 align:start position:0% contract execution and and the general idea<00:48:17.240> is<00:48:17.300> that<00:48:17.600> all<00:48:17.870> of<00:48:18.200> the<00:48:18.380> inputs<00:48:18.950> and 00:48:19.150 --> 00:48:19.160 align:start position:0% idea is that all of the inputs and 00:48:19.160 --> 00:48:20.800 align:start position:0% idea is that all of the inputs and outputs<00:48:19.430> of<00:48:19.910> a<00:48:19.970> smart<00:48:20.210> contract<00:48:20.630> are 00:48:20.800 --> 00:48:20.810 align:start position:0% outputs of a smart contract are 00:48:20.810 --> 00:48:23.560 align:start position:0% outputs of a smart contract are encrypted<00:48:21.500> so<00:48:22.310> that<00:48:22.490> nobody<00:48:23.090> in<00:48:23.180> the<00:48:23.270> network 00:48:23.560 --> 00:48:23.570 align:start position:0% encrypted so that nobody in the network 00:48:23.570 --> 00:48:25.740 align:start position:0% encrypted so that nobody in the network is<00:48:24.080> actually<00:48:24.230> able<00:48:24.470> to<00:48:24.590> view<00:48:24.920> the<00:48:25.100> contents 00:48:25.740 --> 00:48:25.750 align:start position:0% is actually able to view the contents 00:48:25.750 --> 00:48:27.820 align:start position:0% is actually able to view the contents except<00:48:26.750> the<00:48:26.840> smart<00:48:27.080> contract<00:48:27.230> it's 00:48:27.820 --> 00:48:27.830 align:start position:0% except the smart contract it's 00:48:27.830 --> 00:48:30.400 align:start position:0% except the smart contract it's so<00:48:28.010> this<00:48:28.160> means<00:48:28.370> no<00:48:28.580> nodes<00:48:29.090> can<00:48:29.420> view<00:48:29.660> the<00:48:30.170> data 00:48:30.400 --> 00:48:30.410 align:start position:0% so this means no nodes can view the data 00:48:30.410 --> 00:48:32.770 align:start position:0% so this means no nodes can view the data the<00:48:31.100> Gateway<00:48:31.610> can't<00:48:31.940> view<00:48:32.060> the<00:48:32.120> data<00:48:32.390> and<00:48:32.630> even 00:48:32.770 --> 00:48:32.780 align:start position:0% the Gateway can't view the data and even 00:48:32.780 --> 00:48:35.080 align:start position:0% the Gateway can't view the data and even the<00:48:32.960> worker<00:48:33.170> that<00:48:33.530> is<00:48:33.650> processing<00:48:34.130> the<00:48:34.850> smart 00:48:35.080 --> 00:48:35.090 align:start position:0% the worker that is processing the smart 00:48:35.090 --> 00:48:38.680 align:start position:0% the worker that is processing the smart contract<00:48:35.210> can't<00:48:36.080> view<00:48:36.320> the<00:48:36.470> data<00:48:36.970> so<00:48:37.970> how<00:48:38.270> do 00:48:38.680 --> 00:48:38.690 align:start position:0% contract can't view the data so how do 00:48:38.690 --> 00:48:40.390 align:start position:0% contract can't view the data so how do you<00:48:38.780> actually<00:48:38.870> access<00:48:39.770> this<00:48:39.920> functionality 00:48:40.390 --> 00:48:40.400 align:start position:0% you actually access this functionality 00:48:40.400 --> 00:48:43.030 align:start position:0% you actually access this functionality so<00:48:40.940> today<00:48:41.840> if<00:48:42.020> you<00:48:42.140> want<00:48:42.260> to<00:48:42.380> call<00:48:42.530> into<00:48:42.800> smart 00:48:43.030 --> 00:48:43.040 align:start position:0% so today if you want to call into smart 00:48:43.040 --> 00:48:45.070 align:start position:0% so today if you want to call into smart contract<00:48:43.460> you<00:48:43.550> would<00:48:43.640> usually<00:48:43.790> use<00:48:44.080> existing 00:48:45.070 --> 00:48:45.080 align:start position:0% contract you would usually use existing 00:48:45.080 --> 00:48:47.550 align:start position:0% contract you would usually use existing interfaces<00:48:45.800> like<00:48:45.830> web<00:48:46.340> 3 00:48:47.550 --> 00:48:47.560 align:start position:0% interfaces like web 3 00:48:47.560 --> 00:48:49.960 align:start position:0% interfaces like web 3 unfortunately<00:48:48.560> web<00:48:48.650> 3<00:48:48.890> was<00:48:49.070> designed<00:48:49.490> under 00:48:49.960 --> 00:48:49.970 align:start position:0% unfortunately web 3 was designed under 00:48:49.970 --> 00:48:51.580 align:start position:0% unfortunately web 3 was designed under the<00:48:50.060> assumption<00:48:50.420> that<00:48:50.450> all<00:48:50.690> data<00:48:50.930> is<00:48:51.170> public 00:48:51.580 --> 00:48:51.590 align:start position:0% the assumption that all data is public 00:48:51.590 --> 00:48:53.650 align:start position:0% the assumption that all data is public so<00:48:51.800> the<00:48:52.010> existing<00:48:52.580> API<00:48:52.940> is<00:48:53.060> actually<00:48:53.330> are 00:48:53.650 --> 00:48:53.660 align:start position:0% so the existing API is actually are 00:48:53.660 --> 00:48:55.180 align:start position:0% so the existing API is actually are insufficient<00:48:54.590> and<00:48:54.770> so<00:48:54.890> for<00:48:55.070> that<00:48:55.130> reason 00:48:55.180 --> 00:48:55.190 align:start position:0% insufficient and so for that reason 00:48:55.190 --> 00:48:57.610 align:start position:0% insufficient and so for that reason we've<00:48:55.700> developed<00:48:56.180> an<00:48:56.360> extension<00:48:57.140> to<00:48:57.230> web<00:48:57.380> 3 00:48:57.610 --> 00:48:57.620 align:start position:0% we've developed an extension to web 3 00:48:57.620 --> 00:48:59.920 align:start position:0% we've developed an extension to web 3 called<00:48:57.920> confidential<00:48:58.520> whip<00:48:58.670> 3<00:48:58.880> that<00:48:59.030> adds<00:48:59.210> new 00:48:59.920 --> 00:48:59.930 align:start position:0% called confidential whip 3 that adds new 00:48:59.930 --> 00:49:02.610 align:start position:0% called confidential whip 3 that adds new api's<00:49:00.470> that<00:49:00.770> essentially<00:49:01.190> allow<00:49:01.460> users<00:49:02.240> to 00:49:02.610 --> 00:49:02.620 align:start position:0% api's that essentially allow users to 00:49:02.620 --> 00:49:05.200 align:start position:0% api's that essentially allow users to construct<00:49:03.620> a<00:49:03.860> secure<00:49:04.370> channel<00:49:04.730> into<00:49:05.120> the 00:49:05.200 --> 00:49:05.210 align:start position:0% construct a secure channel into the 00:49:05.210 --> 00:49:07.240 align:start position:0% construct a secure channel into the smart<00:49:05.450> contract<00:49:05.600> so<00:49:06.050> that<00:49:06.080> they<00:49:06.350> can<00:49:06.530> encrypt 00:49:07.240 --> 00:49:07.250 align:start position:0% smart contract so that they can encrypt 00:49:07.250 --> 00:49:09.400 align:start position:0% smart contract so that they can encrypt the<00:49:07.520> transaction<00:49:08.120> payload<00:49:08.540> in<00:49:08.720> such<00:49:09.200> a<00:49:09.230> way 00:49:09.400 --> 00:49:09.410 align:start position:0% the transaction payload in such a way 00:49:09.410 --> 00:49:11.530 align:start position:0% the transaction payload in such a way that<00:49:09.440> only<00:49:10.130> the<00:49:10.550> smart<00:49:10.790> contract<00:49:11.240> can 00:49:11.530 --> 00:49:11.540 align:start position:0% that only the smart contract can 00:49:11.540 --> 00:49:14.650 align:start position:0% that only the smart contract can actually<00:49:11.900> decrypt<00:49:12.590> it<00:49:12.800> and<00:49:13.520> so<00:49:13.970> web<00:49:14.180> 3<00:49:14.480> is 00:49:14.650 --> 00:49:14.660 align:start position:0% actually decrypt it and so web 3 is 00:49:14.660 --> 00:49:16.900 align:start position:0% actually decrypt it and so web 3 is backwards<00:49:15.380> compatible<00:49:15.860> with<00:49:15.920> standard<00:49:16.100> sorry 00:49:16.900 --> 00:49:16.910 align:start position:0% backwards compatible with standard sorry 00:49:16.910 --> 00:49:18.190 align:start position:0% backwards compatible with standard sorry confidential<00:49:17.480> web<00:49:17.600> 3<00:49:17.750> is<00:49:17.840> backwards 00:49:18.190 --> 00:49:18.200 align:start position:0% confidential web 3 is backwards 00:49:18.200 --> 00:49:20.170 align:start position:0% confidential web 3 is backwards compatible<00:49:18.260> with<00:49:18.860> standard<00:49:19.310> web<00:49:19.700> 3<00:49:19.910> and<00:49:20.060> so 00:49:20.170 --> 00:49:20.180 align:start position:0% compatible with standard web 3 and so 00:49:20.180 --> 00:49:21.310 align:start position:0% compatible with standard web 3 and so it's<00:49:20.360> a<00:49:20.510> you<00:49:20.840> know<00:49:20.870> it's<00:49:20.960> a<00:49:21.080> drop-in 00:49:21.310 --> 00:49:21.320 align:start position:0% it's a you know it's a drop-in 00:49:21.320 --> 00:49:22.900 align:start position:0% it's a you know it's a drop-in replacement<00:49:21.950> the<00:49:22.070> modifications<00:49:22.700> that<00:49:22.790> are 00:49:22.900 --> 00:49:22.910 align:start position:0% replacement the modifications that are 00:49:22.910 --> 00:49:26.320 align:start position:0% replacement the modifications that are needed<00:49:23.240> to<00:49:23.840> existing<00:49:24.740> applications<00:49:25.670> are<00:49:25.910> very 00:49:26.320 --> 00:49:26.330 align:start position:0% needed to existing applications are very 00:49:26.330 --> 00:49:28.870 align:start position:0% needed to existing applications are very minor<00:49:26.630> we<00:49:27.470> might<00:49:27.650> also<00:49:27.830> look<00:49:28.190> at<00:49:28.340> supporting 00:49:28.870 --> 00:49:28.880 align:start position:0% minor we might also look at supporting 00:49:28.880 --> 00:49:32.170 align:start position:0% minor we might also look at supporting EE<00:49:29.510> A's<00:49:29.780> trusted<00:49:30.230> compute<00:49:30.530> API<00:49:30.860> as<00:49:31.160> well<00:49:31.760> given 00:49:32.170 --> 00:49:32.180 align:start position:0% EE A's trusted compute API as well given 00:49:32.180 --> 00:49:34.440 align:start position:0% EE A's trusted compute API as well given that<00:49:32.210> it<00:49:32.780> solves<00:49:33.050> largely<00:49:33.500> similar<00:49:33.800> problem 00:49:34.440 --> 00:49:34.450 align:start position:0% that it solves largely similar problem 00:49:34.450 --> 00:49:36.550 align:start position:0% that it solves largely similar problem so<00:49:35.450> there<00:49:35.870> are<00:49:35.990> a<00:49:36.050> number<00:49:36.080> of<00:49:36.290> different 00:49:36.550 --> 00:49:36.560 align:start position:0% so there are a number of different 00:49:36.560 --> 00:49:39.190 align:start position:0% so there are a number of different technologies<00:49:36.830> for<00:49:37.270> enabling<00:49:38.270> secure 00:49:39.190 --> 00:49:39.200 align:start position:0% technologies for enabling secure 00:49:39.200 --> 00:49:41.800 align:start position:0% technologies for enabling secure computing<00:49:39.590> these<00:49:40.580> are<00:49:41.090> generally<00:49:41.690> classified 00:49:41.800 --> 00:49:41.810 align:start position:0% computing these are generally classified 00:49:41.810 --> 00:49:43.900 align:start position:0% computing these are generally classified into<00:49:42.590> you<00:49:43.070> know<00:49:43.160> techniques<00:49:43.520> that<00:49:43.670> rely<00:49:43.880> on 00:49:43.900 --> 00:49:43.910 align:start position:0% into you know techniques that rely on 00:49:43.910 --> 00:49:45.730 align:start position:0% into you know techniques that rely on secure<00:49:44.390> hardware<00:49:44.570> and<00:49:45.020> crypto<00:49:45.560> based 00:49:45.730 --> 00:49:45.740 align:start position:0% secure hardware and crypto based 00:49:45.740 --> 00:49:47.770 align:start position:0% secure hardware and crypto based techniques<00:49:46.160> that<00:49:46.400> don't<00:49:46.880> rely<00:49:47.240> on<00:49:47.270> secure 00:49:47.770 --> 00:49:47.780 align:start position:0% techniques that don't rely on secure 00:49:47.780 --> 00:49:48.970 align:start position:0% techniques that don't rely on secure Hardware<00:49:48.080> they<00:49:48.200> instead<00:49:48.680> rely<00:49:48.950> on 00:49:48.970 --> 00:49:48.980 align:start position:0% Hardware they instead rely on 00:49:48.980 --> 00:49:51.460 align:start position:0% Hardware they instead rely on cryptographic<00:49:49.520> algorithms<00:49:50.350> so<00:49:51.350> they're 00:49:51.460 --> 00:49:51.470 align:start position:0% cryptographic algorithms so they're 00:49:51.470 --> 00:49:52.510 align:start position:0% cryptographic algorithms so they're different<00:49:51.620> trade-offs<00:49:52.130> all<00:49:52.370> these 00:49:52.510 --> 00:49:52.520 align:start position:0% different trade-offs all these 00:49:52.520 --> 00:49:54.700 align:start position:0% different trade-offs all these techniques<00:49:52.880> as<00:49:53.120> Sanjay<00:49:53.840> was<00:49:54.050> was<00:49:54.350> mentioning 00:49:54.700 --> 00:49:54.710 align:start position:0% techniques as Sanjay was was mentioning 00:49:54.710 --> 00:49:56.680 align:start position:0% techniques as Sanjay was was mentioning earlier<00:49:54.800> there's<00:49:55.250> no<00:49:55.430> single<00:49:56.090> approach<00:49:56.420> that 00:49:56.680 --> 00:49:56.690 align:start position:0% earlier there's no single approach that 00:49:56.690 --> 00:49:58.660 align:start position:0% earlier there's no single approach that is<00:49:56.810> a<00:49:56.840> silver<00:49:57.200> bullet<00:49:57.410> and<00:49:57.680> is<00:49:58.010> that<00:49:58.310> you<00:49:58.580> know 00:49:58.660 --> 00:49:58.670 align:start position:0% is a silver bullet and is that you know 00:49:58.670 --> 00:50:00.970 align:start position:0% is a silver bullet and is that you know the<00:49:58.820> optimal<00:49:59.300> approach<00:49:59.570> it<00:50:00.440> depends<00:50:00.830> on<00:50:00.890> the 00:50:00.970 --> 00:50:00.980 align:start position:0% the optimal approach it depends on the 00:50:00.980 --> 00:50:03.280 align:start position:0% the optimal approach it depends on the application<00:50:01.520> and<00:50:01.670> it<00:50:01.790> depends<00:50:02.180> on<00:50:02.330> the 00:50:03.280 --> 00:50:03.290 align:start position:0% application and it depends on the 00:50:03.290 --> 00:50:04.990 align:start position:0% application and it depends on the performance<00:50:03.710> requirements<00:50:04.250> and<00:50:04.400> and<00:50:04.880> the 00:50:04.990 --> 00:50:05.000 align:start position:0% performance requirements and and the 00:50:05.000 --> 00:50:07.300 align:start position:0% performance requirements and and the threat<00:50:05.180> model<00:50:05.450> and<00:50:05.570> so<00:50:06.080> the<00:50:06.380> goal<00:50:06.530> of<00:50:06.560> oasis<00:50:07.100> is 00:50:07.300 --> 00:50:07.310 align:start position:0% threat model and so the goal of oasis is 00:50:07.310 --> 00:50:09.130 align:start position:0% threat model and so the goal of oasis is to<00:50:07.640> integrate<00:50:08.300> all<00:50:08.600> these<00:50:08.750> different 00:50:09.130 --> 00:50:09.140 align:start position:0% to integrate all these different 00:50:09.140 --> 00:50:11.620 align:start position:0% to integrate all these different technologies<00:50:09.580> into<00:50:10.580> a<00:50:10.610> single<00:50:11.030> platform<00:50:11.210> and 00:50:11.620 --> 00:50:11.630 align:start position:0% technologies into a single platform and 00:50:11.630 --> 00:50:13.360 align:start position:0% technologies into a single platform and a<00:50:11.660> lot<00:50:11.810> of<00:50:11.870> developer<00:50:12.350> to<00:50:12.590> decide<00:50:13.010> which<00:50:13.220> one 00:50:13.360 --> 00:50:13.370 align:start position:0% a lot of developer to decide which one 00:50:13.370 --> 00:50:14.980 align:start position:0% a lot of developer to decide which one they<00:50:13.400> want<00:50:13.640> to<00:50:13.730> use<00:50:13.880> and<00:50:14.090> make<00:50:14.180> it<00:50:14.300> very<00:50:14.480> easy 00:50:14.980 --> 00:50:14.990 align:start position:0% they want to use and make it very easy 00:50:14.990 --> 00:50:16.630 align:start position:0% they want to use and make it very easy for<00:50:15.170> them<00:50:15.440> to<00:50:15.470> have<00:50:15.680> access<00:50:15.860> to<00:50:16.100> these 00:50:16.630 --> 00:50:16.640 align:start position:0% for them to have access to these 00:50:16.640 --> 00:50:19.060 align:start position:0% for them to have access to these technologies<00:50:17.470> one<00:50:18.470> of<00:50:18.560> the<00:50:18.620> reasons<00:50:18.920> we're 00:50:19.060 --> 00:50:19.070 align:start position:0% technologies one of the reasons we're 00:50:19.070 --> 00:50:20.530 align:start position:0% technologies one of the reasons we're especially<00:50:19.370> excited<00:50:19.850> about<00:50:19.910> secure<00:50:20.390> hardware 00:50:20.530 --> 00:50:20.540 align:start position:0% especially excited about secure hardware 00:50:20.540 --> 00:50:23.290 align:start position:0% especially excited about secure hardware is<00:50:20.930> that<00:50:21.200> of<00:50:21.740> these<00:50:22.100> techniques<00:50:22.610> it's<00:50:22.880> by<00:50:23.090> far 00:50:23.290 --> 00:50:23.300 align:start position:0% is that of these techniques it's by far 00:50:23.300 --> 00:50:25.450 align:start position:0% is that of these techniques it's by far the<00:50:23.360> most<00:50:23.690> performant<00:50:24.230> and<00:50:24.800> the<00:50:24.980> most<00:50:25.130> general 00:50:25.450 --> 00:50:25.460 align:start position:0% the most performant and the most general 00:50:25.460 --> 00:50:27.250 align:start position:0% the most performant and the most general purpose<00:50:25.820> so<00:50:26.000> the<00:50:26.120> fact<00:50:26.300> that<00:50:26.390> you<00:50:26.870> can<00:50:27.050> run 00:50:27.250 --> 00:50:27.260 align:start position:0% purpose so the fact that you can run 00:50:27.260 --> 00:50:29.050 align:start position:0% purpose so the fact that you can run code<00:50:27.470> you<00:50:28.010> know<00:50:28.100> directly<00:50:28.550> on<00:50:28.730> bare<00:50:29.030> metal 00:50:29.050 --> 00:50:29.060 align:start position:0% code you know directly on bare metal 00:50:29.060 --> 00:50:32.320 align:start position:0% code you know directly on bare metal means<00:50:29.570> that<00:50:30.130> you<00:50:31.130> can<00:50:31.340> run<00:50:31.550> essentially<00:50:32.210> any 00:50:32.320 --> 00:50:32.330 align:start position:0% means that you can run essentially any 00:50:32.330 --> 00:50:34.300 align:start position:0% means that you can run essentially any application<00:50:32.960> and<00:50:33.050> you<00:50:33.170> pay<00:50:33.350> very<00:50:33.650> little<00:50:34.040> in 00:50:34.300 --> 00:50:34.310 align:start position:0% application and you pay very little in 00:50:34.310 --> 00:50:36.400 align:start position:0% application and you pay very little in terms<00:50:34.340> of<00:50:34.760> performance<00:50:35.510> overhead<00:50:35.900> so<00:50:36.080> this<00:50:36.230> is 00:50:36.400 --> 00:50:36.410 align:start position:0% terms of performance overhead so this is 00:50:36.410 --> 00:50:39.880 align:start position:0% terms of performance overhead so this is the<00:50:36.920> first<00:50:37.160> technology<00:50:37.940> that<00:50:38.420> will<00:50:38.570> expose<00:50:39.080> in 00:50:39.880 --> 00:50:39.890 align:start position:0% the first technology that will expose in 00:50:39.890 --> 00:50:41.290 align:start position:0% the first technology that will expose in oasis 00:50:41.290 --> 00:50:41.300 align:start position:0% oasis 00:50:41.300 --> 00:50:42.250 align:start position:0% oasis people<00:50:41.510> aren't<00:50:41.720> familiar<00:50:41.780> with<00:50:42.020> secure 00:50:42.250 --> 00:50:42.260 align:start position:0% people aren't familiar with secure 00:50:42.260 --> 00:50:44.770 align:start position:0% people aren't familiar with secure hardware<00:50:42.410> the<00:50:43.310> the<00:50:43.670> basic<00:50:44.060> properties<00:50:44.540> that 00:50:44.770 --> 00:50:44.780 align:start position:0% hardware the the basic properties that 00:50:44.780 --> 00:50:46.410 align:start position:0% hardware the the basic properties that provided<00:50:45.170> by<00:50:45.260> secure<00:50:45.560> hardware<00:50:45.710> are 00:50:46.410 --> 00:50:46.420 align:start position:0% provided by secure hardware are 00:50:46.420 --> 00:50:48.820 align:start position:0% provided by secure hardware are essentially<00:50:47.420> the<00:50:47.480> hardware<00:50:47.780> allows<00:50:48.020> code<00:50:48.620> to 00:50:48.820 --> 00:50:48.830 align:start position:0% essentially the hardware allows code to 00:50:48.830 --> 00:50:50.200 align:start position:0% essentially the hardware allows code to construct<00:50:49.250> what's<00:50:49.460> called<00:50:49.700> a<00:50:49.820> trusted 00:50:50.200 --> 00:50:50.210 align:start position:0% construct what's called a trusted 00:50:50.210 --> 00:50:52.420 align:start position:0% construct what's called a trusted execution<00:50:50.690> environment<00:50:51.170> in<00:50:51.440> which<00:50:51.980> you<00:50:52.310> can 00:50:52.420 --> 00:50:52.430 align:start position:0% execution environment in which you can 00:50:52.430 --> 00:50:55.150 align:start position:0% execution environment in which you can put<00:50:52.610> applications<00:50:53.600> and<00:50:53.810> data<00:50:54.080> and<00:50:54.350> you<00:50:55.010> have<00:50:55.130> a 00:50:55.150 --> 00:50:55.160 align:start position:0% put applications and data and you have a 00:50:55.160 --> 00:50:58.180 align:start position:0% put applications and data and you have a guarantee<00:50:55.640> that<00:50:56.800> nobody<00:50:57.800> else<00:50:57.980> on<00:50:58.070> the 00:50:58.180 --> 00:50:58.190 align:start position:0% guarantee that nobody else on the 00:50:58.190 --> 00:50:59.890 align:start position:0% guarantee that nobody else on the machine<00:50:58.460> the<00:50:58.730> applications<00:50:59.300> the<00:50:59.540> operating 00:50:59.890 --> 00:50:59.900 align:start position:0% machine the applications the operating 00:50:59.900 --> 00:51:01.900 align:start position:0% machine the applications the operating system<00:51:00.230> even<00:51:00.410> the<00:51:00.650> user<00:51:00.860> is<00:51:01.250> actually<00:51:01.670> able<00:51:01.820> to 00:51:01.900 --> 00:51:01.910 align:start position:0% system even the user is actually able to 00:51:01.910 --> 00:51:05.140 align:start position:0% system even the user is actually able to view<00:51:02.330> or<00:51:02.630> tamper<00:51:03.590> with<00:51:03.740> the<00:51:04.430> contents<00:51:04.910> of<00:51:05.000> this 00:51:05.140 --> 00:51:05.150 align:start position:0% view or tamper with the contents of this 00:51:05.150 --> 00:51:07.060 align:start position:0% view or tamper with the contents of this trusted<00:51:05.930> execution<00:51:06.410> environment<00:51:06.800> so<00:51:06.920> this 00:51:07.060 --> 00:51:07.070 align:start position:0% trusted execution environment so this 00:51:07.070 --> 00:51:08.380 align:start position:0% trusted execution environment so this provides<00:51:07.430> both<00:51:07.640> integrity<00:51:08.270> and 00:51:08.380 --> 00:51:08.390 align:start position:0% provides both integrity and 00:51:08.390 --> 00:51:11.050 align:start position:0% provides both integrity and confidentiality<00:51:08.810> and<00:51:09.320> also<00:51:10.040> allows<00:51:10.550> the 00:51:11.050 --> 00:51:11.060 align:start position:0% confidentiality and also allows the 00:51:11.060 --> 00:51:13.630 align:start position:0% confidentiality and also allows the hardware<00:51:11.450> to<00:51:11.630> generate<00:51:11.960> a<00:51:11.990> certificate<00:51:12.640> that 00:51:13.630 --> 00:51:13.640 align:start position:0% hardware to generate a certificate that 00:51:13.640 --> 00:51:15.430 align:start position:0% hardware to generate a certificate that can<00:51:13.700> be<00:51:13.940> verified<00:51:14.180> by<00:51:14.600> a<00:51:14.630> remote<00:51:14.930> party<00:51:15.290> to 00:51:15.430 --> 00:51:15.440 align:start position:0% can be verified by a remote party to 00:51:15.440 --> 00:51:17.620 align:start position:0% can be verified by a remote party to prove<00:51:15.650> that<00:51:15.860> the<00:51:16.250> hardware<00:51:16.610> is<00:51:16.790> is<00:51:17.000> genuine 00:51:17.620 --> 00:51:17.630 align:start position:0% prove that the hardware is is genuine 00:51:17.630 --> 00:51:19.840 align:start position:0% prove that the hardware is is genuine and<00:51:17.780> you<00:51:18.320> know<00:51:18.410> the<00:51:18.530> right<00:51:18.650> code<00:51:18.920> is<00:51:19.160> running 00:51:19.840 --> 00:51:19.850 align:start position:0% and you know the right code is running 00:51:19.850 --> 00:51:24.160 align:start position:0% and you know the right code is running so<00:51:20.410> this<00:51:21.410> goal<00:51:22.070> of<00:51:22.460> sort<00:51:23.300> of<00:51:23.360> emulating<00:51:23.900> an 00:51:24.160 --> 00:51:24.170 align:start position:0% so this goal of sort of emulating an 00:51:24.170 --> 00:51:26.170 align:start position:0% so this goal of sort of emulating an ideal<00:51:24.530> trusted<00:51:25.070> third-party<00:51:25.280> right<00:51:26.000> to 00:51:26.170 --> 00:51:26.180 align:start position:0% ideal trusted third-party right to 00:51:26.180 --> 00:51:28.960 align:start position:0% ideal trusted third-party right to provide<00:51:26.510> certain<00:51:27.410> guarantees<00:51:27.920> even<00:51:28.790> in<00:51:28.880> the 00:51:28.960 --> 00:51:28.970 align:start position:0% provide certain guarantees even in the 00:51:28.970 --> 00:51:31.180 align:start position:0% provide certain guarantees even in the face<00:51:29.120> of<00:51:29.150> you<00:51:29.810> know<00:51:29.930> untrusted<00:51:30.650> parts<00:51:31.040> of<00:51:31.130> the 00:51:31.180 --> 00:51:31.190 align:start position:0% face of you know untrusted parts of the 00:51:31.190 --> 00:51:33.250 align:start position:0% face of you know untrusted parts of the system<00:51:31.340> are<00:51:31.790> very<00:51:31.850> similar<00:51:32.300> to<00:51:32.480> the<00:51:32.750> goals<00:51:32.960> of 00:51:33.250 --> 00:51:33.260 align:start position:0% system are very similar to the goals of 00:51:33.260 --> 00:51:34.810 align:start position:0% system are very similar to the goals of you<00:51:33.650> know<00:51:33.770> a<00:51:33.800> general<00:51:34.160> smart<00:51:34.430> contract 00:51:34.810 --> 00:51:34.820 align:start position:0% you know a general smart contract 00:51:34.820 --> 00:51:36.040 align:start position:0% you know a general smart contract platform<00:51:35.210> right<00:51:35.420> and<00:51:35.630> it<00:51:35.690> turns<00:51:35.870> out<00:51:35.990> that 00:51:36.040 --> 00:51:36.050 align:start position:0% platform right and it turns out that 00:51:36.050 --> 00:51:39.310 align:start position:0% platform right and it turns out that smart<00:51:36.860> contracts<00:51:37.340> and<00:51:37.610> T's<00:51:38.210> have<00:51:38.660> very 00:51:39.310 --> 00:51:39.320 align:start position:0% smart contracts and T's have very 00:51:39.320 --> 00:51:41.320 align:start position:0% smart contracts and T's have very similar<00:51:39.800> and<00:51:40.070> in<00:51:40.460> fact<00:51:40.640> complementary 00:51:41.320 --> 00:51:41.330 align:start position:0% similar and in fact complementary 00:51:41.330 --> 00:51:44.050 align:start position:0% similar and in fact complementary properties<00:51:41.870> for<00:51:42.560> example<00:51:42.700> smart<00:51:43.700> contract 00:51:44.050 --> 00:51:44.060 align:start position:0% properties for example smart contract 00:51:44.060 --> 00:51:46.090 align:start position:0% properties for example smart contract platforms<00:51:44.600> provide<00:51:45.200> strong<00:51:45.470> availability 00:51:46.090 --> 00:51:46.100 align:start position:0% platforms provide strong availability 00:51:46.100 --> 00:51:47.770 align:start position:0% platforms provide strong availability given<00:51:46.430> it's<00:51:46.580> a<00:51:46.670> decentralized<00:51:46.940> network<00:51:47.600> if 00:51:47.770 --> 00:51:47.780 align:start position:0% given it's a decentralized network if 00:51:47.780 --> 00:51:49.240 align:start position:0% given it's a decentralized network if one<00:51:47.960> node<00:51:48.170> goes<00:51:48.410> down<00:51:48.590> you<00:51:48.800> can<00:51:48.920> still<00:51:49.100> access 00:51:49.240 --> 00:51:49.250 align:start position:0% one node goes down you can still access 00:51:49.250 --> 00:51:51.400 align:start position:0% one node goes down you can still access the<00:51:49.580> network<00:51:49.850> state<00:51:50.630> is<00:51:50.840> stored<00:51:51.170> on<00:51:51.350> a 00:51:51.400 --> 00:51:51.410 align:start position:0% the network state is stored on a 00:51:51.410 --> 00:51:53.290 align:start position:0% the network state is stored on a permanent<00:51:51.980> ledger<00:51:52.250> so<00:51:52.580> there's<00:51:52.760> persistence 00:51:53.290 --> 00:51:53.300 align:start position:0% permanent ledger so there's persistence 00:51:53.300 --> 00:51:56.320 align:start position:0% permanent ledger so there's persistence but<00:51:54.170> as<00:51:54.350> we<00:51:54.590> mentioned<00:51:54.890> earlier<00:51:55.330> today's 00:51:56.320 --> 00:51:56.330 align:start position:0% but as we mentioned earlier today's 00:51:56.330 --> 00:51:57.910 align:start position:0% but as we mentioned earlier today's smart<00:51:56.570> contract<00:51:56.900> platforms<00:51:57.260> don't<00:51:57.470> provide 00:51:57.910 --> 00:51:57.920 align:start position:0% smart contract platforms don't provide 00:51:57.920 --> 00:52:00.610 align:start position:0% smart contract platforms don't provide any<00:51:58.190> confidentiality<00:51:58.700> for<00:51:59.300> data<00:51:59.480> or<00:51:59.570> state<00:51:59.900> on 00:52:00.610 --> 00:52:00.620 align:start position:0% any confidentiality for data or state on 00:52:00.620 --> 00:52:01.900 align:start position:0% any confidentiality for data or state on the<00:52:00.740> other<00:52:00.890> hand<00:52:01.130> trusted<00:52:01.640> execution 00:52:01.900 --> 00:52:01.910 align:start position:0% the other hand trusted execution 00:52:01.910 --> 00:52:04.390 align:start position:0% the other hand trusted execution environments<00:52:02.780> provide<00:52:03.380> weak<00:52:03.710> availability 00:52:04.390 --> 00:52:04.400 align:start position:0% environments provide weak availability 00:52:04.400 --> 00:52:06.190 align:start position:0% environments provide weak availability given<00:52:04.760> that<00:52:04.970> you<00:52:05.300> know<00:52:05.390> anyone<00:52:05.660> can<00:52:05.720> just<00:52:06.050> shut 00:52:06.190 --> 00:52:06.200 align:start position:0% given that you know anyone can just shut 00:52:06.200 --> 00:52:08.080 align:start position:0% given that you know anyone can just shut off<00:52:06.230> a<00:52:06.320> machine<00:52:06.740> that<00:52:07.070> is<00:52:07.100> running<00:52:07.370> a<00:52:07.760> trusted 00:52:08.080 --> 00:52:08.090 align:start position:0% off a machine that is running a trusted 00:52:08.090 --> 00:52:09.430 align:start position:0% off a machine that is running a trusted executor<00:52:08.450> environment<00:52:08.870> and<00:52:09.020> you<00:52:09.110> would<00:52:09.260> lose 00:52:09.430 --> 00:52:09.440 align:start position:0% executor environment and you would lose 00:52:09.440 --> 00:52:12.490 align:start position:0% executor environment and you would lose the<00:52:09.800> application<00:52:10.550> state<00:52:11.050> because<00:52:12.050> these 00:52:12.490 --> 00:52:12.500 align:start position:0% the application state because these 00:52:12.500 --> 00:52:15.130 align:start position:0% the application state because these don't<00:52:12.830> have<00:52:13.070> direct<00:52:13.430> access<00:52:13.610> to<00:52:14.140> durable 00:52:15.130 --> 00:52:15.140 align:start position:0% don't have direct access to durable 00:52:15.140 --> 00:52:17.380 align:start position:0% don't have direct access to durable storage<00:52:15.560> they<00:52:15.770> don't<00:52:15.950> provide<00:52:16.390> persistence 00:52:17.380 --> 00:52:17.390 align:start position:0% storage they don't provide persistence 00:52:17.390 --> 00:52:19.540 align:start position:0% storage they don't provide persistence but<00:52:17.840> they<00:52:17.990> do<00:52:18.050> provide<00:52:18.350> confidentiality<00:52:19.010> and 00:52:19.540 --> 00:52:19.550 align:start position:0% but they do provide confidentiality and 00:52:19.550 --> 00:52:20.890 align:start position:0% but they do provide confidentiality and so<00:52:19.730> the<00:52:19.880> fact<00:52:20.120> that<00:52:20.300> we<00:52:20.540> have<00:52:20.720> these 00:52:20.890 --> 00:52:20.900 align:start position:0% so the fact that we have these 00:52:20.900 --> 00:52:22.420 align:start position:0% so the fact that we have these complementary<00:52:21.500> properties<00:52:22.010> means<00:52:22.190> if<00:52:22.340> you 00:52:22.420 --> 00:52:22.430 align:start position:0% complementary properties means if you 00:52:22.430 --> 00:52:24.820 align:start position:0% complementary properties means if you combine<00:52:22.820> the<00:52:23.090> technologies<00:52:23.720> together<00:52:23.930> you 00:52:24.820 --> 00:52:24.830 align:start position:0% combine the technologies together you 00:52:24.830 --> 00:52:26.920 align:start position:0% combine the technologies together you can<00:52:25.070> get<00:52:25.280> the<00:52:25.520> best<00:52:25.730> of<00:52:25.970> both<00:52:26.330> worlds<00:52:26.390> and 00:52:26.920 --> 00:52:26.930 align:start position:0% can get the best of both worlds and 00:52:26.930 --> 00:52:28.720 align:start position:0% can get the best of both worlds and that's<00:52:27.200> exactly<00:52:27.470> what<00:52:27.770> we<00:52:27.890> did<00:52:28.070> in<00:52:28.310> our 00:52:28.720 --> 00:52:28.730 align:start position:0% that's exactly what we did in our 00:52:28.730 --> 00:52:30.610 align:start position:0% that's exactly what we did in our previous<00:52:28.790> research<00:52:29.480> project<00:52:29.930> called<00:52:30.110> akedan 00:52:30.610 --> 00:52:30.620 align:start position:0% previous research project called akedan 00:52:30.620 --> 00:52:33.400 align:start position:0% previous research project called akedan so<00:52:30.770> we<00:52:30.890> showed<00:52:31.070> how<00:52:31.250> to<00:52:31.310> run<00:52:32.210> smart<00:52:32.930> contracts 00:52:33.400 --> 00:52:33.410 align:start position:0% so we showed how to run smart contracts 00:52:33.410 --> 00:52:35.590 align:start position:0% so we showed how to run smart contracts inside<00:52:33.980> a<00:52:34.280> trusted<00:52:34.670> execution<00:52:34.910> environment 00:52:35.590 --> 00:52:35.600 align:start position:0% inside a trusted execution environment 00:52:35.600 --> 00:52:38.020 align:start position:0% inside a trusted execution environment in<00:52:35.720> order<00:52:35.900> to<00:52:36.140> endow<00:52:37.130> the<00:52:37.190> smart<00:52:37.580> contracts 00:52:38.020 --> 00:52:38.030 align:start position:0% in order to endow the smart contracts 00:52:38.030 --> 00:52:40.510 align:start position:0% in order to endow the smart contracts with<00:52:38.180> confidentiality<00:52:38.630> and<00:52:39.230> attach<00:52:39.890> that<00:52:40.250> to 00:52:40.510 --> 00:52:40.520 align:start position:0% with confidentiality and attach that to 00:52:40.520 --> 00:52:42.880 align:start position:0% with confidentiality and attach that to consensus<00:52:41.480> and<00:52:41.660> a<00:52:41.900> distributed<00:52:42.380> ledger<00:52:42.530> in 00:52:42.880 --> 00:52:42.890 align:start position:0% consensus and a distributed ledger in 00:52:42.890 --> 00:52:45.040 align:start position:0% consensus and a distributed ledger in order<00:52:43.130> to<00:52:43.250> retain<00:52:44.000> all<00:52:44.270> the<00:52:44.390> benefits<00:52:44.810> of 00:52:45.040 --> 00:52:45.050 align:start position:0% order to retain all the benefits of 00:52:45.050 --> 00:52:47.470 align:start position:0% order to retain all the benefits of blockchain<00:52:45.770> and<00:52:45.950> decentralisation<00:52:46.550> so<00:52:47.360> all 00:52:47.470 --> 00:52:47.480 align:start position:0% blockchain and decentralisation so all 00:52:47.480 --> 00:52:51.940 align:start position:0% blockchain and decentralisation so all the<00:52:47.600> details<00:52:47.720> are<00:52:48.140> in<00:52:48.170> this<00:52:48.770> paper 00:52:51.940 --> 00:52:51.950 align:start position:0% 00:52:51.950 --> 00:52:54.609 align:start position:0% we're<00:52:52.520> also<00:52:52.640> working<00:52:52.940> with<00:52:53.690> a<00:52:54.049> project<00:52:54.290> called 00:52:54.609 --> 00:52:54.619 align:start position:0% we're also working with a project called 00:52:54.619 --> 00:52:56.980 align:start position:0% we're also working with a project called Keystone<00:52:55.069> which<00:52:55.280> is<00:52:55.490> a<00:52:55.670> fully<00:52:56.510> open<00:52:56.780> source 00:52:56.980 --> 00:52:56.990 align:start position:0% Keystone which is a fully open source 00:52:56.990 --> 00:52:59.620 align:start position:0% Keystone which is a fully open source design<00:52:57.589> for<00:52:57.920> secure<00:52:58.220> hardware<00:52:58.369> so<00:52:58.730> today<00:52:59.270> the 00:52:59.620 --> 00:52:59.630 align:start position:0% design for secure hardware so today the 00:52:59.630 --> 00:53:02.230 align:start position:0% design for secure hardware so today the sort<00:52:59.990> of<00:53:00.020> the<00:53:00.140> state<00:53:00.349> of<00:53:00.470> the<00:53:00.530> art<00:53:01.240> secure 00:53:02.230 --> 00:53:02.240 align:start position:0% sort of the state of the art secure 00:53:02.240 --> 00:53:04.870 align:start position:0% sort of the state of the art secure Enclave<00:53:02.359> technology<00:53:03.079> is<00:53:03.349> Intel<00:53:04.010> SGX<00:53:04.160> and<00:53:04.730> it's 00:53:04.870 --> 00:53:04.880 align:start position:0% Enclave technology is Intel SGX and it's 00:53:04.880 --> 00:53:06.880 align:start position:0% Enclave technology is Intel SGX and it's it's<00:53:05.359> nice<00:53:05.569> in<00:53:05.839> that<00:53:05.990> you<00:53:06.200> know<00:53:06.290> it<00:53:06.470> runs<00:53:06.680> on 00:53:06.880 --> 00:53:06.890 align:start position:0% it's nice in that you know it runs on 00:53:06.890 --> 00:53:08.920 align:start position:0% it's nice in that you know it runs on commodity<00:53:07.309> hardware<00:53:07.730> has<00:53:08.480> very<00:53:08.720> very<00:53:08.780> high 00:53:08.920 --> 00:53:08.930 align:start position:0% commodity hardware has very very high 00:53:08.930 --> 00:53:10.780 align:start position:0% commodity hardware has very very high performance<00:53:09.589> we<00:53:10.190> want<00:53:10.369> to<00:53:10.520> provide<00:53:10.730> more 00:53:10.780 --> 00:53:10.790 align:start position:0% performance we want to provide more 00:53:10.790 --> 00:53:13.450 align:start position:0% performance we want to provide more options<00:53:11.240> to<00:53:11.660> developers<00:53:12.170> we<00:53:12.770> want<00:53:12.980> to<00:53:13.099> grow 00:53:13.450 --> 00:53:13.460 align:start position:0% options to developers we want to grow 00:53:13.460 --> 00:53:15.819 align:start position:0% options to developers we want to grow the<00:53:13.640> ecosystem<00:53:14.270> and<00:53:15.140> one<00:53:15.380> of<00:53:15.440> the<00:53:15.559> things<00:53:15.710> we 00:53:15.819 --> 00:53:15.829 align:start position:0% the ecosystem and one of the things we 00:53:15.829 --> 00:53:18.089 align:start position:0% the ecosystem and one of the things we want<00:53:16.040> to<00:53:16.130> use<00:53:16.579> Keystone<00:53:17.150> for<00:53:17.359> is<00:53:17.510> to<00:53:17.720> kind<00:53:17.930> of 00:53:18.089 --> 00:53:18.099 align:start position:0% want to use Keystone for is to kind of 00:53:18.099 --> 00:53:20.589 align:start position:0% want to use Keystone for is to kind of explore<00:53:19.099> new<00:53:19.339> designs<00:53:19.670> and<00:53:19.970> secure<00:53:20.240> enclaves 00:53:20.589 --> 00:53:20.599 align:start position:0% explore new designs and secure enclaves 00:53:20.599 --> 00:53:22.990 align:start position:0% explore new designs and secure enclaves and<00:53:21.440> bring<00:53:21.740> together<00:53:21.890> researchers<00:53:22.640> in<00:53:22.880> an 00:53:22.990 --> 00:53:23.000 align:start position:0% and bring together researchers in an 00:53:23.000 --> 00:53:25.720 align:start position:0% and bring together researchers in an open<00:53:23.390> platform<00:53:23.660> for<00:53:24.530> figuring<00:53:25.280> out<00:53:25.460> you<00:53:25.700> know 00:53:25.720 --> 00:53:25.730 align:start position:0% open platform for figuring out you know 00:53:25.730 --> 00:53:27.609 align:start position:0% open platform for figuring out you know what<00:53:25.849> are<00:53:26.089> the<00:53:26.329> limitations<00:53:26.960> of<00:53:27.200> today's 00:53:27.609 --> 00:53:27.619 align:start position:0% what are the limitations of today's 00:53:27.619 --> 00:53:29.620 align:start position:0% what are the limitations of today's designs<00:53:28.040> and<00:53:28.309> how<00:53:28.400> do<00:53:28.460> we<00:53:28.520> improve<00:53:28.700> on<00:53:29.059> them<00:53:29.210> so 00:53:29.620 --> 00:53:29.630 align:start position:0% designs and how do we improve on them so 00:53:29.630 --> 00:53:31.829 align:start position:0% designs and how do we improve on them so he's<00:53:30.170> don't<00:53:30.410> eventually<00:53:30.680> will<00:53:30.980> publish<00:53:31.430> a 00:53:31.829 --> 00:53:31.839 align:start position:0% he's don't eventually will publish a 00:53:31.839 --> 00:53:34.809 align:start position:0% he's don't eventually will publish a specification<00:53:32.839> for<00:53:33.109> a<00:53:33.170> secure<00:53:33.650> Enclave<00:53:33.829> that 00:53:34.809 --> 00:53:34.819 align:start position:0% specification for a secure Enclave that 00:53:34.819 --> 00:53:36.789 align:start position:0% specification for a secure Enclave that is<00:53:35.089> royalty-free<00:53:35.480> that<00:53:35.960> can<00:53:36.109> be<00:53:36.230> manufactured 00:53:36.789 --> 00:53:36.799 align:start position:0% is royalty-free that can be manufactured 00:53:36.799 --> 00:53:40.030 align:start position:0% is royalty-free that can be manufactured by<00:53:37.010> any<00:53:37.309> chip<00:53:37.549> maker<00:53:37.760> and<00:53:38.750> as<00:53:39.170> those<00:53:39.770> chips 00:53:40.030 --> 00:53:40.040 align:start position:0% by any chip maker and as those chips 00:53:40.040 --> 00:53:41.799 align:start position:0% by any chip maker and as those chips become<00:53:40.369> available<00:53:40.609> they'll<00:53:41.299> be<00:53:41.480> exposed 00:53:41.799 --> 00:53:41.809 align:start position:0% become available they'll be exposed 00:53:41.809 --> 00:53:43.630 align:start position:0% become available they'll be exposed through<00:53:42.140> the<00:53:42.230> Oasis<00:53:42.589> platform<00:53:43.010> so<00:53:43.190> developers 00:53:43.630 --> 00:53:43.640 align:start position:0% through the Oasis platform so developers 00:53:43.640 --> 00:53:45.490 align:start position:0% through the Oasis platform so developers can<00:53:43.790> choose<00:53:44.119> whether<00:53:44.390> they<00:53:44.599> want<00:53:44.630> to<00:53:44.839> use<00:53:45.020> for 00:53:45.490 --> 00:53:45.500 align:start position:0% can choose whether they want to use for 00:53:45.500 --> 00:53:48.190 align:start position:0% can choose whether they want to use for example<00:53:45.530> SGX<00:53:46.250> or<00:53:46.490> key<00:53:46.940> stones<00:53:47.180> the<00:53:47.420> idea<00:53:47.660> is<00:53:47.839> to 00:53:48.190 --> 00:53:48.200 align:start position:0% example SGX or key stones the idea is to 00:53:48.200 --> 00:53:51.370 align:start position:0% example SGX or key stones the idea is to grow<00:53:48.859> the<00:53:49.130> entire<00:53:49.490> community<00:53:50.119> by<00:53:50.660> you<00:53:51.260> know 00:53:51.370 --> 00:53:51.380 align:start position:0% grow the entire community by you know 00:53:51.380 --> 00:53:53.740 align:start position:0% grow the entire community by you know accelerating<00:53:52.190> adoption<00:53:52.670> of<00:53:52.880> secure<00:53:53.599> Enclave 00:53:53.740 --> 00:53:53.750 align:start position:0% accelerating adoption of secure Enclave 00:53:53.750 --> 00:53:55.450 align:start position:0% accelerating adoption of secure Enclave technologies<00:53:54.530> and<00:53:54.799> allowing<00:53:55.040> developers<00:53:55.400> to 00:53:55.450 --> 00:53:55.460 align:start position:0% technologies and allowing developers to 00:53:55.460 --> 00:53:57.400 align:start position:0% technologies and allowing developers to choose<00:53:55.760> which<00:53:55.910> one<00:53:56.119> makes<00:53:56.480> sense<00:53:56.690> for<00:53:57.260> their 00:53:57.400 --> 00:53:57.410 align:start position:0% choose which one makes sense for their 00:53:57.410 --> 00:54:00.099 align:start position:0% choose which one makes sense for their application<00:53:57.950> a<00:53:58.299> few<00:53:59.299> weeks<00:53:59.450> ago<00:53:59.569> we<00:53:59.780> hosted<00:54:00.049> a 00:54:00.099 --> 00:54:00.109 align:start position:0% application a few weeks ago we hosted a 00:54:00.109 --> 00:54:02.140 align:start position:0% application a few weeks ago we hosted a workshop<00:54:00.500> at<00:54:00.680> Berkeley<00:54:01.040> specifically<00:54:01.790> around 00:54:02.140 --> 00:54:02.150 align:start position:0% workshop at Berkeley specifically around 00:54:02.150 --> 00:54:04.690 align:start position:0% workshop at Berkeley specifically around how<00:54:02.900> to<00:54:02.960> design<00:54:03.349> open-source<00:54:04.130> enclaves<00:54:04.520> and 00:54:04.690 --> 00:54:04.700 align:start position:0% how to design open-source enclaves and 00:54:04.700 --> 00:54:06.849 align:start position:0% how to design open-source enclaves and we<00:54:05.089> brought<00:54:05.299> together<00:54:05.740> industry<00:54:06.740> and 00:54:06.849 --> 00:54:06.859 align:start position:0% we brought together industry and 00:54:06.859 --> 00:54:08.470 align:start position:0% we brought together industry and academic<00:54:07.250> leaders<00:54:07.520> in<00:54:07.700> the<00:54:07.819> space<00:54:07.940> to<00:54:08.329> talk 00:54:08.470 --> 00:54:08.480 align:start position:0% academic leaders in the space to talk 00:54:08.480 --> 00:54:09.609 align:start position:0% academic leaders in the space to talk about<00:54:08.630> you<00:54:08.960> know<00:54:09.079> what<00:54:09.290> are<00:54:09.349> the<00:54:09.440> open 00:54:09.609 --> 00:54:09.619 align:start position:0% about you know what are the open 00:54:09.619 --> 00:54:10.839 align:start position:0% about you know what are the open problems<00:54:09.950> and<00:54:10.160> how<00:54:10.250> do<00:54:10.309> we<00:54:10.400> work<00:54:10.700> together 00:54:10.839 --> 00:54:10.849 align:start position:0% problems and how do we work together 00:54:10.849 --> 00:54:14.470 align:start position:0% problems and how do we work together towards<00:54:11.450> this<00:54:11.599> goal<00:54:12.579> ok<00:54:13.579> so<00:54:13.640> once<00:54:14.030> you<00:54:14.270> can 00:54:14.470 --> 00:54:14.480 align:start position:0% towards this goal ok so once you can 00:54:14.480 --> 00:54:16.510 align:start position:0% towards this goal ok so once you can protect<00:54:14.900> data<00:54:15.109> on<00:54:15.740> a<00:54:16.040> smart<00:54:16.369> contract 00:54:16.510 --> 00:54:16.520 align:start position:0% protect data on a smart contract 00:54:16.520 --> 00:54:18.700 align:start position:0% protect data on a smart contract platform<00:54:17.150> this<00:54:17.270> opens<00:54:17.690> the<00:54:17.780> door<00:54:17.960> for<00:54:18.230> a<00:54:18.530> lot 00:54:18.700 --> 00:54:18.710 align:start position:0% platform this opens the door for a lot 00:54:18.710 --> 00:54:20.710 align:start position:0% platform this opens the door for a lot of<00:54:18.950> really<00:54:19.339> exciting<00:54:19.819> applications<00:54:20.390> here's<00:54:20.660> a 00:54:20.710 --> 00:54:20.720 align:start position:0% of really exciting applications here's a 00:54:20.720 --> 00:54:23.230 align:start position:0% of really exciting applications here's a list<00:54:20.960> of<00:54:21.200> some<00:54:21.770> of<00:54:21.799> them<00:54:22.040> many<00:54:22.819> of<00:54:22.910> these<00:54:23.059> are 00:54:23.230 --> 00:54:23.240 align:start position:0% list of some of them many of these are 00:54:23.240 --> 00:54:25.450 align:start position:0% list of some of them many of these are already<00:54:23.450> being<00:54:23.690> developed<00:54:24.140> on<00:54:24.829> the<00:54:24.890> Oasis 00:54:25.450 --> 00:54:25.460 align:start position:0% already being developed on the Oasis 00:54:25.460 --> 00:54:27.609 align:start position:0% already being developed on the Oasis platform<00:54:25.880> things<00:54:26.329> like<00:54:26.569> credit<00:54:26.930> scoring<00:54:27.200> and 00:54:27.609 --> 00:54:27.619 align:start position:0% platform things like credit scoring and 00:54:27.619 --> 00:54:29.470 align:start position:0% platform things like credit scoring and decentralized<00:54:28.160> exchanges<00:54:28.730> I<00:54:28.880> want<00:54:29.299> to<00:54:29.390> talk 00:54:29.470 --> 00:54:29.480 align:start position:0% decentralized exchanges I want to talk 00:54:29.480 --> 00:54:31.030 align:start position:0% decentralized exchanges I want to talk about<00:54:29.599> one<00:54:29.960> application<00:54:30.140> that's<00:54:30.829> especially 00:54:31.030 --> 00:54:31.040 align:start position:0% about one application that's especially 00:54:31.040 --> 00:54:34.750 align:start position:0% about one application that's especially exciting<00:54:31.730> this<00:54:32.210> is<00:54:32.390> called<00:54:32.569> Cara<00:54:32.930> and<00:54:33.460> Cara<00:54:34.460> is 00:54:34.750 --> 00:54:34.760 align:start position:0% exciting this is called Cara and Cara is 00:54:34.760 --> 00:54:37.809 align:start position:0% exciting this is called Cara and Cara is being<00:54:35.720> deployed<00:54:35.990> on<00:54:36.140> Oasis<00:54:36.589> it's<00:54:37.309> designed<00:54:37.670> to 00:54:37.809 --> 00:54:37.819 align:start position:0% being deployed on Oasis it's designed to 00:54:37.819 --> 00:54:40.270 align:start position:0% being deployed on Oasis it's designed to solve<00:54:38.059> this<00:54:38.540> problem<00:54:38.750> of<00:54:39.170> data<00:54:39.530> silos<00:54:39.980> around 00:54:40.270 --> 00:54:40.280 align:start position:0% solve this problem of data silos around 00:54:40.280 --> 00:54:43.960 align:start position:0% solve this problem of data silos around medical<00:54:40.460> data<00:54:41.000> so<00:54:41.240> today<00:54:41.540> you<00:54:42.200> know<00:54:42.970> medical 00:54:43.960 --> 00:54:43.970 align:start position:0% medical data so today you know medical 00:54:43.970 --> 00:54:45.789 align:start position:0% medical data so today you know medical data<00:54:44.150> is<00:54:44.240> extremely<00:54:44.720> valuable<00:54:44.839> for<00:54:45.319> for 00:54:45.789 --> 00:54:45.799 align:start position:0% data is extremely valuable for for 00:54:45.799 --> 00:54:48.190 align:start position:0% data is extremely valuable for for research<00:54:46.040> purposes<00:54:46.630> but<00:54:47.630> users<00:54:47.869> are 00:54:48.190 --> 00:54:48.200 align:start position:0% research purposes but users are 00:54:48.200 --> 00:54:49.809 align:start position:0% research purposes but users are reluctant<00:54:48.829> to<00:54:48.950> share<00:54:48.980> their<00:54:49.309> medical<00:54:49.579> data 00:54:49.809 --> 00:54:49.819 align:start position:0% reluctant to share their medical data 00:54:49.819 --> 00:54:52.809 align:start position:0% reluctant to share their medical data rightly<00:54:50.690> so<00:54:50.869> primarily<00:54:51.829> because<00:54:52.099> of<00:54:52.280> privacy 00:54:52.809 --> 00:54:52.819 align:start position:0% rightly so primarily because of privacy 00:54:52.819 --> 00:54:54.309 align:start position:0% rightly so primarily because of privacy concerns<00:54:53.119> right<00:54:53.510> because<00:54:53.869> they<00:54:54.020> don't<00:54:54.049> know 00:54:54.309 --> 00:54:54.319 align:start position:0% concerns right because they don't know 00:54:54.319 --> 00:54:56.530 align:start position:0% concerns right because they don't know what<00:54:54.589> people<00:54:54.710> will<00:54:55.010> use<00:54:55.309> the<00:54:55.490> data<00:54:55.640> for<00:54:55.880> so 00:54:56.530 --> 00:54:56.540 align:start position:0% what people will use the data for so 00:54:56.540 --> 00:54:58.210 align:start position:0% what people will use the data for so Cara<00:54:56.809> tries<00:54:57.140> to<00:54:57.290> solve<00:54:57.470> that<00:54:57.650> problem<00:54:58.010> and<00:54:58.160> the 00:54:58.210 --> 00:54:58.220 align:start position:0% Cara tries to solve that problem and the 00:54:58.220 --> 00:55:01.329 align:start position:0% Cara tries to solve that problem and the way<00:54:58.309> it<00:54:58.430> does<00:54:58.609> that<00:54:58.640> is<00:54:59.440> by<00:55:00.440> allowing<00:55:00.710> patients 00:55:01.329 --> 00:55:01.339 align:start position:0% way it does that is by allowing patients 00:55:01.339 --> 00:55:03.970 align:start position:0% way it does that is by allowing patients and<00:55:01.819> doctors<00:55:01.970> to<00:55:02.480> input<00:55:03.049> their<00:55:03.200> data<00:55:03.440> into<00:55:03.950> a 00:55:03.970 --> 00:55:03.980 align:start position:0% and doctors to input their data into a 00:55:03.980 --> 00:55:04.900 align:start position:0% and doctors to input their data into a smart<00:55:04.280> contract 00:55:04.900 --> 00:55:04.910 align:start position:0% smart contract 00:55:04.910 --> 00:55:07.570 align:start position:0% smart contract and<00:55:05.830> researchers<00:55:06.830> that<00:55:06.950> want<00:55:07.130> to<00:55:07.370> train 00:55:07.570 --> 00:55:07.580 align:start position:0% and researchers that want to train 00:55:07.580 --> 00:55:10.840 align:start position:0% and researchers that want to train models<00:55:08.090> on<00:55:08.330> that<00:55:08.870> data<00:55:09.370> can<00:55:10.370> submit<00:55:10.670> those 00:55:10.840 --> 00:55:10.850 align:start position:0% models on that data can submit those 00:55:10.850 --> 00:55:12.580 align:start position:0% models on that data can submit those models<00:55:11.240> to<00:55:11.300> the<00:55:11.480> smart<00:55:11.720> contract<00:55:12.140> and<00:55:12.350> the 00:55:12.580 --> 00:55:12.590 align:start position:0% models to the smart contract and the 00:55:12.590 --> 00:55:14.470 align:start position:0% models to the smart contract and the smart<00:55:12.830> contract<00:55:12.980> sort<00:55:13.700> of<00:55:13.790> mediates<00:55:14.240> that 00:55:14.470 --> 00:55:14.480 align:start position:0% smart contract sort of mediates that 00:55:14.480 --> 00:55:17.440 align:start position:0% smart contract sort of mediates that interaction<00:55:15.230> and<00:55:16.040> the<00:55:16.340> entire<00:55:16.610> thing<00:55:16.910> runs<00:55:17.180> on 00:55:17.440 --> 00:55:17.450 align:start position:0% interaction and the entire thing runs on 00:55:17.450 --> 00:55:20.350 align:start position:0% interaction and the entire thing runs on the<00:55:17.870> Oasis<00:55:18.410> blockchain<00:55:18.830> once<00:55:19.730> the<00:55:19.940> bottle<00:55:20.270> is 00:55:20.350 --> 00:55:20.360 align:start position:0% the Oasis blockchain once the bottle is 00:55:20.360 --> 00:55:23.950 align:start position:0% the Oasis blockchain once the bottle is trained<00:55:20.660> the<00:55:21.170> users<00:55:21.590> are<00:55:21.860> paid<00:55:22.520> tokens<00:55:22.960> you 00:55:23.950 --> 00:55:23.960 align:start position:0% trained the users are paid tokens you 00:55:23.960 --> 00:55:25.570 align:start position:0% trained the users are paid tokens you know<00:55:24.080> to<00:55:24.260> compensate<00:55:24.740> them<00:55:24.890> for<00:55:24.920> contributing 00:55:25.570 --> 00:55:25.580 align:start position:0% know to compensate them for contributing 00:55:25.580 --> 00:55:27.370 align:start position:0% know to compensate them for contributing their<00:55:25.730> data<00:55:25.910> and<00:55:26.120> the<00:55:26.300> researcher<00:55:26.780> receives<00:55:27.140> a 00:55:27.370 --> 00:55:27.380 align:start position:0% their data and the researcher receives a 00:55:27.380 --> 00:55:29.470 align:start position:0% their data and the researcher receives a trainer<00:55:27.890> model<00:55:28.250> so<00:55:28.580> the<00:55:28.970> nice<00:55:29.150> thing<00:55:29.360> about 00:55:29.470 --> 00:55:29.480 align:start position:0% trainer model so the nice thing about 00:55:29.480 --> 00:55:31.270 align:start position:0% trainer model so the nice thing about running<00:55:29.930> this<00:55:30.230> as<00:55:30.380> a<00:55:30.410> smart<00:55:30.650> contract<00:55:31.130> of 00:55:31.270 --> 00:55:31.280 align:start position:0% running this as a smart contract of 00:55:31.280 --> 00:55:33.700 align:start position:0% running this as a smart contract of course<00:55:31.490> is<00:55:31.640> that<00:55:31.820> it<00:55:32.210> means<00:55:32.450> the<00:55:32.720> patient's 00:55:33.700 --> 00:55:33.710 align:start position:0% course is that it means the patient's 00:55:33.710 --> 00:55:35.200 align:start position:0% course is that it means the patient's don't<00:55:33.830> have<00:55:34.040> to<00:55:34.190> trust<00:55:34.400> researchers<00:55:35.000> they 00:55:35.200 --> 00:55:35.210 align:start position:0% don't have to trust researchers they 00:55:35.210 --> 00:55:37.900 align:start position:0% don't have to trust researchers they know<00:55:35.420> that<00:55:36.140> their<00:55:36.620> data<00:55:36.860> will<00:55:37.100> only<00:55:37.340> be<00:55:37.640> used 00:55:37.900 --> 00:55:37.910 align:start position:0% know that their data will only be used 00:55:37.910 --> 00:55:40.330 align:start position:0% know that their data will only be used for<00:55:38.120> the<00:55:38.330> purpose<00:55:38.690> of<00:55:38.840> training<00:55:39.770> this<00:55:39.920> machine 00:55:40.330 --> 00:55:40.340 align:start position:0% for the purpose of training this machine 00:55:40.340 --> 00:55:42.970 align:start position:0% for the purpose of training this machine learning<00:55:40.610> model<00:55:40.880> and<00:55:41.260> because<00:55:42.260> this<00:55:42.410> runs<00:55:42.710> on 00:55:42.970 --> 00:55:42.980 align:start position:0% learning model and because this runs on 00:55:42.980 --> 00:55:45.490 align:start position:0% learning model and because this runs on a<00:55:43.040> platform<00:55:43.460> that<00:55:44.030> can<00:55:44.360> expose<00:55:44.690> secure 00:55:45.490 --> 00:55:45.500 align:start position:0% a platform that can expose secure 00:55:45.500 --> 00:55:48.640 align:start position:0% a platform that can expose secure enclaves<00:55:45.860> then<00:55:46.430> all<00:55:46.790> of<00:55:46.850> the<00:55:47.450> computation<00:55:48.080> can 00:55:48.640 --> 00:55:48.650 align:start position:0% enclaves then all of the computation can 00:55:48.650 --> 00:55:51.400 align:start position:0% enclaves then all of the computation can run<00:55:48.860> in<00:55:49.040> a<00:55:49.130> secure<00:55:49.520> Enclave<00:55:50.410> allowing 00:55:51.400 --> 00:55:51.410 align:start position:0% run in a secure Enclave allowing 00:55:51.410 --> 00:55:52.810 align:start position:0% run in a secure Enclave allowing patients<00:55:51.590> to<00:55:51.920> know<00:55:52.100> that<00:55:52.310> their<00:55:52.460> data<00:55:52.610> won't 00:55:52.810 --> 00:55:52.820 align:start position:0% patients to know that their data won't 00:55:52.820 --> 00:55:55.900 align:start position:0% patients to know that their data won't be<00:55:53.030> leaked<00:55:53.780> or<00:55:54.470> viewed<00:55:54.860> by<00:55:55.100> even<00:55:55.640> the<00:55:55.730> worker 00:55:55.900 --> 00:55:55.910 align:start position:0% be leaked or viewed by even the worker 00:55:55.910 --> 00:55:57.280 align:start position:0% be leaked or viewed by even the worker that's<00:55:56.300> doing<00:55:56.540> this<00:55:56.630> training<00:55:56.840> and<00:55:57.050> this<00:55:57.140> is 00:55:57.280 --> 00:55:57.290 align:start position:0% that's doing this training and this is 00:55:57.290 --> 00:55:58.780 align:start position:0% that's doing this training and this is exactly<00:55:57.650> why<00:55:57.830> secure<00:55:58.190> enclaves<00:55:58.520> are<00:55:58.670> so 00:55:58.780 --> 00:55:58.790 align:start position:0% exactly why secure enclaves are so 00:55:58.790 --> 00:56:00.220 align:start position:0% exactly why secure enclaves are so exciting<00:55:59.240> for<00:55:59.360> these<00:55:59.780> sorts<00:56:00.020> of<00:56:00.080> applications 00:56:00.220 --> 00:56:00.230 align:start position:0% exciting for these sorts of applications 00:56:00.230 --> 00:56:02.710 align:start position:0% exciting for these sorts of applications is<00:56:00.770> because<00:56:01.010> it<00:56:01.130> allows<00:56:01.370> you<00:56:01.580> to<00:56:01.610> run<00:56:01.820> very 00:56:02.710 --> 00:56:02.720 align:start position:0% is because it allows you to run very 00:56:02.720 --> 00:56:05.380 align:start position:0% is because it allows you to run very complex<00:56:03.370> application<00:56:04.370> workloads<00:56:04.730> with<00:56:05.120> very 00:56:05.380 --> 00:56:05.390 align:start position:0% complex application workloads with very 00:56:05.390 --> 00:56:06.640 align:start position:0% complex application workloads with very little<00:56:05.540> performance<00:56:06.080> overhead<00:56:06.320> while 00:56:06.640 --> 00:56:06.650 align:start position:0% little performance overhead while 00:56:06.650 --> 00:56:10.060 align:start position:0% little performance overhead while getting<00:56:06.920> those<00:56:07.220> security<00:56:07.820> guarantees<00:56:08.680> so<00:56:09.680> if 00:56:10.060 --> 00:56:10.070 align:start position:0% getting those security guarantees so if 00:56:10.070 --> 00:56:11.620 align:start position:0% getting those security guarantees so if you're<00:56:10.460> interested<00:56:10.850> in<00:56:11.150> learning<00:56:11.300> more<00:56:11.480> about 00:56:11.620 --> 00:56:11.630 align:start position:0% you're interested in learning more about 00:56:11.630 --> 00:56:13.480 align:start position:0% you're interested in learning more about this<00:56:12.020> or<00:56:12.230> you<00:56:12.350> want<00:56:12.530> to<00:56:12.620> get<00:56:12.740> involved<00:56:13.100> one<00:56:13.340> of 00:56:13.480 --> 00:56:13.490 align:start position:0% this or you want to get involved one of 00:56:13.490 --> 00:56:15.550 align:start position:0% this or you want to get involved one of the<00:56:13.640> developers<00:56:14.120> of<00:56:14.630> this<00:56:14.840> project<00:56:15.200> Nick<00:56:15.350> is 00:56:15.550 --> 00:56:15.560 align:start position:0% the developers of this project Nick is 00:56:15.560 --> 00:56:17.650 align:start position:0% the developers of this project Nick is actually<00:56:15.980> in<00:56:16.220> attendance<00:56:16.640> today<00:56:16.820> and<00:56:17.090> he'd 00:56:17.650 --> 00:56:17.660 align:start position:0% actually in attendance today and he'd 00:56:17.660 --> 00:56:21.220 align:start position:0% actually in attendance today and he'd love<00:56:17.810> to<00:56:17.840> chat<00:56:18.080> with<00:56:18.110> you<00:56:19.150> okay<00:56:20.150> so<00:56:20.390> that's<00:56:20.990> the 00:56:21.220 --> 00:56:21.230 align:start position:0% love to chat with you okay so that's the 00:56:21.230 --> 00:56:22.780 align:start position:0% love to chat with you okay so that's the end<00:56:21.350> of<00:56:21.410> my<00:56:21.530> talk<00:56:21.740> if<00:56:21.980> you're<00:56:22.130> interested<00:56:22.670> in 00:56:22.780 --> 00:56:22.790 align:start position:0% end of my talk if you're interested in 00:56:22.790 --> 00:56:23.940 align:start position:0% end of my talk if you're interested in building<00:56:22.970> a<00:56:23.330> privacy-preserving 00:56:23.940 --> 00:56:23.950 align:start position:0% building a privacy-preserving 00:56:23.950 --> 00:56:26.290 align:start position:0% building a privacy-preserving application<00:56:24.950> on<00:56:25.160> our<00:56:25.400> test<00:56:25.610> net<00:56:25.760> you<00:56:26.150> can<00:56:26.240> go 00:56:26.290 --> 00:56:26.300 align:start position:0% application on our test net you can go 00:56:26.300 --> 00:56:28.270 align:start position:0% application on our test net you can go to<00:56:26.360> this<00:56:26.450> URL<00:56:26.660> you<00:56:27.410> can<00:56:27.560> sign<00:56:27.920> up<00:56:27.950> to<00:56:28.100> our 00:56:28.270 --> 00:56:28.280 align:start position:0% to this URL you can sign up to our 00:56:28.280 --> 00:56:32.200 align:start position:0% to this URL you can sign up to our Twitter<00:56:28.730> to<00:56:29.230> get<00:56:30.230> updates<00:56:30.290> and<00:56:31.000> you<00:56:32.000> know<00:56:32.090> if 00:56:32.200 --> 00:56:32.210 align:start position:0% Twitter to get updates and you know if 00:56:32.210 --> 00:56:34.210 align:start position:0% Twitter to get updates and you know if you're<00:56:32.330> interested<00:56:32.720> in<00:56:32.810> the<00:56:32.900> space<00:56:33.110> and<00:56:33.380> you 00:56:34.210 --> 00:56:34.220 align:start position:0% you're interested in the space and you 00:56:34.220 --> 00:56:35.590 align:start position:0% you're interested in the space and you want<00:56:34.340> to<00:56:34.400> help<00:56:34.550> us<00:56:34.670> build<00:56:34.880> the<00:56:34.970> system<00:56:35.300> we're 00:56:35.590 --> 00:56:35.600 align:start position:0% want to help us build the system we're 00:56:35.600 --> 00:56:37.540 align:start position:0% want to help us build the system we're always<00:56:35.750> looking<00:56:35.990> for<00:56:36.170> for<00:56:36.950> passionate<00:56:37.400> people 00:56:37.540 --> 00:56:37.550 align:start position:0% always looking for for passionate people 00:56:37.550 --> 00:56:40.270 align:start position:0% always looking for for passionate people who<00:56:37.700> are<00:56:38.200> really<00:56:39.200> excited<00:56:39.230> about<00:56:39.620> privacy<00:56:40.160> as 00:56:40.270 --> 00:56:40.280 align:start position:0% who are really excited about privacy as 00:56:40.280 --> 00:56:47.850 align:start position:0% who are really excited about privacy as we<00:56:40.400> are<00:56:42.190> that's<00:56:43.190> it<00:56:43.370> thank<00:56:43.580> you 00:56:47.850 --> 00:56:47.860 align:start position:0% 00:56:47.860 --> 00:56:55.780 align:start position:0% thank<00:56:48.860> thanks<00:56:49.160> Nora<00:56:53.140> a<00:56:54.140> little<00:56:54.830> bit<00:56:54.980> we<00:56:55.340> shift 00:56:55.780 --> 00:56:55.790 align:start position:0% thank thanks Nora a little bit we shift 00:56:55.790 --> 00:56:58.480 align:start position:0% thank thanks Nora a little bit we shift the<00:56:55.940> gear<00:56:56.150> in<00:56:56.330> the<00:56:56.420> sense<00:56:56.600> like<00:56:56.780> you<00:56:56.900> know<00:56:57.490> in 00:56:58.480 --> 00:56:58.490 align:start position:0% the gear in the sense like you know in 00:56:58.490 --> 00:57:00.850 align:start position:0% the gear in the sense like you know in the<00:56:58.670> last<00:56:58.850> two<00:56:59.360> section<00:56:59.720> it<00:56:59.810> was<00:57:00.020> the<00:57:00.410> idea<00:57:00.650> was 00:57:00.850 --> 00:57:00.860 align:start position:0% the last two section it was the idea was 00:57:00.860 --> 00:57:03.609 align:start position:0% the last two section it was the idea was to<00:57:00.890> say<00:57:01.850> how<00:57:02.450> you<00:57:02.600> could<00:57:02.780> use<00:57:03.020> some<00:57:03.320> of<00:57:03.440> these 00:57:03.609 --> 00:57:03.619 align:start position:0% to say how you could use some of these 00:57:03.619 --> 00:57:06.220 align:start position:0% to say how you could use some of these things<00:57:03.890> with<00:57:04.850> some<00:57:05.030> real-world<00:57:05.600> applications 00:57:06.220 --> 00:57:06.230 align:start position:0% things with some real-world applications 00:57:06.230 --> 00:57:09.210 align:start position:0% things with some real-world applications that<00:57:06.940> various<00:57:07.940> partners<00:57:08.360> are<00:57:08.480> building<00:57:08.810> and 00:57:09.210 --> 00:57:09.220 align:start position:0% that various partners are building and 00:57:09.220 --> 00:57:13.500 align:start position:0% that various partners are building and now<00:57:10.220> I<00:57:10.250> will<00:57:10.640> have<00:57:11.080> Marlee<00:57:12.080> from<00:57:12.410> Microsoft 00:57:13.500 --> 00:57:13.510 align:start position:0% now I will have Marlee from Microsoft 00:57:13.510 --> 00:57:17.490 align:start position:0% now I will have Marlee from Microsoft talk<00:57:14.510> about<00:57:14.780> like<00:57:14.960> you<00:57:14.990> know<00:57:16.000> if<00:57:17.000> you<00:57:17.119> were<00:57:17.270> to 00:57:17.490 --> 00:57:17.500 align:start position:0% talk about like you know if you were to 00:57:17.500 --> 00:57:19.630 align:start position:0% talk about like you know if you were to say<00:57:18.500> that<00:57:18.530> okay<00:57:18.920> I<00:57:18.980> want<00:57:19.160> to<00:57:19.220> build<00:57:19.369> something 00:57:19.630 --> 00:57:19.640 align:start position:0% say that okay I want to build something 00:57:19.640 --> 00:57:21.550 align:start position:0% say that okay I want to build something on<00:57:19.880> these<00:57:20.030> enclaves<00:57:20.240> where<00:57:20.720> could<00:57:20.990> I<00:57:21.080> actually 00:57:21.550 --> 00:57:21.560 align:start position:0% on these enclaves where could I actually 00:57:21.560 --> 00:57:25.090 align:start position:0% on these enclaves where could I actually get<00:57:22.520> access<00:57:22.910> to<00:57:22.940> this<00:57:23.180> hardware<00:57:23.630> and<00:57:23.710> and<00:57:24.710> oh 00:57:25.090 --> 00:57:25.100 align:start position:0% get access to this hardware and and oh 00:57:25.100 --> 00:57:29.040 align:start position:0% get access to this hardware and and oh and<00:57:25.520> what's<00:57:25.760> the<00:57:26.000> environment<00:57:26.450> so<00:57:27.290> Marlee 00:57:29.040 --> 00:57:29.050 align:start position:0% and what's the environment so Marlee 00:57:29.050 --> 00:57:34.630 align:start position:0% and what's the environment so Marlee besides<00:57:30.050> that<00:57:30.200> pyramid<00:57:30.910> so<00:57:32.560> Microsoft<00:57:33.640> we're 00:57:34.630 --> 00:57:34.640 align:start position:0% besides that pyramid so Microsoft we're 00:57:34.640 --> 00:57:37.300 align:start position:0% besides that pyramid so Microsoft we're from<00:57:34.790> I<00:57:35.150> work<00:57:35.630> in<00:57:35.750> the<00:57:35.840> Azure<00:57:36.020> team<00:57:36.290> and<00:57:36.530> that's 00:57:37.300 --> 00:57:37.310 align:start position:0% from I work in the Azure team and that's 00:57:37.310 --> 00:57:39.340 align:start position:0% from I work in the Azure team and that's our<00:57:37.490> cloud<00:57:37.820> platform<00:57:38.000> and<00:57:38.600> one<00:57:38.990> of<00:57:39.110> the<00:57:39.170> major 00:57:39.340 --> 00:57:39.350 align:start position:0% our cloud platform and one of the major 00:57:39.350 --> 00:57:44.109 align:start position:0% our cloud platform and one of the major issues<00:57:39.860> of<00:57:40.520> adoption<00:57:41.740> for<00:57:42.740> clouds<00:57:43.190> is<00:57:43.700> why 00:57:44.109 --> 00:57:44.119 align:start position:0% issues of adoption for clouds is why 00:57:44.119 --> 00:57:46.900 align:start position:0% issues of adoption for clouds is why would<00:57:44.360> I<00:57:44.390> run<00:57:44.690> my<00:57:44.960> code<00:57:45.260> in<00:57:45.650> a<00:57:46.070> public<00:57:46.520> network 00:57:46.900 --> 00:57:46.910 align:start position:0% would I run my code in a public network 00:57:46.910 --> 00:57:50.920 align:start position:0% would I run my code in a public network when<00:57:47.690> you<00:57:48.350> know<00:57:48.470> it<00:57:49.220> I<00:57:49.670> have<00:57:49.910> to<00:57:50.030> trust<00:57:50.270> you 00:57:50.920 --> 00:57:50.930 align:start position:0% when you know it I have to trust you 00:57:50.930 --> 00:57:54.820 align:start position:0% when you know it I have to trust you Microsoft<00:57:51.850> to<00:57:52.850> not<00:57:53.390> steal<00:57:54.290> my<00:57:54.470> intellectual 00:57:54.820 --> 00:57:54.830 align:start position:0% Microsoft to not steal my intellectual 00:57:54.830 --> 00:57:56.560 align:start position:0% Microsoft to not steal my intellectual property<00:57:55.130> and<00:57:55.609> then<00:57:55.700> you<00:57:56.000> know<00:57:56.180> do<00:57:56.300> all<00:57:56.359> the 00:57:56.560 --> 00:57:56.570 align:start position:0% property and then you know do all the 00:57:56.570 --> 00:57:58.980 align:start position:0% property and then you know do all the evil<00:57:56.960> things<00:57:57.170> that<00:57:57.380> used<00:57:57.530> to<00:57:57.710> do<00:57:57.980> in<00:57:58.160> the<00:57:58.280> past 00:57:58.980 --> 00:57:58.990 align:start position:0% evil things that used to do in the past 00:57:58.990 --> 00:58:03.849 align:start position:0% evil things that used to do in the past Darth<00:57:59.990> Vader<00:58:00.260> ish<00:58:01.240> so<00:58:02.240> we<00:58:02.570> see<00:58:02.859> confidential 00:58:03.849 --> 00:58:03.859 align:start position:0% Darth Vader ish so we see confidential 00:58:03.859 --> 00:58:05.170 align:start position:0% Darth Vader ish so we see confidential competing<00:58:04.160> sort<00:58:04.340> of<00:58:04.400> holistically<00:58:04.850> and<00:58:05.060> say 00:58:05.170 --> 00:58:05.180 align:start position:0% competing sort of holistically and say 00:58:05.180 --> 00:58:06.880 align:start position:0% competing sort of holistically and say this<00:58:05.450> is<00:58:05.600> super<00:58:05.900> important<00:58:06.290> for<00:58:06.410> us<00:58:06.470> to<00:58:06.650> grow 00:58:06.880 --> 00:58:06.890 align:start position:0% this is super important for us to grow 00:58:06.890 --> 00:58:09.490 align:start position:0% this is super important for us to grow our<00:58:07.190> core<00:58:07.640> business<00:58:08.030> we<00:58:08.780> have<00:58:09.050> to<00:58:09.200> be<00:58:09.290> able<00:58:09.380> to 00:58:09.490 --> 00:58:09.500 align:start position:0% our core business we have to be able to 00:58:09.500 --> 00:58:12.640 align:start position:0% our core business we have to be able to have<00:58:09.680> a<00:58:09.710> cloud<00:58:10.010> platform<00:58:10.190> that<00:58:10.910> our<00:58:11.650> customers 00:58:12.640 --> 00:58:12.650 align:start position:0% have a cloud platform that our customers 00:58:12.650 --> 00:58:14.800 align:start position:0% have a cloud platform that our customers whether<00:58:12.890> they're<00:58:13.220> large<00:58:13.850> corporation<00:58:14.540> or 00:58:14.800 --> 00:58:14.810 align:start position:0% whether they're large corporation or 00:58:14.810 --> 00:58:16.720 align:start position:0% whether they're large corporation or someone<00:58:15.650> building<00:58:15.920> that<00:58:16.040> decentralized 00:58:16.720 --> 00:58:16.730 align:start position:0% someone building that decentralized 00:58:16.730 --> 00:58:18.730 align:start position:0% someone building that decentralized application<00:58:17.510> and<00:58:18.170> what<00:58:18.290> I<00:58:18.320> would<00:58:18.440> like<00:58:18.619> to 00:58:18.730 --> 00:58:18.740 align:start position:0% application and what I would like to 00:58:18.740 --> 00:58:20.170 align:start position:0% application and what I would like to call<00:58:18.920> the<00:58:19.130> next-generation<00:58:19.609> killer 00:58:20.170 --> 00:58:20.180 align:start position:0% call the next-generation killer 00:58:20.180 --> 00:58:22.930 align:start position:0% call the next-generation killer decentralized<00:58:20.960> application<00:58:21.650> needs<00:58:22.580> to<00:58:22.760> have 00:58:22.930 --> 00:58:22.940 align:start position:0% decentralized application needs to have 00:58:22.940 --> 00:58:25.030 align:start position:0% decentralized application needs to have the<00:58:23.090> ability<00:58:23.270> to<00:58:23.480> just<00:58:24.380> in<00:58:24.530> time 00:58:25.030 --> 00:58:25.040 align:start position:0% the ability to just in time 00:58:25.040 --> 00:58:29.349 align:start position:0% the ability to just in time grab<00:58:25.760> a<00:58:26.410> secure<00:58:27.609> Enclave<00:58:28.609> we'll<00:58:29.060> talk<00:58:29.240> about 00:58:29.349 --> 00:58:29.359 align:start position:0% grab a secure Enclave we'll talk about 00:58:29.359 --> 00:58:31.300 align:start position:0% grab a secure Enclave we'll talk about this<00:58:29.750> in<00:58:29.869> a<00:58:29.930> minute<00:58:30.080> to<00:58:30.680> be<00:58:30.770> able<00:58:30.859> to<00:58:30.980> execute 00:58:31.300 --> 00:58:31.310 align:start position:0% this in a minute to be able to execute 00:58:31.310 --> 00:58:34.270 align:start position:0% this in a minute to be able to execute some<00:58:31.640> arbitrary<00:58:32.119> code<00:58:32.619> and<00:58:33.619> confidentially 00:58:34.270 --> 00:58:34.280 align:start position:0% some arbitrary code and confidentially 00:58:34.280 --> 00:58:36.240 align:start position:0% some arbitrary code and confidentially execute<00:58:34.609> that<00:58:34.730> and<00:58:34.940> then<00:58:35.090> you<00:58:35.720> know<00:58:35.840> have<00:58:36.080> it 00:58:36.240 --> 00:58:36.250 align:start position:0% execute that and then you know have it 00:58:36.250 --> 00:58:39.790 align:start position:0% execute that and then you know have it its<00:58:37.250> results<00:58:37.730> published<00:58:38.510> on<00:58:38.690> some<00:58:38.960> network<00:58:39.560> of 00:58:39.790 --> 00:58:39.800 align:start position:0% its results published on some network of 00:58:39.800 --> 00:58:41.500 align:start position:0% its results published on some network of some<00:58:39.980> sort<00:58:40.220> how<00:58:40.820> do<00:58:40.880> we<00:58:41.000> make<00:58:41.150> that<00:58:41.270> possible 00:58:41.500 --> 00:58:41.510 align:start position:0% some sort how do we make that possible 00:58:41.510 --> 00:58:45.000 align:start position:0% some sort how do we make that possible what<00:58:42.020> infrastructure<00:58:42.710> is<00:58:42.800> required<00:58:43.510> so 00:58:45.000 --> 00:58:45.010 align:start position:0% what infrastructure is required so 00:58:45.010 --> 00:58:47.140 align:start position:0% what infrastructure is required so that's<00:58:46.010> our<00:58:46.190> main<00:58:46.310> goal<00:58:46.520> is<00:58:46.550> primarily<00:58:47.030> to 00:58:47.140 --> 00:58:47.150 align:start position:0% that's our main goal is primarily to 00:58:47.150 --> 00:58:49.720 align:start position:0% that's our main goal is primarily to remove<00:58:47.359> Microsoft<00:58:47.960> out<00:58:48.770> of<00:58:49.160> the<00:58:49.280> trust<00:58:49.490> base 00:58:49.720 --> 00:58:49.730 align:start position:0% remove Microsoft out of the trust base 00:58:49.730 --> 00:58:51.700 align:start position:0% remove Microsoft out of the trust base so<00:58:49.970> you<00:58:50.000> no<00:58:50.270> longer<00:58:50.450> have<00:58:50.780> to<00:58:50.810> trust<00:58:51.080> Microsoft 00:58:51.700 --> 00:58:51.710 align:start position:0% so you no longer have to trust Microsoft 00:58:51.710 --> 00:58:55.990 align:start position:0% so you no longer have to trust Microsoft to<00:58:52.400> run<00:58:52.609> your<00:58:53.210> data<00:58:53.869> in<00:58:54.290> your<00:58:54.440> code<00:58:54.740> in<00:58:55.100> in<00:58:55.490> our 00:58:55.990 --> 00:58:56.000 align:start position:0% to run your data in your code in in our 00:58:56.000 --> 00:58:58.270 align:start position:0% to run your data in your code in in our cloud<00:58:56.240> which<00:58:56.540> seems<00:58:57.050> kind<00:58:57.260> of<00:58:57.380> weird<00:58:57.530> but 00:58:58.270 --> 00:58:58.280 align:start position:0% cloud which seems kind of weird but 00:58:58.280 --> 00:59:00.220 align:start position:0% cloud which seems kind of weird but that's<00:58:59.210> really<00:58:59.420> quarter 00:59:00.220 --> 00:59:00.230 align:start position:0% that's really quarter 00:59:00.230 --> 00:59:02.710 align:start position:0% that's really quarter growing<00:59:00.800> our<00:59:00.920> business<00:59:02.030> it's<00:59:02.330> quarter<00:59:02.570> not 00:59:02.710 --> 00:59:02.720 align:start position:0% growing our business it's quarter not 00:59:02.720 --> 00:59:04.630 align:start position:0% growing our business it's quarter not only<00:59:02.960> giving<00:59:03.260> you<00:59:04.070> know<00:59:04.160> our<00:59:04.310> largest 00:59:04.630 --> 00:59:04.640 align:start position:0% only giving you know our largest 00:59:04.640 --> 00:59:07.720 align:start position:0% only giving you know our largest financial<00:59:05.480> services<00:59:05.930> customers<00:59:06.470> but<00:59:07.070> also<00:59:07.100> a 00:59:07.720 --> 00:59:07.730 align:start position:0% financial services customers but also a 00:59:07.730 --> 00:59:09.460 align:start position:0% financial services customers but also a lot<00:59:08.180> of<00:59:08.300> you<00:59:08.720> folks<00:59:08.930> that<00:59:09.140> are<00:59:09.230> really 00:59:09.460 --> 00:59:09.470 align:start position:0% lot of you folks that are really 00:59:09.470 --> 00:59:11.830 align:start position:0% lot of you folks that are really concerned<00:59:09.800> with<00:59:10.070> you<00:59:10.340> know<00:59:10.840> centralization 00:59:11.830 --> 00:59:11.840 align:start position:0% concerned with you know centralization 00:59:11.840 --> 00:59:14.500 align:start position:0% concerned with you know centralization and<00:59:12.080> and<00:59:12.290> the<00:59:12.830> I've<00:59:13.369> been<00:59:13.580> doing<00:59:14.150> this<00:59:14.300> since 00:59:14.500 --> 00:59:14.510 align:start position:0% and and the I've been doing this since 00:59:14.510 --> 00:59:16.660 align:start position:0% and and the I've been doing this since 2015<00:59:14.930> and<00:59:15.470> I<00:59:15.680> always<00:59:16.130> get<00:59:16.310> that<00:59:16.369> first 00:59:16.660 --> 00:59:16.670 align:start position:0% 2015 and I always get that first 00:59:16.670 --> 00:59:18.250 align:start position:0% 2015 and I always get that first question<00:59:16.940> people<00:59:17.210> walk<00:59:17.420> up<00:59:17.450> to<00:59:17.630> me<00:59:17.840> what's 00:59:18.250 --> 00:59:18.260 align:start position:0% question people walk up to me what's 00:59:18.260 --> 00:59:19.420 align:start position:0% question people walk up to me what's Microsoft<00:59:18.800> doing<00:59:18.950> here 00:59:19.420 --> 00:59:19.430 align:start position:0% Microsoft doing here 00:59:19.430 --> 00:59:21.849 align:start position:0% Microsoft doing here you're<00:59:20.330> centralized<00:59:20.930> you<00:59:21.200> know<00:59:21.290> you<00:59:21.740> know 00:59:21.849 --> 00:59:21.859 align:start position:0% you're centralized you know you know 00:59:21.859 --> 00:59:25.930 align:start position:0% you're centralized you know you know it's<00:59:22.630> okay<00:59:23.630> if<00:59:24.410> we<00:59:24.590> get<00:59:24.740> it<00:59:24.890> but<00:59:25.400> we're<00:59:25.790> trying 00:59:25.930 --> 00:59:25.940 align:start position:0% it's okay if we get it but we're trying 00:59:25.940 --> 00:59:27.880 align:start position:0% it's okay if we get it but we're trying to<00:59:26.090> contribute<00:59:26.359> into<00:59:26.690> the<00:59:26.900> distributed<00:59:27.350> space 00:59:27.880 --> 00:59:27.890 align:start position:0% to contribute into the distributed space 00:59:27.890 --> 00:59:30.359 align:start position:0% to contribute into the distributed space oh<00:59:27.920> well<00:59:28.160> this<00:59:28.220> is<00:59:28.280> broadly<00:59:28.820> applicable<00:59:29.119> so 00:59:30.359 --> 00:59:30.369 align:start position:0% oh well this is broadly applicable so 00:59:30.369 --> 00:59:32.800 align:start position:0% oh well this is broadly applicable so the<00:59:31.369> thing<00:59:31.550> that<00:59:31.670> we've<00:59:31.820> the<00:59:32.480> previous 00:59:32.800 --> 00:59:32.810 align:start position:0% the thing that we've the previous 00:59:32.810 --> 00:59:35.290 align:start position:0% the thing that we've the previous speakers<00:59:33.460> talked<00:59:34.460> about<00:59:34.670> is<00:59:34.790> how<00:59:35.000> do<00:59:35.060> you 00:59:35.290 --> 00:59:35.300 align:start position:0% speakers talked about is how do you 00:59:35.300 --> 00:59:39.520 align:start position:0% speakers talked about is how do you apply<00:59:35.830> enclaves<00:59:37.420> the<00:59:38.420> news<00:59:38.840> the<00:59:39.109> good<00:59:39.200> news<00:59:39.260> is 00:59:39.520 --> 00:59:39.530 align:start position:0% apply enclaves the news the good news is 00:59:39.530 --> 00:59:40.630 align:start position:0% apply enclaves the news the good news is you<00:59:39.650> can<00:59:39.770> apply<00:59:39.830> it<00:59:39.980> in<00:59:40.130> a<00:59:40.190> lot<00:59:40.369> of<00:59:40.400> different 00:59:40.630 --> 00:59:40.640 align:start position:0% you can apply it in a lot of different 00:59:40.640 --> 00:59:41.950 align:start position:0% you can apply it in a lot of different ways<00:59:40.910> that<00:59:41.150> solves<00:59:41.420> a<00:59:41.480> lot<00:59:41.600> of<00:59:41.720> different 00:59:41.950 --> 00:59:41.960 align:start position:0% ways that solves a lot of different 00:59:41.960 --> 00:59:43.960 align:start position:0% ways that solves a lot of different problems<00:59:42.140> but<00:59:42.530> it<00:59:42.590> is<00:59:42.680> it's<00:59:43.369> not<00:59:43.550> a<00:59:43.609> hammer 00:59:43.960 --> 00:59:43.970 align:start position:0% problems but it is it's not a hammer 00:59:43.970 --> 00:59:46.210 align:start position:0% problems but it is it's not a hammer right<00:59:44.450> it<00:59:45.260> is<00:59:45.410> your<00:59:45.590> hammer<00:59:45.770> and<00:59:45.950> everything's 00:59:46.210 --> 00:59:46.220 align:start position:0% right it is your hammer and everything's 00:59:46.220 --> 00:59:47.770 align:start position:0% right it is your hammer and everything's a<00:59:46.280> nail<00:59:46.430> you<00:59:46.520> try<00:59:46.700> to<00:59:46.760> hit<00:59:47.000> it<00:59:47.240> doesn't<00:59:47.630> solve 00:59:47.770 --> 00:59:47.780 align:start position:0% a nail you try to hit it doesn't solve 00:59:47.780 --> 00:59:50.530 align:start position:0% a nail you try to hit it doesn't solve every<00:59:48.140> problem<00:59:48.369> but<00:59:49.369> when<00:59:49.640> you<00:59:49.730> do<00:59:49.910> find<00:59:50.270> sort 00:59:50.530 --> 00:59:50.540 align:start position:0% every problem but when you do find sort 00:59:50.540 --> 00:59:52.780 align:start position:0% every problem but when you do find sort of<00:59:50.600> an<00:59:50.690> intractable<00:59:51.020> problem<00:59:51.550> having<00:59:52.550> an 00:59:52.780 --> 00:59:52.790 align:start position:0% of an intractable problem having an 00:59:52.790 --> 00:59:55.930 align:start position:0% of an intractable problem having an enclave<00:59:53.650> available<00:59:54.650> to<00:59:54.770> you<00:59:54.980> lets<00:59:55.760> you 00:59:55.930 --> 00:59:55.940 align:start position:0% enclave available to you lets you 00:59:55.940 --> 00:59:58.300 align:start position:0% enclave available to you lets you explore<00:59:56.480> different<00:59:57.380> ways<00:59:57.500> you<00:59:57.920> can<00:59:58.100> solve 00:59:58.300 --> 00:59:58.310 align:start position:0% explore different ways you can solve 00:59:58.310 --> 01:00:00.280 align:start position:0% explore different ways you can solve those<00:59:58.640> difficult<00:59:59.060> problems<00:59:59.450> particularly<01:00:00.080> on 01:00:00.280 --> 01:00:00.290 align:start position:0% those difficult problems particularly on 01:00:00.290 --> 01:00:03.160 align:start position:0% those difficult problems particularly on a<01:00:00.530> privacy<01:00:01.340> and<01:00:01.460> confidentiality<01:00:02.020> so<01:00:03.020> let's 01:00:03.160 --> 01:00:03.170 align:start position:0% a privacy and confidentiality so let's 01:00:03.170 --> 01:00:05.410 align:start position:0% a privacy and confidentiality so let's do<01:00:03.980> this<01:00:04.100> so<01:00:04.280> we're<01:00:04.700> looking<01:00:04.970> at<01:00:05.119> things<01:00:05.300> like 01:00:05.410 --> 01:00:05.420 align:start position:0% do this so we're looking at things like 01:00:05.420 --> 01:00:07.470 align:start position:0% do this so we're looking at things like machine<01:00:05.810> learning<01:00:05.840> sequel<01:00:06.740> server 01:00:07.470 --> 01:00:07.480 align:start position:0% machine learning sequel server 01:00:07.480 --> 01:00:09.310 align:start position:0% machine learning sequel server essentially<01:00:08.480> anything<01:00:09.020> that<01:00:09.140> we're<01:00:09.260> running 01:00:09.310 --> 01:00:09.320 align:start position:0% essentially anything that we're running 01:00:09.320 --> 01:00:11.320 align:start position:0% essentially anything that we're running in<01:00:09.500> the<01:00:09.530> cloud<01:00:09.680> is<01:00:10.190> looking<01:00:10.850> at<01:00:10.970> how<01:00:11.150> they're 01:00:11.320 --> 01:00:11.330 align:start position:0% in the cloud is looking at how they're 01:00:11.330 --> 01:00:14.470 align:start position:0% in the cloud is looking at how they're gonna<01:00:11.450> use<01:00:11.869> te<01:00:12.290> es<01:00:12.650> or<01:00:12.950> trusted<01:00:13.310> compute<01:00:13.760> to 01:00:14.470 --> 01:00:14.480 align:start position:0% gonna use te es or trusted compute to 01:00:14.480 --> 01:00:17.620 align:start position:0% gonna use te es or trusted compute to enhance<01:00:15.140> their<01:00:15.740> product<01:00:16.340> to<01:00:16.940> remove 01:00:17.620 --> 01:00:17.630 align:start position:0% enhance their product to remove 01:00:17.630 --> 01:00:19.840 align:start position:0% enhance their product to remove Microsoft<01:00:18.410> from<01:00:18.560> the<01:00:18.650> chest<01:00:18.890> pain<01:00:19.100> let's<01:00:19.730> go 01:00:19.840 --> 01:00:19.850 align:start position:0% Microsoft from the chest pain let's go 01:00:19.850 --> 01:00:24.190 align:start position:0% Microsoft from the chest pain let's go the<01:00:19.940> next<01:00:20.150> slide<01:00:21.910> okay<01:00:22.910> so<01:00:22.970> some<01:00:23.930> basic<01:00:24.020> things 01:00:24.190 --> 01:00:24.200 align:start position:0% the next slide okay so some basic things 01:00:24.200 --> 01:00:27.400 align:start position:0% the next slide okay so some basic things we're<01:00:24.530> doing<01:00:24.590> is<01:00:24.770> sort<01:00:24.890> of<01:00:24.950> broadly<01:00:26.200> we<01:00:27.200> want 01:00:27.400 --> 01:00:27.410 align:start position:0% we're doing is sort of broadly we want 01:00:27.410 --> 01:00:28.870 align:start position:0% we're doing is sort of broadly we want to<01:00:27.560> have<01:00:27.859> of<01:00:28.040> course<01:00:28.070> this<01:00:28.369> we<01:00:28.550> think<01:00:28.700> this<01:00:28.760> is 01:00:28.870 --> 01:00:28.880 align:start position:0% to have of course this we think this is 01:00:28.880 --> 01:00:30.910 align:start position:0% to have of course this we think this is going<01:00:29.000> to<01:00:29.060> apply<01:00:29.240> everywhere<01:00:29.570> we<01:00:29.920> we're 01:00:30.910 --> 01:00:30.920 align:start position:0% going to apply everywhere we we're 01:00:30.920 --> 01:00:33.310 align:start position:0% going to apply everywhere we we're really<01:00:31.250> interested<01:00:32.000> in<01:00:32.090> hearing<01:00:32.390> customers 01:00:33.310 --> 01:00:33.320 align:start position:0% really interested in hearing customers 01:00:33.320 --> 01:00:36.550 align:start position:0% really interested in hearing customers and<01:00:33.440> how<01:00:33.530> they're<01:00:33.680> using<01:00:34.070> it<01:00:34.220> and<01:00:35.320> we<01:00:36.320> want<01:00:36.500> to 01:00:36.550 --> 01:00:36.560 align:start position:0% and how they're using it and we want to 01:00:36.560 --> 01:00:38.080 align:start position:0% and how they're using it and we want to make<01:00:36.710> sure<01:00:36.740> that<01:00:37.040> we<01:00:37.130> encourage<01:00:37.490> them<01:00:37.820> to<01:00:37.880> do 01:00:38.080 --> 01:00:38.090 align:start position:0% make sure that we encourage them to do 01:00:38.090 --> 01:00:41.730 align:start position:0% make sure that we encourage them to do that<01:00:38.410> any<01:00:39.410> of<01:00:39.530> you<01:00:39.650> worked<01:00:40.340> with<01:00:40.640> enclaves 01:00:41.730 --> 01:00:41.740 align:start position:0% that any of you worked with enclaves 01:00:41.740 --> 01:00:44.050 align:start position:0% that any of you worked with enclaves anybody's<01:00:42.740> written<01:00:43.070> an<01:00:43.250> app<01:00:43.490> that<01:00:43.670> runs<01:00:43.850> in<01:00:43.970> an 01:00:44.050 --> 01:00:44.060 align:start position:0% anybody's written an app that runs in an 01:00:44.060 --> 01:00:45.640 align:start position:0% anybody's written an app that runs in an enclave<01:00:44.300> come<01:00:44.780> on<01:00:44.930> show<01:00:45.230> of<01:00:45.320> hands 01:00:45.640 --> 01:00:45.650 align:start position:0% enclave come on show of hands 01:00:45.650 --> 01:00:49.420 align:start position:0% enclave come on show of hands alright<01:00:46.390> handful<01:00:47.390> of<01:00:47.480> you<01:00:48.430> relatively 01:00:49.420 --> 01:00:49.430 align:start position:0% alright handful of you relatively 01:00:49.430 --> 01:00:52.890 align:start position:0% alright handful of you relatively speaking<01:00:49.609> how<01:00:49.880> easy<01:00:50.150> was<01:00:50.420> it<01:00:51.070> extremely<01:00:52.070> easy 01:00:52.890 --> 01:00:52.900 align:start position:0% speaking how easy was it extremely easy 01:00:52.900 --> 01:00:56.890 align:start position:0% speaking how easy was it extremely easy no<01:00:53.900> it<01:00:54.080> wasn't<01:00:54.500> your<01:00:55.180> probably<01:00:56.180> easy<01:00:56.330> now<01:00:56.570> but 01:00:56.890 --> 01:00:56.900 align:start position:0% no it wasn't your probably easy now but 01:00:56.900 --> 01:00:58.270 align:start position:0% no it wasn't your probably easy now but really<01:00:57.230> you<01:00:57.320> probably<01:00:57.440> look<01:00:57.770> it<01:00:57.890> back<01:00:58.010> at<01:00:58.160> you 01:00:58.270 --> 01:00:58.280 align:start position:0% really you probably look it back at you 01:00:58.280 --> 01:01:00.130 align:start position:0% really you probably look it back at you have<01:00:58.430> some<01:00:58.550> scar<01:00:58.790> tissue<01:00:58.960> because<01:00:59.960> it<01:01:00.020> was 01:01:00.130 --> 01:01:00.140 align:start position:0% have some scar tissue because it was 01:01:00.140 --> 01:01:02.500 align:start position:0% have some scar tissue because it was very<01:01:00.320> difficult<01:01:01.030> what<01:01:02.030> we're<01:01:02.150> trying<01:01:02.359> to<01:01:02.420> do 01:01:02.500 --> 01:01:02.510 align:start position:0% very difficult what we're trying to do 01:01:02.510 --> 01:01:04.060 align:start position:0% very difficult what we're trying to do is<01:01:02.630> it's<01:01:02.900> not<01:01:03.080> just<01:01:03.140> getting<01:01:03.470> your<01:01:03.710> code<01:01:03.890> to 01:01:04.060 --> 01:01:04.070 align:start position:0% is it's not just getting your code to 01:01:04.070 --> 01:01:05.320 align:start position:0% is it's not just getting your code to run<01:01:04.160> in<01:01:04.280> the<01:01:04.369> Enclave<01:01:04.670> but<01:01:04.790> it's<01:01:04.910> also<01:01:05.030> how<01:01:05.270> do 01:01:05.320 --> 01:01:05.330 align:start position:0% run in the Enclave but it's also how do 01:01:05.330 --> 01:01:07.210 align:start position:0% run in the Enclave but it's also how do you<01:01:05.480> get<01:01:05.720> your<01:01:05.869> data<01:01:06.170> to<01:01:06.440> the<01:01:06.470> Enclave<01:01:06.980> how 01:01:07.210 --> 01:01:07.220 align:start position:0% you get your data to the Enclave how 01:01:07.220 --> 01:01:08.710 align:start position:0% you get your data to the Enclave how there's<01:01:07.700> a<01:01:07.730> lot<01:01:07.850> of<01:01:07.940> infrastructure<01:01:08.510> you<01:01:08.690> have 01:01:08.710 --> 01:01:08.720 align:start position:0% there's a lot of infrastructure you have 01:01:08.720 --> 01:01:11.020 align:start position:0% there's a lot of infrastructure you have to<01:01:08.960> do<01:01:09.109> there<01:01:09.350> so<01:01:09.530> we<01:01:09.980> will<01:01:10.070> make<01:01:10.190> it<01:01:10.369> very<01:01:10.550> easy 01:01:11.020 --> 01:01:11.030 align:start position:0% to do there so we will make it very easy 01:01:11.030 --> 01:01:13.450 align:start position:0% to do there so we will make it very easy for<01:01:11.180> you<01:01:11.390> to<01:01:11.480> get<01:01:11.570> your<01:01:11.840> your 01:01:13.450 --> 01:01:13.460 align:start position:0% for you to get your your 01:01:13.460 --> 01:01:15.010 align:start position:0% for you to get your your to<01:01:13.609> introduce<01:01:13.820> this<01:01:14.119> into<01:01:14.300> your<01:01:14.450> environments 01:01:15.010 --> 01:01:15.020 align:start position:0% to introduce this into your environments 01:01:15.020 --> 01:01:17.109 align:start position:0% to introduce this into your environments so<01:01:15.710> we<01:01:15.800> want<01:01:15.980> to<01:01:16.070> solve<01:01:16.520> those<01:01:16.700> difficult 01:01:17.109 --> 01:01:17.119 align:start position:0% so we want to solve those difficult 01:01:17.119 --> 01:01:19.240 align:start position:0% so we want to solve those difficult problems<01:01:17.540> so<01:01:18.500> the<01:01:18.589> things<01:01:18.740> we're<01:01:18.890> doing<01:01:18.950> we're 01:01:19.240 --> 01:01:19.250 align:start position:0% problems so the things we're doing we're 01:01:19.250 --> 01:01:21.280 align:start position:0% problems so the things we're doing we're trying<01:01:19.369> to<01:01:19.550> work<01:01:19.700> with<01:01:19.820> this<01:01:20.000> open<01:01:20.420> Enclave 01:01:21.280 --> 01:01:21.290 align:start position:0% trying to work with this open Enclave 01:01:21.290 --> 01:01:26.710 align:start position:0% trying to work with this open Enclave SDK<01:01:22.359> we<01:01:23.359> to<01:01:23.630> share<01:01:24.080> the<01:01:24.260> desire<01:01:25.190> not<01:01:25.490> to<01:01:25.720> to 01:01:26.710 --> 01:01:26.720 align:start position:0% SDK we to share the desire not to to 01:01:26.720 --> 01:01:28.930 align:start position:0% SDK we to share the desire not to to provide<01:01:26.930> choice<01:01:27.230> in<01:01:27.890> enclaves<01:01:28.339> we're<01:01:28.609> a<01:01:28.640> huge 01:01:28.930 --> 01:01:28.940 align:start position:0% provide choice in enclaves we're a huge 01:01:28.940 --> 01:01:30.970 align:start position:0% provide choice in enclaves we're a huge customer<01:01:29.240> of<01:01:29.599> Intel<01:01:30.080> they're<01:01:30.410> huge<01:01:30.650> partner 01:01:30.970 --> 01:01:30.980 align:start position:0% customer of Intel they're huge partner 01:01:30.980 --> 01:01:34.750 align:start position:0% customer of Intel they're huge partner but<01:01:31.390> there's<01:01:32.770> our<01:01:33.770> customers<01:01:34.190> wanted<01:01:34.520> other 01:01:34.750 --> 01:01:34.760 align:start position:0% but there's our customers wanted other 01:01:34.760 --> 01:01:36.390 align:start position:0% but there's our customers wanted other options<01:01:35.330> so<01:01:35.480> we<01:01:35.510> have<01:01:35.750> things<01:01:35.930> like<01:01:36.080> a 01:01:36.390 --> 01:01:36.400 align:start position:0% options so we have things like a 01:01:36.400 --> 01:01:39.670 align:start position:0% options so we have things like a hypervisor<01:01:37.400> based<01:01:37.820> on<01:01:38.210> clave<01:01:38.630> that's<01:01:39.530> an 01:01:39.670 --> 01:01:39.680 align:start position:0% hypervisor based on clave that's an 01:01:39.680 --> 01:01:41.710 align:start position:0% hypervisor based on clave that's an option<01:01:40.099> working<01:01:40.910> with<01:01:41.000> other<01:01:41.270> hardware 01:01:41.710 --> 01:01:41.720 align:start position:0% option working with other hardware 01:01:41.720 --> 01:01:45.690 align:start position:0% option working with other hardware providers<01:01:42.200> to<01:01:42.410> make<01:01:42.530> sure<01:01:42.890> that<01:01:43.580> we<01:01:44.540> provide<01:01:45.050> a 01:01:45.690 --> 01:01:45.700 align:start position:0% providers to make sure that we provide a 01:01:45.700 --> 01:01:48.550 align:start position:0% providers to make sure that we provide a platform<01:01:46.839> that<01:01:47.839> gives<01:01:47.900> you<01:01:48.109> choice<01:01:48.349> in 01:01:48.550 --> 01:01:48.560 align:start position:0% platform that gives you choice in 01:01:48.560 --> 01:01:50.109 align:start position:0% platform that gives you choice in enclaves<01:01:48.980> but<01:01:49.280> that<01:01:49.400> also<01:01:49.670> introduces<01:01:50.089> a 01:01:50.109 --> 01:01:50.119 align:start position:0% enclaves but that also introduces a 01:01:50.119 --> 01:01:53.050 align:start position:0% enclaves but that also introduces a visual<01:01:50.570> problem<01:01:50.990> which<01:01:51.859> then<01:01:52.580> you<01:01:52.730> start<01:01:52.970> to 01:01:53.050 --> 01:01:53.060 align:start position:0% visual problem which then you start to 01:01:53.060 --> 01:01:54.730 align:start position:0% visual problem which then you start to say<01:01:53.150> okay<01:01:53.359> now<01:01:53.480> I<01:01:53.570> have<01:01:53.660> to<01:01:53.869> write<01:01:54.050> my<01:01:54.230> code 01:01:54.730 --> 01:01:54.740 align:start position:0% say okay now I have to write my code 01:01:54.740 --> 01:01:57.700 align:start position:0% say okay now I have to write my code specific<01:01:55.430> to<01:01:55.550> the<01:01:55.670> type<01:01:55.880> of<01:01:55.910> Enclave<01:01:56.510> that<01:01:56.869> I'm 01:01:57.700 --> 01:01:57.710 align:start position:0% specific to the type of Enclave that I'm 01:01:57.710 --> 01:01:59.470 align:start position:0% specific to the type of Enclave that I'm using<01:01:57.980> and<01:01:58.430> that<01:01:58.460> creates<01:01:58.820> a<01:01:58.940> significant 01:01:59.470 --> 01:01:59.480 align:start position:0% using and that creates a significant 01:01:59.480 --> 01:02:00.910 align:start position:0% using and that creates a significant problem<01:01:59.630> so<01:01:59.780> we're<01:01:59.900> also<01:02:00.050> investing<01:02:00.680> a<01:02:00.740> lot 01:02:00.910 --> 01:02:00.920 align:start position:0% problem so we're also investing a lot 01:02:00.920 --> 01:02:03.310 align:start position:0% problem so we're also investing a lot through<01:02:01.640> Microsoft<01:02:02.119> research<01:02:02.450> in<01:02:02.839> building 01:02:03.310 --> 01:02:03.320 align:start position:0% through Microsoft research in building 01:02:03.320 --> 01:02:06.430 align:start position:0% through Microsoft research in building what<01:02:03.410> we<01:02:03.500> call<01:02:03.650> the<01:02:03.740> open<01:02:03.940> Enclave<01:02:04.940> SDK<01:02:05.660> so 01:02:06.430 --> 01:02:06.440 align:start position:0% what we call the open Enclave SDK so 01:02:06.440 --> 01:02:09.700 align:start position:0% what we call the open Enclave SDK so this<01:02:06.589> is<01:02:06.740> an<01:02:06.859> open<01:02:06.950> source<01:02:07.310> sdk<01:02:08.180> that<01:02:08.660> we<01:02:09.020> will 01:02:09.700 --> 01:02:09.710 align:start position:0% this is an open source sdk that we will 01:02:09.710 --> 01:02:11.859 align:start position:0% this is an open source sdk that we will allow<01:02:09.859> you<01:02:09.920> to<01:02:10.010> to<01:02:10.550> write<01:02:10.760> your<01:02:10.940> apps<01:02:11.089> to<01:02:11.660> that 01:02:11.859 --> 01:02:11.869 align:start position:0% allow you to to write your apps to that 01:02:11.869 --> 01:02:13.420 align:start position:0% allow you to to write your apps to that sdk<01:02:12.410> and<01:02:12.440> abstract<01:02:12.890> yourself<01:02:13.190> from<01:02:13.310> the 01:02:13.420 --> 01:02:13.430 align:start position:0% sdk and abstract yourself from the 01:02:13.430 --> 01:02:15.790 align:start position:0% sdk and abstract yourself from the actual<01:02:13.820> implementation<01:02:14.349> so<01:02:15.349> you<01:02:15.440> sort<01:02:15.619> of<01:02:15.710> get 01:02:15.790 --> 01:02:15.800 align:start position:0% actual implementation so you sort of get 01:02:15.800 --> 01:02:18.579 align:start position:0% actual implementation so you sort of get the<01:02:15.950> the<01:02:16.550> JVM<01:02:17.119> type<01:02:17.480> experience<01:02:18.140> where<01:02:18.380> you 01:02:18.579 --> 01:02:18.589 align:start position:0% the the JVM type experience where you 01:02:18.589 --> 01:02:19.930 align:start position:0% the the JVM type experience where you can<01:02:18.619> write<01:02:18.859> your<01:02:18.890> code<01:02:19.160> once<01:02:19.400> and<01:02:19.580> not<01:02:19.730> really 01:02:19.930 --> 01:02:19.940 align:start position:0% can write your code once and not really 01:02:19.940 --> 01:02:22.270 align:start position:0% can write your code once and not really be<01:02:20.030> concerned<01:02:20.660> with<01:02:20.810> which<01:02:21.020> actual<01:02:21.800> Enclave 01:02:22.270 --> 01:02:22.280 align:start position:0% be concerned with which actual Enclave 01:02:22.280 --> 01:02:23.890 align:start position:0% be concerned with which actual Enclave that<01:02:22.460> you're<01:02:22.580> using<01:02:22.820> so<01:02:23.480> that's<01:02:23.599> sort<01:02:23.690> of<01:02:23.780> a 01:02:23.890 --> 01:02:23.900 align:start position:0% that you're using so that's sort of a 01:02:23.900 --> 01:02:25.750 align:start position:0% that you're using so that's sort of a pragmatic<01:02:24.530> approach<01:02:24.770> to<01:02:25.220> doing<01:02:25.339> that<01:02:25.580> we'll 01:02:25.750 --> 01:02:25.760 align:start position:0% pragmatic approach to doing that we'll 01:02:25.760 --> 01:02:27.640 align:start position:0% pragmatic approach to doing that we'll still<01:02:25.970> have<01:02:26.260> scenarios<01:02:27.260> where<01:02:27.440> you're<01:02:27.530> going 01:02:27.640 --> 01:02:27.650 align:start position:0% still have scenarios where you're going 01:02:27.650 --> 01:02:28.750 align:start position:0% still have scenarios where you're going to<01:02:27.710> want<01:02:27.859> to<01:02:27.920> write<01:02:28.130> to<01:02:28.310> the<01:02:28.400> bare<01:02:28.550> metal 01:02:28.750 --> 01:02:28.760 align:start position:0% to want to write to the bare metal 01:02:28.760 --> 01:02:30.609 align:start position:0% to want to write to the bare metal there's<01:02:29.660> a<01:02:29.720> lot<01:02:29.930> of<01:02:30.109> scenarios<01:02:30.290> where<01:02:30.500> you 01:02:30.609 --> 01:02:30.619 align:start position:0% there's a lot of scenarios where you 01:02:30.619 --> 01:02:33.250 align:start position:0% there's a lot of scenarios where you don't<01:02:30.859> want<01:02:31.010> to<01:02:31.099> do<01:02:31.220> that<01:02:31.369> or<01:02:32.150> it's<01:02:32.630> not<01:02:32.810> the 01:02:33.250 --> 01:02:33.260 align:start position:0% don't want to do that or it's not the 01:02:33.260 --> 01:02:34.660 align:start position:0% don't want to do that or it's not the most<01:02:33.410> cost-effective<01:02:33.920> thing<01:02:34.220> for<01:02:34.369> you<01:02:34.460> to<01:02:34.520> do 01:02:34.660 --> 01:02:34.670 align:start position:0% most cost-effective thing for you to do 01:02:34.670 --> 01:02:37.650 align:start position:0% most cost-effective thing for you to do so<01:02:35.240> these<01:02:35.359> abstractions<01:02:35.750> are<01:02:36.650> very<01:02:36.890> important 01:02:37.650 --> 01:02:37.660 align:start position:0% so these abstractions are very important 01:02:37.660 --> 01:02:41.020 align:start position:0% so these abstractions are very important we<01:02:38.660> talk<01:02:38.780> about<01:02:38.869> SGX<01:02:39.349> and<01:02:39.530> VSM<01:02:40.040> and<01:02:40.310> and<01:02:40.460> others 01:02:41.020 --> 01:02:41.030 align:start position:0% we talk about SGX and VSM and and others 01:02:41.030 --> 01:02:43.960 align:start position:0% we talk about SGX and VSM and and others will<01:02:41.210> come<01:02:41.390> across<01:02:42.580> so<01:02:43.580> that's<01:02:43.700> better<01:02:43.820> next 01:02:43.960 --> 01:02:43.970 align:start position:0% will come across so that's better next 01:02:43.970 --> 01:02:50.980 align:start position:0% will come across so that's better next slide<01:02:45.580> please<01:02:46.580> thank<01:02:47.390> you<01:02:48.160> two<01:02:49.160> basic<01:02:49.990> things 01:02:50.980 --> 01:02:50.990 align:start position:0% slide please thank you two basic things 01:02:50.990 --> 01:02:52.030 align:start position:0% slide please thank you two basic things that<01:02:51.140> we're<01:02:51.349> trying<01:02:51.619> to<01:02:51.680> do<01:02:51.770> these<01:02:51.859> are 01:02:52.030 --> 01:02:52.040 align:start position:0% that we're trying to do these are 01:02:52.040 --> 01:02:53.859 align:start position:0% that we're trying to do these are examples<01:02:52.520> of<01:02:52.580> frameworks<01:02:53.060> that<01:02:53.300> were<01:02:53.510> working 01:02:53.859 --> 01:02:53.869 align:start position:0% examples of frameworks that were working 01:02:53.869 --> 01:02:57.609 align:start position:0% examples of frameworks that were working on<01:02:54.020> to<01:02:54.859> try<01:02:54.890> to<01:02:55.359> to<01:02:56.359> allow<01:02:56.570> customers<01:02:57.050> to<01:02:57.440> build 01:02:57.609 --> 01:02:57.619 align:start position:0% on to try to to allow customers to build 01:02:57.619 --> 01:02:59.920 align:start position:0% on to try to to allow customers to build killer<01:02:58.520> applications<01:02:59.240> we<01:02:59.510> think<01:02:59.750> that's 01:02:59.920 --> 01:02:59.930 align:start position:0% killer applications we think that's 01:02:59.930 --> 01:03:02.380 align:start position:0% killer applications we think that's gonna<01:03:00.109> be<01:03:00.260> what's<01:03:00.470> really<01:03:00.859> drives<01:03:01.390> blockchain 01:03:02.380 --> 01:03:02.390 align:start position:0% gonna be what's really drives blockchain 01:03:02.390 --> 01:03:05.079 align:start position:0% gonna be what's really drives blockchain networks<01:03:02.750> we've<01:03:03.740> worked<01:03:04.130> a<01:03:04.160> lot<01:03:04.280> with<01:03:04.400> tons 01:03:05.079 --> 01:03:05.089 align:start position:0% networks we've worked a lot with tons 01:03:05.089 --> 01:03:07.030 align:start position:0% networks we've worked a lot with tons and<01:03:05.330> tons<01:03:05.359> of<01:03:05.660> customers<01:03:06.080> to<01:03:06.800> try<01:03:06.980> to 01:03:07.030 --> 01:03:07.040 align:start position:0% and tons of customers to try to 01:03:07.040 --> 01:03:10.150 align:start position:0% and tons of customers to try to establish<01:03:07.220> networks<01:03:07.970> and<01:03:08.470> to<01:03:09.470> roll<01:03:09.980> these 01:03:10.150 --> 01:03:10.160 align:start position:0% establish networks and to roll these 01:03:10.160 --> 01:03:13.540 align:start position:0% establish networks and to roll these consortiums<01:03:10.849> out<01:03:11.359> and<01:03:11.630> for<01:03:12.200> the<01:03:12.260> EEA<01:03:12.560> it's 01:03:13.540 --> 01:03:13.550 align:start position:0% consortiums out and for the EEA it's 01:03:13.550 --> 01:03:16.930 align:start position:0% consortiums out and for the EEA it's very<01:03:13.820> difficult<01:03:14.359> to<01:03:14.839> justify<01:03:15.790> rolling<01:03:16.790> out 01:03:16.930 --> 01:03:16.940 align:start position:0% very difficult to justify rolling out 01:03:16.940 --> 01:03:18.790 align:start position:0% very difficult to justify rolling out this<01:03:17.150> infrastructure<01:03:17.660> and<01:03:17.839> contributing<01:03:18.770> a 01:03:18.790 --> 01:03:18.800 align:start position:0% this infrastructure and contributing a 01:03:18.800 --> 01:03:21.849 align:start position:0% this infrastructure and contributing a lot<01:03:18.920> of<01:03:19.040> the<01:03:19.190> the<01:03:19.400> resources<01:03:19.940> needed<01:03:20.240> to<01:03:20.859> work 01:03:21.849 --> 01:03:21.859 align:start position:0% lot of the the resources needed to work 01:03:21.859 --> 01:03:24.970 align:start position:0% lot of the the resources needed to work with<01:03:22.040> your<01:03:22.220> fiercest<01:03:22.790> competitors<01:03:23.980> doing 01:03:24.970 --> 01:03:24.980 align:start position:0% with your fiercest competitors doing 01:03:24.980 --> 01:03:27.079 align:start position:0% with your fiercest competitors doing that's<01:03:25.250> that<01:03:25.430> time<01:03:25.670> and<01:03:25.970> money<01:03:26.089> to<01:03:26.390> build<01:03:26.780> on 01:03:27.079 --> 01:03:27.089 align:start position:0% that's that time and money to build on 01:03:27.089 --> 01:03:29.690 align:start position:0% that's that time and money to build on work<01:03:27.269> that<01:03:28.109> will<01:03:28.259> smooth<01:03:28.680> operations<01:03:29.400> across 01:03:29.690 --> 01:03:29.700 align:start position:0% work that will smooth operations across 01:03:29.700 --> 01:03:33.229 align:start position:0% work that will smooth operations across that<01:03:29.969> ecosystem<01:03:30.690> it<01:03:30.839> sounds<01:03:31.200> very<01:03:31.380> noble<01:03:32.239> but 01:03:33.229 --> 01:03:33.239 align:start position:0% that ecosystem it sounds very noble but 01:03:33.239 --> 01:03:35.329 align:start position:0% that ecosystem it sounds very noble but at<01:03:33.329> the<01:03:33.390> end<01:03:33.509> of<01:03:33.599> the<01:03:33.660> day<01:03:33.979> people<01:03:34.979> are<01:03:35.130> writing 01:03:35.329 --> 01:03:35.339 align:start position:0% at the end of the day people are writing 01:03:35.339 --> 01:03:37.729 align:start position:0% at the end of the day people are writing those<01:03:35.460> checks<01:03:35.549> don't<01:03:36.390> really<01:03:36.749> you<01:03:37.140> know<01:03:37.229> the 01:03:37.729 --> 01:03:37.739 align:start position:0% those checks don't really you know the 01:03:37.739 --> 01:03:39.349 align:start position:0% those checks don't really you know the friction<01:03:38.160> in<01:03:38.279> the<01:03:38.369> marketplace<01:03:38.880> as<01:03:39.059> long<01:03:39.210> as 01:03:39.349 --> 01:03:39.359 align:start position:0% friction in the marketplace as long as 01:03:39.359 --> 01:03:43.430 align:start position:0% friction in the marketplace as long as they're<01:03:39.509> spreaded<01:03:39.900> they're<01:03:40.170> good<01:03:41.239> so<01:03:42.440> what's 01:03:43.430 --> 01:03:43.440 align:start position:0% they're spreaded they're good so what's 01:03:43.440 --> 01:03:45.459 align:start position:0% they're spreaded they're good so what's gonna<01:03:43.589> actually<01:03:43.799> be<01:03:44.130> the<01:03:44.160> tipping<01:03:44.579> point<01:03:44.849> are 01:03:45.459 --> 01:03:45.469 align:start position:0% gonna actually be the tipping point are 01:03:45.469 --> 01:03:48.620 align:start position:0% gonna actually be the tipping point are killer<01:03:46.469> applications<01:03:47.219> that<01:03:47.999> are<01:03:48.180> consumer 01:03:48.620 --> 01:03:48.630 align:start position:0% killer applications that are consumer 01:03:48.630 --> 01:03:51.410 align:start position:0% killer applications that are consumer facing<01:03:48.920> enterprise<01:03:49.920> facing<01:03:50.430> industry<01:03:50.999> facing 01:03:51.410 --> 01:03:51.420 align:start position:0% facing enterprise facing industry facing 01:03:51.420 --> 01:03:54.049 align:start position:0% facing enterprise facing industry facing crossing<01:03:51.989> industries<01:03:52.609> so<01:03:53.609> what<01:03:53.789> we<01:03:53.880> need<01:03:54.029> to 01:03:54.049 --> 01:03:54.059 align:start position:0% crossing industries so what we need to 01:03:54.059 --> 01:03:54.920 align:start position:0% crossing industries so what we need to do<01:03:54.180> is<01:03:54.269> be<01:03:54.359> able<01:03:54.509> to<01:03:54.569> address<01:03:54.779> some 01:03:54.920 --> 01:03:54.930 align:start position:0% do is be able to address some 01:03:54.930 --> 01:03:56.930 align:start position:0% do is be able to address some fundamental<01:03:55.739> problems<01:03:56.099> in<01:03:56.190> architecture<01:03:56.849> and 01:03:56.930 --> 01:03:56.940 align:start position:0% fundamental problems in architecture and 01:03:56.940 --> 01:04:00.950 align:start position:0% fundamental problems in architecture and infrastructure<01:03:57.450> to<01:03:58.430> start<01:03:59.450> having<01:04:00.450> tools<01:04:00.690> and 01:04:00.950 --> 01:04:00.960 align:start position:0% infrastructure to start having tools and 01:04:00.960 --> 01:04:03.019 align:start position:0% infrastructure to start having tools and platforms<01:04:01.019> available<01:04:01.559> so<01:04:02.430> you<01:04:02.489> can<01:04:02.670> start<01:04:02.910> to 01:04:03.019 --> 01:04:03.029 align:start position:0% platforms available so you can start to 01:04:03.029 --> 01:04:04.969 align:start position:0% platforms available so you can start to build<01:04:03.180> those<01:04:03.269> killer<01:04:03.539> applications<01:04:04.140> one<01:04:04.890> of 01:04:04.969 --> 01:04:04.979 align:start position:0% build those killer applications one of 01:04:04.979 --> 01:04:07.789 align:start position:0% build those killer applications one of them<01:04:05.099> release<01:04:05.789> was<01:04:06.029> called<01:04:06.329> as<01:04:07.140> we<01:04:07.559> call<01:04:07.710> the 01:04:07.789 --> 01:04:07.799 align:start position:0% them release was called as we call the 01:04:07.799 --> 01:04:09.380 align:start position:0% them release was called as we call the confidential<01:04:08.279> compute<01:04:08.789> blockchain 01:04:09.380 --> 01:04:09.390 align:start position:0% confidential compute blockchain 01:04:09.390 --> 01:04:11.660 align:start position:0% confidential compute blockchain framework<01:04:09.869> this<01:04:10.739> is<01:04:10.890> essentially<01:04:11.369> a<01:04:11.400> node 01:04:11.660 --> 01:04:11.670 align:start position:0% framework this is essentially a node 01:04:11.670 --> 01:04:15.319 align:start position:0% framework this is essentially a node level<01:04:11.989> data<01:04:12.989> to<01:04:13.170> your<01:04:13.289> optimization<01:04:14.180> it<01:04:15.180> is 01:04:15.319 --> 01:04:15.329 align:start position:0% level data to your optimization it is 01:04:15.329 --> 01:04:17.959 align:start position:0% level data to your optimization it is not<01:04:15.539> a<01:04:15.569> blockchain<01:04:15.839> it<01:04:16.829> is<01:04:17.009> essentially<01:04:17.549> an 01:04:17.959 --> 01:04:17.969 align:start position:0% not a blockchain it is essentially an 01:04:17.969 --> 01:04:19.640 align:start position:0% not a blockchain it is essentially an open<01:04:18.239> source<01:04:18.630> project<01:04:18.869> we'll<01:04:19.289> be<01:04:19.319> releasing 01:04:19.640 --> 01:04:19.650 align:start position:0% open source project we'll be releasing 01:04:19.650 --> 01:04:22.279 align:start position:0% open source project we'll be releasing soon<01:04:20.309> I<01:04:20.700> can't<01:04:21.509> give<01:04:21.660> you<01:04:21.779> exact<01:04:22.049> date<01:04:22.259> but 01:04:22.279 --> 01:04:22.289 align:start position:0% soon I can't give you exact date but 01:04:22.289 --> 01:04:26.660 align:start position:0% soon I can't give you exact date but mark<01:04:23.099> shaking<01:04:23.489> his<01:04:23.579> head<01:04:23.759> the<01:04:23.910> back<01:04:25.279> that<01:04:26.279> will 01:04:26.660 --> 01:04:26.670 align:start position:0% mark shaking his head the back that will 01:04:26.670 --> 01:04:28.430 align:start position:0% mark shaking his head the back that will be<01:04:26.789> raised<01:04:26.999> soon<01:04:27.359> that<01:04:27.539> essentially<01:04:28.109> provides 01:04:28.430 --> 01:04:28.440 align:start position:0% be raised soon that essentially provides 01:04:28.440 --> 01:04:33.259 align:start position:0% be raised soon that essentially provides a<01:04:28.799> framework<01:04:29.460> to<01:04:29.700> use<01:04:30.140> in<01:04:31.140> this<01:04:31.319> case<01:04:31.499> SGX<01:04:32.269> to 01:04:33.259 --> 01:04:33.269 align:start position:0% a framework to use in this case SGX to 01:04:33.269 --> 01:04:35.359 align:start position:0% a framework to use in this case SGX to create<01:04:33.509> a<01:04:33.539> confidential<01:04:34.140> compute<01:04:34.529> consortium 01:04:35.359 --> 01:04:35.369 align:start position:0% create a confidential compute consortium 01:04:35.369 --> 01:04:37.670 align:start position:0% create a confidential compute consortium write<01:04:35.969> us<01:04:36.089> down<01:04:36.119> for<01:04:36.390> public<01:04:36.809> this<01:04:37.410> is<01:04:37.650> a 01:04:37.670 --> 01:04:37.680 align:start position:0% write us down for public this is a 01:04:37.680 --> 01:04:40.009 align:start position:0% write us down for public this is a private<01:04:38.069> consortium<01:04:38.400> network<01:04:38.940> that<01:04:39.809> will 01:04:40.009 --> 01:04:40.019 align:start position:0% private consortium network that will 01:04:40.019 --> 01:04:41.779 align:start position:0% private consortium network that will give<01:04:40.259> you<01:04:40.349> a<01:04:40.410> governance<01:04:40.829> framework<01:04:41.249> so<01:04:41.609> it 01:04:41.779 --> 01:04:41.789 align:start position:0% give you a governance framework so it 01:04:41.789 --> 01:04:44.410 align:start position:0% give you a governance framework so it controls<01:04:42.239> who<01:04:42.599> you<01:04:42.989> let<01:04:43.200> into<01:04:43.410> your<01:04:43.589> network 01:04:44.410 --> 01:04:44.420 align:start position:0% controls who you let into your network 01:04:44.420 --> 01:04:47.209 align:start position:0% controls who you let into your network privacy<01:04:45.420> so<01:04:45.960> you<01:04:45.989> can<01:04:46.170> have<01:04:46.529> essential 01:04:47.209 --> 01:04:47.219 align:start position:0% privacy so you can have essential 01:04:47.219 --> 01:04:49.309 align:start position:0% privacy so you can have essential privacy<01:04:47.700> and<01:04:47.910> then<01:04:48.329> performance<01:04:48.930> because<01:04:49.200> we 01:04:49.309 --> 01:04:49.319 align:start position:0% privacy and then performance because we 01:04:49.319 --> 01:04:51.609 align:start position:0% privacy and then performance because we introduce<01:04:49.619> trusted<01:04:50.069> compute<01:04:50.460> we<01:04:50.999> can<01:04:51.150> use 01:04:51.609 --> 01:04:51.619 align:start position:0% introduce trusted compute we can use 01:04:51.619 --> 01:04:54.469 align:start position:0% introduce trusted compute we can use faster<01:04:52.619> consistence<01:04:53.279> algorithms<01:04:53.729> so<01:04:54.150> it's<01:04:54.329> a 01:04:54.469 --> 01:04:54.479 align:start position:0% faster consistence algorithms so it's a 01:04:54.479 --> 01:04:57.049 align:start position:0% faster consistence algorithms so it's a framework<01:04:55.349> it's<01:04:55.739> available<01:04:56.460> and<01:04:56.849> then<01:04:56.940> you 01:04:57.049 --> 01:04:57.059 align:start position:0% framework it's available and then you 01:04:57.059 --> 01:04:59.269 align:start position:0% framework it's available and then you could<01:04:57.239> take<01:04:57.450> that<01:04:57.779> framework<01:04:58.619> and<01:04:58.829> build<01:04:59.130> on 01:04:59.269 --> 01:04:59.279 align:start position:0% could take that framework and build on 01:04:59.279 --> 01:05:03.069 align:start position:0% could take that framework and build on top<01:04:59.549> of<01:04:59.700> it<01:04:59.849> to<01:04:59.940> create<01:05:00.329> high<01:05:01.319> performance 01:05:03.069 --> 01:05:03.079 align:start position:0% top of it to create high performance 01:05:03.079 --> 01:05:06.890 align:start position:0% top of it to create high performance consortium<01:05:04.079> block<01:05:04.319> chains<01:05:04.589> on<01:05:05.599> this<01:05:06.599> platform 01:05:06.890 --> 01:05:06.900 align:start position:0% consortium block chains on this platform 01:05:06.900 --> 01:05:08.420 align:start position:0% consortium block chains on this platform to<01:05:07.200> really<01:05:07.559> deliver<01:05:07.710> on<01:05:07.979> some<01:05:08.009> of<01:05:08.309> the 01:05:08.420 --> 01:05:08.430 align:start position:0% to really deliver on some of the 01:05:08.430 --> 01:05:10.370 align:start position:0% to really deliver on some of the enterprise<01:05:09.119> promises<01:05:09.660> that<01:05:09.839> we<01:05:09.960> at<01:05:10.079> the<01:05:10.200> EA 01:05:10.370 --> 01:05:10.380 align:start position:0% enterprise promises that we at the EA 01:05:10.380 --> 01:05:14.719 align:start position:0% enterprise promises that we at the EA are<01:05:11.219> striving<01:05:11.549> to<01:05:11.759> make<01:05:12.210> possible<01:05:13.579> above<01:05:14.579> that 01:05:14.719 --> 01:05:14.729 align:start position:0% are striving to make possible above that 01:05:14.729 --> 01:05:16.729 align:start position:0% are striving to make possible above that is<01:05:14.999> another<01:05:15.690> thing<01:05:15.900> in<01:05:16.019> the<01:05:16.109> middle<01:05:16.289> tier<01:05:16.440> so 01:05:16.729 --> 01:05:16.739 align:start position:0% is another thing in the middle tier so 01:05:16.739 --> 01:05:19.640 align:start position:0% is another thing in the middle tier so sort<01:05:17.039> of<01:05:17.069> how<01:05:17.219> do<01:05:17.279> I<01:05:17.430> build<01:05:17.579> applications<01:05:18.650> and 01:05:19.640 --> 01:05:19.650 align:start position:0% sort of how do I build applications and 01:05:19.650 --> 01:05:21.259 align:start position:0% sort of how do I build applications and wrap<01:05:19.920> and<01:05:20.249> give<01:05:20.430> me<01:05:20.519> that<01:05:20.640> infrastructure<01:05:21.119> to 01:05:21.259 --> 01:05:21.269 align:start position:0% wrap and give me that infrastructure to 01:05:21.269 --> 01:05:23.450 align:start position:0% wrap and give me that infrastructure to where<01:05:21.359> I<01:05:21.420> can<01:05:21.599> execute<01:05:22.140> code<01:05:22.710> and<01:05:23.009> logic<01:05:23.130> off 01:05:23.450 --> 01:05:23.460 align:start position:0% where I can execute code and logic off 01:05:23.460 --> 01:05:27.499 align:start position:0% where I can execute code and logic off chain<01:05:24.319> and<01:05:25.319> then<01:05:25.469> persist<01:05:26.279> that<01:05:26.519> on<01:05:26.940> chain<01:05:27.359> so 01:05:27.499 --> 01:05:27.509 align:start position:0% chain and then persist that on chain so 01:05:27.509 --> 01:05:31.069 align:start position:0% chain and then persist that on chain so I<01:05:27.539> usually<01:05:27.839> tell<01:05:28.109> people<01:05:28.289> the<01:05:29.329> I<01:05:30.329> have<01:05:30.989> to 01:05:31.069 --> 01:05:31.079 align:start position:0% I usually tell people the I have to 01:05:31.079 --> 01:05:33.650 align:start position:0% I usually tell people the I have to explain<01:05:31.319> this<01:05:31.499> a<01:05:31.559> lot<01:05:31.799> and<01:05:32.640> I<01:05:33.029> talk<01:05:33.269> about<01:05:33.299> the 01:05:33.650 --> 01:05:33.660 align:start position:0% explain this a lot and I talk about the 01:05:33.660 --> 01:05:36.459 align:start position:0% explain this a lot and I talk about the bottom<01:05:34.109> being<01:05:34.349> the<01:05:34.589> distributed<01:05:35.130> truth<01:05:35.430> so 01:05:36.459 --> 01:05:36.469 align:start position:0% bottom being the distributed truth so 01:05:36.469 --> 01:05:38.749 align:start position:0% bottom being the distributed truth so most<01:05:37.469> of<01:05:37.619> you<01:05:37.710> will<01:05:37.890> get<01:05:38.009> this<01:05:38.219> because<01:05:38.579> it's 01:05:38.749 --> 01:05:38.759 align:start position:0% most of you will get this because it's 01:05:38.759 --> 01:05:40.339 align:start position:0% most of you will get this because it's the<01:05:38.849> audience<01:05:39.269> and<01:05:39.479> the<01:05:39.539> demographic<01:05:40.109> I<01:05:40.200> have 01:05:40.339 --> 01:05:40.349 align:start position:0% the audience and the demographic I have 01:05:40.349 --> 01:05:40.790 align:start position:0% the audience and the demographic I have in<01:05:40.469> the<01:05:40.559> room 01:05:40.790 --> 01:05:40.800 align:start position:0% in the room 01:05:40.800 --> 01:05:42.920 align:start position:0% in the room so<01:05:41.370> if<01:05:41.730> I<01:05:41.850> go<01:05:41.970> and<01:05:42.120> look<01:05:42.240> at<01:05:42.330> the<01:05:42.390> blonde<01:05:42.570> I'll 01:05:42.920 --> 01:05:42.930 align:start position:0% so if I go and look at the blonde I'll 01:05:42.930 --> 01:05:44.690 align:start position:0% so if I go and look at the blonde I'll look<01:05:43.110> and<01:05:43.530> I<01:05:43.740> see<01:05:43.950> the<01:05:44.100> answer<01:05:44.460> for<01:05:44.610> my 01:05:44.690 --> 01:05:44.700 align:start position:0% look and I see the answer for my 01:05:44.700 --> 01:05:48.130 align:start position:0% look and I see the answer for my question<01:05:44.730> that's<01:05:45.240> 42<01:05:45.570> and<01:05:46.080> the<01:05:47.040> question<01:05:47.610> is 01:05:48.130 --> 01:05:48.140 align:start position:0% question that's 42 and the question is 01:05:48.140 --> 01:05:52.090 align:start position:0% question that's 42 and the question is what's<01:05:49.140> the<01:05:49.260> meaning<01:05:49.470> life<01:05:49.680> and<01:05:49.830> everything 01:05:52.090 --> 01:05:52.100 align:start position:0% what's the meaning life and everything 01:05:52.100 --> 01:05:55.160 align:start position:0% what's the meaning life and everything so<01:05:53.100> if<01:05:53.670> you<01:05:53.820> haven't<01:05:54.090> read<01:05:54.300> Douglas<01:05:54.840> Adams 01:05:55.160 --> 01:05:55.170 align:start position:0% so if you haven't read Douglas Adams 01:05:55.170 --> 01:05:56.360 align:start position:0% so if you haven't read Douglas Adams Hitchhiker's<01:05:55.290> Guide<01:05:55.680> to<01:05:55.800> the<01:05:55.920> galaxy<01:05:56.340> I 01:05:56.360 --> 01:05:56.370 align:start position:0% Hitchhiker's Guide to the galaxy I 01:05:56.370 --> 01:05:58.970 align:start position:0% Hitchhiker's Guide to the galaxy I encourage<01:05:57.030> you<01:05:57.210> to<01:05:57.390> do<01:05:57.540> so<01:05:57.750> but<01:05:58.560> this<01:05:58.680> is<01:05:58.830> one 01:05:58.970 --> 01:05:58.980 align:start position:0% encourage you to do so but this is one 01:05:58.980 --> 01:06:00.620 align:start position:0% encourage you to do so but this is one of<01:05:59.010> the<01:05:59.130> big<01:05:59.310> themes<01:05:59.850> that<01:06:00.120> runs<01:06:00.360> throughout 01:06:00.620 --> 01:06:00.630 align:start position:0% of the big themes that runs throughout 01:06:00.630 --> 01:06:02.690 align:start position:0% of the big themes that runs throughout as<01:06:01.020> you<01:06:01.200> go<01:06:01.380> and<01:06:01.650> you<01:06:01.770> speak<01:06:02.010> this<01:06:02.190> answer 01:06:02.690 --> 01:06:02.700 align:start position:0% as you go and you speak this answer 01:06:02.700 --> 01:06:05.180 align:start position:0% as you go and you speak this answer you're<01:06:03.420> looking<01:06:03.450> to<01:06:04.170> get<01:06:04.380> find<01:06:04.620> the<01:06:04.710> answer<01:06:04.980> to 01:06:05.180 --> 01:06:05.190 align:start position:0% you're looking to get find the answer to 01:06:05.190 --> 01:06:07.640 align:start position:0% you're looking to get find the answer to what<01:06:05.520> is<01:06:05.550> the<01:06:05.760> meaning<01:06:06.390> of<01:06:06.540> life<01:06:06.720> the<01:06:07.500> universe 01:06:07.640 --> 01:06:07.650 align:start position:0% what is the meaning of life the universe 01:06:07.650 --> 01:06:09.920 align:start position:0% what is the meaning of life the universe and<01:06:07.980> everything<01:06:08.070> and<01:06:08.580> you<01:06:09.330> finally<01:06:09.570> own<01:06:09.810> the 01:06:09.920 --> 01:06:09.930 align:start position:0% and everything and you finally own the 01:06:09.930 --> 01:06:12.560 align:start position:0% and everything and you finally own the answer<01:06:10.200> is<01:06:10.290> 42<01:06:10.940> how<01:06:11.940> many<01:06:12.120> of<01:06:12.210> you<01:06:12.330> are<01:06:12.450> gonna 01:06:12.560 --> 01:06:12.570 align:start position:0% answer is 42 how many of you are gonna 01:06:12.570 --> 01:06:14.690 align:start position:0% answer is 42 how many of you are gonna be<01:06:12.660> satisfied<01:06:13.320> with<01:06:13.650> that<01:06:13.950> answer<01:06:14.220> and<01:06:14.610> the 01:06:14.690 --> 01:06:14.700 align:start position:0% be satisfied with that answer and the 01:06:14.700 --> 01:06:16.280 align:start position:0% be satisfied with that answer and the answer<01:06:14.730> is<01:06:15.060> no<01:06:15.420> one<01:06:15.660> is<01:06:15.780> gonna<01:06:15.960> be<01:06:16.080> satisfied 01:06:16.280 --> 01:06:16.290 align:start position:0% answer is no one is gonna be satisfied 01:06:16.290 --> 01:06:17.420 align:start position:0% answer is no one is gonna be satisfied with<01:06:16.680> the<01:06:16.740> answer<01:06:16.950> even<01:06:17.130> though<01:06:17.220> you<01:06:17.280> know 01:06:17.420 --> 01:06:17.430 align:start position:0% with the answer even though you know 01:06:17.430 --> 01:06:19.040 align:start position:0% with the answer even though you know it's<01:06:17.580> the<01:06:17.670> truth<01:06:17.880> that's<01:06:18.570> on<01:06:18.690> the<01:06:18.840> blockchain 01:06:19.040 --> 01:06:19.050 align:start position:0% it's the truth that's on the blockchain 01:06:19.050 --> 01:06:21.970 align:start position:0% it's the truth that's on the blockchain so<01:06:19.740> what<01:06:19.980> do<01:06:20.040> we<01:06:20.100> have<01:06:20.190> to<01:06:20.520> do<01:06:20.670> to<01:06:21.480> be<01:06:21.600> able<01:06:21.720> to 01:06:21.970 --> 01:06:21.980 align:start position:0% so what do we have to do to be able to 01:06:21.980 --> 01:06:25.010 align:start position:0% so what do we have to do to be able to you<01:06:22.980> know<01:06:23.010> accept<01:06:23.550> that<01:06:23.670> as<01:06:23.850> the<01:06:23.880> answer<01:06:24.060> well 01:06:25.010 --> 01:06:25.020 align:start position:0% you know accept that as the answer well 01:06:25.020 --> 01:06:26.600 align:start position:0% you know accept that as the answer well you're<01:06:25.230> gonna<01:06:25.350> go<01:06:25.500> off<01:06:25.620> on<01:06:25.650> a<01:06:25.860> wild<01:06:25.980> track 01:06:26.600 --> 01:06:26.610 align:start position:0% you're gonna go off on a wild track 01:06:26.610 --> 01:06:29.600 align:start position:0% you're gonna go off on a wild track across<01:06:27.030> the<01:06:27.150> galaxy<01:06:27.720> to<01:06:28.040> you<01:06:29.040> know<01:06:29.160> compute 01:06:29.600 --> 01:06:29.610 align:start position:0% across the galaxy to you know compute 01:06:29.610 --> 01:06:30.770 align:start position:0% across the galaxy to you know compute all<01:06:29.700> these<01:06:29.880> things<01:06:30.090> you'll<01:06:30.240> come<01:06:30.420> back<01:06:30.540> and 01:06:30.770 --> 01:06:30.780 align:start position:0% all these things you'll come back and 01:06:30.780 --> 01:06:32.900 align:start position:0% all these things you'll come back and sure<01:06:30.990> enough<01:06:31.020> the<01:06:31.290> answer<01:06:31.470> is<01:06:31.590> 42<01:06:31.860> the<01:06:32.700> next 01:06:32.900 --> 01:06:32.910 align:start position:0% sure enough the answer is 42 the next 01:06:32.910 --> 01:06:34.940 align:start position:0% sure enough the answer is 42 the next person<01:06:33.180> comes<01:06:33.360> up<01:06:33.540> and<01:06:33.720> they<01:06:33.810> go<01:06:33.960> well<01:06:34.380> what's 01:06:34.940 --> 01:06:34.950 align:start position:0% person comes up and they go well what's 01:06:34.950 --> 01:06:36.980 align:start position:0% person comes up and they go well what's the<01:06:35.040> answer<01:06:35.190> they<01:06:35.400> see<01:06:35.460> 42<01:06:35.910> they're<01:06:36.690> not<01:06:36.840> gonna 01:06:36.980 --> 01:06:36.990 align:start position:0% the answer they see 42 they're not gonna 01:06:36.990 --> 01:06:38.060 align:start position:0% the answer they see 42 they're not gonna believe<01:06:37.230> it<01:06:37.290> they're<01:06:37.530> gonna<01:06:37.620> go<01:06:37.770> do<01:06:37.920> the<01:06:38.040> same 01:06:38.060 --> 01:06:38.070 align:start position:0% believe it they're gonna go do the same 01:06:38.070 --> 01:06:40.100 align:start position:0% believe it they're gonna go do the same thing<01:06:38.610> again<01:06:38.910> that's<01:06:39.570> what<01:06:39.720> watching 01:06:40.100 --> 01:06:40.110 align:start position:0% thing again that's what watching 01:06:40.110 --> 01:06:42.740 align:start position:0% thing again that's what watching networks<01:06:40.470> do<01:06:40.790> right<01:06:41.790> we<01:06:41.970> just<01:06:42.270> compute<01:06:42.660> the 01:06:42.740 --> 01:06:42.750 align:start position:0% networks do right we just compute the 01:06:42.750 --> 01:06:44.660 align:start position:0% networks do right we just compute the same<01:06:42.990> thing<01:06:43.350> over<01:06:43.710> and<01:06:43.770> over<01:06:43.830> again<01:06:44.040> to 01:06:44.660 --> 01:06:44.670 align:start position:0% same thing over and over again to 01:06:44.670 --> 01:06:47.210 align:start position:0% same thing over and over again to satisfy<01:06:45.210> that<01:06:45.390> yes<01:06:45.600> the<01:06:46.410> answer<01:06:46.560> is<01:06:46.650> 42<01:06:46.980> the 01:06:47.210 --> 01:06:47.220 align:start position:0% satisfy that yes the answer is 42 the 01:06:47.220 --> 01:06:48.590 align:start position:0% satisfy that yes the answer is 42 the next<01:06:47.400> one<01:06:47.520> comes<01:06:47.760> in<01:06:47.880> they<01:06:47.970> don't<01:06:48.150> trust<01:06:48.300> it<01:06:48.480> so 01:06:48.590 --> 01:06:48.600 align:start position:0% next one comes in they don't trust it so 01:06:48.600 --> 01:06:50.060 align:start position:0% next one comes in they don't trust it so they're<01:06:48.690> gonna<01:06:48.780> recompute<01:06:49.260> it<01:06:49.320> and<01:06:49.890> that 01:06:50.060 --> 01:06:50.070 align:start position:0% they're gonna recompute it and that 01:06:50.070 --> 01:06:53.150 align:start position:0% they're gonna recompute it and that works<01:06:50.280> great<01:06:50.400> but<01:06:51.360> it's<01:06:51.680> not<01:06:52.680> gonna<01:06:52.800> solve<01:06:53.010> all 01:06:53.150 --> 01:06:53.160 align:start position:0% works great but it's not gonna solve all 01:06:53.160 --> 01:06:54.470 align:start position:0% works great but it's not gonna solve all of<01:06:53.220> our<01:06:53.340> problems<01:06:53.430> we<01:06:53.910> need<01:06:54.060> to<01:06:54.120> be<01:06:54.270> able<01:06:54.360> to 01:06:54.470 --> 01:06:54.480 align:start position:0% of our problems we need to be able to 01:06:54.480 --> 01:06:56.990 align:start position:0% of our problems we need to be able to pull<01:06:54.870> things<01:06:55.050> off<01:06:55.380> or<01:06:56.190> particularly<01:06:56.820> the 01:06:56.990 --> 01:06:57.000 align:start position:0% pull things off or particularly the 01:06:57.000 --> 01:06:58.820 align:start position:0% pull things off or particularly the contract<01:06:57.570> if<01:06:57.690> you<01:06:57.780> think<01:06:57.900> of<01:06:57.960> what<01:06:58.050> a<01:06:58.110> contract 01:06:58.820 --> 01:06:58.830 align:start position:0% contract if you think of what a contract 01:06:58.830 --> 01:07:02.150 align:start position:0% contract if you think of what a contract is<01:06:59.070> it's<01:06:59.880> a<01:07:00.060> trust<01:07:00.560> agreement<01:07:01.560> between 01:07:02.150 --> 01:07:02.160 align:start position:0% is it's a trust agreement between 01:07:02.160 --> 01:07:04.910 align:start position:0% is it's a trust agreement between discreet<01:07:02.700> parties<01:07:03.320> the<01:07:04.320> only<01:07:04.590> people<01:07:04.740> that 01:07:04.910 --> 01:07:04.920 align:start position:0% discreet parties the only people that 01:07:04.920 --> 01:07:08.510 align:start position:0% discreet parties the only people that really<01:07:05.010> care<01:07:05.580> about<01:07:06.110> the<01:07:07.110> answer<01:07:07.740> being<01:07:07.920> 42 01:07:08.510 --> 01:07:08.520 align:start position:0% really care about the answer being 42 01:07:08.520 --> 01:07:11.210 align:start position:0% really care about the answer being 42 and<01:07:08.880> really<01:07:09.720> the<01:07:09.990> question<01:07:10.350> are<01:07:11.040> the 01:07:11.210 --> 01:07:11.220 align:start position:0% and really the question are the 01:07:11.220 --> 01:07:13.430 align:start position:0% and really the question are the counterparties<01:07:11.910> to<01:07:11.940> that<01:07:12.240> contract<01:07:12.690> so<01:07:13.320> if<01:07:13.380> I 01:07:13.430 --> 01:07:13.440 align:start position:0% counterparties to that contract so if I 01:07:13.440 --> 01:07:15.440 align:start position:0% counterparties to that contract so if I can<01:07:13.590> pull<01:07:13.740> that<01:07:13.770> off<01:07:14.070> and<01:07:14.640> write<01:07:15.030> that<01:07:15.240> then 01:07:15.440 --> 01:07:15.450 align:start position:0% can pull that off and write that then 01:07:15.450 --> 01:07:18.650 align:start position:0% can pull that off and write that then write<01:07:15.660> the<01:07:15.810> answer<01:07:16.050> 42<01:07:16.350> down<01:07:16.910> then<01:07:17.910> you<01:07:18.330> as 01:07:18.650 --> 01:07:18.660 align:start position:0% write the answer 42 down then you as 01:07:18.660 --> 01:07:20.690 align:start position:0% write the answer 42 down then you as someone<01:07:19.140> that's<01:07:19.350> on<01:07:19.500> this<01:07:19.890> blockchain<01:07:20.370> you 01:07:20.690 --> 01:07:20.700 align:start position:0% someone that's on this blockchain you 01:07:20.700 --> 01:07:22.040 align:start position:0% someone that's on this blockchain you didn't<01:07:20.940> necessarily<01:07:21.030> ask<01:07:21.450> the<01:07:21.660> question<01:07:22.020> you 01:07:22.040 --> 01:07:22.050 align:start position:0% didn't necessarily ask the question you 01:07:22.050 --> 01:07:24.980 align:start position:0% didn't necessarily ask the question you see<01:07:22.260> the<01:07:22.350> answer<01:07:22.560> is<01:07:22.650> 42<01:07:22.950> and<01:07:23.100> you're<01:07:23.340> like<01:07:23.990> I'm 01:07:24.980 --> 01:07:24.990 align:start position:0% see the answer is 42 and you're like I'm 01:07:24.990 --> 01:07:30.320 align:start position:0% see the answer is 42 and you're like I'm good<01:07:25.170> with<01:07:25.260> that<01:07:25.410> move<01:07:26.010> on<01:07:26.900> so<01:07:28.400> middle<01:07:29.400> tier<01:07:29.550> we 01:07:30.320 --> 01:07:30.330 align:start position:0% good with that move on so middle tier we 01:07:30.330 --> 01:07:32.390 align:start position:0% good with that move on so middle tier we think<01:07:30.510> solving<01:07:31.170> these<01:07:31.260> types<01:07:31.440> of<01:07:31.620> problems<01:07:31.680> we 01:07:32.390 --> 01:07:32.400 align:start position:0% think solving these types of problems we 01:07:32.400 --> 01:07:35.630 align:start position:0% think solving these types of problems we call<01:07:32.580> that<01:07:32.820> the<01:07:33.360> truth<01:07:34.200> resolution<01:07:34.890> tier<01:07:35.280> so 01:07:35.630 --> 01:07:35.640 align:start position:0% call that the truth resolution tier so 01:07:35.640 --> 01:07:39.080 align:start position:0% call that the truth resolution tier so and<01:07:36.480> have<01:07:36.690> an<01:07:36.810> option<01:07:37.110> to<01:07:37.200> pull<01:07:37.640> your<01:07:38.640> contract 01:07:39.080 --> 01:07:39.090 align:start position:0% and have an option to pull your contract 01:07:39.090 --> 01:07:41.090 align:start position:0% and have an option to pull your contract logic<01:07:39.480> and<01:07:39.660> all<01:07:39.720> sorts<01:07:40.020> of<01:07:40.080> Oracle's<01:07:40.590> and<01:07:40.920> and 01:07:41.090 --> 01:07:41.100 align:start position:0% logic and all sorts of Oracle's and and 01:07:41.100 --> 01:07:44.450 align:start position:0% logic and all sorts of Oracle's and and things<01:07:41.580> like<01:07:41.760> that<01:07:41.820> off<01:07:42.240> so<01:07:43.160> trusted<01:07:44.160> compute 01:07:44.450 --> 01:07:44.460 align:start position:0% things like that off so trusted compute 01:07:44.460 --> 01:07:47.480 align:start position:0% things like that off so trusted compute in<01:07:44.610> watching<01:07:45.390> involves<01:07:46.290> that<01:07:46.470> as<01:07:46.680> well<01:07:46.890> and<01:07:47.100> we 01:07:47.480 --> 01:07:47.490 align:start position:0% in watching involves that as well and we 01:07:47.490 --> 01:07:49.550 align:start position:0% in watching involves that as well and we address<01:07:47.790> that<01:07:47.940> in<01:07:48.120> the<01:07:48.240> tea<01:07:48.420> of<01:07:49.170> the<01:07:49.260> trusted 01:07:49.550 --> 01:07:49.560 align:start position:0% address that in the tea of the trusted 01:07:49.560 --> 01:07:52.640 align:start position:0% address that in the tea of the trusted computation<01:07:51.110> so<01:07:52.110> our<01:07:52.230> middle<01:07:52.410> tier<01:07:52.530> we're 01:07:52.640 --> 01:07:52.650 align:start position:0% computation so our middle tier we're 01:07:52.650 --> 01:07:54.560 align:start position:0% computation so our middle tier we're trying<01:07:52.860> to<01:07:52.920> make<01:07:53.010> it<01:07:53.100> easy<01:07:53.340> for<01:07:53.490> you<01:07:53.730> to 01:07:54.560 --> 01:07:54.570 align:start position:0% trying to make it easy for you to 01:07:54.570 --> 01:07:57.470 align:start position:0% trying to make it easy for you to use<01:07:54.930> enclaves<01:07:55.410> in<01:07:55.680> the<01:07:56.460> middle<01:07:56.670> tier<01:07:56.820> so<01:07:57.150> it's 01:07:57.470 --> 01:07:57.480 align:start position:0% use enclaves in the middle tier so it's 01:07:57.480 --> 01:07:58.940 align:start position:0% use enclaves in the middle tier so it's more<01:07:57.660> of<01:07:57.720> a<01:07:57.780> pooling<01:07:58.020> getting<01:07:58.680> scarce 01:07:58.940 --> 01:07:58.950 align:start position:0% more of a pooling getting scarce 01:07:58.950 --> 01:08:01.130 align:start position:0% more of a pooling getting scarce resources<01:07:59.400> just<01:07:59.700> in<01:07:59.850> time<01:08:00.060> to<01:08:00.660> do<01:08:00.810> certain 01:08:01.130 --> 01:08:01.140 align:start position:0% resources just in time to do certain 01:08:01.140 --> 01:08:06.190 align:start position:0% resources just in time to do certain things<01:08:01.170> that<01:08:01.680> you<01:08:02.460> want<01:08:02.610> done<01:08:02.820> in<01:08:02.850> private 01:08:06.190 --> 01:08:06.200 align:start position:0% 01:08:06.200 --> 01:08:09.370 align:start position:0% so<01:08:07.200> yesterday<01:08:07.560> I<01:08:07.830> published<01:08:08.460> a<01:08:08.580> blog 01:08:09.370 --> 01:08:09.380 align:start position:0% so yesterday I published a blog 01:08:09.380 --> 01:08:11.570 align:start position:0% so yesterday I published a blog announcing<01:08:10.380> the<01:08:10.470> release<01:08:10.590> of<01:08:10.950> the<01:08:11.100> enclave 01:08:11.570 --> 01:08:11.580 align:start position:0% announcing the release of the enclave 01:08:11.580 --> 01:08:16.579 align:start position:0% announcing the release of the enclave ready<01:08:12.140> EVM<01:08:13.140> which<01:08:13.650> is<01:08:13.920> a<01:08:14.420> open<01:08:15.420> source<01:08:15.630> C++ 01:08:16.579 --> 01:08:16.589 align:start position:0% ready EVM which is a open source C++ 01:08:16.589 --> 01:08:21.020 align:start position:0% ready EVM which is a open source C++ implementation<01:08:16.740> of<01:08:17.580> the<01:08:17.730> EVM<01:08:18.890> it<01:08:19.890> is<01:08:20.190> it<01:08:20.850> has 01:08:21.020 --> 01:08:21.030 align:start position:0% implementation of the EVM it is it has 01:08:21.030 --> 01:08:23.180 align:start position:0% implementation of the EVM it is it has no<01:08:21.240> dependencies<01:08:21.900> outside<01:08:22.440> of<01:08:22.710> so<01:08:22.920> you<01:08:22.980> don't 01:08:23.180 --> 01:08:23.190 align:start position:0% no dependencies outside of so you don't 01:08:23.190 --> 01:08:27.500 align:start position:0% no dependencies outside of so you don't need<01:08:23.310> to<01:08:23.430> even<01:08:23.609> use<01:08:23.850> the<01:08:24.000> Intel<01:08:24.480> SGX<01:08:25.339> SDK<01:08:26.510> it'll 01:08:27.500 --> 01:08:27.510 align:start position:0% need to even use the Intel SGX SDK it'll 01:08:27.510 --> 01:08:30.680 align:start position:0% need to even use the Intel SGX SDK it'll run<01:08:27.690> as<01:08:27.930> is<01:08:28.410> back<01:08:29.100> to<01:08:29.580> run<01:08:29.760> outside<01:08:30.210> of<01:08:30.330> Enclave 01:08:30.680 --> 01:08:30.690 align:start position:0% run as is back to run outside of Enclave 01:08:30.690 --> 01:08:34.400 align:start position:0% run as is back to run outside of Enclave as<01:08:30.839> well<01:08:32.180> some<01:08:33.180> things<01:08:33.359> about<01:08:33.510> it<01:08:33.780> it's<01:08:33.960> not 01:08:34.400 --> 01:08:34.410 align:start position:0% as well some things about it it's not 01:08:34.410 --> 01:08:36.860 align:start position:0% as well some things about it it's not fully<01:08:34.680> functional<01:08:35.160> doesn't<01:08:35.400> count<01:08:35.549> gas<01:08:35.870> right 01:08:36.860 --> 01:08:36.870 align:start position:0% fully functional doesn't count gas right 01:08:36.870 --> 01:08:39.650 align:start position:0% fully functional doesn't count gas right it<01:08:37.710> is<01:08:38.010> compatible<01:08:38.460> with<01:08:38.670> the<01:08:38.819> EVM<01:08:39.180> opcodes 01:08:39.650 --> 01:08:39.660 align:start position:0% it is compatible with the EVM opcodes 01:08:39.660 --> 01:08:43.250 align:start position:0% it is compatible with the EVM opcodes for<01:08:39.900> Homestead<01:08:41.150> let's<01:08:42.150> see<01:08:42.330> well<01:08:42.630> do<01:08:42.780> existing 01:08:43.250 --> 01:08:43.260 align:start position:0% for Homestead let's see well do existing 01:08:43.260 --> 01:08:45.800 align:start position:0% for Homestead let's see well do existing bytecode<01:08:43.620> things<01:08:43.859> like<01:08:44.010> this<01:08:44.660> but<01:08:45.660> there's 01:08:45.800 --> 01:08:45.810 align:start position:0% bytecode things like this but there's 01:08:45.810 --> 01:08:47.090 align:start position:0% bytecode things like this but there's some<01:08:45.930> interesting<01:08:46.080> things<01:08:46.350> about<01:08:46.859> this<01:08:47.040> and 01:08:47.090 --> 01:08:47.100 align:start position:0% some interesting things about this and 01:08:47.100 --> 01:08:49.190 align:start position:0% some interesting things about this and we<01:08:48.030> built<01:08:48.270> this<01:08:48.420> not<01:08:48.750> because<01:08:49.020> we're<01:08:49.170> trying 01:08:49.190 --> 01:08:49.200 align:start position:0% we built this not because we're trying 01:08:49.200 --> 01:08:50.570 align:start position:0% we built this not because we're trying to<01:08:49.500> compete<01:08:49.859> with<01:08:49.920> aetherium 01:08:50.570 --> 01:08:50.580 align:start position:0% to compete with aetherium 01:08:50.580 --> 01:08:53.030 align:start position:0% to compete with aetherium or<01:08:51.330> come<01:08:51.480> out<01:08:51.600> with<01:08:51.750> a<01:08:51.780> theory<01:08:52.650> on<01:08:52.740> virtual 01:08:53.030 --> 01:08:53.040 align:start position:0% or come out with a theory on virtual 01:08:53.040 --> 01:08:54.200 align:start position:0% or come out with a theory on virtual machine<01:08:53.250> that's<01:08:53.460> better<01:08:53.640> than<01:08:53.819> anyone<01:08:54.060> else 01:08:54.200 --> 01:08:54.210 align:start position:0% machine that's better than anyone else 01:08:54.210 --> 01:08:56.450 align:start position:0% machine that's better than anyone else we<01:08:54.299> had<01:08:54.540> to<01:08:54.690> build<01:08:54.870> this<01:08:55.020> for<01:08:55.890> the<01:08:56.040> confidence 01:08:56.450 --> 01:08:56.460 align:start position:0% we had to build this for the confidence 01:08:56.460 --> 01:08:58.130 align:start position:0% we had to build this for the confidence of<01:08:56.549> compute<01:08:56.880> blockchain<01:08:57.480> framework<01:08:57.900> we<01:08:58.020> had 01:08:58.130 --> 01:08:58.140 align:start position:0% of compute blockchain framework we had 01:08:58.140 --> 01:08:59.450 align:start position:0% of compute blockchain framework we had to<01:08:58.200> be<01:08:58.260> able<01:08:58.319> to<01:08:58.410> test<01:08:58.710> this<01:08:58.890> infrastructure 01:08:59.450 --> 01:08:59.460 align:start position:0% to be able to test this infrastructure 01:08:59.460 --> 01:09:01.640 align:start position:0% to be able to test this infrastructure so<01:09:00.270> we<01:09:00.359> had<01:09:00.480> to<01:09:00.569> have<01:09:00.690> smart<01:09:00.960> contracts<01:09:01.440> that 01:09:01.640 --> 01:09:01.650 align:start position:0% so we had to have smart contracts that 01:09:01.650 --> 01:09:03.980 align:start position:0% so we had to have smart contracts that would<01:09:01.770> execute<01:09:02.040> in<01:09:02.430> a<01:09:02.520> te<01:09:02.760> to<01:09:03.180> C<01:09:03.330> is<01:09:03.510> actually 01:09:03.980 --> 01:09:03.990 align:start position:0% would execute in a te to C is actually 01:09:03.990 --> 01:09:06.230 align:start position:0% would execute in a te to C is actually gonna<01:09:04.080> work<01:09:04.520> so<01:09:05.520> what<01:09:05.670> we<01:09:05.760> did<01:09:05.880> is<01:09:06.000> we<01:09:06.030> said 01:09:06.230 --> 01:09:06.240 align:start position:0% gonna work so what we did is we said 01:09:06.240 --> 01:09:08.900 align:start position:0% gonna work so what we did is we said okay<01:09:06.420> let's<01:09:06.450> just<01:09:06.839> release<01:09:07.560> that<01:09:07.859> work<01:09:08.130> out<01:09:08.400> we 01:09:08.900 --> 01:09:08.910 align:start position:0% okay let's just release that work out we 01:09:08.910 --> 01:09:10.970 align:start position:0% okay let's just release that work out we think<01:09:09.060> it's<01:09:09.240> gonna<01:09:09.330> be<01:09:09.540> valuable<01:09:09.960> and<01:09:10.350> let<01:09:10.920> me 01:09:10.970 --> 01:09:10.980 align:start position:0% think it's gonna be valuable and let me 01:09:10.980 --> 01:09:13.550 align:start position:0% think it's gonna be valuable and let me give<01:09:11.130> you<01:09:11.220> some<01:09:11.400> four<01:09:11.790> examples<01:09:12.080> this<01:09:13.080> type<01:09:13.410> of 01:09:13.550 --> 01:09:13.560 align:start position:0% give you some four examples this type of 01:09:13.560 --> 01:09:16.220 align:start position:0% give you some four examples this type of code<01:09:13.770> you<01:09:14.010> can<01:09:14.220> take<01:09:14.460> it<01:09:14.670> and<01:09:14.790> modify<01:09:15.569> it<01:09:15.839> and 01:09:16.220 --> 01:09:16.230 align:start position:0% code you can take it and modify it and 01:09:16.230 --> 01:09:18.590 align:start position:0% code you can take it and modify it and you<01:09:17.190> could<01:09:17.339> add<01:09:17.520> in<01:09:17.700> these<01:09:17.819> features<01:09:18.240> because 01:09:18.590 --> 01:09:18.600 align:start position:0% you could add in these features because 01:09:18.600 --> 01:09:20.870 align:start position:0% you could add in these features because it<01:09:18.720> has<01:09:18.839> decoupled<01:09:19.260> from<01:09:19.710> the<01:09:20.310> consensus 01:09:20.870 --> 01:09:20.880 align:start position:0% it has decoupled from the consensus 01:09:20.880 --> 01:09:22.789 align:start position:0% it has decoupled from the consensus algorithm<01:09:21.120> you<01:09:22.109> could<01:09:22.290> use<01:09:22.470> something<01:09:22.650> like 01:09:22.789 --> 01:09:22.799 align:start position:0% algorithm you could use something like 01:09:22.799 --> 01:09:26.870 align:start position:0% algorithm you could use something like the<01:09:23.040> a<01:09:23.069> BCI<01:09:23.520> interface<01:09:24.530> like<01:09:25.530> boro<01:09:25.859> boro<01:09:26.310> uses 01:09:26.870 --> 01:09:26.880 align:start position:0% the a BCI interface like boro boro uses 01:09:26.880 --> 01:09:31.280 align:start position:0% the a BCI interface like boro boro uses to<01:09:27.240> have<01:09:27.690> an<01:09:28.109> enclave<01:09:29.180> this<01:09:30.180> Enclave<01:09:30.480> EVM<01:09:31.020> run 01:09:31.280 --> 01:09:31.290 align:start position:0% to have an enclave this Enclave EVM run 01:09:31.290 --> 01:09:34.430 align:start position:0% to have an enclave this Enclave EVM run off<01:09:31.500> chain<01:09:32.210> and<01:09:33.210> then<01:09:33.420> write<01:09:33.630> results<01:09:34.080> on<01:09:34.260> to 01:09:34.430 --> 01:09:34.440 align:start position:0% off chain and then write results on to 01:09:34.440 --> 01:09:37.400 align:start position:0% off chain and then write results on to the<01:09:34.530> chain<01:09:35.060> sometimes<01:09:36.060> we<01:09:36.299> call<01:09:36.450> that<01:09:36.510> even<01:09:37.350> on 01:09:37.400 --> 01:09:37.410 align:start position:0% the chain sometimes we call that even on 01:09:37.410 --> 01:09:38.960 align:start position:0% the chain sometimes we call that even on the<01:09:37.500> public<01:09:37.799> network<01:09:37.830> record<01:09:38.310> so<01:09:38.490> must<01:09:38.910> be 01:09:38.960 --> 01:09:38.970 align:start position:0% the public network record so must be 01:09:38.970 --> 01:09:42.650 align:start position:0% the public network record so must be check<01:09:39.780> some<01:09:40.339> node<01:09:41.339> that<01:09:41.850> actually<01:09:42.180> executes 01:09:42.650 --> 01:09:42.660 align:start position:0% check some node that actually executes 01:09:42.660 --> 01:09:44.000 align:start position:0% check some node that actually executes decoded<01:09:43.350> and<01:09:43.440> SGX 01:09:44.000 --> 01:09:44.010 align:start position:0% decoded and SGX 01:09:44.010 --> 01:09:46.340 align:start position:0% decoded and SGX the<01:09:44.370> rest<01:09:44.520> of<01:09:44.640> them<01:09:44.760> don't<01:09:44.940> have<01:09:45.060> to<01:09:45.240> do<01:09:45.359> that 01:09:46.340 --> 01:09:46.350 align:start position:0% the rest of them don't have to do that 01:09:46.350 --> 01:09:47.660 align:start position:0% the rest of them don't have to do that as<01:09:46.650> long<01:09:46.830> as<01:09:46.980> you<01:09:47.069> come<01:09:47.190> to<01:09:47.339> agreement<01:09:47.640> on 01:09:47.660 --> 01:09:47.670 align:start position:0% as long as you come to agreement on 01:09:47.670 --> 01:09:48.800 align:start position:0% as long as you come to agreement on consensus<01:09:48.210> it<01:09:48.330> would<01:09:48.420> be<01:09:48.510> an<01:09:48.630> interesting 01:09:48.800 --> 01:09:48.810 align:start position:0% consensus it would be an interesting 01:09:48.810 --> 01:09:52.789 align:start position:0% consensus it would be an interesting scenario<01:09:49.790> it<01:09:50.790> is<01:09:50.850> an<01:09:51.120> MIT<01:09:51.359> license<01:09:52.200> so 01:09:52.789 --> 01:09:52.799 align:start position:0% scenario it is an MIT license so 01:09:52.799 --> 01:09:55.400 align:start position:0% scenario it is an MIT license so currently<01:09:53.780> it<01:09:54.780> won't<01:09:54.960> go<01:09:55.110> any<01:09:55.230> more 01:09:55.400 --> 01:09:55.410 align:start position:0% currently it won't go any more 01:09:55.410 --> 01:09:57.310 align:start position:0% currently it won't go any more restrictive<01:09:55.830> I<01:09:55.890> don't<01:09:56.040> believe<01:09:56.220> so 01:09:57.310 --> 01:09:57.320 align:start position:0% restrictive I don't believe so 01:09:57.320 --> 01:10:01.100 align:start position:0% restrictive I don't believe so alright<01:09:58.320> next<01:09:58.470> slide<01:09:58.710> oh<01:09:59.330> there<01:10:00.330> the<01:10:00.660> URL<01:10:01.020> is 01:10:01.100 --> 01:10:01.110 align:start position:0% alright next slide oh there the URL is 01:10:01.110 --> 01:10:04.280 align:start position:0% alright next slide oh there the URL is there<01:10:01.230> if<01:10:01.950> you<01:10:02.040> notice<01:10:02.280> that<01:10:02.400> I<01:10:02.990> won't<01:10:03.990> get<01:10:04.140> up 01:10:04.280 --> 01:10:04.290 align:start position:0% there if you notice that I won't get up 01:10:04.290 --> 01:10:07.200 align:start position:0% there if you notice that I won't get up so<01:10:05.090> let's<01:10:06.090> go<01:10:06.240> next 01:10:07.200 --> 01:10:07.210 align:start position:0% so let's go next 01:10:07.210 --> 01:10:08.850 align:start position:0% so let's go next here's<01:10:07.600> another<01:10:07.750> example<01:10:08.020> this<01:10:08.440> is<01:10:08.500> sort<01:10:08.830> of 01:10:08.850 --> 01:10:08.860 align:start position:0% here's another example this is sort of 01:10:08.860 --> 01:10:12.270 align:start position:0% here's another example this is sort of an<01:10:09.190> eye<01:10:09.370> chart<01:10:09.640> this<01:10:09.880> is<01:10:10.620> more<01:10:11.620> of<01:10:11.680> an<01:10:11.770> example 01:10:12.270 --> 01:10:12.280 align:start position:0% an eye chart this is more of an example 01:10:12.280 --> 01:10:13.890 align:start position:0% an eye chart this is more of an example of<01:10:12.400> how<01:10:12.490> what<01:10:12.790> we<01:10:12.910> do<01:10:13.030> in<01:10:13.150> the<01:10:13.240> middle<01:10:13.450> tier<01:10:13.600> one 01:10:13.890 --> 01:10:13.900 align:start position:0% of how what we do in the middle tier one 01:10:13.900 --> 01:10:16.560 align:start position:0% of how what we do in the middle tier one of<01:10:13.990> the<01:10:14.050> things<01:10:14.230> that<01:10:14.380> we<01:10:14.470> do<01:10:14.680> and<01:10:14.920> a<01:10:15.850> lot<01:10:16.480> of 01:10:16.560 --> 01:10:16.570 align:start position:0% of the things that we do and a lot of 01:10:16.570 --> 01:10:18.510 align:start position:0% of the things that we do and a lot of customers<01:10:16.990> have<01:10:17.170> difficulty<01:10:17.860> in<01:10:18.100> the 01:10:18.510 --> 01:10:18.520 align:start position:0% customers have difficulty in the 01:10:18.520 --> 01:10:20.730 align:start position:0% customers have difficulty in the enterprise<01:10:18.880> of<01:10:19.210> managing<01:10:20.020> keys<01:10:20.260> and<01:10:20.530> want<01:10:20.680> to 01:10:20.730 --> 01:10:20.740 align:start position:0% enterprise of managing keys and want to 01:10:20.740 --> 01:10:22.770 align:start position:0% enterprise of managing keys and want to have<01:10:20.860> key<01:10:21.220> management<01:10:21.550> building<01:10:22.360> blockchain 01:10:22.770 --> 01:10:22.780 align:start position:0% have key management building blockchain 01:10:22.780 --> 01:10:23.820 align:start position:0% have key management building blockchain applications<01:10:23.410> for<01:10:23.680> enterprise 01:10:23.820 --> 01:10:23.830 align:start position:0% applications for enterprise 01:10:23.830 --> 01:10:26.070 align:start position:0% applications for enterprise organizations<01:10:24.610> creates<01:10:25.000> a<01:10:25.060> huge<01:10:25.360> problem<01:10:25.510> and 01:10:26.070 --> 01:10:26.080 align:start position:0% organizations creates a huge problem and 01:10:26.080 --> 01:10:28.770 align:start position:0% organizations creates a huge problem and that<01:10:26.800> your<01:10:27.220> if<01:10:27.850> you<01:10:28.000> need<01:10:28.150> to<01:10:28.240> sign<01:10:28.480> your 01:10:28.770 --> 01:10:28.780 align:start position:0% that your if you need to sign your 01:10:28.780 --> 01:10:31.170 align:start position:0% that your if you need to sign your transactions<01:10:29.410> for<01:10:29.590> each<01:10:29.940> individual<01:10:30.940> person 01:10:31.170 --> 01:10:31.180 align:start position:0% transactions for each individual person 01:10:31.180 --> 01:10:34.920 align:start position:0% transactions for each individual person you've<01:10:31.630> got<01:10:31.660> a<01:10:31.900> lot<01:10:32.200> of<01:10:32.320> keys<01:10:32.560> to<01:10:32.590> manage<01:10:33.930> what 01:10:34.920 --> 01:10:34.930 align:start position:0% you've got a lot of keys to manage what 01:10:34.930 --> 01:10:39.210 align:start position:0% you've got a lot of keys to manage what we<01:10:35.020> do<01:10:35.200> here<01:10:35.860> is<01:10:36.010> we<01:10:36.340> use<01:10:36.760> HSMs<01:10:37.770> and<01:10:38.770> Azure<01:10:38.950> that 01:10:39.210 --> 01:10:39.220 align:start position:0% we do here is we use HSMs and Azure that 01:10:39.220 --> 01:10:41.330 align:start position:0% we do here is we use HSMs and Azure that as<01:10:39.400> a<01:10:39.430> service<01:10:39.730> we<01:10:39.850> call<01:10:40.000> as<01:10:40.330> your<01:10:40.600> key<01:10:40.840> vault 01:10:41.330 --> 01:10:41.340 align:start position:0% as a service we call as your key vault 01:10:41.340 --> 01:10:44.070 align:start position:0% as a service we call as your key vault we<01:10:42.340> front-end<01:10:42.790> that<01:10:42.850> with<01:10:43.120> some<01:10:43.240> enclaves<01:10:43.780> and 01:10:44.070 --> 01:10:44.080 align:start position:0% we front-end that with some enclaves and 01:10:44.080 --> 01:10:46.740 align:start position:0% we front-end that with some enclaves and we<01:10:44.500> can<01:10:44.710> at<01:10:45.670> run<01:10:46.000> time<01:10:46.030> when<01:10:46.480> you're<01:10:46.600> running 01:10:46.740 --> 01:10:46.750 align:start position:0% we can at run time when you're running 01:10:46.750 --> 01:10:49.740 align:start position:0% we can at run time when you're running an<01:10:46.960> execution<01:10:47.560> of<01:10:48.010> some<01:10:48.460> logic<01:10:48.880> could<01:10:49.060> be<01:10:49.210> any 01:10:49.740 --> 01:10:49.750 align:start position:0% an execution of some logic could be any 01:10:49.750 --> 01:10:52.320 align:start position:0% an execution of some logic could be any type<01:10:50.170> of<01:10:50.200> code<01:10:50.830> we<01:10:51.250> call<01:10:51.400> that<01:10:51.520> code<01:10:52.120> running 01:10:52.320 --> 01:10:52.330 align:start position:0% type of code we call that code running 01:10:52.330 --> 01:10:55.110 align:start position:0% type of code we call that code running and<01:10:52.920> that<01:10:53.920> your<01:10:54.100> logic<01:10:54.430> called<01:10:54.640> a<01:10:54.910> late' 01:10:55.110 --> 01:10:55.120 align:start position:0% and that your logic called a late' 01:10:55.120 --> 01:10:57.870 align:start position:0% and that your logic called a late' you<01:10:56.020> create<01:10:56.380> some<01:10:56.590> sort<01:10:56.740> of<01:10:56.860> result<01:10:57.310> like<01:10:57.460> 42 01:10:57.870 --> 01:10:57.880 align:start position:0% you create some sort of result like 42 01:10:57.880 --> 01:11:02.130 align:start position:0% you create some sort of result like 42 and<01:10:58.600> you<01:10:58.720> need<01:10:58.870> to<01:10:58.960> sign<01:10:59.200> your<01:10:59.910> proof<01:11:01.140> not 01:11:02.130 --> 01:11:02.140 align:start position:0% and you need to sign your proof not 01:11:02.140 --> 01:11:03.510 align:start position:0% and you need to sign your proof not actually<01:11:02.380> we're<01:11:02.680> not<01:11:02.770> talking<01:11:02.980> about<01:11:03.010> Enclave 01:11:03.510 --> 01:11:03.520 align:start position:0% actually we're not talking about Enclave 01:11:03.520 --> 01:11:04.680 align:start position:0% actually we're not talking about Enclave proof<01:11:03.730> we're<01:11:03.910> just<01:11:04.030> saying<01:11:04.180> I<01:11:04.270> need<01:11:04.330> to<01:11:04.540> sign 01:11:04.680 --> 01:11:04.690 align:start position:0% proof we're just saying I need to sign 01:11:04.690 --> 01:11:08.100 align:start position:0% proof we're just saying I need to sign this<01:11:04.870> transaction<01:11:06.630> but<01:11:07.630> I<01:11:07.660> don't<01:11:07.870> want<01:11:08.020> to 01:11:08.100 --> 01:11:08.110 align:start position:0% this transaction but I don't want to 01:11:08.110 --> 01:11:11.340 align:start position:0% this transaction but I don't want to have<01:11:08.770> my<01:11:08.950> keys<01:11:09.220> inside<01:11:09.550> this<01:11:09.970> code<01:11:10.210> I<01:11:10.450> think<01:11:10.630> we 01:11:11.340 --> 01:11:11.350 align:start position:0% have my keys inside this code I think we 01:11:11.350 --> 01:11:12.930 align:start position:0% have my keys inside this code I think we use<01:11:11.470> this<01:11:11.620> is<01:11:11.800> what<01:11:11.950> we<01:11:12.040> call<01:11:12.190> crypto<01:11:12.520> delegate 01:11:12.930 --> 01:11:12.940 align:start position:0% use this is what we call crypto delegate 01:11:12.940 --> 01:11:14.520 align:start position:0% use this is what we call crypto delegate we<01:11:13.390> just<01:11:13.570> delegate<01:11:13.930> all<01:11:14.170> cryptographic 01:11:14.520 --> 01:11:14.530 align:start position:0% we just delegate all cryptographic 01:11:14.530 --> 01:11:19.350 align:start position:0% we just delegate all cryptographic operations<01:11:15.510> to<01:11:16.510> an<01:11:16.660> enclave<01:11:17.910> out<01:11:18.910> of<01:11:19.090> the<01:11:19.150> pool 01:11:19.350 --> 01:11:19.360 align:start position:0% operations to an enclave out of the pool 01:11:19.360 --> 01:11:21.870 align:start position:0% operations to an enclave out of the pool and<01:11:19.630> in<01:11:20.200> the<01:11:20.410> future<01:11:20.590> we<01:11:20.830> think<01:11:20.860> this<01:11:21.640> will<01:11:21.820> be 01:11:21.870 --> 01:11:21.880 align:start position:0% and in the future we think this will be 01:11:21.880 --> 01:11:23.010 align:start position:0% and in the future we think this will be useful<01:11:22.240> to<01:11:22.270> create<01:11:22.720> some<01:11:22.840> of<01:11:22.870> this 01:11:23.010 --> 01:11:23.020 align:start position:0% useful to create some of this 01:11:23.020 --> 01:11:25.230 align:start position:0% useful to create some of this multi-party<01:11:23.590> compute<01:11:24.000> scenarios<01:11:25.000> where<01:11:25.210> we 01:11:25.230 --> 01:11:25.240 align:start position:0% multi-party compute scenarios where we 01:11:25.240 --> 01:11:28.050 align:start position:0% multi-party compute scenarios where we can<01:11:25.450> do<01:11:25.680> rapidly<01:11:26.680> create<01:11:27.100> things<01:11:27.580> like<01:11:27.730> ring 01:11:28.050 --> 01:11:28.060 align:start position:0% can do rapidly create things like ring 01:11:28.060 --> 01:11:35.450 align:start position:0% can do rapidly create things like ring and<01:11:28.360> threshold<01:11:29.310> artifacts<01:11:30.310> out<01:11:30.640> of<01:11:30.880> this<01:11:31.890> okay 01:11:35.450 --> 01:11:35.460 align:start position:0% 01:11:35.460 --> 01:11:39.360 align:start position:0% so<01:11:36.460> big<01:11:36.910> picture<01:11:37.470> again<01:11:38.470> we're<01:11:38.860> building<01:11:39.190> sort 01:11:39.360 --> 01:11:39.370 align:start position:0% so big picture again we're building sort 01:11:39.370 --> 01:11:43.260 align:start position:0% so big picture again we're building sort of<01:11:39.490> a<01:11:39.610> broad<01:11:40.210> platform<01:11:41.640> watching<01:11:42.640> agnostic<01:11:43.150> we 01:11:43.260 --> 01:11:43.270 align:start position:0% of a broad platform watching agnostic we 01:11:43.270 --> 01:11:45.180 align:start position:0% of a broad platform watching agnostic we started<01:11:43.510> with<01:11:43.630> aetherium<01:11:43.870> will<01:11:44.830> we<01:11:44.950> support 01:11:45.180 --> 01:11:45.190 align:start position:0% started with aetherium will we support 01:11:45.190 --> 01:11:47.180 align:start position:0% started with aetherium will we support essentially<01:11:46.000> all<01:11:46.270> blockchains 01:11:47.180 --> 01:11:47.190 align:start position:0% essentially all blockchains 01:11:47.190 --> 01:11:52.710 align:start position:0% essentially all blockchains go<01:11:48.190> ahead<01:11:48.310> and<01:11:50.100> give<01:11:51.100> you<01:11:51.160> an<01:11:51.280> example 01:11:52.710 --> 01:11:52.720 align:start position:0% go ahead and give you an example 01:11:52.720 --> 01:11:55.620 align:start position:0% go ahead and give you an example see<01:11:53.260> CBF<01:11:53.710> is<01:11:54.010> that<01:11:54.460> that<01:11:54.700> lower<01:11:54.880> level<01:11:55.150> so<01:11:55.480> this 01:11:55.620 --> 01:11:55.630 align:start position:0% see CBF is that that lower level so this 01:11:55.630 --> 01:11:57.170 align:start position:0% see CBF is that that lower level so this is<01:11:55.750> the<01:11:55.870> tearing<01:11:56.260> so<01:11:56.440> the<01:11:56.620> data<01:11:56.770> tier 01:11:57.170 --> 01:11:57.180 align:start position:0% is the tearing so the data tier 01:11:57.180 --> 01:11:59.730 align:start position:0% is the tearing so the data tier introducing<01:11:58.180> a<01:11:58.240> framework<01:11:58.480> that<01:11:59.230> allows<01:11:59.410> you 01:11:59.730 --> 01:11:59.740 align:start position:0% introducing a framework that allows you 01:11:59.740 --> 01:12:02.190 align:start position:0% introducing a framework that allows you to<01:11:59.890> build<01:12:00.070> the<01:12:00.190> next<01:12:00.370> generation<01:12:00.910> and<01:12:01.870> source 01:12:02.190 --> 01:12:02.200 align:start position:0% to build the next generation and source 01:12:02.200 --> 01:12:07.110 align:start position:0% to build the next generation and source 'm<01:12:02.410> so<01:12:02.770> this<01:12:02.890> is<01:12:03.040> private<01:12:03.550> right<01:12:04.560> network<01:12:06.120> so 01:12:07.110 --> 01:12:07.120 align:start position:0% 'm so this is private right network so 01:12:07.120 --> 01:12:09.030 align:start position:0% 'm so this is private right network so that's<01:12:07.240> that's<01:12:07.750> down<01:12:07.990> here 01:12:09.030 --> 01:12:09.040 align:start position:0% that's that's down here 01:12:09.040 --> 01:12:11.580 align:start position:0% that's that's down here middleware<01:12:09.580> platforms<01:12:10.180> there's<01:12:10.930> a<01:12:11.020> range<01:12:11.350> of 01:12:11.580 --> 01:12:11.590 align:start position:0% middleware platforms there's a range of 01:12:11.590 --> 01:12:13.860 align:start position:0% middleware platforms there's a range of services<01:12:11.710> that<01:12:12.070> we'll<01:12:12.250> be<01:12:12.340> introducing<01:12:12.870> this 01:12:13.860 --> 01:12:13.870 align:start position:0% services that we'll be introducing this 01:12:13.870 --> 01:12:16.410 align:start position:0% services that we'll be introducing this is<01:12:14.020> language<01:12:14.560> agnostic<01:12:14.710> but<01:12:15.580> the<01:12:16.000> intention 01:12:16.410 --> 01:12:16.420 align:start position:0% is language agnostic but the intention 01:12:16.420 --> 01:12:18.360 align:start position:0% is language agnostic but the intention is<01:12:16.510> to<01:12:16.600> be<01:12:16.720> able<01:12:16.810> to<01:12:16.900> support<01:12:17.230> any<01:12:17.890> language 01:12:18.360 --> 01:12:18.370 align:start position:0% is to be able to support any language 01:12:18.370 --> 01:12:20.830 align:start position:0% is to be able to support any language any<01:12:18.670> runtime<01:12:19.000> whether<01:12:19.450> it 01:12:20.830 --> 01:12:20.840 align:start position:0% any runtime whether it 01:12:20.840 --> 01:12:24.490 align:start position:0% any runtime whether it dotnet<01:12:21.470> core<01:12:21.710> Java<01:12:22.340> JVM<01:12:23.050> actually<01:12:24.050> working<01:12:24.380> on 01:12:24.490 --> 01:12:24.500 align:start position:0% dotnet core Java JVM actually working on 01:12:24.500 --> 01:12:28.000 align:start position:0% dotnet core Java JVM actually working on those<01:12:25.100> some<01:12:25.340> room<01:12:26.170> actually<01:12:27.170> working<01:12:27.320> on<01:12:27.530> that 01:12:28.000 --> 01:12:28.010 align:start position:0% those some room actually working on that 01:12:28.010 --> 01:12:29.920 align:start position:0% those some room actually working on that implementation<01:12:28.490> right<01:12:28.760> now<01:12:28.910> and<01:12:29.180> then<01:12:29.840> we 01:12:29.920 --> 01:12:29.930 align:start position:0% implementation right now and then we 01:12:29.930 --> 01:12:31.300 align:start position:0% implementation right now and then we also<01:12:30.110> have<01:12:30.350> an<01:12:30.440> offering<01:12:30.710> called<01:12:30.950> as<01:12:31.100> your 01:12:31.300 --> 01:12:31.310 align:start position:0% also have an offering called as your 01:12:31.310 --> 01:12:33.820 align:start position:0% also have an offering called as your work<01:12:31.670> bench<01:12:31.880> watching<01:12:32.600> workbench<01:12:33.170> which 01:12:33.820 --> 01:12:33.830 align:start position:0% work bench watching workbench which 01:12:33.830 --> 01:12:36.550 align:start position:0% work bench watching workbench which allows<01:12:34.100> you<01:12:34.280> to<01:12:34.400> rapidly<01:12:34.640> prototype<01:12:35.560> your 01:12:36.550 --> 01:12:36.560 align:start position:0% allows you to rapidly prototype your 01:12:36.560 --> 01:12:37.990 align:start position:0% allows you to rapidly prototype your solution<01:12:37.010> so<01:12:37.190> any<01:12:37.460> of<01:12:37.550> you<01:12:37.640> that<01:12:37.760> are<01:12:37.820> trying 01:12:37.990 --> 01:12:38.000 align:start position:0% solution so any of you that are trying 01:12:38.000 --> 01:12:41.620 align:start position:0% solution so any of you that are trying to<01:12:38.210> build<01:12:38.420> an<01:12:38.930> application<01:12:39.680> or<01:12:40.490> to<01:12:41.300> get 01:12:41.620 --> 01:12:41.630 align:start position:0% to build an application or to get 01:12:41.630 --> 01:12:44.130 align:start position:0% to build an application or to get funding<01:12:42.080> for<01:12:42.230> one<01:12:42.410> or<01:12:42.590> get<01:12:42.680> approval<01:12:43.100> to<01:12:43.190> do<01:12:43.340> it 01:12:44.130 --> 01:12:44.140 align:start position:0% funding for one or get approval to do it 01:12:44.140 --> 01:12:46.480 align:start position:0% funding for one or get approval to do it but<01:12:45.140> you<01:12:45.320> don't<01:12:45.530> have<01:12:45.740> anything<01:12:45.920> to<01:12:46.070> show<01:12:46.250> for 01:12:46.480 --> 01:12:46.490 align:start position:0% but you don't have anything to show for 01:12:46.490 --> 01:12:48.820 align:start position:0% but you don't have anything to show for you<01:12:46.940> can<01:12:47.090> rapidly<01:12:47.420> build<01:12:47.750> an<01:12:48.200> application 01:12:48.820 --> 01:12:48.830 align:start position:0% you can rapidly build an application 01:12:48.830 --> 01:12:51.670 align:start position:0% you can rapidly build an application here<01:12:49.100> and<01:12:49.550> workbench<01:12:50.390> and<01:12:50.690> have<01:12:51.020> it<01:12:51.140> build<01:12:51.350> a 01:12:51.670 --> 01:12:51.680 align:start position:0% here and workbench and have it build a 01:12:51.680 --> 01:12:55.230 align:start position:0% here and workbench and have it build a solution<01:12:52.220> on<01:12:52.430> a<01:12:52.750> theorem<01:12:53.750> or<01:12:53.930> EEA 01:12:55.230 --> 01:12:55.240 align:start position:0% solution on a theorem or EEA 01:12:55.240 --> 01:12:57.730 align:start position:0% solution on a theorem or EEA implementation<01:12:56.240> and<01:12:57.020> go<01:12:57.200> get<01:12:57.350> your<01:12:57.500> funding 01:12:57.730 --> 01:12:57.740 align:start position:0% implementation and go get your funding 01:12:57.740 --> 01:12:59.170 align:start position:0% implementation and go get your funding cuz<01:12:57.950> that's<01:12:58.070> a<01:12:58.160> pretty<01:12:58.340> user<01:12:58.550> interface<01:12:58.940> and 01:12:59.170 --> 01:12:59.180 align:start position:0% cuz that's a pretty user interface and 01:12:59.180 --> 01:13:00.730 align:start position:0% cuz that's a pretty user interface and it<01:12:59.300> has<01:12:59.600> all<01:12:59.780> the<01:12:59.900> features<01:13:00.050> and<01:13:00.440> bells<01:13:00.590> and 01:13:00.730 --> 01:13:00.740 align:start position:0% it has all the features and bells and 01:13:00.740 --> 01:13:03.190 align:start position:0% it has all the features and bells and whistles<01:13:01.040> that<01:13:01.670> you<01:13:01.700> want<01:13:02.090> to<01:13:02.240> demonstrate<01:13:03.050> so 01:13:03.190 --> 01:13:03.200 align:start position:0% whistles that you want to demonstrate so 01:13:03.200 --> 01:13:05.590 align:start position:0% whistles that you want to demonstrate so it's<01:13:03.350> an<01:13:03.470> awesome<01:13:03.860> tool<01:13:04.040> to<01:13:04.790> go<01:13:05.270> out<01:13:05.420> and 01:13:05.590 --> 01:13:05.600 align:start position:0% it's an awesome tool to go out and 01:13:05.600 --> 01:13:07.900 align:start position:0% it's an awesome tool to go out and rapidly<01:13:06.050> move<01:13:07.040> forward<01:13:07.340> towards<01:13:07.610> your<01:13:07.730> use 01:13:07.900 --> 01:13:07.910 align:start position:0% rapidly move forward towards your use 01:13:07.910 --> 01:13:17.890 align:start position:0% rapidly move forward towards your use cases<01:13:08.230> that's<01:13:09.230> it<01:13:09.350> for<01:13:09.470> me<01:13:09.560> I<01:13:16.180> think<01:13:17.180> the<01:13:17.540> last 01:13:17.890 --> 01:13:17.900 align:start position:0% cases that's it for me I think the last 01:13:17.900 --> 01:13:21.700 align:start position:0% cases that's it for me I think the last up<01:13:18.820> for<01:13:19.820> the<01:13:19.910> presentation<01:13:20.180> is<01:13:20.600> lei<01:13:21.170> from<01:13:21.230> my 01:13:21.700 --> 01:13:21.710 align:start position:0% up for the presentation is lei from my 01:13:21.710 --> 01:13:29.230 align:start position:0% up for the presentation is lei from my exec<01:13:22.100> and<01:13:25.060> so<01:13:26.060> so<01:13:26.810> in<01:13:27.440> this<01:13:27.680> one<01:13:27.950> it's<01:13:28.370> a<01:13:28.580> short 01:13:29.230 --> 01:13:29.240 align:start position:0% exec and so so in this one it's a short 01:13:29.240 --> 01:13:33.360 align:start position:0% exec and so so in this one it's a short presentation<01:13:29.510> and<01:13:30.110> I<01:13:30.230> think<01:13:30.500> a<01:13:31.250> short<01:13:31.580> demo<01:13:32.320> to 01:13:33.360 --> 01:13:33.370 align:start position:0% presentation and I think a short demo to 01:13:33.370 --> 01:13:36.760 align:start position:0% presentation and I think a short demo to you<01:13:34.370> know<01:13:34.520> put<01:13:35.150> put<01:13:35.900> some<01:13:36.140> of<01:13:36.260> these<01:13:36.380> things<01:13:36.560> in 01:13:36.760 --> 01:13:36.770 align:start position:0% you know put put some of these things in 01:13:36.770 --> 01:13:44.770 align:start position:0% you know put put some of these things in context<01:13:41.980> morning<01:13:42.980> everyone<01:13:43.340> my<01:13:44.300> name<01:13:44.480> is<01:13:44.510> lei 01:13:44.770 --> 01:13:44.780 align:start position:0% context morning everyone my name is lei 01:13:44.780 --> 01:13:47.980 align:start position:0% context morning everyone my name is lei and<01:13:45.140> I<01:13:46.010> am<01:13:46.310> from<01:13:46.700> Isaak<01:13:47.360> blockchain 01:13:47.980 --> 01:13:47.990 align:start position:0% and I am from Isaak blockchain 01:13:47.990 --> 01:13:50.800 align:start position:0% and I am from Isaak blockchain technology<01:13:48.890> which<01:13:49.310> is<01:13:49.520> based<01:13:49.550> in<01:13:50.000> Lyon<01:13:50.360> in 01:13:50.800 --> 01:13:50.810 align:start position:0% technology which is based in Lyon in 01:13:50.810 --> 01:13:54.460 align:start position:0% technology which is based in Lyon in France<01:13:51.160> so<01:13:52.160> today<01:13:52.940> I<01:13:53.180> would<01:13:53.420> like<01:13:53.600> to<01:13:53.660> give<01:13:54.140> you 01:13:54.460 --> 01:13:54.470 align:start position:0% France so today I would like to give you 01:13:54.470 --> 01:13:58.060 align:start position:0% France so today I would like to give you a<01:13:54.740> presentation<01:13:55.550> our<01:13:56.410> exact<01:13:57.410> end-to-end 01:13:58.060 --> 01:13:58.070 align:start position:0% a presentation our exact end-to-end 01:13:58.070 --> 01:14:02.200 align:start position:0% a presentation our exact end-to-end trusted<01:13:59.000> execution<01:13:59.240> with<01:14:00.140> info<01:14:00.620> as<01:14:00.830> G<01:14:01.100> X<01:14:01.280> which 01:14:02.200 --> 01:14:02.210 align:start position:0% trusted execution with info as G X which 01:14:02.210 --> 01:14:05.110 align:start position:0% trusted execution with info as G X which is<01:14:02.450> the<01:14:02.600> first<01:14:03.370> stable<01:14:04.370> solution<01:14:04.850> for 01:14:05.110 --> 01:14:05.120 align:start position:0% is the first stable solution for 01:14:05.120 --> 01:14:07.330 align:start position:0% is the first stable solution for business<01:14:05.480> purpose<01:14:05.870> here's<01:14:06.560> Q<01:14:06.950> the<01:14:07.130> blockchain 01:14:07.330 --> 01:14:07.340 align:start position:0% business purpose here's Q the blockchain 01:14:07.340 --> 01:14:10.660 align:start position:0% business purpose here's Q the blockchain based<01:14:07.760> computing<01:14:08.420> using<01:14:09.020> Intel<01:14:09.860> SGX 01:14:10.660 --> 01:14:10.670 align:start position:0% based computing using Intel SGX 01:14:10.670 --> 01:14:14.140 align:start position:0% based computing using Intel SGX I<01:14:10.930> would<01:14:11.930> like<01:14:12.140> to<01:14:12.320> start<01:14:12.680> with<01:14:13.520> talking<01:14:13.880> about 01:14:14.140 --> 01:14:14.150 align:start position:0% I would like to start with talking about 01:14:14.150 --> 01:14:18.100 align:start position:0% I would like to start with talking about what<01:14:15.050> is<01:14:15.440> its<01:14:15.880> interest<01:14:16.880> to<01:14:16.970> X<01:14:17.300> although<01:14:17.840> I 01:14:18.100 --> 01:14:18.110 align:start position:0% what is its interest to X although I 01:14:18.110 --> 01:14:20.230 align:start position:0% what is its interest to X although I know<01:14:18.440> a<01:14:18.620> lot<01:14:18.920> of<01:14:18.950> you<01:14:19.130> guys<01:14:19.340> understand<01:14:20.000> how<01:14:20.030> it 01:14:20.230 --> 01:14:20.240 align:start position:0% know a lot of you guys understand how it 01:14:20.240 --> 01:14:20.800 align:start position:0% know a lot of you guys understand how it works 01:14:20.800 --> 01:14:20.810 align:start position:0% works 01:14:20.810 --> 01:14:24.340 align:start position:0% works so<01:14:21.680> interest<01:14:22.370> react<01:14:22.730> stands<01:14:23.330> for<01:14:23.690> in<01:14:24.080> tow 01:14:24.340 --> 01:14:24.350 align:start position:0% so interest react stands for in tow 01:14:24.350 --> 01:14:27.790 align:start position:0% so interest react stands for in tow software<01:14:24.950> called<01:14:25.430> extensions<01:14:26.210> so<01:14:26.930> basically 01:14:27.790 --> 01:14:27.800 align:start position:0% software called extensions so basically 01:14:27.800 --> 01:14:30.040 align:start position:0% software called extensions so basically it's<01:14:28.040> in<01:14:28.250> host<01:14:28.550> clearly<01:14:29.030> technology<01:14:29.660> which<01:14:29.900> is 01:14:30.040 --> 01:14:30.050 align:start position:0% it's in host clearly technology which is 01:14:30.050 --> 01:14:32.649 align:start position:0% it's in host clearly technology which is available<01:14:30.470> since<01:14:30.980> 2000s<01:14:31.760> Christine 01:14:32.649 --> 01:14:32.659 align:start position:0% available since 2000s Christine 01:14:32.659 --> 01:14:37.000 align:start position:0% available since 2000s Christine and<01:14:33.219> interest<01:14:34.219> reax<01:14:34.610> is<01:14:35.000> based<01:14:35.330> on<01:14:35.750> the<01:14:36.010> secret 01:14:37.000 --> 01:14:37.010 align:start position:0% and interest reax is based on the secret 01:14:37.010 --> 01:14:41.140 align:start position:0% and interest reax is based on the secret kings<01:14:37.429> that<01:14:37.880> are<01:14:38.540> fused<01:14:39.130> inside<01:14:40.130> the<01:14:40.460> cpu 01:14:41.140 --> 01:14:41.150 align:start position:0% kings that are fused inside the cpu 01:14:41.150 --> 01:14:44.290 align:start position:0% kings that are fused inside the cpu during<01:14:41.659> the<01:14:41.810> manufacture<01:14:42.460> so<01:14:43.460> basically<01:14:43.940> it's 01:14:44.290 --> 01:14:44.300 align:start position:0% during the manufacture so basically it's 01:14:44.300 --> 01:14:48.580 align:start position:0% during the manufacture so basically it's a<01:14:44.449> hardware<01:14:44.929> based<01:14:46.150> security<01:14:47.590> technologies 01:14:48.580 --> 01:14:48.590 align:start position:0% a hardware based security technologies 01:14:48.590 --> 01:14:52.000 align:start position:0% a hardware based security technologies which<01:14:48.889> means<01:14:49.250> it<01:14:49.550> leaves<01:14:50.239> very<01:14:50.960> very<01:14:51.469> little 01:14:52.000 --> 01:14:52.010 align:start position:0% which means it leaves very very little 01:14:52.010 --> 01:14:54.220 align:start position:0% which means it leaves very very little attacking<01:14:52.850> face<01:14:53.120> for<01:14:53.810> the<01:14:53.900> malicious 01:14:54.220 --> 01:14:54.230 align:start position:0% attacking face for the malicious 01:14:54.230 --> 01:14:57.790 align:start position:0% attacking face for the malicious attackers<01:14:54.790> so<01:14:55.790> basically<01:14:56.239> you<01:14:56.960> can<01:14:57.199> consider 01:14:57.790 --> 01:14:57.800 align:start position:0% attackers so basically you can consider 01:14:57.800 --> 01:15:01.959 align:start position:0% attackers so basically you can consider as<01:14:58.219> GX<01:14:59.150> as<01:14:59.570> a<01:14:59.739> secured<01:15:00.739> bubble<01:15:01.219> surrounding 01:15:01.959 --> 01:15:01.969 align:start position:0% as GX as a secured bubble surrounding 01:15:01.969 --> 01:15:04.629 align:start position:0% as GX as a secured bubble surrounding you<01:15:02.480> application<01:15:03.199> and<01:15:03.639> protective 01:15:04.629 --> 01:15:04.639 align:start position:0% you application and protective 01:15:04.639 --> 01:15:08.290 align:start position:0% you application and protective applications<01:15:05.360> from<01:15:05.960> the<01:15:06.020> host<01:15:06.380> machine<01:15:07.300> for 01:15:08.290 --> 01:15:08.300 align:start position:0% applications from the host machine for 01:15:08.300 --> 01:15:11.500 align:start position:0% applications from the host machine for example<01:15:08.650> if<01:15:09.650> I<01:15:09.920> have<01:15:10.280> a<01:15:10.310> fan<01:15:10.580> tackle<01:15:10.969> occasions 01:15:11.500 --> 01:15:11.510 align:start position:0% example if I have a fan tackle occasions 01:15:11.510 --> 01:15:14.260 align:start position:0% example if I have a fan tackle occasions which<01:15:12.500> contain<01:15:13.010> some<01:15:13.250> of<01:15:13.280> my<01:15:13.580> sensitive<01:15:14.060> data 01:15:14.260 --> 01:15:14.270 align:start position:0% which contain some of my sensitive data 01:15:14.270 --> 01:15:16.570 align:start position:0% which contain some of my sensitive data I<01:15:14.540> want<01:15:15.020> to<01:15:15.139> run<01:15:15.350> these<01:15:15.500> applications<01:15:16.100> on<01:15:16.429> the 01:15:16.570 --> 01:15:16.580 align:start position:0% I want to run these applications on the 01:15:16.580 --> 01:15:19.360 align:start position:0% I want to run these applications on the decentralized<01:15:17.449> networks<01:15:18.020> say<01:15:18.770> if<01:15:18.980> the 01:15:19.360 --> 01:15:19.370 align:start position:0% decentralized networks say if the 01:15:19.370 --> 01:15:21.550 align:start position:0% decentralized networks say if the application<01:15:19.639> runs<01:15:20.060> on<01:15:20.270> your<01:15:20.300> machine<01:15:20.870> think 01:15:21.550 --> 01:15:21.560 align:start position:0% application runs on your machine think 01:15:21.560 --> 01:15:24.100 align:start position:0% application runs on your machine think about<01:15:21.770> it<01:15:21.980> you<01:15:22.760> are<01:15:22.790> the<01:15:23.060> administrator<01:15:23.360> of 01:15:24.100 --> 01:15:24.110 align:start position:0% about it you are the administrator of 01:15:24.110 --> 01:15:26.830 align:start position:0% about it you are the administrator of your<01:15:24.409> machine<01:15:24.889> right<01:15:25.130> you<01:15:25.820> have<01:15:26.090> hundreds 01:15:26.830 --> 01:15:26.840 align:start position:0% your machine right you have hundreds 01:15:26.840 --> 01:15:29.740 align:start position:0% your machine right you have hundreds ways<01:15:27.170> to<01:15:28.010> easily<01:15:28.429> access<01:15:28.790> to<01:15:29.570> this 01:15:29.740 --> 01:15:29.750 align:start position:0% ways to easily access to this 01:15:29.750 --> 01:15:32.800 align:start position:0% ways to easily access to this application<01:15:29.989> and<01:15:30.710> still<01:15:31.489> my<01:15:32.000> sensitive<01:15:32.570> data 01:15:32.800 --> 01:15:32.810 align:start position:0% application and still my sensitive data 01:15:32.810 --> 01:15:34.959 align:start position:0% application and still my sensitive data in<01:15:33.500> which<01:15:33.860> I've<01:15:34.010> been<01:15:34.159> involved<01:15:34.460> in<01:15:34.760> this 01:15:34.959 --> 01:15:34.969 align:start position:0% in which I've been involved in this 01:15:34.969 --> 01:15:39.310 align:start position:0% in which I've been involved in this application<01:15:35.920> so<01:15:36.920> thanks<01:15:37.730> to<01:15:37.760> this<01:15:38.060> intro<01:15:38.659> SGX 01:15:39.310 --> 01:15:39.320 align:start position:0% application so thanks to this intro SGX 01:15:39.320 --> 01:15:42.700 align:start position:0% application so thanks to this intro SGX technology<01:15:40.100> so<01:15:40.820> interest<01:15:41.659> reacts<01:15:42.020> creates<01:15:42.560> a 01:15:42.700 --> 01:15:42.710 align:start position:0% technology so interest reacts creates a 01:15:42.710 --> 01:15:46.510 align:start position:0% technology so interest reacts creates a bubble<01:15:43.130> which<01:15:43.940> is<01:15:44.150> strictly<01:15:45.010> isolate<01:15:46.010> the 01:15:46.510 --> 01:15:46.520 align:start position:0% bubble which is strictly isolate the 01:15:46.520 --> 01:15:49.570 align:start position:0% bubble which is strictly isolate the application<01:15:47.300> from<01:15:47.780> the<01:15:47.900> host<01:15:48.139> machine<01:15:48.429> so<01:15:49.429> in 01:15:49.570 --> 01:15:49.580 align:start position:0% application from the host machine so in 01:15:49.580 --> 01:15:52.300 align:start position:0% application from the host machine so in this<01:15:49.760> case<01:15:50.030> even<01:15:50.659> you<01:15:51.020> are<01:15:51.290> the<01:15:51.500> administrator 01:15:52.300 --> 01:15:52.310 align:start position:0% this case even you are the administrator 01:15:52.310 --> 01:15:54.970 align:start position:0% this case even you are the administrator of<01:15:52.340> your<01:15:52.550> machine<01:15:52.909> you<01:15:53.540> cannot<01:15:54.050> penetrate 01:15:54.970 --> 01:15:54.980 align:start position:0% of your machine you cannot penetrate 01:15:54.980 --> 01:15:57.520 align:start position:0% of your machine you cannot penetrate this<01:15:55.520> bubble<01:15:55.969> and<01:15:56.230> access<01:15:57.230> to<01:15:57.380> my 01:15:57.520 --> 01:15:57.530 align:start position:0% this bubble and access to my 01:15:57.530 --> 01:16:00.189 align:start position:0% this bubble and access to my applications<01:15:58.219> to<01:15:58.550> camera<01:15:59.030> map<01:15:59.179> occasions<01:15:59.690> to 01:16:00.189 --> 01:16:00.199 align:start position:0% applications to camera map occasions to 01:16:00.199 --> 01:16:02.919 align:start position:0% applications to camera map occasions to steal<01:16:00.530> the<01:16:00.800> secrets<01:16:01.330> involved<01:16:02.330> in<01:16:02.719> this 01:16:02.919 --> 01:16:02.929 align:start position:0% steal the secrets involved in this 01:16:02.929 --> 01:16:06.820 align:start position:0% steal the secrets involved in this application<01:16:04.510> so<01:16:05.510> based<01:16:05.810> on<01:16:05.989> the<01:16:06.230> s3x 01:16:06.820 --> 01:16:06.830 align:start position:0% application so based on the s3x 01:16:06.830 --> 01:16:09.970 align:start position:0% application so based on the s3x technology<01:16:07.489> we<01:16:07.940> propose<01:16:08.389> our<01:16:08.719> solution<01:16:09.320> which 01:16:09.970 --> 01:16:09.980 align:start position:0% technology we propose our solution which 01:16:09.980 --> 01:16:13.990 align:start position:0% technology we propose our solution which provides<01:16:10.780> end-to-end<01:16:11.780> data<01:16:12.650> protection<01:16:13.250> for 01:16:13.990 --> 01:16:14.000 align:start position:0% provides end-to-end data protection for 01:16:14.000 --> 01:16:15.550 align:start position:0% provides end-to-end data protection for the<01:16:14.090> applications<01:16:14.719> running<01:16:15.050> on<01:16:15.350> the 01:16:15.550 --> 01:16:15.560 align:start position:0% the applications running on the 01:16:15.560 --> 01:16:17.680 align:start position:0% the applications running on the blockchain<01:16:16.310> base<01:16:16.760> to<01:16:17.000> the<01:16:17.120> centralized 01:16:17.680 --> 01:16:17.690 align:start position:0% blockchain base to the centralized 01:16:17.690 --> 01:16:21.129 align:start position:0% blockchain base to the centralized networks<01:16:18.170> so<01:16:18.949> firstly<01:16:19.310> what<01:16:20.060> is<01:16:20.449> our 01:16:21.129 --> 01:16:21.139 align:start position:0% networks so firstly what is our 01:16:21.139 --> 01:16:26.260 align:start position:0% networks so firstly what is our definition<01:16:22.040> of<01:16:22.250> end-to-end<01:16:23.920> protection<01:16:25.270> we 01:16:26.260 --> 01:16:26.270 align:start position:0% definition of end-to-end protection we 01:16:26.270 --> 01:16:29.850 align:start position:0% definition of end-to-end protection we know<01:16:26.389> that<01:16:26.600> a<01:16:26.949> typical<01:16:27.949> application<01:16:28.699> data 01:16:29.850 --> 01:16:29.860 align:start position:0% know that a typical application data 01:16:29.860 --> 01:16:32.950 align:start position:0% know that a typical application data consists<01:16:30.860> report<01:16:31.370> the<01:16:32.000> application<01:16:32.570> in<01:16:32.719> poor 01:16:32.950 --> 01:16:32.960 align:start position:0% consists report the application in poor 01:16:32.960 --> 01:16:35.590 align:start position:0% consists report the application in poor tailor<01:16:33.199> so<01:16:33.980> mostly<01:16:34.429> probably<01:16:34.790> it<01:16:35.179> from<01:16:35.420> the 01:16:35.590 --> 01:16:35.600 align:start position:0% tailor so mostly probably it from the 01:16:35.600 --> 01:16:38.020 align:start position:0% tailor so mostly probably it from the user<01:16:35.989> side<01:16:36.230> you<01:16:36.560> the<01:16:36.710> import<01:16:37.040> data<01:16:37.130> the 01:16:38.020 --> 01:16:38.030 align:start position:0% user side you the import data the 01:16:38.030 --> 01:16:39.870 align:start position:0% user side you the import data the application<01:16:38.570> in<01:16:38.690> banded<01:16:39.110> data<01:16:39.380> and 01:16:39.870 --> 01:16:39.880 align:start position:0% application in banded data and 01:16:39.880 --> 01:16:42.700 align:start position:0% application in banded data and application<01:16:40.880> output<01:16:41.300> data<01:16:41.480> memory<01:16:42.139> 2<01:16:42.380> refers 01:16:42.700 --> 01:16:42.710 align:start position:0% application output data memory 2 refers 01:16:42.710 --> 01:16:45.129 align:start position:0% application output data memory 2 refers to<01:16:42.739> the<01:16:42.980> application<01:16:43.100> result<01:16:43.820> right 01:16:45.129 --> 01:16:45.139 align:start position:0% to the application result right 01:16:45.139 --> 01:16:49.320 align:start position:0% to the application result right so<01:16:45.770> our<01:16:46.219> end-to-end<01:16:47.210> for<01:16:47.869> protection<01:16:48.560> means<01:16:48.860> a 01:16:49.320 --> 01:16:49.330 align:start position:0% so our end-to-end for protection means a 01:16:49.330 --> 01:16:51.669 align:start position:0% so our end-to-end for protection means a protection<01:16:50.330> for<01:16:50.510> all<01:16:50.630> these<01:16:51.020> application 01:16:51.669 --> 01:16:51.679 align:start position:0% protection for all these application 01:16:51.679 --> 01:16:54.669 align:start position:0% protection for all these application datas<01:16:52.100> all<01:16:52.610> these<01:16:53.119> application<01:16:53.750> data<01:16:53.989> stays 01:16:54.669 --> 01:16:54.679 align:start position:0% datas all these application data stays 01:16:54.679 --> 01:16:57.970 align:start position:0% datas all these application data stays in<01:16:55.100> the<01:16:55.360> encrypted<01:16:56.360> Staters<01:16:56.900> during<01:16:57.830> the 01:16:57.970 --> 01:16:57.980 align:start position:0% in the encrypted Staters during the 01:16:57.980 --> 01:17:00.370 align:start position:0% in the encrypted Staters during the whole<01:16:58.280> procedure<01:16:58.699> of<01:16:59.210> running<01:16:59.690> application 01:17:00.370 --> 01:17:00.380 align:start position:0% whole procedure of running application 01:17:00.380 --> 01:17:03.970 align:start position:0% whole procedure of running application so<01:17:01.280> the<01:17:01.550> creation<01:17:02.210> only<01:17:02.330> happens<01:17:02.960> inside<01:17:03.920> a 01:17:03.970 --> 01:17:03.980 align:start position:0% so the creation only happens inside a 01:17:03.980 --> 01:17:07.390 align:start position:0% so the creation only happens inside a high<01:17:04.580> secure<01:17:05.199> SGX<01:17:06.199> bubble<01:17:06.590> which<01:17:07.010> is<01:17:07.159> also 01:17:07.390 --> 01:17:07.400 align:start position:0% high secure SGX bubble which is also 01:17:07.400 --> 01:17:10.629 align:start position:0% high secure SGX bubble which is also called<01:17:07.790> as<01:17:07.940> reacts<01:17:08.659> Enclave<01:17:09.260> and<01:17:09.500> cannot<01:17:10.400> be 01:17:10.629 --> 01:17:10.639 align:start position:0% called as reacts Enclave and cannot be 01:17:10.639 --> 01:17:13.330 align:start position:0% called as reacts Enclave and cannot be accessible<01:17:11.179> from<01:17:11.449> outside<01:17:11.690> world<01:17:12.230> so<01:17:13.100> from 01:17:13.330 --> 01:17:13.340 align:start position:0% accessible from outside world so from 01:17:13.340 --> 01:17:17.220 align:start position:0% accessible from outside world so from outside<01:17:13.550> world<01:17:14.110> everything<01:17:15.110> happens<01:17:15.830> in<01:17:16.310> this 01:17:17.220 --> 01:17:17.230 align:start position:0% outside world everything happens in this 01:17:17.230 --> 01:17:22.350 align:start position:0% outside world everything happens in this s3x<01:17:18.230> Enclave<01:17:18.920> is<01:17:19.250> in<01:17:19.909> the<01:17:20.060> encrypted<01:17:20.510> status 01:17:22.350 --> 01:17:22.360 align:start position:0% s3x Enclave is in the encrypted status 01:17:22.360 --> 01:17:24.970 align:start position:0% s3x Enclave is in the encrypted status the<01:17:23.360> example<01:17:23.780> I<01:17:23.960> have<01:17:24.230> a<01:17:24.530> fun<01:17:24.830> track 01:17:24.970 --> 01:17:24.980 align:start position:0% the example I have a fun track 01:17:24.980 --> 01:17:27.479 align:start position:0% the example I have a fun track application<01:17:25.190> right<01:17:25.670> I<01:17:25.940> want<01:17:26.270> to<01:17:26.360> run<01:17:26.659> it<01:17:26.960> only 01:17:27.479 --> 01:17:27.489 align:start position:0% application right I want to run it only 01:17:27.489 --> 01:17:30.220 align:start position:0% application right I want to run it only blockchain<01:17:28.489> based<01:17:28.760> decentralized<01:17:29.750> networks 01:17:30.220 --> 01:17:30.230 align:start position:0% blockchain based decentralized networks 01:17:30.230 --> 01:17:33.820 align:start position:0% blockchain based decentralized networks and<01:17:30.980> this<01:17:31.760> Vantage<01:17:32.270> application<01:17:33.050> requires 01:17:33.820 --> 01:17:33.830 align:start position:0% and this Vantage application requires 01:17:33.830 --> 01:17:37.899 align:start position:0% and this Vantage application requires some<01:17:34.489> user<01:17:34.850> as<01:17:35.270> user<01:17:35.869> input<01:17:36.199> data<01:17:36.460> so<01:17:37.460> from<01:17:37.730> my 01:17:37.899 --> 01:17:37.909 align:start position:0% some user as user input data so from my 01:17:37.909 --> 01:17:41.260 align:start position:0% some user as user input data so from my side<01:17:38.210> this<01:17:38.780> user<01:17:39.440> input<01:17:39.830> Eric<01:17:40.130> Oracle<01:17:40.610> asked 01:17:41.260 --> 01:17:41.270 align:start position:0% side this user input Eric Oracle asked 01:17:41.270 --> 01:17:43.899 align:start position:0% side this user input Eric Oracle asked me<01:17:41.570> some<01:17:41.810> about<01:17:41.989> my<01:17:42.440> say<01:17:42.980> bank<01:17:43.460> account 01:17:43.899 --> 01:17:43.909 align:start position:0% me some about my say bank account 01:17:43.909 --> 01:17:46.840 align:start position:0% me some about my say bank account information<01:17:44.540> my<01:17:45.139> privacy<01:17:45.590> information<01:17:45.820> so<01:17:46.820> I 01:17:46.840 --> 01:17:46.850 align:start position:0% information my privacy information so I 01:17:46.850 --> 01:17:49.629 align:start position:0% information my privacy information so I definitely<01:17:47.690> don't<01:17:47.869> want<01:17:48.170> these<01:17:48.440> my<01:17:49.010> personal 01:17:49.629 --> 01:17:49.639 align:start position:0% definitely don't want these my personal 01:17:49.639 --> 01:17:52.390 align:start position:0% definitely don't want these my personal informations<01:17:50.270> to<01:17:50.449> be<01:17:50.869> just<01:17:51.110> diffused<01:17:51.710> to<01:17:52.159> the 01:17:52.390 --> 01:17:52.400 align:start position:0% informations to be just diffused to the 01:17:52.400 --> 01:17:53.820 align:start position:0% informations to be just diffused to the centralized<01:17:52.850> networks 01:17:53.820 --> 01:17:53.830 align:start position:0% centralized networks 01:17:53.830 --> 01:17:58.419 align:start position:0% centralized networks so<01:17:54.830> all<01:17:55.340> this<01:17:55.850> user<01:17:56.300> input<01:17:56.869> data<01:17:57.170> has<01:17:58.130> to<01:17:58.159> be 01:17:58.419 --> 01:17:58.429 align:start position:0% so all this user input data has to be 01:17:58.429 --> 01:18:01.359 align:start position:0% so all this user input data has to be encrypted<01:17:59.300> before<01:18:00.290> staining<01:18:01.010> to<01:18:01.190> the 01:18:01.359 --> 01:18:01.369 align:start position:0% encrypted before staining to the 01:18:01.369 --> 01:18:04.000 align:start position:0% encrypted before staining to the decentralized<01:18:01.850> networks<01:18:02.630> to<01:18:03.170> feed<01:18:03.500> the 01:18:04.000 --> 01:18:04.010 align:start position:0% decentralized networks to feed the 01:18:04.010 --> 01:18:07.450 align:start position:0% decentralized networks to feed the application<01:18:04.550> execution<01:18:05.030> and<01:18:05.949> at<01:18:06.949> the<01:18:07.190> wrong 01:18:07.450 --> 01:18:07.460 align:start position:0% application execution and at the wrong 01:18:07.460 --> 01:18:09.520 align:start position:0% application execution and at the wrong time<01:18:07.820> of<01:18:07.850> the<01:18:08.119> application<01:18:08.869> this<01:18:09.469> application 01:18:09.520 --> 01:18:09.530 align:start position:0% time of the application this application 01:18:09.530 --> 01:18:14.379 align:start position:0% time of the application this application runs<01:18:10.400> in<01:18:10.610> the<01:18:10.790> int<01:18:11.030> o<01:18:11.380> GX<01:18:12.380> Enclave<01:18:13.310> so<01:18:14.060> from 01:18:14.379 --> 01:18:14.389 align:start position:0% runs in the int o GX Enclave so from 01:18:14.389 --> 01:18:16.840 align:start position:0% runs in the int o GX Enclave so from again<01:18:14.719> from<01:18:14.989> outside<01:18:15.170> world<01:18:15.850> everything 01:18:16.840 --> 01:18:16.850 align:start position:0% again from outside world everything 01:18:16.850 --> 01:18:19.629 align:start position:0% again from outside world everything happens<01:18:17.270> in<01:18:17.480> this<01:18:18.219> SGX<01:18:19.219> babo 01:18:19.629 --> 01:18:19.639 align:start position:0% happens in this SGX babo 01:18:19.639 --> 01:18:23.590 align:start position:0% happens in this SGX babo is<01:18:19.820> encrypted<01:18:20.750> status<01:18:21.380> and<01:18:21.790> finally<01:18:22.790> when<01:18:23.449> the 01:18:23.590 --> 01:18:23.600 align:start position:0% is encrypted status and finally when the 01:18:23.600 --> 01:18:25.990 align:start position:0% is encrypted status and finally when the application<01:18:24.170> finishes<01:18:24.650> running<01:18:25.130> it<01:18:25.369> we<01:18:25.790> have 01:18:25.990 --> 01:18:26.000 align:start position:0% application finishes running it we have 01:18:26.000 --> 01:18:29.320 align:start position:0% application finishes running it we have the<01:18:26.119> result<01:18:26.600> and<01:18:26.840> result<01:18:27.590> is<01:18:27.770> also<01:18:28.330> encrypted 01:18:29.320 --> 01:18:29.330 align:start position:0% the result and result is also encrypted 01:18:29.330 --> 01:18:34.270 align:start position:0% the result and result is also encrypted inside<01:18:30.170> this<01:18:30.770> s3x<01:18:31.310> Enclave<01:18:32.469> so<01:18:33.469> finally<01:18:33.920> only 01:18:34.270 --> 01:18:34.280 align:start position:0% inside this s3x Enclave so finally only 01:18:34.280 --> 01:18:36.399 align:start position:0% inside this s3x Enclave so finally only the<01:18:34.639> corresponding<01:18:35.030> user<01:18:35.540> who<01:18:35.900> treated<01:18:36.230> this 01:18:36.399 --> 01:18:36.409 align:start position:0% the corresponding user who treated this 01:18:36.409 --> 01:18:38.740 align:start position:0% the corresponding user who treated this application<01:18:37.130> is<01:18:37.310> able<01:18:38.000> to<01:18:38.119> download<01:18:38.389> an 01:18:38.740 --> 01:18:38.750 align:start position:0% application is able to download an 01:18:38.750 --> 01:18:40.479 align:start position:0% application is able to download an applique<01:18:39.080> at<01:18:39.260> unloaded<01:18:39.800> application<01:18:40.310> out 01:18:40.479 --> 01:18:40.489 align:start position:0% applique at unloaded application out 01:18:40.489 --> 01:18:43.149 align:start position:0% applique at unloaded application out port<01:18:40.820> and<01:18:41.060> only<01:18:41.780> this<01:18:41.929> corresponding<01:18:42.590> user<01:18:42.920> is 01:18:43.149 --> 01:18:43.159 align:start position:0% port and only this corresponding user is 01:18:43.159 --> 01:18:47.010 align:start position:0% port and only this corresponding user is able<01:18:43.730> to<01:18:43.909> decrypt<01:18:44.600> the<01:18:45.290> application<01:18:45.920> output 01:18:47.010 --> 01:18:47.020 align:start position:0% able to decrypt the application output 01:18:47.020 --> 01:18:50.790 align:start position:0% able to decrypt the application output so<01:18:48.020> this<01:18:48.409> is<01:18:48.679> extremely<01:18:49.270> important<01:18:50.270> for<01:18:50.480> the 01:18:50.790 --> 01:18:50.800 align:start position:0% so this is extremely important for the 01:18:50.800 --> 01:18:53.080 align:start position:0% so this is extremely important for the decentralized<01:18:51.800> applications<01:18:52.090> which 01:18:53.080 --> 01:18:53.090 align:start position:0% decentralized applications which 01:18:53.090 --> 01:18:56.080 align:start position:0% decentralized applications which contains<01:18:53.659> some<01:18:53.929> sensitive<01:18:54.560> data<01:18:54.710> and<01:18:55.090> another 01:18:56.080 --> 01:18:56.090 align:start position:0% contains some sensitive data and another 01:18:56.090 --> 01:18:58.280 align:start position:0% contains some sensitive data and another great<01:18:56.330> hue<01:18:56.719> a<01:18:56.989> use<01:18:57.560> case 01:18:58.280 --> 01:18:58.290 align:start position:0% great hue a use case 01:18:58.290 --> 01:19:01.250 align:start position:0% great hue a use case very<01:18:58.500> demoralizing<01:18:59.270> say<01:19:00.270> if<01:19:00.450> I<01:19:00.660> am<01:19:00.900> a<01:19:00.930> data 01:19:01.250 --> 01:19:01.260 align:start position:0% very demoralizing say if I am a data 01:19:01.260 --> 01:19:03.980 align:start position:0% very demoralizing say if I am a data provider<01:19:01.500> I<01:19:02.010> would<01:19:02.850> like<01:19:03.120> to<01:19:03.300> make<01:19:03.480> money<01:19:03.720> by 01:19:03.980 --> 01:19:03.990 align:start position:0% provider I would like to make money by 01:19:03.990 --> 01:19:06.740 align:start position:0% provider I would like to make money by renting<01:19:04.410> my<01:19:04.920> data<01:19:05.190> to<01:19:05.280> you<01:19:05.640> to<01:19:06.300> feed<01:19:06.600> your 01:19:06.740 --> 01:19:06.750 align:start position:0% renting my data to you to feed your 01:19:06.750 --> 01:19:10.370 align:start position:0% renting my data to you to feed your application<01:19:07.410> I<01:19:08.660> definitely<01:19:09.660> don't<01:19:09.810> want<01:19:10.080> you 01:19:10.370 --> 01:19:10.380 align:start position:0% application I definitely don't want you 01:19:10.380 --> 01:19:12.530 align:start position:0% application I definitely don't want you just<01:19:10.710> copy<01:19:11.070> my<01:19:11.340> data<01:19:11.640> and<01:19:11.910> the<01:19:12.000> result<01:19:12.390> of 01:19:12.530 --> 01:19:12.540 align:start position:0% just copy my data and the result of 01:19:12.540 --> 01:19:15.830 align:start position:0% just copy my data and the result of someone<01:19:12.810> else<01:19:12.990> right<01:19:13.260> so<01:19:13.970> the<01:19:14.970> end-to-end 01:19:15.830 --> 01:19:15.840 align:start position:0% someone else right so the end-to-end 01:19:15.840 --> 01:19:19.210 align:start position:0% someone else right so the end-to-end photo<01:19:16.770> data<01:19:16.980> protection<01:19:17.520> is<01:19:18.050> really<01:19:19.050> a 01:19:19.210 --> 01:19:19.220 align:start position:0% photo data protection is really a 01:19:19.220 --> 01:19:22.460 align:start position:0% photo data protection is really a essential<01:19:20.220> requirement<01:19:20.850> in<01:19:21.030> such<01:19:21.470> contests 01:19:22.460 --> 01:19:22.470 align:start position:0% essential requirement in such contests 01:19:22.470 --> 01:19:28.850 align:start position:0% essential requirement in such contests and<01:19:22.680> use<01:19:22.830> case<01:19:24.890> so<01:19:26.990> we<01:19:27.990> talk<01:19:28.230> about<01:19:28.350> any 01:19:28.850 --> 01:19:28.860 align:start position:0% and use case so we talk about any 01:19:28.860 --> 01:19:32.180 align:start position:0% and use case so we talk about any twinned<01:19:29.660> photo<01:19:30.660> for<01:19:31.020> data<01:19:31.200> protection<01:19:31.380> and 01:19:32.180 --> 01:19:32.190 align:start position:0% twinned photo for data protection and 01:19:32.190 --> 01:19:35.690 align:start position:0% twinned photo for data protection and why<01:19:32.640> it<01:19:33.030> is<01:19:33.270> so<01:19:33.570> important<01:19:34.350> to<01:19:34.560> our<01:19:34.920> Isaac 01:19:35.690 --> 01:19:35.700 align:start position:0% why it is so important to our Isaac 01:19:35.700 --> 01:19:38.650 align:start position:0% why it is so important to our Isaac platform<01:19:36.330> and<01:19:36.570> blockchain<01:19:37.320> based<01:19:37.830> cloud 01:19:38.650 --> 01:19:38.660 align:start position:0% platform and blockchain based cloud 01:19:38.660 --> 01:19:43.220 align:start position:0% platform and blockchain based cloud complexion<01:19:39.660> based<01:19:39.840> computing<01:19:41.300> so<01:19:42.300> we<01:19:43.020> know 01:19:43.220 --> 01:19:43.230 align:start position:0% complexion based computing so we know 01:19:43.230 --> 01:19:46.040 align:start position:0% complexion based computing so we know that<01:19:43.470> the<01:19:43.770> core<01:19:44.160> of<01:19:44.430> a<01:19:44.610> proc<01:19:44.850> chain<01:19:45.180> is<01:19:45.450> its 01:19:46.040 --> 01:19:46.050 align:start position:0% that the core of a proc chain is its 01:19:46.050 --> 01:19:48.770 align:start position:0% that the core of a proc chain is its decentralization<01:19:46.940> which<01:19:47.940> means<01:19:48.210> the<01:19:48.330> data<01:19:48.570> or 01:19:48.770 --> 01:19:48.780 align:start position:0% decentralization which means the data or 01:19:48.780 --> 01:19:50.150 align:start position:0% decentralization which means the data or the<01:19:48.870> applications<01:19:49.470> running<01:19:49.800> on<01:19:49.980> the 01:19:50.150 --> 01:19:50.160 align:start position:0% the applications running on the 01:19:50.160 --> 01:19:54.100 align:start position:0% the applications running on the decentralized<01:19:50.820> networks<01:19:51.330> right<01:19:52.250> so 01:19:54.100 --> 01:19:54.110 align:start position:0% decentralized networks right so 01:19:54.110 --> 01:19:57.160 align:start position:0% decentralized networks right so approaching<01:19:55.110> a<01:19:55.260> questions<01:19:55.740> naturally<01:19:56.610> raised 01:19:57.160 --> 01:19:57.170 align:start position:0% approaching a questions naturally raised 01:19:57.170 --> 01:20:00.170 align:start position:0% approaching a questions naturally raised that's<01:19:58.170> decentralized<01:19:59.100> networks<01:19:59.730> being 01:20:00.170 --> 01:20:00.180 align:start position:0% that's decentralized networks being 01:20:00.180 --> 01:20:05.090 align:start position:0% that's decentralized networks being trustless<01:20:01.580> to<01:20:02.580> some<01:20:02.820> extent<01:20:03.300> yes<01:20:03.890> think<01:20:04.890> about 01:20:05.090 --> 01:20:05.100 align:start position:0% trustless to some extent yes think about 01:20:05.100 --> 01:20:08.210 align:start position:0% trustless to some extent yes think about the<01:20:05.700> legacy<01:20:06.080> centralized<01:20:07.080> networks<01:20:07.740> see 01:20:08.210 --> 01:20:08.220 align:start position:0% the legacy centralized networks see 01:20:08.220 --> 01:20:12.020 align:start position:0% the legacy centralized networks see about<01:20:08.400> the<01:20:08.700> cloud<01:20:09.480> provider<01:20:09.900> how<01:20:10.200> it<01:20:10.260> works<01:20:11.030> so 01:20:12.020 --> 01:20:12.030 align:start position:0% about the cloud provider how it works so 01:20:12.030 --> 01:20:14.780 align:start position:0% about the cloud provider how it works so this<01:20:12.300> is<01:20:12.600> a<01:20:12.960> centralized<01:20:13.710> entity<01:20:13.950> or<01:20:14.400> the 01:20:14.780 --> 01:20:14.790 align:start position:0% this is a centralized entity or the 01:20:14.790 --> 01:20:17.330 align:start position:0% this is a centralized entity or the cloud<01:20:15.000> provider<01:20:15.450> cloud<01:20:15.930> administrator<01:20:16.340> who 01:20:17.330 --> 01:20:17.340 align:start position:0% cloud provider cloud administrator who 01:20:17.340 --> 01:20:20.060 align:start position:0% cloud provider cloud administrator who is<01:20:17.430> there<01:20:17.760> to<01:20:18.420> deploy<01:20:18.810> the<01:20:19.110> sophisticated 01:20:20.060 --> 01:20:20.070 align:start position:0% is there to deploy the sophisticated 01:20:20.070 --> 01:20:23.750 align:start position:0% is there to deploy the sophisticated security<01:20:21.060> Magid<01:20:21.750> isms<01:20:22.010> just<01:20:23.010> to<01:20:23.190> protect<01:20:23.610> your 01:20:23.750 --> 01:20:23.760 align:start position:0% security Magid isms just to protect your 01:20:23.760 --> 01:20:26.990 align:start position:0% security Magid isms just to protect your applications<01:20:24.390> wrong<01:20:24.900> on<01:20:25.110> their<01:20:25.610> on<01:20:26.610> the<01:20:26.880> earth 01:20:26.990 --> 01:20:27.000 align:start position:0% applications wrong on their on the earth 01:20:27.000 --> 01:20:29.810 align:start position:0% applications wrong on their on the earth centralized<01:20:27.870> networks<01:20:28.490> but<01:20:29.490> for<01:20:29.730> the 01:20:29.810 --> 01:20:29.820 align:start position:0% centralized networks but for the 01:20:29.820 --> 01:20:32.180 align:start position:0% centralized networks but for the blockchain<01:20:30.240> page<01:20:30.690> to<01:20:30.990> decentralize<01:20:31.560> networks 01:20:32.180 --> 01:20:32.190 align:start position:0% blockchain page to decentralize networks 01:20:32.190 --> 01:20:34.850 align:start position:0% blockchain page to decentralize networks there<01:20:32.880> is<01:20:33.030> no<01:20:33.330> such<01:20:33.690> administrator<01:20:34.530> who<01:20:34.800> is 01:20:34.850 --> 01:20:34.860 align:start position:0% there is no such administrator who is 01:20:34.860 --> 01:20:36.560 align:start position:0% there is no such administrator who is there<01:20:35.130> to<01:20:35.310> protect<01:20:35.520> the<01:20:35.850> applications 01:20:36.560 --> 01:20:36.570 align:start position:0% there to protect the applications 01:20:36.570 --> 01:20:38.870 align:start position:0% there to protect the applications running<01:20:37.260> on<01:20:37.530> the<01:20:37.710> decentralized<01:20:38.250> networks 01:20:38.870 --> 01:20:38.880 align:start position:0% running on the decentralized networks 01:20:38.880 --> 01:20:42.110 align:start position:0% running on the decentralized networks so<01:20:39.750> without<01:20:39.960> the<01:20:40.410> end-to-end<01:20:41.220> their 01:20:42.110 --> 01:20:42.120 align:start position:0% so without the end-to-end their 01:20:42.120 --> 01:20:44.930 align:start position:0% so without the end-to-end their propulsion<01:20:42.600> or<01:20:43.110> your<01:20:43.950> application<01:20:44.700> better 01:20:44.930 --> 01:20:44.940 align:start position:0% propulsion or your application better 01:20:44.940 --> 01:20:48.230 align:start position:0% propulsion or your application better are<01:20:45.480> just<01:20:45.930> exposed<01:20:46.890> to<01:20:47.430> the<01:20:47.550> millions<01:20:48.030> of 01:20:48.230 --> 01:20:48.240 align:start position:0% are just exposed to the millions of 01:20:48.240 --> 01:20:51.830 align:start position:0% are just exposed to the millions of decentralized<01:20:49.170> node<01:20:50.000> so<01:20:51.000> for<01:20:51.210> our<01:20:51.420> eyes<01:20:51.660> our 01:20:51.830 --> 01:20:51.840 align:start position:0% decentralized node so for our eyes our 01:20:51.840 --> 01:20:54.410 align:start position:0% decentralized node so for our eyes our eyes<01:20:51.960> ik<01:20:52.200> platform<01:20:52.740> so<01:20:53.250> basically<01:20:53.640> how<01:20:54.060> Isaac 01:20:54.410 --> 01:20:54.420 align:start position:0% eyes ik platform so basically how Isaac 01:20:54.420 --> 01:20:57.230 align:start position:0% eyes ik platform so basically how Isaac perform<01:20:55.080> away<01:20:55.260> offers<01:20:55.770> a<01:20:55.950> blockchain<01:20:56.820> based 01:20:57.230 --> 01:20:57.240 align:start position:0% perform away offers a blockchain based 01:20:57.240 --> 01:21:00.170 align:start position:0% perform away offers a blockchain based platform<01:20:57.930> to<01:20:58.110> trade<01:20:58.320> computing<01:20:58.920> resources<01:20:59.310> so 01:21:00.170 --> 01:21:00.180 align:start position:0% platform to trade computing resources so 01:21:00.180 --> 01:21:02.030 align:start position:0% platform to trade computing resources so basically<01:21:00.510> if<01:21:00.690> you<01:21:00.840> are<01:21:00.990> a<01:21:01.170> silver<01:21:01.590> provider 01:21:02.030 --> 01:21:02.040 align:start position:0% basically if you are a silver provider 01:21:02.040 --> 01:21:04.850 align:start position:0% basically if you are a silver provider you<01:21:02.670> can<01:21:02.700> join<01:21:03.090> our<01:21:03.360> platform<01:21:03.990> to<01:21:04.170> monetize 01:21:04.850 --> 01:21:04.860 align:start position:0% you can join our platform to monetize 01:21:04.860 --> 01:21:06.980 align:start position:0% you can join our platform to monetize your<01:21:05.040> service<01:21:05.490> service<01:21:05.820> if<01:21:06.060> you<01:21:06.660> are<01:21:06.960> a 01:21:06.980 --> 01:21:06.990 align:start position:0% your service service if you are a 01:21:06.990 --> 01:21:09.380 align:start position:0% your service service if you are a application<01:21:07.860> provider<01:21:08.190> you<01:21:08.730> can<01:21:08.940> join<01:21:09.120> our 01:21:09.380 --> 01:21:09.390 align:start position:0% application provider you can join our 01:21:09.390 --> 01:21:11.510 align:start position:0% application provider you can join our platform<01:21:09.930> to<01:21:10.050> monetize<01:21:10.620> your 01:21:11.510 --> 01:21:11.520 align:start position:0% platform to monetize your 01:21:11.520 --> 01:21:14.120 align:start position:0% platform to monetize your Suri's<01:21:12.150> and<01:21:12.360> it's<01:21:13.230> simile<01:21:13.680> if<01:21:13.770> you<01:21:13.920> are<01:21:14.100> a 01:21:14.120 --> 01:21:14.130 align:start position:0% Suri's and it's simile if you are a 01:21:14.130 --> 01:21:17.570 align:start position:0% Suri's and it's simile if you are a dataset<01:21:14.730> provider<01:21:15.710> since<01:21:16.710> our<01:21:16.950> platform<01:21:17.490> is 01:21:17.570 --> 01:21:17.580 align:start position:0% dataset provider since our platform is 01:21:17.580 --> 01:21:19.550 align:start position:0% dataset provider since our platform is blockchain<01:21:18.060> belched<01:21:18.390> so<01:21:18.720> all<01:21:18.900> this<01:21:19.110> data<01:21:19.320> as 01:21:19.550 --> 01:21:19.560 align:start position:0% blockchain belched so all this data as 01:21:19.560 --> 01:21:20.990 align:start position:0% blockchain belched so all this data as applications<01:21:20.220> running<01:21:20.610> on<01:21:20.820> the 01:21:20.990 --> 01:21:21.000 align:start position:0% applications running on the 01:21:21.000 --> 01:21:23.480 align:start position:0% applications running on the decentralized<01:21:21.450> networks<01:21:22.080> so<01:21:22.830> thanks<01:21:23.190> to<01:21:23.220> this 01:21:23.480 --> 01:21:23.490 align:start position:0% decentralized networks so thanks to this 01:21:23.490 --> 01:21:26.210 align:start position:0% decentralized networks so thanks to this end-to-end<01:21:23.970> protection<01:21:24.780> the<01:21:25.470> application 01:21:26.210 --> 01:21:26.220 align:start position:0% end-to-end protection the application 01:21:26.220 --> 01:21:29.990 align:start position:0% end-to-end protection the application and<01:21:26.400> data<01:21:26.670> service<01:21:27.150> can<01:21:27.660> be<01:21:28.050> monetizable<01:21:28.980> in<01:21:29.790> a 01:21:29.990 --> 01:21:30.000 align:start position:0% and data service can be monetizable in a 01:21:30.000 --> 01:21:32.450 align:start position:0% and data service can be monetizable in a secure<01:21:30.390> way<01:21:30.540> via<01:21:30.870> our<01:21:31.110> Isaac<01:21:31.770> decentralized 01:21:32.450 --> 01:21:32.460 align:start position:0% secure way via our Isaac decentralized 01:21:32.460 --> 01:21:36.050 align:start position:0% secure way via our Isaac decentralized platform<01:21:33.260> so<01:21:34.260> the<01:21:34.740> for<01:21:35.040> data<01:21:35.280> protection<01:21:35.760> and 01:21:36.050 --> 01:21:36.060 align:start position:0% platform so the for data protection and 01:21:36.060 --> 01:21:39.740 align:start position:0% platform so the for data protection and a<01:21:36.210> trusted<01:21:36.780> execution<01:21:37.050> is<01:21:37.950> a<01:21:38.280> must<01:21:38.580> is<01:21:38.820> a<01:21:39.330> must 01:21:39.740 --> 01:21:39.750 align:start position:0% a trusted execution is a must is a must 01:21:39.750 --> 01:21:43.480 align:start position:0% a trusted execution is a must is a must for<01:21:40.110> Isaac<01:21:40.740> platform<01:21:41.250> and<01:21:41.820> blockchain<01:21:42.210> based 01:21:43.480 --> 01:21:43.490 align:start position:0% for Isaac platform and blockchain based 01:21:43.490 --> 01:21:49.910 align:start position:0% for Isaac platform and blockchain based approach<01:21:44.490> and<01:21:44.670> based<01:21:44.880> computing<01:21:47.900> okay<01:21:48.900> so<01:21:49.500> I 01:21:49.910 --> 01:21:49.920 align:start position:0% approach and based computing okay so I 01:21:49.920 --> 01:21:53.120 align:start position:0% approach and based computing okay so I just<01:21:50.220> talked<01:21:50.670> about<01:21:51.230> what<01:21:52.230> is<01:21:52.500> interest 01:21:53.120 --> 01:21:53.130 align:start position:0% just talked about what is interest 01:21:53.130 --> 01:21:56.870 align:start position:0% just talked about what is interest reacts<01:21:53.640> I<01:21:54.000> also<01:21:54.720> talked<01:21:55.110> about<01:21:55.580> what<01:21:56.580> is 01:21:56.870 --> 01:21:56.880 align:start position:0% reacts I also talked about what is 01:21:56.880 --> 01:22:00.460 align:start position:0% reacts I also talked about what is entering<01:21:57.450> data<01:21:57.690> protection<01:21:58.200> and<01:21:59.060> why<01:22:00.060> the 01:22:00.460 --> 01:22:00.470 align:start position:0% entering data protection and why the 01:22:00.470 --> 01:22:02.780 align:start position:0% entering data protection and why the end-to-end<01:22:01.470> data<01:22:01.800> protection<01:22:02.310> trust 01:22:02.780 --> 01:22:02.790 align:start position:0% end-to-end data protection trust 01:22:02.790 --> 01:22:05.180 align:start position:0% end-to-end data protection trust execution<01:22:03.390> is<01:22:03.480> so<01:22:03.600> important<01:22:04.230> to<01:22:04.710> Isaac 01:22:05.180 --> 01:22:05.190 align:start position:0% execution is so important to Isaac 01:22:05.190 --> 01:22:07.160 align:start position:0% execution is so important to Isaac platform<01:22:05.760> and<01:22:06.030> to<01:22:06.540> blockchain<01:22:06.960> based 01:22:07.160 --> 01:22:07.170 align:start position:0% platform and to blockchain based 01:22:07.170 --> 01:22:10.190 align:start position:0% platform and to blockchain based computing<01:22:07.760> so<01:22:08.760> here's<01:22:09.030> our<01:22:09.210> solution<01:22:09.420> our 01:22:10.190 --> 01:22:10.200 align:start position:0% computing so here's our solution our 01:22:10.200 --> 01:22:12.470 align:start position:0% computing so here's our solution our solution<01:22:10.560> which<01:22:11.070> is<01:22:11.220> based<01:22:11.460> on<01:22:11.700> Intel<01:22:12.090> SGX 01:22:12.470 --> 01:22:12.480 align:start position:0% solution which is based on Intel SGX 01:22:12.480 --> 01:22:15.890 align:start position:0% solution which is based on Intel SGX solution<01:22:13.260> as<01:22:13.770> technology<01:22:14.610> which<01:22:15.180> provides 01:22:15.890 --> 01:22:15.900 align:start position:0% solution as technology which provides 01:22:15.900 --> 01:22:19.310 align:start position:0% solution as technology which provides end-to-end<01:22:16.830> data<01:22:17.400> protection<01:22:17.970> for<01:22:18.780> Isaac 01:22:19.310 --> 01:22:19.320 align:start position:0% end-to-end data protection for Isaac 01:22:19.320 --> 01:22:21.860 align:start position:0% end-to-end data protection for Isaac platform<01:22:19.980> and<01:22:20.370> a<01:22:20.910> blockchain<01:22:21.360> based 01:22:21.860 --> 01:22:21.870 align:start position:0% platform and a blockchain based 01:22:21.870 --> 01:22:24.740 align:start position:0% platform and a blockchain based computing<01:22:22.610> so<01:22:23.610> our<01:22:23.790> solution<01:22:24.330> firstly 01:22:24.740 --> 01:22:24.750 align:start position:0% computing so our solution firstly 01:22:24.750 --> 01:22:27.530 align:start position:0% computing so our solution firstly provides<01:22:25.560> a<01:22:25.800> full<01:22:26.160> data<01:22:26.460> protection<01:22:26.970> covering 01:22:27.530 --> 01:22:27.540 align:start position:0% provides a full data protection covering 01:22:27.540 --> 01:22:28.670 align:start position:0% provides a full data protection covering application<01:22:28.050> portator 01:22:28.670 --> 01:22:28.680 align:start position:0% application portator 01:22:28.680 --> 01:22:31.130 align:start position:0% application portator application<01:22:29.610> embedded<01:22:30.120> data<01:22:30.360> of<01:22:30.630> an 01:22:31.130 --> 01:22:31.140 align:start position:0% application embedded data of an 01:22:31.140 --> 01:22:34.340 align:start position:0% application embedded data of an application<01:22:31.560> output<01:22:32.190> data<01:22:32.600> so<01:22:33.600> protecting 01:22:34.340 --> 01:22:34.350 align:start position:0% application output data so protecting 01:22:34.350 --> 01:22:36.560 align:start position:0% application output data so protecting these<01:22:34.500> application<01:22:35.160> data<01:22:35.400> running<01:22:36.240> on<01:22:36.390> the 01:22:36.560 --> 01:22:36.570 align:start position:0% these application data running on the 01:22:36.570 --> 01:22:40.280 align:start position:0% these application data running on the decentralized<01:22:37.230> networks<01:22:38.540> secondly<01:22:39.540> our 01:22:40.280 --> 01:22:40.290 align:start position:0% decentralized networks secondly our 01:22:40.290 --> 01:22:43.010 align:start position:0% decentralized networks secondly our solution<01:22:40.860> allows<01:22:41.280> to<01:22:41.640> make<01:22:42.000> sure<01:22:42.360> the 01:22:43.010 --> 01:22:43.020 align:start position:0% solution allows to make sure the 01:22:43.020 --> 01:22:45.980 align:start position:0% solution allows to make sure the corrected<01:22:43.860> applications<01:22:44.640> are<01:22:45.000> correctly 01:22:45.980 --> 01:22:45.990 align:start position:0% corrected applications are correctly 01:22:45.990 --> 01:22:49.280 align:start position:0% corrected applications are correctly execute<01:22:46.640> executed<01:22:47.640> and<01:22:47.850> the<01:22:48.420> execution<01:22:49.050> are 01:22:49.280 --> 01:22:49.290 align:start position:0% execute executed and the execution are 01:22:49.290 --> 01:22:52.970 align:start position:0% execute executed and the execution are neither<01:22:49.710> tempered<01:22:50.490> nor<01:22:51.380> interrupted<01:22:52.380> by<01:22:52.620> any 01:22:52.970 --> 01:22:52.980 align:start position:0% neither tempered nor interrupted by any 01:22:52.980 --> 01:22:54.530 align:start position:0% neither tempered nor interrupted by any malicious<01:22:53.640> attackers 01:22:54.530 --> 01:22:54.540 align:start position:0% malicious attackers 01:22:54.540 --> 01:22:59.240 align:start position:0% malicious attackers so<01:22:55.260> basically<01:22:55.620> we<01:22:56.580> assure<01:22:57.030> user<01:22:58.250> imperative 01:22:59.240 --> 01:22:59.250 align:start position:0% so basically we assure user imperative 01:22:59.250 --> 01:23:02.150 align:start position:0% so basically we assure user imperative you<01:22:59.520> decide<01:22:59.850> we<01:23:00.390> can<01:23:00.420> assure<01:23:00.690> you<01:23:00.930> that<01:23:01.170> the 01:23:02.150 --> 01:23:02.160 align:start position:0% you decide we can assure you that the 01:23:02.160 --> 01:23:05.390 align:start position:0% you decide we can assure you that the two<01:23:02.280> points<01:23:02.670> the<01:23:03.150> first<01:23:03.360> point<01:23:03.510> well<01:23:04.410> this<01:23:05.130> is 01:23:05.390 --> 01:23:05.400 align:start position:0% two points the first point well this is 01:23:05.400 --> 01:23:08.300 align:start position:0% two points the first point well this is actually<01:23:06.000> the<01:23:06.300> expected<01:23:07.170> application<01:23:07.890> the 01:23:08.300 --> 01:23:08.310 align:start position:0% actually the expected application the 01:23:08.310 --> 01:23:10.460 align:start position:0% actually the expected application the correct<01:23:08.700> application<01:23:08.910> that<01:23:09.600> is<01:23:09.750> actually 01:23:10.460 --> 01:23:10.470 align:start position:0% correct application that is actually 01:23:10.470 --> 01:23:12.760 align:start position:0% correct application that is actually running<01:23:10.820> the<01:23:11.820> second<01:23:12.180> point 01:23:12.760 --> 01:23:12.770 align:start position:0% running the second point 01:23:12.770 --> 01:23:15.890 align:start position:0% running the second point these<01:23:13.770> applications<01:23:14.130> are<01:23:14.850> correctly<01:23:15.480> running 01:23:15.890 --> 01:23:15.900 align:start position:0% these applications are correctly running 01:23:15.900 --> 01:23:18.770 align:start position:0% these applications are correctly running is<01:23:16.050> neither<01:23:16.590> tempered<01:23:17.310> nor<01:23:17.850> interrupted<01:23:18.510> by 01:23:18.770 --> 01:23:18.780 align:start position:0% is neither tempered nor interrupted by 01:23:18.780 --> 01:23:22.700 align:start position:0% is neither tempered nor interrupted by any<01:23:19.080> other<01:23:19.350> malicious<01:23:20.100> attackers<01:23:20.640> and<01:23:21.710> our 01:23:22.700 --> 01:23:22.710 align:start position:0% any other malicious attackers and our 01:23:22.710 --> 01:23:24.979 align:start position:0% any other malicious attackers and our solution<01:23:23.250> is<01:23:23.610> based<01:23:23.970> on<01:23:24.150> Scone<01:23:24.510> framework 01:23:24.979 --> 01:23:24.989 align:start position:0% solution is based on Scone framework 01:23:24.989 --> 01:23:29.030 align:start position:0% solution is based on Scone framework so<01:23:26.090> we're<01:23:27.090> currently<01:23:27.300> working<01:23:27.830> closely<01:23:28.830> with 01:23:29.030 --> 01:23:29.040 align:start position:0% so we're currently working closely with 01:23:29.040 --> 01:23:33.940 align:start position:0% so we're currently working closely with contain<01:23:29.700> to<01:23:30.270> push<01:23:30.510> for<01:23:30.840> to<01:23:31.410> push<01:23:31.650> for<01:23:31.920> this<01:23:32.360> our 01:23:33.940 --> 01:23:33.950 align:start position:0% contain to push for to push for this our 01:23:33.950 --> 01:23:36.380 align:start position:0% contain to push for to push for this our extract<01:23:34.950> solution<01:23:35.370> based<01:23:35.610> on<01:23:35.730> us<01:23:35.910> conferring 01:23:36.380 --> 01:23:36.390 align:start position:0% extract solution based on us conferring 01:23:36.390 --> 01:23:38.870 align:start position:0% extract solution based on us conferring work<01:23:36.540> and<01:23:37.170> our<01:23:37.800> solution<01:23:38.280> is<01:23:38.370> also<01:23:38.550> EA 01:23:38.870 --> 01:23:38.880 align:start position:0% work and our solution is also EA 01:23:38.880 --> 01:23:42.170 align:start position:0% work and our solution is also EA compatible<01:23:39.630> which<01:23:39.989> leverage<01:23:40.469> EA<01:23:41.370> trusted 01:23:42.170 --> 01:23:42.180 align:start position:0% compatible which leverage EA trusted 01:23:42.180 --> 01:23:44.450 align:start position:0% compatible which leverage EA trusted computing<01:23:42.620> specification<01:23:43.620> so<01:23:44.070> which<01:23:44.250> was 01:23:44.450 --> 01:23:44.460 align:start position:0% computing specification so which was 01:23:44.460 --> 01:23:49.070 align:start position:0% computing specification so which was just<01:23:44.730> released<01:23:45.150> several<01:23:45.570> days<01:23:45.840> ago<01:23:47.270> so<01:23:48.270> and 01:23:49.070 --> 01:23:49.080 align:start position:0% just released several days ago so and 01:23:49.080 --> 01:23:52.280 align:start position:0% just released several days ago so and this<01:23:49.650> EA<01:23:49.950> trusted<01:23:50.790> computing<01:23:51.290> specification 01:23:52.280 --> 01:23:52.290 align:start position:0% this EA trusted computing specification 01:23:52.290 --> 01:23:55.280 align:start position:0% this EA trusted computing specification we<01:23:52.680> believe<01:23:52.980> it's<01:23:53.520> a<01:23:53.850> milestone<01:23:54.239> for<01:23:54.719> the 01:23:55.280 --> 01:23:55.290 align:start position:0% we believe it's a milestone for the 01:23:55.290 --> 01:23:57.770 align:start position:0% we believe it's a milestone for the easier<01:23:55.680> own<01:23:55.800> community<01:23:56.460> to<01:23:56.640> support<01:23:57.270> the 01:23:57.770 --> 01:23:57.780 align:start position:0% easier own community to support the 01:23:57.780 --> 01:24:03.080 align:start position:0% easier own community to support the trusted<01:23:58.350> computing<01:24:01.190> ok<01:24:02.190> so<01:24:02.460> here<01:24:02.850> is<01:24:03.060> a 01:24:03.080 --> 01:24:03.090 align:start position:0% trusted computing ok so here is a 01:24:03.090 --> 01:24:05.690 align:start position:0% trusted computing ok so here is a workflow<01:24:03.600> of<01:24:04.020> our<01:24:04.320> Isaac<01:24:05.070> and<01:24:05.340> to<01:24:05.550> Anna 01:24:05.690 --> 01:24:05.700 align:start position:0% workflow of our Isaac and to Anna 01:24:05.700 --> 01:24:08.900 align:start position:0% workflow of our Isaac and to Anna trusted<01:24:06.360> exclusion<01:24:07.010> with<01:24:08.010> interest<01:24:08.580> reacts 01:24:08.900 --> 01:24:08.910 align:start position:0% trusted exclusion with interest reacts 01:24:08.910 --> 01:24:12.010 align:start position:0% trusted exclusion with interest reacts so<01:24:09.510> principle<01:24:10.110> principle<01:24:10.980> it<01:24:11.160> contains<01:24:11.670> three 01:24:12.010 --> 01:24:12.020 align:start position:0% so principle principle it contains three 01:24:12.020 --> 01:24:15.709 align:start position:0% so principle principle it contains three steps<01:24:13.020> the<01:24:13.710> first<01:24:13.890> step<01:24:14.120> focus<01:24:15.120> on<01:24:15.300> the<01:24:15.420> user 01:24:15.709 --> 01:24:15.719 align:start position:0% steps the first step focus on the user 01:24:15.719 --> 01:24:18.440 align:start position:0% steps the first step focus on the user input<01:24:16.170> data<01:24:16.320> encryption<01:24:16.860> so<01:24:17.790> remember<01:24:18.239> what<01:24:18.420> I 01:24:18.440 --> 01:24:18.450 align:start position:0% input data encryption so remember what I 01:24:18.450 --> 01:24:21.350 align:start position:0% input data encryption so remember what I talked<01:24:18.750> about<01:24:18.780> the<01:24:19.230> end-to-end<01:24:20.360> data 01:24:21.350 --> 01:24:21.360 align:start position:0% talked about the end-to-end data 01:24:21.360 --> 01:24:22.100 align:start position:0% talked about the end-to-end data protection 01:24:22.100 --> 01:24:22.110 align:start position:0% protection 01:24:22.110 --> 01:24:24.440 align:start position:0% protection so<01:24:22.739> if<01:24:23.040> basically<01:24:23.700> if<01:24:23.760> you<01:24:24.000> don't<01:24:24.150> want<01:24:24.330> to 01:24:24.440 --> 01:24:24.450 align:start position:0% so if basically if you don't want to 01:24:24.450 --> 01:24:26.840 align:start position:0% so if basically if you don't want to trick<01:24:24.660> at<01:24:24.870> the<01:24:24.930> centralized<01:24:25.500> applications<01:24:26.280> so 01:24:26.840 --> 01:24:26.850 align:start position:0% trick at the centralized applications so 01:24:26.850 --> 01:24:29.120 align:start position:0% trick at the centralized applications so firstly<01:24:27.210> user<01:24:27.989> import<01:24:28.350> data<01:24:28.530> has<01:24:28.860> to<01:24:28.890> be 01:24:29.120 --> 01:24:29.130 align:start position:0% firstly user import data has to be 01:24:29.130 --> 01:24:31.790 align:start position:0% firstly user import data has to be protected<01:24:29.910> has<01:24:30.330> to<01:24:30.570> be<01:24:30.690> strictly<01:24:31.140> encrypted 01:24:31.790 --> 01:24:31.800 align:start position:0% protected has to be strictly encrypted 01:24:31.800 --> 01:24:36.590 align:start position:0% protected has to be strictly encrypted and<01:24:31.920> protected<01:24:32.239> so<01:24:33.239> the<01:24:33.719> step<01:24:33.989> 1<01:24:34.290> the<01:24:35.130> user<01:24:35.600> the 01:24:36.590 --> 01:24:36.600 align:start position:0% and protected so the step 1 the user the 01:24:36.600 --> 01:24:40.400 align:start position:0% and protected so the step 1 the user the user<01:24:36.630> input<01:24:37.320> data<01:24:37.560> is<01:24:38.060> strictly<01:24:39.170> encrypted<01:24:40.170> at 01:24:40.400 --> 01:24:40.410 align:start position:0% user input data is strictly encrypted at 01:24:40.410 --> 01:24:43.400 align:start position:0% user input data is strictly encrypted at the<01:24:40.830> you<01:24:41.010> decide<01:24:41.489> with<01:24:42.330> the<01:24:42.360> user<01:24:42.930> generated 01:24:43.400 --> 01:24:43.410 align:start position:0% the you decide with the user generated 01:24:43.410 --> 01:24:47.720 align:start position:0% the you decide with the user generated secret<01:24:44.160> kings<01:24:44.460> and<01:24:44.900> the<01:24:45.900> you<01:24:46.380> the<01:24:46.730> crate 01:24:47.720 --> 01:24:47.730 align:start position:0% secret kings and the you the crate 01:24:47.730 --> 01:24:49.580 align:start position:0% secret kings and the you the crate encrypted<01:24:48.300> you<01:24:48.420> the<01:24:48.570> import<01:24:48.810> data<01:24:48.930> can<01:24:49.560> then 01:24:49.580 --> 01:24:49.590 align:start position:0% encrypted you the import data can then 01:24:49.590 --> 01:24:52.070 align:start position:0% encrypted you the import data can then be<01:24:49.770> transferred<01:24:50.700> to<01:24:50.760> the<01:24:51.270> remote<01:24:51.780> filesystem 01:24:52.070 --> 01:24:52.080 align:start position:0% be transferred to the remote filesystem 01:24:52.080 --> 01:24:55.520 align:start position:0% be transferred to the remote filesystem and<01:24:52.680> the<01:24:53.340> secret<01:24:53.940> king<01:24:54.180> can<01:24:54.420> also<01:24:54.570> updated<01:24:55.320> to 01:24:55.520 --> 01:24:55.530 align:start position:0% and the secret king can also updated to 01:24:55.530 --> 01:24:57.620 align:start position:0% and the secret king can also updated to the<01:24:55.620> secret<01:24:55.980> management<01:24:56.550> service<01:24:56.940> which<01:24:57.450> is 01:24:57.620 --> 01:24:57.630 align:start position:0% the secret management service which is 01:24:57.630 --> 01:25:02.270 align:start position:0% the secret management service which is also<01:24:57.930> as<01:24:58.290> G<01:24:58.739> X<01:24:58.890> based<01:24:59.219> in<01:25:00.440> first<01:25:01.440> step<01:25:01.680> 2 01:25:02.270 --> 01:25:02.280 align:start position:0% also as G X based in first step 2 01:25:02.280 --> 01:25:05.360 align:start position:0% also as G X based in first step 2 the<01:25:02.790> user<01:25:03.120> is<01:25:03.540> able<01:25:03.989> to<01:25:04.200> trigger<01:25:04.680> the<01:25:05.190> off 01:25:05.360 --> 01:25:05.370 align:start position:0% the user is able to trigger the off 01:25:05.370 --> 01:25:08.240 align:start position:0% the user is able to trigger the off chain<01:25:06.350> applications<01:25:07.350> running<01:25:07.860> on<01:25:08.100> the 01:25:08.240 --> 01:25:08.250 align:start position:0% chain applications running on the 01:25:08.250 --> 01:25:13.400 align:start position:0% chain applications running on the decentralized<01:25:08.700> node<01:25:09.920> so<01:25:11.600> these<01:25:12.600> 3<01:25:12.900> you<01:25:13.200> that 01:25:13.400 --> 01:25:13.410 align:start position:0% decentralized node so these 3 you that 01:25:13.410 --> 01:25:15.110 align:start position:0% decentralized node so these 3 you that can<01:25:13.530> trigger<01:25:13.739> this<01:25:13.920> obtain<01:25:14.489> computing<01:25:14.969> via 01:25:15.110 --> 01:25:15.120 align:start position:0% can trigger this obtain computing via 01:25:15.120 --> 01:25:17.209 align:start position:0% can trigger this obtain computing via our<01:25:15.300> Isaac<01:25:15.660> marketplace<01:25:16.260> which<01:25:16.800> is<01:25:17.010> also 01:25:17.209 --> 01:25:17.219 align:start position:0% our Isaac marketplace which is also 01:25:17.219 --> 01:25:20.300 align:start position:0% our Isaac marketplace which is also based<01:25:17.550> on<01:25:17.820> the<01:25:17.969> blockchain<01:25:18.510> introduction<01:25:19.320> so 01:25:20.300 --> 01:25:20.310 align:start position:0% based on the blockchain introduction so 01:25:20.310 --> 01:25:22.370 align:start position:0% based on the blockchain introduction so as<01:25:20.489> soon<01:25:20.700> as<01:25:20.760> the<01:25:21.210> of<01:25:21.450> chain<01:25:21.719> application 01:25:22.370 --> 01:25:22.380 align:start position:0% as soon as the of chain application 01:25:22.380 --> 01:25:24.680 align:start position:0% as soon as the of chain application starts<01:25:22.739> running<01:25:23.160> at<01:25:23.340> the<01:25:24.060> decentralize 01:25:24.680 --> 01:25:24.690 align:start position:0% starts running at the decentralize 01:25:24.690 --> 01:25:27.860 align:start position:0% starts running at the decentralize denude<01:25:25.520> SGX<01:25:26.520> Babel<01:25:26.969> is<01:25:27.150> automatically 01:25:27.860 --> 01:25:27.870 align:start position:0% denude SGX Babel is automatically 01:25:27.870 --> 01:25:30.200 align:start position:0% denude SGX Babel is automatically created<01:25:28.469> to<01:25:28.950> protect<01:25:29.520> the<01:25:29.940> Ronnie 01:25:30.200 --> 01:25:30.210 align:start position:0% created to protect the Ronnie 01:25:30.210 --> 01:25:33.740 align:start position:0% created to protect the Ronnie application<01:25:30.930> so<01:25:31.830> firstly<01:25:32.280> the<01:25:32.880> application 01:25:33.740 --> 01:25:33.750 align:start position:0% application so firstly the application 01:25:33.750 --> 01:25:36.860 align:start position:0% application so firstly the application will<01:25:33.930> retrieve<01:25:34.500> the<01:25:34.920> user<01:25:35.600> encrypted<01:25:36.600> data 01:25:36.860 --> 01:25:36.870 align:start position:0% will retrieve the user encrypted data 01:25:36.870 --> 01:25:38.959 align:start position:0% will retrieve the user encrypted data from<01:25:37.710> the<01:25:37.890> remote<01:25:38.219> filesystem 01:25:38.959 --> 01:25:38.969 align:start position:0% from the remote filesystem 01:25:38.969 --> 01:25:42.890 align:start position:0% from the remote filesystem and<01:25:39.410> then<01:25:40.760> application<01:25:41.760> we<01:25:41.850> also<01:25:41.880> pull<01:25:42.570> the 01:25:42.890 --> 01:25:42.900 align:start position:0% and then application we also pull the 01:25:42.900 --> 01:25:45.890 align:start position:0% and then application we also pull the secret<01:25:43.590> Kings<01:25:43.949> from<01:25:44.370> the<01:25:44.550> s3x<01:25:45.330> management 01:25:45.890 --> 01:25:45.900 align:start position:0% secret Kings from the s3x management 01:25:45.900 --> 01:25:48.320 align:start position:0% secret Kings from the s3x management service<01:25:46.260> via<01:25:46.680> high-security<01:25:47.310> channel<01:25:47.880> so 01:25:48.320 --> 01:25:48.330 align:start position:0% service via high-security channel so 01:25:48.330 --> 01:25:51.740 align:start position:0% service via high-security channel so which<01:25:49.170> is<01:25:49.320> called<01:25:49.860> s3x<01:25:50.790> provision<01:25:51.390> channel 01:25:51.740 --> 01:25:51.750 align:start position:0% which is called s3x provision channel 01:25:51.750 --> 01:25:57.050 align:start position:0% which is called s3x provision channel and<01:25:53.150> then<01:25:54.150> the<01:25:54.690> this<01:25:55.020> squad<01:25:55.350> King<01:25:55.760> allows<01:25:56.760> to 01:25:57.050 --> 01:25:57.060 align:start position:0% and then the this squad King allows to 01:25:57.060 --> 01:26:00.939 align:start position:0% and then the this squad King allows to decrypt<01:25:57.660> the<01:25:58.260> user<01:25:58.590> import<01:25:59.430> data<01:25:59.610> inside<01:26:00.449> this 01:26:00.939 --> 01:26:00.949 align:start position:0% decrypt the user import data inside this 01:26:00.949 --> 01:26:04.970 align:start position:0% decrypt the user import data inside this SGX<01:26:01.949> Enclave<01:26:02.520> and<01:26:02.790> as<01:26:03.719> the<01:26:03.840> decrypted<01:26:04.500> data<01:26:04.530> is 01:26:04.970 --> 01:26:04.980 align:start position:0% SGX Enclave and as the decrypted data is 01:26:04.980 --> 01:26:07.820 align:start position:0% SGX Enclave and as the decrypted data is used<01:26:05.610> to<01:26:05.850> feed<01:26:06.180> the<01:26:06.660> application<01:26:07.350> execution 01:26:07.820 --> 01:26:07.830 align:start position:0% used to feed the application execution 01:26:07.830 --> 01:26:10.720 align:start position:0% used to feed the application execution and<01:26:08.390> when<01:26:09.390> application<01:26:09.960> finishes<01:26:10.410> running 01:26:10.720 --> 01:26:10.730 align:start position:0% and when application finishes running 01:26:10.730 --> 01:26:15.220 align:start position:0% and when application finishes running the<01:26:11.730> output<01:26:12.270> is<01:26:12.510> also<01:26:13.310> encrypted<01:26:14.310> inside 01:26:15.220 --> 01:26:15.230 align:start position:0% the output is also encrypted inside 01:26:15.230 --> 01:26:20.990 align:start position:0% the output is also encrypted inside these<01:26:16.580> SGX<01:26:17.580> Enclave<01:26:18.030> and<01:26:18.290> a<01:26:20.000> execution 01:26:20.990 --> 01:26:21.000 align:start position:0% these SGX Enclave and a execution 01:26:21.000 --> 01:26:24.140 align:start position:0% these SGX Enclave and a execution attestation<01:26:21.480> is<01:26:21.900> also<01:26:22.530> provided<01:26:23.370> inside<01:26:23.820> this 01:26:24.140 --> 01:26:24.150 align:start position:0% attestation is also provided inside this 01:26:24.150 --> 01:26:28.520 align:start position:0% attestation is also provided inside this s3x<01:26:24.780> Enclave<01:26:25.730> so<01:26:26.730> the<01:26:26.910> step<01:26:27.150> 3<01:26:27.449> finally<01:26:28.260> the 01:26:28.520 --> 01:26:28.530 align:start position:0% s3x Enclave so the step 3 finally the 01:26:28.530 --> 01:26:31.490 align:start position:0% s3x Enclave so the step 3 finally the user<01:26:28.770> can<01:26:29.250> just<01:26:29.280> download<01:26:29.640> the<01:26:30.510> application 01:26:31.490 --> 01:26:31.500 align:start position:0% user can just download the application 01:26:31.500 --> 01:26:35.630 align:start position:0% user can just download the application out<01:26:31.650> port<01:26:32.010> which<01:26:32.850> is<01:26:33.060> encrypted<01:26:33.800> inside<01:26:34.800> these 01:26:35.630 --> 01:26:35.640 align:start position:0% out port which is encrypted inside these 01:26:35.640 --> 01:26:40.189 align:start position:0% out port which is encrypted inside these sjx<01:26:36.350> Enclave<01:26:37.350> and<01:26:37.699> I<01:26:38.699> want<01:26:39.270> to<01:26:39.360> underline<01:26:39.570> that 01:26:40.189 --> 01:26:40.199 align:start position:0% sjx Enclave and I want to underline that 01:26:40.199 --> 01:26:42.439 align:start position:0% sjx Enclave and I want to underline that only<01:26:40.590> the<01:26:40.800> corresponding<01:26:41.100> user<01:26:41.699> is<01:26:41.940> able<01:26:42.239> to 01:26:42.439 --> 01:26:42.449 align:start position:0% only the corresponding user is able to 01:26:42.449 --> 01:26:44.540 align:start position:0% only the corresponding user is able to download<01:26:42.989> that<01:26:43.320> port<01:26:43.680> and<01:26:43.890> only<01:26:44.460> the 01:26:44.540 --> 01:26:44.550 align:start position:0% download that port and only the 01:26:44.550 --> 01:26:46.880 align:start position:0% download that port and only the corresponding<01:26:45.090> user<01:26:45.449> is<01:26:45.660> able<01:26:46.080> to<01:26:46.260> decrypt 01:26:46.880 --> 01:26:46.890 align:start position:0% corresponding user is able to decrypt 01:26:46.890 --> 01:26:52.310 align:start position:0% corresponding user is able to decrypt the<01:26:47.489> application<01:26:48.000> or<01:26:48.150> port<01:26:50.150> so<01:26:51.150> I<01:26:51.449> would<01:26:52.110> like 01:26:52.310 --> 01:26:52.320 align:start position:0% the application or port so I would like 01:26:52.320 --> 01:26:57.500 align:start position:0% the application or port so I would like to<01:26:52.560> show<01:26:52.800> a<01:26:52.830> demo<01:26:53.239> let's<01:26:54.239> see<01:26:54.480> you<01:26:54.650> ok<01:26:55.650> ok<01:26:56.520> so 01:26:57.500 --> 01:26:57.510 align:start position:0% to show a demo let's see you ok ok so 01:26:57.510 --> 01:27:06.620 align:start position:0% to show a demo let's see you ok ok so basically<01:26:58.440> this<01:26:59.219> is<01:26:59.550> a<01:27:03.199> ok<01:27:04.199> so<01:27:04.260> actually<01:27:05.630> this 01:27:06.620 --> 01:27:06.630 align:start position:0% basically this is a ok so actually this 01:27:06.630 --> 01:27:11.900 align:start position:0% basically this is a ok so actually this demo<01:27:06.989> is<01:27:07.230> based<01:27:07.469> on<01:27:07.739> the<01:27:09.590> 3d<01:27:10.590> rendering<01:27:11.219> plant 01:27:11.900 --> 01:27:11.910 align:start position:0% demo is based on the 3d rendering plant 01:27:11.910 --> 01:27:14.720 align:start position:0% demo is based on the 3d rendering plant applications<01:27:12.080> so<01:27:13.080> this<01:27:13.350> demo<01:27:13.680> can<01:27:14.400> show<01:27:14.670> you 01:27:14.720 --> 01:27:14.730 align:start position:0% applications so this demo can show you 01:27:14.730 --> 01:27:19.420 align:start position:0% applications so this demo can show you show<01:27:15.480> the<01:27:15.630> user<01:27:15.989> how<01:27:16.620> to<01:27:17.489> use<01:27:17.730> our<01:27:17.969> h3x 01:27:19.420 --> 01:27:19.430 align:start position:0% show the user how to use our h3x 01:27:19.430 --> 01:27:22.250 align:start position:0% show the user how to use our h3x solution<01:27:20.430> to<01:27:20.910> protect<01:27:21.120> protect<01:27:21.630> you<01:27:22.110> the 01:27:22.250 --> 01:27:22.260 align:start position:0% solution to protect protect you the 01:27:22.260 --> 01:27:25.220 align:start position:0% solution to protect protect you the Imperator<01:27:22.590> an<01:27:22.980> output<01:27:23.730> data<01:27:23.910> and<01:27:24.300> provide<01:27:25.199> a 01:27:25.220 --> 01:27:25.230 align:start position:0% Imperator an output data and provide a 01:27:25.230 --> 01:27:28.850 align:start position:0% Imperator an output data and provide a full<01:27:25.739> data<01:27:25.949> protections<01:27:26.690> so<01:27:27.690> firstly<01:27:28.350> user 01:27:28.850 --> 01:27:28.860 align:start position:0% full data protections so firstly user 01:27:28.860 --> 01:27:31.459 align:start position:0% full data protections so firstly user only<01:27:29.160> needs<01:27:29.310> to<01:27:29.670> run<01:27:30.000> a<01:27:30.030> simple<01:27:30.600> command<01:27:30.870> the 01:27:31.459 --> 01:27:31.469 align:start position:0% only needs to run a simple command the 01:27:31.469 --> 01:27:34.160 align:start position:0% only needs to run a simple command the Isaac<01:27:31.890> T<01:27:32.190> in<01:27:32.550> it<01:27:32.670> which<01:27:33.000> allows<01:27:33.120> to<01:27:33.300> initialize 01:27:34.160 --> 01:27:34.170 align:start position:0% Isaac T in it which allows to initialize 01:27:34.170 --> 01:27:38.360 align:start position:0% Isaac T in it which allows to initialize s3x<01:27:34.980> project<01:27:35.610> and<01:27:35.880> then<01:27:36.840> the<01:27:37.199> user<01:27:37.410> just<01:27:38.219> a 01:27:38.360 --> 01:27:38.370 align:start position:0% s3x project and then the user just a 01:27:38.370 --> 01:27:40.910 align:start position:0% s3x project and then the user just a copy<01:27:38.790> heal<01:27:39.360> you<01:27:39.600> the<01:27:39.780> import<01:27:40.110> data<01:27:40.199> to<01:27:40.890> a 01:27:40.910 --> 01:27:40.920 align:start position:0% copy heal you the import data to a 01:27:40.920 --> 01:27:44.630 align:start position:0% copy heal you the import data to a specific<01:27:41.550> specific<01:27:42.150> folder<01:27:43.140> which<01:27:43.770> is<01:27:43.800> te 01:27:44.630 --> 01:27:44.640 align:start position:0% specific specific folder which is te 01:27:44.640 --> 01:27:46.280 align:start position:0% specific specific folder which is te imports 01:27:46.280 --> 01:27:46.290 align:start position:0% imports 01:27:46.290 --> 01:27:48.530 align:start position:0% imports and<01:27:46.410> the<01:27:46.920> user<01:27:47.280> runs<01:27:47.670> a<01:27:47.850> very<01:27:48.030> simple<01:27:48.390> command 01:27:48.530 --> 01:27:48.540 align:start position:0% and the user runs a very simple command 01:27:48.540 --> 01:27:51.680 align:start position:0% and the user runs a very simple command which<01:27:49.290> is<01:27:49.470> that<01:27:49.680> he<01:27:49.860> Issac<01:27:50.580> te<01:27:50.760> encrypt<01:27:51.360> post 01:27:51.680 --> 01:27:51.690 align:start position:0% which is that he Issac te encrypt post 01:27:51.690 --> 01:27:54.130 align:start position:0% which is that he Issac te encrypt post so<01:27:52.230> basically<01:27:52.590> this<01:27:52.950> command<01:27:53.310> course 01:27:54.130 --> 01:27:54.140 align:start position:0% so basically this command course 01:27:54.140 --> 01:27:57.470 align:start position:0% so basically this command course represents<01:27:55.140> the<01:27:55.260> step<01:27:55.560> one<01:27:55.890> of<01:27:56.130> our<01:27:56.910> workflow 01:27:57.470 --> 01:27:57.480 align:start position:0% represents the step one of our workflow 01:27:57.480 --> 01:27:59.570 align:start position:0% represents the step one of our workflow so<01:27:58.020> basically<01:27:58.410> which<01:27:58.590> allows<01:27:58.860> to<01:27:58.890> encrypt 01:27:59.570 --> 01:27:59.580 align:start position:0% so basically which allows to encrypt 01:27:59.580 --> 01:28:03.280 align:start position:0% so basically which allows to encrypt users<01:28:00.120> input<01:28:00.870> data<01:28:01.260> and<01:28:01.470> push<01:28:02.190> it<01:28:02.520> to<01:28:02.940> the 01:28:03.280 --> 01:28:03.290 align:start position:0% users input data and push it to the 01:28:03.290 --> 01:28:05.500 align:start position:0% users input data and push it to the remote<01:28:04.290> filesystem 01:28:05.500 --> 01:28:05.510 align:start position:0% remote filesystem 01:28:05.510 --> 01:28:10.670 align:start position:0% remote filesystem so<01:28:06.890> basically<01:28:07.910> the<01:28:08.910> the<01:28:09.840> this<01:28:10.350> command 01:28:10.670 --> 01:28:10.680 align:start position:0% so basically the the this command 01:28:10.680 --> 01:28:13.100 align:start position:0% so basically the the this command returns<01:28:11.100> output<01:28:11.340> which<01:28:12.300> contains<01:28:12.840> some 01:28:13.100 --> 01:28:13.110 align:start position:0% returns output which contains some 01:28:13.110 --> 01:28:15.710 align:start position:0% returns output which contains some parameters<01:28:13.620> like<01:28:13.830> URL<01:28:14.520> pointing<01:28:15.360> to<01:28:15.540> the 01:28:15.710 --> 01:28:15.720 align:start position:0% parameters like URL pointing to the 01:28:15.720 --> 01:28:16.670 align:start position:0% parameters like URL pointing to the remote<01:28:15.960> filesystem 01:28:16.670 --> 01:28:16.680 align:start position:0% remote filesystem 01:28:16.680 --> 01:28:20.090 align:start position:0% remote filesystem storing<01:28:17.430> the<01:28:18.270> userís<01:28:18.960> encrypted<01:28:19.650> data<01:28:19.830> and 01:28:20.090 --> 01:28:20.100 align:start position:0% storing the userís encrypted data and 01:28:20.100 --> 01:28:24.080 align:start position:0% storing the userís encrypted data and you<01:28:20.970> there<01:28:21.180> just<01:28:21.360> do<01:28:21.480> some<01:28:22.140> several<01:28:23.100> simple 01:28:24.080 --> 01:28:24.090 align:start position:0% you there just do some several simple 01:28:24.090 --> 01:28:27.500 align:start position:0% you there just do some several simple configurations<01:28:24.810> with<01:28:25.260> this<01:28:25.530> URL<01:28:26.510> because 01:28:27.500 --> 01:28:27.510 align:start position:0% configurations with this URL because 01:28:27.510 --> 01:28:30.380 align:start position:0% configurations with this URL because this<01:28:27.840> you<01:28:27.990> are<01:28:28.110> we<01:28:28.230> all<01:28:28.380> are<01:28:28.920> used<01:28:29.190> to<01:28:29.580> feed 01:28:30.380 --> 01:28:30.390 align:start position:0% this you are we all are used to feed 01:28:30.390 --> 01:28:33.620 align:start position:0% this you are we all are used to feed through<01:28:30.840> the<01:28:30.990> second<01:28:31.290> step<01:28:31.560> so<01:28:32.490> basically<01:28:32.880> the 01:28:33.620 --> 01:28:33.630 align:start position:0% through the second step so basically the 01:28:33.630 --> 01:28:36.290 align:start position:0% through the second step so basically the second<01:28:33.990> step<01:28:34.200> is<01:28:34.440> that<01:28:34.590> user<01:28:35.040> want<01:28:35.850> to<01:28:35.970> trigger 01:28:36.290 --> 01:28:36.300 align:start position:0% second step is that user want to trigger 01:28:36.300 --> 01:28:39.380 align:start position:0% second step is that user want to trigger the<01:28:36.810> off<01:28:36.960> chain<01:28:37.850> applications<01:28:38.850> running<01:28:39.180> on 01:28:39.380 --> 01:28:39.390 align:start position:0% the off chain applications running on 01:28:39.390 --> 01:28:42.820 align:start position:0% the off chain applications running on the<01:28:39.540> decentralized<01:28:39.960> node<01:28:40.590> so<01:28:41.520> a<01:28:41.790> user<01:28:42.120> can 01:28:42.820 --> 01:28:42.830 align:start position:0% the decentralized node so a user can 01:28:42.830 --> 01:28:46.400 align:start position:0% the decentralized node so a user can campaign<01:28:43.830> based<01:28:44.160> on<01:28:44.340> Isaac<01:28:44.910> marketplace<01:28:45.840> the 01:28:46.400 --> 01:28:46.410 align:start position:0% campaign based on Isaac marketplace the 01:28:46.410 --> 01:28:49.700 align:start position:0% campaign based on Isaac marketplace the user<01:28:46.770> can<01:28:46.980> choose<01:28:47.270> available<01:28:48.270> as<01:28:48.450> GX<01:28:49.110> o<01:28:49.350> Kapoor 01:28:49.700 --> 01:28:49.710 align:start position:0% user can choose available as GX o Kapoor 01:28:49.710 --> 01:28:52.760 align:start position:0% user can choose available as GX o Kapoor and<01:28:50.420> when<01:28:51.420> as<01:28:51.660> soon<01:28:51.720> as<01:28:51.960> the<01:28:52.080> user<01:28:52.110> choose 01:28:52.760 --> 01:28:52.770 align:start position:0% and when as soon as the user choose 01:28:52.770 --> 01:28:55.520 align:start position:0% and when as soon as the user choose available<01:28:53.310> who<01:28:53.880> X<01:28:54.450> work<01:28:54.630> pool<01:28:54.900> he<01:28:55.080> can<01:28:55.290> trigger 01:28:55.520 --> 01:28:55.530 align:start position:0% available who X work pool he can trigger 01:28:55.530 --> 01:28:58.970 align:start position:0% available who X work pool he can trigger the<01:28:56.040> option<01:28:56.490> applications<01:28:57.450> via<01:28:57.960> our<01:28:58.230> a<01:28:58.500> simple 01:28:58.970 --> 01:28:58.980 align:start position:0% the option applications via our a simple 01:28:58.980 --> 01:29:02.630 align:start position:0% the option applications via our a simple command<01:28:59.250> so<01:28:59.790> which<01:29:00.060> is<01:29:00.300> Isaac<01:29:00.810> or<01:29:00.990> a<01:29:01.050> few<01:29:01.640> user 01:29:02.630 --> 01:29:02.640 align:start position:0% command so which is Isaac or a few user 01:29:02.640 --> 01:29:05.810 align:start position:0% command so which is Isaac or a few user can<01:29:02.850> also<01:29:03.000> use<01:29:03.420> the<01:29:03.600> option<01:29:03.960> watch<01:29:04.370> to<01:29:05.370> monitor 01:29:05.810 --> 01:29:05.820 align:start position:0% can also use the option watch to monitor 01:29:05.820 --> 01:29:08.750 align:start position:0% can also use the option watch to monitor in<01:29:06.030> real<01:29:06.240> time<01:29:06.540> the<01:29:07.020> running<01:29:07.500> status<01:29:07.980> of<01:29:08.280> the 01:29:08.750 --> 01:29:08.760 align:start position:0% in real time the running status of the 01:29:08.760 --> 01:29:12.530 align:start position:0% in real time the running status of the application<01:29:09.390> execution<01:29:10.230> and<01:29:10.790> user<01:29:11.790> can<01:29:12.030> also 01:29:12.530 --> 01:29:12.540 align:start position:0% application execution and user can also 01:29:12.540 --> 01:29:15.620 align:start position:0% application execution and user can also use<01:29:13.080> the<01:29:13.290> option<01:29:13.620> download<01:29:14.040> to<01:29:14.640> download<01:29:14.850> the 01:29:15.620 --> 01:29:15.630 align:start position:0% use the option download to download the 01:29:15.630 --> 01:29:18.140 align:start position:0% use the option download to download the application<01:29:16.170> out<01:29:16.710> port<01:29:17.070> as<01:29:17.280> some<01:29:17.790> add<01:29:18.000> the 01:29:18.140 --> 01:29:18.150 align:start position:0% application out port as some add the 01:29:18.150 --> 01:29:20.570 align:start position:0% application out port as some add the application<01:29:18.240> finishes<01:29:19.110> running<01:29:19.280> so<01:29:20.280> you<01:29:20.430> they 01:29:20.570 --> 01:29:20.580 align:start position:0% application finishes running so you they 01:29:20.580 --> 01:29:24.590 align:start position:0% application finishes running so you they can<01:29:20.790> also<01:29:21.020> monitor<01:29:22.020> monitor<01:29:22.530> the<01:29:23.330> status<01:29:24.330> of 01:29:24.590 --> 01:29:24.600 align:start position:0% can also monitor monitor the status of 01:29:24.600 --> 01:29:27.610 align:start position:0% can also monitor monitor the status of the<01:29:25.020> application<01:29:25.440> execution<01:29:26.370> via<01:29:26.700> our<01:29:26.880> UI 01:29:27.610 --> 01:29:27.620 align:start position:0% the application execution via our UI 01:29:27.620 --> 01:29:31.690 align:start position:0% the application execution via our UI interface<01:29:28.620> via<01:29:29.400> the<01:29:29.490> Isaac<01:29:30.030> Explorer<01:29:30.930> or 01:29:31.690 --> 01:29:31.700 align:start position:0% interface via the Isaac Explorer or 01:29:31.700 --> 01:29:37.160 align:start position:0% interface via the Isaac Explorer or governor<01:29:33.380> so<01:29:35.210> so<01:29:36.210> for<01:29:36.480> the<01:29:36.600> embro<01:29:36.780> here<01:29:36.990> the 01:29:37.160 --> 01:29:37.170 align:start position:0% governor so so for the embro here the 01:29:37.170 --> 01:29:42.440 align:start position:0% governor so so for the embro here the running<01:29:37.530> status<01:29:38.040> of<01:29:38.310> the<01:29:38.850> application<01:29:39.690> so<01:29:41.450> the 01:29:42.440 --> 01:29:42.450 align:start position:0% running status of the application so the 01:29:42.450 --> 01:29:44.720 align:start position:0% running status of the application so the blockchain<01:29:42.810> the<01:29:43.620> transaction<01:29:44.370> takes<01:29:44.460> some 01:29:44.720 --> 01:29:44.730 align:start position:0% blockchain the transaction takes some 01:29:44.730 --> 01:29:47.840 align:start position:0% blockchain the transaction takes some times<01:29:45.110> so<01:29:46.110> finally<01:29:46.860> as<01:29:46.980> soon<01:29:47.190> as<01:29:47.340> the 01:29:47.840 --> 01:29:47.850 align:start position:0% times so finally as soon as the 01:29:47.850 --> 01:29:48.770 align:start position:0% times so finally as soon as the applications 01:29:48.770 --> 01:29:48.780 align:start position:0% applications 01:29:48.780 --> 01:29:52.010 align:start position:0% applications finishes<01:29:49.290> running<01:29:49.500> so<01:29:50.430> the<01:29:51.210> user<01:29:51.510> only<01:29:51.840> needs 01:29:52.010 --> 01:29:52.020 align:start position:0% finishes running so the user only needs 01:29:52.020 --> 01:29:54.950 align:start position:0% finishes running so the user only needs to<01:29:52.410> run<01:29:52.650> a<01:29:52.770> very<01:29:53.040> simple<01:29:53.610> command<01:29:53.790> so<01:29:54.540> which<01:29:54.720> is 01:29:54.950 --> 01:29:54.960 align:start position:0% to run a very simple command so which is 01:29:54.960 --> 01:29:56.330 align:start position:0% to run a very simple command so which is the<01:29:55.530> IV 01:29:56.330 --> 01:29:56.340 align:start position:0% the IV 01:29:56.340 --> 01:30:00.050 align:start position:0% the IV te<01:29:57.060> decrypt<01:29:57.900> so<01:29:58.770> this<01:29:59.010> command<01:29:59.310> allows 01:30:00.050 --> 01:30:00.060 align:start position:0% te decrypt so this command allows 01:30:00.060 --> 01:30:03.620 align:start position:0% te decrypt so this command allows you<01:30:00.230> decrypt<01:30:01.230> the<01:30:01.790> application<01:30:02.790> out<01:30:03.000> port<01:30:03.360> and 01:30:03.620 --> 01:30:03.630 align:start position:0% you decrypt the application out port and 01:30:03.630 --> 01:30:07.400 align:start position:0% you decrypt the application out port and push<01:30:04.350> the<01:30:05.040> decrypt<01:30:06.000> out<01:30:06.240> port<01:30:06.570> to<01:30:06.750> a<01:30:06.780> specific 01:30:07.400 --> 01:30:07.410 align:start position:0% push the decrypt out port to a specific 01:30:07.410 --> 01:30:11.750 align:start position:0% push the decrypt out port to a specific space<01:30:07.860> folder<01:30:08.430> which<01:30:08.970> is<01:30:09.000> names<01:30:09.660> the<01:30:10.320> PE<01:30:11.220> out 01:30:11.750 --> 01:30:11.760 align:start position:0% space folder which is names the PE out 01:30:11.760 --> 01:30:15.710 align:start position:0% space folder which is names the PE out ports<01:30:12.770> so<01:30:13.770> here<01:30:14.040> we<01:30:14.190> can<01:30:14.340> see<01:30:14.550> that<01:30:14.580> the<01:30:15.060> DS 01:30:15.710 --> 01:30:15.720 align:start position:0% ports so here we can see that the DS 01:30:15.720 --> 01:30:17.630 align:start position:0% ports so here we can see that the DS application<01:30:16.320> automatically<01:30:16.860> created<01:30:17.400> K 01:30:17.630 --> 01:30:17.640 align:start position:0% application automatically created K 01:30:17.640 --> 01:30:20.090 align:start position:0% application automatically created K decrypted<01:30:18.600> outputs<01:30:19.020> and<01:30:19.200> pushed<01:30:19.710> to<01:30:19.890> the 01:30:20.090 --> 01:30:20.100 align:start position:0% decrypted outputs and pushed to the 01:30:20.100 --> 01:30:23.240 align:start position:0% decrypted outputs and pushed to the airports<01:30:20.640> so<01:30:21.510> the<01:30:21.690> user<01:30:21.930> go<01:30:22.140> to<01:30:22.200> te<01:30:22.560> and<01:30:23.010> route 01:30:23.240 --> 01:30:23.250 align:start position:0% airports so the user go to te and route 01:30:23.250 --> 01:30:26.000 align:start position:0% airports so the user go to te and route posts<01:30:23.670> and<01:30:23.880> thievery<01:30:24.360> this<01:30:24.810> is<01:30:25.050> the<01:30:25.230> output<01:30:25.560> of 01:30:26.000 --> 01:30:26.010 align:start position:0% posts and thievery this is the output of 01:30:26.010 --> 01:30:30.440 align:start position:0% posts and thievery this is the output of the<01:30:26.610> of<01:30:27.570> the<01:30:27.840> application<01:30:28.350> without<01:30:28.910> well<01:30:29.910> so 01:30:30.440 --> 01:30:30.450 align:start position:0% the of the application without well so 01:30:30.450 --> 01:30:33.820 align:start position:0% the of the application without well so uh<01:30:30.480> I<01:30:31.020> would<01:30:31.410> like<01:30:31.500> to<01:30:31.740> analyze<01:30:31.890> that<01:30:32.400> only<01:30:32.850> the 01:30:33.820 --> 01:30:33.830 align:start position:0% uh I would like to analyze that only the 01:30:33.830 --> 01:30:35.380 align:start position:0% uh I would like to analyze that only the [Music] 01:30:35.380 --> 01:30:35.390 align:start position:0% [Music] 01:30:35.390 --> 01:30:39.620 align:start position:0% [Music] living<01:30:36.390> a<01:30:36.750> very<01:30:36.960> little<01:30:37.230> time<01:30:37.560> so<01:30:38.210> I<01:30:39.210> think 01:30:39.620 --> 01:30:39.630 align:start position:0% living a very little time so I think 01:30:39.630 --> 01:30:41.630 align:start position:0% living a very little time so I think we'll<01:30:39.900> hold<01:30:40.140> off<01:30:40.380> any<01:30:40.710> questions<01:30:41.280> and<01:30:41.430> you<01:30:41.490> can 01:30:41.630 --> 01:30:41.640 align:start position:0% we'll hold off any questions and you can 01:30:41.640 --> 01:30:45.170 align:start position:0% we'll hold off any questions and you can catch<01:30:42.090> layer<01:30:42.480> after<01:30:42.750> the<01:30:43.110> meeting<01:30:43.470> and<01:30:44.180> thanks 01:30:45.170 --> 01:30:45.180 align:start position:0% catch layer after the meeting and thanks 01:30:45.180 --> 01:30:54.650 align:start position:0% catch layer after the meeting and thanks lis<01:30:50.900> so<01:30:51.900> so<01:30:52.320> we<01:30:52.880> wanted<01:30:53.880> to<01:30:53.940> also<01:30:54.360> like<01:30:54.540> you 01:30:54.650 --> 01:30:54.660 align:start position:0% lis so so we wanted to also like you 01:30:54.660 --> 01:30:56.330 align:start position:0% lis so so we wanted to also like you know<01:30:54.690> how<01:30:54.900> try<01:30:55.410> to<01:30:55.470> hopefully<01:30:55.890> make<01:30:56.190> it<01:30:56.220> a 01:30:56.330 --> 01:30:56.340 align:start position:0% know how try to hopefully make it a 01:30:56.340 --> 01:30:58.070 align:start position:0% know how try to hopefully make it a little<01:30:56.460> bit<01:30:56.700> more<01:30:56.820> interactive<01:30:57.390> and<01:30:57.510> we'll 01:30:58.070 --> 01:30:58.080 align:start position:0% little bit more interactive and we'll 01:30:58.080 --> 01:31:02.360 align:start position:0% little bit more interactive and we'll have<01:30:58.230> a<01:30:58.260> short<01:30:58.590> panel<01:30:59.130> which<01:30:59.280> commonly<01:30:59.910> I<01:31:01.370> hope 01:31:02.360 --> 01:31:02.370 align:start position:0% have a short panel which commonly I hope 01:31:02.370 --> 01:31:04.880 align:start position:0% have a short panel which commonly I hope is<01:31:02.550> that<01:31:02.730> you<01:31:03.690> know<01:31:03.810> we<01:31:03.990> entertain<01:31:04.440> you 01:31:04.880 --> 01:31:04.890 align:start position:0% is that you know we entertain you 01:31:04.890 --> 01:31:08.600 align:start position:0% is that you know we entertain you perhaps<01:31:05.730> by<01:31:06.030> our<01:31:06.300> disagreements<01:31:06.990> and<01:31:07.580> so<01:31:08.580> I 01:31:08.600 --> 01:31:08.610 align:start position:0% perhaps by our disagreements and so I 01:31:08.610 --> 01:31:10.280 align:start position:0% perhaps by our disagreements and so I have<01:31:08.880> a<01:31:08.940> set<01:31:09.150> of<01:31:09.240> questions<01:31:09.360> I<01:31:09.690> can<01:31:09.900> ask<01:31:10.080> them 01:31:10.280 --> 01:31:10.290 align:start position:0% have a set of questions I can ask them 01:31:10.290 --> 01:31:11.810 align:start position:0% have a set of questions I can ask them but<01:31:10.530> if<01:31:10.680> there's<01:31:10.860> any<01:31:11.040> questions<01:31:11.580> that<01:31:11.730> are 01:31:11.810 --> 01:31:11.820 align:start position:0% but if there's any questions that are 01:31:11.820 --> 01:31:15.250 align:start position:0% but if there's any questions that are really<01:31:11.970> you<01:31:12.360> know<01:31:12.450> burning<01:31:12.980> inside<01:31:14.090> you<01:31:15.090> know 01:31:15.250 --> 01:31:15.260 align:start position:0% really you know burning inside you know 01:31:15.260 --> 01:31:17.870 align:start position:0% really you know burning inside you know you<01:31:16.260> and<01:31:16.410> the<01:31:16.770> audience<01:31:17.100> can<01:31:17.160> also<01:31:17.400> ask<01:31:17.670> them 01:31:17.870 --> 01:31:17.880 align:start position:0% you and the audience can also ask them 01:31:17.880 --> 01:31:20.990 align:start position:0% you and the audience can also ask them and<01:31:18.500> I<01:31:19.500> think<01:31:20.280> you<01:31:20.670> know<01:31:20.730> we<01:31:20.850> should<01:31:20.970> probably 01:31:20.990 --> 01:31:21.000 align:start position:0% and I think you know we should probably 01:31:21.000 --> 01:31:23.150 align:start position:0% and I think you know we should probably start<01:31:21.540> by<01:31:21.630> introducing<01:31:21.870> ourselves<01:31:22.380> so<01:31:23.010> I'm 01:31:23.150 --> 01:31:23.160 align:start position:0% start by introducing ourselves so I'm 01:31:23.160 --> 01:31:29.300 align:start position:0% start by introducing ourselves so I'm Tom<01:31:23.400> Willis<01:31:23.580> I'm<01:31:23.910> at<01:31:24.330> Intel<01:31:25.010> I'm<01:31:27.080> I'm<01:31:28.080> a<01:31:28.310> board 01:31:29.300 --> 01:31:29.310 align:start position:0% Tom Willis I'm at Intel I'm I'm a board 01:31:29.310 --> 01:31:31.070 align:start position:0% Tom Willis I'm at Intel I'm I'm a board member<01:31:29.400> of<01:31:29.580> the<01:31:29.670> EEA<01:31:29.910> and<01:31:30.360> I'm<01:31:30.690> also<01:31:30.900> a 01:31:31.070 --> 01:31:31.080 align:start position:0% member of the EEA and I'm also a 01:31:31.080 --> 01:31:32.870 align:start position:0% member of the EEA and I'm also a director<01:31:31.410> in<01:31:31.800> the<01:31:31.890> open<01:31:32.100> source<01:31:32.250> Technology 01:31:32.870 --> 01:31:32.880 align:start position:0% director in the open source Technology 01:31:32.880 --> 01:31:38.870 align:start position:0% director in the open source Technology Center<01:31:35.900> Thank<01:31:36.900> You<01:31:36.930> Thomas<01:31:37.860> Bertani<01:31:38.280> I<01:31:38.520> am<01:31:38.640> the 01:31:38.870 --> 01:31:38.880 align:start position:0% Center Thank You Thomas Bertani I am the 01:31:38.880 --> 01:31:42.230 align:start position:0% Center Thank You Thomas Bertani I am the CEO<01:31:39.090> of<01:31:39.210> our<01:31:39.510> cries<01:31:39.980> we<01:31:40.980> are<01:31:41.220> the<01:31:41.550> most<01:31:42.000> widely 01:31:42.230 --> 01:31:42.240 align:start position:0% CEO of our cries we are the most widely 01:31:42.240 --> 01:31:43.850 align:start position:0% CEO of our cries we are the most widely used<01:31:42.390> Oracle<01:31:42.900> service<01:31:43.200> on<01:31:43.320> aetherium<01:31:43.680> right 01:31:43.850 --> 01:31:43.860 align:start position:0% used Oracle service on aetherium right 01:31:43.860 --> 01:31:46.310 align:start position:0% used Oracle service on aetherium right now<01:31:44.040> on<01:31:44.310> the<01:31:44.580> main<01:31:44.700> net<01:31:44.940> and<01:31:45.200> we<01:31:46.200> have 01:31:46.310 --> 01:31:46.320 align:start position:0% now on the main net and we have 01:31:46.320 --> 01:31:49.280 align:start position:0% now on the main net and we have approximately<01:31:46.860> 1,000<01:31:47.760> contracts<01:31:48.630> as<01:31:49.080> much 01:31:49.280 --> 01:31:49.290 align:start position:0% approximately 1,000 contracts as much 01:31:49.290 --> 01:31:52.430 align:start position:0% approximately 1,000 contracts as much contrast<01:31:49.620> using<01:31:50.070> our<01:31:50.370> Oracle<01:31:50.910> API<01:31:51.390> which<01:31:52.050> uses 01:31:52.430 --> 01:31:52.440 align:start position:0% contrast using our Oracle API which uses 01:31:52.440 --> 01:31:56.680 align:start position:0% contrast using our Oracle API which uses T<01:31:52.590> to<01:31:53.280> secure<01:31:53.850> the<01:31:54.180> authenticity<01:31:54.390> of<01:31:54.750> data 01:31:56.680 --> 01:31:56.690 align:start position:0% T to secure the authenticity of data 01:31:56.690 --> 01:32:00.080 align:start position:0% T to secure the authenticity of data Andreas<01:31:57.690> Freund<01:31:57.960> from<01:31:58.260> consensus<01:31:58.890> my<01:31:59.850> roller 01:32:00.080 --> 01:32:00.090 align:start position:0% Andreas Freund from consensus my roller 01:32:00.090 --> 01:32:05.060 align:start position:0% Andreas Freund from consensus my roller is<01:32:00.480> the<01:32:00.780> blockchain<01:32:01.200> Swiss<01:32:01.650> Army<01:32:01.920> knife<01:32:03.230> is<01:32:04.230> C 01:32:05.060 --> 01:32:05.070 align:start position:0% is the blockchain Swiss Army knife is C 01:32:05.070 --> 01:32:08.300 align:start position:0% is the blockchain Swiss Army knife is C so<01:32:05.280> for<01:32:05.550> golem<01:32:06.000> your<01:32:06.600> neural<01:32:06.960> curves 01:32:08.300 --> 01:32:08.310 align:start position:0% so for golem your neural curves 01:32:08.310 --> 01:32:13.470 align:start position:0% so for golem your neural curves and<01:32:10.770> our<01:32:11.770> aim<01:32:12.130> is<01:32:12.340> to<01:32:12.370> create<01:32:12.520> user<01:32:12.940> controlled 01:32:13.470 --> 01:32:13.480 align:start position:0% and our aim is to create user controlled 01:32:13.480 --> 01:32:16.560 align:start position:0% and our aim is to create user controlled clouds<01:32:13.810> actually<01:32:15.179> morally<01:32:16.179> right 01:32:16.560 --> 01:32:16.570 align:start position:0% clouds actually morally right 01:32:16.570 --> 01:32:25.620 align:start position:0% clouds actually morally right Microsoft<01:32:17.760> yeah<01:32:18.929> Sanjay<01:32:23.580> okay<01:32:24.580> so<01:32:24.640> my<01:32:25.330> first 01:32:25.620 --> 01:32:25.630 align:start position:0% Microsoft yeah Sanjay okay so my first 01:32:25.630 --> 01:32:28.140 align:start position:0% Microsoft yeah Sanjay okay so my first question<01:32:26.260> for<01:32:26.560> the<01:32:26.620> panel<01:32:27.130> is<01:32:27.340> we<01:32:27.850> just 01:32:28.140 --> 01:32:28.150 align:start position:0% question for the panel is we just 01:32:28.150 --> 01:32:30.570 align:start position:0% question for the panel is we just released<01:32:28.840> this<01:32:29.190> trusted<01:32:30.190> compute 01:32:30.570 --> 01:32:30.580 align:start position:0% released this trusted compute 01:32:30.580 --> 01:32:34.919 align:start position:0% released this trusted compute specification<01:32:31.449> from<01:32:31.660> the<01:32:31.929> EA<01:32:33.300> why<01:32:34.300> is<01:32:34.360> wise 01:32:34.919 --> 01:32:34.929 align:start position:0% specification from the EA why is wise 01:32:34.929 --> 01:32:37.430 align:start position:0% specification from the EA why is wise how's<01:32:35.230> this<01:32:35.380> help<01:32:35.650> and<01:32:36.340> why<01:32:36.489> is<01:32:36.550> it<01:32:36.699> important 01:32:37.430 --> 01:32:37.440 align:start position:0% how's this help and why is it important 01:32:37.440 --> 01:32:40.140 align:start position:0% how's this help and why is it important anybody<01:32:38.440> want<01:32:38.560> to<01:32:38.679> start<01:32:39.070> that<01:32:39.219> answer<01:32:39.969> that 01:32:40.140 --> 01:32:40.150 align:start position:0% anybody want to start that answer that 01:32:40.150 --> 01:32:48.060 align:start position:0% anybody want to start that answer that question<01:32:44.850> okay<01:32:46.290> so<01:32:47.290> the<01:32:47.500> thing<01:32:47.679> is<01:32:47.770> like<01:32:47.890> the 01:32:48.060 --> 01:32:48.070 align:start position:0% question okay so the thing is like the 01:32:48.070 --> 01:32:52.140 align:start position:0% question okay so the thing is like the reason<01:32:48.489> we<01:32:50.400> like<01:32:51.400> one<01:32:51.580> of<01:32:51.670> the<01:32:51.790> things<01:32:51.969> like 01:32:52.140 --> 01:32:52.150 align:start position:0% reason we like one of the things like 01:32:52.150 --> 01:32:55.560 align:start position:0% reason we like one of the things like you<01:32:52.210> know<01:32:52.420> the<01:32:52.600> EA<01:32:53.380> came<01:32:53.800> into<01:32:54.010> the<01:32:54.300> being<01:32:55.300> is 01:32:55.560 --> 01:32:55.570 align:start position:0% you know the EA came into the being is 01:32:55.570 --> 01:32:57.680 align:start position:0% you know the EA came into the being is to<01:32:56.290> create<01:32:56.560> standardized<01:32:57.070> interfaces 01:32:57.680 --> 01:32:57.690 align:start position:0% to create standardized interfaces 01:32:57.690 --> 01:32:59.700 align:start position:0% to create standardized interfaces interoperability<01:32:58.690> between<01:32:59.020> clients 01:32:59.700 --> 01:32:59.710 align:start position:0% interoperability between clients 01:32:59.710 --> 01:33:01.680 align:start position:0% interoperability between clients implementing<01:33:00.310> all<01:33:00.460> kinds<01:33:00.790> of<01:33:00.880> various<01:33:01.480> types 01:33:01.680 --> 01:33:01.690 align:start position:0% implementing all kinds of various types 01:33:01.690 --> 01:33:05.010 align:start position:0% implementing all kinds of various types of<01:33:01.870> say<01:33:03.360> scalability<01:33:04.360> solutions<01:33:04.780> and<01:33:04.929> things 01:33:05.010 --> 01:33:05.020 align:start position:0% of say scalability solutions and things 01:33:05.020 --> 01:33:05.430 align:start position:0% of say scalability solutions and things like<01:33:05.199> that 01:33:05.430 --> 01:33:05.440 align:start position:0% like that 01:33:05.440 --> 01:33:09.300 align:start position:0% like that as<01:33:05.890> part<01:33:06.219> of<01:33:06.280> that<01:33:06.489> we<01:33:08.040> noticed<01:33:09.040> that<01:33:09.160> there 01:33:09.300 --> 01:33:09.310 align:start position:0% as part of that we noticed that there 01:33:09.310 --> 01:33:11.580 align:start position:0% as part of that we noticed that there are<01:33:09.429> different<01:33:09.790> ways<01:33:09.969> the<01:33:10.690> off<01:33:10.870> chain<01:33:11.140> compute 01:33:11.580 --> 01:33:11.590 align:start position:0% are different ways the off chain compute 01:33:11.590 --> 01:33:14.040 align:start position:0% are different ways the off chain compute based<01:33:11.800> on<01:33:12.040> you<01:33:12.460> know<01:33:12.520> teas<01:33:13.120> and<01:33:13.570> other<01:33:13.690> kinds 01:33:14.040 --> 01:33:14.050 align:start position:0% based on you know teas and other kinds 01:33:14.050 --> 01:33:17.250 align:start position:0% based on you know teas and other kinds of<01:33:14.140> zero<01:33:14.949> knowledge<01:33:15.130> and<01:33:15.550> MPC<01:33:16.540> can<01:33:16.750> be<01:33:16.900> also 01:33:17.250 --> 01:33:17.260 align:start position:0% of zero knowledge and MPC can be also 01:33:17.260 --> 01:33:20.100 align:start position:0% of zero knowledge and MPC can be also very<01:33:17.410> relevant<01:33:17.770> in<01:33:18.070> this<01:33:18.250> space<01:33:18.460> so<01:33:18.750> the<01:33:19.750> idea 01:33:20.100 --> 01:33:20.110 align:start position:0% very relevant in this space so the idea 01:33:20.110 --> 01:33:23.970 align:start position:0% very relevant in this space so the idea was<01:33:20.320> to<01:33:20.500> create<01:33:20.620> a<01:33:22.530> standardized<01:33:23.530> interface 01:33:23.970 --> 01:33:23.980 align:start position:0% was to create a standardized interface 01:33:23.980 --> 01:33:25.740 align:start position:0% was to create a standardized interface behind<01:33:24.460> which<01:33:24.610> all<01:33:24.820> these<01:33:25.000> implementations 01:33:25.740 --> 01:33:25.750 align:start position:0% behind which all these implementations 01:33:25.750 --> 01:33:30.090 align:start position:0% behind which all these implementations can<01:33:26.100> sit<01:33:27.540> seamlessly<01:33:28.540> and<01:33:28.739> for<01:33:29.739> a<01:33:29.770> smart 01:33:30.090 --> 01:33:30.100 align:start position:0% can sit seamlessly and for a smart 01:33:30.100 --> 01:33:32.310 align:start position:0% can sit seamlessly and for a smart contract<01:33:30.340> developer<01:33:31.090> whether<01:33:31.929> they<01:33:32.199> are 01:33:32.310 --> 01:33:32.320 align:start position:0% contract developer whether they are 01:33:32.320 --> 01:33:34.950 align:start position:0% contract developer whether they are talking<01:33:33.120> they<01:33:34.120> should<01:33:34.330> be<01:33:34.449> able<01:33:34.540> to<01:33:34.660> use<01:33:34.929> a 01:33:34.950 --> 01:33:34.960 align:start position:0% talking they should be able to use a 01:33:34.960 --> 01:33:37.770 align:start position:0% talking they should be able to use a common<01:33:35.560> interface<01:33:35.830> -<01:33:36.239> without<01:33:37.239> having<01:33:37.510> to 01:33:37.770 --> 01:33:37.780 align:start position:0% common interface - without having to 01:33:37.780 --> 01:33:39.479 align:start position:0% common interface - without having to worry<01:33:37.929> about<01:33:37.989> the<01:33:38.410> implementation<01:33:38.770> of<01:33:39.280> this 01:33:39.479 --> 01:33:39.489 align:start position:0% worry about the implementation of this 01:33:39.489 --> 01:33:44.490 align:start position:0% worry about the implementation of this off<01:33:39.699> Jim<01:33:40.000> transferred<01:33:40.870> computer<01:33:42.960> yeah<01:33:43.960> if<01:33:44.320> I 01:33:44.490 --> 01:33:44.500 align:start position:0% off Jim transferred computer yeah if I 01:33:44.500 --> 01:33:46.200 align:start position:0% off Jim transferred computer yeah if I can<01:33:44.650> add<01:33:44.770> something<01:33:44.980> I<01:33:45.340> think<01:33:45.699> that<01:33:45.910> this 01:33:46.200 --> 01:33:46.210 align:start position:0% can add something I think that this 01:33:46.210 --> 01:33:48.000 align:start position:0% can add something I think that this effort<01:33:46.390> is<01:33:46.900> really<01:33:47.110> important<01:33:47.530> because<01:33:47.710> right 01:33:48.000 --> 01:33:48.010 align:start position:0% effort is really important because right 01:33:48.010 --> 01:33:48.930 align:start position:0% effort is really important because right now 01:33:48.930 --> 01:33:48.940 align:start position:0% now 01:33:48.940 --> 01:33:52.709 align:start position:0% now whoever<01:33:49.560> like<01:33:50.560> us<01:33:50.770> is<01:33:51.040> already<01:33:51.460> like<01:33:52.360> in 01:33:52.709 --> 01:33:52.719 align:start position:0% whoever like us is already like in 01:33:52.719 --> 01:33:54.870 align:start position:0% whoever like us is already like in looking<01:33:53.350> for<01:33:53.500> something<01:33:53.770> like<01:33:53.890> this<01:33:54.100> has 01:33:54.870 --> 01:33:54.880 align:start position:0% looking for something like this has 01:33:54.880 --> 01:33:56.689 align:start position:0% looking for something like this has basically<01:33:55.120> to<01:33:55.540> design<01:33:55.840> its<01:33:56.050> own<01:33:56.199> solution 01:33:56.689 --> 01:33:56.699 align:start position:0% basically to design its own solution 01:33:56.699 --> 01:34:00.570 align:start position:0% basically to design its own solution which<01:33:57.699> can<01:33:58.090> be<01:33:58.270> hardly<01:33:58.660> compatible<01:33:59.469> with<01:34:00.400> the 01:34:00.570 --> 01:34:00.580 align:start position:0% which can be hardly compatible with the 01:34:00.580 --> 01:34:02.970 align:start position:0% which can be hardly compatible with the competitors<01:34:01.210> of<01:34:01.449> course<01:34:01.719> so<01:34:02.170> having<01:34:02.590> someone 01:34:02.970 --> 01:34:02.980 align:start position:0% competitors of course so having someone 01:34:02.980 --> 01:34:05.760 align:start position:0% competitors of course so having someone like<01:34:03.219> the<01:34:03.910> ATM<01:34:04.150> enterprise<01:34:04.570> Alliance<01:34:05.050> pushing 01:34:05.760 --> 01:34:05.770 align:start position:0% like the ATM enterprise Alliance pushing 01:34:05.770 --> 01:34:08.070 align:start position:0% like the ATM enterprise Alliance pushing for<01:34:05.980> like<01:34:06.219> a<01:34:06.250> common<01:34:06.670> standard<01:34:07.420> interface 01:34:08.070 --> 01:34:08.080 align:start position:0% for like a common standard interface 01:34:08.080 --> 01:34:10.709 align:start position:0% for like a common standard interface helps<01:34:09.040> to<01:34:09.250> understand<01:34:10.060> better<01:34:10.239> than<01:34:10.510> the 01:34:10.709 --> 01:34:10.719 align:start position:0% helps to understand better than the 01:34:10.719 --> 01:34:13.200 align:start position:0% helps to understand better than the needs<01:34:10.870> of<01:34:10.960> everyone<01:34:11.400> in<01:34:12.400> you<01:34:12.670> know<01:34:12.790> a<01:34:12.820> neutral 01:34:13.200 --> 01:34:13.210 align:start position:0% needs of everyone in you know a neutral 01:34:13.210 --> 01:34:16.650 align:start position:0% needs of everyone in you know a neutral account<01:34:13.920> and<01:34:14.920> having<01:34:15.699> a<01:34:16.000> standard<01:34:16.360> like<01:34:16.510> this 01:34:16.650 --> 01:34:16.660 align:start position:0% account and having a standard like this 01:34:16.660 --> 01:34:20.010 align:start position:0% account and having a standard like this going<01:34:17.290> forward<01:34:17.560> will<01:34:18.219> possibly<01:34:18.820> also<01:34:19.330> try<01:34:19.960> to 01:34:20.010 --> 01:34:20.020 align:start position:0% going forward will possibly also try to 01:34:20.020 --> 01:34:21.439 align:start position:0% going forward will possibly also try to find<01:34:20.500> a<01:34:20.739> common 01:34:21.439 --> 01:34:21.449 align:start position:0% find a common 01:34:21.449 --> 01:34:24.830 align:start position:0% find a common between<01:34:21.840> the<01:34:22.320> enterprise<01:34:22.530> needs<01:34:23.010> and<01:34:23.310> the<01:34:23.940> you 01:34:24.830 --> 01:34:24.840 align:start position:0% between the enterprise needs and the you 01:34:24.840 --> 01:34:26.689 align:start position:0% between the enterprise needs and the you know<01:34:24.929> public<01:34:25.140> chain<01:34:25.530> needs<01:34:25.739> because<01:34:26.520> right 01:34:26.689 --> 01:34:26.699 align:start position:0% know public chain needs because right 01:34:26.699 --> 01:34:28.520 align:start position:0% know public chain needs because right now<01:34:26.850> they<01:34:27.090> are<01:34:27.390> very<01:34:27.449> different<01:34:27.810> but<01:34:28.110> we 01:34:28.520 --> 01:34:28.530 align:start position:0% now they are very different but we 01:34:28.530 --> 01:34:30.080 align:start position:0% now they are very different but we expect<01:34:28.920> in<01:34:29.040> the<01:34:29.130> future<01:34:29.429> that<01:34:29.699> they<01:34:29.880> may 01:34:30.080 --> 01:34:30.090 align:start position:0% expect in the future that they may 01:34:30.090 --> 01:34:35.650 align:start position:0% expect in the future that they may converge<01:34:30.679> so<01:34:32.030> yeah<01:34:33.030> we<01:34:33.210> are<01:34:33.239> totally<01:34:34.310> like 01:34:35.650 --> 01:34:35.660 align:start position:0% converge so yeah we are totally like 01:34:35.660 --> 01:34:37.939 align:start position:0% converge so yeah we are totally like supporting<01:34:36.660> this<01:34:36.840> and<01:34:37.110> looking<01:34:37.410> forward<01:34:37.800> to 01:34:37.939 --> 01:34:37.949 align:start position:0% supporting this and looking forward to 01:34:37.949 --> 01:34:39.470 align:start position:0% supporting this and looking forward to keep<01:34:38.160> contributing<01:34:38.820> to<01:34:38.940> the<01:34:39.239> next 01:34:39.470 --> 01:34:39.480 align:start position:0% keep contributing to the next 01:34:39.480 --> 01:34:43.910 align:start position:0% keep contributing to the next specifications<01:34:40.110> as<01:34:40.230> well<01:34:42.560> okay<01:34:43.560> next 01:34:43.910 --> 01:34:43.920 align:start position:0% specifications as well okay next 01:34:43.920 --> 01:34:46.280 align:start position:0% specifications as well okay next question<01:34:44.900> we've<01:34:45.900> heard<01:34:46.050> a<01:34:46.080> lot<01:34:46.260> about 01:34:46.280 --> 01:34:46.290 align:start position:0% question we've heard a lot about 01:34:46.290 --> 01:34:50.240 align:start position:0% question we've heard a lot about decentralization<01:34:47.120> here<01:34:48.120> at<01:34:49.010> this<01:34:50.010> conference 01:34:50.240 --> 01:34:50.250 align:start position:0% decentralization here at this conference 01:34:50.250 --> 01:34:52.220 align:start position:0% decentralization here at this conference this<01:34:51.239> trusted<01:34:51.719> compute<01:34:52.020> help 01:34:52.220 --> 01:34:52.230 align:start position:0% this trusted compute help 01:34:52.230 --> 01:34:54.050 align:start position:0% this trusted compute help decentralization<01:34:52.920> or<01:34:53.340> hurt<01:34:53.910> the 01:34:54.050 --> 01:34:54.060 align:start position:0% decentralization or hurt the 01:34:54.060 --> 01:34:55.790 align:start position:0% decentralization or hurt the centralization<01:34:54.690> or<01:34:54.870> does<01:34:55.080> it<01:34:55.170> depend<01:34:55.380> how<01:34:55.620> we 01:34:55.790 --> 01:34:55.800 align:start position:0% centralization or does it depend how we 01:34:55.800 --> 01:35:02.780 align:start position:0% centralization or does it depend how we implement<01:34:56.250> it<01:34:59.449> so<01:35:01.100> maybe<01:35:02.100> I<01:35:02.190> will<01:35:02.370> focus<01:35:02.550> on 01:35:02.780 --> 01:35:02.790 align:start position:0% implement it so maybe I will focus on 01:35:02.790 --> 01:35:03.380 align:start position:0% implement it so maybe I will focus on SGX 01:35:03.380 --> 01:35:03.390 align:start position:0% SGX 01:35:03.390 --> 01:35:07.640 align:start position:0% SGX especially<01:35:05.600> SGX<01:35:06.600> unfortunately<01:35:07.260> even<01:35:07.530> though 01:35:07.640 --> 01:35:07.650 align:start position:0% especially SGX unfortunately even though 01:35:07.650 --> 01:35:09.260 align:start position:0% especially SGX unfortunately even though it's<01:35:07.800> exciting<01:35:08.250> technology<01:35:08.760> it<01:35:08.880> really<01:35:09.150> is 01:35:09.260 --> 01:35:09.270 align:start position:0% it's exciting technology it really is 01:35:09.270 --> 01:35:13.610 align:start position:0% it's exciting technology it really is but<01:35:09.830> as<01:35:10.830> this<01:35:11.130> in<01:35:11.910> a<01:35:12.060> current<01:35:12.449> shape<01:35:12.719> with 01:35:13.610 --> 01:35:13.620 align:start position:0% but as this in a current shape with 01:35:13.620 --> 01:35:18.439 align:start position:0% but as this in a current shape with those<01:35:14.370> two<01:35:15.060> centralized<01:35:17.000> creations<01:35:18.000> one<01:35:18.300> of 01:35:18.439 --> 01:35:18.449 align:start position:0% those two centralized creations one of 01:35:18.449 --> 01:35:21.709 align:start position:0% those two centralized creations one of those<01:35:18.660> is<01:35:19.080> remote<01:35:19.679> attestation<01:35:20.219> which<01:35:21.210> let<01:35:21.570> me 01:35:21.709 --> 01:35:21.719 align:start position:0% those is remote attestation which let me 01:35:21.719 --> 01:35:24.040 align:start position:0% those is remote attestation which let me stress<01:35:21.989> it<01:35:22.170> one<01:35:22.380> more<01:35:22.650> time<01:35:22.860> requires 01:35:24.040 --> 01:35:24.050 align:start position:0% stress it one more time requires 01:35:24.050 --> 01:35:27.890 align:start position:0% stress it one more time requires centralized<01:35:25.050> Intel<01:35:25.949> operated<01:35:26.900> Intel 01:35:27.890 --> 01:35:27.900 align:start position:0% centralized Intel operated Intel 01:35:27.900 --> 01:35:31.430 align:start position:0% centralized Intel operated Intel attestation<01:35:28.380> service<01:35:29.070> is<01:35:29.580> without<01:35:30.360> I<01:35:30.750> is 01:35:31.430 --> 01:35:31.440 align:start position:0% attestation service is without I is 01:35:31.440 --> 01:35:33.709 align:start position:0% attestation service is without I is without<01:35:31.830> contacting<01:35:32.460> I<01:35:32.699> is<01:35:33.000> for<01:35:33.300> every 01:35:33.709 --> 01:35:33.719 align:start position:0% without contacting I is for every 01:35:33.719 --> 01:35:36.290 align:start position:0% without contacting I is for every execution<01:35:33.989> of<01:35:34.560> an<01:35:34.800> Clive<01:35:35.070> of<01:35:35.400> a<01:35:35.610> new<01:35:35.790> provision 01:35:36.290 --> 01:35:36.300 align:start position:0% execution of an Clive of a new provision 01:35:36.300 --> 01:35:40.040 align:start position:0% execution of an Clive of a new provision and<01:35:36.449> Clive<01:35:36.660> as<01:35:37.020> GX<01:35:37.920> is<01:35:38.219> meaningless<01:35:38.870> let<01:35:39.870> me 01:35:40.040 --> 01:35:40.050 align:start position:0% and Clive as GX is meaningless let me 01:35:40.050 --> 01:35:42.229 align:start position:0% and Clive as GX is meaningless let me stress<01:35:40.320> it's<01:35:40.800> meaningless<01:35:41.190> without<01:35:41.460> AES<01:35:42.030> and 01:35:42.229 --> 01:35:42.239 align:start position:0% stress it's meaningless without AES and 01:35:42.239 --> 01:35:44.419 align:start position:0% stress it's meaningless without AES and is<01:35:42.600> in<01:35:43.110> full<01:35:43.350> control<01:35:43.530> of<01:35:43.739> Intel<01:35:44.190> it's<01:35:44.340> a 01:35:44.419 --> 01:35:44.429 align:start position:0% is in full control of Intel it's a 01:35:44.429 --> 01:35:47.000 align:start position:0% is in full control of Intel it's a centralized<01:35:45.000> point<01:35:45.210> which<01:35:45.650> nullifies 01:35:47.000 --> 01:35:47.010 align:start position:0% centralized point which nullifies 01:35:47.010 --> 01:35:49.280 align:start position:0% centralized point which nullifies all<01:35:47.429> the<01:35:47.850> decentralize<01:35:48.449> attempts<01:35:48.989> that<01:35:49.170> it 01:35:49.280 --> 01:35:49.290 align:start position:0% all the decentralize attempts that it 01:35:49.290 --> 01:35:51.890 align:start position:0% all the decentralize attempts that it tries<01:35:49.530> to<01:35:49.560> help<01:35:50.000> another<01:35:51.000> centralized<01:35:51.660> point 01:35:51.890 --> 01:35:51.900 align:start position:0% tries to help another centralized point 01:35:51.900 --> 01:35:55.160 align:start position:0% tries to help another centralized point which<01:35:52.230> is<01:35:52.380> often<01:35:53.150> which<01:35:54.150> we<01:35:54.300> often<01:35:54.449> missing 01:35:55.160 --> 01:35:55.170 align:start position:0% which is often which we often missing 01:35:55.170 --> 01:35:58.700 align:start position:0% which is often which we often missing this<01:35:55.320> is<01:35:55.530> the<01:35:56.600> interest<01:35:57.600> control<01:35:58.140> on<01:35:58.410> the 01:35:58.700 --> 01:35:58.710 align:start position:0% this is the interest control on the 01:35:58.710 --> 01:36:01.010 align:start position:0% this is the interest control on the launching<01:35:59.219> Kevin<01:35:59.520> Clive<01:35:59.790> which<01:36:00.420> Intel<01:36:00.840> has 01:36:01.010 --> 01:36:01.020 align:start position:0% launching Kevin Clive which Intel has 01:36:01.020 --> 01:36:03.350 align:start position:0% launching Kevin Clive which Intel has recently<01:36:01.260> made<01:36:01.800> some<01:36:01.860> steps<01:36:02.400> would<01:36:02.670> flexible 01:36:03.350 --> 01:36:03.360 align:start position:0% recently made some steps would flexible 01:36:03.360 --> 01:36:05.300 align:start position:0% recently made some steps would flexible launch<01:36:03.540> control<01:36:03.989> which<01:36:04.260> is<01:36:04.290> a<01:36:04.469> good<01:36:04.800> step<01:36:05.280> but 01:36:05.300 --> 01:36:05.310 align:start position:0% launch control which is a good step but 01:36:05.310 --> 01:36:07.580 align:start position:0% launch control which is a good step but it's<01:36:05.610> still<01:36:06.000> as<01:36:06.300> far<01:36:06.570> as<01:36:06.719> I<01:36:06.810> know<01:36:06.870> the<01:36:07.290> hardware 01:36:07.580 --> 01:36:07.590 align:start position:0% it's still as far as I know the hardware 01:36:07.590 --> 01:36:09.740 align:start position:0% it's still as far as I know the hardware is<01:36:07.710> available<01:36:07.880> very<01:36:08.880> few<01:36:09.120> details<01:36:09.239> in<01:36:09.630> the 01:36:09.740 --> 01:36:09.750 align:start position:0% is available very few details in the 01:36:09.750 --> 01:36:11.959 align:start position:0% is available very few details in the spec<01:36:10.050> there<01:36:10.500> are<01:36:10.590> some<01:36:10.739> corner<01:36:11.070> cases<01:36:11.310> that 01:36:11.959 --> 01:36:11.969 align:start position:0% spec there are some corner cases that 01:36:11.969 --> 01:36:13.490 align:start position:0% spec there are some corner cases that are<01:36:12.120> not<01:36:12.330> clear<01:36:12.660> whether<01:36:12.870> it<01:36:13.170> will<01:36:13.350> actually 01:36:13.490 --> 01:36:13.500 align:start position:0% are not clear whether it will actually 01:36:13.500 --> 01:36:15.860 align:start position:0% are not clear whether it will actually make<01:36:13.890> practical<01:36:14.550> sense<01:36:14.730> or<01:36:15.120> not<01:36:15.270> so<01:36:15.810> two 01:36:15.860 --> 01:36:15.870 align:start position:0% make practical sense or not so two 01:36:15.870 --> 01:36:18.860 align:start position:0% make practical sense or not so two things<01:36:16.500> centralized<01:36:17.460> is<01:36:18.000> and<01:36:18.270> centralized 01:36:18.860 --> 01:36:18.870 align:start position:0% things centralized is and centralized 01:36:18.870 --> 01:36:22.910 align:start position:0% things centralized is and centralized policing<01:36:19.560> conlon<01:36:19.949> lunch<01:36:20.429> and<01:36:20.640> and<01:36:21.239> grave<01:36:21.920> on 01:36:22.910 --> 01:36:22.920 align:start position:0% policing conlon lunch and and grave on 01:36:22.920 --> 01:36:24.919 align:start position:0% policing conlon lunch and and grave on launching<01:36:23.460> their<01:36:23.670> enclaves<01:36:24.000> it's<01:36:24.480> very 01:36:24.919 --> 01:36:24.929 align:start position:0% launching their enclaves it's very 01:36:24.929 --> 01:36:30.880 align:start position:0% launching their enclaves it's very problematic<01:36:25.230> on<01:36:25.739> centralization 01:36:30.880 --> 01:36:30.890 align:start position:0% 01:36:30.890 --> 01:36:36.130 align:start position:0% SGX<01:36:31.890> you<01:36:32.850> know<01:36:33.000> it's<01:36:33.300> like<01:36:33.510> Andy<01:36:34.430> trustzone 01:36:36.130 --> 01:36:36.140 align:start position:0% SGX you know it's like Andy trustzone 01:36:36.140 --> 01:36:42.500 align:start position:0% SGX you know it's like Andy trustzone MPC<01:36:37.140> ck<01:36:38.130> ck<01:36:38.760> proofs<01:36:40.730> decentralization<01:36:41.730> is<01:36:42.270> not 01:36:42.500 --> 01:36:42.510 align:start position:0% MPC ck ck proofs decentralization is not 01:36:42.510 --> 01:36:45.140 align:start position:0% MPC ck ck proofs decentralization is not gonna<01:36:42.720> be<01:36:42.870> achieved<01:36:43.230> by<01:36:43.440> a<01:36:43.470> single<01:36:44.100> of<01:36:44.670> those 01:36:45.140 --> 01:36:45.150 align:start position:0% gonna be achieved by a single of those 01:36:45.150 --> 01:36:49.040 align:start position:0% gonna be achieved by a single of those technologies<01:36:46.100> only<01:36:47.100> in<01:36:47.460> combination<01:36:48.060> will<01:36:48.870> we 01:36:49.040 --> 01:36:49.050 align:start position:0% technologies only in combination will we 01:36:49.050 --> 01:36:50.990 align:start position:0% technologies only in combination will we achieve<01:36:49.200> that<01:36:49.650> and<01:36:49.890> only<01:36:50.070> once<01:36:50.550> we<01:36:50.760> can 01:36:50.990 --> 01:36:51.000 align:start position:0% achieve that and only once we can 01:36:51.000 --> 01:36:55.960 align:start position:0% achieve that and only once we can reliably<01:36:51.750> push<01:36:52.470> out<01:36:53.510> trusts<01:36:54.510> compute<01:36:54.960> loads 01:36:55.960 --> 01:36:55.970 align:start position:0% reliably push out trusts compute loads 01:36:55.970 --> 01:37:00.110 align:start position:0% reliably push out trusts compute loads to<01:36:56.970> every<01:36:57.240> one<01:36:57.390> of<01:36:57.420> you<01:36:57.660> right<01:36:58.820> that's<01:36:59.820> the 01:37:00.110 --> 01:37:00.120 align:start position:0% to every one of you right that's the 01:37:00.120 --> 01:37:03.280 align:start position:0% to every one of you right that's the that's<01:37:00.510> the<01:37:00.630> the<01:37:01.230> promise<01:37:01.620> of<01:37:02.270> decentralized 01:37:03.280 --> 01:37:03.290 align:start position:0% that's the the promise of decentralized 01:37:03.290 --> 01:37:06.980 align:start position:0% that's the the promise of decentralized trust<01:37:04.290> at<01:37:04.470> fall<01:37:04.710> computing<01:37:05.280> because<01:37:06.060> in<01:37:06.660> the 01:37:06.980 --> 01:37:06.990 align:start position:0% trust at fall computing because in the 01:37:06.990 --> 01:37:09.110 align:start position:0% trust at fall computing because in the end<01:37:07.140> if<01:37:07.590> you<01:37:07.800> look<01:37:08.070> where<01:37:08.370> things<01:37:08.790> are<01:37:08.940> going 01:37:09.110 --> 01:37:09.120 align:start position:0% end if you look where things are going 01:37:09.120 --> 01:37:12.350 align:start position:0% end if you look where things are going especially<01:37:09.690> around<01:37:09.780> AI<01:37:10.410> if<01:37:10.950> we<01:37:11.670> don't<01:37:11.940> have 01:37:12.350 --> 01:37:12.360 align:start position:0% especially around AI if we don't have 01:37:12.360 --> 01:37:18.020 align:start position:0% especially around AI if we don't have trusted<01:37:13.080> compute<01:37:13.560> at<01:37:13.710> the<01:37:13.920> edge<01:37:17.030> everything 01:37:18.020 --> 01:37:18.030 align:start position:0% trusted compute at the edge everything 01:37:18.030 --> 01:37:22.010 align:start position:0% trusted compute at the edge everything is<01:37:18.150> still<01:37:18.270> gonna<01:37:18.420> be<01:37:18.510> run<01:37:18.750> by<01:37:18.900> Google<01:37:20.450> right<01:37:21.450> so 01:37:22.010 --> 01:37:22.020 align:start position:0% is still gonna be run by Google right so 01:37:22.020 --> 01:37:26.720 align:start position:0% is still gonna be run by Google right so at<01:37:22.740> that<01:37:22.830> point<01:37:23.130> who<01:37:23.430> cares<01:37:23.780> right<01:37:24.780> so<01:37:25.730> having 01:37:26.720 --> 01:37:26.730 align:start position:0% at that point who cares right so having 01:37:26.730 --> 01:37:29.960 align:start position:0% at that point who cares right so having the<01:37:27.180> interfaces<01:37:27.870> the<01:37:28.110> specs<01:37:28.410> is<01:37:28.800> an<01:37:29.490> important 01:37:29.960 --> 01:37:29.970 align:start position:0% the interfaces the specs is an important 01:37:29.970 --> 01:37:32.210 align:start position:0% the interfaces the specs is an important step<01:37:30.210> in<01:37:30.450> the<01:37:31.170> right<01:37:31.320> direction<01:37:31.350> because<01:37:31.950> now 01:37:32.210 --> 01:37:32.220 align:start position:0% step in the right direction because now 01:37:32.220 --> 01:37:35.150 align:start position:0% step in the right direction because now everybody<01:37:32.760> can<01:37:32.940> can<01:37:33.360> can<01:37:34.320> build<01:37:34.560> towards<01:37:34.950> that 01:37:35.150 --> 01:37:35.160 align:start position:0% everybody can can can build towards that 01:37:35.160 --> 01:37:37.100 align:start position:0% everybody can can can build towards that towards<01:37:35.760> that<01:37:35.970> that's<01:37:36.360> spec<01:37:36.660> and<01:37:36.840> make<01:37:36.960> their 01:37:37.100 --> 01:37:37.110 align:start position:0% towards that that's spec and make their 01:37:37.110 --> 01:37:40.520 align:start position:0% towards that that's spec and make their their<01:37:37.770> services<01:37:38.630> available<01:37:39.630> and<01:37:40.200> I<01:37:40.230> really 01:37:40.520 --> 01:37:40.530 align:start position:0% their services available and I really 01:37:40.530 --> 01:37:43.010 align:start position:0% their services available and I really encourage<01:37:40.650> everyone<01:37:41.310> or<01:37:41.700> someone<01:37:42.630> out<01:37:42.780> there 01:37:43.010 --> 01:37:43.020 align:start position:0% encourage everyone or someone out there 01:37:43.020 --> 01:37:45.110 align:start position:0% encourage everyone or someone out there who<01:37:43.170> wants<01:37:43.440> to<01:37:43.470> start<01:37:43.800> a<01:37:44.190> marketplace<01:37:45.090> for 01:37:45.110 --> 01:37:45.120 align:start position:0% who wants to start a marketplace for 01:37:45.120 --> 01:37:48.520 align:start position:0% who wants to start a marketplace for trusted<01:37:45.720> compute<01:37:46.140> services<01:37:46.650> using<01:37:47.580> laptops 01:37:48.520 --> 01:37:48.530 align:start position:0% trusted compute services using laptops 01:37:48.530 --> 01:37:53.390 align:start position:0% trusted compute services using laptops go<01:37:49.530> for<01:37:49.770> it<01:37:49.860> I'll<01:37:50.580> support<01:37:51.030> you<01:37:51.890> otherwise<01:37:52.890> the 01:37:53.390 --> 01:37:53.400 align:start position:0% go for it I'll support you otherwise the 01:37:53.400 --> 01:37:55.880 align:start position:0% go for it I'll support you otherwise the rest<01:37:53.550> focusing<01:37:54.240> on<01:37:54.330> one<01:37:54.480> technology<01:37:54.890> versus 01:37:55.880 --> 01:37:55.890 align:start position:0% rest focusing on one technology versus 01:37:55.890 --> 01:37:58.430 align:start position:0% rest focusing on one technology versus the<01:37:55.980> other<01:37:56.130> it<01:37:57.120> that's<01:37:57.480> that's<01:37:57.810> a<01:37:58.080> that's<01:37:58.290> a 01:37:58.430 --> 01:37:58.440 align:start position:0% the other it that's that's a that's a 01:37:58.440 --> 01:38:02.660 align:start position:0% the other it that's that's a that's a sideshow<01:37:58.860> is<01:37:59.010> completely<01:37:59.520> unimportant<01:38:01.340> so<01:38:02.340> I 01:38:02.660 --> 01:38:02.670 align:start position:0% sideshow is completely unimportant so I 01:38:02.670 --> 01:38:05.360 align:start position:0% sideshow is completely unimportant so I just<01:38:03.240> want<01:38:03.390> to<01:38:03.480> add<01:38:03.570> one<01:38:03.600> thing<01:38:04.050> is<01:38:04.320> like<01:38:04.470> when 01:38:05.360 --> 01:38:05.370 align:start position:0% just want to add one thing is like when 01:38:05.370 --> 01:38:08.420 align:start position:0% just want to add one thing is like when I<01:38:05.840> started<01:38:06.840> to<01:38:06.960> engage<01:38:07.080> with<01:38:07.380> the<01:38:07.590> helium 01:38:08.420 --> 01:38:08.430 align:start position:0% I started to engage with the helium 01:38:08.430 --> 01:38:11.570 align:start position:0% I started to engage with the helium community<01:38:09.620> close<01:38:10.620> to<01:38:10.800> like<01:38:10.950> you<01:38:11.070> know<01:38:11.190> year 01:38:11.570 --> 01:38:11.580 align:start position:0% community close to like you know year 01:38:11.580 --> 01:38:16.460 align:start position:0% community close to like you know year and<01:38:11.760> a<01:38:11.820> half<01:38:12.470> and<01:38:13.470> I<01:38:14.240> quickly<01:38:15.240> figured<01:38:15.630> out<01:38:15.900> the 01:38:16.460 --> 01:38:16.470 align:start position:0% and a half and I quickly figured out the 01:38:16.470 --> 01:38:19.300 align:start position:0% and a half and I quickly figured out the two<01:38:16.710> points<01:38:17.100> of<01:38:17.310> that<01:38:18.270> we<01:38:18.510> have 01:38:19.300 --> 01:38:19.310 align:start position:0% two points of that we have 01:38:19.310 --> 01:38:23.120 align:start position:0% two points of that we have centralization<01:38:20.720> are<01:38:21.720> we<01:38:21.930> I<01:38:22.170> would<01:38:22.380> say<01:38:22.560> had<01:38:22.800> as 01:38:23.120 --> 01:38:23.130 align:start position:0% centralization are we I would say had as 01:38:23.130 --> 01:38:27.020 align:start position:0% centralization are we I would say had as I<01:38:23.730> was<01:38:24.240> talking<01:38:24.570> about<01:38:24.630> this<01:38:25.340> the<01:38:26.340> is<01:38:26.670> thing 01:38:27.020 --> 01:38:27.030 align:start position:0% I was talking about this the is thing 01:38:27.030 --> 01:38:30.910 align:start position:0% I was talking about this the is thing and<01:38:27.360> as<01:38:27.630> well<01:38:27.810> as<01:38:28.130> the<01:38:29.130> flexible<01:38:29.640> as<01:38:30.300> well<01:38:30.510> as 01:38:30.910 --> 01:38:30.920 align:start position:0% and as well as the flexible as well as 01:38:30.920 --> 01:38:35.960 align:start position:0% and as well as the flexible as well as unclear<01:38:31.920> launch<01:38:32.100> control<01:38:33.080> so<01:38:34.080> what<01:38:34.860> what<01:38:35.670> I 01:38:35.960 --> 01:38:35.970 align:start position:0% unclear launch control so what what I 01:38:35.970 --> 01:38:39.530 align:start position:0% unclear launch control so what what I can<01:38:36.240> hear<01:38:36.660> is<01:38:36.930> that<01:38:37.520> we<01:38:38.520> at<01:38:38.940> Intel 01:38:39.530 --> 01:38:39.540 align:start position:0% can hear is that we at Intel 01:38:39.540 --> 01:38:39.959 align:start position:0% can hear is that we at Intel look 01:38:39.959 --> 01:38:39.969 align:start position:0% look 01:38:39.969 --> 01:38:44.310 align:start position:0% look that<01:38:40.150> and<01:38:41.280> and<01:38:42.280> we<01:38:42.670> have<01:38:43.659> worked<01:38:44.019> out<01:38:44.139> the 01:38:44.310 --> 01:38:44.320 align:start position:0% that and and we have worked out the 01:38:44.320 --> 01:38:47.270 align:start position:0% that and and we have worked out the solutions<01:38:44.800> for<01:38:45.070> those<01:38:45.340> things<01:38:45.610> because 01:38:47.270 --> 01:38:47.280 align:start position:0% solutions for those things because 01:38:47.280 --> 01:38:49.919 align:start position:0% solutions for those things because keeping<01:38:48.280> Intel<01:38:48.699> in<01:38:49.030> the<01:38:49.210> middle<01:38:49.479> of<01:38:49.749> those 01:38:49.919 --> 01:38:49.929 align:start position:0% keeping Intel in the middle of those 01:38:49.929 --> 01:38:53.669 align:start position:0% keeping Intel in the middle of those kinds<01:38:50.320> of<01:38:50.409> things<01:38:50.999> you<01:38:51.999> know<01:38:52.119> generally<01:38:52.719> we 01:38:53.669 --> 01:38:53.679 align:start position:0% kinds of things you know generally we 01:38:53.679 --> 01:38:56.040 align:start position:0% kinds of things you know generally we believe<01:38:54.280> is<01:38:54.400> we<01:38:55.030> want<01:38:55.239> to<01:38:55.329> go<01:38:55.449> away<01:38:55.659> from<01:38:55.869> that 01:38:56.040 --> 01:38:56.050 align:start position:0% believe is we want to go away from that 01:38:56.050 --> 01:38:58.770 align:start position:0% believe is we want to go away from that so<01:38:56.949> what<01:38:57.159> I<01:38:57.190> would<01:38:57.400> say<01:38:57.579> is<01:38:57.639> like<01:38:58.269> stay<01:38:58.539> tuned 01:38:58.770 --> 01:38:58.780 align:start position:0% so what I would say is like stay tuned 01:38:58.780 --> 01:39:02.339 align:start position:0% so what I would say is like stay tuned in<01:38:59.739> a<01:38:59.889> very<01:39:00.510> short<01:39:01.510> period<01:39:01.659> of<01:39:01.809> time<01:39:01.869> we<01:39:02.199> will 01:39:02.339 --> 01:39:02.349 align:start position:0% in a very short period of time we will 01:39:02.349 --> 01:39:04.469 align:start position:0% in a very short period of time we will be<01:39:02.530> you<01:39:03.340> will<01:39:03.460> see<01:39:03.639> like<01:39:03.849> you<01:39:03.940> know<01:39:04.030> how<01:39:04.150> Intel 01:39:04.469 --> 01:39:04.479 align:start position:0% be you will see like you know how Intel 01:39:04.479 --> 01:39:07.229 align:start position:0% be you will see like you know how Intel is<01:39:04.630> basically<01:39:05.050> making<01:39:05.349> it<01:39:05.610> you<01:39:06.610> know<01:39:06.670> getting 01:39:07.229 --> 01:39:07.239 align:start position:0% is basically making it you know getting 01:39:07.239 --> 01:39:09.209 align:start position:0% is basically making it you know getting getting<01:39:07.449> out<01:39:07.690> of<01:39:07.840> the<01:39:07.929> way<01:39:08.079> so<01:39:08.860> that<01:39:09.039> you 01:39:09.209 --> 01:39:09.219 align:start position:0% getting out of the way so that you 01:39:09.219 --> 01:39:12.209 align:start position:0% getting out of the way so that you control<01:39:09.670> the<01:39:09.849> and<01:39:10.030> claves<01:39:10.619> on<01:39:11.619> the<01:39:11.829> hardware 01:39:12.209 --> 01:39:12.219 align:start position:0% control the and claves on the hardware 01:39:12.219 --> 01:39:14.549 align:start position:0% control the and claves on the hardware you<01:39:13.150> control<01:39:13.539> that<01:39:13.719> a<01:39:13.780> station<01:39:14.079> and<01:39:14.469> you 01:39:14.549 --> 01:39:14.559 align:start position:0% you control that a station and you 01:39:14.559 --> 01:39:21.959 align:start position:0% you control that a station and you control<01:39:14.949> the<01:39:15.010> launch<01:39:20.070> hello<01:39:21.070> I'm<01:39:21.249> Simon<01:39:21.820> from 01:39:21.959 --> 01:39:21.969 align:start position:0% control the launch hello I'm Simon from 01:39:21.969 --> 01:39:25.459 align:start position:0% control the launch hello I'm Simon from Santander<01:39:22.539> we<01:39:23.229> are<01:39:23.380> part<01:39:23.619> of<01:39:23.789> John<01:39:24.789> my 01:39:25.459 --> 01:39:25.469 align:start position:0% Santander we are part of John my 01:39:25.469 --> 01:39:27.779 align:start position:0% Santander we are part of John my colleague<01:39:26.469> should<01:39:26.769> be<01:39:26.889> on<01:39:27.010> the<01:39:27.099> panel<01:39:27.280> he's<01:39:27.639> in 01:39:27.779 --> 01:39:27.789 align:start position:0% colleague should be on the panel he's in 01:39:27.789 --> 01:39:30.359 align:start position:0% colleague should be on the panel he's in London<01:39:27.940> now<01:39:28.210> so<01:39:29.199> let<01:39:29.409> me<01:39:29.559> just<01:39:29.739> give<01:39:30.039> you<01:39:30.070> the 01:39:30.359 --> 01:39:30.369 align:start position:0% London now so let me just give you the 01:39:30.369 --> 01:39:35.069 align:start position:0% London now so let me just give you the motivation<01:39:30.960> an<01:39:31.960> enterprise<01:39:32.829> has<01:39:33.519> huge<01:39:34.239> IT 01:39:35.069 --> 01:39:35.079 align:start position:0% motivation an enterprise has huge IT 01:39:35.079 --> 01:39:37.919 align:start position:0% motivation an enterprise has huge IT operation<01:39:35.800> of<01:39:35.949> chain<01:39:36.249> like<01:39:37.030> my<01:39:37.420> bank<01:39:37.659> has<01:39:37.900> a 01:39:37.919 --> 01:39:37.929 align:start position:0% operation of chain like my bank has a 01:39:37.929 --> 01:39:41.819 align:start position:0% operation of chain like my bank has a hundred<01:39:38.349> to<01:39:38.499> 40<01:39:38.889> million<01:39:39.070> users<01:39:39.340> and<01:39:40.619> if<01:39:41.619> we 01:39:41.819 --> 01:39:41.829 align:start position:0% hundred to 40 million users and if we 01:39:41.829 --> 01:39:44.729 align:start position:0% hundred to 40 million users and if we want<01:39:42.010> to<01:39:42.099> have<01:39:42.369> also<01:39:42.969> operation<01:39:43.900> on<01:39:44.229> chain 01:39:44.729 --> 01:39:44.739 align:start position:0% want to have also operation on chain 01:39:44.739 --> 01:39:48.180 align:start position:0% want to have also operation on chain whatever<01:39:45.550> however<01:39:46.539> small<01:39:47.050> the<01:39:47.739> critical 01:39:48.180 --> 01:39:48.190 align:start position:0% whatever however small the critical 01:39:48.190 --> 01:39:51.089 align:start position:0% whatever however small the critical thing<01:39:48.639> is<01:39:48.909> to<01:39:49.150> bridge<01:39:49.389> them<01:39:49.630> so<01:39:50.469> anything<01:39:50.949> that 01:39:51.089 --> 01:39:51.099 align:start position:0% thing is to bridge them so anything that 01:39:51.099 --> 01:39:53.729 align:start position:0% thing is to bridge them so anything that helps<01:39:51.429> us<01:39:51.610> to<01:39:52.210> bridge<01:39:52.479> unchain<01:39:53.260> an<01:39:53.440> offstring 01:39:53.729 --> 01:39:53.739 align:start position:0% helps us to bridge unchain an offstring 01:39:53.739 --> 01:39:58.370 align:start position:0% helps us to bridge unchain an offstring operation<01:39:54.340> is<01:39:55.239> a<01:39:55.570> godsend<01:39:55.960> at<01:39:56.289> this<01:39:56.619> point<01:39:56.860> I 01:39:58.370 --> 01:39:58.380 align:start position:0% operation is a godsend at this point I 01:39:58.380 --> 01:40:02.339 align:start position:0% operation is a godsend at this point I think<01:39:59.380> that<01:39:59.619> the<01:39:59.920> reality<01:40:00.429> nobody<01:40:01.420> has<01:40:01.630> said 01:40:02.339 --> 01:40:02.349 align:start position:0% think that the reality nobody has said 01:40:02.349 --> 01:40:05.339 align:start position:0% think that the reality nobody has said anything<01:40:02.530> about<01:40:03.070> is<01:40:03.519> that<01:40:03.789> T's<01:40:04.479> will<01:40:04.900> never<01:40:05.139> be 01:40:05.339 --> 01:40:05.349 align:start position:0% anything about is that T's will never be 01:40:05.349 --> 01:40:07.370 align:start position:0% anything about is that T's will never be decentralized<01:40:05.679> because<01:40:06.489> the<01:40:06.849> centralization 01:40:07.370 --> 01:40:07.380 align:start position:0% decentralized because the centralization 01:40:07.380 --> 01:40:09.810 align:start position:0% decentralized because the centralization implies<01:40:08.380> that<01:40:08.679> you<01:40:08.860> have<01:40:09.010> a<01:40:09.249> deterministic 01:40:09.810 --> 01:40:09.820 align:start position:0% implies that you have a deterministic 01:40:09.820 --> 01:40:13.200 align:start position:0% implies that you have a deterministic process<01:40:10.179> and<01:40:10.570> it<01:40:11.409> implies<01:40:12.010> that<01:40:12.070> you<01:40:12.789> wouldn't 01:40:13.200 --> 01:40:13.210 align:start position:0% process and it implies that you wouldn't 01:40:13.210 --> 01:40:14.580 align:start position:0% process and it implies that you wouldn't need<01:40:13.329> a<01:40:13.389> T<01:40:13.630> in<01:40:13.809> the<01:40:13.900> first<01:40:14.050> place 01:40:14.580 --> 01:40:14.590 align:start position:0% need a T in the first place 01:40:14.590 --> 01:40:17.399 align:start position:0% need a T in the first place so<01:40:15.309> the<01:40:15.489> using<01:40:16.210> a<01:40:16.300> T<01:40:16.479> using<01:40:17.019> a<01:40:17.079> trusted 01:40:17.399 --> 01:40:17.409 align:start position:0% so the using a T using a trusted 01:40:17.409 --> 01:40:19.200 align:start position:0% so the using a T using a trusted computing<01:40:17.650> solution<01:40:18.280> and<01:40:18.429> is<01:40:18.670> relating<01:40:19.119> a 01:40:19.200 --> 01:40:19.210 align:start position:0% computing solution and is relating a 01:40:19.210 --> 01:40:22.020 align:start position:0% computing solution and is relating a process<01:40:19.599> assuming<01:40:20.499> it's<01:40:20.650> safe<01:40:20.920> is<01:40:21.429> like 01:40:22.020 --> 01:40:22.030 align:start position:0% process assuming it's safe is like 01:40:22.030 --> 01:40:22.890 align:start position:0% process assuming it's safe is like cheating 01:40:22.890 --> 01:40:22.900 align:start position:0% cheating 01:40:22.900 --> 01:40:24.660 align:start position:0% cheating is<01:40:23.170> like<01:40:23.440> saying<01:40:23.739> we<01:40:23.889> don't<01:40:24.159> have<01:40:24.280> anything 01:40:24.660 --> 01:40:24.670 align:start position:0% is like saying we don't have anything 01:40:24.670 --> 01:40:27.419 align:start position:0% is like saying we don't have anything better<01:40:25.179> we<01:40:25.510> don't<01:40:25.659> have<01:40:26.190> mathematical<01:40:27.190> proof 01:40:27.419 --> 01:40:27.429 align:start position:0% better we don't have mathematical proof 01:40:27.429 --> 01:40:30.330 align:start position:0% better we don't have mathematical proof or<01:40:27.670> a<01:40:28.030> consensus<01:40:28.809> model<01:40:29.139> which<01:40:29.800> is<01:40:29.920> convincing 01:40:30.330 --> 01:40:30.340 align:start position:0% or a consensus model which is convincing 01:40:30.340 --> 01:40:33.089 align:start position:0% or a consensus model which is convincing enough<01:40:30.489> so<01:40:31.239> we<01:40:31.420> need<01:40:31.630> to<01:40:31.989> use<01:40:32.139> the<01:40:32.320> T<01:40:32.499> because 01:40:33.089 --> 01:40:33.099 align:start position:0% enough so we need to use the T because 01:40:33.099 --> 01:40:35.750 align:start position:0% enough so we need to use the T because the<01:40:33.369> T<01:40:33.550> if<01:40:33.880> if<01:40:34.570> we<01:40:34.749> assume<01:40:34.989> it<01:40:35.110> works<01:40:35.289> correctly 01:40:35.750 --> 01:40:35.760 align:start position:0% the T if if we assume it works correctly 01:40:35.760 --> 01:40:39.180 align:start position:0% the T if if we assume it works correctly we'll<01:40:36.760> do<01:40:37.269> you<01:40:38.110> know<01:40:38.229> whatever<01:40:38.650> we<01:40:38.800> need<01:40:38.979> to<01:40:39.070> do 01:40:39.180 --> 01:40:39.190 align:start position:0% we'll do you know whatever we need to do 01:40:39.190 --> 01:40:41.069 align:start position:0% we'll do you know whatever we need to do in<01:40:39.820> in<01:40:40.059> a<01:40:40.179> way<01:40:40.300> which<01:40:40.479> we<01:40:40.630> considered 01:40:41.069 --> 01:40:41.079 align:start position:0% in in a way which we considered 01:40:41.079 --> 01:40:44.910 align:start position:0% in in a way which we considered trustworthy<01:40:41.460> so<01:40:43.260> what<01:40:44.260> I<01:40:44.289> think<01:40:44.650> we<01:40:44.889> should 01:40:44.910 --> 01:40:44.920 align:start position:0% trustworthy so what I think we should 01:40:44.920 --> 01:40:46.529 align:start position:0% trustworthy so what I think we should avoid<01:40:45.340> doing<01:40:45.489> is<01:40:45.909> relying<01:40:46.300> on<01:40:46.420> a<01:40:46.479> single 01:40:46.529 --> 01:40:46.539 align:start position:0% avoid doing is relying on a single 01:40:46.539 --> 01:40:49.040 align:start position:0% avoid doing is relying on a single technology<01:40:47.079> because<01:40:47.559> other<01:40:47.949> than<01:40:48.070> the<01:40:48.340> true 01:40:49.040 --> 01:40:49.050 align:start position:0% technology because other than the true 01:40:49.050 --> 01:40:52.140 align:start position:0% technology because other than the true potential<01:40:50.050> point<01:40:51.010> of<01:40:51.190> videos<01:40:51.550> let's<01:40:51.940> say<01:40:52.030> or 01:40:52.140 --> 01:40:52.150 align:start position:0% potential point of videos let's say or 01:40:52.150 --> 01:40:53.910 align:start position:0% potential point of videos let's say or transference<01:40:52.989> we<01:40:53.079> have<01:40:53.199> with<01:40:53.349> as<01:40:53.499> Jack 01:40:53.910 --> 01:40:53.920 align:start position:0% transference we have with as Jack 01:40:53.920 --> 01:40:56.610 align:start position:0% transference we have with as Jack which<01:40:54.310> one<01:40:54.520> as<01:40:54.700> mentioned<01:40:55.330> there<01:40:56.290> is<01:40:56.380> a<01:40:56.410> third 01:40:56.610 --> 01:40:56.620 align:start position:0% which one as mentioned there is a third 01:40:56.620 --> 01:40:58.380 align:start position:0% which one as mentioned there is a third one<01:40:56.800> which<01:40:56.950> is<01:40:56.980> in<01:40:57.190> common<01:40:57.490> with<01:40:57.670> everyone<01:40:58.120> not 01:40:58.380 --> 01:40:58.390 align:start position:0% one which is in common with everyone not 01:40:58.390 --> 01:41:00.030 align:start position:0% one which is in common with everyone not just<01:40:58.420> with<01:40:58.780> the<01:40:58.900> interest<01:40:59.230> checks<01:40:59.440> with<01:40:59.770> any 01:41:00.030 --> 01:41:00.040 align:start position:0% just with the interest checks with any 01:41:00.040 --> 01:41:02.790 align:start position:0% just with the interest checks with any tea<01:41:00.610> solution<01:41:01.120> any<01:41:01.810> harder<01:41:02.140> back<01:41:02.350> solution 01:41:02.790 --> 01:41:02.800 align:start position:0% tea solution any harder back solution 01:41:02.800 --> 01:41:04.650 align:start position:0% tea solution any harder back solution which<01:41:02.980> is<01:41:03.190> that<01:41:03.400> we<01:41:03.760> don't<01:41:03.790> have<01:41:04.150> control<01:41:04.420> of 01:41:04.650 --> 01:41:04.660 align:start position:0% which is that we don't have control of 01:41:04.660 --> 01:41:06.810 align:start position:0% which is that we don't have control of the<01:41:04.960> manufacturing<01:41:05.440> process<01:41:05.890> and<01:41:06.010> we<01:41:06.670> will 01:41:06.810 --> 01:41:06.820 align:start position:0% the manufacturing process and we will 01:41:06.820 --> 01:41:09.000 align:start position:0% the manufacturing process and we will never<01:41:07.120> be<01:41:07.330> able<01:41:07.480> to<01:41:07.600> verify<01:41:07.840> in-house<01:41:08.410> that 01:41:09.000 --> 01:41:09.010 align:start position:0% never be able to verify in-house that 01:41:09.010 --> 01:41:12.300 align:start position:0% never be able to verify in-house that that<01:41:09.340> chip<01:41:09.700> is<01:41:09.910> actually<01:41:10.420> matching<01:41:11.080> and<01:41:11.950> open 01:41:12.300 --> 01:41:12.310 align:start position:0% that chip is actually matching and open 01:41:12.310 --> 01:41:13.680 align:start position:0% that chip is actually matching and open our<01:41:12.460> door<01:41:12.670> spec<01:41:12.910> that<01:41:12.940> we<01:41:13.120> typically<01:41:13.540> don't 01:41:13.680 --> 01:41:13.690 align:start position:0% our door spec that we typically don't 01:41:13.690 --> 01:41:16.140 align:start position:0% our door spec that we typically don't even<01:41:13.960> have<01:41:14.080> so<01:41:15.040> in<01:41:15.370> any<01:41:15.520> case<01:41:15.730> there<01:41:16.000> is<01:41:16.090> a 01:41:16.140 --> 01:41:16.150 align:start position:0% even have so in any case there is a 01:41:16.150 --> 01:41:18.540 align:start position:0% even have so in any case there is a trans<01:41:16.450> line<01:41:16.630> on<01:41:17.440> the<01:41:17.650> fact<01:41:17.860> that<01:41:17.950> the<01:41:18.190> tea<01:41:18.370> is 01:41:18.540 --> 01:41:18.550 align:start position:0% trans line on the fact that the tea is 01:41:18.550 --> 01:41:21.450 align:start position:0% trans line on the fact that the tea is doing<01:41:18.790> what<01:41:19.000> we<01:41:19.330> assume<01:41:19.600> it's<01:41:19.750> doing<01:41:20.280> and<01:41:21.280> we 01:41:21.450 --> 01:41:21.460 align:start position:0% doing what we assume it's doing and we 01:41:21.460 --> 01:41:23.580 align:start position:0% doing what we assume it's doing and we never<01:41:21.610> be<01:41:21.850> able<01:41:22.000> to<01:41:22.180> verify<01:41:22.300> that<01:41:22.630> so<01:41:22.690> what<01:41:23.350> we 01:41:23.580 --> 01:41:23.590 align:start position:0% never be able to verify that so what we 01:41:23.590 --> 01:41:24.990 align:start position:0% never be able to verify that so what we are<01:41:23.710> currently<01:41:23.920> doing<01:41:24.250> to<01:41:24.460> try<01:41:24.670> to<01:41:24.700> overcome 01:41:24.990 --> 01:41:25.000 align:start position:0% are currently doing to try to overcome 01:41:25.000 --> 01:41:27.720 align:start position:0% are currently doing to try to overcome death<01:41:25.360> is<01:41:25.510> saying<01:41:26.380> okay<01:41:26.710> that's<01:41:26.920> fine<01:41:27.280> this 01:41:27.720 --> 01:41:27.730 align:start position:0% death is saying okay that's fine this 01:41:27.730 --> 01:41:29.310 align:start position:0% death is saying okay that's fine this this<01:41:27.940> is<01:41:28.090> something<01:41:28.240> that<01:41:28.420> is<01:41:28.540> impossible<01:41:28.900> to 01:41:29.310 --> 01:41:29.320 align:start position:0% this is something that is impossible to 01:41:29.320 --> 01:41:32.070 align:start position:0% this is something that is impossible to solve<01:41:29.970> so<01:41:30.970> let's<01:41:31.120> just<01:41:31.300> use<01:41:31.480> more<01:41:31.750> than<01:41:31.900> one 01:41:32.070 --> 01:41:32.080 align:start position:0% solve so let's just use more than one 01:41:32.080 --> 01:41:34.560 align:start position:0% solve so let's just use more than one technology<01:41:32.380> so<01:41:33.340> that<01:41:33.550> we<01:41:34.060> know<01:41:34.270> we<01:41:34.510> are 01:41:34.560 --> 01:41:34.570 align:start position:0% technology so that we know we are 01:41:34.570 --> 01:41:36.750 align:start position:0% technology so that we know we are trusting<01:41:34.900> Intel<01:41:35.140> but<01:41:35.320> we<01:41:35.500> with<01:41:35.830> in<01:41:36.250> this<01:41:36.580> way 01:41:36.750 --> 01:41:36.760 align:start position:0% trusting Intel but we with in this way 01:41:36.760 --> 01:41:38.640 align:start position:0% trusting Intel but we with in this way we<01:41:36.910> spread<01:41:37.180> out<01:41:37.330> the<01:41:37.480> trust<01:41:37.720> and<01:41:37.930> as<01:41:38.380> long<01:41:38.590> as 01:41:38.640 --> 01:41:38.650 align:start position:0% we spread out the trust and as long as 01:41:38.650 --> 01:41:42.480 align:start position:0% we spread out the trust and as long as we<01:41:38.920> pick<01:41:39.190> some<01:41:39.520> artists<01:41:40.270> eaters<01:41:40.630> which<01:41:41.490> don't 01:41:42.480 --> 01:41:42.490 align:start position:0% we pick some artists eaters which don't 01:41:42.490 --> 01:41:45.150 align:start position:0% we pick some artists eaters which don't have<01:41:42.760> any<01:41:43.270> interest<01:41:44.170> or<01:41:44.470> any<01:41:44.680> conflict<01:41:45.070> of 01:41:45.150 --> 01:41:45.160 align:start position:0% have any interest or any conflict of 01:41:45.160 --> 01:41:46.710 align:start position:0% have any interest or any conflict of interest<01:41:45.550> if<01:41:46.030> they<01:41:46.210> are<01:41:46.270> competing<01:41:46.540> for 01:41:46.710 --> 01:41:46.720 align:start position:0% interest if they are competing for 01:41:46.720 --> 01:41:48.780 align:start position:0% interest if they are competing for example<01:41:47.200> then<01:41:47.650> the<01:41:48.010> proof<01:41:48.250> you<01:41:48.430> get<01:41:48.640> is 01:41:48.780 --> 01:41:48.790 align:start position:0% example then the proof you get is 01:41:48.790 --> 01:41:51.000 align:start position:0% example then the proof you get is stronger<01:41:49.210> like<01:41:49.750> if<01:41:49.960> we<01:41:50.110> get<01:41:50.320> the<01:41:50.620> Intel 01:41:51.000 --> 01:41:51.010 align:start position:0% stronger like if we get the Intel 01:41:51.010 --> 01:41:52.590 align:start position:0% stronger like if we get the Intel proving<01:41:51.460> something<01:41:51.880> in<01:41:52.060> then<01:41:52.240> we<01:41:52.390> get 01:41:52.590 --> 01:41:52.600 align:start position:0% proving something in then we get 01:41:52.600 --> 01:41:54.570 align:start position:0% proving something in then we get Microsoft<01:41:53.230> proving<01:41:53.650> something<01:41:53.830> else<01:41:54.070> may<01:41:54.550> be 01:41:54.570 --> 01:41:54.580 align:start position:0% Microsoft proving something else may be 01:41:54.580 --> 01:41:56.460 align:start position:0% Microsoft proving something else may be the<01:41:54.790> same<01:41:55.000> plane<01:41:55.240> right<01:41:55.540> and<01:41:55.720> then<01:41:56.200> we<01:41:56.350> have 01:41:56.460 --> 01:41:56.470 align:start position:0% the same plane right and then we have 01:41:56.470 --> 01:41:59.310 align:start position:0% the same plane right and then we have ledger<01:41:56.770> and<01:41:57.130> then<01:41:57.520> we<01:41:57.670> have<01:41:57.850> Google<01:41:58.750> I<01:41:59.080> think 01:41:59.310 --> 01:41:59.320 align:start position:0% ledger and then we have Google I think 01:41:59.320 --> 01:42:00.690 align:start position:0% ledger and then we have Google I think said<01:41:59.470> that<01:41:59.620> you<01:41:59.740> understand<01:42:00.310> we<01:42:00.430> have<01:42:00.520> like 01:42:00.690 --> 01:42:00.700 align:start position:0% said that you understand we have like 01:42:00.700 --> 01:42:02.580 align:start position:0% said that you understand we have like four<01:42:00.970> players<01:42:01.300> which<01:42:01.840> are<01:42:01.990> competing<01:42:02.470> and 01:42:02.580 --> 01:42:02.590 align:start position:0% four players which are competing and 01:42:02.590 --> 01:42:05.430 align:start position:0% four players which are competing and have<01:42:02.800> a<01:42:02.830> huge<01:42:03.220> reputation<01:42:03.550> at<01:42:03.910> stake<01:42:04.440> which 01:42:05.430 --> 01:42:05.440 align:start position:0% have a huge reputation at stake which 01:42:05.440 --> 01:42:07.140 align:start position:0% have a huge reputation at stake which are<01:42:05.590> claiming<01:42:05.800> the<01:42:05.920> same<01:42:06.100> thing<01:42:06.340> so<01:42:06.850> does<01:42:07.000> the 01:42:07.140 --> 01:42:07.150 align:start position:0% are claiming the same thing so does the 01:42:07.150 --> 01:42:09.720 align:start position:0% are claiming the same thing so does the tea<01:42:07.300> help<01:42:07.660> yes<01:42:07.960> it<01:42:08.110> does<01:42:08.590> but<01:42:09.160> it's<01:42:09.340> not<01:42:09.490> enough 01:42:09.720 --> 01:42:09.730 align:start position:0% tea help yes it does but it's not enough 01:42:09.730 --> 01:42:11.580 align:start position:0% tea help yes it does but it's not enough there<01:42:10.030> is<01:42:10.150> always<01:42:10.510> a<01:42:10.540> transfer<01:42:10.960> in<01:42:11.020> any<01:42:11.170> way<01:42:11.320> so 01:42:11.580 --> 01:42:11.590 align:start position:0% there is always a transfer in any way so 01:42:11.590 --> 01:42:13.350 align:start position:0% there is always a transfer in any way so it's<01:42:11.710> not<01:42:11.770> decentralized<01:42:12.520> and<01:42:12.790> we<01:42:12.940> never<01:42:13.150> will 01:42:13.350 --> 01:42:13.360 align:start position:0% it's not decentralized and we never will 01:42:13.360 --> 01:42:18.030 align:start position:0% it's not decentralized and we never will be<01:42:16.050> okay<01:42:17.050> great 01:42:18.030 --> 01:42:18.040 align:start position:0% be okay great 01:42:18.040 --> 01:42:21.270 align:start position:0% be okay great that<01:42:18.370> was<01:42:18.490> entertaining<01:42:19.180> so<01:42:19.870> next<01:42:20.830> next 01:42:21.270 --> 01:42:21.280 align:start position:0% that was entertaining so next next 01:42:21.280 --> 01:42:25.230 align:start position:0% that was entertaining so next next question<01:42:21.910> is<01:42:22.120> um<01:42:23.340> trusted<01:42:24.340> compute<01:42:24.730> are<01:42:25.000> there 01:42:25.230 --> 01:42:25.240 align:start position:0% question is um trusted compute are there 01:42:25.240 --> 01:42:27.510 align:start position:0% question is um trusted compute are there any<01:42:25.390> new<01:42:25.960> we<01:42:26.350> don't<01:42:26.770> like<01:42:26.890> to<01:42:27.010> make<01:42:27.130> a<01:42:27.190> living 01:42:27.510 --> 01:42:27.520 align:start position:0% any new we don't like to make a living 01:42:27.520 --> 01:42:31.130 align:start position:0% any new we don't like to make a living right<01:42:27.820> and<01:42:27.970> is<01:42:28.840> there<01:42:29.320> are<01:42:29.590> there<01:42:29.800> any<01:42:29.950> new 01:42:31.130 --> 01:42:31.140 align:start position:0% right and is there are there any new 01:42:31.140 --> 01:42:33.900 align:start position:0% right and is there are there any new business<01:42:32.140> opportunities<01:42:32.890> that<01:42:33.520> have<01:42:33.640> merged 01:42:33.900 --> 01:42:33.910 align:start position:0% business opportunities that have merged 01:42:33.910 --> 01:42:35.820 align:start position:0% business opportunities that have merged because<01:42:34.360> trusted<01:42:34.750> compute<01:42:35.110> now<01:42:35.260> can<01:42:35.500> be<01:42:35.620> used 01:42:35.820 --> 01:42:35.830 align:start position:0% because trusted compute now can be used 01:42:35.830 --> 01:42:40.770 align:start position:0% because trusted compute now can be used with<01:42:36.490> aetherium<01:42:39.240> Marley<01:42:40.240> has<01:42:40.390> the<01:42:40.480> answer<01:42:40.690> to 01:42:40.770 --> 01:42:40.780 align:start position:0% with aetherium Marley has the answer to 01:42:40.780 --> 01:42:46.470 align:start position:0% with aetherium Marley has the answer to that<01:42:41.970> yeah<01:42:43.770> yeah<01:42:44.770> well<01:42:45.760> we<01:42:45.850> think<01:42:45.970> about<01:42:46.120> you 01:42:46.470 --> 01:42:46.480 align:start position:0% that yeah yeah well we think about you 01:42:46.480 --> 01:42:50.820 align:start position:0% that yeah yeah well we think about you know<01:42:46.600> I<01:42:46.810> think<01:42:47.490> it<01:42:48.490> will<01:42:48.760> enable<01:42:49.290> the<01:42:50.290> ability 01:42:50.820 --> 01:42:50.830 align:start position:0% know I think it will enable the ability 01:42:50.830 --> 01:42:52.890 align:start position:0% know I think it will enable the ability to<01:42:50.890> create<01:42:51.220> them<01:42:51.370> so<01:42:51.850> you<01:42:52.450> know<01:42:52.510> Microsoft 01:42:52.890 --> 01:42:52.900 align:start position:0% to create them so you know Microsoft 01:42:52.900 --> 01:42:54.300 align:start position:0% to create them so you know Microsoft will<01:42:53.110> try<01:42:53.230> to<01:42:53.260> build<01:42:53.410> a<01:42:53.530> platform<01:42:53.740> to<01:42:54.100> make<01:42:54.220> it 01:42:54.300 --> 01:42:54.310 align:start position:0% will try to build a platform to make it 01:42:54.310 --> 01:42:55.500 align:start position:0% will try to build a platform to make it possible<01:42:54.640> to<01:42:54.970> create<01:42:55.060> the<01:42:55.300> killer 01:42:55.500 --> 01:42:55.510 align:start position:0% possible to create the killer 01:42:55.510 --> 01:43:01.590 align:start position:0% possible to create the killer application<01:42:58.080> so<01:42:59.080> you<01:42:59.440> know<01:43:00.060> the<01:43:01.060> the<01:43:01.390> thing<01:43:01.420> is 01:43:01.590 --> 01:43:01.600 align:start position:0% application so you know the the thing is 01:43:01.600 --> 01:43:03.420 align:start position:0% application so you know the the thing is is<01:43:01.870> when<01:43:02.050> you<01:43:02.170> start<01:43:02.440> to<01:43:02.530> lay<01:43:02.650> these<01:43:02.830> layers<01:43:03.250> of 01:43:03.420 --> 01:43:03.430 align:start position:0% is when you start to lay these layers of 01:43:03.430 --> 01:43:05.760 align:start position:0% is when you start to lay these layers of em<01:43:03.520> structure<01:43:03.880> you<01:43:04.000> start<01:43:04.480> to<01:43:04.600> like<01:43:05.140> we're 01:43:05.760 --> 01:43:05.770 align:start position:0% em structure you start to like we're 01:43:05.770 --> 01:43:07.500 align:start position:0% em structure you start to like we're just<01:43:05.800> finishing<01:43:06.070> you<01:43:06.640> need<01:43:06.790> to 01:43:07.500 --> 01:43:07.510 align:start position:0% just finishing you need to 01:43:07.510 --> 01:43:09.540 align:start position:0% just finishing you need to in<01:43:07.750> depth<01:43:07.980> security<01:43:08.980> in<01:43:09.070> depth<01:43:09.310> and<01:43:09.460> you're 01:43:09.540 --> 01:43:09.550 align:start position:0% in depth security in depth and you're 01:43:09.550 --> 01:43:11.010 align:start position:0% in depth security in depth and you're gonna<01:43:09.640> have<01:43:09.790> layers<01:43:10.030> of<01:43:10.239> the<01:43:10.330> stress<01:43:10.570> or<01:43:10.720> have 01:43:11.010 --> 01:43:11.020 align:start position:0% gonna have layers of the stress or have 01:43:11.020 --> 01:43:13.380 align:start position:0% gonna have layers of the stress or have single<01:43:12.010> points<01:43:12.220> of<01:43:12.280> failure<01:43:12.340> in<01:43:12.730> places<01:43:13.150> and 01:43:13.380 --> 01:43:13.390 align:start position:0% single points of failure in places and 01:43:13.390 --> 01:43:16.200 align:start position:0% single points of failure in places and the<01:43:14.040> good<01:43:15.040> news<01:43:15.190> is<01:43:15.310> we're<01:43:15.460> progressing<01:43:15.820> in 01:43:16.200 --> 01:43:16.210 align:start position:0% the good news is we're progressing in 01:43:16.210 --> 01:43:19.830 align:start position:0% the good news is we're progressing in that<01:43:16.360> that<01:43:16.720> direction<01:43:17.760> but<01:43:18.760> while<01:43:19.660> that's 01:43:19.830 --> 01:43:19.840 align:start position:0% that that direction but while that's 01:43:19.840 --> 01:43:21.770 align:start position:0% that that direction but while that's going<01:43:20.080> on<01:43:20.350> people<01:43:20.980> do<01:43:21.130> need<01:43:21.280> to<01:43:21.430> make<01:43:21.550> money 01:43:21.770 --> 01:43:21.780 align:start position:0% going on people do need to make money 01:43:21.780 --> 01:43:23.940 align:start position:0% going on people do need to make money and<01:43:22.780> you<01:43:23.140> need<01:43:23.380> to<01:43:23.470> be<01:43:23.560> able<01:43:23.620> to<01:43:23.739> build 01:43:23.940 --> 01:43:23.950 align:start position:0% and you need to be able to build 01:43:23.950 --> 01:43:27.540 align:start position:0% and you need to be able to build solutions<01:43:24.130> rapidly<01:43:25.030> and<01:43:25.930> get<01:43:26.140> them<01:43:26.290> to<01:43:26.410> market 01:43:27.540 --> 01:43:27.550 align:start position:0% solutions rapidly and get them to market 01:43:27.550 --> 01:43:32.340 align:start position:0% solutions rapidly and get them to market and<01:43:28.150> also<01:43:28.510> do<01:43:28.989> it<01:43:29.140> cost<01:43:29.800> effectively<01:43:31.020> so<01:43:32.020> you 01:43:32.340 --> 01:43:32.350 align:start position:0% and also do it cost effectively so you 01:43:32.350 --> 01:43:35.100 align:start position:0% and also do it cost effectively so you know<01:43:32.590> as<01:43:32.710> we<01:43:32.739> go<01:43:33.610> around<01:43:33.730> and<01:43:34.239> start<01:43:34.420> telling 01:43:35.100 --> 01:43:35.110 align:start position:0% know as we go around and start telling 01:43:35.110 --> 01:43:37.310 align:start position:0% know as we go around and start telling customers<01:43:35.350> about<01:43:35.950> what<01:43:36.580> we're<01:43:36.700> trying<01:43:36.850> to<01:43:37.090> do 01:43:37.310 --> 01:43:37.320 align:start position:0% customers about what we're trying to do 01:43:37.320 --> 01:43:40.110 align:start position:0% customers about what we're trying to do with<01:43:38.320> a<01:43:38.350> platform<01:43:38.920> we're<01:43:39.640> not<01:43:39.760> trying<01:43:40.090> to 01:43:40.110 --> 01:43:40.120 align:start position:0% with a platform we're not trying to 01:43:40.120 --> 01:43:41.550 align:start position:0% with a platform we're not trying to compete<01:43:40.420> with<01:43:40.570> anyone<01:43:40.810> we're<01:43:41.140> trying<01:43:41.350> to<01:43:41.440> lay 01:43:41.550 --> 01:43:41.560 align:start position:0% compete with anyone we're trying to lay 01:43:41.560 --> 01:43:43.500 align:start position:0% compete with anyone we're trying to lay the<01:43:41.710> groundwork<01:43:42.100> because<01:43:42.430> we<01:43:42.550> think<01:43:42.730> this<01:43:43.300> is 01:43:43.500 --> 01:43:43.510 align:start position:0% the groundwork because we think this is 01:43:43.510 --> 01:43:47.100 align:start position:0% the groundwork because we think this is super<01:43:43.660> exciting<01:43:45.690> from<01:43:46.690> an<01:43:46.780> application 01:43:47.100 --> 01:43:47.110 align:start position:0% super exciting from an application 01:43:47.110 --> 01:43:49.500 align:start position:0% super exciting from an application standpoint<01:43:47.500> we<01:43:47.770> honestly<01:43:48.610> don't<01:43:48.790> know<01:43:48.970> we've 01:43:49.500 --> 01:43:49.510 align:start position:0% standpoint we honestly don't know we've 01:43:49.510 --> 01:43:51.300 align:start position:0% standpoint we honestly don't know we've heard<01:43:49.840> so<01:43:49.989> many<01:43:50.140> ideas<01:43:50.320> and<01:43:50.710> sometimes<01:43:50.920> I 01:43:51.300 --> 01:43:51.310 align:start position:0% heard so many ideas and sometimes I 01:43:51.310 --> 01:43:53.820 align:start position:0% heard so many ideas and sometimes I can't<01:43:51.640> share<01:43:51.790> some<01:43:52.030> of<01:43:52.150> them<01:43:52.290> that<01:43:53.290> we<01:43:53.680> have 01:43:53.820 --> 01:43:53.830 align:start position:0% can't share some of them that we have 01:43:53.830 --> 01:43:57.050 align:start position:0% can't share some of them that we have active<01:43:54.760> customers<01:43:55.180> in<01:43:55.390> development<01:43:55.960> building 01:43:57.050 --> 01:43:57.060 align:start position:0% active customers in development building 01:43:57.060 --> 01:43:59.010 align:start position:0% active customers in development building applications<01:43:58.060> that<01:43:58.210> are<01:43:58.420> intended<01:43:58.780> to<01:43:58.930> make 01:43:59.010 --> 01:43:59.020 align:start position:0% applications that are intended to make 01:43:59.020 --> 01:44:02.400 align:start position:0% applications that are intended to make lots<01:43:59.380> of<01:43:59.590> money<01:44:00.239> I'm<01:44:01.239> just<01:44:01.480> saying<01:44:01.720> not 01:44:02.400 --> 01:44:02.410 align:start position:0% lots of money I'm just saying not 01:44:02.410 --> 01:44:04.440 align:start position:0% lots of money I'm just saying not necessarily<01:44:02.800> cryptocurrency<01:44:03.190> but<01:44:03.580> that<01:44:04.239> will 01:44:04.440 --> 01:44:04.450 align:start position:0% necessarily cryptocurrency but that will 01:44:04.450 --> 01:44:11.930 align:start position:0% necessarily cryptocurrency but that will come<01:44:04.630> as<01:44:04.810> well<01:44:08.880> yeah<01:44:09.880> if<01:44:10.180> I<01:44:10.390> can<01:44:10.570> add<01:44:10.690> on<01:44:11.020> this 01:44:11.930 --> 01:44:11.940 align:start position:0% come as well yeah if I can add on this 01:44:11.940 --> 01:44:14.280 align:start position:0% come as well yeah if I can add on this Oracle<01:44:12.940> is<01:44:13.060> has<01:44:13.300> been<01:44:13.450> currently<01:44:13.720> serving 01:44:14.280 --> 01:44:14.290 align:start position:0% Oracle is has been currently serving 01:44:14.290 --> 01:44:16.680 align:start position:0% Oracle is has been currently serving approximately<01:44:15.070> 1<01:44:15.280> million<01:44:15.550> paid<01:44:16.150> requests 01:44:16.680 --> 01:44:16.690 align:start position:0% approximately 1 million paid requests 01:44:16.690 --> 01:44:21.150 align:start position:0% approximately 1 million paid requests asking<01:44:17.050> for<01:44:17.470> TE<01:44:17.790> back<01:44:18.790> data<01:44:19.170> so<01:44:20.170> there<01:44:20.530> is<01:44:20.650> like 01:44:21.150 --> 01:44:21.160 align:start position:0% asking for TE back data so there is like 01:44:21.160 --> 01:44:22.560 align:start position:0% asking for TE back data so there is like an<01:44:21.340> opportunity<01:44:21.730> to<01:44:21.910> make<01:44:22.090> money<01:44:22.270> here 01:44:22.560 --> 01:44:22.570 align:start position:0% an opportunity to make money here 01:44:22.570 --> 01:44:24.990 align:start position:0% an opportunity to make money here especially<01:44:23.200> because<01:44:23.500> this<01:44:23.890> T<01:44:24.520> is<01:44:24.760> these 01:44:24.990 --> 01:44:25.000 align:start position:0% especially because this T is these 01:44:25.000 --> 01:44:27.210 align:start position:0% especially because this T is these actual<01:44:25.450> physical<01:44:25.989> devices<01:44:26.290> they<01:44:26.980> are<01:44:27.010> not 01:44:27.210 --> 01:44:27.220 align:start position:0% actual physical devices they are not 01:44:27.220 --> 01:44:28.890 align:start position:0% actual physical devices they are not something<01:44:27.460> he<01:44:27.790> is<01:44:27.850> it<01:44:28.000> fine<01:44:28.270> at<01:44:28.750> the<01:44:28.870> moment 01:44:28.890 --> 01:44:28.900 align:start position:0% something he is it fine at the moment 01:44:28.900 --> 01:44:30.120 align:start position:0% something he is it fine at the moment list<01:44:29.440> in<01:44:29.620> the<01:44:29.710> cloud 01:44:30.120 --> 01:44:30.130 align:start position:0% list in the cloud 01:44:30.130 --> 01:44:33.270 align:start position:0% list in the cloud other<01:44:30.520> than<01:44:30.730> interest<01:44:31.120> checks<01:44:31.440> if<01:44:32.440> we<01:44:32.980> assume 01:44:33.270 --> 01:44:33.280 align:start position:0% other than interest checks if we assume 01:44:33.280 --> 01:44:35.610 align:start position:0% other than interest checks if we assume we<01:44:33.430> will<01:44:33.670> want<01:44:34.210> to<01:44:34.330> use<01:44:34.420> more<01:44:34.720> than<01:44:34.750> one<01:44:34.900> some 01:44:35.610 --> 01:44:35.620 align:start position:0% we will want to use more than one some 01:44:35.620 --> 01:44:37.170 align:start position:0% we will want to use more than one some of<01:44:35.770> those<01:44:35.950> are<01:44:36.190> not<01:44:36.280> even<01:44:36.550> designed<01:44:36.910> to<01:44:37.090> be 01:44:37.170 --> 01:44:37.180 align:start position:0% of those are not even designed to be 01:44:37.180 --> 01:44:41.250 align:start position:0% of those are not even designed to be using<01:44:37.420> the<01:44:37.540> cloud<01:44:37.690> yet<01:44:38.850> so<01:44:39.850> yeah<01:44:40.570> I<01:44:40.600> think<01:44:40.989> that 01:44:41.250 --> 01:44:41.260 align:start position:0% using the cloud yet so yeah I think that 01:44:41.260 --> 01:44:43.860 align:start position:0% using the cloud yet so yeah I think that at<01:44:41.470> least<01:44:41.710> for<01:44:42.100> the<01:44:42.430> next<01:44:42.760> two<01:44:43.600> or<01:44:43.690> three<01:44:43.720> years 01:44:43.860 --> 01:44:43.870 align:start position:0% at least for the next two or three years 01:44:43.870 --> 01:44:45.750 align:start position:0% at least for the next two or three years there<01:44:44.470> is<01:44:44.560> definitely<01:44:44.890> this<01:44:44.980> opportunity<01:44:45.610> and 01:44:45.750 --> 01:44:45.760 align:start position:0% there is definitely this opportunity and 01:44:45.760 --> 01:44:47.610 align:start position:0% there is definitely this opportunity and then<01:44:46.030> other<01:44:46.210> opportunities<01:44:46.840> will<01:44:47.050> arise<01:44:47.080> once 01:44:47.610 --> 01:44:47.620 align:start position:0% then other opportunities will arise once 01:44:47.620 --> 01:44:52.500 align:start position:0% then other opportunities will arise once this<01:44:48.270> like<01:44:49.830> market<01:44:50.830> will<01:44:51.040> scale<01:44:51.310> up<01:44:51.340> and<01:44:51.700> we 01:44:52.500 --> 01:44:52.510 align:start position:0% this like market will scale up and we 01:44:52.510 --> 01:44:54.060 align:start position:0% this like market will scale up and we actually<01:44:52.540> see<01:44:53.050> where<01:44:53.260> it<01:44:53.590> will<01:44:53.770> be<01:44:53.920> going 01:44:54.060 --> 01:44:54.070 align:start position:0% actually see where it will be going 01:44:54.070 --> 01:44:59.100 align:start position:0% actually see where it will be going exactly<01:44:55.739> so<01:44:56.739> I<01:44:56.770> think<01:44:57.960> there's<01:44:58.960> an 01:44:59.100 --> 01:44:59.110 align:start position:0% exactly so I think there's an 01:44:59.110 --> 01:45:03.710 align:start position:0% exactly so I think there's an interesting<01:44:59.650> conundrum<01:45:00.580> on<01:45:01.120> the<01:45:01.480> for<01:45:02.410> the<01:45:02.440> for 01:45:03.710 --> 01:45:03.720 align:start position:0% interesting conundrum on the for the for 01:45:03.720 --> 01:45:06.750 align:start position:0% interesting conundrum on the for the for trusted<01:45:04.720> compute<01:45:05.140> enablers<01:45:05.890> if<01:45:06.400> you<01:45:06.489> look<01:45:06.640> at 01:45:06.750 --> 01:45:06.760 align:start position:0% trusted compute enablers if you look at 01:45:06.760 --> 01:45:09.840 align:start position:0% trusted compute enablers if you look at the<01:45:06.850> AI<01:45:06.940> space<01:45:07.420> right<01:45:08.280> the<01:45:09.280> biggest<01:45:09.610> enabler 01:45:09.840 --> 01:45:09.850 align:start position:0% the AI space right the biggest enabler 01:45:09.850 --> 01:45:12.750 align:start position:0% the AI space right the biggest enabler of<01:45:10.120> AI<01:45:10.510> applications<01:45:11.100> nowadays<01:45:12.100> is 01:45:12.750 --> 01:45:12.760 align:start position:0% of AI applications nowadays is 01:45:12.760 --> 01:45:16.229 align:start position:0% of AI applications nowadays is Hortonworks<01:45:13.660> cloud<01:45:14.260> cloud<01:45:15.040> era<01:45:15.310> there<01:45:15.969> what 01:45:16.229 --> 01:45:16.239 align:start position:0% Hortonworks cloud cloud era there what 01:45:16.239 --> 01:45:19.470 align:start position:0% Hortonworks cloud cloud era there what three<01:45:16.630> billion<01:45:16.900> in<01:45:17.200> market<01:45:17.980> value<01:45:18.360> the<01:45:19.360> AI 01:45:19.470 --> 01:45:19.480 align:start position:0% three billion in market value the AI 01:45:19.480 --> 01:45:21.150 align:start position:0% three billion in market value the AI application<01:45:20.320> providers 01:45:21.150 --> 01:45:21.160 align:start position:0% application providers 01:45:21.160 --> 01:45:24.150 align:start position:0% application providers what<01:45:21.550> like<01:45:21.880> three<01:45:22.330> trillion<01:45:22.780> in<01:45:23.650> market<01:45:23.800> value 01:45:24.150 --> 01:45:24.160 align:start position:0% what like three trillion in market value 01:45:24.160 --> 01:45:26.870 align:start position:0% what like three trillion in market value so<01:45:24.940> we're<01:45:25.210> looking<01:45:25.540> at<01:45:25.660> like<01:45:25.930> a<01:45:26.080> thousand<01:45:26.560> x 01:45:26.870 --> 01:45:26.880 align:start position:0% so we're looking at like a thousand x 01:45:26.880 --> 01:45:32.040 align:start position:0% so we're looking at like a thousand x right<01:45:27.880> difference<01:45:29.040> so<01:45:30.270> enablers<01:45:31.270> so<01:45:31.810> that 01:45:32.040 --> 01:45:32.050 align:start position:0% right difference so enablers so that 01:45:32.050 --> 01:45:34.140 align:start position:0% right difference so enablers so that what<01:45:32.230> what<01:45:32.530> Marley<01:45:32.890> kind<01:45:33.160> of<01:45:33.220> alluded<01:45:33.640> to<01:45:33.670> is 01:45:34.140 --> 01:45:34.150 align:start position:0% what what Marley kind of alluded to is 01:45:34.150 --> 01:45:36.930 align:start position:0% what what Marley kind of alluded to is like<01:45:34.750> yeah<01:45:35.260> you<01:45:35.320> need<01:45:35.650> the<01:45:35.680> security<01:45:36.250> down<01:45:36.760> the 01:45:36.930 --> 01:45:36.940 align:start position:0% like yeah you need the security down the 01:45:36.940 --> 01:45:39.360 align:start position:0% like yeah you need the security down the sack<01:45:37.180> right<01:45:38.140> what's<01:45:38.530> the<01:45:38.620> security<01:45:38.890> down<01:45:39.190> the 01:45:39.360 --> 01:45:39.370 align:start position:0% sack right what's the security down the 01:45:39.370 --> 01:45:41.310 align:start position:0% sack right what's the security down the stack<01:45:39.610> ain't<01:45:39.910> gonna<01:45:40.030> make<01:45:40.210> you<01:45:40.330> money<01:45:40.480> in<01:45:40.900> the 01:45:41.310 --> 01:45:41.320 align:start position:0% stack ain't gonna make you money in the 01:45:41.320 --> 01:45:44.310 align:start position:0% stack ain't gonna make you money in the traditional<01:45:41.830> way<01:45:41.980> right<01:45:42.310> so<01:45:43.050> the<01:45:44.050> interesting 01:45:44.310 --> 01:45:44.320 align:start position:0% traditional way right so the interesting 01:45:44.320 --> 01:45:49.040 align:start position:0% traditional way right so the interesting question<01:45:44.920> is<01:45:45.070> can<01:45:45.340> we<01:45:45.490> come<01:45:45.760> up<01:45:45.790> with<01:45:47.400> novel 01:45:49.040 --> 01:45:49.050 align:start position:0% question is can we come up with novel 01:45:49.050 --> 01:45:52.790 align:start position:0% question is can we come up with novel collaborative<01:45:50.280> business<01:45:51.280> models<01:45:51.940> that<01:45:52.300> allow 01:45:52.790 --> 01:45:52.800 align:start position:0% collaborative business models that allow 01:45:52.800 --> 01:45:56.130 align:start position:0% collaborative business models that allow revenue<01:45:53.800> share<01:45:54.040> that<01:45:54.400> combines<01:45:55.140> players 01:45:56.130 --> 01:45:56.140 align:start position:0% revenue share that combines players 01:45:56.140 --> 01:45:58.940 align:start position:0% revenue share that combines players across<01:45:56.590> the<01:45:56.890> stack<01:45:57.100> so<01:45:57.460> from<01:45:58.330> the<01:45:58.450> enabler 01:45:58.940 --> 01:45:58.950 align:start position:0% across the stack so from the enabler 01:45:58.950 --> 01:46:01.530 align:start position:0% across the stack so from the enabler infrastructure<01:45:59.950> all<01:46:00.310> the<01:46:00.670> way<01:46:00.790> to<01:46:01.420> the 01:46:01.530 --> 01:46:01.540 align:start position:0% infrastructure all the way to the 01:46:01.540 --> 01:46:05.070 align:start position:0% infrastructure all the way to the application<01:46:02.490> and<01:46:03.490> distributor<01:46:03.970> level<01:46:04.360> that 01:46:05.070 --> 01:46:05.080 align:start position:0% application and distributor level that 01:46:05.080 --> 01:46:08.100 align:start position:0% application and distributor level that you<01:46:05.710> can<01:46:05.980> create<01:46:06.400> novel<01:46:07.150> solutions<01:46:07.750> that 01:46:08.100 --> 01:46:08.110 align:start position:0% you can create novel solutions that 01:46:08.110 --> 01:46:11.970 align:start position:0% you can create novel solutions that solve<01:46:09.870> currently<01:46:10.870> intractable<01:46:11.440> problems 01:46:11.970 --> 01:46:11.980 align:start position:0% solve currently intractable problems 01:46:11.980 --> 01:46:14.070 align:start position:0% solve currently intractable problems that<01:46:12.640> are<01:46:12.760> high<01:46:12.940> value<01:46:13.390> for<01:46:13.690> the<01:46:13.780> end<01:46:13.930> consumer 01:46:14.070 --> 01:46:14.080 align:start position:0% that are high value for the end consumer 01:46:14.080 --> 01:46:15.720 align:start position:0% that are high value for the end consumer and<01:46:14.560> that<01:46:14.680> they're<01:46:14.830> willing<01:46:14.920> to<01:46:15.130> pay<01:46:15.250> for<01:46:15.610> and 01:46:15.720 --> 01:46:15.730 align:start position:0% and that they're willing to pay for and 01:46:15.730 --> 01:46:21.750 align:start position:0% and that they're willing to pay for and therefore<01:46:15.880> everybody<01:46:16.510> gets<01:46:16.750> a<01:46:18.750> gets<01:46:19.750> a<01:46:19.870> cut<01:46:20.760> so 01:46:21.750 --> 01:46:21.760 align:start position:0% therefore everybody gets a gets a cut so 01:46:21.760 --> 01:46:23.520 align:start position:0% therefore everybody gets a gets a cut so rather<01:46:22.090> than<01:46:22.330> having<01:46:22.660> the<01:46:22.960> ones<01:46:23.110> down<01:46:23.350> there 01:46:23.520 --> 01:46:23.530 align:start position:0% rather than having the ones down there 01:46:23.530 --> 01:46:25.710 align:start position:0% rather than having the ones down there be<01:46:24.010> a<01:46:24.040> thousand<01:46:24.580> X<01:46:24.730> lower<01:46:24.970> than<01:46:25.240> the<01:46:25.330> ones<01:46:25.510> up 01:46:25.710 --> 01:46:25.720 align:start position:0% be a thousand X lower than the ones up 01:46:25.720 --> 01:46:28.410 align:start position:0% be a thousand X lower than the ones up there<01:46:26.200> you<01:46:26.380> spread<01:46:26.740> the<01:46:26.860> wealth<01:46:27.040> a<01:46:27.370> little<01:46:28.270> bit 01:46:28.410 --> 01:46:28.420 align:start position:0% there you spread the wealth a little bit 01:46:28.420 --> 01:46:32.360 align:start position:0% there you spread the wealth a little bit and<01:46:28.620> incentivize<01:46:29.620> therefore<01:46:30.900> right 01:46:32.360 --> 01:46:32.370 align:start position:0% and incentivize therefore right 01:46:32.370 --> 01:46:34.410 align:start position:0% and incentivize therefore right collaboration<01:46:33.370> because<01:46:33.670> there's<01:46:33.940> there's 01:46:34.410 --> 01:46:34.420 align:start position:0% collaboration because there's there's 01:46:34.420 --> 01:46:41.280 align:start position:0% collaboration because there's there's more<01:46:34.930> to<01:46:35.260> to<01:46:36.360> go<01:46:37.360> around<01:46:39.840> okay<01:46:40.840> my<01:46:41.230> next 01:46:41.280 --> 01:46:41.290 align:start position:0% more to to go around okay my next 01:46:41.290 --> 01:46:44.190 align:start position:0% more to to go around okay my next question<01:46:41.830> is<01:46:42.090> what<01:46:43.090> is<01:46:43.120> trusted<01:46:43.690> compute 01:46:44.190 --> 01:46:44.200 align:start position:0% question is what is trusted compute 01:46:44.200 --> 01:46:46.830 align:start position:0% question is what is trusted compute allow<01:46:44.800> aetherium<01:46:45.220> to<01:46:46.090> do<01:46:46.210> that<01:46:46.390> it<01:46:46.480> can't 01:46:46.830 --> 01:46:46.840 align:start position:0% allow aetherium to do that it can't 01:46:46.840 --> 01:46:54.030 align:start position:0% allow aetherium to do that it can't already<01:46:47.080> do<01:46:52.110> if<01:46:53.110> we<01:46:53.320> look<01:46:53.470> on<01:46:53.560> main<01:46:53.800> it 01:46:54.030 --> 01:46:54.040 align:start position:0% already do if we look on main it 01:46:54.040 --> 01:46:56.940 align:start position:0% already do if we look on main it actually<01:46:54.790> you<01:46:55.120> know<01:46:55.380> really<01:46:56.380> I<01:46:56.440> mean<01:46:56.680> beyond 01:46:56.940 --> 01:46:56.950 align:start position:0% actually you know really I mean beyond 01:46:56.950 --> 01:46:59.460 align:start position:0% actually you know really I mean beyond the<01:46:57.040> D<01:46:57.310> hype<01:46:57.550> if<01:46:58.270> we<01:46:58.510> look<01:46:58.660> at<01:46:58.810> the<01:46:58.960> concrete 01:46:59.460 --> 01:46:59.470 align:start position:0% the D hype if we look at the concrete 01:46:59.470 --> 01:47:03.720 align:start position:0% the D hype if we look at the concrete use<01:46:59.650> cases<01:46:59.920> or<01:47:00.160> smart<01:47:00.430> contrast<01:47:00.880> today<01:47:02.730> you 01:47:03.720 --> 01:47:03.730 align:start position:0% use cases or smart contrast today you 01:47:03.730 --> 01:47:05.160 align:start position:0% use cases or smart contrast today you have<01:47:03.850> a<01:47:03.880> big<01:47:04.150> chunk<01:47:04.360> which<01:47:04.660> is<01:47:04.840> decentralized 01:47:05.160 --> 01:47:05.170 align:start position:0% have a big chunk which is decentralized 01:47:05.170 --> 01:47:07.620 align:start position:0% have a big chunk which is decentralized exchanges<01:47:05.920> which<01:47:06.550> typically<01:47:07.030> don't<01:47:07.300> need<01:47:07.480> an 01:47:07.620 --> 01:47:07.630 align:start position:0% exchanges which typically don't need an 01:47:07.630 --> 01:47:09.990 align:start position:0% exchanges which typically don't need an Oracle<01:47:07.960> in<01:47:08.170> most<01:47:08.380> cases<01:47:08.640> so<01:47:09.640> they<01:47:09.730> don't<01:47:09.910> need 01:47:09.990 --> 01:47:10.000 align:start position:0% Oracle in most cases so they don't need 01:47:10.000 --> 01:47:14.300 align:start position:0% Oracle in most cases so they don't need any<01:47:10.180> extra<01:47:10.390> date<01:47:10.750> or<01:47:10.900> any<01:47:11.080> t<01:47:11.320> supported<01:47:12.130> data 01:47:14.300 --> 01:47:14.310 align:start position:0% any extra date or any t supported data 01:47:14.310 --> 01:47:18.290 align:start position:0% any extra date or any t supported data and<01:47:15.540> then<01:47:16.540> you<01:47:16.990> see<01:47:17.230> caming<01:47:17.710> and<01:47:17.890> gambling 01:47:18.290 --> 01:47:18.300 align:start position:0% and then you see caming and gambling 01:47:18.300 --> 01:47:22.110 align:start position:0% and then you see caming and gambling those<01:47:19.300> ones<01:47:19.570> typically<01:47:20.050> do<01:47:20.350> need<01:47:21.120> something 01:47:22.110 --> 01:47:22.120 align:start position:0% those ones typically do need something 01:47:22.120 --> 01:47:24.930 align:start position:0% those ones typically do need something like<01:47:22.360> that<01:47:22.540> so<01:47:22.930> I<01:47:23.290> think<01:47:23.770> the<01:47:24.190> the<01:47:24.220> biggest<01:47:24.730> use 01:47:24.930 --> 01:47:24.940 align:start position:0% like that so I think the the biggest use 01:47:24.940 --> 01:47:26.910 align:start position:0% like that so I think the the biggest use case<01:47:25.180> in<01:47:25.360> production<01:47:25.930> on<01:47:26.140> the<01:47:26.320> public<01:47:26.650> chain 01:47:26.910 --> 01:47:26.920 align:start position:0% case in production on the public chain 01:47:26.920 --> 01:47:30.210 align:start position:0% case in production on the public chain today<01:47:27.400> is<01:47:28.000> providing<01:47:28.660> randomness<01:47:29.220> like 01:47:30.210 --> 01:47:30.220 align:start position:0% today is providing randomness like 01:47:30.220 --> 01:47:32.100 align:start position:0% today is providing randomness like generating<01:47:30.790> some<01:47:31.030> external<01:47:31.450> randomness 01:47:32.100 --> 01:47:32.110 align:start position:0% generating some external randomness 01:47:32.110 --> 01:47:34.530 align:start position:0% generating some external randomness which<01:47:32.350> we're<01:47:32.860> -<01:47:33.610> will<01:47:34.060> not<01:47:34.180> be<01:47:34.360> able<01:47:34.420> to 01:47:34.530 --> 01:47:34.540 align:start position:0% which we're - will not be able to 01:47:34.540 --> 01:47:35.159 align:start position:0% which we're - will not be able to collude 01:47:35.159 --> 01:47:35.169 align:start position:0% collude 01:47:35.169 --> 01:47:40.080 align:start position:0% collude with<01:47:35.949> that<01:47:37.800> there<01:47:38.800> are<01:47:38.889> others<01:47:39.550> like<01:47:39.669> price 01:47:40.080 --> 01:47:40.090 align:start position:0% with that there are others like price 01:47:40.090 --> 01:47:42.959 align:start position:0% with that there are others like price fields<01:47:40.570> or<01:47:40.780> like<01:47:41.619> insurance<01:47:42.159> products<01:47:42.550> many 01:47:42.959 --> 01:47:42.969 align:start position:0% fields or like insurance products many 01:47:42.969 --> 01:47:45.889 align:start position:0% fields or like insurance products many others<01:47:43.300> like<01:47:43.409> we<01:47:44.409> have<01:47:44.499> seen<01:47:44.709> a<01:47:44.739> bunch<01:47:44.949> but 01:47:45.889 --> 01:47:45.899 align:start position:0% others like we have seen a bunch but 01:47:45.899 --> 01:47:48.359 align:start position:0% others like we have seen a bunch but this<01:47:46.899> is<01:47:47.079> the<01:47:47.260> this<01:47:47.709> is<01:47:47.860> still<01:47:48.070> having<01:47:48.340> a 01:47:48.359 --> 01:47:48.369 align:start position:0% this is the this is still having a 01:47:48.369 --> 01:47:50.639 align:start position:0% this is the this is still having a limited<01:47:48.729> traction<01:47:49.360> on<01:47:49.630> test<01:47:50.199> night<01:47:50.409> there<01:47:50.559> is 01:47:50.639 --> 01:47:50.649 align:start position:0% limited traction on test night there is 01:47:50.649 --> 01:47:52.469 align:start position:0% limited traction on test night there is much<01:47:50.829> more<01:47:50.949> variance<01:47:51.309> on<01:47:51.459> private<01:47:51.999> chains<01:47:52.239> I'm 01:47:52.469 --> 01:47:52.479 align:start position:0% much more variance on private chains I'm 01:47:52.479 --> 01:47:54.330 align:start position:0% much more variance on private chains I'm sure<01:47:52.689> other<01:47:53.199> people<01:47:53.559> on<01:47:53.649> the<01:47:53.739> panel<01:47:53.889> here<01:47:54.159> will 01:47:54.330 --> 01:47:54.340 align:start position:0% sure other people on the panel here will 01:47:54.340 --> 01:47:56.310 align:start position:0% sure other people on the panel here will be<01:47:54.459> able<01:47:54.550> to<01:47:54.729> share<01:47:54.909> their<01:47:55.059> experience<01:47:55.510> there 01:47:56.310 --> 01:47:56.320 align:start position:0% be able to share their experience there 01:47:56.320 --> 01:47:58.259 align:start position:0% be able to share their experience there are<01:47:56.380> so<01:47:56.800> many<01:47:56.979> different<01:47:57.340> use<01:47:57.459> cases<01:47:57.669> but<01:47:57.939> the 01:47:58.259 --> 01:47:58.269 align:start position:0% are so many different use cases but the 01:47:58.269 --> 01:47:59.429 align:start position:0% are so many different use cases but the reality<01:47:58.599> is<01:47:58.630> that<01:47:58.689> it<01:47:58.959> depends<01:47:59.229> on<01:47:59.320> the 01:47:59.429 --> 01:47:59.439 align:start position:0% reality is that it depends on the 01:47:59.439 --> 01:48:01.949 align:start position:0% reality is that it depends on the context<01:47:59.860> and<01:48:00.119> randomness<01:48:01.119> is<01:48:01.300> something<01:48:01.630> huge 01:48:01.949 --> 01:48:01.959 align:start position:0% context and randomness is something huge 01:48:01.959 --> 01:48:05.100 align:start position:0% context and randomness is something huge on<01:48:02.199> the<01:48:02.739> theorem<01:48:03.130> may<01:48:03.909> net<01:48:04.179> on<01:48:04.389> the<01:48:04.840> public 01:48:05.100 --> 01:48:05.110 align:start position:0% on the theorem may net on the public 01:48:05.110 --> 01:48:06.359 align:start position:0% on the theorem may net on the public chain<01:48:05.320> while<01:48:05.590> it's<01:48:05.769> probably<01:48:06.130> something 01:48:06.359 --> 01:48:06.369 align:start position:0% chain while it's probably something 01:48:06.369 --> 01:48:09.569 align:start position:0% chain while it's probably something really<01:48:07.209> small<01:48:07.510> or<01:48:07.719> negligible<01:48:08.019> on<01:48:08.579> consortium 01:48:09.569 --> 01:48:09.579 align:start position:0% really small or negligible on consortium 01:48:09.579 --> 01:48:15.449 align:start position:0% really small or negligible on consortium chains<01:48:09.849> I<01:48:10.889> have<01:48:11.889> a<01:48:11.919> comment<01:48:12.510> related<01:48:13.510> but<01:48:14.459> it's 01:48:15.449 --> 01:48:15.459 align:start position:0% chains I have a comment related but it's 01:48:15.459 --> 01:48:23.009 align:start position:0% chains I have a comment related but it's about<01:48:15.749> that<01:48:16.749> we<01:48:16.989> keep<01:48:18.539> some<01:48:20.159> good<01:48:21.159> view<01:48:21.429> on<01:48:22.019> how 01:48:23.009 --> 01:48:23.019 align:start position:0% about that we keep some good view on how 01:48:23.019 --> 01:48:25.350 align:start position:0% about that we keep some good view on how much<01:48:23.260> we<01:48:23.709> can<01:48:23.739> really<01:48:24.099> get<01:48:24.820> from<01:48:25.149> those 01:48:25.350 --> 01:48:25.360 align:start position:0% much we can really get from those 01:48:25.360 --> 01:48:28.560 align:start position:0% much we can really get from those various<01:48:26.079> key<01:48:26.409> technologies<01:48:27.130> versus<01:48:27.610> how<01:48:28.389> much 01:48:28.560 --> 01:48:28.570 align:start position:0% various key technologies versus how much 01:48:28.570 --> 01:48:30.439 align:start position:0% various key technologies versus how much we<01:48:28.719> should<01:48:28.749> be<01:48:28.959> reserved<01:48:29.499> about<01:48:29.619> them<01:48:29.949> because 01:48:30.439 --> 01:48:30.449 align:start position:0% we should be reserved about them because 01:48:30.449 --> 01:48:34.620 align:start position:0% we should be reserved about them because we<01:48:32.099> use<01:48:33.099> cases<01:48:33.429> how<01:48:33.849> it<01:48:33.999> solves<01:48:34.329> all<01:48:34.510> the 01:48:34.620 --> 01:48:34.630 align:start position:0% we use cases how it solves all the 01:48:34.630 --> 01:48:37.379 align:start position:0% we use cases how it solves all the problem<01:48:35.079> we<01:48:35.199> treat<01:48:35.439> those<01:48:36.130> as<01:48:36.550> jigs<01:48:36.969> and<01:48:37.149> clubs 01:48:37.379 --> 01:48:37.389 align:start position:0% problem we treat those as jigs and clubs 01:48:37.389 --> 01:48:39.330 align:start position:0% problem we treat those as jigs and clubs or<01:48:37.599> other<01:48:37.719> enclaves<01:48:38.110> this<01:48:38.409> magical<01:48:38.829> black<01:48:39.099> box 01:48:39.330 --> 01:48:39.340 align:start position:0% or other enclaves this magical black box 01:48:39.340 --> 01:48:41.549 align:start position:0% or other enclaves this magical black box is<01:48:39.550> protecting<01:48:40.059> our<01:48:40.209> powers<01:48:40.630> but<01:48:40.809> in<01:48:40.959> reality 01:48:41.549 --> 01:48:41.559 align:start position:0% is protecting our powers but in reality 01:48:41.559 --> 01:48:45.419 align:start position:0% is protecting our powers but in reality we<01:48:42.159> always<01:48:42.519> should<01:48:42.729> know<01:48:43.300> that<01:48:43.570> they<01:48:44.499> can<01:48:45.219> only 01:48:45.419 --> 01:48:45.429 align:start position:0% we always should know that they can only 01:48:45.429 --> 01:48:48.629 align:start position:0% we always should know that they can only offer<01:48:45.610> limited<01:48:46.239> protection<01:48:46.749> and<01:48:47.469> for<01:48:48.399> example 01:48:48.629 --> 01:48:48.639 align:start position:0% offer limited protection and for example 01:48:48.639 --> 01:48:54.419 align:start position:0% offer limited protection and for example I<01:48:48.880> quickly<01:48:49.149> looked<01:48:49.389> at<01:48:49.689> the<01:48:52.439> e05<01:48:53.439> spec<01:48:53.860> this 01:48:54.419 --> 01:48:54.429 align:start position:0% I quickly looked at the e05 spec this 01:48:54.429 --> 01:48:56.549 align:start position:0% I quickly looked at the e05 spec this morning<01:48:54.820> and<01:48:55.689> at<01:48:55.869> no<01:48:56.019> point<01:48:56.050> there<01:48:56.439> was 01:48:56.549 --> 01:48:56.559 align:start position:0% morning and at no point there was 01:48:56.559 --> 01:48:58.409 align:start position:0% morning and at no point there was explicitly<01:48:57.249> stated<01:48:57.340> that<01:48:57.880> we<01:48:58.059> should<01:48:58.209> always 01:48:58.409 --> 01:48:58.419 align:start position:0% explicitly stated that we should always 01:48:58.419 --> 01:49:01.049 align:start position:0% explicitly stated that we should always probably<01:48:58.989> give<01:48:59.559> some<01:48:59.829> time<01:49:00.159> limit<01:49:00.519> on<01:49:00.729> the 01:49:01.049 --> 01:49:01.059 align:start position:0% probably give some time limit on the 01:49:01.059 --> 01:49:03.540 align:start position:0% probably give some time limit on the longevity<01:49:01.570> of<01:49:02.139> secret<01:49:02.590> that<01:49:02.889> our<01:49:02.949> enclaves 01:49:03.540 --> 01:49:03.550 align:start position:0% longevity of secret that our enclaves 01:49:03.550 --> 01:49:08.069 align:start position:0% longevity of secret that our enclaves process<01:49:04.419> and<01:49:06.389> because<01:49:07.389> of<01:49:07.539> various<01:49:07.869> things 01:49:08.069 --> 01:49:08.079 align:start position:0% process and because of various things 01:49:08.079 --> 01:49:09.449 align:start position:0% process and because of various things because<01:49:08.439> there<01:49:08.709> are<01:49:08.800> attacks<01:49:09.249> like 01:49:09.449 --> 01:49:09.459 align:start position:0% because there are attacks like 01:49:09.459 --> 01:49:11.279 align:start position:0% because there are attacks like foreshadow<01:49:09.969> but<01:49:10.360> also<01:49:10.539> because<01:49:10.959> there<01:49:11.139> are 01:49:11.279 --> 01:49:11.289 align:start position:0% foreshadow but also because there are 01:49:11.289 --> 01:49:14.399 align:start position:0% foreshadow but also because there are and<01:49:11.649> there<01:49:11.919> will<01:49:12.130> always<01:49:12.429> be<01:49:12.869> side<01:49:13.869> channels 01:49:14.399 --> 01:49:14.409 align:start position:0% and there will always be side channels 01:49:14.409 --> 01:49:18.389 align:start position:0% and there will always be side channels which<01:49:15.099> means<01:49:15.399> that<01:49:15.729> we<01:49:15.999> cannot<01:49:16.479> be<01:49:17.050> so<01:49:17.619> so 01:49:18.389 --> 01:49:18.399 align:start position:0% which means that we cannot be so so 01:49:18.399 --> 01:49:20.370 align:start position:0% which means that we cannot be so so excited<01:49:18.999> about<01:49:19.239> using<01:49:19.809> that<01:49:19.959> for<01:49:20.229> just 01:49:20.370 --> 01:49:20.380 align:start position:0% excited about using that for just 01:49:20.380 --> 01:49:23.310 align:start position:0% excited about using that for just protecting<01:49:20.979> any<01:49:21.280> kind<01:49:21.610> of<01:49:21.760> secrets<01:49:22.360> but<01:49:23.019> more 01:49:23.310 --> 01:49:23.320 align:start position:0% protecting any kind of secrets but more 01:49:23.320 --> 01:49:25.409 align:start position:0% protecting any kind of secrets but more like<01:49:23.530> the<01:49:23.559> only<01:49:23.949> very<01:49:24.280> short-lived<01:49:24.760> secrets 01:49:25.409 --> 01:49:25.419 align:start position:0% like the only very short-lived secrets 01:49:25.419 --> 01:49:27.979 align:start position:0% like the only very short-lived secrets which<01:49:25.630> will<01:49:25.840> likely<01:49:26.169> limit<01:49:26.949> the<01:49:27.189> amount<01:49:27.489> of 01:49:27.979 --> 01:49:27.989 align:start position:0% which will likely limit the amount of 01:49:27.989 --> 01:49:35.729 align:start position:0% which will likely limit the amount of usable<01:49:28.989> applications<01:49:29.949> quite<01:49:30.939> significantly 01:49:35.729 --> 01:49:35.739 align:start position:0% 01:49:35.739 --> 01:49:38.310 align:start position:0% oh<01:49:35.770> no<01:49:36.250> I<01:49:36.280> haven't<01:49:36.520> seen<01:49:36.880> a<01:49:36.910> Faraday<01:49:37.390> cage<01:49:37.420> in<01:49:37.900> a 01:49:38.310 --> 01:49:38.320 align:start position:0% oh no I haven't seen a Faraday cage in a 01:49:38.320 --> 01:49:43.550 align:start position:0% oh no I haven't seen a Faraday cage in a Microsoft<01:49:38.830> data<01:49:39.040> center<01:49:39.340> yet<01:49:39.550> but<01:49:40.300> you<01:49:41.050> know 01:49:43.550 --> 01:49:43.560 align:start position:0% 01:49:43.560 --> 01:49:47.700 align:start position:0% what<01:49:45.060> like<01:49:46.060> you<01:49:46.090> you<01:49:46.510> you<01:49:46.540> you<01:49:47.260> you<01:49:47.290> made<01:49:47.680> a 01:49:47.700 --> 01:49:47.710 align:start position:0% what like you you you you you made a 01:49:47.710 --> 01:49:50.250 align:start position:0% what like you you you you you made a successful<01:49:48.130> side<01:49:48.460> channel<01:49:49.170> attacking<01:49:50.170> at 01:49:50.250 --> 01:49:50.260 align:start position:0% successful side channel attacking at 01:49:50.260 --> 01:50:01.140 align:start position:0% successful side channel attacking at Starbucks<01:49:53.430> yeah<01:49:54.430> oh<01:49:54.760> no<01:49:55.860> no<01:49:56.860> all<01:49:57.219> right<01:50:00.120> now<01:50:01.120> I 01:50:01.140 --> 01:50:01.150 align:start position:0% Starbucks yeah oh no no all right now I 01:50:01.150 --> 01:50:04.470 align:start position:0% Starbucks yeah oh no no all right now I think<01:50:01.300> Amanda's<01:50:01.810> so<01:50:02.340> you<01:50:03.340> mock<01:50:03.580> my<01:50:03.790> angry 01:50:04.470 --> 01:50:04.480 align:start position:0% think Amanda's so you mock my angry 01:50:04.480 --> 01:50:06.270 align:start position:0% think Amanda's so you mock my angry argument<01:50:04.870> because<01:50:05.170> saying<01:50:05.710> that<01:50:05.860> there's<01:50:06.070> no 01:50:06.270 --> 01:50:06.280 align:start position:0% argument because saying that there's no 01:50:06.280 --> 01:50:08.760 align:start position:0% argument because saying that there's no hedges<01:50:07.150> in<01:50:07.480> in<01:50:07.750> data<01:50:07.989> centers<01:50:08.469> but<01:50:08.710> they 01:50:08.760 --> 01:50:08.770 align:start position:0% hedges in in data centers but they 01:50:08.770 --> 01:50:12.900 align:start position:0% hedges in in data centers but they doesn't<01:50:09.160> is<01:50:09.430> running<01:50:09.820> I<01:50:10.000> somehow<01:50:11.910> perhaps 01:50:12.900 --> 01:50:12.910 align:start position:0% doesn't is running I somehow perhaps 01:50:12.910 --> 01:50:15.810 align:start position:0% doesn't is running I somehow perhaps willing<01:50:13.570> to<01:50:13.750> trust<01:50:13.989> Microsoft<01:50:14.770> slightly<01:50:15.550> more 01:50:15.810 --> 01:50:15.820 align:start position:0% willing to trust Microsoft slightly more 01:50:15.820 --> 01:50:17.850 align:start position:0% willing to trust Microsoft slightly more than<01:50:15.850> just<01:50:16.300> a<01:50:16.420> random<01:50:16.870> person<01:50:17.050> running<01:50:17.620> some 01:50:17.850 --> 01:50:17.860 align:start position:0% than just a random person running some 01:50:17.860 --> 01:50:22.140 align:start position:0% than just a random person running some et<01:50:18.130> room<01:50:18.370> note<01:50:18.610> it's<01:50:19.090> a<01:50:19.560> note<01:50:20.560> okay<01:50:21.370> running<01:50:21.880> by 01:50:22.140 --> 01:50:22.150 align:start position:0% et room note it's a note okay running by 01:50:22.150 --> 01:50:24.830 align:start position:0% et room note it's a note okay running by whoever<01:50:22.690> and<01:50:23.020> which<01:50:23.830> so<01:50:24.040> we<01:50:24.160> should<01:50:24.310> be<01:50:24.460> very 01:50:24.830 --> 01:50:24.840 align:start position:0% whoever and which so we should be very 01:50:24.840 --> 01:50:29.760 align:start position:0% whoever and which so we should be very cautious<01:50:25.840> about<01:50:26.760> trusting<01:50:27.760> this<01:50:28.770> whatever 01:50:29.760 --> 01:50:29.770 align:start position:0% cautious about trusting this whatever 01:50:29.770 --> 01:50:33.150 align:start position:0% cautious about trusting this whatever now<01:50:30.070> to<01:50:30.130> a<01:50:30.340> SGX<01:50:31.060> note<01:50:31.350> because<01:50:32.350> this<01:50:32.770> is<01:50:32.920> not 01:50:33.150 --> 01:50:33.160 align:start position:0% now to a SGX note because this is not 01:50:33.160 --> 01:50:37.320 align:start position:0% now to a SGX note because this is not just<01:50:33.660> as<01:50:34.920> it's<01:50:35.920> not<01:50:36.130> like<01:50:36.430> that<01:50:36.640> cage<01:50:36.969> okay 01:50:37.320 --> 01:50:37.330 align:start position:0% just as it's not like that cage okay 01:50:37.330 --> 01:50:40.860 align:start position:0% just as it's not like that cage okay it's<01:50:38.020> it<01:50:38.380> can<01:50:38.710> maybe<01:50:39.550> protect<01:50:40.150> us<01:50:40.300> for<01:50:40.570> maybe 01:50:40.860 --> 01:50:40.870 align:start position:0% it's it can maybe protect us for maybe 01:50:40.870 --> 01:50:43.140 align:start position:0% it's it can maybe protect us for maybe five<01:50:41.200> minutes<01:50:41.380> maybe<01:50:41.770> five<01:50:42.040> hours<01:50:42.250> our 01:50:43.140 --> 01:50:43.150 align:start position:0% five minutes maybe five hours our 01:50:43.150 --> 01:50:46.110 align:start position:0% five minutes maybe five hours our secrets<01:50:43.800> maybe<01:50:44.800> five<01:50:45.130> weeks<01:50:45.400> I<01:50:45.670> don't<01:50:45.940> know 01:50:46.110 --> 01:50:46.120 align:start position:0% secrets maybe five weeks I don't know 01:50:46.120 --> 01:50:47.970 align:start position:0% secrets maybe five weeks I don't know that's<01:50:46.540> probably<01:50:46.930> we<01:50:47.350> need<01:50:47.469> some<01:50:47.680> kind<01:50:47.830> of 01:50:47.970 --> 01:50:47.980 align:start position:0% that's probably we need some kind of 01:50:47.980 --> 01:50:51.150 align:start position:0% that's probably we need some kind of metric<01:50:48.310> to<01:50:48.820> do<01:50:49.450> that<01:50:49.690> so<01:50:50.620> that<01:50:51.010> our 01:50:51.150 --> 01:50:51.160 align:start position:0% metric to do that so that our 01:50:51.160 --> 01:50:53.459 align:start position:0% metric to do that so that our applications<01:50:51.940> can<01:50:52.150> be<01:50:52.300> designed<01:50:52.750> in<01:50:53.020> a<01:50:53.050> way<01:50:53.200> in 01:50:53.459 --> 01:50:53.469 align:start position:0% applications can be designed in a way in 01:50:53.469 --> 01:50:56.640 align:start position:0% applications can be designed in a way in a<01:50:53.590> way<01:50:53.739> taking<01:50:54.370> this<01:50:54.489> into<01:50:54.700> account<01:50:55.530> so<01:50:56.530> that's 01:50:56.640 --> 01:50:56.650 align:start position:0% a way taking this into account so that's 01:50:56.650 --> 01:50:59.520 align:start position:0% a way taking this into account so that's why<01:50:56.860> you<01:50:56.920> need<01:50:57.130> to<01:50:57.280> try<01:50:57.460> to<01:50:57.520> hack<01:50:57.820> a<01:50:58.060> 80<01:50:58.900> at 01:50:59.520 --> 01:50:59.530 align:start position:0% why you need to try to hack a 80 at 01:50:59.530 --> 01:51:02.100 align:start position:0% why you need to try to hack a 80 at Starbucks<01:51:00.160> to<01:51:00.370> see<01:51:00.850> what<01:51:01.060> it<01:51:01.180> takes<01:51:01.390> such<01:51:01.900> that 01:51:02.100 --> 01:51:02.110 align:start position:0% Starbucks to see what it takes such that 01:51:02.110 --> 01:51:03.750 align:start position:0% Starbucks to see what it takes such that you<01:51:02.230> can<01:51:02.410> actually<01:51:02.800> give<01:51:02.980> those<01:51:03.160> metrics<01:51:03.640> you 01:51:03.750 --> 01:51:03.760 align:start position:0% you can actually give those metrics you 01:51:03.760 --> 01:51:08.280 align:start position:0% you can actually give those metrics you need<01:51:03.940> to<01:51:04.030> run<01:51:04.150> experiment<01:51:04.690> I<01:51:07.020> just<01:51:08.020> want<01:51:08.200> to 01:51:08.280 --> 01:51:08.290 align:start position:0% need to run experiment I just want to 01:51:08.290 --> 01:51:11.190 align:start position:0% need to run experiment I just want to say<01:51:08.410> one<01:51:08.590> thing<01:51:08.620> is<01:51:08.860> that<01:51:09.719> like<01:51:10.719> anything<01:51:10.960> in 01:51:11.190 --> 01:51:11.200 align:start position:0% say one thing is that like anything in 01:51:11.200 --> 01:51:17.490 align:start position:0% say one thing is that like anything in anything<01:51:12.130> in<01:51:12.430> software<01:51:12.960> it<01:51:13.960> is<01:51:15.120> till<01:51:16.120> it's<01:51:16.500> not 01:51:17.490 --> 01:51:17.500 align:start position:0% anything in software it is till it's not 01:51:17.500 --> 01:51:20.970 align:start position:0% anything in software it is till it's not broken<01:51:17.830> it's<01:51:18.100> not<01:51:18.370> you<01:51:18.940> know<01:51:19.710> at<01:51:20.710> some<01:51:20.920> point 01:51:20.970 --> 01:51:20.980 align:start position:0% broken it's not you know at some point 01:51:20.980 --> 01:51:23.340 align:start position:0% broken it's not you know at some point in<01:51:21.250> time<01:51:21.310> it<01:51:21.640> everything<01:51:22.180> will<01:51:22.600> be<01:51:22.780> broken<01:51:23.020> and 01:51:23.340 --> 01:51:23.350 align:start position:0% in time it everything will be broken and 01:51:23.350 --> 01:51:26.760 align:start position:0% in time it everything will be broken and even<01:51:23.680> when<01:51:23.830> we<01:51:24.040> talk<01:51:24.190> about<01:51:24.250> this<01:51:24.700> whole<01:51:25.770> you 01:51:26.760 --> 01:51:26.770 align:start position:0% even when we talk about this whole you 01:51:26.770 --> 01:51:29.850 align:start position:0% even when we talk about this whole you know<01:51:26.830> crypto<01:51:27.280> economics<01:51:27.730> based<01:51:28.860> solutions 01:51:29.850 --> 01:51:29.860 align:start position:0% know crypto economics based solutions 01:51:29.860 --> 01:51:32.160 align:start position:0% know crypto economics based solutions they<01:51:30.190> also<01:51:30.370> have<01:51:30.670> their<01:51:30.850> parameters<01:51:31.180> between 01:51:32.160 --> 01:51:32.170 align:start position:0% they also have their parameters between 01:51:32.170 --> 01:51:33.660 align:start position:0% they also have their parameters between which<01:51:32.410> they<01:51:32.650> work<01:51:32.890> and<01:51:33.040> beyond<01:51:33.340> which<01:51:33.489> they 01:51:33.660 --> 01:51:33.670 align:start position:0% which they work and beyond which they 01:51:33.670 --> 01:51:36.810 align:start position:0% which they work and beyond which they start<01:51:34.360> to<01:51:34.540> fail<01:51:35.250> you<01:51:36.250> know<01:51:36.340> how<01:51:36.460> much<01:51:36.640> should<01:51:36.790> I 01:51:36.810 --> 01:51:36.820 align:start position:0% start to fail you know how much should I 01:51:36.820 --> 01:51:38.870 align:start position:0% start to fail you know how much should I have<01:51:37.030> ants<01:51:37.300> take<01:51:37.480> and<01:51:37.780> how<01:51:38.170> much<01:51:38.350> should<01:51:38.500> I<01:51:38.560> get 01:51:38.870 --> 01:51:38.880 align:start position:0% have ants take and how much should I get 01:51:38.880 --> 01:51:41.310 align:start position:0% have ants take and how much should I get penalized<01:51:39.880> and<01:51:40.120> things<01:51:40.300> like<01:51:40.420> that<01:51:40.480> so<01:51:41.110> the 01:51:41.310 --> 01:51:41.320 align:start position:0% penalized and things like that so the 01:51:41.320 --> 01:51:43.650 align:start position:0% penalized and things like that so the the<01:51:42.100> point<01:51:42.130> I<01:51:42.430> want<01:51:42.610> to<01:51:42.640> make<01:51:42.790> is<01:51:42.969> like<01:51:43.000> there 01:51:43.650 --> 01:51:43.660 align:start position:0% the point I want to make is like there 01:51:43.660 --> 01:51:45.900 align:start position:0% the point I want to make is like there is<01:51:43.780> no<01:51:43.930> one<01:51:44.230> solution<01:51:44.860> that<01:51:45.430> is<01:51:45.610> a<01:51:45.640> silver 01:51:45.900 --> 01:51:45.910 align:start position:0% is no one solution that is a silver 01:51:45.910 --> 01:51:49.060 align:start position:0% is no one solution that is a silver bullet<01:51:46.030> for<01:51:46.739> everything<01:51:47.739> out 01:51:49.060 --> 01:51:49.070 align:start position:0% bullet for everything out 01:51:49.070 --> 01:51:51.310 align:start position:0% bullet for everything out depending<01:51:49.820> upon<01:51:49.880> the<01:51:50.150> use<01:51:50.330> case<01:51:50.570> it<01:51:50.810> is<01:51:50.960> a<01:51:50.990> mix 01:51:51.310 --> 01:51:51.320 align:start position:0% depending upon the use case it is a mix 01:51:51.320 --> 01:51:55.510 align:start position:0% depending upon the use case it is a mix of<01:51:51.650> a<01:51:52.340> solution<01:51:52.670> you<01:51:53.360> could<01:51:53.510> think<01:51:54.050> of<01:51:54.260> a<01:51:55.070> key 01:51:55.510 --> 01:51:55.520 align:start position:0% of a solution you could think of a key 01:51:55.520 --> 01:51:58.720 align:start position:0% of a solution you could think of a key based<01:51:56.090> T<01:51:56.750> combined<01:51:57.590> with<01:51:57.830> some<01:51:58.340> kind<01:51:58.550> of<01:51:58.610> a 01:51:58.720 --> 01:51:58.730 align:start position:0% based T combined with some kind of a 01:51:58.730 --> 01:52:00.940 align:start position:0% based T combined with some kind of a crypto<01:51:59.060> and<01:51:59.180> economics<01:51:59.930> so<01:52:00.350> there<01:52:00.710> are<01:52:00.830> these 01:52:00.940 --> 01:52:00.950 align:start position:0% crypto and economics so there are these 01:52:00.950 --> 01:52:02.530 align:start position:0% crypto and economics so there are these kinds<01:52:01.280> of<01:52:01.310> permutation<01:52:01.850> combinations<01:52:02.360> that 01:52:02.530 --> 01:52:02.540 align:start position:0% kinds of permutation combinations that 01:52:02.540 --> 01:52:05.020 align:start position:0% kinds of permutation combinations that we<01:52:02.690> have<01:52:02.840> to<01:52:02.960> think<01:52:03.140> and<01:52:03.550> always<01:52:04.550> think<01:52:04.760> about 01:52:05.020 --> 01:52:05.030 align:start position:0% we have to think and always think about 01:52:05.030 --> 01:52:08.980 align:start position:0% we have to think and always think about you<01:52:05.720> know<01:52:06.310> you<01:52:07.310> know<01:52:07.690> defense-in-depth<01:52:08.690> and 01:52:08.980 --> 01:52:08.990 align:start position:0% you know you know defense-in-depth and 01:52:08.990 --> 01:52:12.220 align:start position:0% you know you know defense-in-depth and not<01:52:09.950> how<01:52:10.340> one<01:52:11.060> point<01:52:11.390> of<01:52:11.570> failure 01:52:12.220 --> 01:52:12.230 align:start position:0% not how one point of failure 01:52:12.230 --> 01:52:14.380 align:start position:0% not how one point of failure anyways<01:52:12.650> that's<01:52:12.980> not<01:52:13.280> a<01:52:13.310> good<01:52:13.970> design<01:52:14.120> in 01:52:14.380 --> 01:52:14.390 align:start position:0% anyways that's not a good design in 01:52:14.390 --> 01:52:18.250 align:start position:0% anyways that's not a good design in general<01:52:14.630> so<01:52:16.000> T's<01:52:17.000> have<01:52:17.480> a<01:52:17.510> role<01:52:17.780> to<01:52:18.020> play<01:52:18.050> in 01:52:18.250 --> 01:52:18.260 align:start position:0% general so T's have a role to play in 01:52:18.260 --> 01:52:22.810 align:start position:0% general so T's have a role to play in there<01:52:18.620> but<01:52:19.160> knowing<01:52:19.970> over<01:52:20.750> wire<01:52:21.110> you<01:52:21.820> where 01:52:22.810 --> 01:52:22.820 align:start position:0% there but knowing over wire you where 01:52:22.820 --> 01:52:24.160 align:start position:0% there but knowing over wire you where you<01:52:22.940> should<01:52:23.120> apply<01:52:23.150> them<01:52:23.630> and<01:52:23.870> when<01:52:24.020> you 01:52:24.160 --> 01:52:24.170 align:start position:0% you should apply them and when you 01:52:24.170 --> 01:52:26.380 align:start position:0% you should apply them and when you should<01:52:24.440> be<01:52:24.470> basically<01:52:25.160> have<01:52:25.670> an<01:52:25.820> alternative 01:52:26.380 --> 01:52:26.390 align:start position:0% should be basically have an alternative 01:52:26.390 --> 01:52:30.850 align:start position:0% should be basically have an alternative is<01:52:26.630> part<01:52:27.110> of<01:52:27.230> the<01:52:27.500> system<01:52:28.070> design<01:52:29.710> okay<01:52:30.710> one 01:52:30.850 --> 01:52:30.860 align:start position:0% is part of the system design okay one 01:52:30.860 --> 01:52:33.540 align:start position:0% is part of the system design okay one last<01:52:31.010> thing<01:52:31.160> I<01:52:31.550> was<01:52:32.150> a<01:52:32.210> good<01:52:32.360> one<01:52:32.540> on<01:52:32.660> the<01:52:32.720> time 01:52:33.540 --> 01:52:33.550 align:start position:0% last thing I was a good one on the time 01:52:33.550 --> 01:52:36.790 align:start position:0% last thing I was a good one on the time limit<01:52:34.550> of<01:52:34.580> the<01:52:34.700> secrets<01:52:35.030> so<01:52:35.930> that's<01:52:36.380> the<01:52:36.530> the 01:52:36.790 --> 01:52:36.800 align:start position:0% limit of the secrets so that's the the 01:52:36.800 --> 01:52:39.430 align:start position:0% limit of the secrets so that's the the thing<01:52:37.010> as<01:52:37.190> we<01:52:37.730> start<01:52:38.000> to<01:52:38.120> do<01:52:38.270> these<01:52:38.390> things<01:52:38.630> no 01:52:39.430 --> 01:52:39.440 align:start position:0% thing as we start to do these things no 01:52:39.440 --> 01:52:41.820 align:start position:0% thing as we start to do these things no system<01:52:39.800> is<01:52:39.950> riskless 01:52:41.820 --> 01:52:41.830 align:start position:0% system is riskless 01:52:41.830 --> 01:52:44.350 align:start position:0% system is riskless risk<01:52:42.830> tolerances<01:52:43.400> you<01:52:43.730> live<01:52:43.940> with<01:52:44.060> it<01:52:44.120> right 01:52:44.350 --> 01:52:44.360 align:start position:0% risk tolerances you live with it right 01:52:44.360 --> 01:52:46.690 align:start position:0% risk tolerances you live with it right everybody<01:52:44.810> decided<01:52:45.170> to<01:52:45.230> do<01:52:45.350> this<01:52:45.500> if<01:52:45.860> you<01:52:46.280> had 01:52:46.690 --> 01:52:46.700 align:start position:0% everybody decided to do this if you had 01:52:46.700 --> 01:52:48.870 align:start position:0% everybody decided to do this if you had zero<01:52:47.060> risk<01:52:47.360> tolerance<01:52:47.810> you<01:52:47.930> would<01:52:48.050> get<01:52:48.230> a<01:52:48.260> bet 01:52:48.870 --> 01:52:48.880 align:start position:0% zero risk tolerance you would get a bet 01:52:48.880 --> 01:52:50.770 align:start position:0% zero risk tolerance you would get a bet anything<01:52:49.880> yeah<01:52:50.150> you<01:52:50.450> wouldn't<01:52:50.630> use<01:52:50.750> a 01:52:50.770 --> 01:52:50.780 align:start position:0% anything yeah you wouldn't use a 01:52:50.780 --> 01:52:52.330 align:start position:0% anything yeah you wouldn't use a toothbrush<01:52:51.290> especially<01:52:51.980> the<01:52:52.040> electric 01:52:52.330 --> 01:52:52.340 align:start position:0% toothbrush especially the electric 01:52:52.340 --> 01:52:55.120 align:start position:0% toothbrush especially the electric toothbrush<01:52:52.780> electric<01:52:53.780> razor<01:52:53.960> when<01:52:54.950> use<01:52:55.100> a 01:52:55.120 --> 01:52:55.130 align:start position:0% toothbrush electric razor when use a 01:52:55.130 --> 01:52:58.600 align:start position:0% toothbrush electric razor when use a razor<01:52:55.310> at<01:52:55.520> all<01:52:55.670> because<01:52:56.120> yourself<01:52:57.110> right<01:52:57.610> but 01:52:58.600 --> 01:52:58.610 align:start position:0% razor at all because yourself right but 01:52:58.610 --> 01:53:00.730 align:start position:0% razor at all because yourself right but it's<01:52:59.120> a<01:52:59.270> continuous<01:52:59.780> thing<01:52:59.810> and<01:53:00.410> you're 01:53:00.730 --> 01:53:00.740 align:start position:0% it's a continuous thing and you're 01:53:00.740 --> 01:53:03.520 align:start position:0% it's a continuous thing and you're pointing<01:53:01.130> out<01:53:01.220> a<01:53:01.250> great<01:53:02.020> attack<01:53:03.020> vector<01:53:03.380> that 01:53:03.520 --> 01:53:03.530 align:start position:0% pointing out a great attack vector that 01:53:03.530 --> 01:53:04.870 align:start position:0% pointing out a great attack vector that would<01:53:03.710> probably<01:53:03.890> didn't<01:53:04.190> think<01:53:04.250> about<01:53:04.640> was 01:53:04.870 --> 01:53:04.880 align:start position:0% would probably didn't think about was 01:53:04.880 --> 01:53:08.400 align:start position:0% would probably didn't think about was how<01:53:05.750> long<01:53:05.960> should<01:53:06.530> we<01:53:06.590> let<01:53:06.980> these<01:53:07.160> secrets 01:53:08.400 --> 01:53:08.410 align:start position:0% how long should we let these secrets 01:53:08.410 --> 01:53:11.320 align:start position:0% how long should we let these secrets survive<01:53:09.410> I<01:53:09.440> mean<01:53:09.830> we<01:53:10.010> at<01:53:10.250> Microsoft<01:53:10.430> we<01:53:10.880> rotate 01:53:11.320 --> 01:53:11.330 align:start position:0% survive I mean we at Microsoft we rotate 01:53:11.330 --> 01:53:11.920 align:start position:0% survive I mean we at Microsoft we rotate keys 01:53:11.920 --> 01:53:11.930 align:start position:0% keys 01:53:11.930 --> 01:53:13.840 align:start position:0% keys how<01:53:12.560> many<01:53:12.740> Microsoft<01:53:13.160> everybody<01:53:13.550> else<01:53:13.700> left 01:53:13.840 --> 01:53:13.850 align:start position:0% how many Microsoft everybody else left 01:53:13.850 --> 01:53:16.030 align:start position:0% how many Microsoft everybody else left in<01:53:13.970> the<01:53:14.090> room<01:53:14.210> for<01:53:14.420> Microsoft<01:53:14.900> you<01:53:15.770> have<01:53:15.920> to 01:53:16.030 --> 01:53:16.040 align:start position:0% in the room for Microsoft you have to 01:53:16.040 --> 01:53:19.600 align:start position:0% in the room for Microsoft you have to rotate<01:53:16.220> your<01:53:16.460> keys<01:53:17.290> all<01:53:18.290> the<01:53:18.650> time<01:53:18.890> and<01:53:19.250> it<01:53:19.400> is 01:53:19.600 --> 01:53:19.610 align:start position:0% rotate your keys all the time and it is 01:53:19.610 --> 01:53:22.240 align:start position:0% rotate your keys all the time and it is painful<01:53:19.970> I<01:53:20.870> mean<01:53:21.050> it's<01:53:21.260> like<01:53:21.440> when<01:53:21.920> we<01:53:22.010> have<01:53:22.160> to 01:53:22.240 --> 01:53:22.250 align:start position:0% painful I mean it's like when we have to 01:53:22.250 --> 01:53:24.850 align:start position:0% painful I mean it's like when we have to rotate<01:53:22.430> rotate<01:53:22.970> our<01:53:23.300> keys<01:53:23.480> on<01:53:23.660> our<01:53:23.780> systems<01:53:24.200> we 01:53:24.850 --> 01:53:24.860 align:start position:0% rotate rotate our keys on our systems we 01:53:24.860 --> 01:53:26.830 align:start position:0% rotate rotate our keys on our systems we have<01:53:25.100> to<01:53:25.190> prepare<01:53:25.400> for<01:53:25.880> two<01:53:26.030> weeks<01:53:26.300> when<01:53:26.810> we 01:53:26.830 --> 01:53:26.840 align:start position:0% have to prepare for two weeks when we 01:53:26.840 --> 01:53:29.250 align:start position:0% have to prepare for two weeks when we get<01:53:26.990> down<01:53:27.170> to<01:53:27.350> a<01:53:27.380> rocket<01:53:27.710> science<01:53:28.310> almost 01:53:29.250 --> 01:53:29.260 align:start position:0% get down to a rocket science almost 01:53:29.260 --> 01:53:32.530 align:start position:0% get down to a rocket science almost process<01:53:30.260> we<01:53:30.410> can't<01:53:30.710> just<01:53:30.830> hit<01:53:30.920> a<01:53:30.980> button<01:53:31.540> but 01:53:32.530 --> 01:53:32.540 align:start position:0% process we can't just hit a button but 01:53:32.540 --> 01:53:34.750 align:start position:0% process we can't just hit a button but we<01:53:32.810> add<01:53:32.990> the<01:53:33.200> t's<01:53:33.410> it<01:53:33.860> gets<01:53:34.070> even<01:53:34.310> more<01:53:34.340> complex 01:53:34.750 --> 01:53:34.760 align:start position:0% we add the t's it gets even more complex 01:53:34.760 --> 01:53:36.580 align:start position:0% we add the t's it gets even more complex especially<01:53:35.330> with<01:53:35.690> we<01:53:35.900> talk<01:53:36.050> about<01:53:36.170> watching 01:53:36.580 --> 01:53:36.590 align:start position:0% especially with we talk about watching 01:53:36.590 --> 01:53:40.150 align:start position:0% especially with we talk about watching keys<01:53:36.770> so<01:53:36.890> we<01:53:36.920> really<01:53:37.520> need<01:53:38.170> and<01:53:39.170> the<01:53:39.620> EA<01:53:39.800> and 01:53:40.150 --> 01:53:40.160 align:start position:0% keys so we really need and the EA and 01:53:40.160 --> 01:53:42.760 align:start position:0% keys so we really need and the EA and that's<01:53:40.310> the<01:53:40.490> the<01:53:40.910> greatness<01:53:41.120> of<01:53:41.450> the<01:53:42.350> benefit 01:53:42.760 --> 01:53:42.770 align:start position:0% that's the the greatness of the benefit 01:53:42.770 --> 01:53:44.830 align:start position:0% that's the the greatness of the benefit of<01:53:42.800> the<01:53:43.250> open<01:53:43.520> standards<01:53:43.760> is<01:53:44.060> we<01:53:44.210> put<01:53:44.690> some 01:53:44.830 --> 01:53:44.840 align:start position:0% of the open standards is we put some 01:53:44.840 --> 01:53:46.570 align:start position:0% of the open standards is we put some sunlight<01:53:45.080> on<01:53:45.320> these<01:53:45.470> things<01:53:45.770> and<01:53:46.310> we're<01:53:46.490> gonna 01:53:46.570 --> 01:53:46.580 align:start position:0% sunlight on these things and we're gonna 01:53:46.580 --> 01:53:48.400 align:start position:0% sunlight on these things and we're gonna get<01:53:46.760> great<01:53:47.090> feedback<01:53:47.330> from<01:53:47.780> collaborators 01:53:48.400 --> 01:53:48.410 align:start position:0% get great feedback from collaborators 01:53:48.410 --> 01:53:50.470 align:start position:0% get great feedback from collaborators that<01:53:48.560> really<01:53:48.920> sort<01:53:49.760> of<01:53:49.850> been<01:53:50.030> there<01:53:50.180> done<01:53:50.240> that 01:53:50.470 --> 01:53:50.480 align:start position:0% that really sort of been there done that 01:53:50.480 --> 01:53:52.390 align:start position:0% that really sort of been there done that and<01:53:50.720> know<01:53:51.080> you<01:53:51.410> know<01:53:51.500> you<01:53:51.920> might<01:53:52.070> not<01:53:52.250> know 01:53:52.390 --> 01:53:52.400 align:start position:0% and know you know you might not know 01:53:52.400 --> 01:53:53.860 align:start position:0% and know you know you might not know there<01:53:52.700> might<01:53:52.790> not<01:53:52.940> be<01:53:53.000> an<01:53:53.150> attack<01:53:53.390> vector<01:53:53.420> for 01:53:53.860 --> 01:53:53.870 align:start position:0% there might not be an attack vector for 01:53:53.870 --> 01:53:55.540 align:start position:0% there might not be an attack vector for it<01:53:53.960> now<01:53:54.320> but<01:53:54.740> who<01:53:54.860> knows<01:53:55.100> there<01:53:55.280> might<01:53:55.400> be<01:53:55.430> a 01:53:55.540 --> 01:53:55.550 align:start position:0% it now but who knows there might be a 01:53:55.550 --> 01:53:59.110 align:start position:0% it now but who knows there might be a long-lived<01:53:56.320> patient<01:53:57.700> patiently<01:53:58.700> planned 01:53:59.110 --> 01:53:59.120 align:start position:0% long-lived patient patiently planned 01:53:59.120 --> 01:54:02.230 align:start position:0% long-lived patient patiently planned attack<01:53:59.810> vector<01:54:00.200> that<01:54:00.410> will<01:54:00.680> if<01:54:01.610> you<01:54:01.910> have<01:54:02.060> too 01:54:02.230 --> 01:54:02.240 align:start position:0% attack vector that will if you have too 01:54:02.240 --> 01:54:02.590 align:start position:0% attack vector that will if you have too long 01:54:02.590 --> 01:54:02.600 align:start position:0% long 01:54:02.600 --> 01:54:05.380 align:start position:0% long wife<01:54:02.840> of<01:54:02.990> your<01:54:03.170> secret<01:54:03.590> it<01:54:04.460> will<01:54:04.610> be<01:54:04.730> a<01:54:04.760> ticking 01:54:05.380 --> 01:54:05.390 align:start position:0% wife of your secret it will be a ticking 01:54:05.390 --> 01:54:09.040 align:start position:0% wife of your secret it will be a ticking time<01:54:05.570> bomb<01:54:06.730> okay<01:54:07.730> last<01:54:08.030> question<01:54:08.270> what<01:54:08.810> should 01:54:09.040 --> 01:54:09.050 align:start position:0% time bomb okay last question what should 01:54:09.050 --> 01:54:12.120 align:start position:0% time bomb okay last question what should we<01:54:09.290> add<01:54:09.860> to<01:54:10.250> the<01:54:10.340> next<01:54:10.610> release<01:54:10.880> of<01:54:11.150> the 01:54:12.120 --> 01:54:12.130 align:start position:0% we add to the next release of the 01:54:12.130 --> 01:54:14.770 align:start position:0% we add to the next release of the trusted<01:54:13.130> execution<01:54:13.400> the<01:54:13.850> trecek<01:54:14.210> compute 01:54:14.770 --> 01:54:14.780 align:start position:0% trusted execution the trecek compute 01:54:14.780 --> 01:54:20.140 align:start position:0% trusted execution the trecek compute spec<01:54:16.120> okay<01:54:17.150> that's<01:54:17.780> the<01:54:18.080> question<01:54:18.350> about<01:54:19.150> what 01:54:20.140 --> 01:54:20.150 align:start position:0% spec okay that's the question about what 01:54:20.150 --> 01:54:21.880 align:start position:0% spec okay that's the question about what I<01:54:20.210> would<01:54:20.330> like<01:54:20.450> to<01:54:20.510> see<01:54:20.780> in<01:54:20.870> the<01:54:20.930> next<01:54:21.080> SGX<01:54:21.650> bag 01:54:21.880 --> 01:54:21.890 align:start position:0% I would like to see in the next SGX bag 01:54:21.890 --> 01:54:25.960 align:start position:0% I would like to see in the next SGX bag just<01:54:22.460> to<01:54:22.640> clarify<01:54:23.170> so<01:54:24.400> the<01:54:25.400> centralized 01:54:25.960 --> 01:54:25.970 align:start position:0% just to clarify so the centralized 01:54:25.970 --> 01:54:28.840 align:start position:0% just to clarify so the centralized remote<01:54:26.420> at<01:54:26.540> the<01:54:26.570> station<01:54:27.140> just<01:54:27.740> nothing<01:54:28.580> fast 01:54:28.840 --> 01:54:28.850 align:start position:0% remote at the station just nothing fast 01:54:28.850 --> 01:54:31.000 align:start position:0% remote at the station just nothing fast you<01:54:28.970> just<01:54:29.180> do<01:54:29.330> it<01:54:29.480> like<01:54:29.690> like<01:54:30.080> like<01:54:30.590> we<01:54:30.770> had 01:54:31.000 --> 01:54:31.010 align:start position:0% you just do it like like like we had 01:54:31.010 --> 01:54:33.400 align:start position:0% you just do it like like like we had with<01:54:31.280> this<01:54:31.640> eg<01:54:31.790> TPM<01:54:32.390> the<01:54:32.720> all<01:54:32.870> times 01:54:33.400 --> 01:54:33.410 align:start position:0% with this eg TPM the all times 01:54:33.410 --> 01:54:35.290 align:start position:0% with this eg TPM the all times everybody<01:54:33.980> could<01:54:34.220> look<01:54:34.340> how<01:54:34.520> he<01:54:34.580> verified<01:54:35.090> the 01:54:35.290 --> 01:54:35.300 align:start position:0% everybody could look how he verified the 01:54:35.300 --> 01:54:38.200 align:start position:0% everybody could look how he verified the quad<01:54:35.570> 40<01:54:36.110> TPM<01:54:36.560> that's<01:54:37.190> really<01:54:37.550> easy<01:54:37.730> you<01:54:37.970> can 01:54:38.200 --> 01:54:38.210 align:start position:0% quad 40 TPM that's really easy you can 01:54:38.210 --> 01:54:42.240 align:start position:0% quad 40 TPM that's really easy you can know<01:54:38.360> that<01:54:39.040> second<01:54:40.040> thing<01:54:40.220> make<01:54:40.910> claims<01:54:41.900> about 01:54:42.240 --> 01:54:42.250 align:start position:0% know that second thing make claims about 01:54:42.250 --> 01:54:45.610 align:start position:0% know that second thing make claims about what<01:54:43.450> trade-offs<01:54:44.450> a<01:54:44.810> flexible<01:54:45.380> launch 01:54:45.610 --> 01:54:45.620 align:start position:0% what trade-offs a flexible launch 01:54:45.620 --> 01:54:48.400 align:start position:0% what trade-offs a flexible launch control<01:54:46.160> will<01:54:46.700> will<01:54:47.150> imply<01:54:47.540> for<01:54:47.600> example<01:54:48.260> will 01:54:48.400 --> 01:54:48.410 align:start position:0% control will will imply for example will 01:54:48.410 --> 01:54:50.470 align:start position:0% control will will imply for example will I<01:54:48.440> still<01:54:48.830> be<01:54:48.890> able<01:54:49.130> to<01:54:49.280> use<01:54:49.430> in<01:54:49.850> toast<01:54:50.060> quoting 01:54:50.470 --> 01:54:50.480 align:start position:0% I still be able to use in toast quoting 01:54:50.480 --> 01:54:53.080 align:start position:0% I still be able to use in toast quoting Conclave<01:54:50.900> while<01:54:51.560> having<01:54:52.070> my<01:54:52.100> custom<01:54:52.730> Lantern 01:54:53.080 --> 01:54:53.090 align:start position:0% Conclave while having my custom Lantern 01:54:53.090 --> 01:54:53.700 align:start position:0% Conclave while having my custom Lantern alive 01:54:53.700 --> 01:54:53.710 align:start position:0% alive 01:54:53.710 --> 01:54:56.260 align:start position:0% alive nowhere<01:54:54.710> in<01:54:54.860> the<01:54:54.980> spec<01:54:55.220> this<01:54:55.400> is<01:54:55.580> explicitly 01:54:56.260 --> 01:54:56.270 align:start position:0% nowhere in the spec this is explicitly 01:54:56.270 --> 01:54:56.710 align:start position:0% nowhere in the spec this is explicitly written 01:54:56.710 --> 01:54:56.720 align:start position:0% written 01:54:56.720 --> 01:54:58.720 align:start position:0% written will<01:54:56.930> it<01:54:57.050> work<01:54:57.080> or<01:54:57.500> not<01:54:57.530> I<01:54:57.890> would<01:54:58.280> like<01:54:58.490> to<01:54:58.610> know 01:54:58.720 --> 01:54:58.730 align:start position:0% will it work or not I would like to know 01:54:58.730 --> 01:55:01.630 align:start position:0% will it work or not I would like to know that<01:54:58.910> because<01:54:59.150> if<01:54:59.720> by<01:55:00.350> using<01:55:00.530> my<01:55:01.190> custom 01:55:01.630 --> 01:55:01.640 align:start position:0% that because if by using my custom 01:55:01.640 --> 01:55:03.730 align:start position:0% that because if by using my custom Lantern<01:55:02.000> Clive<01:55:02.270> what<01:55:02.930> will<01:55:03.110> not<01:55:03.260> force<01:55:03.530> me<01:55:03.710> to 01:55:03.730 --> 01:55:03.740 align:start position:0% Lantern Clive what will not force me to 01:55:03.740 --> 01:55:05.560 align:start position:0% Lantern Clive what will not force me to have<01:55:03.920> a<01:55:04.160> legal<01:55:04.610> contract<01:55:04.760> with<01:55:05.150> Intel<01:55:05.450> to 01:55:05.560 --> 01:55:05.570 align:start position:0% have a legal contract with Intel to 01:55:05.570 --> 01:55:08.530 align:start position:0% have a legal contract with Intel to start<01:55:05.810> my<01:55:05.930> own<01:55:05.960> Clive<01:55:06.590> so<01:55:07.340> if<01:55:07.640> having<01:55:08.330> my 01:55:08.530 --> 01:55:08.540 align:start position:0% start my own Clive so if having my 01:55:08.540 --> 01:55:10.630 align:start position:0% start my own Clive so if having my custom<01:55:08.960> Lantern<01:55:09.290> Clive<01:55:09.530> who<01:55:09.710> require<01:55:10.190> me<01:55:10.460> not 01:55:10.630 --> 01:55:10.640 align:start position:0% custom Lantern Clive who require me not 01:55:10.640 --> 01:55:13.000 align:start position:0% custom Lantern Clive who require me not to<01:55:10.970> be<01:55:11.690> will<01:55:12.290> prevent<01:55:12.620> me<01:55:12.770> from<01:55:12.800> using 01:55:13.000 --> 01:55:13.010 align:start position:0% to be will prevent me from using 01:55:13.010 --> 01:55:15.040 align:start position:0% to be will prevent me from using interest<01:55:13.880> coding<01:55:14.210> and<01:55:14.360> craft<01:55:14.660> and<01:55:14.870> so 01:55:15.040 --> 01:55:15.050 align:start position:0% interest coding and craft and so 01:55:15.050 --> 01:55:18.670 align:start position:0% interest coding and craft and so meaningless<01:55:15.430> unfortunately<01:55:17.200> second<01:55:18.200> or 01:55:18.670 --> 01:55:18.680 align:start position:0% meaningless unfortunately second or 01:55:18.680 --> 01:55:22.050 align:start position:0% meaningless unfortunately second or third<01:55:19.100> is<01:55:20.060> increased<01:55:20.930> memory<01:55:21.110> for<01:55:21.530> enclave's 01:55:22.050 --> 01:55:22.060 align:start position:0% third is increased memory for enclave's 01:55:22.060 --> 01:55:25.120 align:start position:0% third is increased memory for enclave's in<01:55:23.060> Colin<01:55:23.450> where<01:55:23.660> we<01:55:23.780> want<01:55:23.960> to<01:55:24.140> run<01:55:24.500> a<01:55:24.710> lot<01:55:24.980> of 01:55:25.120 --> 01:55:25.130 align:start position:0% in Colin where we want to run a lot of 01:55:25.130 --> 01:55:27.190 align:start position:0% in Colin where we want to run a lot of tile<01:55:25.370> outs<01:55:25.580> of<01:55:25.940> lots<01:55:26.270> of<01:55:26.330> complex<01:55:26.690> pallets<01:55:27.110> we 01:55:27.190 --> 01:55:27.200 align:start position:0% tile outs of lots of complex pallets we 01:55:27.200 --> 01:55:28.810 align:start position:0% tile outs of lots of complex pallets we already<01:55:27.530> run<01:55:27.800> for<01:55:28.100> example<01:55:28.460> we<01:55:28.520> can<01:55:28.670> run 01:55:28.810 --> 01:55:28.820 align:start position:0% already run for example we can run 01:55:28.820 --> 01:55:31.810 align:start position:0% already run for example we can run blender<01:55:29.270> in<01:55:29.540> in<01:55:29.870> enclaves<01:55:30.340> and<01:55:31.340> trans<01:55:31.580> pretty 01:55:31.810 --> 01:55:31.820 align:start position:0% blender in in enclaves and trans pretty 01:55:31.820 --> 01:55:34.960 align:start position:0% blender in in enclaves and trans pretty well<01:55:32.030> however<01:55:32.480> if<01:55:32.780> the<01:55:32.900> scenes<01:55:33.200> goes<01:55:33.970> really 01:55:34.960 --> 01:55:34.970 align:start position:0% well however if the scenes goes really 01:55:34.970 --> 01:55:38.590 align:start position:0% well however if the scenes goes really large<01:55:36.040> the<01:55:37.040> problem<01:55:37.400> of<01:55:37.520> swapping<01:55:37.820> memory<01:55:38.330> to 01:55:38.590 --> 01:55:38.600 align:start position:0% large the problem of swapping memory to 01:55:38.600 --> 01:55:41.770 align:start position:0% large the problem of swapping memory to DRAM<01:55:38.960> really<01:55:39.860> hits<01:55:40.430> the<01:55:40.520> performance<01:55:41.210> so 01:55:41.770 --> 01:55:41.780 align:start position:0% DRAM really hits the performance so 01:55:41.780 --> 01:55:44.590 align:start position:0% DRAM really hits the performance so ideally<01:55:42.200> we<01:55:42.650> could<01:55:42.890> have<01:55:43.190> that<01:55:43.880> the<01:55:44.090> operator 01:55:44.590 --> 01:55:44.600 align:start position:0% ideally we could have that the operator 01:55:44.600 --> 01:55:46.840 align:start position:0% ideally we could have that the operator of<01:55:44.930> an<01:55:45.080> out<01:55:45.260> could<01:55:45.590> have<01:55:45.770> a<01:55:45.800> slider<01:55:46.250> how<01:55:46.670> much 01:55:46.840 --> 01:55:46.850 align:start position:0% of an out could have a slider how much 01:55:46.850 --> 01:55:49.090 align:start position:0% of an out could have a slider how much of<01:55:47.030> the<01:55:47.150> DRAM<01:55:47.540> should<01:55:47.780> be<01:55:47.930> devoted<01:55:48.410> to<01:55:48.440> EPC 01:55:49.090 --> 01:55:49.100 align:start position:0% of the DRAM should be devoted to EPC 01:55:49.100 --> 01:55:53.680 align:start position:0% of the DRAM should be devoted to EPC tank<01:55:49.430> life<01:55:50.560> memory<01:55:51.560> and<01:55:52.330> finally<01:55:53.330> it<01:55:53.420> would<01:55:53.540> be 01:55:53.680 --> 01:55:53.690 align:start position:0% tank life memory and finally it would be 01:55:53.690 --> 01:55:55.720 align:start position:0% tank life memory and finally it would be nice<01:55:53.840> if<01:55:53.870> he<01:55:54.110> also<01:55:54.290> provided<01:55:55.040> some<01:55:55.340> secure 01:55:55.720 --> 01:55:55.730 align:start position:0% nice if he also provided some secure 01:55:55.730 --> 01:55:58.780 align:start position:0% nice if he also provided some secure perhaps<01:55:55.880> to<01:55:56.210> devices<01:55:56.620> in<01:55:57.620> general<01:55:57.760> not<01:55:58.760> just 01:55:58.780 --> 01:55:58.790 align:start position:0% perhaps to devices in general not just 01:55:58.790 --> 01:56:01.690 align:start position:0% perhaps to devices in general not just to<01:55:59.240> Intel<01:55:59.810> integrated<01:56:00.050> graphics<01:56:00.580> which<01:56:01.580> I 01:56:01.690 --> 01:56:01.700 align:start position:0% to Intel integrated graphics which I 01:56:01.700 --> 01:56:03.850 align:start position:0% to Intel integrated graphics which I know<01:56:01.880> you<01:56:01.940> already<01:56:02.240> have<01:56:02.630> as<01:56:02.900> the<01:56:03.590> larger 01:56:03.850 --> 01:56:03.860 align:start position:0% know you already have as the larger 01:56:03.860 --> 01:56:05.740 align:start position:0% know you already have as the larger presentation<01:56:04.430> told<01:56:04.640> us<01:56:04.760> unfortunately<01:56:05.150> never 01:56:05.740 --> 01:56:05.750 align:start position:0% presentation told us unfortunately never 01:56:05.750 --> 01:56:07.870 align:start position:0% presentation told us unfortunately never found<01:56:06.020> the<01:56:06.170> public<01:56:06.530> spec<01:56:06.830> that<01:56:07.160> would<01:56:07.670> be 01:56:07.870 --> 01:56:07.880 align:start position:0% found the public spec that would be 01:56:07.880 --> 01:56:10.810 align:start position:0% found the public spec that would be allow<01:56:08.600> others<01:56:09.110> to<01:56:09.200> use<01:56:09.500> it<01:56:09.680> but<01:56:10.370> we<01:56:10.520> would<01:56:10.640> like 01:56:10.810 --> 01:56:10.820 align:start position:0% allow others to use it but we would like 01:56:10.820 --> 01:56:14.590 align:start position:0% allow others to use it but we would like just<01:56:11.630> to<01:56:11.810> any<01:56:12.650> device<01:56:13.180> especially<01:56:14.180> to<01:56:14.360> more 01:56:14.590 --> 01:56:14.600 align:start position:0% just to any device especially to more 01:56:14.600 --> 01:56:15.779 align:start position:0% just to any device especially to more advanced 01:56:15.779 --> 01:56:15.789 align:start position:0% advanced 01:56:15.789 --> 01:56:19.779 align:start position:0% advanced GPUs<01:56:16.789> that<01:56:17.679> implement<01:56:18.679> CUDA<01:56:19.039> so<01:56:19.460> we<01:56:19.579> could 01:56:19.779 --> 01:56:19.789 align:start position:0% GPUs that implement CUDA so we could 01:56:19.789 --> 01:56:23.589 align:start position:0% GPUs that implement CUDA so we could allow<01:56:20.239> people<01:56:20.570> to<01:56:20.929> use<01:56:21.440> or<01:56:21.739> to<01:56:22.190> rent<01:56:22.599> GPU 01:56:23.589 --> 01:56:23.599 align:start position:0% allow people to use or to rent GPU 01:56:23.599 --> 01:56:25.779 align:start position:0% allow people to use or to rent GPU powerful<01:56:24.139> computations<01:56:24.860> that<01:56:25.309> those<01:56:25.489> four 01:56:25.779 --> 01:56:25.789 align:start position:0% powerful computations that those four 01:56:25.789 --> 01:56:26.549 align:start position:0% powerful computations that those four things 01:56:26.549 --> 01:56:26.559 align:start position:0% things 01:56:26.559 --> 01:56:29.470 align:start position:0% things liberate<01:56:27.559> is<01:56:28.130> the<01:56:28.369> centralized<01:56:28.849> remote 01:56:29.470 --> 01:56:29.480 align:start position:0% liberate is the centralized remote 01:56:29.480 --> 01:56:33.160 align:start position:0% liberate is the centralized remote attestation<01:56:29.869> point<01:56:31.269> specify<01:56:32.269> what<01:56:32.960> are<01:56:32.989> the 01:56:33.160 --> 01:56:33.170 align:start position:0% attestation point specify what are the 01:56:33.170 --> 01:56:35.379 align:start position:0% attestation point specify what are the condition<01:56:33.650> for<01:56:33.829> for<01:56:34.429> custom<01:56:34.789> launch<01:56:34.969> enclaves 01:56:35.379 --> 01:56:35.389 align:start position:0% condition for for custom launch enclaves 01:56:35.389 --> 01:56:37.810 align:start position:0% condition for for custom launch enclaves increase<01:56:36.050> memory<01:56:36.349> and<01:56:36.710> security<01:56:37.460> have<01:56:37.610> two 01:56:37.810 --> 01:56:37.820 align:start position:0% increase memory and security have two 01:56:37.820 --> 01:56:47.049 align:start position:0% increase memory and security have two devices<01:56:37.969> just<01:56:38.719> for<01:56:38.960> fixed<01:56:45.639> I'm<01:56:46.639> slightly 01:56:47.049 --> 01:56:47.059 align:start position:0% devices just for fixed I'm slightly 01:56:47.059 --> 01:56:49.089 align:start position:0% devices just for fixed I'm slightly confused<01:56:47.420> were<01:56:48.110> you<01:56:48.230> was<01:56:48.710> your<01:56:48.860> question 01:56:49.089 --> 01:56:49.099 align:start position:0% confused were you was your question 01:56:49.099 --> 01:56:53.859 align:start position:0% confused were you was your question around<01:56:49.489> the<01:56:49.880> the<01:56:50.239> API<01:56:50.809> spec<01:56:51.260> or<01:56:51.499> oh<01:56:52.599> okay<01:56:53.599> so<01:56:53.659> I 01:56:53.859 --> 01:56:53.869 align:start position:0% around the the API spec or oh okay so I 01:56:53.869 --> 01:56:57.609 align:start position:0% around the the API spec or oh okay so I was<01:56:54.079> like<01:56:54.289> what<01:56:54.909> yeah<01:56:55.909> no<01:56:56.900> no<01:56:57.019> I<01:56:57.050> know<01:56:57.289> it's 01:56:57.609 --> 01:56:57.619 align:start position:0% was like what yeah no no I know it's 01:56:57.619 --> 01:56:58.870 align:start position:0% was like what yeah no no I know it's like<01:56:57.769> it's<01:56:57.980> like<01:56:58.039> it's<01:56:58.280> here<01:56:58.400> it's<01:56:58.670> here<01:56:58.760> it's 01:56:58.870 --> 01:56:58.880 align:start position:0% like it's like it's here it's here it's 01:56:58.880 --> 01:57:00.879 align:start position:0% like it's like it's here it's here it's your<01:56:59.179> wish<01:56:59.329> list<01:56:59.360> for<01:57:00.110> insulin<01:57:00.559> I<01:57:00.650> think 01:57:00.879 --> 01:57:00.889 align:start position:0% your wish list for insulin I think 01:57:00.889 --> 01:57:02.500 align:start position:0% your wish list for insulin I think Sanjay<01:57:01.309> I<01:57:01.340> heard<01:57:01.460> you<01:57:01.610> loud<01:57:01.760> and<01:57:01.820> loud<01:57:02.360> and 01:57:02.500 --> 01:57:02.510 align:start position:0% Sanjay I heard you loud and loud and 01:57:02.510 --> 01:57:04.450 align:start position:0% Sanjay I heard you loud and loud and loud<01:57:02.840> and<01:57:02.989> clear<01:57:03.260> and<01:57:03.469> and<01:57:03.619> it's<01:57:03.800> it's<01:57:04.190> it's 01:57:04.450 --> 01:57:04.460 align:start position:0% loud and clear and and it's it's it's 01:57:04.460 --> 01:57:10.060 align:start position:0% loud and clear and and it's it's it's his<01:57:04.639> new<01:57:04.820> KPIs<01:57:05.420> for<01:57:05.599> next<01:57:05.960> year<01:57:06.139> right<01:57:09.070> action 01:57:10.060 --> 01:57:10.070 align:start position:0% his new KPIs for next year right action 01:57:10.070 --> 01:57:12.069 align:start position:0% his new KPIs for next year right action items<01:57:10.369> and<01:57:10.639> I'll<01:57:11.480> talk<01:57:11.719> to<01:57:11.809> your<01:57:11.900> boss<01:57:12.050> about 01:57:12.069 --> 01:57:12.079 align:start position:0% items and I'll talk to your boss about 01:57:12.079 --> 01:57:16.689 align:start position:0% items and I'll talk to your boss about that<01:57:12.320> one<01:57:13.809> III<01:57:14.809> think<01:57:15.289> for<01:57:15.710> the<01:57:15.829> for<01:57:16.249> the<01:57:16.369> spec 01:57:16.689 --> 01:57:16.699 align:start position:0% that one III think for the for the spec 01:57:16.699 --> 01:57:21.069 align:start position:0% that one III think for the for the spec I<01:57:17.090> think<01:57:17.840> as<01:57:18.139> far<01:57:18.380> as<01:57:18.469> an<01:57:18.590> API<01:57:18.829> spec<01:57:19.249> goes<01:57:19.760> is<01:57:20.210> we 01:57:21.069 --> 01:57:21.079 align:start position:0% I think as far as an API spec goes is we 01:57:21.079 --> 01:57:23.229 align:start position:0% I think as far as an API spec goes is we need<01:57:21.559> to<01:57:21.679> add<01:57:21.829> a<01:57:21.860> few<01:57:22.219> more<01:57:22.429> specifics<01:57:22.820> that 01:57:23.229 --> 01:57:23.239 align:start position:0% need to add a few more specifics that 01:57:23.239 --> 01:57:27.910 align:start position:0% need to add a few more specifics that are<01:57:24.400> directly<01:57:25.400> related<01:57:25.909> to<01:57:26.170> ZK<01:57:27.170> proves<01:57:27.469> and 01:57:27.910 --> 01:57:27.920 align:start position:0% are directly related to ZK proves and 01:57:27.920 --> 01:57:31.629 align:start position:0% are directly related to ZK proves and MPC<01:57:29.050> sort<01:57:30.050> of<01:57:30.110> like<01:57:30.260> more<01:57:30.530> that<01:57:31.039> are<01:57:31.190> that<01:57:31.489> are 01:57:31.629 --> 01:57:31.639 align:start position:0% MPC sort of like more that are that are 01:57:31.639 --> 01:57:33.700 align:start position:0% MPC sort of like more that are that are that<01:57:32.090> are<01:57:32.570> more<01:57:32.719> specific<01:57:33.139> around<01:57:33.230> that<01:57:33.499> as<01:57:33.590> we 01:57:33.700 --> 01:57:33.710 align:start position:0% that are more specific around that as we 01:57:33.710 --> 01:57:37.029 align:start position:0% that are more specific around that as we have<01:57:33.860> currently<01:57:34.309> for<01:57:34.820> for<01:57:35.300> a<01:57:35.869> te<01:57:36.499> even<01:57:36.949> though 01:57:37.029 --> 01:57:37.039 align:start position:0% have currently for for a te even though 01:57:37.039 --> 01:57:39.910 align:start position:0% have currently for for a te even though it's<01:57:37.219> just<01:57:37.489> for<01:57:37.639> what<01:57:37.820> for<01:57:38.239> SGX<01:57:38.900> we<01:57:39.230> that's<01:57:39.559> the 01:57:39.910 --> 01:57:39.920 align:start position:0% it's just for what for SGX we that's the 01:57:39.920 --> 01:57:41.259 align:start position:0% it's just for what for SGX we that's the next<01:57:40.099> iteration<01:57:40.429> that<01:57:40.699> I<01:57:40.760> think<01:57:41.030> we<01:57:41.119> should 01:57:41.259 --> 01:57:41.269 align:start position:0% next iteration that I think we should 01:57:41.269 --> 01:57:43.870 align:start position:0% next iteration that I think we should add<01:57:41.449> I<01:57:41.749> think<01:57:42.739> what<01:57:42.889> we<01:57:43.010> need<01:57:43.039> to<01:57:43.489> do<01:57:43.610> in<01:57:43.789> the 01:57:43.870 --> 01:57:43.880 align:start position:0% add I think what we need to do in the 01:57:43.880 --> 01:57:47.279 align:start position:0% add I think what we need to do in the working<01:57:44.210> group<01:57:44.420> is<01:57:44.829> a<01:57:45.829> best<01:57:46.489> practice 01:57:47.279 --> 01:57:47.289 align:start position:0% working group is a best practice 01:57:47.289 --> 01:57:52.029 align:start position:0% working group is a best practice document<01:57:48.289> around<01:57:49.210> how<01:57:50.210> to<01:57:50.269> how<01:57:51.050> to<01:57:51.110> create<01:57:51.650> and 01:57:52.029 --> 01:57:52.039 align:start position:0% document around how to how to create and 01:57:52.039 --> 01:57:55.330 align:start position:0% document around how to how to create and deploy<01:57:52.159> trusted<01:57:52.999> compute<01:57:53.929> whether<01:57:54.829> that<01:57:55.130> is 01:57:55.330 --> 01:57:55.340 align:start position:0% deploy trusted compute whether that is 01:57:55.340 --> 01:57:58.330 align:start position:0% deploy trusted compute whether that is is<01:57:55.909> so<01:57:56.300> so<01:57:56.630> if<01:57:56.809> I<01:57:56.960> want<01:57:57.199> to<01:57:57.380> if<01:57:57.590> I<01:57:57.980> want<01:57:58.010> to 01:57:58.330 --> 01:57:58.340 align:start position:0% is so so if I want to if I want to 01:57:58.340 --> 01:58:00.839 align:start position:0% is so so if I want to if I want to create<01:57:58.639> a<01:57:58.940> ZK<01:57:59.510> snark 01:58:00.839 --> 01:58:00.849 align:start position:0% create a ZK snark 01:58:00.849 --> 01:58:04.600 align:start position:0% create a ZK snark compute<01:58:01.849> service<01:58:02.239> right<01:58:03.159> what<01:58:04.159> are<01:58:04.249> the<01:58:04.340> steps 01:58:04.600 --> 01:58:04.610 align:start position:0% compute service right what are the steps 01:58:04.610 --> 01:58:05.979 align:start position:0% compute service right what are the steps that<01:58:04.789> I<01:58:04.820> need<01:58:05.030> to<01:58:05.150> follow<01:58:05.389> what<01:58:05.749> are<01:58:05.840> best 01:58:05.979 --> 01:58:05.989 align:start position:0% that I need to follow what are best 01:58:05.989 --> 01:58:07.810 align:start position:0% that I need to follow what are best practices<01:58:06.079> if<01:58:06.650> I<01:58:06.739> want<01:58:06.920> to<01:58:06.980> do<01:58:07.070> it<01:58:07.190> for<01:58:07.340> a<01:58:07.400> te<01:58:07.610> I 01:58:07.810 --> 01:58:07.820 align:start position:0% practices if I want to do it for a te I 01:58:07.820 --> 01:58:09.819 align:start position:0% practices if I want to do it for a te I would<01:58:08.239> if<01:58:08.570> I<01:58:08.690> want<01:58:08.869> to<01:58:08.929> virtualize<01:58:09.320> that<01:58:09.619> what 01:58:09.819 --> 01:58:09.829 align:start position:0% would if I want to virtualize that what 01:58:09.829 --> 01:58:12.160 align:start position:0% would if I want to virtualize that what I<01:58:09.860> need<01:58:10.099> to<01:58:10.219> do<01:58:10.369> right<01:58:10.969> so<01:58:11.030> these<01:58:11.510> are<01:58:11.780> I<01:58:11.809> think 01:58:12.160 --> 01:58:12.170 align:start position:0% I need to do right so these are I think 01:58:12.170 --> 01:58:15.129 align:start position:0% I need to do right so these are I think that<01:58:12.499> is<01:58:12.679> is<01:58:13.010> beyond<01:58:13.579> the<01:58:13.820> API<01:58:14.090> spec<01:58:14.539> is<01:58:14.780> really 01:58:15.129 --> 01:58:15.139 align:start position:0% that is is beyond the API spec is really 01:58:15.139 --> 01:58:16.600 align:start position:0% that is is beyond the API spec is really starting<01:58:15.559> to<01:58:15.739> talk<01:58:15.920> about<01:58:16.219> what<01:58:16.369> are<01:58:16.460> best 01:58:16.600 --> 01:58:16.610 align:start position:0% starting to talk about what are best 01:58:16.610 --> 01:58:18.189 align:start position:0% starting to talk about what are best practices<01:58:16.699> what<01:58:17.300> do<01:58:17.389> we<01:58:17.480> need<01:58:17.599> to<01:58:17.719> do<01:58:17.869> how<01:58:18.139> can 01:58:18.189 --> 01:58:18.199 align:start position:0% practices what do we need to do how can 01:58:18.199 --> 01:58:22.779 align:start position:0% practices what do we need to do how can we<01:58:18.849> implement<01:58:19.849> CK<01:58:20.690> CK<01:58:21.170> starks<01:58:21.789> effectively 01:58:22.779 --> 01:58:22.789 align:start position:0% we implement CK CK starks effectively 01:58:22.789 --> 01:58:25.239 align:start position:0% we implement CK CK starks effectively what<01:58:23.420> are<01:58:23.539> the<01:58:23.659> the<01:58:24.229> best<01:58:24.260> practices<01:58:24.949> for<01:58:25.190> the 01:58:25.239 --> 01:58:25.249 align:start position:0% what are the the best practices for the 01:58:25.249 --> 01:58:28.540 align:start position:0% what are the the best practices for the for<01:58:25.789> the<01:58:25.880> for<01:58:26.869> the<01:58:26.989> type<01:58:27.170> of<01:58:27.249> Ahri's<01:58:28.249> to<01:58:28.429> be 01:58:28.540 --> 01:58:28.550 align:start position:0% for the for the type of Ahri's to be 01:58:28.550 --> 01:58:29.500 align:start position:0% for the for the type of Ahri's to be used<01:58:28.760> etc<01:58:29.210> as 01:58:29.500 --> 01:58:29.510 align:start position:0% used etc as 01:58:29.510 --> 01:58:31.540 align:start position:0% used etc as I<01:58:29.570> think<01:58:29.960> that's<01:58:30.140> that<01:58:30.440> is<01:58:31.040> the<01:58:31.280> next<01:58:31.460> big 01:58:31.540 --> 01:58:31.550 align:start position:0% I think that's that is the next big 01:58:31.550 --> 01:58:37.000 align:start position:0% I think that's that is the next big workload<01:58:32.510> for<01:58:32.870> us<01:58:33.020> I<01:58:35.260> think<01:58:36.260> there<01:58:36.770> are<01:58:36.830> two 01:58:37.000 --> 01:58:37.010 align:start position:0% workload for us I think there are two 01:58:37.010 --> 01:58:40.090 align:start position:0% workload for us I think there are two main<01:58:37.400> pieces<01:58:37.670> that<01:58:38.300> I<01:58:38.570> would<01:58:39.080> like<01:58:39.290> to<01:58:39.560> see<01:58:39.980> in 01:58:40.090 --> 01:58:40.100 align:start position:0% main pieces that I would like to see in 01:58:40.100 --> 01:58:43.480 align:start position:0% main pieces that I would like to see in the<01:58:40.190> spec<01:58:40.400> one<01:58:41.390> is<01:58:41.720> better<01:58:42.680> it<01:58:43.220> was<01:58:43.340> already 01:58:43.480 --> 01:58:43.490 align:start position:0% the spec one is better it was already 01:58:43.490 --> 01:58:45.700 align:start position:0% the spec one is better it was already mentioned<01:58:43.730> by<01:58:43.940> Sanjay<01:58:44.270> I<01:58:44.300> think<01:58:44.570> a<01:58:45.020> better 01:58:45.700 --> 01:58:45.710 align:start position:0% mentioned by Sanjay I think a better 01:58:45.710 --> 01:58:49.990 align:start position:0% mentioned by Sanjay I think a better compatibility<01:58:46.100> and<01:58:46.790> cost<01:58:47.740> efficiency<01:58:49.000> we 01:58:49.990 --> 01:58:50.000 align:start position:0% compatibility and cost efficiency we 01:58:50.000 --> 01:58:54.190 align:start position:0% compatibility and cost efficiency we when<01:58:50.600> we<01:58:51.040> apply<01:58:52.040> that<01:58:52.540> API<01:58:53.540> on<01:58:53.780> the<01:58:53.870> public 01:58:54.190 --> 01:58:54.200 align:start position:0% when we apply that API on the public 01:58:54.200 --> 01:58:55.570 align:start position:0% when we apply that API on the public chain<01:58:54.470> because<01:58:54.980> right<01:58:55.160> now<01:58:55.280> it<01:58:55.400> would<01:58:55.550> be 01:58:55.570 --> 01:58:55.580 align:start position:0% chain because right now it would be 01:58:55.580 --> 01:58:57.460 align:start position:0% chain because right now it would be super<01:58:55.910> expensive<01:58:56.180> and<01:58:56.690> in<01:58:56.960> practice<01:58:57.320> it 01:58:57.460 --> 01:58:57.470 align:start position:0% super expensive and in practice it 01:58:57.470 --> 01:58:58.960 align:start position:0% super expensive and in practice it doesn't<01:58:57.500> really<01:58:57.830> make<01:58:58.070> it<01:58:58.100> viable<01:58:58.400> for<01:58:58.850> the 01:58:58.960 --> 01:58:58.970 align:start position:0% doesn't really make it viable for the 01:58:58.970 --> 01:59:02.200 align:start position:0% doesn't really make it viable for the public<01:58:59.210> chain<01:58:59.420> and<01:59:00.080> so<01:59:00.560> I<01:59:00.620> would<01:59:00.800> like<01:59:00.980> to<01:59:01.220> like 01:59:02.200 --> 01:59:02.210 align:start position:0% public chain and so I would like to like 01:59:02.210 --> 01:59:05.380 align:start position:0% public chain and so I would like to like have<01:59:02.960> also<01:59:03.580> either<01:59:04.580> some<01:59:04.820> kind<01:59:04.850> of<01:59:05.060> variation 01:59:05.380 --> 01:59:05.390 align:start position:0% have also either some kind of variation 01:59:05.390 --> 01:59:07.630 align:start position:0% have also either some kind of variation which<01:59:06.290> was<01:59:06.560> better<01:59:06.830> for<01:59:07.070> the<01:59:07.160> public<01:59:07.280> chain 01:59:07.630 --> 01:59:07.640 align:start position:0% which was better for the public chain 01:59:07.640 --> 01:59:09.670 align:start position:0% which was better for the public chain like<01:59:07.910> a<01:59:07.940> minimal<01:59:08.480> set<01:59:08.690> of<01:59:08.750> features<01:59:09.560> or 01:59:09.670 --> 01:59:09.680 align:start position:0% like a minimal set of features or 01:59:09.680 --> 01:59:13.150 align:start position:0% like a minimal set of features or something<01:59:10.180> or<01:59:11.180> just<01:59:11.900> a<01:59:12.320> new<01:59:12.470> iteration<01:59:12.680> of<01:59:13.010> the 01:59:13.150 --> 01:59:13.160 align:start position:0% something or just a new iteration of the 01:59:13.160 --> 01:59:15.900 align:start position:0% something or just a new iteration of the spec<01:59:13.400> which<01:59:13.850> is<01:59:14.150> more<01:59:14.840> cost<01:59:15.140> efficient<01:59:15.560> there 01:59:15.900 --> 01:59:15.910 align:start position:0% spec which is more cost efficient there 01:59:15.910 --> 01:59:18.640 align:start position:0% spec which is more cost efficient there and<01:59:16.910> the<01:59:17.060> second<01:59:17.330> thing<01:59:17.510> is<01:59:17.750> like<01:59:18.350> trying<01:59:18.530> to 01:59:18.640 --> 01:59:18.650 align:start position:0% and the second thing is like trying to 01:59:18.650 --> 01:59:21.720 align:start position:0% and the second thing is like trying to understand<01:59:19.130> better<01:59:19.730> if<01:59:20.150> the<01:59:20.480> current<01:59:20.840> spec<01:59:21.170> is 01:59:21.720 --> 01:59:21.730 align:start position:0% understand better if the current spec is 01:59:21.730 --> 01:59:26.050 align:start position:0% understand better if the current spec is as<01:59:23.230> intelligent<01:59:24.250> a<01:59:25.250> stick<01:59:25.460> as<01:59:25.580> it<01:59:25.700> could<01:59:25.880> be 01:59:26.050 --> 01:59:26.060 align:start position:0% as intelligent a stick as it could be 01:59:26.060 --> 01:59:27.520 align:start position:0% as intelligent a stick as it could be because<01:59:26.480> I<01:59:26.720> know<01:59:26.750> that<01:59:27.050> there<01:59:27.140> are<01:59:27.170> already 01:59:27.520 --> 01:59:27.530 align:start position:0% because I know that there are already 01:59:27.530 --> 01:59:29.530 align:start position:0% because I know that there are already it's<01:59:28.160> really<01:59:28.340> quite<01:59:28.580> agnostic<01:59:29.060> in<01:59:29.150> some<01:59:29.330> part 01:59:29.530 --> 01:59:29.540 align:start position:0% it's really quite agnostic in some part 01:59:29.540 --> 01:59:31.180 align:start position:0% it's really quite agnostic in some part it<01:59:29.690> says<01:59:29.870> it<01:59:30.260> could<01:59:30.530> be<01:59:30.710> something<01:59:31.070> different 01:59:31.180 --> 01:59:31.190 align:start position:0% it says it could be something different 01:59:31.190 --> 01:59:33.100 align:start position:0% it says it could be something different and<01:59:31.520> IntelliJ<01:59:31.970> X<01:59:32.090> you<01:59:32.330> have<01:59:32.420> to<01:59:32.630> specify<01:59:32.810> it 01:59:33.100 --> 01:59:33.110 align:start position:0% and IntelliJ X you have to specify it 01:59:33.110 --> 01:59:37.810 align:start position:0% and IntelliJ X you have to specify it like<01:59:33.320> this<01:59:33.470> and<01:59:33.710> so<01:59:34.340> on<01:59:34.370> however<01:59:36.580> we<01:59:37.580> have 01:59:37.810 --> 01:59:37.820 align:start position:0% like this and so on however we have 01:59:37.820 --> 01:59:39.520 align:start position:0% like this and so on however we have already<01:59:37.970> mentioned<01:59:38.240> like<01:59:38.720> open<01:59:39.170> and<01:59:39.290> close 01:59:39.520 --> 01:59:39.530 align:start position:0% already mentioned like open and close 01:59:39.530 --> 01:59:42.190 align:start position:0% already mentioned like open and close SDK<01:59:39.950> for<01:59:40.580> example<01:59:41.000> and<01:59:41.210> also<01:59:41.540> Google<01:59:41.900> is 01:59:42.190 --> 01:59:42.200 align:start position:0% SDK for example and also Google is 01:59:42.200 --> 01:59:44.050 align:start position:0% SDK for example and also Google is working<01:59:42.530> on<01:59:42.770> a<01:59:42.860> silo<01:59:43.100> so<01:59:43.490> there<01:59:43.640> are<01:59:43.700> those<01:59:43.880> two 01:59:44.050 --> 01:59:44.060 align:start position:0% working on a silo so there are those two 01:59:44.060 --> 01:59:46.450 align:start position:0% working on a silo so there are those two projects<01:59:44.450> and<01:59:44.660> that<01:59:45.500> are<01:59:45.650> pretty<01:59:45.890> much<01:59:46.100> both 01:59:46.450 --> 01:59:46.460 align:start position:0% projects and that are pretty much both 01:59:46.460 --> 01:59:48.490 align:start position:0% projects and that are pretty much both trying<01:59:46.850> to<01:59:46.970> abstract<01:59:47.300> out<01:59:47.540> the<01:59:47.990> enclaves 01:59:48.490 --> 01:59:48.500 align:start position:0% trying to abstract out the enclaves 01:59:48.500 --> 01:59:50.680 align:start position:0% trying to abstract out the enclaves specific<01:59:49.130> logic<01:59:49.310> I<01:59:49.700> would<01:59:50.180> like<01:59:50.330> also<01:59:50.570> to 01:59:50.680 --> 01:59:50.690 align:start position:0% specific logic I would like also to 01:59:50.690 --> 01:59:54.130 align:start position:0% specific logic I would like also to understand<01:59:51.230> if<01:59:52.040> the<01:59:52.820> existing<01:59:53.450> API<01:59:53.750> in<01:59:53.990> the 01:59:54.130 --> 01:59:54.140 align:start position:0% understand if the existing API in the 01:59:54.140 --> 01:59:56.530 align:start position:0% understand if the existing API in the spec<01:59:54.440> would<01:59:55.070> work<01:59:55.430> well<01:59:55.730> with<01:59:56.060> either<01:59:56.240> one<01:59:56.480> or 01:59:56.530 --> 01:59:56.540 align:start position:0% spec would work well with either one or 01:59:56.540 --> 02:00:00.670 align:start position:0% spec would work well with either one or the<01:59:56.690> other<01:59:56.810> or<01:59:57.050> both<01:59:58.120> so<01:59:59.120> so<01:59:59.510> yeah<01:59:59.690> I<02:00:00.110> think 02:00:00.670 --> 02:00:00.680 align:start position:0% the other or both so so yeah I think 02:00:00.680 --> 02:00:02.740 align:start position:0% the other or both so so yeah I think that<02:00:01.070> was<02:00:01.250> one<02:00:01.700> of<02:00:01.730> the<02:00:01.970> purposes<02:00:02.360> of<02:00:02.510> this 02:00:02.740 --> 02:00:02.750 align:start position:0% that was one of the purposes of this 02:00:02.750 --> 02:00:05.860 align:start position:0% that was one of the purposes of this whole<02:00:02.960> thing<02:00:03.140> is<02:00:03.290> like<02:00:03.410> you<02:00:03.560> know<02:00:03.850> it's<02:00:04.850> at<02:00:05.150> 0.5 02:00:05.860 --> 02:00:05.870 align:start position:0% whole thing is like you know it's at 0.5 02:00:05.870 --> 02:00:09.340 align:start position:0% whole thing is like you know it's at 0.5 for<02:00:06.140> a<02:00:06.170> reason<02:00:06.650> so<02:00:07.160> we<02:00:07.310> wanted<02:00:07.700> to<02:00:07.870> get<02:00:08.870> out<02:00:09.080> the 02:00:09.340 --> 02:00:09.350 align:start position:0% for a reason so we wanted to get out the 02:00:09.350 --> 02:00:14.020 align:start position:0% for a reason so we wanted to get out the spake<02:00:10.900> get<02:00:11.900> start<02:00:12.440> put<02:00:13.430> something<02:00:13.880> out<02:00:13.970> there 02:00:14.020 --> 02:00:14.030 align:start position:0% spake get start put something out there 02:00:14.030 --> 02:00:16.420 align:start position:0% spake get start put something out there so<02:00:14.390> that<02:00:14.540> people<02:00:14.810> can<02:00:14.990> react<02:00:15.380> to<02:00:15.650> provide 02:00:16.420 --> 02:00:16.430 align:start position:0% so that people can react to provide 02:00:16.430 --> 02:00:19.630 align:start position:0% so that people can react to provide input<02:00:16.640> and<02:00:17.410> create<02:00:18.410> something<02:00:18.860> that<02:00:19.190> we<02:00:19.460> as<02:00:19.610> a 02:00:19.630 --> 02:00:19.640 align:start position:0% input and create something that we as a 02:00:19.640 --> 02:00:23.230 align:start position:0% input and create something that we as a community<02:00:19.910> feel<02:00:20.780> that<02:00:20.810> it<02:00:21.500> meets<02:00:21.800> our<02:00:22.070> needs 02:00:23.230 --> 02:00:23.240 align:start position:0% community feel that it meets our needs 02:00:23.240 --> 02:00:27.100 align:start position:0% community feel that it meets our needs and<02:00:23.600> and<02:00:24.590> what<02:00:24.860> I<02:00:24.890> would<02:00:25.130> say<02:00:25.310> is<02:00:25.370> that<02:00:26.110> it 02:00:27.100 --> 02:00:27.110 align:start position:0% and and what I would say is that it 02:00:27.110 --> 02:00:29.230 align:start position:0% and and what I would say is that it would<02:00:27.290> be<02:00:27.320> great<02:00:27.670> you<02:00:28.670> know<02:00:28.820> there<02:00:29.120> are<02:00:29.180> a<02:00:29.210> few 02:00:29.230 --> 02:00:29.240 align:start position:0% would be great you know there are a few 02:00:29.240 --> 02:00:32.470 align:start position:0% would be great you know there are a few of<02:00:29.480> us<02:00:29.630> who<02:00:30.170> were<02:00:30.920> you<02:00:31.430> know<02:00:31.580> pushing<02:00:31.970> the<02:00:32.210> spec 02:00:32.470 --> 02:00:32.480 align:start position:0% of us who were you know pushing the spec 02:00:32.480 --> 02:00:35.710 align:start position:0% of us who were you know pushing the spec till<02:00:32.690> now<02:00:33.340> more<02:00:34.340> of<02:00:34.460> you<02:00:34.580> can<02:00:34.760> join<02:00:35.000> and<02:00:35.270> we<02:00:35.570> can 02:00:35.710 --> 02:00:35.720 align:start position:0% till now more of you can join and we can 02:00:35.720 --> 02:00:38.740 align:start position:0% till now more of you can join and we can get<02:00:35.870> all<02:00:36.050> of<02:00:36.170> these<02:00:36.290> perspective<02:00:37.010> in<02:00:37.600> into<02:00:38.600> the 02:00:38.740 --> 02:00:38.750 align:start position:0% get all of these perspective in into the 02:00:38.750 --> 02:00:41.650 align:start position:0% get all of these perspective in into the spec<02:00:39.020> and<02:00:39.610> that<02:00:40.610> that's<02:00:40.760> that's<02:00:41.360> really<02:00:41.540> the 02:00:41.650 --> 02:00:41.660 align:start position:0% spec and that that's that's really the 02:00:41.660 --> 02:00:42.659 align:start position:0% spec and that that's that's really the object<02:00:42.020> to<02:00:42.110> is 02:00:42.659 --> 02:00:42.669 align:start position:0% object to is 02:00:42.669 --> 02:00:44.729 align:start position:0% object to is it's<02:00:43.059> not<02:00:43.329> to<02:00:43.510> be<02:00:43.630> specific<02:00:44.050> to<02:00:44.169> technology 02:00:44.729 --> 02:00:44.739 align:start position:0% it's not to be specific to technology 02:00:44.739 --> 02:00:47.750 align:start position:0% it's not to be specific to technology but<02:00:44.919> something<02:00:45.309> that<02:00:45.340> the<02:00:45.489> community<02:00:45.999> can<02:00:46.149> use 02:00:47.750 --> 02:00:47.760 align:start position:0% but something that the community can use 02:00:47.760 --> 02:00:50.699 align:start position:0% but something that the community can use okay<02:00:48.760> thanks<02:00:49.479> very<02:00:49.539> much<02:00:49.929> the<02:00:50.110> panel<02:00:50.469> and 02:00:50.699 --> 02:00:50.709 align:start position:0% okay thanks very much the panel and 02:00:50.709 --> 02:01:01.390 align:start position:0% okay thanks very much the panel and thanks<02:00:51.219> to<02:00:51.309> the<02:00:51.429> audience 02:01:01.390 --> 02:01:01.400 align:start position:0% 02:01:01.400 --> 02:01:03.460 align:start position:0% you