WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:14.910 align:start position:0% [Music] 00:00:14.910 --> 00:00:14.920 align:start position:0% 00:00:14.920 --> 00:00:20.710 align:start position:0% [Music] 00:00:20.710 --> 00:00:20.720 align:start position:0% 00:00:20.720 --> 00:00:21.830 align:start position:0% good 00:00:21.830 --> 00:00:21.840 align:start position:0% good 00:00:21.840 --> 00:00:24.509 align:start position:0% good morning<00:00:22.840> I'm<00:00:23.039> excited<00:00:23.359> to<00:00:23.480> be<00:00:23.640> here<00:00:23.800> this 00:00:24.509 --> 00:00:24.519 align:start position:0% morning I'm excited to be here this 00:00:24.519 --> 00:00:28.589 align:start position:0% morning I'm excited to be here this morning<00:00:25.519> um<00:00:26.439> and<00:00:26.640> to<00:00:27.240> uh<00:00:27.720> guide<00:00:28.000> you<00:00:28.199> through 00:00:28.589 --> 00:00:28.599 align:start position:0% morning um and to uh guide you through 00:00:28.599 --> 00:00:31.429 align:start position:0% morning um and to uh guide you through what<00:00:28.880> I<00:00:29.480> see<00:00:29.720> as<00:00:29.840> a<00:00:30.320> exciting<00:00:30.759> development<00:00:31.320> so 00:00:31.429 --> 00:00:31.439 align:start position:0% what I see as a exciting development so 00:00:31.439 --> 00:00:33.790 align:start position:0% what I see as a exciting development so I'm<00:00:31.599> here<00:00:31.720> to<00:00:31.960> introduce<00:00:32.439> you<00:00:32.800> or<00:00:33.360> better<00:00:33.640> yet 00:00:33.790 --> 00:00:33.800 align:start position:0% I'm here to introduce you or better yet 00:00:33.800 --> 00:00:34.709 align:start position:0% I'm here to introduce you or better yet let 00:00:34.709 --> 00:00:34.719 align:start position:0% let 00:00:34.719 --> 00:00:38.830 align:start position:0% let Cortana<00:00:35.719> introduce<00:00:36.160> you<00:00:36.360> to<00:00:36.680> the<00:00:37.480> uh<00:00:37.760> Galaxy's 00:00:38.830 --> 00:00:38.840 align:start position:0% Cortana introduce you to the uh Galaxy's 00:00:38.840 --> 00:00:42.590 align:start position:0% Cortana introduce you to the uh Galaxy's largest<00:00:39.840> playground<00:00:40.719> for<00:00:40.960> blockchain 00:00:42.590 --> 00:00:42.600 align:start position:0% largest playground for blockchain 00:00:42.600 --> 00:00:45.110 align:start position:0% largest playground for blockchain developers<00:00:43.600> so<00:00:43.879> Microsoft 00:00:45.110 --> 00:00:45.120 align:start position:0% developers so Microsoft 00:00:45.120 --> 00:00:47.670 align:start position:0% developers so Microsoft Azure<00:00:46.120> is<00:00:46.360> a 00:00:47.670 --> 00:00:47.680 align:start position:0% Azure is a 00:00:47.680 --> 00:00:51.590 align:start position:0% Azure is a hyperscale<00:00:48.680> uh<00:00:48.879> Global<00:00:49.399> Cloud<00:00:50.239> platform<00:00:51.239> that 00:00:51.590 --> 00:00:51.600 align:start position:0% hyperscale uh Global Cloud platform that 00:00:51.600 --> 00:00:54.110 align:start position:0% hyperscale uh Global Cloud platform that has<00:00:52.359> the<00:00:52.520> fundamentals<00:00:53.359> to<00:00:53.520> provide<00:00:53.760> you<00:00:53.960> for 00:00:54.110 --> 00:00:54.120 align:start position:0% has the fundamentals to provide you for 00:00:54.120 --> 00:00:56.630 align:start position:0% has the fundamentals to provide you for infra<00:00:54.520> infrastructure<00:00:55.320> services<00:00:56.320> like 00:00:56.630 --> 00:00:56.640 align:start position:0% infra infrastructure services like 00:00:56.640 --> 00:00:58.229 align:start position:0% infra infrastructure services like virtual<00:00:57.000> machines<00:00:57.480> and<00:00:57.680> storage<00:00:58.000> and 00:00:58.229 --> 00:00:58.239 align:start position:0% virtual machines and storage and 00:00:58.239 --> 00:01:01.430 align:start position:0% virtual machines and storage and networking<00:00:59.239> but<00:00:59.399> so<00:00:59.600> much<00:00:59.760> more<00:01:00.280> more<00:01:01.280> uh 00:01:01.430 --> 00:01:01.440 align:start position:0% networking but so much more more uh 00:01:01.440 --> 00:01:03.229 align:start position:0% networking but so much more more uh Microsoft<00:01:01.960> when<00:01:02.160> began<00:01:02.440> the<00:01:02.600> cloud<00:01:02.879> Journey 00:01:03.229 --> 00:01:03.239 align:start position:0% Microsoft when began the cloud Journey 00:01:03.239 --> 00:01:04.390 align:start position:0% Microsoft when began the cloud Journey we<00:01:03.399> actually 00:01:04.390 --> 00:01:04.400 align:start position:0% we actually 00:01:04.400 --> 00:01:07.030 align:start position:0% we actually overshock<00:01:05.400> uh<00:01:05.640> the<00:01:05.920> marketplace<00:01:06.799> and 00:01:07.030 --> 00:01:07.040 align:start position:0% overshock uh the marketplace and 00:01:07.040 --> 00:01:08.749 align:start position:0% overshock uh the marketplace and developed<00:01:07.439> and<00:01:07.600> focused<00:01:08.000> our<00:01:08.159> attention<00:01:08.479> on 00:01:08.749 --> 00:01:08.759 align:start position:0% developed and focused our attention on 00:01:08.759 --> 00:01:10.950 align:start position:0% developed and focused our attention on platform<00:01:09.200> as<00:01:09.320> a<00:01:09.520> service<00:01:10.520> essentially 00:01:10.950 --> 00:01:10.960 align:start position:0% platform as a service essentially 00:01:10.960 --> 00:01:12.510 align:start position:0% platform as a service essentially building<00:01:11.320> a<00:01:11.520> fabric<00:01:11.840> of 00:01:12.510 --> 00:01:12.520 align:start position:0% building a fabric of 00:01:12.520 --> 00:01:15.350 align:start position:0% building a fabric of apis<00:01:13.520> uh<00:01:13.720> that<00:01:13.960> don't<00:01:14.360> have<00:01:14.560> any<00:01:14.880> dependence 00:01:15.350 --> 00:01:15.360 align:start position:0% apis uh that don't have any dependence 00:01:15.360 --> 00:01:17.789 align:start position:0% apis uh that don't have any dependence on<00:01:15.680> particular<00:01:16.159> VMS<00:01:16.640> and<00:01:16.840> instances<00:01:17.520> rather 00:01:17.789 --> 00:01:17.799 align:start position:0% on particular VMS and instances rather 00:01:17.799 --> 00:01:19.590 align:start position:0% on particular VMS and instances rather you<00:01:17.920> just<00:01:18.119> declaratively<00:01:18.920> program<00:01:19.360> what<00:01:19.520> it 00:01:19.590 --> 00:01:19.600 align:start position:0% you just declaratively program what it 00:01:19.600 --> 00:01:20.670 align:start position:0% you just declaratively program what it is<00:01:19.799> your 00:01:20.670 --> 00:01:20.680 align:start position:0% is your 00:01:20.680 --> 00:01:23.190 align:start position:0% is your intentions<00:01:21.680> uh<00:01:21.799> so<00:01:21.960> we<00:01:22.119> have<00:01:22.280> a<00:01:22.560> a<00:01:22.759> huge 00:01:23.190 --> 00:01:23.200 align:start position:0% intentions uh so we have a a huge 00:01:23.200 --> 00:01:25.789 align:start position:0% intentions uh so we have a a huge portfolio<00:01:24.079> of<00:01:24.280> these<00:01:24.640> platform<00:01:25.200> services 00:01:25.789 --> 00:01:25.799 align:start position:0% portfolio of these platform services 00:01:25.799 --> 00:01:28.149 align:start position:0% portfolio of these platform services that<00:01:25.920> you<00:01:26.040> see<00:01:26.439> here<00:01:27.280> now<00:01:27.479> why<00:01:27.640> am<00:01:27.759> i<00:01:27.880> showing 00:01:28.149 --> 00:01:28.159 align:start position:0% that you see here now why am i showing 00:01:28.159 --> 00:01:30.030 align:start position:0% that you see here now why am i showing you<00:01:28.360> these<00:01:28.600> platform<00:01:29.040> Services<00:01:29.520> instead<00:01:29.759> of 00:01:30.030 --> 00:01:30.040 align:start position:0% you these platform Services instead of 00:01:30.040 --> 00:01:31.190 align:start position:0% you these platform Services instead of focusing<00:01:30.439> on 00:01:31.190 --> 00:01:31.200 align:start position:0% focusing on 00:01:31.200 --> 00:01:34.710 align:start position:0% focusing on VMS<00:01:32.200> uh<00:01:32.520> platform<00:01:33.040> services<00:01:33.479> are<00:01:33.680> the<00:01:33.840> future 00:01:34.710 --> 00:01:34.720 align:start position:0% VMS uh platform services are the future 00:01:34.720 --> 00:01:38.149 align:start position:0% VMS uh platform services are the future uh<00:01:34.840> worrying<00:01:35.320> about<00:01:35.680> your<00:01:35.920> VMS<00:01:36.720> and<00:01:37.720> uh<00:01:38.040> you 00:01:38.149 --> 00:01:38.159 align:start position:0% uh worrying about your VMS and uh you 00:01:38.159 --> 00:01:39.789 align:start position:0% uh worrying about your VMS and uh you know<00:01:38.479> what<00:01:38.640> their<00:01:38.880> sizes<00:01:39.280> are<00:01:39.479> and<00:01:39.600> their 00:01:39.789 --> 00:01:39.799 align:start position:0% know what their sizes are and their 00:01:39.799 --> 00:01:41.670 align:start position:0% know what their sizes are and their capabilities<00:01:40.360> are<00:01:40.720> really<00:01:40.920> a<00:01:41.079> thing<00:01:41.200> of<00:01:41.399> the 00:01:41.670 --> 00:01:41.680 align:start position:0% capabilities are really a thing of the 00:01:41.680 --> 00:01:44.310 align:start position:0% capabilities are really a thing of the past<00:01:42.680> uh<00:01:42.840> we<00:01:42.960> are<00:01:43.200> rather<00:01:43.479> getting<00:01:43.759> to<00:01:43.920> a<00:01:44.079> point 00:01:44.310 --> 00:01:44.320 align:start position:0% past uh we are rather getting to a point 00:01:44.320 --> 00:01:47.030 align:start position:0% past uh we are rather getting to a point where<00:01:44.479> you're<00:01:44.719> declaring<00:01:45.719> uh<00:01:45.880> in<00:01:46.159> software 00:01:47.030 --> 00:01:47.040 align:start position:0% where you're declaring uh in software 00:01:47.040 --> 00:01:48.550 align:start position:0% where you're declaring uh in software what<00:01:47.200> your<00:01:47.360> hardware<00:01:47.799> dependencies<00:01:48.399> and 00:01:48.550 --> 00:01:48.560 align:start position:0% what your hardware dependencies and 00:01:48.560 --> 00:01:51.870 align:start position:0% what your hardware dependencies and needs<00:01:49.079> are<00:01:50.079> so<00:01:50.920> uh<00:01:51.079> with<00:01:51.280> this<00:01:51.640> uh<00:01:51.719> for 00:01:51.870 --> 00:01:51.880 align:start position:0% needs are so uh with this uh for 00:01:51.880 --> 00:01:53.190 align:start position:0% needs are so uh with this uh for blockchain<00:01:52.320> developers<00:01:52.799> I'm<00:01:52.880> just<00:01:53.000> going<00:01:53.119> to 00:01:53.190 --> 00:01:53.200 align:start position:0% blockchain developers I'm just going to 00:01:53.200 --> 00:01:54.990 align:start position:0% blockchain developers I'm just going to point<00:01:53.399> out<00:01:53.520> a<00:01:53.640> couple<00:01:53.920> of<00:01:54.079> these<00:01:54.320> this<00:01:54.439> is<00:01:54.640> a<00:01:54.840> an 00:01:54.990 --> 00:01:55.000 align:start position:0% point out a couple of these this is a an 00:01:55.000 --> 00:01:57.029 align:start position:0% point out a couple of these this is a an ey<00:01:55.280> chart<00:01:55.520> slide<00:01:55.840> and<00:01:56.000> believe<00:01:56.240> me<00:01:56.520> this<00:01:56.799> ey 00:01:57.029 --> 00:01:57.039 align:start position:0% ey chart slide and believe me this ey 00:01:57.039 --> 00:01:59.429 align:start position:0% ey chart slide and believe me this ey chart<00:01:57.280> slide<00:01:57.759> has<00:01:57.920> been<00:01:58.280> condensed<00:01:59.280> and 00:01:59.429 --> 00:01:59.439 align:start position:0% chart slide has been condensed and 00:01:59.439 --> 00:02:02.830 align:start position:0% chart slide has been condensed and simpli<00:01:59.960> if<00:02:00.200> it's<00:02:00.360> a<00:02:00.560> much<00:02:00.880> a<00:02:01.039> larger<00:02:01.840> ecosystem 00:02:02.830 --> 00:02:02.840 align:start position:0% simpli if it's a much a larger ecosystem 00:02:02.840 --> 00:02:04.429 align:start position:0% simpli if it's a much a larger ecosystem but<00:02:02.960> you<00:02:03.039> can<00:02:03.159> see<00:02:03.439> some<00:02:03.600> of<00:02:03.759> these<00:02:03.920> services 00:02:04.429 --> 00:02:04.439 align:start position:0% but you can see some of these services 00:02:04.439 --> 00:02:08.229 align:start position:0% but you can see some of these services like<00:02:04.600> notification<00:02:05.719> hubs<00:02:06.719> machine<00:02:07.239> learning 00:02:08.229 --> 00:02:08.239 align:start position:0% like notification hubs machine learning 00:02:08.239 --> 00:02:10.430 align:start position:0% like notification hubs machine learning uh<00:02:08.399> which<00:02:08.560> we<00:02:08.679> have<00:02:09.160> uh<00:02:09.319> rebranded<00:02:10.119> into 00:02:10.430 --> 00:02:10.440 align:start position:0% uh which we have uh rebranded into 00:02:10.440 --> 00:02:13.830 align:start position:0% uh which we have uh rebranded into Cortana<00:02:11.560> analytics<00:02:12.560> um<00:02:12.879> brings<00:02:13.520> machine 00:02:13.830 --> 00:02:13.840 align:start position:0% Cortana analytics um brings machine 00:02:13.840 --> 00:02:17.030 align:start position:0% Cortana analytics um brings machine learning<00:02:14.400> to<00:02:14.599> the<00:02:14.760> masses<00:02:15.519> and<00:02:15.680> makes<00:02:16.000> it<00:02:16.480> um 00:02:17.030 --> 00:02:17.040 align:start position:0% learning to the masses and makes it um 00:02:17.040 --> 00:02:19.630 align:start position:0% learning to the masses and makes it um achievable<00:02:18.040> uh<00:02:18.160> and<00:02:18.360> surfacing<00:02:19.160> uh<00:02:19.319> machine 00:02:19.630 --> 00:02:19.640 align:start position:0% achievable uh and surfacing uh machine 00:02:19.640 --> 00:02:21.710 align:start position:0% achievable uh and surfacing uh machine learning<00:02:20.080> capabilities<00:02:20.640> for<00:02:20.840> prediction 00:02:21.710 --> 00:02:21.720 align:start position:0% learning capabilities for prediction 00:02:21.720 --> 00:02:24.910 align:start position:0% learning capabilities for prediction markets<00:02:22.720> uh<00:02:23.280> around<00:02:23.560> the<00:02:23.680> world<00:02:24.360> the<00:02:24.519> event 00:02:24.910 --> 00:02:24.920 align:start position:0% markets uh around the world the event 00:02:24.920 --> 00:02:28.550 align:start position:0% markets uh around the world the event hubs<00:02:25.480> the<00:02:25.640> key<00:02:26.280> Vault<00:02:27.280> uh<00:02:27.519> so<00:02:27.760> crypto<00:02:28.160> is<00:02:28.319> very 00:02:28.550 --> 00:02:28.560 align:start position:0% hubs the key Vault uh so crypto is very 00:02:28.560 --> 00:02:30.910 align:start position:0% hubs the key Vault uh so crypto is very important<00:02:28.959> we<00:02:29.120> offer<00:02:29.360> a<00:02:29.519> key<00:02:29.680> VA<00:02:30.200> that<00:02:30.400> has<00:02:30.560> a<00:02:30.800> a 00:02:30.910 --> 00:02:30.920 align:start position:0% important we offer a key VA that has a a 00:02:30.920 --> 00:02:32.190 align:start position:0% important we offer a key VA that has a a unique<00:02:31.200> service<00:02:31.560> we<00:02:31.680> think<00:02:31.800> will<00:02:31.920> be<00:02:32.040> of 00:02:32.190 --> 00:02:32.200 align:start position:0% unique service we think will be of 00:02:32.200 --> 00:02:34.229 align:start position:0% unique service we think will be of interest<00:02:32.440> in<00:02:32.640> this<00:02:32.959> community<00:02:33.959> and<00:02:34.080> then 00:02:34.229 --> 00:02:34.239 align:start position:0% interest in this community and then 00:02:34.239 --> 00:02:35.670 align:start position:0% interest in this community and then active<00:02:34.560> director<00:02:34.959> where<00:02:35.080> we<00:02:35.200> talk<00:02:35.400> a<00:02:35.480> little 00:02:35.670 --> 00:02:35.680 align:start position:0% active director where we talk a little 00:02:35.680 --> 00:02:37.710 align:start position:0% active director where we talk a little bit<00:02:35.840> about<00:02:36.280> uh<00:02:36.400> identity<00:02:36.920> and<00:02:37.160> Federated 00:02:37.710 --> 00:02:37.720 align:start position:0% bit about uh identity and Federated 00:02:37.720 --> 00:02:40.149 align:start position:0% bit about uh identity and Federated identity<00:02:38.640> how<00:02:38.720> do<00:02:38.879> we<00:02:39.280> first<00:02:39.640> establish 00:02:40.149 --> 00:02:40.159 align:start position:0% identity how do we first establish 00:02:40.159 --> 00:02:42.790 align:start position:0% identity how do we first establish identity<00:02:41.080> uh<00:02:41.200> and<00:02:41.360> how<00:02:41.440> do<00:02:41.640> we<00:02:42.239> allow<00:02:42.519> you<00:02:42.640> to 00:02:42.790 --> 00:02:42.800 align:start position:0% identity uh and how do we allow you to 00:02:42.800 --> 00:02:45.470 align:start position:0% identity uh and how do we allow you to have<00:02:43.040> composite<00:02:44.000> identities<00:02:45.000> uh<00:02:45.120> that<00:02:45.200> is<00:02:45.319> a 00:02:45.470 --> 00:02:45.480 align:start position:0% have composite identities uh that is a 00:02:45.480 --> 00:02:47.550 align:start position:0% have composite identities uh that is a very<00:02:45.640> important<00:02:46.200> thing<00:02:47.040> and<00:02:47.159> when<00:02:47.319> I<00:02:47.400> talk 00:02:47.550 --> 00:02:47.560 align:start position:0% very important thing and when I talk 00:02:47.560 --> 00:02:49.149 align:start position:0% very important thing and when I talk about<00:02:47.760> Azure<00:02:48.200> I'm<00:02:48.239> going<00:02:48.319> to<00:02:48.440> talk<00:02:48.599> about<00:02:48.800> size 00:02:49.149 --> 00:02:49.159 align:start position:0% about Azure I'm going to talk about size 00:02:49.159 --> 00:02:52.869 align:start position:0% about Azure I'm going to talk about size for<00:02:49.319> a<00:02:49.440> minute<00:02:50.360> so<00:02:51.280> uh<00:02:51.440> this<00:02:51.560> is<00:02:51.959> but<00:02:52.200> one 00:02:52.869 --> 00:02:52.879 align:start position:0% for a minute so uh this is but one 00:02:52.879 --> 00:02:55.030 align:start position:0% for a minute so uh this is but one building<00:02:53.879> this<00:02:54.040> building<00:02:54.319> is<00:02:54.480> very<00:02:54.680> large<00:02:54.959> I 00:02:55.030 --> 00:02:55.040 align:start position:0% building this building is very large I 00:02:55.040 --> 00:02:57.350 align:start position:0% building this building is very large I don't<00:02:55.159> know<00:02:55.239> if<00:02:55.319> you<00:02:55.400> can<00:02:55.599> see<00:02:55.879> the<00:02:56.120> scale<00:02:56.640> here 00:02:57.350 --> 00:02:57.360 align:start position:0% don't know if you can see the scale here 00:02:57.360 --> 00:03:00.910 align:start position:0% don't know if you can see the scale here oops<00:02:58.640> well<00:02:59.640> I<00:02:59.840> I<00:02:59.920> can't<00:03:00.120> pinch<00:03:00.360> in<00:03:00.560> Zoom 00:03:00.910 --> 00:03:00.920 align:start position:0% oops well I I can't pinch in Zoom 00:03:00.920 --> 00:03:03.229 align:start position:0% oops well I I can't pinch in Zoom because<00:03:01.200> it's<00:03:01.680> uh<00:03:01.959> projecting<00:03:02.440> but<00:03:02.599> anyway 00:03:03.229 --> 00:03:03.239 align:start position:0% because it's uh projecting but anyway 00:03:03.239 --> 00:03:05.270 align:start position:0% because it's uh projecting but anyway you<00:03:03.319> can<00:03:03.480> see<00:03:03.720> the<00:03:03.920> cars<00:03:04.440> over<00:03:04.680> there<00:03:04.879> this<00:03:05.000> is 00:03:05.270 --> 00:03:05.280 align:start position:0% you can see the cars over there this is 00:03:05.280 --> 00:03:07.589 align:start position:0% you can see the cars over there this is one<00:03:05.560> building<00:03:05.959> in<00:03:06.360> a<00:03:06.480> typical<00:03:06.879> data<00:03:07.159> center<00:03:07.400> in 00:03:07.589 --> 00:03:07.599 align:start position:0% one building in a typical data center in 00:03:07.599 --> 00:03:10.110 align:start position:0% one building in a typical data center in Azure<00:03:08.599> each<00:03:08.840> data<00:03:09.120> center<00:03:09.560> the<00:03:09.640> new<00:03:09.840> data 00:03:10.110 --> 00:03:10.120 align:start position:0% Azure each data center the new data 00:03:10.120 --> 00:03:12.550 align:start position:0% Azure each data center the new data centers<00:03:10.519> have<00:03:10.799> four<00:03:11.319> of<00:03:11.519> these<00:03:11.720> buildings 00:03:12.550 --> 00:03:12.560 align:start position:0% centers have four of these buildings 00:03:12.560 --> 00:03:16.070 align:start position:0% centers have four of these buildings connected<00:03:13.200> at<00:03:13.560> each<00:03:14.360> location<00:03:15.360> we<00:03:15.519> are<00:03:15.799> adding 00:03:16.070 --> 00:03:16.080 align:start position:0% connected at each location we are adding 00:03:16.080 --> 00:03:19.869 align:start position:0% connected at each location we are adding a<00:03:16.319> million<00:03:17.159> cores<00:03:18.159> uh<00:03:18.319> that's<00:03:18.480> our<00:03:18.680> run<00:03:19.000> rate 00:03:19.869 --> 00:03:19.879 align:start position:0% a million cores uh that's our run rate 00:03:19.879 --> 00:03:22.070 align:start position:0% a million cores uh that's our run rate uh<00:03:20.000> and<00:03:20.120> a<00:03:20.400> very<00:03:21.040> we<00:03:21.200> would<00:03:21.480> every<00:03:21.640> time<00:03:21.799> I<00:03:21.920> say 00:03:22.070 --> 00:03:22.080 align:start position:0% uh and a very we would every time I say 00:03:22.080 --> 00:03:23.949 align:start position:0% uh and a very we would every time I say it's<00:03:22.200> a<00:03:22.280> million<00:03:22.560> cores<00:03:22.879> a<00:03:23.000> year<00:03:23.319> we<00:03:23.480> we<00:03:23.599> up 00:03:23.949 --> 00:03:23.959 align:start position:0% it's a million cores a year we we up 00:03:23.959 --> 00:03:27.509 align:start position:0% it's a million cores a year we we up that<00:03:24.159> so<00:03:24.360> we're<00:03:25.080> growing<00:03:26.080> uh<00:03:26.920> very<00:03:27.200> very 00:03:27.509 --> 00:03:27.519 align:start position:0% that so we're growing uh very very 00:03:27.519 --> 00:03:29.750 align:start position:0% that so we're growing uh very very rapidly<00:03:27.920> in<00:03:28.080> this<00:03:28.280> space<00:03:29.159> now<00:03:29.400> again<00:03:29.560> this 00:03:29.750 --> 00:03:29.760 align:start position:0% rapidly in this space now again this 00:03:29.760 --> 00:03:32.429 align:start position:0% rapidly in this space now again this this<00:03:29.840> is<00:03:29.959> just<00:03:30.120> one<00:03:30.360> data<00:03:30.680> center<00:03:31.480> uh<00:03:31.640> one 00:03:32.429 --> 00:03:32.439 align:start position:0% this is just one data center uh one 00:03:32.439 --> 00:03:34.910 align:start position:0% this is just one data center uh one quarter<00:03:32.879> of<00:03:33.000> a<00:03:33.159> data<00:03:33.439> center<00:03:34.239> now<00:03:34.439> these<00:03:34.640> Data 00:03:34.910 --> 00:03:34.920 align:start position:0% quarter of a data center now these Data 00:03:34.920 --> 00:03:37.830 align:start position:0% quarter of a data center now these Data Centers<00:03:35.400> do<00:03:35.840> span<00:03:36.439> the<00:03:36.599> globe<00:03:37.280> so<00:03:37.480> when<00:03:37.599> we 00:03:37.830 --> 00:03:37.840 align:start position:0% Centers do span the globe so when we 00:03:37.840 --> 00:03:40.070 align:start position:0% Centers do span the globe so when we talk<00:03:38.040> about<00:03:38.319> what's<00:03:38.720> there<00:03:39.400> we<00:03:39.560> are<00:03:39.760> talking 00:03:40.070 --> 00:03:40.080 align:start position:0% talk about what's there we are talking 00:03:40.080 --> 00:03:43.630 align:start position:0% talk about what's there we are talking about<00:03:40.439> hyperscale<00:03:41.439> Global<00:03:42.360> Network<00:03:43.360> um<00:03:43.519> the 00:03:43.630 --> 00:03:43.640 align:start position:0% about hyperscale Global Network um the 00:03:43.640 --> 00:03:45.309 align:start position:0% about hyperscale Global Network um the ones<00:03:43.840> in<00:03:44.080> green<00:03:44.400> that<00:03:44.519> are<00:03:44.720> highlighted<00:03:45.200> those 00:03:45.309 --> 00:03:45.319 align:start position:0% ones in green that are highlighted those 00:03:45.319 --> 00:03:48.350 align:start position:0% ones in green that are highlighted those are<00:03:45.480> coming<00:03:45.879> online<00:03:46.400> later<00:03:46.760> this<00:03:47.200> year<00:03:48.200> but 00:03:48.350 --> 00:03:48.360 align:start position:0% are coming online later this year but 00:03:48.360 --> 00:03:51.509 align:start position:0% are coming online later this year but you<00:03:48.439> can<00:03:48.599> see<00:03:48.840> we<00:03:49.040> basically<00:03:49.799> covered<00:03:50.799> uh 00:03:51.509 --> 00:03:51.519 align:start position:0% you can see we basically covered uh 00:03:51.519 --> 00:03:54.229 align:start position:0% you can see we basically covered uh cover<00:03:51.840> the<00:03:52.000> world<00:03:52.760> um<00:03:52.879> and<00:03:53.040> where<00:03:53.239> we<00:03:53.439> find<00:03:54.040> a 00:03:54.229 --> 00:03:54.239 align:start position:0% cover the world um and where we find a 00:03:54.239 --> 00:03:57.910 align:start position:0% cover the world um and where we find a need<00:03:55.239> particularly<00:03:55.720> if<00:03:55.799> it's<00:03:56.400> regulatory<00:03:57.400> um 00:03:57.910 --> 00:03:57.920 align:start position:0% need particularly if it's regulatory um 00:03:57.920 --> 00:03:59.789 align:start position:0% need particularly if it's regulatory um we<00:03:58.120> and<00:03:58.239> there's<00:03:58.439> a<00:03:58.760> a<00:03:58.959> demand<00:03:59.280> from<00:03:59.400> our 00:03:59.789 --> 00:03:59.799 align:start position:0% we and there's a a demand from our 00:03:59.799 --> 00:04:01.550 align:start position:0% we and there's a a demand from our customers<00:04:00.200> will<00:04:00.400> plop<00:04:00.680> a<00:04:00.840> data<00:04:01.079> center<00:04:01.360> in 00:04:01.550 --> 00:04:01.560 align:start position:0% customers will plop a data center in 00:04:01.560 --> 00:04:04.190 align:start position:0% customers will plop a data center in there<00:04:02.439> uh<00:04:02.560> we<00:04:02.680> have<00:04:02.879> data<00:04:03.079> centers<00:04:03.439> in 00:04:04.190 --> 00:04:04.200 align:start position:0% there uh we have data centers in 00:04:04.200 --> 00:04:06.910 align:start position:0% there uh we have data centers in China<00:04:05.200> um<00:04:05.519> we<00:04:05.640> have<00:04:05.840> data<00:04:06.120> centers<00:04:06.640> coming 00:04:06.910 --> 00:04:06.920 align:start position:0% China um we have data centers coming 00:04:06.920 --> 00:04:11.429 align:start position:0% China um we have data centers coming into<00:04:07.360> Canada<00:04:08.360> uh<00:04:08.560> this<00:04:09.040> year<00:04:10.040> um<00:04:10.280> now<00:04:10.840> Azure<00:04:11.280> is 00:04:11.429 --> 00:04:11.439 align:start position:0% into Canada uh this year um now Azure is 00:04:11.439 --> 00:04:14.350 align:start position:0% into Canada uh this year um now Azure is an<00:04:11.680> open<00:04:12.120> Cloud<00:04:12.920> it<00:04:13.040> is<00:04:13.239> the<00:04:13.400> most<00:04:13.680> open<00:04:14.000> Cloud 00:04:14.350 --> 00:04:14.360 align:start position:0% an open Cloud it is the most open Cloud 00:04:14.360 --> 00:04:17.150 align:start position:0% an open Cloud it is the most open Cloud I<00:04:14.439> would<00:04:14.680> argue<00:04:15.680> um<00:04:16.000> we<00:04:16.120> are<00:04:16.400> not<00:04:16.680> the<00:04:16.840> old 00:04:17.150 --> 00:04:17.160 align:start position:0% I would argue um we are not the old 00:04:17.160 --> 00:04:19.069 align:start position:0% I would argue um we are not the old Microsoft<00:04:17.840> this<00:04:17.959> is<00:04:18.120> the<00:04:18.239> new 00:04:19.069 --> 00:04:19.079 align:start position:0% Microsoft this is the new 00:04:19.079 --> 00:04:22.990 align:start position:0% Microsoft this is the new Microsoft<00:04:20.079> uh<00:04:20.199> we<00:04:20.400> Embrace<00:04:21.280> open<00:04:21.880> source<00:04:22.880> uh 00:04:22.990 --> 00:04:23.000 align:start position:0% Microsoft uh we Embrace open source uh 00:04:23.000 --> 00:04:24.870 align:start position:0% Microsoft uh we Embrace open source uh we<00:04:23.160> actually<00:04:23.440> contribute<00:04:24.000> a<00:04:24.120> great<00:04:24.360> deal<00:04:24.680> to 00:04:24.870 --> 00:04:24.880 align:start position:0% we actually contribute a great deal to 00:04:24.880 --> 00:04:27.710 align:start position:0% we actually contribute a great deal to some<00:04:25.040> of<00:04:25.160> the<00:04:25.400> most<00:04:26.400> uh<00:04:26.600> Innovative<00:04:27.600> uh 00:04:27.710 --> 00:04:27.720 align:start position:0% some of the most uh Innovative uh 00:04:27.720 --> 00:04:29.350 align:start position:0% some of the most uh Innovative uh features<00:04:28.160> that<00:04:28.240> are<00:04:28.400> coming<00:04:28.720> with<00:04:28.919> Cloud<00:04:29.280> I'm 00:04:29.350 --> 00:04:29.360 align:start position:0% features that are coming with Cloud I'm 00:04:29.360 --> 00:04:30.710 align:start position:0% features that are coming with Cloud I'm going<00:04:29.479> to<00:04:29.759> talk<00:04:29.919> about<00:04:30.160> ones<00:04:30.360> that<00:04:30.520> I<00:04:30.600> think 00:04:30.710 --> 00:04:30.720 align:start position:0% going to talk about ones that I think 00:04:30.720 --> 00:04:33.029 align:start position:0% going to talk about ones that I think are<00:04:30.960> very<00:04:31.240> strategic<00:04:32.240> to<00:04:32.440> what<00:04:32.560> we're<00:04:32.759> trying 00:04:33.029 --> 00:04:33.039 align:start position:0% are very strategic to what we're trying 00:04:33.039 --> 00:04:37.390 align:start position:0% are very strategic to what we're trying to<00:04:33.240> do<00:04:33.800> here<00:04:34.800> um<00:04:35.320> with<00:04:35.880> ethereum<00:04:36.880> and<00:04:37.039> our 00:04:37.390 --> 00:04:37.400 align:start position:0% to do here um with ethereum and our 00:04:37.400 --> 00:04:39.830 align:start position:0% to do here um with ethereum and our partners<00:04:38.400> so<00:04:38.680> all<00:04:38.800> of<00:04:39.000> this<00:04:39.120> is<00:04:39.320> available<00:04:39.720> to 00:04:39.830 --> 00:04:39.840 align:start position:0% partners so all of this is available to 00:04:39.840 --> 00:04:42.029 align:start position:0% partners so all of this is available to you<00:04:40.000> in<00:04:40.280> Azure<00:04:40.759> so<00:04:40.919> you<00:04:41.080> pick<00:04:41.280> and<00:04:41.479> choose<00:04:41.919> the 00:04:42.029 --> 00:04:42.039 align:start position:0% you in Azure so you pick and choose the 00:04:42.039 --> 00:04:45.029 align:start position:0% you in Azure so you pick and choose the flavor<00:04:42.759> of<00:04:43.000> os<00:04:43.440> that<00:04:43.600> you<00:04:43.720> want<00:04:44.120> or<00:04:44.720> forget 00:04:45.029 --> 00:04:45.039 align:start position:0% flavor of os that you want or forget 00:04:45.039 --> 00:04:46.670 align:start position:0% flavor of os that you want or forget about<00:04:45.240> the<00:04:45.360> OS<00:04:45.800> pick<00:04:46.000> and<00:04:46.120> choose<00:04:46.440> the 00:04:46.670 --> 00:04:46.680 align:start position:0% about the OS pick and choose the 00:04:46.680 --> 00:04:49.070 align:start position:0% about the OS pick and choose the database<00:04:47.680> the<00:04:47.880> platform<00:04:48.400> the 00:04:49.070 --> 00:04:49.080 align:start position:0% database the platform the 00:04:49.080 --> 00:04:52.230 align:start position:0% database the platform the blockchain<00:04:50.080> um<00:04:50.440> the<00:04:50.680> UI<00:04:51.280> whatever<00:04:51.960> whatever 00:04:52.230 --> 00:04:52.240 align:start position:0% blockchain um the UI whatever whatever 00:04:52.240 --> 00:04:54.590 align:start position:0% blockchain um the UI whatever whatever your<00:04:52.360> Dev<00:04:52.639> tools<00:04:52.960> are<00:04:53.360> will<00:04:53.680> support 00:04:54.590 --> 00:04:54.600 align:start position:0% your Dev tools are will support 00:04:54.600 --> 00:04:57.990 align:start position:0% your Dev tools are will support it<00:04:55.600> so<00:04:56.199> uh<00:04:56.400> again<00:04:56.639> this<00:04:56.759> is<00:04:57.000> hyperscale 00:04:57.990 --> 00:04:58.000 align:start position:0% it so uh again this is hyperscale 00:04:58.000 --> 00:05:02.710 align:start position:0% it so uh again this is hyperscale Enterprise<00:04:58.639> cloud<00:04:59.800> and<00:05:00.440> before<00:05:01.160> the<00:05:01.320> red<00:05:01.680> hat 00:05:02.710 --> 00:05:02.720 align:start position:0% Enterprise cloud and before the red hat 00:05:02.720 --> 00:05:04.870 align:start position:0% Enterprise cloud and before the red hat announcement<00:05:03.720> which<00:05:03.880> was<00:05:04.160> last<00:05:04.440> week<00:05:04.759> I 00:05:04.870 --> 00:05:04.880 align:start position:0% announcement which was last week I 00:05:04.880 --> 00:05:07.029 align:start position:0% announcement which was last week I believe<00:05:05.560> uh<00:05:05.680> we<00:05:05.800> announced<00:05:06.479> Red<00:05:06.759> Hat 00:05:07.029 --> 00:05:07.039 align:start position:0% believe uh we announced Red Hat 00:05:07.039 --> 00:05:09.029 align:start position:0% believe uh we announced Red Hat availability<00:05:08.039> uh<00:05:08.199> for<00:05:08.400> our<00:05:08.520> Enterprise 00:05:09.029 --> 00:05:09.039 align:start position:0% availability uh for our Enterprise 00:05:09.039 --> 00:05:11.310 align:start position:0% availability uh for our Enterprise customers<00:05:09.479> and<00:05:09.639> really<00:05:09.880> anybody<00:05:10.720> one<00:05:10.919> in<00:05:11.080> four 00:05:11.310 --> 00:05:11.320 align:start position:0% customers and really anybody one in four 00:05:11.320 --> 00:05:14.189 align:start position:0% customers and really anybody one in four of<00:05:11.440> our<00:05:11.560> VMS<00:05:11.960> were<00:05:12.400> Linux<00:05:13.400> uh<00:05:13.520> we<00:05:13.720> expect<00:05:14.039> that 00:05:14.189 --> 00:05:14.199 align:start position:0% of our VMS were Linux uh we expect that 00:05:14.199 --> 00:05:16.950 align:start position:0% of our VMS were Linux uh we expect that to<00:05:14.400> about<00:05:15.039> double<00:05:15.720> to<00:05:15.880> be<00:05:16.039> about<00:05:16.360> half<00:05:16.600> of<00:05:16.759> our 00:05:16.950 --> 00:05:16.960 align:start position:0% to about double to be about half of our 00:05:16.960 --> 00:05:20.430 align:start position:0% to about double to be about half of our VMS<00:05:17.360> will<00:05:17.560> be<00:05:17.840> Linux<00:05:18.520> based<00:05:19.520> uh<00:05:19.639> running<00:05:20.199> in 00:05:20.430 --> 00:05:20.440 align:start position:0% VMS will be Linux based uh running in 00:05:20.440 --> 00:05:23.070 align:start position:0% VMS will be Linux based uh running in the<00:05:20.600> cloud<00:05:21.199> now<00:05:21.880> I<00:05:21.960> would<00:05:22.120> be<00:05:22.280> remiss<00:05:22.840> in 00:05:23.070 --> 00:05:23.080 align:start position:0% the cloud now I would be remiss in 00:05:23.080 --> 00:05:25.390 align:start position:0% the cloud now I would be remiss in talking<00:05:23.440> about<00:05:23.800> Regulatory<00:05:24.400> Compliance<00:05:25.319> uh 00:05:25.390 --> 00:05:25.400 align:start position:0% talking about Regulatory Compliance uh 00:05:25.400 --> 00:05:26.950 align:start position:0% talking about Regulatory Compliance uh for<00:05:25.600> those<00:05:25.720> of<00:05:25.840> you<00:05:25.960> that<00:05:26.120> Target<00:05:26.440> Enterprise 00:05:26.950 --> 00:05:26.960 align:start position:0% for those of you that Target Enterprise 00:05:26.960 --> 00:05:29.270 align:start position:0% for those of you that Target Enterprise customers<00:05:27.880> they<00:05:28.039> do<00:05:28.319> tend<00:05:28.560> to<00:05:28.759> care<00:05:29.000> about 00:05:29.270 --> 00:05:29.280 align:start position:0% customers they do tend to care about 00:05:29.280 --> 00:05:31.270 align:start position:0% customers they do tend to care about this<00:05:29.759> stuff<00:05:29.960> we<00:05:30.039> are<00:05:30.160> the<00:05:30.280> most<00:05:30.560> compliant 00:05:31.270 --> 00:05:31.280 align:start position:0% this stuff we are the most compliant 00:05:31.280 --> 00:05:34.230 align:start position:0% this stuff we are the most compliant Cloud<00:05:32.280> uh<00:05:32.400> and<00:05:32.560> have<00:05:32.720> the<00:05:32.880> largest<00:05:33.400> portfolio 00:05:34.230 --> 00:05:34.240 align:start position:0% Cloud uh and have the largest portfolio 00:05:34.240 --> 00:05:37.110 align:start position:0% Cloud uh and have the largest portfolio of<00:05:34.479> certifications<00:05:35.440> in<00:05:35.560> the<00:05:35.840> world<00:05:36.840> uh<00:05:36.960> none 00:05:37.110 --> 00:05:37.120 align:start position:0% of certifications in the world uh none 00:05:37.120 --> 00:05:38.670 align:start position:0% of certifications in the world uh none of<00:05:37.240> our<00:05:37.360> competitors<00:05:37.919> can<00:05:38.120> attest<00:05:38.400> to<00:05:38.560> this 00:05:38.670 --> 00:05:38.680 align:start position:0% of our competitors can attest to this 00:05:38.680 --> 00:05:40.350 align:start position:0% of our competitors can attest to this there's<00:05:38.880> one<00:05:39.039> up<00:05:39.199> put<00:05:39.400> a<00:05:39.560> question<00:05:39.800> mark<00:05:40.120> about 00:05:40.350 --> 00:05:40.360 align:start position:0% there's one up put a question mark about 00:05:40.360 --> 00:05:42.790 align:start position:0% there's one up put a question mark about the<00:05:40.479> Safe<00:05:40.960> Harbor<00:05:41.960> um<00:05:42.199> we'll<00:05:42.400> see<00:05:42.600> what 00:05:42.790 --> 00:05:42.800 align:start position:0% the Safe Harbor um we'll see what 00:05:42.800 --> 00:05:46.469 align:start position:0% the Safe Harbor um we'll see what happens<00:05:43.560> there<00:05:44.560> uh<00:05:45.039> but<00:05:45.400> uh<00:05:45.600> I<00:05:45.840> I<00:05:46.000> guarantee 00:05:46.469 --> 00:05:46.479 align:start position:0% happens there uh but uh I I guarantee 00:05:46.479 --> 00:05:48.430 align:start position:0% happens there uh but uh I I guarantee you<00:05:46.759> if<00:05:46.880> there<00:05:47.000> is<00:05:47.160> a<00:05:47.319> certification<00:05:48.039> to<00:05:48.160> be 00:05:48.430 --> 00:05:48.440 align:start position:0% you if there is a certification to be 00:05:48.440 --> 00:05:51.469 align:start position:0% you if there is a certification to be had<00:05:49.400> we<00:05:49.520> will<00:05:49.720> get<00:05:49.880> it<00:05:50.800> um<00:05:50.960> if<00:05:51.080> there<00:05:51.199> is<00:05:51.319> a 00:05:51.469 --> 00:05:51.479 align:start position:0% had we will get it um if there is a 00:05:51.479 --> 00:05:53.870 align:start position:0% had we will get it um if there is a regulatory<00:05:52.039> hurdle<00:05:52.400> to<00:05:52.560> jump<00:05:53.080> we<00:05:53.199> will<00:05:53.520> jump 00:05:53.870 --> 00:05:53.880 align:start position:0% regulatory hurdle to jump we will jump 00:05:53.880 --> 00:05:58.189 align:start position:0% regulatory hurdle to jump we will jump it<00:05:54.880> um<00:05:55.080> there<00:05:55.199> will<00:05:55.440> not<00:05:55.720> be<00:05:56.039> a<00:05:56.720> blocker<00:05:57.720> uh<00:05:57.840> for 00:05:58.189 --> 00:05:58.199 align:start position:0% it um there will not be a blocker uh for 00:05:58.199 --> 00:06:00.749 align:start position:0% it um there will not be a blocker uh for Azure<00:05:58.680> moving<00:05:59.000> forward 00:06:00.749 --> 00:06:00.759 align:start position:0% Azure moving forward 00:06:00.759 --> 00:06:02.629 align:start position:0% Azure moving forward so<00:06:01.199> what<00:06:01.319> is<00:06:01.520> blockchain<00:06:01.919> as<00:06:02.039> a<00:06:02.199> service<00:06:02.520> what 00:06:02.629 --> 00:06:02.639 align:start position:0% so what is blockchain as a service what 00:06:02.639 --> 00:06:04.790 align:start position:0% so what is blockchain as a service what are<00:06:02.759> we<00:06:02.880> intending<00:06:03.240> to<00:06:03.440> do<00:06:04.240> so<00:06:04.479> the<00:06:04.600> first 00:06:04.790 --> 00:06:04.800 align:start position:0% are we intending to do so the first 00:06:04.800 --> 00:06:06.950 align:start position:0% are we intending to do so the first thing<00:06:04.919> we're<00:06:05.120> doing<00:06:05.680> at<00:06:06.120> uh<00:06:06.280> the<00:06:06.400> Enterprise 00:06:06.950 --> 00:06:06.960 align:start position:0% thing we're doing at uh the Enterprise 00:06:06.960 --> 00:06:09.110 align:start position:0% thing we're doing at uh the Enterprise level<00:06:07.199> so<00:06:07.360> we're<00:06:07.599> targeting<00:06:08.440> primarily<00:06:08.960> our 00:06:09.110 --> 00:06:09.120 align:start position:0% level so we're targeting primarily our 00:06:09.120 --> 00:06:10.749 align:start position:0% level so we're targeting primarily our Enterprise<00:06:09.639> customers<00:06:10.120> but<00:06:10.319> really<00:06:10.560> this 00:06:10.749 --> 00:06:10.759 align:start position:0% Enterprise customers but really this 00:06:10.759 --> 00:06:12.710 align:start position:0% Enterprise customers but really this benefits<00:06:11.319> the<00:06:11.479> entire<00:06:11.840> development 00:06:12.710 --> 00:06:12.720 align:start position:0% benefits the entire development 00:06:12.720 --> 00:06:15.790 align:start position:0% benefits the entire development Community<00:06:13.720> uh<00:06:13.880> we<00:06:14.000> are<00:06:14.360> creating<00:06:15.080> a<00:06:15.280> set<00:06:15.639> of 00:06:15.790 --> 00:06:15.800 align:start position:0% Community uh we are creating a set of 00:06:15.800 --> 00:06:17.830 align:start position:0% Community uh we are creating a set of services<00:06:16.319> that<00:06:16.479> allow<00:06:16.720> our<00:06:16.960> customers<00:06:17.479> to 00:06:17.830 --> 00:06:17.840 align:start position:0% services that allow our customers to 00:06:17.840 --> 00:06:20.469 align:start position:0% services that allow our customers to fail<00:06:18.520> fast<00:06:19.520> most<00:06:19.720> of<00:06:19.840> our<00:06:20.000> Enterprise 00:06:20.469 --> 00:06:20.479 align:start position:0% fail fast most of our Enterprise 00:06:20.479 --> 00:06:22.830 align:start position:0% fail fast most of our Enterprise customers<00:06:20.880> cannot<00:06:21.240> afford<00:06:21.639> to<00:06:22.039> take<00:06:22.240> the<00:06:22.440> jump 00:06:22.830 --> 00:06:22.840 align:start position:0% customers cannot afford to take the jump 00:06:22.840 --> 00:06:25.589 align:start position:0% customers cannot afford to take the jump particularly<00:06:23.240> into<00:06:23.759> ethereum<00:06:24.280> or<00:06:24.599> blockchain 00:06:25.589 --> 00:06:25.599 align:start position:0% particularly into ethereum or blockchain 00:06:25.599 --> 00:06:27.350 align:start position:0% particularly into ethereum or blockchain and<00:06:25.720> use<00:06:25.880> a<00:06:26.080> parachute<00:06:26.639> when<00:06:26.759> they<00:06:26.880> jump<00:06:27.120> out 00:06:27.350 --> 00:06:27.360 align:start position:0% and use a parachute when they jump out 00:06:27.360 --> 00:06:29.430 align:start position:0% and use a parachute when they jump out the<00:06:27.479> plane<00:06:27.880> they<00:06:28.000> need<00:06:28.160> to<00:06:28.319> fall<00:06:28.880> fast<00:06:29.160> and<00:06:29.280> hit 00:06:29.430 --> 00:06:29.440 align:start position:0% the plane they need to fall fast and hit 00:06:29.440 --> 00:06:31.230 align:start position:0% the plane they need to fall fast and hit the<00:06:29.639> ground<00:06:30.000> fast<00:06:30.319> if<00:06:30.400> they're<00:06:30.520> going<00:06:30.599> to<00:06:30.720> fail 00:06:31.230 --> 00:06:31.240 align:start position:0% the ground fast if they're going to fail 00:06:31.240 --> 00:06:34.070 align:start position:0% the ground fast if they're going to fail fail<00:06:31.759> early<00:06:32.759> uh<00:06:32.880> and<00:06:32.960> then<00:06:33.160> get<00:06:33.400> back<00:06:33.599> up<00:06:33.919> and 00:06:34.070 --> 00:06:34.080 align:start position:0% fail early uh and then get back up and 00:06:34.080 --> 00:06:36.350 align:start position:0% fail early uh and then get back up and try<00:06:34.319> it<00:06:34.520> again<00:06:35.160> now<00:06:35.319> how<00:06:35.400> do<00:06:35.560> they<00:06:35.720> do<00:06:36.000> that 00:06:36.350 --> 00:06:36.360 align:start position:0% try it again now how do they do that 00:06:36.360 --> 00:06:39.070 align:start position:0% try it again now how do they do that with<00:06:36.639> it<00:06:37.039> infrastructures<00:06:37.960> and<00:06:38.199> budgets<00:06:38.680> and 00:06:39.070 --> 00:06:39.080 align:start position:0% with it infrastructures and budgets and 00:06:39.080 --> 00:06:41.589 align:start position:0% with it infrastructures and budgets and constraints<00:06:40.080> it's<00:06:40.319> expensive<00:06:40.919> they're<00:06:41.120> too 00:06:41.589 --> 00:06:41.599 align:start position:0% constraints it's expensive they're too 00:06:41.599 --> 00:06:43.909 align:start position:0% constraints it's expensive they're too slow<00:06:42.599> we<00:06:42.759> want<00:06:42.960> our<00:06:43.160> customers<00:06:43.599> and<00:06:43.759> our 00:06:43.909 --> 00:06:43.919 align:start position:0% slow we want our customers and our 00:06:43.919 --> 00:06:45.950 align:start position:0% slow we want our customers and our developers<00:06:44.440> to<00:06:44.560> be<00:06:44.720> able<00:06:44.919> to<00:06:45.240> experiment 00:06:45.950 --> 00:06:45.960 align:start position:0% developers to be able to experiment 00:06:45.960 --> 00:06:48.870 align:start position:0% developers to be able to experiment rapidly<00:06:46.400> at<00:06:46.560> low<00:06:46.960> cost<00:06:47.440> to<00:06:47.599> spin<00:06:47.880> up<00:06:48.120> resources 00:06:48.870 --> 00:06:48.880 align:start position:0% rapidly at low cost to spin up resources 00:06:48.880 --> 00:06:52.070 align:start position:0% rapidly at low cost to spin up resources on<00:06:49.440> demand<00:06:50.440> uh<00:06:50.560> and<00:06:50.800> experiment<00:06:51.440> by<00:06:51.680> mixing 00:06:52.070 --> 00:06:52.080 align:start position:0% on demand uh and experiment by mixing 00:06:52.080 --> 00:06:54.070 align:start position:0% on demand uh and experiment by mixing and<00:06:52.319> matching<00:06:52.840> different<00:06:53.120> Frameworks 00:06:54.070 --> 00:06:54.080 align:start position:0% and matching different Frameworks 00:06:54.080 --> 00:06:56.430 align:start position:0% and matching different Frameworks different<00:06:54.440> platforms<00:06:55.360> different<00:06:55.680> tools<00:06:56.160> to 00:06:56.430 --> 00:06:56.440 align:start position:0% different platforms different tools to 00:06:56.440 --> 00:07:00.189 align:start position:0% different platforms different tools to create<00:06:57.440> the<00:06:57.680> most<00:06:58.120> awesome<00:06:59.120> ethereum<00:06:59.840> based 00:07:00.189 --> 00:07:00.199 align:start position:0% create the most awesome ethereum based 00:07:00.199 --> 00:07:02.110 align:start position:0% create the most awesome ethereum based applications<00:07:01.160> on<00:07:01.319> the 00:07:02.110 --> 00:07:02.120 align:start position:0% applications on the 00:07:02.120 --> 00:07:05.070 align:start position:0% applications on the planet<00:07:03.120> so<00:07:04.039> uh<00:07:04.120> we<00:07:04.280> talk<00:07:04.479> about<00:07:04.680> creating 00:07:05.070 --> 00:07:05.080 align:start position:0% planet so uh we talk about creating 00:07:05.080 --> 00:07:07.430 align:start position:0% planet so uh we talk about creating private<00:07:05.360> ethereum<00:07:06.280> environments<00:07:07.080> uh<00:07:07.199> how<00:07:07.280> do 00:07:07.430 --> 00:07:07.440 align:start position:0% private ethereum environments uh how do 00:07:07.440 --> 00:07:09.510 align:start position:0% private ethereum environments uh how do they<00:07:07.599> do<00:07:07.759> that<00:07:08.000> rapidly<00:07:08.840> uh<00:07:08.919> supporting<00:07:09.360> the 00:07:09.510 --> 00:07:09.520 align:start position:0% they do that rapidly uh supporting the 00:07:09.520 --> 00:07:12.230 align:start position:0% they do that rapidly uh supporting the public<00:07:09.800> network<00:07:10.280> going<00:07:10.599> back<00:07:10.759> and<00:07:11.120> forth<00:07:12.120> uh 00:07:12.230 --> 00:07:12.240 align:start position:0% public network going back and forth uh 00:07:12.240 --> 00:07:14.469 align:start position:0% public network going back and forth uh and<00:07:12.720> eventually<00:07:13.400> you<00:07:13.520> know<00:07:13.840> we're<00:07:14.080> creating 00:07:14.469 --> 00:07:14.479 align:start position:0% and eventually you know we're creating 00:07:14.479 --> 00:07:16.629 align:start position:0% and eventually you know we're creating that<00:07:14.680> platform<00:07:15.160> to<00:07:15.560> evolve<00:07:16.240> as<00:07:16.400> this 00:07:16.629 --> 00:07:16.639 align:start position:0% that platform to evolve as this 00:07:16.639 --> 00:07:19.390 align:start position:0% that platform to evolve as this technology<00:07:17.560> evolves<00:07:18.560> uh<00:07:18.680> to<00:07:18.800> be<00:07:18.919> able<00:07:19.080> to<00:07:19.240> make 00:07:19.390 --> 00:07:19.400 align:start position:0% technology evolves uh to be able to make 00:07:19.400 --> 00:07:21.670 align:start position:0% technology evolves uh to be able to make sure<00:07:19.800> that<00:07:20.000> the<00:07:20.160> services<00:07:20.680> that<00:07:20.800> you<00:07:20.960> need<00:07:21.360> are 00:07:21.670 --> 00:07:21.680 align:start position:0% sure that the services that you need are 00:07:21.680 --> 00:07:24.070 align:start position:0% sure that the services that you need are there<00:07:22.639> so<00:07:22.840> the<00:07:22.960> biggest<00:07:23.240> hurdle<00:07:23.720> I<00:07:23.879> always 00:07:24.070 --> 00:07:24.080 align:start position:0% there so the biggest hurdle I always 00:07:24.080 --> 00:07:26.309 align:start position:0% there so the biggest hurdle I always hear<00:07:24.319> from<00:07:24.520> customers<00:07:24.960> is<00:07:25.280> getting<00:07:25.720> started 00:07:26.309 --> 00:07:26.319 align:start position:0% hear from customers is getting started 00:07:26.319 --> 00:07:29.230 align:start position:0% hear from customers is getting started and<00:07:26.440> I<00:07:26.599> remember<00:07:27.120> July<00:07:27.479> 31st<00:07:28.160> when<00:07:28.720> Frontier 00:07:29.230 --> 00:07:29.240 align:start position:0% and I remember July 31st when Frontier 00:07:29.240 --> 00:07:31.070 align:start position:0% and I remember July 31st when Frontier came<00:07:29.599> out<00:07:29.759> I<00:07:29.879> spent<00:07:30.160> the<00:07:30.280> better<00:07:30.520> part<00:07:30.680> of<00:07:30.840> two 00:07:31.070 --> 00:07:31.080 align:start position:0% came out I spent the better part of two 00:07:31.080 --> 00:07:33.070 align:start position:0% came out I spent the better part of two days<00:07:31.599> sitting<00:07:31.919> in<00:07:32.080> my<00:07:32.280> office<00:07:32.560> trying<00:07:32.800> to<00:07:32.960> get 00:07:33.070 --> 00:07:33.080 align:start position:0% days sitting in my office trying to get 00:07:33.080 --> 00:07:35.550 align:start position:0% days sitting in my office trying to get the<00:07:33.199> damn<00:07:33.479> thing<00:07:33.639> up<00:07:33.759> and<00:07:34.199> running<00:07:35.199> uh<00:07:35.319> and<00:07:35.440> I 00:07:35.550 --> 00:07:35.560 align:start position:0% the damn thing up and running uh and I 00:07:35.560 --> 00:07:36.990 align:start position:0% the damn thing up and running uh and I unfortunately<00:07:36.039> I<00:07:36.080> was<00:07:36.199> using<00:07:36.440> Windows<00:07:36.879> which 00:07:36.990 --> 00:07:37.000 align:start position:0% unfortunately I was using Windows which 00:07:37.000 --> 00:07:39.909 align:start position:0% unfortunately I was using Windows which is<00:07:37.160> even<00:07:37.520> worse<00:07:38.520> once<00:07:38.720> I<00:07:38.840> switched<00:07:39.160> to<00:07:39.319> auntu<00:07:39.840> I 00:07:39.909 --> 00:07:39.919 align:start position:0% is even worse once I switched to auntu I 00:07:39.919 --> 00:07:43.270 align:start position:0% is even worse once I switched to auntu I was<00:07:40.400> a<00:07:40.479> little<00:07:40.639> bit<00:07:40.759> more<00:07:41.240> successful<00:07:42.240> uh<00:07:42.440> but 00:07:43.270 --> 00:07:43.280 align:start position:0% was a little bit more successful uh but 00:07:43.280 --> 00:07:48.909 align:start position:0% was a little bit more successful uh but uh<00:07:44.120> we'll<00:07:44.360> try<00:07:44.520> to<00:07:44.639> fix<00:07:44.960> that<00:07:45.159> by<00:07:45.280> the<00:07:45.360> way<00:07:46.039> U 00:07:48.909 --> 00:07:48.919 align:start position:0% uh we'll try to fix that by the way U 00:07:48.919 --> 00:07:52.510 align:start position:0% uh we'll try to fix that by the way U uh<00:07:49.919> um<00:07:50.319> but<00:07:50.639> anyway<00:07:51.639> uh<00:07:51.879> so<00:07:52.039> we<00:07:52.120> want<00:07:52.280> to<00:07:52.400> make 00:07:52.510 --> 00:07:52.520 align:start position:0% uh um but anyway uh so we want to make 00:07:52.520 --> 00:07:55.189 align:start position:0% uh um but anyway uh so we want to make it<00:07:52.720> very<00:07:52.960> easy<00:07:53.280> so<00:07:53.639> oneclick<00:07:54.360> deployment<00:07:55.000> now 00:07:55.189 --> 00:07:55.199 align:start position:0% it very easy so oneclick deployment now 00:07:55.199 --> 00:07:58.270 align:start position:0% it very easy so oneclick deployment now what<00:07:55.319> does<00:07:55.520> that<00:07:56.120> mean<00:07:57.120> so<00:07:57.280> in<00:07:57.479> Azure<00:07:58.039> if<00:07:58.120> you 00:07:58.270 --> 00:07:58.280 align:start position:0% what does that mean so in Azure if you 00:07:58.280 --> 00:07:59.749 align:start position:0% what does that mean so in Azure if you have<00:07:58.440> not<00:07:58.599> seen<00:07:58.879> Azure<00:07:59.199> I'm<00:07:59.240> going<00:07:59.319> to<00:07:59.560> show<00:07:59.680> it 00:07:59.749 --> 00:07:59.759 align:start position:0% have not seen Azure I'm going to show it 00:07:59.759 --> 00:08:02.029 align:start position:0% have not seen Azure I'm going to show it to<00:07:59.840> you<00:07:59.960> in<00:08:00.039> a<00:08:00.159> moment<00:08:00.400> so<00:08:00.560> the<00:08:00.680> azer<00:08:01.280> has<00:08:01.879> a 00:08:02.029 --> 00:08:02.039 align:start position:0% to you in a moment so the azer has a 00:08:02.039 --> 00:08:04.670 align:start position:0% to you in a moment so the azer has a portal<00:08:02.800> that<00:08:03.000> our<00:08:03.240> developers<00:08:03.720> and<00:08:03.919> it<00:08:04.280> Pros 00:08:04.670 --> 00:08:04.680 align:start position:0% portal that our developers and it Pros 00:08:04.680 --> 00:08:06.990 align:start position:0% portal that our developers and it Pros go<00:08:04.879> to<00:08:05.199> to<00:08:05.479> create<00:08:05.800> and<00:08:06.000> manage<00:08:06.440> resources 00:08:06.990 --> 00:08:07.000 align:start position:0% go to to create and manage resources 00:08:07.000 --> 00:08:09.550 align:start position:0% go to to create and manage resources that<00:08:07.120> are<00:08:07.240> going<00:08:07.319> to<00:08:07.400> be<00:08:07.560> used<00:08:07.800> in<00:08:07.919> the<00:08:08.560> cloud 00:08:09.550 --> 00:08:09.560 align:start position:0% that are going to be used in the cloud 00:08:09.560 --> 00:08:11.990 align:start position:0% that are going to be used in the cloud so<00:08:09.720> we<00:08:09.840> are<00:08:10.039> going<00:08:10.159> to<00:08:10.280> be<00:08:10.560> introducing<00:08:11.560> um 00:08:11.990 --> 00:08:12.000 align:start position:0% so we are going to be introducing um 00:08:12.000 --> 00:08:14.110 align:start position:0% so we are going to be introducing um this<00:08:12.080> is<00:08:12.199> what<00:08:12.360> I<00:08:12.479> call<00:08:12.680> a<00:08:12.919> soft<00:08:13.400> launch 00:08:14.110 --> 00:08:14.120 align:start position:0% this is what I call a soft launch 00:08:14.120 --> 00:08:16.149 align:start position:0% this is what I call a soft launch because<00:08:14.280> this<00:08:14.400> is<00:08:14.520> a<00:08:14.680> developer<00:08:15.120> audience<00:08:16.000> you 00:08:16.149 --> 00:08:16.159 align:start position:0% because this is a developer audience you 00:08:16.159 --> 00:08:17.710 align:start position:0% because this is a developer audience you guys<00:08:16.319> will<00:08:16.520> forgive<00:08:16.840> me<00:08:17.000> if<00:08:17.120> I<00:08:17.240> show<00:08:17.479> you 00:08:17.710 --> 00:08:17.720 align:start position:0% guys will forgive me if I show you 00:08:17.720 --> 00:08:20.149 align:start position:0% guys will forgive me if I show you GitHub<00:08:18.319> and<00:08:18.520> things<00:08:18.800> like<00:08:19.039> that<00:08:19.319> if<00:08:19.440> I<00:08:19.879> did<00:08:20.039> a 00:08:20.149 --> 00:08:20.159 align:start position:0% GitHub and things like that if I did a 00:08:20.159 --> 00:08:21.950 align:start position:0% GitHub and things like that if I did a hard<00:08:20.400> launch<00:08:20.720> it<00:08:20.840> would<00:08:21.000> be<00:08:21.120> all<00:08:21.400> polished<00:08:21.840> and 00:08:21.950 --> 00:08:21.960 align:start position:0% hard launch it would be all polished and 00:08:21.960 --> 00:08:24.430 align:start position:0% hard launch it would be all polished and marketing<00:08:22.479> and<00:08:23.000> we<00:08:23.159> wouldn't<00:08:23.479> show<00:08:23.720> you<00:08:23.960> any 00:08:24.430 --> 00:08:24.440 align:start position:0% marketing and we wouldn't show you any 00:08:24.440 --> 00:08:27.149 align:start position:0% marketing and we wouldn't show you any uh<00:08:24.599> I<00:08:24.680> would<00:08:24.919> not<00:08:25.520> definitely<00:08:25.960> show<00:08:26.199> you<00:08:26.599> uh<00:08:27.000> an 00:08:27.149 --> 00:08:27.159 align:start position:0% uh I would not definitely show you uh an 00:08:27.159 --> 00:08:29.990 align:start position:0% uh I would not definitely show you uh an SSH<00:08:28.000> shell<00:08:29.000> uh<00:08:29.120> or<00:08:29.240> anything<00:08:29.520> anything<00:08:29.759> like 00:08:29.990 --> 00:08:30.000 align:start position:0% SSH shell uh or anything anything like 00:08:30.000 --> 00:08:31.950 align:start position:0% SSH shell uh or anything anything like that<00:08:30.560> um<00:08:30.720> but<00:08:30.960> here<00:08:31.360> we're<00:08:31.479> going<00:08:31.599> to<00:08:31.680> show 00:08:31.950 --> 00:08:31.960 align:start position:0% that um but here we're going to show 00:08:31.960 --> 00:08:33.190 align:start position:0% that um but here we're going to show what<00:08:32.039> the<00:08:32.200> vision<00:08:32.519> is<00:08:32.680> and<00:08:32.760> then<00:08:32.880> I'm<00:08:33.039> actually 00:08:33.190 --> 00:08:33.200 align:start position:0% what the vision is and then I'm actually 00:08:33.200 --> 00:08:34.389 align:start position:0% what the vision is and then I'm actually show<00:08:33.360> you<00:08:33.440> what<00:08:33.519> it<00:08:33.599> looks<00:08:33.839> like<00:08:34.039> at<00:08:34.200> this 00:08:34.389 --> 00:08:34.399 align:start position:0% show you what it looks like at this 00:08:34.399 --> 00:08:37.110 align:start position:0% show you what it looks like at this moment<00:08:35.320> but<00:08:35.519> this<00:08:35.719> blockchain<00:08:36.399> category<00:08:36.959> will 00:08:37.110 --> 00:08:37.120 align:start position:0% moment but this blockchain category will 00:08:37.120 --> 00:08:38.509 align:start position:0% moment but this blockchain category will be<00:08:37.279> up<00:08:37.479> here<00:08:37.640> now<00:08:37.760> you'll<00:08:37.919> notice<00:08:38.200> we<00:08:38.360> have 00:08:38.509 --> 00:08:38.519 align:start position:0% be up here now you'll notice we have 00:08:38.519 --> 00:08:41.230 align:start position:0% be up here now you'll notice we have some<00:08:39.120> pre-populated<00:08:40.120> uh<00:08:40.279> items<00:08:40.680> up<00:08:40.880> here<00:08:41.159> and 00:08:41.230 --> 00:08:41.240 align:start position:0% some pre-populated uh items up here and 00:08:41.240 --> 00:08:42.630 align:start position:0% some pre-populated uh items up here and we're<00:08:41.399> talking<00:08:41.680> about<00:08:41.839> the<00:08:41.959> blockchain<00:08:42.399> as<00:08:42.519> a 00:08:42.630 --> 00:08:42.640 align:start position:0% we're talking about the blockchain as a 00:08:42.640 --> 00:08:44.029 align:start position:0% we're talking about the blockchain as a service<00:08:42.959> particularly<00:08:43.360> the<00:08:43.440> ethereum 00:08:44.029 --> 00:08:44.039 align:start position:0% service particularly the ethereum 00:08:44.039 --> 00:08:45.870 align:start position:0% service particularly the ethereum blockchain<00:08:44.519> as<00:08:44.640> a<00:08:44.760> service<00:08:45.040> or 00:08:45.870 --> 00:08:45.880 align:start position:0% blockchain as a service or 00:08:45.880 --> 00:08:48.990 align:start position:0% blockchain as a service or Fass<00:08:46.880> um<00:08:47.160> provided<00:08:47.560> by<00:08:47.800> consensus<00:08:48.720> so 00:08:48.990 --> 00:08:49.000 align:start position:0% Fass um provided by consensus so 00:08:49.000 --> 00:08:53.230 align:start position:0% Fass um provided by consensus so consensus<00:08:49.600> is<00:08:49.800> launching<00:08:50.440> today<00:08:51.440> uh<00:08:52.080> two<00:08:53.080> uh 00:08:53.230 --> 00:08:53.240 align:start position:0% consensus is launching today uh two uh 00:08:53.240 --> 00:08:56.630 align:start position:0% consensus is launching today uh two uh basic<00:08:53.800> packages<00:08:54.640> uh<00:08:54.760> in<00:08:54.959> this<00:08:55.560> Marketplace<00:08:56.560> uh 00:08:56.630 --> 00:08:56.640 align:start position:0% basic packages uh in this Marketplace uh 00:08:56.640 --> 00:08:59.430 align:start position:0% basic packages uh in this Marketplace uh the<00:08:56.760> marketplace<00:08:57.240> will<00:08:57.480> consist<00:08:57.839> of<00:08:58.040> a<00:08:58.519> uh<00:08:59.160> PR 00:08:59.430 --> 00:08:59.440 align:start position:0% the marketplace will consist of a uh PR 00:08:59.440 --> 00:09:01.750 align:start position:0% the marketplace will consist of a uh PR private<00:08:59.839> loop<00:09:00.200> back<00:09:00.600> if<00:09:00.720> you<00:09:00.839> will<00:09:01.200> private 00:09:01.750 --> 00:09:01.760 align:start position:0% private loop back if you will private 00:09:01.760 --> 00:09:03.430 align:start position:0% private loop back if you will private blockchain<00:09:02.279> environment<00:09:02.760> based<00:09:03.000> off<00:09:03.160> of<00:09:03.279> the 00:09:03.430 --> 00:09:03.440 align:start position:0% blockchain environment based off of the 00:09:03.440 --> 00:09:04.190 align:start position:0% blockchain environment based off of the go 00:09:04.190 --> 00:09:04.200 align:start position:0% go 00:09:04.200 --> 00:09:06.269 align:start position:0% go implementation<00:09:05.200> with<00:09:05.360> one<00:09:05.640> click<00:09:05.959> you<00:09:06.040> will 00:09:06.269 --> 00:09:06.279 align:start position:0% implementation with one click you will 00:09:06.279 --> 00:09:09.550 align:start position:0% implementation with one click you will install<00:09:06.640> a<00:09:06.839> private<00:09:07.120> Network<00:09:07.640> that<00:09:07.800> has<00:09:08.079> a<00:09:08.560> pre 00:09:09.550 --> 00:09:09.560 align:start position:0% install a private Network that has a pre 00:09:09.560 --> 00:09:12.430 align:start position:0% install a private Network that has a pre uh<00:09:09.760> fueled<00:09:10.760> ether<00:09:11.240> account<00:09:11.600> so<00:09:11.800> you<00:09:11.920> can<00:09:12.240> go 00:09:12.430 --> 00:09:12.440 align:start position:0% uh fueled ether account so you can go 00:09:12.440 --> 00:09:14.389 align:start position:0% uh fueled ether account so you can go ahead<00:09:12.920> and<00:09:13.079> Our<00:09:13.360> intention<00:09:13.800> is<00:09:13.959> to<00:09:14.160> have 00:09:14.389 --> 00:09:14.399 align:start position:0% ahead and Our intention is to have 00:09:14.399 --> 00:09:16.949 align:start position:0% ahead and Our intention is to have someone<00:09:14.839> a<00:09:15.079> newbie<00:09:16.040> and<00:09:16.200> these<00:09:16.399> Enterprise 00:09:16.949 --> 00:09:16.959 align:start position:0% someone a newbie and these Enterprise 00:09:16.959 --> 00:09:19.110 align:start position:0% someone a newbie and these Enterprise customers<00:09:17.640> to<00:09:17.880> with<00:09:18.040> one<00:09:18.320> click<00:09:18.600> be<00:09:18.760> able<00:09:18.920> to 00:09:19.110 --> 00:09:19.120 align:start position:0% customers to with one click be able to 00:09:19.120 --> 00:09:21.190 align:start position:0% customers to with one click be able to deploy<00:09:19.720> and<00:09:19.880> get<00:09:20.040> up<00:09:20.480> uh<00:09:20.600> and<00:09:20.720> stand<00:09:20.959> up<00:09:21.079> an 00:09:21.190 --> 00:09:21.200 align:start position:0% deploy and get up uh and stand up an 00:09:21.200 --> 00:09:23.750 align:start position:0% deploy and get up uh and stand up an ethereum<00:09:21.880> environment<00:09:22.880> follow<00:09:23.240> a<00:09:23.440> simple 00:09:23.750 --> 00:09:23.760 align:start position:0% ethereum environment follow a simple 00:09:23.760 --> 00:09:25.350 align:start position:0% ethereum environment follow a simple script<00:09:24.120> and<00:09:24.279> write<00:09:24.519> their<00:09:24.680> first<00:09:24.959> smart 00:09:25.350 --> 00:09:25.360 align:start position:0% script and write their first smart 00:09:25.360 --> 00:09:27.910 align:start position:0% script and write their first smart contract<00:09:25.880> application<00:09:26.560> within<00:09:26.880> 20 00:09:27.910 --> 00:09:27.920 align:start position:0% contract application within 20 00:09:27.920 --> 00:09:30.670 align:start position:0% contract application within 20 minutes<00:09:28.920> if<00:09:29.040> you<00:09:29.440> told<00:09:29.640> me<00:09:29.760> that<00:09:29.920> on<00:09:30.040> the<00:09:30.160> 31st 00:09:30.670 --> 00:09:30.680 align:start position:0% minutes if you told me that on the 31st 00:09:30.680 --> 00:09:33.190 align:start position:0% minutes if you told me that on the 31st i'<00:09:30.959> probably<00:09:31.160> come<00:09:31.360> to<00:09:31.839> tears<00:09:32.839> because<00:09:32.959> of<00:09:33.079> the 00:09:33.190 --> 00:09:33.200 align:start position:0% i' probably come to tears because of the 00:09:33.200 --> 00:09:35.990 align:start position:0% i' probably come to tears because of the amount<00:09:33.399> of<00:09:33.839> time<00:09:34.079> I<00:09:34.240> spent<00:09:34.640> on<00:09:35.279> learning<00:09:35.680> how 00:09:35.990 --> 00:09:36.000 align:start position:0% amount of time I spent on learning how 00:09:36.000 --> 00:09:39.310 align:start position:0% amount of time I spent on learning how not<00:09:36.600> to<00:09:36.800> do<00:09:37.040> it<00:09:38.040> uh<00:09:38.160> so<00:09:38.320> we<00:09:38.480> want<00:09:38.640> to<00:09:38.839> make<00:09:39.040> it 00:09:39.310 --> 00:09:39.320 align:start position:0% not to do it uh so we want to make it 00:09:39.320 --> 00:09:42.150 align:start position:0% not to do it uh so we want to make it much<00:09:39.760> easier<00:09:40.760> now<00:09:41.040> we<00:09:41.240> en<00:09:41.480> we<00:09:41.600> envision<00:09:42.000> our 00:09:42.150 --> 00:09:42.160 align:start position:0% much easier now we en we envision our 00:09:42.160 --> 00:09:43.949 align:start position:0% much easier now we en we envision our customers<00:09:42.640> picking<00:09:43.000> from<00:09:43.320> this<00:09:43.480> menu<00:09:43.800> and 00:09:43.949 --> 00:09:43.959 align:start position:0% customers picking from this menu and 00:09:43.959 --> 00:09:45.790 align:start position:0% customers picking from this menu and this<00:09:44.120> menu<00:09:44.480> when<00:09:44.640> it<00:09:44.760> says<00:09:45.000> blockchains<00:09:45.640> we 00:09:45.790 --> 00:09:45.800 align:start position:0% this menu when it says blockchains we 00:09:45.800 --> 00:09:48.590 align:start position:0% this menu when it says blockchains we kept<00:09:46.000> it<00:09:46.880> unique<00:09:47.240> because<00:09:47.399> we<00:09:47.519> want<00:09:48.000> services 00:09:48.590 --> 00:09:48.600 align:start position:0% kept it unique because we want services 00:09:48.600 --> 00:09:50.350 align:start position:0% kept it unique because we want services that<00:09:49.200> um<00:09:49.399> apply<00:09:49.839> even<00:09:50.000> if<00:09:50.079> you're<00:09:50.200> not 00:09:50.350 --> 00:09:50.360 align:start position:0% that um apply even if you're not 00:09:50.360 --> 00:09:52.190 align:start position:0% that um apply even if you're not providing<00:09:50.720> a<00:09:50.800> full<00:09:51.079> blockchain<00:09:51.680> stack<00:09:52.079> if 00:09:52.190 --> 00:09:52.200 align:start position:0% providing a full blockchain stack if 00:09:52.200 --> 00:09:54.030 align:start position:0% providing a full blockchain stack if you're<00:09:52.320> not<00:09:52.440> doing<00:09:52.720> this<00:09:53.120> the<00:09:53.360> C++ 00:09:54.030 --> 00:09:54.040 align:start position:0% you're not doing this the C++ 00:09:54.040 --> 00:09:55.710 align:start position:0% you're not doing this the C++ implementation<00:09:54.640> or<00:09:54.760> the<00:09:54.920> go<00:09:55.160> implementation 00:09:55.710 --> 00:09:55.720 align:start position:0% implementation or the go implementation 00:09:55.720 --> 00:09:57.949 align:start position:0% implementation or the go implementation or<00:09:55.880> the<00:09:56.000> Java<00:09:56.440> implementation<00:09:57.440> but<00:09:57.560> you<00:09:57.760> have 00:09:57.949 --> 00:09:57.959 align:start position:0% or the Java implementation but you have 00:09:57.959 --> 00:10:01.470 align:start position:0% or the Java implementation but you have a<00:09:58.200> service<00:09:59.440> that<00:09:59.600> you<00:09:59.800> have<00:10:00.079> written<00:10:01.079> that<00:10:01.240> is 00:10:01.470 --> 00:10:01.480 align:start position:0% a service that you have written that is 00:10:01.480 --> 00:10:03.269 align:start position:0% a service that you have written that is specifically<00:10:02.160> designed<00:10:02.640> to<00:10:02.800> work<00:10:03.040> with 00:10:03.269 --> 00:10:03.279 align:start position:0% specifically designed to work with 00:10:03.279 --> 00:10:04.470 align:start position:0% specifically designed to work with ethereum 00:10:04.470 --> 00:10:04.480 align:start position:0% ethereum 00:10:04.480 --> 00:10:07.430 align:start position:0% ethereum networks<00:10:05.480> you<00:10:05.760> should<00:10:06.120> publish<00:10:06.440> it<00:10:06.680> here<00:10:07.360> to 00:10:07.430 --> 00:10:07.440 align:start position:0% networks you should publish it here to 00:10:07.440 --> 00:10:08.470 align:start position:0% networks you should publish it here to make<00:10:07.600> it 00:10:08.470 --> 00:10:08.480 align:start position:0% make it 00:10:08.480 --> 00:10:10.630 align:start position:0% make it discoverable<00:10:09.480> um<00:10:09.680> so<00:10:09.920> we're<00:10:10.120> we're<00:10:10.279> creating 00:10:10.630 --> 00:10:10.640 align:start position:0% discoverable um so we're we're creating 00:10:10.640 --> 00:10:12.509 align:start position:0% discoverable um so we're we're creating this<00:10:10.880> category<00:10:11.360> and<00:10:11.480> you<00:10:11.560> can<00:10:11.680> see<00:10:11.920> you<00:10:12.040> could 00:10:12.509 --> 00:10:12.519 align:start position:0% this category and you can see you could 00:10:12.519 --> 00:10:13.710 align:start position:0% this category and you can see you could go<00:10:12.680> through<00:10:12.880> any<00:10:13.079> one<00:10:13.200> of<00:10:13.360> these<00:10:13.519> and<00:10:13.640> I'm 00:10:13.710 --> 00:10:13.720 align:start position:0% go through any one of these and I'm 00:10:13.720 --> 00:10:15.069 align:start position:0% go through any one of these and I'm going<00:10:13.839> to<00:10:13.959> walk<00:10:14.160> you<00:10:14.320> through<00:10:14.600> what<00:10:14.680> it<00:10:14.839> looks 00:10:15.069 --> 00:10:15.079 align:start position:0% going to walk you through what it looks 00:10:15.079 --> 00:10:17.350 align:start position:0% going to walk you through what it looks like<00:10:15.959> but<00:10:16.120> if<00:10:16.240> you<00:10:16.320> wanted<00:10:16.560> to<00:10:16.720> have<00:10:16.839> a<00:10:17.000> private 00:10:17.350 --> 00:10:17.360 align:start position:0% like but if you wanted to have a private 00:10:17.360 --> 00:10:20.110 align:start position:0% like but if you wanted to have a private blockchain<00:10:17.880> for<00:10:18.040> instance<00:10:18.519> had<00:10:18.720> six<00:10:19.120> nodes 00:10:20.110 --> 00:10:20.120 align:start position:0% blockchain for instance had six nodes 00:10:20.120 --> 00:10:21.750 align:start position:0% blockchain for instance had six nodes one<00:10:20.320> node<00:10:20.600> in<00:10:20.760> the<00:10:20.839> east<00:10:21.079> coast<00:10:21.279> of<00:10:21.360> the<00:10:21.440> United 00:10:21.750 --> 00:10:21.760 align:start position:0% one node in the east coast of the United 00:10:21.760 --> 00:10:24.269 align:start position:0% one node in the east coast of the United States<00:10:22.160> one<00:10:22.320> in<00:10:22.519> Europe<00:10:22.959> one<00:10:23.120> in<00:10:23.360> China<00:10:23.920> One<00:10:24.079> in 00:10:24.269 --> 00:10:24.279 align:start position:0% States one in Europe one in China One in 00:10:24.279 --> 00:10:26.590 align:start position:0% States one in Europe one in China One in Japan<00:10:24.800> and<00:10:25.079> one<00:10:25.320> in<00:10:25.560> Singapore<00:10:26.079> you<00:10:26.200> could<00:10:26.360> do 00:10:26.590 --> 00:10:26.600 align:start position:0% Japan and one in Singapore you could do 00:10:26.600 --> 00:10:29.110 align:start position:0% Japan and one in Singapore you could do that<00:10:27.560> all<00:10:27.800> within<00:10:28.040> filling<00:10:28.360> out<00:10:28.600> one<00:10:28.800> Wizard 00:10:29.110 --> 00:10:29.120 align:start position:0% that all within filling out one Wizard 00:10:29.120 --> 00:10:30.750 align:start position:0% that all within filling out one Wizard and<00:10:29.399> click<00:10:29.640> deploy<00:10:30.120> and<00:10:30.200> you'd<00:10:30.399> be<00:10:30.519> up<00:10:30.640> and 00:10:30.750 --> 00:10:30.760 align:start position:0% and click deploy and you'd be up and 00:10:30.760 --> 00:10:34.230 align:start position:0% and click deploy and you'd be up and running<00:10:31.079> within<00:10:31.480> minutes<00:10:32.480> that's<00:10:32.800> amazingly 00:10:34.230 --> 00:10:34.240 align:start position:0% running within minutes that's amazingly 00:10:34.240 --> 00:10:36.230 align:start position:0% running within minutes that's amazingly powerful<00:10:35.240> so<00:10:35.480> let<00:10:35.560> me<00:10:35.680> show<00:10:35.839> you<00:10:35.959> what<00:10:36.079> this 00:10:36.230 --> 00:10:36.240 align:start position:0% powerful so let me show you what this 00:10:36.240 --> 00:10:40.110 align:start position:0% powerful so let me show you what this looks<00:10:36.800> like<00:10:37.800> really<00:10:38.240> quickly<00:10:39.240> um<00:10:39.920> the 00:10:40.110 --> 00:10:40.120 align:start position:0% looks like really quickly um the 00:10:40.120 --> 00:10:42.710 align:start position:0% looks like really quickly um the marketplace<00:10:40.920> real<00:10:41.480> uh<00:10:41.680> fast<00:10:42.120> if<00:10:42.240> I<00:10:42.360> can<00:10:42.519> come 00:10:42.710 --> 00:10:42.720 align:start position:0% marketplace real uh fast if I can come 00:10:42.720 --> 00:10:47.350 align:start position:0% marketplace real uh fast if I can come up<00:10:42.880> and<00:10:43.480> let<00:10:43.920> me<00:10:44.920> not<00:10:45.399> have<00:10:45.560> it<00:10:46.360> extend<00:10:46.720> to<00:10:46.839> my 00:10:47.350 --> 00:10:47.360 align:start position:0% up and let me not have it extend to my 00:10:47.360 --> 00:10:49.670 align:start position:0% up and let me not have it extend to my screen<00:10:48.360> so<00:10:48.560> this<00:10:48.680> is<00:10:48.800> what<00:10:48.920> the<00:10:49.000> Azure<00:10:49.399> portal 00:10:49.670 --> 00:10:49.680 align:start position:0% screen so this is what the Azure portal 00:10:49.680 --> 00:10:52.190 align:start position:0% screen so this is what the Azure portal looks<00:10:49.880> like<00:10:50.040> I'm<00:10:50.160> using<00:10:50.440> the<00:10:50.639> Batman<00:10:51.120> theme<00:10:52.000> uh 00:10:52.190 --> 00:10:52.200 align:start position:0% looks like I'm using the Batman theme uh 00:10:52.200 --> 00:10:53.870 align:start position:0% looks like I'm using the Batman theme uh it<00:10:52.320> does<00:10:52.560> come<00:10:52.680> in 00:10:53.870 --> 00:10:53.880 align:start position:0% it does come in 00:10:53.880 --> 00:10:56.030 align:start position:0% it does come in black<00:10:54.880> um<00:10:55.000> so<00:10:55.160> I'm<00:10:55.240> going<00:10:55.360> to<00:10:55.480> come<00:10:55.639> in<00:10:55.839> here 00:10:56.030 --> 00:10:56.040 align:start position:0% black um so I'm going to come in here 00:10:56.040 --> 00:10:57.910 align:start position:0% black um so I'm going to come in here and<00:10:56.160> I'm<00:10:56.240> just<00:10:56.360> going<00:10:56.480> to<00:10:56.600> say<00:10:56.839> new<00:10:57.680> and<00:10:57.839> I'm 00:10:57.910 --> 00:10:57.920 align:start position:0% and I'm just going to say new and I'm 00:10:57.920 --> 00:11:00.030 align:start position:0% and I'm just going to say new and I'm going<00:10:58.040> to<00:10:58.200> create<00:10:58.560> a<00:10:58.760> new 00:11:00.030 --> 00:11:00.040 align:start position:0% going to create a new 00:11:00.040 --> 00:11:02.910 align:start position:0% going to create a new uh<00:11:00.240> let's<00:11:00.519> say<00:11:01.000> auntu<00:11:01.839> just<00:11:02.360> you<00:11:02.480> know<00:11:02.680> because 00:11:02.910 --> 00:11:02.920 align:start position:0% uh let's say auntu just you know because 00:11:02.920 --> 00:11:05.269 align:start position:0% uh let's say auntu just you know because that's<00:11:03.079> what<00:11:03.200> I've<00:11:03.320> been<00:11:03.639> using<00:11:04.200> lately<00:11:05.200> I'm 00:11:05.269 --> 00:11:05.279 align:start position:0% that's what I've been using lately I'm 00:11:05.279 --> 00:11:07.470 align:start position:0% that's what I've been using lately I'm going<00:11:05.399> to<00:11:05.600> create<00:11:06.079> here<00:11:06.760> and<00:11:06.959> show<00:11:07.160> you<00:11:07.320> what 00:11:07.470 --> 00:11:07.480 align:start position:0% going to create here and show you what 00:11:07.480 --> 00:11:09.670 align:start position:0% going to create here and show you what this<00:11:07.639> looks<00:11:07.920> like<00:11:08.680> now<00:11:09.079> I'm<00:11:09.200> not<00:11:09.320> going<00:11:09.440> to<00:11:09.560> go 00:11:09.670 --> 00:11:09.680 align:start position:0% this looks like now I'm not going to go 00:11:09.680 --> 00:11:10.990 align:start position:0% this looks like now I'm not going to go through<00:11:09.880> this<00:11:10.120> process<00:11:10.440> because<00:11:10.639> I'm<00:11:10.720> showing 00:11:10.990 --> 00:11:11.000 align:start position:0% through this process because I'm showing 00:11:11.000 --> 00:11:14.190 align:start position:0% through this process because I'm showing you<00:11:11.160> creating<00:11:11.760> a<00:11:11.959> VM<00:11:12.320> for<00:11:12.800> auntu<00:11:13.800> that's<00:11:13.959> not 00:11:14.190 --> 00:11:14.200 align:start position:0% you creating a VM for auntu that's not 00:11:14.200 --> 00:11:15.710 align:start position:0% you creating a VM for auntu that's not exciting<00:11:14.720> I'm<00:11:14.839> going<00:11:14.920> to<00:11:15.040> let<00:11:15.480> uh<00:11:15.560> I'm<00:11:15.639> going 00:11:15.710 --> 00:11:15.720 align:start position:0% exciting I'm going to let uh I'm going 00:11:15.720 --> 00:11:16.750 align:start position:0% exciting I'm going to let uh I'm going to<00:11:15.839> show<00:11:15.959> you<00:11:16.040> what<00:11:16.160> it's<00:11:16.279> going<00:11:16.360> to<00:11:16.480> look<00:11:16.639> like 00:11:16.750 --> 00:11:16.760 align:start position:0% to show you what it's going to look like 00:11:16.760 --> 00:11:18.550 align:start position:0% to show you what it's going to look like to<00:11:16.959> create<00:11:17.360> uh<00:11:17.480> one<00:11:17.600> of<00:11:17.720> these<00:11:17.920> blockchain 00:11:18.550 --> 00:11:18.560 align:start position:0% to create uh one of these blockchain 00:11:18.560 --> 00:11:20.310 align:start position:0% to create uh one of these blockchain assets<00:11:19.040> but<00:11:19.160> I<00:11:19.279> did<00:11:19.480> want<00:11:19.639> to<00:11:19.800> point<00:11:20.000> out<00:11:20.200> a 00:11:20.310 --> 00:11:20.320 align:start position:0% assets but I did want to point out a 00:11:20.320 --> 00:11:23.509 align:start position:0% assets but I did want to point out a couple<00:11:20.519> of<00:11:20.880> things<00:11:21.880> let<00:11:22.040> me<00:11:22.560> uh<00:11:23.160> pick<00:11:23.360> a 00:11:23.509 --> 00:11:23.519 align:start position:0% couple of things let me uh pick a 00:11:23.519 --> 00:11:25.590 align:start position:0% couple of things let me uh pick a different<00:11:23.839> region<00:11:24.320> and<00:11:24.519> just<00:11:24.680> show<00:11:24.920> you<00:11:25.279> how 00:11:25.590 --> 00:11:25.600 align:start position:0% different region and just show you how 00:11:25.600 --> 00:11:28.550 align:start position:0% different region and just show you how badass<00:11:26.040> a<00:11:26.200> machine<00:11:26.600> I<00:11:26.720> can<00:11:27.120> create<00:11:28.120> let's<00:11:28.320> say 00:11:28.550 --> 00:11:28.560 align:start position:0% badass a machine I can create let's say 00:11:28.560 --> 00:11:30.750 align:start position:0% badass a machine I can create let's say I'm<00:11:29.440> you<00:11:29.600> know<00:11:29.880> really<00:11:30.279> going<00:11:30.399> to<00:11:30.519> be 00:11:30.750 --> 00:11:30.760 align:start position:0% I'm you know really going to be 00:11:30.760 --> 00:11:33.430 align:start position:0% I'm you know really going to be aggressive<00:11:31.200> with<00:11:31.480> this<00:11:32.000> and<00:11:32.279> I<00:11:32.399> want<00:11:32.680> to<00:11:33.000> say 00:11:33.430 --> 00:11:33.440 align:start position:0% aggressive with this and I want to say 00:11:33.440 --> 00:11:35.269 align:start position:0% aggressive with this and I want to say create 00:11:35.269 --> 00:11:35.279 align:start position:0% create 00:11:35.279 --> 00:11:38.269 align:start position:0% create a<00:11:36.279> let's<00:11:36.480> see<00:11:36.680> how<00:11:36.800> much<00:11:36.959> money<00:11:37.279> I<00:11:37.360> want<00:11:37.480> to 00:11:38.269 --> 00:11:38.279 align:start position:0% a let's see how much money I want to 00:11:38.279 --> 00:11:40.990 align:start position:0% a let's see how much money I want to spend<00:11:39.279> there<00:11:39.399> we<00:11:39.600> go<00:11:39.920> this<00:11:40.040> looks<00:11:40.320> good<00:11:40.480> 32 00:11:40.990 --> 00:11:41.000 align:start position:0% spend there we go this looks good 32 00:11:41.000 --> 00:11:44.910 align:start position:0% spend there we go this looks good 32 cores<00:11:41.360> and<00:11:41.560> 448<00:11:42.560> gigs<00:11:43.519> that<00:11:43.639> looks<00:11:43.959> good<00:11:44.120> to 00:11:44.910 --> 00:11:44.920 align:start position:0% cores and 448 gigs that looks good to 00:11:44.920 --> 00:11:47.829 align:start position:0% cores and 448 gigs that looks good to me<00:11:45.920> so<00:11:46.240> you<00:11:46.360> can<00:11:46.560> see<00:11:46.920> I<00:11:47.000> can<00:11:47.200> pick<00:11:47.360> and<00:11:47.519> choose 00:11:47.829 --> 00:11:47.839 align:start position:0% me so you can see I can pick and choose 00:11:47.839 --> 00:11:50.350 align:start position:0% me so you can see I can pick and choose from<00:11:48.000> a<00:11:48.160> menu<00:11:48.800> of<00:11:49.079> these<00:11:49.360> type<00:11:49.560> of<00:11:49.760> resources 00:11:50.350 --> 00:11:50.360 align:start position:0% from a menu of these type of resources 00:11:50.360 --> 00:11:52.550 align:start position:0% from a menu of these type of resources and<00:11:50.880> and<00:11:51.200> uh<00:11:51.399> go<00:11:51.560> ahead<00:11:51.760> and<00:11:51.959> just<00:11:52.120> type<00:11:52.320> in<00:11:52.440> a 00:11:52.550 --> 00:11:52.560 align:start position:0% and and uh go ahead and just type in a 00:11:52.560 --> 00:11:55.069 align:start position:0% and and uh go ahead and just type in a host 00:11:55.069 --> 00:11:55.079 align:start position:0% 00:11:55.079 --> 00:11:59.350 align:start position:0% name<00:11:56.079> that's<00:11:56.200> not<00:11:56.360> going<00:11:56.440> to<00:11:56.639> work 00:11:59.350 --> 00:11:59.360 align:start position:0% name that's not going to work 00:11:59.360 --> 00:12:01.230 align:start position:0% name that's not going to work that's<00:11:59.519> not<00:11:59.639> going<00:11:59.760> to<00:11:59.839> work<00:12:00.079> either<00:12:00.920> anyway 00:12:01.230 --> 00:12:01.240 align:start position:0% that's not going to work either anyway 00:12:01.240 --> 00:12:04.389 align:start position:0% that's not going to work either anyway there's<00:12:01.399> a<00:12:01.680> I<00:12:01.839> can't<00:12:02.040> use<00:12:02.639> uh<00:12:03.639> spaces<00:12:04.240> there's 00:12:04.389 --> 00:12:04.399 align:start position:0% there's a I can't use uh spaces there's 00:12:04.399 --> 00:12:06.190 align:start position:0% there's a I can't use uh spaces there's a<00:12:04.639> space<00:12:04.880> in 00:12:06.190 --> 00:12:06.200 align:start position:0% a space in 00:12:06.200 --> 00:12:08.389 align:start position:0% a space in there<00:12:07.200> but<00:12:07.320> anyway<00:12:07.560> I<00:12:07.639> can<00:12:07.839> configure<00:12:08.279> this 00:12:08.389 --> 00:12:08.399 align:start position:0% there but anyway I can configure this 00:12:08.399 --> 00:12:09.990 align:start position:0% there but anyway I can configure this and<00:12:08.600> say<00:12:08.880> go<00:12:09.160> and<00:12:09.279> then<00:12:09.399> we'll<00:12:09.560> go<00:12:09.680> out<00:12:09.839> and 00:12:09.990 --> 00:12:10.000 align:start position:0% and say go and then we'll go out and 00:12:10.000 --> 00:12:12.310 align:start position:0% and say go and then we'll go out and provision<00:12:10.440> this<00:12:10.560> and<00:12:10.800> create<00:12:11.079> it<00:12:11.880> now<00:12:12.000> for<00:12:12.160> the 00:12:12.310 --> 00:12:12.320 align:start position:0% provision this and create it now for the 00:12:12.320 --> 00:12:13.870 align:start position:0% provision this and create it now for the quick<00:12:12.560> starts<00:12:13.040> you're<00:12:13.160> going<00:12:13.279> to<00:12:13.399> see<00:12:13.639> when<00:12:13.760> I 00:12:13.870 --> 00:12:13.880 align:start position:0% quick starts you're going to see when I 00:12:13.880 --> 00:12:17.870 align:start position:0% quick starts you're going to see when I told<00:12:14.120> you<00:12:14.360> that<00:12:14.800> um<00:12:15.440> for<00:12:15.680> the<00:12:16.320> uh<00:12:17.320> ethereum 00:12:17.870 --> 00:12:17.880 align:start position:0% told you that um for the uh ethereum 00:12:17.880 --> 00:12:19.829 align:start position:0% told you that um for the uh ethereum blockchains<00:12:18.519> we<00:12:18.839> have<00:12:19.079> not<00:12:19.240> stood<00:12:19.600> up<00:12:19.720> the 00:12:19.829 --> 00:12:19.839 align:start position:0% blockchains we have not stood up the 00:12:19.839 --> 00:12:21.590 align:start position:0% blockchains we have not stood up the blockchain<00:12:20.360> category<00:12:20.839> yet<00:12:21.079> that<00:12:21.160> will<00:12:21.320> happen 00:12:21.590 --> 00:12:21.600 align:start position:0% blockchain category yet that will happen 00:12:21.600 --> 00:12:23.710 align:start position:0% blockchain category yet that will happen probably<00:12:21.920> by<00:12:22.040> the<00:12:22.120> end<00:12:22.240> of<00:12:22.360> the<00:12:22.480> month<00:12:23.440> uh<00:12:23.560> but 00:12:23.710 --> 00:12:23.720 align:start position:0% probably by the end of the month uh but 00:12:23.720 --> 00:12:25.310 align:start position:0% probably by the end of the month uh but what<00:12:23.839> you<00:12:23.959> do<00:12:24.160> see<00:12:24.519> this<00:12:24.600> is<00:12:24.760> the<00:12:24.920> Azure 00:12:25.310 --> 00:12:25.320 align:start position:0% what you do see this is the Azure 00:12:25.320 --> 00:12:27.110 align:start position:0% what you do see this is the Azure Marketplace<00:12:25.880> I'm<00:12:26.040> just<00:12:26.160> going<00:12:26.279> to<00:12:26.519> t<00:12:26.760> uh<00:12:26.880> touch 00:12:27.110 --> 00:12:27.120 align:start position:0% Marketplace I'm just going to t uh touch 00:12:27.120 --> 00:12:29.430 align:start position:0% Marketplace I'm just going to t uh touch on<00:12:27.320> this<00:12:27.519> blockchain<00:12:28.040> Strat<00:12:29.000> which<00:12:29.240> are 00:12:29.430 --> 00:12:29.440 align:start position:0% on this blockchain Strat which are 00:12:29.440 --> 00:12:31.870 align:start position:0% on this blockchain Strat which are actually<00:12:29.639> going<00:12:29.720> to<00:12:29.839> show<00:12:30.040> you<00:12:30.560> next<00:12:31.560> and<00:12:31.800> I'm 00:12:31.870 --> 00:12:31.880 align:start position:0% actually going to show you next and I'm 00:12:31.880 --> 00:12:33.629 align:start position:0% actually going to show you next and I'm going<00:12:31.959> to<00:12:32.040> show<00:12:32.160> you<00:12:32.279> the<00:12:32.399> oneclick<00:12:32.880> deploy<00:12:33.480> of 00:12:33.629 --> 00:12:33.639 align:start position:0% going to show you the oneclick deploy of 00:12:33.639 --> 00:12:36.750 align:start position:0% going to show you the oneclick deploy of what<00:12:33.720> it<00:12:33.880> looks<00:12:34.160> like<00:12:34.880> um<00:12:35.320> for<00:12:36.000> deploying 00:12:36.750 --> 00:12:36.760 align:start position:0% what it looks like um for deploying 00:12:36.760 --> 00:12:38.629 align:start position:0% what it looks like um for deploying blockchain<00:12:37.760> uh<00:12:37.880> so<00:12:38.000> I'm<00:12:38.079> going<00:12:38.199> to<00:12:38.320> create 00:12:38.629 --> 00:12:38.639 align:start position:0% blockchain uh so I'm going to create 00:12:38.639 --> 00:12:41.430 align:start position:0% blockchain uh so I'm going to create this<00:12:38.880> block<00:12:39.279> block<00:12:39.600> app<00:12:39.839> Strat<00:12:40.760> image<00:12:41.279> now 00:12:41.430 --> 00:12:41.440 align:start position:0% this block block app Strat image now 00:12:41.440 --> 00:12:43.350 align:start position:0% this block block app Strat image now this<00:12:41.560> is<00:12:42.120> based<00:12:42.399> on<00:12:42.519> a<00:12:42.600> boont<00:12:42.839> tu<00:12:43.000> and<00:12:43.079> it<00:12:43.199> has 00:12:43.350 --> 00:12:43.360 align:start position:0% this is based on a boont tu and it has 00:12:43.360 --> 00:12:45.470 align:start position:0% this is based on a boont tu and it has the<00:12:43.560> full<00:12:44.000> stack<00:12:44.440> here<00:12:44.839> we<00:12:44.959> got<00:12:45.079> a<00:12:45.199> lot<00:12:45.360> of 00:12:45.470 --> 00:12:45.480 align:start position:0% the full stack here we got a lot of 00:12:45.480 --> 00:12:47.790 align:start position:0% the full stack here we got a lot of azure<00:12:45.920> logins<00:12:46.920> so<00:12:47.079> I'm<00:12:47.160> going<00:12:47.240> to<00:12:47.399> log<00:12:47.600> in 00:12:47.790 --> 00:12:47.800 align:start position:0% azure logins so I'm going to log in 00:12:47.800 --> 00:12:51.949 align:start position:0% azure logins so I'm going to log in really<00:12:48.360> quick<00:12:49.360> and<00:12:49.680> it's<00:12:49.839> going<00:12:49.959> to<00:12:50.199> fire<00:12:50.959> up 00:12:51.949 --> 00:12:51.959 align:start position:0% really quick and it's going to fire up 00:12:51.959 --> 00:12:54.030 align:start position:0% really quick and it's going to fire up yeah<00:12:52.199> yeah<00:12:52.480> comeing<00:12:52.760> as 00:12:54.030 --> 00:12:54.040 align:start position:0% yeah yeah comeing as 00:12:54.040 --> 00:12:57.509 align:start position:0% yeah yeah comeing as me<00:12:55.040> and<00:12:55.199> it's<00:12:55.360> going<00:12:55.480> to<00:12:55.600> fire<00:12:55.839> up<00:12:56.160> right<00:12:56.519> into 00:12:57.509 --> 00:12:57.519 align:start position:0% me and it's going to fire up right into 00:12:57.519 --> 00:12:59.949 align:start position:0% me and it's going to fire up right into uh<00:12:57.680> the<00:12:57.959> template<00:12:58.360> for<00:12:58.519> me<00:12:58.680> to<00:12:58.839> fill<00:12:59.360> in<00:12:59.519> my 00:12:59.949 --> 00:12:59.959 align:start position:0% uh the template for me to fill in my 00:12:59.959 --> 00:13:02.870 align:start position:0% uh the template for me to fill in my parameters<00:13:00.959> for<00:13:01.320> my<00:13:01.519> new<00:13:01.760> blockchain<00:13:02.760> uh 00:13:02.870 --> 00:13:02.880 align:start position:0% parameters for my new blockchain uh 00:13:02.880 --> 00:13:05.870 align:start position:0% parameters for my new blockchain uh environment<00:13:03.399> that<00:13:03.480> I<00:13:03.560> want<00:13:03.720> to<00:13:03.839> spin<00:13:04.480> up<00:13:05.480> so<00:13:05.760> as 00:13:05.870 --> 00:13:05.880 align:start position:0% environment that I want to spin up so as 00:13:05.880 --> 00:13:07.629 align:start position:0% environment that I want to spin up so as we<00:13:06.079> come<00:13:06.279> up<00:13:06.519> and<00:13:06.639> this<00:13:06.760> is<00:13:06.959> live<00:13:07.320> I'm<00:13:07.440> not 00:13:07.629 --> 00:13:07.639 align:start position:0% we come up and this is live I'm not 00:13:07.639 --> 00:13:09.509 align:start position:0% we come up and this is live I'm not chewing<00:13:08.160> a<00:13:08.360> video<00:13:08.760> or<00:13:08.920> anything<00:13:09.240> here<00:13:09.399> I'm 00:13:09.509 --> 00:13:09.519 align:start position:0% chewing a video or anything here I'm 00:13:09.519 --> 00:13:14.350 align:start position:0% chewing a video or anything here I'm going<00:13:09.600> to<00:13:09.760> name<00:13:10.120> this<00:13:10.800> you<00:13:11.519> he 00:13:14.350 --> 00:13:14.360 align:start position:0% 00:13:14.360 --> 00:13:19.389 align:start position:0% whoops<00:13:15.360> let<00:13:15.440> me<00:13:15.600> go 00:13:19.389 --> 00:13:19.399 align:start position:0% 00:13:19.399 --> 00:13:21.870 align:start position:0% back<00:13:20.399> so<00:13:20.560> I'm<00:13:20.639> going<00:13:20.760> to<00:13:20.880> type<00:13:21.079> in<00:13:21.279> some<00:13:21.519> stuff 00:13:21.870 --> 00:13:21.880 align:start position:0% back so I'm going to type in some stuff 00:13:21.880 --> 00:13:23.750 align:start position:0% back so I'm going to type in some stuff here<00:13:22.480> I'm<00:13:22.560> going<00:13:22.680> to<00:13:22.800> go<00:13:22.880> on<00:13:22.959> the<00:13:23.160> dev<00:13:23.399> Network 00:13:23.750 --> 00:13:23.760 align:start position:0% here I'm going to go on the dev Network 00:13:23.760 --> 00:13:26.310 align:start position:0% here I'm going to go on the dev Network and<00:13:23.920> put<00:13:24.040> in<00:13:24.160> a<00:13:24.399> password<00:13:25.360> and<00:13:25.480> then<00:13:25.639> say<00:13:26.000> okay 00:13:26.310 --> 00:13:26.320 align:start position:0% and put in a password and then say okay 00:13:26.320 --> 00:13:28.030 align:start position:0% and put in a password and then say okay and<00:13:26.480> it'll<00:13:26.680> spin<00:13:26.920> up<00:13:27.040> and<00:13:27.240> create<00:13:27.519> it<00:13:27.880> now<00:13:27.959> I'm 00:13:28.030 --> 00:13:28.040 align:start position:0% and it'll spin up and create it now I'm 00:13:28.040 --> 00:13:29.269 align:start position:0% and it'll spin up and create it now I'm going<00:13:28.160> let<00:13:28.320> these<00:13:28.480> guys<00:13:28.680> actually<00:13:28.880> do 00:13:29.269 --> 00:13:29.279 align:start position:0% going let these guys actually do 00:13:29.279 --> 00:13:30.829 align:start position:0% going let these guys actually do actually<00:13:29.440> going<00:13:29.519> to<00:13:29.639> do<00:13:29.720> it<00:13:29.959> live<00:13:30.600> let<00:13:30.720> me 00:13:30.829 --> 00:13:30.839 align:start position:0% actually going to do it live let me 00:13:30.839 --> 00:13:33.470 align:start position:0% actually going to do it live let me switch<00:13:31.160> back<00:13:31.279> to<00:13:31.440> my<00:13:31.600> slides<00:13:32.040> really<00:13:32.480> quick 00:13:33.470 --> 00:13:33.480 align:start position:0% switch back to my slides really quick 00:13:33.480 --> 00:13:36.750 align:start position:0% switch back to my slides really quick and<00:13:33.600> give<00:13:33.720> you<00:13:33.839> the<00:13:34.000> big<00:13:34.560> picture 00:13:36.750 --> 00:13:36.760 align:start position:0% and give you the big picture 00:13:36.760 --> 00:13:39.430 align:start position:0% and give you the big picture so<00:13:37.760> let's<00:13:37.959> talk<00:13:38.160> about<00:13:38.519> the<00:13:38.680> the<00:13:38.839> technology<00:13:39.320> I 00:13:39.430 --> 00:13:39.440 align:start position:0% so let's talk about the the technology I 00:13:39.440 --> 00:13:40.949 align:start position:0% so let's talk about the the technology I think<00:13:39.560> it's<00:13:39.680> going<00:13:39.760> to<00:13:40.079> change<00:13:40.480> the<00:13:40.600> way<00:13:40.760> we 00:13:40.949 --> 00:13:40.959 align:start position:0% think it's going to change the way we 00:13:40.959 --> 00:13:42.750 align:start position:0% think it's going to change the way we deliver<00:13:41.360> these<00:13:41.600> types<00:13:41.839> of<00:13:42.000> services<00:13:42.600> and 00:13:42.750 --> 00:13:42.760 align:start position:0% deliver these types of services and 00:13:42.760 --> 00:13:45.790 align:start position:0% deliver these types of services and deliver<00:13:43.120> this<00:13:43.399> value<00:13:44.240> the<00:13:44.399> first<00:13:44.680> is<00:13:45.120> uh<00:13:45.560> is 00:13:45.790 --> 00:13:45.800 align:start position:0% deliver this value the first is uh is 00:13:45.800 --> 00:13:48.829 align:start position:0% deliver this value the first is uh is containers<00:13:46.480> so<00:13:46.680> namely<00:13:47.199> Docker<00:13:48.199> and<00:13:48.399> windows 00:13:48.829 --> 00:13:48.839 align:start position:0% containers so namely Docker and windows 00:13:48.839 --> 00:13:51.509 align:start position:0% containers so namely Docker and windows containers<00:13:49.519> they're<00:13:50.199> basically<00:13:51.199> um 00:13:51.509 --> 00:13:51.519 align:start position:0% containers they're basically um 00:13:51.519 --> 00:13:53.670 align:start position:0% containers they're basically um interchangeable<00:13:52.320> at<00:13:52.480> this<00:13:52.680> point<00:13:53.320> the<00:13:53.480> amount 00:13:53.670 --> 00:13:53.680 align:start position:0% interchangeable at this point the amount 00:13:53.680 --> 00:13:56.269 align:start position:0% interchangeable at this point the amount of<00:13:53.839> work<00:13:54.120> we've<00:13:54.360> done<00:13:54.720> with<00:13:54.920> Docker<00:13:55.560> to<00:13:55.759> make 00:13:56.269 --> 00:13:56.279 align:start position:0% of work we've done with Docker to make 00:13:56.279 --> 00:13:58.110 align:start position:0% of work we've done with Docker to make um<00:13:56.440> container<00:13:56.920> technology<00:13:57.480> ubiquitous 00:13:58.110 --> 00:13:58.120 align:start position:0% um container technology ubiquitous 00:13:58.120 --> 00:14:01.310 align:start position:0% um container technology ubiquitous across<00:13:58.480> Linux<00:13:59.279> and<00:13:59.480> windows<00:14:00.320> distributions 00:14:01.310 --> 00:14:01.320 align:start position:0% across Linux and windows distributions 00:14:01.320 --> 00:14:03.670 align:start position:0% across Linux and windows distributions uh<00:14:01.480> and<00:14:01.680> be<00:14:02.199> uh<00:14:02.360> have<00:14:02.480> a<00:14:02.639> single<00:14:03.040> management 00:14:03.670 --> 00:14:03.680 align:start position:0% uh and be uh have a single management 00:14:03.680 --> 00:14:05.870 align:start position:0% uh and be uh have a single management platform<00:14:04.199> and<00:14:04.360> deployment<00:14:04.959> platform<00:14:05.440> working 00:14:05.870 --> 00:14:05.880 align:start position:0% platform and deployment platform working 00:14:05.880 --> 00:14:08.389 align:start position:0% platform and deployment platform working with<00:14:06.040> the<00:14:06.199> Apache<00:14:07.000> Foundation<00:14:08.000> we<00:14:08.160> have 00:14:08.389 --> 00:14:08.399 align:start position:0% with the Apache Foundation we have 00:14:08.399 --> 00:14:10.189 align:start position:0% with the Apache Foundation we have created<00:14:08.800> an<00:14:08.959> environment<00:14:09.519> where<00:14:09.680> you<00:14:09.800> can<00:14:10.000> mix 00:14:10.189 --> 00:14:10.199 align:start position:0% created an environment where you can mix 00:14:10.199 --> 00:14:12.629 align:start position:0% created an environment where you can mix and<00:14:10.399> match<00:14:10.759> VMS<00:14:11.240> and<00:14:11.480> containers<00:14:12.040> to<00:14:12.199> get<00:14:12.440> the 00:14:12.629 --> 00:14:12.639 align:start position:0% and match VMS and containers to get the 00:14:12.639 --> 00:14:14.629 align:start position:0% and match VMS and containers to get the right<00:14:12.959> environment<00:14:13.480> for<00:14:13.680> you<00:14:13.959> at<00:14:14.079> the<00:14:14.199> drop<00:14:14.519> of 00:14:14.629 --> 00:14:14.639 align:start position:0% right environment for you at the drop of 00:14:14.639 --> 00:14:17.790 align:start position:0% right environment for you at the drop of a<00:14:14.880> hat<00:14:15.880> and<00:14:16.040> be<00:14:16.160> able<00:14:16.360> to<00:14:16.560> change<00:14:17.079> things 00:14:17.790 --> 00:14:17.800 align:start position:0% a hat and be able to change things 00:14:17.800 --> 00:14:18.990 align:start position:0% a hat and be able to change things almost 00:14:18.990 --> 00:14:19.000 align:start position:0% almost 00:14:19.000 --> 00:14:22.430 align:start position:0% almost instantly<00:14:20.000> uh<00:14:20.120> and<00:14:20.320> deploy<00:14:20.839> in<00:14:21.320> scale<00:14:22.320> uh 00:14:22.430 --> 00:14:22.440 align:start position:0% instantly uh and deploy in scale uh 00:14:22.440 --> 00:14:24.189 align:start position:0% instantly uh and deploy in scale uh based<00:14:22.720> on<00:14:22.839> your<00:14:23.079> needs<00:14:23.360> and<00:14:23.560> demand<00:14:24.040> and 00:14:24.189 --> 00:14:24.199 align:start position:0% based on your needs and demand and 00:14:24.199 --> 00:14:26.310 align:start position:0% based on your needs and demand and remember<00:14:24.680> this<00:14:24.800> is<00:14:25.079> azure<00:14:25.680> and<00:14:25.800> if<00:14:25.920> you're<00:14:26.120> not 00:14:26.310 --> 00:14:26.320 align:start position:0% remember this is azure and if you're not 00:14:26.320 --> 00:14:27.829 align:start position:0% remember this is azure and if you're not familiar<00:14:26.680> with<00:14:26.800> Azure<00:14:27.160> Azure<00:14:27.560> is<00:14:27.639> a 00:14:27.829 --> 00:14:27.839 align:start position:0% familiar with Azure Azure is a 00:14:27.839 --> 00:14:30.470 align:start position:0% familiar with Azure Azure is a subscription<00:14:28.480> service<00:14:29.399> you<00:14:29.560> only<00:14:29.959> pay<00:14:30.199> for 00:14:30.470 --> 00:14:30.480 align:start position:0% subscription service you only pay for 00:14:30.480 --> 00:14:32.670 align:start position:0% subscription service you only pay for what<00:14:30.600> you<00:14:30.839> use<00:14:31.680> it's<00:14:31.839> not<00:14:32.040> like<00:14:32.240> getting<00:14:32.440> a 00:14:32.670 --> 00:14:32.680 align:start position:0% what you use it's not like getting a 00:14:32.680 --> 00:14:34.990 align:start position:0% what you use it's not like getting a cable<00:14:33.000> TV<00:14:33.519> package<00:14:33.839> or<00:14:34.040> getting<00:14:34.240> a<00:14:34.360> cell<00:14:34.639> phone 00:14:34.990 --> 00:14:35.000 align:start position:0% cable TV package or getting a cell phone 00:14:35.000 --> 00:14:36.710 align:start position:0% cable TV package or getting a cell phone package<00:14:35.720> you're<00:14:35.920> only<00:14:36.120> going<00:14:36.199> to<00:14:36.360> pay<00:14:36.519> for 00:14:36.710 --> 00:14:36.720 align:start position:0% package you're only going to pay for 00:14:36.720 --> 00:14:39.870 align:start position:0% package you're only going to pay for what<00:14:36.839> you<00:14:37.360> use<00:14:38.360> so<00:14:39.199> when<00:14:39.360> we<00:14:39.480> have<00:14:39.680> these 00:14:39.870 --> 00:14:39.880 align:start position:0% what you use so when we have these 00:14:39.880 --> 00:14:42.749 align:start position:0% what you use so when we have these containers<00:14:40.880> um<00:14:41.279> so<00:14:41.920> um<00:14:42.160> a<00:14:42.320> container<00:14:42.680> if 00:14:42.749 --> 00:14:42.759 align:start position:0% containers um so um a container if 00:14:42.759 --> 00:14:44.550 align:start position:0% containers um so um a container if you're<00:14:42.920> not<00:14:43.040> familiar<00:14:43.399> with<00:14:43.560> Docker<00:14:44.000> it<00:14:44.120> runs 00:14:44.550 --> 00:14:44.560 align:start position:0% you're not familiar with Docker it runs 00:14:44.560 --> 00:14:46.749 align:start position:0% you're not familiar with Docker it runs within<00:14:44.800> a<00:14:44.959> VM<00:14:45.360> or<00:14:45.480> it<00:14:45.560> can<00:14:45.720> run<00:14:46.160> on<00:14:46.480> the 00:14:46.749 --> 00:14:46.759 align:start position:0% within a VM or it can run on the 00:14:46.759 --> 00:14:49.189 align:start position:0% within a VM or it can run on the hypervisor<00:14:47.480> itself<00:14:48.480> we<00:14:48.600> are<00:14:48.720> creating<00:14:49.040> an 00:14:49.189 --> 00:14:49.199 align:start position:0% hypervisor itself we are creating an 00:14:49.199 --> 00:14:50.910 align:start position:0% hypervisor itself we are creating an image<00:14:49.560> repository<00:14:50.279> and<00:14:50.399> these<00:14:50.600> image 00:14:50.910 --> 00:14:50.920 align:start position:0% image repository and these image 00:14:50.920 --> 00:14:52.310 align:start position:0% image repository and these image repositories<00:14:51.560> are<00:14:51.720> going<00:14:51.800> to<00:14:51.959> have 00:14:52.310 --> 00:14:52.320 align:start position:0% repositories are going to have 00:14:52.320 --> 00:14:55.710 align:start position:0% repositories are going to have containers<00:14:53.320> that<00:14:53.519> have<00:14:54.240> prepackaged<00:14:55.240> like 00:14:55.710 --> 00:14:55.720 align:start position:0% containers that have prepackaged like 00:14:55.720 --> 00:14:59.310 align:start position:0% containers that have prepackaged like say<00:14:56.720> um<00:14:57.040> a<00:14:57.279> stack<00:14:57.639> for<00:14:57.920> ethereum<00:14:58.880> uh<00:14:59.199> a 00:14:59.310 --> 00:14:59.320 align:start position:0% say um a stack for ethereum uh a 00:14:59.320 --> 00:15:01.069 align:start position:0% say um a stack for ethereum uh a particular<00:14:59.680> stack<00:14:59.920> and<00:15:00.000> you<00:15:00.079> can<00:15:00.240> have<00:15:00.440> 10<00:15:00.759> 20 00:15:01.069 --> 00:15:01.079 align:start position:0% particular stack and you can have 10 20 00:15:01.079 --> 00:15:02.749 align:start position:0% particular stack and you can have 10 20 30<00:15:01.480> different<00:15:01.839> types<00:15:02.079> of<00:15:02.240> stacks<00:15:02.560> that<00:15:02.680> you 00:15:02.749 --> 00:15:02.759 align:start position:0% 30 different types of stacks that you 00:15:02.759 --> 00:15:05.389 align:start position:0% 30 different types of stacks that you can<00:15:02.880> mix<00:15:03.079> and<00:15:03.279> match<00:15:04.279> select<00:15:04.759> those<00:15:05.120> from<00:15:05.279> the 00:15:05.389 --> 00:15:05.399 align:start position:0% can mix and match select those from the 00:15:05.399 --> 00:15:08.189 align:start position:0% can mix and match select those from the image<00:15:05.759> repository<00:15:06.480> and<00:15:06.639> then<00:15:07.000> spin<00:15:07.279> up<00:15:07.959> on 00:15:08.189 --> 00:15:08.199 align:start position:0% image repository and then spin up on 00:15:08.199 --> 00:15:11.110 align:start position:0% image repository and then spin up on your<00:15:08.959> platform<00:15:09.959> um<00:15:10.279> the<00:15:10.480> the<00:15:10.639> stack<00:15:11.000> that 00:15:11.110 --> 00:15:11.120 align:start position:0% your platform um the the stack that 00:15:11.120 --> 00:15:13.509 align:start position:0% your platform um the the stack that you're<00:15:11.759> that<00:15:11.880> you're<00:15:12.120> wanting<00:15:12.399> to<00:15:12.560> build<00:15:12.839> upon 00:15:13.509 --> 00:15:13.519 align:start position:0% you're that you're wanting to build upon 00:15:13.519 --> 00:15:16.829 align:start position:0% you're that you're wanting to build upon now<00:15:13.680> where<00:15:13.920> this<00:15:14.079> leads<00:15:14.480> us<00:15:14.839> is<00:15:15.440> to<00:15:16.440> this 00:15:16.829 --> 00:15:16.839 align:start position:0% now where this leads us is to this 00:15:16.839 --> 00:15:19.670 align:start position:0% now where this leads us is to this broader<00:15:17.320> vision<00:15:17.759> for<00:15:18.399> blockchains<00:15:19.399> so<00:15:19.600> the 00:15:19.670 --> 00:15:19.680 align:start position:0% broader vision for blockchains so the 00:15:19.680 --> 00:15:22.189 align:start position:0% broader vision for blockchains so the ethereum<00:15:20.120> blockchain<00:15:20.480> is<00:15:20.600> a<00:15:20.759> service<00:15:21.199> Vision 00:15:22.189 --> 00:15:22.199 align:start position:0% ethereum blockchain is a service Vision 00:15:22.199 --> 00:15:24.509 align:start position:0% ethereum blockchain is a service Vision with<00:15:22.680> containers<00:15:23.680> and<00:15:23.839> the<00:15:23.959> ability<00:15:24.279> to 00:15:24.509 --> 00:15:24.519 align:start position:0% with containers and the ability to 00:15:24.519 --> 00:15:26.150 align:start position:0% with containers and the ability to dynamically<00:15:25.079> spin<00:15:25.399> up<00:15:25.600> these<00:15:25.759> type<00:15:25.959> of 00:15:26.150 --> 00:15:26.160 align:start position:0% dynamically spin up these type of 00:15:26.160 --> 00:15:28.069 align:start position:0% dynamically spin up these type of resources<00:15:26.680> we<00:15:26.839> envision<00:15:27.240> an<00:15:27.480> era<00:15:27.839> of 00:15:28.069 --> 00:15:28.079 align:start position:0% resources we envision an era of 00:15:28.079 --> 00:15:29.629 align:start position:0% resources we envision an era of microservices 00:15:29.629 --> 00:15:29.639 align:start position:0% microservices 00:15:29.639 --> 00:15:31.870 align:start position:0% microservices so<00:15:30.040> microservices<00:15:31.040> uh<00:15:31.120> we<00:15:31.240> are<00:15:31.519> really 00:15:31.870 --> 00:15:31.880 align:start position:0% so microservices uh we are really 00:15:31.880 --> 00:15:34.629 align:start position:0% so microservices uh we are really decomposing<00:15:32.880> is<00:15:33.399> U<00:15:33.759> let<00:15:33.839> me<00:15:34.040> go<00:15:34.199> back<00:15:34.319> to<00:15:34.480> the 00:15:34.629 --> 00:15:34.639 align:start position:0% decomposing is U let me go back to the 00:15:34.639 --> 00:15:37.230 align:start position:0% decomposing is U let me go back to the talks<00:15:35.000> yesterday<00:15:35.959> the<00:15:36.199> capability<00:15:36.959> so<00:15:37.120> that 00:15:37.230 --> 00:15:37.240 align:start position:0% talks yesterday the capability so that 00:15:37.240 --> 00:15:39.870 align:start position:0% talks yesterday the capability so that you<00:15:37.360> can<00:15:37.600> quickly<00:15:38.399> compose 00:15:39.870 --> 00:15:39.880 align:start position:0% you can quickly compose 00:15:39.880 --> 00:15:43.230 align:start position:0% you can quickly compose Solutions<00:15:40.880> um<00:15:41.079> and<00:15:41.240> be<00:15:41.399> able<00:15:41.880> to<00:15:42.880> look<00:15:43.040> at 00:15:43.230 --> 00:15:43.240 align:start position:0% Solutions um and be able to look at 00:15:43.240 --> 00:15:44.670 align:start position:0% Solutions um and be able to look at these<00:15:43.440> different<00:15:43.759> capabilities<00:15:44.319> in<00:15:44.519> this 00:15:44.670 --> 00:15:44.680 align:start position:0% these different capabilities in this 00:15:44.680 --> 00:15:48.269 align:start position:0% these different capabilities in this service<00:15:45.480> fabric<00:15:46.480> um<00:15:46.759> and<00:15:46.920> be<00:15:47.120> able<00:15:47.360> to<00:15:47.759> begin 00:15:48.269 --> 00:15:48.279 align:start position:0% service fabric um and be able to begin 00:15:48.279 --> 00:15:50.430 align:start position:0% service fabric um and be able to begin developing<00:15:48.839> blockchainbased 00:15:50.430 --> 00:15:50.440 align:start position:0% developing blockchainbased 00:15:50.440 --> 00:15:53.269 align:start position:0% developing blockchainbased applications<00:15:51.440> consuming<00:15:52.120> and<00:15:52.399> exposing 00:15:53.269 --> 00:15:53.279 align:start position:0% applications consuming and exposing 00:15:53.279 --> 00:15:55.269 align:start position:0% applications consuming and exposing these<00:15:53.519> other<00:15:53.839> additional<00:15:54.360> value<00:15:54.639> added 00:15:55.269 --> 00:15:55.279 align:start position:0% these other additional value added 00:15:55.279 --> 00:15:58.550 align:start position:0% these other additional value added services<00:15:56.279> such<00:15:56.600> that<00:15:56.839> the<00:15:57.399> blockchain<00:15:58.399> um 00:15:58.550 --> 00:15:58.560 align:start position:0% services such that the blockchain um 00:15:58.560 --> 00:16:01.030 align:start position:0% services such that the blockchain um develop<00:15:59.199> in<00:15:59.279> the<00:15:59.399> ecosystem<00:16:00.040> becomes<00:16:00.319> a<00:16:00.600> much 00:16:01.030 --> 00:16:01.040 align:start position:0% develop in the ecosystem becomes a much 00:16:01.040 --> 00:16:02.949 align:start position:0% develop in the ecosystem becomes a much richer<00:16:01.600> environment<00:16:02.120> for<00:16:02.279> our<00:16:02.399> Enterprise 00:16:02.949 --> 00:16:02.959 align:start position:0% richer environment for our Enterprise 00:16:02.959 --> 00:16:06.470 align:start position:0% richer environment for our Enterprise customers<00:16:03.959> so<00:16:04.160> my<00:16:04.360> question<00:16:04.639> for<00:16:04.880> you<00:16:05.319> is<00:16:06.319> uh 00:16:06.470 --> 00:16:06.480 align:start position:0% customers so my question for you is uh 00:16:06.480 --> 00:16:08.309 align:start position:0% customers so my question for you is uh as<00:16:06.560> you<00:16:06.720> look<00:16:06.959> at<00:16:07.120> this<00:16:07.360> type<00:16:07.560> of 00:16:08.309 --> 00:16:08.319 align:start position:0% as you look at this type of 00:16:08.319 --> 00:16:11.150 align:start position:0% as you look at this type of environment<00:16:09.319> uh<00:16:09.600> and<00:16:10.000> noting<00:16:10.600> that<00:16:10.759> in<00:16:10.920> the 00:16:11.150 --> 00:16:11.160 align:start position:0% environment uh and noting that in the 00:16:11.160 --> 00:16:13.550 align:start position:0% environment uh and noting that in the back<00:16:11.839> if<00:16:11.959> you<00:16:12.120> grab<00:16:12.399> one<00:16:12.519> of<00:16:12.639> those<00:16:12.880> big 00:16:13.550 --> 00:16:13.560 align:start position:0% back if you grab one of those big 00:16:13.560 --> 00:16:16.990 align:start position:0% back if you grab one of those big posters<00:16:14.560> it<00:16:14.759> has<00:16:14.959> a<00:16:15.040> $200<00:16:15.920> certificate<00:16:16.839> it's 00:16:16.990 --> 00:16:17.000 align:start position:0% posters it has a $200 certificate it's 00:16:17.000 --> 00:16:18.629 align:start position:0% posters it has a $200 certificate it's like<00:16:17.120> winning<00:16:17.440> the<00:16:17.600> lottery<00:16:18.120> you<00:16:18.240> get<00:16:18.399> that 00:16:18.629 --> 00:16:18.639 align:start position:0% like winning the lottery you get that 00:16:18.639 --> 00:16:20.470 align:start position:0% like winning the lottery you get that big<00:16:18.920> check<00:16:19.399> that<00:16:19.800> actually<00:16:20.040> you<00:16:20.160> can't<00:16:20.360> do 00:16:20.470 --> 00:16:20.480 align:start position:0% big check that actually you can't do 00:16:20.480 --> 00:16:21.790 align:start position:0% big check that actually you can't do anything<00:16:20.759> with<00:16:21.120> you<00:16:21.240> actually<00:16:21.440> don't<00:16:21.600> have<00:16:21.680> to 00:16:21.790 --> 00:16:21.800 align:start position:0% anything with you actually don't have to 00:16:21.800 --> 00:16:23.629 align:start position:0% anything with you actually don't have to take<00:16:21.959> the<00:16:22.120> poster<00:16:22.519> but<00:16:23.000> everyone<00:16:23.279> that's<00:16:23.440> in 00:16:23.629 --> 00:16:23.639 align:start position:0% take the poster but everyone that's in 00:16:23.639 --> 00:16:25.069 align:start position:0% take the poster but everyone that's in attendance<00:16:24.240> will<00:16:24.399> have<00:16:24.519> the<00:16:24.600> ability<00:16:24.880> to<00:16:24.959> get 00:16:25.069 --> 00:16:25.079 align:start position:0% attendance will have the ability to get 00:16:25.079 --> 00:16:28.550 align:start position:0% attendance will have the ability to get a<00:16:25.120> $200<00:16:25.959> credit<00:16:26.240> for<00:16:26.880> Azure<00:16:27.880> um<00:16:28.000> to<00:16:28.120> be<00:16:28.240> able<00:16:28.399> to 00:16:28.550 --> 00:16:28.560 align:start position:0% a $200 credit for Azure um to be able to 00:16:28.560 --> 00:16:31.550 align:start position:0% a $200 credit for Azure um to be able to evaluate<00:16:29.279> this<00:16:30.160> and<00:16:30.560> uh<00:16:30.680> start<00:16:30.959> building<00:16:31.319> your 00:16:31.550 --> 00:16:31.560 align:start position:0% evaluate this and uh start building your 00:16:31.560 --> 00:16:33.670 align:start position:0% evaluate this and uh start building your apps<00:16:32.040> and<00:16:32.160> looking<00:16:32.440> at<00:16:32.680> building<00:16:33.079> ethereum 00:16:33.670 --> 00:16:33.680 align:start position:0% apps and looking at building ethereum 00:16:33.680 --> 00:16:36.870 align:start position:0% apps and looking at building ethereum apis<00:16:34.360> blockchain<00:16:34.880> apis<00:16:35.560> crypto<00:16:36.040> Services 00:16:36.870 --> 00:16:36.880 align:start position:0% apis blockchain apis crypto Services 00:16:36.880 --> 00:16:40.030 align:start position:0% apis blockchain apis crypto Services whatever<00:16:37.319> you<00:16:37.480> can<00:16:37.720> dream<00:16:38.160> of<00:16:39.160> uh<00:16:39.240> to<00:16:39.440> build<00:16:39.839> on 00:16:40.030 --> 00:16:40.040 align:start position:0% whatever you can dream of uh to build on 00:16:40.040 --> 00:16:42.749 align:start position:0% whatever you can dream of uh to build on this<00:16:40.279> platform<00:16:41.199> and<00:16:41.319> my<00:16:41.480> question<00:16:41.759> to<00:16:41.959> you<00:16:42.240> is 00:16:42.749 --> 00:16:42.759 align:start position:0% this platform and my question to you is 00:16:42.759 --> 00:16:46.020 align:start position:0% this platform and my question to you is what<00:16:42.920> will<00:16:43.120> you<00:16:43.639> add<00:16:44.639> thank<00:16:44.839> you 00:16:46.020 --> 00:16:46.030 align:start position:0% what will you add thank you 00:16:46.030 --> 00:16:52.090 align:start position:0% what will you add thank you [Applause] 00:16:52.090 --> 00:16:52.100 align:start position:0% [Applause] 00:16:52.100 --> 00:16:56.419 align:start position:0% [Applause] [Music]