WEBVTT
Kind: captions
Language: en

00:00:00.620 --> 00:00:03.919 align:start position:0%
 
so<00:00:01.620><c> in</c><00:00:02.580><c> the</c><00:00:02.669><c> decentralized</c><00:00:03.030><c> environment</c><00:00:03.720><c> and</c>

00:00:03.919 --> 00:00:03.929 align:start position:0%
so in the decentralized environment and
 

00:00:03.929 --> 00:00:05.539 align:start position:0%
so in the decentralized environment and
taking<00:00:04.710><c> of</c><00:00:04.770><c> the</c><00:00:04.890><c> consideration</c><00:00:05.520><c> that</c>

00:00:05.539 --> 00:00:05.549 align:start position:0%
taking of the consideration that
 

00:00:05.549 --> 00:00:07.909 align:start position:0%
taking of the consideration that
malicious<00:00:06.509><c> software</c><00:00:06.779><c> can</c><00:00:07.200><c> get</c><00:00:07.440><c> somehow</c><00:00:07.859><c> to</c>

00:00:07.909 --> 00:00:07.919 align:start position:0%
malicious software can get somehow to
 

00:00:07.919 --> 00:00:11.379 align:start position:0%
malicious software can get somehow to
your<00:00:08.130><c> computer</c><00:00:09.679><c> transfer</c><00:00:10.679><c> to</c><00:00:10.860><c> computation</c>

00:00:11.379 --> 00:00:11.389 align:start position:0%
your computer transfer to computation
 

00:00:11.389 --> 00:00:14.419 align:start position:0%
your computer transfer to computation
Roosevelt<00:00:12.389><c> sank</c><00:00:12.630><c> it's</c><00:00:12.840><c> a</c><00:00:13.259><c> need</c><00:00:13.590><c> it's</c><00:00:14.040><c> a</c><00:00:14.219><c> must</c>

00:00:14.419 --> 00:00:14.429 align:start position:0%
Roosevelt sank it's a need it's a must
 

00:00:14.429 --> 00:00:17.480 align:start position:0%
Roosevelt sank it's a need it's a must
but<00:00:15.059><c> different</c><00:00:15.420><c> parties</c><00:00:15.809><c> may</c><00:00:16.139><c> need</c><00:00:16.490><c> different</c>

00:00:17.480 --> 00:00:17.490 align:start position:0%
but different parties may need different
 

00:00:17.490 --> 00:00:19.910 align:start position:0%
but different parties may need different
aspects<00:00:18.449><c> of</c><00:00:18.570><c> trustworthiness</c><00:00:19.320><c> in</c><00:00:19.590><c> terms</c><00:00:19.770><c> of</c>

00:00:19.910 --> 00:00:19.920 align:start position:0%
aspects of trustworthiness in terms of
 

00:00:19.920 --> 00:00:23.420 align:start position:0%
aspects of trustworthiness in terms of
computation<00:00:20.520><c> and</c><00:00:21.619><c> this</c><00:00:22.619><c> is</c><00:00:22.800><c> an</c><00:00:23.039><c> important</c>

00:00:23.420 --> 00:00:23.430 align:start position:0%
computation and this is an important
 

00:00:23.430 --> 00:00:26.960 align:start position:0%
computation and this is an important
question<00:00:23.820><c> of</c><00:00:23.910><c> why</c><00:00:24.720><c> we</c><00:00:24.750><c> really</c><00:00:25.019><c> need</c><00:00:25.970><c> these</c>

00:00:26.960 --> 00:00:26.970 align:start position:0%
question of why we really need these
 

00:00:26.970 --> 00:00:28.880 align:start position:0%
question of why we really need these
computations<00:00:27.599><c> so</c><00:00:27.930><c> for</c><00:00:28.140><c> example</c><00:00:28.500><c> we</c><00:00:28.590><c> may</c><00:00:28.740><c> need</c>

00:00:28.880 --> 00:00:28.890 align:start position:0%
computations so for example we may need
 

00:00:28.890 --> 00:00:32.020 align:start position:0%
computations so for example we may need
to<00:00:28.949><c> deploy</c><00:00:29.820><c> a</c><00:00:30.050><c> peer-to-peer</c><00:00:31.050><c> network</c><00:00:31.679><c> of</c>

00:00:32.020 --> 00:00:32.030 align:start position:0%
to deploy a peer-to-peer network of
 

00:00:32.030 --> 00:00:36.110 align:start position:0%
to deploy a peer-to-peer network of
decentralized<00:00:33.980><c> computers</c><00:00:34.980><c> with</c><00:00:35.850><c> a</c><00:00:35.880><c> non</c>

00:00:36.110 --> 00:00:36.120 align:start position:0%
decentralized computers with a non
 

00:00:36.120 --> 00:00:39.549 align:start position:0%
decentralized computers with a non
consensus<00:00:36.600><c> out</c><00:00:36.719><c> ribs</c><00:00:36.989><c> or</c><00:00:37.800><c> we</c><00:00:38.219><c> may</c><00:00:38.399><c> need</c><00:00:38.579><c> to</c>

00:00:39.549 --> 00:00:39.559 align:start position:0%
consensus out ribs or we may need to
 

00:00:39.559 --> 00:00:43.549 align:start position:0%
consensus out ribs or we may need to
deploy<00:00:40.559><c> a</c><00:00:40.860><c> smaller</c><00:00:41.610><c> consensus</c><00:00:42.420><c> between</c><00:00:43.320><c> two</c>

00:00:43.549 --> 00:00:43.559 align:start position:0%
deploy a smaller consensus between two
 

00:00:43.559 --> 00:00:46.520 align:start position:0%
deploy a smaller consensus between two
computers<00:00:43.800><c> to</c><00:00:44.309><c> compute</c><00:00:44.610><c> something</c><00:00:44.820><c> and</c><00:00:45.530><c> the</c>

00:00:46.520 --> 00:00:46.530 align:start position:0%
computers to compute something and the
 

00:00:46.530 --> 00:00:48.860 align:start position:0%
computers to compute something and the
second<00:00:46.890><c> use</c><00:00:47.129><c> case</c><00:00:47.219><c> requires</c><00:00:48.000><c> other</c><00:00:48.450><c> aspects</c>

00:00:48.860 --> 00:00:48.870 align:start position:0%
second use case requires other aspects
 

00:00:48.870 --> 00:00:50.209 align:start position:0%
second use case requires other aspects
of<00:00:48.930><c> transport</c><00:00:49.379><c> units</c><00:00:49.559><c> than</c><00:00:49.680><c> the</c><00:00:49.770><c> first</c><00:00:49.950><c> one</c><00:00:50.100><c> in</c>

00:00:50.209 --> 00:00:50.219 align:start position:0%
of transport units than the first one in
 

00:00:50.219 --> 00:00:52.279 align:start position:0%
of transport units than the first one in
the<00:00:50.309><c> first</c><00:00:50.430><c> one</c><00:00:50.640><c> you</c><00:00:50.730><c> need</c><00:00:50.879><c> bounce</c><00:00:51.809><c> on</c><00:00:52.140><c> the</c>

00:00:52.279 --> 00:00:52.289 align:start position:0%
the first one you need bounce on the
 

00:00:52.289 --> 00:00:54.139 align:start position:0%
the first one you need bounce on the
malicious<00:00:52.710><c> actors</c><00:00:53.129><c> the</c><00:00:53.399><c> number</c><00:00:53.699><c> of</c><00:00:53.820><c> them</c><00:00:53.969><c> and</c>

00:00:54.139 --> 00:00:54.149 align:start position:0%
malicious actors the number of them and
 

00:00:54.149 --> 00:00:57.110 align:start position:0%
malicious actors the number of them and
some<00:00:55.079><c> availability</c><00:00:55.770><c> in</c><00:00:56.250><c> the</c><00:00:56.370><c> second</c><00:00:56.760><c> case</c><00:00:56.910><c> you</c>

00:00:57.110 --> 00:00:57.120 align:start position:0%
some availability in the second case you
 

00:00:57.120 --> 00:00:59.630 align:start position:0%
some availability in the second case you
probably<00:00:57.870><c> need</c><00:00:58.050><c> confidentiality</c><00:00:58.829><c> if</c><00:00:59.129><c> you</c>

00:00:59.630 --> 00:00:59.640 align:start position:0%
probably need confidentiality if you
 

00:00:59.640 --> 00:01:00.529 align:start position:0%
probably need confidentiality if you
would<00:00:59.730><c> like</c><00:00:59.879><c> to</c><00:00:59.910><c> decentralize</c><00:01:00.510><c> the</c>

00:01:00.529 --> 00:01:00.539 align:start position:0%
would like to decentralize the
 

00:01:00.539 --> 00:01:03.830 align:start position:0%
would like to decentralize the
centralized<00:01:01.289><c> service</c><00:01:01.680><c> that</c><00:01:02.370><c> hosts</c><00:01:02.969><c> as</c><00:01:03.660><c> an</c>

00:01:03.830 --> 00:01:03.840 align:start position:0%
centralized service that hosts as an
 

00:01:03.840 --> 00:01:07.039 align:start position:0%
centralized service that hosts as an
all-purpose<00:01:04.580><c> computation</c><00:01:05.580><c> then</c><00:01:05.820><c> it</c><00:01:06.119><c> is</c><00:01:06.270><c> quite</c>

00:01:07.039 --> 00:01:07.049 align:start position:0%
all-purpose computation then it is quite
 

00:01:07.049 --> 00:01:09.980 align:start position:0%
all-purpose computation then it is quite
a<00:01:07.080><c> different</c><00:01:07.439><c> deal</c><00:01:07.619><c> and</c><00:01:08.100><c> there</c><00:01:08.430><c> are</c><00:01:08.520><c> more</c><00:01:08.990><c> so</c>

00:01:09.980 --> 00:01:09.990 align:start position:0%
a different deal and there are more so
 

00:01:09.990 --> 00:01:12.700 align:start position:0%
a different deal and there are more so
we<00:01:10.409><c> had</c><00:01:10.590><c> to</c><00:01:10.710><c> ask</c><00:01:10.860><c> this</c><00:01:11.010><c> ourself</c><00:01:11.640><c> this</c><00:01:12.150><c> question</c>

00:01:12.700 --> 00:01:12.710 align:start position:0%
we had to ask this ourself this question
 

00:01:12.710 --> 00:01:15.800 align:start position:0%
we had to ask this ourself this question
what<00:01:13.710><c> is</c><00:01:13.820><c> important</c><00:01:14.820><c> from</c><00:01:15.030><c> our</c><00:01:15.210><c> perspective</c>

00:01:15.800 --> 00:01:15.810 align:start position:0%
what is important from our perspective
 

00:01:15.810 --> 00:01:19.370 align:start position:0%
what is important from our perspective
at<00:01:16.380><c> Colin</c><00:01:16.939><c> so</c><00:01:17.939><c> just</c><00:01:18.150><c> a</c><00:01:18.210><c> short</c><00:01:18.420><c> recap</c><00:01:18.570><c> in</c>

00:01:19.370 --> 00:01:19.380 align:start position:0%
at Colin so just a short recap in
 

00:01:19.380 --> 00:01:22.060 align:start position:0%
at Colin so just a short recap in
context<00:01:19.799><c> of</c><00:01:19.920><c> this</c><00:01:20.009><c> presentation</c><00:01:20.689><c> Joanne</c><00:01:21.689><c> is</c><00:01:21.810><c> a</c>

00:01:22.060 --> 00:01:22.070 align:start position:0%
context of this presentation Joanne is a
 

00:01:22.070 --> 00:01:25.100 align:start position:0%
context of this presentation Joanne is a
network<00:01:23.070><c> of</c><00:01:23.220><c> catalyst</c><00:01:23.790><c> resources</c><00:01:24.360><c> ranging</c>

00:01:25.100 --> 00:01:25.110 align:start position:0%
network of catalyst resources ranging
 

00:01:25.110 --> 00:01:28.760 align:start position:0%
network of catalyst resources ranging
from<00:01:25.560><c> individual</c><00:01:26.490><c> machines</c><00:01:26.909><c> to</c><00:01:27.810><c> sub</c><00:01:28.380><c> networks</c>

00:01:28.760 --> 00:01:28.770 align:start position:0%
from individual machines to sub networks
 

00:01:28.770 --> 00:01:30.890 align:start position:0%
from individual machines to sub networks
exposing<00:01:29.670><c> the</c><00:01:29.850><c> compute</c><00:01:30.479><c> power</c><00:01:30.630><c> to</c><00:01:30.810><c> the</c>

00:01:30.890 --> 00:01:30.900 align:start position:0%
exposing the compute power to the
 

00:01:30.900 --> 00:01:33.980 align:start position:0%
exposing the compute power to the
network<00:01:31.200><c> and</c><00:01:31.380><c> two</c><00:01:32.369><c> kinds</c><00:01:32.610><c> of</c><00:01:32.990><c> participants</c>

00:01:33.980 --> 00:01:33.990 align:start position:0%
network and two kinds of participants
 

00:01:33.990 --> 00:01:35.990 align:start position:0%
network and two kinds of participants
that<00:01:34.229><c> interact</c><00:01:34.680><c> with</c><00:01:34.860><c> both</c><00:01:35.340><c> the</c><00:01:35.610><c> resources</c>

00:01:35.990 --> 00:01:36.000 align:start position:0%
that interact with both the resources
 

00:01:36.000 --> 00:01:37.300 align:start position:0%
that interact with both the resources
and<00:01:36.210><c> with</c><00:01:36.810><c> each</c><00:01:36.930><c> other</c>

00:01:37.300 --> 00:01:37.310 align:start position:0%
and with each other
 

00:01:37.310 --> 00:01:40.340 align:start position:0%
and with each other
the<00:01:38.310><c> first</c><00:01:38.520><c> one</c><00:01:38.700><c> is</c><00:01:38.790><c> requester</c><00:01:39.350><c> the</c>

00:01:40.340 --> 00:01:40.350 align:start position:0%
the first one is requester the
 

00:01:40.350 --> 00:01:43.609 align:start position:0%
the first one is requester the
participants<00:01:41.280><c> who</c><00:01:41.490><c> would</c><00:01:41.579><c> like</c><00:01:41.759><c> to</c><00:01:42.439><c> do</c><00:01:43.439><c> some</c>

00:01:43.609 --> 00:01:43.619 align:start position:0%
participants who would like to do some
 

00:01:43.619 --> 00:01:45.260 align:start position:0%
participants who would like to do some
computations<00:01:44.130><c> using</c><00:01:44.250><c> the</c><00:01:44.460><c> resources</c><00:01:44.909><c> and</c><00:01:45.090><c> the</c>

00:01:45.260 --> 00:01:45.270 align:start position:0%
computations using the resources and the
 

00:01:45.270 --> 00:01:48.020 align:start position:0%
computations using the resources and the
second<00:01:45.570><c> was</c><00:01:45.720><c> one</c><00:01:46.140><c> is</c><00:01:46.229><c> the</c><00:01:46.350><c> provider</c><00:01:47.030><c> provider</c>

00:01:48.020 --> 00:01:48.030 align:start position:0%
second was one is the provider provider
 

00:01:48.030 --> 00:01:50.330 align:start position:0%
second was one is the provider provider
rents<00:01:48.659><c> out</c><00:01:48.780><c> the</c><00:01:48.840><c> resources</c><00:01:49.320><c> and</c><00:01:49.649><c> perhaps</c>

00:01:50.330 --> 00:01:50.340 align:start position:0%
rents out the resources and perhaps
 

00:01:50.340 --> 00:01:52.630 align:start position:0%
rents out the resources and perhaps
would<00:01:50.610><c> like</c><00:01:50.759><c> to</c><00:01:50.880><c> do</c><00:01:51.000><c> it</c><00:01:51.119><c> in</c><00:01:51.600><c> a</c><00:01:51.720><c> secure</c><00:01:51.960><c> manner</c>

00:01:52.630 --> 00:01:52.640 align:start position:0%
would like to do it in a secure manner
 

00:01:52.640 --> 00:01:57.830 align:start position:0%
would like to do it in a secure manner
so<00:01:53.640><c> this</c><00:01:54.509><c> is</c><00:01:54.689><c> the</c><00:01:55.700><c> basics</c><00:01:56.700><c> and</c><00:01:56.850><c> this</c><00:01:57.540><c> is</c><00:01:57.659><c> the</c>

00:01:57.830 --> 00:01:57.840 align:start position:0%
so this is the basics and this is the
 

00:01:57.840 --> 00:01:59.690 align:start position:0%
so this is the basics and this is the
fundamental<00:01:58.140><c> layer</c><00:01:58.649><c> on</c><00:01:58.950><c> top</c><00:01:59.250><c> of</c><00:01:59.399><c> which</c><00:01:59.549><c> of</c>

00:01:59.690 --> 00:01:59.700 align:start position:0%
fundamental layer on top of which of
 

00:01:59.700 --> 00:02:01.069 align:start position:0%
fundamental layer on top of which of
course<00:01:59.729><c> we</c><00:02:00.000><c> need</c><00:02:00.149><c> to</c><00:02:00.299><c> build</c><00:02:00.479><c> another</c><00:02:00.719><c> layers</c>

00:02:01.069 --> 00:02:01.079 align:start position:0%
course we need to build another layers
 

00:02:01.079 --> 00:02:03.139 align:start position:0%
course we need to build another layers
for<00:02:01.229><c> example</c><00:02:01.259><c> economy</c><00:02:01.920><c> but</c><00:02:02.640><c> in</c><00:02:02.759><c> context</c><00:02:03.090><c> of</c>

00:02:03.139 --> 00:02:03.149 align:start position:0%
for example economy but in context of
 

00:02:03.149 --> 00:02:05.090 align:start position:0%
for example economy but in context of
this<00:02:03.270><c> presentation</c><00:02:03.420><c> I'll</c><00:02:03.930><c> focus</c><00:02:04.170><c> only</c><00:02:04.890><c> on</c>

00:02:05.090 --> 00:02:05.100 align:start position:0%
this presentation I'll focus only on
 

00:02:05.100 --> 00:02:10.669 align:start position:0%
this presentation I'll focus only on
this<00:02:05.310><c> infrastructural</c><00:02:06.000><c> part</c><00:02:07.940><c> so</c><00:02:09.349><c> the</c><00:02:10.349><c> problem</c>

00:02:10.669 --> 00:02:10.679 align:start position:0%
this infrastructural part so the problem
 

00:02:10.679 --> 00:02:13.070 align:start position:0%
this infrastructural part so the problem
statement<00:02:10.709><c> is</c><00:02:11.160><c> pretty</c><00:02:11.730><c> easy</c><00:02:11.940><c> the</c><00:02:12.660><c> requester</c>

00:02:13.070 --> 00:02:13.080 align:start position:0%
statement is pretty easy the requester
 

00:02:13.080 --> 00:02:13.670 align:start position:0%
statement is pretty easy the requester
wants<00:02:13.379><c> to</c>

00:02:13.670 --> 00:02:13.680 align:start position:0%
wants to
 

00:02:13.680 --> 00:02:16.309 align:start position:0%
wants to
carry<00:02:14.459><c> out</c><00:02:14.780><c> computationally</c><00:02:15.780><c> trustworthy</c>

00:02:16.309 --> 00:02:16.319 align:start position:0%
carry out computationally trustworthy
 

00:02:16.319 --> 00:02:17.780 align:start position:0%
carry out computationally trustworthy
manner<00:02:16.500><c> on</c><00:02:16.709><c> the</c><00:02:16.829><c> resources</c><00:02:17.280><c> provided</c><00:02:17.670><c> by</c><00:02:17.700><c> the</c>

00:02:17.780 --> 00:02:17.790 align:start position:0%
manner on the resources provided by the
 

00:02:17.790 --> 00:02:21.349 align:start position:0%
manner on the resources provided by the
provider<00:02:18.180><c> and</c><00:02:18.450><c> the</c><00:02:19.230><c> provider</c><00:02:19.969><c> should</c><00:02:20.969><c> be</c><00:02:21.120><c> safe</c>

00:02:21.349 --> 00:02:21.359 align:start position:0%
provider and the provider should be safe
 

00:02:21.359 --> 00:02:24.199 align:start position:0%
provider and the provider should be safe
in<00:02:21.930><c> this</c><00:02:22.079><c> set</c><00:02:22.290><c> should</c><00:02:22.590><c> be</c><00:02:22.909><c> protected</c><00:02:23.909><c> from</c><00:02:24.030><c> the</c>

00:02:24.199 --> 00:02:24.209 align:start position:0%
in this set should be protected from the
 

00:02:24.209 --> 00:02:26.240 align:start position:0%
in this set should be protected from the
malicious<00:02:24.569><c> of</c><00:02:24.719><c> software</c><00:02:25.500><c> malicious</c><00:02:25.829><c> binaries</c>

00:02:26.240 --> 00:02:26.250 align:start position:0%
malicious of software malicious binaries
 

00:02:26.250 --> 00:02:30.559 align:start position:0%
malicious of software malicious binaries
and<00:02:26.780><c> this</c><00:02:28.670><c> simple</c><00:02:29.670><c> problem</c><00:02:29.879><c> stamp</c><00:02:30.239><c> and</c><00:02:30.389><c> most</c>

00:02:30.559 --> 00:02:30.569 align:start position:0%
and this simple problem stamp and most
 

00:02:30.569 --> 00:02:32.479 align:start position:0%
and this simple problem stamp and most
pretty<00:02:30.810><c> well</c><00:02:31.049><c> to</c><00:02:31.230><c> high</c><00:02:31.739><c> level</c><00:02:32.010><c> requirements</c>

00:02:32.479 --> 00:02:32.489 align:start position:0%
pretty well to high level requirements
 

00:02:32.489 --> 00:02:35.209 align:start position:0%
pretty well to high level requirements
so<00:02:32.939><c> yeah</c><00:02:33.480><c> requester</c><00:02:34.379><c> wants</c><00:02:34.620><c> to</c><00:02:34.709><c> be</c><00:02:34.829><c> able</c><00:02:35.069><c> to</c>

00:02:35.209 --> 00:02:35.219 align:start position:0%
so yeah requester wants to be able to
 

00:02:35.219 --> 00:02:41.050 align:start position:0%
so yeah requester wants to be able to
run<00:02:35.849><c> any</c><00:02:36.659><c> any</c><00:02:37.260><c> binary</c><00:02:38.090><c> in</c><00:02:39.090><c> this</c><00:02:39.329><c> network</c>

00:02:41.050 --> 00:02:41.060 align:start position:0%
run any any binary in this network
 

00:02:41.060 --> 00:02:44.140 align:start position:0%
run any any binary in this network
perhaps<00:02:42.060><c> efficiently</c><00:02:42.659><c> and</c><00:02:42.870><c> this</c><00:02:43.590><c> binary</c>

00:02:44.140 --> 00:02:44.150 align:start position:0%
perhaps efficiently and this binary
 

00:02:44.150 --> 00:02:46.819 align:start position:0%
perhaps efficiently and this binary
shouldn't<00:02:45.150><c> need</c><00:02:45.299><c> any</c><00:02:45.480><c> additional</c><00:02:45.930><c> changes</c>

00:02:46.819 --> 00:02:46.829 align:start position:0%
shouldn't need any additional changes
 

00:02:46.829 --> 00:02:51.589 align:start position:0%
shouldn't need any additional changes
just<00:02:47.220><c> to</c><00:02:47.340><c> be</c><00:02:47.519><c> run</c><00:02:48.299><c> within</c><00:02:48.989><c> the</c><00:02:49.230><c> network</c><00:02:50.599><c> tasks</c>

00:02:51.589 --> 00:02:51.599 align:start position:0%
just to be run within the network tasks
 

00:02:51.599 --> 00:02:53.929 align:start position:0%
just to be run within the network tasks
input<00:02:52.019><c> used</c><00:02:52.409><c> by</c><00:02:52.620><c> the</c><00:02:52.680><c> requester</c><00:02:53.669><c> should</c><00:02:53.849><c> be</c>

00:02:53.929 --> 00:02:53.939 align:start position:0%
input used by the requester should be
 

00:02:53.939 --> 00:02:55.460 align:start position:0%
input used by the requester should be
exactly<00:02:54.329><c> this</c><00:02:54.419><c> way</c><00:02:54.599><c> by</c><00:02:54.840><c> the</c><00:02:54.900><c> provider</c><00:02:55.379><c> should</c>

00:02:55.460 --> 00:02:55.470 align:start position:0%
exactly this way by the provider should
 

00:02:55.470 --> 00:02:56.780 align:start position:0%
exactly this way by the provider should
be<00:02:55.620><c> exactly</c><00:02:55.919><c> the</c><00:02:56.069><c> same</c><00:02:56.280><c> as</c><00:02:56.400><c> request</c><00:02:56.700><c> who</c>

00:02:56.780 --> 00:02:56.790 align:start position:0%
be exactly the same as request who
 

