WEBVTT Kind: captions Language: en 00:00:04.979 --> 00:00:08.369 align:start position:0% hello<00:00:05.979> everyone<00:00:06.540> thank<00:00:07.540> you<00:00:07.599> for<00:00:07.839> having<00:00:08.109> me 00:00:08.369 --> 00:00:08.379 align:start position:0% hello everyone thank you for having me 00:00:08.379 --> 00:00:08.970 align:start position:0% hello everyone thank you for having me here<00:00:08.410> today 00:00:08.970 --> 00:00:08.980 align:start position:0% here today 00:00:08.980 --> 00:00:11.339 align:start position:0% here today my<00:00:09.430> name<00:00:09.580> is<00:00:09.700> Thomas<00:00:10.030> I'm<00:00:10.389> the<00:00:10.690> CEO<00:00:11.170> and 00:00:11.339 --> 00:00:11.349 align:start position:0% my name is Thomas I'm the CEO and 00:00:11.349 --> 00:00:15.749 align:start position:0% my name is Thomas I'm the CEO and founder<00:00:11.410> of<00:00:12.299> provable<00:00:14.099> provable<00:00:15.099> is<00:00:15.339> a 00:00:15.749 --> 00:00:15.759 align:start position:0% founder of provable provable is a 00:00:15.759 --> 00:00:17.550 align:start position:0% founder of provable provable is a blockchain<00:00:16.180> Oracle<00:00:16.689> service<00:00:17.020> that<00:00:17.169> has<00:00:17.349> been 00:00:17.550 --> 00:00:17.560 align:start position:0% blockchain Oracle service that has been 00:00:17.560 --> 00:00:19.260 align:start position:0% blockchain Oracle service that has been operating<00:00:17.919> in<00:00:18.250> the<00:00:18.430> tearoom<00:00:18.669> space<00:00:18.939> since 00:00:19.260 --> 00:00:19.270 align:start position:0% operating in the tearoom space since 00:00:19.270 --> 00:00:20.220 align:start position:0% operating in the tearoom space since 2015 00:00:20.220 --> 00:00:20.230 align:start position:0% 2015 00:00:20.230 --> 00:00:22.470 align:start position:0% 2015 so<00:00:20.890> duties<00:00:21.220> during<00:00:21.610> this<00:00:21.700> presentation<00:00:22.029> I 00:00:22.470 --> 00:00:22.480 align:start position:0% so duties during this presentation I 00:00:22.480 --> 00:00:24.839 align:start position:0% so duties during this presentation I will<00:00:23.020> show<00:00:23.290> you<00:00:23.349> what<00:00:24.160> is<00:00:24.279> the<00:00:24.430> trust<00:00:24.669> model 00:00:24.839 --> 00:00:24.849 align:start position:0% will show you what is the trust model 00:00:24.849 --> 00:00:27.990 align:start position:0% will show you what is the trust model that<00:00:25.540> we<00:00:25.840> are<00:00:26.169> using<00:00:26.230> with<00:00:27.099> our<00:00:27.430> Oracle 00:00:27.990 --> 00:00:28.000 align:start position:0% that we are using with our Oracle 00:00:28.000 --> 00:00:30.780 align:start position:0% that we are using with our Oracle service<00:00:28.300> and<00:00:29.070> we<00:00:30.070> try<00:00:30.250> to<00:00:30.309> understand<00:00:30.700> what 00:00:30.780 --> 00:00:30.790 align:start position:0% service and we try to understand what 00:00:30.790 --> 00:00:32.729 align:start position:0% service and we try to understand what are<00:00:30.820> the<00:00:30.939> trust<00:00:31.180> implications<00:00:31.750> and<00:00:31.930> what's 00:00:32.729 --> 00:00:32.739 align:start position:0% are the trust implications and what's 00:00:32.739 --> 00:00:34.560 align:start position:0% are the trust implications and what's the<00:00:32.890> challenge<00:00:33.309> behind<00:00:33.670> the<00:00:34.059> you<00:00:34.480> know 00:00:34.560 --> 00:00:34.570 align:start position:0% the challenge behind the you know 00:00:34.570 --> 00:00:38.280 align:start position:0% the challenge behind the you know designing<00:00:35.020> of<00:00:35.320> social<00:00:35.920> services<00:00:36.520> and<00:00:37.140> in<00:00:38.140> the 00:00:38.280 --> 00:00:38.290 align:start position:0% designing of social services and in the 00:00:38.290 --> 00:00:41.370 align:start position:0% designing of social services and in the last<00:00:38.470> part<00:00:38.650> I<00:00:38.920> will<00:00:39.220> like<00:00:40.030> introduce<00:00:40.660> a<00:00:40.870> new 00:00:41.370 --> 00:00:41.380 align:start position:0% last part I will like introduce a new 00:00:41.380 --> 00:00:43.800 align:start position:0% last part I will like introduce a new project<00:00:41.740> based<00:00:42.190> on<00:00:42.460> the<00:00:43.030> same<00:00:43.240> trans<00:00:43.510> model 00:00:43.800 --> 00:00:43.810 align:start position:0% project based on the same trans model 00:00:43.810 --> 00:00:47.160 align:start position:0% project based on the same trans model which<00:00:44.170> is<00:00:44.410> called<00:00:44.710> the<00:00:44.860> P<00:00:45.160> tokens<00:00:45.550> and<00:00:45.990> this<00:00:46.990> is 00:00:47.160 --> 00:00:47.170 align:start position:0% which is called the P tokens and this is 00:00:47.170 --> 00:00:50.819 align:start position:0% which is called the P tokens and this is basically<00:00:47.470> a<00:00:47.770> two-way<00:00:48.310> peg<00:00:48.579> for<00:00:49.590> tokens<00:00:50.590> which 00:00:50.819 --> 00:00:50.829 align:start position:0% basically a two-way peg for tokens which 00:00:50.829 --> 00:00:52.470 align:start position:0% basically a two-way peg for tokens which are<00:00:51.010> native<00:00:51.190> to<00:00:51.489> one<00:00:51.640> blockchain<00:00:52.060> so<00:00:52.239> that<00:00:52.360> we 00:00:52.470 --> 00:00:52.480 align:start position:0% are native to one blockchain so that we 00:00:52.480 --> 00:00:54.210 align:start position:0% are native to one blockchain so that we can<00:00:52.660> use<00:00:52.840> them<00:00:53.050> like<00:00:53.320> on<00:00:53.500> a<00:00:53.530> theorem<00:00:53.829> or<00:00:53.950> on 00:00:54.210 --> 00:00:54.220 align:start position:0% can use them like on a theorem or on 00:00:54.220 --> 00:00:57.000 align:start position:0% can use them like on a theorem or on other<00:00:54.370> blockchain<00:00:55.470> so<00:00:56.470> let's<00:00:56.649> start<00:00:56.829> with 00:00:57.000 --> 00:00:57.010 align:start position:0% other blockchain so let's start with 00:00:57.010 --> 00:00:59.460 align:start position:0% other blockchain so let's start with like<00:00:57.640> a<00:00:57.670> brief<00:00:57.940> introduction<00:00:58.360> to<00:00:58.989> understand 00:00:59.460 --> 00:00:59.470 align:start position:0% like a brief introduction to understand 00:00:59.470 --> 00:01:02.400 align:start position:0% like a brief introduction to understand the<00:00:59.790> like<00:01:00.790> some<00:01:01.120> terms<00:01:01.750> that<00:01:02.050> we<00:01:02.170> will<00:01:02.290> be 00:01:02.400 --> 00:01:02.410 align:start position:0% the like some terms that we will be 00:01:02.410 --> 00:01:05.550 align:start position:0% the like some terms that we will be using<00:01:02.670> during<00:01:03.670> the<00:01:03.880> presentation<00:01:04.360> so<00:01:04.560> the 00:01:05.550 --> 00:01:05.560 align:start position:0% using during the presentation so the 00:01:05.560 --> 00:01:07.170 align:start position:0% using during the presentation so the three<00:01:05.860> entities<00:01:06.189> we<00:01:06.490> are<00:01:06.520> interested<00:01:06.909> in<00:01:07.030> are 00:01:07.170 --> 00:01:07.180 align:start position:0% three entities we are interested in are 00:01:07.180 --> 00:01:11.370 align:start position:0% three entities we are interested in are basically<00:01:08.039> the<00:01:09.039> data<00:01:09.909> source<00:01:10.210> which<00:01:10.659> is<00:01:10.869> like 00:01:11.370 --> 00:01:11.380 align:start position:0% basically the data source which is like 00:01:11.380 --> 00:01:14.129 align:start position:0% basically the data source which is like a<00:01:11.409> Web<00:01:11.799> API<00:01:11.829> or<00:01:12.549> a<00:01:13.060> source<00:01:13.329> for<00:01:13.509> external<00:01:13.810> data 00:01:14.129 --> 00:01:14.139 align:start position:0% a Web API or a source for external data 00:01:14.139 --> 00:01:16.410 align:start position:0% a Web API or a source for external data that<00:01:14.439> doesn't<00:01:14.740> live<00:01:14.859> on<00:01:14.950> the<00:01:15.069> blockchain<00:01:15.420> then 00:01:16.410 --> 00:01:16.420 align:start position:0% that doesn't live on the blockchain then 00:01:16.420 --> 00:01:18.239 align:start position:0% that doesn't live on the blockchain then we<00:01:16.569> have<00:01:16.689> the<00:01:16.840> application<00:01:17.380> which<00:01:17.710> typically 00:01:18.239 --> 00:01:18.249 align:start position:0% we have the application which typically 00:01:18.249 --> 00:01:20.580 align:start position:0% we have the application which typically will<00:01:18.429> be<00:01:18.579> a<00:01:18.609> smart<00:01:18.999> contract<00:01:19.210> and<00:01:19.600> we<00:01:20.319> have<00:01:20.409> the 00:01:20.580 --> 00:01:20.590 align:start position:0% will be a smart contract and we have the 00:01:20.590 --> 00:01:23.190 align:start position:0% will be a smart contract and we have the Oracle<00:01:20.979> which<00:01:21.369> is<00:01:21.579> this<00:01:21.850> like<00:01:22.630> new 00:01:23.190 --> 00:01:23.200 align:start position:0% Oracle which is this like new 00:01:23.200 --> 00:01:25.590 align:start position:0% Oracle which is this like new intermediary<00:01:23.829> in<00:01:24.369> a<00:01:24.609> word<00:01:24.819> that<00:01:25.119> is<00:01:25.240> trying<00:01:25.509> to 00:01:25.590 --> 00:01:25.600 align:start position:0% intermediary in a word that is trying to 00:01:25.600 --> 00:01:28.440 align:start position:0% intermediary in a word that is trying to get<00:01:25.780> rid<00:01:25.990> of<00:01:26.020> intermediaries<00:01:26.679> right<00:01:27.240> so<00:01:28.240> why 00:01:28.440 --> 00:01:28.450 align:start position:0% get rid of intermediaries right so why 00:01:28.450 --> 00:01:30.809 align:start position:0% get rid of intermediaries right so why do<00:01:28.509> we<00:01:28.689> need<00:01:28.929> like<00:01:29.380> an<00:01:29.740> Oracle<00:01:30.219> to<00:01:30.399> reach<00:01:30.639> out 00:01:30.809 --> 00:01:30.819 align:start position:0% do we need like an Oracle to reach out 00:01:30.819 --> 00:01:33.449 align:start position:0% do we need like an Oracle to reach out to<00:01:30.850> external<00:01:31.179> data<00:01:31.509> well<00:01:32.139> this<00:01:32.319> is<00:01:32.469> because<00:01:33.340> of 00:01:33.449 --> 00:01:33.459 align:start position:0% to external data well this is because of 00:01:33.459 --> 00:01:35.969 align:start position:0% to external data well this is because of the<00:01:33.609> way<00:01:33.759> the<00:01:34.179> blushin<00:01:34.630> works<00:01:34.840> so<00:01:35.740> it's<00:01:35.889> not 00:01:35.969 --> 00:01:35.979 align:start position:0% the way the blushin works so it's not 00:01:35.979 --> 00:01:39.599 align:start position:0% the way the blushin works so it's not possible<00:01:36.219> to<00:01:36.729> reach<00:01:37.119> out<00:01:37.329> to<00:01:38.310> like<00:01:39.310> the 00:01:39.599 --> 00:01:39.609 align:start position:0% possible to reach out to like the 00:01:39.609 --> 00:01:41.760 align:start position:0% possible to reach out to like the internet<00:01:40.029> from<00:01:40.329> within<00:01:40.539> the<00:01:40.749> blockchain<00:01:41.170> so 00:01:41.760 --> 00:01:41.770 align:start position:0% internet from within the blockchain so 00:01:41.770 --> 00:01:44.219 align:start position:0% internet from within the blockchain so the<00:01:42.189> or<00:01:42.310> core<00:01:42.549> somehow<00:01:42.789> enables<00:01:43.389> that<00:01:43.539> we<00:01:43.990> see 00:01:44.219 --> 00:01:44.229 align:start position:0% the or core somehow enables that we see 00:01:44.229 --> 00:01:46.469 align:start position:0% the or core somehow enables that we see later<00:01:44.380> how<00:01:44.799> this<00:01:45.310> is<00:01:45.429> possible<00:01:45.579> but<00:01:46.270> the 00:01:46.469 --> 00:01:46.479 align:start position:0% later how this is possible but the 00:01:46.479 --> 00:01:48.089 align:start position:0% later how this is possible but the Oracle<00:01:46.689> is<00:01:46.899> basically<00:01:47.289> an<00:01:47.439> actor<00:01:47.799> that 00:01:48.089 --> 00:01:48.099 align:start position:0% Oracle is basically an actor that 00:01:48.099 --> 00:01:49.919 align:start position:0% Oracle is basically an actor that operates<00:01:48.549> on<00:01:48.729> the<00:01:48.819> blockchain<00:01:49.029> but<00:01:49.599> he's<00:01:49.749> also 00:01:49.919 --> 00:01:49.929 align:start position:0% operates on the blockchain but he's also 00:01:49.929 --> 00:01:52.199 align:start position:0% operates on the blockchain but he's also capable<00:01:50.229> somehow<00:01:50.859> to<00:01:50.920> reach<00:01:51.219> out<00:01:51.369> outside<00:01:51.759> to 00:01:52.199 --> 00:01:52.209 align:start position:0% capable somehow to reach out outside to 00:01:52.209 --> 00:01:54.449 align:start position:0% capable somehow to reach out outside to the<00:01:52.329> data<00:01:52.479> source<00:01:52.859> so<00:01:53.859> as<00:01:53.979> you<00:01:54.130> see<00:01:54.279> already 00:01:54.449 --> 00:01:54.459 align:start position:0% the data source so as you see already 00:01:54.459 --> 00:01:57.419 align:start position:0% the data source so as you see already here<00:01:54.880> the<00:01:55.869> data<00:01:56.049> source<00:01:56.349> is<00:01:56.499> always<00:01:57.009> to<00:01:57.279> be 00:01:57.419 --> 00:01:57.429 align:start position:0% here the data source is always to be 00:01:57.429 --> 00:02:01.709 align:start position:0% here the data source is always to be trusted<00:01:58.060> because<00:01:59.049> the<00:01:59.679> data<00:02:00.029> in<00:02:01.029> general<00:02:01.479> is 00:02:01.709 --> 00:02:01.719 align:start position:0% trusted because the data in general is 00:02:01.719 --> 00:02:04.859 align:start position:0% trusted because the data in general is something<00:02:01.929> inherently<00:02:02.709> trusted<00:02:03.340> like<00:02:03.880> if<00:02:04.450> we 00:02:04.859 --> 00:02:04.869 align:start position:0% something inherently trusted like if we 00:02:04.869 --> 00:02:07.289 align:start position:0% something inherently trusted like if we have<00:02:05.259> a<00:02:05.289> smart<00:02:05.709> contract<00:02:05.919> that<00:02:06.429> needs<00:02:07.119> to 00:02:07.289 --> 00:02:07.299 align:start position:0% have a smart contract that needs to 00:02:07.299 --> 00:02:10.650 align:start position:0% have a smart contract that needs to release<00:02:07.659> a<00:02:08.020> payment<00:02:08.740> when<00:02:09.550> you<00:02:10.209> know<00:02:10.300> given 00:02:10.650 --> 00:02:10.660 align:start position:0% release a payment when you know given 00:02:10.660 --> 00:02:14.369 align:start position:0% release a payment when you know given flight<00:02:10.869> is<00:02:11.050> late<00:02:11.260> or<00:02:11.650> if<00:02:12.130> the<00:02:12.459> temperature<00:02:13.379> is 00:02:14.369 --> 00:02:14.379 align:start position:0% flight is late or if the temperature is 00:02:14.379 --> 00:02:18.660 align:start position:0% flight is late or if the temperature is reaching<00:02:14.920> a<00:02:15.069> some<00:02:15.970> degrees<00:02:16.480> or<00:02:16.950> like<00:02:17.950> if 00:02:18.660 --> 00:02:18.670 align:start position:0% reaching a some degrees or like if 00:02:18.670 --> 00:02:20.610 align:start position:0% reaching a some degrees or like if number<00:02:18.940> of<00:02:19.030> views<00:02:19.330> of<00:02:19.510> a<00:02:19.540> YouTube<00:02:19.990> video<00:02:20.170> go 00:02:20.610 --> 00:02:20.620 align:start position:0% number of views of a YouTube video go 00:02:20.620 --> 00:02:23.280 align:start position:0% number of views of a YouTube video go above<00:02:20.950> a<00:02:21.160> certain<00:02:21.610> limit<00:02:22.000> then<00:02:22.840> we<00:02:22.870> always 00:02:23.280 --> 00:02:23.290 align:start position:0% above a certain limit then we always 00:02:23.290 --> 00:02:26.280 align:start position:0% above a certain limit then we always have<00:02:23.830> like<00:02:24.340> a<00:02:24.370> third<00:02:24.670> party<00:02:25.209> that<00:02:25.569> is<00:02:25.780> like 00:02:26.280 --> 00:02:26.290 align:start position:0% have like a third party that is like 00:02:26.290 --> 00:02:28.920 align:start position:0% have like a third party that is like claiming<00:02:26.830> what<00:02:27.040> the<00:02:27.250> correct<00:02:27.780> answer<00:02:28.780> to 00:02:28.920 --> 00:02:28.930 align:start position:0% claiming what the correct answer to 00:02:28.930 --> 00:02:31.979 align:start position:0% claiming what the correct answer to those<00:02:29.050> questions<00:02:29.110> is<00:02:29.620> so<00:02:30.280> one<00:02:30.970> example<00:02:31.270> for 00:02:31.979 --> 00:02:31.989 align:start position:0% those questions is so one example for 00:02:31.989 --> 00:02:34.080 align:start position:0% those questions is so one example for the<00:02:32.170> number<00:02:32.470> of<00:02:32.590> like<00:02:33.130> views<00:02:33.489> for<00:02:33.700> a<00:02:33.760> YouTube 00:02:34.080 --> 00:02:34.090 align:start position:0% the number of like views for a YouTube 00:02:34.090 --> 00:02:37.440 align:start position:0% the number of like views for a YouTube video<00:02:34.209> is<00:02:34.569> that<00:02:35.140> YouTube<00:02:35.860> is<00:02:36.069> the<00:02:36.220> one<00:02:36.730> telling 00:02:37.440 --> 00:02:37.450 align:start position:0% video is that YouTube is the one telling 00:02:37.450 --> 00:02:39.809 align:start position:0% video is that YouTube is the one telling us<00:02:37.660> how<00:02:38.020> many<00:02:38.350> views<00:02:38.620> the<00:02:38.800> video<00:02:38.890> has<00:02:39.280> and<00:02:39.580> we 00:02:39.809 --> 00:02:39.819 align:start position:0% us how many views the video has and we 00:02:39.819 --> 00:02:41.460 align:start position:0% us how many views the video has and we have<00:02:39.910> no<00:02:40.060> way<00:02:40.239> to<00:02:40.270> independently<00:02:40.959> verify<00:02:41.290> that 00:02:41.460 --> 00:02:41.470 align:start position:0% have no way to independently verify that 00:02:41.470 --> 00:02:44.430 align:start position:0% have no way to independently verify that so<00:02:41.950> we<00:02:42.100> always<00:02:42.280> need<00:02:42.640> to<00:02:42.670> trust<00:02:43.030> YouTube<00:02:44.020> in 00:02:44.430 --> 00:02:44.440 align:start position:0% so we always need to trust YouTube in 00:02:44.440 --> 00:02:47.160 align:start position:0% so we always need to trust YouTube in the<00:02:44.620> same<00:02:44.800> way<00:02:44.980> if<00:02:45.280> we<00:02:45.459> if<00:02:45.880> I<00:02:46.060> was<00:02:46.360> asking<00:02:47.019> you 00:02:47.160 --> 00:02:47.170 align:start position:0% the same way if we if I was asking you 00:02:47.170 --> 00:02:48.900 align:start position:0% the same way if we if I was asking you like<00:02:47.560> what's<00:02:47.800> the<00:02:47.890> temperature<00:02:48.160> here<00:02:48.610> today 00:02:48.900 --> 00:02:48.910 align:start position:0% like what's the temperature here today 00:02:48.910 --> 00:02:50.640 align:start position:0% like what's the temperature here today I'm<00:02:49.330> sure<00:02:49.599> I<00:02:49.630> will<00:02:49.810> get<00:02:50.110> different<00:02:50.380> answers 00:02:50.640 --> 00:02:50.650 align:start position:0% I'm sure I will get different answers 00:02:50.650 --> 00:02:52.830 align:start position:0% I'm sure I will get different answers but<00:02:50.890> most<00:02:51.310> of<00:02:51.430> you<00:02:51.580> will<00:02:51.610> probably<00:02:52.150> look<00:02:52.600> for 00:02:52.830 --> 00:02:52.840 align:start position:0% but most of you will probably look for 00:02:52.840 --> 00:02:54.660 align:start position:0% but most of you will probably look for the<00:02:52.930> first<00:02:53.170> results<00:02:53.560> on<00:02:53.650> Google<00:02:53.980> and<00:02:54.160> the 00:02:54.660 --> 00:02:54.670 align:start position:0% the first results on Google and the 00:02:54.670 --> 00:02:57.240 align:start position:0% the first results on Google and the reality<00:02:55.060> is<00:02:55.090> that<00:02:55.269> we<00:02:55.660> don't<00:02:55.690> know<00:02:55.989> like<00:02:56.680> the 00:02:57.240 --> 00:02:57.250 align:start position:0% reality is that we don't know like the 00:02:57.250 --> 00:02:59.610 align:start position:0% reality is that we don't know like the precision<00:02:57.640> that<00:02:58.000> we<00:02:58.150> are<00:02:58.330> looking<00:02:58.420> for<00:02:58.840> as<00:02:59.019> for 00:02:59.610 --> 00:02:59.620 align:start position:0% precision that we are looking for as for 00:02:59.620 --> 00:03:01.080 align:start position:0% precision that we are looking for as for the<00:02:59.739> this<00:03:00.040> data<00:03:00.250> we<00:03:00.489> don't<00:03:00.580> know<00:03:00.700> the<00:03:00.760> exact 00:03:01.080 --> 00:03:01.090 align:start position:0% the this data we don't know the exact 00:03:01.090 --> 00:03:03.960 align:start position:0% the this data we don't know the exact location<00:03:01.650> so<00:03:02.650> you<00:03:02.950> know<00:03:03.069> the<00:03:03.310> data<00:03:03.549> source<00:03:03.850> is 00:03:03.960 --> 00:03:03.970 align:start position:0% location so you know the data source is 00:03:03.970 --> 00:03:05.640 align:start position:0% location so you know the data source is always<00:03:04.150> making<00:03:04.600> some<00:03:04.750> assumptions<00:03:05.200> so<00:03:05.500> we 00:03:05.640 --> 00:03:05.650 align:start position:0% always making some assumptions so we 00:03:05.650 --> 00:03:08.009 align:start position:0% always making some assumptions so we need<00:03:05.799> to<00:03:05.920> trust<00:03:06.160> the<00:03:06.330> the<00:03:07.330> data<00:03:07.510> source<00:03:07.840> for 00:03:08.009 --> 00:03:08.019 align:start position:0% need to trust the the data source for 00:03:08.019 --> 00:03:10.410 align:start position:0% need to trust the the data source for the<00:03:08.470> data's<00:03:08.709> providing<00:03:09.190> is<00:03:09.280> like<00:03:09.459> the<00:03:09.819> data<00:03:10.030> we 00:03:10.410 --> 00:03:10.420 align:start position:0% the data's providing is like the data we 00:03:10.420 --> 00:03:13.130 align:start position:0% the data's providing is like the data we are<00:03:10.450> pushing<00:03:10.780> to<00:03:11.019> the<00:03:11.049> blockchain<00:03:11.350> is<00:03:11.700> always 00:03:13.130 --> 00:03:13.140 align:start position:0% are pushing to the blockchain is always 00:03:13.140 --> 00:03:18.140 align:start position:0% are pushing to the blockchain is always like<00:03:14.140> a<00:03:14.500> claim<00:03:14.890> coming<00:03:15.310> from<00:03:15.430> the<00:03:15.580> data<00:03:15.730> source 00:03:18.140 --> 00:03:18.150 align:start position:0% 00:03:18.150 --> 00:03:28.140 align:start position:0% yes<00:03:19.150> sorry<00:03:24.299> so<00:03:26.250> as<00:03:27.250> I<00:03:27.760> said<00:03:27.910> we<00:03:28.030> have<00:03:28.120> been 00:03:28.140 --> 00:03:28.150 align:start position:0% yes sorry so as I said we have been 00:03:28.150 --> 00:03:29.819 align:start position:0% yes sorry so as I said we have been around<00:03:28.450> for<00:03:28.600> a<00:03:28.660> while<00:03:28.810> so<00:03:29.109> this<00:03:29.230> enabled<00:03:29.650> us<00:03:29.799> to 00:03:29.819 --> 00:03:29.829 align:start position:0% around for a while so this enabled us to 00:03:29.829 --> 00:03:32.039 align:start position:0% around for a while so this enabled us to collect<00:03:30.280> some<00:03:30.430> interesting<00:03:30.790> data<00:03:30.910> the<00:03:31.900> data 00:03:32.039 --> 00:03:32.049 align:start position:0% collect some interesting data the data 00:03:32.049 --> 00:03:34.229 align:start position:0% collect some interesting data the data you<00:03:32.200> can<00:03:32.230> see<00:03:32.380> here<00:03:32.859> it's<00:03:33.220> quite<00:03:33.579> small<00:03:33.970> but 00:03:34.229 --> 00:03:34.239 align:start position:0% you can see here it's quite small but 00:03:34.239 --> 00:03:37.229 align:start position:0% you can see here it's quite small but they<00:03:34.390> will<00:03:34.540> help<00:03:34.750> you<00:03:34.930> to<00:03:35.670> to<00:03:36.670> understand<00:03:37.090> it 00:03:37.229 --> 00:03:37.239 align:start position:0% they will help you to to understand it 00:03:37.239 --> 00:03:41.460 align:start position:0% they will help you to to understand it so<00:03:37.650> over<00:03:38.650> the<00:03:39.340> last<00:03:39.459> like<00:03:40.209> four<00:03:40.420> years<00:03:40.480> we<00:03:41.350> have 00:03:41.460 --> 00:03:41.470 align:start position:0% so over the last like four years we have 00:03:41.470 --> 00:03:43.949 align:start position:0% so over the last like four years we have processed<00:03:42.010> over<00:03:42.280> 1<00:03:42.820> million<00:03:43.060> transactions<00:03:43.780> on 00:03:43.949 --> 00:03:43.959 align:start position:0% processed over 1 million transactions on 00:03:43.959 --> 00:03:45.630 align:start position:0% processed over 1 million transactions on the<00:03:44.200> T<00:03:44.290> domain<00:03:44.410> net<00:03:44.769> asking<00:03:45.250> for<00:03:45.400> external 00:03:45.630 --> 00:03:45.640 align:start position:0% the T domain net asking for external 00:03:45.640 --> 00:03:48.210 align:start position:0% the T domain net asking for external data<00:03:46.000> and<00:03:46.299> if<00:03:47.019> you<00:03:47.109> look<00:03:47.260> on<00:03:47.350> github<00:03:47.829> there<00:03:48.070> are 00:03:48.210 --> 00:03:48.220 align:start position:0% data and if you look on github there are 00:03:48.220 --> 00:03:51.539 align:start position:0% data and if you look on github there are approximately<00:03:49.060> 1,000<00:03:49.870> Gita<00:03:50.799> open<00:03:51.310> source 00:03:51.539 --> 00:03:51.549 align:start position:0% approximately 1,000 Gita open source 00:03:51.549 --> 00:03:54.990 align:start position:0% approximately 1,000 Gita open source smart<00:03:52.299> contracts<00:03:52.750> that<00:03:53.470> are<00:03:53.859> basically<00:03:54.430> using 00:03:54.990 --> 00:03:55.000 align:start position:0% smart contracts that are basically using 00:03:55.000 --> 00:03:56.940 align:start position:0% smart contracts that are basically using the<00:03:55.359> Oracle<00:03:55.570> service<00:03:55.989> so<00:03:56.410> we<00:03:56.590> have<00:03:56.680> like 00:03:56.940 --> 00:03:56.950 align:start position:0% the Oracle service so we have like 00:03:56.950 --> 00:03:59.190 align:start position:0% the Oracle service so we have like process<00:03:57.430> this<00:03:57.549> data<00:03:57.609> to<00:03:58.239> understand<00:03:58.630> what 00:03:59.190 --> 00:03:59.200 align:start position:0% process this data to understand what 00:03:59.200 --> 00:04:02.069 align:start position:0% process this data to understand what those<00:03:59.470> contracts<00:04:00.220> do<00:04:00.430> but<00:04:01.090> they're<00:04:01.569> like 00:04:02.069 --> 00:04:02.079 align:start position:0% those contracts do but they're like 00:04:02.079 --> 00:04:05.280 align:start position:0% those contracts do but they're like field<00:04:02.940> and<00:04:03.940> basically<00:04:04.150> what<00:04:04.510> we<00:04:04.630> found<00:04:04.660> out<00:04:05.019> is 00:04:05.280 --> 00:04:05.290 align:start position:0% field and basically what we found out is 00:04:05.290 --> 00:04:07.680 align:start position:0% field and basically what we found out is that<00:04:05.799> of<00:04:06.220> course<00:04:06.670> there<00:04:06.790> is<00:04:06.880> a<00:04:06.910> lot<00:04:07.090> around<00:04:07.329> you 00:04:07.680 --> 00:04:07.690 align:start position:0% that of course there is a lot around you 00:04:07.690 --> 00:04:12.090 align:start position:0% that of course there is a lot around you know<00:04:07.780> D<00:04:07.930> Phi<00:04:08.109> so<00:04:08.709> a<00:04:09.700> certain<00:04:10.420> tokens<00:04:10.930> or<00:04:11.230> you 00:04:12.090 --> 00:04:12.100 align:start position:0% know D Phi so a certain tokens or you 00:04:12.100 --> 00:04:14.520 align:start position:0% know D Phi so a certain tokens or you know<00:04:12.220> I<00:04:12.400> cos<00:04:12.790> that<00:04:13.120> needs<00:04:13.390> to<00:04:13.600> check<00:04:14.140> a<00:04:14.200> price 00:04:14.520 --> 00:04:14.530 align:start position:0% know I cos that needs to check a price 00:04:14.530 --> 00:04:16.379 align:start position:0% know I cos that needs to check a price feed<00:04:14.859> because<00:04:15.459> maybe<00:04:15.639> they<00:04:15.819> wants<00:04:16.060> to<00:04:16.150> fix 00:04:16.379 --> 00:04:16.389 align:start position:0% feed because maybe they wants to fix 00:04:16.389 --> 00:04:22.140 align:start position:0% feed because maybe they wants to fix like<00:04:18.000> the<00:04:19.000> contribution<00:04:19.989> in<00:04:20.500> USD<00:04:21.340> instead<00:04:21.820> but 00:04:22.140 --> 00:04:22.150 align:start position:0% like the contribution in USD instead but 00:04:22.150 --> 00:04:24.270 align:start position:0% like the contribution in USD instead but they<00:04:22.300> receive<00:04:22.630> eaters<00:04:22.990> or<00:04:23.139> things<00:04:23.830> like<00:04:23.889> that 00:04:24.270 --> 00:04:24.280 align:start position:0% they receive eaters or things like that 00:04:24.280 --> 00:04:26.490 align:start position:0% they receive eaters or things like that but<00:04:24.520> there<00:04:24.639> is<00:04:24.700> also<00:04:24.910> a<00:04:25.060> lot<00:04:25.330> around<00:04:25.720> gambling 00:04:26.490 --> 00:04:26.500 align:start position:0% but there is also a lot around gambling 00:04:26.500 --> 00:04:28.740 align:start position:0% but there is also a lot around gambling as<00:04:26.800> you<00:04:27.039> can<00:04:27.190> see<00:04:27.340> here<00:04:27.640> because<00:04:28.599> the 00:04:28.740 --> 00:04:28.750 align:start position:0% as you can see here because the 00:04:28.750 --> 00:04:31.740 align:start position:0% as you can see here because the randomness<00:04:29.229> is<00:04:29.470> yet<00:04:30.190> another<00:04:30.400> like<00:04:31.180> piece<00:04:31.599> of 00:04:31.740 --> 00:04:31.750 align:start position:0% randomness is yet another like piece of 00:04:31.750 --> 00:04:32.590 align:start position:0% randomness is yet another like piece of data<00:04:31.900> which<00:04:32.169> is<00:04:32.320> not 00:04:32.590 --> 00:04:32.600 align:start position:0% data which is not 00:04:32.600 --> 00:04:35.260 align:start position:0% data which is not easy<00:04:32.750> to<00:04:33.410> compute<00:04:34.340> straight<00:04:34.970> on<00:04:35.150> the 00:04:35.260 --> 00:04:35.270 align:start position:0% easy to compute straight on the 00:04:35.270 --> 00:04:38.170 align:start position:0% easy to compute straight on the blockchain<00:04:35.480> without<00:04:36.170> having<00:04:36.650> like<00:04:37.490> the<00:04:37.730> -<00:04:37.940> to 00:04:38.170 --> 00:04:38.180 align:start position:0% blockchain without having like the - to 00:04:38.180 --> 00:04:42.250 align:start position:0% blockchain without having like the - to possibly<00:04:38.540> collude<00:04:39.310> so<00:04:40.310> the<00:04:41.210> D<00:04:41.810> role<00:04:41.990> of<00:04:42.110> the 00:04:42.250 --> 00:04:42.260 align:start position:0% possibly collude so the D role of the 00:04:42.260 --> 00:04:45.640 align:start position:0% possibly collude so the D role of the Oracle<00:04:42.650> goes<00:04:42.980> way<00:04:43.280> beyond<00:04:43.700> the<00:04:44.500> fetching<00:04:45.500> of 00:04:45.640 --> 00:04:45.650 align:start position:0% Oracle goes way beyond the fetching of 00:04:45.650 --> 00:04:47.410 align:start position:0% Oracle goes way beyond the fetching of the<00:04:45.740> data<00:04:45.890> from<00:04:46.130> a<00:04:46.190> Web<00:04:46.340> API<00:04:46.370> it<00:04:47.090> could<00:04:47.300> be 00:04:47.410 --> 00:04:47.420 align:start position:0% the data from a Web API it could be 00:04:47.420 --> 00:04:49.270 align:start position:0% the data from a Web API it could be really<00:04:47.750> the<00:04:48.170> offloading<00:04:48.710> to<00:04:48.830> of<00:04:49.160> a 00:04:49.270 --> 00:04:49.280 align:start position:0% really the offloading to of a 00:04:49.280 --> 00:04:51.550 align:start position:0% really the offloading to of a competition<00:04:49.670> to<00:04:50.240> an<00:04:50.360> Austrian<00:04:50.690> context<00:04:51.110> but 00:04:51.550 --> 00:04:51.560 align:start position:0% competition to an Austrian context but 00:04:51.560 --> 00:04:55.390 align:start position:0% competition to an Austrian context but it<00:04:51.710> could<00:04:51.920> be<00:04:52.070> much<00:04:52.430> more<00:04:52.670> as<00:04:52.850> we<00:04:52.910> see<00:04:53.450> later<00:04:54.400> so 00:04:55.390 --> 00:04:55.400 align:start position:0% it could be much more as we see later so 00:04:55.400 --> 00:05:00.640 align:start position:0% it could be much more as we see later so the<00:04:55.760> model<00:04:56.270> the<00:04:57.460> provable<00:04:58.540> as<00:04:59.540> adopted<00:05:00.050> is<00:05:00.320> the 00:05:00.640 --> 00:05:00.650 align:start position:0% the model the provable as adopted is the 00:05:00.650 --> 00:05:03.820 align:start position:0% the model the provable as adopted is the one<00:05:00.800> of<00:05:00.920> using<00:05:01.310> the<00:05:02.270> basically<00:05:03.200> trusted 00:05:03.820 --> 00:05:03.830 align:start position:0% one of using the basically trusted 00:05:03.830 --> 00:05:08.320 align:start position:0% one of using the basically trusted computing<00:05:04.100> techniques<00:05:04.610> to<00:05:06.550> prove<00:05:07.550> that<00:05:08.060> the 00:05:08.320 --> 00:05:08.330 align:start position:0% computing techniques to prove that the 00:05:08.330 --> 00:05:10.450 align:start position:0% computing techniques to prove that the data<00:05:08.540> we<00:05:08.780> are<00:05:08.810> fetching<00:05:09.050> from<00:05:09.380> a<00:05:09.530> Web<00:05:09.680> API<00:05:09.980> is 00:05:10.450 --> 00:05:10.460 align:start position:0% data we are fetching from a Web API is 00:05:10.460 --> 00:05:12.580 align:start position:0% data we are fetching from a Web API is indeed<00:05:11.060> authentic<00:05:11.270> and<00:05:11.870> it<00:05:12.080> has<00:05:12.230> not<00:05:12.410> been 00:05:12.580 --> 00:05:12.590 align:start position:0% indeed authentic and it has not been 00:05:12.590 --> 00:05:13.930 align:start position:0% indeed authentic and it has not been tampered<00:05:12.800> with<00:05:13.100> during<00:05:13.610> the<00:05:13.700> delivery 00:05:13.930 --> 00:05:13.940 align:start position:0% tampered with during the delivery 00:05:13.940 --> 00:05:16.870 align:start position:0% tampered with during the delivery process<00:05:14.110> so<00:05:15.110> you<00:05:15.170> don't<00:05:15.410> want<00:05:15.620> the<00:05:15.860> Oracle<00:05:16.430> to 00:05:16.870 --> 00:05:16.880 align:start position:0% process so you don't want the Oracle to 00:05:16.880 --> 00:05:20.200 align:start position:0% process so you don't want the Oracle to potentially<00:05:17.540> like<00:05:18.500> compromise<00:05:19.160> the<00:05:19.310> data<00:05:19.490> so 00:05:20.200 --> 00:05:20.210 align:start position:0% potentially like compromise the data so 00:05:20.210 --> 00:05:22.030 align:start position:0% potentially like compromise the data so you're<00:05:20.360> already<00:05:20.630> trusting<00:05:21.140> data<00:05:21.350> source<00:05:21.620> you 00:05:22.030 --> 00:05:22.040 align:start position:0% you're already trusting data source you 00:05:22.040 --> 00:05:24.580 align:start position:0% you're already trusting data source you shouldn't<00:05:22.430> trust<00:05:22.700> the<00:05:23.240> Oracle<00:05:23.630> as<00:05:23.780> the<00:05:24.230> Oracle 00:05:24.580 --> 00:05:24.590 align:start position:0% shouldn't trust the Oracle as the Oracle 00:05:24.590 --> 00:05:26.380 align:start position:0% shouldn't trust the Oracle as the Oracle could<00:05:24.740> potentially<00:05:25.250> you<00:05:25.340> know<00:05:25.370> change<00:05:26.060> the 00:05:26.380 --> 00:05:26.390 align:start position:0% could potentially you know change the 00:05:26.390 --> 00:05:28.630 align:start position:0% could potentially you know change the data<00:05:27.290> it<00:05:27.620> has<00:05:27.740> received<00:05:28.130> from<00:05:28.310> the<00:05:28.460> data 00:05:28.630 --> 00:05:28.640 align:start position:0% data it has received from the data 00:05:28.640 --> 00:05:30.550 align:start position:0% data it has received from the data source<00:05:28.910> and<00:05:29.060> just<00:05:29.360> push<00:05:29.750> something<00:05:30.140> different 00:05:30.550 --> 00:05:30.560 align:start position:0% source and just push something different 00:05:30.560 --> 00:05:33.130 align:start position:0% source and just push something different to<00:05:30.620> the<00:05:30.680> blushing<00:05:31.100> so<00:05:31.460> it<00:05:31.580> may<00:05:31.760> trigger<00:05:32.060> like<00:05:32.840> a 00:05:33.130 --> 00:05:33.140 align:start position:0% to the blushing so it may trigger like a 00:05:33.140 --> 00:05:34.780 align:start position:0% to the blushing so it may trigger like a Bronk<00:05:33.470> payment<00:05:33.920> on<00:05:34.040> the<00:05:34.130> blockchain<00:05:34.340> or<00:05:34.670> it 00:05:34.780 --> 00:05:34.790 align:start position:0% Bronk payment on the blockchain or it 00:05:34.790 --> 00:05:36.610 align:start position:0% Bronk payment on the blockchain or it may<00:05:34.970> lead<00:05:35.180> to<00:05:35.210> Bronk<00:05:35.570> results<00:05:35.960> so<00:05:36.320> what<00:05:36.500> you 00:05:36.610 --> 00:05:36.620 align:start position:0% may lead to Bronk results so what you 00:05:36.620 --> 00:05:38.860 align:start position:0% may lead to Bronk results so what you want<00:05:36.860> is<00:05:37.010> the<00:05:37.310> Oracle<00:05:37.550> not<00:05:38.090> to<00:05:38.240> be<00:05:38.330> trusted<00:05:38.540> and 00:05:38.860 --> 00:05:38.870 align:start position:0% want is the Oracle not to be trusted and 00:05:38.870 --> 00:05:42.460 align:start position:0% want is the Oracle not to be trusted and that's<00:05:39.380> why<00:05:39.530> you<00:05:39.590> need<00:05:39.950> the<00:05:40.720> like<00:05:41.720> some<00:05:42.200> kind 00:05:42.460 --> 00:05:42.470 align:start position:0% that's why you need the like some kind 00:05:42.470 --> 00:05:44.890 align:start position:0% that's why you need the like some kind of<00:05:42.620> proofs<00:05:43.130> that<00:05:43.400> the<00:05:43.880> data<00:05:44.270> delivered<00:05:44.750> is 00:05:44.890 --> 00:05:44.900 align:start position:0% of proofs that the data delivered is 00:05:44.900 --> 00:05:46.360 align:start position:0% of proofs that the data delivered is correct<00:05:45.260> is<00:05:45.410> is<00:05:45.740> authentic 00:05:46.360 --> 00:05:46.370 align:start position:0% correct is is authentic 00:05:46.370 --> 00:05:49.650 align:start position:0% correct is is authentic so<00:05:47.080> provable<00:05:48.080> has<00:05:48.290> been<00:05:48.560> doing<00:05:48.710> that<00:05:48.920> with 00:05:49.650 --> 00:05:49.660 align:start position:0% so provable has been doing that with 00:05:49.660 --> 00:05:52.630 align:start position:0% so provable has been doing that with trusted<00:05:50.660> computing<00:05:50.870> techniques<00:05:51.430> for<00:05:52.430> those 00:05:52.630 --> 00:05:52.640 align:start position:0% trusted computing techniques for those 00:05:52.640 --> 00:05:53.950 align:start position:0% trusted computing techniques for those of<00:05:52.790> you<00:05:52.910> who<00:05:53.120> are<00:05:53.210> not<00:05:53.390> familiar<00:05:53.570> around 00:05:53.950 --> 00:05:53.960 align:start position:0% of you who are not familiar around 00:05:53.960 --> 00:05:56.020 align:start position:0% of you who are not familiar around trusted<00:05:54.500> computing<00:05:54.740> the<00:05:55.460> idea<00:05:55.700> is<00:05:55.850> to 00:05:56.020 --> 00:05:56.030 align:start position:0% trusted computing the idea is to 00:05:56.030 --> 00:05:59.410 align:start position:0% trusted computing the idea is to basically<00:05:56.210> use<00:05:56.720> some<00:05:57.080> like<00:05:57.910> dedicated<00:05:58.910> chips 00:05:59.410 --> 00:05:59.420 align:start position:0% basically use some like dedicated chips 00:05:59.420 --> 00:06:03.430 align:start position:0% basically use some like dedicated chips that<00:06:00.020> provide<00:06:00.670> sandboxing<00:06:01.670> in<00:06:01.910> hardware<00:06:02.900> for 00:06:03.430 --> 00:06:03.440 align:start position:0% that provide sandboxing in hardware for 00:06:03.440 --> 00:06:05.140 align:start position:0% that provide sandboxing in hardware for the<00:06:03.560> execution<00:06:04.010> of<00:06:04.070> a<00:06:04.220> given<00:06:04.490> piece<00:06:04.820> of<00:06:04.970> code 00:06:05.140 --> 00:06:05.150 align:start position:0% the execution of a given piece of code 00:06:05.150 --> 00:06:07.570 align:start position:0% the execution of a given piece of code so<00:06:05.900> basically<00:06:06.230> we<00:06:06.470> publish<00:06:06.830> the<00:06:06.980> code<00:06:07.220> that 00:06:07.570 --> 00:06:07.580 align:start position:0% so basically we publish the code that 00:06:07.580 --> 00:06:10.000 align:start position:0% so basically we publish the code that gets<00:06:07.640> executed<00:06:08.030> on<00:06:08.720> those<00:06:09.170> special<00:06:09.500> machines 00:06:10.000 --> 00:06:10.010 align:start position:0% gets executed on those special machines 00:06:10.010 --> 00:06:13.210 align:start position:0% gets executed on those special machines and<00:06:10.220> with<00:06:11.180> those<00:06:11.420> machines<00:06:11.870> help<00:06:12.230> to<00:06:12.560> to 00:06:13.210 --> 00:06:13.220 align:start position:0% and with those machines help to to 00:06:13.220 --> 00:06:15.790 align:start position:0% and with those machines help to to generate<00:06:13.640> an<00:06:14.030> authenticity<00:06:14.630> proof<00:06:15.170> so<00:06:15.680> it's 00:06:15.790 --> 00:06:15.800 align:start position:0% generate an authenticity proof so it's 00:06:15.800 --> 00:06:18.550 align:start position:0% generate an authenticity proof so it's basically<00:06:16.240> something<00:06:17.240> that<00:06:17.660> along<00:06:18.110> with<00:06:18.140> the 00:06:18.550 --> 00:06:18.560 align:start position:0% basically something that along with the 00:06:18.560 --> 00:06:20.620 align:start position:0% basically something that along with the result<00:06:18.890> helps<00:06:19.490> to<00:06:19.610> understand<00:06:20.150> that<00:06:20.390> the 00:06:20.620 --> 00:06:20.630 align:start position:0% result helps to understand that the 00:06:20.630 --> 00:06:22.270 align:start position:0% result helps to understand that the computation<00:06:21.200> has<00:06:21.320> happened<00:06:21.680> within<00:06:21.920> those 00:06:22.270 --> 00:06:22.280 align:start position:0% computation has happened within those 00:06:22.280 --> 00:06:24.280 align:start position:0% computation has happened within those safe<00:06:22.520> boundaries<00:06:23.000> we<00:06:23.720> send<00:06:23.930> them<00:06:24.080> to<00:06:24.200> the 00:06:24.280 --> 00:06:24.290 align:start position:0% safe boundaries we send them to the 00:06:24.290 --> 00:06:25.990 align:start position:0% safe boundaries we send them to the blockchain<00:06:24.710> and<00:06:24.830> then<00:06:25.160> basically<00:06:25.670> this 00:06:25.990 --> 00:06:26.000 align:start position:0% blockchain and then basically this 00:06:26.000 --> 00:06:27.970 align:start position:0% blockchain and then basically this provides<00:06:26.450> like<00:06:26.630> a<00:06:26.660> shield<00:06:27.050> against<00:06:27.860> the 00:06:27.970 --> 00:06:27.980 align:start position:0% provides like a shield against the 00:06:27.980 --> 00:06:30.250 align:start position:0% provides like a shield against the manipulations<00:06:28.940> during<00:06:29.540> the<00:06:29.630> data<00:06:29.840> delivery 00:06:30.250 --> 00:06:30.260 align:start position:0% manipulations during the data delivery 00:06:30.260 --> 00:06:32.500 align:start position:0% manipulations during the data delivery so<00:06:30.950> this<00:06:31.100> enables<00:06:31.490> you<00:06:31.610> to<00:06:31.670> verify<00:06:31.910> that<00:06:32.330> the 00:06:32.500 --> 00:06:32.510 align:start position:0% so this enables you to verify that the 00:06:32.510 --> 00:06:35.320 align:start position:0% so this enables you to verify that the Oracle<00:06:32.870> has<00:06:33.110> sent<00:06:33.440> the<00:06:33.590> answer<00:06:33.860> but<00:06:34.460> it<00:06:34.880> is<00:06:35.030> not 00:06:35.320 --> 00:06:35.330 align:start position:0% Oracle has sent the answer but it is not 00:06:35.330 --> 00:06:37.600 align:start position:0% Oracle has sent the answer but it is not the<00:06:35.600> like<00:06:36.290> owner<00:06:36.590> of<00:06:36.830> the<00:06:36.950> data<00:06:37.130> and<00:06:37.370> the<00:06:37.430> owner 00:06:37.600 --> 00:06:37.610 align:start position:0% the like owner of the data and the owner 00:06:37.610 --> 00:06:39.220 align:start position:0% the like owner of the data and the owner of<00:06:37.730> the<00:06:37.850> data<00:06:38.000> is<00:06:38.150> really<00:06:38.390> the<00:06:38.480> website<00:06:38.900> so 00:06:39.220 --> 00:06:39.230 align:start position:0% of the data is really the website so 00:06:39.230 --> 00:06:40.630 align:start position:0% of the data is really the website so there<00:06:39.350> has<00:06:39.440> been<00:06:39.470> no<00:06:39.650> alteration<00:06:40.340> during<00:06:40.550> the 00:06:40.630 --> 00:06:40.640 align:start position:0% there has been no alteration during the 00:06:40.640 --> 00:06:42.909 align:start position:0% there has been no alteration during the process<00:06:40.970> this<00:06:41.780> is<00:06:41.960> why<00:06:42.110> they<00:06:42.410> are<00:06:42.500> called<00:06:42.740> like 00:06:42.909 --> 00:06:42.919 align:start position:0% process this is why they are called like 00:06:42.919 --> 00:06:46.480 align:start position:0% process this is why they are called like authenticity<00:06:43.310> bras<00:06:44.440> there<00:06:45.440> are<00:06:45.560> many<00:06:45.740> like 00:06:46.480 --> 00:06:46.490 align:start position:0% authenticity bras there are many like 00:06:46.490 --> 00:06:48.309 align:start position:0% authenticity bras there are many like challenges<00:06:46.910> around<00:06:47.120> Oracle's<00:06:47.630> it's<00:06:47.870> not<00:06:48.080> just 00:06:48.309 --> 00:06:48.319 align:start position:0% challenges around Oracle's it's not just 00:06:48.319 --> 00:06:49.839 align:start position:0% challenges around Oracle's it's not just around<00:06:48.590> it<00:06:48.830> you<00:06:49.280> know<00:06:49.400> proving<00:06:49.759> the 00:06:49.839 --> 00:06:49.849 align:start position:0% around it you know proving the 00:06:49.849 --> 00:06:52.270 align:start position:0% around it you know proving the authenticity<00:06:49.880> of<00:06:50.389> data<00:06:50.630> which<00:06:51.259> has<00:06:51.470> been<00:06:51.680> our 00:06:52.270 --> 00:06:52.280 align:start position:0% authenticity of data which has been our 00:06:52.280 --> 00:06:56.080 align:start position:0% authenticity of data which has been our main<00:06:53.199> like<00:06:54.199> focus<00:06:54.650> for<00:06:55.009> the<00:06:55.130> last<00:06:55.160> years<00:06:55.490> there 00:06:56.080 --> 00:06:56.090 align:start position:0% main like focus for the last years there 00:06:56.090 --> 00:06:58.870 align:start position:0% main like focus for the last years there are<00:06:56.180> many<00:06:56.360> more<00:06:56.509> challenges<00:06:57.020> so<00:06:57.650> as<00:06:58.610> you<00:06:58.759> can 00:06:58.870 --> 00:06:58.880 align:start position:0% are many more challenges so as you can 00:06:58.880 --> 00:07:01.270 align:start position:0% are many more challenges so as you can see<00:06:58.940> here<00:06:59.330> one<00:06:59.599> is<00:06:59.780> around<00:07:00.080> you<00:07:00.590> know<00:07:00.710> relying 00:07:01.270 --> 00:07:01.280 align:start position:0% see here one is around you know relying 00:07:01.280 --> 00:07:03.550 align:start position:0% see here one is around you know relying on<00:07:01.400> reliable<00:07:01.910> data<00:07:02.090> sources<00:07:02.449> we<00:07:03.169> don't<00:07:03.349> want 00:07:03.550 --> 00:07:03.560 align:start position:0% on reliable data sources we don't want 00:07:03.560 --> 00:07:06.339 align:start position:0% on reliable data sources we don't want to<00:07:03.770> you<00:07:04.220> know<00:07:04.280> push<00:07:04.699> data<00:07:05.389> to<00:07:05.630> the<00:07:05.720> blocks<00:07:05.960> in<00:07:06.110> a 00:07:06.339 --> 00:07:06.349 align:start position:0% to you know push data to the blocks in a 00:07:06.349 --> 00:07:09.309 align:start position:0% to you know push data to the blocks in a way<00:07:06.590> which<00:07:06.830> is<00:07:06.860> secure<00:07:07.849> and<00:07:08.090> then<00:07:08.750> have<00:07:09.080> low 00:07:09.309 --> 00:07:09.319 align:start position:0% way which is secure and then have low 00:07:09.319 --> 00:07:11.650 align:start position:0% way which is secure and then have low quality<00:07:09.530> data<00:07:09.949> sources<00:07:10.310> that<00:07:10.580> cannot<00:07:11.479> really 00:07:11.650 --> 00:07:11.660 align:start position:0% quality data sources that cannot really 00:07:11.660 --> 00:07:12.219 align:start position:0% quality data sources that cannot really be<00:07:11.810> trusted 00:07:12.219 --> 00:07:12.229 align:start position:0% be trusted 00:07:12.229 --> 00:07:15.939 align:start position:0% be trusted so<00:07:12.800> this<00:07:13.009> is<00:07:13.160> something<00:07:13.699> where<00:07:13.970> well<00:07:14.949> players 00:07:15.939 --> 00:07:15.949 align:start position:0% so this is something where well players 00:07:15.949 --> 00:07:18.339 align:start position:0% so this is something where well players like<00:07:16.280> Thomson<00:07:17.090> Reuters<00:07:17.210> but<00:07:17.780> also<00:07:17.960> streamer 00:07:18.339 --> 00:07:18.349 align:start position:0% like Thomson Reuters but also streamer 00:07:18.349 --> 00:07:20.800 align:start position:0% like Thomson Reuters but also streamer and<00:07:18.620> few<00:07:19.190> others<00:07:19.400> are<00:07:19.580> working<00:07:20.000> a<00:07:20.240> lot<00:07:20.389> so<00:07:20.449> that 00:07:20.800 --> 00:07:20.810 align:start position:0% and few others are working a lot so that 00:07:20.810 --> 00:07:23.230 align:start position:0% and few others are working a lot so that they<00:07:20.990> can<00:07:21.199> basically<00:07:22.000> provide<00:07:23.000> some 00:07:23.230 --> 00:07:23.240 align:start position:0% they can basically provide some 00:07:23.240 --> 00:07:25.689 align:start position:0% they can basically provide some guarantees<00:07:23.389> on<00:07:23.870> the<00:07:24.159> selected<00:07:25.159> data<00:07:25.370> sources 00:07:25.689 --> 00:07:25.699 align:start position:0% guarantees on the selected data sources 00:07:25.699 --> 00:07:28.600 align:start position:0% guarantees on the selected data sources and<00:07:25.880> they<00:07:26.030> can<00:07:26.180> provide<00:07:26.419> quality<00:07:26.720> data<00:07:27.110> to<00:07:27.889> to 00:07:28.600 --> 00:07:28.610 align:start position:0% and they can provide quality data to to 00:07:28.610 --> 00:07:32.409 align:start position:0% and they can provide quality data to to the<00:07:28.699> blossom<00:07:29.919> and<00:07:30.919> the<00:07:31.370> way<00:07:31.550> to<00:07:31.610> basically<00:07:32.120> not 00:07:32.409 --> 00:07:32.419 align:start position:0% the blossom and the way to basically not 00:07:32.419 --> 00:07:36.010 align:start position:0% the blossom and the way to basically not rely<00:07:33.289> on<00:07:33.319> a<00:07:33.500> single<00:07:33.880> trust<00:07:34.880> line<00:07:35.120> on<00:07:35.539> the<00:07:35.840> data 00:07:36.010 --> 00:07:36.020 align:start position:0% rely on a single trust line on the data 00:07:36.020 --> 00:07:38.559 align:start position:0% rely on a single trust line on the data source<00:07:36.319> front<00:07:36.530> is<00:07:36.680> to<00:07:37.310> basically<00:07:37.789> use<00:07:38.300> more 00:07:38.559 --> 00:07:38.569 align:start position:0% source front is to basically use more 00:07:38.569 --> 00:07:40.870 align:start position:0% source front is to basically use more than<00:07:38.720> one<00:07:38.870> data<00:07:39.050> source<00:07:39.259> so<00:07:39.860> in<00:07:40.370> the<00:07:40.520> case<00:07:40.699> of 00:07:40.870 --> 00:07:40.880 align:start position:0% than one data source so in the case of 00:07:40.880 --> 00:07:42.850 align:start position:0% than one data source so in the case of the<00:07:41.180> price<00:07:41.599> of<00:07:41.810> each<00:07:42.020> other<00:07:42.199> for<00:07:42.440> instance<00:07:42.740> is 00:07:42.850 --> 00:07:42.860 align:start position:0% the price of each other for instance is 00:07:42.860 --> 00:07:44.920 align:start position:0% the price of each other for instance is quite<00:07:43.099> simple<00:07:43.460> because<00:07:43.880> you<00:07:44.030> can<00:07:44.270> just<00:07:44.539> you 00:07:44.920 --> 00:07:44.930 align:start position:0% quite simple because you can just you 00:07:44.930 --> 00:07:47.800 align:start position:0% quite simple because you can just you know<00:07:44.960> do<00:07:45.199> an<00:07:45.319> average<00:07:45.680> on<00:07:46.000> all<00:07:47.000> the<00:07:47.330> exchanges 00:07:47.800 --> 00:07:47.810 align:start position:0% know do an average on all the exchanges 00:07:47.810 --> 00:07:50.350 align:start position:0% know do an average on all the exchanges that<00:07:47.990> have<00:07:48.440> the<00:07:49.009> majority<00:07:49.250> of<00:07:49.490> the<00:07:49.550> trading 00:07:50.350 --> 00:07:50.360 align:start position:0% that have the majority of the trading 00:07:50.360 --> 00:07:52.540 align:start position:0% that have the majority of the trading volumes<00:07:50.719> so<00:07:51.349> you<00:07:51.409> have<00:07:51.860> something<00:07:52.159> accurate 00:07:52.540 --> 00:07:52.550 align:start position:0% volumes so you have something accurate 00:07:52.550 --> 00:07:54.339 align:start position:0% volumes so you have something accurate which<00:07:52.849> doesn't<00:07:53.240> have<00:07:53.419> like<00:07:53.870> points<00:07:54.259> of 00:07:54.339 --> 00:07:54.349 align:start position:0% which doesn't have like points of 00:07:54.349 --> 00:07:57.339 align:start position:0% which doesn't have like points of failure<00:07:54.469> theory<00:07:55.539> but<00:07:56.539> it<00:07:56.630> depends<00:07:56.960> it<00:07:57.050> can<00:07:57.169> get 00:07:57.339 --> 00:07:57.349 align:start position:0% failure theory but it depends it can get 00:07:57.349 --> 00:07:59.140 align:start position:0% failure theory but it depends it can get much<00:07:57.620> harder<00:07:57.860> depending<00:07:58.610> on<00:07:58.729> the<00:07:58.849> data<00:07:59.000> you 00:07:59.140 --> 00:07:59.150 align:start position:0% much harder depending on the data you 00:07:59.150 --> 00:07:59.529 align:start position:0% much harder depending on the data you want 00:07:59.529 --> 00:07:59.539 align:start position:0% want 00:07:59.539 --> 00:08:02.140 align:start position:0% want as<00:07:59.599> I<00:08:00.110> said<00:08:00.320> for<00:08:00.530> with<00:08:01.370> the<00:08:01.490> example<00:08:01.940> of<00:08:02.090> the 00:08:02.140 --> 00:08:02.150 align:start position:0% as I said for with the example of the 00:08:02.150 --> 00:08:04.719 align:start position:0% as I said for with the example of the number<00:08:02.810> of<00:08:02.840> views<00:08:03.530> for<00:08:03.800> a<00:08:03.860> YouTube<00:08:04.159> video<00:08:04.340> you 00:08:04.719 --> 00:08:04.729 align:start position:0% number of views for a YouTube video you 00:08:04.729 --> 00:08:07.749 align:start position:0% number of views for a YouTube video you have<00:08:04.940> no<00:08:05.180> possibility<00:08:05.750> to<00:08:06.530> go<00:08:06.740> you<00:08:07.219> know<00:08:07.340> to 00:08:07.749 --> 00:08:07.759 align:start position:0% have no possibility to go you know to 00:08:07.759 --> 00:08:09.790 align:start position:0% have no possibility to go you know to avoid<00:08:08.060> the<00:08:08.449> trust<00:08:08.690> on<00:08:08.840> with<00:08:09.020> Google<00:08:09.139> because 00:08:09.790 --> 00:08:09.800 align:start position:0% avoid the trust on with Google because 00:08:09.800 --> 00:08:11.080 align:start position:0% avoid the trust on with Google because it's<00:08:09.919> just<00:08:10.099> something<00:08:10.280> which<00:08:10.580> inherently 00:08:11.080 --> 00:08:11.090 align:start position:0% it's just something which inherently 00:08:11.090 --> 00:08:14.439 align:start position:0% it's just something which inherently belongs<00:08:11.810> to<00:08:12.710> to<00:08:13.039> YouTube<00:08:13.340> right<00:08:13.610> so<00:08:14.090> YouTube 00:08:14.439 --> 00:08:14.449 align:start position:0% belongs to to YouTube right so YouTube 00:08:14.449 --> 00:08:17.499 align:start position:0% belongs to to YouTube right so YouTube is<00:08:14.630> somehow<00:08:15.080> the<00:08:15.259> only<00:08:15.409> data<00:08:15.710> source<00:08:15.979> you<00:08:16.509> you 00:08:17.499 --> 00:08:17.509 align:start position:0% is somehow the only data source you you 00:08:17.509 --> 00:08:21.670 align:start position:0% is somehow the only data source you you you<00:08:18.229> will<00:08:18.380> need<00:08:18.500> to<00:08:18.710> do<00:08:19.550> reach<00:08:19.699> out<00:08:19.849> to<00:08:20.469> then<00:08:21.469> as 00:08:21.670 --> 00:08:21.680 align:start position:0% you will need to do reach out to then as 00:08:21.680 --> 00:08:24.850 align:start position:0% you will need to do reach out to then as for<00:08:21.919> the<00:08:22.069> like<00:08:22.430> authenticity<00:08:22.759> of<00:08:23.120> the<00:08:23.419> data<00:08:23.860> we 00:08:24.850 --> 00:08:24.860 align:start position:0% for the like authenticity of the data we 00:08:24.860 --> 00:08:26.770 align:start position:0% for the like authenticity of the data we have<00:08:24.949> been<00:08:25.130> using<00:08:25.310> few<00:08:25.580> technologies<00:08:25.880> such<00:08:26.750> as 00:08:26.770 --> 00:08:26.780 align:start position:0% have been using few technologies such as 00:08:26.780 --> 00:08:29.680 align:start position:0% have been using few technologies such as like<00:08:27.590> the<00:08:27.860> trusted<00:08:28.610> execution<00:08:28.849> environment 00:08:29.680 --> 00:08:29.690 align:start position:0% like the trusted execution environment 00:08:29.690 --> 00:08:33.490 align:start position:0% like the trusted execution environment of<00:08:29.900> Qualcomm<00:08:30.710> the<00:08:31.520> legend<00:08:32.479> on<00:08:32.630> us<00:08:32.810> the<00:08:33.289> some<00:08:33.469> of 00:08:33.490 --> 00:08:33.500 align:start position:0% of Qualcomm the legend on us the some of 00:08:33.500 --> 00:08:36.100 align:start position:0% of Qualcomm the legend on us the some of you<00:08:33.680> some<00:08:34.099> of<00:08:34.159> you<00:08:34.339> may<00:08:34.520> be<00:08:34.820> familiar<00:08:35.029> with<00:08:35.360> and 00:08:36.100 --> 00:08:36.110 align:start position:0% you some of you may be familiar with and 00:08:36.110 --> 00:08:38.409 align:start position:0% you some of you may be familiar with and Intel<00:08:36.380> SGX<00:08:36.500> so<00:08:37.490> this<00:08:37.640> is<00:08:37.760> something<00:08:37.969> that's 00:08:38.409 --> 00:08:38.419 align:start position:0% Intel SGX so this is something that's 00:08:38.419 --> 00:08:41.920 align:start position:0% Intel SGX so this is something that's also<00:08:39.729> chain<00:08:40.729> linked<00:08:40.969> with<00:08:41.120> the<00:08:41.539> town<00:08:41.719> crier 00:08:41.920 --> 00:08:41.930 align:start position:0% also chain linked with the town crier 00:08:41.930 --> 00:08:45.280 align:start position:0% also chain linked with the town crier project<00:08:42.500> has<00:08:42.649> been<00:08:43.130> working<00:08:43.370> on<00:08:44.170> there<00:08:45.170> are<00:08:45.260> a 00:08:45.280 --> 00:08:45.290 align:start position:0% project has been working on there are a 00:08:45.290 --> 00:08:47.590 align:start position:0% project has been working on there are a few<00:08:45.440> options<00:08:45.620> on<00:08:46.040> that<00:08:46.520> front<00:08:46.760> but<00:08:47.060> using 00:08:47.590 --> 00:08:47.600 align:start position:0% few options on that front but using 00:08:47.600 --> 00:08:49.300 align:start position:0% few options on that front but using trusted<00:08:47.930> computing<00:08:48.200> is<00:08:48.560> quite<00:08:48.890> general 00:08:49.300 --> 00:08:49.310 align:start position:0% trusted computing is quite general 00:08:49.310 --> 00:08:51.519 align:start position:0% trusted computing is quite general purpose<00:08:49.700> so<00:08:49.940> it<00:08:50.029> can<00:08:50.209> help<00:08:50.420> to<00:08:50.750> basically 00:08:51.519 --> 00:08:51.529 align:start position:0% purpose so it can help to basically 00:08:51.529 --> 00:08:53.110 align:start position:0% purpose so it can help to basically provide<00:08:51.860> those<00:08:52.070> guarantees<00:08:52.579> for<00:08:53.060> the 00:08:53.110 --> 00:08:53.120 align:start position:0% provide those guarantees for the 00:08:53.120 --> 00:08:54.850 align:start position:0% provide those guarantees for the execution<00:08:53.720> of<00:08:53.810> something<00:08:54.290> on<00:08:54.410> the<00:08:54.560> option 00:08:54.850 --> 00:08:54.860 align:start position:0% execution of something on the option 00:08:54.860 --> 00:08:56.800 align:start position:0% execution of something on the option context<00:08:55.279> while<00:08:55.880> interacting<00:08:56.540> with 00:08:56.800 --> 00:08:56.810 align:start position:0% context while interacting with 00:08:56.810 --> 00:08:59.590 align:start position:0% context while interacting with young-shin<00:08:57.350> context<00:08:57.970> also<00:08:58.970> there<00:08:59.240> is<00:08:59.329> a<00:08:59.360> lot 00:08:59.590 --> 00:08:59.600 align:start position:0% young-shin context also there is a lot 00:08:59.600 --> 00:09:00.280 align:start position:0% young-shin context also there is a lot of<00:08:59.630> work<00:08:59.959> go 00:09:00.280 --> 00:09:00.290 align:start position:0% of work go 00:09:00.290 --> 00:09:02.889 align:start position:0% of work go on<00:09:00.679> the<00:09:01.189> protocol<00:09:01.729> that<00:09:01.939> those<00:09:02.329> Oracle's 00:09:02.889 --> 00:09:02.899 align:start position:0% on the protocol that those Oracle's 00:09:02.899 --> 00:09:05.139 align:start position:0% on the protocol that those Oracle's should<00:09:03.169> use<00:09:03.410> while<00:09:04.129> speaking<00:09:04.759> with<00:09:05.059> the 00:09:05.139 --> 00:09:05.149 align:start position:0% should use while speaking with the 00:09:05.149 --> 00:09:05.559 align:start position:0% should use while speaking with the blockchain 00:09:05.559 --> 00:09:05.569 align:start position:0% blockchain 00:09:05.569 --> 00:09:08.829 align:start position:0% blockchain so<00:09:06.559> chain<00:09:07.369> link<00:09:07.609> but<00:09:07.879> also<00:09:08.089> make<00:09:08.449> a<00:09:08.479> dao 00:09:08.829 --> 00:09:08.839 align:start position:0% so chain link but also make a dao 00:09:08.839 --> 00:09:11.739 align:start position:0% so chain link but also make a dao compound<00:09:09.369> rhombus<00:09:10.369> and<00:09:10.639> others<00:09:10.999> also<00:09:11.449> with 00:09:11.739 --> 00:09:11.749 align:start position:0% compound rhombus and others also with 00:09:11.749 --> 00:09:16.569 align:start position:0% compound rhombus and others also with net<00:09:11.959> they<00:09:12.889> are<00:09:13.249> working<00:09:13.489> on<00:09:13.790> on<00:09:14.179> that<00:09:14.389> front<00:09:15.579> we 00:09:16.569 --> 00:09:16.579 align:start position:0% net they are working on on that front we 00:09:16.579 --> 00:09:18.069 align:start position:0% net they are working on on that front we have<00:09:16.669> been<00:09:16.850> doing<00:09:16.999> so<00:09:17.209> for<00:09:17.389> few<00:09:17.600> years<00:09:17.629> as<00:09:17.929> well 00:09:18.069 --> 00:09:18.079 align:start position:0% have been doing so for few years as well 00:09:18.079 --> 00:09:20.710 align:start position:0% have been doing so for few years as well and<00:09:18.410> I<00:09:19.009> think<00:09:19.039> those<00:09:19.399> systems<00:09:19.819> will<00:09:19.999> end<00:09:20.239> up<00:09:20.419> to 00:09:20.710 --> 00:09:20.720 align:start position:0% and I think those systems will end up to 00:09:20.720 --> 00:09:22.689 align:start position:0% and I think those systems will end up to interoperate<00:09:21.589> one<00:09:22.039> with<00:09:22.189> the<00:09:22.309> other<00:09:22.429> and 00:09:22.689 --> 00:09:22.699 align:start position:0% interoperate one with the other and 00:09:22.699 --> 00:09:26.139 align:start position:0% interoperate one with the other and depending<00:09:23.569> on<00:09:23.779> like<00:09:24.259> the<00:09:24.499> needs<00:09:24.709> of<00:09:24.919> the<00:09:25.220> smart 00:09:26.139 --> 00:09:26.149 align:start position:0% depending on like the needs of the smart 00:09:26.149 --> 00:09:28.090 align:start position:0% depending on like the needs of the smart contract<00:09:26.389> there<00:09:27.139> will<00:09:27.289> be<00:09:27.319> the<00:09:27.559> adoption<00:09:27.979> or 00:09:28.090 --> 00:09:28.100 align:start position:0% contract there will be the adoption or 00:09:28.100 --> 00:09:29.979 align:start position:0% contract there will be the adoption or of<00:09:28.249> one<00:09:28.459> system<00:09:28.819> over<00:09:29.029> the<00:09:29.149> other<00:09:29.269> so<00:09:29.839> for 00:09:29.979 --> 00:09:29.989 align:start position:0% of one system over the other so for 00:09:29.989 --> 00:09:32.229 align:start position:0% of one system over the other so for example<00:09:30.379> as<00:09:30.559> you<00:09:30.589> will<00:09:30.979> see<00:09:31.100> in<00:09:31.160> a<00:09:31.220> second<00:09:31.579> the 00:09:32.229 --> 00:09:32.239 align:start position:0% example as you will see in a second the 00:09:32.239 --> 00:09:34.719 align:start position:0% example as you will see in a second the provable<00:09:32.569> one<00:09:32.869> is<00:09:33.079> optimized<00:09:33.889> for<00:09:34.069> being<00:09:34.519> a 00:09:34.719 --> 00:09:34.729 align:start position:0% provable one is optimized for being a 00:09:34.729 --> 00:09:36.999 align:start position:0% provable one is optimized for being a cost-effective<00:09:35.449> on<00:09:35.629> chain<00:09:35.959> so<00:09:36.410> the<00:09:36.529> gas<00:09:36.709> cost 00:09:36.999 --> 00:09:37.009 align:start position:0% cost-effective on chain so the gas cost 00:09:37.009 --> 00:09:39.400 align:start position:0% cost-effective on chain so the gas cost is<00:09:37.160> very<00:09:37.189> low<00:09:37.429> and<00:09:37.759> it<00:09:38.479> doesn't<00:09:38.929> give<00:09:39.109> strong 00:09:39.400 --> 00:09:39.410 align:start position:0% is very low and it doesn't give strong 00:09:39.410 --> 00:09:41.219 align:start position:0% is very low and it doesn't give strong guarantees<00:09:40.009> on<00:09:40.309> the<00:09:40.549> fact<00:09:40.729> that<00:09:40.819> the 00:09:41.219 --> 00:09:41.229 align:start position:0% guarantees on the fact that the 00:09:41.229 --> 00:09:44.139 align:start position:0% guarantees on the fact that the unanswered<00:09:42.259> will<00:09:42.619> be<00:09:42.769> provided<00:09:43.279> but<00:09:43.879> it 00:09:44.139 --> 00:09:44.149 align:start position:0% unanswered will be provided but it 00:09:44.149 --> 00:09:45.639 align:start position:0% unanswered will be provided but it provides<00:09:44.509> guarantees<00:09:45.019> on<00:09:45.229> the<00:09:45.350> fact<00:09:45.559> that 00:09:45.639 --> 00:09:45.649 align:start position:0% provides guarantees on the fact that 00:09:45.649 --> 00:09:47.739 align:start position:0% provides guarantees on the fact that when<00:09:45.979> an<00:09:46.129> answer<00:09:46.519> is<00:09:46.729> sent<00:09:47.179> to<00:09:47.239> the<00:09:47.359> blocking 00:09:47.739 --> 00:09:47.749 align:start position:0% when an answer is sent to the blocking 00:09:47.749 --> 00:09:50.019 align:start position:0% when an answer is sent to the blocking it's<00:09:48.169> really<00:09:48.439> authentic<00:09:48.859> so<00:09:49.519> you<00:09:49.579> know<00:09:49.850> that 00:09:50.019 --> 00:09:50.029 align:start position:0% it's really authentic so you know that 00:09:50.029 --> 00:09:51.460 align:start position:0% it's really authentic so you know that basically<00:09:50.419> if<00:09:50.569> you<00:09:50.689> get<00:09:50.809> an<00:09:51.019> answer<00:09:51.169> the 00:09:51.460 --> 00:09:51.470 align:start position:0% basically if you get an answer the 00:09:51.470 --> 00:09:54.159 align:start position:0% basically if you get an answer the answer<00:09:51.559> is<00:09:51.859> secure<00:09:52.509> while<00:09:53.509> other<00:09:53.720> systems 00:09:54.159 --> 00:09:54.169 align:start position:0% answer is secure while other systems 00:09:54.169 --> 00:09:57.219 align:start position:0% answer is secure while other systems focus<00:09:54.559> also<00:09:54.799> on<00:09:55.039> like<00:09:55.759> giving<00:09:56.749> some<00:09:56.959> more 00:09:57.219 --> 00:09:57.229 align:start position:0% focus also on like giving some more 00:09:57.229 --> 00:09:59.859 align:start position:0% focus also on like giving some more guarantees<00:09:58.129> around<00:09:58.459> the<00:09:58.579> redundancy<00:09:59.149> so<00:09:59.720> that 00:09:59.859 --> 00:09:59.869 align:start position:0% guarantees around the redundancy so that 00:09:59.869 --> 00:10:02.769 align:start position:0% guarantees around the redundancy so that basically<00:10:00.289> you<00:10:00.829> can<00:10:01.009> potentially<00:10:01.279> have<00:10:01.779> also 00:10:02.769 --> 00:10:02.779 align:start position:0% basically you can potentially have also 00:10:02.779 --> 00:10:06.460 align:start position:0% basically you can potentially have also a<00:10:02.959> guarantee<00:10:03.379> that<00:10:03.410> the<00:10:03.939> result<00:10:04.939> will<00:10:05.329> be<00:10:05.470> sent 00:10:06.460 --> 00:10:06.470 align:start position:0% a guarantee that the result will be sent 00:10:06.470 --> 00:10:08.590 align:start position:0% a guarantee that the result will be sent so<00:10:07.189> that's<00:10:07.399> why<00:10:07.519> for<00:10:08.119> instance<00:10:08.449> we<00:10:08.539> are 00:10:08.590 --> 00:10:08.600 align:start position:0% so that's why for instance we are 00:10:08.600 --> 00:10:09.729 align:start position:0% so that's why for instance we are looking<00:10:08.809> to<00:10:08.959> integrate<00:10:09.139> with<00:10:09.439> other<00:10:09.499> systems 00:10:09.729 --> 00:10:09.739 align:start position:0% looking to integrate with other systems 00:10:09.739 --> 00:10:12.489 align:start position:0% looking to integrate with other systems here<00:10:10.279> so<00:10:10.759> if<00:10:10.910> someone<00:10:11.299> is<00:10:11.480> interested<00:10:11.779> to<00:10:12.169> pay 00:10:12.489 --> 00:10:12.499 align:start position:0% here so if someone is interested to pay 00:10:12.499 --> 00:10:14.259 align:start position:0% here so if someone is interested to pay a<00:10:12.529> premium<00:10:12.889> because<00:10:13.309> maybe<00:10:13.730> they<00:10:13.910> want<00:10:14.089> more 00:10:14.259 --> 00:10:14.269 align:start position:0% a premium because maybe they want more 00:10:14.269 --> 00:10:16.479 align:start position:0% a premium because maybe they want more redundancy<00:10:14.720> then<00:10:15.319> they<00:10:15.679> can<00:10:15.889> go<00:10:16.069> via<00:10:16.279> other 00:10:16.479 --> 00:10:16.489 align:start position:0% redundancy then they can go via other 00:10:16.489 --> 00:10:18.489 align:start position:0% redundancy then they can go via other Oracle<00:10:16.939> systems<00:10:17.389> and<00:10:17.539> still<00:10:18.019> benefit<00:10:18.470> from 00:10:18.489 --> 00:10:18.499 align:start position:0% Oracle systems and still benefit from 00:10:18.499 --> 00:10:23.079 align:start position:0% Oracle systems and still benefit from our<00:10:18.769> authenticity<00:10:19.100> process<00:10:21.129> so<00:10:22.129> over<00:10:22.910> the 00:10:23.079 --> 00:10:23.089 align:start position:0% our authenticity process so over the 00:10:23.089 --> 00:10:25.749 align:start position:0% our authenticity process so over the years<00:10:23.119> what<00:10:23.869> we<00:10:24.049> have<00:10:24.189> like<00:10:25.189> heard<00:10:25.429> from<00:10:25.609> the 00:10:25.749 --> 00:10:25.759 align:start position:0% years what we have like heard from the 00:10:25.759 --> 00:10:27.340 align:start position:0% years what we have like heard from the community<00:10:25.999> as<00:10:26.480> for<00:10:26.720> the<00:10:26.779> community<00:10:26.929> feedback 00:10:27.340 --> 00:10:27.350 align:start position:0% community as for the community feedback 00:10:27.350 --> 00:10:30.189 align:start position:0% community as for the community feedback is<00:10:27.859> basically<00:10:28.669> that<00:10:28.970> this<00:10:29.359> is<00:10:29.509> what<00:10:29.689> they<00:10:29.869> were 00:10:30.189 --> 00:10:30.199 align:start position:0% is basically that this is what they were 00:10:30.199 --> 00:10:33.669 align:start position:0% is basically that this is what they were looking<00:10:30.230> for<00:10:30.709> like<00:10:31.549> a<00:10:32.059> reduced<00:10:32.720> cost<00:10:32.959> because 00:10:33.669 --> 00:10:33.679 align:start position:0% looking for like a reduced cost because 00:10:33.679 --> 00:10:36.729 align:start position:0% looking for like a reduced cost because many<00:10:33.889> times<00:10:34.160> you<00:10:34.399> have<00:10:34.519> like<00:10:34.819> a<00:10:35.739> transaction 00:10:36.729 --> 00:10:36.739 align:start position:0% many times you have like a transaction 00:10:36.739 --> 00:10:39.400 align:start position:0% many times you have like a transaction on<00:10:36.829> a<00:10:36.889> theorem<00:10:37.279> that<00:10:37.970> needs<00:10:38.809> to<00:10:39.019> reach<00:10:39.169> out<00:10:39.379> to 00:10:39.400 --> 00:10:39.410 align:start position:0% on a theorem that needs to reach out to 00:10:39.410 --> 00:10:41.619 align:start position:0% on a theorem that needs to reach out to external<00:10:40.220> data<00:10:40.399> and<00:10:40.730> you<00:10:40.910> don't<00:10:41.089> really<00:10:41.329> want 00:10:41.619 --> 00:10:41.629 align:start position:0% external data and you don't really want 00:10:41.629 --> 00:10:46.299 align:start position:0% external data and you don't really want this<00:10:42.139> external<00:10:42.889> data<00:10:43.419> fetching<00:10:44.419> to<00:10:45.309> like 00:10:46.299 --> 00:10:46.309 align:start position:0% this external data fetching to like 00:10:46.309 --> 00:10:48.939 align:start position:0% this external data fetching to like increase<00:10:47.269> significantly<00:10:47.539> the<00:10:48.169> cost<00:10:48.649> of<00:10:48.829> your 00:10:48.939 --> 00:10:48.949 align:start position:0% increase significantly the cost of your 00:10:48.949 --> 00:10:51.249 align:start position:0% increase significantly the cost of your transaction<00:10:49.309> you're<00:10:50.149> already<00:10:50.359> paying<00:10:50.629> like 00:10:51.249 --> 00:10:51.259 align:start position:0% transaction you're already paying like 00:10:51.259 --> 00:10:54.129 align:start position:0% transaction you're already paying like the<00:10:51.829> gas<00:10:52.129> price<00:10:52.429> for<00:10:52.789> confirming<00:10:53.449> transaction 00:10:54.129 --> 00:10:54.139 align:start position:0% the gas price for confirming transaction 00:10:54.139 --> 00:10:56.079 align:start position:0% the gas price for confirming transaction you<00:10:54.499> don't<00:10:54.679> want<00:10:54.919> the<00:10:55.100> Oracle<00:10:55.519> to<00:10:55.699> impact 00:10:56.079 --> 00:10:56.089 align:start position:0% you don't want the Oracle to impact 00:10:56.089 --> 00:10:58.689 align:start position:0% you don't want the Oracle to impact significantly<00:10:56.749> on<00:10:56.899> that<00:10:57.049> cost<00:10:57.289> so<00:10:57.559> this<00:10:58.549> is 00:10:58.689 --> 00:10:58.699 align:start position:0% significantly on that cost so this is 00:10:58.699 --> 00:11:00.429 align:start position:0% significantly on that cost so this is why<00:10:58.850> having<00:10:59.329> a<00:10:59.449> fully<00:11:00.139> decentralized 00:11:00.429 --> 00:11:00.439 align:start position:0% why having a fully decentralized 00:11:00.439 --> 00:11:02.469 align:start position:0% why having a fully decentralized approach<00:11:01.009> is<00:11:01.309> typically<00:11:01.699> more<00:11:01.819> expensive<00:11:01.879> and 00:11:02.469 --> 00:11:02.479 align:start position:0% approach is typically more expensive and 00:11:02.479 --> 00:11:06.279 align:start position:0% approach is typically more expensive and for<00:11:02.869> some<00:11:03.049> applications<00:11:03.589> it<00:11:03.739> may<00:11:04.220> be<00:11:04.509> like<00:11:05.509> it 00:11:06.279 --> 00:11:06.289 align:start position:0% for some applications it may be like it 00:11:06.289 --> 00:11:08.019 align:start position:0% for some applications it may be like it may<00:11:06.499> not<00:11:06.649> be<00:11:06.829> a<00:11:06.859> good<00:11:07.039> fit<00:11:07.249> so<00:11:07.429> it<00:11:07.699> depends<00:11:07.970> on 00:11:08.019 --> 00:11:08.029 align:start position:0% may not be a good fit so it depends on 00:11:08.029 --> 00:11:09.399 align:start position:0% may not be a good fit so it depends on the<00:11:08.089> application<00:11:08.600> if<00:11:08.749> you<00:11:09.079> have<00:11:09.169> an 00:11:09.399 --> 00:11:09.409 align:start position:0% the application if you have an 00:11:09.409 --> 00:11:11.529 align:start position:0% the application if you have an application<00:11:09.589> where<00:11:09.980> for<00:11:10.369> instance<00:11:10.699> you<00:11:11.149> want 00:11:11.529 --> 00:11:11.539 align:start position:0% application where for instance you want 00:11:11.539 --> 00:11:14.079 align:start position:0% application where for instance you want to<00:11:11.689> like<00:11:12.529> get<00:11:12.739> external<00:11:13.159> data<00:11:13.339> for<00:11:13.699> every 00:11:14.079 --> 00:11:14.089 align:start position:0% to like get external data for every 00:11:14.089 --> 00:11:15.910 align:start position:0% to like get external data for every transaction<00:11:14.600> doing<00:11:15.319> it<00:11:15.499> in<00:11:15.649> a<00:11:15.709> fully 00:11:15.910 --> 00:11:15.920 align:start position:0% transaction doing it in a fully 00:11:15.920 --> 00:11:17.559 align:start position:0% transaction doing it in a fully decentralized<00:11:16.160> way<00:11:16.550> maybe<00:11:17.059> we're<00:11:17.389> more 00:11:17.559 --> 00:11:17.569 align:start position:0% decentralized way maybe we're more 00:11:17.569 --> 00:11:20.410 align:start position:0% decentralized way maybe we're more expensive<00:11:18.319> so<00:11:19.100> it<00:11:19.550> depends<00:11:19.910> like<00:11:20.149> for 00:11:20.410 --> 00:11:20.420 align:start position:0% expensive so it depends like for 00:11:20.420 --> 00:11:22.559 align:start position:0% expensive so it depends like for gambling<00:11:20.839> for<00:11:20.990> instance<00:11:21.350> I<00:11:21.529> don't<00:11:21.889> think<00:11:22.249> that 00:11:22.559 --> 00:11:22.569 align:start position:0% gambling for instance I don't think that 00:11:22.569 --> 00:11:24.610 align:start position:0% gambling for instance I don't think that decentralization<00:11:23.569> provides<00:11:24.079> really<00:11:24.439> a 00:11:24.610 --> 00:11:24.620 align:start position:0% decentralization provides really a 00:11:24.620 --> 00:11:26.590 align:start position:0% decentralization provides really a strong<00:11:25.069> benefit<00:11:25.519> on<00:11:25.730> the<00:11:25.790> random<00:11:26.329> number 00:11:26.590 --> 00:11:26.600 align:start position:0% strong benefit on the random number 00:11:26.600 --> 00:11:28.569 align:start position:0% strong benefit on the random number generation<00:11:26.959> part<00:11:27.290> why<00:11:28.009> for<00:11:28.339> other<00:11:28.490> things 00:11:28.569 --> 00:11:28.579 align:start position:0% generation part why for other things 00:11:28.579 --> 00:11:31.600 align:start position:0% generation part why for other things like<00:11:29.029> price<00:11:29.360> feeds<00:11:29.660> you<00:11:30.499> may<00:11:30.709> want<00:11:31.009> like<00:11:31.430> to 00:11:31.600 --> 00:11:31.610 align:start position:0% like price feeds you may want like to 00:11:31.610 --> 00:11:33.699 align:start position:0% like price feeds you may want like to get<00:11:31.790> data<00:11:32.029> every<00:11:32.629> few<00:11:32.839> minutes<00:11:33.019> instead<00:11:33.559> that 00:11:33.699 --> 00:11:33.709 align:start position:0% get data every few minutes instead that 00:11:33.709 --> 00:11:36.549 align:start position:0% get data every few minutes instead that then<00:11:34.129> every<00:11:34.819> transaction<00:11:35.240> so<00:11:35.809> you<00:11:35.870> may<00:11:36.110> want 00:11:36.549 --> 00:11:36.559 align:start position:0% then every transaction so you may want 00:11:36.559 --> 00:11:38.949 align:start position:0% then every transaction so you may want to<00:11:36.649> obtain<00:11:37.069> in<00:11:37.399> a<00:11:37.610> more<00:11:37.819> like<00:11:38.089> decentralized 00:11:38.949 --> 00:11:38.959 align:start position:0% to obtain in a more like decentralized 00:11:38.959 --> 00:11:42.670 align:start position:0% to obtain in a more like decentralized approach<00:11:39.709> and<00:11:40.129> pay<00:11:40.249> a<00:11:40.279> premium<00:11:40.490> for<00:11:40.670> that<00:11:41.680> also 00:11:42.670 --> 00:11:42.680 align:start position:0% approach and pay a premium for that also 00:11:42.680 --> 00:11:44.949 align:start position:0% approach and pay a premium for that also the<00:11:42.860> other<00:11:42.980> things<00:11:43.249> you<00:11:43.370> see<00:11:43.550> here<00:11:43.879> like<00:11:44.420> data 00:11:44.949 --> 00:11:44.959 align:start position:0% the other things you see here like data 00:11:44.959 --> 00:11:46.809 align:start position:0% the other things you see here like data security<00:11:45.589> so<00:11:45.949> the<00:11:46.129> authenticity<00:11:46.370> proofs 00:11:46.809 --> 00:11:46.819 align:start position:0% security so the authenticity proofs 00:11:46.819 --> 00:11:48.999 align:start position:0% security so the authenticity proofs approach<00:11:47.120> and<00:11:47.360> more<00:11:47.839> they<00:11:48.230> are<00:11:48.259> all<00:11:48.529> like 00:11:48.999 --> 00:11:49.009 align:start position:0% approach and more they are all like 00:11:49.009 --> 00:11:50.650 align:start position:0% approach and more they are all like critical<00:11:49.699> components<00:11:50.149> that<00:11:50.209> are<00:11:50.329> needed 00:11:50.650 --> 00:11:50.660 align:start position:0% critical components that are needed 00:11:50.660 --> 00:11:51.970 align:start position:0% critical components that are needed because<00:11:50.839> you<00:11:51.050> don't<00:11:51.230> want<00:11:51.410> to<00:11:51.529> compromise<00:11:51.680> the 00:11:51.970 --> 00:11:51.980 align:start position:0% because you don't want to compromise the 00:11:51.980 --> 00:11:53.850 align:start position:0% because you don't want to compromise the security<00:11:52.220> of<00:11:52.550> your<00:11:52.610> smart<00:11:52.939> contract<00:11:53.300> again 00:11:53.850 --> 00:11:53.860 align:start position:0% security of your smart contract again 00:11:53.860 --> 00:11:59.799 align:start position:0% security of your smart contract again and<00:11:56.589> also<00:11:57.910> reputation<00:11:58.910> systems<00:11:59.360> of<00:11:59.540> course 00:11:59.799 --> 00:11:59.809 align:start position:0% and also reputation systems of course 00:11:59.809 --> 00:12:02.110 align:start position:0% and also reputation systems of course are<00:12:00.019> something<00:12:00.589> that<00:12:00.620> is<00:12:00.860> often<00:12:01.129> mentioned 00:12:02.110 --> 00:12:02.120 align:start position:0% are something that is often mentioned 00:12:02.120 --> 00:12:07.569 align:start position:0% are something that is often mentioned and<00:12:02.269> that<00:12:02.839> somehow<00:12:03.579> is<00:12:04.809> part<00:12:05.809> of<00:12:06.079> those<00:12:06.709> Oracle 00:12:07.569 --> 00:12:07.579 align:start position:0% and that somehow is part of those Oracle 00:12:07.579 --> 00:12:09.309 align:start position:0% and that somehow is part of those Oracle systems<00:12:07.970> that<00:12:08.180> are<00:12:08.329> being<00:12:08.509> implemented<00:12:08.930> and 00:12:09.309 --> 00:12:09.319 align:start position:0% systems that are being implemented and 00:12:09.319 --> 00:12:11.679 align:start position:0% systems that are being implemented and where<00:12:10.129> the<00:12:10.249> ease<00:12:10.370> of<00:12:10.399> use<00:12:10.699> as<00:12:10.879> well<00:12:11.089> because<00:12:11.569> he 00:12:11.679 --> 00:12:11.689 align:start position:0% where the ease of use as well because he 00:12:11.689 --> 00:12:14.499 align:start position:0% where the ease of use as well because he really<00:12:11.930> wants<00:12:12.199> to<00:12:12.259> you<00:12:12.949> know<00:12:13.069> you<00:12:14.029> don't<00:12:14.209> want 00:12:14.499 --> 00:12:14.509 align:start position:0% really wants to you know you don't want 00:12:14.509 --> 00:12:17.710 align:start position:0% really wants to you know you don't want the<00:12:14.779> Oracle<00:12:15.470> components<00:12:16.040> to<00:12:16.519> complicate<00:12:17.509> too 00:12:17.710 --> 00:12:17.720 align:start position:0% the Oracle components to complicate too 00:12:17.720 --> 00:12:19.720 align:start position:0% the Oracle components to complicate too much<00:12:17.930> the<00:12:18.319> way<00:12:18.470> your<00:12:18.679> application<00:12:18.980> is 00:12:19.720 --> 00:12:19.730 align:start position:0% much the way your application is 00:12:19.730 --> 00:12:24.519 align:start position:0% much the way your application is structure<00:12:21.009> so<00:12:23.079> so<00:12:24.079> basically<00:12:24.199> the 00:12:24.519 --> 00:12:24.529 align:start position:0% structure so so basically the 00:12:24.529 --> 00:12:26.499 align:start position:0% structure so so basically the technologies<00:12:24.949> as<00:12:25.279> I<00:12:25.370> said<00:12:25.519> that<00:12:25.670> we<00:12:25.819> work<00:12:26.329> with 00:12:26.499 --> 00:12:26.509 align:start position:0% technologies as I said that we work with 00:12:26.509 --> 00:12:28.720 align:start position:0% technologies as I said that we work with are<00:12:26.660> basically<00:12:27.309> blockchain<00:12:28.309> in<00:12:28.399> general 00:12:28.720 --> 00:12:28.730 align:start position:0% are basically blockchain in general 00:12:28.730 --> 00:12:30.069 align:start position:0% are basically blockchain in general because<00:12:28.970> we<00:12:29.089> don't<00:12:29.269> integrate<00:12:29.509> just<00:12:29.870> with<00:12:30.050> a 00:12:30.069 --> 00:12:30.079 align:start position:0% because we don't integrate just with a 00:12:30.079 --> 00:12:32.169 align:start position:0% because we don't integrate just with a theorem<00:12:30.439> we<00:12:30.860> have<00:12:30.920> integrations<00:12:31.490> with<00:12:31.670> a<00:12:31.999> few 00:12:32.169 --> 00:12:32.179 align:start position:0% theorem we have integrations with a few 00:12:32.179 --> 00:12:33.850 align:start position:0% theorem we have integrations with a few blocks<00:12:32.360> but<00:12:32.959> the<00:12:33.019> theorem<00:12:33.319> is<00:12:33.439> the<00:12:33.470> one<00:12:33.679> with 00:12:33.850 --> 00:12:33.860 align:start position:0% blocks but the theorem is the one with 00:12:33.860 --> 00:12:36.189 align:start position:0% blocks but the theorem is the one with most<00:12:34.100> of<00:12:34.189> the<00:12:34.309> traction<00:12:34.550> and<00:12:35.199> trusted 00:12:36.189 --> 00:12:36.199 align:start position:0% most of the traction and trusted 00:12:36.199 --> 00:12:37.869 align:start position:0% most of the traction and trusted execution<00:12:36.379> environments<00:12:37.249> so<00:12:37.519> trusted 00:12:37.869 --> 00:12:37.879 align:start position:0% execution environments so trusted 00:12:37.879 --> 00:12:43.049 align:start position:0% execution environments so trusted computing<00:12:38.120> techniques<00:12:38.569> of<00:12:38.809> different<00:12:39.679> kinds 00:12:43.049 --> 00:12:43.059 align:start position:0% 00:12:43.059 --> 00:12:47.790 align:start position:0% so<00:12:45.040> at<00:12:46.040> the<00:12:46.279> moment<00:12:46.429> we<00:12:46.730> have<00:12:46.850> approximately 00:12:47.790 --> 00:12:47.800 align:start position:0% so at the moment we have approximately 00:12:47.800 --> 00:12:51.340 align:start position:0% so at the moment we have approximately 200<00:12:48.800> projects<00:12:49.610> that<00:12:50.209> are<00:12:50.449> reaching<00:12:50.870> out<00:12:51.019> to 00:12:51.340 --> 00:12:51.350 align:start position:0% 200 projects that are reaching out to 00:12:51.350 --> 00:12:53.739 align:start position:0% 200 projects that are reaching out to provable<00:12:52.040> every<00:12:52.429> month<00:12:52.639> from<00:12:53.209> their<00:12:53.480> smart 00:12:53.739 --> 00:12:53.749 align:start position:0% provable every month from their smart 00:12:53.749 --> 00:12:55.720 align:start position:0% provable every month from their smart contracts<00:12:54.170> to<00:12:54.319> to<00:12:54.620> get<00:12:54.800> real-world<00:12:55.069> data<00:12:55.370> and 00:12:55.720 --> 00:12:55.730 align:start position:0% contracts to to get real-world data and 00:12:55.730 --> 00:13:00.220 align:start position:0% contracts to to get real-world data and as<00:12:56.629> I<00:12:57.079> said<00:12:57.139> most<00:12:57.620> of<00:12:57.829> them<00:12:58.040> are<00:12:58.660> around<00:12:59.660> like 00:13:00.220 --> 00:13:00.230 align:start position:0% as I said most of them are around like 00:13:00.230 --> 00:13:02.379 align:start position:0% as I said most of them are around like the<00:13:00.350> generation<00:13:00.740> of<00:13:00.800> random<00:13:01.160> numbers<00:13:01.490> price 00:13:02.379 --> 00:13:02.389 align:start position:0% the generation of random numbers price 00:13:02.389 --> 00:13:05.889 align:start position:0% the generation of random numbers price feeds<00:13:02.720> or<00:13:03.009> like<00:13:04.009> a<00:13:04.040> variety<00:13:04.370> of<00:13:04.730> web<00:13:05.240> API<00:13:05.569> calls 00:13:05.889 --> 00:13:05.899 align:start position:0% feeds or like a variety of web API calls 00:13:05.899 --> 00:13:09.100 align:start position:0% feeds or like a variety of web API calls that<00:13:06.170> connect<00:13:07.160> some<00:13:07.910> advanced<00:13:08.449> like<00:13:08.839> off 00:13:09.100 --> 00:13:09.110 align:start position:0% that connect some advanced like off 00:13:09.110 --> 00:13:12.369 align:start position:0% that connect some advanced like off chain<00:13:09.550> computations<00:13:10.550> typically<00:13:11.029> with<00:13:11.480> the<00:13:11.689> on 00:13:12.369 --> 00:13:12.379 align:start position:0% chain computations typically with the on 00:13:12.379 --> 00:13:14.230 align:start position:0% chain computations typically with the on chain<00:13:12.709> smart<00:13:12.980> contracts<00:13:13.399> that<00:13:13.519> may<00:13:13.699> just<00:13:13.910> you 00:13:14.230 --> 00:13:14.240 align:start position:0% chain smart contracts that may just you 00:13:14.240 --> 00:13:19.119 align:start position:0% chain smart contracts that may just you know<00:13:14.329> release<00:13:14.629> a<00:13:14.660> payment<00:13:16.929> so<00:13:17.929> Oracle<00:13:18.889> is 00:13:19.119 --> 00:13:19.129 align:start position:0% know release a payment so Oracle is 00:13:19.129 --> 00:13:20.679 align:start position:0% know release a payment so Oracle is currently<00:13:19.429> integrated<00:13:19.879> with<00:13:20.029> it'll<00:13:20.360> may<00:13:20.509> not 00:13:20.679 --> 00:13:20.689 align:start position:0% currently integrated with it'll may not 00:13:20.689 --> 00:13:22.840 align:start position:0% currently integrated with it'll may not but<00:13:20.839> also<00:13:21.050> with<00:13:21.350> many<00:13:21.529> test<00:13:21.769> nets<00:13:21.980> basically 00:13:22.840 --> 00:13:22.850 align:start position:0% but also with many test nets basically 00:13:22.850 --> 00:13:27.040 align:start position:0% but also with many test nets basically all<00:13:23.120> the<00:13:23.870> main<00:13:24.199> etherium<00:13:25.299> testaments 00:13:27.040 --> 00:13:27.050 align:start position:0% all the main etherium testaments 00:13:27.050 --> 00:13:30.730 align:start position:0% all the main etherium testaments and<00:13:27.140> also<00:13:27.740> with<00:13:28.420> like<00:13:29.420> other<00:13:30.200> Oracle's 00:13:30.730 --> 00:13:30.740 align:start position:0% and also with like other Oracle's 00:13:30.740 --> 00:13:36.940 align:start position:0% and also with like other Oracle's Network<00:13:31.040> and<00:13:31.459> with<00:13:31.700> some<00:13:32.450> side<00:13:32.839> chains<00:13:35.709> so<00:13:36.709> we 00:13:36.940 --> 00:13:36.950 align:start position:0% Network and with some side chains so we 00:13:36.950 --> 00:13:38.320 align:start position:0% Network and with some side chains so we have<00:13:37.130> focused<00:13:37.550> a<00:13:37.580> lot<00:13:37.730> in<00:13:37.880> the<00:13:37.970> last<00:13:38.060> few<00:13:38.180> years 00:13:38.320 --> 00:13:38.330 align:start position:0% have focused a lot in the last few years 00:13:38.330 --> 00:13:40.269 align:start position:0% have focused a lot in the last few years on<00:13:38.600> the<00:13:38.870> random<00:13:39.110> number<00:13:39.470> generation<00:13:39.800> use<00:13:40.070> case 00:13:40.269 --> 00:13:40.279 align:start position:0% on the random number generation use case 00:13:40.279 --> 00:13:44.019 align:start position:0% on the random number generation use case because<00:13:40.970> it's<00:13:41.240> actually<00:13:41.860> a<00:13:42.860> strong<00:13:43.579> need<00:13:43.820> and 00:13:44.019 --> 00:13:44.029 align:start position:0% because it's actually a strong need and 00:13:44.029 --> 00:13:45.009 align:start position:0% because it's actually a strong need and it<00:13:44.089> has<00:13:44.209> been<00:13:44.420> one<00:13:44.600> of<00:13:44.630> the<00:13:44.839> first 00:13:45.009 --> 00:13:45.019 align:start position:0% it has been one of the first 00:13:45.019 --> 00:13:46.660 align:start position:0% it has been one of the first applications<00:13:45.649> getting<00:13:45.980> some<00:13:46.160> traction<00:13:46.370> in 00:13:46.660 --> 00:13:46.670 align:start position:0% applications getting some traction in 00:13:46.670 --> 00:13:48.639 align:start position:0% applications getting some traction in the<00:13:47.000> etherium<00:13:47.300> space<00:13:47.510> and<00:13:47.750> before<00:13:48.380> also<00:13:48.529> in 00:13:48.639 --> 00:13:48.649 align:start position:0% the etherium space and before also in 00:13:48.649 --> 00:13:50.650 align:start position:0% the etherium space and before also in the<00:13:48.740> Bitcoin<00:13:48.920> space<00:13:49.180> if<00:13:50.180> you<00:13:50.269> think<00:13:50.540> of 00:13:50.650 --> 00:13:50.660 align:start position:0% the Bitcoin space if you think of 00:13:50.660 --> 00:13:53.139 align:start position:0% the Bitcoin space if you think of Satoshi<00:13:51.019> dice<00:13:51.110> which<00:13:51.860> was<00:13:52.070> like<00:13:52.310> the<00:13:52.519> first 00:13:53.139 --> 00:13:53.149 align:start position:0% Satoshi dice which was like the first 00:13:53.149 --> 00:13:56.620 align:start position:0% Satoshi dice which was like the first application<00:13:53.750> on<00:13:53.959> Bitcoin<00:13:54.649> death<00:13:55.310> caused<00:13:56.060> like 00:13:56.620 --> 00:13:56.630 align:start position:0% application on Bitcoin death caused like 00:13:56.630 --> 00:13:59.759 align:start position:0% application on Bitcoin death caused like a<00:13:56.660> spike<00:13:57.050> in<00:13:57.290> the<00:13:57.410> transaction<00:13:57.920> volumes<00:13:58.160> in 00:13:59.759 --> 00:13:59.769 align:start position:0% a spike in the transaction volumes in 00:13:59.769 --> 00:14:04.569 align:start position:0% a spike in the transaction volumes in 2012<00:14:01.810> so<00:14:02.810> the<00:14:03.170> technology<00:14:03.649> we<00:14:04.010> have<00:14:04.130> used<00:14:04.339> to 00:14:04.569 --> 00:14:04.579 align:start position:0% 2012 so the technology we have used to 00:14:04.579 --> 00:14:07.060 align:start position:0% 2012 so the technology we have used to like<00:14:05.120> provide<00:14:05.480> the<00:14:05.779> provable<00:14:06.350> random<00:14:06.800> number 00:14:07.060 --> 00:14:07.070 align:start position:0% like provide the provable random number 00:14:07.070 --> 00:14:08.949 align:start position:0% like provide the provable random number generator<00:14:07.430> which<00:14:07.970> is<00:14:08.000> a<00:14:08.149> part<00:14:08.390> of<00:14:08.480> the<00:14:08.630> Oracle 00:14:08.949 --> 00:14:08.959 align:start position:0% generator which is a part of the Oracle 00:14:08.959 --> 00:14:11.079 align:start position:0% generator which is a part of the Oracle are<00:14:09.170> the<00:14:09.470> ones<00:14:09.649> you<00:14:09.769> see<00:14:09.950> mention<00:14:10.250> here<00:14:10.519> so 00:14:11.079 --> 00:14:11.089 align:start position:0% are the ones you see mention here so 00:14:11.089 --> 00:14:13.329 align:start position:0% are the ones you see mention here so it's<00:14:11.480> quite<00:14:11.690> interesting<00:14:11.930> the<00:14:12.829> use<00:14:13.010> of<00:14:13.190> the 00:14:13.329 --> 00:14:13.339 align:start position:0% it's quite interesting the use of the 00:14:13.339 --> 00:14:16.420 align:start position:0% it's quite interesting the use of the ledger<00:14:14.180> te<00:14:14.510> because<00:14:15.260> most<00:14:15.500> of<00:14:15.589> us<00:14:15.769> know<00:14:16.190> the 00:14:16.420 --> 00:14:16.430 align:start position:0% ledger te because most of us know the 00:14:16.430 --> 00:14:18.610 align:start position:0% ledger te because most of us know the legend<00:14:16.790> an<00:14:16.910> OS<00:14:17.120> has<00:14:17.360> the<00:14:17.990> you<00:14:18.170> know<00:14:18.260> Hardware 00:14:18.610 --> 00:14:18.620 align:start position:0% legend an OS has the you know Hardware 00:14:18.620 --> 00:14:21.579 align:start position:0% legend an OS has the you know Hardware wallet<00:14:18.950> to<00:14:19.550> secure<00:14:20.180> you<00:14:20.540> know<00:14:20.660> if<00:14:20.899> or<00:14:21.230> other 00:14:21.579 --> 00:14:21.589 align:start position:0% wallet to secure you know if or other 00:14:21.589 --> 00:14:24.280 align:start position:0% wallet to secure you know if or other tokens<00:14:22.010> but<00:14:22.970> the<00:14:23.089> reality<00:14:23.480> is<00:14:23.510> that<00:14:23.600> the 00:14:24.280 --> 00:14:24.290 align:start position:0% tokens but the reality is that the 00:14:24.290 --> 00:14:26.350 align:start position:0% tokens but the reality is that the security<00:14:24.950> guarantee<00:14:25.610> is<00:14:25.670> provided<00:14:26.149> by<00:14:26.300> the 00:14:26.350 --> 00:14:26.360 align:start position:0% security guarantee is provided by the 00:14:26.360 --> 00:14:28.509 align:start position:0% security guarantee is provided by the legend<00:14:26.750> an<00:14:26.870> OS<00:14:27.050> could<00:14:27.680> be<00:14:27.800> used<00:14:28.010> for<00:14:28.190> custom 00:14:28.509 --> 00:14:28.519 align:start position:0% legend an OS could be used for custom 00:14:28.519 --> 00:14:29.980 align:start position:0% legend an OS could be used for custom applications<00:14:29.029> and<00:14:29.240> you<00:14:29.600> can<00:14:29.779> really 00:14:29.980 --> 00:14:29.990 align:start position:0% applications and you can really 00:14:29.990 --> 00:14:32.139 align:start position:0% applications and you can really implement<00:14:30.110> anything<00:14:30.589> within<00:14:31.579> the<00:14:31.850> safe 00:14:32.139 --> 00:14:32.149 align:start position:0% implement anything within the safe 00:14:32.149 --> 00:14:34.690 align:start position:0% implement anything within the safe boundaries<00:14:32.600> of<00:14:32.779> the<00:14:32.899> legend<00:14:33.230> an<00:14:33.350> OS<00:14:33.529> Y<00:14:34.160> proving 00:14:34.690 --> 00:14:34.700 align:start position:0% boundaries of the legend an OS Y proving 00:14:34.700 --> 00:14:36.760 align:start position:0% boundaries of the legend an OS Y proving to<00:14:34.880> third<00:14:35.060> parties<00:14:35.570> that<00:14:36.230> you<00:14:36.560> know<00:14:36.649> the 00:14:36.760 --> 00:14:36.770 align:start position:0% to third parties that you know the 00:14:36.770 --> 00:14:38.139 align:start position:0% to third parties that you know the application<00:14:37.220> was<00:14:37.370> really<00:14:37.610> running<00:14:37.790> on<00:14:38.120> a 00:14:38.139 --> 00:14:38.149 align:start position:0% application was really running on a 00:14:38.149 --> 00:14:40.510 align:start position:0% application was really running on a legend<00:14:38.570> an<00:14:38.720> OS<00:14:38.870> with<00:14:39.170> North<00:14:39.380> durations<00:14:39.770> so 00:14:40.510 --> 00:14:40.520 align:start position:0% legend an OS with North durations so 00:14:40.520 --> 00:14:41.980 align:start position:0% legend an OS with North durations so this<00:14:40.700> is<00:14:40.820> what<00:14:40.970> we<00:14:41.089> are<00:14:41.149> using<00:14:41.329> for<00:14:41.600> the<00:14:41.720> random 00:14:41.980 --> 00:14:41.990 align:start position:0% this is what we are using for the random 00:14:41.990 --> 00:14:46.240 align:start position:0% this is what we are using for the random number<00:14:42.260> generator<00:14:42.290> for<00:14:42.950> instance<00:14:45.100> these<00:14:46.100> are 00:14:46.240 --> 00:14:46.250 align:start position:0% number generator for instance these are 00:14:46.250 --> 00:14:48.250 align:start position:0% number generator for instance these are the<00:14:46.430> networks<00:14:46.790> I<00:14:46.970> was<00:14:47.300> mentioning<00:14:47.510> where<00:14:47.990> we 00:14:48.250 --> 00:14:48.260 align:start position:0% the networks I was mentioning where we 00:14:48.260 --> 00:14:51.430 align:start position:0% the networks I was mentioning where we are<00:14:48.670> integrated<00:14:49.670> as<00:14:49.820> you<00:14:50.720> see<00:14:50.899> we<00:14:51.020> also<00:14:51.170> have 00:14:51.430 --> 00:14:51.440 align:start position:0% are integrated as you see we also have 00:14:51.440 --> 00:14:53.410 align:start position:0% are integrated as you see we also have like<00:14:51.680> other<00:14:51.920> ATM<00:14:52.339> based<00:14:52.459> networks<00:14:52.670> such<00:14:53.390> as 00:14:53.410 --> 00:14:53.420 align:start position:0% like other ATM based networks such as 00:14:53.420 --> 00:14:56.710 align:start position:0% like other ATM based networks such as our<00:14:53.899> SK<00:14:54.230> but<00:14:54.890> also<00:14:55.520> other<00:14:55.880> networks<00:14:56.300> which<00:14:56.510> are 00:14:56.710 --> 00:14:56.720 align:start position:0% our SK but also other networks which are 00:14:56.720 --> 00:15:00.300 align:start position:0% our SK but also other networks which are not<00:14:57.140> a<00:14:57.440> tea<00:14:57.829> room<00:14:57.980> based<00:14:58.250> EDM<00:14:59.149> based<00:14:59.360> such<00:14:59.839> as 00:15:00.300 --> 00:15:00.310 align:start position:0% not a tea room based EDM based such as 00:15:00.310 --> 00:15:06.660 align:start position:0% not a tea room based EDM based such as us<00:15:01.310> art<00:15:02.120> record<00:15:02.510> fabric<00:15:03.350> and<00:15:03.680> others<00:15:05.170> so<00:15:06.170> um 00:15:06.660 --> 00:15:06.670 align:start position:0% us art record fabric and others so um 00:15:06.670 --> 00:15:10.030 align:start position:0% us art record fabric and others so um everyone<00:15:07.670> is<00:15:07.850> discussing<00:15:08.690> this<00:15:09.350> year<00:15:09.620> about 00:15:10.030 --> 00:15:10.040 align:start position:0% everyone is discussing this year about 00:15:10.040 --> 00:15:12.400 align:start position:0% everyone is discussing this year about defy<00:15:10.699> which<00:15:11.000> is<00:15:11.120> really<00:15:11.329> a<00:15:11.420> new<00:15:11.810> term<00:15:12.110> for 00:15:12.400 --> 00:15:12.410 align:start position:0% defy which is really a new term for 00:15:12.410 --> 00:15:13.840 align:start position:0% defy which is really a new term for something<00:15:12.649> that<00:15:12.829> you<00:15:13.130> know<00:15:13.250> we<00:15:13.610> have<00:15:13.699> always 00:15:13.840 --> 00:15:13.850 align:start position:0% something that you know we have always 00:15:13.850 --> 00:15:16.060 align:start position:0% something that you know we have always discussed<00:15:14.209> which<00:15:14.870> is<00:15:14.899> the<00:15:15.290> potential<00:15:15.709> of 00:15:16.060 --> 00:15:16.070 align:start position:0% discussed which is the potential of 00:15:16.070 --> 00:15:18.250 align:start position:0% discussed which is the potential of decentralized<00:15:16.910> financial<00:15:17.630> applications<00:15:18.110> in 00:15:18.250 --> 00:15:18.260 align:start position:0% decentralized financial applications in 00:15:18.260 --> 00:15:24.400 align:start position:0% decentralized financial applications in this<00:15:18.709> space<00:15:19.720> so<00:15:20.720> I<00:15:21.170> found<00:15:22.040> that<00:15:22.570> tweet<00:15:23.570> a<00:15:23.899> few 00:15:24.400 --> 00:15:24.410 align:start position:0% this space so I found that tweet a few 00:15:24.410 --> 00:15:27.550 align:start position:0% this space so I found that tweet a few months<00:15:24.589> ago<00:15:24.680> quite<00:15:24.980> interesting<00:15:25.600> as<00:15:26.600> it's 00:15:27.550 --> 00:15:27.560 align:start position:0% months ago quite interesting as it's 00:15:27.560 --> 00:15:29.410 align:start position:0% months ago quite interesting as it's basically<00:15:27.890> showing<00:15:28.220> as<00:15:28.550> we<00:15:29.089> have<00:15:29.180> seen<00:15:29.329> in 00:15:29.410 --> 00:15:29.420 align:start position:0% basically showing as we have seen in 00:15:29.420 --> 00:15:32.290 align:start position:0% basically showing as we have seen in other<00:15:29.510> presentations<00:15:30.110> as<00:15:30.260> well<00:15:30.440> that<00:15:31.300> like 00:15:32.290 --> 00:15:32.300 align:start position:0% other presentations as well that like 00:15:32.300 --> 00:15:37.180 align:start position:0% other presentations as well that like the<00:15:33.170> composability<00:15:33.740> of<00:15:34.160> those<00:15:34.550> defy<00:15:35.620> tools<00:15:36.620> is 00:15:37.180 --> 00:15:37.190 align:start position:0% the composability of those defy tools is 00:15:37.190 --> 00:15:39.069 align:start position:0% the composability of those defy tools is somehow<00:15:37.610> leading<00:15:38.209> to<00:15:38.360> many<00:15:38.570> interesting<00:15:38.779> use 00:15:39.069 --> 00:15:39.079 align:start position:0% somehow leading to many interesting use 00:15:39.079 --> 00:15:40.960 align:start position:0% somehow leading to many interesting use cases<00:15:39.320> and<00:15:39.589> everyone<00:15:40.279> is<00:15:40.490> building 00:15:40.960 --> 00:15:40.970 align:start position:0% cases and everyone is building 00:15:40.970 --> 00:15:42.759 align:start position:0% cases and everyone is building on<00:15:41.029> top<00:15:41.269> of<00:15:41.509> other<00:15:41.870> components<00:15:42.350> that<00:15:42.589> are 00:15:42.759 --> 00:15:42.769 align:start position:0% on top of other components that are 00:15:42.769 --> 00:15:45.879 align:start position:0% on top of other components that are built<00:15:42.800> by<00:15:43.220> other<00:15:43.399> teams<00:15:43.699> so<00:15:44.680> thinking<00:15:45.680> about 00:15:45.879 --> 00:15:45.889 align:start position:0% built by other teams so thinking about 00:15:45.889 --> 00:15:49.600 align:start position:0% built by other teams so thinking about that<00:15:46.129> I<00:15:46.839> think<00:15:47.839> we<00:15:47.959> could<00:15:48.139> really<00:15:48.199> split<00:15:49.069> the 00:15:49.600 --> 00:15:49.610 align:start position:0% that I think we could really split the 00:15:49.610 --> 00:15:52.240 align:start position:0% that I think we could really split the needs<00:15:49.850> of<00:15:50.029> defy<00:15:50.569> into<00:15:51.439> categories<00:15:51.889> so<00:15:52.129> the 00:15:52.240 --> 00:15:52.250 align:start position:0% needs of defy into categories so the 00:15:52.250 --> 00:15:54.100 align:start position:0% needs of defy into categories so the first<00:15:52.490> one<00:15:52.639> is<00:15:52.819> the<00:15:53.240> engine<00:15:53.600> which<00:15:53.810> is<00:15:53.839> like 00:15:54.100 --> 00:15:54.110 align:start position:0% first one is the engine which is like 00:15:54.110 --> 00:15:55.929 align:start position:0% first one is the engine which is like the<00:15:54.319> platform<00:15:54.800> where<00:15:54.980> you<00:15:55.160> want<00:15:55.430> to<00:15:55.610> run<00:15:55.759> the 00:15:55.929 --> 00:15:55.939 align:start position:0% the platform where you want to run the 00:15:55.939 --> 00:15:59.319 align:start position:0% the platform where you want to run the defy<00:15:56.329> tool<00:15:57.319> and<00:15:57.560> at<00:15:58.399> the<00:15:58.519> moment<00:15:58.670> it's<00:15:59.060> mostly 00:15:59.319 --> 00:15:59.329 align:start position:0% defy tool and at the moment it's mostly 00:15:59.329 --> 00:16:01.329 align:start position:0% defy tool and at the moment it's mostly tedium<00:15:59.689> right<00:15:59.870> so<00:16:00.199> we<00:16:00.410> have<00:16:00.500> something<00:16:00.740> that<00:16:01.009> I 00:16:01.329 --> 00:16:01.339 align:start position:0% tedium right so we have something that I 00:16:01.339 --> 00:16:04.240 align:start position:0% tedium right so we have something that I like<00:16:01.670> on<00:16:01.930> eros<00:16:02.930> but<00:16:03.620> it's<00:16:03.860> still<00:16:04.009> quite 00:16:04.240 --> 00:16:04.250 align:start position:0% like on eros but it's still quite 00:16:04.250 --> 00:16:04.840 align:start position:0% like on eros but it's still quite limited 00:16:04.840 --> 00:16:04.850 align:start position:0% limited 00:16:04.850 --> 00:16:07.569 align:start position:0% limited why<00:16:05.149> because<00:16:06.019> on<00:16:06.319> on<00:16:06.620> you<00:16:06.769> don't<00:16:07.069> really<00:16:07.339> have 00:16:07.569 --> 00:16:07.579 align:start position:0% why because on on you don't really have 00:16:07.579 --> 00:16:10.210 align:start position:0% why because on on you don't really have other<00:16:08.139> you<00:16:09.139> know<00:16:09.230> the<00:16:09.350> rest<00:16:09.529> of<00:16:09.649> the<00:16:09.769> ecosystem 00:16:10.210 --> 00:16:10.220 align:start position:0% other you know the rest of the ecosystem 00:16:10.220 --> 00:16:11.110 align:start position:0% other you know the rest of the ecosystem is<00:16:10.339> sort<00:16:10.519> of<00:16:10.610> missing 00:16:11.110 --> 00:16:11.120 align:start position:0% is sort of missing 00:16:11.120 --> 00:16:13.569 align:start position:0% is sort of missing so<00:16:11.569> a<00:16:11.600> tedium<00:16:11.959> got<00:16:12.410> a<00:16:12.620> lot<00:16:12.829> of<00:16:12.860> traction<00:16:13.160> for 00:16:13.569 --> 00:16:13.579 align:start position:0% so a tedium got a lot of traction for 00:16:13.579 --> 00:16:16.210 align:start position:0% so a tedium got a lot of traction for different<00:16:14.089> reasons<00:16:14.449> for<00:16:14.899> the<00:16:15.410> technology<00:16:15.980> but 00:16:16.210 --> 00:16:16.220 align:start position:0% different reasons for the technology but 00:16:16.220 --> 00:16:18.879 align:start position:0% different reasons for the technology but I<00:16:16.430> would<00:16:16.910> say<00:16:17.089> that<00:16:17.360> one<00:16:17.750> of<00:16:17.779> the<00:16:17.990> main<00:16:18.589> points 00:16:18.879 --> 00:16:18.889 align:start position:0% I would say that one of the main points 00:16:18.889 --> 00:16:21.429 align:start position:0% I would say that one of the main points in<00:16:19.189> favor<00:16:19.310> of<00:16:19.610> a<00:16:19.819> team<00:16:20.029> today<00:16:20.180> is<00:16:20.480> the<00:16:21.079> huge 00:16:21.429 --> 00:16:21.439 align:start position:0% in favor of a team today is the huge 00:16:21.439 --> 00:16:23.740 align:start position:0% in favor of a team today is the huge like<00:16:21.920> developers<00:16:22.459> base<00:16:22.699> and<00:16:23.000> the<00:16:23.269> user<00:16:23.449> base 00:16:23.740 --> 00:16:23.750 align:start position:0% like developers base and the user base 00:16:23.750 --> 00:16:25.420 align:start position:0% like developers base and the user base and<00:16:24.019> the<00:16:24.110> fact<00:16:24.290> that<00:16:24.350> we<00:16:24.560> already<00:16:24.649> have<00:16:24.949> some 00:16:25.420 --> 00:16:25.430 align:start position:0% and the fact that we already have some 00:16:25.430 --> 00:16:27.249 align:start position:0% and the fact that we already have some initial<00:16:25.579> traction<00:16:25.970> differently<00:16:26.959> than<00:16:27.110> other 00:16:27.249 --> 00:16:27.259 align:start position:0% initial traction differently than other 00:16:27.259 --> 00:16:30.100 align:start position:0% initial traction differently than other blushes<00:16:27.529> so<00:16:28.220> this<00:16:28.790> is<00:16:28.939> probably<00:16:29.660> one<00:16:29.870> of<00:16:29.899> the 00:16:30.100 --> 00:16:30.110 align:start position:0% blushes so this is probably one of the 00:16:30.110 --> 00:16:32.230 align:start position:0% blushes so this is probably one of the main<00:16:30.259> reasons<00:16:30.620> why<00:16:30.740> defy<00:16:31.220> is<00:16:31.459> being<00:16:32.000> built 00:16:32.230 --> 00:16:32.240 align:start position:0% main reasons why defy is being built 00:16:32.240 --> 00:16:34.030 align:start position:0% main reasons why defy is being built there<00:16:32.480> and<00:16:32.720> why<00:16:33.019> there<00:16:33.199> are<00:16:33.290> so<00:16:33.500> many<00:16:33.649> new 00:16:34.030 --> 00:16:34.040 align:start position:0% there and why there are so many new 00:16:34.040 --> 00:16:36.519 align:start position:0% there and why there are so many new tools<00:16:34.220> that<00:16:34.519> are<00:16:34.879> being<00:16:35.120> built<00:16:35.329> there 00:16:36.519 --> 00:16:36.529 align:start position:0% tools that are being built there 00:16:36.529 --> 00:16:38.230 align:start position:0% tools that are being built there so<00:16:36.860> interoperability<00:16:37.519> of<00:16:37.730> blockchain<00:16:38.209> and 00:16:38.230 --> 00:16:38.240 align:start position:0% so interoperability of blockchain and 00:16:38.240 --> 00:16:41.230 align:start position:0% so interoperability of blockchain and composability<00:16:38.899> of<00:16:39.350> those<00:16:40.129> defy<00:16:40.550> tools<00:16:40.790> are 00:16:41.230 --> 00:16:41.240 align:start position:0% composability of those defy tools are 00:16:41.240 --> 00:16:44.679 align:start position:0% composability of those defy tools are helping<00:16:41.720> to<00:16:41.990> like<00:16:42.529> grow<00:16:42.829> significantly<00:16:43.689> the 00:16:44.679 --> 00:16:44.689 align:start position:0% helping to like grow significantly the 00:16:44.689 --> 00:16:47.139 align:start position:0% helping to like grow significantly the relevance<00:16:45.379> of<00:16:45.559> define<00:16:46.069> in<00:16:46.189> general<00:16:46.550> so<00:16:47.000> the 00:16:47.139 --> 00:16:47.149 align:start position:0% relevance of define in general so the 00:16:47.149 --> 00:16:48.610 align:start position:0% relevance of define in general so the first<00:16:47.360> thing<00:16:47.480> you<00:16:47.569> need<00:16:47.720> is<00:16:47.870> like<00:16:48.050> the<00:16:48.259> engine 00:16:48.610 --> 00:16:48.620 align:start position:0% first thing you need is like the engine 00:16:48.620 --> 00:16:50.949 align:start position:0% first thing you need is like the engine as<00:16:48.800> I<00:16:48.860> said<00:16:49.250> which<00:16:49.639> today<00:16:50.209> is<00:16:50.420> a<00:16:50.449> theorem<00:16:50.809> and 00:16:50.949 --> 00:16:50.959 align:start position:0% as I said which today is a theorem and 00:16:50.959 --> 00:16:53.319 align:start position:0% as I said which today is a theorem and that<00:16:51.470> that's<00:16:51.980> fine<00:16:52.220> as<00:16:52.490> there<00:16:52.939> doesn't<00:16:53.300> seem 00:16:53.319 --> 00:16:53.329 align:start position:0% that that's fine as there doesn't seem 00:16:53.329 --> 00:16:56.439 align:start position:0% that that's fine as there doesn't seem to<00:16:53.480> be<00:16:53.750> like<00:16:54.259> requests<00:16:54.740> from<00:16:54.860> the<00:16:54.949> users<00:16:55.370> to<00:16:55.850> to 00:16:56.439 --> 00:16:56.449 align:start position:0% to be like requests from the users to to 00:16:56.449 --> 00:16:58.269 align:start position:0% to be like requests from the users to to move<00:16:56.600> it<00:16:56.720> as<00:16:56.870> well<00:16:57.079> so<00:16:57.379> that's<00:16:57.559> that's<00:16:58.040> where 00:16:58.269 --> 00:16:58.279 align:start position:0% move it as well so that's that's where 00:16:58.279 --> 00:17:00.819 align:start position:0% move it as well so that's that's where we<00:16:58.430> are<00:16:58.550> building<00:16:58.930> and<00:16:59.930> then<00:17:00.170> you<00:17:00.290> need<00:17:00.439> assets 00:17:00.819 --> 00:17:00.829 align:start position:0% we are building and then you need assets 00:17:00.829 --> 00:17:02.860 align:start position:0% we are building and then you need assets right<00:17:00.980> this<00:17:01.699> is<00:17:01.850> what's<00:17:02.059> also<00:17:02.269> listed<00:17:02.689> in<00:17:02.750> the 00:17:02.860 --> 00:17:02.870 align:start position:0% right this is what's also listed in the 00:17:02.870 --> 00:17:06.189 align:start position:0% right this is what's also listed in the TWiT<00:17:03.050> but<00:17:03.290> we've<00:17:03.920> been<00:17:04.130> saying<00:17:04.850> like<00:17:05.199> tokens 00:17:06.189 --> 00:17:06.199 align:start position:0% TWiT but we've been saying like tokens 00:17:06.199 --> 00:17:08.439 align:start position:0% TWiT but we've been saying like tokens of<00:17:06.319> all<00:17:06.740> kinds<00:17:07.370> that<00:17:07.400> you<00:17:07.549> know<00:17:07.760> are<00:17:07.909> interest 00:17:08.439 --> 00:17:08.449 align:start position:0% of all kinds that you know are interest 00:17:08.449 --> 00:17:10.860 align:start position:0% of all kinds that you know are interest bearing<00:17:08.870> or<00:17:09.350> that<00:17:09.559> I<00:17:09.589> have<00:17:09.740> other<00:17:09.919> properties 00:17:10.860 --> 00:17:10.870 align:start position:0% bearing or that I have other properties 00:17:10.870 --> 00:17:14.679 align:start position:0% bearing or that I have other properties think<00:17:11.870> of<00:17:12.049> like<00:17:12.650> Rob<00:17:13.250> the<00:17:13.520> bitcoin<00:17:14.030> is<00:17:14.240> one<00:17:14.569> of 00:17:14.679 --> 00:17:14.689 align:start position:0% think of like Rob the bitcoin is one of 00:17:14.689 --> 00:17:16.270 align:start position:0% think of like Rob the bitcoin is one of example<00:17:15.169> of<00:17:15.260> that<00:17:15.409> where<00:17:15.919> you<00:17:16.100> have<00:17:16.250> a 00:17:16.270 --> 00:17:16.280 align:start position:0% example of that where you have a 00:17:16.280 --> 00:17:19.689 align:start position:0% example of that where you have a federation<00:17:16.750> securing<00:17:17.799> basically<00:17:18.799> any<00:17:19.010> RC<00:17:19.280> 20 00:17:19.689 --> 00:17:19.699 align:start position:0% federation securing basically any RC 20 00:17:19.699 --> 00:17:22.199 align:start position:0% federation securing basically any RC 20 token<00:17:20.120> on<00:17:20.299> a<00:17:20.360> theorem<00:17:20.949> which<00:17:21.949> is 00:17:22.199 --> 00:17:22.209 align:start position:0% token on a theorem which is 00:17:22.209 --> 00:17:28.029 align:start position:0% token on a theorem which is collateralized<00:17:23.209> by<00:17:23.390> Bitcoin<00:17:24.549> and<00:17:26.199> yeah 00:17:28.029 --> 00:17:28.039 align:start position:0% collateralized by Bitcoin and yeah 00:17:28.039 --> 00:17:31.180 align:start position:0% collateralized by Bitcoin and yeah the<00:17:28.820> point<00:17:29.030> is<00:17:29.330> do<00:17:30.260> we<00:17:30.380> really<00:17:30.650> believe<00:17:30.799> that 00:17:31.180 --> 00:17:31.190 align:start position:0% the point is do we really believe that 00:17:31.190 --> 00:17:35.110 align:start position:0% the point is do we really believe that like<00:17:31.760> all<00:17:32.000> those<00:17:32.210> defy<00:17:32.929> tools<00:17:33.380> we'll<00:17:34.250> never 00:17:35.110 --> 00:17:35.120 align:start position:0% like all those defy tools we'll never 00:17:35.120 --> 00:17:37.270 align:start position:0% like all those defy tools we'll never have<00:17:35.450> any<00:17:35.750> need<00:17:36.020> outside<00:17:36.230> of<00:17:36.559> a<00:17:36.650> theorem<00:17:36.919> well 00:17:37.270 --> 00:17:37.280 align:start position:0% have any need outside of a theorem well 00:17:37.280 --> 00:17:39.250 align:start position:0% have any need outside of a theorem well I<00:17:37.309> guess<00:17:37.850> the<00:17:37.970> answer<00:17:38.210> is<00:17:38.240> already<00:17:38.780> there<00:17:39.020> with 00:17:39.250 --> 00:17:39.260 align:start position:0% I guess the answer is already there with 00:17:39.260 --> 00:17:41.560 align:start position:0% I guess the answer is already there with W<00:17:39.559> BTC<00:17:39.919> right<00:17:40.100> we<00:17:40.520> see<00:17:40.669> there<00:17:40.820> is<00:17:40.880> a<00:17:40.940> first<00:17:41.330> need 00:17:41.560 --> 00:17:41.570 align:start position:0% W BTC right we see there is a first need 00:17:41.570 --> 00:17:46.450 align:start position:0% W BTC right we see there is a first need for<00:17:42.200> like<00:17:44.140> going<00:17:45.140> beyond<00:17:45.559> the<00:17:45.860> limits<00:17:46.220> of<00:17:46.340> the 00:17:46.450 --> 00:17:46.460 align:start position:0% for like going beyond the limits of the 00:17:46.460 --> 00:17:48.820 align:start position:0% for like going beyond the limits of the platform<00:17:47.240> where<00:17:47.539> the<00:17:47.720> defy<00:17:48.140> those<00:17:48.650> are 00:17:48.820 --> 00:17:48.830 align:start position:0% platform where the defy those are 00:17:48.830 --> 00:17:52.120 align:start position:0% platform where the defy those are operating<00:17:49.309> which<00:17:49.669> is<00:17:49.820> a<00:17:49.850> theorem<00:17:50.500> so<00:17:51.500> we<00:17:51.950> have 00:17:52.120 --> 00:17:52.130 align:start position:0% operating which is a theorem so we have 00:17:52.130 --> 00:17:54.330 align:start position:0% operating which is a theorem so we have if<00:17:52.700> you<00:17:52.789> look<00:17:52.880> on<00:17:53.030> current<00:17:53.450> market<00:17:53.480> cap 00:17:54.330 --> 00:17:54.340 align:start position:0% if you look on current market cap 00:17:54.340 --> 00:17:57.390 align:start position:0% if you look on current market cap the<00:17:54.610> like<00:17:55.390> tools<00:17:55.750> being<00:17:56.200> the<00:17:56.740> the<00:17:57.070> assets 00:17:57.390 --> 00:17:57.400 align:start position:0% the like tools being the the assets 00:17:57.400 --> 00:17:59.030 align:start position:0% the like tools being the the assets being<00:17:57.580> traded<00:17:57.880> that<00:17:58.240> I<00:17:58.300> have<00:17:58.450> most<00:17:58.630> of<00:17:58.840> the 00:17:59.030 --> 00:17:59.040 align:start position:0% being traded that I have most of the 00:17:59.040 --> 00:18:01.890 align:start position:0% being traded that I have most of the volumes<00:18:00.040> and<00:18:00.250> also<00:18:00.520> the<00:18:00.610> liquidity<00:18:00.880> are<00:18:01.540> not 00:18:01.890 --> 00:18:01.900 align:start position:0% volumes and also the liquidity are not 00:18:01.900 --> 00:18:03.600 align:start position:0% volumes and also the liquidity are not just<00:18:02.140> a<00:18:02.230> Tyrian<00:18:02.470> based<00:18:02.680> so<00:18:02.980> some<00:18:03.220> of<00:18:03.250> them<00:18:03.490> are 00:18:03.600 --> 00:18:03.610 align:start position:0% just a Tyrian based so some of them are 00:18:03.610 --> 00:18:05.040 align:start position:0% just a Tyrian based so some of them are 18<00:18:03.760> on<00:18:03.940> base<00:18:04.090> but<00:18:04.270> you<00:18:04.330> have<00:18:04.480> many<00:18:04.660> others<00:18:04.960> that 00:18:05.040 --> 00:18:05.050 align:start position:0% 18 on base but you have many others that 00:18:05.050 --> 00:18:07.020 align:start position:0% 18 on base but you have many others that are<00:18:05.110> not<00:18:05.350> adhere<00:18:05.590> on<00:18:05.680> base<00:18:05.830> not<00:18:06.610> to<00:18:06.730> talk<00:18:06.880> about 00:18:07.020 --> 00:18:07.030 align:start position:0% are not adhere on base not to talk about 00:18:07.030 --> 00:18:10.170 align:start position:0% are not adhere on base not to talk about the<00:18:07.360> you<00:18:07.540> know<00:18:07.660> non-blocking<00:18:08.380> assets<00:18:09.180> so 00:18:10.170 --> 00:18:10.180 align:start position:0% the you know non-blocking assets so 00:18:10.180 --> 00:18:11.790 align:start position:0% the you know non-blocking assets so there<00:18:10.570> is<00:18:10.630> a<00:18:10.660> strong<00:18:10.900> need<00:18:11.080> to<00:18:11.230> go<00:18:11.410> beyond<00:18:11.740> that 00:18:11.790 --> 00:18:11.800 align:start position:0% there is a strong need to go beyond that 00:18:11.800 --> 00:18:14.400 align:start position:0% there is a strong need to go beyond that so<00:18:12.130> that's<00:18:12.370> why<00:18:12.520> we<00:18:12.730> started<00:18:13.270> to<00:18:13.420> work<00:18:13.600> on<00:18:13.840> this 00:18:14.400 --> 00:18:14.410 align:start position:0% so that's why we started to work on this 00:18:14.410 --> 00:18:17.670 align:start position:0% so that's why we started to work on this new<00:18:14.740> project<00:18:15.100> called<00:18:15.490> the<00:18:15.850> P<00:18:16.450> tokens<00:18:16.810> this<00:18:17.530> is 00:18:17.670 --> 00:18:17.680 align:start position:0% new project called the P tokens this is 00:18:17.680 --> 00:18:20.580 align:start position:0% new project called the P tokens this is based<00:18:17.920> on<00:18:18.130> the<00:18:18.910> provable<00:18:19.450> infrastructure<00:18:20.440> and 00:18:20.580 --> 00:18:20.590 align:start position:0% based on the provable infrastructure and 00:18:20.590 --> 00:18:23.280 align:start position:0% based on the provable infrastructure and provable<00:18:20.950> technology<00:18:21.430> P<00:18:22.180> stands<00:18:22.570> for<00:18:22.690> a<00:18:22.870> few 00:18:23.280 --> 00:18:23.290 align:start position:0% provable technology P stands for a few 00:18:23.290 --> 00:18:25.740 align:start position:0% provable technology P stands for a few things<00:18:23.500> instance<00:18:24.250> for<00:18:24.490> provable<00:18:25.090> but<00:18:25.600> it's 00:18:25.740 --> 00:18:25.750 align:start position:0% things instance for provable but it's 00:18:25.750 --> 00:18:28.950 align:start position:0% things instance for provable but it's also<00:18:26.020> stands<00:18:26.410> for<00:18:26.580> portable<00:18:27.580> tokens<00:18:28.090> and<00:18:28.270> also 00:18:28.950 --> 00:18:28.960 align:start position:0% also stands for portable tokens and also 00:18:28.960 --> 00:18:31.440 align:start position:0% also stands for portable tokens and also for<00:18:29.290> pegged<00:18:29.620> tokens<00:18:30.190> because<00:18:30.940> what<00:18:31.150> they<00:18:31.300> are 00:18:31.440 --> 00:18:31.450 align:start position:0% for pegged tokens because what they are 00:18:31.450 --> 00:18:33.690 align:start position:0% for pegged tokens because what they are is<00:18:31.720> really<00:18:31.750> just<00:18:32.290> a<00:18:32.410> two-way<00:18:32.740> back<00:18:33.010> with 00:18:33.690 --> 00:18:33.700 align:start position:0% is really just a two-way back with 00:18:33.700 --> 00:18:36.450 align:start position:0% is really just a two-way back with tokens<00:18:34.510> from<00:18:34.660> that<00:18:35.290> live<00:18:35.650> natively<00:18:36.220> on<00:18:36.370> a 00:18:36.450 --> 00:18:36.460 align:start position:0% tokens from that live natively on a 00:18:36.460 --> 00:18:38.820 align:start position:0% tokens from that live natively on a different<00:18:36.880> block<00:18:37.330> containing<00:18:37.720> helium<00:18:37.870> but 00:18:38.820 --> 00:18:38.830 align:start position:0% different block containing helium but 00:18:38.830 --> 00:18:40.740 align:start position:0% different block containing helium but the<00:18:39.190> P<00:18:39.340> tokens<00:18:39.670> are<00:18:39.790> their<00:18:40.000> representation<00:18:40.660> on 00:18:40.740 --> 00:18:40.750 align:start position:0% the P tokens are their representation on 00:18:40.750 --> 00:18:42.780 align:start position:0% the P tokens are their representation on it<00:18:40.900> of<00:18:41.080> a<00:18:41.230> material<00:18:41.590> so<00:18:42.130> it's<00:18:42.250> basically<00:18:42.550> the 00:18:42.780 --> 00:18:42.790 align:start position:0% it of a material so it's basically the 00:18:42.790 --> 00:18:45.210 align:start position:0% it of a material so it's basically the same<00:18:43.120> thing<00:18:43.330> you<00:18:44.170> may<00:18:44.350> have<00:18:44.530> already<00:18:44.890> tested 00:18:45.210 --> 00:18:45.220 align:start position:0% same thing you may have already tested 00:18:45.220 --> 00:18:48.540 align:start position:0% same thing you may have already tested out<00:18:45.550> with<00:18:45.910> W<00:18:46.150> BTC<00:18:46.740> but<00:18:47.740> it<00:18:47.860> goes<00:18:48.070> beyond<00:18:48.430> that 00:18:48.540 --> 00:18:48.550 align:start position:0% out with W BTC but it goes beyond that 00:18:48.550 --> 00:18:51.330 align:start position:0% out with W BTC but it goes beyond that because<00:18:48.790> it<00:18:49.720> could<00:18:49.930> either<00:18:50.200> be<00:18:50.320> like<00:18:51.070> in 00:18:51.330 --> 00:18:51.340 align:start position:0% because it could either be like in 00:18:51.340 --> 00:18:53.220 align:start position:0% because it could either be like in support<00:18:51.850> of<00:18:52.060> a<00:18:52.240> federation<00:18:52.570> so<00:18:52.930> it<00:18:53.020> could<00:18:53.200> be 00:18:53.220 --> 00:18:53.230 align:start position:0% support of a federation so it could be 00:18:53.230 --> 00:18:56.460 align:start position:0% support of a federation so it could be something<00:18:53.530> used<00:18:53.950> on<00:18:54.130> top<00:18:54.580> of<00:18:54.700> W<00:18:55.030> BTC<00:18:55.390> or<00:18:55.570> it's 00:18:56.460 --> 00:18:56.470 align:start position:0% something used on top of W BTC or it's 00:18:56.470 --> 00:18:57.840 align:start position:0% something used on top of W BTC or it's something<00:18:56.680> you<00:18:56.890> can<00:18:57.040> use<00:18:57.070> to<00:18:57.370> potentially 00:18:57.840 --> 00:18:57.850 align:start position:0% something you can use to potentially 00:18:57.850 --> 00:19:00.690 align:start position:0% something you can use to potentially like<00:18:58.630> replicate<00:18:59.440> WBT<00:19:00.040> see<00:19:00.190> without<00:19:00.430> the 00:19:00.690 --> 00:19:00.700 align:start position:0% like replicate WBT see without the 00:19:00.700 --> 00:19:04.140 align:start position:0% like replicate WBT see without the Federation<00:19:01.180> or<00:19:01.590> start<00:19:02.590> other<00:19:02.890> tokens<00:19:03.400> without 00:19:04.140 --> 00:19:04.150 align:start position:0% Federation or start other tokens without 00:19:04.150 --> 00:19:06.330 align:start position:0% Federation or start other tokens without bootstrapping<00:19:04.870> a<00:19:05.050> new<00:19:05.170> Federation<00:19:05.500> again<00:19:06.220> and 00:19:06.330 --> 00:19:06.340 align:start position:0% bootstrapping a new Federation again and 00:19:06.340 --> 00:19:10.620 align:start position:0% bootstrapping a new Federation again and again<00:19:06.690> so<00:19:07.690> I<00:19:08.820> believe<00:19:09.820> this<00:19:09.940> is<00:19:10.000> like<00:19:10.270> quite 00:19:10.620 --> 00:19:10.630 align:start position:0% again so I believe this is like quite 00:19:10.630 --> 00:19:12.210 align:start position:0% again so I believe this is like quite significant<00:19:11.260> for<00:19:11.500> the<00:19:11.590> impact<00:19:11.890> it<00:19:12.010> could<00:19:12.160> have 00:19:12.210 --> 00:19:12.220 align:start position:0% significant for the impact it could have 00:19:12.220 --> 00:19:15.450 align:start position:0% significant for the impact it could have on<00:19:12.490> defi<00:19:13.410> so<00:19:14.410> I<00:19:14.440> want<00:19:14.740> to<00:19:14.800> explain<00:19:15.010> you<00:19:15.250> how<00:19:15.340> it 00:19:15.450 --> 00:19:15.460 align:start position:0% on defi so I want to explain you how it 00:19:15.460 --> 00:19:15.810 align:start position:0% on defi so I want to explain you how it works 00:19:15.810 --> 00:19:15.820 align:start position:0% works 00:19:15.820 --> 00:19:18.240 align:start position:0% works the<00:19:16.390> the<00:19:16.900> test<00:19:17.110> assumption<00:19:17.560> is<00:19:17.710> the<00:19:17.920> same<00:19:18.100> one 00:19:18.240 --> 00:19:18.250 align:start position:0% the the test assumption is the same one 00:19:18.250 --> 00:19:20.850 align:start position:0% the the test assumption is the same one we<00:19:18.280> had<00:19:18.490> built<00:19:18.700> the<00:19:19.110> provable<00:19:20.110> Oracle<00:19:20.560> service 00:19:20.850 --> 00:19:20.860 align:start position:0% we had built the provable Oracle service 00:19:20.860 --> 00:19:23.250 align:start position:0% we had built the provable Oracle service on<00:19:21.010> so<00:19:21.460> its<00:19:21.640> uses<00:19:21.970> trusted<00:19:22.330> computing<00:19:22.600> to 00:19:23.250 --> 00:19:23.260 align:start position:0% on so its uses trusted computing to 00:19:23.260 --> 00:19:26.850 align:start position:0% on so its uses trusted computing to secure<00:19:23.680> the<00:19:23.980> packing<00:19:24.940> and<00:19:25.500> it<00:19:26.500> can<00:19:26.740> be 00:19:26.850 --> 00:19:26.860 align:start position:0% secure the packing and it can be 00:19:26.860 --> 00:19:28.890 align:start position:0% secure the packing and it can be integrated<00:19:27.010> with<00:19:27.490> like<00:19:27.910> any<00:19:28.270> blockchain 00:19:28.890 --> 00:19:28.900 align:start position:0% integrated with like any blockchain 00:19:28.900 --> 00:19:30.600 align:start position:0% integrated with like any blockchain really<00:19:29.170> for<00:19:29.530> the<00:19:29.620> way<00:19:29.740> it<00:19:29.800> works<00:19:30.010> so<00:19:30.340> it's<00:19:30.490> very 00:19:30.600 --> 00:19:30.610 align:start position:0% really for the way it works so it's very 00:19:30.610 --> 00:19:33.750 align:start position:0% really for the way it works so it's very general<00:19:31.030> purpose<00:19:32.040> so<00:19:33.040> let<00:19:33.190> me<00:19:33.370> show<00:19:33.700> you 00:19:33.750 --> 00:19:33.760 align:start position:0% general purpose so let me show you 00:19:33.760 --> 00:19:36.740 align:start position:0% general purpose so let me show you what's<00:19:34.240> the<00:19:34.560> what's<00:19:35.560> the<00:19:35.590> flaw<00:19:35.830> so<00:19:36.040> this<00:19:36.490> is 00:19:36.740 --> 00:19:36.750 align:start position:0% what's the what's the flaw so this is 00:19:36.750 --> 00:19:40.260 align:start position:0% what's the what's the flaw so this is like<00:19:37.750> a<00:19:37.780> general<00:19:38.290> representation<00:19:38.770> of<00:19:39.250> DT<00:19:40.150> on 00:19:40.260 --> 00:19:40.270 align:start position:0% like a general representation of DT on 00:19:40.270 --> 00:19:42.510 align:start position:0% like a general representation of DT on blockchain<00:19:40.510> on<00:19:40.810> the<00:19:40.930> right<00:19:41.080> and<00:19:41.380> on<00:19:42.130> the<00:19:42.190> left 00:19:42.510 --> 00:19:42.520 align:start position:0% blockchain on the right and on the left 00:19:42.520 --> 00:19:44.160 align:start position:0% blockchain on the right and on the left you<00:19:42.790> have<00:19:42.850> a<00:19:42.940> blush<00:19:43.210> in<00:19:43.360> which<00:19:43.510> is<00:19:43.660> known<00:19:43.930> at 00:19:44.160 --> 00:19:44.170 align:start position:0% you have a blush in which is known at 00:19:44.170 --> 00:19:48.930 align:start position:0% you have a blush in which is known at Eden<00:19:44.470> based<00:19:44.680> so<00:19:45.490> it's<00:19:45.910> like<00:19:47.490> the<00:19:48.490> the<00:19:48.700> first 00:19:48.930 --> 00:19:48.940 align:start position:0% Eden based so it's like the the first 00:19:48.940 --> 00:19:52.320 align:start position:0% Eden based so it's like the the first one<00:19:49.120> we<00:19:49.270> release<00:19:49.960> is<00:19:50.140> years<00:19:51.010> as<00:19:51.280> it<00:19:51.910> didn't 00:19:52.320 --> 00:19:52.330 align:start position:0% one we release is years as it didn't 00:19:52.330 --> 00:19:54.300 align:start position:0% one we release is years as it didn't exist<00:19:52.630> on<00:19:52.900> a<00:19:52.960> theorem<00:19:53.350> so<00:19:53.740> it<00:19:53.830> will<00:19:53.980> be<00:19:54.100> like<00:19:54.250> a 00:19:54.300 --> 00:19:54.310 align:start position:0% exist on a theorem so it will be like a 00:19:54.310 --> 00:19:58.620 align:start position:0% exist on a theorem so it will be like a PE<00:19:54.700> Oz<00:19:55.060> token<00:19:55.540> on<00:19:55.720> a<00:19:55.780> theorem<00:19:57.240> but<00:19:58.240> it<00:19:58.450> is 00:19:58.620 --> 00:19:58.630 align:start position:0% PE Oz token on a theorem but it is 00:19:58.630 --> 00:20:00.480 align:start position:0% PE Oz token on a theorem but it is disciplinary<00:19:59.260> 20<00:19:59.650> blushing<00:19:59.980> so<00:20:00.190> it<00:20:00.280> could<00:20:00.460> be 00:20:00.480 --> 00:20:00.490 align:start position:0% disciplinary 20 blushing so it could be 00:20:00.490 --> 00:20:02.640 align:start position:0% disciplinary 20 blushing so it could be a<00:20:00.610> Bitcoin<00:20:01.030> it<00:20:01.240> could<00:20:01.450> be<00:20:01.570> you<00:20:01.810> know<00:20:01.840> rape<00:20:02.440> or 00:20:02.640 --> 00:20:02.650 align:start position:0% a Bitcoin it could be you know rape or 00:20:02.650 --> 00:20:05.070 align:start position:0% a Bitcoin it could be you know rape or or<00:20:02.770> whatever<00:20:03.120> whatever<00:20:04.120> there<00:20:04.240> is<00:20:04.270> our<00:20:04.510> need 00:20:05.070 --> 00:20:05.080 align:start position:0% or whatever whatever there is our need 00:20:05.080 --> 00:20:07.680 align:start position:0% or whatever whatever there is our need for<00:20:05.110> in<00:20:06.010> the<00:20:06.190> defi<00:20:06.520> ecosystem<00:20:07.090> on 00:20:07.680 --> 00:20:07.690 align:start position:0% for in the defi ecosystem on 00:20:07.690 --> 00:20:09.750 align:start position:0% for in the defi ecosystem on on<00:20:07.960> a<00:20:08.170> theorem<00:20:08.530> so<00:20:09.070> you<00:20:09.130> have<00:20:09.280> the<00:20:09.400> trusted 00:20:09.750 --> 00:20:09.760 align:start position:0% on a theorem so you have the trusted 00:20:09.760 --> 00:20:11.280 align:start position:0% on a theorem so you have the trusted execution<00:20:10.210> environment<00:20:10.690> in<00:20:10.870> the<00:20:10.990> middle 00:20:11.280 --> 00:20:11.290 align:start position:0% execution environment in the middle 00:20:11.290 --> 00:20:13.320 align:start position:0% execution environment in the middle which<00:20:11.590> is<00:20:11.620> the<00:20:11.770> secure<00:20:12.250> sign<00:20:12.490> books<00:20:12.670> executed 00:20:13.320 --> 00:20:13.330 align:start position:0% which is the secure sign books executed 00:20:13.330 --> 00:20:17.550 align:start position:0% which is the secure sign books executed on<00:20:13.510> Intel<00:20:13.810> SGX<00:20:13.960> in<00:20:14.440> this<00:20:14.980> case<00:20:15.510> and<00:20:16.560> basically 00:20:17.550 --> 00:20:17.560 align:start position:0% on Intel SGX in this case and basically 00:20:17.560 --> 00:20:23.070 align:start position:0% on Intel SGX in this case and basically what<00:20:18.310> the<00:20:19.230> what<00:20:20.230> the<00:20:21.270> what<00:20:22.270> happens<00:20:22.660> is<00:20:22.840> that 00:20:23.070 --> 00:20:23.080 align:start position:0% what the what the what happens is that 00:20:23.080 --> 00:20:25.500 align:start position:0% what the what the what happens is that the<00:20:23.350> the<00:20:23.380> securing<00:20:24.070> clave<00:20:24.250> at<00:20:24.640> the<00:20:25.150> moment<00:20:25.420> is 00:20:25.500 --> 00:20:25.510 align:start position:0% the the securing clave at the moment is 00:20:25.510 --> 00:20:27.690 align:start position:0% the the securing clave at the moment is running<00:20:25.810> within<00:20:25.990> like<00:20:26.650> those<00:20:26.860> boxes<00:20:27.280> that<00:20:27.520> we 00:20:27.690 --> 00:20:27.700 align:start position:0% running within like those boxes that we 00:20:27.700 --> 00:20:29.520 align:start position:0% running within like those boxes that we had<00:20:27.790> as<00:20:27.910> part<00:20:28.120> of<00:20:28.210> our<00:20:28.330> infrastructure<00:20:28.840> but<00:20:29.110> it 00:20:29.520 --> 00:20:29.530 align:start position:0% had as part of our infrastructure but it 00:20:29.530 --> 00:20:31.200 align:start position:0% had as part of our infrastructure but it could<00:20:29.710> be<00:20:29.830> run<00:20:29.950> anywhere<00:20:30.310> so<00:20:30.580> you<00:20:30.610> can<00:20:30.760> run<00:20:31.090> it 00:20:31.200 --> 00:20:31.210 align:start position:0% could be run anywhere so you can run it 00:20:31.210 --> 00:20:33.300 align:start position:0% could be run anywhere so you can run it on<00:20:31.420> your<00:20:31.450> own<00:20:31.810> like<00:20:32.080> Intel<00:20:32.440> SGX<00:20:32.560> machine<00:20:33.100> it 00:20:33.300 --> 00:20:33.310 align:start position:0% on your own like Intel SGX machine it 00:20:33.310 --> 00:20:34.980 align:start position:0% on your own like Intel SGX machine it could<00:20:33.760> be<00:20:33.880> run<00:20:34.000> in<00:20:34.120> the<00:20:34.240> cloud<00:20:34.480> with<00:20:34.810> some 00:20:34.980 --> 00:20:34.990 align:start position:0% could be run in the cloud with some 00:20:34.990 --> 00:20:38.850 align:start position:0% could be run in the cloud with some Intel<00:20:35.260> SGX<00:20:36.390> enable<00:20:37.390> the<00:20:37.540> machines<00:20:37.960> or<00:20:38.170> you<00:20:38.710> can 00:20:38.850 --> 00:20:38.860 align:start position:0% Intel SGX enable the machines or you can 00:20:38.860 --> 00:20:40.830 align:start position:0% Intel SGX enable the machines or you can just<00:20:39.070> use<00:20:39.340> one<00:20:39.880> of<00:20:39.910> those<00:20:40.120> machines<00:20:40.540> as<00:20:40.660> well 00:20:40.830 --> 00:20:40.840 align:start position:0% just use one of those machines as well 00:20:40.840 --> 00:20:45.480 align:start position:0% just use one of those machines as well if<00:20:41.820> like<00:20:43.260> you<00:20:44.260> want<00:20:44.500> to<00:20:44.650> potentially<00:20:45.130> secure 00:20:45.480 --> 00:20:45.490 align:start position:0% if like you want to potentially secure 00:20:45.490 --> 00:20:48.030 align:start position:0% if like you want to potentially secure this<00:20:46.150> two-way<00:20:46.630> back<00:20:46.900> and<00:20:47.170> contribute<00:20:47.710> to<00:20:47.950> the 00:20:48.030 --> 00:20:48.040 align:start position:0% this two-way back and contribute to the 00:20:48.040 --> 00:20:52.080 align:start position:0% this two-way back and contribute to the redundancy<00:20:48.520> of<00:20:48.670> it<00:20:49.230> so<00:20:50.310> it<00:20:51.310> doesn't<00:20:51.550> it<00:20:51.940> need 00:20:52.080 --> 00:20:52.090 align:start position:0% redundancy of it so it doesn't it need 00:20:52.090 --> 00:20:54.240 align:start position:0% redundancy of it so it doesn't it need to<00:20:52.300> be<00:20:52.420> limited<00:20:52.600> to<00:20:52.870> Intel<00:20:53.200> SGX<00:20:53.320> the<00:20:53.830> concept 00:20:54.240 --> 00:20:54.250 align:start position:0% to be limited to Intel SGX the concept 00:20:54.250 --> 00:20:57.270 align:start position:0% to be limited to Intel SGX the concept goes<00:20:55.090> beyond<00:20:55.510> SGX<00:20:56.050> itself<00:20:56.470> but<00:20:56.800> the<00:20:57.040> first 00:20:57.270 --> 00:20:57.280 align:start position:0% goes beyond SGX itself but the first 00:20:57.280 --> 00:20:59.190 align:start position:0% goes beyond SGX itself but the first implementation<00:20:57.790> will<00:20:58.360> be<00:20:58.390> honest<00:20:58.750> reacts<00:20:58.990> as 00:20:59.190 --> 00:20:59.200 align:start position:0% implementation will be honest reacts as 00:20:59.200 --> 00:21:02.310 align:start position:0% implementation will be honest reacts as if<00:20:59.620> the<00:20:59.830> like<00:21:00.220> easier<00:21:00.840> the<00:21:01.840> easiest<00:21:02.050> to<00:21:02.200> get 00:21:02.310 --> 00:21:02.320 align:start position:0% if the like easier the easiest to get 00:21:02.320 --> 00:21:04.260 align:start position:0% if the like easier the easiest to get started<00:21:02.740> with<00:21:02.920> and<00:21:03.160> the<00:21:03.670> code<00:21:03.940> is<00:21:04.060> quite 00:21:04.260 --> 00:21:04.270 align:start position:0% started with and the code is quite 00:21:04.270 --> 00:21:06.180 align:start position:0% started with and the code is quite complex<00:21:04.690> at<00:21:04.930> the<00:21:05.020> moment 00:21:06.180 --> 00:21:06.190 align:start position:0% complex at the moment 00:21:06.190 --> 00:21:07.650 align:start position:0% complex at the moment the<00:21:06.490> code<00:21:06.670> is<00:21:06.760> open<00:21:06.880> source<00:21:07.030> so<00:21:07.390> basically 00:21:07.650 --> 00:21:07.660 align:start position:0% the code is open source so basically 00:21:07.660 --> 00:21:10.590 align:start position:0% the code is open source so basically anyone<00:21:08.170> will<00:21:08.650> be<00:21:08.830> able<00:21:08.860> to<00:21:09.280> to<00:21:10.180> verify<00:21:10.540> the 00:21:10.590 --> 00:21:10.600 align:start position:0% anyone will be able to to verify the 00:21:10.600 --> 00:21:12.480 align:start position:0% anyone will be able to to verify the code<00:21:10.840> and<00:21:11.110> know<00:21:11.410> that<00:21:11.620> the<00:21:11.830> true<00:21:11.980> way<00:21:12.130> peg<00:21:12.340> is 00:21:12.480 --> 00:21:12.490 align:start position:0% code and know that the true way peg is 00:21:12.490 --> 00:21:14.130 align:start position:0% code and know that the true way peg is actually<00:21:12.820> secure<00:21:13.180> and<00:21:13.390> it's<00:21:13.720> running<00:21:13.930> as 00:21:14.130 --> 00:21:14.140 align:start position:0% actually secure and it's running as 00:21:14.140 --> 00:21:16.400 align:start position:0% actually secure and it's running as intended<00:21:14.620> so<00:21:15.250> it<00:21:15.370> gives<00:21:15.580> full<00:21:15.790> transparency 00:21:16.400 --> 00:21:16.410 align:start position:0% intended so it gives full transparency 00:21:16.410 --> 00:21:19.470 align:start position:0% intended so it gives full transparency which<00:21:17.410> is<00:21:17.590> not<00:21:17.740> reputation<00:21:18.310> based<00:21:18.520> so<00:21:19.000> that's 00:21:19.470 --> 00:21:19.480 align:start position:0% which is not reputation based so that's 00:21:19.480 --> 00:21:21.150 align:start position:0% which is not reputation based so that's why<00:21:19.630> you<00:21:19.690> know<00:21:20.020> you<00:21:20.320> don't<00:21:20.560> necessarily<00:21:20.740> need 00:21:21.150 --> 00:21:21.160 align:start position:0% why you know you don't necessarily need 00:21:21.160 --> 00:21:23.040 align:start position:0% why you know you don't necessarily need a<00:21:21.220> Federation<00:21:21.760> you<00:21:22.210> can<00:21:22.390> potentially<00:21:22.750> use<00:21:22.900> it 00:21:23.040 --> 00:21:23.050 align:start position:0% a Federation you can potentially use it 00:21:23.050 --> 00:21:24.870 align:start position:0% a Federation you can potentially use it with<00:21:23.320> other<00:21:23.440> Federation<00:21:23.950> or<00:21:24.100> in<00:21:24.460> support<00:21:24.790> of 00:21:24.870 --> 00:21:24.880 align:start position:0% with other Federation or in support of 00:21:24.880 --> 00:21:26.820 align:start position:0% with other Federation or in support of Federation<00:21:25.480> to<00:21:25.810> minimize<00:21:26.170> the<00:21:26.320> trust<00:21:26.560> in<00:21:26.740> the 00:21:26.820 --> 00:21:26.830 align:start position:0% Federation to minimize the trust in the 00:21:26.830 --> 00:21:31.650 align:start position:0% Federation to minimize the trust in the players<00:21:27.160> involved<00:21:27.970> so<00:21:28.930> we<00:21:29.110> in<00:21:29.260> the<00:21:29.290> peos<00:21:30.660> use 00:21:31.650 --> 00:21:31.660 align:start position:0% players involved so we in the peos use 00:21:31.660 --> 00:21:33.990 align:start position:0% players involved so we in the peos use case<00:21:31.900> that's<00:21:32.620> what<00:21:32.800> happens<00:21:33.130> with<00:21:33.820> the 00:21:33.990 --> 00:21:34.000 align:start position:0% case that's what happens with the 00:21:34.000 --> 00:21:36.720 align:start position:0% case that's what happens with the issuance<00:21:34.660> of<00:21:34.750> new<00:21:34.900> POS<00:21:35.500> tokens<00:21:35.980> so<00:21:36.670> you 00:21:36.720 --> 00:21:36.730 align:start position:0% issuance of new POS tokens so you 00:21:36.730 --> 00:21:41.130 align:start position:0% issuance of new POS tokens so you basically<00:21:37.060> send<00:21:37.920> like<00:21:38.920> a<00:21:39.370> new<00:21:39.700> transaction<00:21:40.390> to 00:21:41.130 --> 00:21:41.140 align:start position:0% basically send like a new transaction to 00:21:41.140 --> 00:21:43.560 align:start position:0% basically send like a new transaction to a<00:21:41.170> specific<00:21:41.830> address<00:21:41.950> which<00:21:42.790> is<00:21:42.820> probably 00:21:43.560 --> 00:21:43.570 align:start position:0% a specific address which is probably 00:21:43.570 --> 00:21:46.500 align:start position:0% a specific address which is probably under<00:21:43.870> the<00:21:44.080> control<00:21:44.590> of<00:21:44.770> the<00:21:45.130> clave<00:21:46.000> of<00:21:46.240> the 00:21:46.500 --> 00:21:46.510 align:start position:0% under the control of the clave of the 00:21:46.510 --> 00:21:48.630 align:start position:0% under the control of the clave of the trusted<00:21:46.840> execution<00:21:46.990> environment<00:21:47.710> and<00:21:47.890> then 00:21:48.630 --> 00:21:48.640 align:start position:0% trusted execution environment and then 00:21:48.640 --> 00:21:49.890 align:start position:0% trusted execution environment and then you<00:21:48.790> send<00:21:49.090> to<00:21:49.270> the<00:21:49.390> trusted<00:21:49.690> execution 00:21:49.890 --> 00:21:49.900 align:start position:0% you send to the trusted execution 00:21:49.900 --> 00:21:52.230 align:start position:0% you send to the trusted execution environment<00:21:50.650> approve<00:21:51.040> of<00:21:51.250> that<00:21:51.430> like<00:21:51.880> a<00:21:51.910> proof 00:21:52.230 --> 00:21:52.240 align:start position:0% environment approve of that like a proof 00:21:52.240 --> 00:21:54.690 align:start position:0% environment approve of that like a proof of<00:21:52.330> the<00:21:52.480> deposit<00:21:52.930> so<00:21:53.650> the<00:21:54.040> in<00:21:54.130> clave<00:21:54.340> will<00:21:54.580> be 00:21:54.690 --> 00:21:54.700 align:start position:0% of the deposit so the in clave will be 00:21:54.700 --> 00:21:56.760 align:start position:0% of the deposit so the in clave will be able<00:21:54.820> to<00:21:55.060> verify<00:21:55.240> that<00:21:55.480> this<00:21:55.900> deposit<00:21:56.260> opened 00:21:56.760 --> 00:21:56.770 align:start position:0% able to verify that this deposit opened 00:21:56.770 --> 00:21:58.770 align:start position:0% able to verify that this deposit opened correctly<00:21:57.190> and<00:21:57.370> will<00:21:57.880> authorize<00:21:58.120> on<00:21:58.720> a 00:21:58.770 --> 00:21:58.780 align:start position:0% correctly and will authorize on a 00:21:58.780 --> 00:22:00.810 align:start position:0% correctly and will authorize on a theorem<00:21:59.140> a<00:21:59.290> transaction<00:21:59.920> where<00:22:00.520> that 00:22:00.810 --> 00:22:00.820 align:start position:0% theorem a transaction where that 00:22:00.820 --> 00:22:04.770 align:start position:0% theorem a transaction where that basically<00:22:01.210> issues<00:22:01.780> the<00:22:01.930> new<00:22:02.050> POS<00:22:02.380> tokens<00:22:03.780> so 00:22:04.770 --> 00:22:04.780 align:start position:0% basically issues the new POS tokens so 00:22:04.780 --> 00:22:06.930 align:start position:0% basically issues the new POS tokens so the<00:22:04.990> opposite<00:22:05.380> happens<00:22:05.830> when<00:22:06.160> you<00:22:06.370> want<00:22:06.700> to 00:22:06.930 --> 00:22:06.940 align:start position:0% the opposite happens when you want to 00:22:06.940 --> 00:22:10.530 align:start position:0% the opposite happens when you want to like<00:22:07.500> Banda<00:22:08.500> token<00:22:08.830> and<00:22:08.980> redeem<00:22:09.580> DPOs<00:22:10.180> token 00:22:10.530 --> 00:22:10.540 align:start position:0% like Banda token and redeem DPOs token 00:22:10.540 --> 00:22:14.160 align:start position:0% like Banda token and redeem DPOs token so<00:22:10.870> the<00:22:10.990> POS<00:22:11.290> token<00:22:11.590> can<00:22:11.770> like<00:22:12.310> freely<00:22:13.170> be 00:22:14.160 --> 00:22:14.170 align:start position:0% so the POS token can like freely be 00:22:14.170 --> 00:22:16.890 align:start position:0% so the POS token can like freely be exchanged<00:22:14.740> on<00:22:14.890> a<00:22:14.950> theorem<00:22:15.370> as<00:22:15.490> NESC<00:22:16.180> 20<00:22:16.600> token 00:22:16.890 --> 00:22:16.900 align:start position:0% exchanged on a theorem as NESC 20 token 00:22:16.900 --> 00:22:20.220 align:start position:0% exchanged on a theorem as NESC 20 token and<00:22:16.930> at<00:22:17.650> any<00:22:17.920> time<00:22:18.040> in<00:22:18.640> an<00:22:18.850> automated<00:22:19.300> way<00:22:19.510> with 00:22:20.220 --> 00:22:20.230 align:start position:0% and at any time in an automated way with 00:22:20.230 --> 00:22:21.450 align:start position:0% and at any time in an automated way with no<00:22:20.410> manual<00:22:20.650> intervention 00:22:21.450 --> 00:22:21.460 align:start position:0% no manual intervention 00:22:21.460 --> 00:22:23.220 align:start position:0% no manual intervention it<00:22:21.670> can<00:22:22.030> just<00:22:22.210> be<00:22:22.300> redeemed<00:22:22.780> for<00:22:23.080> the 00:22:23.220 --> 00:22:23.230 align:start position:0% it can just be redeemed for the 00:22:23.230 --> 00:22:25.410 align:start position:0% it can just be redeemed for the underlying<00:22:23.620> asset<00:22:24.040> which<00:22:24.580> in<00:22:24.790> this<00:22:24.880> case<00:22:25.120> is 00:22:25.410 --> 00:22:25.420 align:start position:0% underlying asset which in this case is 00:22:25.420 --> 00:22:27.510 align:start position:0% underlying asset which in this case is ears<00:22:25.690> so<00:22:26.470> what<00:22:26.650> you<00:22:26.770> will<00:22:26.980> do<00:22:27.190> is<00:22:27.370> basically 00:22:27.510 --> 00:22:27.520 align:start position:0% ears so what you will do is basically 00:22:27.520 --> 00:22:31.560 align:start position:0% ears so what you will do is basically barring<00:22:28.150> the<00:22:28.300> use<00:22:28.890> DPS<00:22:29.890> token<00:22:30.400> and<00:22:30.610> when<00:22:31.420> you 00:22:31.560 --> 00:22:31.570 align:start position:0% barring the use DPS token and when you 00:22:31.570 --> 00:22:34.530 align:start position:0% barring the use DPS token and when you burn<00:22:31.750> it<00:22:31.840> you<00:22:32.050> specify<00:22:32.560> the<00:22:33.210> ears<00:22:34.210> address 00:22:34.530 --> 00:22:34.540 align:start position:0% burn it you specify the ears address 00:22:34.540 --> 00:22:36.510 align:start position:0% burn it you specify the ears address that<00:22:34.840> where<00:22:35.140> you<00:22:35.290> want<00:22:35.470> to<00:22:35.560> redeem<00:22:35.830> the<00:22:36.070> de<00:22:36.250> oz 00:22:36.510 --> 00:22:36.520 align:start position:0% that where you want to redeem the de oz 00:22:36.520 --> 00:22:38.970 align:start position:0% that where you want to redeem the de oz torque<00:22:36.760> and<00:22:36.880> so<00:22:36.970> on<00:22:37.030> and<00:22:37.350> what<00:22:38.350> happens<00:22:38.860> is 00:22:38.970 --> 00:22:38.980 align:start position:0% torque and so on and what happens is 00:22:38.980 --> 00:22:40.350 align:start position:0% torque and so on and what happens is that<00:22:39.010> basically<00:22:39.460> after<00:22:39.730> the<00:22:39.910> trusted 00:22:40.350 --> 00:22:40.360 align:start position:0% that basically after the trusted 00:22:40.360 --> 00:22:42.080 align:start position:0% that basically after the trusted execution<00:22:40.570> environment<00:22:41.290> has<00:22:41.410> verified<00:22:41.680> that 00:22:42.080 --> 00:22:42.090 align:start position:0% execution environment has verified that 00:22:42.090 --> 00:22:45.960 align:start position:0% execution environment has verified that everything<00:22:43.090> is<00:22:43.500> correct<00:22:44.500> it<00:22:45.100> really<00:22:45.670> is<00:22:45.730> the 00:22:45.960 --> 00:22:45.970 align:start position:0% everything is correct it really is the 00:22:45.970 --> 00:22:48.480 align:start position:0% everything is correct it really is the ears<00:22:46.360> focus<00:22:46.990> accordingly<00:22:47.440> so<00:22:48.130> there<00:22:48.280> is<00:22:48.370> no 00:22:48.480 --> 00:22:48.490 align:start position:0% ears focus accordingly so there is no 00:22:48.490 --> 00:22:50.700 align:start position:0% ears focus accordingly so there is no possibility<00:22:48.850> to<00:22:49.060> steal<00:22:49.360> funds<00:22:49.600> is<00:22:49.900> fully 00:22:50.700 --> 00:22:50.710 align:start position:0% possibility to steal funds is fully 00:22:50.710 --> 00:22:52.110 align:start position:0% possibility to steal funds is fully transparent<00:22:51.010> and<00:22:51.370> secure<00:22:51.670> thanks<00:22:51.910> to<00:22:52.030> the 00:22:52.110 --> 00:22:52.120 align:start position:0% transparent and secure thanks to the 00:22:52.120 --> 00:22:56.210 align:start position:0% transparent and secure thanks to the trusted<00:22:52.390> computing<00:22:52.690> component<00:22:53.320> and<00:22:54.090> yeah<00:22:55.090> so 00:22:56.210 --> 00:22:56.220 align:start position:0% trusted computing component and yeah so 00:22:56.220 --> 00:23:00.390 align:start position:0% trusted computing component and yeah so we<00:22:57.220> have<00:22:57.340> a<00:22:57.370> demo<00:22:58.240> working<00:22:58.720> we<00:22:59.680> plan<00:23:00.130> to 00:23:00.390 --> 00:23:00.400 align:start position:0% we have a demo working we plan to 00:23:00.400 --> 00:23:03.390 align:start position:0% we have a demo working we plan to release<00:23:00.790> the<00:23:01.600> production<00:23:02.140> version<00:23:02.500> of<00:23:02.620> the<00:23:02.950> PS 00:23:03.390 --> 00:23:03.400 align:start position:0% release the production version of the PS 00:23:03.400 --> 00:23:05.790 align:start position:0% release the production version of the PS token<00:23:04.030> by<00:23:04.210> end<00:23:04.360> of<00:23:04.480> month<00:23:04.720> but<00:23:05.440> now<00:23:05.590> we<00:23:05.650> are 00:23:05.790 --> 00:23:05.800 align:start position:0% token by end of month but now we are 00:23:05.800 --> 00:23:07.470 align:start position:0% token by end of month but now we are looking<00:23:05.890> for<00:23:06.160> community<00:23:06.340> feedback<00:23:06.730> and<00:23:07.090> we 00:23:07.470 --> 00:23:07.480 align:start position:0% looking for community feedback and we 00:23:07.480 --> 00:23:10.380 align:start position:0% looking for community feedback and we are<00:23:07.600> discussing<00:23:07.930> with<00:23:08.260> defy<00:23:09.130> tools<00:23:09.550> to<00:23:10.120> see<00:23:10.300> if 00:23:10.380 --> 00:23:10.390 align:start position:0% are discussing with defy tools to see if 00:23:10.390 --> 00:23:11.940 align:start position:0% are discussing with defy tools to see if they<00:23:10.510> are<00:23:10.540> interested<00:23:10.780> and<00:23:11.230> what<00:23:11.440> tokens<00:23:11.830> they 00:23:11.940 --> 00:23:11.950 align:start position:0% they are interested and what tokens they 00:23:11.950 --> 00:23:15.090 align:start position:0% they are interested and what tokens they would<00:23:12.130> like<00:23:12.310> to<00:23:12.520> have<00:23:13.360> on<00:23:14.140> a<00:23:14.200> theorem<00:23:14.560> so<00:23:15.010> if 00:23:15.090 --> 00:23:15.100 align:start position:0% would like to have on a theorem so if 00:23:15.100 --> 00:23:16.470 align:start position:0% would like to have on a theorem so if you<00:23:15.190> are<00:23:15.250> interested<00:23:15.430> to<00:23:15.790> potentially<00:23:16.300> have 00:23:16.470 --> 00:23:16.480 align:start position:0% you are interested to potentially have 00:23:16.480 --> 00:23:19.560 align:start position:0% you are interested to potentially have like<00:23:17.080> on<00:23:17.380> etherium<00:23:17.890> a<00:23:18.370> token<00:23:19.060> which<00:23:19.210> is<00:23:19.360> not 00:23:19.560 --> 00:23:19.570 align:start position:0% like on etherium a token which is not 00:23:19.570 --> 00:23:22.230 align:start position:0% like on etherium a token which is not there<00:23:20.290> at<00:23:20.560> the<00:23:20.590> moment<00:23:20.680> please<00:23:21.610> reach<00:23:21.820> out<00:23:22.000> and 00:23:22.230 --> 00:23:22.240 align:start position:0% there at the moment please reach out and 00:23:22.240 --> 00:23:25.140 align:start position:0% there at the moment please reach out and we<00:23:22.840> will<00:23:22.960> be<00:23:23.140> happy<00:23:23.440> to<00:23:23.650> support<00:23:24.010> you<00:23:24.340> so<00:23:24.970> this 00:23:25.140 --> 00:23:25.150 align:start position:0% we will be happy to support you so this 00:23:25.150 --> 00:23:27.780 align:start position:0% we will be happy to support you so this is<00:23:25.270> the<00:23:25.420> dub<00:23:25.810> that<00:23:26.230> you<00:23:26.530> will<00:23:26.770> be<00:23:26.980> connecting 00:23:27.780 --> 00:23:27.790 align:start position:0% is the dub that you will be connecting 00:23:27.790 --> 00:23:30.180 align:start position:0% is the dub that you will be connecting to<00:23:27.820> it's<00:23:28.600> ready<00:23:28.930> actually<00:23:29.080> everything<00:23:30.070> is 00:23:30.180 --> 00:23:30.190 align:start position:0% to it's ready actually everything is 00:23:30.190 --> 00:23:32.370 align:start position:0% to it's ready actually everything is already<00:23:30.340> working<00:23:30.970> we<00:23:31.600> are<00:23:31.690> finalizing<00:23:32.050> the 00:23:32.370 --> 00:23:32.380 align:start position:0% already working we are finalizing the 00:23:32.380 --> 00:23:34.620 align:start position:0% already working we are finalizing the enclaved<00:23:32.710> component<00:23:33.190> at<00:23:33.310> the<00:23:33.400> moment<00:23:33.670> but<00:23:34.210> the 00:23:34.620 --> 00:23:34.630 align:start position:0% enclaved component at the moment but the 00:23:34.630 --> 00:23:35.850 align:start position:0% enclaved component at the moment but the blockchain<00:23:34.930> component<00:23:35.470> is<00:23:35.560> already 00:23:35.850 --> 00:23:35.860 align:start position:0% blockchain component is already 00:23:35.860 --> 00:23:39.260 align:start position:0% blockchain component is already finalized<00:23:36.460> so<00:23:37.000> what<00:23:37.180> you<00:23:37.330> have<00:23:37.600> ended<00:23:38.200> up<00:23:38.380> is 00:23:39.260 --> 00:23:39.270 align:start position:0% finalized so what you have ended up is 00:23:39.270 --> 00:23:43.770 align:start position:0% finalized so what you have ended up is well<00:23:40.270> just<00:23:40.840> a<00:23:40.960> transparent<00:23:42.330> Luke<00:23:43.330> house<00:23:43.510> - 00:23:43.770 --> 00:23:43.780 align:start position:0% well just a transparent Luke house - 00:23:43.780 --> 00:23:45.330 align:start position:0% well just a transparent Luke house - like<00:23:44.080> the<00:23:44.350> minting<00:23:44.680> events<00:23:45.010> and<00:23:45.100> binding 00:23:45.330 --> 00:23:45.340 align:start position:0% like the minting events and binding 00:23:45.340 --> 00:23:47.460 align:start position:0% like the minting events and binding events<00:23:45.640> so<00:23:46.030> you<00:23:46.090> can<00:23:46.300> check<00:23:46.510> that<00:23:46.540> you<00:23:46.930> know<00:23:47.050> DP 00:23:47.460 --> 00:23:47.470 align:start position:0% events so you can check that you know DP 00:23:47.470 --> 00:23:49.530 align:start position:0% events so you can check that you know DP of<00:23:47.500> tokens<00:23:47.950> and<00:23:48.130> the<00:23:48.280> underlying<00:23:48.850> euros 00:23:49.530 --> 00:23:49.540 align:start position:0% of tokens and the underlying euros 00:23:49.540 --> 00:23:54.510 align:start position:0% of tokens and the underlying euros tokens<00:23:50.190> do<00:23:51.190> match<00:23:52.290> and<00:23:53.290> then<00:23:53.800> you<00:23:53.980> would<00:23:54.160> see 00:23:54.510 --> 00:23:54.520 align:start position:0% tokens do match and then you would see 00:23:54.520 --> 00:23:56.280 align:start position:0% tokens do match and then you would see the<00:23:54.730> state<00:23:55.120> of<00:23:55.270> the<00:23:55.390> enclaves<00:23:55.660> so<00:23:55.930> this<00:23:56.080> is<00:23:56.200> the 00:23:56.280 --> 00:23:56.290 align:start position:0% the state of the enclaves so this is the 00:23:56.290 --> 00:23:58.200 align:start position:0% the state of the enclaves so this is the trusted<00:23:56.590> computing<00:23:56.620> you<00:23:57.460> will<00:23:57.640> see<00:23:57.820> the<00:23:58.000> last 00:23:58.200 --> 00:23:58.210 align:start position:0% trusted computing you will see the last 00:23:58.210 --> 00:24:00.630 align:start position:0% trusted computing you will see the last year's<00:23:58.840> and<00:23:59.050> the<00:23:59.230> last<00:23:59.380> item<00:23:59.590> block<00:24:00.010> that<00:24:00.520> is 00:24:00.630 --> 00:24:00.640 align:start position:0% year's and the last item block that is 00:24:00.640 --> 00:24:04.170 align:start position:0% year's and the last item block that is that<00:24:00.880> are<00:24:01.030> known<00:24:01.390> to<00:24:01.900> the<00:24:02.020> in<00:24:02.080> clave<00:24:02.760> and<00:24:03.760> there 00:24:04.170 --> 00:24:04.180 align:start position:0% that are known to the in clave and there 00:24:04.180 --> 00:24:06.090 align:start position:0% that are known to the in clave and there are<00:24:04.240> some<00:24:04.450> statistics<00:24:04.930> here<00:24:05.020> on<00:24:05.440> like<00:24:05.950> the 00:24:06.090 --> 00:24:06.100 align:start position:0% are some statistics here on like the 00:24:06.100 --> 00:24:08.100 align:start position:0% are some statistics here on like the operations<00:24:06.550> that<00:24:06.670> has<00:24:06.820> been<00:24:07.000> done<00:24:07.180> by<00:24:07.360> the<00:24:07.420> in 00:24:08.100 --> 00:24:08.110 align:start position:0% operations that has been done by the in 00:24:08.110 --> 00:24:11.490 align:start position:0% operations that has been done by the in Cleveland<00:24:08.710> that<00:24:09.280> are<00:24:09.610> reported<00:24:10.210> by<00:24:10.630> it<00:24:10.690> you 00:24:11.490 --> 00:24:11.500 align:start position:0% Cleveland that are reported by it you 00:24:11.500 --> 00:24:14.220 align:start position:0% Cleveland that are reported by it you can<00:24:11.680> also<00:24:11.890> like<00:24:12.370> issue<00:24:12.850> and<00:24:13.090> redeem<00:24:13.420> via<00:24:13.960> deed 00:24:14.220 --> 00:24:14.230 align:start position:0% can also like issue and redeem via deed 00:24:14.230 --> 00:24:16.680 align:start position:0% can also like issue and redeem via deed up<00:24:14.380> the<00:24:15.070> tokens<00:24:15.400> independently<00:24:16.120> at<00:24:16.240> any<00:24:16.420> time 00:24:16.680 --> 00:24:16.690 align:start position:0% up the tokens independently at any time 00:24:16.690 --> 00:24:19.020 align:start position:0% up the tokens independently at any time with<00:24:17.110> no<00:24:17.350> intervention<00:24:17.740> so<00:24:18.490> that's<00:24:18.820> much 00:24:19.020 --> 00:24:19.030 align:start position:0% with no intervention so that's much 00:24:19.030 --> 00:24:21.300 align:start position:0% with no intervention so that's much faster<00:24:19.060> than<00:24:19.630> any<00:24:19.900> alternative<00:24:20.440> solution 00:24:21.300 --> 00:24:21.310 align:start position:0% faster than any alternative solution 00:24:21.310 --> 00:24:25.500 align:start position:0% faster than any alternative solution like<00:24:21.520> WB<00:24:22.240> TC<00:24:22.540> or<00:24:22.840> in<00:24:23.530> general<00:24:24.210> since<00:24:25.210> there<00:24:25.420> is 00:24:25.500 --> 00:24:25.510 align:start position:0% like WB TC or in general since there is 00:24:25.510 --> 00:24:27.120 align:start position:0% like WB TC or in general since there is no<00:24:25.660> human<00:24:25.840> intervention<00:24:26.170> for<00:24:26.620> the<00:24:26.740> main<00:24:26.890> thing 00:24:27.120 --> 00:24:27.130 align:start position:0% no human intervention for the main thing 00:24:27.130 --> 00:24:29.580 align:start position:0% no human intervention for the main thing or<00:24:27.340> anything<00:24:27.820> like<00:24:28.030> that<00:24:28.090> it<00:24:28.510> can<00:24:28.960> be<00:24:29.110> really 00:24:29.580 --> 00:24:29.590 align:start position:0% or anything like that it can be really 00:24:29.590 --> 00:24:32.030 align:start position:0% or anything like that it can be really done<00:24:29.950> very<00:24:30.220> quickly<00:24:30.340> so<00:24:31.060> in<00:24:31.150> the<00:24:31.240> case<00:24:31.420> of<00:24:31.600> like 00:24:32.030 --> 00:24:32.040 align:start position:0% done very quickly so in the case of like 00:24:32.040 --> 00:24:34.140 align:start position:0% done very quickly so in the case of like Bitcoin<00:24:33.040> for<00:24:33.190> example<00:24:33.580> you<00:24:33.700> would<00:24:33.850> just<00:24:34.030> need 00:24:34.140 --> 00:24:34.150 align:start position:0% Bitcoin for example you would just need 00:24:34.150 --> 00:24:35.250 align:start position:0% Bitcoin for example you would just need to<00:24:34.210> wait<00:24:34.480> for<00:24:34.510> the<00:24:34.720> confirmation 00:24:35.250 --> 00:24:35.260 align:start position:0% to wait for the confirmation 00:24:35.260 --> 00:24:42.180 align:start position:0% to wait for the confirmation time<00:24:37.559> so<00:24:38.559> this<00:24:39.130> is<00:24:39.190> a<00:24:39.610> recap<00:24:40.120> so<00:24:40.360> basically<00:24:41.190> we 00:24:42.180 --> 00:24:42.190 align:start position:0% time so this is a recap so basically we 00:24:42.190 --> 00:24:44.430 align:start position:0% time so this is a recap so basically we have<00:24:42.460> worked<00:24:42.790> a<00:24:42.940> lot<00:24:43.090> recently<00:24:43.360> on<00:24:43.840> securing 00:24:44.430 --> 00:24:44.440 align:start position:0% have worked a lot recently on securing 00:24:44.440 --> 00:24:47.520 align:start position:0% have worked a lot recently on securing like<00:24:45.100> the<00:24:45.340> the<00:24:45.760> Oracle<00:24:46.059> service<00:24:46.390> which<00:24:47.350> is 00:24:47.520 --> 00:24:47.530 align:start position:0% like the the Oracle service which is 00:24:47.530 --> 00:24:51.000 align:start position:0% like the the Oracle service which is already<00:24:47.710> like<00:24:48.480> stable<00:24:49.480> and<00:24:49.690> use<00:24:49.870> the<00:24:50.140> a<00:24:50.380> lot<00:24:50.770> on 00:24:51.000 --> 00:24:51.010 align:start position:0% already like stable and use the a lot on 00:24:51.010 --> 00:24:53.010 align:start position:0% already like stable and use the a lot on DT<00:24:51.370> no<00:24:51.460> maintenance<00:24:51.669> we<00:24:52.480> have<00:24:52.600> also<00:24:52.809> released 00:24:53.010 --> 00:24:53.020 align:start position:0% DT no maintenance we have also released 00:24:53.020 --> 00:24:55.470 align:start position:0% DT no maintenance we have also released like<00:24:53.410> new<00:24:53.590> certifications<00:24:54.340> for<00:24:54.700> regulated 00:24:55.470 --> 00:24:55.480 align:start position:0% like new certifications for regulated 00:24:55.480 --> 00:24:58.950 align:start position:0% like new certifications for regulated casinos<00:24:55.900> around<00:24:56.110> the<00:24:56.380> provable<00:24:56.740> RNG<00:24:57.660> but<00:24:58.660> our 00:24:58.950 --> 00:24:58.960 align:start position:0% casinos around the provable RNG but our 00:24:58.960 --> 00:25:01.320 align:start position:0% casinos around the provable RNG but our recent<00:24:59.650> area<00:24:59.950> focus<00:25:00.340> has<00:25:00.490> become<00:25:00.880> the<00:25:01.059> P 00:25:01.320 --> 00:25:01.330 align:start position:0% recent area focus has become the P 00:25:01.330 --> 00:25:03.210 align:start position:0% recent area focus has become the P tokens<00:25:01.660> which<00:25:01.990> we<00:25:02.140> believe<00:25:02.440> will<00:25:02.650> use<00:25:03.070> the 00:25:03.210 --> 00:25:03.220 align:start position:0% tokens which we believe will use the 00:25:03.220 --> 00:25:05.130 align:start position:0% tokens which we believe will use the same<00:25:03.400> technology<00:25:03.730> while<00:25:04.179> providing<00:25:04.480> like<00:25:05.110> a 00:25:05.130 --> 00:25:05.140 align:start position:0% same technology while providing like a 00:25:05.140 --> 00:25:06.900 align:start position:0% same technology while providing like a service<00:25:05.620> which<00:25:05.980> is<00:25:06.130> strongly<00:25:06.429> needed<00:25:06.760> today 00:25:06.900 --> 00:25:06.910 align:start position:0% service which is strongly needed today 00:25:06.910 --> 00:25:09.419 align:start position:0% service which is strongly needed today in<00:25:07.270> DD<00:25:07.840> Phi<00:25:07.960> ecosystem<00:25:08.470> so<00:25:09.160> if<00:25:09.250> you<00:25:09.370> are 00:25:09.419 --> 00:25:09.429 align:start position:0% in DD Phi ecosystem so if you are 00:25:09.429 --> 00:25:13.289 align:start position:0% in DD Phi ecosystem so if you are interested<00:25:10.559> well<00:25:11.559> sorry<00:25:12.010> this<00:25:12.370> was<00:25:12.669> like<00:25:13.000> P 00:25:13.289 --> 00:25:13.299 align:start position:0% interested well sorry this was like P 00:25:13.299 --> 00:25:15.780 align:start position:0% interested well sorry this was like P tokens<00:25:13.690> dot<00:25:13.840> IO<00:25:14.020> is<00:25:14.380> a<00:25:14.440> website<00:25:14.919> where<00:25:15.520> you<00:25:15.640> can 00:25:15.780 --> 00:25:15.790 align:start position:0% tokens dot IO is a website where you can 00:25:15.790 --> 00:25:17.100 align:start position:0% tokens dot IO is a website where you can go<00:25:15.970> ahead<00:25:16.030> there<00:25:16.210> is<00:25:16.240> like<00:25:16.450> a<00:25:16.480> whitepaper 00:25:17.100 --> 00:25:17.110 align:start position:0% go ahead there is like a whitepaper 00:25:17.110 --> 00:25:18.990 align:start position:0% go ahead there is like a whitepaper there<00:25:17.590> is<00:25:17.679> the<00:25:17.919> draft<00:25:18.250> of<00:25:18.429> a<00:25:18.520> white<00:25:18.669> paper<00:25:18.880> that 00:25:18.990 --> 00:25:19.000 align:start position:0% there is the draft of a white paper that 00:25:19.000 --> 00:25:21.240 align:start position:0% there is the draft of a white paper that we<00:25:19.270> have<00:25:19.360> released<00:25:19.600> today<00:25:19.990> and<00:25:20.320> there<00:25:21.130> is<00:25:21.220> a 00:25:21.240 --> 00:25:21.250 align:start position:0% we have released today and there is a 00:25:21.250 --> 00:25:22.830 align:start position:0% we have released today and there is a telegram<00:25:21.669> channel<00:25:22.059> where<00:25:22.210> you<00:25:22.330> can<00:25:22.510> join<00:25:22.690> the 00:25:22.830 --> 00:25:22.840 align:start position:0% telegram channel where you can join the 00:25:22.840 --> 00:25:25.140 align:start position:0% telegram channel where you can join the discussion<00:25:22.870> if<00:25:23.500> you<00:25:24.040> are<00:25:24.160> interested<00:25:24.730> on<00:25:25.030> the 00:25:25.140 --> 00:25:25.150 align:start position:0% discussion if you are interested on the 00:25:25.150 --> 00:25:28.230 align:start position:0% discussion if you are interested on the topic<00:25:25.480> so<00:25:25.660> it's<00:25:25.840> betoken<00:25:26.320> so<00:25:26.470> ty<00:25:26.590> oh<00:25:27.120> thank<00:25:28.120> you 00:25:28.230 --> 00:25:28.240 align:start position:0% topic so it's betoken so ty oh thank you 00:25:28.240 --> 00:25:29.789 align:start position:0% topic so it's betoken so ty oh thank you for<00:25:28.780> your<00:25:29.410> attention 00:25:29.789 --> 00:25:29.799 align:start position:0% for your attention 00:25:29.799 --> 00:25:31.490 align:start position:0% for your attention Thanks 00:25:31.490 --> 00:25:31.500 align:start position:0% Thanks 00:25:31.500 --> 00:25:41.400 align:start position:0% Thanks [Applause] 00:25:41.400 --> 00:25:41.410 align:start position:0% 00:25:41.410 --> 00:25:43.470 align:start position:0% you