WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:19.660 align:start position:0% [Applause] 00:00:19.660 --> 00:00:19.670 align:start position:0% 00:00:19.670 --> 00:00:24.720 align:start position:0% just 00:00:24.720 --> 00:00:24.730 align:start position:0% 00:00:24.730 --> 00:00:28.230 align:start position:0% a<00:00:25.170> little<00:00:26.170> bit<00:00:26.260> of<00:00:26.350> ourselves<00:00:26.470> so<00:00:27.310> we<00:00:27.940> are<00:00:28.060> from 00:00:28.230 --> 00:00:28.240 align:start position:0% a little bit of ourselves so we are from 00:00:28.240 --> 00:00:30.440 align:start position:0% a little bit of ourselves so we are from Table<00:00:28.570> seven<00:00:28.720> states<00:00:29.200> and<00:00:29.590> quite<00:00:29.770> simply 00:00:30.440 --> 00:00:30.450 align:start position:0% Table seven states and quite simply 00:00:30.450 --> 00:00:32.790 align:start position:0% Table seven states and quite simply asking<00:00:31.450> about<00:00:31.630> a<00:00:31.840> plan<00:00:32.140> or<00:00:32.349> customized 00:00:32.790 --> 00:00:32.800 align:start position:0% asking about a plan or customized 00:00:32.800 --> 00:00:35.640 align:start position:0% asking about a plan or customized prospect<00:00:33.340> we<00:00:33.520> have<00:00:33.670> a<00:00:33.820> mistake<00:00:34.180> might<00:00:34.500> come<00:00:35.500> to 00:00:35.640 --> 00:00:35.650 align:start position:0% prospect we have a mistake might come to 00:00:35.650 --> 00:00:39.930 align:start position:0% prospect we have a mistake might come to us<00:00:36.070> after<00:00:36.250> that<00:00:36.520> and<00:00:36.940> so<00:00:37.600> we<00:00:37.720> are<00:00:38.580> jumping<00:00:39.580> in 00:00:39.930 --> 00:00:39.940 align:start position:0% us after that and so we are jumping in 00:00:39.940 --> 00:00:47.689 align:start position:0% us after that and so we are jumping in at<00:00:40.180> least<00:00:40.540> try<00:00:40.780> to<00:00:40.840> stay<00:00:41.140> above<00:00:41.620> the 00:00:47.689 --> 00:00:47.699 align:start position:0% 00:00:47.699 --> 00:00:50.340 align:start position:0% consistency<00:00:48.699> where<00:00:48.970> our<00:00:49.090> expertise<00:00:49.690> come<00:00:49.870> in 00:00:50.340 --> 00:00:50.350 align:start position:0% consistency where our expertise come in 00:00:50.350 --> 00:00:54.490 align:start position:0% consistency where our expertise come in part<00:00:50.590> from<00:00:50.650> a<00:00:50.920> nowhere<00:00:51.220> and<00:00:51.940> unabated<00:00:52.570> work 00:00:54.490 --> 00:00:54.500 align:start position:0% part from a nowhere and unabated work 00:00:54.500 --> 00:00:58.180 align:start position:0% part from a nowhere and unabated work body<00:00:55.899> lower<00:00:56.899> focus<00:00:57.079> has<00:00:57.469> been<00:00:57.500> developer 00:00:58.180 --> 00:00:58.190 align:start position:0% body lower focus has been developer 00:00:58.190 --> 00:01:07.870 align:start position:0% body lower focus has been developer tools<00:00:58.430> to<00:00:58.760> have<00:00:59.170> original<00:01:01.449> diversity 00:01:07.870 --> 00:01:07.880 align:start position:0% 00:01:07.880 --> 00:01:11.249 align:start position:0% [Music] 00:01:11.249 --> 00:01:11.259 align:start position:0% 00:01:11.259 --> 00:01:16.840 align:start position:0% ministers<00:01:14.770> including<00:01:15.770> a<00:01:16.220> certain<00:01:16.549> spot 00:01:16.840 --> 00:01:16.850 align:start position:0% ministers including a certain spot 00:01:16.850 --> 00:01:19.450 align:start position:0% ministers including a certain spot context<00:01:17.330> certainly<00:01:17.659> an<00:01:18.110> explorer<00:01:18.530> and<00:01:19.009> the 00:01:19.450 --> 00:01:19.460 align:start position:0% context certainly an explorer and the 00:01:19.460 --> 00:01:21.510 align:start position:0% context certainly an explorer and the models<00:01:19.850> be<00:01:20.119> combined<00:01:20.450> into<00:01:20.690> a<00:01:20.840> single 00:01:21.510 --> 00:01:21.520 align:start position:0% models be combined into a single 00:01:21.520 --> 00:01:56.830 align:start position:0% models be combined into a single web-based<00:01:22.520> product 00:01:56.830 --> 00:01:56.840 align:start position:0% 00:01:56.840 --> 00:02:26.530 align:start position:0% we<00:02:08.780> love<00:02:10.579> this<00:02:11.579> project 00:02:26.530 --> 00:02:26.540 align:start position:0% 00:02:26.540 --> 00:02:31.950 align:start position:0% [Music] 00:02:31.950 --> 00:02:31.960 align:start position:0% 00:02:31.960 --> 00:02:47.809 align:start position:0% [Music] 00:02:47.809 --> 00:02:47.819 align:start position:0% 00:02:47.819 --> 00:03:05.620 align:start position:0% okay 00:03:05.620 --> 00:03:05.630 align:start position:0% 00:03:05.630 --> 00:03:19.910 align:start position:0% [Music] 00:03:19.910 --> 00:03:19.920 align:start position:0% 00:03:19.920 --> 00:03:23.039 align:start position:0% that<00:03:20.920> means<00:03:21.159> difficult<00:03:21.609> what<00:03:22.090> -<00:03:22.419> photoresist 00:03:23.039 --> 00:03:23.049 align:start position:0% that means difficult what - photoresist 00:03:23.049 --> 00:03:25.050 align:start position:0% that means difficult what - photoresist applications<00:03:23.680> we<00:03:23.980> come<00:03:24.220> on<00:03:24.370> enterprise<00:03:24.790> world 00:03:25.050 --> 00:03:25.060 align:start position:0% applications we come on enterprise world 00:03:25.060 --> 00:03:27.569 align:start position:0% applications we come on enterprise world you<00:03:25.299> know<00:03:25.480> that<00:03:25.720> DSL<00:03:26.139> has<00:03:26.349> always<00:03:26.560> been<00:03:26.889> one<00:03:27.549> of 00:03:27.569 --> 00:03:27.579 align:start position:0% you know that DSL has always been one of 00:03:27.579 --> 00:03:30.089 align:start position:0% you know that DSL has always been one of the<00:03:27.879> you<00:03:28.209> know<00:03:28.359> you<00:03:29.049> look<00:03:29.560> at<00:03:29.709> that<00:03:29.739> for 00:03:30.089 --> 00:03:30.099 align:start position:0% the you know you look at that for 00:03:30.099 --> 00:03:30.870 align:start position:0% the you know you look at that for maturity 00:03:30.870 --> 00:03:30.880 align:start position:0% maturity 00:03:30.880 --> 00:03:33.990 align:start position:0% maturity SPS<00:03:31.630> not<00:03:31.840> domain-specific<00:03:32.410> language<00:03:33.130> is<00:03:33.760> very 00:03:33.990 --> 00:03:34.000 align:start position:0% SPS not domain-specific language is very 00:03:34.000 --> 00:03:36.690 align:start position:0% SPS not domain-specific language is very important<00:03:34.540> for<00:03:35.530> for<00:03:36.160> real<00:03:36.370> word<00:03:36.580> and 00:03:36.690 --> 00:03:36.700 align:start position:0% important for for real word and 00:03:36.700 --> 00:03:39.300 align:start position:0% important for for real word and minimizing<00:03:37.510> states<00:03:37.810> and<00:03:38.320> today<00:03:38.800> in<00:03:38.950> salinity 00:03:39.300 --> 00:03:39.310 align:start position:0% minimizing states and today in salinity 00:03:39.310 --> 00:03:41.250 align:start position:0% minimizing states and today in salinity is<00:03:39.640> very<00:03:39.910> generic<00:03:40.120> everything<00:03:40.870> has<00:03:41.020> to<00:03:41.140> be 00:03:41.250 --> 00:03:41.260 align:start position:0% is very generic everything has to be 00:03:41.260 --> 00:03:42.840 align:start position:0% is very generic everything has to be brewing<00:03:41.470> companies<00:03:41.860> so<00:03:42.070> there's<00:03:42.310> no<00:03:42.520> specific 00:03:42.840 --> 00:03:42.850 align:start position:0% brewing companies so there's no specific 00:03:42.850 --> 00:03:45.720 align:start position:0% brewing companies so there's no specific optimization<00:03:43.660> solutions<00:03:44.200> and<00:03:44.470> the<00:03:45.280> second<00:03:45.640> is 00:03:45.720 --> 00:03:45.730 align:start position:0% optimization solutions and the second is 00:03:45.730 --> 00:03:48.870 align:start position:0% optimization solutions and the second is the<00:03:46.300> design<00:03:46.660> of<00:03:46.690> solidity<00:03:47.320> and<00:03:47.440> other<00:03:47.880> vendors 00:03:48.870 --> 00:03:48.880 align:start position:0% the design of solidity and other vendors 00:03:48.880 --> 00:03:53.670 align:start position:0% the design of solidity and other vendors they<00:03:49.150> must<00:03:49.480> assess<00:03:50.380> SS<00:03:50.800> and<00:03:50.980> SS<00:03:51.540> so<00:03:52.560> you<00:03:53.560> know 00:03:53.670 --> 00:03:53.680 align:start position:0% they must assess SS and SS so you know 00:03:53.680 --> 00:03:55.490 align:start position:0% they must assess SS and SS so you know gas<00:03:53.890> ourselves<00:03:54.490> why<00:03:54.700> so<00:03:55.030> difficult 00:03:55.490 --> 00:03:55.500 align:start position:0% gas ourselves why so difficult 00:03:55.500 --> 00:03:58.530 align:start position:0% gas ourselves why so difficult discrimination<00:03:56.500> of<00:03:56.560> scenario<00:03:56.950> why<00:03:57.760> is<00:03:57.820> it<00:03:58.030> no 00:03:58.530 --> 00:03:58.540 align:start position:0% discrimination of scenario why is it no 00:03:58.540 --> 00:04:01.320 align:start position:0% discrimination of scenario why is it no random<00:03:58.870> number<00:03:59.140> is<00:03:59.260> why<00:04:00.250> is<00:04:00.670> that<00:04:00.700> no<00:04:01.060> checks 00:04:01.320 --> 00:04:01.330 align:start position:0% random number is why is that no checks 00:04:01.330 --> 00:04:05.670 align:start position:0% random number is why is that no checks on<00:04:01.480> supporting<00:04:01.870> today<00:04:02.290> it's<00:04:02.890> because<00:04:04.680> the 00:04:05.670 --> 00:04:05.680 align:start position:0% on supporting today it's because the 00:04:05.680 --> 00:04:08.100 align:start position:0% on supporting today it's because the cylindrical<00:04:06.310> has<00:04:06.730> to<00:04:06.940> be<00:04:07.060> able<00:04:07.120> to<00:04:07.270> criticize 00:04:08.100 --> 00:04:08.110 align:start position:0% cylindrical has to be able to criticize 00:04:08.110 --> 00:04:10.290 align:start position:0% cylindrical has to be able to criticize actions<00:04:08.590> on<00:04:08.740> the<00:04:08.830> project<00:04:09.280> if<00:04:09.850> any<00:04:10.030> of<00:04:10.150> those 00:04:10.290 --> 00:04:10.300 align:start position:0% actions on the project if any of those 00:04:10.300 --> 00:04:13.560 align:start position:0% actions on the project if any of those cause<00:04:10.690> in<00:04:10.870> their<00:04:11.080> place<00:04:11.920> under<00:04:12.570> deterministic 00:04:13.560 --> 00:04:13.570 align:start position:0% cause in their place under deterministic 00:04:13.570 --> 00:04:21.630 align:start position:0% cause in their place under deterministic behavior<00:04:13.750> or<00:04:14.970> gas<00:04:15.970> fire<00:04:20.130> you<00:04:21.130> do<00:04:21.280> need<00:04:21.459> those 00:04:21.630 --> 00:04:21.640 align:start position:0% behavior or gas fire you do need those 00:04:21.640 --> 00:04:24.150 align:start position:0% behavior or gas fire you do need those features<00:04:22.060> Tammy<00:04:22.930> put<00:04:23.410> those<00:04:23.500> features<00:04:23.890> in 00:04:24.150 --> 00:04:24.160 align:start position:0% features Tammy put those features in 00:04:24.160 --> 00:04:26.400 align:start position:0% features Tammy put those features in view<00:04:24.370> functions<00:04:24.940> of<00:04:25.090> European<00:04:25.570> countries<00:04:25.780> and 00:04:26.400 --> 00:04:26.410 align:start position:0% view functions of European countries and 00:04:26.410 --> 00:04:31.830 align:start position:0% view functions of European countries and and<00:04:28.980> so<00:04:29.980> that's<00:04:30.160> a<00:04:30.340> great<00:04:30.460> out<00:04:30.940> there<00:04:31.240> most<00:04:31.630> of 00:04:31.830 --> 00:04:31.840 align:start position:0% and so that's a great out there most of 00:04:31.840 --> 00:04:36.120 align:start position:0% and so that's a great out there most of the<00:04:33.000> vendors<00:04:34.000> today<00:04:34.510> so<00:04:35.020> that's<00:04:35.170> where<00:04:35.470> you 00:04:36.120 --> 00:04:36.130 align:start position:0% the vendors today so that's where you 00:04:36.130 --> 00:04:39.120 align:start position:0% the vendors today so that's where you know<00:04:36.930> we<00:04:37.930> both<00:04:38.080> have<00:04:38.290> already<00:04:38.620> no<00:04:38.740> reason<00:04:39.040> to 00:04:39.120 --> 00:04:39.130 align:start position:0% know we both have already no reason to 00:04:39.130 --> 00:04:42.300 align:start position:0% know we both have already no reason to be<00:04:39.250> able<00:04:39.370> to<00:04:39.490> try<00:04:40.030> to<00:04:40.090> create<00:04:40.390> various<00:04:41.310> vessels 00:04:42.300 --> 00:04:42.310 align:start position:0% be able to try to create various vessels 00:04:42.310 --> 00:04:44.460 align:start position:0% be able to try to create various vessels to<00:04:42.670> province<00:04:43.060> because<00:04:43.780> if<00:04:43.960> you<00:04:44.050> don't<00:04:44.230> have 00:04:44.460 --> 00:04:44.470 align:start position:0% to province because if you don't have 00:04:44.470 --> 00:04:50.410 align:start position:0% to province because if you don't have consensus 00:04:50.410 --> 00:04:50.420 align:start position:0% 00:04:50.420 --> 00:04:53.120 align:start position:0% cameras<00:04:51.420> or<00:04:51.540> any<00:04:51.690> conferences<00:04:52.200> that's<00:04:52.890> not 00:04:53.120 --> 00:04:53.130 align:start position:0% cameras or any conferences that's not 00:04:53.130 --> 00:05:11.930 align:start position:0% cameras or any conferences that's not something<00:04:54.080> we<00:04:55.080> say<00:05:06.140> okay<00:05:07.140> so<00:05:08.720> how<00:05:10.130> who<00:05:11.130> shared 00:05:11.930 --> 00:05:11.940 align:start position:0% something we say okay so how who shared 00:05:11.940 --> 00:05:17.090 align:start position:0% something we say okay so how who shared over<00:05:12.150> my<00:05:12.390> time<00:05:12.600> and<00:05:14.390> talk<00:05:15.390> about<00:05:15.890> how<00:05:16.890> do<00:05:16.950> we 00:05:17.090 --> 00:05:17.100 align:start position:0% over my time and talk about how do we 00:05:17.100 --> 00:05:19.370 align:start position:0% over my time and talk about how do we address<00:05:17.250> the<00:05:17.610> first<00:05:17.850> challenge<00:05:18.330> the<00:05:18.930> first<00:05:18.960> is 00:05:19.370 --> 00:05:19.380 align:start position:0% address the first challenge the first is 00:05:19.380 --> 00:05:21.860 align:start position:0% address the first challenge the first is solidity<00:05:20.370> is<00:05:20.490> Tory<00:05:20.940> complete<00:05:21.330> and<00:05:21.630> its 00:05:21.860 --> 00:05:21.870 align:start position:0% solidity is Tory complete and its 00:05:21.870 --> 00:05:22.520 align:start position:0% solidity is Tory complete and its general 00:05:22.520 --> 00:05:22.530 align:start position:0% general 00:05:22.530 --> 00:05:25.430 align:start position:0% general there's<00:05:22.740> no<00:05:22.980> domain<00:05:23.250> system<00:05:23.760> seniors<00:05:24.230> in<00:05:25.230> that 00:05:25.430 --> 00:05:25.440 align:start position:0% there's no domain system seniors in that 00:05:25.440 --> 00:05:43.640 align:start position:0% there's no domain system seniors in that language<00:05:25.620> oh<00:05:42.020> I'm<00:05:43.020> sorry 00:05:43.640 --> 00:05:43.650 align:start position:0% language oh I'm sorry 00:05:43.650 --> 00:05:48.709 align:start position:0% language oh I'm sorry Ezra<00:05:44.130> so<00:05:44.610> I<00:05:46.100> was<00:05:47.100> some<00:05:47.250> of<00:05:47.370> the 00:05:48.709 --> 00:05:48.719 align:start position:0% Ezra so I was some of the 00:05:48.719 --> 00:05:52.230 align:start position:0% Ezra so I was some of the go<00:05:49.719> ahead<00:05:50.439> so<00:05:50.860> first<00:05:51.400> of<00:05:51.550> all<00:05:51.639> why<00:05:51.819> do<00:05:51.879> we<00:05:52.120> need 00:05:52.230 --> 00:05:52.240 align:start position:0% go ahead so first of all why do we need 00:05:52.240 --> 00:05:55.050 align:start position:0% go ahead so first of all why do we need a<00:05:52.300> ruler<00:05:52.569> is<00:05:52.870> 111/2<00:05:53.770> I<00:05:53.860> ask<00:05:54.069> this<00:05:54.189> question 00:05:55.050 --> 00:05:55.060 align:start position:0% a ruler is 111/2 I ask this question 00:05:55.060 --> 00:05:57.209 align:start position:0% a ruler is 111/2 I ask this question nobody's<00:05:55.599> not<00:05:55.780> contracted<00:05:56.379> automated<00:05:56.889> stress 00:05:57.209 --> 00:05:57.219 align:start position:0% nobody's not contracted automated stress 00:05:57.219 --> 00:06:02.629 align:start position:0% nobody's not contracted automated stress on<00:05:57.580> a<00:05:57.699> triggered<00:05:58.090> by<00:05:58.330> end<00:05:59.020> results<00:05:59.590> in<00:05:59.789> their 00:06:02.629 --> 00:06:02.639 align:start position:0% on a triggered by end results in their 00:06:02.639 --> 00:06:07.439 align:start position:0% on a triggered by end results in their eyes<00:06:03.639> their<00:06:03.879> very<00:06:04.120> definition<00:06:06.360> it's<00:06:07.360> a 00:06:07.439 --> 00:06:07.449 align:start position:0% eyes their very definition it's a 00:06:07.449 --> 00:06:09.600 align:start position:0% eyes their very definition it's a perfect<00:06:07.749> match<00:06:07.960> you<00:06:08.289> know<00:06:08.349> my<00:06:08.710> disciples<00:06:09.370> must 00:06:09.600 --> 00:06:09.610 align:start position:0% perfect match you know my disciples must 00:06:09.610 --> 00:06:12.029 align:start position:0% perfect match you know my disciples must be<00:06:09.759> transparent<00:06:10.629> regions<00:06:11.080> and<00:06:11.349> the<00:06:11.529> musical 00:06:12.029 --> 00:06:12.039 align:start position:0% be transparent regions and the musical 00:06:12.039 --> 00:06:14.459 align:start position:0% be transparent regions and the musical blockchain<00:06:12.849> is<00:06:12.879> perfect<00:06:13.870> for<00:06:14.080> Pat<00:06:14.259> Wall 00:06:14.459 --> 00:06:14.469 align:start position:0% blockchain is perfect for Pat Wall 00:06:14.469 --> 00:06:17.719 align:start position:0% blockchain is perfect for Pat Wall Street<00:06:14.740> fescue<00:06:15.219> rules<00:06:15.520> today<00:06:16.270> and<00:06:16.719> rice<00:06:16.960> go 00:06:17.719 --> 00:06:17.729 align:start position:0% Street fescue rules today and rice go 00:06:17.729 --> 00:06:39.450 align:start position:0% Street fescue rules today and rice go sizes<00:06:35.340> and<00:06:36.340> rules<00:06:36.729> engine<00:06:36.939> is<00:06:38.400> essentially<00:06:39.400> a 00:06:39.450 --> 00:06:39.460 align:start position:0% sizes and rules engine is essentially a 00:06:39.460 --> 00:06:41.399 align:start position:0% sizes and rules engine is essentially a decision<00:06:39.819> trees<00:06:40.029> in<00:06:40.300> rules<00:06:40.629> will<00:06:40.779> be<00:06:40.960> living 00:06:41.399 --> 00:06:41.409 align:start position:0% decision trees in rules will be living 00:06:41.409 --> 00:06:48.390 align:start position:0% decision trees in rules will be living in<00:06:41.650> a<00:06:41.889> decision<00:06:42.400> tree<00:06:42.490> using<00:06:42.969> a<00:06:43.830> large<00:06:47.400> driver 00:06:48.390 --> 00:06:48.400 align:start position:0% in a decision tree using a large driver 00:06:48.400 --> 00:06:50.640 align:start position:0% in a decision tree using a large driver impacts<00:06:49.089> it<00:06:49.300> relates<00:06:49.629> financially<00:06:50.199> absolute 00:06:50.640 --> 00:06:50.650 align:start position:0% impacts it relates financially absolute 00:06:50.650 --> 00:06:52.230 align:start position:0% impacts it relates financially absolute increase<00:06:51.009> you<00:06:51.339> know<00:06:51.460> so<00:06:51.639> if<00:06:51.819> you<00:06:51.969> have 00:06:52.230 --> 00:06:52.240 align:start position:0% increase you know so if you have 00:06:52.240 --> 00:06:55.409 align:start position:0% increase you know so if you have multiple<00:06:53.139> interacting<00:06:53.800> rules<00:06:54.129> in<00:06:54.460> trees<00:06:54.789> that 00:06:55.409 --> 00:06:55.419 align:start position:0% multiple interacting rules in trees that 00:06:55.419 --> 00:07:27.470 align:start position:0% multiple interacting rules in trees that every<00:06:55.719> single<00:06:56.050> change<00:06:56.379> on<00:06:56.740> this<00:06:57.219> side 00:07:27.470 --> 00:07:27.480 align:start position:0% 00:07:27.480 --> 00:07:58.439 align:start position:0% [Music] 00:07:58.439 --> 00:07:58.449 align:start position:0% 00:07:58.449 --> 00:08:02.950 align:start position:0% how<00:07:59.449> we<00:07:59.509> do<00:08:00.020> our<00:08:00.380> ascension<00:08:00.830> into<00:08:01.280> the<00:08:01.699> side<00:08:02.599> 13 00:08:02.950 --> 00:08:02.960 align:start position:0% how we do our ascension into the side 13 00:08:02.960 --> 00:08:06.909 align:start position:0% how we do our ascension into the side 13 a<00:08:03.169> sake<00:08:04.060> as<00:08:05.060> we<00:08:05.240> know<00:08:05.419> if<00:08:05.630> we<00:08:05.840> want<00:08:06.169> to<00:08:06.349> add<00:08:06.620> a 00:08:06.909 --> 00:08:06.919 align:start position:0% a sake as we know if we want to add a 00:08:06.919 --> 00:08:12.370 align:start position:0% a sake as we know if we want to add a puppy<00:08:07.520> they<00:08:08.240> must<00:08:08.479> be<00:08:09.070> some<00:08:10.070> new<00:08:11.080> clothes<00:08:12.080> or 00:08:12.370 --> 00:08:12.380 align:start position:0% puppy they must be some new clothes or 00:08:12.380 --> 00:08:15.520 align:start position:0% puppy they must be some new clothes or some<00:08:13.130> new<00:08:13.370> instruction<00:08:14.030> but<00:08:14.330> you<00:08:15.020> know<00:08:15.139> whose 00:08:15.520 --> 00:08:15.530 align:start position:0% some new instruction but you know whose 00:08:15.530 --> 00:08:17.170 align:start position:0% some new instruction but you know whose engine<00:08:15.740> we<00:08:16.070> don't<00:08:16.280> do<00:08:16.460> that<00:08:16.610> because<00:08:16.849> we<00:08:17.150> know 00:08:17.170 --> 00:08:17.180 align:start position:0% engine we don't do that because we know 00:08:17.180 --> 00:08:19.600 align:start position:0% engine we don't do that because we know a<00:08:17.510> half<00:08:17.990> of<00:08:18.229> half<00:08:18.470> of<00:08:18.500> Harvard<00:08:19.130> has<00:08:19.280> too<00:08:19.490> many 00:08:19.600 --> 00:08:19.610 align:start position:0% a half of half of Harvard has too many 00:08:19.610 --> 00:08:22.480 align:start position:0% a half of half of Harvard has too many Howard<00:08:20.060> we<00:08:20.180> don't<00:08:20.360> want<00:08:20.510> to<00:08:20.599> do<00:08:20.750> that<00:08:20.930> so<00:08:21.500> we 00:08:22.480 --> 00:08:22.490 align:start position:0% Howard we don't want to do that so we 00:08:22.490 --> 00:08:25.390 align:start position:0% Howard we don't want to do that so we just<00:08:22.639> separate<00:08:23.180> that<00:08:23.479> we<00:08:23.870> had<00:08:24.139> a<00:08:24.409> numerical 00:08:25.390 --> 00:08:25.400 align:start position:0% just separate that we had a numerical 00:08:25.400 --> 00:08:29.050 align:start position:0% just separate that we had a numerical rule<00:08:25.729> and<00:08:26.169> we<00:08:27.169> just<00:08:27.380> build<00:08:27.680> a<00:08:28.010> new<00:08:28.190> pasture<00:08:28.820> for 00:08:29.050 --> 00:08:29.060 align:start position:0% rule and we just build a new pasture for 00:08:29.060 --> 00:08:33.100 align:start position:0% rule and we just build a new pasture for years<00:08:29.300> and<00:08:29.539> neupogen<00:08:30.580> also<00:08:31.580> e<00:08:31.639> is<00:08:32.180> compatible 00:08:33.100 --> 00:08:33.110 align:start position:0% years and neupogen also e is compatible 00:08:33.110 --> 00:08:36.820 align:start position:0% years and neupogen also e is compatible with<00:08:33.169> the<00:08:34.099> original<00:08:34.310> if<00:08:34.909> you<00:08:35.060> want<00:08:35.270> so<00:08:35.830> you 00:08:36.820 --> 00:08:36.830 align:start position:0% with the original if you want so you 00:08:36.830 --> 00:08:38.920 align:start position:0% with the original if you want so you should<00:08:37.039> go<00:08:37.159> to<00:08:37.219> our<00:08:37.430> country<00:08:38.330> you<00:08:38.510> can<00:08:38.719> buy 00:08:38.920 --> 00:08:38.930 align:start position:0% should go to our country you can buy 00:08:38.930 --> 00:08:40.750 align:start position:0% should go to our country you can buy with<00:08:39.140> the<00:08:39.260> final<00:08:39.620> summer<00:08:39.830> clothes<00:08:40.430> and<00:08:40.640> she 00:08:40.750 --> 00:08:40.760 align:start position:0% with the final summer clothes and she 00:08:40.760 --> 00:08:44.440 align:start position:0% with the final summer clothes and she has<00:08:40.940> V<00:08:41.209> and<00:08:41.979> when<00:08:42.979> the<00:08:43.219> passer<00:08:43.459> going<00:08:44.089> inspired 00:08:44.440 --> 00:08:44.450 align:start position:0% has V and when the passer going inspired 00:08:44.450 --> 00:08:47.920 align:start position:0% has V and when the passer going inspired oh<00:08:45.080> that's<00:08:45.560> the<00:08:45.680> whole<00:08:45.890> walk<00:08:46.550> when<00:08:46.850> my<00:08:47.630> summer 00:08:47.920 --> 00:08:47.930 align:start position:0% oh that's the whole walk when my summer 00:08:47.930 --> 00:08:51.250 align:start position:0% oh that's the whole walk when my summer when<00:08:48.140> somebody<00:08:48.890> is<00:08:49.100> 12<00:08:49.490> and<00:08:49.940> a<00:08:50.209> naked<00:08:50.450> Testim 00:08:51.250 --> 00:08:51.260 align:start position:0% when somebody is 12 and a naked Testim 00:08:51.260 --> 00:09:00.480 align:start position:0% when somebody is 12 and a naked Testim case<00:08:52.220> a<00:08:52.339> mommy 00:09:00.480 --> 00:09:00.490 align:start position:0% 00:09:00.490 --> 00:09:46.929 align:start position:0% and<00:09:42.639> so<00:09:43.639> when<00:09:44.560> when<00:09:45.560> somebody<00:09:45.740> is<00:09:46.069> cute<00:09:46.459> the 00:09:46.929 --> 00:09:46.939 align:start position:0% and so when when somebody is cute the 00:09:46.939 --> 00:09:53.009 align:start position:0% and so when when somebody is cute the contrary<00:09:47.870> I<00:09:48.430> will<00:09:49.689> find<00:09:50.689> all<00:09:50.870> the<00:09:51.110> rules<00:09:51.980> and 00:09:53.009 --> 00:09:53.019 align:start position:0% contrary I will find all the rules and 00:09:53.019 --> 00:09:56.800 align:start position:0% contrary I will find all the rules and you<00:09:54.019> must<00:09:54.259> resist<00:09:54.649> something<00:09:55.610> our<00:09:55.970> company<00:09:56.779> I 00:09:56.800 --> 00:09:56.810 align:start position:0% you must resist something our company I 00:09:56.810 --> 00:10:00.280 align:start position:0% you must resist something our company I want<00:09:57.259> to<00:09:57.319> modify<00:09:58.509> because<00:09:59.509> there<00:09:59.750> are<00:09:59.899> lots<00:10:00.139> of 00:10:00.280 --> 00:10:00.290 align:start position:0% want to modify because there are lots of 00:10:00.290 --> 00:10:03.400 align:start position:0% want to modify because there are lots of horrible<00:10:00.790> not<00:10:01.790> everywhere<00:10:02.600> I<00:10:02.720> will<00:10:02.990> need<00:10:03.230> to 00:10:03.400 --> 00:10:03.410 align:start position:0% horrible not everywhere I will need to 00:10:03.410 --> 00:10:05.590 align:start position:0% horrible not everywhere I will need to be<00:10:03.620> modified<00:10:03.920> so<00:10:04.459> he<00:10:04.579> was<00:10:05.059> not<00:10:05.180> address<00:10:05.569> that 00:10:05.590 --> 00:10:05.600 align:start position:0% be modified so he was not address that 00:10:05.600 --> 00:10:10.210 align:start position:0% be modified so he was not address that and<00:10:06.519> or<00:10:07.519> handle<00:10:07.910> were<00:10:08.120> together<00:10:08.300> and<00:10:09.220> just 00:10:10.210 --> 00:10:10.220 align:start position:0% and or handle were together and just 00:10:10.220 --> 00:10:19.749 align:start position:0% and or handle were together and just feel<00:10:11.000> out<00:10:11.240> of<00:10:12.069> something<00:10:13.300> like<00:10:14.300> and<00:10:16.720> so<00:10:18.759> we 00:10:19.749 --> 00:10:19.759 align:start position:0% feel out of something like and so we 00:10:19.759 --> 00:10:23.049 align:start position:0% feel out of something like and so we just<00:10:19.939> go<00:10:20.209> to<00:10:20.990> our<00:10:21.019> demo<00:10:21.740> and<00:10:21.920> this<00:10:22.579> is<00:10:22.819> our 00:10:23.049 --> 00:10:23.059 align:start position:0% just go to our demo and this is our 00:10:23.059 --> 00:10:25.720 align:start position:0% just go to our demo and this is our website<00:10:23.870> you<00:10:24.290> can<00:10:24.470> go<00:10:24.620> there<00:10:24.829> and<00:10:24.860> get<00:10:25.370> more 00:10:25.720 --> 00:10:25.730 align:start position:0% website you can go there and get more 00:10:25.730 --> 00:10:26.590 align:start position:0% website you can go there and get more example 00:10:26.590 --> 00:10:26.600 align:start position:0% example 00:10:26.600 --> 00:10:29.620 align:start position:0% example yeah<00:10:26.959> oh<00:10:27.610> so 00:10:29.620 --> 00:10:29.630 align:start position:0% yeah oh so 00:10:29.630 --> 00:10:41.140 align:start position:0% yeah oh so our<00:10:30.010> looks 00:10:41.140 --> 00:10:41.150 align:start position:0% 00:10:41.150 --> 00:10:44.800 align:start position:0% they<00:10:41.690> were<00:10:41.810> resetting<00:10:42.290> it<00:10:42.610> and<00:10:43.610> our<00:10:44.360> first 00:10:44.800 --> 00:10:44.810 align:start position:0% they were resetting it and our first 00:10:44.810 --> 00:10:57.850 align:start position:0% they were resetting it and our first instant<00:10:54.310> okay<00:10:55.339> Alpha<00:10:55.850> Centauri<00:10:56.000> is<00:10:56.860> attention 00:10:57.850 --> 00:10:57.860 align:start position:0% instant okay Alpha Centauri is attention 00:10:57.860 --> 00:11:00.700 align:start position:0% instant okay Alpha Centauri is attention that's<00:10:58.339> we<00:10:58.610> define<00:10:59.060> a<00:10:59.330> person<00:10:59.779> who<00:11:00.020> has<00:11:00.260> a 00:11:00.700 --> 00:11:00.710 align:start position:0% that's we define a person who has a 00:11:00.710 --> 00:11:05.070 align:start position:0% that's we define a person who has a number<00:11:01.339> of<00:11:01.460> edge<00:11:01.670> and<00:11:02.230> locate<00:11:03.230> which<00:11:03.980> means<00:11:04.250> he 00:11:05.070 --> 00:11:05.080 align:start position:0% number of edge and locate which means he 00:11:05.080 --> 00:11:08.280 align:start position:0% number of edge and locate which means he attended<00:11:06.080> a<00:11:06.170> school<00:11:06.410> for<00:11:06.770> a<00:11:07.460> while<00:11:07.610> and 00:11:08.280 --> 00:11:08.290 align:start position:0% attended a school for a while and 00:11:08.290 --> 00:11:13.690 align:start position:0% attended a school for a while and packets<00:11:09.290> for<00:11:09.589> his<00:11:10.330> money<00:11:11.330> and<00:11:11.740> this<00:11:12.740> is<00:11:12.800> we 00:11:13.690 --> 00:11:13.700 align:start position:0% packets for his money and this is we 00:11:13.700 --> 00:11:19.090 align:start position:0% packets for his money and this is we define<00:11:14.000> a<00:11:14.170> structure<00:11:15.170> to<00:11:17.740> share<00:11:18.740> some<00:11:18.920> money 00:11:19.090 --> 00:11:19.100 align:start position:0% define a structure to share some money 00:11:19.100 --> 00:11:23.410 align:start position:0% define a structure to share some money to<00:11:19.370> those<00:11:19.940> person<00:11:20.390> and<00:11:21.020> we<00:11:21.320> have<00:11:21.500> to<00:11:22.390> we<00:11:23.390> have 00:11:23.410 --> 00:11:23.420 align:start position:0% to those person and we have to we have 00:11:23.420 --> 00:11:26.860 align:start position:0% to those person and we have to we have one<00:11:23.779> is<00:11:24.020> called<00:11:24.470> awesomest<00:11:25.460> which<00:11:25.970> will<00:11:26.240> store 00:11:26.860 --> 00:11:26.870 align:start position:0% one is called awesomest which will store 00:11:26.870 --> 00:11:29.740 align:start position:0% one is called awesomest which will store all<00:11:27.200> the<00:11:27.620> person<00:11:28.010> and<00:11:28.250> total<00:11:29.240> back<00:11:29.360> in<00:11:29.540> here 00:11:29.740 --> 00:11:29.750 align:start position:0% all the person and total back in here 00:11:29.750 --> 00:11:35.170 align:start position:0% all the person and total back in here and<00:11:31.270> we<00:11:32.270> add<00:11:32.450> a<00:11:32.480> new<00:11:33.020> numeric<00:11:33.589> encode<00:11:34.550> effect 00:11:35.170 --> 00:11:35.180 align:start position:0% and we add a new numeric encode effect 00:11:35.180 --> 00:11:37.890 align:start position:0% and we add a new numeric encode effect in<00:11:35.480> certain<00:11:35.960> Factory<00:11:36.260> in<00:11:36.350> series<00:11:36.830> just<00:11:37.220> like 00:11:37.890 --> 00:11:37.900 align:start position:0% in certain Factory in series just like 00:11:37.900 --> 00:11:41.500 align:start position:0% in certain Factory in series just like notify<00:11:38.900> our<00:11:39.310> pendulum<00:11:40.310> which<00:11:40.790> were<00:11:41.210> about 00:11:41.500 --> 00:11:41.510 align:start position:0% notify our pendulum which were about 00:11:41.510 --> 00:11:45.010 align:start position:0% notify our pendulum which were about shooting<00:11:42.080> money<00:11:42.520> in<00:11:43.520> this<00:11:43.910> example<00:11:44.300> dance<00:11:44.690> of 00:11:45.010 --> 00:11:45.020 align:start position:0% shooting money in this example dance of 00:11:45.020 --> 00:11:47.890 align:start position:0% shooting money in this example dance of the<00:11:45.320> package<00:11:45.830> will<00:11:46.160> be<00:11:46.190> alloyed<00:11:47.120> per<00:11:47.420> hour<00:11:47.600> and 00:11:47.890 --> 00:11:47.900 align:start position:0% the package will be alloyed per hour and 00:11:47.900 --> 00:11:55.480 align:start position:0% the package will be alloyed per hour and all<00:11:48.050> and<00:11:48.650> we<00:11:48.770> just<00:11:48.800> say<00:11:49.190> in<00:11:50.380> 2000<00:11:53.080> and<00:11:54.130> we<00:11:55.130> go 00:11:55.480 --> 00:11:55.490 align:start position:0% all and we just say in 2000 and we go 00:11:55.490 --> 00:11:57.160 align:start position:0% all and we just say in 2000 and we go through<00:11:55.820> a<00:11:55.880> little<00:11:56.450> car<00:11:56.660> first 00:11:57.160 --> 00:11:57.170 align:start position:0% through a little car first 00:11:57.170 --> 00:12:04.150 align:start position:0% through a little car first II<00:11:57.350> just<00:11:58.839> you<00:11:59.839> just<00:12:00.020> write<00:12:00.770> a<00:12:00.800> rule<00:12:02.050> like<00:12:03.160> a 00:12:04.150 --> 00:12:04.160 align:start position:0% II just you just write a rule like a 00:12:04.160 --> 00:12:09.670 align:start position:0% II just you just write a rule like a world<00:12:04.670> woman<00:12:05.570> he<00:12:06.080> can<00:12:06.320> be<00:12:06.529> a<00:12:07.330> stream<00:12:08.330> more<00:12:09.290> each 00:12:09.670 --> 00:12:09.680 align:start position:0% world woman he can be a stream more each 00:12:09.680 --> 00:12:12.970 align:start position:0% world woman he can be a stream more each of<00:12:09.890> the<00:12:10.040> men<00:12:10.250> and<00:12:10.670> the<00:12:11.209> window<00:12:11.810> will<00:12:12.200> will 00:12:12.970 --> 00:12:12.980 align:start position:0% of the men and the window will will 00:12:12.980 --> 00:12:15.640 align:start position:0% of the men and the window will will contain<00:12:13.790> several<00:12:14.060> conditions<00:12:14.480> as<00:12:15.020> you<00:12:15.470> can 00:12:15.640 --> 00:12:15.650 align:start position:0% contain several conditions as you can 00:12:15.650 --> 00:12:19.180 align:start position:0% contain several conditions as you can see<00:12:15.830> you<00:12:16.160> can<00:12:16.339> say<00:12:16.790> oh<00:12:17.000> I<00:12:17.300> want<00:12:17.540> to<00:12:17.980> feel<00:12:18.980> to 00:12:19.180 --> 00:12:19.190 align:start position:0% see you can say oh I want to feel to 00:12:19.190 --> 00:12:25.300 align:start position:0% see you can say oh I want to feel to that<00:12:20.920> last<00:12:21.920> person<00:12:22.480> who's<00:12:23.480> and<00:12:23.810> is<00:12:24.200> greater<00:12:24.950> or 00:12:25.300 --> 00:12:25.310 align:start position:0% that last person who's and is greater or 00:12:25.310 --> 00:12:29.019 align:start position:0% that last person who's and is greater or equal<00:12:25.550> than<00:12:25.990> 65<00:12:26.990> and<00:12:27.260> water<00:12:27.890> is<00:12:28.279> fertile<00:12:28.730> and 00:12:29.019 --> 00:12:29.029 align:start position:0% equal than 65 and water is fertile and 00:12:29.029 --> 00:12:34.449 align:start position:0% equal than 65 and water is fertile and equal<00:12:30.339> 5<00:12:31.339> and<00:12:31.839> also<00:12:32.839> our<00:12:33.080> package<00:12:33.500> must<00:12:33.709> must 00:12:34.449 --> 00:12:34.459 align:start position:0% equal 5 and also our package must must 00:12:34.459 --> 00:12:38.470 align:start position:0% equal 5 and also our package must must have<00:12:34.870> come<00:12:35.870> greater<00:12:36.290> than<00:12:36.500> 10<00:12:36.770> yeah<00:12:37.279> and<00:12:37.790> if 00:12:38.470 --> 00:12:38.480 align:start position:0% have come greater than 10 yeah and if 00:12:38.480 --> 00:12:42.269 align:start position:0% have come greater than 10 yeah and if you<00:12:38.720> find<00:12:39.080> if<00:12:39.620> our<00:12:39.980> intro<00:12:40.370> final<00:12:40.820> edge<00:12:40.940> and<00:12:41.300> me 00:12:42.269 --> 00:12:42.279 align:start position:0% you find if our intro final edge and me 00:12:42.279 --> 00:12:46.090 align:start position:0% you find if our intro final edge and me any<00:12:43.279> modifier<00:12:43.730> objects<00:12:44.510> is 00:12:46.090 --> 00:12:46.100 align:start position:0% any modifier objects is 00:12:46.100 --> 00:12:51.940 align:start position:0% any modifier objects is is<00:12:46.540> in<00:12:48.910> these<00:12:49.910> conditions<00:12:50.270> then<00:12:51.200> he<00:12:51.770> will 00:12:51.940 --> 00:12:51.950 align:start position:0% is in these conditions then he will 00:12:51.950 --> 00:12:55.150 align:start position:0% is in these conditions then he will check<00:12:52.190> out<00:12:52.370> this<00:12:53.120> inspections<00:12:54.110> like<00:12:54.380> we<00:12:54.980> will 00:12:55.150 --> 00:12:55.160 align:start position:0% check out this inspections like we will 00:12:55.160 --> 00:12:59.020 align:start position:0% check out this inspections like we will add<00:12:55.430> the<00:12:56.150> person<00:12:56.690> and<00:12:56.990> depend<00:12:57.830> on<00:12:57.980> us<00:12:58.130> and<00:12:58.340> just 00:12:59.020 --> 00:12:59.030 align:start position:0% add the person and depend on us and just 00:12:59.030 --> 00:13:00.850 align:start position:0% add the person and depend on us and just -<00:12:59.390> our<00:12:59.570> photo<00:12:59.840> packets<00:13:00.230> in<00:13:00.440> darkness 00:13:00.850 --> 00:13:00.860 align:start position:0% - our photo packets in darkness 00:13:00.860 --> 00:13:05.260 align:start position:0% - our photo packets in darkness yeah<00:13:01.430> and<00:13:02.170> another<00:13:03.170> one<00:13:03.380> is<00:13:03.500> how<00:13:04.490> can<00:13:04.670> we<00:13:04.700> add<00:13:04.940> a 00:13:05.260 --> 00:13:05.270 align:start position:0% yeah and another one is how can we add a 00:13:05.270 --> 00:13:08.680 align:start position:0% yeah and another one is how can we add a new<00:13:05.510> person<00:13:05.750> -<00:13:06.020> here<00:13:06.260> we<00:13:07.070> can<00:13:07.220> see<00:13:07.430> we<00:13:08.210> have<00:13:08.450> a 00:13:08.680 --> 00:13:08.690 align:start position:0% new person - here we can see we have a 00:13:08.690 --> 00:13:12.010 align:start position:0% new person - here we can see we have a list<00:13:08.960> here<00:13:09.320> and<00:13:09.910> we<00:13:10.910> create<00:13:11.180> lots<00:13:11.450> of<00:13:11.630> person 00:13:12.010 --> 00:13:12.020 align:start position:0% list here and we create lots of person 00:13:12.020 --> 00:13:14.740 align:start position:0% list here and we create lots of person of<00:13:12.200> judgment<00:13:12.710> and<00:13:12.860> then<00:13:13.430> that's<00:13:13.910> insert<00:13:14.390> to 00:13:14.740 --> 00:13:14.750 align:start position:0% of judgment and then that's insert to 00:13:14.750 --> 00:13:18.340 align:start position:0% of judgment and then that's insert to tell<00:13:15.080> our<00:13:15.230> Endora<00:13:15.740> to<00:13:16.340> modify<00:13:16.850> a<00:13:17.120> piece<00:13:17.810> this 00:13:18.340 --> 00:13:18.350 align:start position:0% tell our Endora to modify a piece this 00:13:18.350 --> 00:13:23.500 align:start position:0% tell our Endora to modify a piece this object<00:13:18.590> and<00:13:20.350> the<00:13:21.350> last<00:13:21.770> action<00:13:22.670> is<00:13:22.940> we<00:13:23.300> well 00:13:23.500 --> 00:13:23.510 align:start position:0% object and the last action is we well 00:13:23.510 --> 00:13:27.220 align:start position:0% object and the last action is we well called<00:13:24.730> punching<00:13:25.730> or<00:13:25.940> the<00:13:26.090> final<00:13:26.510> rules<00:13:26.780> it 00:13:27.220 --> 00:13:27.230 align:start position:0% called punching or the final rules it 00:13:27.230 --> 00:13:30.220 align:start position:0% called punching or the final rules it will<00:13:27.410> just<00:13:27.770> delete<00:13:28.700> all<00:13:29.090> of<00:13:29.120> the<00:13:29.540> rules<00:13:29.840> and 00:13:30.220 --> 00:13:30.230 align:start position:0% will just delete all of the rules and 00:13:30.230 --> 00:13:35.050 align:start position:0% will just delete all of the rules and and<00:13:31.240> just<00:13:32.240> just<00:13:32.390> do<00:13:33.200> these<00:13:33.470> actions<00:13:33.800> so<00:13:34.610> let<00:13:34.940> me 00:13:35.050 --> 00:13:35.060 align:start position:0% and just just do these actions so let me 00:13:35.060 --> 00:13:43.760 align:start position:0% and just just do these actions so let me compare<00:13:35.420> yet 00:13:43.760 --> 00:13:43.770 align:start position:0% 00:13:43.770 --> 00:13:51.090 align:start position:0% first<00:13:44.770> of<00:13:44.890> all<00:13:45.010> we<00:13:45.490> had<00:13:45.640> a<00:13:45.910> person<00:13:46.450> like<00:13:50.100> the 00:13:51.090 --> 00:13:51.100 align:start position:0% first of all we had a person like the 00:13:51.100 --> 00:13:57.090 align:start position:0% first of all we had a person like the first<00:13:51.340> one<00:13:53.700> okay<00:13:54.700> we<00:13:55.420> can<00:13:55.600> just<00:13:56.170> check<00:13:56.380> was 00:13:57.090 --> 00:13:57.100 align:start position:0% first one okay we can just check was 00:13:57.100 --> 00:14:01.950 align:start position:0% first one okay we can just check was once<00:13:57.310> they<00:13:57.490> happen<00:13:59.310> and<00:14:00.310> we<00:14:00.610> at<00:14:00.760> the<00:14:00.930> spawn<00:14:01.930> is 00:14:01.950 --> 00:14:01.960 align:start position:0% once they happen and we at the spawn is 00:14:01.960 --> 00:14:11.170 align:start position:0% once they happen and we at the spawn is this<00:14:02.530> is<00:14:03.280> five<00:14:03.550> and<00:14:03.790> twenty<00:14:04.600> and<00:14:04.870> to 00:14:11.170 --> 00:14:11.180 align:start position:0% 00:14:11.180 --> 00:14:17.060 align:start position:0% Sara<00:14:12.180> because<00:14:12.779> these<00:14:13.170> villages<00:14:15.440> large<00:14:16.440> or<00:14:16.680> or 00:14:17.060 --> 00:14:17.070 align:start position:0% Sara because these villages large or or 00:14:17.070 --> 00:14:20.290 align:start position:0% Sara because these villages large or or equal<00:14:17.399> to<00:14:17.550> five<00:14:17.760> so<00:14:17.790> we<00:14:18.420> want<00:14:18.899> to<00:14:19.080> adhere<00:14:19.560> to 00:14:20.290 --> 00:14:20.300 align:start position:0% equal to five so we want to adhere to 00:14:20.300 --> 00:14:24.650 align:start position:0% equal to five so we want to adhere to just<00:14:21.300> be<00:14:21.480> wrong<00:14:21.720> okay<00:14:22.670> now<00:14:23.670> we<00:14:23.730> have<00:14:24.000> three 00:14:24.650 --> 00:14:24.660 align:start position:0% just be wrong okay now we have three 00:14:24.660 --> 00:14:27.670 align:start position:0% just be wrong okay now we have three person<00:14:25.050> and<00:14:25.290> certified<00:14:26.000> classes<00:14:27.029> now<00:14:27.390> we 00:14:27.670 --> 00:14:27.680 align:start position:0% person and certified classes now we 00:14:27.680 --> 00:14:34.400 align:start position:0% person and certified classes now we image<00:14:28.680> the<00:14:28.950> pay<00:14:29.160> machine<00:14:31.250> and<00:14:32.250> just<00:14:33.200> check<00:14:34.200> all 00:14:34.400 --> 00:14:34.410 align:start position:0% image the pay machine and just check all 00:14:34.410 --> 00:14:38.480 align:start position:0% image the pay machine and just check all of<00:14:34.470> the<00:14:34.920> person<00:14:35.310> liked<00:14:35.580> on<00:14:35.940> the<00:14:36.630> Negro<00:14:37.370> but<00:14:38.370> he 00:14:38.480 --> 00:14:38.490 align:start position:0% of the person liked on the Negro but he 00:14:38.490 --> 00:14:40.639 align:start position:0% of the person liked on the Negro but he didn't<00:14:38.760> get<00:14:38.880> any<00:14:39.029> money<00:14:39.180> because<00:14:39.420> this<00:14:40.170> is 00:14:40.639 --> 00:14:40.649 align:start position:0% didn't get any money because this is 00:14:40.649 --> 00:14:45.260 align:start position:0% didn't get any money because this is only<00:14:40.830> system<00:14:41.399> for<00:14:41.610> years<00:14:43.430> second<00:14:44.430> one<00:14:44.610> jacket 00:14:45.260 --> 00:14:45.270 align:start position:0% only system for years second one jacket 00:14:45.270 --> 00:14:51.050 align:start position:0% only system for years second one jacket $10<00:14:45.870> and<00:14:46.850> sir<00:14:47.850> one<00:14:48.709> known<00:14:49.709> angle<00:14:50.190> and<00:14:50.700> dollars 00:14:51.050 --> 00:14:51.060 align:start position:0% $10 and sir one known angle and dollars 00:14:51.060 --> 00:14:53.870 align:start position:0% $10 and sir one known angle and dollars yeah<00:14:51.330> and<00:14:51.750> as<00:14:52.380> though<00:14:52.560> we<00:14:52.890> can<00:14:52.920> just<00:14:53.459> check<00:14:53.640> the 00:14:53.870 --> 00:14:53.880 align:start position:0% yeah and as though we can just check the 00:14:53.880 --> 00:14:57.760 align:start position:0% yeah and as though we can just check the baggage<00:14:54.839> if<00:14:55.140> he<00:14:55.470> just<00:14:55.680> he<00:14:56.010> just<00:14:56.040> spend<00:14:56.880> $10 00:14:57.760 --> 00:14:57.770 align:start position:0% baggage if he just he just spend $10 00:14:57.770 --> 00:14:58.970 align:start position:0% baggage if he just he just spend $10 okay 00:14:58.970 --> 00:14:58.980 align:start position:0% okay 00:14:58.980 --> 00:15:02.690 align:start position:0% okay that's<00:14:59.370> our<00:14:59.670> our<00:15:00.390> table<00:15:00.990> full<00:15:01.320> of<00:15:01.350> loss<00:15:02.250> engine 00:15:02.690 --> 00:15:02.700 align:start position:0% that's our our table full of loss engine 00:15:02.700 --> 00:15:04.490 align:start position:0% that's our our table full of loss engine if<00:15:03.029> we<00:15:03.209> right<00:15:03.390> scan<00:15:03.750> you<00:15:03.899> can<00:15:04.080> find<00:15:04.350> more 00:15:04.490 --> 00:15:04.500 align:start position:0% if we right scan you can find more 00:15:04.500 --> 00:15:27.590 align:start position:0% if we right scan you can find more examples<00:15:05.130> on<00:15:05.370> our<00:15:05.610> website 00:15:27.590 --> 00:15:27.600 align:start position:0% 00:15:27.600 --> 00:15:30.509 align:start position:0% research<00:15:28.600> coming<00:15:29.019> off<00:15:29.139> to<00:15:29.319> say<00:15:29.500> that's<00:15:30.250> the 00:15:30.509 --> 00:15:30.519 align:start position:0% research coming off to say that's the 00:15:30.519 --> 00:15:32.689 align:start position:0% research coming off to say that's the verdict<00:15:30.819> you<00:15:30.850> retired<00:15:31.329> the<00:15:31.509> laundry<00:15:31.810> to<00:15:31.899> them 00:15:32.689 --> 00:15:32.699 align:start position:0% verdict you retired the laundry to them 00:15:32.699 --> 00:15:35.850 align:start position:0% verdict you retired the laundry to them retire<00:15:33.699> like<00:15:33.850> 15<00:15:34.540> leading<00:15:34.779> to<00:15:35.019> the<00:15:35.110> minutes<00:15:35.410> if 00:15:35.850 --> 00:15:35.860 align:start position:0% retire like 15 leading to the minutes if 00:15:35.860 --> 00:15:44.370 align:start position:0% retire like 15 leading to the minutes if you<00:15:36.009> retire<00:15:36.370> at<00:15:36.550> 65<00:15:38.339> 67<00:15:42.779> so<00:15:43.779> it's<00:15:44.170> really 00:15:44.370 --> 00:15:44.380 align:start position:0% you retire at 65 67 so it's really 00:15:44.380 --> 00:15:45.870 align:start position:0% you retire at 65 67 so it's really important<00:15:44.829> that's<00:15:45.040> the<00:15:45.220> top<00:15:45.399> and<00:15:45.579> have<00:15:45.670> all 00:15:45.870 --> 00:15:45.880 align:start position:0% important that's the top and have all 00:15:45.880 --> 00:15:48.660 align:start position:0% important that's the top and have all this<00:15:46.000> cool<00:15:46.800> you<00:15:47.800> know<00:15:47.889> who<00:15:48.009> gets<00:15:48.190> love<00:15:48.399> to 00:15:48.660 --> 00:15:48.670 align:start position:0% this cool you know who gets love to 00:15:48.670 --> 00:16:08.630 align:start position:0% this cool you know who gets love to retirement<00:15:49.120> age<00:15:49.209> so<00:15:49.540> I'd<00:15:49.899> actually<00:15:50.170> show<00:15:50.230> up 00:16:08.630 --> 00:16:08.640 align:start position:0% 00:16:08.640 --> 00:17:10.760 align:start position:0% [Music] 00:17:10.760 --> 00:17:10.770 align:start position:0% 00:17:10.770 --> 00:17:17.460 align:start position:0% [Music] 00:17:17.460 --> 00:17:17.470 align:start position:0% 00:17:17.470 --> 00:17:23.590 align:start position:0% so<00:17:18.470> the<00:17:18.589> next<00:17:18.740> one<00:17:18.980> I<00:17:19.160> want<00:17:19.189> to<00:17:21.280> talk<00:17:22.280> about<00:17:22.600> how 00:17:23.590 --> 00:17:23.600 align:start position:0% so the next one I want to talk about how 00:17:23.600 --> 00:17:25.600 align:start position:0% so the next one I want to talk about how we<00:17:23.660> saw<00:17:23.990> the<00:17:24.500> second<00:17:24.770> review<00:17:25.010> before<00:17:25.459> the 00:17:25.600 --> 00:17:25.610 align:start position:0% we saw the second review before the 00:17:25.610 --> 00:17:28.000 align:start position:0% we saw the second review before the first<00:17:25.790> Apollo<00:17:26.120> is<00:17:26.480> noting<00:17:27.110> specific<00:17:27.290> stages 00:17:28.000 --> 00:17:28.010 align:start position:0% first Apollo is noting specific stages 00:17:28.010 --> 00:17:30.130 align:start position:0% first Apollo is noting specific stages for<00:17:28.370> the<00:17:28.640> language<00:17:29.000> the<00:17:29.210> second<00:17:29.480> problem<00:17:29.690> is 00:17:30.130 --> 00:17:30.140 align:start position:0% for the language the second problem is 00:17:30.140 --> 00:17:33.560 align:start position:0% for the language the second problem is no<00:17:30.890> separation<00:17:31.340> between<00:17:31.490> suspect 00:17:33.560 --> 00:17:33.570 align:start position:0% no separation between suspect 00:17:33.570 --> 00:17:40.489 align:start position:0% no separation between suspect any<00:17:35.179> final<00:17:36.179> winners<00:17:37.789> we<00:17:38.789> see<00:17:39.359> you<00:17:39.570> be<00:17:39.720> my<00:17:39.809> kids 00:17:40.489 --> 00:17:40.499 align:start position:0% any final winners we see you be my kids 00:17:40.499 --> 00:17:54.320 align:start position:0% any final winners we see you be my kids 1.1<00:17:41.190> X<00:17:51.169> separated<00:17:52.220> so<00:17:53.220> basically<00:17:53.999> we<00:17:54.179> could 00:17:54.320 --> 00:17:54.330 align:start position:0% 1.1 X separated so basically we could 00:17:54.330 --> 00:17:56.659 align:start position:0% 1.1 X separated so basically we could call<00:17:54.479> this<00:17:54.600> an<00:17:54.840> auxilary<00:17:55.200> application<00:17:56.100> and 00:17:56.659 --> 00:17:56.669 align:start position:0% call this an auxilary application and 00:17:56.669 --> 00:17:57.499 align:start position:0% call this an auxilary application and what<00:17:56.999> we<00:17:57.090> mean<00:17:57.239> by 00:17:57.499 --> 00:17:57.509 align:start position:0% what we mean by 00:17:57.509 --> 00:18:00.139 align:start position:0% what we mean by auxilary<00:17:58.109> application<00:17:59.070> is<00:17:59.220> an<00:17:59.729> application 00:18:00.139 --> 00:18:00.149 align:start position:0% auxilary application is an application 00:18:00.149 --> 00:18:03.019 align:start position:0% auxilary application is an application that<00:18:00.539> is<00:18:00.809> really<00:18:01.289> assisting<00:18:01.830> the<00:18:02.009> end-user<00:18:02.580> of 00:18:03.019 --> 00:18:03.029 align:start position:0% that is really assisting the end-user of 00:18:03.029 --> 00:18:03.590 align:start position:0% that is really assisting the end-user of a<00:18:03.090> blockchain 00:18:03.590 --> 00:18:03.600 align:start position:0% a blockchain 00:18:03.600 --> 00:18:06.999 align:start position:0% a blockchain application<00:18:04.259> and<00:18:05.100> essentially<00:18:05.869> transforming 00:18:06.999 --> 00:18:07.009 align:start position:0% application and essentially transforming 00:18:07.009 --> 00:18:10.519 align:start position:0% application and essentially transforming full<00:18:08.009> node<00:18:08.309> data<00:18:08.779> to<00:18:09.779> make<00:18:09.929> it<00:18:10.080> available<00:18:10.259> to 00:18:10.519 --> 00:18:10.529 align:start position:0% full node data to make it available to 00:18:10.529 --> 00:18:12.259 align:start position:0% full node data to make it available to the<00:18:10.649> end<00:18:10.739> user<00:18:10.919> in<00:18:11.460> a<00:18:11.489> useful<00:18:11.669> way 00:18:12.259 --> 00:18:12.269 align:start position:0% the end user in a useful way 00:18:12.269 --> 00:18:13.969 align:start position:0% the end user in a useful way so<00:18:12.450> this<00:18:12.570> is<00:18:12.690> not<00:18:12.869> a<00:18:12.929> second<00:18:13.289> layer<00:18:13.440> solution 00:18:13.969 --> 00:18:13.979 align:start position:0% so this is not a second layer solution 00:18:13.979 --> 00:18:16.339 align:start position:0% so this is not a second layer solution and<00:18:14.309> does<00:18:14.489> not<00:18:14.669> play<00:18:14.940> a<00:18:14.970> role<00:18:15.359> in<00:18:15.749> and<00:18:16.019> network 00:18:16.339 --> 00:18:16.349 align:start position:0% and does not play a role in and network 00:18:16.349 --> 00:18:18.830 align:start position:0% and does not play a role in and network consensus<00:18:16.889> at<00:18:17.099> all<00:18:17.220> and<00:18:17.460> it<00:18:18.239> doesn't<00:18:18.539> play<00:18:18.809> a 00:18:18.830 --> 00:18:18.840 align:start position:0% consensus at all and it doesn't play a 00:18:18.840 --> 00:18:21.919 align:start position:0% consensus at all and it doesn't play a role<00:18:18.929> in<00:18:19.379> updating<00:18:19.979> the<00:18:20.099> blockchain<00:18:20.340> state<00:18:21.059> c0 00:18:21.919 --> 00:18:21.929 align:start position:0% role in updating the blockchain state c0 00:18:21.929 --> 00:18:25.940 align:start position:0% role in updating the blockchain state c0 read<00:18:22.619> only<00:18:23.539> one<00:18:24.539> axillary<00:18:25.049> application 00:18:25.940 --> 00:18:25.950 align:start position:0% read only one axillary application 00:18:25.950 --> 00:18:27.919 align:start position:0% read only one axillary application example<00:18:26.429> would<00:18:26.580> be<00:18:26.759> like<00:18:27.149> a<00:18:27.179> Bitcoin<00:18:27.659> core 00:18:27.919 --> 00:18:27.929 align:start position:0% example would be like a Bitcoin core 00:18:27.929 --> 00:18:32.149 align:start position:0% example would be like a Bitcoin core wallet<00:18:28.320> so<00:18:28.950> as<00:18:29.489> we<00:18:29.669> know<00:18:29.700> we<00:18:30.479> have<00:18:31.159> episodes 00:18:32.149 --> 00:18:32.159 align:start position:0% wallet so as we know we have episodes 00:18:32.159 --> 00:18:34.279 align:start position:0% wallet so as we know we have episodes and<00:18:32.460> the<00:18:32.970> system<00:18:33.359> the<00:18:33.599> Bitcoin<00:18:33.929> states 00:18:34.279 --> 00:18:34.289 align:start position:0% and the system the Bitcoin states 00:18:34.289 --> 00:18:36.680 align:start position:0% and the system the Bitcoin states represented<00:18:35.039> by<00:18:35.190> its<00:18:35.249> global<00:18:35.519> collection<00:18:36.059> of 00:18:36.680 --> 00:18:36.690 align:start position:0% represented by its global collection of 00:18:36.690 --> 00:18:38.839 align:start position:0% represented by its global collection of unspent<00:18:37.109> transaction<00:18:37.649> out<00:18:37.739> please<00:18:38.039> but<00:18:38.759> the 00:18:38.839 --> 00:18:38.849 align:start position:0% unspent transaction out please but the 00:18:38.849 --> 00:18:41.359 align:start position:0% unspent transaction out please but the Bitcoin<00:18:39.269> blockchain<00:18:39.649> doesn't<00:18:40.649> actually<00:18:40.889> hold 00:18:41.359 --> 00:18:41.369 align:start position:0% Bitcoin blockchain doesn't actually hold 00:18:41.369 --> 00:18:44.389 align:start position:0% Bitcoin blockchain doesn't actually hold the<00:18:41.549> account<00:18:41.820> balances<00:18:42.330> so<00:18:43.200> it<00:18:43.739> uses<00:18:44.099> account 00:18:44.389 --> 00:18:44.399 align:start position:0% the account balances so it uses account 00:18:44.399 --> 00:18:48.499 align:start position:0% the account balances so it uses account balance<00:18:44.789> in<00:18:44.909> Bitcoin<00:18:46.970> axillary<00:18:47.970> application 00:18:48.499 --> 00:18:48.509 align:start position:0% balance in Bitcoin axillary application 00:18:48.509 --> 00:18:51.499 align:start position:0% balance in Bitcoin axillary application i.e<00:18:48.809> the<00:18:49.080> long<00:18:49.259> so<00:18:49.979> there's<00:18:50.580> a<00:18:50.700> purpose<00:18:51.299> for 00:18:51.499 --> 00:18:51.509 align:start position:0% i.e the long so there's a purpose for 00:18:51.509 --> 00:18:54.080 align:start position:0% i.e the long so there's a purpose for ancillary<00:18:51.779> applications<00:18:52.700> they<00:18:53.700> are<00:18:53.729> safe 00:18:54.080 --> 00:18:54.090 align:start position:0% ancillary applications they are safe 00:18:54.090 --> 00:18:56.299 align:start position:0% ancillary applications they are safe because<00:18:54.499> they're<00:18:55.499> really<00:18:55.619> just<00:18:55.830> a<00:18:55.979> helper 00:18:56.299 --> 00:18:56.309 align:start position:0% because they're really just a helper 00:18:56.309 --> 00:18:58.920 align:start position:0% because they're really just a helper right<00:18:56.460> so<00:18:56.940> it's<00:18:57.809> important 00:18:58.920 --> 00:18:58.930 align:start position:0% right so it's important 00:18:58.930 --> 00:19:01.060 align:start position:0% right so it's important application<00:18:59.930> can't<00:19:00.560> really<00:19:00.830> make<00:19:01.010> the 00:19:01.060 --> 00:19:01.070 align:start position:0% application can't really make the 00:19:01.070 --> 00:19:03.340 align:start position:0% application can't really make the blockchain<00:19:01.400> do<00:19:01.790> anything<00:19:02.150> in<00:19:02.270> college<00:19:02.480> so<00:19:02.870> in 00:19:03.340 --> 00:19:03.350 align:start position:0% blockchain do anything in college so in 00:19:03.350 --> 00:19:06.570 align:start position:0% blockchain do anything in college so in example<00:19:03.860> is<00:19:03.980> yeah<00:19:04.700> Alice<00:19:05.450> here<00:19:05.660> she's<00:19:06.080> got<00:19:06.260> to 00:19:06.570 --> 00:19:06.580 align:start position:0% example is yeah Alice here she's got to 00:19:06.580 --> 00:19:09.430 align:start position:0% example is yeah Alice here she's got to the<00:19:07.580> point<00:19:07.880> if<00:19:08.090> she<00:19:08.330> thinks<00:19:08.930> that<00:19:09.050> she's<00:19:09.260> got 00:19:09.430 --> 00:19:09.440 align:start position:0% the point if she thinks that she's got 00:19:09.440 --> 00:19:10.960 align:start position:0% the point if she thinks that she's got three<00:19:09.740> for<00:19:10.010> some<00:19:10.190> reason<00:19:10.490> that<00:19:10.550> she<00:19:10.730> tries<00:19:10.940> to 00:19:10.960 --> 00:19:10.970 align:start position:0% three for some reason that she tries to 00:19:10.970 --> 00:19:12.460 align:start position:0% three for some reason that she tries to execute<00:19:11.600> a<00:19:11.630> transaction<00:19:12.170> that<00:19:12.200> might 00:19:12.460 --> 00:19:12.470 align:start position:0% execute a transaction that might 00:19:12.470 --> 00:19:14.020 align:start position:0% execute a transaction that might actually<00:19:12.680> succeed<00:19:12.980> so<00:19:13.460> they<00:19:13.550> can't<00:19:13.820> make 00:19:14.020 --> 00:19:14.030 align:start position:0% actually succeed so they can't make 00:19:14.030 --> 00:19:18.430 align:start position:0% actually succeed so they can't make blockchain<00:19:14.900> do<00:19:15.050> anything<00:19:15.380> that<00:19:15.560> song<00:19:17.410> so<00:19:18.410> the 00:19:18.430 --> 00:19:18.440 align:start position:0% blockchain do anything that song so the 00:19:18.440 --> 00:19:20.500 align:start position:0% blockchain do anything that song so the smart<00:19:18.830> contract<00:19:19.010> search<00:19:19.490> engine<00:19:19.910> falls<00:19:20.240> into 00:19:20.500 --> 00:19:20.510 align:start position:0% smart contract search engine falls into 00:19:20.510 --> 00:19:22.570 align:start position:0% smart contract search engine falls into this<00:19:20.690> category<00:19:20.750> of<00:19:21.230> what<00:19:21.440> non-consensus<00:19:22.340> code 00:19:22.570 --> 00:19:22.580 align:start position:0% this category of what non-consensus code 00:19:22.580 --> 00:19:25.120 align:start position:0% this category of what non-consensus code and<00:19:22.970> the<00:19:23.600> search<00:19:23.810> engine<00:19:24.170> that<00:19:24.290> allows<00:19:24.380> pure 00:19:25.120 --> 00:19:25.130 align:start position:0% and the search engine that allows pure 00:19:25.130 --> 00:19:27.220 align:start position:0% and the search engine that allows pure view<00:19:25.550> infractions<00:19:26.210> to<00:19:26.330> be<00:19:26.540> executed<00:19:27.080> off 00:19:27.220 --> 00:19:27.230 align:start position:0% view infractions to be executed off 00:19:27.230 --> 00:19:29.530 align:start position:0% view infractions to be executed off chain<00:19:27.530> with<00:19:28.190> arbitrary<00:19:28.640> programming 00:19:29.530 --> 00:19:29.540 align:start position:0% chain with arbitrary programming 00:19:29.540 --> 00:19:31.990 align:start position:0% chain with arbitrary programming languages<00:19:29.930> and<00:19:30.140> rules<00:19:30.350> and<00:19:30.850> example<00:19:31.850> this 00:19:31.990 --> 00:19:32.000 align:start position:0% languages and rules and example this 00:19:32.000 --> 00:19:34.000 align:start position:0% languages and rules and example this will<00:19:32.180> show<00:19:32.360> you<00:19:32.420> minute<00:19:32.780> is<00:19:32.900> it's<00:19:33.080> reading<00:19:33.560> the 00:19:34.000 --> 00:19:34.010 align:start position:0% will show you minute is it's reading the 00:19:34.010 --> 00:19:36.760 align:start position:0% will show you minute is it's reading the public<00:19:34.550> data<00:19:35.270> that<00:19:35.660> exists<00:19:36.050> so<00:19:36.260> for<00:19:36.440> example 00:19:36.760 --> 00:19:36.770 align:start position:0% public data that exists so for example 00:19:36.770 --> 00:19:38.170 align:start position:0% public data that exists so for example if<00:19:36.860> there's<00:19:37.010> a<00:19:37.070> public<00:19:37.220> variable<00:19:37.550> the 00:19:38.170 --> 00:19:38.180 align:start position:0% if there's a public variable the 00:19:38.180 --> 00:19:39.940 align:start position:0% if there's a public variable the compiled<00:19:38.720> traffic<00:19:39.080> to<00:19:39.350> the<00:19:39.500> Guinness<00:19:39.770> and 00:19:39.940 --> 00:19:39.950 align:start position:0% compiled traffic to the Guinness and 00:19:39.950 --> 00:19:42.070 align:start position:0% compiled traffic to the Guinness and service<00:19:40.220> automatically<00:19:40.820> you<00:19:41.480> can<00:19:41.510> go<00:19:41.810> in<00:19:41.960> and 00:19:42.070 --> 00:19:42.080 align:start position:0% service automatically you can go in and 00:19:42.080 --> 00:19:44.890 align:start position:0% service automatically you can go in and grab<00:19:42.260> that<00:19:42.410> information<00:19:43.300> automatically<00:19:44.300> so 00:19:44.890 --> 00:19:44.900 align:start position:0% grab that information automatically so 00:19:44.900 --> 00:19:47.860 align:start position:0% grab that information automatically so it's<00:19:45.470> a<00:19:45.530> bit<00:19:45.650> of<00:19:45.740> an<00:19:45.800> overview<00:19:46.100> of<00:19:46.250> the<00:19:46.880> smart 00:19:47.860 --> 00:19:47.870 align:start position:0% it's a bit of an overview of the smart 00:19:47.870 --> 00:19:49.690 align:start position:0% it's a bit of an overview of the smart contractor<00:19:48.380> attention<00:19:48.740> is<00:19:48.860> this<00:19:49.040> proponent 00:19:49.690 --> 00:19:49.700 align:start position:0% contractor attention is this proponent 00:19:49.700 --> 00:19:52.390 align:start position:0% contractor attention is this proponent here<00:19:49.910> it<00:19:50.360> is<00:19:50.510> 100%<00:19:50.930> free<00:19:51.380> and<00:19:51.410> open<00:19:51.740> source<00:19:51.950> in 00:19:52.390 --> 00:19:52.400 align:start position:0% here it is 100% free and open source in 00:19:52.400 --> 00:19:55.930 align:start position:0% here it is 100% free and open source in that<00:19:52.790> it's<00:19:52.970> just<00:19:53.150> using<00:19:53.540> basic<00:19:54.040> Apache<00:19:55.040> to<00:19:55.370> on 00:19:55.930 --> 00:19:55.940 align:start position:0% that it's just using basic Apache to on 00:19:55.940 --> 00:19:59.040 align:start position:0% that it's just using basic Apache to on a<00:19:56.000> Linux<00:19:56.360> operating<00:19:56.480> system<00:19:57.160> already<00:19:58.160> HTML 00:19:59.040 --> 00:19:59.050 align:start position:0% a Linux operating system already HTML 00:19:59.050 --> 00:20:03.790 align:start position:0% a Linux operating system already HTML Javascript<00:20:00.050> and<00:20:00.470> a<00:20:00.590> bit<00:20:00.740> of<00:20:00.830> -<00:20:01.270> even<00:20:02.270> plus<00:20:02.800> the 00:20:03.790 --> 00:20:03.800 align:start position:0% Javascript and a bit of - even plus the 00:20:03.800 --> 00:20:05.680 align:start position:0% Javascript and a bit of - even plus the indexing<00:20:04.310> where<00:20:04.700> the<00:20:04.880> local<00:20:05.180> using<00:20:05.480> elastic 00:20:05.680 --> 00:20:05.690 align:start position:0% indexing where the local using elastic 00:20:05.690 --> 00:20:07.840 align:start position:0% indexing where the local using elastic search<00:20:06.020> and<00:20:06.260> that's<00:20:06.410> also<00:20:06.770> a<00:20:07.010> percent<00:20:07.640> open 00:20:07.840 --> 00:20:07.850 align:start position:0% search and that's also a percent open 00:20:07.850 --> 00:20:10.330 align:start position:0% search and that's also a percent open source<00:20:08.120> product<00:20:08.510> as<00:20:08.660> well<00:20:08.840> so<00:20:09.560> the<00:20:10.100> blockchain 00:20:10.330 --> 00:20:10.340 align:start position:0% source product as well so the blockchain 00:20:10.340 --> 00:20:13.210 align:start position:0% source product as well so the blockchain here<00:20:10.880> reading<00:20:11.660> the<00:20:11.840> data<00:20:12.110> here<00:20:12.440> and<00:20:12.710> then 00:20:13.210 --> 00:20:13.220 align:start position:0% here reading the data here and then 00:20:13.220 --> 00:20:15.490 align:start position:0% here reading the data here and then there's<00:20:13.490> multiple<00:20:14.450> interfaces<00:20:14.720> out<00:20:15.260> to 00:20:15.490 --> 00:20:15.500 align:start position:0% there's multiple interfaces out to 00:20:15.500 --> 00:20:21.400 align:start position:0% there's multiple interfaces out to different<00:20:16.040> services<00:20:16.640> from<00:20:17.210> there<00:20:17.390> so<00:20:20.230> this<00:20:21.230> is 00:20:21.400 --> 00:20:21.410 align:start position:0% different services from there so this is 00:20:21.410 --> 00:20:23.230 align:start position:0% different services from there so this is the<00:20:21.470> web<00:20:21.620> browser<00:20:21.650> search<00:20:22.310> and<00:20:22.820> this<00:20:23.000> is<00:20:23.210> a 00:20:23.230 --> 00:20:23.240 align:start position:0% the web browser search and this is a 00:20:23.240 --> 00:20:25.500 align:start position:0% the web browser search and this is a optional<00:20:24.050> third<00:20:24.290> party<00:20:24.650> things<00:20:24.950> like 00:20:25.500 --> 00:20:25.510 align:start position:0% optional third party things like 00:20:25.510 --> 00:20:27.660 align:start position:0% optional third party things like push<00:20:25.630> notifications<00:20:25.810> and<00:20:26.500> so<00:20:26.710> on<00:20:26.860> we'll<00:20:27.520> get 00:20:27.660 --> 00:20:27.670 align:start position:0% push notifications and so on we'll get 00:20:27.670 --> 00:20:29.490 align:start position:0% push notifications and so on we'll get to<00:20:27.850> this<00:20:28.030> component<00:20:28.420> in<00:20:28.750> a<00:20:28.810> little<00:20:29.050> bit<00:20:29.230> I'll 00:20:29.490 --> 00:20:29.500 align:start position:0% to this component in a little bit I'll 00:20:29.500 --> 00:20:32.490 align:start position:0% to this component in a little bit I'll talk<00:20:29.650> about<00:20:29.680> this<00:20:30.070> I<00:20:30.990> bet<00:20:31.990> so<00:20:32.140> the<00:20:32.230> smart 00:20:32.490 --> 00:20:32.500 align:start position:0% talk about this I bet so the smart 00:20:32.500 --> 00:20:34.850 align:start position:0% talk about this I bet so the smart contracts<00:20:32.950> search<00:20:33.130> engine<00:20:33.490> sits<00:20:33.940> between 00:20:34.850 --> 00:20:34.860 align:start position:0% contracts search engine sits between 00:20:34.860 --> 00:20:38.520 align:start position:0% contracts search engine sits between just<00:20:35.860> a<00:20:36.580> sits<00:20:37.180> between<00:20:37.330> the<00:20:37.600> full<00:20:37.810> note<00:20:38.080> and 00:20:38.520 --> 00:20:38.530 align:start position:0% just a sits between the full note and 00:20:38.530 --> 00:20:40.980 align:start position:0% just a sits between the full note and the<00:20:38.770> data<00:20:39.010> and<00:20:39.280> its<00:20:39.700> organizing<00:20:40.120> Rossum<00:20:40.870> our 00:20:40.980 --> 00:20:40.990 align:start position:0% the data and its organizing Rossum our 00:20:40.990 --> 00:20:43.980 align:start position:0% the data and its organizing Rossum our contract<00:20:41.410> data<00:20:41.590> and<00:20:42.360> the<00:20:43.360> blockchain<00:20:43.570> are 00:20:43.980 --> 00:20:43.990 align:start position:0% contract data and the blockchain are 00:20:43.990 --> 00:20:46.710 align:start position:0% contract data and the blockchain are like<00:20:44.350> event<00:20:44.890> logs<00:20:45.100> and<00:20:45.340> so<00:20:45.490> on<00:20:45.610> and<00:20:45.880> it's 00:20:46.710 --> 00:20:46.720 align:start position:0% like event logs and so on and it's 00:20:46.720 --> 00:20:48.600 align:start position:0% like event logs and so on and it's providing<00:20:47.290> essentially<00:20:47.860> like<00:20:48.100> a<00:20:48.130> search<00:20:48.430> and 00:20:48.600 --> 00:20:48.610 align:start position:0% providing essentially like a search and 00:20:48.610 --> 00:20:51.000 align:start position:0% providing essentially like a search and discovery<00:20:49.090> service<00:20:49.870> for<00:20:50.170> the<00:20:50.410> decentralized 00:20:51.000 --> 00:20:51.010 align:start position:0% discovery service for the decentralized 00:20:51.010 --> 00:20:55.170 align:start position:0% discovery service for the decentralized applications<00:20:52.830> okay<00:20:53.830> so<00:20:54.010> this<00:20:54.220> demo<00:20:54.610> I'm<00:20:54.940> just 00:20:55.170 --> 00:20:55.180 align:start position:0% applications okay so this demo I'm just 00:20:55.180 --> 00:20:57.060 align:start position:0% applications okay so this demo I'm just taking<00:20:55.720> some<00:20:55.750> screen<00:20:56.110> captures<00:20:56.140> if<00:20:56.560> you<00:20:56.680> go<00:20:56.830> to 00:20:57.060 --> 00:20:57.070 align:start position:0% taking some screen captures if you go to 00:20:57.070 --> 00:21:00.210 align:start position:0% taking some screen captures if you go to endorse<00:20:57.460> it<00:20:58.000> instead<00:20:58.710> there's<00:20:59.710> a<00:20:59.770> menu<00:20:59.980> down 00:21:00.210 --> 00:21:00.220 align:start position:0% endorse it instead there's a menu down 00:21:00.220 --> 00:21:01.590 align:start position:0% endorse it instead there's a menu down the<00:21:00.370> left-hand<00:21:00.640> side<00:21:00.940> you'll<00:21:01.240> see<00:21:01.450> this 00:21:01.590 --> 00:21:01.600 align:start position:0% the left-hand side you'll see this 00:21:01.600 --> 00:21:05.400 align:start position:0% the left-hand side you'll see this data-driven<00:21:02.140> depths<00:21:02.680> here<00:21:03.610> this<00:21:04.600> year<00:21:04.870> we've 00:21:05.400 --> 00:21:05.410 align:start position:0% data-driven depths here this year we've 00:21:05.410 --> 00:21:06.930 align:start position:0% data-driven depths here this year we've the<00:21:05.530> first<00:21:05.770> paragraph<00:21:06.070> that<00:21:06.340> links<00:21:06.640> off<00:21:06.790> to 00:21:06.930 --> 00:21:06.940 align:start position:0% the first paragraph that links off to 00:21:06.940 --> 00:21:09.900 align:start position:0% the first paragraph that links off to some<00:21:07.120> coding<00:21:07.540> get<00:21:07.720> up<00:21:07.870> and<00:21:08.080> this<00:21:08.680> is<00:21:08.910> HTML 00:21:09.900 --> 00:21:09.910 align:start position:0% some coding get up and this is HTML 00:21:09.910 --> 00:21:12.480 align:start position:0% some coding get up and this is HTML Javascript<00:21:10.600> and<00:21:10.690> solidity<00:21:11.380> smoke<00:21:11.920> detector 00:21:12.480 --> 00:21:12.490 align:start position:0% Javascript and solidity smoke detector 00:21:12.490 --> 00:21:14.730 align:start position:0% Javascript and solidity smoke detector and<00:21:12.700> there's<00:21:13.360> might<00:21:13.540> be<00:21:13.660> just<00:21:13.870> shown<00:21:14.050> us<00:21:14.230> this 00:21:14.730 --> 00:21:14.740 align:start position:0% and there's might be just shown us this 00:21:14.740 --> 00:21:16.920 align:start position:0% and there's might be just shown us this is<00:21:14.890> the<00:21:15.040> build<00:21:15.370> tool<00:21:15.610> that<00:21:16.000> we<00:21:16.090> have<00:21:16.120> and<00:21:16.570> so 00:21:16.920 --> 00:21:16.930 align:start position:0% is the build tool that we have and so 00:21:16.930 --> 00:21:19.980 align:start position:0% is the build tool that we have and so you<00:21:16.990> put<00:21:17.260> the<00:21:17.440> salinity<00:21:18.430> code<00:21:18.790> in<00:21:18.940> man<00:21:19.120> you<00:21:19.690> hit 00:21:19.980 --> 00:21:19.990 align:start position:0% you put the salinity code in man you hit 00:21:19.990 --> 00:21:22.530 align:start position:0% you put the salinity code in man you hit compile<00:21:20.410> and<00:21:20.920> deploy<00:21:21.250> this<00:21:21.430> so<00:21:21.970> the<00:21:22.090> argument 00:21:22.530 --> 00:21:22.540 align:start position:0% compile and deploy this so the argument 00:21:22.540 --> 00:21:24.150 align:start position:0% compile and deploy this so the argument for<00:21:22.690> this<00:21:22.780> constructor<00:21:23.470> here<00:21:23.650> is<00:21:23.710> asking<00:21:24.070> for 00:21:24.150 --> 00:21:24.160 align:start position:0% for this constructor here is asking for 00:21:24.160 --> 00:21:26.490 align:start position:0% for this constructor here is asking for an<00:21:24.250> accounting<00:21:24.730> so<00:21:25.210> we<00:21:25.330> put<00:21:25.510> in<00:21:25.600> one<00:21:26.200> five 00:21:26.490 --> 00:21:26.500 align:start position:0% an accounting so we put in one five 00:21:26.500 --> 00:21:29.220 align:start position:0% an accounting so we put in one five underscore<00:21:27.340> double<00:21:27.670> zero<00:21:27.850> one<00:21:28.090> that<00:21:28.990> to<00:21:29.140> the 00:21:29.220 --> 00:21:29.230 align:start position:0% underscore double zero one that to the 00:21:29.230 --> 00:21:31.980 align:start position:0% underscore double zero one that to the chain<00:21:29.470> and<00:21:29.740> then<00:21:30.190> what<00:21:30.790> we<00:21:30.910> see<00:21:30.940> in<00:21:31.450> the<00:21:31.810> build 00:21:31.980 --> 00:21:31.990 align:start position:0% chain and then what we see in the build 00:21:31.990 --> 00:21:33.840 align:start position:0% chain and then what we see in the build tool<00:21:32.230> women<00:21:32.500> click<00:21:32.680> the<00:21:32.800> play<00:21:32.980> button<00:21:33.010> in<00:21:33.610> the 00:21:33.840 --> 00:21:33.850 align:start position:0% tool women click the play button in the 00:21:33.850 --> 00:21:35.970 align:start position:0% tool women click the play button in the duct<00:21:34.060> tape<00:21:34.390> you<00:21:34.960> actually<00:21:35.260> deploy<00:21:35.560> the<00:21:35.740> front 00:21:35.970 --> 00:21:35.980 align:start position:0% duct tape you actually deploy the front 00:21:35.980 --> 00:21:38.160 align:start position:0% duct tape you actually deploy the front end<00:21:36.130> of<00:21:36.370> your<00:21:36.430> done<00:21:36.760> so<00:21:37.390> this<00:21:37.570> is<00:21:37.630> what<00:21:37.900> the<00:21:38.020> end 00:21:38.160 --> 00:21:38.170 align:start position:0% end of your done so this is what the end 00:21:38.170 --> 00:21:41.070 align:start position:0% end of your done so this is what the end user<00:21:38.410> will<00:21:38.530> see<00:21:39.160> and<00:21:39.400> here<00:21:40.270> we<00:21:40.390> have<00:21:40.600> this 00:21:41.070 --> 00:21:41.080 align:start position:0% user will see and here we have this 00:21:41.080 --> 00:21:43.500 align:start position:0% user will see and here we have this account<00:21:41.440> and<00:21:41.980> I<00:21:42.340> put<00:21:42.550> a<00:21:42.580> belly<00:21:42.790> in<00:21:42.970> on<00:21:43.090> one<00:21:43.360> two 00:21:43.500 --> 00:21:43.510 align:start position:0% account and I put a belly in on one two 00:21:43.510 --> 00:21:45.780 align:start position:0% account and I put a belly in on one two three<00:21:43.810> and<00:21:44.170> we<00:21:44.710> update<00:21:44.830> the<00:21:45.130> balance<00:21:45.460> and<00:21:45.670> what 00:21:45.780 --> 00:21:45.790 align:start position:0% three and we update the balance and what 00:21:45.790 --> 00:21:48.180 align:start position:0% three and we update the balance and what it<00:21:45.850> does<00:21:46.030> this<00:21:46.600> my<00:21:46.810> quick<00:21:47.200> search<00:21:47.410> engine<00:21:47.770> goes 00:21:48.180 --> 00:21:48.190 align:start position:0% it does this my quick search engine goes 00:21:48.190 --> 00:21:50.940 align:start position:0% it does this my quick search engine goes and<00:21:48.430> finds<00:21:49.230> small<00:21:50.230> contracts<00:21:50.680> on<00:21:50.860> the 00:21:50.940 --> 00:21:50.950 align:start position:0% and finds small contracts on the 00:21:50.950 --> 00:21:53.430 align:start position:0% and finds small contracts on the blockchain<00:21:51.190> that<00:21:51.700> match<00:21:52.300> so<00:21:52.720> what<00:21:53.140> we<00:21:53.230> do<00:21:53.380> is 00:21:53.430 --> 00:21:53.440 align:start position:0% blockchain that match so what we do is 00:21:53.440 --> 00:21:55.890 align:start position:0% blockchain that match so what we do is we<00:21:53.590> store<00:21:53.860> the<00:21:54.070> API<00:21:54.370> and<00:21:55.060> then<00:21:55.240> we<00:21:55.360> hash<00:21:55.570> it<00:21:55.600> so 00:21:55.890 --> 00:21:55.900 align:start position:0% we store the API and then we hash it so 00:21:55.900 --> 00:21:57.990 align:start position:0% we store the API and then we hash it so we<00:21:56.020> end<00:21:56.140> up<00:21:56.230> with<00:21:56.380> a<00:21:56.440> deterministic<00:21:57.100> key<00:21:57.400> per 00:21:57.990 --> 00:21:58.000 align:start position:0% we end up with a deterministic key per 00:21:58.000 --> 00:22:00.330 align:start position:0% we end up with a deterministic key per API<00:21:58.480> and<00:21:58.930> so<00:21:59.260> this<00:21:59.470> my<00:21:59.650> contract<00:22:00.100> search 00:22:00.330 --> 00:22:00.340 align:start position:0% API and so this my contract search 00:22:00.340 --> 00:22:02.190 align:start position:0% API and so this my contract search engine<00:22:00.670> can<00:22:00.850> go<00:22:01.300> through<00:22:01.510> the<00:22:01.630> blockchain<00:22:01.840> and 00:22:02.190 --> 00:22:02.200 align:start position:0% engine can go through the blockchain and 00:22:02.200 --> 00:22:04.380 align:start position:0% engine can go through the blockchain and find<00:22:02.500> all<00:22:02.890> the<00:22:03.100> contracts<00:22:03.640> that<00:22:03.820> match<00:22:04.360> to 00:22:04.380 --> 00:22:04.390 align:start position:0% find all the contracts that match to 00:22:04.390 --> 00:22:06.480 align:start position:0% find all the contracts that match to that<00:22:04.780> key<00:22:05.020> and<00:22:05.350> so<00:22:05.800> what<00:22:06.040> it's<00:22:06.160> essentially 00:22:06.480 --> 00:22:06.490 align:start position:0% that key and so what it's essentially 00:22:06.490 --> 00:22:08.820 align:start position:0% that key and so what it's essentially doing<00:22:06.880> here<00:22:07.120> is<00:22:07.510> finding<00:22:08.050> accounts<00:22:08.530> of 00:22:08.820 --> 00:22:08.830 align:start position:0% doing here is finding accounts of 00:22:08.830 --> 00:22:11.880 align:start position:0% doing here is finding accounts of contract<00:22:09.340> top<00:22:09.910> X<00:22:10.360> with<00:22:11.050> different<00:22:11.380> names<00:22:11.500> and 00:22:11.880 --> 00:22:11.890 align:start position:0% contract top X with different names and 00:22:11.890 --> 00:22:14.190 align:start position:0% contract top X with different names and it's<00:22:12.010> trading<00:22:12.640> the<00:22:12.790> sum<00:22:13.030> total<00:22:13.300> of<00:22:13.690> their 00:22:14.190 --> 00:22:14.200 align:start position:0% it's trading the sum total of their 00:22:14.200 --> 00:22:16.260 align:start position:0% it's trading the sum total of their balance<00:22:14.380> and<00:22:14.740> they're<00:22:15.220> providing<00:22:15.640> that<00:22:15.790> so<00:22:16.030> a 00:22:16.260 --> 00:22:16.270 align:start position:0% balance and they're providing that so a 00:22:16.270 --> 00:22:16.770 align:start position:0% balance and they're providing that so a smart 00:22:16.770 --> 00:22:16.780 align:start position:0% smart 00:22:16.780 --> 00:22:18.720 align:start position:0% smart I<00:22:16.810> can't<00:22:17.200> do<00:22:17.380> that<00:22:17.560> to<00:22:17.950> another<00:22:18.040> contractors 00:22:18.720 --> 00:22:18.730 align:start position:0% I can't do that to another contractors 00:22:18.730 --> 00:22:20.460 align:start position:0% I can't do that to another contractors they<00:22:18.820> can't<00:22:19.030> see<00:22:19.180> each<00:22:19.270> other's<00:22:19.540> data<00:22:19.750> but<00:22:20.380> the 00:22:20.460 --> 00:22:20.470 align:start position:0% they can't see each other's data but the 00:22:20.470 --> 00:22:25.860 align:start position:0% they can't see each other's data but the search<00:22:20.680> engine<00:22:21.010> can<00:22:21.190> aggregate<00:22:23.790> so<00:22:24.790> just<00:22:25.480> move 00:22:25.860 --> 00:22:25.870 align:start position:0% search engine can aggregate so just move 00:22:25.870 --> 00:22:28.500 align:start position:0% search engine can aggregate so just move on<00:22:26.050> to<00:22:26.200> this<00:22:26.320> part<00:22:26.770> here<00:22:27.010> what<00:22:27.520> we<00:22:27.640> call<00:22:27.820> the 00:22:28.500 --> 00:22:28.510 align:start position:0% on to this part here what we call the 00:22:28.510 --> 00:22:31.560 align:start position:0% on to this part here what we call the SSS<00:22:29.050> and<00:22:29.730> a-goin<00:22:30.730> police<00:22:30.970> come<00:22:31.240> talk<00:22:31.450> to<00:22:31.480> me 00:22:31.560 --> 00:22:31.570 align:start position:0% SSS and a-goin police come talk to me 00:22:31.570 --> 00:22:33.210 align:start position:0% SSS and a-goin police come talk to me afterwards<00:22:32.020> because<00:22:32.140> this<00:22:32.320> there's<00:22:32.950> too<00:22:33.100> much 00:22:33.210 --> 00:22:33.220 align:start position:0% afterwards because this there's too much 00:22:33.220 --> 00:22:35.790 align:start position:0% afterwards because this there's too much to<00:22:33.430> say<00:22:33.580> in<00:22:33.820> ten<00:22:34.000> minutes<00:22:34.150> so<00:22:34.660> this<00:22:35.140> is<00:22:35.200> the 00:22:35.790 --> 00:22:35.800 align:start position:0% to say in ten minutes so this is the 00:22:35.800 --> 00:22:38.100 align:start position:0% to say in ten minutes so this is the easiest<00:22:36.430> way<00:22:36.640> to<00:22:36.670> access<00:22:36.970> all<00:22:37.300> this<00:22:37.480> if<00:22:37.930> you 00:22:38.100 --> 00:22:38.110 align:start position:0% easiest way to access all this if you 00:22:38.110 --> 00:22:40.380 align:start position:0% easiest way to access all this if you don't<00:22:38.260> install<00:22:38.650> or<00:22:38.860> do<00:22:38.980> anything<00:22:39.250> with<00:22:39.940> any<00:22:40.270> of 00:22:40.380 --> 00:22:40.390 align:start position:0% don't install or do anything with any of 00:22:40.390 --> 00:22:42.960 align:start position:0% don't install or do anything with any of these<00:22:40.720> smart<00:22:41.290> contract<00:22:41.740> code<00:22:42.040> or<00:22:42.250> anything<00:22:42.430> if 00:22:42.960 --> 00:22:42.970 align:start position:0% these smart contract code or anything if 00:22:42.970 --> 00:22:48.270 align:start position:0% these smart contract code or anything if you<00:22:43.120> just<00:22:43.330> simply<00:22:43.570> go<00:22:43.900> to<00:22:44.040> ESS<00:22:45.040> SJS<00:22:46.770> and<00:22:47.770> you 00:22:48.270 --> 00:22:48.280 align:start position:0% you just simply go to ESS SJS and you 00:22:48.280 --> 00:22:51.120 align:start position:0% you just simply go to ESS SJS and you just<00:22:48.490> install<00:22:49.210> that<00:22:49.470> and<00:22:50.470> then<00:22:50.680> you<00:22:50.950> have 00:22:51.120 --> 00:22:51.130 align:start position:0% just install that and then you have 00:22:51.130 --> 00:22:53.700 align:start position:0% just install that and then you have instant<00:22:51.340> access<00:22:51.670> to<00:22:52.180> blockchain<00:22:53.020> data<00:22:53.260> so 00:22:53.700 --> 00:22:53.710 align:start position:0% instant access to blockchain data so 00:22:53.710 --> 00:22:55.050 align:start position:0% instant access to blockchain data so we're<00:22:53.860> running<00:22:54.100> if<00:22:54.190> the<00:22:54.310> remainder<00:22:54.880> theorem 00:22:55.050 --> 00:22:55.060 align:start position:0% we're running if the remainder theorem 00:22:55.060 --> 00:22:57.000 align:start position:0% we're running if the remainder theorem classic<00:22:55.540> sophomores<00:22:55.930> marionette<00:22:56.500> saga<00:22:56.740> miles 00:22:57.000 --> 00:22:57.010 align:start position:0% classic sophomores marionette saga miles 00:22:57.010 --> 00:22:58.770 align:start position:0% classic sophomores marionette saga miles test<00:22:57.250> net<00:22:57.430> for<00:22:57.640> the<00:22:57.700> death<00:22:57.910> train<00:22:58.150> so<00:22:58.660> these 00:22:58.770 --> 00:22:58.780 align:start position:0% test net for the death train so these 00:22:58.780 --> 00:23:00.720 align:start position:0% test net for the death train so these are<00:22:58.960> already<00:22:59.050> set<00:22:59.470> up<00:22:59.500> we<00:23:00.040> have<00:23:00.190> some<00:23:00.400> specific 00:23:00.720 --> 00:23:00.730 align:start position:0% are already set up we have some specific 00:23:00.730 --> 00:23:02.460 align:start position:0% are already set up we have some specific premade<00:23:01.450> functions<00:23:01.930> here<00:23:02.110> for<00:23:02.350> your 00:23:02.460 --> 00:23:02.470 align:start position:0% premade functions here for your 00:23:02.470 --> 00:23:04.700 align:start position:0% premade functions here for your convenience<00:23:02.770> so<00:23:03.490> for<00:23:03.700> example<00:23:04.120> you're<00:23:04.510> just 00:23:04.700 --> 00:23:04.710 align:start position:0% convenience so for example you're just 00:23:04.710 --> 00:23:07.710 align:start position:0% convenience so for example you're just esss<00:23:05.710> your<00:23:06.220> search<00:23:06.670> using<00:23:07.000> address<00:23:07.420> and 00:23:07.710 --> 00:23:07.720 align:start position:0% esss your search using address and 00:23:07.720 --> 00:23:10.170 align:start position:0% esss your search using address and that's<00:23:07.960> the<00:23:08.140> address<00:23:08.230> and<00:23:08.830> all<00:23:09.250> return<00:23:09.670> done 00:23:10.170 --> 00:23:10.180 align:start position:0% that's the address and all return done 00:23:10.180 --> 00:23:12.210 align:start position:0% that's the address and all return done the<00:23:10.720> next<00:23:10.990> thing<00:23:11.140> a<00:23:11.170> specific<00:23:11.770> thing<00:23:11.890> search 00:23:12.210 --> 00:23:12.220 align:start position:0% the next thing a specific thing search 00:23:12.220 --> 00:23:14.250 align:start position:0% the next thing a specific thing search using<00:23:12.640> keywords<00:23:12.730> so<00:23:13.330> in<00:23:13.660> this<00:23:13.870> case<00:23:14.110> that 00:23:14.250 --> 00:23:14.260 align:start position:0% using keywords so in this case that 00:23:14.260 --> 00:23:16.980 align:start position:0% using keywords so in this case that variable<00:23:14.680> name<00:23:14.890> the<00:23:15.460> account<00:23:15.550> we<00:23:16.420> put<00:23:16.690> that<00:23:16.810> in 00:23:16.980 --> 00:23:16.990 align:start position:0% variable name the account we put that in 00:23:16.990 --> 00:23:19.170 align:start position:0% variable name the account we put that in as<00:23:17.110> the<00:23:17.140> dark<00:23:17.640> and<00:23:18.640> returns 00:23:19.170 --> 00:23:19.180 align:start position:0% as the dark and returns 00:23:19.180 --> 00:23:21.960 align:start position:0% as the dark and returns well<00:23:19.750> adjacent<00:23:20.380> so<00:23:20.980> then<00:23:21.130> your<00:23:21.310> phone<00:23:21.610> can 00:23:21.960 --> 00:23:21.970 align:start position:0% well adjacent so then your phone can 00:23:21.970 --> 00:23:23.850 align:start position:0% well adjacent so then your phone can pass<00:23:22.210> this<00:23:22.480> right<00:23:22.750> that's<00:23:23.050> a<00:23:23.260> really 00:23:23.850 --> 00:23:23.860 align:start position:0% pass this right that's a really 00:23:23.860 --> 00:23:26.520 align:start position:0% pass this right that's a really efficient<00:23:24.280> way<00:23:24.430> to<00:23:24.460> call<00:23:25.330> data<00:23:25.840> blockchain 00:23:26.520 --> 00:23:26.530 align:start position:0% efficient way to call data blockchain 00:23:26.530 --> 00:23:28.410 align:start position:0% efficient way to call data blockchain data<00:23:26.770> and<00:23:27.040> get<00:23:27.220> that<00:23:27.340> back<00:23:27.550> so<00:23:27.970> instead<00:23:28.330> of 00:23:28.410 --> 00:23:28.420 align:start position:0% data and get that back so instead of 00:23:28.420 --> 00:23:29.880 align:start position:0% data and get that back so instead of your<00:23:28.540> phone<00:23:28.780> having<00:23:29.020> to<00:23:29.200> get<00:23:29.380> home<00:23:29.650> there<00:23:29.860> are 00:23:29.880 --> 00:23:29.890 align:start position:0% your phone having to get home there are 00:23:29.890 --> 00:23:31.260 align:start position:0% your phone having to get home there are some<00:23:30.040> records<00:23:30.460> and<00:23:30.580> look<00:23:30.730> through<00:23:30.910> the<00:23:31.060> wallet 00:23:31.260 --> 00:23:31.270 align:start position:0% some records and look through the wallet 00:23:31.270 --> 00:23:33.360 align:start position:0% some records and look through the wallet do<00:23:32.080> decision<00:23:32.500> making<00:23:32.800> what<00:23:32.950> you<00:23:33.040> can<00:23:33.130> do<00:23:33.250> is 00:23:33.360 --> 00:23:33.370 align:start position:0% do decision making what you can do is 00:23:33.370 --> 00:23:35.370 align:start position:0% do decision making what you can do is quite<00:23:33.610> a<00:23:33.640> complex<00:23:34.060> query<00:23:34.960> where<00:23:35.140> you<00:23:35.230> can 00:23:35.370 --> 00:23:35.380 align:start position:0% quite a complex query where you can 00:23:35.380 --> 00:23:36.960 align:start position:0% quite a complex query where you can filter<00:23:35.650> out<00:23:35.800> so<00:23:36.400> I<00:23:36.430> don't<00:23:36.610> want<00:23:36.820> to<00:23:36.880> see 00:23:36.960 --> 00:23:36.970 align:start position:0% filter out so I don't want to see 00:23:36.970 --> 00:23:38.430 align:start position:0% filter out so I don't want to see everything<00:23:37.360> in<00:23:37.450> the<00:23:37.480> last<00:23:37.690> AR<00:23:37.960> from<00:23:38.260> this 00:23:38.430 --> 00:23:38.440 align:start position:0% everything in the last AR from this 00:23:38.440 --> 00:23:39.870 align:start position:0% everything in the last AR from this address<00:23:38.650> with<00:23:38.980> an<00:23:39.100> account<00:23:39.370> name<00:23:39.550> called 00:23:39.870 --> 00:23:39.880 align:start position:0% address with an account name called 00:23:39.880 --> 00:23:41.880 align:start position:0% address with an account name called DEFCON<00:23:40.210> and<00:23:40.660> then<00:23:41.080> you'll<00:23:41.170> just<00:23:41.260> get<00:23:41.470> back<00:23:41.680> one 00:23:41.880 --> 00:23:41.890 align:start position:0% DEFCON and then you'll just get back one 00:23:41.890 --> 00:23:43.950 align:start position:0% DEFCON and then you'll just get back one report<00:23:42.310> so<00:23:42.490> it's<00:23:42.670> really<00:23:42.880> efficient<00:23:43.360> and<00:23:43.750> then 00:23:43.950 --> 00:23:43.960 align:start position:0% report so it's really efficient and then 00:23:43.960 --> 00:23:46.620 align:start position:0% report so it's really efficient and then you'll<00:23:44.080> find<00:23:44.290> any<00:23:44.470> active<00:23:44.830> process<00:23:45.250> one<00:23:45.880> small 00:23:46.620 --> 00:23:46.630 align:start position:0% you'll find any active process one small 00:23:46.630 --> 00:23:48.610 align:start position:0% you'll find any active process one small piece<00:23:46.930> of<00:23:46.990> Jason 00:23:48.610 --> 00:23:48.620 align:start position:0% piece of Jason 00:23:48.620 --> 00:23:51.370 align:start position:0% piece of Jason okay<00:23:48.950> so<00:23:49.010> one<00:23:49.880> of<00:23:49.909> the<00:23:50.059> reasons<00:23:50.240> why<00:23:51.049> this<00:23:51.110> is 00:23:51.370 --> 00:23:51.380 align:start position:0% okay so one of the reasons why this is 00:23:51.380 --> 00:23:53.500 align:start position:0% okay so one of the reasons why this is all<00:23:52.190> right<00:23:52.309> this<00:23:52.460> because<00:23:52.789> it's<00:23:52.940> separating 00:23:53.500 --> 00:23:53.510 align:start position:0% all right this because it's separating 00:23:53.510 --> 00:23:54.519 align:start position:0% all right this because it's separating out<00:23:53.600> it's<00:23:53.720> very<00:23:53.750> flexible<00:23:54.260> but<00:23:54.380> it's 00:23:54.519 --> 00:23:54.529 align:start position:0% out it's very flexible but it's 00:23:54.529 --> 00:23:57.190 align:start position:0% out it's very flexible but it's simmering<00:23:54.799> it<00:23:54.950> out<00:23:55.190> the<00:23:55.370> components<00:23:55.970> so<00:23:56.480> if 00:23:57.190 --> 00:23:57.200 align:start position:0% simmering it out the components so if 00:23:57.200 --> 00:23:59.169 align:start position:0% simmering it out the components so if you<00:23:57.320> have<00:23:57.440> a<00:23:57.470> friend<00:23:57.710> developer<00:23:58.279> that's<00:23:58.820> a 00:23:59.169 --> 00:23:59.179 align:start position:0% you have a friend developer that's a 00:23:59.179 --> 00:24:01.360 align:start position:0% you have a friend developer that's a really<00:23:59.900> different<00:24:00.080> skill<00:24:00.440> set<00:24:00.679> you<00:24:00.919> can<00:24:01.039> just 00:24:01.360 --> 00:24:01.370 align:start position:0% really different skill set you can just 00:24:01.370 --> 00:24:03.669 align:start position:0% really different skill set you can just take<00:24:01.549> them<00:24:01.730> you<00:24:01.880> know<00:24:02.120> JavaScript<00:24:02.840> and<00:24:03.200> HTML 00:24:03.669 --> 00:24:03.679 align:start position:0% take them you know JavaScript and HTML 00:24:03.679 --> 00:24:05.649 align:start position:0% take them you know JavaScript and HTML and<00:24:03.710> CSS<00:24:04.070> but<00:24:04.850> what<00:24:04.970> you<00:24:05.090> do<00:24:05.210> and<00:24:05.330> this<00:24:05.390> is<00:24:05.539> what 00:24:05.649 --> 00:24:05.659 align:start position:0% and CSS but what you do and this is what 00:24:05.659 --> 00:24:07.480 align:start position:0% and CSS but what you do and this is what I<00:24:05.690> want<00:24:05.900> my<00:24:05.929> duck<00:24:06.200> to<00:24:06.380> do<00:24:06.559> from<00:24:07.070> the<00:24:07.159> users 00:24:07.480 --> 00:24:07.490 align:start position:0% I want my duck to do from the users 00:24:07.490 --> 00:24:09.340 align:start position:0% I want my duck to do from the users perspective<00:24:07.700> you<00:24:08.539> don't<00:24:08.570> need<00:24:08.809> to<00:24:08.929> know<00:24:09.110> when 00:24:09.340 --> 00:24:09.350 align:start position:0% perspective you don't need to know when 00:24:09.350 --> 00:24:10.480 align:start position:0% perspective you don't need to know when they<00:24:09.529> push<00:24:09.740> the<00:24:09.860> button<00:24:10.130> that's<00:24:10.250> going<00:24:10.400> to 00:24:10.480 --> 00:24:10.490 align:start position:0% they push the button that's going to 00:24:10.490 --> 00:24:12.760 align:start position:0% they push the button that's going to call<00:24:10.700> smart<00:24:11.390> contract<00:24:11.929> functions<00:24:12.350> and<00:24:12.500> so<00:24:12.650> on 00:24:12.760 --> 00:24:12.770 align:start position:0% call smart contract functions and so on 00:24:12.770 --> 00:24:14.769 align:start position:0% call smart contract functions and so on just<00:24:12.799> don't<00:24:13.220> worry<00:24:13.370> about<00:24:13.460> that<00:24:13.730> just<00:24:14.299> poke<00:24:14.600> up 00:24:14.769 --> 00:24:14.779 align:start position:0% just don't worry about that just poke up 00:24:14.779 --> 00:24:16.600 align:start position:0% just don't worry about that just poke up the<00:24:14.900> front<00:24:15.049> end<00:24:15.200> of<00:24:15.350> the<00:24:15.440> HTML<00:24:15.890> Javascript<00:24:16.429> and 00:24:16.600 --> 00:24:16.610 align:start position:0% the front end of the HTML Javascript and 00:24:16.610 --> 00:24:20.409 align:start position:0% the front end of the HTML Javascript and CSS<00:24:16.700> so<00:24:17.690> it's<00:24:18.679> enabling<00:24:19.130> you<00:24:19.309> to<00:24:19.340> have<00:24:20.120> teams 00:24:20.409 --> 00:24:20.419 align:start position:0% CSS so it's enabling you to have teams 00:24:20.419 --> 00:24:22.810 align:start position:0% CSS so it's enabling you to have teams work<00:24:20.690> together<00:24:20.779> similar<00:24:21.740> to<00:24:21.950> the<00:24:22.190> the<00:24:22.580> rules 00:24:22.810 --> 00:24:22.820 align:start position:0% work together similar to the the rules 00:24:22.820 --> 00:24:24.970 align:start position:0% work together similar to the the rules engine<00:24:23.149> allows<00:24:23.419> like<00:24:23.659> a<00:24:23.690> business<00:24:24.080> analyst<00:24:24.440> to 00:24:24.970 --> 00:24:24.980 align:start position:0% engine allows like a business analyst to 00:24:24.980 --> 00:24:28.090 align:start position:0% engine allows like a business analyst to write<00:24:25.220> rules<00:24:25.909> and<00:24:26.450> rules<00:24:26.779> and<00:24:27.049> hand<00:24:27.919> that<00:24:28.039> off 00:24:28.090 --> 00:24:28.100 align:start position:0% write rules and rules and hand that off 00:24:28.100 --> 00:24:30.010 align:start position:0% write rules and rules and hand that off they<00:24:28.820> don't<00:24:29.000> need<00:24:29.120> to<00:24:29.270> actually<00:24:29.419> be<00:24:29.779> able<00:24:29.840> to 00:24:30.010 --> 00:24:30.020 align:start position:0% they don't need to actually be able to 00:24:30.020 --> 00:24:33.039 align:start position:0% they don't need to actually be able to contract<00:24:30.440> the<00:24:31.220> right<00:24:31.399> contractor<00:24:32.299> but<00:24:32.539> that 00:24:33.039 --> 00:24:33.049 align:start position:0% contract the right contractor but that 00:24:33.049 --> 00:24:35.110 align:start position:0% contract the right contractor but that same<00:24:33.289> syntax<00:24:33.770> will<00:24:34.010> apply<00:24:34.250> and<00:24:34.730> just<00:24:34.970> plug 00:24:35.110 --> 00:24:35.120 align:start position:0% same syntax will apply and just plug 00:24:35.120 --> 00:24:37.450 align:start position:0% same syntax will apply and just plug straight<00:24:35.450> in<00:24:35.570> and<00:24:35.720> work<00:24:35.870> so<00:24:36.140> this<00:24:36.620> concept<00:24:37.279> to 00:24:37.450 --> 00:24:37.460 align:start position:0% straight in and work so this concept to 00:24:37.460 --> 00:24:39.789 align:start position:0% straight in and work so this concept to that<00:24:37.580> you<00:24:38.419> can<00:24:38.570> create<00:24:38.840> your<00:24:38.960> own<00:24:39.020> custom 00:24:39.789 --> 00:24:39.799 align:start position:0% that you can create your own custom 00:24:39.799 --> 00:24:41.980 align:start position:0% that you can create your own custom queries<00:24:40.190> you<00:24:40.669> can<00:24:41.120> extend<00:24:41.419> on<00:24:41.630> this<00:24:41.779> to 00:24:41.980 --> 00:24:41.990 align:start position:0% queries you can extend on this to 00:24:41.990 --> 00:24:43.990 align:start position:0% queries you can extend on this to provide<00:24:42.260> like<00:24:42.529> customer<00:24:43.010> push<00:24:43.250> notifications 00:24:43.990 --> 00:24:44.000 align:start position:0% provide like customer push notifications 00:24:44.000 --> 00:24:45.460 align:start position:0% provide like customer push notifications you<00:24:44.419> know<00:24:44.630> triggering<00:24:45.020> what<00:24:45.049> amounts<00:24:45.440> to 00:24:45.460 --> 00:24:45.470 align:start position:0% you know triggering what amounts to 00:24:45.470 --> 00:24:47.590 align:start position:0% you know triggering what amounts to overall<00:24:45.980> under<00:24:46.279> certain<00:24:46.640> values<00:24:47.090> etc 00:24:47.590 --> 00:24:47.600 align:start position:0% overall under certain values etc 00:24:47.600 --> 00:24:51.370 align:start position:0% overall under certain values etc and<00:24:49.000> I'll<00:24:50.000> pull<00:24:50.240> it<00:24:50.270> up<00:24:50.419> if<00:24:50.779> you're<00:24:50.960> interested 00:24:51.370 --> 00:24:51.380 align:start position:0% and I'll pull it up if you're interested 00:24:51.380 --> 00:24:54.370 align:start position:0% and I'll pull it up if you're interested in<00:24:51.620> building<00:24:52.399> your<00:24:52.640> own<00:24:52.970> or<00:24:53.510> using<00:24:53.870> hours<00:24:54.049> or 00:24:54.370 --> 00:24:54.380 align:start position:0% in building your own or using hours or 00:24:54.380 --> 00:24:56.200 align:start position:0% in building your own or using hours or deploying<00:24:54.980> it<00:24:55.100> up<00:24:55.279> and<00:24:55.490> creating<00:24:55.760> the<00:24:55.820> product 00:24:56.200 --> 00:24:56.210 align:start position:0% deploying it up and creating the product 00:24:56.210 --> 00:24:57.840 align:start position:0% deploying it up and creating the product please<00:24:56.659> get<00:24:56.840> in<00:24:56.929> touch<00:24:56.960> and<00:24:57.140> we'll<00:24:57.440> help<00:24:57.679> you 00:24:57.840 --> 00:24:57.850 align:start position:0% please get in touch and we'll help you 00:24:57.850 --> 00:25:06.240 align:start position:0% please get in touch and we'll help you [Music] 00:25:06.240 --> 00:25:06.250 align:start position:0% 00:25:06.250 --> 00:25:09.310 align:start position:0% [Music] 00:25:09.310 --> 00:25:09.320 align:start position:0% [Music] 00:25:09.320 --> 00:25:14.020 align:start position:0% all<00:25:09.860> right<00:25:10.040> so<00:25:11.080> we<00:25:12.080> have<00:25:12.110> this<00:25:12.380> possible<00:25:13.030> to 00:25:14.020 --> 00:25:14.030 align:start position:0% all right so we have this possible to 00:25:14.030 --> 00:25:20.400 align:start position:0% all right so we have this possible to challenges<00:25:14.540> and<00:25:15.850> parties 00:25:20.400 --> 00:25:20.410 align:start position:0% 00:25:20.410 --> 00:25:23.080 align:start position:0% in<00:25:21.410> the<00:25:21.530> second<00:25:21.860> abilities<00:25:22.250> would<00:25:22.550> have<00:25:22.730> a<00:25:22.760> few 00:25:23.080 --> 00:25:23.090 align:start position:0% in the second abilities would have a few 00:25:23.090 --> 00:25:26.770 align:start position:0% in the second abilities would have a few stuff<00:25:23.420> outside<00:25:24.230> of<00:25:24.530> the<00:25:24.680> UVM<00:25:25.130> so<00:25:25.430> that<00:25:25.780> the 00:25:26.770 --> 00:25:26.780 align:start position:0% stuff outside of the UVM so that the 00:25:26.780 --> 00:26:11.090 align:start position:0% stuff outside of the UVM so that the mountains<00:25:27.650> that<00:25:27.800> they<00:25:27.920> can<00:25:28.310> flow<00:25:28.580> out 00:26:11.090 --> 00:26:11.100 align:start position:0% 00:26:11.100 --> 00:26:15.269 align:start position:0% [Music] 00:26:15.269 --> 00:26:15.279 align:start position:0% 00:26:15.279 --> 00:26:20.049 align:start position:0% we<00:26:16.279> impress<00:26:17.000> LVN<00:26:17.809> our<00:26:18.470> foots<00:26:19.460> on<00:26:19.669> fire<00:26:19.700> twice 00:26:20.049 --> 00:26:20.059 align:start position:0% we impress LVN our foots on fire twice 00:26:20.059 --> 00:26:23.190 align:start position:0% we impress LVN our foots on fire twice to<00:26:20.450> the<00:26:20.570> heart<00:26:21.440> and<00:26:22.010> first<00:26:22.370> of<00:26:22.490> all<00:26:22.610> because 00:26:23.190 --> 00:26:23.200 align:start position:0% to the heart and first of all because 00:26:23.200 --> 00:26:27.669 align:start position:0% to the heart and first of all because elegant<00:26:25.570> always<00:26:26.570> just<00:26:26.840> like<00:26:27.049> a<00:26:27.080> jerk 00:26:27.669 --> 00:26:27.679 align:start position:0% elegant always just like a jerk 00:26:27.679 --> 00:26:32.049 align:start position:0% elegant always just like a jerk cc-come<00:26:28.429> hell<00:26:29.110> so<00:26:30.110> it<00:26:30.350> has<00:26:31.130> a<00:26:31.159> call<00:26:31.490> like<00:26:31.700> a 00:26:32.049 --> 00:26:32.059 align:start position:0% cc-come hell so it has a call like a 00:26:32.059 --> 00:26:35.080 align:start position:0% cc-come hell so it has a call like a signal<00:26:32.570> to<00:26:32.720> us<00:26:32.809> to<00:26:33.080> see<00:26:33.350> or<00:26:33.740> rosto<00:26:34.309> provide<00:26:34.789> all 00:26:35.080 --> 00:26:35.090 align:start position:0% signal to us to see or rosto provide all 00:26:35.090 --> 00:26:39.720 align:start position:0% signal to us to see or rosto provide all you<00:26:35.299> can<00:26:35.570> see<00:26:35.840> yes<00:26:36.289> they<00:26:36.919> all<00:26:37.070> will<00:26:37.309> have 00:26:39.720 --> 00:26:39.730 align:start position:0% 00:26:39.730 --> 00:26:43.450 align:start position:0% support<00:26:40.730> in<00:26:41.539> language<00:26:42.019> to<00:26:42.139> you<00:26:42.230> if<00:26:43.190> you<00:26:43.429> are 00:26:43.450 --> 00:26:43.460 align:start position:0% support in language to you if you are 00:26:43.460 --> 00:26:49.480 align:start position:0% support in language to you if you are not<00:26:44.269> interesting<00:26:44.779> with<00:26:46.210> just 00:26:49.480 --> 00:26:49.490 align:start position:0% 00:26:49.490 --> 00:26:53.340 align:start position:0% he<00:26:50.059> want<00:26:50.480> to<00:26:50.600> use<00:26:50.779> your<00:26:51.070> fire 00:26:53.340 --> 00:26:53.350 align:start position:0% he want to use your fire 00:26:53.350 --> 00:26:57.010 align:start position:0% he want to use your fire Alice<00:26:54.350> languages<00:26:54.890> yes<00:26:55.190> in<00:26:55.610> venues<00:26:55.970> Albion<00:26:56.659> and 00:26:57.010 --> 00:26:57.020 align:start position:0% Alice languages yes in venues Albion and 00:26:57.020 --> 00:26:58.000 align:start position:0% Alice languages yes in venues Albion and the<00:26:57.320> umpires 00:26:58.000 --> 00:26:58.010 align:start position:0% the umpires 00:26:58.010 --> 00:27:02.200 align:start position:0% the umpires that<00:26:58.990> with<00:26:59.990> our<00:27:00.200> BN<00:27:00.620> if<00:27:00.919> we<00:27:01.159> want<00:27:01.429> to<00:27:01.520> define<00:27:02.149> a 00:27:02.200 --> 00:27:02.210 align:start position:0% that with our BN if we want to define a 00:27:02.210 --> 00:27:05.680 align:start position:0% that with our BN if we want to define a new<00:27:02.570> target<00:27:03.080> West<00:27:03.740> in<00:27:04.059> Pakistan<00:27:05.059> tonight<00:27:05.360> that 00:27:05.680 --> 00:27:05.690 align:start position:0% new target West in Pakistan tonight that 00:27:05.690 --> 00:27:11.769 align:start position:0% new target West in Pakistan tonight that we<00:27:05.990> have<00:27:06.370> one<00:27:07.370> we<00:27:07.640> have<00:27:08.470> yossel<00:27:09.470> maybe<00:27:09.980> if<00:27:10.779> what 00:27:11.769 --> 00:27:11.779 align:start position:0% we have one we have yossel maybe if what 00:27:11.779 --> 00:27:13.810 align:start position:0% we have one we have yossel maybe if what that<00:27:11.990> happens<00:27:12.380> maybe<00:27:12.830> there<00:27:13.220> will<00:27:13.490> be<00:27:13.549> the 00:27:13.810 --> 00:27:13.820 align:start position:0% that happens maybe there will be the 00:27:13.820 --> 00:27:16.960 align:start position:0% that happens maybe there will be the Boston<00:27:14.720> familiar<00:27:15.710> with<00:27:15.919> the<00:27:16.039> EBS<00:27:16.520> three<00:27:16.820> or 00:27:16.960 --> 00:27:16.970 align:start position:0% Boston familiar with the EBS three or 00:27:16.970 --> 00:27:22.149 align:start position:0% Boston familiar with the EBS three or four<00:27:17.659> or<00:27:17.899> five<00:27:18.110> so<00:27:20.230> Albion<00:27:21.230> provide<00:27:21.860> a 00:27:22.149 --> 00:27:22.159 align:start position:0% four or five so Albion provide a 00:27:22.159 --> 00:27:25.299 align:start position:0% four or five so Albion provide a mechanism<00:27:23.000> that<00:27:23.570> we<00:27:23.870> can<00:27:24.080> very<00:27:24.409> easy<00:27:24.740> to 00:27:25.299 --> 00:27:25.309 align:start position:0% mechanism that we can very easy to 00:27:25.309 --> 00:27:29.590 align:start position:0% mechanism that we can very easy to define<00:27:25.970> a<00:27:26.330> new<00:27:26.450> target<00:27:26.929> and<00:27:27.640> this<00:27:28.640> DC<00:27:29.059> vendor 00:27:29.590 --> 00:27:29.600 align:start position:0% define a new target and this DC vendor 00:27:29.600 --> 00:27:31.630 align:start position:0% define a new target and this DC vendor with<00:27:29.779> your<00:27:30.080> financial<00:27:30.559> you<00:27:30.950> don't<00:27:31.159> mean<00:27:31.490> to 00:27:31.630 --> 00:27:31.640 align:start position:0% with your financial you don't mean to 00:27:31.640 --> 00:27:34.060 align:start position:0% with your financial you don't mean to have<00:27:31.820> to<00:27:32.120> translate<00:27:32.480> your<00:27:33.070> oscillatory 00:27:34.060 --> 00:27:34.070 align:start position:0% have to translate your oscillatory 00:27:34.070 --> 00:27:38.529 align:start position:0% have to translate your oscillatory directly<00:27:34.970> to<00:27:35.240> the<00:27:35.450> mean<00:27:35.779> pocket<00:27:36.230> you<00:27:36.770> can<00:27:37.539> use 00:27:38.529 --> 00:27:38.539 align:start position:0% directly to the mean pocket you can use 00:27:38.539 --> 00:27:42.850 align:start position:0% directly to the mean pocket you can use the<00:27:38.899> Oviatt<00:27:39.500> because<00:27:40.899> intermediate<00:27:41.899> format 00:27:42.850 --> 00:27:42.860 align:start position:0% the Oviatt because intermediate format 00:27:42.860 --> 00:27:45.610 align:start position:0% the Oviatt because intermediate format called<00:27:43.190> lv<00:27:43.610> NIR<00:27:44.059> so<00:27:44.360> every<00:27:44.960> language<00:27:45.140> will<00:27:45.590> be 00:27:45.610 --> 00:27:45.620 align:start position:0% called lv NIR so every language will be 00:27:45.620 --> 00:27:49.149 align:start position:0% called lv NIR so every language will be transformed<00:27:46.340> into<00:27:46.460> a<00:27:46.610> unit<00:27:47.330> your<00:27:48.159> uniform 00:27:49.149 --> 00:27:49.159 align:start position:0% transformed into a unit your uniform 00:27:49.159 --> 00:27:52.000 align:start position:0% transformed into a unit your uniform uniform<00:27:50.000> language<00:27:50.419> and<00:27:50.690> then<00:27:51.169> use<00:27:51.590> this 00:27:52.000 --> 00:27:52.010 align:start position:0% uniform language and then use this 00:27:52.010 --> 00:27:55.029 align:start position:0% uniform language and then use this language<00:27:52.370> in<00:27:52.850> two<00:27:53.289> different<00:27:54.289> objects<00:27:54.980> so 00:27:55.029 --> 00:27:55.039 align:start position:0% language in two different objects so 00:27:55.039 --> 00:28:02.799 align:start position:0% language in two different objects so this<00:27:55.399> is<00:27:57.279> a<00:27:59.440> surprise<00:28:00.440> as<00:28:00.980> we<00:28:01.340> have<00:28:01.659> lots<00:28:02.659> of 00:28:02.799 --> 00:28:02.809 align:start position:0% this is a surprise as we have lots of 00:28:02.809 --> 00:28:06.510 align:start position:0% this is a surprise as we have lots of new<00:28:03.500> partners<00:28:04.159> or<00:28:04.460> dangers<00:28:04.970> of<00:28:05.210> problems<00:28:05.870> in 00:28:06.510 --> 00:28:06.520 align:start position:0% new partners or dangers of problems in 00:28:06.520 --> 00:28:10.060 align:start position:0% new partners or dangers of problems in fortune<00:28:07.520> for<00:28:08.000> VN<00:28:08.960> so<00:28:09.350> when<00:28:09.590> we<00:28:09.740> just 00:28:10.060 --> 00:28:10.070 align:start position:0% fortune for VN so when we just 00:28:10.070 --> 00:28:13.539 align:start position:0% fortune for VN so when we just integrated<00:28:10.789> their<00:28:11.120> way<00:28:11.360> into<00:28:12.010> the<00:28:13.010> question 00:28:13.539 --> 00:28:13.549 align:start position:0% integrated their way into the question 00:28:13.549 --> 00:28:18.779 align:start position:0% integrated their way into the question which<00:28:14.059> M<00:28:14.299> so<00:28:14.950> the<00:28:15.950> debuggers<00:28:16.520> we<00:28:17.090> don't 00:28:18.779 --> 00:28:18.789 align:start position:0% which M so the debuggers we don't 00:28:18.789 --> 00:28:20.909 align:start position:0% which M so the debuggers we don't -<00:28:18.909> its<00:28:19.149> weekend<00:28:19.599> during<00:28:19.839> average<00:28:20.619> of<00:28:20.769> the 00:28:20.909 --> 00:28:20.919 align:start position:0% - its weekend during average of the 00:28:20.919 --> 00:28:24.229 align:start position:0% - its weekend during average of the perennial<00:28:21.820> VP<00:28:22.239> or<00:28:22.329> something<00:28:22.779> like<00:28:22.869> that<00:28:22.929> and 00:28:24.229 --> 00:28:24.239 align:start position:0% perennial VP or something like that and 00:28:24.239 --> 00:28:27.089 align:start position:0% perennial VP or something like that and the<00:28:25.239> host<00:28:25.479> parties<00:28:25.839> well<00:28:26.169> we<00:28:26.379> want<00:28:26.589> to<00:28:26.679> talk 00:28:27.089 --> 00:28:27.099 align:start position:0% the host parties well we want to talk 00:28:27.099 --> 00:28:32.369 align:start position:0% the host parties well we want to talk about<00:28:27.369> more<00:28:27.869> banana<00:28:30.659> leaf<00:28:31.659> love<00:28:31.899> healthy 00:28:32.369 --> 00:28:32.379 align:start position:0% about more banana leaf love healthy 00:28:32.379 --> 00:28:35.399 align:start position:0% about more banana leaf love healthy infant<00:28:32.739> walk<00:28:32.889> we<00:28:33.159> can<00:28:33.190> define<00:28:33.759> a<00:28:33.789> new<00:28:34.409> cast 00:28:35.399 --> 00:28:35.409 align:start position:0% infant walk we can define a new cast 00:28:35.409 --> 00:28:43.859 align:start position:0% infant walk we can define a new cast optimization<00:28:36.159> skill<00:28:36.579> that<00:28:36.969> less<00:28:37.419> can<00:28:42.690> so<00:28:43.690> we 00:28:43.859 --> 00:28:43.869 align:start position:0% optimization skill that less can so we 00:28:43.869 --> 00:28:57.509 align:start position:0% optimization skill that less can so we can<00:28:44.139> just<00:28:44.579> modify<00:28:45.579> each<00:28:46.199> augmentation<00:28:55.079> so<00:28:56.519> my 00:28:57.509 --> 00:28:57.519 align:start position:0% can just modify each augmentation so my 00:28:57.519 --> 00:28:59.849 align:start position:0% can just modify each augmentation so my style<00:28:57.909> is<00:28:58.179> more<00:28:58.449> programming<00:28:59.349> language<00:28:59.619> on 00:28:59.849 --> 00:28:59.859 align:start position:0% style is more programming language on 00:28:59.859 --> 00:29:04.669 align:start position:0% style is more programming language on IBM's<00:29:00.399> and<00:29:01.499> all<00:29:02.499> proceeds<00:29:03.039> will<00:29:03.579> be<00:29:03.969> be 00:29:04.669 --> 00:29:04.679 align:start position:0% IBM's and all proceeds will be be 00:29:04.679 --> 00:29:07.649 align:start position:0% IBM's and all proceeds will be be translated<00:29:05.679> library's<00:29:06.279> certainty<00:29:06.969> or<00:29:07.149> writer 00:29:07.649 --> 00:29:07.659 align:start position:0% translated library's certainty or writer 00:29:07.659 --> 00:29:10.859 align:start position:0% translated library's certainty or writer or<00:29:08.039> Rasta<00:29:09.039> or<00:29:09.219> Cephas<00:29:09.609> or<00:29:09.789> any<00:29:10.149> foreign 00:29:10.859 --> 00:29:10.869 align:start position:0% or Rasta or Cephas or any foreign 00:29:10.869 --> 00:29:15.209 align:start position:0% or Rasta or Cephas or any foreign language<00:29:11.319> they<00:29:11.589> will<00:29:11.769> be<00:29:12.929> they<00:29:13.929> will<00:29:14.219> be 00:29:15.209 --> 00:29:15.219 align:start position:0% language they will be they will be 00:29:15.219 --> 00:29:18.329 align:start position:0% language they will be they will be passed<00:29:15.549> and<00:29:16.259> constructs<00:29:17.259> with<00:29:17.409> the<00:29:17.529> SBA<00:29:18.009> heart 00:29:18.329 --> 00:29:18.339 align:start position:0% passed and constructs with the SBA heart 00:29:18.339 --> 00:29:20.669 align:start position:0% passed and constructs with the SBA heart rate<00:29:18.579> and<00:29:18.819> funding<00:29:19.779> which<00:29:19.959> generates<00:29:20.469> the 00:29:20.669 --> 00:29:20.679 align:start position:0% rate and funding which generates the 00:29:20.679 --> 00:29:23.609 align:start position:0% rate and funding which generates the healthy<00:29:21.069> IR<00:29:21.519> and<00:29:21.969> in<00:29:22.509> effect<00:29:22.809> we<00:29:23.109> call<00:29:23.319> you<00:29:23.409> up 00:29:23.609 --> 00:29:23.619 align:start position:0% healthy IR and in effect we call you up 00:29:23.619 --> 00:29:25.799 align:start position:0% healthy IR and in effect we call you up max<00:29:23.859> are<00:29:24.009> because<00:29:24.309> we<00:29:24.549> can<00:29:24.759> add<00:29:24.999> lots<00:29:25.509> of 00:29:25.799 --> 00:29:25.809 align:start position:0% max are because we can add lots of 00:29:25.809 --> 00:29:31.430 align:start position:0% max are because we can add lots of manager<00:29:26.769> here<00:29:27.159> some<00:29:27.699> sniper<00:29:27.969> can<00:29:29.519> reduce 00:29:31.430 --> 00:29:31.440 align:start position:0% manager here some sniper can reduce 00:29:31.440 --> 00:29:35.099 align:start position:0% manager here some sniper can reduce reduce<00:29:32.440> the<00:29:32.739> echo<00:29:33.159> or<00:29:33.519> again<00:29:34.359> we<00:29:34.719> can<00:29:34.899> just 00:29:35.099 --> 00:29:35.109 align:start position:0% reduce the echo or again we can just 00:29:35.109 --> 00:30:12.280 align:start position:0% reduce the echo or again we can just simplify<00:29:35.499> a<00:29:35.739> lot<00:29:36.009> of<00:29:37.679> addition<00:29:38.679> or<00:29:38.949> multiple 00:30:12.280 --> 00:30:12.290 align:start position:0% 00:30:12.290 --> 00:30:20.100 align:start position:0% [Music] 00:30:20.100 --> 00:30:20.110 align:start position:0% 00:30:20.110 --> 00:30:23.169 align:start position:0% [Music] 00:30:23.169 --> 00:30:23.179 align:start position:0% [Music] 00:30:23.179 --> 00:30:28.610 align:start position:0% [Music] current<00:30:25.399> it's<00:30:26.399> very<00:30:26.610> easy<00:30:26.880> in<00:30:27.600> this<00:30:27.929> photo 00:30:28.610 --> 00:30:28.620 align:start position:0% current it's very easy in this photo 00:30:28.620 --> 00:30:31.190 align:start position:0% current it's very easy in this photo charts<00:30:29.070> we<00:30:29.519> only<00:30:29.730> do<00:30:30.000> what's<00:30:30.299> the<00:30:30.539> latest<00:30:30.840> with 00:30:31.190 --> 00:30:31.200 align:start position:0% charts we only do what's the latest with 00:30:31.200 --> 00:30:31.879 align:start position:0% charts we only do what's the latest with Madonna 00:30:31.879 --> 00:30:31.889 align:start position:0% Madonna 00:30:31.889 --> 00:30:35.960 align:start position:0% Madonna Olivia<00:30:32.370> I<00:30:32.580> are<00:30:32.850> with<00:30:33.389> a<00:30:33.690> native<00:30:34.380> of<00:30:34.889> Michael<00:30:35.700> so 00:30:35.960 --> 00:30:35.970 align:start position:0% Olivia I are with a native of Michael so 00:30:35.970 --> 00:30:39.139 align:start position:0% Olivia I are with a native of Michael so we<00:30:36.360> can<00:30:36.570> know<00:30:36.750> every<00:30:37.289> instruction<00:30:38.130> in<00:30:38.789> high 00:30:39.139 --> 00:30:39.149 align:start position:0% we can know every instruction in high 00:30:39.149 --> 00:30:42.740 align:start position:0% we can know every instruction in high level<00:30:39.539> the<00:30:40.200> closer<00:30:40.500> it<00:30:40.919> is<00:30:40.950> the<00:30:41.549> closer<00:30:42.480> is 00:30:42.740 --> 00:30:42.750 align:start position:0% level the closer it is the closer is 00:30:42.750 --> 00:30:45.139 align:start position:0% level the closer it is the closer is like<00:30:43.039> hunter<00:30:44.039> -<00:30:44.340> hunter<00:30:44.370> or<00:30:44.760> something<00:30:44.789> like 00:30:45.139 --> 00:30:45.149 align:start position:0% like hunter - hunter or something like 00:30:45.149 --> 00:30:49.389 align:start position:0% like hunter - hunter or something like that<00:30:45.210> and<00:30:45.590> we<00:30:46.590> can<00:30:46.620> apply<00:30:46.980> lots<00:30:47.490> of<00:30:47.700> difference 00:30:49.389 --> 00:30:49.399 align:start position:0% that and we can apply lots of difference 00:30:49.399 --> 00:30:53.950 align:start position:0% that and we can apply lots of difference here<00:30:51.169> right<00:30:52.169> here<00:30:52.409> well<00:30:52.710> we<00:30:52.889> met<00:30:53.370> in<00:30:53.549> the 00:30:53.950 --> 00:30:53.960 align:start position:0% here right here well we met in the 00:30:53.960 --> 00:30:56.870 align:start position:0% here right here well we met in the assembly<00:30:54.960> center<00:30:55.260> he<00:30:55.440> was<00:30:55.470> a<00:30:55.620> non-indian<00:30:56.220> and 00:30:56.870 --> 00:30:56.880 align:start position:0% assembly center he was a non-indian and 00:30:56.880 --> 00:31:00.200 align:start position:0% assembly center he was a non-indian and back<00:30:57.149> into<00:30:57.510> AI<00:30:57.929> also<00:30:58.260> we<00:30:58.830> have<00:30:59.159> a<00:30:59.429> cost<00:30:59.880> amount 00:31:00.200 --> 00:31:00.210 align:start position:0% back into AI also we have a cost amount 00:31:00.210 --> 00:31:02.870 align:start position:0% back into AI also we have a cost amount of<00:31:00.450> here<00:31:00.690> and<00:31:00.899> when<00:31:01.679> we<00:31:01.710> have<00:31:01.950> a<00:31:01.980> problem<00:31:02.549> here 00:31:02.870 --> 00:31:02.880 align:start position:0% of here and when we have a problem here 00:31:02.880 --> 00:31:07.220 align:start position:0% of here and when we have a problem here we<00:31:03.059> can<00:31:03.269> apply<00:31:04.940> the<00:31:05.940> traditional<00:31:06.230> energy 00:31:07.220 --> 00:31:07.230 align:start position:0% we can apply the traditional energy 00:31:07.230 --> 00:31:09.769 align:start position:0% we can apply the traditional energy consumption<00:31:07.620> issue<00:31:08.130> the<00:31:08.820> package<00:31:09.360> of<00:31:09.539> that 00:31:09.769 --> 00:31:09.779 align:start position:0% consumption issue the package of that 00:31:09.779 --> 00:31:14.240 align:start position:0% consumption issue the package of that into<00:31:10.590> this<00:31:11.519> model<00:31:12.029> and<00:31:12.240> we<00:31:12.299> had<00:31:13.110> just<00:31:13.980> apply 00:31:14.240 --> 00:31:14.250 align:start position:0% into this model and we had just apply 00:31:14.250 --> 00:31:16.690 align:start position:0% into this model and we had just apply laws<00:31:14.580> are<00:31:15.059> the<00:31:15.179> manifest<00:31:15.750> engineer 00:31:16.690 --> 00:31:16.700 align:start position:0% laws are the manifest engineer 00:31:16.700 --> 00:31:21.460 align:start position:0% laws are the manifest engineer and<00:31:16.879> we<00:31:17.179> get<00:31:17.389> of<00:31:18.580> Mulcair<00:31:19.580> some<00:31:19.789> Isis<00:31:20.470> Michael 00:31:21.460 --> 00:31:21.470 align:start position:0% and we get of Mulcair some Isis Michael 00:31:21.470 --> 00:31:26.560 align:start position:0% and we get of Mulcair some Isis Michael here<00:31:21.739> okay<00:31:22.840> so<00:31:24.070> let's<00:31:25.070> go<00:31:25.249> into<00:31:25.429> the<00:31:25.789> demo<00:31:26.210> part 00:31:26.560 --> 00:31:26.570 align:start position:0% here okay so let's go into the demo part 00:31:26.570 --> 00:31:28.930 align:start position:0% here okay so let's go into the demo part I<00:31:26.840> will<00:31:27.379> show<00:31:27.409> you<00:31:27.649> how<00:31:27.830> to<00:31:27.859> use<00:31:28.159> our<00:31:28.369> compiler 00:31:28.930 --> 00:31:28.940 align:start position:0% I will show you how to use our compiler 00:31:28.940 --> 00:31:32.590 align:start position:0% I will show you how to use our compiler to<00:31:29.809> compile<00:31:30.200> you<00:31:30.350> as<00:31:30.499> I<00:31:30.529> recall<00:31:30.830> 92<00:31:31.759> and<00:31:32.269> then<00:31:32.480> I 00:31:32.590 --> 00:31:32.600 align:start position:0% to compile you as I recall 92 and then I 00:31:32.600 --> 00:31:35.680 align:start position:0% to compile you as I recall 92 and then I are<00:31:32.779> finally<00:31:33.259> 482<00:31:34.100> that<00:31:34.549> you<00:31:34.639> Boston<00:31:34.850> I<00:31:35.179> seem 00:31:35.680 --> 00:31:35.690 align:start position:0% are finally 482 that you Boston I seem 00:31:35.690 --> 00:31:52.029 align:start position:0% are finally 482 that you Boston I seem for<00:31:35.929> Evo<00:31:36.350> parties<00:31:50.049> okay<00:31:51.049> so<00:31:51.109> first<00:31:51.590> of<00:31:51.710> all<00:31:51.889> you 00:31:52.029 --> 00:31:52.039 align:start position:0% for Evo parties okay so first of all you 00:31:52.039 --> 00:31:54.279 align:start position:0% for Evo parties okay so first of all you need<00:31:52.279> to<00:31:52.549> come<00:31:52.940> into<00:31:53.090> love<00:31:53.389> in<00:31:53.539> answer<00:31:53.929> to<00:31:53.960> the 00:31:54.279 --> 00:31:54.289 align:start position:0% need to come into love in answer to the 00:31:54.289 --> 00:32:03.269 align:start position:0% need to come into love in answer to the he<00:31:54.679> wasn't<00:31:54.980> has<00:31:55.100> hands<00:31:55.419> just<00:31:56.419> like<00:31:56.659> this<00:31:57.289> and 00:32:03.269 --> 00:32:03.279 align:start position:0% 00:32:03.279 --> 00:32:06.310 align:start position:0% we<00:32:04.279> have<00:32:04.309> these<00:32:04.850> muscles<00:32:05.480> you<00:32:05.629> can<00:32:05.809> keep<00:32:05.989> going 00:32:06.310 --> 00:32:06.320 align:start position:0% we have these muscles you can keep going 00:32:06.320 --> 00:32:12.489 align:start position:0% we have these muscles you can keep going as<00:32:06.470> he<00:32:09.700> attacks<00:32:10.700> the<00:32:11.059> soup<00:32:11.239> I<00:32:11.419> if<00:32:11.659> you<00:32:11.899> use<00:32:12.200> is 00:32:12.489 --> 00:32:12.499 align:start position:0% as he attacks the soup I if you use is 00:32:12.499 --> 00:32:15.430 align:start position:0% as he attacks the soup I if you use is metal<00:32:12.889> he<00:32:13.580> may<00:32:13.730> detect<00:32:14.149> a<00:32:14.450> one<00:32:14.840> hour<00:32:15.019> the 00:32:15.430 --> 00:32:15.440 align:start position:0% metal he may detect a one hour the 00:32:15.440 --> 00:32:20.529 align:start position:0% metal he may detect a one hour the audience<00:32:15.799> so<00:32:16.220> as<00:32:16.340> to<00:32:16.820> know<00:32:19.029> so<00:32:20.029> you<00:32:20.090> can<00:32:20.389> just 00:32:20.529 --> 00:32:20.539 align:start position:0% audience so as to know so you can just 00:32:20.539 --> 00:32:24.700 align:start position:0% audience so as to know so you can just go<00:32:20.749> yet<00:32:21.019> they<00:32:21.529> just<00:32:21.559> run<00:32:22.129> it<00:32:22.369> and<00:32:23.710> excuses 00:32:24.700 --> 00:32:24.710 align:start position:0% go yet they just run it and excuses 00:32:24.710 --> 00:32:29.139 align:start position:0% go yet they just run it and excuses comment<00:32:25.609> in<00:32:25.850> our<00:32:26.799> next<00:32:27.799> eyes<00:32:27.980> and<00:32:28.340> together 00:32:29.139 --> 00:32:29.149 align:start position:0% comment in our next eyes and together 00:32:29.149 --> 00:32:35.009 align:start position:0% comment in our next eyes and together I<00:32:29.679> go<00:32:30.679> so<00:32:30.950> I<00:32:30.980> see<00:32:31.609> I<00:32:31.639> think<00:32:31.730> I<00:32:32.149> can<00:32:32.450> do<00:32:32.629> that 00:32:35.009 --> 00:32:35.019 align:start position:0% 00:32:35.019 --> 00:32:38.340 align:start position:0% already 00:32:38.340 --> 00:32:38.350 align:start position:0% 00:32:38.350 --> 00:32:46.900 align:start position:0% so<00:32:40.270> it's<00:32:41.270> not<00:32:41.450> enough 00:32:46.900 --> 00:32:46.910 align:start position:0% 00:32:46.910 --> 00:32:49.550 align:start position:0% okay<00:32:47.910> I<00:32:48.090> know<00:32:48.300> this<00:32:48.600> best 00:32:49.550 --> 00:32:49.560 align:start position:0% okay I know this best 00:32:49.560 --> 00:32:52.150 align:start position:0% okay I know this best [Music] 00:32:52.150 --> 00:32:52.160 align:start position:0% [Music] 00:32:52.160 --> 00:32:56.560 align:start position:0% [Music] okay<00:32:52.760> now<00:32:53.740> I<00:32:54.740> run<00:32:55.190> the<00:32:56.030> mansion<00:32:56.270> of 00:32:56.560 --> 00:32:56.570 align:start position:0% okay now I run the mansion of 00:32:56.570 --> 00:33:01.590 align:start position:0% okay now I run the mansion of srl<00:32:57.550> demo<00:32:58.550> and<00:32:58.850> first<00:32:59.660> of<00:32:59.780> all<00:32:59.960> you<00:33:00.320> need<00:33:00.620> to 00:33:01.590 --> 00:33:01.600 align:start position:0% srl demo and first of all you need to 00:33:01.600 --> 00:33:07.210 align:start position:0% srl demo and first of all you need to create<00:33:02.600> a<00:33:02.630> comrade<00:33:03.410> and<00:33:05.710> we'll<00:33:06.710> many<00:33:06.950> endemic 00:33:07.210 --> 00:33:07.220 align:start position:0% create a comrade and we'll many endemic 00:33:07.220 --> 00:33:13.420 align:start position:0% create a comrade and we'll many endemic opiates 00:33:13.420 --> 00:33:13.430 align:start position:0% 00:33:13.430 --> 00:33:19.480 align:start position:0% Oh 00:33:19.480 --> 00:33:19.490 align:start position:0% 00:33:19.490 --> 00:33:23.840 align:start position:0% so<00:33:20.490> just<00:33:21.150> press<00:33:21.330> it<00:33:21.950> as<00:33:22.950> you<00:33:23.100> can<00:33:23.250> see<00:33:23.309> this<00:33:23.610> is 00:33:23.840 --> 00:33:23.850 align:start position:0% so just press it as you can see this is 00:33:23.850 --> 00:33:26.419 align:start position:0% so just press it as you can see this is just<00:33:24.419> 20<00:33:24.809> country<00:33:25.200> and<00:33:25.440> we<00:33:25.710> have<00:33:25.919> possibly 00:33:26.419 --> 00:33:26.429 align:start position:0% just 20 country and we have possibly 00:33:26.429 --> 00:33:29.120 align:start position:0% just 20 country and we have possibly without<00:33:27.150> pan<00:33:27.480> sets<00:33:27.750> and<00:33:28.260> we<00:33:28.380> have<00:33:28.590> event 00:33:29.120 --> 00:33:29.130 align:start position:0% without pan sets and we have event 00:33:29.130 --> 00:33:32.570 align:start position:0% without pan sets and we have event wealth<00:33:29.460> transfer<00:33:29.940> and<00:33:29.970> here<00:33:30.900> is<00:33:31.080> a<00:33:31.400> short<00:33:32.400> term 00:33:32.570 --> 00:33:32.580 align:start position:0% wealth transfer and here is a short term 00:33:32.580 --> 00:33:36.110 align:start position:0% wealth transfer and here is a short term you<00:33:32.789> can<00:33:32.970> sell<00:33:33.240> the<00:33:34.010> post<00:33:35.010> buy<00:33:35.280> and<00:33:35.669> sell<00:33:35.880> like 00:33:36.110 --> 00:33:36.120 align:start position:0% you can sell the post buy and sell like 00:33:36.120 --> 00:33:39.680 align:start position:0% you can sell the post buy and sell like utilize<00:33:36.690> basic<00:33:37.590> bounces<00:33:38.100> and<00:33:38.400> also<00:33:39.090> a<00:33:39.120> budget 00:33:39.680 --> 00:33:39.690 align:start position:0% utilize basic bounces and also a budget 00:33:39.690 --> 00:33:42.669 align:start position:0% utilize basic bounces and also a budget for<00:33:39.870> the<00:33:40.049> affairs<00:33:40.470> of<00:33:40.679> people<00:33:41.130> careers<00:33:42.090> and 00:33:42.669 --> 00:33:42.679 align:start position:0% for the affairs of people careers and 00:33:42.679 --> 00:33:46.760 align:start position:0% for the affairs of people careers and families<00:33:43.679> in<00:33:43.860> such<00:33:44.070> as<00:33:44.280> crunching<00:33:44.820> and<00:33:45.590> if<00:33:46.590> you 00:33:46.760 --> 00:33:46.770 align:start position:0% families in such as crunching and if you 00:33:46.770 --> 00:33:48.890 align:start position:0% families in such as crunching and if you want<00:33:46.980> to<00:33:47.130> add<00:33:47.340> the<00:33:47.700> setbacks<00:33:48.179> protesting<00:33:48.780> in 00:33:48.890 --> 00:33:48.900 align:start position:0% want to add the setbacks protesting in 00:33:48.900 --> 00:33:50.899 align:start position:0% want to add the setbacks protesting in the<00:33:48.990> just<00:33:49.230> include<00:33:49.830> library<00:33:50.370> and<00:33:50.580> you<00:33:50.730> see 00:33:50.899 --> 00:33:50.909 align:start position:0% the just include library and you see 00:33:50.909 --> 00:33:53.450 align:start position:0% the just include library and you see it's<00:33:51.059> a<00:33:51.210> lesser<00:33:51.450> that's<00:33:51.929> fine<00:33:52.169> but<00:33:53.100> for<00:33:53.309> the 00:33:53.450 --> 00:33:53.460 align:start position:0% it's a lesser that's fine but for the 00:33:53.460 --> 00:33:59.240 align:start position:0% it's a lesser that's fine but for the diverse<00:33:53.850> artists<00:33:54.360> recommend<00:33:58.039> when<00:33:59.039> you<00:33:59.130> use 00:33:59.240 --> 00:33:59.250 align:start position:0% diverse artists recommend when you use 00:33:59.250 --> 00:34:03.020 align:start position:0% diverse artists recommend when you use as<00:33:59.909> however<00:34:00.419> you<00:34:00.750> can<00:34:01.020> can<00:34:01.409> help<00:34:02.039> making<00:34:02.370> like 00:34:03.020 --> 00:34:03.030 align:start position:0% as however you can can help making like 00:34:03.030 --> 00:34:06.230 align:start position:0% as however you can can help making like this<00:34:03.299> and<00:34:04.140> no<00:34:04.530> worries<00:34:04.860> because<00:34:05.190> we<00:34:05.909> all<00:34:06.059> need 00:34:06.230 --> 00:34:06.240 align:start position:0% this and no worries because we all need 00:34:06.240 --> 00:34:45.850 align:start position:0% this and no worries because we all need the<00:34:06.539> compound<00:34:06.960> is<00:34:10.520> yeah 00:34:45.850 --> 00:34:45.860 align:start position:0% 00:34:45.860 --> 00:34:57.049 align:start position:0% [Applause] 00:34:57.049 --> 00:34:57.059 align:start position:0% 00:34:57.059 --> 00:34:59.930 align:start position:0% we'll<00:34:58.059> be<00:34:58.180> in<00:34:58.270> compilers<00:34:58.690> and<00:34:59.050> was<00:34:59.470> no 00:34:59.930 --> 00:34:59.940 align:start position:0% we'll be in compilers and was no 00:34:59.940 --> 00:35:01.140 align:start position:0% we'll be in compilers and was no accident 00:35:01.140 --> 00:35:01.150 align:start position:0% accident 00:35:01.150 --> 00:35:05.640 align:start position:0% accident we<00:35:01.900> were<00:35:01.960> so<00:35:02.170> many<00:35:02.290> cars<00:35:02.619> and<00:35:04.020> in<00:35:05.020> welcome<00:35:05.470> to 00:35:05.640 --> 00:35:05.650 align:start position:0% we were so many cars and in welcome to 00:35:05.650 --> 00:35:09.839 align:start position:0% we were so many cars and in welcome to was<00:35:06.369> final<00:35:07.030> one<00:35:07.300> is<00:35:07.540> love<00:35:08.069> one<00:35:09.069> hi<00:35:09.250> file<00:35:09.520> called 00:35:09.839 --> 00:35:09.849 align:start position:0% was final one is love one hi file called 00:35:09.849 --> 00:35:13.740 align:start position:0% was final one is love one hi file called cancer<00:35:10.329> that<00:35:10.510> was<00:35:10.660> a<00:35:10.720> novice<00:35:11.470> the<00:35:12.329> Ebro<00:35:13.329> a<00:35:13.359> file 00:35:13.740 --> 00:35:13.750 align:start position:0% cancer that was a novice the Ebro a file 00:35:13.750 --> 00:35:17.549 align:start position:0% cancer that was a novice the Ebro a file called<00:35:14.140> the<00:35:14.349> country<00:35:14.800> appointment<00:35:15.460> and<00:35:16.559> the 00:35:17.549 --> 00:35:17.559 align:start position:0% called the country appointment and the 00:35:17.559 --> 00:35:20.430 align:start position:0% called the country appointment and the vampire<00:35:18.250> you<00:35:18.549> want<00:35:18.760> to<00:35:18.880> deploy<00:35:19.089> light<00:35:19.480> into<00:35:19.990> a 00:35:20.430 --> 00:35:20.440 align:start position:0% vampire you want to deploy light into a 00:35:20.440 --> 00:35:23.599 align:start position:0% vampire you want to deploy light into a certain<00:35:20.890> he<00:35:21.339> was<00:35:21.490> a<00:35:21.520> personnel<00:35:22.030> was<00:35:22.540> new<00:35:22.780> just 00:35:23.599 --> 00:35:23.609 align:start position:0% certain he was a personnel was new just 00:35:23.609 --> 00:35:27.390 align:start position:0% certain he was a personnel was new just back<00:35:24.609> here<00:35:24.970> and<00:35:25.270> you<00:35:25.510> can<00:35:25.540> find<00:35:25.960> it<00:35:26.950> wasn't<00:35:27.130> as 00:35:27.390 --> 00:35:27.400 align:start position:0% back here and you can find it wasn't as 00:35:27.400 --> 00:35:30.140 align:start position:0% back here and you can find it wasn't as natural<00:35:27.940> and 00:35:30.140 --> 00:35:30.150 align:start position:0% natural and 00:35:30.150 --> 00:35:34.849 align:start position:0% natural and and<00:35:31.109> just<00:35:31.680> some<00:35:32.339> your<00:35:32.519> transaction<00:35:33.029> because<00:35:33.859> I 00:35:34.849 --> 00:35:34.859 align:start position:0% and just some your transaction because I 00:35:34.859 --> 00:35:38.569 align:start position:0% and just some your transaction because I think<00:35:35.700> this<00:35:36.319> anyway<00:35:37.319> to<00:35:37.380> city<00:35:37.829> or<00:35:38.009> a<00:35:38.039> remember 00:35:38.569 --> 00:35:38.579 align:start position:0% think this anyway to city or a remember 00:35:38.579 --> 00:35:43.460 align:start position:0% think this anyway to city or a remember there<00:35:38.789> and<00:35:41.180> because<00:35:42.180> you<00:35:42.359> need<00:35:42.630> to<00:35:42.779> pass<00:35:43.140> your 00:35:43.460 --> 00:35:43.470 align:start position:0% there and because you need to pass your 00:35:43.470 --> 00:35:46.640 align:start position:0% there and because you need to pass your your<00:35:43.920> your<00:35:44.220> all<00:35:44.519> wasn't<00:35:45.089> to<00:35:45.240> here<00:35:45.630> so<00:35:45.809> you<00:35:46.200> need 00:35:46.640 --> 00:35:46.650 align:start position:0% your your all wasn't to here so you need 00:35:46.650 --> 00:35:50.499 align:start position:0% your your all wasn't to here so you need to<00:35:46.769> enclose<00:35:47.220> this<00:35:47.579> finer<00:35:48.299> file<00:35:48.630> into<00:35:49.230> a<00:35:49.259> stream 00:35:50.499 --> 00:35:50.509 align:start position:0% to enclose this finer file into a stream 00:35:50.509 --> 00:35:58.430 align:start position:0% to enclose this finer file into a stream we<00:35:51.509> have<00:35:51.720> we<00:35:52.109> have<00:35:52.380> provide<00:35:56.839> the<00:35:57.839> coming<00:35:58.140> here 00:35:58.430 --> 00:35:58.440 align:start position:0% we have we have provide the coming here 00:35:58.440 --> 00:36:04.039 align:start position:0% we have we have provide the coming here just<00:35:58.890> okay<00:35:59.069> that<00:35:59.309> and<00:36:01.940> enter<00:36:02.940> okay<00:36:03.539> you've<00:36:03.690> got 00:36:04.039 --> 00:36:04.049 align:start position:0% just okay that and enter okay you've got 00:36:04.049 --> 00:36:07.190 align:start position:0% just okay that and enter okay you've got this<00:36:04.529> this<00:36:05.160> lots<00:36:05.970> of<00:36:06.089> string<00:36:06.480> this<00:36:06.690> is<00:36:06.990> your 00:36:07.190 --> 00:36:07.200 align:start position:0% this this lots of string this is your 00:36:07.200 --> 00:36:09.410 align:start position:0% this this lots of string this is your country<00:36:07.529> and<00:36:08.069> because<00:36:08.640> it<00:36:08.789> is<00:36:08.819> very<00:36:08.970> very 00:36:09.410 --> 00:36:09.420 align:start position:0% country and because it is very very 00:36:09.420 --> 00:36:13.390 align:start position:0% country and because it is very very large<00:36:09.930> so<00:36:10.200> I<00:36:10.259> need<00:36:10.499> to<00:36:10.680> just<00:36:11.569> just<00:36:12.569> scored<00:36:12.930> our 00:36:13.390 --> 00:36:13.400 align:start position:0% large so I need to just just scored our 00:36:13.400 --> 00:36:33.109 align:start position:0% large so I need to just just scored our my<00:36:14.400> coming<00:36:14.700> home 00:36:33.109 --> 00:36:33.119 align:start position:0% 00:36:33.119 --> 00:36:36.660 align:start position:0% okay 00:36:36.660 --> 00:36:36.670 align:start position:0% 00:36:36.670 --> 00:36:45.109 align:start position:0% and 00:36:45.109 --> 00:36:45.119 align:start position:0% 00:36:45.119 --> 00:37:03.420 align:start position:0% my<00:36:46.119> comments<00:36:46.480> will<00:36:46.690> ask<00:36:46.930> you<00:36:47.170> to<00:36:47.319> confirm<00:36:47.920> it 00:37:03.420 --> 00:37:03.430 align:start position:0% 00:37:03.430 --> 00:37:04.750 align:start position:0% right 00:37:04.750 --> 00:37:04.760 align:start position:0% right 00:37:04.760 --> 00:37:12.660 align:start position:0% right [Music] 00:37:12.660 --> 00:37:12.670 align:start position:0% 00:37:12.670 --> 00:37:17.480 align:start position:0% [Music] 00:37:17.480 --> 00:37:17.490 align:start position:0% 00:37:17.490 --> 00:37:20.180 align:start position:0% don't<00:37:18.060> worry<00:37:18.180> we<00:37:18.450> have<00:37:18.720> employee<00:37:19.500> of<00:37:19.800> amount 00:37:20.180 --> 00:37:20.190 align:start position:0% don't worry we have employee of amount 00:37:20.190 --> 00:37:23.089 align:start position:0% don't worry we have employee of amount of<00:37:20.280> things<00:37:20.490> before<00:37:20.970> words<00:37:21.330> also<00:37:21.650> if<00:37:22.650> you've 00:37:23.089 --> 00:37:23.099 align:start position:0% of things before words also if you've 00:37:23.099 --> 00:37:24.950 align:start position:0% of things before words also if you've got<00:37:23.280> the<00:37:23.430> arrows<00:37:23.700> of<00:37:23.849> where<00:37:24.000> you<00:37:24.119> can<00:37:24.300> retry<00:37:24.900> it 00:37:24.950 --> 00:37:24.960 align:start position:0% got the arrows of where you can retry it 00:37:24.960 --> 00:37:28.010 align:start position:0% got the arrows of where you can retry it simmer<00:37:25.859> 5<00:37:26.130> because<00:37:26.609> I<00:37:26.820> have<00:37:27.240> no<00:37:27.390> idear<00:37:27.810> when<00:37:27.990> I 00:37:28.010 --> 00:37:28.020 align:start position:0% simmer 5 because I have no idear when I 00:37:28.020 --> 00:37:32.240 align:start position:0% simmer 5 because I have no idear when I just<00:37:28.349> write<00:37:28.770> several<00:37:29.400> nine<00:37:30.980> there<00:37:31.980> will 00:37:32.240 --> 00:37:32.250 align:start position:0% just write several nine there will 00:37:32.250 --> 00:37:34.010 align:start position:0% just write several nine there will always<00:37:32.400> be<00:37:32.550> one<00:37:33.300> or<00:37:33.690> two 00:37:34.010 --> 00:37:34.020 align:start position:0% always be one or two 00:37:34.020 --> 00:37:39.890 align:start position:0% always be one or two well<00:37:34.320> success<00:37:34.760> this<00:37:35.760> we're<00:37:36.000> the<00:37:38.450> 40s<00:37:39.450> you<00:37:39.599> can 00:37:39.890 --> 00:37:39.900 align:start position:0% well success this we're the 40s you can 00:37:39.900 --> 00:37:42.050 align:start position:0% well success this we're the 40s you can get<00:37:40.109> your<00:37:40.320> mutter<00:37:40.589> here<00:37:41.010> and<00:37:41.250> listen<00:37:41.730> to<00:37:41.760> earn 00:37:42.050 --> 00:37:42.060 align:start position:0% get your mutter here and listen to earn 00:37:42.060 --> 00:37:47.000 align:start position:0% get your mutter here and listen to earn your<00:37:42.440> badges<00:37:43.440> and<00:37:44.010> you<00:37:44.820> can<00:37:45.030> find<00:37:45.630> a<00:37:45.810> Westco<00:37:46.619> if 00:37:47.000 --> 00:37:47.010 align:start position:0% your badges and you can find a Westco if 00:37:47.010 --> 00:37:49.190 align:start position:0% your badges and you can find a Westco if they<00:37:47.190> want<00:37:47.400> to<00:37:47.460> know<00:37:47.760> Weiss<00:37:48.150> the<00:37:48.510> use<00:37:48.780> I<00:37:49.020> love 00:37:49.190 --> 00:37:49.200 align:start position:0% they want to know Weiss the use I love 00:37:49.200 --> 00:37:50.870 align:start position:0% they want to know Weiss the use I love the<00:37:49.410> what<00:37:49.589> while<00:37:49.890> we<00:37:50.070> can<00:37:50.280> see<00:37:50.490> at<00:37:50.849> least 00:37:50.870 --> 00:37:50.880 align:start position:0% the what while we can see at least 00:37:50.880 --> 00:37:53.900 align:start position:0% the what while we can see at least happen<00:37:51.480> and<00:37:51.690> also<00:37:52.109> if<00:37:52.740> we<00:37:52.980> want<00:37:53.010> to<00:37:53.280> see<00:37:53.580> how 00:37:53.900 --> 00:37:53.910 align:start position:0% happen and also if we want to see how 00:37:53.910 --> 00:37:56.900 align:start position:0% happen and also if we want to see how our<00:37:54.290> storage<00:37:55.290> parables<00:37:56.010> even<00:37:56.400> kind<00:37:56.790> of 00:37:56.900 --> 00:37:56.910 align:start position:0% our storage parables even kind of 00:37:56.910 --> 00:37:59.270 align:start position:0% our storage parables even kind of storage<00:37:57.570> have<00:37:57.960> and<00:37:58.290> you<00:37:58.440> can<00:37:58.619> find<00:37:58.830> this<00:37:58.980> file 00:37:59.270 --> 00:37:59.280 align:start position:0% storage have and you can find this file 00:37:59.280 --> 00:38:07.760 align:start position:0% storage have and you can find this file and<00:38:00.089> it<00:38:00.810> was<00:38:01.790> bet<00:38:02.790> here<00:38:06.230> this<00:38:07.230> model<00:38:07.740> that 00:38:07.760 --> 00:38:07.770 align:start position:0% and it was bet here this model that 00:38:07.770 --> 00:38:10.790 align:start position:0% and it was bet here this model that shows<00:38:08.160> our<00:38:08.430> metamath<00:38:09.000> to<00:38:09.300> connect<00:38:09.690> our<00:38:09.990> wasn't 00:38:10.790 --> 00:38:10.800 align:start position:0% shows our metamath to connect our wasn't 00:38:10.800 --> 00:38:22.400 align:start position:0% shows our metamath to connect our wasn't has<00:38:10.950> met<00:38:11.190> and<00:38:12.410> just<00:38:13.410> change<00:38:13.980> to<00:38:14.070> occur<00:38:17.330> here<00:38:21.410> is 00:38:22.400 --> 00:38:22.410 align:start position:0% has met and just change to occur here is 00:38:22.410 --> 00:38:27.910 align:start position:0% has met and just change to occur here is your<00:38:22.680> focus<00:38:23.070> now<00:38:23.430> you<00:38:23.760> can't<00:38:24.030> get<00:38:24.270> pellets 00:38:27.910 --> 00:38:27.920 align:start position:0% 00:38:27.920 --> 00:38:31.460 align:start position:0% vote<00:38:28.920> and<00:38:29.450> you<00:38:30.450> will<00:38:30.600> get<00:38:30.810> you<00:38:30.930> a<00:38:30.960> balance<00:38:31.320> in 00:38:31.460 --> 00:38:31.470 align:start position:0% vote and you will get you a balance in 00:38:31.470 --> 00:38:34.610 align:start position:0% vote and you will get you a balance in here<00:38:31.680> and<00:38:31.950> you<00:38:32.340> can<00:38:32.520> transfer<00:38:33.120> your<00:38:33.660> your<00:38:34.380> bath 00:38:34.610 --> 00:38:34.620 align:start position:0% here and you can transfer your your bath 00:38:34.620 --> 00:38:46.430 align:start position:0% here and you can transfer your your bath and<00:38:35.100> a<00:38:35.940> hot<00:38:36.210> dog<00:38:36.480> and<00:38:36.750> just<00:38:36.990> by 00:38:46.430 --> 00:38:46.440 align:start position:0% 00:38:46.440 --> 00:38:51.960 align:start position:0% [Music] 00:38:51.960 --> 00:38:51.970 align:start position:0% 00:38:51.970 --> 00:39:01.710 align:start position:0% and<00:38:52.970> any<00:38:53.570> monitor 00:39:01.710 --> 00:39:01.720 align:start position:0% 00:39:01.720 --> 00:39:10.370 align:start position:0% [Music] 00:39:10.370 --> 00:39:10.380 align:start position:0% 00:39:10.380 --> 00:39:26.339 align:start position:0% but<00:39:11.380> you<00:39:11.470> need<00:39:11.619> to<00:39:11.739> see<00:39:12.009> your<00:39:13.289> semantics 00:39:26.339 --> 00:39:26.349 align:start position:0% 00:39:26.349 --> 00:39:28.790 align:start position:0% all<00:39:27.349> right 00:39:28.790 --> 00:39:28.800 align:start position:0% all right 00:39:28.800 --> 00:39:31.160 align:start position:0% all right you<00:39:29.670> know<00:39:29.730> I<00:39:29.820> think<00:39:30.120> our<00:39:30.300> time<00:39:30.480> is<00:39:30.540> optional<00:39:31.050> I 00:39:31.160 --> 00:39:31.170 align:start position:0% you know I think our time is optional I 00:39:31.170 --> 00:39:34.660 align:start position:0% you know I think our time is optional I don't<00:39:31.620> even 00:39:34.660 --> 00:39:34.670 align:start position:0% 00:39:34.670 --> 00:39:52.620 align:start position:0% anyone<00:39:35.510> there's<00:39:36.580> a<00:39:39.040> kind<00:39:40.040> of<00:39:41.890> second<00:39:42.890> sight 00:39:52.620 --> 00:39:52.630 align:start position:0% 00:39:52.630 --> 00:39:58.929 align:start position:0% [Applause]