00:02:56.790 --> 00:03:01.220 align:start position:0%
be exactly the same as request who
provided<00:02:57.829><c> the</c><00:02:58.829><c> binary</c><00:02:59.510><c> that</c><00:03:00.510><c> is</c><00:03:00.659><c> run</c><00:03:00.900><c> on</c><00:03:01.109><c> the</c>

00:03:01.220 --> 00:03:01.230 align:start position:0%
provided the binary that is run on the
 

00:03:01.230 --> 00:03:02.959 align:start position:0%
provided the binary that is run on the
providers<00:03:01.620><c> machine</c><00:03:01.950><c> should</c><00:03:02.340><c> be</c><00:03:02.489><c> exactly</c><00:03:02.730><c> the</c>

00:03:02.959 --> 00:03:02.969 align:start position:0%
providers machine should be exactly the
 

00:03:02.969 --> 00:03:05.089 align:start position:0%
providers machine should be exactly the
same<00:03:03.000><c> but</c><00:03:03.930><c> requester</c><00:03:04.319><c> wanted</c><00:03:04.620><c> and</c><00:03:04.769><c> the</c><00:03:04.829><c> invar</c>

00:03:05.089 --> 00:03:05.099 align:start position:0%
same but requester wanted and the invar
 

00:03:05.099 --> 00:03:06.530 align:start position:0%
same but requester wanted and the invar
environment<00:03:05.609><c> should</c><00:03:05.760><c> be</c><00:03:05.849><c> exactly</c><00:03:06.150><c> the</c><00:03:06.299><c> same</c>

00:03:06.530 --> 00:03:06.540 align:start position:0%
environment should be exactly the same
 

00:03:06.540 --> 00:03:08.030 align:start position:0%
environment should be exactly the same
as<00:03:06.659><c> requester</c><00:03:07.019><c> wanted</c><00:03:07.319><c> this</c><00:03:07.650><c> is</c><00:03:07.739><c> different</c>

00:03:08.030 --> 00:03:08.040 align:start position:0%
as requester wanted this is different
 

00:03:08.040 --> 00:03:11.059 align:start position:0%
as requester wanted this is different
from<00:03:08.129><c> the</c><00:03:08.310><c> first</c><00:03:08.540><c> requirement</c><00:03:09.540><c> which</c><00:03:10.069><c> states</c>

00:03:11.059 --> 00:03:11.069 align:start position:0%
from the first requirement which states
 

00:03:11.069 --> 00:03:13.550 align:start position:0%
from the first requirement which states
that<00:03:11.159><c> requesters</c><00:03:11.760><c> should</c><00:03:11.909><c> be</c><00:03:12.030><c> able</c><00:03:12.209><c> to</c><00:03:12.560><c> choose</c>

00:03:13.550 --> 00:03:13.560 align:start position:0%
that requesters should be able to choose
 

00:03:13.560 --> 00:03:16.970 align:start position:0%
that requesters should be able to choose
any<00:03:14.129><c> binary</c><00:03:15.060><c> any</c><00:03:15.719><c> absolute</c><00:03:16.620><c> to</c><00:03:16.680><c> any</c><00:03:16.829><c> binary</c>

00:03:16.970 --> 00:03:16.980 align:start position:0%
any binary any absolute to any binary
 

00:03:16.980 --> 00:03:18.860 align:start position:0%
any binary any absolute to any binary
right<00:03:17.519><c> here</c><00:03:17.760><c> we</c><00:03:17.940><c> need</c><00:03:18.030><c> to</c><00:03:18.180><c> make</c><00:03:18.329><c> sure</c><00:03:18.359><c> that</c><00:03:18.690><c> no</c>

00:03:18.860 --> 00:03:18.870 align:start position:0%
right here we need to make sure that no
 

00:03:18.870 --> 00:03:21.349 align:start position:0%
right here we need to make sure that no
one<00:03:19.129><c> can</c><00:03:20.129><c> interfere</c><00:03:20.400><c> with</c><00:03:20.579><c> the</c><00:03:20.729><c> binary</c><00:03:20.940><c> before</c>

00:03:21.349 --> 00:03:21.359 align:start position:0%
one can interfere with the binary before
 

00:03:21.359 --> 00:03:24.439 align:start position:0%
one can interfere with the binary before
it<00:03:21.449><c> is</c><00:03:21.569><c> run</c><00:03:22.579><c> the</c><00:03:23.579><c> execution</c><00:03:24.090><c> should</c><00:03:24.299><c> be</c>

00:03:24.439 --> 00:03:24.449 align:start position:0%
it is run the execution should be
 

00:03:24.449 --> 00:03:26.750 align:start position:0%
it is run the execution should be
carried<00:03:24.840><c> out</c><00:03:24.959><c> the</c><00:03:25.620><c> valid</c><00:03:25.799><c> way</c><00:03:26.010><c> no</c><00:03:26.370><c> tampering</c>

00:03:26.750 --> 00:03:26.760 align:start position:0%
carried out the valid way no tampering
 

00:03:26.760 --> 00:03:28.849 align:start position:0%
carried out the valid way no tampering
no<00:03:26.970><c> interference</c><00:03:27.510><c> which</c><00:03:28.260><c> means</c><00:03:28.500><c> that</c><00:03:28.709><c> the</c>

00:03:28.849 --> 00:03:28.859 align:start position:0%
no interference which means that the
 

00:03:28.859 --> 00:03:31.729 align:start position:0%
no interference which means that the
requesters<00:03:29.639><c> can</c><00:03:30.239><c> expect</c><00:03:30.659><c> the</c><00:03:30.780><c> valid</c><00:03:31.349><c> results</c>

00:03:31.729 --> 00:03:31.739 align:start position:0%
requesters can expect the valid results
 

00:03:31.739 --> 00:03:33.979 align:start position:0%
requesters can expect the valid results
provided<00:03:32.189><c> that</c><00:03:32.340><c> task</c><00:03:32.909><c> person</c><00:03:33.209><c> called</c><00:03:33.419><c> at</c><00:03:33.540><c> the</c>

00:03:33.979 --> 00:03:33.989 align:start position:0%
provided that task person called at the
 

00:03:33.989 --> 00:03:37.490 align:start position:0%
provided that task person called at the
right<00:03:34.139><c> way</c><00:03:34.909><c> the</c><00:03:35.909><c> output</c><00:03:36.180><c> data</c><00:03:36.299><c> shouldn't</c><00:03:37.199><c> well</c>

00:03:37.490 --> 00:03:37.500 align:start position:0%
right way the output data shouldn't well
 

00:03:37.500 --> 00:03:39.469 align:start position:0%
right way the output data shouldn't well
it<00:03:37.709><c> cannot</c><00:03:37.979><c> be</c><00:03:38.159><c> in</c><00:03:38.250><c> fact</c><00:03:38.459><c> altered</c><00:03:38.849><c> by</c><00:03:39.060><c> anyone</c>

00:03:39.469 --> 00:03:39.479 align:start position:0%
it cannot be in fact altered by anyone
 

00:03:39.479 --> 00:03:41.449 align:start position:0%
it cannot be in fact altered by anyone
in<00:03:39.840><c> a</c><00:03:39.959><c> way</c><00:03:40.049><c> that's</c><00:03:40.280><c> undetected</c><00:03:41.280><c> to</c><00:03:41.310><c> the</c>

00:03:41.449 --> 00:03:41.459 align:start position:0%
in a way that's undetected to the
 

00:03:41.459 --> 00:03:44.420 align:start position:0%
in a way that's undetected to the
requester<00:03:41.879><c> and</c><00:03:42.769><c> only</c><00:03:43.769><c> the</c><00:03:43.859><c> requester</c><00:03:44.250><c> should</c>

00:03:44.420 --> 00:03:44.430 align:start position:0%
requester and only the requester should
 

00:03:44.430 --> 00:03:47.240 align:start position:0%
requester and only the requester should
be<00:03:44.549><c> able</c><00:03:44.699><c> to</c><00:03:45.199><c> show</c><00:03:46.199><c> the</c><00:03:46.379><c> data</c><00:03:46.530><c> to</c><00:03:46.769><c> the</c><00:03:46.799><c> external</c>

00:03:47.240 --> 00:03:47.250 align:start position:0%
be able to show the data to the external
 

00:03:47.250 --> 00:03:50.960 align:start position:0%
be able to show the data to the external
world<00:03:47.430><c> meaning</c><00:03:48.389><c> that</c><00:03:48.509><c> perhaps</c><00:03:49.970><c> the</c>

00:03:50.960 --> 00:03:50.970 align:start position:0%
world meaning that perhaps the
 

00:03:50.970 --> 00:03:53.599 align:start position:0%
world meaning that perhaps the
application<00:03:51.569><c> that's</c><00:03:52.470><c> taking</c><00:03:53.129><c> the</c>

00:03:53.599 --> 00:03:53.609 align:start position:0%
application that's taking the
 

00:03:53.609 --> 00:03:55.670 align:start position:0%
application that's taking the
Constituent<00:03:54.239><c> providers</c><00:03:54.599><c> machine</c><00:03:54.930><c> can</c><00:03:55.470><c> look</c>

00:03:55.670 --> 00:03:55.680 align:start position:0%
Constituent providers machine can look
 

00:03:55.680 --> 00:03:58.249 align:start position:0%
Constituent providers machine can look
up<00:03:55.799><c> the</c><00:03:55.919><c> data</c><00:03:56.150><c> but</c><00:03:57.150><c> other</c><00:03:57.449><c> than</c><00:03:57.659><c> that</c><00:03:57.720><c> no</c><00:03:58.109><c> one</c>

00:03:58.249 --> 00:03:58.259 align:start position:0%
up the data but other than that no one
 

00:03:58.259 --> 00:03:59.929 align:start position:0%
up the data but other than that no one
should<00:03:58.409><c> be</c><00:03:58.560><c> able</c><00:03:58.709><c> to</c><00:03:58.889><c> leak</c><00:03:59.189><c> this</c><00:03:59.400><c> data</c><00:03:59.579><c> to</c><00:03:59.790><c> the</c>

00:03:59.929 --> 00:03:59.939 align:start position:0%
should be able to leak this data to the
 

00:03:59.939 --> 00:04:02.629 align:start position:0%
should be able to leak this data to the
outside<00:04:00.180><c> world</c><00:04:00.329><c> only</c><00:04:00.930><c> the</c><00:04:01.169><c> requester</c><00:04:01.620><c> if</c><00:04:02.370><c> who</c>

00:04:02.629 --> 00:04:02.639 align:start position:0%
outside world only the requester if who
 

00:04:02.639 --> 00:04:05.569 align:start position:0%
outside world only the requester if who
is<00:04:02.819><c> do</c><00:04:03.090><c> so</c><00:04:03.290><c> and</c><00:04:04.290><c> let's</c><00:04:04.530><c> not</c><00:04:04.680><c> forget</c><00:04:04.739><c> about</c><00:04:05.129><c> the</c>

00:04:05.569 --> 00:04:05.579 align:start position:0%
is do so and let's not forget about the
 

00:04:05.579 --> 00:04:09.020 align:start position:0%
is do so and let's not forget about the
provider<00:04:06.560><c> he</c><00:04:07.560><c> has</c><00:04:07.680><c> to</c><00:04:07.829><c> be</c><00:04:07.919><c> protected</c><00:04:08.370><c> from</c><00:04:08.849><c> the</c>

00:04:09.020 --> 00:04:09.030 align:start position:0%
provider he has to be protected from the
 

00:04:09.030 --> 00:04:12.140 align:start position:0%
provider he has to be protected from the
cold<00:04:09.060><c> as</c><00:04:09.299><c> well</c><00:04:10.069><c> so</c><00:04:11.069><c> how</c><00:04:11.609><c> can</c><00:04:11.669><c> we</c><00:04:11.879><c> meet</c><00:04:11.970><c> these</c>

00:04:12.140 --> 00:04:12.150 align:start position:0%
cold as well so how can we meet these
 

00:04:12.150 --> 00:04:15.219 align:start position:0%
cold as well so how can we meet these
requirements<00:04:13.099><c> there</c><00:04:14.099><c> are</c><00:04:14.129><c> a</c><00:04:14.220><c> few</c><00:04:14.370><c> approaches</c>

00:04:15.219 --> 00:04:15.229 align:start position:0%
requirements there are a few approaches
 

00:04:15.229 --> 00:04:18.589 align:start position:0%
requirements there are a few approaches
quite<00:04:16.229><c> a</c><00:04:16.259><c> few</c><00:04:16.530><c> the</c><00:04:17.400><c> point</c><00:04:17.639><c> is</c><00:04:17.820><c> that</c><00:04:18.030><c> there</c><00:04:18.539><c> is</c>

00:04:18.589 --> 00:04:18.599 align:start position:0%
quite a few the point is that there is
 

00:04:18.599 --> 00:04:20.810 align:start position:0%
quite a few the point is that there is
no<00:04:18.750><c> single</c><00:04:18.959><c> bullet</c><00:04:19.349><c> some</c><00:04:20.190><c> silver</c><00:04:20.519><c> bullet</c><00:04:20.789><c> for</c>

00:04:20.810 --> 00:04:20.820 align:start position:0%
no single bullet some silver bullet for
 

00:04:20.820 --> 00:04:23.839 align:start position:0%
no single bullet some silver bullet for
this<00:04:21.529><c> requirements</c><00:04:22.529><c> and</c><00:04:22.849><c> different</c>

00:04:23.839 --> 00:04:23.849 align:start position:0%
this requirements and different
 

00:04:23.849 --> 00:04:27.140 align:start position:0%
this requirements and different
approaches<00:04:24.950><c> result</c><00:04:25.950><c> in</c><00:04:26.250><c> me</c>

00:04:27.140 --> 00:04:27.150 align:start position:0%
approaches result in me
 

00:04:27.150 --> 00:04:30.050 align:start position:0%
approaches result in me
some<00:04:27.510><c> of</c><00:04:27.660><c> them</c><00:04:27.840><c> or</c><00:04:28.140><c> all</c><00:04:28.200><c> of</c><00:04:29.040><c> them</c><00:04:29.190><c> in</c><00:04:29.640><c> some</c><00:04:29.700><c> way</c>

00:04:30.050 --> 00:04:30.060 align:start position:0%
some of them or all of them in some way
 

00:04:30.060 --> 00:04:32.840 align:start position:0%
some of them or all of them in some way
but<00:04:30.300><c> not</c><00:04:30.990><c> all</c><00:04:31.140><c> of</c><00:04:31.260><c> them</c><00:04:31.440><c> with</c><00:04:32.340><c> all</c><00:04:32.700><c> the</c>

00:04:32.840 --> 00:04:32.850 align:start position:0%
but not all of them with all the
 

00:04:32.850 --> 00:04:34.610 align:start position:0%
but not all of them with all the
required<00:04:33.330><c> features</c><00:04:33.540><c> so</c><00:04:33.840><c> for</c><00:04:34.110><c> example</c><00:04:34.410><c> we</c><00:04:34.470><c> can</c>

00:04:34.610 --> 00:04:34.620 align:start position:0%
required features so for example we can
 

00:04:34.620 --> 00:04:37.340 align:start position:0%
required features so for example we can
constrain<00:04:35.160><c> ourself</c><00:04:35.640><c> to</c><00:04:35.820><c> the</c><00:04:36.660><c> terminus</c><00:04:37.020><c> covers</c>

00:04:37.340 --> 00:04:37.350 align:start position:0%
constrain ourself to the terminus covers
 

00:04:37.350 --> 00:04:38.990 align:start position:0%
constrain ourself to the terminus covers
for<00:04:37.620><c> each</c><00:04:37.710><c> proof-of-work</c><00:04:38.070><c> exist</c><00:04:38.550><c> with</c><00:04:38.910><c> the</c>

00:04:38.990 --> 00:04:39.000 align:start position:0%
for each proof-of-work exist with the
 

00:04:39.000 --> 00:04:41.180 align:start position:0%
for each proof-of-work exist with the
trade-off<00:04:39.390><c> is</c><00:04:39.510><c> that</c><00:04:39.750><c> we</c><00:04:40.410><c> only</c><00:04:40.560><c> can</c><00:04:40.800><c> do</c>

00:04:41.180 --> 00:04:41.190 align:start position:0%
trade-off is that we only can do
 

00:04:41.190 --> 00:04:43.820 align:start position:0%
trade-off is that we only can do
deterministic<00:04:41.910><c> work</c><00:04:42.150><c> we</c><00:04:42.660><c> make</c><00:04:42.840><c> sacrifice</c>

00:04:43.820 --> 00:04:43.830 align:start position:0%
deterministic work we make sacrifice
 

00:04:43.830 --> 00:04:45.970 align:start position:0%
deterministic work we make sacrifice
confidentiality<00:04:44.670><c> and</c><00:04:44.760><c> get</c><00:04:44.970><c> into</c><00:04:45.180><c> integrity</c>

00:04:45.970 --> 00:04:45.980 align:start position:0%
confidentiality and get into integrity
 

00:04:45.980 --> 00:04:49.610 align:start position:0%
confidentiality and get into integrity
but<00:04:46.980><c> yeah</c><00:04:47.670><c> we</c><00:04:47.820><c> lose</c><00:04:48.000><c> confidentiality</c><00:04:48.630><c> on</c><00:04:49.530><c> the</c>

00:04:49.610 --> 00:04:49.620 align:start position:0%
but yeah we lose confidentiality on the
 

00:04:49.620 --> 00:04:51.950 align:start position:0%
but yeah we lose confidentiality on the
other<00:04:49.710><c> hand</c><00:04:49.950><c> we</c><00:04:50.100><c> may</c><00:04:50.250><c> for</c><00:04:51.060><c> example</c><00:04:51.090><c> use</c>

00:04:51.950 --> 00:04:51.960 align:start position:0%
other hand we may for example use
 

00:04:51.960 --> 00:04:53.750 align:start position:0%
other hand we may for example use
third-party<00:04:52.950><c> sources</c><00:04:53.190><c> of</c><00:04:53.370><c> trust</c>

00:04:53.750 --> 00:04:53.760 align:start position:0%
third-party sources of trust
 

00:04:53.760 --> 00:04:55.910 align:start position:0%
third-party sources of trust
this<00:04:54.180><c> is</c><00:04:54.300><c> either</c><00:04:54.690><c> a</c><00:04:55.050><c> third</c><00:04:55.410><c> party</c><00:04:55.740><c> service</c>

00:04:55.910 --> 00:04:55.920 align:start position:0%
this is either a third party service
 

00:04:55.920 --> 00:05:00.560 align:start position:0%
this is either a third party service
that<00:04:56.310><c> is</c><00:04:57.000><c> going</c><00:04:57.420><c> to</c><00:04:58.580><c> provide</c><00:04:59.580><c> trust</c><00:04:59.910><c> to</c><00:05:00.450><c> the</c>

00:05:00.560 --> 00:05:00.570 align:start position:0%
that is going to provide trust to the
 

00:05:00.570 --> 00:05:04.010 align:start position:0%
that is going to provide trust to the
actors<00:05:00.870><c> or</c><00:05:01.130><c> we</c><00:05:02.130><c> might</c><00:05:02.340><c> simply</c><00:05:02.580><c> use</c><00:05:03.480><c> some</c><00:05:03.810><c> check</c>

00:05:04.010 --> 00:05:04.020 align:start position:0%
actors or we might simply use some check
 

00:05:04.020 --> 00:05:08.150 align:start position:0%
actors or we might simply use some check
pointing<00:05:04.410><c> to</c><00:05:04.970><c> make</c><00:05:05.970><c> the</c><00:05:06.120><c> cheating</c><00:05:07.160><c> less</c>

00:05:08.150 --> 00:05:08.160 align:start position:0%
pointing to make the cheating less
 

00:05:08.160 --> 00:05:10.190 align:start position:0%
pointing to make the cheating less
feasible<00:05:08.540><c> at</c><00:05:09.540><c> the</c><00:05:09.630><c> same</c><00:05:09.780><c> time</c><00:05:09.930><c> we</c><00:05:10.020><c> can</c><00:05:10.170><c> use</c>

00:05:10.190 --> 00:05:10.200 align:start position:0%
feasible at the same time we can use
 

00:05:10.200 --> 00:05:12.110 align:start position:0%
feasible at the same time we can use
infrastructure<00:05:10.860><c> such</c><00:05:11.100><c> as</c><00:05:11.130><c> trusted</c><00:05:11.910><c> execution</c>

00:05:12.110 --> 00:05:12.120 align:start position:0%
infrastructure such as trusted execution
 

00:05:12.120 --> 00:05:21.530 align:start position:0%
infrastructure such as trusted execution
environments<00:05:13.430><c> or</c><00:05:15.170><c> mix</c><00:05:16.170><c> of</c><00:05:16.290><c> thereof</c><00:05:18.590><c> so</c><00:05:20.390><c> as</c><00:05:21.390><c> I</c>

00:05:21.530 --> 00:05:21.540 align:start position:0%
environments or mix of thereof so as I
 

00:05:21.540 --> 00:05:23.080 align:start position:0%
environments or mix of thereof so as I
said<00:05:21.750><c> there's</c><00:05:21.960><c> trade</c><00:05:22.230><c> off</c><00:05:22.380><c> for</c><00:05:22.410><c> every</c>

00:05:23.080 --> 00:05:23.090 align:start position:0%
said there's trade off for every
 

00:05:23.090 --> 00:05:26.030 align:start position:0%
said there's trade off for every
approach<00:05:24.090><c> and</c><00:05:24.390><c> is</c><00:05:25.230><c> either</c><00:05:25.440><c> inherent</c><00:05:25.890><c> to</c><00:05:25.950><c> the</c>

00:05:26.030 --> 00:05:26.040 align:start position:0%
approach and is either inherent to the
 

00:05:26.040 --> 00:05:28.040 align:start position:0%
approach and is either inherent to the
method<00:05:26.310><c> such</c><00:05:26.700><c> as</c><00:05:26.730><c> using</c><00:05:27.330><c> proof</c><00:05:27.600><c> of</c><00:05:27.690><c> work</c><00:05:27.870><c> or</c>

00:05:28.040 --> 00:05:28.050 align:start position:0%
method such as using proof of work or
 

00:05:28.050 --> 00:05:30.530 align:start position:0%
method such as using proof of work or
task<00:05:28.230><c> specific</c><00:05:28.410><c> for</c><00:05:28.800><c> example</c><00:05:29.190><c> in</c><00:05:30.030><c> rendering</c>

00:05:30.530 --> 00:05:30.540 align:start position:0%
task specific for example in rendering
 

00:05:30.540 --> 00:05:32.300 align:start position:0%
task specific for example in rendering
you<00:05:30.660><c> can</c><00:05:30.690><c> be</c><00:05:30.930><c> interested</c><00:05:31.290><c> in</c><00:05:31.380><c> confidentiality</c>

00:05:32.300 --> 00:05:32.310 align:start position:0%
you can be interested in confidentiality
 

00:05:32.310 --> 00:05:35.240 align:start position:0%
you can be interested in confidentiality
if<00:05:32.430><c> you're</c><00:05:32.610><c> under</c><00:05:32.850><c> a</c><00:05:33.560><c> movie</c><00:05:34.560><c> but</c><00:05:35.010><c> if</c><00:05:35.130><c> you</c>

00:05:35.240 --> 00:05:35.250 align:start position:0%
if you're under a movie but if you
 

00:05:35.250 --> 00:05:37.130 align:start position:0%
if you're under a movie but if you
render<00:05:35.520><c> open</c><00:05:35.880><c> source</c><00:05:36.060><c> animation</c><00:05:36.540><c> you</c><00:05:36.660><c> it</c><00:05:36.960><c> may</c>

00:05:37.130 --> 00:05:37.140 align:start position:0%
render open source animation you it may
 

00:05:37.140 --> 00:05:38.840 align:start position:0%
render open source animation you it may
not<00:05:37.170><c> be</c><00:05:37.380><c> so</c><00:05:37.500><c> important</c><00:05:37.890><c> you</c><00:05:38.010><c> care</c><00:05:38.610><c> about</c><00:05:38.790><c> the</c>

00:05:38.840 --> 00:05:38.850 align:start position:0%
not be so important you care about the
 

00:05:38.850 --> 00:05:40.910 align:start position:0%
not be so important you care about the
integrity<00:05:39.080><c> it's</c><00:05:40.080><c> only</c><00:05:40.260><c> also</c><00:05:40.650><c> runtime</c>

00:05:40.910 --> 00:05:40.920 align:start position:0%
integrity it's only also runtime
 

00:05:40.920 --> 00:05:42.320 align:start position:0%
integrity it's only also runtime
dependent<00:05:41.340><c> for</c><00:05:41.520><c> example</c><00:05:41.850><c> for</c><00:05:42.060><c> trust</c><00:05:42.240><c> at</c>

00:05:42.320 --> 00:05:42.330 align:start position:0%
dependent for example for trust at
 

00:05:42.330 --> 00:05:44.030 align:start position:0%
dependent for example for trust at
execution<00:05:42.690><c> environments</c><00:05:43.080><c> memory</c><00:05:43.800><c> access</c>

00:05:44.030 --> 00:05:44.040 align:start position:0%
execution environments memory access
 

