WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:16.640 align:start position:0% [Music] 00:00:16.640 --> 00:00:16.650 align:start position:0% [Music] 00:00:16.650 --> 00:00:19.679 align:start position:0% [Music] good<00:00:17.650> afternoon<00:00:17.919> everyone<00:00:18.279> my<00:00:18.939> name<00:00:19.419> is<00:00:19.509> Sam 00:00:19.679 --> 00:00:19.689 align:start position:0% good afternoon everyone my name is Sam 00:00:19.689 --> 00:00:22.169 align:start position:0% good afternoon everyone my name is Sam Chadwick<00:00:20.109> and<00:00:20.380> I<00:00:20.710> am<00:00:20.890> in<00:00:21.159> the<00:00:21.400> innovation<00:00:21.939> team 00:00:22.169 --> 00:00:22.179 align:start position:0% Chadwick and I am in the innovation team 00:00:22.179 --> 00:00:24.300 align:start position:0% Chadwick and I am in the innovation team at<00:00:22.419> Thomson<00:00:22.779> Reuters<00:00:22.900> and<00:00:23.349> I<00:00:23.800> am<00:00:23.859> accompanied 00:00:24.300 --> 00:00:24.310 align:start position:0% at Thomson Reuters and I am accompanied 00:00:24.310 --> 00:00:27.419 align:start position:0% at Thomson Reuters and I am accompanied by<00:00:24.339> Tim<00:00:24.819> Nugent<00:00:25.029> who<00:00:25.929> is<00:00:26.319> in<00:00:26.589> our<00:00:26.710> research<00:00:27.279> and 00:00:27.419 --> 00:00:27.429 align:start position:0% by Tim Nugent who is in our research and 00:00:27.429 --> 00:00:30.239 align:start position:0% by Tim Nugent who is in our research and development<00:00:27.489> team<00:00:28.679> and<00:00:29.679> we<00:00:29.859> thought<00:00:30.039> we'd 00:00:30.239 --> 00:00:30.249 align:start position:0% development team and we thought we'd 00:00:30.249 --> 00:00:31.950 align:start position:0% development team and we thought we'd spend<00:00:30.399> today<00:00:30.849> talking<00:00:31.149> about<00:00:31.359> some<00:00:31.569> of<00:00:31.899> the 00:00:31.950 --> 00:00:31.960 align:start position:0% spend today talking about some of the 00:00:31.960 --> 00:00:33.330 align:start position:0% spend today talking about some of the things<00:00:32.169> that<00:00:32.230> Thomson<00:00:32.559> Reuters<00:00:32.829> has<00:00:33.160> been 00:00:33.330 --> 00:00:33.340 align:start position:0% things that Thomson Reuters has been 00:00:33.340 --> 00:00:36.690 align:start position:0% things that Thomson Reuters has been doing<00:00:33.670> over<00:00:34.180> the<00:00:34.330> last<00:00:34.450> two<00:00:35.170> years<00:00:35.410> in<00:00:36.040> the 00:00:36.690 --> 00:00:36.700 align:start position:0% doing over the last two years in the 00:00:36.700 --> 00:00:39.840 align:start position:0% doing over the last two years in the etherium<00:00:37.090> space<00:00:38.070> but<00:00:39.070> we<00:00:39.220> thought<00:00:39.460> we'd<00:00:39.610> start 00:00:39.840 --> 00:00:39.850 align:start position:0% etherium space but we thought we'd start 00:00:39.850 --> 00:00:42.360 align:start position:0% etherium space but we thought we'd start because<00:00:40.590> over<00:00:41.590> the<00:00:41.680> last<00:00:41.830> couple<00:00:42.010> of<00:00:42.160> days 00:00:42.360 --> 00:00:42.370 align:start position:0% because over the last couple of days 00:00:42.370 --> 00:00:44.490 align:start position:0% because over the last couple of days I've<00:00:42.580> realized<00:00:42.820> that<00:00:43.300> not<00:00:43.870> a<00:00:43.930> lot<00:00:44.140> of<00:00:44.320> you<00:00:44.470> know 00:00:44.490 --> 00:00:44.500 align:start position:0% I've realized that not a lot of you know 00:00:44.500 --> 00:00:49.290 align:start position:0% I've realized that not a lot of you know what<00:00:45.400> or<00:00:46.240> who<00:00:46.270> Thomson<00:00:47.080> Reuters<00:00:47.170> are<00:00:48.150> we<00:00:49.150> are 00:00:49.290 --> 00:00:49.300 align:start position:0% what or who Thomson Reuters are we are 00:00:49.300 --> 00:00:52.770 align:start position:0% what or who Thomson Reuters are we are famous<00:00:49.630> for<00:00:49.870> our<00:00:50.590> Reuters<00:00:51.310> news<00:00:51.340> agency<00:00:51.790> that 00:00:52.770 --> 00:00:52.780 align:start position:0% famous for our Reuters news agency that 00:00:52.780 --> 00:00:54.660 align:start position:0% famous for our Reuters news agency that delivers<00:00:53.260> news<00:00:53.590> to<00:00:53.920> over<00:00:54.190> a<00:00:54.220> billion<00:00:54.640> people 00:00:54.660 --> 00:00:54.670 align:start position:0% delivers news to over a billion people 00:00:54.670 --> 00:00:58.230 align:start position:0% delivers news to over a billion people around<00:00:55.480> the<00:00:55.780> planet<00:00:55.900> every<00:00:56.410> day<00:00:56.970> but<00:00:57.970> what<00:00:58.120> you 00:00:58.230 --> 00:00:58.240 align:start position:0% around the planet every day but what you 00:00:58.240 --> 00:01:00.750 align:start position:0% around the planet every day but what you may<00:00:58.390> not<00:00:58.420> be<00:00:58.660> aware<00:00:58.900> of<00:00:58.960> is<00:00:59.290> that<00:00:59.680> the<00:01:00.280> majority 00:01:00.750 --> 00:01:00.760 align:start position:0% may not be aware of is that the majority 00:01:00.760 --> 00:01:03.090 align:start position:0% may not be aware of is that the majority of<00:01:00.790> our<00:01:00.970> business<00:01:01.030> comes<00:01:01.750> from<00:01:02.100> three 00:01:03.090 --> 00:01:03.100 align:start position:0% of our business comes from three 00:01:03.100 --> 00:01:05.700 align:start position:0% of our business comes from three business<00:01:03.460> units<00:01:03.489> where<00:01:04.059> we<00:01:04.329> are<00:01:04.509> a<00:01:04.750> trusted 00:01:05.700 --> 00:01:05.710 align:start position:0% business units where we are a trusted 00:01:05.710 --> 00:01:08.730 align:start position:0% business units where we are a trusted information<00:01:06.280> provider<00:01:06.969> for<00:01:07.740> professional 00:01:08.730 --> 00:01:08.740 align:start position:0% information provider for professional 00:01:08.740 --> 00:01:11.249 align:start position:0% information provider for professional services<00:01:09.249> across<00:01:09.939> financial<00:01:10.539> and<00:01:10.659> risk<00:01:10.780> tax 00:01:11.249 --> 00:01:11.259 align:start position:0% services across financial and risk tax 00:01:11.259 --> 00:01:15.090 align:start position:0% services across financial and risk tax and<00:01:11.409> accounting<00:01:11.469> and<00:01:11.950> legal<00:01:13.319> so<00:01:14.319> our<00:01:14.710> journey 00:01:15.090 --> 00:01:15.100 align:start position:0% and accounting and legal so our journey 00:01:15.100 --> 00:01:17.809 align:start position:0% and accounting and legal so our journey here<00:01:15.789> started<00:01:16.390> a<00:01:16.810> couple<00:01:17.289> of<00:01:17.350> years<00:01:17.530> ago 00:01:17.809 --> 00:01:17.819 align:start position:0% here started a couple of years ago 00:01:17.819 --> 00:01:22.080 align:start position:0% here started a couple of years ago because<00:01:18.819> I'm<00:01:19.210> based<00:01:19.539> in<00:01:19.840> zhuge<00:01:20.670> which<00:01:21.670> as<00:01:21.909> you 00:01:22.080 --> 00:01:22.090 align:start position:0% because I'm based in zhuge which as you 00:01:22.090 --> 00:01:24.690 align:start position:0% because I'm based in zhuge which as you port<00:01:22.329> mentioned<00:01:22.840> has<00:01:22.990> been<00:01:23.259> coined<00:01:24.009> as<00:01:24.310> Krypto 00:01:24.690 --> 00:01:24.700 align:start position:0% port mentioned has been coined as Krypto 00:01:24.700 --> 00:01:29.870 align:start position:0% port mentioned has been coined as Krypto Valley<00:01:24.939> now<00:01:25.409> and<00:01:26.409> I'd<00:01:26.560> gone<00:01:26.979> back<00:01:27.039> to<00:01:27.549> study<00:01:28.509> a 00:01:29.870 --> 00:01:29.880 align:start position:0% Valley now and I'd gone back to study a 00:01:29.880 --> 00:01:33.239 align:start position:0% Valley now and I'd gone back to study a degree<00:01:30.880> at<00:01:31.030> Oxford<00:01:31.229> and<00:01:32.229> was<00:01:32.619> hunting<00:01:33.039> for<00:01:33.219> a 00:01:33.239 --> 00:01:33.249 align:start position:0% degree at Oxford and was hunting for a 00:01:33.249 --> 00:01:36.779 align:start position:0% degree at Oxford and was hunting for a dissertation<00:01:33.429> topic<00:01:34.259> and<00:01:35.490> Vitalik<00:01:36.490> paper 00:01:36.779 --> 00:01:36.789 align:start position:0% dissertation topic and Vitalik paper 00:01:36.789 --> 00:01:41.069 align:start position:0% dissertation topic and Vitalik paper came<00:01:37.090> out<00:01:37.799> and<00:01:38.799> a<00:01:39.459> lot<00:01:39.969> of<00:01:40.030> the<00:01:40.209> people<00:01:40.479> or 00:01:41.069 --> 00:01:41.079 align:start position:0% came out and a lot of the people or 00:01:41.079 --> 00:01:42.749 align:start position:0% came out and a lot of the people or media<00:01:41.530> were<00:01:41.709> picking<00:01:42.009> it<00:01:42.130> up<00:01:42.219> saying<00:01:42.579> well 00:01:42.749 --> 00:01:42.759 align:start position:0% media were picking it up saying well 00:01:42.759 --> 00:01:44.279 align:start position:0% media were picking it up saying well this<00:01:42.909> is<00:01:43.060> going<00:01:43.209> to<00:01:43.299> disrupt<00:01:43.569> the<00:01:43.749> financial 00:01:44.279 --> 00:01:44.289 align:start position:0% this is going to disrupt the financial 00:01:44.289 --> 00:01:47.069 align:start position:0% this is going to disrupt the financial services<00:01:44.740> tremendously<00:01:45.479> and<00:01:46.479> given<00:01:46.779> that<00:01:46.899> a 00:01:47.069 --> 00:01:47.079 align:start position:0% services tremendously and given that a 00:01:47.079 --> 00:01:48.599 align:start position:0% services tremendously and given that a large<00:01:47.350> proportion<00:01:47.679> of<00:01:48.100> our<00:01:48.219> revenue<00:01:48.579> comes 00:01:48.599 --> 00:01:48.609 align:start position:0% large proportion of our revenue comes 00:01:48.609 --> 00:01:50.999 align:start position:0% large proportion of our revenue comes from<00:01:48.939> the<00:01:49.090> financial<00:01:49.569> services<00:01:49.990> business<00:01:50.170> the 00:01:50.999 --> 00:01:51.009 align:start position:0% from the financial services business the 00:01:51.009 --> 00:01:52.830 align:start position:0% from the financial services business the question<00:01:51.399> was<00:01:51.549> well<00:01:52.090> how's<00:01:52.359> that<00:01:52.569> going<00:01:52.779> to 00:01:52.830 --> 00:01:52.840 align:start position:0% question was well how's that going to 00:01:52.840 --> 00:01:57.359 align:start position:0% question was well how's that going to impact<00:01:53.079> us<00:01:53.969> so<00:01:54.969> of<00:01:55.090> course<00:01:55.560> not<00:01:56.560> knowing<00:01:56.950> where 00:01:57.359 --> 00:01:57.369 align:start position:0% impact us so of course not knowing where 00:01:57.369 --> 00:01:58.980 align:start position:0% impact us so of course not knowing where aetherium<00:01:57.700> was<00:01:57.969> based<00:01:58.240> I<00:01:58.509> reached<00:01:58.719> out<00:01:58.929> to 00:01:58.980 --> 00:01:58.990 align:start position:0% aetherium was based I reached out to 00:01:58.990 --> 00:02:02.370 align:start position:0% aetherium was based I reached out to vitalic<00:02:00.509> these<00:02:01.509> were<00:02:01.630> the<00:02:01.749> days<00:02:01.899> before<00:02:02.259> he 00:02:02.370 --> 00:02:02.380 align:start position:0% vitalic these were the days before he 00:02:02.380 --> 00:02:04.769 align:start position:0% vitalic these were the days before he was<00:02:02.409> famous<00:02:02.679> so<00:02:03.639> he<00:02:04.179> was<00:02:04.299> very<00:02:04.450> happy<00:02:04.659> to 00:02:04.769 --> 00:02:04.779 align:start position:0% was famous so he was very happy to 00:02:04.779 --> 00:02:07.349 align:start position:0% was famous so he was very happy to answer<00:02:05.200> my<00:02:05.289> email<00:02:05.590> fortunately<00:02:06.340> and<00:02:06.969> we<00:02:07.149> met 00:02:07.349 --> 00:02:07.359 align:start position:0% answer my email fortunately and we met 00:02:07.359 --> 00:02:10.290 align:start position:0% answer my email fortunately and we met up<00:02:07.479> for<00:02:07.509> a<00:02:07.810> coffee<00:02:08.200> and<00:02:08.380> Zook<00:02:08.740> I<00:02:09.580> had<00:02:10.000> no<00:02:10.180> idea 00:02:10.290 --> 00:02:10.300 align:start position:0% up for a coffee and Zook I had no idea 00:02:10.300 --> 00:02:11.850 align:start position:0% up for a coffee and Zook I had no idea that<00:02:10.540> he<00:02:10.750> lived<00:02:10.930> two<00:02:11.140> kilometers<00:02:11.650> down<00:02:11.830> the 00:02:11.850 --> 00:02:11.860 align:start position:0% that he lived two kilometers down the 00:02:11.860 --> 00:02:12.260 align:start position:0% that he lived two kilometers down the road 00:02:12.260 --> 00:02:12.270 align:start position:0% road 00:02:12.270 --> 00:02:16.430 align:start position:0% road from<00:02:12.360> me<00:02:14.030> he<00:02:15.030> more<00:02:15.330> or<00:02:15.360> less<00:02:15.450> said<00:02:15.810> very 00:02:16.430 --> 00:02:16.440 align:start position:0% from me he more or less said very 00:02:16.440 --> 00:02:18.200 align:start position:0% from me he more or less said very quickly<00:02:16.710> you<00:02:17.160> guys<00:02:17.370> need<00:02:17.670> to<00:02:17.700> be<00:02:17.880> an<00:02:17.970> Oracle 00:02:18.200 --> 00:02:18.210 align:start position:0% quickly you guys need to be an Oracle 00:02:18.210 --> 00:02:21.770 align:start position:0% quickly you guys need to be an Oracle the<00:02:19.310> financial<00:02:20.310> services<00:02:20.730> industry<00:02:20.790> trusts 00:02:21.770 --> 00:02:21.780 align:start position:0% the financial services industry trusts 00:02:21.780 --> 00:02:24.800 align:start position:0% the financial services industry trusts you<00:02:22.020> you're<00:02:22.680> an<00:02:22.770> information<00:02:23.310> provider<00:02:23.810> and 00:02:24.800 --> 00:02:24.810 align:start position:0% you you're an information provider and 00:02:24.810 --> 00:02:27.140 align:start position:0% you you're an information provider and we<00:02:25.290> need<00:02:25.530> to<00:02:25.650> bring<00:02:25.860> those<00:02:26.070> capabilities<00:02:26.550> to 00:02:27.140 --> 00:02:27.150 align:start position:0% we need to bring those capabilities to 00:02:27.150 --> 00:02:29.870 align:start position:0% we need to bring those capabilities to aetherium<00:02:27.710> so<00:02:28.710> the<00:02:28.830> journey<00:02:29.070> really<00:02:29.280> started 00:02:29.870 --> 00:02:29.880 align:start position:0% aetherium so the journey really started 00:02:29.880 --> 00:02:32.840 align:start position:0% aetherium so the journey really started there<00:02:30.180> and<00:02:30.390> as<00:02:31.020> I<00:02:31.920> was<00:02:32.040> looking<00:02:32.220> at<00:02:32.490> the<00:02:32.580> space 00:02:32.840 --> 00:02:32.850 align:start position:0% there and as I was looking at the space 00:02:32.850 --> 00:02:35.900 align:start position:0% there and as I was looking at the space the<00:02:33.120> question<00:02:33.510> became<00:02:33.900> so<00:02:34.890> what<00:02:35.460> part<00:02:35.790> of 00:02:35.900 --> 00:02:35.910 align:start position:0% the question became so what part of 00:02:35.910 --> 00:02:37.790 align:start position:0% the question became so what part of financial<00:02:36.540> services<00:02:36.990> is<00:02:37.170> like<00:02:37.380> me<00:02:37.560> to<00:02:37.680> get 00:02:37.790 --> 00:02:37.800 align:start position:0% financial services is like me to get 00:02:37.800 --> 00:02:40.880 align:start position:0% financial services is like me to get impacted<00:02:38.400> first<00:02:39.230> so<00:02:40.230> we<00:02:40.350> put<00:02:40.560> together<00:02:40.680> a 00:02:40.880 --> 00:02:40.890 align:start position:0% impacted first so we put together a 00:02:40.890 --> 00:02:44.020 align:start position:0% impacted first so we put together a model<00:02:41.100> that<00:02:42.030> we<00:02:42.420> call<00:02:42.570> the<00:02:42.720> three<00:02:42.990> V's<00:02:43.170> model 00:02:44.020 --> 00:02:44.030 align:start position:0% model that we call the three V's model 00:02:44.030 --> 00:02:48.170 align:start position:0% model that we call the three V's model volume<00:02:45.030> value<00:02:45.840> and<00:02:46.050> venue<00:02:46.610> you<00:02:47.610> can't<00:02:47.850> see<00:02:48.030> the 00:02:48.170 --> 00:02:48.180 align:start position:0% volume value and venue you can't see the 00:02:48.180 --> 00:02:49.940 align:start position:0% volume value and venue you can't see the venue<00:02:48.390> axis<00:02:48.930> that's<00:02:49.140> going<00:02:49.410> in<00:02:49.560> and<00:02:49.710> out<00:02:49.800> of 00:02:49.940 --> 00:02:49.950 align:start position:0% venue axis that's going in and out of 00:02:49.950 --> 00:02:52.880 align:start position:0% venue axis that's going in and out of the<00:02:50.010> page<00:02:50.220> but<00:02:51.180> it's<00:02:51.330> essentially<00:02:51.960> the 00:02:52.880 --> 00:02:52.890 align:start position:0% the page but it's essentially the 00:02:52.890 --> 00:02:54.980 align:start position:0% the page but it's essentially the difference<00:02:53.700> between<00:02:53.850> centralized<00:02:54.750> and 00:02:54.980 --> 00:02:54.990 align:start position:0% difference between centralized and 00:02:54.990 --> 00:02:58.130 align:start position:0% difference between centralized and decentralized<00:02:55.140> venues<00:02:56.330> but<00:02:57.330> on<00:02:57.480> the<00:02:57.600> axis 00:02:58.130 --> 00:02:58.140 align:start position:0% decentralized venues but on the axis 00:02:58.140 --> 00:03:00.140 align:start position:0% decentralized venues but on the axis that<00:02:58.320> I've<00:02:58.440> decided<00:02:59.250> to<00:02:59.430> talk<00:02:59.640> about<00:02:59.760> today 00:03:00.140 --> 00:03:00.150 align:start position:0% that I've decided to talk about today 00:03:00.150 --> 00:03:03.080 align:start position:0% that I've decided to talk about today you've<00:03:00.360> got<00:03:00.620> value<00:03:01.620> on<00:03:02.280> the<00:03:02.430> y-axis<00:03:02.550> and 00:03:03.080 --> 00:03:03.090 align:start position:0% you've got value on the y-axis and 00:03:03.090 --> 00:03:06.680 align:start position:0% you've got value on the y-axis and volume<00:03:03.420> of<00:03:03.780> transactions<00:03:04.530> on<00:03:04.890> the<00:03:05.040> x-axis<00:03:05.690> so 00:03:06.680 --> 00:03:06.690 align:start position:0% volume of transactions on the x-axis so 00:03:06.690 --> 00:03:08.840 align:start position:0% volume of transactions on the x-axis so if<00:03:06.750> you<00:03:06.840> look<00:03:06.990> at<00:03:07.080> the<00:03:07.170> top<00:03:07.410> right<00:03:07.860> corner<00:03:07.890> so 00:03:08.840 --> 00:03:08.850 align:start position:0% if you look at the top right corner so 00:03:08.850 --> 00:03:11.660 align:start position:0% if you look at the top right corner so this<00:03:09.000> is<00:03:09.150> the<00:03:09.270> global<00:03:09.510> capital<00:03:10.140> segment<00:03:10.670> for 00:03:11.660 --> 00:03:11.670 align:start position:0% this is the global capital segment for 00:03:11.670 --> 00:03:13.760 align:start position:0% this is the global capital segment for an<00:03:11.760> exchange<00:03:12.180> public<00:03:12.600> equity<00:03:13.080> exchanges 00:03:13.760 --> 00:03:13.770 align:start position:0% an exchange public equity exchanges 00:03:13.770 --> 00:03:16.760 align:start position:0% an exchange public equity exchanges government<00:03:14.640> bonds<00:03:14.850> these<00:03:15.840> are<00:03:16.020> incredibly 00:03:16.760 --> 00:03:16.770 align:start position:0% government bonds these are incredibly 00:03:16.770 --> 00:03:20.240 align:start position:0% government bonds these are incredibly sophisticated<00:03:17.780> markets<00:03:18.780> today<00:03:19.250> decade's 00:03:20.240 --> 00:03:20.250 align:start position:0% sophisticated markets today decade's 00:03:20.250 --> 00:03:23.150 align:start position:0% sophisticated markets today decade's worth<00:03:20.459> of<00:03:20.940> improvements<00:03:21.530> yes<00:03:22.530> people<00:03:22.800> point 00:03:23.150 --> 00:03:23.160 align:start position:0% worth of improvements yes people point 00:03:23.160 --> 00:03:24.830 align:start position:0% worth of improvements yes people point at<00:03:23.280> them<00:03:23.459> and<00:03:23.610> say<00:03:23.730> they<00:03:23.910> work<00:03:24.060> inefficiently 00:03:24.830 --> 00:03:24.840 align:start position:0% at them and say they work inefficiently 00:03:24.840 --> 00:03:28.850 align:start position:0% at them and say they work inefficiently but<00:03:25.440> actually<00:03:25.920> the<00:03:26.990> time<00:03:27.990> and<00:03:28.320> effort<00:03:28.709> it's 00:03:28.850 --> 00:03:28.860 align:start position:0% but actually the time and effort it's 00:03:28.860 --> 00:03:30.380 align:start position:0% but actually the time and effort it's going<00:03:28.950> to<00:03:29.160> take<00:03:29.370> to<00:03:29.700> migrate<00:03:30.180> those 00:03:30.380 --> 00:03:30.390 align:start position:0% going to take to migrate those 00:03:30.390 --> 00:03:32.210 align:start position:0% going to take to migrate those industries<00:03:30.930> and<00:03:31.230> those<00:03:31.410> markets<00:03:31.830> is<00:03:32.010> quite 00:03:32.210 --> 00:03:32.220 align:start position:0% industries and those markets is quite 00:03:32.220 --> 00:03:34.580 align:start position:0% industries and those markets is quite considerable<00:03:33.020> so<00:03:34.020> we're<00:03:34.140> not<00:03:34.230> saying<00:03:34.440> it 00:03:34.580 --> 00:03:34.590 align:start position:0% considerable so we're not saying it 00:03:34.590 --> 00:03:36.260 align:start position:0% considerable so we're not saying it won't<00:03:34.800> happen<00:03:35.100> we're<00:03:35.850> just<00:03:36.030> saying<00:03:36.180> that 00:03:36.260 --> 00:03:36.270 align:start position:0% won't happen we're just saying that 00:03:36.270 --> 00:03:38.000 align:start position:0% won't happen we're just saying that probably<00:03:36.570> that<00:03:37.230> won't<00:03:37.440> be<00:03:37.620> the<00:03:37.770> place<00:03:37.980> where 00:03:38.000 --> 00:03:38.010 align:start position:0% probably that won't be the place where 00:03:38.010 --> 00:03:41.000 align:start position:0% probably that won't be the place where it<00:03:38.340> starts<00:03:38.459> first<00:03:39.500> so<00:03:40.500> if<00:03:40.560> you<00:03:40.650> go<00:03:40.740> to<00:03:40.770> the 00:03:41.000 --> 00:03:41.010 align:start position:0% it starts first so if you go to the 00:03:41.010 --> 00:03:43.540 align:start position:0% it starts first so if you go to the opposite<00:03:41.580> end<00:03:41.820> this<00:03:42.630> is<00:03:42.780> the<00:03:42.870> retail<00:03:43.230> space 00:03:43.540 --> 00:03:43.550 align:start position:0% opposite end this is the retail space 00:03:43.550 --> 00:03:46.430 align:start position:0% opposite end this is the retail space peer-to-peer<00:03:44.550> lending<00:03:45.209> music<00:03:46.020> royalties 00:03:46.430 --> 00:03:46.440 align:start position:0% peer-to-peer lending music royalties 00:03:46.440 --> 00:03:50.090 align:start position:0% peer-to-peer lending music royalties gambling<00:03:48.020> you've<00:03:49.020> seen<00:03:49.230> a<00:03:49.260> lot<00:03:49.530> of<00:03:49.560> startups 00:03:50.090 --> 00:03:50.100 align:start position:0% gambling you've seen a lot of startups 00:03:50.100 --> 00:03:52.100 align:start position:0% gambling you've seen a lot of startups that's<00:03:50.610> starting<00:03:51.209> to<00:03:51.360> attack<00:03:51.600> this<00:03:51.810> space 00:03:52.100 --> 00:03:52.110 align:start position:0% that's starting to attack this space 00:03:52.110 --> 00:03:54.560 align:start position:0% that's starting to attack this space it's<00:03:52.680> really<00:03:53.070> interesting<00:03:53.370> there's<00:03:54.150> a<00:03:54.240> lot<00:03:54.450> of 00:03:54.560 --> 00:03:54.570 align:start position:0% it's really interesting there's a lot of 00:03:54.570 --> 00:03:57.230 align:start position:0% it's really interesting there's a lot of activity<00:03:55.080> here<00:03:55.320> it's<00:03:56.070> not<00:03:56.250> really<00:03:56.730> a<00:03:56.760> space 00:03:57.230 --> 00:03:57.240 align:start position:0% activity here it's not really a space 00:03:57.240 --> 00:03:59.300 align:start position:0% activity here it's not really a space for<00:03:57.510> Thomson<00:03:57.840> Reuters<00:03:57.959> it's<00:03:58.650> not<00:03:58.860> one<00:03:59.040> that<00:03:59.190> we 00:03:59.300 --> 00:03:59.310 align:start position:0% for Thomson Reuters it's not one that we 00:03:59.310 --> 00:04:02.480 align:start position:0% for Thomson Reuters it's not one that we play<00:03:59.520> in<00:03:59.670> today<00:04:00.890> so<00:04:01.890> in<00:04:01.980> the<00:04:02.070> bottom<00:04:02.220> right 00:04:02.480 --> 00:04:02.490 align:start position:0% play in today so in the bottom right 00:04:02.490 --> 00:04:05.330 align:start position:0% play in today so in the bottom right you've<00:04:02.760> got<00:04:02.910> the<00:04:03.000> Machine<00:04:03.120> age<00:04:03.600> and<00:04:04.070> this<00:04:05.070> I 00:04:05.330 --> 00:04:05.340 align:start position:0% you've got the Machine age and this I 00:04:05.340 --> 00:04:08.630 align:start position:0% you've got the Machine age and this I think<00:04:06.209> will<00:04:06.720> be<00:04:06.900> a<00:04:07.170> huge<00:04:07.709> opportunity<00:04:07.920> for 00:04:08.630 --> 00:04:08.640 align:start position:0% think will be a huge opportunity for 00:04:08.640 --> 00:04:11.570 align:start position:0% think will be a huge opportunity for blockchain<00:04:09.540> technologies<00:04:10.550> Internet<00:04:11.550> of 00:04:11.570 --> 00:04:11.580 align:start position:0% blockchain technologies Internet of 00:04:11.580 --> 00:04:13.820 align:start position:0% blockchain technologies Internet of Things<00:04:11.700> we're<00:04:12.690> already<00:04:12.870> seeing<00:04:13.170> companies 00:04:13.820 --> 00:04:13.830 align:start position:0% Things we're already seeing companies 00:04:13.830 --> 00:04:15.770 align:start position:0% Things we're already seeing companies like<00:04:14.010> Gollum<00:04:14.340> with<00:04:14.489> distributed<00:04:15.180> computation 00:04:15.770 --> 00:04:15.780 align:start position:0% like Gollum with distributed computation 00:04:15.780 --> 00:04:19.310 align:start position:0% like Gollum with distributed computation and<00:04:16.080> I<00:04:16.140> expect<00:04:16.530> downstairs<00:04:17.120> so<00:04:18.120> for<00:04:18.690> us<00:04:18.840> we 00:04:19.310 --> 00:04:19.320 align:start position:0% and I expect downstairs so for us we 00:04:19.320 --> 00:04:22.099 align:start position:0% and I expect downstairs so for us we felt<00:04:19.500> this<00:04:19.680> was<00:04:19.739> a<00:04:19.890> bit<00:04:20.100> early<00:04:20.750> we<00:04:21.750> started 00:04:22.099 --> 00:04:22.109 align:start position:0% felt this was a bit early we started 00:04:22.109 --> 00:04:23.930 align:start position:0% felt this was a bit early we started doing<00:04:22.200> this<00:04:22.350> analysis<00:04:22.860> as<00:04:23.010> I<00:04:23.130> mentioned<00:04:23.460> most 00:04:23.930 --> 00:04:23.940 align:start position:0% doing this analysis as I mentioned most 00:04:23.940 --> 00:04:25.520 align:start position:0% doing this analysis as I mentioned most two<00:04:24.240> years<00:04:24.450> ago 00:04:25.520 --> 00:04:25.530 align:start position:0% two years ago 00:04:25.530 --> 00:04:28.010 align:start position:0% two years ago so<00:04:25.740> the<00:04:26.460> question<00:04:26.820> became<00:04:27.120> what<00:04:27.660> about<00:04:27.870> this 00:04:28.010 --> 00:04:28.020 align:start position:0% so the question became what about this 00:04:28.020 --> 00:04:30.590 align:start position:0% so the question became what about this last<00:04:28.230> segment<00:04:28.970> these<00:04:29.970> are<00:04:30.120> the<00:04:30.210> big-ticket 00:04:30.590 --> 00:04:30.600 align:start position:0% last segment these are the big-ticket 00:04:30.600 --> 00:04:31.370 align:start position:0% last segment these are the big-ticket items 00:04:31.370 --> 00:04:31.380 align:start position:0% items 00:04:31.380 --> 00:04:34.400 align:start position:0% items high<00:04:32.040> value<00:04:32.610> low<00:04:32.850> volume<00:04:33.660> transactions 00:04:34.400 --> 00:04:34.410 align:start position:0% high value low volume transactions 00:04:34.410 --> 00:04:35.890 align:start position:0% high value low volume transactions venture<00:04:34.800> capital<00:04:35.190> private<00:04:35.490> equity 00:04:35.890 --> 00:04:35.900 align:start position:0% venture capital private equity 00:04:35.900 --> 00:04:38.120 align:start position:0% venture capital private equity over-the-counter<00:04:36.900> derivatives<00:04:37.200> syndicated 00:04:38.120 --> 00:04:38.130 align:start position:0% over-the-counter derivatives syndicated 00:04:38.130 --> 00:04:41.150 align:start position:0% over-the-counter derivatives syndicated loans<00:04:38.390> this<00:04:39.390> was<00:04:39.600> where<00:04:39.810> we<00:04:39.990> decided<00:04:40.560> to<00:04:40.740> focus 00:04:41.150 --> 00:04:41.160 align:start position:0% loans this was where we decided to focus 00:04:41.160 --> 00:04:42.140 align:start position:0% loans this was where we decided to focus our<00:04:41.370> effort 00:04:42.140 --> 00:04:42.150 align:start position:0% our effort 00:04:42.150 --> 00:04:44.030 align:start position:0% our effort this<00:04:42.930> was<00:04:43.110> the<00:04:43.230> markets<00:04:43.680> these<00:04:43.860> are<00:04:43.980> the 00:04:44.030 --> 00:04:44.040 align:start position:0% this was the markets these are the 00:04:44.040 --> 00:04:45.410 align:start position:0% this was the markets these are the markets<00:04:44.400> that<00:04:44.460> we<00:04:44.550> believed<00:04:44.970> were<00:04:45.180> going<00:04:45.330> to 00:04:45.410 --> 00:04:45.420 align:start position:0% markets that we believed were going to 00:04:45.420 --> 00:04:46.840 align:start position:0% markets that we believed were going to move<00:04:45.570> first 00:04:46.840 --> 00:04:46.850 align:start position:0% move first 00:04:46.850 --> 00:04:49.670 align:start position:0% move first so<00:04:47.850> having<00:04:48.210> sat<00:04:48.420> down<00:04:48.600> with<00:04:48.810> Vitalik<00:04:49.260> and<00:04:49.470> him 00:04:49.670 --> 00:04:49.680 align:start position:0% so having sat down with Vitalik and him 00:04:49.680 --> 00:04:51.500 align:start position:0% so having sat down with Vitalik and him having<00:04:49.950> told<00:04:50.190> me<00:04:50.340> well<00:04:50.700> we<00:04:50.970> really<00:04:51.240> need<00:04:51.390> an 00:04:51.500 --> 00:04:51.510 align:start position:0% having told me well we really need an 00:04:51.510 --> 00:04:53.630 align:start position:0% having told me well we really need an Oracle<00:04:51.990> I<00:04:52.200> thought<00:04:52.800> that<00:04:53.010> rather<00:04:53.190> than<00:04:53.340> just 00:04:53.630 --> 00:04:53.640 align:start position:0% Oracle I thought that rather than just 00:04:53.640 --> 00:04:56.660 align:start position:0% Oracle I thought that rather than just believe<00:04:53.940> him<00:04:53.970> outright<00:04:55.280> let's<00:04:56.280> have<00:04:56.400> a<00:04:56.430> think 00:04:56.660 --> 00:04:56.670 align:start position:0% believe him outright let's have a think 00:04:56.670 --> 00:04:59.780 align:start position:0% believe him outright let's have a think about<00:04:56.970> what<00:04:57.300> data<00:04:57.780> would<00:04:58.169> be<00:04:58.230> needed<00:04:58.830> from<00:04:59.580> an 00:04:59.780 --> 00:04:59.790 align:start position:0% about what data would be needed from an 00:04:59.790 --> 00:05:03.530 align:start position:0% about what data would be needed from an off<00:04:59.910> chain<00:05:00.240> provider<00:05:00.720> like<00:05:01.020> us<00:05:01.610> so<00:05:02.610> looking<00:05:03.419> at 00:05:03.530 --> 00:05:03.540 align:start position:0% off chain provider like us so looking at 00:05:03.540 --> 00:05:05.180 align:start position:0% off chain provider like us so looking at the<00:05:03.600> conditional<00:05:04.020> transaction<00:05:04.560> dependencies 00:05:05.180 --> 00:05:05.190 align:start position:0% the conditional transaction dependencies 00:05:05.190 --> 00:05:07.370 align:start position:0% the conditional transaction dependencies you<00:05:05.430> can<00:05:05.880> obviously<00:05:06.180> create<00:05:06.540> lots<00:05:06.930> of<00:05:07.110> smart 00:05:07.370 --> 00:05:07.380 align:start position:0% you can obviously create lots of smart 00:05:07.380 --> 00:05:10.159 align:start position:0% you can obviously create lots of smart contract<00:05:07.800> opportunities<00:05:08.430> using<00:05:08.910> on<00:05:09.419> chain 00:05:10.159 --> 00:05:10.169 align:start position:0% contract opportunities using on chain 00:05:10.169 --> 00:05:13.040 align:start position:0% contract opportunities using on chain data<00:05:10.910> doesn't<00:05:11.910> really<00:05:12.060> need<00:05:12.270> an<00:05:12.419> Oracle<00:05:12.840> the 00:05:13.040 --> 00:05:13.050 align:start position:0% data doesn't really need an Oracle the 00:05:13.050 --> 00:05:14.570 align:start position:0% data doesn't really need an Oracle the data<00:05:13.410> is<00:05:13.590> already<00:05:13.919> there<00:05:14.100> that<00:05:14.310> you<00:05:14.400> can 00:05:14.570 --> 00:05:14.580 align:start position:0% data is already there that you can 00:05:14.580 --> 00:05:17.690 align:start position:0% data is already there that you can reference<00:05:15.560> but<00:05:16.560> as<00:05:16.680> we<00:05:16.830> looked<00:05:17.040> more<00:05:17.280> and<00:05:17.460> more 00:05:17.690 --> 00:05:17.700 align:start position:0% reference but as we looked more and more 00:05:17.700 --> 00:05:20.110 align:start position:0% reference but as we looked more and more we<00:05:18.240> realized<00:05:18.660> that<00:05:19.110> he<00:05:19.260> was<00:05:19.440> indeed<00:05:19.590> right 00:05:20.110 --> 00:05:20.120 align:start position:0% we realized that he was indeed right 00:05:20.120 --> 00:05:22.040 align:start position:0% we realized that he was indeed right which<00:05:21.120> I<00:05:21.240> probably<00:05:21.450> shouldn't<00:05:21.750> have<00:05:21.810> doubted 00:05:22.040 --> 00:05:22.050 align:start position:0% which I probably shouldn't have doubted 00:05:22.050 --> 00:05:26.150 align:start position:0% which I probably shouldn't have doubted him<00:05:23.030> and<00:05:24.030> the<00:05:24.510> majority<00:05:24.990> of<00:05:25.200> opportunities 00:05:26.150 --> 00:05:26.160 align:start position:0% him and the majority of opportunities 00:05:26.160 --> 00:05:28.370 align:start position:0% him and the majority of opportunities are<00:05:26.400> actually<00:05:26.820> those<00:05:27.480> that<00:05:27.750> require<00:05:28.110> off 00:05:28.370 --> 00:05:28.380 align:start position:0% are actually those that require off 00:05:28.380 --> 00:05:32.510 align:start position:0% are actually those that require off chain<00:05:28.680> data<00:05:29.150> and<00:05:30.150> I<00:05:30.510> think<00:05:30.690> in<00:05:30.870> the<00:05:31.740> last<00:05:31.950> two 00:05:32.510 --> 00:05:32.520 align:start position:0% chain data and I think in the last two 00:05:32.520 --> 00:05:36.710 align:start position:0% chain data and I think in the last two years<00:05:32.550> since<00:05:33.360> we<00:05:33.540> did<00:05:33.690> this<00:05:34.370> that<00:05:35.720> hypothesis 00:05:36.710 --> 00:05:36.720 align:start position:0% years since we did this that hypothesis 00:05:36.720 --> 00:05:40.670 align:start position:0% years since we did this that hypothesis has<00:05:36.870> been<00:05:37.050> validated<00:05:37.229> over<00:05:37.890> and<00:05:38.010> over<00:05:38.630> so<00:05:39.680> we 00:05:40.670 --> 00:05:40.680 align:start position:0% has been validated over and over so we 00:05:40.680 --> 00:05:42.740 align:start position:0% has been validated over and over so we looked<00:05:40.890> at<00:05:41.010> all<00:05:41.160> of<00:05:41.220> these<00:05:41.460> and<00:05:41.520> thought<00:05:42.060> you 00:05:42.740 --> 00:05:42.750 align:start position:0% looked at all of these and thought you 00:05:42.750 --> 00:05:45.280 align:start position:0% looked at all of these and thought you know<00:05:42.870> the<00:05:43.020> probably<00:05:43.500> the<00:05:43.650> space<00:05:43.950> to<00:05:44.220> start<00:05:44.520> is 00:05:45.280 --> 00:05:45.290 align:start position:0% know the probably the space to start is 00:05:45.290 --> 00:05:47.930 align:start position:0% know the probably the space to start is benchmarks<00:05:46.290> and<00:05:46.500> values<00:05:47.220> for<00:05:47.250> derivatives 00:05:47.930 --> 00:05:47.940 align:start position:0% benchmarks and values for derivatives 00:05:47.940 --> 00:05:50.750 align:start position:0% benchmarks and values for derivatives given<00:05:48.810> that<00:05:49.169> that<00:05:49.320> fell<00:05:49.680> squarely<00:05:50.010> into<00:05:50.610> that 00:05:50.750 --> 00:05:50.760 align:start position:0% given that that fell squarely into that 00:05:50.760 --> 00:05:52.969 align:start position:0% given that that fell squarely into that top<00:05:51.030> left<00:05:51.330> quadrant<00:05:51.990> from<00:05:52.470> the<00:05:52.620> previous 00:05:52.969 --> 00:05:52.979 align:start position:0% top left quadrant from the previous 00:05:52.979 --> 00:05:56.930 align:start position:0% top left quadrant from the previous slide<00:05:54.350> so<00:05:55.350> we<00:05:55.500> created<00:05:55.860> a<00:05:56.130> capability<00:05:56.729> that 00:05:56.930 --> 00:05:56.940 align:start position:0% slide so we created a capability that 00:05:56.940 --> 00:06:02.180 align:start position:0% slide so we created a capability that we've<00:05:57.270> called<00:05:57.570> block<00:05:57.810> 1<00:05:58.020> IQ<00:06:00.290> block<00:06:01.290> 1<00:06:01.470> IQ<00:06:01.890> is<00:06:02.070> an 00:06:02.180 --> 00:06:02.190 align:start position:0% we've called block 1 IQ block 1 IQ is an 00:06:02.190 --> 00:06:06.440 align:start position:0% we've called block 1 IQ block 1 IQ is an Oracle<00:06:02.479> it's<00:06:03.479> in<00:06:03.690> beta<00:06:04.220> but<00:06:05.220> it's<00:06:05.400> live<00:06:05.610> and<00:06:06.000> it 00:06:06.440 --> 00:06:06.450 align:start position:0% Oracle it's in beta but it's live and it 00:06:06.450 --> 00:06:08.780 align:start position:0% Oracle it's in beta but it's live and it works<00:06:06.660> and<00:06:07.050> it's<00:06:07.680> compatible<00:06:08.070> with<00:06:08.400> both 00:06:08.780 --> 00:06:08.790 align:start position:0% works and it's compatible with both 00:06:08.790 --> 00:06:11.719 align:start position:0% works and it's compatible with both quarter<00:06:09.210> and<00:06:09.390> aetherium<00:06:10.250> we've<00:06:11.250> been<00:06:11.400> talking 00:06:11.719 --> 00:06:11.729 align:start position:0% quarter and aetherium we've been talking 00:06:11.729 --> 00:06:13.790 align:start position:0% quarter and aetherium we've been talking with<00:06:11.820> the<00:06:11.940> JP<00:06:12.240> Morgan<00:06:12.540> guys<00:06:12.720> about<00:06:13.380> making 00:06:13.790 --> 00:06:13.800 align:start position:0% with the JP Morgan guys about making 00:06:13.800 --> 00:06:16.610 align:start position:0% with the JP Morgan guys about making extending<00:06:14.750> compatibility<00:06:15.750> to<00:06:15.960> quorum<00:06:16.470> as 00:06:16.610 --> 00:06:16.620 align:start position:0% extending compatibility to quorum as 00:06:16.620 --> 00:06:18.800 align:start position:0% extending compatibility to quorum as well<00:06:16.860> but<00:06:17.610> that<00:06:18.090> shouldn't<00:06:18.390> be<00:06:18.479> very<00:06:18.660> much 00:06:18.800 --> 00:06:18.810 align:start position:0% well but that shouldn't be very much 00:06:18.810 --> 00:06:21.409 align:start position:0% well but that shouldn't be very much effort<00:06:19.110> at<00:06:19.200> all<00:06:19.410> and<00:06:19.710> the<00:06:20.550> data<00:06:20.760> sets<00:06:21.180> we've 00:06:21.409 --> 00:06:21.419 align:start position:0% effort at all and the data sets we've 00:06:21.419 --> 00:06:24.800 align:start position:0% effort at all and the data sets we've started<00:06:21.750> with<00:06:22.169> that<00:06:23.040> share<00:06:23.310> prices<00:06:23.810> so 00:06:24.800 --> 00:06:24.810 align:start position:0% started with that share prices so 00:06:24.810 --> 00:06:28.550 align:start position:0% started with that share prices so exchange<00:06:25.550> public<00:06:26.550> exchange<00:06:26.940> equity<00:06:27.360> data<00:06:27.600> for 00:06:28.550 --> 00:06:28.560 align:start position:0% exchange public exchange equity data for 00:06:28.560 --> 00:06:31.580 align:start position:0% exchange public exchange equity data for an<00:06:28.650> exchange<00:06:29.040> data<00:06:29.390> corporate<00:06:30.390> actions<00:06:30.780> which 00:06:31.580 --> 00:06:31.590 align:start position:0% an exchange data corporate actions which 00:06:31.590 --> 00:06:34.250 align:start position:0% an exchange data corporate actions which are<00:06:31.710> things<00:06:31.919> like<00:06:32.040> mergers<00:06:32.820> buybacks<00:06:33.419> stock 00:06:34.250 --> 00:06:34.260 align:start position:0% are things like mergers buybacks stock 00:06:34.260 --> 00:06:37.279 align:start position:0% are things like mergers buybacks stock splits<00:06:34.680> dividends<00:06:35.460> coupons<00:06:36.180> anything<00:06:37.020> where 00:06:37.279 --> 00:06:37.289 align:start position:0% splits dividends coupons anything where 00:06:37.289 --> 00:06:38.659 align:start position:0% splits dividends coupons anything where there's<00:06:37.470> a<00:06:37.500> change 00:06:38.659 --> 00:06:38.669 align:start position:0% there's a change 00:06:38.669 --> 00:06:43.309 align:start position:0% there's a change cryptocurrency<00:06:39.509> rates<00:06:40.139> from<00:06:41.069> our<00:06:42.319> partner 00:06:43.309 --> 00:06:43.319 align:start position:0% cryptocurrency rates from our partner 00:06:43.319 --> 00:06:47.059 align:start position:0% cryptocurrency rates from our partner company<00:06:43.919> crypto<00:06:44.819> compare<00:06:46.069> financial 00:06:47.059 --> 00:06:47.069 align:start position:0% company crypto compare financial 00:06:47.069 --> 00:06:49.219 align:start position:0% company crypto compare financial benchmarks<00:06:47.939> so<00:06:48.599> these<00:06:48.780> are<00:06:48.930> things<00:06:49.139> like 00:06:49.219 --> 00:06:49.229 align:start position:0% benchmarks so these are things like 00:06:49.229 --> 00:06:50.929 align:start position:0% benchmarks so these are things like Libor<00:06:49.740> rates<00:06:49.770> that<00:06:50.460> a<00:06:50.490> lot<00:06:50.729> of<00:06:50.759> the 00:06:50.929 --> 00:06:50.939 align:start position:0% Libor rates that a lot of the 00:06:50.939 --> 00:06:52.219 align:start position:0% Libor rates that a lot of the derivatives<00:06:51.449> around<00:06:51.689> the<00:06:51.780> world<00:06:51.930> today 00:06:52.219 --> 00:06:52.229 align:start position:0% derivatives around the world today 00:06:52.229 --> 00:06:54.409 align:start position:0% derivatives around the world today reference<00:06:52.889> and<00:06:53.159> then<00:06:53.849> the<00:06:53.969> knowledge<00:06:54.240> graph 00:06:54.409 --> 00:06:54.419 align:start position:0% reference and then the knowledge graph 00:06:54.419 --> 00:06:56.570 align:start position:0% reference and then the knowledge graph which<00:06:55.020> I<00:06:55.169> won't<00:06:55.349> discuss<00:06:55.919> now<00:06:56.129> but<00:06:56.310> I'll<00:06:56.400> come 00:06:56.570 --> 00:06:56.580 align:start position:0% which I won't discuss now but I'll come 00:06:56.580 --> 00:06:57.760 align:start position:0% which I won't discuss now but I'll come back<00:06:56.610> to<00:06:56.819> you<00:06:56.909> later 00:06:57.760 --> 00:06:57.770 align:start position:0% back to you later 00:06:57.770 --> 00:07:01.820 align:start position:0% back to you later so<00:06:58.939> the<00:06:59.939> problem<00:07:00.360> facing<00:07:00.629> us<00:07:01.199> was<00:07:01.560> slightly 00:07:01.820 --> 00:07:01.830 align:start position:0% so the problem facing us was slightly 00:07:01.830 --> 00:07:03.890 align:start position:0% so the problem facing us was slightly different<00:07:02.129> to<00:07:02.460> some<00:07:02.669> of<00:07:02.789> the<00:07:02.879> other<00:07:03.060> Oracle 00:07:03.890 --> 00:07:03.900 align:start position:0% different to some of the other Oracle 00:07:03.900 --> 00:07:05.990 align:start position:0% different to some of the other Oracle players<00:07:04.319> that<00:07:04.740> are<00:07:05.159> following<00:07:05.460> us<00:07:05.729> later 00:07:05.990 --> 00:07:06.000 align:start position:0% players that are following us later 00:07:06.000 --> 00:07:09.080 align:start position:0% players that are following us later today<00:07:06.270> in<00:07:07.020> that<00:07:07.590> they<00:07:08.340> needed<00:07:08.550> to<00:07:08.789> create 00:07:09.080 --> 00:07:09.090 align:start position:0% today in that they needed to create 00:07:09.090 --> 00:07:12.559 align:start position:0% today in that they needed to create trust<00:07:09.449> first<00:07:10.400> but<00:07:11.400> customers<00:07:12.000> already<00:07:12.150> trust 00:07:12.559 --> 00:07:12.569 align:start position:0% trust first but customers already trust 00:07:12.569 --> 00:07:14.749 align:start position:0% trust first but customers already trust us<00:07:12.919> we're<00:07:13.919> the<00:07:14.099> trusted<00:07:14.520> information 00:07:14.749 --> 00:07:14.759 align:start position:0% us we're the trusted information 00:07:14.759 --> 00:07:16.670 align:start position:0% us we're the trusted information provider<00:07:15.419> for<00:07:15.870> the<00:07:15.960> majority<00:07:16.229> of<00:07:16.469> the 00:07:16.670 --> 00:07:16.680 align:start position:0% provider for the majority of the 00:07:16.680 --> 00:07:19.640 align:start position:0% provider for the majority of the financial<00:07:17.129> services<00:07:17.310> industry<00:07:18.500> so<00:07:19.500> our 00:07:19.640 --> 00:07:19.650 align:start position:0% financial services industry so our 00:07:19.650 --> 00:07:21.230 align:start position:0% financial services industry so our problem<00:07:19.979> was<00:07:20.279> slightly<00:07:20.580> different 00:07:21.230 --> 00:07:21.240 align:start position:0% problem was slightly different 00:07:21.240 --> 00:07:24.469 align:start position:0% problem was slightly different it's<00:07:22.020> been<00:07:22.259> around<00:07:22.759> enabling<00:07:23.759> the<00:07:24.060> etherium 00:07:24.469 --> 00:07:24.479 align:start position:0% it's been around enabling the etherium 00:07:24.479 --> 00:07:27.640 align:start position:0% it's been around enabling the etherium community<00:07:24.990> with<00:07:25.409> high<00:07:25.650> quality<00:07:25.759> trusted<00:07:26.759> data 00:07:27.640 --> 00:07:27.650 align:start position:0% community with high quality trusted data 00:07:27.650 --> 00:07:29.899 align:start position:0% community with high quality trusted data so<00:07:28.650> this<00:07:28.800> is<00:07:28.949> the<00:07:29.039> place<00:07:29.250> we've<00:07:29.430> chosen<00:07:29.669> to 00:07:29.899 --> 00:07:29.909 align:start position:0% so this is the place we've chosen to 00:07:29.909 --> 00:07:32.740 align:start position:0% so this is the place we've chosen to start<00:07:30.409> we<00:07:31.409> can<00:07:31.590> only<00:07:31.770> support<00:07:32.250> today 00:07:32.740 --> 00:07:32.750 align:start position:0% start we can only support today 00:07:32.750 --> 00:07:37.939 align:start position:0% start we can only support today non-production<00:07:35.539> POCs<00:07:36.539> run<00:07:37.349> on<00:07:37.500> private 00:07:37.939 --> 00:07:37.949 align:start position:0% non-production POCs run on private 00:07:37.949 --> 00:07:40.429 align:start position:0% non-production POCs run on private ledgers<00:07:38.279> I<00:07:38.629> know<00:07:39.629> this<00:07:39.810> is<00:07:39.960> a<00:07:39.990> limitation 00:07:40.429 --> 00:07:40.439 align:start position:0% ledgers I know this is a limitation 00:07:40.439 --> 00:07:43.189 align:start position:0% ledgers I know this is a limitation we're<00:07:40.919> working<00:07:41.310> on<00:07:41.430> this<00:07:41.610> but<00:07:42.569> a<00:07:42.599> majority<00:07:42.960> of 00:07:43.189 --> 00:07:43.199 align:start position:0% we're working on this but a majority of 00:07:43.199 --> 00:07:45.980 align:start position:0% we're working on this but a majority of the<00:07:43.379> problems<00:07:43.800> for<00:07:44.190> us<00:07:44.599> reside<00:07:45.599> around 00:07:45.980 --> 00:07:45.990 align:start position:0% the problems for us reside around 00:07:45.990 --> 00:07:51.800 align:start position:0% the problems for us reside around content<00:07:46.379> licensing<00:07:47.039> barriers<00:07:48.529> so<00:07:49.729> when<00:07:50.810> you 00:07:51.800 --> 00:07:51.810 align:start position:0% content licensing barriers so when you 00:07:51.810 --> 00:07:54.260 align:start position:0% content licensing barriers so when you look<00:07:51.990> at<00:07:52.080> block<00:07:52.259> 1<00:07:52.440> IQ<00:07:52.610> we<00:07:53.610> asked<00:07:53.849> for<00:07:54.120> you<00:07:54.240> to 00:07:54.260 --> 00:07:54.270 align:start position:0% look at block 1 IQ we asked for you to 00:07:54.270 --> 00:07:57.079 align:start position:0% look at block 1 IQ we asked for you to think<00:07:54.599> about<00:07:55.039> creating<00:07:56.039> a<00:07:56.129> consortium<00:07:56.819> a 00:07:57.079 --> 00:07:57.089 align:start position:0% think about creating a consortium a 00:07:57.089 --> 00:07:59.510 align:start position:0% think about creating a consortium a group<00:07:57.509> of<00:07:57.750> organizations<00:07:58.560> that<00:07:59.099> are<00:07:59.310> going<00:07:59.460> to 00:07:59.510 --> 00:07:59.520 align:start position:0% group of organizations that are going to 00:07:59.520 --> 00:08:01.909 align:start position:0% group of organizations that are going to use<00:07:59.699> this<00:07:59.940> as<00:08:00.180> opposed<00:08:00.900> to<00:08:01.020> just<00:08:01.259> reaching<00:08:01.800> out 00:08:01.909 --> 00:08:01.919 align:start position:0% use this as opposed to just reaching out 00:08:01.919 --> 00:08:05.390 align:start position:0% use this as opposed to just reaching out to<00:08:02.099> try<00:08:02.279> and<00:08:02.400> kick<00:08:02.550> the<00:08:02.699> tires<00:08:03.979> and<00:08:04.979> I<00:08:05.219> should 00:08:05.390 --> 00:08:05.400 align:start position:0% to try and kick the tires and I should 00:08:05.400 --> 00:08:08.029 align:start position:0% to try and kick the tires and I should add<00:08:05.520> that<00:08:05.789> it's<00:08:06.270> free<00:08:06.680> we're<00:08:07.680> not<00:08:07.830> charging 00:08:08.029 --> 00:08:08.039 align:start position:0% add that it's free we're not charging 00:08:08.039 --> 00:08:10.939 align:start position:0% add that it's free we're not charging anything<00:08:08.639> for<00:08:08.819> this<00:08:08.909> we<00:08:09.449> want<00:08:09.659> to<00:08:09.810> enable<00:08:10.379> you 00:08:10.939 --> 00:08:10.949 align:start position:0% anything for this we want to enable you 00:08:10.949 --> 00:08:14.179 align:start position:0% anything for this we want to enable you guys<00:08:11.159> to<00:08:11.580> see<00:08:11.729> what<00:08:11.879> you<00:08:12.029> can<00:08:12.180> do<00:08:12.330> with<00:08:12.479> them<00:08:13.189> so 00:08:14.179 --> 00:08:14.189 align:start position:0% guys to see what you can do with them so 00:08:14.189 --> 00:08:15.529 align:start position:0% guys to see what you can do with them so with<00:08:14.310> that<00:08:14.370> I'm<00:08:14.550> going<00:08:14.699> to<00:08:14.729> hand<00:08:14.909> over<00:08:15.029> to<00:08:15.150> Tim 00:08:15.529 --> 00:08:15.539 align:start position:0% with that I'm going to hand over to Tim 00:08:15.539 --> 00:08:16.969 align:start position:0% with that I'm going to hand over to Tim who's<00:08:15.810> going<00:08:15.990> to<00:08:16.050> show<00:08:16.229> you<00:08:16.289> a<00:08:16.589> bit<00:08:16.800> more<00:08:16.830> about 00:08:16.969 --> 00:08:16.979 align:start position:0% who's going to show you a bit more about 00:08:16.979 --> 00:08:25.700 align:start position:0% who's going to show you a bit more about the<00:08:17.279> capabilities 00:08:25.700 --> 00:08:25.710 align:start position:0% 00:08:25.710 --> 00:08:27.900 align:start position:0% right<00:08:26.710> thank<00:08:27.370> you<00:08:27.430> Sam 00:08:27.900 --> 00:08:27.910 align:start position:0% right thank you Sam 00:08:27.910 --> 00:08:31.440 align:start position:0% right thank you Sam so<00:08:28.800> this<00:08:29.800> is<00:08:30.040> essentially<00:08:30.580> the<00:08:30.850> landing<00:08:31.240> page 00:08:31.440 --> 00:08:31.450 align:start position:0% so this is essentially the landing page 00:08:31.450 --> 00:08:34.529 align:start position:0% so this is essentially the landing page for<00:08:31.900> block<00:08:32.260> 1<00:08:32.440> IQ<00:08:32.830> at<00:08:33.160> the<00:08:33.310> moment<00:08:33.669> so<00:08:34.390> if<00:08:34.479> you 00:08:34.529 --> 00:08:34.539 align:start position:0% for block 1 IQ at the moment so if you 00:08:34.539 --> 00:08:36.990 align:start position:0% for block 1 IQ at the moment so if you visit<00:08:34.780> this<00:08:34.870> site<00:08:35.200> you<00:08:35.560> couldn't<00:08:36.000> download 00:08:36.990 --> 00:08:37.000 align:start position:0% visit this site you couldn't download 00:08:37.000 --> 00:08:40.400 align:start position:0% visit this site you couldn't download some<00:08:37.390> architectural<00:08:37.960> schemes<00:08:38.550> api's 00:08:40.400 --> 00:08:40.410 align:start position:0% some architectural schemes api's 00:08:40.410 --> 00:08:42.390 align:start position:0% some architectural schemes api's documentation<00:08:41.410> and<00:08:41.620> some<00:08:41.710> other<00:08:41.860> downloads 00:08:42.390 --> 00:08:42.400 align:start position:0% documentation and some other downloads 00:08:42.400 --> 00:08:44.370 align:start position:0% documentation and some other downloads and<00:08:42.970> actually<00:08:43.330> and<00:08:43.450> so<00:08:43.539> this<00:08:43.690> is<00:08:43.810> the<00:08:43.990> the 00:08:44.370 --> 00:08:44.380 align:start position:0% and actually and so this is the the 00:08:44.380 --> 00:08:45.960 align:start position:0% and actually and so this is the the thomson<00:08:44.680> reuters<00:08:44.800> develop<00:08:45.460> a<00:08:45.550> convenient 00:08:45.960 --> 00:08:45.970 align:start position:0% thomson reuters develop a convenient 00:08:45.970 --> 00:08:47.730 align:start position:0% thomson reuters develop a convenient community<00:08:46.420> website<00:08:46.870> and<00:08:47.350> if<00:08:47.470> you<00:08:47.560> click 00:08:47.730 --> 00:08:47.740 align:start position:0% community website and if you click 00:08:47.740 --> 00:08:49.290 align:start position:0% community website and if you click around<00:08:48.010> actually<00:08:48.490> there's<00:08:48.670> some<00:08:48.820> links<00:08:49.090> to 00:08:49.290 --> 00:08:49.300 align:start position:0% around actually there's some links to 00:08:49.300 --> 00:08:51.450 align:start position:0% around actually there's some links to some<00:08:49.450> other<00:08:49.540> api's<00:08:50.080> that<00:08:50.350> we<00:08:50.440> offer<00:08:50.590> so<00:08:51.070> last 00:08:51.450 --> 00:08:51.460 align:start position:0% some other api's that we offer so last 00:08:51.460 --> 00:08:53.460 align:start position:0% some other api's that we offer so last year<00:08:51.760> i<00:08:51.990> demonstrated<00:08:52.990> and<00:08:53.230> are<00:08:53.320> there 00:08:53.460 --> 00:08:53.470 align:start position:0% year i demonstrated and are there 00:08:53.470 --> 00:08:56.370 align:start position:0% year i demonstrated and are there offering<00:08:53.590> something<00:08:54.490> called<00:08:54.730> block<00:08:54.970> 1a<00:08:55.540> ID 00:08:56.370 --> 00:08:56.380 align:start position:0% offering something called block 1a ID 00:08:56.380 --> 00:08:58.950 align:start position:0% offering something called block 1a ID which<00:08:56.920> is<00:08:57.040> essentially<00:08:57.480> an<00:08:58.480> identity 00:08:58.950 --> 00:08:58.960 align:start position:0% which is essentially an identity 00:08:58.960 --> 00:09:00.810 align:start position:0% which is essentially an identity resolution<00:08:59.860> system<00:09:00.190> which<00:09:00.340> connects 00:09:00.810 --> 00:09:00.820 align:start position:0% resolution system which connects 00:09:00.820 --> 00:09:03.300 align:start position:0% resolution system which connects aetherium<00:09:01.570> addresses<00:09:02.080> with<00:09:02.590> OAuth<00:09:03.010> 2 00:09:03.300 --> 00:09:03.310 align:start position:0% aetherium addresses with OAuth 2 00:09:03.310 --> 00:09:04.890 align:start position:0% aetherium addresses with OAuth 2 credentials<00:09:03.700> so<00:09:04.090> if<00:09:04.180> you<00:09:04.270> click<00:09:04.450> around<00:09:04.660> you 00:09:04.890 --> 00:09:04.900 align:start position:0% credentials so if you click around you 00:09:04.900 --> 00:09:07.320 align:start position:0% credentials so if you click around you can<00:09:05.020> also<00:09:05.170> find<00:09:05.590> that<00:09:05.910> so<00:09:06.910> have<00:09:07.060> a<00:09:07.120> look<00:09:07.240> around 00:09:07.320 --> 00:09:07.330 align:start position:0% can also find that so have a look around 00:09:07.330 --> 00:09:09.150 align:start position:0% can also find that so have a look around this<00:09:07.540> website<00:09:07.960> when<00:09:08.530> you're<00:09:08.650> ready<00:09:08.800> to<00:09:08.950> sign 00:09:09.150 --> 00:09:09.160 align:start position:0% this website when you're ready to sign 00:09:09.160 --> 00:09:12.300 align:start position:0% this website when you're ready to sign up<00:09:09.340> you'll<00:09:09.550> be<00:09:09.700> faced<00:09:09.850> with<00:09:09.880> this<00:09:10.180> page<00:09:11.070> we<00:09:12.070> ask 00:09:12.300 --> 00:09:12.310 align:start position:0% up you'll be faced with this page we ask 00:09:12.310 --> 00:09:14.610 align:start position:0% up you'll be faced with this page we ask that<00:09:12.670> you<00:09:12.880> sign<00:09:13.210> up<00:09:13.390> to<00:09:13.540> certain<00:09:13.750> terms<00:09:14.320> and 00:09:14.610 --> 00:09:14.620 align:start position:0% that you sign up to certain terms and 00:09:14.620 --> 00:09:17.160 align:start position:0% that you sign up to certain terms and conditions<00:09:15.270> most<00:09:16.270> of<00:09:16.480> the<00:09:16.540> data<00:09:16.780> that<00:09:17.080> you 00:09:17.160 --> 00:09:17.170 align:start position:0% conditions most of the data that you 00:09:17.170 --> 00:09:19.740 align:start position:0% conditions most of the data that you will<00:09:17.320> have<00:09:17.560> access<00:09:17.740> to<00:09:18.160> is<00:09:18.550> proprietary<00:09:19.030> and 00:09:19.740 --> 00:09:19.750 align:start position:0% will have access to is proprietary and 00:09:19.750 --> 00:09:22.620 align:start position:0% will have access to is proprietary and in<00:09:20.350> many<00:09:20.500> cases<00:09:20.770> we<00:09:21.640> license<00:09:22.090> it<00:09:22.210> from<00:09:22.390> third 00:09:22.620 --> 00:09:22.630 align:start position:0% in many cases we license it from third 00:09:22.630 --> 00:09:25.380 align:start position:0% in many cases we license it from third parties<00:09:23.280> so<00:09:24.280> fill<00:09:24.580> in<00:09:24.700> all<00:09:24.850> the<00:09:25.000> all<00:09:25.240> the 00:09:25.380 --> 00:09:25.390 align:start position:0% parties so fill in all the all the 00:09:25.390 --> 00:09:26.910 align:start position:0% parties so fill in all the all the details<00:09:25.780> tell<00:09:26.110> us<00:09:26.200> a<00:09:26.290> little<00:09:26.380> bit<00:09:26.560> about<00:09:26.620> your 00:09:26.910 --> 00:09:26.920 align:start position:0% details tell us a little bit about your 00:09:26.920 --> 00:09:29.340 align:start position:0% details tell us a little bit about your project<00:09:27.400> and<00:09:27.550> your<00:09:27.820> your<00:09:28.210> your<00:09:28.480> plans<00:09:28.810> and 00:09:29.340 --> 00:09:29.350 align:start position:0% project and your your your plans and 00:09:29.350 --> 00:09:31.380 align:start position:0% project and your your your plans and when<00:09:29.650> you<00:09:29.740> click<00:09:29.950> Submit<00:09:30.430> I<00:09:30.580> think<00:09:30.790> Sam<00:09:31.210> will 00:09:31.380 --> 00:09:31.390 align:start position:0% when you click Submit I think Sam will 00:09:31.390 --> 00:09:33.720 align:start position:0% when you click Submit I think Sam will get<00:09:31.510> a<00:09:31.570> notification<00:09:32.460> there'll<00:09:33.460> be<00:09:33.490> some 00:09:33.720 --> 00:09:33.730 align:start position:0% get a notification there'll be some 00:09:33.730 --> 00:09:35.610 align:start position:0% get a notification there'll be some legal<00:09:34.150> documentation<00:09:34.690> that<00:09:34.930> may<00:09:35.050> need<00:09:35.380> to<00:09:35.500> be 00:09:35.610 --> 00:09:35.620 align:start position:0% legal documentation that may need to be 00:09:35.620 --> 00:09:38.010 align:start position:0% legal documentation that may need to be attended<00:09:35.890> to<00:09:36.060> if<00:09:37.060> everything<00:09:37.480> goes<00:09:37.660> through 00:09:38.010 --> 00:09:38.020 align:start position:0% attended to if everything goes through 00:09:38.020 --> 00:09:41.070 align:start position:0% attended to if everything goes through you<00:09:38.380> will<00:09:38.530> receive<00:09:39.180> access<00:09:40.180> and<00:09:40.420> they<00:09:40.810> login 00:09:41.070 --> 00:09:41.080 align:start position:0% you will receive access and they login 00:09:41.080 --> 00:09:45.690 align:start position:0% you will receive access and they login to<00:09:41.470> our<00:09:41.620> self-service<00:09:42.280> system<00:09:43.890> so<00:09:44.890> this<00:09:45.580> is 00:09:45.690 --> 00:09:45.700 align:start position:0% to our self-service system so this is 00:09:45.700 --> 00:09:46.980 align:start position:0% to our self-service system so this is our<00:09:45.850> self-service<00:09:46.210> system<00:09:46.540> it's<00:09:46.660> very<00:09:46.690> much<00:09:46.930> a 00:09:46.980 --> 00:09:46.990 align:start position:0% our self-service system it's very much a 00:09:46.990 --> 00:09:49.410 align:start position:0% our self-service system it's very much a work<00:09:47.020> in<00:09:47.320> progress<00:09:47.560> but<00:09:48.100> this<00:09:48.790> allows<00:09:49.090> us<00:09:49.300> to 00:09:49.410 --> 00:09:49.420 align:start position:0% work in progress but this allows us to 00:09:49.420 --> 00:09:50.700 align:start position:0% work in progress but this allows us to do<00:09:49.540> some<00:09:49.720> sort<00:09:49.960> of<00:09:49.990> onboarding<00:09:50.560> and 00:09:50.700 --> 00:09:50.710 align:start position:0% do some sort of onboarding and 00:09:50.710 --> 00:09:54.270 align:start position:0% do some sort of onboarding and whitelisting<00:09:51.460> of<00:09:51.690> your<00:09:52.690> contracts<00:09:53.440> so<00:09:53.890> very 00:09:54.270 --> 00:09:54.280 align:start position:0% whitelisting of your contracts so very 00:09:54.280 --> 00:09:56.790 align:start position:0% whitelisting of your contracts so very simply<00:09:54.610> just<00:09:55.000> add<00:09:55.690> a<00:09:55.750> few<00:09:55.990> users<00:09:56.260> you<00:09:56.560> can<00:09:56.650> do 00:09:56.790 --> 00:09:56.800 align:start position:0% simply just add a few users you can do 00:09:56.800 --> 00:09:59.880 align:start position:0% simply just add a few users you can do that<00:09:56.980> here<00:09:57.220> by<00:09:57.940> adding<00:09:58.180> names<00:09:58.540> emails<00:09:59.410> and 00:09:59.880 --> 00:09:59.890 align:start position:0% that here by adding names emails and 00:09:59.890 --> 00:10:01.890 align:start position:0% that here by adding names emails and setting<00:10:00.190> whether<00:10:00.580> they<00:10:00.970> are<00:10:01.120> a<00:10:01.150> user<00:10:01.480> or<00:10:01.630> an 00:10:01.890 --> 00:10:01.900 align:start position:0% setting whether they are a user or an 00:10:01.900 --> 00:10:06.210 align:start position:0% setting whether they are a user or an admin<00:10:02.230> for<00:10:03.220> example<00:10:04.320> do<00:10:05.320> that<00:10:05.530> and<00:10:05.740> then<00:10:06.100> you 00:10:06.210 --> 00:10:06.220 align:start position:0% admin for example do that and then you 00:10:06.220 --> 00:10:07.950 align:start position:0% admin for example do that and then you you<00:10:06.610> click<00:10:07.000> through<00:10:07.210> you<00:10:07.360> get<00:10:07.450> to<00:10:07.600> this<00:10:07.690> bit 00:10:07.950 --> 00:10:07.960 align:start position:0% you click through you get to this bit 00:10:07.960 --> 00:10:09.660 align:start position:0% you click through you get to this bit where<00:10:08.200> you<00:10:08.320> can<00:10:08.500> configure<00:10:08.800> your<00:10:08.950> deployment 00:10:09.660 --> 00:10:09.670 align:start position:0% where you can configure your deployment 00:10:09.670 --> 00:10:11.850 align:start position:0% where you can configure your deployment so<00:10:09.820> I<00:10:09.850> think<00:10:09.970> as<00:10:10.180> Sam<00:10:10.420> mentioned<00:10:10.660> this<00:10:11.350> service 00:10:11.850 --> 00:10:11.860 align:start position:0% so I think as Sam mentioned this service 00:10:11.860 --> 00:10:14.040 align:start position:0% so I think as Sam mentioned this service is<00:10:11.950> only<00:10:12.100> available<00:10:12.250> for<00:10:12.640> private<00:10:13.360> chains<00:10:13.840> at 00:10:14.040 --> 00:10:14.050 align:start position:0% is only available for private chains at 00:10:14.050 --> 00:10:15.630 align:start position:0% is only available for private chains at the<00:10:14.110> moment<00:10:14.470> so<00:10:14.680> put<00:10:15.160> in<00:10:15.280> your<00:10:15.400> deployment 00:10:15.630 --> 00:10:15.640 align:start position:0% the moment so put in your deployment 00:10:15.640 --> 00:10:18.330 align:start position:0% the moment so put in your deployment name<00:10:16.090> are<00:10:16.480> the<00:10:16.840> details<00:10:17.170> for<00:10:17.380> example<00:10:17.500> our<00:10:18.010> PC 00:10:18.330 --> 00:10:18.340 align:start position:0% name are the details for example our PC 00:10:18.340 --> 00:10:23.910 align:start position:0% name are the details for example our PC host<00:10:18.640> our<00:10:19.030> PC<00:10:19.330> port<00:10:19.660> a<00:10:19.990> default<00:10:20.920> account<00:10:22.920> click 00:10:23.910 --> 00:10:23.920 align:start position:0% host our PC port a default account click 00:10:23.920 --> 00:10:25.170 align:start position:0% host our PC port a default account click through<00:10:24.190> and<00:10:24.430> you<00:10:24.700> can<00:10:24.790> see<00:10:24.970> what<00:10:25.090> the 00:10:25.170 --> 00:10:25.180 align:start position:0% through and you can see what the 00:10:25.180 --> 00:10:27.810 align:start position:0% through and you can see what the configuration<00:10:25.840> looks<00:10:25.990> like<00:10:26.260> now<00:10:27.100> from<00:10:27.700> this 00:10:27.810 --> 00:10:27.820 align:start position:0% configuration looks like now from this 00:10:27.820 --> 00:10:29.850 align:start position:0% configuration looks like now from this page<00:10:28.060> it<00:10:28.780> gets<00:10:28.930> a<00:10:28.990> bit<00:10:29.110> more<00:10:29.260> interesting<00:10:29.440> if 00:10:29.850 --> 00:10:29.860 align:start position:0% page it gets a bit more interesting if 00:10:29.860 --> 00:10:31.590 align:start position:0% page it gets a bit more interesting if you<00:10:30.250> hit<00:10:30.370> the<00:10:30.430> orange<00:10:30.580> button<00:10:30.910> this<00:10:31.330> allows 00:10:31.590 --> 00:10:31.600 align:start position:0% you hit the orange button this allows 00:10:31.600 --> 00:10:33.450 align:start position:0% you hit the orange button this allows you<00:10:31.750> to<00:10:31.900> add<00:10:32.050> a<00:10:32.320> contract<00:10:32.920> to<00:10:33.040> say<00:10:33.190> you<00:10:33.250> have<00:10:33.430> a 00:10:33.450 --> 00:10:33.460 align:start position:0% you to add a contract to say you have a 00:10:33.460 --> 00:10:35.940 align:start position:0% you to add a contract to say you have a trade<00:10:33.760> contract<00:10:34.360> you<00:10:35.230> couldn't<00:10:35.560> click 00:10:35.940 --> 00:10:35.950 align:start position:0% trade contract you couldn't click 00:10:35.950 --> 00:10:37.980 align:start position:0% trade contract you couldn't click that<00:10:36.130> button<00:10:36.340> putting<00:10:36.940> the<00:10:37.030> address<00:10:37.120> of<00:10:37.930> that 00:10:37.980 --> 00:10:37.990 align:start position:0% that button putting the address of that 00:10:37.990 --> 00:10:39.960 align:start position:0% that button putting the address of that contract<00:10:38.770> and<00:10:38.950> what<00:10:39.130> essentially<00:10:39.550> happens 00:10:39.960 --> 00:10:39.970 align:start position:0% contract and what essentially happens 00:10:39.970 --> 00:10:41.790 align:start position:0% contract and what essentially happens here<00:10:40.150> is<00:10:40.390> is<00:10:40.840> that<00:10:41.020> address<00:10:41.500> is<00:10:41.650> being 00:10:41.790 --> 00:10:41.800 align:start position:0% here is is that address is being 00:10:41.800 --> 00:10:43.650 align:start position:0% here is is that address is being whitelisted<00:10:42.520> with<00:10:42.700> our<00:10:42.850> service<00:10:43.300> so<00:10:43.480> our 00:10:43.650 --> 00:10:43.660 align:start position:0% whitelisted with our service so our 00:10:43.660 --> 00:10:45.750 align:start position:0% whitelisted with our service so our Oracle<00:10:44.350> contract<00:10:44.980> will<00:10:45.160> see<00:10:45.400> that<00:10:45.550> the 00:10:45.750 --> 00:10:45.760 align:start position:0% Oracle contract will see that the 00:10:45.760 --> 00:10:48.180 align:start position:0% Oracle contract will see that the request<00:10:46.330> for<00:10:46.930> data<00:10:47.140> has<00:10:47.440> come<00:10:47.680> from<00:10:47.800> a<00:10:47.950> white 00:10:48.180 --> 00:10:48.190 align:start position:0% request for data has come from a white 00:10:48.190 --> 00:10:51.240 align:start position:0% request for data has come from a white listed<00:10:48.610> contract<00:10:49.150> and<00:10:49.390> as<00:10:50.080> long<00:10:50.230> as<00:10:50.260> it's<00:10:51.160> on 00:10:51.240 --> 00:10:51.250 align:start position:0% listed contract and as long as it's on 00:10:51.250 --> 00:10:52.920 align:start position:0% listed contract and as long as it's on that<00:10:51.400> white<00:10:51.580> list<00:10:51.820> we<00:10:52.000> will<00:10:52.120> be<00:10:52.270> able<00:10:52.390> to<00:10:52.660> send 00:10:52.920 --> 00:10:52.930 align:start position:0% that white list we will be able to send 00:10:52.930 --> 00:10:54.870 align:start position:0% that white list we will be able to send data<00:10:52.990> back<00:10:53.860> to<00:10:53.890> you<00:10:54.130> you<00:10:54.250> can<00:10:54.310> also<00:10:54.490> click<00:10:54.850> on 00:10:54.870 --> 00:10:54.880 align:start position:0% data back to you you can also click on 00:10:54.880 --> 00:10:56.700 align:start position:0% data back to you you can also click on the<00:10:55.240> contracts<00:10:55.660> button<00:10:55.990> and<00:10:56.140> you<00:10:56.230> can<00:10:56.380> see<00:10:56.590> the 00:10:56.700 --> 00:10:56.710 align:start position:0% the contracts button and you can see the 00:10:56.710 --> 00:10:58.200 align:start position:0% the contracts button and you can see the list<00:10:56.890> of<00:10:57.040> the<00:10:57.160> contracts<00:10:57.550> you've<00:10:57.760> added<00:10:57.910> and 00:10:58.200 --> 00:10:58.210 align:start position:0% list of the contracts you've added and 00:10:58.210 --> 00:11:01.140 align:start position:0% list of the contracts you've added and you<00:10:58.240> can<00:10:58.840> edit<00:10:59.050> that<00:10:59.580> once<00:11:00.580> you've<00:11:00.700> set<00:11:00.910> a<00:11:00.940> lot 00:11:01.140 --> 00:11:01.150 align:start position:0% you can edit that once you've set a lot 00:11:01.150 --> 00:11:02.970 align:start position:0% you can edit that once you've set a lot set<00:11:01.540> that<00:11:01.660> up<00:11:01.690> the<00:11:01.900> Oracle<00:11:02.260> contract<00:11:02.680> address 00:11:02.970 --> 00:11:02.980 align:start position:0% set that up the Oracle contract address 00:11:02.980 --> 00:11:04.620 align:start position:0% set that up the Oracle contract address will<00:11:03.190> also<00:11:03.430> be<00:11:03.610> visible<00:11:03.940> so<00:11:04.270> you<00:11:04.300> will<00:11:04.480> know 00:11:04.620 --> 00:11:04.630 align:start position:0% will also be visible so you will know 00:11:04.630 --> 00:11:06.710 align:start position:0% will also be visible so you will know the<00:11:04.810> address<00:11:05.080> to<00:11:05.590> hit<00:11:05.740> with<00:11:05.920> your<00:11:06.040> requests 00:11:06.710 --> 00:11:06.720 align:start position:0% the address to hit with your requests 00:11:06.720 --> 00:11:09.180 align:start position:0% the address to hit with your requests there's<00:11:07.720> also<00:11:07.870> a<00:11:07.990> little<00:11:08.140> test<00:11:08.470> interface<00:11:08.860> so 00:11:09.180 --> 00:11:09.190 align:start position:0% there's also a little test interface so 00:11:09.190 --> 00:11:11.520 align:start position:0% there's also a little test interface so you<00:11:09.280> can<00:11:09.430> test<00:11:10.320> requesting<00:11:11.320> and<00:11:11.500> receiving 00:11:11.520 --> 00:11:11.530 align:start position:0% you can test requesting and receiving 00:11:11.530 --> 00:11:14.460 align:start position:0% you can test requesting and receiving data<00:11:12.010> so<00:11:12.520> we've<00:11:12.670> got<00:11:12.820> a<00:11:12.850> very<00:11:13.510> small<00:11:13.780> sample<00:11:14.380> of 00:11:14.460 --> 00:11:14.470 align:start position:0% data so we've got a very small sample of 00:11:14.470 --> 00:11:16.620 align:start position:0% data so we've got a very small sample of the<00:11:14.530> of<00:11:15.160> the<00:11:15.430> different<00:11:16.120> requests<00:11:16.450> you<00:11:16.570> can 00:11:16.620 --> 00:11:16.630 align:start position:0% the of the different requests you can 00:11:16.630 --> 00:11:18.590 align:start position:0% the of the different requests you can make<00:11:16.870> so<00:11:17.020> end-of-day<00:11:17.440> prices<00:11:17.950> intraday 00:11:18.590 --> 00:11:18.600 align:start position:0% make so end-of-day prices intraday 00:11:18.600 --> 00:11:22.020 align:start position:0% make so end-of-day prices intraday interest<00:11:19.600> rates<00:11:19.900> cryptocurrency<00:11:20.860> rates<00:11:21.370> so 00:11:22.020 --> 00:11:22.030 align:start position:0% interest rates cryptocurrency rates so 00:11:22.030 --> 00:11:24.000 align:start position:0% interest rates cryptocurrency rates so select<00:11:22.390> your<00:11:22.480> your<00:11:23.020> symbol<00:11:23.530> from<00:11:23.680> the<00:11:23.770> Joc 00:11:24.000 --> 00:11:24.010 align:start position:0% select your your symbol from the Joc 00:11:24.010 --> 00:11:26.580 align:start position:0% select your your symbol from the Joc from<00:11:24.250> the<00:11:24.340> drop<00:11:24.520> down<00:11:24.840> hit<00:11:25.840> submit<00:11:26.260> and<00:11:26.440> a 00:11:26.580 --> 00:11:26.590 align:start position:0% from the drop down hit submit and a 00:11:26.590 --> 00:11:28.440 align:start position:0% from the drop down hit submit and a block<00:11:26.830> later<00:11:27.040> that<00:11:27.490> the<00:11:27.610> data<00:11:27.850> will<00:11:28.060> come<00:11:28.090> back 00:11:28.440 --> 00:11:28.450 align:start position:0% block later that the data will come back 00:11:28.450 --> 00:11:30.300 align:start position:0% block later that the data will come back and<00:11:28.750> here<00:11:29.140> it's<00:11:29.290> simply<00:11:29.590> represented<00:11:30.160> as<00:11:30.280> a 00:11:30.300 --> 00:11:30.310 align:start position:0% and here it's simply represented as a 00:11:30.310 --> 00:11:32.610 align:start position:0% and here it's simply represented as a JSON<00:11:30.760> object<00:11:30.900> if<00:11:31.900> you<00:11:32.020> go<00:11:32.170> and<00:11:32.290> look<00:11:32.380> at<00:11:32.500> our 00:11:32.610 --> 00:11:32.620 align:start position:0% JSON object if you go and look at our 00:11:32.620 --> 00:11:34.590 align:start position:0% JSON object if you go and look at our API<00:11:32.980> you<00:11:33.160> can<00:11:33.610> you<00:11:33.910> can<00:11:34.060> be<00:11:34.180> quite<00:11:34.390> selective 00:11:34.590 --> 00:11:34.600 align:start position:0% API you can you can be quite selective 00:11:34.600 --> 00:11:37.500 align:start position:0% API you can you can be quite selective with<00:11:35.110> with<00:11:35.980> exactly<00:11:36.490> what<00:11:36.670> you<00:11:36.790> request<00:11:37.180> and 00:11:37.500 --> 00:11:37.510 align:start position:0% with with exactly what you request and 00:11:37.510 --> 00:11:39.600 align:start position:0% with with exactly what you request and exactly<00:11:37.870> what<00:11:38.110> is<00:11:38.230> returned<00:11:38.710> and<00:11:39.010> you<00:11:39.430> can 00:11:39.600 --> 00:11:39.610 align:start position:0% exactly what is returned and you can 00:11:39.610 --> 00:11:41.970 align:start position:0% exactly what is returned and you can tailor<00:11:39.850> tailor<00:11:40.300> that<00:11:40.570> to<00:11:40.630> the<00:11:41.410> needs<00:11:41.650> of<00:11:41.860> your 00:11:41.970 --> 00:11:41.980 align:start position:0% tailor tailor that to the needs of your 00:11:41.980 --> 00:11:44.820 align:start position:0% tailor tailor that to the needs of your smart<00:11:42.460> contract<00:11:43.200> so<00:11:44.200> that's<00:11:44.380> pretty<00:11:44.530> much<00:11:44.680> the 00:11:44.820 --> 00:11:44.830 align:start position:0% smart contract so that's pretty much the 00:11:44.830 --> 00:11:46.950 align:start position:0% smart contract so that's pretty much the self-serve<00:11:45.220> it's<00:11:45.430> quite<00:11:45.580> straightforward<00:11:45.960> on 00:11:46.950 --> 00:11:46.960 align:start position:0% self-serve it's quite straightforward on 00:11:46.960 --> 00:11:49.740 align:start position:0% self-serve it's quite straightforward on our<00:11:47.230> roadmap<00:11:47.470> is<00:11:47.860> to<00:11:48.100> provide<00:11:48.610> an<00:11:48.790> API<00:11:49.420> which 00:11:49.740 --> 00:11:49.750 align:start position:0% our roadmap is to provide an API which 00:11:49.750 --> 00:11:51.720 align:start position:0% our roadmap is to provide an API which will<00:11:50.020> expose<00:11:50.320> most<00:11:50.740> of<00:11:50.920> this<00:11:51.010> functionality 00:11:51.720 --> 00:11:51.730 align:start position:0% will expose most of this functionality 00:11:51.730 --> 00:11:55.020 align:start position:0% will expose most of this functionality such<00:11:52.360> the<00:11:52.570> registering<00:11:53.050> smart<00:11:53.440> contracts<00:11:54.030> and 00:11:55.020 --> 00:11:55.030 align:start position:0% such the registering smart contracts and 00:11:55.030 --> 00:12:00.620 align:start position:0% such the registering smart contracts and with<00:11:55.870> our<00:11:56.020> will<00:11:56.710> be<00:11:56.800> done<00:11:56.830> quickly<00:11:57.640> off<00:11:58.030> chain 00:12:00.620 --> 00:12:00.630 align:start position:0% 00:12:00.630 --> 00:12:02.820 align:start position:0% so<00:12:01.630> just<00:12:01.840> to<00:12:01.930> make<00:12:02.050> this<00:12:02.290> a<00:12:02.350> little<00:12:02.500> bit<00:12:02.710> more 00:12:02.820 --> 00:12:02.830 align:start position:0% so just to make this a little bit more 00:12:02.830 --> 00:12:04.850 align:start position:0% so just to make this a little bit more tangible<00:12:03.040> a<00:12:03.400> couple<00:12:03.640> of<00:12:03.700> examples<00:12:04.270> of<00:12:04.480> some 00:12:04.850 --> 00:12:04.860 align:start position:0% tangible a couple of examples of some 00:12:04.860 --> 00:12:07.950 align:start position:0% tangible a couple of examples of some some<00:12:05.860> assets<00:12:06.430> that<00:12:06.580> we've<00:12:06.700> modeled<00:12:07.180> to 00:12:07.950 --> 00:12:07.960 align:start position:0% some assets that we've modeled to 00:12:07.960 --> 00:12:10.170 align:start position:0% some assets that we've modeled to demonstrate<00:12:08.530> interactivity<00:12:09.370> with<00:12:10.030> our 00:12:10.170 --> 00:12:10.180 align:start position:0% demonstrate interactivity with our 00:12:10.180 --> 00:12:12.660 align:start position:0% demonstrate interactivity with our Oracle<00:12:10.480> so<00:12:11.110> this<00:12:11.260> is<00:12:11.410> this<00:12:11.650> is<00:12:11.830> an<00:12:11.920> equity<00:12:12.280> swap 00:12:12.660 --> 00:12:12.670 align:start position:0% Oracle so this is this is an equity swap 00:12:12.670 --> 00:12:17.040 align:start position:0% Oracle so this is this is an equity swap contract<00:12:13.950> it<00:12:14.950> essentially<00:12:15.340> has<00:12:15.430> two<00:12:15.670> legs<00:12:16.050> an 00:12:17.040 --> 00:12:17.050 align:start position:0% contract it essentially has two legs an 00:12:17.050 --> 00:12:19.170 align:start position:0% contract it essentially has two legs an interest<00:12:17.470> rate<00:12:17.650> leg<00:12:17.920> in<00:12:18.100> an<00:12:18.190> equity<00:12:18.580> leg<00:12:18.820> so 00:12:19.170 --> 00:12:19.180 align:start position:0% interest rate leg in an equity leg so 00:12:19.180 --> 00:12:21.510 align:start position:0% interest rate leg in an equity leg so there<00:12:19.360> are<00:12:19.450> two<00:12:19.600> sort<00:12:19.900> of<00:12:19.930> streams<00:12:20.920> of<00:12:21.160> payment 00:12:21.510 --> 00:12:21.520 align:start position:0% there are two sort of streams of payment 00:12:21.520 --> 00:12:23.100 align:start position:0% there are two sort of streams of payment here<00:12:21.700> one<00:12:21.940> is<00:12:22.060> based<00:12:22.300> on<00:12:22.480> the<00:12:22.570> performance<00:12:23.020> of 00:12:23.100 --> 00:12:23.110 align:start position:0% here one is based on the performance of 00:12:23.110 --> 00:12:26.250 align:start position:0% here one is based on the performance of an<00:12:23.230> equity<00:12:23.590> so<00:12:23.830> here<00:12:24.040> the<00:12:24.760> S&P<00:12:25.030> 500<00:12:25.750> or<00:12:25.930> in 00:12:26.250 --> 00:12:26.260 align:start position:0% an equity so here the S&P 500 or in 00:12:26.260 --> 00:12:28.500 align:start position:0% an equity so here the S&P 500 or in equity<00:12:26.410> index<00:12:26.980> as<00:12:27.130> the<00:12:27.220> case<00:12:27.400> may<00:12:27.580> be<00:12:27.610> and<00:12:28.030> on 00:12:28.500 --> 00:12:28.510 align:start position:0% equity index as the case may be and on 00:12:28.510 --> 00:12:30.690 align:start position:0% equity index as the case may be and on the<00:12:28.600> other<00:12:28.720> leg<00:12:28.990> it's<00:12:29.260> typically<00:12:29.590> based<00:12:30.070> on<00:12:30.460> an 00:12:30.690 --> 00:12:30.700 align:start position:0% the other leg it's typically based on an 00:12:30.700 --> 00:12:32.100 align:start position:0% the other leg it's typically based on an interest<00:12:31.030> rate<00:12:31.270> which<00:12:31.510> in<00:12:31.630> this<00:12:31.720> case<00:12:31.900> is 00:12:32.100 --> 00:12:32.110 align:start position:0% interest rate which in this case is 00:12:32.110 --> 00:12:34.880 align:start position:0% interest rate which in this case is LIBOR<00:12:32.760> so<00:12:33.760> when<00:12:33.910> the<00:12:34.030> contract<00:12:34.420> is 00:12:34.880 --> 00:12:34.890 align:start position:0% LIBOR so when the contract is 00:12:34.890 --> 00:12:38.310 align:start position:0% LIBOR so when the contract is instantiated<00:12:35.890> by<00:12:36.370> either<00:12:37.120> party<00:12:37.420> a<00:12:37.660> or<00:12:37.780> party 00:12:38.310 --> 00:12:38.320 align:start position:0% instantiated by either party a or party 00:12:38.320 --> 00:12:40.170 align:start position:0% instantiated by either party a or party B<00:12:38.500> at<00:12:39.040> the<00:12:39.130> moment<00:12:39.430> the<00:12:39.490> request<00:12:39.850> to<00:12:40.090> the 00:12:40.170 --> 00:12:40.180 align:start position:0% B at the moment the request to the 00:12:40.180 --> 00:12:42.600 align:start position:0% B at the moment the request to the oracle<00:12:40.600> was<00:12:40.660> made<00:12:40.870> on<00:12:41.110> chain<00:12:41.590> but<00:12:42.430> we're 00:12:42.600 --> 00:12:42.610 align:start position:0% oracle was made on chain but we're 00:12:42.610 --> 00:12:44.640 align:start position:0% oracle was made on chain but we're adapting<00:12:43.150> our<00:12:43.300> functionality<00:12:44.230> so<00:12:44.350> that<00:12:44.500> could 00:12:44.640 --> 00:12:44.650 align:start position:0% adapting our functionality so that could 00:12:44.650 --> 00:12:46.590 align:start position:0% adapting our functionality so that could be<00:12:44.740> made<00:12:44.920> by<00:12:45.130> a<00:12:45.160> signed<00:12:45.520> message<00:12:45.940> off<00:12:46.150> chain 00:12:46.590 --> 00:12:46.600 align:start position:0% be made by a signed message off chain 00:12:46.600 --> 00:12:48.720 align:start position:0% be made by a signed message off chain but<00:12:47.200> at<00:12:47.350> the<00:12:47.440> point<00:12:47.680> of<00:12:47.800> instantiation<00:12:48.430> a 00:12:48.720 --> 00:12:48.730 align:start position:0% but at the point of instantiation a 00:12:48.730 --> 00:12:49.269 align:start position:0% but at the point of instantiation a request<00:12:49.060> is 00:12:49.269 --> 00:12:49.279 align:start position:0% request is 00:12:49.279 --> 00:12:51.280 align:start position:0% request is sent<00:12:49.490> to<00:12:49.790> our<00:12:49.939> or<00:12:50.180> record<00:12:50.509> in<00:12:50.720> this<00:12:50.810> case<00:12:50.870> it 00:12:51.280 --> 00:12:51.290 align:start position:0% sent to our or record in this case it 00:12:51.290 --> 00:12:55.329 align:start position:0% sent to our or record in this case it will<00:12:51.379> request<00:12:51.800> two<00:12:52.759> symbols<00:12:53.209> the<00:12:54.110> sp500<00:12:54.740> SPX 00:12:55.329 --> 00:12:55.339 align:start position:0% will request two symbols the sp500 SPX 00:12:55.339 --> 00:12:57.759 align:start position:0% will request two symbols the sp500 SPX and<00:12:55.550> also<00:12:55.790> LIBOR<00:12:56.360> and<00:12:56.689> you<00:12:56.959> can<00:12:57.139> configure<00:12:57.439> how 00:12:57.759 --> 00:12:57.769 align:start position:0% and also LIBOR and you can configure how 00:12:57.769 --> 00:13:00.160 align:start position:0% and also LIBOR and you can configure how regularly<00:12:58.339> you<00:12:58.879> want<00:12:59.089> the<00:12:59.269> the<00:12:59.509> response<00:12:59.930> data 00:13:00.160 --> 00:13:00.170 align:start position:0% regularly you want the the response data 00:13:00.170 --> 00:13:02.079 align:start position:0% regularly you want the the response data to<00:13:00.379> come<00:13:00.529> back<00:13:00.769> it<00:13:00.980> could<00:13:01.129> be<00:13:01.189> an<00:13:01.550> end-of-day 00:13:02.079 --> 00:13:02.089 align:start position:0% to come back it could be an end-of-day 00:13:02.089 --> 00:13:04.600 align:start position:0% to come back it could be an end-of-day or<00:13:02.600> it<00:13:02.720> could<00:13:02.899> be<00:13:03.019> a<00:13:03.129> single<00:13:04.129> point<00:13:04.370> in<00:13:04.519> the 00:13:04.600 --> 00:13:04.610 align:start position:0% or it could be a single point in the 00:13:04.610 --> 00:13:07.449 align:start position:0% or it could be a single point in the future<00:13:05.170> so<00:13:06.170> when<00:13:06.319> this<00:13:06.439> data<00:13:06.680> is<00:13:06.860> delivered<00:13:07.249> by 00:13:07.449 --> 00:13:07.459 align:start position:0% future so when this data is delivered by 00:13:07.459 --> 00:13:10.420 align:start position:0% future so when this data is delivered by our<00:13:07.490> Oracle<00:13:08.209> the<00:13:08.480> two<00:13:08.899> values<00:13:09.589> the<00:13:09.800> SPX<00:13:10.160> and 00:13:10.420 --> 00:13:10.430 align:start position:0% our Oracle the two values the SPX and 00:13:10.430 --> 00:13:13.360 align:start position:0% our Oracle the two values the SPX and LIBOR<00:13:10.819> are<00:13:11.120> updated<00:13:11.870> and<00:13:12.050> these<00:13:12.829> values<00:13:13.220> are 00:13:13.360 --> 00:13:13.370 align:start position:0% LIBOR are updated and these values are 00:13:13.370 --> 00:13:15.489 align:start position:0% LIBOR are updated and these values are used<00:13:13.579> to<00:13:13.730> calculate<00:13:13.819> the<00:13:14.329> value<00:13:15.139> of<00:13:15.170> the<00:13:15.319> two 00:13:15.489 --> 00:13:15.499 align:start position:0% used to calculate the value of the two 00:13:15.499 --> 00:13:18.819 align:start position:0% used to calculate the value of the two legs<00:13:15.709> so<00:13:16.069> with<00:13:16.550> the<00:13:16.699> equity<00:13:17.029> leg<00:13:17.470> this<00:13:18.470> will<00:13:18.709> be 00:13:18.819 --> 00:13:18.829 align:start position:0% legs so with the equity leg this will be 00:13:18.829 --> 00:13:21.639 align:start position:0% legs so with the equity leg this will be based<00:13:19.040> on<00:13:19.370> the<00:13:20.089> notional<00:13:20.629> which<00:13:20.899> is<00:13:21.079> a<00:13:21.110> trade 00:13:21.639 --> 00:13:21.649 align:start position:0% based on the notional which is a trade 00:13:21.649 --> 00:13:23.290 align:start position:0% based on the notional which is a trade parameter<00:13:22.160> you<00:13:22.279> can<00:13:22.309> see<00:13:22.579> in<00:13:22.699> the<00:13:22.790> bottom<00:13:22.939> left 00:13:23.290 --> 00:13:23.300 align:start position:0% parameter you can see in the bottom left 00:13:23.300 --> 00:13:25.150 align:start position:0% parameter you can see in the bottom left hand<00:13:23.360> corner<00:13:23.720> and<00:13:23.990> it<00:13:24.439> will<00:13:24.529> be<00:13:24.649> the<00:13:24.740> notional 00:13:25.150 --> 00:13:25.160 align:start position:0% hand corner and it will be the notional 00:13:25.160 --> 00:13:27.429 align:start position:0% hand corner and it will be the notional multiplied<00:13:25.939> by<00:13:26.209> the<00:13:26.269> percentage<00:13:26.540> change<00:13:27.139> in 00:13:27.429 --> 00:13:27.439 align:start position:0% multiplied by the percentage change in 00:13:27.439 --> 00:13:30.280 align:start position:0% multiplied by the percentage change in the<00:13:27.470> S&P<00:13:27.829> 500<00:13:28.480> for<00:13:29.480> the<00:13:29.540> interest<00:13:29.839> rate<00:13:30.050> leg 00:13:30.280 --> 00:13:30.290 align:start position:0% the S&P 500 for the interest rate leg 00:13:30.290 --> 00:13:33.670 align:start position:0% the S&P 500 for the interest rate leg that<00:13:30.889> is<00:13:31.009> essentially<00:13:31.579> LIBOR<00:13:32.480> plus<00:13:32.779> basis 00:13:33.670 --> 00:13:33.680 align:start position:0% that is essentially LIBOR plus basis 00:13:33.680 --> 00:13:35.019 align:start position:0% that is essentially LIBOR plus basis points<00:13:34.040> which<00:13:34.160> is<00:13:34.279> another<00:13:34.519> one<00:13:34.730> of<00:13:34.790> these 00:13:35.019 --> 00:13:35.029 align:start position:0% points which is another one of these 00:13:35.029 --> 00:13:38.829 align:start position:0% points which is another one of these trade<00:13:35.720> parameters<00:13:36.230> and<00:13:37.160> the<00:13:38.059> ten<00:13:38.300> or<00:13:38.480> here<00:13:38.689> is 00:13:38.829 --> 00:13:38.839 align:start position:0% trade parameters and the ten or here is 00:13:38.839 --> 00:13:41.110 align:start position:0% trade parameters and the ten or here is essentially<00:13:39.170> the<00:13:39.350> duration<00:13:39.949> of<00:13:40.009> the<00:13:40.129> trade<00:13:40.399> so 00:13:41.110 --> 00:13:41.120 align:start position:0% essentially the duration of the trade so 00:13:41.120 --> 00:13:43.869 align:start position:0% essentially the duration of the trade so using<00:13:41.839> the<00:13:41.959> values<00:13:42.559> from<00:13:42.920> our<00:13:43.129> Oracle<00:13:43.490> the 00:13:43.869 --> 00:13:43.879 align:start position:0% using the values from our Oracle the 00:13:43.879 --> 00:13:45.579 align:start position:0% using the values from our Oracle the value<00:13:44.569> of<00:13:44.660> these<00:13:44.809> two<00:13:45.050> legs<00:13:45.230> can<00:13:45.470> be 00:13:45.579 --> 00:13:45.589 align:start position:0% value of these two legs can be 00:13:45.589 --> 00:13:47.110 align:start position:0% value of these two legs can be calculated<00:13:46.100> and<00:13:46.399> here<00:13:46.579> we<00:13:46.730> have<00:13:46.850> a<00:13:46.879> very 00:13:47.110 --> 00:13:47.120 align:start position:0% calculated and here we have a very 00:13:47.120 --> 00:13:50.980 align:start position:0% calculated and here we have a very simple<00:13:47.680> ERC<00:13:48.680> 20<00:13:49.069> settlement<00:13:50.029> so<00:13:50.329> you<00:13:50.660> can<00:13:50.809> see 00:13:50.980 --> 00:13:50.990 align:start position:0% simple ERC 20 settlement so you can see 00:13:50.990 --> 00:13:52.780 align:start position:0% simple ERC 20 settlement so you can see how<00:13:51.170> the<00:13:51.230> prices<00:13:51.949> that<00:13:52.069> arrived<00:13:52.339> from<00:13:52.610> our 00:13:52.780 --> 00:13:52.790 align:start position:0% how the prices that arrived from our 00:13:52.790 --> 00:13:55.480 align:start position:0% how the prices that arrived from our Oracle<00:13:53.170> further<00:13:54.170> down<00:13:54.410> the<00:13:54.529> line<00:13:54.680> drive<00:13:55.160> the 00:13:55.480 --> 00:13:55.490 align:start position:0% Oracle further down the line drive the 00:13:55.490 --> 00:13:57.400 align:start position:0% Oracle further down the line drive the movement<00:13:55.670> of<00:13:56.120> these<00:13:56.329> tokens<00:13:56.629> to<00:13:57.079> set<00:13:57.259> all 00:13:57.400 --> 00:13:57.410 align:start position:0% movement of these tokens to set all 00:13:57.410 --> 00:14:01.240 align:start position:0% movement of these tokens to set all these<00:13:57.589> two<00:13:57.829> legs<00:13:59.769> slightly<00:14:00.769> more<00:14:00.920> elaborate 00:14:01.240 --> 00:14:01.250 align:start position:0% these two legs slightly more elaborate 00:14:01.250 --> 00:14:04.449 align:start position:0% these two legs slightly more elaborate one<00:14:01.430> here<00:14:01.610> so<00:14:01.790> this<00:14:01.910> is<00:14:02.059> a<00:14:02.089> a<00:14:02.870> RC<00:14:03.170> 20<00:14:03.620> token 00:14:04.449 --> 00:14:04.459 align:start position:0% one here so this is a a RC 20 token 00:14:04.459 --> 00:14:07.210 align:start position:0% one here so this is a a RC 20 token basket<00:14:05.019> so<00:14:06.019> this<00:14:06.199> might<00:14:06.410> be<00:14:06.439> an<00:14:06.860> actively 00:14:07.210 --> 00:14:07.220 align:start position:0% basket so this might be an actively 00:14:07.220 --> 00:14:10.960 align:start position:0% basket so this might be an actively managed<00:14:08.050> contract<00:14:09.050> or<00:14:09.170> basket<00:14:09.860> of<00:14:09.980> ERC<00:14:10.610> 20 00:14:10.960 --> 00:14:10.970 align:start position:0% managed contract or basket of ERC 20 00:14:10.970 --> 00:14:12.400 align:start position:0% managed contract or basket of ERC 20 tokens<00:14:11.389> so<00:14:11.569> the<00:14:11.750> bottom<00:14:11.990> left<00:14:12.170> you<00:14:12.290> have<00:14:12.379> a 00:14:12.400 --> 00:14:12.410 align:start position:0% tokens so the bottom left you have a 00:14:12.410 --> 00:14:14.710 align:start position:0% tokens so the bottom left you have a manager<00:14:12.920> the<00:14:13.610> manager<00:14:13.730> will<00:14:14.120> assign<00:14:14.389> weights 00:14:14.710 --> 00:14:14.720 align:start position:0% manager the manager will assign weights 00:14:14.720 --> 00:14:18.129 align:start position:0% manager the manager will assign weights to<00:14:15.230> the<00:14:15.319> tokens<00:14:15.740> held<00:14:16.069> within<00:14:16.370> the<00:14:16.519> basket<00:14:17.139> at 00:14:18.129 --> 00:14:18.139 align:start position:0% to the tokens held within the basket at 00:14:18.139 --> 00:14:19.480 align:start position:0% to the tokens held within the basket at the<00:14:18.230> point<00:14:18.529> of<00:14:18.680> assigning<00:14:19.009> these<00:14:19.189> weights 00:14:19.480 --> 00:14:19.490 align:start position:0% the point of assigning these weights 00:14:19.490 --> 00:14:22.030 align:start position:0% the point of assigning these weights this<00:14:19.910> request<00:14:20.329> is<00:14:20.509> sent<00:14:20.689> on<00:14:21.199> chain<00:14:21.769> or<00:14:21.920> off 00:14:22.030 --> 00:14:22.040 align:start position:0% this request is sent on chain or off 00:14:22.040 --> 00:14:24.639 align:start position:0% this request is sent on chain or off chain<00:14:22.339> to<00:14:23.029> our<00:14:23.329> Oracle<00:14:23.750> saying<00:14:24.230> essentially 00:14:24.639 --> 00:14:24.649 align:start position:0% chain to our Oracle saying essentially 00:14:24.649 --> 00:14:27.100 align:start position:0% chain to our Oracle saying essentially this<00:14:24.889> this<00:14:25.250> contract<00:14:25.730> requests<00:14:26.240> the<00:14:26.629> price 00:14:27.100 --> 00:14:27.110 align:start position:0% this this contract requests the price 00:14:27.110 --> 00:14:29.829 align:start position:0% this this contract requests the price the<00:14:27.319> values<00:14:27.709> of<00:14:27.980> the<00:14:28.279> specific<00:14:28.819> tokens<00:14:29.240> so 00:14:29.829 --> 00:14:29.839 align:start position:0% the values of the specific tokens so 00:14:29.839 --> 00:14:31.600 align:start position:0% the values of the specific tokens so these<00:14:30.019> tokens<00:14:30.290> and<00:14:30.709> other<00:14:31.069> cryptocurrency 00:14:31.600 --> 00:14:31.610 align:start position:0% these tokens and other cryptocurrency 00:14:31.610 --> 00:14:33.639 align:start position:0% these tokens and other cryptocurrency values<00:14:32.209> come<00:14:32.449> from<00:14:32.480> crypto<00:14:32.959> compare<00:14:33.319> us<00:14:33.439> our 00:14:33.639 --> 00:14:33.649 align:start position:0% values come from crypto compare us our 00:14:33.649 --> 00:14:37.329 align:start position:0% values come from crypto compare us our mentioned<00:14:34.129> when<00:14:34.819> those<00:14:35.059> values<00:14:35.449> arrive<00:14:36.339> they 00:14:37.329 --> 00:14:37.339 align:start position:0% mentioned when those values arrive they 00:14:37.339 --> 00:14:39.970 align:start position:0% mentioned when those values arrive they are<00:14:37.790> those<00:14:38.540> those<00:14:38.929> values<00:14:39.290> are<00:14:39.410> used<00:14:39.589> in 00:14:39.970 --> 00:14:39.980 align:start position:0% are those those values are used in 00:14:39.980 --> 00:14:41.679 align:start position:0% are those those values are used in combination<00:14:40.670> with<00:14:40.790> the<00:14:40.879> allocations<00:14:41.480> that 00:14:41.679 --> 00:14:41.689 align:start position:0% combination with the allocations that 00:14:41.689 --> 00:14:43.360 align:start position:0% combination with the allocations that are<00:14:41.779> currently<00:14:42.050> held<00:14:42.290> to<00:14:42.949> call<00:14:43.220> this 00:14:43.360 --> 00:14:43.370 align:start position:0% are currently held to call this 00:14:43.370 --> 00:14:45.220 align:start position:0% are currently held to call this evaluation<00:14:44.089> function<00:14:44.629> and<00:14:44.809> using<00:14:45.139> this 00:14:45.220 --> 00:14:45.230 align:start position:0% evaluation function and using this 00:14:45.230 --> 00:14:47.259 align:start position:0% evaluation function and using this valuation<00:14:45.529> function<00:14:46.189> we<00:14:46.309> can<00:14:46.490> we<00:14:46.759> can<00:14:46.939> come<00:14:47.149> up 00:14:47.259 --> 00:14:47.269 align:start position:0% valuation function we can we can come up 00:14:47.269 --> 00:14:49.569 align:start position:0% valuation function we can we can come up with<00:14:47.420> a<00:14:47.449> we<00:14:47.839> can<00:14:47.990> calculate<00:14:48.410> a<00:14:48.439> value<00:14:48.740> for<00:14:49.519> the 00:14:49.569 --> 00:14:49.579 align:start position:0% with a we can calculate a value for the 00:14:49.579 --> 00:14:52.749 align:start position:0% with a we can calculate a value for the overall<00:14:50.170> token<00:14:51.170> basket<00:14:51.709> depending<00:14:52.639> on 00:14:52.749 --> 00:14:52.759 align:start position:0% overall token basket depending on 00:14:52.759 --> 00:14:54.759 align:start position:0% overall token basket depending on performance<00:14:53.209> whether<00:14:53.420> things<00:14:53.839> go<00:14:54.259> well<00:14:54.470> or<00:14:54.620> go 00:14:54.759 --> 00:14:54.769 align:start position:0% performance whether things go well or go 00:14:54.769 --> 00:14:57.129 align:start position:0% performance whether things go well or go badly<00:14:55.329> investors<00:14:56.329> who<00:14:56.449> are<00:14:56.480> these<00:14:56.660> parties 00:14:57.129 --> 00:14:57.139 align:start position:0% badly investors who are these parties 00:14:57.139 --> 00:14:59.319 align:start position:0% badly investors who are these parties ABC<00:14:57.829> down<00:14:58.189> at<00:14:58.309> the<00:14:58.370> bottom<00:14:58.519> can<00:14:58.790> either<00:14:58.910> invest 00:14:59.319 --> 00:14:59.329 align:start position:0% ABC down at the bottom can either invest 00:14:59.329 --> 00:15:02.630 align:start position:0% ABC down at the bottom can either invest or<00:14:59.600> withdraw<00:14:59.959> ether<00:15:00.800> and<00:15:01.009> depending<00:15:01.850> on<00:15:01.970> on 00:15:02.630 --> 00:15:02.640 align:start position:0% or withdraw ether and depending on on 00:15:02.640 --> 00:15:05.150 align:start position:0% or withdraw ether and depending on on that<00:15:02.730> investment<00:15:03.470> using<00:15:04.470> a<00:15:04.560> hook<00:15:04.740> out<00:15:04.920> to<00:15:05.100> your 00:15:05.150 --> 00:15:05.160 align:start position:0% that investment using a hook out to your 00:15:05.160 --> 00:15:09.370 align:start position:0% that investment using a hook out to your favorite<00:15:05.930> decentralized<00:15:06.930> exchange<00:15:07.080> protocol 00:15:09.370 --> 00:15:09.380 align:start position:0% favorite decentralized exchange protocol 00:15:09.380 --> 00:15:11.450 align:start position:0% favorite decentralized exchange protocol tokens<00:15:10.380> can<00:15:10.560> either<00:15:10.680> be<00:15:10.830> purchased<00:15:11.280> or<00:15:11.430> sold 00:15:11.450 --> 00:15:11.460 align:start position:0% tokens can either be purchased or sold 00:15:11.460 --> 00:15:15.080 align:start position:0% tokens can either be purchased or sold to<00:15:11.820> keep<00:15:12.090> the<00:15:12.180> allocation<00:15:12.780> in<00:15:12.900> check<00:15:13.880> right<00:15:14.880> so 00:15:15.080 --> 00:15:15.090 align:start position:0% to keep the allocation in check right so 00:15:15.090 --> 00:15:15.860 align:start position:0% to keep the allocation in check right so that's<00:15:15.180> it<00:15:15.360> from<00:15:15.480> me 00:15:15.860 --> 00:15:15.870 align:start position:0% that's it from me 00:15:15.870 --> 00:15:17.630 align:start position:0% that's it from me I<00:15:15.900> will<00:15:16.290> pass<00:15:16.440> back<00:15:16.650> to<00:15:16.770> Sam<00:15:16.980> who<00:15:17.250> will<00:15:17.430> talk 00:15:17.630 --> 00:15:17.640 align:start position:0% I will pass back to Sam who will talk 00:15:17.640 --> 00:15:19.340 align:start position:0% I will pass back to Sam who will talk about<00:15:17.940> some<00:15:18.300> of<00:15:18.330> our<00:15:18.480> learnings<00:15:18.990> from<00:15:19.140> these 00:15:19.340 --> 00:15:19.350 align:start position:0% about some of our learnings from these 00:15:19.350 --> 00:15:22.250 align:start position:0% about some of our learnings from these experience<00:15:20.120> experiences<00:15:21.120> and<00:15:21.330> also<00:15:21.450> a<00:15:21.900> little 00:15:22.250 --> 00:15:22.260 align:start position:0% experience experiences and also a little 00:15:22.260 --> 00:15:28.640 align:start position:0% experience experiences and also a little bit<00:15:22.380> about<00:15:22.500> our<00:15:22.800> future<00:15:23.100> roadmap<00:15:27.650> great 00:15:28.640 --> 00:15:28.650 align:start position:0% bit about our future roadmap great 00:15:28.650 --> 00:15:33.940 align:start position:0% bit about our future roadmap great thanks<00:15:28.920> Tim<00:15:29.750> so<00:15:30.750> as<00:15:30.840> you<00:15:30.960> mentioned<00:15:31.610> I<00:15:32.610> think 00:15:33.940 --> 00:15:33.950 align:start position:0% thanks Tim so as you mentioned I think 00:15:33.950 --> 00:15:36.020 align:start position:0% thanks Tim so as you mentioned I think going<00:15:34.950> through<00:15:35.220> this<00:15:35.340> over<00:15:35.580> the<00:15:35.730> last<00:15:35.820> couple 00:15:36.020 --> 00:15:36.030 align:start position:0% going through this over the last couple 00:15:36.030 --> 00:15:38.120 align:start position:0% going through this over the last couple of<00:15:36.180> years<00:15:36.390> Tim<00:15:36.810> was<00:15:36.960> here<00:15:37.230> this<00:15:37.620> time<00:15:37.890> last 00:15:38.120 --> 00:15:38.130 align:start position:0% of years Tim was here this time last 00:15:38.130 --> 00:15:41.240 align:start position:0% of years Tim was here this time last year<00:15:38.360> or<00:15:39.360> in<00:15:39.420> Shanghai<00:15:39.930> rather<00:15:40.200> talking<00:15:41.100> about 00:15:41.240 --> 00:15:41.250 align:start position:0% year or in Shanghai rather talking about 00:15:41.250 --> 00:15:43.970 align:start position:0% year or in Shanghai rather talking about block<00:15:41.460> one<00:15:41.670> ID<00:15:42.170> and<00:15:43.170> this<00:15:43.320> was<00:15:43.500> one<00:15:43.740> of<00:15:43.770> the 00:15:43.970 --> 00:15:43.980 align:start position:0% block one ID and this was one of the 00:15:43.980 --> 00:15:46.280 align:start position:0% block one ID and this was one of the biggest<00:15:44.190> learning<00:15:44.910> points<00:15:45.180> as<00:15:45.300> we<00:15:45.450> set 00:15:46.280 --> 00:15:46.290 align:start position:0% biggest learning points as we set 00:15:46.290 --> 00:15:48.230 align:start position:0% biggest learning points as we set forward<00:15:46.650> into<00:15:46.950> looking<00:15:47.310> at<00:15:47.430> how<00:15:47.550> we<00:15:47.610> make<00:15:48.060> our 00:15:48.230 --> 00:15:48.240 align:start position:0% forward into looking at how we make our 00:15:48.240 --> 00:15:50.450 align:start position:0% forward into looking at how we make our content<00:15:48.630> available<00:15:49.170> and<00:15:49.350> for<00:15:50.100> those<00:15:50.220> of<00:15:50.370> you 00:15:50.450 --> 00:15:50.460 align:start position:0% content available and for those of you 00:15:50.460 --> 00:15:52.370 align:start position:0% content available and for those of you that<00:15:50.640> weren't<00:15:50.820> here<00:15:51.330> last<00:15:51.720> year<00:15:52.140> this<00:15:52.320> is 00:15:52.370 --> 00:15:52.380 align:start position:0% that weren't here last year this is 00:15:52.380 --> 00:15:55.820 align:start position:0% that weren't here last year this is block<00:15:52.800> 1<00:15:53.070> ID<00:15:53.330> it<00:15:54.330> was<00:15:54.750> a<00:15:54.780> capability<00:15:55.260> that<00:15:55.500> we 00:15:55.820 --> 00:15:55.830 align:start position:0% block 1 ID it was a capability that we 00:15:55.830 --> 00:15:58.580 align:start position:0% block 1 ID it was a capability that we had<00:15:56.040> to<00:15:56.220> create<00:15:56.460> in<00:15:56.970> order<00:15:57.360> to<00:15:57.510> honor<00:15:57.900> the 00:15:58.580 --> 00:15:58.590 align:start position:0% had to create in order to honor the 00:15:58.590 --> 00:16:00.590 align:start position:0% had to create in order to honor the content<00:15:59.280> licensing<00:16:00.000> and<00:16:00.150> permissioning 00:16:00.590 --> 00:16:00.600 align:start position:0% content licensing and permissioning 00:16:00.600 --> 00:16:02.450 align:start position:0% content licensing and permissioning arrangements<00:16:01.290> that<00:16:01.440> we're<00:16:01.620> responsible<00:16:02.220> for 00:16:02.450 --> 00:16:02.460 align:start position:0% arrangements that we're responsible for 00:16:02.460 --> 00:16:04.760 align:start position:0% arrangements that we're responsible for as<00:16:02.880> we<00:16:03.150> distribute<00:16:03.750> content<00:16:04.110> that<00:16:04.650> we 00:16:04.760 --> 00:16:04.770 align:start position:0% as we distribute content that we 00:16:04.770 --> 00:16:07.460 align:start position:0% as we distribute content that we aggregate<00:16:05.360> through<00:16:06.360> to<00:16:06.600> the<00:16:07.110> ultimate 00:16:07.460 --> 00:16:07.470 align:start position:0% aggregate through to the ultimate 00:16:07.470 --> 00:16:13.340 align:start position:0% aggregate through to the ultimate consumer<00:16:10.460> block<00:16:11.460> 1<00:16:11.670> ID<00:16:11.850> is<00:16:12.300> essentially<00:16:13.020> an 00:16:13.340 --> 00:16:13.350 align:start position:0% consumer block 1 ID is essentially an 00:16:13.350 --> 00:16:16.340 align:start position:0% consumer block 1 ID is essentially an address<00:16:13.830> mapping<00:16:14.070> service<00:16:14.640> so<00:16:15.510> slightly 00:16:16.340 --> 00:16:16.350 align:start position:0% address mapping service so slightly 00:16:16.350 --> 00:16:17.840 align:start position:0% address mapping service so slightly different<00:16:16.680> to<00:16:16.800> some<00:16:16.950> of<00:16:17.070> the<00:16:17.130> other<00:16:17.250> identity 00:16:17.840 --> 00:16:17.850 align:start position:0% different to some of the other identity 00:16:17.850 --> 00:16:21.590 align:start position:0% different to some of the other identity capabilities<00:16:18.810> that<00:16:19.020> you've<00:16:19.230> heard<00:16:19.440> from<00:16:20.600> but 00:16:21.590 --> 00:16:21.600 align:start position:0% capabilities that you've heard from but 00:16:21.600 --> 00:16:23.630 align:start position:0% capabilities that you've heard from but it<00:16:21.750> means<00:16:22.050> that<00:16:22.260> we<00:16:22.530> can<00:16:22.710> take<00:16:22.920> an<00:16:23.190> OAuth 00:16:23.630 --> 00:16:23.640 align:start position:0% it means that we can take an OAuth 00:16:23.640 --> 00:16:26.170 align:start position:0% it means that we can take an OAuth address<00:16:24.060> like<00:16:24.630> Google<00:16:25.050> Twitter<00:16:25.380> Linkedin<00:16:25.950> and 00:16:26.170 --> 00:16:26.180 align:start position:0% address like Google Twitter Linkedin and 00:16:26.180 --> 00:16:29.180 align:start position:0% address like Google Twitter Linkedin and map<00:16:27.180> it<00:16:27.420> to<00:16:27.450> an<00:16:28.140> aetherium<00:16:28.590> address<00:16:28.860> and 00:16:29.180 --> 00:16:29.190 align:start position:0% map it to an aetherium address and 00:16:29.190 --> 00:16:34.400 align:start position:0% map it to an aetherium address and therefore<00:16:30.170> we<00:16:31.170> know<00:16:31.800> and<00:16:32.840> DAP<00:16:33.840> developers 00:16:34.400 --> 00:16:34.410 align:start position:0% therefore we know and DAP developers 00:16:34.410 --> 00:16:37.190 align:start position:0% therefore we know and DAP developers know<00:16:34.620> when<00:16:35.280> a<00:16:35.310> user<00:16:35.610> is<00:16:35.820> returning<00:16:36.390> there<00:16:37.020> they 00:16:37.190 --> 00:16:37.200 align:start position:0% know when a user is returning there they 00:16:37.200 --> 00:16:37.730 align:start position:0% know when a user is returning there they are 00:16:37.730 --> 00:16:37.740 align:start position:0% are 00:16:37.740 --> 00:16:39.950 align:start position:0% are through<00:16:38.520> a<00:16:38.550> pop-up<00:16:38.940> asked<00:16:39.240> to<00:16:39.390> authenticate 00:16:39.950 --> 00:16:39.960 align:start position:0% through a pop-up asked to authenticate 00:16:39.960 --> 00:16:42.020 align:start position:0% through a pop-up asked to authenticate themselves<00:16:40.170> and<00:16:40.800> then<00:16:41.460> you<00:16:41.580> know<00:16:41.730> that<00:16:41.910> that's 00:16:42.020 --> 00:16:42.030 align:start position:0% themselves and then you know that that's 00:16:42.030 --> 00:16:44.360 align:start position:0% themselves and then you know that that's the<00:16:42.210> same<00:16:42.330> user<00:16:42.900> coming<00:16:43.440> back<00:16:43.710> even<00:16:44.100> if<00:16:44.190> they 00:16:44.360 --> 00:16:44.370 align:start position:0% the same user coming back even if they 00:16:44.370 --> 00:16:46.430 align:start position:0% the same user coming back even if they have<00:16:44.520> different<00:16:44.760> aetherium<00:16:45.750> addresses<00:16:46.260> that 00:16:46.430 --> 00:16:46.440 align:start position:0% have different aetherium addresses that 00:16:46.440 --> 00:16:49.430 align:start position:0% have different aetherium addresses that they're<00:16:46.620> using<00:16:47.390> so<00:16:48.390> this<00:16:48.510> was<00:16:48.690> the<00:16:48.810> first<00:16:49.110> step 00:16:49.430 --> 00:16:49.440 align:start position:0% they're using so this was the first step 00:16:49.440 --> 00:16:52.790 align:start position:0% they're using so this was the first step it<00:16:49.860> was<00:16:50.040> around<00:16:50.480> identity<00:16:51.480> of<00:16:51.750> users<00:16:52.170> in<00:16:52.410> order 00:16:52.790 --> 00:16:52.800 align:start position:0% it was around identity of users in order 00:16:52.800 --> 00:16:57.110 align:start position:0% it was around identity of users in order to<00:16:52.920> honor<00:16:53.280> content<00:16:53.760> licensing<00:16:55.610> the<00:16:56.610> second 00:16:57.110 --> 00:16:57.120 align:start position:0% to honor content licensing the second 00:16:57.120 --> 00:17:01.220 align:start position:0% to honor content licensing the second learning<00:16:57.510> point<00:16:57.990> was<00:16:58.380> around<00:16:58.680> identifiers<00:17:00.230> so 00:17:01.220 --> 00:17:01.230 align:start position:0% learning point was around identifiers so 00:17:01.230 --> 00:17:04.360 align:start position:0% learning point was around identifiers so if<00:17:01.290> I<00:17:01.410> asked<00:17:01.860> you<00:17:02.130> what<00:17:02.460> the<00:17:02.880> ticker<00:17:03.330> symbol<00:17:03.510> C 00:17:04.360 --> 00:17:04.370 align:start position:0% if I asked you what the ticker symbol C 00:17:04.370 --> 00:17:07.880 align:start position:0% if I asked you what the ticker symbol C stands<00:17:05.370> for<00:17:05.610> today<00:17:06.230> then<00:17:07.230> you<00:17:07.380> would<00:17:07.530> be<00:17:07.709> right 00:17:07.880 --> 00:17:07.890 align:start position:0% stands for today then you would be right 00:17:07.890 --> 00:17:11.210 align:start position:0% stands for today then you would be right if<00:17:08.100> you<00:17:08.130> answered<00:17:08.760> Citigroup<00:17:09.770> but<00:17:10.770> if<00:17:10.860> I<00:17:10.980> dance 00:17:11.210 --> 00:17:11.220 align:start position:0% if you answered Citigroup but if I dance 00:17:11.220 --> 00:17:14.689 align:start position:0% if you answered Citigroup but if I dance Q<00:17:11.670> that<00:17:11.850> same<00:17:12.120> question<00:17:12.540> in<00:17:12.660> 1998<00:17:13.470> the<00:17:14.310> answer 00:17:14.689 --> 00:17:14.699 align:start position:0% Q that same question in 1998 the answer 00:17:14.699 --> 00:17:16.280 align:start position:0% Q that same question in 1998 the answer would<00:17:14.850> have<00:17:14.880> been<00:17:14.970> Chrysler 00:17:16.280 --> 00:17:16.290 align:start position:0% would have been Chrysler 00:17:16.290 --> 00:17:19.360 align:start position:0% would have been Chrysler and<00:17:17.100> the<00:17:17.579> problem<00:17:17.970> is<00:17:18.180> that<00:17:18.510> these<00:17:18.839> tickers 00:17:19.360 --> 00:17:19.370 align:start position:0% and the problem is that these tickers 00:17:19.370 --> 00:17:21.410 align:start position:0% and the problem is that these tickers across<00:17:20.370> the<00:17:20.490> financial<00:17:20.670> services<00:17:21.270> industry 00:17:21.410 --> 00:17:21.420 align:start position:0% across the financial services industry 00:17:21.420 --> 00:17:24.350 align:start position:0% across the financial services industry get<00:17:22.020> recycled<00:17:22.320> and<00:17:23.100> if<00:17:23.760> you're<00:17:23.880> writing<00:17:24.240> small 00:17:24.350 --> 00:17:24.360 align:start position:0% get recycled and if you're writing small 00:17:24.360 --> 00:17:26.720 align:start position:0% get recycled and if you're writing small contracts<00:17:25.050> using<00:17:25.230> these<00:17:25.530> that's<00:17:26.250> an<00:17:26.400> absolute 00:17:26.720 --> 00:17:26.730 align:start position:0% contracts using these that's an absolute 00:17:26.730 --> 00:17:29.390 align:start position:0% contracts using these that's an absolute nightmare<00:17:27.800> because<00:17:28.800> you<00:17:28.830> can't<00:17:29.100> change<00:17:29.280> your 00:17:29.390 --> 00:17:29.400 align:start position:0% nightmare because you can't change your 00:17:29.400 --> 00:17:32.090 align:start position:0% nightmare because you can't change your smart<00:17:29.760> contract<00:17:30.180> so<00:17:31.110> we<00:17:31.230> created<00:17:31.530> an<00:17:31.770> open 00:17:32.090 --> 00:17:32.100 align:start position:0% smart contract so we created an open 00:17:32.100 --> 00:17:35.960 align:start position:0% smart contract so we created an open capability<00:17:32.730> it's<00:17:33.300> called<00:17:33.480> a<00:17:33.570> perm<00:17:33.990> ID<00:17:34.200> and<00:17:34.970> you 00:17:35.960 --> 00:17:35.970 align:start position:0% capability it's called a perm ID and you 00:17:35.970 --> 00:17:38.590 align:start position:0% capability it's called a perm ID and you can<00:17:36.120> all<00:17:36.240> access<00:17:36.450> it<00:17:36.780> today<00:17:37.080> at<00:17:37.320> perm<00:17:37.560> ID<00:17:37.800> org 00:17:38.590 --> 00:17:38.600 align:start position:0% can all access it today at perm ID org 00:17:38.600 --> 00:17:40.730 align:start position:0% can all access it today at perm ID org it<00:17:39.600> essentially<00:17:39.990> creates<00:17:40.410> permanent 00:17:40.730 --> 00:17:40.740 align:start position:0% it essentially creates permanent 00:17:40.740 --> 00:17:43.880 align:start position:0% it essentially creates permanent identifiers<00:17:41.700> for<00:17:42.150> entities<00:17:42.600> which<00:17:43.470> means<00:17:43.710> you 00:17:43.880 --> 00:17:43.890 align:start position:0% identifiers for entities which means you 00:17:43.890 --> 00:17:45.560 align:start position:0% identifiers for entities which means you could<00:17:44.010> always<00:17:44.220> reference<00:17:44.820> that<00:17:45.000> number<00:17:45.420> and 00:17:45.560 --> 00:17:45.570 align:start position:0% could always reference that number and 00:17:45.570 --> 00:17:47.270 align:start position:0% could always reference that number and always<00:17:46.080> have<00:17:46.230> confidence<00:17:46.470> that<00:17:46.890> it's<00:17:47.160> going 00:17:47.270 --> 00:17:47.280 align:start position:0% always have confidence that it's going 00:17:47.280 --> 00:17:48.680 align:start position:0% always have confidence that it's going to<00:17:47.370> return<00:17:47.670> the<00:17:47.880> information<00:17:48.000> that<00:17:48.600> you 00:17:48.680 --> 00:17:48.690 align:start position:0% to return the information that you 00:17:48.690 --> 00:17:51.770 align:start position:0% to return the information that you require<00:17:48.840> even<00:17:49.320> if<00:17:49.980> the<00:17:50.130> industry<00:17:50.760> symbols<00:17:51.330> are 00:17:51.770 --> 00:17:51.780 align:start position:0% require even if the industry symbols are 00:17:51.780 --> 00:17:54.980 align:start position:0% require even if the industry symbols are recycled<00:17:52.340> so<00:17:53.340> take<00:17:53.490> a<00:17:53.520> look<00:17:53.700> at<00:17:53.850> perm<00:17:54.060> ID<00:17:54.270> or 00:17:54.980 --> 00:17:54.990 align:start position:0% recycled so take a look at perm ID or 00:17:54.990 --> 00:17:56.810 align:start position:0% recycled so take a look at perm ID or --g<00:17:55.070> doesn't<00:17:56.070> have<00:17:56.190> to<00:17:56.310> be<00:17:56.400> blockchain 00:17:56.810 --> 00:17:56.820 align:start position:0% --g doesn't have to be blockchain 00:17:56.820 --> 00:17:58.910 align:start position:0% --g doesn't have to be blockchain related<00:17:57.270> this<00:17:57.450> is<00:17:57.690> open<00:17:58.380> and<00:17:58.530> works<00:17:58.680> for 00:17:58.910 --> 00:17:58.920 align:start position:0% related this is open and works for 00:17:58.920 --> 00:18:01.130 align:start position:0% related this is open and works for everything<00:17:59.460> and<00:17:59.790> it's<00:18:00.300> available<00:18:00.870> under<00:18:01.020> a 00:18:01.130 --> 00:18:01.140 align:start position:0% everything and it's available under a 00:18:01.140 --> 00:18:03.980 align:start position:0% everything and it's available under a Creative<00:18:01.230> Commons<00:18:01.650> license<00:18:02.340> so<00:18:02.810> I'll<00:18:03.810> finish 00:18:03.980 --> 00:18:03.990 align:start position:0% Creative Commons license so I'll finish 00:18:03.990 --> 00:18:07.460 align:start position:0% Creative Commons license so I'll finish in<00:18:04.200> the<00:18:04.290> last<00:18:04.440> minute<00:18:04.890> with<00:18:05.010> what's<00:18:05.250> next<00:18:06.470> so 00:18:07.460 --> 00:18:07.470 align:start position:0% in the last minute with what's next so 00:18:07.470 --> 00:18:10.340 align:start position:0% in the last minute with what's next so firstly<00:18:07.880> we're<00:18:08.880> looking<00:18:09.150> to<00:18:09.270> expand<00:18:09.720> data 00:18:10.340 --> 00:18:10.350 align:start position:0% firstly we're looking to expand data 00:18:10.350 --> 00:18:14.390 align:start position:0% firstly we're looking to expand data coverage<00:18:10.830> I<00:18:11.100> mentioned<00:18:11.790> a<00:18:11.850> few<00:18:12.800> earlier<00:18:13.800> but 00:18:14.390 --> 00:18:14.400 align:start position:0% coverage I mentioned a few earlier but 00:18:14.400 --> 00:18:16.250 align:start position:0% coverage I mentioned a few earlier but we're<00:18:14.550> already<00:18:14.880> having<00:18:15.270> organizations<00:18:16.020> come 00:18:16.250 --> 00:18:16.260 align:start position:0% we're already having organizations come 00:18:16.260 --> 00:18:18.080 align:start position:0% we're already having organizations come to<00:18:16.380> us<00:18:16.500> now<00:18:16.710> and<00:18:16.920> saying<00:18:17.190> can<00:18:17.340> you<00:18:17.370> please<00:18:17.670> add 00:18:18.080 --> 00:18:18.090 align:start position:0% to us now and saying can you please add 00:18:18.090 --> 00:18:20.900 align:start position:0% to us now and saying can you please add electricity<00:18:18.990> prices<00:18:19.470> natural<00:18:20.370> gas<00:18:20.550> prices 00:18:20.900 --> 00:18:20.910 align:start position:0% electricity prices natural gas prices 00:18:20.910 --> 00:18:23.420 align:start position:0% electricity prices natural gas prices are<00:18:21.360> the<00:18:21.540> commodities<00:18:21.860> information<00:18:22.860> we've 00:18:23.420 --> 00:18:23.430 align:start position:0% are the commodities information we've 00:18:23.430 --> 00:18:26.030 align:start position:0% are the commodities information we've had<00:18:23.580> interest<00:18:24.210> in<00:18:24.360> supply<00:18:25.110> chain<00:18:25.440> in<00:18:25.620> general 00:18:26.030 --> 00:18:26.040 align:start position:0% had interest in supply chain in general 00:18:26.040 --> 00:18:29.540 align:start position:0% had interest in supply chain in general and<00:18:26.400> so<00:18:26.970> is<00:18:27.380> my<00:18:28.380> request<00:18:28.740> out<00:18:28.950> to<00:18:28.980> you<00:18:29.250> or<00:18:29.430> my 00:18:29.540 --> 00:18:29.550 align:start position:0% and so is my request out to you or my 00:18:29.550 --> 00:18:32.270 align:start position:0% and so is my request out to you or my first<00:18:29.730> request<00:18:30.180> out<00:18:30.360> to<00:18:30.390> you<00:18:30.690> is<00:18:30.870> if<00:18:31.070> you<00:18:32.070> have 00:18:32.270 --> 00:18:32.280 align:start position:0% first request out to you is if you have 00:18:32.280 --> 00:18:34.160 align:start position:0% first request out to you is if you have needs<00:18:32.580> for<00:18:32.880> other<00:18:33.150> content<00:18:33.600> sets<00:18:33.810> then<00:18:33.990> do 00:18:34.160 --> 00:18:34.170 align:start position:0% needs for other content sets then do 00:18:34.170 --> 00:18:36.500 align:start position:0% needs for other content sets then do come<00:18:34.350> and<00:18:34.500> talk<00:18:34.590> to<00:18:34.620> us<00:18:34.860> it's<00:18:35.580> not<00:18:35.700> limited<00:18:36.480> to 00:18:36.500 --> 00:18:36.510 align:start position:0% come and talk to us it's not limited to 00:18:36.510 --> 00:18:38.630 align:start position:0% come and talk to us it's not limited to what<00:18:36.810> we've<00:18:36.990> shown<00:18:37.200> in<00:18:37.380> this<00:18:37.530> first<00:18:37.740> beta<00:18:38.010> that 00:18:38.630 --> 00:18:38.640 align:start position:0% what we've shown in this first beta that 00:18:38.640 --> 00:18:42.370 align:start position:0% what we've shown in this first beta that was<00:18:38.760> just<00:18:38.970> a<00:18:39.060> place<00:18:39.240> to<00:18:39.450> start<00:18:39.890> and<00:18:41.240> secondly 00:18:42.370 --> 00:18:42.380 align:start position:0% was just a place to start and secondly 00:18:42.380 --> 00:18:45.980 align:start position:0% was just a place to start and secondly we<00:18:43.380> have<00:18:43.830> a<00:18:44.040> capability<00:18:44.640> called<00:18:45.150> kyc<00:18:45.870> as<00:18:45.960> a 00:18:45.980 --> 00:18:45.990 align:start position:0% we have a capability called kyc as a 00:18:45.990 --> 00:18:48.170 align:start position:0% we have a capability called kyc as a service<00:18:46.560> we<00:18:47.190> do<00:18:47.340> this<00:18:47.490> for<00:18:47.670> all<00:18:47.760> the<00:18:47.850> banks 00:18:48.170 --> 00:18:48.180 align:start position:0% service we do this for all the banks 00:18:48.180 --> 00:18:52.160 align:start position:0% service we do this for all the banks already<00:18:48.740> and<00:18:49.740> one<00:18:50.010> of<00:18:50.100> our<00:18:50.220> hypotheses<00:18:51.060> is<00:18:51.420> can 00:18:52.160 --> 00:18:52.170 align:start position:0% already and one of our hypotheses is can 00:18:52.170 --> 00:18:56.210 align:start position:0% already and one of our hypotheses is can we<00:18:52.380> be<00:18:52.590> a<00:18:52.620> kyc<00:18:53.280> service<00:18:53.760> for<00:18:54.510> investors<00:18:55.230> for 00:18:56.210 --> 00:18:56.220 align:start position:0% we be a kyc service for investors for 00:18:56.220 --> 00:18:59.120 align:start position:0% we be a kyc service for investors for initial<00:18:56.550> coin<00:18:56.730> offerings<00:18:57.240> for<00:18:58.170> advisors<00:18:58.770> for 00:18:59.120 --> 00:18:59.130 align:start position:0% initial coin offerings for advisors for 00:18:59.130 --> 00:19:02.660 align:start position:0% initial coin offerings for advisors for law<00:18:59.310> firms<00:18:59.720> can<00:19:00.720> you<00:19:00.930> take<00:19:01.200> advantage<00:19:01.500> of<00:19:02.040> the 00:19:02.660 --> 00:19:02.670 align:start position:0% law firms can you take advantage of the 00:19:02.670 --> 00:19:04.550 align:start position:0% law firms can you take advantage of the capabilities<00:19:02.850> that<00:19:03.360> we<00:19:03.750> have<00:19:03.780> that<00:19:04.230> we<00:19:04.380> would 00:19:04.550 --> 00:19:04.560 align:start position:0% capabilities that we have that we would 00:19:04.560 --> 00:19:08.210 align:start position:0% capabilities that we have that we would traditionally<00:19:04.740> use<00:19:05.430> in<00:19:05.700> banks<00:19:06.360> and<00:19:07.040> use<00:19:08.040> those 00:19:08.210 --> 00:19:08.220 align:start position:0% traditionally use in banks and use those 00:19:08.220 --> 00:19:10.640 align:start position:0% traditionally use in banks and use those same<00:19:08.720> capabilities<00:19:09.720> and<00:19:10.110> data<00:19:10.440> and 00:19:10.640 --> 00:19:10.650 align:start position:0% same capabilities and data and 00:19:10.650 --> 00:19:14.200 align:start position:0% same capabilities and data and information<00:19:10.950> in<00:19:11.700> your<00:19:12.180> identity<00:19:13.190> activities 00:19:14.200 --> 00:19:14.210 align:start position:0% information in your identity activities 00:19:14.210 --> 00:19:16.880 align:start position:0% information in your identity activities so<00:19:15.210> if<00:19:15.540> you<00:19:15.780> think<00:19:15.960> that's<00:19:16.170> appealing<00:19:16.470> please 00:19:16.880 --> 00:19:16.890 align:start position:0% so if you think that's appealing please 00:19:16.890 --> 00:19:18.380 align:start position:0% so if you think that's appealing please come<00:19:17.130> and<00:19:17.250> talk<00:19:17.400> to<00:19:17.460> me<00:19:17.700> because<00:19:18.090> that's 00:19:18.380 --> 00:19:18.390 align:start position:0% come and talk to me because that's 00:19:18.390 --> 00:19:19.790 align:start position:0% come and talk to me because that's something<00:19:18.780> that<00:19:18.900> we're<00:19:19.020> thinking<00:19:19.410> about 00:19:19.790 --> 00:19:19.800 align:start position:0% something that we're thinking about 00:19:19.800 --> 00:19:27.390 align:start position:0% something that we're thinking about working<00:19:20.010> on<00:19:20.250> right<00:19:20.550> now 00:19:27.390 --> 00:19:27.400 align:start position:0% 00:19:27.400 --> 00:19:34.979 align:start position:0% [Music]