WEBVTT Kind: captions Language: en 00:00:04.650 --> 00:00:07.800 align:start position:0% hi<00:00:05.310> everyone<00:00:05.580> thanks<00:00:05.990> thing 00:00:07.800 --> 00:00:07.810 align:start position:0% hi everyone thanks thing 00:00:07.810 --> 00:00:10.470 align:start position:0% hi everyone thanks thing to<00:00:08.140> learn<00:00:08.260> more<00:00:08.320> about<00:00:08.500> Oracle's<00:00:09.460> and<00:00:09.820> how 00:00:10.470 --> 00:00:10.480 align:start position:0% to learn more about Oracle's and how 00:00:10.480 --> 00:00:13.560 align:start position:0% to learn more about Oracle's and how they<00:00:10.690> fit<00:00:10.900> into<00:00:11.020> smart<00:00:11.380> contracts<00:00:12.010> and<00:00:12.250> and<00:00:13.180> if 00:00:13.560 --> 00:00:13.570 align:start position:0% they fit into smart contracts and and if 00:00:13.570 --> 00:00:16.260 align:start position:0% they fit into smart contracts and and if they're<00:00:13.690> iums<00:00:13.900> overall<00:00:14.230> future<00:00:15.119> so<00:00:16.119> I<00:00:16.150> think 00:00:16.260 --> 00:00:16.270 align:start position:0% they're iums overall future so I think 00:00:16.270 --> 00:00:18.480 align:start position:0% they're iums overall future so I think the<00:00:16.630> the<00:00:16.660> first<00:00:17.200> useful<00:00:17.590> thing<00:00:17.740> is<00:00:17.860> for<00:00:18.189> us<00:00:18.279> to 00:00:18.480 --> 00:00:18.490 align:start position:0% the the first useful thing is for us to 00:00:18.490 --> 00:00:21.210 align:start position:0% the the first useful thing is for us to get<00:00:18.849> some<00:00:19.029> share<00:00:19.240> context<00:00:19.900> and<00:00:20.259> to<00:00:20.439> look<00:00:20.560> look 00:00:21.210 --> 00:00:21.220 align:start position:0% get some share context and to look look 00:00:21.220 --> 00:00:22.859 align:start position:0% get some share context and to look look at<00:00:21.310> the<00:00:21.400> security<00:00:21.849> problem<00:00:22.270> that<00:00:22.750> we're 00:00:22.859 --> 00:00:22.869 align:start position:0% at the security problem that we're 00:00:22.869 --> 00:00:24.330 align:start position:0% at the security problem that we're trying<00:00:23.020> to<00:00:23.110> solve<00:00:23.320> and<00:00:23.740> then<00:00:23.920> look<00:00:24.130> at<00:00:24.220> the 00:00:24.330 --> 00:00:24.340 align:start position:0% trying to solve and then look at the 00:00:24.340 --> 00:00:26.760 align:start position:0% trying to solve and then look at the different<00:00:24.670> ways<00:00:24.820> in<00:00:25.270> which<00:00:25.900> that<00:00:26.230> security 00:00:26.760 --> 00:00:26.770 align:start position:0% different ways in which that security 00:00:26.770 --> 00:00:30.330 align:start position:0% different ways in which that security problem<00:00:27.220> can<00:00:27.550> can<00:00:28.090> be<00:00:28.240> solved<00:00:28.570> effectively<00:00:29.340> so 00:00:30.330 --> 00:00:30.340 align:start position:0% problem can can be solved effectively so 00:00:30.340 --> 00:00:32.820 align:start position:0% problem can can be solved effectively so the<00:00:30.519> nature<00:00:30.789> of<00:00:30.850> the<00:00:31.029> problem<00:00:31.510> is<00:00:31.779> that<00:00:32.260> smart 00:00:32.820 --> 00:00:32.830 align:start position:0% the nature of the problem is that smart 00:00:32.830 --> 00:00:34.860 align:start position:0% the nature of the problem is that smart contracts<00:00:33.519> on<00:00:33.760> great<00:00:34.420> networks<00:00:34.750> like 00:00:34.860 --> 00:00:34.870 align:start position:0% contracts on great networks like 00:00:34.870 --> 00:00:36.869 align:start position:0% contracts on great networks like aetherium<00:00:35.320> can't<00:00:36.010> connect<00:00:36.400> with<00:00:36.550> external 00:00:36.869 --> 00:00:36.879 align:start position:0% aetherium can't connect with external 00:00:36.879 --> 00:00:39.780 align:start position:0% aetherium can't connect with external data<00:00:37.210> this<00:00:38.019> is<00:00:38.260> based<00:00:38.590> on<00:00:38.800> how<00:00:39.430> they<00:00:39.640> reach 00:00:39.780 --> 00:00:39.790 align:start position:0% data this is based on how they reach 00:00:39.790 --> 00:00:42.440 align:start position:0% data this is based on how they reach consensus<00:00:40.360> about<00:00:40.450> transactions<00:00:41.200> how<00:00:42.070> they 00:00:42.440 --> 00:00:42.450 align:start position:0% consensus about transactions how they 00:00:42.450 --> 00:00:46.380 align:start position:0% consensus about transactions how they verify<00:00:43.770> verify<00:00:44.770> the<00:00:45.010> data<00:00:45.280> in<00:00:45.520> in<00:00:45.820> in<00:00:46.090> blocks 00:00:46.380 --> 00:00:46.390 align:start position:0% verify verify the data in in in blocks 00:00:46.390 --> 00:00:48.299 align:start position:0% verify verify the data in in in blocks and<00:00:46.809> it<00:00:47.320> isn't<00:00:47.440> something<00:00:47.860> that's<00:00:48.010> likely<00:00:48.160> to 00:00:48.299 --> 00:00:48.309 align:start position:0% and it isn't something that's likely to 00:00:48.309 --> 00:00:50.549 align:start position:0% and it isn't something that's likely to change<00:00:48.550> it's<00:00:49.090> it's<00:00:49.420> an<00:00:49.540> inherent<00:00:49.930> problem<00:00:50.140> of 00:00:50.549 --> 00:00:50.559 align:start position:0% change it's it's an inherent problem of 00:00:50.559 --> 00:00:53.310 align:start position:0% change it's it's an inherent problem of all<00:00:51.460> decentralized<00:00:52.149> infrastructure<00:00:52.840> that 00:00:53.310 --> 00:00:53.320 align:start position:0% all decentralized infrastructure that 00:00:53.320 --> 00:00:55.500 align:start position:0% all decentralized infrastructure that seeks<00:00:54.100> to<00:00:54.190> package<00:00:54.789> transactions<00:00:55.390> into 00:00:55.500 --> 00:00:55.510 align:start position:0% seeks to package transactions into 00:00:55.510 --> 00:00:57.720 align:start position:0% seeks to package transactions into blocks<00:00:55.809> because<00:00:56.649> the<00:00:56.800> miners<00:00:57.100> set<00:00:57.340> that<00:00:57.610> you 00:00:57.720 --> 00:00:57.730 align:start position:0% blocks because the miners set that you 00:00:57.730 --> 00:00:59.850 align:start position:0% blocks because the miners set that you have<00:00:57.760> doing<00:00:58.180> that<00:00:58.329> you<00:00:59.230> don't<00:00:59.410> want<00:00:59.620> a 00:00:59.850 --> 00:00:59.860 align:start position:0% have doing that you don't want a 00:00:59.860 --> 00:01:01.770 align:start position:0% have doing that you don't want a specific<00:01:00.489> miner<00:01:00.699> responsible<00:01:01.480> you<00:01:01.629> don't 00:01:01.770 --> 00:01:01.780 align:start position:0% specific miner responsible you don't 00:01:01.780 --> 00:01:03.990 align:start position:0% specific miner responsible you don't want<00:01:01.899> him<00:01:01.989> having<00:01:02.140> control<00:01:02.590> over<00:01:02.890> the<00:01:03.579> ability 00:01:03.990 --> 00:01:04.000 align:start position:0% want him having control over the ability 00:01:04.000 --> 00:01:06.420 align:start position:0% want him having control over the ability to<00:01:04.080> you<00:01:05.080> know<00:01:05.110> make<00:01:05.530> your<00:01:05.649> contract<00:01:06.130> trigger 00:01:06.420 --> 00:01:06.430 align:start position:0% to you know make your contract trigger 00:01:06.430 --> 00:01:08.279 align:start position:0% to you know make your contract trigger from<00:01:06.580> data<00:01:06.789> or<00:01:06.940> not<00:01:07.000> trigger<00:01:07.360> and<00:01:07.539> you<00:01:08.140> also 00:01:08.279 --> 00:01:08.289 align:start position:0% from data or not trigger and you also 00:01:08.289 --> 00:01:10.139 align:start position:0% from data or not trigger and you also can't<00:01:08.680> have<00:01:08.800> the<00:01:08.979> entire<00:01:09.190> miners<00:01:09.580> set<00:01:09.759> exposed 00:01:10.139 --> 00:01:10.149 align:start position:0% can't have the entire miners set exposed 00:01:10.149 --> 00:01:12.899 align:start position:0% can't have the entire miners set exposed to<00:01:10.420> various<00:01:10.690> arbitrary<00:01:11.200> API<00:01:11.500> s<00:01:11.640> so<00:01:12.640> this<00:01:12.850> is 00:01:12.899 --> 00:01:12.909 align:start position:0% to various arbitrary API s so this is 00:01:12.909 --> 00:01:14.640 align:start position:0% to various arbitrary API s so this is this<00:01:13.270> is<00:01:13.420> known<00:01:13.600> as<00:01:13.630> the<00:01:13.810> Oracle<00:01:13.990> problem<00:01:14.500> and 00:01:14.640 --> 00:01:14.650 align:start position:0% this is known as the Oracle problem and 00:01:14.650 --> 00:01:17.490 align:start position:0% this is known as the Oracle problem and it's<00:01:14.770> the<00:01:14.890> inability<00:01:15.070> of<00:01:15.630> layer<00:01:16.630> 1<00:01:16.689> systems<00:01:17.320> to 00:01:17.490 --> 00:01:17.500 align:start position:0% it's the inability of layer 1 systems to 00:01:17.500 --> 00:01:20.490 align:start position:0% it's the inability of layer 1 systems to interact<00:01:17.860> with<00:01:17.979> external<00:01:18.159> data<00:01:18.840> now<00:01:19.840> the 00:01:20.490 --> 00:01:20.500 align:start position:0% interact with external data now the 00:01:20.500 --> 00:01:22.640 align:start position:0% interact with external data now the significance<00:01:20.710> of<00:01:21.189> this<00:01:21.340> is<00:01:21.729> is<00:01:21.970> rather<00:01:22.150> large 00:01:22.640 --> 00:01:22.650 align:start position:0% significance of this is is rather large 00:01:22.650 --> 00:01:25.350 align:start position:0% significance of this is is rather large the<00:01:23.650> significance<00:01:24.189> of<00:01:24.400> this<00:01:24.549> is<00:01:24.729> is<00:01:24.970> why<00:01:25.330> we 00:01:25.350 --> 00:01:25.360 align:start position:0% the significance of this is is why we 00:01:25.360 --> 00:01:28.980 align:start position:0% the significance of this is is why we are<00:01:26.080> currently<00:01:27.000> mainly<00:01:28.000> defined<00:01:28.150> as<00:01:28.840> an 00:01:28.980 --> 00:01:28.990 align:start position:0% are currently mainly defined as an 00:01:28.990 --> 00:01:31.469 align:start position:0% are currently mainly defined as an industry<00:01:29.259> by<00:01:29.590> tokens<00:01:30.040> and<00:01:30.310> we're<00:01:31.030> defined<00:01:31.330> as 00:01:31.469 --> 00:01:31.479 align:start position:0% industry by tokens and we're defined as 00:01:31.479 --> 00:01:33.570 align:start position:0% industry by tokens and we're defined as an<00:01:31.570> industry<00:01:31.780> by<00:01:32.020> tokens<00:01:32.439> because<00:01:32.860> that's 00:01:33.570 --> 00:01:33.580 align:start position:0% an industry by tokens because that's 00:01:33.580 --> 00:01:35.429 align:start position:0% an industry by tokens because that's effectively<00:01:34.150> what<00:01:34.360> base<00:01:34.570> layer<00:01:34.840> 1<00:01:35.049> systems 00:01:35.429 --> 00:01:35.439 align:start position:0% effectively what base layer 1 systems 00:01:35.439 --> 00:01:36.990 align:start position:0% effectively what base layer 1 systems can<00:01:35.619> do<00:01:35.799> because<00:01:36.189> they<00:01:36.310> have<00:01:36.340> it<00:01:36.640> inherently 00:01:36.990 --> 00:01:37.000 align:start position:0% can do because they have it inherently 00:01:37.000 --> 00:01:39.149 align:start position:0% can do because they have it inherently built-in<00:01:37.570> to<00:01:38.020> incentivize<00:01:38.470> mining<00:01:39.040> and 00:01:39.149 --> 00:01:39.159 align:start position:0% built-in to incentivize mining and 00:01:39.159 --> 00:01:40.800 align:start position:0% built-in to incentivize mining and therefore<00:01:39.549> allow<00:01:40.060> their<00:01:40.299> you<00:01:40.540> know<00:01:40.570> their 00:01:40.800 --> 00:01:40.810 align:start position:0% therefore allow their you know their 00:01:40.810 --> 00:01:44.910 align:start position:0% therefore allow their you know their base<00:01:40.990> basic<00:01:41.590> existence<00:01:42.090> now<00:01:43.290> the<00:01:44.290> the<00:01:44.650> reality 00:01:44.910 --> 00:01:44.920 align:start position:0% base basic existence now the the reality 00:01:44.920 --> 00:01:47.850 align:start position:0% base basic existence now the the reality is<00:01:45.280> is<00:01:46.060> that<00:01:46.090> if<00:01:46.360> you<00:01:46.450> look<00:01:46.659> at<00:01:46.840> the<00:01:47.380> the<00:01:47.619> rest 00:01:47.850 --> 00:01:47.860 align:start position:0% is is that if you look at the the rest 00:01:47.860 --> 00:01:49.230 align:start position:0% is is that if you look at the the rest of<00:01:48.040> the<00:01:48.130> world<00:01:48.340> and<00:01:48.670> you<00:01:48.729> look<00:01:48.759> at<00:01:49.000> all<00:01:49.119> the 00:01:49.230 --> 00:01:49.240 align:start position:0% of the world and you look at all the 00:01:49.240 --> 00:01:52.649 align:start position:0% of the world and you look at all the digital<00:01:49.600> agreements<00:01:50.189> powering<00:01:51.659> financial 00:01:52.649 --> 00:01:52.659 align:start position:0% digital agreements powering financial 00:01:52.659 --> 00:01:55.319 align:start position:0% digital agreements powering financial products<00:01:53.170> in<00:01:53.530> in<00:01:54.009> various<00:01:54.369> centralized<00:01:54.850> forms 00:01:55.319 --> 00:01:55.329 align:start position:0% products in in various centralized forms 00:01:55.329 --> 00:01:58.020 align:start position:0% products in in various centralized forms the<00:01:55.930> insurance<00:01:56.350> industry<00:01:56.920> the<00:01:57.490> global<00:01:57.790> trade 00:01:58.020 --> 00:01:58.030 align:start position:0% the insurance industry the global trade 00:01:58.030 --> 00:02:00.090 align:start position:0% the insurance industry the global trade trade<00:01:58.329> finance<00:01:58.689> industry<00:01:58.899> all<00:01:59.560> of<00:01:59.979> these 00:02:00.090 --> 00:02:00.100 align:start position:0% trade finance industry all of these 00:02:00.100 --> 00:02:01.770 align:start position:0% trade finance industry all of these industries<00:02:00.640> use<00:02:00.880> some<00:02:01.180> form<00:02:01.479> of<00:02:01.600> digital 00:02:01.770 --> 00:02:01.780 align:start position:0% industries use some form of digital 00:02:01.780 --> 00:02:03.810 align:start position:0% industries use some form of digital agreement<00:02:02.409> and<00:02:02.590> all<00:02:03.070> of<00:02:03.159> those<00:02:03.280> forms<00:02:03.700> of 00:02:03.810 --> 00:02:03.820 align:start position:0% agreement and all of those forms of 00:02:03.820 --> 00:02:07.440 align:start position:0% agreement and all of those forms of digital<00:02:03.939> agreement<00:02:04.829> require<00:02:05.829> inputs<00:02:06.450> inputs 00:02:07.440 --> 00:02:07.450 align:start position:0% digital agreement require inputs inputs 00:02:07.450 --> 00:02:10.469 align:start position:0% digital agreement require inputs inputs about<00:02:08.049> what<00:02:08.799> happened<00:02:09.399> relative<00:02:10.239> to<00:02:10.360> the 00:02:10.469 --> 00:02:10.479 align:start position:0% about what happened relative to the 00:02:10.479 --> 00:02:12.810 align:start position:0% about what happened relative to the agreements<00:02:10.929> terms<00:02:11.430> so<00:02:12.430> generally<00:02:12.790> speaking 00:02:12.810 --> 00:02:12.820 align:start position:0% agreements terms so generally speaking 00:02:12.820 --> 00:02:16.589 align:start position:0% agreements terms so generally speaking we<00:02:13.269> call<00:02:13.480> these<00:02:13.630> events<00:02:14.079> and<00:02:14.400> the<00:02:15.569> ability<00:02:16.569> for 00:02:16.589 --> 00:02:16.599 align:start position:0% we call these events and the ability for 00:02:16.599 --> 00:02:18.750 align:start position:0% we call these events and the ability for a<00:02:16.870> contract<00:02:17.349> to<00:02:17.530> know<00:02:17.650> about<00:02:17.770> an<00:02:18.010> event<00:02:18.220> is<00:02:18.520> the 00:02:18.750 --> 00:02:18.760 align:start position:0% a contract to know about an event is the 00:02:18.760 --> 00:02:21.120 align:start position:0% a contract to know about an event is the is<00:02:18.940> the<00:02:19.180> necessary<00:02:19.780> point<00:02:20.140> is<00:02:20.290> the<00:02:20.410> necessary 00:02:21.120 --> 00:02:21.130 align:start position:0% is the necessary point is the necessary 00:02:21.130 --> 00:02:24.260 align:start position:0% is the necessary point is the necessary for<00:02:21.460> it<00:02:21.550> to<00:02:21.760> be<00:02:22.150> written<00:02:22.570> about<00:02:22.780> that<00:02:23.020> event<00:02:23.170> so 00:02:24.260 --> 00:02:24.270 align:start position:0% for it to be written about that event so 00:02:24.270 --> 00:02:27.000 align:start position:0% for it to be written about that event so essentially<00:02:25.270> the<00:02:25.720> the<00:02:26.260> significance<00:02:26.410> of<00:02:26.890> the 00:02:27.000 --> 00:02:27.010 align:start position:0% essentially the the significance of the 00:02:27.010 --> 00:02:28.860 align:start position:0% essentially the the significance of the limitation<00:02:27.490> is<00:02:27.640> with<00:02:28.150> without<00:02:28.510> the<00:02:28.570> ability 00:02:28.860 --> 00:02:28.870 align:start position:0% limitation is with without the ability 00:02:28.870 --> 00:02:31.760 align:start position:0% limitation is with without the ability interact<00:02:29.380> with<00:02:29.770> events<00:02:30.100> smart<00:02:30.370> contracts 00:02:31.760 --> 00:02:31.770 align:start position:0% interact with events smart contracts 00:02:31.770 --> 00:02:34.710 align:start position:0% interact with events smart contracts would<00:02:32.770> stay<00:02:33.010> related<00:02:33.670> to<00:02:33.760> tokens<00:02:34.150> which<00:02:34.540> is 00:02:34.710 --> 00:02:34.720 align:start position:0% would stay related to tokens which is 00:02:34.720 --> 00:02:36.360 align:start position:0% would stay related to tokens which is only<00:02:34.900> a<00:02:34.990> small<00:02:35.080> percentage<00:02:35.710> of<00:02:35.860> what<00:02:35.920> our 00:02:36.360 --> 00:02:36.370 align:start position:0% only a small percentage of what our 00:02:36.370 --> 00:02:38.610 align:start position:0% only a small percentage of what our technology<00:02:37.030> could<00:02:37.600> be<00:02:37.720> about<00:02:37.930> so<00:02:38.500> our 00:02:38.610 --> 00:02:38.620 align:start position:0% technology could be about so our 00:02:38.620 --> 00:02:40.500 align:start position:0% technology could be about so our industry<00:02:39.010> could<00:02:39.160> be<00:02:39.220> about<00:02:39.550> financial 00:02:40.500 --> 00:02:40.510 align:start position:0% industry could be about financial 00:02:40.510 --> 00:02:43.140 align:start position:0% industry could be about financial products<00:02:40.900> insurance<00:02:41.380> global<00:02:41.950> trade<00:02:42.190> if<00:02:42.460> if 00:02:43.140 --> 00:02:43.150 align:start position:0% products insurance global trade if if 00:02:43.150 --> 00:02:45.380 align:start position:0% products insurance global trade if if we're<00:02:43.390> able<00:02:43.510> to<00:02:43.750> solve<00:02:43.930> this<00:02:44.080> problem<00:02:44.140> so 00:02:45.380 --> 00:02:45.390 align:start position:0% we're able to solve this problem so 00:02:45.390 --> 00:02:47.520 align:start position:0% we're able to solve this problem so historically<00:02:46.390> how<00:02:46.630> our<00:02:46.960> industry<00:02:47.440> has 00:02:47.520 --> 00:02:47.530 align:start position:0% historically how our industry has 00:02:47.530 --> 00:02:50.090 align:start position:0% historically how our industry has actually<00:02:47.730> evolved<00:02:48.730> is<00:02:48.910> it's<00:02:49.150> gone<00:02:49.360> from<00:02:49.600> a 00:02:50.090 --> 00:02:50.100 align:start position:0% actually evolved is it's gone from a 00:02:50.100 --> 00:02:52.290 align:start position:0% actually evolved is it's gone from a smaller<00:02:51.100> set<00:02:51.430> of<00:02:51.460> capabilities<00:02:51.730> for 00:02:52.290 --> 00:02:52.300 align:start position:0% smaller set of capabilities for 00:02:52.300 --> 00:02:53.610 align:start position:0% smaller set of capabilities for developers<00:02:52.780> to<00:02:52.960> a<00:02:52.990> larger<00:02:53.380> set<00:02:53.590> of 00:02:53.610 --> 00:02:53.620 align:start position:0% developers to a larger set of 00:02:53.620 --> 00:02:55.830 align:start position:0% developers to a larger set of capabilities<00:02:54.280> the<00:02:54.970> first<00:02:55.210> large<00:02:55.450> shift<00:02:55.690> in 00:02:55.830 --> 00:02:55.840 align:start position:0% capabilities the first large shift in 00:02:55.840 --> 00:02:58.110 align:start position:0% capabilities the first large shift in capabilities<00:02:56.470> was<00:02:56.770> from<00:02:57.100> Bitcoin<00:02:57.640> Multi 00:02:58.110 --> 00:02:58.120 align:start position:0% capabilities was from Bitcoin Multi 00:02:58.120 --> 00:03:00.240 align:start position:0% capabilities was from Bitcoin Multi signature<00:02:58.570> as<00:02:58.750> the<00:02:59.350> only<00:02:59.470> capability<00:03:00.130> that 00:03:00.240 --> 00:03:00.250 align:start position:0% signature as the only capability that 00:03:00.250 --> 00:03:02.130 align:start position:0% signature as the only capability that anybody<00:03:00.550> could<00:03:00.730> build<00:03:00.910> around<00:03:01.150> in<00:03:01.690> around<00:03:01.960> you 00:03:02.130 --> 00:03:02.140 align:start position:0% anybody could build around in around you 00:03:02.140 --> 00:03:05.730 align:start position:0% anybody could build around in around you know<00:03:02.260> 2011-12<00:03:03.190> and<00:03:03.810> then<00:03:04.810> in<00:03:04.960> about<00:03:05.170> 14<00:03:05.590> you 00:03:05.730 --> 00:03:05.740 align:start position:0% know 2011-12 and then in about 14 you 00:03:05.740 --> 00:03:07.380 align:start position:0% know 2011-12 and then in about 14 you had<00:03:05.890> the<00:03:06.010> first<00:03:06.250> app<00:03:06.490> coins<00:03:06.880> as<00:03:07.180> they<00:03:07.330> were 00:03:07.380 --> 00:03:07.390 align:start position:0% had the first app coins as they were 00:03:07.390 --> 00:03:07.800 align:start position:0% had the first app coins as they were called 00:03:07.800 --> 00:03:07.810 align:start position:0% called 00:03:07.810 --> 00:03:09.810 align:start position:0% called these<00:03:08.230> were<00:03:08.320> protocols<00:03:08.800> smart<00:03:09.160> contracts 00:03:09.810 --> 00:03:09.820 align:start position:0% these were protocols smart contracts 00:03:09.820 --> 00:03:12.090 align:start position:0% these were protocols smart contracts where<00:03:10.300> you<00:03:10.390> had<00:03:10.540> to<00:03:10.690> bake<00:03:10.870> up<00:03:11.110> smart<00:03:11.650> contract 00:03:12.090 --> 00:03:12.100 align:start position:0% where you had to bake up smart contract 00:03:12.100 --> 00:03:14.430 align:start position:0% where you had to bake up smart contract into<00:03:12.310> each<00:03:12.400> protocol<00:03:12.930> then<00:03:13.930> the<00:03:14.050> protocol 00:03:14.430 --> 00:03:14.440 align:start position:0% into each protocol then the protocol 00:03:14.440 --> 00:03:16.110 align:start position:0% into each protocol then the protocol smart<00:03:14.740> contracts<00:03:15.280> got<00:03:15.490> switched<00:03:15.790> over<00:03:16.000> to 00:03:16.110 --> 00:03:16.120 align:start position:0% smart contracts got switched over to 00:03:16.120 --> 00:03:18.240 align:start position:0% smart contracts got switched over to scriptable<00:03:16.540> contracts<00:03:17.530> and<00:03:17.800> scriptable 00:03:18.240 --> 00:03:18.250 align:start position:0% scriptable contracts and scriptable 00:03:18.250 --> 00:03:20.760 align:start position:0% scriptable contracts and scriptable contracts<00:03:18.850> is<00:03:18.940> what<00:03:19.090> aetherium<00:03:19.390> deserves<00:03:19.810> the 00:03:20.760 --> 00:03:20.770 align:start position:0% contracts is what aetherium deserves the 00:03:20.770 --> 00:03:22.830 align:start position:0% contracts is what aetherium deserves the vast<00:03:20.950> majority<00:03:21.130> of<00:03:21.460> the<00:03:21.580> credit<00:03:21.730> for<00:03:22.090> they've 00:03:22.830 --> 00:03:22.840 align:start position:0% vast majority of the credit for they've 00:03:22.840 --> 00:03:25.110 align:start position:0% vast majority of the credit for they've done<00:03:23.050> a<00:03:23.080> fantastic<00:03:23.710> job<00:03:24.160> of<00:03:24.460> taking<00:03:24.580> our<00:03:24.850> space 00:03:25.110 --> 00:03:25.120 align:start position:0% done a fantastic job of taking our space 00:03:25.120 --> 00:03:26.910 align:start position:0% done a fantastic job of taking our space from<00:03:25.360> these<00:03:25.510> protocol<00:03:25.990> contracts<00:03:26.560> that<00:03:26.710> took 00:03:26.910 --> 00:03:26.920 align:start position:0% from these protocol contracts that took 00:03:26.920 --> 00:03:30.000 align:start position:0% from these protocol contracts that took months<00:03:27.250> to<00:03:27.630> get<00:03:28.630> launched<00:03:28.990> to<00:03:29.320> scriptable 00:03:30.000 --> 00:03:30.010 align:start position:0% months to get launched to scriptable 00:03:30.010 --> 00:03:32.310 align:start position:0% months to get launched to scriptable contracts<00:03:30.610> which<00:03:30.730> took<00:03:30.940> days<00:03:31.150> to<00:03:31.360> launch<00:03:31.540> and 00:03:32.310 --> 00:03:32.320 align:start position:0% contracts which took days to launch and 00:03:32.320 --> 00:03:33.780 align:start position:0% contracts which took days to launch and because<00:03:32.620> they<00:03:32.740> took<00:03:32.920> days<00:03:33.100> to<00:03:33.280> launch<00:03:33.370> we<00:03:33.670> now 00:03:33.780 --> 00:03:33.790 align:start position:0% because they took days to launch we now 00:03:33.790 --> 00:03:35.910 align:start position:0% because they took days to launch we now have<00:03:34.000> all<00:03:34.150> these<00:03:34.270> people<00:03:34.600> launching<00:03:35.080> massive 00:03:35.910 --> 00:03:35.920 align:start position:0% have all these people launching massive 00:03:35.920 --> 00:03:38.760 align:start position:0% have all these people launching massive high<00:03:36.790> value<00:03:37.150> systems<00:03:37.570> based<00:03:38.500> on<00:03:38.650> this 00:03:38.760 --> 00:03:38.770 align:start position:0% high value systems based on this 00:03:38.770 --> 00:03:41.670 align:start position:0% high value systems based on this capability<00:03:39.570> and<00:03:40.570> as<00:03:40.900> you<00:03:41.050> can<00:03:41.170> see<00:03:41.350> a<00:03:41.380> lot<00:03:41.590> of 00:03:41.670 --> 00:03:41.680 align:start position:0% capability and as you can see a lot of 00:03:41.680 --> 00:03:42.630 align:start position:0% capability and as you can see a lot of those<00:03:41.800> systems<00:03:41.980> are<00:03:42.250> pretty<00:03:42.430> much 00:03:42.630 --> 00:03:42.640 align:start position:0% those systems are pretty much 00:03:42.640 --> 00:03:45.150 align:start position:0% those systems are pretty much exclusively<00:03:43.180> focused<00:03:43.810> on<00:03:43.930> tokens<00:03:44.320> because<00:03:45.010> at 00:03:45.150 --> 00:03:45.160 align:start position:0% exclusively focused on tokens because at 00:03:45.160 --> 00:03:46.350 align:start position:0% exclusively focused on tokens because at the<00:03:45.250> moment<00:03:45.520> that's<00:03:45.640> what<00:03:45.880> scriptable 00:03:46.350 --> 00:03:46.360 align:start position:0% the moment that's what scriptable 00:03:46.360 --> 00:03:48.750 align:start position:0% the moment that's what scriptable capabilities<00:03:47.050> allow<00:03:47.260> what<00:03:47.980> we<00:03:48.130> think<00:03:48.460> is<00:03:48.700> that 00:03:48.750 --> 00:03:48.760 align:start position:0% capabilities allow what we think is that 00:03:48.760 --> 00:03:51.330 align:start position:0% capabilities allow what we think is that scriptable<00:03:49.690> contracts<00:03:50.590> together<00:03:51.070> with 00:03:51.330 --> 00:03:51.340 align:start position:0% scriptable contracts together with 00:03:51.340 --> 00:03:54.480 align:start position:0% scriptable contracts together with external<00:03:52.209> events<00:03:52.690> is<00:03:52.870> how<00:03:53.620> our<00:03:53.860> space<00:03:54.160> moves 00:03:54.480 --> 00:03:54.490 align:start position:0% external events is how our space moves 00:03:54.490 --> 00:03:56.250 align:start position:0% external events is how our space moves into<00:03:54.790> this<00:03:54.880> entirely<00:03:55.300> new<00:03:55.510> stage<00:03:55.900> of 00:03:56.250 --> 00:03:56.260 align:start position:0% into this entirely new stage of 00:03:56.260 --> 00:04:00.449 align:start position:0% into this entirely new stage of usefulness<00:03:56.860> for<00:03:57.570> for<00:03:58.570> developers<00:03:59.080> for<00:03:59.459> users 00:04:00.449 --> 00:04:00.459 align:start position:0% usefulness for for developers for users 00:04:00.459 --> 00:04:03.480 align:start position:0% usefulness for for developers for users you<00:04:00.850> know<00:04:00.970> how<00:04:01.360> we<00:04:01.420> redefine<00:04:02.020> our<00:04:02.170> space<00:04:02.530> to<00:04:03.340> be 00:04:03.480 --> 00:04:03.490 align:start position:0% you know how we redefine our space to be 00:04:03.490 --> 00:04:07.140 align:start position:0% you know how we redefine our space to be about<00:04:04.110> tokens<00:04:05.110> and<00:04:05.500> all<00:04:06.400> the<00:04:06.580> other<00:04:06.700> types<00:04:06.940> of 00:04:07.140 --> 00:04:07.150 align:start position:0% about tokens and all the other types of 00:04:07.150 --> 00:04:10.680 align:start position:0% about tokens and all the other types of digital<00:04:07.300> agreements<00:04:07.990> that<00:04:09.240> that<00:04:10.240> underpin 00:04:10.680 --> 00:04:10.690 align:start position:0% digital agreements that that underpin 00:04:10.690 --> 00:04:12.300 align:start position:0% digital agreements that that underpin you<00:04:11.110> know<00:04:11.230> very<00:04:11.680> important<00:04:12.070> global 00:04:12.300 --> 00:04:12.310 align:start position:0% you know very important global 00:04:12.310 --> 00:04:15.330 align:start position:0% you know very important global industries<00:04:13.800> generally<00:04:14.800> speaking<00:04:15.070> this<00:04:15.280> is 00:04:15.330 --> 00:04:15.340 align:start position:0% industries generally speaking this is 00:04:15.340 --> 00:04:18.030 align:start position:0% industries generally speaking this is the<00:04:15.459> problem<00:04:15.910> that<00:04:15.940> we<00:04:16.060> work<00:04:16.359> on<00:04:16.540> we<00:04:17.500> focus<00:04:17.859> on 00:04:18.030 --> 00:04:18.040 align:start position:0% the problem that we work on we focus on 00:04:18.040 --> 00:04:20.280 align:start position:0% the problem that we work on we focus on creating<00:04:18.670> secure<00:04:19.450> blockchain<00:04:19.900> middleware 00:04:20.280 --> 00:04:20.290 align:start position:0% creating secure blockchain middleware 00:04:20.290 --> 00:04:23.280 align:start position:0% creating secure blockchain middleware that<00:04:21.250> product<00:04:22.150> is<00:04:22.240> called<00:04:22.390> chain<00:04:22.690> link<00:04:22.930> and<00:04:23.200> it 00:04:23.280 --> 00:04:23.290 align:start position:0% that product is called chain link and it 00:04:23.290 --> 00:04:25.680 align:start position:0% that product is called chain link and it basically<00:04:23.590> focuses<00:04:24.340> on<00:04:24.570> enabling<00:04:25.570> the 00:04:25.680 --> 00:04:25.690 align:start position:0% basically focuses on enabling the 00:04:25.690 --> 00:04:28.230 align:start position:0% basically focuses on enabling the ability<00:04:26.110> to<00:04:26.590> get<00:04:26.740> data<00:04:26.950> into<00:04:27.190> networks<00:04:28.120> like 00:04:28.230 --> 00:04:28.240 align:start position:0% ability to get data into networks like 00:04:28.240 --> 00:04:30.000 align:start position:0% ability to get data into networks like aetherium<00:04:28.720> get<00:04:29.050> networks<00:04:29.350> like<00:04:29.440> aetherium<00:04:29.860> to 00:04:30.000 --> 00:04:30.010 align:start position:0% aetherium get networks like aetherium to 00:04:30.010 --> 00:04:31.320 align:start position:0% aetherium get networks like aetherium to pay<00:04:30.160> in<00:04:30.220> other<00:04:30.370> systems<00:04:30.640> and<00:04:30.970> interact<00:04:31.240> with 00:04:31.320 --> 00:04:31.330 align:start position:0% pay in other systems and interact with 00:04:31.330 --> 00:04:33.180 align:start position:0% pay in other systems and interact with other<00:04:31.540> environments<00:04:32.110> as<00:04:32.290> well<00:04:32.800> as<00:04:32.890> get<00:04:33.040> them 00:04:33.180 --> 00:04:33.190 align:start position:0% other environments as well as get them 00:04:33.190 --> 00:04:35.060 align:start position:0% other environments as well as get them to<00:04:33.310> do<00:04:33.430> cross<00:04:33.640> chain<00:04:33.880> things 00:04:35.060 --> 00:04:35.070 align:start position:0% to do cross chain things 00:04:35.070 --> 00:04:37.310 align:start position:0% to do cross chain things we're<00:04:35.669> ready<00:04:36.090> live<00:04:36.240> on<00:04:36.419> main<00:04:36.600> net<00:04:36.780> it's<00:04:37.139> all 00:04:37.310 --> 00:04:37.320 align:start position:0% we're ready live on main net it's all 00:04:37.320 --> 00:04:39.020 align:start position:0% we're ready live on main net it's all working<00:04:37.710> and<00:04:37.919> and<00:04:38.490> the<00:04:38.639> things<00:04:38.820> that<00:04:38.880> I'm 00:04:39.020 --> 00:04:39.030 align:start position:0% working and and the things that I'm 00:04:39.030 --> 00:04:40.340 align:start position:0% working and and the things that I'm going<00:04:39.150> to<00:04:39.180> be<00:04:39.270> showing<00:04:39.479> to<00:04:39.690> you<00:04:39.780> are<00:04:39.930> live<00:04:40.110> and 00:04:40.340 --> 00:04:40.350 align:start position:0% going to be showing to you are live and 00:04:40.350 --> 00:04:43.749 align:start position:0% going to be showing to you are live and working<00:04:40.680> and<00:04:40.770> usable<00:04:41.160> by<00:04:41.190> by<00:04:41.759> us<00:04:42.030> developers 00:04:43.749 --> 00:04:43.759 align:start position:0% working and usable by by us developers 00:04:43.759 --> 00:04:47.689 align:start position:0% working and usable by by us developers so<00:04:44.759> generally<00:04:45.330> speaking<00:04:45.630> the<00:04:46.139> the<00:04:46.560> I<00:04:47.370> think 00:04:47.689 --> 00:04:47.699 align:start position:0% so generally speaking the the I think 00:04:47.699 --> 00:04:50.420 align:start position:0% so generally speaking the the I think there's<00:04:47.970> kind<00:04:48.120> of<00:04:48.270> two<00:04:48.770> two<00:04:49.770> key<00:04:49.919> points<00:04:50.160> and 00:04:50.420 --> 00:04:50.430 align:start position:0% there's kind of two two key points and 00:04:50.430 --> 00:04:53.029 align:start position:0% there's kind of two two key points and in<00:04:50.610> this<00:04:50.789> talk<00:04:51.030> one<00:04:51.270> one<00:04:51.660> key<00:04:51.840> point<00:04:52.110> is<00:04:52.440> how<00:04:52.979> do 00:04:53.029 --> 00:04:53.039 align:start position:0% in this talk one one key point is how do 00:04:53.039 --> 00:04:54.830 align:start position:0% in this talk one one key point is how do you<00:04:53.130> define<00:04:53.310> the<00:04:53.610> security<00:04:54.090> of<00:04:54.180> an<00:04:54.270> Oracle<00:04:54.509> so 00:04:54.830 --> 00:04:54.840 align:start position:0% you define the security of an Oracle so 00:04:54.840 --> 00:04:56.210 align:start position:0% you define the security of an Oracle so that<00:04:54.990> you<00:04:55.080> can<00:04:55.229> rely<00:04:55.500> on<00:04:55.530> it<00:04:55.770> to<00:04:55.860> trigger<00:04:56.039> your 00:04:56.210 --> 00:04:56.220 align:start position:0% that you can rely on it to trigger your 00:04:56.220 --> 00:04:58.070 align:start position:0% that you can rely on it to trigger your contract<00:04:56.729> so<00:04:57.360> that's<00:04:57.539> that's<00:04:57.750> a<00:04:57.930> very 00:04:58.070 --> 00:04:58.080 align:start position:0% contract so that's that's a very 00:04:58.080 --> 00:05:00.020 align:start position:0% contract so that's that's a very important<00:04:58.440> question<00:04:58.530> and<00:04:58.919> then<00:04:59.550> the<00:04:59.699> second 00:05:00.020 --> 00:05:00.030 align:start position:0% important question and then the second 00:05:00.030 --> 00:05:01.370 align:start position:0% important question and then the second question<00:05:00.120> is<00:05:00.479> once<00:05:00.720> you<00:05:00.840> rely<00:05:01.110> on<00:05:01.139> the 00:05:01.370 --> 00:05:01.380 align:start position:0% question is once you rely on the 00:05:01.380 --> 00:05:03.590 align:start position:0% question is once you rely on the security<00:05:01.860> of<00:05:01.889> an<00:05:02.070> Oracle<00:05:02.310> what<00:05:03.000> can<00:05:03.150> an<00:05:03.270> Oracle 00:05:03.590 --> 00:05:03.600 align:start position:0% security of an Oracle what can an Oracle 00:05:03.600 --> 00:05:06.860 align:start position:0% security of an Oracle what can an Oracle really<00:05:03.810> do<00:05:03.990> for<00:05:04.229> you<00:05:04.350> right<00:05:04.949> like<00:05:05.460> okay<00:05:06.210> I've 00:05:06.860 --> 00:05:06.870 align:start position:0% really do for you right like okay I've 00:05:06.870 --> 00:05:08.560 align:start position:0% really do for you right like okay I've arrived<00:05:07.139> at<00:05:07.289> a<00:05:07.350> place<00:05:07.560> where<00:05:07.710> I<00:05:07.800> can<00:05:08.010> can 00:05:08.560 --> 00:05:08.570 align:start position:0% arrived at a place where I can can 00:05:08.570 --> 00:05:11.060 align:start position:0% arrived at a place where I can can assess<00:05:09.570> and<00:05:09.960> feel<00:05:10.289> comfortable<00:05:10.740> about<00:05:10.860> the 00:05:11.060 --> 00:05:11.070 align:start position:0% assess and feel comfortable about the 00:05:11.070 --> 00:05:12.469 align:start position:0% assess and feel comfortable about the security<00:05:11.520> of<00:05:11.550> these<00:05:11.699> of<00:05:12.030> this<00:05:12.150> Oracle 00:05:12.469 --> 00:05:12.479 align:start position:0% security of these of this Oracle 00:05:12.479 --> 00:05:14.750 align:start position:0% security of these of this Oracle mechanism<00:05:12.960> which<00:05:13.590> effectively<00:05:14.010> makes<00:05:14.250> up<00:05:14.580> the 00:05:14.750 --> 00:05:14.760 align:start position:0% mechanism which effectively makes up the 00:05:14.760 --> 00:05:17.570 align:start position:0% mechanism which effectively makes up the second<00:05:15.240> half<00:05:15.449> of<00:05:15.539> my<00:05:15.720> contract<00:05:16.139> because<00:05:17.039> if<00:05:17.160> my 00:05:17.570 --> 00:05:17.580 align:start position:0% second half of my contract because if my 00:05:17.580 --> 00:05:19.070 align:start position:0% second half of my contract because if my contract<00:05:18.060> is<00:05:18.180> about<00:05:18.389> an<00:05:18.510> event<00:05:18.720> I<00:05:18.870> have<00:05:19.050> a 00:05:19.070 --> 00:05:19.080 align:start position:0% contract is about an event I have a 00:05:19.080 --> 00:05:21.110 align:start position:0% contract is about an event I have a piece<00:05:19.380> of<00:05:19.560> it<00:05:19.650> about<00:05:20.190> on<00:05:20.340> change<00:05:20.669> state<00:05:20.940> and<00:05:21.090> I 00:05:21.110 --> 00:05:21.120 align:start position:0% piece of it about on change state and I 00:05:21.120 --> 00:05:22.580 align:start position:0% piece of it about on change state and I have<00:05:21.210> a<00:05:21.240> piece<00:05:21.419> of<00:05:21.600> it<00:05:21.690> about<00:05:21.990> the<00:05:22.139> event<00:05:22.410> and 00:05:22.580 --> 00:05:22.590 align:start position:0% have a piece of it about the event and 00:05:22.590 --> 00:05:25.189 align:start position:0% have a piece of it about the event and both<00:05:23.280> the<00:05:23.850> unchanged<00:05:24.389> state<00:05:24.660> and<00:05:24.930> the<00:05:25.050> off 00:05:25.189 --> 00:05:25.199 align:start position:0% both the unchanged state and the off 00:05:25.199 --> 00:05:27.170 align:start position:0% both the unchanged state and the off trained<00:05:25.440> event<00:05:25.740> needs<00:05:26.400> to<00:05:26.610> be<00:05:26.789> properly 00:05:27.170 --> 00:05:27.180 align:start position:0% trained event needs to be properly 00:05:27.180 --> 00:05:29.360 align:start position:0% trained event needs to be properly guaranteed<00:05:27.990> from<00:05:28.560> a<00:05:28.680> technical<00:05:29.010> point<00:05:29.220> of 00:05:29.360 --> 00:05:29.370 align:start position:0% guaranteed from a technical point of 00:05:29.370 --> 00:05:31.339 align:start position:0% guaranteed from a technical point of view<00:05:29.490> in<00:05:29.970> order<00:05:30.150> for<00:05:30.479> the<00:05:30.599> the<00:05:30.630> smart<00:05:31.169> contract 00:05:31.339 --> 00:05:31.349 align:start position:0% view in order for the the smart contract 00:05:31.349 --> 00:05:33.200 align:start position:0% view in order for the the smart contract to<00:05:31.949> retain<00:05:32.280> its<00:05:32.460> unique<00:05:32.729> property<00:05:33.180> of 00:05:33.200 --> 00:05:33.210 align:start position:0% to retain its unique property of 00:05:33.210 --> 00:05:37.159 align:start position:0% to retain its unique property of reliability<00:05:34.729> so<00:05:35.729> the<00:05:36.479> these<00:05:36.780> are<00:05:36.930> these<00:05:37.110> are 00:05:37.159 --> 00:05:37.169 align:start position:0% reliability so the these are these are 00:05:37.169 --> 00:05:38.210 align:start position:0% reliability so the these are these are kind<00:05:37.440> of<00:05:37.500> the<00:05:37.620> points<00:05:37.860> I'm<00:05:37.949> going<00:05:37.979> to<00:05:38.099> be 00:05:38.210 --> 00:05:38.220 align:start position:0% kind of the points I'm going to be 00:05:38.220 --> 00:05:40.219 align:start position:0% kind of the points I'm going to be speaking<00:05:38.550> about<00:05:38.760> and<00:05:39.060> and<00:05:39.419> elaborating<00:05:40.139> on 00:05:40.219 --> 00:05:40.229 align:start position:0% speaking about and and elaborating on 00:05:40.229 --> 00:05:43.670 align:start position:0% speaking about and and elaborating on what<00:05:40.979> what<00:05:41.580> it<00:05:41.669> is<00:05:41.789> that<00:05:42.060> that<00:05:42.630> what<00:05:43.410> makes<00:05:43.560> a 00:05:43.670 --> 00:05:43.680 align:start position:0% what what it is that that what makes a 00:05:43.680 --> 00:05:45.830 align:start position:0% what what it is that that what makes a secure<00:05:43.979> call<00:05:44.250> and<00:05:44.490> what<00:05:44.699> a<00:05:44.880> secure<00:05:45.300> Oracle<00:05:45.690> can 00:05:45.830 --> 00:05:45.840 align:start position:0% secure call and what a secure Oracle can 00:05:45.840 --> 00:05:48.050 align:start position:0% secure call and what a secure Oracle can do<00:05:45.990> to<00:05:46.500> expand<00:05:46.889> what<00:05:47.039> developers<00:05:47.849> in<00:05:47.970> our 00:05:48.050 --> 00:05:48.060 align:start position:0% do to expand what developers in our 00:05:48.060 --> 00:05:49.969 align:start position:0% do to expand what developers in our space<00:05:48.300> could<00:05:48.510> build<00:05:48.690> to<00:05:49.260> create<00:05:49.740> all<00:05:49.830> these 00:05:49.969 --> 00:05:49.979 align:start position:0% space could build to create all these 00:05:49.979 --> 00:05:51.649 align:start position:0% space could build to create all these other<00:05:50.250> various<00:05:50.639> types<00:05:50.849> of<00:05:51.000> usefulness<00:05:51.360> and 00:05:51.649 --> 00:05:51.659 align:start position:0% other various types of usefulness and 00:05:51.659 --> 00:05:55.670 align:start position:0% other various types of usefulness and and<00:05:51.990> valuable<00:05:52.710> contracts<00:05:54.680> generally 00:05:55.670 --> 00:05:55.680 align:start position:0% and valuable contracts generally 00:05:55.680 --> 00:05:57.740 align:start position:0% and valuable contracts generally speaking<00:05:55.949> our<00:05:56.130> approach<00:05:56.490> to<00:05:56.849> all<00:05:57.210> of<00:05:57.360> this<00:05:57.479> is 00:05:57.740 --> 00:05:57.750 align:start position:0% speaking our approach to all of this is 00:05:57.750 --> 00:06:00.200 align:start position:0% speaking our approach to all of this is the<00:05:57.900> ability<00:05:58.169> to<00:05:58.490> provide<00:05:59.490> decentralization 00:06:00.200 --> 00:06:00.210 align:start position:0% the ability to provide decentralization 00:06:00.210 --> 00:06:02.120 align:start position:0% the ability to provide decentralization for<00:06:00.570> the<00:06:00.659> Oracle<00:06:00.960> mechanism<00:06:01.409> by<00:06:01.860> having 00:06:02.120 --> 00:06:02.130 align:start position:0% for the Oracle mechanism by having 00:06:02.130 --> 00:06:03.500 align:start position:0% for the Oracle mechanism by having multiple<00:06:02.250> independent<00:06:02.909> node<00:06:03.030> operators 00:06:03.500 --> 00:06:03.510 align:start position:0% multiple independent node operators 00:06:03.510 --> 00:06:07.010 align:start position:0% multiple independent node operators validate<00:06:04.020> the<00:06:04.830> accuracy<00:06:05.130> of<00:06:05.550> Oracle<00:06:06.419> Oracle 00:06:07.010 --> 00:06:07.020 align:start position:0% validate the accuracy of Oracle Oracle 00:06:07.020 --> 00:06:09.589 align:start position:0% validate the accuracy of Oracle Oracle reports<00:06:07.880> we<00:06:08.880> do<00:06:09.000> this<00:06:09.150> through<00:06:09.330> something 00:06:09.589 --> 00:06:09.599 align:start position:0% reports we do this through something 00:06:09.599 --> 00:06:10.879 align:start position:0% reports we do this through something called<00:06:09.630> binding<00:06:10.080> service<00:06:10.440> agreements 00:06:10.879 --> 00:06:10.889 align:start position:0% called binding service agreements 00:06:10.889 --> 00:06:13.520 align:start position:0% called binding service agreements binding<00:06:11.250> service<00:06:11.520> agreements<00:06:12.260> make<00:06:13.260> an 00:06:13.520 --> 00:06:13.530 align:start position:0% binding service agreements make an 00:06:13.530 --> 00:06:16.550 align:start position:0% binding service agreements make an Oracle<00:06:14.010> commit<00:06:14.820> to<00:06:15.360> delivering<00:06:15.720> a<00:06:16.080> certain 00:06:16.550 --> 00:06:16.560 align:start position:0% Oracle commit to delivering a certain 00:06:16.560 --> 00:06:18.710 align:start position:0% Oracle commit to delivering a certain quality<00:06:16.740> of<00:06:16.919> data<00:06:17.130> or<00:06:17.400> computation<00:06:18.120> or<00:06:18.330> our 00:06:18.710 --> 00:06:18.720 align:start position:0% quality of data or computation or our 00:06:18.720 --> 00:06:21.409 align:start position:0% quality of data or computation or our payments<00:06:19.080> outcome<00:06:19.440> and<00:06:19.620> that<00:06:20.060> commitment<00:06:21.060> is 00:06:21.409 --> 00:06:21.419 align:start position:0% payments outcome and that commitment is 00:06:21.419 --> 00:06:23.060 align:start position:0% payments outcome and that commitment is both<00:06:21.870> technically<00:06:22.440> in<00:06:22.530> cryptographically 00:06:23.060 --> 00:06:23.070 align:start position:0% both technically in cryptographically 00:06:23.070 --> 00:06:25.129 align:start position:0% both technically in cryptographically guaranteed<00:06:23.610> and<00:06:23.820> crypto<00:06:24.690> economically 00:06:25.129 --> 00:06:25.139 align:start position:0% guaranteed and crypto economically 00:06:25.139 --> 00:06:27.640 align:start position:0% guaranteed and crypto economically guaranteed<00:06:25.590> through<00:06:25.830> things<00:06:26.010> like<00:06:26.070> staking 00:06:27.640 --> 00:06:27.650 align:start position:0% guaranteed through things like staking 00:06:27.650 --> 00:06:30.830 align:start position:0% guaranteed through things like staking the<00:06:28.650> ability<00:06:29.070> for<00:06:29.490> all<00:06:29.789> the<00:06:30.000> binding<00:06:30.479> service 00:06:30.830 --> 00:06:30.840 align:start position:0% the ability for all the binding service 00:06:30.840 --> 00:06:33.890 align:start position:0% the ability for all the binding service agreements<00:06:31.320> that<00:06:31.470> an<00:06:31.650> Oracle<00:06:32.039> a<00:06:32.360> generates<00:06:33.360> to 00:06:33.890 --> 00:06:33.900 align:start position:0% agreements that an Oracle a generates to 00:06:33.900 --> 00:06:36.080 align:start position:0% agreements that an Oracle a generates to be<00:06:34.169> aggregated<00:06:34.560> into<00:06:35.280> a<00:06:35.490> picture<00:06:35.760> of<00:06:36.000> that 00:06:36.080 --> 00:06:36.090 align:start position:0% be aggregated into a picture of that 00:06:36.090 --> 00:06:39.649 align:start position:0% be aggregated into a picture of that Oracle's<00:06:36.599> overall<00:06:37.080> reliability<00:06:38.659> the 00:06:39.649 --> 00:06:39.659 align:start position:0% Oracle's overall reliability the 00:06:39.659 --> 00:06:40.700 align:start position:0% Oracle's overall reliability the application<00:06:40.169> of<00:06:40.289> something<00:06:40.590> called 00:06:40.700 --> 00:06:40.710 align:start position:0% application of something called 00:06:40.710 --> 00:06:42.110 align:start position:0% application of something called defense-in-depth<00:06:41.490> where<00:06:41.789> we<00:06:41.909> lay<00:06:42.030> around 00:06:42.110 --> 00:06:42.120 align:start position:0% defense-in-depth where we lay around 00:06:42.120 --> 00:06:43.940 align:start position:0% defense-in-depth where we lay around multiple<00:06:42.630> security<00:06:42.870> approaches<00:06:43.440> on<00:06:43.650> top<00:06:43.800> of 00:06:43.940 --> 00:06:43.950 align:start position:0% multiple security approaches on top of 00:06:43.950 --> 00:06:45.529 align:start position:0% multiple security approaches on top of decentralization<00:06:44.580> such<00:06:45.000> as<00:06:45.180> trusted 00:06:45.529 --> 00:06:45.539 align:start position:0% decentralization such as trusted 00:06:45.539 --> 00:06:46.730 align:start position:0% decentralization such as trusted execution<00:06:45.750> environments<00:06:46.469> and<00:06:46.560> zero 00:06:46.730 --> 00:06:46.740 align:start position:0% execution environments and zero 00:06:46.740 --> 00:06:47.970 align:start position:0% execution environments and zero knowledge<00:06:46.919> proof 00:06:47.970 --> 00:06:47.980 align:start position:0% knowledge proof 00:06:47.980 --> 00:06:49.890 align:start position:0% knowledge proof and<00:06:48.070> the<00:06:48.970> fact<00:06:49.150> that<00:06:49.240> we<00:06:49.450> do<00:06:49.600> this<00:06:49.690> with<00:06:49.870> a 00:06:49.890 --> 00:06:49.900 align:start position:0% and the fact that we do this with a 00:06:49.900 --> 00:06:51.510 align:start position:0% and the fact that we do this with a large<00:06:50.050> open-source<00:06:50.560> community<00:06:51.010> made<00:06:51.190> up<00:06:51.220> of 00:06:51.510 --> 00:06:51.520 align:start position:0% large open-source community made up of 00:06:51.520 --> 00:06:53.340 align:start position:0% large open-source community made up of some<00:06:51.970> of<00:06:52.060> the<00:06:52.120> best<00:06:52.270> academic<00:06:52.450> researchers 00:06:53.340 --> 00:06:53.350 align:start position:0% some of the best academic researchers 00:06:53.350 --> 00:06:55.290 align:start position:0% some of the best academic researchers the<00:06:54.250> best<00:06:54.430> some<00:06:54.850> of<00:06:54.940> the<00:06:55.000> best<00:06:55.150> security 00:06:55.290 --> 00:06:55.300 align:start position:0% the best some of the best security 00:06:55.300 --> 00:06:57.330 align:start position:0% the best some of the best security auditors<00:06:55.900> and<00:06:56.170> and<00:06:56.890> a<00:06:56.950> large<00:06:57.160> and<00:06:57.280> growing 00:06:57.330 --> 00:06:57.340 align:start position:0% auditors and and a large and growing 00:06:57.340 --> 00:06:59.100 align:start position:0% auditors and and a large and growing group<00:06:57.670> of<00:06:57.790> developers<00:06:58.330> that<00:06:58.360> are<00:06:58.660> excited 00:06:59.100 --> 00:06:59.110 align:start position:0% group of developers that are excited 00:06:59.110 --> 00:07:01.770 align:start position:0% group of developers that are excited about<00:06:59.170> enabling<00:06:59.980> this<00:07:00.580> world<00:07:00.850> of<00:07:01.150> smart 00:07:01.770 --> 00:07:01.780 align:start position:0% about enabling this world of smart 00:07:01.780 --> 00:07:05.250 align:start position:0% about enabling this world of smart contracts<00:07:02.380> beyond<00:07:02.620> tokenization<00:07:03.750> so<00:07:04.750> it's 00:07:05.250 --> 00:07:05.260 align:start position:0% contracts beyond tokenization so it's 00:07:05.260 --> 00:07:07.230 align:start position:0% contracts beyond tokenization so it's usually<00:07:05.410> useful<00:07:05.950> to<00:07:06.250> look<00:07:06.430> at<00:07:06.580> the<00:07:06.790> problem<00:07:07.150> or 00:07:07.230 --> 00:07:07.240 align:start position:0% usually useful to look at the problem or 00:07:07.240 --> 00:07:09.060 align:start position:0% usually useful to look at the problem or solving<00:07:07.660> the<00:07:07.960> the<00:07:08.200> specific<00:07:08.650> problem<00:07:08.950> we're 00:07:09.060 --> 00:07:09.070 align:start position:0% solving the the specific problem we're 00:07:09.070 --> 00:07:10.760 align:start position:0% solving the the specific problem we're solving<00:07:09.220> is<00:07:09.520> the<00:07:09.820> the<00:07:10.090> problem<00:07:10.300> of 00:07:10.760 --> 00:07:10.770 align:start position:0% solving is the the problem of 00:07:10.770 --> 00:07:13.290 align:start position:0% solving is the the problem of centralization<00:07:11.770> and<00:07:12.100> the<00:07:12.490> capacity<00:07:13.060> for<00:07:13.240> an 00:07:13.290 --> 00:07:13.300 align:start position:0% centralization and the capacity for an 00:07:13.300 --> 00:07:16.710 align:start position:0% centralization and the capacity for an Oracle<00:07:13.690> to<00:07:13.720> fail<00:07:14.170> because<00:07:15.010> it's<00:07:15.550> been<00:07:15.850> it's 00:07:16.710 --> 00:07:16.720 align:start position:0% Oracle to fail because it's been it's 00:07:16.720 --> 00:07:20.010 align:start position:0% Oracle to fail because it's been it's been<00:07:17.640> it's<00:07:18.640> been<00:07:18.730> it's<00:07:19.000> been<00:07:19.090> made<00:07:19.300> unreliable 00:07:20.010 --> 00:07:20.020 align:start position:0% been it's been it's been made unreliable 00:07:20.020 --> 00:07:22.050 align:start position:0% been it's been it's been made unreliable by<00:07:20.410> being<00:07:20.980> attacked<00:07:21.280> as<00:07:21.430> a<00:07:21.460> single<00:07:21.820> point<00:07:21.970> of 00:07:22.050 --> 00:07:22.060 align:start position:0% by being attacked as a single point of 00:07:22.060 --> 00:07:24.630 align:start position:0% by being attacked as a single point of failure<00:07:22.530> generally<00:07:23.530> speaking<00:07:23.800> that<00:07:24.340> the<00:07:24.550> way 00:07:24.630 --> 00:07:24.640 align:start position:0% failure generally speaking that the way 00:07:24.640 --> 00:07:25.590 align:start position:0% failure generally speaking that the way to<00:07:24.670> approach<00:07:24.820> this<00:07:25.180> is<00:07:25.300> through<00:07:25.450> the 00:07:25.590 --> 00:07:25.600 align:start position:0% to approach this is through the 00:07:25.600 --> 00:07:28.440 align:start position:0% to approach this is through the centralization<00:07:26.730> just<00:07:27.730> like<00:07:27.850> the<00:07:27.940> contract<00:07:28.330> is 00:07:28.440 --> 00:07:28.450 align:start position:0% centralization just like the contract is 00:07:28.450 --> 00:07:30.390 align:start position:0% centralization just like the contract is secured<00:07:28.750> through<00:07:28.930> multiple<00:07:29.320> node<00:07:29.950> operators 00:07:30.390 --> 00:07:30.400 align:start position:0% secured through multiple node operators 00:07:30.400 --> 00:07:33.200 align:start position:0% secured through multiple node operators validating<00:07:30.910> the<00:07:31.090> the<00:07:31.330> inputs<00:07:31.720> and<00:07:31.960> the 00:07:33.200 --> 00:07:33.210 align:start position:0% validating the the inputs and the 00:07:33.210 --> 00:07:35.850 align:start position:0% validating the the inputs and the validating<00:07:34.210> the<00:07:34.270> transactions<00:07:34.870> that<00:07:34.930> the 00:07:35.850 --> 00:07:35.860 align:start position:0% validating the transactions that the 00:07:35.860 --> 00:07:37.800 align:start position:0% validating the transactions that the block<00:07:36.070> and<00:07:36.220> the<00:07:36.310> contract<00:07:36.700> is<00:07:36.820> made<00:07:36.970> up<00:07:37.090> of<00:07:37.240> we 00:07:37.800 --> 00:07:37.810 align:start position:0% block and the contract is made up of we 00:07:37.810 --> 00:07:39.960 align:start position:0% block and the contract is made up of we have<00:07:37.960> multiple<00:07:38.380> Oracle's<00:07:38.940> validating<00:07:39.940> that 00:07:39.960 --> 00:07:39.970 align:start position:0% have multiple Oracle's validating that 00:07:39.970 --> 00:07:42.630 align:start position:0% have multiple Oracle's validating that an<00:07:40.450> input<00:07:40.870> is<00:07:41.080> is<00:07:41.800> indeed<00:07:42.190> correctly 00:07:42.630 --> 00:07:42.640 align:start position:0% an input is is indeed correctly 00:07:42.640 --> 00:07:44.430 align:start position:0% an input is is indeed correctly validated<00:07:43.150> and<00:07:43.330> secure<00:07:43.810> and<00:07:43.930> reliable<00:07:44.080> enough 00:07:44.430 --> 00:07:44.440 align:start position:0% validated and secure and reliable enough 00:07:44.440 --> 00:07:48.390 align:start position:0% validated and secure and reliable enough to<00:07:44.680> trigger<00:07:44.920> large<00:07:45.640> amounts<00:07:46.000> of<00:07:46.060> value<00:07:47.400> this 00:07:48.390 --> 00:07:48.400 align:start position:0% to trigger large amounts of value this 00:07:48.400 --> 00:07:49.980 align:start position:0% to trigger large amounts of value this is<00:07:48.550> partly<00:07:48.820> guaranteed<00:07:49.300> by<00:07:49.570> service 00:07:49.980 --> 00:07:49.990 align:start position:0% is partly guaranteed by service 00:07:49.990 --> 00:07:51.270 align:start position:0% is partly guaranteed by service agreement<00:07:50.410> service<00:07:50.680> agreements<00:07:51.100> are<00:07:51.190> not 00:07:51.270 --> 00:07:51.280 align:start position:0% agreement service agreements are not 00:07:51.280 --> 00:07:53.090 align:start position:0% agreement service agreements are not legal<00:07:51.700> documents<00:07:52.180> they<00:07:52.300> are<00:07:52.330> on<00:07:52.540> chain 00:07:53.090 --> 00:07:53.100 align:start position:0% legal documents they are on chain 00:07:53.100 --> 00:07:55.410 align:start position:0% legal documents they are on chain commitments<00:07:54.100> that<00:07:54.550> are<00:07:54.610> cryptographically 00:07:55.410 --> 00:07:55.420 align:start position:0% commitments that are cryptographically 00:07:55.420 --> 00:07:57.510 align:start position:0% commitments that are cryptographically and<00:07:55.750> technically<00:07:56.080> enforced<00:07:56.560> to<00:07:57.070> guarantee 00:07:57.510 --> 00:07:57.520 align:start position:0% and technically enforced to guarantee 00:07:57.520 --> 00:07:59.310 align:start position:0% and technically enforced to guarantee that<00:07:57.550> an<00:07:57.820> Oracle<00:07:58.240> does<00:07:58.510> deliver<00:07:58.810> data<00:07:59.020> and 00:07:59.310 --> 00:07:59.320 align:start position:0% that an Oracle does deliver data and 00:07:59.320 --> 00:08:01.230 align:start position:0% that an Oracle does deliver data and that<00:07:59.770> if<00:07:59.980> the<00:08:00.100> Norrell<00:08:00.430> doesn't<00:08:00.790> deliver<00:08:00.970> data 00:08:01.230 --> 00:08:01.240 align:start position:0% that if the Norrell doesn't deliver data 00:08:01.240 --> 00:08:03.780 align:start position:0% that if the Norrell doesn't deliver data there's<00:08:01.930> there's<00:08:02.680> immediate<00:08:03.310> and 00:08:03.780 --> 00:08:03.790 align:start position:0% there's there's immediate and 00:08:03.790 --> 00:08:06.960 align:start position:0% there's there's immediate and inescapable<00:08:04.890> penalties<00:08:05.890> both<00:08:06.550> to<00:08:06.820> their 00:08:06.960 --> 00:08:06.970 align:start position:0% inescapable penalties both to their 00:08:06.970 --> 00:08:08.790 align:start position:0% inescapable penalties both to their their<00:08:07.720> long<00:08:07.900> term<00:08:08.080> usefulness<00:08:08.530> for<00:08:08.560> other 00:08:08.790 --> 00:08:08.800 align:start position:0% their long term usefulness for other 00:08:08.800 --> 00:08:12.630 align:start position:0% their long term usefulness for other users<00:08:09.070> an<00:08:09.970> immediate<00:08:10.330> loss<00:08:10.480> of<00:08:10.840> stake<00:08:11.440> and<00:08:12.310> and 00:08:12.630 --> 00:08:12.640 align:start position:0% users an immediate loss of stake and and 00:08:12.640 --> 00:08:15.510 align:start position:0% users an immediate loss of stake and and and<00:08:12.940> and<00:08:13.240> other<00:08:13.360> negative<00:08:13.630> factors<00:08:14.520> generally 00:08:15.510 --> 00:08:15.520 align:start position:0% and and other negative factors generally 00:08:15.520 --> 00:08:18.540 align:start position:0% and and other negative factors generally speaking<00:08:15.840> we<00:08:16.840> see<00:08:17.050> a<00:08:17.080> world<00:08:17.320> where<00:08:17.530> just<00:08:18.370> like 00:08:18.540 --> 00:08:18.550 align:start position:0% speaking we see a world where just like 00:08:18.550 --> 00:08:20.250 align:start position:0% speaking we see a world where just like you<00:08:18.670> have<00:08:18.880> right<00:08:19.750> now<00:08:19.780> extreme 00:08:20.250 --> 00:08:20.260 align:start position:0% you have right now extreme 00:08:20.260 --> 00:08:21.930 align:start position:0% you have right now extreme decentralization<00:08:20.860> aetherium<00:08:21.490> you<00:08:21.610> should<00:08:21.790> be 00:08:21.930 --> 00:08:21.940 align:start position:0% decentralization aetherium you should be 00:08:21.940 --> 00:08:23.490 align:start position:0% decentralization aetherium you should be able<00:08:22.120> to<00:08:22.210> have<00:08:22.360> whatever<00:08:23.080> degree<00:08:23.260> of 00:08:23.490 --> 00:08:23.500 align:start position:0% able to have whatever degree of 00:08:23.500 --> 00:08:25.470 align:start position:0% able to have whatever degree of decentralization<00:08:24.130> you'd<00:08:24.460> like<00:08:24.640> to<00:08:24.790> have<00:08:24.970> from 00:08:25.470 --> 00:08:25.480 align:start position:0% decentralization you'd like to have from 00:08:25.480 --> 00:08:27.450 align:start position:0% decentralization you'd like to have from the<00:08:25.600> Oracle<00:08:25.900> mechanism<00:08:26.350> and<00:08:26.560> also<00:08:27.190> that'll 00:08:27.450 --> 00:08:27.460 align:start position:0% the Oracle mechanism and also that'll 00:08:27.460 --> 00:08:29.010 align:start position:0% the Oracle mechanism and also that'll probably<00:08:27.610> lead<00:08:27.910> to<00:08:28.090> the<00:08:28.180> centralization<00:08:28.600> at 00:08:29.010 --> 00:08:29.020 align:start position:0% probably lead to the centralization at 00:08:29.020 --> 00:08:31.260 align:start position:0% probably lead to the centralization at the<00:08:29.110> data<00:08:29.290> source<00:08:29.530> level<00:08:29.770> such<00:08:30.730> that<00:08:30.760> you<00:08:31.180> know 00:08:31.260 --> 00:08:31.270 align:start position:0% the data source level such that you know 00:08:31.270 --> 00:08:32.940 align:start position:0% the data source level such that you know the<00:08:31.390> highest<00:08:31.570> value<00:08:32.169> hundreds<00:08:32.560> of<00:08:32.680> millions 00:08:32.940 --> 00:08:32.950 align:start position:0% the highest value hundreds of millions 00:08:32.950 --> 00:08:35.400 align:start position:0% the highest value hundreds of millions of<00:08:33.040> dollar<00:08:33.280> contracts<00:08:34.030> you<00:08:34.510> already<00:08:34.990> see<00:08:35.200> them 00:08:35.400 --> 00:08:35.410 align:start position:0% of dollar contracts you already see them 00:08:35.410 --> 00:08:36.990 align:start position:0% of dollar contracts you already see them thinking<00:08:35.680> about<00:08:35.950> all<00:08:36.220> these<00:08:36.370> things<00:08:36.430> in<00:08:36.880> more 00:08:36.990 --> 00:08:37.000 align:start position:0% thinking about all these things in more 00:08:37.000 --> 00:08:39.690 align:start position:0% thinking about all these things in more detail<00:08:37.419> and<00:08:37.690> you<00:08:38.110> see<00:08:38.290> them<00:08:38.470> wondering<00:08:38.890> why<00:08:39.640> do 00:08:39.690 --> 00:08:39.700 align:start position:0% detail and you see them wondering why do 00:08:39.700 --> 00:08:41.700 align:start position:0% detail and you see them wondering why do I<00:08:39.849> think<00:08:39.880> an<00:08:40.210> Oracle<00:08:40.540> is<00:08:40.630> secure<00:08:41.020> how<00:08:41.500> do<00:08:41.560> I 00:08:41.700 --> 00:08:41.710 align:start position:0% I think an Oracle is secure how do I 00:08:41.710 --> 00:08:43.050 align:start position:0% I think an Oracle is secure how do I know<00:08:41.800> that<00:08:42.070> this<00:08:42.250> data<00:08:42.430> source<00:08:42.669> won't<00:08:42.940> be 00:08:43.050 --> 00:08:43.060 align:start position:0% know that this data source won't be 00:08:43.060 --> 00:08:45.390 align:start position:0% know that this data source won't be compromised<00:08:43.570> how<00:08:44.050> do<00:08:44.110> I<00:08:44.229> protect<00:08:44.620> myself<00:08:44.830> from 00:08:45.390 --> 00:08:45.400 align:start position:0% compromised how do I protect myself from 00:08:45.400 --> 00:08:47.910 align:start position:0% compromised how do I protect myself from a<00:08:46.240> data<00:08:46.630> source<00:08:46.840> being<00:08:47.140> compromised<00:08:47.590> how<00:08:47.770> do<00:08:47.830> I 00:08:47.910 --> 00:08:47.920 align:start position:0% a data source being compromised how do I 00:08:47.920 --> 00:08:49.350 align:start position:0% a data source being compromised how do I protect<00:08:48.250> myself<00:08:48.430> from<00:08:48.670> an<00:08:48.880> Oracle<00:08:49.210> being 00:08:49.350 --> 00:08:49.360 align:start position:0% protect myself from an Oracle being 00:08:49.360 --> 00:08:51.600 align:start position:0% protect myself from an Oracle being compromised<00:08:49.840> these<00:08:50.530> are<00:08:50.710> the<00:08:50.800> problems<00:08:51.310> that 00:08:51.600 --> 00:08:51.610 align:start position:0% compromised these are the problems that 00:08:51.610 --> 00:08:53.520 align:start position:0% compromised these are the problems that our<00:08:52.060> space<00:08:52.420> is<00:08:52.750> going<00:08:53.020> to<00:08:53.080> have<00:08:53.200> to<00:08:53.320> have<00:08:53.440> an 00:08:53.520 --> 00:08:53.530 align:start position:0% our space is going to have to have an 00:08:53.530 --> 00:08:55.770 align:start position:0% our space is going to have to have an answer<00:08:53.680> to<00:08:53.830> if<00:08:54.220> we<00:08:54.730> want<00:08:54.940> to<00:08:55.000> if<00:08:55.270> we<00:08:55.450> wanted<00:08:55.720> to 00:08:55.770 --> 00:08:55.780 align:start position:0% answer to if we want to if we wanted to 00:08:55.780 --> 00:08:57.660 align:start position:0% answer to if we want to if we wanted to move<00:08:56.080> into<00:08:56.440> this<00:08:56.650> realm<00:08:56.920> of<00:08:57.100> events<00:08:57.430> driven 00:08:57.660 --> 00:08:57.670 align:start position:0% move into this realm of events driven 00:08:57.670 --> 00:08:59.640 align:start position:0% move into this realm of events driven contracts<00:08:58.240> so<00:08:58.840> that's<00:08:58.990> that's<00:08:59.230> the<00:08:59.470> very 00:08:59.640 --> 00:08:59.650 align:start position:0% contracts so that's that's the very 00:08:59.650 --> 00:09:01.410 align:start position:0% contracts so that's that's the very large<00:08:59.830> focus<00:09:00.250> that<00:09:00.490> that<00:09:00.850> that<00:09:01.120> we 00:09:01.410 --> 00:09:01.420 align:start position:0% large focus that that that we 00:09:01.420 --> 00:09:03.390 align:start position:0% large focus that that that we have<00:09:01.600> is<00:09:02.140> solving<00:09:02.650> the<00:09:02.710> problem<00:09:03.100> of<00:09:03.190> how<00:09:03.340> do 00:09:03.390 --> 00:09:03.400 align:start position:0% have is solving the problem of how do 00:09:03.400 --> 00:09:06.840 align:start position:0% have is solving the problem of how do you<00:09:03.780> reliably<00:09:04.780> provide<00:09:05.260> guarantees<00:09:05.920> that 00:09:06.840 --> 00:09:06.850 align:start position:0% you reliably provide guarantees that 00:09:06.850 --> 00:09:09.870 align:start position:0% you reliably provide guarantees that your<00:09:07.840> Vince<00:09:08.140> driven<00:09:08.440> contract<00:09:08.950> can<00:09:09.610> have<00:09:09.850> a 00:09:09.870 --> 00:09:09.880 align:start position:0% your Vince driven contract can have a 00:09:09.880 --> 00:09:12.120 align:start position:0% your Vince driven contract can have a billion<00:09:10.210> dollars<00:09:10.510> put<00:09:10.750> into<00:09:10.780> it<00:09:11.080> and<00:09:11.290> can<00:09:11.980> be 00:09:12.120 --> 00:09:12.130 align:start position:0% billion dollars put into it and can be 00:09:12.130 --> 00:09:14.340 align:start position:0% billion dollars put into it and can be considered<00:09:12.580> reliable<00:09:12.940> reliable<00:09:13.930> enough<00:09:14.290> to 00:09:14.340 --> 00:09:14.350 align:start position:0% considered reliable reliable enough to 00:09:14.350 --> 00:09:16.830 align:start position:0% considered reliable reliable enough to move<00:09:14.620> that<00:09:14.680> million<00:09:15.160> billion<00:09:15.670> 100<00:09:16.600> million 00:09:16.830 --> 00:09:16.840 align:start position:0% move that million billion 100 million 00:09:16.840 --> 00:09:18.720 align:start position:0% move that million billion 100 million billion<00:09:17.110> dollars<00:09:17.440> in<00:09:17.920> a<00:09:18.070> matter<00:09:18.220> of<00:09:18.280> seconds 00:09:18.720 --> 00:09:18.730 align:start position:0% billion dollars in a matter of seconds 00:09:18.730 --> 00:09:21.510 align:start position:0% billion dollars in a matter of seconds which<00:09:19.570> is<00:09:19.600> the<00:09:20.020> the<00:09:20.230> real<00:09:20.410> promise<00:09:21.070> and<00:09:21.310> value 00:09:21.510 --> 00:09:21.520 align:start position:0% which is the the real promise and value 00:09:21.520 --> 00:09:23.940 align:start position:0% which is the the real promise and value of<00:09:21.610> our<00:09:21.730> space<00:09:22.110> so<00:09:23.110> generally<00:09:23.500> speaking<00:09:23.530> the 00:09:23.940 --> 00:09:23.950 align:start position:0% of our space so generally speaking the 00:09:23.950 --> 00:09:26.640 align:start position:0% of our space so generally speaking the way<00:09:24.040> this<00:09:24.160> looks<00:09:24.340> in<00:09:24.520> practice<00:09:24.730> is<00:09:25.560> you<00:09:26.560> know 00:09:26.640 --> 00:09:26.650 align:start position:0% way this looks in practice is you know 00:09:26.650 --> 00:09:28.020 align:start position:0% way this looks in practice is you know service<00:09:27.190> agreements<00:09:27.610> are<00:09:27.700> made<00:09:27.850> up<00:09:27.940> of 00:09:28.020 --> 00:09:28.030 align:start position:0% service agreements are made up of 00:09:28.030 --> 00:09:30.150 align:start position:0% service agreements are made up of something<00:09:28.240> called<00:09:28.450> jobs<00:09:28.750> jobs<00:09:29.530> are<00:09:29.710> basically 00:09:30.150 --> 00:09:30.160 align:start position:0% something called jobs jobs are basically 00:09:30.160 --> 00:09:31.710 align:start position:0% something called jobs jobs are basically function<00:09:30.550> as<00:09:30.640> a<00:09:30.670> service<00:09:31.060> of<00:09:31.150> blocks<00:09:31.360> of 00:09:31.710 --> 00:09:31.720 align:start position:0% function as a service of blocks of 00:09:31.720 --> 00:09:34.230 align:start position:0% function as a service of blocks of predefined<00:09:32.350> computations<00:09:33.040> that<00:09:33.790> a<00:09:33.820> node 00:09:34.230 --> 00:09:34.240 align:start position:0% predefined computations that a node 00:09:34.240 --> 00:09:36.270 align:start position:0% predefined computations that a node operator<00:09:34.600> lists<00:09:35.080> themselves<00:09:35.260> as<00:09:35.710> opting<00:09:36.130> into 00:09:36.270 --> 00:09:36.280 align:start position:0% operator lists themselves as opting into 00:09:36.280 --> 00:09:39.030 align:start position:0% operator lists themselves as opting into do<00:09:36.520> you<00:09:37.510> interact<00:09:38.440> with<00:09:38.500> them<00:09:38.680> as<00:09:38.830> on<00:09:39.010> a 00:09:39.030 --> 00:09:39.040 align:start position:0% do you interact with them as on a 00:09:39.040 --> 00:09:41.040 align:start position:0% do you interact with them as on a service<00:09:39.370> agreement<00:09:39.490> they<00:09:39.940> commit<00:09:40.270> to<00:09:40.570> do<00:09:40.900> this 00:09:41.040 --> 00:09:41.050 align:start position:0% service agreement they commit to do this 00:09:41.050 --> 00:09:42.540 align:start position:0% service agreement they commit to do this computation<00:09:41.320> for<00:09:41.740> you<00:09:41.830> in<00:09:41.920> this<00:09:42.010> case<00:09:42.340> the 00:09:42.540 --> 00:09:42.550 align:start position:0% computation for you in this case the 00:09:42.550 --> 00:09:45.270 align:start position:0% computation for you in this case the retrieval<00:09:42.880> of<00:09:43.000> price<00:09:43.620> you<00:09:44.620> select<00:09:44.950> from<00:09:45.250> a 00:09:45.270 --> 00:09:45.280 align:start position:0% retrieval of price you select from a 00:09:45.280 --> 00:09:48.870 align:start position:0% retrieval of price you select from a multitude<00:09:45.850> of<00:09:46.060> nodes<00:09:46.470> we<00:09:47.470> have<00:09:47.500> I<00:09:48.040> predict 00:09:48.870 --> 00:09:48.880 align:start position:0% multitude of nodes we have I predict 00:09:48.880 --> 00:09:50.640 align:start position:0% multitude of nodes we have I predict approaching<00:09:49.210> 70<00:09:49.660> high<00:09:49.840> quality<00:09:50.260> nodes<00:09:50.440> now 00:09:50.640 --> 00:09:50.650 align:start position:0% approaching 70 high quality nodes now 00:09:50.650 --> 00:09:52.290 align:start position:0% approaching 70 high quality nodes now and<00:09:51.040> I<00:09:51.190> think<00:09:51.250> a<00:09:51.430> quarter<00:09:51.730> of<00:09:51.850> them<00:09:52.000> are 00:09:52.290 --> 00:09:52.300 align:start position:0% and I think a quarter of them are 00:09:52.300 --> 00:09:54.090 align:start position:0% and I think a quarter of them are securely<00:09:52.990> reviewed<00:09:53.350> in<00:09:53.500> a<00:09:53.590> two<00:09:53.740> week<00:09:53.860> process 00:09:54.090 --> 00:09:54.100 align:start position:0% securely reviewed in a two week process 00:09:54.100 --> 00:09:56.300 align:start position:0% securely reviewed in a two week process what<00:09:54.550> a<00:09:54.580> security<00:09:55.390> interview<00:09:55.720> at<00:09:55.960> the<00:09:56.110> end 00:09:56.300 --> 00:09:56.310 align:start position:0% what a security interview at the end 00:09:56.310 --> 00:09:58.920 align:start position:0% what a security interview at the end both<00:09:57.310> creating<00:09:57.730> civil<00:09:58.060> resistance<00:09:58.450> in<00:09:58.810> an 00:09:58.920 --> 00:09:58.930 align:start position:0% both creating civil resistance in an 00:09:58.930 --> 00:10:00.150 align:start position:0% both creating civil resistance in an overview<00:09:59.290> of<00:09:59.500> their<00:09:59.860> security 00:10:00.150 --> 00:10:00.160 align:start position:0% overview of their security 00:10:00.160 --> 00:10:01.860 align:start position:0% overview of their security infrastructure<00:10:00.730> which<00:10:01.030> we<00:10:01.180> then<00:10:01.330> present<00:10:01.510> to 00:10:01.860 --> 00:10:01.870 align:start position:0% infrastructure which we then present to 00:10:01.870 --> 00:10:04.590 align:start position:0% infrastructure which we then present to users<00:10:02.110> as<00:10:02.260> well<00:10:02.460> and<00:10:03.460> generally<00:10:04.210> speaking<00:10:04.330> the 00:10:04.590 --> 00:10:04.600 align:start position:0% users as well and generally speaking the 00:10:04.600 --> 00:10:07.380 align:start position:0% users as well and generally speaking the goal<00:10:04.870> is<00:10:05.140> well<00:10:05.950> the<00:10:06.250> dis<00:10:06.610> goal<00:10:06.820> right<00:10:07.240> what 00:10:07.380 --> 00:10:07.390 align:start position:0% goal is well the dis goal right what 00:10:07.390 --> 00:10:09.300 align:start position:0% goal is well the dis goal right what iswhat<00:10:07.600> I<00:10:07.960> shown<00:10:08.650> you<00:10:08.800> here<00:10:09.010> has<00:10:09.160> been 00:10:09.300 --> 00:10:09.310 align:start position:0% iswhat I shown you here has been 00:10:09.310 --> 00:10:12.120 align:start position:0% iswhat I shown you here has been achieved<00:10:09.640> you<00:10:09.970> if<00:10:10.210> you<00:10:10.360> want<00:10:10.690> to<00:10:11.350> compose<00:10:11.740> a 00:10:12.120 --> 00:10:12.130 align:start position:0% achieved you if you want to compose a 00:10:12.130 --> 00:10:13.620 align:start position:0% achieved you if you want to compose a reliable<00:10:12.640> Oracle<00:10:12.970> network<00:10:13.300> with<00:10:13.480> multiple 00:10:13.620 --> 00:10:13.630 align:start position:0% reliable Oracle network with multiple 00:10:13.630 --> 00:10:15.750 align:start position:0% reliable Oracle network with multiple independent<00:10:14.410> parties<00:10:14.980> running<00:10:15.130> that<00:10:15.400> network 00:10:15.750 --> 00:10:15.760 align:start position:0% independent parties running that network 00:10:15.760 --> 00:10:17.370 align:start position:0% independent parties running that network and<00:10:15.970> multiple<00:10:16.450> independent<00:10:16.900> data<00:10:16.990> sources 00:10:17.370 --> 00:10:17.380 align:start position:0% and multiple independent data sources 00:10:17.380 --> 00:10:19.860 align:start position:0% and multiple independent data sources feeding<00:10:18.280> your<00:10:18.510> decentralized<00:10:19.510> finance 00:10:19.860 --> 00:10:19.870 align:start position:0% feeding your decentralized finance 00:10:19.870 --> 00:10:23.400 align:start position:0% feeding your decentralized finance contract<00:10:20.440> reliable<00:10:21.250> data<00:10:21.400> you<00:10:22.210> can<00:10:22.420> is<00:10:23.170> now 00:10:23.400 --> 00:10:23.410 align:start position:0% contract reliable data you can is now 00:10:23.410 --> 00:10:24.660 align:start position:0% contract reliable data you can is now been<00:10:23.620> achieved<00:10:23.890> on<00:10:24.010> may<00:10:24.220> not 00:10:24.660 --> 00:10:24.670 align:start position:0% been achieved on may not 00:10:24.670 --> 00:10:26.250 align:start position:0% been achieved on may not it's<00:10:24.910> been<00:10:25.030> live<00:10:25.240> for<00:10:25.270> you<00:10:25.780> know<00:10:25.870> a<00:10:25.900> number<00:10:26.170> of 00:10:26.250 --> 00:10:26.260 align:start position:0% it's been live for you know a number of 00:10:26.260 --> 00:10:28.290 align:start position:0% it's been live for you know a number of months<00:10:26.440> now<00:10:26.650> without<00:10:27.220> without<00:10:27.670> any<00:10:27.820> security 00:10:28.290 --> 00:10:28.300 align:start position:0% months now without without any security 00:10:28.300 --> 00:10:30.800 align:start position:0% months now without without any security issues<00:10:28.560> likewise<00:10:29.560> if<00:10:29.980> you<00:10:30.100> wanted<00:10:30.280> to<00:10:30.400> compose 00:10:30.800 --> 00:10:30.810 align:start position:0% issues likewise if you wanted to compose 00:10:30.810 --> 00:10:34.230 align:start position:0% issues likewise if you wanted to compose something<00:10:31.810> like<00:10:32.020> smart<00:10:32.640> smart<00:10:33.640> contract<00:10:34.060> a 00:10:34.230 --> 00:10:34.240 align:start position:0% something like smart smart contract a 00:10:34.240 --> 00:10:36.210 align:start position:0% something like smart smart contract a smart<00:10:34.480> contract<00:10:34.840> for<00:10:34.960> crop<00:10:35.140> insurance<00:10:35.220> the 00:10:36.210 --> 00:10:36.220 align:start position:0% smart contract for crop insurance the 00:10:36.220 --> 00:10:39.330 align:start position:0% smart contract for crop insurance the crop<00:10:36.460> insurance<00:10:37.500> would<00:10:38.500> would<00:10:38.770> learn<00:10:39.130> about 00:10:39.330 --> 00:10:39.340 align:start position:0% crop insurance would would learn about 00:10:39.340 --> 00:10:41.700 align:start position:0% crop insurance would would learn about whether<00:10:39.610> it<00:10:40.150> would<00:10:40.300> aggregate<00:10:40.540> death<00:10:40.810> or<00:10:40.930> data 00:10:41.700 --> 00:10:41.710 align:start position:0% whether it would aggregate death or data 00:10:41.710 --> 00:10:44.130 align:start position:0% whether it would aggregate death or data about<00:10:41.950> whether<00:10:42.220> and<00:10:42.520> it<00:10:42.910> would<00:10:43.060> then<00:10:43.270> arrive 00:10:44.130 --> 00:10:44.140 align:start position:0% about whether and it would then arrive 00:10:44.140 --> 00:10:46.380 align:start position:0% about whether and it would then arrive at<00:10:44.170> at<00:10:44.860> a<00:10:44.920> conclusion<00:10:45.460> for<00:10:45.640> that<00:10:45.790> for<00:10:46.360> that 00:10:46.380 --> 00:10:46.390 align:start position:0% at at a conclusion for that for that 00:10:46.390 --> 00:10:49.140 align:start position:0% at at a conclusion for that for that outcome<00:10:46.780> and<00:10:47.190> then<00:10:48.190> also<00:10:48.370> through<00:10:48.790> through 00:10:49.140 --> 00:10:49.150 align:start position:0% outcome and then also through through 00:10:49.150 --> 00:10:50.550 align:start position:0% outcome and then also through through the<00:10:49.240> set<00:10:49.390> of<00:10:49.480> Oracle's<00:10:49.840> that<00:10:49.990> we<00:10:50.080> have<00:10:50.230> be<00:10:50.440> able 00:10:50.550 --> 00:10:50.560 align:start position:0% the set of Oracle's that we have be able 00:10:50.560 --> 00:10:53.160 align:start position:0% the set of Oracle's that we have be able to<00:10:50.710> execute<00:10:51.400> payments<00:10:51.910> so<00:10:52.780> it<00:10:52.810> would<00:10:52.990> be<00:10:53.080> able 00:10:53.160 --> 00:10:53.170 align:start position:0% to execute payments so it would be able 00:10:53.170 --> 00:10:55.710 align:start position:0% to execute payments so it would be able to<00:10:53.320> ingest<00:10:53.950> inputs<00:10:54.340> put<00:10:54.640> outputs<00:10:54.970> and<00:10:55.180> these 00:10:55.710 --> 00:10:55.720 align:start position:0% to ingest inputs put outputs and these 00:10:55.720 --> 00:10:57.570 align:start position:0% to ingest inputs put outputs and these are<00:10:55.930> the<00:10:56.350> previous<00:10:56.530> defy<00:10:56.950> example<00:10:57.370> in<00:10:57.460> this 00:10:57.570 --> 00:10:57.580 align:start position:0% are the previous defy example in this 00:10:57.580 --> 00:10:59.520 align:start position:0% are the previous defy example in this example<00:10:57.910> are<00:10:58.120> what<00:10:58.750> we're<00:10:58.930> really<00:10:59.140> trying<00:10:59.410> to 00:10:59.520 --> 00:10:59.530 align:start position:0% example are what we're really trying to 00:10:59.530 --> 00:11:02.610 align:start position:0% example are what we're really trying to get<00:10:59.860> the<00:11:00.430> space<00:11:00.670> to<00:11:00.970> so<00:11:01.570> that<00:11:01.720> just<00:11:01.990> just<00:11:02.500> like 00:11:02.610 --> 00:11:02.620 align:start position:0% get the space to so that just just like 00:11:02.620 --> 00:11:04.230 align:start position:0% get the space to so that just just like you<00:11:02.740> could<00:11:02.890> write<00:11:03.010> a<00:11:03.070> token<00:11:03.460> in<00:11:03.550> a<00:11:03.610> day<00:11:03.760> you 00:11:04.230 --> 00:11:04.240 align:start position:0% you could write a token in a day you 00:11:04.240 --> 00:11:06.330 align:start position:0% you could write a token in a day you should<00:11:04.300> be<00:11:04.570> able<00:11:04.660> to<00:11:04.780> compose<00:11:05.230> a<00:11:05.680> high-quality 00:11:06.330 --> 00:11:06.340 align:start position:0% should be able to compose a high-quality 00:11:06.340 --> 00:11:08.930 align:start position:0% should be able to compose a high-quality externally<00:11:07.150> connected<00:11:07.330> contract<00:11:07.900> in<00:11:08.050> a<00:11:08.110> day 00:11:08.930 --> 00:11:08.940 align:start position:0% externally connected contract in a day 00:11:08.940 --> 00:11:11.160 align:start position:0% externally connected contract in a day generally<00:11:09.940> speaking<00:11:10.210> what<00:11:10.600> what<00:11:10.840> all<00:11:10.930> of<00:11:10.960> this 00:11:11.160 --> 00:11:11.170 align:start position:0% generally speaking what what all of this 00:11:11.170 --> 00:11:13.020 align:start position:0% generally speaking what what all of this usage<00:11:11.530> does<00:11:11.740> and<00:11:12.220> and<00:11:12.430> this<00:11:12.580> is<00:11:12.730> one<00:11:12.850> of<00:11:12.880> the 00:11:13.020 --> 00:11:13.030 align:start position:0% usage does and and this is one of the 00:11:13.030 --> 00:11:14.550 align:start position:0% usage does and and this is one of the important<00:11:13.360> nuances<00:11:13.810> of<00:11:13.840> how<00:11:14.290> you<00:11:14.350> would 00:11:14.550 --> 00:11:14.560 align:start position:0% important nuances of how you would 00:11:14.560 --> 00:11:15.110 align:start position:0% important nuances of how you would evaluate 00:11:15.110 --> 00:11:15.120 align:start position:0% evaluate 00:11:15.120 --> 00:11:17.269 align:start position:0% evaluate Oracle<00:11:15.480> is<00:11:15.600> generates<00:11:16.080> a<00:11:16.200> lot<00:11:16.320> of<00:11:16.410> data<00:11:16.589> it 00:11:17.269 --> 00:11:17.279 align:start position:0% Oracle is generates a lot of data it 00:11:17.279 --> 00:11:19.730 align:start position:0% Oracle is generates a lot of data it generates<00:11:17.700> massive<00:11:18.089> amounts<00:11:18.360> of<00:11:18.480> data<00:11:18.740> just 00:11:19.730 --> 00:11:19.740 align:start position:0% generates massive amounts of data just 00:11:19.740 --> 00:11:21.500 align:start position:0% generates massive amounts of data just like<00:11:20.100> you<00:11:20.220> have<00:11:20.339> block<00:11:20.760> explorers<00:11:21.270> for<00:11:21.450> a 00:11:21.500 --> 00:11:21.510 align:start position:0% like you have block explorers for a 00:11:21.510 --> 00:11:23.480 align:start position:0% like you have block explorers for a theorem<00:11:21.720> contracts<00:11:22.230> we<00:11:22.740> have<00:11:22.770> even<00:11:23.250> more 00:11:23.480 --> 00:11:23.490 align:start position:0% theorem contracts we have even more 00:11:23.490 --> 00:11:26.450 align:start position:0% theorem contracts we have even more detailed<00:11:23.910> block<00:11:24.120> explorers<00:11:24.660> for<00:11:25.380> Qing<00:11:26.250> link 00:11:26.450 --> 00:11:26.460 align:start position:0% detailed block explorers for Qing link 00:11:26.460 --> 00:11:28.670 align:start position:0% detailed block explorers for Qing link Oracle<00:11:26.790> reports<00:11:27.150> that<00:11:27.720> define<00:11:28.080> exactly<00:11:28.290> what 00:11:28.670 --> 00:11:28.680 align:start position:0% Oracle reports that define exactly what 00:11:28.680 --> 00:11:30.290 align:start position:0% Oracle reports that define exactly what somebody<00:11:29.100> did<00:11:29.279> what<00:11:29.490> they<00:11:29.610> committed<00:11:30.029> to<00:11:30.060> do 00:11:30.290 --> 00:11:30.300 align:start position:0% somebody did what they committed to do 00:11:30.300 --> 00:11:31.970 align:start position:0% somebody did what they committed to do and<00:11:30.570> whether<00:11:31.050> they<00:11:31.230> met<00:11:31.440> their<00:11:31.650> previous 00:11:31.970 --> 00:11:31.980 align:start position:0% and whether they met their previous 00:11:31.980 --> 00:11:34.370 align:start position:0% and whether they met their previous commitment<00:11:32.490> you<00:11:33.270> can<00:11:33.480> you<00:11:33.720> can<00:11:33.870> find<00:11:33.900> all<00:11:34.230> this 00:11:34.370 --> 00:11:34.380 align:start position:0% commitment you can you can find all this 00:11:34.380 --> 00:11:36.680 align:start position:0% commitment you can you can find all this in<00:11:34.620> a<00:11:34.890> multitude<00:11:35.190> of<00:11:35.370> resources<00:11:35.550> and<00:11:36.120> I'll 00:11:36.680 --> 00:11:36.690 align:start position:0% in a multitude of resources and I'll 00:11:36.690 --> 00:11:37.940 align:start position:0% in a multitude of resources and I'll show<00:11:36.930> you<00:11:36.990> how<00:11:37.170> to<00:11:37.230> do<00:11:37.380> that<00:11:37.500> at<00:11:37.650> the<00:11:37.740> end<00:11:37.860> of 00:11:37.940 --> 00:11:37.950 align:start position:0% show you how to do that at the end of 00:11:37.950 --> 00:11:41.269 align:start position:0% show you how to do that at the end of the<00:11:38.040> talk<00:11:38.250> for<00:11:39.560> for<00:11:40.560> a<00:11:40.589> set<00:11:40.800> of<00:11:40.890> Oracle's 00:11:41.269 --> 00:11:41.279 align:start position:0% the talk for for a set of Oracle's 00:11:41.279 --> 00:11:42.829 align:start position:0% the talk for for a set of Oracle's Oracle<00:11:41.850> networks<00:11:42.120> that<00:11:42.240> we<00:11:42.330> call<00:11:42.480> reference 00:11:42.829 --> 00:11:42.839 align:start position:0% Oracle networks that we call reference 00:11:42.839 --> 00:11:46.160 align:start position:0% Oracle networks that we call reference data<00:11:43.050> networks<00:11:44.180> so<00:11:45.180> generally<00:11:45.540> speaking<00:11:45.810> that 00:11:46.160 --> 00:11:46.170 align:start position:0% data networks so generally speaking that 00:11:46.170 --> 00:11:48.740 align:start position:0% data networks so generally speaking that part<00:11:46.500> of<00:11:46.589> the<00:11:46.680> goal<00:11:46.830> here<00:11:46.860> is<00:11:47.100> how<00:11:47.490> do<00:11:47.550> I<00:11:47.700> as<00:11:47.850> a 00:11:48.740 --> 00:11:48.750 align:start position:0% part of the goal here is how do I as a 00:11:48.750 --> 00:11:51.620 align:start position:0% part of the goal here is how do I as a user<00:11:49.400> effectively<00:11:50.400> assess<00:11:50.760> a<00:11:51.029> node<00:11:51.240> operator 00:11:51.620 --> 00:11:51.630 align:start position:0% user effectively assess a node operator 00:11:51.630 --> 00:11:54.050 align:start position:0% user effectively assess a node operator that<00:11:52.020> I<00:11:52.050> can<00:11:52.260> then<00:11:52.500> compose<00:11:53.370> into<00:11:53.700> greater<00:11:53.910> and 00:11:54.050 --> 00:11:54.060 align:start position:0% that I can then compose into greater and 00:11:54.060 --> 00:11:56.420 align:start position:0% that I can then compose into greater and greater<00:11:54.210> networks<00:11:54.690> and<00:11:55.020> such<00:11:55.770> that<00:11:55.980> if<00:11:56.220> not 00:11:56.420 --> 00:11:56.430 align:start position:0% greater networks and such that if not 00:11:56.430 --> 00:11:58.040 align:start position:0% greater networks and such that if not the<00:11:56.550> value<00:11:56.760> of<00:11:56.820> my<00:11:56.940> contract<00:11:57.330> grows<00:11:57.660> I<00:11:57.870> can 00:11:58.040 --> 00:11:58.050 align:start position:0% the value of my contract grows I can 00:11:58.050 --> 00:11:59.540 align:start position:0% the value of my contract grows I can compose<00:11:58.410> greater<00:11:58.770> and<00:11:58.920> greater<00:11:59.040> collections 00:11:59.540 --> 00:11:59.550 align:start position:0% compose greater and greater collections 00:11:59.550 --> 00:12:01.400 align:start position:0% compose greater and greater collections of<00:11:59.670> node<00:11:59.790> operators<00:12:00.270> we<00:12:00.900> enable<00:12:01.230> this<00:12:01.350> by 00:12:01.400 --> 00:12:01.410 align:start position:0% of node operators we enable this by 00:12:01.410 --> 00:12:03.740 align:start position:0% of node operators we enable this by floating<00:12:02.190> provable<00:12:03.120> information<00:12:03.570> about 00:12:03.740 --> 00:12:03.750 align:start position:0% floating provable information about 00:12:03.750 --> 00:12:06.620 align:start position:0% floating provable information about their<00:12:03.900> infrastructure<00:12:04.500> how<00:12:05.190> how<00:12:06.000> they've 00:12:06.620 --> 00:12:06.630 align:start position:0% their infrastructure how how they've 00:12:06.630 --> 00:12:08.120 align:start position:0% their infrastructure how how they've been<00:12:06.750> able<00:12:06.810> to<00:12:07.200> successfully<00:12:07.710> fulfill<00:12:07.800> their 00:12:08.120 --> 00:12:08.130 align:start position:0% been able to successfully fulfill their 00:12:08.130 --> 00:12:10.280 align:start position:0% been able to successfully fulfill their commitments<00:12:08.640> and<00:12:08.820> also<00:12:09.540> what<00:12:09.839> specific 00:12:10.280 --> 00:12:10.290 align:start position:0% commitments and also what specific 00:12:10.290 --> 00:12:12.980 align:start position:0% commitments and also what specific infrastructure<00:12:10.860> they<00:12:11.550> run<00:12:11.820> on<00:12:11.850> and<00:12:12.240> also<00:12:12.810> the 00:12:12.980 --> 00:12:12.990 align:start position:0% infrastructure they run on and also the 00:12:12.990 --> 00:12:14.150 align:start position:0% infrastructure they run on and also the capabilities<00:12:13.529> they<00:12:13.650> can<00:12:13.800> give<00:12:13.920> you<00:12:14.010> through 00:12:14.150 --> 00:12:14.160 align:start position:0% capabilities they can give you through 00:12:14.160 --> 00:12:16.970 align:start position:0% capabilities they can give you through that<00:12:14.250> infrastructure<00:12:15.170> so<00:12:16.170> so<00:12:16.620> that's<00:12:16.800> the 00:12:16.970 --> 00:12:16.980 align:start position:0% that infrastructure so so that's the 00:12:16.980 --> 00:12:18.110 align:start position:0% that infrastructure so so that's the thing<00:12:17.160> that<00:12:17.310> we've<00:12:17.430> actually<00:12:17.580> been<00:12:17.850> seeing 00:12:18.110 --> 00:12:18.120 align:start position:0% thing that we've actually been seeing 00:12:18.120 --> 00:12:20.900 align:start position:0% thing that we've actually been seeing quite<00:12:18.270> a<00:12:18.390> bit<00:12:18.570> of<00:12:18.860> since<00:12:19.860> since<00:12:20.339> launching<00:12:20.820> on 00:12:20.900 --> 00:12:20.910 align:start position:0% quite a bit of since since launching on 00:12:20.910 --> 00:12:22.250 align:start position:0% quite a bit of since since launching on main<00:12:21.089> net<00:12:21.270> we've<00:12:21.450> been<00:12:21.600> seeing<00:12:21.839> quite<00:12:21.990> a<00:12:22.080> lot 00:12:22.250 --> 00:12:22.260 align:start position:0% main net we've been seeing quite a lot 00:12:22.260 --> 00:12:25.160 align:start position:0% main net we've been seeing quite a lot of<00:12:22.410> adoption<00:12:23.310> and<00:12:23.670> in<00:12:23.940> an<00:12:24.209> additional<00:12:24.779> usage 00:12:25.160 --> 00:12:25.170 align:start position:0% of adoption and in an additional usage 00:12:25.170 --> 00:12:27.230 align:start position:0% of adoption and in an additional usage not<00:12:25.650> only<00:12:26.070> in<00:12:26.160> data<00:12:26.339> delivery<00:12:26.790> but<00:12:26.970> in<00:12:27.120> the 00:12:27.230 --> 00:12:27.240 align:start position:0% not only in data delivery but in the 00:12:27.240 --> 00:12:28.670 align:start position:0% not only in data delivery but in the ability<00:12:27.600> for<00:12:27.630> a<00:12:27.779> chain<00:12:27.990> link<00:12:28.140> to<00:12:28.350> connect 00:12:28.670 --> 00:12:28.680 align:start position:0% ability for a chain link to connect 00:12:28.680 --> 00:12:31.250 align:start position:0% ability for a chain link to connect smart<00:12:29.370> contracts<00:12:29.970> to<00:12:30.120> all<00:12:30.150> the<00:12:30.540> different<00:12:30.900> you 00:12:31.250 --> 00:12:31.260 align:start position:0% smart contracts to all the different you 00:12:31.260 --> 00:12:32.870 align:start position:0% smart contracts to all the different you know<00:12:31.350> function<00:12:31.800> as<00:12:31.890> a<00:12:31.920> service<00:12:32.310> systems<00:12:32.640> all 00:12:32.870 --> 00:12:32.880 align:start position:0% know function as a service systems all 00:12:32.880 --> 00:12:34.370 align:start position:0% know function as a service systems all the<00:12:32.910> different<00:12:33.270> computational<00:12:33.839> environments 00:12:34.370 --> 00:12:34.380 align:start position:0% the different computational environments 00:12:34.380 --> 00:12:37.040 align:start position:0% the different computational environments other<00:12:34.770> other<00:12:35.339> than<00:12:35.490> other<00:12:36.150> than<00:12:36.270> block<00:12:36.810> chains 00:12:37.040 --> 00:12:37.050 align:start position:0% other other than other than block chains 00:12:37.050 --> 00:12:39.199 align:start position:0% other other than other than block chains which<00:12:37.380> which<00:12:37.860> gives<00:12:38.100> smart<00:12:38.580> contracts<00:12:39.089> the 00:12:39.199 --> 00:12:39.209 align:start position:0% which which gives smart contracts the 00:12:39.209 --> 00:12:41.660 align:start position:0% which which gives smart contracts the capacity<00:12:39.720> to<00:12:39.750> securely<00:12:40.140> use<00:12:40.410> huge<00:12:41.160> huge 00:12:41.660 --> 00:12:41.670 align:start position:0% capacity to securely use huge huge 00:12:41.670 --> 00:12:44.900 align:start position:0% capacity to securely use huge huge amounts<00:12:42.000> of<00:12:42.089> computing<00:12:42.510> resources<00:12:43.730> this<00:12:44.730> is 00:12:44.900 --> 00:12:44.910 align:start position:0% amounts of computing resources this is 00:12:44.910 --> 00:12:47.780 align:start position:0% amounts of computing resources this is for<00:12:45.029> example<00:12:45.180> a<00:12:45.450> diagram<00:12:45.870> we<00:12:46.020> released<00:12:46.459> in<00:12:47.459> in 00:12:47.780 --> 00:12:47.790 align:start position:0% for example a diagram we released in in 00:12:47.790 --> 00:12:49.820 align:start position:0% for example a diagram we released in in a<00:12:47.880> post<00:12:48.330> with<00:12:48.510> Google<00:12:48.870> describing<00:12:49.680> how<00:12:49.800> a 00:12:49.820 --> 00:12:49.830 align:start position:0% a post with Google describing how a 00:12:49.830 --> 00:12:52.340 align:start position:0% a post with Google describing how a theoretical<00:12:50.550> architecture<00:12:51.180> would<00:12:51.360> look<00:12:51.690> in 00:12:52.340 --> 00:12:52.350 align:start position:0% theoretical architecture would look in 00:12:52.350 --> 00:12:54.079 align:start position:0% theoretical architecture would look in in<00:12:52.830> the<00:12:52.950> case<00:12:53.100> of<00:12:53.279> using<00:12:53.520> Google<00:12:53.880> cloud 00:12:54.079 --> 00:12:54.089 align:start position:0% in the case of using Google cloud 00:12:54.089 --> 00:12:54.740 align:start position:0% in the case of using Google cloud platform 00:12:54.740 --> 00:12:54.750 align:start position:0% platform 00:12:54.750 --> 00:12:56.660 align:start position:0% platform for<00:12:55.110> one<00:12:55.200> of<00:12:55.260> their<00:12:55.380> specific<00:12:55.589> services<00:12:56.490> like 00:12:56.660 --> 00:12:56.670 align:start position:0% for one of their specific services like 00:12:56.670 --> 00:12:59.870 align:start position:0% for one of their specific services like bigquery<00:12:56.880> and<00:12:57.770> here<00:12:58.770> here<00:12:59.580> at<00:12:59.670> Def<00:12:59.850> Con 00:12:59.870 --> 00:12:59.880 align:start position:0% bigquery and here here at Def Con 00:12:59.880 --> 00:13:01.790 align:start position:0% bigquery and here here at Def Con there's<00:13:00.540> been<00:13:00.720> released<00:13:01.020> by<00:13:01.200> one<00:13:01.589> of<00:13:01.740> our 00:13:01.790 --> 00:13:01.800 align:start position:0% there's been released by one of our 00:13:01.800 --> 00:13:04.880 align:start position:0% there's been released by one of our users<00:13:01.980> Foam<00:13:02.990> you<00:13:03.990> know<00:13:04.200> great<00:13:04.410> group<00:13:04.589> of<00:13:04.709> folks 00:13:04.880 --> 00:13:04.890 align:start position:0% users Foam you know great group of folks 00:13:04.890 --> 00:13:07.880 align:start position:0% users Foam you know great group of folks basically<00:13:05.130> building<00:13:05.670> an<00:13:06.570> incentive<00:13:07.470> serve<00:13:07.740> as 00:13:07.880 --> 00:13:07.890 align:start position:0% basically building an incentive serve as 00:13:07.890 --> 00:13:10.010 align:start position:0% basically building an incentive serve as a<00:13:07.920> service<00:13:08.610> to<00:13:08.700> generate<00:13:09.029> valuable<00:13:09.510> location 00:13:10.010 --> 00:13:10.020 align:start position:0% a service to generate valuable location 00:13:10.020 --> 00:13:12.890 align:start position:0% a service to generate valuable location data<00:13:10.200> using<00:13:10.950> token<00:13:11.310> incentives<00:13:11.760> and<00:13:12.089> and 00:13:12.890 --> 00:13:12.900 align:start position:0% data using token incentives and and 00:13:12.900 --> 00:13:15.380 align:start position:0% data using token incentives and and here's<00:13:13.140> how<00:13:13.290> that<00:13:13.470> architecture<00:13:14.160> looks<00:13:14.390> so 00:13:15.380 --> 00:13:15.390 align:start position:0% here's how that architecture looks so 00:13:15.390 --> 00:13:18.260 align:start position:0% here's how that architecture looks so just<00:13:16.170> like<00:13:16.370> you<00:13:17.370> know<00:13:17.490> just<00:13:17.730> like<00:13:17.820> we<00:13:17.880> started 00:13:18.260 --> 00:13:18.270 align:start position:0% just like you know just like we started 00:13:18.270 --> 00:13:19.550 align:start position:0% just like you know just like we started out<00:13:18.420> with<00:13:18.540> data<00:13:18.779> and<00:13:19.020> we've<00:13:19.140> started<00:13:19.350> to 00:13:19.550 --> 00:13:19.560 align:start position:0% out with data and we've started to 00:13:19.560 --> 00:13:21.620 align:start position:0% out with data and we've started to enable<00:13:19.800> a<00:13:19.860> lot<00:13:19.980> of<00:13:20.100> define<00:13:20.490> a<00:13:20.520> lot<00:13:20.760> of<00:13:20.910> simpler 00:13:21.620 --> 00:13:21.630 align:start position:0% enable a lot of define a lot of simpler 00:13:21.630 --> 00:13:24.050 align:start position:0% enable a lot of define a lot of simpler arching<00:13:22.110> contracts<00:13:22.589> with<00:13:22.740> data<00:13:22.950> the<00:13:23.730> next 00:13:24.050 --> 00:13:24.060 align:start position:0% arching contracts with data the next 00:13:24.060 --> 00:13:26.770 align:start position:0% arching contracts with data the next stage<00:13:24.270> in<00:13:24.690> in<00:13:25.020> in<00:13:25.230> all<00:13:25.350> of<00:13:25.380> this<00:13:25.589> is<00:13:25.890> actually 00:13:26.770 --> 00:13:26.780 align:start position:0% stage in in in all of this is actually 00:13:26.780 --> 00:13:27.870 align:start position:0% stage in in in all of this is actually expanding 00:13:27.870 --> 00:13:27.880 align:start position:0% expanding 00:13:27.880 --> 00:13:30.290 align:start position:0% expanding the<00:13:27.940> definition<00:13:28.390> of<00:13:28.450> an<00:13:28.540> Oracle<00:13:28.800> beyond<00:13:29.800> just 00:13:30.290 --> 00:13:30.300 align:start position:0% the definition of an Oracle beyond just 00:13:30.300 --> 00:13:32.460 align:start position:0% the definition of an Oracle beyond just something<00:13:31.300> that<00:13:31.330> provides<00:13:31.630> data<00:13:31.900> but 00:13:32.460 --> 00:13:32.470 align:start position:0% something that provides data but 00:13:32.470 --> 00:13:34.100 align:start position:0% something that provides data but something<00:13:32.800> that<00:13:32.830> actually<00:13:32.950> provides<00:13:33.580> access 00:13:34.100 --> 00:13:34.110 align:start position:0% something that actually provides access 00:13:34.110 --> 00:13:37.560 align:start position:0% something that actually provides access secure<00:13:35.110> and<00:13:35.500> provably<00:13:35.830> secure<00:13:35.980> access<00:13:36.490> to<00:13:37.390> all 00:13:37.560 --> 00:13:37.570 align:start position:0% secure and provably secure access to all 00:13:37.570 --> 00:13:39.590 align:start position:0% secure and provably secure access to all the<00:13:37.780> different<00:13:38.080> computational<00:13:38.770> resources 00:13:39.590 --> 00:13:39.600 align:start position:0% the different computational resources 00:13:39.600 --> 00:13:42.990 align:start position:0% the different computational resources available<00:13:40.600> outside<00:13:40.900> of<00:13:41.530> blockchains<00:13:42.040> this 00:13:42.990 --> 00:13:43.000 align:start position:0% available outside of blockchains this 00:13:43.000 --> 00:13:45.240 align:start position:0% available outside of blockchains this includes<00:13:43.420> random<00:13:43.990> number<00:13:44.440> generators<00:13:44.920> it 00:13:45.240 --> 00:13:45.250 align:start position:0% includes random number generators it 00:13:45.250 --> 00:13:46.950 align:start position:0% includes random number generators it includes<00:13:45.610> all<00:13:45.820> the<00:13:45.910> resources<00:13:46.360> in<00:13:46.720> cloud 00:13:46.950 --> 00:13:46.960 align:start position:0% includes all the resources in cloud 00:13:46.960 --> 00:13:48.600 align:start position:0% includes all the resources in cloud providers<00:13:47.620> all<00:13:47.950> the<00:13:48.070> great<00:13:48.280> pre-made 00:13:48.600 --> 00:13:48.610 align:start position:0% providers all the great pre-made 00:13:48.610 --> 00:13:50.250 align:start position:0% providers all the great pre-made services<00:13:49.150> and<00:13:49.330> functions<00:13:49.660> as<00:13:49.750> a<00:13:49.780> service<00:13:50.110> that 00:13:50.250 --> 00:13:50.260 align:start position:0% services and functions as a service that 00:13:50.260 --> 00:13:52.410 align:start position:0% services and functions as a service that you<00:13:50.350> would<00:13:50.440> want<00:13:50.590> to<00:13:50.650> use<00:13:50.710> and<00:13:51.190> the<00:13:51.880> capacity 00:13:52.410 --> 00:13:52.420 align:start position:0% you would want to use and the capacity 00:13:52.420 --> 00:13:54.510 align:start position:0% you would want to use and the capacity to<00:13:52.450> validate<00:13:53.050> and<00:13:53.350> prove<00:13:53.980> that<00:13:54.010> those 00:13:54.510 --> 00:13:54.520 align:start position:0% to validate and prove that those 00:13:54.520 --> 00:13:58.530 align:start position:0% to validate and prove that those computations<00:13:55.450> were<00:13:56.440> correctly<00:13:56.890> executed<00:13:57.580> on 00:13:58.530 --> 00:13:58.540 align:start position:0% computations were correctly executed on 00:13:58.540 --> 00:14:00.450 align:start position:0% computations were correctly executed on one<00:13:58.900> server<00:13:59.170> serving<00:13:59.590> across<00:13:59.770> across 00:14:00.450 --> 00:14:00.460 align:start position:0% one server serving across across 00:14:00.460 --> 00:14:03.420 align:start position:0% one server serving across across different<00:14:00.820> services<00:14:01.270> so<00:14:02.050> I<00:14:02.530> think<00:14:03.130> the 00:14:03.420 --> 00:14:03.430 align:start position:0% different services so I think the 00:14:03.430 --> 00:14:04.680 align:start position:0% different services so I think the interesting<00:14:03.760> thing<00:14:03.940> that<00:14:03.970> we've<00:14:04.180> seen<00:14:04.210> is<00:14:04.450> the 00:14:04.680 --> 00:14:04.690 align:start position:0% interesting thing that we've seen is the 00:14:04.690 --> 00:14:07.470 align:start position:0% interesting thing that we've seen is the capacity<00:14:05.230> to<00:14:05.260> move<00:14:05.650> beyond<00:14:06.070> data<00:14:06.460> and<00:14:06.820> into 00:14:07.470 --> 00:14:07.480 align:start position:0% capacity to move beyond data and into 00:14:07.480 --> 00:14:10.680 align:start position:0% capacity to move beyond data and into data<00:14:08.080> plus<00:14:08.530> computation<00:14:09.240> such<00:14:10.240> that<00:14:10.510> chain 00:14:10.680 --> 00:14:10.690 align:start position:0% data plus computation such that chain 00:14:10.690 --> 00:14:13.170 align:start position:0% data plus computation such that chain link<00:14:10.840> becomes<00:14:11.200> an<00:14:11.380> off<00:14:11.500> chain<00:14:11.770> resource<00:14:12.220> that 00:14:13.170 --> 00:14:13.180 align:start position:0% link becomes an off chain resource that 00:14:13.180 --> 00:14:15.210 align:start position:0% link becomes an off chain resource that developers<00:14:13.780> can<00:14:13.930> go<00:14:14.110> to<00:14:14.170> to<00:14:14.440> compose<00:14:14.800> whatever 00:14:15.210 --> 00:14:15.220 align:start position:0% developers can go to to compose whatever 00:14:15.220 --> 00:14:17.550 align:start position:0% developers can go to to compose whatever interactions<00:14:15.820> they<00:14:15.970> need<00:14:16.150> to<00:14:16.270> compose<00:14:16.600> around 00:14:17.550 --> 00:14:17.560 align:start position:0% interactions they need to compose around 00:14:17.560 --> 00:14:20.880 align:start position:0% interactions they need to compose around their<00:14:17.740> contract<00:14:18.190> in<00:14:18.820> in<00:14:19.180> in<00:14:20.140> in<00:14:20.410> the<00:14:20.530> world<00:14:20.710> of 00:14:20.880 --> 00:14:20.890 align:start position:0% their contract in in in in the world of 00:14:20.890 --> 00:14:22.440 align:start position:0% their contract in in in in the world of all<00:14:21.010> of<00:14:21.250> Auld<00:14:21.430> already<00:14:21.760> existing<00:14:22.270> high 00:14:22.440 --> 00:14:22.450 align:start position:0% all of Auld already existing high 00:14:22.450 --> 00:14:24.720 align:start position:0% all of Auld already existing high quality<00:14:22.900> of<00:14:23.590> chain<00:14:23.830> computation<00:14:24.430> that's<00:14:24.580> out 00:14:24.720 --> 00:14:24.730 align:start position:0% quality of chain computation that's out 00:14:24.730 --> 00:14:27.540 align:start position:0% quality of chain computation that's out there<00:14:25.140> another<00:14:26.140> example<00:14:26.710> of<00:14:26.980> this<00:14:27.190> is<00:14:27.490> a 00:14:27.540 --> 00:14:27.550 align:start position:0% there another example of this is a 00:14:27.550 --> 00:14:29.010 align:start position:0% there another example of this is a recent<00:14:27.970> announcement<00:14:28.210> at<00:14:28.540> the<00:14:28.600> start<00:14:28.840> of<00:14:28.870> this 00:14:29.010 --> 00:14:29.020 align:start position:0% recent announcement at the start of this 00:14:29.020 --> 00:14:31.200 align:start position:0% recent announcement at the start of this conference<00:14:29.320> about<00:14:29.740> how<00:14:29.920> chain<00:14:30.610> link<00:14:30.790> enables 00:14:31.200 --> 00:14:31.210 align:start position:0% conference about how chain link enables 00:14:31.210 --> 00:14:33.390 align:start position:0% conference about how chain link enables aetherium<00:14:31.930> contracts<00:14:32.650> to<00:14:32.770> use<00:14:32.920> Intel's 00:14:33.390 --> 00:14:33.400 align:start position:0% aetherium contracts to use Intel's 00:14:33.400 --> 00:14:35.940 align:start position:0% aetherium contracts to use Intel's trusted<00:14:33.880> computing<00:14:34.090> framework<00:14:34.600> so<00:14:35.380> Intel<00:14:35.680> has 00:14:35.940 --> 00:14:35.950 align:start position:0% trusted computing framework so Intel has 00:14:35.950 --> 00:14:37.470 align:start position:0% trusted computing framework so Intel has spent<00:14:36.160> a<00:14:36.220> lot<00:14:36.310> of<00:14:36.370> time<00:14:36.580> and<00:14:36.760> effort<00:14:37.000> and<00:14:37.210> and 00:14:37.470 --> 00:14:37.480 align:start position:0% spent a lot of time and effort and and 00:14:37.480 --> 00:14:38.730 align:start position:0% spent a lot of time and effort and and we've<00:14:37.630> been<00:14:37.780> working<00:14:38.050> with<00:14:38.080> them<00:14:38.320> to<00:14:38.350> generate 00:14:38.730 --> 00:14:38.740 align:start position:0% we've been working with them to generate 00:14:38.740 --> 00:14:41.910 align:start position:0% we've been working with them to generate a<00:14:39.430> good<00:14:40.000> trust<00:14:40.240> of<00:14:40.390> computing<00:14:40.720> framework<00:14:41.140> that 00:14:41.910 --> 00:14:41.920 align:start position:0% a good trust of computing framework that 00:14:41.920 --> 00:14:43.650 align:start position:0% a good trust of computing framework that implements<00:14:42.760> trusted<00:14:43.480> execution 00:14:43.650 --> 00:14:43.660 align:start position:0% implements trusted execution 00:14:43.660 --> 00:14:46.500 align:start position:0% implements trusted execution environments<00:14:44.470> as<00:14:44.650> as<00:14:45.640> something<00:14:46.060> that<00:14:46.210> can<00:14:46.390> be 00:14:46.500 --> 00:14:46.510 align:start position:0% environments as as something that can be 00:14:46.510 --> 00:14:48.870 align:start position:0% environments as as something that can be used<00:14:46.660> in<00:14:46.810> layer<00:14:46.960> 2<00:14:47.170> systems<00:14:47.560> and<00:14:47.830> the<00:14:48.340> capacity 00:14:48.870 --> 00:14:48.880 align:start position:0% used in layer 2 systems and the capacity 00:14:48.880 --> 00:14:50.970 align:start position:0% used in layer 2 systems and the capacity to<00:14:49.060> use<00:14:49.540> layer<00:14:49.810> 2<00:14:49.990> systems<00:14:50.350> that<00:14:50.500> use<00:14:50.620> trusted 00:14:50.970 --> 00:14:50.980 align:start position:0% to use layer 2 systems that use trusted 00:14:50.980 --> 00:14:53.820 align:start position:0% to use layer 2 systems that use trusted execution<00:14:51.190> environments<00:14:51.970> as<00:14:52.320> as<00:14:53.320> an<00:14:53.530> option 00:14:53.820 --> 00:14:53.830 align:start position:0% execution environments as as an option 00:14:53.830 --> 00:14:56.150 align:start position:0% execution environments as as an option computational<00:14:54.520> resource<00:14:54.910> that<00:14:55.660> provides 00:14:56.150 --> 00:14:56.160 align:start position:0% computational resource that provides 00:14:56.160 --> 00:15:00.020 align:start position:0% computational resource that provides highly<00:14:57.160> highly<00:14:57.970> reliable<00:14:58.510> highly<00:14:59.320> scalable 00:15:00.020 --> 00:15:00.030 align:start position:0% highly highly reliable highly scalable 00:15:00.030 --> 00:15:04.350 align:start position:0% highly highly reliable highly scalable private<00:15:01.860> computations<00:15:02.860> while<00:15:03.820> keeping<00:15:04.240> a 00:15:04.350 --> 00:15:04.360 align:start position:0% private computations while keeping a 00:15:04.360 --> 00:15:07.380 align:start position:0% private computations while keeping a contract<00:15:04.810> on<00:15:04.990> chain<00:15:05.290> is<00:15:05.590> is<00:15:06.490> right<00:15:06.820> now<00:15:07.000> due<00:15:07.060> to 00:15:07.380 --> 00:15:07.390 align:start position:0% contract on chain is is right now due to 00:15:07.390 --> 00:15:08.730 align:start position:0% contract on chain is is right now due to the<00:15:07.540> current<00:15:07.810> limitations<00:15:08.350> of<00:15:08.470> launching 00:15:08.730 --> 00:15:08.740 align:start position:0% the current limitations of launching 00:15:08.740 --> 00:15:10.500 align:start position:0% the current limitations of launching contracts<00:15:09.370> probably<00:15:09.880> the<00:15:10.000> way<00:15:10.090> people<00:15:10.420> are 00:15:10.500 --> 00:15:10.510 align:start position:0% contracts probably the way people are 00:15:10.510 --> 00:15:12.510 align:start position:0% contracts probably the way people are going<00:15:10.630> to<00:15:10.690> build<00:15:10.930> high<00:15:11.740> throughput<00:15:12.130> high 00:15:12.510 --> 00:15:12.520 align:start position:0% going to build high throughput high 00:15:12.520 --> 00:15:14.880 align:start position:0% going to build high throughput high value<00:15:12.880> applications<00:15:13.140> that<00:15:14.140> still<00:15:14.650> have 00:15:14.880 --> 00:15:14.890 align:start position:0% value applications that still have 00:15:14.890 --> 00:15:18.480 align:start position:0% value applications that still have access<00:15:15.400> to<00:15:15.910> public<00:15:16.090> network<00:15:16.750> value<00:15:17.260> right<00:15:18.160> so 00:15:18.480 --> 00:15:18.490 align:start position:0% access to public network value right so 00:15:18.490 --> 00:15:20.640 align:start position:0% access to public network value right so on<00:15:18.580> the<00:15:18.880> one<00:15:19.000> hand<00:15:19.210> we<00:15:19.810> want<00:15:19.990> applications 00:15:20.640 --> 00:15:20.650 align:start position:0% on the one hand we want applications 00:15:20.650 --> 00:15:22.320 align:start position:0% on the one hand we want applications that<00:15:20.860> exist<00:15:20.980> in<00:15:21.310> large<00:15:21.460> public<00:15:21.730> networks<00:15:22.240> like 00:15:22.320 --> 00:15:22.330 align:start position:0% that exist in large public networks like 00:15:22.330 --> 00:15:24.390 align:start position:0% that exist in large public networks like aetherium<00:15:22.840> that<00:15:23.260> have<00:15:23.410> access<00:15:23.770> to<00:15:23.800> that<00:15:24.070> the 00:15:24.390 --> 00:15:24.400 align:start position:0% aetherium that have access to that the 00:15:24.400 --> 00:15:27.750 align:start position:0% aetherium that have access to that the user<00:15:25.090> set<00:15:25.840> to<00:15:26.080> the<00:15:26.170> network<00:15:26.590> effect<00:15:26.920> kind<00:15:27.610> of 00:15:27.750 --> 00:15:27.760 align:start position:0% user set to the network effect kind of 00:15:27.760 --> 00:15:30.390 align:start position:0% user set to the network effect kind of value<00:15:28.420> that<00:15:28.570> that<00:15:29.050> network<00:15:29.500> has<00:15:29.650> a<00:15:29.680> accrued 00:15:30.390 --> 00:15:30.400 align:start position:0% value that that network has a accrued 00:15:30.400 --> 00:15:32.130 align:start position:0% value that that network has a accrued but<00:15:30.970> at<00:15:31.090> the<00:15:31.180> same<00:15:31.360> time<00:15:31.540> we<00:15:31.720> want<00:15:31.900> a<00:15:31.960> lot<00:15:32.110> of 00:15:32.130 --> 00:15:32.140 align:start position:0% but at the same time we want a lot of 00:15:32.140 --> 00:15:34.020 align:start position:0% but at the same time we want a lot of functionality<00:15:32.680> because<00:15:33.430> we<00:15:33.670> want<00:15:33.820> to<00:15:33.880> build 00:15:34.020 --> 00:15:34.030 align:start position:0% functionality because we want to build 00:15:34.030 --> 00:15:35.640 align:start position:0% functionality because we want to build more<00:15:34.210> and<00:15:34.270> more<00:15:34.480> complex<00:15:34.900> more<00:15:35.320> and<00:15:35.470> more 00:15:35.640 --> 00:15:35.650 align:start position:0% more and more complex more and more 00:15:35.650 --> 00:15:38.700 align:start position:0% more and more complex more and more valuable<00:15:36.160> and<00:15:36.370> useful<00:15:36.460> contracts<00:15:37.180> and<00:15:37.710> the 00:15:38.700 --> 00:15:38.710 align:start position:0% valuable and useful contracts and the 00:15:38.710 --> 00:15:41.520 align:start position:0% valuable and useful contracts and the middle<00:15:38.950> ground<00:15:39.130> seems<00:15:39.550> to<00:15:39.730> be<00:15:39.880> the<00:15:40.780> capacity 00:15:41.520 --> 00:15:41.530 align:start position:0% middle ground seems to be the capacity 00:15:41.530 --> 00:15:43.770 align:start position:0% middle ground seems to be the capacity developer<00:15:42.100> to<00:15:42.430> use<00:15:42.760> an<00:15:42.880> auction<00:15:43.210> computation 00:15:43.770 --> 00:15:43.780 align:start position:0% developer to use an auction computation 00:15:43.780 --> 00:15:45.930 align:start position:0% developer to use an auction computation environment<00:15:44.290> to<00:15:44.770> interact<00:15:45.220> with<00:15:45.340> all<00:15:45.730> the 00:15:45.930 --> 00:15:45.940 align:start position:0% environment to interact with all the 00:15:45.940 --> 00:15:47.460 align:start position:0% environment to interact with all the different<00:15:46.150> computations<00:15:46.870> they<00:15:47.050> need<00:15:47.230> and 00:15:47.460 --> 00:15:47.470 align:start position:0% different computations they need and 00:15:47.470 --> 00:15:50.520 align:start position:0% different computations they need and then<00:15:48.130> to<00:15:48.280> prove<00:15:48.490> back<00:15:48.820> on<00:15:49.120> chain<00:15:49.600> that<00:15:50.320> those 00:15:50.520 --> 00:15:50.530 align:start position:0% then to prove back on chain that those 00:15:50.530 --> 00:15:52.230 align:start position:0% then to prove back on chain that those computations<00:15:50.920> that<00:15:51.460> they<00:15:51.550> performed<00:15:52.060> were 00:15:52.230 --> 00:15:52.240 align:start position:0% computations that they performed were 00:15:52.240 --> 00:15:53.730 align:start position:0% computations that they performed were properly<00:15:52.630> performed<00:15:53.140> that<00:15:53.260> the<00:15:53.380> data<00:15:53.560> was 00:15:53.730 --> 00:15:53.740 align:start position:0% properly performed that the data was 00:15:53.740 --> 00:15:55.080 align:start position:0% properly performed that the data was properly<00:15:54.160> delivered<00:15:54.790> for<00:15:54.970> those 00:15:55.080 --> 00:15:55.090 align:start position:0% properly delivered for those 00:15:55.090 --> 00:15:57.720 align:start position:0% properly delivered for those computations<00:15:55.390> and<00:15:56.050> that<00:15:56.710> that<00:15:57.040> computation 00:15:57.720 --> 00:15:57.730 align:start position:0% computations and that that computation 00:15:57.730 --> 00:15:59.910 align:start position:0% computations and that that computation can't<00:15:58.030> form<00:15:58.270> a<00:15:58.360> reliable<00:15:58.900> part<00:15:59.170> of<00:15:59.380> that 00:15:59.910 --> 00:15:59.920 align:start position:0% can't form a reliable part of that 00:15:59.920 --> 00:16:03.470 align:start position:0% can't form a reliable part of that contract<00:16:00.430> so<00:16:01.330> that's<00:16:01.510> that's<00:16:02.200> kind<00:16:02.470> of<00:16:02.560> the 00:16:03.470 --> 00:16:03.480 align:start position:0% contract so that's that's kind of the 00:16:03.480 --> 00:16:06.300 align:start position:0% contract so that's that's kind of the expansion<00:16:04.480> of<00:16:04.780> of<00:16:05.500> what<00:16:05.770> we're<00:16:05.920> starting<00:16:06.070> to 00:16:06.300 --> 00:16:06.310 align:start position:0% expansion of of what we're starting to 00:16:06.310 --> 00:16:09.450 align:start position:0% expansion of of what we're starting to define<00:16:06.430> chain-linked<00:16:06.970> as<00:16:07.980> what<00:16:08.980> what<00:16:09.250> a<00:16:09.280> lot 00:16:09.450 --> 00:16:09.460 align:start position:0% define chain-linked as what what a lot 00:16:09.460 --> 00:16:11.160 align:start position:0% define chain-linked as what what a lot of<00:16:09.490> this<00:16:09.700> leads<00:16:09.910> to<00:16:10.030> is<00:16:10.300> it<00:16:10.480> leads<00:16:10.810> us<00:16:10.990> to<00:16:11.020> a 00:16:11.160 --> 00:16:11.170 align:start position:0% of this leads to is it leads us to a 00:16:11.170 --> 00:16:13.140 align:start position:0% of this leads to is it leads us to a world<00:16:11.350> where<00:16:11.560> across<00:16:12.100> environments<00:16:12.340> we<00:16:13.120> have 00:16:13.140 --> 00:16:13.150 align:start position:0% world where across environments we have 00:16:13.150 --> 00:16:14.640 align:start position:0% world where across environments we have chain<00:16:13.510> link<00:16:13.660> node<00:16:13.810> operators<00:16:14.290> that<00:16:14.500> are 00:16:14.640 --> 00:16:14.650 align:start position:0% chain link node operators that are 00:16:14.650 --> 00:16:16.580 align:start position:0% chain link node operators that are servicing<00:16:15.070> various<00:16:15.430> different<00:16:15.730> chains<00:16:15.970> and 00:16:16.580 --> 00:16:16.590 align:start position:0% servicing various different chains and 00:16:16.590 --> 00:16:20.190 align:start position:0% servicing various different chains and they're<00:16:17.590> accruing<00:16:18.190> usage<00:16:18.730> and<00:16:19.030> that<00:16:19.660> usage<00:16:20.080> in 00:16:20.190 --> 00:16:20.200 align:start position:0% they're accruing usage and that usage in 00:16:20.200 --> 00:16:21.750 align:start position:0% they're accruing usage and that usage in various<00:16:20.500> different<00:16:20.650> environments<00:16:21.310> is<00:16:21.520> once 00:16:21.750 --> 00:16:21.760 align:start position:0% various different environments is once 00:16:21.760 --> 00:16:24.120 align:start position:0% various different environments is once again<00:16:21.940> another<00:16:22.450> source<00:16:22.750> of<00:16:22.930> proof<00:16:23.140> it's<00:16:24.010> a 00:16:24.120 --> 00:16:24.130 align:start position:0% again another source of proof it's a 00:16:24.130 --> 00:16:25.950 align:start position:0% again another source of proof it's a source<00:16:24.340> of<00:16:24.520> proof<00:16:24.730> that<00:16:24.760> there's<00:16:25.630> you<00:16:25.900> know 00:16:25.950 --> 00:16:25.960 align:start position:0% source of proof that there's you know 00:16:25.960 --> 00:16:27.900 align:start position:0% source of proof that there's you know five<00:16:26.320> defy<00:16:26.710> applications<00:16:27.310> to<00:16:27.580> insurance 00:16:27.900 --> 00:16:27.910 align:start position:0% five defy applications to insurance 00:16:27.910 --> 00:16:30.540 align:start position:0% five defy applications to insurance applications<00:16:28.570> you<00:16:29.260> know<00:16:29.350> five<00:16:29.650> gaming 00:16:30.540 --> 00:16:30.550 align:start position:0% applications you know five gaming 00:16:30.550 --> 00:16:32.220 align:start position:0% applications you know five gaming applications<00:16:31.120> using<00:16:31.360> this<00:16:31.570> note<00:16:31.810> operator 00:16:32.220 --> 00:16:32.230 align:start position:0% applications using this note operator 00:16:32.230 --> 00:16:34.260 align:start position:0% applications using this note operator and<00:16:32.500> this<00:16:33.190> note<00:16:33.400> operator<00:16:33.790> is<00:16:33.940> able<00:16:34.180> to 00:16:34.260 --> 00:16:34.270 align:start position:0% and this note operator is able to 00:16:34.270 --> 00:16:36.060 align:start position:0% and this note operator is able to successfully<00:16:34.870> deliver<00:16:34.960> data<00:16:35.350> and<00:16:35.620> randomness 00:16:36.060 --> 00:16:36.070 align:start position:0% successfully deliver data and randomness 00:16:36.070 --> 00:16:37.860 align:start position:0% successfully deliver data and randomness and<00:16:36.550> and<00:16:36.790> and<00:16:37.000> various<00:16:37.300> types<00:16:37.480> of<00:16:37.630> data<00:16:37.780> to 00:16:37.860 --> 00:16:37.870 align:start position:0% and and and various types of data to 00:16:37.870 --> 00:16:39.900 align:start position:0% and and and various types of data to these<00:16:38.050> users<00:16:38.410> and<00:16:38.590> that<00:16:39.340> provides<00:16:39.760> even 00:16:39.900 --> 00:16:39.910 align:start position:0% these users and that provides even 00:16:39.910 --> 00:16:43.320 align:start position:0% these users and that provides even greater<00:16:40.030> surety<00:16:40.690> so<00:16:41.440> as<00:16:41.770> a<00:16:42.430> system<00:16:42.760> like<00:16:43.060> ours 00:16:43.320 --> 00:16:43.330 align:start position:0% greater surety so as a system like ours 00:16:43.330 --> 00:16:45.960 align:start position:0% greater surety so as a system like ours gets<00:16:43.510> used<00:16:43.840> you<00:16:44.710> you<00:16:44.980> start<00:16:45.310> to<00:16:45.370> accrue<00:16:45.730> a<00:16:45.760> lot 00:16:45.960 --> 00:16:45.970 align:start position:0% gets used you you start to accrue a lot 00:16:45.970 --> 00:16:47.610 align:start position:0% gets used you you start to accrue a lot more<00:16:46.180> data<00:16:46.420> about<00:16:46.720> each<00:16:46.960> individual<00:16:47.470> note 00:16:47.610 --> 00:16:47.620 align:start position:0% more data about each individual note 00:16:47.620 --> 00:16:49.290 align:start position:0% more data about each individual note operator<00:16:47.980> and<00:16:48.220> that<00:16:48.250> accrual<00:16:48.970> of<00:16:49.060> data 00:16:49.290 --> 00:16:49.300 align:start position:0% operator and that accrual of data 00:16:49.300 --> 00:16:51.450 align:start position:0% operator and that accrual of data provides<00:16:49.990> even<00:16:50.230> greater<00:16:50.470> assurances<00:16:51.100> so 00:16:51.450 --> 00:16:51.460 align:start position:0% provides even greater assurances so 00:16:51.460 --> 00:16:53.280 align:start position:0% provides even greater assurances so there<00:16:51.610> there's<00:16:51.850> kind<00:16:52.089> of<00:16:52.150> a<00:16:52.300> network<00:16:53.170> effect 00:16:53.280 --> 00:16:53.290 align:start position:0% there there's kind of a network effect 00:16:53.290 --> 00:16:55.640 align:start position:0% there there's kind of a network effect from<00:16:53.680> usage<00:16:54.070> that<00:16:54.640> allows<00:16:55.060> people<00:16:55.270> to 00:16:55.640 --> 00:16:55.650 align:start position:0% from usage that allows people to 00:16:55.650 --> 00:16:57.900 align:start position:0% from usage that allows people to continually<00:16:56.650> define<00:16:57.070> greater<00:16:57.430> degrees<00:16:57.880> of 00:16:57.900 --> 00:16:57.910 align:start position:0% continually define greater degrees of 00:16:57.910 --> 00:17:00.860 align:start position:0% continually define greater degrees of their<00:16:58.210> security<00:16:58.690> and<00:16:58.780> guarantees<00:16:59.230> for<00:16:59.500> users 00:17:00.860 --> 00:17:00.870 align:start position:0% their security and guarantees for users 00:17:00.870 --> 00:17:03.720 align:start position:0% their security and guarantees for users now<00:17:01.950> one<00:17:02.950> of<00:17:02.980> the<00:17:03.130> things<00:17:03.339> that<00:17:03.520> we've<00:17:03.700> been 00:17:03.720 --> 00:17:03.730 align:start position:0% now one of the things that we've been 00:17:03.730 --> 00:17:06.179 align:start position:0% now one of the things that we've been using<00:17:04.319> you<00:17:05.319> know<00:17:05.439> when<00:17:05.589> it<00:17:05.680> when<00:17:05.829> at<00:17:05.949> one<00:17:06.069> of 00:17:06.179 --> 00:17:06.189 align:start position:0% using you know when it when at one of 00:17:06.189 --> 00:17:07.620 align:start position:0% using you know when it when at one of the<00:17:06.280> Oracle<00:17:06.610> networks<00:17:06.910> that<00:17:07.089> we've<00:17:07.240> composed 00:17:07.620 --> 00:17:07.630 align:start position:0% the Oracle networks that we've composed 00:17:07.630 --> 00:17:10.319 align:start position:0% the Oracle networks that we've composed for<00:17:08.110> the<00:17:08.260> use<00:17:08.470> of<00:17:08.800> the<00:17:09.250> ecosystem<00:17:09.850> are<00:17:10.089> these 00:17:10.319 --> 00:17:10.329 align:start position:0% for the use of the ecosystem are these 00:17:10.329 --> 00:17:12.449 align:start position:0% for the use of the ecosystem are these reference<00:17:10.930> price<00:17:11.500> reference<00:17:11.890> data<00:17:12.100> networks 00:17:12.449 --> 00:17:12.459 align:start position:0% reference price reference data networks 00:17:12.459 --> 00:17:14.790 align:start position:0% reference price reference data networks price<00:17:13.420> reference<00:17:13.990> data<00:17:14.170> networks<00:17:14.560> basically 00:17:14.790 --> 00:17:14.800 align:start position:0% price reference data networks basically 00:17:14.800 --> 00:17:17.730 align:start position:0% price reference data networks basically put<00:17:15.280> data<00:17:15.490> on<00:17:15.670> chain<00:17:16.030> they<00:17:16.900> put<00:17:17.110> data<00:17:17.290> on<00:17:17.439> chain 00:17:17.730 --> 00:17:17.740 align:start position:0% put data on chain they put data on chain 00:17:17.740 --> 00:17:20.280 align:start position:0% put data on chain they put data on chain for<00:17:18.160> use<00:17:18.400> mainly<00:17:18.850> by<00:17:19.089> D<00:17:19.150> Phi<00:17:19.449> projects<00:17:20.050> and 00:17:20.280 --> 00:17:20.290 align:start position:0% for use mainly by D Phi projects and 00:17:20.290 --> 00:17:22.350 align:start position:0% for use mainly by D Phi projects and right<00:17:20.920> now<00:17:21.100> price<00:17:21.400> reference<00:17:21.760> data<00:17:21.939> networks 00:17:22.350 --> 00:17:22.360 align:start position:0% right now price reference data networks 00:17:22.360 --> 00:17:24.390 align:start position:0% right now price reference data networks like<00:17:22.990> like<00:17:23.290> the<00:17:23.410> one<00:17:23.560> I<00:17:23.589> I'm<00:17:23.860> showing<00:17:24.130> here 00:17:24.390 --> 00:17:24.400 align:start position:0% like like the one I I'm showing here 00:17:24.400 --> 00:17:26.780 align:start position:0% like like the one I I'm showing here powers<00:17:25.120> all<00:17:25.420> of<00:17:25.569> the<00:17:25.660> centralized<00:17:26.079> finance 00:17:26.780 --> 00:17:26.790 align:start position:0% powers all of the centralized finance 00:17:26.790 --> 00:17:29.100 align:start position:0% powers all of the centralized finance well<00:17:27.790> it<00:17:28.000> except<00:17:28.600> if<00:17:28.720> somebody<00:17:28.960> made<00:17:29.080> a 00:17:29.100 --> 00:17:29.110 align:start position:0% well it except if somebody made a 00:17:29.110 --> 00:17:30.720 align:start position:0% well it except if somebody made a centralized<00:17:29.560> Oracle<00:17:29.920> and<00:17:30.070> you<00:17:30.400> took<00:17:30.520> a<00:17:30.580> big 00:17:30.720 --> 00:17:30.730 align:start position:0% centralized Oracle and you took a big 00:17:30.730 --> 00:17:32.400 align:start position:0% centralized Oracle and you took a big risk<00:17:30.760> on<00:17:31.030> that<00:17:31.060> but<00:17:31.450> you<00:17:31.600> know<00:17:31.720> that's<00:17:31.870> that's 00:17:32.400 --> 00:17:32.410 align:start position:0% risk on that but you know that's that's 00:17:32.410 --> 00:17:33.420 align:start position:0% risk on that but you know that's that's their<00:17:32.560> decision<00:17:32.740> which<00:17:33.070> I<00:17:33.160> don't<00:17:33.220> really 00:17:33.420 --> 00:17:33.430 align:start position:0% their decision which I don't really 00:17:33.430 --> 00:17:36.960 align:start position:0% their decision which I don't really advise<00:17:34.320> so<00:17:35.320> these<00:17:35.710> price<00:17:35.920> reference<00:17:36.790> data 00:17:36.960 --> 00:17:36.970 align:start position:0% advise so these price reference data 00:17:36.970 --> 00:17:38.640 align:start position:0% advise so these price reference data networks<00:17:37.330> that<00:17:37.480> we've<00:17:37.630> already<00:17:37.750> made<00:17:37.990> right 00:17:38.640 --> 00:17:38.650 align:start position:0% networks that we've already made right 00:17:38.650 --> 00:17:41.040 align:start position:0% networks that we've already made right now<00:17:38.680> have<00:17:39.100> grown<00:17:39.400> to<00:17:39.640> be<00:17:39.850> the<00:17:40.180> largest<00:17:40.330> most 00:17:41.040 --> 00:17:41.050 align:start position:0% now have grown to be the largest most 00:17:41.050 --> 00:17:43.110 align:start position:0% now have grown to be the largest most secure<00:17:41.500> most<00:17:41.800> civil<00:17:42.070> resistant<00:17:42.520> we<00:17:42.970> can 00:17:43.110 --> 00:17:43.120 align:start position:0% secure most civil resistant we can 00:17:43.120 --> 00:17:44.610 align:start position:0% secure most civil resistant we can definitively<00:17:43.360> say<00:17:43.630> that<00:17:43.840> because<00:17:44.140> we<00:17:44.440> have 00:17:44.610 --> 00:17:44.620 align:start position:0% definitively say that because we have 00:17:44.620 --> 00:17:46.620 align:start position:0% definitively say that because we have the<00:17:44.890> most<00:17:45.250> note<00:17:45.520> operators<00:17:46.000> for<00:17:46.180> example<00:17:46.540> in 00:17:46.620 --> 00:17:46.630 align:start position:0% the most note operators for example in 00:17:46.630 --> 00:17:48.990 align:start position:0% the most note operators for example in this<00:17:46.750> network<00:17:47.470> with<00:17:47.650> eath<00:17:47.800> USD<00:17:48.190> price<00:17:48.400> we<00:17:48.880> have 00:17:48.990 --> 00:17:49.000 align:start position:0% this network with eath USD price we have 00:17:49.000 --> 00:17:50.310 align:start position:0% this network with eath USD price we have seventeen<00:17:49.510> and<00:17:49.720> we're<00:17:49.840> far<00:17:50.050> ahead<00:17:50.170> of 00:17:50.310 --> 00:17:50.320 align:start position:0% seventeen and we're far ahead of 00:17:50.320 --> 00:17:52.500 align:start position:0% seventeen and we're far ahead of schedule<00:17:50.410> to<00:17:51.280> reach<00:17:51.429> the<00:17:51.700> targeted<00:17:52.270> twenty 00:17:52.500 --> 00:17:52.510 align:start position:0% schedule to reach the targeted twenty 00:17:52.510 --> 00:17:55.169 align:start position:0% schedule to reach the targeted twenty one<00:17:52.660> we<00:17:53.320> have<00:17:53.440> multiple<00:17:53.830> high<00:17:53.980> quality<00:17:54.429> data 00:17:55.169 --> 00:17:55.179 align:start position:0% one we have multiple high quality data 00:17:55.179 --> 00:17:57.479 align:start position:0% one we have multiple high quality data sources<00:17:56.049> so<00:17:56.379> not<00:17:56.529> original<00:17:56.919> exchanges<00:17:57.339> but 00:17:57.479 --> 00:17:57.489 align:start position:0% sources so not original exchanges but 00:17:57.489 --> 00:17:59.489 align:start position:0% sources so not original exchanges but data<00:17:57.669> aggregators<00:17:58.179> that<00:17:58.690> take<00:17:58.839> on<00:17:59.019> the<00:17:59.469> the 00:17:59.489 --> 00:17:59.499 align:start position:0% data aggregators that take on the the 00:17:59.499 --> 00:18:01.349 align:start position:0% data aggregators that take on the the burden<00:17:59.979> of<00:18:00.249> making<00:18:00.639> sure<00:18:00.909> the<00:18:00.940> data<00:18:01.239> is 00:18:01.349 --> 00:18:01.359 align:start position:0% burden of making sure the data is 00:18:01.359 --> 00:18:04.229 align:start position:0% burden of making sure the data is correct<00:18:01.779> and<00:18:02.429> it's<00:18:03.429> a<00:18:03.549> civil<00:18:03.729> resistant 00:18:04.229 --> 00:18:04.239 align:start position:0% correct and it's a civil resistant 00:18:04.239 --> 00:18:05.669 align:start position:0% correct and it's a civil resistant network<00:18:04.509> because<00:18:04.869> we've<00:18:05.019> validated<00:18:05.589> these 00:18:05.669 --> 00:18:05.679 align:start position:0% network because we've validated these 00:18:05.679 --> 00:18:07.169 align:start position:0% network because we've validated these node<00:18:05.889> operators<00:18:06.309> over<00:18:06.580> the<00:18:06.789> course<00:18:06.969> of<00:18:07.089> a 00:18:07.169 --> 00:18:07.179 align:start position:0% node operators over the course of a 00:18:07.179 --> 00:18:09.180 align:start position:0% node operators over the course of a two-week<00:18:07.419> process<00:18:07.629> and<00:18:08.109> a<00:18:08.619> final<00:18:08.919> security 00:18:09.180 --> 00:18:09.190 align:start position:0% two-week process and a final security 00:18:09.190 --> 00:18:12.299 align:start position:0% two-week process and a final security interview<00:18:09.639> and<00:18:09.869> it's<00:18:10.869> also<00:18:11.219> you<00:18:12.219> know 00:18:12.299 --> 00:18:12.309 align:start position:0% interview and it's also you know 00:18:12.309 --> 00:18:14.219 align:start position:0% interview and it's also you know security<00:18:12.639> reviewed<00:18:13.119> in<00:18:13.239> many<00:18:13.719> other<00:18:13.929> forms 00:18:14.219 --> 00:18:14.229 align:start position:0% security reviewed in many other forms 00:18:14.229 --> 00:18:16.139 align:start position:0% security reviewed in many other forms like<00:18:14.320> the<00:18:14.559> ways<00:18:14.679> that<00:18:14.919> I<00:18:15.159> showed<00:18:15.609> you<00:18:15.759> so<00:18:15.940> even 00:18:16.139 --> 00:18:16.149 align:start position:0% like the ways that I showed you so even 00:18:16.149 --> 00:18:17.820 align:start position:0% like the ways that I showed you so even the<00:18:16.659> note<00:18:16.809> operators<00:18:17.259> I<00:18:17.409> showed<00:18:17.619> you<00:18:17.710> in<00:18:17.769> the 00:18:17.820 --> 00:18:17.830 align:start position:0% the note operators I showed you in the 00:18:17.830 --> 00:18:19.440 align:start position:0% the note operators I showed you in the previous<00:18:17.950> slide<00:18:18.339> with<00:18:18.580> all<00:18:18.700> that<00:18:18.789> detail<00:18:19.179> are 00:18:19.440 --> 00:18:19.450 align:start position:0% previous slide with all that detail are 00:18:19.450 --> 00:18:21.089 align:start position:0% previous slide with all that detail are the<00:18:19.960> ones<00:18:20.169> that<00:18:20.379> are<00:18:20.469> powering<00:18:20.649> a<00:18:20.830> network 00:18:21.089 --> 00:18:21.099 align:start position:0% the ones that are powering a network 00:18:21.099 --> 00:18:23.099 align:start position:0% the ones that are powering a network like<00:18:21.249> this<00:18:21.330> so<00:18:22.330> these<00:18:22.450> reference<00:18:22.929> data 00:18:23.099 --> 00:18:23.109 align:start position:0% like this so these reference data 00:18:23.109 --> 00:18:25.289 align:start position:0% like this so these reference data networks<00:18:23.469> are<00:18:23.589> actually<00:18:23.859> very<00:18:24.009> important<00:18:24.429> as 00:18:25.289 --> 00:18:25.299 align:start position:0% networks are actually very important as 00:18:25.299 --> 00:18:27.119 align:start position:0% networks are actually very important as you<00:18:25.509> can<00:18:25.659> see<00:18:25.839> you<00:18:26.019> can<00:18:26.169> dig<00:18:26.409> into<00:18:26.559> them<00:18:26.799> we 00:18:27.119 --> 00:18:27.129 align:start position:0% you can see you can dig into them we 00:18:27.129 --> 00:18:29.039 align:start position:0% you can see you can dig into them we encourage<00:18:27.460> you<00:18:27.609> to<00:18:27.700> go<00:18:27.879> and<00:18:28.119> and<00:18:28.330> and<00:18:28.539> and<00:18:28.809> and 00:18:29.039 --> 00:18:29.049 align:start position:0% encourage you to go and and and and and 00:18:29.049 --> 00:18:31.320 align:start position:0% encourage you to go and and and and and look<00:18:29.200> at<00:18:29.349> them<00:18:29.759> you<00:18:30.759> can<00:18:30.909> once<00:18:31.089> again<00:18:31.179> see 00:18:31.320 --> 00:18:31.330 align:start position:0% look at them you can once again see 00:18:31.330 --> 00:18:33.690 align:start position:0% look at them you can once again see exactly<00:18:31.929> what<00:18:32.080> they're<00:18:32.229> doing<00:18:32.259> and<00:18:32.679> and<00:18:33.549> this 00:18:33.690 --> 00:18:33.700 align:start position:0% exactly what they're doing and and this 00:18:33.700 --> 00:18:35.099 align:start position:0% exactly what they're doing and and this level<00:18:33.940> of<00:18:34.059> clarity<00:18:34.450> is<00:18:34.539> supposed<00:18:34.809> to<00:18:34.869> provide 00:18:35.099 --> 00:18:35.109 align:start position:0% level of clarity is supposed to provide 00:18:35.109 --> 00:18:36.719 align:start position:0% level of clarity is supposed to provide users<00:18:35.320> a<00:18:35.499> guarantee<00:18:36.009> that<00:18:36.219> the<00:18:36.339> reference 00:18:36.719 --> 00:18:36.729 align:start position:0% users a guarantee that the reference 00:18:36.729 --> 00:18:39.209 align:start position:0% users a guarantee that the reference data<00:18:36.999> on<00:18:37.210> this<00:18:37.479> network<00:18:37.899> is<00:18:38.139> reliable<00:18:39.009> enough 00:18:39.209 --> 00:18:39.219 align:start position:0% data on this network is reliable enough 00:18:39.219 --> 00:18:40.649 align:start position:0% data on this network is reliable enough to<00:18:39.429> trigger<00:18:39.639> their<00:18:39.849> hundreds<00:18:40.179> of<00:18:40.299> millions<00:18:40.570> of 00:18:40.649 --> 00:18:40.659 align:start position:0% to trigger their hundreds of millions of 00:18:40.659 --> 00:18:43.289 align:start position:0% to trigger their hundreds of millions of dollars<00:18:40.809> in<00:18:41.109> value<00:18:41.229> whereas<00:18:42.099> any<00:18:42.820> other<00:18:43.029> type 00:18:43.289 --> 00:18:43.299 align:start position:0% dollars in value whereas any other type 00:18:43.299 --> 00:18:44.609 align:start position:0% dollars in value whereas any other type of<00:18:43.450> reference<00:18:43.599> data<00:18:43.929> network<00:18:44.259> or<00:18:44.440> some 00:18:44.609 --> 00:18:44.619 align:start position:0% of reference data network or some 00:18:44.619 --> 00:18:46.109 align:start position:0% of reference data network or some centralized<00:18:45.070> Oracle<00:18:45.519> wouldn't<00:18:45.789> have<00:18:45.909> any<00:18:46.089> of 00:18:46.109 --> 00:18:46.119 align:start position:0% centralized Oracle wouldn't have any of 00:18:46.119 --> 00:18:48.029 align:start position:0% centralized Oracle wouldn't have any of this<00:18:46.299> information<00:18:46.599> you<00:18:47.080> wouldn't<00:18:47.739> have<00:18:47.859> any 00:18:48.029 --> 00:18:48.039 align:start position:0% this information you wouldn't have any 00:18:48.039 --> 00:18:51.299 align:start position:0% this information you wouldn't have any guarantees<00:18:48.519> that<00:18:49.440> this<00:18:50.440> Oracle<00:18:50.799> is<00:18:50.919> committed 00:18:51.299 --> 00:18:51.309 align:start position:0% guarantees that this Oracle is committed 00:18:51.309 --> 00:18:53.399 align:start position:0% guarantees that this Oracle is committed to<00:18:51.489> or<00:18:51.789> has<00:18:51.969> successfully<00:18:52.359> performed<00:18:53.259> its 00:18:53.399 --> 00:18:53.409 align:start position:0% to or has successfully performed its 00:18:53.409 --> 00:18:57.119 align:start position:0% to or has successfully performed its obligations<00:18:53.919> previously<00:18:55.349> we've<00:18:56.349> we've<00:18:56.950> had 00:18:57.119 --> 00:18:57.129 align:start position:0% obligations previously we've we've had 00:18:57.129 --> 00:18:59.579 align:start position:0% obligations previously we've we've had so<00:18:57.309> much<00:18:57.429> success<00:18:57.669> so<00:18:58.029> far<00:18:58.269> doing<00:18:58.929> this<00:18:59.200> and 00:18:59.579 --> 00:18:59.589 align:start position:0% so much success so far doing this and 00:18:59.589 --> 00:19:02.009 align:start position:0% so much success so far doing this and it's<00:18:59.889> it's<00:19:00.219> been<00:19:00.339> done<00:19:00.729> so<00:19:01.089> securely<00:19:01.509> all<00:19:01.690> over 00:19:02.009 --> 00:19:02.019 align:start position:0% it's it's been done so securely all over 00:19:02.019 --> 00:19:04.619 align:start position:0% it's it's been done so securely all over the<00:19:02.320> past<00:19:02.529> number<00:19:02.739> of<00:19:02.889> months<00:19:02.979> that<00:19:03.629> we've 00:19:04.619 --> 00:19:04.629 align:start position:0% the past number of months that we've 00:19:04.629 --> 00:19:07.259 align:start position:0% the past number of months that we've were<00:19:05.409> basically<00:19:05.739> committing<00:19:06.159> to<00:19:06.279> expand<00:19:06.789> the 00:19:07.259 --> 00:19:07.269 align:start position:0% were basically committing to expand the 00:19:07.269 --> 00:19:09.089 align:start position:0% were basically committing to expand the amount<00:19:07.359> of<00:19:07.509> reference<00:19:07.839> data<00:19:08.019> networks<00:19:08.379> these 00:19:09.089 --> 00:19:09.099 align:start position:0% amount of reference data networks these 00:19:09.099 --> 00:19:10.469 align:start position:0% amount of reference data networks these are<00:19:09.249> the<00:19:09.339> next<00:19:09.639> seven<00:19:09.969> reference<00:19:10.299> data 00:19:10.469 --> 00:19:10.479 align:start position:0% are the next seven reference data 00:19:10.479 --> 00:19:11.519 align:start position:0% are the next seven reference data networks<00:19:10.839> that<00:19:11.169> we're<00:19:11.259> going<00:19:11.349> to<00:19:11.409> be 00:19:11.519 --> 00:19:11.529 align:start position:0% networks that we're going to be 00:19:11.529 --> 00:19:16.529 align:start position:0% networks that we're going to be launching<00:19:12.239> bitcoin<00:19:13.239> dai<00:19:13.509> USD<00:19:14.320> c0x<00:19:15.219> rep<00:19:15.609> WB<00:19:16.210> TC 00:19:16.529 --> 00:19:16.539 align:start position:0% launching bitcoin dai USD c0x rep WB TC 00:19:16.539 --> 00:19:19.529 align:start position:0% launching bitcoin dai USD c0x rep WB TC and<00:19:16.690> and<00:19:16.929> bat<00:19:17.139> prices<00:19:17.710> these<00:19:18.519> prices<00:19:18.969> and<00:19:19.330> and 00:19:19.529 --> 00:19:19.539 align:start position:0% and and bat prices these prices and and 00:19:19.539 --> 00:19:21.570 align:start position:0% and and bat prices these prices and and feeds<00:19:19.809> were<00:19:20.019> chosen<00:19:20.289> based<00:19:20.710> on<00:19:21.009> the<00:19:21.219> needs<00:19:21.429> of 00:19:21.570 --> 00:19:21.580 align:start position:0% feeds were chosen based on the needs of 00:19:21.580 --> 00:19:23.669 align:start position:0% feeds were chosen based on the needs of our<00:19:21.669> users<00:19:22.029> and<00:19:22.149> customers<00:19:22.599> they're<00:19:23.259> meant<00:19:23.499> to 00:19:23.669 --> 00:19:23.679 align:start position:0% our users and customers they're meant to 00:19:23.679 --> 00:19:27.599 align:start position:0% our users and customers they're meant to service<00:19:24.809> systems<00:19:25.809> like<00:19:25.960> compound<00:19:26.609> partially 00:19:27.599 --> 00:19:27.609 align:start position:0% service systems like compound partially 00:19:27.609 --> 00:19:29.639 align:start position:0% service systems like compound partially synthetics<00:19:28.089> partially<00:19:28.479> other<00:19:28.599> systems<00:19:29.019> that 00:19:29.639 --> 00:19:29.649 align:start position:0% synthetics partially other systems that 00:19:29.649 --> 00:19:31.680 align:start position:0% synthetics partially other systems that are<00:19:29.889> going<00:19:29.919> to<00:19:30.159> be<00:19:30.249> building<00:19:30.669> their<00:19:31.119> contracts 00:19:31.680 --> 00:19:31.690 align:start position:0% are going to be building their contracts 00:19:31.690 --> 00:19:32.879 align:start position:0% are going to be building their contracts and<00:19:31.749> securing<00:19:32.169> their<00:19:32.289> value<00:19:32.559> using<00:19:32.799> these 00:19:32.879 --> 00:19:32.889 align:start position:0% and securing their value using these 00:19:32.889 --> 00:19:35.399 align:start position:0% and securing their value using these reference<00:19:33.279> data<00:19:33.460> networks<00:19:34.019> these<00:19:35.019> reference 00:19:35.399 --> 00:19:35.409 align:start position:0% reference data networks these reference 00:19:35.409 --> 00:19:36.839 align:start position:0% reference data networks these reference data<00:19:35.559> networks<00:19:35.950> are<00:19:36.099> once<00:19:36.309> again<00:19:36.549> I<00:19:36.669> mean 00:19:36.839 --> 00:19:36.849 align:start position:0% data networks are once again I mean 00:19:36.849 --> 00:19:38.969 align:start position:0% data networks are once again I mean they're<00:19:36.999> provided<00:19:37.389> free<00:19:37.570> by<00:19:37.599> us<00:19:37.869> if<00:19:38.289> somebody 00:19:38.969 --> 00:19:38.979 align:start position:0% they're provided free by us if somebody 00:19:38.979 --> 00:19:41.159 align:start position:0% they're provided free by us if somebody wants<00:19:39.249> to<00:19:39.279> add<00:19:39.489> security<00:19:39.940> to<00:19:40.210> them<00:19:40.389> we're 00:19:41.159 --> 00:19:41.169 align:start position:0% wants to add security to them we're 00:19:41.169 --> 00:19:42.299 align:start position:0% wants to add security to them we're going<00:19:41.289> to<00:19:41.379> be<00:19:41.440> releasing<00:19:41.710> information<00:19:41.919> about 00:19:42.299 --> 00:19:42.309 align:start position:0% going to be releasing information about 00:19:42.309 --> 00:19:44.099 align:start position:0% going to be releasing information about how<00:19:42.549> somebody<00:19:42.969> could<00:19:43.089> take<00:19:43.239> reference<00:19:43.929> data 00:19:44.099 --> 00:19:44.109 align:start position:0% how somebody could take reference data 00:19:44.109 --> 00:19:45.570 align:start position:0% how somebody could take reference data network<00:19:44.440> with<00:19:44.679> you<00:19:44.859> know<00:19:44.950> five<00:19:45.190> or<00:19:45.219> seven 00:19:45.570 --> 00:19:45.580 align:start position:0% network with you know five or seven 00:19:45.580 --> 00:19:47.700 align:start position:0% network with you know five or seven Oracle's<00:19:45.940> and<00:19:46.149> how<00:19:46.659> they<00:19:46.869> can<00:19:46.929> add<00:19:47.320> more 00:19:47.700 --> 00:19:47.710 align:start position:0% Oracle's and how they can add more 00:19:47.710 --> 00:19:49.289 align:start position:0% Oracle's and how they can add more Oracle's<00:19:48.219> to<00:19:48.369> that<00:19:48.489> reference<00:19:48.789> data<00:19:48.969> network 00:19:49.289 --> 00:19:49.299 align:start position:0% Oracle's to that reference data network 00:19:49.299 --> 00:19:51.029 align:start position:0% Oracle's to that reference data network in<00:19:49.719> case<00:19:49.989> they<00:19:50.200> start<00:19:50.259> using<00:19:50.679> it<00:19:50.889> and<00:19:50.919> they 00:19:51.029 --> 00:19:51.039 align:start position:0% in case they start using it and they 00:19:51.039 --> 00:19:52.739 align:start position:0% in case they start using it and they want<00:19:51.219> to<00:19:51.279> add<00:19:51.369> more<00:19:51.399> security<00:19:51.909> on<00:19:52.239> top<00:19:52.509> of<00:19:52.629> the 00:19:52.739 --> 00:19:52.749 align:start position:0% want to add more security on top of the 00:19:52.749 --> 00:19:55.560 align:start position:0% want to add more security on top of the initial<00:19:52.960> security<00:19:53.409> we<00:19:53.710> paid<00:19:53.919> for<00:19:54.129> but<00:19:55.089> we're 00:19:55.560 --> 00:19:55.570 align:start position:0% initial security we paid for but we're 00:19:55.570 --> 00:19:57.690 align:start position:0% initial security we paid for but we're we're<00:19:55.899> very<00:19:55.929> excited<00:19:56.169> to<00:19:56.769> be<00:19:57.249> giving<00:19:57.549> back<00:19:57.669> to 00:19:57.690 --> 00:19:57.700 align:start position:0% we're very excited to be giving back to 00:19:57.700 --> 00:19:59.700 align:start position:0% we're very excited to be giving back to the<00:19:57.909> community<00:19:58.320> because<00:19:59.320> the<00:19:59.409> etherium 00:19:59.700 --> 00:19:59.710 align:start position:0% the community because the etherium 00:19:59.710 --> 00:20:01.289 align:start position:0% the community because the etherium community<00:20:00.039> has<00:20:00.129> done<00:20:00.279> a<00:20:00.460> huge<00:20:00.700> amount<00:20:00.879> for<00:20:01.179> us 00:20:01.289 --> 00:20:01.299 align:start position:0% community has done a huge amount for us 00:20:01.299 --> 00:20:04.799 align:start position:0% community has done a huge amount for us and<00:20:01.769> where<00:20:02.769> we<00:20:03.759> think<00:20:03.940> that<00:20:04.119> the<00:20:04.179> capacity<00:20:04.779> to 00:20:04.799 --> 00:20:04.809 align:start position:0% and where we think that the capacity to 00:20:04.809 --> 00:20:07.469 align:start position:0% and where we think that the capacity to have<00:20:05.019> high<00:20:05.229> quality<00:20:05.289> data<00:20:05.859> on<00:20:06.039> chain<00:20:06.339> and<00:20:06.579> to 00:20:07.469 --> 00:20:07.479 align:start position:0% have high quality data on chain and to 00:20:07.479 --> 00:20:08.980 align:start position:0% have high quality data on chain and to make<00:20:07.599> it<00:20:07.719> extremely<00:20:07.989> usable<00:20:08.559> and<00:20:08.679> rely 00:20:08.980 --> 00:20:08.990 align:start position:0% make it extremely usable and rely 00:20:08.990 --> 00:20:11.500 align:start position:0% make it extremely usable and rely is<00:20:09.350> one<00:20:10.070> of<00:20:10.100> the<00:20:10.279> key<00:20:10.549> things<00:20:11.179> that<00:20:11.390> were 00:20:11.500 --> 00:20:11.510 align:start position:0% is one of the key things that were 00:20:11.510 --> 00:20:14.289 align:start position:0% is one of the key things that were kickstart<00:20:11.929> defy<00:20:12.260> and<00:20:12.590> so<00:20:13.370> right<00:20:13.970> now<00:20:14.120> we're 00:20:14.289 --> 00:20:14.299 align:start position:0% kickstart defy and so right now we're 00:20:14.299 --> 00:20:15.610 align:start position:0% kickstart defy and so right now we're committing<00:20:14.600> to<00:20:14.690> put<00:20:14.840> these<00:20:14.990> seven<00:20:15.289> networks 00:20:15.610 --> 00:20:15.620 align:start position:0% committing to put these seven networks 00:20:15.620 --> 00:20:17.049 align:start position:0% committing to put these seven networks out<00:20:15.830> because<00:20:16.190> we<00:20:16.460> know<00:20:16.669> they're<00:20:16.880> going<00:20:17.000> to 00:20:17.049 --> 00:20:17.059 align:start position:0% out because we know they're going to 00:20:17.059 --> 00:20:20.409 align:start position:0% out because we know they're going to successfully<00:20:17.390> service<00:20:18.429> you<00:20:19.429> know<00:20:19.940> existing 00:20:20.409 --> 00:20:20.419 align:start position:0% successfully service you know existing 00:20:20.419 --> 00:20:23.440 align:start position:0% successfully service you know existing users<00:20:20.720> and<00:20:20.840> customers<00:20:21.260> and<00:20:22.210> beyond<00:20:23.210> that<00:20:23.330> we 00:20:23.440 --> 00:20:23.450 align:start position:0% users and customers and beyond that we 00:20:23.450 --> 00:20:27.940 align:start position:0% users and customers and beyond that we plan<00:20:23.840> to<00:20:23.990> launch<00:20:24.110> many<00:20:24.440> more<00:20:26.200> in<00:20:27.200> in<00:20:27.559> that<00:20:27.710> vein 00:20:27.940 --> 00:20:27.950 align:start position:0% plan to launch many more in in that vein 00:20:27.950 --> 00:20:29.830 align:start position:0% plan to launch many more in in that vein if<00:20:28.190> you<00:20:28.340> if<00:20:28.549> you<00:20:28.669> have<00:20:28.789> a<00:20:28.880> deep<00:20:29.029> eye<00:20:29.149> project<00:20:29.630> if 00:20:29.830 --> 00:20:29.840 align:start position:0% if you if you have a deep eye project if 00:20:29.840 --> 00:20:32.500 align:start position:0% if you if you have a deep eye project if you<00:20:29.990> have<00:20:30.230> a<00:20:30.260> need<00:20:30.620> for<00:20:30.919> a<00:20:31.580> reference<00:20:32.330> data 00:20:32.500 --> 00:20:32.510 align:start position:0% you have a need for a reference data 00:20:32.510 --> 00:20:35.830 align:start position:0% you have a need for a reference data price<00:20:32.750> on<00:20:32.960> chain<00:20:33.700> we<00:20:34.700> we<00:20:35.210> want<00:20:35.390> to<00:20:35.480> support<00:20:35.750> you 00:20:35.830 --> 00:20:35.840 align:start position:0% price on chain we we want to support you 00:20:35.840 --> 00:20:37.930 align:start position:0% price on chain we we want to support you and<00:20:36.110> our<00:20:36.620> goal<00:20:36.860> as<00:20:37.010> a<00:20:37.039> company<00:20:37.130> is<00:20:37.520> actually<00:20:37.850> to 00:20:37.930 --> 00:20:37.940 align:start position:0% and our goal as a company is actually to 00:20:37.940 --> 00:20:40.360 align:start position:0% and our goal as a company is actually to make<00:20:38.090> our<00:20:38.240> users<00:20:38.480> succeed<00:20:39.080> by<00:20:39.740> giving<00:20:40.190> them 00:20:40.360 --> 00:20:40.370 align:start position:0% make our users succeed by giving them 00:20:40.370 --> 00:20:43.450 align:start position:0% make our users succeed by giving them access<00:20:40.669> to<00:20:41.090> this<00:20:41.179> reliable<00:20:41.659> data<00:20:42.039> so<00:20:43.039> our 00:20:43.450 --> 00:20:43.460 align:start position:0% access to this reliable data so our 00:20:43.460 --> 00:20:45.760 align:start position:0% access to this reliable data so our chain<00:20:44.029> link<00:20:44.210> is<00:20:44.299> basically<00:20:44.659> here<00:20:45.020> to<00:20:45.049> enable 00:20:45.760 --> 00:20:45.770 align:start position:0% chain link is basically here to enable 00:20:45.770 --> 00:20:48.490 align:start position:0% chain link is basically here to enable smart<00:20:46.669> contract<00:20:47.090> developers<00:20:47.570> to<00:20:48.110> build<00:20:48.260> any 00:20:48.490 --> 00:20:48.500 align:start position:0% smart contract developers to build any 00:20:48.500 --> 00:20:49.870 align:start position:0% smart contract developers to build any kind<00:20:48.620> of<00:20:48.890> externally<00:20:49.370> connected<00:20:49.789> or 00:20:49.870 --> 00:20:49.880 align:start position:0% kind of externally connected or 00:20:49.880 --> 00:20:52.570 align:start position:0% kind of externally connected or next-generation<00:20:50.270> contract<00:20:50.990> and<00:20:51.260> if<00:20:52.159> that's 00:20:52.570 --> 00:20:52.580 align:start position:0% next-generation contract and if that's 00:20:52.580 --> 00:20:55.000 align:start position:0% next-generation contract and if that's what<00:20:52.760> you're<00:20:52.880> doing<00:20:53.559> you<00:20:54.559> know<00:20:54.590> we're<00:20:54.860> very 00:20:55.000 --> 00:20:55.010 align:start position:0% what you're doing you know we're very 00:20:55.010 --> 00:20:56.620 align:start position:0% what you're doing you know we're very collaborative<00:20:55.279> very<00:20:55.850> helpful<00:20:56.149> people<00:20:56.299> we 00:20:56.620 --> 00:20:56.630 align:start position:0% collaborative very helpful people we 00:20:56.630 --> 00:20:58.180 align:start position:0% collaborative very helpful people we have<00:20:56.779> a<00:20:56.809> huge<00:20:57.110> integration<00:20:57.770> engineer<00:20:58.070> and 00:20:58.180 --> 00:20:58.190 align:start position:0% have a huge integration engineer and 00:20:58.190 --> 00:21:00.190 align:start position:0% have a huge integration engineer and support<00:20:58.490> engineering<00:20:58.820> staff<00:20:59.059> that<00:20:59.720> that<00:21:00.049> that 00:21:00.190 --> 00:21:00.200 align:start position:0% support engineering staff that that that 00:21:00.200 --> 00:21:01.299 align:start position:0% support engineering staff that that that is<00:21:00.350> there<00:21:00.500> to<00:21:00.649> help<00:21:00.770> you<00:21:00.980> build<00:21:01.100> these 00:21:01.299 --> 00:21:01.309 align:start position:0% is there to help you build these 00:21:01.309 --> 00:21:04.149 align:start position:0% is there to help you build these contracts<00:21:01.850> and<00:21:02.059> likewise<00:21:03.049> even<00:21:03.289> make<00:21:03.590> a<00:21:03.830> great 00:21:04.149 --> 00:21:04.159 align:start position:0% contracts and likewise even make a great 00:21:04.159 --> 00:21:06.850 align:start position:0% contracts and likewise even make a great reference<00:21:04.880> data<00:21:05.210> network<00:21:05.649> possibly<00:21:06.649> even 00:21:06.850 --> 00:21:06.860 align:start position:0% reference data network possibly even 00:21:06.860 --> 00:21:09.460 align:start position:0% reference data network possibly even even<00:21:07.190> starting<00:21:07.850> out<00:21:07.940> for<00:21:08.210> your<00:21:08.360> use<00:21:08.539> case<00:21:08.779> but 00:21:09.460 --> 00:21:09.470 align:start position:0% even starting out for your use case but 00:21:09.470 --> 00:21:11.740 align:start position:0% even starting out for your use case but then<00:21:09.590> getting<00:21:09.799> used<00:21:10.070> by<00:21:10.279> other<00:21:10.460> other<00:21:11.419> dphi 00:21:11.740 --> 00:21:11.750 align:start position:0% then getting used by other other dphi 00:21:11.750 --> 00:21:14.710 align:start position:0% then getting used by other other dphi projects<00:21:12.169> as<00:21:12.289> well<00:21:12.490> so<00:21:13.490> thank<00:21:14.029> you<00:21:14.179> thank<00:21:14.659> you 00:21:14.710 --> 00:21:14.720 align:start position:0% projects as well so thank you thank you 00:21:14.720 --> 00:21:16.990 align:start position:0% projects as well so thank you thank you very<00:21:14.779> much<00:21:15.110> and<00:21:15.440> I'm<00:21:15.860> looking<00:21:16.669> forward<00:21:16.850> to 00:21:16.990 --> 00:21:17.000 align:start position:0% very much and I'm looking forward to 00:21:17.000 --> 00:21:18.669 align:start position:0% very much and I'm looking forward to seeing<00:21:17.179> you<00:21:17.299> all<00:21:17.330> at<00:21:17.539> the<00:21:17.779> conference<00:21:18.169> thank 00:21:18.669 --> 00:21:18.679 align:start position:0% seeing you all at the conference thank 00:21:18.679 --> 00:21:28.490 align:start position:0% seeing you all at the conference thank you 00:21:28.490 --> 00:21:28.500 align:start position:0% 00:21:28.500 --> 00:21:30.560 align:start position:0% you