WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.909 align:start position:0% [Applause] 00:00:11.909 --> 00:00:11.919 align:start position:0% 00:00:11.919 --> 00:00:18.609 align:start position:0% or<00:00:12.919> a<00:00:14.170> tamale<00:00:15.789> this<00:00:16.789> morning<00:00:17.200> how<00:00:18.200> efficient 00:00:18.609 --> 00:00:18.619 align:start position:0% or a tamale this morning how efficient 00:00:18.619 --> 00:00:22.450 align:start position:0% or a tamale this morning how efficient is<00:00:18.829> how<00:00:18.980> to<00:00:19.039> box<00:00:19.400> of<00:00:19.610> Engineers<00:00:21.460> blockchain 00:00:22.450 --> 00:00:22.460 align:start position:0% is how to box of Engineers blockchain 00:00:22.460 --> 00:00:27.070 align:start position:0% is how to box of Engineers blockchain enterprise<00:00:23.029> applications<00:00:24.369> so<00:00:25.570> the<00:00:26.570> two<00:00:26.900> of<00:00:26.990> us 00:00:27.070 --> 00:00:27.080 align:start position:0% enterprise applications so the two of us 00:00:27.080 --> 00:00:31.079 align:start position:0% enterprise applications so the two of us today<00:00:27.380> we've<00:00:27.679> got<00:00:27.890> pal<00:00:28.250> Peter<00:00:28.839> hello 00:00:31.079 --> 00:00:31.089 align:start position:0% today we've got pal Peter hello 00:00:31.089 --> 00:00:33.729 align:start position:0% today we've got pal Peter hello so<00:00:32.089> if<00:00:32.210> any<00:00:32.360> of<00:00:32.449> you<00:00:32.599> are<00:00:32.900> using<00:00:33.140> some<00:00:33.559> of<00:00:33.589> the 00:00:33.729 --> 00:00:33.739 align:start position:0% so if any of you are using some of the 00:00:33.739 --> 00:00:35.560 align:start position:0% so if any of you are using some of the cool<00:00:33.890> stuff<00:00:33.920> that<00:00:34.190> we<00:00:34.400> have<00:00:34.640> my<00:00:34.820> phone<00:00:35.059> as<00:00:35.360> your 00:00:35.560 --> 00:00:35.570 align:start position:0% cool stuff that we have my phone as your 00:00:35.570 --> 00:00:38.350 align:start position:0% cool stuff that we have my phone as your inside<00:00:35.900> okay<00:00:36.079> okay<00:00:36.739> okay<00:00:37.640> I<00:00:37.670> was<00:00:37.820> out<00:00:38.059> of<00:00:38.120> the 00:00:38.350 --> 00:00:38.360 align:start position:0% inside okay okay okay I was out of the 00:00:38.360 --> 00:00:40.540 align:start position:0% inside okay okay okay I was out of the Parkers<00:00:38.960> so<00:00:39.440> the<00:00:39.500> primary<00:00:39.680> by<00:00:40.070> the<00:00:40.129> wife<00:00:40.339> is 00:00:40.540 --> 00:00:40.550 align:start position:0% Parkers so the primary by the wife is 00:00:40.550 --> 00:00:42.189 align:start position:0% Parkers so the primary by the wife is not<00:00:40.610> a<00:00:40.820> watch<00:00:41.089> something<00:00:41.420> you<00:00:41.659> would<00:00:41.900> all<00:00:42.050> the 00:00:42.189 --> 00:00:42.199 align:start position:0% not a watch something you would all the 00:00:42.199 --> 00:00:44.529 align:start position:0% not a watch something you would all the cool<00:00:42.410> tools<00:00:42.710> that<00:00:42.980> everyone<00:00:43.250> can<00:00:43.520> use<00:00:43.550> about 00:00:44.529 --> 00:00:44.539 align:start position:0% cool tools that everyone can use about 00:00:44.539 --> 00:00:47.260 align:start position:0% cool tools that everyone can use about me<00:00:44.949> I'm<00:00:45.949> in<00:00:46.129> a<00:00:46.190> different<00:00:46.520> section<00:00:46.699> of<00:00:46.850> markup 00:00:47.260 --> 00:00:47.270 align:start position:0% me I'm in a different section of markup 00:00:47.270 --> 00:00:48.610 align:start position:0% me I'm in a different section of markup for<00:00:47.539> an<00:00:47.629> unconventional<00:00:47.960> software 00:00:48.610 --> 00:00:48.620 align:start position:0% for an unconventional software 00:00:48.620 --> 00:00:57.170 align:start position:0% for an unconventional software engineering 00:00:57.170 --> 00:00:57.180 align:start position:0% 00:00:57.180 --> 00:01:00.620 align:start position:0% they<00:00:58.050> do<00:00:58.250> so<00:00:59.250> we<00:00:59.370> go<00:00:59.550> where<00:01:00.390> are<00:01:00.480> these 00:01:00.620 --> 00:01:00.630 align:start position:0% they do so we go where are these 00:01:00.630 --> 00:01:03.440 align:start position:0% they do so we go where are these customers<00:01:01.170> so<00:01:02.040> what<00:01:02.220> I<00:01:02.250> do<00:01:02.400> is<00:01:02.790> I<00:01:03.000> hope<00:01:03.240> these 00:01:03.440 --> 00:01:03.450 align:start position:0% customers so what I do is I hope these 00:01:03.450 --> 00:01:05.119 align:start position:0% customers so what I do is I hope these new<00:01:03.510> customs<00:01:04.170> going<00:01:04.470> to<00:01:04.530> be<00:01:04.589> launching 00:01:05.119 --> 00:01:05.129 align:start position:0% new customs going to be launching 00:01:05.129 --> 00:01:09.140 align:start position:0% new customs going to be launching applications<00:01:06.830> this<00:01:07.830> session<00:01:08.160> is<00:01:08.580> a<00:01:08.610> mixture 00:01:09.140 --> 00:01:09.150 align:start position:0% applications this session is a mixture 00:01:09.150 --> 00:01:11.270 align:start position:0% applications this session is a mixture of<00:01:09.300> me<00:01:10.229> going<00:01:10.500> through<00:01:10.800> some<00:01:11.130> of<00:01:11.190> the 00:01:11.270 --> 00:01:11.280 align:start position:0% of me going through some of the 00:01:11.280 --> 00:01:16.040 align:start position:0% of me going through some of the architecture<00:01:11.970> that<00:01:12.000> I<00:01:12.479> use<00:01:14.060> sometimes<00:01:15.060> I<00:01:15.840> use 00:01:16.040 --> 00:01:16.050 align:start position:0% architecture that I use sometimes I use 00:01:16.050 --> 00:01:17.150 align:start position:0% architecture that I use sometimes I use when<00:01:16.229> I'm<00:01:16.320> creating<00:01:16.619> this<00:01:16.890> enterprise 00:01:17.150 --> 00:01:17.160 align:start position:0% when I'm creating this enterprise 00:01:17.160 --> 00:01:19.760 align:start position:0% when I'm creating this enterprise applications<00:01:18.030> wouldn't<00:01:18.810> we<00:01:18.869> talk<00:01:19.080> to<00:01:19.590> these 00:01:19.760 --> 00:01:19.770 align:start position:0% applications wouldn't we talk to these 00:01:19.770 --> 00:01:21.140 align:start position:0% applications wouldn't we talk to these I'm<00:01:20.010> in<00:01:20.160> across<00:01:20.400> the<00:01:20.670> mouth<00:01:20.820> cavity 00:01:21.140 --> 00:01:21.150 align:start position:0% I'm in across the mouth cavity 00:01:21.150 --> 00:01:24.469 align:start position:0% I'm in across the mouth cavity architecture<00:01:22.550> remember<00:01:23.550> -<00:01:23.729> Cael<00:01:23.970> he<00:01:24.360> will 00:01:24.469 --> 00:01:24.479 align:start position:0% architecture remember - Cael he will 00:01:24.479 --> 00:01:28.250 align:start position:0% architecture remember - Cael he will walk<00:01:24.660> through<00:01:26.330> cooling<00:01:27.330> and<00:01:27.600> how<00:01:27.780> that<00:01:28.020> can<00:01:28.200> be 00:01:28.250 --> 00:01:28.260 align:start position:0% walk through cooling and how that can be 00:01:28.260 --> 00:01:29.900 align:start position:0% walk through cooling and how that can be used<00:01:28.530> to<00:01:28.619> accelerate<00:01:28.920> doing<00:01:29.490> blockchain 00:01:29.900 --> 00:01:29.910 align:start position:0% used to accelerate doing blockchain 00:01:29.910 --> 00:01:32.359 align:start position:0% used to accelerate doing blockchain applications<00:01:30.509> I<00:01:30.780> will<00:01:31.320> flip<00:01:31.470> back<00:01:31.710> to<00:01:31.740> me<00:01:32.070> and 00:01:32.359 --> 00:01:32.369 align:start position:0% applications I will flip back to me and 00:01:32.369 --> 00:01:34.460 align:start position:0% applications I will flip back to me and I'll<00:01:32.580> cover<00:01:32.820> up<00:01:33.090> now<00:01:33.450> that<00:01:33.630> young<00:01:33.780> and<00:01:34.170> some<00:01:34.350> of 00:01:34.460 --> 00:01:34.470 align:start position:0% I'll cover up now that young and some of 00:01:34.470 --> 00:01:36.139 align:start position:0% I'll cover up now that young and some of the<00:01:34.560> tunic<00:01:34.950> looks<00:01:35.190> Alec<00:01:35.880> Eger 00:01:36.139 --> 00:01:36.149 align:start position:0% the tunic looks Alec Eger 00:01:36.149 --> 00:01:42.859 align:start position:0% the tunic looks Alec Eger compose<00:01:36.600> things<00:01:36.780> together<00:01:41.509> let's<00:01:42.509> cover<00:01:42.690> up 00:01:42.859 --> 00:01:42.869 align:start position:0% compose things together let's cover up 00:01:42.869 --> 00:01:45.050 align:start position:0% compose things together let's cover up the<00:01:43.050> one<00:01:43.320> that<00:01:43.500> I<00:01:43.560> usually<00:01:43.740> get<00:01:44.100> like<00:01:44.729> this 00:01:45.050 --> 00:01:45.060 align:start position:0% the one that I usually get like this 00:01:45.060 --> 00:01:47.240 align:start position:0% the one that I usually get like this which<00:01:45.690> is<00:01:45.840> usually<00:01:46.170> why<00:01:46.380> the<00:01:46.860> do<00:01:47.040> we<00:01:47.070> need 00:01:47.240 --> 00:01:47.250 align:start position:0% which is usually why the do we need 00:01:47.250 --> 00:01:48.680 align:start position:0% which is usually why the do we need public<00:01:47.550> and<00:01:47.759> private<00:01:48.119> blockchains 00:01:48.680 --> 00:01:48.690 align:start position:0% public and private blockchains 00:01:48.690 --> 00:01:50.150 align:start position:0% public and private blockchains we<00:01:48.810> have<00:01:48.960> public<00:01:49.380> everything<00:01:49.920> should<00:01:50.040> be 00:01:50.150 --> 00:01:50.160 align:start position:0% we have public everything should be 00:01:50.160 --> 00:01:54.700 align:start position:0% we have public everything should be covered<00:01:51.170> so<00:01:52.550> come<00:01:53.550> up<00:01:53.670> with<00:01:53.790> the<00:01:53.880> oval<00:01:54.420> ring 00:01:54.700 --> 00:01:54.710 align:start position:0% covered so come up with the oval ring 00:01:54.710 --> 00:01:57.740 align:start position:0% covered so come up with the oval ring public<00:01:55.710> aetherium<00:01:56.310> we<00:01:56.910> can't<00:01:57.149> trust<00:01:57.390> anyone 00:01:57.740 --> 00:01:57.750 align:start position:0% public aetherium we can't trust anyone 00:01:57.750 --> 00:02:00.770 align:start position:0% public aetherium we can't trust anyone so<00:01:58.350> because<00:01:59.100> of<00:01:59.250> that<00:01:59.280> the<00:01:59.850> security<00:02:00.390> thinks 00:02:00.770 --> 00:02:00.780 align:start position:0% so because of that the security thinks 00:02:00.780 --> 00:02:01.969 align:start position:0% so because of that the security thinks that<00:02:00.869> they'll<00:02:01.110> intro<00:02:01.500> them<00:02:01.710> all<00:02:01.860> around 00:02:01.969 --> 00:02:01.979 align:start position:0% that they'll intro them all around 00:02:01.979 --> 00:02:03.890 align:start position:0% that they'll intro them all around justice<00:02:02.729> human<00:02:03.030> if<00:02:03.119> everyone<00:02:03.540> is<00:02:03.630> trying<00:02:03.810> to 00:02:03.890 --> 00:02:03.900 align:start position:0% justice human if everyone is trying to 00:02:03.900 --> 00:02:06.980 align:start position:0% justice human if everyone is trying to take<00:02:04.049> us<00:02:04.200> lightly<00:02:04.490> so<00:02:05.490> everyone<00:02:06.060> is<00:02:06.299> confirmed 00:02:06.980 --> 00:02:06.990 align:start position:0% take us lightly so everyone is confirmed 00:02:06.990 --> 00:02:10.150 align:start position:0% take us lightly so everyone is confirmed the<00:02:07.080> keys 00:02:10.150 --> 00:02:10.160 align:start position:0% 00:02:10.160 --> 00:02:12.670 align:start position:0% in<00:02:10.400> disgust<00:02:10.760> yet<00:02:11.000> because<00:02:11.600> we<00:02:11.720> diagnose<00:02:12.200> to<00:02:12.530> do 00:02:12.670 --> 00:02:12.680 align:start position:0% in disgust yet because we diagnose to do 00:02:12.680 --> 00:02:14.830 align:start position:0% in disgust yet because we diagnose to do the<00:02:12.800> bad<00:02:12.980> act<00:02:13.190> aside<00:02:13.520> so<00:02:13.880> everything<00:02:14.510> has<00:02:14.660> to 00:02:14.830 --> 00:02:14.840 align:start position:0% the bad act aside so everything has to 00:02:14.840 --> 00:02:17.350 align:start position:0% the bad act aside so everything has to be<00:02:14.960> security<00:02:15.740> around<00:02:15.980> that<00:02:16.400> axis<00:02:16.730> trying<00:02:17.210> to 00:02:17.350 --> 00:02:17.360 align:start position:0% be security around that axis trying to 00:02:17.360 --> 00:02:20.980 align:start position:0% be security around that axis trying to take<00:02:17.540> these<00:02:17.720> tools<00:02:18.880> which<00:02:19.880> is<00:02:20.030> okay<00:02:20.330> but<00:02:20.780> what 00:02:20.980 --> 00:02:20.990 align:start position:0% take these tools which is okay but what 00:02:20.990 --> 00:02:22.660 align:start position:0% take these tools which is okay but what we<00:02:21.110> can<00:02:21.260> solve<00:02:21.500> a<00:02:21.620> private<00:02:22.040> network<00:02:22.160> we<00:02:22.550> have 00:02:22.660 --> 00:02:22.670 align:start position:0% we can solve a private network we have 00:02:22.670 --> 00:02:24.700 align:start position:0% we can solve a private network we have different<00:02:23.120> security<00:02:23.560> considerations<00:02:24.560> to 00:02:24.700 --> 00:02:24.710 align:start position:0% different security considerations to 00:02:24.710 --> 00:02:29.230 align:start position:0% different security considerations to worry<00:02:24.890> about<00:02:25.750> and<00:02:26.750> usually<00:02:27.350> with<00:02:28.310> the<00:02:28.520> web<00:02:28.970> UI 00:02:29.230 --> 00:02:29.240 align:start position:0% worry about and usually with the web UI 00:02:29.240 --> 00:02:31.300 align:start position:0% worry about and usually with the web UI and<00:02:29.540> application<00:02:30.050> front<00:02:30.290> end<00:02:30.470> usually<00:02:30.800> this 00:02:31.300 --> 00:02:31.310 align:start position:0% and application front end usually this 00:02:31.310 --> 00:02:34.089 align:start position:0% and application front end usually this type<00:02:31.610> of<00:02:31.640> stuff<00:02:31.910> is<00:02:31.940> deployed<00:02:32.360> else<00:02:32.540> would 00:02:34.089 --> 00:02:34.099 align:start position:0% type of stuff is deployed else would 00:02:34.099 --> 00:02:37.809 align:start position:0% type of stuff is deployed else would well<00:02:35.469> now<00:02:36.469> that's<00:02:36.920> great<00:02:37.280> bro 00:02:37.809 --> 00:02:37.819 align:start position:0% well now that's great bro 00:02:37.819 --> 00:02:40.119 align:start position:0% well now that's great bro venison<00:02:38.569> are<00:02:38.749> great<00:02:38.930> but<00:02:39.139> I'm<00:02:39.379> Shiva<00:02:39.769> to<00:02:40.010> kiss 00:02:40.119 --> 00:02:40.129 align:start position:0% venison are great but I'm Shiva to kiss 00:02:40.129 --> 00:02:43.300 align:start position:0% venison are great but I'm Shiva to kiss you<00:02:40.280> apps<00:02:40.579> that's<00:02:41.090> right<00:02:41.389> both<00:02:42.159> inside<00:02:43.159> of<00:02:43.249> the 00:02:43.300 --> 00:02:43.310 align:start position:0% you apps that's right both inside of the 00:02:43.310 --> 00:02:45.970 align:start position:0% you apps that's right both inside of the enterprise<00:02:43.730> space<00:02:43.989> these<00:02:44.989> limits<00:02:45.590> reading 00:02:45.970 --> 00:02:45.980 align:start position:0% enterprise space these limits reading 00:02:45.980 --> 00:02:48.580 align:start position:0% enterprise space these limits reading the<00:02:46.069> February<00:02:46.430> about<00:02:47.319> enterprises<00:02:48.319> think 00:02:48.580 --> 00:02:48.590 align:start position:0% the February about enterprises think 00:02:48.590 --> 00:02:49.839 align:start position:0% the February about enterprises think that<00:02:48.769> they<00:02:48.889> have<00:02:49.099> really<00:02:49.340> really<00:02:49.459> live 00:02:49.839 --> 00:02:49.849 align:start position:0% that they have really really live 00:02:49.849 --> 00:02:51.670 align:start position:0% that they have really really live transaction<00:02:50.420> volumes<00:02:50.689> so<00:02:51.019> they<00:02:51.170> always<00:02:51.349> say 00:02:51.670 --> 00:02:51.680 align:start position:0% transaction volumes so they always say 00:02:51.680 --> 00:02:53.530 align:start position:0% transaction volumes so they always say the<00:02:51.889> company<00:02:52.219> the<00:02:52.280> etherium<00:02:53.000> public<00:02:53.359> club 00:02:53.530 --> 00:02:53.540 align:start position:0% the company the etherium public club 00:02:53.540 --> 00:02:56.500 align:start position:0% the company the etherium public club chains<00:02:53.780> not<00:02:53.989> allowed<00:02:55.180> we<00:02:56.180> want<00:02:56.359> to<00:02:56.420> do 00:02:56.500 --> 00:02:56.510 align:start position:0% chains not allowed we want to do 00:02:56.510 --> 00:02:57.490 align:start position:0% chains not allowed we want to do something<00:02:56.719> possible 00:02:57.490 --> 00:02:57.500 align:start position:0% something possible 00:02:57.500 --> 00:02:59.860 align:start position:0% something possible so<00:02:57.950> because<00:02:58.310> we<00:02:58.459> have<00:02:58.489> different<00:02:58.870> security 00:02:59.860 --> 00:02:59.870 align:start position:0% so because we have different security 00:02:59.870 --> 00:03:02.649 align:start position:0% so because we have different security considerations<00:03:00.859> we<00:03:01.430> can<00:03:01.609> relax<00:03:02.000> some<00:03:02.569> of 00:03:02.649 --> 00:03:02.659 align:start position:0% considerations we can relax some of 00:03:02.659 --> 00:03:04.720 align:start position:0% considerations we can relax some of these<00:03:02.750> things<00:03:02.989> so<00:03:03.349> we<00:03:03.739> can<00:03:03.889> go<00:03:04.040> move<00:03:04.310> to<00:03:04.519> things 00:03:04.720 --> 00:03:04.730 align:start position:0% these things so we can go move to things 00:03:04.730 --> 00:03:06.580 align:start position:0% these things so we can go move to things like<00:03:04.790> approval<00:03:05.269> Authority<00:03:05.719> where<00:03:05.959> we<00:03:06.019> can<00:03:06.290> get 00:03:06.580 --> 00:03:06.590 align:start position:0% like approval Authority where we can get 00:03:06.590 --> 00:03:08.800 align:start position:0% like approval Authority where we can get some<00:03:06.769> of<00:03:06.829> its<00:03:06.980> high<00:03:07.129> transaction<00:03:07.489> volume<00:03:07.969> so 00:03:08.800 --> 00:03:08.810 align:start position:0% some of its high transaction volume so 00:03:08.810 --> 00:03:10.659 align:start position:0% some of its high transaction volume so that's<00:03:09.049> one<00:03:09.409> consideration<00:03:09.769> but<00:03:10.549> it's 00:03:10.659 --> 00:03:10.669 align:start position:0% that's one consideration but it's 00:03:10.669 --> 00:03:12.580 align:start position:0% that's one consideration but it's usually<00:03:10.760> not<00:03:11.000> the<00:03:11.510> main<00:03:11.719> reason<00:03:12.169> that<00:03:12.199> we<00:03:12.349> end 00:03:12.580 --> 00:03:12.590 align:start position:0% usually not the main reason that we end 00:03:12.590 --> 00:03:14.300 align:start position:0% usually not the main reason that we end up<00:03:12.650> using<00:03:12.709> a<00:03:12.949> ramen<00:03:13.310> change 00:03:14.300 --> 00:03:14.310 align:start position:0% up using a ramen change 00:03:14.310 --> 00:03:17.660 align:start position:0% up using a ramen change the<00:03:14.970> two<00:03:15.180> main<00:03:15.480> reasons<00:03:15.510> I<00:03:16.470> usually<00:03:17.190> scared<00:03:17.550> of 00:03:17.660 --> 00:03:17.670 align:start position:0% the two main reasons I usually scared of 00:03:17.670 --> 00:03:19.760 align:start position:0% the two main reasons I usually scared of the<00:03:17.730> other<00:03:17.880> thing<00:03:18.060> we're<00:03:18.930> going<00:03:19.080> to<00:03:19.140> talk<00:03:19.470> in<00:03:19.680> a 00:03:19.760 --> 00:03:19.770 align:start position:0% the other thing we're going to talk in a 00:03:19.770 --> 00:03:23.630 align:start position:0% the other thing we're going to talk in a process<00:03:20.220> with<00:03:21.950> motivated<00:03:22.950> develop<00:03:23.280> test<00:03:23.489> and 00:03:23.630 --> 00:03:23.640 align:start position:0% process with motivated develop test and 00:03:23.640 --> 00:03:25.640 align:start position:0% process with motivated develop test and they<00:03:24.510> want<00:03:24.720> to<00:03:24.810> go<00:03:24.900> to<00:03:24.930> something 00:03:25.640 --> 00:03:25.650 align:start position:0% they want to go to something 00:03:25.650 --> 00:03:28.220 align:start position:0% they want to go to something what<00:03:25.830> chaining<00:03:26.250> but<00:03:26.489> they're<00:03:26.670> afraid<00:03:27.390> of<00:03:27.510> and 00:03:28.220 --> 00:03:28.230 align:start position:0% what chaining but they're afraid of and 00:03:28.230 --> 00:03:31.900 align:start position:0% what chaining but they're afraid of and they<00:03:28.590> want<00:03:28.800> to<00:03:28.860> know<00:03:28.920> publicly<00:03:29.910> because<00:03:30.150> that 00:03:31.900 --> 00:03:31.910 align:start position:0% they want to know publicly because that 00:03:31.910 --> 00:03:34.880 align:start position:0% they want to know publicly because that so<00:03:32.910> they<00:03:33.060> want<00:03:33.239> to<00:03:33.300> have<00:03:33.390> a<00:03:33.420> nice<00:03:33.720> safe<00:03:34.560> space 00:03:34.880 --> 00:03:34.890 align:start position:0% so they want to have a nice safe space 00:03:34.890 --> 00:03:37.430 align:start position:0% so they want to have a nice safe space that<00:03:34.920> they<00:03:35.220> can<00:03:35.400> go<00:03:35.630> deploy<00:03:36.630> something<00:03:36.900> play 00:03:37.430 --> 00:03:37.440 align:start position:0% that they can go deploy something play 00:03:37.440 --> 00:03:39.380 align:start position:0% that they can go deploy something play with<00:03:37.650> it<00:03:37.800> get<00:03:38.280> the<00:03:38.400> developers<00:03:38.910> through<00:03:39.269> the 00:03:39.380 --> 00:03:39.390 align:start position:0% with it get the developers through the 00:03:39.390 --> 00:03:41.330 align:start position:0% with it get the developers through the emotion<00:03:39.810> of<00:03:39.930> how<00:03:40.170> to<00:03:40.230> build<00:03:40.620> these<00:03:40.830> things<00:03:41.040> and 00:03:41.330 --> 00:03:41.340 align:start position:0% emotion of how to build these things and 00:03:41.340 --> 00:03:43.490 align:start position:0% emotion of how to build these things and then<00:03:41.940> once<00:03:42.150> I<00:03:42.420> mean<00:03:42.540> if<00:03:42.599> you<00:03:42.810> use<00:03:42.840> on<00:03:43.110> some<00:03:43.230> more 00:03:43.490 --> 00:03:43.500 align:start position:0% then once I mean if you use on some more 00:03:43.500 --> 00:03:46.370 align:start position:0% then once I mean if you use on some more happy<00:03:44.010> go<00:03:44.730> start<00:03:44.940> moving<00:03:45.239> into<00:03:45.380> painting 00:03:46.370 --> 00:03:46.380 align:start position:0% happy go start moving into painting 00:03:46.380 --> 00:03:49.789 align:start position:0% happy go start moving into painting space<00:03:47.660> level<00:03:48.660> of<00:03:48.720> maturity<00:03:49.049> of<00:03:49.440> private 00:03:49.789 --> 00:03:49.799 align:start position:0% space level of maturity of private 00:03:49.799 --> 00:03:52.220 align:start position:0% space level of maturity of private transactions<00:03:50.370> a<00:03:50.760> lot<00:03:51.690> of<00:03:51.780> the<00:03:51.870> things<00:03:52.140> that 00:03:52.220 --> 00:03:52.230 align:start position:0% transactions a lot of the things that 00:03:52.230 --> 00:03:53.930 align:start position:0% transactions a lot of the things that they<00:03:52.410> sent<00:03:52.620> a<00:03:52.650> positive<00:03:53.040> doing<00:03:53.310> a<00:03:53.459> beta<00:03:53.700> base 00:03:53.930 --> 00:03:53.940 align:start position:0% they sent a positive doing a beta base 00:03:53.940 --> 00:03:56.990 align:start position:0% they sent a positive doing a beta base scenario<00:03:54.480> is<00:03:54.840> commercially<00:03:55.500> sensitive<00:03:56.000> right 00:03:56.990 --> 00:03:57.000 align:start position:0% scenario is commercially sensitive right 00:03:57.000 --> 00:04:01.240 align:start position:0% scenario is commercially sensitive right now<00:03:57.239> with<00:03:57.690> public<00:03:58.440> etherium<00:03:59.989> transaction<00:04:00.989> is 00:04:01.240 --> 00:04:01.250 align:start position:0% now with public etherium transaction is 00:04:01.250 --> 00:04:03.949 align:start position:0% now with public etherium transaction is now<00:04:02.250> there<00:04:02.489> are<00:04:02.610> things<00:04:03.180> happening<00:04:03.420> with<00:04:03.780> Zeke 00:04:03.949 --> 00:04:03.959 align:start position:0% now there are things happening with Zeke 00:04:03.959 --> 00:04:07.250 align:start position:0% now there are things happening with Zeke I<00:04:04.140> stocks<00:04:05.269> young<00:04:06.269> have<00:04:06.930> just<00:04:07.140> released 00:04:07.250 --> 00:04:07.260 align:start position:0% I stocks young have just released 00:04:07.260 --> 00:04:08.120 align:start position:0% I stocks young have just released Michael 00:04:08.120 --> 00:04:08.130 align:start position:0% Michael 00:04:08.130 --> 00:04:10.660 align:start position:0% Michael they<00:04:08.400> were<00:04:08.459> looking<00:04:08.700> at<00:04:08.819> logical<00:04:09.269> to<00:04:09.420> coding 00:04:10.660 --> 00:04:10.670 align:start position:0% they were looking at logical to coding 00:04:10.670 --> 00:04:12.650 align:start position:0% they were looking at logical to coding integrate<00:04:11.670> thoughtful<00:04:12.090> into<00:04:12.299> some<00:04:12.450> of<00:04:12.540> what 00:04:12.650 --> 00:04:12.660 align:start position:0% integrate thoughtful into some of what 00:04:12.660 --> 00:04:14.839 align:start position:0% integrate thoughtful into some of what we're<00:04:12.810> doing<00:04:12.930> but<00:04:13.290> as<00:04:13.890> it<00:04:14.160> is<00:04:14.190> things<00:04:14.700> the 00:04:14.839 --> 00:04:14.849 align:start position:0% we're doing but as it is things the 00:04:14.849 --> 00:04:16.069 align:start position:0% we're doing but as it is things the three<00:04:15.090> main<00:04:15.269> reasons<00:04:15.299> why<00:04:15.810> we<00:04:16.019> need 00:04:16.069 --> 00:04:16.079 align:start position:0% three main reasons why we need 00:04:16.079 --> 00:04:17.150 align:start position:0% three main reasons why we need everything 00:04:17.150 --> 00:04:17.160 align:start position:0% everything 00:04:17.160 --> 00:04:20.180 align:start position:0% everything yes<00:04:17.810> there<00:04:18.810> people<00:04:19.110> at<00:04:19.380> a<00:04:19.410> private<00:04:19.800> enterprise 00:04:20.180 --> 00:04:20.190 align:start position:0% yes there people at a private enterprise 00:04:20.190 --> 00:04:22.970 align:start position:0% yes there people at a private enterprise network<00:04:20.730> look<00:04:21.450> like<00:04:21.630> this<00:04:21.870> so<00:04:22.500> instead<00:04:22.770> of 00:04:22.970 --> 00:04:22.980 align:start position:0% network look like this so instead of 00:04:22.980 --> 00:04:26.000 align:start position:0% network look like this so instead of having<00:04:23.310> unknown<00:04:24.000> actors<00:04:24.690> we've<00:04:25.290> got<00:04:25.530> a<00:04:25.560> profit 00:04:26.000 --> 00:04:26.010 align:start position:0% having unknown actors we've got a profit 00:04:26.010 --> 00:04:28.610 align:start position:0% having unknown actors we've got a profit or<00:04:26.310> Arbitron<00:04:26.790> so<00:04:27.030> we<00:04:27.210> know<00:04:27.420> garment<00:04:28.320> bag 00:04:28.610 --> 00:04:28.620 align:start position:0% or Arbitron so we know garment bag 00:04:28.620 --> 00:04:32.150 align:start position:0% or Arbitron so we know garment bag design<00:04:30.110> we<00:04:31.110> can<00:04:31.320> relax<00:04:31.680> some<00:04:31.980> of<00:04:32.010> these 00:04:32.150 --> 00:04:32.160 align:start position:0% design we can relax some of these 00:04:32.160 --> 00:04:34.310 align:start position:0% design we can relax some of these security<00:04:32.700> considerations<00:04:33.450> just<00:04:33.900> a<00:04:34.020> little 00:04:34.310 --> 00:04:34.320 align:start position:0% security considerations just a little 00:04:34.320 --> 00:04:37.100 align:start position:0% security considerations just a little bit<00:04:34.500> so<00:04:35.250> it<00:04:35.520> goes<00:04:35.670> from<00:04:35.970> heaven<00:04:36.390> trying<00:04:36.900> to<00:04:36.990> do 00:04:37.100 --> 00:04:37.110 align:start position:0% bit so it goes from heaven trying to do 00:04:37.110 --> 00:04:39.950 align:start position:0% bit so it goes from heaven trying to do this<00:04:37.260> in<00:04:37.500> a<00:04:37.650> trust<00:04:38.220> us<00:04:38.370> this<00:04:38.490> implies<00:04:38.940> way<00:04:39.300> to 00:04:39.950 --> 00:04:39.960 align:start position:0% this in a trust us this implies way to 00:04:39.960 --> 00:04:42.620 align:start position:0% this in a trust us this implies way to more<00:04:40.140> of<00:04:40.290> a<00:04:40.380> we<00:04:41.370> go<00:04:41.580> and<00:04:41.850> use<00:04:41.970> a<00:04:42.000> blockchain<00:04:42.270> to 00:04:42.620 --> 00:04:42.630 align:start position:0% more of a we go and use a blockchain to 00:04:42.630 --> 00:04:45.770 align:start position:0% more of a we go and use a blockchain to the<00:04:42.720> shared<00:04:42.990> source<00:04:43.200> of<00:04:43.410> truth<00:04:43.740> so<00:04:44.780> understand 00:04:45.770 --> 00:04:45.780 align:start position:0% the shared source of truth so understand 00:04:45.780 --> 00:04:55.010 align:start position:0% the shared source of truth so understand that<00:04:48.950> right<00:04:49.950> now<00:04:51.200> business<00:04:52.200> applications<00:04:54.020> so 00:04:55.010 --> 00:04:55.020 align:start position:0% that right now business applications so 00:04:55.020 --> 00:04:57.800 align:start position:0% that right now business applications so to<00:04:55.290> me<00:04:55.610> that's<00:04:56.610> another<00:04:56.970> reason<00:04:57.180> why<00:04:57.420> we<00:04:57.450> do<00:04:57.750> it 00:04:57.800 --> 00:04:57.810 align:start position:0% to me that's another reason why we do it 00:04:57.810 --> 00:04:58.370 align:start position:0% to me that's another reason why we do it like<00:04:57.960> this 00:04:58.370 --> 00:04:58.380 align:start position:0% like this 00:04:58.380 --> 00:05:00.320 align:start position:0% like this they<00:04:58.500> have<00:04:58.710> it<00:04:58.920> three<00:04:59.760> different 00:05:00.320 --> 00:05:00.330 align:start position:0% they have it three different 00:05:00.330 --> 00:05:04.810 align:start position:0% they have it three different appointments<00:05:01.170> each<00:05:01.590> and<00:05:01.800> a<00:05:01.860> processor<00:05:02.430> and 00:05:04.810 --> 00:05:04.820 align:start position:0% 00:05:04.820 --> 00:05:07.490 align:start position:0% because<00:05:05.820> although<00:05:06.150> they're<00:05:06.810> gonna<00:05:06.930> be<00:05:07.290> here 00:05:07.490 --> 00:05:07.500 align:start position:0% because although they're gonna be here 00:05:07.500 --> 00:05:09.590 align:start position:0% because although they're gonna be here the<00:05:07.650> pump<00:05:07.890> go<00:05:08.160> hey<00:05:08.760> we<00:05:08.970> wanted<00:05:09.210> me<00:05:09.330> out<00:05:09.360> to 00:05:09.590 --> 00:05:09.600 align:start position:0% the pump go hey we wanted me out to 00:05:09.600 --> 00:05:11.150 align:start position:0% the pump go hey we wanted me out to track<00:05:09.840> these<00:05:10.020> widgets<00:05:10.290> more<00:05:10.710> efficiently 00:05:11.150 --> 00:05:11.160 align:start position:0% track these widgets more efficiently 00:05:11.160 --> 00:05:16.840 align:start position:0% track these widgets more efficiently between<00:05:11.820> us 00:05:16.840 --> 00:05:16.850 align:start position:0% 00:05:16.850 --> 00:05:18.880 align:start position:0% [Music] 00:05:18.880 --> 00:05:18.890 align:start position:0% [Music] 00:05:18.890 --> 00:05:25.719 align:start position:0% [Music] application 00:05:25.719 --> 00:05:25.729 align:start position:0% 00:05:25.729 --> 00:05:29.679 align:start position:0% now<00:05:26.559> that's<00:05:27.559> a<00:05:27.680> while<00:05:27.830> I'm<00:05:27.949> good<00:05:28.249> so<00:05:28.689> typically 00:05:29.679 --> 00:05:29.689 align:start position:0% now that's a while I'm good so typically 00:05:29.689 --> 00:05:31.689 align:start position:0% now that's a while I'm good so typically happening<00:05:30.349> that's<00:05:30.499> what<00:05:30.650> happens<00:05:31.009> when<00:05:31.309> I<00:05:31.639> get 00:05:31.689 --> 00:05:31.699 align:start position:0% happening that's what happens when I get 00:05:31.699 --> 00:05:34.929 align:start position:0% happening that's what happens when I get caught<00:05:32.059> in<00:05:32.270> is<00:05:32.889> we<00:05:33.889> talk<00:05:34.099> to<00:05:34.580> the<00:05:34.699> enterprise 00:05:34.929 --> 00:05:34.939 align:start position:0% caught in is we talk to the enterprise 00:05:34.939 --> 00:05:37.209 align:start position:0% caught in is we talk to the enterprise and<00:05:35.449> what<00:05:35.779> we<00:05:35.900> ask<00:05:36.080> them<00:05:36.439> do<00:05:36.889> you<00:05:36.949> know<00:05:37.099> about 00:05:37.209 --> 00:05:37.219 align:start position:0% and what we ask them do you know about 00:05:37.219 --> 00:05:38.799 align:start position:0% and what we ask them do you know about blockchain<00:05:37.610> that<00:05:38.089> was<00:05:38.270> good<00:05:38.449> yeah<00:05:38.599> yeah<00:05:38.779> I 00:05:38.799 --> 00:05:38.809 align:start position:0% blockchain that was good yeah yeah I 00:05:38.809 --> 00:05:40.600 align:start position:0% blockchain that was good yeah yeah I read<00:05:39.110> Forbes<00:05:39.379> magazine<00:05:39.889> under<00:05:40.069> all<00:05:40.249> about<00:05:40.490> the 00:05:40.600 --> 00:05:40.610 align:start position:0% read Forbes magazine under all about the 00:05:40.610 --> 00:05:44.409 align:start position:0% read Forbes magazine under all about the options<00:05:42.129> and<00:05:43.129> so<00:05:43.400> because<00:05:43.729> they<00:05:43.879> are<00:05:44.029> a<00:05:44.059> large 00:05:44.409 --> 00:05:44.419 align:start position:0% options and so because they are a large 00:05:44.419 --> 00:05:47.079 align:start position:0% options and so because they are a large digital<00:05:45.080> enterprise<00:05:45.860> of<00:05:46.370> got<00:05:46.639> all<00:05:46.849> that 00:05:47.079 --> 00:05:47.089 align:start position:0% digital enterprise of got all that 00:05:47.089 --> 00:05:49.239 align:start position:0% digital enterprise of got all that legacy<00:05:47.389> applications<00:05:48.139> created<00:05:48.770> so<00:05:49.099> those 00:05:49.239 --> 00:05:49.249 align:start position:0% legacy applications created so those 00:05:49.249 --> 00:05:51.779 align:start position:0% legacy applications created so those used<00:05:49.430> to<00:05:49.490> go<00:05:49.669> as<00:05:49.849> traditional<00:05:50.539> multiplication 00:05:51.779 --> 00:05:51.789 align:start position:0% used to go as traditional multiplication 00:05:51.789 --> 00:05:57.040 align:start position:0% used to go as traditional multiplication so<00:05:52.789> if<00:05:53.089> we<00:05:53.210> go<00:05:53.389> with<00:05:53.900> typical<00:05:55.779> there<00:05:56.779> going<00:05:56.990> to 00:05:57.040 --> 00:05:57.050 align:start position:0% so if we go with typical there going to 00:05:57.050 --> 00:06:03.579 align:start position:0% so if we go with typical there going to be<00:05:57.110> one<00:05:57.650> really<00:05:58.370> large<00:05:58.520> company<00:06:02.229> so<00:06:03.229> making 00:06:03.579 --> 00:06:03.589 align:start position:0% be one really large company so making 00:06:03.589 --> 00:06:06.909 align:start position:0% be one really large company so making these<00:06:04.580> of<00:06:04.759> not<00:06:05.169> let's<00:06:06.169> just<00:06:06.229> go<00:06:06.439> with<00:06:06.589> Walmart 00:06:06.909 --> 00:06:06.919 align:start position:0% these of not let's just go with Walmart 00:06:06.919 --> 00:06:09.010 align:start position:0% these of not let's just go with Walmart everyone<00:06:07.490> knows<00:06:07.699> that<00:06:07.729> and<00:06:08.210> supplies<00:06:08.689> to<00:06:08.719> for 00:06:09.010 --> 00:06:09.020 align:start position:0% everyone knows that and supplies to for 00:06:09.020 --> 00:06:11.019 align:start position:0% everyone knows that and supplies to for money<00:06:09.259> so<00:06:10.159> typically<00:06:10.520> what<00:06:10.699> what<00:06:10.939> would 00:06:11.019 --> 00:06:11.029 align:start position:0% money so typically what what would 00:06:11.029 --> 00:06:11.589 align:start position:0% money so typically what what would happen 00:06:11.589 --> 00:06:11.599 align:start position:0% happen 00:06:11.599 --> 00:06:14.379 align:start position:0% happen Walmart<00:06:12.050> the<00:06:12.199> largest<00:06:12.499> player<00:06:12.740> in<00:06:12.770> this<00:06:12.979> place 00:06:14.379 --> 00:06:14.389 align:start position:0% Walmart the largest player in this place 00:06:14.389 --> 00:06:16.719 align:start position:0% Walmart the largest player in this place all<00:06:14.689> of<00:06:14.930> these<00:06:15.080> supplies<00:06:15.800> are<00:06:15.919> going<00:06:16.580> and 00:06:16.719 --> 00:06:16.729 align:start position:0% all of these supplies are going and 00:06:16.729 --> 00:06:18.999 align:start position:0% all of these supplies are going and supplying<00:06:17.089> packages<00:06:17.749> to<00:06:17.930> them<00:06:18.169> but<00:06:18.830> because 00:06:18.999 --> 00:06:19.009 align:start position:0% supplying packages to them but because 00:06:19.009 --> 00:06:21.249 align:start position:0% supplying packages to them but because we'll<00:06:19.309> have<00:06:19.339> to<00:06:19.699> be<00:06:19.849> playing<00:06:20.210> if<00:06:20.479> they<00:06:20.960> can<00:06:21.169> go 00:06:21.249 --> 00:06:21.259 align:start position:0% we'll have to be playing if they can go 00:06:21.259 --> 00:06:23.200 align:start position:0% we'll have to be playing if they can go dictates<00:06:21.800> of<00:06:21.979> all<00:06:22.099> of<00:06:22.279> these<00:06:22.370> normal<00:06:22.789> players 00:06:23.200 --> 00:06:23.210 align:start position:0% dictates of all of these normal players 00:06:23.210 --> 00:06:24.730 align:start position:0% dictates of all of these normal players what<00:06:23.659> are<00:06:23.779> you<00:06:23.930> going<00:06:24.080> to<00:06:24.139> log<00:06:24.319> into<00:06:24.499> our 00:06:24.730 --> 00:06:24.740 align:start position:0% what are you going to log into our 00:06:24.740 --> 00:06:27.010 align:start position:0% what are you going to log into our front-end<00:06:25.610> web<00:06:25.819> portal<00:06:26.300> or<00:06:26.539> if<00:06:26.629> you<00:06:26.779> go<00:06:26.990> to 00:06:27.010 --> 00:06:27.020 align:start position:0% front-end web portal or if you go to 00:06:27.020 --> 00:06:29.829 align:start position:0% front-end web portal or if you go to update<00:06:27.349> to<00:06:27.889> them<00:06:28.129> so<00:06:28.969> Walmart<00:06:29.180> in<00:06:29.539> the<00:06:29.629> back 00:06:29.829 --> 00:06:29.839 align:start position:0% update to them so Walmart in the back 00:06:29.839 --> 00:06:33.040 align:start position:0% update to them so Walmart in the back end<00:06:30.139> and<00:06:30.289> have<00:06:30.529> their<00:06:30.800> business<00:06:31.639> here<00:06:31.909> but<00:06:32.779> got 00:06:33.040 --> 00:06:33.050 align:start position:0% end and have their business here but got 00:06:33.050 --> 00:06:34.839 align:start position:0% end and have their business here but got the<00:06:33.229> image<00:06:33.709> here<00:06:33.919> with<00:06:34.129> database<00:06:34.580> their 00:06:34.839 --> 00:06:34.849 align:start position:0% the image here with database their 00:06:34.849 --> 00:06:36.999 align:start position:0% the image here with database their traditional<00:06:35.300> degree<00:06:35.509> to<00:06:36.020> application<00:06:36.740> and 00:06:36.999 --> 00:06:37.009 align:start position:0% traditional degree to application and 00:06:37.009 --> 00:06:39.100 align:start position:0% traditional degree to application and they<00:06:37.490> might<00:06:37.669> have<00:06:37.879> some<00:06:37.999> analytics<00:06:38.569> reporting 00:06:39.100 --> 00:06:39.110 align:start position:0% they might have some analytics reporting 00:06:39.110 --> 00:06:39.850 align:start position:0% they might have some analytics reporting or<00:06:39.259> something 00:06:39.850 --> 00:06:39.860 align:start position:0% or something 00:06:39.860 --> 00:06:41.860 align:start position:0% or something so<00:06:40.069> because<00:06:40.550> of<00:06:40.580> reading<00:06:40.999> couple<00:06:41.449> is<00:06:41.659> in<00:06:41.839> a 00:06:41.860 --> 00:06:41.870 align:start position:0% so because of reading couple is in a 00:06:41.870 --> 00:06:47.080 align:start position:0% so because of reading couple is in a legacy<00:06:42.620> enterprise<00:06:43.129> infrastructure 00:06:47.080 --> 00:06:47.090 align:start position:0% 00:06:47.090 --> 00:06:49.240 align:start position:0% that<00:06:47.690> fable<00:06:48.139> there<00:06:48.380> you<00:06:48.470> go<00:06:48.590> we<00:06:48.830> want<00:06:49.040> to<00:06:49.130> make 00:06:49.240 --> 00:06:49.250 align:start position:0% that fable there you go we want to make 00:06:49.250 --> 00:06:51.490 align:start position:0% that fable there you go we want to make this<00:06:49.370> more<00:06:49.550> secure<00:06:50.000> but<00:06:50.510> making<00:06:51.080> a<00:06:51.139> blockchain 00:06:51.490 --> 00:06:51.500 align:start position:0% this more secure but making a blockchain 00:06:51.500 --> 00:06:53.890 align:start position:0% this more secure but making a blockchain instead<00:06:52.100> all<00:06:52.669> they<00:06:52.820> do<00:06:53.030> is<00:06:53.270> they<00:06:53.389> take<00:06:53.690> that 00:06:53.890 --> 00:06:53.900 align:start position:0% instead all they do is they take that 00:06:53.900 --> 00:06:58.270 align:start position:0% instead all they do is they take that data<00:06:54.110> bit<00:06:54.380> and<00:06:54.949> they<00:06:56.530> replace<00:06:57.530> that<00:06:57.830> with 00:06:58.270 --> 00:06:58.280 align:start position:0% data bit and they replace that with 00:06:58.280 --> 00:07:01.030 align:start position:0% data bit and they replace that with watching<00:06:58.790> they<00:06:59.330> go<00:06:59.510> now<00:06:59.870> all<00:07:00.229> secure<00:07:00.680> that's 00:07:01.030 --> 00:07:01.040 align:start position:0% watching they go now all secure that's 00:07:01.040 --> 00:07:03.219 align:start position:0% watching they go now all secure that's not<00:07:01.190> watching<00:07:01.610> and<00:07:02.360> we<00:07:02.630> tell<00:07:02.840> them<00:07:02.960> no<00:07:03.169> you 00:07:03.219 --> 00:07:03.229 align:start position:0% not watching and we tell them no you 00:07:03.229 --> 00:07:06.969 align:start position:0% not watching and we tell them no you just<00:07:03.500> made<00:07:03.830> it<00:07:04.460> work<00:07:05.590> you<00:07:06.590> made<00:07:06.800> it 00:07:06.969 --> 00:07:06.979 align:start position:0% just made it work you made it 00:07:06.979 --> 00:07:09.760 align:start position:0% just made it work you made it taken<00:07:07.520> the<00:07:07.610> worst<00:07:07.850> party<00:07:08.540> boat<00:07:08.750> so<00:07:09.470> all<00:07:09.650> of 00:07:09.760 --> 00:07:09.770 align:start position:0% taken the worst party boat so all of 00:07:09.770 --> 00:07:11.290 align:start position:0% taken the worst party boat so all of them<00:07:09.919> got<00:07:10.190> now<00:07:10.400> is<00:07:10.460> it<00:07:10.699> exact<00:07:11.120> same 00:07:11.290 --> 00:07:11.300 align:start position:0% them got now is it exact same 00:07:11.300 --> 00:07:13.540 align:start position:0% them got now is it exact same application<00:07:12.020> which<00:07:12.500> is<00:07:12.620> now<00:07:12.740> a<00:07:12.770> whole<00:07:13.190> lot 00:07:13.540 --> 00:07:13.550 align:start position:0% application which is now a whole lot 00:07:13.550 --> 00:07:15.610 align:start position:0% application which is now a whole lot slower<00:07:13.970> than<00:07:14.479> what<00:07:14.660> their<00:07:14.870> sequel<00:07:15.229> database 00:07:15.610 --> 00:07:15.620 align:start position:0% slower than what their sequel database 00:07:15.620 --> 00:07:20.379 align:start position:0% slower than what their sequel database cool<00:07:15.889> is<00:07:16.010> it<00:07:16.360> and<00:07:17.360> then<00:07:17.990> think<00:07:18.850> yeah<00:07:19.850> sorry 00:07:20.379 --> 00:07:20.389 align:start position:0% cool is it and then think yeah sorry 00:07:20.389 --> 00:07:22.030 align:start position:0% cool is it and then think yeah sorry everything<00:07:20.810> is<00:07:20.900> now<00:07:21.020> a<00:07:21.050> few<00:07:21.320> minor<00:07:21.500> firewall 00:07:22.030 --> 00:07:22.040 align:start position:0% everything is now a few minor firewall 00:07:22.040 --> 00:07:24.280 align:start position:0% everything is now a few minor firewall so<00:07:22.370> none<00:07:22.610> of<00:07:22.639> these<00:07:22.790> parties<00:07:23.630> came<00:07:23.810> to<00:07:23.930> access 00:07:24.280 --> 00:07:24.290 align:start position:0% so none of these parties came to access 00:07:24.290 --> 00:07:28.090 align:start position:0% so none of these parties came to access that<00:07:24.470> watching<00:07:25.220> so<00:07:25.940> I<00:07:25.970> asked<00:07:26.540> him<00:07:26.690> so<00:07:27.500> anything 00:07:28.090 --> 00:07:28.100 align:start position:0% that watching so I asked him so anything 00:07:28.100 --> 00:07:30.580 align:start position:0% that watching so I asked him so anything who<00:07:28.790> wasn't<00:07:29.150> going<00:07:29.270> to<00:07:29.510> post<00:07:29.870> this<00:07:30.080> blockchain 00:07:30.580 --> 00:07:30.590 align:start position:0% who wasn't going to post this blockchain 00:07:30.590 --> 00:07:33.340 align:start position:0% who wasn't going to post this blockchain no<00:07:31.010> one<00:07:31.220> we<00:07:31.550> control<00:07:32.090> the<00:07:32.180> blockchain<00:07:32.479> it 00:07:33.340 --> 00:07:33.350 align:start position:0% no one we control the blockchain it 00:07:33.350 --> 00:07:36.129 align:start position:0% no one we control the blockchain it doesn't<00:07:33.620> work<00:07:33.740> like<00:07:33.770> that<00:07:33.950> guys<00:07:34.810> so<00:07:35.810> then<00:07:36.020> we 00:07:36.129 --> 00:07:36.139 align:start position:0% doesn't work like that guys so then we 00:07:36.139 --> 00:07:38.890 align:start position:0% doesn't work like that guys so then we say<00:07:36.380> okay<00:07:36.889> so<00:07:36.950> if<00:07:37.430> you're<00:07:37.610> not<00:07:37.729> going<00:07:38.030> to<00:07:38.240> even 00:07:38.890 --> 00:07:38.900 align:start position:0% say okay so if you're not going to even 00:07:38.900 --> 00:07:41.629 align:start position:0% say okay so if you're not going to even let<00:07:39.260> them<00:07:39.410> host<00:07:39.710> it<00:07:40.070> and 00:07:41.629 --> 00:07:41.639 align:start position:0% let them host it and 00:07:41.639 --> 00:07:43.909 align:start position:0% let them host it and have<00:07:42.240> I<00:07:42.389> had<00:07:42.569> direct<00:07:42.900> time<00:07:43.110> and<00:07:43.349> points<00:07:43.770> of 00:07:43.909 --> 00:07:43.919 align:start position:0% have I had direct time and points of 00:07:43.919 --> 00:07:45.619 align:start position:0% have I had direct time and points of change<00:07:44.430> that<00:07:44.580> I<00:07:44.669> can<00:07:44.819> leave<00:07:44.999> serve<00:07:45.300> my<00:07:45.599> own 00:07:45.619 --> 00:07:45.629 align:start position:0% change that I can leave serve my own 00:07:45.629 --> 00:07:48.260 align:start position:0% change that I can leave serve my own limits<00:07:46.139> behind<00:07:46.439> a<00:07:46.499> firewall<00:07:46.800> so<00:07:47.729> you<00:07:47.789> guys<00:07:48.030> are 00:07:48.260 --> 00:07:48.270 align:start position:0% limits behind a firewall so you guys are 00:07:48.270 --> 00:07:52.010 align:start position:0% limits behind a firewall so you guys are right<00:07:48.449> a<00:07:48.749> blockchain<00:07:49.199> your<00:07:50.090> your<00:07:51.090> reign<00:07:51.389> the 00:07:52.010 --> 00:07:52.020 align:start position:0% right a blockchain your your reign the 00:07:52.020 --> 00:07:53.899 align:start position:0% right a blockchain your your reign the blockchain<00:07:52.319> you're<00:07:52.949> the<00:07:53.099> only<00:07:53.430> one<00:07:53.610> who's 00:07:53.899 --> 00:07:53.909 align:start position:0% blockchain you're the only one who's 00:07:53.909 --> 00:07:55.550 align:start position:0% blockchain you're the only one who's even<00:07:54.270> though<00:07:54.419> and<00:07:54.779> it<00:07:54.870> can<00:07:55.050> be<00:07:55.199> kind<00:07:55.379> of 00:07:55.550 --> 00:07:55.560 align:start position:0% even though and it can be kind of 00:07:55.560 --> 00:07:59.929 align:start position:0% even though and it can be kind of firewater<00:07:56.039> not<00:07:56.340> access<00:07:56.990> so<00:07:58.400> you<00:07:59.400> can't<00:07:59.639> prove 00:07:59.929 --> 00:07:59.939 align:start position:0% firewater not access so you can't prove 00:07:59.939 --> 00:08:02.540 align:start position:0% firewater not access so you can't prove anything<00:08:00.229> because<00:08:01.229> right<00:08:01.560> now<00:08:01.770> it<00:08:02.310> may<00:08:02.520> be 00:08:02.540 --> 00:08:02.550 align:start position:0% anything because right now it may be 00:08:02.550 --> 00:08:04.999 align:start position:0% anything because right now it may be secured<00:08:03.449> in<00:08:03.509> a<00:08:03.599> blockchain<00:08:03.900> that<00:08:04.529> they<00:08:04.680> can't 00:08:04.999 --> 00:08:05.009 align:start position:0% secured in a blockchain that they can't 00:08:05.009 --> 00:08:07.189 align:start position:0% secured in a blockchain that they can't tell<00:08:05.249> because<00:08:05.789> whenever<00:08:06.240> it<00:08:06.419> comes<00:08:06.599> in 00:08:07.189 --> 00:08:07.199 align:start position:0% tell because whenever it comes in 00:08:07.199 --> 00:08:09.350 align:start position:0% tell because whenever it comes in transit<00:08:07.680> it's<00:08:08.039> doing<00:08:08.370> modified<00:08:08.789> in<00:08:08.999> any<00:08:09.210> of 00:08:09.350 --> 00:08:09.360 align:start position:0% transit it's doing modified in any of 00:08:09.360 --> 00:08:11.450 align:start position:0% transit it's doing modified in any of these<00:08:09.509> deities<00:08:10.139> before<00:08:10.680> it<00:08:10.770> gets<00:08:10.919> out<00:08:11.099> to<00:08:11.219> here 00:08:11.450 --> 00:08:11.460 align:start position:0% these deities before it gets out to here 00:08:11.460 --> 00:08:14.990 align:start position:0% these deities before it gets out to here and<00:08:11.999> so<00:08:12.210> the<00:08:12.659> biggest<00:08:13.020> thing<00:08:13.169> that<00:08:14.000> the 00:08:14.990 --> 00:08:15.000 align:start position:0% and so the biggest thing that the 00:08:15.000 --> 00:08:15.980 align:start position:0% and so the biggest thing that the biggest<00:08:15.300> challenge<00:08:15.509> we<00:08:15.779> have<00:08:15.960> with 00:08:15.980 --> 00:08:15.990 align:start position:0% biggest challenge we have with 00:08:15.990 --> 00:08:18.999 align:start position:0% biggest challenge we have with enterprise<00:08:16.289> is<00:08:16.740> that<00:08:17.009> education<00:08:17.189> around 00:08:18.999 --> 00:08:19.009 align:start position:0% enterprise is that education around 00:08:19.009 --> 00:08:21.890 align:start position:0% enterprise is that education around every<00:08:20.009> every<00:08:20.370> single<00:08:20.909> party<00:08:21.330> has<00:08:21.569> to<00:08:21.689> be<00:08:21.779> how 00:08:21.890 --> 00:08:21.900 align:start position:0% every every single party has to be how 00:08:21.900 --> 00:08:23.510 align:start position:0% every every single party has to be how to<00:08:21.930> access<00:08:22.259> the<00:08:22.500> blockchain<00:08:22.710> directly<00:08:23.370> to 00:08:23.510 --> 00:08:23.520 align:start position:0% to access the blockchain directly to 00:08:23.520 --> 00:08:25.640 align:start position:0% to access the blockchain directly to verify<00:08:24.060> it<00:08:24.120> if<00:08:24.840> you<00:08:24.990> still<00:08:25.199> go<00:08:25.349> through<00:08:25.379> a 00:08:25.640 --> 00:08:25.650 align:start position:0% verify it if you still go through a 00:08:25.650 --> 00:08:28.219 align:start position:0% verify it if you still go through a centralized<00:08:26.310> access<00:08:26.580> point<00:08:27.029> like<00:08:27.180> this<00:08:27.449> and 00:08:28.219 --> 00:08:28.229 align:start position:0% centralized access point like this and 00:08:28.229 --> 00:08:30.529 align:start position:0% centralized access point like this and it<00:08:28.500> has<00:08:28.529> absolutely<00:08:28.860> no<00:08:29.310> value<00:08:29.539> there's 00:08:30.529 --> 00:08:30.539 align:start position:0% it has absolutely no value there's 00:08:30.539 --> 00:08:33.079 align:start position:0% it has absolutely no value there's always<00:08:30.719> a<00:08:30.840> deep<00:08:31.080> trouble<00:08:31.529> because<00:08:31.789> the<00:08:32.789> light 00:08:33.079 --> 00:08:33.089 align:start position:0% always a deep trouble because the light 00:08:33.089 --> 00:08:34.969 align:start position:0% always a deep trouble because the light is<00:08:33.120> playing<00:08:33.510> here<00:08:33.899> but<00:08:34.110> wants<00:08:34.440> to<00:08:34.560> still<00:08:34.800> look 00:08:34.969 --> 00:08:34.979 align:start position:0% is playing here but wants to still look 00:08:34.979 --> 00:08:37.250 align:start position:0% is playing here but wants to still look down<00:08:35.010> and<00:08:35.310> control<00:08:35.669> everything<00:08:36.060> so<00:08:36.539> trying<00:08:37.199> to 00:08:37.250 --> 00:08:37.260 align:start position:0% down and control everything so trying to 00:08:37.260 --> 00:08:38.110 align:start position:0% down and control everything so trying to get<00:08:37.380> them<00:08:37.500> down 00:08:38.110 --> 00:08:38.120 align:start position:0% get them down 00:08:38.120 --> 00:08:39.459 align:start position:0% get them down you<00:08:38.209> can't<00:08:38.449> control<00:08:38.809> the<00:08:39.229> blockchain 00:08:39.459 --> 00:08:39.469 align:start position:0% you can't control the blockchain 00:08:39.469 --> 00:08:41.829 align:start position:0% you can't control the blockchain everyone<00:08:40.399> needs<00:08:40.579> the<00:08:40.699> festive<00:08:41.120> that's 00:08:41.829 --> 00:08:41.839 align:start position:0% everyone needs the festive that's 00:08:41.839 --> 00:08:45.910 align:start position:0% everyone needs the festive that's usually<00:08:42.050> a<00:08:42.229> scary<00:08:42.699> important<00:08:44.499> so<00:08:45.499> the<00:08:45.680> common 00:08:45.910 --> 00:08:45.920 align:start position:0% usually a scary important so the common 00:08:45.920 --> 00:08:48.759 align:start position:0% usually a scary important so the common mistakes<00:08:46.279> I<00:08:46.610> usually<00:08:46.939> see<00:08:47.180> what<00:08:47.990> we<00:08:48.079> do<00:08:48.199> so<00:08:48.379> far 00:08:48.759 --> 00:08:48.769 align:start position:0% mistakes I usually see what we do so far 00:08:48.769 --> 00:08:51.309 align:start position:0% mistakes I usually see what we do so far they<00:08:49.550> have<00:08:49.699> a<00:08:49.730> 3d<00:08:50.029> application<00:08:50.809> they're<00:08:51.170> used 00:08:51.309 --> 00:08:51.319 align:start position:0% they have a 3d application they're used 00:08:51.319 --> 00:08:52.720 align:start position:0% they have a 3d application they're used to<00:08:51.410> they<00:08:51.680> are<00:08:51.860> they<00:08:52.009> want<00:08:52.160> to<00:08:52.370> control 00:08:52.720 --> 00:08:52.730 align:start position:0% to they are they want to control 00:08:52.730 --> 00:08:55.299 align:start position:0% to they are they want to control everything<00:08:53.329> propose<00:08:53.899> everything<00:08:54.499> for<00:08:55.069> the 00:08:55.299 --> 00:08:55.309 align:start position:0% everything propose everything for the 00:08:55.309 --> 00:08:57.249 align:start position:0% everything propose everything for the industry<00:08:55.730> they<00:08:56.629> want<00:08:56.749> to<00:08:56.899> use<00:08:56.990> a<00:08:57.019> block 00:08:57.249 --> 00:08:57.259 align:start position:0% industry they want to use a block 00:08:57.259 --> 00:08:59.379 align:start position:0% industry they want to use a block transit<00:08:57.709> database<00:08:58.009> to<00:08:58.730> try<00:08:58.939> and<00:08:59.059> get<00:08:59.209> them 00:08:59.379 --> 00:08:59.389 align:start position:0% transit database to try and get them 00:08:59.389 --> 00:09:01.090 align:start position:0% transit database to try and get them moving<00:08:59.600> with<00:08:59.959> their<00:09:00.110> bare<00:09:00.259> hands<00:09:00.410> get<00:09:00.680> out<00:09:00.920> of 00:09:01.090 --> 00:09:01.100 align:start position:0% moving with their bare hands get out of 00:09:01.100 --> 00:09:04.299 align:start position:0% moving with their bare hands get out of we<00:09:01.579> have<00:09:01.759> a<00:09:02.059> database<00:09:02.509> that<00:09:02.660> we<00:09:03.110> control<00:09:03.470> -<00:09:04.040> we 00:09:04.299 --> 00:09:04.309 align:start position:0% we have a database that we control - we 00:09:04.309 --> 00:09:05.739 align:start position:0% we have a database that we control - we have<00:09:04.490> a<00:09:04.519> shared<00:09:04.910> state<00:09:05.269> for<00:09:05.480> shared 00:09:05.739 --> 00:09:05.749 align:start position:0% have a shared state for shared 00:09:05.749 --> 00:09:07.600 align:start position:0% have a shared state for shared understanding<00:09:06.410> between<00:09:06.559> all<00:09:06.889> parties<00:09:07.339> that 00:09:07.600 --> 00:09:07.610 align:start position:0% understanding between all parties that 00:09:07.610 --> 00:09:10.389 align:start position:0% understanding between all parties that speakers<00:09:08.329> might<00:09:08.540> shift<00:09:08.779> but<00:09:09.589> once<00:09:09.800> we<00:09:10.009> get 00:09:10.389 --> 00:09:10.399 align:start position:0% speakers might shift but once we get 00:09:10.399 --> 00:09:12.160 align:start position:0% speakers might shift but once we get through<00:09:10.759> that<00:09:10.970> usually<00:09:11.480> takes<00:09:11.689> about<00:09:11.839> two 00:09:12.160 --> 00:09:12.170 align:start position:0% through that usually takes about two 00:09:12.170 --> 00:09:15.069 align:start position:0% through that usually takes about two days<00:09:12.199> one<00:09:12.829> speeding<00:09:13.160> it<00:09:13.819> with<00:09:13.999> interest<00:09:14.300> and 00:09:15.069 --> 00:09:15.079 align:start position:0% days one speeding it with interest and 00:09:15.079 --> 00:09:16.689 align:start position:0% days one speeding it with interest and you<00:09:15.350> can<00:09:15.529> see<00:09:15.649> them<00:09:15.800> get<00:09:15.949> excited<00:09:15.980> with<00:09:16.490> now 00:09:16.689 --> 00:09:16.699 align:start position:0% you can see them get excited with now 00:09:16.699 --> 00:09:22.929 align:start position:0% you can see them get excited with now they<00:09:16.910> understand<00:09:20.649> and<00:09:21.649> it<00:09:22.279> would<00:09:22.399> still<00:09:22.639> be 00:09:22.929 --> 00:09:22.939 align:start position:0% they understand and it would still be 00:09:22.939 --> 00:09:28.530 align:start position:0% they understand and it would still be problem<00:09:23.420> why<00:09:23.689> these<00:09:23.749> company 00:09:28.530 --> 00:09:28.540 align:start position:0% 00:09:28.540 --> 00:09:31.360 align:start position:0% so<00:09:29.540> how<00:09:30.200> do<00:09:30.260> we<00:09:30.320> go<00:09:30.500> about<00:09:30.620> hoping<00:09:31.160> to<00:09:31.279> educate 00:09:31.360 --> 00:09:31.370 align:start position:0% so how do we go about hoping to educate 00:09:31.370 --> 00:09:35.500 align:start position:0% so how do we go about hoping to educate them<00:09:32.770> if<00:09:33.770> they're<00:09:34.010> to<00:09:34.100> go<00:09:34.250> that<00:09:34.550> much<00:09:34.880> changes 00:09:35.500 --> 00:09:35.510 align:start position:0% them if they're to go that much changes 00:09:35.510 --> 00:09:37.210 align:start position:0% them if they're to go that much changes the<00:09:35.720> source<00:09:35.960> of<00:09:36.110> material<00:09:36.500> so<00:09:36.740> it's<00:09:36.920> no<00:09:37.040> longer 00:09:37.210 --> 00:09:37.220 align:start position:0% the source of material so it's no longer 00:09:37.220 --> 00:09:39.790 align:start position:0% the source of material so it's no longer your<00:09:37.910> Bacchus<00:09:38.300> systems<00:09:39.230> are<00:09:39.350> the<00:09:39.470> source<00:09:39.680> of 00:09:39.790 --> 00:09:39.800 align:start position:0% your Bacchus systems are the source of 00:09:39.800 --> 00:09:41.560 align:start position:0% your Bacchus systems are the source of truth<00:09:40.010> one<00:09:40.670> isn't<00:09:40.940> the<00:09:41.000> blockchain<00:09:41.210> is<00:09:41.540> a 00:09:41.560 --> 00:09:41.570 align:start position:0% truth one isn't the blockchain is a 00:09:41.570 --> 00:09:43.360 align:start position:0% truth one isn't the blockchain is a slice<00:09:41.839> of<00:09:41.870> truth<00:09:42.140> which<00:09:42.589> again<00:09:42.860> another 00:09:43.360 --> 00:09:43.370 align:start position:0% slice of truth which again another 00:09:43.370 --> 00:09:49.660 align:start position:0% slice of truth which again another mindset<00:09:43.810> might<00:09:44.810> entice<00:09:47.860> kids<00:09:48.860> understand 00:09:49.660 --> 00:09:49.670 align:start position:0% mindset might entice kids understand 00:09:49.670 --> 00:09:52.090 align:start position:0% mindset might entice kids understand that<00:09:49.850> yeah<00:09:50.480> that<00:09:50.510> consider<00:09:51.110> going<00:09:51.529> to<00:09:51.650> react 00:09:52.090 --> 00:09:52.100 align:start position:0% that yeah that consider going to react 00:09:52.100 --> 00:09:55.510 align:start position:0% that yeah that consider going to react what<00:09:52.610> has<00:09:52.760> happened<00:09:53.180> in<00:09:53.920> chamber<00:09:54.920> Oracle's 00:09:55.510 --> 00:09:55.520 align:start position:0% what has happened in chamber Oracle's 00:09:55.520 --> 00:09:57.790 align:start position:0% what has happened in chamber Oracle's and<00:09:56.029> again<00:09:56.330> it's<00:09:56.450> another<00:09:56.660> mindset<00:09:56.930> shift<00:09:57.470> but 00:09:57.790 --> 00:09:57.800 align:start position:0% and again it's another mindset shift but 00:09:57.800 --> 00:09:59.380 align:start position:0% and again it's another mindset shift but you<00:09:57.890> can't<00:09:58.040> tell<00:09:58.279> them<00:09:58.430> nothing's<00:09:59.150> confirmed 00:09:59.380 --> 00:09:59.390 align:start position:0% you can't tell them nothing's confirmed 00:09:59.390 --> 00:10:01.900 align:start position:0% you can't tell them nothing's confirmed we've<00:10:00.020> sent<00:10:00.260> it<00:10:00.380> into<00:10:00.710> the<00:10:00.890> shared<00:10:01.160> state<00:10:01.460> this 00:10:01.900 --> 00:10:01.910 align:start position:0% we've sent it into the shared state this 00:10:01.910 --> 00:10:04.240 align:start position:0% we've sent it into the shared state this headset<00:10:02.360> is<00:10:02.420> updated<00:10:03.020> and<00:10:03.320> has<00:10:03.680> come<00:10:03.950> back<00:10:04.130> to 00:10:04.240 --> 00:10:04.250 align:start position:0% headset is updated and has come back to 00:10:04.250 --> 00:10:05.890 align:start position:0% headset is updated and has come back to buy<00:10:04.370> an<00:10:04.520> Oracle<00:10:04.910> scheme<00:10:05.120> and<00:10:05.300> a<00:10:05.390> potato<00:10:05.750> you 00:10:05.890 --> 00:10:05.900 align:start position:0% buy an Oracle scheme and a potato you 00:10:05.900 --> 00:10:13.350 align:start position:0% buy an Oracle scheme and a potato you will<00:10:06.020> back<00:10:06.200> into<00:10:06.589> your<00:10:06.710> recording<00:10:07.190> systems 00:10:13.350 --> 00:10:13.360 align:start position:0% 00:10:13.360 --> 00:10:17.670 align:start position:0% this<00:10:14.360> one<00:10:14.570> is<00:10:14.810> from<00:10:15.710> what<00:10:15.980> we've<00:10:16.160> seen<00:10:16.339> on<00:10:16.640> many 00:10:17.670 --> 00:10:17.680 align:start position:0% this one is from what we've seen on many 00:10:17.680 --> 00:10:22.030 align:start position:0% this one is from what we've seen on many projects<00:10:18.680> file<00:10:19.070> would<00:10:19.850> have<00:10:20.089> one<00:10:20.960> party<00:10:21.440> one 00:10:22.030 --> 00:10:22.040 align:start position:0% projects file would have one party one 00:10:22.040 --> 00:10:24.700 align:start position:0% projects file would have one party one company<00:10:22.490> inside<00:10:23.000> of<00:10:23.150> an<00:10:23.240> industry<00:10:23.690> say<00:10:24.320> we<00:10:24.650> are 00:10:24.700 --> 00:10:24.710 align:start position:0% company inside of an industry say we are 00:10:24.710 --> 00:10:27.100 align:start position:0% company inside of an industry say we are going<00:10:24.830> to<00:10:25.010> go<00:10:25.130> and<00:10:25.310> create<00:10:25.430> D<00:10:26.150> blockchain<00:10:26.779> for 00:10:27.100 --> 00:10:27.110 align:start position:0% going to go and create D blockchain for 00:10:27.110 --> 00:10:29.980 align:start position:0% going to go and create D blockchain for supply<00:10:27.800> chain<00:10:27.830> D<00:10:28.400> block<00:10:28.640> chain<00:10:29.000> or<00:10:29.360> Apple<00:10:29.810> Z 00:10:29.980 --> 00:10:29.990 align:start position:0% supply chain D block chain or Apple Z 00:10:29.990 --> 00:10:32.500 align:start position:0% supply chain D block chain or Apple Z table<00:10:30.200> tank<00:10:30.440> whatever<00:10:30.830> so<00:10:31.580> every<00:10:32.120> time<00:10:32.360> we've 00:10:32.500 --> 00:10:32.510 align:start position:0% table tank whatever so every time we've 00:10:32.510 --> 00:10:35.170 align:start position:0% table tank whatever so every time we've seen<00:10:32.690> one<00:10:32.960> comfy<00:10:33.500> say<00:10:33.950> we're<00:10:34.490> going<00:10:34.700> to<00:10:34.880> create 00:10:35.170 --> 00:10:35.180 align:start position:0% seen one comfy say we're going to create 00:10:35.180 --> 00:10:36.730 align:start position:0% seen one comfy say we're going to create the<00:10:35.450> blockchain<00:10:35.720> and<00:10:35.960> then<00:10:36.320> we're<00:10:36.440> going<00:10:36.589> to 00:10:36.730 --> 00:10:36.740 align:start position:0% the blockchain and then we're going to 00:10:36.740 --> 00:10:39.290 align:start position:0% the blockchain and then we're going to roll<00:10:36.920> it<00:10:36.950> out<00:10:37.190> to<00:10:37.220> our<00:10:37.490> partners<00:10:37.670> if<00:10:38.300> it's<00:10:38.540> bail 00:10:39.290 --> 00:10:39.300 align:start position:0% roll it out to our partners if it's bail 00:10:39.300 --> 00:10:41.000 align:start position:0% roll it out to our partners if it's bail every<00:10:39.390> single<00:10:39.630> time<00:10:39.959> I've<00:10:40.290> never<00:10:40.529> seen<00:10:40.830> that 00:10:41.000 --> 00:10:41.010 align:start position:0% every single time I've never seen that 00:10:41.010 --> 00:10:43.610 align:start position:0% every single time I've never seen that way<00:10:41.279> why<00:10:42.240> don't<00:10:42.420> we<00:10:42.450> seen<00:10:42.690> it<00:10:42.810> work<00:10:42.990> is<00:10:43.260> when 00:10:43.610 --> 00:10:43.620 align:start position:0% way why don't we seen it work is when 00:10:43.620 --> 00:10:46.550 align:start position:0% way why don't we seen it work is when that<00:10:43.950> they<00:10:44.190> get<00:10:44.490> us<00:10:44.610> engaged<00:10:44.820> we'll<00:10:45.810> go<00:10:46.050> in<00:10:46.290> and 00:10:46.550 --> 00:10:46.560 align:start position:0% that they get us engaged we'll go in and 00:10:46.560 --> 00:10:47.990 align:start position:0% that they get us engaged we'll go in and we'll<00:10:46.620> say<00:10:46.890> what<00:10:47.100> are<00:10:47.279> you<00:10:47.459> going<00:10:47.670> to<00:10:47.850> be 00:10:47.990 --> 00:10:48.000 align:start position:0% we'll say what are you going to be 00:10:48.000 --> 00:10:49.519 align:start position:0% we'll say what are you going to be working<00:10:48.209> with<00:10:48.390> you<00:10:48.660> you<00:10:48.870> bring<00:10:49.140> in<00:10:49.260> at<00:10:49.500> least 00:10:49.519 --> 00:10:49.529 align:start position:0% working with you you bring in at least 00:10:49.529 --> 00:10:53.420 align:start position:0% working with you you bring in at least two<00:10:50.279> other<00:10:50.459> parties<00:10:50.940> for<00:10:51.600> an<00:10:51.839> expedient<00:10:52.279> to<00:10:53.279> go 00:10:53.420 --> 00:10:53.430 align:start position:0% two other parties for an expedient to go 00:10:53.430 --> 00:10:55.280 align:start position:0% two other parties for an expedient to go in<00:10:53.640> then<00:10:53.850> we've<00:10:54.149> got<00:10:54.420> at<00:10:54.630> least<00:10:54.720> three 00:10:55.280 --> 00:10:55.290 align:start position:0% in then we've got at least three 00:10:55.290 --> 00:10:56.900 align:start position:0% in then we've got at least three companies<00:10:55.860> are<00:10:56.040> going<00:10:56.190> to<00:10:56.250> be<00:10:56.399> part<00:10:56.730> of<00:10:56.790> that 00:10:56.900 --> 00:10:56.910 align:start position:0% companies are going to be part of that 00:10:56.910 --> 00:10:58.460 align:start position:0% companies are going to be part of that initial<00:10:57.329> development<00:10:57.720> that<00:10:58.140> initial 00:10:58.460 --> 00:10:58.470 align:start position:0% initial development that initial 00:10:58.470 --> 00:11:01.040 align:start position:0% initial development that initial deployment<00:10:58.680> it<00:10:59.610> was<00:10:59.820> the<00:11:00.000> same<00:11:00.329> thing<00:11:00.360> a<00:11:00.899> lot 00:11:01.040 --> 00:11:01.050 align:start position:0% deployment it was the same thing a lot 00:11:01.050 --> 00:11:03.949 align:start position:0% deployment it was the same thing a lot more<00:11:01.290> successful<00:11:02.329> because<00:11:03.329> that's<00:11:03.720> what<00:11:03.870> we 00:11:03.949 --> 00:11:03.959 align:start position:0% more successful because that's what we 00:11:03.959 --> 00:11:07.759 align:start position:0% more successful because that's what we do<00:11:04.079> have<00:11:04.260> three<00:11:04.470> companies<00:11:04.829> to<00:11:06.769> businesses 00:11:07.759 --> 00:11:07.769 align:start position:0% do have three companies to businesses 00:11:07.769 --> 00:11:09.829 align:start position:0% do have three companies to businesses into<00:11:08.279> the<00:11:08.370> development<00:11:08.880> it's<00:11:09.360> been<00:11:09.510> employed 00:11:09.829 --> 00:11:09.839 align:start position:0% into the development it's been employed 00:11:09.839 --> 00:11:15.350 align:start position:0% into the development it's been employed out<00:11:10.019> to<00:11:10.350> their<00:11:10.560> three<00:11:13.700> -<00:11:14.700> your<00:11:14.850> subscriptions 00:11:15.350 --> 00:11:15.360 align:start position:0% out to their three - your subscriptions 00:11:15.360 --> 00:11:19.639 align:start position:0% out to their three - your subscriptions to<00:11:16.230> the<00:11:16.560> kids<00:11:16.769> rolling<00:11:17.870> and<00:11:18.870> most<00:11:19.320> most 00:11:19.639 --> 00:11:19.649 align:start position:0% to the kids rolling and most most 00:11:19.649 --> 00:11:21.259 align:start position:0% to the kids rolling and most most importantly<00:11:20.220> it's<00:11:20.399> every<00:11:20.610> time<00:11:20.790> a<00:11:20.850> teaching 00:11:21.259 --> 00:11:21.269 align:start position:0% importantly it's every time a teaching 00:11:21.269 --> 00:11:24.290 align:start position:0% importantly it's every time a teaching them<00:11:21.529> it's<00:11:22.529> applicable<00:11:22.829> to<00:11:23.579> public<00:11:23.970> watch 00:11:24.290 --> 00:11:24.300 align:start position:0% them it's applicable to public watch 00:11:24.300 --> 00:11:25.970 align:start position:0% them it's applicable to public watch chains<00:11:24.570> so<00:11:25.260> everything<00:11:25.529> we're<00:11:25.649> teaching<00:11:25.829> them 00:11:25.970 --> 00:11:25.980 align:start position:0% chains so everything we're teaching them 00:11:25.980 --> 00:11:28.100 align:start position:0% chains so everything we're teaching them around<00:11:26.220> key<00:11:26.760> security<00:11:27.180> around<00:11:27.750> app 00:11:28.100 --> 00:11:28.110 align:start position:0% around key security around app 00:11:28.110 --> 00:11:30.920 align:start position:0% around key security around app development<00:11:28.560> Oracle<00:11:29.279> etc<00:11:29.820> works<00:11:30.480> inside<00:11:30.779> of 00:11:30.920 --> 00:11:30.930 align:start position:0% development Oracle etc works inside of 00:11:30.930 --> 00:11:33.920 align:start position:0% development Oracle etc works inside of the<00:11:30.990> private<00:11:31.380> space<00:11:31.470> but<00:11:31.920> my<00:11:32.910> super<00:11:33.420> defenders 00:11:33.920 --> 00:11:33.930 align:start position:0% the private space but my super defenders 00:11:33.930 --> 00:11:36.079 align:start position:0% the private space but my super defenders to<00:11:34.230> get<00:11:34.589> the<00:11:34.709> ball<00:11:34.920> out<00:11:34.950> steals<00:11:35.399> that<00:11:35.760> wants<00:11:35.970> it 00:11:36.079 --> 00:11:36.089 align:start position:0% to get the ball out steals that wants it 00:11:36.089 --> 00:11:38.600 align:start position:0% to get the ball out steals that wants it happy<00:11:36.390> within<00:11:36.959> the<00:11:37.140> b2b<00:11:37.410> space<00:11:37.589> that<00:11:38.279> can<00:11:38.430> take 00:11:38.600 --> 00:11:38.610 align:start position:0% happy within the b2b space that can take 00:11:38.610 --> 00:11:40.340 align:start position:0% happy within the b2b space that can take everything<00:11:39.089> that's<00:11:39.209> at<00:11:39.390> learn<00:11:39.600> to<00:11:39.810> stop<00:11:40.050> doing 00:11:40.340 --> 00:11:40.350 align:start position:0% everything that's at learn to stop doing 00:11:40.350 --> 00:11:43.310 align:start position:0% everything that's at learn to stop doing things<00:11:40.560> in<00:11:40.709> b2c<00:11:41.220> public<00:11:41.940> aetherium<00:11:42.450> so<00:11:43.050> we're 00:11:43.310 --> 00:11:43.320 align:start position:0% things in b2c public aetherium so we're 00:11:43.320 --> 00:11:45.440 align:start position:0% things in b2c public aetherium so we're talking<00:11:43.470> to<00:11:43.770> them<00:11:43.920> around<00:11:44.190> sure<00:11:44.940> we<00:11:45.300> could 00:11:45.440 --> 00:11:45.450 align:start position:0% talking to them around sure we could 00:11:45.450 --> 00:11:47.300 align:start position:0% talking to them around sure we could have<00:11:45.600> a<00:11:45.630> private<00:11:45.870> network<00:11:46.170> but<00:11:47.070> why<00:11:47.250> don't 00:11:47.300 --> 00:11:47.310 align:start position:0% have a private network but why don't 00:11:47.310 --> 00:11:49.579 align:start position:0% have a private network but why don't make<00:11:47.579> the<00:11:47.760> plasma<00:11:48.209> chamber<00:11:48.450> so<00:11:49.050> sniffs<00:11:49.380> the 00:11:49.579 --> 00:11:49.589 align:start position:0% make the plasma chamber so sniffs the 00:11:49.589 --> 00:11:51.019 align:start position:0% make the plasma chamber so sniffs the public<00:11:49.890> networks<00:11:50.250> we<00:11:50.459> can<00:11:50.490> do<00:11:50.730> some<00:11:51.000> more 00:11:51.019 --> 00:11:51.029 align:start position:0% public networks we can do some more 00:11:51.029 --> 00:11:53.420 align:start position:0% public networks we can do some more things<00:11:51.390> easier<00:11:52.079> from<00:11:52.200> there<00:11:52.260> so<00:11:53.010> to<00:11:53.070> change 00:11:53.420 --> 00:11:53.430 align:start position:0% things easier from there so to change 00:11:53.430 --> 00:11:56.199 align:start position:0% things easier from there so to change the<00:11:53.579> conversation<00:11:53.790> of<00:11:54.329> plasma<00:11:54.839> change<00:11:55.140> is 00:11:56.199 --> 00:11:56.209 align:start position:0% the conversation of plasma change is 00:11:56.209 --> 00:12:01.080 align:start position:0% the conversation of plasma change is working<00:11:57.209> well<00:11:58.970> so 00:12:01.080 --> 00:12:01.090 align:start position:0% working well so 00:12:01.090 --> 00:12:03.520 align:start position:0% working well so once<00:12:02.090> we've<00:12:02.300> gotten<00:12:02.630> past<00:12:02.810> that<00:12:03.050> point<00:12:03.290> and 00:12:03.520 --> 00:12:03.530 align:start position:0% once we've gotten past that point and 00:12:03.530 --> 00:12:05.520 align:start position:0% once we've gotten past that point and they<00:12:03.860> were<00:12:03.920> talking<00:12:04.340> about<00:12:04.460> architecture 00:12:05.520 --> 00:12:05.530 align:start position:0% they were talking about architecture 00:12:05.530 --> 00:12:08.370 align:start position:0% they were talking about architecture there's<00:12:06.530> a<00:12:06.590> few<00:12:06.830> little<00:12:07.490> pieces<00:12:07.730> that<00:12:07.880> we<00:12:08.150> use 00:12:08.370 --> 00:12:08.380 align:start position:0% there's a few little pieces that we use 00:12:08.380 --> 00:12:10.360 align:start position:0% there's a few little pieces that we use so<00:12:09.380> I'm<00:12:09.470> going<00:12:09.680> to<00:12:09.710> go<00:12:09.830> through<00:12:10.040> some<00:12:10.220> of<00:12:10.310> the 00:12:10.360 --> 00:12:10.370 align:start position:0% so I'm going to go through some of the 00:12:10.370 --> 00:12:13.090 align:start position:0% so I'm going to go through some of the service<00:12:11.020> pieces<00:12:12.020> that<00:12:12.140> I<00:12:12.170> usually<00:12:12.410> use<00:12:12.800> I'll 00:12:13.090 --> 00:12:13.100 align:start position:0% service pieces that I usually use I'll 00:12:13.100 --> 00:12:15.130 align:start position:0% service pieces that I usually use I'll click<00:12:13.310> over<00:12:13.460> to<00:12:13.670> help<00:12:14.060> repair<00:12:14.330> my<00:12:14.480> own<00:12:14.630> bunch 00:12:15.130 --> 00:12:15.140 align:start position:0% click over to help repair my own bunch 00:12:15.140 --> 00:12:18.030 align:start position:0% click over to help repair my own bunch of<00:12:15.230> stuff<00:12:15.470> then<00:12:15.950> we'll<00:12:16.040> go<00:12:16.130> back<00:12:16.370> to<00:12:16.520> me<00:12:16.670> too 00:12:18.030 --> 00:12:18.040 align:start position:0% of stuff then we'll go back to me too 00:12:18.040 --> 00:12:21.850 align:start position:0% of stuff then we'll go back to me too but<00:12:19.330> to<00:12:20.330> connect<00:12:20.750> the<00:12:20.990> glue<00:12:21.290> between<00:12:21.590> the 00:12:21.850 --> 00:12:21.860 align:start position:0% but to connect the glue between the 00:12:21.860 --> 00:12:24.430 align:start position:0% but to connect the glue between the blood<00:12:22.340> change<00:12:22.610> side<00:12:22.880> and<00:12:23.180> the<00:12:23.870> traditional 00:12:24.430 --> 00:12:24.440 align:start position:0% blood change side and the traditional 00:12:24.440 --> 00:12:27.510 align:start position:0% blood change side and the traditional enterprise<00:12:24.980> of<00:12:25.130> Champions 00:12:27.510 --> 00:12:27.520 align:start position:0% enterprise of Champions 00:12:27.520 --> 00:12:30.460 align:start position:0% enterprise of Champions so<00:12:28.520> we've<00:12:28.790> got<00:12:29.000> two<00:12:29.570> of<00:12:29.600> them<00:12:29.840> which<00:12:30.230> are 00:12:30.460 --> 00:12:30.470 align:start position:0% so we've got two of them which are 00:12:30.470 --> 00:12:34.390 align:start position:0% so we've got two of them which are service<00:12:31.310> based<00:12:31.550> programming<00:12:32.050> we've<00:12:33.050> got<00:12:33.400> as 00:12:34.390 --> 00:12:34.400 align:start position:0% service based programming we've got as 00:12:34.400 --> 00:12:36.760 align:start position:0% service based programming we've got as your<00:12:34.610> functions<00:12:35.000> which<00:12:35.570> it<00:12:35.810> is<00:12:35.960> function<00:12:36.620> of 00:12:36.760 --> 00:12:36.770 align:start position:0% your functions which it is function of 00:12:36.770 --> 00:12:38.830 align:start position:0% your functions which it is function of the<00:12:36.860> service<00:12:37.220> so<00:12:37.490> take<00:12:37.730> a<00:12:37.760> piece<00:12:38.030> of<00:12:38.210> code<00:12:38.450> and 00:12:38.830 --> 00:12:38.840 align:start position:0% the service so take a piece of code and 00:12:38.840 --> 00:12:41.010 align:start position:0% the service so take a piece of code and it<00:12:39.320> will<00:12:39.350> run<00:12:39.590> into<00:12:39.830> service<00:12:40.280> style 00:12:41.010 --> 00:12:41.020 align:start position:0% it will run into service style 00:12:41.020 --> 00:12:42.910 align:start position:0% it will run into service style absolutely<00:12:42.020> that's<00:12:42.350> great 00:12:42.910 --> 00:12:42.920 align:start position:0% absolutely that's great 00:12:42.920 --> 00:12:46.330 align:start position:0% absolutely that's great we've<00:12:43.340> also<00:12:43.520> got<00:12:43.910> logic<00:12:44.570> apps<00:12:45.040> logic<00:12:46.040> capsule 00:12:46.330 --> 00:12:46.340 align:start position:0% we've also got logic apps logic capsule 00:12:46.340 --> 00:12:49.090 align:start position:0% we've also got logic apps logic capsule code<00:12:46.460> on<00:12:46.640> the<00:12:46.700> screen<00:12:46.820> in<00:12:47.090> a<00:12:47.180> second<00:12:47.540> so<00:12:48.080> it<00:12:48.590> is 00:12:49.090 --> 00:12:49.100 align:start position:0% code on the screen in a second so it is 00:12:49.100 --> 00:12:51.220 align:start position:0% code on the screen in a second so it is serve<00:12:49.790> Allah<00:12:50.060> screeches<00:12:50.510> but<00:12:50.870> you<00:12:50.960> don't<00:12:51.140> have 00:12:51.220 --> 00:12:51.230 align:start position:0% serve Allah screeches but you don't have 00:12:51.230 --> 00:12:52.780 align:start position:0% serve Allah screeches but you don't have to<00:12:51.350> write<00:12:51.530> a<00:12:51.560> code<00:12:51.800> you<00:12:52.010> can<00:12:52.160> just<00:12:52.190> drag<00:12:52.550> in 00:12:52.780 --> 00:12:52.790 align:start position:0% to write a code you can just drag in 00:12:52.790 --> 00:12:55.870 align:start position:0% to write a code you can just drag in building<00:12:53.510> blocks<00:12:53.980> and<00:12:54.980> then<00:12:55.160> the<00:12:55.250> last<00:12:55.400> one<00:12:55.700> is 00:12:55.870 --> 00:12:55.880 align:start position:0% building blocks and then the last one is 00:12:55.880 --> 00:12:57.360 align:start position:0% building blocks and then the last one is I've<00:12:56.150> been<00:12:56.420> through<00:12:56.630> which<00:12:56.810> is<00:12:56.960> an<00:12:57.050> enterprise 00:12:57.360 --> 00:12:57.370 align:start position:0% I've been through which is an enterprise 00:12:57.370 --> 00:12:59.940 align:start position:0% I've been through which is an enterprise pub/sub<00:12:58.400> so<00:12:58.970> that's<00:12:59.150> a<00:12:59.240> great<00:12:59.450> way<00:12:59.660> of 00:12:59.940 --> 00:12:59.950 align:start position:0% pub/sub so that's a great way of 00:12:59.950 --> 00:13:02.140 align:start position:0% pub/sub so that's a great way of publishing<00:13:00.950> make<00:13:01.310> something<00:13:01.700> happen<00:13:01.820> in<00:13:02.030> the 00:13:02.140 --> 00:13:02.150 align:start position:0% publishing make something happen in the 00:13:02.150 --> 00:13:04.480 align:start position:0% publishing make something happen in the blockchain<00:13:02.360> come<00:13:03.050> on<00:13:03.230> out<00:13:03.470> to<00:13:03.680> the<00:13:03.860> property 00:13:04.480 --> 00:13:04.490 align:start position:0% blockchain come on out to the property 00:13:04.490 --> 00:13:07.210 align:start position:0% blockchain come on out to the property event<00:13:05.270> group<00:13:05.480> and<00:13:05.870> any<00:13:06.260> back-end<00:13:06.560> systems<00:13:07.100> of 00:13:07.210 --> 00:13:07.220 align:start position:0% event group and any back-end systems of 00:13:07.220 --> 00:13:08.380 align:start position:0% event group and any back-end systems of care<00:13:07.400> that<00:13:07.550> something<00:13:07.910> happened<00:13:08.240> in<00:13:08.300> the 00:13:08.380 --> 00:13:08.390 align:start position:0% care that something happened in the 00:13:08.390 --> 00:13:10.030 align:start position:0% care that something happened in the blockchain<00:13:08.630> we<00:13:09.230> can<00:13:09.380> subscribe<00:13:09.740> to<00:13:09.770> those 00:13:10.030 --> 00:13:10.040 align:start position:0% blockchain we can subscribe to those 00:13:10.040 --> 00:13:12.010 align:start position:0% blockchain we can subscribe to those events<00:13:10.400> and<00:13:10.580> then<00:13:10.730> do<00:13:11.210> something<00:13:11.450> to<00:13:11.690> update 00:13:12.010 --> 00:13:12.020 align:start position:0% events and then do something to update 00:13:12.020 --> 00:13:15.420 align:start position:0% events and then do something to update the<00:13:12.170> reporting 00:13:15.420 --> 00:13:15.430 align:start position:0% 00:13:15.430 --> 00:13:22.090 align:start position:0% so<00:13:17.140> we<00:13:18.140> use<00:13:19.060> so<00:13:20.060> these<00:13:20.300> two<00:13:20.600> and<00:13:21.410> then<00:13:21.620> so 00:13:22.090 --> 00:13:22.100 align:start position:0% so we use so these two and then so 00:13:22.100 --> 00:13:24.810 align:start position:0% so we use so these two and then so between<00:13:22.700> these<00:13:22.910> two<00:13:23.120> if<00:13:23.420> we<00:13:23.600> have<00:13:23.750> to<00:13:23.899> do<00:13:24.410> some 00:13:24.810 --> 00:13:24.820 align:start position:0% between these two if we have to do some 00:13:24.820 --> 00:13:27.130 align:start position:0% between these two if we have to do some tricky<00:13:25.820> custom<00:13:26.209> stuff<00:13:26.420> in<00:13:26.630> his<00:13:26.720> function 00:13:27.130 --> 00:13:27.140 align:start position:0% tricky custom stuff in his function 00:13:27.140 --> 00:13:29.230 align:start position:0% tricky custom stuff in his function anything<00:13:28.040> simple<00:13:28.459> we<00:13:28.700> should<00:13:28.940> just<00:13:29.060> go<00:13:29.180> to 00:13:29.230 --> 00:13:29.240 align:start position:0% anything simple we should just go to 00:13:29.240 --> 00:13:31.420 align:start position:0% anything simple we should just go to logic<00:13:29.480> absolutely<00:13:30.260> get<00:13:30.350> it<00:13:30.529> done<00:13:30.740> in<00:13:30.920> 20 00:13:31.420 --> 00:13:31.430 align:start position:0% logic absolutely get it done in 20 00:13:31.430 --> 00:13:35.260 align:start position:0% logic absolutely get it done in 20 minutes<00:13:32.410> so<00:13:33.410> logic<00:13:33.709> apps<00:13:34.000> building<00:13:35.000> blocks 00:13:35.260 --> 00:13:35.270 align:start position:0% minutes so logic apps building blocks 00:13:35.270 --> 00:13:39.160 align:start position:0% minutes so logic apps building blocks you<00:13:35.390> quick<00:13:36.020> and<00:13:36.230> grab<00:13:36.440> things<00:13:36.950> on<00:13:37.130> there<00:13:38.170> so 00:13:39.160 --> 00:13:39.170 align:start position:0% you quick and grab things on there so 00:13:39.170 --> 00:13:41.079 align:start position:0% you quick and grab things on there so it's<00:13:39.800> great<00:13:39.980> because<00:13:40.250> when<00:13:40.490> we<00:13:40.610> jump<00:13:40.880> to<00:13:41.000> an 00:13:41.079 --> 00:13:41.089 align:start position:0% it's great because when we jump to an 00:13:41.089 --> 00:13:43.840 align:start position:0% it's great because when we jump to an enterprise<00:13:41.510> and<00:13:41.959> we<00:13:42.800> go<00:13:43.279> down<00:13:43.459> as<00:13:43.580> high<00:13:43.790> as 00:13:43.840 --> 00:13:43.850 align:start position:0% enterprise and we go down as high as 00:13:43.850 --> 00:13:46.730 align:start position:0% enterprise and we go down as high as demos<00:13:44.510> in<00:13:44.779> two<00:13:44.870> to<00:13:45.020> three<00:13:45.050> days<00:13:45.350> by<00:13:45.860> using 00:13:46.730 --> 00:13:46.740 align:start position:0% demos in two to three days by using 00:13:46.740 --> 00:13:49.340 align:start position:0% demos in two to three days by using plus<00:13:47.150> we<00:13:48.150> just<00:13:48.330> have<00:13:48.540> when<00:13:48.870> it's<00:13:49.020> not<00:13:49.170> fun 00:13:49.340 --> 00:13:49.350 align:start position:0% plus we just have when it's not fun 00:13:49.350 --> 00:13:51.500 align:start position:0% plus we just have when it's not fun after<00:13:49.680> that<00:13:49.710> happens<00:13:50.250> so<00:13:50.580> like<00:13:50.790> an<00:13:50.910> Oracle 00:13:51.500 --> 00:13:51.510 align:start position:0% after that happens so like an Oracle 00:13:51.510 --> 00:13:54.140 align:start position:0% after that happens so like an Oracle sit<00:13:51.780> down<00:13:51.990> monitor<00:13:52.500> when<00:13:53.340> something<00:13:53.760> happens 00:13:54.140 --> 00:13:54.150 align:start position:0% sit down monitor when something happens 00:13:54.150 --> 00:13:56.570 align:start position:0% sit down monitor when something happens go<00:13:54.360> and<00:13:54.600> do<00:13:54.690> something<00:13:55.110> this<00:13:55.260> place<00:13:55.560> in<00:13:55.830> animo 00:13:56.570 --> 00:13:56.580 align:start position:0% go and do something this place in animo 00:13:56.580 --> 00:13:59.000 align:start position:0% go and do something this place in animo so<00:13:56.790> anyone<00:13:57.450> to<00:13:57.540> do<00:13:57.630> one<00:13:57.810> of<00:13:57.840> those<00:13:58.020> hit<00:13:58.440> go<00:13:58.620> and 00:13:59.000 --> 00:13:59.010 align:start position:0% so anyone to do one of those hit go and 00:13:59.010 --> 00:14:04.160 align:start position:0% so anyone to do one of those hit go and out<00:14:01.430> establishes<00:14:02.430> these<00:14:02.970> what<00:14:03.210> happen<00:14:03.660> X's<00:14:03.990> we 00:14:04.160 --> 00:14:04.170 align:start position:0% out establishes these what happen X's we 00:14:04.170 --> 00:14:06.110 align:start position:0% out establishes these what happen X's we can<00:14:04.290> do<00:14:04.380> a<00:14:04.410> few<00:14:04.680> things<00:14:04.710> we've<00:14:05.610> got<00:14:05.730> triggers 00:14:06.110 --> 00:14:06.120 align:start position:0% can do a few things we've got triggers 00:14:06.120 --> 00:14:08.720 align:start position:0% can do a few things we've got triggers so<00:14:06.660> like<00:14:07.170> Oracle's<00:14:07.740> when<00:14:08.070> something<00:14:08.370> happens 00:14:08.720 --> 00:14:08.730 align:start position:0% so like Oracle's when something happens 00:14:08.730 --> 00:14:11.360 align:start position:0% so like Oracle's when something happens so<00:14:09.150> we<00:14:09.300> now<00:14:09.570> have<00:14:09.840> fabulous<00:14:10.560> codeless 00:14:11.360 --> 00:14:11.370 align:start position:0% so we now have fabulous codeless 00:14:11.370 --> 00:14:14.630 align:start position:0% so we now have fabulous codeless Enterprise<00:14:12.030> marbles<00:14:12.570> it's<00:14:12.750> pretty<00:14:13.050> cool<00:14:13.640> and 00:14:14.630 --> 00:14:14.640 align:start position:0% Enterprise marbles it's pretty cool and 00:14:14.640 --> 00:14:17.130 align:start position:0% Enterprise marbles it's pretty cool and action<00:14:15.000> what<00:14:15.720> to<00:14:15.870> do<00:14:15.960> or<00:14:16.110> something 00:14:17.130 --> 00:14:17.140 align:start position:0% action what to do or something 00:14:17.140 --> 00:14:21.560 align:start position:0% action what to do or something in<00:14:17.230> trigger<00:14:19.290> deployment<00:14:20.290> we<00:14:20.560> can<00:14:20.709> trigger 00:14:21.560 --> 00:14:21.570 align:start position:0% in trigger deployment we can trigger 00:14:21.570 --> 00:14:24.750 align:start position:0% in trigger deployment we can trigger executing<00:14:22.570> a<00:14:22.600> functional<00:14:23.350> spot<00:14:23.529> contract<00:14:24.130> we 00:14:24.750 --> 00:14:24.760 align:start position:0% executing a functional spot contract we 00:14:24.760 --> 00:14:28.319 align:start position:0% executing a functional spot contract we can<00:14:25.000> do<00:14:25.390> the<00:14:25.959> cola<00:14:26.260> transaction<00:14:27.100> and<00:14:27.490> probably 00:14:28.319 --> 00:14:28.329 align:start position:0% can do the cola transaction and probably 00:14:28.329 --> 00:14:33.240 align:start position:0% can do the cola transaction and probably throw<00:14:28.630> about<00:14:28.750> cycle<00:14:29.380> tracks<00:14:31.620> what<00:14:32.620> it<00:14:33.100> looks 00:14:33.240 --> 00:14:33.250 align:start position:0% throw about cycle tracks what it looks 00:14:33.250 --> 00:14:34.889 align:start position:0% throw about cycle tracks what it looks like<00:14:33.399> if<00:14:33.640> you<00:14:33.670> want<00:14:33.880> to<00:14:33.940> read<00:14:34.180> or<00:14:34.390> write<00:14:34.420> to<00:14:34.839> a 00:14:34.889 --> 00:14:34.899 align:start position:0% like if you want to read or write to a 00:14:34.899 --> 00:14:38.040 align:start position:0% like if you want to read or write to a blockchain<00:14:35.200> not<00:14:36.070> usually<00:14:36.519> this<00:14:36.700> so<00:14:37.269> what<00:14:38.019> I 00:14:38.040 --> 00:14:38.050 align:start position:0% blockchain not usually this so what I 00:14:38.050 --> 00:14:39.600 align:start position:0% blockchain not usually this so what I love<00:14:38.260> to<00:14:38.410> win<00:14:38.529> the<00:14:38.620> develop<00:14:39.070> it<00:14:39.190> about<00:14:39.399> with 00:14:39.600 --> 00:14:39.610 align:start position:0% love to win the develop it about with 00:14:39.610 --> 00:14:46.230 align:start position:0% love to win the develop it about with new<00:14:40.029> you<00:14:40.750> teams<00:14:41.019> I<00:14:41.399> get<00:14:42.399> them<00:14:42.579> too<00:14:45.120> so<00:14:46.120> that 00:14:46.230 --> 00:14:46.240 align:start position:0% new you teams I get them too so that 00:14:46.240 --> 00:14:48.420 align:start position:0% new you teams I get them too so that takes<00:14:46.420> them<00:14:46.630> a<00:14:46.660> few<00:14:46.870> minutes<00:14:47.350> but<00:14:47.560> see<00:14:48.130> how<00:14:48.370> do 00:14:48.420 --> 00:14:48.430 align:start position:0% takes them a few minutes but see how do 00:14:48.430 --> 00:14:51.120 align:start position:0% takes them a few minutes but see how do I<00:14:48.880> want<00:14:49.450> some<00:14:49.779> that<00:14:50.019> who<00:14:50.320> can<00:14:50.440> just<00:14:50.620> go<00:14:50.829> and 00:14:51.120 --> 00:14:51.130 align:start position:0% I want some that who can just go and 00:14:51.130 --> 00:14:53.400 align:start position:0% I want some that who can just go and enable<00:14:51.640> them<00:14:51.760> to<00:14:51.790> go<00:14:52.000> trigger<00:14:52.329> these<00:14:52.480> after 00:14:53.400 --> 00:14:53.410 align:start position:0% enable them to go trigger these after 00:14:53.410 --> 00:14:56.840 align:start position:0% enable them to go trigger these after this<00:14:53.760> dragging<00:14:54.760> the<00:14:55.510> endpoint<00:14:55.959> click<00:14:56.260> drag 00:14:56.840 --> 00:14:56.850 align:start position:0% this dragging the endpoint click drag 00:14:56.850 --> 00:15:00.000 align:start position:0% this dragging the endpoint click drag gonna<00:14:57.850> pull<00:14:58.149> this<00:14:58.269> moment<00:14:58.870> reddish<00:14:59.380> gray<00:14:59.649> to 00:15:00.000 --> 00:15:00.010 align:start position:0% gonna pull this moment reddish gray to 00:15:00.010 --> 00:15:02.699 align:start position:0% gonna pull this moment reddish gray to HTTP<00:15:00.700> response<00:15:01.540> passing<00:15:01.990> that<00:15:02.110> context<00:15:02.470> of<00:15:02.589> a 00:15:02.699 --> 00:15:02.709 align:start position:0% HTTP response passing that context of a 00:15:02.709 --> 00:15:10.060 align:start position:0% HTTP response passing that context of a place<00:15:02.950> so<00:15:03.670> that<00:15:03.700> kind<00:15:04.240> of<00:15:04.300> that<00:15:04.420> five<00:15:04.660> minutes 00:15:10.060 --> 00:15:10.070 align:start position:0% 00:15:10.070 --> 00:15:12.730 align:start position:0% that<00:15:11.000> was<00:15:11.090> reading<00:15:11.480> writing<00:15:11.900> and<00:15:12.320> then<00:15:12.620> we 00:15:12.730 --> 00:15:12.740 align:start position:0% that was reading writing and then we 00:15:12.740 --> 00:15:16.660 align:start position:0% that was reading writing and then we have<00:15:12.920> those<00:15:13.330> service<00:15:14.330> articles<00:15:14.540> so<00:15:15.670> just 00:15:16.660 --> 00:15:16.670 align:start position:0% have those service articles so just 00:15:16.670 --> 00:15:18.310 align:start position:0% have those service articles so just things<00:15:17.300> business<00:15:17.690> my<00:15:17.840> contact 00:15:18.310 --> 00:15:18.320 align:start position:0% things business my contact 00:15:18.320 --> 00:15:20.680 align:start position:0% things business my contact address<00:15:18.740> select<00:15:19.700> future<00:15:20.180> if<00:15:20.360> you<00:15:20.450> want 00:15:20.680 --> 00:15:20.690 align:start position:0% address select future if you want 00:15:20.690 --> 00:15:22.990 align:start position:0% address select future if you want just<00:15:21.050> got<00:15:21.200> that<00:15:21.320> from<00:15:21.470> the<00:15:21.500> API<00:15:21.920> and<00:15:22.610> instead 00:15:22.990 --> 00:15:23.000 align:start position:0% just got that from the API and instead 00:15:23.000 --> 00:15:25.420 align:start position:0% just got that from the API and instead what<00:15:23.150> you<00:15:23.240> want<00:15:23.270> to<00:15:23.450> do<00:15:23.570> go<00:15:24.050> and<00:15:24.320> see<00:15:25.130> without 00:15:25.420 --> 00:15:25.430 align:start position:0% what you want to do go and see without 00:15:25.430 --> 00:15:36.970 align:start position:0% what you want to do go and see without advice<00:15:25.760> publish<00:15:26.630> it<00:15:26.779> out<00:15:35.620> so<00:15:36.620> yeah<00:15:36.800> they 00:15:36.970 --> 00:15:36.980 align:start position:0% advice publish it out so yeah they 00:15:36.980 --> 00:15:40.750 align:start position:0% advice publish it out so yeah they talked<00:15:37.130> a<00:15:37.160> little<00:15:37.339> bit<00:15:37.490> about<00:15:39.760> developer 00:15:40.750 --> 00:15:40.760 align:start position:0% talked a little bit about developer 00:15:40.760 --> 00:15:42.579 align:start position:0% talked a little bit about developer experience<00:15:41.210> and<00:15:41.540> one<00:15:42.050> of<00:15:42.140> the<00:15:42.230> big<00:15:42.380> things 00:15:42.579 --> 00:15:42.589 align:start position:0% experience and one of the big things 00:15:42.589 --> 00:15:44.650 align:start position:0% experience and one of the big things we've<00:15:42.830> been<00:15:42.980> doing<00:15:43.130> there<00:15:43.460> is<00:15:43.700> some<00:15:44.420> pseudo 00:15:44.650 --> 00:15:44.660 align:start position:0% we've been doing there is some pseudo 00:15:44.660 --> 00:15:46.890 align:start position:0% we've been doing there is some pseudo code<00:15:44.900> so<00:15:45.230> improving<00:15:45.710> developer<00:15:46.220> productivity 00:15:46.890 --> 00:15:46.900 align:start position:0% code so improving developer productivity 00:15:46.900 --> 00:15:49.540 align:start position:0% code so improving developer productivity making<00:15:47.900> this<00:15:48.020> a<00:15:48.080> much<00:15:48.440> easier<00:15:48.470> process<00:15:48.980> for 00:15:49.540 --> 00:15:49.550 align:start position:0% making this a much easier process for 00:15:49.550 --> 00:15:51.490 align:start position:0% making this a much easier process for you<00:15:50.180> know<00:15:50.240> new<00:15:50.420> users<00:15:50.839> but<00:15:51.080> also<00:15:51.140> I'm<00:15:51.440> not 00:15:51.490 --> 00:15:51.500 align:start position:0% you know new users but also I'm not 00:15:51.500 --> 00:15:53.290 align:start position:0% you know new users but also I'm not trying<00:15:51.890> to<00:15:51.950> get<00:15:52.100> into<00:15:52.279> the<00:15:52.460> way<00:15:52.580> of<00:15:52.610> advanced 00:15:53.290 --> 00:15:53.300 align:start position:0% trying to get into the way of advanced 00:15:53.300 --> 00:15:55.480 align:start position:0% trying to get into the way of advanced users<00:15:53.620> so<00:15:54.620> somebody<00:15:54.890> who<00:15:55.010> knows<00:15:55.220> what<00:15:55.250> they're 00:15:55.480 --> 00:15:55.490 align:start position:0% users so somebody who knows what they're 00:15:55.490 --> 00:15:57.250 align:start position:0% users so somebody who knows what they're doing<00:15:55.550> with<00:15:56.180> these<00:15:56.330> tools<00:15:56.600> we<00:15:56.900> want<00:15:57.050> to<00:15:57.170> make 00:15:57.250 --> 00:15:57.260 align:start position:0% doing with these tools we want to make 00:15:57.260 --> 00:15:59.620 align:start position:0% doing with these tools we want to make sure<00:15:57.290> that<00:15:57.589> that<00:15:57.740> still<00:15:58.040> is<00:15:58.190> frictionless<00:15:58.630> but 00:15:59.620 --> 00:15:59.630 align:start position:0% sure that that still is frictionless but 00:15:59.630 --> 00:16:01.120 align:start position:0% sure that that still is frictionless but we<00:15:59.750> want<00:15:59.930> to<00:16:00.020> break<00:16:00.170> down<00:16:00.320> the<00:16:00.470> walls<00:16:00.680> for<00:16:00.950> like 00:16:01.120 --> 00:16:01.130 align:start position:0% we want to break down the walls for like 00:16:01.130 --> 00:16:04.360 align:start position:0% we want to break down the walls for like new<00:16:01.310> users<00:16:01.670> and<00:16:02.240> somebody<00:16:02.930> coming<00:16:03.170> into<00:16:03.290> the 00:16:04.360 --> 00:16:04.370 align:start position:0% new users and somebody coming into the 00:16:04.370 --> 00:16:06.880 align:start position:0% new users and somebody coming into the sometimes<00:16:05.120> not<00:16:05.420> quite<00:16:05.630> as<00:16:05.750> approachable<00:16:06.170> as<00:16:06.290> I 00:16:06.880 --> 00:16:06.890 align:start position:0% sometimes not quite as approachable as I 00:16:06.890 --> 00:16:09.100 align:start position:0% sometimes not quite as approachable as I think<00:16:07.340> so<00:16:08.150> looking<00:16:08.660> at<00:16:08.780> the<00:16:08.900> current 00:16:09.100 --> 00:16:09.110 align:start position:0% think so looking at the current 00:16:09.110 --> 00:16:10.570 align:start position:0% think so looking at the current developer<00:16:09.650> experience<00:16:10.160> you<00:16:10.310> know<00:16:10.400> there's 00:16:10.570 --> 00:16:10.580 align:start position:0% developer experience you know there's 00:16:10.580 --> 00:16:12.010 align:start position:0% developer experience you know there's obviously<00:16:10.970> some<00:16:11.240> a<00:16:11.270> development<00:16:11.780> component 00:16:12.010 --> 00:16:12.020 align:start position:0% obviously some a development component 00:16:12.020 --> 00:16:14.440 align:start position:0% obviously some a development component there<00:16:12.320> as<00:16:12.470> David<00:16:12.860> mentioned<00:16:13.180> things<00:16:14.180> like 00:16:14.440 --> 00:16:14.450 align:start position:0% there as David mentioned things like 00:16:14.450 --> 00:16:17.410 align:start position:0% there as David mentioned things like writing<00:16:14.720> smart<00:16:15.110> contractors<00:16:15.710> your<00:16:15.950> back<00:16:16.420> but 00:16:17.410 --> 00:16:17.420 align:start position:0% writing smart contractors your back but 00:16:17.420 --> 00:16:18.760 align:start position:0% writing smart contractors your back but a<00:16:17.450> little<00:16:17.660> with<00:16:17.840> that<00:16:18.020> then<00:16:18.230> becomes<00:16:18.620> the 00:16:18.760 --> 00:16:18.770 align:start position:0% a little with that then becomes the 00:16:18.770 --> 00:16:20.770 align:start position:0% a little with that then becomes the second<00:16:19.160> block<00:16:19.310> which<00:16:19.550> is<00:16:19.580> a<00:16:19.700> huge<00:16:20.090> kind<00:16:20.720> of 00:16:20.770 --> 00:16:20.780 align:start position:0% second block which is a huge kind of 00:16:20.780 --> 00:16:23.440 align:start position:0% second block which is a huge kind of area<00:16:21.140> for<00:16:21.350> a<00:16:21.380> new<00:16:21.590> user<00:16:21.830> to<00:16:22.250> say<00:16:22.760> what<00:16:23.030> do<00:16:23.090> I<00:16:23.150> use 00:16:23.440 --> 00:16:23.450 align:start position:0% area for a new user to say what do I use 00:16:23.450 --> 00:16:26.110 align:start position:0% area for a new user to say what do I use to<00:16:23.480> build<00:16:23.840> this<00:16:23.930> back<00:16:24.280> if<00:16:25.280> anyways<00:16:25.670> we've<00:16:25.910> had 00:16:26.110 --> 00:16:26.120 align:start position:0% to build this back if anyways we've had 00:16:26.120 --> 00:16:27.580 align:start position:0% to build this back if anyways we've had that<00:16:26.360> with<00:16:26.540> other<00:16:26.720> frameworks<00:16:26.960> and 00:16:27.580 --> 00:16:27.590 align:start position:0% that with other frameworks and 00:16:27.590 --> 00:16:30.550 align:start position:0% that with other frameworks and programming<00:16:28.430> languages<00:16:28.760> before<00:16:29.030> but<00:16:29.630> one 00:16:30.550 --> 00:16:30.560 align:start position:0% programming languages before but one 00:16:30.560 --> 00:16:32.560 align:start position:0% programming languages before but one change<00:16:30.830> specifically<00:16:31.340> a<00:16:31.460> very<00:16:31.790> open<00:16:32.360> source 00:16:32.560 --> 00:16:32.570 align:start position:0% change specifically a very open source 00:16:32.570 --> 00:16:35.350 align:start position:0% change specifically a very open source at<00:16:32.750> nature<00:16:33.110> there's<00:16:33.950> a<00:16:34.040> lot<00:16:34.310> of<00:16:34.580> awesome<00:16:35.150> tools 00:16:35.350 --> 00:16:35.360 align:start position:0% at nature there's a lot of awesome tools 00:16:35.360 --> 00:16:37.870 align:start position:0% at nature there's a lot of awesome tools out<00:16:35.570> there<00:16:35.600> and<00:16:36.070> there's<00:16:37.070> some<00:16:37.310> things<00:16:37.730> that 00:16:37.870 --> 00:16:37.880 align:start position:0% out there and there's some things that 00:16:37.880 --> 00:16:40.240 align:start position:0% out there and there's some things that maybe<00:16:38.180> aren't<00:16:38.750> so<00:16:38.840> awesome<00:16:39.290> right<00:16:39.380> so<00:16:39.620> people 00:16:40.240 --> 00:16:40.250 align:start position:0% maybe aren't so awesome right so people 00:16:40.250 --> 00:16:41.890 align:start position:0% maybe aren't so awesome right so people trying<00:16:40.520> to<00:16:40.700> find<00:16:40.940> the<00:16:41.120> right<00:16:41.300> tool<00:16:41.570> for<00:16:41.600> the 00:16:41.890 --> 00:16:41.900 align:start position:0% trying to find the right tool for the 00:16:41.900 --> 00:16:45.010 align:start position:0% trying to find the right tool for the right<00:16:41.930> job<00:16:42.280> has<00:16:43.280> been<00:16:43.430> a<00:16:43.490> struggle<00:16:43.810> we've<00:16:44.810> seen 00:16:45.010 --> 00:16:45.020 align:start position:0% right job has been a struggle we've seen 00:16:45.020 --> 00:16:47.410 align:start position:0% right job has been a struggle we've seen a<00:16:45.050> lot<00:16:45.290> that<00:16:45.560> people<00:16:45.740> use<00:16:45.980> in<00:16:46.220> these<00:16:46.370> so<00:16:47.060> one<00:16:47.270> of 00:16:47.410 --> 00:16:47.420 align:start position:0% a lot that people use in these so one of 00:16:47.420 --> 00:16:49.120 align:start position:0% a lot that people use in these so one of the<00:16:47.480> motivations<00:16:47.870> for<00:16:48.260> even<00:16:48.530> getting<00:16:49.010> into 00:16:49.120 --> 00:16:49.130 align:start position:0% the motivations for even getting into 00:16:49.130 --> 00:16:50.800 align:start position:0% the motivations for even getting into developer<00:16:49.670> experience<00:16:50.090> was<00:16:50.240> can<00:16:50.420> we<00:16:50.450> improve 00:16:50.800 --> 00:16:50.810 align:start position:0% developer experience was can we improve 00:16:50.810 --> 00:16:53.230 align:start position:0% developer experience was can we improve that<00:16:50.960> process<00:16:51.400> make<00:16:52.400> it<00:16:52.520> easier<00:16:52.910> for<00:16:53.120> people 00:16:53.230 --> 00:16:53.240 align:start position:0% that process make it easier for people 00:16:53.240 --> 00:16:55.750 align:start position:0% that process make it easier for people to<00:16:53.420> get<00:16:53.720> their<00:16:53.930> job<00:16:54.110> done<00:16:54.220> and<00:16:55.220> then<00:16:55.430> they<00:16:55.580> can 00:16:55.750 --> 00:16:55.760 align:start position:0% to get their job done and then they can 00:16:55.760 --> 00:16:57.750 align:start position:0% to get their job done and then they can grow<00:16:56.000> to<00:16:56.210> enlarge<00:16:56.600> as<00:16:56.990> a<00:16:57.020> building<00:16:57.500> we 00:16:57.750 --> 00:16:57.760 align:start position:0% grow to enlarge as a building we 00:16:57.760 --> 00:17:01.660 align:start position:0% grow to enlarge as a building we subsidize<00:16:58.930> the<00:16:59.930> second<00:17:00.320> thing<00:17:00.440> when<00:17:00.650> we<00:17:01.400> hook 00:17:01.660 --> 00:17:01.670 align:start position:0% subsidize the second thing when we hook 00:17:01.670 --> 00:17:03.700 align:start position:0% subsidize the second thing when we hook this<00:17:01.820> up<00:17:02.000> to<00:17:02.060> infrastructure<00:17:02.870> so<00:17:03.290> if<00:17:03.560> we're 00:17:03.700 --> 00:17:03.710 align:start position:0% this up to infrastructure so if we're 00:17:03.710 --> 00:17:05.950 align:start position:0% this up to infrastructure so if we're just<00:17:03.860> playing<00:17:04.130> to<00:17:04.340> a<00:17:04.370> public<00:17:04.730> or<00:17:05.270> private<00:17:05.420> note 00:17:05.950 --> 00:17:05.960 align:start position:0% just playing to a public or private note 00:17:05.960 --> 00:17:08.290 align:start position:0% just playing to a public or private note we<00:17:06.890> want<00:17:07.010> to<00:17:07.130> break<00:17:07.280> that<00:17:07.430> that<00:17:07.610> wall<00:17:07.820> down<00:17:08.030> to 00:17:08.290 --> 00:17:08.300 align:start position:0% we want to break that that wall down to 00:17:08.300 --> 00:17:10.660 align:start position:0% we want to break that that wall down to a<00:17:08.620> lot<00:17:09.620> of<00:17:09.650> times<00:17:09.830> we<00:17:10.160> do<00:17:10.280> these<00:17:10.400> hackathons 00:17:10.660 --> 00:17:10.670 align:start position:0% a lot of times we do these hackathons 00:17:10.670 --> 00:17:13.960 align:start position:0% a lot of times we do these hackathons early<00:17:11.270> in<00:17:11.690> the<00:17:11.780> last<00:17:12.020> few<00:17:12.470> years<00:17:12.500> and<00:17:12.950> I<00:17:13.790> can 00:17:13.960 --> 00:17:13.970 align:start position:0% early in the last few years and I can 00:17:13.970 --> 00:17:15.490 align:start position:0% early in the last few years and I can tell<00:17:14.150> you<00:17:14.240> that<00:17:14.420> we're<00:17:14.750> the<00:17:14.870> stumbling<00:17:15.110> blocks 00:17:15.490 --> 00:17:15.500 align:start position:0% tell you that we're the stumbling blocks 00:17:15.500 --> 00:17:17.470 align:start position:0% tell you that we're the stumbling blocks happening<00:17:16.100> not<00:17:16.340> coming<00:17:16.730> up<00:17:16.820> with<00:17:16.850> ideas<00:17:17.450> and 00:17:17.470 --> 00:17:17.480 align:start position:0% happening not coming up with ideas and 00:17:17.480 --> 00:17:20.020 align:start position:0% happening not coming up with ideas and get<00:17:17.870> the<00:17:17.960> things<00:17:18.170> that<00:17:18.260> we<00:17:18.830> like<00:17:19.400> how<00:17:19.760> do<00:17:19.820> we<00:17:19.940> do 00:17:20.020 --> 00:17:20.030 align:start position:0% get the things that we like how do we do 00:17:20.030 --> 00:17:22.330 align:start position:0% get the things that we like how do we do a<00:17:20.060> transaction<00:17:20.630> like<00:17:21.350> you<00:17:21.920> know<00:17:21.980> everybody 00:17:22.330 --> 00:17:22.340 align:start position:0% a transaction like you know everybody 00:17:22.340 --> 00:17:23.590 align:start position:0% a transaction like you know everybody knows<00:17:22.520> the<00:17:22.670> theory<00:17:22.940> of<00:17:23.000> like<00:17:23.330> that<00:17:23.480> this 00:17:23.590 --> 00:17:23.600 align:start position:0% knows the theory of like that this 00:17:23.600 --> 00:17:25.390 align:start position:0% knows the theory of like that this happens<00:17:24.020> when<00:17:24.200> the<00:17:24.830> rubber<00:17:25.010> meets<00:17:25.100> the<00:17:25.310> road 00:17:25.390 --> 00:17:25.400 align:start position:0% happens when the rubber meets the road 00:17:25.400 --> 00:17:27.760 align:start position:0% happens when the rubber meets the road and<00:17:25.580> they<00:17:25.790> have<00:17:25.880> to<00:17:26.000> use<00:17:26.210> 1/3<00:17:27.020> chance<00:17:27.110> or<00:17:27.680> they 00:17:27.760 --> 00:17:27.770 align:start position:0% and they have to use 1/3 chance or they 00:17:27.770 --> 00:17:29.320 align:start position:0% and they have to use 1/3 chance or they have<00:17:27.890> to<00:17:28.040> use<00:17:28.190> some<00:17:28.340> of<00:17:28.430> these<00:17:28.520> tools<00:17:28.730> they 00:17:29.320 --> 00:17:29.330 align:start position:0% have to use some of these tools they 00:17:29.330 --> 00:17:30.820 align:start position:0% have to use some of these tools they start<00:17:29.570> getting<00:17:29.630> confused<00:17:30.140> right<00:17:30.290> away<00:17:30.530> and 00:17:30.820 --> 00:17:30.830 align:start position:0% start getting confused right away and 00:17:30.830 --> 00:17:32.740 align:start position:0% start getting confused right away and then<00:17:31.040> you<00:17:31.370> know<00:17:31.610> they<00:17:31.970> start<00:17:32.300> to<00:17:32.360> fall<00:17:32.510> apart 00:17:32.740 --> 00:17:32.750 align:start position:0% then you know they start to fall apart 00:17:32.750 --> 00:17:33.540 align:start position:0% then you know they start to fall apart and<00:17:32.930> English 00:17:33.540 --> 00:17:33.550 align:start position:0% and English 00:17:33.550 --> 00:17:35.430 align:start position:0% and English activity<00:17:33.940> and<00:17:34.120> so<00:17:34.780> one<00:17:34.930> of<00:17:34.960> the<00:17:35.080> things<00:17:35.230> there 00:17:35.430 --> 00:17:35.440 align:start position:0% activity and so one of the things there 00:17:35.440 --> 00:17:37.410 align:start position:0% activity and so one of the things there was<00:17:35.620> how<00:17:35.800> can<00:17:35.860> we<00:17:35.980> connect<00:17:36.460> these<00:17:37.120> Ledger's 00:17:37.410 --> 00:17:37.420 align:start position:0% was how can we connect these Ledger's 00:17:37.420 --> 00:17:39.750 align:start position:0% was how can we connect these Ledger's and<00:17:37.840> much<00:17:38.050> more<00:17:38.170> sequels<00:17:38.590> fashion<00:17:39.070> and<00:17:39.250> then 00:17:39.750 --> 00:17:39.760 align:start position:0% and much more sequels fashion and then 00:17:39.760 --> 00:17:42.570 align:start position:0% and much more sequels fashion and then also<00:17:39.940> to<00:17:40.120> open<00:17:40.420> the<00:17:40.540> deployment<00:17:41.110> so<00:17:42.100> as<00:17:42.250> you 00:17:42.570 --> 00:17:42.580 align:start position:0% also to open the deployment so as you 00:17:42.580 --> 00:17:44.370 align:start position:0% also to open the deployment so as you are<00:17:42.940> starting<00:17:43.180> to<00:17:43.420> put<00:17:43.600> new<00:17:43.720> things<00:17:43.750> out<00:17:44.170> there 00:17:44.370 --> 00:17:44.380 align:start position:0% are starting to put new things out there 00:17:44.380 --> 00:17:45.810 align:start position:0% are starting to put new things out there people<00:17:44.770> are<00:17:44.920> starting<00:17:45.250> to<00:17:45.310> be<00:17:45.490> used<00:17:45.520> to 00:17:45.810 --> 00:17:45.820 align:start position:0% people are starting to be used to 00:17:45.820 --> 00:17:47.640 align:start position:0% people are starting to be used to beautiful<00:17:46.390> smart<00:17:46.810> contracts<00:17:47.320> and 00:17:47.640 --> 00:17:47.650 align:start position:0% beautiful smart contracts and 00:17:47.650 --> 00:17:49.680 align:start position:0% beautiful smart contracts and transactions<00:17:48.310> how<00:17:48.970> can<00:17:49.180> we<00:17:49.300> help<00:17:49.450> that 00:17:49.680 --> 00:17:49.690 align:start position:0% transactions how can we help that 00:17:49.690 --> 00:17:51.930 align:start position:0% transactions how can we help that process<00:17:49.870> as<00:17:50.290> well<00:17:50.440> so<00:17:50.740> that's<00:17:51.280> those<00:17:51.670> are<00:17:51.700> the 00:17:51.930 --> 00:17:51.940 align:start position:0% process as well so that's those are the 00:17:51.940 --> 00:17:56.790 align:start position:0% process as well so that's those are the main<00:17:52.240> motivations<00:17:52.900> for<00:17:53.080> why<00:17:53.550> all<00:17:54.550> business<00:17:55.800> so 00:17:56.790 --> 00:17:56.800 align:start position:0% main motivations for why all business so 00:17:56.800 --> 00:17:58.230 align:start position:0% main motivations for why all business so from<00:17:56.980> an<00:17:57.130> integrated<00:17:58.060> development 00:17:58.230 --> 00:17:58.240 align:start position:0% from an integrated development 00:17:58.240 --> 00:17:59.820 align:start position:0% from an integrated development experience<00:17:58.990> if<00:17:59.140> people<00:17:59.320> look<00:17:59.410> at<00:17:59.500> the<00:17:59.590> left 00:17:59.820 --> 00:17:59.830 align:start position:0% experience if people look at the left 00:17:59.830 --> 00:18:01.080 align:start position:0% experience if people look at the left side<00:18:00.010> of<00:18:00.130> this<00:18:00.220> and<00:18:00.430> then<00:18:00.520> move<00:18:00.610> to<00:18:00.790> the<00:18:00.940> right 00:18:01.080 --> 00:18:01.090 align:start position:0% side of this and then move to the right 00:18:01.090 --> 00:18:03.330 align:start position:0% side of this and then move to the right on<00:18:02.020> the<00:18:02.140> left<00:18:02.320> side<00:18:02.440> basically<00:18:03.040> are<00:18:03.280> saying 00:18:03.330 --> 00:18:03.340 align:start position:0% on the left side basically are saying 00:18:03.340 --> 00:18:05.640 align:start position:0% on the left side basically are saying like<00:18:03.760> in<00:18:04.000> most<00:18:04.300> languages<00:18:05.020> and<00:18:05.380> most 00:18:05.640 --> 00:18:05.650 align:start position:0% like in most languages and most 00:18:05.650 --> 00:18:07.890 align:start position:0% like in most languages and most programming<00:18:06.220> structures<00:18:07.000> that<00:18:07.090> we<00:18:07.180> have<00:18:07.210> we 00:18:07.890 --> 00:18:07.900 align:start position:0% programming structures that we have we 00:18:07.900 --> 00:18:09.480 align:start position:0% programming structures that we have we have<00:18:08.080> the<00:18:08.230> idea<00:18:08.590> of<00:18:08.710> a<00:18:08.800> create<00:18:09.160> your<00:18:09.280> project 00:18:09.480 --> 00:18:09.490 align:start position:0% have the idea of a create your project 00:18:09.490 --> 00:18:12.330 align:start position:0% have the idea of a create your project right<00:18:10.390> not<00:18:11.080> just<00:18:11.230> a<00:18:11.320> hello<00:18:11.500> world<00:18:11.590> but<00:18:12.010> like 00:18:12.330 --> 00:18:12.340 align:start position:0% right not just a hello world but like 00:18:12.340 --> 00:18:14.310 align:start position:0% right not just a hello world but like let<00:18:12.580> me<00:18:12.790> scaffold<00:18:13.270> out<00:18:13.390> a<00:18:13.600> real<00:18:13.810> structure 00:18:14.310 --> 00:18:14.320 align:start position:0% let me scaffold out a real structure 00:18:14.320 --> 00:18:16.500 align:start position:0% let me scaffold out a real structure that<00:18:14.500> I<00:18:14.530> would<00:18:14.710> actually<00:18:14.860> use<00:18:15.100> I<00:18:15.640> don't<00:18:16.240> want 00:18:16.500 --> 00:18:16.510 align:start position:0% that I would actually use I don't want 00:18:16.510 --> 00:18:18.000 align:start position:0% that I would actually use I don't want just<00:18:16.540> one<00:18:16.870> something<00:18:17.140> example<00:18:17.710> or<00:18:17.830> something 00:18:18.000 --> 00:18:18.010 align:start position:0% just one something example or something 00:18:18.010 --> 00:18:22.130 align:start position:0% just one something example or something like<00:18:18.250> that<00:18:18.310> just<00:18:18.490> wanna<00:18:18.820> get<00:18:19.000> started 00:18:22.130 --> 00:18:22.140 align:start position:0% 00:18:22.140 --> 00:18:25.260 align:start position:0% creating<00:18:23.140> Ledger's<00:18:23.560> how<00:18:23.950> can<00:18:24.130> we<00:18:24.280> do<00:18:25.060> that 00:18:25.260 --> 00:18:25.270 align:start position:0% creating Ledger's how can we do that 00:18:25.270 --> 00:18:28.260 align:start position:0% creating Ledger's how can we do that from<00:18:25.420> inside<00:18:25.600> the<00:18:25.780> I<00:18:25.900> mean<00:18:26.520> we<00:18:27.520> don't<00:18:27.700> another 00:18:28.260 --> 00:18:28.270 align:start position:0% from inside the I mean we don't another 00:18:28.270 --> 00:18:30.360 align:start position:0% from inside the I mean we don't another issue<00:18:28.660> that<00:18:28.840> comes<00:18:29.080> up<00:18:29.290> is<00:18:29.530> there's<00:18:30.070> a<00:18:30.130> lot<00:18:30.280> of 00:18:30.360 --> 00:18:30.370 align:start position:0% issue that comes up is there's a lot of 00:18:30.370 --> 00:18:32.580 align:start position:0% issue that comes up is there's a lot of different<00:18:30.610> service<00:18:30.880> providers<00:18:31.000> as<00:18:31.630> a<00:18:32.110> big<00:18:32.410> one 00:18:32.580 --> 00:18:32.590 align:start position:0% different service providers as a big one 00:18:32.590 --> 00:18:34.770 align:start position:0% different service providers as a big one but<00:18:33.310> there's<00:18:33.460> many<00:18:33.580> other<00:18:33.700> ones<00:18:34.060> right<00:18:34.390> and<00:18:34.630> so 00:18:34.770 --> 00:18:34.780 align:start position:0% but there's many other ones right and so 00:18:34.780 --> 00:18:36.930 align:start position:0% but there's many other ones right and so it's<00:18:34.900> like<00:18:35.080> okay<00:18:35.740> I<00:18:35.770> need<00:18:35.980> a<00:18:36.130> ledger<00:18:36.460> after<00:18:36.910> I 00:18:36.930 --> 00:18:36.940 align:start position:0% it's like okay I need a ledger after I 00:18:36.940 --> 00:18:38.820 align:start position:0% it's like okay I need a ledger after I create<00:18:37.240> my<00:18:37.360> stuff<00:18:37.660> then<00:18:38.170> I<00:18:38.260> got<00:18:38.380> a<00:18:38.410> bounce<00:18:38.620> out 00:18:38.820 --> 00:18:38.830 align:start position:0% create my stuff then I got a bounce out 00:18:38.830 --> 00:18:41.760 align:start position:0% create my stuff then I got a bounce out to<00:18:38.920> it<00:18:39.130> website<00:18:39.490> another<00:18:40.180> Facebook<00:18:40.620> there<00:18:41.620> is 00:18:41.760 --> 00:18:41.770 align:start position:0% to it website another Facebook there is 00:18:41.770 --> 00:18:44.370 align:start position:0% to it website another Facebook there is my<00:18:41.920> productivity<00:18:42.310> right<00:18:42.820> so<00:18:43.450> you<00:18:44.290> know 00:18:44.370 --> 00:18:44.380 align:start position:0% my productivity right so you know 00:18:44.380 --> 00:18:46.650 align:start position:0% my productivity right so you know keeping<00:18:44.830> someone<00:18:45.190> engaged<00:18:45.640> in<00:18:45.910> the<00:18:45.970> IDE<00:18:46.270> is 00:18:46.650 --> 00:18:46.660 align:start position:0% keeping someone engaged in the IDE is 00:18:46.660 --> 00:18:48.330 align:start position:0% keeping someone engaged in the IDE is really<00:18:46.960> beneficial<00:18:47.350> for<00:18:47.560> the<00:18:47.920> programmer 00:18:48.330 --> 00:18:48.340 align:start position:0% really beneficial for the programmer 00:18:48.340 --> 00:18:50.040 align:start position:0% really beneficial for the programmer that<00:18:48.460> stay<00:18:48.790> involved<00:18:49.060> it's<00:18:49.420> a<00:18:49.540> like<00:18:49.780> if<00:18:49.930> you 00:18:50.040 --> 00:18:50.050 align:start position:0% that stay involved it's a like if you 00:18:50.050 --> 00:18:51.690 align:start position:0% that stay involved it's a like if you want<00:18:50.200> to<00:18:50.260> go<00:18:50.320> to<00:18:50.380> deploy<00:18:50.620> this<00:18:50.830> okay<00:18:51.220> I<00:18:51.250> keep<00:18:51.580> my 00:18:51.690 --> 00:18:51.700 align:start position:0% want to go to deploy this okay I keep my 00:18:51.700 --> 00:18:53.070 align:start position:0% want to go to deploy this okay I keep my same<00:18:51.880> mindset<00:18:52.210> if<00:18:52.390> I<00:18:52.450> start<00:18:52.690> context 00:18:53.070 --> 00:18:53.080 align:start position:0% same mindset if I start context 00:18:53.080 --> 00:18:56.260 align:start position:0% same mindset if I start context switching<00:18:53.470> I<00:18:53.710> got<00:18:54.190> issues 00:18:56.260 --> 00:18:56.270 align:start position:0% switching I got issues 00:18:56.270 --> 00:18:59.330 align:start position:0% switching I got issues and<00:18:57.270> the<00:18:57.780> automatic<00:18:58.380> configuration<00:18:58.530> as<00:18:59.220> I 00:18:59.330 --> 00:18:59.340 align:start position:0% and the automatic configuration as I 00:18:59.340 --> 00:19:01.670 align:start position:0% and the automatic configuration as I mentioned<00:18:59.670> before<00:18:59.730> so<00:19:00.240> we<00:19:00.360> want<00:19:00.570> to<00:19:00.720> take<00:19:01.440> what 00:19:01.670 --> 00:19:01.680 align:start position:0% mentioned before so we want to take what 00:19:01.680 --> 00:19:03.530 align:start position:0% mentioned before so we want to take what we're<00:19:01.830> building<00:19:01.950> take<00:19:02.640> wherever<00:19:02.850> it<00:19:03.120> wanted 00:19:03.530 --> 00:19:03.540 align:start position:0% we're building take wherever it wanted 00:19:03.540 --> 00:19:05.630 align:start position:0% we're building take wherever it wanted to<00:19:03.600> and<00:19:03.930> help<00:19:04.320> build<00:19:04.710> that<00:19:04.800> configuration<00:19:05.550> on 00:19:05.630 --> 00:19:05.640 align:start position:0% to and help build that configuration on 00:19:05.640 --> 00:19:07.940 align:start position:0% to and help build that configuration on the<00:19:05.670> fly<00:19:05.940> for<00:19:06.000> you<00:19:06.390> so<00:19:07.230> you<00:19:07.440> don't<00:19:07.620> have<00:19:07.770> to 00:19:07.940 --> 00:19:07.950 align:start position:0% the fly for you so you don't have to 00:19:07.950 --> 00:19:09.740 align:start position:0% the fly for you so you don't have to like<00:19:08.130> waste<00:19:08.370> your<00:19:08.610> time<00:19:08.820> with<00:19:09.060> configuration 00:19:09.740 --> 00:19:09.750 align:start position:0% like waste your time with configuration 00:19:09.750 --> 00:19:11.750 align:start position:0% like waste your time with configuration files<00:19:10.020> certainly<00:19:11.010> they're<00:19:11.160> there<00:19:11.370> and<00:19:11.670> you 00:19:11.750 --> 00:19:11.760 align:start position:0% files certainly they're there and you 00:19:11.760 --> 00:19:14.540 align:start position:0% files certainly they're there and you can<00:19:11.910> go<00:19:12.000> sweet<00:19:12.270> them<00:19:12.480> and<00:19:12.780> wait<00:19:13.380> easy<00:19:13.620> but<00:19:14.310> most 00:19:14.540 --> 00:19:14.550 align:start position:0% can go sweet them and wait easy but most 00:19:14.550 --> 00:19:16.160 align:start position:0% can go sweet them and wait easy but most times<00:19:14.790> you<00:19:15.360> just<00:19:15.390> want<00:19:15.540> to<00:19:15.690> get<00:19:15.870> through<00:19:16.140> it 00:19:16.160 --> 00:19:16.170 align:start position:0% times you just want to get through it 00:19:16.170 --> 00:19:17.300 align:start position:0% times you just want to get through it let's<00:19:16.500> get<00:19:16.590> this<00:19:16.710> thing<00:19:16.890> running<00:19:17.040> that 00:19:17.300 --> 00:19:17.310 align:start position:0% let's get this thing running that 00:19:17.310 --> 00:19:18.980 align:start position:0% let's get this thing running that seemeth<00:19:17.610> broken<00:19:18.030> and<00:19:18.210> see<00:19:18.300> how<00:19:18.450> I<00:19:18.480> can<00:19:18.600> visit 00:19:18.980 --> 00:19:18.990 align:start position:0% seemeth broken and see how I can visit 00:19:18.990 --> 00:19:22.570 align:start position:0% seemeth broken and see how I can visit you<00:19:19.170> through<00:19:19.910> the<00:19:20.910> middle<00:19:21.150> of<00:19:21.240> the<00:19:21.570> IDE<00:19:21.870> and 00:19:22.570 --> 00:19:22.580 align:start position:0% you through the middle of the IDE and 00:19:22.580 --> 00:19:25.400 align:start position:0% you through the middle of the IDE and part<00:19:23.580> of<00:19:23.670> this<00:19:23.760> is<00:19:24.000> like<00:19:24.240> Microsoft<00:19:24.480> and<00:19:25.080> you 00:19:25.400 --> 00:19:25.410 align:start position:0% part of this is like Microsoft and you 00:19:25.410 --> 00:19:27.350 align:start position:0% part of this is like Microsoft and you know<00:19:25.530> bringing<00:19:25.980> our<00:19:26.220> OEE<00:19:26.610> like<00:19:26.970> that<00:19:27.120> Visual 00:19:27.350 --> 00:19:27.360 align:start position:0% know bringing our OEE like that Visual 00:19:27.360 --> 00:19:30.320 align:start position:0% know bringing our OEE like that Visual Studio<00:19:27.480> best<00:19:28.110> example<00:19:28.620> is<00:19:29.160> one<00:19:29.490> aspect<00:19:29.850> of<00:19:30.180> it 00:19:30.320 --> 00:19:30.330 align:start position:0% Studio best example is one aspect of it 00:19:30.330 --> 00:19:32.420 align:start position:0% Studio best example is one aspect of it but<00:19:30.810> trying<00:19:31.110> to<00:19:31.200> like<00:19:31.410> take<00:19:31.620> over<00:19:31.860> this<00:19:32.010> market 00:19:32.420 --> 00:19:32.430 align:start position:0% but trying to like take over this market 00:19:32.430 --> 00:19:33.650 align:start position:0% but trying to like take over this market and<00:19:32.490> say<00:19:32.610> we're<00:19:32.760> going<00:19:32.850> to<00:19:32.910> build<00:19:33.030> the<00:19:33.240> best 00:19:33.650 --> 00:19:33.660 align:start position:0% and say we're going to build the best 00:19:33.660 --> 00:19:35.240 align:start position:0% and say we're going to build the best debugger<00:19:34.050> we're<00:19:34.680> gonna<00:19:34.800> build<00:19:35.040> the<00:19:35.220> best 00:19:35.240 --> 00:19:35.250 align:start position:0% debugger we're gonna build the best 00:19:35.250 --> 00:19:37.910 align:start position:0% debugger we're gonna build the best packager<00:19:36.090> this<00:19:36.720> is<00:19:36.840> not<00:19:37.050> something<00:19:37.800> that's 00:19:37.910 --> 00:19:37.920 align:start position:0% packager this is not something that's 00:19:37.920 --> 00:19:40.040 align:start position:0% packager this is not something that's going<00:19:38.130> to<00:19:38.220> happen<00:19:38.460> right<00:19:38.850> because<00:19:39.270> there's 00:19:40.040 --> 00:19:40.050 align:start position:0% going to happen right because there's 00:19:40.050 --> 00:19:42.020 align:start position:0% going to happen right because there's such<00:19:40.320> a<00:19:40.350> huge<00:19:40.830> community<00:19:41.220> around<00:19:41.490> this<00:19:41.730> that's 00:19:42.020 --> 00:19:42.030 align:start position:0% such a huge community around this that's 00:19:42.030 --> 00:19:44.570 align:start position:0% such a huge community around this that's building<00:19:42.330> awesome<00:19:42.720> stuff<00:19:42.960> and<00:19:43.230> so<00:19:44.010> really<00:19:44.280> we 00:19:44.570 --> 00:19:44.580 align:start position:0% building awesome stuff and so really we 00:19:44.580 --> 00:19:46.220 align:start position:0% building awesome stuff and so really we see<00:19:44.730> ourselves<00:19:44.850> as<00:19:45.420> more<00:19:45.690> of<00:19:45.750> a<00:19:45.810> connecting 00:19:46.220 --> 00:19:46.230 align:start position:0% see ourselves as more of a connecting 00:19:46.230 --> 00:19:48.530 align:start position:0% see ourselves as more of a connecting tool<00:19:46.440> to<00:19:46.620> say<00:19:46.770> who<00:19:47.610> are<00:19:47.670> the<00:19:47.760> best<00:19:47.940> guys<00:19:48.180> doing 00:19:48.530 --> 00:19:48.540 align:start position:0% tool to say who are the best guys doing 00:19:48.540 --> 00:19:50.330 align:start position:0% tool to say who are the best guys doing these<00:19:48.780> things<00:19:48.990> are<00:19:49.170> who<00:19:49.290> the<00:19:49.500> most<00:19:49.950> popular 00:19:50.330 --> 00:19:50.340 align:start position:0% these things are who the most popular 00:19:50.340 --> 00:19:53.210 align:start position:0% these things are who the most popular ones<00:19:50.550> that<00:19:50.670> we<00:19:50.730> can<00:19:50.880> work<00:19:51.060> with<00:19:51.090> and<00:19:51.870> get<00:19:52.220> them 00:19:53.210 --> 00:19:53.220 align:start position:0% ones that we can work with and get them 00:19:53.220 --> 00:19:54.650 align:start position:0% ones that we can work with and get them if<00:19:53.400> there's<00:19:53.580> something<00:19:53.880> bigger<00:19:54.060> in<00:19:54.180> there<00:19:54.420> so 00:19:54.650 --> 00:19:54.660 align:start position:0% if there's something bigger in there so 00:19:54.660 --> 00:19:57.050 align:start position:0% if there's something bigger in there so that<00:19:54.690> we<00:19:54.900> can<00:19:55.050> build<00:19:55.200> a<00:19:55.380> better<00:19:55.470> tool<00:19:55.940> and<00:19:56.940> so 00:19:57.050 --> 00:19:57.060 align:start position:0% that we can build a better tool and so 00:19:57.060 --> 00:19:58.550 align:start position:0% that we can build a better tool and so in<00:19:57.180> this<00:19:57.240> case<00:19:57.300> one<00:19:57.870> of<00:19:57.900> the<00:19:58.050> first<00:19:58.260> ones<00:19:58.470> that 00:19:58.550 --> 00:19:58.560 align:start position:0% in this case one of the first ones that 00:19:58.560 --> 00:20:00.860 align:start position:0% in this case one of the first ones that we<00:19:58.680> worked<00:19:58.890> with<00:19:58.980> was<00:19:59.220> truffle<00:19:59.670> a<00:19:59.910> great 00:20:00.860 --> 00:20:00.870 align:start position:0% we worked with was truffle a great 00:20:00.870 --> 00:20:02.630 align:start position:0% we worked with was truffle a great relationship<00:20:01.470> with<00:20:01.620> tammand<00:20:02.100> and<00:20:02.370> a<00:20:02.430> group 00:20:02.630 --> 00:20:02.640 align:start position:0% relationship with tammand and a group 00:20:02.640 --> 00:20:04.790 align:start position:0% relationship with tammand and a group there<00:20:03.020> we<00:20:04.020> work<00:20:04.170> very<00:20:04.200> closely<00:20:04.590> with 00:20:04.790 --> 00:20:04.800 align:start position:0% there we work very closely with 00:20:04.800 --> 00:20:08.930 align:start position:0% there we work very closely with consensus<00:20:05.520> and<00:20:05.900> code<00:20:06.900> with<00:20:07.110> Blanco<00:20:07.950> we<00:20:08.820> work 00:20:08.930 --> 00:20:08.940 align:start position:0% consensus and code with Blanco we work 00:20:08.940 --> 00:20:10.460 align:start position:0% consensus and code with Blanco we work very<00:20:08.970> closely<00:20:09.330> the<00:20:09.570> very<00:20:09.810> foundation<00:20:10.350> on 00:20:10.460 --> 00:20:10.470 align:start position:0% very closely the very foundation on 00:20:10.470 --> 00:20:12.530 align:start position:0% very closely the very foundation on remix<00:20:10.860> and<00:20:11.700> there's<00:20:11.880> others<00:20:12.150> that<00:20:12.180> are 00:20:12.530 --> 00:20:12.540 align:start position:0% remix and there's others that are 00:20:12.540 --> 00:20:14.120 align:start position:0% remix and there's others that are imagined<00:20:12.960> tears<00:20:13.200> that<00:20:13.410> we've<00:20:13.590> been<00:20:13.680> actively 00:20:14.120 --> 00:20:14.130 align:start position:0% imagined tears that we've been actively 00:20:14.130 --> 00:20:16.550 align:start position:0% imagined tears that we've been actively working<00:20:14.490> with<00:20:14.850> the<00:20:14.970> foundation<00:20:15.630> to<00:20:15.840> bring<00:20:16.260> a 00:20:16.550 --> 00:20:16.560 align:start position:0% working with the foundation to bring a 00:20:16.560 --> 00:20:18.040 align:start position:0% working with the foundation to bring a more<00:20:16.800> of<00:20:17.100> the<00:20:17.250> people<00:20:17.430> building 00:20:18.040 --> 00:20:18.050 align:start position:0% more of the people building 00:20:18.050 --> 00:20:20.620 align:start position:0% more of the people building tools<00:20:18.320> in<00:20:18.620> the<00:20:18.830> ecosystem<00:20:19.670> so<00:20:20.330> if<00:20:20.450> there's 00:20:20.620 --> 00:20:20.630 align:start position:0% tools in the ecosystem so if there's 00:20:20.630 --> 00:20:22.060 align:start position:0% tools in the ecosystem so if there's anybody<00:20:20.900> in<00:20:21.170> here<00:20:21.320> building<00:20:21.650> dev<00:20:21.830> tools 00:20:22.060 --> 00:20:22.070 align:start position:0% anybody in here building dev tools 00:20:22.070 --> 00:20:24.460 align:start position:0% anybody in here building dev tools certainly<00:20:22.880> come<00:20:23.120> see<00:20:23.330> me<00:20:23.480> at<00:20:23.570> the<00:20:23.600> booth<00:20:23.840> or<00:20:24.350> my 00:20:24.460 --> 00:20:24.470 align:start position:0% certainly come see me at the booth or my 00:20:24.470 --> 00:20:26.650 align:start position:0% certainly come see me at the booth or my group<00:20:24.710> and<00:20:25.550> talk<00:20:25.790> to<00:20:25.940> us<00:20:26.120> because<00:20:26.270> we're<00:20:26.600> very 00:20:26.650 --> 00:20:26.660 align:start position:0% group and talk to us because we're very 00:20:26.660 --> 00:20:29.020 align:start position:0% group and talk to us because we're very interested<00:20:27.190> we<00:20:28.190> want<00:20:28.430> to<00:20:28.490> make<00:20:28.610> sure<00:20:28.640> that<00:20:28.910> as 00:20:29.020 --> 00:20:29.030 align:start position:0% interested we want to make sure that as 00:20:29.030 --> 00:20:30.430 align:start position:0% interested we want to make sure that as we're<00:20:29.210> building<00:20:29.480> this<00:20:29.600> toilet<00:20:29.990> we're<00:20:30.230> doing 00:20:30.430 --> 00:20:30.440 align:start position:0% we're building this toilet we're doing 00:20:30.440 --> 00:20:31.750 align:start position:0% we're building this toilet we're doing it<00:20:30.530> in<00:20:30.620> such<00:20:30.800> a<00:20:30.830> way<00:20:30.920> it's<00:20:31.190> not<00:20:31.310> like<00:20:31.370> tightly 00:20:31.750 --> 00:20:31.760 align:start position:0% it in such a way it's not like tightly 00:20:31.760 --> 00:20:33.700 align:start position:0% it in such a way it's not like tightly coupled<00:20:32.090> to<00:20:32.360> one<00:20:32.660> of<00:20:32.780> these<00:20:32.870> kind<00:20:33.680> of 00:20:33.700 --> 00:20:33.710 align:start position:0% coupled to one of these kind of 00:20:33.710 --> 00:20:35.770 align:start position:0% coupled to one of these kind of frameworks<00:20:34.160> we<00:20:34.340> much<00:20:34.550> rather<00:20:34.790> it<00:20:34.970> be<00:20:35.120> open<00:20:35.510> let 00:20:35.770 --> 00:20:35.780 align:start position:0% frameworks we much rather it be open let 00:20:35.780 --> 00:20:38.290 align:start position:0% frameworks we much rather it be open let people<00:20:36.050> have<00:20:36.140> choice<00:20:36.410> I<00:20:36.830> just<00:20:37.700> help<00:20:37.880> the<00:20:38.000> user 00:20:38.290 --> 00:20:38.300 align:start position:0% people have choice I just help the user 00:20:38.300 --> 00:20:40.990 align:start position:0% people have choice I just help the user get<00:20:38.480> started<00:20:39.220> and<00:20:40.220> then<00:20:40.370> at<00:20:40.520> the<00:20:40.640> right<00:20:40.670> time 00:20:40.990 --> 00:20:41.000 align:start position:0% get started and then at the right time 00:20:41.000 --> 00:20:43.750 align:start position:0% get started and then at the right time is<00:20:41.210> basically<00:20:41.930> the<00:20:42.350> ledger<00:20:42.740> technology<00:20:43.070> so 00:20:43.750 --> 00:20:43.760 align:start position:0% is basically the ledger technology so 00:20:43.760 --> 00:20:45.280 align:start position:0% is basically the ledger technology so like<00:20:43.970> after<00:20:44.300> we<00:20:44.420> built<00:20:44.630> something<00:20:44.840> that<00:20:45.170> we 00:20:45.280 --> 00:20:45.290 align:start position:0% like after we built something that we 00:20:45.290 --> 00:20:46.890 align:start position:0% like after we built something that we have<00:20:45.410> a<00:20:45.440> skoy<00:20:45.710> you<00:20:45.860> need<00:20:46.160> to<00:20:46.250> actually<00:20:46.370> do<00:20:46.700> it 00:20:46.890 --> 00:20:46.900 align:start position:0% have a skoy you need to actually do it 00:20:46.900 --> 00:20:49.500 align:start position:0% have a skoy you need to actually do it what<00:20:47.900> we're<00:20:48.140> we<00:20:48.320> deploying<00:20:48.650> these<00:20:48.890> things<00:20:49.130> to 00:20:49.500 --> 00:20:49.510 align:start position:0% what we're we deploying these things to 00:20:49.510 --> 00:20:51.670 align:start position:0% what we're we deploying these things to certainly<00:20:50.510> one<00:20:50.840> of<00:20:50.870> the<00:20:51.020> things<00:20:51.230> to<00:20:51.530> get 00:20:51.670 --> 00:20:51.680 align:start position:0% certainly one of the things to get 00:20:51.680 --> 00:20:53.740 align:start position:0% certainly one of the things to get started<00:20:52.070> and<00:20:52.310> if<00:20:52.670> I'm<00:20:52.790> on<00:20:52.910> a<00:20:52.940> plane<00:20:53.240> or<00:20:53.570> if<00:20:53.630> I'm 00:20:53.740 --> 00:20:53.750 align:start position:0% started and if I'm on a plane or if I'm 00:20:53.750 --> 00:20:54.910 align:start position:0% started and if I'm on a plane or if I'm disconnected<00:20:54.350> I<00:20:54.410> want<00:20:54.560> to<00:20:54.620> do<00:20:54.710> something 00:20:54.910 --> 00:20:54.920 align:start position:0% disconnected I want to do something 00:20:54.920 --> 00:20:57.010 align:start position:0% disconnected I want to do something local<00:20:55.430> I<00:20:55.670> don't<00:20:56.090> have<00:20:56.210> to<00:20:56.300> go<00:20:56.390> spin<00:20:56.630> up<00:20:56.750> a<00:20:56.810> huge 00:20:57.010 --> 00:20:57.020 align:start position:0% local I don't have to go spin up a huge 00:20:57.020 --> 00:20:58.660 align:start position:0% local I don't have to go spin up a huge Network<00:20:57.380> and<00:20:57.620> waste<00:20:57.950> a<00:20:58.010> bunch<00:20:58.100> of<00:20:58.250> money<00:20:58.430> just 00:20:58.660 --> 00:20:58.670 align:start position:0% Network and waste a bunch of money just 00:20:58.670 --> 00:21:00.220 align:start position:0% Network and waste a bunch of money just to<00:20:58.820> see<00:20:59.030> my<00:20:59.240> smart<00:20:59.450> contracts<00:20:59.900> working 00:21:00.220 --> 00:21:00.230 align:start position:0% to see my smart contracts working 00:21:00.230 --> 00:21:03.730 align:start position:0% to see my smart contracts working functionally<00:21:01.000> my<00:21:02.000> automated<00:21:02.330> tests<00:21:02.900> are<00:21:03.050> if 00:21:03.730 --> 00:21:03.740 align:start position:0% functionally my automated tests are if 00:21:03.740 --> 00:21:05.020 align:start position:0% functionally my automated tests are if some<00:21:03.890> of<00:21:03.980> the<00:21:04.130> other<00:21:04.160> vendors<00:21:04.580> were<00:21:04.700> working 00:21:05.020 --> 00:21:05.030 align:start position:0% some of the other vendors were working 00:21:05.030 --> 00:21:06.580 align:start position:0% some of the other vendors were working with<00:21:05.150> MIT<00:21:05.480> backs<00:21:05.720> some<00:21:05.960> of<00:21:06.050> the<00:21:06.110> security 00:21:06.580 --> 00:21:06.590 align:start position:0% with MIT backs some of the security 00:21:06.590 --> 00:21:08.440 align:start position:0% with MIT backs some of the security vendors<00:21:06.980> we<00:21:07.400> want<00:21:07.640> to<00:21:07.700> make<00:21:07.820> sure<00:21:07.850> that<00:21:08.330> it's 00:21:08.440 --> 00:21:08.450 align:start position:0% vendors we want to make sure that it's 00:21:08.450 --> 00:21:10.120 align:start position:0% vendors we want to make sure that it's all<00:21:08.750> working<00:21:08.990> when<00:21:09.260> we<00:21:09.350> can<00:21:09.470> test<00:21:09.710> that<00:21:09.860> stuff 00:21:10.120 --> 00:21:10.130 align:start position:0% all working when we can test that stuff 00:21:10.130 --> 00:21:12.340 align:start position:0% all working when we can test that stuff on<00:21:10.310> local<00:21:10.730> dev<00:21:10.880> before<00:21:11.540> we<00:21:11.660> even<00:21:11.810> want<00:21:12.050> to<00:21:12.140> have 00:21:12.340 --> 00:21:12.350 align:start position:0% on local dev before we even want to have 00:21:12.350 --> 00:21:14.350 align:start position:0% on local dev before we even want to have been<00:21:12.470> changed<00:21:12.860> to<00:21:13.040> do<00:21:13.700> something<00:21:14.060> whether<00:21:14.210> it 00:21:14.350 --> 00:21:14.360 align:start position:0% been changed to do something whether it 00:21:14.360 --> 00:21:16.600 align:start position:0% been changed to do something whether it be<00:21:14.390> private<00:21:14.720> or<00:21:14.810> public<00:21:15.280> we<00:21:16.280> mentioned<00:21:16.580> a 00:21:16.600 --> 00:21:16.610 align:start position:0% be private or public we mentioned a 00:21:16.610 --> 00:21:19.500 align:start position:0% be private or public we mentioned a private<00:21:16.910> consortiums<00:21:18.130> Estonian<00:21:19.130> eyes 00:21:19.500 --> 00:21:19.510 align:start position:0% private consortiums Estonian eyes 00:21:19.510 --> 00:21:22.600 align:start position:0% private consortiums Estonian eyes tightly<00:21:20.510> comes<00:21:20.840> to<00:21:21.080> Azure<00:21:21.400> certainly<00:21:22.400> Azure 00:21:22.600 --> 00:21:22.610 align:start position:0% tightly comes to Azure certainly Azure 00:21:22.610 --> 00:21:25.390 align:start position:0% tightly comes to Azure certainly Azure is<00:21:22.880> a<00:21:23.000> nice<00:21:23.870> experience<00:21:24.050> in<00:21:24.620> here<00:21:24.860> but 00:21:25.390 --> 00:21:25.400 align:start position:0% is a nice experience in here but 00:21:25.400 --> 00:21:27.120 align:start position:0% is a nice experience in here but certainly<00:21:25.610> you<00:21:26.000> can<00:21:26.150> also<00:21:26.300> plug<00:21:26.600> this<00:21:26.780> into 00:21:27.120 --> 00:21:27.130 align:start position:0% certainly you can also plug this into 00:21:27.130 --> 00:21:28.960 align:start position:0% certainly you can also plug this into existing<00:21:28.130> notes<00:21:28.310> if<00:21:28.460> you<00:21:28.490> have<00:21:28.610> them<00:21:28.760> running 00:21:28.960 --> 00:21:28.970 align:start position:0% existing notes if you have them running 00:21:28.970 --> 00:21:30.460 align:start position:0% existing notes if you have them running on<00:21:29.120> premises<00:21:29.630> or<00:21:29.840> something<00:21:30.170> of<00:21:30.290> that<00:21:30.320> nature 00:21:30.460 --> 00:21:30.470 align:start position:0% on premises or something of that nature 00:21:30.470 --> 00:21:32.980 align:start position:0% on premises or something of that nature so<00:21:31.040> don't<00:21:31.610> think<00:21:31.790> of<00:21:31.910> this<00:21:32.030> I<00:21:32.240> did<00:21:32.660> hear<00:21:32.810> some 00:21:32.980 --> 00:21:32.990 align:start position:0% so don't think of this I did hear some 00:21:32.990 --> 00:21:34.870 align:start position:0% so don't think of this I did hear some feedback<00:21:33.140> people<00:21:33.680> say<00:21:33.830> let's<00:21:34.340> go<00:21:34.460> -<00:21:34.670> you're<00:21:34.820> in 00:21:34.870 --> 00:21:34.880 align:start position:0% feedback people say let's go - you're in 00:21:34.880 --> 00:21:36.760 align:start position:0% feedback people say let's go - you're in there<00:21:35.120> that<00:21:35.390> scares<00:21:35.480> me<00:21:35.750> you<00:21:36.080> know<00:21:36.140> somebody 00:21:36.760 --> 00:21:36.770 align:start position:0% there that scares me you know somebody 00:21:36.770 --> 00:21:42.190 align:start position:0% there that scares me you know somebody defiled<00:21:37.400> Roger<00:21:40.420> as<00:21:41.420> you're<00:21:41.630> just<00:21:41.840> a<00:21:41.960> great 00:21:42.190 --> 00:21:42.200 align:start position:0% defiled Roger as you're just a great 00:21:42.200 --> 00:21:44.380 align:start position:0% defiled Roger as you're just a great place<00:21:42.440> to<00:21:42.470> run<00:21:42.800> your<00:21:42.950> stuff<00:21:43.190> but<00:21:44.060> if<00:21:44.150> you<00:21:44.270> just 00:21:44.380 --> 00:21:44.390 align:start position:0% place to run your stuff but if you just 00:21:44.390 --> 00:21:45.640 align:start position:0% place to run your stuff but if you just want<00:21:44.570> to<00:21:44.600> run<00:21:44.720> this<00:21:44.840> stuff<00:21:44.990> local<00:21:45.410> there<00:21:45.500> are 00:21:45.640 --> 00:21:45.650 align:start position:0% want to run this stuff local there are 00:21:45.650 --> 00:21:49.810 align:start position:0% want to run this stuff local there are around<00:21:46.400> premises<00:21:47.140> as<00:21:48.140> well<00:21:48.350> and<00:21:49.160> which<00:21:49.610> raises 00:21:49.810 --> 00:21:49.820 align:start position:0% around premises as well and which raises 00:21:49.820 --> 00:21:51.680 align:start position:0% around premises as well and which raises to<00:21:50.090> the<00:21:50.120> third<00:21:50.300> box<00:21:50.540> which<00:21:50.990> is<00:21:51.170> a 00:21:51.680 --> 00:21:51.690 align:start position:0% to the third box which is a 00:21:51.690 --> 00:21:53.749 align:start position:0% to the third box which is a we<00:21:52.019> announced<00:21:52.379> in<00:21:52.500> May<00:21:52.740> has<00:21:53.549> your<00:21:53.669> blood 00:21:53.749 --> 00:21:53.759 align:start position:0% we announced in May has your blood 00:21:53.759 --> 00:21:56.509 align:start position:0% we announced in May has your blood change<00:21:54.090> service<00:21:54.480> so<00:21:55.320> don't<00:21:55.919> take<00:21:56.100> away<00:21:56.250> if<00:21:56.429> you 00:21:56.509 --> 00:21:56.519 align:start position:0% change service so don't take away if you 00:21:56.519 --> 00:21:57.889 align:start position:0% change service so don't take away if you don't<00:21:56.639> know<00:21:56.850> anything<00:21:57.120> about<00:21:57.210> this<00:21:57.480> we're<00:21:57.690> not 00:21:57.889 --> 00:21:57.899 align:start position:0% don't know anything about this we're not 00:21:57.899 --> 00:22:00.830 align:start position:0% don't know anything about this we're not building<00:21:58.500> a<00:21:58.740> ledger<00:21:58.919> ourselves<00:21:59.669> so<00:22:00.570> this<00:22:00.720> is 00:22:00.830 --> 00:22:00.840 align:start position:0% building a ledger ourselves so this is 00:22:00.840 --> 00:22:02.899 align:start position:0% building a ledger ourselves so this is kind<00:22:01.019> of<00:22:01.049> like<00:22:01.200> quorum<00:22:01.529> and<00:22:01.950> essentially<00:22:02.639> what 00:22:02.899 --> 00:22:02.909 align:start position:0% kind of like quorum and essentially what 00:22:02.909 --> 00:22:05.350 align:start position:0% kind of like quorum and essentially what this<00:22:03.029> is<00:22:03.090> is<00:22:03.299> for<00:22:03.899> some<00:22:04.139> users<00:22:04.409> as<00:22:04.740> they<00:22:04.769> I 00:22:05.350 --> 00:22:05.360 align:start position:0% this is is for some users as they I 00:22:05.360 --> 00:22:07.490 align:start position:0% this is is for some users as they I trust<00:22:06.360> you<00:22:06.509> enough<00:22:06.750> so<00:22:06.929> that<00:22:06.960> you<00:22:07.110> can<00:22:07.139> run<00:22:07.379> my 00:22:07.490 --> 00:22:07.500 align:start position:0% trust you enough so that you can run my 00:22:07.500 --> 00:22:09.470 align:start position:0% trust you enough so that you can run my notes<00:22:07.799> for<00:22:07.950> me<00:22:08.100> just<00:22:08.789> front<00:22:08.940> windows<00:22:09.240> for<00:22:09.450> me 00:22:09.470 --> 00:22:09.480 align:start position:0% notes for me just front windows for me 00:22:09.480 --> 00:22:12.350 align:start position:0% notes for me just front windows for me as<00:22:09.659> a<00:22:09.750> pastor<00:22:10.049> as<00:22:10.710> opposed<00:22:11.129> to<00:22:11.250> me<00:22:11.429> having<00:22:11.759> a<00:22:12.000> VM 00:22:12.350 --> 00:22:12.360 align:start position:0% as a pastor as opposed to me having a VM 00:22:12.360 --> 00:22:13.669 align:start position:0% as a pastor as opposed to me having a VM that<00:22:12.389> I<00:22:12.690> have<00:22:12.840> to<00:22:12.929> maintain<00:22:13.080> there<00:22:13.500> and 00:22:13.669 --> 00:22:13.679 align:start position:0% that I have to maintain there and 00:22:13.679 --> 00:22:16.310 align:start position:0% that I have to maintain there and manager<00:22:14.129> can<00:22:15.029> still<00:22:15.240> do<00:22:15.330> the<00:22:15.419> VM<00:22:15.659> stuff<00:22:15.899> so 00:22:16.310 --> 00:22:16.320 align:start position:0% manager can still do the VM stuff so 00:22:16.320 --> 00:22:17.690 align:start position:0% manager can still do the VM stuff so people<00:22:16.679> want<00:22:16.830> to<00:22:16.889> have<00:22:17.039> their<00:22:17.129> hands<00:22:17.429> on<00:22:17.519> all 00:22:17.690 --> 00:22:17.700 align:start position:0% people want to have their hands on all 00:22:17.700 --> 00:22:19.430 align:start position:0% people want to have their hands on all the<00:22:17.909> internals<00:22:18.870> and<00:22:18.990> make<00:22:19.110> sure<00:22:19.230> that<00:22:19.320> that 00:22:19.430 --> 00:22:19.440 align:start position:0% the internals and make sure that that 00:22:19.440 --> 00:22:21.680 align:start position:0% the internals and make sure that that works<00:22:19.679> totally<00:22:20.129> fine<00:22:20.490> you<00:22:20.639> can<00:22:20.789> run<00:22:20.940> that<00:22:21.120> this 00:22:21.680 --> 00:22:21.690 align:start position:0% works totally fine you can run that this 00:22:21.690 --> 00:22:23.570 align:start position:0% works totally fine you can run that this is<00:22:21.870> something<00:22:22.049> that's<00:22:22.409> a<00:22:22.559> little<00:22:23.100> bit<00:22:23.220> faster 00:22:23.570 --> 00:22:23.580 align:start position:0% is something that's a little bit faster 00:22:23.580 --> 00:22:25.490 align:start position:0% is something that's a little bit faster so<00:22:24.389> maybe<00:22:24.539> you<00:22:24.690> can<00:22:24.809> even<00:22:24.960> use<00:22:25.110> it<00:22:25.230> for<00:22:25.350> dev 00:22:25.490 --> 00:22:25.500 align:start position:0% so maybe you can even use it for dev 00:22:25.500 --> 00:22:27.499 align:start position:0% so maybe you can even use it for dev test<00:22:25.710> certainly<00:22:26.610> introduction<00:22:27.120> people<00:22:27.360> want 00:22:27.499 --> 00:22:27.509 align:start position:0% test certainly introduction people want 00:22:27.509 --> 00:22:28.879 align:start position:0% test certainly introduction people want to<00:22:27.600> use<00:22:27.690> this<00:22:27.870> because<00:22:28.259> there's<00:22:28.470> a<00:22:28.559> highly 00:22:28.879 --> 00:22:28.889 align:start position:0% to use this because there's a highly 00:22:28.889 --> 00:22:31.159 align:start position:0% to use this because there's a highly available<00:22:29.100> solution<00:22:29.940> here<00:22:30.120> so<00:22:30.389> basically 00:22:31.159 --> 00:22:31.169 align:start position:0% available solution here so basically 00:22:31.169 --> 00:22:32.389 align:start position:0% available solution here so basically we're<00:22:31.440> making<00:22:31.559> sure<00:22:31.860> those<00:22:32.009> nodes<00:22:32.250> are 00:22:32.389 --> 00:22:32.399 align:start position:0% we're making sure those nodes are 00:22:32.399 --> 00:22:34.430 align:start position:0% we're making sure those nodes are healthy<00:22:32.730> and<00:22:32.879> running<00:22:33.179> you<00:22:34.080> can<00:22:34.110> think<00:22:34.379> about 00:22:34.430 --> 00:22:34.440 align:start position:0% healthy and running you can think about 00:22:34.440 --> 00:22:35.960 align:start position:0% healthy and running you can think about other<00:22:34.620> services<00:22:35.129> who<00:22:35.279> do<00:22:35.429> something<00:22:35.759> similar 00:22:35.960 --> 00:22:35.970 align:start position:0% other services who do something similar 00:22:35.970 --> 00:22:37.580 align:start position:0% other services who do something similar where<00:22:36.269> there<00:22:36.389> is<00:22:36.509> steam<00:22:36.690> in<00:22:36.840> it<00:22:36.929> for<00:22:37.200> you<00:22:37.350> this 00:22:37.580 --> 00:22:37.590 align:start position:0% where there is steam in it for you this 00:22:37.590 --> 00:22:41.240 align:start position:0% where there is steam in it for you this is<00:22:37.769> Microsoft<00:22:38.460> version<00:22:39.919> and<00:22:40.919> then<00:22:41.039> on<00:22:41.159> the 00:22:41.240 --> 00:22:41.250 align:start position:0% is Microsoft version and then on the 00:22:41.250 --> 00:22:43.519 align:start position:0% is Microsoft version and then on the public<00:22:41.519> side<00:22:41.759> you<00:22:42.690> know<00:22:42.779> we<00:22:42.990> talked<00:22:43.440> about 00:22:43.519 --> 00:22:43.529 align:start position:0% public side you know we talked about 00:22:43.529 --> 00:22:44.990 align:start position:0% public side you know we talked about this<00:22:43.830> because<00:22:44.070> we<00:22:44.190> don't<00:22:44.399> want<00:22:44.610> to<00:22:44.639> build<00:22:44.850> any 00:22:44.990 --> 00:22:45.000 align:start position:0% this because we don't want to build any 00:22:45.000 --> 00:22:47.779 align:start position:0% this because we don't want to build any barriers<00:22:45.419> in<00:22:45.629> here<00:22:45.889> certainly<00:22:46.889> Microsoft's 00:22:47.779 --> 00:22:47.789 align:start position:0% barriers in here certainly Microsoft's 00:22:47.789 --> 00:22:50.210 align:start position:0% barriers in here certainly Microsoft's bread<00:22:48.149> butter<00:22:48.389> is<00:22:48.570> enterprise<00:22:48.809> and<00:22:49.769> having 00:22:50.210 --> 00:22:50.220 align:start position:0% bread butter is enterprise and having 00:22:50.220 --> 00:22:51.680 align:start position:0% bread butter is enterprise and having these<00:22:50.340> big<00:22:50.549> enterprises<00:22:51.000> engaging 00:22:51.680 --> 00:22:51.690 align:start position:0% these big enterprises engaging 00:22:51.690 --> 00:22:54.139 align:start position:0% these big enterprises engaging blockchain<00:22:52.230> technology<00:22:52.799> but<00:22:53.460> we<00:22:53.759> also<00:22:53.909> don't 00:22:54.139 --> 00:22:54.149 align:start position:0% blockchain technology but we also don't 00:22:54.149 --> 00:22:55.549 align:start position:0% blockchain technology but we also don't want<00:22:54.240> to<00:22:54.419> sever<00:22:54.600> off<00:22:54.840> anybody<00:22:55.230> from<00:22:55.440> the 00:22:55.549 --> 00:22:55.559 align:start position:0% want to sever off anybody from the 00:22:55.559 --> 00:22:57.049 align:start position:0% want to sever off anybody from the public<00:22:55.860> side<00:22:56.039> they<00:22:56.250> should<00:22:56.279> also<00:22:56.580> use<00:22:56.730> this 00:22:57.049 --> 00:22:57.059 align:start position:0% public side they should also use this 00:22:57.059 --> 00:22:58.490 align:start position:0% public side they should also use this tool<00:22:57.299> we<00:22:57.600> want<00:22:57.720> to<00:22:57.840> make<00:22:57.960> sure<00:22:57.990> that<00:22:58.289> it's 00:22:58.490 --> 00:22:58.500 align:start position:0% tool we want to make sure that it's 00:22:58.500 --> 00:23:01.340 align:start position:0% tool we want to make sure that it's amenable<00:22:58.919> to<00:22:58.980> this<00:22:59.309> and<00:23:00.240> so<00:23:00.870> on<00:23:00.960> the<00:23:01.049> public 00:23:01.340 --> 00:23:01.350 align:start position:0% amenable to this and so on the public 00:23:01.350 --> 00:23:03.789 align:start position:0% amenable to this and so on the public side<00:23:01.730> something<00:23:02.730> we're<00:23:02.850> launching<00:23:03.210> this<00:23:03.360> week 00:23:03.789 --> 00:23:03.799 align:start position:0% side something we're launching this week 00:23:03.799 --> 00:23:06.169 align:start position:0% side something we're launching this week we<00:23:04.799> haven't<00:23:05.039> kind<00:23:05.340> of<00:23:05.399> talked<00:23:05.639> about<00:23:05.730> it<00:23:05.909> yet 00:23:06.169 --> 00:23:06.179 align:start position:0% we haven't kind of talked about it yet 00:23:06.179 --> 00:23:08.749 align:start position:0% we haven't kind of talked about it yet is<00:23:06.360> that<00:23:06.750> we're<00:23:07.259> going<00:23:07.350> to<00:23:07.470> tiara<00:23:07.889> so<00:23:08.220> we've 00:23:08.749 --> 00:23:08.759 align:start position:0% is that we're going to tiara so we've 00:23:08.759 --> 00:23:09.830 align:start position:0% is that we're going to tiara so we've been<00:23:08.850> working<00:23:09.000> with<00:23:09.299> them<00:23:09.419> for<00:23:09.450> some<00:23:09.779> time 00:23:09.830 --> 00:23:09.840 align:start position:0% been working with them for some time 00:23:09.840 --> 00:23:11.990 align:start position:0% been working with them for some time what<00:23:10.679> we<00:23:10.769> wanted<00:23:11.009> to<00:23:11.070> smooth<00:23:11.370> that<00:23:11.519> process 00:23:11.990 --> 00:23:12.000 align:start position:0% what we wanted to smooth that process 00:23:12.000 --> 00:23:13.100 align:start position:0% what we wanted to smooth that process not<00:23:12.149> much<00:23:12.360> more<00:23:12.570> from 00:23:13.100 --> 00:23:13.110 align:start position:0% not much more from 00:23:13.110 --> 00:23:15.050 align:start position:0% not much more from so<00:23:13.410> I'll<00:23:14.010> show<00:23:14.310> you<00:23:14.340> what<00:23:14.610> it<00:23:14.670> looks<00:23:14.790> like<00:23:14.910> from 00:23:15.050 --> 00:23:15.060 align:start position:0% so I'll show you what it looks like from 00:23:15.060 --> 00:23:16.310 align:start position:0% so I'll show you what it looks like from the<00:23:15.210> hazard<00:23:15.480> walking<00:23:15.870> service 00:23:16.310 --> 00:23:16.320 align:start position:0% the hazard walking service 00:23:16.320 --> 00:23:19.280 align:start position:0% the hazard walking service Charon<00:23:16.800> is<00:23:16.890> nearly<00:23:17.730> identical<00:23:18.290> so 00:23:19.280 --> 00:23:19.290 align:start position:0% Charon is nearly identical so 00:23:19.290 --> 00:23:20.960 align:start position:0% Charon is nearly identical so essentially<00:23:19.740> it's<00:23:20.010> down<00:23:20.190> to<00:23:20.430> the<00:23:20.580> couple 00:23:20.960 --> 00:23:20.970 align:start position:0% essentially it's down to the couple 00:23:20.970 --> 00:23:23.390 align:start position:0% essentially it's down to the couple clicks<00:23:21.150> and<00:23:21.450> you<00:23:22.170> can<00:23:22.350> have<00:23:22.500> yourself<00:23:22.860> in<00:23:23.040> fear 00:23:23.390 --> 00:23:23.400 align:start position:0% clicks and you can have yourself in fear 00:23:23.400 --> 00:23:24.830 align:start position:0% clicks and you can have yourself in fear without<00:23:23.760> having<00:23:24.150> to<00:23:24.210> jump<00:23:24.240> to<00:23:24.480> any<00:23:24.630> other 00:23:24.830 --> 00:23:24.840 align:start position:0% without having to jump to any other 00:23:24.840 --> 00:23:29.390 align:start position:0% without having to jump to any other website<00:23:24.960> even<00:23:25.530> if<00:23:25.590> you're<00:23:25.740> new<00:23:25.890> to<00:23:25.920> in<00:23:26.190> fear<00:23:26.460> up 00:23:29.390 --> 00:23:29.400 align:start position:0% 00:23:29.400 --> 00:23:31.860 align:start position:0% public<00:23:30.400> networks<00:23:30.730> and<00:23:31.240> I<00:23:31.450> know<00:23:31.510> there's<00:23:31.810> only 00:23:31.860 --> 00:23:31.870 align:start position:0% public networks and I know there's only 00:23:31.870 --> 00:23:33.420 align:start position:0% public networks and I know there's only winners<00:23:32.260> we've<00:23:32.470> been<00:23:32.590> talking<00:23:32.950> to<00:23:33.070> as<00:23:33.220> well 00:23:33.420 --> 00:23:33.430 align:start position:0% winners we've been talking to as well 00:23:33.430 --> 00:23:35.910 align:start position:0% winners we've been talking to as well who<00:23:33.670> also<00:23:33.850> in<00:23:34.300> this<00:23:34.630> work<00:23:35.500> with<00:23:35.650> you<00:23:35.740> guys<00:23:35.770> to 00:23:35.910 --> 00:23:35.920 align:start position:0% who also in this work with you guys to 00:23:35.920 --> 00:23:37.650 align:start position:0% who also in this work with you guys to of<00:23:36.310> course<00:23:36.490> the<00:23:36.580> architectures<00:23:37.150> bill<00:23:37.420> to 00:23:37.650 --> 00:23:37.660 align:start position:0% of course the architectures bill to 00:23:37.660 --> 00:23:44.580 align:start position:0% of course the architectures bill to cover<00:23:38.380> you<00:23:39.010> know<00:23:39.070> no<00:23:39.700> providers<00:23:40.210> into<00:23:40.420> that<00:23:43.590> so 00:23:44.580 --> 00:23:44.590 align:start position:0% cover you know no providers into that so 00:23:44.590 --> 00:23:47.070 align:start position:0% cover you know no providers into that so this<00:23:45.400> is<00:23:45.460> kind<00:23:45.970> of<00:23:46.000> like<00:23:46.180> our<00:23:46.300> honeycomb<00:23:46.630> as<00:23:46.960> we 00:23:47.070 --> 00:23:47.080 align:start position:0% this is kind of like our honeycomb as we 00:23:47.080 --> 00:23:48.600 align:start position:0% this is kind of like our honeycomb as we call<00:23:47.290> it<00:23:47.470> which<00:23:47.650> basically<00:23:47.800> looks<00:23:48.280> like<00:23:48.490> the 00:23:48.600 --> 00:23:48.610 align:start position:0% call it which basically looks like the 00:23:48.610 --> 00:23:50.160 align:start position:0% call it which basically looks like the stickers<00:23:48.940> on<00:23:49.090> people's<00:23:49.420> laptops<00:23:49.630> but 00:23:50.160 --> 00:23:50.170 align:start position:0% stickers on people's laptops but 00:23:50.170 --> 00:23:52.800 align:start position:0% stickers on people's laptops but basically<00:23:51.130> just<00:23:51.250> the<00:23:51.970> the<00:23:52.210> key<00:23:52.360> points<00:23:52.750> I 00:23:52.800 --> 00:23:52.810 align:start position:0% basically just the the key points I 00:23:52.810 --> 00:23:54.240 align:start position:0% basically just the the key points I wanted<00:23:53.020> to<00:23:53.110> kill<00:23:53.230> and<00:23:53.470> I<00:23:53.560> hit<00:23:53.770> on<00:23:53.920> some<00:23:54.160> of 00:23:54.240 --> 00:23:54.250 align:start position:0% wanted to kill and I hit on some of 00:23:54.250 --> 00:23:55.860 align:start position:0% wanted to kill and I hit on some of these<00:23:54.340> earlier<00:23:54.820> but<00:23:55.000> just<00:23:55.180> hit<00:23:55.360> on<00:23:55.540> most<00:23:55.750> of 00:23:55.860 --> 00:23:55.870 align:start position:0% these earlier but just hit on most of 00:23:55.870 --> 00:23:57.900 align:start position:0% these earlier but just hit on most of them<00:23:56.020> and<00:23:56.200> we<00:23:56.410> have<00:23:56.560> the<00:23:56.770> the<00:23:57.340> answer<00:23:57.610> market 00:23:57.900 --> 00:23:57.910 align:start position:0% them and we have the the answer market 00:23:57.910 --> 00:23:59.790 align:start position:0% them and we have the the answer market service<00:23:58.210> integration<00:23:58.510> penalty<00:23:58.900> project<00:23:59.440> we 00:23:59.790 --> 00:23:59.800 align:start position:0% service integration penalty project we 00:23:59.800 --> 00:24:01.290 align:start position:0% service integration penalty project we have<00:23:59.950> all<00:24:00.070> those<00:24:00.190> language<00:24:00.700> defects<00:24:01.090> and 00:24:01.290 --> 00:24:01.300 align:start position:0% have all those language defects and 00:24:01.300 --> 00:24:02.790 align:start position:0% have all those language defects and Lenti<00:24:01.690> compilation<00:24:02.350> of<00:24:02.380> those<00:24:02.530> things 00:24:02.790 --> 00:24:02.800 align:start position:0% Lenti compilation of those things 00:24:02.800 --> 00:24:04.290 align:start position:0% Lenti compilation of those things happening<00:24:03.190> we<00:24:03.340> have<00:24:03.430> a<00:24:03.460> debugger<00:24:03.790> and<00:24:03.940> built 00:24:04.290 --> 00:24:04.300 align:start position:0% happening we have a debugger and built 00:24:04.300 --> 00:24:05.550 align:start position:0% happening we have a debugger and built in<00:24:04.450> there<00:24:04.630> is<00:24:04.780> you<00:24:04.900> can<00:24:05.050> see<00:24:05.200> that<00:24:05.350> as<00:24:05.470> well 00:24:05.550 --> 00:24:05.560 align:start position:0% in there is you can see that as well 00:24:05.560 --> 00:24:08.040 align:start position:0% in there is you can see that as well I'll<00:24:05.740> show<00:24:05.950> you<00:24:06.010> that<00:24:06.420> any<00:24:07.420> kind<00:24:07.690> of<00:24:07.780> different 00:24:08.040 --> 00:24:08.050 align:start position:0% I'll show you that any kind of different 00:24:08.050 --> 00:24:10.110 align:start position:0% I'll show you that any kind of different changes<00:24:08.320> you<00:24:08.440> want<00:24:08.530> to<00:24:08.620> deploy<00:24:08.830> to<00:24:09.120> working 00:24:10.110 --> 00:24:10.120 align:start position:0% changes you want to deploy to working 00:24:10.120 --> 00:24:12.120 align:start position:0% changes you want to deploy to working like<00:24:10.240> everything<00:24:10.600> from<00:24:10.630> the<00:24:10.840> for<00:24:11.050> tape<00:24:11.290> so<00:24:12.010> if 00:24:12.120 --> 00:24:12.130 align:start position:0% like everything from the for tape so if 00:24:12.130 --> 00:24:13.170 align:start position:0% like everything from the for tape so if you<00:24:12.190> guys<00:24:12.340> are<00:24:12.400> familiar<00:24:12.640> with<00:24:12.940> our 00:24:13.170 --> 00:24:13.180 align:start position:0% you guys are familiar with our 00:24:13.180 --> 00:24:15.390 align:start position:0% you guys are familiar with our chocolates<00:24:13.870> been<00:24:14.050> doing<00:24:14.260> in<00:24:14.380> that<00:24:14.410> space<00:24:14.620> this 00:24:15.390 --> 00:24:15.400 align:start position:0% chocolates been doing in that space this 00:24:15.400 --> 00:24:16.890 align:start position:0% chocolates been doing in that space this is<00:24:15.520> pretty<00:24:15.730> interesting<00:24:16.030> so<00:24:16.480> you<00:24:16.540> can<00:24:16.750> have 00:24:16.890 --> 00:24:16.900 align:start position:0% is pretty interesting so you can have 00:24:16.900 --> 00:24:18.810 align:start position:0% is pretty interesting so you can have your<00:24:17.140> induction<00:24:17.590> environment<00:24:18.250> which<00:24:18.610> could 00:24:18.810 --> 00:24:18.820 align:start position:0% your induction environment which could 00:24:18.820 --> 00:24:21.120 align:start position:0% your induction environment which could even<00:24:19.000> be<00:24:19.120> public<00:24:19.420> watching<00:24:19.840> or<00:24:20.770> it<00:24:20.890> could<00:24:21.010> be<00:24:21.070> a 00:24:21.120 --> 00:24:21.130 align:start position:0% even be public watching or it could be a 00:24:21.130 --> 00:24:22.860 align:start position:0% even be public watching or it could be a private<00:24:21.490> when<00:24:21.640> it's<00:24:21.790> in<00:24:21.910> production<00:24:22.090> you 00:24:22.860 --> 00:24:22.870 align:start position:0% private when it's in production you 00:24:22.870 --> 00:24:24.600 align:start position:0% private when it's in production you essentially<00:24:23.230> for<00:24:23.530> that<00:24:23.740> change<00:24:24.010> make<00:24:24.430> your 00:24:24.600 --> 00:24:24.610 align:start position:0% essentially for that change make your 00:24:24.610 --> 00:24:26.280 align:start position:0% essentially for that change make your changes<00:24:24.910> to<00:24:25.030> your<00:24:25.120> code<00:24:25.300> tested<00:24:25.930> yep 00:24:26.280 --> 00:24:26.290 align:start position:0% changes to your code tested yep 00:24:26.290 --> 00:24:27.990 align:start position:0% changes to your code tested yep everything's<00:24:26.680> working<00:24:27.070> destroy<00:24:27.340> your<00:24:27.520> form 00:24:27.990 --> 00:24:28.000 align:start position:0% everything's working destroy your form 00:24:28.000 --> 00:24:32.250 align:start position:0% everything's working destroy your form push<00:24:28.390> your<00:24:28.540> changes<00:24:28.660> either<00:24:29.020> public<00:24:29.590> or<00:24:29.620> push 00:24:32.250 --> 00:24:32.260 align:start position:0% 00:24:32.260 --> 00:24:34.140 align:start position:0% to<00:24:32.620> what<00:24:32.890> automate<00:24:33.220> that<00:24:33.400> little<00:24:33.700> bit<00:24:33.790> more<00:24:33.820> we 00:24:34.140 --> 00:24:34.150 align:start position:0% to what automate that little bit more we 00:24:34.150 --> 00:24:37.110 align:start position:0% to what automate that little bit more we definitely<00:24:34.570> have<00:24:34.660> to<00:24:35.430> so<00:24:36.430> the<00:24:36.520> smart<00:24:36.730> contract 00:24:37.110 --> 00:24:37.120 align:start position:0% definitely have to so the smart contract 00:24:37.120 --> 00:24:38.640 align:start position:0% definitely have to so the smart contract test<00:24:37.360> execution<00:24:37.660> I've<00:24:38.110> mentioned<00:24:38.440> some 00:24:38.640 --> 00:24:38.650 align:start position:0% test execution I've mentioned some 00:24:38.650 --> 00:24:40.380 align:start position:0% test execution I've mentioned some editors<00:24:38.980> were<00:24:39.100> working<00:24:39.400> with<00:24:39.580> their<00:24:39.850> once 00:24:40.380 --> 00:24:40.390 align:start position:0% editors were working with their once 00:24:40.390 --> 00:24:41.760 align:start position:0% editors were working with their once their<00:24:40.540> workers<00:24:40.780> would<00:24:40.990> like<00:24:41.140> some<00:24:41.320> walnut 00:24:41.760 --> 00:24:41.770 align:start position:0% their workers would like some walnut 00:24:41.770 --> 00:24:43.920 align:start position:0% their workers would like some walnut vendors<00:24:42.580> as<00:24:42.730> well<00:24:42.760> truffle<00:24:43.420> is<00:24:43.510> one<00:24:43.660> of<00:24:43.780> them 00:24:43.920 --> 00:24:43.930 align:start position:0% vendors as well truffle is one of them 00:24:43.930 --> 00:24:45.480 align:start position:0% vendors as well truffle is one of them we've<00:24:44.170> been<00:24:44.290> working<00:24:44.650> with<00:24:44.680> them<00:24:44.950> to<00:24:45.010> improve 00:24:45.480 --> 00:24:45.490 align:start position:0% we've been working with them to improve 00:24:45.490 --> 00:24:48.000 align:start position:0% we've been working with them to improve the<00:24:45.700> truffle<00:24:46.060> HD<00:24:46.330> walnut<00:24:46.570> experience<00:24:47.050> all 00:24:48.000 --> 00:24:48.010 align:start position:0% the truffle HD walnut experience all 00:24:48.010 --> 00:24:49.560 align:start position:0% the truffle HD walnut experience all support<00:24:48.430> us<00:24:48.490> is<00:24:48.850> another<00:24:49.180> one<00:24:49.330> that<00:24:49.360> we're 00:24:49.560 --> 00:24:49.570 align:start position:0% support us is another one that we're 00:24:49.570 --> 00:24:52.430 align:start position:0% support us is another one that we're working<00:24:49.720> with<00:24:49.900> it<00:24:50.590> was<00:24:51.010> base<00:24:51.190> to<00:24:51.460> improve<00:24:52.030> that 00:24:52.430 --> 00:24:52.440 align:start position:0% working with it was base to improve that 00:24:52.440 --> 00:24:54.630 align:start position:0% working with it was base to improve that we<00:24:53.440> also<00:24:53.560> have<00:24:53.800> these<00:24:53.890> like<00:24:54.160> logical 00:24:54.630 --> 00:24:54.640 align:start position:0% we also have these like logical 00:24:54.640 --> 00:24:56.580 align:start position:0% we also have these like logical integration<00:24:55.540> they<00:24:55.690> was<00:24:56.020> talking<00:24:56.290> about<00:24:56.350> some 00:24:56.580 --> 00:24:56.590 align:start position:0% integration they was talking about some 00:24:56.590 --> 00:24:57.870 align:start position:0% integration they was talking about some of<00:24:56.650> these<00:24:56.770> server<00:24:57.070> list<00:24:57.340> things<00:24:57.550> I'll<00:24:57.850> show 00:24:57.870 --> 00:24:57.880 align:start position:0% of these server list things I'll show 00:24:57.880 --> 00:25:02.490 align:start position:0% of these server list things I'll show you<00:24:58.120> what<00:24:58.300> we<00:25:00.270> basically<00:25:01.270> if<00:25:01.930> you<00:25:02.050> build<00:25:02.230> smart 00:25:02.490 --> 00:25:02.500 align:start position:0% you what we basically if you build smart 00:25:02.500 --> 00:25:04.590 align:start position:0% you what we basically if you build smart contract<00:25:03.010> anyone<00:25:03.700> like<00:25:03.940> interoperate<00:25:04.570> with 00:25:04.590 --> 00:25:04.600 align:start position:0% contract anyone like interoperate with 00:25:04.600 --> 00:25:06.690 align:start position:0% contract anyone like interoperate with it<00:25:04.900> we<00:25:05.080> have<00:25:05.260> a<00:25:05.290> contract<00:25:05.860> interaction<00:25:06.580> we 00:25:06.690 --> 00:25:06.700 align:start position:0% it we have a contract interaction we 00:25:06.700 --> 00:25:08.730 align:start position:0% it we have a contract interaction we call<00:25:06.880> it<00:25:07.060> which<00:25:07.540> basically<00:25:07.870> built<00:25:08.200> a<00:25:08.320> you<00:25:08.590> will 00:25:08.730 --> 00:25:08.740 align:start position:0% call it which basically built a you will 00:25:08.740 --> 00:25:10.590 align:start position:0% call it which basically built a you will have<00:25:08.860> apply<00:25:09.190> for<00:25:09.460> you<00:25:09.550> of<00:25:09.760> adhesions<00:25:10.210> to<00:25:10.300> test 00:25:10.590 --> 00:25:10.600 align:start position:0% have apply for you of adhesions to test 00:25:10.600 --> 00:25:12.120 align:start position:0% have apply for you of adhesions to test your<00:25:10.780> contract<00:25:11.170> and<00:25:11.350> certainly<00:25:11.710> playing<00:25:11.920> with 00:25:12.120 --> 00:25:12.130 align:start position:0% your contract and certainly playing with 00:25:12.130 --> 00:25:14.580 align:start position:0% your contract and certainly playing with the<00:25:12.250> decedent's<00:25:12.760> working<00:25:13.120> but<00:25:14.050> then<00:25:14.230> on<00:25:14.410> top 00:25:14.580 --> 00:25:14.590 align:start position:0% the decedent's working but then on top 00:25:14.590 --> 00:25:16.740 align:start position:0% the decedent's working but then on top of<00:25:14.650> that<00:25:14.770> you<00:25:15.280> know<00:25:15.400> I<00:25:15.670> want<00:25:15.880> to<00:25:15.940> wrap<00:25:16.120> that<00:25:16.360> in 00:25:16.740 --> 00:25:16.750 align:start position:0% of that you know I want to wrap that in 00:25:16.750 --> 00:25:18.900 align:start position:0% of that you know I want to wrap that in a<00:25:16.870> service<00:25:17.200> function<00:25:17.590> so<00:25:18.130> that<00:25:18.310> the<00:25:18.490> functions 00:25:18.900 --> 00:25:18.910 align:start position:0% a service function so that the functions 00:25:18.910 --> 00:25:20.850 align:start position:0% a service function so that the functions are<00:25:19.030> really<00:25:19.390> these<00:25:19.720> logic<00:25:20.140> active<00:25:20.470> functions 00:25:20.850 --> 00:25:20.860 align:start position:0% are really these logic active functions 00:25:20.860 --> 00:25:22.680 align:start position:0% are really these logic active functions are<00:25:20.980> really<00:25:21.310> just<00:25:21.460> like<00:25:21.580> crowd<00:25:21.880> operations<00:25:22.420> to 00:25:22.680 --> 00:25:22.690 align:start position:0% are really just like crowd operations to 00:25:22.690 --> 00:25:24.930 align:start position:0% are really just like crowd operations to a<00:25:22.720> blockchain<00:25:23.130> producer<00:25:24.130> we<00:25:24.550> want<00:25:24.730> to<00:25:24.790> set<00:25:24.910> a 00:25:24.930 --> 00:25:24.940 align:start position:0% a blockchain producer we want to set a 00:25:24.940 --> 00:25:26.400 align:start position:0% a blockchain producer we want to set a transaction<00:25:25.510> in<00:25:25.630> we<00:25:25.750> want<00:25:25.930> to<00:25:25.990> read<00:25:26.080> some<00:25:26.260> data 00:25:26.400 --> 00:25:26.410 align:start position:0% transaction in we want to read some data 00:25:26.410 --> 00:25:28.500 align:start position:0% transaction in we want to read some data we<00:25:26.770> want<00:25:26.950> to<00:25:27.010> react<00:25:27.250> with<00:25:27.430> the<00:25:27.490> but<00:25:27.700> it's 00:25:28.500 --> 00:25:28.510 align:start position:0% we want to react with the but it's 00:25:28.510 --> 00:25:30.960 align:start position:0% we want to react with the but it's pretty<00:25:28.630> basic<00:25:28.900> so<00:25:29.860> what<00:25:30.160> we<00:25:30.250> did<00:25:30.370> any<00:25:30.550> BS<00:25:30.790> code 00:25:30.960 --> 00:25:30.970 align:start position:0% pretty basic so what we did any BS code 00:25:30.970 --> 00:25:32.340 align:start position:0% pretty basic so what we did any BS code was<00:25:31.150> said<00:25:31.300> well<00:25:31.510> if<00:25:31.720> you<00:25:31.840> build<00:25:32.020> your<00:25:32.140> smart 00:25:32.340 --> 00:25:32.350 align:start position:0% was said well if you build your smart 00:25:32.350 --> 00:25:34.410 align:start position:0% was said well if you build your smart contractor<00:25:32.890> we<00:25:33.370> know<00:25:33.580> what<00:25:33.790> methods<00:25:34.150> you<00:25:34.210> have 00:25:34.410 --> 00:25:34.420 align:start position:0% contractor we know what methods you have 00:25:34.420 --> 00:25:36.210 align:start position:0% contractor we know what methods you have it<00:25:34.570> there<00:25:34.780> so<00:25:35.230> we<00:25:35.350> can<00:25:35.470> basically<00:25:35.620> we<00:25:35.950> have<00:25:36.070> to 00:25:36.210 --> 00:25:36.220 align:start position:0% it there so we can basically we have to 00:25:36.220 --> 00:25:37.650 align:start position:0% it there so we can basically we have to have<00:25:36.310> with<00:25:36.430> a<00:25:36.520> lot<00:25:36.670> you<00:25:36.700> guys<00:25:37.000> give<00:25:37.300> you<00:25:37.420> that 00:25:37.650 --> 00:25:37.660 align:start position:0% have with a lot you guys give you that 00:25:37.660 --> 00:25:39.420 align:start position:0% have with a lot you guys give you that as<00:25:37.840> an<00:25:37.960> output<00:25:38.290> you<00:25:38.860> don't<00:25:38.980> have<00:25:39.070> to<00:25:39.160> write<00:25:39.280> any 00:25:39.420 --> 00:25:39.430 align:start position:0% as an output you don't have to write any 00:25:39.430 --> 00:25:42.180 align:start position:0% as an output you don't have to write any code<00:25:39.640> you<00:25:40.120> can<00:25:40.690> basically<00:25:40.840> pop<00:25:41.350> that<00:25:41.530> into<00:25:41.710> our 00:25:42.180 --> 00:25:42.190 align:start position:0% code you can basically pop that into our 00:25:42.190 --> 00:25:45.030 align:start position:0% code you can basically pop that into our logic<00:25:42.850> app<00:25:42.970> service<00:25:43.740> developers<00:25:44.740> what<00:25:44.950> we 00:25:45.030 --> 00:25:45.040 align:start position:0% logic app service developers what we 00:25:45.040 --> 00:25:46.110 align:start position:0% logic app service developers what we call<00:25:45.220> them<00:25:45.340> someone<00:25:45.610> who<00:25:45.700> doesn't<00:25:45.880> write<00:25:46.090> a 00:25:46.110 --> 00:25:46.120 align:start position:0% call them someone who doesn't write a 00:25:46.120 --> 00:25:48.000 align:start position:0% call them someone who doesn't write a lot<00:25:46.300> of<00:25:46.330> code<00:25:46.450> can<00:25:47.110> even<00:25:47.350> use<00:25:47.500> that<00:25:47.530> because 00:25:48.000 --> 00:25:48.010 align:start position:0% lot of code can even use that because 00:25:48.010 --> 00:25:50.610 align:start position:0% lot of code can even use that because it's<00:25:48.160> basically<00:25:48.490> like<00:25:48.760> connection<00:25:49.620> they're 00:25:50.610 --> 00:25:50.620 align:start position:0% it's basically like connection they're 00:25:50.620 --> 00:25:55.860 align:start position:0% it's basically like connection they're super<00:25:51.340> easy<00:25:51.370> then<00:25:53.700> the<00:25:54.700> extension<00:25:55.150> and<00:25:55.390> this 00:25:55.860 --> 00:25:55.870 align:start position:0% super easy then the extension and this 00:25:55.870 --> 00:25:57.570 align:start position:0% super easy then the extension and this stuff<00:25:56.110> definitely<00:25:56.710> seems<00:25:56.890> to<00:25:57.100> keep<00:25:57.400> up 00:25:57.570 --> 00:25:57.580 align:start position:0% stuff definitely seems to keep up 00:25:57.580 --> 00:25:59.670 align:start position:0% stuff definitely seems to keep up finding<00:25:57.970> it<00:25:58.120> but<00:25:58.270> it<00:25:58.750> isn't<00:25:59.140> our<00:25:59.200> traditional 00:25:59.670 --> 00:25:59.680 align:start position:0% finding it but it isn't our traditional 00:25:59.680 --> 00:26:01.950 align:start position:0% finding it but it isn't our traditional studio<00:25:59.950> marketplace<00:26:00.520> watch<00:26:01.030> later<00:26:01.360> period 00:26:01.950 --> 00:26:01.960 align:start position:0% studio marketplace watch later period 00:26:01.960 --> 00:26:03.870 align:start position:0% studio marketplace watch later period you'll<00:26:02.260> find<00:26:02.500> it<00:26:02.680> this<00:26:02.830> is<00:26:02.980> a<00:26:03.070> short<00:26:03.550> link<00:26:03.700> to 00:26:03.870 --> 00:26:03.880 align:start position:0% you'll find it this is a short link to 00:26:03.880 --> 00:26:04.650 align:start position:0% you'll find it this is a short link to it 00:26:04.650 --> 00:26:04.660 align:start position:0% it 00:26:04.660 --> 00:26:07.460 align:start position:0% it we<00:26:05.110> launched<00:26:05.320> this<00:26:05.470> back<00:26:05.650> in<00:26:05.860> May 00:26:07.460 --> 00:26:07.470 align:start position:0% we launched this back in May 00:26:07.470 --> 00:26:09.440 align:start position:0% we launched this back in May get<00:26:07.980> feedback<00:26:08.279> it's<00:26:08.460> all<00:26:08.580> open<00:26:08.759> source<00:26:08.879> you<00:26:09.269> go 00:26:09.440 --> 00:26:09.450 align:start position:0% get feedback it's all open source you go 00:26:09.450 --> 00:26:12.889 align:start position:0% get feedback it's all open source you go look<00:26:09.629> at<00:26:09.750> our<00:26:09.870> turn<00:26:10.230> up<00:26:10.350> their<00:26:11.450> monthly<00:26:12.450> bills 00:26:12.889 --> 00:26:12.899 align:start position:0% look at our turn up their monthly bills 00:26:12.899 --> 00:26:15.019 align:start position:0% look at our turn up their monthly bills right<00:26:13.200> now<00:26:13.320> and<00:26:13.559> publishes<00:26:14.279> like<00:26:14.580> I<00:26:14.669> said<00:26:14.850> this 00:26:15.019 --> 00:26:15.029 align:start position:0% right now and publishes like I said this 00:26:15.029 --> 00:26:17.570 align:start position:0% right now and publishes like I said this week<00:26:15.210> we're<00:26:15.450> doing<00:26:15.480> one<00:26:16.100> I'll<00:26:17.100> show<00:26:17.159> you<00:26:17.279> some 00:26:17.570 --> 00:26:17.580 align:start position:0% week we're doing one I'll show you some 00:26:17.580 --> 00:26:18.950 align:start position:0% week we're doing one I'll show you some another<00:26:17.940> vendor<00:26:18.120> we're<00:26:18.360> working<00:26:18.629> with<00:26:18.809> so 00:26:18.950 --> 00:26:18.960 align:start position:0% another vendor we're working with so 00:26:18.960 --> 00:26:20.749 align:start position:0% another vendor we're working with so we're<00:26:19.110> gonna<00:26:19.200> we<00:26:19.769> put<00:26:19.950> some<00:26:20.070> new<00:26:20.190> stuff<00:26:20.429> in<00:26:20.580> for 00:26:20.749 --> 00:26:20.759 align:start position:0% we're gonna we put some new stuff in for 00:26:20.759 --> 00:26:22.759 align:start position:0% we're gonna we put some new stuff in for this<00:26:20.879> one<00:26:21.059> today<00:26:21.240> and<00:26:21.929> then<00:26:22.259> also<00:26:22.409> this<00:26:22.710> is 00:26:22.759 --> 00:26:22.769 align:start position:0% this one today and then also this is 00:26:22.769 --> 00:26:24.080 align:start position:0% this one today and then also this is just<00:26:23.190> the<00:26:23.279> experience<00:26:23.490> but<00:26:23.820> we'll<00:26:23.940> walk 00:26:24.080 --> 00:26:24.090 align:start position:0% just the experience but we'll walk 00:26:24.090 --> 00:26:28.940 align:start position:0% just the experience but we'll walk through<00:26:24.120> that<00:26:24.450> second<00:26:24.899> and<00:26:27.769> puppet<00:26:28.769> to 00:26:28.940 --> 00:26:28.950 align:start position:0% through that second and puppet to 00:26:28.950 --> 00:26:39.040 align:start position:0% through that second and puppet to actually<00:26:29.399> do<00:26:29.549> some<00:26:29.879> work 00:26:39.040 --> 00:26:39.050 align:start position:0% 00:26:39.050 --> 00:26:44.240 align:start position:0% [Music] 00:26:44.240 --> 00:26:44.250 align:start position:0% 00:26:44.250 --> 00:26:47.149 align:start position:0% okay<00:26:44.970> so<00:26:45.870> let<00:26:46.289> me<00:26:46.320> pump<00:26:46.530> into<00:26:46.860> a<00:26:46.890> pressure 00:26:47.149 --> 00:26:47.159 align:start position:0% okay so let me pump into a pressure 00:26:47.159 --> 00:26:49.159 align:start position:0% okay so let me pump into a pressure console<00:26:47.820> here<00:26:48.000> so<00:26:48.210> this<00:26:48.360> is<00:26:48.480> just<00:26:48.630> three<00:26:48.900> BS 00:26:49.159 --> 00:26:49.169 align:start position:0% console here so this is just three BS 00:26:49.169 --> 00:26:51.230 align:start position:0% console here so this is just three BS code<00:26:49.380> on<00:26:49.559> the<00:26:49.679> Marx<00:26:50.070> Brothers<00:26:50.130> are<00:26:51.000> getting 00:26:51.230 --> 00:26:51.240 align:start position:0% code on the Marx Brothers are getting 00:26:51.240 --> 00:26:53.360 align:start position:0% code on the Marx Brothers are getting started<00:26:51.480> if<00:26:52.320> you<00:26:52.409> just<00:26:52.530> go<00:26:52.650> down<00:26:52.860> low<00:26:53.039> just<00:26:53.190> go 00:26:53.360 --> 00:26:53.370 align:start position:0% started if you just go down low just go 00:26:53.370 --> 00:26:55.490 align:start position:0% started if you just go down low just go just<00:26:53.580> go<00:26:53.669> straight<00:26:53.940> for<00:26:54.000> it<00:26:54.270> when<00:26:55.200> you<00:26:55.289> come<00:26:55.409> in 00:26:55.490 --> 00:26:55.500 align:start position:0% just go straight for it when you come in 00:26:55.500 --> 00:26:56.930 align:start position:0% just go straight for it when you come in here<00:26:55.530> you<00:26:55.799> can<00:26:55.950> search<00:26:56.130> for<00:26:56.159> these<00:26:56.460> miscible 00:26:56.930 --> 00:26:56.940 align:start position:0% here you can search for these miscible 00:26:56.940 --> 00:26:58.549 align:start position:0% here you can search for these miscible no<00:26:57.059> extensions<00:26:57.690> so<00:26:58.020> these<00:26:58.140> are<00:26:58.320> things<00:26:58.470> that 00:26:58.549 --> 00:26:58.559 align:start position:0% no extensions so these are things that 00:26:58.559 --> 00:27:02.570 align:start position:0% no extensions so these are things that meant<00:26:59.630> you<00:27:00.630> just<00:27:00.780> type<00:27:00.929> it<00:27:01.080> won't<00:27:01.289> change<00:27:01.580> and 00:27:02.570 --> 00:27:02.580 align:start position:0% meant you just type it won't change and 00:27:02.580 --> 00:27:08.870 align:start position:0% meant you just type it won't change and you'll<00:27:02.789> find<00:27:03.030> better<00:27:03.960> here<00:27:06.919> and<00:27:07.919> so<00:27:08.520> basically 00:27:08.870 --> 00:27:08.880 align:start position:0% you'll find better here and so basically 00:27:08.880 --> 00:27:10.250 align:start position:0% you'll find better here and so basically once<00:27:09.150> you<00:27:09.240> have<00:27:09.330> thought<00:27:09.570> you'll<00:27:09.900> see<00:27:10.110> this 00:27:10.250 --> 00:27:10.260 align:start position:0% once you have thought you'll see this 00:27:10.260 --> 00:27:13.010 align:start position:0% once you have thought you'll see this little<00:27:10.789> over<00:27:11.789> here<00:27:12.000> now<00:27:12.330> I<00:27:12.360> already<00:27:12.630> have<00:27:12.750> one 00:27:13.010 --> 00:27:13.020 align:start position:0% little over here now I already have one 00:27:13.020 --> 00:27:15.440 align:start position:0% little over here now I already have one pre<00:27:13.289> connected<00:27:13.710> here<00:27:13.970> this<00:27:14.970> is<00:27:15.059> one<00:27:15.240> talking 00:27:15.440 --> 00:27:15.450 align:start position:0% pre connected here this is one talking 00:27:15.450 --> 00:27:16.880 align:start position:0% pre connected here this is one talking to<00:27:15.600> a<00:27:15.630> sure<00:27:15.840> but<00:27:15.960> also<00:27:16.110> explain<00:27:16.559> what<00:27:16.740> that<00:27:16.770> is 00:27:16.880 --> 00:27:16.890 align:start position:0% to a sure but also explain what that is 00:27:16.890 --> 00:27:17.750 align:start position:0% to a sure but also explain what that is in<00:27:17.130> a<00:27:17.190> second 00:27:17.750 --> 00:27:17.760 align:start position:0% in a second 00:27:17.760 --> 00:27:20.630 align:start position:0% in a second I<00:27:17.990> basically<00:27:18.990> opened<00:27:19.530> a<00:27:19.559> foreword<00:27:19.860> here<00:27:20.070> it's 00:27:20.630 --> 00:27:20.640 align:start position:0% I basically opened a foreword here it's 00:27:20.640 --> 00:27:22.520 align:start position:0% I basically opened a foreword here it's just<00:27:20.820> empty<00:27:21.030> right<00:27:21.330> now<00:27:21.480> and<00:27:22.020> I<00:27:22.320> brought<00:27:22.470> up 00:27:22.520 --> 00:27:22.530 align:start position:0% just empty right now and I brought up 00:27:22.530 --> 00:27:24.110 align:start position:0% just empty right now and I brought up the<00:27:22.679> command<00:27:22.980> palette<00:27:23.190> man<00:27:23.580> palettes<00:27:24.059> like 00:27:24.110 --> 00:27:24.120 align:start position:0% the command palette man palettes like 00:27:24.120 --> 00:27:25.789 align:start position:0% the command palette man palettes like basically<00:27:24.690> all<00:27:24.900> the<00:27:25.049> commands<00:27:25.350> that<00:27:25.470> we<00:27:25.620> can 00:27:25.789 --> 00:27:25.799 align:start position:0% basically all the commands that we can 00:27:25.799 --> 00:27:28.010 align:start position:0% basically all the commands that we can do<00:27:25.919> with<00:27:26.100> these<00:27:26.220> tools<00:27:26.520> then<00:27:27.510> we<00:27:27.600> can<00:27:27.720> add<00:27:27.840> new 00:27:28.010 --> 00:27:28.020 align:start position:0% do with these tools then we can add new 00:27:28.020 --> 00:27:29.360 align:start position:0% do with these tools then we can add new ones<00:27:28.140> to<00:27:28.380> it<00:27:28.500> but<00:27:28.620> right<00:27:28.799> here<00:27:28.830> is<00:27:29.039> what<00:27:29.159> we<00:27:29.250> do 00:27:29.360 --> 00:27:29.370 align:start position:0% ones to it but right here is what we do 00:27:29.370 --> 00:27:31.039 align:start position:0% ones to it but right here is what we do right<00:27:29.520> now<00:27:29.760> so<00:27:30.000> we<00:27:30.510> have<00:27:30.600> our<00:27:30.690> founding 00:27:31.039 --> 00:27:31.049 align:start position:0% right now so we have our founding 00:27:31.049 --> 00:27:32.690 align:start position:0% right now so we have our founding project<00:27:31.559> I'll<00:27:31.740> show<00:27:31.890> you<00:27:31.950> is<00:27:32.159> about<00:27:32.460> the 00:27:32.690 --> 00:27:32.700 align:start position:0% project I'll show you is about the 00:27:32.700 --> 00:27:35.210 align:start position:0% project I'll show you is about the transaction<00:27:33.120> flow<00:27:33.450> we<00:27:34.350> fully<00:27:34.620> integrated<00:27:35.100> the 00:27:35.210 --> 00:27:35.220 align:start position:0% transaction flow we fully integrated the 00:27:35.220 --> 00:27:37.159 align:start position:0% transaction flow we fully integrated the debugger<00:27:35.610> into<00:27:36.000> the<00:27:36.120> IDE<00:27:36.360> so<00:27:36.720> you<00:27:36.809> can<00:27:36.960> do<00:27:37.049> all 00:27:37.159 --> 00:27:37.169 align:start position:0% debugger into the IDE so you can do all 00:27:37.169 --> 00:27:38.990 align:start position:0% debugger into the IDE so you can do all the<00:27:37.289> step<00:27:37.500> through<00:27:37.770> step<00:27:38.070> out<00:27:38.250> of<00:27:38.460> you<00:27:38.789> can<00:27:38.909> do 00:27:38.990 --> 00:27:39.000 align:start position:0% the step through step out of you can do 00:27:39.000 --> 00:27:40.399 align:start position:0% the step through step out of you can do the<00:27:39.120> inspection<00:27:39.659> and<00:27:39.840> now<00:27:40.140> for<00:27:40.350> the 00:27:40.399 --> 00:27:40.409 align:start position:0% the inspection and now for the 00:27:40.409 --> 00:27:43.539 align:start position:0% the inspection and now for the instruction<00:27:40.860> level<00:27:41.090> you<00:27:42.090> can<00:27:42.299> see<00:27:42.480> all<00:27:42.659> the 00:27:43.539 --> 00:27:43.549 align:start position:0% instruction level you can see all the 00:27:43.549 --> 00:27:47.330 align:start position:0% instruction level you can see all the there<00:27:44.549> we<00:27:45.330> do<00:27:45.510> the<00:27:45.990> deployments<00:27:46.530> the<00:27:46.650> bills<00:27:46.830> in 00:27:47.330 --> 00:27:47.340 align:start position:0% there we do the deployments the bills in 00:27:47.340 --> 00:27:48.649 align:start position:0% there we do the deployments the bills in all<00:27:47.520> the<00:27:47.669> compilation<00:27:47.940> that's<00:27:48.360> happening 00:27:48.649 --> 00:27:48.659 align:start position:0% all the compilation that's happening 00:27:48.659 --> 00:27:50.000 align:start position:0% all the compilation that's happening there<00:27:48.870> we<00:27:48.960> can<00:27:49.140> connect<00:27:49.470> and<00:27:49.679> create<00:27:49.799> new 00:27:50.000 --> 00:27:50.010 align:start position:0% there we can connect and create new 00:27:50.010 --> 00:27:51.560 align:start position:0% there we can connect and create new networks<00:27:50.190> up<00:27:50.580> here<00:27:50.820> I'll<00:27:51.270> show<00:27:51.450> you<00:27:51.480> what 00:27:51.560 --> 00:27:51.570 align:start position:0% networks up here I'll show you what 00:27:51.570 --> 00:27:52.190 align:start position:0% networks up here I'll show you what those<00:27:51.750> look<00:27:51.809> like 00:27:52.190 --> 00:27:52.200 align:start position:0% those look like 00:27:52.200 --> 00:27:57.149 align:start position:0% those look like we<00:27:52.890> have<00:27:52.980> some<00:27:53.190> things<00:27:53.520> for<00:27:53.730> key<00:27:54.090> management 00:27:57.149 --> 00:27:57.159 align:start position:0% 00:27:57.159 --> 00:27:59.880 align:start position:0% so<00:27:57.789> if<00:27:58.059> we<00:27:58.210> basically<00:27:58.390> just<00:27:58.720> do<00:27:58.990> a<00:27:59.020> new<00:27:59.200> one<00:27:59.380> you 00:27:59.880 --> 00:27:59.890 align:start position:0% so if we basically just do a new one you 00:27:59.890 --> 00:28:01.409 align:start position:0% so if we basically just do a new one you can<00:27:59.950> see<00:28:00.159> when<00:28:00.279> I<00:28:00.340> do<00:28:00.399> a<00:28:00.460> new<00:28:00.610> project<00:28:00.789> now<00:28:01.210> if<00:28:01.330> I 00:28:01.409 --> 00:28:01.419 align:start position:0% can see when I do a new project now if I 00:28:01.419 --> 00:28:03.149 align:start position:0% can see when I do a new project now if I was<00:28:01.539> a<00:28:01.570> user<00:28:01.840> that<00:28:02.020> doesn't<00:28:02.380> know<00:28:02.740> what<00:28:03.070> the 00:28:03.149 --> 00:28:03.159 align:start position:0% was a user that doesn't know what the 00:28:03.159 --> 00:28:04.889 align:start position:0% was a user that doesn't know what the heck<00:28:03.309> I'm<00:28:03.460> doing<00:28:03.490> if<00:28:04.149> I<00:28:04.240> just<00:28:04.390> keep<00:28:04.539> hitting<00:28:04.659> at 00:28:04.889 --> 00:28:04.899 align:start position:0% heck I'm doing if I just keep hitting at 00:28:04.899 --> 00:28:06.480 align:start position:0% heck I'm doing if I just keep hitting at her<00:28:04.990> I'm<00:28:05.260> gonna<00:28:05.380> get<00:28:05.620> a<00:28:05.649> nice<00:28:05.860> scaffold<00:28:06.309> in<00:28:06.370> our 00:28:06.480 --> 00:28:06.490 align:start position:0% her I'm gonna get a nice scaffold in our 00:28:06.490 --> 00:28:08.250 align:start position:0% her I'm gonna get a nice scaffold in our project<00:28:06.880> I<00:28:07.149> know<00:28:07.450> what<00:28:07.690> I'm<00:28:07.779> doing<00:28:08.080> and<00:28:08.169> I<00:28:08.230> want 00:28:08.250 --> 00:28:08.260 align:start position:0% project I know what I'm doing and I want 00:28:08.260 --> 00:28:10.110 align:start position:0% project I know what I'm doing and I want to<00:28:08.470> go<00:28:08.529> I<00:28:08.620> said<00:28:08.890> to<00:28:09.130> hey<00:28:09.220> there's<00:28:09.429> truffle<00:28:09.970> box 00:28:10.110 --> 00:28:10.120 align:start position:0% to go I said to hey there's truffle box 00:28:10.120 --> 00:28:11.549 align:start position:0% to go I said to hey there's truffle box I<00:28:10.270> want<00:28:10.450> to<00:28:10.510> use<00:28:10.630> it<00:28:10.779> something<00:28:11.080> like<00:28:11.200> that<00:28:11.380> I 00:28:11.549 --> 00:28:11.559 align:start position:0% I want to use it something like that I 00:28:11.559 --> 00:28:14.220 align:start position:0% I want to use it something like that I can<00:28:11.679> do<00:28:11.770> that<00:28:11.950> as<00:28:12.220> well<00:28:12.630> so<00:28:13.630> in<00:28:13.750> this<00:28:13.809> case<00:28:14.049> I'm 00:28:14.220 --> 00:28:14.230 align:start position:0% can do that as well so in this case I'm 00:28:14.230 --> 00:28:15.750 align:start position:0% can do that as well so in this case I'm just<00:28:14.260> going<00:28:14.409> to<00:28:14.559> take<00:28:14.740> the<00:28:14.830> info<00:28:15.130> guitar<00:28:15.520> the 00:28:15.750 --> 00:28:15.760 align:start position:0% just going to take the info guitar the 00:28:15.760 --> 00:28:18.019 align:start position:0% just going to take the info guitar the compliment<00:28:16.299> put<00:28:17.020> it<00:28:17.080> in<00:28:17.169> the<00:28:17.260> same<00:28:17.440> forward 00:28:18.019 --> 00:28:18.029 align:start position:0% compliment put it in the same forward 00:28:18.029 --> 00:28:22.649 align:start position:0% compliment put it in the same forward will<00:28:19.029> pray<00:28:19.240> to<00:28:19.299> the<00:28:19.600> internet<00:28:20.080> gods<00:28:20.289> here<00:28:21.659> the 00:28:22.649 --> 00:28:22.659 align:start position:0% will pray to the internet gods here the 00:28:22.659 --> 00:28:24.600 align:start position:0% will pray to the internet gods here the network<00:28:23.020> is<00:28:23.230> not<00:28:23.260> great<00:28:23.679> here<00:28:23.919> but<00:28:24.130> that's 00:28:24.600 --> 00:28:24.610 align:start position:0% network is not great here but that's 00:28:24.610 --> 00:28:27.149 align:start position:0% network is not great here but that's okay<00:28:24.880> I<00:28:25.120> have<00:28:25.480> the<00:28:25.690> cookie<00:28:26.260> demo<00:28:26.770> in<00:28:26.950> case 00:28:27.149 --> 00:28:27.159 align:start position:0% okay I have the cookie demo in case 00:28:27.159 --> 00:28:29.279 align:start position:0% okay I have the cookie demo in case there's<00:28:27.399> mail<00:28:27.549> but<00:28:27.940> basically<00:28:28.929> what<00:28:29.169> we're 00:28:29.279 --> 00:28:29.289 align:start position:0% there's mail but basically what we're 00:28:29.289 --> 00:28:31.080 align:start position:0% there's mail but basically what we're doing<00:28:29.320> here<00:28:29.559> is<00:28:29.919> we've<00:28:30.100> created<00:28:30.279> a<00:28:30.640> template 00:28:31.080 --> 00:28:31.090 align:start position:0% doing here is we've created a template 00:28:31.090 --> 00:28:34.169 align:start position:0% doing here is we've created a template if<00:28:31.960> you're<00:28:32.110> familiar<00:28:32.260> with<00:28:32.500> truffle<00:28:32.950> boxes<00:28:33.399> is 00:28:34.169 --> 00:28:34.179 align:start position:0% if you're familiar with truffle boxes is 00:28:34.179 --> 00:28:35.909 align:start position:0% if you're familiar with truffle boxes is one<00:28:34.360> package<00:28:34.690> format<00:28:35.080> that<00:28:35.200> we're<00:28:35.380> using<00:28:35.620> and 00:28:35.909 --> 00:28:35.919 align:start position:0% one package format that we're using and 00:28:35.919 --> 00:28:37.919 align:start position:0% one package format that we're using and so<00:28:36.370> basically<00:28:36.700> be<00:28:36.940> scaffold<00:28:37.419> about<00:28:37.600> it<00:28:37.779> but 00:28:37.919 --> 00:28:37.929 align:start position:0% so basically be scaffold about it but 00:28:37.929 --> 00:28:39.360 align:start position:0% so basically be scaffold about it but the<00:28:38.049> right<00:28:38.230> stuff<00:28:38.529> out<00:28:38.649> here<00:28:38.860> for<00:28:39.070> what<00:28:39.190> people 00:28:39.360 --> 00:28:39.370 align:start position:0% the right stuff out here for what people 00:28:39.370 --> 00:28:40.710 align:start position:0% the right stuff out here for what people should<00:28:39.549> be<00:28:39.730> doing<00:28:39.850> with<00:28:40.210> they're<00:28:40.330> doing<00:28:40.539> one 00:28:40.710 --> 00:28:40.720 align:start position:0% should be doing with they're doing one 00:28:40.720 --> 00:28:43.649 align:start position:0% should be doing with they're doing one of<00:28:40.750> these<00:28:40.929> so<00:28:41.230> we<00:28:41.830> have<00:28:42.039> a<00:28:42.070> basic<00:28:42.659> project 00:28:43.649 --> 00:28:43.659 align:start position:0% of these so we have a basic project 00:28:43.659 --> 00:28:47.190 align:start position:0% of these so we have a basic project structure<00:28:44.110> you<00:28:44.440> have<00:28:44.789> like<00:28:45.789> compare<00:28:46.779> all<00:28:47.080> the 00:28:47.190 --> 00:28:47.200 align:start position:0% structure you have like compare all the 00:28:47.200 --> 00:28:49.799 align:start position:0% structure you have like compare all the normal<00:28:47.649> stuff<00:28:47.710> people<00:28:48.100> would<00:28:48.340> eat<00:28:48.659> and<00:28:49.659> then 00:28:49.799 --> 00:28:49.809 align:start position:0% normal stuff people would eat and then 00:28:49.809 --> 00:28:51.120 align:start position:0% normal stuff people would eat and then basically<00:28:50.169> you<00:28:50.350> can<00:28:50.500> see<00:28:50.649> as<00:28:50.770> it<00:28:50.919> went<00:28:51.039> through 00:28:51.120 --> 00:28:51.130 align:start position:0% basically you can see as it went through 00:28:51.130 --> 00:28:52.799 align:start position:0% basically you can see as it went through it<00:28:51.370> just<00:28:51.520> went<00:28:51.700> pull<00:28:51.880> this<00:28:52.059> box<00:28:52.270> down<00:28:52.480> it's 00:28:52.799 --> 00:28:52.809 align:start position:0% it just went pull this box down it's 00:28:52.809 --> 00:28:55.049 align:start position:0% it just went pull this box down it's already<00:28:53.110> developing<00:28:53.559> local<00:28:53.919> tendencies<00:28:54.370> so 00:28:55.049 --> 00:28:55.059 align:start position:0% already developing local tendencies so 00:28:55.059 --> 00:28:57.120 align:start position:0% already developing local tendencies so in<00:28:55.179> our<00:28:55.270> case<00:28:55.419> we're<00:28:55.630> using<00:28:55.659> wallet<00:28:56.200> so<00:28:57.039> we 00:28:57.120 --> 00:28:57.130 align:start position:0% in our case we're using wallet so we 00:28:57.130 --> 00:28:59.220 align:start position:0% in our case we're using wallet so we needed<00:28:57.309> a<00:28:57.429> salsa<00:28:57.789> with<00:28:57.940> no<00:28:58.059> dependencies<00:28:58.690> so 00:28:59.220 --> 00:28:59.230 align:start position:0% needed a salsa with no dependencies so 00:28:59.230 --> 00:29:00.659 align:start position:0% needed a salsa with no dependencies so when<00:28:59.350> you<00:28:59.440> do<00:28:59.559> this<00:28:59.679> yourself<00:29:00.100> you<00:29:00.309> see<00:29:00.490> that 00:29:00.659 --> 00:29:00.669 align:start position:0% when you do this yourself you see that 00:29:00.669 --> 00:29:01.889 align:start position:0% when you do this yourself you see that it<00:29:00.760> kind<00:29:00.880> of<00:29:00.970> hangs<00:29:01.179> here<00:29:01.419> as<00:29:01.570> it's<00:29:01.750> doing 00:29:01.889 --> 00:29:01.899 align:start position:0% it kind of hangs here as it's doing 00:29:01.899 --> 00:29:03.690 align:start position:0% it kind of hangs here as it's doing something<00:29:02.409> what<00:29:02.890> it's<00:29:03.010> doing<00:29:03.250> is<00:29:03.370> just<00:29:03.520> going 00:29:03.690 --> 00:29:03.700 align:start position:0% something what it's doing is just going 00:29:03.700 --> 00:29:05.279 align:start position:0% something what it's doing is just going getting<00:29:04.090> all<00:29:04.210> the<00:29:04.330> packages<00:29:04.840> that<00:29:04.960> we<00:29:05.110> need 00:29:05.279 --> 00:29:05.289 align:start position:0% getting all the packages that we need 00:29:05.289 --> 00:29:07.320 align:start position:0% getting all the packages that we need I'm<00:29:05.799> doing<00:29:06.010> it<00:29:06.130> for<00:29:06.309> you<00:29:06.520> again<00:29:07.149> you 00:29:07.320 --> 00:29:07.330 align:start position:0% I'm doing it for you again you 00:29:07.330 --> 00:29:09.840 align:start position:0% I'm doing it for you again you customized<00:29:08.020> about<00:29:08.770> the<00:29:08.860> terminal<00:29:09.399> and<00:29:09.610> do<00:29:09.730> it 00:29:09.840 --> 00:29:09.850 align:start position:0% customized about the terminal and do it 00:29:09.850 --> 00:29:12.269 align:start position:0% customized about the terminal and do it every<00:29:10.029> two<00:29:10.390> here<00:29:10.630> if<00:29:10.750> you're<00:29:10.960> into<00:29:11.830> know<00:29:11.980> and 00:29:12.269 --> 00:29:12.279 align:start position:0% every two here if you're into know and 00:29:12.279 --> 00:29:13.500 align:start position:0% every two here if you're into know and know<00:29:12.520> what<00:29:12.669> you're<00:29:12.820> doing<00:29:13.029> with<00:29:13.149> this<00:29:13.270> stuff 00:29:13.500 --> 00:29:13.510 align:start position:0% know what you're doing with this stuff 00:29:13.510 --> 00:29:15.000 align:start position:0% know what you're doing with this stuff but<00:29:13.990> if<00:29:14.080> you<00:29:14.169> don't<00:29:14.350> know<00:29:14.500> what<00:29:14.649> you're<00:29:14.799> doing 00:29:15.000 --> 00:29:15.010 align:start position:0% but if you don't know what you're doing 00:29:15.010 --> 00:29:15.799 align:start position:0% but if you don't know what you're doing is<00:29:15.190> what 00:29:15.799 --> 00:29:15.809 align:start position:0% is what 00:29:15.809 --> 00:29:18.619 align:start position:0% is what it's<00:29:15.929> a<00:29:16.019> good<00:29:16.349> state<00:29:17.090> so<00:29:18.090> just<00:29:18.330> give<00:29:18.450> that<00:29:18.599> a 00:29:18.619 --> 00:29:18.629 align:start position:0% it's a good state so just give that a 00:29:18.629 --> 00:29:22.669 align:start position:0% it's a good state so just give that a few<00:29:18.840> seconds<00:29:19.200> here<00:29:20.179> there<00:29:21.179> this<00:29:21.440> so<00:29:22.440> as<00:29:22.559> that 00:29:22.669 --> 00:29:22.679 align:start position:0% few seconds here there this so as that 00:29:22.679 --> 00:29:25.940 align:start position:0% few seconds here there this so as that finishes<00:29:23.129> basically<00:29:23.700> we<00:29:23.820> have<00:29:23.969> our<00:29:24.950> hello 00:29:25.940 --> 00:29:25.950 align:start position:0% finishes basically we have our hello 00:29:25.950 --> 00:29:27.950 align:start position:0% finishes basically we have our hello world<00:29:26.039> we<00:29:26.460> have<00:29:26.549> our<00:29:26.639> migrations<00:29:27.179> I<00:29:27.479> already 00:29:27.950 --> 00:29:27.960 align:start position:0% world we have our migrations I already 00:29:27.960 --> 00:29:30.049 align:start position:0% world we have our migrations I already have<00:29:28.109> all<00:29:28.229> the<00:29:28.320> migrations<00:29:28.859> set<00:29:29.039> up<00:29:29.159> for<00:29:29.399> us<00:29:29.519> if 00:29:30.049 --> 00:29:30.059 align:start position:0% have all the migrations set up for us if 00:29:30.059 --> 00:29:32.269 align:start position:0% have all the migrations set up for us if we<00:29:30.210> look<00:29:30.359> at<00:29:30.479> our<00:29:30.539> truffle<00:29:30.929> config<00:29:31.289> minimize 00:29:32.269 --> 00:29:32.279 align:start position:0% we look at our truffle config minimize 00:29:32.279 --> 00:29:33.979 align:start position:0% we look at our truffle config minimize some<00:29:32.460> things<00:29:32.669> here<00:29:32.879> we<00:29:33.539> automatically 00:29:33.979 --> 00:29:33.989 align:start position:0% some things here we automatically 00:29:33.989 --> 00:29:35.450 align:start position:0% some things here we automatically through<00:29:34.379> a<00:29:34.409> development<00:29:34.679> environment<00:29:35.039> they'd 00:29:35.450 --> 00:29:35.460 align:start position:0% through a development environment they'd 00:29:35.460 --> 00:29:36.200 align:start position:0% through a development environment they'd appear<00:29:35.639> for<00:29:35.879> you 00:29:36.200 --> 00:29:36.210 align:start position:0% appear for you 00:29:36.210 --> 00:29:38.749 align:start position:0% appear for you we<00:29:36.450> have<00:29:36.539> ganache<00:29:36.809> baked<00:29:37.139> into<00:29:37.349> the<00:29:37.499> IDE<00:29:37.889> so<00:29:38.369> if 00:29:38.749 --> 00:29:38.759 align:start position:0% we have ganache baked into the IDE so if 00:29:38.759 --> 00:29:40.039 align:start position:0% we have ganache baked into the IDE so if you<00:29:38.909> don't<00:29:39.149> do<00:29:39.269> anything<00:29:39.509> else<00:29:39.719> it'll 00:29:40.039 --> 00:29:40.049 align:start position:0% you don't do anything else it'll 00:29:40.049 --> 00:29:42.289 align:start position:0% you don't do anything else it'll automatically<00:29:40.529> just<00:29:40.889> work<00:29:41.070> in<00:29:41.759> a<00:29:41.879> distinct 00:29:42.289 --> 00:29:42.299 align:start position:0% automatically just work in a distinct 00:29:42.299 --> 00:29:42.950 align:start position:0% automatically just work in a distinct obsession 00:29:42.950 --> 00:29:42.960 align:start position:0% obsession 00:29:42.960 --> 00:29:44.810 align:start position:0% obsession we<00:29:43.259> also<00:29:43.409> inject<00:29:43.830> the<00:29:44.219> part<00:29:44.399> where<00:29:44.519> provider 00:29:44.810 --> 00:29:44.820 align:start position:0% we also inject the part where provider 00:29:44.820 --> 00:29:47.269 align:start position:0% we also inject the part where provider and<00:29:45.059> the<00:29:45.149> HDL<00:29:45.779> provider<00:29:46.109> and<00:29:46.590> you'll<00:29:47.009> see<00:29:47.159> what 00:29:47.269 --> 00:29:47.279 align:start position:0% and the HDL provider and you'll see what 00:29:47.279 --> 00:29:48.409 align:start position:0% and the HDL provider and you'll see what that<00:29:47.309> means<00:29:47.609> here<00:29:47.789> in<00:29:47.879> a<00:29:47.940> second<00:29:48.269> when<00:29:48.389> we 00:29:48.409 --> 00:29:48.419 align:start position:0% that means here in a second when we 00:29:48.419 --> 00:29:50.779 align:start position:0% that means here in a second when we start<00:29:48.690> talking<00:29:48.989> to<00:29:49.080> other<00:29:49.109> networks<00:29:49.710> so<00:29:50.700> the 00:29:50.779 --> 00:29:50.789 align:start position:0% start talking to other networks so the 00:29:50.789 --> 00:29:52.339 align:start position:0% start talking to other networks so the first<00:29:50.969> thing<00:29:51.119> you'd<00:29:51.239> want<00:29:51.450> to<00:29:51.479> do<00:29:51.599> is<00:29:51.629> just<00:29:51.929> you 00:29:52.339 --> 00:29:52.349 align:start position:0% first thing you'd want to do is just you 00:29:52.349 --> 00:29:55.879 align:start position:0% first thing you'd want to do is just you know<00:29:52.379> do<00:29:52.739> a<00:29:52.769> basic<00:29:53.249> build<00:29:54.139> this<00:29:55.139> is<00:29:55.349> in<00:29:55.499> preview 00:29:55.879 --> 00:29:55.889 align:start position:0% know do a basic build this is in preview 00:29:55.889 --> 00:29:57.560 align:start position:0% know do a basic build this is in preview so<00:29:56.039> you'll<00:29:56.219> see<00:29:56.369> lovely<00:29:56.759> debug<00:29:57.179> commands<00:29:57.419> to 00:29:57.560 --> 00:29:57.570 align:start position:0% so you'll see lovely debug commands to 00:29:57.570 --> 00:29:59.089 align:start position:0% so you'll see lovely debug commands to be<00:29:57.599> continued<00:29:57.929> to<00:29:58.049> minimize<00:29:58.379> this<00:29:58.649> but<00:29:58.830> we<00:29:58.919> put 00:29:59.089 --> 00:29:59.099 align:start position:0% be continued to minimize this but we put 00:29:59.099 --> 00:30:01.039 align:start position:0% be continued to minimize this but we put this<00:29:59.219> out<00:29:59.369> here<00:29:59.429> so<00:29:59.820> that<00:29:59.969> people<00:30:00.269> can<00:30:00.419> see 00:30:01.039 --> 00:30:01.049 align:start position:0% this out here so that people can see 00:30:01.049 --> 00:30:02.299 align:start position:0% this out here so that people can see what's<00:30:01.259> happening<00:30:01.619> there<00:30:01.830> in<00:30:01.950> case<00:30:02.099> there's 00:30:02.299 --> 00:30:02.309 align:start position:0% what's happening there in case there's 00:30:02.309 --> 00:30:04.430 align:start position:0% what's happening there in case there's any<00:30:02.460> break<00:30:02.700> so<00:30:02.940> that<00:30:02.969> it<00:30:03.179> is<00:30:03.299> cooling<00:30:03.690> while 00:30:04.430 --> 00:30:04.440 align:start position:0% any break so that it is cooling while 00:30:04.440 --> 00:30:06.320 align:start position:0% any break so that it is cooling while we're<00:30:04.619> in<00:30:04.710> preview<00:30:05.129> but<00:30:05.759> basically<00:30:06.089> you<00:30:06.210> can 00:30:06.320 --> 00:30:06.330 align:start position:0% we're in preview but basically you can 00:30:06.330 --> 00:30:09.349 align:start position:0% we're in preview but basically you can see<00:30:06.450> interested<00:30:06.839> in<00:30:06.929> compilation<00:30:08.359> projects 00:30:09.349 --> 00:30:09.359 align:start position:0% see interested in compilation projects 00:30:09.359 --> 00:30:12.589 align:start position:0% see interested in compilation projects and<00:30:09.599> then<00:30:10.139> if<00:30:10.259> we<00:30:10.379> do<00:30:10.529> a<00:30:10.559> deploy<00:30:11.389> and<00:30:12.389> notice 00:30:12.589 --> 00:30:12.599 align:start position:0% and then if we do a deploy and notice 00:30:12.599 --> 00:30:16.430 align:start position:0% and then if we do a deploy and notice what<00:30:12.749> we<00:30:12.869> do<00:30:12.989> at<00:30:13.109> the<00:30:13.200> point<00:30:14.690> we<00:30:15.690> basically<00:30:15.869> get 00:30:16.430 --> 00:30:16.440 align:start position:0% what we do at the point we basically get 00:30:16.440 --> 00:30:18.349 align:start position:0% what we do at the point we basically get this<00:30:16.559> little<00:30:16.889> drop<00:30:17.669> down<00:30:17.700> here<00:30:18.089> now<00:30:18.179> what's 00:30:18.349 --> 00:30:18.359 align:start position:0% this little drop down here now what's 00:30:18.359 --> 00:30:20.930 align:start position:0% this little drop down here now what's cool<00:30:18.509> about<00:30:18.539> this<00:30:18.869> you<00:30:19.049> don't<00:30:19.349> get<00:30:19.589> was<00:30:19.940> you 00:30:20.930 --> 00:30:20.940 align:start position:0% cool about this you don't get was you 00:30:20.940 --> 00:30:23.389 align:start position:0% cool about this you don't get was you can<00:30:21.089> see<00:30:21.119> it<00:30:21.330> says<00:30:21.479> from<00:30:21.809> truffle<00:30:22.200> in<00:30:22.379> PJs<00:30:22.769> so 00:30:23.389 --> 00:30:23.399 align:start position:0% can see it says from truffle in PJs so 00:30:23.399 --> 00:30:25.159 align:start position:0% can see it says from truffle in PJs so basically<00:30:23.820> in<00:30:24.059> the<00:30:24.149> trouble<00:30:24.419> config<00:30:24.749> where<00:30:24.989> we 00:30:25.159 --> 00:30:25.169 align:start position:0% basically in the trouble config where we 00:30:25.169 --> 00:30:27.289 align:start position:0% basically in the trouble config where we had<00:30:25.320> that<00:30:25.499> development<00:30:25.950> by<00:30:26.279> default<00:30:26.700> intended 00:30:27.289 --> 00:30:27.299 align:start position:0% had that development by default intended 00:30:27.299 --> 00:30:27.919 align:start position:0% had that development by default intended for<00:30:27.509> you 00:30:27.919 --> 00:30:27.929 align:start position:0% for you 00:30:27.929 --> 00:30:29.299 align:start position:0% for you but<00:30:28.289> you<00:30:28.349> also<00:30:28.499> want<00:30:28.619> them<00:30:28.889> to<00:30:28.919> trigger 00:30:29.299 --> 00:30:29.309 align:start position:0% but you also want them to trigger 00:30:29.309 --> 00:30:31.609 align:start position:0% but you also want them to trigger because<00:30:29.849> I<00:30:30.029> already<00:30:30.119> have<00:30:30.359> one<00:30:30.539> register<00:30:30.719> so<00:30:31.589> I 00:30:31.609 --> 00:30:31.619 align:start position:0% because I already have one register so I 00:30:31.619 --> 00:30:33.660 align:start position:0% because I already have one register so I think<00:30:31.739> go<00:30:32.009> up<00:30:32.190> more 00:30:33.660 --> 00:30:33.670 align:start position:0% think go up more 00:30:33.670 --> 00:30:36.610 align:start position:0% think go up more if<00:30:34.670> you're<00:30:34.880> listed<00:30:35.750> over<00:30:35.840> here<00:30:35.930> you<00:30:36.380> can<00:30:36.500> also 00:30:36.610 --> 00:30:36.620 align:start position:0% if you're listed over here you can also 00:30:36.620 --> 00:30:38.410 align:start position:0% if you're listed over here you can also do<00:30:36.830> local<00:30:37.160> networks<00:30:37.490> and<00:30:37.820> things<00:30:38.060> over<00:30:38.270> here 00:30:38.410 --> 00:30:38.420 align:start position:0% do local networks and things over here 00:30:38.420 --> 00:30:41.590 align:start position:0% do local networks and things over here and<00:30:39.050> again<00:30:39.500> too<00:30:39.710> many<00:30:40.420> audience<00:30:41.420> who<00:30:41.570> are 00:30:41.590 --> 00:30:41.600 align:start position:0% and again too many audience who are 00:30:41.600 --> 00:30:44.350 align:start position:0% and again too many audience who are working<00:30:42.410> ledger<00:30:43.370> infrastructure<00:30:44.060> would<00:30:44.210> love 00:30:44.350 --> 00:30:44.360 align:start position:0% working ledger infrastructure would love 00:30:44.360 --> 00:30:45.750 align:start position:0% working ledger infrastructure would love to<00:30:44.480> blow<00:30:44.600> you<00:30:44.780> guys<00:30:44.840> they<00:30:45.110> can<00:30:45.290> as<00:30:45.410> well 00:30:45.750 --> 00:30:45.760 align:start position:0% to blow you guys they can as well 00:30:45.760 --> 00:30:47.800 align:start position:0% to blow you guys they can as well architecture<00:30:46.760> is<00:30:46.820> very<00:30:46.850> offensive<00:30:47.330> and<00:30:47.570> it's 00:30:47.800 --> 00:30:47.810 align:start position:0% architecture is very offensive and it's 00:30:47.810 --> 00:30:49.600 align:start position:0% architecture is very offensive and it's basically<00:30:48.140> extended<00:30:48.770> and<00:30:49.070> then<00:30:49.520> they 00:30:49.600 --> 00:30:49.610 align:start position:0% basically extended and then they 00:30:49.610 --> 00:30:51.100 align:start position:0% basically extended and then they basically<00:30:49.760> show<00:30:50.180> through<00:30:50.450> user<00:30:50.690> just<00:30:50.900> as<00:30:51.080> a 00:30:51.100 --> 00:30:51.110 align:start position:0% basically show through user just as a 00:30:51.110 --> 00:30:53.140 align:start position:0% basically show through user just as a choices<00:30:51.620> so<00:30:52.310> again<00:30:52.520> they<00:30:52.640> didn't<00:30:52.850> have<00:30:52.940> to<00:30:53.030> do 00:30:53.140 --> 00:30:53.150 align:start position:0% choices so again they didn't have to do 00:30:53.150 --> 00:30:54.370 align:start position:0% choices so again they didn't have to do anything<00:30:53.390> they<00:30:53.750> didn't<00:30:53.930> have<00:30:54.020> to<00:30:54.080> go<00:30:54.200> get 00:30:54.370 --> 00:30:54.380 align:start position:0% anything they didn't have to go get 00:30:54.380 --> 00:30:55.930 align:start position:0% anything they didn't have to go get Marcus<00:30:54.740> Ian<00:30:54.980> points<00:30:55.400> and<00:30:55.550> figure<00:30:55.670> out<00:30:55.820> like 00:30:55.930 --> 00:30:55.940 align:start position:0% Marcus Ian points and figure out like 00:30:55.940 --> 00:30:57.430 align:start position:0% Marcus Ian points and figure out like how<00:30:56.300> to<00:30:56.330> authenticate<00:30:56.660> for<00:30:57.080> this<00:30:57.230> thing 00:30:57.430 --> 00:30:57.440 align:start position:0% how to authenticate for this thing 00:30:57.440 --> 00:30:59.560 align:start position:0% how to authenticate for this thing that's<00:30:58.010> happening<00:30:58.370> for<00:30:58.580> them<00:30:58.820> I'm<00:30:59.120> happy<00:30:59.300> to 00:30:59.560 --> 00:30:59.570 align:start position:0% that's happening for them I'm happy to 00:30:59.570 --> 00:31:01.480 align:start position:0% that's happening for them I'm happy to talk<00:31:00.410> through<00:31:00.590> that<00:31:00.800> in<00:31:00.890> detail<00:31:00.920> if<00:31:01.370> you<00:31:01.430> want 00:31:01.480 --> 00:31:01.490 align:start position:0% talk through that in detail if you want 00:31:01.490 --> 00:31:02.890 align:start position:0% talk through that in detail if you want to<00:31:01.640> come<00:31:01.760> by<00:31:01.880> the<00:31:01.910> booth<00:31:02.120> I<00:31:02.330> can<00:31:02.480> tell<00:31:02.660> you<00:31:02.720> how 00:31:02.890 --> 00:31:02.900 align:start position:0% to come by the booth I can tell you how 00:31:02.900 --> 00:31:06.070 align:start position:0% to come by the booth I can tell you how we're<00:31:03.170> kind<00:31:03.440> of<00:31:03.590> doing<00:31:03.740> that<00:31:04.040> securely<00:31:05.080> to 00:31:06.070 --> 00:31:06.080 align:start position:0% we're kind of doing that securely to 00:31:06.080 --> 00:31:07.930 align:start position:0% we're kind of doing that securely to make<00:31:06.200> that<00:31:06.380> work<00:31:06.560> but<00:31:07.160> for<00:31:07.310> instance<00:31:07.610> is<00:31:07.730> just 00:31:07.930 --> 00:31:07.940 align:start position:0% make that work but for instance is just 00:31:07.940 --> 00:31:09.790 align:start position:0% make that work but for instance is just go<00:31:08.060> to<00:31:08.120> the<00:31:08.270> location<00:31:08.750> on<00:31:08.900> to<00:31:09.200> say<00:31:09.410> I<00:31:09.440> just<00:31:09.590> want 00:31:09.790 --> 00:31:09.800 align:start position:0% go to the location on to say I just want 00:31:09.800 --> 00:31:11.230 align:start position:0% go to the location on to say I just want to<00:31:09.950> do<00:31:10.010> something<00:31:10.340> quickly<00:31:10.550> because<00:31:11.030> we're 00:31:11.230 --> 00:31:11.240 align:start position:0% to do something quickly because we're 00:31:11.240 --> 00:31:14.050 align:start position:0% to do something quickly because we're going<00:31:11.360> to<00:31:11.710> try<00:31:12.710> this<00:31:12.770> out<00:31:13.040> so<00:31:13.760> you<00:31:13.850> can<00:31:13.940> see<00:31:13.970> I 00:31:14.050 --> 00:31:14.060 align:start position:0% going to try this out so you can see I 00:31:14.060 --> 00:31:15.940 align:start position:0% going to try this out so you can see I do<00:31:14.180> my<00:31:14.420> deployment<00:31:14.900> we<00:31:15.020> can<00:31:15.140> see<00:31:15.290> our<00:31:15.380> logs 00:31:15.940 --> 00:31:15.950 align:start position:0% do my deployment we can see our logs 00:31:15.950 --> 00:31:17.650 align:start position:0% do my deployment we can see our logs here<00:31:16.250> and<00:31:16.880> we<00:31:17.000> got<00:31:17.120> our<00:31:17.210> build<00:31:17.360> floors 00:31:17.650 --> 00:31:17.660 align:start position:0% here and we got our build floors 00:31:17.660 --> 00:31:19.000 align:start position:0% here and we got our build floors everything<00:31:18.170> came<00:31:18.350> now 00:31:19.000 --> 00:31:19.010 align:start position:0% everything came now 00:31:19.010 --> 00:31:21.010 align:start position:0% everything came now now<00:31:19.220> the<00:31:19.340> next<00:31:19.550> step<00:31:19.730> you<00:31:19.850> said<00:31:20.060> was<00:31:20.270> well<00:31:20.570> once 00:31:21.010 --> 00:31:21.020 align:start position:0% now the next step you said was well once 00:31:21.020 --> 00:31:23.320 align:start position:0% now the next step you said was well once you<00:31:21.140> get<00:31:21.440> to<00:31:21.530> this<00:31:21.650> stage<00:31:21.890> you<00:31:22.490> know<00:31:22.610> 30<00:31:22.880> users 00:31:23.320 --> 00:31:23.330 align:start position:0% you get to this stage you know 30 users 00:31:23.330 --> 00:31:24.790 align:start position:0% you get to this stage you know 30 users or<00:31:23.390> look<00:31:23.540> like<00:31:23.720> well<00:31:24.050> that's<00:31:24.200> great<00:31:24.440> like 00:31:24.790 --> 00:31:24.800 align:start position:0% or look like well that's great like 00:31:24.800 --> 00:31:26.920 align:start position:0% or look like well that's great like everything<00:31:25.250> worked<00:31:25.490> how<00:31:26.150> do<00:31:26.210> I<00:31:26.360> like<00:31:26.570> work 00:31:26.920 --> 00:31:26.930 align:start position:0% everything worked how do I like work 00:31:26.930 --> 00:31:29.230 align:start position:0% everything worked how do I like work with<00:31:27.140> this<00:31:27.230> thing<00:31:27.500> I<00:31:28.190> didn't<00:31:28.820> build<00:31:28.910> an<00:31:29.060> app 00:31:29.230 --> 00:31:29.240 align:start position:0% with this thing I didn't build an app 00:31:29.240 --> 00:31:31.090 align:start position:0% with this thing I didn't build an app yet<00:31:29.510> I<00:31:29.750> just<00:31:29.840> want<00:31:30.170> to<00:31:30.230> like<00:31:30.380> work<00:31:30.590> with<00:31:30.800> it<00:31:30.920> and 00:31:31.090 --> 00:31:31.100 align:start position:0% yet I just want to like work with it and 00:31:31.100 --> 00:31:33.070 align:start position:0% yet I just want to like work with it and so<00:31:31.700> in<00:31:31.820> this<00:31:31.910> case<00:31:31.970> they<00:31:32.420> could<00:31:32.480> drop<00:31:32.870> to<00:31:32.930> a 00:31:33.070 --> 00:31:33.080 align:start position:0% so in this case they could drop to a 00:31:33.080 --> 00:31:34.540 align:start position:0% so in this case they could drop to a command<00:31:33.380> line<00:31:33.560> and<00:31:33.770> do<00:31:33.890> that<00:31:34.070> then<00:31:34.430> they're 00:31:34.540 --> 00:31:34.550 align:start position:0% command line and do that then they're 00:31:34.550 --> 00:31:36.940 align:start position:0% command line and do that then they're gonna<00:31:34.640> have<00:31:34.730> to<00:31:34.910> go<00:31:35.090> read<00:31:35.330> and<00:31:36.260> hopefully<00:31:36.830> they 00:31:36.940 --> 00:31:36.950 align:start position:0% gonna have to go read and hopefully they 00:31:36.950 --> 00:31:39.280 align:start position:0% gonna have to go read and hopefully they know<00:31:37.070> how<00:31:37.220> to<00:31:37.250> read<00:31:37.520> and<00:31:38.000> they<00:31:38.150> will<00:31:38.360> read<00:31:38.600> but 00:31:39.280 --> 00:31:39.290 align:start position:0% know how to read and they will read but 00:31:39.290 --> 00:31:40.870 align:start position:0% know how to read and they will read but you<00:31:39.590> know<00:31:39.890> they're<00:31:40.280> trying<00:31:40.550> to<00:31:40.580> get<00:31:40.700> things 00:31:40.870 --> 00:31:40.880 align:start position:0% you know they're trying to get things 00:31:40.880 --> 00:31:42.700 align:start position:0% you know they're trying to get things done<00:31:41.090> quickly<00:31:41.390> so<00:31:41.570> we<00:31:41.810> say<00:31:41.990> okay<00:31:42.260> we<00:31:42.410> created 00:31:42.700 --> 00:31:42.710 align:start position:0% done quickly so we say okay we created 00:31:42.710 --> 00:31:45.520 align:start position:0% done quickly so we say okay we created this<00:31:42.830> contract<00:31:43.310> interaction<00:31:43.910> page<00:31:44.530> minimize 00:31:45.520 --> 00:31:45.530 align:start position:0% this contract interaction page minimize 00:31:45.530 --> 00:31:46.120 align:start position:0% this contract interaction page minimize some<00:31:45.740> things 00:31:46.120 --> 00:31:46.130 align:start position:0% some things 00:31:46.130 --> 00:31:47.890 align:start position:0% some things is<00:31:46.340> this<00:31:46.490> a<00:31:46.550> react<00:31:47.000> application<00:31:47.660> that's 00:31:47.890 --> 00:31:47.900 align:start position:0% is this a react application that's 00:31:47.900 --> 00:31:49.990 align:start position:0% is this a react application that's inside<00:31:48.200> here<00:31:48.440> that<00:31:48.650> basically<00:31:49.250> is<00:31:49.790> then 00:31:49.990 --> 00:31:50.000 align:start position:0% inside here that basically is then 00:31:50.000 --> 00:31:52.180 align:start position:0% inside here that basically is then reading<00:31:50.600> our<00:31:50.780> contract<00:31:51.620> so<00:31:51.800> this<00:31:51.920> is<00:31:52.040> dynamic 00:31:52.180 --> 00:31:52.190 align:start position:0% reading our contract so this is dynamic 00:31:52.190 --> 00:31:54.100 align:start position:0% reading our contract so this is dynamic this<00:31:52.820> knows<00:31:53.030> what<00:31:53.240> methods<00:31:53.570> repairs<00:31:53.960> the 00:31:54.100 --> 00:31:54.110 align:start position:0% this knows what methods repairs the 00:31:54.110 --> 00:31:55.930 align:start position:0% this knows what methods repairs the latrine<00:31:54.500> methods<00:31:54.860> in<00:31:54.980> my<00:31:55.100> contract 00:31:55.930 --> 00:31:55.940 align:start position:0% latrine methods in my contract 00:31:55.940 --> 00:31:58.270 align:start position:0% latrine methods in my contract request<00:31:56.300> said<00:31:56.660> response<00:31:57.050> five<00:31:57.920> has<00:31:58.130> the 00:31:58.270 --> 00:31:58.280 align:start position:0% request said response five has the 00:31:58.280 --> 00:31:59.890 align:start position:0% request said response five has the deployment<00:31:58.760> so<00:31:58.880> if<00:31:58.940> I<00:31:59.030> do<00:31:59.090> multiple<00:31:59.630> this 00:31:59.890 --> 00:31:59.900 align:start position:0% deployment so if I do multiple this 00:31:59.900 --> 00:32:02.470 align:start position:0% deployment so if I do multiple this drop-down<00:32:00.200> list<00:32:00.530> will<00:32:00.590> fill<00:32:00.860> up<00:32:01.060> it<00:32:02.060> also<00:32:02.210> has 00:32:02.470 --> 00:32:02.480 align:start position:0% drop-down list will fill up it also has 00:32:02.480 --> 00:32:03.910 align:start position:0% drop-down list will fill up it also has a<00:32:02.510> bunch<00:32:02.720> of<00:32:02.810> metadata<00:32:03.110> like<00:32:03.440> where<00:32:03.710> does<00:32:03.800> this 00:32:03.910 --> 00:32:03.920 align:start position:0% a bunch of metadata like where does this 00:32:03.920 --> 00:32:05.380 align:start position:0% a bunch of metadata like where does this thing<00:32:04.070> get<00:32:04.190> deployed<00:32:04.460> to<00:32:04.730> from<00:32:05.030> all<00:32:05.270> the 00:32:05.380 --> 00:32:05.390 align:start position:0% thing get deployed to from all the 00:32:05.390 --> 00:32:07.270 align:start position:0% thing get deployed to from all the address<00:32:05.720> detail<00:32:06.110> you<00:32:06.320> can<00:32:06.500> copy<00:32:06.710> and<00:32:06.860> paste<00:32:07.070> my 00:32:07.270 --> 00:32:07.280 align:start position:0% address detail you can copy and paste my 00:32:07.280 --> 00:32:09.460 align:start position:0% address detail you can copy and paste my code<00:32:07.310> and<00:32:07.640> API<00:32:07.880> if<00:32:08.180> you<00:32:08.270> need<00:32:08.510> them<00:32:08.660> and<00:32:09.440> you 00:32:09.460 --> 00:32:09.470 align:start position:0% code and API if you need them and you 00:32:09.470 --> 00:32:11.050 align:start position:0% code and API if you need them and you start<00:32:09.800> building<00:32:09.920> your<00:32:10.070> application<00:32:10.640> so<00:32:10.910> we 00:32:11.050 --> 00:32:11.060 align:start position:0% start building your application so we 00:32:11.060 --> 00:32:13.000 align:start position:0% start building your application so we thought<00:32:11.330> that<00:32:11.510> might<00:32:11.630> be<00:32:11.780> a<00:32:11.810> good<00:32:12.020> thing<00:32:12.050> and 00:32:13.000 --> 00:32:13.010 align:start position:0% thought that might be a good thing and 00:32:13.010 --> 00:32:14.320 align:start position:0% thought that might be a good thing and then<00:32:13.190> you<00:32:13.280> can<00:32:13.430> actually<00:32:13.550> interact<00:32:13.910> with<00:32:14.120> them 00:32:14.320 --> 00:32:14.330 align:start position:0% then you can actually interact with them 00:32:14.330 --> 00:32:17.980 align:start position:0% then you can actually interact with them so<00:32:14.480> if<00:32:14.540> I<00:32:14.660> set<00:32:14.840> a<00:32:14.870> test<00:32:15.140> request<00:32:16.450> by<00:32:17.450> executed 00:32:17.980 --> 00:32:17.990 align:start position:0% so if I set a test request by executed 00:32:17.990 --> 00:32:19.570 align:start position:0% so if I set a test request by executed you<00:32:18.080> can<00:32:18.200> see<00:32:18.350> the<00:32:18.470> state<00:32:18.710> filled<00:32:18.950> up<00:32:19.070> I'll 00:32:19.570 --> 00:32:19.580 align:start position:0% you can see the state filled up I'll 00:32:19.580 --> 00:32:20.740 align:start position:0% you can see the state filled up I'll show<00:32:19.790> you<00:32:19.850> in<00:32:20.000> a<00:32:20.060> second<00:32:20.420> and<00:32:20.480> it's<00:32:20.630> not 00:32:20.740 --> 00:32:20.750 align:start position:0% show you in a second and it's not 00:32:20.750 --> 00:32:22.150 align:start position:0% show you in a second and it's not smoking<00:32:21.170> mirrors<00:32:21.410> that<00:32:21.530> actually<00:32:21.920> went<00:32:22.100> to 00:32:22.150 --> 00:32:22.160 align:start position:0% smoking mirrors that actually went to 00:32:22.160 --> 00:32:24.700 align:start position:0% smoking mirrors that actually went to ganache<00:32:22.460> right<00:32:22.700> now<00:32:22.930> and<00:32:23.930> we<00:32:24.170> will<00:32:24.290> do<00:32:24.470> that<00:32:24.590> as 00:32:24.700 --> 00:32:24.710 align:start position:0% ganache right now and we will do that as 00:32:24.710 --> 00:32:27.790 align:start position:0% ganache right now and we will do that as will<00:32:24.890> do<00:32:25.010> a<00:32:25.040> debug<00:32:25.780> but<00:32:26.780> it<00:32:27.020> gets<00:32:27.170> also<00:32:27.530> seen 00:32:27.790 --> 00:32:27.800 align:start position:0% will do a debug but it gets also seen 00:32:27.800 --> 00:32:31.470 align:start position:0% will do a debug but it gets also seen you<00:32:27.950> could<00:32:28.160> get<00:32:28.310> a<00:32:28.340> response<00:32:28.670> messy<00:32:29.740> response 00:32:31.470 --> 00:32:31.480 align:start position:0% you could get a response messy response 00:32:31.480 --> 00:32:33.580 align:start position:0% you could get a response messy response you<00:32:32.480> see<00:32:32.630> that<00:32:32.780> was<00:32:32.900> filled<00:32:33.110> in<00:32:33.200> so<00:32:33.350> this<00:32:33.440> is 00:32:33.580 --> 00:32:33.590 align:start position:0% you see that was filled in so this is 00:32:33.590 --> 00:32:35.230 align:start position:0% you see that was filled in so this is basically<00:32:33.890> showing<00:32:34.010> the<00:32:34.190> state<00:32:34.520> and<00:32:34.850> these 00:32:35.230 --> 00:32:35.240 align:start position:0% basically showing the state and these 00:32:35.240 --> 00:32:36.790 align:start position:0% basically showing the state and these are<00:32:35.390> all<00:32:35.540> your<00:32:35.750> actions<00:32:36.170> that<00:32:36.350> are<00:32:36.470> inside<00:32:36.770> of 00:32:36.790 --> 00:32:36.800 align:start position:0% are all your actions that are inside of 00:32:36.800 --> 00:32:37.590 align:start position:0% are all your actions that are inside of there 00:32:37.590 --> 00:32:37.600 align:start position:0% there 00:32:37.600 --> 00:32:40.420 align:start position:0% there like<00:32:38.600> this<00:32:38.840> is<00:32:38.960> not<00:32:39.110> smoking<00:32:39.470> here<00:32:39.680> so<00:32:39.980> we<00:32:40.220> pull 00:32:40.420 --> 00:32:40.430 align:start position:0% like this is not smoking here so we pull 00:32:40.430 --> 00:32:42.820 align:start position:0% like this is not smoking here so we pull up<00:32:40.520> our<00:32:40.900> command<00:32:41.900> palette<00:32:42.080> you<00:32:42.230> can<00:32:42.260> go<00:32:42.560> into<00:32:42.710> a 00:32:42.820 --> 00:32:42.830 align:start position:0% up our command palette you can go into a 00:32:42.830 --> 00:32:45.070 align:start position:0% up our command palette you can go into a debug<00:32:43.160> transaction<00:32:43.910> if<00:32:44.600> you<00:32:44.720> look<00:32:44.870> really 00:32:45.070 --> 00:32:45.080 align:start position:0% debug transaction if you look really 00:32:45.080 --> 00:32:46.540 align:start position:0% debug transaction if you look really closely<00:32:45.410> maybe<00:32:45.860> you<00:32:45.980> can't<00:32:46.130> see<00:32:46.190> it<00:32:46.310> in<00:32:46.460> the 00:32:46.540 --> 00:32:46.550 align:start position:0% closely maybe you can't see it in the 00:32:46.550 --> 00:32:47.980 align:start position:0% closely maybe you can't see it in the back<00:32:46.700> but<00:32:46.730> we<00:32:47.360> give<00:32:47.480> you<00:32:47.570> a<00:32:47.630> hint 00:32:47.980 --> 00:32:47.990 align:start position:0% back but we give you a hint 00:32:47.990 --> 00:32:49.270 align:start position:0% back but we give you a hint these<00:32:48.110> are<00:32:48.260> all<00:32:48.380> the<00:32:48.470> transactions<00:32:49.100> that<00:32:49.130> have 00:32:49.270 --> 00:32:49.280 align:start position:0% these are all the transactions that have 00:32:49.280 --> 00:32:51.550 align:start position:0% these are all the transactions that have happened<00:32:49.430> recently<00:32:49.930> and<00:32:50.930> you<00:32:51.050> can<00:32:51.200> see<00:32:51.350> there 00:32:51.550 --> 00:32:51.560 align:start position:0% happened recently and you can see there 00:32:51.560 --> 00:32:53.290 align:start position:0% happened recently and you can see there this<00:32:51.710> is<00:32:51.890> set<00:32:52.040> response<00:32:52.430> and<00:32:52.700> this<00:32:53.000> one<00:32:53.180> was 00:32:53.290 --> 00:32:53.300 align:start position:0% this is set response and this one was 00:32:53.300 --> 00:32:55.540 align:start position:0% this is set response and this one was send<00:32:53.480> requests<00:32:53.870> that<00:32:53.930> you<00:32:54.080> snip<00:32:54.290> those<00:32:54.470> two<00:32:54.680> so 00:32:55.540 --> 00:32:55.550 align:start position:0% send requests that you snip those two so 00:32:55.550 --> 00:32:58.390 align:start position:0% send requests that you snip those two so if<00:32:55.610> you<00:32:55.700> click<00:32:55.910> on<00:32:56.090> this<00:32:57.040> basically<00:32:58.040> launch<00:32:58.310> a 00:32:58.390 --> 00:32:58.400 align:start position:0% if you click on this basically launch a 00:32:58.400 --> 00:33:00.820 align:start position:0% if you click on this basically launch a debug<00:32:58.700> session<00:32:58.910> for<00:32:59.240> you<00:32:59.440> will<00:33:00.440> commemorate 00:33:00.820 --> 00:33:00.830 align:start position:0% debug session for you will commemorate 00:33:00.830 --> 00:33:02.230 align:start position:0% debug session for you will commemorate everything<00:33:01.310> back<00:33:01.460> here<00:33:01.640> at<00:33:01.760> the<00:33:01.880> transaction 00:33:02.230 --> 00:33:02.240 align:start position:0% everything back here at the transaction 00:33:02.240 --> 00:33:04.300 align:start position:0% everything back here at the transaction level<00:33:02.450> but<00:33:03.080> we<00:33:03.200> need<00:33:03.440> all<00:33:03.530> those<00:33:03.650> details<00:33:03.920> you 00:33:04.300 --> 00:33:04.310 align:start position:0% level but we need all those details you 00:33:04.310 --> 00:33:05.530 align:start position:0% level but we need all those details you can<00:33:04.430> expand<00:33:04.730> this<00:33:04.880> stuff<00:33:05.090> to<00:33:05.240> your<00:33:05.330> heart's 00:33:05.530 --> 00:33:05.540 align:start position:0% can expand this stuff to your heart's 00:33:05.540 --> 00:33:07.660 align:start position:0% can expand this stuff to your heart's content<00:33:05.660> to<00:33:06.020> look<00:33:06.140> at<00:33:06.320> it<00:33:06.470> if<00:33:07.340> you<00:33:07.460> start 00:33:07.660 --> 00:33:07.670 align:start position:0% content to look at it if you start 00:33:07.670 --> 00:33:08.860 align:start position:0% content to look at it if you start jumping<00:33:07.880> in<00:33:08.120> here<00:33:08.240> with<00:33:08.390> your<00:33:08.510> function<00:33:08.840> keys 00:33:08.860 --> 00:33:08.870 align:start position:0% jumping in here with your function keys 00:33:08.870 --> 00:33:11.260 align:start position:0% jumping in here with your function keys as<00:33:09.290> normal<00:33:09.710> you'll<00:33:10.370> see<00:33:10.520> a<00:33:10.550> percent<00:33:10.880> response 00:33:11.260 --> 00:33:11.270 align:start position:0% as normal you'll see a percent response 00:33:11.270 --> 00:33:12.610 align:start position:0% as normal you'll see a percent response that<00:33:11.450> we<00:33:11.540> actually<00:33:11.690> called<00:33:12.050> there<00:33:12.260> you<00:33:12.500> can 00:33:12.610 --> 00:33:12.620 align:start position:0% that we actually called there you can 00:33:12.620 --> 00:33:14.110 align:start position:0% that we actually called there you can see<00:33:12.740> our<00:33:12.770> response<00:33:13.190> message<00:33:13.550> we<00:33:13.670> can<00:33:13.790> cover<00:33:13.970> it 00:33:14.110 --> 00:33:14.120 align:start position:0% see our response message we can cover it 00:33:14.120 --> 00:33:17.740 align:start position:0% see our response message we can cover it and<00:33:14.210> see<00:33:14.360> those<00:33:14.980> so<00:33:15.980> really<00:33:16.610> nicely<00:33:16.790> debugging 00:33:17.740 --> 00:33:17.750 align:start position:0% and see those so really nicely debugging 00:33:17.750 --> 00:33:20.110 align:start position:0% and see those so really nicely debugging interface<00:33:18.110> it<00:33:18.470> actually<00:33:18.890> breaks<00:33:19.430> down<00:33:19.700> even 00:33:20.110 --> 00:33:20.120 align:start position:0% interface it actually breaks down even 00:33:20.120 --> 00:33:21.430 align:start position:0% interface it actually breaks down even into<00:33:20.270> the<00:33:20.540> instruction<00:33:21.020> level<00:33:21.140> as<00:33:21.350> I 00:33:21.430 --> 00:33:21.440 align:start position:0% into the instruction level as I 00:33:21.440 --> 00:33:23.560 align:start position:0% into the instruction level as I mentioned<00:33:21.800> before<00:33:22.130> so<00:33:22.880> if<00:33:22.940> you're<00:33:22.970> a<00:33:23.120> public 00:33:23.560 --> 00:33:23.570 align:start position:0% mentioned before so if you're a public 00:33:23.570 --> 00:33:24.970 align:start position:0% mentioned before so if you're a public developer<00:33:24.050> you<00:33:24.140> might<00:33:24.260> be<00:33:24.440> be<00:33:24.560> concerned 00:33:24.970 --> 00:33:24.980 align:start position:0% developer you might be be concerned 00:33:24.980 --> 00:33:26.740 align:start position:0% developer you might be be concerned about<00:33:25.100> you<00:33:26.000> know<00:33:26.030> what's<00:33:26.360> happening<00:33:26.690> here 00:33:26.740 --> 00:33:26.750 align:start position:0% about you know what's happening here 00:33:26.750 --> 00:33:28.450 align:start position:0% about you know what's happening here their<00:33:27.140> store<00:33:27.380> calls<00:33:27.680> have<00:33:27.920> you<00:33:28.040> can<00:33:28.160> see<00:33:28.310> all 00:33:28.450 --> 00:33:28.460 align:start position:0% their store calls have you can see all 00:33:28.460 --> 00:33:30.519 align:start position:0% their store calls have you can see all that<00:33:28.670> stuff<00:33:28.730> directly 00:33:30.519 --> 00:33:30.529 align:start position:0% that stuff directly 00:33:30.529 --> 00:33:32.019 align:start position:0% that stuff directly so<00:33:31.219> we<00:33:31.279> think<00:33:31.369> that's<00:33:31.519> a<00:33:31.639> pretty<00:33:31.789> nice<00:33:31.969> thing 00:33:32.019 --> 00:33:32.029 align:start position:0% so we think that's a pretty nice thing 00:33:32.029 --> 00:33:34.539 align:start position:0% so we think that's a pretty nice thing for<00:33:32.469> users<00:33:33.469> who<00:33:33.499> are<00:33:33.649> like<00:33:34.039> trying<00:33:34.279> to<00:33:34.309> figure 00:33:34.539 --> 00:33:34.549 align:start position:0% for users who are like trying to figure 00:33:34.549 --> 00:33:35.889 align:start position:0% for users who are like trying to figure out<00:33:34.609> what's<00:33:34.820> broken<00:33:35.149> in<00:33:35.269> their<00:33:35.419> contracts 00:33:35.889 --> 00:33:35.899 align:start position:0% out what's broken in their contracts 00:33:35.899 --> 00:33:41.919 align:start position:0% out what's broken in their contracts really<00:33:36.229> quickly<00:33:36.619> in<00:33:37.489> Chinese<00:33:40.659> so<00:33:41.659> we<00:33:41.749> jump 00:33:41.919 --> 00:33:41.929 align:start position:0% really quickly in Chinese so we jump 00:33:41.929 --> 00:33:44.139 align:start position:0% really quickly in Chinese so we jump back<00:33:42.109> to<00:33:42.139> say<00:33:42.529> okay<00:33:42.769> our<00:33:42.950> typical<00:33:43.429> flow<00:33:43.639> was<00:33:43.909> we 00:33:44.139 --> 00:33:44.149 align:start position:0% back to say okay our typical flow was we 00:33:44.149 --> 00:33:45.820 align:start position:0% back to say okay our typical flow was we we<00:33:44.450> did<00:33:44.629> something<00:33:44.989> locally<00:33:45.379> there<00:33:45.590> we've 00:33:45.820 --> 00:33:45.830 align:start position:0% we did something locally there we've 00:33:45.830 --> 00:33:47.289 align:start position:0% we did something locally there we've deployed<00:33:46.099> it<00:33:46.309> everything<00:33:46.669> seems<00:33:46.909> to<00:33:46.999> be<00:33:47.090> good 00:33:47.289 --> 00:33:47.299 align:start position:0% deployed it everything seems to be good 00:33:47.299 --> 00:33:51.849 align:start position:0% deployed it everything seems to be good and<00:33:47.479> now<00:33:48.700> now<00:33:49.700> my<00:33:49.909> case<00:33:50.119> I<00:33:50.149> already<00:33:50.989> connected 00:33:51.849 --> 00:33:51.859 align:start position:0% and now now my case I already connected 00:33:51.859 --> 00:33:53.709 align:start position:0% and now now my case I already connected to<00:33:51.919> an<00:33:52.129> Hydra<00:33:52.369> blockchain<00:33:52.789> service<00:33:53.210> how<00:33:53.450> I<00:33:53.479> did 00:33:53.709 --> 00:33:53.719 align:start position:0% to an Hydra blockchain service how I did 00:33:53.719 --> 00:33:55.599 align:start position:0% to an Hydra blockchain service how I did that<00:33:53.869> I<00:33:54.139> can<00:33:54.679> connect<00:33:54.979> to<00:33:55.129> or<00:33:55.309> create<00:33:55.580> a 00:33:55.599 --> 00:33:55.609 align:start position:0% that I can connect to or create a 00:33:55.609 --> 00:33:58.239 align:start position:0% that I can connect to or create a network<00:33:55.999> here<00:33:56.149> so<00:33:57.080> if<00:33:57.169> I<00:33:57.259> say<00:33:57.440> connect<00:33:57.799> to<00:33:57.950> the 00:33:58.239 --> 00:33:58.249 align:start position:0% network here so if I say connect to the 00:33:58.249 --> 00:34:00.639 align:start position:0% network here so if I say connect to the sand<00:33:58.489> dip<00:33:58.700> your<00:33:58.879> manager<00:33:59.269> by<00:33:59.690> the<00:33:59.719> way<00:33:59.960> this 00:34:00.639 --> 00:34:00.649 align:start position:0% sand dip your manager by the way this 00:34:00.649 --> 00:34:02.139 align:start position:0% sand dip your manager by the way this week<00:34:00.859> in<00:34:01.039> furor<00:34:01.249> will<00:34:01.460> show<00:34:01.609> up<00:34:01.729> and<00:34:01.879> hit<00:34:01.969> drop 00:34:02.139 --> 00:34:02.149 align:start position:0% week in furor will show up and hit drop 00:34:02.149 --> 00:34:04.599 align:start position:0% week in furor will show up and hit drop down<00:34:02.330> as<00:34:02.479> well<00:34:02.629> so<00:34:02.710> the<00:34:03.710> same<00:34:03.950> experience<00:34:04.489> will 00:34:04.599 --> 00:34:04.609 align:start position:0% down as well so the same experience will 00:34:04.609 --> 00:34:06.489 align:start position:0% down as well so the same experience will happen<00:34:04.879> from<00:34:05.029> Europe<00:34:05.450> and<00:34:05.749> then<00:34:06.139> basically 00:34:06.489 --> 00:34:06.499 align:start position:0% happen from Europe and then basically 00:34:06.499 --> 00:34:08.349 align:start position:0% happen from Europe and then basically you<00:34:06.649> can<00:34:06.769> pick<00:34:06.919> your<00:34:07.009> subscription<00:34:07.609> in<00:34:07.849> Azure 00:34:08.349 --> 00:34:08.359 align:start position:0% you can pick your subscription in Azure 00:34:08.359 --> 00:34:09.970 align:start position:0% you can pick your subscription in Azure it's<00:34:08.899> very<00:34:09.139> context<00:34:09.529> sensitive<00:34:09.799> to<00:34:09.950> a 00:34:09.970 --> 00:34:09.980 align:start position:0% it's very context sensitive to a 00:34:09.980 --> 00:34:11.579 align:start position:0% it's very context sensitive to a subscription<00:34:10.279> in<00:34:10.609> the<00:34:10.669> resource<00:34:11.029> group 00:34:11.579 --> 00:34:11.589 align:start position:0% subscription in the resource group 00:34:11.589 --> 00:34:13.659 align:start position:0% subscription in the resource group interfere<00:34:12.589> and<00:34:12.770> but<00:34:12.919> basically<00:34:13.220> list<00:34:13.520> your 00:34:13.659 --> 00:34:13.669 align:start position:0% interfere and but basically list your 00:34:13.669 --> 00:34:15.309 align:start position:0% interfere and but basically list your projects<00:34:14.059> here<00:34:14.240> I<00:34:14.480> mean<00:34:14.750> you<00:34:14.929> can<00:34:15.079> pick<00:34:15.230> your 00:34:15.309 --> 00:34:15.319 align:start position:0% projects here I mean you can pick your 00:34:15.319 --> 00:34:17.859 align:start position:0% projects here I mean you can pick your project<00:34:15.799> up<00:34:16.159> there<00:34:16.490> get<00:34:16.700> your<00:34:16.789> horse<00:34:17.149> back<00:34:17.389> in 00:34:17.859 --> 00:34:17.869 align:start position:0% project up there get your horse back in 00:34:17.869 --> 00:34:19.990 align:start position:0% project up there get your horse back in this<00:34:18.049> place<00:34:18.230> it<00:34:18.589> will<00:34:18.679> see<00:34:19.190> what<00:34:19.369> consortiums 00:34:19.990 --> 00:34:20.000 align:start position:0% this place it will see what consortiums 00:34:20.000 --> 00:34:21.069 align:start position:0% this place it will see what consortiums up<00:34:20.089> there<00:34:20.299> in<00:34:20.569> my<00:34:20.690> case<00:34:20.869> I've<00:34:21.020> already 00:34:21.069 --> 00:34:21.079 align:start position:0% up there in my case I've already 00:34:21.079 --> 00:34:22.539 align:start position:0% up there in my case I've already connected<00:34:21.589> that<00:34:21.799> one<00:34:21.950> so<00:34:22.069> I<00:34:22.129> could<00:34:22.190> create<00:34:22.460> a 00:34:22.539 --> 00:34:22.549 align:start position:0% connected that one so I could create a 00:34:22.549 --> 00:34:24.730 align:start position:0% connected that one so I could create a do<00:34:22.669> it<00:34:22.839> you<00:34:23.839> know<00:34:23.960> what<00:34:24.079> I'll<00:34:24.139> do<00:34:24.409> everything 00:34:24.730 --> 00:34:24.740 align:start position:0% do it you know what I'll do everything 00:34:24.740 --> 00:34:26.289 align:start position:0% do it you know what I'll do everything for<00:34:24.889> me<00:34:25.039> I<00:34:25.099> don't<00:34:25.159> even<00:34:25.490> have<00:34:25.579> to<00:34:25.700> go<00:34:25.819> to<00:34:26.059> any 00:34:26.289 --> 00:34:26.299 align:start position:0% for me I don't even have to go to any 00:34:26.299 --> 00:34:28.210 align:start position:0% for me I don't even have to go to any other<00:34:26.389> portals<00:34:26.929> or<00:34:27.169> web<00:34:27.319> sites<00:34:27.559> it<00:34:27.799> will<00:34:27.919> spin 00:34:28.210 --> 00:34:28.220 align:start position:0% other portals or web sites it will spin 00:34:28.220 --> 00:34:30.250 align:start position:0% other portals or web sites it will spin up<00:34:28.339> that<00:34:28.490> consortium<00:34:28.760> for<00:34:29.149> me<00:34:29.270> it<00:34:29.419> takes<00:34:29.990> a<00:34:30.139> few 00:34:30.250 --> 00:34:30.260 align:start position:0% up that consortium for me it takes a few 00:34:30.260 --> 00:34:32.109 align:start position:0% up that consortium for me it takes a few minutes<00:34:30.379> so<00:34:30.619> we<00:34:30.980> will<00:34:31.010> do<00:34:31.309> that<00:34:31.490> right<00:34:31.520> now<00:34:31.700> if 00:34:32.109 --> 00:34:32.119 align:start position:0% minutes so we will do that right now if 00:34:32.119 --> 00:34:34.359 align:start position:0% minutes so we will do that right now if you<00:34:32.929> expand<00:34:33.379> this<00:34:33.500> you'll<00:34:33.829> see<00:34:34.069> that<00:34:34.220> we<00:34:34.339> have 00:34:34.359 --> 00:34:34.369 align:start position:0% you expand this you'll see that we have 00:34:34.369 --> 00:34:37.059 align:start position:0% you expand this you'll see that we have a<00:34:34.659> context<00:34:35.659> of<00:34:35.779> a<00:34:36.020> sure<00:34:36.260> we<00:34:36.889> have<00:34:37.039> our 00:34:37.059 --> 00:34:37.069 align:start position:0% a context of a sure we have our 00:34:37.069 --> 00:34:39.129 align:start position:0% a context of a sure we have our consortium<00:34:37.429> remember<00:34:38.149> our<00:34:38.389> transaction<00:34:38.960> node 00:34:39.129 --> 00:34:39.139 align:start position:0% consortium remember our transaction node 00:34:39.139 --> 00:34:40.930 align:start position:0% consortium remember our transaction node if<00:34:39.710> you<00:34:39.829> right-click<00:34:40.010> on<00:34:40.309> the<00:34:40.399> transaction 00:34:40.930 --> 00:34:40.940 align:start position:0% if you right-click on the transaction 00:34:40.940 --> 00:34:42.519 align:start position:0% if you right-click on the transaction and<00:34:41.059> you<00:34:41.179> can<00:34:41.329> see<00:34:41.450> we<00:34:41.539> get<00:34:41.690> to<00:34:41.779> our<00:34:41.869> PC<00:34:42.169> address 00:34:42.519 --> 00:34:42.529 align:start position:0% and you can see we get to our PC address 00:34:42.529 --> 00:34:44.409 align:start position:0% and you can see we get to our PC address again<00:34:42.950> if<00:34:43.190> you're<00:34:43.309> building<00:34:43.579> an<00:34:43.639> app<00:34:43.789> you 00:34:44.409 --> 00:34:44.419 align:start position:0% again if you're building an app you 00:34:44.419 --> 00:34:45.970 align:start position:0% again if you're building an app you typically<00:34:44.750> need<00:34:44.869> a<00:34:45.020> like<00:34:45.559> as<00:34:45.710> soon<00:34:45.859> as<00:34:45.919> you 00:34:45.970 --> 00:34:45.980 align:start position:0% typically need a like as soon as you 00:34:45.980 --> 00:34:47.799 align:start position:0% typically need a like as soon as you start<00:34:46.250> like<00:34:46.399> writing<00:34:46.609> JavaScript<00:34:47.299> code<00:34:47.450> or 00:34:47.799 --> 00:34:47.809 align:start position:0% start like writing JavaScript code or 00:34:47.809 --> 00:34:48.819 align:start position:0% start like writing JavaScript code or something<00:34:48.079> like<00:34:48.200> that<00:34:48.379> you're<00:34:48.559> gonna<00:34:48.649> need 00:34:48.819 --> 00:34:48.829 align:start position:0% something like that you're gonna need 00:34:48.829 --> 00:34:50.440 align:start position:0% something like that you're gonna need that<00:34:49.010> you<00:34:49.490> can<00:34:49.609> just<00:34:49.760> grab<00:34:49.849> this<00:34:50.089> and<00:34:50.240> put<00:34:50.419> it 00:34:50.440 --> 00:34:50.450 align:start position:0% that you can just grab this and put it 00:34:50.450 --> 00:34:51.789 align:start position:0% that you can just grab this and put it right<00:34:50.599> in<00:34:50.690> your<00:34:50.750> clipboard<00:34:51.169> you<00:34:51.289> can<00:34:51.440> use<00:34:51.619> it 00:34:51.789 --> 00:34:51.799 align:start position:0% right in your clipboard you can use it 00:34:51.799 --> 00:34:54.129 align:start position:0% right in your clipboard you can use it get<00:34:52.429> all<00:34:52.549> the<00:34:52.669> disconnect<00:34:53.359> if<00:34:53.750> we<00:34:53.839> do<00:34:53.960> not 00:34:54.129 --> 00:34:54.139 align:start position:0% get all the disconnect if we do not 00:34:54.139 --> 00:34:55.720 align:start position:0% get all the disconnect if we do not using<00:34:54.440> this<00:34:54.529> consortium<00:34:54.829> anymore<00:34:55.369> they'll 00:34:55.720 --> 00:34:55.730 align:start position:0% using this consortium anymore they'll 00:34:55.730 --> 00:34:56.950 align:start position:0% using this consortium anymore they'll still<00:34:55.970> keep<00:34:56.149> it<00:34:56.270> there<00:34:56.450> we're<00:34:56.629> just<00:34:56.809> basically 00:34:56.950 --> 00:34:56.960 align:start position:0% still keep it there we're just basically 00:34:56.960 --> 00:34:59.049 align:start position:0% still keep it there we're just basically disconnecting<00:34:57.859> from<00:34:57.890> it<00:34:58.190> the<00:34:58.760> exact<00:34:59.029> same 00:34:59.049 --> 00:34:59.059 align:start position:0% disconnecting from it the exact same 00:34:59.059 --> 00:35:00.760 align:start position:0% disconnecting from it the exact same thing<00:34:59.390> happens<00:34:59.690> with<00:34:59.809> the<00:34:59.930> pure<00:35:00.140> except<00:35:00.559> for 00:35:00.760 --> 00:35:00.770 align:start position:0% thing happens with the pure except for 00:35:00.770 --> 00:35:02.650 align:start position:0% thing happens with the pure except for and<00:35:01.069> wish<00:35:01.250> I<00:35:01.309> can<00:35:01.430> show<00:35:01.549> you<00:35:01.609> here<00:35:01.819> but<00:35:01.880> we're 00:35:02.650 --> 00:35:02.660 align:start position:0% and wish I can show you here but we're 00:35:02.660 --> 00:35:03.940 align:start position:0% and wish I can show you here but we're just<00:35:02.690> publishing<00:35:03.260> you're<00:35:03.470> actually<00:35:03.770> right 00:35:03.940 --> 00:35:03.950 align:start position:0% just publishing you're actually right 00:35:03.950 --> 00:35:04.300 align:start position:0% just publishing you're actually right now 00:35:04.300 --> 00:35:04.310 align:start position:0% now 00:35:04.310 --> 00:35:06.160 align:start position:0% now but<00:35:04.760> it'll<00:35:05.000> basically<00:35:05.150> show<00:35:05.720> you<00:35:05.750> all<00:35:06.050> the 00:35:06.160 --> 00:35:06.170 align:start position:0% but it'll basically show you all the 00:35:06.170 --> 00:35:07.420 align:start position:0% but it'll basically show you all the gnomes<00:35:06.350> underneath<00:35:06.740> there<00:35:06.950> for<00:35:07.250> the 00:35:07.420 --> 00:35:07.430 align:start position:0% gnomes underneath there for the 00:35:07.430 --> 00:35:08.620 align:start position:0% gnomes underneath there for the different<00:35:07.700> networks<00:35:08.000> whether<00:35:08.210> it<00:35:08.330> be<00:35:08.420> rock 00:35:08.620 --> 00:35:08.630 align:start position:0% different networks whether it be rock 00:35:08.630 --> 00:35:10.660 align:start position:0% different networks whether it be rock scene<00:35:08.930> ring<00:35:09.200> be<00:35:09.380> you<00:35:09.950> know<00:35:10.070> main<00:35:10.280> tent<00:35:10.490> those 00:35:10.660 --> 00:35:10.670 align:start position:0% scene ring be you know main tent those 00:35:10.670 --> 00:35:14.170 align:start position:0% scene ring be you know main tent those kind<00:35:10.910> of<00:35:10.940> things<00:35:11.180> same<00:35:11.660> experience<00:35:13.030> and<00:35:14.030> then 00:35:14.170 --> 00:35:14.180 align:start position:0% kind of things same experience and then 00:35:14.180 --> 00:35:15.700 align:start position:0% kind of things same experience and then basically<00:35:14.540> whenever<00:35:14.870> we<00:35:15.080> go<00:35:15.170> to<00:35:15.320> the<00:35:15.410> puddin 00:35:15.700 --> 00:35:15.710 align:start position:0% basically whenever we go to the puddin 00:35:15.710 --> 00:35:17.590 align:start position:0% basically whenever we go to the puddin that<00:35:15.830> it's<00:35:16.010> the<00:35:16.100> same<00:35:16.280> process<00:35:16.550> so<00:35:17.210> once<00:35:17.420> this 00:35:17.590 --> 00:35:17.600 align:start position:0% that it's the same process so once this 00:35:17.600 --> 00:35:19.720 align:start position:0% that it's the same process so once this comes<00:35:17.780> up<00:35:17.990> one<00:35:18.170> deployment<00:35:18.430> we<00:35:19.430> would<00:35:19.610> pick 00:35:19.720 --> 00:35:19.730 align:start position:0% comes up one deployment we would pick 00:35:19.730 --> 00:35:25.330 align:start position:0% comes up one deployment we would pick this<00:35:19.910> guy<00:35:20.680> and<00:35:23.860> you'll<00:35:24.860> notice<00:35:25.010> in<00:35:25.190> this<00:35:25.280> case 00:35:25.330 --> 00:35:25.340 align:start position:0% this guy and you'll notice in this case 00:35:25.340 --> 00:35:27.880 align:start position:0% this guy and you'll notice in this case whenever<00:35:25.910> I<00:35:25.970> hit<00:35:26.150> a<00:35:26.330> network<00:35:26.780> it's<00:35:27.050> not<00:35:27.110> local 00:35:27.880 --> 00:35:27.890 align:start position:0% whenever I hit a network it's not local 00:35:27.890 --> 00:35:29.770 align:start position:0% whenever I hit a network it's not local I<00:35:27.920> need<00:35:28.490> a<00:35:28.520> mnemonic<00:35:28.700> so<00:35:29.420> I<00:35:29.450> can<00:35:29.630> either 00:35:29.770 --> 00:35:29.780 align:start position:0% I need a mnemonic so I can either 00:35:29.780 --> 00:35:31.630 align:start position:0% I need a mnemonic so I can either generate<00:35:29.960> a<00:35:30.200> new<00:35:30.380> one<00:35:30.410> here<00:35:30.740> or<00:35:31.070> I<00:35:31.100> can<00:35:31.190> use<00:35:31.430> one 00:35:31.630 --> 00:35:31.640 align:start position:0% generate a new one here or I can use one 00:35:31.640 --> 00:35:33.490 align:start position:0% generate a new one here or I can use one that<00:35:31.760> I<00:35:31.850> have<00:35:31.940> existing<00:35:32.420> which<00:35:33.140> is<00:35:33.260> here<00:35:33.470> on 00:35:33.490 --> 00:35:33.500 align:start position:0% that I have existing which is here on 00:35:33.500 --> 00:35:34.080 align:start position:0% that I have existing which is here on disk 00:35:34.080 --> 00:35:34.090 align:start position:0% disk 00:35:34.090 --> 00:35:36.640 align:start position:0% disk so<00:35:35.090> we<00:35:35.240> initially<00:35:35.450> give<00:35:36.290> you<00:35:36.350> some<00:35:36.470> feedback 00:35:36.640 --> 00:35:36.650 align:start position:0% so we initially give you some feedback 00:35:36.650 --> 00:35:40.510 align:start position:0% so we initially give you some feedback here<00:35:38.860> initially<00:35:39.860> we<00:35:39.980> wanted<00:35:40.100> to<00:35:40.280> make<00:35:40.400> this 00:35:40.510 --> 00:35:40.520 align:start position:0% here initially we wanted to make this 00:35:40.520 --> 00:35:42.100 align:start position:0% here initially we wanted to make this super<00:35:40.820> easy<00:35:40.850> to<00:35:41.150> get<00:35:41.270> free<00:35:41.450> users<00:35:41.750> to<00:35:41.900> say<00:35:42.080> I 00:35:42.100 --> 00:35:42.110 align:start position:0% super easy to get free users to say I 00:35:42.110 --> 00:35:43.990 align:start position:0% super easy to get free users to say I don't<00:35:42.290> know<00:35:42.590> what<00:35:42.710> lot<00:35:42.920> is<00:35:43.190> they<00:35:43.370> can<00:35:43.640> generate 00:35:43.990 --> 00:35:44.000 align:start position:0% don't know what lot is they can generate 00:35:44.000 --> 00:35:45.970 align:start position:0% don't know what lot is they can generate they<00:35:44.420> don't<00:35:44.570> open<00:35:44.930> file<00:35:45.350> location'<00:35:45.830> things 00:35:45.970 --> 00:35:45.980 align:start position:0% they don't open file location' things 00:35:45.980 --> 00:35:47.850 align:start position:0% they don't open file location' things but<00:35:46.130> if<00:35:46.220> you<00:35:46.280> just<00:35:46.430> be<00:35:46.550> drawing<00:35:46.850> or<00:35:47.000> wherever 00:35:47.850 --> 00:35:47.860 align:start position:0% but if you just be drawing or wherever 00:35:47.860 --> 00:35:49.990 align:start position:0% but if you just be drawing or wherever it's<00:35:48.860> gonna<00:35:49.040> get<00:35:49.100> enough<00:35:49.370> like<00:35:49.670> from<00:35:49.880> a 00:35:49.990 --> 00:35:50.000 align:start position:0% it's gonna get enough like from a 00:35:50.000 --> 00:35:52.000 align:start position:0% it's gonna get enough like from a security<00:35:50.330> perspective<00:35:50.650> so<00:35:51.650> what<00:35:51.800> we've<00:35:51.920> been 00:35:52.000 --> 00:35:52.010 align:start position:0% security perspective so what we've been 00:35:52.010 --> 00:35:54.100 align:start position:0% security perspective so what we've been doing<00:35:52.280> is<00:35:52.430> working<00:35:52.550> our<00:35:52.850> HD<00:35:53.540> wallet<00:35:53.780> provider 00:35:54.100 --> 00:35:54.110 align:start position:0% doing is working our HD wallet provider 00:35:54.110 --> 00:35:56.050 align:start position:0% doing is working our HD wallet provider so<00:35:54.470> that<00:35:54.590> we<00:35:54.710> can<00:35:54.890> provide<00:35:55.160> two<00:35:55.490> options<00:35:55.880> one 00:35:56.050 --> 00:35:56.060 align:start position:0% so that we can provide two options one 00:35:56.060 --> 00:35:58.420 align:start position:0% so that we can provide two options one is<00:35:56.120> have<00:35:56.630> this<00:35:56.840> encrypted<00:35:57.680> file<00:35:57.980> wherever<00:35:58.280> you 00:35:58.420 --> 00:35:58.430 align:start position:0% is have this encrypted file wherever you 00:35:58.430 --> 00:35:59.980 align:start position:0% is have this encrypted file wherever you want<00:35:58.580> to<00:35:58.640> put<00:35:58.730> that<00:35:58.880> thing<00:35:59.090> the<00:35:59.570> other<00:35:59.630> one<00:35:59.870> is 00:35:59.980 --> 00:35:59.990 align:start position:0% want to put that thing the other one is 00:35:59.990 --> 00:36:02.860 align:start position:0% want to put that thing the other one is you<00:36:00.110> know<00:36:00.500> real<00:36:00.680> HSN<00:36:01.180> so<00:36:02.180> families<00:36:02.570> just<00:36:02.690> have 00:36:02.860 --> 00:36:02.870 align:start position:0% you know real HSN so families just have 00:36:02.870 --> 00:36:04.780 align:start position:0% you know real HSN so families just have an<00:36:03.020> azure<00:36:03.170> there<00:36:04.010> are<00:36:04.130> others<00:36:04.340> that<00:36:04.550> we<00:36:04.610> exist 00:36:04.780 --> 00:36:04.790 align:start position:0% an azure there are others that we exist 00:36:04.790 --> 00:36:06.640 align:start position:0% an azure there are others that we exist out<00:36:05.000> there<00:36:05.030> but<00:36:05.750> basically<00:36:05.870> you<00:36:06.290> can<00:36:06.440> choose 00:36:06.640 --> 00:36:06.650 align:start position:0% out there but basically you can choose 00:36:06.650 --> 00:36:08.830 align:start position:0% out there but basically you can choose to<00:36:06.860> use<00:36:07.040> an<00:36:07.160> HSM<00:36:07.610> to<00:36:07.790> hold<00:36:08.030> that<00:36:08.150> demonic<00:36:08.510> that 00:36:08.830 --> 00:36:08.840 align:start position:0% to use an HSM to hold that demonic that 00:36:08.840 --> 00:36:10.570 align:start position:0% to use an HSM to hold that demonic that secret<00:36:09.290> so<00:36:10.010> that<00:36:10.190> they<00:36:10.250> can't<00:36:10.460> get 00:36:10.570 --> 00:36:10.580 align:start position:0% secret so that they can't get 00:36:10.580 --> 00:36:13.480 align:start position:0% secret so that they can't get compromised<00:36:11.000> just<00:36:12.010> something<00:36:13.010> we're 00:36:13.480 --> 00:36:13.490 align:start position:0% compromised just something we're 00:36:13.490 --> 00:36:17.290 align:start position:0% compromised just something we're actively<00:36:13.820> working<00:36:14.060> on<00:36:15.970> but<00:36:16.970> if<00:36:17.060> I<00:36:17.120> put<00:36:17.270> a 00:36:17.290 --> 00:36:17.300 align:start position:0% actively working on but if I put a 00:36:17.300 --> 00:36:18.880 align:start position:0% actively working on but if I put a pneumonic<00:36:17.600> in<00:36:17.900> here<00:36:18.140> and<00:36:18.500> I<00:36:18.560> look<00:36:18.710> at<00:36:18.800> my 00:36:18.880 --> 00:36:18.890 align:start position:0% pneumonic in here and I look at my 00:36:18.890 --> 00:36:21.160 align:start position:0% pneumonic in here and I look at my output<00:36:19.220> window<00:36:19.540> it's<00:36:20.540> a<00:36:20.600> little<00:36:20.840> bit<00:36:20.960> slower 00:36:21.160 --> 00:36:21.170 align:start position:0% output window it's a little bit slower 00:36:21.170 --> 00:36:22.760 align:start position:0% output window it's a little bit slower because 00:36:22.760 --> 00:36:22.770 align:start position:0% because 00:36:22.770 --> 00:36:24.650 align:start position:0% because but<00:36:23.010> it<00:36:23.130> will<00:36:23.190> eventually<00:36:23.310> push<00:36:24.270> this<00:36:24.450> stuff 00:36:24.650 --> 00:36:24.660 align:start position:0% but it will eventually push this stuff 00:36:24.660 --> 00:36:26.240 align:start position:0% but it will eventually push this stuff you<00:36:24.780> can<00:36:24.869> see<00:36:25.020> we<00:36:25.140> say<00:36:25.320> they're<00:36:25.530> going<00:36:25.830> up<00:36:25.980> here 00:36:26.240 --> 00:36:26.250 align:start position:0% you can see we say they're going up here 00:36:26.250 --> 00:36:28.520 align:start position:0% you can see we say they're going up here and<00:36:27.030> even<00:36:27.180> C<00:36:27.390> is<00:36:27.510> a<00:36:27.540> point<00:36:27.900> to<00:36:28.170> a<00:36:28.290> different 00:36:28.520 --> 00:36:28.530 align:start position:0% and even C is a point to a different 00:36:28.530 --> 00:36:31.010 align:start position:0% and even C is a point to a different network<00:36:28.830> here<00:36:29.359> and<00:36:30.359> eventually<00:36:30.720> that<00:36:30.900> will 00:36:31.010 --> 00:36:31.020 align:start position:0% network here and eventually that will 00:36:31.020 --> 00:36:34.130 align:start position:0% network here and eventually that will complete<00:36:31.970> so<00:36:32.970> just<00:36:33.330> make<00:36:33.480> it<00:36:33.570> super<00:36:33.839> easy<00:36:33.900> I 00:36:34.130 --> 00:36:34.140 align:start position:0% complete so just make it super easy I 00:36:34.140 --> 00:36:35.300 align:start position:0% complete so just make it super easy I don't<00:36:34.260> have<00:36:34.440> to<00:36:34.530> write<00:36:34.650> any<00:36:34.800> code<00:36:34.890> any 00:36:35.300 --> 00:36:35.310 align:start position:0% don't have to write any code any 00:36:35.310 --> 00:36:37.460 align:start position:0% don't have to write any code any migrations<00:36:36.089> and<00:36:36.390> I'm<00:36:36.690> able<00:36:36.839> to<00:36:36.990> live<00:36:37.200> employ 00:36:37.460 --> 00:36:37.470 align:start position:0% migrations and I'm able to live employ 00:36:37.470 --> 00:36:39.620 align:start position:0% migrations and I'm able to live employ it<00:36:37.530> directly<00:36:37.950> to<00:36:38.220> other<00:36:38.700> chains<00:36:39.030> you<00:36:39.450> think 00:36:39.620 --> 00:36:39.630 align:start position:0% it directly to other chains you think 00:36:39.630 --> 00:36:44.030 align:start position:0% it directly to other chains you think that's<00:36:39.780> pretty<00:36:39.900> cool<00:36:42.380> here<00:36:43.410> now<00:36:43.859> another 00:36:44.030 --> 00:36:44.040 align:start position:0% that's pretty cool here now another 00:36:44.040 --> 00:36:45.820 align:start position:0% that's pretty cool here now another thing<00:36:44.280> that's<00:36:44.490> while<00:36:45.060> that's<00:36:45.210> finishing<00:36:45.359> up 00:36:45.820 --> 00:36:45.830 align:start position:0% thing that's while that's finishing up 00:36:45.830 --> 00:36:48.109 align:start position:0% thing that's while that's finishing up on<00:36:46.830> this<00:36:46.950> menu 00:36:48.109 --> 00:36:48.119 align:start position:0% on this menu 00:36:48.119 --> 00:36:49.849 align:start position:0% on this menu a<00:36:48.150> couple<00:36:48.660> things<00:36:48.780> one<00:36:49.140> is<00:36:49.290> we<00:36:49.320> just<00:36:49.680> talked 00:36:49.849 --> 00:36:49.859 align:start position:0% a couple things one is we just talked 00:36:49.859 --> 00:36:51.950 align:start position:0% a couple things one is we just talked about<00:36:49.890> these<00:36:50.220> Falacci<00:36:50.460> gaps<00:36:50.820> so<00:36:51.510> this<00:36:51.630> bottom 00:36:51.950 --> 00:36:51.960 align:start position:0% about these Falacci gaps so this bottom 00:36:51.960 --> 00:36:54.380 align:start position:0% about these Falacci gaps so this bottom menu<00:36:52.230> section<00:36:52.650> here<00:36:52.859> is<00:36:53.220> basically<00:36:53.640> covering 00:36:54.380 --> 00:36:54.390 align:start position:0% menu section here is basically covering 00:36:54.390 --> 00:36:56.000 align:start position:0% menu section here is basically covering those<00:36:54.540> things<00:36:54.839> so<00:36:55.050> far<00:36:55.200> grapple<00:36:55.770> in<00:36:55.890> these 00:36:56.000 --> 00:36:56.010 align:start position:0% those things so far grapple in these 00:36:56.010 --> 00:36:56.660 align:start position:0% those things so far grapple in these contracts 00:36:56.660 --> 00:36:56.670 align:start position:0% contracts 00:36:56.670 --> 00:36:59.329 align:start position:0% contracts in<00:36:56.849> a<00:36:57.089> server<00:36:57.570> this<00:36:57.720> application<00:36:58.349> I<00:36:58.589> pick<00:36:59.220> this 00:36:59.329 --> 00:36:59.339 align:start position:0% in a server this application I pick this 00:36:59.339 --> 00:37:02.570 align:start position:0% in a server this application I pick this I<00:36:59.580> think<00:36:59.880> what<00:37:00.089> I<00:37:00.119> want<00:37:00.390> to<00:37:00.450> do<00:37:00.920> blow<00:37:01.920> up<00:37:02.160> at 00:37:02.570 --> 00:37:02.580 align:start position:0% I think what I want to do blow up at 00:37:02.580 --> 00:37:05.630 align:start position:0% I think what I want to do blow up at your<00:37:02.760> function<00:37:03.349> I'll<00:37:04.349> give<00:37:05.220> you<00:37:05.280> a<00:37:05.339> link<00:37:05.490> to 00:37:05.630 --> 00:37:05.640 align:start position:0% your function I'll give you a link to 00:37:05.640 --> 00:37:07.190 align:start position:0% your function I'll give you a link to the<00:37:05.730> documentation<00:37:06.210> you<00:37:06.510> can<00:37:06.570> look<00:37:06.780> at<00:37:06.930> how 00:37:07.190 --> 00:37:07.200 align:start position:0% the documentation you can look at how 00:37:07.200 --> 00:37:08.870 align:start position:0% the documentation you can look at how these<00:37:07.349> things<00:37:07.500> actually<00:37:07.680> work<00:37:07.920> we<00:37:08.580> would<00:37:08.730> put 00:37:08.870 --> 00:37:08.880 align:start position:0% these things actually work we would put 00:37:08.880 --> 00:37:12.260 align:start position:0% these things actually work we would put a<00:37:08.910> contract<00:37:09.270> address<00:37:09.780> really<00:37:10.200> so<00:37:11.210> don't<00:37:12.210> look 00:37:12.260 --> 00:37:12.270 align:start position:0% a contract address really so don't look 00:37:12.270 --> 00:37:13.730 align:start position:0% a contract address really so don't look like 00:37:13.730 --> 00:37:13.740 align:start position:0% like 00:37:13.740 --> 00:37:16.280 align:start position:0% like I'll<00:37:14.190> go<00:37:14.309> big<00:37:14.550> with<00:37:14.670> him<00:37:14.819> for<00:37:14.970> now 00:37:16.280 --> 00:37:16.290 align:start position:0% I'll go big with him for now 00:37:16.290 --> 00:37:20.920 align:start position:0% I'll go big with him for now and<00:37:16.590> it<00:37:16.800> basically<00:37:16.950> will<00:37:17.490> pick<00:37:17.720> because<00:37:18.720> it 00:37:20.920 --> 00:37:20.930 align:start position:0% and it basically will pick because it 00:37:20.930 --> 00:37:23.240 align:start position:0% and it basically will pick because it and<00:37:21.930> you<00:37:22.020> can<00:37:22.140> see<00:37:22.260> it<00:37:22.350> generate<00:37:22.740> a<00:37:22.770> logic 00:37:23.240 --> 00:37:23.250 align:start position:0% and you can see it generate a logic 00:37:23.250 --> 00:37:25.310 align:start position:0% and you can see it generate a logic addict<00:37:23.520> now<00:37:24.240> what's<00:37:24.420> that<00:37:24.540> mean<00:37:24.660> it<00:37:24.960> basically 00:37:25.310 --> 00:37:25.320 align:start position:0% addict now what's that mean it basically 00:37:25.320 --> 00:37:27.250 align:start position:0% addict now what's that mean it basically generated<00:37:25.890> a<00:37:25.950> bunch<00:37:26.040> of<00:37:26.220> JavaScript<00:37:26.520> for<00:37:26.880> me 00:37:27.250 --> 00:37:27.260 align:start position:0% generated a bunch of JavaScript for me 00:37:27.260 --> 00:37:29.570 align:start position:0% generated a bunch of JavaScript for me it<00:37:28.260> already<00:37:28.560> prefilled<00:37:28.980> everything<00:37:29.430> in 00:37:29.570 --> 00:37:29.580 align:start position:0% it already prefilled everything in 00:37:29.580 --> 00:37:31.670 align:start position:0% it already prefilled everything in forecast<00:37:30.030> but<00:37:30.480> basically<00:37:30.840> it<00:37:31.020> looked<00:37:31.470> at<00:37:31.590> all 00:37:31.670 --> 00:37:31.680 align:start position:0% forecast but basically it looked at all 00:37:31.680 --> 00:37:33.380 align:start position:0% forecast but basically it looked at all my<00:37:31.800> methods<00:37:31.980> looked<00:37:32.490> at<00:37:32.610> what<00:37:32.760> state<00:37:33.000> Berenice 00:37:33.380 --> 00:37:33.390 align:start position:0% my methods looked at what state Berenice 00:37:33.390 --> 00:37:35.210 align:start position:0% my methods looked at what state Berenice exist<00:37:33.750> stuff<00:37:33.930> and<00:37:34.140> they<00:37:34.650> created<00:37:34.890> a<00:37:34.980> wrapper 00:37:35.210 --> 00:37:35.220 align:start position:0% exist stuff and they created a wrapper 00:37:35.220 --> 00:37:37.370 align:start position:0% exist stuff and they created a wrapper for<00:37:35.490> that<00:37:35.670> and<00:37:36.360> basically<00:37:36.720> put<00:37:36.990> that<00:37:37.140> on<00:37:37.260> the 00:37:37.370 --> 00:37:37.380 align:start position:0% for that and basically put that on the 00:37:37.380 --> 00:37:39.230 align:start position:0% for that and basically put that on the jason<00:37:37.800> and<00:37:38.070> i<00:37:38.190> conversion<00:37:38.700> that<00:37:38.820> now<00:37:38.970> but<00:37:39.120> it 00:37:39.230 --> 00:37:39.240 align:start position:0% jason and i conversion that now but it 00:37:39.240 --> 00:37:40.520 align:start position:0% jason and i conversion that now but it in<00:37:39.360> my<00:37:39.450> source<00:37:39.660> control<00:37:40.020> engine<00:37:40.290> they<00:37:40.380> can 00:37:40.520 --> 00:37:40.530 align:start position:0% in my source control engine they can 00:37:40.530 --> 00:37:42.650 align:start position:0% in my source control engine they can take<00:37:40.680> that<00:37:40.830> up<00:37:41.010> to<00:37:41.130> Azure<00:37:41.250> and<00:37:41.760> it<00:37:42.090> will<00:37:42.270> fill 00:37:42.650 --> 00:37:42.660 align:start position:0% take that up to Azure and it will fill 00:37:42.660 --> 00:37:43.970 align:start position:0% take that up to Azure and it will fill what<00:37:42.960> David<00:37:43.260> showed<00:37:43.440> you<00:37:43.560> on<00:37:43.680> the<00:37:43.710> screen 00:37:43.970 --> 00:37:43.980 align:start position:0% what David showed you on the screen 00:37:43.980 --> 00:37:45.650 align:start position:0% what David showed you on the screen before<00:37:44.130> those<00:37:44.580> thank<00:37:44.940> you<00:37:45.060> we<00:37:45.180> don't<00:37:45.570> build 00:37:45.650 --> 00:37:45.660 align:start position:0% before those thank you we don't build 00:37:45.660 --> 00:37:48.200 align:start position:0% before those thank you we don't build that<00:37:45.840> automatically<00:37:46.440> for<00:37:46.680> you<00:37:46.910> so<00:37:47.910> makes<00:37:48.090> it 00:37:48.200 --> 00:37:48.210 align:start position:0% that automatically for you so makes it 00:37:48.210 --> 00:37:49.490 align:start position:0% that automatically for you so makes it super<00:37:48.450> easy<00:37:48.480> for<00:37:48.930> people<00:37:49.050> to<00:37:49.230> build 00:37:49.490 --> 00:37:49.500 align:start position:0% super easy for people to build 00:37:49.500 --> 00:37:51.980 align:start position:0% super easy for people to build applications<00:37:49.980> whether<00:37:50.640> be<00:37:50.850> event<00:37:51.180> based<00:37:51.420> or 00:37:51.980 --> 00:37:51.990 align:start position:0% applications whether be event based or 00:37:51.990 --> 00:37:54.320 align:start position:0% applications whether be event based or crud<00:37:52.470> like<00:37:52.860> I<00:37:52.950> want<00:37:53.130> to<00:37:53.190> read<00:37:53.790> or<00:37:54.030> create 00:37:54.320 --> 00:37:54.330 align:start position:0% crud like I want to read or create 00:37:54.330 --> 00:37:57.680 align:start position:0% crud like I want to read or create something<00:37:54.570> inside<00:37:55.050> there<00:37:56.360> so<00:37:57.360> the<00:37:57.570> other 00:37:57.680 --> 00:37:57.690 align:start position:0% something inside there so the other 00:37:57.690 --> 00:37:59.930 align:start position:0% something inside there so the other thing<00:37:58.130> then<00:37:59.130> immunity<00:37:59.550> you<00:37:59.640> might<00:37:59.820> have 00:37:59.930 --> 00:37:59.940 align:start position:0% thing then immunity you might have 00:37:59.940 --> 00:38:01.160 align:start position:0% thing then immunity you might have notice<00:38:00.240> whenever<00:38:00.510> I<00:38:00.660> was<00:38:00.810> going<00:38:01.020> through 00:38:01.160 --> 00:38:01.170 align:start position:0% notice whenever I was going through 00:38:01.170 --> 00:38:03.380 align:start position:0% notice whenever I was going through these<00:38:01.290> menus<00:38:01.650> really<00:38:01.800> fast<00:38:01.950> was<00:38:02.490> in<00:38:03.210> your 00:38:03.380 --> 00:38:03.390 align:start position:0% these menus really fast was in your 00:38:03.390 --> 00:38:04.910 align:start position:0% these menus really fast was in your contracts<00:38:03.870> one<00:38:04.110> of<00:38:04.170> the<00:38:04.260> things<00:38:04.440> people<00:38:04.620> want 00:38:04.910 --> 00:38:04.920 align:start position:0% contracts one of the things people want 00:38:04.920 --> 00:38:06.950 align:start position:0% contracts one of the things people want to<00:38:05.010> do<00:38:05.130> is<00:38:05.370> language<00:38:05.760> suck<00:38:06.510> this<00:38:06.690> stuff's 00:38:06.950 --> 00:38:06.960 align:start position:0% to do is language suck this stuff's 00:38:06.960 --> 00:38:13.130 align:start position:0% to do is language suck this stuff's already<00:38:07.140> consult<00:38:07.620> great<00:38:09.260> anybody<00:38:11.960> they<00:38:12.960> have 00:38:13.130 --> 00:38:13.140 align:start position:0% already consult great anybody they have 00:38:13.140 --> 00:38:14.810 align:start position:0% already consult great anybody they have a<00:38:13.170> pretty<00:38:13.380> nice<00:38:13.590> set<00:38:13.800> of<00:38:13.890> libraries<00:38:14.010> up<00:38:14.430> there 00:38:14.810 --> 00:38:14.820 align:start position:0% a pretty nice set of libraries up there 00:38:14.820 --> 00:38:16.610 align:start position:0% a pretty nice set of libraries up there that<00:38:15.270> people<00:38:15.540> typically<00:38:16.020> use<00:38:16.140> for<00:38:16.560> our 00:38:16.610 --> 00:38:16.620 align:start position:0% that people typically use for our 00:38:16.620 --> 00:38:18.470 align:start position:0% that people typically use for our production<00:38:16.860> applications<00:38:17.670> that<00:38:18.300> have<00:38:18.450> been 00:38:18.470 --> 00:38:18.480 align:start position:0% production applications that have been 00:38:18.480 --> 00:38:21.680 align:start position:0% production applications that have been fully<00:38:18.870> vetted<00:38:19.790> rock-solid<00:38:20.790> contracts<00:38:21.480> for 00:38:21.680 --> 00:38:21.690 align:start position:0% fully vetted rock-solid contracts for 00:38:21.690 --> 00:38:23.420 align:start position:0% fully vetted rock-solid contracts for different<00:38:21.990> things<00:38:22.140> and<00:38:22.830> so<00:38:22.950> we<00:38:23.040> said<00:38:23.220> how 00:38:23.420 --> 00:38:23.430 align:start position:0% different things and so we said how 00:38:23.430 --> 00:38:25.700 align:start position:0% different things and so we said how could<00:38:23.580> we<00:38:23.730> improve<00:38:23.820> that<00:38:24.330> experience<00:38:24.510> right 00:38:25.700 --> 00:38:25.710 align:start position:0% could we improve that experience right 00:38:25.710 --> 00:38:27.950 align:start position:0% could we improve that experience right so<00:38:26.070> the<00:38:26.700> typical<00:38:27.150> flow<00:38:27.330> we<00:38:27.540> saw<00:38:27.750> with 00:38:27.950 --> 00:38:27.960 align:start position:0% so the typical flow we saw with 00:38:27.960 --> 00:38:31.490 align:start position:0% so the typical flow we saw with enterprises<00:38:28.620> was<00:38:29.330> I'll<00:38:30.330> go<00:38:30.570> do<00:38:31.110> an<00:38:31.230> NPM 00:38:31.490 --> 00:38:31.500 align:start position:0% enterprises was I'll go do an NPM 00:38:31.500 --> 00:38:33.230 align:start position:0% enterprises was I'll go do an NPM package<00:38:31.920> go<00:38:32.160> ahead<00:38:32.340> and<00:38:32.460> pull<00:38:32.610> the<00:38:32.850> opens<00:38:33.120> up 00:38:33.230 --> 00:38:33.240 align:start position:0% package go ahead and pull the opens up 00:38:33.240 --> 00:38:35.900 align:start position:0% package go ahead and pull the opens up in<00:38:33.360> contracts<00:38:33.780> the<00:38:34.020> problem<00:38:34.470> is<00:38:34.620> that<00:38:35.580> we<00:38:35.670> saw 00:38:35.900 --> 00:38:35.910 align:start position:0% in contracts the problem is that we saw 00:38:35.910 --> 00:38:37.910 align:start position:0% in contracts the problem is that we saw with<00:38:36.150> some<00:38:36.300> of<00:38:36.390> the<00:38:36.450> customers<00:38:36.840> was<00:38:37.050> pulling 00:38:37.910 --> 00:38:37.920 align:start position:0% with some of the customers was pulling 00:38:37.920 --> 00:38:39.860 align:start position:0% with some of the customers was pulling down<00:38:37.950> everything<00:38:38.550> like<00:38:38.940> I<00:38:39.180> just<00:38:39.600> want<00:38:39.720> to<00:38:39.780> do<00:38:39.840> a 00:38:39.860 --> 00:38:39.870 align:start position:0% down everything like I just want to do a 00:38:39.870 --> 00:38:42.770 align:start position:0% down everything like I just want to do a TRC<00:38:40.290> 20<00:38:40.620> or<00:38:40.770> an<00:38:40.860> e<00:38:40.920> or<00:38:41.040> C<00:38:41.190> 721<00:38:41.880> all<00:38:42.450> right<00:38:42.540> see 00:38:42.770 --> 00:38:42.780 align:start position:0% TRC 20 or an e or C 721 all right see 00:38:42.780 --> 00:38:44.630 align:start position:0% TRC 20 or an e or C 721 all right see some<00:38:42.990> math<00:38:43.170> libraries<00:38:43.740> I<00:38:43.980> don't<00:38:44.400> need<00:38:44.580> all 00:38:44.630 --> 00:38:44.640 align:start position:0% some math libraries I don't need all 00:38:44.640 --> 00:38:45.950 align:start position:0% some math libraries I don't need all this<00:38:44.730> other<00:38:44.880> stuff<00:38:45.000> so<00:38:45.300> I<00:38:45.360> have<00:38:45.510> to<00:38:45.570> go<00:38:45.660> to<00:38:45.720> lead 00:38:45.950 --> 00:38:45.960 align:start position:0% this other stuff so I have to go to lead 00:38:45.960 --> 00:38:47.160 align:start position:0% this other stuff so I have to go to lead it<00:38:46.080> and<00:38:46.290> make<00:38:46.410> sure<00:38:46.530> no<00:38:46.650> one 00:38:47.160 --> 00:38:47.170 align:start position:0% it and make sure no one 00:38:47.170 --> 00:38:49.349 align:start position:0% it and make sure no one p.m.<00:38:47.470> installs<00:38:47.920> and<00:38:48.220> that<00:38:48.579> was<00:38:48.700> stuff<00:38:49.119> in<00:38:49.150> my 00:38:49.349 --> 00:38:49.359 align:start position:0% p.m. installs and that was stuff in my 00:38:49.359 --> 00:38:51.809 align:start position:0% p.m. installs and that was stuff in my directory<00:38:49.960> that<00:38:50.020> I<00:38:50.170> didn't<00:38:50.349> really<00:38:50.470> think<00:38:50.950> we 00:38:51.809 --> 00:38:51.819 align:start position:0% directory that I didn't really think we 00:38:51.819 --> 00:38:53.220 align:start position:0% directory that I didn't really think we were<00:38:51.880> talking<00:38:52.240> to<00:38:52.299> the<00:38:52.390> Zeppelin<00:38:52.869> guys<00:38:52.990> about 00:38:53.220 --> 00:38:53.230 align:start position:0% were talking to the Zeppelin guys about 00:38:53.230 --> 00:38:54.900 align:start position:0% were talking to the Zeppelin guys about was<00:38:53.470> could<00:38:53.770> we<00:38:53.799> create<00:38:54.010> like<00:38:54.280> categories 00:38:54.900 --> 00:38:54.910 align:start position:0% was could we create like categories 00:38:54.910 --> 00:38:56.730 align:start position:0% was could we create like categories similar<00:38:55.599> to<00:38:55.750> what<00:38:55.990> they<00:38:56.109> have<00:38:56.260> under<00:38:56.380> folder 00:38:56.730 --> 00:38:56.740 align:start position:0% similar to what they have under folder 00:38:56.740 --> 00:38:58.920 align:start position:0% similar to what they have under folder structure<00:38:57.130> that<00:38:57.760> selectively<00:38:58.359> allow<00:38:58.599> me<00:38:58.809> to 00:38:58.920 --> 00:38:58.930 align:start position:0% structure that selectively allow me to 00:38:58.930 --> 00:39:00.660 align:start position:0% structure that selectively allow me to do<00:38:59.020> pull<00:38:59.260> these<00:38:59.349> down<00:38:59.410> and<00:38:59.890> then<00:39:00.130> resolve<00:39:00.490> all 00:39:00.660 --> 00:39:00.670 align:start position:0% do pull these down and then resolve all 00:39:00.670 --> 00:39:02.700 align:start position:0% do pull these down and then resolve all the<00:39:00.790> dependencies<00:39:01.180> for<00:39:01.510> me<00:39:01.599> so<00:39:02.290> if<00:39:02.380> I<00:39:02.440> just 00:39:02.700 --> 00:39:02.710 align:start position:0% the dependencies for me so if I just 00:39:02.710 --> 00:39:04.829 align:start position:0% the dependencies for me so if I just want<00:39:02.890> the<00:39:03.040> mass<00:39:03.220> or<00:39:03.730> the<00:39:03.790> lifecycle<00:39:04.180> stuff<00:39:04.510> for 00:39:04.829 --> 00:39:04.839 align:start position:0% want the mass or the lifecycle stuff for 00:39:04.839 --> 00:39:07.650 align:start position:0% want the mass or the lifecycle stuff for me<00:39:04.990> access<00:39:05.740> to<00:39:05.770> stuff<00:39:06.280> I<00:39:06.640> can<00:39:07.000> pull<00:39:07.180> just<00:39:07.420> those 00:39:07.650 --> 00:39:07.660 align:start position:0% me access to stuff I can pull just those 00:39:07.660 --> 00:39:10.319 align:start position:0% me access to stuff I can pull just those I'll<00:39:08.589> show<00:39:08.740> you<00:39:08.829> what<00:39:08.950> it<00:39:09.010> looks<00:39:09.130> like<00:39:09.250> in<00:39:10.119> here 00:39:10.319 --> 00:39:10.329 align:start position:0% I'll show you what it looks like in here 00:39:10.329 --> 00:39:12.599 align:start position:0% I'll show you what it looks like in here so<00:39:11.170> what<00:39:11.349> this<00:39:11.470> is<00:39:11.650> actually<00:39:11.799> doing<00:39:12.010> is<00:39:12.369> going 00:39:12.599 --> 00:39:12.609 align:start position:0% so what this is actually doing is going 00:39:12.609 --> 00:39:15.690 align:start position:0% so what this is actually doing is going and<00:39:13.000> grabbing<00:39:13.210> a<00:39:13.630> specific<00:39:14.290> version<00:39:14.500> of<00:39:15.369> the 00:39:15.690 --> 00:39:15.700 align:start position:0% and grabbing a specific version of the 00:39:15.700 --> 00:39:18.030 align:start position:0% and grabbing a specific version of the open<00:39:16.299> some<00:39:16.450> blood<00:39:16.599> contracts<00:39:17.079> and<00:39:17.349> it<00:39:17.859> pulled 00:39:18.030 --> 00:39:18.040 align:start position:0% open some blood contracts and it pulled 00:39:18.040 --> 00:39:19.829 align:start position:0% open some blood contracts and it pulled down<00:39:18.099> 15<00:39:18.549> files<00:39:18.790> in<00:39:18.970> this<00:39:19.089> case<00:39:19.150> and<00:39:19.569> I'll<00:39:19.660> show 00:39:19.829 --> 00:39:19.839 align:start position:0% down 15 files in this case and I'll show 00:39:19.839 --> 00:39:21.240 align:start position:0% down 15 files in this case and I'll show you<00:39:19.869> what<00:39:20.049> they<00:39:20.140> look<00:39:20.170> like<00:39:20.380> but<00:39:21.040> it<00:39:21.130> also 00:39:21.240 --> 00:39:21.250 align:start position:0% you what they look like but it also 00:39:21.250 --> 00:39:22.920 align:start position:0% you what they look like but it also gives<00:39:21.520> me<00:39:21.670> this<00:39:21.910> little<00:39:22.059> more<00:39:22.390> detail<00:39:22.720> so<00:39:22.839> you 00:39:22.920 --> 00:39:22.930 align:start position:0% gives me this little more detail so you 00:39:22.930 --> 00:39:24.990 align:start position:0% gives me this little more detail so you can<00:39:23.020> click<00:39:23.619> one<00:39:23.829> and<00:39:24.220> this<00:39:24.579> will<00:39:24.730> take<00:39:24.849> me 00:39:24.990 --> 00:39:25.000 align:start position:0% can click one and this will take me 00:39:25.000 --> 00:39:27.240 align:start position:0% can click one and this will take me directly<00:39:25.150> to<00:39:25.510> this<00:39:25.839> rich<00:39:26.079> documentation<00:39:26.859> so 00:39:27.240 --> 00:39:27.250 align:start position:0% directly to this rich documentation so 00:39:27.250 --> 00:39:29.130 align:start position:0% directly to this rich documentation so if<00:39:27.369> I'm<00:39:27.520> new<00:39:27.730> to<00:39:27.760> here<00:39:28.210> see<00:39:28.390> a<00:39:28.420> plan<00:39:28.720> of<00:39:29.020> what 00:39:29.130 --> 00:39:29.140 align:start position:0% if I'm new to here see a plan of what 00:39:29.140 --> 00:39:31.200 align:start position:0% if I'm new to here see a plan of what I'm<00:39:29.260> doing<00:39:29.500> I<00:39:29.950> can<00:39:30.369> come<00:39:30.609> up<00:39:30.640> here<00:39:30.880> this<00:39:31.030> will 00:39:31.200 --> 00:39:31.210 align:start position:0% I'm doing I can come up here this will 00:39:31.210 --> 00:39:32.609 align:start position:0% I'm doing I can come up here this will walk<00:39:31.390> me<00:39:31.420> through<00:39:31.869> everything<00:39:32.230> I<00:39:32.440> need<00:39:32.589> to 00:39:32.609 --> 00:39:32.619 align:start position:0% walk me through everything I need to 00:39:32.619 --> 00:39:34.530 align:start position:0% walk me through everything I need to know<00:39:32.710> about<00:39:32.950> what<00:39:33.250> I'm<00:39:33.339> doing<00:39:33.369> with<00:39:33.640> that<00:39:33.940> a 00:39:34.530 --> 00:39:34.540 align:start position:0% know about what I'm doing with that a 00:39:34.540 --> 00:39:35.940 align:start position:0% know about what I'm doing with that a couple<00:39:34.599> other<00:39:35.500> things<00:39:35.530> that<00:39:35.829> were<00:39:35.920> doing 00:39:35.940 --> 00:39:35.950 align:start position:0% couple other things that were doing 00:39:35.950 --> 00:39:38.130 align:start position:0% couple other things that were doing there<00:39:36.400> as<00:39:36.609> you<00:39:36.940> see<00:39:37.089> it<00:39:37.210> down<00:39:37.420> little<00:39:37.599> contract 00:39:38.130 --> 00:39:38.140 align:start position:0% there as you see it down little contract 00:39:38.140 --> 00:39:40.109 align:start position:0% there as you see it down little contract immediately<00:39:38.490> it<00:39:39.490> resolved<00:39:39.970> all<00:39:40.089> the 00:39:40.109 --> 00:39:40.119 align:start position:0% immediately it resolved all the 00:39:40.119 --> 00:39:41.609 align:start position:0% immediately it resolved all the dependencies<00:39:40.720> for<00:39:41.020> these<00:39:41.170> things<00:39:41.380> so 00:39:41.609 --> 00:39:41.619 align:start position:0% dependencies for these things so 00:39:41.619 --> 00:39:43.440 align:start position:0% dependencies for these things so anything<00:39:42.250> that's<00:39:42.400> you<00:39:43.059> know<00:39:43.150> these<00:39:43.270> things 00:39:43.440 --> 00:39:43.450 align:start position:0% anything that's you know these things 00:39:43.450 --> 00:39:45.000 align:start position:0% anything that's you know these things have<00:39:43.780> multiple<00:39:44.290> dependency 00:39:45.000 --> 00:39:45.010 align:start position:0% have multiple dependency 00:39:45.010 --> 00:39:47.160 align:start position:0% have multiple dependency to<00:39:45.340> each<00:39:45.520> one<00:39:45.730> of<00:39:45.850> these<00:39:45.970> so<00:39:46.750> that's<00:39:46.870> happening 00:39:47.160 --> 00:39:47.170 align:start position:0% to each one of these so that's happening 00:39:47.170 --> 00:39:49.200 align:start position:0% to each one of these so that's happening automatically<00:39:47.950> it's<00:39:48.610> also<00:39:48.730> making<00:39:48.970> them 00:39:49.200 --> 00:39:49.210 align:start position:0% automatically it's also making them 00:39:49.210 --> 00:39:51.150 align:start position:0% automatically it's also making them read-only<00:39:49.390> so<00:39:50.140> one<00:39:50.290> of<00:39:50.320> the<00:39:50.410> things<00:39:50.560> and<00:39:50.860> in 00:39:51.150 --> 00:39:51.160 align:start position:0% read-only so one of the things and in 00:39:51.160 --> 00:39:53.130 align:start position:0% read-only so one of the things and in talking<00:39:51.370> with<00:39:51.520> open<00:39:51.820> Zeppelin<00:39:52.150> was<00:39:52.330> you<00:39:53.050> know 00:39:53.130 --> 00:39:53.140 align:start position:0% talking with open Zeppelin was you know 00:39:53.140 --> 00:39:54.690 align:start position:0% talking with open Zeppelin was you know sometimes<00:39:53.590> people<00:39:53.770> in<00:39:54.040> inverted<00:39:54.430> leave<00:39:54.550> make 00:39:54.690 --> 00:39:54.700 align:start position:0% sometimes people in inverted leave make 00:39:54.700 --> 00:39:56.190 align:start position:0% sometimes people in inverted leave make changes<00:39:55.030> to<00:39:55.210> these<00:39:55.300> thing<00:39:55.540> and<00:39:55.780> then<00:39:56.170> that 00:39:56.190 --> 00:39:56.200 align:start position:0% changes to these thing and then that 00:39:56.200 --> 00:39:57.450 align:start position:0% changes to these thing and then that you're<00:39:56.410> going<00:39:56.530> to<00:39:56.590> introduce<00:39:56.770> a<00:39:57.070> security 00:39:57.450 --> 00:39:57.460 align:start position:0% you're going to introduce a security 00:39:57.460 --> 00:40:00.450 align:start position:0% you're going to introduce a security problem<00:39:57.670> and<00:39:58.000> that's<00:39:58.180> not<00:39:58.360> good<00:39:58.600> and<00:39:58.950> so<00:39:59.950> said 00:40:00.450 --> 00:40:00.460 align:start position:0% problem and that's not good and so said 00:40:00.460 --> 00:40:01.740 align:start position:0% problem and that's not good and so said well<00:40:00.670> first<00:40:00.910> off<00:40:01.090> we<00:40:01.120> could<00:40:01.270> make<00:40:01.390> read-only 00:40:01.740 --> 00:40:01.750 align:start position:0% well first off we could make read-only 00:40:01.750 --> 00:40:03.690 align:start position:0% well first off we could make read-only but<00:40:02.650> that's<00:40:02.800> not<00:40:02.950> good<00:40:03.070> enough<00:40:03.100> right<00:40:03.460> because 00:40:03.690 --> 00:40:03.700 align:start position:0% but that's not good enough right because 00:40:03.700 --> 00:40:04.680 align:start position:0% but that's not good enough right because somebody<00:40:03.940> could<00:40:04.060> just<00:40:04.210> make<00:40:04.420> them<00:40:04.540> not 00:40:04.680 --> 00:40:04.690 align:start position:0% somebody could just make them not 00:40:04.690 --> 00:40:07.350 align:start position:0% somebody could just make them not revealed<00:40:04.960> so<00:40:05.740> what<00:40:06.070> we<00:40:06.190> did<00:40:06.310> is<00:40:06.550> look<00:40:07.090> at<00:40:07.210> the 00:40:07.350 --> 00:40:07.360 align:start position:0% revealed so what we did is look at the 00:40:07.360 --> 00:40:09.720 align:start position:0% revealed so what we did is look at the actual<00:40:07.810> commit<00:40:08.140> hash<00:40:08.320> and<00:40:08.620> at<00:40:09.100> the<00:40:09.250> final 00:40:09.720 --> 00:40:09.730 align:start position:0% actual commit hash and at the final 00:40:09.730 --> 00:40:11.700 align:start position:0% actual commit hash and at the final match<00:40:09.940> up<00:40:10.120> and<00:40:10.240> get<00:40:10.360> up<00:40:10.480> and<00:40:11.140> so<00:40:11.290> we<00:40:11.380> know<00:40:11.500> for 00:40:11.700 --> 00:40:11.710 align:start position:0% match up and get up and so we know for 00:40:11.710 --> 00:40:13.560 align:start position:0% match up and get up and so we know for sure<00:40:11.740> so<00:40:11.920> when<00:40:12.400> we<00:40:12.520> do<00:40:12.640> it<00:40:12.760> limit<00:40:13.180> we<00:40:13.300> actually 00:40:13.560 --> 00:40:13.570 align:start position:0% sure so when we do it limit we actually 00:40:13.570 --> 00:40:15.240 align:start position:0% sure so when we do it limit we actually check<00:40:13.780> that<00:40:13.810> instead<00:40:14.590> like<00:40:14.770> every<00:40:15.100> time 00:40:15.240 --> 00:40:15.250 align:start position:0% check that instead like every time 00:40:15.250 --> 00:40:17.070 align:start position:0% check that instead like every time somebody<00:40:15.580> doesn't<00:40:15.760> want<00:40:16.090> to<00:40:16.240> wear<00:40:16.570> this<00:40:16.780> we 00:40:17.070 --> 00:40:17.080 align:start position:0% somebody doesn't want to wear this we 00:40:17.080 --> 00:40:18.450 align:start position:0% somebody doesn't want to wear this we actually<00:40:17.200> walk<00:40:17.620> it<00:40:17.800> right<00:40:17.830> now<00:40:18.100> and<00:40:18.280> say 00:40:18.450 --> 00:40:18.460 align:start position:0% actually walk it right now and say 00:40:18.460 --> 00:40:20.340 align:start position:0% actually walk it right now and say someone<00:40:19.450> changed<00:40:19.720> one<00:40:19.840> of<00:40:19.870> the<00:40:19.960> core 00:40:20.340 --> 00:40:20.350 align:start position:0% someone changed one of the core 00:40:20.350 --> 00:40:21.600 align:start position:0% someone changed one of the core contracts<00:40:20.800> right<00:40:20.950> here<00:40:21.160> is<00:40:21.250> the<00:40:21.340> one<00:40:21.460> that 00:40:21.600 --> 00:40:21.610 align:start position:0% contracts right here is the one that 00:40:21.610 --> 00:40:26.180 align:start position:0% contracts right here is the one that they<00:40:21.730> changed<00:40:22.060> go<00:40:22.600> fix<00:40:22.810> it<00:40:24.870> thinking<00:40:25.870> about 00:40:26.180 --> 00:40:26.190 align:start position:0% they changed go fix it thinking about 00:40:26.190 --> 00:40:29.700 align:start position:0% they changed go fix it thinking about tweak<00:40:27.190> that<00:40:27.370> but<00:40:27.670> the<00:40:28.180> mockolate<00:40:28.510> of<00:40:29.080> linear 00:40:29.700 --> 00:40:29.710 align:start position:0% tweak that but the mockolate of linear 00:40:29.710 --> 00:40:31.290 align:start position:0% tweak that but the mockolate of linear shared<00:40:29.980> is<00:40:30.190> really<00:40:30.430> good<00:40:30.610> that<00:40:30.880> she's<00:40:31.030> using 00:40:31.290 --> 00:40:31.300 align:start position:0% shared is really good that she's using 00:40:31.300 --> 00:40:33.060 align:start position:0% shared is really good that she's using parents<00:40:31.840> as<00:40:32.020> opposed<00:40:32.410> to<00:40:32.530> changing<00:40:32.770> those 00:40:33.060 --> 00:40:33.070 align:start position:0% parents as opposed to changing those 00:40:33.070 --> 00:40:35.190 align:start position:0% parents as opposed to changing those core<00:40:33.280> contracts<00:40:33.790> and<00:40:34.090> so<00:40:34.570> we<00:40:34.720> want<00:40:34.900> to<00:40:34.960> kind<00:40:35.080> of 00:40:35.190 --> 00:40:35.200 align:start position:0% core contracts and so we want to kind of 00:40:35.200 --> 00:40:36.660 align:start position:0% core contracts and so we want to kind of make<00:40:35.410> a<00:40:35.440> firm<00:40:35.890> stance<00:40:36.220> there<00:40:36.430> to<00:40:36.520> make<00:40:36.640> sure 00:40:36.660 --> 00:40:36.670 align:start position:0% make a firm stance there to make sure 00:40:36.670 --> 00:40:38.910 align:start position:0% make a firm stance there to make sure people<00:40:36.910> don't<00:40:37.090> pull<00:40:37.930> over<00:40:37.990> leg<00:40:38.260> off<00:40:38.440> you<00:40:38.800> know 00:40:38.910 --> 00:40:38.920 align:start position:0% people don't pull over leg off you know 00:40:38.920 --> 00:40:41.250 align:start position:0% people don't pull over leg off you know with<00:40:39.070> this<00:40:39.190> kind<00:40:39.250> of<00:40:39.460> stuff<00:40:39.640> so<00:40:40.260> basically 00:40:41.250 --> 00:40:41.260 align:start position:0% with this kind of stuff so basically 00:40:41.260 --> 00:40:42.270 align:start position:0% with this kind of stuff so basically this<00:40:41.470> will<00:40:41.620> automatically<00:40:42.100> do<00:40:42.250> a 00:40:42.270 --> 00:40:42.280 align:start position:0% this will automatically do a 00:40:42.280 --> 00:40:43.620 align:start position:0% this will automatically do a verification<00:40:42.490> check<00:40:43.030> now<00:40:43.180> every<00:40:43.390> time<00:40:43.510> they 00:40:43.620 --> 00:40:43.630 align:start position:0% verification check now every time they 00:40:43.630 --> 00:40:45.510 align:start position:0% verification check now every time they do<00:40:43.750> an<00:40:43.840> employment<00:40:44.290> make<00:40:44.980> sure<00:40:45.100> that<00:40:45.220> don't 00:40:45.510 --> 00:40:45.520 align:start position:0% do an employment make sure that don't 00:40:45.520 --> 00:40:47.010 align:start position:0% do an employment make sure that don't change<00:40:45.640> season<00:40:46.090> and<00:40:46.270> I<00:40:46.330> can<00:40:46.480> started<00:40:46.780> studying 00:40:47.010 --> 00:40:47.020 align:start position:0% change season and I can started studying 00:40:47.020 --> 00:40:49.740 align:start position:0% change season and I can started studying that<00:40:47.290> it<00:40:48.010> also<00:40:48.220> created<00:40:49.060> the<00:40:49.120> migration<00:40:49.570> for 00:40:49.740 --> 00:40:49.750 align:start position:0% that it also created the migration for 00:40:49.750 --> 00:40:51.900 align:start position:0% that it also created the migration for me<00:40:49.840> this<00:40:50.800> kind<00:40:51.040> of<00:40:51.070> cool<00:40:51.250> to<00:40:51.400> it<00:40:51.520> like<00:40:51.640> we<00:40:51.670> went 00:40:51.900 --> 00:40:51.910 align:start position:0% me this kind of cool to it like we went 00:40:51.910 --> 00:40:53.130 align:start position:0% me this kind of cool to it like we went looked<00:40:52.300> at<00:40:52.450> when<00:40:52.570> all<00:40:52.690> the<00:40:52.780> dependencies 00:40:53.130 --> 00:40:53.140 align:start position:0% looked at when all the dependencies 00:40:53.140 --> 00:40:55.260 align:start position:0% looked at when all the dependencies aren't<00:40:53.530> built<00:40:53.710> in<00:40:53.890> the<00:40:54.070> KT<00:40:54.340> migration<00:40:55.090> file 00:40:55.260 --> 00:40:55.270 align:start position:0% aren't built in the KT migration file 00:40:55.270 --> 00:40:57.780 align:start position:0% aren't built in the KT migration file for<00:40:55.540> you<00:40:55.690> so<00:40:56.050> again<00:40:56.380> you<00:40:57.340> don't<00:40:57.400> have<00:40:57.490> to<00:40:57.610> write 00:40:57.780 --> 00:40:57.790 align:start position:0% for you so again you don't have to write 00:40:57.790 --> 00:40:59.640 align:start position:0% for you so again you don't have to write any<00:40:57.940> code<00:40:58.030> if<00:40:58.420> you<00:40:58.570> just<00:40:58.750> downloaded<00:40:59.110> a<00:40:59.230> T<00:40:59.380> or<00:40:59.530> C 00:40:59.640 --> 00:40:59.650 align:start position:0% any code if you just downloaded a T or C 00:40:59.650 --> 00:41:01.470 align:start position:0% any code if you just downloaded a T or C 20<00:41:00.010> and<00:41:00.130> hit<00:41:00.280> go<00:41:00.430> it<00:41:00.880> will<00:41:01.090> take<00:41:01.240> care<00:41:01.360> of 00:41:01.470 --> 00:41:01.480 align:start position:0% 20 and hit go it will take care of 00:41:01.480 --> 00:41:04.260 align:start position:0% 20 and hit go it will take care of everything<00:41:01.690> and<00:41:01.990> migrate<00:41:02.380> it<00:41:02.500> for<00:41:02.710> you<00:41:03.270> I'll 00:41:04.260 --> 00:41:04.270 align:start position:0% everything and migrate it for you I'll 00:41:04.270 --> 00:41:05.820 align:start position:0% everything and migrate it for you I'll just<00:41:04.480> be<00:41:04.600> totally<00:41:05.050> honest<00:41:05.350> there's<00:41:05.560> a<00:41:05.620> couple 00:41:05.820 --> 00:41:05.830 align:start position:0% just be totally honest there's a couple 00:41:05.830 --> 00:41:08.310 align:start position:0% just be totally honest there's a couple breaks<00:41:06.160> in<00:41:06.340> this<00:41:06.460> as<00:41:06.640> a<00:41:06.670> brand<00:41:06.940> oh<00:41:07.090> and<00:41:07.780> some<00:41:08.290> of 00:41:08.310 --> 00:41:08.320 align:start position:0% breaks in this as a brand oh and some of 00:41:08.320 --> 00:41:09.750 align:start position:0% breaks in this as a brand oh and some of those<00:41:08.440> are<00:41:08.500> around<00:41:08.920> like<00:41:09.220> some<00:41:09.580> of<00:41:09.700> the 00:41:09.750 --> 00:41:09.760 align:start position:0% those are around like some of the 00:41:09.760 --> 00:41:11.370 align:start position:0% those are around like some of the contracts<00:41:10.180> actually<00:41:10.570> need<00:41:10.780> parameters<00:41:11.230> to 00:41:11.370 --> 00:41:11.380 align:start position:0% contracts actually need parameters to 00:41:11.380 --> 00:41:12.870 align:start position:0% contracts actually need parameters to initialize<00:41:11.830> themself<00:41:12.190> like<00:41:12.520> I<00:41:12.550> didn't<00:41:12.850> a 00:41:12.870 --> 00:41:12.880 align:start position:0% initialize themself like I didn't a 00:41:12.880 --> 00:41:14.640 align:start position:0% initialize themself like I didn't a constructor<00:41:13.330> or<00:41:13.480> something<00:41:13.780> and<00:41:14.350> so<00:41:14.500> we're 00:41:14.640 --> 00:41:14.650 align:start position:0% constructor or something and so we're 00:41:14.650 --> 00:41:16.170 align:start position:0% constructor or something and so we're thinking<00:41:15.070> about<00:41:15.130> a<00:41:15.310> better<00:41:15.670> experience<00:41:15.970> for 00:41:16.170 --> 00:41:16.180 align:start position:0% thinking about a better experience for 00:41:16.180 --> 00:41:17.850 align:start position:0% thinking about a better experience for that<00:41:16.390> happy<00:41:16.720> to<00:41:16.810> hear<00:41:17.020> feedback<00:41:17.290> from<00:41:17.620> anyone 00:41:17.850 --> 00:41:17.860 align:start position:0% that happy to hear feedback from anyone 00:41:17.860 --> 00:41:19.620 align:start position:0% that happy to hear feedback from anyone here<00:41:18.100> too<00:41:18.310> but<00:41:18.580> we're<00:41:19.090> thinking<00:41:19.270> about 00:41:19.620 --> 00:41:19.630 align:start position:0% here too but we're thinking about 00:41:19.630 --> 00:41:21.450 align:start position:0% here too but we're thinking about integrating<00:41:19.900> that<00:41:20.320> as<00:41:20.500> well<00:41:20.680> to<00:41:20.860> say<00:41:21.040> hey<00:41:21.220> in 00:41:21.450 --> 00:41:21.460 align:start position:0% integrating that as well to say hey in 00:41:21.460 --> 00:41:23.250 align:start position:0% integrating that as well to say hey in order<00:41:22.000> to<00:41:22.090> using<00:41:22.360> air<00:41:22.480> C<00:41:22.630> 20<00:41:22.900> I<00:41:22.930> need<00:41:23.110> to<00:41:23.170> know 00:41:23.250 --> 00:41:23.260 align:start position:0% order to using air C 20 I need to know 00:41:23.260 --> 00:41:24.390 align:start position:0% order to using air C 20 I need to know what<00:41:23.410> you<00:41:23.500> want<00:41:23.650> to<00:41:23.710> name<00:41:23.830> it<00:41:23.860> or<00:41:24.160> what<00:41:24.280> the 00:41:24.390 --> 00:41:24.400 align:start position:0% what you want to name it or what the 00:41:24.400 --> 00:41:26.220 align:start position:0% what you want to name it or what the supply<00:41:24.700> is<00:41:24.760> or<00:41:25.060> something<00:41:25.300> like<00:41:25.420> that<00:41:25.630> then<00:41:26.200> we 00:41:26.220 --> 00:41:26.230 align:start position:0% supply is or something like that then we 00:41:26.230 --> 00:41:27.960 align:start position:0% supply is or something like that then we can<00:41:26.500> prompt<00:41:26.770> them<00:41:26.920> for<00:41:27.130> that<00:41:27.280> and<00:41:27.550> then<00:41:27.850> do<00:41:27.940> it 00:41:27.960 --> 00:41:27.970 align:start position:0% can prompt them for that and then do it 00:41:27.970 --> 00:41:28.540 align:start position:0% can prompt them for that and then do it for<00:41:28.090> them 00:41:28.540 --> 00:41:28.550 align:start position:0% for them 00:41:28.550 --> 00:41:30.490 align:start position:0% for them they<00:41:28.820> don't<00:41:29.000> have<00:41:29.120> to<00:41:29.240> dig<00:41:29.450> around<00:41:29.500> inside 00:41:30.490 --> 00:41:30.500 align:start position:0% they don't have to dig around inside 00:41:30.500 --> 00:41:35.320 align:start position:0% they don't have to dig around inside these<00:41:30.650> contractors<00:41:32.440> and<00:41:33.440> so<00:41:33.830> I<00:41:34.280> think<00:41:35.030> that's 00:41:35.320 --> 00:41:35.330 align:start position:0% these contractors and so I think that's 00:41:35.330 --> 00:41:37.420 align:start position:0% these contractors and so I think that's pretty<00:41:35.960> much<00:41:36.080> all<00:41:36.290> in<00:41:36.530> the<00:41:36.650> show<00:41:36.800> I'm<00:41:37.010> happy 00:41:37.420 --> 00:41:37.430 align:start position:0% pretty much all in the show I'm happy 00:41:37.430 --> 00:41:38.800 align:start position:0% pretty much all in the show I'm happy that<00:41:37.460> afterwards<00:41:38.120> we<00:41:38.330> can<00:41:38.450> talk<00:41:38.630> through 00:41:38.800 --> 00:41:38.810 align:start position:0% that afterwards we can talk through 00:41:38.810 --> 00:41:40.690 align:start position:0% that afterwards we can talk through anything<00:41:39.140> here<00:41:39.500> and<00:41:39.770> I'm<00:41:40.100> happy<00:41:40.400> to<00:41:40.430> talk 00:41:40.690 --> 00:41:40.700 align:start position:0% anything here and I'm happy to talk 00:41:40.700 --> 00:41:42.760 align:start position:0% anything here and I'm happy to talk about<00:41:40.760> the<00:41:41.150> eternal<00:41:41.480> darkness<00:41:41.780> ugh<00:41:42.350> how<00:41:42.710> it 00:41:42.760 --> 00:41:42.770 align:start position:0% about the eternal darkness ugh how it 00:41:42.770 --> 00:41:43.920 align:start position:0% about the eternal darkness ugh how it works 00:41:43.920 --> 00:41:43.930 align:start position:0% works 00:41:43.930 --> 00:41:46.120 align:start position:0% works like<00:41:44.930> the<00:41:45.140> new<00:41:45.260> stuffs<00:41:45.500> coming<00:41:45.740> live<00:41:45.920> this 00:41:46.120 --> 00:41:46.130 align:start position:0% like the new stuffs coming live this 00:41:46.130 --> 00:41:49.240 align:start position:0% like the new stuffs coming live this week<00:41:46.390> so<00:41:47.390> actually<00:41:48.200> in<00:41:48.380> process<00:41:48.650> right<00:41:48.890> now<00:41:49.040> if 00:41:49.240 --> 00:41:49.250 align:start position:0% week so actually in process right now if 00:41:49.250 --> 00:41:51.490 align:start position:0% week so actually in process right now if it<00:41:49.400> is<00:41:49.550> publish<00:41:49.940> and<00:41:50.540> this<00:41:50.690> will<00:41:50.870> happens<00:41:51.350> that 00:41:51.490 --> 00:41:51.500 align:start position:0% it is publish and this will happens that 00:41:51.500 --> 00:41:52.330 align:start position:0% it is publish and this will happens that one<00:41:51.650> stuff<00:41:51.890> in<00:41:52.070> it 00:41:52.330 --> 00:41:52.340 align:start position:0% one stuff in it 00:41:52.340 --> 00:41:55.810 align:start position:0% one stuff in it as<00:41:52.550> well<00:41:52.790> as<00:41:52.910> the<00:41:53.060> carousel<00:41:54.580> and<00:41:55.580> this 00:41:55.810 --> 00:41:55.820 align:start position:0% as well as the carousel and this 00:41:55.820 --> 00:42:00.330 align:start position:0% as well as the carousel and this ascension<00:41:56.150> works<00:41:56.480> on<00:41:56.870> Windows<00:41:57.770> Mac<00:41:58.220> Linux 00:42:00.330 --> 00:42:00.340 align:start position:0% ascension works on Windows Mac Linux 00:42:00.340 --> 00:42:13.390 align:start position:0% ascension works on Windows Mac Linux yeah<00:42:01.340> those<00:42:01.730> three 00:42:13.390 --> 00:42:13.400 align:start position:0% 00:42:13.400 --> 00:42:15.370 align:start position:0% so<00:42:14.000> that's<00:42:14.210> something<00:42:14.360> important<00:42:14.990> when<00:42:15.350> I 00:42:15.370 --> 00:42:15.380 align:start position:0% so that's something important when I 00:42:15.380 --> 00:42:16.960 align:start position:0% so that's something important when I feel<00:42:15.650> at<00:42:15.740> work<00:42:15.920> for<00:42:16.100> these<00:42:16.220> toughness<00:42:16.790> Oh 00:42:16.960 --> 00:42:16.970 align:start position:0% feel at work for these toughness Oh 00:42:16.970 --> 00:42:19.150 align:start position:0% feel at work for these toughness Oh usually<00:42:17.210> have<00:42:17.570> a<00:42:17.600> bunch<00:42:17.930> of<00:42:18.140> half<00:42:18.680> of<00:42:18.860> this<00:42:18.980> in 00:42:19.150 --> 00:42:19.160 align:start position:0% usually have a bunch of half of this in 00:42:19.160 --> 00:42:21.400 align:start position:0% usually have a bunch of half of this in the<00:42:19.250> room<00:42:19.430> we'll<00:42:19.820> have<00:42:19.850> those<00:42:20.660> laptop<00:42:21.080> and<00:42:21.380> a 00:42:21.400 --> 00:42:21.410 align:start position:0% the room we'll have those laptop and a 00:42:21.410 --> 00:42:23.500 align:start position:0% the room we'll have those laptop and a half<00:42:21.590> we'll<00:42:21.800> have<00:42:21.980> Mac<00:42:22.250> laptops<00:42:22.730> so<00:42:23.330> being 00:42:23.500 --> 00:42:23.510 align:start position:0% half we'll have Mac laptops so being 00:42:23.510 --> 00:42:25.450 align:start position:0% half we'll have Mac laptops so being able<00:42:23.570> to<00:42:23.750> have<00:42:24.200> everyone<00:42:24.590> using<00:42:25.040> the<00:42:25.160> exact 00:42:25.450 --> 00:42:25.460 align:start position:0% able to have everyone using the exact 00:42:25.460 --> 00:42:27.070 align:start position:0% able to have everyone using the exact same<00:42:25.520> visual<00:42:25.910> studio<00:42:26.210> code<00:42:26.480> tooling<00:42:26.930> with 00:42:27.070 --> 00:42:27.080 align:start position:0% same visual studio code tooling with 00:42:27.080 --> 00:42:29.080 align:start position:0% same visual studio code tooling with these<00:42:27.200> same<00:42:27.500> extension<00:42:28.100> makes<00:42:28.670> it<00:42:28.820> easy<00:42:28.940> for 00:42:29.080 --> 00:42:29.090 align:start position:0% these same extension makes it easy for 00:42:29.090 --> 00:42:35.140 align:start position:0% these same extension makes it easy for all<00:42:29.510> the<00:42:29.660> devs<00:42:29.900> to<00:42:30.200> have<00:42:31.040> the<00:42:31.160> same<00:42:33.340> so<00:42:34.340> beyond 00:42:35.140 --> 00:42:35.150 align:start position:0% all the devs to have the same so beyond 00:42:35.150 --> 00:42:37.120 align:start position:0% all the devs to have the same so beyond just<00:42:35.210> like<00:42:35.600> scaffolding<00:42:36.350> stuff<00:42:36.890> that<00:42:37.040> we<00:42:37.100> put 00:42:37.120 --> 00:42:37.130 align:start position:0% just like scaffolding stuff that we put 00:42:37.130 --> 00:42:39.130 align:start position:0% just like scaffolding stuff that we put up<00:42:37.340> here<00:42:37.520> today<00:42:37.700> there's<00:42:38.150> also<00:42:38.300> this<00:42:38.900> thing 00:42:39.130 --> 00:42:39.140 align:start position:0% up here today there's also this thing 00:42:39.140 --> 00:42:40.360 align:start position:0% up here today there's also this thing and<00:42:39.500> people<00:42:39.710> sometimes<00:42:39.980> get<00:42:40.310> confused 00:42:40.360 --> 00:42:40.370 align:start position:0% and people sometimes get confused 00:42:40.370 --> 00:42:42.660 align:start position:0% and people sometimes get confused because<00:42:40.880> we're<00:42:41.300> portable<00:42:41.720> and<00:42:41.930> who<00:42:42.020> thinks 00:42:42.660 --> 00:42:42.670 align:start position:0% because we're portable and who thinks 00:42:42.670 --> 00:42:46.150 align:start position:0% because we're portable and who thinks it's<00:42:43.670> okay<00:42:44.080> hockey<00:42:45.080> tournament<00:42:45.440> so<00:42:45.830> basically 00:42:46.150 --> 00:42:46.160 align:start position:0% it's okay hockey tournament so basically 00:42:46.160 --> 00:42:48.520 align:start position:0% it's okay hockey tournament so basically the<00:42:46.340> answer<00:42:46.490> Joaquin<00:42:47.000> dev<00:42:47.210> kit<00:42:47.450> part<00:42:48.170> of<00:42:48.350> that 00:42:48.520 --> 00:42:48.530 align:start position:0% the answer Joaquin dev kit part of that 00:42:48.530 --> 00:42:50.590 align:start position:0% the answer Joaquin dev kit part of that is<00:42:48.710> this<00:42:48.860> Visual<00:42:49.190> Studio<00:42:49.280> code<00:42:49.670> extension<00:42:50.210> but 00:42:50.590 --> 00:42:50.600 align:start position:0% is this Visual Studio code extension but 00:42:50.600 --> 00:42:52.510 align:start position:0% is this Visual Studio code extension but another<00:42:50.780> part<00:42:51.050> of<00:42:51.170> it<00:42:51.350> is<00:42:51.590> this<00:42:51.920> github<00:42:52.130> repo 00:42:52.510 --> 00:42:52.520 align:start position:0% another part of it is this github repo 00:42:52.520 --> 00:42:55.840 align:start position:0% another part of it is this github repo there's<00:42:52.760> open<00:42:53.090> source<00:42:54.280> code<00:42:55.280> examples<00:42:55.730> up 00:42:55.840 --> 00:42:55.850 align:start position:0% there's open source code examples up 00:42:55.850 --> 00:42:58.090 align:start position:0% there's open source code examples up here<00:42:55.880> a<00:42:56.450> much<00:42:57.050> more<00:42:57.230> advanced<00:42:57.560> stuff<00:42:57.800> on 00:42:58.090 --> 00:42:58.100 align:start position:0% here a much more advanced stuff on 00:42:58.100 --> 00:42:59.770 align:start position:0% here a much more advanced stuff on server<00:42:58.400> functions<00:42:59.060> there's<00:42:59.360> a<00:42:59.390> lot<00:42:59.600> of 00:42:59.770 --> 00:42:59.780 align:start position:0% server functions there's a lot of 00:42:59.780 --> 00:43:01.900 align:start position:0% server functions there's a lot of documentation<00:43:00.220> helping<00:43:01.220> get<00:43:01.340> started<00:43:01.640> to<00:43:01.700> all 00:43:01.900 --> 00:43:01.910 align:start position:0% documentation helping get started to all 00:43:01.910 --> 00:43:04.120 align:start position:0% documentation helping get started to all that<00:43:02.030> stuff<00:43:02.270> so<00:43:02.330> once<00:43:03.320> you<00:43:03.410> get<00:43:03.560> beyond<00:43:03.890> the 00:43:04.120 --> 00:43:04.130 align:start position:0% that stuff so once you get beyond the 00:43:04.130 --> 00:43:05.530 align:start position:0% that stuff so once you get beyond the initial<00:43:04.520> stuff<00:43:04.940> that<00:43:05.120> you<00:43:05.180> want<00:43:05.330> to<00:43:05.390> start 00:43:05.530 --> 00:43:05.540 align:start position:0% initial stuff that you want to start 00:43:05.540 --> 00:43:08.860 align:start position:0% initial stuff that you want to start diving<00:43:05.750> into<00:43:06.020> more<00:43:06.470> complex<00:43:07.100> flows<00:43:07.870> something 00:43:08.860 --> 00:43:08.870 align:start position:0% diving into more complex flows something 00:43:08.870 --> 00:43:11.710 align:start position:0% diving into more complex flows something cool<00:43:09.080> to<00:43:09.320> look<00:43:09.440> at<00:43:09.590> the<00:43:10.250> other<00:43:10.370> side<00:43:10.700> was<00:43:10.940> last 00:43:11.710 --> 00:43:11.720 align:start position:0% cool to look at the other side was last 00:43:11.720 --> 00:43:14.820 align:start position:0% cool to look at the other side was last ethereal<00:43:12.350> other<00:43:12.920> one<00:43:13.040> matambi<00:43:13.460> but<00:43:13.730> before<00:43:14.120> in 00:43:14.820 --> 00:43:14.830 align:start position:0% ethereal other one matambi but before in 00:43:14.830 --> 00:43:18.220 align:start position:0% ethereal other one matambi but before in Brooklyn<00:43:15.830> we<00:43:16.580> actually<00:43:17.060> made<00:43:17.240> a<00:43:17.270> first 00:43:18.220 --> 00:43:18.230 align:start position:0% Brooklyn we actually made a first 00:43:18.230 --> 00:43:20.560 align:start position:0% Brooklyn we actually made a first Balinese<00:43:18.920> project<00:43:19.700> with<00:43:19.820> Microsoft<00:43:20.330> actually 00:43:20.560 --> 00:43:20.570 align:start position:0% Balinese project with Microsoft actually 00:43:20.570 --> 00:43:21.730 align:start position:0% Balinese project with Microsoft actually hundred<00:43:20.960> and<00:43:21.110> twenty<00:43:21.380> thousand<00:43:21.710> dollars 00:43:21.730 --> 00:43:21.740 align:start position:0% hundred and twenty thousand dollars 00:43:21.740 --> 00:43:24.490 align:start position:0% hundred and twenty thousand dollars worth<00:43:22.370> of<00:43:22.520> Alibaba<00:43:23.090> and<00:43:23.690> basically<00:43:24.110> what<00:43:24.410> we 00:43:24.490 --> 00:43:24.500 align:start position:0% worth of Alibaba and basically what we 00:43:24.500 --> 00:43:26.440 align:start position:0% worth of Alibaba and basically what we did<00:43:24.650> is<00:43:24.710> proposed<00:43:25.280> out<00:43:25.550> twenty<00:43:26.360> different 00:43:26.440 --> 00:43:26.450 align:start position:0% did is proposed out twenty different 00:43:26.450 --> 00:43:28.390 align:start position:0% did is proposed out twenty different projects<00:43:27.080> for<00:43:27.200> people<00:43:27.440> to<00:43:27.500> work<00:43:27.710> on<00:43:27.830> to<00:43:28.160> build 00:43:28.390 --> 00:43:28.400 align:start position:0% projects for people to work on to build 00:43:28.400 --> 00:43:31.030 align:start position:0% projects for people to work on to build different<00:43:29.060> things<00:43:29.450> using<00:43:29.690> our<00:43:29.930> HSS<00:43:30.470> using 00:43:31.030 --> 00:43:31.040 align:start position:0% different things using our HSS using 00:43:31.040 --> 00:43:33.190 align:start position:0% different things using our HSS using some<00:43:31.430> service<00:43:31.790> functions<00:43:32.240> and<00:43:33.020> there's<00:43:33.140> a 00:43:33.190 --> 00:43:33.200 align:start position:0% some service functions and there's a 00:43:33.200 --> 00:43:34.960 align:start position:0% some service functions and there's a whole<00:43:33.380> slope<00:43:33.710> for<00:43:34.010> some<00:43:34.190> around<00:43:34.430> gaming<00:43:34.640> and 00:43:34.960 --> 00:43:34.970 align:start position:0% whole slope for some around gaming and 00:43:34.970 --> 00:43:37.210 align:start position:0% whole slope for some around gaming and tokenization<00:43:35.300> and<00:43:35.930> basically<00:43:36.800> those<00:43:37.190> are 00:43:37.210 --> 00:43:37.220 align:start position:0% tokenization and basically those are 00:43:37.220 --> 00:43:39.190 align:start position:0% tokenization and basically those are fair<00:43:37.640> as<00:43:37.760> well<00:43:37.970> it<00:43:38.690> was<00:43:38.810> super<00:43:39.170> great 00:43:39.190 --> 00:43:39.200 align:start position:0% fair as well it was super great 00:43:39.200 --> 00:43:42.550 align:start position:0% fair as well it was super great responsible 00:43:42.550 --> 00:43:42.560 align:start position:0% 00:43:42.560 --> 00:43:44.500 align:start position:0% and<00:43:43.010> I<00:43:43.040> worked<00:43:43.640> out<00:43:43.760> really<00:43:43.940> well<00:43:44.060> but<00:43:44.390> we 00:43:44.500 --> 00:43:44.510 align:start position:0% and I worked out really well but we 00:43:44.510 --> 00:43:45.820 align:start position:0% and I worked out really well but we basically<00:43:44.690> have<00:43:45.110> this<00:43:45.200> community-driven 00:43:45.820 --> 00:43:45.830 align:start position:0% basically have this community-driven 00:43:45.830 --> 00:43:47.590 align:start position:0% basically have this community-driven section<00:43:46.370> now<00:43:46.520> too<00:43:46.580> so<00:43:47.000> we<00:43:47.090> have<00:43:47.210> the<00:43:47.330> Microsoft 00:43:47.590 --> 00:43:47.600 align:start position:0% section now too so we have the Microsoft 00:43:47.600 --> 00:43:49.660 align:start position:0% section now too so we have the Microsoft samples<00:43:48.110> we're<00:43:48.350> producing<00:43:48.650> we<00:43:49.340> have<00:43:49.520> the 00:43:49.660 --> 00:43:49.670 align:start position:0% samples we're producing we have the 00:43:49.670 --> 00:43:51.640 align:start position:0% samples we're producing we have the community-driven<00:43:50.180> ones<00:43:50.600> that<00:43:50.840> were<00:43:50.960> kind<00:43:51.560> of 00:43:51.640 --> 00:43:51.650 align:start position:0% community-driven ones that were kind of 00:43:51.650 --> 00:43:53.170 align:start position:0% community-driven ones that were kind of vetting<00:43:51.860> working<00:43:52.430> with<00:43:52.520> the<00:43:52.610> community<00:43:53.000> one 00:43:53.170 --> 00:43:53.180 align:start position:0% vetting working with the community one 00:43:53.180 --> 00:43:55.360 align:start position:0% vetting working with the community one but<00:43:53.720> happy<00:43:54.020> to<00:43:54.140> take<00:43:54.350> for<00:43:54.560> contributions<00:43:55.220> up 00:43:55.360 --> 00:43:55.370 align:start position:0% but happy to take for contributions up 00:43:55.370 --> 00:43:57.250 align:start position:0% but happy to take for contributions up there<00:43:55.550> if<00:43:55.790> you<00:43:55.880> guys<00:43:56.030> on<00:43:56.360> either<00:43:56.570> side<00:43:56.870> forward 00:43:57.250 --> 00:43:57.260 align:start position:0% there if you guys on either side forward 00:43:57.260 --> 00:43:59.440 align:start position:0% there if you guys on either side forward busts<00:43:57.650> are<00:43:57.770> welcome<00:43:58.130> anywhere<00:43:58.460> I<00:43:58.760> elect 00:43:59.440 --> 00:43:59.450 align:start position:0% busts are welcome anywhere I elect 00:43:59.450 --> 00:44:08.009 align:start position:0% busts are welcome anywhere I elect you're<00:43:59.570> here 00:44:08.009 --> 00:44:08.019 align:start position:0% 00:44:08.019 --> 00:44:11.829 align:start position:0% okay<00:44:09.049> so<00:44:09.499> for<00:44:10.430> the<00:44:10.519> last<00:44:10.640> 15<00:44:11.269> minutes<00:44:11.509> I'm 00:44:11.829 --> 00:44:11.839 align:start position:0% okay so for the last 15 minutes I'm 00:44:11.839 --> 00:44:13.509 align:start position:0% okay so for the last 15 minutes I'm going<00:44:12.319> to<00:44:12.380> get<00:44:12.619> everything<00:44:13.190> that<00:44:13.309> we've 00:44:13.509 --> 00:44:13.519 align:start position:0% going to get everything that we've 00:44:13.519 --> 00:44:15.730 align:start position:0% going to get everything that we've talked<00:44:13.759> about<00:44:13.910> and<00:44:14.390> try<00:44:14.569> to<00:44:14.630> remix<00:44:15.380> it<00:44:15.529> to<00:44:15.680> a 00:44:15.730 --> 00:44:15.740 align:start position:0% talked about and try to remix it to a 00:44:15.740 --> 00:44:20.680 align:start position:0% talked about and try to remix it to a fingerprint<00:44:18.309> we<00:44:19.309> dive<00:44:19.519> in<00:44:19.759> and<00:44:20.150> everything 00:44:20.680 --> 00:44:20.690 align:start position:0% fingerprint we dive in and everything 00:44:20.690 --> 00:44:22.690 align:start position:0% fingerprint we dive in and everything that<00:44:20.779> doula<00:44:21.170> Custis<00:44:21.589> is<00:44:21.769> exactly<00:44:22.190> what<00:44:22.369> panel 00:44:22.690 --> 00:44:22.700 align:start position:0% that doula Custis is exactly what panel 00:44:22.700 --> 00:44:23.410 align:start position:0% that doula Custis is exactly what panel to<00:44:22.849> show<00:44:22.880> you 00:44:23.410 --> 00:44:23.420 align:start position:0% to show you 00:44:23.420 --> 00:44:25.089 align:start position:0% to show you so<00:44:23.599> we<00:44:23.779> showed<00:44:23.990> them<00:44:24.109> from<00:44:24.349> the<00:44:24.440> beginning<00:44:24.559> how 00:44:25.089 --> 00:44:25.099 align:start position:0% so we showed them from the beginning how 00:44:25.099 --> 00:44:27.519 align:start position:0% so we showed them from the beginning how to<00:44:25.160> go<00:44:25.549> sceptile<00:44:26.089> sceptile<00:44:26.630> down<00:44:27.079> a<00:44:27.109> brand<00:44:27.410> new 00:44:27.519 --> 00:44:27.529 align:start position:0% to go sceptile sceptile down a brand new 00:44:27.529 --> 00:44:30.339 align:start position:0% to go sceptile sceptile down a brand new project<00:44:27.799> I<00:44:28.309> don't<00:44:28.910> learn<00:44:29.299> how<00:44:29.329> to<00:44:29.569> add<00:44:30.109> in<00:44:30.259> a 00:44:30.339 --> 00:44:30.349 align:start position:0% project I don't learn how to add in a 00:44:30.349 --> 00:44:32.079 align:start position:0% project I don't learn how to add in a few<00:44:30.380> functions<00:44:30.769> into<00:44:31.279> you<00:44:31.460> there's<00:44:31.670> my<00:44:31.819> own 00:44:32.079 --> 00:44:32.089 align:start position:0% few functions into you there's my own 00:44:32.089 --> 00:44:32.529 align:start position:0% few functions into you there's my own tracks 00:44:32.529 --> 00:44:32.539 align:start position:0% tracks 00:44:32.539 --> 00:44:35.230 align:start position:0% tracks show<00:44:32.960> them<00:44:33.079> how<00:44:33.319> to<00:44:33.349> debug<00:44:34.249> cataract<00:44:34.910> unit 00:44:35.230 --> 00:44:35.240 align:start position:0% show them how to debug cataract unit 00:44:35.240 --> 00:44:39.309 align:start position:0% show them how to debug cataract unit tests<00:44:35.779> by<00:44:36.710> 8<00:44:36.890> -<00:44:37.009> the<00:44:37.099> champion<00:44:37.460> testing<00:44:38.319> it's 00:44:39.309 --> 00:44:39.319 align:start position:0% tests by 8 - the champion testing it's 00:44:39.319 --> 00:44:45.819 align:start position:0% tests by 8 - the champion testing it's been<00:44:42.700> through<00:44:43.700> that<00:44:43.849> again<00:44:44.480> it's<00:44:44.690> a<00:44:44.839> getting 00:44:45.819 --> 00:44:45.829 align:start position:0% been through that again it's a getting 00:44:45.829 --> 00:44:48.190 align:start position:0% been through that again it's a getting what<00:44:46.759> we've<00:44:46.880> done<00:44:46.999> in<00:44:47.119> the<00:44:47.180> blockchain<00:44:47.450> blew 00:44:48.190 --> 00:44:48.200 align:start position:0% what we've done in the blockchain blew 00:44:48.200 --> 00:44:49.480 align:start position:0% what we've done in the blockchain blew it<00:44:48.319> up<00:44:48.410> to<00:44:48.589> what's<00:44:48.769> happening<00:44:49.160> in<00:44:49.430> the 00:44:49.480 --> 00:44:49.490 align:start position:0% it up to what's happening in the 00:44:49.490 --> 00:44:53.650 align:start position:0% it up to what's happening in the enterprise<00:44:50.440> so<00:44:51.970> I've<00:44:52.970> run<00:44:53.150> through<00:44:53.420> how<00:44:53.630> it 00:44:53.650 --> 00:44:53.660 align:start position:0% enterprise so I've run through how it 00:44:53.660 --> 00:44:56.680 align:start position:0% enterprise so I've run through how it works<00:44:53.900> for<00:44:54.109> single<00:44:54.950> men<00:44:55.880> million<00:44:56.269> Cybermen 00:44:56.680 --> 00:44:56.690 align:start position:0% works for single men million Cybermen 00:44:56.690 --> 00:44:59.349 align:start position:0% works for single men million Cybermen sodium<00:44:57.109> then<00:44:57.410> we<00:44:57.529> go<00:44:57.730> zoom<00:44:58.730> out<00:44:58.880> to<00:44:59.029> see<00:44:59.059> how<00:44:59.329> it 00:44:59.349 --> 00:44:59.359 align:start position:0% sodium then we go zoom out to see how it 00:44:59.359 --> 00:45:02.019 align:start position:0% sodium then we go zoom out to see how it looks<00:44:59.569> when<00:44:59.839> they<00:44:59.960> come<00:45:00.109> all<00:45:00.769> together<00:45:00.890> so<00:45:01.819> for 00:45:02.019 --> 00:45:02.029 align:start position:0% looks when they come all together so for 00:45:02.029 --> 00:45:07.870 align:start position:0% looks when they come all together so for one<00:45:02.180> enterprise<00:45:06.190> we<00:45:07.190> used<00:45:07.369> to<00:45:07.460> have<00:45:07.549> to<00:45:07.670> go<00:45:07.819> to 00:45:07.870 --> 00:45:07.880 align:start position:0% one enterprise we used to have to go to 00:45:07.880 --> 00:45:10.299 align:start position:0% one enterprise we used to have to go to all<00:45:08.660> the<00:45:08.839> writing<00:45:09.319> of<00:45:09.470> unit<00:45:09.799> testing 00:45:10.299 --> 00:45:10.309 align:start position:0% all the writing of unit testing 00:45:10.309 --> 00:45:13.239 align:start position:0% all the writing of unit testing debugging<00:45:10.490> all<00:45:11.269> that<00:45:11.569> stuff<00:45:11.869> so<00:45:12.069> doing<00:45:13.069> that 00:45:13.239 --> 00:45:13.249 align:start position:0% debugging all that stuff so doing that 00:45:13.249 --> 00:45:17.430 align:start position:0% debugging all that stuff so doing that locally<00:45:14.059> I've<00:45:14.839> got<00:45:15.079> this<00:45:15.920> is<00:45:16.099> bad<00:45:16.339> watching 00:45:17.430 --> 00:45:17.440 align:start position:0% locally I've got this is bad watching 00:45:17.440 --> 00:45:20.460 align:start position:0% locally I've got this is bad watching so<00:45:18.370> public<00:45:18.760> love<00:45:18.940> chamber<00:45:19.360> start<00:45:20.140> doing 00:45:20.460 --> 00:45:20.470 align:start position:0% so public love chamber start doing 00:45:20.470 --> 00:45:22.200 align:start position:0% so public love chamber start doing things<00:45:20.740> so<00:45:20.980> that<00:45:21.190> the<00:45:21.370> back<00:45:21.700> that's<00:45:21.910> Purdue 00:45:22.200 --> 00:45:22.210 align:start position:0% things so that the back that's Purdue 00:45:22.210 --> 00:45:24.480 align:start position:0% things so that the back that's Purdue Cal<00:45:22.780> is<00:45:22.960> talking<00:45:23.290> about<00:45:23.320> with<00:45:23.590> this<00:45:23.650> crowd 00:45:24.480 --> 00:45:24.490 align:start position:0% Cal is talking about with this crowd 00:45:24.490 --> 00:45:26.910 align:start position:0% Cal is talking about with this crowd so<00:45:24.760> if<00:45:25.000> you<00:45:25.180> look<00:45:25.330> at<00:45:25.480> those<00:45:25.660> logic<00:45:26.020> maps<00:45:26.200> so<00:45:26.680> as 00:45:26.910 --> 00:45:26.920 align:start position:0% so if you look at those logic maps so as 00:45:26.920 --> 00:45:30.750 align:start position:0% so if you look at those logic maps so as Cal<00:45:27.220> showed<00:45:27.810> so<00:45:28.810> I<00:45:29.110> used<00:45:29.770> to<00:45:29.920> go<00:45:30.130> and<00:45:30.430> get<00:45:30.610> them 00:45:30.750 --> 00:45:30.760 align:start position:0% Cal showed so I used to go and get them 00:45:30.760 --> 00:45:32.250 align:start position:0% Cal showed so I used to go and get them to<00:45:30.880> do<00:45:31.060> a<00:45:31.090> backhand<00:45:31.360> because<00:45:31.930> I<00:45:31.990> may<00:45:32.080> need<00:45:32.140> to 00:45:32.250 --> 00:45:32.260 align:start position:0% to do a backhand because I may need to 00:45:32.260 --> 00:45:36.000 align:start position:0% to do a backhand because I may need to apply<00:45:33.090> drag<00:45:34.090> in<00:45:34.390> visual<00:45:35.020> designer<00:45:35.380> better 00:45:36.000 --> 00:45:36.010 align:start position:0% apply drag in visual designer better 00:45:36.010 --> 00:45:37.650 align:start position:0% apply drag in visual designer better scale<00:45:36.370> showed<00:45:36.670> you<00:45:36.850> now<00:45:37.000> it<00:45:37.060> takes<00:45:37.330> ten 00:45:37.650 --> 00:45:37.660 align:start position:0% scale showed you now it takes ten 00:45:37.660 --> 00:45:39.480 align:start position:0% scale showed you now it takes ten seconds<00:45:38.080> now<00:45:38.500> just<00:45:38.740> right<00:45:38.920> difference<00:45:39.340> by<00:45:39.460> a 00:45:39.480 --> 00:45:39.490 align:start position:0% seconds now just right difference by a 00:45:39.490 --> 00:45:42.090 align:start position:0% seconds now just right difference by a contractor<00:45:40.090> site<00:45:40.330> we've<00:45:40.570> just<00:45:40.890> generated<00:45:41.890> for 00:45:42.090 --> 00:45:42.100 align:start position:0% contractor site we've just generated for 00:45:42.100 --> 00:45:45.180 align:start position:0% contractor site we've just generated for me<00:45:42.130> generates<00:45:43.090> out<00:45:43.270> that<00:45:43.450> Jason<00:45:43.660> but<00:45:44.050> we<00:45:44.950> still 00:45:45.180 --> 00:45:45.190 align:start position:0% me generates out that Jason but we still 00:45:45.190 --> 00:45:47.280 align:start position:0% me generates out that Jason but we still find<00:45:45.400> that<00:45:45.670> much<00:45:45.850> capital<00:45:46.270> we<00:45:46.480> you<00:45:46.960> can<00:45:47.110> just 00:45:47.280 --> 00:45:47.290 align:start position:0% find that much capital we you can just 00:45:47.290 --> 00:45:49.080 align:start position:0% find that much capital we you can just go<00:45:47.500> and<00:45:47.710> copy<00:45:47.920> paste<00:45:48.100> that<00:45:48.550> what's<00:45:48.760> your<00:45:48.850> path 00:45:49.080 --> 00:45:49.090 align:start position:0% go and copy paste that what's your path 00:45:49.090 --> 00:45:52.290 align:start position:0% go and copy paste that what's your path Jason<00:45:50.020> file<00:45:50.200> happen<00:45:50.740> to<00:45:50.860> add<00:45:50.980> your<00:45:51.160> band<00:45:51.940> now 00:45:52.290 --> 00:45:52.300 align:start position:0% Jason file happen to add your band now 00:45:52.300 --> 00:45:55.140 align:start position:0% Jason file happen to add your band now have<00:45:52.540> your<00:45:52.750> service<00:45:53.590> properties<00:45:54.370> to<00:45:54.700> go<00:45:54.850> into 00:45:55.140 --> 00:45:55.150 align:start position:0% have your service properties to go into 00:45:55.150 --> 00:45:57.450 align:start position:0% have your service properties to go into the<00:45:55.240> blockchain<00:45:55.770> but<00:45:56.770> once<00:45:56.920> you've<00:45:57.040> got<00:45:57.280> that 00:45:57.450 --> 00:45:57.460 align:start position:0% the blockchain but once you've got that 00:45:57.460 --> 00:46:01.120 align:start position:0% the blockchain but once you've got that then<00:45:57.700> in<00:45:58.270> the<00:45:58.360> custom<00:45:58.720> style 00:46:01.120 --> 00:46:01.130 align:start position:0% 00:46:01.130 --> 00:46:07.310 align:start position:0% intranets<00:46:03.380> go<00:46:04.380> and<00:46:05.010> the<00:46:06.000> enterprise<00:46:06.660> dips<00:46:06.960> all 00:46:07.310 --> 00:46:07.320 align:start position:0% intranets go and the enterprise dips all 00:46:07.320 --> 00:46:08.990 align:start position:0% intranets go and the enterprise dips all I<00:46:07.350> care<00:46:07.680> about<00:46:07.710> now<00:46:07.890> is<00:46:08.130> that<00:46:08.400> I<00:46:08.520> kind<00:46:08.730> of<00:46:08.790> rest 00:46:08.990 --> 00:46:09.000 align:start position:0% I care about now is that I kind of rest 00:46:09.000 --> 00:46:11.540 align:start position:0% I care about now is that I kind of rest in<00:46:09.180> pointing<00:46:09.690> the<00:46:10.230> rest<00:46:10.590> endpoint<00:46:10.770> to<00:46:11.130> go<00:46:11.250> and 00:46:11.540 --> 00:46:11.550 align:start position:0% in pointing the rest endpoint to go and 00:46:11.550 --> 00:46:13.430 align:start position:0% in pointing the rest endpoint to go and in<00:46:11.760> terms<00:46:11.940> of<00:46:12.150> reading<00:46:12.480> and<00:46:12.690> writing<00:46:12.840> looking 00:46:13.430 --> 00:46:13.440 align:start position:0% in terms of reading and writing looking 00:46:13.440 --> 00:46:17.270 align:start position:0% in terms of reading and writing looking into<00:46:13.680> the<00:46:13.850> transactions<00:46:16.040> so<00:46:17.040> there<00:46:17.190> are 00:46:17.270 --> 00:46:17.280 align:start position:0% into the transactions so there are 00:46:17.280 --> 00:46:18.950 align:start position:0% into the transactions so there are people<00:46:17.430> we<00:46:17.640> can<00:46:17.940> do<00:46:18.150> around<00:46:18.240> locking<00:46:18.810> this 00:46:18.950 --> 00:46:18.960 align:start position:0% people we can do around locking this 00:46:18.960 --> 00:46:26.410 align:start position:0% people we can do around locking this down<00:46:19.350> to<00:46:20.040> a<00:46:20.070> configuration<00:46:20.520> so<00:46:22.790> accesses<00:46:25.370> but 00:46:26.410 --> 00:46:26.420 align:start position:0% down to a configuration so accesses but 00:46:26.420 --> 00:46:28.730 align:start position:0% down to a configuration so accesses but hopefully<00:46:27.420> use<00:46:27.660> this<00:46:27.840> is<00:46:28.050> a<00:46:28.350> standard 00:46:28.730 --> 00:46:28.740 align:start position:0% hopefully use this is a standard 00:46:28.740 --> 00:46:31.730 align:start position:0% hopefully use this is a standard question<00:46:28.770> points<00:46:29.580> along<00:46:29.970> about<00:46:30.420> which<00:46:31.080> is 00:46:31.730 --> 00:46:31.740 align:start position:0% question points along about which is 00:46:31.740 --> 00:46:35.180 align:start position:0% question points along about which is which<00:46:32.250> is<00:46:32.430> and<00:46:32.940> caring<00:46:33.840> about<00:46:33.980> its<00:46:34.980> money 00:46:35.180 --> 00:46:35.190 align:start position:0% which is and caring about its money 00:46:35.190 --> 00:46:37.160 align:start position:0% which is and caring about its money transactions<00:46:35.850> so<00:46:36.090> we<00:46:36.240> do<00:46:36.420> a<00:46:36.450> little<00:46:36.600> data<00:46:36.870> sign 00:46:37.160 --> 00:46:37.170 align:start position:0% transactions so we do a little data sign 00:46:37.170 --> 00:46:38.020 align:start position:0% transactions so we do a little data sign of<00:46:37.410> that 00:46:38.020 --> 00:46:38.030 align:start position:0% of that 00:46:38.030 --> 00:46:40.810 align:start position:0% of that here<00:46:38.380> that<00:46:39.380> way<00:46:39.560> if<00:46:40.010> something<00:46:40.250> happens<00:46:40.700> as 00:46:40.810 --> 00:46:40.820 align:start position:0% here that way if something happens as 00:46:40.820 --> 00:46:44.680 align:start position:0% here that way if something happens as though<00:46:41.630> we<00:46:41.930> go<00:46:42.140> and<00:46:42.560> step<00:46:43.070> down<00:46:43.310> but<00:46:44.060> that<00:46:44.420> will 00:46:44.680 --> 00:46:44.690 align:start position:0% though we go and step down but that will 00:46:44.690 --> 00:46:45.430 align:start position:0% though we go and step down but that will change 00:46:45.430 --> 00:46:45.440 align:start position:0% change 00:46:45.440 --> 00:46:47.500 align:start position:0% change whose<00:46:45.860> kid<00:46:46.100> including<00:46:46.520> the<00:46:46.580> stuff<00:46:46.850> passion 00:46:47.500 --> 00:46:47.510 align:start position:0% whose kid including the stuff passion 00:46:47.510 --> 00:46:50.650 align:start position:0% whose kid including the stuff passion function 00:46:50.650 --> 00:46:50.660 align:start position:0% 00:46:50.660 --> 00:46:54.780 align:start position:0% perhaps<00:46:51.650> I<00:46:52.070> think<00:46:53.000> how<00:46:53.240> we<00:46:53.990> showed<00:46:54.170> how<00:46:54.380> you<00:46:54.440> do 00:46:54.780 --> 00:46:54.790 align:start position:0% perhaps I think how we showed how you do 00:46:54.790 --> 00:47:10.910 align:start position:0% perhaps I think how we showed how you do colas<00:46:55.790> service<00:46:56.600> we've<00:46:57.140> got<00:46:57.320> this<00:46:57.800> and<00:46:58.100> why 00:47:10.910 --> 00:47:10.920 align:start position:0% 00:47:10.920 --> 00:47:14.130 align:start position:0% that's<00:47:11.920> a<00:47:12.069> good<00:47:12.220> reading<00:47:12.430> a<00:47:12.579> binding<00:47:12.880> site<00:47:13.140> but 00:47:14.130 --> 00:47:14.140 align:start position:0% that's a good reading a binding site but 00:47:14.140 --> 00:47:16.079 align:start position:0% that's a good reading a binding site but if<00:47:14.410> someone<00:47:14.829> else<00:47:14.980> goes<00:47:15.400> enough<00:47:15.640> to<00:47:15.790> watch 00:47:16.079 --> 00:47:16.089 align:start position:0% if someone else goes enough to watch 00:47:16.089 --> 00:47:18.569 align:start position:0% if someone else goes enough to watch chain<00:47:16.359> we<00:47:16.930> have<00:47:17.109> to<00:47:17.260> react<00:47:17.470> to<00:47:17.680> it<00:47:17.800> so<00:47:18.130> we<00:47:18.400> have 00:47:18.569 --> 00:47:18.579 align:start position:0% chain we have to react to it so we have 00:47:18.579 --> 00:47:19.859 align:start position:0% chain we have to react to it so we have the<00:47:18.609> adventure<00:47:19.180> of<00:47:19.270> the<00:47:19.329> stuff<00:47:19.569> in<00:47:19.660> the<00:47:19.720> other 00:47:19.859 --> 00:47:19.869 align:start position:0% the adventure of the stuff in the other 00:47:19.869 --> 00:47:20.490 align:start position:0% the adventure of the stuff in the other side 00:47:20.490 --> 00:47:20.500 align:start position:0% side 00:47:20.500 --> 00:47:22.800 align:start position:0% side again<00:47:21.070> is<00:47:21.280> that<00:47:21.310> that<00:47:21.820> was<00:47:22.000> that<00:47:22.030> I'm<00:47:22.359> service 00:47:22.800 --> 00:47:22.810 align:start position:0% again is that that was that I'm service 00:47:22.810 --> 00:47:26.339 align:start position:0% again is that that was that I'm service article<00:47:23.880> from<00:47:24.880> a<00:47:25.030> sailor<00:47:25.270> star<00:47:25.510> who<00:47:25.810> pushed<00:47:26.140> it 00:47:26.339 --> 00:47:26.349 align:start position:0% article from a sailor star who pushed it 00:47:26.349 --> 00:47:29.339 align:start position:0% article from a sailor star who pushed it to<00:47:26.619> an<00:47:26.950> event<00:47:27.099> grid<00:47:27.580> an<00:47:28.090> event<00:47:28.510> grid<00:47:28.810> what<00:47:29.260> are 00:47:29.339 --> 00:47:29.349 align:start position:0% to an event grid an event grid what are 00:47:29.349 --> 00:47:31.349 align:start position:0% to an event grid an event grid what are the<00:47:29.440> kids<00:47:29.680> back<00:47:29.830> enzyme<00:47:30.490> subscriber<00:47:31.000> three 00:47:31.349 --> 00:47:31.359 align:start position:0% the kids back enzyme subscriber three 00:47:31.359 --> 00:47:32.400 align:start position:0% the kids back enzyme subscriber three cups<00:47:31.599> up 00:47:32.400 --> 00:47:32.410 align:start position:0% cups up 00:47:32.410 --> 00:47:35.220 align:start position:0% cups up so<00:47:32.950> another<00:47:33.400> member<00:47:33.760> updates<00:47:34.210> the<00:47:34.420> borman's 00:47:35.220 --> 00:47:35.230 align:start position:0% so another member updates the borman's 00:47:35.230 --> 00:47:38.030 align:start position:0% so another member updates the borman's for<00:47:35.500> widgets<00:47:35.650> and<00:47:36.340> the<00:47:36.700> event<00:47:36.970> comes<00:47:37.270> up<00:47:37.450> here 00:47:38.030 --> 00:47:38.040 align:start position:0% for widgets and the event comes up here 00:47:38.040 --> 00:47:41.640 align:start position:0% for widgets and the event comes up here architects<00:47:39.040> it<00:47:39.220> publishes<00:47:40.060> it<00:47:40.359> event<00:47:41.230> update 00:47:41.640 --> 00:47:41.650 align:start position:0% architects it publishes it event update 00:47:41.650 --> 00:47:45.680 align:start position:0% architects it publishes it event update evacuate<00:47:42.340> sickle<00:47:42.640> cell<00:47:42.820> we<00:47:43.270> can<00:47:43.300> update<00:47:43.830> how<00:47:44.830> I 00:47:45.680 --> 00:47:45.690 align:start position:0% evacuate sickle cell we can update how I 00:47:45.690 --> 00:47:49.910 align:start position:0% evacuate sickle cell we can update how I reports<00:47:46.690> that<00:47:46.869> for<00:47:47.170> you<00:47:47.290> we<00:47:47.859> go 00:47:49.910 --> 00:47:49.920 align:start position:0% reports that for you we go 00:47:49.920 --> 00:47:53.630 align:start position:0% reports that for you we go and<00:47:50.040> figure<00:47:50.760> out<00:47:51.590> to<00:47:52.590> go<00:47:52.710> start<00:47:53.070> construction 00:47:53.630 --> 00:47:53.640 align:start position:0% and figure out to go start construction 00:47:53.640 --> 00:47:55.280 align:start position:0% and figure out to go start construction constructing<00:47:54.450> widgets<00:47:54.780> for<00:47:54.900> something 00:47:55.280 --> 00:47:55.290 align:start position:0% constructing widgets for something 00:47:55.290 --> 00:48:00.230 align:start position:0% constructing widgets for something twisted<00:47:56.690> so<00:47:57.690> this<00:47:58.350> one<00:47:58.740> his<00:47:59.130> price<00:47:59.460> can<00:47:59.790> go<00:47:59.970> to 00:48:00.230 --> 00:48:00.240 align:start position:0% twisted so this one his price can go to 00:48:00.240 --> 00:48:02.090 align:start position:0% twisted so this one his price can go to website<00:48:00.750> one<00:48:00.990> it's<00:48:01.230> inside<00:48:01.680> of<00:48:01.830> a 00:48:02.090 --> 00:48:02.100 align:start position:0% website one it's inside of a 00:48:02.100 --> 00:48:07.490 align:start position:0% website one it's inside of a infrastructure<00:48:02.900> but<00:48:03.900> because<00:48:04.770> the<00:48:05.040> house<00:48:06.500> and 00:48:07.490 --> 00:48:07.500 align:start position:0% infrastructure but because the house and 00:48:07.500 --> 00:48:08.420 align:start position:0% infrastructure but because the house and looks<00:48:07.770> like<00:48:07.950> this 00:48:08.420 --> 00:48:08.430 align:start position:0% looks like this 00:48:08.430 --> 00:48:10.640 align:start position:0% looks like this so<00:48:08.610> what<00:48:08.940> an<00:48:09.060> approx<00:48:09.630> will<00:48:09.780> pay<00:48:09.900> plump<00:48:10.230> but 00:48:10.640 --> 00:48:10.650 align:start position:0% so what an approx will pay plump but 00:48:10.650 --> 00:48:12.170 align:start position:0% so what an approx will pay plump but because<00:48:10.980> of<00:48:11.130> love<00:48:11.340> shining<00:48:11.580> that<00:48:11.910> cheers 00:48:12.170 --> 00:48:12.180 align:start position:0% because of love shining that cheers 00:48:12.180 --> 00:48:14.090 align:start position:0% because of love shining that cheers thank<00:48:12.540> might<00:48:12.780> expose<00:48:13.290> the<00:48:13.530> truth 00:48:14.090 --> 00:48:14.100 align:start position:0% thank might expose the truth 00:48:14.100 --> 00:48:15.800 align:start position:0% thank might expose the truth Apple<00:48:14.640> the<00:48:14.670> other<00:48:14.910> Enterprise<00:48:15.390> is<00:48:15.570> just 00:48:15.800 --> 00:48:15.810 align:start position:0% Apple the other Enterprise is just 00:48:15.810 --> 00:48:20.330 align:start position:0% Apple the other Enterprise is just reacting<00:48:17.960> have<00:48:18.960> whatever<00:48:19.230> backend<00:48:19.920> systems 00:48:20.330 --> 00:48:20.340 align:start position:0% reacting have whatever backend systems 00:48:20.340 --> 00:48:23.050 align:start position:0% reacting have whatever backend systems if<00:48:20.460> they<00:48:20.490> want<00:48:20.910> to<00:48:20.970> buy<00:48:21.180> as<00:48:21.240> long<00:48:21.480> as<00:48:21.780> is 00:48:23.050 --> 00:48:23.060 align:start position:0% if they want to buy as long as is 00:48:23.060 --> 00:48:25.090 align:start position:0% if they want to buy as long as is everything<00:48:24.060> what's<00:48:24.360> wrong 00:48:25.090 --> 00:48:25.100 align:start position:0% everything what's wrong 00:48:25.100 --> 00:48:28.310 align:start position:0% everything what's wrong I'm<00:48:26.100> so<00:48:26.460> the<00:48:26.610> kid<00:48:26.790> might<00:48:27.540> that<00:48:27.750> we<00:48:27.900> gotta<00:48:28.080> teach 00:48:28.310 --> 00:48:28.320 align:start position:0% I'm so the kid might that we gotta teach 00:48:28.320 --> 00:48:30.910 align:start position:0% I'm so the kid might that we gotta teach them<00:48:28.530> about<00:48:28.620> this<00:48:28.980> is<00:48:29.160> it's<00:48:29.310> over<00:48:29.430> everybody 00:48:30.910 --> 00:48:30.920 align:start position:0% them about this is it's over everybody 00:48:30.920 --> 00:48:34.310 align:start position:0% them about this is it's over everybody remembers<00:48:31.920> what<00:48:32.520> was<00:48:32.550> yeah<00:48:33.180> we're<00:48:33.870> gonna<00:48:33.990> go 00:48:34.310 --> 00:48:34.320 align:start position:0% remembers what was yeah we're gonna go 00:48:34.320 --> 00:48:35.589 align:start position:0% remembers what was yeah we're gonna go ahead 00:48:35.589 --> 00:48:35.599 align:start position:0% ahead 00:48:35.599 --> 00:48:40.029 align:start position:0% ahead a<00:48:35.650> way<00:48:36.880> to<00:48:37.880> say<00:48:38.059> happy<00:48:38.210> to<00:48:38.569> see<00:48:38.749> so<00:48:39.380> they<00:48:39.829> can 00:48:40.029 --> 00:48:40.039 align:start position:0% a way to say happy to see so they can 00:48:40.039 --> 00:48:41.620 align:start position:0% a way to say happy to see so they can still<00:48:40.220> do<00:48:40.369> what<00:48:40.549> they<00:48:40.759> want<00:48:41.089> to<00:48:41.269> predict 00:48:41.620 --> 00:48:41.630 align:start position:0% still do what they want to predict 00:48:41.630 --> 00:48:44.680 align:start position:0% still do what they want to predict management<00:48:42.440> of<00:48:42.529> their<00:48:42.799> articles<00:48:43.099> etc<00:48:43.460> but<00:48:44.450> if 00:48:44.680 --> 00:48:44.690 align:start position:0% management of their articles etc but if 00:48:44.690 --> 00:48:46.630 align:start position:0% management of their articles etc but if they're<00:48:44.839> doing<00:48:44.869> a<00:48:45.109> Big<00:48:45.289> C<00:48:45.680> app<00:48:45.950> they<00:48:46.249> can<00:48:46.279> still 00:48:46.630 --> 00:48:46.640 align:start position:0% they're doing a Big C app they can still 00:48:46.640 --> 00:48:49.450 align:start position:0% they're doing a Big C app they can still have<00:48:46.819> a<00:48:46.880> continuous<00:48:47.450> unattractively<00:48:48.380> so<00:48:49.309> that 00:48:49.450 --> 00:48:49.460 align:start position:0% have a continuous unattractively so that 00:48:49.460 --> 00:48:51.759 align:start position:0% have a continuous unattractively so that we<00:48:49.609> can<00:48:49.789> do<00:48:49.910> it<00:48:50.059> in<00:48:50.329> two<00:48:50.839> different<00:48:50.989> ways<00:48:51.319> the 00:48:51.759 --> 00:48:51.769 align:start position:0% we can do it in two different ways the 00:48:51.769 --> 00:48:54.940 align:start position:0% we can do it in two different ways the first<00:48:52.190> way<00:48:52.569> enterprises<00:48:53.569> usually<00:48:54.499> want<00:48:54.680> to<00:48:54.769> do 00:48:54.940 --> 00:48:54.950 align:start position:0% first way enterprises usually want to do 00:48:54.950 --> 00:48:57.849 align:start position:0% first way enterprises usually want to do it<00:48:55.130> is<00:48:55.609> it<00:48:56.450> was<00:48:56.660> forget<00:48:56.960> the<00:48:57.049> past<00:48:57.410> this<00:48:57.559> point 00:48:57.849 --> 00:48:57.859 align:start position:0% it is it was forget the past this point 00:48:57.859 --> 00:49:00.609 align:start position:0% it is it was forget the past this point is<00:48:58.220> to<00:48:58.489> usually<00:48:58.759> want<00:48:58.940> to<00:48:58.970> control<00:48:59.359> like<00:48:59.720> these 00:49:00.609 --> 00:49:00.619 align:start position:0% is to usually want to control like these 00:49:00.619 --> 00:49:03.999 align:start position:0% is to usually want to control like these for<00:49:00.920> the<00:49:01.009> users<00:49:01.450> so<00:49:02.450> many<00:49:03.229> paths<00:49:03.529> of<00:49:03.680> mobile 00:49:03.999 --> 00:49:04.009 align:start position:0% for the users so many paths of mobile 00:49:04.009 --> 00:49:06.410 align:start position:0% for the users so many paths of mobile apps<00:49:04.249> etc<00:49:04.989> the 00:49:06.410 --> 00:49:06.420 align:start position:0% apps etc the 00:49:06.420 --> 00:49:09.240 align:start position:0% apps etc the [Music] 00:49:09.240 --> 00:49:09.250 align:start position:0% [Music] 00:49:09.250 --> 00:49:12.900 align:start position:0% [Music] can<00:49:09.880> go<00:49:10.030> for<00:49:10.360> watching<00:49:11.110> cat<00:49:11.290> go<00:49:11.740> in<00:49:12.040> switching 00:49:12.900 --> 00:49:12.910 align:start position:0% can go for watching cat go in switching 00:49:12.910 --> 00:49:16.430 align:start position:0% can go for watching cat go in switching transactions<00:49:13.630> updates<00:49:14.020> etc<00:49:14.700> but<00:49:15.700> the<00:49:15.820> keys 00:49:16.430 --> 00:49:16.440 align:start position:0% transactions updates etc but the keys 00:49:16.440 --> 00:49:19.100 align:start position:0% transactions updates etc but the keys yeah<00:49:16.800> so<00:49:17.700> that's<00:49:17.910> probably<00:49:18.390> going<00:49:18.600> to<00:49:18.690> be<00:49:18.810> step 00:49:19.100 --> 00:49:19.110 align:start position:0% yeah so that's probably going to be step 00:49:19.110 --> 00:49:20.900 align:start position:0% yeah so that's probably going to be step one<00:49:19.260> as<00:49:19.710> we<00:49:19.950> get<00:49:20.160> my<00:49:20.310> crack<00:49:20.550> these<00:49:20.700> in<00:49:20.880> a 00:49:20.900 --> 00:49:20.910 align:start position:0% one as we get my crack these in a 00:49:20.910 --> 00:49:23.150 align:start position:0% one as we get my crack these in a process<00:49:21.300> across<00:49:21.810> the<00:49:22.140> state<00:49:22.380> getting<00:49:22.950> about 00:49:23.150 --> 00:49:23.160 align:start position:0% process across the state getting about 00:49:23.160 --> 00:49:25.640 align:start position:0% process across the state getting about more<00:49:23.460> confident<00:49:23.970> and<00:49:24.330> then<00:49:24.840> hopefully<00:49:25.350> also 00:49:25.640 --> 00:49:25.650 align:start position:0% more confident and then hopefully also 00:49:25.650 --> 00:49:33.230 align:start position:0% more confident and then hopefully also get<00:49:25.860> up<00:49:26.010> to<00:49:26.190> something<00:49:26.520> like<00:49:26.550> this<00:49:32.120> in<00:49:33.120> a 00:49:33.230 --> 00:49:33.240 align:start position:0% get up to something like this in a 00:49:33.240 --> 00:49:36.320 align:start position:0% get up to something like this in a process<00:49:33.600> to<00:49:33.750> have<00:49:34.020> a<00:49:34.530> whole<00:49:35.310> day<00:49:35.490> of<00:49:35.520> stuff<00:49:35.850> as 00:49:36.320 --> 00:49:36.330 align:start position:0% process to have a whole day of stuff as 00:49:36.330 --> 00:49:38.600 align:start position:0% process to have a whole day of stuff as well<00:49:36.720> so<00:49:36.750> again<00:49:37.020> everything<00:49:37.650> with<00:49:37.890> teaching 00:49:38.600 --> 00:49:38.610 align:start position:0% well so again everything with teaching 00:49:38.610 --> 00:49:40.640 align:start position:0% well so again everything with teaching here<00:49:38.790> in<00:49:39.090> many<00:49:39.360> show<00:49:39.600> that<00:49:40.020> they<00:49:40.590> could 00:49:40.640 --> 00:49:40.650 align:start position:0% here in many show that they could 00:49:40.650 --> 00:49:43.760 align:start position:0% here in many show that they could enterprise<00:49:41.460> dancer<00:49:42.420> also<00:49:42.720> to<00:49:42.900> public<00:49:43.560> deck 00:49:43.760 --> 00:49:43.770 align:start position:0% enterprise dancer also to public deck 00:49:43.770 --> 00:49:48.290 align:start position:0% enterprise dancer also to public deck tips<00:49:45.530> so<00:49:46.530> once<00:49:46.980> we<00:49:47.220> start<00:49:47.490> getting<00:49:47.670> closer<00:49:48.000> to 00:49:48.290 --> 00:49:48.300 align:start position:0% tips so once we start getting closer to 00:49:48.300 --> 00:49:50.510 align:start position:0% tips so once we start getting closer to you<00:49:48.510> Robles<00:49:48.930> and<00:49:49.170> adoption<00:49:49.800> that<00:49:50.070> means<00:49:50.280> stop 00:49:50.510 --> 00:49:50.520 align:start position:0% you Robles and adoption that means stop 00:49:50.520 --> 00:49:52.290 align:start position:0% you Robles and adoption that means stop happening<00:49:50.760> for 00:49:52.290 --> 00:49:52.300 align:start position:0% happening for 00:49:52.300 --> 00:49:55.380 align:start position:0% happening for so<00:49:52.600> how'd<00:49:53.140> it<00:49:53.170> go<00:49:53.320> at<00:49:53.620> business<00:49:54.150> so<00:49:55.150> if<00:49:55.270> you 00:49:55.380 --> 00:49:55.390 align:start position:0% so how'd it go at business so if you 00:49:55.390 --> 00:49:57.300 align:start position:0% so how'd it go at business so if you closed<00:49:55.630> they<00:49:55.930> should<00:49:56.320> use<00:49:56.470> before<00:49:56.620> that's 00:49:57.300 --> 00:49:57.310 align:start position:0% closed they should use before that's 00:49:57.310 --> 00:50:00.510 align:start position:0% closed they should use before that's these<00:49:57.820> like<00:49:58.000> anaphors<00:49:59.130> and<00:50:00.130> as<00:50:00.370> your 00:50:00.510 --> 00:50:00.520 align:start position:0% these like anaphors and as your 00:50:00.520 --> 00:50:02.940 align:start position:0% these like anaphors and as your blockchain<00:50:00.910> says<00:50:01.180> have<00:50:02.110> some<00:50:02.380> right 00:50:02.940 --> 00:50:02.950 align:start position:0% blockchain says have some right 00:50:02.950 --> 00:50:04.830 align:start position:0% blockchain says have some right mechanisms<00:50:03.520> they<00:50:03.670> have<00:50:03.760> but<00:50:03.970> how<00:50:04.090> to<00:50:04.150> good<00:50:04.480> at 00:50:04.830 --> 00:50:04.840 align:start position:0% mechanisms they have but how to good at 00:50:04.840 --> 00:50:07.290 align:start position:0% mechanisms they have but how to good at magazines<00:50:05.080> like<00:50:05.770> what<00:50:06.640> if<00:50:06.790> I<00:50:06.880> went<00:50:07.060> around 00:50:07.290 --> 00:50:07.300 align:start position:0% magazines like what if I went around 00:50:07.300 --> 00:50:09.800 align:start position:0% magazines like what if I went around that<00:50:07.560> but<00:50:08.560> also<00:50:08.740> on<00:50:09.010> the<00:50:09.100> development<00:50:09.250> side 00:50:09.800 --> 00:50:09.810 align:start position:0% that but also on the development side 00:50:09.810 --> 00:50:12.390 align:start position:0% that but also on the development side now<00:50:10.810> this<00:50:11.020> word<00:50:11.350> gets<00:50:11.560> trigger<00:50:11.830> that<00:50:12.130> we've 00:50:12.390 --> 00:50:12.400 align:start position:0% now this word gets trigger that we've 00:50:12.400 --> 00:50:14.250 align:start position:0% now this word gets trigger that we've actually<00:50:12.580> released<00:50:13.120> a<00:50:13.300> white<00:50:13.510> paper<00:50:13.570> around 00:50:14.250 --> 00:50:14.260 align:start position:0% actually released a white paper around 00:50:14.260 --> 00:50:25.050 align:start position:0% actually released a white paper around how<00:50:14.500> we<00:50:14.710> work<00:50:15.210> in<00:50:16.210> the<00:50:19.410> Microsoft 00:50:25.050 --> 00:50:25.060 align:start position:0% 00:50:25.060 --> 00:50:30.570 align:start position:0% so<00:50:26.050> you<00:50:26.320> have<00:50:27.010> three<00:50:27.400> companies<00:50:29.250> three<00:50:30.250> five 00:50:30.570 --> 00:50:30.580 align:start position:0% so you have three companies three five 00:50:30.580 --> 00:50:32.340 align:start position:0% so you have three companies three five ten<00:50:30.880> companies<00:50:31.300> working<00:50:31.540> together<00:50:31.750> and<00:50:32.260> this 00:50:32.340 --> 00:50:32.350 align:start position:0% ten companies working together and this 00:50:32.350 --> 00:50:34.950 align:start position:0% ten companies working together and this want<00:50:32.620> to<00:50:32.740> show<00:50:32.950> you<00:50:33.150> how<00:50:34.150> do<00:50:34.210> we<00:50:34.390> good<00:50:34.690> and 00:50:34.950 --> 00:50:34.960 align:start position:0% want to show you how do we good and 00:50:34.960 --> 00:50:37.320 align:start position:0% want to show you how do we good and manage<00:50:35.320> everything<00:50:35.890> around<00:50:36.270> updating<00:50:37.270> your 00:50:37.320 --> 00:50:37.330 align:start position:0% manage everything around updating your 00:50:37.330 --> 00:50:39.300 align:start position:0% manage everything around updating your small<00:50:37.600> Skoda<00:50:37.900> updating<00:50:38.350> spot<00:50:38.590> contracts<00:50:39.130> the 00:50:39.300 --> 00:50:39.310 align:start position:0% small Skoda updating spot contracts the 00:50:39.310 --> 00:50:41.610 align:start position:0% small Skoda updating spot contracts the point<00:50:39.610> about<00:50:39.880> I've<00:50:40.780> got<00:50:40.840> some<00:50:41.230> things<00:50:41.440> rather 00:50:41.610 --> 00:50:41.620 align:start position:0% point about I've got some things rather 00:50:41.620 --> 00:50:44.760 align:start position:0% point about I've got some things rather dip<00:50:41.920> around<00:50:42.280> there<00:50:42.640> they're<00:50:42.820> all<00:50:42.940> dead<00:50:43.680> so<00:50:44.680> we 00:50:44.760 --> 00:50:44.770 align:start position:0% dip around there they're all dead so we 00:50:44.770 --> 00:50:47.760 align:start position:0% dip around there they're all dead so we can<00:50:44.950> do<00:50:45.070> things<00:50:45.370> live<00:50:45.810> in<00:50:46.810> southern<00:50:47.530> Asia 00:50:47.760 --> 00:50:47.770 align:start position:0% can do things live in southern Asia 00:50:47.770 --> 00:50:49.830 align:start position:0% can do things live in southern Asia DevOps<00:50:48.250> whenever<00:50:49.120> we<00:50:49.300> have<00:50:49.450> a<00:50:49.480> fuller 00:50:49.830 --> 00:50:49.840 align:start position:0% DevOps whenever we have a fuller 00:50:49.840 --> 00:50:51.420 align:start position:0% DevOps whenever we have a fuller questions<00:50:50.320> we<00:50:50.470> can<00:50:50.620> say<00:50:50.860> that<00:50:51.070> we<00:50:51.220> need<00:50:51.370> to 00:50:51.420 --> 00:50:51.430 align:start position:0% questions we can say that we need to 00:50:51.430 --> 00:50:53.820 align:start position:0% questions we can say that we need to have<00:50:51.790> an<00:50:52.000> agreement<00:50:52.240> on<00:50:52.600> each<00:50:52.900> of<00:50:53.320> consortium 00:50:53.820 --> 00:50:53.830 align:start position:0% have an agreement on each of consortium 00:50:53.830 --> 00:50:57.970 align:start position:0% have an agreement on each of consortium members<00:50:54.280> before<00:50:54.820> that<00:50:54.910> question 00:50:57.970 --> 00:50:57.980 align:start position:0% 00:50:57.980 --> 00:51:00.710 align:start position:0% thank<00:50:58.980> you<00:50:59.130> moving<00:50:59.400> pointing<00:50:59.700> that<00:50:59.760> out<00:51:00.000> we 00:51:00.710 --> 00:51:00.720 align:start position:0% thank you moving pointing that out we 00:51:00.720 --> 00:51:03.050 align:start position:0% thank you moving pointing that out we have<00:51:01.380> multi-seat<00:51:02.010> bullet<00:51:02.310> so<00:51:02.670> that<00:51:02.820> each<00:51:03.030> of 00:51:03.050 --> 00:51:03.060 align:start position:0% have multi-seat bullet so that each of 00:51:03.060 --> 00:51:05.540 align:start position:0% have multi-seat bullet so that each of the<00:51:03.300> consortium<00:51:03.600> ends<00:51:03.960> have<00:51:04.230> to<00:51:04.350> go<00:51:04.500> and<00:51:04.800> sign 00:51:05.540 --> 00:51:05.550 align:start position:0% the consortium ends have to go and sign 00:51:05.550 --> 00:51:06.130 align:start position:0% the consortium ends have to go and sign up<00:51:05.820> before 00:51:06.130 --> 00:51:06.140 align:start position:0% up before 00:51:06.140 --> 00:51:13.540 align:start position:0% up before [Music] 00:51:13.540 --> 00:51:13.550 align:start position:0% 00:51:13.550 --> 00:51:17.620 align:start position:0% so<00:51:14.180> a<00:51:14.950> bunch<00:51:15.950> of<00:51:16.010> life<00:51:16.340> examples<00:51:17.030> but<00:51:17.180> he<00:51:17.540> is 00:51:17.620 --> 00:51:17.630 align:start position:0% so a bunch of life examples but he is 00:51:17.630 --> 00:51:20.980 align:start position:0% so a bunch of life examples but he is one<00:51:17.840> which<00:51:18.170> is<00:51:18.290> he<00:51:18.470> local<00:51:19.010> in<00:51:19.220> Japan<00:51:19.720> so<00:51:20.720> here 00:51:20.980 --> 00:51:20.990 align:start position:0% one which is he local in Japan so here 00:51:20.990 --> 00:51:23.020 align:start position:0% one which is he local in Japan so here at<00:51:21.080> Japan<00:51:21.410> were<00:51:21.620> working<00:51:22.010> with<00:51:22.190> a<00:51:22.490> couple<00:51:23.000> of 00:51:23.020 --> 00:51:23.030 align:start position:0% at Japan were working with a couple of 00:51:23.030 --> 00:51:24.550 align:start position:0% at Japan were working with a couple of company<00:51:23.450> and<00:51:23.540> some<00:51:23.720> to<00:51:23.900> Craig<00:51:24.170> and<00:51:24.200> even 00:51:24.550 --> 00:51:24.560 align:start position:0% company and some to Craig and even 00:51:24.560 --> 00:51:27.040 align:start position:0% company and some to Craig and even saurian<00:51:24.950> we've<00:51:25.160> got<00:51:25.370> Japan<00:51:25.970> Rockies<00:51:26.510> is<00:51:26.990> a 00:51:27.040 --> 00:51:27.050 align:start position:0% saurian we've got Japan Rockies is a 00:51:27.050 --> 00:51:32.530 align:start position:0% saurian we've got Japan Rockies is a both<00:51:27.320> a<00:51:29.590> nation<00:51:30.590> services<00:51:31.280> some<00:51:32.150> insurance 00:51:32.530 --> 00:51:32.540 align:start position:0% both a nation services some insurance 00:51:32.540 --> 00:51:33.740 align:start position:0% both a nation services some insurance companies 00:51:33.740 --> 00:51:33.750 align:start position:0% companies 00:51:33.750 --> 00:51:37.280 align:start position:0% companies so<00:51:34.620> Johnny<00:51:35.310> here's<00:51:35.760> namely<00:51:36.300> the<00:51:36.810> ability<00:51:36.870> of 00:51:37.280 --> 00:51:37.290 align:start position:0% so Johnny here's namely the ability of 00:51:37.290 --> 00:51:39.110 align:start position:0% so Johnny here's namely the ability of the<00:51:37.380> service<00:51:37.770> kind<00:51:38.160> of<00:51:38.310> Hope<00:51:38.430> Commons<00:51:38.820> get<00:51:39.000> the 00:51:39.110 --> 00:51:39.120 align:start position:0% the service kind of Hope Commons get the 00:51:39.120 --> 00:51:40.910 align:start position:0% the service kind of Hope Commons get the point<00:51:39.360> our<00:51:39.510> R&D<00:51:39.960> but<00:51:40.380> they've<00:51:40.530> go<00:51:40.710> through 00:51:40.910 --> 00:51:40.920 align:start position:0% point our R&D but they've go through 00:51:40.920 --> 00:51:42.740 align:start position:0% point our R&D but they've go through multiple<00:51:41.130> different<00:51:41.400> disasters<00:51:41.910> providers 00:51:42.740 --> 00:51:42.750 align:start position:0% multiple different disasters providers 00:51:42.750 --> 00:51:44.360 align:start position:0% multiple different disasters providers as<00:51:43.050> some<00:51:43.590> of<00:51:43.680> you<00:51:43.770> may<00:51:43.890> have<00:51:43.920> seen<00:51:44.190> while 00:51:44.360 --> 00:51:44.370 align:start position:0% as some of you may have seen while 00:51:44.370 --> 00:51:45.980 align:start position:0% as some of you may have seen while you've<00:51:44.460> been<00:51:44.490> in<00:51:44.640> Japan<00:51:44.820> you<00:51:45.210> may<00:51:45.480> have<00:51:45.810> to<00:51:45.900> go 00:51:45.980 --> 00:51:45.990 align:start position:0% you've been in Japan you may have to go 00:51:45.990 --> 00:51:48.440 align:start position:0% you've been in Japan you may have to go to<00:51:46.020> Japan<00:51:46.310> ravishing<00:51:47.310> fenced<00:51:47.670> in<00:51:47.820> maybe<00:51:48.120> take 00:51:48.440 --> 00:51:48.450 align:start position:0% to Japan ravishing fenced in maybe take 00:51:48.450 --> 00:51:51.320 align:start position:0% to Japan ravishing fenced in maybe take you<00:51:48.570> underground<00:51:48.870> gentle<00:51:49.860> to<00:51:49.950> a<00:51:49.980> bus<00:51:50.280> so<00:51:51.180> the 00:51:51.320 --> 00:51:51.330 align:start position:0% you underground gentle to a bus so the 00:51:51.330 --> 00:51:54.490 align:start position:0% you underground gentle to a bus so the idea<00:51:51.630> here<00:51:51.810> is<00:51:51.900> about<00:51:52.170> having<00:51:52.680> one<00:51:53.280> system 00:51:54.490 --> 00:51:54.500 align:start position:0% idea here is about having one system 00:51:54.500 --> 00:51:58.250 align:start position:0% idea here is about having one system spend<00:51:55.500> abusing<00:51:56.040> and<00:51:56.820> so<00:51:57.030> the<00:51:57.510> best<00:51:57.720> prototype 00:51:58.250 --> 00:51:58.260 align:start position:0% spend abusing and so the best prototype 00:51:58.260 --> 00:52:00.740 align:start position:0% spend abusing and so the best prototype for<00:51:58.620> this<00:51:58.800> we<00:51:59.040> got<00:51:59.220> up<00:51:59.340> to<00:51:59.370> money<00:51:59.670> got<00:51:59.970> me<00:52:00.240> three 00:52:00.740 --> 00:52:00.750 align:start position:0% for this we got up to money got me three 00:52:00.750 --> 00:52:02.510 align:start position:0% for this we got up to money got me three four<00:52:00.960> days<00:52:01.140> but<00:52:01.680> we're<00:52:01.920> using<00:52:02.040> the<00:52:02.250> best 00:52:02.510 --> 00:52:02.520 align:start position:0% four days but we're using the best 00:52:02.520 --> 00:52:03.620 align:start position:0% four days but we're using the best Korean<00:52:02.910> intentions 00:52:03.620 --> 00:52:03.630 align:start position:0% Korean intentions 00:52:03.630 --> 00:52:06.200 align:start position:0% Korean intentions the<00:52:04.050> scaffolding<00:52:04.290> out<00:52:04.830> all<00:52:05.670> of<00:52:05.700> the<00:52:05.880> civil 00:52:06.200 --> 00:52:06.210 align:start position:0% the scaffolding out all of the civil 00:52:06.210 --> 00:52:09.560 align:start position:0% the scaffolding out all of the civil patients<00:52:06.930> here<00:52:07.080> you<00:52:07.680> can<00:52:08.040> see<00:52:08.190> here<00:52:08.730> megabytes 00:52:09.560 --> 00:52:09.570 align:start position:0% patients here you can see here megabytes 00:52:09.570 --> 00:52:12.620 align:start position:0% patients here you can see here megabytes and<00:52:09.810> Japanese<00:52:10.200> but<00:52:10.770> the<00:52:11.460> only<00:52:11.760> ones<00:52:12.090> of<00:52:12.210> tokens 00:52:12.620 --> 00:52:12.630 align:start position:0% and Japanese but the only ones of tokens 00:52:12.630 --> 00:52:14.720 align:start position:0% and Japanese but the only ones of tokens the<00:52:12.900> icing<00:52:13.230> seven<00:52:13.500> to<00:52:13.620> one<00:52:13.770> tokens<00:52:14.310> who<00:52:14.580> are 00:52:14.720 --> 00:52:14.730 align:start position:0% the icing seven to one tokens who are 00:52:14.730 --> 00:52:16.730 align:start position:0% the icing seven to one tokens who are just<00:52:14.970> using<00:52:15.150> industry<00:52:15.690> standards<00:52:16.380> open 00:52:16.730 --> 00:52:16.740 align:start position:0% just using industry standards open 00:52:16.740 --> 00:52:20.350 align:start position:0% just using industry standards open Zeppelin<00:52:17.190> to<00:52:17.430> go<00:52:17.550> step<00:52:17.940> up<00:52:18.120> works<00:52:18.330> out<00:52:18.510> for<00:52:18.750> us 00:52:20.350 --> 00:52:20.360 align:start position:0% Zeppelin to go step up works out for us 00:52:20.360 --> 00:52:23.090 align:start position:0% Zeppelin to go step up works out for us we're<00:52:21.360> using<00:52:21.570> the<00:52:21.810> service<00:52:22.290> Oracle's<00:52:22.770> to<00:52:22.950> go 00:52:23.090 --> 00:52:23.100 align:start position:0% we're using the service Oracle's to go 00:52:23.100 --> 00:52:24.200 align:start position:0% we're using the service Oracle's to go to<00:52:23.160> the<00:52:23.310> technical<00:52:23.730> things<00:52:23.910> were<00:52:24.030> happening 00:52:24.200 --> 00:52:24.210 align:start position:0% to the technical things were happening 00:52:24.210 --> 00:52:27.420 align:start position:0% to the technical things were happening update<00:52:25.140> report<00:52:25.650> so<00:52:25.950> we<00:52:26.070> can<00:52:26.160> show<00:52:26.370> how 00:52:27.420 --> 00:52:27.430 align:start position:0% update report so we can show how 00:52:27.430 --> 00:52:32.280 align:start position:0% update report so we can show how the<00:52:27.910> tickers<00:52:29.190> etc<00:52:30.190> so<00:52:30.760> there<00:52:31.480> are<00:52:31.660> many<00:52:31.839> places 00:52:32.280 --> 00:52:32.290 align:start position:0% the tickers etc so there are many places 00:52:32.290 --> 00:52:37.530 align:start position:0% the tickers etc so there are many places to<00:52:32.530> go<00:52:32.559> and<00:52:32.680> bash<00:52:32.980> up<00:52:33.780> these<00:52:34.780> things<00:52:35.970> so<00:52:36.970> here 00:52:37.530 --> 00:52:37.540 align:start position:0% to go and bash up these things so here 00:52:37.540 --> 00:52:39.540 align:start position:0% to go and bash up these things so here we've<00:52:38.410> got<00:52:38.440> you<00:52:38.890> need<00:52:39.010> to<00:52:39.130> connect<00:52:39.430> between 00:52:39.540 --> 00:52:39.550 align:start position:0% we've got you need to connect between 00:52:39.550 --> 00:52:41.579 align:start position:0% we've got you need to connect between these<00:52:40.000> are<00:52:40.119> home<00:52:40.270> base<00:52:40.480> traditional<00:52:41.079> back-end 00:52:41.579 --> 00:52:41.589 align:start position:0% these are home base traditional back-end 00:52:41.589 --> 00:52:44.760 align:start position:0% these are home base traditional back-end systems<00:52:42.420> so<00:52:43.420> that's<00:52:43.780> got<00:52:43.930> the<00:52:44.050> open<00:52:44.410> banking 00:52:44.760 --> 00:52:44.770 align:start position:0% systems so that's got the open banking 00:52:44.770 --> 00:52:48.180 align:start position:0% systems so that's got the open banking HDI<00:52:45.190> -<00:52:45.339> and<00:52:46.000> the<00:52:46.150> customer<00:52:46.569> accounts<00:52:47.319> so<00:52:47.950> how 00:52:48.180 --> 00:52:48.190 align:start position:0% HDI - and the customer accounts so how 00:52:48.190 --> 00:52:50.280 align:start position:0% HDI - and the customer accounts so how do<00:52:48.250> we<00:52:48.400> go<00:52:48.609> and<00:52:48.880> take<00:52:49.150> that<00:52:49.359> in<00:52:49.569> with<00:52:49.750> what<00:52:50.109> they 00:52:50.280 --> 00:52:50.290 align:start position:0% do we go and take that in with what they 00:52:50.290 --> 00:52:53.130 align:start position:0% do we go and take that in with what they sew<00:52:50.800> in<00:52:51.130> weave<00:52:51.430> those<00:52:51.819> simplest<00:52:52.450> applications 00:52:53.130 --> 00:52:53.140 align:start position:0% sew in weave those simplest applications 00:52:53.140 --> 00:52:55.349 align:start position:0% sew in weave those simplest applications to<00:52:53.349> allow<00:52:53.440> customers<00:52:54.069> to<00:52:54.130> think<00:52:54.220> something<00:52:54.790> do 00:52:55.349 --> 00:52:55.359 align:start position:0% to allow customers to think something do 00:52:55.359 --> 00:52:57.210 align:start position:0% to allow customers to think something do something<00:52:55.390> do<00:52:56.020> something<00:52:56.050> service<00:52:57.040> which 00:52:57.210 --> 00:52:57.220 align:start position:0% something do something service which 00:52:57.220 --> 00:52:59.579 align:start position:0% something do something service which goes<00:52:57.460> and<00:52:57.609> updates<00:52:57.880> the<00:52:57.970> SE<00:52:58.270> $20<00:52:59.170> attended 00:52:59.579 --> 00:52:59.589 align:start position:0% goes and updates the SE $20 attended 00:52:59.589 --> 00:53:04.230 align:start position:0% goes and updates the SE $20 attended cetera<00:53:01.829> so<00:53:02.829> then<00:53:02.980> we<00:53:03.099> went<00:53:03.250> back<00:53:03.369> and<00:53:04.030> then<00:53:04.119> in 00:53:04.230 --> 00:53:04.240 align:start position:0% cetera so then we went back and then in 00:53:04.240 --> 00:53:07.200 align:start position:0% cetera so then we went back and then in another<00:53:04.329> four<00:53:04.720> days<00:53:04.750> we<00:53:05.260> went<00:53:05.410> and<00:53:06.210> smashed 00:53:07.200 --> 00:53:07.210 align:start position:0% another four days we went and smashed 00:53:07.210 --> 00:53:09.569 align:start position:0% another four days we went and smashed together<00:53:07.690> another<00:53:08.109> Houston<00:53:08.589> our<00:53:08.740> race<00:53:08.920> so 00:53:09.569 --> 00:53:09.579 align:start position:0% together another Houston our race so 00:53:09.579 --> 00:53:13.609 align:start position:0% together another Houston our race so again<00:53:09.849> we've<00:53:10.059> got<00:53:10.089> more<00:53:10.480> as<00:53:10.720> in<00:53:10.960> 27<00:53:11.710> to<00:53:11.859> one 00:53:13.609 --> 00:53:13.619 align:start position:0% again we've got more as in 27 to one 00:53:13.619 --> 00:53:15.739 align:start position:0% again we've got more as in 27 to one happened 00:53:15.739 --> 00:53:15.749 align:start position:0% happened 00:53:15.749 --> 00:53:18.349 align:start position:0% happened but<00:53:16.170> in<00:53:16.920> everything<00:53:17.549> we're<00:53:17.700> doing<00:53:17.880> here<00:53:18.029> is 00:53:18.349 --> 00:53:18.359 align:start position:0% but in everything we're doing here is 00:53:18.359 --> 00:53:19.969 align:start position:0% but in everything we're doing here is helping<00:53:18.539> make<00:53:18.839> sure<00:53:18.900> it's<00:53:19.200> all<00:53:19.349> blockchain 00:53:19.969 --> 00:53:19.979 align:start position:0% helping make sure it's all blockchain 00:53:19.979 --> 00:53:22.130 align:start position:0% helping make sure it's all blockchain fundamentals<00:53:20.579> but<00:53:21.150> for<00:53:21.269> example<00:53:21.660> malkia 00:53:22.130 --> 00:53:22.140 align:start position:0% fundamentals but for example malkia 00:53:22.140 --> 00:53:26.029 align:start position:0% fundamentals but for example malkia around<00:53:23.269> management<00:53:24.269> so<00:53:24.779> looking<00:53:25.710> around<00:53:25.799> how 00:53:26.029 --> 00:53:26.039 align:start position:0% around management so looking around how 00:53:26.039 --> 00:53:27.200 align:start position:0% around management so looking around how can<00:53:26.099> we<00:53:26.279> do<00:53:26.430> this<00:53:26.549> with<00:53:26.729> the<00:53:26.819> centralized 00:53:27.200 --> 00:53:27.210 align:start position:0% can we do this with the centralized 00:53:27.210 --> 00:53:29.299 align:start position:0% can we do this with the centralized identity<00:53:27.749> but<00:53:28.319> we<00:53:28.469> wanted<00:53:28.769> to<00:53:28.829> make<00:53:29.039> sure<00:53:29.069> that 00:53:29.299 --> 00:53:29.309 align:start position:0% identity but we wanted to make sure that 00:53:29.309 --> 00:53:35.779 align:start position:0% identity but we wanted to make sure that these<00:53:31.880> as<00:53:32.880> well<00:53:33.180> so<00:53:34.190> I'll<00:53:35.190> be<00:53:35.279> very<00:53:35.519> careful 00:53:35.779 --> 00:53:35.789 align:start position:0% these as well so I'll be very careful 00:53:35.789 --> 00:53:37.729 align:start position:0% these as well so I'll be very careful with<00:53:36.239> what<00:53:36.390> I've<00:53:36.539> said<00:53:36.989> because<00:53:37.349> this<00:53:37.410> is<00:53:37.589> all 00:53:37.729 --> 00:53:37.739 align:start position:0% with what I've said because this is all 00:53:37.739 --> 00:53:42.650 align:start position:0% with what I've said because this is all still<00:53:38.779> ocean<00:53:39.779> but<00:53:40.549> that's<00:53:41.549> a<00:53:41.849> picture<00:53:42.359> of<00:53:42.479> that 00:53:42.650 --> 00:53:42.660 align:start position:0% still ocean but that's a picture of that 00:53:42.660 --> 00:53:44.180 align:start position:0% still ocean but that's a picture of that picture<00:53:43.019> is<00:53:43.140> in<00:53:43.289> the<00:53:43.319> official<00:53:43.979> press<00:53:44.160> release 00:53:44.180 --> 00:53:44.190 align:start position:0% picture is in the official press release 00:53:44.190 --> 00:53:51.240 align:start position:0% picture is in the official press release um<00:53:44.670> let's<00:53:44.880> talk<00:53:45.119> about 00:53:51.240 --> 00:53:51.250 align:start position:0% 00:53:51.250 --> 00:53:59.280 align:start position:0% talk<00:53:51.550> about 00:53:59.280 --> 00:53:59.290 align:start position:0% 00:53:59.290 --> 00:54:01.950 align:start position:0% so<00:53:59.829> that<00:53:59.980> was<00:54:00.099> one<00:54:00.280> customer<00:54:00.670> example<00:54:01.150> I'm 00:54:01.950 --> 00:54:01.960 align:start position:0% so that was one customer example I'm 00:54:01.960 --> 00:54:03.930 align:start position:0% so that was one customer example I'm sorry<00:54:02.380> to<00:54:02.589> show<00:54:02.740> another<00:54:03.099> way<00:54:03.339> that<00:54:03.369> we<00:54:03.760> can 00:54:03.930 --> 00:54:03.940 align:start position:0% sorry to show another way that we can 00:54:03.940 --> 00:54:08.700 align:start position:0% sorry to show another way that we can smash<00:54:04.750> these<00:54:05.020> up<00:54:06.990> so<00:54:07.990> another<00:54:08.260> way<00:54:08.380> to<00:54:08.410> match 00:54:08.700 --> 00:54:08.710 align:start position:0% smash these up so another way to match 00:54:08.710 --> 00:54:12.960 align:start position:0% smash these up so another way to match these<00:54:08.920> up<00:54:09.180> so<00:54:10.180> actually<00:54:10.720> we<00:54:11.700> doesn't<00:54:12.700> dispense 00:54:12.960 --> 00:54:12.970 align:start position:0% these up so actually we doesn't dispense 00:54:12.970 --> 00:54:17.010 align:start position:0% these up so actually we doesn't dispense intelligent<00:54:13.540> customers<00:54:13.960> now<00:54:15.270> because<00:54:16.270> high 00:54:17.010 --> 00:54:17.020 align:start position:0% intelligent customers now because high 00:54:17.020 --> 00:54:19.620 align:start position:0% intelligent customers now because high high<00:54:17.470> frequency<00:54:17.980> item<00:54:18.490> data<00:54:18.730> coming<00:54:19.060> in<00:54:19.329> so 00:54:19.620 --> 00:54:19.630 align:start position:0% high frequency item data coming in so 00:54:19.630 --> 00:54:22.410 align:start position:0% high frequency item data coming in so for<00:54:19.839> the<00:54:19.930> IOT<00:54:20.349> devices<00:54:20.730> sending<00:54:21.730> in<00:54:21.819> millions 00:54:22.410 --> 00:54:22.420 align:start position:0% for the IOT devices sending in millions 00:54:22.420 --> 00:54:24.270 align:start position:0% for the IOT devices sending in millions of<00:54:22.540> transactions<00:54:23.079> per<00:54:23.109> second<00:54:23.530> half<00:54:24.069> we 00:54:24.270 --> 00:54:24.280 align:start position:0% of transactions per second half we 00:54:24.280 --> 00:54:26.970 align:start position:0% of transactions per second half we handled<00:54:24.700> a<00:54:24.819> band<00:54:25.180> security<00:54:25.839> so<00:54:26.470> we<00:54:26.859> obviously 00:54:26.970 --> 00:54:26.980 align:start position:0% handled a band security so we obviously 00:54:26.980 --> 00:54:29.099 align:start position:0% handled a band security so we obviously have<00:54:27.430> a<00:54:27.670> million<00:54:28.000> transactions<00:54:28.690> a<00:54:28.780> second 00:54:29.099 --> 00:54:29.109 align:start position:0% have a million transactions a second 00:54:29.109 --> 00:54:45.859 align:start position:0% have a million transactions a second into<00:54:29.290> a<00:54:29.319> blockchain<00:54:30.089> so<00:54:31.089> what<00:54:31.480> we<00:54:32.190> want<00:54:33.190> to<00:54:43.980> do 00:54:45.859 --> 00:54:45.869 align:start position:0% into a blockchain so what we want to do 00:54:45.869 --> 00:54:53.609 align:start position:0% into a blockchain so what we want to do what<00:54:46.869> we<00:54:46.990> call<00:54:47.170> an<00:54:47.349> end<00:54:47.589> up<00:54:47.770> citizen 00:54:53.609 --> 00:54:53.619 align:start position:0% 00:54:53.619 --> 00:54:56.710 align:start position:0% these<00:54:54.619> transactions<00:54:55.340> turn<00:54:56.119> out<00:54:56.270> to<00:54:56.540> the 00:54:56.710 --> 00:54:56.720 align:start position:0% these transactions turn out to the 00:54:56.720 --> 00:55:06.640 align:start position:0% these transactions turn out to the beautiful<00:54:57.110> beautiful<00:54:57.410> ball<00:54:57.800> storage<00:55:05.650> which 00:55:06.640 --> 00:55:06.650 align:start position:0% beautiful beautiful ball storage which 00:55:06.650 --> 00:55:12.750 align:start position:0% beautiful beautiful ball storage which is<00:55:06.680> right<00:55:07.220> well<00:55:07.520> still<00:55:07.820> a<00:55:07.940> Samba<00:55:08.300> subscription 00:55:12.750 --> 00:55:12.760 align:start position:0% 00:55:12.760 --> 00:55:18.280 align:start position:0% this<00:55:13.760> is<00:55:13.910> not<00:55:14.060> try<00:55:14.240> to<00:55:16.150> deter<00:55:17.150> I<00:55:17.450> could<00:55:18.020> still 00:55:18.280 --> 00:55:18.290 align:start position:0% this is not try to deter I could still 00:55:18.290 --> 00:55:24.220 align:start position:0% this is not try to deter I could still want<00:55:18.590> to<00:55:18.650> buy<00:55:18.830> while<00:55:19.100> it's<00:55:19.250> in<00:55:19.400> transit<00:55:23.200> rabbit 00:55:24.220 --> 00:55:24.230 align:start position:0% want to buy while it's in transit rabbit 00:55:24.230 --> 00:55:26.710 align:start position:0% want to buy while it's in transit rabbit so<00:55:24.800> we<00:55:25.220> periodically<00:55:25.820> wanted<00:55:26.540> to<00:55:26.630> the 00:55:26.710 --> 00:55:26.720 align:start position:0% so we periodically wanted to the 00:55:26.720 --> 00:55:29.680 align:start position:0% so we periodically wanted to the beautiful<00:55:27.080> gorgeous<00:55:27.500> happy<00:55:28.280> change<00:55:28.610> so<00:55:29.330> we<00:55:29.480> go 00:55:29.680 --> 00:55:29.690 align:start position:0% beautiful gorgeous happy change so we go 00:55:29.690 --> 00:55:31.720 align:start position:0% beautiful gorgeous happy change so we go and<00:55:30.050> every<00:55:30.590> minute<00:55:30.740> or<00:55:31.010> 10<00:55:31.220> minutes<00:55:31.580> or 00:55:31.720 --> 00:55:31.730 align:start position:0% and every minute or 10 minutes or 00:55:31.730 --> 00:55:33.640 align:start position:0% and every minute or 10 minutes or everyone<00:55:32.270> I'm<00:55:32.690> going<00:55:33.020> to<00:55:33.110> take<00:55:33.260> the<00:55:33.410> hash 00:55:33.640 --> 00:55:33.650 align:start position:0% everyone I'm going to take the hash 00:55:33.650 --> 00:55:35.350 align:start position:0% everyone I'm going to take the hash among<00:55:34.040> those<00:55:34.190> millions<00:55:34.640> of<00:55:34.730> transactions 00:55:35.350 --> 00:55:35.360 align:start position:0% among those millions of transactions 00:55:35.360 --> 00:55:36.910 align:start position:0% among those millions of transactions which<00:55:35.570> is<00:55:35.690> sitting<00:55:35.930> there<00:55:36.110> I'm<00:55:36.530> gonna<00:55:36.680> anchor 00:55:36.910 --> 00:55:36.920 align:start position:0% which is sitting there I'm gonna anchor 00:55:36.920 --> 00:55:40.270 align:start position:0% which is sitting there I'm gonna anchor that<00:55:37.250> into<00:55:37.670> a<00:55:37.700> blockchain<00:55:37.910> somewhere<00:55:39.280> so 00:55:40.270 --> 00:55:40.280 align:start position:0% that into a blockchain somewhere so 00:55:40.280 --> 00:55:42.250 align:start position:0% that into a blockchain somewhere so we've<00:55:40.610> actually<00:55:40.760> got<00:55:41.300> an<00:55:41.570> to<00:55:41.780> read<00:55:41.900> up<00:55:42.080> on 00:55:42.250 --> 00:55:42.260 align:start position:0% we've actually got an to read up on 00:55:42.260 --> 00:55:49.170 align:start position:0% we've actually got an to read up on stream<00:55:42.740> github 00:55:49.170 --> 00:55:49.180 align:start position:0% 00:55:49.180 --> 00:55:53.730 align:start position:0% so<00:55:49.329> we've<00:55:49.630> got<00:55:49.809> pictures<00:55:50.819> etc<00:55:52.349> but<00:55:53.349> we<00:55:53.500> just 00:55:53.730 --> 00:55:53.740 align:start position:0% so we've got pictures etc but we just 00:55:53.740 --> 00:55:57.450 align:start position:0% so we've got pictures etc but we just did<00:55:54.010> this<00:55:54.569> quickly<00:55:55.569> with<00:55:55.990> Rio<00:55:56.260> together<00:55:56.619> next 00:55:57.450 --> 00:55:57.460 align:start position:0% did this quickly with Rio together next 00:55:57.460 --> 00:55:59.880 align:start position:0% did this quickly with Rio together next month<00:55:58.020> marks<00:55:59.020> up<00:55:59.170> we're<00:55:59.319> doing<00:55:59.500> a<00:55:59.559> little<00:55:59.740> bit 00:55:59.880 --> 00:55:59.890 align:start position:0% month marks up we're doing a little bit 00:55:59.890 --> 00:56:02.730 align:start position:0% month marks up we're doing a little bit channel<00:56:00.160> hackathon<00:56:01.000> so<00:56:01.599> I'm<00:56:02.079> gonna<00:56:02.260> get<00:56:02.529> a<00:56:02.559> few 00:56:02.730 --> 00:56:02.740 align:start position:0% channel hackathon so I'm gonna get a few 00:56:02.740 --> 00:56:04.710 align:start position:0% channel hackathon so I'm gonna get a few people<00:56:02.950> to<00:56:03.099> it<00:56:03.279> could<00:56:03.430> be<00:56:03.490> said<00:56:03.849> we<00:56:04.480> would<00:56:04.599> have 00:56:04.710 --> 00:56:04.720 align:start position:0% people to it could be said we would have 00:56:04.720 --> 00:56:07.260 align:start position:0% people to it could be said we would have this<00:56:04.900> documentation<00:56:05.440> a<00:56:05.650> little<00:56:05.890> bit<00:56:05.980> nicer<00:56:06.270> so 00:56:07.260 --> 00:56:07.270 align:start position:0% this documentation a little bit nicer so 00:56:07.270 --> 00:56:08.549 align:start position:0% this documentation a little bit nicer so what<00:56:07.420> have<00:56:07.539> some<00:56:07.690> better<00:56:07.809> Quick<00:56:08.079> Start<00:56:08.289> Guide 00:56:08.549 --> 00:56:08.559 align:start position:0% what have some better Quick Start Guide 00:56:08.559 --> 00:56:12.620 align:start position:0% what have some better Quick Start Guide today 00:56:12.620 --> 00:56:12.630 align:start position:0% 00:56:12.630 --> 00:56:16.260 align:start position:0% now<00:56:13.680> all<00:56:14.680> the<00:56:15.069> stuff<00:56:15.309> that<00:56:15.339> you<00:56:15.640> show<00:56:15.849> someone 00:56:16.260 --> 00:56:16.270 align:start position:0% now all the stuff that you show someone 00:56:16.270 --> 00:56:19.500 align:start position:0% now all the stuff that you show someone really<00:56:16.779> importantly<00:56:17.260> kid<00:56:17.559> so<00:56:18.430> we<00:56:19.150> did<00:56:19.329> this 00:56:19.500 --> 00:56:19.510 align:start position:0% really importantly kid so we did this 00:56:19.510 --> 00:56:22.529 align:start position:0% really importantly kid so we did this same<00:56:19.720> talk<00:56:19.990> in<00:56:20.140> truffle<00:56:20.470> color<00:56:20.940> so<00:56:21.940> the<00:56:22.150> link 00:56:22.529 --> 00:56:22.539 align:start position:0% same talk in truffle color so the link 00:56:22.539 --> 00:56:25.440 align:start position:0% same talk in truffle color so the link there<00:56:22.750> is<00:56:22.930> chunk<00:56:23.680> of<00:56:23.770> 2019<00:56:24.430> so<00:56:25.150> if<00:56:25.210> you've<00:56:25.329> got 00:56:25.440 --> 00:56:25.450 align:start position:0% there is chunk of 2019 so if you've got 00:56:25.450 --> 00:56:30.720 align:start position:0% there is chunk of 2019 so if you've got a<00:56:25.599> cage<00:56:25.869> or<00:56:26.170> ms<00:56:26.910> /<00:56:27.910> truffle<00:56:28.569> 2019<00:56:29.460> you've<00:56:30.460> got<00:56:30.700> a 00:56:30.720 --> 00:56:30.730 align:start position:0% a cage or ms / truffle 2019 you've got a 00:56:30.730 --> 00:56:32.640 align:start position:0% a cage or ms / truffle 2019 you've got a lot<00:56:31.119> of<00:56:31.420> the<00:56:31.690> cool<00:56:31.960> things<00:56:32.289> that<00:56:32.349> I<00:56:32.470> just 00:56:32.640 --> 00:56:32.650 align:start position:0% lot of the cool things that I just 00:56:32.650 --> 00:56:35.519 align:start position:0% lot of the cool things that I just talked<00:56:32.890> about<00:56:33.059> here<00:56:34.059> anodized<00:56:34.779> readme<00:56:35.260> file 00:56:35.519 --> 00:56:35.529 align:start position:0% talked about here anodized readme file 00:56:35.529 --> 00:56:37.920 align:start position:0% talked about here anodized readme file so<00:56:36.430> we've<00:56:36.640> got<00:56:36.880> everything<00:56:37.299> got<00:56:37.720> up 00:56:37.920 --> 00:56:37.930 align:start position:0% so we've got everything got up 00:56:37.930 --> 00:56:39.450 align:start position:0% so we've got everything got up and<00:56:38.109> four<00:56:38.319> tenets<00:56:38.710> of<00:56:38.799> law<00:56:38.950> changes 00:56:39.450 --> 00:56:39.460 align:start position:0% and four tenets of law changes 00:56:39.460 --> 00:56:43.039 align:start position:0% and four tenets of law changes development<00:56:40.150> pretty<00:56:40.869> pictures<00:56:41.289> that<00:56:41.980> you<00:56:42.069> do 00:56:43.039 --> 00:56:43.049 align:start position:0% development pretty pictures that you do 00:56:43.049 --> 00:56:46.049 align:start position:0% development pretty pictures that you do some<00:56:44.049> information<00:56:44.529> about<00:56:44.619> what<00:56:45.069> connectors 00:56:46.049 --> 00:56:46.059 align:start position:0% some information about what connectors 00:56:46.059 --> 00:56:49.140 align:start position:0% some information about what connectors are<00:56:46.589> links<00:56:47.589> to<00:56:47.619> the<00:56:47.829> vias<00:56:48.160> code<00:56:48.430> extension<00:56:49.029> or 00:56:49.140 --> 00:56:49.150 align:start position:0% are links to the vias code extension or 00:56:49.150 --> 00:56:52.640 align:start position:0% are links to the vias code extension or sad<00:56:49.359> cetera 00:56:52.640 --> 00:56:52.650 align:start position:0% 00:56:52.650 --> 00:56:56.570 align:start position:0% so<00:56:53.280> that's<00:56:53.910> the<00:56:54.090> important<00:56:54.600> work<00:56:54.720> that<00:56:55.580> now 00:56:56.570 --> 00:56:56.580 align:start position:0% so that's the important work that now 00:56:56.580 --> 00:56:59.410 align:start position:0% so that's the important work that now with<00:56:56.910> that<00:56:57.150> so<00:56:57.900> it<00:56:58.050> Microsoft<00:56:58.560> we<00:56:58.680> do<00:56:58.830> have<00:56:59.040> a 00:56:59.410 --> 00:56:59.420 align:start position:0% with that so it Microsoft we do have a 00:56:59.420 --> 00:57:03.920 align:start position:0% with that so it Microsoft we do have a three-foot<00:57:00.420> hole<00:57:00.600> settlement<00:57:02.810> placement<00:57:03.810> the 00:57:03.920 --> 00:57:03.930 align:start position:0% three-foot hole settlement placement the 00:57:03.930 --> 00:57:05.840 align:start position:0% three-foot hole settlement placement the biggest<00:57:04.380> about<00:57:04.590> their<00:57:04.710> ticket<00:57:05.070> so<00:57:05.610> you<00:57:05.700> could 00:57:05.840 --> 00:57:05.850 align:start position:0% biggest about their ticket so you could 00:57:05.850 --> 00:57:07.840 align:start position:0% biggest about their ticket so you could answer<00:57:06.090> the<00:57:06.180> basic<00:57:06.300> you<00:57:06.690> can<00:57:06.840> get<00:57:06.960> it<00:57:07.050> talk<00:57:07.260> to 00:57:07.840 --> 00:57:07.850 align:start position:0% answer the basic you can get it talk to 00:57:07.850 --> 00:57:20.750 align:start position:0% answer the basic you can get it talk to we<00:57:08.850> get<00:57:09.030> into<00:57:09.210> the<00:57:09.300> basement 00:57:20.750 --> 00:57:20.760 align:start position:0% 00:57:20.760 --> 00:57:26.710 align:start position:0% [Applause]