WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:15.089 align:start position:0% [Music] 00:00:15.089 --> 00:00:15.099 align:start position:0% [Music] 00:00:15.099 --> 00:00:20.579 align:start position:0% [Music] thanks.thanks<00:00:16.000> me<00:00:16.570> hi<00:00:17.080> everyone<00:00:17.769> so<00:00:18.929> the<00:00:19.929> the 00:00:20.579 --> 00:00:20.589 align:start position:0% thanks.thanks me hi everyone so the the 00:00:20.589 --> 00:00:22.679 align:start position:0% thanks.thanks me hi everyone so the the problem<00:00:20.980> that<00:00:21.130> we're<00:00:21.310> we're<00:00:21.730> focusing<00:00:22.239> on<00:00:22.390> is 00:00:22.679 --> 00:00:22.689 align:start position:0% problem that we're we're focusing on is 00:00:22.689 --> 00:00:26.450 align:start position:0% problem that we're we're focusing on is one<00:00:23.109> which<00:00:23.289> we<00:00:23.470> think<00:00:23.999> keep<00:00:24.999> smart<00:00:25.390> contracts 00:00:26.450 --> 00:00:26.460 align:start position:0% one which we think keep smart contracts 00:00:26.460 --> 00:00:30.210 align:start position:0% one which we think keep smart contracts limited<00:00:27.460> to<00:00:27.609> tokenization<00:00:27.999> right<00:00:28.749> if<00:00:29.470> the 00:00:30.210 --> 00:00:30.220 align:start position:0% limited to tokenization right if the 00:00:30.220 --> 00:00:31.859 align:start position:0% limited to tokenization right if the native<00:00:30.489> functionality<00:00:30.880> you<00:00:31.149> have<00:00:31.179> when<00:00:31.779> you 00:00:31.859 --> 00:00:31.869 align:start position:0% native functionality you have when you 00:00:31.869 --> 00:00:32.940 align:start position:0% native functionality you have when you start<00:00:31.929> working<00:00:32.290> with<00:00:32.410> a<00:00:32.529> smart<00:00:32.800> contract 00:00:32.940 --> 00:00:32.950 align:start position:0% start working with a smart contract 00:00:32.950 --> 00:00:35.550 align:start position:0% start working with a smart contract network<00:00:33.940> is<00:00:34.120> the<00:00:34.240> ability<00:00:34.450> to<00:00:34.630> make<00:00:34.840> tokens 00:00:35.550 --> 00:00:35.560 align:start position:0% network is the ability to make tokens 00:00:35.560 --> 00:00:37.320 align:start position:0% network is the ability to make tokens that's<00:00:36.340> the<00:00:36.490> functionality<00:00:37.030> you'll<00:00:37.150> start 00:00:37.320 --> 00:00:37.330 align:start position:0% that's the functionality you'll start 00:00:37.330 --> 00:00:38.370 align:start position:0% that's the functionality you'll start working<00:00:37.630> with<00:00:37.750> and<00:00:37.900> you'll<00:00:37.990> do<00:00:38.110> a<00:00:38.140> lot<00:00:38.260> of 00:00:38.370 --> 00:00:38.380 align:start position:0% working with and you'll do a lot of 00:00:38.380 --> 00:00:40.380 align:start position:0% working with and you'll do a lot of interesting<00:00:38.710> things<00:00:38.770> with<00:00:39.130> it<00:00:39.250> but<00:00:39.460> the 00:00:40.380 --> 00:00:40.390 align:start position:0% interesting things with it but the 00:00:40.390 --> 00:00:42.330 align:start position:0% interesting things with it but the capabilities<00:00:40.990> of<00:00:41.020> smart<00:00:41.380> contracts<00:00:41.920> go<00:00:42.040> far 00:00:42.330 --> 00:00:42.340 align:start position:0% capabilities of smart contracts go far 00:00:42.340 --> 00:00:44.310 align:start position:0% capabilities of smart contracts go far beyond<00:00:42.610> to<00:00:42.760> organization<00:00:43.360> there's<00:00:44.050> enough 00:00:44.310 --> 00:00:44.320 align:start position:0% beyond to organization there's enough 00:00:44.320 --> 00:00:46.260 align:start position:0% beyond to organization there's enough logic<00:00:44.770> to<00:00:44.950> mimic<00:00:45.310> and<00:00:45.520> eventually<00:00:45.880> replace 00:00:46.260 --> 00:00:46.270 align:start position:0% logic to mimic and eventually replace 00:00:46.270 --> 00:00:48.450 align:start position:0% logic to mimic and eventually replace the<00:00:46.930> majority<00:00:47.500> of<00:00:47.530> digital<00:00:48.010> financial 00:00:48.450 --> 00:00:48.460 align:start position:0% the majority of digital financial 00:00:48.460 --> 00:00:51.780 align:start position:0% the majority of digital financial agreements<00:00:48.930> those<00:00:49.930> agreements<00:00:50.680> as<00:00:51.430> they're 00:00:51.780 --> 00:00:51.790 align:start position:0% agreements those agreements as they're 00:00:51.790 --> 00:00:54.540 align:start position:0% agreements those agreements as they're structured<00:00:52.330> will<00:00:53.230> need<00:00:53.470> triggering<00:00:54.190> events 00:00:54.540 --> 00:00:54.550 align:start position:0% structured will need triggering events 00:00:54.550 --> 00:00:56.160 align:start position:0% structured will need triggering events so<00:00:54.910> they'll<00:00:55.060> need<00:00:55.180> inputs<00:00:55.630> into<00:00:56.050> the 00:00:56.160 --> 00:00:56.170 align:start position:0% so they'll need inputs into the 00:00:56.170 --> 00:00:58.470 align:start position:0% so they'll need inputs into the application<00:00:56.770> and<00:00:56.980> they<00:00:57.700> also<00:00:57.910> need<00:00:58.270> to<00:00:58.300> have 00:00:58.470 --> 00:00:58.480 align:start position:0% application and they also need to have 00:00:58.480 --> 00:01:02.010 align:start position:0% application and they also need to have outputs<00:00:59.079> as<00:00:59.350> a<00:00:59.710> form<00:01:00.010> of<00:01:00.100> payment<00:01:00.310> right<00:01:01.239> so<00:01:01.960> in 00:01:02.010 --> 00:01:02.020 align:start position:0% outputs as a form of payment right so in 00:01:02.020 --> 00:01:04.170 align:start position:0% outputs as a form of payment right so in our<00:01:02.110> opinion<00:01:02.579> one<00:01:03.579> of<00:01:03.670> the<00:01:03.760> very<00:01:03.970> large 00:01:04.170 --> 00:01:04.180 align:start position:0% our opinion one of the very large 00:01:04.180 --> 00:01:06.389 align:start position:0% our opinion one of the very large limiting<00:01:04.509> factors<00:01:04.930> for<00:01:05.350> the<00:01:05.950> creation<00:01:06.219> of 00:01:06.389 --> 00:01:06.399 align:start position:0% limiting factors for the creation of 00:01:06.399 --> 00:01:09.209 align:start position:0% limiting factors for the creation of interesting<00:01:07.409> real-world<00:01:08.409> use<00:01:08.649> case<00:01:08.890> smart 00:01:09.209 --> 00:01:09.219 align:start position:0% interesting real-world use case smart 00:01:09.219 --> 00:01:11.190 align:start position:0% interesting real-world use case smart contracts<00:01:09.880> is<00:01:10.030> their<00:01:10.479> ability<00:01:10.689> to<00:01:10.990> step 00:01:11.190 --> 00:01:11.200 align:start position:0% contracts is their ability to step 00:01:11.200 --> 00:01:13.709 align:start position:0% contracts is their ability to step beyond<00:01:11.560> tokens<00:01:12.039> and<00:01:12.280> interact<00:01:13.149> with<00:01:13.420> external 00:01:13.709 --> 00:01:13.719 align:start position:0% beyond tokens and interact with external 00:01:13.719 --> 00:01:16.289 align:start position:0% beyond tokens and interact with external inputs<00:01:14.469> and<00:01:14.740> external<00:01:15.490> outputs<00:01:15.909> in<00:01:16.179> a 00:01:16.289 --> 00:01:16.299 align:start position:0% inputs and external outputs in a 00:01:16.299 --> 00:01:19.919 align:start position:0% inputs and external outputs in a meaningful<00:01:16.569> manner<00:01:16.840> right<00:01:17.819> so<00:01:18.819> the<00:01:19.659> approach 00:01:19.919 --> 00:01:19.929 align:start position:0% meaningful manner right so the approach 00:01:19.929 --> 00:01:21.749 align:start position:0% meaningful manner right so the approach to<00:01:20.139> solving<00:01:20.409> that<00:01:20.530> problem<00:01:20.710> is<00:01:21.219> basically 00:01:21.749 --> 00:01:21.759 align:start position:0% to solving that problem is basically 00:01:21.759 --> 00:01:24.029 align:start position:0% to solving that problem is basically middleware<00:01:22.469> you<00:01:23.469> create<00:01:23.710> a<00:01:23.740> piece<00:01:23.920> of 00:01:24.029 --> 00:01:24.039 align:start position:0% middleware you create a piece of 00:01:24.039 --> 00:01:25.800 align:start position:0% middleware you create a piece of middleware<00:01:24.219> that<00:01:24.850> takes<00:01:25.119> the<00:01:25.389> external 00:01:25.800 --> 00:01:25.810 align:start position:0% middleware that takes the external 00:01:25.810 --> 00:01:27.690 align:start position:0% middleware that takes the external inputs<00:01:26.139> turns<00:01:26.920> them<00:01:27.130> into<00:01:27.189> something<00:01:27.549> that 00:01:27.690 --> 00:01:27.700 align:start position:0% inputs turns them into something that 00:01:27.700 --> 00:01:30.270 align:start position:0% inputs turns them into something that the<00:01:28.170> contract<00:01:29.170> Unchained<00:01:29.590> can<00:01:29.710> interact<00:01:30.069> with 00:01:30.270 --> 00:01:30.280 align:start position:0% the contract Unchained can interact with 00:01:30.280 --> 00:01:32.760 align:start position:0% the contract Unchained can interact with and<00:01:30.490> you<00:01:30.939> have<00:01:31.179> the<00:01:31.450> middleware<00:01:32.289> provide 00:01:32.760 --> 00:01:32.770 align:start position:0% and you have the middleware provide 00:01:32.770 --> 00:01:34.980 align:start position:0% and you have the middleware provide those<00:01:32.979> inputs<00:01:33.399> to<00:01:33.549> the<00:01:33.639> contract<00:01:34.149> those 00:01:34.980 --> 00:01:34.990 align:start position:0% those inputs to the contract those 00:01:34.990 --> 00:01:37.770 align:start position:0% those inputs to the contract those inputs<00:01:35.380> can<00:01:35.560> be<00:01:35.590> any<00:01:36.310> kind<00:01:36.549> of<00:01:36.639> data<00:01:36.850> feed<00:01:37.149> IOT 00:01:37.770 --> 00:01:37.780 align:start position:0% inputs can be any kind of data feed IOT 00:01:37.780 --> 00:01:41.129 align:start position:0% inputs can be any kind of data feed IOT input<00:01:38.530> about<00:01:38.770> delivery<00:01:39.310> any<00:01:39.639> any<00:01:39.939> input<00:01:40.450> that 00:01:41.129 --> 00:01:41.139 align:start position:0% input about delivery any any input that 00:01:41.139 --> 00:01:44.849 align:start position:0% input about delivery any any input that application<00:01:42.009> needs<00:01:43.679> likewise<00:01:44.679> the 00:01:44.849 --> 00:01:44.859 align:start position:0% application needs likewise the 00:01:44.859 --> 00:01:47.219 align:start position:0% application needs likewise the middleware<00:01:45.130> can<00:01:45.340> provide<00:01:45.609> outputs<00:01:46.229> into 00:01:47.219 --> 00:01:47.229 align:start position:0% middleware can provide outputs into 00:01:47.229 --> 00:01:50.910 align:start position:0% middleware can provide outputs into relevant<00:01:47.770> payment<00:01:48.279> systems<00:01:48.779> now<00:01:49.779> right<00:01:50.709> now 00:01:50.910 --> 00:01:50.920 align:start position:0% relevant payment systems now right now 00:01:50.920 --> 00:01:52.769 align:start position:0% relevant payment systems now right now there<00:01:51.189> isn't<00:01:51.549> a<00:01:51.579> large<00:01:51.729> amount<00:01:52.119> of<00:01:52.420> these 00:01:52.769 --> 00:01:52.779 align:start position:0% there isn't a large amount of these 00:01:52.779 --> 00:01:54.779 align:start position:0% there isn't a large amount of these capabilities<00:01:53.229> and<00:01:53.859> the<00:01:54.009> parallel<00:01:54.399> I<00:01:54.520> tread 00:01:54.779 --> 00:01:54.789 align:start position:0% capabilities and the parallel I tread 00:01:54.789 --> 00:01:57.179 align:start position:0% capabilities and the parallel I tread tend<00:01:54.999> to<00:01:55.090> draw<00:01:55.270> in<00:01:55.329> my<00:01:55.479> mind<00:01:55.509> is<00:01:56.079> in<00:01:56.560> the<00:01:57.069> web 00:01:57.179 --> 00:01:57.189 align:start position:0% tend to draw in my mind is in the web 00:01:57.189 --> 00:01:58.529 align:start position:0% tend to draw in my mind is in the web development<00:01:57.609> world<00:01:57.849> when<00:01:58.119> you<00:01:58.209> want<00:01:58.359> to<00:01:58.420> build 00:01:58.529 --> 00:01:58.539 align:start position:0% development world when you want to build 00:01:58.539 --> 00:02:00.059 align:start position:0% development world when you want to build an<00:01:58.659> application<00:01:58.779> you<00:01:59.289> have<00:01:59.380> a<00:01:59.439> ton<00:01:59.619> of<00:01:59.649> api's 00:02:00.059 --> 00:02:00.069 align:start position:0% an application you have a ton of api's 00:02:00.069 --> 00:02:02.129 align:start position:0% an application you have a ton of api's you<00:02:00.310> can<00:02:00.459> connect<00:02:00.789> to<00:02:00.909> a<00:02:00.939> contract<00:02:01.450> right<00:02:01.959> in 00:02:02.129 --> 00:02:02.139 align:start position:0% you can connect to a contract right in 00:02:02.139 --> 00:02:04.169 align:start position:0% you can connect to a contract right in the<00:02:02.889> smart<00:02:03.159> contract<00:02:03.340> development<00:02:04.029> world 00:02:04.169 --> 00:02:04.179 align:start position:0% the smart contract development world 00:02:04.179 --> 00:02:07.980 align:start position:0% the smart contract development world right<00:02:04.450> now<00:02:04.479> due<00:02:05.289> to<00:02:05.319> the<00:02:05.679> lack<00:02:06.429> of<00:02:06.990> unchained 00:02:07.980 --> 00:02:07.990 align:start position:0% right now due to the lack of unchained 00:02:07.990 --> 00:02:09.840 align:start position:0% right now due to the lack of unchained contracts<00:02:08.679> that<00:02:08.830> represent<00:02:09.369> off<00:02:09.610> chain 00:02:09.840 --> 00:02:09.850 align:start position:0% contracts that represent off chain 00:02:09.850 --> 00:02:11.910 align:start position:0% contracts that represent off chain resources<00:02:10.479> it's<00:02:11.080> very<00:02:11.290> difficult<00:02:11.680> for<00:02:11.860> a 00:02:11.910 --> 00:02:11.920 align:start position:0% resources it's very difficult for a 00:02:11.920 --> 00:02:13.500 align:start position:0% resources it's very difficult for a smart<00:02:12.190> contract<00:02:12.370> developer<00:02:13.060> to<00:02:13.180> get<00:02:13.300> access 00:02:13.500 --> 00:02:13.510 align:start position:0% smart contract developer to get access 00:02:13.510 --> 00:02:15.330 align:start position:0% smart contract developer to get access to<00:02:14.050> the<00:02:14.230> inputs<00:02:14.620> and 00:02:15.330 --> 00:02:15.340 align:start position:0% to the inputs and 00:02:15.340 --> 00:02:17.250 align:start position:0% to the inputs and the<00:02:15.370> outputs<00:02:15.849> they<00:02:16.060> need<00:02:16.330> to<00:02:16.989> make<00:02:17.140> an 00:02:17.250 --> 00:02:17.260 align:start position:0% the outputs they need to make an 00:02:17.260 --> 00:02:19.500 align:start position:0% the outputs they need to make an application<00:02:17.860> right<00:02:18.400> like<00:02:19.120> the<00:02:19.239> people<00:02:19.480> that 00:02:19.500 --> 00:02:19.510 align:start position:0% application right like the people that 00:02:19.510 --> 00:02:20.970 align:start position:0% application right like the people that made<00:02:19.750> Ober<00:02:20.110> or<00:02:20.260> any<00:02:20.379> number<00:02:20.530> of<00:02:20.680> other<00:02:20.769> web 00:02:20.970 --> 00:02:20.980 align:start position:0% made Ober or any number of other web 00:02:20.980 --> 00:02:24.000 align:start position:0% made Ober or any number of other web applications<00:02:21.580> they<00:02:22.150> put<00:02:22.330> the<00:02:22.450> GPS<00:02:22.989> API<00:02:23.590> any 00:02:24.000 --> 00:02:24.010 align:start position:0% applications they put the GPS API any 00:02:24.010 --> 00:02:25.410 align:start position:0% applications they put the GPS API any number<00:02:24.280> of<00:02:24.340> other<00:02:24.430> api's<00:02:24.879> together<00:02:25.269> with 00:02:25.410 --> 00:02:25.420 align:start position:0% number of other api's together with 00:02:25.420 --> 00:02:27.210 align:start position:0% number of other api's together with their<00:02:25.569> core<00:02:25.720> application<00:02:26.290> and<00:02:26.500> then<00:02:26.950> they<00:02:27.069> had 00:02:27.210 --> 00:02:27.220 align:start position:0% their core application and then they had 00:02:27.220 --> 00:02:29.280 align:start position:0% their core application and then they had a<00:02:27.250> payments<00:02:27.700> output<00:02:28.090> in<00:02:28.269> a<00:02:28.690> payments<00:02:29.170> API 00:02:29.280 --> 00:02:29.290 align:start position:0% a payments output in a payments API 00:02:29.290 --> 00:02:31.800 align:start position:0% a payments output in a payments API right<00:02:29.950> it<00:02:30.340> should<00:02:30.550> be<00:02:30.670> just<00:02:30.879> that<00:02:31.030> easy<00:02:31.300> for<00:02:31.780> a 00:02:31.800 --> 00:02:31.810 align:start position:0% right it should be just that easy for a 00:02:31.810 --> 00:02:33.900 align:start position:0% right it should be just that easy for a smart<00:02:32.080> contract<00:02:32.230> developer<00:02:32.950> to<00:02:33.310> take<00:02:33.459> inputs 00:02:33.900 --> 00:02:33.910 align:start position:0% smart contract developer to take inputs 00:02:33.910 --> 00:02:35.820 align:start position:0% smart contract developer to take inputs combine<00:02:34.690> them<00:02:34.870> with<00:02:34.989> their<00:02:35.110> core<00:02:35.290> application 00:02:35.820 --> 00:02:35.830 align:start position:0% combine them with their core application 00:02:35.830 --> 00:02:37.770 align:start position:0% combine them with their core application in<00:02:35.920> the<00:02:35.980> form<00:02:36.160> of<00:02:36.250> a<00:02:36.340> smart<00:02:36.610> contract<00:02:37.090> and<00:02:37.299> then 00:02:37.770 --> 00:02:37.780 align:start position:0% in the form of a smart contract and then 00:02:37.780 --> 00:02:39.119 align:start position:0% in the form of a smart contract and then have<00:02:37.959> that<00:02:38.080> smart<00:02:38.410> contract<00:02:38.830> to<00:02:38.920> make<00:02:39.040> the 00:02:39.119 --> 00:02:39.129 align:start position:0% have that smart contract to make the 00:02:39.129 --> 00:02:41.369 align:start position:0% have that smart contract to make the relevant<00:02:39.459> outputs<00:02:39.849> without<00:02:40.750> them<00:02:40.989> figuring 00:02:41.369 --> 00:02:41.379 align:start position:0% relevant outputs without them figuring 00:02:41.379 --> 00:02:44.309 align:start position:0% relevant outputs without them figuring out<00:02:41.590> how<00:02:42.129> to<00:02:42.459> make<00:02:42.670> that<00:02:42.989> connectivity<00:02:43.989> work 00:02:44.309 --> 00:02:44.319 align:start position:0% out how to make that connectivity work 00:02:44.319 --> 00:02:46.380 align:start position:0% out how to make that connectivity work at<00:02:44.500> a<00:02:44.530> very<00:02:44.590> deep<00:02:44.920> level<00:02:45.010> right<00:02:45.610> that's<00:02:45.819> that's 00:02:46.380 --> 00:02:46.390 align:start position:0% at a very deep level right that's that's 00:02:46.390 --> 00:02:49.229 align:start position:0% at a very deep level right that's that's what<00:02:46.950> blockchain<00:02:47.950> middleware<00:02:48.340> as<00:02:48.579> a<00:02:48.610> general 00:02:49.229 --> 00:02:49.239 align:start position:0% what blockchain middleware as a general 00:02:49.239 --> 00:02:53.640 align:start position:0% what blockchain middleware as a general solution<00:02:49.450> provides<00:02:50.110> right<00:02:51.269> the<00:02:52.269> the<00:02:53.200> benefit 00:02:53.640 --> 00:02:53.650 align:start position:0% solution provides right the the benefit 00:02:53.650 --> 00:02:56.819 align:start position:0% solution provides right the the benefit of<00:02:53.680> a<00:02:54.040> blockchain<00:02:54.970> middleware<00:02:55.599> for<00:02:55.930> a<00:02:56.530> smart 00:02:56.819 --> 00:02:56.829 align:start position:0% of a blockchain middleware for a smart 00:02:56.829 --> 00:02:59.190 align:start position:0% of a blockchain middleware for a smart contract<00:02:57.040> ideally<00:02:57.970> would<00:02:58.720> be<00:02:58.780> that<00:02:59.079> it 00:02:59.190 --> 00:02:59.200 align:start position:0% contract ideally would be that it 00:02:59.200 --> 00:03:01.710 align:start position:0% contract ideally would be that it maintains<00:02:59.920> the<00:03:00.069> same<00:03:00.370> level<00:03:00.760> of<00:03:00.849> security<00:03:01.329> as 00:03:01.710 --> 00:03:01.720 align:start position:0% maintains the same level of security as 00:03:01.720 --> 00:03:04.589 align:start position:0% maintains the same level of security as the<00:03:02.290> contract<00:03:02.799> right<00:03:03.370> you<00:03:04.000> don't<00:03:04.239> want<00:03:04.540> a 00:03:04.589 --> 00:03:04.599 align:start position:0% the contract right you don't want a 00:03:04.599 --> 00:03:07.680 align:start position:0% the contract right you don't want a contract<00:03:05.140> that's<00:03:05.920> highly<00:03:06.310> secure<00:03:06.730> that's 00:03:07.680 --> 00:03:07.690 align:start position:0% contract that's highly secure that's 00:03:07.690 --> 00:03:09.750 align:start position:0% contract that's highly secure that's triggered<00:03:08.170> by<00:03:08.349> a<00:03:08.379> highly<00:03:08.769> insecure<00:03:09.129> system 00:03:09.750 --> 00:03:09.760 align:start position:0% triggered by a highly insecure system 00:03:09.760 --> 00:03:12.210 align:start position:0% triggered by a highly insecure system and<00:03:10.030> that<00:03:10.690> pays<00:03:10.989> out<00:03:11.260> through<00:03:11.530> another<00:03:11.590> highly 00:03:12.210 --> 00:03:12.220 align:start position:0% and that pays out through another highly 00:03:12.220 --> 00:03:14.880 align:start position:0% and that pays out through another highly insecure<00:03:12.549> system<00:03:13.120> if<00:03:13.390> you<00:03:14.349> have<00:03:14.530> a<00:03:14.560> very 00:03:14.880 --> 00:03:14.890 align:start position:0% insecure system if you have a very 00:03:14.890 --> 00:03:17.100 align:start position:0% insecure system if you have a very secure<00:03:15.340> middle<00:03:15.940> part<00:03:16.269> of<00:03:16.390> the<00:03:16.510> end-to-end 00:03:17.100 --> 00:03:17.110 align:start position:0% secure middle part of the end-to-end 00:03:17.110 --> 00:03:19.319 align:start position:0% secure middle part of the end-to-end setup<00:03:17.620> and<00:03:17.829> the<00:03:18.340> inputs<00:03:18.700> and<00:03:18.790> the<00:03:18.879> outputs<00:03:19.239> are 00:03:19.319 --> 00:03:19.329 align:start position:0% setup and the inputs and the outputs are 00:03:19.329 --> 00:03:22.710 align:start position:0% setup and the inputs and the outputs are insecure<00:03:19.859> it's<00:03:20.859> unlikely<00:03:21.340> that<00:03:22.030> digital 00:03:22.710 --> 00:03:22.720 align:start position:0% insecure it's unlikely that digital 00:03:22.720 --> 00:03:24.479 align:start position:0% insecure it's unlikely that digital financial<00:03:23.079> agreements<00:03:23.530> of<00:03:23.620> large<00:03:23.829> value<00:03:24.280> are 00:03:24.479 --> 00:03:24.489 align:start position:0% financial agreements of large value are 00:03:24.489 --> 00:03:27.180 align:start position:0% financial agreements of large value are going<00:03:25.420> to<00:03:25.540> transfer<00:03:26.079> from<00:03:26.380> the<00:03:26.620> legacy<00:03:27.010> world 00:03:27.180 --> 00:03:27.190 align:start position:0% going to transfer from the legacy world 00:03:27.190 --> 00:03:30.390 align:start position:0% going to transfer from the legacy world into<00:03:27.819> the<00:03:28.120> smart<00:03:28.389> contract<00:03:28.540> world<00:03:29.049> right<00:03:29.709> so 00:03:30.390 --> 00:03:30.400 align:start position:0% into the smart contract world right so 00:03:30.400 --> 00:03:33.569 align:start position:0% into the smart contract world right so as<00:03:30.880> a<00:03:30.940> community<00:03:31.599> or<00:03:31.840> at<00:03:32.139> least<00:03:32.410> we<00:03:33.130> as<00:03:33.280> a<00:03:33.310> group 00:03:33.569 --> 00:03:33.579 align:start position:0% as a community or at least we as a group 00:03:33.579 --> 00:03:35.970 align:start position:0% as a community or at least we as a group of<00:03:33.670> people<00:03:33.849> are<00:03:34.090> very<00:03:34.269> interested<00:03:34.780> in<00:03:34.980> solving 00:03:35.970 --> 00:03:35.980 align:start position:0% of people are very interested in solving 00:03:35.980 --> 00:03:38.970 align:start position:0% of people are very interested in solving this<00:03:36.519> problem<00:03:37.209> of<00:03:37.389> how<00:03:38.230> do<00:03:38.290> you<00:03:38.410> get<00:03:38.590> a<00:03:38.620> smart 00:03:38.970 --> 00:03:38.980 align:start position:0% this problem of how do you get a smart 00:03:38.980 --> 00:03:40.949 align:start position:0% this problem of how do you get a smart contract<00:03:39.180> to<00:03:40.180> do<00:03:40.299> something<00:03:40.660> meaningful 00:03:40.949 --> 00:03:40.959 align:start position:0% contract to do something meaningful 00:03:40.959 --> 00:03:43.500 align:start position:0% contract to do something meaningful relative<00:03:41.530> to<00:03:41.620> the<00:03:41.709> real<00:03:41.859> world<00:03:42.090> but<00:03:43.090> also<00:03:43.299> to 00:03:43.500 --> 00:03:43.510 align:start position:0% relative to the real world but also to 00:03:43.510 --> 00:03:46.289 align:start position:0% relative to the real world but also to do<00:03:43.780> it<00:03:43.810> so<00:03:44.139> securely<00:03:44.620> that<00:03:45.459> the<00:03:45.700> input<00:03:46.060> of<00:03:46.090> the 00:03:46.289 --> 00:03:46.299 align:start position:0% do it so securely that the input of the 00:03:46.299 --> 00:03:48.120 align:start position:0% do it so securely that the input of the data<00:03:46.510> that<00:03:46.599> triggers<00:03:47.049> their<00:03:47.230> contract<00:03:47.859> the 00:03:48.120 --> 00:03:48.130 align:start position:0% data that triggers their contract the 00:03:48.130 --> 00:03:50.610 align:start position:0% data that triggers their contract the contract<00:03:48.579> itself<00:03:48.970> and<00:03:49.239> the<00:03:49.450> output<00:03:49.840> can<00:03:50.410> all 00:03:50.610 --> 00:03:50.620 align:start position:0% contract itself and the output can all 00:03:50.620 --> 00:03:52.680 align:start position:0% contract itself and the output can all be<00:03:50.829> trusted<00:03:51.340> at<00:03:51.849> a<00:03:51.880> very<00:03:52.150> high<00:03:52.299> level<00:03:52.480> of 00:03:52.680 --> 00:03:52.690 align:start position:0% be trusted at a very high level of 00:03:52.690 --> 00:03:56.370 align:start position:0% be trusted at a very high level of tamper-proof<00:03:53.079> enos<00:03:54.329> so<00:03:55.329> to<00:03:55.389> understand<00:03:56.200> what 00:03:56.370 --> 00:03:56.380 align:start position:0% tamper-proof enos so to understand what 00:03:56.380 --> 00:03:58.530 align:start position:0% tamper-proof enos so to understand what our<00:03:56.410> options<00:03:56.650> are<00:03:57.069> in<00:03:57.190> this<00:03:57.910> problem<00:03:58.180> it's 00:03:58.530 --> 00:03:58.540 align:start position:0% our options are in this problem it's 00:03:58.540 --> 00:04:01.170 align:start position:0% our options are in this problem it's good<00:03:58.930> to<00:03:59.079> look<00:03:59.200> at<00:03:59.380> like<00:04:00.040> what<00:04:00.069> is<00:04:00.430> some<00:04:00.970> of<00:04:01.000> the 00:04:01.170 --> 00:04:01.180 align:start position:0% good to look at like what is some of the 00:04:01.180 --> 00:04:03.449 align:start position:0% good to look at like what is some of the current<00:04:01.450> approaches<00:04:02.040> one<00:04:03.040> very<00:04:03.220> common 00:04:03.449 --> 00:04:03.459 align:start position:0% current approaches one very common 00:04:03.459 --> 00:04:05.640 align:start position:0% current approaches one very common approach<00:04:03.669> is<00:04:04.090> basically<00:04:04.690> the<00:04:04.810> use<00:04:05.019> of<00:04:05.410> a 00:04:05.640 --> 00:04:05.650 align:start position:0% approach is basically the use of a 00:04:05.650 --> 00:04:08.400 align:start position:0% approach is basically the use of a centralized<00:04:06.130> Oracle<00:04:06.609> so<00:04:07.450> that<00:04:07.840> is<00:04:08.139> the 00:04:08.400 --> 00:04:08.410 align:start position:0% centralized Oracle so that is the 00:04:08.410 --> 00:04:10.800 align:start position:0% centralized Oracle so that is the approach<00:04:08.709> where<00:04:09.040> either<00:04:09.760> an<00:04:10.060> individual<00:04:10.630> in 00:04:10.800 --> 00:04:10.810 align:start position:0% approach where either an individual in 00:04:10.810 --> 00:04:13.199 align:start position:0% approach where either an individual in the<00:04:10.930> contract<00:04:11.380> runs<00:04:11.590> an<00:04:11.739> Oracle<00:04:12.130> one<00:04:13.060> of<00:04:13.150> the 00:04:13.199 --> 00:04:13.209 align:start position:0% the contract runs an Oracle one of the 00:04:13.209 --> 00:04:15.960 align:start position:0% the contract runs an Oracle one of the counterparties<00:04:13.810> or<00:04:14.079> possibly<00:04:14.980> a<00:04:15.069> service<00:04:15.549> in 00:04:15.960 --> 00:04:15.970 align:start position:0% counterparties or possibly a service in 00:04:15.970 --> 00:04:18.029 align:start position:0% counterparties or possibly a service in any<00:04:16.479> case<00:04:16.690> there's<00:04:16.930> a<00:04:16.989> single<00:04:17.440> centralized 00:04:18.029 --> 00:04:18.039 align:start position:0% any case there's a single centralized 00:04:18.039 --> 00:04:22.080 align:start position:0% any case there's a single centralized Oracle<00:04:18.489> that<00:04:18.669> acquires<00:04:19.630> data<00:04:20.019> as<00:04:20.349> a<00:04:21.090> trusted 00:04:22.080 --> 00:04:22.090 align:start position:0% Oracle that acquires data as a trusted 00:04:22.090 --> 00:04:24.120 align:start position:0% Oracle that acquires data as a trusted third<00:04:22.150> party<00:04:22.630> and<00:04:22.840> gives<00:04:23.110> that<00:04:23.320> data<00:04:23.530> to<00:04:23.919> the 00:04:24.120 --> 00:04:24.130 align:start position:0% third party and gives that data to the 00:04:24.130 --> 00:04:26.190 align:start position:0% third party and gives that data to the decentralized<00:04:25.000> computation<00:04:25.780> Network<00:04:26.080> to 00:04:26.190 --> 00:04:26.200 align:start position:0% decentralized computation Network to 00:04:26.200 --> 00:04:28.159 align:start position:0% decentralized computation Network to process<00:04:26.590> it<00:04:26.770> right 00:04:28.159 --> 00:04:28.169 align:start position:0% process it right 00:04:28.169 --> 00:04:30.080 align:start position:0% process it right the<00:04:28.530> problem<00:04:28.919> with<00:04:29.039> this<00:04:29.159> in<00:04:29.340> our<00:04:29.430> opinion<00:04:29.879> is 00:04:30.080 --> 00:04:30.090 align:start position:0% the problem with this in our opinion is 00:04:30.090 --> 00:04:32.089 align:start position:0% the problem with this in our opinion is that<00:04:30.150> the<00:04:30.960> decentralized<00:04:31.289> computation 00:04:32.089 --> 00:04:32.099 align:start position:0% that the decentralized computation 00:04:32.099 --> 00:04:34.249 align:start position:0% that the decentralized computation network<00:04:32.430> has<00:04:32.610> thousands<00:04:33.180> of<00:04:33.300> nodes<00:04:33.479> which 00:04:34.249 --> 00:04:34.259 align:start position:0% network has thousands of nodes which 00:04:34.259 --> 00:04:35.749 align:start position:0% network has thousands of nodes which provide<00:04:34.620> the<00:04:34.770> tamper<00:04:35.129> proof<00:04:35.310> nests<00:04:35.520> and<00:04:35.669> the 00:04:35.749 --> 00:04:35.759 align:start position:0% provide the tamper proof nests and the 00:04:35.759 --> 00:04:37.550 align:start position:0% provide the tamper proof nests and the security<00:04:36.180> guarantees<00:04:36.599> we<00:04:36.810> all<00:04:36.930> value<00:04:37.110> in<00:04:37.409> that 00:04:37.550 --> 00:04:37.560 align:start position:0% security guarantees we all value in that 00:04:37.560 --> 00:04:40.820 align:start position:0% security guarantees we all value in that contract<00:04:38.150> while<00:04:39.150> the<00:04:39.900> centralized<00:04:40.379> Oracle 00:04:40.820 --> 00:04:40.830 align:start position:0% contract while the centralized Oracle 00:04:40.830 --> 00:04:42.409 align:start position:0% contract while the centralized Oracle shrivelling<00:04:41.430> triggering<00:04:41.969> this<00:04:42.120> highly 00:04:42.409 --> 00:04:42.419 align:start position:0% shrivelling triggering this highly 00:04:42.419 --> 00:04:44.270 align:start position:0% shrivelling triggering this highly tamper<00:04:42.750> proof<00:04:42.930> decentralized<00:04:43.560> computation 00:04:44.270 --> 00:04:44.280 align:start position:0% tamper proof decentralized computation 00:04:44.280 --> 00:04:49.189 align:start position:0% tamper proof decentralized computation is<00:04:45.259> not<00:04:46.259> tamper<00:04:46.620> proof<00:04:46.770> right<00:04:47.550> so<00:04:48.210> the<00:04:48.509> set<00:04:49.080> up 00:04:49.189 --> 00:04:49.199 align:start position:0% is not tamper proof right so the set up 00:04:49.199 --> 00:04:50.990 align:start position:0% is not tamper proof right so the set up end-to-end<00:04:49.590> at<00:04:49.860> this<00:04:50.009> point<00:04:50.280> is<00:04:50.490> not<00:04:50.639> tamper 00:04:50.990 --> 00:04:51.000 align:start position:0% end-to-end at this point is not tamper 00:04:51.000 --> 00:04:52.700 align:start position:0% end-to-end at this point is not tamper proof<00:04:51.210> it's<00:04:51.990> not<00:04:52.080> going<00:04:52.349> to<00:04:52.409> appear<00:04:52.590> very 00:04:52.700 --> 00:04:52.710 align:start position:0% proof it's not going to appear very 00:04:52.710 --> 00:04:54.830 align:start position:0% proof it's not going to appear very secure<00:04:53.189> it<00:04:53.759> doesn't<00:04:54.120> provide<00:04:54.360> the<00:04:54.419> tamper 00:04:54.830 --> 00:04:54.840 align:start position:0% secure it doesn't provide the tamper 00:04:54.840 --> 00:04:57.589 align:start position:0% secure it doesn't provide the tamper proof<00:04:54.990> guarantees<00:04:55.530> that<00:04:56.120> that<00:04:57.120> we<00:04:57.270> think<00:04:57.479> are 00:04:57.589 --> 00:04:57.599 align:start position:0% proof guarantees that that we think are 00:04:57.599 --> 00:04:59.689 align:start position:0% proof guarantees that that we think are important<00:04:58.050> for<00:04:58.500> smart<00:04:58.830> contracts<00:04:59.370> to<00:04:59.550> have<00:04:59.669> a 00:04:59.689 --> 00:04:59.699 align:start position:0% important for smart contracts to have a 00:04:59.699 --> 00:05:03.320 align:start position:0% important for smart contracts to have a unique<00:04:59.969> value<00:05:00.389> right<00:05:00.930> and<00:05:01.430> so<00:05:02.430> this<00:05:03.150> attack 00:05:03.320 --> 00:05:03.330 align:start position:0% unique value right and so this attack 00:05:03.330 --> 00:05:08.119 align:start position:0% unique value right and so this attack vector<00:05:03.930> of<00:05:04.969> how<00:05:05.969> do<00:05:06.029> you<00:05:06.529> attack<00:05:07.529> a<00:05:07.560> contract 00:05:08.119 --> 00:05:08.129 align:start position:0% vector of how do you attack a contract 00:05:08.129 --> 00:05:09.830 align:start position:0% vector of how do you attack a contract that<00:05:08.279> has<00:05:08.400> one<00:05:08.699> node<00:05:08.939> triggering<00:05:09.569> the<00:05:09.689> key 00:05:09.830 --> 00:05:09.840 align:start position:0% that has one node triggering the key 00:05:09.840 --> 00:05:12.200 align:start position:0% that has one node triggering the key events<00:05:10.229> is<00:05:10.379> is<00:05:11.159> the<00:05:11.340> attack<00:05:11.610> vector<00:05:11.969> that<00:05:12.090> we 00:05:12.200 --> 00:05:12.210 align:start position:0% events is is the attack vector that we 00:05:12.210 --> 00:05:13.969 align:start position:0% events is is the attack vector that we think<00:05:12.419> is<00:05:12.539> worth<00:05:12.750> worth<00:05:13.379> seriously 00:05:13.969 --> 00:05:13.979 align:start position:0% think is worth worth seriously 00:05:13.979 --> 00:05:16.399 align:start position:0% think is worth worth seriously considering<00:05:14.569> everything<00:05:15.569> from<00:05:15.990> DevOps 00:05:16.399 --> 00:05:16.409 align:start position:0% considering everything from DevOps 00:05:16.409 --> 00:05:18.439 align:start position:0% considering everything from DevOps problems<00:05:16.860> with<00:05:17.069> that<00:05:17.189> one<00:05:17.430> node<00:05:17.639> to<00:05:18.120> somebody 00:05:18.439 --> 00:05:18.449 align:start position:0% problems with that one node to somebody 00:05:18.449 --> 00:05:20.480 align:start position:0% problems with that one node to somebody genuinely<00:05:18.810> attacking<00:05:19.319> a<00:05:19.409> single<00:05:19.770> node<00:05:19.919> to 00:05:20.480 --> 00:05:20.490 align:start position:0% genuinely attacking a single node to 00:05:20.490 --> 00:05:22.519 align:start position:0% genuinely attacking a single node to stop<00:05:20.699> a<00:05:20.729> contract<00:05:21.270> from<00:05:21.389> running<00:05:21.719> on<00:05:21.840> you<00:05:22.439> know 00:05:22.519 --> 00:05:22.529 align:start position:0% stop a contract from running on you know 00:05:22.529 --> 00:05:24.110 align:start position:0% stop a contract from running on you know could<00:05:22.710> be<00:05:22.740> a<00:05:22.860> million<00:05:23.279> nodes<00:05:23.490> it<00:05:23.909> doesn't 00:05:24.110 --> 00:05:24.120 align:start position:0% could be a million nodes it doesn't 00:05:24.120 --> 00:05:25.189 align:start position:0% could be a million nodes it doesn't matter<00:05:24.270> how<00:05:24.479> many<00:05:24.539> nodes<00:05:24.840> are<00:05:25.020> in<00:05:25.139> the 00:05:25.189 --> 00:05:25.199 align:start position:0% matter how many nodes are in the 00:05:25.199 --> 00:05:26.959 align:start position:0% matter how many nodes are in the decentralized<00:05:25.529> computation<00:05:26.340> environment<00:05:26.819> if 00:05:26.959 --> 00:05:26.969 align:start position:0% decentralized computation environment if 00:05:26.969 --> 00:05:29.779 align:start position:0% decentralized computation environment if the<00:05:27.599> trigger<00:05:27.870> is<00:05:28.169> attacked<00:05:28.680> and<00:05:28.979> compromised 00:05:29.779 --> 00:05:29.789 align:start position:0% the trigger is attacked and compromised 00:05:29.789 --> 00:05:31.850 align:start position:0% the trigger is attacked and compromised and<00:05:30.150> doesn't<00:05:30.479> happen<00:05:30.599> the<00:05:31.229> contract<00:05:31.680> won't 00:05:31.850 --> 00:05:31.860 align:start position:0% and doesn't happen the contract won't 00:05:31.860 --> 00:05:36.279 align:start position:0% and doesn't happen the contract won't trigger<00:05:33.289> so<00:05:34.289> the<00:05:34.889> the<00:05:35.190> approach<00:05:35.520> that<00:05:35.550> we 00:05:36.279 --> 00:05:36.289 align:start position:0% trigger so the the approach that we 00:05:36.289 --> 00:05:38.930 align:start position:0% trigger so the the approach that we advocated<00:05:37.289> this<00:05:37.379> problem<00:05:37.800> is<00:05:37.889> twofold<00:05:38.069> the 00:05:38.930 --> 00:05:38.940 align:start position:0% advocated this problem is twofold the 00:05:38.940 --> 00:05:42.379 align:start position:0% advocated this problem is twofold the first<00:05:39.629> part<00:05:39.900> of<00:05:39.960> it<00:05:40.110> is<00:05:40.259> decentralization<00:05:41.389> so 00:05:42.379 --> 00:05:42.389 align:start position:0% first part of it is decentralization so 00:05:42.389 --> 00:05:45.619 align:start position:0% first part of it is decentralization so we<00:05:42.539> apply<00:05:43.020> the<00:05:43.979> idea<00:05:44.219> of<00:05:44.310> decentralization<00:05:44.909> to 00:05:45.619 --> 00:05:45.629 align:start position:0% we apply the idea of decentralization to 00:05:45.629 --> 00:05:47.779 align:start position:0% we apply the idea of decentralization to Oracle's<00:05:46.110> to<00:05:46.259> blockchain<00:05:46.680> but<00:05:46.830> aware<00:05:47.039> and<00:05:47.250> we 00:05:47.779 --> 00:05:47.789 align:start position:0% Oracle's to blockchain but aware and we 00:05:47.789 --> 00:05:51.320 align:start position:0% Oracle's to blockchain but aware and we create<00:05:48.210> an<00:05:48.690> Oracle<00:05:49.110> network<00:05:49.430> that<00:05:50.430> is<00:05:50.669> able<00:05:51.120> to 00:05:51.320 --> 00:05:51.330 align:start position:0% create an Oracle network that is able to 00:05:51.330 --> 00:05:55.070 align:start position:0% create an Oracle network that is able to process<00:05:51.599> and<00:05:52.169> acquire<00:05:52.620> the<00:05:52.830> data<00:05:54.080> using 00:05:55.070 --> 00:05:55.080 align:start position:0% process and acquire the data using 00:05:55.080 --> 00:05:57.219 align:start position:0% process and acquire the data using multiple<00:05:55.650> independent<00:05:56.159> node<00:05:56.310> operators 00:05:57.219 --> 00:05:57.229 align:start position:0% multiple independent node operators 00:05:57.229 --> 00:06:00.950 align:start position:0% multiple independent node operators those<00:05:58.229> independent<00:05:58.830> node<00:05:58.979> operators<00:05:59.930> can<00:06:00.930> be 00:06:00.950 --> 00:06:00.960 align:start position:0% those independent node operators can be 00:06:00.960 --> 00:06:02.269 align:start position:0% those independent node operators can be selected<00:06:01.469> by<00:06:01.560> the<00:06:01.620> person<00:06:01.949> making<00:06:02.099> the 00:06:02.269 --> 00:06:02.279 align:start position:0% selected by the person making the 00:06:02.279 --> 00:06:03.589 align:start position:0% selected by the person making the contract<00:06:02.639> and<00:06:02.879> they<00:06:02.939> can<00:06:03.089> select<00:06:03.270> as<00:06:03.569> many 00:06:03.589 --> 00:06:03.599 align:start position:0% contract and they can select as many 00:06:03.599 --> 00:06:06.110 align:start position:0% contract and they can select as many note<00:06:03.900> operators<00:06:04.349> as<00:06:04.469> they<00:06:04.589> want<00:06:04.800> to<00:06:05.370> five<00:06:05.759> 10 00:06:06.110 --> 00:06:06.120 align:start position:0% note operators as they want to five 10 00:06:06.120 --> 00:06:08.809 align:start position:0% note operators as they want to five 10 50<00:06:06.539> 100<00:06:07.050> however<00:06:07.949> much<00:06:08.129> decentralization 00:06:08.809 --> 00:06:08.819 align:start position:0% 50 100 however much decentralization 00:06:08.819 --> 00:06:10.519 align:start position:0% 50 100 however much decentralization they<00:06:09.089> want<00:06:09.360> at<00:06:09.539> this<00:06:09.750> level<00:06:10.020> of<00:06:10.229> middleware 00:06:10.519 --> 00:06:10.529 align:start position:0% they want at this level of middleware 00:06:10.529 --> 00:06:13.339 align:start position:0% they want at this level of middleware they<00:06:11.339> can<00:06:11.520> now<00:06:11.639> acquire<00:06:12.000> to<00:06:12.839> give<00:06:13.080> them 00:06:13.339 --> 00:06:13.349 align:start position:0% they can now acquire to give them 00:06:13.349 --> 00:06:15.769 align:start position:0% they can now acquire to give them guarantees<00:06:14.219> about<00:06:14.610> tamper<00:06:15.180> proof<00:06:15.389> venus<00:06:15.629> in 00:06:15.769 --> 00:06:15.779 align:start position:0% guarantees about tamper proof venus in 00:06:15.779 --> 00:06:18.679 align:start position:0% guarantees about tamper proof venus in terms<00:06:15.990> of<00:06:16.139> their<00:06:16.289> inputs<00:06:17.210> this<00:06:18.210> ability<00:06:18.509> to 00:06:18.679 --> 00:06:18.689 align:start position:0% terms of their inputs this ability to 00:06:18.689 --> 00:06:21.800 align:start position:0% terms of their inputs this ability to decentralize<00:06:19.379> the<00:06:20.210> blockchain<00:06:21.210> middleware 00:06:21.800 --> 00:06:21.810 align:start position:0% decentralize the blockchain middleware 00:06:21.810 --> 00:06:23.899 align:start position:0% decentralize the blockchain middleware layer<00:06:21.839> the<00:06:22.229> Oracle<00:06:22.620> layer<00:06:22.770> also<00:06:23.339> gives<00:06:23.789> you 00:06:23.899 --> 00:06:23.909 align:start position:0% layer the Oracle layer also gives you 00:06:23.909 --> 00:06:25.399 align:start position:0% layer the Oracle layer also gives you the<00:06:24.029> ability<00:06:24.210> to<00:06:24.449> now<00:06:24.659> contract<00:06:25.229> with 00:06:25.399 --> 00:06:25.409 align:start position:0% the ability to now contract with 00:06:25.409 --> 00:06:28.129 align:start position:0% the ability to now contract with multiple<00:06:25.830> data<00:06:26.009> sources<00:06:26.479> in<00:06:27.479> our<00:06:27.599> opinion<00:06:28.020> it 00:06:28.129 --> 00:06:28.139 align:start position:0% multiple data sources in our opinion it 00:06:28.139 --> 00:06:30.529 align:start position:0% multiple data sources in our opinion it doesn't<00:06:28.259> make<00:06:28.500> as<00:06:28.650> much<00:06:28.680> sense<00:06:28.949> for<00:06:29.550> one<00:06:29.819> node 00:06:30.529 --> 00:06:30.539 align:start position:0% doesn't make as much sense for one node 00:06:30.539 --> 00:06:34.309 align:start position:0% doesn't make as much sense for one node to<00:06:30.839> use<00:06:31.439> five<00:06:31.830> data<00:06:32.069> sources<00:06:32.520> you<00:06:33.360> centralize 00:06:34.309 --> 00:06:34.319 align:start position:0% to use five data sources you centralize 00:06:34.319 --> 00:06:36.649 align:start position:0% to use five data sources you centralize the<00:06:34.529> data<00:06:35.159> at<00:06:35.339> the<00:06:35.430> level<00:06:35.669> of<00:06:35.729> the<00:06:35.849> origin<00:06:36.270> but 00:06:36.649 --> 00:06:36.659 align:start position:0% the data at the level of the origin but 00:06:36.659 --> 00:06:37.790 align:start position:0% the data at the level of the origin but it's<00:06:36.810> still<00:06:36.959> going<00:06:37.169> through<00:06:37.349> one<00:06:37.469> point<00:06:37.709> of 00:06:37.790 --> 00:06:37.800 align:start position:0% it's still going through one point of 00:06:37.800 --> 00:06:39.829 align:start position:0% it's still going through one point of failure<00:06:37.979> now<00:06:38.819> once<00:06:39.180> you<00:06:39.300> have<00:06:39.330> for<00:06:39.779> example 00:06:39.829 --> 00:06:39.839 align:start position:0% failure now once you have for example 00:06:39.839 --> 00:06:41.990 align:start position:0% failure now once you have for example five<00:06:40.469> separate<00:06:41.459> decentral 00:06:41.990 --> 00:06:42.000 align:start position:0% five separate decentral 00:06:42.000 --> 00:06:44.510 align:start position:0% five separate decentral doricles<00:06:42.570> they<00:06:42.990> can<00:06:43.200> all<00:06:43.380> acquire<00:06:43.740> data<00:06:44.010> from 00:06:44.510 --> 00:06:44.520 align:start position:0% doricles they can all acquire data from 00:06:44.520 --> 00:06:47.180 align:start position:0% doricles they can all acquire data from five<00:06:44.760> separate<00:06:45.360> data<00:06:45.690> sources<00:06:46.050> if<00:06:46.530> that's 00:06:47.180 --> 00:06:47.190 align:start position:0% five separate data sources if that's 00:06:47.190 --> 00:06:49.670 align:start position:0% five separate data sources if that's something<00:06:47.490> that<00:06:48.360> your<00:06:48.480> use<00:06:48.690> case<00:06:48.930> needs<00:06:49.260> so 00:06:49.670 --> 00:06:49.680 align:start position:0% something that your use case needs so 00:06:49.680 --> 00:06:51.350 align:start position:0% something that your use case needs so it's<00:06:49.860> there's<00:06:50.220> gonna<00:06:50.340> be<00:06:50.490> an<00:06:50.550> entire<00:06:50.850> spectrum 00:06:51.350 --> 00:06:51.360 align:start position:0% it's there's gonna be an entire spectrum 00:06:51.360 --> 00:06:53.540 align:start position:0% it's there's gonna be an entire spectrum of<00:06:51.540> use<00:06:51.690> cases<00:06:51.960> that<00:06:52.710> doing<00:06:53.010> don't<00:06:53.160> need<00:06:53.370> this 00:06:53.540 --> 00:06:53.550 align:start position:0% of use cases that doing don't need this 00:06:53.550 --> 00:06:55.880 align:start position:0% of use cases that doing don't need this but<00:06:54.240> in<00:06:54.330> our<00:06:54.450> opinion<00:06:54.570> the<00:06:55.140> high-value<00:06:55.560> use 00:06:55.880 --> 00:06:55.890 align:start position:0% but in our opinion the high-value use 00:06:55.890 --> 00:06:57.920 align:start position:0% but in our opinion the high-value use cases<00:06:56.160> are<00:06:56.580> going<00:06:57.090> to<00:06:57.330> want<00:06:57.480> to<00:06:57.630> provide<00:06:57.870> a 00:06:57.920 --> 00:06:57.930 align:start position:0% cases are going to want to provide a 00:06:57.930 --> 00:07:00.320 align:start position:0% cases are going to want to provide a high<00:06:58.200> level<00:06:58.230> of<00:06:58.620> tamper-proof<00:06:58.980> eNOS<00:06:59.400> through 00:07:00.320 --> 00:07:00.330 align:start position:0% high level of tamper-proof eNOS through 00:07:00.330 --> 00:07:02.780 align:start position:0% high level of tamper-proof eNOS through the<00:07:00.450> centralization<00:07:00.900> right<00:07:01.770> which<00:07:01.950> is<00:07:02.130> which 00:07:02.780 --> 00:07:02.790 align:start position:0% the centralization right which is which 00:07:02.790 --> 00:07:05.060 align:start position:0% the centralization right which is which is<00:07:02.940> what<00:07:03.180> we<00:07:03.330> we'd<00:07:03.630> like<00:07:03.840> to<00:07:03.990> enable<00:07:04.170> so<00:07:04.920> that 00:07:05.060 --> 00:07:05.070 align:start position:0% is what we we'd like to enable so that 00:07:05.070 --> 00:07:06.710 align:start position:0% is what we we'd like to enable so that the<00:07:05.160> end-to-end<00:07:05.580> setup<00:07:06.090> is<00:07:06.240> sufficiently 00:07:06.710 --> 00:07:06.720 align:start position:0% the end-to-end setup is sufficiently 00:07:06.720 --> 00:07:09.740 align:start position:0% the end-to-end setup is sufficiently secure<00:07:07.200> for<00:07:08.010> people<00:07:08.250> to<00:07:08.370> trust<00:07:08.640> it<00:07:08.910> to<00:07:09.600> put 00:07:09.740 --> 00:07:09.750 align:start position:0% secure for people to trust it to put 00:07:09.750 --> 00:07:12.200 align:start position:0% secure for people to trust it to put actual<00:07:10.140> money<00:07:10.410> into<00:07:10.710> a<00:07:10.740> smart<00:07:11.040> contract<00:07:11.210> for 00:07:12.200 --> 00:07:12.210 align:start position:0% actual money into a smart contract for 00:07:12.210 --> 00:07:17.600 align:start position:0% actual money into a smart contract for things<00:07:12.450> to<00:07:12.540> go<00:07:12.690> to<00:07:12.750> production<00:07:14.840> the<00:07:16.460> the<00:07:17.460> other 00:07:17.600 --> 00:07:17.610 align:start position:0% things to go to production the the other 00:07:17.610 --> 00:07:19.100 align:start position:0% things to go to production the the other part<00:07:17.880> of<00:07:17.940> our<00:07:18.030> approach<00:07:18.270> is<00:07:18.570> that<00:07:18.600> it's<00:07:18.840> open 00:07:19.100 --> 00:07:19.110 align:start position:0% part of our approach is that it's open 00:07:19.110 --> 00:07:22.100 align:start position:0% part of our approach is that it's open source<00:07:19.320> and<00:07:20.180> we<00:07:21.180> believe<00:07:21.510> very<00:07:21.540> strongly<00:07:21.990> in 00:07:22.100 --> 00:07:22.110 align:start position:0% source and we believe very strongly in 00:07:22.110 --> 00:07:23.870 align:start position:0% source and we believe very strongly in open<00:07:22.380> source<00:07:22.620> and<00:07:22.860> security<00:07:23.340> reviews<00:07:23.640> through 00:07:23.870 --> 00:07:23.880 align:start position:0% open source and security reviews through 00:07:23.880 --> 00:07:25.760 align:start position:0% open source and security reviews through open<00:07:24.180> source<00:07:24.210> both<00:07:25.020> on<00:07:25.260> the<00:07:25.350> level<00:07:25.590> of<00:07:25.650> the 00:07:25.760 --> 00:07:25.770 align:start position:0% open source both on the level of the 00:07:25.770 --> 00:07:27.740 align:start position:0% open source both on the level of the Unchained<00:07:26.160> contracts<00:07:26.790> and<00:07:26.940> the<00:07:27.360> off<00:07:27.480> chain 00:07:27.740 --> 00:07:27.750 align:start position:0% Unchained contracts and the off chain 00:07:27.750 --> 00:07:31.580 align:start position:0% Unchained contracts and the off chain implementation<00:07:28.440> of<00:07:28.620> the<00:07:29.160> middleware<00:07:29.520> and<00:07:30.590> we 00:07:31.580 --> 00:07:31.590 align:start position:0% implementation of the middleware and we 00:07:31.590 --> 00:07:35.030 align:start position:0% implementation of the middleware and we believe<00:07:31.860> that<00:07:31.890> a<00:07:32.070> shared<00:07:33.470> large<00:07:34.470> community<00:07:35.010> of 00:07:35.030 --> 00:07:35.040 align:start position:0% believe that a shared large community of 00:07:35.040 --> 00:07:36.260 align:start position:0% believe that a shared large community of people<00:07:35.280> working<00:07:35.730> towards<00:07:35.880> the<00:07:36.060> blockchain 00:07:36.260 --> 00:07:36.270 align:start position:0% people working towards the blockchain 00:07:36.270 --> 00:07:37.720 align:start position:0% people working towards the blockchain middleware<00:07:36.750> that<00:07:36.900> can<00:07:37.020> solve<00:07:37.230> this<00:07:37.440> problem 00:07:37.720 --> 00:07:37.730 align:start position:0% middleware that can solve this problem 00:07:37.730 --> 00:07:40.670 align:start position:0% middleware that can solve this problem will<00:07:38.730> make<00:07:38.880> a<00:07:39.180> blockchain<00:07:39.900> were<00:07:40.200> aware<00:07:40.410> that 00:07:40.670 --> 00:07:40.680 align:start position:0% will make a blockchain were aware that 00:07:40.680 --> 00:07:44.330 align:start position:0% will make a blockchain were aware that payments<00:07:41.640> processors<00:07:42.150> data<00:07:42.780> providers<00:07:43.410> these 00:07:44.330 --> 00:07:44.340 align:start position:0% payments processors data providers these 00:07:44.340 --> 00:07:46.850 align:start position:0% payments processors data providers these signature<00:07:44.790> providers<00:07:45.300> various<00:07:45.870> API<00:07:46.200> services 00:07:46.850 --> 00:07:46.860 align:start position:0% signature providers various API services 00:07:46.860 --> 00:07:49.580 align:start position:0% signature providers various API services will<00:07:47.550> adopt<00:07:47.820> because<00:07:48.720> they<00:07:48.990> don't<00:07:49.260> want<00:07:49.530> to 00:07:49.580 --> 00:07:49.590 align:start position:0% will adopt because they don't want to 00:07:49.590 --> 00:07:51.950 align:start position:0% will adopt because they don't want to build<00:07:49.710> their<00:07:49.919> own<00:07:49.950> middleware<00:07:50.660> they<00:07:51.660> just 00:07:51.950 --> 00:07:51.960 align:start position:0% build their own middleware they just 00:07:51.960 --> 00:07:53.750 align:start position:0% build their own middleware they just want<00:07:52.169> to<00:07:52.200> sell<00:07:52.380> their<00:07:52.560> services<00:07:52.770> and<00:07:53.280> they 00:07:53.750 --> 00:07:53.760 align:start position:0% want to sell their services and they 00:07:53.760 --> 00:07:55.430 align:start position:0% want to sell their services and they constantly<00:07:54.120> buy<00:07:54.479> things<00:07:54.780> that<00:07:54.990> just<00:07:55.169> let<00:07:55.290> them 00:07:55.430 --> 00:07:55.440 align:start position:0% constantly buy things that just let them 00:07:55.440 --> 00:07:57.590 align:start position:0% constantly buy things that just let them sell<00:07:55.650> their<00:07:55.800> services<00:07:55.979> so<00:07:56.490> what<00:07:57.120> we<00:07:57.240> should<00:07:57.479> do 00:07:57.590 --> 00:07:57.600 align:start position:0% sell their services so what we should do 00:07:57.600 --> 00:07:59.960 align:start position:0% sell their services so what we should do in<00:07:57.840> our<00:07:58.140> opinion<00:07:58.650> is<00:07:58.800> that<00:07:59.130> if<00:07:59.550> we<00:07:59.820> as<00:07:59.940> a 00:07:59.960 --> 00:07:59.970 align:start position:0% in our opinion is that if we as a 00:07:59.970 --> 00:08:01.340 align:start position:0% in our opinion is that if we as a community<00:08:00.180> are<00:08:00.419> interested<00:08:00.900> in<00:08:00.990> this<00:08:01.080> problem 00:08:01.340 --> 00:08:01.350 align:start position:0% community are interested in this problem 00:08:01.350 --> 00:08:03.260 align:start position:0% community are interested in this problem we<00:08:02.220> should<00:08:02.280> solve<00:08:02.640> it<00:08:02.760> in<00:08:02.880> the<00:08:02.970> decentralized 00:08:03.260 --> 00:08:03.270 align:start position:0% we should solve it in the decentralized 00:08:03.270 --> 00:08:05.510 align:start position:0% we should solve it in the decentralized manner<00:08:03.720> that<00:08:04.380> allows<00:08:04.590> the<00:08:04.800> people<00:08:05.010> with<00:08:05.340> the 00:08:05.510 --> 00:08:05.520 align:start position:0% manner that allows the people with the 00:08:05.520 --> 00:08:07.700 align:start position:0% manner that allows the people with the data<00:08:05.700> resources<00:08:06.270> payment<00:08:06.870> resources<00:08:07.470> each 00:08:07.700 --> 00:08:07.710 align:start position:0% data resources payment resources each 00:08:07.710 --> 00:08:10.159 align:start position:0% data resources payment resources each signature<00:08:08.070> resources<00:08:08.790> various<00:08:09.540> other<00:08:09.720> api's 00:08:10.159 --> 00:08:10.169 align:start position:0% signature resources various other api's 00:08:10.169 --> 00:08:12.440 align:start position:0% signature resources various other api's to<00:08:10.919> be<00:08:11.040> able<00:08:11.220> to<00:08:11.310> provide<00:08:11.610> those<00:08:11.850> services<00:08:12.090> to 00:08:12.440 --> 00:08:12.450 align:start position:0% to be able to provide those services to 00:08:12.450 --> 00:08:15.500 align:start position:0% to be able to provide those services to contracts<00:08:13.350> so<00:08:14.340> those<00:08:14.490> contracts<00:08:15.090> can<00:08:15.240> then<00:08:15.360> do 00:08:15.500 --> 00:08:15.510 align:start position:0% contracts so those contracts can then do 00:08:15.510 --> 00:08:19.840 align:start position:0% contracts so those contracts can then do something<00:08:15.720> much<00:08:16.020> more<00:08:16.200> meaningful<00:08:16.530> right<00:08:18.080> now 00:08:19.840 --> 00:08:19.850 align:start position:0% something much more meaningful right now 00:08:19.850 --> 00:08:23.360 align:start position:0% something much more meaningful right now the<00:08:20.850> second<00:08:21.240> part<00:08:21.419> of<00:08:21.479> our<00:08:21.570> approach<00:08:22.370> after 00:08:23.360 --> 00:08:23.370 align:start position:0% the second part of our approach after 00:08:23.370 --> 00:08:25.070 align:start position:0% the second part of our approach after the<00:08:23.640> centralization<00:08:24.030> and<00:08:24.390> open<00:08:24.600> source<00:08:24.810> is 00:08:25.070 --> 00:08:25.080 align:start position:0% the centralization and open source is 00:08:25.080 --> 00:08:28.190 align:start position:0% the centralization and open source is the<00:08:25.530> application<00:08:26.010> of<00:08:26.220> trusted<00:08:27.030> hardware<00:08:27.390> so 00:08:28.190 --> 00:08:28.200 align:start position:0% the application of trusted hardware so 00:08:28.200 --> 00:08:31.490 align:start position:0% the application of trusted hardware so trusted<00:08:28.620> Hardware<00:08:29.150> provides<00:08:30.150> certain<00:08:30.750> tamper 00:08:31.490 --> 00:08:31.500 align:start position:0% trusted Hardware provides certain tamper 00:08:31.500 --> 00:08:33.800 align:start position:0% trusted Hardware provides certain tamper proof<00:08:31.710> nice<00:08:31.950> guarantees<00:08:32.430> in<00:08:32.820> this<00:08:33.539> case 00:08:33.800 --> 00:08:33.810 align:start position:0% proof nice guarantees in this case 00:08:33.810 --> 00:08:36.020 align:start position:0% proof nice guarantees in this case applied<00:08:34.349> to<00:08:34.770> Oracle's<00:08:35.219> those<00:08:35.550> guarantees 00:08:36.020 --> 00:08:36.030 align:start position:0% applied to Oracle's those guarantees 00:08:36.030 --> 00:08:38.839 align:start position:0% applied to Oracle's those guarantees extend<00:08:36.479> as<00:08:36.630> far<00:08:36.659> as<00:08:36.990> the<00:08:37.680> note<00:08:37.890> operator<00:08:38.370> will 00:08:38.839 --> 00:08:38.849 align:start position:0% extend as far as the note operator will 00:08:38.849 --> 00:08:40.880 align:start position:0% extend as far as the note operator will not<00:08:39.060> know<00:08:39.270> what<00:08:39.419> they<00:08:39.539> are<00:08:39.570> running<00:08:39.839> the<00:08:40.710> note 00:08:40.880 --> 00:08:40.890 align:start position:0% not know what they are running the note 00:08:40.890 --> 00:08:42.890 align:start position:0% not know what they are running the note operator<00:08:41.339> will<00:08:41.610> not<00:08:41.789> be<00:08:41.969> able<00:08:42.120> to<00:08:42.240> tamper<00:08:42.750> with 00:08:42.890 --> 00:08:42.900 align:start position:0% operator will not be able to tamper with 00:08:42.900 --> 00:08:45.050 align:start position:0% operator will not be able to tamper with the<00:08:43.020> data<00:08:43.260> the<00:08:44.010> note<00:08:44.159> operator<00:08:44.550> will<00:08:44.760> really 00:08:45.050 --> 00:08:45.060 align:start position:0% the data the note operator will really 00:08:45.060 --> 00:08:47.300 align:start position:0% the data the note operator will really only<00:08:45.510> be<00:08:45.900> able<00:08:46.140> to<00:08:46.230> turn<00:08:46.410> off<00:08:46.620> their<00:08:46.800> node<00:08:47.010> and 00:08:47.300 --> 00:08:47.310 align:start position:0% only be able to turn off their node and 00:08:47.310 --> 00:08:50.230 align:start position:0% only be able to turn off their node and that<00:08:48.270> will<00:08:48.420> be<00:08:48.540> an<00:08:48.630> immediate<00:08:48.780> signal<00:08:49.410> and 00:08:50.230 --> 00:08:50.240 align:start position:0% that will be an immediate signal and 00:08:50.240 --> 00:08:52.910 align:start position:0% that will be an immediate signal and with<00:08:51.240> even<00:08:51.390> basic<00:08:51.810> reputation<00:08:52.350> systems<00:08:52.709> they 00:08:52.910 --> 00:08:52.920 align:start position:0% with even basic reputation systems they 00:08:52.920 --> 00:08:55.680 align:start position:0% with even basic reputation systems they won't<00:08:53.130> participate<00:08:53.280> in<00:08:53.670> future<00:08:54.050> inputs<00:08:55.050> into 00:08:55.680 --> 00:08:55.690 align:start position:0% won't participate in future inputs into 00:08:55.690 --> 00:08:58.199 align:start position:0% won't participate in future inputs into high-value<00:08:55.990> contracts<00:08:56.800> right<00:08:57.129> so<00:08:58.089> the 00:08:58.199 --> 00:08:58.209 align:start position:0% high-value contracts right so the 00:08:58.209 --> 00:09:01.710 align:start position:0% high-value contracts right so the application<00:08:58.899> of<00:08:59.139> trusted<00:09:00.100> hardware<00:09:00.519> and<00:09:00.730> its 00:09:01.710 --> 00:09:01.720 align:start position:0% application of trusted hardware and its 00:09:01.720 --> 00:09:04.379 align:start position:0% application of trusted hardware and its new<00:09:01.930> recently<00:09:02.769> fall<00:09:02.980> form<00:09:03.339> in<00:09:03.699> terms<00:09:04.029> of<00:09:04.149> Intel 00:09:04.379 --> 00:09:04.389 align:start position:0% new recently fall form in terms of Intel 00:09:04.389 --> 00:09:07.110 align:start position:0% new recently fall form in terms of Intel SGX<00:09:04.540> is<00:09:05.139> something<00:09:06.129> we<00:09:06.339> think<00:09:06.639> has<00:09:06.850> a<00:09:06.879> lot<00:09:07.089> of 00:09:07.110 --> 00:09:07.120 align:start position:0% SGX is something we think has a lot of 00:09:07.120 --> 00:09:10.199 align:start position:0% SGX is something we think has a lot of merit<00:09:07.569> and<00:09:07.750> and<00:09:08.709> is<00:09:08.949> an<00:09:09.069> approach<00:09:09.399> that<00:09:09.940> that 00:09:10.199 --> 00:09:10.209 align:start position:0% merit and and is an approach that that 00:09:10.209 --> 00:09:11.910 align:start position:0% merit and and is an approach that that can<00:09:10.779> create<00:09:11.079> a<00:09:11.110> decentralized<00:09:11.740> oracle 00:09:11.910 --> 00:09:11.920 align:start position:0% can create a decentralized oracle 00:09:11.920 --> 00:09:14.519 align:start position:0% can create a decentralized oracle network<00:09:12.459> where<00:09:13.120> you<00:09:13.149> can<00:09:13.300> sufficiently<00:09:14.050> trust 00:09:14.519 --> 00:09:14.529 align:start position:0% network where you can sufficiently trust 00:09:14.529 --> 00:09:16.619 align:start position:0% network where you can sufficiently trust the<00:09:14.800> independent<00:09:15.310> node<00:09:15.459> operators<00:09:16.060> to 00:09:16.619 --> 00:09:16.629 align:start position:0% the independent node operators to 00:09:16.629 --> 00:09:19.949 align:start position:0% the independent node operators to execute<00:09:17.230> the<00:09:17.379> acquisition<00:09:17.949> of<00:09:18.040> data<00:09:18.250> and<00:09:18.959> the 00:09:19.949 --> 00:09:19.959 align:start position:0% execute the acquisition of data and the 00:09:19.959 --> 00:09:23.340 align:start position:0% execute the acquisition of data and the act<00:09:20.529> and<00:09:20.889> the<00:09:21.310> execution<00:09:21.879> of<00:09:21.970> payments<00:09:22.480> while 00:09:23.340 --> 00:09:23.350 align:start position:0% act and the execution of payments while 00:09:23.350 --> 00:09:26.490 align:start position:0% act and the execution of payments while not<00:09:23.860> knowing<00:09:24.569> important<00:09:25.569> things<00:09:25.870> like<00:09:26.170> your 00:09:26.490 --> 00:09:26.500 align:start position:0% not knowing important things like your 00:09:26.500 --> 00:09:29.970 align:start position:0% not knowing important things like your payment<00:09:26.889> credentials<00:09:27.220> or<00:09:27.870> what<00:09:28.870> data<00:09:29.769> they're 00:09:29.970 --> 00:09:29.980 align:start position:0% payment credentials or what data they're 00:09:29.980 --> 00:09:32.610 align:start position:0% payment credentials or what data they're executing<00:09:30.639> another<00:09:31.629> very<00:09:31.870> large<00:09:31.930> benefit<00:09:32.529> is 00:09:32.610 --> 00:09:32.620 align:start position:0% executing another very large benefit is 00:09:32.620 --> 00:09:34.650 align:start position:0% executing another very large benefit is the<00:09:32.740> ability<00:09:32.829> for<00:09:33.790> you<00:09:33.970> to<00:09:34.120> do<00:09:34.240> all<00:09:34.269> chin 00:09:34.650 --> 00:09:34.660 align:start position:0% the ability for you to do all chin 00:09:34.660 --> 00:09:36.689 align:start position:0% the ability for you to do all chin computation<00:09:35.410> in<00:09:35.589> this<00:09:35.769> same<00:09:35.980> Oracle<00:09:36.399> network 00:09:36.689 --> 00:09:36.699 align:start position:0% computation in this same Oracle network 00:09:36.699 --> 00:09:40.490 align:start position:0% computation in this same Oracle network so<00:09:37.329> the<00:09:37.420> Oracle<00:09:37.750> network<00:09:38.110> can<00:09:38.800> now<00:09:38.920> become<00:09:39.160> a 00:09:40.490 --> 00:09:40.500 align:start position:0% so the Oracle network can now become a 00:09:40.500 --> 00:09:43.379 align:start position:0% so the Oracle network can now become a desire<00:09:41.500> of<00:09:41.529> all<00:09:42.310> the<00:09:42.430> same<00:09:42.610> computation<00:09:43.329> of 00:09:43.379 --> 00:09:43.389 align:start position:0% desire of all the same computation of 00:09:43.389 --> 00:09:46.050 align:start position:0% desire of all the same computation of around<00:09:43.720> the<00:09:43.870> data<00:09:44.050> it<00:09:44.259> acquired<00:09:45.060> for 00:09:46.050 --> 00:09:46.060 align:start position:0% around the data it acquired for 00:09:46.060 --> 00:09:48.360 align:start position:0% around the data it acquired for intensive<00:09:46.899> computations<00:09:47.620> that<00:09:47.800> you<00:09:47.920> can't<00:09:48.160> or 00:09:48.360 --> 00:09:48.370 align:start position:0% intensive computations that you can't or 00:09:48.370 --> 00:09:51.090 align:start position:0% intensive computations that you can't or don't<00:09:48.550> want<00:09:48.819> to<00:09:48.939> do<00:09:49.149> unchanged<00:09:49.800> so<00:09:50.800> to<00:09:50.860> dive<00:09:51.069> a 00:09:51.090 --> 00:09:51.100 align:start position:0% don't want to do unchanged so to dive a 00:09:51.100 --> 00:09:53.129 align:start position:0% don't want to do unchanged so to dive a little<00:09:51.310> deeper<00:09:51.430> into<00:09:51.759> trusted<00:09:52.509> Hardware<00:09:52.899> and 00:09:53.129 --> 00:09:53.139 align:start position:0% little deeper into trusted Hardware and 00:09:53.139 --> 00:09:54.389 align:start position:0% little deeper into trusted Hardware and and<00:09:53.379> why<00:09:53.620> we<00:09:53.769> think<00:09:53.920> it's<00:09:54.100> an<00:09:54.189> interesting 00:09:54.389 --> 00:09:54.399 align:start position:0% and why we think it's an interesting 00:09:54.399 --> 00:09:58.050 align:start position:0% and why we think it's an interesting approach<00:09:55.829> the<00:09:56.829> the<00:09:57.100> the<00:09:57.399> main<00:09:57.610> premise 00:09:58.050 --> 00:09:58.060 align:start position:0% approach the the the main premise 00:09:58.060 --> 00:10:00.389 align:start position:0% approach the the the main premise underlying<00:09:58.300> trusted<00:09:59.230> hardware<00:09:59.589> is<00:09:59.769> that 00:10:00.389 --> 00:10:00.399 align:start position:0% underlying trusted hardware is that 00:10:00.399 --> 00:10:02.850 align:start position:0% underlying trusted hardware is that compared<00:10:01.029> to<00:10:01.180> previous<00:10:01.540> approaches<00:10:02.079> like 00:10:02.850 --> 00:10:02.860 align:start position:0% compared to previous approaches like 00:10:02.860 --> 00:10:04.679 align:start position:0% compared to previous approaches like various<00:10:03.279> HSMs<00:10:03.790> various<00:10:04.269> data<00:10:04.480> rights 00:10:04.679 --> 00:10:04.689 align:start position:0% various HSMs various data rights 00:10:04.689 --> 00:10:07.019 align:start position:0% various HSMs various data rights management<00:10:04.899> modules<00:10:05.529> it<00:10:06.130> has<00:10:06.399> a<00:10:06.430> smaller 00:10:07.019 --> 00:10:07.029 align:start position:0% management modules it has a smaller 00:10:07.029 --> 00:10:09.809 align:start position:0% management modules it has a smaller trusted<00:10:07.540> computing<00:10:07.810> base<00:10:08.189> so<00:10:09.189> what<00:10:09.670> that 00:10:09.809 --> 00:10:09.819 align:start position:0% trusted computing base so what that 00:10:09.819 --> 00:10:11.490 align:start position:0% trusted computing base so what that means<00:10:10.089> is<00:10:10.329> that<00:10:10.360> privileged<00:10:10.899> system<00:10:11.290> code 00:10:11.490 --> 00:10:11.500 align:start position:0% means is that privileged system code 00:10:11.500 --> 00:10:15.360 align:start position:0% means is that privileged system code like<00:10:11.769> the<00:10:12.279> OS<00:10:12.639> and<00:10:13.120> BIOS<00:10:13.889> are<00:10:14.889> no<00:10:15.069> longer 00:10:15.360 --> 00:10:15.370 align:start position:0% like the OS and BIOS are no longer 00:10:15.370 --> 00:10:17.429 align:start position:0% like the OS and BIOS are no longer attack<00:10:15.639> vectors<00:10:16.089> for<00:10:16.449> something<00:10:17.139> like<00:10:17.290> an 00:10:17.429 --> 00:10:17.439 align:start position:0% attack vectors for something like an 00:10:17.439 --> 00:10:20.040 align:start position:0% attack vectors for something like an Intel<00:10:17.680> SGX<00:10:17.829> Enclave<00:10:18.519> what<00:10:19.449> that<00:10:19.600> means<00:10:19.839> is 00:10:20.040 --> 00:10:20.050 align:start position:0% Intel SGX Enclave what that means is 00:10:20.050 --> 00:10:22.439 align:start position:0% Intel SGX Enclave what that means is that<00:10:20.079> you<00:10:20.500> can<00:10:20.680> give<00:10:20.860> even<00:10:21.459> encrypted<00:10:22.240> code 00:10:22.439 --> 00:10:22.449 align:start position:0% that you can give even encrypted code 00:10:22.449 --> 00:10:26.550 align:start position:0% that you can give even encrypted code into<00:10:23.290> the<00:10:23.699> the<00:10:24.699> Enclave<00:10:25.120> and<00:10:25.480> it<00:10:26.079> can<00:10:26.259> decrypt 00:10:26.550 --> 00:10:26.560 align:start position:0% into the the Enclave and it can decrypt 00:10:26.560 --> 00:10:28.920 align:start position:0% into the the Enclave and it can decrypt it<00:10:26.769> and<00:10:26.949> run<00:10:27.160> and<00:10:27.399> make<00:10:27.670> outputs<00:10:28.149> and<00:10:28.420> the 00:10:28.920 --> 00:10:28.930 align:start position:0% it and run and make outputs and the 00:10:28.930 --> 00:10:31.889 align:start position:0% it and run and make outputs and the operator<00:10:29.470> of<00:10:29.769> the<00:10:29.860> node<00:10:30.660> running<00:10:31.660> something 00:10:31.889 --> 00:10:31.899 align:start position:0% operator of the node running something 00:10:31.899 --> 00:10:33.319 align:start position:0% operator of the node running something like<00:10:32.050> until<00:10:32.500> SGX 00:10:33.319 --> 00:10:33.329 align:start position:0% like until SGX 00:10:33.329 --> 00:10:37.590 align:start position:0% like until SGX can't<00:10:34.329> tell<00:10:35.199> what's<00:10:35.410> going<00:10:35.589> on<00:10:36.180> they<00:10:37.180> they 00:10:37.590 --> 00:10:37.600 align:start position:0% can't tell what's going on they they 00:10:37.600 --> 00:10:40.410 align:start position:0% can't tell what's going on they they can't<00:10:37.839> acquire<00:10:38.170> private<00:10:38.620> information<00:10:39.420> and 00:10:40.410 --> 00:10:40.420 align:start position:0% can't acquire private information and 00:10:40.420 --> 00:10:41.639 align:start position:0% can't acquire private information and once<00:10:40.630> again<00:10:40.750> all<00:10:40.990> they<00:10:41.110> can<00:10:41.230> really<00:10:41.439> do<00:10:41.559> is 00:10:41.639 --> 00:10:41.649 align:start position:0% once again all they can really do is 00:10:41.649 --> 00:10:43.170 align:start position:0% once again all they can really do is turn<00:10:41.829> it<00:10:41.889> off<00:10:42.100> which<00:10:42.519> becomes<00:10:42.910> a<00:10:43.059> me 00:10:43.170 --> 00:10:43.180 align:start position:0% turn it off which becomes a me 00:10:43.180 --> 00:10:47.340 align:start position:0% turn it off which becomes a me immediately<00:10:43.689> apparent<00:10:45.480> now<00:10:46.480> the<00:10:46.540> the 00:10:47.340 --> 00:10:47.350 align:start position:0% immediately apparent now the the 00:10:47.350 --> 00:10:49.499 align:start position:0% immediately apparent now the the approach<00:10:47.680> that<00:10:47.709> that<00:10:48.370> we're<00:10:49.269> adopting 00:10:49.499 --> 00:10:49.509 align:start position:0% approach that that we're adopting 00:10:49.509 --> 00:10:51.629 align:start position:0% approach that that we're adopting towards<00:10:50.170> trusted<00:10:50.559> hardware<00:10:50.889> in<00:10:51.069> the<00:10:51.160> context 00:10:51.629 --> 00:10:51.639 align:start position:0% towards trusted hardware in the context 00:10:51.639 --> 00:10:53.790 align:start position:0% towards trusted hardware in the context of<00:10:51.699> a<00:10:51.790> decentralized<00:10:52.329> oracle<00:10:52.540> network<00:10:53.019> with 00:10:53.790 --> 00:10:53.800 align:start position:0% of a decentralized oracle network with 00:10:53.800 --> 00:10:56.069 align:start position:0% of a decentralized oracle network with the<00:10:53.949> help<00:10:54.129> of<00:10:54.189> the<00:10:54.339> very<00:10:54.519> smart<00:10:54.790> folks<00:10:55.000> at<00:10:55.240> ic3 00:10:56.069 --> 00:10:56.079 align:start position:0% the help of the very smart folks at ic3 00:10:56.079 --> 00:10:57.629 align:start position:0% the help of the very smart folks at ic3 who<00:10:56.470> were<00:10:56.589> very<00:10:56.769> lucky<00:10:56.980> to<00:10:57.160> be<00:10:57.250> working<00:10:57.370> with 00:10:57.629 --> 00:10:57.639 align:start position:0% who were very lucky to be working with 00:10:57.639 --> 00:11:01.319 align:start position:0% who were very lucky to be working with our<00:10:58.139> is<00:10:59.139> called<00:10:59.439> town<00:10:59.649> crier<00:10:59.970> town<00:11:00.970> crier 00:11:01.319 --> 00:11:01.329 align:start position:0% our is called town crier town crier 00:11:01.329 --> 00:11:05.069 align:start position:0% our is called town crier town crier basically<00:11:02.230> applies<00:11:02.769> Intel<00:11:03.550> SGX<00:11:03.779> which<00:11:04.779> at 00:11:05.069 --> 00:11:05.079 align:start position:0% basically applies Intel SGX which at 00:11:05.079 --> 00:11:06.990 align:start position:0% basically applies Intel SGX which at this<00:11:05.259> moment<00:11:05.470> appears<00:11:06.370> to<00:11:06.519> be<00:11:06.639> the<00:11:06.819> leading 00:11:06.990 --> 00:11:07.000 align:start position:0% this moment appears to be the leading 00:11:07.000 --> 00:11:08.710 align:start position:0% this moment appears to be the leading trusted<00:11:07.750> Hardware<00:11:08.079> approach 00:11:08.710 --> 00:11:08.720 align:start position:0% trusted Hardware approach 00:11:08.720 --> 00:11:12.610 align:start position:0% trusted Hardware approach to<00:11:09.709> the<00:11:10.189> problem<00:11:10.879> of<00:11:11.120> secure<00:11:11.779> tamper-proof 00:11:12.610 --> 00:11:12.620 align:start position:0% to the problem of secure tamper-proof 00:11:12.620 --> 00:11:17.079 align:start position:0% to the problem of secure tamper-proof Oracle's<00:11:13.610> it<00:11:14.329> basically<00:11:15.139> allows<00:11:15.860> a<00:11:16.310> contract 00:11:17.079 --> 00:11:17.089 align:start position:0% Oracle's it basically allows a contract 00:11:17.089 --> 00:11:20.290 align:start position:0% Oracle's it basically allows a contract to<00:11:17.689> talk<00:11:17.899> to<00:11:18.079> an<00:11:18.199> INT<00:11:18.350> SGX<00:11:18.889> enclave<00:11:19.370> that<00:11:20.089> then 00:11:20.290 --> 00:11:20.300 align:start position:0% to talk to an INT SGX enclave that then 00:11:20.300 --> 00:11:22.600 align:start position:0% to talk to an INT SGX enclave that then using<00:11:20.779> the<00:11:20.899> existing<00:11:21.110> TLS<00:11:21.649> scheme<00:11:21.980> can 00:11:22.600 --> 00:11:22.610 align:start position:0% using the existing TLS scheme can 00:11:22.610 --> 00:11:24.999 align:start position:0% using the existing TLS scheme can acquire<00:11:22.939> data<00:11:23.180> from<00:11:23.509> a<00:11:23.600> data<00:11:23.779> source<00:11:24.079> and<00:11:24.379> then 00:11:24.999 --> 00:11:25.009 align:start position:0% acquire data from a data source and then 00:11:25.009 --> 00:11:27.670 align:start position:0% acquire data from a data source and then provably<00:11:25.490> return<00:11:26.029> only<00:11:26.720> the<00:11:27.170> value<00:11:27.439> that<00:11:27.560> it 00:11:27.670 --> 00:11:27.680 align:start position:0% provably return only the value that it 00:11:27.680 --> 00:11:30.850 align:start position:0% provably return only the value that it acquired<00:11:27.980> from<00:11:28.970> the<00:11:29.000> Enclave<00:11:29.769> into<00:11:30.769> the 00:11:30.850 --> 00:11:30.860 align:start position:0% acquired from the Enclave into the 00:11:30.860 --> 00:11:33.129 align:start position:0% acquired from the Enclave into the requesting<00:11:31.370> contract<00:11:31.850> right<00:11:32.660> in<00:11:32.779> this<00:11:32.930> case 00:11:33.129 --> 00:11:33.139 align:start position:0% requesting contract right in this case 00:11:33.139 --> 00:11:34.420 align:start position:0% requesting contract right in this case the<00:11:33.290> requesting<00:11:33.709> contract<00:11:34.129> is<00:11:34.310> the 00:11:34.420 --> 00:11:34.430 align:start position:0% the requesting contract is the 00:11:34.430 --> 00:11:36.429 align:start position:0% the requesting contract is the town-crier<00:11:34.730> contract<00:11:35.329> which<00:11:35.540> then<00:11:35.750> kind<00:11:36.350> of 00:11:36.429 --> 00:11:36.439 align:start position:0% town-crier contract which then kind of 00:11:36.439 --> 00:11:39.610 align:start position:0% town-crier contract which then kind of is<00:11:36.620> the<00:11:37.000> unchained<00:11:38.000> bridge<00:11:38.300> from<00:11:39.019> the<00:11:39.079> Enclave 00:11:39.610 --> 00:11:39.620 align:start position:0% is the unchained bridge from the Enclave 00:11:39.620 --> 00:11:41.559 align:start position:0% is the unchained bridge from the Enclave into<00:11:40.100> the<00:11:40.220> user<00:11:40.399> contract<00:11:40.970> right<00:11:41.300> so<00:11:41.449> it's 00:11:41.559 --> 00:11:41.569 align:start position:0% into the user contract right so it's 00:11:41.569 --> 00:11:44.019 align:start position:0% into the user contract right so it's it's<00:11:41.990> a<00:11:42.079> very<00:11:42.259> common<00:11:42.500> Oracle<00:11:42.949> set<00:11:43.160> up<00:11:43.310> but<00:11:44.000> the 00:11:44.019 --> 00:11:44.029 align:start position:0% it's a very common Oracle set up but the 00:11:44.029 --> 00:11:46.329 align:start position:0% it's a very common Oracle set up but the the<00:11:44.420> difference<00:11:44.810> is<00:11:44.990> that<00:11:45.740> the<00:11:45.920> Enclave 00:11:46.329 --> 00:11:46.339 align:start position:0% the difference is that the Enclave 00:11:46.339 --> 00:11:48.759 align:start position:0% the difference is that the Enclave provides<00:11:47.209> this<00:11:47.420> tamper<00:11:48.290> proof<00:11:48.500> guarantee 00:11:48.759 --> 00:11:48.769 align:start position:0% provides this tamper proof guarantee 00:11:48.769 --> 00:11:52.840 align:start position:0% provides this tamper proof guarantee right<00:11:49.699> so<00:11:50.509> in<00:11:51.290> our<00:11:51.560> opinion<00:11:51.860> when<00:11:52.370> you<00:11:52.459> look<00:11:52.670> at 00:11:52.840 --> 00:11:52.850 align:start position:0% right so in our opinion when you look at 00:11:52.850 --> 00:11:55.540 align:start position:0% right so in our opinion when you look at how<00:11:53.689> do<00:11:53.750> we<00:11:53.990> make<00:11:54.139> smart<00:11:54.470> contracts<00:11:55.069> useful 00:11:55.540 --> 00:11:55.550 align:start position:0% how do we make smart contracts useful 00:11:55.550 --> 00:11:57.790 align:start position:0% how do we make smart contracts useful what<00:11:55.819> is<00:11:55.939> their<00:11:56.089> unique<00:11:56.360> value<00:11:56.810> it's<00:11:57.379> the<00:11:57.589> fact 00:11:57.790 --> 00:11:57.800 align:start position:0% what is their unique value it's the fact 00:11:57.800 --> 00:12:00.400 align:start position:0% what is their unique value it's the fact that<00:11:57.889> their<00:11:58.100> tamper<00:11:58.519> proof<00:11:58.870> tamper<00:11:59.870> resistant 00:12:00.400 --> 00:12:00.410 align:start position:0% that their tamper proof tamper resistant 00:12:00.410 --> 00:12:03.220 align:start position:0% that their tamper proof tamper resistant kind<00:12:01.160> of<00:12:01.279> these<00:12:01.459> unstoppable<00:12:02.329> financial 00:12:03.220 --> 00:12:03.230 align:start position:0% kind of these unstoppable financial 00:12:03.230 --> 00:12:07.300 align:start position:0% kind of these unstoppable financial agreements<00:12:03.769> and<00:12:04.089> as<00:12:05.089> as<00:12:05.569> tamper<00:12:06.139> proof<00:12:06.350> as<00:12:06.649> we 00:12:07.300 --> 00:12:07.310 align:start position:0% agreements and as as tamper proof as we 00:12:07.310 --> 00:12:10.300 align:start position:0% agreements and as as tamper proof as we can<00:12:07.970> make<00:12:08.209> something<00:12:09.199> like<00:12:09.379> the<00:12:09.709> triggers<00:12:10.100> of 00:12:10.300 --> 00:12:10.310 align:start position:0% can make something like the triggers of 00:12:10.310 --> 00:12:14.259 align:start position:0% can make something like the triggers of those<00:12:10.459> agreements<00:12:12.160> is<00:12:13.160> probably<00:12:13.759> the<00:12:13.939> right 00:12:14.259 --> 00:12:14.269 align:start position:0% those agreements is probably the right 00:12:14.269 --> 00:12:16.150 align:start position:0% those agreements is probably the right direction<00:12:14.449> to<00:12:14.839> go<00:12:14.959> in<00:12:14.990> and<00:12:15.319> and<00:12:15.829> those<00:12:15.980> two 00:12:16.150 --> 00:12:16.160 align:start position:0% direction to go in and and those two 00:12:16.160 --> 00:12:17.259 align:start position:0% direction to go in and and those two approaches<00:12:16.639> once<00:12:16.819> again 00:12:17.259 --> 00:12:17.269 align:start position:0% approaches once again 00:12:17.269 --> 00:12:20.319 align:start position:0% approaches once again one<00:12:18.199> is<00:12:18.699> decentralization<00:12:19.699> and<00:12:20.029> the<00:12:20.180> other 00:12:20.319 --> 00:12:20.329 align:start position:0% one is decentralization and the other 00:12:20.329 --> 00:12:21.639 align:start position:0% one is decentralization and the other one<00:12:20.480> is<00:12:20.569> the<00:12:20.689> application<00:12:20.779> of<00:12:21.290> trusted 00:12:21.639 --> 00:12:21.649 align:start position:0% one is the application of trusted 00:12:21.649 --> 00:12:25.840 align:start position:0% one is the application of trusted hardware<00:12:22.540> now<00:12:23.569> how<00:12:24.500> this<00:12:24.709> would<00:12:24.920> look<00:12:24.949> if 00:12:25.840 --> 00:12:25.850 align:start position:0% hardware now how this would look if 00:12:25.850 --> 00:12:27.610 align:start position:0% hardware now how this would look if trusted<00:12:26.360> Hardware<00:12:26.720> works<00:12:27.050> and<00:12:27.319> everything 00:12:27.610 --> 00:12:27.620 align:start position:0% trusted Hardware works and everything 00:12:27.620 --> 00:12:30.610 align:start position:0% trusted Hardware works and everything works<00:12:27.800> out<00:12:27.949> properly<00:12:28.399> is<00:12:28.639> that<00:12:29.329> a<00:12:29.870> user<00:12:30.290> shows 00:12:30.610 --> 00:12:30.620 align:start position:0% works out properly is that a user shows 00:12:30.620 --> 00:12:32.939 align:start position:0% works out properly is that a user shows up<00:12:30.800> and<00:12:30.980> says<00:12:31.160> I<00:12:31.220> have<00:12:31.670> a<00:12:32.209> very<00:12:32.720> large 00:12:32.939 --> 00:12:32.949 align:start position:0% up and says I have a very large 00:12:32.949 --> 00:12:36.009 align:start position:0% up and says I have a very large computation<00:12:33.949> that<00:12:34.220> needs<00:12:34.399> data<00:12:34.670> I'm<00:12:35.569> going<00:12:35.660> to 00:12:36.009 --> 00:12:36.019 align:start position:0% computation that needs data I'm going to 00:12:36.019 --> 00:12:39.309 align:start position:0% computation that needs data I'm going to give<00:12:36.199> that<00:12:36.379> computation<00:12:37.189> into<00:12:37.819> the<00:12:38.329> the 00:12:39.309 --> 00:12:39.319 align:start position:0% give that computation into the the 00:12:39.319 --> 00:12:41.259 align:start position:0% give that computation into the the relevant<00:12:39.559> node<00:12:39.889> the<00:12:40.550> relevant<00:12:40.910> node<00:12:41.029> is<00:12:41.149> going 00:12:41.259 --> 00:12:41.269 align:start position:0% relevant node the relevant node is going 00:12:41.269 --> 00:12:43.119 align:start position:0% relevant node the relevant node is going to<00:12:41.329> take<00:12:41.509> that<00:12:41.660> computation<00:12:42.290> and<00:12:42.529> run<00:12:42.949> it<00:12:43.040> in 00:12:43.119 --> 00:12:43.129 align:start position:0% to take that computation and run it in 00:12:43.129 --> 00:12:45.999 align:start position:0% to take that computation and run it in the<00:12:43.250> Enclave<00:12:43.699> inside<00:12:44.629> an<00:12:44.899> EVM<00:12:45.319> right<00:12:45.889> so 00:12:45.999 --> 00:12:46.009 align:start position:0% the Enclave inside an EVM right so 00:12:46.009 --> 00:12:47.350 align:start position:0% the Enclave inside an EVM right so there'll<00:12:46.160> be<00:12:46.220> an<00:12:46.339> EVM<00:12:46.730> running<00:12:47.059> inside<00:12:47.300> the 00:12:47.350 --> 00:12:47.360 align:start position:0% there'll be an EVM running inside the 00:12:47.360 --> 00:12:49.749 align:start position:0% there'll be an EVM running inside the Enclave<00:12:47.839> the<00:12:48.319> EVM<00:12:48.740> will<00:12:49.129> run<00:12:49.339> the<00:12:49.430> computation 00:12:49.749 --> 00:12:49.759 align:start position:0% Enclave the EVM will run the computation 00:12:49.759 --> 00:12:52.389 align:start position:0% Enclave the EVM will run the computation and<00:12:50.269> it<00:12:50.720> will<00:12:50.809> run<00:12:50.959> it<00:12:51.050> privately<00:12:51.470> such<00:12:52.189> that 00:12:52.389 --> 00:12:52.399 align:start position:0% and it will run it privately such that 00:12:52.399 --> 00:12:53.980 align:start position:0% and it will run it privately such that even<00:12:52.519> the<00:12:52.699> node<00:12:52.850> operator<00:12:53.240> can't<00:12:53.509> acquire<00:12:53.839> the 00:12:53.980 --> 00:12:53.990 align:start position:0% even the node operator can't acquire the 00:12:53.990 --> 00:12:58.389 align:start position:0% even the node operator can't acquire the data<00:12:54.279> if<00:12:55.449> and<00:12:56.449> then<00:12:56.839> they'll<00:12:57.800> return<00:12:58.100> a<00:12:58.129> query 00:12:58.389 --> 00:12:58.399 align:start position:0% data if and then they'll return a query 00:12:58.399 --> 00:13:00.610 align:start position:0% data if and then they'll return a query ID<00:12:58.579> the<00:12:58.850> query<00:12:59.059> ID<00:12:59.240> is<00:12:59.899> what's<00:13:00.170> used<00:13:00.350> to<00:13:00.500> pay 00:13:00.610 --> 00:13:00.620 align:start position:0% ID the query ID is what's used to pay 00:13:00.620 --> 00:13:02.379 align:start position:0% ID the query ID is what's used to pay the<00:13:00.649> contract<00:13:01.189> and<00:13:01.370> it<00:13:01.430> returns<00:13:01.939> relevant 00:13:02.379 --> 00:13:02.389 align:start position:0% the contract and it returns relevant 00:13:02.389 --> 00:13:05.530 align:start position:0% the contract and it returns relevant information<00:13:02.839> for<00:13:03.019> payment<00:13:03.350> after<00:13:04.220> that<00:13:05.029> well 00:13:05.530 --> 00:13:05.540 align:start position:0% information for payment after that well 00:13:05.540 --> 00:13:08.920 align:start position:0% information for payment after that well what<00:13:05.870> happens<00:13:06.230> is<00:13:07.269> let's<00:13:08.269> say<00:13:08.480> one<00:13:08.689> of<00:13:08.720> the 00:13:08.920 --> 00:13:08.930 align:start position:0% what happens is let's say one of the 00:13:08.930 --> 00:13:11.259 align:start position:0% what happens is let's say one of the counterparties<00:13:09.889> wants<00:13:10.220> to<00:13:10.339> know<00:13:10.490> what<00:13:11.149> is 00:13:11.259 --> 00:13:11.269 align:start position:0% counterparties wants to know what is 00:13:11.269 --> 00:13:13.150 align:start position:0% counterparties wants to know what is this<00:13:11.420> Oracle<00:13:11.809> doing<00:13:12.110> what<00:13:12.860> is<00:13:12.980> this 00:13:13.150 --> 00:13:13.160 align:start position:0% this Oracle doing what is this 00:13:13.160 --> 00:13:15.249 align:start position:0% this Oracle doing what is this decentralized<00:13:14.120> oracle<00:13:14.329> network<00:13:14.809> or<00:13:14.930> this<00:13:15.079> set 00:13:15.249 --> 00:13:15.259 align:start position:0% decentralized oracle network or this set 00:13:15.259 --> 00:13:17.290 align:start position:0% decentralized oracle network or this set of<00:13:15.350> Oracle's<00:13:15.769> that<00:13:16.339> is<00:13:16.459> that<00:13:16.790> are<00:13:16.910> going<00:13:17.149> to 00:13:17.290 --> 00:13:17.300 align:start position:0% of Oracle's that is that are going to 00:13:17.300 --> 00:13:19.350 align:start position:0% of Oracle's that is that are going to trigger<00:13:17.569> the<00:13:17.779> agreement<00:13:18.259> that<00:13:18.380> I'm<00:13:18.470> a<00:13:18.500> part<00:13:18.740> of 00:13:19.350 --> 00:13:19.360 align:start position:0% trigger the agreement that I'm a part of 00:13:19.360 --> 00:13:21.610 align:start position:0% trigger the agreement that I'm a part of what<00:13:20.360> actions<00:13:20.569> are<00:13:20.959> they<00:13:21.079> actually<00:13:21.380> going<00:13:21.529> to 00:13:21.610 --> 00:13:21.620 align:start position:0% what actions are they actually going to 00:13:21.620 --> 00:13:22.390 align:start position:0% what actions are they actually going to take<00:13:21.889> can<00:13:22.220> you 00:13:22.390 --> 00:13:22.400 align:start position:0% take can you 00:13:22.400 --> 00:13:24.700 align:start position:0% take can you please<00:13:22.580> return<00:13:22.940> to<00:13:23.180> me<00:13:23.330> the<00:13:23.840> code<00:13:24.110> that<00:13:24.590> you're 00:13:24.700 --> 00:13:24.710 align:start position:0% please return to me the code that you're 00:13:24.710 --> 00:13:28.840 align:start position:0% please return to me the code that you're gonna<00:13:24.890> execute<00:13:25.520> at<00:13:25.760> Timex<00:13:26.510> at<00:13:27.470> that<00:13:27.710> point<00:13:28.070> the 00:13:28.840 --> 00:13:28.850 align:start position:0% gonna execute at Timex at that point the 00:13:28.850 --> 00:13:31.990 align:start position:0% gonna execute at Timex at that point the counterparty<00:13:29.450> this<00:13:29.780> case<00:13:29.960> Bob<00:13:30.200> receives<00:13:31.190> back 00:13:31.990 --> 00:13:32.000 align:start position:0% counterparty this case Bob receives back 00:13:32.000 --> 00:13:33.550 align:start position:0% counterparty this case Bob receives back an<00:13:32.210> encrypted<00:13:32.510> blob<00:13:32.780> which<00:13:32.990> he<00:13:33.140> can<00:13:33.290> decrypt 00:13:33.550 --> 00:13:33.560 align:start position:0% an encrypted blob which he can decrypt 00:13:33.560 --> 00:13:34.870 align:start position:0% an encrypted blob which he can decrypt because<00:13:33.800> he<00:13:33.890> has<00:13:33.980> the<00:13:34.100> relevant<00:13:34.400> private<00:13:34.550> key 00:13:34.870 --> 00:13:34.880 align:start position:0% because he has the relevant private key 00:13:34.880 --> 00:13:38.500 align:start position:0% because he has the relevant private key so<00:13:35.090> in<00:13:36.050> in<00:13:36.260> this<00:13:36.440> scenario<00:13:37.180> what's<00:13:38.180> been<00:13:38.360> done 00:13:38.500 --> 00:13:38.510 align:start position:0% so in in this scenario what's been done 00:13:38.510 --> 00:13:40.990 align:start position:0% so in in this scenario what's been done is<00:13:38.660> that<00:13:38.690> the<00:13:39.380> creator<00:13:39.740> of<00:13:39.890> a<00:13:40.250> smart<00:13:40.490> contract 00:13:40.990 --> 00:13:41.000 align:start position:0% is that the creator of a smart contract 00:13:41.000 --> 00:13:45.730 align:start position:0% is that the creator of a smart contract has<00:13:42.190> written<00:13:43.190> in<00:13:43.930> Oracle<00:13:44.930> instructions<00:13:45.470> in 00:13:45.730 --> 00:13:45.740 align:start position:0% has written in Oracle instructions in 00:13:45.740 --> 00:13:47.710 align:start position:0% has written in Oracle instructions in this<00:13:45.950> case<00:13:46.160> in<00:13:46.370> solidity<00:13:46.700> so<00:13:47.420> they've<00:13:47.540> written 00:13:47.710 --> 00:13:47.720 align:start position:0% this case in solidity so they've written 00:13:47.720 --> 00:13:51.430 align:start position:0% this case in solidity so they've written Oracle<00:13:48.080> instructions<00:13:48.590> in<00:13:49.310> in<00:13:50.180> in<00:13:50.480> a<00:13:51.140> format 00:13:51.430 --> 00:13:51.440 align:start position:0% Oracle instructions in in in a format 00:13:51.440 --> 00:13:52.570 align:start position:0% Oracle instructions in in in a format they're<00:13:51.620> already<00:13:51.860> used<00:13:52.010> to<00:13:52.100> working<00:13:52.430> with 00:13:52.570 --> 00:13:52.580 align:start position:0% they're already used to working with 00:13:52.580 --> 00:13:54.970 align:start position:0% they're already used to working with that<00:13:52.790> that<00:13:53.240> compiles<00:13:53.780> down<00:13:53.930> to<00:13:54.110> EVM<00:13:54.530> byte<00:13:54.740> code 00:13:54.970 --> 00:13:54.980 align:start position:0% that that compiles down to EVM byte code 00:13:54.980 --> 00:13:57.520 align:start position:0% that that compiles down to EVM byte code they've<00:13:55.940> put<00:13:56.330> those<00:13:56.480> Oracle<00:13:56.930> instructions 00:13:57.520 --> 00:13:57.530 align:start position:0% they've put those Oracle instructions 00:13:57.530 --> 00:14:02.050 align:start position:0% they've put those Oracle instructions into<00:13:57.970> the<00:13:58.970> V<00:13:59.810> Enclave<00:14:00.340> they've<00:14:01.340> set<00:14:01.640> it<00:14:01.670> up<00:14:01.850> to 00:14:02.050 --> 00:14:02.060 align:start position:0% into the V Enclave they've set it up to 00:14:02.060 --> 00:14:03.850 align:start position:0% into the V Enclave they've set it up to trigger<00:14:02.330> their<00:14:02.510> contract<00:14:03.050> without<00:14:03.440> the<00:14:03.710> node 00:14:03.850 --> 00:14:03.860 align:start position:0% trigger their contract without the node 00:14:03.860 --> 00:14:06.280 align:start position:0% trigger their contract without the node operator<00:14:04.280> knowing<00:14:04.670> they've<00:14:05.360> done<00:14:05.630> this<00:14:05.810> with 00:14:06.280 --> 00:14:06.290 align:start position:0% operator knowing they've done this with 00:14:06.290 --> 00:14:08.770 align:start position:0% operator knowing they've done this with anywhere<00:14:06.830> from<00:14:06.890> 5<00:14:07.250> 10<00:14:07.580> 15<00:14:08.060> 20<00:14:08.180> in<00:14:08.630> the 00:14:08.770 --> 00:14:08.780 align:start position:0% anywhere from 5 10 15 20 in the 00:14:08.780 --> 00:14:11.230 align:start position:0% anywhere from 5 10 15 20 in the individual<00:14:09.500> node<00:14:09.650> operators<00:14:10.190> so<00:14:10.820> that<00:14:10.850> if<00:14:11.060> one 00:14:11.230 --> 00:14:11.240 align:start position:0% individual node operators so that if one 00:14:11.240 --> 00:14:12.970 align:start position:0% individual node operators so that if one fails<00:14:11.570> or<00:14:11.810> if<00:14:11.870> one<00:14:12.020> is<00:14:12.050> attacked<00:14:12.410> it<00:14:12.650> doesn't 00:14:12.970 --> 00:14:12.980 align:start position:0% fails or if one is attacked it doesn't 00:14:12.980 --> 00:14:14.950 align:start position:0% fails or if one is attacked it doesn't it<00:14:13.370> doesn't<00:14:13.700> compromise<00:14:13.850> the<00:14:14.330> execution<00:14:14.900> of 00:14:14.950 --> 00:14:14.960 align:start position:0% it doesn't compromise the execution of 00:14:14.960 --> 00:14:17.470 align:start position:0% it doesn't compromise the execution of the<00:14:15.080> contract<00:14:15.560> and<00:14:15.850> then<00:14:16.850> they've<00:14:17.060> done<00:14:17.270> it<00:14:17.360> in 00:14:17.470 --> 00:14:17.480 align:start position:0% the contract and then they've done it in 00:14:17.480 --> 00:14:19.210 align:start position:0% the contract and then they've done it in such<00:14:17.660> a<00:14:17.690> way<00:14:17.930> that<00:14:17.960> if<00:14:18.380> their<00:14:18.560> counterparty 00:14:19.210 --> 00:14:19.220 align:start position:0% such a way that if their counterparty 00:14:19.220 --> 00:14:22.240 align:start position:0% such a way that if their counterparty wants<00:14:19.490> to<00:14:19.610> know<00:14:19.730> what<00:14:20.450> is<00:14:20.750> the<00:14:21.590> Oracle<00:14:21.860> setup 00:14:22.240 --> 00:14:22.250 align:start position:0% wants to know what is the Oracle setup 00:14:22.250 --> 00:14:23.890 align:start position:0% wants to know what is the Oracle setup we're<00:14:22.400> using<00:14:22.550> going<00:14:22.910> to<00:14:23.000> do<00:14:23.120> at<00:14:23.240> time<00:14:23.420> X<00:14:23.600> let<00:14:23.870> me 00:14:23.890 --> 00:14:23.900 align:start position:0% we're using going to do at time X let me 00:14:23.900 --> 00:14:25.390 align:start position:0% we're using going to do at time X let me randomly<00:14:24.500> checked<00:14:24.740> at<00:14:24.890> any<00:14:25.010> time<00:14:25.220> I<00:14:25.250> would 00:14:25.390 --> 00:14:25.400 align:start position:0% randomly checked at any time I would 00:14:25.400 --> 00:14:28.540 align:start position:0% randomly checked at any time I would like<00:14:25.640> they<00:14:26.540> can<00:14:26.750> go<00:14:26.930> submit<00:14:27.590> the<00:14:27.680> query<00:14:27.860> ID<00:14:28.160> and 00:14:28.540 --> 00:14:28.550 align:start position:0% like they can go submit the query ID and 00:14:28.550 --> 00:14:31.030 align:start position:0% like they can go submit the query ID and receive<00:14:29.300> both<00:14:29.930> the<00:14:29.960> encrypted<00:14:30.380> blob<00:14:30.710> and<00:14:30.980> then 00:14:31.030 --> 00:14:31.040 align:start position:0% receive both the encrypted blob and then 00:14:31.040 --> 00:14:33.670 align:start position:0% receive both the encrypted blob and then anta<00:14:31.520> station<00:14:31.970> from<00:14:32.510> the<00:14:32.660> Enclave<00:14:33.080> proving<00:14:33.560> to 00:14:33.670 --> 00:14:33.680 align:start position:0% anta station from the Enclave proving to 00:14:33.680 --> 00:14:36.340 align:start position:0% anta station from the Enclave proving to them<00:14:33.800> that<00:14:34.670> the<00:14:34.790> execution<00:14:35.150> that<00:14:35.960> is<00:14:36.050> supposed 00:14:36.340 --> 00:14:36.350 align:start position:0% them that the execution that is supposed 00:14:36.350 --> 00:14:38.530 align:start position:0% them that the execution that is supposed to<00:14:36.440> happen<00:14:36.590> at<00:14:36.860> time<00:14:37.040> X<00:14:37.220> is<00:14:37.490> is<00:14:38.210> going<00:14:38.450> to 00:14:38.530 --> 00:14:38.540 align:start position:0% to happen at time X is is going to 00:14:38.540 --> 00:14:41.680 align:start position:0% to happen at time X is is going to happen<00:14:38.960> right<00:14:39.220> so<00:14:40.220> at<00:14:40.310> this<00:14:40.430> point<00:14:40.700> we<00:14:41.150> we<00:14:41.510> have 00:14:41.680 --> 00:14:41.690 align:start position:0% happen right so at this point we we have 00:14:41.690 --> 00:14:44.590 align:start position:0% happen right so at this point we we have multiple<00:14:42.560> node<00:14:42.890> operators<00:14:43.540> executing<00:14:44.540> a 00:14:44.590 --> 00:14:44.600 align:start position:0% multiple node operators executing a 00:14:44.600 --> 00:14:47.500 align:start position:0% multiple node operators executing a valuable<00:14:44.900> off<00:14:45.260> chain<00:14:45.530> operation<00:14:46.070> and<00:14:46.330> we<00:14:47.330> have 00:14:47.500 --> 00:14:47.510 align:start position:0% valuable off chain operation and we have 00:14:47.510 --> 00:14:49.150 align:start position:0% valuable off chain operation and we have them<00:14:47.990> being<00:14:48.200> able<00:14:48.350> to<00:14:48.530> prove<00:14:48.830> it 00:14:49.150 --> 00:14:49.160 align:start position:0% them being able to prove it 00:14:49.160 --> 00:14:54.360 align:start position:0% them being able to prove it to<00:14:49.790> the<00:14:50.180> other<00:14:50.330> parties<00:14:50.720> in<00:14:50.840> the<00:14:50.870> transaction 00:14:54.360 --> 00:14:54.370 align:start position:0% 00:14:54.370 --> 00:14:57.160 align:start position:0% the<00:14:55.370> the<00:14:55.910> benefits<00:14:56.360> of<00:14:56.510> this<00:14:56.600> approach<00:14:56.930> in<00:14:57.110> our 00:14:57.160 --> 00:14:57.170 align:start position:0% the the benefits of this approach in our 00:14:57.170 --> 00:15:00.400 align:start position:0% the the benefits of this approach in our opinion<00:14:57.680> are<00:14:58.120> basically<00:14:59.120> that<00:14:59.330> you<00:15:00.140> can<00:15:00.260> have 00:15:00.400 --> 00:15:00.410 align:start position:0% opinion are basically that you can have 00:15:00.410 --> 00:15:03.790 align:start position:0% opinion are basically that you can have very<00:15:00.650> scalable<00:15:01.330> execution<00:15:02.330> off<00:15:02.420> chain<00:15:02.800> you 00:15:03.790 --> 00:15:03.800 align:start position:0% very scalable execution off chain you 00:15:03.800 --> 00:15:06.760 align:start position:0% very scalable execution off chain you can<00:15:04.010> put<00:15:04.760> put<00:15:05.030> a<00:15:05.060> well<00:15:05.630> not<00:15:05.870> anything<00:15:06.230> but<00:15:06.560> but 00:15:06.760 --> 00:15:06.770 align:start position:0% can put put a well not anything but but 00:15:06.770 --> 00:15:09.570 align:start position:0% can put put a well not anything but but definitely<00:15:07.310> much<00:15:07.490> more<00:15:07.520> much<00:15:08.210> more<00:15:08.420> intensive 00:15:09.570 --> 00:15:09.580 align:start position:0% definitely much more much more intensive 00:15:09.580 --> 00:15:13.450 align:start position:0% definitely much more much more intensive computations<00:15:10.580> into<00:15:10.850> SGX<00:15:11.330> and<00:15:12.070> very<00:15:13.070> possibly 00:15:13.450 --> 00:15:13.460 align:start position:0% computations into SGX and very possibly 00:15:13.460 --> 00:15:15.430 align:start position:0% computations into SGX and very possibly things<00:15:13.700> you<00:15:13.850> would<00:15:14.300> never<00:15:14.450> want<00:15:14.720> to<00:15:14.870> be<00:15:15.050> public 00:15:15.430 --> 00:15:15.440 align:start position:0% things you would never want to be public 00:15:15.440 --> 00:15:16.690 align:start position:0% things you would never want to be public of<00:15:15.560> and<00:15:15.710> under<00:15:15.890> certain<00:15:16.100> conditions<00:15:16.610> of 00:15:16.690 --> 00:15:16.700 align:start position:0% of and under certain conditions of 00:15:16.700 --> 00:15:19.990 align:start position:0% of and under certain conditions of encryption<00:15:17.000> or<00:15:17.210> other<00:15:17.360> things<00:15:18.790> due<00:15:19.790> to<00:15:19.910> the 00:15:19.990 --> 00:15:20.000 align:start position:0% encryption or other things due to the 00:15:20.000 --> 00:15:21.550 align:start position:0% encryption or other things due to the privacy<00:15:20.510> of<00:15:20.780> SGX 00:15:21.550 --> 00:15:21.560 align:start position:0% privacy of SGX 00:15:21.560 --> 00:15:24.340 align:start position:0% privacy of SGX you<00:15:21.920> can<00:15:22.130> basically<00:15:22.310> acquire<00:15:23.020> some<00:15:24.020> amount<00:15:24.260> of 00:15:24.340 --> 00:15:24.350 align:start position:0% you can basically acquire some amount of 00:15:24.350 --> 00:15:25.900 align:start position:0% you can basically acquire some amount of surety<00:15:24.710> that's<00:15:25.010> the<00:15:25.130> node<00:15:25.280> operator<00:15:25.700> that 00:15:25.900 --> 00:15:25.910 align:start position:0% surety that's the node operator that 00:15:25.910 --> 00:15:29.410 align:start position:0% surety that's the node operator that you've<00:15:26.060> given<00:15:26.420> the<00:15:26.690> code<00:15:26.870> to<00:15:27.400> hasn't<00:15:28.420> hasn't 00:15:29.410 --> 00:15:29.420 align:start position:0% you've given the code to hasn't hasn't 00:15:29.420 --> 00:15:34.120 align:start position:0% you've given the code to hasn't hasn't acquired<00:15:29.780> it<00:15:31.180> and<00:15:32.320> you<00:15:33.320> can<00:15:33.470> also<00:15:33.650> do<00:15:33.890> very 00:15:34.120 --> 00:15:34.130 align:start position:0% acquired it and you can also do very 00:15:34.130 --> 00:15:36.249 align:start position:0% acquired it and you can also do very interesting<00:15:34.160> things<00:15:34.610> such<00:15:35.360> as<00:15:35.390> have<00:15:35.840> smart 00:15:36.249 --> 00:15:36.259 align:start position:0% interesting things such as have smart 00:15:36.259 --> 00:15:39.489 align:start position:0% interesting things such as have smart contract<00:15:36.649> control<00:15:37.100> private<00:15:37.459> keys<00:15:37.809> so<00:15:38.809> how<00:15:39.439> we 00:15:39.489 --> 00:15:39.499 align:start position:0% contract control private keys so how we 00:15:39.499 --> 00:15:41.129 align:start position:0% contract control private keys so how we think<00:15:39.829> this<00:15:40.009> is<00:15:40.069> going<00:15:40.339> to<00:15:40.429> evolve<00:15:40.699> is<00:15:40.939> that 00:15:41.129 --> 00:15:41.139 align:start position:0% think this is going to evolve is that 00:15:41.139 --> 00:15:44.019 align:start position:0% think this is going to evolve is that you're<00:15:42.139> going<00:15:42.319> to<00:15:42.350> write<00:15:42.619> one<00:15:42.919> big<00:15:43.369> one<00:15:43.699> smart 00:15:44.019 --> 00:15:44.029 align:start position:0% you're going to write one big one smart 00:15:44.029 --> 00:15:46.900 align:start position:0% you're going to write one big one smart contract<00:15:44.509> in<00:15:45.290> in<00:15:45.829> two<00:15:46.009> parts<00:15:46.339> right<00:15:46.519> you're 00:15:46.900 --> 00:15:46.910 align:start position:0% contract in in two parts right you're 00:15:46.910 --> 00:15:48.789 align:start position:0% contract in in two parts right you're gonna<00:15:47.029> have<00:15:47.119> an<00:15:47.299> off<00:15:47.449> chain<00:15:47.749> part<00:15:48.019> both<00:15:48.619> of 00:15:48.789 --> 00:15:48.799 align:start position:0% gonna have an off chain part both of 00:15:48.799 --> 00:15:49.960 align:start position:0% gonna have an off chain part both of them<00:15:48.889> written<00:15:48.979> so<00:15:49.279> that<00:15:49.399> you<00:15:49.549> can<00:15:49.699> have<00:15:49.790> an<00:15:49.879> off 00:15:49.960 --> 00:15:49.970 align:start position:0% them written so that you can have an off 00:15:49.970 --> 00:15:52.210 align:start position:0% them written so that you can have an off chain<00:15:50.209> part<00:15:50.479> the<00:15:51.049> off<00:15:51.169> chain<00:15:51.439> part<00:15:51.709> is<00:15:51.919> gonna 00:15:52.210 --> 00:15:52.220 align:start position:0% chain part the off chain part is gonna 00:15:52.220 --> 00:15:54.460 align:start position:0% chain part the off chain part is gonna is<00:15:52.519> gonna<00:15:53.239> make<00:15:53.389> all<00:15:53.660> kinds<00:15:53.959> of<00:15:54.019> all<00:15:54.199> chain 00:15:54.460 --> 00:15:54.470 align:start position:0% is gonna make all kinds of all chain 00:15:54.470 --> 00:15:57.519 align:start position:0% is gonna make all kinds of all chain requests<00:15:55.309> that<00:15:55.609> look<00:15:56.059> like<00:15:56.179> this<00:15:56.419> and<00:15:56.689> require 00:15:57.519 --> 00:15:57.529 align:start position:0% requests that look like this and require 00:15:57.529 --> 00:15:59.949 align:start position:0% requests that look like this and require all<00:15:57.799> kinds<00:15:58.369> of<00:15:58.429> computations 00:15:59.949 --> 00:15:59.959 align:start position:0% all kinds of computations 00:15:59.959 --> 00:16:02.349 align:start position:0% all kinds of computations you're<00:16:00.229> gonna<00:16:00.350> write<00:16:00.589> it<00:16:00.739> in<00:16:01.179> solidity<00:16:02.179> or 00:16:02.349 --> 00:16:02.359 align:start position:0% you're gonna write it in solidity or 00:16:02.359 --> 00:16:03.759 align:start position:0% you're gonna write it in solidity or whatever<00:16:02.809> language<00:16:03.139> you'd<00:16:03.289> like<00:16:03.439> that<00:16:03.470> goes 00:16:03.759 --> 00:16:03.769 align:start position:0% whatever language you'd like that goes 00:16:03.769 --> 00:16:05.889 align:start position:0% whatever language you'd like that goes down<00:16:03.949> to<00:16:04.009> the<00:16:04.160> VM<00:16:04.399> bytecode<00:16:04.850> you're<00:16:05.569> going<00:16:05.749> to 00:16:05.889 --> 00:16:05.899 align:start position:0% down to the VM bytecode you're going to 00:16:05.899 --> 00:16:11.759 align:start position:0% down to the VM bytecode you're going to run<00:16:06.049> it<00:16:06.199> into<00:16:06.589> and<00:16:06.919> and<00:16:07.579> an<00:16:08.949> SGX<00:16:09.949> Enclave<00:16:10.459> and 00:16:11.759 --> 00:16:11.769 align:start position:0% run it into and and an SGX Enclave and 00:16:11.769 --> 00:16:14.049 align:start position:0% run it into and and an SGX Enclave and then<00:16:12.769> that<00:16:12.949> as<00:16:13.069> G<00:16:13.249> ox<00:16:13.369> Enclave<00:16:13.759> will<00:16:13.939> have 00:16:14.049 --> 00:16:14.059 align:start position:0% then that as G ox Enclave will have 00:16:14.059 --> 00:16:16.329 align:start position:0% then that as G ox Enclave will have capabilities<00:16:14.779> such<00:16:15.589> as<00:16:15.739> the<00:16:15.859> control<00:16:16.100> of<00:16:16.220> a 00:16:16.329 --> 00:16:16.339 align:start position:0% capabilities such as the control of a 00:16:16.339 --> 00:16:19.960 align:start position:0% capabilities such as the control of a private<00:16:16.729> key<00:16:17.319> or<00:16:18.319> the<00:16:18.679> ability<00:16:19.069> for<00:16:19.309> the<00:16:19.519> SGX 00:16:19.960 --> 00:16:19.970 align:start position:0% private key or the ability for the SGX 00:16:19.970 --> 00:16:22.869 align:start position:0% private key or the ability for the SGX Enclave<00:16:20.419> to<00:16:21.079> make<00:16:21.229> a<00:16:21.259> direct<00:16:21.679> request<00:16:21.889> to<00:16:22.850> a 00:16:22.869 --> 00:16:22.879 align:start position:0% Enclave to make a direct request to a 00:16:22.879 --> 00:16:25.119 align:start position:0% Enclave to make a direct request to a native<00:16:23.209> OS<00:16:23.329> library<00:16:24.049> for<00:16:24.709> something<00:16:25.009> as 00:16:25.119 --> 00:16:25.129 align:start position:0% native OS library for something as 00:16:25.129 --> 00:16:30.159 align:start position:0% native OS library for something as useful<00:16:25.309> as<00:16:25.579> randomness<00:16:26.119> right<00:16:26.839> so<00:16:28.329> the<00:16:29.329> the 00:16:30.159 --> 00:16:30.169 align:start position:0% useful as randomness right so the the 00:16:30.169 --> 00:16:31.689 align:start position:0% useful as randomness right so the the thinking<00:16:30.499> here<00:16:30.709> is<00:16:30.859> that<00:16:31.039> you<00:16:31.249> you<00:16:31.459> don't 00:16:31.689 --> 00:16:31.699 align:start position:0% thinking here is that you you don't 00:16:31.699 --> 00:16:34.900 align:start position:0% thinking here is that you you don't learn<00:16:31.970> a<00:16:32.329> new<00:16:33.319> language<00:16:33.709> for<00:16:34.339> Oracle's<00:16:34.759> or 00:16:34.900 --> 00:16:34.910 align:start position:0% learn a new language for Oracle's or 00:16:34.910 --> 00:16:37.210 align:start position:0% learn a new language for Oracle's or anything<00:16:35.059> super<00:16:35.539> specific<00:16:35.749> you<00:16:36.559> you<00:16:36.859> continue 00:16:37.210 --> 00:16:37.220 align:start position:0% anything super specific you you continue 00:16:37.220 --> 00:16:38.439 align:start position:0% anything super specific you you continue writing<00:16:37.519> in<00:16:37.759> the<00:16:37.850> language<00:16:38.149> that<00:16:38.299> you're 00:16:38.439 --> 00:16:38.449 align:start position:0% writing in the language that you're 00:16:38.449 --> 00:16:40.449 align:start position:0% writing in the language that you're writing<00:16:38.629> your<00:16:38.809> contract<00:16:39.289> in<00:16:39.470> but<00:16:40.100> you<00:16:40.189> have<00:16:40.220> an 00:16:40.449 --> 00:16:40.459 align:start position:0% writing your contract in but you have an 00:16:40.459 --> 00:16:42.939 align:start position:0% writing your contract in but you have an off<00:16:40.639> chain<00:16:40.970> portion<00:16:41.480> the<00:16:42.109> off<00:16:42.199> chain<00:16:42.470> portion 00:16:42.939 --> 00:16:42.949 align:start position:0% off chain portion the off chain portion 00:16:42.949 --> 00:16:45.489 align:start position:0% off chain portion the off chain portion relates<00:16:43.669> to<00:16:43.910> your<00:16:44.179> acquisition<00:16:44.509> of<00:16:44.809> data<00:16:44.989> and 00:16:45.489 --> 00:16:45.499 align:start position:0% relates to your acquisition of data and 00:16:45.499 --> 00:16:47.970 align:start position:0% relates to your acquisition of data and your<00:16:46.220> computation<00:16:46.970> around<00:16:47.209> that<00:16:47.359> data<00:16:47.569> and 00:16:47.970 --> 00:16:47.980 align:start position:0% your computation around that data and 00:16:47.980 --> 00:16:50.169 align:start position:0% your computation around that data and then<00:16:48.980> the<00:16:49.069> on<00:16:49.189> chain<00:16:49.459> portion<00:16:49.819> is<00:16:49.939> what<00:16:50.059> you 00:16:50.169 --> 00:16:50.179 align:start position:0% then the on chain portion is what you 00:16:50.179 --> 00:16:51.699 align:start position:0% then the on chain portion is what you have<00:16:50.299> on<00:16:50.480> chain<00:16:50.720> that<00:16:51.259> is<00:16:51.410> presumably 00:16:51.699 --> 00:16:51.709 align:start position:0% have on chain that is presumably 00:16:51.709 --> 00:16:54.699 align:start position:0% have on chain that is presumably triggered<00:16:52.339> by<00:16:52.789> that<00:16:52.970> on<00:16:53.119> chain<00:16:53.389> data<00:16:53.629> but<00:16:54.499> by 00:16:54.699 --> 00:16:54.709 align:start position:0% triggered by that on chain data but by 00:16:54.709 --> 00:16:56.499 align:start position:0% triggered by that on chain data but by the<00:16:54.769> off<00:16:54.980> chain<00:16:55.189> data<00:16:55.309> that<00:16:55.519> that<00:16:56.029> reaches<00:16:56.359> it 00:16:56.499 --> 00:16:56.509 align:start position:0% the off chain data that that reaches it 00:16:56.509 --> 00:16:59.049 align:start position:0% the off chain data that that reaches it and<00:16:56.779> then<00:16:57.739> presumably<00:16:58.519> you<00:16:58.639> have<00:16:58.789> another 00:16:59.049 --> 00:16:59.059 align:start position:0% and then presumably you have another 00:16:59.059 --> 00:17:00.699 align:start position:0% and then presumably you have another section<00:16:59.509> to<00:16:59.779> the<00:16:59.869> contract<00:17:00.319> where<00:17:00.499> you<00:17:00.559> have 00:17:00.699 --> 00:17:00.709 align:start position:0% section to the contract where you have 00:17:00.709 --> 00:17:02.499 align:start position:0% section to the contract where you have off<00:17:00.859> chain<00:17:01.129> payments<00:17:01.609> where<00:17:02.119> you<00:17:02.239> want<00:17:02.419> the 00:17:02.499 --> 00:17:02.509 align:start position:0% off chain payments where you want the 00:17:02.509 --> 00:17:04.689 align:start position:0% off chain payments where you want the contract<00:17:02.869> to<00:17:03.230> send<00:17:03.559> some<00:17:04.189> kind<00:17:04.370> of<00:17:04.459> payment 00:17:04.689 --> 00:17:04.699 align:start position:0% contract to send some kind of payment 00:17:04.699 --> 00:17:07.929 align:start position:0% contract to send some kind of payment message<00:17:05.799> to<00:17:06.799> a<00:17:06.829> payment<00:17:07.220> network<00:17:07.519> or<00:17:07.639> a<00:17:07.699> bank 00:17:07.929 --> 00:17:07.939 align:start position:0% message to a payment network or a bank 00:17:07.939 --> 00:17:09.850 align:start position:0% message to a payment network or a bank or<00:17:08.089> or<00:17:08.269> any<00:17:08.419> other<00:17:08.569> system<00:17:08.809> that<00:17:09.409> has<00:17:09.589> their 00:17:09.850 --> 00:17:09.860 align:start position:0% or or any other system that has their 00:17:09.860 --> 00:17:11.619 align:start position:0% or or any other system that has their own<00:17:09.919> blockchain<00:17:10.429> middleware<00:17:10.819> that 00:17:11.619 --> 00:17:11.629 align:start position:0% own blockchain middleware that 00:17:11.629 --> 00:17:15.159 align:start position:0% own blockchain middleware that represents<00:17:12.230> their<00:17:12.409> services<00:17:12.949> right<00:17:13.699> and<00:17:14.169> then 00:17:15.159 --> 00:17:15.169 align:start position:0% represents their services right and then 00:17:15.169 --> 00:17:18.369 align:start position:0% represents their services right and then also<00:17:15.470> if<00:17:15.829> if<00:17:16.069> you<00:17:16.339> want<00:17:16.659> if<00:17:17.659> you<00:17:17.870> want<00:17:18.049> key 00:17:18.369 --> 00:17:18.379 align:start position:0% also if if you want if you want key 00:17:18.379 --> 00:17:21.250 align:start position:0% also if if you want if you want key resources<00:17:19.010> such<00:17:19.789> as<00:17:19.819> randomness<00:17:20.539> or<00:17:21.019> any 00:17:21.250 --> 00:17:21.260 align:start position:0% resources such as randomness or any 00:17:21.260 --> 00:17:23.289 align:start position:0% resources such as randomness or any other<00:17:21.470> number<00:17:22.189> of<00:17:22.279> resources<00:17:22.639> that<00:17:22.939> can<00:17:23.149> be 00:17:23.289 --> 00:17:23.299 align:start position:0% other number of resources that can be 00:17:23.299 --> 00:17:25.689 align:start position:0% other number of resources that can be provided<00:17:23.629> from<00:17:23.929> a<00:17:24.049> native<00:17:24.379> OS<00:17:24.500> library<00:17:25.129> that's 00:17:25.689 --> 00:17:25.699 align:start position:0% provided from a native OS library that's 00:17:25.699 --> 00:17:27.909 align:start position:0% provided from a native OS library that's been<00:17:25.850> widely<00:17:26.059> used<00:17:26.389> and<00:17:26.539> tested<00:17:26.740> you<00:17:27.740> can 00:17:27.909 --> 00:17:27.919 align:start position:0% been widely used and tested you can 00:17:27.919 --> 00:17:30.549 align:start position:0% been widely used and tested you can acquire<00:17:28.220> it<00:17:28.519> by<00:17:29.090> directly<00:17:29.840> messaging<00:17:30.379> within 00:17:30.549 --> 00:17:30.559 align:start position:0% acquire it by directly messaging within 00:17:30.559 --> 00:17:32.950 align:start position:0% acquire it by directly messaging within the<00:17:30.769> Enclave<00:17:31.190> so<00:17:32.120> there's<00:17:32.360> there's<00:17:32.629> entire 00:17:32.950 --> 00:17:32.960 align:start position:0% the Enclave so there's there's entire 00:17:32.960 --> 00:17:35.649 align:start position:0% the Enclave so there's there's entire subsets<00:17:33.620> of<00:17:33.879> of<00:17:34.879> what<00:17:35.090> you're<00:17:35.240> all<00:17:35.360> chained 00:17:35.649 --> 00:17:35.659 align:start position:0% subsets of of what you're all chained 00:17:35.659 --> 00:17:38.500 align:start position:0% subsets of of what you're all chained computation<00:17:36.350> can<00:17:36.500> have<00:17:36.789> within<00:17:37.789> the<00:17:38.059> Enclave 00:17:38.500 --> 00:17:38.510 align:start position:0% computation can have within the Enclave 00:17:38.510 --> 00:17:41.169 align:start position:0% computation can have within the Enclave by<00:17:39.289> having<00:17:39.649> it<00:17:39.830> message<00:17:40.340> something<00:17:40.940> like<00:17:41.149> a 00:17:41.169 --> 00:17:41.179 align:start position:0% by having it message something like a 00:17:41.179 --> 00:17:43.409 align:start position:0% by having it message something like a native<00:17:41.539> OS<00:17:41.659> library<00:17:42.200> from<00:17:42.379> randomness 00:17:43.409 --> 00:17:43.419 align:start position:0% native OS library from randomness 00:17:43.419 --> 00:17:45.580 align:start position:0% native OS library from randomness eliminating<00:17:44.419> certain<00:17:44.600> scenarios<00:17:45.379> where<00:17:45.559> you 00:17:45.580 --> 00:17:45.590 align:start position:0% eliminating certain scenarios where you 00:17:45.590 --> 00:17:47.200 align:start position:0% eliminating certain scenarios where you would<00:17:45.769> ever<00:17:45.889> need<00:17:46.100> to<00:17:46.220> use<00:17:46.370> a<00:17:46.399> service<00:17:46.669> and<00:17:47.029> you 00:17:47.200 --> 00:17:47.210 align:start position:0% would ever need to use a service and you 00:17:47.210 --> 00:17:48.850 align:start position:0% would ever need to use a service and you you<00:17:47.809> kind<00:17:48.019> of<00:17:48.080> get<00:17:48.289> the<00:17:48.379> tamper<00:17:48.710> proof 00:17:48.850 --> 00:17:48.860 align:start position:0% you kind of get the tamper proof 00:17:48.860 --> 00:17:49.940 align:start position:0% you kind of get the tamper proof guarantees<00:17:49.370> both 00:17:49.940 --> 00:17:49.950 align:start position:0% guarantees both 00:17:49.950 --> 00:17:52.490 align:start position:0% guarantees both on<00:17:50.040> the<00:17:50.850> level<00:17:51.000> of<00:17:51.240> the<00:17:51.390> data<00:17:51.540> acquisition<00:17:52.170> and 00:17:52.490 --> 00:17:52.500 align:start position:0% on the level of the data acquisition and 00:17:52.500 --> 00:17:54.140 align:start position:0% on the level of the data acquisition and also<00:17:53.010> on<00:17:53.130> the<00:17:53.250> level<00:17:53.400> of<00:17:53.580> this<00:17:53.760> native<00:17:54.060> OS 00:17:54.140 --> 00:17:54.150 align:start position:0% also on the level of this native OS 00:17:54.150 --> 00:17:56.690 align:start position:0% also on the level of this native OS library<00:17:54.720> once<00:17:55.530> again<00:17:55.770> also<00:17:55.950> very<00:17:56.280> possibly 00:17:56.690 --> 00:17:56.700 align:start position:0% library once again also very possibly 00:17:56.700 --> 00:17:59.180 align:start position:0% library once again also very possibly run<00:17:56.970> in<00:17:57.090> multiple<00:17:57.660> nodes<00:17:57.870> and<00:17:58.170> those<00:17:58.890> nodes 00:17:59.180 --> 00:17:59.190 align:start position:0% run in multiple nodes and those nodes 00:17:59.190 --> 00:18:01.130 align:start position:0% run in multiple nodes and those nodes being<00:17:59.730> able<00:17:59.910> to<00:18:00.090> come<00:18:00.330> to<00:18:00.360> the<00:18:00.660> centralized 00:18:01.130 --> 00:18:01.140 align:start position:0% being able to come to the centralized 00:18:01.140 --> 00:18:07.150 align:start position:0% being able to come to the centralized consensus<00:18:01.830> about<00:18:03.170> about<00:18:04.170> the<00:18:05.300> execution<00:18:06.300> of 00:18:07.150 --> 00:18:07.160 align:start position:0% consensus about about the execution of 00:18:07.160 --> 00:18:09.830 align:start position:0% consensus about about the execution of of<00:18:08.160> that<00:18:08.340> computation<00:18:08.670> and<00:18:09.210> even<00:18:09.750> the 00:18:09.830 --> 00:18:09.840 align:start position:0% of that computation and even the 00:18:09.840 --> 00:18:13.130 align:start position:0% of that computation and even the acquisition<00:18:10.290> of<00:18:10.350> randomness<00:18:11.180> now<00:18:12.180> the<00:18:12.750> the 00:18:13.130 --> 00:18:13.140 align:start position:0% acquisition of randomness now the the 00:18:13.140 --> 00:18:15.470 align:start position:0% acquisition of randomness now the the reason<00:18:13.470> we're<00:18:13.680> we're<00:18:14.490> kind<00:18:14.670> of<00:18:14.730> applying<00:18:15.120> this 00:18:15.470 --> 00:18:15.480 align:start position:0% reason we're we're kind of applying this 00:18:15.480 --> 00:18:17.570 align:start position:0% reason we're we're kind of applying this level<00:18:15.840> of<00:18:15.930> stringent<00:18:16.440> security<00:18:16.620> and<00:18:17.190> tamper 00:18:17.570 --> 00:18:17.580 align:start position:0% level of stringent security and tamper 00:18:17.580 --> 00:18:22.400 align:start position:0% level of stringent security and tamper proof<00:18:17.790> Ness<00:18:18.030> is<00:18:18.240> that<00:18:20.660> the<00:18:21.660> world<00:18:21.900> we'd<00:18:22.170> like 00:18:22.400 --> 00:18:22.410 align:start position:0% proof Ness is that the world we'd like 00:18:22.410 --> 00:18:25.570 align:start position:0% proof Ness is that the world we'd like to<00:18:22.590> be<00:18:22.770> in<00:18:22.920> in<00:18:23.250> a<00:18:23.970> year<00:18:24.570> or<00:18:24.930> two<00:18:25.080> years 00:18:25.570 --> 00:18:25.580 align:start position:0% to be in in a year or two years 00:18:25.580 --> 00:18:29.060 align:start position:0% to be in in a year or two years relatively<00:18:26.580> soon<00:18:26.820> is<00:18:27.000> is<00:18:27.750> the<00:18:28.200> ability<00:18:28.500> for<00:18:28.890> a 00:18:29.060 --> 00:18:29.070 align:start position:0% relatively soon is is the ability for a 00:18:29.070 --> 00:18:31.250 align:start position:0% relatively soon is is the ability for a contract<00:18:29.640> to<00:18:30.240> reach<00:18:30.450> out<00:18:30.720> to<00:18:30.750> another 00:18:31.250 --> 00:18:31.260 align:start position:0% contract to reach out to another 00:18:31.260 --> 00:18:33.800 align:start position:0% contract to reach out to another contract<00:18:31.800> on<00:18:31.980> chain<00:18:32.310> and<00:18:32.580> for<00:18:33.180> that<00:18:33.270> Unchained 00:18:33.800 --> 00:18:33.810 align:start position:0% contract on chain and for that Unchained 00:18:33.810 --> 00:18:36.860 align:start position:0% contract on chain and for that Unchained contract<00:18:34.350> to<00:18:34.920> represent<00:18:35.700> an<00:18:36.030> off<00:18:36.600> chain 00:18:36.860 --> 00:18:36.870 align:start position:0% contract to represent an off chain 00:18:36.870 --> 00:18:39.470 align:start position:0% contract to represent an off chain resource<00:18:37.640> so<00:18:38.640> that<00:18:38.670> a<00:18:39.000> smart<00:18:39.330> contract 00:18:39.470 --> 00:18:39.480 align:start position:0% resource so that a smart contract 00:18:39.480 --> 00:18:42.010 align:start position:0% resource so that a smart contract developer<00:18:40.170> no<00:18:40.290> longer<00:18:40.620> needs<00:18:40.860> to<00:18:41.070> learn<00:18:41.220> api's 00:18:42.010 --> 00:18:42.020 align:start position:0% developer no longer needs to learn api's 00:18:42.020 --> 00:18:45.830 align:start position:0% developer no longer needs to learn api's they<00:18:43.020> have<00:18:43.500> an<00:18:43.920> entire<00:18:44.370> list<00:18:44.700> of<00:18:44.940> contracts<00:18:45.630> on 00:18:45.830 --> 00:18:45.840 align:start position:0% they have an entire list of contracts on 00:18:45.840 --> 00:18:48.320 align:start position:0% they have an entire list of contracts on chain<00:18:46.230> which<00:18:47.130> we<00:18:47.250> call<00:18:47.400> chain<00:18:47.640> links<00:18:47.940> but<00:18:48.150> you 00:18:48.320 --> 00:18:48.330 align:start position:0% chain which we call chain links but you 00:18:48.330 --> 00:18:50.780 align:start position:0% chain which we call chain links but you know<00:18:48.450> are<00:18:48.960> basically<00:18:49.290> Oracle's<00:18:49.790> that 00:18:50.780 --> 00:18:50.790 align:start position:0% know are basically Oracle's that 00:18:50.790 --> 00:18:54.800 align:start position:0% know are basically Oracle's that represent<00:18:51.720> every<00:18:52.650> type<00:18:53.490> of<00:18:53.640> data<00:18:53.910> of<00:18:54.300> chain 00:18:54.800 --> 00:18:54.810 align:start position:0% represent every type of data of chain 00:18:54.810 --> 00:18:58.070 align:start position:0% represent every type of data of chain payment<00:18:55.260> mechanism<00:18:55.970> is<00:18:56.970> signature<00:18:57.510> basically 00:18:58.070 --> 00:18:58.080 align:start position:0% payment mechanism is signature basically 00:18:58.080 --> 00:19:00.620 align:start position:0% payment mechanism is signature basically any<00:18:58.260> any<00:18:58.710> web<00:18:59.160> service<00:18:59.460> that<00:18:59.850> a<00:18:59.880> web<00:19:00.090> developer 00:19:00.620 --> 00:19:00.630 align:start position:0% any any web service that a web developer 00:19:00.630 --> 00:19:01.940 align:start position:0% any any web service that a web developer gets<00:19:00.840> access<00:19:01.290> to<00:19:01.320> to<00:19:01.620> build<00:19:01.830> their 00:19:01.940 --> 00:19:01.950 align:start position:0% gets access to to build their 00:19:01.950 --> 00:19:04.070 align:start position:0% gets access to to build their application<00:19:02.580> is<00:19:03.030> a<00:19:03.120> service<00:19:03.630> that<00:19:03.660> a<00:19:03.810> smart 00:19:04.070 --> 00:19:04.080 align:start position:0% application is a service that a smart 00:19:04.080 --> 00:19:06.350 align:start position:0% application is a service that a smart contract<00:19:04.320> developer<00:19:05.130> should<00:19:05.700> be<00:19:05.880> able<00:19:05.970> to<00:19:06.240> get 00:19:06.350 --> 00:19:06.360 align:start position:0% contract developer should be able to get 00:19:06.360 --> 00:19:09.040 align:start position:0% contract developer should be able to get access<00:19:06.510> to<00:19:06.810> from<00:19:07.530> a<00:19:07.590> contract<00:19:08.070> on<00:19:08.250> chain<00:19:08.580> and 00:19:09.040 --> 00:19:09.050 align:start position:0% access to from a contract on chain and 00:19:09.050 --> 00:19:12.280 align:start position:0% access to from a contract on chain and and<00:19:10.050> that's<00:19:10.410> the<00:19:10.770> that's<00:19:11.460> the<00:19:11.610> quick 00:19:12.280 --> 00:19:12.290 align:start position:0% and that's the that's the quick 00:19:12.290 --> 00:19:15.050 align:start position:0% and that's the that's the quick prototyping<00:19:13.290> world<00:19:13.530> we<00:19:13.770> want<00:19:14.010> to<00:19:14.100> be<00:19:14.250> in<00:19:14.400> for 00:19:15.050 --> 00:19:15.060 align:start position:0% prototyping world we want to be in for 00:19:15.060 --> 00:19:17.000 align:start position:0% prototyping world we want to be in for people<00:19:15.390> to<00:19:15.510> build<00:19:15.720> killer<00:19:16.080> applications<00:19:16.770> of 00:19:17.000 --> 00:19:17.010 align:start position:0% people to build killer applications of 00:19:17.010 --> 00:19:19.340 align:start position:0% people to build killer applications of smart<00:19:17.550> contracts<00:19:18.180> by<00:19:18.630> focusing<00:19:19.110> on<00:19:19.230> their 00:19:19.340 --> 00:19:19.350 align:start position:0% smart contracts by focusing on their 00:19:19.350 --> 00:19:21.200 align:start position:0% smart contracts by focusing on their core<00:19:19.530> application<00:19:20.130> and<00:19:20.340> getting<00:19:21.000> all<00:19:21.090> the 00:19:21.200 --> 00:19:21.210 align:start position:0% core application and getting all the 00:19:21.210 --> 00:19:23.090 align:start position:0% core application and getting all the inputs<00:19:21.570> and<00:19:21.660> outputs<00:19:21.720> they<00:19:22.140> need<00:19:22.350> while 00:19:23.090 --> 00:19:23.100 align:start position:0% inputs and outputs they need while 00:19:23.100 --> 00:19:24.800 align:start position:0% inputs and outputs they need while making<00:19:23.430> sure<00:19:23.790> that<00:19:23.970> those<00:19:24.150> inputs<00:19:24.660> and 00:19:24.800 --> 00:19:24.810 align:start position:0% making sure that those inputs and 00:19:24.810 --> 00:19:27.980 align:start position:0% making sure that those inputs and outputs<00:19:25.200> are<00:19:25.650> sufficiently<00:19:26.340> secure<00:19:26.990> that 00:19:27.980 --> 00:19:27.990 align:start position:0% outputs are sufficiently secure that 00:19:27.990 --> 00:19:30.740 align:start position:0% outputs are sufficiently secure that their<00:19:28.890> end-users<00:19:29.520> the<00:19:30.000> other<00:19:30.150> parties<00:19:30.540> in<00:19:30.660> the 00:19:30.740 --> 00:19:30.750 align:start position:0% their end-users the other parties in the 00:19:30.750 --> 00:19:33.920 align:start position:0% their end-users the other parties in the agreement<00:19:31.230> trust<00:19:31.950> that<00:19:32.760> the<00:19:33.030> source<00:19:33.660> of<00:19:33.840> the 00:19:33.920 --> 00:19:33.930 align:start position:0% agreement trust that the source of the 00:19:33.930 --> 00:19:35.960 align:start position:0% agreement trust that the source of the inputs<00:19:34.260> the<00:19:34.470> method<00:19:34.770> of<00:19:34.860> input<00:19:35.220> the<00:19:35.520> contract 00:19:35.960 --> 00:19:35.970 align:start position:0% inputs the method of input the contract 00:19:35.970 --> 00:19:38.960 align:start position:0% inputs the method of input the contract itself<00:19:36.300> the<00:19:37.050> method<00:19:37.350> of<00:19:37.380> the<00:19:37.530> output<00:19:37.950> is<00:19:38.160> is 00:19:38.960 --> 00:19:38.970 align:start position:0% itself the method of the output is is 00:19:38.970 --> 00:19:41.900 align:start position:0% itself the method of the output is is sufficiently<00:19:39.690> secure<00:19:40.280> to<00:19:41.280> trust<00:19:41.670> that 00:19:41.900 --> 00:19:41.910 align:start position:0% sufficiently secure to trust that 00:19:41.910 --> 00:19:44.900 align:start position:0% sufficiently secure to trust that end-to-end<00:19:42.480> setup<00:19:42.990> right<00:19:43.560> the<00:19:44.130> the<00:19:44.610> world<00:19:44.790> we 00:19:44.900 --> 00:19:44.910 align:start position:0% end-to-end setup right the the world we 00:19:44.910 --> 00:19:46.640 align:start position:0% end-to-end setup right the the world we want<00:19:45.060> to<00:19:45.150> avoid<00:19:45.420> is<00:19:45.720> one<00:19:46.320> where<00:19:46.440> you<00:19:46.500> have<00:19:46.620> a 00:19:46.640 --> 00:19:46.650 align:start position:0% want to avoid is one where you have a 00:19:46.650 --> 00:19:49.100 align:start position:0% want to avoid is one where you have a highly<00:19:47.130> secure<00:19:47.520> decentralized<00:19:48.210> computation 00:19:49.100 --> 00:19:49.110 align:start position:0% highly secure decentralized computation 00:19:49.110 --> 00:19:51.350 align:start position:0% highly secure decentralized computation that<00:19:49.320> is<00:19:50.280> then<00:19:50.460> triggered<00:19:50.820> by<00:19:51.000> highly 00:19:51.350 --> 00:19:51.360 align:start position:0% that is then triggered by highly 00:19:51.360 --> 00:19:54.890 align:start position:0% that is then triggered by highly insecure<00:19:51.690> services<00:19:52.410> which<00:19:53.420> once<00:19:54.420> looked<00:19:54.720> at 00:19:54.890 --> 00:19:54.900 align:start position:0% insecure services which once looked at 00:19:54.900 --> 00:19:57.170 align:start position:0% insecure services which once looked at lead<00:19:55.470> people<00:19:55.890> to<00:19:56.010> not<00:19:56.190> put<00:19:56.430> any<00:19:56.610> real<00:19:56.760> value<00:19:56.790> in 00:19:57.170 --> 00:19:57.180 align:start position:0% lead people to not put any real value in 00:19:57.180 --> 00:19:59.120 align:start position:0% lead people to not put any real value in the<00:19:57.270> contract<00:19:57.750> right<00:19:58.410> that's<00:19:58.650> the<00:19:58.830> world<00:19:58.980> we 00:19:59.120 --> 00:19:59.130 align:start position:0% the contract right that's the world we 00:19:59.130 --> 00:20:01.400 align:start position:0% the contract right that's the world we want<00:19:59.310> to<00:19:59.340> get<00:19:59.460> away<00:19:59.550> from<00:19:59.670> and<00:20:00.090> the<00:20:01.020> world<00:20:01.230> of 00:20:01.400 --> 00:20:01.410 align:start position:0% want to get away from and the world of 00:20:01.410 --> 00:20:03.230 align:start position:0% want to get away from and the world of secure<00:20:01.770> end-to-end<00:20:02.100> smart<00:20:02.490> contracts<00:20:03.060> is<00:20:03.150> the 00:20:03.230 --> 00:20:03.240 align:start position:0% secure end-to-end smart contracts is the 00:20:03.240 --> 00:20:03.620 align:start position:0% secure end-to-end smart contracts is the world 00:20:03.620 --> 00:20:03.630 align:start position:0% world 00:20:03.630 --> 00:20:05.960 align:start position:0% world like<00:20:03.750> to<00:20:03.900> approach<00:20:04.310> if<00:20:05.310> you'd<00:20:05.580> like<00:20:05.700> to<00:20:05.880> know 00:20:05.960 --> 00:20:05.970 align:start position:0% like to approach if you'd like to know 00:20:05.970 --> 00:20:08.180 align:start position:0% like to approach if you'd like to know more<00:20:06.210> you<00:20:06.990> can<00:20:07.140> find<00:20:07.350> the<00:20:07.440> technical<00:20:07.830> details 00:20:08.180 --> 00:20:08.190 align:start position:0% more you can find the technical details 00:20:08.190 --> 00:20:11.030 align:start position:0% more you can find the technical details in<00:20:08.370> these<00:20:08.520> two<00:20:08.700> papers<00:20:09.590> and<00:20:10.590> we're<00:20:10.920> always 00:20:11.030 --> 00:20:11.040 align:start position:0% in these two papers and we're always 00:20:11.040 --> 00:20:14.270 align:start position:0% in these two papers and we're always happy<00:20:11.700> to<00:20:11.930> discuss<00:20:12.930> this<00:20:13.140> and<00:20:13.410> we're<00:20:14.160> also 00:20:14.270 --> 00:20:14.280 align:start position:0% happy to discuss this and we're also 00:20:14.280 --> 00:20:16.250 align:start position:0% happy to discuss this and we're also working<00:20:14.970> on<00:20:15.150> this<00:20:15.300> in<00:20:15.420> an<00:20:15.570> open<00:20:15.690> source<00:20:15.930> manner 00:20:16.250 --> 00:20:16.260 align:start position:0% working on this in an open source manner 00:20:16.260 --> 00:20:19.490 align:start position:0% working on this in an open source manner and<00:20:16.500> looking<00:20:17.490> for<00:20:17.760> we're<00:20:18.420> interested<00:20:18.900> folks 00:20:19.490 --> 00:20:19.500 align:start position:0% and looking for we're interested folks 00:20:19.500 --> 00:20:21.620 align:start position:0% and looking for we're interested folks to<00:20:19.650> join<00:20:19.860> us<00:20:20.040> to<00:20:20.640> solve<00:20:20.850> this<00:20:21.000> problem<00:20:21.390> so 00:20:21.620 --> 00:20:21.630 align:start position:0% to join us to solve this problem so 00:20:21.630 --> 00:20:28.270 align:start position:0% to join us to solve this problem so thank<00:20:22.470> you 00:20:28.270 --> 00:20:28.280 align:start position:0% 00:20:28.280 --> 00:20:35.859 align:start position:0% [Music]