00:05:44.040 --> 00:05:45.920 align:start position:0%
execution environments memory access
patterns<00:05:44.070><c> may</c><00:05:44.550><c> have</c><00:05:44.790><c> profound</c><00:05:45.390><c> impact</c><00:05:45.690><c> on</c><00:05:45.810><c> the</c>

00:05:45.920 --> 00:05:45.930 align:start position:0%
patterns may have profound impact on the
 

00:05:45.930 --> 00:05:48.260 align:start position:0%
patterns may have profound impact on the
efficiency<00:05:46.740><c> so</c><00:05:47.040><c> this</c><00:05:47.460><c> has</c><00:05:47.640><c> be</c><00:05:47.790><c> taken</c><00:05:48.120><c> into</c>

00:05:48.260 --> 00:05:48.270 align:start position:0%
efficiency so this has be taken into
 

00:05:48.270 --> 00:05:50.120 align:start position:0%
efficiency so this has be taken into
consideration<00:05:48.500><c> from</c><00:05:49.500><c> my</c><00:05:49.560><c> perspective</c><00:05:49.830><c> you</c>

00:05:50.120 --> 00:05:50.130 align:start position:0%
consideration from my perspective you
 

00:05:50.130 --> 00:05:54.230 align:start position:0%
consideration from my perspective you
wanted<00:05:50.490><c> a</c><00:05:50.730><c> solution</c><00:05:51.450><c> that</c><00:05:51.780><c> is</c><00:05:51.840><c> generic</c><00:05:53.240><c> easy</c>

00:05:54.230 --> 00:05:54.240 align:start position:0%
wanted a solution that is generic easy
 

00:05:54.240 --> 00:05:58.310 align:start position:0%
wanted a solution that is generic easy
to<00:05:54.480><c> use</c><00:05:54.630><c> has</c><00:05:55.400><c> well</c><00:05:56.400><c> specified</c><00:05:57.320><c> security</c>

00:05:58.310 --> 00:05:58.320 align:start position:0%
to use has well specified security
 

00:05:58.320 --> 00:06:00.850 align:start position:0%
to use has well specified security
considerations<00:05:59.040><c> known</c><00:05:59.370><c> to</c><00:05:59.520><c> us</c><00:05:59.640><c> and</c><00:05:59.940><c> to</c><00:06:00.000><c> others</c>

00:06:00.850 --> 00:06:00.860 align:start position:0%
considerations known to us and to others
 

00:06:00.860 --> 00:06:03.950 align:start position:0%
considerations known to us and to others
well<00:06:01.860><c> allows</c><00:06:02.820><c> for</c><00:06:03.240><c> remote</c><00:06:03.540><c> computation</c>

00:06:03.950 --> 00:06:03.960 align:start position:0%
well allows for remote computation
 

00:06:03.960 --> 00:06:07.730 align:start position:0%
well allows for remote computation
because<00:06:04.320><c> it's</c><00:06:04.470><c> what</c><00:06:05.220><c> going</c><00:06:06.090><c> with</c><00:06:06.300><c> so</c><00:06:06.870><c> as</c><00:06:07.560><c> you</c>

00:06:07.730 --> 00:06:07.740 align:start position:0%
because it's what going with so as you
 

00:06:07.740 --> 00:06:11.180 align:start position:0%
because it's what going with so as you
know<00:06:07.890><c> our</c><00:06:09.230><c> trusted</c><00:06:10.230><c> execution</c><00:06:10.380><c> of</c><00:06:10.650><c> choices</c><00:06:10.980><c> as</c>

00:06:11.180 --> 00:06:11.190 align:start position:0%
know our trusted execution of choices as
 

00:06:11.190 --> 00:06:14.000 align:start position:0%
know our trusted execution of choices as
the<00:06:11.340><c> eggs</c><00:06:11.460><c> or</c><00:06:12.180><c> more</c><00:06:13.110><c> importantly</c><00:06:13.680><c> it's</c><00:06:13.830><c> not</c>

00:06:14.000 --> 00:06:14.010 align:start position:0%
the eggs or more importantly it's not
 

00:06:14.010 --> 00:06:15.980 align:start position:0%
the eggs or more importantly it's not
only<00:06:14.280><c> SDXC</c><00:06:14.790><c> the</c><00:06:15.030><c> technology</c><00:06:15.540><c> stack</c><00:06:15.720><c> that</c><00:06:15.840><c> can</c>

00:06:15.980 --> 00:06:15.990 align:start position:0%
only SDXC the technology stack that can
 

00:06:15.990 --> 00:06:18.080 align:start position:0%
only SDXC the technology stack that can
be<00:06:16.080><c> built</c><00:06:16.290><c> on</c><00:06:16.410><c> top</c><00:06:16.560><c> of</c><00:06:16.620><c> the</c><00:06:16.830><c> HDX</c><00:06:17.130><c> and</c><00:06:17.340><c> we</c>

00:06:18.080 --> 00:06:18.090 align:start position:0%
be built on top of the HDX and we
 

00:06:18.090 --> 00:06:19.580 align:start position:0%
be built on top of the HDX and we
achieve<00:06:18.330><c> it</c><00:06:18.450><c> by</c><00:06:18.570><c> means</c><00:06:18.750><c> of</c><00:06:18.930><c> graphene</c><00:06:19.560><c> graphene</c>

00:06:19.580 --> 00:06:19.590 align:start position:0%
achieve it by means of graphene graphene
 

00:06:19.590 --> 00:06:22.430 align:start position:0%
achieve it by means of graphene graphene
energy<00:06:20.040><c> and</c><00:06:20.450><c> this</c><00:06:21.450><c> is</c><00:06:21.630><c> quite</c><00:06:22.290><c> interesting</c>

00:06:22.430 --> 00:06:22.440 align:start position:0%
energy and this is quite interesting
 

00:06:22.440 --> 00:06:25.580 align:start position:0%
energy and this is quite interesting
stuck<00:06:23.190><c> and</c><00:06:23.400><c> quite</c><00:06:23.669><c> fine</c><00:06:24.120><c> because</c><00:06:24.360><c> it</c><00:06:25.260><c> allows</c>

00:06:25.580 --> 00:06:25.590 align:start position:0%
stuck and quite fine because it allows
 

00:06:25.590 --> 00:06:29.110 align:start position:0%
stuck and quite fine because it allows
us<00:06:25.620><c> to</c><00:06:26.210><c> provide</c><00:06:27.290><c> generic</c>

00:06:29.110 --> 00:06:29.120 align:start position:0%
us to provide generic
 

00:06:29.120 --> 00:06:32.630 align:start position:0%
us to provide generic
computations<00:06:31.220><c> meeting</c><00:06:32.220><c> most</c><00:06:32.430><c> of</c><00:06:32.580><c> the</c>

00:06:32.630 --> 00:06:32.640 align:start position:0%
computations meeting most of the
 

00:06:32.640 --> 00:06:36.529 align:start position:0%
computations meeting most of the
requirements<00:06:33.240><c> with</c><00:06:33.419><c> more</c><00:06:34.410><c> or</c><00:06:34.530><c> less</c><00:06:34.650><c> known</c><00:06:35.539><c> if</c>

00:06:36.529 --> 00:06:36.539 align:start position:0%
requirements with more or less known if
 

00:06:36.539 --> 00:06:38.810 align:start position:0%
requirements with more or less known if
you<00:06:36.720><c> chassis</c><00:06:37.640><c> considerations</c><00:06:38.640><c> and</c>

00:06:38.810 --> 00:06:38.820 align:start position:0%
you chassis considerations and
 

00:06:38.820 --> 00:06:41.029 align:start position:0%
you chassis considerations and
non-security<00:06:39.390><c> considerations</c>

00:06:41.029 --> 00:06:41.039 align:start position:0%
non-security considerations
 

00:06:41.039 --> 00:06:43.589 align:start position:0%
non-security considerations
we<00:06:42.039><c> know</c><00:06:42.219><c> that</c><00:06:42.490><c> the</c><00:06:42.909><c> communities</c><00:06:43.389><c> around</c>

00:06:43.589 --> 00:06:43.599 align:start position:0%
we know that the communities around
 

00:06:43.599 --> 00:06:46.769 align:start position:0%
we know that the communities around
building<00:06:44.379><c> those</c><00:06:44.589><c> well</c><00:06:45.009><c> evolving</c><00:06:45.759><c> in</c><00:06:46.179><c> terms</c><00:06:46.509><c> of</c>

00:06:46.769 --> 00:06:46.779 align:start position:0%
building those well evolving in terms of
 

00:06:46.779 --> 00:06:49.969 align:start position:0%
building those well evolving in terms of
for<00:06:47.499><c> example</c><00:06:47.529><c> security</c><00:06:47.919><c> and</c><00:06:48.460><c> efficiency</c><00:06:48.639><c> and</c>

00:06:49.969 --> 00:06:49.979 align:start position:0%
for example security and efficiency and
 

00:06:49.979 --> 00:06:52.919 align:start position:0%
for example security and efficiency and
this<00:06:50.979><c> is</c><00:06:51.129><c> that's</c><00:06:51.520><c> why</c><00:06:51.759><c> we</c><00:06:51.939><c> move</c><00:06:52.270><c> toward</c><00:06:52.809><c> this</c>

00:06:52.919 --> 00:06:52.929 align:start position:0%
this is that's why we move toward this
 

00:06:52.929 --> 00:06:55.230 align:start position:0%
this is that's why we move toward this
question<00:06:53.319><c> so</c><00:06:53.439><c> just</c><00:06:53.649><c> a</c><00:06:53.949><c> sure</c><00:06:54.069><c> recap</c><00:06:54.369><c> what</c><00:06:54.669><c> axis</c>

00:06:55.230 --> 00:06:55.240 align:start position:0%
question so just a sure recap what axis
 

00:06:55.240 --> 00:06:59.279 align:start position:0%
question so just a sure recap what axis
as<00:06:55.509><c> we</c><00:06:55.689><c> axis</c><00:06:55.929><c> and</c><00:06:56.169><c> Intel</c><00:06:56.619><c> technology</c><00:06:57.099><c> it's</c><00:06:58.289><c> an</c>

00:06:59.279 --> 00:06:59.289 align:start position:0%
as we axis and Intel technology it's an
 

00:06:59.289 --> 00:07:02.549 align:start position:0%
as we axis and Intel technology it's an
architecture<00:07:00.449><c> enhancement</c><00:07:01.449><c> to</c><00:07:01.809><c> the</c><00:07:01.959><c> process</c>

00:07:02.549 --> 00:07:02.559 align:start position:0%
architecture enhancement to the process
 

00:07:02.559 --> 00:07:04.350 align:start position:0%
architecture enhancement to the process
source<00:07:02.800><c> allowing</c><00:07:03.219><c> protection</c><00:07:04.209><c> of</c>

00:07:04.350 --> 00:07:04.360 align:start position:0%
source allowing protection of
 

00:07:04.360 --> 00:07:07.699 align:start position:0%
source allowing protection of
application<00:07:05.319><c> and</c><00:07:05.469><c> the</c><00:07:05.529><c> data</c><00:07:05.740><c> from</c><00:07:06.669><c> the</c>

00:07:07.699 --> 00:07:07.709 align:start position:0%
application and the data from the
 

00:07:07.709 --> 00:07:09.869 align:start position:0%
application and the data from the
processes<00:07:08.709><c> on</c><00:07:08.830><c> the</c><00:07:08.860><c> same</c><00:07:09.099><c> machine</c><00:07:09.279><c> even</c>

00:07:09.869 --> 00:07:09.879 align:start position:0%
processes on the same machine even
 

00:07:09.879 --> 00:07:13.619 align:start position:0%
processes on the same machine even
previous<00:07:10.719><c> ones</c><00:07:11.610><c> this</c><00:07:12.610><c> happens</c><00:07:13.089><c> in</c><00:07:13.270><c> so-called</c>

00:07:13.619 --> 00:07:13.629 align:start position:0%
previous ones this happens in so-called
 

00:07:13.629 --> 00:07:16.290 align:start position:0%
previous ones this happens in so-called
anklet<00:07:13.990><c> compute</c><00:07:14.319><c> model</c><00:07:14.589><c> and</c><00:07:15.300><c> additionally</c>

00:07:16.290 --> 00:07:16.300 align:start position:0%
anklet compute model and additionally
 

00:07:16.300 --> 00:07:20.369 align:start position:0%
anklet compute model and additionally
there<00:07:16.479><c> is</c><00:07:16.509><c> a</c><00:07:17.279><c> way</c><00:07:18.279><c> of</c><00:07:18.309><c> making</c><00:07:18.999><c> sure</c><00:07:19.360><c> that</c><00:07:19.389><c> the</c>

00:07:20.369 --> 00:07:20.379 align:start position:0%
there is a way of making sure that the
 

00:07:20.379 --> 00:07:21.719 align:start position:0%
there is a way of making sure that the
computation<00:07:20.889><c> takes</c><00:07:20.979><c> place</c><00:07:21.249><c> in</c><00:07:21.369><c> the</c><00:07:21.459><c> end</c><00:07:21.550><c> life</c>

00:07:21.719 --> 00:07:21.729 align:start position:0%
computation takes place in the end life
 

00:07:21.729 --> 00:07:24.179 align:start position:0%
computation takes place in the end life
so<00:07:21.909><c> it's</c><00:07:22.149><c> called</c><00:07:22.389><c> remoted</c><00:07:22.839><c> station</c><00:07:23.229><c> so</c><00:07:23.919><c> this</c>

00:07:24.179 --> 00:07:24.189 align:start position:0%
so it's called remoted station so this
 

00:07:24.189 --> 00:07:26.279 align:start position:0%
so it's called remoted station so this
is<00:07:24.339><c> quite</c><00:07:24.789><c> powerful</c><00:07:25.300><c> in</c><00:07:25.330><c> quite</c><00:07:25.569><c> good</c><00:07:25.599><c> the</c>

00:07:26.279 --> 00:07:26.289 align:start position:0%
is quite powerful in quite good the
 

00:07:26.289 --> 00:07:28.350 align:start position:0%
is quite powerful in quite good the
problem<00:07:26.469><c> is</c><00:07:26.740><c> that</c><00:07:26.949><c> well</c><00:07:27.639><c> not</c><00:07:27.879><c> a</c><00:07:27.909><c> problem</c><00:07:28.180><c> the</c>

00:07:28.350 --> 00:07:28.360 align:start position:0%
problem is that well not a problem the
 

00:07:28.360 --> 00:07:31.129 align:start position:0%
problem is that well not a problem the
issue<00:07:28.709><c> that</c><00:07:29.709><c> from</c><00:07:29.919><c> developers</c><00:07:30.279><c> perspective</c>

00:07:31.129 --> 00:07:31.139 align:start position:0%
issue that from developers perspective
 

00:07:31.139 --> 00:07:36.769 align:start position:0%
issue that from developers perspective
it's<00:07:33.059><c> kinda</c><00:07:34.059><c> limited</c><00:07:34.389><c> so</c><00:07:34.899><c> we</c><00:07:35.019><c> can</c><00:07:35.169><c> only</c><00:07:35.499><c> run</c>

00:07:36.769 --> 00:07:36.779 align:start position:0%
it's kinda limited so we can only run
 

00:07:36.779 --> 00:07:38.429 align:start position:0%
it's kinda limited so we can only run
application<00:07:37.779><c> if</c><00:07:37.899><c> you</c><00:07:37.930><c> call</c><00:07:38.139><c> them</c><00:07:38.289><c> from</c>

00:07:38.429 --> 00:07:38.439 align:start position:0%
application if you call them from
 

00:07:38.439 --> 00:07:40.999 align:start position:0%
application if you call them from
scratch<00:07:38.709><c> preferably</c><00:07:39.459><c> using</c><00:07:39.689><c> intellect</c><00:07:40.689><c> ak'</c>

00:07:40.999 --> 00:07:41.009 align:start position:0%
scratch preferably using intellect ak'
 

00:07:41.009 --> 00:07:43.679 align:start position:0%
scratch preferably using intellect ak'
you<00:07:42.009><c> cannot</c><00:07:42.219><c> run</c><00:07:42.429><c> arbitrary</c><00:07:42.580><c> binaries</c><00:07:43.509><c> so</c>

00:07:43.679 --> 00:07:43.689 align:start position:0%
you cannot run arbitrary binaries so
 

00:07:43.689 --> 00:07:46.859 align:start position:0%
you cannot run arbitrary binaries so
they<00:07:43.990><c> have</c><00:07:44.110><c> to</c><00:07:44.229><c> be</c><00:07:44.319><c> modified</c><00:07:44.639><c> and</c><00:07:45.639><c> by</c><00:07:46.509><c> default</c>

00:07:46.859 --> 00:07:46.869 align:start position:0%
they have to be modified and by default
 

00:07:46.869 --> 00:07:49.199 align:start position:0%
they have to be modified and by default
you<00:07:47.229><c> have</c><00:07:47.409><c> to</c><00:07:47.529><c> specify</c><00:07:47.740><c> static</c><00:07:48.159><c> interface</c><00:07:48.580><c> of</c>

00:07:49.199 --> 00:07:49.209 align:start position:0%
you have to specify static interface of
 

00:07:49.209 --> 00:07:50.730 align:start position:0%
you have to specify static interface of
interaction<00:07:49.719><c> between</c><00:07:49.809><c> the</c><00:07:50.139><c> application</c><00:07:50.649><c> in</c>

00:07:50.730 --> 00:07:50.740 align:start position:0%
interaction between the application in
 

00:07:50.740 --> 00:07:51.989 align:start position:0%
interaction between the application in
the<00:07:50.800><c> end</c><00:07:50.919><c> of</c><00:07:50.979><c> life</c><00:07:51.129><c> and</c><00:07:51.249><c> the</c><00:07:51.369><c> untrusted</c><00:07:51.639><c> part</c>

00:07:51.989 --> 00:07:51.999 align:start position:0%
the end of life and the untrusted part
 

00:07:51.999 --> 00:07:53.100 align:start position:0%
the end of life and the untrusted part
of<00:07:52.089><c> application</c><00:07:52.539><c> of</c><00:07:52.599><c> site</c><00:07:52.749><c> of</c><00:07:52.869><c> the</c><00:07:52.959><c> Enclave</c>

00:07:53.100 --> 00:07:53.110 align:start position:0%
of application of site of the Enclave
 

00:07:53.110 --> 00:07:59.059 align:start position:0%
of application of site of the Enclave
the<00:07:53.379><c> host</c><00:07:54.279><c> and</c><00:07:56.309><c> this</c><00:07:57.309><c> is</c><00:07:57.490><c> well</c><00:07:58.089><c> something</c>

00:07:59.059 --> 00:07:59.069 align:start position:0%
the host and this is well something
 

00:07:59.069 --> 00:08:02.850 align:start position:0%
the host and this is well something
kinda<00:08:00.069><c> limiting</c><00:08:00.399><c> so</c><00:08:00.909><c> we</c><00:08:01.360><c> get</c><00:08:01.539><c> this</c><00:08:01.860><c> powerful</c>

00:08:02.850 --> 00:08:02.860 align:start position:0%
kinda limiting so we get this powerful
 

00:08:02.860 --> 00:08:07.709 align:start position:0%
kinda limiting so we get this powerful
feature<00:08:03.129><c> of</c><00:08:04.740><c> running</c><00:08:05.740><c> insecure</c><00:08:06.279><c> ant</c><00:08:06.490><c> life</c><00:08:06.719><c> but</c>

00:08:07.709 --> 00:08:07.719 align:start position:0%
feature of running insecure ant life but
 

00:08:07.719 --> 00:08:09.239 align:start position:0%
feature of running insecure ant life but
at<00:08:07.869><c> the</c><00:08:07.959><c> same</c><00:08:08.139><c> time</c><00:08:08.379><c> we</c><00:08:08.559><c> cannot</c><00:08:08.829><c> run</c><00:08:09.039><c> arbitrary</c>

00:08:09.239 --> 00:08:09.249 align:start position:0%
at the same time we cannot run arbitrary
 

00:08:09.249 --> 00:08:11.459 align:start position:0%
at the same time we cannot run arbitrary
binaries<00:08:09.879><c> which</c><00:08:10.029><c> is</c><00:08:10.180><c> important</c><00:08:10.569><c> to</c><00:08:10.629><c> us</c><00:08:10.749><c> but</c>

00:08:11.459 --> 00:08:11.469 align:start position:0%
binaries which is important to us but
 

00:08:11.469 --> 00:08:13.709 align:start position:0%
binaries which is important to us but
this<00:08:11.709><c> is</c><00:08:11.860><c> a</c><00:08:11.889><c> good</c><00:08:12.550><c> starting</c><00:08:13.269><c> point</c><00:08:13.479><c> good</c>

00:08:13.709 --> 00:08:13.719 align:start position:0%
this is a good starting point good
 

00:08:13.719 --> 00:08:14.759 align:start position:0%
this is a good starting point good
building<00:08:14.050><c> block</c><00:08:14.199><c> for</c><00:08:14.229><c> something</c><00:08:14.649><c> more</c>

00:08:14.759 --> 00:08:14.769 align:start position:0%
building block for something more
 

00:08:14.769 --> 00:08:18.629 align:start position:0%
building block for something more
generic<00:08:14.919><c> and</c><00:08:16.740><c> the</c><00:08:17.740><c> next</c><00:08:17.979><c> step</c><00:08:18.159><c> from</c><00:08:18.399><c> our</c>

00:08:18.629 --> 00:08:18.639 align:start position:0%
generic and the next step from our
 

00:08:18.639 --> 00:08:21.049 align:start position:0%
generic and the next step from our
perspective<00:08:19.089><c> is</c><00:08:19.180><c> graphene</c><00:08:19.569><c> graphene</c><00:08:20.009><c> is</c>

00:08:21.049 --> 00:08:21.059 align:start position:0%
perspective is graphene graphene is
 

00:08:21.059 --> 00:08:24.809 align:start position:0%
perspective is graphene graphene is
libros<00:08:22.059><c> based</c><00:08:22.449><c> framework</c><00:08:23.219><c> which</c><00:08:24.219><c> allows</c><00:08:24.249><c> you</c>

00:08:24.809 --> 00:08:24.819 align:start position:0%
libros based framework which allows you
 

00:08:24.819 --> 00:08:28.139 align:start position:0%
libros based framework which allows you
to<00:08:25.180><c> run</c><00:08:25.389><c> arbitrary</c><00:08:25.659><c> Linux</c><00:08:26.349><c> binaries</c><00:08:27.149><c> in</c>

00:08:28.139 --> 00:08:28.149 align:start position:0%
to run arbitrary Linux binaries in
 

00:08:28.149 --> 00:08:31.859 align:start position:0%
to run arbitrary Linux binaries in
enclaves<00:08:28.919><c> using</c><00:08:29.919><c> all</c><00:08:30.159><c> the</c><00:08:30.309><c> features</c><00:08:31.300><c> of</c><00:08:31.329><c> SGX</c>

00:08:31.859 --> 00:08:31.869 align:start position:0%
enclaves using all the features of SGX
 

00:08:31.869 --> 00:08:36.800 align:start position:0%
enclaves using all the features of SGX
and<00:08:33.930><c> from</c><00:08:34.930><c> the</c><00:08:35.110><c> application</c><00:08:35.709><c> point</c><00:08:35.740><c> of</c><00:08:36.039><c> view</c>

00:08:36.800 --> 00:08:36.810 align:start position:0%
and from the application point of view
 

00:08:36.810 --> 00:08:38.969 align:start position:0%
and from the application point of view
this<00:08:37.810><c> is</c><00:08:37.870><c> just</c><00:08:38.199><c> as</c><00:08:38.319><c> interacting</c><00:08:38.829><c> to</c><00:08:38.889><c> the</c>

00:08:38.969 --> 00:08:38.979 align:start position:0%
this is just as interacting to the
 

00:08:38.979 --> 00:08:40.769 align:start position:0%
this is just as interacting to the
regular<00:08:39.279><c> eyes</c><00:08:39.490><c> so</c><00:08:39.969><c> this</c><00:08:40.120><c> important</c><00:08:40.539><c> this</c><00:08:40.569><c> is</c>

00:08:40.769 --> 00:08:40.779 align:start position:0%
regular eyes so this important this is
 

00:08:40.779 --> 00:08:44.600 align:start position:0%
regular eyes so this important this is
completely<00:08:41.740><c> unmodified</c><00:08:42.389><c> Linux</c><00:08:43.389><c> binary</c><00:08:43.719><c> and</c>

00:08:44.600 --> 00:08:44.610 align:start position:0%
completely unmodified Linux binary and
 

00:08:44.610 --> 00:08:49.410 align:start position:0%
completely unmodified Linux binary and
why<00:08:45.610><c> we</c><00:08:45.819><c> preferred</c><00:08:47.880><c> graphing</c><00:08:48.880><c> over</c><00:08:49.240><c> other</c>

00:08:49.410 --> 00:08:49.420 align:start position:0%
why we preferred graphing over other
 

