WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:18.439 align:start position:0% [Music] 00:00:18.439 --> 00:00:18.449 align:start position:0% 00:00:18.449 --> 00:00:21.540 align:start position:0% hello<00:00:19.449> to<00:00:19.570> everyone<00:00:19.900> thank<00:00:20.710> you<00:00:20.769> for<00:00:20.919> having 00:00:21.540 --> 00:00:21.550 align:start position:0% hello to everyone thank you for having 00:00:21.550 --> 00:00:22.529 align:start position:0% hello to everyone thank you for having me<00:00:21.819> here<00:00:21.849> today 00:00:22.529 --> 00:00:22.539 align:start position:0% me here today 00:00:22.539 --> 00:00:25.319 align:start position:0% me here today my<00:00:23.230> name<00:00:23.409> is<00:00:23.560> Thomas<00:00:23.949> Burton<00:00:24.159> I'm<00:00:24.699> the<00:00:24.970> CEO<00:00:25.179> of 00:00:25.319 --> 00:00:25.329 align:start position:0% my name is Thomas Burton I'm the CEO of 00:00:25.329 --> 00:00:27.929 align:start position:0% my name is Thomas Burton I'm the CEO of Oracle<00:00:25.839> eyes<00:00:25.919> during<00:00:26.919> this<00:00:26.980> presentation<00:00:27.339> I 00:00:27.929 --> 00:00:27.939 align:start position:0% Oracle eyes during this presentation I 00:00:27.939 --> 00:00:31.499 align:start position:0% Oracle eyes during this presentation I will<00:00:28.869> start<00:00:29.319> with<00:00:29.800> a<00:00:30.099> brief<00:00:30.130> recap<00:00:30.759> of<00:00:30.970> the 00:00:31.499 --> 00:00:31.509 align:start position:0% will start with a brief recap of the 00:00:31.509 --> 00:00:33.660 align:start position:0% will start with a brief recap of the Oracle<00:00:31.869> problem<00:00:32.259> and<00:00:32.500> how<00:00:32.770> Oracle<00:00:33.070> eyes<00:00:33.309> is 00:00:33.660 --> 00:00:33.670 align:start position:0% Oracle problem and how Oracle eyes is 00:00:33.670 --> 00:00:37.500 align:start position:0% Oracle problem and how Oracle eyes is trying<00:00:34.630> to<00:00:34.870> solve<00:00:35.320> it<00:00:35.470> and<00:00:35.730> I<00:00:36.730> will<00:00:37.000> do<00:00:37.150> a<00:00:37.180> deep 00:00:37.500 --> 00:00:37.510 align:start position:0% trying to solve it and I will do a deep 00:00:37.510 --> 00:00:40.320 align:start position:0% trying to solve it and I will do a deep dive<00:00:37.570> on<00:00:38.170> the<00:00:38.470> authenticity<00:00:38.680> proofs<00:00:39.220> and<00:00:39.460> on 00:00:40.320 --> 00:00:40.330 align:start position:0% dive on the authenticity proofs and on 00:00:40.330 --> 00:00:45.360 align:start position:0% dive on the authenticity proofs and on how<00:00:40.750> we<00:00:41.050> could<00:00:41.290> verify<00:00:41.530> them<00:00:42.040> on<00:00:42.460> chain<00:00:44.130> so<00:00:45.130> we 00:00:45.360 --> 00:00:45.370 align:start position:0% how we could verify them on chain so we 00:00:45.370 --> 00:00:46.230 align:start position:0% how we could verify them on chain so we have<00:00:45.550> already<00:00:45.640> seen<00:00:46.000> in<00:00:46.120> the<00:00:46.210> previous 00:00:46.230 --> 00:00:46.240 align:start position:0% have already seen in the previous 00:00:46.240 --> 00:00:50.130 align:start position:0% have already seen in the previous presentations<00:00:47.140> what<00:00:47.890> it<00:00:48.070> means<00:00:48.460> the<00:00:49.270> what<00:00:50.020> the 00:00:50.130 --> 00:00:50.140 align:start position:0% presentations what it means the what the 00:00:50.140 --> 00:00:52.770 align:start position:0% presentations what it means the what the problem<00:00:50.470> the<00:00:50.590> Oracle<00:00:51.370> problem<00:00:51.790> really<00:00:51.970> is<00:00:52.270> so 00:00:52.770 --> 00:00:52.780 align:start position:0% problem the Oracle problem really is so 00:00:52.780 --> 00:00:55.020 align:start position:0% problem the Oracle problem really is so we<00:00:52.930> know<00:00:53.079> that<00:00:53.110> in<00:00:53.590> decentralized<00:00:54.310> networks 00:00:55.020 --> 00:00:55.030 align:start position:0% we know that in decentralized networks 00:00:55.030 --> 00:00:58.290 align:start position:0% we know that in decentralized networks like<00:00:55.329> on<00:00:55.630> etherium<00:00:56.220> it's<00:00:57.220> really<00:00:57.640> complicated 00:00:58.290 --> 00:00:58.300 align:start position:0% like on etherium it's really complicated 00:00:58.300 --> 00:01:00.810 align:start position:0% like on etherium it's really complicated to<00:00:58.480> reach<00:00:58.930> out<00:00:59.140> to<00:00:59.170> external<00:00:59.590> data<00:00:59.980> to<00:01:00.579> data 00:01:00.810 --> 00:01:00.820 align:start position:0% to reach out to external data to data 00:01:00.820 --> 00:01:03.840 align:start position:0% to reach out to external data to data which<00:01:01.290> we<00:01:02.290> find<00:01:02.530> in<00:01:02.800> different<00:01:03.220> contexts<00:01:03.670> is 00:01:03.840 --> 00:01:03.850 align:start position:0% which we find in different contexts is 00:01:03.850 --> 00:01:06.179 align:start position:0% which we find in different contexts is like<00:01:04.119> for<00:01:04.299> example<00:01:04.390> on<00:01:04.809> the<00:01:04.930> web<00:01:05.110> but<00:01:06.009> in 00:01:06.179 --> 00:01:06.189 align:start position:0% like for example on the web but in 00:01:06.189 --> 00:01:07.590 align:start position:0% like for example on the web but in general<00:01:06.579> this<00:01:06.729> is<00:01:06.880> something<00:01:07.210> we<00:01:07.359> want 00:01:07.590 --> 00:01:07.600 align:start position:0% general this is something we want 00:01:07.600 --> 00:01:09.749 align:start position:0% general this is something we want because<00:01:08.229> of<00:01:08.560> the<00:01:08.710> centralized<00:01:09.159> applications 00:01:09.749 --> 00:01:09.759 align:start position:0% because of the centralized applications 00:01:09.759 --> 00:01:12.149 align:start position:0% because of the centralized applications to<00:01:09.939> have<00:01:10.030> value<00:01:10.390> because<00:01:11.020> those<00:01:11.469> application 00:01:12.149 --> 00:01:12.159 align:start position:0% to have value because those application 00:01:12.159 --> 00:01:16.459 align:start position:0% to have value because those application might<00:01:12.729> depend<00:01:13.299> on<00:01:13.450> external<00:01:13.899> real<00:01:14.319> world<00:01:14.619> data 00:01:16.459 --> 00:01:16.469 align:start position:0% might depend on external real world data 00:01:16.469 --> 00:01:20.309 align:start position:0% might depend on external real world data so<00:01:17.469> it's<00:01:17.740> important<00:01:18.280> to<00:01:18.729> define<00:01:19.149> those<00:01:19.869> three 00:01:20.309 --> 00:01:20.319 align:start position:0% so it's important to define those three 00:01:20.319 --> 00:01:24.059 align:start position:0% so it's important to define those three different<00:01:21.069> entities<00:01:21.579> as<00:01:22.299> in<00:01:23.259> different 00:01:24.059 --> 00:01:24.069 align:start position:0% different entities as in different 00:01:24.069 --> 00:01:26.010 align:start position:0% different entities as in different Oracle<00:01:24.639> models<00:01:24.999> than<00:01:25.210> others 00:01:26.010 --> 00:01:26.020 align:start position:0% Oracle models than others 00:01:26.020 --> 00:01:29.340 align:start position:0% Oracle models than others some<00:01:26.409> of<00:01:26.590> those<00:01:26.799> are<00:01:27.100> merged<00:01:27.420> so<00:01:28.420> specifically 00:01:29.340 --> 00:01:29.350 align:start position:0% some of those are merged so specifically 00:01:29.350 --> 00:01:33.179 align:start position:0% some of those are merged so specifically we<00:01:29.799> know<00:01:29.979> that<00:01:30.219> the<00:01:30.520> data<00:01:30.759> is<00:01:31.179> the<00:01:31.770> any<00:01:32.770> piece 00:01:33.179 --> 00:01:33.189 align:start position:0% we know that the data is the any piece 00:01:33.189 --> 00:01:36.679 align:start position:0% we know that the data is the any piece of<00:01:33.340> code<00:01:33.609> that<00:01:33.819> requires<00:01:34.770> the<00:01:35.770> external<00:01:36.520> data 00:01:36.679 --> 00:01:36.689 align:start position:0% of code that requires the external data 00:01:36.689 --> 00:01:39.239 align:start position:0% of code that requires the external data then<00:01:37.689> we<00:01:37.840> have<00:01:37.959> the<00:01:38.139> Oracle<00:01:38.649> and<00:01:38.859> the<00:01:38.920> data 00:01:39.239 --> 00:01:39.249 align:start position:0% then we have the Oracle and the data 00:01:39.249 --> 00:01:41.190 align:start position:0% then we have the Oracle and the data source<00:01:39.639> the<00:01:39.850> data<00:01:40.119> source<00:01:40.630> is<00:01:40.899> not 00:01:41.190 --> 00:01:41.200 align:start position:0% source the data source is not 00:01:41.200 --> 00:01:44.039 align:start position:0% source the data source is not necessarily<00:01:41.829> the<00:01:41.950> same<00:01:42.100> party<00:01:42.819> as<00:01:43.030> the<00:01:43.689> Oracle 00:01:44.039 --> 00:01:44.049 align:start position:0% necessarily the same party as the Oracle 00:01:44.049 --> 00:01:46.679 align:start position:0% necessarily the same party as the Oracle itself<00:01:44.409> it's<00:01:45.130> easy<00:01:45.340> to<00:01:45.490> define<00:01:45.759> the<00:01:45.999> Oracle<00:01:46.479> as 00:01:46.679 --> 00:01:46.689 align:start position:0% itself it's easy to define the Oracle as 00:01:46.689 --> 00:01:49.410 align:start position:0% itself it's easy to define the Oracle as the<00:01:47.139> Oracle<00:01:47.619> is<00:01:47.829> the<00:01:48.130> party<00:01:48.579> that<00:01:48.850> sends<00:01:49.329> the 00:01:49.410 --> 00:01:49.420 align:start position:0% the Oracle is the party that sends the 00:01:49.420 --> 00:01:52.109 align:start position:0% the Oracle is the party that sends the data<00:01:49.539> to<00:01:49.719> the<00:01:49.840> blockchain<00:01:50.700> but<00:01:51.700> the<00:01:51.969> data 00:01:52.109 --> 00:01:52.119 align:start position:0% data to the blockchain but the data 00:01:52.119 --> 00:01:54.870 align:start position:0% data to the blockchain but the data source<00:01:52.509> might<00:01:53.259> as<00:01:53.649> well<00:01:53.859> be<00:01:54.130> a<00:01:54.369> different 00:01:54.870 --> 00:01:54.880 align:start position:0% source might as well be a different 00:01:54.880 --> 00:01:57.149 align:start position:0% source might as well be a different party<00:01:55.329> than<00:01:55.659> the<00:01:55.840> Oracle<00:01:56.200> so<00:01:56.380> we<00:01:56.529> have<00:01:56.619> seen<00:01:56.859> in 00:01:57.149 --> 00:01:57.159 align:start position:0% party than the Oracle so we have seen in 00:01:57.159 --> 00:01:59.219 align:start position:0% party than the Oracle so we have seen in the<00:01:57.310> Thomson<00:01:57.729> Reuters<00:01:57.819> presentation<00:01:58.689> a<00:01:58.810> model 00:01:59.219 --> 00:01:59.229 align:start position:0% the Thomson Reuters presentation a model 00:01:59.229 --> 00:02:01.469 align:start position:0% the Thomson Reuters presentation a model where<00:01:59.469> basically<00:02:00.249> the<00:02:00.490> data<00:02:00.639> source<00:02:01.029> and<00:02:01.270> the 00:02:01.469 --> 00:02:01.479 align:start position:0% where basically the data source and the 00:02:01.479 --> 00:02:04.289 align:start position:0% where basically the data source and the Oracle<00:02:01.840> are<00:02:02.020> the<00:02:02.200> same<00:02:02.380> entity<00:02:02.999> but<00:02:03.999> in 00:02:04.289 --> 00:02:04.299 align:start position:0% Oracle are the same entity but in 00:02:04.299 --> 00:02:07.199 align:start position:0% Oracle are the same entity but in general<00:02:04.749> what<00:02:04.990> we<00:02:05.170> want<00:02:05.380> is<00:02:05.649> be<00:02:06.340> able<00:02:06.819> to<00:02:07.060> reach 00:02:07.199 --> 00:02:07.209 align:start position:0% general what we want is be able to reach 00:02:07.209 --> 00:02:09.749 align:start position:0% general what we want is be able to reach out<00:02:07.450> to<00:02:07.719> any<00:02:07.959> external<00:02:08.410> data<00:02:08.800> sources<00:02:09.190> without 00:02:09.749 --> 00:02:09.759 align:start position:0% out to any external data sources without 00:02:09.759 --> 00:02:11.640 align:start position:0% out to any external data sources without having<00:02:09.970> the<00:02:10.390> data<00:02:10.540> sources<00:02:10.930> to<00:02:11.140> adapt<00:02:11.410> to<00:02:11.440> the 00:02:11.640 --> 00:02:11.650 align:start position:0% having the data sources to adapt to the 00:02:11.650 --> 00:02:13.770 align:start position:0% having the data sources to adapt to the blockchain<00:02:11.860> this<00:02:12.700> is<00:02:12.880> because<00:02:13.210> there<00:02:13.420> are<00:02:13.510> so 00:02:13.770 --> 00:02:13.780 align:start position:0% blockchain this is because there are so 00:02:13.780 --> 00:02:15.570 align:start position:0% blockchain this is because there are so many<00:02:13.840> external<00:02:14.740> data<00:02:14.950> sources 00:02:15.570 --> 00:02:15.580 align:start position:0% many external data sources 00:02:15.580 --> 00:02:17.700 align:start position:0% many external data sources available<00:02:15.880> on<00:02:16.000> the<00:02:16.030> internet<00:02:16.540> that<00:02:17.110> is<00:02:17.320> quite 00:02:17.700 --> 00:02:17.710 align:start position:0% available on the internet that is quite 00:02:17.710 --> 00:02:19.740 align:start position:0% available on the internet that is quite quite<00:02:18.100> unlikely<00:02:18.550> that<00:02:19.030> in<00:02:19.210> the<00:02:19.300> short<00:02:19.570> term 00:02:19.740 --> 00:02:19.750 align:start position:0% quite unlikely that in the short term 00:02:19.750 --> 00:02:21.600 align:start position:0% quite unlikely that in the short term they<00:02:20.020> will<00:02:20.050> add<00:02:20.410> up<00:02:20.590> to<00:02:20.740> the<00:02:20.860> blockchain<00:02:21.070> they 00:02:21.600 --> 00:02:21.610 align:start position:0% they will add up to the blockchain they 00:02:21.610 --> 00:02:24.030 align:start position:0% they will add up to the blockchain they will<00:02:21.790> start<00:02:22.270> signing<00:02:22.540> the<00:02:22.810> data<00:02:22.990> and<00:02:23.320> sending 00:02:24.030 --> 00:02:24.040 align:start position:0% will start signing the data and sending 00:02:24.040 --> 00:02:27.750 align:start position:0% will start signing the data and sending it<00:02:24.250> wherever<00:02:24.760> we<00:02:24.970> need<00:02:25.000> it<00:02:25.180> so<00:02:26.460> the<00:02:27.460> Oracle 00:02:27.750 --> 00:02:27.760 align:start position:0% it wherever we need it so the Oracle 00:02:27.760 --> 00:02:31.160 align:start position:0% it wherever we need it so the Oracle eyes<00:02:27.850> solution<00:02:28.510> is<00:02:28.840> basically<00:02:29.380> the<00:02:29.620> one<00:02:29.800> of 00:02:31.160 --> 00:02:31.170 align:start position:0% eyes solution is basically the one of 00:02:31.170 --> 00:02:33.990 align:start position:0% eyes solution is basically the one of intermediating<00:02:32.170> and<00:02:32.440> so<00:02:33.190> ironically<00:02:33.370> we 00:02:33.990 --> 00:02:34.000 align:start position:0% intermediating and so ironically we 00:02:34.000 --> 00:02:36.570 align:start position:0% intermediating and so ironically we could<00:02:34.210> say<00:02:34.390> that<00:02:34.600> Oracle<00:02:34.960> eyes<00:02:35.080> is<00:02:35.440> a<00:02:35.830> new<00:02:36.040> type 00:02:36.570 --> 00:02:36.580 align:start position:0% could say that Oracle eyes is a new type 00:02:36.580 --> 00:02:39.270 align:start position:0% could say that Oracle eyes is a new type of<00:02:36.610> intermediary<00:02:37.600> in<00:02:38.020> a<00:02:38.200> word<00:02:38.410> that<00:02:38.680> is<00:02:38.920> trying 00:02:39.270 --> 00:02:39.280 align:start position:0% of intermediary in a word that is trying 00:02:39.280 --> 00:02:42.060 align:start position:0% of intermediary in a word that is trying to<00:02:39.370> get<00:02:39.580> rid<00:02:39.790> of<00:02:39.820> them<00:02:40.110> so<00:02:41.110> we<00:02:41.350> see<00:02:41.500> on<00:02:41.590> one<00:02:41.800> side 00:02:42.060 --> 00:02:42.070 align:start position:0% to get rid of them so we see on one side 00:02:42.070 --> 00:02:45.240 align:start position:0% to get rid of them so we see on one side web<00:02:42.460> api<00:02:42.850> so<00:02:43.390> any<00:02:43.630> possible<00:02:44.500> existing<00:02:45.040> data 00:02:45.240 --> 00:02:45.250 align:start position:0% web api so any possible existing data 00:02:45.250 --> 00:02:47.610 align:start position:0% web api so any possible existing data source<00:02:45.610> and<00:02:45.850> on<00:02:46.360> the<00:02:46.540> other<00:02:46.630> blockchains<00:02:47.440> in 00:02:47.610 --> 00:02:47.620 align:start position:0% source and on the other blockchains in 00:02:47.620 --> 00:02:49.860 align:start position:0% source and on the other blockchains in general<00:02:48.040> so<00:02:48.730> our<00:02:48.940> client<00:02:49.360> stays<00:02:49.540> in<00:02:49.750> the 00:02:49.860 --> 00:02:49.870 align:start position:0% general so our client stays in the 00:02:49.870 --> 00:02:51.960 align:start position:0% general so our client stays in the middle<00:02:50.230> and<00:02:50.440> tries<00:02:50.860> to<00:02:50.890> make<00:02:51.520> the<00:02:51.760> two 00:02:51.960 --> 00:02:51.970 align:start position:0% middle and tries to make the two 00:02:51.970 --> 00:02:54.180 align:start position:0% middle and tries to make the two different<00:02:52.420> words<00:02:52.690> communicate<00:02:53.470> so<00:02:53.740> different 00:02:54.180 --> 00:02:54.190 align:start position:0% different words communicate so different 00:02:54.190 --> 00:02:56.580 align:start position:0% different words communicate so different context<00:02:54.640> is<00:02:54.820> to<00:02:55.000> communicate<00:02:55.660> and<00:02:56.350> exchange 00:02:56.580 --> 00:02:56.590 align:start position:0% context is to communicate and exchange 00:02:56.590 --> 00:02:59.340 align:start position:0% context is to communicate and exchange data<00:02:56.980> so<00:02:57.700> this<00:02:57.850> is<00:02:58.090> what<00:02:58.510> we<00:02:58.660> call<00:02:58.900> a<00:02:58.930> data 00:02:59.340 --> 00:02:59.350 align:start position:0% data so this is what we call a data 00:02:59.350 --> 00:03:03.390 align:start position:0% data so this is what we call a data transport<00:02:59.890> layer<00:03:00.840> we<00:03:01.840> have<00:03:01.930> seen<00:03:02.470> a<00:03:02.680> lot<00:03:02.950> in 00:03:03.390 --> 00:03:03.400 align:start position:0% transport layer we have seen a lot in 00:03:03.400 --> 00:03:04.949 align:start position:0% transport layer we have seen a lot in previous<00:03:03.760> presentation<00:03:04.390> the<00:03:04.510> problem<00:03:04.840> of 00:03:04.949 --> 00:03:04.959 align:start position:0% previous presentation the problem of 00:03:04.959 --> 00:03:06.750 align:start position:0% previous presentation the problem of trust<00:03:05.260> so<00:03:05.800> of<00:03:05.920> course<00:03:06.160> having<00:03:06.550> a<00:03:06.640> new 00:03:06.750 --> 00:03:06.760 align:start position:0% trust so of course having a new 00:03:06.760 --> 00:03:09.210 align:start position:0% trust so of course having a new intermediary<00:03:07.330> implies<00:03:08.050> some<00:03:08.620> trust<00:03:08.950> lines 00:03:09.210 --> 00:03:09.220 align:start position:0% intermediary implies some trust lines 00:03:09.220 --> 00:03:11.730 align:start position:0% intermediary implies some trust lines that<00:03:09.520> we<00:03:09.670> have<00:03:09.760> to<00:03:09.910> open<00:03:10.209> we<00:03:11.140> don't<00:03:11.320> want<00:03:11.530> to 00:03:11.730 --> 00:03:11.740 align:start position:0% that we have to open we don't want to 00:03:11.740 --> 00:03:14.250 align:start position:0% that we have to open we don't want to trust<00:03:12.010> a<00:03:12.220> small<00:03:12.459> startup<00:03:12.910> of<00:03:13.120> 10<00:03:13.390> people<00:03:13.780> so 00:03:14.250 --> 00:03:14.260 align:start position:0% trust a small startup of 10 people so 00:03:14.260 --> 00:03:17.310 align:start position:0% trust a small startup of 10 people so this<00:03:14.500> is<00:03:14.709> why<00:03:14.920> we<00:03:15.490> add<00:03:15.670> to<00:03:16.030> provide<00:03:16.390> some<00:03:16.959> kind 00:03:17.310 --> 00:03:17.320 align:start position:0% this is why we add to provide some kind 00:03:17.320 --> 00:03:19.800 align:start position:0% this is why we add to provide some kind of<00:03:17.560> authenticity<00:03:17.830> pros<00:03:18.550> so<00:03:19.180> a<00:03:19.209> proof<00:03:19.510> of<00:03:19.660> the 00:03:19.800 --> 00:03:19.810 align:start position:0% of authenticity pros so a proof of the 00:03:19.810 --> 00:03:22.050 align:start position:0% of authenticity pros so a proof of the fact<00:03:20.050> that<00:03:20.170> the<00:03:20.530> data<00:03:20.769> we<00:03:21.220> are<00:03:21.310> sending<00:03:21.550> to<00:03:21.730> the 00:03:22.050 --> 00:03:22.060 align:start position:0% fact that the data we are sending to the 00:03:22.060 --> 00:03:23.759 align:start position:0% fact that the data we are sending to the blockchain<00:03:22.269> application<00:03:22.959> is<00:03:23.140> indeed 00:03:23.759 --> 00:03:23.769 align:start position:0% blockchain application is indeed 00:03:23.769 --> 00:03:26.400 align:start position:0% blockchain application is indeed authentic<00:03:24.430> as<00:03:24.640> reported<00:03:25.570> by<00:03:25.720> the<00:03:25.780> external 00:03:26.400 --> 00:03:26.410 align:start position:0% authentic as reported by the external 00:03:26.410 --> 00:03:29.460 align:start position:0% authentic as reported by the external data<00:03:26.590> source<00:03:26.920> and<00:03:27.040> not<00:03:27.550> tampered<00:03:28.180> with<00:03:28.209> by<00:03:28.810> the 00:03:29.460 --> 00:03:29.470 align:start position:0% data source and not tampered with by the 00:03:29.470 --> 00:03:31.320 align:start position:0% data source and not tampered with by the intermediary<00:03:30.280> which<00:03:30.459> is<00:03:30.610> authorized<00:03:31.000> in<00:03:31.030> that 00:03:31.320 --> 00:03:31.330 align:start position:0% intermediary which is authorized in that 00:03:31.330 --> 00:03:35.190 align:start position:0% intermediary which is authorized in that case<00:03:31.650> so<00:03:32.650> in<00:03:32.860> order<00:03:33.010> to<00:03:33.190> do<00:03:33.459> that<00:03:33.640> we<00:03:34.120> send<00:03:34.900> the 00:03:35.190 --> 00:03:35.200 align:start position:0% case so in order to do that we send the 00:03:35.200 --> 00:03:37.259 align:start position:0% case so in order to do that we send the blockchain<00:03:35.440> not<00:03:35.830> just<00:03:36.070> the<00:03:36.250> result<00:03:36.730> that 00:03:37.259 --> 00:03:37.269 align:start position:0% blockchain not just the result that 00:03:37.269 --> 00:03:39.180 align:start position:0% blockchain not just the result that comes<00:03:37.540> from<00:03:37.750> the<00:03:37.870> external<00:03:38.230> data<00:03:38.380> source<00:03:38.739> but 00:03:39.180 --> 00:03:39.190 align:start position:0% comes from the external data source but 00:03:39.190 --> 00:03:41.340 align:start position:0% comes from the external data source but also<00:03:39.430> the<00:03:39.730> so-called<00:03:39.910> authenticity<00:03:40.660> profit 00:03:41.340 --> 00:03:41.350 align:start position:0% also the so-called authenticity profit 00:03:41.350 --> 00:03:43.650 align:start position:0% also the so-called authenticity profit so<00:03:42.010> authenticity<00:03:42.340> proofs<00:03:42.820> are<00:03:43.060> a<00:03:43.120> very 00:03:43.650 --> 00:03:43.660 align:start position:0% so authenticity proofs are a very 00:03:43.660 --> 00:03:47.310 align:start position:0% so authenticity proofs are a very generic<00:03:43.980> concept<00:03:44.980> what<00:03:45.940> we<00:03:45.970> want<00:03:46.390> to<00:03:46.510> get<00:03:46.750> is 00:03:47.310 --> 00:03:47.320 align:start position:0% generic concept what we want to get is 00:03:47.320 --> 00:03:49.710 align:start position:0% generic concept what we want to get is just<00:03:47.680> some<00:03:48.010> kind<00:03:48.280> of<00:03:48.400> evidence<00:03:48.970> of<00:03:49.209> the<00:03:49.540> fact 00:03:49.710 --> 00:03:49.720 align:start position:0% just some kind of evidence of the fact 00:03:49.720 --> 00:03:52.320 align:start position:0% just some kind of evidence of the fact that<00:03:49.930> the<00:03:50.769> data<00:03:51.040> fetching<00:03:51.610> from<00:03:51.760> the<00:03:51.940> external 00:03:52.320 --> 00:03:52.330 align:start position:0% that the data fetching from the external 00:03:52.330 --> 00:03:56.220 align:start position:0% that the data fetching from the external data<00:03:52.480> source<00:03:52.870> is<00:03:53.100> indeed<00:03:54.100> honest<00:03:55.060> is<00:03:55.330> not<00:03:55.780> that 00:03:56.220 --> 00:03:56.230 align:start position:0% data source is indeed honest is not that 00:03:56.230 --> 00:03:57.960 align:start position:0% data source is indeed honest is not that we<00:03:56.380> want<00:03:56.560> to<00:03:56.680> know<00:03:56.830> that<00:03:57.040> the<00:03:57.220> operator<00:03:57.610> is 00:03:57.960 --> 00:03:57.970 align:start position:0% we want to know that the operator is 00:03:57.970 --> 00:04:01.500 align:start position:0% we want to know that the operator is behaving<00:03:58.540> honestly<00:03:59.370> this<00:04:00.370> is<00:04:00.580> trivial<00:04:01.000> when 00:04:01.500 --> 00:04:01.510 align:start position:0% behaving honestly this is trivial when 00:04:01.510 --> 00:04:04.070 align:start position:0% behaving honestly this is trivial when the<00:04:01.870> data<00:04:02.200> source<00:04:02.530> signs<00:04:02.920> the<00:04:03.160> data 00:04:04.070 --> 00:04:04.080 align:start position:0% the data source signs the data 00:04:04.080 --> 00:04:05.790 align:start position:0% the data source signs the data unfortunately<00:04:05.080> there<00:04:05.260> are<00:04:05.380> so<00:04:05.620> many 00:04:05.790 --> 00:04:05.800 align:start position:0% unfortunately there are so many 00:04:05.800 --> 00:04:08.100 align:start position:0% unfortunately there are so many different<00:04:06.340> standard<00:04:06.900> standards<00:04:07.900> and 00:04:08.100 --> 00:04:08.110 align:start position:0% different standard standards and 00:04:08.110 --> 00:04:10.979 align:start position:0% different standard standards and proposals<00:04:09.070> to<00:04:09.519> sign<00:04:09.760> data<00:04:10.030> on<00:04:10.180> the<00:04:10.330> Internet 00:04:10.979 --> 00:04:10.989 align:start position:0% proposals to sign data on the Internet 00:04:10.989 --> 00:04:13.410 align:start position:0% proposals to sign data on the Internet that<00:04:11.320> pretty<00:04:11.739> much<00:04:12.010> none<00:04:12.370> of<00:04:12.549> them<00:04:12.790> is<00:04:13.120> being 00:04:13.410 --> 00:04:13.420 align:start position:0% that pretty much none of them is being 00:04:13.420 --> 00:04:16.199 align:start position:0% that pretty much none of them is being widely<00:04:13.630> used<00:04:14.670> hopefully<00:04:15.670> this<00:04:15.850> will<00:04:16.000> be 00:04:16.199 --> 00:04:16.209 align:start position:0% widely used hopefully this will be 00:04:16.209 --> 00:04:18.539 align:start position:0% widely used hopefully this will be solved<00:04:16.600> in<00:04:16.720> the<00:04:16.900> future<00:04:17.200> years<00:04:17.470> but<00:04:17.919> in<00:04:18.370> the 00:04:18.539 --> 00:04:18.549 align:start position:0% solved in the future years but in the 00:04:18.549 --> 00:04:20.460 align:start position:0% solved in the future years but in the meantime<00:04:18.729> we<00:04:19.150> know<00:04:19.299> already<00:04:19.510> that<00:04:19.810> some<00:04:20.229> data 00:04:20.460 --> 00:04:20.470 align:start position:0% meantime we know already that some data 00:04:20.470 --> 00:04:23.400 align:start position:0% meantime we know already that some data sources<00:04:20.919> made<00:04:21.459> a<00:04:21.700> choice<00:04:21.970> so<00:04:22.780> for<00:04:22.960> example 00:04:23.400 --> 00:04:23.410 align:start position:0% sources made a choice so for example 00:04:23.410 --> 00:04:26.610 align:start position:0% sources made a choice so for example there<00:04:23.560> is<00:04:23.590> an<00:04:23.919> IETF<00:04:24.960> proposal<00:04:25.960> that<00:04:26.229> is<00:04:26.410> being 00:04:26.610 --> 00:04:26.620 align:start position:0% there is an IETF proposal that is being 00:04:26.620 --> 00:04:29.020 align:start position:0% there is an IETF proposal that is being discussed<00:04:27.100> for<00:04:27.250> several<00:04:27.940> years 00:04:29.020 --> 00:04:29.030 align:start position:0% discussed for several years 00:04:29.030 --> 00:04:31.390 align:start position:0% discussed for several years which<00:04:29.180> is<00:04:29.330> being<00:04:29.510> called<00:04:29.930> cabbage<00:04:30.860> HTTP 00:04:31.390 --> 00:04:31.400 align:start position:0% which is being called cabbage HTTP 00:04:31.400 --> 00:04:34.120 align:start position:0% which is being called cabbage HTTP signatures<00:04:31.880> which<00:04:32.480> is<00:04:32.690> that<00:04:32.930> is<00:04:33.170> seventy 00:04:34.120 --> 00:04:34.130 align:start position:0% signatures which is that is seventy 00:04:34.130 --> 00:04:37.120 align:start position:0% signatures which is that is seventy duration<00:04:34.550> now<00:04:34.990> this<00:04:35.990> is<00:04:36.140> one<00:04:36.380> possible<00:04:36.890> way<00:04:36.950> to 00:04:37.120 --> 00:04:37.130 align:start position:0% duration now this is one possible way to 00:04:37.130 --> 00:04:39.130 align:start position:0% duration now this is one possible way to sign<00:04:37.520> the<00:04:37.670> data<00:04:37.850> for<00:04:38.090> the<00:04:38.180> data<00:04:38.360> source<00:04:38.600> there 00:04:39.130 --> 00:04:39.140 align:start position:0% sign the data for the data source there 00:04:39.140 --> 00:04:41.140 align:start position:0% sign the data for the data source there are<00:04:39.230> already<00:04:39.380> several<00:04:39.890> data<00:04:40.370> sources<00:04:40.460> signing 00:04:41.140 --> 00:04:41.150 align:start position:0% are already several data sources signing 00:04:41.150 --> 00:04:43.600 align:start position:0% are already several data sources signing the<00:04:41.240> data<00:04:41.570> in<00:04:41.660> this<00:04:41.780> way<00:04:41.920> Oracle<00:04:42.920> I<00:04:42.980> supports 00:04:43.600 --> 00:04:43.610 align:start position:0% the data in this way Oracle I supports 00:04:43.610 --> 00:04:45.790 align:start position:0% the data in this way Oracle I supports it<00:04:43.760> so<00:04:44.120> it<00:04:44.240> means<00:04:44.510> that<00:04:44.780> if<00:04:45.080> the<00:04:45.320> data<00:04:45.500> source 00:04:45.790 --> 00:04:45.800 align:start position:0% it so it means that if the data source 00:04:45.800 --> 00:04:48.640 align:start position:0% it so it means that if the data source you<00:04:45.950> choose<00:04:46.250> on<00:04:46.630> is<00:04:47.630> signing<00:04:48.200> the<00:04:48.320> data<00:04:48.500> in 00:04:48.640 --> 00:04:48.650 align:start position:0% you choose on is signing the data in 00:04:48.650 --> 00:04:50.740 align:start position:0% you choose on is signing the data in this<00:04:48.770> way<00:04:48.830> you<00:04:49.580> can<00:04:49.760> leverage<00:04:50.000> the<00:04:50.420> Oracle 00:04:50.740 --> 00:04:50.750 align:start position:0% this way you can leverage the Oracle 00:04:50.750 --> 00:04:53.620 align:start position:0% this way you can leverage the Oracle eyes<00:04:50.870> data<00:04:51.620> transport<00:04:52.040> layer<00:04:52.310> and<00:04:52.670> connect 00:04:53.620 --> 00:04:53.630 align:start position:0% eyes data transport layer and connect 00:04:53.630 --> 00:04:56.260 align:start position:0% eyes data transport layer and connect this<00:04:53.810> Web<00:04:54.410> API<00:04:54.920> to<00:04:55.460> your<00:04:55.610> smart<00:04:55.910> contrast 00:04:56.260 --> 00:04:56.270 align:start position:0% this Web API to your smart contrast 00:04:56.270 --> 00:04:58.960 align:start position:0% this Web API to your smart contrast application<00:04:56.840> straightaway<00:04:57.500> but<00:04:58.370> in<00:04:58.550> general 00:04:58.960 --> 00:04:58.970 align:start position:0% application straightaway but in general 00:04:58.970 --> 00:05:01.720 align:start position:0% application straightaway but in general Web<00:04:59.390> API<00:04:59.720> eyes<00:04:59.840> do<00:05:00.200> not<00:05:00.440> sign<00:05:00.890> the<00:05:01.130> data<00:05:01.340> and 00:05:01.720 --> 00:05:01.730 align:start position:0% Web API eyes do not sign the data and 00:05:01.730 --> 00:05:03.100 align:start position:0% Web API eyes do not sign the data and this<00:05:02.150> is<00:05:02.300> why<00:05:02.480> we<00:05:02.660> need<00:05:02.810> to<00:05:02.960> leverage 00:05:03.100 --> 00:05:03.110 align:start position:0% this is why we need to leverage 00:05:03.110 --> 00:05:05.170 align:start position:0% this is why we need to leverage different<00:05:03.440> techniques<00:05:03.980> we<00:05:04.250> have<00:05:04.340> seen<00:05:04.610> what 00:05:05.170 --> 00:05:05.180 align:start position:0% different techniques we have seen what 00:05:05.180 --> 00:05:08.920 align:start position:0% different techniques we have seen what chain<00:05:05.990> link<00:05:06.230> does<00:05:06.470> with<00:05:07.420> the<00:05:08.420> Town<00:05:08.720> Crier 00:05:08.920 --> 00:05:08.930 align:start position:0% chain link does with the Town Crier 00:05:08.930 --> 00:05:11.770 align:start position:0% chain link does with the Town Crier project<00:05:09.470> which<00:05:09.620> is<00:05:09.770> based<00:05:09.980> on<00:05:10.190> Intel<00:05:10.730> SGX<00:05:10.910> this 00:05:11.770 --> 00:05:11.780 align:start position:0% project which is based on Intel SGX this 00:05:11.780 --> 00:05:13.930 align:start position:0% project which is based on Intel SGX this is<00:05:11.930> one<00:05:12.140> possible<00:05:12.620> technology<00:05:12.890> which<00:05:13.490> we<00:05:13.760> can 00:05:13.930 --> 00:05:13.940 align:start position:0% is one possible technology which we can 00:05:13.940 --> 00:05:16.440 align:start position:0% is one possible technology which we can use<00:05:14.150> so<00:05:14.690> trusted<00:05:15.110> computing<00:05:15.500> by<00:05:15.860> Intel<00:05:16.220> SGX 00:05:16.440 --> 00:05:16.450 align:start position:0% use so trusted computing by Intel SGX 00:05:16.450 --> 00:05:19.000 align:start position:0% use so trusted computing by Intel SGX but<00:05:17.450> there<00:05:17.630> are<00:05:17.690> many<00:05:17.930> others<00:05:18.350> techniques 00:05:19.000 --> 00:05:19.010 align:start position:0% but there are many others techniques 00:05:19.010 --> 00:05:21.730 align:start position:0% but there are many others techniques that<00:05:19.280> can<00:05:19.490> be<00:05:19.550> used<00:05:20.380> Oracle<00:05:21.380> eyes<00:05:21.470> at<00:05:21.620> the 00:05:21.730 --> 00:05:21.740 align:start position:0% that can be used Oracle eyes at the 00:05:21.740 --> 00:05:23.710 align:start position:0% that can be used Oracle eyes at the moment<00:05:21.860> is<00:05:22.250> using<00:05:22.790> some<00:05:23.090> sandboxing 00:05:23.710 --> 00:05:23.720 align:start position:0% moment is using some sandboxing 00:05:23.720 --> 00:05:26.110 align:start position:0% moment is using some sandboxing techniques<00:05:24.200> which<00:05:24.680> are<00:05:24.890> backed<00:05:25.220> by<00:05:25.370> software 00:05:26.110 --> 00:05:26.120 align:start position:0% techniques which are backed by software 00:05:26.120 --> 00:05:28.780 align:start position:0% techniques which are backed by software guarantees<00:05:26.630> such<00:05:27.080> as<00:05:27.290> TLS<00:05:27.620> notary<00:05:28.040> and<00:05:28.220> some 00:05:28.780 --> 00:05:28.790 align:start position:0% guarantees such as TLS notary and some 00:05:28.790 --> 00:05:31.120 align:start position:0% guarantees such as TLS notary and some others<00:05:29.150> that<00:05:29.180> are<00:05:29.450> backed<00:05:29.750> by<00:05:30.130> hardware 00:05:31.120 --> 00:05:31.130 align:start position:0% others that are backed by hardware 00:05:31.130 --> 00:05:33.490 align:start position:0% others that are backed by hardware techniques<00:05:31.760> like<00:05:32.210> Intel<00:05:32.900> SGX 00:05:33.490 --> 00:05:33.500 align:start position:0% techniques like Intel SGX 00:05:33.500 --> 00:05:37.150 align:start position:0% techniques like Intel SGX or<00:05:33.830> the<00:05:34.430> Qualcomm<00:05:35.030> teehee<00:05:35.800> legend<00:05:36.800> analyst 00:05:37.150 --> 00:05:37.160 align:start position:0% or the Qualcomm teehee legend analyst 00:05:37.160 --> 00:05:38.590 align:start position:0% or the Qualcomm teehee legend analyst attestation<00:05:37.610> that<00:05:37.880> we<00:05:38.120> have<00:05:38.210> seen<00:05:38.390> yesterday 00:05:38.590 --> 00:05:38.600 align:start position:0% attestation that we have seen yesterday 00:05:38.600 --> 00:05:40.960 align:start position:0% attestation that we have seen yesterday here<00:05:39.320> with<00:05:39.530> Nikolas<00:05:39.980> from<00:05:40.190> Letcher<00:05:40.490> and<00:05:40.760> many 00:05:40.960 --> 00:05:40.970 align:start position:0% here with Nikolas from Letcher and many 00:05:40.970 --> 00:05:43.900 align:start position:0% here with Nikolas from Letcher and many others<00:05:41.300> so<00:05:42.310> basically<00:05:43.310> there<00:05:43.580> are<00:05:43.640> many 00:05:43.900 --> 00:05:43.910 align:start position:0% others so basically there are many 00:05:43.910 --> 00:05:46.750 align:start position:0% others so basically there are many different<00:05:44.450> ways<00:05:44.690> we<00:05:45.470> can<00:05:45.740> give<00:05:46.160> this<00:05:46.340> kind<00:05:46.550> of 00:05:46.750 --> 00:05:46.760 align:start position:0% different ways we can give this kind of 00:05:46.760 --> 00:05:49.150 align:start position:0% different ways we can give this kind of evidence<00:05:47.480> and<00:05:47.720> this<00:05:47.810> kind<00:05:48.050> of<00:05:48.140> proof<00:05:48.410> and<00:05:48.650> what 00:05:49.150 --> 00:05:49.160 align:start position:0% evidence and this kind of proof and what 00:05:49.160 --> 00:05:51.760 align:start position:0% evidence and this kind of proof and what our<00:05:49.280> class<00:05:49.550> is<00:05:49.730> doing<00:05:49.880> is<00:05:50.240> not<00:05:50.540> using<00:05:51.140> a<00:05:51.320> single 00:05:51.760 --> 00:05:51.770 align:start position:0% our class is doing is not using a single 00:05:51.770 --> 00:05:52.920 align:start position:0% our class is doing is not using a single technology<00:05:52.160> to<00:05:52.550> do<00:05:52.700> it 00:05:52.920 --> 00:05:52.930 align:start position:0% technology to do it 00:05:52.930 --> 00:05:55.930 align:start position:0% technology to do it as<00:05:53.930> as<00:05:54.350> we<00:05:54.530> will<00:05:54.740> see<00:05:54.890> in<00:05:54.950> a<00:05:55.040> minute<00:05:55.160> we<00:05:55.610> believe 00:05:55.930 --> 00:05:55.940 align:start position:0% as as we will see in a minute we believe 00:05:55.940 --> 00:05:58.510 align:start position:0% as as we will see in a minute we believe that<00:05:56.180> that<00:05:56.870> will<00:05:57.110> be<00:05:57.260> a<00:05:57.290> quite<00:05:58.130> a<00:05:58.160> weak 00:05:58.510 --> 00:05:58.520 align:start position:0% that that will be a quite a weak 00:05:58.520 --> 00:06:01.750 align:start position:0% that that will be a quite a weak architecture<00:05:59.180> so<00:06:00.340> basically<00:06:01.340> what<00:06:01.550> we<00:06:01.670> are 00:06:01.750 --> 00:06:01.760 align:start position:0% architecture so basically what we are 00:06:01.760 --> 00:06:03.970 align:start position:0% architecture so basically what we are saying<00:06:01.940> is<00:06:02.240> that<00:06:02.300> when<00:06:02.900> the<00:06:03.140> data<00:06:03.290> source<00:06:03.680> does 00:06:03.970 --> 00:06:03.980 align:start position:0% saying is that when the data source does 00:06:03.980 --> 00:06:06.700 align:start position:0% saying is that when the data source does not<00:06:04.010> sign<00:06:04.580> the<00:06:04.760> data<00:06:04.970> then<00:06:05.780> we<00:06:05.960> need<00:06:06.350> to<00:06:06.530> use<00:06:06.680> a 00:06:06.700 --> 00:06:06.710 align:start position:0% not sign the data then we need to use a 00:06:06.710 --> 00:06:09.040 align:start position:0% not sign the data then we need to use a different<00:06:07.100> technology<00:06:07.460> but<00:06:08.360> which<00:06:08.600> one<00:06:08.870> do 00:06:09.040 --> 00:06:09.050 align:start position:0% different technology but which one do 00:06:09.050 --> 00:06:09.570 align:start position:0% different technology but which one do you<00:06:09.170> choose 00:06:09.570 --> 00:06:09.580 align:start position:0% you choose 00:06:09.580 --> 00:06:12.060 align:start position:0% you choose well<00:06:10.580> this<00:06:10.760> is<00:06:10.880> a<00:06:10.910> complicated<00:06:11.330> question 00:06:12.060 --> 00:06:12.070 align:start position:0% well this is a complicated question 00:06:12.070 --> 00:06:14.350 align:start position:0% well this is a complicated question because<00:06:13.070> every<00:06:13.550> time<00:06:13.730> we<00:06:13.910> use<00:06:13.940> the<00:06:14.180> technology 00:06:14.350 --> 00:06:14.360 align:start position:0% because every time we use the technology 00:06:14.360 --> 00:06:16.810 align:start position:0% because every time we use the technology we<00:06:15.080> are<00:06:15.200> really<00:06:15.470> trusting<00:06:15.950> the<00:06:16.130> at<00:06:16.340> the<00:06:16.550> stator 00:06:16.810 --> 00:06:16.820 align:start position:0% we are really trusting the at the stator 00:06:16.820 --> 00:06:19.210 align:start position:0% we are really trusting the at the stator so<00:06:17.480> the<00:06:17.660> at<00:06:17.810> the<00:06:17.990> stator<00:06:18.260> is<00:06:18.590> basically 00:06:19.210 --> 00:06:19.220 align:start position:0% so the at the stator is basically 00:06:19.220 --> 00:06:22.120 align:start position:0% so the at the stator is basically whoever<00:06:19.780> designs<00:06:20.780> the<00:06:21.020> technology<00:06:21.620> whoever 00:06:22.120 --> 00:06:22.130 align:start position:0% whoever designs the technology whoever 00:06:22.130 --> 00:06:24.370 align:start position:0% whoever designs the technology whoever is<00:06:22.430> providing<00:06:23.060> the<00:06:23.180> technology<00:06:23.480> so<00:06:24.170> think 00:06:24.370 --> 00:06:24.380 align:start position:0% is providing the technology so think 00:06:24.380 --> 00:06:27.190 align:start position:0% is providing the technology so think about<00:06:24.470> the<00:06:24.890> Intel<00:06:25.310> SGX<00:06:25.520> case<00:06:26.060> so<00:06:26.780> on<00:06:26.990> paper 00:06:27.190 --> 00:06:27.200 align:start position:0% about the Intel SGX case so on paper 00:06:27.200 --> 00:06:30.220 align:start position:0% about the Intel SGX case so on paper Intel<00:06:27.770> SGX<00:06:27.920> is<00:06:28.610> very<00:06:28.910> safe<00:06:29.150> for<00:06:29.450> sure<00:06:29.720> is<00:06:30.050> one 00:06:30.220 --> 00:06:30.230 align:start position:0% Intel SGX is very safe for sure is one 00:06:30.230 --> 00:06:32.020 align:start position:0% Intel SGX is very safe for sure is one of<00:06:30.380> the<00:06:30.530> most<00:06:30.770> interesting<00:06:31.340> and<00:06:31.520> flexible 00:06:32.020 --> 00:06:32.030 align:start position:0% of the most interesting and flexible 00:06:32.030 --> 00:06:34.030 align:start position:0% of the most interesting and flexible technologies<00:06:32.690> for<00:06:32.960> trusted<00:06:33.350> computing<00:06:33.680> that 00:06:34.030 --> 00:06:34.040 align:start position:0% technologies for trusted computing that 00:06:34.040 --> 00:06:36.850 align:start position:0% technologies for trusted computing that we<00:06:34.100> have<00:06:34.340> available<00:06:35.030> on<00:06:35.330> the<00:06:35.450> market<00:06:35.840> but<00:06:36.590> at 00:06:36.850 --> 00:06:36.860 align:start position:0% we have available on the market but at 00:06:36.860 --> 00:06:38.980 align:start position:0% we have available on the market but at the<00:06:37.040> end<00:06:37.070> of<00:06:37.250> the<00:06:37.400> day<00:06:37.550> we<00:06:38.090> need<00:06:38.300> to<00:06:38.690> trust 00:06:38.980 --> 00:06:38.990 align:start position:0% the end of the day we need to trust 00:06:38.990 --> 00:06:41.950 align:start position:0% the end of the day we need to trust Intel<00:06:39.560> because<00:06:40.130> we<00:06:40.580> cannot<00:06:40.910> verify<00:06:40.970> in<00:06:41.690> our 00:06:41.950 --> 00:06:41.960 align:start position:0% Intel because we cannot verify in our 00:06:41.960 --> 00:06:42.790 align:start position:0% Intel because we cannot verify in our homes 00:06:42.790 --> 00:06:42.800 align:start position:0% homes 00:06:42.800 --> 00:06:45.760 align:start position:0% homes if<00:06:42.889> the<00:06:43.460> chip<00:06:44.090> for<00:06:44.300> example<00:06:44.840> is<00:06:45.139> the<00:06:45.440> CPU 00:06:45.760 --> 00:06:45.770 align:start position:0% if the chip for example is the CPU 00:06:45.770 --> 00:06:48.070 align:start position:0% if the chip for example is the CPU package<00:06:46.220> is<00:06:47.150> really<00:06:47.509> doing<00:06:47.750> what<00:06:47.900> it<00:06:47.990> is 00:06:48.070 --> 00:06:48.080 align:start position:0% package is really doing what it is 00:06:48.080 --> 00:06:50.589 align:start position:0% package is really doing what it is supposed<00:06:48.500> to<00:06:48.590> do<00:06:48.770> we<00:06:49.310> cannot<00:06:49.610> really<00:06:49.849> know<00:06:50.180> if 00:06:50.589 --> 00:06:50.599 align:start position:0% supposed to do we cannot really know if 00:06:50.599 --> 00:06:52.210 align:start position:0% supposed to do we cannot really know if the<00:06:51.050> signature<00:06:51.560> coming<00:06:51.800> from<00:06:51.979> the 00:06:52.210 --> 00:06:52.220 align:start position:0% the signature coming from the 00:06:52.220 --> 00:06:55.029 align:start position:0% the signature coming from the attestation<00:06:52.550> services<00:06:53.270> is<00:06:53.509> done<00:06:54.139> correctly 00:06:55.029 --> 00:06:55.039 align:start position:0% attestation services is done correctly 00:06:55.039 --> 00:06:58.240 align:start position:0% attestation services is done correctly as<00:06:55.370> intended<00:06:56.270> and<00:06:56.479> in<00:06:57.020> general<00:06:57.440> every<00:06:57.770> time<00:06:57.979> we 00:06:58.240 --> 00:06:58.250 align:start position:0% as intended and in general every time we 00:06:58.250 --> 00:07:00.249 align:start position:0% as intended and in general every time we use<00:06:58.280> one<00:06:59.030> of<00:06:59.060> those<00:06:59.330> technology<00:06:59.930> we<00:07:00.229> are 00:07:00.249 --> 00:07:00.259 align:start position:0% use one of those technology we are 00:07:00.259 --> 00:07:02.499 align:start position:0% use one of those technology we are always<00:07:00.590> trusting<00:07:01.310> somebody<00:07:01.520> so<00:07:02.090> Internet 00:07:02.499 --> 00:07:02.509 align:start position:0% always trusting somebody so Internet 00:07:02.509 --> 00:07:04.570 align:start position:0% always trusting somebody so Internet even<00:07:02.629> in<00:07:02.870> the<00:07:02.960> case<00:07:03.139> of<00:07:03.470> the<00:07:03.889> ledger<00:07:04.069> proof<00:07:04.400> for 00:07:04.570 --> 00:07:04.580 align:start position:0% even in the case of the ledger proof for 00:07:04.580 --> 00:07:06.670 align:start position:0% even in the case of the ledger proof for example<00:07:05.000> we<00:07:05.150> are<00:07:05.180> trusting<00:07:05.629> ledger<00:07:05.840> in<00:07:06.349> the 00:07:06.670 --> 00:07:06.680 align:start position:0% example we are trusting ledger in the 00:07:06.680 --> 00:07:08.290 align:start position:0% example we are trusting ledger in the case<00:07:06.860> of<00:07:07.069> the<00:07:07.220> Android<00:07:07.490> proof<00:07:07.759> we<00:07:08.270> are 00:07:08.290 --> 00:07:08.300 align:start position:0% case of the Android proof we are 00:07:08.300 --> 00:07:10.659 align:start position:0% case of the Android proof we are trusting<00:07:08.810> a<00:07:08.840> Qualcomm<00:07:09.560> and<00:07:09.889> Google<00:07:10.310> for<00:07:10.490> sure 00:07:10.659 --> 00:07:10.669 align:start position:0% trusting a Qualcomm and Google for sure 00:07:10.669 --> 00:07:13.570 align:start position:0% trusting a Qualcomm and Google for sure so<00:07:11.539> basically<00:07:11.569> by<00:07:12.289> using<00:07:12.530> those<00:07:13.190> technologies 00:07:13.570 --> 00:07:13.580 align:start position:0% so basically by using those technologies 00:07:13.580 --> 00:07:17.409 align:start position:0% so basically by using those technologies to<00:07:14.120> prove<00:07:14.569> the<00:07:15.139> authenticity<00:07:15.440> of<00:07:16.099> the<00:07:16.430> data<00:07:16.610> we 00:07:17.409 --> 00:07:17.419 align:start position:0% to prove the authenticity of the data we 00:07:17.419 --> 00:07:20.020 align:start position:0% to prove the authenticity of the data we are<00:07:17.509> not<00:07:17.870> really<00:07:18.169> giving<00:07:18.680> out<00:07:18.889> a<00:07:19.219> trustless 00:07:20.020 --> 00:07:20.030 align:start position:0% are not really giving out a trustless 00:07:20.030 --> 00:07:22.450 align:start position:0% are not really giving out a trustless solution<00:07:20.780> we<00:07:21.289> are<00:07:21.349> simply<00:07:21.770> shifting<00:07:22.340> the 00:07:22.450 --> 00:07:22.460 align:start position:0% solution we are simply shifting the 00:07:22.460 --> 00:07:25.209 align:start position:0% solution we are simply shifting the trust<00:07:22.729> from<00:07:23.479> the<00:07:23.690> central<00:07:24.080> operator<00:07:24.469> which<00:07:25.009> in 00:07:25.209 --> 00:07:25.219 align:start position:0% trust from the central operator which in 00:07:25.219 --> 00:07:27.580 align:start position:0% trust from the central operator which in that<00:07:25.370> case<00:07:25.610> is<00:07:25.879> recognized<00:07:26.389> as<00:07:26.810> most<00:07:27.139> are<00:07:27.319> that 00:07:27.580 --> 00:07:27.590 align:start position:0% that case is recognized as most are that 00:07:27.590 --> 00:07:30.309 align:start position:0% that case is recognized as most are that startup<00:07:28.039> that<00:07:28.069> we<00:07:28.400> do<00:07:28.550> not<00:07:28.729> want<00:07:29.090> to<00:07:29.210> trust<00:07:29.479> to 00:07:30.309 --> 00:07:30.319 align:start position:0% startup that we do not want to trust to 00:07:30.319 --> 00:07:32.140 align:start position:0% startup that we do not want to trust to parties<00:07:30.889> that<00:07:30.919> has<00:07:31.310> something<00:07:31.610> more<00:07:31.789> at<00:07:32.060> stake 00:07:32.140 --> 00:07:32.150 align:start position:0% parties that has something more at stake 00:07:32.150 --> 00:07:35.740 align:start position:0% parties that has something more at stake that<00:07:32.599> have<00:07:33.110> a<00:07:33.440> strong<00:07:33.740> reputation<00:07:34.039> of<00:07:34.750> course 00:07:35.740 --> 00:07:35.750 align:start position:0% that have a strong reputation of course 00:07:35.750 --> 00:07:39.820 align:start position:0% that have a strong reputation of course if<00:07:36.500> this<00:07:37.009> is<00:07:37.280> all<00:07:38.150> we<00:07:38.780> have<00:07:38.930> this<00:07:39.500> will<00:07:39.680> be 00:07:39.820 --> 00:07:39.830 align:start position:0% if this is all we have this will be 00:07:39.830 --> 00:07:42.730 align:start position:0% if this is all we have this will be quite<00:07:40.099> weak<00:07:40.340> and<00:07:40.490> disappointing<00:07:41.180> as<00:07:41.440> if<00:07:42.440> the 00:07:42.730 --> 00:07:42.740 align:start position:0% quite weak and disappointing as if the 00:07:42.740 --> 00:07:45.430 align:start position:0% quite weak and disappointing as if the solution<00:07:42.889> for<00:07:43.729> the<00:07:43.909> Oracle<00:07:44.210> problem<00:07:44.629> is<00:07:44.810> to 00:07:45.430 --> 00:07:45.440 align:start position:0% solution for the Oracle problem is to 00:07:45.440 --> 00:07:47.499 align:start position:0% solution for the Oracle problem is to trust<00:07:45.680> a<00:07:45.919> single<00:07:46.219> party<00:07:46.639> then<00:07:47.120> we<00:07:47.270> could 00:07:47.499 --> 00:07:47.509 align:start position:0% trust a single party then we could 00:07:47.509 --> 00:07:50.439 align:start position:0% trust a single party then we could simply<00:07:47.930> go<00:07:48.110> to<00:07:48.409> that<00:07:49.009> company<00:07:49.490> and<00:07:49.639> ask<00:07:50.120> them 00:07:50.439 --> 00:07:50.449 align:start position:0% simply go to that company and ask them 00:07:50.449 --> 00:07:52.809 align:start position:0% simply go to that company and ask them to<00:07:50.719> run<00:07:50.960> the<00:07:51.139> Oracle<00:07:51.440> service<00:07:51.800> this<00:07:52.490> would<00:07:52.669> be 00:07:52.809 --> 00:07:52.819 align:start position:0% to run the Oracle service this would be 00:07:52.819 --> 00:07:53.890 align:start position:0% to run the Oracle service this would be exactly<00:07:53.389> the<00:07:53.630> same 00:07:53.890 --> 00:07:53.900 align:start position:0% exactly the same 00:07:53.900 --> 00:07:56.350 align:start position:0% exactly the same open<00:07:54.259> trust<00:07:54.529> wine<00:07:54.770> and<00:07:55.009> it<00:07:55.759> would<00:07:55.969> be<00:07:56.120> much 00:07:56.350 --> 00:07:56.360 align:start position:0% open trust wine and it would be much 00:07:56.360 --> 00:07:57.279 align:start position:0% open trust wine and it would be much more<00:07:56.389> efficient 00:07:57.279 --> 00:07:57.289 align:start position:0% more efficient 00:07:57.289 --> 00:08:00.459 align:start position:0% more efficient however<00:07:58.190> the<00:07:58.669> blockchain<00:07:59.270> was<00:07:59.750> not<00:07:59.990> designed 00:08:00.459 --> 00:08:00.469 align:start position:0% however the blockchain was not designed 00:08:00.469 --> 00:08:02.350 align:start position:0% however the blockchain was not designed to<00:08:00.860> move<00:08:00.979> the<00:08:01.159> trust<00:08:01.400> away<00:08:01.669> to<00:08:01.729> a<00:08:01.940> single 00:08:02.350 --> 00:08:02.360 align:start position:0% to move the trust away to a single 00:08:02.360 --> 00:08:04.809 align:start position:0% to move the trust away to a single central<00:08:02.779> company<00:08:03.169> right<00:08:03.469> or<00:08:03.860> we<00:08:04.310> will<00:08:04.460> not<00:08:04.610> be 00:08:04.809 --> 00:08:04.819 align:start position:0% central company right or we will not be 00:08:04.819 --> 00:08:07.809 align:start position:0% central company right or we will not be here<00:08:05.000> today<00:08:05.380> so<00:08:06.380> by<00:08:07.219> using<00:08:07.400> different 00:08:07.809 --> 00:08:07.819 align:start position:0% here today so by using different 00:08:07.819 --> 00:08:10.540 align:start position:0% here today so by using different technologies<00:08:08.779> we<00:08:09.169> can<00:08:09.349> spread<00:08:09.680> the<00:08:09.919> trust<00:08:10.190> and 00:08:10.540 --> 00:08:10.550 align:start position:0% technologies we can spread the trust and 00:08:10.550 --> 00:08:12.820 align:start position:0% technologies we can spread the trust and get<00:08:11.000> more<00:08:11.330> than<00:08:11.389> one<00:08:11.810> proof<00:08:12.110> backing<00:08:12.680> that 00:08:12.820 --> 00:08:12.830 align:start position:0% get more than one proof backing that 00:08:12.830 --> 00:08:15.339 align:start position:0% get more than one proof backing that claim<00:08:13.129> so<00:08:14.029> if<00:08:14.150> we<00:08:14.270> use<00:08:14.419> all<00:08:14.659> the<00:08:14.840> technology<00:08:15.319> we 00:08:15.339 --> 00:08:15.349 align:start position:0% claim so if we use all the technology we 00:08:15.349 --> 00:08:17.499 align:start position:0% claim so if we use all the technology we see<00:08:15.590> here<00:08:15.830> for<00:08:16.039> example<00:08:16.099> we<00:08:16.940> are<00:08:17.029> trusting 00:08:17.499 --> 00:08:17.509 align:start position:0% see here for example we are trusting 00:08:17.509 --> 00:08:21.100 align:start position:0% see here for example we are trusting four<00:08:18.199> different<00:08:18.889> companies<00:08:19.419> which<00:08:20.419> in<00:08:20.930> order 00:08:21.100 --> 00:08:21.110 align:start position:0% four different companies which in order 00:08:21.110 --> 00:08:24.730 align:start position:0% four different companies which in order to<00:08:21.440> provide<00:08:21.940> valid<00:08:22.940> proofs<00:08:23.270> but<00:08:24.110> backed<00:08:24.469> by 00:08:24.730 --> 00:08:24.740 align:start position:0% to provide valid proofs but backed by 00:08:24.740 --> 00:08:28.119 align:start position:0% to provide valid proofs but backed by tamper<00:08:25.219> with<00:08:25.490> data<00:08:25.759> they<00:08:26.509> will<00:08:26.659> need<00:08:26.930> to<00:08:27.409> well 00:08:28.119 --> 00:08:28.129 align:start position:0% tamper with data they will need to well 00:08:28.129 --> 00:08:30.159 align:start position:0% tamper with data they will need to well basically<00:08:28.759> they<00:08:28.909> will<00:08:29.029> need<00:08:29.210> to<00:08:29.419> lie<00:08:29.569> all<00:08:29.930> at 00:08:30.159 --> 00:08:30.169 align:start position:0% basically they will need to lie all at 00:08:30.169 --> 00:08:32.199 align:start position:0% basically they will need to lie all at the<00:08:30.319> same<00:08:30.529> time<00:08:30.590> in<00:08:31.039> the<00:08:31.129> same<00:08:31.279> way<00:08:31.520> which<00:08:32.180> is 00:08:32.199 --> 00:08:32.209 align:start position:0% the same time in the same way which is 00:08:32.209 --> 00:08:35.170 align:start position:0% the same time in the same way which is quite<00:08:32.539> unlikely<00:08:33.339> so<00:08:34.339> basically<00:08:34.699> all<00:08:34.820> we're 00:08:35.170 --> 00:08:35.180 align:start position:0% quite unlikely so basically all we're 00:08:35.180 --> 00:08:37.329 align:start position:0% quite unlikely so basically all we're doing<00:08:35.449> here<00:08:35.479> is<00:08:35.930> moving<00:08:36.320> the<00:08:36.440> trust<00:08:36.649> away<00:08:36.919> to 00:08:37.329 --> 00:08:37.339 align:start position:0% doing here is moving the trust away to 00:08:37.339 --> 00:08:38.980 align:start position:0% doing here is moving the trust away to different<00:08:37.820> parties<00:08:38.209> by<00:08:38.449> using<00:08:38.659> their 00:08:38.980 --> 00:08:38.990 align:start position:0% different parties by using their 00:08:38.990 --> 00:08:42.219 align:start position:0% different parties by using their technology<00:08:39.620> but<00:08:39.800> without<00:08:40.729> asking<00:08:41.360> them<00:08:41.659> to 00:08:42.219 --> 00:08:42.229 align:start position:0% technology but without asking them to 00:08:42.229 --> 00:08:44.800 align:start position:0% technology but without asking them to run<00:08:42.409> the<00:08:42.560> service<00:08:43.300> something<00:08:44.300> that<00:08:44.449> we<00:08:44.570> get 00:08:44.800 --> 00:08:44.810 align:start position:0% run the service something that we get 00:08:44.810 --> 00:08:48.550 align:start position:0% run the service something that we get asked<00:08:45.110> quite<00:08:45.260> often<00:08:45.500> is<00:08:45.980> wait<00:08:46.640> what<00:08:46.880> but<00:08:47.690> why 00:08:48.550 --> 00:08:48.560 align:start position:0% asked quite often is wait what but why 00:08:48.560 --> 00:08:51.430 align:start position:0% asked quite often is wait what but why don't<00:08:49.130> we<00:08:49.279> just<00:08:49.519> ask<00:08:50.240> those<00:08:50.750> companies<00:08:51.230> to 00:08:51.430 --> 00:08:51.440 align:start position:0% don't we just ask those companies to 00:08:51.440 --> 00:08:53.650 align:start position:0% don't we just ask those companies to come<00:08:51.589> together<00:08:51.800> in<00:08:52.130> a<00:08:52.220> consortium<00:08:52.550> and<00:08:53.000> to 00:08:53.650 --> 00:08:53.660 align:start position:0% come together in a consortium and to 00:08:53.660 --> 00:08:55.569 align:start position:0% come together in a consortium and to provide<00:08:54.079> this<00:08:54.410> as<00:08:54.680> a<00:08:54.709> service<00:08:54.800> they<00:08:55.339> could 00:08:55.569 --> 00:08:55.579 align:start position:0% provide this as a service they could 00:08:55.579 --> 00:08:56.650 align:start position:0% provide this as a service they could simply<00:08:55.790> sign<00:08:56.209> the<00:08:56.390> date 00:08:56.650 --> 00:08:56.660 align:start position:0% simply sign the date 00:08:56.660 --> 00:08:58.629 align:start position:0% simply sign the date animalistic<00:08:57.050> fashion<00:08:57.800> this<00:08:58.250> will<00:08:58.310> be 00:08:58.629 --> 00:08:58.639 align:start position:0% animalistic fashion this will be 00:08:58.639 --> 00:09:02.470 align:start position:0% animalistic fashion this will be trivially<00:08:59.149> doable<00:08:59.360> and<00:09:00.370> this<00:09:01.370> will<00:09:01.610> be<00:09:01.790> much 00:09:02.470 --> 00:09:02.480 align:start position:0% trivially doable and this will be much 00:09:02.480 --> 00:09:05.319 align:start position:0% trivially doable and this will be much easier<00:09:02.750> right<00:09:03.459> well<00:09:04.459> if<00:09:04.699> they<00:09:04.970> come<00:09:05.120> together 00:09:05.319 --> 00:09:05.329 align:start position:0% easier right well if they come together 00:09:05.329 --> 00:09:07.569 align:start position:0% easier right well if they come together in<00:09:05.629> a<00:09:05.720> consortium<00:09:06.019> this<00:09:06.889> is<00:09:07.069> quite<00:09:07.279> weak 00:09:07.569 --> 00:09:07.579 align:start position:0% in a consortium this is quite weak 00:09:07.579 --> 00:09:10.269 align:start position:0% in a consortium this is quite weak because<00:09:08.240> by<00:09:08.629> doing<00:09:08.870> that<00:09:09.019> they<00:09:09.589> would<00:09:09.949> show<00:09:10.250> to 00:09:10.269 --> 00:09:10.279 align:start position:0% because by doing that they would show to 00:09:10.279 --> 00:09:11.590 align:start position:0% because by doing that they would show to the<00:09:10.519> world<00:09:10.550> that<00:09:10.910> they<00:09:11.180> have<00:09:11.300> an<00:09:11.420> agreement 00:09:11.590 --> 00:09:11.600 align:start position:0% the world that they have an agreement 00:09:11.600 --> 00:09:14.860 align:start position:0% the world that they have an agreement and<00:09:12.110> if<00:09:12.680> they<00:09:12.860> have<00:09:13.009> an<00:09:13.160> agreement<00:09:13.339> the<00:09:14.269> chain 00:09:14.860 --> 00:09:14.870 align:start position:0% and if they have an agreement the chain 00:09:14.870 --> 00:09:17.079 align:start position:0% and if they have an agreement the chain of<00:09:15.139> the<00:09:15.410> different<00:09:15.800> proofs<00:09:16.040> is<00:09:16.250> much<00:09:16.850> weaker 00:09:17.079 --> 00:09:17.089 align:start position:0% of the different proofs is much weaker 00:09:17.089 --> 00:09:19.869 align:start position:0% of the different proofs is much weaker as<00:09:17.480> they<00:09:18.259> basically<00:09:19.040> show<00:09:19.399> that<00:09:19.430> they<00:09:19.850> are 00:09:19.869 --> 00:09:19.879 align:start position:0% as they basically show that they are 00:09:19.879 --> 00:09:23.019 align:start position:0% as they basically show that they are willing<00:09:20.149> to<00:09:20.269> cooperate<00:09:20.600> so<00:09:21.430> this<00:09:22.430> is<00:09:22.550> why<00:09:22.699> it's 00:09:23.019 --> 00:09:23.029 align:start position:0% willing to cooperate so this is why it's 00:09:23.029 --> 00:09:24.819 align:start position:0% willing to cooperate so this is why it's much<00:09:23.329> better<00:09:23.569> to<00:09:23.899> have<00:09:23.930> an<00:09:24.110> independent<00:09:24.680> party 00:09:24.819 --> 00:09:24.829 align:start position:0% much better to have an independent party 00:09:24.829 --> 00:09:26.679 align:start position:0% much better to have an independent party which<00:09:25.279> is<00:09:25.430> different<00:09:25.970> from<00:09:26.180> all<00:09:26.480> these 00:09:26.679 --> 00:09:26.689 align:start position:0% which is different from all these 00:09:26.689 --> 00:09:29.259 align:start position:0% which is different from all these different<00:09:26.899> technology<00:09:27.740> providers<00:09:28.189> that<00:09:28.879> runs 00:09:29.259 --> 00:09:29.269 align:start position:0% different technology providers that runs 00:09:29.269 --> 00:09:32.259 align:start position:0% different technology providers that runs to<00:09:29.480> the<00:09:29.509> service<00:09:30.490> so<00:09:31.490> basically<00:09:31.790> what<00:09:32.000> Oracle 00:09:32.259 --> 00:09:32.269 align:start position:0% to the service so basically what Oracle 00:09:32.269 --> 00:09:35.650 align:start position:0% to the service so basically what Oracle Isis<00:09:32.449> is<00:09:32.509> doing<00:09:32.689> is<00:09:33.079> putting<00:09:33.800> in<00:09:34.129> the<00:09:34.819> Oracle 00:09:35.650 --> 00:09:35.660 align:start position:0% Isis is doing is putting in the Oracle 00:09:35.660 --> 00:09:37.840 align:start position:0% Isis is doing is putting in the Oracle eyes<00:09:35.750> engine<00:09:36.199> which<00:09:36.379> is<00:09:36.410> one<00:09:36.889> physical<00:09:37.610> box 00:09:37.840 --> 00:09:37.850 align:start position:0% eyes engine which is one physical box 00:09:37.850 --> 00:09:39.670 align:start position:0% eyes engine which is one physical box that<00:09:38.060> we<00:09:38.180> designed<00:09:38.569> all<00:09:38.810> these<00:09:39.230> different 00:09:39.670 --> 00:09:39.680 align:start position:0% that we designed all these different 00:09:39.680 --> 00:09:41.559 align:start position:0% that we designed all these different technologies<00:09:40.519> all<00:09:40.699> these<00:09:40.879> different<00:09:41.269> trusted 00:09:41.559 --> 00:09:41.569 align:start position:0% technologies all these different trusted 00:09:41.569 --> 00:09:43.960 align:start position:0% technologies all these different trusted computing<00:09:41.839> techniques<00:09:42.319> so<00:09:43.129> that<00:09:43.160> we<00:09:43.790> can 00:09:43.960 --> 00:09:43.970 align:start position:0% computing techniques so that we can 00:09:43.970 --> 00:09:45.730 align:start position:0% computing techniques so that we can provide<00:09:44.269> different<00:09:44.540> layers<00:09:45.139> different 00:09:45.730 --> 00:09:45.740 align:start position:0% provide different layers different 00:09:45.740 --> 00:09:48.879 align:start position:0% provide different layers different levels<00:09:46.069> of<00:09:46.189> proofs<00:09:46.519> and<00:09:47.500> provide<00:09:48.500> this<00:09:48.649> as<00:09:48.860> a 00:09:48.879 --> 00:09:48.889 align:start position:0% levels of proofs and provide this as a 00:09:48.889 --> 00:09:51.970 align:start position:0% levels of proofs and provide this as a service<00:09:48.980> to<00:09:49.490> the<00:09:49.579> blockchain<00:09:50.829> this<00:09:51.829> is 00:09:51.970 --> 00:09:51.980 align:start position:0% service to the blockchain this is 00:09:51.980 --> 00:09:53.619 align:start position:0% service to the blockchain this is something<00:09:52.310> that<00:09:52.339> today<00:09:52.670> we<00:09:53.300> are<00:09:53.389> managing 00:09:53.619 --> 00:09:53.629 align:start position:0% something that today we are managing 00:09:53.629 --> 00:09:56.920 align:start position:0% something that today we are managing with<00:09:54.500> a<00:09:54.829> distributed<00:09:55.550> network<00:09:56.420> so<00:09:56.660> this<00:09:56.810> is 00:09:56.920 --> 00:09:56.930 align:start position:0% with a distributed network so this is 00:09:56.930 --> 00:09:59.490 align:start position:0% with a distributed network so this is something<00:09:57.110> we<00:09:57.350> fully<00:09:57.560> manage<00:09:57.949> so<00:09:58.759> as<00:09:58.970> we<00:09:59.209> just 00:09:59.490 --> 00:09:59.500 align:start position:0% something we fully manage so as we just 00:09:59.500 --> 00:10:02.290 align:start position:0% something we fully manage so as we just we<00:10:00.500> have<00:10:00.589> just<00:10:00.800> seen<00:10:01.149> thanks<00:10:02.149> to<00:10:02.240> the 00:10:02.290 --> 00:10:02.300 align:start position:0% we have just seen thanks to the 00:10:02.300 --> 00:10:04.269 align:start position:0% we have just seen thanks to the authenticity<00:10:02.540> proofs<00:10:03.050> we<00:10:03.410> do<00:10:03.560> not<00:10:03.740> need<00:10:04.040> to 00:10:04.269 --> 00:10:04.279 align:start position:0% authenticity proofs we do not need to 00:10:04.279 --> 00:10:07.179 align:start position:0% authenticity proofs we do not need to trust<00:10:04.550> Oracle<00:10:05.389> eyes<00:10:05.480> but<00:10:06.019> we<00:10:06.649> need<00:10:06.829> to<00:10:06.980> trust 00:10:07.179 --> 00:10:07.189 align:start position:0% trust Oracle eyes but we need to trust 00:10:07.189 --> 00:10:09.610 align:start position:0% trust Oracle eyes but we need to trust all<00:10:07.670> these<00:10:07.850> different<00:10:08.269> artists<00:10:08.509> theaters<00:10:08.870> so 00:10:09.610 --> 00:10:09.620 align:start position:0% all these different artists theaters so 00:10:09.620 --> 00:10:11.949 align:start position:0% all these different artists theaters so the<00:10:09.769> only<00:10:09.889> risk<00:10:10.220> of<00:10:10.610> the<00:10:10.759> central<00:10:11.240> operator<00:10:11.630> of 00:10:11.949 --> 00:10:11.959 align:start position:0% the only risk of the central operator of 00:10:11.959 --> 00:10:14.139 align:start position:0% the only risk of the central operator of the<00:10:12.139> Oracle<00:10:12.410> eyes<00:10:12.500> service<00:10:12.980> is<00:10:13.310> basically<00:10:13.910> the 00:10:14.139 --> 00:10:14.149 align:start position:0% the Oracle eyes service is basically the 00:10:14.149 --> 00:10:18.100 align:start position:0% the Oracle eyes service is basically the service<00:10:14.600> to<00:10:15.339> stop<00:10:16.339> running<00:10:16.699> so<00:10:17.209> bad<00:10:17.660> quality 00:10:18.100 --> 00:10:18.110 align:start position:0% service to stop running so bad quality 00:10:18.110 --> 00:10:20.590 align:start position:0% service to stop running so bad quality of<00:10:18.139> service<00:10:18.589> or<00:10:18.769> maybe<00:10:19.250> censorship<00:10:20.180> or<00:10:20.389> many 00:10:20.590 --> 00:10:20.600 align:start position:0% of service or maybe censorship or many 00:10:20.600 --> 00:10:22.600 align:start position:0% of service or maybe censorship or many other<00:10:20.779> of<00:10:20.930> these<00:10:21.050> problems<00:10:21.500> this<00:10:22.040> is<00:10:22.100> why<00:10:22.399> we 00:10:22.600 --> 00:10:22.610 align:start position:0% other of these problems this is why we 00:10:22.610 --> 00:10:25.329 align:start position:0% other of these problems this is why we are<00:10:22.639> working<00:10:23.089> towards<00:10:23.600> a<00:10:24.290> new<00:10:24.920> possibility 00:10:25.329 --> 00:10:25.339 align:start position:0% are working towards a new possibility 00:10:25.339 --> 00:10:27.759 align:start position:0% are working towards a new possibility which<00:10:26.029> is<00:10:26.060> basically<00:10:26.810> delegating<00:10:27.620> the 00:10:27.759 --> 00:10:27.769 align:start position:0% which is basically delegating the 00:10:27.769 --> 00:10:29.980 align:start position:0% which is basically delegating the management<00:10:28.310> of<00:10:28.490> the<00:10:29.120> Oracle<00:10:29.540> eyes<00:10:29.630> engine 00:10:29.980 --> 00:10:29.990 align:start position:0% management of the Oracle eyes engine 00:10:29.990 --> 00:10:32.530 align:start position:0% management of the Oracle eyes engine machines<00:10:30.350> to<00:10:30.740> any<00:10:30.949> interested<00:10:31.639> parties<00:10:32.089> that 00:10:32.530 --> 00:10:32.540 align:start position:0% machines to any interested parties that 00:10:32.540 --> 00:10:35.650 align:start position:0% machines to any interested parties that might<00:10:32.959> be<00:10:33.230> willing<00:10:33.620> to<00:10:33.970> contribute<00:10:34.970> to 00:10:35.650 --> 00:10:35.660 align:start position:0% might be willing to contribute to 00:10:35.660 --> 00:10:37.809 align:start position:0% might be willing to contribute to maintaining<00:10:35.990> the<00:10:36.319> service<00:10:36.740> running<00:10:36.949> so<00:10:37.670> this 00:10:37.809 --> 00:10:37.819 align:start position:0% maintaining the service running so this 00:10:37.819 --> 00:10:39.639 align:start position:0% maintaining the service running so this is<00:10:37.970> something<00:10:38.329> that<00:10:38.360> will<00:10:38.750> basically<00:10:39.139> move 00:10:39.639 --> 00:10:39.649 align:start position:0% is something that will basically move 00:10:39.649 --> 00:10:43.809 align:start position:0% is something that will basically move away<00:10:39.949> the<00:10:40.309> governance<00:10:40.910> of<00:10:41.089> the<00:10:42.819> maintenance 00:10:43.809 --> 00:10:43.819 align:start position:0% away the governance of the maintenance 00:10:43.819 --> 00:10:45.670 align:start position:0% away the governance of the maintenance of<00:10:43.939> the<00:10:44.059> service<00:10:44.449> from<00:10:44.689> Oracle<00:10:45.110> eyes<00:10:45.199> to<00:10:45.649> a 00:10:45.670 --> 00:10:45.680 align:start position:0% of the service from Oracle eyes to a 00:10:45.680 --> 00:10:49.299 align:start position:0% of the service from Oracle eyes to a different<00:10:46.309> entity<00:10:47.920> the<00:10:48.920> rest<00:10:49.069> of<00:10:49.189> the 00:10:49.299 --> 00:10:49.309 align:start position:0% different entity the rest of the 00:10:49.309 --> 00:10:51.519 align:start position:0% different entity the rest of the presentation<00:10:49.730> is<00:10:50.300> around<00:10:51.050> authenticity 00:10:51.519 --> 00:10:51.529 align:start position:0% presentation is around authenticity 00:10:51.529 --> 00:10:53.350 align:start position:0% presentation is around authenticity proof<00:10:51.980> so<00:10:52.220> I<00:10:52.250> want<00:10:52.550> to<00:10:52.639> dive<00:10:52.819> into<00:10:53.059> the 00:10:53.350 --> 00:10:53.360 align:start position:0% proof so I want to dive into the 00:10:53.360 --> 00:10:56.559 align:start position:0% proof so I want to dive into the verifications<00:10:54.139> of<00:10:54.350> those<00:10:54.620> proofs<00:10:55.389> so<00:10:56.389> what 00:10:56.559 --> 00:10:56.569 align:start position:0% verifications of those proofs so what 00:10:56.569 --> 00:10:58.600 align:start position:0% verifications of those proofs so what you<00:10:56.689> see<00:10:56.930> here<00:10:57.230> is<00:10:57.410> the<00:10:57.559> network<00:10:57.860> monitor<00:10:58.309> this 00:10:58.600 --> 00:10:58.610 align:start position:0% you see here is the network monitor this 00:10:58.610 --> 00:11:00.490 align:start position:0% you see here is the network monitor this is<00:10:58.819> a<00:10:58.850> web-based<00:10:59.269> tool<00:10:59.600> that<00:10:59.750> anybody<00:11:00.139> can<00:11:00.439> use 00:11:00.490 --> 00:11:00.500 align:start position:0% is a web-based tool that anybody can use 00:11:00.500 --> 00:11:02.650 align:start position:0% is a web-based tool that anybody can use to<00:11:00.800> verify<00:11:01.129> of<00:11:01.309> chain<00:11:01.699> the<00:11:02.089> authenticity<00:11:02.300> of 00:11:02.650 --> 00:11:02.660 align:start position:0% to verify of chain the authenticity of 00:11:02.660 --> 00:11:05.290 align:start position:0% to verify of chain the authenticity of the<00:11:02.809> proofs<00:11:03.339> unfortunately<00:11:04.339> this<00:11:04.790> means<00:11:05.029> that 00:11:05.290 --> 00:11:05.300 align:start position:0% the proofs unfortunately this means that 00:11:05.300 --> 00:11:07.059 align:start position:0% the proofs unfortunately this means that once<00:11:05.569> you<00:11:05.660> have<00:11:05.839> a<00:11:06.079> smart<00:11:06.500> contract<00:11:06.680> like<00:11:07.040> this 00:11:07.059 --> 00:11:07.069 align:start position:0% once you have a smart contract like this 00:11:07.069 --> 00:11:09.549 align:start position:0% once you have a smart contract like this which<00:11:07.819> wants<00:11:08.300> to<00:11:08.449> reach<00:11:08.630> out<00:11:08.809> to<00:11:08.990> a<00:11:09.019> Web<00:11:09.199> API 00:11:09.549 --> 00:11:09.559 align:start position:0% which wants to reach out to a Web API 00:11:09.559 --> 00:11:10.930 align:start position:0% which wants to reach out to a Web API like<00:11:09.949> crypto<00:11:10.279> compare 00:11:10.930 --> 00:11:10.940 align:start position:0% like crypto compare 00:11:10.940 --> 00:11:13.270 align:start position:0% like crypto compare you<00:11:11.420> specify<00:11:11.660> the<00:11:11.990> proof<00:11:12.380> you<00:11:12.500> want<00:11:12.770> like 00:11:13.270 --> 00:11:13.280 align:start position:0% you specify the proof you want like 00:11:13.280 --> 00:11:15.760 align:start position:0% you specify the proof you want like Oracle<00:11:13.730> is<00:11:14.000> that<00:11:14.450> proof<00:11:14.690> proof<00:11:15.140> type<00:11:15.410> TLS 00:11:15.760 --> 00:11:15.770 align:start position:0% Oracle is that proof proof type TLS 00:11:15.770 --> 00:11:17.620 align:start position:0% Oracle is that proof proof type TLS notary<00:11:16.130> so<00:11:16.460> here<00:11:16.700> we<00:11:16.850> are<00:11:16.880> saying<00:11:17.150> we<00:11:17.330> want<00:11:17.540> a 00:11:17.620 --> 00:11:17.630 align:start position:0% notary so here we are saying we want a 00:11:17.630 --> 00:11:19.480 align:start position:0% notary so here we are saying we want a TLS<00:11:17.900> notary<00:11:18.290> proof<00:11:18.500> which<00:11:18.950> is<00:11:19.100> software 00:11:19.480 --> 00:11:19.490 align:start position:0% TLS notary proof which is software 00:11:19.490 --> 00:11:22.750 align:start position:0% TLS notary proof which is software backed<00:11:19.820> and<00:11:20.090> based<00:11:20.420> on<00:11:20.890> the<00:11:21.890> trust<00:11:22.430> with 00:11:22.750 --> 00:11:22.760 align:start position:0% backed and based on the trust with 00:11:22.760 --> 00:11:26.500 align:start position:0% backed and based on the trust with Amazon<00:11:23.330> and<00:11:24.160> we<00:11:25.160> want<00:11:25.370> proof<00:11:25.610> storage<00:11:26.000> AP<00:11:26.300> FS 00:11:26.500 --> 00:11:26.510 align:start position:0% Amazon and we want proof storage AP FS 00:11:26.510 --> 00:11:30.550 align:start position:0% Amazon and we want proof storage AP FS so<00:11:26.990> actually<00:11:27.440> we<00:11:27.890> will<00:11:28.010> not<00:11:28.220> get<00:11:28.460> back<00:11:28.730> the<00:11:29.560> raw 00:11:30.550 --> 00:11:30.560 align:start position:0% so actually we will not get back the raw 00:11:30.560 --> 00:11:33.220 align:start position:0% so actually we will not get back the raw proof<00:11:30.890> which<00:11:31.700> will<00:11:32.060> be<00:11:32.240> quite<00:11:32.450> big<00:11:32.720> but<00:11:33.200> just 00:11:33.220 --> 00:11:33.230 align:start position:0% proof which will be quite big but just 00:11:33.230 --> 00:11:35.860 align:start position:0% proof which will be quite big but just the<00:11:33.590> AP<00:11:33.800> FS<00:11:34.040> multi<00:11:34.430> ash<00:11:34.550> of<00:11:34.730> the<00:11:34.850> same<00:11:35.090> so<00:11:35.720> as<00:11:35.810> a 00:11:35.860 --> 00:11:35.870 align:start position:0% the AP FS multi ash of the same so as a 00:11:35.870 --> 00:11:37.900 align:start position:0% the AP FS multi ash of the same so as a consequence<00:11:36.440> it<00:11:36.770> means<00:11:37.190> that<00:11:37.520> it's<00:11:37.700> not 00:11:37.900 --> 00:11:37.910 align:start position:0% consequence it means that it's not 00:11:37.910 --> 00:11:40.150 align:start position:0% consequence it means that it's not possible<00:11:38.180> to<00:11:38.720> verify<00:11:38.900> with<00:11:39.620> a<00:11:39.650> contract<00:11:40.130> like 00:11:40.150 --> 00:11:40.160 align:start position:0% possible to verify with a contract like 00:11:40.160 --> 00:11:44.020 align:start position:0% possible to verify with a contract like this<00:11:40.990> the<00:11:41.990> validity<00:11:42.710> of<00:11:42.920> the<00:11:43.100> proof<00:11:43.340> on<00:11:43.610> the 00:11:44.020 --> 00:11:44.030 align:start position:0% this the validity of the proof on the 00:11:44.030 --> 00:11:46.450 align:start position:0% this the validity of the proof on the contract<00:11:44.510> once<00:11:45.080> it<00:11:45.410> receives<00:11:45.620> the<00:11:46.100> codec 00:11:46.450 --> 00:11:46.460 align:start position:0% contract once it receives the codec 00:11:46.460 --> 00:11:49.060 align:start position:0% contract once it receives the codec function<00:11:46.910> so<00:11:47.480> this<00:11:47.630> is<00:11:47.780> something<00:11:48.020> that<00:11:48.410> is 00:11:49.060 --> 00:11:49.070 align:start position:0% function so this is something that is 00:11:49.070 --> 00:11:51.490 align:start position:0% function so this is something that is not<00:11:49.250> easier<00:11:49.610> because<00:11:49.940> basically<00:11:50.420> Oracle<00:11:51.410> eyes 00:11:51.490 --> 00:11:51.500 align:start position:0% not easier because basically Oracle eyes 00:11:51.500 --> 00:11:53.620 align:start position:0% not easier because basically Oracle eyes could<00:11:51.890> potentially<00:11:52.550> send<00:11:52.820> back<00:11:53.030> a<00:11:53.270> Bronk 00:11:53.620 --> 00:11:53.630 align:start position:0% could potentially send back a Bronk 00:11:53.630 --> 00:11:55.120 align:start position:0% could potentially send back a Bronk proof<00:11:53.870> and<00:11:54.110> you<00:11:54.440> will<00:11:54.620> just<00:11:54.830> notice 00:11:55.120 --> 00:11:55.130 align:start position:0% proof and you will just notice 00:11:55.130 --> 00:11:57.760 align:start position:0% proof and you will just notice afterwards<00:11:55.790> so<00:11:56.720> the<00:11:56.960> interesting<00:11:57.320> part<00:11:57.500> is 00:11:57.760 --> 00:11:57.770 align:start position:0% afterwards so the interesting part is 00:11:57.770 --> 00:12:00.250 align:start position:0% afterwards so the interesting part is that<00:11:57.830> anybody<00:11:58.730> can<00:11:58.910> check<00:11:59.210> for<00:11:59.510> the<00:11:59.900> last<00:12:00.110> two 00:12:00.250 --> 00:12:00.260 align:start position:0% that anybody can check for the last two 00:12:00.260 --> 00:12:03.730 align:start position:0% that anybody can check for the last two years<00:12:00.350> and<00:12:00.650> all<00:12:00.800> all<00:12:01.400> the<00:12:02.290> 300,000<00:12:03.290> proofs<00:12:03.410> we 00:12:03.730 --> 00:12:03.740 align:start position:0% years and all all the 300,000 proofs we 00:12:03.740 --> 00:12:05.590 align:start position:0% years and all all the 300,000 proofs we are<00:12:03.830> sent<00:12:04.040> on<00:12:04.130> chain<00:12:04.430> and<00:12:04.760> you<00:12:05.090> will<00:12:05.270> see<00:12:05.450> that 00:12:05.590 --> 00:12:05.600 align:start position:0% are sent on chain and you will see that 00:12:05.600 --> 00:12:07.420 align:start position:0% are sent on chain and you will see that there<00:12:05.780> is<00:12:05.810> none<00:12:06.200> which<00:12:06.710> at<00:12:06.860> the<00:12:06.950> moment<00:12:06.980> is<00:12:07.310> not 00:12:07.420 --> 00:12:07.430 align:start position:0% there is none which at the moment is not 00:12:07.430 --> 00:12:09.490 align:start position:0% there is none which at the moment is not passing<00:12:07.880> unless<00:12:08.630> there<00:12:08.780> was<00:12:08.930> one<00:12:09.170> while<00:12:09.380> it 00:12:09.490 --> 00:12:09.500 align:start position:0% passing unless there was one while it 00:12:09.500 --> 00:12:12.970 align:start position:0% passing unless there was one while it was<00:12:09.680> on<00:12:09.800> stage<00:12:10.010> but<00:12:10.660> in<00:12:11.660> general<00:12:12.200> what<00:12:12.560> we<00:12:12.740> want 00:12:12.970 --> 00:12:12.980 align:start position:0% was on stage but in general what we want 00:12:12.980 --> 00:12:15.880 align:start position:0% was on stage but in general what we want is<00:12:13.250> a<00:12:13.280> stronger<00:12:13.820> guarantee<00:12:14.380> where<00:12:15.380> basically 00:12:15.880 --> 00:12:15.890 align:start position:0% is a stronger guarantee where basically 00:12:15.890 --> 00:12:18.040 align:start position:0% is a stronger guarantee where basically the<00:12:16.040> authenticity<00:12:16.280> proofs<00:12:16.790> can<00:12:17.270> be<00:12:17.480> verified 00:12:18.040 --> 00:12:18.050 align:start position:0% the authenticity proofs can be verified 00:12:18.050 --> 00:12:20.590 align:start position:0% the authenticity proofs can be verified by<00:12:18.320> the<00:12:18.590> receiving<00:12:19.130> contracts<00:12:19.610> so<00:12:20.180> let's<00:12:20.420> see 00:12:20.590 --> 00:12:20.600 align:start position:0% by the receiving contracts so let's see 00:12:20.600 --> 00:12:22.510 align:start position:0% by the receiving contracts so let's see what<00:12:21.050> the<00:12:21.320> authenticity<00:12:21.560> proof<00:12:22.040> contains 00:12:22.510 --> 00:12:22.520 align:start position:0% what the authenticity proof contains 00:12:22.520 --> 00:12:25.450 align:start position:0% what the authenticity proof contains first<00:12:22.940> of<00:12:23.060> all<00:12:23.180> so<00:12:24.110> basically<00:12:24.800> this<00:12:25.130> really 00:12:25.450 --> 00:12:25.460 align:start position:0% first of all so basically this really 00:12:25.460 --> 00:12:28.060 align:start position:0% first of all so basically this really depends<00:12:25.820> on<00:12:26.090> the<00:12:26.960> sandboxing<00:12:27.710> technique 00:12:28.060 --> 00:12:28.070 align:start position:0% depends on the sandboxing technique 00:12:28.070 --> 00:12:29.860 align:start position:0% depends on the sandboxing technique being<00:12:28.280> used<00:12:28.610> because<00:12:28.970> different<00:12:29.360> techniques 00:12:29.860 --> 00:12:29.870 align:start position:0% being used because different techniques 00:12:29.870 --> 00:12:32.130 align:start position:0% being used because different techniques need<00:12:30.230> different<00:12:30.650> verification<00:12:31.490> steps 00:12:32.130 --> 00:12:32.140 align:start position:0% need different verification steps 00:12:32.140 --> 00:12:34.990 align:start position:0% need different verification steps however<00:12:33.140> they<00:12:33.680> are<00:12:33.770> all<00:12:34.010> basically<00:12:34.670> a 00:12:34.990 --> 00:12:35.000 align:start position:0% however they are all basically a 00:12:35.000 --> 00:12:37.540 align:start position:0% however they are all basically a collection<00:12:35.450> of<00:12:35.780> signatures<00:12:36.620> and<00:12:36.830> data<00:12:37.100> to 00:12:37.540 --> 00:12:37.550 align:start position:0% collection of signatures and data to 00:12:37.550 --> 00:12:39.460 align:start position:0% collection of signatures and data to verify<00:12:37.670> some<00:12:38.120> kind<00:12:38.360> of<00:12:38.480> attestation<00:12:38.960> some 00:12:39.460 --> 00:12:39.470 align:start position:0% verify some kind of attestation some 00:12:39.470 --> 00:12:42.730 align:start position:0% verify some kind of attestation some kind<00:12:39.740> of<00:12:39.860> claim<00:12:40.190> coming<00:12:40.760> from<00:12:40.970> the<00:12:41.780> artists 00:12:42.730 --> 00:12:42.740 align:start position:0% kind of claim coming from the artists 00:12:42.740 --> 00:12:46.300 align:start position:0% kind of claim coming from the artists theater<00:12:43.570> still<00:12:44.570> those<00:12:44.990> proofs<00:12:45.260> are<00:12:45.470> general 00:12:46.300 --> 00:12:46.310 align:start position:0% theater still those proofs are general 00:12:46.310 --> 00:12:47.920 align:start position:0% theater still those proofs are general purpose<00:12:46.430> so<00:12:47.030> they<00:12:47.180> have<00:12:47.270> nothing<00:12:47.600> to<00:12:47.750> do<00:12:47.900> with 00:12:47.920 --> 00:12:47.930 align:start position:0% purpose so they have nothing to do with 00:12:47.930 --> 00:12:50.170 align:start position:0% purpose so they have nothing to do with the<00:12:48.350> blockchain<00:12:48.590> in<00:12:48.980> their<00:12:49.160> format<00:12:49.580> we<00:12:50.090> are 00:12:50.170 --> 00:12:50.180 align:start position:0% the blockchain in their format we are 00:12:50.180 --> 00:12:52.150 align:start position:0% the blockchain in their format we are investigating<00:12:50.570> use<00:12:51.020> cases<00:12:51.260> also<00:12:51.620> outside<00:12:52.100> the 00:12:52.150 --> 00:12:52.160 align:start position:0% investigating use cases also outside the 00:12:52.160 --> 00:12:55.420 align:start position:0% investigating use cases also outside the blockchain<00:12:52.850> space<00:12:53.650> and<00:12:54.650> they<00:12:55.400> are 00:12:55.420 --> 00:12:55.430 align:start position:0% blockchain space and they are 00:12:55.430 --> 00:12:57.430 align:start position:0% blockchain space and they are self-contained<00:12:55.850> so<00:12:56.600> it<00:12:56.690> means<00:12:56.900> that<00:12:57.140> once<00:12:57.350> you 00:12:57.430 --> 00:12:57.440 align:start position:0% self-contained so it means that once you 00:12:57.440 --> 00:12:58.960 align:start position:0% self-contained so it means that once you have<00:12:57.590> the<00:12:57.740> proof<00:12:57.980> you<00:12:58.310> should<00:12:58.520> be<00:12:58.670> able<00:12:58.760> to 00:12:58.960 --> 00:12:58.970 align:start position:0% have the proof you should be able to 00:12:58.970 --> 00:13:01.690 align:start position:0% have the proof you should be able to extract<00:12:59.600> the<00:13:00.140> full<00:13:00.380> message<00:13:00.620> from<00:13:01.310> the<00:13:01.490> proof 00:13:01.690 --> 00:13:01.700 align:start position:0% extract the full message from the proof 00:13:01.700 --> 00:13:04.090 align:start position:0% extract the full message from the proof itself<00:13:02.030> there<00:13:02.840> should<00:13:03.050> be<00:13:03.200> nothing<00:13:03.440> outside 00:13:04.090 --> 00:13:04.100 align:start position:0% itself there should be nothing outside 00:13:04.100 --> 00:13:06.280 align:start position:0% itself there should be nothing outside the<00:13:04.160> proof<00:13:04.580> that<00:13:04.610> you<00:13:04.880> need<00:13:05.090> to<00:13:05.870> verify<00:13:06.050> the 00:13:06.280 --> 00:13:06.290 align:start position:0% the proof that you need to verify the 00:13:06.290 --> 00:13:09.490 align:start position:0% the proof that you need to verify the validity<00:13:06.470> of<00:13:06.770> the<00:13:06.920> proof<00:13:07.130> itself<00:13:08.500> however 00:13:09.490 --> 00:13:09.500 align:start position:0% validity of the proof itself however 00:13:09.500 --> 00:13:11.830 align:start position:0% validity of the proof itself however giving<00:13:10.190> that<00:13:10.430> nature<00:13:10.910> of<00:13:11.120> the<00:13:11.300> proof<00:13:11.510> they 00:13:11.830 --> 00:13:11.840 align:start position:0% giving that nature of the proof they 00:13:11.840 --> 00:13:14.530 align:start position:0% giving that nature of the proof they might<00:13:12.050> be<00:13:12.320> quite<00:13:12.680> big<00:13:12.950> depending<00:13:13.760> on<00:13:13.910> the<00:13:14.330> data 00:13:14.530 --> 00:13:14.540 align:start position:0% might be quite big depending on the data 00:13:14.540 --> 00:13:15.790 align:start position:0% might be quite big depending on the data you<00:13:14.660> are<00:13:14.840> trying<00:13:15.050> to<00:13:15.140> fetch<00:13:15.410> from<00:13:15.680> the 00:13:15.790 --> 00:13:15.800 align:start position:0% you are trying to fetch from the 00:13:15.800 --> 00:13:17.800 align:start position:0% you are trying to fetch from the external<00:13:16.010> data<00:13:16.280> source<00:13:16.670> so<00:13:17.030> this<00:13:17.150> is<00:13:17.300> why<00:13:17.450> we 00:13:17.800 --> 00:13:17.810 align:start position:0% external data source so this is why we 00:13:17.810 --> 00:13:19.960 align:start position:0% external data source so this is why we cannot<00:13:18.140> send<00:13:18.560> them<00:13:18.800> every<00:13:19.460> time<00:13:19.670> on<00:13:19.880> the 00:13:19.960 --> 00:13:19.970 align:start position:0% cannot send them every time on the 00:13:19.970 --> 00:13:21.250 align:start position:0% cannot send them every time on the blockchain<00:13:20.180> because<00:13:20.630> it<00:13:20.780> will<00:13:20.930> be<00:13:21.050> a<00:13:21.080> very 00:13:21.250 --> 00:13:21.260 align:start position:0% blockchain because it will be a very 00:13:21.260 --> 00:13:24.220 align:start position:0% blockchain because it will be a very high<00:13:21.530> cost<00:13:21.830> and<00:13:22.390> well<00:13:23.390> given<00:13:23.720> the<00:13:23.810> gas<00:13:23.990> limit 00:13:24.220 --> 00:13:24.230 align:start position:0% high cost and well given the gas limit 00:13:24.230 --> 00:13:26.530 align:start position:0% high cost and well given the gas limit of<00:13:24.710> course<00:13:24.950> this<00:13:25.280> is<00:13:25.400> something<00:13:25.700> that<00:13:25.730> it's 00:13:26.530 --> 00:13:26.540 align:start position:0% of course this is something that it's 00:13:26.540 --> 00:13:30.400 align:start position:0% of course this is something that it's not<00:13:26.840> possible<00:13:27.430> above<00:13:28.430> certain<00:13:28.940> sizes<00:13:29.330> so<00:13:30.320> I'm 00:13:30.400 --> 00:13:30.410 align:start position:0% not possible above certain sizes so I'm 00:13:30.410 --> 00:13:31.600 align:start position:0% not possible above certain sizes so I'm intent<00:13:30.680> is<00:13:30.800> the<00:13:30.950> proofs<00:13:31.190> that<00:13:31.250> we<00:13:31.400> have 00:13:31.600 --> 00:13:31.610 align:start position:0% intent is the proofs that we have 00:13:31.610 --> 00:13:34.000 align:start position:0% intent is the proofs that we have designed<00:13:31.820> such<00:13:32.300> as<00:13:32.510> the<00:13:32.750> ledger<00:13:33.050> proof<00:13:33.470> for 00:13:34.000 --> 00:13:34.010 align:start position:0% designed such as the ledger proof for 00:13:34.010 --> 00:13:36.130 align:start position:0% designed such as the ledger proof for the<00:13:34.160> random<00:13:34.520> data<00:13:34.730> source<00:13:35.030> and<00:13:35.210> the<00:13:35.780> native 00:13:36.130 --> 00:13:36.140 align:start position:0% the random data source and the native 00:13:36.140 --> 00:13:38.200 align:start position:0% the random data source and the native proofs<00:13:36.440> like<00:13:37.130> the<00:13:37.310> ones<00:13:37.520> where<00:13:37.850> the<00:13:38.030> data 00:13:38.200 --> 00:13:38.210 align:start position:0% proofs like the ones where the data 00:13:38.210 --> 00:13:40.480 align:start position:0% proofs like the ones where the data source<00:13:38.480> signs<00:13:38.660> the<00:13:38.810> data<00:13:39.020> are<00:13:39.490> trivially 00:13:40.480 --> 00:13:40.490 align:start position:0% source signs the data are trivially 00:13:40.490 --> 00:13:43.390 align:start position:0% source signs the data are trivially verifiable<00:13:41.330> on<00:13:41.630> chain<00:13:41.900> so<00:13:42.560> this<00:13:43.070> is<00:13:43.250> for 00:13:43.390 --> 00:13:43.400 align:start position:0% verifiable on chain so this is for 00:13:43.400 --> 00:13:46.510 align:start position:0% verifiable on chain so this is for example<00:13:43.460> a<00:13:44.210> very<00:13:44.450> short<00:13:44.720> piece<00:13:44.900> of<00:13:44.930> code<00:13:45.520> which 00:13:46.510 --> 00:13:46.520 align:start position:0% example a very short piece of code which 00:13:46.520 --> 00:13:48.850 align:start position:0% example a very short piece of code which verifies<00:13:46.820> native<00:13:47.510> proofs<00:13:47.840> on<00:13:47.990> chain<00:13:48.230> as<00:13:48.500> we 00:13:48.850 --> 00:13:48.860 align:start position:0% verifies native proofs on chain as we 00:13:48.860 --> 00:13:50.620 align:start position:0% verifies native proofs on chain as we expect<00:13:49.340> this<00:13:49.790> is<00:13:50.030> nothing<00:13:50.450> really 00:13:50.620 --> 00:13:50.630 align:start position:0% expect this is nothing really 00:13:50.630 --> 00:13:52.300 align:start position:0% expect this is nothing really complicated<00:13:50.870> but<00:13:51.740> we<00:13:51.920> see<00:13:52.070> there<00:13:52.220> are 00:13:52.300 --> 00:13:52.310 align:start position:0% complicated but we see there are 00:13:52.310 --> 00:13:53.860 align:start position:0% complicated but we see there are different<00:13:52.700> steps<00:13:52.940> like<00:13:53.240> we<00:13:53.420> need<00:13:53.540> to<00:13:53.690> check 00:13:53.860 --> 00:13:53.870 align:start position:0% different steps like we need to check 00:13:53.870 --> 00:13:56.200 align:start position:0% different steps like we need to check that<00:13:54.200> the<00:13:54.470> answer<00:13:54.860> is<00:13:55.040> fresh<00:13:55.640> that<00:13:56.030> is 00:13:56.200 --> 00:13:56.210 align:start position:0% that the answer is fresh that is 00:13:56.210 --> 00:13:58.990 align:start position:0% that the answer is fresh that is authentic<00:13:56.570> and<00:13:57.050> that<00:13:57.650> there<00:13:58.130> is<00:13:58.250> integrity<00:13:58.910> of 00:13:58.990 --> 00:13:59.000 align:start position:0% authentic and that there is integrity of 00:13:59.000 --> 00:14:02.710 align:start position:0% authentic and that there is integrity of the<00:13:59.150> proof<00:13:59.330> and<00:13:59.510> other<00:14:00.260> steps<00:14:01.390> for<00:14:02.390> the 00:14:02.710 --> 00:14:02.720 align:start position:0% the proof and other steps for the 00:14:02.720 --> 00:14:04.600 align:start position:0% the proof and other steps for the alleged<00:14:02.900> proof<00:14:03.230> it's<00:14:03.530> even<00:14:03.800> more<00:14:03.920> complicated 00:14:04.600 --> 00:14:04.610 align:start position:0% alleged proof it's even more complicated 00:14:04.610 --> 00:14:07.450 align:start position:0% alleged proof it's even more complicated because<00:14:05.000> we<00:14:05.300> are<00:14:05.780> checking<00:14:06.140> basically<00:14:06.980> that 00:14:07.450 --> 00:14:07.460 align:start position:0% because we are checking basically that 00:14:07.460 --> 00:14:10.300 align:start position:0% because we are checking basically that the<00:14:07.790> trusted<00:14:08.720> computing<00:14:08.750> device<00:14:09.440> is<00:14:09.890> really 00:14:10.300 --> 00:14:10.310 align:start position:0% the trusted computing device is really 00:14:10.310 --> 00:14:12.730 align:start position:0% the trusted computing device is really executing<00:14:10.910> the<00:14:11.390> correct<00:14:12.020> code<00:14:12.320> that<00:14:12.560> we 00:14:12.730 --> 00:14:12.740 align:start position:0% executing the correct code that we 00:14:12.740 --> 00:14:15.130 align:start position:0% executing the correct code that we expect<00:14:13.130> it<00:14:13.280> to<00:14:13.310> be<00:14:13.550> executed<00:14:14.150> so<00:14:14.690> you<00:14:14.750> see<00:14:15.080> in 00:14:15.130 --> 00:14:15.140 align:start position:0% expect it to be executed so you see in 00:14:15.140 --> 00:14:16.690 align:start position:0% expect it to be executed so you see in the<00:14:15.260> code<00:14:15.470> that<00:14:15.500> there<00:14:15.830> is<00:14:15.950> for<00:14:16.100> example<00:14:16.130> our 00:14:16.690 --> 00:14:16.700 align:start position:0% the code that there is for example our 00:14:16.700 --> 00:14:19.210 align:start position:0% the code that there is for example our code<00:14:16.940> ash<00:14:17.120> which<00:14:17.630> is<00:14:17.660> the<00:14:18.020> ash<00:14:18.260> of<00:14:18.650> the<00:14:19.040> code 00:14:19.210 --> 00:14:19.220 align:start position:0% code ash which is the ash of the code 00:14:19.220 --> 00:14:21.040 align:start position:0% code ash which is the ash of the code being<00:14:19.430> executed<00:14:19.790> which<00:14:20.510> being<00:14:20.720> open<00:14:21.020> source 00:14:21.040 --> 00:14:21.050 align:start position:0% being executed which being open source 00:14:21.050 --> 00:14:23.460 align:start position:0% being executed which being open source you<00:14:21.380> can<00:14:21.500> verify<00:14:21.710> yourself<00:14:21.980> of<00:14:22.400> chain<00:14:22.880> once 00:14:23.460 --> 00:14:23.470 align:start position:0% you can verify yourself of chain once 00:14:23.470 --> 00:14:26.230 align:start position:0% you can verify yourself of chain once there<00:14:24.470> is<00:14:24.590> the<00:14:24.830> public<00:14:25.190> key<00:14:25.370> of<00:14:25.400> ledger<00:14:25.730> which 00:14:26.230 --> 00:14:26.240 align:start position:0% there is the public key of ledger which 00:14:26.240 --> 00:14:28.000 align:start position:0% there is the public key of ledger which is<00:14:26.420> the<00:14:26.570> one<00:14:26.720> sign<00:14:26.990> the<00:14:27.230> attestation<00:14:27.590> claim 00:14:28.000 --> 00:14:28.010 align:start position:0% is the one sign the attestation claim 00:14:28.010 --> 00:14:30.520 align:start position:0% is the one sign the attestation claim and<00:14:28.340> much<00:14:28.760> more<00:14:29.000> both<00:14:29.810> these<00:14:30.050> are<00:14:30.350> already 00:14:30.520 --> 00:14:30.530 align:start position:0% and much more both these are already 00:14:30.530 --> 00:14:33.790 align:start position:0% and much more both these are already working<00:14:30.890> on<00:14:31.160> chain<00:14:31.660> and<00:14:32.660> the<00:14:33.230> cost<00:14:33.470> is<00:14:33.620> quite 00:14:33.790 --> 00:14:33.800 align:start position:0% working on chain and the cost is quite 00:14:33.800 --> 00:14:36.130 align:start position:0% working on chain and the cost is quite reasonable<00:14:34.250> so<00:14:35.000> it's<00:14:35.120> around<00:14:35.270> the<00:14:35.600> 50 00:14:36.130 --> 00:14:36.140 align:start position:0% reasonable so it's around the 50 00:14:36.140 --> 00:14:40.240 align:start position:0% reasonable so it's around the 50 thousand<00:14:36.830> gasps<00:14:37.040> 60000<00:14:37.910> gasp<00:14:38.500> but<00:14:39.500> to<00:14:39.860> be<00:14:40.010> for 00:14:40.240 --> 00:14:40.250 align:start position:0% thousand gasps 60000 gasp but to be for 00:14:40.250 --> 00:14:42.040 align:start position:0% thousand gasps 60000 gasp but to be for bigger<00:14:40.490> proofs<00:14:40.880> where<00:14:41.210> we<00:14:41.420> have<00:14:41.570> bigger 00:14:42.040 --> 00:14:42.050 align:start position:0% bigger proofs where we have bigger 00:14:42.050 --> 00:14:44.230 align:start position:0% bigger proofs where we have bigger messages<00:14:42.650> it<00:14:42.890> might<00:14:43.100> not<00:14:43.310> be<00:14:43.490> possible<00:14:43.670> to<00:14:44.000> it 00:14:44.230 --> 00:14:44.240 align:start position:0% messages it might not be possible to it 00:14:44.240 --> 00:14:48.250 align:start position:0% messages it might not be possible to it to<00:14:44.420> do<00:14:44.540> it<00:14:44.680> so<00:14:45.680> in<00:14:46.010> those<00:14:46.160> cases<00:14:46.370> um<00:14:46.880> we<00:14:47.810> have<00:14:47.930> to 00:14:48.250 --> 00:14:48.260 align:start position:0% to do it so in those cases um we have to 00:14:48.260 --> 00:14:50.560 align:start position:0% to do it so in those cases um we have to think<00:14:49.040> of<00:14:49.250> something<00:14:49.520> different<00:14:50.150> and<00:14:50.270> this<00:14:50.390> is 00:14:50.560 --> 00:14:50.570 align:start position:0% think of something different and this is 00:14:50.570 --> 00:14:52.990 align:start position:0% think of something different and this is what<00:14:50.780> the<00:14:50.930> proof<00:14:51.140> shield<00:14:51.440> is<00:14:51.670> so<00:14:52.670> the<00:14:52.820> proof 00:14:52.990 --> 00:14:53.000 align:start position:0% what the proof shield is so the proof 00:14:53.000 --> 00:14:54.910 align:start position:0% what the proof shield is so the proof shield<00:14:53.300> is<00:14:53.510> basically<00:14:53.960> a<00:14:54.050> new<00:14:54.170> concept<00:14:54.590> where 00:14:54.910 --> 00:14:54.920 align:start position:0% shield is basically a new concept where 00:14:54.920 --> 00:14:59.080 align:start position:0% shield is basically a new concept where we<00:14:55.340> take<00:14:55.640> the<00:14:56.890> same<00:14:57.890> trust<00:14:58.220> model<00:14:58.550> that<00:14:58.970> we 00:14:59.080 --> 00:14:59.090 align:start position:0% we take the same trust model that we 00:14:59.090 --> 00:15:01.330 align:start position:0% we take the same trust model that we explained<00:14:59.420> before<00:14:59.450> we<00:15:00.230> use<00:15:00.410> exactly<00:15:00.620> the<00:15:01.070> same 00:15:01.330 --> 00:15:01.340 align:start position:0% explained before we use exactly the same 00:15:01.340 --> 00:15:04.120 align:start position:0% explained before we use exactly the same technology<00:15:01.760> to<00:15:02.240> reduce<00:15:02.930> the<00:15:03.440> complexity<00:15:03.980> of 00:15:04.120 --> 00:15:04.130 align:start position:0% technology to reduce the complexity of 00:15:04.130 --> 00:15:06.610 align:start position:0% technology to reduce the complexity of the<00:15:04.490> proof<00:15:04.670> verification<00:15:05.330> down<00:15:05.600> a<00:15:06.140> single 00:15:06.610 --> 00:15:06.620 align:start position:0% the proof verification down a single 00:15:06.620 --> 00:15:08.770 align:start position:0% the proof verification down a single signature<00:15:07.250> so<00:15:08.000> basically<00:15:08.360> this<00:15:08.570> is<00:15:08.630> a 00:15:08.770 --> 00:15:08.780 align:start position:0% signature so basically this is a 00:15:08.780 --> 00:15:11.290 align:start position:0% signature so basically this is a different<00:15:09.470> application<00:15:09.640> running<00:15:10.640> on<00:15:10.850> trusted 00:15:11.290 --> 00:15:11.300 align:start position:0% different application running on trusted 00:15:11.300 --> 00:15:14.260 align:start position:0% different application running on trusted computing<00:15:11.620> devices<00:15:12.620> or<00:15:13.070> on<00:15:13.280> other<00:15:13.520> tanks<00:15:14.120> and 00:15:14.260 --> 00:15:14.270 align:start position:0% computing devices or on other tanks and 00:15:14.270 --> 00:15:16.780 align:start position:0% computing devices or on other tanks and boxing<00:15:14.600> techniques<00:15:14.990> that<00:15:15.170> we<00:15:15.290> are<00:15:15.350> using<00:15:15.790> so 00:15:16.780 --> 00:15:16.790 align:start position:0% boxing techniques that we are using so 00:15:16.790 --> 00:15:18.730 align:start position:0% boxing techniques that we are using so that<00:15:16.820> the<00:15:17.180> complexity<00:15:17.720> of<00:15:17.750> the<00:15:17.960> proof<00:15:18.200> the 00:15:18.730 --> 00:15:18.740 align:start position:0% that the complexity of the proof the 00:15:18.740 --> 00:15:20.800 align:start position:0% that the complexity of the proof the proof<00:15:18.770> the<00:15:19.310> raw<00:15:19.460> proof<00:15:19.700> we<00:15:19.850> had<00:15:19.940> before<00:15:20.120> is<00:15:20.510> the 00:15:20.800 --> 00:15:20.810 align:start position:0% proof the raw proof we had before is the 00:15:20.810 --> 00:15:24.040 align:start position:0% proof the raw proof we had before is the input<00:15:21.020> of<00:15:21.440> this<00:15:21.800> software<00:15:22.700> and<00:15:22.910> the<00:15:23.450> output<00:15:23.870> is 00:15:24.040 --> 00:15:24.050 align:start position:0% input of this software and the output is 00:15:24.050 --> 00:15:26.410 align:start position:0% input of this software and the output is a<00:15:24.110> simple<00:15:24.680> signature<00:15:25.130> which<00:15:25.760> we<00:15:25.970> can<00:15:26.150> easily 00:15:26.410 --> 00:15:26.420 align:start position:0% a simple signature which we can easily 00:15:26.420 --> 00:15:28.990 align:start position:0% a simple signature which we can easily verify<00:15:27.100> on<00:15:28.100> the<00:15:28.280> blockchain<00:15:28.490> from<00:15:28.880> the 00:15:28.990 --> 00:15:29.000 align:start position:0% verify on the blockchain from the 00:15:29.000 --> 00:15:31.030 align:start position:0% verify on the blockchain from the calling<00:15:29.270> smart<00:15:29.510> country<00:15:29.750> like<00:15:30.320> with<00:15:30.590> native 00:15:31.030 --> 00:15:31.040 align:start position:0% calling smart country like with native 00:15:31.040 --> 00:15:33.970 align:start position:0% calling smart country like with native proofs<00:15:31.340> or<00:15:31.520> with<00:15:31.760> alleged<00:15:32.180> proof<00:15:32.590> so<00:15:33.590> in<00:15:33.800> this 00:15:33.970 --> 00:15:33.980 align:start position:0% proofs or with alleged proof so in this 00:15:33.980 --> 00:15:35.410 align:start position:0% proofs or with alleged proof so in this case<00:15:34.250> it<00:15:34.460> means<00:15:34.610> that<00:15:34.790> the<00:15:35.030> receiving 00:15:35.410 --> 00:15:35.420 align:start position:0% case it means that the receiving 00:15:35.420 --> 00:15:36.580 align:start position:0% case it means that the receiving contract 00:15:36.580 --> 00:15:36.590 align:start position:0% contract 00:15:36.590 --> 00:15:39.640 align:start position:0% contract is<00:15:36.710> not<00:15:37.130> the<00:15:37.400> raw<00:15:37.940> proof<00:15:38.270> but<00:15:39.020> the<00:15:39.290> proof 00:15:39.640 --> 00:15:39.650 align:start position:0% is not the raw proof but the proof 00:15:39.650 --> 00:15:41.560 align:start position:0% is not the raw proof but the proof shield<00:15:39.950> proof<00:15:40.220> so<00:15:40.850> it's<00:15:41.000> a<00:15:41.060> different<00:15:41.390> problem 00:15:41.560 --> 00:15:41.570 align:start position:0% shield proof so it's a different problem 00:15:41.570 --> 00:15:44.680 align:start position:0% shield proof so it's a different problem we<00:15:41.810> solve<00:15:42.080> but<00:15:42.740> when<00:15:43.190> we<00:15:43.400> keep<00:15:43.730> the<00:15:44.090> same<00:15:44.300> open 00:15:44.680 --> 00:15:44.690 align:start position:0% we solve but when we keep the same open 00:15:44.690 --> 00:15:47.920 align:start position:0% we solve but when we keep the same open trust<00:15:44.960> line<00:15:45.790> the<00:15:46.790> security<00:15:47.330> model<00:15:47.480> doesn't 00:15:47.920 --> 00:15:47.930 align:start position:0% trust line the security model doesn't 00:15:47.930 --> 00:15:50.760 align:start position:0% trust line the security model doesn't really<00:15:48.050> change<00:15:48.140> so<00:15:49.040> for<00:15:49.160> example<00:15:49.700> if<00:15:49.940> we<00:15:50.390> have 00:15:50.760 --> 00:15:50.770 align:start position:0% really change so for example if we have 00:15:50.770 --> 00:15:53.830 align:start position:0% really change so for example if we have TLS<00:15:51.770> not<00:15:51.980> reproof<00:15:52.490> which<00:15:52.790> is<00:15:52.970> based<00:15:53.240> at<00:15:53.810> the 00:15:53.830 --> 00:15:53.840 align:start position:0% TLS not reproof which is based at the 00:15:53.840 --> 00:15:56.200 align:start position:0% TLS not reproof which is based at the end<00:15:54.170> of<00:15:54.320> the<00:15:54.440> day<00:15:54.590> given<00:15:55.010> its<00:15:55.160> nature<00:15:55.700> to 00:15:56.200 --> 00:15:56.210 align:start position:0% end of the day given its nature to 00:15:56.210 --> 00:15:58.090 align:start position:0% end of the day given its nature to unopened<00:15:56.900> restrain<00:15:57.320> with<00:15:57.500> Amazon<00:15:58.070> Web 00:15:58.090 --> 00:15:58.100 align:start position:0% unopened restrain with Amazon Web 00:15:58.100 --> 00:16:01.770 align:start position:0% unopened restrain with Amazon Web service<00:15:58.610> well<00:15:59.120> if<00:15:59.420> we<00:15:59.750> somehow<00:16:00.020> leverage<00:16:00.710> a 00:16:01.770 --> 00:16:01.780 align:start position:0% service well if we somehow leverage a 00:16:01.780 --> 00:16:05.140 align:start position:0% service well if we somehow leverage a fully<00:16:02.780> lockdown<00:16:03.290> approvable<00:16:04.150> machine 00:16:05.140 --> 00:16:05.150 align:start position:0% fully lockdown approvable machine 00:16:05.150 --> 00:16:07.120 align:start position:0% fully lockdown approvable machine running<00:16:05.540> on<00:16:05.660> amazon<00:16:06.110> web<00:16:06.260> service<00:16:06.680> which 00:16:07.120 --> 00:16:07.130 align:start position:0% running on amazon web service which 00:16:07.130 --> 00:16:09.430 align:start position:0% running on amazon web service which converts<00:16:07.670> this<00:16:07.970> proof<00:16:08.330> to<00:16:08.630> a<00:16:08.990> single 00:16:09.430 --> 00:16:09.440 align:start position:0% converts this proof to a single 00:16:09.440 --> 00:16:11.850 align:start position:0% converts this proof to a single signature<00:16:09.980> then<00:16:10.550> we<00:16:10.790> are<00:16:10.880> still<00:16:11.150> trusting 00:16:11.850 --> 00:16:11.860 align:start position:0% signature then we are still trusting 00:16:11.860 --> 00:16:14.320 align:start position:0% signature then we are still trusting Amazon<00:16:12.860> for<00:16:13.190> that<00:16:13.370> convention<00:16:13.910> for<00:16:14.120> that 00:16:14.320 --> 00:16:14.330 align:start position:0% Amazon for that convention for that 00:16:14.330 --> 00:16:16.690 align:start position:0% Amazon for that convention for that transformation<00:16:15.290> and<00:16:15.410> the<00:16:16.340> optional 00:16:16.690 --> 00:16:16.700 align:start position:0% transformation and the optional 00:16:16.700 --> 00:16:18.820 align:start position:0% transformation and the optional verifications<00:16:17.300> becomes<00:16:17.690> possible<00:16:17.930> though<00:16:18.350> so 00:16:18.820 --> 00:16:18.830 align:start position:0% verifications becomes possible though so 00:16:18.830 --> 00:16:20.400 align:start position:0% verifications becomes possible though so this<00:16:18.950> is<00:16:19.070> something<00:16:19.280> we<00:16:19.460> have<00:16:19.580> written<00:16:19.940> in<00:16:20.060> C 00:16:20.400 --> 00:16:20.410 align:start position:0% this is something we have written in C 00:16:20.410 --> 00:16:23.440 align:start position:0% this is something we have written in C is<00:16:21.410> quite<00:16:21.880> modular<00:16:22.880> and<00:16:23.030> portable 00:16:23.440 --> 00:16:23.450 align:start position:0% is quite modular and portable 00:16:23.450 --> 00:16:24.790 align:start position:0% is quite modular and portable architecture<00:16:23.930> you<00:16:24.020> can<00:16:24.050> run<00:16:24.350> in<00:16:24.470> different 00:16:24.790 --> 00:16:24.800 align:start position:0% architecture you can run in different 00:16:24.800 --> 00:16:26.620 align:start position:0% architecture you can run in different contexts<00:16:25.190> --is<00:16:25.370> it<00:16:25.640> will<00:16:25.970> be<00:16:26.120> open<00:16:26.360> sourced 00:16:26.620 --> 00:16:26.630 align:start position:0% contexts --is it will be open sourced 00:16:26.630 --> 00:16:27.220 align:start position:0% contexts --is it will be open sourced very<00:16:26.780> soon 00:16:27.220 --> 00:16:27.230 align:start position:0% very soon 00:16:27.230 --> 00:16:29.260 align:start position:0% very soon it<00:16:27.380> supports<00:16:28.130> basically<00:16:28.610> all<00:16:28.820> the<00:16:29.030> existing 00:16:29.260 --> 00:16:29.270 align:start position:0% it supports basically all the existing 00:16:29.270 --> 00:16:31.360 align:start position:0% it supports basically all the existing proofs<00:16:29.750> provided<00:16:30.230> by<00:16:30.350> Oracle<00:16:30.440> eyes<00:16:30.740> so<00:16:31.130> all 00:16:31.360 --> 00:16:31.370 align:start position:0% proofs provided by Oracle eyes so all 00:16:31.370 --> 00:16:34.090 align:start position:0% proofs provided by Oracle eyes so all you<00:16:31.640> could<00:16:31.820> put<00:16:32.030> actually<00:16:32.450> use<00:16:33.020> I<00:16:33.320> don't<00:16:34.040> know 00:16:34.090 --> 00:16:34.100 align:start position:0% you could put actually use I don't know 00:16:34.100 --> 00:16:37.540 align:start position:0% you could put actually use I don't know like<00:16:34.780> ledger<00:16:35.780> device<00:16:36.320> to<00:16:37.010> run<00:16:37.190> the<00:16:37.340> proof 00:16:37.540 --> 00:16:37.550 align:start position:0% like ledger device to run the proof 00:16:37.550 --> 00:16:40.960 align:start position:0% like ledger device to run the proof sheet<00:16:37.790> to<00:16:38.300> verify<00:16:38.690> an<00:16:38.990> android<00:16:39.320> proof<00:16:39.850> but<00:16:40.850> of 00:16:40.960 --> 00:16:40.970 align:start position:0% sheet to verify an android proof but of 00:16:40.970 --> 00:16:42.130 align:start position:0% sheet to verify an android proof but of course<00:16:41.210> in<00:16:41.330> that<00:16:41.420> case<00:16:41.480> you<00:16:41.780> open<00:16:41.990> a<00:16:42.020> new 00:16:42.130 --> 00:16:42.140 align:start position:0% course in that case you open a new 00:16:42.140 --> 00:16:43.570 align:start position:0% course in that case you open a new additional<00:16:42.440> trust<00:16:42.710> range<00:16:42.950> so<00:16:43.070> the<00:16:43.190> optimal 00:16:43.570 --> 00:16:43.580 align:start position:0% additional trust range so the optimal 00:16:43.580 --> 00:16:45.040 align:start position:0% additional trust range so the optimal case<00:16:43.760> is<00:16:43.940> going<00:16:44.090> to<00:16:44.180> use<00:16:44.330> exactly<00:16:44.540> the<00:16:44.870> same 00:16:45.040 --> 00:16:45.050 align:start position:0% case is going to use exactly the same 00:16:45.050 --> 00:16:48.100 align:start position:0% case is going to use exactly the same technology<00:16:45.350> and<00:16:46.090> the<00:16:47.090> first<00:16:47.300> prototype<00:16:47.750> will 00:16:48.100 --> 00:16:48.110 align:start position:0% technology and the first prototype will 00:16:48.110 --> 00:16:50.500 align:start position:0% technology and the first prototype will be<00:16:48.140> released<00:16:48.620> on<00:16:48.860> test<00:16:49.370> net<00:16:49.610> before<00:16:50.120> the<00:16:50.390> end 00:16:50.500 --> 00:16:50.510 align:start position:0% be released on test net before the end 00:16:50.510 --> 00:16:52.960 align:start position:0% be released on test net before the end of<00:16:50.600> year<00:16:50.780> and<00:16:51.160> it's<00:16:52.160> in<00:16:52.400> the<00:16:52.700> first 00:16:52.960 --> 00:16:52.970 align:start position:0% of year and it's in the first 00:16:52.970 --> 00:16:55.060 align:start position:0% of year and it's in the first implementation<00:16:53.210> will<00:16:53.990> be<00:16:54.140> based<00:16:54.350> on<00:16:54.560> as<00:16:55.010> a 00:16:55.060 --> 00:16:55.070 align:start position:0% implementation will be based on as a 00:16:55.070 --> 00:16:57.940 align:start position:0% implementation will be based on as a bolus<00:16:55.460> up<00:16:55.670> so<00:16:56.330> basically<00:16:56.690> it's<00:16:57.410> running<00:16:57.770> on<00:16:57.920> a 00:16:57.940 --> 00:16:57.950 align:start position:0% bolus up so basically it's running on a 00:16:57.950 --> 00:17:01.330 align:start position:0% bolus up so basically it's running on a ledger<00:16:58.340> device<00:16:58.790> and<00:16:59.590> the<00:17:00.590> verification<00:17:00.860> cost 00:17:01.330 --> 00:17:01.340 align:start position:0% ledger device and the verification cost 00:17:01.340 --> 00:17:04.030 align:start position:0% ledger device and the verification cost again<00:17:01.670> are<00:17:02.030> in<00:17:02.240> the<00:17:02.450> fifty<00:17:02.900> sixty<00:17:03.530> thousand 00:17:04.030 --> 00:17:04.040 align:start position:0% again are in the fifty sixty thousand 00:17:04.040 --> 00:17:06.310 align:start position:0% again are in the fifty sixty thousand gas<00:17:04.190> range<00:17:04.490> and<00:17:04.790> it<00:17:05.360> can<00:17:05.540> be<00:17:05.690> reduced<00:17:06.020> even 00:17:06.310 --> 00:17:06.320 align:start position:0% gas range and it can be reduced even 00:17:06.320 --> 00:17:10.630 align:start position:0% gas range and it can be reduced even more<00:17:06.500> so<00:17:07.040> that<00:17:07.250> basically<00:17:08.290> the<00:17:09.640> transaction 00:17:10.630 --> 00:17:10.640 align:start position:0% more so that basically the transaction 00:17:10.640 --> 00:17:12.670 align:start position:0% more so that basically the transaction verification<00:17:10.910> itself<00:17:11.750> so<00:17:12.170> the<00:17:12.290> signature 00:17:12.670 --> 00:17:12.680 align:start position:0% verification itself so the signature 00:17:12.680 --> 00:17:14.470 align:start position:0% verification itself so the signature showing<00:17:13.160> that<00:17:13.280> transaction<00:17:13.910> is<00:17:14.030> coming<00:17:14.360> from 00:17:14.470 --> 00:17:14.480 align:start position:0% showing that transaction is coming from 00:17:14.480 --> 00:17:17.800 align:start position:0% showing that transaction is coming from a<00:17:14.600> given<00:17:15.020> sender<00:17:15.700> it<00:17:16.700> can<00:17:17.090> be<00:17:17.330> a<00:17:17.360> ready<00:17:17.660> the 00:17:17.800 --> 00:17:17.810 align:start position:0% a given sender it can be a ready the 00:17:17.810 --> 00:17:19.900 align:start position:0% a given sender it can be a ready the verification<00:17:18.410> step<00:17:18.650> so<00:17:18.920> in<00:17:19.220> a<00:17:19.310> version<00:17:19.700> two<00:17:19.880> of 00:17:19.900 --> 00:17:19.910 align:start position:0% verification step so in a version two of 00:17:19.910 --> 00:17:20.620 align:start position:0% verification step so in a version two of the<00:17:20.030> proshield 00:17:20.620 --> 00:17:20.630 align:start position:0% the proshield 00:17:20.630 --> 00:17:22.840 align:start position:0% the proshield we<00:17:20.959> will<00:17:21.140> be<00:17:21.260> able<00:17:21.500> to<00:17:21.620> reduce<00:17:21.980> down<00:17:22.280> the<00:17:22.340> cost 00:17:22.840 --> 00:17:22.850 align:start position:0% we will be able to reduce down the cost 00:17:22.850 --> 00:17:25.150 align:start position:0% we will be able to reduce down the cost of<00:17:23.090> the<00:17:23.570> proof<00:17:23.780> sheet<00:17:23.990> proof<00:17:24.230> verification<00:17:24.890> to 00:17:25.150 --> 00:17:25.160 align:start position:0% of the proof sheet proof verification to 00:17:25.160 --> 00:17:28.600 align:start position:0% of the proof sheet proof verification to basically<00:17:25.640> zero<00:17:26.260> so<00:17:27.260> that<00:17:27.500> is<00:17:27.770> also<00:17:28.130> a<00:17:28.370> really 00:17:28.600 --> 00:17:28.610 align:start position:0% basically zero so that is also a really 00:17:28.610 --> 00:17:30.010 align:start position:0% basically zero so that is also a really compatible<00:17:28.910> with<00:17:29.390> a<00:17:29.420> ready<00:17:29.690> deployed 00:17:30.010 --> 00:17:30.020 align:start position:0% compatible with a ready deployed 00:17:30.020 --> 00:17:33.280 align:start position:0% compatible with a ready deployed contract<00:17:30.530> which<00:17:30.860> now<00:17:31.160> are<00:17:31.640> several<00:17:32.540> hundreds 00:17:33.280 --> 00:17:33.290 align:start position:0% contract which now are several hundreds 00:17:33.290 --> 00:17:38.140 align:start position:0% contract which now are several hundreds on<00:17:33.470> the<00:17:33.950> main<00:17:34.130> chain<00:17:34.900> so<00:17:35.900> so<00:17:36.470> far<00:17:36.730> we<00:17:37.730> are<00:17:37.760> the 00:17:38.140 --> 00:17:38.150 align:start position:0% on the main chain so so far we are the 00:17:38.150 --> 00:17:40.270 align:start position:0% on the main chain so so far we are the most<00:17:38.660> widely<00:17:38.930> used<00:17:39.110> Oracle<00:17:39.800> service<00:17:40.100> on<00:17:40.190> the 00:17:40.270 --> 00:17:40.280 align:start position:0% most widely used Oracle service on the 00:17:40.280 --> 00:17:41.770 align:start position:0% most widely used Oracle service on the blockchain<00:17:40.460> we<00:17:40.760> yes<00:17:41.000> and<00:17:41.300> three<00:17:41.720> hundred 00:17:41.770 --> 00:17:41.780 align:start position:0% blockchain we yes and three hundred 00:17:41.780 --> 00:17:44.350 align:start position:0% blockchain we yes and three hundred thousand<00:17:42.770> over<00:17:43.400> three<00:17:43.550> hundred<00:17:43.610> thousand 00:17:44.350 --> 00:17:44.360 align:start position:0% thousand over three hundred thousand 00:17:44.360 --> 00:17:47.980 align:start position:0% thousand over three hundred thousand queries<00:17:44.750> on<00:17:44.930> the<00:17:45.470> main<00:17:45.650> net<00:17:45.860> and<00:17:46.390> today<00:17:47.390> the 00:17:47.980 --> 00:17:47.990 align:start position:0% queries on the main net and today the 00:17:47.990 --> 00:17:49.900 align:start position:0% queries on the main net and today the range<00:17:48.200> is<00:17:48.470> typically<00:17:48.950> between<00:17:49.160> one<00:17:49.550> and<00:17:49.580> five 00:17:49.900 --> 00:17:49.910 align:start position:0% range is typically between one and five 00:17:49.910 --> 00:17:50.420 align:start position:0% range is typically between one and five thousand 00:17:50.420 --> 00:17:50.430 align:start position:0% thousand 00:17:50.430 --> 00:17:52.400 align:start position:0% thousand the<00:17:50.550> transactions<00:17:51.150> per<00:17:51.330> day<00:17:51.540> on<00:17:51.870> the<00:17:52.110> main<00:17:52.230> not 00:17:52.400 --> 00:17:52.410 align:start position:0% the transactions per day on the main not 00:17:52.410 --> 00:17:54.350 align:start position:0% the transactions per day on the main not only<00:17:52.740> we<00:17:53.250> have<00:17:53.280> integrations<00:17:53.910> also<00:17:54.210> with 00:17:54.350 --> 00:17:54.360 align:start position:0% only we have integrations also with 00:17:54.360 --> 00:17:56.360 align:start position:0% only we have integrations also with other<00:17:54.600> blockchains<00:17:55.260> as<00:17:55.350> you<00:17:55.800> can<00:17:55.950> see<00:17:56.100> here 00:17:56.360 --> 00:17:56.370 align:start position:0% other blockchains as you can see here 00:17:56.370 --> 00:17:59.060 align:start position:0% other blockchains as you can see here but<00:17:57.240> a<00:17:57.450> Tyrian<00:17:57.840> is<00:17:58.200> where<00:17:58.500> we<00:17:58.650> started<00:17:59.010> from 00:17:59.060 --> 00:17:59.070 align:start position:0% but a Tyrian is where we started from 00:17:59.070 --> 00:18:01.220 align:start position:0% but a Tyrian is where we started from and<00:17:59.700> where<00:18:00.030> most<00:18:00.330> of<00:18:00.450> the<00:18:00.630> usage<00:18:00.960> at<00:18:01.110> the 00:18:01.220 --> 00:18:01.230 align:start position:0% and where most of the usage at the 00:18:01.230 --> 00:18:04.780 align:start position:0% and where most of the usage at the moment<00:18:01.500> comes<00:18:01.710> from<00:18:02.930> we<00:18:03.930> are<00:18:04.230> using<00:18:04.500> different 00:18:04.780 --> 00:18:04.790 align:start position:0% moment comes from we are using different 00:18:04.790 --> 00:18:06.830 align:start position:0% moment comes from we are using different technologies<00:18:05.790> and<00:18:05.820> attestation<00:18:06.390> techniques 00:18:06.830 --> 00:18:06.840 align:start position:0% technologies and attestation techniques 00:18:06.840 --> 00:18:08.300 align:start position:0% technologies and attestation techniques and<00:18:07.020> this<00:18:07.140> is<00:18:07.260> something<00:18:07.470> that<00:18:07.740> we<00:18:07.860> still<00:18:08.190> have 00:18:08.300 --> 00:18:08.310 align:start position:0% and this is something that we still have 00:18:08.310 --> 00:18:09.890 align:start position:0% and this is something that we still have in<00:18:08.340> the<00:18:08.520> working<00:18:08.940> sister<00:18:09.300> continues<00:18:09.720> the 00:18:09.890 --> 00:18:09.900 align:start position:0% in the working sister continues the 00:18:09.900 --> 00:18:12.950 align:start position:0% in the working sister continues the research<00:18:10.290> problem<00:18:10.850> so<00:18:11.850> these<00:18:12.180> are<00:18:12.450> the<00:18:12.750> things 00:18:12.950 --> 00:18:12.960 align:start position:0% research problem so these are the things 00:18:12.960 --> 00:18:14.990 align:start position:0% research problem so these are the things we<00:18:13.140> have<00:18:13.440> in<00:18:13.590> the<00:18:13.710> working<00:18:14.010> for<00:18:14.190> the<00:18:14.280> future<00:18:14.640> so 00:18:14.990 --> 00:18:15.000 align:start position:0% we have in the working for the future so 00:18:15.000 --> 00:18:16.670 align:start position:0% we have in the working for the future so basically<00:18:15.480> we<00:18:15.660> will<00:18:15.780> facilitate<00:18:16.020> with 00:18:16.670 --> 00:18:16.680 align:start position:0% basically we will facilitate with 00:18:16.680 --> 00:18:20.540 align:start position:0% basically we will facilitate with Stargate<00:18:17.480> D<00:18:18.480> using<00:18:18.750> private<00:18:19.140> chains<00:18:19.590> and<00:18:20.070> for 00:18:20.540 --> 00:18:20.550 align:start position:0% Stargate D using private chains and for 00:18:20.550 --> 00:18:23.120 align:start position:0% Stargate D using private chains and for in-memory<00:18:20.790> executions<00:18:21.600> and<00:18:21.750> simulations<00:18:22.290> the 00:18:23.120 --> 00:18:23.130 align:start position:0% in-memory executions and simulations the 00:18:23.130 --> 00:18:24.800 align:start position:0% in-memory executions and simulations the proof<00:18:23.430> shield<00:18:23.700> I've<00:18:24.120> already<00:18:24.480> talked<00:18:24.690> about 00:18:24.800 --> 00:18:24.810 align:start position:0% proof shield I've already talked about 00:18:24.810 --> 00:18:27.410 align:start position:0% proof shield I've already talked about the<00:18:25.350> decimal<00:18:25.950> deployment<00:18:26.460> and<00:18:26.730> the<00:18:27.150> version 00:18:27.410 --> 00:18:27.420 align:start position:0% the decimal deployment and the version 00:18:27.420 --> 00:18:29.140 align:start position:0% the decimal deployment and the version show<00:18:27.750> that<00:18:27.930> we<00:18:28.020> have<00:18:28.110> in<00:18:28.200> the<00:18:28.290> workings<00:18:28.680> and 00:18:29.140 --> 00:18:29.150 align:start position:0% show that we have in the workings and 00:18:29.150 --> 00:18:32.330 align:start position:0% show that we have in the workings and Newton<00:18:30.150> disapproves<00:18:30.800> the<00:18:31.800> reduce<00:18:32.190> the 00:18:32.330 --> 00:18:32.340 align:start position:0% Newton disapproves the reduce the 00:18:32.340 --> 00:18:34.190 align:start position:0% Newton disapproves the reduce the centralization<00:18:32.760> points<00:18:33.420> of<00:18:33.540> the<00:18:33.690> operators 00:18:34.190 --> 00:18:34.200 align:start position:0% centralization points of the operators 00:18:34.200 --> 00:18:37.010 align:start position:0% centralization points of the operators of<00:18:34.380> us<00:18:34.830> of<00:18:35.190> our<00:18:35.340> service<00:18:35.850> via<00:18:36.330> the<00:18:36.540> delegation 00:18:37.010 --> 00:18:37.020 align:start position:0% of us of our service via the delegation 00:18:37.020 --> 00:18:39.080 align:start position:0% of us of our service via the delegation of<00:18:37.110> the<00:18:37.260> management<00:18:37.590> machines<00:18:38.130> to<00:18:38.610> external 00:18:39.080 --> 00:18:39.090 align:start position:0% of the management machines to external 00:18:39.090 --> 00:18:41.120 align:start position:0% of the management machines to external nodes<00:18:39.270> and<00:18:39.950> tomorrow 00:18:41.120 --> 00:18:41.130 align:start position:0% nodes and tomorrow 00:18:41.130 --> 00:18:45.050 align:start position:0% nodes and tomorrow downstairs<00:18:42.090> in<00:18:42.390> the<00:18:42.450> breakout<00:18:42.960> hall<00:18:43.380> at<00:18:44.060> 3:45 00:18:45.050 --> 00:18:45.060 align:start position:0% downstairs in the breakout hall at 3:45 00:18:45.060 --> 00:18:47.780 align:start position:0% downstairs in the breakout hall at 3:45 p.m.<00:18:45.090> I<00:18:45.600> will<00:18:45.720> do<00:18:46.110> a<00:18:46.140> deep<00:18:46.500> dive<00:18:46.530> around<00:18:47.520> the 00:18:47.780 --> 00:18:47.790 align:start position:0% p.m. I will do a deep dive around the 00:18:47.790 --> 00:18:50.120 align:start position:0% p.m. I will do a deep dive around the oracle<00:18:48.270> eyes<00:18:48.360> offering<00:18:48.870> computations<00:18:49.530> and<00:18:49.680> i 00:18:50.120 --> 00:18:50.130 align:start position:0% oracle eyes offering computations and i 00:18:50.130 --> 00:18:51.980 align:start position:0% oracle eyes offering computations and i will<00:18:50.340> show<00:18:50.520> you<00:18:50.580> something<00:18:51.060> which<00:18:51.420> is<00:18:51.690> quite 00:18:51.980 --> 00:18:51.990 align:start position:0% will show you something which is quite 00:18:51.990 --> 00:18:55.460 align:start position:0% will show you something which is quite interesting<00:18:52.560> or<00:18:52.710> the<00:18:53.690> using<00:18:54.690> of<00:18:54.780> this<00:18:55.200> the 00:18:55.460 --> 00:18:55.470 align:start position:0% interesting or the using of this the 00:18:55.470 --> 00:18:57.410 align:start position:0% interesting or the using of this the same<00:18:55.710> technologies<00:18:56.400> and<00:18:56.670> the<00:18:56.880> same<00:18:57.120> trust 00:18:57.410 --> 00:18:57.420 align:start position:0% same technologies and the same trust 00:18:57.420 --> 00:19:00.830 align:start position:0% same technologies and the same trust model<00:18:57.840> to<00:18:58.700> execute<00:18:59.700> obtain<00:19:00.150> any<00:19:00.390> piece<00:19:00.660> of 00:19:00.830 --> 00:19:00.840 align:start position:0% model to execute obtain any piece of 00:19:00.840 --> 00:19:02.510 align:start position:0% model to execute obtain any piece of code<00:19:01.080> and<00:19:01.320> say<00:19:01.470> no<00:19:01.530> change<00:19:01.860> as<00:19:02.040> the<00:19:02.220> result 00:19:02.510 --> 00:19:02.520 align:start position:0% code and say no change as the result 00:19:02.520 --> 00:19:04.790 align:start position:0% code and say no change as the result also<00:19:02.790> for<00:19:03.180> like<00:19:03.420> non-deterministic<00:19:04.260> pieces 00:19:04.790 --> 00:19:04.800 align:start position:0% also for like non-deterministic pieces 00:19:04.800 --> 00:19:05.300 align:start position:0% also for like non-deterministic pieces of<00:19:04.920> code 00:19:05.300 --> 00:19:05.310 align:start position:0% of code 00:19:05.310 --> 00:19:12.150 align:start position:0% of code thank<00:19:05.970> you<00:19:06.030> for<00:19:06.150> attention 00:19:12.150 --> 00:19:12.160 align:start position:0% 00:19:12.160 --> 00:19:19.739 align:start position:0% [Music]