WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:17.250 align:start position:0% [Music] 00:00:17.250 --> 00:00:17.260 align:start position:0% [Music] 00:00:17.260 --> 00:00:20.800 align:start position:0% [Music] so<00:00:18.260> during<00:00:18.800> this<00:00:18.920> presentation<00:00:19.250> I'll<00:00:20.150> speak 00:00:20.800 --> 00:00:20.810 align:start position:0% so during this presentation I'll speak 00:00:20.810 --> 00:00:23.950 align:start position:0% so during this presentation I'll speak about<00:00:21.110> the<00:00:22.029> Acolytes<00:00:23.029> Oracle<00:00:23.360> solution<00:00:23.779> and 00:00:23.950 --> 00:00:23.960 align:start position:0% about the Acolytes Oracle solution and 00:00:23.960 --> 00:00:25.900 align:start position:0% about the Acolytes Oracle solution and some<00:00:24.800> of<00:00:24.950> the<00:00:25.070> things<00:00:25.279> that<00:00:25.490> we<00:00:25.640> have<00:00:25.730> in<00:00:25.820> the 00:00:25.900 --> 00:00:25.910 align:start position:0% some of the things that we have in the 00:00:25.910 --> 00:00:28.920 align:start position:0% some of the things that we have in the workings<00:00:26.770> so 00:00:28.920 --> 00:00:28.930 align:start position:0% workings so 00:00:28.930 --> 00:00:31.240 align:start position:0% workings so given<00:00:29.930> the<00:00:30.110> circumstances<00:00:30.800> there<00:00:30.980> are<00:00:31.040> many 00:00:31.240 --> 00:00:31.250 align:start position:0% given the circumstances there are many 00:00:31.250 --> 00:00:33.850 align:start position:0% given the circumstances there are many smart<00:00:32.090> contracts<00:00:32.660> that<00:00:32.930> need<00:00:33.200> to<00:00:33.680> get 00:00:33.850 --> 00:00:33.860 align:start position:0% smart contracts that need to get 00:00:33.860 --> 00:00:36.280 align:start position:0% smart contracts that need to get external<00:00:34.220> data<00:00:34.400> think<00:00:35.120> about<00:00:35.360> web<00:00:35.570> api's<00:00:36.020> or 00:00:36.280 --> 00:00:36.290 align:start position:0% external data think about web api's or 00:00:36.290 --> 00:00:38.940 align:start position:0% external data think about web api's or from<00:00:36.860> any<00:00:37.100> data<00:00:37.790> source 00:00:38.940 --> 00:00:38.950 align:start position:0% from any data source 00:00:38.950 --> 00:00:41.590 align:start position:0% from any data source still<00:00:39.950> decentralized<00:00:40.850> networks<00:00:41.300> like 00:00:41.590 --> 00:00:41.600 align:start position:0% still decentralized networks like 00:00:41.600 --> 00:00:43.840 align:start position:0% still decentralized networks like aetherium<00:00:42.140> i've<00:00:42.320> and<00:00:42.680> the<00:00:42.980> inherent 00:00:43.840 --> 00:00:43.850 align:start position:0% aetherium i've and the inherent 00:00:43.850 --> 00:00:46.900 align:start position:0% aetherium i've and the inherent limitation<00:00:44.600> in<00:00:45.020> not<00:00:45.470> being<00:00:45.710> able<00:00:45.980> to<00:00:46.280> reach 00:00:46.900 --> 00:00:46.910 align:start position:0% limitation in not being able to reach 00:00:46.910 --> 00:00:49.780 align:start position:0% limitation in not being able to reach out<00:00:47.030> the<00:00:47.210> internet<00:00:47.630> so<00:00:48.230> the<00:00:49.130> smart<00:00:49.400> contrasts 00:00:49.780 --> 00:00:49.790 align:start position:0% out the internet so the smart contrasts 00:00:49.790 --> 00:00:51.850 align:start position:0% out the internet so the smart contrasts live<00:00:49.970> like<00:00:50.210> in<00:00:50.420> a<00:00:50.510> walled<00:00:50.690> garden<00:00:50.720> and<00:00:51.320> they 00:00:51.850 --> 00:00:51.860 align:start position:0% live like in a walled garden and they 00:00:51.860 --> 00:00:53.800 align:start position:0% live like in a walled garden and they cannot<00:00:52.130> simply<00:00:52.370> open<00:00:52.820> a<00:00:52.910> socket<00:00:53.090> and<00:00:53.360> fetch 00:00:53.800 --> 00:00:53.810 align:start position:0% cannot simply open a socket and fetch 00:00:53.810 --> 00:00:56.890 align:start position:0% cannot simply open a socket and fetch external<00:00:54.320> data<00:00:54.530> so<00:00:55.400> this<00:00:55.760> is<00:00:56.000> why<00:00:56.240> there<00:00:56.840> are 00:00:56.890 --> 00:00:56.900 align:start position:0% external data so this is why there are 00:00:56.900 --> 00:00:59.260 align:start position:0% external data so this is why there are many<00:00:57.110> different<00:00:57.470> solutions<00:00:58.010> called<00:00:58.880> as 00:00:59.260 --> 00:00:59.270 align:start position:0% many different solutions called as 00:00:59.270 --> 00:01:03.160 align:start position:0% many different solutions called as Oracle's<00:01:00.340> to<00:01:01.340> pull<00:01:01.610> or<00:01:01.850> push<00:01:01.880> data<00:01:02.390> external 00:01:03.160 --> 00:01:03.170 align:start position:0% Oracle's to pull or push data external 00:01:03.170 --> 00:01:05.710 align:start position:0% Oracle's to pull or push data external data<00:01:03.350> to<00:01:03.530> the<00:01:03.620> blockchain<00:01:03.850> so<00:01:04.850> we'll<00:01:05.420> focus 00:01:05.710 --> 00:01:05.720 align:start position:0% data to the blockchain so we'll focus 00:01:05.720 --> 00:01:08.800 align:start position:0% data to the blockchain so we'll focus during<00:01:06.200> this<00:01:06.290> presentation<00:01:06.590> on<00:01:07.220> the<00:01:08.000> first 00:01:08.800 --> 00:01:08.810 align:start position:0% during this presentation on the first 00:01:08.810 --> 00:01:10.450 align:start position:0% during this presentation on the first approach<00:01:09.140> listed<00:01:09.590> in<00:01:09.740> there<00:01:09.920> in<00:01:10.040> this<00:01:10.220> slide 00:01:10.450 --> 00:01:10.460 align:start position:0% approach listed in there in this slide 00:01:10.460 --> 00:01:12.640 align:start position:0% approach listed in there in this slide so<00:01:11.210> this<00:01:11.360> is<00:01:11.509> the<00:01:11.600> one<00:01:11.750> used<00:01:11.930> by<00:01:12.049> Oracle<00:01:12.560> eyes 00:01:12.640 --> 00:01:12.650 align:start position:0% so this is the one used by Oracle eyes 00:01:12.650 --> 00:01:15.700 align:start position:0% so this is the one used by Oracle eyes and<00:01:12.979> as<00:01:13.220> we<00:01:13.369> speak<00:01:13.640> this<00:01:14.030> is<00:01:14.299> the<00:01:14.600> most<00:01:15.320> widely 00:01:15.700 --> 00:01:15.710 align:start position:0% and as we speak this is the most widely 00:01:15.710 --> 00:01:19.060 align:start position:0% and as we speak this is the most widely used<00:01:15.740> on<00:01:16.130> the<00:01:16.670> public<00:01:17.090> blockchain<00:01:17.750> so<00:01:18.560> one<00:01:19.040> of 00:01:19.060 --> 00:01:19.070 align:start position:0% used on the public blockchain so one of 00:01:19.070 --> 00:01:21.280 align:start position:0% used on the public blockchain so one of the<00:01:19.400> pros<00:01:19.640> of<00:01:19.880> this<00:01:20.060> approach<00:01:20.420> is<00:01:20.810> that<00:01:20.900> it's 00:01:21.280 --> 00:01:21.290 align:start position:0% the pros of this approach is that it's 00:01:21.290 --> 00:01:23.590 align:start position:0% the pros of this approach is that it's fully<00:01:21.830> transparent<00:01:22.130> in<00:01:22.760> the<00:01:22.970> sense<00:01:23.180> that<00:01:23.270> both 00:01:23.590 --> 00:01:23.600 align:start position:0% fully transparent in the sense that both 00:01:23.600 --> 00:01:25.510 align:start position:0% fully transparent in the sense that both the<00:01:23.780> query<00:01:24.050> and<00:01:24.290> the<00:01:24.350> results<00:01:25.310> are 00:01:25.510 --> 00:01:25.520 align:start position:0% the query and the results are 00:01:25.520 --> 00:01:28.270 align:start position:0% the query and the results are permanently<00:01:26.210> stored<00:01:26.300> on<00:01:26.600> blockchain<00:01:27.280> another 00:01:28.270 --> 00:01:28.280 align:start position:0% permanently stored on blockchain another 00:01:28.280 --> 00:01:31.180 align:start position:0% permanently stored on blockchain another advantage<00:01:28.670> is<00:01:29.120> that<00:01:29.210> we<00:01:29.600> can<00:01:29.630> use<00:01:30.140> any<00:01:30.860> data 00:01:31.180 --> 00:01:31.190 align:start position:0% advantage is that we can use any data 00:01:31.190 --> 00:01:33.460 align:start position:0% advantage is that we can use any data source<00:01:31.430> available<00:01:31.970> on<00:01:32.060> the<00:01:32.180> Internet<00:01:32.600> so<00:01:33.260> any 00:01:33.460 --> 00:01:33.470 align:start position:0% source available on the Internet so any 00:01:33.470 --> 00:01:36.219 align:start position:0% source available on the Internet so any Web<00:01:33.770> API<00:01:34.190> potentially<00:01:34.940> since<00:01:35.630> there<00:01:35.840> is<00:01:35.960> no 00:01:36.219 --> 00:01:36.229 align:start position:0% Web API potentially since there is no 00:01:36.229 --> 00:01:37.690 align:start position:0% Web API potentially since there is no need<00:01:36.409> for<00:01:36.440> them<00:01:36.800> to<00:01:36.830> adapt<00:01:37.190> to<00:01:37.220> the<00:01:37.490> blockchain 00:01:37.690 --> 00:01:37.700 align:start position:0% need for them to adapt to the blockchain 00:01:37.700 --> 00:01:39.850 align:start position:0% need for them to adapt to the blockchain they<00:01:38.510> have<00:01:38.600> no<00:01:38.840> knowledge<00:01:38.990> of<00:01:39.290> the<00:01:39.440> blocking 00:01:39.850 --> 00:01:39.860 align:start position:0% they have no knowledge of the blocking 00:01:39.860 --> 00:01:42.000 align:start position:0% they have no knowledge of the blocking and<00:01:40.070> it<00:01:40.280> doesn't<00:01:40.550> have<00:01:40.729> to<00:01:40.760> and 00:01:42.000 --> 00:01:42.010 align:start position:0% and it doesn't have to and 00:01:42.010 --> 00:01:44.440 align:start position:0% and it doesn't have to and another<00:01:43.010> advantage<00:01:43.220> is<00:01:43.700> that<00:01:43.790> there<00:01:44.120> is<00:01:44.270> no 00:01:44.440 --> 00:01:44.450 align:start position:0% another advantage is that there is no 00:01:44.450 --> 00:01:46.630 align:start position:0% another advantage is that there is no trust<00:01:44.720> line<00:01:44.990> open<00:01:45.380> with<00:01:45.560> the<00:01:45.710> Oracle<00:01:46.100> so<00:01:46.520> the 00:01:46.630 --> 00:01:46.640 align:start position:0% trust line open with the Oracle so the 00:01:46.640 --> 00:01:49.030 align:start position:0% trust line open with the Oracle so the Oracle<00:01:47.060> cannot<00:01:48.049> simply<00:01:48.470> tamper<00:01:48.740> with<00:01:48.920> the 00:01:49.030 --> 00:01:49.040 align:start position:0% Oracle cannot simply tamper with the 00:01:49.040 --> 00:01:52.600 align:start position:0% Oracle cannot simply tamper with the data<00:01:49.250> as<00:01:49.659> with<00:01:50.690> attestation<00:01:51.200> we<00:01:51.680> can<00:01:51.920> move<00:01:52.220> the 00:01:52.600 --> 00:01:52.610 align:start position:0% data as with attestation we can move the 00:01:52.610 --> 00:01:54.850 align:start position:0% data as with attestation we can move the trust<00:01:52.880> away<00:01:53.299> from<00:01:53.540> the<00:01:53.659> Oracle<00:01:54.080> to<00:01:54.530> Atta 00:01:54.850 --> 00:01:54.860 align:start position:0% trust away from the Oracle to Atta 00:01:54.860 --> 00:01:57.130 align:start position:0% trust away from the Oracle to Atta status<00:01:55.400> we<00:01:55.760> seen<00:01:56.000> a<00:01:56.060> bit<00:01:56.240> who<00:01:56.450> this<00:01:56.570> artist<00:01:56.990> it 00:01:57.130 --> 00:01:57.140 align:start position:0% status we seen a bit who this artist it 00:01:57.140 --> 00:01:58.050 align:start position:0% status we seen a bit who this artist it was<00:01:57.170> our 00:01:58.050 --> 00:01:58.060 align:start position:0% was our 00:01:58.060 --> 00:02:01.750 align:start position:0% was our so<00:01:59.060> this<00:02:00.020> is<00:02:00.200> the<00:02:00.320> logic<00:02:00.440> flow<00:02:00.799> what<00:02:01.400> you<00:02:01.580> have 00:02:01.750 --> 00:02:01.760 align:start position:0% so this is the logic flow what you have 00:02:01.760 --> 00:02:04.990 align:start position:0% so this is the logic flow what you have is<00:02:02.440> a<00:02:03.440> smart<00:02:03.830> counter<00:02:04.010> sitting<00:02:04.460> on<00:02:04.610> a<00:02:04.640> theorem 00:02:04.990 --> 00:02:05.000 align:start position:0% is a smart counter sitting on a theorem 00:02:05.000 --> 00:02:07.330 align:start position:0% is a smart counter sitting on a theorem that<00:02:05.630> can<00:02:05.930> reach<00:02:06.380> out<00:02:06.560> the<00:02:06.710> Internet<00:02:07.130> via 00:02:07.330 --> 00:02:07.340 align:start position:0% that can reach out the Internet via 00:02:07.340 --> 00:02:10.479 align:start position:0% that can reach out the Internet via Oracle<00:02:08.060> eyes<00:02:08.149> the<00:02:08.929> way<00:02:09.049> they<00:02:09.200> do<00:02:09.379> so<00:02:09.409> is<00:02:09.890> simply 00:02:10.479 --> 00:02:10.489 align:start position:0% Oracle eyes the way they do so is simply 00:02:10.489 --> 00:02:11.820 align:start position:0% Oracle eyes the way they do so is simply by<00:02:10.610> using<00:02:10.670> the 00:02:11.820 --> 00:02:11.830 align:start position:0% by using the 00:02:11.830 --> 00:02:15.490 align:start position:0% by using the Oracle<00:02:12.830> AERS<00:02:13.129> query<00:02:13.840> function<00:02:14.840> so<00:02:15.349> this 00:02:15.490 --> 00:02:15.500 align:start position:0% Oracle AERS query function so this 00:02:15.500 --> 00:02:18.610 align:start position:0% Oracle AERS query function so this function<00:02:15.920> essentially<00:02:16.340> is<00:02:16.730> an<00:02:17.209> event<00:02:17.420> so<00:02:17.810> our 00:02:18.610 --> 00:02:18.620 align:start position:0% function essentially is an event so our 00:02:18.620 --> 00:02:20.199 align:start position:0% function essentially is an event so our of<00:02:18.890> train<00:02:19.099> engine<00:02:19.519> can<00:02:19.730> listen<00:02:20.000> to<00:02:20.120> this 00:02:20.199 --> 00:02:20.209 align:start position:0% of train engine can listen to this 00:02:20.209 --> 00:02:22.030 align:start position:0% of train engine can listen to this events<00:02:20.659> and<00:02:20.840> fulfill<00:02:21.290> the<00:02:21.409> request<00:02:21.680> so 00:02:22.030 --> 00:02:22.040 align:start position:0% events and fulfill the request so 00:02:22.040 --> 00:02:24.309 align:start position:0% events and fulfill the request so essentially<00:02:22.400> we<00:02:22.580> are<00:02:22.610> the<00:02:22.790> one<00:02:22.970> opening<00:02:23.540> the 00:02:24.309 --> 00:02:24.319 align:start position:0% essentially we are the one opening the 00:02:24.319 --> 00:02:26.470 align:start position:0% essentially we are the one opening the connection<00:02:24.860> with<00:02:25.160> the<00:02:25.400> remote<00:02:25.880> web<00:02:26.090> service 00:02:26.470 --> 00:02:26.480 align:start position:0% connection with the remote web service 00:02:26.480 --> 00:02:27.910 align:start position:0% connection with the remote web service we<00:02:26.990> get<00:02:27.170> a<00:02:27.230> result 00:02:27.910 --> 00:02:27.920 align:start position:0% we get a result 00:02:27.920 --> 00:02:29.740 align:start position:0% we get a result along<00:02:28.370> with<00:02:28.459> what<00:02:28.760> we<00:02:28.940> call<00:02:29.150> authenticity 00:02:29.740 --> 00:02:29.750 align:start position:0% along with what we call authenticity 00:02:29.750 --> 00:02:32.530 align:start position:0% along with what we call authenticity proof<00:02:30.290> and<00:02:30.530> we<00:02:31.010> send<00:02:31.310> both<00:02:31.640> of<00:02:31.700> them<00:02:31.849> back<00:02:32.420> to 00:02:32.530 --> 00:02:32.540 align:start position:0% proof and we send both of them back to 00:02:32.540 --> 00:02:34.479 align:start position:0% proof and we send both of them back to the<00:02:32.659> contract<00:02:33.110> so<00:02:33.590> this<00:02:33.769> is<00:02:33.920> a<00:02:33.950> synchronous 00:02:34.479 --> 00:02:34.489 align:start position:0% the contract so this is a synchronous 00:02:34.489 --> 00:02:37.440 align:start position:0% the contract so this is a synchronous and 00:02:37.440 --> 00:02:37.450 align:start position:0% 00:02:37.450 --> 00:02:39.880 align:start position:0% there<00:02:38.450> are<00:02:38.540> different<00:02:38.900> approaches<00:02:39.349> actually 00:02:39.880 --> 00:02:39.890 align:start position:0% there are different approaches actually 00:02:39.890 --> 00:02:43.270 align:start position:0% there are different approaches actually to<00:02:40.480> implement<00:02:41.480> these<00:02:41.810> authenticity<00:02:42.440> proofs 00:02:43.270 --> 00:02:43.280 align:start position:0% to implement these authenticity proofs 00:02:43.280 --> 00:02:44.890 align:start position:0% to implement these authenticity proofs so<00:02:43.580> these<00:02:43.760> authenticity<00:02:44.150> proofs<00:02:44.720> are 00:02:44.890 --> 00:02:44.900 align:start position:0% so these authenticity proofs are 00:02:44.900 --> 00:02:46.830 align:start position:0% so these authenticity proofs are cryptographic 00:02:46.830 --> 00:02:46.840 align:start position:0% cryptographic 00:02:46.840 --> 00:02:50.080 align:start position:0% cryptographic signatures<00:02:47.840> that<00:02:48.500> can<00:02:48.860> enable<00:02:49.310> the<00:02:49.819> smart 00:02:50.080 --> 00:02:50.090 align:start position:0% signatures that can enable the smart 00:02:50.090 --> 00:02:52.630 align:start position:0% signatures that can enable the smart contracts<00:02:50.540> and<00:02:50.750> any<00:02:51.019> external<00:02:51.440> auditor<00:02:52.099> to 00:02:52.630 --> 00:02:52.640 align:start position:0% contracts and any external auditor to 00:02:52.640 --> 00:02:54.580 align:start position:0% contracts and any external auditor to verify<00:02:53.000> that<00:02:53.209> the<00:02:53.420> data<00:02:53.450> being<00:02:53.959> provided<00:02:54.290> by 00:02:54.580 --> 00:02:54.590 align:start position:0% verify that the data being provided by 00:02:54.590 --> 00:02:56.170 align:start position:0% verify that the data being provided by the<00:02:54.650> Oracle<00:02:55.099> has<00:02:55.280> not<00:02:55.519> been<00:02:55.730> tampered<00:02:55.970> with 00:02:56.170 --> 00:02:56.180 align:start position:0% the Oracle has not been tampered with 00:02:56.180 --> 00:02:58.569 align:start position:0% the Oracle has not been tampered with and<00:02:56.569> that<00:02:57.079> the<00:02:57.230> result<00:02:57.590> that<00:02:57.920> the<00:02:58.190> smart 00:02:58.569 --> 00:02:58.579 align:start position:0% and that the result that the smart 00:02:58.579 --> 00:03:00.880 align:start position:0% and that the result that the smart contract<00:02:59.000> is<00:02:59.269> receiving<00:02:59.930> is<00:03:00.140> really<00:03:00.530> the<00:03:00.709> one 00:03:00.880 --> 00:03:00.890 align:start position:0% contract is receiving is really the one 00:03:00.890 --> 00:03:05.349 align:start position:0% contract is receiving is really the one sent<00:03:01.250> by<00:03:01.489> the<00:03:02.200> external<00:03:03.200> data<00:03:03.620> source<00:03:04.010> so<00:03:04.940> the 00:03:05.349 --> 00:03:05.359 align:start position:0% sent by the external data source so the 00:03:05.359 --> 00:03:07.059 align:start position:0% sent by the external data source so the first<00:03:05.629> one<00:03:05.840> is<00:03:06.019> based<00:03:06.470> on<00:03:06.620> an<00:03:06.769> external 00:03:07.059 --> 00:03:07.069 align:start position:0% first one is based on an external 00:03:07.069 --> 00:03:09.640 align:start position:0% first one is based on an external project<00:03:07.609> called<00:03:07.849> TLS<00:03:08.150> notary<00:03:08.569> this<00:03:09.349> is<00:03:09.500> the 00:03:09.640 --> 00:03:09.650 align:start position:0% project called TLS notary this is the 00:03:09.650 --> 00:03:11.830 align:start position:0% project called TLS notary this is the only<00:03:09.769> one<00:03:09.950> available<00:03:10.250> today<00:03:10.700> on<00:03:11.150> the<00:03:11.510> ATM 00:03:11.830 --> 00:03:11.840 align:start position:0% only one available today on the ATM 00:03:11.840 --> 00:03:14.759 align:start position:0% only one available today on the ATM maenette<00:03:12.410> since<00:03:13.400> September<00:03:14.060> last<00:03:14.209> year<00:03:14.359> and 00:03:14.759 --> 00:03:14.769 align:start position:0% maenette since September last year and 00:03:14.769 --> 00:03:18.099 align:start position:0% maenette since September last year and the<00:03:15.769> way<00:03:15.920> it<00:03:16.099> works<00:03:16.370> just<00:03:16.760> briefly<00:03:17.120> is<00:03:17.359> that 00:03:18.099 --> 00:03:18.109 align:start position:0% the way it works just briefly is that 00:03:18.109 --> 00:03:20.740 align:start position:0% the way it works just briefly is that when<00:03:18.590> the<00:03:18.920> client<00:03:19.459> the<00:03:20.239> client<00:03:20.599> being 00:03:20.740 --> 00:03:20.750 align:start position:0% when the client the client being 00:03:20.750 --> 00:03:24.250 align:start position:0% when the client the client being authorized<00:03:21.430> initiate<00:03:22.430> a<00:03:22.819> TLS<00:03:23.329> session<00:03:23.569> with<00:03:24.230> a 00:03:24.250 --> 00:03:24.260 align:start position:0% authorized initiate a TLS session with a 00:03:24.260 --> 00:03:26.680 align:start position:0% authorized initiate a TLS session with a web<00:03:24.530> service<00:03:24.950> the<00:03:25.459> client<00:03:25.819> secret<00:03:26.000> is<00:03:26.329> split 00:03:26.680 --> 00:03:26.690 align:start position:0% web service the client secret is split 00:03:26.690 --> 00:03:30.960 align:start position:0% web service the client secret is split in<00:03:26.840> alpha<00:03:27.140> so<00:03:27.829> that<00:03:27.859> Oracle<00:03:28.730> is<00:03:28.819> just 00:03:30.960 --> 00:03:30.970 align:start position:0% in alpha so that Oracle is just 00:03:30.970 --> 00:03:33.550 align:start position:0% in alpha so that Oracle is just just<00:03:31.970> as<00:03:32.120> alpha<00:03:32.540> feet<00:03:32.720> and<00:03:32.900> the<00:03:33.079> other<00:03:33.109> valve 00:03:33.550 --> 00:03:33.560 align:start position:0% just as alpha feet and the other valve 00:03:33.560 --> 00:03:36.849 align:start position:0% just as alpha feet and the other valve the<00:03:34.190> other<00:03:34.310> half<00:03:34.489> is<00:03:34.730> secured<00:03:35.180> by<00:03:35.260> a<00:03:36.260> piece<00:03:36.709> of 00:03:36.849 --> 00:03:36.859 align:start position:0% the other half is secured by a piece of 00:03:36.859 --> 00:03:39.699 align:start position:0% the other half is secured by a piece of code<00:03:37.099> whose<00:03:37.579> correct<00:03:37.940> execution<00:03:38.239> is<00:03:38.810> ensured 00:03:39.699 --> 00:03:39.709 align:start position:0% code whose correct execution is ensured 00:03:39.709 --> 00:03:42.220 align:start position:0% code whose correct execution is ensured via<00:03:40.069> the<00:03:40.669> Amazon<00:03:41.150> Web<00:03:41.329> service<00:03:41.780> sandbox 00:03:42.220 --> 00:03:42.230 align:start position:0% via the Amazon Web service sandbox 00:03:42.230 --> 00:03:45.970 align:start position:0% via the Amazon Web service sandbox concept<00:03:42.769> so<00:03:43.510> the<00:03:44.510> way<00:03:44.660> it<00:03:44.720> works<00:03:44.959> is<00:03:45.200> that<00:03:45.260> we 00:03:45.970 --> 00:03:45.980 align:start position:0% concept so the way it works is that we 00:03:45.980 --> 00:03:48.369 align:start position:0% concept so the way it works is that we get<00:03:46.190> a<00:03:46.459> cryptographic<00:03:46.879> proof<00:03:47.329> out<00:03:47.569> which 00:03:48.369 --> 00:03:48.379 align:start position:0% get a cryptographic proof out which 00:03:48.379 --> 00:03:51.190 align:start position:0% get a cryptographic proof out which doesn't<00:03:48.889> prove<00:03:49.099> that<00:03:49.430> the<00:03:50.000> data<00:03:50.389> has<00:03:50.959> not<00:03:51.139> been 00:03:51.190 --> 00:03:51.200 align:start position:0% doesn't prove that the data has not been 00:03:51.200 --> 00:03:53.680 align:start position:0% doesn't prove that the data has not been tampered<00:03:51.799> it<00:03:52.190> just<00:03:52.519> proves<00:03:52.760> that<00:03:52.970> there<00:03:53.510> was 00:03:53.680 --> 00:03:53.690 align:start position:0% tampered it just proves that there was 00:03:53.690 --> 00:03:55.900 align:start position:0% tampered it just proves that there was some<00:03:53.930> kind<00:03:54.109> of<00:03:54.349> cooperation<00:03:54.769> between<00:03:55.489> the 00:03:55.900 --> 00:03:55.910 align:start position:0% some kind of cooperation between the 00:03:55.910 --> 00:03:57.610 align:start position:0% some kind of cooperation between the notary<00:03:56.180> server<00:03:56.480> running<00:03:56.870> on<00:03:57.109> Amazon<00:03:57.500> Web 00:03:57.610 --> 00:03:57.620 align:start position:0% notary server running on Amazon Web 00:03:57.620 --> 00:03:59.039 align:start position:0% notary server running on Amazon Web service<00:03:58.010> and 00:03:59.039 --> 00:03:59.049 align:start position:0% service and 00:03:59.049 --> 00:04:02.140 align:start position:0% service and Oracle<00:04:00.049> eyes<00:04:00.139> so<00:04:00.919> this<00:04:01.069> means<00:04:01.370> that<00:04:01.459> if<00:04:01.819> you<00:04:01.970> do 00:04:02.140 --> 00:04:02.150 align:start position:0% Oracle eyes so this means that if you do 00:04:02.150 --> 00:04:05.409 align:start position:0% Oracle eyes so this means that if you do trust<00:04:02.590> Amazon<00:04:03.590> being<00:04:03.859> honest<00:04:04.280> then<00:04:04.879> Oracle 00:04:05.409 --> 00:04:05.419 align:start position:0% trust Amazon being honest then Oracle 00:04:05.419 --> 00:04:08.409 align:start position:0% trust Amazon being honest then Oracle eyes<00:04:05.629> is<00:04:05.810> being<00:04:06.049> honest<00:04:06.500> as<00:04:06.620> well<00:04:07.150> so<00:04:08.150> there<00:04:08.329> is 00:04:08.409 --> 00:04:08.419 align:start position:0% eyes is being honest as well so there is 00:04:08.419 --> 00:04:11.199 align:start position:0% eyes is being honest as well so there is a<00:04:08.449> trust<00:04:08.840> in<00:04:09.199> Amazon<00:04:10.040> with<00:04:10.340> Amazon<00:04:10.819> being<00:04:11.030> an 00:04:11.199 --> 00:04:11.209 align:start position:0% a trust in Amazon with Amazon being an 00:04:11.209 --> 00:04:12.240 align:start position:0% a trust in Amazon with Amazon being an artist<00:04:11.449> either 00:04:12.240 --> 00:04:12.250 align:start position:0% artist either 00:04:12.250 --> 00:04:15.400 align:start position:0% artist either another<00:04:13.250> approach<00:04:13.579> that<00:04:14.269> we<00:04:14.900> are<00:04:14.959> presenting 00:04:15.400 --> 00:04:15.410 align:start position:0% another approach that we are presenting 00:04:15.410 --> 00:04:18.640 align:start position:0% another approach that we are presenting today<00:04:15.789> you<00:04:16.789> can<00:04:16.970> check<00:04:17.180> out<00:04:17.359> the<00:04:18.049> paper<00:04:18.260> that 00:04:18.640 --> 00:04:18.650 align:start position:0% today you can check out the paper that 00:04:18.650 --> 00:04:20.740 align:start position:0% today you can check out the paper that we<00:04:18.829> are<00:04:18.919> releasing<00:04:19.130> this<00:04:19.370> afternoon<00:04:19.820> it's 00:04:20.740 --> 00:04:20.750 align:start position:0% we are releasing this afternoon it's 00:04:20.750 --> 00:04:22.719 align:start position:0% we are releasing this afternoon it's based<00:04:21.019> on<00:04:21.199> a<00:04:21.229> different<00:04:21.530> approach<00:04:21.949> so<00:04:22.699> the 00:04:22.719 --> 00:04:22.729 align:start position:0% based on a different approach so the 00:04:22.729 --> 00:04:25.420 align:start position:0% based on a different approach so the first<00:04:23.150> one<00:04:23.360> the<00:04:23.479> TLS<00:04:23.720> not<00:04:23.870> one<00:04:24.410> is<00:04:24.650> essentially 00:04:25.420 --> 00:04:25.430 align:start position:0% first one the TLS not one is essentially 00:04:25.430 --> 00:04:28.000 align:start position:0% first one the TLS not one is essentially a<00:04:25.460> software<00:04:26.060> attestation<00:04:26.690> this<00:04:27.260> one<00:04:27.500> is<00:04:27.770> an 00:04:28.000 --> 00:04:28.010 align:start position:0% a software attestation this one is an 00:04:28.010 --> 00:04:30.550 align:start position:0% a software attestation this one is an app<00:04:28.160> door<00:04:28.340> best<00:04:28.580> one<00:04:28.820> we<00:04:29.570> call<00:04:29.810> it<00:04:29.930> Android 00:04:30.550 --> 00:04:30.560 align:start position:0% app door best one we call it Android 00:04:30.560 --> 00:04:33.610 align:start position:0% app door best one we call it Android proof<00:04:30.830> and<00:04:31.599> essentially<00:04:32.599> it<00:04:32.810> does<00:04:33.110> leverage 00:04:33.610 --> 00:04:33.620 align:start position:0% proof and essentially it does leverage 00:04:33.620 --> 00:04:36.129 align:start position:0% proof and essentially it does leverage through<00:04:33.979> techniques<00:04:34.960> technologies<00:04:35.960> the 00:04:36.129 --> 00:04:36.139 align:start position:0% through techniques technologies the 00:04:36.139 --> 00:04:38.469 align:start position:0% through techniques technologies the first<00:04:36.380> one<00:04:36.590> is<00:04:36.800> Q<00:04:37.280> SE<00:04:37.550> e<00:04:37.580> which<00:04:38.240> is<00:04:38.270> the 00:04:38.469 --> 00:04:38.479 align:start position:0% first one is Q SE e which is the 00:04:38.479 --> 00:04:41.380 align:start position:0% first one is Q SE e which is the Qualcomm<00:04:39.140> te<00:04:39.530> e<00:04:39.680> trusted<00:04:40.310> execution<00:04:40.969> and 00:04:41.380 --> 00:04:41.390 align:start position:0% Qualcomm te e trusted execution and 00:04:41.390 --> 00:04:43.970 align:start position:0% Qualcomm te e trusted execution and viral<00:04:41.760> and<00:04:41.990> solution<00:04:42.990> and<00:04:43.170> Android 00:04:43.970 --> 00:04:43.980 align:start position:0% viral and solution and Android 00:04:43.980 --> 00:04:46.430 align:start position:0% viral and solution and Android safety-net<00:04:44.430> so<00:04:45.120> by<00:04:45.270> using<00:04:45.450> both<00:04:45.690> of<00:04:45.750> them<00:04:46.050> we 00:04:46.430 --> 00:04:46.440 align:start position:0% safety-net so by using both of them we 00:04:46.440 --> 00:04:50.900 align:start position:0% safety-net so by using both of them we can<00:04:46.740> basically<00:04:47.840> verify<00:04:48.840> that<00:04:49.610> there<00:04:50.610> is<00:04:50.730> an 00:04:50.900 --> 00:04:50.910 align:start position:0% can basically verify that there is an 00:04:50.910 --> 00:04:52.670 align:start position:0% can basically verify that there is an open<00:04:51.180> source<00:04:51.360> piece<00:04:51.630> of<00:04:51.780> code<00:04:52.050> fetching<00:04:52.530> the 00:04:52.670 --> 00:04:52.680 align:start position:0% open source piece of code fetching the 00:04:52.680 --> 00:04:54.410 align:start position:0% open source piece of code fetching the data<00:04:52.710> from<00:04:53.400> the<00:04:53.520> web<00:04:53.670> service<00:04:54.060> which<00:04:54.270> is 00:04:54.410 --> 00:04:54.420 align:start position:0% data from the web service which is 00:04:54.420 --> 00:04:57.430 align:start position:0% data from the web service which is running<00:04:54.660> in<00:04:55.020> a<00:04:55.470> secured<00:04:55.980> Hardware<00:04:56.790> bad 00:04:57.430 --> 00:04:57.440 align:start position:0% running in a secured Hardware bad 00:04:57.440 --> 00:05:01.660 align:start position:0% running in a secured Hardware bad Android<00:04:58.440> based<00:04:58.680> device 00:05:01.660 --> 00:05:01.670 align:start position:0% 00:05:01.670 --> 00:05:03.980 align:start position:0% the<00:05:02.670> third<00:05:02.880> one<00:05:03.090> that<00:05:03.120> we<00:05:03.270> are<00:05:03.420> presenting<00:05:03.870> is 00:05:03.980 --> 00:05:03.990 align:start position:0% the third one that we are presenting is 00:05:03.990 --> 00:05:05.570 align:start position:0% the third one that we are presenting is slightly<00:05:04.200> different<00:05:04.470> because<00:05:04.860> it<00:05:05.190> doesn't 00:05:05.570 --> 00:05:05.580 align:start position:0% slightly different because it doesn't 00:05:05.580 --> 00:05:07.940 align:start position:0% slightly different because it doesn't prove<00:05:06.180> that<00:05:06.240> it<00:05:06.930> has<00:05:06.960> not<00:05:07.290> been<00:05:07.470> tampered<00:05:07.650> with 00:05:07.940 --> 00:05:07.950 align:start position:0% prove that it has not been tampered with 00:05:07.950 --> 00:05:09.830 align:start position:0% prove that it has not been tampered with when<00:05:08.340> fetching<00:05:08.700> data<00:05:08.790> from<00:05:09.090> an<00:05:09.180> external<00:05:09.510> data 00:05:09.830 --> 00:05:09.840 align:start position:0% when fetching data from an external data 00:05:09.840 --> 00:05:12.860 align:start position:0% when fetching data from an external data source<00:05:10.140> but<00:05:10.590> it's<00:05:10.770> based<00:05:11.010> on<00:05:11.310> Intel<00:05:11.700> SGX<00:05:11.850> so<00:05:12.750> we 00:05:12.860 --> 00:05:12.870 align:start position:0% source but it's based on Intel SGX so we 00:05:12.870 --> 00:05:14.590 align:start position:0% source but it's based on Intel SGX so we have<00:05:12.990> already<00:05:13.140> seen<00:05:13.740> it<00:05:13.860> with<00:05:14.040> a<00:05:14.070> clipless 00:05:14.590 --> 00:05:14.600 align:start position:0% have already seen it with a clipless 00:05:14.600 --> 00:05:17.360 align:start position:0% have already seen it with a clipless with<00:05:15.600> a<00:05:15.630> clipless<00:05:15.900> presentation<00:05:16.650> Intel<00:05:17.250> SGX 00:05:17.360 --> 00:05:17.370 align:start position:0% with a clipless presentation Intel SGX 00:05:17.370 --> 00:05:21.350 align:start position:0% with a clipless presentation Intel SGX again<00:05:18.210> is<00:05:18.650> capable<00:05:19.650> of<00:05:19.970> verifying<00:05:20.970> that<00:05:21.060> a 00:05:21.350 --> 00:05:21.360 align:start position:0% again is capable of verifying that a 00:05:21.360 --> 00:05:23.630 align:start position:0% again is capable of verifying that a given<00:05:21.630> piece<00:05:21.780> of<00:05:21.900> code<00:05:22.110> a<00:05:22.380> subset<00:05:23.280> of<00:05:23.400> C 00:05:23.630 --> 00:05:23.640 align:start position:0% given piece of code a subset of C 00:05:23.640 --> 00:05:26.650 align:start position:0% given piece of code a subset of C essentially<00:05:24.030> is<00:05:24.420> running<00:05:24.900> in<00:05:25.080> a<00:05:25.260> secure 00:05:26.650 --> 00:05:26.660 align:start position:0% essentially is running in a secure 00:05:26.660 --> 00:05:30.650 align:start position:0% essentially is running in a secure Intel<00:05:27.660> CPU<00:05:28.020> backed<00:05:28.790> sandbox<00:05:29.790> and<00:05:30.060> there<00:05:30.570> is 00:05:30.650 --> 00:05:30.660 align:start position:0% Intel CPU backed sandbox and there is 00:05:30.660 --> 00:05:33.920 align:start position:0% Intel CPU backed sandbox and there is the<00:05:30.920> inter<00:05:31.920> signature<00:05:32.490> on<00:05:32.730> the<00:05:33.450> correct 00:05:33.920 --> 00:05:33.930 align:start position:0% the inter signature on the correct 00:05:33.930 --> 00:05:36.830 align:start position:0% the inter signature on the correct execution<00:05:34.230> of<00:05:34.650> the<00:05:34.770> code<00:05:34.980> so<00:05:35.640> this<00:05:36.240> process<00:05:36.510> is 00:05:36.830 --> 00:05:36.840 align:start position:0% execution of the code so this process is 00:05:36.840 --> 00:05:39.050 align:start position:0% execution of the code so this process is essentially<00:05:37.440> closed<00:05:37.680> called<00:05:38.460> enclaved 00:05:39.050 --> 00:05:39.060 align:start position:0% essentially closed called enclaved 00:05:39.060 --> 00:05:41.030 align:start position:0% essentially closed called enclaved remote<00:05:39.330> attestation<00:05:39.720> and<00:05:40.110> works<00:05:40.440> via<00:05:40.740> the 00:05:41.030 --> 00:05:41.040 align:start position:0% remote attestation and works via the 00:05:41.040 --> 00:05:43.910 align:start position:0% remote attestation and works via the Intel<00:05:41.400> attestation<00:05:41.700> service<00:05:42.180> and<00:05:42.680> we<00:05:43.680> use 00:05:43.910 --> 00:05:43.920 align:start position:0% Intel attestation service and we use 00:05:43.920 --> 00:05:47.450 align:start position:0% Intel attestation service and we use this<00:05:44.270> to<00:05:45.270> solve<00:05:45.840> one<00:05:46.140> of<00:05:46.170> the<00:05:46.440> very<00:05:46.590> issue<00:05:46.830> that 00:05:47.450 --> 00:05:47.460 align:start position:0% this to solve one of the very issue that 00:05:47.460 --> 00:05:48.770 align:start position:0% this to solve one of the very issue that we<00:05:47.670> have<00:05:47.760> seen<00:05:47.970> in<00:05:48.060> the<00:05:48.150> last<00:05:48.180> few<00:05:48.450> days<00:05:48.600> in 00:05:48.770 --> 00:05:48.780 align:start position:0% we have seen in the last few days in 00:05:48.780 --> 00:05:51.080 align:start position:0% we have seen in the last few days in many<00:05:48.960> talks<00:05:49.200> which<00:05:49.800> is<00:05:50.070> the<00:05:50.490> difficulty<00:05:51.060> of 00:05:51.080 --> 00:05:51.090 align:start position:0% many talks which is the difficulty of 00:05:51.090 --> 00:05:54.040 align:start position:0% many talks which is the difficulty of getting<00:05:51.330> reliable<00:05:52.230> on<00:05:52.410> chain<00:05:52.770> random<00:05:53.280> data 00:05:54.040 --> 00:05:54.050 align:start position:0% getting reliable on chain random data 00:05:54.050 --> 00:05:58.040 align:start position:0% getting reliable on chain random data random<00:05:55.050> numbers<00:05:55.440> right<00:05:56.180> so<00:05:57.180> with<00:05:57.510> random<00:05:57.900> data 00:05:58.040 --> 00:05:58.050 align:start position:0% random numbers right so with random data 00:05:58.050 --> 00:06:00.410 align:start position:0% random numbers right so with random data source<00:05:58.410> that<00:05:58.680> you<00:05:58.830> can<00:05:58.860> use<00:05:59.040> via<00:05:59.340> replies<00:05:59.790> what 00:06:00.410 --> 00:06:00.420 align:start position:0% source that you can use via replies what 00:06:00.420 --> 00:06:02.600 align:start position:0% source that you can use via replies what you<00:06:00.600> get<00:06:00.780> out<00:06:00.990> is<00:06:01.320> a<00:06:01.380> random<00:06:01.920> number<00:06:02.280> which<00:06:02.310> is 00:06:02.600 --> 00:06:02.610 align:start position:0% you get out is a random number which is 00:06:02.610 --> 00:06:04.700 align:start position:0% you get out is a random number which is generated<00:06:03.150> by<00:06:03.300> a<00:06:03.330> low-level<00:06:03.870> Intel<00:06:04.500> SGX 00:06:04.700 --> 00:06:04.710 align:start position:0% generated by a low-level Intel SGX 00:06:04.710 --> 00:06:07.040 align:start position:0% generated by a low-level Intel SGX backed<00:06:05.340> instruction<00:06:06.000> and<00:06:06.180> you<00:06:06.690> can<00:06:06.870> verify 00:06:07.040 --> 00:06:07.050 align:start position:0% backed instruction and you can verify 00:06:07.050 --> 00:06:09.740 align:start position:0% backed instruction and you can verify the<00:06:07.290> correct<00:06:07.710> execution<00:06:08.150> meaning<00:06:09.150> that<00:06:09.360> the 00:06:09.740 --> 00:06:09.750 align:start position:0% the correct execution meaning that the 00:06:09.750 --> 00:06:12.040 align:start position:0% the correct execution meaning that the random<00:06:10.050> data<00:06:10.230> was<00:06:10.950> really 00:06:12.040 --> 00:06:12.050 align:start position:0% random data was really 00:06:12.050 --> 00:06:15.650 align:start position:0% random data was really random<00:06:13.050> if<00:06:13.440> you<00:06:13.620> do<00:06:13.800> trust<00:06:14.100> the<00:06:14.910> Intel 00:06:15.650 --> 00:06:15.660 align:start position:0% random if you do trust the Intel 00:06:15.660 --> 00:06:18.950 align:start position:0% random if you do trust the Intel solution<00:06:16.110> so<00:06:16.860> again<00:06:17.250> here<00:06:17.640> we<00:06:18.180> are<00:06:18.210> we<00:06:18.570> have 00:06:18.950 --> 00:06:18.960 align:start position:0% solution so again here we are we have 00:06:18.960 --> 00:06:21.740 align:start position:0% solution so again here we are we have just<00:06:19.170> seen<00:06:19.320> two<00:06:19.500> different<00:06:19.530> data<00:06:20.010> Staters<00:06:20.750> so 00:06:21.740 --> 00:06:21.750 align:start position:0% just seen two different data Staters so 00:06:21.750 --> 00:06:25.660 align:start position:0% just seen two different data Staters so Google<00:06:22.560> or<00:06:22.770> Qualcomm<00:06:23.430> if<00:06:23.550> you<00:06:23.670> want<00:06:23.850> and<00:06:24.530> Intel 00:06:25.660 --> 00:06:25.670 align:start position:0% Google or Qualcomm if you want and Intel 00:06:25.670 --> 00:06:27.890 align:start position:0% Google or Qualcomm if you want and Intel so<00:06:26.670> what<00:06:26.910> we<00:06:27.030> are<00:06:27.090> seeing<00:06:27.240> so<00:06:27.390> far<00:06:27.420> with<00:06:27.750> all 00:06:27.890 --> 00:06:27.900 align:start position:0% so what we are seeing so far with all 00:06:27.900 --> 00:06:30.110 align:start position:0% so what we are seeing so far with all these<00:06:28.110> three<00:06:28.740> different<00:06:29.220> authenticity 00:06:30.110 --> 00:06:30.120 align:start position:0% these three different authenticity 00:06:30.120 --> 00:06:33.050 align:start position:0% these three different authenticity proofs<00:06:30.690> is<00:06:30.950> at<00:06:31.950> the<00:06:32.130> station<00:06:32.490> as<00:06:32.580> a<00:06:32.610> service 00:06:33.050 --> 00:06:33.060 align:start position:0% proofs is at the station as a service 00:06:33.060 --> 00:06:35.410 align:start position:0% proofs is at the station as a service essentially<00:06:33.570> so<00:06:33.720> different<00:06:34.320> kind<00:06:34.920> of 00:06:35.410 --> 00:06:35.420 align:start position:0% essentially so different kind of 00:06:35.420 --> 00:06:38.390 align:start position:0% essentially so different kind of software<00:06:36.420> and<00:06:36.840> adver<00:06:37.230> attestation<00:06:37.650> that<00:06:38.010> we 00:06:38.390 --> 00:06:38.400 align:start position:0% software and adver attestation that we 00:06:38.400 --> 00:06:40.400 align:start position:0% software and adver attestation that we can<00:06:38.580> use<00:06:38.850> to<00:06:39.150> move<00:06:39.270> the<00:06:39.420> trust<00:06:39.630> away<00:06:39.900> from<00:06:40.200> the 00:06:40.400 --> 00:06:40.410 align:start position:0% can use to move the trust away from the 00:06:40.410 --> 00:06:45.130 align:start position:0% can use to move the trust away from the untrusted<00:06:40.830> a<00:06:41.340> small<00:06:41.910> start-up<00:06:42.420> Oracle<00:06:43.320> to<00:06:43.950> a 00:06:45.130 --> 00:06:45.140 align:start position:0% untrusted a small start-up Oracle to a 00:06:45.140 --> 00:06:48.080 align:start position:0% untrusted a small start-up Oracle to a trusted<00:06:46.140> entity<00:06:46.350> which<00:06:47.340> is<00:06:47.550> a<00:06:47.580> much<00:06:47.880> bigger 00:06:48.080 --> 00:06:48.090 align:start position:0% trusted entity which is a much bigger 00:06:48.090 --> 00:06:50.300 align:start position:0% trusted entity which is a much bigger company<00:06:48.390> of<00:06:48.780> course<00:06:49.200> you<00:06:49.410> don't<00:06:49.620> want<00:06:49.890> to 00:06:50.300 --> 00:06:50.310 align:start position:0% company of course you don't want to 00:06:50.310 --> 00:06:52.580 align:start position:0% company of course you don't want to trust<00:06:50.580> a<00:06:50.850> single<00:06:51.390> corporation<00:06:51.810> but<00:06:52.470> the 00:06:52.580 --> 00:06:52.590 align:start position:0% trust a single corporation but the 00:06:52.590 --> 00:06:53.960 align:start position:0% trust a single corporation but the assumption<00:06:53.010> that<00:06:53.040> we<00:06:53.220> are<00:06:53.250> making<00:06:53.340> here<00:06:53.820> is 00:06:53.960 --> 00:06:53.970 align:start position:0% assumption that we are making here is 00:06:53.970 --> 00:06:56.830 align:start position:0% assumption that we are making here is that<00:06:54.030> if<00:06:54.690> you 00:06:56.830 --> 00:06:56.840 align:start position:0% that if you 00:06:56.840 --> 00:07:00.469 align:start position:0% that if you few<00:06:57.840> trusted<00:06:58.520> companies<00:06:59.520> or<00:06:59.669> Atta<00:06:59.849> status<00:07:00.330> in 00:07:00.469 --> 00:07:00.479 align:start position:0% few trusted companies or Atta status in 00:07:00.479 --> 00:07:03.820 align:start position:0% few trusted companies or Atta status in this<00:07:00.629> case<00:07:00.870> are<00:07:01.860> less<00:07:02.310> likely<00:07:02.610> to 00:07:03.820 --> 00:07:03.830 align:start position:0% this case are less likely to 00:07:03.830 --> 00:07:07.279 align:start position:0% this case are less likely to mmm<00:07:04.830> act<00:07:05.039> all<00:07:05.430> aspect<00:07:05.849> actors<00:07:06.270> compared<00:07:06.960> to<00:07:07.259> a 00:07:07.279 --> 00:07:07.289 align:start position:0% mmm act all aspect actors compared to a 00:07:07.289 --> 00:07:10.629 align:start position:0% mmm act all aspect actors compared to a network<00:07:07.949> of<00:07:08.159> untrusted<00:07:08.909> anonymous<00:07:09.419> players 00:07:10.629 --> 00:07:10.639 align:start position:0% network of untrusted anonymous players 00:07:10.639 --> 00:07:14.270 align:start position:0% network of untrusted anonymous players so<00:07:11.639> viralize<00:07:12.360> you<00:07:12.690> can<00:07:12.840> specify<00:07:13.050> the<00:07:13.830> proof 00:07:14.270 --> 00:07:14.280 align:start position:0% so viralize you can specify the proof 00:07:14.280 --> 00:07:17.830 align:start position:0% so viralize you can specify the proof that<00:07:14.460> you<00:07:14.610> want<00:07:14.819> to<00:07:14.879> get<00:07:15.000> out<00:07:15.270> so<00:07:15.990> the<00:07:16.440> kind<00:07:16.770> of 00:07:17.830 --> 00:07:17.840 align:start position:0% that you want to get out so the kind of 00:07:17.840 --> 00:07:20.210 align:start position:0% that you want to get out so the kind of authenticity<00:07:18.840> proof<00:07:19.349> that<00:07:19.560> you<00:07:19.680> want<00:07:19.949> the 00:07:20.210 --> 00:07:20.220 align:start position:0% authenticity proof that you want the 00:07:20.220 --> 00:07:21.980 align:start position:0% authenticity proof that you want the Oracle<00:07:20.669> eyes<00:07:20.759> infrastructure<00:07:21.419> to<00:07:21.599> generate 00:07:21.980 --> 00:07:21.990 align:start position:0% Oracle eyes infrastructure to generate 00:07:21.990 --> 00:07:24.529 align:start position:0% Oracle eyes infrastructure to generate to<00:07:22.710> fetch<00:07:22.949> this<00:07:23.099> kind<00:07:23.340> of<00:07:23.400> data<00:07:23.639> and<00:07:23.970> of<00:07:24.509> course 00:07:24.529 --> 00:07:24.539 align:start position:0% to fetch this kind of data and of course 00:07:24.539 --> 00:07:26.629 align:start position:0% to fetch this kind of data and of course you<00:07:24.960> can<00:07:25.110> specify<00:07:25.319> more<00:07:25.830> than<00:07:26.069> one<00:07:26.220> proof<00:07:26.460> so 00:07:26.629 --> 00:07:26.639 align:start position:0% you can specify more than one proof so 00:07:26.639 --> 00:07:29.899 align:start position:0% you can specify more than one proof so you<00:07:26.669> can<00:07:26.970> get<00:07:27.569> the<00:07:28.080> Android<00:07:28.710> proof<00:07:29.039> DTLS<00:07:29.699> not 00:07:29.899 --> 00:07:29.909 align:start position:0% you can get the Android proof DTLS not 00:07:29.909 --> 00:07:32.629 align:start position:0% you can get the Android proof DTLS not reproof<00:07:30.240> etc<00:07:30.810> on<00:07:30.960> the<00:07:31.259> same<00:07:31.470> request<00:07:31.830> meaning 00:07:32.629 --> 00:07:32.639 align:start position:0% reproof etc on the same request meaning 00:07:32.639 --> 00:07:35.510 align:start position:0% reproof etc on the same request meaning that<00:07:32.819> if<00:07:33.150> all<00:07:33.479> the<00:07:33.720> proofs<00:07:33.990> are<00:07:34.169> valid<00:07:34.590> and<00:07:34.860> the 00:07:35.510 --> 00:07:35.520 align:start position:0% that if all the proofs are valid and the 00:07:35.520 --> 00:07:37.580 align:start position:0% that if all the proofs are valid and the result<00:07:35.819> is<00:07:35.970> the<00:07:36.270> estill<00:07:36.690> been<00:07:36.870> tampered<00:07:37.259> with 00:07:37.580 --> 00:07:37.590 align:start position:0% result is the estill been tampered with 00:07:37.590 --> 00:07:39.830 align:start position:0% result is the estill been tampered with it<00:07:37.710> will<00:07:38.039> mean<00:07:38.190> that<00:07:38.370> at<00:07:38.729> the<00:07:38.880> same<00:07:39.150> time<00:07:39.509> at 00:07:39.830 --> 00:07:39.840 align:start position:0% it will mean that at the same time at 00:07:39.840 --> 00:07:41.379 align:start position:0% it will mean that at the same time at the<00:07:40.020> same<00:07:40.229> exact<00:07:40.650> time 00:07:41.379 --> 00:07:41.389 align:start position:0% the same exact time 00:07:41.389 --> 00:07:45.170 align:start position:0% the same exact time android<00:07:42.389> Qualcomm<00:07:43.199> Amazon<00:07:43.979> and<00:07:44.159> Google<00:07:44.430> were 00:07:45.170 --> 00:07:45.180 align:start position:0% android Qualcomm Amazon and Google were 00:07:45.180 --> 00:07:48.439 align:start position:0% android Qualcomm Amazon and Google were all<00:07:45.419> providing<00:07:46.050> the<00:07:46.169> same<00:07:46.409> wrong<00:07:46.710> data<00:07:47.449> which 00:07:48.439 --> 00:07:48.449 align:start position:0% all providing the same wrong data which 00:07:48.449 --> 00:07:49.510 align:start position:0% all providing the same wrong data which is<00:07:48.569> pretty<00:07:48.810> unlikely 00:07:49.510 --> 00:07:49.520 align:start position:0% is pretty unlikely 00:07:49.520 --> 00:07:52.159 align:start position:0% is pretty unlikely so<00:07:50.520> the<00:07:50.789> last<00:07:50.940> thing<00:07:51.210> that<00:07:51.240> we<00:07:51.569> are<00:07:51.659> presenting 00:07:52.159 --> 00:07:52.169 align:start position:0% so the last thing that we are presenting 00:07:52.169 --> 00:07:54.860 align:start position:0% so the last thing that we are presenting today<00:07:52.520> and<00:07:53.520> that<00:07:53.909> it's<00:07:54.210> available<00:07:54.479> in<00:07:54.810> our 00:07:54.860 --> 00:07:54.870 align:start position:0% today and that it's available in our 00:07:54.870 --> 00:07:58.580 align:start position:0% today and that it's available in our documentation<00:07:55.849> is<00:07:56.849> the<00:07:57.659> option<00:07:58.050> computation 00:07:58.580 --> 00:07:58.590 align:start position:0% documentation is the option computation 00:07:58.590 --> 00:08:01.850 align:start position:0% documentation is the option computation so<00:07:58.800> this<00:07:58.979> is<00:07:59.130> yet<00:07:59.340> another<00:07:59.780> solution<00:08:00.780> to<00:08:01.349> the 00:08:01.850 --> 00:08:01.860 align:start position:0% so this is yet another solution to the 00:08:01.860 --> 00:08:03.640 align:start position:0% so this is yet another solution to the limitation<00:08:02.400> the<00:08:02.520> constraints<00:08:03.030> of<00:08:03.180> the<00:08:03.330> VM 00:08:03.640 --> 00:08:03.650 align:start position:0% limitation the constraints of the VM 00:08:03.650 --> 00:08:06.080 align:start position:0% limitation the constraints of the VM meaning<00:08:04.650> that<00:08:04.770> if<00:08:05.069> you<00:08:05.130> want<00:08:05.400> to<00:08:05.460> execute<00:08:05.729> any 00:08:06.080 --> 00:08:06.090 align:start position:0% meaning that if you want to execute any 00:08:06.090 --> 00:08:08.209 align:start position:0% meaning that if you want to execute any piece<00:08:06.330> of<00:08:06.360> code<00:08:06.750> if<00:08:06.990> you<00:08:07.349> want<00:08:07.560> to<00:08:07.680> reuse<00:08:07.830> any 00:08:08.209 --> 00:08:08.219 align:start position:0% piece of code if you want to reuse any 00:08:08.219 --> 00:08:11.029 align:start position:0% piece of code if you want to reuse any library<00:08:08.960> external<00:08:09.960> library<00:08:10.349> or<00:08:10.560> if<00:08:10.830> you<00:08:10.949> have 00:08:11.029 --> 00:08:11.039 align:start position:0% library external library or if you have 00:08:11.039 --> 00:08:13.070 align:start position:0% library external library or if you have concerns<00:08:11.520> related<00:08:12.120> to<00:08:12.210> the<00:08:12.330> gas<00:08:12.539> limit<00:08:12.779> in 00:08:13.070 --> 00:08:13.080 align:start position:0% concerns related to the gas limit in 00:08:13.080 --> 00:08:14.990 align:start position:0% concerns related to the gas limit in some<00:08:13.289> cases<00:08:13.529> you<00:08:13.830> might<00:08:13.979> want<00:08:14.310> to<00:08:14.430> delegate<00:08:14.819> to 00:08:14.990 --> 00:08:15.000 align:start position:0% some cases you might want to delegate to 00:08:15.000 --> 00:08:17.870 align:start position:0% some cases you might want to delegate to an<00:08:15.090> option<00:08:15.419> context<00:08:15.930> the<00:08:16.440> execution<00:08:17.130> of<00:08:17.370> this 00:08:17.870 --> 00:08:17.880 align:start position:0% an option context the execution of this 00:08:17.880 --> 00:08:20.659 align:start position:0% an option context the execution of this code<00:08:18.180> and<00:08:18.650> the<00:08:19.650> approach<00:08:20.130> that<00:08:20.159> we<00:08:20.460> follow 00:08:20.659 --> 00:08:20.669 align:start position:0% code and the approach that we follow 00:08:20.669 --> 00:08:22.640 align:start position:0% code and the approach that we follow here<00:08:20.909> is<00:08:21.180> again<00:08:21.479> the<00:08:21.659> one<00:08:21.690> based<00:08:22.080> on<00:08:22.380> at<00:08:22.620> least 00:08:22.640 --> 00:08:22.650 align:start position:0% here is again the one based on at least 00:08:22.650 --> 00:08:25.430 align:start position:0% here is again the one based on at least a<00:08:22.949> torso<00:08:23.400> at<00:08:23.550> the<00:08:23.699> station<00:08:24.029> and<00:08:24.930> what<00:08:25.139> we<00:08:25.319> do 00:08:25.430 --> 00:08:25.440 align:start position:0% a torso at the station and what we do 00:08:25.440 --> 00:08:28.580 align:start position:0% a torso at the station and what we do essentially<00:08:26.009> is<00:08:26.310> extending<00:08:27.060> the<00:08:27.240> base<00:08:27.840> Amazon 00:08:28.580 --> 00:08:28.590 align:start position:0% essentially is extending the base Amazon 00:08:28.590 --> 00:08:30.469 align:start position:0% essentially is extending the base Amazon Web<00:08:28.740> service<00:08:29.069> sandbox<00:08:29.490> concept<00:08:29.969> introduced 00:08:30.469 --> 00:08:30.479 align:start position:0% Web service sandbox concept introduced 00:08:30.479 --> 00:08:33.649 align:start position:0% Web service sandbox concept introduced by<00:08:30.599> today's<00:08:30.870> notary<00:08:31.259> and<00:08:32.000> with<00:08:33.000> this<00:08:33.149> extended 00:08:33.649 --> 00:08:33.659 align:start position:0% by today's notary and with this extended 00:08:33.659 --> 00:08:37.630 align:start position:0% by today's notary and with this extended concept<00:08:34.110> you<00:08:34.890> can<00:08:34.919> execute<00:08:35.550> in<00:08:36.240> a<00:08:36.719> safe 00:08:37.630 --> 00:08:37.640 align:start position:0% concept you can execute in a safe 00:08:37.640 --> 00:08:40.610 align:start position:0% concept you can execute in a safe Amazon<00:08:38.640> Web<00:08:38.909> service<00:08:39.390> best<00:08:39.719> lockdown 00:08:40.610 --> 00:08:40.620 align:start position:0% Amazon Web service best lockdown 00:08:40.620 --> 00:08:43.339 align:start position:0% Amazon Web service best lockdown instance<00:08:41.099> any<00:08:41.640> piece<00:08:41.849> of<00:08:41.969> code<00:08:42.209> and<00:08:42.419> you<00:08:42.479> can 00:08:43.339 --> 00:08:43.349 align:start position:0% instance any piece of code and you can 00:08:43.349 --> 00:08:45.680 align:start position:0% instance any piece of code and you can get<00:08:43.500> out<00:08:43.680> an<00:08:44.159> authenticity<00:08:44.790> proof<00:08:45.360> so<00:08:45.540> this 00:08:45.680 --> 00:08:45.690 align:start position:0% get out an authenticity proof so this 00:08:45.690 --> 00:08:47.780 align:start position:0% get out an authenticity proof so this authenticity<00:08:46.020> proof<00:08:46.470> can<00:08:47.100> be<00:08:47.130> verified<00:08:47.550> by 00:08:47.780 --> 00:08:47.790 align:start position:0% authenticity proof can be verified by 00:08:47.790 --> 00:08:49.240 align:start position:0% authenticity proof can be verified by anybody<00:08:48.120> and 00:08:49.240 --> 00:08:49.250 align:start position:0% anybody and 00:08:49.250 --> 00:08:52.579 align:start position:0% anybody and the<00:08:50.250> the<00:08:50.910> way<00:08:51.029> it<00:08:51.089> works<00:08:51.390> is<00:08:51.660> that<00:08:51.750> you<00:08:52.380> define 00:08:52.579 --> 00:08:52.589 align:start position:0% the the way it works is that you define 00:08:52.589 --> 00:08:55.340 align:start position:0% the the way it works is that you define our<00:08:52.890> zip<00:08:53.209> so<00:08:54.209> this<00:08:54.390> is<00:08:54.540> there<00:08:54.720> is<00:08:54.779> an<00:08:54.899> example 00:08:55.340 --> 00:08:55.350 align:start position:0% our zip so this is there is an example 00:08:55.350 --> 00:08:57.860 align:start position:0% our zip so this is there is an example here<00:08:55.680> using<00:08:56.220> for<00:08:56.370> example<00:08:56.459> the<00:08:57.000> Python<00:08:57.540> numpy 00:08:57.860 --> 00:08:57.870 align:start position:0% here using for example the Python numpy 00:08:57.870 --> 00:09:01.430 align:start position:0% here using for example the Python numpy library<00:08:58.290> and<00:08:58.500> we<00:08:59.040> can<00:08:59.220> get<00:08:59.370> a<00:08:59.399> result<00:08:59.760> out<00:09:00.440> we 00:09:01.430 --> 00:09:01.440 align:start position:0% library and we can get a result out we 00:09:01.440 --> 00:09:04.240 align:start position:0% library and we can get a result out we distribute<00:09:02.100> it<00:09:02.190> over<00:09:02.370> IP<00:09:02.640> FS<00:09:03.029> and 00:09:04.240 --> 00:09:04.250 align:start position:0% distribute it over IP FS and 00:09:04.250 --> 00:09:07.610 align:start position:0% distribute it over IP FS and in<00:09:05.250> india<00:09:06.029> oracle<00:09:06.300> ice<00:09:06.390> query<00:09:06.660> we<00:09:06.930> specify<00:09:07.440> as 00:09:07.610 --> 00:09:07.620 align:start position:0% in india oracle ice query we specify as 00:09:07.620 --> 00:09:10.639 align:start position:0% in india oracle ice query we specify as datasource<00:09:08.430> computation<00:09:09.320> metadata<00:09:10.320> source 00:09:10.639 --> 00:09:10.649 align:start position:0% datasource computation metadata source 00:09:10.649 --> 00:09:15.200 align:start position:0% datasource computation metadata source and<00:09:10.860> as<00:09:11.580> query<00:09:12.000> we<00:09:12.600> specify<00:09:13.140> the<00:09:14.210> ipfs 00:09:15.200 --> 00:09:15.210 align:start position:0% and as query we specify the ipfs 00:09:15.210 --> 00:09:18.500 align:start position:0% and as query we specify the ipfs mutation<00:09:15.810> so<00:09:16.710> what<00:09:17.130> happens<00:09:17.550> is<00:09:17.760> that<00:09:17.820> oracle 00:09:18.500 --> 00:09:18.510 align:start position:0% mutation so what happens is that oracle 00:09:18.510 --> 00:09:21.769 align:start position:0% mutation so what happens is that oracle eyes<00:09:18.630> that<00:09:19.529> does<00:09:19.710> initiate<00:09:20.700> the<00:09:21.450> secure 00:09:21.769 --> 00:09:21.779 align:start position:0% eyes that does initiate the secure 00:09:21.779 --> 00:09:24.440 align:start position:0% eyes that does initiate the secure instance<00:09:22.279> generate<00:09:23.279> the<00:09:23.580> honesty<00:09:24.000> proofs<00:09:24.240> and 00:09:24.440 --> 00:09:24.450 align:start position:0% instance generate the honesty proofs and 00:09:24.450 --> 00:09:26.930 align:start position:0% instance generate the honesty proofs and the<00:09:25.110> verification<00:09:25.380> steps<00:09:25.950> are<00:09:26.220> essentially 00:09:26.930 --> 00:09:26.940 align:start position:0% the verification steps are essentially 00:09:26.940 --> 00:09:30.410 align:start position:0% the verification steps are essentially based<00:09:27.149> on<00:09:27.390> an<00:09:27.600> extended<00:09:28.790> verification<00:09:29.790> of<00:09:30.000> the 00:09:30.410 --> 00:09:30.420 align:start position:0% based on an extended verification of the 00:09:30.420 --> 00:09:32.930 align:start position:0% based on an extended verification of the authenticity<00:09:30.779> proof<00:09:31.290> that<00:09:31.440> i've<00:09:31.649> ever<00:09:31.940> just 00:09:32.930 --> 00:09:32.940 align:start position:0% authenticity proof that i've ever just 00:09:32.940 --> 00:09:36.199 align:start position:0% authenticity proof that i've ever just explained<00:09:33.480> before<00:09:34.220> so<00:09:35.220> what<00:09:35.520> you<00:09:35.610> get<00:09:35.790> out<00:09:35.820> is 00:09:36.199 --> 00:09:36.209 align:start position:0% explained before so what you get out is 00:09:36.209 --> 00:09:37.760 align:start position:0% explained before so what you get out is the<00:09:36.420> proof<00:09:36.600> that<00:09:36.630> the<00:09:36.899> result<00:09:37.230> is<00:09:37.410> really 00:09:37.760 --> 00:09:37.770 align:start position:0% the proof that the result is really 00:09:37.770 --> 00:09:39.949 align:start position:0% the proof that the result is really coming<00:09:37.980> from<00:09:38.100> a<00:09:38.339> correct<00:09:38.670> execution<00:09:39.420> in<00:09:39.839> an 00:09:39.949 --> 00:09:39.959 align:start position:0% coming from a correct execution in an 00:09:39.959 --> 00:09:41.960 align:start position:0% coming from a correct execution in an efficient<00:09:40.290> context<00:09:40.740> of<00:09:40.860> a<00:09:41.160> single<00:09:41.399> instance 00:09:41.960 --> 00:09:41.970 align:start position:0% efficient context of a single instance 00:09:41.970 --> 00:09:44.000 align:start position:0% efficient context of a single instance of<00:09:42.120> this<00:09:42.450> piece<00:09:42.720> of<00:09:42.810> code<00:09:43.020> so<00:09:43.500> there<00:09:43.680> is<00:09:43.800> not 00:09:44.000 --> 00:09:44.010 align:start position:0% of this piece of code so there is not 00:09:44.010 --> 00:09:47.389 align:start position:0% of this piece of code so there is not anymore<00:09:44.730> this<00:09:45.390> child<00:09:46.080> this<00:09:46.410> challenge<00:09:46.980> game 00:09:47.389 --> 00:09:47.399 align:start position:0% anymore this child this challenge game 00:09:47.399 --> 00:09:49.780 align:start position:0% anymore this child this challenge game but<00:09:48.120> it's<00:09:48.360> more<00:09:48.660> like 00:09:49.780 --> 00:09:49.790 align:start position:0% but it's more like 00:09:49.790 --> 00:09:52.300 align:start position:0% but it's more like audit<00:09:50.790> or<00:09:51.029> based 00:09:52.300 --> 00:09:52.310 align:start position:0% audit or based 00:09:52.310 --> 00:09:55.160 align:start position:0% audit or based approach<00:09:53.510> so<00:09:54.510> thank<00:09:54.750> you<00:09:54.839> for<00:09:54.990> the<00:09:55.110> attention 00:09:55.160 --> 00:09:55.170 align:start position:0% approach so thank you for the attention 00:09:55.170 --> 00:09:58.070 align:start position:0% approach so thank you for the attention and<00:09:55.740> i<00:09:56.399> will<00:09:56.760> be<00:09:56.910> around<00:09:57.149> so<00:09:57.360> come<00:09:57.570> find<00:09:57.750> me<00:09:57.870> if 00:09:58.070 --> 00:09:58.080 align:start position:0% and i will be around so come find me if 00:09:58.080 --> 00:10:00.230 align:start position:0% and i will be around so come find me if you<00:09:58.200> have<00:09:58.290> any<00:09:58.470> question<00:09:58.920> we<00:09:59.399> are<00:09:59.490> looking<00:10:00.000> for 00:10:00.230 --> 00:10:00.240 align:start position:0% you have any question we are looking for 00:10:00.240 --> 00:10:02.990 align:start position:0% you have any question we are looking for feedbacks<00:10:00.720> and<00:10:01.100> we<00:10:02.100> are<00:10:02.190> releasing<00:10:02.430> as<00:10:02.670> I<00:10:02.760> said 00:10:02.990 --> 00:10:03.000 align:start position:0% feedbacks and we are releasing as I said 00:10:03.000 --> 00:10:05.660 align:start position:0% feedbacks and we are releasing as I said the<00:10:03.209> Android<00:10:03.630> paper<00:10:03.870> later<00:10:04.170> today<00:10:04.410> so<00:10:05.130> please 00:10:05.660 --> 00:10:05.670 align:start position:0% the Android paper later today so please 00:10:05.670 --> 00:10:08.210 align:start position:0% the Android paper later today so please give<00:10:06.240> us<00:10:06.330> some<00:10:06.510> feedbacks<00:10:06.899> and<00:10:07.170> thank<00:10:08.040> you<00:10:08.130> for 00:10:08.210 --> 00:10:08.220 align:start position:0% give us some feedbacks and thank you for 00:10:08.220 --> 00:10:09.430 align:start position:0% give us some feedbacks and thank you for that<00:10:08.430> again 00:10:09.430 --> 00:10:09.440 align:start position:0% that again 00:10:09.440 --> 00:10:11.490 align:start position:0% that again thank<00:10:10.440> you<00:10:10.560> very<00:10:10.589> much<00:10:10.860> time 00:10:11.490 --> 00:10:11.500 align:start position:0% thank you very much time 00:10:11.500 --> 00:10:12.480 align:start position:0% thank you very much time [Applause] 00:10:12.480 --> 00:10:12.490 align:start position:0% [Applause] 00:10:12.490 --> 00:10:20.700 align:start position:0% [Applause] [Music]