WEBVTT Kind: captions Language: en 00:00:00.510 --> 00:00:17.910 align:start position:0% [Music] 00:00:17.910 --> 00:00:17.920 align:start position:0% [Music] 00:00:17.920 --> 00:00:21.950 align:start position:0% [Music] so<00:00:18.520> as<00:00:18.640> you<00:00:18.800> all<00:00:19.400> know<00:00:20.400> Microsoft<00:00:21.400> is<00:00:21.600> our 00:00:21.950 --> 00:00:21.960 align:start position:0% so as you all know Microsoft is our 00:00:21.960 --> 00:00:25.349 align:start position:0% so as you all know Microsoft is our Premier<00:00:22.760> U<00:00:22.920> Premier<00:00:23.359> sponsor<00:00:23.800> of<00:00:24.000> Devcon<00:00:24.480> 2 00:00:25.349 --> 00:00:25.359 align:start position:0% Premier U Premier sponsor of Devcon 2 00:00:25.359 --> 00:00:28.470 align:start position:0% Premier U Premier sponsor of Devcon 2 and<00:00:25.519> Marley<00:00:26.000> gray<00:00:26.800> who<00:00:27.000> is<00:00:27.400> of<00:00:27.840> uh<00:00:27.960> blockchain 00:00:28.470 --> 00:00:28.480 align:start position:0% and Marley gray who is of uh blockchain 00:00:28.480 --> 00:00:30.429 align:start position:0% and Marley gray who is of uh blockchain engineering<00:00:29.279> and<00:00:29.439> the<00:00:29.599> head<00:00:29.720> of<00:00:30.039> blockchain 00:00:30.429 --> 00:00:30.439 align:start position:0% engineering and the head of blockchain 00:00:30.439 --> 00:00:33.950 align:start position:0% engineering and the head of blockchain engineerings<00:00:31.119> is<00:00:31.359> here<00:00:32.200> to<00:00:32.920> uh<00:00:33.160> both<00:00:33.440> speak 00:00:33.950 --> 00:00:33.960 align:start position:0% engineerings is here to uh both speak 00:00:33.960 --> 00:00:37.150 align:start position:0% engineerings is here to uh both speak and<00:00:34.239> give<00:00:34.520> an<00:00:35.200> introduction 00:00:37.150 --> 00:00:37.160 align:start position:0% and give an introduction 00:00:37.160 --> 00:00:40.869 align:start position:0% and give an introduction um<00:00:38.160> and<00:00:38.600> come<00:00:38.719> on<00:00:38.879> up<00:00:39.200> Marley<00:00:40.200> give<00:00:40.360> a<00:00:40.520> hand<00:00:40.680> for 00:00:40.869 --> 00:00:40.879 align:start position:0% um and come on up Marley give a hand for 00:00:40.879 --> 00:00:44.029 align:start position:0% um and come on up Marley give a hand for Marley<00:00:41.280> gray<00:00:41.640> please 00:00:44.029 --> 00:00:44.039 align:start position:0% Marley gray please 00:00:44.039 --> 00:00:46.200 align:start position:0% Marley gray please Microsoft<00:00:45.039> thanks 00:00:46.200 --> 00:00:46.210 align:start position:0% Microsoft thanks 00:00:46.210 --> 00:00:49.389 align:start position:0% Microsoft thanks [Applause] 00:00:49.389 --> 00:00:49.399 align:start position:0% 00:00:49.399 --> 00:00:51.189 align:start position:0% me<00:00:50.399> good 00:00:51.189 --> 00:00:51.199 align:start position:0% me good 00:00:51.199 --> 00:00:53.510 align:start position:0% me good morning<00:00:52.199> I<00:00:52.280> think<00:00:52.399> I<00:00:52.520> should<00:00:52.719> thank<00:00:52.960> Roman<00:00:53.320> for 00:00:53.510 --> 00:00:53.520 align:start position:0% morning I think I should thank Roman for 00:00:53.520 --> 00:00:56.630 align:start position:0% morning I think I should thank Roman for getting<00:00:53.760> you<00:00:53.960> guys<00:00:54.199> wasted<00:00:54.680> last<00:00:55.359> night<00:00:56.359> so 00:00:56.630 --> 00:00:56.640 align:start position:0% getting you guys wasted last night so 00:00:56.640 --> 00:00:58.709 align:start position:0% getting you guys wasted last night so nobody's<00:00:57.079> here<00:00:57.320> this<00:00:57.440> morning<00:00:57.719> to<00:00:57.879> see<00:00:58.399> see 00:00:58.709 --> 00:00:58.719 align:start position:0% nobody's here this morning to see see 00:00:58.719 --> 00:01:01.790 align:start position:0% nobody's here this morning to see see this<00:00:59.480> so<00:01:00.239> uh<00:01:00.559> the<00:01:01.039> the<00:01:01.160> title<00:01:01.359> of<00:01:01.440> the<00:01:01.559> speech 00:01:01.790 --> 00:01:01.800 align:start position:0% this so uh the the title of the speech 00:01:01.800 --> 00:01:06.270 align:start position:0% this so uh the the title of the speech this<00:01:01.920> morning<00:01:02.199> is<00:01:02.519> a<00:01:02.680> lapon<00:01:03.680> criet<00:01:04.360> but<00:01:05.360> um 00:01:06.270 --> 00:01:06.280 align:start position:0% this morning is a lapon criet but um 00:01:06.280 --> 00:01:09.190 align:start position:0% this morning is a lapon criet but um what<00:01:06.400> I<00:01:06.560> really<00:01:06.720> want<00:01:06.880> to<00:01:07.159> do<00:01:07.520> is<00:01:08.360> take<00:01:08.600> a<00:01:08.960> trip 00:01:09.190 --> 00:01:09.200 align:start position:0% what I really want to do is take a trip 00:01:09.200 --> 00:01:13.469 align:start position:0% what I really want to do is take a trip down<00:01:09.439> memory<00:01:10.119> lane<00:01:11.119> uh<00:01:11.320> which<00:01:11.960> was<00:01:12.360> late<00:01:12.759> July 00:01:13.469 --> 00:01:13.479 align:start position:0% down memory lane uh which was late July 00:01:13.479 --> 00:01:16.789 align:start position:0% down memory lane uh which was late July 2015<00:01:14.280> when<00:01:14.479> Frontier<00:01:15.000> was<00:01:15.280> released<00:01:16.280> was<00:01:16.479> when 00:01:16.789 --> 00:01:16.799 align:start position:0% 2015 when Frontier was released was when 00:01:16.799 --> 00:01:19.710 align:start position:0% 2015 when Frontier was released was when we<00:01:17.040> officially<00:01:17.439> started<00:01:18.200> playing<00:01:18.920> with 00:01:19.710 --> 00:01:19.720 align:start position:0% we officially started playing with 00:01:19.720 --> 00:01:23.069 align:start position:0% we officially started playing with ethereum<00:01:20.720> um<00:01:21.200> such<00:01:21.479> that<00:01:21.720> we<00:01:22.079> then<00:01:22.280> launched 00:01:23.069 --> 00:01:23.079 align:start position:0% ethereum um such that we then launched 00:01:23.079 --> 00:01:25.510 align:start position:0% ethereum um such that we then launched with<00:01:23.280> ethereum<00:01:23.840> together<00:01:24.799> uh<00:01:24.920> using<00:01:25.280> with<00:01:25.400> our 00:01:25.510 --> 00:01:25.520 align:start position:0% with ethereum together uh using with our 00:01:25.520 --> 00:01:27.950 align:start position:0% with ethereum together uh using with our partners<00:01:25.880> consensus<00:01:26.799> uh<00:01:26.880> and<00:01:27.000> started<00:01:27.400> down 00:01:27.950 --> 00:01:27.960 align:start position:0% partners consensus uh and started down 00:01:27.960 --> 00:01:31.230 align:start position:0% partners consensus uh and started down the<00:01:28.960> uh<00:01:29.159> ethereum<00:01:29.600> block<00:01:30.000> chain<00:01:30.159> is<00:01:30.280> a<00:01:30.439> service 00:01:31.230 --> 00:01:31.240 align:start position:0% the uh ethereum block chain is a service 00:01:31.240 --> 00:01:33.630 align:start position:0% the uh ethereum block chain is a service so<00:01:32.000> I<00:01:32.119> always<00:01:32.320> feel<00:01:32.560> like<00:01:32.960> uh<00:01:33.079> the<00:01:33.200> journey 00:01:33.630 --> 00:01:33.640 align:start position:0% so I always feel like uh the journey 00:01:33.640 --> 00:01:36.149 align:start position:0% so I always feel like uh the journey with<00:01:34.360> uh<00:01:35.200> a<00:01:35.280> lot<00:01:35.399> of<00:01:35.520> people<00:01:35.720> point<00:01:35.920> to 00:01:36.149 --> 00:01:36.159 align:start position:0% with uh a lot of people point to 00:01:36.159 --> 00:01:37.749 align:start position:0% with uh a lot of people point to Microsoft<00:01:36.600> being<00:01:36.720> an<00:01:36.840> early<00:01:37.040> adopter<00:01:37.399> of 00:01:37.749 --> 00:01:37.759 align:start position:0% Microsoft being an early adopter of 00:01:37.759 --> 00:01:40.190 align:start position:0% Microsoft being an early adopter of Bitcoin<00:01:38.759> that<00:01:38.880> was<00:01:38.960> a<00:01:39.119> sort<00:01:39.280> of<00:01:39.399> an<00:01:39.600> experiment 00:01:40.190 --> 00:01:40.200 align:start position:0% Bitcoin that was a sort of an experiment 00:01:40.200 --> 00:01:42.990 align:start position:0% Bitcoin that was a sort of an experiment our<00:01:40.680> our<00:01:41.439> uh<00:01:41.640> Learning<00:01:42.000> lesson<00:01:42.399> for<00:01:42.600> us<00:01:42.759> to 00:01:42.990 --> 00:01:43.000 align:start position:0% our our uh Learning lesson for us to 00:01:43.000 --> 00:01:46.870 align:start position:0% our our uh Learning lesson for us to really<00:01:43.799> Embrace<00:01:44.920> ethereum<00:01:45.920> so<00:01:46.439> uh<00:01:46.719> I<00:01:46.799> don't 00:01:46.870 --> 00:01:46.880 align:start position:0% really Embrace ethereum so uh I don't 00:01:46.880 --> 00:01:47.870 align:start position:0% really Embrace ethereum so uh I don't want<00:01:47.000> to<00:01:47.119> tell<00:01:47.240> you<00:01:47.360> what<00:01:47.479> I<00:01:47.560> had<00:01:47.680> to<00:01:47.759> go 00:01:47.870 --> 00:01:47.880 align:start position:0% want to tell you what I had to go 00:01:47.880 --> 00:01:49.310 align:start position:0% want to tell you what I had to go through<00:01:48.040> to<00:01:48.159> get<00:01:48.280> the<00:01:48.439> sponsorship<00:01:48.960> for<00:01:49.159> last 00:01:49.310 --> 00:01:49.320 align:start position:0% through to get the sponsorship for last 00:01:49.320 --> 00:01:52.109 align:start position:0% through to get the sponsorship for last year's<00:01:49.759> Devcon<00:01:50.759> uh<00:01:50.880> it<00:01:50.960> was<00:01:51.119> not<00:01:51.360> pretty<00:01:52.000> uh 00:01:52.109 --> 00:01:52.119 align:start position:0% year's Devcon uh it was not pretty uh 00:01:52.119 --> 00:01:53.789 align:start position:0% year's Devcon uh it was not pretty uh this<00:01:52.200> year's<00:01:52.479> Devcon<00:01:52.920> sponsorship<00:01:53.399> was<00:01:53.560> quite 00:01:53.789 --> 00:01:53.799 align:start position:0% this year's Devcon sponsorship was quite 00:01:53.799 --> 00:01:56.510 align:start position:0% this year's Devcon sponsorship was quite easy<00:01:54.640> uh<00:01:54.719> for<00:01:54.880> me<00:01:55.000> to<00:01:55.159> do<00:01:55.920> it's<00:01:56.079> a<00:01:56.200> lot<00:01:56.360> more 00:01:56.510 --> 00:01:56.520 align:start position:0% easy uh for me to do it's a lot more 00:01:56.520 --> 00:01:58.310 align:start position:0% easy uh for me to do it's a lot more money<00:01:56.960> as 00:01:58.310 --> 00:01:58.320 align:start position:0% money as 00:01:58.320 --> 00:02:01.870 align:start position:0% money as well<00:01:59.320> um<00:02:00.039> but<00:02:00.439> uh<00:02:00.600> you<00:02:00.719> know<00:02:00.840> ethereum<00:02:01.439> just<00:02:01.560> to 00:02:01.870 --> 00:02:01.880 align:start position:0% well um but uh you know ethereum just to 00:02:01.880 --> 00:02:03.910 align:start position:0% well um but uh you know ethereum just to set<00:02:02.159> the<00:02:02.399> the<00:02:02.520> stage<00:02:02.880> here<00:02:03.079> for<00:02:03.360> Microsoft's 00:02:03.910 --> 00:02:03.920 align:start position:0% set the the stage here for Microsoft's 00:02:03.920 --> 00:02:05.990 align:start position:0% set the the stage here for Microsoft's commitment<00:02:04.320> here<00:02:04.520> is<00:02:05.240> you<00:02:05.320> know<00:02:05.479> ethereum<00:02:05.880> as 00:02:05.990 --> 00:02:06.000 align:start position:0% commitment here is you know ethereum as 00:02:06.000 --> 00:02:07.590 align:start position:0% commitment here is you know ethereum as a<00:02:06.079> first<00:02:06.360> class<00:02:06.600> citizen<00:02:06.960> will<00:02:07.159> continue<00:02:07.479> to 00:02:07.590 --> 00:02:07.600 align:start position:0% a first class citizen will continue to 00:02:07.600 --> 00:02:09.710 align:start position:0% a first class citizen will continue to be<00:02:07.719> a<00:02:07.880> first<00:02:08.160> class<00:02:08.399> citizen<00:02:09.360> in<00:02:09.520> our 00:02:09.710 --> 00:02:09.720 align:start position:0% be a first class citizen in our 00:02:09.720 --> 00:02:12.589 align:start position:0% be a first class citizen in our distributed<00:02:10.280> Ledger<00:02:10.800> efforts<00:02:11.720> um<00:02:11.879> at 00:02:12.589 --> 00:02:12.599 align:start position:0% distributed Ledger efforts um at 00:02:12.599 --> 00:02:15.869 align:start position:0% distributed Ledger efforts um at Microsoft<00:02:13.599> um<00:02:13.760> and<00:02:13.920> it<00:02:14.080> is<00:02:14.760> um<00:02:15.200> it<00:02:15.360> dominates 00:02:15.869 --> 00:02:15.879 align:start position:0% Microsoft um and it is um it dominates 00:02:15.879 --> 00:02:19.350 align:start position:0% Microsoft um and it is um it dominates our<00:02:16.480> Marketplace<00:02:17.480> um<00:02:17.920> and<00:02:18.319> our<00:02:18.560> customers<00:02:19.120> are 00:02:19.350 --> 00:02:19.360 align:start position:0% our Marketplace um and our customers are 00:02:19.360 --> 00:02:23.229 align:start position:0% our Marketplace um and our customers are using<00:02:19.760> it<00:02:20.760> uh<00:02:20.920> and<00:02:21.200> asking<00:02:21.640> us<00:02:22.319> um<00:02:22.640> and<00:02:22.959> and 00:02:23.229 --> 00:02:23.239 align:start position:0% using it uh and asking us um and and 00:02:23.239 --> 00:02:26.309 align:start position:0% using it uh and asking us um and and with<00:02:23.560> that<00:02:24.560> um<00:02:25.000> we're<00:02:25.160> going<00:02:25.280> to<00:02:25.599> um<00:02:26.040> I've<00:02:26.200> got 00:02:26.309 --> 00:02:26.319 align:start position:0% with that um we're going to um I've got 00:02:26.319 --> 00:02:27.830 align:start position:0% with that um we're going to um I've got some<00:02:26.480> things<00:02:26.680> we're<00:02:26.879> doing<00:02:27.280> U<00:02:27.480> I<00:02:27.599> have<00:02:27.680> a<00:02:27.760> lot 00:02:27.830 --> 00:02:27.840 align:start position:0% some things we're doing U I have a lot 00:02:27.840 --> 00:02:29.110 align:start position:0% some things we're doing U I have a lot of<00:02:27.959> Partners<00:02:28.239> in<00:02:28.360> the<00:02:28.440> room<00:02:28.599> I<00:02:28.680> think<00:02:28.840> almost 00:02:29.110 --> 00:02:29.120 align:start position:0% of Partners in the room I think almost 00:02:29.120 --> 00:02:31.830 align:start position:0% of Partners in the room I think almost everyone<00:02:29.440> should<00:02:29.599> be<00:02:29.959> partner<00:02:30.360> if<00:02:30.480> you're<00:02:30.840> not 00:02:31.830 --> 00:02:31.840 align:start position:0% everyone should be partner if you're not 00:02:31.840 --> 00:02:33.270 align:start position:0% everyone should be partner if you're not uh<00:02:32.120> please<00:02:32.400> talk<00:02:32.560> to<00:02:32.680> your<00:02:32.840> Microsoft 00:02:33.270 --> 00:02:33.280 align:start position:0% uh please talk to your Microsoft 00:02:33.280 --> 00:02:35.150 align:start position:0% uh please talk to your Microsoft representative<00:02:34.040> if<00:02:34.160> you're<00:02:34.280> a<00:02:34.400> small<00:02:34.720> startup 00:02:35.150 --> 00:02:35.160 align:start position:0% representative if you're a small startup 00:02:35.160 --> 00:02:37.190 align:start position:0% representative if you're a small startup we<00:02:35.239> have<00:02:35.440> programs<00:02:35.800> called<00:02:36.040> bis<00:02:36.360> spark<00:02:36.959> I<00:02:37.040> know 00:02:37.190 --> 00:02:37.200 align:start position:0% we have programs called bis spark I know 00:02:37.200 --> 00:02:38.869 align:start position:0% we have programs called bis spark I know a<00:02:37.280> lot<00:02:37.400> of<00:02:37.480> you<00:02:37.640> have<00:02:37.760> taken<00:02:38.319> advantage<00:02:38.720> of 00:02:38.869 --> 00:02:38.879 align:start position:0% a lot of you have taken advantage of 00:02:38.879 --> 00:02:42.390 align:start position:0% a lot of you have taken advantage of that<00:02:39.560> encourage<00:02:39.920> you<00:02:40.040> to<00:02:40.239> do<00:02:40.760> that<00:02:41.760> um<00:02:42.080> and 00:02:42.390 --> 00:02:42.400 align:start position:0% that encourage you to do that um and 00:02:42.400 --> 00:02:44.470 align:start position:0% that encourage you to do that um and we'll<00:02:42.560> be<00:02:42.680> talking<00:02:42.959> some<00:02:43.200> more<00:02:43.720> about<00:02:44.120> the<00:02:44.360> the 00:02:44.470 --> 00:02:44.480 align:start position:0% we'll be talking some more about the the 00:02:44.480 --> 00:02:46.910 align:start position:0% we'll be talking some more about the the other<00:02:44.959> things<00:02:45.760> later<00:02:46.360> but<00:02:46.519> this<00:02:46.599> morning<00:02:46.840> I 00:02:46.910 --> 00:02:46.920 align:start position:0% other things later but this morning I 00:02:46.920 --> 00:02:49.509 align:start position:0% other things later but this morning I want<00:02:47.040> to<00:02:47.400> announce<00:02:48.400> um<00:02:48.840> proud<00:02:49.040> to<00:02:49.200> announce 00:02:49.509 --> 00:02:49.519 align:start position:0% want to announce um proud to announce 00:02:49.519 --> 00:02:51.910 align:start position:0% want to announce um proud to announce Bletchley<00:02:50.159> version<00:02:50.560> one<00:02:51.159> so<00:02:51.360> Bletchley<00:02:51.840> is 00:02:51.910 --> 00:02:51.920 align:start position:0% Bletchley version one so Bletchley is 00:02:51.920 --> 00:02:54.030 align:start position:0% Bletchley version one so Bletchley is our<00:02:52.120> code<00:02:52.400> name<00:02:52.640> for<00:02:52.920> everything<00:02:53.920> uh 00:02:54.030 --> 00:02:54.040 align:start position:0% our code name for everything uh 00:02:54.040 --> 00:02:56.910 align:start position:0% our code name for everything uh blockchain<00:02:54.680> at<00:02:55.280> Microsoft<00:02:56.280> and<00:02:56.560> uh<00:02:56.680> let<00:02:56.800> me 00:02:56.910 --> 00:02:56.920 align:start position:0% blockchain at Microsoft and uh let me 00:02:56.920 --> 00:02:58.350 align:start position:0% blockchain at Microsoft and uh let me explain<00:02:57.200> a<00:02:57.280> little<00:02:57.440> bit<00:02:57.599> about<00:02:57.760> what<00:02:57.879> that<00:02:58.159> is 00:02:58.350 --> 00:02:58.360 align:start position:0% explain a little bit about what that is 00:02:58.360 --> 00:03:00.470 align:start position:0% explain a little bit about what that is and<00:02:58.480> I'm<00:02:58.560> going<00:02:58.680> to<00:02:58.800> walk<00:02:58.959> you<00:02:59.159> through 00:03:00.470 --> 00:03:00.480 align:start position:0% and I'm going to walk you through 00:03:00.480 --> 00:03:04.509 align:start position:0% and I'm going to walk you through uh<00:03:00.599> what<00:03:00.800> V1<00:03:01.599> means<00:03:02.599> um<00:03:02.840> but<00:03:03.360> blly<00:03:03.959> the<00:03:04.239> the 00:03:04.509 --> 00:03:04.519 align:start position:0% uh what V1 means um but blly the the 00:03:04.519 --> 00:03:05.910 align:start position:0% uh what V1 means um but blly the the architectural<00:03:05.040> diagram<00:03:05.400> over<00:03:05.560> here<00:03:05.640> is<00:03:05.760> sort 00:03:05.910 --> 00:03:05.920 align:start position:0% architectural diagram over here is sort 00:03:05.920 --> 00:03:07.190 align:start position:0% architectural diagram over here is sort of<00:03:06.000> the<00:03:06.120> big<00:03:06.319> picture<00:03:06.760> and<00:03:06.840> you'll<00:03:07.000> see 00:03:07.190 --> 00:03:07.200 align:start position:0% of the big picture and you'll see 00:03:07.200 --> 00:03:09.550 align:start position:0% of the big picture and you'll see ethereum<00:03:07.599> is<00:03:07.799> quite<00:03:08.040> prominent<00:03:08.519> here<00:03:08.879> so<00:03:09.360> our 00:03:09.550 --> 00:03:09.560 align:start position:0% ethereum is quite prominent here so our 00:03:09.560 --> 00:03:11.229 align:start position:0% ethereum is quite prominent here so our distributed<00:03:10.000> Ledger<00:03:10.280> stack<00:03:10.840> down<00:03:11.000> at<00:03:11.120> the 00:03:11.229 --> 00:03:11.239 align:start position:0% distributed Ledger stack down at the 00:03:11.239 --> 00:03:12.470 align:start position:0% distributed Ledger stack down at the bottom<00:03:11.519> this<00:03:11.640> is<00:03:11.760> what<00:03:11.879> we<00:03:12.000> call<00:03:12.159> our 00:03:12.470 --> 00:03:12.480 align:start position:0% bottom this is what we call our 00:03:12.480 --> 00:03:14.830 align:start position:0% bottom this is what we call our distributed<00:03:13.480> uh<00:03:13.640> infrastructure<00:03:14.239> or<00:03:14.400> blle 00:03:14.830 --> 00:03:14.840 align:start position:0% distributed uh infrastructure or blle 00:03:14.840 --> 00:03:16.630 align:start position:0% distributed uh infrastructure or blle distributed<00:03:15.360> infrastructure<00:03:16.360> we<00:03:16.480> are 00:03:16.630 --> 00:03:16.640 align:start position:0% distributed infrastructure we are 00:03:16.640 --> 00:03:18.869 align:start position:0% distributed infrastructure we are shipping<00:03:17.080> version<00:03:17.480> one<00:03:18.000> a 00:03:18.869 --> 00:03:18.879 align:start position:0% shipping version one a 00:03:18.879 --> 00:03:22.309 align:start position:0% shipping version one a Consortium<00:03:19.879> ethereum<00:03:20.720> uh<00:03:20.879> private<00:03:21.319> Network 00:03:22.309 --> 00:03:22.319 align:start position:0% Consortium ethereum uh private Network 00:03:22.319 --> 00:03:24.670 align:start position:0% Consortium ethereum uh private Network um<00:03:22.560> starter<00:03:23.200> so<00:03:23.360> you<00:03:23.480> can<00:03:23.640> go<00:03:23.840> on<00:03:23.959> ethereum<00:03:24.440> any 00:03:24.670 --> 00:03:24.680 align:start position:0% um starter so you can go on ethereum any 00:03:24.680 --> 00:03:27.350 align:start position:0% um starter so you can go on ethereum any customer<00:03:25.680> can<00:03:26.200> uh<00:03:26.480> instead<00:03:26.760> of<00:03:26.879> just<00:03:27.000> spinning 00:03:27.350 --> 00:03:27.360 align:start position:0% customer can uh instead of just spinning 00:03:27.360 --> 00:03:29.229 align:start position:0% customer can uh instead of just spinning up<00:03:27.480> a<00:03:27.599> single<00:03:27.840> node<00:03:28.200> or<00:03:28.360> a<00:03:28.439> single<00:03:28.720> death<00:03:28.959> test 00:03:29.229 --> 00:03:29.239 align:start position:0% up a single node or a single death test 00:03:29.239 --> 00:03:31.830 align:start position:0% up a single node or a single death test lab<00:03:29.840> you<00:03:29.959> can<00:03:30.120> actually<00:03:30.360> spin<00:03:30.680> up<00:03:30.959> a<00:03:31.360> full 00:03:31.830 --> 00:03:31.840 align:start position:0% lab you can actually spin up a full 00:03:31.840 --> 00:03:33.509 align:start position:0% lab you can actually spin up a full Consortium<00:03:32.480> Network<00:03:32.879> and<00:03:33.000> I'll<00:03:33.120> go<00:03:33.280> through 00:03:33.509 --> 00:03:33.519 align:start position:0% Consortium Network and I'll go through 00:03:33.519 --> 00:03:35.470 align:start position:0% Consortium Network and I'll go through exactly<00:03:33.920> what<00:03:34.040> that<00:03:34.200> means<00:03:35.040> a<00:03:35.159> little<00:03:35.319> bit 00:03:35.470 --> 00:03:35.480 align:start position:0% exactly what that means a little bit 00:03:35.480 --> 00:03:37.270 align:start position:0% exactly what that means a little bit later<00:03:35.760> on<00:03:35.959> you'll<00:03:36.159> see<00:03:36.319> this<00:03:36.439> in<00:03:36.560> the<00:03:36.720> Press<00:03:37.080> we 00:03:37.270 --> 00:03:37.280 align:start position:0% later on you'll see this in the Press we 00:03:37.280 --> 00:03:38.589 align:start position:0% later on you'll see this in the Press we we<00:03:37.400> release<00:03:37.760> these<00:03:37.920> announcements<00:03:38.480> this 00:03:38.589 --> 00:03:38.599 align:start position:0% we release these announcements this 00:03:38.599 --> 00:03:41.710 align:start position:0% we release these announcements this morning<00:03:39.560> I<00:03:39.959> timed<00:03:40.439> with<00:03:40.799> this<00:03:41.000> keynote<00:03:41.560> it's 00:03:41.710 --> 00:03:41.720 align:start position:0% morning I timed with this keynote it's 00:03:41.720 --> 00:03:43.149 align:start position:0% morning I timed with this keynote it's hard<00:03:41.879> to<00:03:42.040> time<00:03:42.280> those<00:03:42.480> things<00:03:42.680> I<00:03:42.799> was<00:03:42.920> up<00:03:43.040> at 00:03:43.149 --> 00:03:43.159 align:start position:0% hard to time those things I was up at 00:03:43.159 --> 00:03:45.149 align:start position:0% hard to time those things I was up at four<00:03:43.319> o'clock<00:03:43.599> in<00:03:43.680> the<00:03:43.799> morning<00:03:44.480> S<00:03:44.840> I<00:03:44.920> know<00:03:45.040> you 00:03:45.149 --> 00:03:45.159 align:start position:0% four o'clock in the morning S I know you 00:03:45.159 --> 00:03:46.390 align:start position:0% four o'clock in the morning S I know you were<00:03:45.319> up<00:03:45.439> at<00:03:45.560> like 00:03:46.390 --> 00:03:46.400 align:start position:0% were up at like 00:03:46.400 --> 00:03:49.470 align:start position:0% were up at like three<00:03:47.400> working<00:03:47.680> on<00:03:47.879> this<00:03:48.120> stuff<00:03:48.480> so<00:03:49.200> uh<00:03:49.319> we'll 00:03:49.470 --> 00:03:49.480 align:start position:0% three working on this stuff so uh we'll 00:03:49.480 --> 00:03:50.869 align:start position:0% three working on this stuff so uh we'll walk<00:03:49.680> through<00:03:49.879> this<00:03:50.040> but<00:03:50.239> you<00:03:50.319> know<00:03:50.480> ethereum 00:03:50.869 --> 00:03:50.879 align:start position:0% walk through this but you know ethereum 00:03:50.879 --> 00:03:52.069 align:start position:0% walk through this but you know ethereum is<00:03:51.000> the<00:03:51.080> first<00:03:51.319> class<00:03:51.519> we're<00:03:51.640> going<00:03:51.760> to<00:03:51.879> walk 00:03:52.069 --> 00:03:52.079 align:start position:0% is the first class we're going to walk 00:03:52.079 --> 00:03:54.110 align:start position:0% is the first class we're going to walk through<00:03:52.319> that<00:03:53.239> um<00:03:53.360> I'm<00:03:53.439> going<00:03:53.560> to<00:03:53.680> first<00:03:53.920> walk 00:03:54.110 --> 00:03:54.120 align:start position:0% through that um I'm going to first walk 00:03:54.120 --> 00:03:55.630 align:start position:0% through that um I'm going to first walk you<00:03:54.280> through<00:03:54.959> uh 00:03:55.630 --> 00:03:55.640 align:start position:0% you through uh 00:03:55.640 --> 00:03:58.990 align:start position:0% you through uh criet<00:03:56.640> so<00:03:57.120> uh<00:03:57.239> we<00:03:57.360> introduced<00:03:57.799> criet<00:03:58.640> um<00:03:58.799> in 00:03:58.990 --> 00:03:59.000 align:start position:0% criet so uh we introduced criet um in 00:03:59.000 --> 00:04:04.309 align:start position:0% criet so uh we introduced criet um in June<00:04:00.200> as<00:04:00.560> a<00:04:01.280> um<00:04:01.879> a<00:04:02.159> middleware<00:04:03.159> um<00:04:03.480> approach 00:04:04.309 --> 00:04:04.319 align:start position:0% June as a um a middleware um approach 00:04:04.319 --> 00:04:07.069 align:start position:0% June as a um a middleware um approach for<00:04:05.319> um<00:04:05.519> taking<00:04:05.959> blockchains<00:04:06.599> or<00:04:06.760> bringing 00:04:07.069 --> 00:04:07.079 align:start position:0% for um taking blockchains or bringing 00:04:07.079 --> 00:04:09.069 align:start position:0% for um taking blockchains or bringing blockchains<00:04:07.519> into<00:04:07.720> the<00:04:07.840> Enterprise<00:04:08.560> all<00:04:08.720> of 00:04:09.069 --> 00:04:09.079 align:start position:0% blockchains into the Enterprise all of 00:04:09.079 --> 00:04:11.390 align:start position:0% blockchains into the Enterprise all of our<00:04:09.319> interest<00:04:09.720> from<00:04:09.920> our<00:04:10.280> major<00:04:11.280> uh 00:04:11.390 --> 00:04:11.400 align:start position:0% our interest from our major uh 00:04:11.400 --> 00:04:14.869 align:start position:0% our interest from our major uh Enterprises<00:04:12.159> are<00:04:12.680> trying<00:04:12.959> to<00:04:13.159> figure<00:04:13.480> out<00:04:13.959> how 00:04:14.869 --> 00:04:14.879 align:start position:0% Enterprises are trying to figure out how 00:04:14.879 --> 00:04:17.270 align:start position:0% Enterprises are trying to figure out how consortiums<00:04:15.599> will<00:04:15.799> get<00:04:16.079> together<00:04:16.600> to<00:04:17.040> take 00:04:17.270 --> 00:04:17.280 align:start position:0% consortiums will get together to take 00:04:17.280 --> 00:04:20.229 align:start position:0% consortiums will get together to take advantage<00:04:17.680> of<00:04:17.880> this<00:04:18.560> distributed<00:04:19.560> uh<00:04:19.759> Network 00:04:20.229 --> 00:04:20.239 align:start position:0% advantage of this distributed uh Network 00:04:20.239 --> 00:04:24.150 align:start position:0% advantage of this distributed uh Network promise<00:04:21.079> so<00:04:21.320> criet<00:04:21.880> is<00:04:22.639> is<00:04:23.120> uh<00:04:23.520> how<00:04:23.759> we<00:04:23.880> sort<00:04:24.040> of 00:04:24.150 --> 00:04:24.160 align:start position:0% promise so criet is is uh how we sort of 00:04:24.160 --> 00:04:26.629 align:start position:0% promise so criet is is uh how we sort of get<00:04:24.280> our<00:04:24.520> head<00:04:24.720> around<00:04:25.160> this<00:04:26.160> uh<00:04:26.280> and<00:04:26.360> we<00:04:26.520> look 00:04:26.629 --> 00:04:26.639 align:start position:0% get our head around this uh and we look 00:04:26.639 --> 00:04:28.510 align:start position:0% get our head around this uh and we look at<00:04:26.759> it<00:04:26.840> as<00:04:26.919> a<00:04:27.040> new<00:04:27.199> tier<00:04:27.600> so<00:04:27.840> those<00:04:27.960> of<00:04:28.080> you<00:04:28.280> that 00:04:28.510 --> 00:04:28.520 align:start position:0% at it as a new tier so those of you that 00:04:28.520 --> 00:04:30.510 align:start position:0% at it as a new tier so those of you that have<00:04:28.680> some<00:04:28.880> gray<00:04:29.160> hair<00:04:29.840> um<00:04:29.960> we'll<00:04:30.160> remember 00:04:30.510 --> 00:04:30.520 align:start position:0% have some gray hair um we'll remember 00:04:30.520 --> 00:04:31.830 align:start position:0% have some gray hair um we'll remember the<00:04:30.680> pain<00:04:30.880> we<00:04:31.000> went<00:04:31.160> through<00:04:31.479> went<00:04:31.639> from 00:04:31.830 --> 00:04:31.840 align:start position:0% the pain we went through went from 00:04:31.840 --> 00:04:33.790 align:start position:0% the pain we went through went from client<00:04:32.160> server<00:04:33.039> to<00:04:33.240> three-<00:04:33.479> tiered 00:04:33.790 --> 00:04:33.800 align:start position:0% client server to three- tiered 00:04:33.800 --> 00:04:35.590 align:start position:0% client server to three- tiered architecture<00:04:34.280> in<00:04:34.440> the<00:04:34.560> web<00:04:34.919> very<00:04:35.120> similar<00:04:35.440> to 00:04:35.590 --> 00:04:35.600 align:start position:0% architecture in the web very similar to 00:04:35.600 --> 00:04:37.510 align:start position:0% architecture in the web very similar to the<00:04:35.759> pain<00:04:36.120> that<00:04:36.600> um<00:04:36.720> we're<00:04:36.919> experiencing<00:04:37.440> in 00:04:37.510 --> 00:04:37.520 align:start position:0% the pain that um we're experiencing in 00:04:37.520 --> 00:04:40.510 align:start position:0% the pain that um we're experiencing in The<00:04:37.680> Growing<00:04:38.360> Pains<00:04:39.360> uh<00:04:39.520> within<00:04:40.039> distributed 00:04:40.510 --> 00:04:40.520 align:start position:0% The Growing Pains uh within distributed 00:04:40.520 --> 00:04:41.590 align:start position:0% The Growing Pains uh within distributed ledgers<00:04:40.840> or 00:04:41.590 --> 00:04:41.600 align:start position:0% ledgers or 00:04:41.600 --> 00:04:43.870 align:start position:0% ledgers or blockchains<00:04:42.600> and<00:04:42.919> um<00:04:43.240> so<00:04:43.400> there's<00:04:43.560> a<00:04:43.680> lot<00:04:43.759> of 00:04:43.870 --> 00:04:43.880 align:start position:0% blockchains and um so there's a lot of 00:04:43.880 --> 00:04:45.710 align:start position:0% blockchains and um so there's a lot of missing<00:04:44.240> parts<00:04:44.560> that<00:04:44.720> enterprises<00:04:45.320> want<00:04:45.600> they 00:04:45.710 --> 00:04:45.720 align:start position:0% missing parts that enterprises want they 00:04:45.720 --> 00:04:47.909 align:start position:0% missing parts that enterprises want they want<00:04:45.960> things<00:04:46.280> like<00:04:47.160> some<00:04:47.320> people<00:04:47.520> call<00:04:47.680> them 00:04:47.909 --> 00:04:47.919 align:start position:0% want things like some people call them 00:04:47.919 --> 00:04:50.670 align:start position:0% want things like some people call them ill<00:04:48.680> list<00:04:49.440> but<00:04:49.560> it's<00:04:49.919> essentially 00:04:50.670 --> 00:04:50.680 align:start position:0% ill list but it's essentially 00:04:50.680 --> 00:04:52.510 align:start position:0% ill list but it's essentially scalability 00:04:52.510 --> 00:04:52.520 align:start position:0% scalability 00:04:52.520 --> 00:04:55.230 align:start position:0% scalability manageability<00:04:53.520> um<00:04:54.039> you<00:04:54.160> know<00:04:54.720> those<00:04:55.039> those 00:04:55.230 --> 00:04:55.240 align:start position:0% manageability um you know those those 00:04:55.240 --> 00:04:58.430 align:start position:0% manageability um you know those those types<00:04:55.479> of<00:04:55.680> things<00:04:56.560> um<00:04:56.919> so<00:04:57.520> we<00:04:57.680> we<00:04:57.840> identified 00:04:58.430 --> 00:04:58.440 align:start position:0% types of things um so we we identified 00:04:58.440 --> 00:05:00.870 align:start position:0% types of things um so we we identified these<00:04:59.160> these<00:04:59.360> key<00:04:59.800> things<00:05:00.000> like<00:05:00.199> identity 00:05:00.870 --> 00:05:00.880 align:start position:0% these these key things like identity 00:05:00.880 --> 00:05:02.749 align:start position:0% these these key things like identity existing<00:05:01.280> systems<00:05:01.720> integration<00:05:02.440> Key 00:05:02.749 --> 00:05:02.759 align:start position:0% existing systems integration Key 00:05:02.759 --> 00:05:05.510 align:start position:0% existing systems integration Key Management<00:05:03.759> not<00:05:04.000> just<00:05:04.520> storing<00:05:05.000> your<00:05:05.199> keys 00:05:05.510 --> 00:05:05.520 align:start position:0% Management not just storing your keys 00:05:05.520 --> 00:05:07.430 align:start position:0% Management not just storing your keys but<00:05:05.639> managing<00:05:06.039> the<00:05:06.199> entire<00:05:06.560> life<00:05:06.840> cycle<00:05:07.320> of 00:05:07.430 --> 00:05:07.440 align:start position:0% but managing the entire life cycle of 00:05:07.440 --> 00:05:09.510 align:start position:0% but managing the entire life cycle of your<00:05:07.680> keys<00:05:07.919> it's<00:05:08.039> a<00:05:08.240> very<00:05:08.960> difficult<00:05:09.160> thing<00:05:09.320> to 00:05:09.510 --> 00:05:09.520 align:start position:0% your keys it's a very difficult thing to 00:05:09.520 --> 00:05:13.110 align:start position:0% your keys it's a very difficult thing to do<00:05:10.479> uh<00:05:10.560> and<00:05:10.680> do<00:05:11.240> correctly<00:05:12.240> um<00:05:12.440> Security<00:05:12.840> in 00:05:13.110 --> 00:05:13.120 align:start position:0% do uh and do correctly um Security in 00:05:13.120 --> 00:05:15.350 align:start position:0% do uh and do correctly um Security in depth<00:05:13.800> uh<00:05:14.000> just<00:05:14.560> the<00:05:14.720> number<00:05:14.960> of<00:05:15.080> talks 00:05:15.350 --> 00:05:15.360 align:start position:0% depth uh just the number of talks 00:05:15.360 --> 00:05:17.710 align:start position:0% depth uh just the number of talks yesterday<00:05:15.840> on<00:05:16.280> security<00:05:17.280> uh<00:05:17.400> I<00:05:17.440> don't<00:05:17.600> think 00:05:17.710 --> 00:05:17.720 align:start position:0% yesterday on security uh I don't think 00:05:17.720 --> 00:05:20.230 align:start position:0% yesterday on security uh I don't think we<00:05:17.840> even<00:05:18.080> had<00:05:18.199> a<00:05:18.360> topic<00:05:18.639> on<00:05:18.759> it<00:05:19.000> last<00:05:19.240> year 00:05:20.230 --> 00:05:20.240 align:start position:0% we even had a topic on it last year 00:05:20.240 --> 00:05:24.110 align:start position:0% we even had a topic on it last year maybe<00:05:20.520> one<00:05:20.680> or<00:05:20.880> two<00:05:22.039> um<00:05:23.039> but<00:05:23.440> uh<00:05:23.800> we're<00:05:23.960> really 00:05:24.110 --> 00:05:24.120 align:start position:0% maybe one or two um but uh we're really 00:05:24.120 --> 00:05:25.550 align:start position:0% maybe one or two um but uh we're really getting<00:05:24.280> to<00:05:24.360> the<00:05:24.479> point<00:05:24.680> where<00:05:24.840> people<00:05:25.039> can<00:05:25.479> uh 00:05:25.550 --> 00:05:25.560 align:start position:0% getting to the point where people can uh 00:05:25.560 --> 00:05:28.230 align:start position:0% getting to the point where people can uh start<00:05:25.800> Building<00:05:26.600> Solutions<00:05:27.600> uh<00:05:27.720> industry 00:05:28.230 --> 00:05:28.240 align:start position:0% start Building Solutions uh industry 00:05:28.240 --> 00:05:30.270 align:start position:0% start Building Solutions uh industry specific<00:05:28.680> Solutions<00:05:29.080> Financial<00:05:29.400> Service<00:05:30.039> is 00:05:30.270 --> 00:05:30.280 align:start position:0% specific Solutions Financial Service is 00:05:30.280 --> 00:05:32.189 align:start position:0% specific Solutions Financial Service is the<00:05:30.479> is<00:05:30.639> the<00:05:30.800> largest<00:05:31.759> but<00:05:31.919> we're<00:05:32.000> going<00:05:32.120> to 00:05:32.189 --> 00:05:32.199 align:start position:0% the is the largest but we're going to 00:05:32.199 --> 00:05:35.029 align:start position:0% the is the largest but we're going to see<00:05:32.360> them<00:05:32.520> in<00:05:32.680> healthcare<00:05:33.520> media<00:05:34.520> uh<00:05:34.680> Supply 00:05:35.029 --> 00:05:35.039 align:start position:0% see them in healthcare media uh Supply 00:05:35.039 --> 00:05:39.309 align:start position:0% see them in healthcare media uh Supply chains<00:05:35.520> huge<00:05:36.440> all<00:05:36.600> over<00:05:36.800> the<00:05:37.280> place<00:05:38.280> um<00:05:38.759> so<00:05:39.199> uh 00:05:39.309 --> 00:05:39.319 align:start position:0% chains huge all over the place um so uh 00:05:39.319 --> 00:05:42.430 align:start position:0% chains huge all over the place um so uh criet<00:05:39.800> is<00:05:40.080> our<00:05:40.680> uh<00:05:41.240> sort<00:05:41.400> of<00:05:41.520> our<00:05:41.759> catchall<00:05:42.240> for 00:05:42.430 --> 00:05:42.440 align:start position:0% criet is our uh sort of our catchall for 00:05:42.440 --> 00:05:45.150 align:start position:0% criet is our uh sort of our catchall for delivering<00:05:42.919> these<00:05:43.680> capabilities<00:05:44.680> uh<00:05:44.800> in<00:05:44.960> the 00:05:45.150 --> 00:05:45.160 align:start position:0% delivering these capabilities uh in the 00:05:45.160 --> 00:05:48.909 align:start position:0% delivering these capabilities uh in the cloud<00:05:46.199> so<00:05:47.199> um<00:05:48.120> with<00:05:48.240> the<00:05:48.360> introduction<00:05:48.759> of 00:05:48.909 --> 00:05:48.919 align:start position:0% cloud so um with the introduction of 00:05:48.919 --> 00:05:51.909 align:start position:0% cloud so um with the introduction of oracles<00:05:49.880> um<00:05:50.120> you<00:05:50.240> know<00:05:50.560> the<00:05:51.199> how<00:05:51.280> do<00:05:51.440> you<00:05:51.639> get 00:05:51.909 --> 00:05:51.919 align:start position:0% oracles um you know the how do you get 00:05:51.919 --> 00:05:54.150 align:start position:0% oracles um you know the how do you get data<00:05:52.319> injected<00:05:52.880> or<00:05:53.199> real<00:05:53.479> world<00:05:53.800> data 00:05:54.150 --> 00:05:54.160 align:start position:0% data injected or real world data 00:05:54.160 --> 00:05:56.830 align:start position:0% data injected or real world data injected<00:05:54.600> into<00:05:54.800> a<00:05:55.120> blockchain<00:05:56.120> oracles<00:05:56.600> came 00:05:56.830 --> 00:05:56.840 align:start position:0% injected into a blockchain oracles came 00:05:56.840 --> 00:05:59.070 align:start position:0% injected into a blockchain oracles came out<00:05:57.360> um<00:05:57.520> but<00:05:57.639> it's<00:05:57.800> more<00:05:57.960> than<00:05:58.160> just<00:05:58.479> trusted 00:05:59.070 --> 00:05:59.080 align:start position:0% out um but it's more than just trusted 00:05:59.080 --> 00:06:00.590 align:start position:0% out um but it's more than just trusted data<00:05:59.360> it's<00:05:59.680> how<00:05:59.759> do<00:05:59.840> you<00:05:59.919> get<00:06:00.039> trusted 00:06:00.590 --> 00:06:00.600 align:start position:0% data it's how do you get trusted 00:06:00.600 --> 00:06:03.430 align:start position:0% data it's how do you get trusted execution<00:06:01.600> we<00:06:01.720> need<00:06:01.919> a<00:06:02.160> very<00:06:02.600> flexible<00:06:03.199> and 00:06:03.430 --> 00:06:03.440 align:start position:0% execution we need a very flexible and 00:06:03.440 --> 00:06:06.909 align:start position:0% execution we need a very flexible and malleable<00:06:04.440> execution<00:06:05.240> platform<00:06:06.240> where<00:06:06.680> you 00:06:06.909 --> 00:06:06.919 align:start position:0% malleable execution platform where you 00:06:06.919 --> 00:06:08.909 align:start position:0% malleable execution platform where you as<00:06:07.039> an<00:06:07.199> architect<00:06:07.720> or<00:06:07.960> developer<00:06:08.440> can<00:06:08.680> make 00:06:08.909 --> 00:06:08.919 align:start position:0% as an architect or developer can make 00:06:08.919 --> 00:06:10.830 align:start position:0% as an architect or developer can make the<00:06:09.120> right<00:06:09.479> decisions<00:06:10.120> based<00:06:10.360> on<00:06:10.520> what<00:06:10.639> you're 00:06:10.830 --> 00:06:10.840 align:start position:0% the right decisions based on what you're 00:06:10.840 --> 00:06:13.749 align:start position:0% the right decisions based on what you're trying<00:06:11.120> to<00:06:11.560> do<00:06:12.560> um<00:06:12.800> and<00:06:13.000> have<00:06:13.280> clean 00:06:13.749 --> 00:06:13.759 align:start position:0% trying to do um and have clean 00:06:13.759 --> 00:06:16.790 align:start position:0% trying to do um and have clean separation<00:06:14.319> of<00:06:14.599> concerns<00:06:15.360> in<00:06:15.520> your<00:06:15.800> code 00:06:16.790 --> 00:06:16.800 align:start position:0% separation of concerns in your code 00:06:16.800 --> 00:06:19.430 align:start position:0% separation of concerns in your code which<00:06:16.919> is<00:06:17.080> something<00:06:17.880> um<00:06:18.039> in<00:06:18.199> the<00:06:18.440> Enterprise 00:06:19.430 --> 00:06:19.440 align:start position:0% which is something um in the Enterprise 00:06:19.440 --> 00:06:22.749 align:start position:0% which is something um in the Enterprise um<00:06:19.720> is<00:06:20.599> uh<00:06:20.800> paid<00:06:21.039> a<00:06:21.160> lot<00:06:21.280> of<00:06:21.440> attention<00:06:21.800> to<00:06:22.440> so 00:06:22.749 --> 00:06:22.759 align:start position:0% um is uh paid a lot of attention to so 00:06:22.759 --> 00:06:24.629 align:start position:0% um is uh paid a lot of attention to so things<00:06:23.000> like<00:06:23.319> doing<00:06:23.680> things<00:06:23.880> at<00:06:24.120> specific 00:06:24.629 --> 00:06:24.639 align:start position:0% things like doing things at specific 00:06:24.639 --> 00:06:27.589 align:start position:0% things like doing things at specific times<00:06:24.960> or<00:06:25.240> specific<00:06:26.080> intervals<00:06:27.080> uh<00:06:27.240> doing 00:06:27.589 --> 00:06:27.599 align:start position:0% times or specific intervals uh doing 00:06:27.599 --> 00:06:29.589 align:start position:0% times or specific intervals uh doing things<00:06:27.880> based<00:06:28.120> on<00:06:28.319> triggers<00:06:29.000> you<00:06:29.120> can<00:06:29.280> have 00:06:29.589 --> 00:06:29.599 align:start position:0% things based on triggers you can have 00:06:29.599 --> 00:06:32.629 align:start position:0% things based on triggers you can have Market<00:06:30.360> watches<00:06:31.360> um<00:06:31.800> you<00:06:31.919> want<00:06:32.080> to<00:06:32.160> be<00:06:32.280> able<00:06:32.440> to 00:06:32.629 --> 00:06:32.639 align:start position:0% Market watches um you want to be able to 00:06:32.639 --> 00:06:35.070 align:start position:0% Market watches um you want to be able to also<00:06:33.039> protect<00:06:33.520> IP<00:06:34.039> if<00:06:34.160> you<00:06:34.280> have<00:06:34.479> algorithms 00:06:35.070 --> 00:06:35.080 align:start position:0% also protect IP if you have algorithms 00:06:35.080 --> 00:06:36.830 align:start position:0% also protect IP if you have algorithms that<00:06:35.240> you<00:06:35.520> have<00:06:36.160> you<00:06:36.280> don't<00:06:36.440> want<00:06:36.639> those 00:06:36.830 --> 00:06:36.840 align:start position:0% that you have you don't want those 00:06:36.840 --> 00:06:38.990 align:start position:0% that you have you don't want those algorithms<00:06:37.720> you<00:06:37.840> know<00:06:38.000> in<00:06:38.160> the<00:06:38.280> clear<00:06:38.720> on<00:06:38.840> the 00:06:38.990 --> 00:06:39.000 align:start position:0% algorithms you know in the clear on the 00:06:39.000 --> 00:06:41.110 align:start position:0% algorithms you know in the clear on the blockchain<00:06:39.479> you<00:06:39.599> want<00:06:39.720> to<00:06:39.880> protect<00:06:40.280> those<00:06:41.000> you 00:06:41.110 --> 00:06:41.120 align:start position:0% blockchain you want to protect those you 00:06:41.120 --> 00:06:42.830 align:start position:0% blockchain you want to protect those you might<00:06:41.280> want<00:06:41.440> to<00:06:41.680> scale<00:06:42.080> an<00:06:42.280> algorithm<00:06:42.759> you 00:06:42.830 --> 00:06:42.840 align:start position:0% might want to scale an algorithm you 00:06:42.840 --> 00:06:44.070 align:start position:0% might want to scale an algorithm you might<00:06:43.000> want<00:06:43.120> to<00:06:43.240> have<00:06:43.400> better<00:06:43.680> performance 00:06:44.070 --> 00:06:44.080 align:start position:0% might want to have better performance 00:06:44.080 --> 00:06:46.510 align:start position:0% might want to have better performance than<00:06:44.240> a<00:06:44.479> blockchain<00:06:45.479> uh<00:06:45.680> can<00:06:45.919> offer<00:06:46.199> you<00:06:46.440> how 00:06:46.510 --> 00:06:46.520 align:start position:0% than a blockchain uh can offer you how 00:06:46.520 --> 00:06:49.150 align:start position:0% than a blockchain uh can offer you how do<00:06:46.639> you<00:06:46.840> achieve<00:06:47.319> that<00:06:47.919> while<00:06:48.520> still<00:06:48.880> getting 00:06:49.150 --> 00:06:49.160 align:start position:0% do you achieve that while still getting 00:06:49.160 --> 00:06:51.830 align:start position:0% do you achieve that while still getting the<00:06:49.280> benefit<00:06:49.639> of<00:06:49.759> a<00:06:49.880> distributed<00:06:50.680> Ledger<00:06:51.680> and 00:06:51.830 --> 00:06:51.840 align:start position:0% the benefit of a distributed Ledger and 00:06:51.840 --> 00:06:53.830 align:start position:0% the benefit of a distributed Ledger and then<00:06:52.199> complex<00:06:52.639> interactions<00:06:53.280> when<00:06:53.440> we<00:06:53.639> start 00:06:53.830 --> 00:06:53.840 align:start position:0% then complex interactions when we start 00:06:53.840 --> 00:06:56.029 align:start position:0% then complex interactions when we start getting<00:06:54.080> into<00:06:54.360> Enterprise<00:06:54.840> systems<00:06:55.720> you<00:06:55.879> get 00:06:56.029 --> 00:06:56.039 align:start position:0% getting into Enterprise systems you get 00:06:56.039 --> 00:06:58.430 align:start position:0% getting into Enterprise systems you get into<00:06:56.360> complex<00:06:57.199> uh<00:06:57.360> distributed<00:06:57.879> transaction 00:06:58.430 --> 00:06:58.440 align:start position:0% into complex uh distributed transaction 00:06:58.440 --> 00:06:59.950 align:start position:0% into complex uh distributed transaction coordination<00:06:59.280> where<00:06:59.599> you're<00:06:59.680> not<00:06:59.840> just 00:06:59.950 --> 00:06:59.960 align:start position:0% coordination where you're not just 00:06:59.960 --> 00:07:02.350 align:start position:0% coordination where you're not just updating<00:07:00.319> an<00:07:00.520> ethereum<00:07:01.280> Network<00:07:02.080> you<00:07:02.199> might 00:07:02.350 --> 00:07:02.360 align:start position:0% updating an ethereum Network you might 00:07:02.360 --> 00:07:05.629 align:start position:0% updating an ethereum Network you might be<00:07:02.479> updating<00:07:02.879> a<00:07:03.000> CRM<00:07:03.680> system<00:07:04.680> uh<00:07:04.960> old<00:07:05.280> host 00:07:05.629 --> 00:07:05.639 align:start position:0% be updating a CRM system uh old host 00:07:05.639 --> 00:07:09.070 align:start position:0% be updating a CRM system uh old host mainframe<00:07:06.360> system<00:07:07.080> an<00:07:07.240> Oracle<00:07:07.879> database<00:07:08.879> a 00:07:09.070 --> 00:07:09.080 align:start position:0% mainframe system an Oracle database a 00:07:09.080 --> 00:07:11.629 align:start position:0% mainframe system an Oracle database a CRM<00:07:09.720> system<00:07:10.319> and<00:07:10.479> the<00:07:10.639> ethereum<00:07:11.120> blockchain 00:07:11.629 --> 00:07:11.639 align:start position:0% CRM system and the ethereum blockchain 00:07:11.639 --> 00:07:13.909 align:start position:0% CRM system and the ethereum blockchain system<00:07:11.960> in<00:07:12.120> a<00:07:12.240> single<00:07:12.680> transaction<00:07:13.680> how<00:07:13.800> do 00:07:13.909 --> 00:07:13.919 align:start position:0% system in a single transaction how do 00:07:13.919 --> 00:07:15.869 align:start position:0% system in a single transaction how do you<00:07:14.080> do<00:07:14.360> that<00:07:14.960> well<00:07:15.120> we<00:07:15.240> actually<00:07:15.440> know<00:07:15.680> how<00:07:15.759> to 00:07:15.869 --> 00:07:15.879 align:start position:0% you do that well we actually know how to 00:07:15.879 --> 00:07:17.230 align:start position:0% you do that well we actually know how to do<00:07:16.080> that<00:07:16.240> and<00:07:16.360> that<00:07:16.520> technolog<00:07:16.960> has<00:07:17.080> been 00:07:17.230 --> 00:07:17.240 align:start position:0% do that and that technolog has been 00:07:17.240 --> 00:07:18.550 align:start position:0% do that and that technolog has been around<00:07:17.479> since<00:07:17.680> the<00:07:17.800> Turning<00:07:18.160> part<00:07:18.319> of<00:07:18.440> the 00:07:18.550 --> 00:07:18.560 align:start position:0% around since the Turning part of the 00:07:18.560 --> 00:07:20.589 align:start position:0% around since the Turning part of the century<00:07:19.560> uh<00:07:19.680> because<00:07:19.879> we<00:07:20.039> had<00:07:20.160> to<00:07:20.280> go<00:07:20.400> through 00:07:20.589 --> 00:07:20.599 align:start position:0% century uh because we had to go through 00:07:20.599 --> 00:07:22.830 align:start position:0% century uh because we had to go through those<00:07:20.759> gr<00:07:21.120> pains<00:07:21.560> when<00:07:21.680> we<00:07:21.759> went<00:07:21.879> to<00:07:22.000> the<00:07:22.120> web 00:07:22.830 --> 00:07:22.840 align:start position:0% those gr pains when we went to the web 00:07:22.840 --> 00:07:24.350 align:start position:0% those gr pains when we went to the web so<00:07:23.000> we<00:07:23.080> want<00:07:23.199> to<00:07:23.280> be<00:07:23.360> able<00:07:23.560> to<00:07:23.759> use<00:07:24.080> those 00:07:24.350 --> 00:07:24.360 align:start position:0% so we want to be able to use those 00:07:24.360 --> 00:07:27.309 align:start position:0% so we want to be able to use those things<00:07:25.080> and<00:07:25.240> also<00:07:25.520> use<00:07:25.800> libraries<00:07:26.440> like<00:07:27.080> net 00:07:27.309 --> 00:07:27.319 align:start position:0% things and also use libraries like net 00:07:27.319 --> 00:07:29.589 align:start position:0% things and also use libraries like net and<00:07:27.520> Java<00:07:28.000> and<00:07:28.400> you<00:07:28.520> know<00:07:28.759> pick<00:07:28.960> your<00:07:29.240> your 00:07:29.589 --> 00:07:29.599 align:start position:0% and Java and you know pick your your 00:07:29.599 --> 00:07:31.710 align:start position:0% and Java and you know pick your your platform<00:07:30.039> is<00:07:30.199> yours<00:07:30.639> not<00:07:30.960> just<00:07:31.199> going<00:07:31.319> to<00:07:31.479> be 00:07:31.710 --> 00:07:31.720 align:start position:0% platform is yours not just going to be 00:07:31.720 --> 00:07:34.230 align:start position:0% platform is yours not just going to be about<00:07:32.680> uh<00:07:32.840> single<00:07:33.199> language<00:07:33.639> develop<00:07:33.960> it<00:07:34.160> we 00:07:34.230 --> 00:07:34.240 align:start position:0% about uh single language develop it we 00:07:34.240 --> 00:07:36.350 align:start position:0% about uh single language develop it we need<00:07:34.479> choice<00:07:35.240> choice<00:07:35.479> in<00:07:35.759> platform<00:07:36.199> and 00:07:36.350 --> 00:07:36.360 align:start position:0% need choice choice in platform and 00:07:36.360 --> 00:07:38.510 align:start position:0% need choice choice in platform and choice<00:07:36.599> in<00:07:36.800> language<00:07:37.800> so<00:07:37.960> I'll<00:07:38.120> put<00:07:38.280> this<00:07:38.360> in 00:07:38.510 --> 00:07:38.520 align:start position:0% choice in language so I'll put this in 00:07:38.520 --> 00:07:39.430 align:start position:0% choice in language so I'll put this in here<00:07:38.639> I'm<00:07:38.720> not<00:07:38.800> going<00:07:38.879> to<00:07:39.000> go<00:07:39.080> through<00:07:39.240> this 00:07:39.430 --> 00:07:39.440 align:start position:0% here I'm not going to go through this 00:07:39.440 --> 00:07:41.589 align:start position:0% here I'm not going to go through this chart<00:07:39.960> um<00:07:40.120> some<00:07:40.240> of<00:07:40.319> the<00:07:40.440> things<00:07:40.599> that<00:07:40.800> criet 00:07:41.589 --> 00:07:41.599 align:start position:0% chart um some of the things that criet 00:07:41.599 --> 00:07:44.189 align:start position:0% chart um some of the things that criet uh<00:07:41.720> I'll<00:07:41.879> go<00:07:42.000> through<00:07:42.199> the<00:07:42.360> key<00:07:42.800> points<00:07:43.800> uh<00:07:43.879> for 00:07:44.189 --> 00:07:44.199 align:start position:0% uh I'll go through the key points uh for 00:07:44.199 --> 00:07:46.950 align:start position:0% uh I'll go through the key points uh for this<00:07:44.400> audience<00:07:45.199> um<00:07:45.560> getting<00:07:45.800> secure<00:07:46.199> data<00:07:46.680> and 00:07:46.950 --> 00:07:46.960 align:start position:0% this audience um getting secure data and 00:07:46.960 --> 00:07:48.550 align:start position:0% this audience um getting secure data and oracles<00:07:47.440> have<00:07:47.599> been<00:07:47.720> around<00:07:47.960> for<00:07:48.120> some<00:07:48.360> time 00:07:48.550 --> 00:07:48.560 align:start position:0% oracles have been around for some time 00:07:48.560 --> 00:07:50.149 align:start position:0% oracles have been around for some time it's<00:07:48.759> still<00:07:48.960> A<00:07:49.080> New<00:07:49.319> Concept<00:07:49.639> for<00:07:49.800> a<00:07:49.879> lot<00:07:50.000> of 00:07:50.149 --> 00:07:50.159 align:start position:0% it's still A New Concept for a lot of 00:07:50.159 --> 00:07:52.270 align:start position:0% it's still A New Concept for a lot of people<00:07:50.759> how<00:07:50.879> do<00:07:50.960> you<00:07:51.080> get<00:07:51.240> real<00:07:51.479> world<00:07:51.800> data<00:07:52.080> in 00:07:52.270 --> 00:07:52.280 align:start position:0% people how do you get real world data in 00:07:52.280 --> 00:07:55.510 align:start position:0% people how do you get real world data in there<00:07:53.000> uh<00:07:53.120> oracles<00:07:54.039> um<00:07:54.840> really<00:07:55.039> don't<00:07:55.280> provide 00:07:55.510 --> 00:07:55.520 align:start position:0% there uh oracles um really don't provide 00:07:55.520 --> 00:07:56.909 align:start position:0% there uh oracles um really don't provide a<00:07:55.639> standard<00:07:56.080> way<00:07:56.199> for<00:07:56.360> you<00:07:56.440> to<00:07:56.599> have 00:07:56.909 --> 00:07:56.919 align:start position:0% a standard way for you to have 00:07:56.919 --> 00:07:59.670 align:start position:0% a standard way for you to have attestation<00:07:57.639> of<00:07:57.800> that<00:07:57.960> data<00:07:58.639> cets<00:07:59.120> provide 00:07:59.670 --> 00:07:59.680 align:start position:0% attestation of that data cets provide 00:07:59.680 --> 00:08:02.029 align:start position:0% attestation of that data cets provide that<00:07:59.800> to<00:07:59.960> you<00:08:00.280> by<00:08:00.440> default<00:08:01.240> but<00:08:01.360> criet<00:08:01.759> does 00:08:02.029 --> 00:08:02.039 align:start position:0% that to you by default but criet does 00:08:02.039 --> 00:08:03.869 align:start position:0% that to you by default but criet does more<00:08:02.240> than<00:08:02.440> that<00:08:03.000> it's<00:08:03.159> more<00:08:03.319> than<00:08:03.560> secure 00:08:03.869 --> 00:08:03.879 align:start position:0% more than that it's more than secure 00:08:03.879 --> 00:08:06.670 align:start position:0% more than that it's more than secure data<00:08:04.159> it's<00:08:04.319> also<00:08:04.639> secure<00:08:05.319> execution<00:08:06.319> how<00:08:06.520> can 00:08:06.670 --> 00:08:06.680 align:start position:0% data it's also secure execution how can 00:08:06.680 --> 00:08:09.909 align:start position:0% data it's also secure execution how can you<00:08:07.000> enlist<00:08:07.879> complex<00:08:08.440> execution<00:08:09.120> tasks<00:08:09.680> off 00:08:09.909 --> 00:08:09.919 align:start position:0% you enlist complex execution tasks off 00:08:09.919 --> 00:08:12.510 align:start position:0% you enlist complex execution tasks off the<00:08:10.159> chain<00:08:11.159> while<00:08:11.639> uh<00:08:11.759> keeping<00:08:12.120> that 00:08:12.510 --> 00:08:12.520 align:start position:0% the chain while uh keeping that 00:08:12.520 --> 00:08:15.309 align:start position:0% the chain while uh keeping that integrated<00:08:13.520> uh<00:08:13.680> developer<00:08:14.680> um<00:08:14.840> and<00:08:15.000> business 00:08:15.309 --> 00:08:15.319 align:start position:0% integrated uh developer um and business 00:08:15.319 --> 00:08:17.749 align:start position:0% integrated uh developer um and business and<00:08:15.560> operational<00:08:16.240> experience<00:08:17.240> and<00:08:17.400> also 00:08:17.749 --> 00:08:17.759 align:start position:0% and operational experience and also 00:08:17.759 --> 00:08:20.110 align:start position:0% and operational experience and also create<00:08:18.080> a<00:08:18.280> Marketplace<00:08:19.280> uh<00:08:19.360> for<00:08:19.599> developers 00:08:20.110 --> 00:08:20.120 align:start position:0% create a Marketplace uh for developers 00:08:20.120 --> 00:08:22.149 align:start position:0% create a Marketplace uh for developers in<00:08:20.319> this<00:08:20.520> audience<00:08:21.400> you<00:08:21.520> might<00:08:21.759> come<00:08:21.919> up<00:08:22.039> with 00:08:22.149 --> 00:08:22.159 align:start position:0% in this audience you might come up with 00:08:22.159 --> 00:08:24.270 align:start position:0% in this audience you might come up with criet<00:08:22.639> ideas<00:08:23.039> to<00:08:23.199> create<00:08:23.400> a<00:08:23.560> cripp<00:08:23.879> library 00:08:24.270 --> 00:08:24.280 align:start position:0% criet ideas to create a cripp library 00:08:24.280 --> 00:08:25.629 align:start position:0% criet ideas to create a cripp library that<00:08:24.360> you<00:08:24.440> can<00:08:24.560> put<00:08:24.680> in<00:08:24.759> the<00:08:24.879> marketplace<00:08:25.440> and 00:08:25.629 --> 00:08:25.639 align:start position:0% that you can put in the marketplace and 00:08:25.639 --> 00:08:28.189 align:start position:0% that you can put in the marketplace and sell<00:08:26.360> to<00:08:26.520> a<00:08:26.680> specific<00:08:27.120> industry<00:08:27.759> they<00:08:27.879> can<00:08:28.000> be 00:08:28.189 --> 00:08:28.199 align:start position:0% sell to a specific industry they can be 00:08:28.199 --> 00:08:32.190 align:start position:0% sell to a specific industry they can be vertical<00:08:28.919> and<00:08:29.080> hor<00:08:29.720> Al<00:08:29.800> in<00:08:30.240> nature<00:08:31.240> so<00:08:32.000> there's 00:08:32.190 --> 00:08:32.200 align:start position:0% vertical and hor Al in nature so there's 00:08:32.200 --> 00:08:34.750 align:start position:0% vertical and hor Al in nature so there's a<00:08:32.320> lot<00:08:32.440> of<00:08:32.599> infrastructure<00:08:33.240> here<00:08:33.880> um<00:08:34.560> that 00:08:34.750 --> 00:08:34.760 align:start position:0% a lot of infrastructure here um that 00:08:34.760 --> 00:08:37.149 align:start position:0% a lot of infrastructure here um that that<00:08:34.839> we're<00:08:35.000> building<00:08:35.959> uh<00:08:36.120> to<00:08:36.440> to<00:08:36.599> wire<00:08:36.959> this 00:08:37.149 --> 00:08:37.159 align:start position:0% that we're building uh to to wire this 00:08:37.159 --> 00:08:41.070 align:start position:0% that we're building uh to to wire this up<00:08:38.120> uh<00:08:38.240> we<00:08:38.360> are<00:08:38.599> making<00:08:39.479> um<00:08:40.240> our<00:08:40.440> goal<00:08:40.680> is<00:08:40.880> for 00:08:41.070 --> 00:08:41.080 align:start position:0% up uh we are making um our goal is for 00:08:41.080 --> 00:08:43.269 align:start position:0% up uh we are making um our goal is for the<00:08:41.279> criet<00:08:41.839> fabric<00:08:42.519> is<00:08:42.680> what<00:08:42.839> we're<00:08:43.000> calling 00:08:43.269 --> 00:08:43.279 align:start position:0% the criet fabric is what we're calling 00:08:43.279 --> 00:08:46.509 align:start position:0% the criet fabric is what we're calling it<00:08:43.440> or<00:08:43.640> the<00:08:44.200> the<00:08:44.399> blockchain<00:08:44.839> criet<00:08:45.360> fabric<00:08:46.360> to 00:08:46.509 --> 00:08:46.519 align:start position:0% it or the the blockchain criet fabric to 00:08:46.519 --> 00:08:48.790 align:start position:0% it or the the blockchain criet fabric to be<00:08:46.720> easily<00:08:47.480> uh<00:08:47.600> consumed<00:08:48.080> by<00:08:48.240> developers<00:08:48.680> so 00:08:48.790 --> 00:08:48.800 align:start position:0% be easily uh consumed by developers so 00:08:48.800 --> 00:08:51.389 align:start position:0% be easily uh consumed by developers so you'll<00:08:48.959> be<00:08:49.120> simply<00:08:49.480> being<00:08:50.000> able<00:08:50.240> to<00:08:50.440> make<00:08:51.320> uh 00:08:51.389 --> 00:08:51.399 align:start position:0% you'll be simply being able to make uh 00:08:51.399 --> 00:08:54.350 align:start position:0% you'll be simply being able to make uh or<00:08:51.839> discover<00:08:52.440> cets<00:08:52.880> out<00:08:53.000> on<00:08:53.120> the<00:08:53.200> market<00:08:53.640> place 00:08:54.350 --> 00:08:54.360 align:start position:0% or discover cets out on the market place 00:08:54.360 --> 00:08:57.310 align:start position:0% or discover cets out on the market place references<00:08:54.880> to<00:08:55.080> them<00:08:56.000> um<00:08:56.560> declaratively 00:08:57.310 --> 00:08:57.320 align:start position:0% references to them um declaratively 00:08:57.320 --> 00:08:59.110 align:start position:0% references to them um declaratively State<00:08:57.640> what<00:08:57.760> you<00:08:57.880> want<00:08:58.040> to<00:08:58.160> do<00:08:58.360> in<00:08:58.680> code<00:08:58.959> with 00:08:59.110 --> 00:08:59.120 align:start position:0% State what you want to do in code with 00:08:59.120 --> 00:09:01.470 align:start position:0% State what you want to do in code with those<00:08:59.640> cets<00:09:00.640> um<00:09:00.800> and<00:09:01.000> have<00:09:01.320> the 00:09:01.470 --> 00:09:01.480 align:start position:0% those cets um and have the 00:09:01.480 --> 00:09:04.150 align:start position:0% those cets um and have the infrastructure<00:09:02.160> just<00:09:02.600> work<00:09:03.600> uh<00:09:03.720> and<00:09:03.839> you<00:09:04.000> be 00:09:04.150 --> 00:09:04.160 align:start position:0% infrastructure just work uh and you be 00:09:04.160 --> 00:09:06.190 align:start position:0% infrastructure just work uh and you be able<00:09:04.360> to<00:09:04.600> focus<00:09:05.000> on<00:09:05.279> getting<00:09:05.519> your<00:09:05.720> code<00:09:06.000> to 00:09:06.190 --> 00:09:06.200 align:start position:0% able to focus on getting your code to 00:09:06.200 --> 00:09:07.949 align:start position:0% able to focus on getting your code to run<00:09:06.560> and<00:09:06.760> accomplish<00:09:07.200> the<00:09:07.399> business<00:09:07.680> goals 00:09:07.949 --> 00:09:07.959 align:start position:0% run and accomplish the business goals 00:09:07.959 --> 00:09:11.030 align:start position:0% run and accomplish the business goals that<00:09:08.120> you<00:09:08.760> trying<00:09:09.079> to<00:09:09.399> build<00:09:10.399> so<00:09:10.560> the<00:09:10.720> goal 00:09:11.030 --> 00:09:11.040 align:start position:0% that you trying to build so the goal 00:09:11.040 --> 00:09:12.910 align:start position:0% that you trying to build so the goal here<00:09:11.560> um<00:09:11.880> and<00:09:12.040> this<00:09:12.200> diagram<00:09:12.600> is 00:09:12.910 --> 00:09:12.920 align:start position:0% here um and this diagram is 00:09:12.920 --> 00:09:14.949 align:start position:0% here um and this diagram is oversimplified<00:09:13.920> greatly<00:09:14.320> down<00:09:14.480> on<00:09:14.600> the<00:09:14.760> right 00:09:14.949 --> 00:09:14.959 align:start position:0% oversimplified greatly down on the right 00:09:14.959 --> 00:09:17.590 align:start position:0% oversimplified greatly down on the right hand<00:09:15.120> side<00:09:15.320> we<00:09:15.480> have<00:09:15.600> a<00:09:15.720> node<00:09:16.120> this<00:09:16.240> is<00:09:16.360> the<00:09:16.600> evm 00:09:17.590 --> 00:09:17.600 align:start position:0% hand side we have a node this is the evm 00:09:17.600 --> 00:09:18.870 align:start position:0% hand side we have a node this is the evm that<00:09:17.760> has<00:09:17.880> this<00:09:18.079> thing<00:09:18.240> called<00:09:18.399> a<00:09:18.519> crypto 00:09:18.870 --> 00:09:18.880 align:start position:0% that has this thing called a crypto 00:09:18.880 --> 00:09:20.670 align:start position:0% that has this thing called a crypto delegate<00:09:19.320> which<00:09:19.480> handles<00:09:19.839> the<00:09:20.040> delegation<00:09:20.480> of 00:09:20.670 --> 00:09:20.680 align:start position:0% delegate which handles the delegation of 00:09:20.680 --> 00:09:23.949 align:start position:0% delegate which handles the delegation of calls<00:09:21.000> out<00:09:21.160> to<00:09:21.320> the<00:09:21.640> cets<00:09:22.640> uh<00:09:22.800> criet<00:09:23.399> manage 00:09:23.949 --> 00:09:23.959 align:start position:0% calls out to the cets uh criet manage 00:09:23.959 --> 00:09:26.389 align:start position:0% calls out to the cets uh criet manage the<00:09:24.160> entire<00:09:24.920> uh<00:09:25.079> security<00:09:25.560> envelope<00:09:26.079> so<00:09:26.240> we're 00:09:26.389 --> 00:09:26.399 align:start position:0% the entire uh security envelope so we're 00:09:26.399 --> 00:09:28.710 align:start position:0% the entire uh security envelope so we're essentially<00:09:26.880> extending<00:09:27.399> the<00:09:27.519> trust<00:09:27.920> envelope 00:09:28.710 --> 00:09:28.720 align:start position:0% essentially extending the trust envelope 00:09:28.720 --> 00:09:31.630 align:start position:0% essentially extending the trust envelope for<00:09:28.920> not<00:09:29.079> just<00:09:29.480> data<00:09:30.200> but<00:09:30.480> execution<00:09:31.440> which 00:09:31.630 --> 00:09:31.640 align:start position:0% for not just data but execution which 00:09:31.640 --> 00:09:33.150 align:start position:0% for not just data but execution which gives<00:09:31.800> you<00:09:32.040> lots<00:09:32.240> of<00:09:32.440> interesting<00:09:32.920> things 00:09:33.150 --> 00:09:33.160 align:start position:0% gives you lots of interesting things 00:09:33.160 --> 00:09:34.910 align:start position:0% gives you lots of interesting things that<00:09:33.279> you<00:09:33.360> can<00:09:33.560> do<00:09:34.200> so<00:09:34.360> let's<00:09:34.519> talk<00:09:34.640> about<00:09:34.839> some 00:09:34.910 --> 00:09:34.920 align:start position:0% that you can do so let's talk about some 00:09:34.920 --> 00:09:37.350 align:start position:0% that you can do so let's talk about some of<00:09:35.040> the<00:09:35.160> use<00:09:35.480> cases<00:09:36.320> so<00:09:36.519> the<00:09:36.640> most<00:09:36.880> common<00:09:37.120> one 00:09:37.350 --> 00:09:37.360 align:start position:0% of the use cases so the most common one 00:09:37.360 --> 00:09:39.910 align:start position:0% of the use cases so the most common one people<00:09:37.640> think<00:09:37.880> about<00:09:38.760> are<00:09:38.920> for<00:09:39.160> oracles<00:09:39.760> and 00:09:39.910 --> 00:09:39.920 align:start position:0% people think about are for oracles and 00:09:39.920 --> 00:09:41.910 align:start position:0% people think about are for oracles and this<00:09:40.000> is<00:09:40.160> where<00:09:40.360> you're<00:09:40.560> going<00:09:40.880> to<00:09:41.200> want<00:09:41.640> your 00:09:41.910 --> 00:09:41.920 align:start position:0% this is where you're going to want your 00:09:41.920 --> 00:09:44.550 align:start position:0% this is where you're going to want your smart<00:09:42.360> contract<00:09:43.360> to<00:09:43.519> do<00:09:43.760> something<00:09:44.120> based<00:09:44.399> on 00:09:44.550 --> 00:09:44.560 align:start position:0% smart contract to do something based on 00:09:44.560 --> 00:09:46.829 align:start position:0% smart contract to do something based on an<00:09:44.760> event<00:09:45.160> so<00:09:45.360> it's<00:09:45.480> a<00:09:45.600> traditional<00:09:46.120> Pub<00:09:46.480> sub 00:09:46.829 --> 00:09:46.839 align:start position:0% an event so it's a traditional Pub sub 00:09:46.839 --> 00:09:49.269 align:start position:0% an event so it's a traditional Pub sub type<00:09:47.440> model<00:09:48.440> where<00:09:48.560> you're<00:09:48.720> going<00:09:48.839> to<00:09:49.000> go<00:09:49.120> and 00:09:49.269 --> 00:09:49.279 align:start position:0% type model where you're going to go and 00:09:49.279 --> 00:09:52.190 align:start position:0% type model where you're going to go and say<00:09:49.680> hey<00:09:50.000> I<00:09:50.079> need<00:09:50.320> to<00:09:50.800> um<00:09:51.560> uh<00:09:51.720> I<00:09:51.800> want<00:09:51.880> to<00:09:52.040> have 00:09:52.190 --> 00:09:52.200 align:start position:0% say hey I need to um uh I want to have 00:09:52.200 --> 00:09:54.150 align:start position:0% say hey I need to um uh I want to have this<00:09:52.399> criet<00:09:52.880> do<00:09:53.040> something<00:09:53.440> for<00:09:53.600> me<00:09:53.800> in<00:09:53.920> this 00:09:54.150 --> 00:09:54.160 align:start position:0% this criet do something for me in this 00:09:54.160 --> 00:09:55.949 align:start position:0% this criet do something for me in this case<00:09:54.839> down<00:09:55.000> here<00:09:55.079> in<00:09:55.200> the<00:09:55.360> code<00:09:55.640> which<00:09:55.760> you 00:09:55.949 --> 00:09:55.959 align:start position:0% case down here in the code which you 00:09:55.959 --> 00:09:58.910 align:start position:0% case down here in the code which you can't<00:09:56.440> read<00:09:57.440> but<00:09:57.760> uh<00:09:57.880> we<00:09:58.000> have<00:09:58.120> a<00:09:58.279> little<00:09:58.760> uh 00:09:58.910 --> 00:09:58.920 align:start position:0% can't read but uh we have a little uh 00:09:58.920 --> 00:10:00.670 align:start position:0% can't read but uh we have a little uh attribute<00:09:59.560> here<00:09:59.760> where<00:09:59.920> we're<00:10:00.200> subscribing 00:10:00.670 --> 00:10:00.680 align:start position:0% attribute here where we're subscribing 00:10:00.680 --> 00:10:04.389 align:start position:0% attribute here where we're subscribing to<00:10:00.839> an<00:10:01.000> event<00:10:01.680> saying<00:10:02.040> wake<00:10:02.240> me<00:10:02.440> up<00:10:03.160> at<00:10:03.680> 4:00 00:10:04.389 --> 00:10:04.399 align:start position:0% to an event saying wake me up at 4:00 00:10:04.399 --> 00:10:07.430 align:start position:0% to an event saying wake me up at 4:00 Eastern<00:10:04.839> Standard<00:10:05.680> Time<00:10:06.680> if<00:10:06.880> the<00:10:07.000> markets 00:10:07.430 --> 00:10:07.440 align:start position:0% Eastern Standard Time if the markets 00:10:07.440 --> 00:10:10.069 align:start position:0% Eastern Standard Time if the markets were<00:10:07.680> open<00:10:08.000> that<00:10:08.200> day<00:10:08.640> and<00:10:08.800> if<00:10:08.959> they<00:10:09.120> were<00:10:09.440> open 00:10:10.069 --> 00:10:10.079 align:start position:0% were open that day and if they were open 00:10:10.079 --> 00:10:12.630 align:start position:0% were open that day and if they were open give<00:10:10.240> me<00:10:10.399> the<00:10:10.519> liable<00:10:10.959> rate<00:10:11.160> and<00:10:11.320> the<00:10:11.480> price<00:10:11.680> of 00:10:12.630 --> 00:10:12.640 align:start position:0% give me the liable rate and the price of 00:10:12.640 --> 00:10:15.350 align:start position:0% give me the liable rate and the price of gold<00:10:13.640> and<00:10:14.079> what's<00:10:14.240> going<00:10:14.360> to<00:10:14.519> happen<00:10:14.760> is<00:10:15.040> that 00:10:15.350 --> 00:10:15.360 align:start position:0% gold and what's going to happen is that 00:10:15.360 --> 00:10:17.430 align:start position:0% gold and what's going to happen is that a<00:10:15.560> subscription<00:10:16.079> goes<00:10:16.360> up<00:10:16.600> the<00:10:16.720> criet<00:10:17.120> gets 00:10:17.430 --> 00:10:17.440 align:start position:0% a subscription goes up the criet gets 00:10:17.440 --> 00:10:20.230 align:start position:0% a subscription goes up the criet gets the<00:10:18.079> the<00:10:18.200> rules<00:10:18.519> for<00:10:19.120> waking<00:10:19.480> up<00:10:19.680> that<00:10:19.880> smart 00:10:20.230 --> 00:10:20.240 align:start position:0% the the rules for waking up that smart 00:10:20.240 --> 00:10:22.389 align:start position:0% the the rules for waking up that smart contract<00:10:20.640> and<00:10:20.800> says<00:10:21.160> okay<00:10:21.760> I'll<00:10:22.000> wake<00:10:22.160> you<00:10:22.279> up 00:10:22.389 --> 00:10:22.399 align:start position:0% contract and says okay I'll wake you up 00:10:22.399 --> 00:10:24.710 align:start position:0% contract and says okay I'll wake you up when<00:10:22.519> it's<00:10:22.640> 4:00<00:10:23.480> if<00:10:23.600> the<00:10:23.680> markets<00:10:24.000> are<00:10:24.200> open 00:10:24.710 --> 00:10:24.720 align:start position:0% when it's 4:00 if the markets are open 00:10:24.720 --> 00:10:27.870 align:start position:0% when it's 4:00 if the markets are open the<00:10:24.880> price<00:10:25.120> of<00:10:25.480> gold<00:10:25.800> and<00:10:25.959> the<00:10:26.079> liable<00:10:26.480> rate<00:10:27.440> so 00:10:27.870 --> 00:10:27.880 align:start position:0% the price of gold and the liable rate so 00:10:27.880 --> 00:10:29.630 align:start position:0% the price of gold and the liable rate so the<00:10:28.000> criet<00:10:28.399> sits<00:10:28.640> there<00:10:28.720> and<00:10:28.839> runs<00:10:29.079> and<00:10:29.320> EV 00:10:29.630 --> 00:10:29.640 align:start position:0% the criet sits there and runs and EV 00:10:29.640 --> 00:10:32.030 align:start position:0% the criet sits there and runs and EV checks<00:10:30.200> and<00:10:30.480> when<00:10:30.680> the<00:10:31.160> event<00:10:31.600> conditions<00:10:31.839> are 00:10:32.030 --> 00:10:32.040 align:start position:0% checks and when the event conditions are 00:10:32.040 --> 00:10:34.670 align:start position:0% checks and when the event conditions are correct<00:10:32.560> it<00:10:32.680> fires<00:10:33.160> the<00:10:33.320> event<00:10:34.240> the<00:10:34.360> event 00:10:34.670 --> 00:10:34.680 align:start position:0% correct it fires the event the event 00:10:34.680 --> 00:10:37.790 align:start position:0% correct it fires the event the event payload<00:10:35.279> includes<00:10:35.839> an<00:10:36.279> attested<00:10:37.279> value<00:10:37.639> of 00:10:37.790 --> 00:10:37.800 align:start position:0% payload includes an attested value of 00:10:37.800 --> 00:10:40.670 align:start position:0% payload includes an attested value of the<00:10:37.920> Lial<00:10:38.399> rate<00:10:39.040> and<00:10:39.200> the<00:10:39.360> price<00:10:39.560> of<00:10:39.760> gold<00:10:40.560> now 00:10:40.670 --> 00:10:40.680 align:start position:0% the Lial rate and the price of gold now 00:10:40.680 --> 00:10:42.750 align:start position:0% the Lial rate and the price of gold now you<00:10:40.800> not<00:10:41.079> just<00:10:41.200> get<00:10:41.360> the<00:10:41.560> values<00:10:42.040> but<00:10:42.160> you<00:10:42.360> also 00:10:42.750 --> 00:10:42.760 align:start position:0% you not just get the values but you also 00:10:42.760 --> 00:10:46.550 align:start position:0% you not just get the values but you also get<00:10:43.760> a<00:10:43.880> three-way<00:10:44.680> attestation<00:10:45.680> you<00:10:45.839> get<00:10:46.079> the 00:10:46.550 --> 00:10:46.560 align:start position:0% get a three-way attestation you get the 00:10:46.560 --> 00:10:49.470 align:start position:0% get a three-way attestation you get the uh<00:10:46.720> signature<00:10:47.200> of<00:10:47.360> the<00:10:47.480> criet<00:10:48.040> itself<00:10:49.040> you<00:10:49.200> get 00:10:49.470 --> 00:10:49.480 align:start position:0% uh signature of the criet itself you get 00:10:49.480 --> 00:10:51.509 align:start position:0% uh signature of the criet itself you get the<00:10:49.760> signature<00:10:50.279> of<00:10:50.440> The<00:10:50.600> Enclave<00:10:51.240> which<00:10:51.360> I'll 00:10:51.509 --> 00:10:51.519 align:start position:0% the signature of The Enclave which I'll 00:10:51.519 --> 00:10:53.990 align:start position:0% the signature of The Enclave which I'll talk<00:10:51.720> about<00:10:51.959> here<00:10:52.040> in<00:10:52.160> a<00:10:52.279> moment<00:10:53.120> and<00:10:53.440> also<00:10:53.839> the 00:10:53.990 --> 00:10:54.000 align:start position:0% talk about here in a moment and also the 00:10:54.000 --> 00:10:57.269 align:start position:0% talk about here in a moment and also the attested<00:10:54.440> Hoster<00:10:55.200> so<00:10:55.440> you<00:10:55.680> have<00:10:56.399> this<00:10:56.800> trust 00:10:57.269 --> 00:10:57.279 align:start position:0% attested Hoster so you have this trust 00:10:57.279 --> 00:10:59.750 align:start position:0% attested Hoster so you have this trust envelope<00:10:57.800> which<00:10:57.920> is<00:10:58.079> actually<00:10:58.720> sealed 00:10:59.750 --> 00:10:59.760 align:start position:0% envelope which is actually sealed 00:10:59.760 --> 00:11:02.069 align:start position:0% envelope which is actually sealed um<00:11:00.040> and<00:11:00.360> you<00:11:00.519> can<00:11:00.959> uh<00:11:01.079> record<00:11:01.560> all<00:11:01.800> that<00:11:01.920> in<00:11:01.959> the 00:11:02.069 --> 00:11:02.079 align:start position:0% um and you can uh record all that in the 00:11:02.079 --> 00:11:04.470 align:start position:0% um and you can uh record all that in the smart<00:11:02.399> contract<00:11:03.200> for<00:11:03.399> audit 00:11:04.470 --> 00:11:04.480 align:start position:0% smart contract for audit 00:11:04.480 --> 00:11:06.670 align:start position:0% smart contract for audit purposes<00:11:05.480> so<00:11:05.680> that<00:11:05.760> one's<00:11:06.000> the<00:11:06.160> easiest<00:11:06.519> one 00:11:06.670 --> 00:11:06.680 align:start position:0% purposes so that one's the easiest one 00:11:06.680 --> 00:11:07.910 align:start position:0% purposes so that one's the easiest one to<00:11:06.839> kind<00:11:06.959> of<00:11:07.079> get<00:11:07.200> your<00:11:07.360> head<00:11:07.519> around<00:11:07.800> the 00:11:07.910 --> 00:11:07.920 align:start position:0% to kind of get your head around the 00:11:07.920 --> 00:11:10.550 align:start position:0% to kind of get your head around the second<00:11:08.120> one's<00:11:08.399> a<00:11:08.480> little<00:11:08.639> bit<00:11:08.800> more<00:11:09.560> advanced 00:11:10.550 --> 00:11:10.560 align:start position:0% second one's a little bit more advanced 00:11:10.560 --> 00:11:12.190 align:start position:0% second one's a little bit more advanced and<00:11:10.720> it's<00:11:10.959> really<00:11:11.360> taking<00:11:11.760> this<00:11:11.920> three- 00:11:12.190 --> 00:11:12.200 align:start position:0% and it's really taking this three- 00:11:12.200 --> 00:11:14.670 align:start position:0% and it's really taking this three- tiered<00:11:12.519> architecture<00:11:13.040> to<00:11:13.279> an<00:11:14.279> a<00:11:14.399> little<00:11:14.560> bit 00:11:14.670 --> 00:11:14.680 align:start position:0% tiered architecture to an a little bit 00:11:14.680 --> 00:11:15.590 align:start position:0% tiered architecture to an a little bit further 00:11:15.590 --> 00:11:15.600 align:start position:0% further 00:11:15.600 --> 00:11:18.350 align:start position:0% further extent<00:11:16.600> um<00:11:16.839> this<00:11:16.959> is<00:11:17.079> what<00:11:17.200> we<00:11:17.360> call<00:11:17.560> control 00:11:18.350 --> 00:11:18.360 align:start position:0% extent um this is what we call control 00:11:18.360 --> 00:11:19.509 align:start position:0% extent um this is what we call control and<00:11:18.480> this<00:11:18.600> is<00:11:18.760> where<00:11:18.920> you're<00:11:19.079> using<00:11:19.360> your 00:11:19.509 --> 00:11:19.519 align:start position:0% and this is where you're using your 00:11:19.519 --> 00:11:22.190 align:start position:0% and this is where you're using your smart<00:11:20.120> contract<00:11:21.120> more<00:11:21.440> as<00:11:21.560> a<00:11:21.720> traditional 00:11:22.190 --> 00:11:22.200 align:start position:0% smart contract more as a traditional 00:11:22.200 --> 00:11:24.310 align:start position:0% smart contract more as a traditional database<00:11:22.920> so<00:11:23.079> your<00:11:23.279> smart<00:11:23.639> contract<00:11:24.040> you're 00:11:24.310 --> 00:11:24.320 align:start position:0% database so your smart contract you're 00:11:24.320 --> 00:11:26.550 align:start position:0% database so your smart contract you're placing<00:11:25.320> uh<00:11:25.399> you're<00:11:25.560> declaring<00:11:26.120> essentially 00:11:26.550 --> 00:11:26.560 align:start position:0% placing uh you're declaring essentially 00:11:26.560 --> 00:11:28.750 align:start position:0% placing uh you're declaring essentially the<00:11:26.720> data<00:11:27.000> that<00:11:27.079> you're<00:11:27.279> keeping<00:11:27.600> track<00:11:27.920> of 00:11:28.750 --> 00:11:28.760 align:start position:0% the data that you're keeping track of 00:11:28.760 --> 00:11:30.389 align:start position:0% the data that you're keeping track of and<00:11:28.880> then<00:11:29.000> the<00:11:29.279> stored<00:11:29.600> procedures<00:11:30.160> if<00:11:30.240> you 00:11:30.389 --> 00:11:30.399 align:start position:0% and then the stored procedures if you 00:11:30.399 --> 00:11:33.750 align:start position:0% and then the stored procedures if you will<00:11:30.959> for<00:11:31.200> updating<00:11:31.800> that<00:11:32.000> data<00:11:32.959> so<00:11:33.519> um<00:11:33.639> you're 00:11:33.750 --> 00:11:33.760 align:start position:0% will for updating that data so um you're 00:11:33.760 --> 00:11:36.190 align:start position:0% will for updating that data so um you're not<00:11:33.880> writing<00:11:34.360> crud<00:11:35.360> functions<00:11:35.880> but<00:11:36.000> you're 00:11:36.190 --> 00:11:36.200 align:start position:0% not writing crud functions but you're 00:11:36.200 --> 00:11:40.310 align:start position:0% not writing crud functions but you're doing<00:11:37.200> um<00:11:37.519> the<00:11:37.760> up<00:11:38.160> uh<00:11:38.320> the<00:11:38.760> insert<00:11:39.760> um<00:11:39.959> or<00:11:40.120> the 00:11:40.310 --> 00:11:40.320 align:start position:0% doing um the up uh the insert um or the 00:11:40.320 --> 00:11:44.310 align:start position:0% doing um the up uh the insert um or the create<00:11:40.839> and<00:11:41.440> um<00:11:41.839> the<00:11:41.959> read<00:11:42.760> functions<00:11:43.360> for<00:11:44.160> the 00:11:44.310 --> 00:11:44.320 align:start position:0% create and um the read functions for the 00:11:44.320 --> 00:11:47.470 align:start position:0% create and um the read functions for the data<00:11:44.600> in<00:11:44.720> the<00:11:44.839> smart<00:11:45.320> contract<00:11:46.320> you<00:11:46.480> are<00:11:46.760> then 00:11:47.470 --> 00:11:47.480 align:start position:0% data in the smart contract you are then 00:11:47.480 --> 00:11:51.550 align:start position:0% data in the smart contract you are then uh<00:11:48.440> enlisting<00:11:49.040> control<00:11:49.480> surrogation<00:11:50.480> so<00:11:50.920> full 00:11:51.550 --> 00:11:51.560 align:start position:0% uh enlisting control surrogation so full 00:11:51.560 --> 00:11:53.710 align:start position:0% uh enlisting control surrogation so full um<00:11:51.680> surrogation<00:11:52.440> of<00:11:52.600> your<00:11:52.839> logic<00:11:53.320> out<00:11:53.480> to<00:11:53.639> the 00:11:53.710 --> 00:11:53.720 align:start position:0% um surrogation of your logic out to the 00:11:53.720 --> 00:11:56.710 align:start position:0% um surrogation of your logic out to the criet<00:11:54.320> itself<00:11:55.320> so<00:11:55.519> the<00:11:55.680> criet<00:11:56.079> can<00:11:56.240> run 00:11:56.710 --> 00:11:56.720 align:start position:0% criet itself so the criet can run 00:11:56.720 --> 00:11:59.509 align:start position:0% criet itself so the criet can run offchain<00:11:57.720> and<00:11:57.839> you<00:11:57.920> can<00:11:58.120> scale<00:11:58.519> it<00:11:58.680> vertically 00:11:59.509 --> 00:11:59.519 align:start position:0% offchain and you can scale it vertically 00:11:59.519 --> 00:12:02.269 align:start position:0% offchain and you can scale it vertically so<00:11:59.680> it<00:11:59.760> won't<00:11:59.959> run<00:12:00.200> on<00:12:00.399> every<00:12:00.639> single<00:12:01.160> node<00:12:02.160> um 00:12:02.269 --> 00:12:02.279 align:start position:0% so it won't run on every single node um 00:12:02.279 --> 00:12:04.990 align:start position:0% so it won't run on every single node um you<00:12:02.399> can<00:12:02.560> have<00:12:02.680> it<00:12:02.800> run<00:12:03.000> on<00:12:03.519> at<00:12:03.639> least<00:12:03.920> one<00:12:04.480> or<00:12:04.880> a 00:12:04.990 --> 00:12:05.000 align:start position:0% you can have it run on at least one or a 00:12:05.000 --> 00:12:07.829 align:start position:0% you can have it run on at least one or a couple<00:12:05.240> of<00:12:05.399> nodes<00:12:06.360> and<00:12:06.519> this<00:12:06.680> usually<00:12:07.000> becomes 00:12:07.829 --> 00:12:07.839 align:start position:0% couple of nodes and this usually becomes 00:12:07.839 --> 00:12:10.870 align:start position:0% couple of nodes and this usually becomes uh<00:12:08.040> attractive<00:12:08.560> to<00:12:09.279> Consortium<00:12:10.279> uh<00:12:10.399> networks 00:12:10.870 --> 00:12:10.880 align:start position:0% uh attractive to Consortium uh networks 00:12:10.880 --> 00:12:13.389 align:start position:0% uh attractive to Consortium uh networks where<00:12:11.040> you<00:12:11.240> have<00:12:11.839> for<00:12:12.000> example<00:12:12.639> a<00:12:12.760> hedge<00:12:13.040> fund 00:12:13.389 --> 00:12:13.399 align:start position:0% where you have for example a hedge fund 00:12:13.399 --> 00:12:16.910 align:start position:0% where you have for example a hedge fund and<00:12:13.560> a<00:12:13.720> bank<00:12:14.600> entering<00:12:15.000> into<00:12:15.480> a<00:12:16.000> a<00:12:16.160> financial 00:12:16.910 --> 00:12:16.920 align:start position:0% and a bank entering into a a financial 00:12:16.920 --> 00:12:18.790 align:start position:0% and a bank entering into a a financial trade<00:12:17.760> that<00:12:17.920> has<00:12:18.079> to<00:12:18.199> have<00:12:18.440> greater 00:12:18.790 --> 00:12:18.800 align:start position:0% trade that has to have greater 00:12:18.800 --> 00:12:21.269 align:start position:0% trade that has to have greater performance<00:12:19.560> there<00:12:19.680> might<00:12:19.880> be<00:12:20.000> an<00:12:20.279> algorithm 00:12:21.269 --> 00:12:21.279 align:start position:0% performance there might be an algorithm 00:12:21.279 --> 00:12:23.550 align:start position:0% performance there might be an algorithm uh<00:12:21.399> for<00:12:21.600> pricing<00:12:22.000> that<00:12:22.120> needs<00:12:22.320> to<00:12:22.440> be<00:12:22.800> kept 00:12:23.550 --> 00:12:23.560 align:start position:0% uh for pricing that needs to be kept 00:12:23.560 --> 00:12:26.750 align:start position:0% uh for pricing that needs to be kept secret<00:12:24.560> um<00:12:24.720> and<00:12:24.839> that<00:12:24.959> can<00:12:25.079> be<00:12:25.240> run<00:12:25.639> in<00:12:26.240> the<00:12:26.639> uh 00:12:26.750 --> 00:12:26.760 align:start position:0% secret um and that can be run in the uh 00:12:26.760 --> 00:12:29.790 align:start position:0% secret um and that can be run in the uh criet<00:12:27.240> itself<00:12:27.760> off<00:12:27.959> the<00:12:28.120> chain<00:12:29.000> but<00:12:29.240> but<00:12:29.519> still 00:12:29.790 --> 00:12:29.800 align:start position:0% criet itself off the chain but but still 00:12:29.800 --> 00:12:31.030 align:start position:0% criet itself off the chain but but still preserving<00:12:30.240> the<00:12:30.399> goodness<00:12:30.760> of<00:12:30.920> the 00:12:31.030 --> 00:12:31.040 align:start position:0% preserving the goodness of the 00:12:31.040 --> 00:12:32.870 align:start position:0% preserving the goodness of the distributed 00:12:32.870 --> 00:12:32.880 align:start position:0% distributed 00:12:32.880 --> 00:12:35.269 align:start position:0% distributed ledger<00:12:33.880> so<00:12:34.360> when<00:12:34.440> you<00:12:34.560> bring<00:12:34.800> these<00:12:34.959> into 00:12:35.269 --> 00:12:35.279 align:start position:0% ledger so when you bring these into 00:12:35.279 --> 00:12:37.670 align:start position:0% ledger so when you bring these into practice<00:12:36.199> these<00:12:36.399> two<00:12:36.560> use<00:12:36.880> cases<00:12:37.199> fall<00:12:37.440> into 00:12:37.670 --> 00:12:37.680 align:start position:0% practice these two use cases fall into 00:12:37.680 --> 00:12:41.550 align:start position:0% practice these two use cases fall into these<00:12:37.920> types<00:12:38.160> of<00:12:38.360> criet<00:12:39.360> so<00:12:39.600> utility<00:12:40.079> criet<00:12:41.079> um 00:12:41.550 --> 00:12:41.560 align:start position:0% these types of criet so utility criet um 00:12:41.560 --> 00:12:44.110 align:start position:0% these types of criet so utility criet um here's<00:12:41.720> an<00:12:42.240> example<00:12:43.240> again<00:12:43.560> I<00:12:43.680> doubt<00:12:43.880> you<00:12:44.000> can 00:12:44.110 --> 00:12:44.120 align:start position:0% here's an example again I doubt you can 00:12:44.120 --> 00:12:45.670 align:start position:0% here's an example again I doubt you can read<00:12:44.360> this<00:12:44.519> code<00:12:44.800> but<00:12:44.920> this<00:12:45.040> is<00:12:45.199> a<00:12:45.360> smart 00:12:45.670 --> 00:12:45.680 align:start position:0% read this code but this is a smart 00:12:45.680 --> 00:12:48.230 align:start position:0% read this code but this is a smart contract<00:12:46.199> here<00:12:46.920> I'm<00:12:47.040> marked<00:12:47.360> in<00:12:47.519> yellow<00:12:47.959> where 00:12:48.230 --> 00:12:48.240 align:start position:0% contract here I'm marked in yellow where 00:12:48.240 --> 00:12:50.389 align:start position:0% contract here I'm marked in yellow where the<00:12:48.440> event<00:12:49.000> subscription<00:12:49.720> happens<00:12:50.120> this<00:12:50.240> is 00:12:50.389 --> 00:12:50.399 align:start position:0% the event subscription happens this is 00:12:50.399 --> 00:12:53.710 align:start position:0% the event subscription happens this is the<00:12:50.560> exact<00:12:50.880> same<00:12:51.480> uh<00:12:51.600> description<00:12:52.040> I<00:12:52.160> used<00:12:52.560> for 00:12:53.710 --> 00:12:53.720 align:start position:0% the exact same uh description I used for 00:12:53.720 --> 00:12:56.110 align:start position:0% the exact same uh description I used for event<00:12:54.720> where<00:12:55.079> you're<00:12:55.320> subscribing<00:12:55.800> to<00:12:55.959> an 00:12:56.110 --> 00:12:56.120 align:start position:0% event where you're subscribing to an 00:12:56.120 --> 00:12:57.750 align:start position:0% event where you're subscribing to an event<00:12:56.360> for<00:12:56.519> a<00:12:56.680> specific<00:12:57.160> time<00:12:57.519> if<00:12:57.639> the 00:12:57.750 --> 00:12:57.760 align:start position:0% event for a specific time if the 00:12:57.760 --> 00:13:01.110 align:start position:0% event for a specific time if the Market's<00:12:58.199> open<00:12:58.880> for<00:12:59.279> certain<00:12:59.639> rate<00:13:00.519> um<00:13:00.920> to 00:13:01.110 --> 00:13:01.120 align:start position:0% Market's open for certain rate um to 00:13:01.120 --> 00:13:02.430 align:start position:0% Market's open for certain rate um to give<00:13:01.240> you<00:13:01.399> a<00:13:01.560> rate<00:13:01.720> in<00:13:01.839> a<00:13:02.000> price<00:13:02.199> of<00:13:02.279> a 00:13:02.430 --> 00:13:02.440 align:start position:0% give you a rate in a price of a 00:13:02.440 --> 00:13:05.550 align:start position:0% give you a rate in a price of a commodity<00:13:02.920> in<00:13:03.040> this<00:13:03.320> case<00:13:04.320> and<00:13:05.040> uh<00:13:05.240> what 00:13:05.550 --> 00:13:05.560 align:start position:0% commodity in this case and uh what 00:13:05.560 --> 00:13:09.069 align:start position:0% commodity in this case and uh what happens<00:13:06.000> is<00:13:06.519> you<00:13:06.839> simply<00:13:07.839> uh<00:13:08.000> requests<00:13:08.480> that 00:13:09.069 --> 00:13:09.079 align:start position:0% happens is you simply uh requests that 00:13:09.079 --> 00:13:12.629 align:start position:0% happens is you simply uh requests that the<00:13:09.480> uh<00:13:09.600> crypto<00:13:10.000> delegate<00:13:10.360> wires<00:13:10.839> up<00:13:11.839> um<00:13:12.399> the 00:13:12.629 --> 00:13:12.639 align:start position:0% the uh crypto delegate wires up um the 00:13:12.639 --> 00:13:14.350 align:start position:0% the uh crypto delegate wires up um the secure<00:13:13.079> connections<00:13:13.639> between<00:13:13.880> the<00:13:14.000> smart 00:13:14.350 --> 00:13:14.360 align:start position:0% secure connections between the smart 00:13:14.360 --> 00:13:16.629 align:start position:0% secure connections between the smart contract<00:13:14.959> and<00:13:15.160> the<00:13:15.279> criet<00:13:15.720> itself<00:13:16.320> so<00:13:16.480> it's 00:13:16.629 --> 00:13:16.639 align:start position:0% contract and the criet itself so it's 00:13:16.639 --> 00:13:18.949 align:start position:0% contract and the criet itself so it's just<00:13:16.760> like<00:13:16.920> a<00:13:17.079> secure<00:13:17.519> reference<00:13:18.480> so<00:13:18.800> a 00:13:18.949 --> 00:13:18.959 align:start position:0% just like a secure reference so a 00:13:18.959 --> 00:13:21.350 align:start position:0% just like a secure reference so a developer<00:13:19.360> at<00:13:19.519> design<00:13:19.920> time<00:13:20.440> will<00:13:20.959> reference 00:13:21.350 --> 00:13:21.360 align:start position:0% developer at design time will reference 00:13:21.360 --> 00:13:23.350 align:start position:0% developer at design time will reference the<00:13:21.519> criet<00:13:21.920> they<00:13:22.040> want<00:13:22.199> to<00:13:22.360> trust<00:13:23.240> the 00:13:23.350 --> 00:13:23.360 align:start position:0% the criet they want to trust the 00:13:23.360 --> 00:13:25.670 align:start position:0% the criet they want to trust the signatures<00:13:23.839> are<00:13:24.040> recorded<00:13:24.800> and<00:13:24.920> IT<00:13:25.040> wires<00:13:25.440> up 00:13:25.670 --> 00:13:25.680 align:start position:0% signatures are recorded and IT wires up 00:13:25.680 --> 00:13:27.269 align:start position:0% signatures are recorded and IT wires up that<00:13:25.880> and<00:13:25.959> the<00:13:26.079> crypto<00:13:26.440> delegate<00:13:26.800> can<00:13:26.959> also 00:13:27.269 --> 00:13:27.279 align:start position:0% that and the crypto delegate can also 00:13:27.279 --> 00:13:30.110 align:start position:0% that and the crypto delegate can also check<00:13:28.040> and<00:13:28.279> enforce<00:13:28.880> that<00:13:29.199> the<00:13:29.279> messages<00:13:29.800> only 00:13:30.110 --> 00:13:30.120 align:start position:0% check and enforce that the messages only 00:13:30.120 --> 00:13:33.150 align:start position:0% check and enforce that the messages only come<00:13:30.440> from<00:13:30.720> that<00:13:31.240> criet<00:13:32.240> um<00:13:32.480> so<00:13:32.639> it<00:13:32.720> wakes<00:13:33.000> up 00:13:33.150 --> 00:13:33.160 align:start position:0% come from that criet um so it wakes up 00:13:33.160 --> 00:13:34.470 align:start position:0% come from that criet um so it wakes up the<00:13:33.240> smart<00:13:33.560> contract<00:13:33.920> to<00:13:34.079> go<00:13:34.160> ahead<00:13:34.320> and 00:13:34.470 --> 00:13:34.480 align:start position:0% the smart contract to go ahead and 00:13:34.480 --> 00:13:37.110 align:start position:0% the smart contract to go ahead and execute<00:13:34.880> the<00:13:35.040> code<00:13:35.839> you<00:13:35.959> see<00:13:36.160> the<00:13:36.279> code<00:13:36.560> body 00:13:37.110 --> 00:13:37.120 align:start position:0% execute the code you see the code body 00:13:37.120 --> 00:13:39.590 align:start position:0% execute the code you see the code body itself<00:13:37.600> down<00:13:37.800> here<00:13:38.120> the<00:13:38.560> the<00:13:38.680> solidity<00:13:39.199> code 00:13:39.590 --> 00:13:39.600 align:start position:0% itself down here the the solidity code 00:13:39.600 --> 00:13:41.110 align:start position:0% itself down here the the solidity code has<00:13:39.760> all<00:13:39.920> the<00:13:40.120> calculations<00:13:40.720> that<00:13:40.839> we're 00:13:41.110 --> 00:13:41.120 align:start position:0% has all the calculations that we're 00:13:41.120 --> 00:13:42.829 align:start position:0% has all the calculations that we're performing<00:13:42.000> so<00:13:42.160> that's<00:13:42.320> going<00:13:42.399> to<00:13:42.480> run<00:13:42.680> on 00:13:42.829 --> 00:13:42.839 align:start position:0% performing so that's going to run on 00:13:42.839 --> 00:13:46.629 align:start position:0% performing so that's going to run on every<00:13:43.040> single<00:13:43.320> node<00:13:44.279> uh<00:13:44.399> once<00:13:44.680> that<00:13:44.880> is<00:13:45.320> been 00:13:46.629 --> 00:13:46.639 align:start position:0% every single node uh once that is been 00:13:46.639 --> 00:13:49.710 align:start position:0% every single node uh once that is been seated<00:13:47.639> the<00:13:48.000> contract<00:13:48.399> triplet<00:13:48.920> is<00:13:49.519> um 00:13:49.710 --> 00:13:49.720 align:start position:0% seated the contract triplet is um 00:13:49.720 --> 00:13:51.150 align:start position:0% seated the contract triplet is um actually<00:13:50.000> deployed<00:13:50.519> in<00:13:50.680> this<00:13:50.839> case<00:13:51.000> we're 00:13:51.150 --> 00:13:51.160 align:start position:0% actually deployed in this case we're 00:13:51.160 --> 00:13:54.230 align:start position:0% actually deployed in this case we're using<00:13:51.600> the<00:13:52.480> uh<00:13:52.639> deployment<00:13:53.440> uh<00:13:53.560> mechanism<00:13:54.040> to 00:13:54.230 --> 00:13:54.240 align:start position:0% using the uh deployment uh mechanism to 00:13:54.240 --> 00:13:56.269 align:start position:0% using the uh deployment uh mechanism to actually<00:13:54.600> create<00:13:55.120> the<00:13:55.320> surrogate<00:13:55.880> for<00:13:56.120> the 00:13:56.269 --> 00:13:56.279 align:start position:0% actually create the surrogate for the 00:13:56.279 --> 00:13:59.150 align:start position:0% actually create the surrogate for the smart<00:13:56.680> contract<00:13:57.680> in<00:13:57.839> the<00:13:58.000> cloud<00:13:58.560> so<00:13:58.720> it<00:13:58.839> goes 00:13:59.150 --> 00:13:59.160 align:start position:0% smart contract in the cloud so it goes 00:13:59.160 --> 00:14:00.710 align:start position:0% smart contract in the cloud so it goes through<00:13:59.279> the<00:13:59.320> crypto<00:13:59.680> delegate<00:14:00.120> and<00:14:00.240> it<00:14:00.519> goes 00:14:00.710 --> 00:14:00.720 align:start position:0% through the crypto delegate and it goes 00:14:00.720 --> 00:14:03.189 align:start position:0% through the crypto delegate and it goes out<00:14:00.920> and<00:14:01.040> creates<00:14:01.399> the<00:14:01.519> contract<00:14:02.079> criet<00:14:03.079> uh 00:14:03.189 --> 00:14:03.199 align:start position:0% out and creates the contract criet uh 00:14:03.199 --> 00:14:05.069 align:start position:0% out and creates the contract criet uh the<00:14:03.320> contract<00:14:03.639> criet<00:14:04.079> doeses<00:14:04.279> all<00:14:04.519> the<00:14:04.639> market 00:14:05.069 --> 00:14:05.079 align:start position:0% the contract criet doeses all the market 00:14:05.079 --> 00:14:07.949 align:start position:0% the contract criet doeses all the market watching<00:14:05.600> all<00:14:05.800> of<00:14:06.000> the<00:14:06.839> uh<00:14:07.079> logic<00:14:07.720> and 00:14:07.949 --> 00:14:07.959 align:start position:0% watching all of the uh logic and 00:14:07.959 --> 00:14:09.749 align:start position:0% watching all of the uh logic and execution<00:14:08.440> to<00:14:08.639> it's<00:14:08.839> ready<00:14:09.040> to<00:14:09.199> store<00:14:09.480> its 00:14:09.749 --> 00:14:09.759 align:start position:0% execution to it's ready to store its 00:14:09.759 --> 00:14:12.430 align:start position:0% execution to it's ready to store its state<00:14:10.680> in<00:14:10.880> which<00:14:11.040> it<00:14:11.440> uh<00:14:11.519> Records<00:14:11.959> the<00:14:12.120> state 00:14:12.430 --> 00:14:12.440 align:start position:0% state in which it uh Records the state 00:14:12.440 --> 00:14:15.749 align:start position:0% state in which it uh Records the state down<00:14:12.680> to<00:14:13.639> um<00:14:13.839> the<00:14:13.959> smart<00:14:14.320> contract 00:14:15.749 --> 00:14:15.759 align:start position:0% down to um the smart contract 00:14:15.759 --> 00:14:18.389 align:start position:0% down to um the smart contract itself<00:14:16.759> now<00:14:17.040> here's<00:14:17.720> uh<00:14:17.839> where<00:14:18.000> the<00:14:18.120> real 00:14:18.389 --> 00:14:18.399 align:start position:0% itself now here's uh where the real 00:14:18.399 --> 00:14:20.230 align:start position:0% itself now here's uh where the real value<00:14:18.720> is<00:14:19.000> every<00:14:19.320> like<00:14:19.560> hey<00:14:19.680> I<00:14:19.759> can<00:14:19.880> write<00:14:20.120> this 00:14:20.230 --> 00:14:20.240 align:start position:0% value is every like hey I can write this 00:14:20.240 --> 00:14:22.430 align:start position:0% value is every like hey I can write this on<00:14:20.399> my<00:14:20.519> own<00:14:20.759> I<00:14:20.839> don't<00:14:21.079> I<00:14:21.160> don't<00:14:21.320> really<00:14:21.560> need 00:14:22.430 --> 00:14:22.440 align:start position:0% on my own I don't I don't really need 00:14:22.440 --> 00:14:26.269 align:start position:0% on my own I don't I don't really need why<00:14:22.519> would<00:14:22.680> I<00:14:22.800> use<00:14:23.720> um<00:14:23.880> Azure<00:14:24.360> to<00:14:24.519> do<00:14:24.880> this<00:14:25.880> well 00:14:26.269 --> 00:14:26.279 align:start position:0% why would I use um Azure to do this well 00:14:26.279 --> 00:14:29.910 align:start position:0% why would I use um Azure to do this well the<00:14:26.440> advances<00:14:27.120> in<00:14:28.000> um<00:14:28.600> silicon<00:14:29.519> and<00:14:29.800> the 00:14:29.910 --> 00:14:29.920 align:start position:0% the advances in um silicon and the 00:14:29.920 --> 00:14:33.829 align:start position:0% the advances in um silicon and the Hardware<00:14:30.480> security<00:14:31.480> uh<00:14:31.600> namely<00:14:32.079> Intel's<00:14:32.839> sgx 00:14:33.829 --> 00:14:33.839 align:start position:0% Hardware security uh namely Intel's sgx 00:14:33.839 --> 00:14:35.550 align:start position:0% Hardware security uh namely Intel's sgx um<00:14:34.279> provides<00:14:34.600> the<00:14:34.759> capability<00:14:35.199> for<00:14:35.320> you<00:14:35.399> to 00:14:35.550 --> 00:14:35.560 align:start position:0% um provides the capability for you to 00:14:35.560 --> 00:14:38.509 align:start position:0% um provides the capability for you to create<00:14:35.880> secure<00:14:36.560> enclaves<00:14:37.560> so<00:14:37.800> an<00:14:37.959> enclave<00:14:38.440> if 00:14:38.509 --> 00:14:38.519 align:start position:0% create secure enclaves so an enclave if 00:14:38.519 --> 00:14:40.110 align:start position:0% create secure enclaves so an enclave if you're<00:14:38.639> not<00:14:38.800> familiar<00:14:39.120> with<00:14:39.199> what<00:14:39.320> sgx<00:14:39.839> does 00:14:40.110 --> 00:14:40.120 align:start position:0% you're not familiar with what sgx does 00:14:40.120 --> 00:14:44.710 align:start position:0% you're not familiar with what sgx does is<00:14:40.279> it's<00:14:41.199> uh<00:14:41.600> area<00:14:42.040> of<00:14:42.720> um<00:14:43.000> on<00:14:43.199> the<00:14:43.360> chip<00:14:43.720> itself 00:14:44.710 --> 00:14:44.720 align:start position:0% is it's uh area of um on the chip itself 00:14:44.720 --> 00:14:46.870 align:start position:0% is it's uh area of um on the chip itself that's<00:14:44.920> an<00:14:45.519> uh<00:14:45.680> complete<00:14:46.120> isolation<00:14:46.759> where 00:14:46.870 --> 00:14:46.880 align:start position:0% that's an uh complete isolation where 00:14:46.880 --> 00:14:50.509 align:start position:0% that's an uh complete isolation where you<00:14:46.959> can<00:14:47.079> run<00:14:47.399> code<00:14:47.920> and<00:14:48.120> have<00:14:48.399> data<00:14:49.399> run<00:14:50.360> uh 00:14:50.509 --> 00:14:50.519 align:start position:0% you can run code and have data run uh 00:14:50.519 --> 00:14:52.230 align:start position:0% you can run code and have data run uh where<00:14:50.680> it's<00:14:50.880> tamper<00:14:51.360> resistant<00:14:51.759> and<00:14:51.880> tamper 00:14:52.230 --> 00:14:52.240 align:start position:0% where it's tamper resistant and tamper 00:14:52.240 --> 00:14:54.710 align:start position:0% where it's tamper resistant and tamper proof<00:14:52.480> so<00:14:52.600> you<00:14:52.759> can't<00:14:53.399> uh<00:14:53.560> poke<00:14:53.839> into<00:14:54.160> it<00:14:54.360> you 00:14:54.710 --> 00:14:54.720 align:start position:0% proof so you can't uh poke into it you 00:14:54.720 --> 00:14:57.590 align:start position:0% proof so you can't uh poke into it you can't<00:14:55.720> um<00:14:56.160> Step<00:14:56.399> On<00:14:56.480> A<00:14:56.600> Memory<00:14:56.880> address<00:14:57.240> space 00:14:57.590 --> 00:14:57.600 align:start position:0% can't um Step On A Memory address space 00:14:57.600 --> 00:15:01.269 align:start position:0% can't um Step On A Memory address space to<00:14:57.880> to<00:14:58.079> go<00:14:58.240> out<00:14:58.440> and<00:14:58.680> and<00:14:59.360> um<00:14:59.720> corrupt<00:15:00.480> or 00:15:01.269 --> 00:15:01.279 align:start position:0% to to go out and and um corrupt or 00:15:01.279 --> 00:15:04.710 align:start position:0% to to go out and and um corrupt or potentially<00:15:02.279> um<00:15:03.079> um<00:15:04.079> interrupt<00:15:04.560> the 00:15:04.710 --> 00:15:04.720 align:start position:0% potentially um um interrupt the 00:15:04.720 --> 00:15:07.110 align:start position:0% potentially um um interrupt the execution<00:15:05.240> of<00:15:05.560> something<00:15:06.560> um<00:15:06.680> so<00:15:06.920> this 00:15:07.110 --> 00:15:07.120 align:start position:0% execution of something um so this 00:15:07.120 --> 00:15:09.470 align:start position:0% execution of something um so this Enclave<00:15:07.759> provides<00:15:08.120> a<00:15:08.360> secure<00:15:08.759> container<00:15:09.399> and 00:15:09.470 --> 00:15:09.480 align:start position:0% Enclave provides a secure container and 00:15:09.480 --> 00:15:12.150 align:start position:0% Enclave provides a secure container and then<00:15:09.600> it<00:15:09.720> provides<00:15:10.120> full<00:15:10.759> attestation<00:15:11.759> level 00:15:12.150 --> 00:15:12.160 align:start position:0% then it provides full attestation level 00:15:12.160 --> 00:15:15.550 align:start position:0% then it provides full attestation level at<00:15:12.320> the<00:15:12.440> CPU<00:15:13.079> level<00:15:13.839> that<00:15:14.040> this<00:15:14.160> was<00:15:14.560> actually 00:15:15.550 --> 00:15:15.560 align:start position:0% at the CPU level that this was actually 00:15:15.560 --> 00:15:16.310 align:start position:0% at the CPU level that this was actually uh 00:15:16.310 --> 00:15:16.320 align:start position:0% uh 00:15:16.320 --> 00:15:19.389 align:start position:0% uh built<00:15:17.320> um<00:15:17.600> in<00:15:17.759> the<00:15:17.880> enclave<00:15:18.360> and<00:15:18.519> run<00:15:18.720> in<00:15:18.839> an 00:15:19.389 --> 00:15:19.399 align:start position:0% built um in the enclave and run in an 00:15:19.399 --> 00:15:21.430 align:start position:0% built um in the enclave and run in an enclave<00:15:20.399> now<00:15:20.800> when<00:15:20.920> you're<00:15:21.040> starting<00:15:21.320> to 00:15:21.430 --> 00:15:21.440 align:start position:0% enclave now when you're starting to 00:15:21.440 --> 00:15:23.310 align:start position:0% enclave now when you're starting to build<00:15:22.040> uh<00:15:22.199> Solutions<00:15:22.720> like<00:15:22.880> this<00:15:23.120> and<00:15:23.240> you 00:15:23.310 --> 00:15:23.320 align:start position:0% build uh Solutions like this and you 00:15:23.320 --> 00:15:24.790 align:start position:0% build uh Solutions like this and you want<00:15:23.440> to<00:15:23.560> get<00:15:23.800> scale<00:15:24.240> and<00:15:24.320> you<00:15:24.399> want<00:15:24.480> to<00:15:24.600> have 00:15:24.790 --> 00:15:24.800 align:start position:0% want to get scale and you want to have 00:15:24.800 --> 00:15:26.870 align:start position:0% want to get scale and you want to have security<00:15:25.240> and<00:15:25.639> attestation<00:15:26.639> and<00:15:26.759> you're 00:15:26.870 --> 00:15:26.880 align:start position:0% security and attestation and you're 00:15:26.880 --> 00:15:28.629 align:start position:0% security and attestation and you're trying<00:15:27.079> to<00:15:27.240> land<00:15:27.560> that<00:15:27.759> big<00:15:28.079> contract<00:15:28.519> with 00:15:28.629 --> 00:15:28.639 align:start position:0% trying to land that big contract with 00:15:28.639 --> 00:15:30.389 align:start position:0% trying to land that big contract with the<00:15:28.759> bank<00:15:29.199> or<00:15:29.399> some<00:15:29.680> somebody<00:15:29.959> that<00:15:30.040> wants<00:15:30.240> to 00:15:30.389 --> 00:15:30.399 align:start position:0% the bank or some somebody that wants to 00:15:30.399 --> 00:15:32.110 align:start position:0% the bank or some somebody that wants to make<00:15:30.560> sure<00:15:30.839> that<00:15:30.959> your<00:15:31.160> security<00:15:31.519> is<00:15:31.680> Rock 00:15:32.110 --> 00:15:32.120 align:start position:0% make sure that your security is Rock 00:15:32.120 --> 00:15:35.470 align:start position:0% make sure that your security is Rock Solid<00:15:33.120> if<00:15:33.240> you<00:15:33.360> can<00:15:33.880> make<00:15:34.160> guarantees<00:15:34.959> that 00:15:35.470 --> 00:15:35.480 align:start position:0% Solid if you can make guarantees that 00:15:35.480 --> 00:15:37.710 align:start position:0% Solid if you can make guarantees that your<00:15:35.759> code<00:15:36.160> is<00:15:36.319> running<00:15:36.759> in<00:15:36.959> a<00:15:37.160> secure 00:15:37.710 --> 00:15:37.720 align:start position:0% your code is running in a secure 00:15:37.720 --> 00:15:41.910 align:start position:0% your code is running in a secure isolated<00:15:38.480> container<00:15:39.480> in<00:15:39.639> the<00:15:39.839> cloud<00:15:40.800> full 00:15:41.910 --> 00:15:41.920 align:start position:0% isolated container in the cloud full 00:15:41.920 --> 00:15:44.350 align:start position:0% isolated container in the cloud full attestation<00:15:42.920> um<00:15:43.160> on<00:15:43.440> in<00:15:43.680> Silicon<00:15:44.199> and 00:15:44.350 --> 00:15:44.360 align:start position:0% attestation um on in Silicon and 00:15:44.360 --> 00:15:47.069 align:start position:0% attestation um on in Silicon and recorded<00:15:44.880> into<00:15:45.120> the<00:15:45.560> blockchain<00:15:46.560> um<00:15:46.680> it<00:15:46.839> gives 00:15:47.069 --> 00:15:47.079 align:start position:0% recorded into the blockchain um it gives 00:15:47.079 --> 00:15:49.389 align:start position:0% recorded into the blockchain um it gives that<00:15:47.319> level<00:15:47.560> of<00:15:47.800> security<00:15:48.800> um<00:15:48.959> that<00:15:49.160> really 00:15:49.389 --> 00:15:49.399 align:start position:0% that level of security um that really 00:15:49.399 --> 00:15:51.949 align:start position:0% that level of security um that really you<00:15:49.560> can't<00:15:49.839> get<00:15:50.040> anywhere<00:15:50.399> else<00:15:50.600> at<00:15:50.959> scale 00:15:51.949 --> 00:15:51.959 align:start position:0% you can't get anywhere else at scale 00:15:51.959 --> 00:15:52.949 align:start position:0% you can't get anywhere else at scale because<00:15:52.160> you're<00:15:52.240> going<00:15:52.360> to<00:15:52.440> be<00:15:52.560> able<00:15:52.720> to 00:15:52.949 --> 00:15:52.959 align:start position:0% because you're going to be able to 00:15:52.959 --> 00:15:55.990 align:start position:0% because you're going to be able to deploy<00:15:53.480> this<00:15:54.199> and<00:15:54.399> in<00:15:54.639> Azure<00:15:55.160> and<00:15:55.319> Azure<00:15:55.639> has 00:15:55.990 --> 00:15:56.000 align:start position:0% deploy this and in Azure and Azure has 00:15:56.000 --> 00:15:58.309 align:start position:0% deploy this and in Azure and Azure has been<00:15:56.199> deployed<00:15:56.600> in<00:15:56.720> over<00:15:56.959> 30<00:15:57.839> some<00:15:58.079> odd 00:15:58.309 --> 00:15:58.319 align:start position:0% been deployed in over 30 some odd 00:15:58.319 --> 00:16:00.230 align:start position:0% been deployed in over 30 some odd regions<00:15:58.639> around<00:15:59.120> the<00:15:59.199> world<00:15:59.440> there's<00:15:59.920> several 00:16:00.230 --> 00:16:00.240 align:start position:0% regions around the world there's several 00:16:00.240 --> 00:16:03.309 align:start position:0% regions around the world there's several here<00:16:00.360> in<00:16:00.720> China<00:16:01.720> uh<00:16:01.800> so<00:16:01.920> you'll<00:16:02.079> be<00:16:02.199> able<00:16:02.440> to<00:16:03.160> um 00:16:03.309 --> 00:16:03.319 align:start position:0% here in China uh so you'll be able to um 00:16:03.319 --> 00:16:05.749 align:start position:0% here in China uh so you'll be able to um deploy<00:16:03.839> these<00:16:04.480> across<00:16:04.880> the<00:16:05.079> application 00:16:05.749 --> 00:16:05.759 align:start position:0% deploy these across the application 00:16:05.759 --> 00:16:08.670 align:start position:0% deploy these across the application fabric<00:16:06.639> with<00:16:06.800> an<00:16:07.160> Azure<00:16:08.160> now<00:16:08.279> we're<00:16:08.440> going<00:16:08.560> to 00:16:08.670 --> 00:16:08.680 align:start position:0% fabric with an Azure now we're going to 00:16:08.680 --> 00:16:11.269 align:start position:0% fabric with an Azure now we're going to be<00:16:09.160> uh<00:16:09.319> delivering<00:16:10.279> these<00:16:10.440> enclaves<00:16:11.000> in<00:16:11.199> what 00:16:11.269 --> 00:16:11.279 align:start position:0% be uh delivering these enclaves in what 00:16:11.279 --> 00:16:13.910 align:start position:0% be uh delivering these enclaves in what we<00:16:11.440> call<00:16:11.600> a<00:16:11.720> criet<00:16:12.399> container<00:16:13.399> uh<00:16:13.519> cppc 00:16:13.910 --> 00:16:13.920 align:start position:0% we call a criet container uh cppc 00:16:13.920 --> 00:16:15.829 align:start position:0% we call a criet container uh cppc container<00:16:14.279> is<00:16:14.480> essentially<00:16:15.079> an<00:16:15.199> enclave 00:16:15.829 --> 00:16:15.839 align:start position:0% container is essentially an enclave 00:16:15.839 --> 00:16:18.710 align:start position:0% container is essentially an enclave based<00:16:16.839> uh<00:16:17.000> container<00:16:17.519> wrapper<00:16:18.399> where<00:16:18.519> you 00:16:18.710 --> 00:16:18.720 align:start position:0% based uh container wrapper where you 00:16:18.720 --> 00:16:21.150 align:start position:0% based uh container wrapper where you inject<00:16:19.160> criet<00:16:19.600> in<00:16:19.800> there<00:16:20.519> the<00:16:20.639> criet<00:16:21.040> are 00:16:21.150 --> 00:16:21.160 align:start position:0% inject criet in there the criet are 00:16:21.160 --> 00:16:22.949 align:start position:0% inject criet in there the criet are written<00:16:21.519> in<00:16:21.720> the<00:16:21.880> language<00:16:22.279> that<00:16:22.399> you<00:16:22.519> want<00:16:22.720> to 00:16:22.949 --> 00:16:22.959 align:start position:0% written in the language that you want to 00:16:22.959 --> 00:16:25.829 align:start position:0% written in the language that you want to Target<00:16:23.600> so<00:16:23.800> in<00:16:23.920> this<00:16:24.160> case<00:16:25.160> um<00:16:25.399> the<00:16:25.480> first<00:16:25.680> one 00:16:25.829 --> 00:16:25.839 align:start position:0% Target so in this case um the first one 00:16:25.839 --> 00:16:28.870 align:start position:0% Target so in this case um the first one will<00:16:25.959> be<00:16:26.160> the<00:16:26.920> net<00:16:27.120> core<00:16:27.360> CLR<00:16:27.920> that's<00:16:28.160> the<00:16:28.600> open 00:16:28.870 --> 00:16:28.880 align:start position:0% will be the net core CLR that's the open 00:16:28.880 --> 00:16:32.870 align:start position:0% will be the net core CLR that's the open open<00:16:29.160> source<00:16:29.920> Uhn<00:16:30.279> net<00:16:30.680> version<00:16:31.680> uh<00:16:31.880> uh<00:16:32.399> cripp 00:16:32.870 --> 00:16:32.880 align:start position:0% open source Uhn net version uh uh cripp 00:16:32.880 --> 00:16:35.670 align:start position:0% open source Uhn net version uh uh cripp container<00:16:33.680> then<00:16:33.800> you<00:16:33.920> can<00:16:34.440> write<00:16:34.680> it<00:16:34.800> in<00:16:34.959> C<00:16:35.519> you 00:16:35.670 --> 00:16:35.680 align:start position:0% container then you can write it in C you 00:16:35.680 --> 00:16:37.749 align:start position:0% container then you can write it in C you heard<00:16:36.120> some<00:16:36.279> of<00:16:36.399> you<00:16:36.519> might<00:16:36.639> have<00:16:36.720> read<00:16:36.920> about 00:16:37.749 --> 00:16:37.759 align:start position:0% heard some of you might have read about 00:16:37.759 --> 00:16:40.470 align:start position:0% heard some of you might have read about fstar<00:16:38.759> um<00:16:39.519> so<00:16:39.600> you<00:16:39.720> have<00:16:39.880> lots<00:16:40.040> of<00:16:40.120> language 00:16:40.470 --> 00:16:40.480 align:start position:0% fstar um so you have lots of language 00:16:40.480 --> 00:16:43.309 align:start position:0% fstar um so you have lots of language choices<00:16:40.920> there<00:16:41.160> also<00:16:41.360> in<00:16:41.519> the<00:16:41.800> jvm<00:16:42.800> which<00:16:42.920> is 00:16:43.309 --> 00:16:43.319 align:start position:0% choices there also in the jvm which is 00:16:43.319 --> 00:16:45.749 align:start position:0% choices there also in the jvm which is also<00:16:43.600> very<00:16:43.880> popular<00:16:44.199> in<00:16:44.319> the<00:16:44.639> Enterprise<00:16:45.639> and 00:16:45.749 --> 00:16:45.759 align:start position:0% also very popular in the Enterprise and 00:16:45.759 --> 00:16:49.230 align:start position:0% also very popular in the Enterprise and then<00:16:46.519> um<00:16:46.720> you<00:16:46.839> know<00:16:47.000> the<00:16:47.120> evm<00:16:47.920> itself<00:16:48.920> moving 00:16:49.230 --> 00:16:49.240 align:start position:0% then um you know the evm itself moving 00:16:49.240 --> 00:16:55.030 align:start position:0% then um you know the evm itself moving into<00:16:50.160> an<00:16:50.759> enclave<00:16:51.839> so<00:16:52.839> uh<00:16:53.480> this<00:16:53.720> type<00:16:53.920> of<00:16:54.160> scale 00:16:55.030 --> 00:16:55.040 align:start position:0% into an enclave so uh this type of scale 00:16:55.040 --> 00:16:57.230 align:start position:0% into an enclave so uh this type of scale uh<00:16:55.160> rolling<00:16:55.480> out<00:16:55.720> this<00:16:55.880> type<00:16:56.040> of<00:16:56.240> innovation 00:16:57.230 --> 00:16:57.240 align:start position:0% uh rolling out this type of innovation 00:16:57.240 --> 00:16:58.910 align:start position:0% uh rolling out this type of innovation in<00:16:57.440> these<00:16:57.639> massive<00:16:58.079> data<00:16:58.319> centers<00:16:58.600> where<00:16:58.720> you 00:16:58.910 --> 00:16:58.920 align:start position:0% in these massive data centers where you 00:16:58.920 --> 00:17:01.749 align:start position:0% in these massive data centers where you you<00:16:59.040> have<00:16:59.279> on<00:16:59.560> demand<00:17:00.519> secure<00:17:01.000> execution 00:17:01.749 --> 00:17:01.759 align:start position:0% you have on demand secure execution 00:17:01.759 --> 00:17:05.750 align:start position:0% you have on demand secure execution provides<00:17:02.160> you<00:17:02.639> with<00:17:02.880> this<00:17:03.319> five<00:17:04.039> benefits<00:17:05.039> so 00:17:05.750 --> 00:17:05.760 align:start position:0% provides you with this five benefits so 00:17:05.760 --> 00:17:10.150 align:start position:0% provides you with this five benefits so um<00:17:06.760> hyperscale<00:17:07.760> um<00:17:08.240> Cloud<00:17:09.240> secure<00:17:09.640> execution 00:17:10.150 --> 00:17:10.160 align:start position:0% um hyperscale um Cloud secure execution 00:17:10.160 --> 00:17:13.309 align:start position:0% um hyperscale um Cloud secure execution and<00:17:10.480> enclaves<00:17:11.120> on<00:17:11.360> demand<00:17:12.079> worldwide<00:17:13.079> same 00:17:13.309 --> 00:17:13.319 align:start position:0% and enclaves on demand worldwide same 00:17:13.319 --> 00:17:16.230 align:start position:0% and enclaves on demand worldwide same thing<00:17:13.439> for<00:17:13.679> data<00:17:14.559> um<00:17:14.959> and<00:17:15.120> data<00:17:15.439> providers<00:17:16.079> so 00:17:16.230 --> 00:17:16.240 align:start position:0% thing for data um and data providers so 00:17:16.240 --> 00:17:17.829 align:start position:0% thing for data um and data providers so you<00:17:16.319> can<00:17:16.480> start<00:17:16.679> to<00:17:16.839> mix<00:17:17.079> and<00:17:17.240> match<00:17:17.559> you<00:17:17.679> might 00:17:17.829 --> 00:17:17.839 align:start position:0% you can start to mix and match you might 00:17:17.839 --> 00:17:19.549 align:start position:0% you can start to mix and match you might have<00:17:17.959> a<00:17:18.120> great<00:17:18.360> data<00:17:18.679> provider<00:17:19.039> for<00:17:19.199> some<00:17:19.360> sort 00:17:19.549 --> 00:17:19.559 align:start position:0% have a great data provider for some sort 00:17:19.559 --> 00:17:23.909 align:start position:0% have a great data provider for some sort of<00:17:19.720> data<00:17:20.319> service<00:17:21.319> um<00:17:21.839> and<00:17:22.120> you<00:17:22.240> want<00:17:22.439> to<00:17:23.240> uh 00:17:23.909 --> 00:17:23.919 align:start position:0% of data service um and you want to uh 00:17:23.919 --> 00:17:25.990 align:start position:0% of data service um and you want to uh create<00:17:24.480> criet<00:17:24.959> libraries<00:17:25.439> that<00:17:25.559> you<00:17:25.640> can<00:17:25.799> put 00:17:25.990 --> 00:17:26.000 align:start position:0% create criet libraries that you can put 00:17:26.000 --> 00:17:27.350 align:start position:0% create criet libraries that you can put into<00:17:26.240> the<00:17:26.360> marketplace<00:17:26.839> and<00:17:27.000> make 00:17:27.350 --> 00:17:27.360 align:start position:0% into the marketplace and make 00:17:27.360 --> 00:17:29.549 align:start position:0% into the marketplace and make discoverable<00:17:28.360> you<00:17:28.520> have<00:17:28.919> scalability<00:17:29.400> and 00:17:29.549 --> 00:17:29.559 align:start position:0% discoverable you have scalability and 00:17:29.559 --> 00:17:31.669 align:start position:0% discoverable you have scalability and flexibility<00:17:30.240> options<00:17:30.640> now<00:17:30.840> that<00:17:30.960> you<00:17:31.080> don't 00:17:31.669 --> 00:17:31.679 align:start position:0% flexibility options now that you don't 00:17:31.679 --> 00:17:34.789 align:start position:0% flexibility options now that you don't have<00:17:32.679> um<00:17:33.640> and<00:17:33.720> you<00:17:33.840> have<00:17:34.000> them<00:17:34.120> at<00:17:34.320> scale<00:17:34.640> so 00:17:34.789 --> 00:17:34.799 align:start position:0% have um and you have them at scale so 00:17:34.799 --> 00:17:36.190 align:start position:0% have um and you have them at scale so you'll<00:17:34.960> have<00:17:35.080> the<00:17:35.200> developer<00:17:35.600> tools<00:17:35.919> you<00:17:36.080> have 00:17:36.190 --> 00:17:36.200 align:start position:0% you'll have the developer tools you have 00:17:36.200 --> 00:17:38.630 align:start position:0% you'll have the developer tools you have the<00:17:36.320> ecosystem<00:17:36.880> you<00:17:37.000> have<00:17:37.160> the<00:17:37.640> marketplace 00:17:38.630 --> 00:17:38.640 align:start position:0% the ecosystem you have the marketplace 00:17:38.640 --> 00:17:41.669 align:start position:0% the ecosystem you have the marketplace and<00:17:38.799> the<00:17:39.000> cloud<00:17:39.400> where<00:17:39.520> you<00:17:39.640> can<00:17:39.799> go<00:17:40.440> out<00:17:41.440> um 00:17:41.669 --> 00:17:41.679 align:start position:0% and the cloud where you can go out um 00:17:41.679 --> 00:17:43.750 align:start position:0% and the cloud where you can go out um and<00:17:42.039> not<00:17:42.200> only<00:17:42.480> scale<00:17:42.880> Your<00:17:43.080> solution<00:17:43.600> but 00:17:43.750 --> 00:17:43.760 align:start position:0% and not only scale Your solution but 00:17:43.760 --> 00:17:46.190 align:start position:0% and not only scale Your solution but also<00:17:44.080> scale<00:17:44.400> your<00:17:44.799> execution<00:17:45.799> off<00:17:46.039> the 00:17:46.190 --> 00:17:46.200 align:start position:0% also scale your execution off the 00:17:46.200 --> 00:17:47.789 align:start position:0% also scale your execution off the blockchain<00:17:46.720> if<00:17:46.799> you<00:17:46.919> need<00:17:47.120> to<00:17:47.320> so<00:17:47.440> you<00:17:47.559> have<00:17:47.679> a 00:17:47.789 --> 00:17:47.799 align:start position:0% blockchain if you need to so you have a 00:17:47.799 --> 00:17:50.870 align:start position:0% blockchain if you need to so you have a lot<00:17:47.960> more<00:17:48.559> choices<00:17:49.559> uh<00:17:49.720> very<00:17:50.320> uh<00:17:50.440> developer 00:17:50.870 --> 00:17:50.880 align:start position:0% lot more choices uh very uh developer 00:17:50.880 --> 00:17:52.950 align:start position:0% lot more choices uh very uh developer friendly<00:17:51.200> so<00:17:51.320> you'll<00:17:51.520> see<00:17:51.720> lots<00:17:51.919> of<00:17:52.039> tool 00:17:52.950 --> 00:17:52.960 align:start position:0% friendly so you'll see lots of tool 00:17:52.960 --> 00:17:57.789 align:start position:0% friendly so you'll see lots of tool integration<00:17:53.960> um<00:17:54.160> and<00:17:54.280> an<00:17:54.520> ecosystem<00:17:55.520> for<00:17:56.799> um 00:17:57.789 --> 00:17:57.799 align:start position:0% integration um and an ecosystem for um 00:17:57.799 --> 00:18:00.510 align:start position:0% integration um and an ecosystem for um isvs<00:17:58.440> to<00:17:58.600> start<00:17:58.840> start<00:17:59.000> Building<00:17:59.520> Solutions 00:18:00.510 --> 00:18:00.520 align:start position:0% isvs to start start Building Solutions 00:18:00.520 --> 00:18:02.830 align:start position:0% isvs to start start Building Solutions and<00:18:00.760> a<00:18:00.880> standard<00:18:01.320> way<00:18:01.559> we're<00:18:01.720> not<00:18:02.280> uh<00:18:02.480> you<00:18:02.600> know 00:18:02.830 --> 00:18:02.840 align:start position:0% and a standard way we're not uh you know 00:18:02.840 --> 00:18:04.549 align:start position:0% and a standard way we're not uh you know you<00:18:02.960> get<00:18:03.120> a<00:18:03.320> common<00:18:03.600> way<00:18:03.760> to<00:18:03.919> do<00:18:04.159> something<00:18:04.480> and 00:18:04.549 --> 00:18:04.559 align:start position:0% you get a common way to do something and 00:18:04.559 --> 00:18:06.789 align:start position:0% you get a common way to do something and it<00:18:04.720> becomes<00:18:05.039> fairly<00:18:05.760> readily<00:18:06.280> accessible 00:18:06.789 --> 00:18:06.799 align:start position:0% it becomes fairly readily accessible 00:18:06.799 --> 00:18:08.750 align:start position:0% it becomes fairly readily accessible around<00:18:07.080> the<00:18:07.200> world<00:18:07.880> and<00:18:08.320> something<00:18:08.600> that 00:18:08.750 --> 00:18:08.760 align:start position:0% around the world and something that 00:18:08.760 --> 00:18:10.549 align:start position:0% around the world and something that becomes<00:18:09.080> attractive<00:18:09.520> to<00:18:09.679> larger 00:18:10.549 --> 00:18:10.559 align:start position:0% becomes attractive to larger 00:18:10.559 --> 00:18:13.430 align:start position:0% becomes attractive to larger Enterprises<00:18:11.559> so<00:18:12.000> that<00:18:12.240> has<00:18:12.840> um<00:18:13.039> if<00:18:13.120> you're 00:18:13.430 --> 00:18:13.440 align:start position:0% Enterprises so that has um if you're 00:18:13.440 --> 00:18:15.990 align:start position:0% Enterprises so that has um if you're curious<00:18:13.880> about<00:18:14.240> that<00:18:14.640> uh<00:18:14.799> today<00:18:15.080> we<00:18:15.280> released 00:18:15.990 --> 00:18:16.000 align:start position:0% curious about that uh today we released 00:18:16.000 --> 00:18:19.630 align:start position:0% curious about that uh today we released the<00:18:16.159> white<00:18:16.440> paper<00:18:17.159> for<00:18:17.480> criet<00:18:17.960> in<00:18:18.280> depth<00:18:19.280> um<00:18:19.440> to 00:18:19.630 --> 00:18:19.640 align:start position:0% the white paper for criet in depth um to 00:18:19.640 --> 00:18:25.350 align:start position:0% the white paper for criet in depth um to go<00:18:19.840> out<00:18:20.200> this<00:18:20.400> again<00:18:20.640> is<00:18:21.280> uh<00:18:22.080> thank<00:18:22.280> you<00:18:23.159> it<00:18:23.280> is 00:18:25.350 --> 00:18:25.360 align:start position:0% go out this again is uh thank you it is 00:18:25.360 --> 00:18:27.909 align:start position:0% go out this again is uh thank you it is out<00:18:26.360> it<00:18:26.720> uh<00:18:26.880> it<00:18:27.000> almost<00:18:27.320> didn't<00:18:27.559> get<00:18:27.720> out 00:18:27.909 --> 00:18:27.919 align:start position:0% out it uh it almost didn't get out 00:18:27.919 --> 00:18:31.110 align:start position:0% out it uh it almost didn't get out because<00:18:28.120> of<00:18:28.280> the<00:18:28.360> network<00:18:28.799> here<00:18:29.000> I<00:18:29.080> had<00:18:29.240> to<00:18:30.080> to 00:18:31.110 --> 00:18:31.120 align:start position:0% because of the network here I had to to 00:18:31.120 --> 00:18:34.270 align:start position:0% because of the network here I had to to uh<00:18:32.120> to<00:18:32.679> uh<00:18:33.039> push<00:18:33.280> it<00:18:33.400> up<00:18:33.520> to<00:18:33.720> GitHub<00:18:34.159> this 00:18:34.270 --> 00:18:34.280 align:start position:0% uh to uh push it up to GitHub this 00:18:34.280 --> 00:18:35.549 align:start position:0% uh to uh push it up to GitHub this morning<00:18:34.559> and<00:18:34.760> I<00:18:34.919> I<00:18:35.000> thought<00:18:35.120> it<00:18:35.200> was<00:18:35.320> going<00:18:35.440> to 00:18:35.549 --> 00:18:35.559 align:start position:0% morning and I I thought it was going to 00:18:35.559 --> 00:18:39.750 align:start position:0% morning and I I thought it was going to choke<00:18:35.799> on<00:18:35.960> it<00:18:36.720> it<00:18:36.840> is<00:18:37.000> 26<00:18:37.480> pages<00:18:38.120> long<00:18:39.120> uh<00:18:39.320> but 00:18:39.750 --> 00:18:39.760 align:start position:0% choke on it it is 26 pages long uh but 00:18:39.760 --> 00:18:41.870 align:start position:0% choke on it it is 26 pages long uh but uh<00:18:39.880> it<00:18:40.120> has<00:18:40.320> some<00:18:40.799> uh<00:18:40.919> fairly<00:18:41.280> good<00:18:41.480> detail 00:18:41.870 --> 00:18:41.880 align:start position:0% uh it has some uh fairly good detail 00:18:41.880 --> 00:18:42.630 align:start position:0% uh it has some uh fairly good detail about 00:18:42.630 --> 00:18:42.640 align:start position:0% about 00:18:42.640 --> 00:18:46.190 align:start position:0% about cets<00:18:43.640> um<00:18:44.120> but<00:18:44.280> that<00:18:44.440> is<00:18:45.120> coming<00:18:45.919> uh<00:18:46.039> we're 00:18:46.190 --> 00:18:46.200 align:start position:0% cets um but that is coming uh we're 00:18:46.200 --> 00:18:49.430 align:start position:0% cets um but that is coming uh we're building<00:18:46.679> that<00:18:47.480> now<00:18:48.480> um<00:18:48.760> so<00:18:49.039> you're<00:18:49.200> not<00:18:49.320> going 00:18:49.430 --> 00:18:49.440 align:start position:0% building that now um so you're not going 00:18:49.440 --> 00:18:50.590 align:start position:0% building that now um so you're not going to<00:18:49.520> be<00:18:49.600> able<00:18:49.720> to<00:18:49.799> go<00:18:49.919> out<00:18:50.039> and<00:18:50.159> start<00:18:50.320> writing 00:18:50.590 --> 00:18:50.600 align:start position:0% to be able to go out and start writing 00:18:50.600 --> 00:18:53.470 align:start position:0% to be able to go out and start writing criet<00:18:51.120> tomorrow<00:18:51.880> or<00:18:52.120> today<00:18:52.799> I<00:18:52.960> know<00:18:53.159> some<00:18:53.320> of 00:18:53.470 --> 00:18:53.480 align:start position:0% criet tomorrow or today I know some of 00:18:53.480 --> 00:18:56.190 align:start position:0% criet tomorrow or today I know some of you<00:18:54.200> I<00:18:54.520> watch<00:18:54.799> presentations<00:18:55.520> you<00:18:55.640> start 00:18:56.190 --> 00:18:56.200 align:start position:0% you I watch presentations you start 00:18:56.200 --> 00:18:57.990 align:start position:0% you I watch presentations you start before<00:18:56.440> the<00:18:56.600> presentation<00:18:57.080> is<00:18:57.240> over<00:18:57.600> I<00:18:57.720> see 00:18:57.990 --> 00:18:58.000 align:start position:0% before the presentation is over I see 00:18:58.000 --> 00:18:59.830 align:start position:0% before the presentation is over I see people<00:18:58.760> you<00:18:58.799> know<00:18:58.919> downloading<00:18:59.440> code<00:18:59.679> and 00:18:59.830 --> 00:18:59.840 align:start position:0% people you know downloading code and 00:18:59.840 --> 00:19:01.909 align:start position:0% people you know downloading code and starting<00:19:00.120> to<00:19:00.280> try<00:19:00.559> things<00:19:00.760> out<00:19:01.280> can't<00:19:01.480> do<00:19:01.720> that 00:19:01.909 --> 00:19:01.919 align:start position:0% starting to try things out can't do that 00:19:01.919 --> 00:19:03.630 align:start position:0% starting to try things out can't do that yet<00:19:02.320> but<00:19:02.440> you<00:19:02.559> can<00:19:02.679> read<00:19:02.880> the<00:19:03.080> spec<00:19:03.360> so<00:19:03.480> you<00:19:03.559> can 00:19:03.630 --> 00:19:03.640 align:start position:0% yet but you can read the spec so you can 00:19:03.640 --> 00:19:05.430 align:start position:0% yet but you can read the spec so you can start<00:19:03.880> planning<00:19:04.320> for<00:19:04.520> it<00:19:04.640> and<00:19:04.799> thinking<00:19:05.120> about 00:19:05.430 --> 00:19:05.440 align:start position:0% start planning for it and thinking about 00:19:05.440 --> 00:19:07.830 align:start position:0% start planning for it and thinking about new<00:19:05.679> Solutions<00:19:06.520> new<00:19:06.840> business<00:19:07.200> opportunities 00:19:07.830 --> 00:19:07.840 align:start position:0% new Solutions new business opportunities 00:19:07.840 --> 00:19:08.590 align:start position:0% new Solutions new business opportunities for 00:19:08.590 --> 00:19:08.600 align:start position:0% for 00:19:08.600 --> 00:19:11.230 align:start position:0% for you<00:19:09.600> um<00:19:09.960> what<00:19:10.120> you<00:19:10.280> can<00:19:10.520> do<00:19:10.720> today<00:19:11.000> and<00:19:11.120> I'm 00:19:11.230 --> 00:19:11.240 align:start position:0% you um what you can do today and I'm 00:19:11.240 --> 00:19:13.430 align:start position:0% you um what you can do today and I'm proud<00:19:11.480> to<00:19:11.600> announce<00:19:11.919> is<00:19:12.039> Bletchley<00:19:12.559> V1<00:19:13.280> and 00:19:13.430 --> 00:19:13.440 align:start position:0% proud to announce is Bletchley V1 and 00:19:13.440 --> 00:19:15.630 align:start position:0% proud to announce is Bletchley V1 and this<00:19:13.559> is<00:19:13.760> our<00:19:14.520> uh<00:19:14.720> ethereum<00:19:15.159> consorti 00:19:15.630 --> 00:19:15.640 align:start position:0% this is our uh ethereum consorti 00:19:15.640 --> 00:19:18.390 align:start position:0% this is our uh ethereum consorti blockchain<00:19:16.039> network<00:19:16.480> ethereum<00:19:17.039> is<00:19:17.280> the<00:19:17.520> first 00:19:18.390 --> 00:19:18.400 align:start position:0% blockchain network ethereum is the first 00:19:18.400 --> 00:19:22.070 align:start position:0% blockchain network ethereum is the first again<00:19:19.159> in<00:19:19.360> the<00:19:19.559> marketplace<00:19:20.559> with<00:19:20.840> a<00:19:21.760> uh<00:19:21.919> and 00:19:22.070 --> 00:19:22.080 align:start position:0% again in the marketplace with a uh and 00:19:22.080 --> 00:19:25.110 align:start position:0% again in the marketplace with a uh and this<00:19:22.200> is<00:19:22.840> anywhere<00:19:23.159> from<00:19:23.360> two<00:19:23.720> to<00:19:24.000> hundreds<00:19:24.440> of 00:19:25.110 --> 00:19:25.120 align:start position:0% this is anywhere from two to hundreds of 00:19:25.120 --> 00:19:28.510 align:start position:0% this is anywhere from two to hundreds of nodes<00:19:26.120> uh<00:19:26.280> by<00:19:26.480> answering<00:19:27.480> uh<00:19:28.039> a<00:19:28.159> couple<00:19:28.400> of 00:19:28.510 --> 00:19:28.520 align:start position:0% nodes uh by answering uh a couple of 00:19:28.520 --> 00:19:30.630 align:start position:0% nodes uh by answering uh a couple of simp<00:19:28.679> simple<00:19:29.039> questions<00:19:29.960> so<00:19:30.159> when<00:19:30.280> we<00:19:30.440> went 00:19:30.630 --> 00:19:30.640 align:start position:0% simp simple questions so when we went 00:19:30.640 --> 00:19:31.909 align:start position:0% simp simple questions so when we went down<00:19:30.840> this<00:19:30.960> and<00:19:31.080> we<00:19:31.159> started<00:19:31.400> to<00:19:31.520> say<00:19:31.799> okay 00:19:31.909 --> 00:19:31.919 align:start position:0% down this and we started to say okay 00:19:31.919 --> 00:19:33.549 align:start position:0% down this and we started to say okay what<00:19:32.039> does<00:19:32.159> the<00:19:32.360> Consortium<00:19:32.919> Network<00:19:33.360> look 00:19:33.549 --> 00:19:33.559 align:start position:0% what does the Consortium Network look 00:19:33.559 --> 00:19:36.830 align:start position:0% what does the Consortium Network look like<00:19:33.799> for<00:19:34.360> ethereum<00:19:35.360> so<00:19:35.600> we<00:19:35.799> we<00:19:35.919> do<00:19:36.159> this<00:19:36.280> a<00:19:36.440> lot 00:19:36.830 --> 00:19:36.840 align:start position:0% like for ethereum so we we do this a lot 00:19:36.840 --> 00:19:38.669 align:start position:0% like for ethereum so we we do this a lot we<00:19:36.960> have<00:19:37.120> a<00:19:37.240> lot<00:19:37.360> of<00:19:37.840> companies<00:19:38.280> come<00:19:38.400> to<00:19:38.559> us 00:19:38.669 --> 00:19:38.679 align:start position:0% we have a lot of companies come to us 00:19:38.679 --> 00:19:39.950 align:start position:0% we have a lot of companies come to us and<00:19:38.760> say<00:19:38.960> hey<00:19:39.039> we<00:19:39.159> want<00:19:39.240> to<00:19:39.320> start<00:19:39.480> a 00:19:39.950 --> 00:19:39.960 align:start position:0% and say hey we want to start a 00:19:39.960 --> 00:19:42.110 align:start position:0% and say hey we want to start a Consortium<00:19:40.960> you<00:19:41.080> know<00:19:41.200> how<00:19:41.320> do<00:19:41.440> we<00:19:41.640> set<00:19:41.880> these 00:19:42.110 --> 00:19:42.120 align:start position:0% Consortium you know how do we set these 00:19:42.120 --> 00:19:44.390 align:start position:0% Consortium you know how do we set these up<00:19:42.640> it's<00:19:42.760> not<00:19:42.919> a<00:19:43.200> private<00:19:43.720> the<00:19:43.880> private 00:19:44.390 --> 00:19:44.400 align:start position:0% up it's not a private the private 00:19:44.400 --> 00:19:46.390 align:start position:0% up it's not a private the private etherum<00:19:44.799> network<00:19:45.120> is<00:19:45.200> easy<00:19:45.640> install<00:19:45.960> a<00:19:46.080> node 00:19:46.390 --> 00:19:46.400 align:start position:0% etherum network is easy install a node 00:19:46.400 --> 00:19:49.430 align:start position:0% etherum network is easy install a node and<00:19:46.559> you<00:19:46.960> you<00:19:47.200> stand<00:19:47.480> it<00:19:47.640> up<00:19:48.559> so<00:19:49.000> uh<00:19:49.080> we<00:19:49.200> had<00:19:49.320> to 00:19:49.430 --> 00:19:49.440 align:start position:0% and you you stand it up so uh we had to 00:19:49.440 --> 00:19:50.590 align:start position:0% and you you stand it up so uh we had to go<00:19:49.600> through<00:19:49.760> and<00:19:49.919> figure<00:19:50.120> out<00:19:50.320> you<00:19:50.400> know<00:19:50.520> what 00:19:50.590 --> 00:19:50.600 align:start position:0% go through and figure out you know what 00:19:50.600 --> 00:19:52.510 align:start position:0% go through and figure out you know what are<00:19:50.720> the<00:19:50.880> requirements<00:19:51.640> this<00:19:51.880> list<00:19:52.120> of 00:19:52.510 --> 00:19:52.520 align:start position:0% are the requirements this list of 00:19:52.520 --> 00:19:55.270 align:start position:0% are the requirements this list of requirements<00:19:53.520> we<00:19:53.640> saw<00:19:54.400> uh<00:19:54.600> consistently 00:19:55.270 --> 00:19:55.280 align:start position:0% requirements we saw uh consistently 00:19:55.280 --> 00:19:56.990 align:start position:0% requirements we saw uh consistently takes<00:19:55.520> about<00:19:55.760> three<00:19:56.000> weeks<00:19:56.360> to<00:19:56.520> get<00:19:56.720> right 00:19:56.990 --> 00:19:57.000 align:start position:0% takes about three weeks to get right 00:19:57.000 --> 00:19:58.029 align:start position:0% takes about three weeks to get right that's<00:19:57.159> everything<00:19:57.480> from<00:19:57.640> network 00:19:58.029 --> 00:19:58.039 align:start position:0% that's everything from network 00:19:58.039 --> 00:19:59.350 align:start position:0% that's everything from network configuration 00:19:59.350 --> 00:19:59.360 align:start position:0% configuration 00:19:59.360 --> 00:20:00.789 align:start position:0% configuration isolation<00:20:00.080> where<00:20:00.200> do<00:20:00.280> you<00:20:00.360> want<00:20:00.440> to<00:20:00.520> put<00:20:00.640> your 00:20:00.789 --> 00:20:00.799 align:start position:0% isolation where do you want to put your 00:20:00.799 --> 00:20:01.909 align:start position:0% isolation where do you want to put your miners<00:20:01.200> where<00:20:01.320> do<00:20:01.400> you<00:20:01.440> want<00:20:01.559> to<00:20:01.640> put<00:20:01.760> your 00:20:01.909 --> 00:20:01.919 align:start position:0% miners where do you want to put your 00:20:01.919 --> 00:20:04.430 align:start position:0% miners where do you want to put your transaction<00:20:02.559> nodes<00:20:03.559> how<00:20:03.679> do<00:20:03.799> you<00:20:03.960> automate 00:20:04.430 --> 00:20:04.440 align:start position:0% transaction nodes how do you automate 00:20:04.440 --> 00:20:06.590 align:start position:0% transaction nodes how do you automate this<00:20:04.600> so<00:20:04.799> it's<00:20:05.159> it's<00:20:05.400> very<00:20:05.720> fast<00:20:06.000> and<00:20:06.159> easy<00:20:06.400> to 00:20:06.590 --> 00:20:06.600 align:start position:0% this so it's it's very fast and easy to 00:20:06.600 --> 00:20:09.549 align:start position:0% this so it's it's very fast and easy to do<00:20:07.600> so<00:20:07.799> we<00:20:07.919> took<00:20:08.120> this<00:20:08.280> three-week<00:20:08.799> process 00:20:09.549 --> 00:20:09.559 align:start position:0% do so we took this three-week process 00:20:09.559 --> 00:20:11.909 align:start position:0% do so we took this three-week process and<00:20:09.679> we<00:20:09.799> got<00:20:09.960> it<00:20:10.080> down<00:20:10.360> we<00:20:10.520> eliminated<00:20:11.520> all<00:20:11.760> but 00:20:11.909 --> 00:20:11.919 align:start position:0% and we got it down we eliminated all but 00:20:11.919 --> 00:20:12.950 align:start position:0% and we got it down we eliminated all but two<00:20:12.120> of<00:20:12.240> the 00:20:12.950 --> 00:20:12.960 align:start position:0% two of the 00:20:12.960 --> 00:20:15.390 align:start position:0% two of the steps<00:20:13.960> okay<00:20:14.159> you<00:20:14.280> still<00:20:14.520> have<00:20:14.679> to<00:20:14.799> read<00:20:15.000> up<00:20:15.159> on 00:20:15.390 --> 00:20:15.400 align:start position:0% steps okay you still have to read up on 00:20:15.400 --> 00:20:17.669 align:start position:0% steps okay you still have to read up on how<00:20:15.520> to<00:20:15.679> do<00:20:15.960> ethereum<00:20:16.960> once<00:20:17.120> you<00:20:17.240> deploy<00:20:17.559> an 00:20:17.669 --> 00:20:17.679 align:start position:0% how to do ethereum once you deploy an 00:20:17.679 --> 00:20:19.270 align:start position:0% how to do ethereum once you deploy an ethereum<00:20:18.120> Consortium<00:20:18.600> Network<00:20:18.919> you<00:20:19.039> still 00:20:19.270 --> 00:20:19.280 align:start position:0% ethereum Consortium Network you still 00:20:19.280 --> 00:20:21.149 align:start position:0% ethereum Consortium Network you still have<00:20:19.400> to<00:20:19.880> understand<00:20:20.559> you<00:20:20.679> know<00:20:20.799> how<00:20:20.880> to<00:20:21.000> write 00:20:21.149 --> 00:20:21.159 align:start position:0% have to understand you know how to write 00:20:21.159 --> 00:20:24.870 align:start position:0% have to understand you know how to write a<00:20:21.280> smart<00:20:21.600> contract<00:20:22.440> um<00:20:23.360> but<00:20:23.720> uh<00:20:24.280> we<00:20:24.480> we<00:20:24.600> we<00:20:24.720> did 00:20:24.870 --> 00:20:24.880 align:start position:0% a smart contract um but uh we we we did 00:20:24.880 --> 00:20:26.549 align:start position:0% a smart contract um but uh we we we did all<00:20:25.120> this<00:20:25.320> and<00:20:25.440> we<00:20:25.559> got<00:20:25.679> it<00:20:25.840> down<00:20:26.000> to<00:20:26.280> five 00:20:26.549 --> 00:20:26.559 align:start position:0% all this and we got it down to five 00:20:26.559 --> 00:20:28.669 align:start position:0% all this and we got it down to five minutes<00:20:27.480> answering<00:20:27.919> eight<00:20:28.159> simple<00:20:28.400> questions 00:20:28.669 --> 00:20:28.679 align:start position:0% minutes answering eight simple questions 00:20:28.679 --> 00:20:31.230 align:start position:0% minutes answering eight simple questions questions<00:20:29.559> and<00:20:29.640> you<00:20:29.760> can<00:20:29.960> deploy<00:20:30.440> again<00:20:31.080> as 00:20:31.230 --> 00:20:31.240 align:start position:0% questions and you can deploy again as 00:20:31.240 --> 00:20:36.029 align:start position:0% questions and you can deploy again as little<00:20:31.480> as<00:20:31.679> two<00:20:32.480> to<00:20:33.360> hundreds<00:20:34.360> of<00:20:34.679> nodes<00:20:35.159> on<00:20:35.360> a 00:20:36.029 --> 00:20:36.039 align:start position:0% little as two to hundreds of nodes on a 00:20:36.039 --> 00:20:39.510 align:start position:0% little as two to hundreds of nodes on a private<00:20:37.039> uh<00:20:37.159> ethereum<00:20:37.679> Consortium<00:20:38.520> Network 00:20:39.510 --> 00:20:39.520 align:start position:0% private uh ethereum Consortium Network 00:20:39.520 --> 00:20:41.430 align:start position:0% private uh ethereum Consortium Network which<00:20:40.200> is<00:20:40.360> staggering<00:20:40.840> we<00:20:40.960> thought<00:20:41.080> we<00:20:41.200> did<00:20:41.320> a 00:20:41.430 --> 00:20:41.440 align:start position:0% which is staggering we thought we did a 00:20:41.440 --> 00:20:43.789 align:start position:0% which is staggering we thought we did a great<00:20:41.640> job<00:20:41.919> going<00:20:42.120> in<00:20:42.559> from<00:20:42.840> two<00:20:43.120> days<00:20:43.360> to<00:20:43.559> 20 00:20:43.789 --> 00:20:43.799 align:start position:0% great job going in from two days to 20 00:20:43.799 --> 00:20:46.750 align:start position:0% great job going in from two days to 20 minutes<00:20:44.080> for<00:20:44.200> a<00:20:44.280> single<00:20:44.640> ethereum<00:20:45.000> node<00:20:45.720> to<00:20:46.600> uh 00:20:46.750 --> 00:20:46.760 align:start position:0% minutes for a single ethereum node to uh 00:20:46.760 --> 00:20:48.710 align:start position:0% minutes for a single ethereum node to uh this<00:20:47.120> massive<00:20:47.559> Network<00:20:47.960> that<00:20:48.080> you<00:20:48.200> can<00:20:48.360> deploy 00:20:48.710 --> 00:20:48.720 align:start position:0% this massive Network that you can deploy 00:20:48.720 --> 00:20:51.909 align:start position:0% this massive Network that you can deploy in<00:20:48.880> very<00:20:49.080> little 00:20:51.909 --> 00:20:51.919 align:start position:0% 00:20:51.919 --> 00:20:56.470 align:start position:0% time<00:20:52.919> so<00:20:53.840> thank<00:20:54.320> you<00:20:55.320> thank<00:20:55.480> you<00:20:55.720> thanks<00:20:56.000> Sid 00:20:56.470 --> 00:20:56.480 align:start position:0% time so thank you thank you thanks Sid 00:20:56.480 --> 00:20:58.710 align:start position:0% time so thank you thank you thanks Sid Isaac<00:20:56.880> those<00:20:57.080> guys<00:20:57.200> are<00:20:57.320> out<00:20:57.559> here<00:20:58.200> they<00:20:58.320> were 00:20:58.710 --> 00:20:58.720 align:start position:0% Isaac those guys are out here they were 00:20:58.720 --> 00:21:00.390 align:start position:0% Isaac those guys are out here they were at<00:20:58.799> 3:00<00:20:59.200> in<00:20:59.280> the<00:20:59.360> morning<00:20:59.640> making<00:20:59.880> sure<00:21:00.200> that 00:21:00.390 --> 00:21:00.400 align:start position:0% at 3:00 in the morning making sure that 00:21:00.400 --> 00:21:02.990 align:start position:0% at 3:00 in the morning making sure that this<00:21:01.080> so<00:21:01.280> you<00:21:01.640> guys<00:21:01.799> can<00:21:02.000> find<00:21:02.320> this<00:21:02.640> the<00:21:02.760> link 00:21:02.990 --> 00:21:03.000 align:start position:0% this so you guys can find this the link 00:21:03.000 --> 00:21:05.630 align:start position:0% this so you guys can find this the link is<00:21:04.000> uh<00:21:04.159> out<00:21:04.360> on<00:21:04.600> Azure<00:21:05.039> right<00:21:05.159> now<00:21:05.400> you<00:21:05.480> can 00:21:05.630 --> 00:21:05.640 align:start position:0% is uh out on Azure right now you can 00:21:05.640 --> 00:21:07.190 align:start position:0% is uh out on Azure right now you can find<00:21:05.799> the<00:21:05.960> blog<00:21:06.240> post<00:21:06.440> it'll<00:21:06.679> take<00:21:06.840> you<00:21:07.000> right 00:21:07.190 --> 00:21:07.200 align:start position:0% find the blog post it'll take you right 00:21:07.200 --> 00:21:09.310 align:start position:0% find the blog post it'll take you right there<00:21:07.919> this<00:21:08.039> is<00:21:08.400> uh<00:21:08.600> real<00:21:08.799> quickly<00:21:09.120> what<00:21:09.200> it 00:21:09.310 --> 00:21:09.320 align:start position:0% there this is uh real quickly what it 00:21:09.320 --> 00:21:11.950 align:start position:0% there this is uh real quickly what it looks<00:21:09.559> like<00:21:09.760> it<00:21:09.880> creates<00:21:10.240> multiple<00:21:10.960> subnets 00:21:11.950 --> 00:21:11.960 align:start position:0% looks like it creates multiple subnets 00:21:11.960 --> 00:21:14.070 align:start position:0% looks like it creates multiple subnets um<00:21:12.240> and<00:21:12.360> it<00:21:12.520> puts<00:21:12.799> each<00:21:13.080> Consortium<00:21:13.600> member<00:21:13.919> in 00:21:14.070 --> 00:21:14.080 align:start position:0% um and it puts each Consortium member in 00:21:14.080 --> 00:21:16.789 align:start position:0% um and it puts each Consortium member in its<00:21:14.279> own<00:21:14.760> separate<00:21:15.279> subnet<00:21:16.279> uh<00:21:16.360> for<00:21:16.520> example 00:21:16.789 --> 00:21:16.799 align:start position:0% its own separate subnet uh for example 00:21:16.799 --> 00:21:18.669 align:start position:0% its own separate subnet uh for example the<00:21:16.880> miners<00:21:17.240> are<00:21:17.360> on<00:21:17.520> their<00:21:17.640> own<00:21:17.880> subnet<00:21:18.520> you 00:21:18.669 --> 00:21:18.679 align:start position:0% the miners are on their own subnet you 00:21:18.679 --> 00:21:20.789 align:start position:0% the miners are on their own subnet you can't<00:21:18.919> reach<00:21:19.200> the<00:21:19.320> miners<00:21:19.720> from<00:21:19.919> the<00:21:20.120> internet 00:21:20.789 --> 00:21:20.799 align:start position:0% can't reach the miners from the internet 00:21:20.799 --> 00:21:23.110 align:start position:0% can't reach the miners from the internet you<00:21:20.880> can<00:21:21.039> only<00:21:21.240> reach<00:21:21.480> the<00:21:21.600> miners<00:21:22.559> from<00:21:22.840> the 00:21:23.110 --> 00:21:23.120 align:start position:0% you can only reach the miners from the 00:21:23.120 --> 00:21:24.830 align:start position:0% you can only reach the miners from the transaction<00:21:23.679> nodes<00:21:24.200> and<00:21:24.320> the<00:21:24.440> transaction 00:21:24.830 --> 00:21:24.840 align:start position:0% transaction nodes and the transaction 00:21:24.840 --> 00:21:26.950 align:start position:0% transaction nodes and the transaction nodes<00:21:25.080> are<00:21:25.200> on<00:21:25.279> a<00:21:25.400> separate<00:21:25.679> subnet<00:21:26.159> as<00:21:26.320> well 00:21:26.950 --> 00:21:26.960 align:start position:0% nodes are on a separate subnet as well 00:21:26.960 --> 00:21:28.950 align:start position:0% nodes are on a separate subnet as well so<00:21:27.320> we<00:21:27.440> put<00:21:27.600> a<00:21:27.720> quite<00:21:27.960> dat<00:21:28.120> a<00:21:28.320> quite<00:21:28.640> a<00:21:28.720> bit<00:21:28.840> of 00:21:28.950 --> 00:21:28.960 align:start position:0% so we put a quite dat a quite a bit of 00:21:28.960 --> 00:21:31.190 align:start position:0% so we put a quite dat a quite a bit of thought<00:21:29.159> into<00:21:29.480> this<00:21:30.120> uh<00:21:30.240> it<00:21:30.360> also<00:21:30.559> stands<00:21:30.880> up<00:21:31.039> a 00:21:31.190 --> 00:21:31.200 align:start position:0% thought into this uh it also stands up a 00:21:31.200 --> 00:21:35.310 align:start position:0% thought into this uh it also stands up a portal<00:21:32.080> seeds<00:21:32.760> the<00:21:33.080> network<00:21:33.520> with<00:21:33.840> ether<00:21:34.840> um 00:21:35.310 --> 00:21:35.320 align:start position:0% portal seeds the network with ether um 00:21:35.320 --> 00:21:37.149 align:start position:0% portal seeds the network with ether um and<00:21:35.559> you<00:21:35.679> can<00:21:35.840> go<00:21:36.000> out<00:21:36.200> immediately<00:21:36.640> go<00:21:36.760> to<00:21:36.880> the 00:21:37.149 --> 00:21:37.159 align:start position:0% and you can go out immediately go to the 00:21:37.159 --> 00:21:42.510 align:start position:0% and you can go out immediately go to the portal<00:21:38.320> uh<00:21:39.320> we<00:21:39.480> are<00:21:40.400> um<00:21:41.400> uh<00:21:41.600> allow<00:21:41.880> you<00:21:42.320> to 00:21:42.510 --> 00:21:42.520 align:start position:0% portal uh we are um uh allow you to 00:21:42.520 --> 00:21:44.630 align:start position:0% portal uh we are um uh allow you to really<00:21:42.799> quickly<00:21:43.120> get<00:21:43.279> up<00:21:43.440> to<00:21:43.880> to<00:21:44.039> speed<00:21:44.400> and 00:21:44.630 --> 00:21:44.640 align:start position:0% really quickly get up to to speed and 00:21:44.640 --> 00:21:46.430 align:start position:0% really quickly get up to to speed and and<00:21:44.720> show<00:21:44.880> your<00:21:45.039> network<00:21:45.440> running<00:21:46.080> something 00:21:46.430 --> 00:21:46.440 align:start position:0% and show your network running something 00:21:46.440 --> 00:21:49.190 align:start position:0% and show your network running something our<00:21:46.640> customers<00:21:47.080> have<00:21:47.320> really<00:21:47.520> wanted<00:21:47.840> to<00:21:48.200> see 00:21:49.190 --> 00:21:49.200 align:start position:0% our customers have really wanted to see 00:21:49.200 --> 00:21:51.110 align:start position:0% our customers have really wanted to see so<00:21:49.679> I<00:21:49.760> want<00:21:49.880> to<00:21:49.960> leave<00:21:50.159> you<00:21:50.360> with<00:21:50.720> a<00:21:50.840> little<00:21:51.000> bit 00:21:51.110 --> 00:21:51.120 align:start position:0% so I want to leave you with a little bit 00:21:51.120 --> 00:21:55.070 align:start position:0% so I want to leave you with a little bit of<00:21:51.240> a<00:21:51.360> road<00:21:51.640> map<00:21:52.480> um<00:21:52.720> where<00:21:52.880> we're<00:21:53.120> at<00:21:53.880> so<00:21:54.640> um 00:21:55.070 --> 00:21:55.080 align:start position:0% of a road map um where we're at so um 00:21:55.080 --> 00:21:57.029 align:start position:0% of a road map um where we're at so um earlier<00:21:55.480> this<00:21:55.600> summer<00:21:55.919> we<00:21:56.080> released<00:21:56.480> Dev<00:21:56.760> test 00:21:57.029 --> 00:21:57.039 align:start position:0% earlier this summer we released Dev test 00:21:57.039 --> 00:21:59.789 align:start position:0% earlier this summer we released Dev test labs<00:21:57.440> for<00:21:57.720> blockchain<00:21:58.120> as<00:21:58.240> a<00:21:58.320> Serv<00:21:58.600> service<00:21:59.480> in 00:21:59.789 --> 00:21:59.799 align:start position:0% labs for blockchain as a Serv service in 00:21:59.799 --> 00:22:01.909 align:start position:0% labs for blockchain as a Serv service in general<00:22:00.200> availability<00:22:00.880> so<00:22:01.200> around<00:22:01.480> the<00:22:01.600> world 00:22:01.909 --> 00:22:01.919 align:start position:0% general availability so around the world 00:22:01.919 --> 00:22:04.510 align:start position:0% general availability so around the world you<00:22:02.000> can<00:22:02.240> go<00:22:02.400> out<00:22:02.679> and<00:22:02.880> create<00:22:03.200> a<00:22:03.320> Dev<00:22:03.600> test<00:22:03.880> lab 00:22:04.510 --> 00:22:04.520 align:start position:0% you can go out and create a Dev test lab 00:22:04.520 --> 00:22:07.190 align:start position:0% you can go out and create a Dev test lab if<00:22:04.640> you<00:22:04.760> haven't<00:22:05.000> done<00:22:05.279> that<00:22:05.480> it's<00:22:05.720> very<00:22:06.200> easy 00:22:07.190 --> 00:22:07.200 align:start position:0% if you haven't done that it's very easy 00:22:07.200 --> 00:22:08.630 align:start position:0% if you haven't done that it's very easy that's<00:22:07.320> where<00:22:07.480> you<00:22:07.559> can<00:22:07.720> see<00:22:08.000> all<00:22:08.200> the<00:22:08.480> not 00:22:08.630 --> 00:22:08.640 align:start position:0% that's where you can see all the not 00:22:08.640 --> 00:22:10.029 align:start position:0% that's where you can see all the not just<00:22:08.799> ethereum<00:22:09.279> but<00:22:09.440> all<00:22:09.600> the<00:22:09.720> other 00:22:10.029 --> 00:22:10.039 align:start position:0% just ethereum but all the other 00:22:10.039 --> 00:22:13.269 align:start position:0% just ethereum but all the other blockchains<00:22:11.039> that<00:22:11.200> you<00:22:11.279> want<00:22:11.440> to<00:22:11.640> build<00:22:12.640> um<00:22:12.919> BL 00:22:13.269 --> 00:22:13.279 align:start position:0% blockchains that you want to build um BL 00:22:13.279 --> 00:22:16.630 align:start position:0% blockchains that you want to build um BL cv1<00:22:13.919> is<00:22:14.080> ethereum<00:22:14.559> only<00:22:15.240> right<00:22:15.400> now<00:22:16.000> um<00:22:16.240> first 00:22:16.630 --> 00:22:16.640 align:start position:0% cv1 is ethereum only right now um first 00:22:16.640 --> 00:22:18.909 align:start position:0% cv1 is ethereum only right now um first on<00:22:16.880> ethereum<00:22:17.440> First<00:22:17.679> on<00:22:17.840> Azure<00:22:18.600> for 00:22:18.909 --> 00:22:18.919 align:start position:0% on ethereum First on Azure for 00:22:18.919 --> 00:22:23.110 align:start position:0% on ethereum First on Azure for Consortium<00:22:19.720> Network<00:22:20.720> um<00:22:21.039> kakuda<00:22:21.840> is<00:22:22.279> our<00:22:22.919> uh 00:22:23.110 --> 00:22:23.120 align:start position:0% Consortium Network um kakuda is our uh 00:22:23.120 --> 00:22:24.710 align:start position:0% Consortium Network um kakuda is our uh security<00:22:23.480> work<00:22:23.720> group<00:22:23.960> some<00:22:24.159> of<00:22:24.279> you<00:22:24.480> probably 00:22:24.710 --> 00:22:24.720 align:start position:0% security work group some of you probably 00:22:24.720 --> 00:22:27.390 align:start position:0% security work group some of you probably seen<00:22:24.960> that<00:22:25.159> Community<00:22:26.080> we'll<00:22:26.279> be<00:22:26.520> publishing 00:22:27.390 --> 00:22:27.400 align:start position:0% seen that Community we'll be publishing 00:22:27.400 --> 00:22:29.310 align:start position:0% seen that Community we'll be publishing uh<00:22:27.520> more<00:22:27.760> information<00:22:28.200> about<00:22:28.520> fstar<00:22:29.200> the 00:22:29.310 --> 00:22:29.320 align:start position:0% uh more information about fstar the 00:22:29.320 --> 00:22:32.230 align:start position:0% uh more information about fstar the tools<00:22:29.720> for<00:22:30.039> formal<00:22:30.720> verification<00:22:31.720> to<00:22:31.919> the 00:22:32.230 --> 00:22:32.240 align:start position:0% tools for formal verification to the 00:22:32.240 --> 00:22:34.789 align:start position:0% tools for formal verification to the community<00:22:33.240> uh<00:22:33.320> to<00:22:33.520> help<00:22:33.840> facilitate<00:22:34.360> and<00:22:34.520> move 00:22:34.789 --> 00:22:34.799 align:start position:0% community uh to help facilitate and move 00:22:34.799 --> 00:22:36.950 align:start position:0% community uh to help facilitate and move that<00:22:35.159> effort<00:22:35.520> forward<00:22:35.919> through<00:22:36.080> Microsoft 00:22:36.950 --> 00:22:36.960 align:start position:0% that effort forward through Microsoft 00:22:36.960 --> 00:22:39.950 align:start position:0% that effort forward through Microsoft research<00:22:37.960> and<00:22:38.120> then<00:22:38.679> uh<00:22:39.080> in<00:22:39.320> sometime<00:22:39.720> in<00:22:39.840> the 00:22:39.950 --> 00:22:39.960 align:start position:0% research and then uh in sometime in the 00:22:39.960 --> 00:22:41.830 align:start position:0% research and then uh in sometime in the near<00:22:40.200> near<00:22:40.400> future<00:22:40.679> in<00:22:40.760> a<00:22:40.960> distant<00:22:41.279> galaxy<00:22:41.600> far 00:22:41.830 --> 00:22:41.840 align:start position:0% near near future in a distant galaxy far 00:22:41.840 --> 00:22:44.470 align:start position:0% near near future in a distant galaxy far far<00:22:42.039> away<00:22:42.960> uh<00:22:43.080> we'll<00:22:43.279> have<00:22:43.520> releasing<00:22:44.320> the 00:22:44.470 --> 00:22:44.480 align:start position:0% far away uh we'll have releasing the 00:22:44.480 --> 00:22:47.190 align:start position:0% far away uh we'll have releasing the Bley<00:22:45.000> SDK<00:22:45.960> actually<00:22:46.440> it<00:22:46.520> shouldn't<00:22:46.799> be<00:22:47.039> that 00:22:47.190 --> 00:22:47.200 align:start position:0% Bley SDK actually it shouldn't be that 00:22:47.200 --> 00:22:50.070 align:start position:0% Bley SDK actually it shouldn't be that far<00:22:47.520> and<00:22:47.640> it<00:22:47.720> should<00:22:47.880> be<00:22:48.000> in<00:22:48.120> this<00:22:48.799> galaxy<00:22:49.799> so 00:22:50.070 --> 00:22:50.080 align:start position:0% far and it should be in this galaxy so 00:22:50.080 --> 00:22:51.549 align:start position:0% far and it should be in this galaxy so with<00:22:50.240> that<00:22:50.400> I'd<00:22:50.559> like<00:22:50.679> to<00:22:50.840> thank<00:22:51.039> everyone<00:22:51.400> for 00:22:51.549 --> 00:22:51.559 align:start position:0% with that I'd like to thank everyone for 00:22:51.559 --> 00:22:54.669 align:start position:0% with that I'd like to thank everyone for your<00:22:51.799> time<00:22:52.480> and<00:22:52.880> uh<00:22:53.120> enjoy<00:22:53.400> the<00:22:53.480> rest<00:22:53.600> of<00:22:53.679> the 00:22:54.669 --> 00:22:54.679 align:start position:0% your time and uh enjoy the rest of the 00:22:54.679 --> 00:22:57.430 align:start position:0% your time and uh enjoy the rest of the show<00:22:55.679> thank<00:22:55.840> you<00:22:56.039> Marley 00:22:57.430 --> 00:22:57.440 align:start position:0% show thank you Marley 00:22:57.440 --> 00:22:59.750 align:start position:0% show thank you Marley Gray 00:22:59.750 --> 00:22:59.760 align:start position:0% Gray 00:22:59.760 --> 00:23:05.409 align:start position:0% Gray [Music]