00:08:49.420 --> 00:08:52.710 align:start position:0%
why we preferred graphing over other
approaches<00:08:49.930><c> well</c><00:08:50.790><c> there</c><00:08:51.790><c> are</c><00:08:51.910><c> a</c><00:08:51.939><c> few</c><00:08:52.149><c> nice</c>

00:08:52.710 --> 00:08:52.720 align:start position:0%
approaches well there are a few nice
 

00:08:52.720 --> 00:08:54.420 align:start position:0%
approaches well there are a few nice
properties<00:08:53.199><c> that</c><00:08:53.350><c> we</c><00:08:53.500><c> are</c><00:08:53.559><c> interested</c><00:08:53.920><c> in</c>

00:08:54.420 --> 00:08:54.430 align:start position:0%
properties that we are interested in
 

00:08:54.430 --> 00:08:57.720 align:start position:0%
properties that we are interested in
the<00:08:54.610><c> first</c><00:08:54.850><c> one</c><00:08:55.060><c> is</c><00:08:55.720><c> that</c><00:08:56.370><c> the</c><00:08:57.370><c> libras</c>

00:08:57.720 --> 00:08:57.730 align:start position:0%
the first one is that the libras
 

00:08:57.730 --> 00:09:01.830 align:start position:0%
the first one is that the libras
approach<00:08:59.130><c> clearly</c><00:09:00.130><c> states</c><00:09:00.520><c> the</c><00:09:01.390><c> distinction</c>

00:09:01.830 --> 00:09:01.840 align:start position:0%
approach clearly states the distinction
 

00:09:01.840 --> 00:09:04.380 align:start position:0%
approach clearly states the distinction
between<00:09:02.020><c> the</c><00:09:02.230><c> trusted</c><00:09:02.530><c> computerize</c><00:09:02.980><c> and</c><00:09:03.390><c> the</c>

00:09:04.380 --> 00:09:04.390 align:start position:0%
between the trusted computerize and the
 

00:09:04.390 --> 00:09:07.130 align:start position:0%
between the trusted computerize and the
attack<00:09:04.690><c> surface</c><00:09:04.870><c> so</c><00:09:05.350><c> as</c><00:09:06.100><c> you</c><00:09:06.220><c> see</c><00:09:06.400><c> less</c><00:09:06.730><c> is</c>

00:09:07.130 --> 00:09:07.140 align:start position:0%
attack surface so as you see less is
 

00:09:07.140 --> 00:09:10.410 align:start position:0%
attack surface so as you see less is
bigger<00:09:08.140><c> than</c><00:09:08.410><c> the</c><00:09:08.620><c> alternative</c><00:09:09.400><c> approach</c><00:09:09.580><c> it</c>

00:09:10.410 --> 00:09:10.420 align:start position:0%
bigger than the alternative approach it
 

00:09:10.420 --> 00:09:13.320 align:start position:0%
bigger than the alternative approach it
contains<00:09:10.990><c> more</c><00:09:11.440><c> code</c><00:09:11.710><c> it</c><00:09:11.950><c> increases</c><00:09:12.820><c> the</c><00:09:13.090><c> size</c>

00:09:13.320 --> 00:09:13.330 align:start position:0%
contains more code it increases the size
 

00:09:13.330 --> 00:09:17.160 align:start position:0%
contains more code it increases the size
of<00:09:13.570><c> the</c><00:09:13.630><c> TCB</c><00:09:14.490><c> but</c><00:09:15.490><c> this</c><00:09:15.880><c> is</c><00:09:16.000><c> the</c><00:09:16.120><c> part</c><00:09:16.360><c> we</c><00:09:16.900><c> and</c>

00:09:17.160 --> 00:09:17.170 align:start position:0%
of the TCB but this is the part we and
 

00:09:17.170 --> 00:09:19.830 align:start position:0%
of the TCB but this is the part we and
invisibility<00:09:17.740><c> Labs</c><00:09:18.250><c> can</c><00:09:18.730><c> work</c><00:09:19.330><c> on</c><00:09:19.480><c> mostly</c>

00:09:19.830 --> 00:09:19.840 align:start position:0%
invisibility Labs can work on mostly
 

00:09:19.840 --> 00:09:21.780 align:start position:0%
invisibility Labs can work on mostly
invisible<00:09:19.990><c> things</c><00:09:20.350><c> lapse</c><00:09:20.500><c> so</c><00:09:20.830><c> they</c><00:09:20.980><c> can</c><00:09:21.160><c> put</c>

00:09:21.780 --> 00:09:21.790 align:start position:0%
invisible things lapse so they can put
 

00:09:21.790 --> 00:09:23.700 align:start position:0%
invisible things lapse so they can put
lots<00:09:21.940><c> of</c><00:09:22.090><c> resources</c><00:09:22.420><c> to</c><00:09:22.810><c> making</c><00:09:23.050><c> it</c><00:09:23.320><c> better</c>

00:09:23.700 --> 00:09:23.710 align:start position:0%
lots of resources to making it better
 

00:09:23.710 --> 00:09:27.300 align:start position:0%
lots of resources to making it better
not<00:09:24.160><c> only</c><00:09:24.310><c> then</c><00:09:24.550><c> the</c><00:09:25.000><c> community</c><00:09:25.350><c> so</c><00:09:26.350><c> we</c><00:09:27.280><c> can</c>

00:09:27.300 --> 00:09:27.310 align:start position:0%
not only then the community so we can
 

00:09:27.310 --> 00:09:29.460 align:start position:0%
not only then the community so we can
improve<00:09:27.910><c> on</c><00:09:28.060><c> that</c><00:09:28.180><c> but</c><00:09:29.080><c> we</c><00:09:29.230><c> have</c><00:09:29.380><c> absolutely</c>

00:09:29.460 --> 00:09:29.470 align:start position:0%
improve on that but we have absolutely
 

00:09:29.470 --> 00:09:31.770 align:start position:0%
improve on that but we have absolutely
no<00:09:29.920><c> control</c><00:09:30.100><c> over</c><00:09:30.430><c> how</c><00:09:30.760><c> the</c><00:09:31.090><c> user</c><00:09:31.270><c> is</c><00:09:31.510><c> going</c><00:09:31.660><c> to</c>

00:09:31.770 --> 00:09:31.780 align:start position:0%
no control over how the user is going to
 

00:09:31.780 --> 00:09:33.570 align:start position:0%
no control over how the user is going to
abuse<00:09:32.140><c> the</c><00:09:32.290><c> interface</c><00:09:32.620><c> so</c><00:09:32.890><c> the</c><00:09:33.070><c> smaller</c><00:09:33.340><c> and</c>

00:09:33.570 --> 00:09:33.580 align:start position:0%
abuse the interface so the smaller and
 

00:09:33.580 --> 00:09:36.480 align:start position:0%
abuse the interface so the smaller and
the<00:09:33.700><c> better</c><00:09:34.600><c> stuff</c><00:09:34.840><c> content</c><00:09:35.170><c> it</c><00:09:35.260><c> is</c><00:09:35.320><c> but</c><00:09:35.950><c> it's</c>

00:09:36.480 --> 00:09:36.490 align:start position:0%
the better stuff content it is but it's
 

00:09:36.490 --> 00:09:40.710 align:start position:0%
the better stuff content it is but it's
simply<00:09:37.120><c> more</c><00:09:37.420><c> secure</c><00:09:39.030><c> places</c><00:09:40.030><c> before</c><00:09:40.300><c> sandbox</c>

00:09:40.710 --> 00:09:40.720 align:start position:0%
simply more secure places before sandbox
 

00:09:40.720 --> 00:09:43.260 align:start position:0%
simply more secure places before sandbox
we<00:09:41.200><c> still</c><00:09:41.410><c> want</c><00:09:41.620><c> to</c><00:09:41.680><c> have</c><00:09:41.950><c> our</c><00:09:42.270><c> provider</c>

00:09:43.260 --> 00:09:43.270 align:start position:0%
we still want to have our provider
 

00:09:43.270 --> 00:09:44.580 align:start position:0%
we still want to have our provider
security<00:09:43.840><c> even</c><00:09:43.990><c> if</c><00:09:44.140><c> you</c><00:09:44.260><c> add</c><00:09:44.350><c> this</c><00:09:44.470><c> additional</c>

00:09:44.580 --> 00:09:44.590 align:start position:0%
security even if you add this additional
 

00:09:44.590 --> 00:09:50.790 align:start position:0%
security even if you add this additional
layer<00:09:44.980><c> and</c><00:09:46.470><c> it's</c><00:09:47.470><c> pretty</c><00:09:47.920><c> cool</c><00:09:48.190><c> because</c><00:09:49.800><c> blue</c>

00:09:50.790 --> 00:09:50.800 align:start position:0%
layer and it's pretty cool because blue
 

00:09:50.800 --> 00:09:54.570 align:start position:0%
layer and it's pretty cool because blue
bars<00:09:51.130><c> can</c><00:09:51.400><c> be</c><00:09:52.320><c> used</c><00:09:53.320><c> in</c><00:09:53.590><c> a</c><00:09:53.650><c> way</c><00:09:53.800><c> where</c><00:09:54.250><c> it's</c>

00:09:54.570 --> 00:09:54.580 align:start position:0%
bars can be used in a way where it's
 

00:09:54.580 --> 00:09:59.070 align:start position:0%
bars can be used in a way where it's
easy<00:09:54.790><c> to</c><00:09:54.880><c> replace</c><00:09:55.180><c> foster</c><00:09:56.110><c> or</c><00:09:56.170><c> gas</c><00:09:56.320><c> device</c><00:09:58.080><c> so</c>

00:09:59.070 --> 00:09:59.080 align:start position:0%
easy to replace foster or gas device so
 

00:09:59.080 --> 00:10:00.540 align:start position:0%
easy to replace foster or gas device so
what's<00:09:59.770><c> the</c><00:09:59.890><c> difference</c><00:10:00.190><c> between</c><00:10:00.280><c> the</c>

00:10:00.540 --> 00:10:00.550 align:start position:0%
what's the difference between the
 

00:10:00.550 --> 00:10:03.090 align:start position:0%
what's the difference between the
regular<00:10:00.850><c> way</c><00:10:01.000><c> you</c><00:10:01.480><c> run</c><00:10:01.660><c> the</c><00:10:01.810><c> app</c><00:10:02.100><c> computation</c>

00:10:03.090 --> 00:10:03.100 align:start position:0%
regular way you run the app computation
 

00:10:03.100 --> 00:10:07.290 align:start position:0%
regular way you run the app computation
and<00:10:03.460><c> the</c><00:10:03.970><c> graphene</c><00:10:04.540><c> well</c><00:10:05.340><c> in</c><00:10:06.340><c> vanilla</c><00:10:06.670><c> SGX</c>

00:10:07.290 --> 00:10:07.300 align:start position:0%
and the graphene well in vanilla SGX
 

00:10:07.300 --> 00:10:09.870 align:start position:0%
and the graphene well in vanilla SGX
well<00:10:08.080><c> using</c><00:10:08.500><c> the</c><00:10:08.740><c> integrals</c><00:10:09.040><c> decay</c><00:10:09.280><c> you</c><00:10:09.700><c> have</c>

00:10:09.870 --> 00:10:09.880 align:start position:0%
well using the integrals decay you have
 

00:10:09.880 --> 00:10:13.140 align:start position:0%
well using the integrals decay you have
to<00:10:10.030><c> get</c><00:10:10.930><c> the</c><00:10:11.080><c> application</c><00:10:11.650><c> source</c><00:10:11.860><c> code</c><00:10:12.150><c> Tyler</c>

00:10:13.140 --> 00:10:13.150 align:start position:0%
to get the application source code Tyler
 

00:10:13.150 --> 00:10:15.990 align:start position:0%
to get the application source code Tyler
it<00:10:13.450><c> to</c><00:10:13.900><c> the</c><00:10:14.080><c> nth</c><00:10:14.560><c> life</c><00:10:14.770><c> compute</c><00:10:15.130><c> model</c><00:10:15.430><c> specify</c>

00:10:15.990 --> 00:10:16.000 align:start position:0%
it to the nth life compute model specify
 

00:10:16.000 --> 00:10:20.280 align:start position:0%
it to the nth life compute model specify
the<00:10:16.060><c> interface</c><00:10:17.400><c> compile</c><00:10:18.400><c> it</c><00:10:18.580><c> and</c><00:10:18.790><c> run</c><00:10:18.930><c> okay</c><00:10:19.930><c> so</c>

00:10:20.280 --> 00:10:20.290 align:start position:0%
the interface compile it and run okay so
 

00:10:20.290 --> 00:10:22.260 align:start position:0%
the interface compile it and run okay so
this<00:10:21.160><c> is</c><00:10:21.310><c> quite</c><00:10:21.490><c> different</c><00:10:21.700><c> to</c><00:10:21.880><c> what</c><00:10:21.970><c> you</c><00:10:22.120><c> have</c>

00:10:22.260 --> 00:10:22.270 align:start position:0%
this is quite different to what you have
 

00:10:22.270 --> 00:10:24.270 align:start position:0%
this is quite different to what you have
to<00:10:22.360><c> do</c><00:10:22.450><c> here</c><00:10:22.630><c> you</c><00:10:23.410><c> get</c><00:10:23.590><c> the</c><00:10:23.740><c> arbitrary</c><00:10:24.100><c> binary</c>

00:10:24.270 --> 00:10:24.280 align:start position:0%
to do here you get the arbitrary binary
 

00:10:24.280 --> 00:10:26.570 align:start position:0%
to do here you get the arbitrary binary
right<00:10:25.240><c> now</c><00:10:25.330><c> it's</c><00:10:25.480><c> well</c><00:10:25.630><c> it's</c><00:10:25.750><c> binary</c>

00:10:26.570 --> 00:10:26.580 align:start position:0%
right now it's well it's binary
 

00:10:26.580 --> 00:10:29.160 align:start position:0%
right now it's well it's binary
Ubuntu<00:10:27.580><c> and</c><00:10:27.670><c> Debian</c><00:10:27.730><c> but</c><00:10:28.150><c> other</c><00:10:28.990><c> than</c><00:10:29.110><c> that</c>

00:10:29.160 --> 00:10:29.170 align:start position:0%
Ubuntu and Debian but other than that
 

00:10:29.170 --> 00:10:32.370 align:start position:0%
Ubuntu and Debian but other than that
it's<00:10:29.560><c> an</c><00:10:30.190><c> arbitrary</c><00:10:30.760><c> binary</c><00:10:30.990><c> you</c><00:10:31.990><c> pack</c><00:10:32.230><c> it</c>

00:10:32.370 --> 00:10:32.380 align:start position:0%
it's an arbitrary binary you pack it
 

00:10:32.380 --> 00:10:34.710 align:start position:0%
it's an arbitrary binary you pack it
with<00:10:32.560><c> the</c><00:10:32.770><c> graphene</c><00:10:33.100><c> and</c><00:10:33.250><c> good</c><00:10:34.240><c> to</c><00:10:34.330><c> go</c>

00:10:34.710 --> 00:10:34.720 align:start position:0%
with the graphene and good to go
 

00:10:34.720 --> 00:10:36.780 align:start position:0%
with the graphene and good to go
almost<00:10:35.650><c> because</c><00:10:36.190><c> this</c><00:10:36.310><c> process</c><00:10:36.610><c> still</c>

00:10:36.780 --> 00:10:36.790 align:start position:0%
almost because this process still
 

00:10:36.790 --> 00:10:38.700 align:start position:0%
almost because this process still
requires<00:10:36.850><c> some</c><00:10:37.450><c> money</c><00:10:38.200><c> well</c><00:10:38.380><c> work</c><00:10:38.560><c> to</c>

00:10:38.700 --> 00:10:38.710 align:start position:0%
requires some money well work to
 

00:10:38.710 --> 00:10:42.050 align:start position:0%
requires some money well work to
configure<00:10:39.130><c> deploy</c><00:10:39.580><c> and</c><00:10:39.850><c> run</c><00:10:40.270><c> the</c><00:10:40.450><c> application</c>

00:10:42.050 --> 00:10:42.060 align:start position:0%
configure deploy and run the application
 

00:10:42.060 --> 00:10:45.300 align:start position:0%
configure deploy and run the application
that's<00:10:43.060><c> why</c><00:10:43.330><c> we</c><00:10:43.510><c> flip</c><00:10:44.320><c> the</c><00:10:44.410><c> next</c><00:10:44.620><c> step</c><00:10:44.770><c> this</c><00:10:45.160><c> is</c>

00:10:45.300 --> 00:10:45.310 align:start position:0%
that's why we flip the next step this is
 

00:10:45.310 --> 00:10:48.420 align:start position:0%
that's why we flip the next step this is
called<00:10:45.520><c> graphene</c><00:10:45.790><c> energy</c><00:10:46.260><c> which</c><00:10:47.260><c> is</c><00:10:47.470><c> graphene</c>

00:10:48.420 --> 00:10:48.430 align:start position:0%
called graphene energy which is graphene
 

00:10:48.430 --> 00:10:52.440 align:start position:0%
called graphene energy which is graphene
it<00:10:49.360><c> was</c><00:10:49.510><c> a</c><00:10:49.540><c> bunch</c><00:10:49.840><c> of</c><00:10:50.190><c> features</c><00:10:51.190><c> that</c><00:10:51.450><c> are</c>

00:10:52.440 --> 00:10:52.450 align:start position:0%
it was a bunch of features that are
 

00:10:52.450 --> 00:10:54.840 align:start position:0%
it was a bunch of features that are
interesting<00:10:53.260><c> and</c><00:10:53.470><c> should</c><00:10:54.070><c> result</c><00:10:54.340><c> in</c><00:10:54.550><c> better</c>

00:10:54.840 --> 00:10:54.850 align:start position:0%
interesting and should result in better
 

00:10:54.850 --> 00:10:59.340 align:start position:0%
interesting and should result in better
UX<00:10:55.380><c> regarding</c><00:10:56.380><c> both</c><00:10:57.690><c> NCLEX</c><00:10:58.690><c> lifecycle</c><00:10:59.170><c> and</c>

00:10:59.340 --> 00:10:59.350 align:start position:0%
UX regarding both NCLEX lifecycle and
 

00:10:59.350 --> 00:11:02.730 align:start position:0%
UX regarding both NCLEX lifecycle and
deploying<00:10:59.710><c> the</c><00:10:59.950><c> application</c><00:11:01.080><c> so</c><00:11:02.080><c> the</c>

00:11:02.730 --> 00:11:02.740 align:start position:0%
deploying the application so the
 

00:11:02.740 --> 00:11:04.230 align:start position:0%
deploying the application so the
protected<00:11:03.130><c> files</c><00:11:03.340><c> the</c><00:11:03.460><c> protective</c><00:11:03.820><c> Isis</c><00:11:04.120><c> that</c>

00:11:04.230 --> 00:11:04.240 align:start position:0%
protected files the protective Isis that
 

00:11:04.240 --> 00:11:07.730 align:start position:0%
protected files the protective Isis that
library<00:11:04.780><c> which</c><00:11:04.900><c> allows</c><00:11:05.940><c> secure</c>

00:11:07.730 --> 00:11:07.740 align:start position:0%
library which allows secure
 

00:11:07.740 --> 00:11:10.400 align:start position:0%
library which allows secure
or<00:11:07.800><c> encrypted</c><00:11:09.050><c> communication</c><00:11:10.050><c> between</c><00:11:10.170><c> the</c>

00:11:10.400 --> 00:11:10.410 align:start position:0%
or encrypted communication between the
 

00:11:10.410 --> 00:11:13.250 align:start position:0%
or encrypted communication between the
owner<00:11:10.590><c> of</c><00:11:10.860><c> the</c><00:11:11.010><c> nth</c><00:11:11.160><c> life</c><00:11:11.370><c> or</c><00:11:12.060><c> any</c><00:11:12.750><c> party</c><00:11:13.230><c> that</c>

00:11:13.250 --> 00:11:13.260 align:start position:0%
owner of the nth life or any party that
 

00:11:13.260 --> 00:11:16.790 align:start position:0%
owner of the nth life or any party that
initiated<00:11:14.010><c> the</c><00:11:14.250><c> computation</c><00:11:14.790><c> and</c><00:11:15.800><c> they</c>

00:11:16.790 --> 00:11:16.800 align:start position:0%
initiated the computation and they
 

00:11:16.800 --> 00:11:19.880 align:start position:0%
initiated the computation and they
aren't<00:11:16.890><c> life</c><00:11:17.040><c> itself</c><00:11:17.400><c> and</c><00:11:18.080><c> host</c><00:11:19.080><c> which</c><00:11:19.380><c> hosts</c>

00:11:19.880 --> 00:11:19.890 align:start position:0%
aren't life itself and host which hosts
 

00:11:19.890 --> 00:11:24.760 align:start position:0%
aren't life itself and host which hosts
the<00:11:21.110><c> graphing</c><00:11:22.110><c> on</c><00:11:22.500><c> the</c><00:11:22.620><c> end</c><00:11:22.770><c> life</c><00:11:23.450><c> cannot</c>

00:11:24.760 --> 00:11:24.770 align:start position:0%
the graphing on the end life cannot
 

00:11:24.770 --> 00:11:27.020 align:start position:0%
the graphing on the end life cannot
interview<00:11:25.770><c> the</c><00:11:26.040><c> files</c><00:11:26.250><c> in</c><00:11:26.460><c> impact</c><00:11:26.760><c> that</c><00:11:26.880><c> way</c>

00:11:27.020 --> 00:11:27.030 align:start position:0%
interview the files in impact that way
 

00:11:27.030 --> 00:11:29.270 align:start position:0%
interview the files in impact that way
the<00:11:27.630><c> peer</c><00:11:27.780><c> support</c><00:11:27.810><c> is</c><00:11:28.140><c> important</c><00:11:28.560><c> because</c><00:11:28.680><c> as</c>

00:11:29.270 --> 00:11:29.280 align:start position:0%
the peer support is important because as
 

00:11:29.280 --> 00:11:31.690 align:start position:0%
the peer support is important because as
I<00:11:29.490><c> said</c><00:11:29.670><c> we</c><00:11:29.820><c> want</c><00:11:29.970><c> to</c><00:11:30.120><c> make</c><00:11:30.240><c> sure</c><00:11:30.420><c> that</c><00:11:30.810><c> the</c>

00:11:31.690 --> 00:11:31.700 align:start position:0%
I said we want to make sure that the
 

00:11:31.700 --> 00:11:34.070 align:start position:0%
I said we want to make sure that the
computing<00:11:32.700><c> side</c><00:11:32.880><c> the</c><00:11:32.970><c> provider</c><00:11:33.270><c> side</c><00:11:33.540><c> is</c>

00:11:34.070 --> 00:11:34.080 align:start position:0%
computing side the provider side is
 

00:11:34.080 --> 00:11:35.900 align:start position:0%
computing side the provider side is
security<00:11:34.470><c> at</c><00:11:34.680><c> the</c><00:11:34.770><c> same</c><00:11:34.950><c> time</c><00:11:35.190><c> it</c><00:11:35.430><c> makes</c><00:11:35.760><c> it</c>

00:11:35.900 --> 00:11:35.910 align:start position:0%
security at the same time it makes it
 

00:11:35.910 --> 00:11:39.160 align:start position:0%
security at the same time it makes it
easier<00:11:36.240><c> to</c><00:11:36.980><c> configure</c><00:11:37.980><c> the</c><00:11:38.340><c> environments</c>

00:11:39.160 --> 00:11:39.170 align:start position:0%
easier to configure the environments
 

00:11:39.170 --> 00:11:41.390 align:start position:0%
easier to configure the environments
tools<00:11:40.170><c> and</c><00:11:40.320><c> scripts</c><00:11:40.560><c> are</c><00:11:40.710><c> there</c><00:11:40.860><c> for</c><00:11:41.070><c> the</c><00:11:41.160><c> UX</c>

00:11:41.390 --> 00:11:41.400 align:start position:0%
tools and scripts are there for the UX
 

00:11:41.400 --> 00:11:44.000 align:start position:0%
tools and scripts are there for the UX
and<00:11:41.610><c> bug</c><00:11:41.940><c> fixes</c><00:11:42.240><c> it's</c><00:11:42.360><c> very</c><00:11:43.230><c> small</c><00:11:43.590><c> point</c><00:11:43.920><c> but</c>

00:11:44.000 --> 00:11:44.010 align:start position:0%
and bug fixes it's very small point but
 

00:11:44.010 --> 00:11:45.050 align:start position:0%
and bug fixes it's very small point but
it's<00:11:44.280><c> very</c><00:11:44.400><c> important</c>

00:11:45.050 --> 00:11:45.060 align:start position:0%
it's very important
 

00:11:45.060 --> 00:11:47.690 align:start position:0%
it's very important
making<00:11:45.930><c> graphene</c><00:11:46.350><c> stable</c><00:11:46.800><c> took</c><00:11:47.370><c> a</c><00:11:47.490><c> lot</c><00:11:47.610><c> of</c>

00:11:47.690 --> 00:11:47.700 align:start position:0%
making graphene stable took a lot of
 

