WEBVTT Kind: captions Language: en 00:00:05.070 --> 00:00:14.910 align:start position:0% [Music] 00:00:14.910 --> 00:00:14.920 align:start position:0% 00:00:14.920 --> 00:00:17.670 align:start position:0% [Music] 00:00:17.670 --> 00:00:17.680 align:start position:0% [Music] 00:00:17.680 --> 00:00:20.509 align:start position:0% [Music] patterns<00:00:18.039> by<00:00:18.160> the<00:00:18.279> gang<00:00:18.439> of<00:00:18.600> war<00:00:19.240> is<00:00:19.720> uh<00:00:20.119> is<00:00:20.320> is 00:00:20.509 --> 00:00:20.519 align:start position:0% patterns by the gang of war is uh is is 00:00:20.519 --> 00:00:22.910 align:start position:0% patterns by the gang of war is uh is is very<00:00:20.760> famous<00:00:21.680> and<00:00:22.080> also<00:00:22.359> outside<00:00:22.720> of<00:00:22.840> the 00:00:22.910 --> 00:00:22.920 align:start position:0% very famous and also outside of the 00:00:22.920 --> 00:00:26.029 align:start position:0% very famous and also outside of the field<00:00:23.160> of<00:00:23.359> developing<00:00:24.359> you<00:00:24.560> have<00:00:24.760> patterns<00:00:25.439> so 00:00:26.029 --> 00:00:26.039 align:start position:0% field of developing you have patterns so 00:00:26.039 --> 00:00:28.230 align:start position:0% field of developing you have patterns so if<00:00:26.119> you<00:00:26.240> want<00:00:26.400> to<00:00:26.920> if<00:00:27.000> you<00:00:27.119> want<00:00:27.199> to<00:00:27.359> knit<00:00:28.000> a 00:00:28.230 --> 00:00:28.240 align:start position:0% if you want to if you want to knit a 00:00:28.240 --> 00:00:30.269 align:start position:0% if you want to if you want to knit a Celtic<00:00:28.920> pillow<00:00:29.519> I<00:00:29.599> wouldn't<00:00:29.840> know<00:00:30.039> where<00:00:30.160> to 00:00:30.269 --> 00:00:30.279 align:start position:0% Celtic pillow I wouldn't know where to 00:00:30.279 --> 00:00:32.109 align:start position:0% Celtic pillow I wouldn't know where to start<00:00:30.480> so<00:00:30.640> first<00:00:30.800> I<00:00:30.960> Google<00:00:31.519> and<00:00:31.640> then<00:00:31.759> I<00:00:31.920> get 00:00:32.109 --> 00:00:32.119 align:start position:0% start so first I Google and then I get 00:00:32.119 --> 00:00:33.950 align:start position:0% start so first I Google and then I get this<00:00:32.279> kind<00:00:32.439> of<00:00:32.599> stuff<00:00:33.320> I<00:00:33.440> I'm<00:00:33.559> not<00:00:33.680> sure<00:00:33.879> what 00:00:33.950 --> 00:00:33.960 align:start position:0% this kind of stuff I I'm not sure what 00:00:33.960 --> 00:00:35.990 align:start position:0% this kind of stuff I I'm not sure what it<00:00:34.079> is<00:00:34.239> it<00:00:34.320> looks<00:00:34.559> like<00:00:34.840> brain<00:00:35.120> F<00:00:35.480> codes<00:00:35.879> but 00:00:35.990 --> 00:00:36.000 align:start position:0% it is it looks like brain F codes but 00:00:36.000 --> 00:00:38.110 align:start position:0% it is it looks like brain F codes but probably<00:00:36.239> it<00:00:36.360> tells<00:00:36.600> me<00:00:36.840> how<00:00:37.000> to<00:00:37.440> uh<00:00:37.800> how<00:00:37.960> to 00:00:38.110 --> 00:00:38.120 align:start position:0% probably it tells me how to uh how to 00:00:38.120 --> 00:00:39.190 align:start position:0% probably it tells me how to uh how to knit<00:00:38.360> a 00:00:39.190 --> 00:00:39.200 align:start position:0% knit a 00:00:39.200 --> 00:00:43.029 align:start position:0% knit a pillow<00:00:40.200> so<00:00:41.120> what<00:00:41.280> what<00:00:41.360> is<00:00:41.480> a<00:00:41.879> pattern<00:00:42.879> a 00:00:43.029 --> 00:00:43.039 align:start position:0% pillow so what what is a pattern a 00:00:43.039 --> 00:00:46.709 align:start position:0% pillow so what what is a pattern a pattern<00:00:43.480> is<00:00:43.600> a<00:00:44.280> is<00:00:44.399> a<00:00:44.680> reusable<00:00:45.320> solution<00:00:46.120> for 00:00:46.709 --> 00:00:46.719 align:start position:0% pattern is a is a reusable solution for 00:00:46.719 --> 00:00:49.350 align:start position:0% pattern is a is a reusable solution for common<00:00:47.079> occurring<00:00:47.559> problems<00:00:48.559> um<00:00:49.039> that<00:00:49.199> you 00:00:49.350 --> 00:00:49.360 align:start position:0% common occurring problems um that you 00:00:49.360 --> 00:00:51.869 align:start position:0% common occurring problems um that you can<00:00:49.600> that<00:00:49.719> you<00:00:49.800> can<00:00:50.000> apply<00:00:50.719> it's<00:00:50.879> not<00:00:51.239> some 00:00:51.869 --> 00:00:51.879 align:start position:0% can that you can apply it's not some 00:00:51.879 --> 00:00:53.670 align:start position:0% can that you can apply it's not some boilerplate<00:00:52.760> piece<00:00:52.920> of<00:00:53.079> code<00:00:53.280> that<00:00:53.399> you<00:00:53.520> just 00:00:53.670 --> 00:00:53.680 align:start position:0% boilerplate piece of code that you just 00:00:53.680 --> 00:00:55.069 align:start position:0% boilerplate piece of code that you just copy<00:00:54.039> paste<00:00:54.239> and<00:00:54.320> you're<00:00:54.440> done<00:00:54.640> with<00:00:54.800> it<00:00:54.920> you 00:00:55.069 --> 00:00:55.079 align:start position:0% copy paste and you're done with it you 00:00:55.079 --> 00:00:57.069 align:start position:0% copy paste and you're done with it you apply<00:00:55.320> it<00:00:55.440> to<00:00:55.559> your<00:00:55.680> own<00:00:55.840> codex<00:00:56.359> but<00:00:56.480> you<00:00:56.920> you 00:00:57.069 --> 00:00:57.079 align:start position:0% apply it to your own codex but you you 00:00:57.079 --> 00:00:59.310 align:start position:0% apply it to your own codex but you you try<00:00:57.280> to<00:00:57.440> reuse<00:00:57.800> it<00:00:57.960> you<00:00:58.120> try<00:00:58.320> to<00:00:58.800> to<00:00:58.920> see<00:00:59.160> when 00:00:59.310 --> 00:00:59.320 align:start position:0% try to reuse it you try to to see when 00:00:59.320 --> 00:01:00.750 align:start position:0% try to reuse it you try to to see when does<00:00:59.440> it<00:00:59.559> make<00:00:59.719> sense<00:01:00.160> when<00:01:00.280> does<00:01:00.399> it<00:01:00.559> make 00:01:00.750 --> 00:01:00.760 align:start position:0% does it make sense when does it make 00:01:00.760 --> 00:01:03.990 align:start position:0% does it make sense when does it make sense<00:01:01.680> and<00:01:02.440> in<00:01:02.680> the<00:01:03.079> the<00:01:03.359> the<00:01:03.559> the<00:01:03.680> pattern 00:01:03.990 --> 00:01:04.000 align:start position:0% sense and in the the the the pattern 00:01:04.000 --> 00:01:05.870 align:start position:0% sense and in the the the the pattern description<00:01:04.439> the<00:01:04.559> pattern<00:01:04.879> language<00:01:05.680> we 00:01:05.870 --> 00:01:05.880 align:start position:0% description the pattern language we 00:01:05.880 --> 00:01:08.230 align:start position:0% description the pattern language we mention<00:01:06.880> when<00:01:07.040> is<00:01:07.200> the<00:01:07.360> good<00:01:07.640> problem<00:01:08.040> to 00:01:08.230 --> 00:01:08.240 align:start position:0% mention when is the good problem to 00:01:08.240 --> 00:01:09.749 align:start position:0% mention when is the good problem to apply<00:01:08.520> this<00:01:08.720> pattern<00:01:09.040> when<00:01:09.200> you<00:01:09.280> shouldn't<00:01:09.560> do 00:01:09.749 --> 00:01:09.759 align:start position:0% apply this pattern when you shouldn't do 00:01:09.759 --> 00:01:11.429 align:start position:0% apply this pattern when you shouldn't do it<00:01:09.920> and<00:01:10.040> if<00:01:10.159> you're<00:01:10.360> applying<00:01:10.720> it<00:01:11.159> what<00:01:11.280> are 00:01:11.429 --> 00:01:11.439 align:start position:0% it and if you're applying it what are 00:01:11.439 --> 00:01:13.550 align:start position:0% it and if you're applying it what are the<00:01:11.600> considerations<00:01:12.280> and<00:01:12.439> of<00:01:12.600> course<00:01:13.240> some 00:01:13.550 --> 00:01:13.560 align:start position:0% the considerations and of course some 00:01:13.560 --> 00:01:14.749 align:start position:0% the considerations and of course some some<00:01:13.759> code 00:01:14.749 --> 00:01:14.759 align:start position:0% some code 00:01:14.759 --> 00:01:17.950 align:start position:0% some code examples<00:01:15.759> um<00:01:16.640> yeah<00:01:16.799> Microsoft<00:01:17.280> guys<00:01:17.759> with 00:01:17.950 --> 00:01:17.960 align:start position:0% examples um yeah Microsoft guys with 00:01:17.960 --> 00:01:19.749 align:start position:0% examples um yeah Microsoft guys with their<00:01:18.360> their<00:01:18.720> Azure<00:01:19.040> Cloud<00:01:19.400> they<00:01:19.560> also 00:01:19.749 --> 00:01:19.759 align:start position:0% their their Azure Cloud they also 00:01:19.759 --> 00:01:21.469 align:start position:0% their their Azure Cloud they also released<00:01:20.119> all<00:01:20.280> kinds<00:01:20.479> of<00:01:20.640> patterns<00:01:21.000> so<00:01:21.200> in<00:01:21.320> all 00:01:21.469 --> 00:01:21.479 align:start position:0% released all kinds of patterns so in all 00:01:21.479 --> 00:01:23.670 align:start position:0% released all kinds of patterns so in all kinds<00:01:21.680> of<00:01:22.000> software<00:01:22.439> engineering<00:01:22.880> Fields<00:01:23.560> you 00:01:23.670 --> 00:01:23.680 align:start position:0% kinds of software engineering Fields you 00:01:23.680 --> 00:01:26.149 align:start position:0% kinds of software engineering Fields you have<00:01:23.840> this<00:01:24.280> pattern<00:01:24.640> system<00:01:25.439> so<00:01:25.720> probably<00:01:26.000> the 00:01:26.149 --> 00:01:26.159 align:start position:0% have this pattern system so probably the 00:01:26.159 --> 00:01:27.870 align:start position:0% have this pattern system so probably the next<00:01:26.400> version<00:01:26.680> of<00:01:26.840> this<00:01:27.000> slides<00:01:27.520> we'll<00:01:27.720> have 00:01:27.870 --> 00:01:27.880 align:start position:0% next version of this slides we'll have 00:01:27.880 --> 00:01:30.710 align:start position:0% next version of this slides we'll have the<00:01:28.000> blockchain<00:01:28.600> pattern<00:01:29.320> in<00:01:29.520> here<00:01:29.759> at<00:01:29.960> as 00:01:30.710 --> 00:01:30.720 align:start position:0% the blockchain pattern in here at as 00:01:30.720 --> 00:01:33.149 align:start position:0% the blockchain pattern in here at as well<00:01:31.720> so<00:01:32.320> when<00:01:32.479> when<00:01:32.640> looking<00:01:32.880> at<00:01:33.000> the 00:01:33.149 --> 00:01:33.159 align:start position:0% well so when when looking at the 00:01:33.159 --> 00:01:35.350 align:start position:0% well so when when looking at the patterns<00:01:33.640> we<00:01:33.960> discovered<00:01:34.320> three<00:01:34.560> areas<00:01:35.240> we 00:01:35.350 --> 00:01:35.360 align:start position:0% patterns we discovered three areas we 00:01:35.360 --> 00:01:37.990 align:start position:0% patterns we discovered three areas we have<00:01:35.680> data<00:01:36.079> patterns<00:01:36.960> transaction<00:01:37.520> and<00:01:37.680> value 00:01:37.990 --> 00:01:38.000 align:start position:0% have data patterns transaction and value 00:01:38.000 --> 00:01:40.230 align:start position:0% have data patterns transaction and value patterns<00:01:38.840> and<00:01:38.960> we<00:01:39.119> have<00:01:39.399> action<00:01:39.680> and<00:01:39.880> control 00:01:40.230 --> 00:01:40.240 align:start position:0% patterns and we have action and control 00:01:40.240 --> 00:01:42.069 align:start position:0% patterns and we have action and control patterns<00:01:40.759> probably<00:01:41.079> there<00:01:41.159> are<00:01:41.600> much<00:01:41.799> more 00:01:42.069 --> 00:01:42.079 align:start position:0% patterns probably there are much more 00:01:42.079 --> 00:01:43.590 align:start position:0% patterns probably there are much more different<00:01:42.439> categories<00:01:43.000> but<00:01:43.159> these<00:01:43.280> are<00:01:43.439> the 00:01:43.590 --> 00:01:43.600 align:start position:0% different categories but these are the 00:01:43.600 --> 00:01:46.230 align:start position:0% different categories but these are the three<00:01:44.000> distinctions<00:01:44.600> that<00:01:44.759> we<00:01:44.960> came<00:01:45.159> up<00:01:45.360> with 00:01:46.230 --> 00:01:46.240 align:start position:0% three distinctions that we came up with 00:01:46.240 --> 00:01:48.910 align:start position:0% three distinctions that we came up with um<00:01:46.920> and<00:01:47.159> I'm<00:01:47.280> going<00:01:47.439> to<00:01:47.600> mention<00:01:48.159> six<00:01:48.479> examples 00:01:48.910 --> 00:01:48.920 align:start position:0% um and I'm going to mention six examples 00:01:48.920 --> 00:01:51.069 align:start position:0% um and I'm going to mention six examples from<00:01:49.159> this<00:01:49.439> uh<00:01:49.600> this<00:01:49.759> set<00:01:50.680> actually<00:01:50.960> this 00:01:51.069 --> 00:01:51.079 align:start position:0% from this uh this set actually this 00:01:51.079 --> 00:01:54.030 align:start position:0% from this uh this set actually this morning<00:01:51.960> we<00:01:52.119> also<00:01:52.880> we<00:01:53.040> we've<00:01:53.200> seen<00:01:53.399> the<00:01:53.600> fan<00:01:53.880> in 00:01:54.030 --> 00:01:54.040 align:start position:0% morning we also we we've seen the fan in 00:01:54.040 --> 00:01:56.109 align:start position:0% morning we also we we've seen the fan in and<00:01:54.159> fan<00:01:54.360> out<00:01:54.920> pattern<00:01:55.240> from<00:01:55.399> the<00:01:55.600> Block<00:01:55.840> apps 00:01:56.109 --> 00:01:56.119 align:start position:0% and fan out pattern from the Block apps 00:01:56.119 --> 00:01:58.429 align:start position:0% and fan out pattern from the Block apps demo<00:01:56.799> we<00:01:56.880> have<00:01:57.039> seen<00:01:57.360> the<00:01:57.479> the<00:01:57.560> escrow<00:01:58.079> example 00:01:58.429 --> 00:01:58.439 align:start position:0% demo we have seen the the escrow example 00:01:58.439 --> 00:02:00.389 align:start position:0% demo we have seen the the escrow example earlier<00:01:58.759> so<00:01:58.920> already<00:01:59.240> during<00:01:59.479> this<00:01:59.640> day<00:02:00.280> you 00:02:00.389 --> 00:02:00.399 align:start position:0% earlier so already during this day you 00:02:00.399 --> 00:02:01.789 align:start position:0% earlier so already during this day you have<00:02:00.640> me<00:02:00.840> you<00:02:00.920> have<00:02:01.119> witnessed<00:02:01.479> a<00:02:01.560> couple 00:02:01.789 --> 00:02:01.799 align:start position:0% have me you have witnessed a couple 00:02:01.799 --> 00:02:04.429 align:start position:0% have me you have witnessed a couple patterns<00:02:02.240> without<00:02:02.600> even<00:02:02.960> realizing<00:02:03.479> it<00:02:04.280> so 00:02:04.429 --> 00:02:04.439 align:start position:0% patterns without even realizing it so 00:02:04.439 --> 00:02:07.149 align:start position:0% patterns without even realizing it so for<00:02:04.600> each<00:02:04.759> of<00:02:04.880> these<00:02:05.039> patterns<00:02:05.479> we'll<00:02:06.159> mention 00:02:07.149 --> 00:02:07.159 align:start position:0% for each of these patterns we'll mention 00:02:07.159 --> 00:02:09.150 align:start position:0% for each of these patterns we'll mention well<00:02:07.439> of<00:02:07.520> course<00:02:07.640> the<00:02:07.759> name<00:02:08.080> of<00:02:08.239> it<00:02:08.959> a 00:02:09.150 --> 00:02:09.160 align:start position:0% well of course the name of it a 00:02:09.160 --> 00:02:11.510 align:start position:0% well of course the name of it a definition<00:02:09.599> of<00:02:09.720> the<00:02:09.920> problem<00:02:10.319> so<00:02:10.800> when<00:02:11.319> when 00:02:11.510 --> 00:02:11.520 align:start position:0% definition of the problem so when when 00:02:11.520 --> 00:02:13.790 align:start position:0% definition of the problem so when when can<00:02:11.640> you<00:02:11.800> apply<00:02:12.120> this<00:02:12.319> pattern<00:02:13.040> and<00:02:13.160> then<00:02:13.680> if 00:02:13.790 --> 00:02:13.800 align:start position:0% can you apply this pattern and then if 00:02:13.800 --> 00:02:15.910 align:start position:0% can you apply this pattern and then if you're<00:02:13.959> going<00:02:14.120> to<00:02:14.319> apply<00:02:14.599> it<00:02:15.400> what<00:02:15.560> kind<00:02:15.720> of 00:02:15.910 --> 00:02:15.920 align:start position:0% you're going to apply it what kind of 00:02:15.920 --> 00:02:17.710 align:start position:0% you're going to apply it what kind of context<00:02:16.360> what<00:02:16.519> kind<00:02:16.680> of<00:02:16.879> considerations<00:02:17.599> what 00:02:17.710 --> 00:02:17.720 align:start position:0% context what kind of considerations what 00:02:17.720 --> 00:02:19.790 align:start position:0% context what kind of considerations what kind<00:02:17.879> of<00:02:18.040> constraints<00:02:18.560> are<00:02:18.800> there<00:02:19.280> to<00:02:19.599> uh<00:02:19.680> to 00:02:19.790 --> 00:02:19.800 align:start position:0% kind of constraints are there to uh to 00:02:19.800 --> 00:02:20.830 align:start position:0% kind of constraints are there to uh to be<00:02:19.959> assure 00:02:20.830 --> 00:02:20.840 align:start position:0% be assure 00:02:20.840 --> 00:02:24.790 align:start position:0% be assure of<00:02:21.840> followed<00:02:22.280> by<00:02:22.879> an<00:02:23.080> actual<00:02:23.400> solution<00:02:24.120> of<00:02:24.640> uh 00:02:24.790 --> 00:02:24.800 align:start position:0% of followed by an actual solution of uh 00:02:24.800 --> 00:02:26.710 align:start position:0% of followed by an actual solution of uh of<00:02:24.959> this<00:02:25.120> pattern<00:02:25.680> and<00:02:25.840> a<00:02:25.959> couple<00:02:26.239> examples 00:02:26.710 --> 00:02:26.720 align:start position:0% of this pattern and a couple examples 00:02:26.720 --> 00:02:28.869 align:start position:0% of this pattern and a couple examples out<00:02:26.879> of<00:02:27.080> the<00:02:27.519> all<00:02:27.760> the<00:02:27.879> code<00:02:28.200> that<00:02:28.280> is<00:02:28.440> publicly 00:02:28.869 --> 00:02:28.879 align:start position:0% out of the all the code that is publicly 00:02:28.879 --> 00:02:31.990 align:start position:0% out of the all the code that is publicly available<00:02:29.400> on<00:02:30.040> getp<00:02:30.360> already<00:02:31.160> and<00:02:31.640> you<00:02:31.760> see 00:02:31.990 --> 00:02:32.000 align:start position:0% available on getp already and you see 00:02:32.000 --> 00:02:33.830 align:start position:0% available on getp already and you see these<00:02:32.160> patterns<00:02:32.519> are<00:02:32.760> quite<00:02:33.000> often<00:02:33.480> related 00:02:33.830 --> 00:02:33.840 align:start position:0% these patterns are quite often related 00:02:33.840 --> 00:02:35.670 align:start position:0% these patterns are quite often related to<00:02:34.000> each<00:02:34.160> other<00:02:34.360> so<00:02:34.519> if<00:02:34.599> you<00:02:34.680> use<00:02:34.920> one<00:02:35.160> pattern 00:02:35.670 --> 00:02:35.680 align:start position:0% to each other so if you use one pattern 00:02:35.680 --> 00:02:36.990 align:start position:0% to each other so if you use one pattern you<00:02:35.840> might<00:02:36.000> as<00:02:36.120> well<00:02:36.319> consider<00:02:36.680> another 00:02:36.990 --> 00:02:37.000 align:start position:0% you might as well consider another 00:02:37.000 --> 00:02:39.309 align:start position:0% you might as well consider another pattern<00:02:37.319> or<00:02:37.480> even<00:02:37.920> use<00:02:38.200> them<00:02:38.599> in<00:02:38.800> combination 00:02:39.309 --> 00:02:39.319 align:start position:0% pattern or even use them in combination 00:02:39.319 --> 00:02:42.470 align:start position:0% pattern or even use them in combination of<00:02:39.480> each 00:02:42.470 --> 00:02:42.480 align:start position:0% 00:02:42.480 --> 00:02:43.990 align:start position:0% other 00:02:43.990 --> 00:02:44.000 align:start position:0% other 00:02:44.000 --> 00:02:46.710 align:start position:0% other so<00:02:45.000> first<00:02:45.159> of<00:02:45.280> all<00:02:45.480> the<00:02:45.640> the<00:02:45.760> data<00:02:46.080> patterns 00:02:46.710 --> 00:02:46.720 align:start position:0% so first of all the the data patterns 00:02:46.720 --> 00:02:48.910 align:start position:0% so first of all the the data patterns two<00:02:47.239> two 00:02:48.910 --> 00:02:48.920 align:start position:0% two two 00:02:48.920 --> 00:02:51.509 align:start position:0% two two examples<00:02:49.920> the<00:02:50.080> first<00:02:50.280> one<00:02:50.480> is<00:02:50.720> the<00:02:50.959> the<00:02:51.080> name 00:02:51.509 --> 00:02:51.519 align:start position:0% examples the first one is the the name 00:02:51.519 --> 00:02:54.910 align:start position:0% examples the first one is the the name registry<00:02:52.519> it's<00:02:52.920> um<00:02:53.560> so<00:02:53.879> you<00:02:54.040> you<00:02:54.159> need<00:02:54.360> this<00:02:54.599> if 00:02:54.910 --> 00:02:54.920 align:start position:0% registry it's um so you you need this if 00:02:54.920 --> 00:02:57.910 align:start position:0% registry it's um so you you need this if you're<00:02:55.920> looking<00:02:56.280> for<00:02:56.720> for<00:02:56.879> a<00:02:57.040> human<00:02:57.400> readable 00:02:57.910 --> 00:02:57.920 align:start position:0% you're looking for for a human readable 00:02:57.920 --> 00:03:00.790 align:start position:0% you're looking for for a human readable name<00:02:58.440> for<00:02:58.720> a<00:02:58.959> ethereum<00:02:59.480> address 00:03:00.790 --> 00:03:00.800 align:start position:0% name for a ethereum address 00:03:00.800 --> 00:03:02.550 align:start position:0% name for a ethereum address um<00:03:01.200> and<00:03:01.319> you<00:03:01.440> might<00:03:01.599> need<00:03:01.760> this<00:03:01.920> human<00:03:02.200> real 00:03:02.550 --> 00:03:02.560 align:start position:0% um and you might need this human real 00:03:02.560 --> 00:03:03.990 align:start position:0% um and you might need this human real name<00:03:02.800> because<00:03:02.959> you<00:03:03.040> want<00:03:03.159> to<00:03:03.319> display<00:03:03.720> it<00:03:03.879> in 00:03:03.990 --> 00:03:04.000 align:start position:0% name because you want to display it in 00:03:04.000 --> 00:03:05.789 align:start position:0% name because you want to display it in your<00:03:04.159> user<00:03:04.400> interface<00:03:05.280> maybe<00:03:05.480> you<00:03:05.560> have<00:03:05.680> a 00:03:05.789 --> 00:03:05.799 align:start position:0% your user interface maybe you have a 00:03:05.799 --> 00:03:07.630 align:start position:0% your user interface maybe you have a wallet<00:03:06.120> application<00:03:06.760> and<00:03:06.840> you<00:03:06.959> want<00:03:07.040> to<00:03:07.200> show 00:03:07.630 --> 00:03:07.640 align:start position:0% wallet application and you want to show 00:03:07.640 --> 00:03:08.869 align:start position:0% wallet application and you want to show the<00:03:07.840> person<00:03:08.080> that<00:03:08.200> you're<00:03:08.319> transferring 00:03:08.869 --> 00:03:08.879 align:start position:0% the person that you're transferring 00:03:08.879 --> 00:03:11.350 align:start position:0% the person that you're transferring something<00:03:09.360> to<00:03:10.120> or<00:03:10.239> you<00:03:10.360> have<00:03:10.480> a<00:03:10.640> game<00:03:11.159> and<00:03:11.239> you 00:03:11.350 --> 00:03:11.360 align:start position:0% something to or you have a game and you 00:03:11.360 --> 00:03:12.949 align:start position:0% something to or you have a game and you want<00:03:11.440> to<00:03:11.519> show<00:03:11.720> the<00:03:11.879> nickname<00:03:12.319> of<00:03:12.480> the<00:03:12.640> person 00:03:12.949 --> 00:03:12.959 align:start position:0% want to show the nickname of the person 00:03:12.959 --> 00:03:15.229 align:start position:0% want to show the nickname of the person that<00:03:13.159> was<00:03:13.560> uh<00:03:13.720> just<00:03:14.000> just<00:03:14.159> winning<00:03:14.760> your<00:03:15.000> your 00:03:15.229 --> 00:03:15.239 align:start position:0% that was uh just just winning your your 00:03:15.239 --> 00:03:18.990 align:start position:0% that was uh just just winning your your contest<00:03:16.239> or<00:03:16.720> because<00:03:17.040> your<00:03:17.799> dep<00:03:18.400> consists<00:03:18.760> of 00:03:18.990 --> 00:03:19.000 align:start position:0% contest or because your dep consists of 00:03:19.000 --> 00:03:21.350 align:start position:0% contest or because your dep consists of a<00:03:20.000> a<00:03:20.159> cluster<00:03:20.599> of<00:03:20.760> contracts<00:03:21.159> that<00:03:21.239> are 00:03:21.350 --> 00:03:21.360 align:start position:0% a a cluster of contracts that are 00:03:21.360 --> 00:03:22.630 align:start position:0% a a cluster of contracts that are related<00:03:21.680> with<00:03:21.799> each<00:03:21.959> other<00:03:22.200> you<00:03:22.280> want<00:03:22.400> to<00:03:22.519> make 00:03:22.630 --> 00:03:22.640 align:start position:0% related with each other you want to make 00:03:22.640 --> 00:03:24.270 align:start position:0% related with each other you want to make a<00:03:22.799> reference<00:03:23.159> from<00:03:23.400> one<00:03:23.560> contract<00:03:24.000> to<00:03:24.159> the 00:03:24.270 --> 00:03:24.280 align:start position:0% a reference from one contract to the 00:03:24.280 --> 00:03:27.229 align:start position:0% a reference from one contract to the other<00:03:24.879> but<00:03:25.200> this<00:03:25.519> relationship<00:03:26.080> isn't<00:03:26.360> known 00:03:27.229 --> 00:03:27.239 align:start position:0% other but this relationship isn't known 00:03:27.239 --> 00:03:28.910 align:start position:0% other but this relationship isn't known uh<00:03:27.360> up<00:03:27.599> front<00:03:27.840> so<00:03:27.959> you<00:03:28.080> want<00:03:28.159> to<00:03:28.360> refer<00:03:28.680> to<00:03:28.840> the 00:03:28.910 --> 00:03:28.920 align:start position:0% uh up front so you want to refer to the 00:03:28.920 --> 00:03:30.589 align:start position:0% uh up front so you want to refer to the other<00:03:29.120> contract<00:03:29.480> by<00:03:29.799> name<00:03:30.200> instead<00:03:30.480> of 00:03:30.589 --> 00:03:30.599 align:start position:0% other contract by name instead of 00:03:30.599 --> 00:03:33.509 align:start position:0% other contract by name instead of hardcoding<00:03:31.200> the<00:03:31.319> address<00:03:32.159> in<00:03:32.319> your<00:03:32.879> your 00:03:33.509 --> 00:03:33.519 align:start position:0% hardcoding the address in your your 00:03:33.519 --> 00:03:35.990 align:start position:0% hardcoding the address in your your contract<00:03:34.519> um<00:03:35.040> and<00:03:35.200> of<00:03:35.319> course<00:03:35.519> that<00:03:35.640> has<00:03:35.799> the 00:03:35.990 --> 00:03:36.000 align:start position:0% contract um and of course that has the 00:03:36.000 --> 00:03:38.710 align:start position:0% contract um and of course that has the advantage<00:03:37.000> that<00:03:37.480> if<00:03:37.640> you<00:03:38.040> update<00:03:38.360> the<00:03:38.480> name 00:03:38.710 --> 00:03:38.720 align:start position:0% advantage that if you update the name 00:03:38.720 --> 00:03:41.670 align:start position:0% advantage that if you update the name registry<00:03:39.439> you<00:03:39.599> can<00:03:39.799> also<00:03:40.080> update<00:03:40.720> the<00:03:40.879> code<00:03:41.519> of 00:03:41.670 --> 00:03:41.680 align:start position:0% registry you can also update the code of 00:03:41.680 --> 00:03:43.990 align:start position:0% registry you can also update the code of your<00:03:42.040> of<00:03:42.159> your<00:03:42.319> code 00:03:43.990 --> 00:03:44.000 align:start position:0% your of your code 00:03:44.000 --> 00:03:48.149 align:start position:0% your of your code construct<00:03:45.000> um<00:03:45.799> and<00:03:46.280> you<00:03:46.400> can<00:03:46.599> e<00:03:46.959> even<00:03:47.200> apply 00:03:48.149 --> 00:03:48.159 align:start position:0% construct um and you can e even apply 00:03:48.159 --> 00:03:49.670 align:start position:0% construct um and you can e even apply hierarchic<00:03:48.720> patterns<00:03:49.159> here<00:03:49.319> where<00:03:49.439> you<00:03:49.519> get 00:03:49.670 --> 00:03:49.680 align:start position:0% hierarchic patterns here where you get 00:03:49.680 --> 00:03:51.990 align:start position:0% hierarchic patterns here where you get some<00:03:49.840> kind<00:03:50.000> of<00:03:50.439> subdomain<00:03:51.120> registry<00:03:51.680> so<00:03:51.879> you 00:03:51.990 --> 00:03:52.000 align:start position:0% some kind of subdomain registry so you 00:03:52.000 --> 00:03:54.069 align:start position:0% some kind of subdomain registry so you can<00:03:52.159> register<00:03:52.760> uh<00:03:53.360> you<00:03:53.480> can<00:03:53.640> appoint<00:03:53.920> a 00:03:54.069 --> 00:03:54.079 align:start position:0% can register uh you can appoint a 00:03:54.079 --> 00:03:56.470 align:start position:0% can register uh you can appoint a registry<00:03:54.519> for<00:03:54.760> a<00:03:54.959> for<00:03:55.120> a<00:03:55.280> domain<00:03:55.959> and<00:03:56.079> then<00:03:56.239> for 00:03:56.470 --> 00:03:56.480 align:start position:0% registry for a for a domain and then for 00:03:56.480 --> 00:03:59.030 align:start position:0% registry for a for a domain and then for every<00:03:57.200> I<00:03:57.280> don't<00:03:57.439> know<00:03:57.680> for<00:03:57.879> every<00:03:58.120> household 00:03:59.030 --> 00:03:59.040 align:start position:0% every I don't know for every household 00:03:59.040 --> 00:04:01.589 align:start position:0% every I don't know for every household within<00:03:59.480> within<00:03:59.840> in<00:03:59.920> an<00:04:00.079> area<00:04:00.680> there<00:04:00.840> would<00:04:01.000> be 00:04:01.589 --> 00:04:01.599 align:start position:0% within within in an area there would be 00:04:01.599 --> 00:04:03.270 align:start position:0% within within in an area there would be another<00:04:01.959> reference<00:04:02.319> to<00:04:02.519> another<00:04:03.000> name 00:04:03.270 --> 00:04:03.280 align:start position:0% another reference to another name 00:04:03.280 --> 00:04:05.190 align:start position:0% another reference to another name registry<00:04:04.000> for<00:04:04.239> the<00:04:04.480> individual<00:04:04.920> people 00:04:05.190 --> 00:04:05.200 align:start position:0% registry for the individual people 00:04:05.200 --> 00:04:06.949 align:start position:0% registry for the individual people living 00:04:06.949 --> 00:04:06.959 align:start position:0% living 00:04:06.959 --> 00:04:09.350 align:start position:0% living there<00:04:07.959> of<00:04:08.120> course<00:04:08.480> there's<00:04:08.680> some<00:04:08.879> issues<00:04:09.159> with 00:04:09.350 --> 00:04:09.360 align:start position:0% there of course there's some issues with 00:04:09.360 --> 00:04:11.789 align:start position:0% there of course there's some issues with this<00:04:10.239> uh<00:04:10.360> you<00:04:10.480> have<00:04:10.959> the<00:04:11.079> traditional<00:04:11.519> kind<00:04:11.680> of 00:04:11.789 --> 00:04:11.799 align:start position:0% this uh you have the traditional kind of 00:04:11.799 --> 00:04:13.149 align:start position:0% this uh you have the traditional kind of problems<00:04:12.120> that<00:04:12.239> you're<00:04:12.360> also<00:04:12.519> seeing<00:04:12.840> in<00:04:13.000> the 00:04:13.149 --> 00:04:13.159 align:start position:0% problems that you're also seeing in the 00:04:13.159 --> 00:04:15.990 align:start position:0% problems that you're also seeing in the the<00:04:13.319> DNS<00:04:14.319> uh<00:04:14.400> name<00:04:14.720> registry<00:04:15.560> so<00:04:15.760> you<00:04:15.840> have 00:04:15.990 --> 00:04:16.000 align:start position:0% the DNS uh name registry so you have 00:04:16.000 --> 00:04:18.909 align:start position:0% the DNS uh name registry so you have this<00:04:16.440> name<00:04:16.720> squatting<00:04:17.400> potential<00:04:18.400> um<00:04:18.759> what 00:04:18.909 --> 00:04:18.919 align:start position:0% this name squatting potential um what 00:04:18.919 --> 00:04:20.590 align:start position:0% this name squatting potential um what happens<00:04:19.239> if<00:04:19.320> you<00:04:19.479> lose<00:04:19.680> your<00:04:19.880> key<00:04:20.239> is<00:04:20.400> this 00:04:20.590 --> 00:04:20.600 align:start position:0% happens if you lose your key is this 00:04:20.600 --> 00:04:22.870 align:start position:0% happens if you lose your key is this name<00:04:21.160> going<00:04:21.320> to<00:04:21.440> be<00:04:21.600> lost<00:04:22.199> and<00:04:22.360> we're<00:04:22.520> going<00:04:22.680> to 00:04:22.870 --> 00:04:22.880 align:start position:0% name going to be lost and we're going to 00:04:22.880 --> 00:04:25.230 align:start position:0% name going to be lost and we're going to expire<00:04:23.360> it<00:04:23.919> maybe<00:04:24.120> you<00:04:24.199> can<00:04:24.440> out<00:04:24.720> bid<00:04:24.919> somebody 00:04:25.230 --> 00:04:25.240 align:start position:0% expire it maybe you can out bid somebody 00:04:25.240 --> 00:04:27.150 align:start position:0% expire it maybe you can out bid somebody else<00:04:25.400> so<00:04:25.560> there's<00:04:25.720> all<00:04:25.919> these<00:04:26.479> complex<00:04:26.919> things 00:04:27.150 --> 00:04:27.160 align:start position:0% else so there's all these complex things 00:04:27.160 --> 00:04:30.150 align:start position:0% else so there's all these complex things to<00:04:27.479> to<00:04:27.639> think<00:04:27.840> of<00:04:28.320> as<00:04:28.479> well 00:04:30.150 --> 00:04:30.160 align:start position:0% to to think of as well 00:04:30.160 --> 00:04:32.749 align:start position:0% to to think of as well so<00:04:30.440> a<00:04:30.600> solution<00:04:31.000> here<00:04:31.240> is<00:04:31.360> to<00:04:31.560> create<00:04:32.360> uh<00:04:32.600> a 00:04:32.749 --> 00:04:32.759 align:start position:0% so a solution here is to create uh a 00:04:32.759 --> 00:04:34.749 align:start position:0% so a solution here is to create uh a contract<00:04:33.160> a<00:04:33.320> registry<00:04:34.320> and<00:04:34.440> this<00:04:34.600> could 00:04:34.749 --> 00:04:34.759 align:start position:0% contract a registry and this could 00:04:34.759 --> 00:04:36.710 align:start position:0% contract a registry and this could either<00:04:34.960> be<00:04:35.080> a<00:04:35.199> global<00:04:35.560> one<00:04:35.919> that<00:04:36.039> you<00:04:36.160> use<00:04:36.560> in 00:04:36.710 --> 00:04:36.720 align:start position:0% either be a global one that you use in 00:04:36.720 --> 00:04:38.469 align:start position:0% either be a global one that you use in all<00:04:36.880> your<00:04:37.240> ethereum<00:04:37.720> applications<00:04:38.240> or<00:04:38.360> it 00:04:38.469 --> 00:04:38.479 align:start position:0% all your ethereum applications or it 00:04:38.479 --> 00:04:40.870 align:start position:0% all your ethereum applications or it could<00:04:38.600> be<00:04:38.800> one<00:04:39.160> specific<00:04:39.919> for<00:04:40.120> your<00:04:40.360> context 00:04:40.870 --> 00:04:40.880 align:start position:0% could be one specific for your context 00:04:40.880 --> 00:04:43.550 align:start position:0% could be one specific for your context or<00:04:41.000> for<00:04:41.160> your<00:04:41.440> application<00:04:42.440> and<00:04:42.560> it<00:04:42.720> has<00:04:42.880> a<00:04:43.360> a 00:04:43.550 --> 00:04:43.560 align:start position:0% or for your application and it has a a 00:04:43.560 --> 00:04:45.950 align:start position:0% or for your application and it has a a reference<00:04:44.560> from<00:04:44.759> a<00:04:44.960> from<00:04:45.080> a<00:04:45.240> name<00:04:45.680> to<00:04:45.800> an 00:04:45.950 --> 00:04:45.960 align:start position:0% reference from a from a name to an 00:04:45.960 --> 00:04:47.909 align:start position:0% reference from a from a name to an address<00:04:46.680> it's<00:04:46.840> just<00:04:46.960> a<00:04:47.120> big<00:04:47.280> hashmap<00:04:47.759> that 00:04:47.909 --> 00:04:47.919 align:start position:0% address it's just a big hashmap that 00:04:47.919 --> 00:04:49.629 align:start position:0% address it's just a big hashmap that just<00:04:48.000> looks<00:04:48.199> in<00:04:48.320> the<00:04:48.440> contract<00:04:48.759> storage<00:04:49.440> for 00:04:49.629 --> 00:04:49.639 align:start position:0% just looks in the contract storage for 00:04:49.639 --> 00:04:51.710 align:start position:0% just looks in the contract storage for the<00:04:49.840> given<00:04:50.120> name<00:04:50.720> what<00:04:50.880> is<00:04:51.000> the<00:04:51.160> address<00:04:51.560> that 00:04:51.710 --> 00:04:51.720 align:start position:0% the given name what is the address that 00:04:51.720 --> 00:04:53.670 align:start position:0% the given name what is the address that is<00:04:52.000> associated<00:04:52.600> with<00:04:52.759> it<00:04:53.160> and<00:04:53.280> then<00:04:53.400> it 00:04:53.670 --> 00:04:53.680 align:start position:0% is associated with it and then it 00:04:53.680 --> 00:04:55.590 align:start position:0% is associated with it and then it Returns<00:04:53.919> the<00:04:54.080> address<00:04:54.840> and<00:04:54.960> you<00:04:55.039> can<00:04:55.240> extend 00:04:55.590 --> 00:04:55.600 align:start position:0% Returns the address and you can extend 00:04:55.600 --> 00:04:58.590 align:start position:0% Returns the address and you can extend this<00:04:56.160> by<00:04:56.320> giving<00:04:56.560> a<00:04:56.720> reverse<00:04:57.160> lookup<00:04:58.039> so<00:04:58.440> you 00:04:58.590 --> 00:04:58.600 align:start position:0% this by giving a reverse lookup so you 00:04:58.600 --> 00:05:00.070 align:start position:0% this by giving a reverse lookup so you can<00:04:58.880> query<00:04:59.160> it<00:04:59.280> for<00:04:59.440> address<00:04:59.680> address<00:05:00.000> and 00:05:00.070 --> 00:05:00.080 align:start position:0% can query it for address address and 00:05:00.080 --> 00:05:02.390 align:start position:0% can query it for address address and then<00:05:00.240> you<00:05:00.360> can<00:05:00.560> see<00:05:01.120> what<00:05:01.240> is<00:05:01.360> the<00:05:01.560> name<00:05:02.120> that 00:05:02.390 --> 00:05:02.400 align:start position:0% then you can see what is the name that 00:05:02.400 --> 00:05:05.350 align:start position:0% then you can see what is the name that belongs<00:05:02.800> to<00:05:03.080> this<00:05:03.680> uh<00:05:03.840> to<00:05:04.120> this 00:05:05.350 --> 00:05:05.360 align:start position:0% belongs to this uh to this 00:05:05.360 --> 00:05:08.909 align:start position:0% belongs to this uh to this address<00:05:06.360> and<00:05:06.759> a<00:05:06.919> good<00:05:07.120> example<00:05:07.520> here<00:05:08.120> is<00:05:08.400> the 00:05:08.909 --> 00:05:08.919 align:start position:0% address and a good example here is the 00:05:08.919 --> 00:05:11.550 align:start position:0% address and a good example here is the is<00:05:09.039> the<00:05:09.240> name<00:05:09.800> the<00:05:09.919> name<00:05:10.199> rare<00:05:10.479> contract<00:05:11.400> that 00:05:11.550 --> 00:05:11.560 align:start position:0% is the name the name rare contract that 00:05:11.560 --> 00:05:14.270 align:start position:0% is the name the name rare contract that is<00:05:12.000> uh<00:05:12.400> actually<00:05:12.680> implemented<00:05:13.280> by<00:05:13.560> by<00:05:13.720> gin<00:05:14.160> I 00:05:14.270 --> 00:05:14.280 align:start position:0% is uh actually implemented by by gin I 00:05:14.280 --> 00:05:17.070 align:start position:0% is uh actually implemented by by gin I think<00:05:15.000> it's<00:05:15.120> in<00:05:15.400> the<00:05:15.720> the<00:05:15.880> de<00:05:16.160> bin<00:05:16.560> GitHub 00:05:17.070 --> 00:05:17.080 align:start position:0% think it's in the the de bin GitHub 00:05:17.080 --> 00:05:21.749 align:start position:0% think it's in the the de bin GitHub project<00:05:17.560> in<00:05:17.720> the<00:05:18.039> ethereum<00:05:19.280> um<00:05:20.680> repository<00:05:21.680> uh 00:05:21.749 --> 00:05:21.759 align:start position:0% project in the ethereum um repository uh 00:05:21.759 --> 00:05:23.430 align:start position:0% project in the ethereum um repository uh and<00:05:21.919> here<00:05:22.039> you<00:05:22.160> have<00:05:22.360> the<00:05:22.759> the<00:05:22.840> name<00:05:23.080> register 00:05:23.430 --> 00:05:23.440 align:start position:0% and here you have the the name register 00:05:23.440 --> 00:05:25.110 align:start position:0% and here you have the the name register implementation<00:05:24.120> so<00:05:24.280> you<00:05:24.400> can<00:05:24.560> take<00:05:24.680> a<00:05:24.800> look<00:05:24.960> at 00:05:25.110 --> 00:05:25.120 align:start position:0% implementation so you can take a look at 00:05:25.120 --> 00:05:30.830 align:start position:0% implementation so you can take a look at this<00:05:25.560> and<00:05:25.720> see<00:05:26.000> how<00:05:26.600> how<00:05:26.800> G<00:05:27.319> uh<00:05:27.440> how<00:05:27.639> G<00:05:27.880> does<00:05:28.039> it 00:05:30.830 --> 00:05:30.840 align:start position:0% this and see how how G uh how G does it 00:05:30.840 --> 00:05:34.309 align:start position:0% this and see how how G uh how G does it so<00:05:31.639> a<00:05:31.840> second<00:05:32.479> data<00:05:32.840> pattern<00:05:33.199> is<00:05:33.360> this<00:05:33.600> data 00:05:34.309 --> 00:05:34.319 align:start position:0% so a second data pattern is this data 00:05:34.319 --> 00:05:38.150 align:start position:0% so a second data pattern is this data feed<00:05:35.319> smart<00:05:35.919> contracts<00:05:36.919> they<00:05:37.120> cannot<00:05:37.840> reach 00:05:38.150 --> 00:05:38.160 align:start position:0% feed smart contracts they cannot reach 00:05:38.160 --> 00:05:40.309 align:start position:0% feed smart contracts they cannot reach out<00:05:38.440> to<00:05:38.600> the<00:05:38.720> real<00:05:38.919> world<00:05:39.240> you<00:05:39.360> cannot<00:05:39.600> make<00:05:39.800> a 00:05:40.309 --> 00:05:40.319 align:start position:0% out to the real world you cannot make a 00:05:40.319 --> 00:05:43.590 align:start position:0% out to the real world you cannot make a HTTP<00:05:41.000> call<00:05:41.479> and<00:05:41.680> and<00:05:41.800> see<00:05:42.039> what<00:05:42.199> a<00:05:42.600> website 00:05:43.590 --> 00:05:43.600 align:start position:0% HTTP call and and see what a website 00:05:43.600 --> 00:05:46.390 align:start position:0% HTTP call and and see what a website returns<00:05:43.960> as<00:05:44.080> a<00:05:44.520> value<00:05:45.520> you<00:05:45.680> cannot<00:05:46.000> directly 00:05:46.390 --> 00:05:46.400 align:start position:0% returns as a value you cannot directly 00:05:46.400 --> 00:05:48.070 align:start position:0% returns as a value you cannot directly connect<00:05:46.680> the<00:05:46.840> camera<00:05:47.120> to<00:05:47.280> it<00:05:47.440> so<00:05:47.639> can<00:05:47.800> make<00:05:47.960> a 00:05:48.070 --> 00:05:48.080 align:start position:0% connect the camera to it so can make a 00:05:48.080 --> 00:05:49.670 align:start position:0% connect the camera to it so can make a picture<00:05:48.479> so<00:05:48.639> you<00:05:48.720> need<00:05:49.120> you<00:05:49.199> need<00:05:49.360> to<00:05:49.520> actually 00:05:49.670 --> 00:05:49.680 align:start position:0% picture so you need you need to actually 00:05:49.680 --> 00:05:52.110 align:start position:0% picture so you need you need to actually feed<00:05:50.000> the<00:05:50.160> data<00:05:50.400> to<00:05:50.520> your<00:05:50.720> contracts<00:05:51.440> to<00:05:51.680> get 00:05:52.110 --> 00:05:52.120 align:start position:0% feed the data to your contracts to get 00:05:52.120 --> 00:05:54.550 align:start position:0% feed the data to your contracts to get some<00:05:52.360> kind<00:05:52.479> of<00:05:52.639> value<00:05:52.880> out<00:05:53.039> of<00:05:53.160> it<00:05:53.680> so<00:05:53.880> what<00:05:54.039> if 00:05:54.550 --> 00:05:54.560 align:start position:0% some kind of value out of it so what if 00:05:54.560 --> 00:05:56.990 align:start position:0% some kind of value out of it so what if if<00:05:54.680> you're<00:05:54.880> making<00:05:55.880> application<00:05:56.680> that<00:05:56.800> needs 00:05:56.990 --> 00:05:57.000 align:start position:0% if you're making application that needs 00:05:57.000 --> 00:05:59.390 align:start position:0% if you're making application that needs to<00:05:57.160> know<00:05:57.319> the<00:05:57.479> weather<00:05:58.000> for<00:05:58.160> a<00:05:58.319> certain<00:05:58.639> area 00:05:59.390 --> 00:05:59.400 align:start position:0% to know the weather for a certain area 00:05:59.400 --> 00:06:01.189 align:start position:0% to know the weather for a certain area or<00:05:59.680> or<00:05:59.840> it<00:05:59.919> needs<00:06:00.120> to<00:06:00.240> know<00:06:00.400> an<00:06:00.560> exchange<00:06:00.919> rate 00:06:01.189 --> 00:06:01.199 align:start position:0% or or it needs to know an exchange rate 00:06:01.199 --> 00:06:03.390 align:start position:0% or or it needs to know an exchange rate so<00:06:01.360> you<00:06:01.440> can<00:06:01.639> exchange<00:06:02.080> your<00:06:02.680> ether<00:06:03.120> for 00:06:03.390 --> 00:06:03.400 align:start position:0% so you can exchange your ether for 00:06:03.400 --> 00:06:06.830 align:start position:0% so you can exchange your ether for Bitcoin<00:06:04.319> Vis<00:06:05.080> Versa 00:06:06.830 --> 00:06:06.840 align:start position:0% Bitcoin Vis Versa 00:06:06.840 --> 00:06:09.830 align:start position:0% Bitcoin Vis Versa um<00:06:07.840> and<00:06:08.440> yeah<00:06:08.599> there's<00:06:08.840> this<00:06:09.160> limitation<00:06:09.720> of 00:06:09.830 --> 00:06:09.840 align:start position:0% um and yeah there's this limitation of 00:06:09.840 --> 00:06:11.710 align:start position:0% um and yeah there's this limitation of the<00:06:09.960> ethereum<00:06:10.280> virtual<00:06:10.599> machine<00:06:11.440> where 00:06:11.710 --> 00:06:11.720 align:start position:0% the ethereum virtual machine where 00:06:11.720 --> 00:06:13.430 align:start position:0% the ethereum virtual machine where because<00:06:11.919> it's<00:06:12.120> deterministic<00:06:13.000> you<00:06:13.160> cannot 00:06:13.430 --> 00:06:13.440 align:start position:0% because it's deterministic you cannot 00:06:13.440 --> 00:06:16.909 align:start position:0% because it's deterministic you cannot look<00:06:13.639> outside<00:06:14.479> and<00:06:14.639> fetch<00:06:15.319> data<00:06:16.280> uh<00:06:16.400> into<00:06:16.720> the 00:06:16.909 --> 00:06:16.919 align:start position:0% look outside and fetch data uh into the 00:06:16.919 --> 00:06:18.550 align:start position:0% look outside and fetch data uh into the into<00:06:17.080> the<00:06:17.199> blockchain<00:06:17.599> by<00:06:17.759> itself<00:06:18.240> so<00:06:18.440> what 00:06:18.550 --> 00:06:18.560 align:start position:0% into the blockchain by itself so what 00:06:18.560 --> 00:06:20.749 align:start position:0% into the blockchain by itself so what you<00:06:18.639> need<00:06:18.759> to<00:06:18.919> do<00:06:19.479> you<00:06:19.639> actually<00:06:19.919> need<00:06:20.080> to<00:06:20.280> feed 00:06:20.749 --> 00:06:20.759 align:start position:0% you need to do you actually need to feed 00:06:20.759 --> 00:06:23.189 align:start position:0% you need to do you actually need to feed this<00:06:21.000> data<00:06:21.880> into<00:06:22.240> ethereum<00:06:22.800> onto<00:06:23.080> the 00:06:23.189 --> 00:06:23.199 align:start position:0% this data into ethereum onto the 00:06:23.199 --> 00:06:25.150 align:start position:0% this data into ethereum onto the blockchain<00:06:23.759> and<00:06:23.880> then<00:06:24.080> once<00:06:24.240> it<00:06:24.400> is 00:06:25.150 --> 00:06:25.160 align:start position:0% blockchain and then once it is 00:06:25.160 --> 00:06:27.749 align:start position:0% blockchain and then once it is there<00:06:26.160> every<00:06:26.400> other<00:06:26.680> application<00:06:27.360> on<00:06:27.639> the 00:06:27.749 --> 00:06:27.759 align:start position:0% there every other application on the 00:06:27.759 --> 00:06:29.589 align:start position:0% there every other application on the ethereum<00:06:28.199> blockchain<00:06:28.599> can<00:06:28.759> actually<00:06:29.000> use<00:06:29.240> it 00:06:29.589 --> 00:06:29.599 align:start position:0% ethereum blockchain can actually use it 00:06:29.599 --> 00:06:31.790 align:start position:0% ethereum blockchain can actually use it and<00:06:29.759> reuse<00:06:30.120> it<00:06:30.720> and<00:06:30.840> use<00:06:31.039> it<00:06:31.120> in<00:06:31.319> fashions<00:06:31.680> that 00:06:31.790 --> 00:06:31.800 align:start position:0% and reuse it and use it in fashions that 00:06:31.800 --> 00:06:37.990 align:start position:0% and reuse it and use it in fashions that you<00:06:32.160> really<00:06:32.360> didn't<00:06:32.680> think<00:06:32.880> of<00:06:33.080> yourself<00:06:34.039> uh 00:06:37.990 --> 00:06:38.000 align:start position:0% 00:06:38.000 --> 00:06:39.950 align:start position:0% before 00:06:39.950 --> 00:06:39.960 align:start position:0% before 00:06:39.960 --> 00:06:42.589 align:start position:0% before so<00:06:40.960> typically<00:06:41.479> you'll<00:06:41.639> need<00:06:41.800> an<00:06:42.000> automated 00:06:42.589 --> 00:06:42.599 align:start position:0% so typically you'll need an automated 00:06:42.599 --> 00:06:44.749 align:start position:0% so typically you'll need an automated process<00:06:43.080> some<00:06:43.280> kind<00:06:43.479> of<00:06:43.720> demon<00:06:44.520> that 00:06:44.749 --> 00:06:44.759 align:start position:0% process some kind of demon that 00:06:44.759 --> 00:06:47.189 align:start position:0% process some kind of demon that frequently<00:06:45.479> publishes<00:06:46.479> updates<00:06:46.840> to<00:06:47.000> this 00:06:47.189 --> 00:06:47.199 align:start position:0% frequently publishes updates to this 00:06:47.199 --> 00:06:49.870 align:start position:0% frequently publishes updates to this data<00:06:47.440> feed<00:06:47.880> so<00:06:48.120> maybe<00:06:48.840> once<00:06:49.160> every<00:06:49.440> day<00:06:49.759> what 00:06:49.870 --> 00:06:49.880 align:start position:0% data feed so maybe once every day what 00:06:49.880 --> 00:06:51.430 align:start position:0% data feed so maybe once every day what the<00:06:50.000> weather<00:06:50.360> was<00:06:50.680> or<00:06:50.840> what<00:06:50.960> the<00:06:51.080> exchange 00:06:51.430 --> 00:06:51.440 align:start position:0% the weather was or what the exchange 00:06:51.440 --> 00:06:53.550 align:start position:0% the weather was or what the exchange rate<00:06:51.759> was<00:06:52.319> or<00:06:52.520> more<00:06:52.759> frequent<00:06:53.160> or<00:06:53.319> less 00:06:53.550 --> 00:06:53.560 align:start position:0% rate was or more frequent or less 00:06:53.560 --> 00:06:55.909 align:start position:0% rate was or more frequent or less frequent<00:06:54.360> uh<00:06:54.479> depending<00:06:54.880> on<00:06:55.080> your<00:06:55.319> on<00:06:55.440> your 00:06:55.909 --> 00:06:55.919 align:start position:0% frequent uh depending on your on your 00:06:55.919 --> 00:07:00.110 align:start position:0% frequent uh depending on your on your usage<00:06:57.360> um<00:06:58.360> and<00:06:58.599> of<00:06:58.720> course<00:06:58.879> you<00:06:59.000> can<00:06:59.800> you<00:06:59.919> can 00:07:00.110 --> 00:07:00.120 align:start position:0% usage um and of course you can you can 00:07:00.120 --> 00:07:02.510 align:start position:0% usage um and of course you can you can publish<00:07:00.440> this<00:07:00.560> as<00:07:00.680> a<00:07:00.800> free<00:07:01.039> service<00:07:02.039> but<00:07:02.360> you 00:07:02.510 --> 00:07:02.520 align:start position:0% publish this as a free service but you 00:07:02.520 --> 00:07:06.830 align:start position:0% publish this as a free service but you can<00:07:02.720> always<00:07:03.120> you<00:07:03.240> can<00:07:03.560> also<00:07:04.639> uh<00:07:05.639> ask<00:07:05.879> for<00:07:06.080> a<00:07:06.240> fee 00:07:06.830 --> 00:07:06.840 align:start position:0% can always you can also uh ask for a fee 00:07:06.840 --> 00:07:08.469 align:start position:0% can always you can also uh ask for a fee if<00:07:07.039> people<00:07:07.280> are<00:07:07.560> getting<00:07:07.759> the<00:07:07.919> data<00:07:08.160> out<00:07:08.319> of 00:07:08.469 --> 00:07:08.479 align:start position:0% if people are getting the data out of 00:07:08.479 --> 00:07:09.869 align:start position:0% if people are getting the data out of this<00:07:08.639> data<00:07:08.879> feed<00:07:09.120> so<00:07:09.240> of<00:07:09.360> course<00:07:09.479> there's<00:07:09.639> some 00:07:09.869 --> 00:07:09.879 align:start position:0% this data feed so of course there's some 00:07:09.879 --> 00:07:12.309 align:start position:0% this data feed so of course there's some cost<00:07:10.160> associating<00:07:11.160> with<00:07:11.560> with<00:07:11.680> setting<00:07:12.120> up 00:07:12.309 --> 00:07:12.319 align:start position:0% cost associating with with setting up 00:07:12.319 --> 00:07:14.469 align:start position:0% cost associating with with setting up such<00:07:12.479> a<00:07:12.680> process<00:07:13.039> that<00:07:13.360> keeps<00:07:13.639> updating<00:07:14.240> keeps 00:07:14.469 --> 00:07:14.479 align:start position:0% such a process that keeps updating keeps 00:07:14.479 --> 00:07:16.510 align:start position:0% such a process that keeps updating keeps pushing<00:07:15.199> data<00:07:15.599> to<00:07:15.759> the<00:07:15.960> to<00:07:16.080> the<00:07:16.160> ethereum 00:07:16.510 --> 00:07:16.520 align:start position:0% pushing data to the to the ethereum 00:07:16.520 --> 00:07:18.350 align:start position:0% pushing data to the to the ethereum contract<00:07:17.160> at<00:07:17.240> least<00:07:17.440> you<00:07:17.560> need<00:07:17.680> to<00:07:17.840> pay<00:07:18.080> the 00:07:18.350 --> 00:07:18.360 align:start position:0% contract at least you need to pay the 00:07:18.360 --> 00:07:21.029 align:start position:0% contract at least you need to pay the the<00:07:18.520> gas<00:07:19.160> and<00:07:19.280> also<00:07:19.520> some<00:07:19.720> kind<00:07:19.840> of<00:07:20.000> Hosting<00:07:20.919> uh 00:07:21.029 --> 00:07:21.039 align:start position:0% the gas and also some kind of Hosting uh 00:07:21.039 --> 00:07:23.710 align:start position:0% the gas and also some kind of Hosting uh fee<00:07:21.759> so<00:07:22.199> you<00:07:22.319> could<00:07:22.560> actually<00:07:22.840> charge<00:07:23.319> every 00:07:23.710 --> 00:07:23.720 align:start position:0% fee so you could actually charge every 00:07:23.720 --> 00:07:25.550 align:start position:0% fee so you could actually charge every contract<00:07:24.160> that<00:07:24.280> is<00:07:24.400> using<00:07:24.720> this<00:07:25.280> and<00:07:25.400> this 00:07:25.550 --> 00:07:25.560 align:start position:0% contract that is using this and this 00:07:25.560 --> 00:07:28.150 align:start position:0% contract that is using this and this could<00:07:25.720> be<00:07:25.960> a<00:07:26.199> a<00:07:26.360> viable<00:07:26.759> Revenue<00:07:27.120> model<00:07:27.759> for<00:07:28.039> a 00:07:28.150 --> 00:07:28.160 align:start position:0% could be a a viable Revenue model for a 00:07:28.160 --> 00:07:30.309 align:start position:0% could be a a viable Revenue model for a for<00:07:28.360> data<00:07:28.639> feed 00:07:30.309 --> 00:07:30.319 align:start position:0% for data feed 00:07:30.319 --> 00:07:32.430 align:start position:0% for data feed um<00:07:30.720> yeah<00:07:30.919> I've<00:07:31.120> given<00:07:31.319> you<00:07:31.479> these<00:07:31.840> uh<00:07:32.080> examples 00:07:32.430 --> 00:07:32.440 align:start position:0% um yeah I've given you these uh examples 00:07:32.440 --> 00:07:36.510 align:start position:0% um yeah I've given you these uh examples already<00:07:33.800> and<00:07:34.800> a<00:07:35.000> much<00:07:35.160> more<00:07:35.400> advanced<00:07:35.840> example 00:07:36.510 --> 00:07:36.520 align:start position:0% already and a much more advanced example 00:07:36.520 --> 00:07:39.749 align:start position:0% already and a much more advanced example is<00:07:36.759> the<00:07:36.960> the<00:07:37.039> BTC<00:07:37.599> relay<00:07:38.599> uh<00:07:38.800> contracts<00:07:39.599> where 00:07:39.749 --> 00:07:39.759 align:start position:0% is the the BTC relay uh contracts where 00:07:39.759 --> 00:07:41.830 align:start position:0% is the the BTC relay uh contracts where it's<00:07:39.919> actually<00:07:40.160> storing<00:07:41.160> blocks<00:07:41.680> and 00:07:41.830 --> 00:07:41.840 align:start position:0% it's actually storing blocks and 00:07:41.840 --> 00:07:43.909 align:start position:0% it's actually storing blocks and transactions<00:07:42.360> from<00:07:42.520> the<00:07:42.680> Bitcoin<00:07:43.560> onto 00:07:43.909 --> 00:07:43.919 align:start position:0% transactions from the Bitcoin onto 00:07:43.919 --> 00:07:46.469 align:start position:0% transactions from the Bitcoin onto ethereum<00:07:44.560> so<00:07:44.759> then<00:07:44.919> you<00:07:45.039> can<00:07:45.199> use<00:07:45.560> this<00:07:46.039> on<00:07:46.240> the 00:07:46.469 --> 00:07:46.479 align:start position:0% ethereum so then you can use this on the 00:07:46.479 --> 00:07:49.230 align:start position:0% ethereum so then you can use this on the ethereum<00:07:47.479> uh<00:07:47.599> blockchain<00:07:48.039> as 00:07:49.230 --> 00:07:49.240 align:start position:0% ethereum uh blockchain as 00:07:49.240 --> 00:07:53.110 align:start position:0% ethereum uh blockchain as well<00:07:50.240> and<00:07:50.599> and<00:07:50.840> as<00:07:50.919> an<00:07:51.080> example<00:07:51.720> here<00:07:52.720> we<00:07:52.879> have 00:07:53.110 --> 00:07:53.120 align:start position:0% well and and as an example here we have 00:07:53.120 --> 00:07:55.469 align:start position:0% well and and as an example here we have the<00:07:53.479> the<00:07:53.720> price<00:07:54.039> fre<00:07:54.599> the<00:07:54.759> the<00:07:54.879> price<00:07:55.120> feed 00:07:55.469 --> 00:07:55.479 align:start position:0% the the price fre the the price feed 00:07:55.479 --> 00:07:58.189 align:start position:0% the the price fre the the price feed example<00:07:56.400> from<00:07:56.800> Nick<00:07:57.000> Dodson<00:07:57.520> I<00:07:57.599> think<00:07:57.800> he's 00:07:58.189 --> 00:07:58.199 align:start position:0% example from Nick Dodson I think he's 00:07:58.199 --> 00:08:00.710 align:start position:0% example from Nick Dodson I think he's also<00:07:58.440> here<00:07:58.599> or<00:07:58.759> might<00:07:58.919> be<00:07:59.080> presenting<00:07:59.840> later 00:08:00.710 --> 00:08:00.720 align:start position:0% also here or might be presenting later 00:08:00.720 --> 00:08:04.070 align:start position:0% also here or might be presenting later this<00:08:00.879> week<00:08:01.599> so<00:08:01.919> here<00:08:02.479> they're<00:08:02.960> pushing<00:08:03.960> uh 00:08:04.070 --> 00:08:04.080 align:start position:0% this week so here they're pushing uh 00:08:04.080 --> 00:08:07.149 align:start position:0% this week so here they're pushing uh fiat<00:08:04.440> currency<00:08:05.199> uh<00:08:05.360> prices<00:08:05.960> on<00:08:06.199> the<00:08:06.680> uh<00:08:06.800> on<00:08:06.960> the 00:08:07.149 --> 00:08:07.159 align:start position:0% fiat currency uh prices on the uh on the 00:08:07.159 --> 00:08:09.189 align:start position:0% fiat currency uh prices on the uh on the on<00:08:07.319> the<00:08:07.639> on<00:08:07.759> the<00:08:07.879> blockchain<00:08:08.800> and<00:08:08.919> then<00:08:09.080> you 00:08:09.189 --> 00:08:09.199 align:start position:0% on the on the blockchain and then you 00:08:09.199 --> 00:08:11.430 align:start position:0% on the on the blockchain and then you can<00:08:09.319> use<00:08:09.560> that<00:08:09.680> for<00:08:09.879> some<00:08:10.080> kind<00:08:10.240> of<00:08:11.000> set<00:08:11.240> up 00:08:11.430 --> 00:08:11.440 align:start position:0% can use that for some kind of set up 00:08:11.440 --> 00:08:13.230 align:start position:0% can use that for some kind of set up some<00:08:11.560> kind<00:08:11.720> of<00:08:11.840> trade<00:08:12.199> some<00:08:12.479> set<00:08:12.759> set<00:08:12.919> up<00:08:13.080> some 00:08:13.230 --> 00:08:13.240 align:start position:0% some kind of trade some set set up some 00:08:13.240 --> 00:08:15.350 align:start position:0% some kind of trade some set set up some kind<00:08:13.360> of<00:08:13.440> escrow<00:08:14.280> without<00:08:14.599> having<00:08:14.759> to<00:08:14.919> rely<00:08:15.240> on 00:08:15.350 --> 00:08:15.360 align:start position:0% kind of escrow without having to rely on 00:08:15.360 --> 00:08:19.869 align:start position:0% kind of escrow without having to rely on the<00:08:15.520> exchange<00:08:15.919> rates<00:08:16.520> of<00:08:16.919> The<00:08:17.080> Ether 00:08:19.869 --> 00:08:19.879 align:start position:0% 00:08:19.879 --> 00:08:24.189 align:start position:0% itself<00:08:21.280> so<00:08:22.280> looking<00:08:22.599> at<00:08:22.800> these<00:08:23.479> transaction 00:08:24.189 --> 00:08:24.199 align:start position:0% itself so looking at these transaction 00:08:24.199 --> 00:08:26.909 align:start position:0% itself so looking at these transaction and<00:08:24.440> value<00:08:24.759> related<00:08:25.159> patterns<00:08:25.800> two<00:08:26.080> two 00:08:26.909 --> 00:08:26.919 align:start position:0% and value related patterns two two 00:08:26.919 --> 00:08:29.629 align:start position:0% and value related patterns two two examples<00:08:27.919> uh<00:08:28.080> the<00:08:28.240> asset<00:08:28.560> token<00:08:29.280> we<00:08:29.520> you've 00:08:29.629 --> 00:08:29.639 align:start position:0% examples uh the asset token we you've 00:08:29.639 --> 00:08:32.829 align:start position:0% examples uh the asset token we you've seen<00:08:29.840> that<00:08:29.960> in<00:08:30.280> Peter's<00:08:30.919> presentation<00:08:31.919> so<00:08:32.719> you 00:08:32.829 --> 00:08:32.839 align:start position:0% seen that in Peter's presentation so you 00:08:32.839 --> 00:08:34.310 align:start position:0% seen that in Peter's presentation so you need<00:08:33.000> to<00:08:33.080> have<00:08:33.200> some<00:08:33.360> kind<00:08:33.479> of<00:08:33.640> representation 00:08:34.310 --> 00:08:34.320 align:start position:0% need to have some kind of representation 00:08:34.320 --> 00:08:38.190 align:start position:0% need to have some kind of representation from<00:08:34.519> a<00:08:35.159> either<00:08:36.000> virtual<00:08:36.519> or<00:08:36.760> physical<00:08:37.200> asset 00:08:38.190 --> 00:08:38.200 align:start position:0% from a either virtual or physical asset 00:08:38.200 --> 00:08:40.750 align:start position:0% from a either virtual or physical asset uh<00:08:38.320> on<00:08:38.440> the<00:08:38.560> blockchain<00:08:39.560> so<00:08:39.800> you<00:08:39.959> can<00:08:40.560> for 00:08:40.750 --> 00:08:40.760 align:start position:0% uh on the blockchain so you can for 00:08:40.760 --> 00:08:42.630 align:start position:0% uh on the blockchain so you can for crowdfunding<00:08:41.399> purposes<00:08:41.800> so<00:08:41.959> you<00:08:42.120> can<00:08:42.360> you<00:08:42.479> can 00:08:42.630 --> 00:08:42.640 align:start position:0% crowdfunding purposes so you can you can 00:08:42.640 --> 00:08:44.790 align:start position:0% crowdfunding purposes so you can you can sell<00:08:42.959> it<00:08:43.519> or<00:08:43.680> maybe<00:08:43.919> so<00:08:44.120> you<00:08:44.279> can<00:08:44.519> you<00:08:44.640> can 00:08:44.790 --> 00:08:44.800 align:start position:0% sell it or maybe so you can you can 00:08:44.800 --> 00:08:47.230 align:start position:0% sell it or maybe so you can you can lease<00:08:45.080> your<00:08:45.240> car<00:08:46.120> or<00:08:46.320> you<00:08:46.519> can<00:08:46.760> you<00:08:46.839> can<00:08:47.000> trade 00:08:47.230 --> 00:08:47.240 align:start position:0% lease your car or you can you can trade 00:08:47.240 --> 00:08:48.990 align:start position:0% lease your car or you can you can trade it<00:08:47.480> with<00:08:47.839> with<00:08:47.959> somebody<00:08:48.240> else<00:08:48.480> or<00:08:48.720> just<00:08:48.880> you 00:08:48.990 --> 00:08:49.000 align:start position:0% it with with somebody else or just you 00:08:49.000 --> 00:08:51.110 align:start position:0% it with with somebody else or just you can<00:08:49.160> track<00:08:49.440> it<00:08:49.720> for<00:08:50.040> auditing 00:08:51.110 --> 00:08:51.120 align:start position:0% can track it for auditing 00:08:51.120 --> 00:08:54.269 align:start position:0% can track it for auditing purposes<00:08:52.120> and<00:08:53.000> typically<00:08:53.480> these<00:08:53.720> these 00:08:54.269 --> 00:08:54.279 align:start position:0% purposes and typically these these 00:08:54.279 --> 00:08:58.030 align:start position:0% purposes and typically these these assets<00:08:55.279> um<00:08:55.760> are<00:08:56.160> are<00:08:56.560> are<00:08:56.800> equal<00:08:57.360> are<00:08:57.519> equal<00:08:57.800> in 00:08:58.030 --> 00:08:58.040 align:start position:0% assets um are are are equal are equal in 00:08:58.040 --> 00:08:59.670 align:start position:0% assets um are are are equal are equal in kind<00:08:58.279> so<00:08:58.440> you<00:08:58.560> can<00:08:58.880> enumerate<00:08:59.320> that<00:08:59.480> them<00:08:59.600> and 00:08:59.670 --> 00:08:59.680 align:start position:0% kind so you can enumerate that them and 00:08:59.680 --> 00:09:02.710 align:start position:0% kind so you can enumerate that them and you<00:08:59.760> can<00:08:59.880> have<00:09:00.000> multiple<00:09:00.360> of<00:09:00.600> them<00:09:01.600> and<00:09:02.399> if<00:09:02.519> you 00:09:02.710 --> 00:09:02.720 align:start position:0% you can have multiple of them and if you 00:09:02.720 --> 00:09:04.910 align:start position:0% you can have multiple of them and if you for<00:09:02.920> this<00:09:03.079> if<00:09:03.160> you<00:09:03.279> use<00:09:03.680> a<00:09:03.839> standard<00:09:04.279> interface 00:09:04.910 --> 00:09:04.920 align:start position:0% for this if you use a standard interface 00:09:04.920 --> 00:09:07.630 align:start position:0% for this if you use a standard interface and<00:09:05.040> there's<00:09:05.399> the<00:09:06.079> the<00:09:06.279> The<00:09:06.440> Meta<00:09:07.240> Meta 00:09:07.630 --> 00:09:07.640 align:start position:0% and there's the the The Meta Meta 00:09:07.640 --> 00:09:09.790 align:start position:0% and there's the the The Meta Meta currency<00:09:08.519> uh<00:09:08.680> API<00:09:09.120> description<00:09:09.560> on<00:09:09.680> the 00:09:09.790 --> 00:09:09.800 align:start position:0% currency uh API description on the 00:09:09.800 --> 00:09:11.949 align:start position:0% currency uh API description on the ethereum<00:09:10.160> wiki<00:09:10.959> if<00:09:11.079> you<00:09:11.160> use<00:09:11.399> the<00:09:11.519> same<00:09:11.800> kind 00:09:11.949 --> 00:09:11.959 align:start position:0% ethereum wiki if you use the same kind 00:09:11.959 --> 00:09:14.389 align:start position:0% ethereum wiki if you use the same kind of<00:09:12.079> interface<00:09:12.480> for<00:09:12.680> this<00:09:13.320> then<00:09:13.480> you<00:09:13.600> can<00:09:13.800> use 00:09:14.389 --> 00:09:14.399 align:start position:0% of interface for this then you can use 00:09:14.399 --> 00:09:16.470 align:start position:0% of interface for this then you can use all<00:09:14.640> kinds<00:09:14.839> of<00:09:15.000> different<00:09:15.560> wallets<00:09:16.079> and 00:09:16.470 --> 00:09:16.480 align:start position:0% all kinds of different wallets and 00:09:16.480 --> 00:09:19.870 align:start position:0% all kinds of different wallets and exchanges<00:09:17.480> to<00:09:18.160> to<00:09:18.399> to<00:09:18.600> track<00:09:18.920> your<00:09:19.519> uh<00:09:19.640> sub 00:09:19.870 --> 00:09:19.880 align:start position:0% exchanges to to to track your uh sub 00:09:19.880 --> 00:09:22.870 align:start position:0% exchanges to to to track your uh sub currency<00:09:20.279> to<00:09:20.399> track<00:09:20.680> your<00:09:21.040> assets<00:09:22.040> without 00:09:22.870 --> 00:09:22.880 align:start position:0% currency to track your assets without 00:09:22.880 --> 00:09:24.389 align:start position:0% currency to track your assets without the<00:09:23.120> the<00:09:23.240> wallet<00:09:23.600> itself<00:09:23.920> having<00:09:24.160> to 00:09:24.389 --> 00:09:24.399 align:start position:0% the the wallet itself having to 00:09:24.399 --> 00:09:27.150 align:start position:0% the the wallet itself having to specifically<00:09:25.000> support 00:09:27.150 --> 00:09:27.160 align:start position:0% specifically support 00:09:27.160 --> 00:09:32.710 align:start position:0% specifically support you<00:09:28.160> um 00:09:32.710 --> 00:09:32.720 align:start position:0% 00:09:32.720 --> 00:09:36.150 align:start position:0% so<00:09:33.120> what<00:09:33.240> you<00:09:33.360> do<00:09:33.839> you<00:09:34.000> create<00:09:34.240> a<00:09:34.600> contract<00:09:35.600> and 00:09:36.150 --> 00:09:36.160 align:start position:0% so what you do you create a contract and 00:09:36.160 --> 00:09:38.630 align:start position:0% so what you do you create a contract and basically<00:09:36.600> you<00:09:36.800> track<00:09:37.120> per<00:09:37.440> account<00:09:38.320> how<00:09:38.480> much 00:09:38.630 --> 00:09:38.640 align:start position:0% basically you track per account how much 00:09:38.640 --> 00:09:41.790 align:start position:0% basically you track per account how much of<00:09:38.839> these<00:09:39.079> assets<00:09:39.480> they<00:09:39.720> have<00:09:40.440> in<00:09:40.800> uh<00:09:41.279> uh<00:09:41.480> in<00:09:41.680> in 00:09:41.790 --> 00:09:41.800 align:start position:0% of these assets they have in uh uh in in 00:09:41.800 --> 00:09:44.350 align:start position:0% of these assets they have in uh uh in in the<00:09:42.120> the<00:09:42.240> contract<00:09:42.760> storage<00:09:43.760> and<00:09:43.920> then<00:09:44.200> you 00:09:44.350 --> 00:09:44.360 align:start position:0% the the contract storage and then you 00:09:44.360 --> 00:09:48.110 align:start position:0% the the contract storage and then you set<00:09:44.600> up<00:09:45.560> maybe<00:09:45.839> at<00:09:45.959> least<00:09:46.200> two<00:09:46.800> two<00:09:47.120> functions 00:09:48.110 --> 00:09:48.120 align:start position:0% set up maybe at least two two functions 00:09:48.120 --> 00:09:49.949 align:start position:0% set up maybe at least two two functions one<00:09:48.320> to<00:09:48.600> transfer<00:09:49.079> this<00:09:49.240> assets<00:09:49.560> from<00:09:49.720> one 00:09:49.949 --> 00:09:49.959 align:start position:0% one to transfer this assets from one 00:09:49.959 --> 00:09:52.829 align:start position:0% one to transfer this assets from one account<00:09:50.200> to<00:09:50.360> the<00:09:50.440> other<00:09:50.720> account<00:09:51.399> and<00:09:51.600> one<00:09:51.880> to 00:09:52.829 --> 00:09:52.839 align:start position:0% account to the other account and one to 00:09:52.839 --> 00:09:55.790 align:start position:0% account to the other account and one to return<00:09:53.519> the<00:09:53.680> the<00:09:53.800> balance<00:09:54.680> of<00:09:54.880> one<00:09:55.040> of<00:09:55.240> these 00:09:55.790 --> 00:09:55.800 align:start position:0% return the the balance of one of these 00:09:55.800 --> 00:09:57.750 align:start position:0% return the the balance of one of these account<00:09:56.120> holders<00:09:56.399> in<00:09:56.600> there<00:09:57.079> and<00:09:57.320> if<00:09:57.440> you<00:09:57.519> have 00:09:57.750 --> 00:09:57.760 align:start position:0% account holders in there and if you have 00:09:57.760 --> 00:10:00.710 align:start position:0% account holders in there and if you have this<00:09:58.440> you<00:09:58.560> can<00:09:58.720> use<00:09:58.959> this<00:09:59.120> to<00:09:59.399> to<00:09:59.920> create<00:10:00.200> a 00:10:00.710 --> 00:10:00.720 align:start position:0% this you can use this to to create a 00:10:00.720 --> 00:10:03.949 align:start position:0% this you can use this to to create a crowdfunding<00:10:01.320> tokens<00:10:02.240> set<00:10:02.440> up<00:10:02.720> IOU 00:10:03.949 --> 00:10:03.959 align:start position:0% crowdfunding tokens set up IOU 00:10:03.959 --> 00:10:06.190 align:start position:0% crowdfunding tokens set up IOU constructions<00:10:04.959> uh<00:10:05.079> track<00:10:05.360> Fiat<00:10:05.680> currencies 00:10:06.190 --> 00:10:06.200 align:start position:0% constructions uh track Fiat currencies 00:10:06.200 --> 00:10:10.509 align:start position:0% constructions uh track Fiat currencies so<00:10:06.560> US<00:10:07.120> US<00:10:07.480> Dollars<00:10:07.959> Euros<00:10:08.959> whatever<00:10:09.800> or<00:10:10.000> even 00:10:10.509 --> 00:10:10.519 align:start position:0% so US US Dollars Euros whatever or even 00:10:10.519 --> 00:10:13.190 align:start position:0% so US US Dollars Euros whatever or even as<00:10:10.839> uh<00:10:11.000> digix<00:10:11.480> is<00:10:11.600> doing<00:10:12.399> uh<00:10:12.560> keep<00:10:12.800> track<00:10:13.040> of 00:10:13.190 --> 00:10:13.200 align:start position:0% as uh digix is doing uh keep track of 00:10:13.200 --> 00:10:17.190 align:start position:0% as uh digix is doing uh keep track of gold<00:10:13.560> certificates<00:10:14.560> on<00:10:14.760> the<00:10:14.959> on<00:10:15.040> the 00:10:17.190 --> 00:10:17.200 align:start position:0% 00:10:17.200 --> 00:10:20.670 align:start position:0% blockchain<00:10:18.200> and<00:10:18.399> here<00:10:18.760> as<00:10:18.880> an<00:10:19.200> example<00:10:20.200> is<00:10:20.600> uh 00:10:20.670 --> 00:10:20.680 align:start position:0% blockchain and here as an example is uh 00:10:20.680 --> 00:10:24.190 align:start position:0% blockchain and here as an example is uh from<00:10:20.880> slockit<00:10:21.839> they<00:10:22.600> crowdfunding<00:10:23.360> contracts 00:10:24.190 --> 00:10:24.200 align:start position:0% from slockit they crowdfunding contracts 00:10:24.200 --> 00:10:26.310 align:start position:0% from slockit they crowdfunding contracts where<00:10:24.399> they<00:10:24.560> also<00:10:24.760> using<00:10:25.160> this<00:10:25.440> this<00:10:25.640> pattern 00:10:26.310 --> 00:10:26.320 align:start position:0% where they also using this this pattern 00:10:26.320 --> 00:10:27.470 align:start position:0% where they also using this this pattern so<00:10:26.519> they're<00:10:26.800> doing<00:10:27.040> some<00:10:27.240> kind<00:10:27.360> of 00:10:27.470 --> 00:10:27.480 align:start position:0% so they're doing some kind of 00:10:27.480 --> 00:10:28.870 align:start position:0% so they're doing some kind of crowdfunding<00:10:28.040> probably<00:10:28.279> will<00:10:28.440> hear<00:10:28.680> more 00:10:28.870 --> 00:10:28.880 align:start position:0% crowdfunding probably will hear more 00:10:28.880 --> 00:10:31.310 align:start position:0% crowdfunding probably will hear more about<00:10:29.079> this<00:10:29.519> this<00:10:29.680> later<00:10:29.920> on<00:10:30.399> but<00:10:30.560> you<00:10:30.720> can 00:10:31.310 --> 00:10:31.320 align:start position:0% about this this later on but you can 00:10:31.320 --> 00:10:34.269 align:start position:0% about this this later on but you can transfer<00:10:31.959> these<00:10:32.480> tokens<00:10:33.000> to<00:10:33.200> somebody<00:10:33.560> else 00:10:34.269 --> 00:10:34.279 align:start position:0% transfer these tokens to somebody else 00:10:34.279 --> 00:10:36.389 align:start position:0% transfer these tokens to somebody else and<00:10:34.399> you<00:10:34.480> can<00:10:34.640> also<00:10:34.880> see<00:10:35.639> uh<00:10:35.920> what<00:10:36.160> what<00:10:36.240> your 00:10:36.389 --> 00:10:36.399 align:start position:0% and you can also see uh what what your 00:10:36.399 --> 00:10:41.509 align:start position:0% and you can also see uh what what your balance<00:10:36.959> is 00:10:41.509 --> 00:10:41.519 align:start position:0% 00:10:41.519 --> 00:10:45.269 align:start position:0% um<00:10:42.519> another<00:10:43.480> another<00:10:43.839> one<00:10:44.000> of<00:10:44.200> these<00:10:44.680> uh<00:10:45.040> uh 00:10:45.269 --> 00:10:45.279 align:start position:0% um another another one of these uh uh 00:10:45.279 --> 00:10:46.990 align:start position:0% um another another one of these uh uh value<00:10:45.560> and<00:10:45.720> transaction<00:10:46.200> related<00:10:46.639> patterns 00:10:46.990 --> 00:10:47.000 align:start position:0% value and transaction related patterns 00:10:47.000 --> 00:10:50.550 align:start position:0% value and transaction related patterns is<00:10:47.160> the<00:10:47.440> exchange<00:10:48.040> or<00:10:48.279> or<00:10:48.639> market<00:10:49.639> so<00:10:50.279> you<00:10:50.399> have 00:10:50.550 --> 00:10:50.560 align:start position:0% is the exchange or or market so you have 00:10:50.560 --> 00:10:51.829 align:start position:0% is the exchange or or market so you have one<00:10:50.680> of<00:10:50.800> these<00:10:50.920> asset<00:10:51.200> tokens<00:10:51.519> so<00:10:51.639> that's 00:10:51.829 --> 00:10:51.839 align:start position:0% one of these asset tokens so that's 00:10:51.839 --> 00:10:53.629 align:start position:0% one of these asset tokens so that's actually<00:10:52.079> from<00:10:52.200> the<00:10:52.360> previous<00:10:52.720> example<00:10:53.560> and 00:10:53.629 --> 00:10:53.639 align:start position:0% actually from the previous example and 00:10:53.639 --> 00:10:56.230 align:start position:0% actually from the previous example and you<00:10:53.760> want<00:10:53.839> to<00:10:54.720> sell<00:10:55.000> it<00:10:55.240> buy<00:10:55.440> it<00:10:55.720> exchange<00:10:56.079> it 00:10:56.230 --> 00:10:56.240 align:start position:0% you want to sell it buy it exchange it 00:10:56.240 --> 00:10:58.310 align:start position:0% you want to sell it buy it exchange it for<00:10:56.440> something<00:10:56.720> else<00:10:57.200> so<00:10:57.600> you<00:10:57.720> can<00:10:57.880> set<00:10:58.079> up<00:10:58.200> an 00:10:58.310 --> 00:10:58.320 align:start position:0% for something else so you can set up an 00:10:58.320 --> 00:11:03.030 align:start position:0% for something else so you can set up an exchange<00:10:58.920> on<00:10:59.079> the<00:10:59.320> blockchain<00:11:00.040> itself<00:11:01.519> um<00:11:02.519> you 00:11:03.030 --> 00:11:03.040 align:start position:0% exchange on the blockchain itself um you 00:11:03.040 --> 00:11:05.069 align:start position:0% exchange on the blockchain itself um you you<00:11:03.160> don't<00:11:03.360> need<00:11:03.600> any<00:11:03.800> kind<00:11:03.959> of<00:11:04.560> central 00:11:05.069 --> 00:11:05.079 align:start position:0% you don't need any kind of central 00:11:05.079 --> 00:11:06.829 align:start position:0% you don't need any kind of central websites<00:11:05.720> that<00:11:05.839> will<00:11:06.000> do<00:11:06.160> this<00:11:06.320> exchange<00:11:06.639> for 00:11:06.829 --> 00:11:06.839 align:start position:0% websites that will do this exchange for 00:11:06.839 --> 00:11:09.190 align:start position:0% websites that will do this exchange for you<00:11:07.040> and<00:11:07.200> then<00:11:07.480> lose<00:11:07.720> your<00:11:07.839> money<00:11:08.360> and<00:11:08.639> and<00:11:08.880> and 00:11:09.190 --> 00:11:09.200 align:start position:0% you and then lose your money and and and 00:11:09.200 --> 00:11:11.190 align:start position:0% you and then lose your money and and and run<00:11:09.440> away<00:11:09.680> with<00:11:09.800> it<00:11:10.079> but<00:11:10.200> you<00:11:10.320> can<00:11:10.480> do<00:11:10.880> all<00:11:11.040> of 00:11:11.190 --> 00:11:11.200 align:start position:0% run away with it but you can do all of 00:11:11.200 --> 00:11:13.110 align:start position:0% run away with it but you can do all of this<00:11:11.360> on<00:11:11.480> the 00:11:13.110 --> 00:11:13.120 align:start position:0% this on the 00:11:13.120 --> 00:11:16.870 align:start position:0% this on the blockchain<00:11:14.120> and<00:11:14.839> typically<00:11:15.800> both<00:11:16.160> the<00:11:16.360> assets 00:11:16.870 --> 00:11:16.880 align:start position:0% blockchain and typically both the assets 00:11:16.880 --> 00:11:19.069 align:start position:0% blockchain and typically both the assets for<00:11:17.079> a<00:11:17.240> one-on-one<00:11:17.720> exchange<00:11:18.480> will<00:11:18.680> be<00:11:18.839> one<00:11:18.959> of 00:11:19.069 --> 00:11:19.079 align:start position:0% for a one-on-one exchange will be one of 00:11:19.079 --> 00:11:20.990 align:start position:0% for a one-on-one exchange will be one of these<00:11:19.279> assets<00:11:19.600> on<00:11:19.800> the<00:11:20.040> on<00:11:20.240> the<00:11:20.639> uh<00:11:20.760> on<00:11:20.880> the 00:11:20.990 --> 00:11:21.000 align:start position:0% these assets on the on the uh on the 00:11:21.000 --> 00:11:24.150 align:start position:0% these assets on the on the uh on the blockchain<00:11:22.000> or<00:11:22.720> one<00:11:22.880> of<00:11:23.000> the<00:11:23.120> two<00:11:23.720> could<00:11:23.920> be 00:11:24.150 --> 00:11:24.160 align:start position:0% blockchain or one of the two could be 00:11:24.160 --> 00:11:26.790 align:start position:0% blockchain or one of the two could be just<00:11:24.480> the<00:11:24.639> The<00:11:24.720> Ether<00:11:25.560> currency<00:11:26.200> itself<00:11:26.639> but 00:11:26.790 --> 00:11:26.800 align:start position:0% just the The Ether currency itself but 00:11:26.800 --> 00:11:30.310 align:start position:0% just the The Ether currency itself but that<00:11:27.000> I<00:11:27.160> guess<00:11:27.320> that's<00:11:27.560> less<00:11:28.240> uh<00:11:28.399> less<00:11:28.639> common 00:11:30.310 --> 00:11:30.320 align:start position:0% that I guess that's less uh less common 00:11:30.320 --> 00:11:32.110 align:start position:0% that I guess that's less uh less common and<00:11:30.440> then<00:11:30.680> of<00:11:30.800> course<00:11:30.959> the<00:11:31.079> trick<00:11:31.360> is<00:11:31.920> how<00:11:32.040> are 00:11:32.110 --> 00:11:32.120 align:start position:0% and then of course the trick is how are 00:11:32.120 --> 00:11:34.190 align:start position:0% and then of course the trick is how are you<00:11:32.279> going<00:11:32.399> to<00:11:32.560> do<00:11:32.720> this<00:11:32.959> settlement<00:11:33.959> if<00:11:34.079> you 00:11:34.190 --> 00:11:34.200 align:start position:0% you going to do this settlement if you 00:11:34.200 --> 00:11:36.990 align:start position:0% you going to do this settlement if you have<00:11:34.320> a<00:11:34.440> huge<00:11:34.839> Ledger<00:11:35.839> um<00:11:36.320> maybe<00:11:36.600> it's<00:11:36.800> very 00:11:36.990 --> 00:11:37.000 align:start position:0% have a huge Ledger um maybe it's very 00:11:37.000 --> 00:11:39.750 align:start position:0% have a huge Ledger um maybe it's very good<00:11:37.279> to<00:11:38.040> have<00:11:38.200> the<00:11:38.360> user<00:11:38.680> indicates<00:11:39.399> which<00:11:39.560> is 00:11:39.750 --> 00:11:39.760 align:start position:0% good to have the user indicates which is 00:11:39.760 --> 00:11:41.790 align:start position:0% good to have the user indicates which is the<00:11:40.040> the<00:11:40.120> winning<00:11:40.600> pair<00:11:41.079> and<00:11:41.320> and<00:11:41.480> have<00:11:41.680> have 00:11:41.790 --> 00:11:41.800 align:start position:0% the the winning pair and and have have 00:11:41.800 --> 00:11:43.670 align:start position:0% the the winning pair and and have have it<00:11:41.880> matched<00:11:42.200> that<00:11:42.360> way<00:11:42.959> or<00:11:43.160> you<00:11:43.279> need<00:11:43.440> some 00:11:43.670 --> 00:11:43.680 align:start position:0% it matched that way or you need some 00:11:43.680 --> 00:11:46.389 align:start position:0% it matched that way or you need some kind<00:11:43.839> of<00:11:44.480> external<00:11:44.959> trigger<00:11:45.920> that<00:11:46.079> will<00:11:46.200> be 00:11:46.389 --> 00:11:46.399 align:start position:0% kind of external trigger that will be 00:11:46.399 --> 00:11:48.990 align:start position:0% kind of external trigger that will be called<00:11:47.120> uh<00:11:47.240> to<00:11:47.560> to<00:11:47.720> do<00:11:47.920> the<00:11:48.120> to<00:11:48.320> the<00:11:48.440> matching 00:11:48.990 --> 00:11:49.000 align:start position:0% called uh to to do the to the matching 00:11:49.000 --> 00:11:50.670 align:start position:0% called uh to to do the to the matching and<00:11:49.200> the<00:11:49.320> and<00:11:49.440> the<00:11:49.560> settlement<00:11:50.000> payouts<00:11:50.519> but 00:11:50.670 --> 00:11:50.680 align:start position:0% and the and the settlement payouts but 00:11:50.680 --> 00:11:54.069 align:start position:0% and the and the settlement payouts but that's<00:11:51.240> potentially 00:11:54.069 --> 00:11:54.079 align:start position:0% 00:11:54.079 --> 00:11:56.110 align:start position:0% expensive<00:11:55.079> so<00:11:55.240> what<00:11:55.320> you<00:11:55.440> need<00:11:55.560> to<00:11:55.639> do<00:11:55.839> you 00:11:56.110 --> 00:11:56.120 align:start position:0% expensive so what you need to do you 00:11:56.120 --> 00:11:57.790 align:start position:0% expensive so what you need to do you need<00:11:56.240> to<00:11:56.320> have<00:11:56.440> a<00:11:56.560> contract<00:11:57.040> you<00:11:57.120> need<00:11:57.240> to<00:11:57.399> keep 00:11:57.790 --> 00:11:57.800 align:start position:0% need to have a contract you need to keep 00:11:57.800 --> 00:11:59.829 align:start position:0% need to have a contract you need to keep track<00:11:58.040> of<00:11:58.120> the<00:11:58.240> bits<00:11:58.519> or<00:11:58.680> the<00:11:58.760> Buy<00:11:58.959> orderers 00:11:59.829 --> 00:11:59.839 align:start position:0% track of the bits or the Buy orderers 00:11:59.839 --> 00:12:01.470 align:start position:0% track of the bits or the Buy orderers keep<00:12:00.040> track<00:12:00.240> of<00:12:00.360> all<00:12:00.440> the<00:12:00.560> asks<00:12:00.920> or<00:12:01.079> the<00:12:01.160> sell 00:12:01.470 --> 00:12:01.480 align:start position:0% keep track of all the asks or the sell 00:12:01.480 --> 00:12:03.670 align:start position:0% keep track of all the asks or the sell orders<00:12:02.480> and<00:12:02.720> have<00:12:02.839> some<00:12:03.040> kind<00:12:03.160> of<00:12:03.320> matching 00:12:03.670 --> 00:12:03.680 align:start position:0% orders and have some kind of matching 00:12:03.680 --> 00:12:06.230 align:start position:0% orders and have some kind of matching mechanism<00:12:04.519> and<00:12:04.720> once<00:12:05.320> a<00:12:05.480> bit<00:12:05.680> and<00:12:05.839> ask<00:12:06.120> is 00:12:06.230 --> 00:12:06.240 align:start position:0% mechanism and once a bit and ask is 00:12:06.240 --> 00:12:10.069 align:start position:0% mechanism and once a bit and ask is matched<00:12:07.040> you<00:12:07.839> swap<00:12:08.519> the<00:12:08.720> assets<00:12:09.519> from<00:12:09.760> both 00:12:10.069 --> 00:12:10.079 align:start position:0% matched you swap the assets from both 00:12:10.079 --> 00:12:12.750 align:start position:0% matched you swap the assets from both account<00:12:10.440> holders<00:12:11.120> uh<00:12:11.200> to<00:12:11.360> the<00:12:11.440> other<00:12:11.639> one<00:12:12.560> an 00:12:12.750 --> 00:12:12.760 align:start position:0% account holders uh to the other one an 00:12:12.760 --> 00:12:15.710 align:start position:0% account holders uh to the other one an example<00:12:13.079> of<00:12:13.279> this<00:12:13.519> is<00:12:14.000> uh<00:12:14.320> vitalic<00:12:15.199> Cyber<00:12:15.519> diey 00:12:15.710 --> 00:12:15.720 align:start position:0% example of this is uh vitalic Cyber diey 00:12:15.720 --> 00:12:18.430 align:start position:0% example of this is uh vitalic Cyber diey Markets<00:12:16.639> it's<00:12:16.800> written<00:12:17.160> in<00:12:17.680> serpent<00:12:18.160> instead 00:12:18.430 --> 00:12:18.440 align:start position:0% Markets it's written in serpent instead 00:12:18.440 --> 00:12:20.670 align:start position:0% Markets it's written in serpent instead of<00:12:18.720> solidity<00:12:19.560> so<00:12:19.720> it's<00:12:19.839> a<00:12:19.959> good<00:12:20.199> homework 00:12:20.670 --> 00:12:20.680 align:start position:0% of solidity so it's a good homework 00:12:20.680 --> 00:12:22.389 align:start position:0% of solidity so it's a good homework exercise<00:12:21.079> to<00:12:21.240> try<00:12:21.440> to<00:12:21.639> convert<00:12:22.040> that<00:12:22.199> from 00:12:22.389 --> 00:12:22.399 align:start position:0% exercise to try to convert that from 00:12:22.399 --> 00:12:25.110 align:start position:0% exercise to try to convert that from serpent<00:12:23.279> to<00:12:23.600> uh<00:12:23.680> to<00:12:23.800> solidity<00:12:24.680> and<00:12:24.839> another 00:12:25.110 --> 00:12:25.120 align:start position:0% serpent to uh to solidity and another 00:12:25.120 --> 00:12:27.910 align:start position:0% serpent to uh to solidity and another example<00:12:25.519> is<00:12:25.680> the<00:12:25.880> The<00:12:25.959> Ether<00:12:26.279> x<00:12:27.079> uh 00:12:27.910 --> 00:12:27.920 align:start position:0% example is the The Ether x uh 00:12:27.920 --> 00:12:31.590 align:start position:0% example is the The Ether x uh exchange<00:12:28.920> so<00:12:29.360> an<00:12:29.680> example<00:12:30.680> from<00:12:30.920> a 00:12:31.590 --> 00:12:31.600 align:start position:0% exchange so an example from a 00:12:31.600 --> 00:12:33.990 align:start position:0% exchange so an example from a cyberdine<00:12:32.600> you<00:12:32.680> see<00:12:32.920> there's<00:12:33.040> a<00:12:33.279> buy<00:12:33.560> function 00:12:33.990 --> 00:12:34.000 align:start position:0% cyberdine you see there's a buy function 00:12:34.000 --> 00:12:35.870 align:start position:0% cyberdine you see there's a buy function there's<00:12:34.160> a<00:12:34.240> sell<00:12:34.519> function<00:12:35.240> but<00:12:35.360> you<00:12:35.480> can<00:12:35.639> use 00:12:35.870 --> 00:12:35.880 align:start position:0% there's a sell function but you can use 00:12:35.880 --> 00:12:38.870 align:start position:0% there's a sell function but you can use this<00:12:36.839> this<00:12:37.000> Market<00:12:37.440> this<00:12:37.680> exchange<00:12:38.680> to 00:12:38.870 --> 00:12:38.880 align:start position:0% this this Market this exchange to 00:12:38.880 --> 00:12:42.550 align:start position:0% this this Market this exchange to exchange<00:12:39.519> all<00:12:39.800> kinds<00:12:40.120> of<00:12:41.079> assets<00:12:42.079> that<00:12:42.399> have 00:12:42.550 --> 00:12:42.560 align:start position:0% exchange all kinds of assets that have 00:12:42.560 --> 00:12:44.910 align:start position:0% exchange all kinds of assets that have the<00:12:42.720> same<00:12:43.079> interface<00:12:44.000> without<00:12:44.320> having<00:12:44.519> to 00:12:44.910 --> 00:12:44.920 align:start position:0% the same interface without having to 00:12:44.920 --> 00:12:47.590 align:start position:0% the same interface without having to upfront<00:12:45.920> Implement<00:12:46.480> support<00:12:46.800> for<00:12:47.040> this<00:12:47.399> in 00:12:47.590 --> 00:12:47.600 align:start position:0% upfront Implement support for this in 00:12:47.600 --> 00:12:49.389 align:start position:0% upfront Implement support for this in your<00:12:48.000> in<00:12:48.120> your 00:12:49.389 --> 00:12:49.399 align:start position:0% your in your 00:12:49.399 --> 00:12:51.829 align:start position:0% your in your contracts<00:12:50.399> so<00:12:50.680> the<00:12:51.000> the<00:12:51.160> third<00:12:51.360> and<00:12:51.560> final 00:12:51.829 --> 00:12:51.839 align:start position:0% contracts so the the third and final 00:12:51.839 --> 00:12:53.430 align:start position:0% contracts so the the third and final group<00:12:52.079> that<00:12:52.199> we<00:12:52.279> have<00:12:52.399> seen<00:12:52.680> are<00:12:52.839> these<00:12:53.160> action 00:12:53.430 --> 00:12:53.440 align:start position:0% group that we have seen are these action 00:12:53.440 --> 00:12:54.750 align:start position:0% group that we have seen are these action related 00:12:54.750 --> 00:12:54.760 align:start position:0% related 00:12:54.760 --> 00:12:58.790 align:start position:0% related patterns<00:12:55.760> um<00:12:56.760> event<00:12:57.120> lock<00:12:57.760> so<00:12:57.959> it's<00:12:58.079> a<00:12:58.360> feature 00:12:58.790 --> 00:12:58.800 align:start position:0% patterns um event lock so it's a feature 00:12:58.800 --> 00:13:02.189 align:start position:0% patterns um event lock so it's a feature of<00:12:59.199> the<00:12:59.320> evm<00:12:59.760> itself<00:13:00.160> you<00:13:00.279> can<00:13:00.680> emit<00:13:01.199> events 00:13:02.189 --> 00:13:02.199 align:start position:0% of the evm itself you can emit events 00:13:02.199 --> 00:13:04.550 align:start position:0% of the evm itself you can emit events and<00:13:02.440> they<00:13:02.560> will<00:13:02.760> be<00:13:03.160> persisted<00:13:03.600> on<00:13:03.680> the 00:13:04.550 --> 00:13:04.560 align:start position:0% and they will be persisted on the 00:13:04.560 --> 00:13:07.470 align:start position:0% and they will be persisted on the blockchain<00:13:05.560> and<00:13:06.240> you<00:13:06.399> can<00:13:06.600> use<00:13:06.839> them<00:13:07.000> to<00:13:07.279> to 00:13:07.470 --> 00:13:07.480 align:start position:0% blockchain and you can use them to to 00:13:07.480 --> 00:13:10.509 align:start position:0% blockchain and you can use them to to track<00:13:07.800> state<00:13:08.760> or<00:13:09.320> to<00:13:09.519> track<00:13:09.880> when<00:13:10.160> some<00:13:10.360> kind 00:13:10.509 --> 00:13:10.519 align:start position:0% track state or to track when some kind 00:13:10.519 --> 00:13:12.509 align:start position:0% track state or to track when some kind of<00:13:10.680> action<00:13:10.920> happens<00:13:11.680> and<00:13:11.839> have<00:13:11.959> the<00:13:12.120> outside 00:13:12.509 --> 00:13:12.519 align:start position:0% of action happens and have the outside 00:13:12.519 --> 00:13:14.550 align:start position:0% of action happens and have the outside respond<00:13:12.880> to<00:13:13.040> it<00:13:13.600> there's<00:13:13.800> a<00:13:13.920> limitation 00:13:14.550 --> 00:13:14.560 align:start position:0% respond to it there's a limitation 00:13:14.560 --> 00:13:17.910 align:start position:0% respond to it there's a limitation though<00:13:15.519> with<00:13:16.000> the<00:13:16.120> evm<00:13:17.079> from<00:13:17.279> one<00:13:17.519> contract 00:13:17.910 --> 00:13:17.920 align:start position:0% though with the evm from one contract 00:13:17.920 --> 00:13:20.150 align:start position:0% though with the evm from one contract you<00:13:18.079> cannot<00:13:18.480> inspect<00:13:18.920> the<00:13:19.079> event<00:13:19.399> lock<00:13:19.959> of 00:13:20.150 --> 00:13:20.160 align:start position:0% you cannot inspect the event lock of 00:13:20.160 --> 00:13:21.910 align:start position:0% you cannot inspect the event lock of itself<00:13:20.560> or<00:13:20.720> of<00:13:20.880> another<00:13:21.160> contract<00:13:21.519> so<00:13:21.680> you<00:13:21.760> can 00:13:21.910 --> 00:13:21.920 align:start position:0% itself or of another contract so you can 00:13:21.920 --> 00:13:24.350 align:start position:0% itself or of another contract so you can only<00:13:22.120> use<00:13:22.360> this<00:13:22.560> data<00:13:22.959> from<00:13:23.199> the<00:13:23.360> outside<00:13:24.199> but 00:13:24.350 --> 00:13:24.360 align:start position:0% only use this data from the outside but 00:13:24.360 --> 00:13:27.389 align:start position:0% only use this data from the outside but this<00:13:24.519> makes<00:13:24.720> it<00:13:25.320> ideal<00:13:26.120> for<00:13:26.519> user<00:13:26.880> interface 00:13:27.389 --> 00:13:27.399 align:start position:0% this makes it ideal for user interface 00:13:27.399 --> 00:13:29.230 align:start position:0% this makes it ideal for user interface purposes<00:13:28.320> or<00:13:28.480> if<00:13:28.560> you<00:13:28.680> have<00:13:28.760> some<00:13:28.880> kind<00:13:29.000> of 00:13:29.230 --> 00:13:29.240 align:start position:0% purposes or if you have some kind of 00:13:29.240 --> 00:13:31.150 align:start position:0% purposes or if you have some kind of watch<00:13:29.480> doog<00:13:29.760> process<00:13:30.399> that<00:13:30.519> is<00:13:30.680> looking<00:13:30.959> at 00:13:31.150 --> 00:13:31.160 align:start position:0% watch doog process that is looking at 00:13:31.160 --> 00:13:37.310 align:start position:0% watch doog process that is looking at these<00:13:31.760> event<00:13:32.120> logs<00:13:32.920> and<00:13:33.160> act<00:13:33.760> uh<00:13:33.880> upon 00:13:37.310 --> 00:13:37.320 align:start position:0% 00:13:37.320 --> 00:13:40.470 align:start position:0% them<00:13:38.320> so<00:13:39.000> yeah<00:13:39.079> it's<00:13:39.240> just<00:13:39.360> a<00:13:39.480> single<00:13:39.760> line<00:13:40.000> of 00:13:40.470 --> 00:13:40.480 align:start position:0% them so yeah it's just a single line of 00:13:40.480 --> 00:13:43.310 align:start position:0% them so yeah it's just a single line of solidity<00:13:41.040> code<00:13:41.720> to<00:13:42.199> emit<00:13:42.480> an<00:13:42.639> event<00:13:43.000> if<00:13:43.160> an 00:13:43.310 --> 00:13:43.320 align:start position:0% solidity code to emit an event if an 00:13:43.320 --> 00:13:46.310 align:start position:0% solidity code to emit an event if an action<00:13:43.560> happens<00:13:44.480> and<00:13:44.600> then<00:13:44.760> you<00:13:44.880> have<00:13:45.160> a<00:13:46.160> a 00:13:46.310 --> 00:13:46.320 align:start position:0% action happens and then you have a a 00:13:46.320 --> 00:13:48.710 align:start position:0% action happens and then you have a a listening<00:13:46.839> process<00:13:47.320> or<00:13:47.480> a<00:13:47.600> watching<00:13:48.040> process 00:13:48.710 --> 00:13:48.720 align:start position:0% listening process or a watching process 00:13:48.720 --> 00:13:51.150 align:start position:0% listening process or a watching process in<00:13:48.880> your<00:13:49.000> user<00:13:49.320> interface<00:13:49.959> that<00:13:50.079> will<00:13:50.320> update 00:13:51.150 --> 00:13:51.160 align:start position:0% in your user interface that will update 00:13:51.160 --> 00:13:54.310 align:start position:0% in your user interface that will update its<00:13:51.440> state<00:13:52.079> uh<00:13:52.519> accordingly<00:13:53.519> so<00:13:53.800> examples<00:13:54.160> of 00:13:54.310 --> 00:13:54.320 align:start position:0% its state uh accordingly so examples of 00:13:54.320 --> 00:13:56.790 align:start position:0% its state uh accordingly so examples of this<00:13:54.959> if<00:13:55.079> a<00:13:55.240> buy<00:13:55.440> order<00:13:55.680> took<00:13:55.920> place<00:13:56.240> May<00:13:56.560> on<00:13:56.680> to 00:13:56.790 --> 00:13:56.800 align:start position:0% this if a buy order took place May on to 00:13:56.800 --> 00:13:59.310 align:start position:0% this if a buy order took place May on to update<00:13:57.240> your<00:13:57.399> crowdfunding<00:13:58.040> website<00:13:59.079> if<00:13:59.199> you 00:13:59.310 --> 00:13:59.320 align:start position:0% update your crowdfunding website if you 00:13:59.320 --> 00:14:02.230 align:start position:0% update your crowdfunding website if you just<00:13:59.480> least<00:13:59.920> your<00:14:00.120> car<00:14:00.480> key<00:14:00.880> to<00:14:01.079> somebody<00:14:01.440> else 00:14:02.230 --> 00:14:02.240 align:start position:0% just least your car key to somebody else 00:14:02.240 --> 00:14:04.629 align:start position:0% just least your car key to somebody else you<00:14:02.320> need<00:14:02.480> to<00:14:02.639> change<00:14:03.040> the<00:14:03.360> the<00:14:03.839> the<00:14:04.040> the<00:14:04.160> codes 00:14:04.629 --> 00:14:04.639 align:start position:0% you need to change the the the the codes 00:14:04.639 --> 00:14:07.150 align:start position:0% you need to change the the the the codes the<00:14:04.800> public<00:14:05.079> key<00:14:05.320> on<00:14:05.480> the<00:14:05.639> on<00:14:05.759> the<00:14:05.880> lock<00:14:06.160> system 00:14:07.150 --> 00:14:07.160 align:start position:0% the public key on the on the lock system 00:14:07.160 --> 00:14:09.230 align:start position:0% the public key on the on the lock system if<00:14:07.240> an<00:14:07.399> account<00:14:07.600> is<00:14:07.880> registered<00:14:08.880> maybe<00:14:09.079> some 00:14:09.230 --> 00:14:09.240 align:start position:0% if an account is registered maybe some 00:14:09.240 --> 00:14:11.310 align:start position:0% if an account is registered maybe some other<00:14:09.519> event<00:14:09.839> takes<00:14:10.240> uh<00:14:10.399> takes 00:14:11.310 --> 00:14:11.320 align:start position:0% other event takes uh takes 00:14:11.320 --> 00:14:14.430 align:start position:0% other event takes uh takes place<00:14:12.320> so<00:14:12.959> a<00:14:13.079> good<00:14:13.279> example<00:14:13.680> here<00:14:13.880> is<00:14:14.079> the<00:14:14.320> is 00:14:14.430 --> 00:14:14.440 align:start position:0% place so a good example here is the is 00:14:14.440 --> 00:14:18.509 align:start position:0% place so a good example here is the is the<00:14:14.639> W<00:14:14.880> fund<00:14:15.880> again<00:14:16.160> from<00:14:16.600> uh<00:14:16.720> Nick<00:14:17.320> doson<00:14:18.320> the 00:14:18.509 --> 00:14:18.519 align:start position:0% the W fund again from uh Nick doson the 00:14:18.519 --> 00:14:22.509 align:start position:0% the W fund again from uh Nick doson the wund<00:14:18.959> crowdfunding<00:14:19.959> uh<00:14:20.519> uh<00:14:21.040> contracts<00:14:22.040> so<00:14:22.320> yes 00:14:22.509 --> 00:14:22.519 align:start position:0% wund crowdfunding uh uh contracts so yes 00:14:22.519 --> 00:14:23.670 align:start position:0% wund crowdfunding uh uh contracts so yes these<00:14:22.720> events 00:14:23.670 --> 00:14:23.680 align:start position:0% these events 00:14:23.680 --> 00:14:26.069 align:start position:0% these events for<00:14:24.680> that<00:14:24.839> are<00:14:24.959> emitted<00:14:25.279> when<00:14:25.399> a<00:14:25.519> new<00:14:25.720> c 00:14:26.069 --> 00:14:26.079 align:start position:0% for that are emitted when a new c 00:14:26.079 --> 00:14:28.670 align:start position:0% for that are emitted when a new c campaign<00:14:26.399> is<00:14:26.759> created<00:14:27.519> when<00:14:27.880> a<00:14:28.160> contribution 00:14:28.670 --> 00:14:28.680 align:start position:0% campaign is created when a contribution 00:14:28.680 --> 00:14:30.829 align:start position:0% campaign is created when a contribution is<00:14:28.800> made<00:14:29.160> when<00:14:29.279> a<00:14:29.399> payout<00:14:29.759> happens<00:14:30.440> and<00:14:30.600> even 00:14:30.829 --> 00:14:30.839 align:start position:0% is made when a payout happens and even 00:14:30.839 --> 00:14:33.069 align:start position:0% is made when a payout happens and even when<00:14:30.959> a<00:14:31.120> refund<00:14:31.560> happens<00:14:32.399> maybe<00:14:32.639> he<00:14:32.759> doesn't 00:14:33.069 --> 00:14:33.079 align:start position:0% when a refund happens maybe he doesn't 00:14:33.079 --> 00:14:35.509 align:start position:0% when a refund happens maybe he doesn't even<00:14:33.519> use<00:14:33.880> this<00:14:34.680> these<00:14:34.839> kind<00:14:35.000> of<00:14:35.120> events 00:14:35.509 --> 00:14:35.519 align:start position:0% even use this these kind of events 00:14:35.519 --> 00:14:38.790 align:start position:0% even use this these kind of events himself<00:14:36.360> but<00:14:36.600> by<00:14:36.800> just<00:14:37.079> sharing<00:14:37.560> them<00:14:38.560> you 00:14:38.790 --> 00:14:38.800 align:start position:0% himself but by just sharing them you 00:14:38.800 --> 00:14:41.189 align:start position:0% himself but by just sharing them you allow<00:14:39.519> others<00:14:39.920> to<00:14:40.160> consume<00:14:40.600> them<00:14:40.759> and<00:14:40.880> create 00:14:41.189 --> 00:14:41.199 align:start position:0% allow others to consume them and create 00:14:41.199 --> 00:14:43.310 align:start position:0% allow others to consume them and create all<00:14:41.360> kinds<00:14:41.519> of<00:14:41.680> user<00:14:42.079> interface<00:14:43.079> and 00:14:43.310 --> 00:14:43.320 align:start position:0% all kinds of user interface and 00:14:43.320 --> 00:14:44.670 align:start position:0% all kinds of user interface and interactions<00:14:43.839> with<00:14:44.000> them<00:14:44.160> that<00:14:44.240> you<00:14:44.360> didn't 00:14:44.670 --> 00:14:44.680 align:start position:0% interactions with them that you didn't 00:14:44.680 --> 00:14:47.350 align:start position:0% interactions with them that you didn't think<00:14:44.880> of<00:14:45.560> didn't<00:14:45.839> think<00:14:46.000> of 00:14:47.350 --> 00:14:47.360 align:start position:0% think of didn't think of 00:14:47.360 --> 00:14:49.990 align:start position:0% think of didn't think of yourself<00:14:48.360> so 00:14:49.990 --> 00:14:50.000 align:start position:0% yourself so 00:14:50.000 --> 00:14:54.150 align:start position:0% yourself so um<00:14:51.000> yeah<00:14:52.000> there's<00:14:52.199> a<00:14:52.279> bit<00:14:52.399> of<00:14:52.639> issue<00:14:53.240> with<00:14:54.000> um 00:14:54.150 --> 00:14:54.160 align:start position:0% um yeah there's a bit of issue with um 00:14:54.160 --> 00:14:56.829 align:start position:0% um yeah there's a bit of issue with um ethereum<00:14:54.759> there's<00:14:54.959> no<00:14:55.480> alarm<00:14:55.959> up<00:14:56.240> code<00:14:56.680> you 00:14:56.829 --> 00:14:56.839 align:start position:0% ethereum there's no alarm up code you 00:14:56.839 --> 00:14:59.310 align:start position:0% ethereum there's no alarm up code you cannot<00:14:57.560> trigger<00:14:57.959> some<00:14:58.160> kind<00:14:58.320> of<00:14:58.480> future<00:14:59.079> event 00:14:59.310 --> 00:14:59.320 align:start position:0% cannot trigger some kind of future event 00:14:59.320 --> 00:15:03.430 align:start position:0% cannot trigger some kind of future event to<00:14:59.560> happen<00:15:00.399> automatically<00:15:01.399> um<00:15:01.600> so<00:15:01.920> it<00:15:02.440> every 00:15:03.430 --> 00:15:03.440 align:start position:0% to happen automatically um so it every 00:15:03.440 --> 00:15:05.670 align:start position:0% to happen automatically um so it every every<00:15:03.800> action<00:15:04.240> in<00:15:04.360> a<00:15:04.519> contract<00:15:04.959> needs<00:15:05.160> to<00:15:05.320> be 00:15:05.670 --> 00:15:05.680 align:start position:0% every action in a contract needs to be 00:15:05.680 --> 00:15:07.749 align:start position:0% every action in a contract needs to be triggered<00:15:06.120> by<00:15:06.240> a<00:15:06.360> transaction<00:15:06.839> that<00:15:07.040> is 00:15:07.749 --> 00:15:07.759 align:start position:0% triggered by a transaction that is 00:15:07.759 --> 00:15:09.990 align:start position:0% triggered by a transaction that is eventually<00:15:08.160> being<00:15:08.360> sent<00:15:08.720> from<00:15:08.959> a<00:15:09.120> from<00:15:09.240> a<00:15:09.360> user 00:15:09.990 --> 00:15:10.000 align:start position:0% eventually being sent from a from a user 00:15:10.000 --> 00:15:11.629 align:start position:0% eventually being sent from a from a user so<00:15:10.279> what<00:15:10.800> what<00:15:10.920> if<00:15:11.079> something<00:15:11.320> needs<00:15:11.519> to 00:15:11.629 --> 00:15:11.639 align:start position:0% so what what if something needs to 00:15:11.639 --> 00:15:13.030 align:start position:0% so what what if something needs to happen<00:15:11.880> in<00:15:12.000> the<00:15:12.120> future<00:15:12.440> how<00:15:12.560> are<00:15:12.680> you<00:15:12.800> going 00:15:13.030 --> 00:15:13.040 align:start position:0% happen in the future how are you going 00:15:13.040 --> 00:15:15.470 align:start position:0% happen in the future how are you going to<00:15:13.680> to<00:15:13.880> make<00:15:14.079> sure<00:15:14.639> that<00:15:14.839> is<00:15:15.120> that<00:15:15.279> this 00:15:15.470 --> 00:15:15.480 align:start position:0% to to make sure that is that this 00:15:15.480 --> 00:15:17.870 align:start position:0% to to make sure that is that this happens<00:15:16.160> an<00:15:16.320> example<00:15:16.720> for<00:15:16.959> this<00:15:17.079> are<00:15:17.680> if<00:15:17.759> you 00:15:17.870 --> 00:15:17.880 align:start position:0% happens an example for this are if you 00:15:17.880 --> 00:15:19.629 align:start position:0% happens an example for this are if you need<00:15:18.040> some<00:15:18.240> kind<00:15:18.399> of<00:15:19.199> I<00:15:19.279> don't<00:15:19.440> know 00:15:19.629 --> 00:15:19.639 align:start position:0% need some kind of I don't know 00:15:19.639 --> 00:15:22.310 align:start position:0% need some kind of I don't know expiration<00:15:20.320> of<00:15:20.519> your<00:15:20.920> of<00:15:21.079> your<00:15:21.880> um<00:15:22.079> of<00:15:22.199> your 00:15:22.310 --> 00:15:22.320 align:start position:0% expiration of your of your um of your 00:15:22.320 --> 00:15:25.790 align:start position:0% expiration of your of your um of your lottery<00:15:23.000> tickets<00:15:23.880> doing<00:15:24.839> frequent<00:15:25.320> dividend 00:15:25.790 --> 00:15:25.800 align:start position:0% lottery tickets doing frequent dividend 00:15:25.800 --> 00:15:28.509 align:start position:0% lottery tickets doing frequent dividend payouts<00:15:26.639> other<00:15:26.920> kinds<00:15:27.120> of<00:15:27.519> cleanups<00:15:28.360> how<00:15:28.480> are 00:15:28.509 --> 00:15:28.519 align:start position:0% payouts other kinds of cleanups how are 00:15:28.519 --> 00:15:30.189 align:start position:0% payouts other kinds of cleanups how are you<00:15:28.639> going<00:15:28.759> to<00:15:29.040> make<00:15:29.160> sure<00:15:29.399> that<00:15:29.560> this<00:15:29.720> will 00:15:30.189 --> 00:15:30.199 align:start position:0% you going to make sure that this will 00:15:30.199 --> 00:15:32.949 align:start position:0% you going to make sure that this will that<00:15:30.360> this<00:15:30.480> will<00:15:30.800> happen<00:15:31.800> so<00:15:32.319> the<00:15:32.519> solution 00:15:32.949 --> 00:15:32.959 align:start position:0% that this will happen so the solution 00:15:32.959 --> 00:15:36.389 align:start position:0% that this will happen so the solution here<00:15:33.600> is<00:15:33.759> to<00:15:34.279> to<00:15:34.480> reward<00:15:35.279> the<00:15:35.440> collar<00:15:36.160> for 00:15:36.389 --> 00:15:36.399 align:start position:0% here is to to reward the collar for 00:15:36.399 --> 00:15:38.350 align:start position:0% here is to to reward the collar for actually<00:15:36.639> trigging<00:15:37.160> this<00:15:37.319> mechanism<00:15:38.040> so<00:15:38.199> you 00:15:38.350 --> 00:15:38.360 align:start position:0% actually trigging this mechanism so you 00:15:38.360 --> 00:15:41.230 align:start position:0% actually trigging this mechanism so you create<00:15:39.160> a<00:15:39.279> function<00:15:39.839> anybody<00:15:40.639> can<00:15:40.800> trigger 00:15:41.230 --> 00:15:41.240 align:start position:0% create a function anybody can trigger 00:15:41.240 --> 00:15:43.550 align:start position:0% create a function anybody can trigger this<00:15:41.880> but<00:15:42.040> once<00:15:42.240> they<00:15:42.399> do<00:15:42.639> this<00:15:43.160> they<00:15:43.319> get 00:15:43.550 --> 00:15:43.560 align:start position:0% this but once they do this they get 00:15:43.560 --> 00:15:46.350 align:start position:0% this but once they do this they get rewarded<00:15:44.360> for<00:15:44.600> doing<00:15:44.959> so<00:15:45.639> and<00:15:45.880> that<00:15:46.040> way<00:15:46.199> you 00:15:46.350 --> 00:15:46.360 align:start position:0% rewarded for doing so and that way you 00:15:46.360 --> 00:15:48.269 align:start position:0% rewarded for doing so and that way you hope<00:15:47.079> of<00:15:47.199> course<00:15:47.360> you<00:15:47.480> cannot<00:15:47.759> guarantee<00:15:48.160> that 00:15:48.269 --> 00:15:48.279 align:start position:0% hope of course you cannot guarantee that 00:15:48.279 --> 00:15:49.870 align:start position:0% hope of course you cannot guarantee that somebody<00:15:48.519> will<00:15:48.680> do<00:15:48.839> it<00:15:49.040> but<00:15:49.199> they<00:15:49.319> have<00:15:49.440> a 00:15:49.870 --> 00:15:49.880 align:start position:0% somebody will do it but they have a 00:15:49.880 --> 00:15:51.949 align:start position:0% somebody will do it but they have a strong<00:15:50.079> economic<00:15:50.560> incentive<00:15:51.319> for<00:15:51.519> triggering 00:15:51.949 --> 00:15:51.959 align:start position:0% strong economic incentive for triggering 00:15:51.959 --> 00:15:53.910 align:start position:0% strong economic incentive for triggering this<00:15:52.120> method<00:15:52.440> and<00:15:52.560> making<00:15:52.759> sure<00:15:53.440> that<00:15:53.560> it<00:15:53.720> will 00:15:53.910 --> 00:15:53.920 align:start position:0% this method and making sure that it will 00:15:53.920 --> 00:15:55.910 align:start position:0% this method and making sure that it will be<00:15:54.279> uh<00:15:54.440> that<00:15:54.519> it<00:15:54.600> will<00:15:54.759> be 00:15:55.910 --> 00:15:55.920 align:start position:0% be uh that it will be 00:15:55.920 --> 00:15:59.550 align:start position:0% be uh that it will be called<00:15:56.920> so<00:15:57.120> an<00:15:57.279> example<00:15:57.720> here<00:15:57.959> from<00:15:58.319> uh<00:15:58.519> gin<00:15:59.319> uh 00:15:59.550 --> 00:15:59.560 align:start position:0% called so an example here from uh gin uh 00:15:59.560 --> 00:16:03.749 align:start position:0% called so an example here from uh gin uh casino<00:16:00.240> contract<00:16:01.120> is<00:16:01.360> this<00:16:01.920> recycle<00:16:02.759> method 00:16:03.749 --> 00:16:03.759 align:start position:0% casino contract is this recycle method 00:16:03.759 --> 00:16:06.350 align:start position:0% casino contract is this recycle method which<00:16:04.240> anybody<00:16:04.600> can<00:16:04.839> trigger 00:16:06.350 --> 00:16:06.360 align:start position:0% which anybody can trigger 00:16:06.360 --> 00:16:08.590 align:start position:0% which anybody can trigger and<00:16:07.360> if<00:16:07.480> there's<00:16:07.680> some<00:16:07.839> kind<00:16:07.959> of<00:16:08.120> expiration 00:16:08.590 --> 00:16:08.600 align:start position:0% and if there's some kind of expiration 00:16:08.600 --> 00:16:10.309 align:start position:0% and if there's some kind of expiration event<00:16:09.000> the<00:16:09.160> person<00:16:09.480> that<00:16:09.600> was<00:16:09.720> trigging<00:16:10.120> this 00:16:10.309 --> 00:16:10.319 align:start position:0% event the person that was trigging this 00:16:10.319 --> 00:16:13.870 align:start position:0% event the person that was trigging this get<00:16:10.519> rewarded<00:16:11.279> with<00:16:11.480> half<00:16:11.720> a<00:16:11.920> percent<00:16:12.880> of<00:16:13.120> the 00:16:13.870 --> 00:16:13.880 align:start position:0% get rewarded with half a percent of the 00:16:13.880 --> 00:16:17.309 align:start position:0% get rewarded with half a percent of the of<00:16:14.040> the<00:16:14.199> of<00:16:14.319> the<00:16:14.399> funds<00:16:14.839> so<00:16:15.600> makes<00:16:15.839> sense 00:16:17.309 --> 00:16:17.319 align:start position:0% of the of the funds so makes sense 00:16:17.319 --> 00:16:20.309 align:start position:0% of the of the funds so makes sense there<00:16:18.319> so<00:16:18.680> combining<00:16:19.120> these<00:16:19.279> things<00:16:19.639> together 00:16:20.309 --> 00:16:20.319 align:start position:0% there so combining these things together 00:16:20.319 --> 00:16:22.509 align:start position:0% there so combining these things together you<00:16:20.519> can<00:16:21.360> come<00:16:21.560> up<00:16:21.680> with<00:16:21.800> all<00:16:21.920> kinds<00:16:22.079> of<00:16:22.199> use 00:16:22.509 --> 00:16:22.519 align:start position:0% you can come up with all kinds of use 00:16:22.519 --> 00:16:24.590 align:start position:0% you can come up with all kinds of use cases<00:16:23.160> so<00:16:23.360> say<00:16:23.560> you<00:16:23.680> have<00:16:23.839> a<00:16:24.079> a<00:16:24.199> betting 00:16:24.590 --> 00:16:24.600 align:start position:0% cases so say you have a a betting 00:16:24.600 --> 00:16:26.550 align:start position:0% cases so say you have a a betting website<00:16:25.600> where<00:16:25.759> you<00:16:25.839> want<00:16:26.000> to<00:16:26.199> allow<00:16:26.440> your 00:16:26.550 --> 00:16:26.560 align:start position:0% website where you want to allow your 00:16:26.560 --> 00:16:29.269 align:start position:0% website where you want to allow your users<00:16:26.880> to<00:16:27.040> bet<00:16:27.279> on<00:16:27.399> soccer<00:16:27.920> scores<00:16:28.959> you<00:16:29.160> you 00:16:29.269 --> 00:16:29.279 align:start position:0% users to bet on soccer scores you you 00:16:29.279 --> 00:16:31.309 align:start position:0% users to bet on soccer scores you you would<00:16:29.440> use<00:16:29.560> a<00:16:29.759> name<00:16:30.000> registry<00:16:30.680> to<00:16:30.839> keep<00:16:31.040> track 00:16:31.309 --> 00:16:31.319 align:start position:0% would use a name registry to keep track 00:16:31.319 --> 00:16:32.949 align:start position:0% would use a name registry to keep track of<00:16:31.519> the<00:16:31.720> the<00:16:31.839> different<00:16:32.120> usernames<00:16:32.720> so<00:16:32.839> you 00:16:32.949 --> 00:16:32.959 align:start position:0% of the the different usernames so you 00:16:32.959 --> 00:16:36.069 align:start position:0% of the the different usernames so you can<00:16:33.120> have<00:16:33.279> a<00:16:33.759> a<00:16:33.959> top<00:16:34.440> a<00:16:34.600> top<00:16:34.759> scoring<00:16:35.199> list<00:16:35.839> High 00:16:36.069 --> 00:16:36.079 align:start position:0% can have a a top a top scoring list High 00:16:36.079 --> 00:16:38.350 align:start position:0% can have a a top a top scoring list High all<00:16:36.399> Fame<00:16:36.680> on<00:16:36.880> your<00:16:37.199> on<00:16:37.360> your<00:16:37.680> on<00:16:37.800> your<00:16:37.959> site<00:16:38.240> of 00:16:38.350 --> 00:16:38.360 align:start position:0% all Fame on your on your on your site of 00:16:38.360 --> 00:16:41.230 align:start position:0% all Fame on your on your on your site of on<00:16:38.480> your<00:16:38.720> da<00:16:39.720> need<00:16:39.920> some<00:16:40.079> kind<00:16:40.240> of<00:16:40.360> data<00:16:40.639> feed 00:16:41.230 --> 00:16:41.240 align:start position:0% on your da need some kind of data feed 00:16:41.240 --> 00:16:43.150 align:start position:0% on your da need some kind of data feed to<00:16:41.399> know<00:16:41.800> which<00:16:41.959> soer<00:16:42.319> events<00:16:42.639> happened<00:16:43.000> and 00:16:43.150 --> 00:16:43.160 align:start position:0% to know which soer events happened and 00:16:43.160 --> 00:16:47.470 align:start position:0% to know which soer events happened and what<00:16:43.279> scoring<00:16:43.800> was<00:16:44.240> was<00:16:44.639> there<00:16:45.639> um<00:16:46.560> event<00:16:46.920> lock 00:16:47.470 --> 00:16:47.480 align:start position:0% what scoring was was there um event lock 00:16:47.480 --> 00:16:49.470 align:start position:0% what scoring was was there um event lock so<00:16:47.920> if<00:16:48.079> somebody<00:16:48.440> takes<00:16:48.639> a<00:16:48.839> bet<00:16:49.079> or<00:16:49.240> if<00:16:49.319> you 00:16:49.470 --> 00:16:49.480 align:start position:0% so if somebody takes a bet or if you 00:16:49.480 --> 00:16:51.509 align:start position:0% so if somebody takes a bet or if you want<00:16:50.199> you<00:16:50.319> want<00:16:50.440> to<00:16:50.600> update<00:16:51.120> again<00:16:51.319> your 00:16:51.509 --> 00:16:51.519 align:start position:0% want you want to update again your 00:16:51.519 --> 00:16:53.110 align:start position:0% want you want to update again your website<00:16:51.880> or<00:16:52.040> your<00:16:52.240> dep<00:16:52.440> accordingly<00:16:52.880> so<00:16:53.000> you 00:16:53.110 --> 00:16:53.120 align:start position:0% website or your dep accordingly so you 00:16:53.120 --> 00:16:55.550 align:start position:0% website or your dep accordingly so you use<00:16:53.360> event<00:16:53.639> lock<00:16:53.880> to<00:16:54.000> get<00:16:54.160> the<00:16:54.279> output<00:16:55.199> uh<00:16:55.319> from 00:16:55.550 --> 00:16:55.560 align:start position:0% use event lock to get the output uh from 00:16:55.560 --> 00:16:58.069 align:start position:0% use event lock to get the output uh from that<00:16:56.199> so<00:16:56.639> already<00:16:56.920> you<00:16:57.000> see<00:16:57.240> with<00:16:57.759> such<00:16:57.920> a 00:16:58.069 --> 00:16:58.079 align:start position:0% that so already you see with such a 00:16:58.079 --> 00:17:00.030 align:start position:0% that so already you see with such a system<00:16:58.319> you're<00:16:58.519> combining<00:16:59.040> ing<00:16:59.440> multiple<00:16:59.839> of 00:17:00.030 --> 00:17:00.040 align:start position:0% system you're combining ing multiple of 00:17:00.040 --> 00:17:01.470 align:start position:0% system you're combining ing multiple of these<00:17:00.399> patterns 00:17:01.470 --> 00:17:01.480 align:start position:0% these patterns 00:17:01.480 --> 00:17:04.710 align:start position:0% these patterns together<00:17:02.480> um<00:17:02.759> again<00:17:02.920> for<00:17:03.280> Market<00:17:04.280> if<00:17:04.360> you<00:17:04.439> have 00:17:04.710 --> 00:17:04.720 align:start position:0% together um again for Market if you have 00:17:04.720 --> 00:17:06.630 align:start position:0% together um again for Market if you have some<00:17:04.880> kind<00:17:05.000> of<00:17:05.240> manufacturing<00:17:05.919> site<00:17:06.199> and<00:17:06.439> you 00:17:06.630 --> 00:17:06.640 align:start position:0% some kind of manufacturing site and you 00:17:06.640 --> 00:17:08.350 align:start position:0% some kind of manufacturing site and you do<00:17:06.880> some<00:17:07.039> kind<00:17:07.160> of<00:17:07.280> internal<00:17:07.679> research 00:17:08.350 --> 00:17:08.360 align:start position:0% do some kind of internal research 00:17:08.360 --> 00:17:10.870 align:start position:0% do some kind of internal research optimization<00:17:09.360> you<00:17:09.520> can<00:17:09.679> try<00:17:09.880> to<00:17:10.199> centralize 00:17:10.870 --> 00:17:10.880 align:start position:0% optimization you can try to centralize 00:17:10.880 --> 00:17:12.590 align:start position:0% optimization you can try to centralize this<00:17:11.280> but<00:17:11.400> you<00:17:11.480> can<00:17:11.640> also<00:17:11.799> think<00:17:12.000> about<00:17:12.319> can<00:17:12.439> we 00:17:12.590 --> 00:17:12.600 align:start position:0% this but you can also think about can we 00:17:12.600 --> 00:17:16.150 align:start position:0% this but you can also think about can we do<00:17:12.799> this<00:17:13.120> on<00:17:13.360> the<00:17:13.760> on<00:17:13.919> the<00:17:14.360> blockchain<00:17:15.360> using 00:17:16.150 --> 00:17:16.160 align:start position:0% do this on the on the blockchain using 00:17:16.160 --> 00:17:18.949 align:start position:0% do this on the on the blockchain using asset<00:17:16.520> token<00:17:16.839> to<00:17:17.000> indicate<00:17:17.720> resources<00:17:18.720> having 00:17:18.949 --> 00:17:18.959 align:start position:0% asset token to indicate resources having 00:17:18.959 --> 00:17:21.029 align:start position:0% asset token to indicate resources having a<00:17:19.280> exchange<00:17:19.720> contract<00:17:20.160> where<00:17:20.319> people<00:17:20.559> can<00:17:20.760> bid 00:17:21.029 --> 00:17:21.039 align:start position:0% a exchange contract where people can bid 00:17:21.039 --> 00:17:23.750 align:start position:0% a exchange contract where people can bid and<00:17:21.240> ask<00:17:21.520> for<00:17:21.880> for<00:17:22.319> resources<00:17:23.319> and<00:17:23.400> then<00:17:23.559> of 00:17:23.750 --> 00:17:23.760 align:start position:0% and ask for for resources and then of 00:17:23.760 --> 00:17:25.710 align:start position:0% and ask for for resources and then of course<00:17:24.319> having<00:17:24.600> some<00:17:24.799> kind<00:17:24.919> of<00:17:25.120> incentivized 00:17:25.710 --> 00:17:25.720 align:start position:0% course having some kind of incentivized 00:17:25.720 --> 00:17:28.189 align:start position:0% course having some kind of incentivized trigger<00:17:26.400> for<00:17:27.079> making<00:17:27.360> sure<00:17:27.640> that<00:17:27.799> frequent 00:17:28.189 --> 00:17:28.199 align:start position:0% trigger for making sure that frequent 00:17:28.199 --> 00:17:32.070 align:start position:0% trigger for making sure that frequent updates<00:17:28.919> such<00:17:29.120> as<00:17:29.320> Market<00:17:29.679> settlements 00:17:32.070 --> 00:17:32.080 align:start position:0% updates such as Market settlements 00:17:32.080 --> 00:17:36.350 align:start position:0% updates such as Market settlements happen<00:17:33.080> and<00:17:33.360> another<00:17:34.160> example<00:17:35.160> um<00:17:35.520> is<00:17:36.160> if<00:17:36.280> you 00:17:36.350 --> 00:17:36.360 align:start position:0% happen and another example um is if you 00:17:36.360 --> 00:17:38.190 align:start position:0% happen and another example um is if you want<00:17:36.520> to<00:17:36.640> have<00:17:36.760> your<00:17:36.960> dep<00:17:37.240> interact<00:17:37.840> with<00:17:38.080> with 00:17:38.190 --> 00:17:38.200 align:start position:0% want to have your dep interact with with 00:17:38.200 --> 00:17:41.029 align:start position:0% want to have your dep interact with with real<00:17:38.559> Hardware<00:17:39.559> so<00:17:40.120> in<00:17:40.280> this<00:17:40.480> case<00:17:40.720> it's<00:17:40.880> a 00:17:41.029 --> 00:17:41.039 align:start position:0% real Hardware so in this case it's a 00:17:41.039 --> 00:17:43.430 align:start position:0% real Hardware so in this case it's a smart<00:17:41.280> meter<00:17:41.760> in<00:17:41.919> my<00:17:42.400> utility<00:17:42.840> closet<00:17:43.240> that<00:17:43.360> I 00:17:43.430 --> 00:17:43.440 align:start position:0% smart meter in my utility closet that I 00:17:43.440 --> 00:17:45.590 align:start position:0% smart meter in my utility closet that I connect<00:17:43.720> with<00:17:43.880> my<00:17:44.000> ethereum<00:17:44.440> Rasberry<00:17:44.960> Pi<00:17:45.440> I 00:17:45.590 --> 00:17:45.600 align:start position:0% connect with my ethereum Rasberry Pi I 00:17:45.600 --> 00:17:49.029 align:start position:0% connect with my ethereum Rasberry Pi I get<00:17:45.840> data<00:17:46.080> out<00:17:46.200> of<00:17:46.360> it<00:17:47.320> um<00:17:48.000> but<00:17:48.480> how<00:17:48.679> how<00:17:48.760> do<00:17:48.880> I 00:17:49.029 --> 00:17:49.039 align:start position:0% get data out of it um but how how do I 00:17:49.039 --> 00:17:51.150 align:start position:0% get data out of it um but how how do I know<00:17:49.520> that<00:17:49.720> this<00:17:49.919> device<00:17:50.280> belongs<00:17:50.600> to<00:17:50.760> me<00:17:50.919> so<00:17:51.039> I 00:17:51.150 --> 00:17:51.160 align:start position:0% know that this device belongs to me so I 00:17:51.160 --> 00:17:54.590 align:start position:0% know that this device belongs to me so I need<00:17:51.320> some<00:17:51.520> kind<00:17:51.679> of<00:17:52.640> notary<00:17:53.640> data<00:17:53.960> pattern 00:17:54.590 --> 00:17:54.600 align:start position:0% need some kind of notary data pattern 00:17:54.600 --> 00:17:57.230 align:start position:0% need some kind of notary data pattern that<00:17:54.880> that<00:17:55.200> that<00:17:55.440> makes<00:17:55.760> this<00:17:56.159> Association<00:17:57.159> I 00:17:57.230 --> 00:17:57.240 align:start position:0% that that that makes this Association I 00:17:57.240 --> 00:18:00.270 align:start position:0% that that that makes this Association I have<00:17:57.400> this<00:17:57.600> data<00:17:57.799> feeds<00:17:58.520> so<00:17:59.039> for 00:18:00.270 --> 00:18:00.280 align:start position:0% have this data feeds so for 00:18:00.280 --> 00:18:03.630 align:start position:0% have this data feeds so for every<00:18:01.280> energy<00:18:01.840> consumption<00:18:02.520> update<00:18:03.400> uh<00:18:03.480> a 00:18:03.630 --> 00:18:03.640 align:start position:0% every energy consumption update uh a 00:18:03.640 --> 00:18:05.669 align:start position:0% every energy consumption update uh a contract<00:18:04.000> is<00:18:04.159> updated<00:18:04.679> with<00:18:04.880> my<00:18:05.280> uh<00:18:05.400> data 00:18:05.669 --> 00:18:05.679 align:start position:0% contract is updated with my uh data 00:18:05.679 --> 00:18:08.029 align:start position:0% contract is updated with my uh data usage<00:18:06.640> and<00:18:06.880> if<00:18:06.960> I<00:18:07.080> want<00:18:07.159> to<00:18:07.320> display<00:18:07.720> this<00:18:07.880> in 00:18:08.029 --> 00:18:08.039 align:start position:0% usage and if I want to display this in 00:18:08.039 --> 00:18:12.029 align:start position:0% usage and if I want to display this in my<00:18:08.200> dep<00:18:08.840> I<00:18:08.960> need<00:18:09.120> to<00:18:09.840> emit<00:18:10.280> event<00:18:10.799> locks<00:18:11.799> um 00:18:12.029 --> 00:18:12.039 align:start position:0% my dep I need to emit event locks um 00:18:12.039 --> 00:18:14.230 align:start position:0% my dep I need to emit event locks um using<00:18:12.360> the<00:18:12.520> event<00:18:12.799> lock 00:18:14.230 --> 00:18:14.240 align:start position:0% using the event lock 00:18:14.240 --> 00:18:18.510 align:start position:0% using the event lock pattern<00:18:15.600> so<00:18:16.600> what's<00:18:16.880> next<00:18:17.280> for<00:18:17.480> you<00:18:17.720> guys<00:18:18.360> take 00:18:18.510 --> 00:18:18.520 align:start position:0% pattern so what's next for you guys take 00:18:18.520 --> 00:18:20.789 align:start position:0% pattern so what's next for you guys take a<00:18:18.679> look<00:18:18.840> at<00:18:19.159> existing<00:18:19.840> codes<00:18:20.159> in<00:18:20.320> GitHub 00:18:20.789 --> 00:18:20.799 align:start position:0% a look at existing codes in GitHub 00:18:20.799 --> 00:18:22.990 align:start position:0% a look at existing codes in GitHub existing<00:18:21.159> contracts<00:18:21.640> study<00:18:22.039> them<00:18:22.520> and<00:18:22.679> see 00:18:22.990 --> 00:18:23.000 align:start position:0% existing contracts study them and see 00:18:23.000 --> 00:18:25.390 align:start position:0% existing contracts study them and see what<00:18:23.159> kind<00:18:23.320> of<00:18:23.480> common<00:18:23.799> patterns<00:18:24.799> do<00:18:25.000> you<00:18:25.280> do 00:18:25.390 --> 00:18:25.400 align:start position:0% what kind of common patterns do you do 00:18:25.400 --> 00:18:28.029 align:start position:0% what kind of common patterns do you do you<00:18:25.520> see<00:18:25.799> do<00:18:25.919> you<00:18:26.120> you<00:18:26.520> are<00:18:26.720> used<00:18:27.200> and<00:18:27.400> and<00:18:27.640> can 00:18:28.029 --> 00:18:28.039 align:start position:0% you see do you you are used and and can 00:18:28.039 --> 00:18:29.630 align:start position:0% you see do you you are used and and can be<00:18:28.240> used<00:18:28.520> re<00:18:28.799> use<00:18:28.960> for 00:18:29.630 --> 00:18:29.640 align:start position:0% be used re use for 00:18:29.640 --> 00:18:31.669 align:start position:0% be used re use for yourself<00:18:30.640> and 00:18:31.669 --> 00:18:31.679 align:start position:0% yourself and 00:18:31.679 --> 00:18:34.549 align:start position:0% yourself and also<00:18:32.679> we're<00:18:32.880> trying<00:18:33.360> as<00:18:33.480> a<00:18:33.640> community<00:18:34.120> effort 00:18:34.549 --> 00:18:34.559 align:start position:0% also we're trying as a community effort 00:18:34.559 --> 00:18:37.630 align:start position:0% also we're trying as a community effort to<00:18:34.799> get<00:18:35.039> this<00:18:35.919> uh<00:18:36.280> stack<00:18:36.679> overflow<00:18:37.320> stack 00:18:37.630 --> 00:18:37.640 align:start position:0% to get this uh stack overflow stack 00:18:37.640 --> 00:18:41.029 align:start position:0% to get this uh stack overflow stack exchange<00:18:38.039> site<00:18:38.320> setup<00:18:38.760> for<00:18:39.159> E<00:18:39.720> ethereum<00:18:40.720> so<00:18:40.960> if 00:18:41.029 --> 00:18:41.039 align:start position:0% exchange site setup for E ethereum so if 00:18:41.039 --> 00:18:43.310 align:start position:0% exchange site setup for E ethereum so if you<00:18:41.159> go<00:18:41.280> to<00:18:41.480> Area<00:18:41.840> 51<00:18:42.400> on<00:18:42.559> the<00:18:42.679> stack<00:18:42.919> exchange 00:18:43.310 --> 00:18:43.320 align:start position:0% you go to Area 51 on the stack exchange 00:18:43.320 --> 00:18:45.430 align:start position:0% you go to Area 51 on the stack exchange please<00:18:43.520> vote<00:18:43.760> for<00:18:43.919> it<00:18:44.520> as<00:18:44.640> of<00:18:44.840> this<00:18:45.000> morning<00:18:45.320> I 00:18:45.430 --> 00:18:45.440 align:start position:0% please vote for it as of this morning I 00:18:45.440 --> 00:18:49.950 align:start position:0% please vote for it as of this morning I think<00:18:45.559> we<00:18:45.679> were<00:18:45.799> at<00:18:46.679> n<00:18:47.679> um<00:18:48.159> almost<00:18:48.640> 70%<00:18:49.640> so<00:18:49.840> a 00:18:49.950 --> 00:18:49.960 align:start position:0% think we were at n um almost 70% so a 00:18:49.960 --> 00:18:51.590 align:start position:0% think we were at n um almost 70% so a couple<00:18:50.200> more<00:18:50.360> votes<00:18:51.120> and<00:18:51.240> we<00:18:51.320> have<00:18:51.440> a 00:18:51.590 --> 00:18:51.600 align:start position:0% couple more votes and we have a 00:18:51.600 --> 00:18:53.630 align:start position:0% couple more votes and we have a community<00:18:52.000> site<00:18:52.320> for<00:18:52.480> all<00:18:52.640> kinds<00:18:52.840> of<00:18:53.000> Q&A<00:18:53.520> all 00:18:53.630 --> 00:18:53.640 align:start position:0% community site for all kinds of Q&A all 00:18:53.640 --> 00:18:55.669 align:start position:0% community site for all kinds of Q&A all kinds<00:18:53.840> of<00:18:54.000> discussions<00:18:55.000> around<00:18:55.440> best 00:18:55.669 --> 00:18:55.679 align:start position:0% kinds of discussions around best 00:18:55.679 --> 00:18:58.350 align:start position:0% kinds of discussions around best practices<00:18:56.559> about<00:18:56.840> patterns<00:18:57.640> sharing<00:18:58.080> code 00:18:58.350 --> 00:18:58.360 align:start position:0% practices about patterns sharing code 00:18:58.360 --> 00:19:00.029 align:start position:0% practices about patterns sharing code sharing<00:18:58.799> knowled<00:18:59.039> with<00:18:59.159> each<00:18:59.320> other<00:18:59.760> and<00:18:59.919> this 00:19:00.029 --> 00:19:00.039 align:start position:0% sharing knowled with each other and this 00:19:00.039 --> 00:19:02.990 align:start position:0% sharing knowled with each other and this would<00:19:00.159> be<00:19:00.280> a<00:19:00.679> great<00:19:00.960> place<00:19:01.559> to<00:19:01.799> exchange<00:19:02.720> uh 00:19:02.990 --> 00:19:03.000 align:start position:0% would be a great place to exchange uh 00:19:03.000 --> 00:19:06.230 align:start position:0% would be a great place to exchange uh ethereum<00:19:03.840> or<00:19:04.080> Deb<00:19:04.960> patterns<00:19:05.400> as<00:19:05.520> well<00:19:06.080> thank 00:19:06.230 --> 00:19:06.240 align:start position:0% ethereum or Deb patterns as well thank 00:19:06.240 --> 00:19:14.940 align:start position:0% ethereum or Deb patterns as well thank you<00:19:06.480> guys 00:19:14.940 --> 00:19:14.950 align:start position:0% 00:19:14.950 --> 00:19:19.279 align:start position:0% [Music]