WEBVTT Kind: captions Language: en 00:00:00.540 --> 00:00:19.110 align:start position:0% [Music] 00:00:19.110 --> 00:00:19.120 align:start position:0% 00:00:19.120 --> 00:00:23.470 align:start position:0% right<00:00:20.120> okay<00:00:20.750> so<00:00:21.710> my<00:00:21.890> name<00:00:21.950> is<00:00:22.130> Tim<00:00:22.340> I<00:00:22.550> work<00:00:23.000> in 00:00:23.470 --> 00:00:23.480 align:start position:0% right okay so my name is Tim I work in 00:00:23.480 --> 00:00:25.090 align:start position:0% right okay so my name is Tim I work in corporate<00:00:24.080> research<00:00:24.439> and<00:00:24.619> development<00:00:25.010> at 00:00:25.090 --> 00:00:25.100 align:start position:0% corporate research and development at 00:00:25.100 --> 00:00:28.150 align:start position:0% corporate research and development at Thomson<00:00:25.369> Reuters<00:00:25.490> in<00:00:25.880> London<00:00:26.710> R&D<00:00:27.710> typically 00:00:28.150 --> 00:00:28.160 align:start position:0% Thomson Reuters in London R&D typically 00:00:28.160 --> 00:00:29.980 align:start position:0% Thomson Reuters in London R&D typically works<00:00:28.460> on<00:00:28.760> problems<00:00:29.300> involving<00:00:29.660> machine 00:00:29.980 --> 00:00:29.990 align:start position:0% works on problems involving machine 00:00:29.990 --> 00:00:31.240 align:start position:0% works on problems involving machine learning<00:00:30.350> we<00:00:30.470> just<00:00:30.619> might<00:00:30.770> background<00:00:31.130> in 00:00:31.240 --> 00:00:31.250 align:start position:0% learning we just might background in 00:00:31.250 --> 00:00:32.980 align:start position:0% learning we just might background in natural<00:00:31.490> language<00:00:31.730> processing<00:00:31.759> but<00:00:32.720> I<00:00:32.810> think 00:00:32.980 --> 00:00:32.990 align:start position:0% natural language processing but I think 00:00:32.990 --> 00:00:34.270 align:start position:0% natural language processing but I think for<00:00:33.110> about<00:00:33.170> the<00:00:33.320> last<00:00:33.350> year<00:00:33.590> and<00:00:33.829> a<00:00:33.890> half<00:00:34.040> we've 00:00:34.270 --> 00:00:34.280 align:start position:0% for about the last year and a half we've 00:00:34.280 --> 00:00:36.430 align:start position:0% for about the last year and a half we've been<00:00:34.400> looking<00:00:34.670> very<00:00:34.700> closely<00:00:35.420> at<00:00:35.660> blockchain 00:00:36.430 --> 00:00:36.440 align:start position:0% been looking very closely at blockchain 00:00:36.440 --> 00:00:38.470 align:start position:0% been looking very closely at blockchain and<00:00:36.650> trying<00:00:36.829> to<00:00:36.890> figure<00:00:37.070> out<00:00:37.220> where<00:00:37.520> we<00:00:38.120> as<00:00:38.360> an 00:00:38.470 --> 00:00:38.480 align:start position:0% and trying to figure out where we as an 00:00:38.480 --> 00:00:40.590 align:start position:0% and trying to figure out where we as an organization<00:00:39.110> fit<00:00:39.470> into<00:00:39.650> this<00:00:39.890> space 00:00:40.590 --> 00:00:40.600 align:start position:0% organization fit into this space 00:00:40.600 --> 00:00:43.300 align:start position:0% organization fit into this space we're<00:00:41.600> part<00:00:41.900> of<00:00:42.050> some<00:00:42.200> of<00:00:42.230> the<00:00:42.380> other<00:00:42.530> larger 00:00:43.300 --> 00:00:43.310 align:start position:0% we're part of some of the other larger 00:00:43.310 --> 00:00:46.090 align:start position:0% we're part of some of the other larger blockchain<00:00:44.270> consortiums<00:00:44.840> like<00:00:44.960> r3<00:00:45.500> and<00:00:45.800> hyper 00:00:46.090 --> 00:00:46.100 align:start position:0% blockchain consortiums like r3 and hyper 00:00:46.100 --> 00:00:48.490 align:start position:0% blockchain consortiums like r3 and hyper ledger<00:00:46.340> but<00:00:47.030> I<00:00:47.210> think<00:00:47.450> we<00:00:47.660> spend<00:00:47.990> most<00:00:48.200> of<00:00:48.410> our 00:00:48.490 --> 00:00:48.500 align:start position:0% ledger but I think we spend most of our 00:00:48.500 --> 00:00:50.500 align:start position:0% ledger but I think we spend most of our time<00:00:48.560> working<00:00:49.010> with<00:00:49.280> aetherium<00:00:50.030> and<00:00:50.180> building 00:00:50.500 --> 00:00:50.510 align:start position:0% time working with aetherium and building 00:00:50.510 --> 00:00:54.300 align:start position:0% time working with aetherium and building demos<00:00:50.960> proof<00:00:51.860> concepts<00:00:52.370> on<00:00:52.580> aetherium 00:00:54.300 --> 00:00:54.310 align:start position:0% demos proof concepts on aetherium 00:00:54.310 --> 00:00:57.090 align:start position:0% demos proof concepts on aetherium next<00:00:55.310> slide<00:00:55.490> please 00:00:57.090 --> 00:00:57.100 align:start position:0% next slide please 00:00:57.100 --> 00:00:59.890 align:start position:0% next slide please so<00:00:58.100> a<00:00:58.460> little<00:00:58.760> bit<00:00:58.850> of<00:00:58.940> context<00:00:59.450> about<00:00:59.570> our 00:00:59.890 --> 00:00:59.900 align:start position:0% so a little bit of context about our 00:00:59.900 --> 00:01:00.690 align:start position:0% so a little bit of context about our business 00:01:00.690 --> 00:01:00.700 align:start position:0% business 00:01:00.700 --> 00:01:03.430 align:start position:0% business so<00:01:01.700> a<00:01:01.730> lot<00:01:02.120> of<00:01:02.210> you<00:01:02.330> will<00:01:02.450> know<00:01:02.690> of<00:01:03.020> us<00:01:03.170> as<00:01:03.380> a 00:01:03.430 --> 00:01:03.440 align:start position:0% so a lot of you will know of us as a 00:01:03.440 --> 00:01:05.289 align:start position:0% so a lot of you will know of us as a news<00:01:03.950> organization<00:01:04.100> but<00:01:04.820> this<00:01:04.939> is<00:01:05.059> only<00:01:05.180> a 00:01:05.289 --> 00:01:05.299 align:start position:0% news organization but this is only a 00:01:05.299 --> 00:01:08.170 align:start position:0% news organization but this is only a tiny<00:01:05.540> piece<00:01:06.110> of<00:01:06.140> what<00:01:06.439> we<00:01:06.590> do<00:01:06.820> we<00:01:07.820> essentially 00:01:08.170 --> 00:01:08.180 align:start position:0% tiny piece of what we do we essentially 00:01:08.180 --> 00:01:10.350 align:start position:0% tiny piece of what we do we essentially have<00:01:08.360> five<00:01:08.630> diverse<00:01:09.229> business<00:01:09.770> verticals 00:01:10.350 --> 00:01:10.360 align:start position:0% have five diverse business verticals 00:01:10.360 --> 00:01:12.660 align:start position:0% have five diverse business verticals financial<00:01:11.360> and<00:01:11.479> risk 00:01:12.660 --> 00:01:12.670 align:start position:0% financial and risk 00:01:12.670 --> 00:01:15.270 align:start position:0% financial and risk critical<00:01:13.670> news<00:01:13.939> and<00:01:14.090> information<00:01:14.329> about 00:01:15.270 --> 00:01:15.280 align:start position:0% critical news and information about 00:01:15.280 --> 00:01:17.190 align:start position:0% critical news and information about financial<00:01:16.280> data 00:01:17.190 --> 00:01:17.200 align:start position:0% financial data 00:01:17.200 --> 00:01:19.410 align:start position:0% financial data regulatory<00:01:18.200> information<00:01:18.710> risk<00:01:18.980> information 00:01:19.410 --> 00:01:19.420 align:start position:0% regulatory information risk information 00:01:19.420 --> 00:01:22.090 align:start position:0% regulatory information risk information we<00:01:20.420> have<00:01:20.510> a<00:01:20.540> flagship<00:01:21.050> product<00:01:21.380> called<00:01:21.590> icon 00:01:22.090 --> 00:01:22.100 align:start position:0% we have a flagship product called icon 00:01:22.100 --> 00:01:25.600 align:start position:0% we have a flagship product called icon which<00:01:22.760> has<00:01:23.560> 200,000<00:01:24.560> installs<00:01:25.040> and<00:01:25.340> you<00:01:25.400> can 00:01:25.600 --> 00:01:25.610 align:start position:0% which has 200,000 installs and you can 00:01:25.610 --> 00:01:27.700 align:start position:0% which has 200,000 installs and you can you<00:01:25.970> can<00:01:26.000> trade<00:01:26.690> and<00:01:26.900> do<00:01:26.990> analytics<00:01:27.500> on<00:01:27.560> all 00:01:27.700 --> 00:01:27.710 align:start position:0% you can trade and do analytics on all 00:01:27.710 --> 00:01:30.070 align:start position:0% you can trade and do analytics on all manner<00:01:28.010> of<00:01:28.130> financial<00:01:28.730> instruments<00:01:29.240> someone 00:01:30.070 --> 00:01:30.080 align:start position:0% manner of financial instruments someone 00:01:30.080 --> 00:01:31.780 align:start position:0% manner of financial instruments someone asked<00:01:30.290> me<00:01:30.320> last<00:01:30.500> night<00:01:30.650> we<00:01:30.950> have<00:01:31.070> either<00:01:31.250> on 00:01:31.780 --> 00:01:31.790 align:start position:0% asked me last night we have either on 00:01:31.790 --> 00:01:33.610 align:start position:0% asked me last night we have either on that<00:01:32.420> year<00:01:32.630> and<00:01:32.780> the<00:01:32.840> answer<00:01:33.050> is<00:01:33.170> not<00:01:33.380> quite 00:01:33.610 --> 00:01:33.620 align:start position:0% that year and the answer is not quite 00:01:33.620 --> 00:01:36.460 align:start position:0% that year and the answer is not quite yet<00:01:34.070> that<00:01:35.060> depends<00:01:35.450> on<00:01:35.540> customer<00:01:36.050> interests 00:01:36.460 --> 00:01:36.470 align:start position:0% yet that depends on customer interests 00:01:36.470 --> 00:01:37.800 align:start position:0% yet that depends on customer interests but<00:01:36.590> we're<00:01:36.770> working<00:01:36.920> with 00:01:37.800 --> 00:01:37.810 align:start position:0% but we're working with 00:01:37.810 --> 00:01:40.149 align:start position:0% but we're working with crypto<00:01:38.810> compare<00:01:39.200> and<00:01:39.409> so<00:01:39.650> there<00:01:39.830> might<00:01:40.010> be<00:01:40.040> a 00:01:40.149 --> 00:01:40.159 align:start position:0% crypto compare and so there might be a 00:01:40.159 --> 00:01:41.490 align:start position:0% crypto compare and so there might be a conversation<00:01:40.490> there 00:01:41.490 --> 00:01:41.500 align:start position:0% conversation there 00:01:41.500 --> 00:01:44.560 align:start position:0% conversation there legal<00:01:42.729> legal<00:01:43.729> information<00:01:44.180> for<00:01:44.330> legal 00:01:44.560 --> 00:01:44.570 align:start position:0% legal legal information for legal 00:01:44.570 --> 00:01:45.960 align:start position:0% legal legal information for legal professionals<00:01:45.049> worldwide 00:01:45.960 --> 00:01:45.970 align:start position:0% professionals worldwide 00:01:45.970 --> 00:01:49.570 align:start position:0% professionals worldwide tax<00:01:46.970> and<00:01:47.210> accounting<00:01:47.299> again<00:01:48.110> for<00:01:48.409> tax<00:01:48.650> and 00:01:49.570 --> 00:01:49.580 align:start position:0% tax and accounting again for tax and 00:01:49.580 --> 00:01:52.390 align:start position:0% tax and accounting again for tax and accountants<00:01:50.270> in<00:01:50.420> government's<00:01:51.400> intellectual 00:01:52.390 --> 00:01:52.400 align:start position:0% accountants in government's intellectual 00:01:52.400 --> 00:01:54.520 align:start position:0% accountants in government's intellectual property<00:01:52.729> and<00:01:52.850> life<00:01:53.150> sciences<00:01:53.870> so 00:01:54.520 --> 00:01:54.530 align:start position:0% property and life sciences so 00:01:54.530 --> 00:01:57.130 align:start position:0% property and life sciences so information<00:01:55.250> and<00:01:55.549> data<00:01:55.940> for<00:01:56.390> pharmaceutical 00:01:57.130 --> 00:01:57.140 align:start position:0% information and data for pharmaceutical 00:01:57.140 --> 00:01:59.680 align:start position:0% information and data for pharmaceutical firms<00:01:57.560> for<00:01:57.799> example<00:01:58.280> and<00:01:58.490> lasting<00:01:59.330> reuters 00:01:59.680 --> 00:01:59.690 align:start position:0% firms for example and lasting reuters 00:01:59.690 --> 00:02:01.539 align:start position:0% firms for example and lasting reuters news<00:02:00.080> and<00:02:00.590> i<00:02:00.710> would<00:02:00.830> say<00:02:00.979> that<00:02:01.010> it's<00:02:01.369> these 00:02:01.539 --> 00:02:01.549 align:start position:0% news and i would say that it's these 00:02:01.549 --> 00:02:03.460 align:start position:0% news and i would say that it's these first<00:02:01.909> four<00:02:02.360> that<00:02:02.750> we<00:02:02.900> are<00:02:03.020> looking<00:02:03.140> at 00:02:03.460 --> 00:02:03.470 align:start position:0% first four that we are looking at 00:02:03.470 --> 00:02:05.710 align:start position:0% first four that we are looking at potential<00:02:04.130> blockchain<00:02:04.760> applications<00:02:05.540> we're 00:02:05.710 --> 00:02:05.720 align:start position:0% potential blockchain applications we're 00:02:05.720 --> 00:02:09.759 align:start position:0% potential blockchain applications we're not<00:02:05.930> as<00:02:06.310> a<00:02:07.310> post<00:02:07.790> I<00:02:07.940> saw<00:02:08.119> on<00:02:08.299> reddit<00:02:09.140> suggested 00:02:09.759 --> 00:02:09.769 align:start position:0% not as a post I saw on reddit suggested 00:02:09.769 --> 00:02:12.220 align:start position:0% not as a post I saw on reddit suggested thinking<00:02:10.670> about<00:02:10.849> doing<00:02:11.060> journalism<00:02:11.450> on<00:02:11.989> the 00:02:12.220 --> 00:02:12.230 align:start position:0% thinking about doing journalism on the 00:02:12.230 --> 00:02:14.100 align:start position:0% thinking about doing journalism on the blockchain 00:02:14.100 --> 00:02:14.110 align:start position:0% blockchain 00:02:14.110 --> 00:02:19.150 align:start position:0% blockchain okay<00:02:15.110> next<00:02:15.290> slide<00:02:15.409> please 00:02:19.150 --> 00:02:19.160 align:start position:0% 00:02:19.160 --> 00:02:23.050 align:start position:0% I'm<00:02:20.160> just<00:02:20.400> switch<00:02:20.760> to<00:02:20.790> my<00:02:21.120> presenter<00:02:21.630> view 00:02:23.050 --> 00:02:23.060 align:start position:0% I'm just switch to my presenter view 00:02:23.060 --> 00:02:25.850 align:start position:0% I'm just switch to my presenter view so<00:02:24.060> I<00:02:24.420> suppose<00:02:24.870> many<00:02:25.050> of<00:02:25.170> our<00:02:25.260> products<00:02:25.620> and 00:02:25.850 --> 00:02:25.860 align:start position:0% so I suppose many of our products and 00:02:25.860 --> 00:02:27.410 align:start position:0% so I suppose many of our products and services<00:02:25.920> manifest<00:02:26.880> themselves<00:02:27.030> as 00:02:27.410 --> 00:02:27.420 align:start position:0% services manifest themselves as 00:02:27.420 --> 00:02:29.960 align:start position:0% services manifest themselves as proprietary<00:02:28.200> databases<00:02:28.950> and<00:02:29.430> analytic 00:02:29.960 --> 00:02:29.970 align:start position:0% proprietary databases and analytic 00:02:29.970 --> 00:02:31.940 align:start position:0% proprietary databases and analytic solutions<00:02:30.480> but<00:02:31.170> one<00:02:31.320> of<00:02:31.350> the<00:02:31.530> problems<00:02:31.740> that 00:02:31.940 --> 00:02:31.950 align:start position:0% solutions but one of the problems that 00:02:31.950 --> 00:02:33.890 align:start position:0% solutions but one of the problems that we've<00:02:32.190> had<00:02:32.220> to<00:02:32.490> deal<00:02:32.640> with<00:02:32.670> from<00:02:33.240> I<00:02:33.510> suppose<00:02:33.870> a 00:02:33.890 --> 00:02:33.900 align:start position:0% we've had to deal with from I suppose a 00:02:33.900 --> 00:02:36.230 align:start position:0% we've had to deal with from I suppose a commercial<00:02:34.500> perspective<00:02:34.650> is<00:02:35.370> one<00:02:36.120> of 00:02:36.230 --> 00:02:36.240 align:start position:0% commercial perspective is one of 00:02:36.240 --> 00:02:38.420 align:start position:0% commercial perspective is one of entitlement<00:02:36.900> so<00:02:37.020> who<00:02:37.200> should<00:02:37.260> have<00:02:37.530> access<00:02:37.770> to 00:02:38.420 --> 00:02:38.430 align:start position:0% entitlement so who should have access to 00:02:38.430 --> 00:02:41.930 align:start position:0% entitlement so who should have access to these<00:02:38.700> tools<00:02:39.000> and<00:02:39.540> databases<00:02:40.400> typically<00:02:41.400> our 00:02:41.930 --> 00:02:41.940 align:start position:0% these tools and databases typically our 00:02:41.940 --> 00:02:45.290 align:start position:0% these tools and databases typically our users<00:02:42.330> will<00:02:42.480> sign<00:02:42.720> a<00:02:43.590> license<00:02:44.430> agreement<00:02:44.520> we 00:02:45.290 --> 00:02:45.300 align:start position:0% users will sign a license agreement we 00:02:45.300 --> 00:02:46.790 align:start position:0% users will sign a license agreement we will<00:02:45.450> know<00:02:45.540> their<00:02:45.720> identity<00:02:46.260> so<00:02:46.440> essentially 00:02:46.790 --> 00:02:46.800 align:start position:0% will know their identity so essentially 00:02:46.800 --> 00:02:48.400 align:start position:0% will know their identity so essentially we're<00:02:46.920> doing<00:02:47.130> some<00:02:47.310> form<00:02:47.550> of<00:02:47.610> due<00:02:47.820> diligence 00:02:48.400 --> 00:02:48.410 align:start position:0% we're doing some form of due diligence 00:02:48.410 --> 00:02:50.600 align:start position:0% we're doing some form of due diligence and<00:02:49.410> to<00:02:49.590> help<00:02:49.740> manage<00:02:50.070> this<00:02:50.250> issue<00:02:50.400> on 00:02:50.600 --> 00:02:50.610 align:start position:0% and to help manage this issue on 00:02:50.610 --> 00:02:52.220 align:start position:0% and to help manage this issue on blockchain<00:02:51.150> and<00:02:51.180> I<00:02:51.420> emphasize<00:02:51.570> is<00:02:51.959> really<00:02:52.200> a 00:02:52.220 --> 00:02:52.230 align:start position:0% blockchain and I emphasize is really a 00:02:52.230 --> 00:02:54.020 align:start position:0% blockchain and I emphasize is really a management<00:02:52.590> rather<00:02:53.070> than<00:02:53.310> a<00:02:53.370> sort<00:02:53.550> of<00:02:53.580> control 00:02:54.020 --> 00:02:54.030 align:start position:0% management rather than a sort of control 00:02:54.030 --> 00:02:57.320 align:start position:0% management rather than a sort of control issue<00:02:55.020> we<00:02:55.830> put<00:02:56.010> together<00:02:56.130> what<00:02:56.610> we<00:02:56.640> call<00:02:57.180> an 00:02:57.320 --> 00:02:57.330 align:start position:0% issue we put together what we call an 00:02:57.330 --> 00:02:59.030 align:start position:0% issue we put together what we call an entitlement<00:02:57.930> framework<00:02:58.470> which<00:02:58.800> allows 00:02:59.030 --> 00:02:59.040 align:start position:0% entitlement framework which allows 00:02:59.040 --> 00:03:01.670 align:start position:0% entitlement framework which allows developers<00:02:59.070> to<00:02:59.760> control<00:03:00.360> access<00:03:00.690> to<00:03:01.170> their 00:03:01.670 --> 00:03:01.680 align:start position:0% developers to control access to their 00:03:01.680 --> 00:03:02.860 align:start position:0% developers to control access to their doubts 00:03:02.860 --> 00:03:02.870 align:start position:0% doubts 00:03:02.870 --> 00:03:06.530 align:start position:0% doubts next<00:03:03.870> slide<00:03:04.050> please 00:03:06.530 --> 00:03:06.540 align:start position:0% 00:03:06.540 --> 00:03:08.420 align:start position:0% so<00:03:06.840> what<00:03:06.989> does<00:03:07.080> this<00:03:07.170> look<00:03:07.350> like<00:03:07.410> well<00:03:08.220> we 00:03:08.420 --> 00:03:08.430 align:start position:0% so what does this look like well we 00:03:08.430 --> 00:03:10.190 align:start position:0% so what does this look like well we decided<00:03:08.670> to<00:03:08.880> call<00:03:09.030> it<00:03:09.180> block<00:03:09.390> 1<00:03:09.660> ID<00:03:09.870> 4 00:03:10.190 --> 00:03:10.200 align:start position:0% decided to call it block 1 ID 4 00:03:10.200 --> 00:03:11.690 align:start position:0% decided to call it block 1 ID 4 aetherium<00:03:10.530> and<00:03:10.860> we're<00:03:11.010> testing<00:03:11.430> it<00:03:11.520> at<00:03:11.640> the 00:03:11.690 --> 00:03:11.700 align:start position:0% aetherium and we're testing it at the 00:03:11.700 --> 00:03:13.720 align:start position:0% aetherium and we're testing it at the moment<00:03:11.850> and<00:03:12.390> essentially<00:03:13.020> it's<00:03:13.170> a<00:03:13.320> delegated 00:03:13.720 --> 00:03:13.730 align:start position:0% moment and essentially it's a delegated 00:03:13.730 --> 00:03:16.370 align:start position:0% moment and essentially it's a delegated identity<00:03:14.730> service<00:03:15.420> connected<00:03:16.230> to 00:03:16.370 --> 00:03:16.380 align:start position:0% identity service connected to 00:03:16.380 --> 00:03:18.890 align:start position:0% identity service connected to entitlement<00:03:17.040> contracts<00:03:17.610> so<00:03:18.360> we<00:03:18.570> would<00:03:18.720> host 00:03:18.890 --> 00:03:18.900 align:start position:0% entitlement contracts so we would host 00:03:18.900 --> 00:03:22.360 align:start position:0% entitlement contracts so we would host an<00:03:19.140> HD<00:03:19.500> wallet<00:03:19.830> we<00:03:20.790> only<00:03:20.970> hold<00:03:21.209> encrypted<00:03:21.810> keys 00:03:22.360 --> 00:03:22.370 align:start position:0% an HD wallet we only hold encrypted keys 00:03:22.370 --> 00:03:26.060 align:start position:0% an HD wallet we only hold encrypted keys ID<00:03:23.370> is<00:03:23.820> delegated<00:03:24.660> via<00:03:24.870> OAuth<00:03:25.200> 2<00:03:25.680> to<00:03:25.890> some 00:03:26.060 --> 00:03:26.070 align:start position:0% ID is delegated via OAuth 2 to some 00:03:26.070 --> 00:03:28.130 align:start position:0% ID is delegated via OAuth 2 to some standard<00:03:26.489> provider<00:03:26.820> so<00:03:27.150> it<00:03:27.239> might<00:03:27.360> be<00:03:27.420> terms 00:03:28.130 --> 00:03:28.140 align:start position:0% standard provider so it might be terms 00:03:28.140 --> 00:03:30.380 align:start position:0% standard provider so it might be terms of<00:03:28.260> Reuters<00:03:28.620> or<00:03:28.860> LinkedIn<00:03:29.370> Facebook<00:03:29.820> Google 00:03:30.380 --> 00:03:30.390 align:start position:0% of Reuters or LinkedIn Facebook Google 00:03:30.390 --> 00:03:33.110 align:start position:0% of Reuters or LinkedIn Facebook Google etc<00:03:30.870> so<00:03:31.380> this<00:03:31.500> is<00:03:31.709> an<00:03:31.830> effect<00:03:32.130> a<00:03:32.640> bridge 00:03:33.110 --> 00:03:33.120 align:start position:0% etc so this is an effect a bridge 00:03:33.120 --> 00:03:36.620 align:start position:0% etc so this is an effect a bridge between<00:03:33.360> the<00:03:33.810> wallet<00:03:34.260> and<00:03:34.410> OAuth<00:03:34.830> 2<00:03:35.630> this 00:03:36.620 --> 00:03:36.630 align:start position:0% between the wallet and OAuth 2 this 00:03:36.630 --> 00:03:38.210 align:start position:0% between the wallet and OAuth 2 this requires<00:03:36.989> that<00:03:37.170> you<00:03:37.320> need<00:03:37.500> to<00:03:37.590> be<00:03:37.680> logged<00:03:37.980> in 00:03:38.210 --> 00:03:38.220 align:start position:0% requires that you need to be logged in 00:03:38.220 --> 00:03:40.009 align:start position:0% requires that you need to be logged in to<00:03:38.610> use<00:03:39.030> the<00:03:39.150> DAP<00:03:39.330> and<00:03:39.480> if<00:03:39.540> you're<00:03:39.660> not<00:03:39.810> logged 00:03:40.009 --> 00:03:40.019 align:start position:0% to use the DAP and if you're not logged 00:03:40.019 --> 00:03:43.460 align:start position:0% to use the DAP and if you're not logged in<00:03:40.230> access<00:03:41.100> to<00:03:41.310> the<00:03:41.400> DAP<00:03:41.580> is<00:03:41.760> blocked<00:03:42.290> we<00:03:43.290> have 00:03:43.460 --> 00:03:43.470 align:start position:0% in access to the DAP is blocked we have 00:03:43.470 --> 00:03:46.729 align:start position:0% in access to the DAP is blocked we have some<00:03:43.739> ID<00:03:44.220> obfuscation<00:03:45.120> and<00:03:45.540> also<00:03:45.989> isolation 00:03:46.729 --> 00:03:46.739 align:start position:0% some ID obfuscation and also isolation 00:03:46.739 --> 00:03:47.870 align:start position:0% some ID obfuscation and also isolation so<00:03:46.980> there<00:03:47.160> will<00:03:47.250> be<00:03:47.280> a<00:03:47.370> separate<00:03:47.760> address 00:03:47.870 --> 00:03:47.880 align:start position:0% so there will be a separate address 00:03:47.880 --> 00:03:50.539 align:start position:0% so there will be a separate address generated<00:03:48.810> for<00:03:49.260> different<00:03:49.590> apps<00:03:49.769> to<00:03:50.010> prevent 00:03:50.539 --> 00:03:50.549 align:start position:0% generated for different apps to prevent 00:03:50.549 --> 00:03:51.520 align:start position:0% generated for different apps to prevent interference 00:03:51.520 --> 00:03:51.530 align:start position:0% interference 00:03:51.530 --> 00:03:54.229 align:start position:0% interference and<00:03:52.530> then<00:03:52.620> on<00:03:52.799> the<00:03:52.920> entitlement<00:03:53.190> side<00:03:53.700> that's 00:03:54.229 --> 00:03:54.239 align:start position:0% and then on the entitlement side that's 00:03:54.239 --> 00:03:56.180 align:start position:0% and then on the entitlement side that's performed<00:03:54.570> on<00:03:54.690> chain<00:03:54.930> we<00:03:55.530> have<00:03:55.620> a<00:03:55.680> contract 00:03:56.180 --> 00:03:56.190 align:start position:0% performed on chain we have a contract 00:03:56.190 --> 00:03:59.530 align:start position:0% performed on chain we have a contract that<00:03:56.250> is<00:03:56.370> populated<00:03:57.060> with<00:03:57.540> addresses<00:03:58.380> by<00:03:58.920> us 00:03:59.530 --> 00:03:59.540 align:start position:0% that is populated with addresses by us 00:03:59.540 --> 00:04:01.970 align:start position:0% that is populated with addresses by us and<00:04:00.540> those<00:04:00.780> addresses<00:04:01.170> are<00:04:01.320> allowed<00:04:01.530> to<00:04:01.650> use 00:04:01.970 --> 00:04:01.980 align:start position:0% and those addresses are allowed to use 00:04:01.980 --> 00:04:04.789 align:start position:0% and those addresses are allowed to use the<00:04:02.220> DAP<00:04:02.430> the<00:04:03.420> DAP<00:04:03.630> developer<00:04:04.170> can<00:04:04.440> require 00:04:04.789 --> 00:04:04.799 align:start position:0% the DAP the DAP developer can require 00:04:04.799 --> 00:04:06.710 align:start position:0% the DAP the DAP developer can require the<00:04:05.010> end<00:04:05.220> users<00:04:05.670> sign<00:04:06.030> up<00:04:06.180> to<00:04:06.299> terms<00:04:06.540> and 00:04:06.710 --> 00:04:06.720 align:start position:0% the end users sign up to terms and 00:04:06.720 --> 00:04:08.930 align:start position:0% the end users sign up to terms and conditions<00:04:07.160> and<00:04:08.160> a<00:04:08.250> few<00:04:08.430> things<00:04:08.580> that<00:04:08.820> we're 00:04:08.930 --> 00:04:08.940 align:start position:0% conditions and a few things that we're 00:04:08.940 --> 00:04:10.699 align:start position:0% conditions and a few things that we're looking<00:04:09.030> to<00:04:09.180> add<00:04:09.360> in<00:04:09.480> the<00:04:09.570> future<00:04:09.750> note<00:04:10.290> sort 00:04:10.699 --> 00:04:10.709 align:start position:0% looking to add in the future note sort 00:04:10.709 --> 00:04:12.620 align:start position:0% looking to add in the future note sort of<00:04:10.769> certainty<00:04:11.190> about<00:04:11.340> this<00:04:11.730> but<00:04:11.970> essentially 00:04:12.620 --> 00:04:12.630 align:start position:0% of certainty about this but essentially 00:04:12.630 --> 00:04:15.440 align:start position:0% of certainty about this but essentially connect<00:04:12.900> up<00:04:13.049> to<00:04:13.170> some<00:04:13.350> of<00:04:13.380> our<00:04:13.709> kyc<00:04:14.519> services 00:04:15.440 --> 00:04:15.450 align:start position:0% connect up to some of our kyc services 00:04:15.450 --> 00:04:18.670 align:start position:0% connect up to some of our kyc services and<00:04:15.720> add<00:04:16.109> more<00:04:16.350> identity<00:04:16.950> providers 00:04:18.670 --> 00:04:18.680 align:start position:0% and add more identity providers 00:04:18.680 --> 00:04:21.520 align:start position:0% and add more identity providers next<00:04:19.680> slide 00:04:21.520 --> 00:04:21.530 align:start position:0% next slide 00:04:21.530 --> 00:04:23.810 align:start position:0% next slide so<00:04:22.530> I<00:04:22.740> suppose<00:04:22.950> this<00:04:23.100> is<00:04:23.250> what<00:04:23.370> it<00:04:23.460> looks<00:04:23.640> like 00:04:23.810 --> 00:04:23.820 align:start position:0% so I suppose this is what it looks like 00:04:23.820 --> 00:04:25.640 align:start position:0% so I suppose this is what it looks like you<00:04:24.000> would<00:04:24.090> get<00:04:24.240> a<00:04:24.300> wallet<00:04:24.600> bar<00:04:24.900> we<00:04:25.410> were<00:04:25.470> very 00:04:25.640 --> 00:04:25.650 align:start position:0% you would get a wallet bar we were very 00:04:25.650 --> 00:04:27.950 align:start position:0% you would get a wallet bar we were very simple<00:04:26.010> API<00:04:26.100> allowing<00:04:26.940> users<00:04:27.210> to<00:04:27.240> sign<00:04:27.599> in<00:04:27.810> and 00:04:27.950 --> 00:04:27.960 align:start position:0% simple API allowing users to sign in and 00:04:27.960 --> 00:04:28.610 align:start position:0% simple API allowing users to sign in and out 00:04:28.610 --> 00:04:28.620 align:start position:0% out 00:04:28.620 --> 00:04:30.469 align:start position:0% out there's<00:04:28.979> also<00:04:29.280> generation<00:04:30.030> of<00:04:30.120> aetherium 00:04:30.469 --> 00:04:30.479 align:start position:0% there's also generation of aetherium 00:04:30.479 --> 00:04:31.570 align:start position:0% there's also generation of aetherium accounts 00:04:31.570 --> 00:04:31.580 align:start position:0% accounts 00:04:31.580 --> 00:04:34.059 align:start position:0% accounts on<00:04:31.759> first<00:04:32.120> use<00:04:32.360> for<00:04:32.900> each<00:04:33.020> nap 00:04:34.059 --> 00:04:34.069 align:start position:0% on first use for each nap 00:04:34.069 --> 00:04:37.300 align:start position:0% on first use for each nap there's<00:04:34.370> also<00:04:34.520> wallet<00:04:35.060> admin<00:04:35.479> console<00:04:36.310> and 00:04:37.300 --> 00:04:37.310 align:start position:0% there's also wallet admin console and 00:04:37.310 --> 00:04:38.740 align:start position:0% there's also wallet admin console and importantly<00:04:37.729> we<00:04:37.879> have<00:04:38.000> no<00:04:38.180> access<00:04:38.539> to 00:04:38.740 --> 00:04:38.750 align:start position:0% importantly we have no access to 00:04:38.750 --> 00:04:40.659 align:start position:0% importantly we have no access to accounts<00:04:39.020> or<00:04:39.409> passwords<00:04:39.949> we<00:04:40.189> only<00:04:40.340> store 00:04:40.659 --> 00:04:40.669 align:start position:0% accounts or passwords we only store 00:04:40.669 --> 00:04:43.240 align:start position:0% accounts or passwords we only store encrypted<00:04:41.569> keys<00:04:41.780> and<00:04:42.590> the<00:04:42.710> system<00:04:42.979> received 00:04:43.240 --> 00:04:43.250 align:start position:0% encrypted keys and the system received 00:04:43.250 --> 00:04:45.550 align:start position:0% encrypted keys and the system received an<00:04:43.340> encrypted<00:04:43.460> blob<00:04:44.000> from<00:04:44.389> our<00:04:44.509> server<00:04:44.780> and 00:04:45.550 --> 00:04:45.560 align:start position:0% an encrypted blob from our server and 00:04:45.560 --> 00:04:47.170 align:start position:0% an encrypted blob from our server and down<00:04:46.039> on<00:04:46.159> the<00:04:46.219> bottom<00:04:46.550> I<00:04:46.699> suppose<00:04:46.909> this<00:04:47.030> is 00:04:47.170 --> 00:04:47.180 align:start position:0% down on the bottom I suppose this is 00:04:47.180 --> 00:04:48.939 align:start position:0% down on the bottom I suppose this is just<00:04:47.360> the<00:04:47.479> hierarchical<00:04:48.050> wallet<00:04:48.469> structure 00:04:48.939 --> 00:04:48.949 align:start position:0% just the hierarchical wallet structure 00:04:48.949 --> 00:04:50.409 align:start position:0% just the hierarchical wallet structure and<00:04:49.129> it<00:04:49.490> sort<00:04:49.669> of<00:04:49.699> indicates<00:04:50.120> that<00:04:50.240> you<00:04:50.300> would 00:04:50.409 --> 00:04:50.419 align:start position:0% and it sort of indicates that you would 00:04:50.419 --> 00:04:52.450 align:start position:0% and it sort of indicates that you would have<00:04:50.509> a<00:04:50.539> different<00:04:50.840> address<00:04:50.990> for<00:04:51.590> each<00:04:51.620> for 00:04:52.450 --> 00:04:52.460 align:start position:0% have a different address for each for 00:04:52.460 --> 00:04:54.270 align:start position:0% have a different address for each for each<00:04:52.490> doubt 00:04:54.270 --> 00:04:54.280 align:start position:0% each doubt 00:04:54.280 --> 00:04:57.719 align:start position:0% each doubt and<00:04:55.360> next<00:04:56.360> slide 00:04:57.719 --> 00:04:57.729 align:start position:0% and next slide 00:04:57.729 --> 00:05:01.869 align:start position:0% and next slide so<00:04:58.729> what<00:04:59.509> sort<00:04:59.719> of<00:04:59.780> DAPs<00:05:00.319> and<00:05:00.680> services<00:05:01.639> might 00:05:01.869 --> 00:05:01.879 align:start position:0% so what sort of DAPs and services might 00:05:01.879 --> 00:05:04.330 align:start position:0% so what sort of DAPs and services might we<00:05:02.030> provide<00:05:02.590> well<00:05:03.590> I've<00:05:03.650> already<00:05:03.800> talked<00:05:04.129> to<00:05:04.250> a 00:05:04.330 --> 00:05:04.340 align:start position:0% we provide well I've already talked to a 00:05:04.340 --> 00:05:05.770 align:start position:0% we provide well I've already talked to a number<00:05:04.639> of<00:05:04.699> people<00:05:04.849> over<00:05:05.030> the<00:05:05.210> last<00:05:05.300> couple<00:05:05.719> of 00:05:05.770 --> 00:05:05.780 align:start position:0% number of people over the last couple of 00:05:05.780 --> 00:05:08.709 align:start position:0% number of people over the last couple of days<00:05:05.930> about<00:05:06.229> kyc<00:05:06.830> and<00:05:07.129> naml<00:05:07.699> services<00:05:08.330> and 00:05:08.709 --> 00:05:08.719 align:start position:0% days about kyc and naml services and 00:05:08.719 --> 00:05:09.879 align:start position:0% days about kyc and naml services and this<00:05:08.870> is<00:05:09.020> actually<00:05:09.259> a<00:05:09.319> space<00:05:09.560> where<00:05:09.800> we 00:05:09.879 --> 00:05:09.889 align:start position:0% this is actually a space where we 00:05:09.889 --> 00:05:11.320 align:start position:0% this is actually a space where we already<00:05:10.159> are<00:05:10.460> very<00:05:10.639> active<00:05:11.030> and<00:05:11.150> have<00:05:11.270> a 00:05:11.320 --> 00:05:11.330 align:start position:0% already are very active and have a 00:05:11.330 --> 00:05:13.029 align:start position:0% already are very active and have a number<00:05:11.479> of<00:05:11.629> sort<00:05:12.139> of<00:05:12.169> so-called<00:05:12.560> flagship 00:05:13.029 --> 00:05:13.039 align:start position:0% number of sort of so-called flagship 00:05:13.039 --> 00:05:15.309 align:start position:0% number of sort of so-called flagship products<00:05:13.430> that<00:05:13.940> are<00:05:14.030> heavily<00:05:14.270> used<00:05:14.569> by<00:05:14.690> for 00:05:15.309 --> 00:05:15.319 align:start position:0% products that are heavily used by for 00:05:15.319 --> 00:05:17.290 align:start position:0% products that are heavily used by for example<00:05:15.440> investment<00:05:16.039> banks<00:05:16.370> and<00:05:17.180> we're 00:05:17.290 --> 00:05:17.300 align:start position:0% example investment banks and we're 00:05:17.300 --> 00:05:18.430 align:start position:0% example investment banks and we're having<00:05:17.419> a<00:05:17.539> good<00:05:17.690> think<00:05:17.900> about<00:05:17.960> how<00:05:18.169> we<00:05:18.229> can 00:05:18.430 --> 00:05:18.440 align:start position:0% having a good think about how we can 00:05:18.440 --> 00:05:20.170 align:start position:0% having a good think about how we can make<00:05:18.560> these<00:05:18.710> things<00:05:18.860> available<00:05:19.099> on<00:05:19.490> chain<00:05:19.849> for 00:05:20.170 --> 00:05:20.180 align:start position:0% make these things available on chain for 00:05:20.180 --> 00:05:22.119 align:start position:0% make these things available on chain for example<00:05:20.210> via<00:05:20.810> some<00:05:21.139> kind<00:05:21.169> of<00:05:21.379> Oracle<00:05:21.740> service 00:05:22.119 --> 00:05:22.129 align:start position:0% example via some kind of Oracle service 00:05:22.129 --> 00:05:24.279 align:start position:0% example via some kind of Oracle service so<00:05:23.000> we<00:05:23.090> have<00:05:23.180> something<00:05:23.389> called<00:05:23.479> org<00:05:23.719> ID<00:05:23.900> and 00:05:24.279 --> 00:05:24.289 align:start position:0% so we have something called org ID and 00:05:24.289 --> 00:05:28.110 align:start position:0% so we have something called org ID and this<00:05:24.409> is<00:05:24.590> a<00:05:24.620> sort<00:05:24.919> of<00:05:24.979> organizational<00:05:26.199> level 00:05:28.110 --> 00:05:28.120 align:start position:0% this is a sort of organizational level 00:05:28.120 --> 00:05:31.170 align:start position:0% this is a sort of organizational level database<00:05:29.120> of<00:05:29.389> 190,000<00:05:30.349> compliance<00:05:30.770> records 00:05:31.170 --> 00:05:31.180 align:start position:0% database of 190,000 compliance records 00:05:31.180 --> 00:05:33.580 align:start position:0% database of 190,000 compliance records we<00:05:32.180> also<00:05:32.360> have<00:05:32.539> something<00:05:32.750> called<00:05:32.840> enhanced 00:05:33.580 --> 00:05:33.590 align:start position:0% we also have something called enhanced 00:05:33.590 --> 00:05:35.559 align:start position:0% we also have something called enhanced due<00:05:33.800> diligence<00:05:34.310> this<00:05:34.759> is<00:05:34.879> background<00:05:35.120> checks 00:05:35.559 --> 00:05:35.569 align:start position:0% due diligence this is background checks 00:05:35.569 --> 00:05:37.899 align:start position:0% due diligence this is background checks on<00:05:35.690> individuals<00:05:36.289> so<00:05:36.500> so<00:05:37.069> all<00:05:37.219> that<00:05:37.370> is<00:05:37.550> more<00:05:37.819> of 00:05:37.899 --> 00:05:37.909 align:start position:0% on individuals so so all that is more of 00:05:37.909 --> 00:05:41.019 align:start position:0% on individuals so so all that is more of a<00:05:38.000> sort<00:05:38.330> of<00:05:38.389> business<00:05:38.960> level<00:05:39.319> kyc<00:05:40.219> enhanced 00:05:41.019 --> 00:05:41.029 align:start position:0% a sort of business level kyc enhanced 00:05:41.029 --> 00:05:42.430 align:start position:0% a sort of business level kyc enhanced you<00:05:41.120> diligence<00:05:41.479> is<00:05:41.629> sort<00:05:41.779> of<00:05:41.810> businesses<00:05:42.229> and 00:05:42.430 --> 00:05:42.440 align:start position:0% you diligence is sort of businesses and 00:05:42.440 --> 00:05:44.320 align:start position:0% you diligence is sort of businesses and individuals<00:05:42.879> and<00:05:43.879> then<00:05:44.000> there's<00:05:44.150> something 00:05:44.320 --> 00:05:44.330 align:start position:0% individuals and then there's something 00:05:44.330 --> 00:05:45.820 align:start position:0% individuals and then there's something called<00:05:44.419> world<00:05:44.719> check<00:05:45.020> and<00:05:45.289> again<00:05:45.560> this<00:05:45.680> is 00:05:45.820 --> 00:05:45.830 align:start position:0% called world check and again this is 00:05:45.830 --> 00:05:48.189 align:start position:0% called world check and again this is sort<00:05:46.039> of<00:05:46.129> entity<00:05:46.490> level<00:05:46.699> screening<00:05:47.479> based<00:05:47.930> on 00:05:48.189 --> 00:05:48.199 align:start position:0% sort of entity level screening based on 00:05:48.199 --> 00:05:49.899 align:start position:0% sort of entity level screening based on both<00:05:48.349> business<00:05:48.770> relationships<00:05:49.339> and<00:05:49.460> human 00:05:49.899 --> 00:05:49.909 align:start position:0% both business relationships and human 00:05:49.909 --> 00:05:52.659 align:start position:0% both business relationships and human networks<00:05:50.469> so<00:05:51.469> those<00:05:51.620> are<00:05:51.740> a<00:05:51.800> few<00:05:51.919> of<00:05:52.039> our<00:05:52.099> K<00:05:52.550> by 00:05:52.659 --> 00:05:52.669 align:start position:0% networks so those are a few of our K by 00:05:52.669 --> 00:05:54.519 align:start position:0% networks so those are a few of our K by CNA<00:05:53.000> ml<00:05:53.180> products<00:05:53.690> but<00:05:54.229> there's<00:05:54.379> another 00:05:54.519 --> 00:05:54.529 align:start position:0% CNA ml products but there's another 00:05:54.529 --> 00:05:56.409 align:start position:0% CNA ml products but there's another space<00:05:55.039> where<00:05:55.279> we<00:05:55.370> have<00:05:55.490> a<00:05:55.520> very<00:05:55.580> natural<00:05:56.210> fit 00:05:56.409 --> 00:05:56.419 align:start position:0% space where we have a very natural fit 00:05:56.419 --> 00:05:57.579 align:start position:0% space where we have a very natural fit we<00:05:56.599> think<00:05:56.810> in<00:05:56.900> the<00:05:56.960> blockchain<00:05:57.169> space 00:05:57.579 --> 00:05:57.589 align:start position:0% we think in the blockchain space 00:05:57.589 --> 00:05:59.079 align:start position:0% we think in the blockchain space particularly<00:05:58.430> with<00:05:58.639> regard<00:05:58.909> to<00:05:58.969> our 00:05:59.079 --> 00:05:59.089 align:start position:0% particularly with regard to our 00:05:59.089 --> 00:06:01.329 align:start position:0% particularly with regard to our financial<00:05:59.509> and<00:05:59.719> risk<00:05:59.900> business<00:06:00.589> unit<00:06:01.069> and 00:06:01.329 --> 00:06:01.339 align:start position:0% financial and risk business unit and 00:06:01.339 --> 00:06:03.700 align:start position:0% financial and risk business unit and that's<00:06:01.550> with<00:06:01.729> regard<00:06:02.000> to<00:06:02.029> financial<00:06:02.539> data<00:06:02.750> via 00:06:03.700 --> 00:06:03.710 align:start position:0% that's with regard to financial data via 00:06:03.710 --> 00:06:14.360 align:start position:0% that's with regard to financial data via Oracle's 00:06:14.360 --> 00:06:14.370 align:start position:0% 00:06:14.370 --> 00:06:18.780 align:start position:0% so<00:06:15.750> we<00:06:16.750> have<00:06:17.230> a<00:06:17.470> product<00:06:17.830> called<00:06:18.160> Thomson 00:06:18.780 --> 00:06:18.790 align:start position:0% so we have a product called Thomson 00:06:18.790 --> 00:06:21.000 align:start position:0% so we have a product called Thomson Reuters<00:06:18.880> electron<00:06:19.510> and<00:06:20.320> this<00:06:20.530> essentially 00:06:21.000 --> 00:06:21.010 align:start position:0% Reuters electron and this essentially 00:06:21.010 --> 00:06:23.070 align:start position:0% Reuters electron and this essentially contains<00:06:21.310> vast<00:06:21.820> amounts<00:06:22.300> of<00:06:22.420> financial<00:06:22.630> data 00:06:23.070 --> 00:06:23.080 align:start position:0% contains vast amounts of financial data 00:06:23.080 --> 00:06:24.860 align:start position:0% contains vast amounts of financial data sorry 00:06:24.860 --> 00:06:24.870 align:start position:0% sorry 00:06:24.870 --> 00:06:29.000 align:start position:0% sorry I've<00:06:25.870> got<00:06:26.050> to<00:06:26.080> click<00:06:26.290> on<00:06:26.410> to<00:06:26.440> the<00:06:26.560> next<00:06:26.710> one 00:06:29.000 --> 00:06:29.010 align:start position:0% 00:06:29.010 --> 00:06:31.820 align:start position:0% yeah<00:06:30.010> there<00:06:30.250> we<00:06:30.340> go 00:06:31.820 --> 00:06:31.830 align:start position:0% yeah there we go 00:06:31.830 --> 00:06:34.920 align:start position:0% yeah there we go these<00:06:32.830> products<00:06:33.280> are<00:06:33.370> already<00:06:33.490> used<00:06:33.880> by<00:06:34.240> some 00:06:34.920 --> 00:06:34.930 align:start position:0% these products are already used by some 00:06:34.930 --> 00:06:36.750 align:start position:0% these products are already used by some of<00:06:35.020> the<00:06:35.080> world's<00:06:35.380> top<00:06:35.560> 50<00:06:36.040> investment<00:06:36.490> banks 00:06:36.750 --> 00:06:36.760 align:start position:0% of the world's top 50 investment banks 00:06:36.760 --> 00:06:38.520 align:start position:0% of the world's top 50 investment banks so<00:06:36.910> in<00:06:37.060> many<00:06:37.570> ways<00:06:37.810> we're<00:06:37.990> already<00:06:38.170> a<00:06:38.200> highly 00:06:38.520 --> 00:06:38.530 align:start position:0% so in many ways we're already a highly 00:06:38.530 --> 00:06:40.860 align:start position:0% so in many ways we're already a highly trusted<00:06:38.980> data<00:06:39.580> source 00:06:40.860 --> 00:06:40.870 align:start position:0% trusted data source 00:06:40.870 --> 00:06:42.660 align:start position:0% trusted data source what<00:06:41.320> electron<00:06:41.710> is<00:06:41.830> is<00:06:41.980> essentially<00:06:42.340> a<00:06:42.400> low 00:06:42.660 --> 00:06:42.670 align:start position:0% what electron is is essentially a low 00:06:42.670 --> 00:06:44.480 align:start position:0% what electron is is essentially a low latency<00:06:43.180> feed<00:06:43.420> platform<00:06:43.930> it<00:06:44.050> covers 00:06:44.480 --> 00:06:44.490 align:start position:0% latency feed platform it covers 00:06:44.490 --> 00:06:47.670 align:start position:0% latency feed platform it covers exchange-traded<00:06:45.490> and<00:06:45.820> OTC<00:06:46.240> markets<00:06:46.680> all 00:06:47.670 --> 00:06:47.680 align:start position:0% exchange-traded and OTC markets all 00:06:47.680 --> 00:06:49.370 align:start position:0% exchange-traded and OTC markets all manner<00:06:47.950> of<00:06:48.040> financial<00:06:48.640> instruments 00:06:49.370 --> 00:06:49.380 align:start position:0% manner of financial instruments 00:06:49.380 --> 00:06:52.110 align:start position:0% manner of financial instruments currencies<00:06:50.380> equities<00:06:50.890> you<00:06:51.190> name<00:06:51.370> it<00:06:51.580> and<00:06:51.820> you 00:06:52.110 --> 00:06:52.120 align:start position:0% currencies equities you name it and you 00:06:52.120 --> 00:06:53.730 align:start position:0% currencies equities you name it and you can<00:06:52.240> also<00:06:52.360> get<00:06:52.540> company<00:06:53.020> fundamental<00:06:53.560> data 00:06:53.730 --> 00:06:53.740 align:start position:0% can also get company fundamental data 00:06:53.740 --> 00:06:56.040 align:start position:0% can also get company fundamental data and<00:06:54.130> we've<00:06:54.490> spoken<00:06:55.060> to<00:06:55.270> some<00:06:55.900> of<00:06:55.990> the 00:06:56.040 --> 00:06:56.050 align:start position:0% and we've spoken to some of the 00:06:56.050 --> 00:06:57.840 align:start position:0% and we've spoken to some of the prediction<00:06:56.410> market<00:06:56.770> guys<00:06:56.950> about<00:06:57.280> that<00:06:57.340> sort 00:06:57.840 --> 00:06:57.850 align:start position:0% prediction market guys about that sort 00:06:57.850 --> 00:07:00.360 align:start position:0% prediction market guys about that sort of<00:06:57.910> information<00:06:58.680> there's<00:06:59.680> a<00:06:59.710> real-time<00:07:00.100> data 00:07:00.360 --> 00:07:00.370 align:start position:0% of information there's a real-time data 00:07:00.370 --> 00:07:02.670 align:start position:0% of information there's a real-time data you<00:07:00.700> can<00:07:00.820> get<00:07:00.970> news<00:07:01.270> from<00:07:01.510> their<00:07:01.690> reference 00:07:02.670 --> 00:07:02.680 align:start position:0% you can get news from their reference 00:07:02.680 --> 00:07:05.250 align:start position:0% you can get news from their reference data<00:07:03.090> third-party<00:07:04.090> data<00:07:04.240> and<00:07:04.930> we<00:07:04.990> won't<00:07:05.140> have 00:07:05.250 --> 00:07:05.260 align:start position:0% data third-party data and we won't have 00:07:05.260 --> 00:07:06.540 align:start position:0% data third-party data and we won't have also<00:07:05.590> have<00:07:05.680> something<00:07:05.830> called<00:07:05.920> tick<00:07:06.190> history 00:07:06.540 --> 00:07:06.550 align:start position:0% also have something called tick history 00:07:06.550 --> 00:07:07.710 align:start position:0% also have something called tick history which<00:07:06.670> currently<00:07:07.030> contains<00:07:07.360> about<00:07:07.570> 2 00:07:07.710 --> 00:07:07.720 align:start position:0% which currently contains about 2 00:07:07.720 --> 00:07:10.590 align:start position:0% which currently contains about 2 petabytes<00:07:08.260> of<00:07:08.490> microsecond<00:07:09.600> time-stamped 00:07:10.590 --> 00:07:10.600 align:start position:0% petabytes of microsecond time-stamped 00:07:10.600 --> 00:07:14.270 align:start position:0% petabytes of microsecond time-stamped tick<00:07:10.930> data<00:07:11.140> going<00:07:11.500> back<00:07:11.680> to<00:07:11.770> about<00:07:11.920> 1996 00:07:14.270 --> 00:07:14.280 align:start position:0% tick data going back to about 1996 00:07:14.280 --> 00:07:17.040 align:start position:0% tick data going back to about 1996 great<00:07:15.310> ok<00:07:15.820> so<00:07:15.880> we've<00:07:16.090> already<00:07:16.240> built<00:07:16.690> some<00:07:17.020> of 00:07:17.040 --> 00:07:17.050 align:start position:0% great ok so we've already built some of 00:07:17.050 --> 00:07:18.690 align:start position:0% great ok so we've already built some of this<00:07:17.200> stuff<00:07:17.440> out<00:07:17.590> so<00:07:17.740> this<00:07:17.860> is<00:07:18.040> this<00:07:18.340> is<00:07:18.460> sort 00:07:18.690 --> 00:07:18.700 align:start position:0% this stuff out so this is this is sort 00:07:18.700 --> 00:07:22.080 align:start position:0% this stuff out so this is this is sort of<00:07:18.760> quite<00:07:19.150> an<00:07:20.110> old<00:07:20.320> image<00:07:20.620> of<00:07:20.980> a<00:07:21.520> sort<00:07:22.060> of 00:07:22.080 --> 00:07:22.090 align:start position:0% of quite an old image of a sort of 00:07:22.090 --> 00:07:25.530 align:start position:0% of quite an old image of a sort of Oracle<00:07:22.510> architectural<00:07:23.410> model<00:07:24.060> so<00:07:25.060> you<00:07:25.390> might 00:07:25.530 --> 00:07:25.540 align:start position:0% Oracle architectural model so you might 00:07:25.540 --> 00:07:27.150 align:start position:0% Oracle architectural model so you might start<00:07:25.690> off<00:07:25.900> over<00:07:26.200> here<00:07:26.380> you<00:07:26.590> might<00:07:26.620> deploy<00:07:27.130> a 00:07:27.150 --> 00:07:27.160 align:start position:0% start off over here you might deploy a 00:07:27.160 --> 00:07:28.890 align:start position:0% start off over here you might deploy a smart<00:07:27.700> financial<00:07:27.910> instrument<00:07:28.570> that<00:07:28.690> might 00:07:28.890 --> 00:07:28.900 align:start position:0% smart financial instrument that might 00:07:28.900 --> 00:07:31.070 align:start position:0% smart financial instrument that might for<00:07:29.050> example<00:07:29.080> represent<00:07:29.740> a<00:07:29.830> bond<00:07:30.130> for<00:07:30.400> example 00:07:31.070 --> 00:07:31.080 align:start position:0% for example represent a bond for example 00:07:31.080 --> 00:07:33.450 align:start position:0% for example represent a bond for example you<00:07:32.080> would<00:07:32.200> make<00:07:32.380> a<00:07:32.410> request<00:07:32.590> and<00:07:33.100> that<00:07:33.220> would 00:07:33.450 --> 00:07:33.460 align:start position:0% you would make a request and that would 00:07:33.460 --> 00:07:35.100 align:start position:0% you would make a request and that would talk<00:07:33.700> to<00:07:33.730> our<00:07:34.120> Oracle<00:07:34.510> and<00:07:34.870> that<00:07:35.020> would 00:07:35.100 --> 00:07:35.110 align:start position:0% talk to our Oracle and that would 00:07:35.110 --> 00:07:36.480 align:start position:0% talk to our Oracle and that would generate<00:07:35.410> an<00:07:35.560> event<00:07:35.650> that<00:07:36.070> we<00:07:36.220> listen<00:07:36.400> to 00:07:36.480 --> 00:07:36.490 align:start position:0% generate an event that we listen to 00:07:36.490 --> 00:07:37.800 align:start position:0% generate an event that we listen to we've<00:07:36.910> got<00:07:37.000> a<00:07:37.030> load<00:07:37.210> of<00:07:37.240> sort<00:07:37.510> of<00:07:37.540> back-end 00:07:37.800 --> 00:07:37.810 align:start position:0% we've got a load of sort of back-end 00:07:37.810 --> 00:07:40.440 align:start position:0% we've got a load of sort of back-end stuff<00:07:38.140> listening<00:07:38.620> for<00:07:38.740> the<00:07:38.800> event<00:07:39.070> it<00:07:40.060> figures 00:07:40.440 --> 00:07:40.450 align:start position:0% stuff listening for the event it figures 00:07:40.450 --> 00:07:43.290 align:start position:0% stuff listening for the event it figures out<00:07:40.540> what<00:07:40.840> the<00:07:41.830> price<00:07:42.280> request<00:07:42.640> is<00:07:42.760> for<00:07:43.030> so 00:07:43.290 --> 00:07:43.300 align:start position:0% out what the price request is for so 00:07:43.300 --> 00:07:44.550 align:start position:0% out what the price request is for so there's<00:07:43.510> an<00:07:43.600> interest<00:07:43.870> rate<00:07:43.930> then<00:07:44.260> we<00:07:44.290> use<00:07:44.530> a 00:07:44.550 --> 00:07:44.560 align:start position:0% there's an interest rate then we use a 00:07:44.560 --> 00:07:48.000 align:start position:0% there's an interest rate then we use a standard<00:07:45.130> REST<00:07:45.340> API<00:07:45.490> to<00:07:46.270> talk<00:07:46.480> to<00:07:46.720> TR<00:07:47.590> electron 00:07:48.000 --> 00:07:48.010 align:start position:0% standard REST API to talk to TR electron 00:07:48.010 --> 00:07:49.770 align:start position:0% standard REST API to talk to TR electron which<00:07:48.130> is<00:07:48.250> up<00:07:48.370> there<00:07:48.520> pull<00:07:49.270> down<00:07:49.450> the<00:07:49.570> price 00:07:49.770 --> 00:07:49.780 align:start position:0% which is up there pull down the price 00:07:49.780 --> 00:07:52.020 align:start position:0% which is up there pull down the price send<00:07:50.650> it<00:07:50.770> back<00:07:50.950> to<00:07:51.190> the<00:07:51.400> blockchain<00:07:51.820> and 00:07:52.020 --> 00:07:52.030 align:start position:0% send it back to the blockchain and 00:07:52.030 --> 00:07:53.550 align:start position:0% send it back to the blockchain and update<00:07:52.450> the<00:07:52.570> smart<00:07:52.840> contact<00:07:53.140> with<00:07:53.320> the<00:07:53.380> data 00:07:53.550 --> 00:07:53.560 align:start position:0% update the smart contact with the data 00:07:53.560 --> 00:07:56.010 align:start position:0% update the smart contact with the data accordingly<00:07:54.100> there<00:07:54.880> is<00:07:55.030> a<00:07:55.060> slight<00:07:55.720> flaw 00:07:56.010 --> 00:07:56.020 align:start position:0% accordingly there is a slight flaw 00:07:56.020 --> 00:07:57.990 align:start position:0% accordingly there is a slight flaw within<00:07:56.290> this<00:07:56.560> scheme<00:07:56.860> as<00:07:57.160> things<00:07:57.460> stand<00:07:57.700> and 00:07:57.990 --> 00:07:58.000 align:start position:0% within this scheme as things stand and 00:07:58.000 --> 00:07:59.340 align:start position:0% within this scheme as things stand and that<00:07:58.090> is<00:07:58.240> as<00:07:58.420> soon<00:07:58.600> as<00:07:58.720> the<00:07:58.810> data<00:07:58.930> is<00:07:59.170> written 00:07:59.340 --> 00:07:59.350 align:start position:0% that is as soon as the data is written 00:07:59.350 --> 00:08:00.810 align:start position:0% that is as soon as the data is written to<00:07:59.530> the<00:07:59.710> blockchain<00:07:59.950> it<00:08:00.310> essentially<00:08:00.700> becomes 00:08:00.810 --> 00:08:00.820 align:start position:0% to the blockchain it essentially becomes 00:08:00.820 --> 00:08:02.910 align:start position:0% to the blockchain it essentially becomes sort<00:08:01.510> of<00:08:01.540> unbounded<00:08:02.140> and<00:08:02.350> actually<00:08:02.710> a<00:08:02.740> lot<00:08:02.890> of 00:08:02.910 --> 00:08:02.920 align:start position:0% sort of unbounded and actually a lot of 00:08:02.920 --> 00:08:04.740 align:start position:0% sort of unbounded and actually a lot of our<00:08:03.100> information<00:08:03.310> is<00:08:03.790> licensed<00:08:04.330> from<00:08:04.420> third 00:08:04.740 --> 00:08:04.750 align:start position:0% our information is licensed from third 00:08:04.750 --> 00:08:06.270 align:start position:0% our information is licensed from third parties<00:08:05.200> and<00:08:05.350> at<00:08:05.470> the<00:08:05.560> moment<00:08:05.860> we<00:08:05.980> can't 00:08:06.270 --> 00:08:06.280 align:start position:0% parties and at the moment we can't 00:08:06.280 --> 00:08:09.710 align:start position:0% parties and at the moment we can't necessarily<00:08:07.350> write<00:08:08.350> data<00:08:08.650> to<00:08:09.070> the<00:08:09.280> blockchain 00:08:09.710 --> 00:08:09.720 align:start position:0% necessarily write data to the blockchain 00:08:09.720 --> 00:08:13.200 align:start position:0% necessarily write data to the blockchain that<00:08:10.720> then<00:08:11.260> everyone<00:08:11.710> is<00:08:11.800> available<00:08:12.220> to<00:08:12.340> to 00:08:13.200 --> 00:08:13.210 align:start position:0% that then everyone is available to to 00:08:13.210 --> 00:08:14.940 align:start position:0% that then everyone is available to to see<00:08:13.390> so<00:08:13.870> we're<00:08:14.050> looking<00:08:14.320> very<00:08:14.350> closely<00:08:14.530> at 00:08:14.940 --> 00:08:14.950 align:start position:0% see so we're looking very closely at 00:08:14.950 --> 00:08:15.810 align:start position:0% see so we're looking very closely at some<00:08:15.130> of<00:08:15.220> the<00:08:15.280> privacy<00:08:15.580> preserving 00:08:15.810 --> 00:08:15.820 align:start position:0% some of the privacy preserving 00:08:15.820 --> 00:08:17.640 align:start position:0% some of the privacy preserving mechanisms<00:08:16.600> so<00:08:16.810> zero<00:08:17.080> knowledge<00:08:17.230> of<00:08:17.410> proofs 00:08:17.640 --> 00:08:17.650 align:start position:0% mechanisms so zero knowledge of proofs 00:08:17.650 --> 00:08:19.680 align:start position:0% mechanisms so zero knowledge of proofs and<00:08:17.890> homomorphic<00:08:18.370> encryption<00:08:18.490> and<00:08:19.030> some<00:08:19.600> of 00:08:19.680 --> 00:08:19.690 align:start position:0% and homomorphic encryption and some of 00:08:19.690 --> 00:08:21.540 align:start position:0% and homomorphic encryption and some of those<00:08:19.840> will<00:08:20.200> probably<00:08:20.710> be<00:08:20.890> necessary<00:08:21.460> to 00:08:21.540 --> 00:08:21.550 align:start position:0% those will probably be necessary to 00:08:21.550 --> 00:08:23.250 align:start position:0% those will probably be necessary to deploy<00:08:21.820> something<00:08:22.360> like<00:08:22.510> this<00:08:22.690> on<00:08:22.900> a<00:08:23.140> public 00:08:23.250 --> 00:08:23.260 align:start position:0% deploy something like this on a public 00:08:23.260 --> 00:08:26.850 align:start position:0% deploy something like this on a public chain 00:08:26.850 --> 00:08:26.860 align:start position:0% 00:08:26.860 --> 00:08:28.980 align:start position:0% and<00:08:27.220> here<00:08:27.520> is<00:08:27.759> some<00:08:28.150> solidity<00:08:28.630> which<00:08:28.870> you 00:08:28.980 --> 00:08:28.990 align:start position:0% and here is some solidity which you 00:08:28.990 --> 00:08:31.080 align:start position:0% and here is some solidity which you probably<00:08:29.320> can't<00:08:29.830> see<00:08:29.949> but<00:08:30.310> essentially<00:08:31.000> you 00:08:31.080 --> 00:08:31.090 align:start position:0% probably can't see but essentially you 00:08:31.090 --> 00:08:34.079 align:start position:0% probably can't see but essentially you can<00:08:31.210> import<00:08:31.479> this<00:08:31.720> as<00:08:32.200> a<00:08:32.740> solidity<00:08:33.339> file<00:08:33.669> and 00:08:34.079 --> 00:08:34.089 align:start position:0% can import this as a solidity file and 00:08:34.089 --> 00:08:36.149 align:start position:0% can import this as a solidity file and you<00:08:34.630> essentially<00:08:35.050> have<00:08:35.320> to<00:08:35.349> first<00:08:36.010> of<00:08:36.099> all 00:08:36.149 --> 00:08:36.159 align:start position:0% you essentially have to first of all 00:08:36.159 --> 00:08:39.209 align:start position:0% you essentially have to first of all make<00:08:36.219> a<00:08:36.700> request<00:08:37.089> and<00:08:37.570> in<00:08:38.500> this<00:08:38.680> line<00:08:38.950> here 00:08:39.209 --> 00:08:39.219 align:start position:0% make a request and in this line here 00:08:39.219 --> 00:08:42.000 align:start position:0% make a request and in this line here there<00:08:39.490> is<00:08:39.640> a<00:08:39.909> bytes<00:08:40.240> 32<00:08:40.750> object<00:08:41.560> called<00:08:41.740> a<00:08:41.770> Rik 00:08:42.000 --> 00:08:42.010 align:start position:0% there is a bytes 32 object called a Rik 00:08:42.010 --> 00:08:44.100 align:start position:0% there is a bytes 32 object called a Rik and<00:08:42.039> a<00:08:42.250> rink<00:08:42.459> is<00:08:42.580> a<00:08:42.610> Reuters<00:08:43.120> instrument<00:08:43.870> code 00:08:44.100 --> 00:08:44.110 align:start position:0% and a rink is a Reuters instrument code 00:08:44.110 --> 00:08:46.170 align:start position:0% and a rink is a Reuters instrument code and<00:08:44.500> that<00:08:44.890> is<00:08:45.010> essentially<00:08:45.370> the<00:08:45.550> identifier 00:08:46.170 --> 00:08:46.180 align:start position:0% and that is essentially the identifier 00:08:46.180 --> 00:08:47.699 align:start position:0% and that is essentially the identifier of<00:08:46.209> the<00:08:46.450> asset<00:08:46.810> that<00:08:46.959> you<00:08:47.080> would<00:08:47.260> you<00:08:47.589> would 00:08:47.699 --> 00:08:47.709 align:start position:0% of the asset that you would you would 00:08:47.709 --> 00:08:50.130 align:start position:0% of the asset that you would you would query<00:08:48.010> the<00:08:48.190> Oracle<00:08:48.580> form<00:08:48.820> you<00:08:49.750> also<00:08:49.870> need<00:08:50.110> to 00:08:50.130 --> 00:08:50.140 align:start position:0% query the Oracle form you also need to 00:08:50.140 --> 00:08:52.590 align:start position:0% query the Oracle form you also need to implement<00:08:50.560> a<00:08:50.860> function<00:08:51.310> called<00:08:51.790> on<00:08:52.000> Oracle 00:08:52.590 --> 00:08:52.600 align:start position:0% implement a function called on Oracle 00:08:52.600 --> 00:08:55.320 align:start position:0% implement a function called on Oracle response<00:08:53.020> and<00:08:53.320> on<00:08:53.920> Oracle<00:08:54.490> failure<00:08:54.880> and<00:08:55.120> then 00:08:55.320 --> 00:08:55.330 align:start position:0% response and on Oracle failure and then 00:08:55.330 --> 00:08:57.120 align:start position:0% response and on Oracle failure and then whatever<00:08:55.810> sort<00:08:56.170> of<00:08:56.200> business<00:08:56.410> logic<00:08:56.680> you<00:08:56.920> want 00:08:57.120 --> 00:08:57.130 align:start position:0% whatever sort of business logic you want 00:08:57.130 --> 00:08:59.220 align:start position:0% whatever sort of business logic you want your<00:08:57.339> your<00:08:57.760> for<00:08:58.149> example<00:08:58.570> your<00:08:58.959> your 00:08:59.220 --> 00:08:59.230 align:start position:0% your your for example your your 00:08:59.230 --> 00:09:01.010 align:start position:0% your your for example your your financial<00:08:59.589> asset<00:08:59.860> to<00:08:59.980> perform<00:09:00.370> on 00:09:01.010 --> 00:09:01.020 align:start position:0% financial asset to perform on 00:09:01.020 --> 00:09:03.930 align:start position:0% financial asset to perform on receivership<00:09:02.020> of<00:09:02.200> of<00:09:02.740> the<00:09:02.980> price<00:09:03.220> you<00:09:03.790> can 00:09:03.930 --> 00:09:03.940 align:start position:0% receivership of of the price you can 00:09:03.940 --> 00:09:05.540 align:start position:0% receivership of of the price you can implement<00:09:04.180> them 00:09:05.540 --> 00:09:05.550 align:start position:0% implement them 00:09:05.550 --> 00:09:07.550 align:start position:0% implement them and 00:09:07.550 --> 00:09:07.560 align:start position:0% and 00:09:07.560 --> 00:09:10.199 align:start position:0% and I<00:09:08.560> showed<00:09:09.130> that<00:09:09.160> there<00:09:09.430> was<00:09:09.520> a<00:09:09.550> rest<00:09:09.790> call<00:09:10.029> in 00:09:10.199 --> 00:09:10.209 align:start position:0% I showed that there was a rest call in 00:09:10.209 --> 00:09:11.940 align:start position:0% I showed that there was a rest call in that<00:09:10.330> process<00:09:10.570> so<00:09:10.750> this<00:09:10.990> is<00:09:11.110> the<00:09:11.320> sort<00:09:11.680> of<00:09:11.740> rest 00:09:11.940 --> 00:09:11.950 align:start position:0% that process so this is the sort of rest 00:09:11.950 --> 00:09:15.449 align:start position:0% that process so this is the sort of rest response<00:09:12.399> from<00:09:13.120> TR<00:09:14.080> electron<00:09:14.770> so<00:09:15.010> this<00:09:15.190> comes 00:09:15.449 --> 00:09:15.459 align:start position:0% response from TR electron so this comes 00:09:15.459 --> 00:09:17.280 align:start position:0% response from TR electron so this comes back<00:09:15.640> as<00:09:15.790> a<00:09:15.820> JSON<00:09:16.240> object<00:09:16.300> and<00:09:16.779> we<00:09:17.140> would 00:09:17.280 --> 00:09:17.290 align:start position:0% back as a JSON object and we would 00:09:17.290 --> 00:09:18.630 align:start position:0% back as a JSON object and we would essentially<00:09:17.560> take<00:09:17.709> this<00:09:17.980> information<00:09:18.520> out 00:09:18.630 --> 00:09:18.640 align:start position:0% essentially take this information out 00:09:18.640 --> 00:09:21.389 align:start position:0% essentially take this information out and<00:09:18.820> put<00:09:19.420> it<00:09:19.510> into<00:09:19.990> the<00:09:20.529> transaction<00:09:21.160> which 00:09:21.389 --> 00:09:21.399 align:start position:0% and put it into the transaction which 00:09:21.399 --> 00:09:24.480 align:start position:0% and put it into the transaction which cause<00:09:21.730> on<00:09:22.360> Oracle<00:09:23.020> response<00:09:23.440> and<00:09:23.740> you<00:09:24.190> can<00:09:24.339> see 00:09:24.480 --> 00:09:24.490 align:start position:0% cause on Oracle response and you can see 00:09:24.490 --> 00:09:25.650 align:start position:0% cause on Oracle response and you can see the<00:09:24.610> sort<00:09:24.790> of<00:09:24.850> thing<00:09:25.000> that's<00:09:25.149> in<00:09:25.270> here<00:09:25.420> so<00:09:25.570> the 00:09:25.650 --> 00:09:25.660 align:start position:0% the sort of thing that's in here so the 00:09:25.660 --> 00:09:27.180 align:start position:0% the sort of thing that's in here so the RIC<00:09:25.839> the<00:09:25.990> Reuters<00:09:26.170> instrument<00:09:26.680> code<00:09:26.890> which<00:09:27.040> is 00:09:27.180 --> 00:09:27.190 align:start position:0% RIC the Reuters instrument code which is 00:09:27.190 --> 00:09:28.710 align:start position:0% RIC the Reuters instrument code which is the<00:09:27.250> euro<00:09:27.640> so<00:09:27.970> that<00:09:28.089> would<00:09:28.180> be<00:09:28.270> the<00:09:28.360> price<00:09:28.540> of 00:09:28.710 --> 00:09:28.720 align:start position:0% the euro so that would be the price of 00:09:28.720 --> 00:09:31.199 align:start position:0% the euro so that would be the price of euro<00:09:28.959> in<00:09:29.140> dollars<00:09:29.560> a<00:09:30.190> lot<00:09:30.520> of<00:09:30.670> timestamp 00:09:31.199 --> 00:09:31.209 align:start position:0% euro in dollars a lot of timestamp 00:09:31.209 --> 00:09:34.170 align:start position:0% euro in dollars a lot of timestamp information<00:09:31.779> bid<00:09:32.740> to<00:09:32.920> ask<00:09:33.130> bid<00:09:33.640> asked<00:09:33.940> size 00:09:34.170 --> 00:09:34.180 align:start position:0% information bid to ask bid asked size 00:09:34.180 --> 00:09:38.300 align:start position:0% information bid to ask bid asked size and<00:09:34.480> a<00:09:34.839> multiplier<00:09:35.320> to<00:09:35.470> go<00:09:35.589> from<00:09:35.800> float<00:09:36.310> to<00:09:36.339> int 00:09:38.300 --> 00:09:38.310 align:start position:0% and a multiplier to go from float to int 00:09:38.310 --> 00:09:41.340 align:start position:0% and a multiplier to go from float to int okay<00:09:39.310> so<00:09:39.550> I'm<00:09:39.730> not<00:09:40.029> really<00:09:40.240> a<00:09:40.360> UI<00:09:40.720> or<00:09:41.020> UX 00:09:41.340 --> 00:09:41.350 align:start position:0% okay so I'm not really a UI or UX 00:09:41.350 --> 00:09:42.990 align:start position:0% okay so I'm not really a UI or UX developer<00:09:41.950> so<00:09:42.100> I've<00:09:42.220> put<00:09:42.490> this<00:09:42.580> together<00:09:42.760> just 00:09:42.990 --> 00:09:43.000 align:start position:0% developer so I've put this together just 00:09:43.000 --> 00:09:45.329 align:start position:0% developer so I've put this together just to<00:09:43.270> sort<00:09:43.420> of<00:09:43.480> demonstrate<00:09:43.810> functionality<00:09:44.800> but 00:09:45.329 --> 00:09:45.339 align:start position:0% to sort of demonstrate functionality but 00:09:45.339 --> 00:09:47.250 align:start position:0% to sort of demonstrate functionality but essentially<00:09:45.700> this<00:09:45.820> is<00:09:45.880> a<00:09:46.029> sort<00:09:46.870> of<00:09:46.900> trading 00:09:47.250 --> 00:09:47.260 align:start position:0% essentially this is a sort of trading 00:09:47.260 --> 00:09:50.400 align:start position:0% essentially this is a sort of trading system<00:09:47.589> for<00:09:47.910> contracts<00:09:48.910> for<00:09:49.029> difference<00:09:49.410> and 00:09:50.400 --> 00:09:50.410 align:start position:0% system for contracts for difference and 00:09:50.410 --> 00:09:52.829 align:start position:0% system for contracts for difference and so<00:09:50.680> at<00:09:50.950> the<00:09:51.070> top<00:09:51.220> we<00:09:51.490> would<00:09:51.670> have<00:09:51.850> an<00:09:52.360> order 00:09:52.829 --> 00:09:52.839 align:start position:0% so at the top we would have an order 00:09:52.839 --> 00:09:55.560 align:start position:0% so at the top we would have an order book<00:09:52.959> contract<00:09:53.589> you<00:09:54.430> would<00:09:54.640> send<00:09:54.940> orders<00:09:55.300> to 00:09:55.560 --> 00:09:55.570 align:start position:0% book contract you would send orders to 00:09:55.570 --> 00:09:58.170 align:start position:0% book contract you would send orders to that<00:09:55.600> order<00:09:56.170> book<00:09:56.320> when<00:09:56.830> the<00:09:56.860> orders<00:09:57.220> cross<00:09:57.520> a 00:09:58.170 --> 00:09:58.180 align:start position:0% that order book when the orders cross a 00:09:58.180 --> 00:10:01.079 align:start position:0% that order book when the orders cross a trade<00:09:59.080> is<00:09:59.290> entered<00:09:59.620> into<00:09:59.770> a<00:09:59.920> positions<00:10:00.670> table 00:10:01.079 --> 00:10:01.089 align:start position:0% trade is entered into a positions table 00:10:01.089 --> 00:10:03.780 align:start position:0% trade is entered into a positions table which<00:10:01.240> is<00:10:01.270> this<00:10:01.810> thing<00:10:02.440> here<00:10:02.860> I<00:10:02.890> think<00:10:03.100> I<00:10:03.580> can't 00:10:03.780 --> 00:10:03.790 align:start position:0% which is this thing here I think I can't 00:10:03.790 --> 00:10:06.090 align:start position:0% which is this thing here I think I can't even<00:10:03.970> see<00:10:04.150> it<00:10:04.209> from<00:10:04.300> it<00:10:04.560> and<00:10:05.560> the<00:10:05.680> positions 00:10:06.090 --> 00:10:06.100 align:start position:0% even see it from it and the positions 00:10:06.100 --> 00:10:07.920 align:start position:0% even see it from it and the positions table<00:10:06.459> is<00:10:06.550> what<00:10:06.730> deals<00:10:07.029> with<00:10:07.300> the<00:10:07.450> Oracle 00:10:07.920 --> 00:10:07.930 align:start position:0% table is what deals with the Oracle 00:10:07.930 --> 00:10:10.590 align:start position:0% table is what deals with the Oracle interface<00:10:08.290> so<00:10:08.650> these<00:10:09.480> contracts<00:10:10.480> of<00:10:10.540> a 00:10:10.590 --> 00:10:10.600 align:start position:0% interface so these contracts of a 00:10:10.600 --> 00:10:12.960 align:start position:0% interface so these contracts of a difference<00:10:10.870> are<00:10:10.990> linked<00:10:11.290> to<00:10:11.520> two<00:10:12.520> major 00:10:12.960 --> 00:10:12.970 align:start position:0% difference are linked to two major 00:10:12.970 --> 00:10:15.180 align:start position:0% difference are linked to two major indices<00:10:13.510> so<00:10:13.779> the<00:10:13.870> footsie<00:10:14.170> 100<00:10:14.320> for<00:10:14.709> example 00:10:15.180 --> 00:10:15.190 align:start position:0% indices so the footsie 100 for example 00:10:15.190 --> 00:10:18.210 align:start position:0% indices so the footsie 100 for example and<00:10:16.029> from<00:10:16.300> that<00:10:16.420> point<00:10:16.630> on<00:10:16.810> the<00:10:17.170> Oracle<00:10:17.829> would 00:10:18.210 --> 00:10:18.220 align:start position:0% and from that point on the Oracle would 00:10:18.220 --> 00:10:21.690 align:start position:0% and from that point on the Oracle would send<00:10:19.209> updates<00:10:19.839> and<00:10:20.260> we<00:10:20.829> have<00:10:20.950> a<00:10:20.980> scheduling 00:10:21.690 --> 00:10:21.700 align:start position:0% send updates and we have a scheduling 00:10:21.700 --> 00:10:23.220 align:start position:0% send updates and we have a scheduling service<00:10:22.089> as<00:10:22.209> well<00:10:22.390> so<00:10:22.570> you<00:10:22.660> can<00:10:22.779> shed<00:10:22.990> your 00:10:23.220 --> 00:10:23.230 align:start position:0% service as well so you can shed your 00:10:23.230 --> 00:10:25.319 align:start position:0% service as well so you can shed your every<00:10:23.770> block<00:10:24.070> or<00:10:24.279> every<00:10:24.520> minute<00:10:24.850> or<00:10:25.000> whatever 00:10:25.319 --> 00:10:25.329 align:start position:0% every block or every minute or whatever 00:10:25.329 --> 00:10:27.060 align:start position:0% every block or every minute or whatever sort<00:10:25.600> of<00:10:25.630> granularity<00:10:26.050> you're<00:10:26.500> interested<00:10:26.920> in 00:10:27.060 --> 00:10:27.070 align:start position:0% sort of granularity you're interested in 00:10:27.070 --> 00:10:29.760 align:start position:0% sort of granularity you're interested in this<00:10:27.940> data<00:10:28.209> comes<00:10:28.510> back<00:10:28.600> and<00:10:28.990> you<00:10:29.260> can<00:10:29.410> see<00:10:29.620> in 00:10:29.760 --> 00:10:29.770 align:start position:0% this data comes back and you can see in 00:10:29.770 --> 00:10:33.300 align:start position:0% this data comes back and you can see in in<00:10:30.310> the<00:10:30.490> logging<00:10:30.720> panel<00:10:31.720> the<00:10:32.709> events<00:10:33.070> are 00:10:33.300 --> 00:10:33.310 align:start position:0% in the logging panel the events are 00:10:33.310 --> 00:10:35.250 align:start position:0% in the logging panel the events are written<00:10:33.970> out<00:10:34.060> and<00:10:34.300> this<00:10:34.450> is<00:10:34.510> used<00:10:34.870> to<00:10:35.050> update 00:10:35.250 --> 00:10:35.260 align:start position:0% written out and this is used to update 00:10:35.260 --> 00:10:37.980 align:start position:0% written out and this is used to update the<00:10:35.770> data<00:10:36.010> and<00:10:36.880> you<00:10:37.000> can<00:10:37.180> see<00:10:37.329> the<00:10:37.480> change<00:10:37.750> in 00:10:37.980 --> 00:10:37.990 align:start position:0% the data and you can see the change in 00:10:37.990 --> 00:10:41.329 align:start position:0% the data and you can see the change in the<00:10:38.079> value<00:10:38.440> of<00:10:38.800> these<00:10:38.950> trades 00:10:41.329 --> 00:10:41.339 align:start position:0% the value of these trades 00:10:41.339 --> 00:10:44.360 align:start position:0% the value of these trades there<00:10:42.339> is<00:10:42.519> the<00:10:42.730> the<00:10:42.970> possibility<00:10:43.570> to 00:10:44.360 --> 00:10:44.370 align:start position:0% there is the the possibility to 00:10:44.370 --> 00:10:46.680 align:start position:0% there is the the possibility to implement<00:10:45.370> things<00:10:45.670> like<00:10:45.880> a<00:10:46.060> meaning<00:10:46.420> in<00:10:46.570> this 00:10:46.680 --> 00:10:46.690 align:start position:0% implement things like a meaning in this 00:10:46.690 --> 00:10:47.880 align:start position:0% implement things like a meaning in this example<00:10:47.080> actually<00:10:47.320> there<00:10:47.649> were<00:10:47.709> some 00:10:47.880 --> 00:10:47.890 align:start position:0% example actually there were some 00:10:47.890 --> 00:10:49.530 align:start position:0% example actually there were some implementations<00:10:48.580> of<00:10:48.670> things<00:10:48.880> called<00:10:49.120> uh<00:10:49.269> stop 00:10:49.530 --> 00:10:49.540 align:start position:0% implementations of things called uh stop 00:10:49.540 --> 00:10:51.420 align:start position:0% implementations of things called uh stop losses<00:10:49.750> over<00:10:50.200> trade<00:10:50.529> drops<00:10:51.040> below<00:10:51.220> a<00:10:51.339> certain 00:10:51.420 --> 00:10:51.430 align:start position:0% losses over trade drops below a certain 00:10:51.430 --> 00:10:53.250 align:start position:0% losses over trade drops below a certain level<00:10:51.850> so<00:10:52.120> if<00:10:52.180> it<00:10:52.300> drops<00:10:52.450> below<00:10:52.600> five<00:10:52.930> percent 00:10:53.250 --> 00:10:53.260 align:start position:0% level so if it drops below five percent 00:10:53.260 --> 00:10:55.410 align:start position:0% level so if it drops below five percent of<00:10:53.350> its<00:10:53.470> value<00:10:53.529> it<00:10:54.220> is<00:10:54.459> closed<00:10:54.790> automatically 00:10:55.410 --> 00:10:55.420 align:start position:0% of its value it is closed automatically 00:10:55.420 --> 00:10:58.019 align:start position:0% of its value it is closed automatically and<00:10:55.930> similarly<00:10:56.500> if<00:10:56.560> it<00:10:56.649> if<00:10:57.010> it<00:10:57.130> rises<00:10:57.399> above<00:10:57.790> a 00:10:58.019 --> 00:10:58.029 align:start position:0% and similarly if it if it rises above a 00:10:58.029 --> 00:11:00.030 align:start position:0% and similarly if it if it rises above a five<00:10:58.390> percent<00:10:58.750> of<00:10:58.870> its<00:10:59.019> original<00:10:59.079> level<00:10:59.649> you 00:11:00.030 --> 00:11:00.040 align:start position:0% five percent of its original level you 00:11:00.040 --> 00:11:01.829 align:start position:0% five percent of its original level you might<00:11:00.220> close<00:11:00.459> that<00:11:00.700> and<00:11:00.820> take<00:11:00.970> the<00:11:01.060> profit<00:11:01.450> so 00:11:01.829 --> 00:11:01.839 align:start position:0% might close that and take the profit so 00:11:01.839 --> 00:11:03.000 align:start position:0% might close that and take the profit so that's<00:11:02.019> the<00:11:02.140> sort<00:11:02.320> of<00:11:02.380> functionality<00:11:02.769> that 00:11:03.000 --> 00:11:03.010 align:start position:0% that's the sort of functionality that 00:11:03.010 --> 00:11:04.590 align:start position:0% that's the sort of functionality that you<00:11:03.220> can<00:11:03.459> implement<00:11:03.760> in<00:11:04.060> that<00:11:04.209> sort<00:11:04.420> of<00:11:04.450> on 00:11:04.590 --> 00:11:04.600 align:start position:0% you can implement in that sort of on 00:11:04.600 --> 00:11:07.970 align:start position:0% you can implement in that sort of on Oracle<00:11:05.200> response<00:11:05.649> function 00:11:07.970 --> 00:11:07.980 align:start position:0% Oracle response function 00:11:07.980 --> 00:11:10.530 align:start position:0% Oracle response function okay<00:11:08.980> so<00:11:09.010> just<00:11:09.430> a<00:11:09.490> little<00:11:09.610> change<00:11:10.000> of<00:11:10.120> tack<00:11:10.390> now 00:11:10.530 --> 00:11:10.540 align:start position:0% okay so just a little change of tack now 00:11:10.540 --> 00:11:11.759 align:start position:0% okay so just a little change of tack now so<00:11:10.779> that's<00:11:10.930> some<00:11:11.110> of<00:11:11.140> the<00:11:11.230> stuff<00:11:11.290> that<00:11:11.500> we're 00:11:11.759 --> 00:11:11.769 align:start position:0% so that's some of the stuff that we're 00:11:11.769 --> 00:11:13.680 align:start position:0% so that's some of the stuff that we're doing<00:11:12.010> internally<00:11:12.519> that's<00:11:12.850> all<00:11:13.029> sort<00:11:13.300> of<00:11:13.329> very 00:11:13.680 --> 00:11:13.690 align:start position:0% doing internally that's all sort of very 00:11:13.690 --> 00:11:16.440 align:start position:0% doing internally that's all sort of very much<00:11:13.810> under<00:11:14.290> test<00:11:15.029> we<00:11:16.029> had<00:11:16.209> some<00:11:16.360> good 00:11:16.440 --> 00:11:16.450 align:start position:0% much under test we had some good 00:11:16.450 --> 00:11:17.790 align:start position:0% much under test we had some good feedback<00:11:16.660> from<00:11:16.899> the<00:11:17.050> etherium<00:11:17.380> foundation 00:11:17.790 --> 00:11:17.800 align:start position:0% feedback from the etherium foundation 00:11:17.800 --> 00:11:20.610 align:start position:0% feedback from the etherium foundation guys<00:11:18.029> about<00:11:19.029> ten<00:11:19.300> days<00:11:19.390> ago<00:11:19.600> when<00:11:20.290> we<00:11:20.440> held 00:11:20.610 --> 00:11:20.620 align:start position:0% guys about ten days ago when we held 00:11:20.620 --> 00:11:22.949 align:start position:0% guys about ten days ago when we held this<00:11:20.769> hackathon<00:11:21.130> which<00:11:21.610> is<00:11:21.820> we<00:11:22.480> thought<00:11:22.690> quite 00:11:22.949 --> 00:11:22.959 align:start position:0% this hackathon which is we thought quite 00:11:22.959 --> 00:11:25.079 align:start position:0% this hackathon which is we thought quite cleverly<00:11:23.290> named<00:11:23.529> eff<00:11:23.980> font<00:11:24.250> so<00:11:24.550> we<00:11:24.730> held<00:11:24.940> this 00:11:25.079 --> 00:11:25.089 align:start position:0% cleverly named eff font so we held this 00:11:25.089 --> 00:11:27.329 align:start position:0% cleverly named eff font so we held this in<00:11:25.320> collaboration<00:11:26.320> with<00:11:26.560> the<00:11:26.980> etherium 00:11:27.329 --> 00:11:27.339 align:start position:0% in collaboration with the etherium 00:11:27.339 --> 00:11:29.730 align:start position:0% in collaboration with the etherium foundation<00:11:27.930> many<00:11:28.930> thanks<00:11:29.140> to<00:11:29.170> George<00:11:29.470> for 00:11:29.730 --> 00:11:29.740 align:start position:0% foundation many thanks to George for 00:11:29.740 --> 00:11:31.170 align:start position:0% foundation many thanks to George for helping<00:11:29.980> out<00:11:30.100> with<00:11:30.130> the<00:11:30.310> organizational<00:11:30.940> side 00:11:31.170 --> 00:11:31.180 align:start position:0% helping out with the organizational side 00:11:31.180 --> 00:11:32.970 align:start position:0% helping out with the organizational side of<00:11:31.300> things<00:11:31.510> and<00:11:31.779> we<00:11:32.230> had<00:11:32.350> a<00:11:32.380> lot<00:11:32.620> of<00:11:32.649> the 00:11:32.970 --> 00:11:32.980 align:start position:0% of things and we had a lot of the 00:11:32.980 --> 00:11:35.370 align:start position:0% of things and we had a lot of the etherium<00:11:33.490> guys<00:11:33.700> down<00:11:34.000> as<00:11:34.180> mentors<00:11:34.630> and<00:11:34.990> judges 00:11:35.370 --> 00:11:35.380 align:start position:0% etherium guys down as mentors and judges 00:11:35.380 --> 00:11:38.880 align:start position:0% etherium guys down as mentors and judges as<00:11:35.560> well<00:11:36.240> so<00:11:37.240> we<00:11:37.360> had<00:11:37.510> a<00:11:37.810> slightly<00:11:38.680> unusual 00:11:38.880 --> 00:11:38.890 align:start position:0% as well so we had a slightly unusual 00:11:38.890 --> 00:11:41.960 align:start position:0% as well so we had a slightly unusual format<00:11:39.579> to<00:11:39.790> this<00:11:40.079> next<00:11:41.079> slide<00:11:41.140> please<00:11:41.380> we<00:11:41.709> had 00:11:41.960 --> 00:11:41.970 align:start position:0% format to this next slide please we had 00:11:41.970 --> 00:11:45.960 align:start position:0% format to this next slide please we had speakers<00:11:42.970> on<00:11:43.920> all<00:11:44.920> three<00:11:45.220> days<00:11:45.399> so<00:11:45.730> we've 00:11:45.960 --> 00:11:45.970 align:start position:0% speakers on all three days so we've 00:11:45.970 --> 00:11:47.940 align:start position:0% speakers on all three days so we've heard<00:11:46.149> from<00:11:46.240> Thomas<00:11:46.660> we've<00:11:47.500> heard<00:11:47.680> from<00:11:47.770> Peter 00:11:47.940 --> 00:11:47.950 align:start position:0% heard from Thomas we've heard from Peter 00:11:47.950 --> 00:11:49.470 align:start position:0% heard from Thomas we've heard from Peter Thomas<00:11:48.279> was<00:11:48.399> talking<00:11:48.490> about<00:11:48.670> Oracle's<00:11:49.209> Peter 00:11:49.470 --> 00:11:49.480 align:start position:0% Thomas was talking about Oracle's Peter 00:11:49.480 --> 00:11:50.850 align:start position:0% Thomas was talking about Oracle's Peter was<00:11:49.690> talking<00:11:49.959> about<00:11:49.990> elaborate<00:11:50.500> ways<00:11:50.649> of 00:11:50.850 --> 00:11:50.860 align:start position:0% was talking about elaborate ways of 00:11:50.860 --> 00:11:53.519 align:start position:0% was talking about elaborate ways of breaking<00:11:51.310> smart<00:11:51.970> contracts<00:11:52.480> I<00:11:52.630> mean<00:11:53.110> had<00:11:53.230> Jack 00:11:53.519 --> 00:11:53.529 align:start position:0% breaking smart contracts I mean had Jack 00:11:53.529 --> 00:11:57.510 align:start position:0% breaking smart contracts I mean had Jack Gavigan<00:11:53.950> from<00:11:54.279> Zed<00:11:54.850> cash<00:11:55.060> or<00:11:55.360> Z<00:11:55.810> cash<00:11:56.520> talking 00:11:57.510 --> 00:11:57.520 align:start position:0% Gavigan from Zed cash or Z cash talking 00:11:57.520 --> 00:11:58.860 align:start position:0% Gavigan from Zed cash or Z cash talking about<00:11:57.700> things<00:11:57.910> like<00:11:58.060> zero<00:11:58.209> knowledge<00:11:58.420> proves 00:11:58.860 --> 00:11:58.870 align:start position:0% about things like zero knowledge proves 00:11:58.870 --> 00:12:00.690 align:start position:0% about things like zero knowledge proves and<00:11:59.170> this<00:11:59.620> is<00:11:59.740> probably<00:11:59.920> my<00:12:00.160> favorite<00:12:00.190> slide 00:12:00.690 --> 00:12:00.700 align:start position:0% and this is probably my favorite slide 00:12:00.700 --> 00:12:02.040 align:start position:0% and this is probably my favorite slide but<00:12:00.880> you<00:12:00.910> probably<00:12:01.120> can't<00:12:01.450> quite<00:12:01.660> make<00:12:01.810> it<00:12:01.870> out 00:12:02.040 --> 00:12:02.050 align:start position:0% but you probably can't quite make it out 00:12:02.050 --> 00:12:03.960 align:start position:0% but you probably can't quite make it out we<00:12:02.230> managed<00:12:02.709> to<00:12:02.770> get<00:12:03.040> control<00:12:03.310> of<00:12:03.430> the<00:12:03.640> Thomson 00:12:03.960 --> 00:12:03.970 align:start position:0% we managed to get control of the Thomson 00:12:03.970 --> 00:12:06.090 align:start position:0% we managed to get control of the Thomson Reuters<00:12:04.089> news<00:12:04.329> ticker<00:12:04.839> and<00:12:05.560> just<00:12:05.770> to<00:12:05.860> show<00:12:06.040> you 00:12:06.090 --> 00:12:06.100 align:start position:0% Reuters news ticker and just to show you 00:12:06.100 --> 00:12:07.829 align:start position:0% Reuters news ticker and just to show you the<00:12:06.250> global<00:12:06.520> importance<00:12:07.180> of<00:12:07.450> this<00:12:07.690> hackathon 00:12:07.829 --> 00:12:07.839 align:start position:0% the global importance of this hackathon 00:12:07.839 --> 00:12:09.930 align:start position:0% the global importance of this hackathon it<00:12:08.230> was<00:12:08.350> sort<00:12:08.800> of<00:12:08.860> juxtaposed<00:12:09.459> against<00:12:09.820> the 00:12:09.930 --> 00:12:09.940 align:start position:0% it was sort of juxtaposed against the 00:12:09.940 --> 00:12:11.310 align:start position:0% it was sort of juxtaposed against the news<00:12:10.089> story<00:12:10.360> of<00:12:10.420> the<00:12:10.510> day<00:12:10.690> which<00:12:10.899> was<00:12:11.050> North 00:12:11.310 --> 00:12:11.320 align:start position:0% news story of the day which was North 00:12:11.320 --> 00:12:14.130 align:start position:0% news story of the day which was North Korea<00:12:11.680> nuclear<00:12:12.279> test<00:12:12.790> so<00:12:13.540> we<00:12:13.750> were<00:12:13.870> we<00:12:14.050> were 00:12:14.130 --> 00:12:14.140 align:start position:0% Korea nuclear test so we were we were 00:12:14.140 --> 00:12:15.920 align:start position:0% Korea nuclear test so we were we were quite<00:12:14.320> fortunate<00:12:14.350> to<00:12:14.920> get<00:12:15.040> control<00:12:15.399> of<00:12:15.430> that 00:12:15.920 --> 00:12:15.930 align:start position:0% quite fortunate to get control of that 00:12:15.930 --> 00:12:19.170 align:start position:0% quite fortunate to get control of that we<00:12:16.930> had<00:12:17.110> two<00:12:17.890> main<00:12:18.070> challenges<00:12:18.339> so<00:12:18.880> the<00:12:19.000> first 00:12:19.170 --> 00:12:19.180 align:start position:0% we had two main challenges so the first 00:12:19.180 --> 00:12:22.260 align:start position:0% we had two main challenges so the first one<00:12:19.420> was<00:12:19.690> data<00:12:20.200> driven<00:12:20.410> smart<00:12:20.890> contracts<00:12:21.459> and 00:12:22.260 --> 00:12:22.270 align:start position:0% one was data driven smart contracts and 00:12:22.270 --> 00:12:23.880 align:start position:0% one was data driven smart contracts and the<00:12:22.360> winning<00:12:22.630> team<00:12:22.839> was<00:12:23.170> essentially<00:12:23.680> a<00:12:23.709> sort 00:12:23.880 --> 00:12:23.890 align:start position:0% the winning team was essentially a sort 00:12:23.890 --> 00:12:27.900 align:start position:0% the winning team was essentially a sort of<00:12:23.920> crack<00:12:24.220> or<00:12:24.940> pro<00:12:25.810> team<00:12:26.800> from<00:12:26.980> BNP<00:12:27.430> Paribas 00:12:27.900 --> 00:12:27.910 align:start position:0% of crack or pro team from BNP Paribas 00:12:27.910 --> 00:12:31.519 align:start position:0% of crack or pro team from BNP Paribas and<00:12:28.240> they<00:12:28.300> put<00:12:28.510> together<00:12:28.600> a<00:12:29.160> fantasy<00:12:30.160> football 00:12:31.519 --> 00:12:31.529 align:start position:0% and they put together a fantasy football 00:12:31.529 --> 00:12:34.319 align:start position:0% and they put together a fantasy football DAP<00:12:32.529> I<00:12:33.010> think<00:12:33.399> it<00:12:33.490> was<00:12:33.610> called<00:12:33.760> fantasy 00:12:34.319 --> 00:12:34.329 align:start position:0% DAP I think it was called fantasy 00:12:34.329 --> 00:12:36.840 align:start position:0% DAP I think it was called fantasy football<00:12:35.050> so<00:12:35.260> it's<00:12:35.410> a<00:12:35.500> more<00:12:35.709> eff<00:12:35.949> play<00:12:36.699> I 00:12:36.840 --> 00:12:36.850 align:start position:0% football so it's a more eff play I 00:12:36.850 --> 00:12:39.180 align:start position:0% football so it's a more eff play I suppose<00:12:37.149> so<00:12:37.839> forgot<00:12:38.230> congrats<00:12:38.680> to<00:12:38.769> those<00:12:38.920> guys 00:12:39.180 --> 00:12:39.190 align:start position:0% suppose so forgot congrats to those guys 00:12:39.190 --> 00:12:42.509 align:start position:0% suppose so forgot congrats to those guys who<00:12:39.519> won<00:12:39.910> the<00:12:40.029> overall<00:12:40.240> prize<00:12:41.070> the<00:12:42.070> etherium 00:12:42.509 --> 00:12:42.519 align:start position:0% who won the overall prize the etherium 00:12:42.519 --> 00:12:45.449 align:start position:0% who won the overall prize the etherium smart<00:12:42.880> contract<00:12:43.269> security<00:12:43.810> challenge<00:12:44.470> post 00:12:45.449 --> 00:12:45.459 align:start position:0% smart contract security challenge post 00:12:45.459 --> 00:12:48.180 align:start position:0% smart contract security challenge post my<00:12:45.730> aetherium<00:12:46.209> that<00:12:47.170> was<00:12:47.320> won<00:12:47.500> by<00:12:47.529> a<00:12:48.130> team 00:12:48.180 --> 00:12:48.190 align:start position:0% my aetherium that was won by a team 00:12:48.190 --> 00:12:50.310 align:start position:0% my aetherium that was won by a team called<00:12:48.699> truth<00:12:49.060> of<00:12:49.329> state<00:12:49.660> and<00:12:49.899> I<00:12:49.959> think<00:12:50.140> some 00:12:50.310 --> 00:12:50.320 align:start position:0% called truth of state and I think some 00:12:50.320 --> 00:12:53.040 align:start position:0% called truth of state and I think some of<00:12:50.410> those<00:12:50.500> guys<00:12:50.829> are<00:12:50.860> here<00:12:51.160> today<00:12:51.790> a<00:12:51.820> wave<00:12:52.720> if 00:12:53.040 --> 00:12:53.050 align:start position:0% of those guys are here today a wave if 00:12:53.050 --> 00:12:54.890 align:start position:0% of those guys are here today a wave if you're<00:12:53.200> here<00:12:53.380> there's<00:12:53.620> a<00:12:53.680> wave<00:12:54.040> over<00:12:54.220> there 00:12:54.890 --> 00:12:54.900 align:start position:0% you're here there's a wave over there 00:12:54.900 --> 00:12:57.740 align:start position:0% you're here there's a wave over there and<00:12:55.900> we<00:12:56.110> had<00:12:56.260> a<00:12:56.290> runner<00:12:56.530> up<00:12:56.710> team 00:12:57.740 --> 00:12:57.750 align:start position:0% and we had a runner up team 00:12:57.750 --> 00:13:01.320 align:start position:0% and we had a runner up team and<00:12:58.750> I<00:12:59.740> command<00:13:00.550> what<00:13:00.670> they're<00:13:00.790> called<00:13:00.970> bounty 00:13:01.320 --> 00:13:01.330 align:start position:0% and I command what they're called bounty 00:13:01.330 --> 00:13:03.690 align:start position:0% and I command what they're called bounty max<00:13:01.540> so<00:13:01.720> this<00:13:01.750> was<00:13:02.020> about<00:13:02.290> providing<00:13:02.800> a<00:13:03.100> bounty 00:13:03.690 --> 00:13:03.700 align:start position:0% max so this was about providing a bounty 00:13:03.700 --> 00:13:07.320 align:start position:0% max so this was about providing a bounty for<00:13:04.230> smart<00:13:05.230> contract<00:13:05.590> exploits<00:13:06.130> and<00:13:06.880> that<00:13:07.150> was 00:13:07.320 --> 00:13:07.330 align:start position:0% for smart contract exploits and that was 00:13:07.330 --> 00:13:09.180 align:start position:0% for smart contract exploits and that was that<00:13:07.870> was<00:13:08.020> deemed<00:13:08.230> the<00:13:08.350> runner-up<00:13:08.740> prize<00:13:08.980> and 00:13:09.180 --> 00:13:09.190 align:start position:0% that was deemed the runner-up prize and 00:13:09.190 --> 00:13:10.740 align:start position:0% that was deemed the runner-up prize and I<00:13:09.250> think<00:13:09.430> those<00:13:09.550> guys<00:13:09.790> are<00:13:09.970> here<00:13:10.090> as<00:13:10.240> well<00:13:10.450> so 00:13:10.740 --> 00:13:10.750 align:start position:0% I think those guys are here as well so 00:13:10.750 --> 00:13:12.770 align:start position:0% I think those guys are here as well so congrats<00:13:11.080> to<00:13:11.350> those<00:13:11.950> guys 00:13:12.770 --> 00:13:12.780 align:start position:0% congrats to those guys 00:13:12.780 --> 00:13:16.590 align:start position:0% congrats to those guys so<00:13:13.780> just<00:13:14.020> one<00:13:14.350> more<00:13:14.380> I<00:13:14.710> think<00:13:14.890> so<00:13:15.640> that<00:13:16.120> was<00:13:16.390> a 00:13:16.590 --> 00:13:16.600 align:start position:0% so just one more I think so that was a 00:13:16.600 --> 00:13:19.200 align:start position:0% so just one more I think so that was a lot<00:13:16.780> of<00:13:16.840> fun<00:13:17.110> we've<00:13:17.380> really<00:13:17.590> enjoyed<00:13:17.860> that<00:13:18.210> and 00:13:19.200 --> 00:13:19.210 align:start position:0% lot of fun we've really enjoyed that and 00:13:19.210 --> 00:13:20.580 align:start position:0% lot of fun we've really enjoyed that and we<00:13:19.330> can<00:13:19.450> hold<00:13:19.600> another<00:13:19.750> one<00:13:19.930> in<00:13:20.050> Switzerland 00:13:20.580 --> 00:13:20.590 align:start position:0% we can hold another one in Switzerland 00:13:20.590 --> 00:13:24.210 align:start position:0% we can hold another one in Switzerland at<00:13:20.830> our<00:13:21.100> head<00:13:21.960> koffice<00:13:22.960> there<00:13:23.170> in<00:13:23.410> bars<00:13:23.890> that's 00:13:24.210 --> 00:13:24.220 align:start position:0% at our head koffice there in bars that's 00:13:24.220 --> 00:13:27.810 align:start position:0% at our head koffice there in bars that's going<00:13:24.400> to<00:13:24.460> be<00:13:24.550> January<00:13:25.180> 27th<00:13:25.810> to<00:13:25.990> 29th<00:13:26.790> again<00:13:27.790> a 00:13:27.810 --> 00:13:27.820 align:start position:0% going to be January 27th to 29th again a 00:13:27.820 --> 00:13:29.850 align:start position:0% going to be January 27th to 29th again a theory<00:13:28.150> and<00:13:28.300> based<00:13:28.510> with<00:13:29.470> the<00:13:29.560> theorem 00:13:29.850 --> 00:13:29.860 align:start position:0% theory and based with the theorem 00:13:29.860 --> 00:13:32.460 align:start position:0% theory and based with the theorem foundation<00:13:30.280> guys<00:13:30.490> helping<00:13:30.910> out<00:13:31.470> more 00:13:32.460 --> 00:13:32.470 align:start position:0% foundation guys helping out more 00:13:32.470 --> 00:13:34.350 align:start position:0% foundation guys helping out more sponsors<00:13:33.010> and<00:13:33.220> some<00:13:33.400> dated<00:13:33.700> providers<00:13:34.090> to<00:13:34.240> be 00:13:34.350 --> 00:13:34.360 align:start position:0% sponsors and some dated providers to be 00:13:34.360 --> 00:13:36.810 align:start position:0% sponsors and some dated providers to be added<00:13:34.720> in<00:13:34.900> future<00:13:35.230> and<00:13:36.040> details<00:13:36.400> about<00:13:36.550> that 00:13:36.810 --> 00:13:36.820 align:start position:0% added in future and details about that 00:13:36.820 --> 00:13:38.400 align:start position:0% added in future and details about that will<00:13:37.000> be<00:13:37.120> made<00:13:37.540> available<00:13:37.570> through<00:13:38.110> the<00:13:38.290> usual 00:13:38.400 --> 00:13:38.410 align:start position:0% will be made available through the usual 00:13:38.410 --> 00:13:39.200 align:start position:0% will be made available through the usual channels 00:13:39.200 --> 00:13:39.210 align:start position:0% channels 00:13:39.210 --> 00:13:42.650 align:start position:0% channels ok<00:13:40.210> and<00:13:40.450> that's<00:13:40.900> it<00:13:40.990> thanks 00:13:42.650 --> 00:13:42.660 align:start position:0% ok and that's it thanks 00:13:42.660 --> 00:13:46.300 align:start position:0% ok and that's it thanks [Applause] 00:13:46.300 --> 00:13:46.310 align:start position:0% [Applause] 00:13:46.310 --> 00:13:53.660 align:start position:0% [Applause] [Music]