00:11:47.700 --> 00:11:49.340 align:start position:0%
making graphene stable took a lot of
work<00:11:47.850><c> so</c><00:11:48.150><c> it's</c><00:11:48.330><c> a</c><00:11:48.510><c> lot</c><00:11:48.630><c> of</c><00:11:48.660><c> work</c><00:11:48.900><c> put</c><00:11:48.930><c> by</c>

00:11:49.340 --> 00:11:49.350 align:start position:0%
work so it's a lot of work put by
 

00:11:49.350 --> 00:11:53.180 align:start position:0%
work so it's a lot of work put by
invisible<00:11:49.770><c> things</c><00:11:50.220><c> lab</c><00:11:50.400><c> and</c><00:11:51.560><c> all</c><00:11:52.560><c> doubt</c><00:11:52.890><c> there</c>

00:11:53.180 --> 00:11:53.190 align:start position:0%
invisible things lab and all doubt there
 

00:11:53.190 --> 00:11:59.090 align:start position:0%
invisible things lab and all doubt there
we're<00:11:53.970><c> now</c><00:11:54.960><c> or</c><00:11:55.230><c> almost</c><00:11:56.010><c> no</c><00:11:58.100><c> important</c>

00:11:59.090 --> 00:11:59.100 align:start position:0%
we're now or almost no important
 

00:11:59.100 --> 00:12:01.520 align:start position:0%
we're now or almost no important
security<00:11:59.280><c> for</c><00:11:59.640><c> vulnerabilities</c><00:12:00.540><c> there</c><00:12:01.350><c> were</c>

00:12:01.520 --> 00:12:01.530 align:start position:0%
security for vulnerabilities there were
 

00:12:01.530 --> 00:12:03.590 align:start position:0%
security for vulnerabilities there were
quite<00:12:01.800><c> a</c><00:12:01.860><c> lot</c><00:12:02.100><c> of</c><00:12:02.220><c> bug</c><00:12:02.370><c> fixes</c><00:12:02.700><c> we</c><00:12:02.850><c> related</c><00:12:03.420><c> to</c>

00:12:03.590 --> 00:12:03.600 align:start position:0%
quite a lot of bug fixes we related to
 

00:12:03.600 --> 00:12:05.570 align:start position:0%
quite a lot of bug fixes we related to
the<00:12:03.720><c> stability</c><00:12:03.930><c> of</c><00:12:04.260><c> the</c><00:12:04.410><c> solution</c><00:12:04.740><c> so</c><00:12:04.920><c> for</c><00:12:05.460><c> us</c>

00:12:05.570 --> 00:12:05.580 align:start position:0%
the stability of the solution so for us
 

00:12:05.580 --> 00:12:06.980 align:start position:0%
the stability of the solution so for us
it<00:12:05.700><c> is</c><00:12:05.760><c> important</c><00:12:06.180><c> that</c><00:12:06.210><c> those</c><00:12:06.480><c> arbitrary</c>

00:12:06.980 --> 00:12:06.990 align:start position:0%
it is important that those arbitrary
 

00:12:06.990 --> 00:12:10.130 align:start position:0%
it is important that those arbitrary
binaries<00:12:07.800><c> can</c><00:12:07.980><c> really</c><00:12:08.280><c> be</c><00:12:08.450><c> run</c><00:12:09.450><c> and</c><00:12:09.690><c> this</c>

00:12:10.130 --> 00:12:10.140 align:start position:0%
binaries can really be run and this
 

00:12:10.140 --> 00:12:15.590 align:start position:0%
binaries can really be run and this
requires<00:12:10.700><c> stable</c><00:12:11.700><c> graphing</c><00:12:12.980><c> so</c><00:12:14.330><c> the</c><00:12:15.330><c> features</c>

00:12:15.590 --> 00:12:15.600 align:start position:0%
requires stable graphing so the features
 

00:12:15.600 --> 00:12:18.640 align:start position:0%
requires stable graphing so the features
whether<00:12:15.900><c> I</c><00:12:16.290><c> think</c><00:12:16.920><c> there</c><00:12:17.190><c> is</c><00:12:17.250><c> this</c><00:12:17.340><c> way</c><00:12:17.580><c> to</c>

00:12:18.640 --> 00:12:18.650 align:start position:0%
whether I think there is this way to
 

00:12:18.650 --> 00:12:22.760 align:start position:0%
whether I think there is this way to
showcase<00:12:19.650><c> how</c><00:12:20.550><c> it</c><00:12:20.700><c> works</c><00:12:21.240><c> is</c><00:12:21.480><c> just</c><00:12:21.750><c> to</c><00:12:21.900><c> show</c><00:12:22.650><c> an</c>

00:12:22.760 --> 00:12:22.770 align:start position:0%
showcase how it works is just to show an
 

00:12:22.770 --> 00:12:24.440 align:start position:0%
showcase how it works is just to show an
example<00:12:23.130><c> and</c><00:12:23.280><c> boy</c><00:12:23.400><c> accidentally</c><00:12:24.090><c> has</c><00:12:24.240><c> one</c>

00:12:24.440 --> 00:12:24.450 align:start position:0%
example and boy accidentally has one
 

00:12:24.450 --> 00:12:26.780 align:start position:0%
example and boy accidentally has one
such<00:12:24.600><c> example</c><00:12:24.720><c> it's</c><00:12:25.170><c> going</c><00:12:25.860><c> to</c><00:12:26.040><c> be</c><00:12:26.130><c> Asian</c><00:12:26.250><c> with</c>

00:12:26.780 --> 00:12:26.790 align:start position:0%
such example it's going to be Asian with
 

00:12:26.790 --> 00:12:29.440 align:start position:0%
such example it's going to be Asian with
brass<00:12:27.090><c> its</c><00:12:27.600><c> graphene</c><00:12:28.020><c> energy</c><00:12:28.290><c> with</c><00:12:28.950><c> blender</c>

00:12:29.440 --> 00:12:29.450 align:start position:0%
brass its graphene energy with blender
 

00:12:29.450 --> 00:12:32.180 align:start position:0%
brass its graphene energy with blender
it's<00:12:30.450><c> proof</c><00:12:30.690><c> of</c><00:12:30.810><c> concept</c><00:12:31.140><c> for</c><00:12:31.170><c> now</c><00:12:31.410><c> due</c><00:12:31.920><c> to</c><00:12:32.070><c> the</c>

00:12:32.180 --> 00:12:32.190 align:start position:0%
it's proof of concept for now due to the
 

00:12:32.190 --> 00:12:34.220 align:start position:0%
it's proof of concept for now due to the
stability<00:12:32.460><c> issues</c><00:12:33.000><c> for</c><00:12:33.150><c> example</c><00:12:33.480><c> but</c><00:12:34.080><c> other</c>

00:12:34.220 --> 00:12:34.230 align:start position:0%
stability issues for example but other
 

00:12:34.230 --> 00:12:37.390 align:start position:0%
stability issues for example but other
than<00:12:34.350><c> that</c><00:12:34.410><c> it</c><00:12:34.620><c> is</c><00:12:34.650><c> a</c><00:12:34.800><c> working</c><00:12:35.130><c> example</c><00:12:36.170><c> so</c>

00:12:37.390 --> 00:12:37.400 align:start position:0%
than that it is a working example so
 

00:12:37.400 --> 00:12:39.890 align:start position:0%
than that it is a working example so
let's<00:12:38.400><c> take</c><00:12:38.640><c> a</c><00:12:38.670><c> look</c><00:12:38.910><c> at</c><00:12:39.120><c> a</c><00:12:39.150><c> few</c><00:12:39.390><c> points</c><00:12:39.840><c> of</c>

00:12:39.890 --> 00:12:39.900 align:start position:0%
let's take a look at a few points of
 

00:12:39.900 --> 00:12:44.840 align:start position:0%
let's take a look at a few points of
views<00:12:41.060><c> of</c><00:12:42.060><c> how</c><00:12:42.600><c> to</c><00:12:42.660><c> use</c><00:12:43.620><c> the</c><00:12:43.830><c> graphing</c><00:12:44.190><c> the</c>

00:12:44.840 --> 00:12:44.850 align:start position:0%
views of how to use the graphing the
 

00:12:44.850 --> 00:12:46.280 align:start position:0%
views of how to use the graphing the
first<00:12:45.030><c> one</c><00:12:45.180><c> is</c><00:12:45.270><c> the</c><00:12:45.390><c> providers</c><00:12:45.810><c> point</c><00:12:46.050><c> of</c><00:12:46.170><c> view</c>

00:12:46.280 --> 00:12:46.290 align:start position:0%
first one is the providers point of view
 

00:12:46.290 --> 00:12:49.580 align:start position:0%
first one is the providers point of view
so<00:12:46.830><c> the</c><00:12:46.950><c> providers</c><00:12:47.310><c> just</c><00:12:47.430><c> have</c><00:12:47.640><c> to</c><00:12:48.290><c> prepare</c><00:12:49.290><c> an</c>

00:12:49.580 --> 00:12:49.590 align:start position:0%
so the providers just have to prepare an
 

00:12:49.590 --> 00:12:50.800 align:start position:0%
so the providers just have to prepare an
image<00:12:49.710><c> with</c><00:12:50.040><c> arbitrary</c><00:12:50.580><c> application</c>

00:12:50.800 --> 00:12:50.810 align:start position:0%
image with arbitrary application
 

00:12:50.810 --> 00:12:52.970 align:start position:0%
image with arbitrary application
preparing<00:12:51.810><c> this</c><00:12:51.870><c> in</c><00:12:51.990><c> which</c><00:12:52.110><c> is</c><00:12:52.260><c> mostly</c>

00:12:52.970 --> 00:12:52.980 align:start position:0%
preparing this in which is mostly
 

00:12:52.980 --> 00:12:58.510 align:start position:0%
preparing this in which is mostly
automatic<00:12:54.110><c> the</c><00:12:55.110><c> manual</c><00:12:55.410><c> part</c><00:12:55.620><c> is</c><00:12:56.750><c> single</c>

00:12:58.510 --> 00:12:58.520 align:start position:0%
automatic the manual part is single
 

00:12:58.520 --> 00:13:01.310 align:start position:0%
automatic the manual part is single
action<00:12:59.520><c> when</c><00:12:59.670><c> SGX</c><00:13:00.150><c> have</c><00:13:00.300><c> to</c><00:13:00.420><c> be</c><00:13:00.510><c> enabled</c><00:13:00.660><c> this</c>

00:13:01.310 --> 00:13:01.320 align:start position:0%
action when SGX have to be enabled this
 

00:13:01.320 --> 00:13:05.240 align:start position:0%
action when SGX have to be enabled this
may<00:13:01.530><c> require</c><00:13:01.860><c> some</c><00:13:02.670><c> BIOS</c><00:13:03.060><c> tweaking</c><00:13:04.250><c> not</c>

00:13:05.240 --> 00:13:05.250 align:start position:0%
may require some BIOS tweaking not
 

00:13:05.250 --> 00:13:06.440 align:start position:0%
may require some BIOS tweaking not
tweaking<00:13:05.490><c> just</c><00:13:05.790><c> switching</c><00:13:06.090><c> something</c><00:13:06.360><c> in</c>

00:13:06.440 --> 00:13:06.450 align:start position:0%
tweaking just switching something in
 

00:13:06.450 --> 00:13:10.640 align:start position:0%
tweaking just switching something in
BIOS<00:13:06.690><c> and</c><00:13:08.660><c> configuring</c><00:13:09.660><c> protected</c><00:13:10.380><c> files</c>

00:13:10.640 --> 00:13:10.650 align:start position:0%
BIOS and configuring protected files
 

00:13:10.650 --> 00:13:12.820 align:start position:0%
BIOS and configuring protected files
which<00:13:10.950><c> require</c><00:13:11.460><c> central</c><00:13:11.880><c> if</c><00:13:11.940><c> manifest</c><00:13:12.390><c> and</c>

00:13:12.820 --> 00:13:12.830 align:start position:0%
which require central if manifest and
 

00:13:12.830 --> 00:13:15.440 align:start position:0%
which require central if manifest and
specifying<00:13:13.830><c> the</c><00:13:14.070><c> run</c><00:13:14.430><c> docker</c><00:13:14.940><c> parameters</c>

00:13:15.440 --> 00:13:15.450 align:start position:0%
specifying the run docker parameters
 

00:13:15.450 --> 00:13:16.880 align:start position:0%
specifying the run docker parameters
during<00:13:15.600><c> the</c><00:13:15.720><c> run</c><00:13:15.870><c> because</c><00:13:16.050><c> simplify</c><00:13:16.710><c> has</c>

00:13:16.880 --> 00:13:16.890 align:start position:0%
during the run because simplify has
 

00:13:16.890 --> 00:13:19.420 align:start position:0%
during the run because simplify has
nothing<00:13:17.220><c> to</c><00:13:17.250><c> do</c><00:13:17.850><c> with</c><00:13:17.880><c> docker</c><00:13:18.600><c> by</c><00:13:18.810><c> default</c><00:13:19.170><c> so</c>

00:13:19.420 --> 00:13:19.430 align:start position:0%
nothing to do with docker by default so
 

00:13:19.430 --> 00:13:22.070 align:start position:0%
nothing to do with docker by default so
those<00:13:20.430><c> protected</c><00:13:20.970><c> files</c><00:13:21.150><c> have</c><00:13:21.270><c> to</c><00:13:21.360><c> come</c>

00:13:22.070 --> 00:13:22.080 align:start position:0%
those protected files have to come
 

00:13:22.080 --> 00:13:24.830 align:start position:0%
those protected files have to come
on<00:13:22.230><c> both</c><00:13:22.500><c> sides</c><00:13:22.950><c> in</c><00:13:23.490><c> the</c><00:13:23.670><c> end</c><00:13:23.820><c> life</c><00:13:23.970><c> and</c><00:13:24.210><c> with</c>

00:13:24.830 --> 00:13:24.840 align:start position:0%
on both sides in the end life and with
 

00:13:24.840 --> 00:13:28.880 align:start position:0%
on both sides in the end life and with
doctor<00:13:25.200><c> but</c><00:13:26.120><c> other</c><00:13:27.120><c> than</c><00:13:27.330><c> that</c><00:13:27.500><c> is</c><00:13:28.500><c> almost</c>

00:13:28.880 --> 00:13:28.890 align:start position:0%
doctor but other than that is almost
 

00:13:28.890 --> 00:13:30.980 align:start position:0%
doctor but other than that is almost
automatic<00:13:29.460><c> so</c><00:13:29.580><c> the</c><00:13:30.360><c> user</c><00:13:30.510><c> prepares</c><00:13:30.930><c> the</c>

00:13:30.980 --> 00:13:30.990 align:start position:0%
automatic so the user prepares the
 

00:13:30.990 --> 00:13:32.750 align:start position:0%
automatic so the user prepares the
container<00:13:31.290><c> deriving</c><00:13:31.680><c> it</c><00:13:31.890><c> from</c><00:13:31.920><c> the</c><00:13:32.220><c> provided</c>

00:13:32.750 --> 00:13:32.760 align:start position:0%
container deriving it from the provided
 

00:13:32.760 --> 00:13:34.700 align:start position:0%
container deriving it from the provided
one<00:13:33.000><c> the</c><00:13:33.540><c> one</c><00:13:33.690><c> with</c><00:13:33.840><c> one</c><00:13:34.200><c> image</c><00:13:34.350><c> the</c><00:13:34.470><c> exten</c>

00:13:34.700 --> 00:13:34.710 align:start position:0%
one the one with one image the exten
 

00:13:34.710 --> 00:13:37.130 align:start position:0%
one the one with one image the exten
plate<00:13:34.860><c> is</c><00:13:35.010><c> the</c><00:13:35.190><c> one</c><00:13:35.310><c> that's</c><00:13:35.490><c> ready</c><00:13:35.990><c> the</c><00:13:36.990><c> user</c>

00:13:37.130 --> 00:13:37.140 align:start position:0%
plate is the one that's ready the user
 

00:13:37.140 --> 00:13:39.380 align:start position:0%
plate is the one that's ready the user
app<00:13:37.350><c> is</c><00:13:37.530><c> whatever</c><00:13:37.800><c> the</c><00:13:38.370><c> user</c><00:13:38.580><c> chooses</c><00:13:38.790><c> to</c><00:13:39.060><c> to</c>

00:13:39.380 --> 00:13:39.390 align:start position:0%
app is whatever the user chooses to to
 

00:13:39.390 --> 00:13:44.540 align:start position:0%
app is whatever the user chooses to to
be<00:13:39.540><c> the</c><00:13:40.230><c> key</c><00:13:40.880><c> is</c><00:13:41.990><c> something</c><00:13:42.990><c> that</c><00:13:43.340><c> user</c><00:13:44.340><c> can</c>

00:13:44.540 --> 00:13:44.550 align:start position:0%
be the key is something that user can
 

00:13:44.550 --> 00:13:49.550 align:start position:0%
be the key is something that user can
either<00:13:44.780><c> generate</c><00:13:46.610><c> using</c><00:13:47.610><c> a</c><00:13:47.850><c> script</c><00:13:48.090><c> or</c><00:13:48.390><c> it</c><00:13:49.320><c> can</c>

00:13:49.550 --> 00:13:49.560 align:start position:0%
either generate using a script or it can
 

00:13:49.560 --> 00:13:54.110 align:start position:0%
either generate using a script or it can
be<00:13:50.510><c> used</c><00:13:51.510><c> by</c><00:13:51.750><c> well</c><00:13:52.740><c> from</c><00:13:52.920><c> other</c><00:13:53.100><c> resource</c><00:13:53.430><c> and</c>

00:13:54.110 --> 00:13:54.120 align:start position:0%
be used by well from other resource and
 

00:13:54.120 --> 00:13:56.450 align:start position:0%
be used by well from other resource and
the<00:13:54.660><c> key</c><00:13:54.840><c> can</c><00:13:55.050><c> be</c><00:13:55.080><c> the</c><00:13:55.740><c> eastern</c><00:13:56.040><c> used</c><00:13:56.190><c> to</c><00:13:56.310><c> sign</c>

00:13:56.450 --> 00:13:56.460 align:start position:0%
the key can be the eastern used to sign
 

00:13:56.460 --> 00:13:58.130 align:start position:0%
the key can be the eastern used to sign
the<00:13:56.490><c> consecrated</c><00:13:56.940><c> container</c><00:13:57.420><c> it</c><00:13:57.630><c> happens</c>

00:13:58.130 --> 00:13:58.140 align:start position:0%
the consecrated container it happens
 

00:13:58.140 --> 00:14:01.490 align:start position:0%
the consecrated container it happens
with<00:13:59.070><c> script</c><00:14:00.030><c> as</c><00:14:00.300><c> well</c><00:14:00.510><c> so</c><00:14:00.900><c> it</c><00:14:01.050><c> is</c><00:14:01.170><c> mostly</c>

00:14:01.490 --> 00:14:01.500 align:start position:0%
with script as well so it is mostly
 

00:14:01.500 --> 00:14:03.320 align:start position:0%
with script as well so it is mostly
automatic<00:14:01.920><c> exactly</c><00:14:02.670><c> the</c><00:14:02.760><c> same</c><00:14:02.910><c> process</c><00:14:03.060><c> was</c>

00:14:03.320 --> 00:14:03.330 align:start position:0%
automatic exactly the same process was
 

00:14:03.330 --> 00:14:06.470 align:start position:0%
automatic exactly the same process was
used<00:14:03.510><c> to</c><00:14:03.750><c> prepare</c><00:14:04.100><c> go</c><00:14:05.100><c> an</c><00:14:05.300><c> integration</c><00:14:06.300><c> and</c>

00:14:06.470 --> 00:14:06.480 align:start position:0%
used to prepare go an integration and
 

00:14:06.480 --> 00:14:09.500 align:start position:0%
used to prepare go an integration and
blender<00:14:06.810><c> integration</c><00:14:07.290><c> so</c><00:14:07.440><c> it</c><00:14:08.340><c> was</c><00:14:08.510><c> nothing</c>

00:14:09.500 --> 00:14:09.510 align:start position:0%
blender integration so it was nothing
 

00:14:09.510 --> 00:14:11.390 align:start position:0%
blender integration so it was nothing
different<00:14:09.630><c> only</c><00:14:10.230><c> thing</c><00:14:10.440><c> is</c><00:14:10.560><c> that</c><00:14:10.590><c> we</c><00:14:11.100><c> have</c><00:14:11.370><c> a</c>

00:14:11.390 --> 00:14:11.400 align:start position:0%
different only thing is that we have a
 

00:14:11.400 --> 00:14:13.400 align:start position:0%
different only thing is that we have a
specified<00:14:11.880><c> application</c><00:14:12.450><c> this</c><00:14:12.750><c> arbitrary</c><00:14:13.230><c> up</c>

00:14:13.400 --> 00:14:13.410 align:start position:0%
specified application this arbitrary up
 

00:14:13.410 --> 00:14:18.170 align:start position:0%
specified application this arbitrary up
and<00:14:14.070><c> the</c><00:14:14.220><c> arbitrary</c><00:14:14.520><c> miss</c><00:14:14.730><c> bender</c><00:14:15.030><c> here</c><00:14:17.180><c> okay</c>

00:14:18.170 --> 00:14:18.180 align:start position:0%
and the arbitrary miss bender here okay
 

00:14:18.180 --> 00:14:21.650 align:start position:0%
and the arbitrary miss bender here okay
so<00:14:19.070><c> the</c><00:14:20.070><c> point</c><00:14:20.310><c> of</c><00:14:20.490><c> view</c><00:14:20.670><c> of</c><00:14:20.850><c> the</c><00:14:21.000><c> handshake</c>

00:14:21.650 --> 00:14:21.660 align:start position:0%
so the point of view of the handshake
 

00:14:21.660 --> 00:14:23.390 align:start position:0%
so the point of view of the handshake
process<00:14:21.960><c> I'm</c><00:14:22.590><c> not</c><00:14:22.740><c> going</c><00:14:22.920><c> to</c><00:14:22.980><c> describe</c><00:14:23.220><c> in</c>

00:14:23.390 --> 00:14:23.400 align:start position:0%
process I'm not going to describe in
 

00:14:23.400 --> 00:14:26.180 align:start position:0%
process I'm not going to describe in
detail<00:14:23.700><c> but</c><00:14:23.880><c> the</c><00:14:24.690><c> point</c><00:14:24.900><c> here</c><00:14:24.930><c> is</c><00:14:25.170><c> that</c><00:14:25.200><c> this</c>

00:14:26.180 --> 00:14:26.190 align:start position:0%
detail but the point here is that this
 

00:14:26.190 --> 00:14:30.980 align:start position:0%
detail but the point here is that this
process<00:14:26.460><c> allows</c><00:14:27.180><c> the</c><00:14:28.490><c> requester</c><00:14:29.490><c> to</c><00:14:29.990><c> connect</c>

00:14:30.980 --> 00:14:30.990 align:start position:0%
process allows the requester to connect
 

00:14:30.990 --> 00:14:34.640 align:start position:0%
process allows the requester to connect
with<00:14:31.440><c> the</c><00:14:32.370><c> end</c><00:14:32.520><c> life</c><00:14:33.110><c> provider</c><00:14:34.110><c> machine</c><00:14:34.500><c> and</c>

00:14:34.640 --> 00:14:34.650 align:start position:0%
with the end life provider machine and
 

00:14:34.650 --> 00:14:39.410 align:start position:0%
with the end life provider machine and
the<00:14:34.740><c> hosted</c><00:14:35.610><c> binary</c><00:14:36.590><c> to</c><00:14:37.590><c> entrusted</c><00:14:38.130><c> one</c><00:14:39.120><c> trust</c>

00:14:39.410 --> 00:14:39.420 align:start position:0%
the hosted binary to entrusted one trust
 

00:14:39.420 --> 00:14:42.440 align:start position:0%
the hosted binary to entrusted one trust
encrypted<00:14:39.840><c> channel</c><00:14:40.140><c> and</c><00:14:41.030><c> what's</c><00:14:42.030><c> important</c>

00:14:42.440 --> 00:14:42.450 align:start position:0%
encrypted channel and what's important
 

00:14:42.450 --> 00:14:44.290 align:start position:0%
encrypted channel and what's important
here<00:14:42.570><c> is</c><00:14:42.690><c> that</c><00:14:42.720><c> it's</c><00:14:43.080><c> mostly</c><00:14:43.470><c> automatic</c><00:14:43.920><c> and</c>

00:14:44.290 --> 00:14:44.300 align:start position:0%
here is that it's mostly automatic and
 

00:14:44.300 --> 00:14:46.760 align:start position:0%
here is that it's mostly automatic and
if<00:14:45.300><c> it's</c><00:14:45.600><c> not</c><00:14:45.840><c> then</c><00:14:46.050><c> there</c><00:14:46.170><c> are</c><00:14:46.260><c> scripts</c><00:14:46.560><c> to</c>

00:14:46.760 --> 00:14:46.770 align:start position:0%
if it's not then there are scripts to
 

00:14:46.770 --> 00:14:49.520 align:start position:0%
if it's not then there are scripts to
assist<00:14:47.610><c> here</c><00:14:47.850><c> so</c><00:14:48.450><c> it</c><00:14:48.900><c> was</c><00:14:49.110><c> important</c><00:14:49.500><c> for</c>

00:14:49.520 --> 00:14:49.530 align:start position:0%
assist here so it was important for
 

00:14:49.530 --> 00:14:51.440 align:start position:0%
assist here so it was important for
volume<00:14:49.860><c> integration</c><00:14:50.100><c> because</c><00:14:50.520><c> the</c><00:14:51.300><c> user</c>

00:14:51.440 --> 00:14:51.450 align:start position:0%
volume integration because the user
 

00:14:51.450 --> 00:14:54.140 align:start position:0%
volume integration because the user
interact<00:14:51.810><c> interacts</c><00:14:52.290><c> with</c><00:14:52.470><c> the</c><00:14:52.620><c> go</c><00:14:53.610><c> and</c><00:14:53.820><c> buy</c>

00:14:54.140 --> 00:14:54.150 align:start position:0%
interact interacts with the go and buy
 

00:14:54.150 --> 00:14:56.480 align:start position:0%
interact interacts with the go and buy
UI<00:14:54.450><c> and</c><00:14:54.840><c> it's</c><00:14:55.290><c> not</c><00:14:55.740><c> really</c><00:14:55.950><c> interested</c><00:14:56.370><c> in</c>

00:14:56.480 --> 00:14:56.490 align:start position:0%
UI and it's not really interested in
 

00:14:56.490 --> 00:14:58.820 align:start position:0%
UI and it's not really interested in
seeing<00:14:56.700><c> all</c><00:14:57.450><c> this</c><00:14:57.720><c> so</c><00:14:58.230><c> this</c><00:14:58.470><c> happens</c>

00:14:58.820 --> 00:14:58.830 align:start position:0%
seeing all this so this happens
 

00:14:58.830 --> 00:15:00.200 align:start position:0%
seeing all this so this happens
automatically<00:14:59.250><c> and</c><00:14:59.490><c> there's</c><00:14:59.640><c> script</c>

00:15:00.200 --> 00:15:00.210 align:start position:0%
automatically and there's script
 

00:15:00.210 --> 00:15:06.530 align:start position:0%
automatically and there's script
verifying<00:15:00.900><c> quote</c><00:15:01.800><c> for</c><00:15:02.250><c> example</c><00:15:04.280><c> and</c><00:15:05.280><c> yeah</c><00:15:06.060><c> the</c>

00:15:06.530 --> 00:15:06.540 align:start position:0%
verifying quote for example and yeah the
 

00:15:06.540 --> 00:15:08.450 align:start position:0%
verifying quote for example and yeah the
more<00:15:06.890><c> interesting</c><00:15:07.890><c> point</c><00:15:08.070><c> of</c><00:15:08.160><c> view</c><00:15:08.220><c> of</c><00:15:08.400><c> the</c>

00:15:08.450 --> 00:15:08.460 align:start position:0%
more interesting point of view of the
 

00:15:08.460 --> 00:15:12.440 align:start position:0%
more interesting point of view of the
application<00:15:08.550><c> so</c><00:15:09.800><c> the</c><00:15:10.800><c> application</c><00:15:11.270><c> point</c><00:15:12.270><c> of</c>

00:15:12.440 --> 00:15:12.450 align:start position:0%
application so the application point of
 

00:15:12.450 --> 00:15:14.870 align:start position:0%
application so the application point of
view<00:15:12.510><c> is</c><00:15:12.720><c> what</c><00:15:12.930><c> you</c><00:15:13.020><c> see</c><00:15:13.170><c> on</c><00:15:13.260><c> the</c><00:15:13.350><c> left</c><00:15:13.880><c> simply</c>

00:15:14.870 --> 00:15:14.880 align:start position:0%
view is what you see on the left simply
 

00:15:14.880 --> 00:15:15.260 align:start position:0%
view is what you see on the left simply
noting

00:15:15.260 --> 00:15:15.270 align:start position:0%
noting
 

00:15:15.270 --> 00:15:18.860 align:start position:0%
noting
application<00:15:15.870><c> sees</c><00:15:16.290><c> it</c><00:15:16.470><c> as</c><00:15:16.740><c> a</c><00:15:16.800><c> regular</c><00:15:17.870><c> regular</c>

00:15:18.860 --> 00:15:18.870 align:start position:0%
application sees it as a regular regular
 

00:15:18.870 --> 00:15:22.970 align:start position:0%
application sees it as a regular regular
IO<00:15:19.050><c> and</c><00:15:20.180><c> that's</c><00:15:21.180><c> it</c><00:15:21.360><c> no</c><00:15:21.870><c> changes</c><00:15:22.260><c> if</c><00:15:22.680><c> you</c><00:15:22.800><c> take</c>

00:15:22.970 --> 00:15:22.980 align:start position:0%
IO and that's it no changes if you take
 

00:15:22.980 --> 00:15:24.230 align:start position:0%
IO and that's it no changes if you take
a<00:15:23.010><c> step</c><00:15:23.280><c> back</c><00:15:23.460><c> then</c><00:15:23.670><c> you</c><00:15:23.760><c> see</c><00:15:23.940><c> that</c><00:15:24.120><c> the</c>

00:15:24.230 --> 00:15:24.240 align:start position:0%
a step back then you see that the
 

00:15:24.240 --> 00:15:26.210 align:start position:0%
a step back then you see that the
framework<00:15:24.600><c> is</c><00:15:24.720><c> there</c><00:15:24.990><c> the</c><00:15:25.620><c> logic</c><00:15:25.860><c> is</c><00:15:26.010><c> there</c>

00:15:26.210 --> 00:15:26.220 align:start position:0%
framework is there the logic is there
 

00:15:26.220 --> 00:15:28.580 align:start position:0%
framework is there the logic is there
and<00:15:26.430><c> it's</c><00:15:27.270><c> doing</c><00:15:27.690><c> its</c><00:15:27.900><c> job</c><00:15:28.080><c> under</c><00:15:28.320><c> the</c><00:15:28.440><c> hood</c>

00:15:28.580 --> 00:15:28.590 align:start position:0%
and it's doing its job under the hood
 

00:15:28.590 --> 00:15:31.130 align:start position:0%
and it's doing its job under the hood
for<00:15:29.400><c> example</c><00:15:29.820><c> they</c><00:15:30.210><c> I</c><00:15:30.240><c> always</c><00:15:30.510><c> encrypted</c><00:15:30.780><c> and</c>

00:15:31.130 --> 00:15:31.140 align:start position:0%
for example they I always encrypted and
 

00:15:31.140 --> 00:15:33.350 align:start position:0%
for example they I always encrypted and
decrypted<00:15:31.230><c> and</c><00:15:31.650><c> fly</c><00:15:31.830><c> so</c>

00:15:33.350 --> 00:15:33.360 align:start position:0%
decrypted and fly so
 

00:15:33.360 --> 00:15:36.320 align:start position:0%
decrypted and fly so
it's<00:15:33.959><c> it's</c><00:15:34.740><c> there</c><00:15:35.010><c> to</c><00:15:35.160><c> be</c><00:15:35.490><c> transparent</c><00:15:36.120><c> to</c><00:15:36.209><c> the</c>

00:15:36.320 --> 00:15:36.330 align:start position:0%
it's it's there to be transparent to the
 

00:15:36.330 --> 00:15:40.759 align:start position:0%
it's it's there to be transparent to the
application<00:15:36.839><c> and</c><00:15:36.990><c> in</c><00:15:37.080><c> fact</c><00:15:37.260><c> to</c><00:15:37.380><c> users</c><00:15:39.769><c> okay</c>

00:15:40.759 --> 00:15:40.769 align:start position:0%
application and in fact to users okay
 

00:15:40.769 --> 00:15:43.310 align:start position:0%
application and in fact to users okay
one<00:15:41.370><c> more</c><00:15:41.610><c> important</c><00:15:42.029><c> and</c><00:15:42.240><c> interesting</c><00:15:42.870><c> point</c>

00:15:43.310 --> 00:15:43.320 align:start position:0%
one more important and interesting point
 

00:15:43.320 --> 00:15:44.870 align:start position:0%
one more important and interesting point
of<00:15:43.440><c> view</c><00:15:43.500><c> is</c><00:15:43.680><c> requester</c><00:15:44.100><c> point</c><00:15:44.310><c> of</c><00:15:44.459><c> view</c><00:15:44.580><c> so</c>

00:15:44.870 --> 00:15:44.880 align:start position:0%
of view is requester point of view so
 

00:15:44.880 --> 00:15:48.560 align:start position:0%
of view is requester point of view so
requester<00:15:45.779><c> still</c><00:15:46.110><c> has</c><00:15:46.350><c> to</c><00:15:46.589><c> interact</c><00:15:47.519><c> with</c><00:15:48.390><c> the</c>

00:15:48.560 --> 00:15:48.570 align:start position:0%
requester still has to interact with the
 

00:15:48.570 --> 00:15:51.560 align:start position:0%
requester still has to interact with the
nodes<00:15:48.810><c> in</c><00:15:48.990><c> the</c><00:15:49.019><c> network</c><00:15:49.110><c> and</c><00:15:50.269><c> connect</c><00:15:51.269><c> to</c><00:15:51.360><c> them</c>

00:15:51.560 --> 00:15:51.570 align:start position:0%
nodes in the network and connect to them
 

00:15:51.570 --> 00:15:53.960 align:start position:0%
nodes in the network and connect to them
should<00:15:52.079><c> choose</c><00:15:52.320><c> the</c><00:15:52.500><c> notes</c><00:15:52.740><c> we</c><00:15:53.700><c> should</c>

00:15:53.960 --> 00:15:53.970 align:start position:0%
should choose the notes we should
 

00:15:53.970 --> 00:15:56.900 align:start position:0%
should choose the notes we should
compute<00:15:54.810><c> something</c><00:15:54.990><c> to</c><00:15:55.170><c> him</c><00:15:55.350><c> but</c><00:15:56.279><c> it</c><00:15:56.459><c> can</c><00:15:56.730><c> be</c>

00:15:56.900 --> 00:15:56.910 align:start position:0%
compute something to him but it can be
 

00:15:56.910 --> 00:16:00.019 align:start position:0%
compute something to him but it can be
envisioned<00:15:57.870><c> as</c><00:15:57.990><c> if</c><00:15:58.829><c> the</c><00:15:59.070><c> requester</c><00:15:59.550><c> was</c><00:15:59.700><c> using</c>

00:16:00.019 --> 00:16:00.029 align:start position:0%
envisioned as if the requester was using
 

00:16:00.029 --> 00:16:02.449 align:start position:0%
envisioned as if the requester was using
more<00:16:00.750><c> locally</c><00:16:01.440><c> available</c><00:16:01.589><c> resources</c>

00:16:02.449 --> 00:16:02.459 align:start position:0%
more locally available resources
 

00:16:02.459 --> 00:16:04.639 align:start position:0%
more locally available resources
of<00:16:02.790><c> course</c><00:16:03.060><c> this</c><00:16:03.180><c> resources</c><00:16:03.779><c> are</c><00:16:03.959><c> not</c>

00:16:04.639 --> 00:16:04.649 align:start position:0%
of course this resources are not
 

00:16:04.649 --> 00:16:06.800 align:start position:0%
of course this resources are not
available<00:16:04.860><c> all</c><00:16:05.310><c> the</c><00:16:05.339><c> time</c><00:16:05.540><c> but</c><00:16:06.540><c> other</c><00:16:06.720><c> than</c>

00:16:06.800 --> 00:16:06.810 align:start position:0%
available all the time but other than
 

00:16:06.810 --> 00:16:10.639 align:start position:0%
available all the time but other than
that<00:16:07.370><c> it</c><00:16:08.370><c> can</c><00:16:09.000><c> be</c><00:16:09.120><c> treated</c><00:16:09.480><c> well</c><00:16:09.899><c> requester</c>

00:16:10.639 --> 00:16:10.649 align:start position:0%
that it can be treated well requester
 

00:16:10.649 --> 00:16:13.250 align:start position:0%
that it can be treated well requester
can<00:16:10.829><c> treat</c><00:16:11.010><c> them</c><00:16:11.190><c> just</c><00:16:11.339><c> as</c><00:16:11.519><c> maybe</c><00:16:12.329><c> not</c><00:16:12.570><c> all</c><00:16:12.779><c> the</c>

00:16:13.250 --> 00:16:13.260 align:start position:0%
can treat them just as maybe not all the
 

00:16:13.260 --> 00:16:15.050 align:start position:0%
can treat them just as maybe not all the
time<00:16:13.380><c> available</c><00:16:13.740><c> local</c><00:16:14.250><c> resources</c><00:16:14.670><c> making</c>

00:16:15.050 --> 00:16:15.060 align:start position:0%
time available local resources making
 

00:16:15.060 --> 00:16:19.730 align:start position:0%
time available local resources making
his<00:16:15.390><c> computer</c><00:16:16.140><c> more</c><00:16:16.350><c> powerful</c><00:16:17.779><c> so</c><00:16:18.779><c> yeah</c><00:16:19.290><c> as</c><00:16:19.589><c> I</c>

00:16:19.730 --> 00:16:19.740 align:start position:0%
his computer more powerful so yeah as I
 

00:16:19.740 --> 00:16:22.130 align:start position:0%
his computer more powerful so yeah as I
said<00:16:19.800><c> we</c><00:16:20.550><c> have</c><00:16:20.700><c> a</c><00:16:20.730><c> working</c><00:16:21.060><c> example</c><00:16:21.180><c> work</c>

00:16:22.130 --> 00:16:22.140 align:start position:0%
said we have a working example work
 

00:16:22.140 --> 00:16:25.130 align:start position:0%
said we have a working example work
integration<00:16:22.620><c> you</c><00:16:23.610><c> can</c><00:16:23.690><c> get</c><00:16:24.690><c> more</c><00:16:24.870><c> information</c>

00:16:25.130 --> 00:16:25.140 align:start position:0%
integration you can get more information
 

00:16:25.140 --> 00:16:27.310 align:start position:0%
integration you can get more information
about<00:16:25.410><c> it</c><00:16:25.560><c> at</c><00:16:25.769><c> our</c><00:16:25.890><c> booth</c><00:16:26.130><c> and</c><00:16:26.730><c> see</c><00:16:26.850><c> the</c><00:16:26.940><c> demo</c>

00:16:27.310 --> 00:16:27.320 align:start position:0%
about it at our booth and see the demo
 

00:16:27.320 --> 00:16:29.449 align:start position:0%
about it at our booth and see the demo
what<00:16:28.320><c> we</c><00:16:28.500><c> achieved</c><00:16:28.829><c> with</c><00:16:28.890><c> this</c><00:16:29.070><c> integration</c>

00:16:29.449 --> 00:16:29.459 align:start position:0%
what we achieved with this integration
 

00:16:29.459 --> 00:16:31.639 align:start position:0%
what we achieved with this integration
is<00:16:29.700><c> well</c><00:16:30.149><c> we</c><00:16:30.300><c> proved</c><00:16:30.600><c> that</c><00:16:30.779><c> the</c><00:16:30.959><c> graphing</c><00:16:31.470><c> and</c>

00:16:31.639 --> 00:16:31.649 align:start position:0%
is well we proved that the graphing and
 

00:16:31.649 --> 00:16:34.639 align:start position:0%
is well we proved that the graphing and
G<00:16:31.769><c> approach</c><00:16:32.100><c> is</c><00:16:32.250><c> the</c><00:16:32.670><c> valid</c><00:16:32.940><c> one</c><00:16:33.089><c> and</c><00:16:33.329><c> that</c><00:16:34.170><c> the</c>

00:16:34.639 --> 00:16:34.649 align:start position:0%
G approach is the valid one and that the
 

00:16:34.649 --> 00:16:37.400 align:start position:0%
G approach is the valid one and that the
features<00:16:35.010><c> that</c><00:16:35.310><c> it</c><00:16:35.760><c> offers</c><00:16:36.029><c> can</c><00:16:36.750><c> be</c><00:16:36.779><c> used</c><00:16:37.140><c> to</c>

00:16:37.400 --> 00:16:37.410 align:start position:0%
features that it offers can be used to
 

00:16:37.410 --> 00:16:40.730 align:start position:0%
features that it offers can be used to
make<00:16:38.310><c> such</c><00:16:38.520><c> an</c><00:16:38.610><c> integration</c>

00:16:40.730 --> 00:16:40.740 align:start position:0%
make such an integration
 

00:16:40.740 --> 00:16:43.699 align:start position:0%
make such an integration
it<00:16:41.459><c> offered</c><00:16:41.940><c> what</c><00:16:42.660><c> we</c><00:16:42.810><c> wanted</c><00:16:43.050><c> confidential</c>

00:16:43.699 --> 00:16:43.709 align:start position:0%
it offered what we wanted confidential
 

00:16:43.709 --> 00:16:46.870 align:start position:0%
it offered what we wanted confidential
remote<00:16:44.100><c> computation</c><00:16:44.899><c> with</c><00:16:45.899><c> arbitrary</c><00:16:46.560><c> binary</c>

00:16:46.870 --> 00:16:46.880 align:start position:0%
remote computation with arbitrary binary
 

00:16:46.880 --> 00:16:49.850 align:start position:0%
remote computation with arbitrary binary
well<00:16:47.880><c> the</c><00:16:48.180><c> blender</c><00:16:48.480><c> is</c><00:16:48.630><c> binary</c><00:16:49.320><c> of</c><00:16:49.470><c> choice</c><00:16:49.620><c> but</c>

00:16:49.850 --> 00:16:49.860 align:start position:0%
well the blender is binary of choice but
 

00:16:49.860 --> 00:16:52.940 align:start position:0%
well the blender is binary of choice but
it<00:16:50.130><c> could</c><00:16:50.279><c> be</c><00:16:50.399><c> any</c><00:16:50.579><c> binary</c><00:16:51.260><c> well</c><00:16:52.260><c> Linux</c><00:16:52.649><c> binary</c>

00:16:52.940 --> 00:16:52.950 align:start position:0%
it could be any binary well Linux binary
 

00:16:52.950 --> 00:16:55.880 align:start position:0%
it could be any binary well Linux binary
at<00:16:53.070><c> all</c><00:16:53.220><c> and</c><00:16:54.050><c> what's</c><00:16:55.050><c> more</c><00:16:55.200><c> important</c><00:16:55.680><c> is</c><00:16:55.829><c> that</c>

00:16:55.880 --> 00:16:55.890 align:start position:0%
at all and what's more important is that
 

00:16:55.890 --> 00:16:58.490 align:start position:0%
at all and what's more important is that
it's<00:16:56.370><c> a</c><00:16:56.700><c> clear</c><00:16:57.420><c> decoupling</c><00:16:57.930><c> of</c><00:16:58.110><c> the</c><00:16:58.260><c> binary</c>

00:16:58.490 --> 00:16:58.500 align:start position:0%
it's a clear decoupling of the binary
 

00:16:58.500 --> 00:17:01.430 align:start position:0%
it's a clear decoupling of the binary
and<00:16:58.740><c> in</c><00:16:59.279><c> the</c><00:16:59.399><c> application</c><00:16:59.940><c> that</c><00:17:00.690><c> is</c><00:17:00.810><c> hosted</c><00:17:01.260><c> on</c>

00:17:01.430 --> 00:17:01.440 align:start position:0%
and in the application that is hosted on
 

00:17:01.440 --> 00:17:02.870 align:start position:0%
and in the application that is hosted on
the<00:17:01.829><c> infrastructure</c><00:17:02.220><c> in</c><00:17:02.399><c> the</c><00:17:02.490><c> infrastructure</c>

00:17:02.870 --> 00:17:02.880 align:start position:0%
the infrastructure in the infrastructure
 

00:17:02.880 --> 00:17:05.059 align:start position:0%
the infrastructure in the infrastructure
itself<00:17:03.029><c> so</c><00:17:03.540><c> the</c><00:17:03.690><c> infrastructure</c><00:17:04.169><c> is</c><00:17:04.319><c> SGX</c><00:17:04.740><c> and</c>

00:17:05.059 --> 00:17:05.069 align:start position:0%
itself so the infrastructure is SGX and
 

00:17:05.069 --> 00:17:07.850 align:start position:0%
itself so the infrastructure is SGX and
the<00:17:05.790><c> application</c><00:17:06.240><c> is</c><00:17:06.329><c> an</c><00:17:06.480><c> application</c><00:17:06.860><c> which</c>

00:17:07.850 --> 00:17:07.860 align:start position:0%
the application is an application which
 

00:17:07.860 --> 00:17:10.819 align:start position:0%
the application is an application which
can<00:17:07.919><c> be</c><00:17:08.189><c> seen</c><00:17:08.760><c> as</c><00:17:08.970><c> a</c><00:17:09.620><c> SGX</c><00:17:10.620><c> as</c><00:17:10.740><c> an</c>

00:17:10.819 --> 00:17:10.829 align:start position:0%
can be seen as a SGX as an
 

00:17:10.829 --> 00:17:12.140 align:start position:0%
can be seen as a SGX as an
infrastructure<00:17:11.250><c> from</c><00:17:11.669><c> one</c><00:17:11.880><c> perspective</c>

00:17:12.140 --> 00:17:12.150 align:start position:0%
infrastructure from one perspective
 

00:17:12.150 --> 00:17:15.049 align:start position:0%
infrastructure from one perspective
which<00:17:12.689><c> is</c><00:17:12.720><c> important</c><00:17:13.230><c> because</c><00:17:13.650><c> we</c><00:17:13.949><c> can</c><00:17:14.130><c> rent</c>

00:17:15.049 --> 00:17:15.059 align:start position:0%
which is important because we can rent
 

00:17:15.059 --> 00:17:17.299 align:start position:0%
which is important because we can rent
out<00:17:15.240><c> we</c><00:17:15.600><c> can</c><00:17:15.780><c> provide</c><00:17:16.380><c> us</c><00:17:16.559><c> can</c><00:17:16.679><c> rent</c><00:17:16.829><c> out</c><00:17:16.919><c> this</c>

00:17:17.299 --> 00:17:17.309 align:start position:0%
out we can provide us can rent out this
 

00:17:17.309 --> 00:17:22.429 align:start position:0%
out we can provide us can rent out this
platform<00:17:18.650><c> ok</c><00:17:19.650><c> so</c><00:17:20.220><c> it</c><00:17:20.970><c> is</c><00:17:21.089><c> pretty</c><00:17:21.270><c> cool</c><00:17:21.569><c> but</c>

00:17:22.429 --> 00:17:22.439 align:start position:0%
platform ok so it is pretty cool but
 

00:17:22.439 --> 00:17:25.220 align:start position:0%
platform ok so it is pretty cool but
there<00:17:22.770><c> are</c><00:17:22.860><c> still</c><00:17:23.419><c> there</c><00:17:24.419><c> is</c><00:17:24.540><c> still</c><00:17:24.780><c> some</c><00:17:25.020><c> more</c>

00:17:25.220 --> 00:17:25.230 align:start position:0%
there are still there is still some more
 

00:17:25.230 --> 00:17:28.250 align:start position:0%
there are still there is still some more
work<00:17:25.410><c> to</c><00:17:25.439><c> do</c><00:17:25.650><c> both</c><00:17:26.069><c> on</c><00:17:26.309><c> our</c><00:17:26.459><c> side</c><00:17:26.880><c> and</c><00:17:27.089><c> in</c><00:17:27.959><c> the</c>

00:17:28.250 --> 00:17:28.260 align:start position:0%
work to do both on our side and in the
 

00:17:28.260 --> 00:17:31.750 align:start position:0%
work to do both on our side and in the
general<00:17:28.590><c> SGX</c><00:17:29.070><c> intro</c><00:17:29.550><c> side</c><00:17:29.960><c> you</c><00:17:30.960><c> name</c><00:17:31.140><c> it</c><00:17:31.290><c> so</c>

00:17:31.750 --> 00:17:31.760 align:start position:0%
general SGX intro side you name it so
 

00:17:31.760 --> 00:17:36.980 align:start position:0%
general SGX intro side you name it so
what<00:17:32.760><c> would</c><00:17:32.910><c> be</c><00:17:32.970><c> fine</c><00:17:33.300><c> to</c><00:17:33.570><c> have</c><00:17:33.600><c> is</c><00:17:35.990><c> liberated</c>

00:17:36.980 --> 00:17:36.990 align:start position:0%
what would be fine to have is liberated
 

00:17:36.990 --> 00:17:39.350 align:start position:0%
what would be fine to have is liberated
in<00:17:37.230><c> the</c><00:17:37.650><c> interrelation</c><00:17:38.370><c> service</c><00:17:38.700><c> so</c><00:17:38.850><c> that</c><00:17:38.880><c> we</c>

00:17:39.350 --> 00:17:39.360 align:start position:0%
in the interrelation service so that we
 

00:17:39.360 --> 00:17:41.240 align:start position:0%
in the interrelation service so that we
don't<00:17:39.570><c> need</c><00:17:39.720><c> this</c><00:17:39.870><c> central</c><00:17:40.290><c> point</c><00:17:40.470><c> at</c><00:17:40.890><c> Estoril</c>

00:17:41.240 --> 00:17:41.250 align:start position:0%
don't need this central point at Estoril
 

00:17:41.250 --> 00:17:43.760 align:start position:0%
don't need this central point at Estoril
and<00:17:41.400><c> place</c><00:17:42.230><c> flexible</c><00:17:43.230><c> launch</c><00:17:43.410><c> control</c>

00:17:43.760 --> 00:17:43.770 align:start position:0%
and place flexible launch control
 

00:17:43.770 --> 00:17:46.330 align:start position:0%
and place flexible launch control
meaning<00:17:43.980><c> that</c><00:17:44.220><c> for</c><00:17:44.669><c> now</c><00:17:44.820><c> inter</c><00:17:45.090><c> controls</c>

00:17:46.330 --> 00:17:46.340 align:start position:0%
meaning that for now inter controls
 

00:17:46.340 --> 00:17:49.660 align:start position:0%
meaning that for now inter controls
the<00:17:47.210><c> Whalers</c><00:17:47.870><c> include</c><00:17:48.320><c> so</c><00:17:48.440><c> lunch</c><00:17:48.650><c> and</c><00:17:48.890><c> can</c>

00:17:49.660 --> 00:17:49.670 align:start position:0%
the Whalers include so lunch and can
 

00:17:49.670 --> 00:17:52.390 align:start position:0%
the Whalers include so lunch and can
potentially<00:17:50.680><c> disallow</c><00:17:51.680><c> so</c><00:17:51.890><c> many</c><00:17:52.070><c> lives</c><00:17:52.220><c> to</c><00:17:52.310><c> be</c>

00:17:52.390 --> 00:17:52.400 align:start position:0%
potentially disallow so many lives to be
 

00:17:52.400 --> 00:17:54.280 align:start position:0%
potentially disallow so many lives to be
lunch<00:17:52.550><c> so</c><00:17:52.700><c> this</c><00:17:52.880><c> should</c><00:17:53.090><c> be</c><00:17:53.300><c> you</c><00:17:54.020><c> should</c><00:17:54.260><c> be</c>

00:17:54.280 --> 00:17:54.290 align:start position:0%
lunch so this should be you should be
 

00:17:54.290 --> 00:17:56.950 align:start position:0%
lunch so this should be you should be
able<00:17:54.470><c> to</c><00:17:55.000><c> write</c><00:17:56.000><c> your</c><00:17:56.180><c> own</c><00:17:56.240><c> lunch</c><00:17:56.510><c> and</c><00:17:56.750><c> life</c>

00:17:56.950 --> 00:17:56.960 align:start position:0%
able to write your own lunch and life
 

00:17:56.960 --> 00:17:59.950 align:start position:0%
able to write your own lunch and life
and<00:17:57.140><c> lunch</c><00:17:57.650><c> any</c><00:17:57.860><c> ant</c><00:17:58.010><c> with</c><00:17:58.160><c> you</c><00:17:58.310><c> you</c><00:17:58.970><c> will</c><00:17:59.120><c> you</c>

00:17:59.950 --> 00:17:59.960 align:start position:0%
and lunch any ant with you you will you
 

00:17:59.960 --> 00:18:03.150 align:start position:0%
and lunch any ant with you you will you
wish<00:18:00.700><c> another</c><00:18:01.700><c> thing</c><00:18:01.970><c> is</c><00:18:02.150><c> that</c><00:18:02.180><c> there</c><00:18:02.900><c> are</c>

00:18:03.150 --> 00:18:03.160 align:start position:0%
wish another thing is that there are
 

00:18:03.160 --> 00:18:07.050 align:start position:0%
wish another thing is that there are
some<00:18:04.160><c> known</c><00:18:04.610><c> attacks</c><00:18:05.000><c> to</c><00:18:05.630><c> enclaves</c><00:18:05.990><c> and</c>

00:18:07.050 --> 00:18:07.060 align:start position:0%
some known attacks to enclaves and
 

00:18:07.060 --> 00:18:09.130 align:start position:0%
some known attacks to enclaves and
mitigation<00:18:08.060><c> steps</c><00:18:08.360><c> are</c><00:18:08.540><c> required</c><00:18:08.630><c> for</c><00:18:09.080><c> these</c>

00:18:09.130 --> 00:18:09.140 align:start position:0%
mitigation steps are required for these
 

00:18:09.140 --> 00:18:11.380 align:start position:0%
mitigation steps are required for these
attacks<00:18:09.410><c> and</c><00:18:09.680><c> we</c><00:18:10.370><c> need</c><00:18:10.550><c> to</c><00:18:10.670><c> increase</c><00:18:11.180><c> the</c>

00:18:11.380 --> 00:18:11.390 align:start position:0%
attacks and we need to increase the
 

00:18:11.390 --> 00:18:14.830 align:start position:0%
attacks and we need to increase the
efficiency<00:18:12.050><c> of</c><00:18:12.200><c> the</c><00:18:12.320><c> solution</c><00:18:12.740><c> so</c><00:18:13.690><c> this</c><00:18:14.690><c> is</c>

00:18:14.830 --> 00:18:14.840 align:start position:0%
efficiency of the solution so this is
 

00:18:14.840 --> 00:18:17.890 align:start position:0%
efficiency of the solution so this is
from<00:18:15.320><c> the</c><00:18:15.470><c> as</c><00:18:15.800><c> the</c><00:18:16.010><c> Excite</c><00:18:16.400><c> we</c><00:18:17.330><c> want</c><00:18:17.540><c> stable</c>

00:18:17.890 --> 00:18:17.900 align:start position:0%
from the as the Excite we want stable
 

00:18:17.900 --> 00:18:21.220 align:start position:0%
from the as the Excite we want stable
and<00:18:18.050><c> efficient</c><00:18:18.320><c> graphene</c><00:18:18.710><c> and</c><00:18:19.750><c> this</c><00:18:20.750><c> requires</c>

00:18:21.220 --> 00:18:21.230 align:start position:0%
and efficient graphene and this requires
 

00:18:21.230 --> 00:18:23.730 align:start position:0%
and efficient graphene and this requires
back<00:18:21.710><c> fixing</c><00:18:22.100><c> proof</c><00:18:22.640><c> as</c><00:18:22.760><c> computation</c><00:18:23.330><c> for</c>

00:18:23.730 --> 00:18:23.740 align:start position:0%
back fixing proof as computation for
 

00:18:23.740 --> 00:18:25.870 align:start position:0%
back fixing proof as computation for
economy<00:18:24.740><c> and</c><00:18:24.770><c> windows</c><00:18:25.280><c> support</c><00:18:25.640><c> because</c>

00:18:25.870 --> 00:18:25.880 align:start position:0%
economy and windows support because
 

00:18:25.880 --> 00:18:28.200 align:start position:0%
economy and windows support because
right<00:18:26.030><c> now</c><00:18:26.150><c> we</c><00:18:26.210><c> have</c><00:18:26.390><c> only</c><00:18:26.510><c> Linux</c><00:18:26.810><c> binaries</c><00:18:27.500><c> so</c>

00:18:28.200 --> 00:18:28.210 align:start position:0%
right now we have only Linux binaries so
 

00:18:28.210 --> 00:18:30.880 align:start position:0%
right now we have only Linux binaries so
this<00:18:29.210><c> is</c><00:18:29.360><c> proof</c><00:18:29.600><c> of</c><00:18:29.720><c> concept</c><00:18:30.170><c> this</c><00:18:30.470><c> requires</c>

00:18:30.880 --> 00:18:30.890 align:start position:0%
this is proof of concept this requires
 

00:18:30.890 --> 00:18:34.090 align:start position:0%
this is proof of concept this requires
additional<00:18:31.730><c> work</c><00:18:32.180><c> but</c><00:18:32.420><c> we</c><00:18:32.630><c> can</c><00:18:33.040><c> talk</c><00:18:34.040><c> about</c>

00:18:34.090 --> 00:18:34.100 align:start position:0%
additional work but we can talk about
 

00:18:34.100 --> 00:18:35.800 align:start position:0%
additional work but we can talk about
use<00:18:34.490><c> cases</c><00:18:34.700><c> that</c><00:18:34.820><c> potentially</c><00:18:35.420><c> can</c><00:18:35.510><c> benefit</c>

00:18:35.800 --> 00:18:35.810 align:start position:0%
use cases that potentially can benefit
 

00:18:35.810 --> 00:18:37.870 align:start position:0%
use cases that potentially can benefit
from<00:18:35.900><c> this</c><00:18:36.140><c> stack</c><00:18:36.350><c> so</c><00:18:36.860><c> the</c><00:18:36.980><c> first</c><00:18:37.190><c> one</c><00:18:37.340><c> is</c><00:18:37.370><c> one</c>

00:18:37.870 --> 00:18:37.880 align:start position:0%
from this stack so the first one is one
 

00:18:37.880 --> 00:18:41.920 align:start position:0%
from this stack so the first one is one
specific<00:18:38.120><c> is</c><00:18:38.540><c> local</c><00:18:38.960><c> brief</c><00:18:39.290><c> occasion</c><00:18:40.330><c> EPA</c><00:18:41.330><c> you</c>

00:18:41.920 --> 00:18:41.930 align:start position:0%
specific is local brief occasion EPA you
 

00:18:41.930 --> 00:18:44.380 align:start position:0%
specific is local brief occasion EPA you
know<00:18:42.050><c> you</c><00:18:42.110><c> have</c><00:18:42.290><c> about</c><00:18:42.530><c> two</c><00:18:42.740><c> minutes</c><00:18:43.000><c> okay</c><00:18:44.000><c> so</c>

00:18:44.380 --> 00:18:44.390 align:start position:0%
know you have about two minutes okay so
 

00:18:44.390 --> 00:18:46.270 align:start position:0%
know you have about two minutes okay so
we<00:18:44.510><c> look</c><00:18:44.660><c> at</c><00:18:44.750><c> verification</c><00:18:45.320><c> you</c><00:18:45.410><c> just</c><00:18:45.620><c> make</c>

00:18:46.270 --> 00:18:46.280 align:start position:0%
we look at verification you just make
 

00:18:46.280 --> 00:18:48.340 align:start position:0%
we look at verification you just make
sure<00:18:46.310><c> that</c><00:18:46.630><c> the</c><00:18:47.630><c> verification</c><00:18:48.080><c> takes</c><00:18:48.140><c> place</c>

00:18:48.340 --> 00:18:48.350 align:start position:0%
sure that the verification takes place
 

00:18:48.350 --> 00:18:50.590 align:start position:0%
sure that the verification takes place
on<00:18:48.470><c> provider</c><00:18:48.770><c> machine</c><00:18:49.190><c> usually</c><00:18:49.940><c> takes</c><00:18:50.180><c> place</c>

00:18:50.590 --> 00:18:50.600 align:start position:0%
on provider machine usually takes place
 

00:18:50.600 --> 00:18:52.480 align:start position:0%
on provider machine usually takes place
on<00:18:50.870><c> request</c><00:18:51.140><c> or</c><00:18:51.290><c> machine</c><00:18:51.530><c> and</c><00:18:51.740><c> you</c><00:18:52.190><c> don't</c><00:18:52.370><c> lose</c>

00:18:52.480 --> 00:18:52.490 align:start position:0%
on request or machine and you don't lose
 

00:18:52.490 --> 00:18:55.390 align:start position:0%
on request or machine and you don't lose
any<00:18:52.760><c> trustworthiness</c><00:18:53.570><c> this</c><00:18:53.900><c> way</c><00:18:54.160><c> other</c><00:18:55.160><c> one</c>

00:18:55.390 --> 00:18:55.400 align:start position:0%
any trustworthiness this way other one
 

00:18:55.400 --> 00:18:57.310 align:start position:0%
any trustworthiness this way other one
is<00:18:55.520><c> gamma</c><00:18:55.790><c> limited</c><00:18:56.180><c> anomaly</c><00:18:56.780><c> that</c><00:18:56.930><c> you</c><00:18:57.110><c> have</c><00:18:57.290><c> a</c>

00:18:57.310 --> 00:18:57.320 align:start position:0%
is gamma limited anomaly that you have a
 

00:18:57.320 --> 00:19:00.370 align:start position:0%
is gamma limited anomaly that you have a
run<00:18:57.830><c> like</c><00:18:58.010><c> setting</c><00:18:58.400><c> we've</c><00:18:58.910><c> trusted</c><00:18:59.380><c> computers</c>

00:19:00.370 --> 00:19:00.380 align:start position:0%
run like setting we've trusted computers
 

00:19:00.380 --> 00:19:02.770 align:start position:0%
run like setting we've trusted computers
you<00:19:00.980><c> can</c><00:19:01.160><c> equip</c><00:19:01.430><c> them</c><00:19:01.640><c> with</c><00:19:01.670><c> ESRI</c><00:19:02.060><c> X</c><00:19:02.210><c> me</c><00:19:02.360><c> making</c>

00:19:02.770 --> 00:19:02.780 align:start position:0%
you can equip them with ESRI X me making
 

00:19:02.780 --> 00:19:08.560 align:start position:0%
you can equip them with ESRI X me making
a<00:19:02.960><c> more</c><00:19:03.230><c> powerful</c><00:19:03.910><c> SGX</c><00:19:04.910><c> node</c><00:19:05.360><c> and</c><00:19:07.420><c> expose</c><00:19:08.420><c> it</c>

00:19:08.560 --> 00:19:08.570 align:start position:0%
a more powerful SGX node and expose it
 

00:19:08.570 --> 00:19:12.960 align:start position:0%
a more powerful SGX node and expose it
for<00:19:08.630><c> example</c><00:19:09.020><c> to</c><00:19:09.200><c> encode</c><00:19:09.770><c> transcode</c><00:19:10.640><c> movies</c>

00:19:12.960 --> 00:19:12.970 align:start position:0%
for example to encode transcode movies
 

00:19:12.970 --> 00:19:15.130 align:start position:0%
for example to encode transcode movies
Identity<00:19:13.970><c> Management</c><00:19:14.270><c> inside</c><00:19:14.630><c> and</c><00:19:14.810><c> golem</c>

00:19:15.130 --> 00:19:15.140 align:start position:0%
Identity Management inside and golem
 

00:19:15.140 --> 00:19:18.030 align:start position:0%
Identity Management inside and golem
Network<00:19:15.470><c> gamma</c><00:19:16.190><c> meter</c><00:19:16.400><c> network</c><00:19:16.760><c> this</c><00:19:17.270><c> makes</c>

00:19:18.030 --> 00:19:18.040 align:start position:0%
Network gamma meter network this makes
 

00:19:18.040 --> 00:19:21.160 align:start position:0%
Network gamma meter network this makes
sense<00:19:19.040><c> because</c><00:19:19.280><c> it's</c><00:19:19.850><c> easier</c><00:19:20.120><c> to</c><00:19:20.180><c> seal</c><00:19:20.960><c> the</c>

00:19:21.160 --> 00:19:21.170 align:start position:0%
sense because it's easier to seal the
 

00:19:21.170 --> 00:19:23.530 align:start position:0%
sense because it's easier to seal the
identities<00:19:21.920><c> well</c><00:19:22.100><c> keys</c><00:19:22.340><c> inside</c><00:19:23.150><c> the</c><00:19:23.300><c> enclaves</c>

00:19:23.530 --> 00:19:23.540 align:start position:0%
identities well keys inside the enclaves
 

00:19:23.540 --> 00:19:27.370 align:start position:0%
identities well keys inside the enclaves
and<00:19:23.870><c> provider</c><00:19:24.710><c> knows</c><00:19:24.950><c> and</c><00:19:26.020><c> work</c><00:19:27.020><c> with</c><00:19:27.200><c> them</c>

00:19:27.370 --> 00:19:27.380 align:start position:0%
and provider knows and work with them
 

00:19:27.380 --> 00:19:30.490 align:start position:0%
and provider knows and work with them
automatically<00:19:28.660><c> or</c><00:19:29.660><c> other</c><00:19:29.870><c> use</c><00:19:30.110><c> cases</c><00:19:30.350><c> that</c>

00:19:30.490 --> 00:19:30.500 align:start position:0%
automatically or other use cases that
 

00:19:30.500 --> 00:19:32.290 align:start position:0%
automatically or other use cases that
people<00:19:31.190><c> can</c><00:19:31.340><c> come</c><00:19:31.520><c> up</c><00:19:31.640><c> with</c><00:19:31.670><c> should</c><00:19:31.970><c> be</c><00:19:32.000><c> able</c>

00:19:32.290 --> 00:19:32.300 align:start position:0%
people can come up with should be able
 

00:19:32.300 --> 00:19:35.260 align:start position:0%
people can come up with should be able
to<00:19:33.070><c> benefit</c><00:19:34.070><c> from</c><00:19:34.130><c> this</c><00:19:34.490><c> technology</c>

00:19:35.260 --> 00:19:35.270 align:start position:0%
to benefit from this technology
 

00:19:35.270 --> 00:19:37.170 align:start position:0%
to benefit from this technology
wider<00:19:36.110><c> audience</c><00:19:36.500><c> for</c><00:19:36.620><c> example</c>

00:19:37.170 --> 00:19:37.180 align:start position:0%
wider audience for example
 

00:19:37.180 --> 00:19:41.110 align:start position:0%
wider audience for example
decentralizing<00:19:38.180><c> server</c><00:19:38.780><c> services</c><00:19:39.790><c> we</c><00:19:40.790><c> can</c><00:19:40.970><c> do</c>

00:19:41.110 --> 00:19:41.120 align:start position:0%
decentralizing server services we can do
 

00:19:41.120 --> 00:19:42.790 align:start position:0%
decentralizing server services we can do
it<00:19:41.240><c> using</c><00:19:41.420><c> the</c><00:19:41.630><c> STX</c><00:19:41.900><c> of</c><00:19:42.050><c> course</c><00:19:42.230><c> it</c><00:19:42.350><c> is</c><00:19:42.470><c> not</c><00:19:42.650><c> an</c>

00:19:42.790 --> 00:19:42.800 align:start position:0%
it using the STX of course it is not an
 

00:19:42.800 --> 00:19:45.100 align:start position:0%
it using the STX of course it is not an
easy<00:19:42.920><c> task</c><00:19:43.190><c> because</c><00:19:44.120><c> decentralizing</c><00:19:44.990><c> may</c>

00:19:45.100 --> 00:19:45.110 align:start position:0%
easy task because decentralizing may
 

00:19:45.110 --> 00:19:47.140 align:start position:0%
easy task because decentralizing may
require<00:19:45.380><c> additional</c><00:19:45.530><c> algorithms</c><00:19:46.250><c> but</c><00:19:46.970><c> the</c>

00:19:47.140 --> 00:19:47.150 align:start position:0%
require additional algorithms but the
 

00:19:47.150 --> 00:19:49.510 align:start position:0%
require additional algorithms but the
building<00:19:47.450><c> block</c><00:19:47.630><c> is</c><00:19:47.810><c> there</c><00:19:47.960><c> and</c><00:19:48.530><c> it</c><00:19:49.340><c> may</c><00:19:49.460><c> be</c>

00:19:49.510 --> 00:19:49.520 align:start position:0%
building block is there and it may be
 

00:19:49.520 --> 00:19:51.310 align:start position:0%
building block is there and it may be
potentially<00:19:49.970><c> used</c><00:19:50.150><c> by</c><00:19:50.300><c> sector</c><00:19:50.840><c> multi-party</c>

00:19:51.310 --> 00:19:51.320 align:start position:0%
potentially used by sector multi-party
 

00:19:51.320 --> 00:19:52.660 align:start position:0%
potentially used by sector multi-party
computation<00:19:51.530><c> it</c><00:19:52.160><c> may</c><00:19:52.280><c> be</c><00:19:52.340><c> used</c><00:19:52.550><c> to</c>

00:19:52.660 --> 00:19:52.670 align:start position:0%
computation it may be used to
 

00:19:52.670 --> 00:19:55.930 align:start position:0%
computation it may be used to
decentralized<00:19:53.300><c> constant</c><00:19:53.810><c> service</c><00:19:54.940><c> atomic</c>

00:19:55.930 --> 00:19:55.940 align:start position:0%
decentralized constant service atomic
 

00:19:55.940 --> 00:19:58.210 align:start position:0%
decentralized constant service atomic
swap<00:19:56.150><c> well</c><00:19:56.510><c> we</c><00:19:56.900><c> can</c><00:19:57.080><c> do</c><00:19:57.200><c> it</c><00:19:57.350><c> well</c><00:19:57.800><c> we</c><00:19:57.830><c> can</c><00:19:58.040><c> do</c><00:19:58.130><c> it</c>

00:19:58.210 --> 00:19:58.220 align:start position:0%
swap well we can do it well we can do it
 

00:19:58.220 --> 00:19:59.650 align:start position:0%
swap well we can do it well we can do it
it<00:19:58.340><c> can</c><00:19:58.550><c> be</c><00:19:58.700><c> done</c>

00:19:59.650 --> 00:19:59.660 align:start position:0%
it can be done
 

00:19:59.660 --> 00:20:01.450 align:start position:0%
it can be done
it<00:19:59.810><c> has</c><00:19:59.990><c> some</c><00:20:00.200><c> problems</c><00:20:00.530><c> because</c><00:20:00.680><c> in</c><00:20:01.190><c> atomic</c>

00:20:01.450 --> 00:20:01.460 align:start position:0%
it has some problems because in atomic
 

00:20:01.460 --> 00:20:02.920 align:start position:0%
it has some problems because in atomic
swap<00:20:01.790><c> you</c><00:20:01.910><c> need</c><00:20:02.090><c> to</c><00:20:02.270><c> make</c><00:20:02.450><c> sure</c><00:20:02.480><c> that</c><00:20:02.810><c> the</c>

00:20:02.920 --> 00:20:02.930 align:start position:0%
swap you need to make sure that the
 

00:20:02.930 --> 00:20:04.450 align:start position:0%
swap you need to make sure that the
application<00:20:03.020><c> has</c><00:20:03.500><c> not</c><00:20:03.560><c> only</c><00:20:03.830><c> not</c><00:20:03.980><c> forged</c><00:20:04.310><c> but</c>

00:20:04.450 --> 00:20:04.460 align:start position:0%
application has not only not forged but
 

00:20:04.460 --> 00:20:07.390 align:start position:0%
application has not only not forged but
they<00:20:04.880><c> reach</c><00:20:05.090><c> the</c><00:20:05.300><c> blockchains</c><00:20:06.200><c> but</c><00:20:07.070><c> if</c><00:20:07.250><c> you</c>

00:20:07.390 --> 00:20:07.400 align:start position:0%
they reach the blockchains but if you
 

00:20:07.400 --> 00:20:10.990 align:start position:0%
they reach the blockchains but if you
use<00:20:07.580><c> multiple</c><00:20:08.260><c> and</c><00:20:09.260><c> place</c><00:20:09.560><c> then</c><00:20:09.800><c> it's</c><00:20:10.580><c> easy</c><00:20:10.790><c> to</c>

00:20:10.990 --> 00:20:11.000 align:start position:0%
use multiple and place then it's easy to
 

00:20:11.000 --> 00:20:13.090 align:start position:0%
use multiple and place then it's easy to
reach<00:20:11.240><c> the</c><00:20:11.420><c> consensus</c><00:20:11.870><c> and</c><00:20:12.080><c> push</c><00:20:12.710><c> it</c><00:20:12.800><c> up</c><00:20:12.920><c> push</c>

00:20:13.090 --> 00:20:13.100 align:start position:0%
reach the consensus and push it up push
 

00:20:13.100 --> 00:20:15.070 align:start position:0%
reach the consensus and push it up push
the<00:20:13.460><c> transactions</c><00:20:14.060><c> this</c><00:20:14.420><c> can</c><00:20:14.600><c> be</c><00:20:14.720><c> used</c><00:20:14.900><c> for</c>

00:20:15.070 --> 00:20:15.080 align:start position:0%
the transactions this can be used for
 

00:20:15.080 --> 00:20:17.100 align:start position:0%
the transactions this can be used for
example<00:20:15.410><c> as</c><00:20:16.100><c> a</c><00:20:16.160><c> building</c><00:20:16.520><c> block</c><00:20:16.670><c> in</c>

00:20:17.100 --> 00:20:17.110 align:start position:0%
example as a building block in
 

00:20:17.110 --> 00:20:20.410 align:start position:0%
example as a building block in
distributed<00:20:18.110><c> exchanges</c><00:20:18.640><c> we</c><00:20:19.640><c> can</c><00:20:19.790><c> also</c><00:20:19.940><c> seal</c>

00:20:20.410 --> 00:20:20.420 align:start position:0%
distributed exchanges we can also seal
 

00:20:20.420 --> 00:20:22.810 align:start position:0%
distributed exchanges we can also seal
keys<00:20:21.200><c> alright</c><00:20:21.980><c> either</c><00:20:22.130><c> locally</c><00:20:22.550><c> or</c><00:20:22.640><c> remotely</c>

00:20:22.810 --> 00:20:22.820 align:start position:0%
keys alright either locally or remotely
 

00:20:22.820 --> 00:20:24.550 align:start position:0%
keys alright either locally or remotely
it's<00:20:23.390><c> just</c><00:20:23.630><c> a</c><00:20:23.720><c> question</c><00:20:24.050><c> of</c><00:20:24.140><c> whether</c><00:20:24.470><c> you</c>

00:20:24.550 --> 00:20:24.560 align:start position:0%
it's just a question of whether you
 

00:20:24.560 --> 00:20:27.640 align:start position:0%
it's just a question of whether you
trust<00:20:24.950><c> the</c><00:20:25.610><c> technology</c><00:20:25.760><c> enough</c><00:20:26.630><c> to</c><00:20:27.350><c> see</c><00:20:27.500><c> look</c>

00:20:27.640 --> 00:20:27.650 align:start position:0%
trust the technology enough to see look
 

00:20:27.650 --> 00:20:29.890 align:start position:0%
trust the technology enough to see look
silly<00:20:27.980><c> or</c><00:20:28.100><c> kiss</c><00:20:28.280><c> remotely</c><00:20:28.700><c> and</c><00:20:29.150><c> this</c><00:20:29.690><c> way</c><00:20:29.840><c> you</c>

00:20:29.890 --> 00:20:29.900 align:start position:0%
silly or kiss remotely and this way you
 

00:20:29.900 --> 00:20:33.430 align:start position:0%
silly or kiss remotely and this way you
can<00:20:30.200><c> for</c><00:20:30.380><c> example</c><00:20:30.820><c> store</c><00:20:31.820><c> your</c><00:20:32.200><c> identity</c><00:20:33.200><c> in</c><00:20:33.350><c> a</c>

00:20:33.430 --> 00:20:33.440 align:start position:0%
can for example store your identity in a
 

00:20:33.440 --> 00:20:35.200 align:start position:0%
can for example store your identity in a
distributed<00:20:33.830><c> manner</c><00:20:34.100><c> both</c><00:20:34.610><c> geographically</c>

00:20:35.200 --> 00:20:35.210 align:start position:0%
distributed manner both geographically
 

00:20:35.210 --> 00:20:39.400 align:start position:0%
distributed manner both geographically
and<00:20:35.330><c> by</c><00:20:36.130><c> making</c><00:20:37.130><c> K</c><00:20:37.520><c> of</c><00:20:37.730><c> n</c><00:20:38.110><c> signatures</c><00:20:39.110><c> required</c>

00:20:39.400 --> 00:20:39.410 align:start position:0%
and by making K of n signatures required
 

00:20:39.410 --> 00:20:42.850 align:start position:0%
and by making K of n signatures required
you<00:20:41.050><c> can</c><00:20:42.050><c> express</c><00:20:42.320><c> the</c><00:20:42.500><c> notion</c><00:20:42.800><c> of</c>

00:20:42.850 --> 00:20:42.860 align:start position:0%
you can express the notion of
 

00:20:42.860 --> 00:20:45.130 align:start position:0%
you can express the notion of
uncertainty<00:20:43.790><c> towards</c><00:20:44.240><c> the</c><00:20:44.390><c> how</c><00:20:44.660><c> do</c><00:20:44.720><c> you</c><00:20:44.900><c> trust</c>

00:20:45.130 --> 00:20:45.140 align:start position:0%
uncertainty towards the how do you trust
 

00:20:45.140 --> 00:20:47.440 align:start position:0%
uncertainty towards the how do you trust
the<00:20:45.260><c> TE</c><00:20:45.440><c> if</c><00:20:46.100><c> you</c><00:20:46.280><c> trust</c><00:20:46.520><c> them</c><00:20:46.730><c> there</c><00:20:47.060><c> is</c><00:20:47.150><c> one</c><00:20:47.330><c> if</c>

00:20:47.440 --> 00:20:47.450 align:start position:0%
the TE if you trust them there is one if
 

00:20:47.450 --> 00:20:48.910 align:start position:0%
the TE if you trust them there is one if
you<00:20:47.540><c> don't</c><00:20:47.660><c> trust</c><00:20:47.900><c> it</c><00:20:48.050><c> that</c><00:20:48.410><c> much</c><00:20:48.620><c> then</c><00:20:48.800><c> there</c>

00:20:48.910 --> 00:20:48.920 align:start position:0%
you don't trust it that much then there
 

00:20:48.920 --> 00:20:51.790 align:start position:0%
you don't trust it that much then there
is<00:20:49.010><c> more</c><00:20:49.220><c> and</c><00:20:49.720><c> in</c><00:20:50.720><c> existing</c><00:20:51.140><c> projects</c><00:20:51.530><c> it</c><00:20:51.650><c> can</c>

00:20:51.790 --> 00:20:51.800 align:start position:0%
is more and in existing projects it can
 

00:20:51.800 --> 00:20:53.470 align:start position:0%
is more and in existing projects it can
be<00:20:51.890><c> used</c><00:20:52.010><c> as</c><00:20:52.160><c> well</c><00:20:52.310><c> so</c><00:20:52.670><c> for</c><00:20:52.850><c> example</c><00:20:53.210><c> we</c><00:20:53.330><c> have</c><00:20:53.450><c> a</c>

00:20:53.470 --> 00:20:53.480 align:start position:0%
be used as well so for example we have a
 

00:20:53.480 --> 00:20:56.380 align:start position:0%
be used as well so for example we have a
manual<00:20:54.170><c> variable</c><00:20:54.650><c> plasma</c><00:20:54.950><c> with</c><00:20:55.610><c> the</c><00:20:56.030><c> central</c>

00:20:56.380 --> 00:20:56.390 align:start position:0%
manual variable plasma with the central
 

00:20:56.390 --> 00:20:58.720 align:start position:0%
manual variable plasma with the central
point<00:20:56.600><c> being</c><00:20:57.020><c> the</c><00:20:57.170><c> plasma</c><00:20:57.500><c> chain</c><00:20:57.680><c> operator</c><00:20:57.980><c> we</c>

00:20:58.720 --> 00:20:58.730 align:start position:0%
point being the plasma chain operator we
 

00:20:58.730 --> 00:21:02.920 align:start position:0%
point being the plasma chain operator we
would<00:20:58.850><c> like</c><00:20:59.000><c> it</c><00:20:59.180><c> to</c><00:20:59.210><c> be</c><00:20:59.650><c> reliable</c><00:21:00.650><c> and</c><00:21:01.040><c> not</c><00:21:01.930><c> to</c>

00:21:02.920 --> 00:21:02.930 align:start position:0%
would like it to be reliable and not to
 

00:21:02.930 --> 00:21:05.290 align:start position:0%
would like it to be reliable and not to
cheat<00:21:03.110><c> so</c><00:21:03.650><c> let's</c><00:21:04.250><c> just</c><00:21:04.460><c> enclose</c><00:21:04.700><c> into</c><00:21:05.000><c> n</c><00:21:05.120><c> place</c>

00:21:05.290 --> 00:21:05.300 align:start position:0%
cheat so let's just enclose into n place
 

00:21:05.300 --> 00:21:09.010 align:start position:0%
cheat so let's just enclose into n place
and<00:21:06.290><c> at</c><00:21:06.500><c> the</c><00:21:06.530><c> same</c><00:21:06.770><c> time</c><00:21:07.690><c> we</c><00:21:08.690><c> would</c><00:21:08.810><c> like</c><00:21:08.990><c> to</c>

00:21:09.010 --> 00:21:09.020 align:start position:0%
and at the same time we would like to
 

00:21:09.020 --> 00:21:12.250 align:start position:0%
and at the same time we would like to
make<00:21:09.380><c> it</c><00:21:10.300><c> reliable</c><00:21:11.300><c> in</c><00:21:11.450><c> terms</c><00:21:11.660><c> of</c><00:21:11.840><c> block</c>

00:21:12.250 --> 00:21:12.260 align:start position:0%
make it reliable in terms of block
 

00:21:12.260 --> 00:21:14.680 align:start position:0%
make it reliable in terms of block
withholding<00:21:12.800><c> which</c><00:21:13.340><c> means</c><00:21:13.580><c> that</c><00:21:13.730><c> we</c><00:21:13.880><c> can</c><00:21:14.060><c> be</c>

00:21:14.680 --> 00:21:14.690 align:start position:0%
withholding which means that we can be
 

00:21:14.690 --> 00:21:17.110 align:start position:0%
withholding which means that we can be
centralize<00:21:15.110><c> it</c><00:21:15.260><c> and</c><00:21:15.490><c> make</c><00:21:16.490><c> sure</c><00:21:16.520><c> that</c><00:21:16.730><c> it's</c>

00:21:17.110 --> 00:21:17.120 align:start position:0%
centralize it and make sure that it's
 

00:21:17.120 --> 00:21:20.500 align:start position:0%
centralize it and make sure that it's
harder<00:21:17.720><c> to</c><00:21:18.280><c> withhold</c><00:21:19.280><c> blocks</c><00:21:19.550><c> by</c><00:21:20.090><c> an</c><00:21:20.180><c> operator</c>

00:21:20.500 --> 00:21:20.510 align:start position:0%
harder to withhold blocks by an operator
 

00:21:20.510 --> 00:21:24.040 align:start position:0%
harder to withhold blocks by an operator
another<00:21:21.290><c> one</c><00:21:21.440><c> is</c><00:21:21.590><c> hard</c><00:21:22.370><c> hard</c><00:21:23.330><c> is</c><00:21:23.510><c> a</c><00:21:23.540><c> platform</c>

00:21:24.040 --> 00:21:24.050 align:start position:0%
another one is hard hard is a platform
 

00:21:24.050 --> 00:21:29.460 align:start position:0%
another one is hard hard is a platform
for<00:21:25.630><c> governing</c><00:21:27.370><c> assets</c><00:21:28.370><c> in</c><00:21:28.880><c> games</c><00:21:29.150><c> and</c>

00:21:29.460 --> 00:21:29.470 align:start position:0%
for governing assets in games and
 

00:21:29.470 --> 00:21:33.130 align:start position:0%
for governing assets in games and
binding<00:21:30.470><c> it</c><00:21:30.790><c> to</c><00:21:31.790><c> players</c><00:21:32.360><c> so</c><00:21:32.780><c> that</c><00:21:32.810><c> players</c>

00:21:33.130 --> 00:21:33.140 align:start position:0%
binding it to players so that players
 

00:21:33.140 --> 00:21:37.120 align:start position:0%
binding it to players so that players
have<00:21:33.410><c> the</c><00:21:33.500><c> true</c><00:21:33.680><c> energy</c><00:21:33.830><c> both</c><00:21:34.810><c> items</c><00:21:35.810><c> and</c><00:21:36.130><c> this</c>

00:21:37.120 --> 00:21:37.130 align:start position:0%
have the true energy both items and this
 

00:21:37.130 --> 00:21:41.860 align:start position:0%
have the true energy both items and this
requires<00:21:38.020><c> keeping</c><00:21:39.020><c> the</c><00:21:39.280><c> notion</c><00:21:40.280><c> of</c><00:21:40.370><c> state</c><00:21:41.060><c> on</c>

00:21:41.860 --> 00:21:41.870 align:start position:0%
requires keeping the notion of state on
 

00:21:41.870 --> 00:21:43.330 align:start position:0%
requires keeping the notion of state on
the<00:21:42.020><c> server</c><00:21:42.230><c> side</c><00:21:42.500><c> so</c><00:21:42.890><c> games</c><00:21:43.100><c> against</c>

00:21:43.330 --> 00:21:43.340 align:start position:0%
the server side so games against
 

00:21:43.340 --> 00:21:45.610 align:start position:0%
the server side so games against
everything<00:21:43.790><c> the</c><00:21:43.880><c> internet</c><00:21:44.210><c> player</c><00:21:45.200><c> plays</c><00:21:45.440><c> the</c>

00:21:45.610 --> 00:21:45.620 align:start position:0%
everything the internet player plays the
 

00:21:45.620 --> 00:21:48.520 align:start position:0%
everything the internet player plays the
game<00:21:45.770><c> and</c><00:21:46.270><c> the</c><00:21:47.270><c> game</c><00:21:47.630><c> server</c><00:21:47.990><c> keeps</c><00:21:48.200><c> track</c><00:21:48.500><c> of</c>

00:21:48.520 --> 00:21:48.530 align:start position:0%
game and the game server keeps track of
 

00:21:48.530 --> 00:21:51.040 align:start position:0%
game and the game server keeps track of
state<00:21:48.890><c> and</c><00:21:49.160><c> make</c><00:21:50.060><c> sure</c><00:21:50.270><c> that</c><00:21:50.450><c> player</c><00:21:50.810><c> doesn't</c>

00:21:51.040 --> 00:21:51.430 align:start position:0%
state and make sure that player doesn't
 

00:21:51.430 --> 00:21:51.440 align:start position:0%
 
 

00:21:51.440 --> 00:21:53.350 align:start position:0%
 
well<00:21:51.620><c> in</c><00:21:51.770><c> fact</c><00:21:51.920><c> this</c><00:21:52.100><c> most</c><00:21:52.730><c> of</c><00:21:52.880><c> the</c><00:21:52.970><c> logic</c><00:21:53.210><c> can</c>

00:21:53.350 --> 00:21:53.360 align:start position:0%
well in fact this most of the logic can
 

00:21:53.360 --> 00:21:55.540 align:start position:0%
well in fact this most of the logic can
be<00:21:53.480><c> run</c><00:21:53.600><c> locally</c><00:21:53.720><c> in</c><00:21:54.260><c> the</c><00:21:54.350><c> enclaves</c><00:21:54.620><c> and</c><00:21:54.770><c> we</c>

00:21:55.540 --> 00:21:55.550 align:start position:0%
be run locally in the enclaves and we
 

00:21:55.550 --> 00:21:56.800 align:start position:0%
be run locally in the enclaves and we
only<00:21:55.670><c> care</c><00:21:55.910><c> about</c><00:21:55.940><c> the</c><00:21:56.150><c> integrity</c><00:21:56.330><c> not</c><00:21:56.690><c> to</c>

00:21:56.800 --> 00:21:56.810 align:start position:0%
only care about the integrity not to
 

00:21:56.810 --> 00:21:58.990 align:start position:0%
only care about the integrity not to
confirm<00:21:57.050><c> confidentiality</c><00:21:57.890><c> under</c><00:21:58.280><c> step</c><00:21:58.490><c> is</c><00:21:58.670><c> we</c>

00:21:58.990 --> 00:21:59.000 align:start position:0%
confirm confidentiality under step is we
 

00:21:59.000 --> 00:22:00.910 align:start position:0%
confirm confidentiality under step is we
centralizing<00:21:59.570><c> the</c><00:21:59.600><c> whole</c><00:21:59.840><c> system</c><00:22:00.170><c> and</c><00:22:00.320><c> making</c>

00:22:00.910 --> 00:22:00.920 align:start position:0%
centralizing the whole system and making
 

00:22:00.920 --> 00:22:02.440 align:start position:0%
centralizing the whole system and making
this<00:22:00.980><c> local</c><00:22:01.280><c> game</c><00:22:01.400><c> server</c><00:22:01.670><c> connect</c><00:22:02.360><c> with</c>

00:22:02.440 --> 00:22:02.450 align:start position:0%
this local game server connect with
 

00:22:02.450 --> 00:22:05.110 align:start position:0%
this local game server connect with
others<00:22:02.720><c> and</c><00:22:02.930><c> build</c><00:22:03.320><c> a</c><00:22:03.440><c> bigger</c><00:22:04.100><c> server</c><00:22:04.340><c> and</c><00:22:04.940><c> the</c>

00:22:05.110 --> 00:22:05.120 align:start position:0%
others and build a bigger server and the
 

00:22:05.120 --> 00:22:08.200 align:start position:0%
others and build a bigger server and the
last<00:22:05.270><c> one</c><00:22:05.510><c> is</c><00:22:05.990><c> data</c><00:22:06.260><c> streaming</c><00:22:06.620><c> so</c><00:22:07.060><c> we</c><00:22:08.060><c> have</c>

00:22:08.200 --> 00:22:08.210 align:start position:0%
last one is data streaming so we have
 

00:22:08.210 --> 00:22:10.060 align:start position:0%
last one is data streaming so we have
this<00:22:08.330><c> intermediate</c><00:22:08.690><c> layer</c><00:22:09.080><c> of</c><00:22:09.290><c> SGX</c><00:22:09.740><c> enabled</c>

00:22:10.060 --> 00:22:10.070 align:start position:0%
this intermediate layer of SGX enabled
 

00:22:10.070 --> 00:22:12.160 align:start position:0%
this intermediate layer of SGX enabled
machines<00:22:10.370><c> and</c><00:22:11.090><c> content</c><00:22:11.570><c> creator</c><00:22:11.780><c> creator</c>

00:22:12.160 --> 00:22:12.170 align:start position:0%
machines and content creator creator
 

00:22:12.170 --> 00:22:13.000 align:start position:0%
machines and content creator creator
uploads<00:22:12.740><c> the</c>

00:22:13.000 --> 00:22:13.010 align:start position:0%
uploads the
 

00:22:13.010 --> 00:22:17.670 align:start position:0%
uploads the
content<00:22:13.310><c> and</c><00:22:13.810><c> by</c><00:22:14.810><c> virtue</c><00:22:15.530><c> of</c><00:22:15.790><c> what</c><00:22:16.850><c> svx</c><00:22:17.240><c> offers</c>

00:22:17.670 --> 00:22:17.680 align:start position:0%
content and by virtue of what svx offers
 

00:22:17.680 --> 00:22:19.930 align:start position:0%
content and by virtue of what svx offers
only<00:22:18.680><c> outdoors</c><00:22:19.280><c> clients</c><00:22:19.610><c> can</c><00:22:19.730><c> download</c>

00:22:19.930 --> 00:22:19.940 align:start position:0%
only outdoors clients can download
 

00:22:19.940 --> 00:22:24.760 align:start position:0%
only outdoors clients can download
content<00:22:21.940><c> the</c><00:22:22.940><c> video</c><00:22:23.630><c> streaming</c><00:22:23.900><c> is</c><00:22:24.140><c> the</c><00:22:24.560><c> most</c>

00:22:24.760 --> 00:22:24.770 align:start position:0%
content the video streaming is the most
 

00:22:24.770 --> 00:22:26.020 align:start position:0%
content the video streaming is the most
obvious<00:22:25.070><c> example</c><00:22:25.430><c> here</c><00:22:25.550><c> but</c><00:22:25.700><c> we</c><00:22:25.820><c> can</c><00:22:25.940><c> also</c>

00:22:26.020 --> 00:22:26.030 align:start position:0%
obvious example here but we can also
 

00:22:26.030 --> 00:22:29.770 align:start position:0%
obvious example here but we can also
envision<00:22:27.370><c> processing</c><00:22:28.370><c> the</c><00:22:28.490><c> data</c><00:22:28.780><c> aggregated</c>

00:22:29.770 --> 00:22:29.780 align:start position:0%
envision processing the data aggregated
 

00:22:29.780 --> 00:22:31.960 align:start position:0%
envision processing the data aggregated
and<00:22:30.020><c> data</c><00:22:30.170><c> and</c><00:22:30.560><c> hosting</c><00:22:31.460><c> some</c><00:22:31.580><c> custom</c><00:22:31.850><c> logic</c>

00:22:31.960 --> 00:22:31.970 align:start position:0%
and data and hosting some custom logic
 

00:22:31.970 --> 00:22:37.380 align:start position:0%
and data and hosting some custom logic
for<00:22:32.360><c> this</c><00:22:33.100><c> data</c><00:22:34.150><c> management</c><00:22:35.150><c> so</c><00:22:36.010><c> users</c><00:22:37.010><c> can</c>

00:22:37.380 --> 00:22:37.390 align:start position:0%
for this data management so users can
 

00:22:37.390 --> 00:22:39.490 align:start position:0%
for this data management so users can
benefit<00:22:38.390><c> from</c><00:22:38.450><c> it</c><00:22:38.630><c> not</c><00:22:38.780><c> only</c><00:22:38.900><c> but</c><00:22:39.140><c> down</c>

00:22:39.490 --> 00:22:39.500 align:start position:0%
benefit from it not only but down
 

00:22:39.500 --> 00:22:42.390 align:start position:0%
benefit from it not only but down
long-delayed<00:22:39.860><c> up</c><00:22:40.040><c> and</c><00:22:40.190><c> getting</c><00:22:40.460><c> some</c><00:22:40.700><c> results</c>

00:22:42.390 --> 00:22:42.400 align:start position:0%
long-delayed up and getting some results
 

00:22:42.400 --> 00:22:44.230 align:start position:0%
long-delayed up and getting some results
resulting<00:22:43.400><c> from</c><00:22:43.520><c> the</c><00:22:43.640><c> data</c><00:22:43.790><c> and</c><00:22:43.940><c> this</c><00:22:44.030><c> may</c><00:22:44.210><c> be</c>

00:22:44.230 --> 00:22:44.240 align:start position:0%
resulting from the data and this may be
 

00:22:44.240 --> 00:22:47.020 align:start position:0%
resulting from the data and this may be
a<00:22:44.360><c> building</c><00:22:44.660><c> block</c><00:22:44.870><c> for</c><00:22:45.130><c> wider</c><00:22:46.130><c> a</c><00:22:46.490><c> bigger</c>

00:22:47.020 --> 00:22:47.030 align:start position:0%
a building block for wider a bigger
 

00:22:47.030 --> 00:22:50.350 align:start position:0%
a building block for wider a bigger
network<00:22:47.480><c> of</c><00:22:47.690><c> data</c><00:22:48.290><c> processing</c><00:22:48.800><c> okay</c><00:22:49.580><c> so</c><00:22:50.120><c> I</c>

00:22:50.350 --> 00:22:50.360 align:start position:0%
network of data processing okay so I
 

00:22:50.360 --> 00:22:52.360 align:start position:0%
network of data processing okay so I
know<00:22:50.600><c> it</c><00:22:50.810><c> was</c><00:22:50.930><c> dense</c><00:22:51.110><c> I</c><00:22:51.260><c> know</c><00:22:51.380><c> quite</c><00:22:52.220><c> a</c><00:22:52.280><c> lot</c>

00:22:52.360 --> 00:22:52.370 align:start position:0%
know it was dense I know quite a lot
 

00:22:52.370 --> 00:22:53.710 align:start position:0%
know it was dense I know quite a lot
information<00:22:52.520><c> I</c><00:22:53.000><c> hope</c><00:22:53.180><c> that</c><00:22:53.390><c> you</c><00:22:53.510><c> got</c><00:22:53.660><c> a</c>

00:22:53.710 --> 00:22:53.720 align:start position:0%
information I hope that you got a
 

00:22:53.720 --> 00:22:55.390 align:start position:0%
information I hope that you got a
glimpse<00:22:54.020><c> of</c><00:22:54.140><c> why</c><00:22:54.590><c> the</c><00:22:54.650><c> technology</c><00:22:55.010><c> stack</c>

00:22:55.390 --> 00:22:55.400 align:start position:0%
glimpse of why the technology stack
 

00:22:55.400 --> 00:22:56.860 align:start position:0%
glimpse of why the technology stack
might<00:22:55.580><c> be</c><00:22:55.670><c> interested</c><00:22:56.060><c> it</c><00:22:56.600><c> might</c><00:22:56.810><c> be</c>

00:22:56.860 --> 00:22:56.870 align:start position:0%
might be interested it might be
 

00:22:56.870 --> 00:22:58.000 align:start position:0%
might be interested it might be
interesting<00:22:57.050><c> to</c><00:22:57.260><c> you</c><00:22:57.380><c> does</c><00:22:57.860><c> definitely</c>

00:22:58.000 --> 00:22:58.010 align:start position:0%
interesting to you does definitely
 

00:22:58.010 --> 00:22:59.650 align:start position:0%
interesting to you does definitely
listen<00:22:58.490><c> to</c><00:22:58.610><c> us</c><00:22:58.700><c> we</c><00:22:58.850><c> are</c><00:22:58.880><c> going</c><00:22:58.970><c> to</c><00:22:59.300><c> work</c><00:22:59.420><c> on</c><00:22:59.570><c> it</c>

00:22:59.650 --> 00:22:59.660 align:start position:0%
listen to us we are going to work on it
 

00:22:59.660 --> 00:23:04.100 align:start position:0%
listen to us we are going to work on it
well<00:23:00.650><c> and</c><00:23:01.010><c> thank</c><00:23:01.430><c> you</c>

00:23:04.100 --> 00:23:04.110 align:start position:0%
 
 

00:23:04.110 --> 00:23:12.120 align:start position:0%
 
[Applause]

00:23:12.120 --> 00:23:12.130 align:start position:0%
 
 

00:23:12.130 --> 00:23:14.190 align:start position:0%
 
you