WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:01:00.049 align:start position:0% [Applause] 00:01:00.049 --> 00:01:00.059 align:start position:0% 00:01:00.059 --> 00:01:16.080 align:start position:0% and<00:01:01.350> has<00:01:02.350> a<00:01:02.379> copy<00:01:02.800> of<00:01:02.920> the<00:01:03.100> slides<00:01:12.630> and<00:01:14.729> is<00:01:15.729> all 00:01:16.080 --> 00:01:16.090 align:start position:0% and has a copy of the slides and is all 00:01:16.090 --> 00:01:19.830 align:start position:0% and has a copy of the slides and is all the<00:01:16.270> codes<00:01:16.479> that<00:01:16.630> will<00:01:16.750> be<00:01:16.869> raining<00:01:17.049> today<00:01:18.840> if 00:01:19.830 --> 00:01:19.840 align:start position:0% the codes that will be raining today if 00:01:19.840 --> 00:01:22.890 align:start position:0% the codes that will be raining today if you<00:01:19.930> watch<00:01:20.110> all<00:01:20.439> along<00:01:20.860> and<00:01:21.150> you<00:01:22.150> can<00:01:22.479> start 00:01:22.890 --> 00:01:22.900 align:start position:0% you watch all along and you can start 00:01:22.900 --> 00:01:32.830 align:start position:0% you watch all along and you can start from<00:01:22.990> the<00:01:23.670> initial<00:01:24.670> version 00:01:32.830 --> 00:01:32.840 align:start position:0% 00:01:32.840 --> 00:01:34.810 align:start position:0% where<00:01:33.109> we've<00:01:33.679> written<00:01:33.920> the<00:01:34.130> entire<00:01:34.219> reach 00:01:34.810 --> 00:01:34.820 align:start position:0% where we've written the entire reach 00:01:34.820 --> 00:01:45.990 align:start position:0% where we've written the entire reach part<00:01:35.119> of<00:01:35.210> the<00:01:35.299> program<00:01:35.630> and<00:01:36.140> it<00:01:36.380> will<00:01:36.530> switch 00:01:45.990 --> 00:01:46.000 align:start position:0% 00:01:46.000 --> 00:01:49.330 align:start position:0% and<00:01:47.000> then<00:01:47.600> the<00:01:47.689> final<00:01:48.049> code<00:01:48.259> will<00:01:48.560> be<00:01:48.590> the<00:01:48.950> I 00:01:49.330 --> 00:01:49.340 align:start position:0% and then the final code will be the I 00:01:49.340 --> 00:01:51.069 align:start position:0% and then the final code will be the I don't<00:01:49.700> want<00:01:49.729> this<00:01:49.939> our<00:01:50.119> target<00:01:50.719> for<00:01:50.840> the<00:01:50.959> end 00:01:51.069 --> 00:01:51.079 align:start position:0% don't want this our target for the end 00:01:51.079 --> 00:01:52.959 align:start position:0% don't want this our target for the end of<00:01:51.140> the<00:01:51.259> day<00:01:51.409> so<00:01:52.219> if<00:01:52.280> you<00:01:52.369> wanted<00:01:52.700> to<00:01:52.819> run<00:01:52.909> a 00:01:52.959 --> 00:01:52.969 align:start position:0% of the day so if you wanted to run a 00:01:52.969 --> 00:01:56.709 align:start position:0% of the day so if you wanted to run a business<00:01:53.179> how<00:01:54.049> to<00:01:54.409> use<00:01:54.770> the<00:01:54.979> English<00:01:55.719> right 00:01:56.709 --> 00:01:56.719 align:start position:0% business how to use the English right 00:01:56.719 --> 00:02:00.429 align:start position:0% business how to use the English right now<00:01:57.459> we<00:01:58.459> have<00:01:58.729> dr.<00:01:59.119> and<00:01:59.270> dr.<00:01:59.359> compose<00:01:59.990> result 00:02:00.429 --> 00:02:00.439 align:start position:0% now we have dr. and dr. compose result 00:02:00.439 --> 00:02:05.880 align:start position:0% now we have dr. and dr. compose result and<00:02:00.979> of<00:02:01.069> course<00:02:01.310> how<00:02:01.459> about<00:02:01.640> music<00:02:02.000> music<00:02:02.500> so 00:02:05.880 --> 00:02:05.890 align:start position:0% 00:02:05.890 --> 00:02:09.550 align:start position:0% you<00:02:06.890> want<00:02:07.099> to<00:02:07.220> go<00:02:07.340> to<00:02:07.399> this<00:02:07.610> site<00:02:07.899> and<00:02:08.899> then 00:02:09.550 --> 00:02:09.560 align:start position:0% you want to go to this site and then 00:02:09.560 --> 00:02:11.650 align:start position:0% you want to go to this site and then from<00:02:09.950> the<00:02:10.130> base<00:02:10.280> directory<00:02:10.459> villain<00:02:11.269> Tuesday 00:02:11.650 --> 00:02:11.660 align:start position:0% from the base directory villain Tuesday 00:02:11.660 --> 00:02:15.250 align:start position:0% from the base directory villain Tuesday final<00:02:12.049> write<00:02:12.709> in<00:02:13.220> Greenville<00:02:14.209> run<00:02:14.480> then<00:02:15.079> that 00:02:15.250 --> 00:02:15.260 align:start position:0% final write in Greenville run then that 00:02:15.260 --> 00:02:17.400 align:start position:0% final write in Greenville run then that will<00:02:15.440> make<00:02:15.829> sure<00:02:16.220> that<00:02:16.250> you<00:02:16.430> have<00:02:16.670> all<00:02:16.910> these 00:02:17.400 --> 00:02:17.410 align:start position:0% will make sure that you have all these 00:02:17.410 --> 00:02:20.350 align:start position:0% will make sure that you have all these velvet<00:02:18.410> if<00:02:18.860> you<00:02:18.980> want<00:02:19.129> to<00:02:19.220> all<00:02:19.370> along<00:02:19.670> if<00:02:20.269> you 00:02:20.350 --> 00:02:20.360 align:start position:0% velvet if you want to all along if you 00:02:20.360 --> 00:02:21.819 align:start position:0% velvet if you want to all along if you don't<00:02:20.510> want<00:02:20.629> to<00:02:20.690> follow<00:02:20.840> a<00:02:20.989> just<00:02:21.620> do<00:02:21.709> this 00:02:21.819 --> 00:02:21.829 align:start position:0% don't want to follow a just do this 00:02:21.829 --> 00:02:24.839 align:start position:0% don't want to follow a just do this later<00:02:22.040> and<00:02:22.519> there<00:02:22.760> will<00:02:22.940> be<00:02:23.019> value<00:02:24.019> and 00:02:24.839 --> 00:02:24.849 align:start position:0% later and there will be value and 00:02:24.849 --> 00:02:33.170 align:start position:0% later and there will be value and experiencing<00:02:25.849> the<00:02:25.940> rest<00:02:26.060> of<00:02:26.180> the<00:02:26.239> show 00:02:33.170 --> 00:02:33.180 align:start position:0% 00:02:33.180 --> 00:02:37.140 align:start position:0% our<00:02:34.180> team<00:02:34.420> is<00:02:35.430> because<00:02:36.430> we<00:02:36.580> were<00:02:36.700> able<00:02:36.850> to 00:02:37.140 --> 00:02:37.150 align:start position:0% our team is because we were able to 00:02:37.150 --> 00:02:41.360 align:start position:0% our team is because we were able to attend<00:02:37.560> and<00:02:38.560> then<00:02:38.680> maintain<00:02:39.070> McCarthy<00:02:40.020> so 00:02:41.360 --> 00:02:41.370 align:start position:0% attend and then maintain McCarthy so 00:02:41.370 --> 00:02:43.770 align:start position:0% attend and then maintain McCarthy so Christmas<00:02:42.370> Carol<00:02:42.910> entrepreneur's<00:02:43.300> had<00:02:43.600> a<00:02:43.630> lot 00:02:43.770 --> 00:02:43.780 align:start position:0% Christmas Carol entrepreneur's had a lot 00:02:43.780 --> 00:02:45.990 align:start position:0% Christmas Carol entrepreneur's had a lot of<00:02:43.810> experience<00:02:44.470> in<00:02:44.710> the<00:02:44.980> space<00:02:45.220> and<00:02:45.550> my 00:02:45.990 --> 00:02:46.000 align:start position:0% of experience in the space and my 00:02:46.000 --> 00:02:47.790 align:start position:0% of experience in the space and my background<00:02:46.270> is<00:02:46.600> that<00:02:46.660> I<00:02:46.990> am<00:02:47.350> a<00:02:47.470> research 00:02:47.790 --> 00:02:47.800 align:start position:0% background is that I am a research 00:02:47.800 --> 00:02:49.260 align:start position:0% background is that I am a research professor<00:02:47.980> at<00:02:48.700> the<00:02:48.760> University<00:02:49.209> of 00:02:49.260 --> 00:02:49.270 align:start position:0% professor at the University of 00:02:49.270 --> 00:02:51.390 align:start position:0% professor at the University of Massachusetts<00:02:49.450> well<00:02:50.290> and<00:02:50.709> I'm<00:02:50.950> also<00:02:51.100> one<00:02:51.370> of 00:02:51.390 --> 00:02:51.400 align:start position:0% Massachusetts well and I'm also one of 00:02:51.400 --> 00:02:53.520 align:start position:0% Massachusetts well and I'm also one of the<00:02:51.520> developers<00:02:51.970> of<00:02:52.030> the<00:02:52.420> record<00:02:53.200> program 00:02:53.520 --> 00:02:53.530 align:start position:0% the developers of the record program 00:02:53.530 --> 00:02:55.980 align:start position:0% the developers of the record program language<00:02:53.920> so<00:02:54.550> a<00:02:54.580> racket<00:02:55.090> is<00:02:55.270> a<00:02:55.450> list<00:02:55.660> based 00:02:55.980 --> 00:02:55.990 align:start position:0% language so a racket is a list based 00:02:55.990 --> 00:02:58.500 align:start position:0% language so a racket is a list based language<00:02:56.380> that's<00:02:56.620> very<00:02:56.740> popular<00:02:57.400> as<00:02:58.120> far<00:02:58.390> as 00:02:58.500 --> 00:02:58.510 align:start position:0% language that's very popular as far as 00:02:58.510 --> 00:03:01.470 align:start position:0% language that's very popular as far as list<00:02:58.990> based<00:02:59.170> programming<00:02:59.530> languages<00:02:59.980> go<00:03:00.480> it's 00:03:01.470 --> 00:03:01.480 align:start position:0% list based programming languages go it's 00:03:01.480 --> 00:03:03.990 align:start position:0% list based programming languages go it's commonly<00:03:01.780> used<00:03:01.870> at<00:03:02.200> a<00:03:02.230> lot<00:03:02.410> of<00:03:03.000> colleges 00:03:03.990 --> 00:03:04.000 align:start position:0% commonly used at a lot of colleges 00:03:04.000 --> 00:03:06.810 align:start position:0% commonly used at a lot of colleges universities<00:03:04.330> and<00:03:05.020> my<00:03:05.739> research<00:03:06.160> has<00:03:06.340> mostly 00:03:06.810 --> 00:03:06.820 align:start position:0% universities and my research has mostly 00:03:06.820 --> 00:03:09.420 align:start position:0% universities and my research has mostly focused<00:03:07.270> on<00:03:07.540> doing<00:03:08.440> verification<00:03:09.250> of 00:03:09.420 --> 00:03:09.430 align:start position:0% focused on doing verification of 00:03:09.430 --> 00:03:12.280 align:start position:0% focused on doing verification of programs<00:03:09.880> for<00:03:10.120> calls<00:03:10.420> and<00:03:10.720> there 00:03:12.280 --> 00:03:12.290 align:start position:0% programs for calls and there 00:03:12.290 --> 00:03:15.080 align:start position:0% programs for calls and there so<00:03:13.290> the<00:03:13.620> reader<00:03:13.830> product<00:03:14.069> the<00:03:14.519> reader<00:03:14.700> project 00:03:15.080 --> 00:03:15.090 align:start position:0% so the reader product the reader project 00:03:15.090 --> 00:03:16.940 align:start position:0% so the reader product the reader project really<00:03:15.269> represented<00:03:15.810> the<00:03:15.840> culmination<00:03:16.319> of<00:03:16.500> my 00:03:16.940 --> 00:03:16.950 align:start position:0% really represented the culmination of my 00:03:16.950 --> 00:03:20.240 align:start position:0% really represented the culmination of my research<00:03:17.540> now<00:03:18.540> our<00:03:19.080> goal<00:03:19.319> as<00:03:19.650> an<00:03:19.739> organization 00:03:20.240 --> 00:03:20.250 align:start position:0% research now our goal as an organization 00:03:20.250 --> 00:03:21.979 align:start position:0% research now our goal as an organization is<00:03:20.370> to<00:03:20.489> try<00:03:20.640> to<00:03:20.670> dramatically<00:03:21.300> lower<00:03:21.360> the 00:03:21.979 --> 00:03:21.989 align:start position:0% is to try to dramatically lower the 00:03:21.989 --> 00:03:24.229 align:start position:0% is to try to dramatically lower the barrier<00:03:22.290> to<00:03:22.470> entry<00:03:22.500> to<00:03:22.739> watch<00:03:23.030> so<00:03:24.030> we<00:03:24.120> think 00:03:24.229 --> 00:03:24.239 align:start position:0% barrier to entry to watch so we think 00:03:24.239 --> 00:03:25.550 align:start position:0% barrier to entry to watch so we think that<00:03:24.360> there's<00:03:24.599> a<00:03:24.690> huge<00:03:24.930> amount<00:03:25.110> of<00:03:25.170> potential 00:03:25.550 --> 00:03:25.560 align:start position:0% that there's a huge amount of potential 00:03:25.560 --> 00:03:27.979 align:start position:0% that there's a huge amount of potential in<00:03:25.980> the<00:03:26.400> space<00:03:26.670> but<00:03:27.180> right<00:03:27.330> now<00:03:27.510> it's<00:03:27.750> just<00:03:27.810> too 00:03:27.979 --> 00:03:27.989 align:start position:0% in the space but right now it's just too 00:03:27.989 --> 00:03:31.460 align:start position:0% in the space but right now it's just too complicated<00:03:28.500> to<00:03:29.340> build<00:03:29.879> real<00:03:30.299> apps<00:03:30.510> and<00:03:31.170> our 00:03:31.460 --> 00:03:31.470 align:start position:0% complicated to build real apps and our 00:03:31.470 --> 00:03:35.809 align:start position:0% complicated to build real apps and our goal<00:03:31.739> is<00:03:33.379> by<00:03:34.379> building<00:03:34.560> something<00:03:34.950> here<00:03:35.310> oh<00:03:35.640> no 00:03:35.809 --> 00:03:35.819 align:start position:0% goal is by building something here oh no 00:03:35.819 --> 00:03:40.400 align:start position:0% goal is by building something here oh no that's<00:03:36.120> 40<00:03:36.420> miles<00:03:36.980> now<00:03:37.980> its<00:03:38.700> pipeline<00:03:39.420> is<00:03:40.110> that 00:03:40.400 --> 00:03:40.410 align:start position:0% that's 40 miles now its pipeline is that 00:03:40.410 --> 00:03:43.369 align:start position:0% that's 40 miles now its pipeline is that we<00:03:41.340> want<00:03:41.519> to<00:03:41.549> solve<00:03:41.730> three<00:03:42.030> problems<00:03:42.230> we<00:03:43.230> want 00:03:43.369 --> 00:03:43.379 align:start position:0% we want to solve three problems we want 00:03:43.379 --> 00:03:45.140 align:start position:0% we want to solve three problems we want to<00:03:43.530> abstract<00:03:43.980> over<00:03:44.519> the<00:03:44.640> decentralisation 00:03:45.140 --> 00:03:45.150 align:start position:0% to abstract over the decentralisation 00:03:45.150 --> 00:03:46.880 align:start position:0% to abstract over the decentralisation important<00:03:46.019> right<00:03:46.620> now 00:03:46.880 --> 00:03:46.890 align:start position:0% important right now 00:03:46.890 --> 00:03:49.190 align:start position:0% important right now here<00:03:47.730> it<00:03:47.819> is<00:03:47.940> extremely<00:03:48.599> productive<00:03:48.870> is 00:03:49.190 --> 00:03:49.200 align:start position:0% here it is extremely productive is 00:03:49.200 --> 00:03:51.080 align:start position:0% here it is extremely productive is probably<00:03:49.470> there<00:03:50.370> are<00:03:50.400> many<00:03:50.610> people<00:03:50.880> who 00:03:51.080 --> 00:03:51.090 align:start position:0% probably there are many people who 00:03:51.090 --> 00:03:52.190 align:start position:0% probably there are many people who believe<00:03:51.360> that<00:03:51.390> there's<00:03:51.660> problems<00:03:51.959> with 00:03:52.190 --> 00:03:52.200 align:start position:0% believe that there's problems with 00:03:52.200 --> 00:03:55.580 align:start position:0% believe that there's problems with aetherium<00:03:52.860> and<00:03:53.160> other<00:03:53.750> and<00:03:54.750> other<00:03:54.810> platforms 00:03:55.580 --> 00:03:55.590 align:start position:0% aetherium and other and other platforms 00:03:55.590 --> 00:03:58.569 align:start position:0% aetherium and other and other platforms but<00:03:56.069> it's<00:03:56.250> too<00:03:56.400> risky<00:03:56.430> to<00:03:56.849> invest<00:03:57.260> their<00:03:58.260> time 00:03:58.569 --> 00:03:58.579 align:start position:0% but it's too risky to invest their time 00:03:58.579 --> 00:04:01.250 align:start position:0% but it's too risky to invest their time if<00:03:59.579> you<00:03:59.730> rate<00:03:59.879> your<00:04:00.000> product<00:04:00.450> and<00:04:00.540> reach<00:04:00.870> and 00:04:01.250 --> 00:04:01.260 align:start position:0% if you rate your product and reach and 00:04:01.260 --> 00:04:03.530 align:start position:0% if you rate your product and reach and you<00:04:01.410> will<00:04:01.530> be<00:04:01.650> able<00:04:01.739> to<00:04:01.890> compile<00:04:02.280> to<00:04:02.540> different 00:04:03.530 --> 00:04:03.540 align:start position:0% you will be able to compile to different 00:04:03.540 --> 00:04:06.890 align:start position:0% you will be able to compile to different platforms<00:04:03.690> we<00:04:04.200> are<00:04:04.860> trying<00:04:05.250> to<00:04:05.720> we're<00:04:06.720> trying 00:04:06.890 --> 00:04:06.900 align:start position:0% platforms we are trying to we're trying 00:04:06.900 --> 00:04:08.509 align:start position:0% platforms we are trying to we're trying to<00:04:06.959> live<00:04:07.110> up<00:04:07.230> to<00:04:07.260> the<00:04:07.470> rate<00:04:07.680> was<00:04:07.890> running<00:04:08.370> many 00:04:08.509 --> 00:04:08.519 align:start position:0% to live up to the rate was running many 00:04:08.519 --> 00:04:10.640 align:start position:0% to live up to the rate was running many business<00:04:08.879> the<00:04:09.780> next<00:04:09.900> thing<00:04:10.110> we<00:04:10.260> want<00:04:10.290> to<00:04:10.470> solve 00:04:10.640 --> 00:04:10.650 align:start position:0% business the next thing we want to solve 00:04:10.650 --> 00:04:13.089 align:start position:0% business the next thing we want to solve is<00:04:10.920> that<00:04:11.280> we<00:04:11.640> want<00:04:11.819> to<00:04:11.879> make<00:04:12.060> sure<00:04:12.090> that<00:04:12.540> the 00:04:13.089 --> 00:04:13.099 align:start position:0% is that we want to make sure that the 00:04:13.099 --> 00:04:15.650 align:start position:0% is that we want to make sure that the that<00:04:14.099> the<00:04:14.640> depth<00:04:14.849> that<00:04:14.970> people<00:04:15.299> rank<00:04:15.510> are 00:04:15.650 --> 00:04:15.660 align:start position:0% that the depth that people rank are 00:04:15.660 --> 00:04:16.490 align:start position:0% that the depth that people rank are trustworthy 00:04:16.490 --> 00:04:16.500 align:start position:0% trustworthy 00:04:16.500 --> 00:04:18.890 align:start position:0% trustworthy so<00:04:17.250> a<00:04:17.639> major<00:04:18.090> important<00:04:18.570> what<00:04:18.690> we'll<00:04:18.840> be 00:04:18.890 --> 00:04:18.900 align:start position:0% so a major important what we'll be 00:04:18.900 --> 00:04:21.470 align:start position:0% so a major important what we'll be talking<00:04:19.019> about<00:04:19.229> later<00:04:19.350> is<00:04:20.010> the<00:04:20.160> way<00:04:20.280> that 00:04:21.470 --> 00:04:21.480 align:start position:0% talking about later is the way that 00:04:21.480 --> 00:04:24.530 align:start position:0% talking about later is the way that is<00:04:21.510> integral<00:04:22.050> to<00:04:22.230> the<00:04:22.920> operation<00:04:23.430> of<00:04:23.550> compiler 00:04:24.530 --> 00:04:24.540 align:start position:0% is integral to the operation of compiler 00:04:24.540 --> 00:04:28.210 align:start position:0% is integral to the operation of compiler and<00:04:24.780> the<00:04:24.870> way<00:04:25.020> that<00:04:25.260> we've<00:04:25.410> progressed 00:04:28.210 --> 00:04:28.220 align:start position:0% 00:04:28.220 --> 00:04:32.150 align:start position:0% finally<00:04:30.020> part<00:04:31.020> of<00:04:31.110> being<00:04:31.290> trustworthy<00:04:31.620> is 00:04:32.150 --> 00:04:32.160 align:start position:0% finally part of being trustworthy is 00:04:32.160 --> 00:04:33.680 align:start position:0% finally part of being trustworthy is ensuring<00:04:32.760> that<00:04:32.820> there<00:04:33.120> is<00:04:33.240> consistency 00:04:33.680 --> 00:04:33.690 align:start position:0% ensuring that there is consistency 00:04:33.690 --> 00:04:36.230 align:start position:0% ensuring that there is consistency between<00:04:34.590> the<00:04:34.890> expectations<00:04:35.190> of<00:04:35.670> contracts 00:04:36.230 --> 00:04:36.240 align:start position:0% between the expectations of contracts 00:04:36.240 --> 00:04:39.350 align:start position:0% between the expectations of contracts and<00:04:36.410> expectations<00:04:37.410> of<00:04:37.560> compliance<00:04:37.980> and<00:04:38.370> it 00:04:39.350 --> 00:04:39.360 align:start position:0% and expectations of compliance and it 00:04:39.360 --> 00:04:41.330 align:start position:0% and expectations of compliance and it needs<00:04:39.690> to<00:04:39.780> realize<00:04:40.260> that<00:04:40.500> in<00:04:40.740> the<00:04:41.190> recent 00:04:41.330 --> 00:04:41.340 align:start position:0% needs to realize that in the recent 00:04:41.340 --> 00:04:43.220 align:start position:0% needs to realize that in the recent languages<00:04:41.880> that<00:04:42.120> it<00:04:42.300> is<00:04:42.420> not<00:04:42.720> a<00:04:42.960> smart 00:04:43.220 --> 00:04:43.230 align:start position:0% languages that it is not a smart 00:04:43.230 --> 00:04:46.130 align:start position:0% languages that it is not a smart contract<00:04:43.500> English<00:04:44.040> is<00:04:45.000> a<00:04:45.150> bounty<00:04:45.630> which<00:04:45.810> we're 00:04:46.130 --> 00:04:46.140 align:start position:0% contract English is a bounty which we're 00:04:46.140 --> 00:04:47.780 align:start position:0% contract English is a bounty which we're going<00:04:46.230> to<00:04:46.290> break<00:04:46.530> their<00:04:46.710> program<00:04:47.070> in<00:04:47.190> this<00:04:47.550> one 00:04:47.780 --> 00:04:47.790 align:start position:0% going to break their program in this one 00:04:47.790 --> 00:04:53.410 align:start position:0% going to break their program in this one because<00:04:48.120> you<00:04:48.240> get<00:04:48.570> the<00:04:48.840> clients<00:04:49.470> that<00:04:49.950> will 00:04:53.410 --> 00:04:53.420 align:start position:0% 00:04:53.420 --> 00:04:57.200 align:start position:0% and<00:04:54.420> there's<00:04:54.600> a<00:04:54.690> guarantee<00:04:55.140> the<00:04:55.380> verities<00:04:56.210> now 00:04:57.200 --> 00:04:57.210 align:start position:0% and there's a guarantee the verities now 00:04:57.210 --> 00:04:58.490 align:start position:0% and there's a guarantee the verities now there<00:04:57.390> are<00:04:57.450> some<00:04:57.540> interesting<00:04:57.870> techniques 00:04:58.490 --> 00:04:58.500 align:start position:0% there are some interesting techniques 00:04:58.500 --> 00:05:00.980 align:start position:0% there are some interesting techniques that<00:04:59.250> we<00:04:59.370> use<00:04:59.580> design<00:05:00.150> and<00:05:00.660> I'll<00:05:00.780> talk<00:05:00.960> a 00:05:00.980 --> 00:05:00.990 align:start position:0% that we use design and I'll talk a 00:05:00.990 --> 00:05:02.810 align:start position:0% that we use design and I'll talk a little<00:05:01.170> bit<00:05:01.530> about<00:05:01.560> that<00:05:01.860> before<00:05:02.010> we<00:05:02.250> focus<00:05:02.670> on 00:05:02.810 --> 00:05:02.820 align:start position:0% little bit about that before we focus on 00:05:02.820 --> 00:05:09.680 align:start position:0% little bit about that before we focus on trade<00:05:06.530> now<00:05:07.530> one<00:05:08.190> of<00:05:08.220> the<00:05:08.340> ways<00:05:08.460> that<00:05:08.490> we<00:05:08.940> get 00:05:09.680 --> 00:05:09.690 align:start position:0% trade now one of the ways that we get 00:05:09.690 --> 00:05:12.110 align:start position:0% trade now one of the ways that we get the<00:05:09.960> abstraction<00:05:10.620> of<00:05:10.830> being<00:05:11.640> able<00:05:11.700> to<00:05:11.790> provide 00:05:12.110 --> 00:05:12.120 align:start position:0% the abstraction of being able to provide 00:05:12.120 --> 00:05:14.060 align:start position:0% the abstraction of being able to provide to<00:05:12.390> go<00:05:12.570> to<00:05:12.630> many<00:05:12.990> defensive<00:05:13.470> centralisation 00:05:14.060 --> 00:05:14.070 align:start position:0% to go to many defensive centralisation 00:05:14.070 --> 00:05:16.540 align:start position:0% to go to many defensive centralisation platforms<00:05:14.520> is<00:05:15.180> that<00:05:15.390> we<00:05:15.480> have<00:05:15.690> a<00:05:15.930> very 00:05:16.540 --> 00:05:16.550 align:start position:0% platforms is that we have a very 00:05:16.550 --> 00:05:19.280 align:start position:0% platforms is that we have a very straightforward<00:05:17.550> constraint<00:05:18.450> model<00:05:18.900> of<00:05:19.050> what 00:05:19.280 --> 00:05:19.290 align:start position:0% straightforward constraint model of what 00:05:19.290 --> 00:05:21.950 align:start position:0% straightforward constraint model of what working<00:05:19.620> provides<00:05:20.130> all<00:05:20.940> right<00:05:21.120> is<00:05:21.540> that<00:05:21.570> we're 00:05:21.950 --> 00:05:21.960 align:start position:0% working provides all right is that we're 00:05:21.960 --> 00:05:24.940 align:start position:0% working provides all right is that we're thinking<00:05:22.110> of<00:05:22.350> the<00:05:22.500> bunting<00:05:22.830> as<00:05:23.100> providing 00:05:24.940 --> 00:05:24.950 align:start position:0% thinking of the bunting as providing 00:05:24.950 --> 00:05:30.330 align:start position:0% thinking of the bunting as providing common<00:05:25.950> knowledge<00:05:26.300> about<00:05:27.300> a<00:05:27.740> monotonically 00:05:30.330 --> 00:05:30.340 align:start position:0% common knowledge about a monotonically 00:05:30.340 --> 00:05:35.670 align:start position:0% common knowledge about a monotonically and<00:05:31.090> those<00:05:32.460> those<00:05:33.540> attitudes<00:05:34.540> might<00:05:34.990> say<00:05:35.170> they 00:05:35.670 --> 00:05:35.680 align:start position:0% and those those attitudes might say they 00:05:35.680 --> 00:05:37.770 align:start position:0% and those those attitudes might say they really<00:05:35.950> like<00:05:36.220> constrain<00:05:37.180> all<00:05:37.450> the<00:05:37.600> ways<00:05:37.750> that 00:05:37.770 --> 00:05:37.780 align:start position:0% really like constrain all the ways that 00:05:37.780 --> 00:05:40.200 align:start position:0% really like constrain all the ways that we<00:05:38.050> look<00:05:38.260> at<00:05:38.580> contractor<00:05:39.580> plans<00:05:40.000> to<00:05:40.150> provide 00:05:40.200 --> 00:05:40.210 align:start position:0% we look at contractor plans to provide 00:05:40.210 --> 00:05:42.960 align:start position:0% we look at contractor plans to provide the<00:05:41.050> contract<00:05:41.560> is<00:05:41.770> this<00:05:42.010> repository<00:05:42.550> of 00:05:42.960 --> 00:05:42.970 align:start position:0% the contract is this repository of 00:05:42.970 --> 00:05:45.720 align:start position:0% the contract is this repository of knowledge<00:05:43.090> and<00:05:43.690> the<00:05:44.020> clients<00:05:44.500> react<00:05:45.100> to<00:05:45.610> that 00:05:45.720 --> 00:05:45.730 align:start position:0% knowledge and the clients react to that 00:05:45.730 --> 00:05:49.080 align:start position:0% knowledge and the clients react to that information<00:05:46.030> and<00:05:46.980> attempt<00:05:47.980> to<00:05:48.040> add<00:05:48.550> things<00:05:48.910> to 00:05:49.080 --> 00:05:49.090 align:start position:0% information and attempt to add things to 00:05:49.090 --> 00:05:57.480 align:start position:0% information and attempt to add things to it<00:05:49.230> if<00:05:50.230> necessary<00:05:50.550> and<00:05:51.550> so<00:05:56.220> what<00:05:57.220> our<00:05:57.340> main 00:05:57.480 --> 00:05:57.490 align:start position:0% it if necessary and so what our main 00:05:57.490 --> 00:06:01.290 align:start position:0% it if necessary and so what our main feature<00:05:57.820> is<00:05:58.350> another<00:05:59.350> principle<00:05:59.890> that<00:06:00.670> we<00:06:01.270> use 00:06:01.290 --> 00:06:01.300 align:start position:0% feature is another principle that we use 00:06:01.300 --> 00:06:02.310 align:start position:0% feature is another principle that we use inside<00:06:01.720> of<00:06:01.780> reach 00:06:02.310 --> 00:06:02.320 align:start position:0% inside of reach 00:06:02.320 --> 00:06:04.410 align:start position:0% inside of reach is<00:06:02.620> that<00:06:02.770> the<00:06:02.860> reach<00:06:03.040> language<00:06:03.460> performs<00:06:04.270> a 00:06:04.410 --> 00:06:04.420 align:start position:0% is that the reach language performs a 00:06:04.420 --> 00:06:06.450 align:start position:0% is that the reach language performs a lot<00:06:04.630> of<00:06:04.810> sophisticated<00:06:05.500> analysis<00:06:06.160> on<00:06:06.310> your 00:06:06.450 --> 00:06:06.460 align:start position:0% lot of sophisticated analysis on your 00:06:06.460 --> 00:06:11.600 align:start position:0% lot of sophisticated analysis on your code<00:06:07.080> at<00:06:08.080> the<00:06:08.260> most<00:06:08.440> basic<00:06:08.590> level<00:06:08.800> we<00:06:09.460> have<00:06:09.670> a 00:06:11.600 --> 00:06:11.610 align:start position:0% code at the most basic level we have a 00:06:11.610 --> 00:06:15.090 align:start position:0% code at the most basic level we have a sound<00:06:12.610> tasting<00:06:13.230> as<00:06:14.230> you<00:06:14.470> can<00:06:14.620> expect<00:06:14.860> in<00:06:15.040> the 00:06:15.090 --> 00:06:15.100 align:start position:0% sound tasting as you can expect in the 00:06:15.100 --> 00:06:17.250 align:start position:0% sound tasting as you can expect in the modern<00:06:15.370> language<00:06:15.720> in<00:06:16.720> addition<00:06:17.050> to<00:06:17.140> that 00:06:17.250 --> 00:06:17.260 align:start position:0% modern language in addition to that 00:06:17.260 --> 00:06:19.380 align:start position:0% modern language in addition to that however<00:06:17.440> we<00:06:18.040> have<00:06:18.280> announced<00:06:18.820> these<00:06:18.970> that<00:06:19.180> are 00:06:19.380 --> 00:06:19.390 align:start position:0% however we have announced these that are 00:06:19.390 --> 00:06:22.290 align:start position:0% however we have announced these that are particular<00:06:20.290> to<00:06:20.320> the<00:06:20.770> needs<00:06:21.010> of<00:06:21.250> deaths<00:06:21.460> as<00:06:21.820> a 00:06:22.290 --> 00:06:22.300 align:start position:0% particular to the needs of deaths as a 00:06:22.300 --> 00:06:24.810 align:start position:0% particular to the needs of deaths as a one<00:06:22.780> little<00:06:23.050> example<00:06:23.250> one<00:06:24.250> of<00:06:24.340> it<00:06:24.430> we'll<00:06:24.670> see 00:06:24.810 --> 00:06:24.820 align:start position:0% one little example one of it we'll see 00:06:24.820 --> 00:06:26.640 align:start position:0% one little example one of it we'll see later<00:06:25.000> is<00:06:25.450> the<00:06:25.600> way<00:06:25.690> that<00:06:25.840> reached<00:06:26.110> uses 00:06:26.640 --> 00:06:26.650 align:start position:0% later is the way that reached uses 00:06:26.650 --> 00:06:29.220 align:start position:0% later is the way that reached uses information<00:06:26.950> flow<00:06:27.490> security<00:06:28.030> to<00:06:28.600> guarantee 00:06:29.220 --> 00:06:29.230 align:start position:0% information flow security to guarantee 00:06:29.230 --> 00:06:32.280 align:start position:0% information flow security to guarantee this<00:06:29.500> information<00:06:30.430> that<00:06:30.790> is<00:06:30.910> known<00:06:31.000> only<00:06:31.420> to 00:06:32.280 --> 00:06:32.290 align:start position:0% this information that is known only to 00:06:32.290 --> 00:06:33.840 align:start position:0% this information that is known only to it<00:06:32.470> does<00:06:32.680> not<00:06:32.890> share<00:06:33.220> without<00:06:33.640> being 00:06:33.840 --> 00:06:33.850 align:start position:0% it does not share without being 00:06:33.850 --> 00:06:39.540 align:start position:0% it does not share without being explicitly<00:06:34.480> transplant<00:06:36.420> now<00:06:38.310> the<00:06:39.310> way<00:06:39.430> that 00:06:39.540 --> 00:06:39.550 align:start position:0% explicitly transplant now the way that 00:06:39.550 --> 00:06:41.850 align:start position:0% explicitly transplant now the way that we<00:06:39.610> do<00:06:39.730> verification<00:06:40.420> is<00:06:40.780> that<00:06:41.050> we<00:06:41.170> take<00:06:41.380> the 00:06:41.850 --> 00:06:41.860 align:start position:0% we do verification is that we take the 00:06:41.860 --> 00:06:43.680 align:start position:0% we do verification is that we take the program<00:06:42.310> written<00:06:42.520> in<00:06:42.670> reach<00:06:42.910> and<00:06:43.270> be 00:06:43.680 --> 00:06:43.690 align:start position:0% program written in reach and be 00:06:43.690 --> 00:06:45.720 align:start position:0% program written in reach and be converted<00:06:44.080> into<00:06:44.470> an<00:06:44.650> estimating<00:06:44.950> problems 00:06:45.720 --> 00:06:45.730 align:start position:0% converted into an estimating problems 00:06:45.730 --> 00:06:48.510 align:start position:0% converted into an estimating problems SMT<00:06:46.390> is<00:06:46.660> one<00:06:47.200> of<00:06:47.290> the<00:06:47.410> classic<00:06:47.920> problems<00:06:48.040> with 00:06:48.510 --> 00:06:48.520 align:start position:0% SMT is one of the classic problems with 00:06:48.520 --> 00:06:50.520 align:start position:0% SMT is one of the classic problems with either<00:06:48.790> science<00:06:49.150> and<00:06:49.360> there<00:06:50.140> are<00:06:50.260> many 00:06:50.520 --> 00:06:50.530 align:start position:0% either science and there are many 00:06:50.530 --> 00:06:52.920 align:start position:0% either science and there are many extremely<00:06:51.220> reliable<00:06:51.760> on<00:06:52.390> an<00:06:52.540> apparent 00:06:52.920 --> 00:06:52.930 align:start position:0% extremely reliable on an apparent 00:06:52.930 --> 00:06:55.650 align:start position:0% extremely reliable on an apparent purpose<00:06:52.960> legacy<00:06:53.800> that<00:06:54.730> can<00:06:54.970> plug<00:06:55.180> not<00:06:55.390> I<00:06:55.420> think 00:06:55.650 --> 00:06:55.660 align:start position:0% purpose legacy that can plug not I think 00:06:55.660 --> 00:07:00.090 align:start position:0% purpose legacy that can plug not I think discharge<00:06:57.570> and<00:06:58.570> so<00:06:58.780> a<00:06:58.960> major<00:06:59.140> part<00:06:59.530> of<00:06:59.590> the<00:06:59.740> way 00:07:00.090 --> 00:07:00.100 align:start position:0% discharge and so a major part of the way 00:07:00.100 --> 00:07:02.520 align:start position:0% discharge and so a major part of the way that<00:07:00.430> the<00:07:00.820> structure<00:07:01.210> it<00:07:01.360> is<00:07:01.720> to<00:07:01.930> make<00:07:02.200> is<00:07:02.350> that 00:07:02.520 --> 00:07:02.530 align:start position:0% that the structure it is to make is that 00:07:02.530 --> 00:07:07.850 align:start position:0% that the structure it is to make is that we<00:07:02.680> can<00:07:02.830> produce<00:07:03.670> as<00:07:04.770> our<00:07:05.770> goal<00:07:06.070> is<00:07:06.460> to<00:07:06.640> provide 00:07:07.850 --> 00:07:07.860 align:start position:0% we can produce as our goal is to provide 00:07:07.860 --> 00:07:12.780 align:start position:0% we can produce as our goal is to provide any<00:07:09.930> during<00:07:10.930> the<00:07:11.050> process<00:07:11.740> so<00:07:12.400> if<00:07:12.490> that<00:07:12.610> means 00:07:12.780 --> 00:07:12.790 align:start position:0% any during the process so if that means 00:07:12.790 --> 00:07:14.520 align:start position:0% any during the process so if that means that<00:07:13.000> they<00:07:13.150> have<00:07:13.180> to<00:07:13.360> be<00:07:13.630> able<00:07:13.720> to<00:07:13.960> discharge 00:07:14.520 --> 00:07:14.530 align:start position:0% that they have to be able to discharge 00:07:14.530 --> 00:07:17.130 align:start position:0% that they have to be able to discharge all<00:07:15.070> the<00:07:15.310> publications<00:07:16.270> automatically<00:07:16.840> and 00:07:17.130 --> 00:07:17.140 align:start position:0% all the publications automatically and 00:07:17.140 --> 00:07:18.840 align:start position:0% all the publications automatically and the<00:07:17.530> only<00:07:17.710> way<00:07:17.920> that<00:07:18.010> we<00:07:18.130> can<00:07:18.190> do<00:07:18.400> that<00:07:18.520> is<00:07:18.670> have 00:07:18.840 --> 00:07:18.850 align:start position:0% the only way that we can do that is have 00:07:18.850 --> 00:07:23.580 align:start position:0% the only way that we can do that is have any<00:07:18.970> ideas<00:07:20.550> now<00:07:21.550> we<00:07:22.540> have<00:07:22.720> a<00:07:22.750> lot<00:07:23.080> of<00:07:23.110> different 00:07:23.580 --> 00:07:23.590 align:start position:0% any ideas now we have a lot of different 00:07:23.590 --> 00:07:26.040 align:start position:0% any ideas now we have a lot of different kinds<00:07:24.190> of<00:07:24.550> properties<00:07:25.120> that<00:07:25.630> can<00:07:26.020> be 00:07:26.040 --> 00:07:26.050 align:start position:0% kinds of properties that can be 00:07:26.050 --> 00:07:29.250 align:start position:0% kinds of properties that can be expressed<00:07:26.850> inside<00:07:27.850> of<00:07:27.970> these<00:07:28.090> programs<00:07:28.540> at 00:07:29.250 --> 00:07:29.260 align:start position:0% expressed inside of these programs at 00:07:29.260 --> 00:07:32.190 align:start position:0% expressed inside of these programs at the<00:07:29.410> highest<00:07:29.650> level<00:07:30.070> we<00:07:30.400> have<00:07:30.910> basic<00:07:31.780> systems 00:07:32.190 --> 00:07:32.200 align:start position:0% the highest level we have basic systems 00:07:32.200 --> 00:07:33.810 align:start position:0% the highest level we have basic systems level<00:07:32.470> property<00:07:32.800> relation<00:07:33.160> between<00:07:33.310> all 00:07:33.810 --> 00:07:33.820 align:start position:0% level property relation between all 00:07:33.820 --> 00:07:35.700 align:start position:0% level property relation between all counts<00:07:34.270> think<00:07:34.960> of<00:07:35.050> like<00:07:35.260> if<00:07:35.530> you're 00:07:35.700 --> 00:07:35.710 align:start position:0% counts think of like if you're 00:07:35.710 --> 00:07:37.830 align:start position:0% counts think of like if you're programming<00:07:36.100> the<00:07:36.280> C<00:07:36.430> program<00:07:36.850> you<00:07:37.390> never<00:07:37.600> want 00:07:37.830 --> 00:07:37.840 align:start position:0% programming the C program you never want 00:07:37.840 --> 00:07:39.690 align:start position:0% programming the C program you never want to<00:07:37.930> have<00:07:38.020> a<00:07:38.050> nullpointerexception<00:07:38.610> and<00:07:39.610> you 00:07:39.690 --> 00:07:39.700 align:start position:0% to have a nullpointerexception and you 00:07:39.700 --> 00:07:41.010 align:start position:0% to have a nullpointerexception and you don't<00:07:39.850> actually<00:07:39.940> need<00:07:40.210> to<00:07:40.270> know<00:07:40.420> anything 00:07:41.010 --> 00:07:41.020 align:start position:0% don't actually need to know anything 00:07:41.020 --> 00:07:42.930 align:start position:0% don't actually need to know anything about<00:07:41.230> the<00:07:41.560> program<00:07:41.980> that<00:07:42.100> you're<00:07:42.190> running<00:07:42.250> to 00:07:42.930 --> 00:07:42.940 align:start position:0% about the program that you're running to 00:07:42.940 --> 00:07:44.430 align:start position:0% about the program that you're running to know<00:07:43.120> that<00:07:43.300> it<00:07:43.390> should<00:07:43.630> have<00:07:43.840> that<00:07:44.050> property 00:07:44.430 --> 00:07:44.440 align:start position:0% know that it should have that property 00:07:44.440 --> 00:07:46.620 align:start position:0% know that it should have that property so<00:07:45.130> slim<00:07:45.370> early<00:07:45.640> part<00:07:46.000> of<00:07:46.090> reaches<00:07:46.450> tool 00:07:46.620 --> 00:07:46.630 align:start position:0% so slim early part of reaches tool 00:07:46.630 --> 00:07:48.720 align:start position:0% so slim early part of reaches tool automatically<00:07:47.140> synthesized<00:07:47.650> companies<00:07:48.550> like 00:07:48.720 --> 00:07:48.730 align:start position:0% automatically synthesized companies like 00:07:48.730 --> 00:07:51.630 align:start position:0% automatically synthesized companies like this<00:07:48.910> would<00:07:49.090> make<00:07:49.240> sense<00:07:49.420> for<00:07:49.630> all<00:07:49.870> others<00:07:50.640> on 00:07:51.630 --> 00:07:51.640 align:start position:0% this would make sense for all others on 00:07:51.640 --> 00:07:52.890 align:start position:0% this would make sense for all others on the<00:07:51.820> other<00:07:51.910> hand<00:07:52.210> we<00:07:52.360> also<00:07:52.390> have<00:07:52.750> the<00:07:52.840> ability 00:07:52.890 --> 00:07:52.900 align:start position:0% the other hand we also have the ability 00:07:52.900 --> 00:07:55.500 align:start position:0% the other hand we also have the ability to<00:07:53.260> break<00:07:53.500> down<00:07:53.680> particular<00:07:54.360> properties<00:07:55.360> of 00:07:55.500 --> 00:07:55.510 align:start position:0% to break down particular properties of 00:07:55.510 --> 00:07:58.110 align:start position:0% to break down particular properties of relevance<00:07:55.870> or<00:07:56.110> one<00:07:56.500> application<00:07:57.010> in<00:07:57.730> the<00:07:57.880> same 00:07:58.110 --> 00:07:58.120 align:start position:0% relevance or one application in the same 00:07:58.120 --> 00:07:59.160 align:start position:0% relevance or one application in the same way<00:07:58.270> that<00:07:58.450> when<00:07:58.600> you're<00:07:58.720> writing<00:07:58.960> the<00:07:59.020> C 00:07:59.160 --> 00:07:59.170 align:start position:0% way that when you're writing the C 00:07:59.170 --> 00:08:01.210 align:start position:0% way that when you're writing the C program<00:07:59.560> you'll<00:07:59.830> have<00:08:00.040> a<00:08:00.070> custom<00:08:00.460> assertion 00:08:01.210 --> 00:08:01.220 align:start position:0% program you'll have a custom assertion 00:08:01.220 --> 00:08:03.130 align:start position:0% program you'll have a custom assertion they<00:08:01.310> make<00:08:01.460> sense<00:08:01.640> program<00:08:02.480> so<00:08:02.870> we<00:08:02.960> have<00:08:03.050> the 00:08:03.130 --> 00:08:03.140 align:start position:0% they make sense program so we have the 00:08:03.140 --> 00:08:05.620 align:start position:0% they make sense program so we have the same<00:08:03.350> letter<00:08:03.650> instead<00:08:04.400> of<00:08:04.460> reach<00:08:05.000> and<00:08:05.390> again 00:08:05.620 --> 00:08:05.630 align:start position:0% same letter instead of reach and again 00:08:05.630 --> 00:08:09.310 align:start position:0% same letter instead of reach and again we'll<00:08:05.750> talk<00:08:05.870> about<00:08:06.020> this<00:08:06.170> later<00:08:07.360> now<00:08:08.360> the<00:08:08.990> next 00:08:09.310 --> 00:08:09.320 align:start position:0% we'll talk about this later now the next 00:08:09.320 --> 00:08:12.820 align:start position:0% we'll talk about this later now the next thing<00:08:09.500> is<00:08:10.490> that<00:08:11.120> as<00:08:11.660> I<00:08:11.810> mentioned<00:08:11.870> the<00:08:12.650> reach 00:08:12.820 --> 00:08:12.830 align:start position:0% thing is that as I mentioned the reach 00:08:12.830 --> 00:08:15.190 align:start position:0% thing is that as I mentioned the reach language<00:08:13.220> provides<00:08:13.760> specifies<00:08:14.690> the<00:08:14.870> entire 00:08:15.190 --> 00:08:15.200 align:start position:0% language provides specifies the entire 00:08:15.200 --> 00:08:17.170 align:start position:0% language provides specifies the entire program<00:08:15.680> we<00:08:16.190> use<00:08:16.310> a<00:08:16.340> process<00:08:16.580> called<00:08:16.880> any 00:08:17.170 --> 00:08:17.180 align:start position:0% program we use a process called any 00:08:17.180 --> 00:08:19.300 align:start position:0% program we use a process called any collector<00:08:17.540> Junction<00:08:17.930> to<00:08:18.380> extract<00:08:18.860> each<00:08:19.160> of 00:08:19.300 --> 00:08:19.310 align:start position:0% collector Junction to extract each of 00:08:19.310 --> 00:08:21.700 align:start position:0% collector Junction to extract each of the<00:08:19.460> individual<00:08:19.940> pieces<00:08:20.180> of<00:08:20.600> the<00:08:20.990> program<00:08:21.500> out 00:08:21.700 --> 00:08:21.710 align:start position:0% the individual pieces of the program out 00:08:21.710 --> 00:08:28.170 align:start position:0% the individual pieces of the program out again<00:08:22.370> I'll<00:08:22.460> talk<00:08:22.670> about<00:08:22.700> this<00:08:22.940> in<00:08:23.090> a<00:08:23.120> moment 00:08:28.170 --> 00:08:28.180 align:start position:0% 00:08:28.180 --> 00:08:31.270 align:start position:0% so<00:08:29.180> that's<00:08:29.660> kind<00:08:29.870> of<00:08:29.900> a<00:08:29.990> roadmap<00:08:30.440> of<00:08:30.680> where<00:08:31.220> I 00:08:31.270 --> 00:08:31.280 align:start position:0% so that's kind of a roadmap of where I 00:08:31.280 --> 00:08:34.260 align:start position:0% so that's kind of a roadmap of where I want<00:08:31.640> to<00:08:31.670> go<00:08:31.910> and<00:08:32.240> the<00:08:32.750> switching<00:08:33.590> dive<00:08:33.800> down 00:08:34.260 --> 00:08:34.270 align:start position:0% want to go and the switching dive down 00:08:34.270 --> 00:08:36.190 align:start position:0% want to go and the switching dive down now<00:08:35.270> what<00:08:35.419> does<00:08:35.510> they<00:08:35.599> actually<00:08:35.840> want<00:08:36.050> one 00:08:36.190 --> 00:08:36.200 align:start position:0% now what does they actually want one 00:08:36.200 --> 00:08:40.450 align:start position:0% now what does they actually want one thing<00:08:36.370> which<00:08:37.370> is<00:08:37.520> that<00:08:38.740> reach<00:08:39.740> is<00:08:40.400> the 00:08:40.450 --> 00:08:40.460 align:start position:0% thing which is that reach is the 00:08:40.460 --> 00:08:43.120 align:start position:0% thing which is that reach is the culmination<00:08:41.300> sorry<00:08:41.930> is<00:08:42.050> the<00:08:42.229> revolution<00:08:43.099> of 00:08:43.120 --> 00:08:43.130 align:start position:0% culmination sorry is the revolution of 00:08:43.130 --> 00:08:45.280 align:start position:0% culmination sorry is the revolution of another<00:08:44.000> DSL<00:08:44.540> that<00:08:44.870> I've<00:08:44.960> worked<00:08:45.080> on 00:08:45.280 --> 00:08:45.290 align:start position:0% another DSL that I've worked on 00:08:45.290 --> 00:08:47.590 align:start position:0% another DSL that I've worked on previously<00:08:45.740> another<00:08:46.730> company<00:08:47.420> making 00:08:47.590 --> 00:08:47.600 align:start position:0% previously another company making 00:08:47.600 --> 00:08:49.390 align:start position:0% previously another company making open-source<00:08:48.080> products<00:08:48.410> called<00:08:48.860> a<00:08:48.950> blacklist 00:08:49.390 --> 00:08:49.400 align:start position:0% open-source products called a blacklist 00:08:49.400 --> 00:08:51.010 align:start position:0% open-source products called a blacklist and<00:08:49.550> that<00:08:50.090> other<00:08:50.330> language<00:08:50.750> is<00:08:50.840> called 00:08:51.010 --> 00:08:51.020 align:start position:0% and that other language is called 00:08:51.020 --> 00:08:53.020 align:start position:0% and that other language is called integrity<00:08:51.440> and<00:08:52.130> the<00:08:52.190> library<00:08:52.520> is<00:08:52.700> also 00:08:53.020 --> 00:08:53.030 align:start position:0% integrity and the library is also 00:08:53.030 --> 00:09:00.420 align:start position:0% integrity and the library is also available<00:08:53.830> and<00:08:54.880> has<00:08:55.880> diverged<00:08:56.870> development 00:09:00.420 --> 00:09:00.430 align:start position:0% 00:09:00.430 --> 00:09:02.280 align:start position:0% different<00:09:00.790> features<00:09:01.120> in<00:09:01.149> the<00:09:01.510> electric<00:09:01.870> 11 00:09:02.280 --> 00:09:02.290 align:start position:0% different features in the electric 11 00:09:02.290 --> 00:09:04.530 align:start position:0% different features in the electric 11 language<00:09:02.649> as<00:09:03.070> the<00:09:03.339> reason<00:09:03.580> language<00:09:03.850> and<00:09:04.120> I 00:09:04.530 --> 00:09:04.540 align:start position:0% language as the reason language and I 00:09:04.540 --> 00:09:06.240 align:start position:0% language as the reason language and I very<00:09:04.779> happy<00:09:04.930> to<00:09:05.140> talk<00:09:05.290> to<00:09:05.350> anyone<00:09:05.649> about<00:09:05.980> what 00:09:06.240 --> 00:09:06.250 align:start position:0% very happy to talk to anyone about what 00:09:06.250 --> 00:09:09.960 align:start position:0% very happy to talk to anyone about what those<00:09:06.670> differences<00:09:07.390> are<00:09:08.490> but<00:09:09.490> I<00:09:09.580> want<00:09:09.790> to<00:09:09.850> make 00:09:09.960 --> 00:09:09.970 align:start position:0% those differences are but I want to make 00:09:09.970 --> 00:09:15.269 align:start position:0% those differences are but I want to make sure<00:09:10.000> that<00:09:10.270> I<00:09:10.480> acknowledge<00:09:11.380> they<00:09:13.410> so<00:09:14.410> now<00:09:15.100> what 00:09:15.269 --> 00:09:15.279 align:start position:0% sure that I acknowledge they so now what 00:09:15.279 --> 00:09:16.800 align:start position:0% sure that I acknowledge they so now what I'm<00:09:15.370> doing<00:09:15.399> is<00:09:15.730> I'm<00:09:15.820> going<00:09:15.850> to<00:09:15.970> switch<00:09:16.120> and<00:09:16.570> go 00:09:16.800 --> 00:09:16.810 align:start position:0% I'm doing is I'm going to switch and go 00:09:16.810 --> 00:09:20.550 align:start position:0% I'm doing is I'm going to switch and go over<00:09:17.170> to<00:09:17.740> the<00:09:18.279> repository<00:09:19.290> so<00:09:20.290> in<00:09:20.500> the 00:09:20.550 --> 00:09:20.560 align:start position:0% over to the repository so in the 00:09:20.560 --> 00:09:23.639 align:start position:0% over to the repository so in the repository<00:09:21.450> we<00:09:22.450> go<00:09:22.750> into<00:09:23.140> the<00:09:23.350> initial 00:09:23.639 --> 00:09:23.649 align:start position:0% repository we go into the initial 00:09:23.649 --> 00:09:27.329 align:start position:0% repository we go into the initial directory<00:09:24.870> and<00:09:25.870> this<00:09:26.560> is<00:09:26.620> the<00:09:26.860> code<00:09:27.010> that<00:09:27.040> will 00:09:27.329 --> 00:09:27.339 align:start position:0% directory and this is the code that will 00:09:27.339 --> 00:09:29.760 align:start position:0% directory and this is the code that will be<00:09:27.430> working<00:09:27.640> on<00:09:27.850> health<00:09:28.720> can<00:09:29.110> you<00:09:29.260> open<00:09:29.410> this 00:09:29.760 --> 00:09:29.770 align:start position:0% be working on health can you open this 00:09:29.770 --> 00:09:32.910 align:start position:0% be working on health can you open this there's<00:09:30.399> been<00:09:30.550> a<00:09:30.850> lot<00:09:31.089> of<00:09:31.500> order<00:09:32.500> fix<00:09:32.740> stuff 00:09:32.910 --> 00:09:32.920 align:start position:0% there's been a lot of order fix stuff 00:09:32.920 --> 00:09:34.650 align:start position:0% there's been a lot of order fix stuff that's<00:09:33.610> to<00:09:33.820> make<00:09:33.970> it<00:09:34.060> so<00:09:34.149> that<00:09:34.270> it<00:09:34.360> can<00:09:34.480> run 00:09:34.650 --> 00:09:34.660 align:start position:0% that's to make it so that it can run 00:09:34.660 --> 00:09:36.930 align:start position:0% that's to make it so that it can run effectively<00:09:35.170> let<00:09:35.890> me<00:09:35.950> just<00:09:36.100> comment<00:09:36.339> a<00:09:36.640> tiny 00:09:36.930 --> 00:09:36.940 align:start position:0% effectively let me just comment a tiny 00:09:36.940 --> 00:09:38.579 align:start position:0% effectively let me just comment a tiny bit<00:09:37.240> about<00:09:37.270> this<00:09:37.570> before<00:09:37.750> we<00:09:38.050> open<00:09:38.290> I'm<00:09:38.380> going 00:09:38.579 --> 00:09:38.589 align:start position:0% bit about this before we open I'm going 00:09:38.589 --> 00:09:47.220 align:start position:0% bit about this before we open I'm going to<00:09:38.649> clarify<00:09:40.260> so<00:09:41.670> we<00:09:42.670> need<00:09:42.910> installation<00:09:46.230> to 00:09:47.220 --> 00:09:47.230 align:start position:0% to clarify so we need installation to 00:09:47.230 --> 00:09:48.810 align:start position:0% to clarify so we need installation to make<00:09:47.260> it<00:09:47.500> to<00:09:47.589> us<00:09:47.680> as<00:09:48.040> easy<00:09:48.279> as<00:09:48.430> possible<00:09:48.550> for 00:09:48.810 --> 00:09:48.820 align:start position:0% make it to us as easy as possible for 00:09:48.820 --> 00:09:50.430 align:start position:0% make it to us as easy as possible for all<00:09:48.970> look<00:09:49.089> it<00:09:49.209> is<00:09:49.420> everything<00:09:49.930> is<00:09:50.080> entirely 00:09:50.430 --> 00:09:50.440 align:start position:0% all look it is everything is entirely 00:09:50.440 --> 00:09:51.269 align:start position:0% all look it is everything is entirely talked<00:09:50.800> arrest 00:09:51.269 --> 00:09:51.279 align:start position:0% talked arrest 00:09:51.279 --> 00:09:53.850 align:start position:0% talked arrest so<00:09:51.880> these<00:09:52.029> run<00:09:52.360> the<00:09:52.480> application<00:09:53.050> certainly 00:09:53.850 --> 00:09:53.860 align:start position:0% so these run the application certainly 00:09:53.860 --> 00:09:56.340 align:start position:0% so these run the application certainly when<00:09:54.220> you<00:09:54.310> compile<00:09:54.670> them<00:09:54.880> even<00:09:55.300> it<00:09:55.720> compiles 00:09:56.340 --> 00:09:56.350 align:start position:0% when you compile them even it compiles 00:09:56.350 --> 00:09:58.199 align:start position:0% when you compile them even it compiles it<00:09:56.440> into<00:09:56.470> a<00:09:56.800> docker<00:09:57.100> container<00:09:57.550> that<00:09:57.910> you<00:09:58.060> can 00:09:58.199 --> 00:09:58.209 align:start position:0% it into a docker container that you can 00:09:58.209 --> 00:10:00.120 align:start position:0% it into a docker container that you can that<00:09:58.360> money<00:09:58.570> that<00:09:58.959> docker<00:09:59.290> container<00:09:59.649> is 00:10:00.120 --> 00:10:00.130 align:start position:0% that money that docker container is 00:10:00.130 --> 00:10:02.280 align:start position:0% that money that docker container is automatically<00:10:00.640> configured<00:10:00.850> to<00:10:01.839> a 00:10:02.280 --> 00:10:02.290 align:start position:0% automatically configured to a 00:10:02.290 --> 00:10:05.250 align:start position:0% automatically configured to a testamental<00:10:02.950> but<00:10:03.160> it<00:10:03.250> also<00:10:04.050> so<00:10:05.050> you<00:10:05.080> don't 00:10:05.250 --> 00:10:05.260 align:start position:0% testamental but it also so you don't 00:10:05.260 --> 00:10:06.750 align:start position:0% testamental but it also so you don't need<00:10:05.380> to<00:10:05.500> worry<00:10:05.650> about<00:10:05.740> that<00:10:06.010> party<00:10:06.370> testing 00:10:06.750 --> 00:10:06.760 align:start position:0% need to worry about that party testing 00:10:06.760 --> 00:10:09.079 align:start position:0% need to worry about that party testing similarly<00:10:07.750> you<00:10:08.110> don't<00:10:08.290> need<00:10:08.410> to<00:10:08.560> download<00:10:08.740> any 00:10:09.079 --> 00:10:09.089 align:start position:0% similarly you don't need to download any 00:10:09.089 --> 00:10:11.160 align:start position:0% similarly you don't need to download any download<00:10:10.089> or<00:10:10.209> install<00:10:10.270> anything<00:10:10.720> like<00:10:11.140> a 00:10:11.160 --> 00:10:11.170 align:start position:0% download or install anything like a 00:10:11.170 --> 00:10:13.470 align:start position:0% download or install anything like a regional<00:10:11.529> pilot<00:10:11.680> the<00:10:12.310> regional<00:10:12.670> pilot<00:10:12.790> is<00:10:13.330> the 00:10:13.470 --> 00:10:13.480 align:start position:0% regional pilot the regional pilot is the 00:10:13.480 --> 00:10:15.329 align:start position:0% regional pilot the regional pilot is the shelter<00:10:13.959> of<00:10:14.230> redundant<00:10:14.650> bottom<00:10:15.070> which<00:10:15.310> is 00:10:15.329 --> 00:10:15.339 align:start position:0% shelter of redundant bottom which is 00:10:15.339 --> 00:10:18.970 align:start position:0% shelter of redundant bottom which is eight<00:10:15.790> lines<00:10:16.120> it<00:10:16.750> configures 00:10:18.970 --> 00:10:18.980 align:start position:0% eight lines it configures 00:10:18.980 --> 00:10:21.710 align:start position:0% eight lines it configures so<00:10:19.980> there's<00:10:20.400> a<00:10:20.460> lot<00:10:20.670> here<00:10:20.880> that's<00:10:21.150> gonna<00:10:21.450> make 00:10:21.710 --> 00:10:21.720 align:start position:0% so there's a lot here that's gonna make 00:10:21.720 --> 00:10:24.830 align:start position:0% so there's a lot here that's gonna make some<00:10:21.750> of<00:10:22.020> those<00:10:22.170> things<00:10:22.560> all<00:10:22.860> together<00:10:23.670> but<00:10:24.600> we 00:10:24.830 --> 00:10:24.840 align:start position:0% some of those things all together but we 00:10:24.840 --> 00:10:27.620 align:start position:0% some of those things all together but we are<00:10:24.900> going<00:10:25.080> to<00:10:25.140> be<00:10:25.230> inside<00:10:26.150> this<00:10:27.150> file<00:10:27.450> right 00:10:27.620 --> 00:10:27.630 align:start position:0% are going to be inside this file right 00:10:27.630 --> 00:10:30.470 align:start position:0% are going to be inside this file right here<00:10:27.890> multi-state<00:10:28.890> not<00:10:29.190> our<00:10:29.430> name<00:10:29.730> that's 00:10:30.470 --> 00:10:30.480 align:start position:0% here multi-state not our name that's 00:10:30.480 --> 00:10:33.800 align:start position:0% here multi-state not our name that's gonna<00:10:30.630> be<00:10:30.810> our<00:10:30.930> meter<00:10:31.290> man<00:10:32.480> here's<00:10:33.480> what<00:10:33.690> we're 00:10:33.800 --> 00:10:33.810 align:start position:0% gonna be our meter man here's what we're 00:10:33.810 --> 00:10:37.790 align:start position:0% gonna be our meter man here's what we're going<00:10:33.930> to<00:10:33.960> start<00:10:34.260> off<00:10:34.380> this<00:10:34.940> so<00:10:36.500> in<00:10:37.500> the<00:10:37.680> rich 00:10:37.790 --> 00:10:37.800 align:start position:0% going to start off this so in the rich 00:10:37.800 --> 00:10:40.070 align:start position:0% going to start off this so in the rich language<00:10:38.010> you<00:10:38.790> are<00:10:38.820> writing<00:10:39.210> in<00:10:39.510> a<00:10:39.600> subset 00:10:40.070 --> 00:10:40.080 align:start position:0% language you are writing in a subset 00:10:40.080 --> 00:10:43.160 align:start position:0% language you are writing in a subset observers<00:10:40.800> so<00:10:41.460> the<00:10:41.760> syntax<00:10:42.000> is<00:10:42.390> exactly<00:10:42.990> the 00:10:43.160 --> 00:10:43.170 align:start position:0% observers so the syntax is exactly the 00:10:43.170 --> 00:10:45.440 align:start position:0% observers so the syntax is exactly the same<00:10:43.320> syntax<00:10:43.560> as<00:10:43.800> JavaScript<00:10:44.430> almost<00:10:45.270> all 00:10:45.440 --> 00:10:45.450 align:start position:0% same syntax as JavaScript almost all 00:10:45.450 --> 00:10:47.560 align:start position:0% same syntax as JavaScript almost all normal<00:10:46.170> JavaScript<00:10:46.410> features<00:10:46.710> are<00:10:47.160> available 00:10:47.560 --> 00:10:47.570 align:start position:0% normal JavaScript features are available 00:10:47.570 --> 00:10:49.880 align:start position:0% normal JavaScript features are available and<00:10:48.570> they<00:10:48.720> mean<00:10:48.960> roughly<00:10:49.380> the<00:10:49.530> same<00:10:49.680> thing 00:10:49.880 --> 00:10:49.890 align:start position:0% and they mean roughly the same thing 00:10:49.890 --> 00:10:56.180 align:start position:0% and they mean roughly the same thing that<00:10:50.070> there<00:10:50.220> are<00:10:50.280> many<00:10:52.490> so<00:10:53.490> for<00:10:53.940> example<00:10:55.190> let's 00:10:56.180 --> 00:10:56.190 align:start position:0% that there are many so for example let's 00:10:56.190 --> 00:10:57.440 align:start position:0% that there are many so for example let's start<00:10:56.430> by<00:10:56.520> talking<00:10:56.700> about<00:10:56.850> what<00:10:57.120> we're<00:10:57.300> going 00:10:57.440 --> 00:10:57.450 align:start position:0% start by talking about what we're going 00:10:57.450 --> 00:11:01.310 align:start position:0% start by talking about what we're going to<00:10:57.480> build<00:10:57.630> and<00:10:58.290> what<00:10:59.190> the<00:10:59.660> overall<00:11:00.660> model<00:11:01.050> of 00:11:01.310 --> 00:11:01.320 align:start position:0% to build and what the overall model of 00:11:01.320 --> 00:11:03.680 align:start position:0% to build and what the overall model of engagement<00:11:01.830> is<00:11:02.430> we're<00:11:03.300> going<00:11:03.390> to<00:11:03.450> build<00:11:03.600> today 00:11:03.680 --> 00:11:03.690 align:start position:0% engagement is we're going to build today 00:11:03.690 --> 00:11:06.800 align:start position:0% engagement is we're going to build today is<00:11:04.170> an<00:11:04.710> abstraction<00:11:05.190> of<00:11:05.550> a<00:11:06.030> multi<00:11:06.360> signature 00:11:06.800 --> 00:11:06.810 align:start position:0% is an abstraction of a multi signature 00:11:06.810 --> 00:11:09.230 align:start position:0% is an abstraction of a multi signature wallet<00:11:07.110> the<00:11:07.740> key<00:11:07.890> idea<00:11:08.160> of<00:11:08.190> a<00:11:08.580> visual<00:11:08.970> wallet 00:11:09.230 --> 00:11:09.240 align:start position:0% wallet the key idea of a visual wallet 00:11:09.240 --> 00:11:12.800 align:start position:0% wallet the key idea of a visual wallet is<00:11:09.570> that<00:11:09.630> many<00:11:10.080> people<00:11:10.170> collaborate<00:11:11.160> to<00:11:11.810> pool 00:11:12.800 --> 00:11:12.810 align:start position:0% is that many people collaborate to pool 00:11:12.810 --> 00:11:15.080 align:start position:0% is that many people collaborate to pool funds<00:11:13.140> and<00:11:13.920> then<00:11:14.040> when<00:11:14.220> they<00:11:14.340> extract<00:11:14.790> those 00:11:15.080 --> 00:11:15.090 align:start position:0% funds and then when they extract those 00:11:15.090 --> 00:11:17.600 align:start position:0% funds and then when they extract those funds<00:11:15.420> other<00:11:16.260> people<00:11:16.620> have<00:11:16.770> a<00:11:16.800> say<00:11:17.100> on<00:11:17.400> whether 00:11:17.600 --> 00:11:17.610 align:start position:0% funds other people have a say on whether 00:11:17.610 --> 00:11:20.210 align:start position:0% funds other people have a say on whether or<00:11:17.790> not<00:11:17.850> the<00:11:18.300> extracting<00:11:18.810> happens<00:11:19.380> so<00:11:20.100> we're 00:11:20.210 --> 00:11:20.220 align:start position:0% or not the extracting happens so we're 00:11:20.220 --> 00:11:22.610 align:start position:0% or not the extracting happens so we're going<00:11:20.310> to<00:11:20.430> distract<00:11:20.730> that<00:11:20.880> idea<00:11:21.300> to<00:11:21.930> two 00:11:22.610 --> 00:11:22.620 align:start position:0% going to distract that idea to two 00:11:22.620 --> 00:11:25.250 align:start position:0% going to distract that idea to two accounts<00:11:23.100> a<00:11:23.480> parent<00:11:24.480> and<00:11:24.660> a<00:11:24.720> child 00:11:25.250 --> 00:11:25.260 align:start position:0% accounts a parent and a child 00:11:25.260 --> 00:11:27.590 align:start position:0% accounts a parent and a child the<00:11:25.620> parent<00:11:26.010> makes<00:11:26.339> a<00:11:26.460> deposit<00:11:27.000> on<00:11:27.120> behalf<00:11:27.420> of 00:11:27.590 --> 00:11:27.600 align:start position:0% the parent makes a deposit on behalf of 00:11:27.600 --> 00:11:30.200 align:start position:0% the parent makes a deposit on behalf of the<00:11:27.720> channel<00:11:28.050> and<00:11:28.530> the<00:11:28.620> child<00:11:28.890> can<00:11:29.310> attempt<00:11:30.150> to 00:11:30.200 --> 00:11:30.210 align:start position:0% the channel and the child can attempt to 00:11:30.210 --> 00:11:32.600 align:start position:0% the channel and the child can attempt to sedate<00:11:30.570> withdraws<00:11:31.020> it<00:11:31.650> must<00:11:31.830> be<00:11:31.980> explicitly 00:11:32.600 --> 00:11:32.610 align:start position:0% sedate withdraws it must be explicitly 00:11:32.610 --> 00:11:35.780 align:start position:0% sedate withdraws it must be explicitly approved<00:11:32.910> by<00:11:33.420> the<00:11:33.480> parent<00:11:34.070> so<00:11:35.070> this<00:11:35.460> is<00:11:35.610> not<00:11:35.730> a 00:11:35.780 --> 00:11:35.790 align:start position:0% approved by the parent so this is not a 00:11:35.790 --> 00:11:38.180 align:start position:0% approved by the parent so this is not a product<00:11:36.270> that<00:11:36.630> when<00:11:37.080> we're<00:11:37.230> done<00:11:37.380> today<00:11:37.589> we're 00:11:38.180 --> 00:11:38.190 align:start position:0% product that when we're done today we're 00:11:38.190 --> 00:11:39.620 align:start position:0% product that when we're done today we're going<00:11:38.280> to<00:11:38.370> launch<00:11:38.550> and<00:11:38.880> become<00:11:39.180> blocked<00:11:39.390> and 00:11:39.620 --> 00:11:39.630 align:start position:0% going to launch and become blocked and 00:11:39.630 --> 00:11:41.780 align:start position:0% going to launch and become blocked and leaners<00:11:40.020> this<00:11:40.650> is<00:11:40.800> an<00:11:40.890> abstraction<00:11:41.339> of<00:11:41.730> what 00:11:41.780 --> 00:11:41.790 align:start position:0% leaners this is an abstraction of what 00:11:41.790 --> 00:11:43.800 align:start position:0% leaners this is an abstraction of what kinds<00:11:42.480> of<00:11:42.570> problems<00:11:42.780> people 00:11:43.800 --> 00:11:43.810 align:start position:0% kinds of problems people 00:11:43.810 --> 00:11:47.519 align:start position:0% kinds of problems people to<00:11:43.900> solve<00:11:44.080> it<00:11:44.290> on<00:11:44.470> the<00:11:44.590> blockchain<00:11:45.300> and<00:11:46.529> it's 00:11:47.519 --> 00:11:47.529 align:start position:0% to solve it on the blockchain and it's 00:11:47.529 --> 00:11:49.170 align:start position:0% to solve it on the blockchain and it's small<00:11:48.190> enough<00:11:48.220> that<00:11:48.460> we<00:11:48.670> can<00:11:48.820> do<00:11:48.940> it<00:11:49.060> in 00:11:49.170 --> 00:11:49.180 align:start position:0% small enough that we can do it in 00:11:49.180 --> 00:11:53.550 align:start position:0% small enough that we can do it in minutes<00:11:49.390> 30<00:11:49.870> minutes<00:11:51.090> all<00:11:52.090> right<00:11:52.120> so<00:11:53.050> the 00:11:53.550 --> 00:11:53.560 align:start position:0% minutes 30 minutes all right so the 00:11:53.560 --> 00:11:56.310 align:start position:0% minutes 30 minutes all right so the first<00:11:53.770> thing<00:11:53.920> that<00:11:53.950> we<00:11:54.100> want<00:11:54.250> to<00:11:54.279> do<00:11:54.570> is<00:11:55.570> you 00:11:56.310 --> 00:11:56.320 align:start position:0% first thing that we want to do is you 00:11:56.320 --> 00:11:58.769 align:start position:0% first thing that we want to do is you want<00:11:56.500> to<00:11:56.620> specify<00:11:56.860> that<00:11:57.490> this<00:11:58.330> protocol 00:11:58.769 --> 00:11:58.779 align:start position:0% want to specify that this protocol 00:11:58.779 --> 00:12:01.200 align:start position:0% want to specify that this protocol involves<00:11:59.440> two<00:11:59.980> different<00:12:00.010> part<00:12:00.640> participants 00:12:01.200 --> 00:12:01.210 align:start position:0% involves two different part participants 00:12:01.210 --> 00:12:02.700 align:start position:0% involves two different part participants a<00:12:01.390> child<00:12:01.900> and<00:12:02.260> the<00:12:02.320> parent 00:12:02.700 --> 00:12:02.710 align:start position:0% a child and the parent 00:12:02.710 --> 00:12:05.100 align:start position:0% a child and the parent it's<00:12:03.640> either<00:12:03.790> each<00:12:04.060> language<00:12:04.270> one<00:12:04.900> of<00:12:05.020> these 00:12:05.100 --> 00:12:05.110 align:start position:0% it's either each language one of these 00:12:05.110 --> 00:12:07.290 align:start position:0% it's either each language one of these you<00:12:05.260> do<00:12:05.500> is<00:12:05.650> you<00:12:05.950> specify<00:12:06.490> each<00:12:06.910> one<00:12:07.120> of<00:12:07.210> the 00:12:07.290 --> 00:12:07.300 align:start position:0% you do is you specify each one of the 00:12:07.300 --> 00:12:09.450 align:start position:0% you do is you specify each one of the parties<00:12:07.630> and<00:12:07.900> then<00:12:08.500> we'll<00:12:08.770> write<00:12:08.890> one<00:12:09.220> program 00:12:09.450 --> 00:12:09.460 align:start position:0% parties and then we'll write one program 00:12:09.460 --> 00:12:11.820 align:start position:0% parties and then we'll write one program in<00:12:09.850> this<00:12:10.390> main<00:12:10.630> function<00:12:10.839> and<00:12:11.200> this<00:12:11.589> main 00:12:11.820 --> 00:12:11.830 align:start position:0% in this main function and this main 00:12:11.830 --> 00:12:13.019 align:start position:0% in this main function and this main function<00:12:12.250> is<00:12:12.339> going<00:12:12.520> to<00:12:12.610> include<00:12:12.820> the 00:12:13.019 --> 00:12:13.029 align:start position:0% function is going to include the 00:12:13.029 --> 00:12:15.329 align:start position:0% function is going to include the behavior<00:12:13.480> of<00:12:13.510> all<00:12:13.779> the<00:12:13.839> participants<00:12:14.620> as<00:12:14.920> well 00:12:15.329 --> 00:12:15.339 align:start position:0% behavior of all the participants as well 00:12:15.339 --> 00:12:20.310 align:start position:0% behavior of all the participants as well as<00:12:15.910> all<00:12:16.510> of<00:12:16.810> the<00:12:16.930> smart<00:12:17.110> contracts<00:12:17.880> so<00:12:19.320> the 00:12:20.310 --> 00:12:20.320 align:start position:0% as all of the smart contracts so the 00:12:20.320 --> 00:12:22.950 align:start position:0% as all of the smart contracts so the first<00:12:20.560> thing<00:12:20.710> that<00:12:20.740> we'll<00:12:20.920> do<00:12:21.070> is<00:12:21.900> we'll<00:12:22.900> have 00:12:22.950 --> 00:12:22.960 align:start position:0% first thing that we'll do is we'll have 00:12:22.960 --> 00:12:26.240 align:start position:0% first thing that we'll do is we'll have the<00:12:23.890> child<00:12:24.190> and<00:12:24.490> attach<00:12:24.790> to<00:12:24.820> the<00:12:25.089> contract 00:12:26.240 --> 00:12:26.250 align:start position:0% the child and attach to the contract 00:12:26.250 --> 00:12:29.040 align:start position:0% the child and attach to the contract we'll<00:12:27.250> do<00:12:27.370> that<00:12:27.520> by<00:12:27.730> having<00:12:27.970> the<00:12:28.120> child<00:12:28.360> make<00:12:29.020> a 00:12:29.040 --> 00:12:29.050 align:start position:0% we'll do that by having the child make a 00:12:29.050 --> 00:12:33.750 align:start position:0% we'll do that by having the child make a publication<00:12:29.680> now<00:12:31.020> the<00:12:32.020> end<00:12:32.110> of<00:12:32.980> watching<00:12:33.640> is 00:12:33.750 --> 00:12:33.760 align:start position:0% publication now the end of watching is 00:12:33.760 --> 00:12:36.030 align:start position:0% publication now the end of watching is there's<00:12:34.000> this<00:12:34.260> monotonically<00:12:35.260> increasing 00:12:36.030 --> 00:12:36.040 align:start position:0% there's this monotonically increasing 00:12:36.040 --> 00:12:40.019 align:start position:0% there's this monotonically increasing data<00:12:36.400> structure<00:12:36.850> of<00:12:37.000> the<00:12:37.930> history<00:12:38.290> all<00:12:39.029> events 00:12:40.019 --> 00:12:40.029 align:start position:0% data structure of the history all events 00:12:40.029 --> 00:12:43.079 align:start position:0% data structure of the history all events or<00:12:40.210> attitudes<00:12:40.839> in<00:12:41.800> this<00:12:42.010> case<00:12:42.279> we<00:12:42.790> think<00:12:43.000> about 00:12:43.079 --> 00:12:43.089 align:start position:0% or attitudes in this case we think about 00:12:43.089 --> 00:12:45.570 align:start position:0% or attitudes in this case we think about that<00:12:43.360> as<00:12:43.570> being<00:12:43.870> a<00:12:44.260> publication<00:12:45.040> to<00:12:45.220> all<00:12:45.400> of 00:12:45.570 --> 00:12:45.580 align:start position:0% that as being a publication to all of 00:12:45.580 --> 00:12:47.790 align:start position:0% that as being a publication to all of the<00:12:45.670> other<00:12:45.850> parties<00:12:46.210> so<00:12:47.080> when<00:12:47.170> we<00:12:47.290> call<00:12:47.500> child 00:12:47.790 --> 00:12:47.800 align:start position:0% the other parties so when we call child 00:12:47.800 --> 00:12:49.530 align:start position:0% the other parties so when we call child publish<00:12:48.550> we're<00:12:49.000> saying<00:12:49.180> that<00:12:49.270> it's<00:12:49.450> the 00:12:49.530 --> 00:12:49.540 align:start position:0% publish we're saying that it's the 00:12:49.540 --> 00:12:51.360 align:start position:0% publish we're saying that it's the child's<00:12:49.930> responsibility<00:12:50.710> we'll<00:12:51.190> publish 00:12:51.360 --> 00:12:51.370 align:start position:0% child's responsibility we'll publish 00:12:51.370 --> 00:12:53.340 align:start position:0% child's responsibility we'll publish this<00:12:51.790> information<00:12:52.030> now<00:12:52.839> it<00:12:52.960> turns<00:12:53.140> out<00:12:53.290> that 00:12:53.340 --> 00:12:53.350 align:start position:0% this information now it turns out that 00:12:53.350 --> 00:12:54.500 align:start position:0% this information now it turns out that there's<00:12:53.620> actually<00:12:53.860> nothing 00:12:54.500 --> 00:12:54.510 align:start position:0% there's actually nothing 00:12:54.510 --> 00:12:55.910 align:start position:0% there's actually nothing originally<00:12:55.290> it's<00:12:55.410> just<00:12:55.560> the<00:12:55.680> way<00:12:55.800> that 00:12:55.910 --> 00:12:55.920 align:start position:0% originally it's just the way that 00:12:55.920 --> 00:13:01.280 align:start position:0% originally it's just the way that they're<00:12:56.040> in<00:12:56.250> now<00:12:59.780> every<00:13:00.780> time<00:13:00.960> when<00:13:01.260> you 00:13:01.280 --> 00:13:01.290 align:start position:0% they're in now every time when you 00:13:01.290 --> 00:13:05.150 align:start position:0% they're in now every time when you expect<00:13:01.800> to<00:13:01.920> see<00:13:02.160> a<00:13:02.460> message<00:13:02.880> on<00:13:03.740> in<00:13:04.740> the 00:13:05.150 --> 00:13:05.160 align:start position:0% expect to see a message on in the 00:13:05.160 --> 00:13:06.440 align:start position:0% expect to see a message on in the vertical<00:13:05.520> we<00:13:05.640> have<00:13:05.790> the<00:13:05.880> same<00:13:06.090> what<00:13:06.330> would 00:13:06.440 --> 00:13:06.450 align:start position:0% vertical we have the same what would 00:13:06.450 --> 00:13:08.210 align:start position:0% vertical we have the same what would happen<00:13:06.780> if<00:13:07.170> the<00:13:07.380> person<00:13:07.530> who's<00:13:07.770> supposed<00:13:08.160> to 00:13:08.210 --> 00:13:08.220 align:start position:0% happen if the person who's supposed to 00:13:08.220 --> 00:13:10.040 align:start position:0% happen if the person who's supposed to do<00:13:08.400> this<00:13:08.550> didn't<00:13:09.510> do<00:13:09.720> it 00:13:10.040 --> 00:13:10.050 align:start position:0% do this didn't do it 00:13:10.050 --> 00:13:13.310 align:start position:0% do this didn't do it what<00:13:10.620> if<00:13:10.710> they<00:13:11.300> what<00:13:12.300> if<00:13:12.330> they<00:13:12.510> time<00:13:12.750> on<00:13:12.870> prices 00:13:13.310 --> 00:13:13.320 align:start position:0% what if they what if they time on prices 00:13:13.320 --> 00:13:15.230 align:start position:0% what if they what if they time on prices and<00:13:13.500> so<00:13:14.010> we<00:13:14.100> always<00:13:14.280> specify<00:13:14.820> what<00:13:15.090> would 00:13:15.230 --> 00:13:15.240 align:start position:0% and so we always specify what would 00:13:15.240 --> 00:13:17.180 align:start position:0% and so we always specify what would happen<00:13:15.540> in<00:13:15.630> the<00:13:15.690> case<00:13:15.720> of<00:13:15.990> the<00:13:16.050> time<00:13:16.230> out<00:13:16.380> and 00:13:17.180 --> 00:13:17.190 align:start position:0% happen in the case of the time out and 00:13:17.190 --> 00:13:20.630 align:start position:0% happen in the case of the time out and typos<00:13:17.850> are<00:13:17.970> expressed<00:13:18.450> in<00:13:19.260> terms<00:13:19.980> of<00:13:20.400> how<00:13:20.580> many 00:13:20.630 --> 00:13:20.640 align:start position:0% typos are expressed in terms of how many 00:13:20.640 --> 00:13:22.100 align:start position:0% typos are expressed in terms of how many blocks<00:13:21.060> you're<00:13:21.360> willing<00:13:21.570> to<00:13:21.600> wait<00:13:21.810> for<00:13:22.020> an 00:13:22.100 --> 00:13:22.110 align:start position:0% blocks you're willing to wait for an 00:13:22.110 --> 00:13:24.260 align:start position:0% blocks you're willing to wait for an accession<00:13:22.350> so<00:13:22.920> we're<00:13:23.490> going<00:13:23.640> to<00:13:23.790> just<00:13:24.210> have 00:13:24.260 --> 00:13:24.270 align:start position:0% accession so we're going to just have 00:13:24.270 --> 00:13:26.690 align:start position:0% accession so we're going to just have this<00:13:24.480> variable<00:13:24.840> and<00:13:25.020> program<00:13:25.440> delay<00:13:25.980> which<00:13:26.670> is 00:13:26.690 --> 00:13:26.700 align:start position:0% this variable and program delay which is 00:13:26.700 --> 00:13:28.580 align:start position:0% this variable and program delay which is going<00:13:26.910> to<00:13:26.970> say<00:13:27.180> the<00:13:27.750> message<00:13:28.050> has<00:13:28.320> kind<00:13:28.500> of 00:13:28.580 --> 00:13:28.590 align:start position:0% going to say the message has kind of 00:13:28.590 --> 00:13:30.380 align:start position:0% going to say the message has kind of comment<00:13:28.950> in<00:13:29.070> delay<00:13:29.310> seconds<00:13:29.670> and<00:13:30.000> if<00:13:30.270> it 00:13:30.380 --> 00:13:30.390 align:start position:0% comment in delay seconds and if it 00:13:30.390 --> 00:13:33.500 align:start position:0% comment in delay seconds and if it doesn't<00:13:30.750> then<00:13:31.260> we'll<00:13:31.530> fail<00:13:31.800> and<00:13:32.340> the<00:13:33.240> way<00:13:33.360> that 00:13:33.500 --> 00:13:33.510 align:start position:0% doesn't then we'll fail and the way that 00:13:33.510 --> 00:13:35.480 align:start position:0% doesn't then we'll fail and the way that will<00:13:33.630> fail<00:13:33.900> is<00:13:34.200> that<00:13:34.440> anyone<00:13:34.860> as<00:13:35.220> well<00:13:35.370> as 00:13:35.480 --> 00:13:35.490 align:start position:0% will fail is that anyone as well as 00:13:35.490 --> 00:13:37.760 align:start position:0% will fail is that anyone as well as underscore<00:13:35.970> means<00:13:36.180> anyone<00:13:37.050> is<00:13:37.260> able<00:13:37.470> to 00:13:37.760 --> 00:13:37.770 align:start position:0% underscore means anyone is able to 00:13:37.770 --> 00:13:39.830 align:start position:0% underscore means anyone is able to submit<00:13:37.980> the<00:13:38.190> message<00:13:38.490> and<00:13:39.330> what<00:13:39.510> this<00:13:39.600> message 00:13:39.830 --> 00:13:39.840 align:start position:0% submit the message and what this message 00:13:39.840 --> 00:13:45.050 align:start position:0% submit the message and what this message does<00:13:40.230> is<00:13:41.510> it<00:13:42.510> will<00:13:43.610> commit<00:13:44.610> the<00:13:44.670> transaction 00:13:45.050 --> 00:13:45.060 align:start position:0% does is it will commit the transaction 00:13:45.060 --> 00:13:49.400 align:start position:0% does is it will commit the transaction and<00:13:45.690> then<00:13:46.460> say<00:13:47.460> that<00:13:47.700> we<00:13:48.050> have<00:13:49.050> finished 00:13:49.400 --> 00:13:49.410 align:start position:0% and then say that we have finished 00:13:49.410 --> 00:13:51.350 align:start position:0% and then say that we have finished writing<00:13:49.860> the<00:13:50.010> curveball<00:13:50.250> and<00:13:50.700> the<00:13:51.090> reason 00:13:51.350 --> 00:13:51.360 align:start position:0% writing the curveball and the reason 00:13:51.360 --> 00:13:53.210 align:start position:0% writing the curveball and the reason that<00:13:51.390> I'm<00:13:51.540> returning<00:13:51.990> this<00:13:52.260> array<00:13:52.650> of<00:13:52.860> turin 00:13:53.210 --> 00:13:53.220 align:start position:0% that I'm returning this array of turin 00:13:53.220 --> 00:13:54.710 align:start position:0% that I'm returning this array of turin zero<00:13:53.460> is<00:13:53.880> because<00:13:54.060> at<00:13:54.240> the<00:13:54.360> end<00:13:54.390> of<00:13:54.660> the 00:13:54.710 --> 00:13:54.720 align:start position:0% zero is because at the end of the 00:13:54.720 --> 00:13:56.390 align:start position:0% zero is because at the end of the protocol<00:13:55.020> when<00:13:55.200> we're<00:13:55.350> finally<00:13:55.680> done<00:13:55.830> we're 00:13:56.390 --> 00:13:56.400 align:start position:0% protocol when we're finally done we're 00:13:56.400 --> 00:13:58.430 align:start position:0% protocol when we're finally done we're gonna<00:13:56.490> return<00:13:56.790> how<00:13:57.150> many<00:13:57.360> times<00:13:57.630> the<00:13:58.260> parents 00:13:58.430 --> 00:13:58.440 align:start position:0% gonna return how many times the parents 00:13:58.440 --> 00:13:59.900 align:start position:0% gonna return how many times the parents said<00:13:58.770> yes<00:13:58.980> and<00:13:59.220> how<00:13:59.310> many<00:13:59.460> times<00:13:59.640> the<00:13:59.760> parents 00:13:59.900 --> 00:13:59.910 align:start position:0% said yes and how many times the parents 00:13:59.910 --> 00:14:03.230 align:start position:0% said yes and how many times the parents said<00:14:00.240> no<00:14:00.390> so<00:14:01.140> if<00:14:01.500> the<00:14:02.130> child<00:14:02.340> times<00:14:02.820> out<00:14:03.030> and 00:14:03.230 --> 00:14:03.240 align:start position:0% said no so if the child times out and 00:14:03.240 --> 00:14:05.690 align:start position:0% said no so if the child times out and never<00:14:03.420> joins<00:14:03.750> and<00:14:04.530> we're<00:14:04.650> done<00:14:04.830> and<00:14:05.130> so<00:14:05.310> no 00:14:05.690 --> 00:14:05.700 align:start position:0% never joins and we're done and so no 00:14:05.700 --> 00:14:09.200 align:start position:0% never joins and we're done and so no event<00:14:06.210> actually<00:14:06.390> happened<00:14:07.220> now<00:14:08.250> after<00:14:08.970> we<00:14:09.060> do 00:14:09.200 --> 00:14:09.210 align:start position:0% event actually happened now after we do 00:14:09.210 --> 00:14:13.130 align:start position:0% event actually happened now after we do this<00:14:10.130> now<00:14:11.130> the<00:14:11.580> code<00:14:11.850> has<00:14:12.030> transitioned<00:14:12.420> down 00:14:13.130 --> 00:14:13.140 align:start position:0% this now the code has transitioned down 00:14:13.140 --> 00:14:15.800 align:start position:0% this now the code has transitioned down here<00:14:13.410> and<00:14:14.280> we're<00:14:14.520> now<00:14:14.700> inside<00:14:15.300> of<00:14:15.600> the 00:14:15.800 --> 00:14:15.810 align:start position:0% here and we're now inside of the 00:14:15.810 --> 00:14:17.750 align:start position:0% here and we're now inside of the contract<00:14:16.230> so<00:14:16.500> at<00:14:16.950> this<00:14:17.040> point<00:14:17.250> we<00:14:17.520> need<00:14:17.610> to 00:14:17.750 --> 00:14:17.760 align:start position:0% contract so at this point we need to 00:14:17.760 --> 00:14:20.900 align:start position:0% contract so at this point we need to verify<00:14:18.620> anything<00:14:19.620> that<00:14:19.890> must<00:14:20.100> be<00:14:20.160> true<00:14:20.460> above 00:14:20.900 --> 00:14:20.910 align:start position:0% verify anything that must be true above 00:14:20.910 --> 00:14:22.910 align:start position:0% verify anything that must be true above the<00:14:21.030> publication<00:14:21.570> now<00:14:22.020> in<00:14:22.050> this<00:14:22.200> case<00:14:22.350> I<00:14:22.620> think 00:14:22.910 --> 00:14:22.920 align:start position:0% the publication now in this case I think 00:14:22.920 --> 00:14:24.319 align:start position:0% the publication now in this case I think was<00:14:23.160> actually 00:14:24.319 --> 00:14:24.329 align:start position:0% was actually 00:14:24.329 --> 00:14:26.329 align:start position:0% was actually there's<00:14:24.509> nothing<00:14:24.720> to<00:14:24.809> say<00:14:25.259> so<00:14:25.589> we<00:14:25.739> commit<00:14:26.249> the 00:14:26.329 --> 00:14:26.339 align:start position:0% there's nothing to say so we commit the 00:14:26.339 --> 00:14:32.389 align:start position:0% there's nothing to say so we commit the transaction<00:14:28.730> and<00:14:29.730> now<00:14:30.660> we<00:14:30.720> go<00:14:30.989> back<00:14:31.259> to<00:14:31.920> a 00:14:32.389 --> 00:14:32.399 align:start position:0% transaction and now we go back to a 00:14:32.399 --> 00:14:34.759 align:start position:0% transaction and now we go back to a context<00:14:33.179> where<00:14:33.360> we're<00:14:33.569> outside<00:14:34.049> of<00:14:34.410> the 00:14:34.759 --> 00:14:34.769 align:start position:0% context where we're outside of the 00:14:34.769 --> 00:14:38.329 align:start position:0% context where we're outside of the purple<00:14:35.100> the<00:14:36.059> idea<00:14:36.389> of<00:14:37.019> the<00:14:37.319> reach<00:14:37.439> language<00:14:37.860> is 00:14:38.329 --> 00:14:38.339 align:start position:0% purple the idea of the reach language is 00:14:38.339 --> 00:14:40.729 align:start position:0% purple the idea of the reach language is that<00:14:38.610> you<00:14:38.730> switch<00:14:39.089> between<00:14:39.470> local<00:14:40.470> blocks 00:14:40.729 --> 00:14:40.739 align:start position:0% that you switch between local blocks 00:14:40.739 --> 00:14:43.280 align:start position:0% that you switch between local blocks where<00:14:41.429> a<00:14:41.459> particular<00:14:41.850> agent<00:14:42.329> or<00:14:42.569> many<00:14:42.929> agents 00:14:43.280 --> 00:14:43.290 align:start position:0% where a particular agent or many agents 00:14:43.290 --> 00:14:45.699 align:start position:0% where a particular agent or many agents are<00:14:43.470> simultaneously<00:14:44.129> doing<00:14:44.369> things<00:14:44.670> and<00:14:44.910> then 00:14:45.699 --> 00:14:45.709 align:start position:0% are simultaneously doing things and then 00:14:45.709 --> 00:14:48.379 align:start position:0% are simultaneously doing things and then synchronization<00:14:46.709> or<00:14:46.889> consensus<00:14:47.519> works<00:14:47.759> and 00:14:48.379 --> 00:14:48.389 align:start position:0% synchronization or consensus works and 00:14:48.389 --> 00:14:50.479 align:start position:0% synchronization or consensus works and in<00:14:48.600> those<00:14:48.720> consensus<00:14:49.259> works<00:14:49.499> all<00:14:50.129> of<00:14:50.189> the 00:14:50.479 --> 00:14:50.489 align:start position:0% in those consensus works all of the 00:14:50.489 --> 00:14:52.280 align:start position:0% in those consensus works all of the parties<00:14:50.850> are<00:14:51.029> doing<00:14:51.269> the<00:14:51.389> same<00:14:51.660> thing<00:14:51.899> and 00:14:52.280 --> 00:14:52.290 align:start position:0% parties are doing the same thing and 00:14:52.290 --> 00:14:55.960 align:start position:0% parties are doing the same thing and they<00:14:52.709> agreed<00:14:53.189> on<00:14:53.489> all<00:14:53.970> the<00:14:54.209> information<00:14:54.480> of 00:14:55.960 --> 00:14:55.970 align:start position:0% they agreed on all the information of 00:14:55.970 --> 00:14:58.879 align:start position:0% they agreed on all the information of let's<00:14:56.970> do<00:14:57.149> an<00:14:57.569> actually<00:14:57.929> interesting<00:14:58.470> example 00:14:58.879 --> 00:14:58.889 align:start position:0% let's do an actually interesting example 00:14:58.889 --> 00:15:01.189 align:start position:0% let's do an actually interesting example so<00:14:59.579> after<00:14:59.939> the<00:15:00.089> child<00:15:00.360> has<00:15:00.720> joined<00:15:01.049> the 00:15:01.189 --> 00:15:01.199 align:start position:0% so after the child has joined the 00:15:01.199 --> 00:15:03.350 align:start position:0% so after the child has joined the protocol<00:15:01.559> we<00:15:01.709> now<00:15:01.829> want<00:15:02.160> the<00:15:02.399> parent<00:15:02.759> table<00:15:02.850> so 00:15:03.350 --> 00:15:03.360 align:start position:0% protocol we now want the parent table so 00:15:03.360 --> 00:15:06.410 align:start position:0% protocol we now want the parent table so a<00:15:03.389> parent<00:15:03.989> table<00:15:04.529> only<00:15:05.059> so<00:15:06.059> this<00:15:06.149> is<00:15:06.269> something 00:15:06.410 --> 00:15:06.420 align:start position:0% a parent table only so this is something 00:15:06.420 --> 00:15:08.600 align:start position:0% a parent table only so this is something that<00:15:06.569> only<00:15:06.779> the<00:15:06.959> parent<00:15:07.379> they<00:15:07.470> do<00:15:07.589> now<00:15:08.339> what<00:15:08.549> do 00:15:08.600 --> 00:15:08.610 align:start position:0% that only the parent they do now what do 00:15:08.610 --> 00:15:09.559 align:start position:0% that only the parent they do now what do we<00:15:08.699> want<00:15:08.730> them<00:15:08.970> to<00:15:08.999> do<00:15:09.149> we're<00:15:09.299> going<00:15:09.389> to<00:15:09.480> have 00:15:09.559 --> 00:15:09.569 align:start position:0% we want them to do we're going to have 00:15:09.569 --> 00:15:11.569 align:start position:0% we want them to do we're going to have them<00:15:09.720> run<00:15:09.959> a<00:15:09.989> function<00:15:10.259> and<00:15:10.860> so<00:15:11.009> we'll<00:15:11.160> specify 00:15:11.569 --> 00:15:11.579 align:start position:0% them run a function and so we'll specify 00:15:11.579 --> 00:15:16.549 align:start position:0% them run a function and so we'll specify that<00:15:11.999> as<00:15:12.499> a<00:15:13.499> function<00:15:14.489> of<00:15:14.549> narrators<00:15:15.059> and<00:15:15.559> what 00:15:16.549 --> 00:15:16.559 align:start position:0% that as a function of narrators and what 00:15:16.559 --> 00:15:18.739 align:start position:0% that as a function of narrators and what they'll<00:15:16.709> do<00:15:16.860> is<00:15:17.100> they'll<00:15:17.369> compute<00:15:17.970> what<00:15:18.629> the 00:15:18.739 --> 00:15:18.749 align:start position:0% they'll do is they'll compute what the 00:15:18.749 --> 00:15:21.249 align:start position:0% they'll do is they'll compute what the allowance<00:15:19.259> that<00:15:19.319> we're<00:15:19.529> going<00:15:19.649> to<00:15:19.709> give<00:15:19.860> us 00:15:21.249 --> 00:15:21.259 align:start position:0% allowance that we're going to give us 00:15:21.259 --> 00:15:27.079 align:start position:0% allowance that we're going to give us now<00:15:22.699> notice<00:15:23.699> that<00:15:24.920> this<00:15:25.920> is<00:15:26.129> a<00:15:26.160> circumstance 00:15:27.079 --> 00:15:27.089 align:start position:0% now notice that this is a circumstance 00:15:27.089 --> 00:15:29.210 align:start position:0% now notice that this is a circumstance where<00:15:27.389> it<00:15:28.019> makes<00:15:28.230> sense<00:15:28.350> that<00:15:28.559> the<00:15:28.829> at<00:15:29.040> this 00:15:29.210 --> 00:15:29.220 align:start position:0% where it makes sense that the at this 00:15:29.220 --> 00:15:31.759 align:start position:0% where it makes sense that the at this point<00:15:29.459> in<00:15:29.579> the<00:15:29.669> parole<00:15:30.119> the<00:15:30.569> parent<00:15:30.989> is<00:15:31.379> always 00:15:31.759 --> 00:15:31.769 align:start position:0% point in the parole the parent is always 00:15:31.769 --> 00:15:34.039 align:start position:0% point in the parole the parent is always going<00:15:31.919> to<00:15:32.009> decide<00:15:32.429> what<00:15:32.699> the<00:15:32.790> allowances<00:15:33.269> but 00:15:34.039 --> 00:15:34.049 align:start position:0% going to decide what the allowances but 00:15:34.049 --> 00:15:36.559 align:start position:0% going to decide what the allowances but in<00:15:34.889> our<00:15:35.069> reach<00:15:35.309> program<00:15:35.699> like<00:15:35.910> how<00:15:36.149> do<00:15:36.209> we<00:15:36.360> know 00:15:36.559 --> 00:15:36.569 align:start position:0% in our reach program like how do we know 00:15:36.569 --> 00:15:39.169 align:start position:0% in our reach program like how do we know what<00:15:37.290> you<00:15:37.739> do<00:15:38.369> clear<00:15:38.549> parent<00:15:38.850> are<00:15:38.999> going<00:15:39.119> to 00:15:39.169 --> 00:15:39.179 align:start position:0% what you do clear parent are going to 00:15:39.179 --> 00:15:41.479 align:start position:0% what you do clear parent are going to give<00:15:39.389> to<00:15:39.959> Sally<00:15:40.169> before<00:15:40.559> she<00:15:40.649> goes<00:15:40.769> on<00:15:41.040> her<00:15:41.249> you 00:15:41.479 --> 00:15:41.489 align:start position:0% give to Sally before she goes on her you 00:15:41.489 --> 00:15:42.559 align:start position:0% give to Sally before she goes on her you know<00:15:41.610> it's<00:15:41.879> big<00:15:42.209> trouble 00:15:42.559 --> 00:15:42.569 align:start position:0% know it's big trouble 00:15:42.569 --> 00:15:45.769 align:start position:0% know it's big trouble how<00:15:43.199> do<00:15:43.259> you<00:15:43.379> know<00:15:44.149> well<00:15:45.149> there's<00:15:45.419> two<00:15:45.600> ways 00:15:45.769 --> 00:15:45.779 align:start position:0% how do you know well there's two ways 00:15:45.779 --> 00:15:47.809 align:start position:0% how do you know well there's two ways that<00:15:45.899> we<00:15:45.989> can<00:15:46.139> do<00:15:46.230> this<00:15:46.410> the<00:15:47.100> first<00:15:47.309> thing<00:15:47.549> is 00:15:47.809 --> 00:15:47.819 align:start position:0% that we can do this the first thing is 00:15:47.819 --> 00:15:50.030 align:start position:0% that we can do this the first thing is that<00:15:48.059> notice<00:15:48.209> I'm<00:15:48.449> here<00:15:48.689> when<00:15:49.139> I<00:15:49.169> wrote<00:15:49.439> when<00:15:49.980> I 00:15:50.030 --> 00:15:50.040 align:start position:0% that notice I'm here when I wrote when I 00:15:50.040 --> 00:15:52.549 align:start position:0% that notice I'm here when I wrote when I defined<00:15:50.489> the<00:15:50.669> parent<00:15:50.999> I<00:15:51.299> said<00:15:51.779> and<00:15:52.049> this<00:15:52.199> empty 00:15:52.549 --> 00:15:52.559 align:start position:0% defined the parent I said and this empty 00:15:52.559 --> 00:15:53.479 align:start position:0% defined the parent I said and this empty object<00:15:52.589> right<00:15:53.069> here 00:15:53.479 --> 00:15:53.489 align:start position:0% object right here 00:15:53.489 --> 00:15:56.660 align:start position:0% object right here so<00:15:53.790> in<00:15:53.970> this<00:15:54.149> spot<00:15:54.449> you<00:15:54.749> can<00:15:55.049> write<00:15:55.259> and 00:15:56.660 --> 00:15:56.670 align:start position:0% so in this spot you can write and 00:15:56.670 --> 00:15:58.190 align:start position:0% so in this spot you can write and at<00:15:56.880> every<00:15:57.149> print<00:15:57.360> that<00:15:57.510> that<00:15:57.690> participant 00:15:58.190 --> 00:15:58.200 align:start position:0% at every print that that participant 00:15:58.200 --> 00:15:59.509 align:start position:0% at every print that that participant starts<00:15:58.620> the<00:15:58.950> Protomen 00:15:59.509 --> 00:15:59.519 align:start position:0% starts the Protomen 00:15:59.519 --> 00:16:02.810 align:start position:0% starts the Protomen so<00:16:00.029> we<00:16:00.120> could<00:16:00.360> add<00:16:00.810> in<00:16:01.230> here<00:16:01.580> knowledge<00:16:02.580> what 00:16:02.810 --> 00:16:02.820 align:start position:0% so we could add in here knowledge what 00:16:02.820 --> 00:16:07.910 align:start position:0% so we could add in here knowledge what the<00:16:02.940> initial<00:16:04.459> step<00:16:05.459> will<00:16:05.640> do<00:16:05.850> though<00:16:06.830> is<00:16:07.830> that 00:16:07.910 --> 00:16:07.920 align:start position:0% the initial step will do though is that 00:16:07.920 --> 00:16:12.230 align:start position:0% the initial step will do though is that we<00:16:08.399> will<00:16:09.380> interact<00:16:10.380> with<00:16:10.769> the<00:16:11.519> front<00:16:11.820> end<00:16:11.970> so 00:16:12.230 --> 00:16:12.240 align:start position:0% we will interact with the front end so 00:16:12.240 --> 00:16:16.240 align:start position:0% we will interact with the front end so we<00:16:12.959> interact<00:16:13.709> this<00:16:14.190> is<00:16:14.399> a<00:16:14.640> special<00:16:15.600> object 00:16:16.240 --> 00:16:16.250 align:start position:0% we interact this is a special object 00:16:16.250 --> 00:16:18.230 align:start position:0% we interact this is a special object inside<00:16:17.250> of<00:16:17.370> the<00:16:17.490> reach<00:16:17.610> language<00:16:18.000> that 00:16:18.230 --> 00:16:18.240 align:start position:0% inside of the reach language that 00:16:18.240 --> 00:16:20.690 align:start position:0% inside of the reach language that represents<00:16:18.959> the<00:16:19.470> client<00:16:20.010> it<00:16:20.399> will<00:16:20.519> ultimately 00:16:20.690 --> 00:16:20.700 align:start position:0% represents the client it will ultimately 00:16:20.700 --> 00:16:23.509 align:start position:0% represents the client it will ultimately run<00:16:21.329> the<00:16:21.810> parent<00:16:22.170> part<00:16:22.380> of<00:16:22.440> the<00:16:22.500> world<00:16:22.709> so 00:16:23.509 --> 00:16:23.519 align:start position:0% run the parent part of the world so 00:16:23.519 --> 00:16:24.889 align:start position:0% run the parent part of the world so we're<00:16:23.610> going<00:16:23.700> to<00:16:23.760> take<00:16:23.910> that<00:16:24.029> object<00:16:24.269> and 00:16:24.889 --> 00:16:24.899 align:start position:0% we're going to take that object and 00:16:24.899 --> 00:16:28.550 align:start position:0% we're going to take that object and we're<00:16:24.990> going<00:16:25.110> to<00:16:25.140> call<00:16:25.440> allowance<00:16:26.399> on<00:16:26.550> it<00:16:27.560> now 00:16:28.550 --> 00:16:28.560 align:start position:0% we're going to call allowance on it now 00:16:28.560 --> 00:16:30.500 align:start position:0% we're going to call allowance on it now let's<00:16:28.740> convert<00:16:28.950> our<00:16:29.190> net<00:16:29.310> value<00:16:29.640> and<00:16:29.910> we<00:16:30.390> need 00:16:30.500 --> 00:16:30.510 align:start position:0% let's convert our net value and we need 00:16:30.510 --> 00:16:33.230 align:start position:0% let's convert our net value and we need to<00:16:30.600> assert<00:16:30.990> that<00:16:31.290> that<00:16:31.560> value<00:16:31.800> is<00:16:32.250> going<00:16:32.880> to<00:16:33.089> be 00:16:33.230 --> 00:16:33.240 align:start position:0% to assert that that value is going to be 00:16:33.240 --> 00:16:40.790 align:start position:0% to assert that that value is going to be an<00:16:33.450> integer<00:16:38.000> now<00:16:39.000> this<00:16:39.600> value<00:16:39.839> right<00:16:40.110> here<00:16:40.170> we 00:16:40.790 --> 00:16:40.800 align:start position:0% an integer now this value right here we 00:16:40.800 --> 00:16:44.120 align:start position:0% an integer now this value right here we want<00:16:41.070> to<00:16:41.250> eventually<00:16:41.490> provide<00:16:42.300> it<00:16:42.980> so<00:16:43.980> we'll 00:16:44.120 --> 00:16:44.130 align:start position:0% want to eventually provide it so we'll 00:16:44.130 --> 00:16:47.509 align:start position:0% want to eventually provide it so we'll go<00:16:44.250> next<00:16:44.810> and<00:16:45.810> we'll<00:16:45.959> say<00:16:46.110> parent<00:16:46.529> not<00:16:47.010> publish 00:16:47.509 --> 00:16:47.519 align:start position:0% go next and we'll say parent not publish 00:16:47.519 --> 00:16:50.660 align:start position:0% go next and we'll say parent not publish the<00:16:48.180> allowance<00:16:49.220> so<00:16:50.220> we're<00:16:50.339> going<00:16:50.430> to<00:16:50.490> publish 00:16:50.660 --> 00:16:50.670 align:start position:0% the allowance so we're going to publish 00:16:50.670 --> 00:16:52.970 align:start position:0% the allowance so we're going to publish to<00:16:50.850> the<00:16:51.060> rest<00:16:51.240> of<00:16:51.329> the<00:16:51.420> world<00:16:51.600> that<00:16:52.500> the 00:16:52.970 --> 00:16:52.980 align:start position:0% to the rest of the world that the 00:16:52.980 --> 00:16:54.650 align:start position:0% to the rest of the world that the allowance<00:16:53.399> that<00:16:53.459> that<00:16:53.880> child<00:16:54.120> has<00:16:54.240> access<00:16:54.480> to 00:16:54.650 --> 00:16:54.660 align:start position:0% allowance that that child has access to 00:16:54.660 --> 00:16:57.680 align:start position:0% allowance that that child has access to is<00:16:55.079> this<00:16:55.290> number<00:16:55.850> now<00:16:56.850> unfortunately<00:16:57.510> if<00:16:57.660> we 00:16:57.680 --> 00:16:57.690 align:start position:0% is this number now unfortunately if we 00:16:57.690 --> 00:16:59.810 align:start position:0% is this number now unfortunately if we try<00:16:58.019> to<00:16:58.079> compile<00:16:58.470> the<00:16:58.620> program<00:16:58.800> right<00:16:59.130> now<00:16:59.160> it 00:16:59.810 --> 00:16:59.820 align:start position:0% try to compile the program right now it 00:16:59.820 --> 00:17:02.269 align:start position:0% try to compile the program right now it is<00:17:00.000> going<00:17:00.180> to<00:17:00.329> fail<00:17:00.560> and<00:17:01.560> it's<00:17:01.829> not<00:17:01.980> an<00:17:02.040> ability 00:17:02.269 --> 00:17:02.279 align:start position:0% is going to fail and it's not an ability 00:17:02.279 --> 00:17:04.069 align:start position:0% is going to fail and it's not an ability because<00:17:02.579> I<00:17:02.640> have<00:17:02.760> this<00:17:02.880> time<00:17:03.089> here<00:17:03.270> it's<00:17:03.899> got<00:17:04.050> a 00:17:04.069 --> 00:17:04.079 align:start position:0% because I have this time here it's got a 00:17:04.079 --> 00:17:06.470 align:start position:0% because I have this time here it's got a billion<00:17:04.260> records<00:17:04.740> that<00:17:05.150> the<00:17:06.150> reason<00:17:06.390> it's 00:17:06.470 --> 00:17:06.480 align:start position:0% billion records that the reason it's 00:17:06.480 --> 00:17:08.809 align:start position:0% billion records that the reason it's going<00:17:06.569> to<00:17:06.689> fail<00:17:06.870> is<00:17:07.169> that<00:17:07.199> this<00:17:07.530> program<00:17:08.010> fails 00:17:08.809 --> 00:17:08.819 align:start position:0% going to fail is that this program fails 00:17:08.819 --> 00:17:11.750 align:start position:0% going to fail is that this program fails to<00:17:09.179> satisfy<00:17:09.870> the<00:17:10.260> information<00:17:11.040> flows<00:17:11.579> of 00:17:11.750 --> 00:17:11.760 align:start position:0% to satisfy the information flows of 00:17:11.760 --> 00:17:15.230 align:start position:0% to satisfy the information flows of dreams<00:17:12.000> the<00:17:12.589> reason<00:17:13.589> why<00:17:13.740> is<00:17:14.309> that<00:17:14.400> all<00:17:14.910> the 00:17:15.230 --> 00:17:15.240 align:start position:0% dreams the reason why is that all the 00:17:15.240 --> 00:17:16.610 align:start position:0% dreams the reason why is that all the information<00:17:15.329> that<00:17:15.720> comes<00:17:15.839> from<00:17:16.110> the<00:17:16.230> client 00:17:16.610 --> 00:17:16.620 align:start position:0% information that comes from the client 00:17:16.620 --> 00:17:19.250 align:start position:0% information that comes from the client comes<00:17:17.250> from<00:17:17.429> the<00:17:17.520> front<00:17:17.699> end<00:17:17.939> is<00:17:18.480> assumed<00:17:19.050> to 00:17:19.250 --> 00:17:19.260 align:start position:0% comes from the front end is assumed to 00:17:19.260 --> 00:17:20.510 align:start position:0% comes from the front end is assumed to be<00:17:19.290> standard<00:17:19.800> information 00:17:20.510 --> 00:17:20.520 align:start position:0% be standard information 00:17:20.520 --> 00:17:21.460 align:start position:0% be standard information it<00:17:20.669> must<00:17:20.850> be<00:17:21.000> it 00:17:21.460 --> 00:17:21.470 align:start position:0% it must be it 00:17:21.470 --> 00:17:24.850 align:start position:0% it must be it classified<00:17:22.730> so<00:17:23.689> we'll<00:17:23.809> do<00:17:23.929> we'll<00:17:24.169> call<00:17:24.409> do<00:17:24.770> you 00:17:24.850 --> 00:17:24.860 align:start position:0% classified so we'll do we'll call do you 00:17:24.860 --> 00:17:33.970 align:start position:0% classified so we'll do we'll call do you classify<00:17:24.980> MS<00:17:29.140> and<00:17:32.110> another<00:17:33.110> Declassified<00:17:33.770> in 00:17:33.970 --> 00:17:33.980 align:start position:0% classify MS and another Declassified in 00:17:33.980 --> 00:17:38.830 align:start position:0% classify MS and another Declassified in we're<00:17:34.130> allowed<00:17:34.400> to<00:17:34.429> watch<00:17:34.700> it<00:17:34.730> okay<00:17:36.730> now<00:17:37.840> the 00:17:38.830 --> 00:17:38.840 align:start position:0% we're allowed to watch it okay now the 00:17:38.840 --> 00:17:40.120 align:start position:0% we're allowed to watch it okay now the next<00:17:38.870> thing<00:17:39.440> that<00:17:39.500> I<00:17:39.620> want<00:17:39.770> to<00:17:39.860> talk<00:17:39.980> to<00:17:40.039> you 00:17:40.120 --> 00:17:40.130 align:start position:0% next thing that I want to talk to you 00:17:40.130 --> 00:17:42.610 align:start position:0% next thing that I want to talk to you about<00:17:40.220> is<00:17:40.909> how<00:17:41.360> every<00:17:42.020> time<00:17:42.049> we<00:17:42.409> make<00:17:42.590> a 00:17:42.610 --> 00:17:42.620 align:start position:0% about is how every time we make a 00:17:42.620 --> 00:17:46.980 align:start position:0% about is how every time we make a publication<00:17:43.539> we<00:17:44.539> can<00:17:44.870> combine<00:17:45.380> that<00:17:45.559> with<00:17:45.909> a 00:17:46.980 --> 00:17:46.990 align:start position:0% publication we can combine that with a 00:17:46.990 --> 00:17:52.080 align:start position:0% publication we can combine that with a unit<00:17:47.990> of<00:17:48.110> value<00:17:48.230> that<00:17:48.620> we<00:17:48.770> transfer<00:17:49.070> it<00:17:49.460> to<00:17:50.020> so 00:17:52.080 --> 00:17:52.090 align:start position:0% unit of value that we transfer it to so 00:17:52.090 --> 00:17:55.539 align:start position:0% unit of value that we transfer it to so so<00:17:53.090> will<00:17:53.210> actually<00:17:53.600> pay<00:17:53.750> the<00:17:54.020> allowance<00:17:54.549> and 00:17:55.539 --> 00:17:55.549 align:start position:0% so will actually pay the allowance and 00:17:55.549 --> 00:18:00.159 align:start position:0% so will actually pay the allowance and will<00:17:56.480> write<00:17:56.630> down<00:17:56.750> the<00:17:56.809> time<00:17:57.110> code<00:17:58.720> so<00:17:59.720> every 00:18:00.159 --> 00:18:00.169 align:start position:0% will write down the time code so every 00:18:00.169 --> 00:18:02.409 align:start position:0% will write down the time code so every program<00:18:00.590> every<00:18:00.770> interaction<00:18:01.460> on<00:18:02.059> the<00:18:02.210> chain 00:18:02.409 --> 00:18:02.419 align:start position:0% program every interaction on the chain 00:18:02.419 --> 00:18:05.830 align:start position:0% program every interaction on the chain must<00:18:03.260> be<00:18:03.669> accompanied<00:18:04.669> by<00:18:04.700> what<00:18:05.390> would<00:18:05.539> happen 00:18:05.830 --> 00:18:05.840 align:start position:0% must be accompanied by what would happen 00:18:05.840 --> 00:18:07.899 align:start position:0% must be accompanied by what would happen if<00:18:05.960> there's<00:18:06.140> a<00:18:06.230> timeout<00:18:06.500> we<00:18:07.429> refer<00:18:07.669> to<00:18:07.700> this 00:18:07.899 --> 00:18:07.909 align:start position:0% if there's a timeout we refer to this 00:18:07.909 --> 00:18:11.680 align:start position:0% if there's a timeout we refer to this property<00:18:08.270> as<00:18:08.799> kill<00:18:09.799> safety<00:18:10.309> the<00:18:11.059> idea<00:18:11.299> is<00:18:11.539> that 00:18:11.680 --> 00:18:11.690 align:start position:0% property as kill safety the idea is that 00:18:11.690 --> 00:18:13.930 align:start position:0% property as kill safety the idea is that your<00:18:11.990> program<00:18:12.350> has<00:18:12.380> to<00:18:12.710> be<00:18:12.740> safe<00:18:13.159> with<00:18:13.520> respect 00:18:13.930 --> 00:18:13.940 align:start position:0% your program has to be safe with respect 00:18:13.940 --> 00:18:18.070 align:start position:0% your program has to be safe with respect to<00:18:14.120> any<00:18:14.390> participant<00:18:15.080> refusing<00:18:15.890> to<00:18:16.570> engage<00:18:17.570> in 00:18:18.070 --> 00:18:18.080 align:start position:0% to any participant refusing to engage in 00:18:18.080 --> 00:18:19.419 align:start position:0% to any participant refusing to engage in the<00:18:18.140> protocol<00:18:18.500> at<00:18:18.650> every<00:18:18.890> point<00:18:19.100> going 00:18:19.419 --> 00:18:19.429 align:start position:0% the protocol at every point going 00:18:19.429 --> 00:18:21.460 align:start position:0% the protocol at every point going forward<00:18:19.549> so<00:18:20.510> in<00:18:20.690> this<00:18:20.780> case<00:18:21.020> what<00:18:21.350> we're 00:18:21.460 --> 00:18:21.470 align:start position:0% forward so in this case what we're 00:18:21.470 --> 00:18:23.409 align:start position:0% forward so in this case what we're saying<00:18:21.650> with<00:18:21.890> this<00:18:22.039> time<00:18:22.250> of<00:18:22.370> luck<00:18:22.549> if<00:18:23.210> we're 00:18:23.409 --> 00:18:23.419 align:start position:0% saying with this time of luck if we're 00:18:23.419 --> 00:18:26.110 align:start position:0% saying with this time of luck if we're saying<00:18:23.600> what<00:18:24.500> if<00:18:24.710> the<00:18:24.740> parent<00:18:25.250> never<00:18:25.669> did<00:18:26.000> this 00:18:26.110 --> 00:18:26.120 align:start position:0% saying what if the parent never did this 00:18:26.120 --> 00:18:28.899 align:start position:0% saying what if the parent never did this problem<00:18:26.530> what<00:18:27.530> should<00:18:27.559> happen<00:18:27.830> now<00:18:28.549> do<00:18:28.610> these 00:18:28.899 --> 00:18:28.909 align:start position:0% problem what should happen now do these 00:18:28.909 --> 00:18:30.430 align:start position:0% problem what should happen now do these early<00:18:29.270> stage<00:18:29.480> of<00:18:29.630> the<00:18:29.750> protocol<00:18:30.169> there's 00:18:30.430 --> 00:18:30.440 align:start position:0% early stage of the protocol there's 00:18:30.440 --> 00:18:32.140 align:start position:0% early stage of the protocol there's really<00:18:30.590> nothing<00:18:30.919> interesting<00:18:31.460> to<00:18:31.490> say<00:18:31.580> that's 00:18:32.140 --> 00:18:32.150 align:start position:0% really nothing interesting to say that's 00:18:32.150 --> 00:18:36.010 align:start position:0% really nothing interesting to say that's why<00:18:32.270> they<00:18:32.390> just<00:18:32.570> had<00:18:32.950> but<00:18:33.950> in<00:18:34.100> principle<00:18:34.840> as<00:18:35.840> we 00:18:36.010 --> 00:18:36.020 align:start position:0% why they just had but in principle as we 00:18:36.020 --> 00:18:37.149 align:start position:0% why they just had but in principle as we go<00:18:36.169> forward<00:18:36.409> there's<00:18:36.679> going<00:18:36.799> to<00:18:36.860> be<00:18:36.919> more 00:18:37.149 --> 00:18:37.159 align:start position:0% go forward there's going to be more 00:18:37.159 --> 00:18:38.470 align:start position:0% go forward there's going to be more interesting<00:18:37.669> interrupts<00:18:38.000> they're<00:18:38.270> going<00:18:38.419> to 00:18:38.470 --> 00:18:38.480 align:start position:0% interesting interrupts they're going to 00:18:38.480 --> 00:18:43.230 align:start position:0% interesting interrupts they're going to happen 00:18:43.230 --> 00:18:43.240 align:start position:0% 00:18:43.240 --> 00:18:45.840 align:start position:0% all<00:18:43.690> right<00:18:43.840> so<00:18:44.649> now<00:18:44.799> at<00:18:44.980> this<00:18:45.100> point<00:18:45.309> you're 00:18:45.840 --> 00:18:45.850 align:start position:0% all right so now at this point you're 00:18:45.850 --> 00:18:50.430 align:start position:0% all right so now at this point you're now<00:18:46.059> inside<00:18:46.840> of<00:18:47.620> the<00:18:48.070> contract<00:18:49.409> the<00:18:50.409> contract 00:18:50.430 --> 00:18:50.440 align:start position:0% now inside of the contract the contract 00:18:50.440 --> 00:18:53.669 align:start position:0% now inside of the contract the contract has<00:18:51.100> access<00:18:51.669> to<00:18:51.940> the<00:18:52.299> allowance<00:18:52.750> and<00:18:52.990> you<00:18:53.559> need 00:18:53.669 --> 00:18:53.679 align:start position:0% has access to the allowance and you need 00:18:53.679 --> 00:18:55.380 align:start position:0% has access to the allowance and you need to<00:18:53.799> go<00:18:53.950> forward<00:18:54.279> the<00:18:54.760> thing<00:18:55.000> that<00:18:55.120> we<00:18:55.179> want<00:18:55.360> to 00:18:55.380 --> 00:18:55.390 align:start position:0% to go forward the thing that we want to 00:18:55.390 --> 00:18:57.600 align:start position:0% to go forward the thing that we want to do<00:18:55.570> going<00:18:55.929> forward<00:18:56.080> is<00:18:57.039> what<00:18:57.279> to<00:18:57.399> have<00:18:57.580> a 00:18:57.600 --> 00:18:57.610 align:start position:0% do going forward is what to have a 00:18:57.610 --> 00:19:00.090 align:start position:0% do going forward is what to have a little<00:18:57.940> well<00:18:58.289> and<00:18:59.289> this<00:18:59.470> little<00:18:59.679> while<00:18:59.890> loop 00:19:00.090 --> 00:19:00.100 align:start position:0% little well and this little while loop 00:19:00.100 --> 00:19:02.909 align:start position:0% little well and this little while loop is<00:19:00.460> going<00:19:00.520> to<00:19:00.850> repeatedly<00:19:01.450> allow<00:19:02.409> the<00:19:02.470> child 00:19:02.909 --> 00:19:02.919 align:start position:0% is going to repeatedly allow the child 00:19:02.919 --> 00:19:11.850 align:start position:0% is going to repeatedly allow the child to<00:19:03.159> ask<00:19:03.640> a<00:19:03.850> buzzer<00:19:06.450> so<00:19:07.450> we'll<00:19:07.570> write<00:19:07.690> about 00:19:11.850 --> 00:19:11.860 align:start position:0% 00:19:11.860 --> 00:19:16.539 align:start position:0% now<00:19:14.200> what<00:19:15.200> is<00:19:15.289> the<00:19:15.440> condition<00:19:15.620> that's<00:19:16.340> going 00:19:16.539 --> 00:19:16.549 align:start position:0% now what is the condition that's going 00:19:16.549 --> 00:19:18.490 align:start position:0% now what is the condition that's going to<00:19:16.639> tell<00:19:16.820> us<00:19:16.850> that<00:19:17.299> we're<00:19:17.419> done<00:19:17.629> well<00:19:18.379> the 00:19:18.490 --> 00:19:18.500 align:start position:0% to tell us that we're done well the 00:19:18.500 --> 00:19:19.509 align:start position:0% to tell us that we're done well the condition<00:19:18.830> was<00:19:18.950> going<00:19:19.129> to<00:19:19.190> tell<00:19:19.309> us<00:19:19.340> that 00:19:19.509 --> 00:19:19.519 align:start position:0% condition was going to tell us that 00:19:19.519 --> 00:19:23.619 align:start position:0% condition was going to tell us that we're<00:19:19.669> done<00:19:19.789> is<00:19:20.450> that<00:19:20.840> the<00:19:21.830> balance<00:19:22.309> is<00:19:22.629> going 00:19:23.619 --> 00:19:23.629 align:start position:0% we're done is that the balance is going 00:19:23.629 --> 00:19:25.869 align:start position:0% we're done is that the balance is going to<00:19:23.750> be<00:19:23.840> zero<00:19:24.139> when<00:19:24.860> the<00:19:25.009> balance<00:19:25.340> is<00:19:25.490> empty 00:19:25.869 --> 00:19:25.879 align:start position:0% to be zero when the balance is empty 00:19:25.879 --> 00:19:29.110 align:start position:0% to be zero when the balance is empty then<00:19:26.629> the<00:19:27.080> program<00:19:27.500> will<00:19:27.529> be<00:19:27.710> over<00:19:27.980> now<00:19:28.370> Alice 00:19:29.110 --> 00:19:29.120 align:start position:0% then the program will be over now Alice 00:19:29.120 --> 00:19:31.389 align:start position:0% then the program will be over now Alice Bob<00:19:29.330> something<00:19:29.690> like<00:19:29.809> special<00:19:30.350> variable<00:19:31.159> that 00:19:31.389 --> 00:19:31.399 align:start position:0% Bob something like special variable that 00:19:31.399 --> 00:19:32.619 align:start position:0% Bob something like special variable that we're<00:19:31.580> not<00:19:31.759> going<00:19:31.909> to<00:19:31.970> we're<00:19:32.240> going<00:19:32.419> to<00:19:32.509> keep 00:19:32.619 --> 00:19:32.629 align:start position:0% we're not going to we're going to keep 00:19:32.629 --> 00:19:35.019 align:start position:0% we're not going to we're going to keep track<00:19:32.870> of<00:19:32.990> the<00:19:33.080> balances<00:19:33.590> okay<00:19:34.490> so<00:19:34.940> we're 00:19:35.019 --> 00:19:35.029 align:start position:0% track of the balances okay so we're 00:19:35.029 --> 00:19:36.399 align:start position:0% track of the balances okay so we're gonna<00:19:35.120> say<00:19:35.240> that<00:19:35.269> well<00:19:35.570> the<00:19:35.779> balance<00:19:36.110> isn't 00:19:36.399 --> 00:19:36.409 align:start position:0% gonna say that well the balance isn't 00:19:36.409 --> 00:19:40.149 align:start position:0% gonna say that well the balance isn't zero<00:19:36.620> continue<00:19:37.399> running<00:19:37.580> this<00:19:37.820> part<00:19:38.029> of<00:19:39.159> Seoul 00:19:40.149 --> 00:19:40.159 align:start position:0% zero continue running this part of Seoul 00:19:40.159 --> 00:19:42.240 align:start position:0% zero continue running this part of Seoul define<00:19:40.460> a<00:19:40.490> new<00:19:40.669> variable<00:19:40.730> call<00:19:41.690> the<00:19:41.840> balance 00:19:42.240 --> 00:19:42.250 align:start position:0% define a new variable call the balance 00:19:42.250 --> 00:19:44.980 align:start position:0% define a new variable call the balance it's<00:19:43.250> going<00:19:43.429> to<00:19:43.490> be<00:19:43.580> equal<00:19:44.059> to<00:19:44.360> the<00:19:44.600> allowance 00:19:44.980 --> 00:19:44.990 align:start position:0% it's going to be equal to the allowance 00:19:44.990 --> 00:19:51.519 align:start position:0% it's going to be equal to the allowance no<00:19:49.870> just<00:19:50.870> so<00:19:50.929> that<00:19:51.049> we<00:19:51.139> have<00:19:51.169> something 00:19:51.519 --> 00:19:51.529 align:start position:0% no just so that we have something 00:19:51.529 --> 00:19:54.879 align:start position:0% no just so that we have something interesting<00:19:51.679> to<00:19:51.950> return<00:19:52.480> to<00:19:53.480> do<00:19:53.600> is<00:19:54.440> we're 00:19:54.879 --> 00:19:54.889 align:start position:0% interesting to return to do is we're 00:19:54.889 --> 00:19:56.470 align:start position:0% interesting to return to do is we're going<00:19:54.919> to<00:19:55.070> keep<00:19:55.220> track<00:19:55.549> of<00:19:56.059> how<00:19:56.269> many<00:19:56.330> times 00:19:56.470 --> 00:19:56.480 align:start position:0% going to keep track of how many times 00:19:56.480 --> 00:20:00.340 align:start position:0% going to keep track of how many times you<00:19:56.870> said<00:19:57.049> yes<00:19:57.289> and<00:19:58.600> how<00:19:59.600> many<00:19:59.720> times<00:19:59.990> you<00:20:00.200> said 00:20:00.340 --> 00:20:00.350 align:start position:0% you said yes and how many times you said 00:20:00.350 --> 00:20:02.769 align:start position:0% you said yes and how many times you said no<00:20:00.549> running<00:20:01.549> the<00:20:01.759> program<00:20:02.059> so<00:20:02.330> how<00:20:02.419> many<00:20:02.480> times 00:20:02.769 --> 00:20:02.779 align:start position:0% no running the program so how many times 00:20:02.779 --> 00:20:04.810 align:start position:0% no running the program so how many times the<00:20:03.080> child<00:20:03.320> asks<00:20:03.679> for<00:20:03.769> money<00:20:03.919> and<00:20:04.250> the<00:20:04.460> parents 00:20:04.810 --> 00:20:04.820 align:start position:0% the child asks for money and the parents 00:20:04.820 --> 00:20:07.930 align:start position:0% the child asks for money and the parents that<00:20:04.909> way<00:20:06.100> we<00:20:07.100> don't<00:20:07.190> this<00:20:07.490> isn't<00:20:07.700> that 00:20:07.930 --> 00:20:07.940 align:start position:0% that way we don't this isn't that 00:20:07.940 --> 00:20:10.389 align:start position:0% that way we don't this isn't that important<00:20:08.629> you<00:20:08.720> just<00:20:08.950> keep<00:20:09.950> adding<00:20:10.100> something 00:20:10.389 --> 00:20:10.399 align:start position:0% important you just keep adding something 00:20:10.399 --> 00:20:12.159 align:start position:0% important you just keep adding something and<00:20:11.179> then<00:20:11.299> that's<00:20:11.480> the<00:20:11.570> information<00:20:12.049> that 00:20:12.159 --> 00:20:12.169 align:start position:0% and then that's the information that 00:20:12.169 --> 00:20:16.960 align:start position:0% and then that's the information that we're<00:20:12.289> going<00:20:12.350> to<00:20:12.440> return<00:20:12.769> at<00:20:13.070> the<00:20:13.159> end 00:20:16.960 --> 00:20:16.970 align:start position:0% 00:20:16.970 --> 00:20:20.830 align:start position:0% okay<00:20:17.799> now<00:20:18.799> there's<00:20:19.400> one<00:20:19.669> last<00:20:19.940> thing<00:20:20.150> that<00:20:20.570> we 00:20:20.830 --> 00:20:20.840 align:start position:0% okay now there's one last thing that we 00:20:20.840 --> 00:20:23.560 align:start position:0% okay now there's one last thing that we need<00:20:20.870> to<00:20:21.020> do<00:20:21.200> and<00:20:22.030> it's<00:20:23.030> actually<00:20:23.270> kind<00:20:23.390> of<00:20:23.480> a 00:20:23.560 --> 00:20:23.570 align:start position:0% need to do and it's actually kind of a 00:20:23.570 --> 00:20:26.890 align:start position:0% need to do and it's actually kind of a big<00:20:23.750> thing<00:20:25.240> when<00:20:26.240> you're<00:20:26.390> doing<00:20:26.480> formal 00:20:26.890 --> 00:20:26.900 align:start position:0% big thing when you're doing formal 00:20:26.900 --> 00:20:30.250 align:start position:0% big thing when you're doing formal verification<00:20:27.080> and<00:20:27.740> you<00:20:28.250> have<00:20:28.429> a<00:20:28.610> value<00:20:29.260> the 00:20:30.250 --> 00:20:30.260 align:start position:0% verification and you have a value the 00:20:30.260 --> 00:20:32.289 align:start position:0% verification and you have a value the while<00:20:30.440> loop<00:20:30.710> represents<00:20:31.700> a<00:20:31.850> point<00:20:32.120> in<00:20:32.240> your 00:20:32.289 --> 00:20:32.299 align:start position:0% while loop represents a point in your 00:20:32.299 --> 00:20:34.299 align:start position:0% while loop represents a point in your program<00:20:32.720> where<00:20:33.230> many<00:20:33.530> many<00:20:33.770> different<00:20:34.159> things 00:20:34.299 --> 00:20:34.309 align:start position:0% program where many many different things 00:20:34.309 --> 00:20:36.430 align:start position:0% program where many many different things to<00:20:34.549> cover<00:20:34.750> there's<00:20:35.750> an<00:20:35.870> addition<00:20:36.230> of<00:20:36.289> this 00:20:36.430 --> 00:20:36.440 align:start position:0% to cover there's an addition of this 00:20:36.440 --> 00:20:39.220 align:start position:0% to cover there's an addition of this program<00:20:36.830> that<00:20:36.950> runs<00:20:37.130> where<00:20:37.940> you<00:20:38.690> reach<00:20:38.990> this 00:20:39.220 --> 00:20:39.230 align:start position:0% program that runs where you reach this 00:20:39.230 --> 00:20:41.560 align:start position:0% program that runs where you reach this point<00:20:39.590> in<00:20:39.919> the<00:20:40.280> allowance<00:20:40.669> with<00:20:40.850> zero<00:20:41.150> and 00:20:41.560 --> 00:20:41.570 align:start position:0% point in the allowance with zero and 00:20:41.570 --> 00:20:43.750 align:start position:0% point in the allowance with zero and since<00:20:42.500> the<00:20:42.650> allowance<00:20:42.950> was<00:20:43.100> thrown<00:20:43.400> we<00:20:43.549> never 00:20:43.750 --> 00:20:43.760 align:start position:0% since the allowance was thrown we never 00:20:43.760 --> 00:20:45.279 align:start position:0% since the allowance was thrown we never execute<00:20:44.270> the<00:20:44.390> code<00:20:44.539> inside<00:20:44.840> of<00:20:44.960> here<00:20:45.110> and<00:20:45.140> we 00:20:45.279 --> 00:20:45.289 align:start position:0% execute the code inside of here and we 00:20:45.289 --> 00:20:47.770 align:start position:0% execute the code inside of here and we go<00:20:45.409> right<00:20:45.590> to<00:20:45.620> the<00:20:45.770> end<00:20:46.510> there's<00:20:47.510> another 00:20:47.770 --> 00:20:47.780 align:start position:0% go right to the end there's another 00:20:47.780 --> 00:20:49.480 align:start position:0% go right to the end there's another version<00:20:48.049> of<00:20:48.200> this<00:20:48.350> program<00:20:48.530> of<00:20:48.980> this<00:20:49.159> program 00:20:49.480 --> 00:20:49.490 align:start position:0% version of this program of this program 00:20:49.490 --> 00:20:51.760 align:start position:0% version of this program of this program executing<00:20:50.000> where<00:20:50.539> we<00:20:50.690> run<00:20:50.870> the<00:20:51.049> inside<00:20:51.440> of<00:20:51.590> one 00:20:51.760 --> 00:20:51.770 align:start position:0% executing where we run the inside of one 00:20:51.770 --> 00:20:55.180 align:start position:0% executing where we run the inside of one time<00:20:52.070> then<00:20:52.850> after<00:20:53.120> running<00:20:53.299> it<00:20:53.480> one<00:20:53.690> time<00:20:54.190> it 00:20:55.180 --> 00:20:55.190 align:start position:0% time then after running it one time it 00:20:55.190 --> 00:20:57.130 align:start position:0% time then after running it one time it all<00:20:55.400> balances<00:20:56.059> fun<00:20:56.299> and<00:20:56.690> then<00:20:56.840> meetings 00:20:57.130 --> 00:20:57.140 align:start position:0% all balances fun and then meetings 00:20:57.140 --> 00:20:58.659 align:start position:0% all balances fun and then meetings there's<00:20:57.890> another<00:20:58.070> version<00:20:58.280> we're<00:20:58.429> gonna<00:20:58.549> run 00:20:58.659 --> 00:20:58.669 align:start position:0% there's another version we're gonna run 00:20:58.669 --> 00:21:00.460 align:start position:0% there's another version we're gonna run it<00:20:58.760> two<00:20:58.909> times<00:20:59.059> sometimes<00:20:59.539> so<00:20:59.659> there's<00:21:00.380> some 00:21:00.460 --> 00:21:00.470 align:start position:0% it two times sometimes so there's some 00:21:00.470 --> 00:21:01.750 align:start position:0% it two times sometimes so there's some times<00:21:00.650> an<00:21:00.770> infinite<00:21:01.190> number<00:21:01.250> of<00:21:01.490> different 00:21:01.750 --> 00:21:01.760 align:start position:0% times an infinite number of different 00:21:01.760 --> 00:21:04.060 align:start position:0% times an infinite number of different ways<00:21:02.120> to<00:21:02.480> run<00:21:02.990> a<00:21:03.020> program<00:21:03.440> that<00:21:03.559> has<00:21:03.710> a<00:21:03.740> single 00:21:04.060 --> 00:21:04.070 align:start position:0% ways to run a program that has a single 00:21:04.070 --> 00:21:06.460 align:start position:0% ways to run a program that has a single level<00:21:04.400> I<00:21:04.850> don't<00:21:05.390> know<00:21:05.600> how<00:21:05.720> many<00:21:05.780> times<00:21:06.140> you<00:21:06.289> go 00:21:06.460 --> 00:21:06.470 align:start position:0% level I don't know how many times you go 00:21:06.470 --> 00:21:10.350 align:start position:0% level I don't know how many times you go around<00:21:06.770> the<00:21:06.860> mouth<00:21:07.600> so<00:21:08.600> it's<00:21:08.750> a<00:21:08.809> big<00:21:09.049> problem 00:21:10.350 --> 00:21:10.360 align:start position:0% around the mouth so it's a big problem 00:21:10.360 --> 00:21:12.970 align:start position:0% around the mouth so it's a big problem how<00:21:11.360> are<00:21:11.480> you<00:21:11.539> gonna<00:21:11.630> know<00:21:11.720> what<00:21:12.230> the<00:21:12.500> program 00:21:12.970 --> 00:21:12.980 align:start position:0% how are you gonna know what the program 00:21:12.980 --> 00:21:15.070 align:start position:0% how are you gonna know what the program will<00:21:13.429> actually<00:21:13.970> do<00:21:14.179> because<00:21:14.720> the<00:21:14.929> way<00:21:15.020> to 00:21:15.070 --> 00:21:15.080 align:start position:0% will actually do because the way to 00:21:15.080 --> 00:21:16.240 align:start position:0% will actually do because the way to think<00:21:15.289> it's<00:21:15.440> a<00:21:15.530> way<00:21:15.650> to<00:21:15.679> internalize<00:21:16.190> what 00:21:16.240 --> 00:21:16.250 align:start position:0% think it's a way to internalize what 00:21:16.250 --> 00:21:18.640 align:start position:0% think it's a way to internalize what program<00:21:16.880> is<00:21:17.000> is<00:21:17.840> you're<00:21:17.990> making<00:21:18.080> a<00:21:18.289> prediction 00:21:18.640 --> 00:21:18.650 align:start position:0% program is is you're making a prediction 00:21:18.650 --> 00:21:21.880 align:start position:0% program is is you're making a prediction about<00:21:18.950> what<00:21:19.220> the<00:21:19.309> program<00:21:19.460> will<00:21:19.730> do<00:21:20.530> now<00:21:21.530> one 00:21:21.880 --> 00:21:21.890 align:start position:0% about what the program will do now one 00:21:21.890 --> 00:21:23.500 align:start position:0% about what the program will do now one way<00:21:22.070> that<00:21:22.190> we<00:21:22.280> could<00:21:22.429> do<00:21:22.580> this<00:21:22.730> is<00:21:23.240> that<00:21:23.390> we<00:21:23.480> can 00:21:23.500 --> 00:21:23.510 align:start position:0% way that we could do this is that we can 00:21:23.510 --> 00:21:26.370 align:start position:0% way that we could do this is that we can automatically<00:21:24.350> take<00:21:24.980> the<00:21:25.159> program<00:21:25.429> and 00:21:26.370 --> 00:21:26.380 align:start position:0% automatically take the program and 00:21:26.380 --> 00:21:28.840 align:start position:0% automatically take the program and verify<00:21:27.380> it<00:21:27.440> for<00:21:27.710> when<00:21:28.039> we<00:21:28.159> went<00:21:28.340> 0<00:21:28.580> times 00:21:28.840 --> 00:21:28.850 align:start position:0% verify it for when we went 0 times 00:21:28.850 --> 00:21:33.279 align:start position:0% verify it for when we went 0 times verify<00:21:29.720> Poneman<00:21:30.289> 1<00:21:30.530> verifiable<00:21:31.400> 1<00:21:31.520> 2<00:21:31.909> 3<00:21:32.299> 4<00:21:32.690> 5<00:21:32.929> 6 00:21:33.279 --> 00:21:33.289 align:start position:0% verify Poneman 1 verifiable 1 2 3 4 5 6 00:21:33.289 --> 00:21:35.590 align:start position:0% verify Poneman 1 verifiable 1 2 3 4 5 6 7<00:21:33.470> 8<00:21:33.620> 9<00:21:33.919> 10<00:21:34.159> etcetera<00:21:34.549> and<00:21:34.940> what<00:21:35.330> we<00:21:35.450> would<00:21:35.510> be 00:21:35.590 --> 00:21:35.600 align:start position:0% 7 8 9 10 etcetera and what we would be 00:21:35.600 --> 00:21:36.970 align:start position:0% 7 8 9 10 etcetera and what we would be doing<00:21:35.659> is<00:21:35.990> we<00:21:36.140> will<00:21:36.260> literally<00:21:36.530> be<00:21:36.799> like 00:21:36.970 --> 00:21:36.980 align:start position:0% doing is we will literally be like 00:21:36.980 --> 00:21:39.399 align:start position:0% doing is we will literally be like copying<00:21:37.460> piecing<00:21:37.820> this<00:21:37.940> code<00:21:38.240> inside<00:21:39.169> of<00:21:39.230> the 00:21:39.399 --> 00:21:39.409 align:start position:0% copying piecing this code inside of the 00:21:39.409 --> 00:21:41.380 align:start position:0% copying piecing this code inside of the verifier<00:21:39.770> over<00:21:40.039> and<00:21:40.190> over<00:21:40.370> again<00:21:40.429> to<00:21:41.059> verify 00:21:41.380 --> 00:21:41.390 align:start position:0% verifier over and over again to verify 00:21:41.390 --> 00:21:42.899 align:start position:0% verifier over and over again to verify each<00:21:41.630> one<00:21:41.809> of<00:21:41.900> those<00:21:41.990> different<00:21:42.169> versions 00:21:42.899 --> 00:21:42.909 align:start position:0% each one of those different versions 00:21:42.909 --> 00:21:45.700 align:start position:0% each one of those different versions that's<00:21:43.909> called<00:21:44.090> interject<00:21:44.840> evening 00:21:45.700 --> 00:21:45.710 align:start position:0% that's called interject evening 00:21:45.710 --> 00:21:48.010 align:start position:0% that's called interject evening and<00:21:46.210> intimidated<00:21:47.210> is<00:21:47.330> what<00:21:47.540> to<00:21:47.660> do<00:21:47.840> in 00:21:48.010 --> 00:21:48.020 align:start position:0% and intimidated is what to do in 00:21:48.020 --> 00:21:54.160 align:start position:0% and intimidated is what to do in situations<00:21:48.430> where<00:21:49.430> we<00:21:49.790> can't<00:21:50.240> figure<00:21:50.540> out<00:21:53.170> we 00:21:54.160 --> 00:21:54.170 align:start position:0% situations where we can't figure out we 00:21:54.170 --> 00:21:55.000 align:start position:0% situations where we can't figure out we do<00:21:54.320> not<00:21:54.440> either 00:21:55.000 --> 00:21:55.010 align:start position:0% do not either 00:21:55.010 --> 00:21:58.930 align:start position:0% do not either instead<00:21:55.810> we<00:21:56.810> have<00:21:57.590> a<00:21:57.620> programmer<00:21:58.040> specify<00:21:58.700> a 00:21:58.930 --> 00:21:58.940 align:start position:0% instead we have a programmer specify a 00:21:58.940 --> 00:22:03.970 align:start position:0% instead we have a programmer specify a loop<00:21:59.330> invariant<00:22:00.460> now<00:22:01.840> if<00:22:02.840> you<00:22:03.020> remember<00:22:03.470> from 00:22:03.970 --> 00:22:03.980 align:start position:0% loop invariant now if you remember from 00:22:03.980 --> 00:22:07.570 align:start position:0% loop invariant now if you remember from your<00:22:04.900> analysis<00:22:05.900> of<00:22:05.990> algorithms<00:22:06.530> course<00:22:06.740> we're 00:22:07.570 --> 00:22:07.580 align:start position:0% your analysis of algorithms course we're 00:22:07.580 --> 00:22:09.880 align:start position:0% your analysis of algorithms course we're you<00:22:07.640> to<00:22:07.700> use<00:22:07.880> the<00:22:08.120> CLN<00:22:08.570> respo<00:22:08.990> excuse 00:22:09.880 --> 00:22:09.890 align:start position:0% you to use the CLN respo excuse 00:22:09.890 --> 00:22:12.370 align:start position:0% you to use the CLN respo excuse computers<00:22:10.430> I<00:22:10.520> hope<00:22:11.020> you've<00:22:12.020> probably<00:22:12.200> learned 00:22:12.370 --> 00:22:12.380 align:start position:0% computers I hope you've probably learned 00:22:12.380 --> 00:22:13.660 align:start position:0% computers I hope you've probably learned a<00:22:12.560> lot<00:22:12.650> love<00:22:12.830> with<00:22:12.950> veneering<00:22:13.310> and<00:22:13.400> if<00:22:13.550> you're 00:22:13.660 --> 00:22:13.670 align:start position:0% a lot love with veneering and if you're 00:22:13.670 --> 00:22:16.570 align:start position:0% a lot love with veneering and if you're like<00:22:13.820> me<00:22:13.850> you<00:22:14.750> hated<00:22:15.080> that<00:22:15.110> class<00:22:15.410> and<00:22:16.250> it<00:22:16.340> was 00:22:16.570 --> 00:22:16.580 align:start position:0% like me you hated that class and it was 00:22:16.580 --> 00:22:20.770 align:start position:0% like me you hated that class and it was very<00:22:16.820> frustrating<00:22:17.140> okay<00:22:18.580> mostly<00:22:19.580> I<00:22:20.390> do<00:22:20.540> have<00:22:20.720> a 00:22:20.770 --> 00:22:20.780 align:start position:0% very frustrating okay mostly I do have a 00:22:20.780 --> 00:22:22.570 align:start position:0% very frustrating okay mostly I do have a little<00:22:20.870> bit<00:22:20.960> Marion<00:22:21.290> is<00:22:21.740> what<00:22:22.100> do<00:22:22.250> you<00:22:22.340> know 00:22:22.570 --> 00:22:22.580 align:start position:0% little bit Marion is what do you know 00:22:22.580 --> 00:22:24.700 align:start position:0% little bit Marion is what do you know before<00:22:23.390> those<00:22:23.630> nerves<00:22:23.930> and<00:22:24.320> what<00:22:24.470> you<00:22:24.590> know 00:22:24.700 --> 00:22:24.710 align:start position:0% before those nerves and what you know 00:22:24.710 --> 00:22:27.280 align:start position:0% before those nerves and what you know again<00:22:24.980> another<00:22:25.550> thing<00:22:25.760> that<00:22:25.880> we<00:22:25.970> know<00:22:26.150> is<00:22:26.480> that 00:22:27.280 --> 00:22:27.290 align:start position:0% again another thing that we know is that 00:22:27.290 --> 00:22:30.160 align:start position:0% again another thing that we know is that the<00:22:27.920> balance<00:22:28.370> in<00:22:28.790> the<00:22:29.090> contract<00:22:29.570> is<00:22:29.690> equal<00:22:30.050> to 00:22:30.160 --> 00:22:30.170 align:start position:0% the balance in the contract is equal to 00:22:30.170 --> 00:22:33.940 align:start position:0% the balance in the contract is equal to this<00:22:30.260> balance<00:22:31.600> okay<00:22:32.630> and<00:22:33.200> anything<00:22:33.620> that<00:22:33.770> we 00:22:33.940 --> 00:22:33.950 align:start position:0% this balance okay and anything that we 00:22:33.950 --> 00:22:39.700 align:start position:0% this balance okay and anything that we do<00:22:34.160> inside<00:22:35.030> of<00:22:35.090> this<00:22:35.800> that<00:22:37.150> and<00:22:38.350> will<00:22:39.350> not<00:22:39.530> be 00:22:39.700 --> 00:22:39.710 align:start position:0% do inside of this that and will not be 00:22:39.710 --> 00:22:41.970 align:start position:0% do inside of this that and will not be like<00:22:39.890> will<00:22:40.370> not<00:22:40.490> be<00:22:40.610> allowed<00:22:40.820> to<00:22:40.850> compilers 00:22:41.970 --> 00:22:41.980 align:start position:0% like will not be allowed to compilers 00:22:41.980 --> 00:22:44.170 align:start position:0% like will not be allowed to compilers and<00:22:42.980> what<00:22:43.160> this<00:22:43.250> is<00:22:43.370> gonna<00:22:43.520> do<00:22:43.760> is<00:22:43.910> it's<00:22:43.940> gonna 00:22:44.170 --> 00:22:44.180 align:start position:0% and what this is gonna do is it's gonna 00:22:44.180 --> 00:22:47.950 align:start position:0% and what this is gonna do is it's gonna allow<00:22:44.420> the<00:22:45.320> compiler<00:22:45.830> to<00:22:46.460> make<00:22:46.700> it<00:22:47.060> to<00:22:47.570> verify 00:22:47.950 --> 00:22:47.960 align:start position:0% allow the compiler to make it to verify 00:22:47.960 --> 00:22:50.020 align:start position:0% allow the compiler to make it to verify this<00:22:48.200> mortgages<00:22:48.800> we're<00:22:49.700> gonna<00:22:49.790> verify 00:22:50.020 --> 00:22:50.030 align:start position:0% this mortgages we're gonna verify 00:22:50.030 --> 00:22:52.210 align:start position:0% this mortgages we're gonna verify everything<00:22:50.540> above<00:22:51.020> this<00:22:51.230> to<00:22:51.800> make<00:22:51.980> sure<00:22:52.100> it 00:22:52.210 --> 00:22:52.220 align:start position:0% everything above this to make sure it 00:22:52.220 --> 00:22:54.100 align:start position:0% everything above this to make sure it establishes<00:22:52.610> Levin<00:22:53.000> great<00:22:53.180> we're<00:22:54.050> gonna 00:22:54.100 --> 00:22:54.110 align:start position:0% establishes Levin great we're gonna 00:22:54.110 --> 00:22:55.990 align:start position:0% establishes Levin great we're gonna verify<00:22:54.410> the<00:22:54.620> inside<00:22:55.190> to<00:22:55.640> make<00:22:55.670> sure<00:22:55.790> that 00:22:55.990 --> 00:22:56.000 align:start position:0% verify the inside to make sure that 00:22:56.000 --> 00:22:57.640 align:start position:0% verify the inside to make sure that preserves<00:22:56.330> it<00:22:56.570> then<00:22:57.020> we're<00:22:57.110> gonna<00:22:57.200> verify<00:22:57.410> the 00:22:57.640 --> 00:22:57.650 align:start position:0% preserves it then we're gonna verify the 00:22:57.650 --> 00:23:00.100 align:start position:0% preserves it then we're gonna verify the end<00:22:57.950> and<00:22:58.730> then<00:22:58.850> also<00:22:59.090> air<00:22:59.360> but<00:22:59.570> what<00:23:00.020> this 00:23:00.100 --> 00:23:00.110 align:start position:0% end and then also air but what this 00:23:00.110 --> 00:23:03.040 align:start position:0% end and then also air but what this means<00:23:00.170> is<00:23:00.710> that<00:23:00.770> we<00:23:01.580> provide<00:23:02.030> complete<00:23:02.840> nerve 00:23:03.040 --> 00:23:03.050 align:start position:0% means is that we provide complete nerve 00:23:03.050 --> 00:23:03.910 align:start position:0% means is that we provide complete nerve agent 00:23:03.910 --> 00:23:03.920 align:start position:0% agent 00:23:03.920 --> 00:23:06.610 align:start position:0% agent behavior<00:23:04.670> of<00:23:04.730> your<00:23:04.820> program<00:23:05.270> by<00:23:05.960> just<00:23:06.170> proving 00:23:06.610 --> 00:23:06.620 align:start position:0% behavior of your program by just proving 00:23:06.620 --> 00:23:12.040 align:start position:0% behavior of your program by just proving three<00:23:07.190> smaller<00:23:07.580> girls<00:23:10.630> it's<00:23:11.630> not<00:23:11.750> let's<00:23:11.900> go 00:23:12.040 --> 00:23:12.050 align:start position:0% three smaller girls it's not let's go 00:23:12.050 --> 00:23:17.650 align:start position:0% three smaller girls it's not let's go inside<00:23:12.350> and<00:23:13.420> do<00:23:14.420> some<00:23:14.600> stuff<00:23:15.640> so<00:23:16.640> we<00:23:17.120> were<00:23:17.330> in 00:23:17.650 --> 00:23:17.660 align:start position:0% inside and do some stuff so we were in 00:23:17.660 --> 00:23:19.930 align:start position:0% inside and do some stuff so we were in kind<00:23:17.930> of<00:23:18.140> the<00:23:18.290> context<00:23:18.800> of<00:23:18.920> the<00:23:18.980> consensus<00:23:19.520> so 00:23:19.930 --> 00:23:19.940 align:start position:0% kind of the context of the consensus so 00:23:19.940 --> 00:23:21.460 align:start position:0% kind of the context of the consensus so we<00:23:20.030> have<00:23:20.120> to<00:23:20.270> commit<00:23:20.570> the<00:23:20.720> transaction<00:23:20.930> and 00:23:21.460 --> 00:23:21.470 align:start position:0% we have to commit the transaction and 00:23:21.470 --> 00:23:23.140 align:start position:0% we have to commit the transaction and that<00:23:21.500> will<00:23:21.980> go<00:23:22.160> back<00:23:22.340> to<00:23:22.400> the<00:23:22.610> world<00:23:22.820> where<00:23:23.030> the 00:23:23.140 --> 00:23:23.150 align:start position:0% that will go back to the world where the 00:23:23.150 --> 00:23:25.450 align:start position:0% that will go back to the world where the two<00:23:23.300> participant<00:23:23.990> do<00:23:24.080> something<00:23:24.380> and<00:23:25.310> then 00:23:25.450 --> 00:23:25.460 align:start position:0% two participant do something and then 00:23:25.460 --> 00:23:27.730 align:start position:0% two participant do something and then they<00:23:25.490> want<00:23:25.910> to<00:23:26.000> do<00:23:26.090> is<00:23:26.240> want<00:23:26.450> the<00:23:26.570> child<00:23:26.870> to<00:23:27.620> do 00:23:27.730 --> 00:23:27.740 align:start position:0% they want to do is want the child to do 00:23:27.740 --> 00:23:31.210 align:start position:0% they want to do is want the child to do something<00:23:28.330> or<00:23:29.330> something<00:23:29.950> where<00:23:30.950> she's<00:23:31.100> gonna 00:23:31.210 --> 00:23:31.220 align:start position:0% something or something where she's gonna 00:23:31.220 --> 00:23:33.430 align:start position:0% something or something where she's gonna ask<00:23:31.460> for<00:23:31.910> a<00:23:31.940> certain<00:23:32.180> amount<00:23:32.330> of<00:23:32.420> money<00:23:32.660> and<00:23:32.900> we 00:23:33.430 --> 00:23:33.440 align:start position:0% ask for a certain amount of money and we 00:23:33.440 --> 00:23:34.840 align:start position:0% ask for a certain amount of money and we know<00:23:33.590> that<00:23:33.800> this<00:23:33.860> money<00:23:34.130> will<00:23:34.340> start<00:23:34.730> be 00:23:34.840 --> 00:23:34.850 align:start position:0% know that this money will start be 00:23:34.850 --> 00:23:36.900 align:start position:0% know that this money will start be classified<00:23:35.330> and<00:23:36.020> it's<00:23:36.200> going<00:23:36.320> to<00:23:36.440> be<00:23:36.560> a<00:23:36.590> number 00:23:36.900 --> 00:23:36.910 align:start position:0% classified and it's going to be a number 00:23:36.910 --> 00:23:41.500 align:start position:0% classified and it's going to be a number and<00:23:37.910> will<00:23:38.090> interact<00:23:39.700> interact<00:23:40.700> with<00:23:41.480> a 00:23:41.500 --> 00:23:41.510 align:start position:0% and will interact interact with a 00:23:41.510 --> 00:23:43.570 align:start position:0% and will interact interact with a customer<00:23:42.140> sorry-sorry<00:23:42.530> the<00:23:42.890> front<00:23:43.100> end<00:23:43.280> to 00:23:43.570 --> 00:23:43.580 align:start position:0% customer sorry-sorry the front end to 00:23:43.580 --> 00:23:46.300 align:start position:0% customer sorry-sorry the front end to request<00:23:44.300> the<00:23:44.450> money<00:23:44.630> and<00:23:45.440> the<00:23:46.010> way<00:23:46.100> that<00:23:46.220> we're 00:23:46.300 --> 00:23:46.310 align:start position:0% request the money and the way that we're 00:23:46.310 --> 00:23:49.300 align:start position:0% request the money and the way that we're gonna<00:23:46.400> do<00:23:46.610> this<00:23:47.170> they<00:23:48.170> said<00:23:48.380> we're<00:23:48.860> gonna<00:23:48.950> tell 00:23:49.300 --> 00:23:49.310 align:start position:0% gonna do this they said we're gonna tell 00:23:49.310 --> 00:23:51.340 align:start position:0% gonna do this they said we're gonna tell the<00:23:49.550> front<00:23:49.730> end<00:23:49.970> how<00:23:50.720> much<00:23:50.870> money<00:23:51.050> is<00:23:51.170> in<00:23:51.290> the 00:23:51.340 --> 00:23:51.350 align:start position:0% the front end how much money is in the 00:23:51.350 --> 00:23:52.480 align:start position:0% the front end how much money is in the account<00:23:51.380> it's<00:23:52.160> okay 00:23:52.480 --> 00:23:52.490 align:start position:0% account it's okay 00:23:52.490 --> 00:23:54.550 align:start position:0% account it's okay you<00:23:52.940> know<00:23:53.060> know<00:23:53.330> how<00:23:53.540> to<00:23:53.600> display<00:23:53.990> to<00:23:54.110> the<00:23:54.230> user 00:23:54.550 --> 00:23:54.560 align:start position:0% you know know how to display to the user 00:23:54.560 --> 00:23:56.800 align:start position:0% you know know how to display to the user yeah<00:23:55.070> Sally<00:23:55.490> do<00:23:56.030> you<00:23:56.120> have<00:23:56.300> a<00:23:56.330> hundred<00:23:56.540> dollars 00:23:56.800 --> 00:23:56.810 align:start position:0% yeah Sally do you have a hundred dollars 00:23:56.810 --> 00:23:59.070 align:start position:0% yeah Sally do you have a hundred dollars of<00:23:56.930> elders<00:23:57.230> how<00:23:57.770> much<00:23:57.920> do<00:23:58.040> you<00:23:58.100> want 00:23:59.070 --> 00:23:59.080 align:start position:0% of elders how much do you want 00:23:59.080 --> 00:24:02.170 align:start position:0% of elders how much do you want so<00:24:00.080> this<00:24:00.230> internet<00:24:00.620> object<00:24:01.070> is<00:24:01.460> not<00:24:01.760> only<00:24:02.030> a 00:24:02.170 --> 00:24:02.180 align:start position:0% so this internet object is not only a 00:24:02.180 --> 00:24:04.330 align:start position:0% so this internet object is not only a way<00:24:02.390> to<00:24:02.450> get<00:24:02.780> information<00:24:02.960> from<00:24:03.650> the<00:24:03.950> front 00:24:04.330 --> 00:24:04.340 align:start position:0% way to get information from the front 00:24:04.340 --> 00:24:07.660 align:start position:0% way to get information from the front end<00:24:04.490> it's<00:24:05.090> a<00:24:05.210> way<00:24:05.300> to<00:24:05.330> share<00:24:05.810> information<00:24:06.670> so 00:24:07.660 --> 00:24:07.670 align:start position:0% end it's a way to share information so 00:24:07.670 --> 00:24:10.870 align:start position:0% end it's a way to share information so it's<00:24:08.390> a<00:24:08.510> two-way<00:24:08.900> street<00:24:09.700> essentially<00:24:10.700> what's 00:24:10.870 --> 00:24:10.880 align:start position:0% it's a two-way street essentially what's 00:24:10.880 --> 00:24:13.270 align:start position:0% it's a two-way street essentially what's going<00:24:10.910> on<00:24:11.240> is<00:24:11.630> that<00:24:11.660> this<00:24:12.380> breach<00:24:12.650> program<00:24:13.070> is 00:24:13.270 --> 00:24:13.280 align:start position:0% going on is that this breach program is 00:24:13.280 --> 00:24:16.870 align:start position:0% going on is that this breach program is specifying<00:24:13.970> the<00:24:14.420> API<00:24:14.780> to<00:24:15.680> the<00:24:15.710> contract<00:24:16.310> the 00:24:16.870 --> 00:24:16.880 align:start position:0% specifying the API to the contract the 00:24:16.880 --> 00:24:19.180 align:start position:0% specifying the API to the contract the API<00:24:17.210> to<00:24:17.330> the<00:24:17.660> clients<00:24:18.110> sorry<00:24:18.710> that<00:24:18.980> they've 00:24:19.180 --> 00:24:19.190 align:start position:0% API to the clients sorry that they've 00:24:19.190 --> 00:24:20.680 align:start position:0% API to the clients sorry that they've got<00:24:19.400> to<00:24:19.430> the<00:24:19.610> backend<00:24:19.790> then<00:24:20.150> we'll<00:24:20.300> write<00:24:20.510> up 00:24:20.680 --> 00:24:20.690 align:start position:0% got to the backend then we'll write up 00:24:20.690 --> 00:24:22.670 align:start position:0% got to the backend then we'll write up some<00:24:20.720> client 00:24:22.670 --> 00:24:22.680 align:start position:0% some client 00:24:22.680 --> 00:24:25.380 align:start position:0% some client now<00:24:23.680> the<00:24:24.460> next<00:24:24.640> thing<00:24:24.730> we<00:24:24.910> need<00:24:25.030> to<00:24:25.060> do<00:24:25.240> is 00:24:25.380 --> 00:24:25.390 align:start position:0% now the next thing we need to do is 00:24:25.390 --> 00:24:27.180 align:start position:0% now the next thing we need to do is write<00:24:25.570> an<00:24:25.750> assertion<00:24:26.020> that's<00:24:26.590> gonna<00:24:26.830> say<00:24:27.010> that 00:24:27.180 --> 00:24:27.190 align:start position:0% write an assertion that's gonna say that 00:24:27.190 --> 00:24:29.340 align:start position:0% write an assertion that's gonna say that how<00:24:27.370> much<00:24:27.580> had<00:24:28.120> better<00:24:28.360> be<00:24:28.630> stronger<00:24:29.080> than<00:24:29.200> or 00:24:29.340 --> 00:24:29.350 align:start position:0% how much had better be stronger than or 00:24:29.350 --> 00:24:32.790 align:start position:0% how much had better be stronger than or equal<00:24:29.680> to<00:24:30.480> the<00:24:31.480> balance<00:24:31.840> because<00:24:32.470> this 00:24:32.790 --> 00:24:32.800 align:start position:0% equal to the balance because this 00:24:32.800 --> 00:24:34.350 align:start position:0% equal to the balance because this program<00:24:33.130> would<00:24:33.400> make<00:24:33.640> sense<00:24:33.880> in<00:24:34.210> that 00:24:34.350 --> 00:24:34.360 align:start position:0% program would make sense in that 00:24:34.360 --> 00:24:36.810 align:start position:0% program would make sense in that production<00:24:34.890> business<00:24:35.890> function<00:24:36.670> right<00:24:36.760> here 00:24:36.810 --> 00:24:36.820 align:start position:0% production business function right here 00:24:36.820 --> 00:24:39.360 align:start position:0% production business function right here is<00:24:37.540> one<00:24:37.990> of<00:24:38.020> the<00:24:38.290> verification<00:24:38.920> assertions 00:24:39.360 --> 00:24:39.370 align:start position:0% is one of the verification assertions 00:24:39.370 --> 00:24:41.250 align:start position:0% is one of the verification assertions that<00:24:39.400> we<00:24:39.550> can<00:24:39.700> put<00:24:39.850> out<00:24:39.970> I<00:24:40.300> mentioned<00:24:40.960> before 00:24:41.250 --> 00:24:41.260 align:start position:0% that we can put out I mentioned before 00:24:41.260 --> 00:24:42.480 align:start position:0% that we can put out I mentioned before you<00:24:41.530> can<00:24:41.590> go<00:24:41.770> look<00:24:41.920> at<00:24:41.980> the<00:24:42.070> slides<00:24:42.280> that<00:24:42.400> you 00:24:42.480 --> 00:24:42.490 align:start position:0% you can go look at the slides that you 00:24:42.490 --> 00:24:44.580 align:start position:0% you can go look at the slides that you might<00:24:42.670> enter<00:24:42.960> that<00:24:43.960> there<00:24:44.140> are<00:24:44.230> different 00:24:44.580 --> 00:24:44.590 align:start position:0% might enter that there are different 00:24:44.590 --> 00:24:47.610 align:start position:0% might enter that there are different kinds<00:24:45.040> of<00:24:45.070> a<00:24:45.250> search<00:24:46.290> assertions<00:24:47.290> are<00:24:47.410> things 00:24:47.610 --> 00:24:47.620 align:start position:0% kinds of a search assertions are things 00:24:47.620 --> 00:24:49.470 align:start position:0% kinds of a search assertions are things I<00:24:47.740> always<00:24:48.100> want<00:24:48.280> to<00:24:48.340> be<00:24:48.430> true<00:24:48.670> if<00:24:49.150> they're<00:24:49.330> not 00:24:49.470 --> 00:24:49.480 align:start position:0% I always want to be true if they're not 00:24:49.480 --> 00:24:52.980 align:start position:0% I always want to be true if they're not refusal<00:24:50.230> in<00:24:50.380> compile<00:24:51.030> assumes<00:24:52.030> are<00:24:52.510> kind<00:24:52.870> of 00:24:52.980 --> 00:24:52.990 align:start position:0% refusal in compile assumes are kind of 00:24:52.990 --> 00:24:58.380 align:start position:0% refusal in compile assumes are kind of like<00:24:53.200> require<00:24:56.250> insulin<00:24:57.250> where<00:24:58.090> we<00:24:58.180> obviously 00:24:58.380 --> 00:24:58.390 align:start position:0% like require insulin where we obviously 00:24:58.390 --> 00:25:00.900 align:start position:0% like require insulin where we obviously check<00:24:58.870> this<00:24:59.020> property<00:24:59.440> at<00:24:59.560> runtime<00:24:59.770> but<00:25:00.760> the 00:25:00.900 --> 00:25:00.910 align:start position:0% check this property at runtime but the 00:25:00.910 --> 00:25:02.430 align:start position:0% check this property at runtime but the other<00:25:01.060> thing<00:25:01.210> that<00:25:01.240> we<00:25:01.390> do<00:25:01.570> is<00:25:01.960> we<00:25:02.170> make<00:25:02.380> sure 00:25:02.430 --> 00:25:02.440 align:start position:0% other thing that we do is we make sure 00:25:02.440 --> 00:25:05.160 align:start position:0% other thing that we do is we make sure that<00:25:03.040> all<00:25:03.550> the<00:25:03.820> assertions<00:25:04.300> later<00:25:04.630> on<00:25:04.930> in<00:25:05.110> the 00:25:05.160 --> 00:25:05.170 align:start position:0% that all the assertions later on in the 00:25:05.170 --> 00:25:07.290 align:start position:0% that all the assertions later on in the program<00:25:05.350> are<00:25:05.890> entailed<00:25:06.490> by<00:25:07.060> these 00:25:07.290 --> 00:25:07.300 align:start position:0% program are entailed by these 00:25:07.300 --> 00:25:09.300 align:start position:0% program are entailed by these assumptions<00:25:07.840> so<00:25:08.590> later<00:25:08.860> on<00:25:08.920> in<00:25:09.100> the<00:25:09.190> program 00:25:09.300 --> 00:25:09.310 align:start position:0% assumptions so later on in the program 00:25:09.310 --> 00:25:11.280 align:start position:0% assumptions so later on in the program were<00:25:09.580> allowed<00:25:09.940> to<00:25:09.970> write<00:25:10.360> down<00:25:10.570> a<00:25:10.600> service<00:25:10.990> and 00:25:11.280 --> 00:25:11.290 align:start position:0% were allowed to write down a service and 00:25:11.290 --> 00:25:13.560 align:start position:0% were allowed to write down a service and if<00:25:11.770> any<00:25:11.980> ascertain<00:25:12.490> would<00:25:12.700> fail<00:25:12.970> because<00:25:13.420> you 00:25:13.560 --> 00:25:13.570 align:start position:0% if any ascertain would fail because you 00:25:13.570 --> 00:25:15.540 align:start position:0% if any ascertain would fail because you forgot<00:25:14.080> one<00:25:14.290> of<00:25:14.320> these<00:25:14.500> assumes<00:25:14.860> then<00:25:15.340> will 00:25:15.540 --> 00:25:15.550 align:start position:0% forgot one of these assumes then will 00:25:15.550 --> 00:25:17.670 align:start position:0% forgot one of these assumes then will refuse<00:25:15.880> to<00:25:15.910> compile<00:25:16.330> the<00:25:16.450> program<00:25:16.630> the<00:25:17.380> idea 00:25:17.670 --> 00:25:17.680 align:start position:0% refuse to compile the program the idea 00:25:17.680 --> 00:25:20.130 align:start position:0% refuse to compile the program the idea is<00:25:18.040> that<00:25:18.220> we're<00:25:18.550> guaranteeing<00:25:19.140> consistency 00:25:20.130 --> 00:25:20.140 align:start position:0% is that we're guaranteeing consistency 00:25:20.140 --> 00:25:21.990 align:start position:0% is that we're guaranteeing consistency between<00:25:20.470> the<00:25:20.650> clients<00:25:21.220> and<00:25:21.370> the<00:25:21.460> contracts 00:25:21.990 --> 00:25:22.000 align:start position:0% between the clients and the contracts 00:25:22.000 --> 00:25:24.510 align:start position:0% between the clients and the contracts we're<00:25:22.480> making<00:25:22.870> sure<00:25:22.990> that<00:25:23.470> your<00:25:23.680> program<00:25:23.980> at 00:25:24.510 --> 00:25:24.520 align:start position:0% we're making sure that your program at 00:25:24.520 --> 00:25:27.030 align:start position:0% we're making sure that your program at runtime<00:25:25.110> actually<00:25:26.110> verifies<00:25:26.590> all<00:25:26.920> the 00:25:27.030 --> 00:25:27.040 align:start position:0% runtime actually verifies all the 00:25:27.040 --> 00:25:29.790 align:start position:0% runtime actually verifies all the properties<00:25:27.520> that<00:25:27.850> are<00:25:28.330> necessary<00:25:28.930> for<00:25:29.710> your 00:25:29.790 --> 00:25:29.800 align:start position:0% properties that are necessary for your 00:25:29.800 --> 00:25:34.800 align:start position:0% properties that are necessary for your contract<00:25:30.340> to<00:25:30.460> run<00:25:33.240> so<00:25:34.240> now<00:25:34.330> what<00:25:34.480> we'll<00:25:34.600> do<00:25:34.720> is 00:25:34.800 --> 00:25:34.810 align:start position:0% contract to run so now what we'll do is 00:25:34.810 --> 00:25:38.430 align:start position:0% contract to run so now what we'll do is we'll<00:25:35.080> have<00:25:35.230> the<00:25:35.320> child<00:25:35.590> publish<00:25:36.550> mmm 00:25:38.430 --> 00:25:38.440 align:start position:0% we'll have the child publish mmm 00:25:38.440 --> 00:25:42.360 align:start position:0% we'll have the child publish mmm then<00:25:40.170> animal<00:25:41.170> ready<00:25:41.320> the<00:25:41.470> time<00:25:41.680> ability<00:25:42.190> and 00:25:42.360 --> 00:25:42.370 align:start position:0% then animal ready the time ability and 00:25:42.370 --> 00:25:44.610 align:start position:0% then animal ready the time ability and the<00:25:43.120> type<00:25:43.300> of<00:25:43.330> food<00:25:43.600> will<00:25:43.780> be<00:25:43.870> a<00:25:43.900> lot<00:25:44.170> of 00:25:44.610 --> 00:25:44.620 align:start position:0% the type of food will be a lot of 00:25:44.620 --> 00:25:47.640 align:start position:0% the type of food will be a lot of available<00:25:45.190> to<00:25:45.310> the<00:25:45.430> parent<00:25:45.760> to<00:25:45.790> run<00:25:46.030> and<00:25:46.960> if 00:25:47.640 --> 00:25:47.650 align:start position:0% available to the parent to run and if 00:25:47.650 --> 00:25:50.520 align:start position:0% available to the parent to run and if she<00:25:48.180> fishy<00:25:49.180> times<00:25:49.540> out<00:25:49.750> then<00:25:50.110> we'll<00:25:50.230> just<00:25:50.380> say 00:25:50.520 --> 00:25:50.530 align:start position:0% she fishy times out then we'll just say 00:25:50.530 --> 00:25:52.920 align:start position:0% she fishy times out then we'll just say that<00:25:50.560> it<00:25:50.770> is<00:25:50.980> an<00:25:51.460> automatic<00:25:52.120> dignity 00:25:52.920 --> 00:25:52.930 align:start position:0% that it is an automatic dignity 00:25:52.930 --> 00:25:54.810 align:start position:0% that it is an automatic dignity so<00:25:53.170> it's<00:25:53.290> not<00:25:53.410> an<00:25:53.590> it's<00:25:53.860> not<00:25:53.920> a<00:25:54.040> yes<00:25:54.280> or<00:25:54.520> a<00:25:54.580> No 00:25:54.810 --> 00:25:54.820 align:start position:0% so it's not an it's not a yes or a No 00:25:54.820 --> 00:25:59.400 align:start position:0% so it's not an it's not a yes or a No but<00:25:55.750> we<00:25:56.140> just<00:25:56.260> continue<00:25:56.800> the<00:25:56.920> purple<00:25:58.320> so<00:25:59.320> what 00:25:59.400 --> 00:25:59.410 align:start position:0% but we just continue the purple so what 00:25:59.410 --> 00:26:00.660 align:start position:0% but we just continue the purple so what happens<00:25:59.680> here<00:25:59.740> is<00:26:00.070> that<00:26:00.100> rather<00:26:00.400> than 00:26:00.660 --> 00:26:00.670 align:start position:0% happens here is that rather than 00:26:00.670 --> 00:26:02.850 align:start position:0% happens here is that rather than returning<00:26:01.060> at<00:26:01.240> the<00:26:01.390> end<00:26:01.510> we<00:26:01.960> say<00:26:02.140> that<00:26:02.320> all<00:26:02.560> of 00:26:02.850 --> 00:26:02.860 align:start position:0% returning at the end we say that all of 00:26:02.860 --> 00:26:05.040 align:start position:0% returning at the end we say that all of the<00:26:02.980> variables<00:26:03.490> that<00:26:03.790> the<00:26:04.270> loot<00:26:04.480> is<00:26:04.630> iterating 00:26:05.040 --> 00:26:05.050 align:start position:0% the variables that the loot is iterating 00:26:05.050 --> 00:26:06.780 align:start position:0% the variables that the loot is iterating over<00:26:05.140> they<00:26:05.560> stayed<00:26:05.830> up<00:26:06.040> in<00:26:06.100> the<00:26:06.280> statement<00:26:06.670> and 00:26:06.780 --> 00:26:06.790 align:start position:0% over they stayed up in the statement and 00:26:06.790 --> 00:26:08.820 align:start position:0% over they stayed up in the statement and then<00:26:07.270> we<00:26:07.360> continue<00:26:07.780> to<00:26:07.900> the<00:26:08.200> next<00:26:08.320> generation 00:26:08.820 --> 00:26:08.830 align:start position:0% then we continue to the next generation 00:26:08.830 --> 00:26:10.890 align:start position:0% then we continue to the next generation if<00:26:09.430> we<00:26:09.580> wanted<00:26:09.880> to<00:26:09.940> we<00:26:10.060> could<00:26:10.270> say<00:26:10.420> that<00:26:10.600> if<00:26:10.690> the 00:26:10.890 --> 00:26:10.900 align:start position:0% if we wanted to we could say that if the 00:26:10.900 --> 00:26:14.130 align:start position:0% if we wanted to we could say that if the time<00:26:11.680> what<00:26:11.830> happens<00:26:12.190> then<00:26:12.790> it<00:26:13.420> like<00:26:13.660> goes<00:26:13.930> in 00:26:14.130 --> 00:26:14.140 align:start position:0% time what happens then it like goes in 00:26:14.140 --> 00:26:16.620 align:start position:0% time what happens then it like goes in favor<00:26:14.410> of<00:26:14.680> the<00:26:15.070> of<00:26:15.820> the<00:26:15.970> child<00:26:16.180> that<00:26:16.390> she<00:26:16.420> had 00:26:16.620 --> 00:26:16.630 align:start position:0% favor of the of the child that she had 00:26:16.630 --> 00:26:20.490 align:start position:0% favor of the of the child that she had for<00:26:16.810> me<00:26:16.840> they<00:26:17.500> talk<00:26:17.680> to<00:26:17.800> us<00:26:17.830> and<00:26:18.370> we<00:26:18.490> do<00:26:19.320> this<00:26:20.320> by 00:26:20.490 --> 00:26:20.500 align:start position:0% for me they talk to us and we do this by 00:26:20.500 --> 00:26:22.260 align:start position:0% for me they talk to us and we do this by the<00:26:20.530> way<00:26:20.650> is<00:26:20.860> one<00:26:21.070> of<00:26:21.100> these<00:26:21.280> one<00:26:21.640> of<00:26:21.670> the<00:26:21.790> one 00:26:22.260 --> 00:26:22.270 align:start position:0% the way is one of these one of the one 00:26:22.270 --> 00:26:25.350 align:start position:0% the way is one of these one of the one of<00:26:22.300> the<00:26:22.510> examples<00:26:23.020> that<00:26:23.260> the<00:26:23.950> reach<00:26:24.880> language 00:26:25.350 --> 00:26:25.360 align:start position:0% of the examples that the reach language 00:26:25.360 --> 00:26:27.000 align:start position:0% of the examples that the reach language is<00:26:25.570> different<00:26:25.900> from<00:26:25.990> my<00:26:26.170> earlier<00:26:26.500> project<00:26:26.920> the 00:26:27.000 --> 00:26:27.010 align:start position:0% is different from my earlier project the 00:26:27.010 --> 00:26:28.530 align:start position:0% is different from my earlier project the elaborate<00:26:27.280> language<00:26:27.790> because<00:26:28.300> they<00:26:28.450> have 00:26:28.530 --> 00:26:28.540 align:start position:0% elaborate language because they have 00:26:28.540 --> 00:26:30.750 align:start position:0% elaborate language because they have that<00:26:28.660> pretty<00:26:28.870> language<00:26:29.320> the<00:26:30.130> timeout<00:26:30.550> locks 00:26:30.750 --> 00:26:30.760 align:start position:0% that pretty language the timeout locks 00:26:30.760 --> 00:26:32.610 align:start position:0% that pretty language the timeout locks are<00:26:30.970> automatically<00:26:31.540> generated<00:26:32.110> upon<00:26:32.320> ear<00:26:32.530> and 00:26:32.610 --> 00:26:32.620 align:start position:0% are automatically generated upon ear and 00:26:32.620 --> 00:26:34.920 align:start position:0% are automatically generated upon ear and a<00:26:32.650> half<00:26:32.800> they're<00:26:33.430> not<00:26:33.610> able<00:26:33.940> to<00:26:34.090> but<00:26:34.630> also<00:26:34.750> you 00:26:34.920 --> 00:26:34.930 align:start position:0% a half they're not able to but also you 00:26:34.930 --> 00:26:37.140 align:start position:0% a half they're not able to but also you don't<00:26:35.080> have<00:26:35.260> to<00:26:35.500> specify<00:26:35.740> what<00:26:35.950> they<00:26:36.220> do<00:26:36.280> so 00:26:37.140 --> 00:26:37.150 align:start position:0% don't have to specify what they do so 00:26:37.150 --> 00:26:39.240 align:start position:0% don't have to specify what they do so they<00:26:37.180> automatically<00:26:37.990> enter<00:26:38.440> protocol<00:26:38.860> to<00:26:39.100> get 00:26:39.240 --> 00:26:39.250 align:start position:0% they automatically enter protocol to get 00:26:39.250 --> 00:26:46.890 align:start position:0% they automatically enter protocol to get all<00:26:39.520> the<00:26:39.730> money<00:26:44.070> okay<00:26:45.070> so<00:26:45.510> now<00:26:46.510> we're<00:26:46.720> inside 00:26:46.890 --> 00:26:46.900 align:start position:0% all the money okay so now we're inside 00:26:46.900 --> 00:26:50.490 align:start position:0% all the money okay so now we're inside of<00:26:47.440> the<00:26:47.590> contract<00:26:48.040> and<00:26:48.370> we<00:26:48.790> will<00:26:49.000> require<00:26:49.500> that 00:26:50.490 --> 00:26:50.500 align:start position:0% of the contract and we will require that 00:26:50.500 --> 00:26:52.900 align:start position:0% of the contract and we will require that how<00:26:51.370> much<00:26:51.580> is<00:26:51.760> less<00:26:51.970> than<00:26:52.120> the<00:26:52.210> balance 00:26:52.900 --> 00:26:52.910 align:start position:0% how much is less than the balance 00:26:52.910 --> 00:26:55.750 align:start position:0% how much is less than the balance so<00:26:53.750> this<00:26:53.990> vertical<00:26:54.200> only<00:26:54.740> makes<00:26:54.950> sense<00:26:55.160> going 00:26:55.750 --> 00:26:55.760 align:start position:0% so this vertical only makes sense going 00:26:55.760 --> 00:26:57.670 align:start position:0% so this vertical only makes sense going forward<00:26:56.300> and<00:26:56.480> how<00:26:56.750> much<00:26:57.020> it<00:26:57.140> is<00:26:57.200> not<00:26:57.410> more<00:26:57.620> than 00:26:57.670 --> 00:26:57.680 align:start position:0% forward and how much it is not more than 00:26:57.680 --> 00:26:59.770 align:start position:0% forward and how much it is not more than that<00:26:58.040> once<00:26:58.250> now<00:26:58.970> it<00:26:59.150> looks<00:26:59.330> like<00:26:59.510> what<00:26:59.630> we're 00:26:59.770 --> 00:26:59.780 align:start position:0% that once now it looks like what we're 00:26:59.780 --> 00:27:01.090 align:start position:0% that once now it looks like what we're doing<00:26:59.990> is<00:27:00.080> we're<00:27:00.230> saying<00:27:00.440> something<00:27:00.710> twice 00:27:01.090 --> 00:27:01.100 align:start position:0% doing is we're saying something twice 00:27:01.100 --> 00:27:02.800 align:start position:0% doing is we're saying something twice we're<00:27:01.490> setting<00:27:01.730> about<00:27:01.850> here<00:27:02.120> coursing<00:27:02.540> event 00:27:02.800 --> 00:27:02.810 align:start position:0% we're setting about here coursing event 00:27:02.810 --> 00:27:05.350 align:start position:0% we're setting about here coursing event here<00:27:03.640> and<00:27:04.640> of<00:27:04.730> course<00:27:04.910> we've<00:27:05.090> literally 00:27:05.350 --> 00:27:05.360 align:start position:0% here and of course we've literally 00:27:05.360 --> 00:27:07.150 align:start position:0% here and of course we've literally ripped<00:27:05.690> down<00:27:05.870> how<00:27:06.230> much<00:27:06.380> less<00:27:06.590> than<00:27:06.740> miles<00:27:06.920> two 00:27:07.150 --> 00:27:07.160 align:start position:0% ripped down how much less than miles two 00:27:07.160 --> 00:27:08.440 align:start position:0% ripped down how much less than miles two times<00:27:07.370> what<00:27:07.550> we<00:27:07.640> did<00:27:07.790> it<00:27:07.910> for<00:27:08.030> totally 00:27:08.440 --> 00:27:08.450 align:start position:0% times what we did it for totally 00:27:08.450 --> 00:27:10.300 align:start position:0% times what we did it for totally different<00:27:08.480> reasons<00:27:08.890> what<00:27:09.890> we're<00:27:10.010> doing<00:27:10.190> right 00:27:10.300 --> 00:27:10.310 align:start position:0% different reasons what we're doing right 00:27:10.310 --> 00:27:11.830 align:start position:0% different reasons what we're doing right here<00:27:10.370> is<00:27:10.670> we're<00:27:10.850> saying<00:27:11.030> that<00:27:11.210> this<00:27:11.360> protocol 00:27:11.830 --> 00:27:11.840 align:start position:0% here is we're saying that this protocol 00:27:11.840 --> 00:27:12.880 align:start position:0% here is we're saying that this protocol makes<00:27:12.140> no<00:27:12.410> sense 00:27:12.880 --> 00:27:12.890 align:start position:0% makes no sense 00:27:12.890 --> 00:27:15.880 align:start position:0% makes no sense unless<00:27:13.430> this<00:27:13.610> is<00:27:13.670> true<00:27:14.440> what<00:27:15.440> we're<00:27:15.590> saying<00:27:15.680> up 00:27:15.880 --> 00:27:15.890 align:start position:0% unless this is true what we're saying up 00:27:15.890 --> 00:27:18.700 align:start position:0% unless this is true what we're saying up here<00:27:15.920> is<00:27:16.430> that<00:27:16.610> I<00:27:17.030> am<00:27:17.180> a<00:27:17.300> bad<00:27:17.510> client<00:27:17.930> if<00:27:18.530> I 00:27:18.700 --> 00:27:18.710 align:start position:0% here is that I am a bad client if I 00:27:18.710 --> 00:27:21.910 align:start position:0% here is that I am a bad client if I don't<00:27:18.950> check<00:27:19.130> this<00:27:19.250> properly<00:27:19.640> and<00:27:20.800> you<00:27:21.800> have 00:27:21.910 --> 00:27:21.920 align:start position:0% don't check this properly and you have 00:27:21.920 --> 00:27:23.620 align:start position:0% don't check this properly and you have to<00:27:22.010> specify<00:27:22.220> both<00:27:22.700> of<00:27:22.880> those<00:27:23.000> things<00:27:23.270> if<00:27:23.600> you 00:27:23.620 --> 00:27:23.630 align:start position:0% to specify both of those things if you 00:27:23.630 --> 00:27:25.690 align:start position:0% to specify both of those things if you want<00:27:23.870> to<00:27:23.990> have<00:27:24.200> a<00:27:24.500> current<00:27:24.800> program<00:27:25.220> because 00:27:25.690 --> 00:27:25.700 align:start position:0% want to have a current program because 00:27:25.700 --> 00:27:28.330 align:start position:0% want to have a current program because you're<00:27:26.120> writing<00:27:26.450> down<00:27:26.600> the<00:27:27.290> client<00:27:27.770> and 00:27:28.330 --> 00:27:28.340 align:start position:0% you're writing down the client and 00:27:28.340 --> 00:27:30.280 align:start position:0% you're writing down the client and you're<00:27:28.550> writing<00:27:28.790> down<00:27:28.910> the<00:27:29.090> content<00:27:29.540> and<00:27:29.780> one 00:27:30.280 --> 00:27:30.290 align:start position:0% you're writing down the content and one 00:27:30.290 --> 00:27:31.180 align:start position:0% you're writing down the content and one of<00:27:30.350> the<00:27:30.440> thing<00:27:30.590> we'll<00:27:30.800> do<00:27:30.980> in<00:27:31.100> the 00:27:31.180 --> 00:27:31.190 align:start position:0% of the thing we'll do in the 00:27:31.190 --> 00:27:33.370 align:start position:0% of the thing we'll do in the verification<00:27:31.760> process<00:27:31.790> is<00:27:32.630> make<00:27:32.930> sure<00:27:33.140> that 00:27:33.370 --> 00:27:33.380 align:start position:0% verification process is make sure that 00:27:33.380 --> 00:27:36.730 align:start position:0% verification process is make sure that the<00:27:33.920> contract<00:27:34.460> only<00:27:34.700> interacts<00:27:35.540> with<00:27:36.200> good 00:27:36.730 --> 00:27:36.740 align:start position:0% the contract only interacts with good 00:27:36.740 --> 00:27:39.700 align:start position:0% the contract only interacts with good clients<00:27:37.220> so<00:27:37.970> if<00:27:38.030> we<00:27:38.240> left<00:27:38.750> of<00:27:38.990> this<00:27:39.170> line<00:27:39.230> and 00:27:39.700 --> 00:27:39.710 align:start position:0% clients so if we left of this line and 00:27:39.710 --> 00:27:42.550 align:start position:0% clients so if we left of this line and this<00:27:40.640> line<00:27:40.700> will<00:27:40.910> fail<00:27:41.330> to<00:27:41.360> verify<00:27:41.900> and<00:27:42.380> it'll 00:27:42.550 --> 00:27:42.560 align:start position:0% this line will fail to verify and it'll 00:27:42.560 --> 00:27:48.570 align:start position:0% this line will fail to verify and it'll say<00:27:43.930> that<00:27:45.640> because<00:27:46.640> of<00:27:46.880> course<00:27:47.090> in<00:27:47.300> the<00:27:47.390> actual 00:27:48.570 --> 00:27:48.580 align:start position:0% say that because of course in the actual 00:27:48.580 --> 00:27:51.730 align:start position:0% say that because of course in the actual and<00:27:49.580> like<00:27:49.910> your<00:27:50.060> actual<00:27:50.210> project<00:27:50.630> you<00:27:51.620> don't 00:27:51.730 --> 00:27:51.740 align:start position:0% and like your actual project you don't 00:27:51.740 --> 00:27:54.280 align:start position:0% and like your actual project you don't want<00:27:52.010> to<00:27:52.520> submit<00:27:52.760> a<00:27:52.910> transaction<00:27:53.570> and<00:27:53.930> how 00:27:54.280 --> 00:27:54.290 align:start position:0% want to submit a transaction and how 00:27:54.290 --> 00:27:55.600 align:start position:0% want to submit a transaction and how that<00:27:54.470> transaction<00:27:54.950> will<00:27:55.040> fail<00:27:55.190> because<00:27:55.340> you 00:27:55.600 --> 00:27:55.610 align:start position:0% that transaction will fail because you 00:27:55.610 --> 00:28:00.430 align:start position:0% that transaction will fail because you failed<00:27:57.910> okay<00:27:58.910> so<00:27:59.780> then<00:27:59.900> we'll<00:28:00.020> forget<00:28:00.320> the 00:28:00.430 --> 00:28:00.440 align:start position:0% failed okay so then we'll forget the 00:28:00.440 --> 00:28:02.410 align:start position:0% failed okay so then we'll forget the transaction<00:28:00.950> and<00:28:01.550> now<00:28:01.760> we're<00:28:01.940> back<00:28:02.090> to<00:28:02.150> the 00:28:02.410 --> 00:28:02.420 align:start position:0% transaction and now we're back to the 00:28:02.420 --> 00:28:04.570 align:start position:0% transaction and now we're back to the local<00:28:02.780> context<00:28:03.410> and<00:28:03.830> we'll<00:28:03.950> have<00:28:04.070> to<00:28:04.220> parent 00:28:04.570 --> 00:28:04.580 align:start position:0% local context and we'll have to parent 00:28:04.580 --> 00:28:13.520 align:start position:0% local context and we'll have to parent oh<00:28:05.080> I<00:28:06.670> know<00:28:07.670> this<00:28:07.850> is<00:28:08.390> approved 00:28:13.520 --> 00:28:13.530 align:start position:0% 00:28:13.530 --> 00:28:15.620 align:start position:0% in<00:28:14.010> this<00:28:14.160> case<00:28:14.370> we'll<00:28:15.000> get<00:28:15.150> back<00:28:15.270> to<00:28:15.480> moving 00:28:15.620 --> 00:28:15.630 align:start position:0% in this case we'll get back to moving 00:28:15.630 --> 00:28:18.890 align:start position:0% in this case we'll get back to moving because<00:28:16.580> the<00:28:17.580> interact<00:28:18.180> on<00:28:18.330> there<00:28:18.480> doesn't 00:28:18.890 --> 00:28:18.900 align:start position:0% because the interact on there doesn't 00:28:18.900 --> 00:28:20.240 align:start position:0% because the interact on there doesn't only<00:28:19.080> the<00:28:19.320> turn<00:28:19.500> numbers<00:28:19.800> can<00:28:20.040> return 00:28:20.240 --> 00:28:20.250 align:start position:0% only the turn numbers can return 00:28:20.250 --> 00:28:23.240 align:start position:0% only the turn numbers can return arbitrary<00:28:20.790> information<00:28:21.950> so<00:28:22.950> will<00:28:23.160> the 00:28:23.240 --> 00:28:23.250 align:start position:0% arbitrary information so will the 00:28:23.250 --> 00:28:25.340 align:start position:0% arbitrary information so will the interaction<00:28:23.760> will<00:28:23.880> say<00:28:24.060> all<00:28:24.540> approve<00:28:24.900> and 00:28:25.340 --> 00:28:25.350 align:start position:0% interaction will say all approve and 00:28:25.350 --> 00:28:26.810 align:start position:0% interaction will say all approve and will<00:28:25.650> tell<00:28:25.830> the<00:28:25.920> front<00:28:26.130> end<00:28:26.280> here's<00:28:26.580> how<00:28:26.670> much 00:28:26.810 --> 00:28:26.820 align:start position:0% will tell the front end here's how much 00:28:26.820 --> 00:28:28.100 align:start position:0% will tell the front end here's how much she<00:28:27.000> asks<00:28:27.270> for<00:28:27.300> it<00:28:27.600> here's<00:28:27.840> what<00:28:28.020> the 00:28:28.100 --> 00:28:28.110 align:start position:0% she asks for it here's what the 00:28:28.110 --> 00:28:33.650 align:start position:0% she asks for it here's what the remaining<00:28:28.470> balances<00:28:32.000> then<00:28:33.000> what<00:28:33.150> we'll<00:28:33.270> do<00:28:33.390> is 00:28:33.650 --> 00:28:33.660 align:start position:0% remaining balances then what we'll do is 00:28:33.660 --> 00:28:38.750 align:start position:0% remaining balances then what we'll do is we'll<00:28:34.590> publish<00:28:34.800> that<00:28:36.890> and<00:28:37.890> we'll<00:28:38.370> have<00:28:38.640> to 00:28:38.750 --> 00:28:38.760 align:start position:0% we'll publish that and we'll have to 00:28:38.760 --> 00:28:40.370 align:start position:0% we'll publish that and we'll have to deal<00:28:38.940> with<00:28:38.970> what<00:28:39.300> happens<00:28:39.600> if<00:28:39.690> there<00:28:39.900> is<00:28:40.170> a 00:28:40.370 --> 00:28:40.380 align:start position:0% deal with what happens if there is a 00:28:40.380 --> 00:28:44.210 align:start position:0% deal with what happens if there is a timeout<00:28:42.320> and<00:28:43.320> we'll<00:28:43.530> do<00:28:43.650> the<00:28:43.740> same<00:28:43.800> thing<00:28:43.950> as 00:28:44.210 --> 00:28:44.220 align:start position:0% timeout and we'll do the same thing as 00:28:44.220 --> 00:28:45.980 align:start position:0% timeout and we'll do the same thing as before<00:28:44.340> where<00:28:44.940> is<00:28:45.060> that<00:28:45.180> if<00:28:45.480> there<00:28:45.630> is<00:28:45.720> a<00:28:45.750> time 00:28:45.980 --> 00:28:45.990 align:start position:0% before where is that if there is a time 00:28:45.990 --> 00:28:47.600 align:start position:0% before where is that if there is a time of<00:28:46.020> the<00:28:46.440> parent<00:28:46.770> never<00:28:46.950> gets<00:28:47.160> around<00:28:47.400> to<00:28:47.580> it 00:28:47.600 --> 00:28:47.610 align:start position:0% of the parent never gets around to it 00:28:47.610 --> 00:28:54.460 align:start position:0% of the parent never gets around to it and<00:28:47.970> in<00:28:48.900> this<00:28:49.020> case<00:28:49.080> we'll<00:28:49.530> call<00:28:49.830> that<00:28:50.070> a<00:28:50.340> note 00:28:54.460 --> 00:28:54.470 align:start position:0% 00:28:54.470 --> 00:29:00.210 align:start position:0% and 00:29:00.210 --> 00:29:00.220 align:start position:0% 00:29:00.220 --> 00:29:03.480 align:start position:0% okay<00:29:00.899> so<00:29:01.899> now<00:29:02.049> we're<00:29:02.379> back<00:29:02.590> inside<00:29:02.889> of<00:29:03.100> the 00:29:03.480 --> 00:29:03.490 align:start position:0% okay so now we're back inside of the 00:29:03.490 --> 00:29:04.970 align:start position:0% okay so now we're back inside of the context 00:29:04.970 --> 00:29:04.980 align:start position:0% context 00:29:04.980 --> 00:29:08.340 align:start position:0% context 45:34<00:29:05.980> the<00:29:06.100> contract<00:29:06.549> and<00:29:07.090> now<00:29:07.389> the<00:29:07.870> contract 00:29:08.340 --> 00:29:08.350 align:start position:0% 45:34 the contract and now the contract 00:29:08.350 --> 00:29:11.549 align:start position:0% 45:34 the contract and now the contract knows<00:29:08.649> the<00:29:09.370> balance<00:29:09.759> it<00:29:10.570> knows<00:29:10.870> how<00:29:11.440> much 00:29:11.549 --> 00:29:11.559 align:start position:0% knows the balance it knows how much 00:29:11.559 --> 00:29:13.350 align:start position:0% knows the balance it knows how much money<00:29:11.710> was<00:29:11.950> asked<00:29:12.100> for<00:29:12.309> and<00:29:12.730> it<00:29:12.850> knows<00:29:13.029> whether 00:29:13.350 --> 00:29:13.360 align:start position:0% money was asked for and it knows whether 00:29:13.360 --> 00:29:15.899 align:start position:0% money was asked for and it knows whether the<00:29:13.600> parent<00:29:13.899> degrees<00:29:14.230> so<00:29:15.070> at<00:29:15.129> this<00:29:15.250> point<00:29:15.490> we 00:29:15.899 --> 00:29:15.909 align:start position:0% the parent degrees so at this point we 00:29:15.909 --> 00:29:20.279 align:start position:0% the parent degrees so at this point we can<00:29:16.029> actually<00:29:17.100> make<00:29:18.100> this<00:29:18.279> transaction<00:29:19.289> so 00:29:20.279 --> 00:29:20.289 align:start position:0% can actually make this transaction so 00:29:20.289 --> 00:29:23.129 align:start position:0% can actually make this transaction so we'll<00:29:20.409> say<00:29:20.559> if<00:29:20.860> the<00:29:21.070> approval<00:29:21.460> is<00:29:21.549> true<00:29:22.139> then 00:29:23.129 --> 00:29:23.139 align:start position:0% we'll say if the approval is true then 00:29:23.139 --> 00:29:30.149 align:start position:0% we'll say if the approval is true then we'll<00:29:23.590> transfer<00:29:23.919> how<00:29:24.879> much<00:29:25.259> to<00:29:26.259> the<00:29:26.379> China<00:29:29.159> and 00:29:30.149 --> 00:29:30.159 align:start position:0% we'll transfer how much to the China and 00:29:30.159 --> 00:29:34.230 align:start position:0% we'll transfer how much to the China and we'll<00:29:30.399> update<00:29:30.610> our<00:29:31.620> state<00:29:32.620> areas<00:29:33.149> say<00:29:34.149> that 00:29:34.230 --> 00:29:34.240 align:start position:0% we'll update our state areas say that 00:29:34.240 --> 00:29:36.779 align:start position:0% we'll update our state areas say that the<00:29:34.360> balance<00:29:34.750> is<00:29:34.990> less<00:29:35.860> than<00:29:36.100> that<00:29:36.370> how<00:29:36.580> much 00:29:36.779 --> 00:29:36.789 align:start position:0% the balance is less than that how much 00:29:36.789 --> 00:29:39.119 align:start position:0% the balance is less than that how much we'll<00:29:37.720> say<00:29:37.809> that<00:29:37.960> there's<00:29:38.139> been<00:29:38.350> a<00:29:38.379> one<00:29:38.889> that 00:29:39.119 --> 00:29:39.129 align:start position:0% we'll say that there's been a one that 00:29:39.129 --> 00:29:42.810 align:start position:0% we'll say that there's been a one that is<00:29:39.279> called<00:29:39.899> yes<00:29:40.899> and<00:29:41.169> no<00:29:41.710> notice<00:29:42.129> and<00:29:42.490> then 00:29:42.810 --> 00:29:42.820 align:start position:0% is called yes and no notice and then 00:29:42.820 --> 00:29:45.690 align:start position:0% is called yes and no notice and then we'll<00:29:42.970> continue<00:29:43.889> and<00:29:44.889> otherwise<00:29:45.340> what<00:29:45.580> will 00:29:45.690 --> 00:29:45.700 align:start position:0% we'll continue and otherwise what will 00:29:45.700 --> 00:29:50.190 align:start position:0% we'll continue and otherwise what will do<00:29:45.850> it<00:29:46.690> will<00:29:46.899> say<00:29:47.080> that<00:29:48.690> the<00:29:49.690> balance<00:29:50.080> is 00:29:50.190 --> 00:29:50.200 align:start position:0% do it will say that the balance is 00:29:50.200 --> 00:29:51.110 align:start position:0% do it will say that the balance is unchanged 00:29:51.110 --> 00:29:51.120 align:start position:0% unchanged 00:29:51.120 --> 00:29:55.180 align:start position:0% unchanged okay<00:29:52.120> is<00:29:52.179> unchanged<00:29:52.720> but<00:29:52.929> there's 00:29:55.180 --> 00:29:55.190 align:start position:0% 00:29:55.190 --> 00:30:01.870 align:start position:0% and<00:29:56.190> we'll<00:29:56.490> continue<00:29:56.690> and<00:29:57.740> then<00:30:00.500> at<00:30:01.500> the<00:30:01.710> end 00:30:01.870 --> 00:30:01.880 align:start position:0% and we'll continue and then at the end 00:30:01.880 --> 00:30:04.160 align:start position:0% and we'll continue and then at the end we'll<00:30:02.880> need<00:30:03.000> to<00:30:03.180> commit<00:30:03.690> the<00:30:03.870> final 00:30:04.160 --> 00:30:04.170 align:start position:0% we'll need to commit the final 00:30:04.170 --> 00:30:05.630 align:start position:0% we'll need to commit the final transaction<00:30:04.530> when<00:30:04.830> the<00:30:04.920> balance<00:30:05.190> is<00:30:05.310> empty 00:30:05.630 --> 00:30:05.640 align:start position:0% transaction when the balance is empty 00:30:05.640 --> 00:30:07.790 align:start position:0% transaction when the balance is empty and<00:30:05.970> then<00:30:06.360> we'll<00:30:06.510> return<00:30:06.630> the<00:30:07.110> OTAs<00:30:07.500> in<00:30:07.710> the 00:30:07.790 --> 00:30:07.800 align:start position:0% and then we'll return the OTAs in the 00:30:07.800 --> 00:30:12.470 align:start position:0% and then we'll return the OTAs in the mix<00:30:08.120> okay<00:30:09.120> so<00:30:09.720> we<00:30:09.840> just<00:30:09.870> fruit<00:30:10.200> 63<00:30:11.190> lives<00:30:11.430> and<00:30:11.970> I 00:30:12.470 --> 00:30:12.480 align:start position:0% mix okay so we just fruit 63 lives and I 00:30:12.480 --> 00:30:16.100 align:start position:0% mix okay so we just fruit 63 lives and I hope<00:30:12.660> that<00:30:12.870> it<00:30:12.990> belts<00:30:13.320> not<00:30:13.950> to<00:30:14.250> beard<00:30:15.110> it 00:30:16.100 --> 00:30:16.110 align:start position:0% hope that it belts not to beard it 00:30:16.110 --> 00:30:18.860 align:start position:0% hope that it belts not to beard it doesn't<00:30:16.530> feel<00:30:16.800> like<00:30:17.130> rating<00:30:17.580> saluting<00:30:18.120> it 00:30:18.860 --> 00:30:18.870 align:start position:0% doesn't feel like rating saluting it 00:30:18.870 --> 00:30:20.750 align:start position:0% doesn't feel like rating saluting it doesn't<00:30:19.230> feel<00:30:19.530> like<00:30:20.190> writing<00:30:20.430> a<00:30:20.550> smart 00:30:20.750 --> 00:30:20.760 align:start position:0% doesn't feel like writing a smart 00:30:20.760 --> 00:30:23.090 align:start position:0% doesn't feel like writing a smart contract<00:30:20.940> it<00:30:21.870> feels<00:30:22.110> like<00:30:22.560> reading<00:30:22.830> the<00:30:22.920> whole 00:30:23.090 --> 00:30:23.100 align:start position:0% contract it feels like reading the whole 00:30:23.100 --> 00:30:25.100 align:start position:0% contract it feels like reading the whole done<00:30:23.280> behind<00:30:24.090> the<00:30:24.330> scenes<00:30:24.420> what<00:30:24.840> we're<00:30:24.990> going 00:30:25.100 --> 00:30:25.110 align:start position:0% done behind the scenes what we're going 00:30:25.110 --> 00:30:26.570 align:start position:0% done behind the scenes what we're going to<00:30:25.140> do<00:30:25.290> is<00:30:25.530> we're<00:30:25.680> going<00:30:25.710> to<00:30:25.860> automatically 00:30:26.570 --> 00:30:26.580 align:start position:0% to do is we're going to automatically 00:30:26.580 --> 00:30:30.200 align:start position:0% to do is we're going to automatically synthesize<00:30:27.350> the<00:30:28.350> front<00:30:28.650> end<00:30:28.830> code<00:30:29.040> and<00:30:29.820> we're 00:30:30.200 --> 00:30:30.210 align:start position:0% synthesize the front end code and we're 00:30:30.210 --> 00:30:32.680 align:start position:0% synthesize the front end code and we're about<00:30:30.420> to<00:30:30.630> synthesizing<00:30:31.290> a<00:30:31.320> contract<00:30:31.740> out 00:30:32.680 --> 00:30:32.690 align:start position:0% about to synthesizing a contract out 00:30:32.690 --> 00:30:36.140 align:start position:0% about to synthesizing a contract out let's<00:30:33.690> go<00:30:33.870> to<00:30:33.930> the<00:30:34.110> terminal<00:30:34.320> and<00:30:34.970> see<00:30:35.970> what 00:30:36.140 --> 00:30:36.150 align:start position:0% let's go to the terminal and see what 00:30:36.150 --> 00:30:39.830 align:start position:0% let's go to the terminal and see what type<00:30:36.510> of<00:30:36.540> a<00:30:36.750> name<00:30:36.980> and<00:30:37.980> then<00:30:38.970> so<00:30:39.570> we'll<00:30:39.690> take 00:30:39.830 --> 00:30:39.840 align:start position:0% type of a name and then so we'll take 00:30:39.840 --> 00:30:43.760 align:start position:0% type of a name and then so we'll take make<00:30:40.080> building<00:30:41.330> and<00:30:42.330> what<00:30:43.290> it's<00:30:43.410> going<00:30:43.440> to<00:30:43.560> do 00:30:43.760 --> 00:30:43.770 align:start position:0% make building and what it's going to do 00:30:43.770 --> 00:30:46.640 align:start position:0% make building and what it's going to do is<00:30:44.190> it's<00:30:44.370> going<00:30:44.520> to<00:30:44.820> run<00:30:45.180> the<00:30:45.300> compiler<00:30:45.570> oh<00:30:46.080> I 00:30:46.640 --> 00:30:46.650 align:start position:0% is it's going to run the compiler oh I 00:30:46.650 --> 00:30:50.630 align:start position:0% is it's going to run the compiler oh I made<00:30:47.250> no<00:30:47.340> mistakes<00:30:49.190> so<00:30:50.190> I<00:30:50.220> don't<00:30:50.460> know<00:30:50.550> about 00:30:50.630 --> 00:30:50.640 align:start position:0% made no mistakes so I don't know about 00:30:50.640 --> 00:30:53.570 align:start position:0% made no mistakes so I don't know about you<00:30:50.970> guys<00:30:51.150> but<00:30:51.630> I'm<00:30:52.170> a<00:30:52.500> master<00:30:52.920> and<00:30:53.250> a<00:30:53.400> lot<00:30:53.550> of 00:30:53.570 --> 00:30:53.580 align:start position:0% you guys but I'm a master and a lot of 00:30:53.580 --> 00:30:55.700 align:start position:0% you guys but I'm a master and a lot of the<00:30:53.670> time<00:30:53.850> my<00:30:54.060> students<00:30:54.420> make<00:30:54.690> mistakes<00:30:55.200> when 00:30:55.700 --> 00:30:55.710 align:start position:0% the time my students make mistakes when 00:30:55.710 --> 00:30:58.010 align:start position:0% the time my students make mistakes when they<00:30:55.800> write<00:30:55.950> paragraphs<00:30:56.220> okay<00:30:57.150> this<00:30:57.750> is<00:30:57.870> why 00:30:58.010 --> 00:30:58.020 align:start position:0% they write paragraphs okay this is why 00:30:58.020 --> 00:31:00.080 align:start position:0% they write paragraphs okay this is why you<00:30:58.200> shouldn't<00:30:58.590> hire<00:30:58.830> them<00:30:59.160> to<00:30:59.520> write<00:30:59.940> their 00:31:00.080 --> 00:31:00.090 align:start position:0% you shouldn't hire them to write their 00:31:00.090 --> 00:31:02.630 align:start position:0% you shouldn't hire them to write their verified<00:31:00.570> compilers<00:31:01.110> you<00:31:01.860> should<00:31:02.010> hire<00:31:02.130> me<00:31:02.250> to 00:31:02.630 --> 00:31:02.640 align:start position:0% verified compilers you should hire me to 00:31:02.640 --> 00:31:04.110 align:start position:0% verified compilers you should hire me to write<00:31:02.760> over 00:31:04.110 --> 00:31:04.120 align:start position:0% write over 00:31:04.120 --> 00:31:07.450 align:start position:0% write over first<00:31:05.120> time<00:31:05.350> now<00:31:06.380> let's<00:31:06.860> me<00:31:06.950> go<00:31:06.980> back<00:31:07.190> for<00:31:07.429> a 00:31:07.450 --> 00:31:07.460 align:start position:0% first time now let's me go back for a 00:31:07.460 --> 00:31:12.250 align:start position:0% first time now let's me go back for a moment<00:31:07.610> and<00:31:08.559> look<00:31:09.559> at<00:31:09.650> what<00:31:09.830> we<00:31:09.950> read<00:31:10.990> now<00:31:11.990> what 00:31:12.250 --> 00:31:12.260 align:start position:0% moment and look at what we read now what 00:31:12.260 --> 00:31:13.299 align:start position:0% moment and look at what we read now what if<00:31:12.320> we<00:31:12.440> made<00:31:12.590> a<00:31:12.620> mistake 00:31:13.299 --> 00:31:13.309 align:start position:0% if we made a mistake 00:31:13.309 --> 00:31:15.910 align:start position:0% if we made a mistake so<00:31:14.140> obviously<00:31:15.140> this<00:31:15.350> it<00:31:15.500> would<00:31:15.620> be<00:31:15.650> totally 00:31:15.910 --> 00:31:15.920 align:start position:0% so obviously this it would be totally 00:31:15.920 --> 00:31:17.890 align:start position:0% so obviously this it would be totally stupid<00:31:16.309> but<00:31:17.000> what<00:31:17.179> if<00:31:17.270> we<00:31:17.390> accidentally 00:31:17.890 --> 00:31:17.900 align:start position:0% stupid but what if we accidentally 00:31:17.900 --> 00:31:20.820 align:start position:0% stupid but what if we accidentally subtracted<00:31:18.650> how<00:31:19.190> much<00:31:19.490> and<00:31:19.790> then<00:31:20.179> added<00:31:20.510> one 00:31:20.820 --> 00:31:20.830 align:start position:0% subtracted how much and then added one 00:31:20.830 --> 00:31:22.900 align:start position:0% subtracted how much and then added one there's<00:31:21.830> no<00:31:21.920> off<00:31:22.070> by<00:31:22.280> one<00:31:22.490> error<00:31:22.700> in<00:31:22.850> our 00:31:22.900 --> 00:31:22.910 align:start position:0% there's no off by one error in our 00:31:22.910 --> 00:31:26.260 align:start position:0% there's no off by one error in our program<00:31:23.890> now<00:31:24.890> I've<00:31:25.460> never<00:31:25.730> made<00:31:25.940> not<00:31:26.120> that 00:31:26.260 --> 00:31:26.270 align:start position:0% program now I've never made not that 00:31:26.270 --> 00:31:28.260 align:start position:0% program now I've never made not that whatever<00:31:26.510> program<00:31:27.020> but<00:31:27.110> I've<00:31:27.200> heard<00:31:27.410> of<00:31:27.559> it 00:31:28.260 --> 00:31:28.270 align:start position:0% whatever program but I've heard of it 00:31:28.270 --> 00:31:31.240 align:start position:0% whatever program but I've heard of it okay<00:31:29.270> let's<00:31:30.140> try<00:31:30.230> to<00:31:30.290> compile<00:31:30.710> and<00:31:30.950> see<00:31:31.130> what 00:31:31.240 --> 00:31:31.250 align:start position:0% okay let's try to compile and see what 00:31:31.250 --> 00:31:39.510 align:start position:0% okay let's try to compile and see what happens 00:31:39.510 --> 00:31:39.520 align:start position:0% 00:31:39.520 --> 00:31:41.950 align:start position:0% I'm<00:31:40.520> suspicious<00:31:41.000> that<00:31:41.420> maybe<00:31:41.540> it's<00:31:41.900> not 00:31:41.950 --> 00:31:41.960 align:start position:0% I'm suspicious that maybe it's not 00:31:41.960 --> 00:31:50.290 align:start position:0% I'm suspicious that maybe it's not looking<00:31:42.320> in<00:31:42.410> smile<00:31:46.900> hmm<00:31:47.900> okay<00:31:49.120> I'm<00:31:50.120> really 00:31:50.290 --> 00:31:50.300 align:start position:0% looking in smile hmm okay I'm really 00:31:50.300 --> 00:31:58.690 align:start position:0% looking in smile hmm okay I'm really nervous<00:31:56.740> one<00:31:57.740> of<00:31:57.830> the<00:31:57.920> one<00:31:58.190> of<00:31:58.220> the<00:31:58.280> annoyances 00:31:58.690 --> 00:31:58.700 align:start position:0% nervous one of the one of the annoyances 00:31:58.700 --> 00:32:00.250 align:start position:0% nervous one of the one of the annoyances with<00:31:58.910> doctor<00:31:59.240> is<00:31:59.330> that<00:31:59.420> sometimes<00:31:59.840> doesn't 00:32:00.250 --> 00:32:00.260 align:start position:0% with doctor is that sometimes doesn't 00:32:00.260 --> 00:32:07.210 align:start position:0% with doctor is that sometimes doesn't copy 00:32:07.210 --> 00:32:07.220 align:start position:0% 00:32:07.220 --> 00:32:09.769 align:start position:0% ok<00:32:08.220> hold<00:32:08.850> up<00:32:08.970> talking<00:32:09.330> about<00:32:09.359> that<00:32:09.570> for<00:32:09.690> a 00:32:09.769 --> 00:32:09.779 align:start position:0% ok hold up talking about that for a 00:32:09.779 --> 00:32:12.169 align:start position:0% ok hold up talking about that for a moment<00:32:10.580> what<00:32:11.580> I'm<00:32:11.669> going<00:32:11.789> to<00:32:11.850> show<00:32:11.940> you<00:32:11.970> right 00:32:12.169 --> 00:32:12.179 align:start position:0% moment what I'm going to show you right 00:32:12.179 --> 00:32:14.539 align:start position:0% moment what I'm going to show you right now<00:32:12.239> is<00:32:12.389> what<00:32:13.169> we<00:32:13.559> make<00:32:13.889> what<00:32:14.159> the<00:32:14.249> compiler 00:32:14.539 --> 00:32:14.549 align:start position:0% now is what we make what the compiler 00:32:14.549 --> 00:32:18.200 align:start position:0% now is what we make what the compiler produced<00:32:16.759> so<00:32:17.759> if<00:32:17.820> there's<00:32:17.970> an<00:32:18.090> adult 00:32:18.200 --> 00:32:18.210 align:start position:0% produced so if there's an adult 00:32:18.210 --> 00:32:20.989 align:start position:0% produced so if there's an adult directory<00:32:18.779> and<00:32:19.249> we'll<00:32:20.249> look<00:32:20.369> at<00:32:20.519> the<00:32:20.669> saloon 00:32:20.989 --> 00:32:20.999 align:start position:0% directory and we'll look at the saloon 00:32:20.999 --> 00:32:23.450 align:start position:0% directory and we'll look at the saloon because<00:32:21.299> it<00:32:21.450> was<00:32:21.570> generating<00:32:22.109> so<00:32:23.100> right<00:32:23.309> now 00:32:23.450 --> 00:32:23.460 align:start position:0% because it was generating so right now 00:32:23.460 --> 00:32:27.519 align:start position:0% because it was generating so right now the<00:32:23.970> reach<00:32:24.090> language<00:32:24.539> can<00:32:25.440> in<00:32:25.859> principle 00:32:27.519 --> 00:32:27.529 align:start position:0% the reach language can in principle 00:32:27.529 --> 00:32:29.690 align:start position:0% the reach language can in principle produce<00:32:28.529> things<00:32:28.679> other<00:32:28.980> than<00:32:29.070> a<00:32:29.220> theory<00:32:29.489> but 00:32:29.690 --> 00:32:29.700 align:start position:0% produce things other than a theory but 00:32:29.700 --> 00:32:31.840 align:start position:0% produce things other than a theory but right<00:32:29.879> now<00:32:29.999> the<00:32:30.059> only<00:32:30.269> part<00:32:30.509> of<00:32:30.629> the<00:32:30.690> theory 00:32:31.840 --> 00:32:31.850 align:start position:0% right now the only part of the theory 00:32:31.850 --> 00:32:34.639 align:start position:0% right now the only part of the theory this<00:32:32.850> is<00:32:32.940> the<00:32:33.059> contract<00:32:33.509> that<00:32:33.570> came<00:32:33.869> out<00:32:34.049> so 00:32:34.639 --> 00:32:34.649 align:start position:0% this is the contract that came out so 00:32:34.649 --> 00:32:37.340 align:start position:0% this is the contract that came out so this<00:32:34.769> program<00:32:35.090> this<00:32:36.090> contract<00:32:36.960> is<00:32:37.080> come 00:32:37.340 --> 00:32:37.350 align:start position:0% this program this contract is come 00:32:37.350 --> 00:32:39.409 align:start position:0% this program this contract is come certainly<00:32:37.739> laborious<00:32:38.489> embers<00:32:38.820> so<00:32:39.299> there's 00:32:39.409 --> 00:32:39.419 align:start position:0% certainly laborious embers so there's 00:32:39.419 --> 00:32:41.509 align:start position:0% certainly laborious embers so there's 100<00:32:39.779> nod2<00:32:40.139> lives<00:32:40.440> you<00:32:40.830> can<00:32:40.980> look<00:32:41.159> at<00:32:41.279> if<00:32:41.460> you 00:32:41.509 --> 00:32:41.519 align:start position:0% 100 nod2 lives you can look at if you 00:32:41.519 --> 00:32:42.859 align:start position:0% 100 nod2 lives you can look at if you want<00:32:41.549> to<00:32:41.759> send<00:32:41.879> them<00:32:41.970> to<00:32:42.029> the<00:32:42.539> Builder 00:32:42.859 --> 00:32:42.869 align:start position:0% want to send them to the Builder 00:32:42.869 --> 00:32:44.599 align:start position:0% want to send them to the Builder everything<00:32:43.320> right<00:32:43.470> in<00:32:43.559> yourself<00:32:43.830> and<00:32:44.190> let's 00:32:44.599 --> 00:32:44.609 align:start position:0% everything right in yourself and let's 00:32:44.609 --> 00:32:46.389 align:start position:0% everything right in yourself and let's just<00:32:44.789> look<00:32:44.879> at<00:32:45.029> like<00:32:45.210> one<00:32:45.480> little<00:32:45.629> part<00:32:45.989> of<00:32:46.019> it 00:32:46.389 --> 00:32:46.399 align:start position:0% just look at like one little part of it 00:32:46.399 --> 00:32:50.919 align:start position:0% just look at like one little part of it so<00:32:47.399> let's<00:32:47.519> look<00:32:47.580> right<00:32:47.730> here<00:32:47.970> at<00:32:48.149> message<00:32:48.899> six 00:32:50.919 --> 00:32:50.929 align:start position:0% so let's look right here at message six 00:32:50.929 --> 00:32:55.549 align:start position:0% so let's look right here at message six so<00:32:51.929> message<00:32:52.649> six<00:32:52.980> is<00:32:53.549> a<00:32:53.789> message<00:32:54.149> that<00:32:54.419> has<00:32:54.600> all 00:32:55.549 --> 00:32:55.559 align:start position:0% so message six is a message that has all 00:32:55.559 --> 00:32:57.680 align:start position:0% so message six is a message that has all these<00:32:55.889> parameters<00:32:56.429> and<00:32:56.669> let's<00:32:57.299> try<00:32:57.389> to<00:32:57.480> see<00:32:57.659> if 00:32:57.680 --> 00:32:57.690 align:start position:0% these parameters and let's try to see if 00:32:57.690 --> 00:33:00.499 align:start position:0% these parameters and let's try to see if what's<00:32:57.989> going<00:32:58.230> on<00:32:58.549> so<00:32:59.549> it<00:33:00.090> says<00:33:00.299> right<00:33:00.330> here 00:33:00.499 --> 00:33:00.509 align:start position:0% what's going on so it says right here 00:33:00.509 --> 00:33:03.470 align:start position:0% what's going on so it says right here that<00:33:00.929> it<00:33:01.200> must<00:33:01.409> have<00:33:01.529> come<00:33:01.769> from<00:33:02.039> a<00:33:02.309> zero<00:33:02.639> that 00:33:03.470 --> 00:33:03.480 align:start position:0% that it must have come from a zero that 00:33:03.480 --> 00:33:06.139 align:start position:0% that it must have come from a zero that the<00:33:03.509> block<00:33:03.929> number<00:33:04.200> is<00:33:04.830> less<00:33:05.309> than<00:33:05.340> the<00:33:05.879> delay 00:33:06.139 --> 00:33:06.149 align:start position:0% the block number is less than the delay 00:33:06.149 --> 00:33:11.090 align:start position:0% the block number is less than the delay going<00:33:06.450> in<00:33:06.539> there<00:33:06.749> the<00:33:07.350> value<00:33:07.889> has<00:33:08.190> to<00:33:08.220> be<00:33:08.369> 0 00:33:11.090 --> 00:33:11.100 align:start position:0% 00:33:11.100 --> 00:33:12.770 align:start position:0% that's<00:33:11.370> one<00:33:11.730> of<00:33:11.820> the<00:33:11.880> messages<00:33:12.270> that<00:33:12.330> doesn't 00:33:12.770 --> 00:33:12.780 align:start position:0% that's one of the messages that doesn't 00:33:12.780 --> 00:33:15.650 align:start position:0% that's one of the messages that doesn't have<00:33:12.929> a<00:33:12.960> payment<00:33:13.410> with<00:33:13.440> that<00:33:13.710> over<00:33:14.070> these<00:33:14.970> 17 00:33:15.650 --> 00:33:15.660 align:start position:0% have a payment with that over these 17 00:33:15.660 --> 00:33:17.810 align:start position:0% have a payment with that over these 17 has<00:33:16.049> to<00:33:16.169> be<00:33:16.260> smaller<00:33:16.559> than<00:33:16.799> to<00:33:16.919> be<00:33:17.010> aimed<00:33:17.280> of 00:33:17.810 --> 00:33:17.820 align:start position:0% has to be smaller than to be aimed of 00:33:17.820 --> 00:33:20.450 align:start position:0% has to be smaller than to be aimed of least<00:33:18.179> 17<00:33:18.630> that's<00:33:18.900> how<00:33:19.110> much<00:33:19.380> he<00:33:19.950> ate<00:33:20.070> was<00:33:20.309> the 00:33:20.450 --> 00:33:20.460 align:start position:0% least 17 that's how much he ate was the 00:33:20.460 --> 00:33:24.320 align:start position:0% least 17 that's how much he ate was the balance<00:33:20.940> then<00:33:21.929> what<00:33:22.049> we<00:33:22.140> do<00:33:22.289> is<00:33:22.590> we<00:33:23.330> commit 00:33:24.320 --> 00:33:24.330 align:start position:0% balance then what we do is we commit 00:33:24.330 --> 00:33:26.000 align:start position:0% balance then what we do is we commit that<00:33:24.480> and<00:33:24.840> then<00:33:24.960> update<00:33:25.380> the<00:33:25.410> state 00:33:26.000 --> 00:33:26.010 align:start position:0% that and then update the state 00:33:26.010 --> 00:33:28.669 align:start position:0% that and then update the state so<00:33:26.429> with<00:33:26.730> this<00:33:26.880> messages<00:33:27.510> this<00:33:27.780> event<00:33:28.440> number 00:33:28.669 --> 00:33:28.679 align:start position:0% so with this messages this event number 00:33:28.679 --> 00:33:30.740 align:start position:0% so with this messages this event number six<00:33:28.919> is<00:33:29.250> the<00:33:29.490> six<00:33:29.789> thing<00:33:30.059> in<00:33:30.210> our<00:33:30.299> program 00:33:30.740 --> 00:33:30.750 align:start position:0% six is the six thing in our program 00:33:30.750 --> 00:33:34.460 align:start position:0% six is the six thing in our program which<00:33:31.650> is<00:33:32.250> this<00:33:33.179> step<00:33:33.510> right<00:33:33.690> here<00:33:33.750> and<00:33:34.380> this 00:33:34.460 --> 00:33:34.470 align:start position:0% which is this step right here and this 00:33:34.470 --> 00:33:36.409 align:start position:0% which is this step right here and this publication<00:33:34.890> right<00:33:35.190> here<00:33:35.340> when<00:33:35.940> the<00:33:36.150> child 00:33:36.409 --> 00:33:36.419 align:start position:0% publication right here when the child 00:33:36.419 --> 00:33:38.930 align:start position:0% publication right here when the child says<00:33:36.780> here's<00:33:37.410> how<00:33:37.500> much<00:33:37.710> I<00:33:37.860> want<00:33:38.160> and<00:33:38.760> when<00:33:38.880> you 00:33:38.930 --> 00:33:38.940 align:start position:0% says here's how much I want and when you 00:33:38.940 --> 00:33:41.390 align:start position:0% says here's how much I want and when you go<00:33:39.090> to<00:33:39.150> the<00:33:39.360> contract<00:33:39.840> we<00:33:40.020> require<00:33:40.530> that<00:33:41.220> how 00:33:41.390 --> 00:33:41.400 align:start position:0% go to the contract we require that how 00:33:41.400 --> 00:33:46.730 align:start position:0% go to the contract we require that how much<00:33:41.549> does<00:33:41.730> my<00:33:41.850> eye<00:33:41.880> care<00:33:42.210> I<00:33:45.590> realized<00:33:46.590> by<00:33:46.679> the 00:33:46.730 --> 00:33:46.740 align:start position:0% much does my eye care I realized by the 00:33:46.740 --> 00:33:50.360 align:start position:0% much does my eye care I realized by the way<00:33:46.860> why<00:33:47.220> the<00:33:47.960> by<00:33:48.960> that<00:33:49.200> allowed<00:33:50.190> us<00:33:50.220> to 00:33:50.360 --> 00:33:50.370 align:start position:0% way why the by that allowed us to 00:33:50.370 --> 00:33:52.130 align:start position:0% way why the by that allowed us to comment<00:33:50.700> on<00:33:50.880> that<00:33:51.000> line<00:33:51.240> because<00:33:51.750> actually 00:33:52.130 --> 00:33:52.140 align:start position:0% comment on that line because actually 00:33:52.140 --> 00:33:55.159 align:start position:0% comment on that line because actually commented<00:33:52.559> out<00:33:52.620> the<00:33:52.799> line<00:33:52.980> that<00:33:53.720> that<00:33:54.720> was<00:33:54.960> the 00:33:55.159 --> 00:33:55.169 align:start position:0% commented out the line that that was the 00:33:55.169 --> 00:33:57.350 align:start position:0% commented out the line that that was the assertion<00:33:55.650> rather<00:33:56.190> than<00:33:56.429> the<00:33:56.549> line<00:33:56.730> that<00:33:57.030> made 00:33:57.350 --> 00:33:57.360 align:start position:0% assertion rather than the line that made 00:33:57.360 --> 00:34:00.200 align:start position:0% assertion rather than the line that made sure<00:33:57.539> the<00:33:57.780> assertion<00:33:58.140> was<00:33:58.260> right<00:33:58.970> so<00:33:59.970> I 00:34:00.200 --> 00:34:00.210 align:start position:0% sure the assertion was right so I 00:34:00.210 --> 00:34:08.260 align:start position:0% sure the assertion was right so I believe<00:34:00.570> that<00:34:00.600> if<00:34:00.960> I<00:34:01.080> comment<00:34:01.380> about<00:34:01.470> this<00:34:01.650> one 00:34:08.260 --> 00:34:08.270 align:start position:0% 00:34:08.270 --> 00:34:10.190 align:start position:0% all<00:34:09.270> right<00:34:09.359> now<00:34:09.480> I'm<00:34:09.720> not<00:34:09.869> really<00:34:10.020> nervous 00:34:10.190 --> 00:34:10.200 align:start position:0% all right now I'm not really nervous 00:34:10.200 --> 00:34:10.780 align:start position:0% all right now I'm not really nervous though 00:34:10.780 --> 00:34:10.790 align:start position:0% though 00:34:10.790 --> 00:34:25.500 align:start position:0% though Hey<00:34:12.110> sorry<00:34:14.230> okay<00:34:15.230> so 00:34:25.500 --> 00:34:25.510 align:start position:0% 00:34:25.510 --> 00:34:27.840 align:start position:0% now<00:34:26.379> let's<00:34:26.590> look<00:34:26.710> at<00:34:26.859> the<00:34:27.070> image<00:34:27.280> options<00:34:27.700> that 00:34:27.840 --> 00:34:27.850 align:start position:0% now let's look at the image options that 00:34:27.850 --> 00:34:30.720 align:start position:0% now let's look at the image options that they<00:34:27.970> generated<00:34:28.800> so<00:34:29.800> this<00:34:29.980> the<00:34:30.280> structure 00:34:30.720 --> 00:34:30.730 align:start position:0% they generated so this the structure 00:34:30.730 --> 00:34:34.950 align:start position:0% they generated so this the structure could<00:34:30.940> have<00:34:31.240> generated<00:34:33.179> is<00:34:34.179> the<00:34:34.480> code<00:34:34.690> for<00:34:34.720> the 00:34:34.950 --> 00:34:34.960 align:start position:0% could have generated is the code for the 00:34:34.960 --> 00:34:37.649 align:start position:0% could have generated is the code for the child<00:34:35.290> so<00:34:36.190> we<00:34:36.310> get<00:34:36.490> a<00:34:36.520> new<00:34:36.760> it's<00:34:37.119> called<00:34:37.270> child 00:34:37.649 --> 00:34:37.659 align:start position:0% child so we get a new it's called child 00:34:37.659 --> 00:34:40.470 align:start position:0% child so we get a new it's called child that<00:34:38.020> takes<00:34:38.230> as<00:34:38.409> an<00:34:39.220> argument<00:34:39.399> that<00:34:39.850> hand<00:34:40.179> over 00:34:40.470 --> 00:34:40.480 align:start position:0% that takes as an argument that hand over 00:34:40.480 --> 00:34:41.639 align:start position:0% that takes as an argument that hand over the<00:34:40.600> contract<00:34:40.960> will<00:34:41.139> see<00:34:41.260> this<00:34:41.350> given<00:34:41.590> a 00:34:41.639 --> 00:34:41.649 align:start position:0% the contract will see this given a 00:34:41.649 --> 00:34:44.369 align:start position:0% the contract will see this given a leader<00:34:41.889> and<00:34:42.190> the<00:34:42.879> interact<00:34:43.240> object<00:34:43.629> and<00:34:43.960> then 00:34:44.369 --> 00:34:44.379 align:start position:0% leader and the interact object and then 00:34:44.379 --> 00:34:46.139 align:start position:0% leader and the interact object and then it<00:34:44.470> goes<00:34:44.679> through<00:34:44.710> and<00:34:45.250> it<00:34:45.310> has<00:34:45.340> each<00:34:45.820> one<00:34:46.030> of 00:34:46.139 --> 00:34:46.149 align:start position:0% it goes through and it has each one of 00:34:46.149 --> 00:34:49.680 align:start position:0% it goes through and it has each one of the<00:34:46.240> pieces<00:34:46.419> of<00:34:46.869> the<00:34:47.109> program<00:34:47.730> so<00:34:48.730> just<00:34:49.540> make<00:34:49.659> a 00:34:49.680 --> 00:34:49.690 align:start position:0% the pieces of the program so just make a 00:34:49.690 --> 00:34:55.859 align:start position:0% the pieces of the program so just make a new<00:34:49.840> window<00:34:54.000> we<00:34:55.000> can<00:34:55.149> compare<00:34:55.540> the<00:34:55.659> two<00:34:55.690> of 00:34:55.859 --> 00:34:55.869 align:start position:0% new window we can compare the two of 00:34:55.869 --> 00:34:59.430 align:start position:0% new window we can compare the two of them<00:34:56.850> so<00:34:57.850> for<00:34:58.030> example<00:34:58.420> look<00:34:58.990> at<00:34:59.020> the<00:34:59.170> first 00:34:59.430 --> 00:34:59.440 align:start position:0% them so for example look at the first 00:34:59.440 --> 00:35:01.830 align:start position:0% them so for example look at the first one<00:34:59.710> that<00:34:59.830> took<00:34:59.950> the<00:35:00.130> child<00:35:00.310> does<00:35:00.600> the<00:35:01.600> child 00:35:01.830 --> 00:35:01.840 align:start position:0% one that took the child does the child 00:35:01.840 --> 00:35:10.859 align:start position:0% one that took the child does the child calls<00:35:02.340> requests<00:35:03.340> on<00:35:03.460> the<00:35:03.490> Internet<00:35:09.780> so<00:35:10.780> the 00:35:10.859 --> 00:35:10.869 align:start position:0% calls requests on the Internet so the 00:35:10.869 --> 00:35:12.120 align:start position:0% calls requests on the Internet so the very<00:35:11.020> first<00:35:11.170> thing<00:35:11.290> is<00:35:11.500> that<00:35:11.530> we<00:35:11.710> published 00:35:12.120 --> 00:35:12.130 align:start position:0% very first thing is that we published 00:35:12.130 --> 00:35:14.760 align:start position:0% very first thing is that we published nothing<00:35:12.490> and<00:35:12.730> then<00:35:13.359> we're<00:35:13.780> going<00:35:13.869> to<00:35:13.930> wait<00:35:14.170> or 00:35:14.760 --> 00:35:14.770 align:start position:0% nothing and then we're going to wait or 00:35:14.770 --> 00:35:18.930 align:start position:0% nothing and then we're going to wait or the<00:35:14.980> parent<00:35:15.369> to<00:35:15.790> publish<00:35:16.119> the<00:35:16.270> allowance<00:35:17.940> so 00:35:18.930 --> 00:35:18.940 align:start position:0% the parent to publish the allowance so 00:35:18.940 --> 00:35:20.580 align:start position:0% the parent to publish the allowance so we<00:35:19.060> look<00:35:19.210> at<00:35:19.270> the<00:35:19.359> code<00:35:19.570> the<00:35:20.020> very<00:35:20.200> first<00:35:20.440> thing 00:35:20.580 --> 00:35:20.590 align:start position:0% we look at the code the very first thing 00:35:20.590 --> 00:35:23.580 align:start position:0% we look at the code the very first thing that<00:35:20.619> happens<00:35:21.010> is<00:35:21.280> that<00:35:21.580> the<00:35:21.970> child<00:35:22.410> sends<00:35:23.410> and 00:35:23.580 --> 00:35:23.590 align:start position:0% that happens is that the child sends and 00:35:23.590 --> 00:35:26.280 align:start position:0% that happens is that the child sends and then<00:35:23.770> receive<00:35:24.130> special<00:35:24.730> message<00:35:25.180> one<00:35:25.420> with<00:35:26.050> no 00:35:26.280 --> 00:35:26.290 align:start position:0% then receive special message one with no 00:35:26.290 --> 00:35:28.890 align:start position:0% then receive special message one with no information<00:35:26.910> expecting<00:35:27.910> to<00:35:28.060> receive<00:35:28.180> event 00:35:28.890 --> 00:35:28.900 align:start position:0% information expecting to receive event 00:35:28.900 --> 00:35:31.770 align:start position:0% information expecting to receive event one<00:35:29.109> afterwards<00:35:29.940> or<00:35:30.940> event<00:35:31.270> two<00:35:31.480> of<00:35:31.630> those 00:35:31.770 --> 00:35:31.780 align:start position:0% one afterwards or event two of those 00:35:31.780 --> 00:35:35.120 align:start position:0% one afterwards or event two of those entitled<00:35:32.369> there<00:35:33.369> was<00:35:33.460> talent<00:35:33.700> nobody<00:35:34.359> do<00:35:34.540> is 00:35:35.120 --> 00:35:35.130 align:start position:0% entitled there was talent nobody do is 00:35:35.130 --> 00:35:38.790 align:start position:0% entitled there was talent nobody do is mean<00:35:36.130> to<00:35:36.460> you<00:35:36.640> or<00:35:36.850> both<00:35:37.260> remember<00:35:38.260> we<00:35:38.380> expect 00:35:38.790 --> 00:35:38.800 align:start position:0% mean to you or both remember we expect 00:35:38.800 --> 00:35:41.700 align:start position:0% mean to you or both remember we expect to<00:35:38.950> receive<00:35:39.310> event<00:35:40.090> three<00:35:40.420> and<00:35:40.720> event<00:35:41.410> three 00:35:41.700 --> 00:35:41.710 align:start position:0% to receive event three and event three 00:35:41.710 --> 00:35:45.740 align:start position:0% to receive event three and event three comes<00:35:42.400> with<00:35:43.080> these<00:35:44.080> five<00:35:44.320> this 00:35:45.740 --> 00:35:45.750 align:start position:0% comes with these five this 00:35:45.750 --> 00:35:47.500 align:start position:0% comes with these five this that<00:35:45.840> will<00:35:45.990> end<00:35:46.020> up<00:35:46.290> being<00:35:46.470> the<00:35:46.680> allowance 00:35:47.500 --> 00:35:47.510 align:start position:0% that will end up being the allowance 00:35:47.510 --> 00:35:50.810 align:start position:0% that will end up being the allowance okay<00:35:48.510> so<00:35:49.320> this<00:35:49.830> rest<00:35:50.310> of<00:35:50.400> the<00:35:50.460> curve<00:35:50.670> right 00:35:50.810 --> 00:35:50.820 align:start position:0% okay so this rest of the curve right 00:35:50.820 --> 00:35:53.780 align:start position:0% okay so this rest of the curve right here<00:35:50.900> is<00:35:51.900> you<00:35:52.290> know<00:35:52.380> no<00:35:52.800> code<00:35:53.280> that<00:35:53.460> a<00:35:53.490> human 00:35:53.780 --> 00:35:53.790 align:start position:0% here is you know no code that a human 00:35:53.790 --> 00:35:55.040 align:start position:0% here is you know no code that a human would<00:35:53.820> ever<00:35:53.970> write<00:35:54.180> but<00:35:54.780> it's<00:35:54.900> very 00:35:55.040 --> 00:35:55.050 align:start position:0% would ever write but it's very 00:35:55.050 --> 00:35:57.140 align:start position:0% would ever write but it's very straightforward<00:35:55.980> about<00:35:56.040> compilers<00:35:56.609> it<00:35:56.940> has 00:35:57.140 --> 00:35:57.150 align:start position:0% straightforward about compilers it has 00:35:57.150 --> 00:35:59.450 align:start position:0% straightforward about compilers it has wonderful<00:35:57.390> things<00:35:57.780> like<00:35:57.869> let<00:35:58.470> V<00:35:58.680> 9<00:35:58.859> equals<00:35:59.280> 0 00:35:59.450 --> 00:35:59.460 align:start position:0% wonderful things like let V 9 equals 0 00:35:59.460 --> 00:36:03.830 align:start position:0% wonderful things like let V 9 equals 0 because<00:36:00.030> let's<00:36:00.930> be<00:36:01.020> 9v9<00:36:01.890> is<00:36:02.880> the<00:36:03.300> count<00:36:03.570> for 00:36:03.830 --> 00:36:03.840 align:start position:0% because let's be 9v9 is the count for 00:36:03.840 --> 00:36:08.390 align:start position:0% because let's be 9v9 is the count for how<00:36:03.930> many<00:36:03.990> times<00:36:04.230> we<00:36:04.349> said<00:36:04.500> ok<00:36:06.560> alright<00:36:07.560> so<00:36:08.250> now 00:36:08.390 --> 00:36:08.400 align:start position:0% how many times we said ok alright so now 00:36:08.400 --> 00:36:10.370 align:start position:0% how many times we said ok alright so now what<00:36:08.550> we've<00:36:08.730> done<00:36:08.760> is<00:36:09.180> we've<00:36:09.630> written<00:36:09.840> the<00:36:10.140> bar 00:36:10.370 --> 00:36:10.380 align:start position:0% what we've done is we've written the bar 00:36:10.380 --> 00:36:14.150 align:start position:0% what we've done is we've written the bar for<00:36:11.280> every<00:36:11.520> reach<00:36:11.730> we've<00:36:12.540> compiled<00:36:13.020> it<00:36:13.260> behind 00:36:14.150 --> 00:36:14.160 align:start position:0% for every reach we've compiled it behind 00:36:14.160 --> 00:36:16.609 align:start position:0% for every reach we've compiled it behind the<00:36:14.280> scenes<00:36:14.520> it's<00:36:15.210> done<00:36:15.540> verification<00:36:16.320> for<00:36:16.500> us 00:36:16.609 --> 00:36:16.619 align:start position:0% the scenes it's done verification for us 00:36:16.619 --> 00:36:20.900 align:start position:0% the scenes it's done verification for us and<00:36:17.430> we<00:36:18.180> now<00:36:18.359> have<00:36:18.690> the<00:36:19.170> Johnson<00:36:19.890> poop<00:36:20.130> and<00:36:20.550> we 00:36:20.900 --> 00:36:20.910 align:start position:0% and we now have the Johnson poop and we 00:36:20.910 --> 00:36:22.580 align:start position:0% and we now have the Johnson poop and we have<00:36:21.090> this<00:36:21.240> ability<00:36:21.420> code<00:36:21.780> but<00:36:22.440> this 00:36:22.580 --> 00:36:22.590 align:start position:0% have this ability code but this 00:36:22.590 --> 00:36:24.800 align:start position:0% have this ability code but this javascript<00:36:23.130> code<00:36:23.250> that<00:36:23.460> we<00:36:23.520> have<00:36:23.730> the<00:36:24.510> only 00:36:24.800 --> 00:36:24.810 align:start position:0% javascript code that we have the only 00:36:24.810 --> 00:36:26.510 align:start position:0% javascript code that we have the only thing<00:36:24.960> that<00:36:25.080> it<00:36:25.170> does<00:36:25.349> is<00:36:25.619> it<00:36:25.830> provides<00:36:26.130> these 00:36:26.510 --> 00:36:26.520 align:start position:0% thing that it does is it provides these 00:36:26.520 --> 00:36:28.970 align:start position:0% thing that it does is it provides these high<00:36:27.030> level<00:36:27.420> up<00:36:28.050> these<00:36:28.410> high<00:36:28.619> level<00:36:28.859> functions 00:36:28.970 --> 00:36:28.980 align:start position:0% high level up these high level functions 00:36:28.980 --> 00:36:33.640 align:start position:0% high level up these high level functions to<00:36:29.580> spin<00:36:30.270> up<00:36:30.390> a<00:36:30.420> child<00:36:30.810> and<00:36:31.109> twos<00:36:31.500> enough<00:36:32.270> the 00:36:33.640 --> 00:36:33.650 align:start position:0% to spin up a child and twos enough the 00:36:33.650 --> 00:36:37.310 align:start position:0% to spin up a child and twos enough the parent<00:36:34.650> may<00:36:35.010> skip<00:36:35.369> down<00:36:35.930> there's<00:36:36.930> a<00:36:37.050> limit 00:36:37.310 --> 00:36:37.320 align:start position:0% parent may skip down there's a limit 00:36:37.320 --> 00:36:39.530 align:start position:0% parent may skip down there's a limit parents<00:36:37.740> and<00:36:37.920> then<00:36:38.340> we<00:36:38.430> also<00:36:38.580> and<00:36:38.880> then<00:36:39.060> you 00:36:39.530 --> 00:36:39.540 align:start position:0% parents and then we also and then you 00:36:39.540 --> 00:36:43.310 align:start position:0% parents and then we also and then you know<00:36:39.660> the<00:36:39.840> details<00:36:39.990> of<00:36:40.380> the<00:36:40.440> contract<00:36:40.700> know<00:36:42.320> we 00:36:43.310 --> 00:36:43.320 align:start position:0% know the details of the contract know we 00:36:43.320 --> 00:36:44.870 align:start position:0% know the details of the contract know we have<00:36:43.560> eight<00:36:43.710> minutes<00:36:43.859> left<00:36:44.130> so<00:36:44.700> we're<00:36:44.820> not 00:36:44.870 --> 00:36:44.880 align:start position:0% have eight minutes left so we're not 00:36:44.880 --> 00:36:47.990 align:start position:0% have eight minutes left so we're not going<00:36:45.060> to<00:36:45.119> break<00:36:45.270> by<00:36:45.599> in<00:36:45.960> the<00:36:46.770> front<00:36:47.640> encoder 00:36:47.990 --> 00:36:48.000 align:start position:0% going to break by in the front encoder 00:36:48.000 --> 00:36:50.690 align:start position:0% going to break by in the front encoder instead<00:36:48.690> I'll<00:36:48.810> show<00:36:49.050> you<00:36:49.109> the<00:36:49.320> front<00:36:49.580> so<00:36:50.580> what 00:36:50.690 --> 00:36:50.700 align:start position:0% instead I'll show you the front so what 00:36:50.700 --> 00:36:53.079 align:start position:0% instead I'll show you the front so what I'm<00:36:50.760> going<00:36:50.849> to<00:36:50.910> do<00:36:51.030> is<00:36:51.180> I'm<00:36:51.300> to<00:36:51.390> go<00:36:51.599> out<00:36:52.530> of<00:36:52.770> the 00:36:53.079 --> 00:36:53.089 align:start position:0% I'm going to do is I'm to go out of the 00:36:53.089 --> 00:36:56.270 align:start position:0% I'm going to do is I'm to go out of the app<00:36:54.089> directory<00:36:54.510> and<00:36:55.200> go<00:36:55.410> is<00:36:55.650> the<00:36:55.859> minimal 00:36:56.270 --> 00:36:56.280 align:start position:0% app directory and go is the minimal 00:36:56.280 --> 00:37:01.460 align:start position:0% app directory and go is the minimal directory<00:36:56.760> and<00:36:57.770> don't<00:36:58.770> look<00:36:58.950> at<00:36:59.960> the<00:37:00.960> index 00:37:01.460 --> 00:37:01.470 align:start position:0% directory and don't look at the index 00:37:01.470 --> 00:37:05.570 align:start position:0% directory and don't look at the index MJS<00:37:02.420> file<00:37:03.920> so<00:37:04.920> the<00:37:05.010> first<00:37:05.220> thing<00:37:05.369> that<00:37:05.400> we'll 00:37:05.570 --> 00:37:05.580 align:start position:0% MJS file so the first thing that we'll 00:37:05.580 --> 00:37:08.359 align:start position:0% MJS file so the first thing that we'll do<00:37:05.730> is<00:37:06.089> we'll<00:37:06.630> import<00:37:07.470> the<00:37:07.650> standard<00:37:08.010> library 00:37:08.359 --> 00:37:08.369 align:start position:0% do is we'll import the standard library 00:37:08.369 --> 00:37:11.260 align:start position:0% do is we'll import the standard library we'll<00:37:09.119> import<00:37:09.540> that<00:37:09.810> noticing<00:37:10.349> for<00:37:10.589> them 00:37:11.260 --> 00:37:11.270 align:start position:0% we'll import that noticing for them 00:37:11.270 --> 00:37:13.940 align:start position:0% we'll import that noticing for them well<00:37:12.270> Sid<00:37:12.540> our<00:37:12.750> starting<00:37:13.140> balance<00:37:13.349> and<00:37:13.800> then 00:37:13.940 --> 00:37:13.950 align:start position:0% well Sid our starting balance and then 00:37:13.950 --> 00:37:14.820 align:start position:0% well Sid our starting balance and then to<00:37:14.070> be 00:37:14.820 --> 00:37:14.830 align:start position:0% to be 00:37:14.830 --> 00:37:17.910 align:start position:0% to be we're<00:37:15.730> going<00:37:15.880> to<00:37:15.970> test<00:37:16.180> assignment<00:37:16.840> and<00:37:17.320> then 00:37:17.910 --> 00:37:17.920 align:start position:0% we're going to test assignment and then 00:37:17.920 --> 00:37:19.260 align:start position:0% we're going to test assignment and then we'll<00:37:18.040> scrape<00:37:18.280> a<00:37:18.340> new<00:37:18.610> account<00:37:18.940> for<00:37:19.120> the 00:37:19.260 --> 00:37:19.270 align:start position:0% we'll scrape a new account for the 00:37:19.270 --> 00:37:20.820 align:start position:0% we'll scrape a new account for the parents<00:37:19.600> that<00:37:19.900> have<00:37:20.110> that<00:37:20.350> starting<00:37:20.680> balance 00:37:20.820 --> 00:37:20.830 align:start position:0% parents that have that starting balance 00:37:20.830 --> 00:37:27.330 align:start position:0% parents that have that starting balance and<00:37:21.250> then<00:37:22.180> that's<00:37:22.540> going<00:37:22.780> to<00:37:22.930> deploy<00:37:23.380> the<00:37:26.340> W 00:37:27.330 --> 00:37:27.340 align:start position:0% and then that's going to deploy the W 00:37:27.340 --> 00:37:29.370 align:start position:0% and then that's going to deploy the W parent<00:37:27.700> unemployed<00:37:28.150> then<00:37:29.020> what<00:37:29.170> we're<00:37:29.260> going 00:37:29.370 --> 00:37:29.380 align:start position:0% parent unemployed then what we're going 00:37:29.380 --> 00:37:30.480 align:start position:0% parent unemployed then what we're going to<00:37:29.410> do<00:37:29.530> is<00:37:29.650> we're<00:37:29.770> going<00:37:29.800> to<00:37:29.920> define<00:37:30.070> the 00:37:30.480 --> 00:37:30.490 align:start position:0% to do is we're going to define the 00:37:30.490 --> 00:37:32.790 align:start position:0% to do is we're going to define the internet<00:37:30.820> project<00:37:31.210> and<00:37:31.900> for<00:37:32.410> this<00:37:32.500> first 00:37:32.790 --> 00:37:32.800 align:start position:0% internet project and for this first 00:37:32.800 --> 00:37:35.550 align:start position:0% internet project and for this first version<00:37:33.010> I'm<00:37:33.850> gonna<00:37:34.000> say<00:37:34.180> that<00:37:34.420> the<00:37:35.140> allowance 00:37:35.550 --> 00:37:35.560 align:start position:0% version I'm gonna say that the allowance 00:37:35.560 --> 00:37:37.230 align:start position:0% version I'm gonna say that the allowance is<00:37:35.650> always<00:37:35.950> going<00:37:36.130> to<00:37:36.160> be<00:37:36.220> fifteen<00:37:36.640> there<00:37:36.880> so<00:37:37.180> I 00:37:37.230 --> 00:37:37.240 align:start position:0% is always going to be fifteen there so I 00:37:37.240 --> 00:37:38.580 align:start position:0% is always going to be fifteen there so I just<00:37:37.390> write<00:37:37.540> this<00:37:37.690> function<00:37:37.840> that<00:37:38.170> money<00:37:38.410> that 00:37:38.580 --> 00:37:38.590 align:start position:0% just write this function that money that 00:37:38.590 --> 00:37:39.870 align:start position:0% just write this function that money that when<00:37:38.740> you<00:37:38.830> get<00:37:38.950> that<00:37:39.160> pause<00:37:39.340> with<00:37:39.520> allowance<00:37:39.820> I 00:37:39.870 --> 00:37:39.880 align:start position:0% when you get that pause with allowance I 00:37:39.880 --> 00:37:41.340 align:start position:0% when you get that pause with allowance I return<00:37:40.120> to<00:37:40.210> the<00:37:40.270> beaver<00:37:40.480> now<00:37:41.020> if<00:37:41.080> I<00:37:41.170> we're 00:37:41.340 --> 00:37:41.350 align:start position:0% return to the beaver now if I we're 00:37:41.350 --> 00:37:42.840 align:start position:0% return to the beaver now if I we're making<00:37:41.590> like<00:37:41.740> a<00:37:41.770> real<00:37:42.010> application<00:37:42.580> you<00:37:42.760> know 00:37:42.840 --> 00:37:42.850 align:start position:0% making like a real application you know 00:37:42.850 --> 00:37:44.820 align:start position:0% making like a real application you know I<00:37:42.880> might<00:37:43.180> have<00:37:43.210> a<00:37:43.390> pop<00:37:43.630> up<00:37:43.780> for<00:37:44.290> ever<00:37:44.410> and<00:37:44.680> oh 00:37:44.820 --> 00:37:44.830 align:start position:0% I might have a pop up for ever and oh 00:37:44.830 --> 00:37:46.320 align:start position:0% I might have a pop up for ever and oh you<00:37:44.980> mean<00:37:45.310> like<00:37:45.340> actually<00:37:45.970> do<00:37:46.090> a<00:37:46.120> real 00:37:46.320 --> 00:37:46.330 align:start position:0% you mean like actually do a real 00:37:46.330 --> 00:37:49.020 align:start position:0% you mean like actually do a real interaction<00:37:46.810> with<00:37:46.900> music<00:37:47.370> then<00:37:48.370> remember<00:37:48.820> our 00:37:49.020 --> 00:37:49.030 align:start position:0% interaction with music then remember our 00:37:49.030 --> 00:37:50.970 align:start position:0% interaction with music then remember our approval<00:37:49.480> function<00:37:49.840> and<00:37:50.230> our<00:37:50.350> cool<00:37:50.620> function 00:37:50.970 --> 00:37:50.980 align:start position:0% approval function and our cool function 00:37:50.980 --> 00:37:53.820 align:start position:0% approval function and our cool function this<00:37:51.250> is<00:37:51.370> a<00:37:51.400> really<00:37:51.730> nice<00:37:51.820> parent<00:37:52.830> aircrew 00:37:53.820 --> 00:37:53.830 align:start position:0% this is a really nice parent aircrew 00:37:53.830 --> 00:37:56.490 align:start position:0% this is a really nice parent aircrew function<00:37:54.220> is<00:37:54.340> true<00:37:54.910> okay<00:37:55.720> because<00:37:56.230> this<00:37:56.440> is 00:37:56.490 --> 00:37:56.500 align:start position:0% function is true okay because this is 00:37:56.500 --> 00:37:59.250 align:start position:0% function is true okay because this is just<00:37:56.680> for<00:37:56.770> testing<00:37:57.100> purposes<00:37:57.460> okay<00:37:58.110> then<00:37:59.110> what 00:37:59.250 --> 00:37:59.260 align:start position:0% just for testing purposes okay then what 00:37:59.260 --> 00:38:01.230 align:start position:0% just for testing purposes okay then what we'll<00:37:59.350> do<00:37:59.470> is<00:37:59.680> we'll<00:37:59.860> define<00:38:00.550> a<00:38:00.610> logo<00:38:01.180> that 00:38:01.230 --> 00:38:01.240 align:start position:0% we'll do is we'll define a logo that 00:38:01.240 --> 00:38:03.360 align:start position:0% we'll do is we'll define a logo that will<00:38:01.570> run<00:38:01.810> the<00:38:01.840> parent<00:38:02.500> function<00:38:02.620> so<00:38:03.280> the 00:38:03.360 --> 00:38:03.370 align:start position:0% will run the parent function so the 00:38:03.370 --> 00:38:05.400 align:start position:0% will run the parent function so the whole<00:38:03.580> month<00:38:03.850> is<00:38:03.970> it<00:38:04.120> but<00:38:04.270> can't<00:38:04.510> give<00:38:05.170> it<00:38:05.290> this 00:38:05.400 --> 00:38:05.410 align:start position:0% whole month is it but can't give it this 00:38:05.410 --> 00:38:06.720 align:start position:0% whole month is it but can't give it this contract<00:38:05.890> object<00:38:06.220> that<00:38:06.280> you<00:38:06.400> might<00:38:06.550> have<00:38:06.610> to 00:38:06.720 --> 00:38:06.730 align:start position:0% contract object that you might have to 00:38:06.730 --> 00:38:09.030 align:start position:0% contract object that you might have to play<00:38:06.970> into<00:38:07.660> that<00:38:07.780> interactive<00:38:08.290> function<00:38:08.650> and 00:38:09.030 --> 00:38:09.040 align:start position:0% play into that interactive function and 00:38:09.040 --> 00:38:11.340 align:start position:0% play into that interactive function and then<00:38:09.160> we'll<00:38:09.370> get<00:38:09.520> back<00:38:09.580> a<00:38:09.880> promise<00:38:10.390> for<00:38:11.230> the 00:38:11.340 --> 00:38:11.350 align:start position:0% then we'll get back a promise for the 00:38:11.350 --> 00:38:13.710 align:start position:0% then we'll get back a promise for the answer<00:38:11.800> that<00:38:12.190> will<00:38:12.340> eventually<00:38:12.670> come<00:38:13.060> out<00:38:13.390> of 00:38:13.710 --> 00:38:13.720 align:start position:0% answer that will eventually come out of 00:38:13.720 --> 00:38:16.920 align:start position:0% answer that will eventually come out of the<00:38:13.900> parent<00:38:14.230> when<00:38:14.560> it's<00:38:14.710> done<00:38:14.860> right<00:38:15.780> and<00:38:16.780> to 00:38:16.920 --> 00:38:16.930 align:start position:0% the parent when it's done right and to 00:38:16.930 --> 00:38:19.050 align:start position:0% the parent when it's done right and to do<00:38:17.020> something<00:38:17.290> similar<00:38:17.590> to<00:38:17.740> the<00:38:17.980> child<00:38:18.220> will 00:38:19.050 --> 00:38:19.060 align:start position:0% do something similar to the child will 00:38:19.060 --> 00:38:20.850 align:start position:0% do something similar to the child will start<00:38:19.210> it<00:38:19.360> off<00:38:19.450> with<00:38:19.480> the<00:38:19.720> balance<00:38:20.110> and<00:38:20.380> just 00:38:20.850 --> 00:38:20.860 align:start position:0% start it off with the balance and just 00:38:20.860 --> 00:38:22.350 align:start position:0% start it off with the balance and just because<00:38:21.100> I'm<00:38:21.220> lazy<00:38:21.430> in<00:38:21.640> this<00:38:21.760> test<00:38:22.000> I<00:38:22.120> mean<00:38:22.270> to 00:38:22.350 --> 00:38:22.360 align:start position:0% because I'm lazy in this test I mean to 00:38:22.360 --> 00:38:27.210 align:start position:0% because I'm lazy in this test I mean to start<00:38:22.570> in<00:38:22.630> exactly<00:38:23.200> the<00:38:23.530> same<00:38:23.710> so<00:38:26.130> and<00:38:27.130> you 00:38:27.210 --> 00:38:27.220 align:start position:0% start in exactly the same so and you 00:38:27.220 --> 00:38:29.450 align:start position:0% start in exactly the same so and you have<00:38:27.370> some<00:38:27.550> money<00:38:27.640> to<00:38:27.880> provide<00:38:28.150> the<00:38:28.210> gasoline 00:38:29.450 --> 00:38:29.460 align:start position:0% have some money to provide the gasoline 00:38:29.460 --> 00:38:32.990 align:start position:0% have some money to provide the gasoline then<00:38:30.240> the<00:38:30.359> child<00:38:30.599> will<00:38:31.109> attach<00:38:31.559> to<00:38:32.369> the 00:38:32.990 --> 00:38:33.000 align:start position:0% then the child will attach to the 00:38:33.000 --> 00:38:35.030 align:start position:0% then the child will attach to the multi-state<00:38:33.480> contract<00:38:33.900> and<00:38:34.500> when<00:38:34.619> you<00:38:34.680> attach 00:38:35.030 --> 00:38:35.040 align:start position:0% multi-state contract and when you attach 00:38:35.040 --> 00:38:37.160 align:start position:0% multi-state contract and when you attach versus<00:38:35.490> deployed<00:38:35.880> he<00:38:36.450> doesn't<00:38:36.780> say<00:38:36.900> what<00:38:37.140> the 00:38:37.160 --> 00:38:37.170 align:start position:0% versus deployed he doesn't say what the 00:38:37.170 --> 00:38:38.809 align:start position:0% versus deployed he doesn't say what the address<00:38:37.650> of<00:38:37.800> the<00:38:37.890> contract<00:38:38.250> is<00:38:38.339> and<00:38:38.640> when<00:38:38.790> it 00:38:38.809 --> 00:38:38.819 align:start position:0% address of the contract is and when it 00:38:38.819 --> 00:38:39.559 align:start position:0% address of the contract is and when it was<00:38:39.000> created 00:38:39.559 --> 00:38:39.569 align:start position:0% was created 00:38:39.569 --> 00:38:40.790 align:start position:0% was created you<00:38:39.660> need<00:38:39.780> to<00:38:39.869> know<00:38:39.990> what<00:38:40.109> it<00:38:40.200> was<00:38:40.290> created<00:38:40.440> to 00:38:40.790 --> 00:38:40.800 align:start position:0% you need to know what it was created to 00:38:40.800 --> 00:38:43.660 align:start position:0% you need to know what it was created to the<00:38:40.890> you<00:38:41.010> know<00:38:41.190> they're<00:38:41.430> not<00:38:41.670> sending<00:38:41.910> people 00:38:43.660 --> 00:38:43.670 align:start position:0% the you know they're not sending people 00:38:43.670 --> 00:38:46.609 align:start position:0% the you know they're not sending people now<00:38:44.670> the<00:38:44.819> child<00:38:45.089> it's<00:38:45.420> gonna<00:38:45.569> say<00:38:45.809> I'm 00:38:46.609 --> 00:38:46.619 align:start position:0% now the child it's gonna say I'm 00:38:46.619 --> 00:38:48.620 align:start position:0% now the child it's gonna say I'm ingredient<00:38:47.160> Island<00:38:47.520> what<00:38:48.000> I<00:38:48.030> want<00:38:48.270> to<00:38:48.359> do<00:38:48.480> my 00:38:48.620 --> 00:38:48.630 align:start position:0% ingredient Island what I want to do my 00:38:48.630 --> 00:38:53.210 align:start position:0% ingredient Island what I want to do my request<00:38:48.990> is<00:38:49.140> everything<00:38:51.020> and<00:38:52.020> then<00:38:52.200> we'll<00:38:52.950> ask 00:38:53.210 --> 00:38:53.220 align:start position:0% request is everything and then we'll ask 00:38:53.220 --> 00:38:59.690 align:start position:0% request is everything and then we'll ask for<00:38:53.579> it<00:38:53.700> he<00:38:54.470> apparently<00:38:58.040> will<00:38:59.040> wait<00:38:59.280> those<00:38:59.490> two 00:38:59.690 --> 00:38:59.700 align:start position:0% for it he apparently will wait those two 00:38:59.700 --> 00:39:01.670 align:start position:0% for it he apparently will wait those two in<00:38:59.880> there<00:39:00.359> let<00:39:00.839> me<00:39:00.869> just<00:39:00.930> pop<00:39:01.230> back<00:39:01.470> to<00:39:01.500> the 00:39:01.670 --> 00:39:01.680 align:start position:0% in there let me just pop back to the 00:39:01.680 --> 00:39:07.370 align:start position:0% in there let me just pop back to the comment<00:39:02.010> over<00:39:03.000> to<00:39:04.490> turn<00:39:05.490> over<00:39:05.700> here<00:39:05.990> and<00:39:06.990> we'll 00:39:07.370 --> 00:39:07.380 align:start position:0% comment over to turn over here and we'll 00:39:07.380 --> 00:39:16.870 align:start position:0% comment over to turn over here and we'll make<00:39:08.369> run 00:39:16.870 --> 00:39:16.880 align:start position:0% 00:39:16.880 --> 00:39:19.520 align:start position:0% finding<00:39:17.880> out<00:39:18.000> that<00:39:18.030> that<00:39:18.180> meant<00:39:18.510> starting<00:39:19.200> get 00:39:19.520 --> 00:39:19.530 align:start position:0% finding out that that meant starting get 00:39:19.530 --> 00:39:21.859 align:start position:0% finding out that that meant starting get waiting<00:39:20.250> for<00:39:20.369> it<00:39:20.430> to<00:39:20.460> be<00:39:20.609> around<00:39:20.849> I<00:39:21.270> mean<00:39:21.750> this 00:39:21.859 --> 00:39:21.869 align:start position:0% waiting for it to be around I mean this 00:39:21.869 --> 00:39:30.190 align:start position:0% waiting for it to be around I mean this the<00:39:22.470> texture<00:39:22.800> here 00:39:30.190 --> 00:39:30.200 align:start position:0% 00:39:30.200 --> 00:39:34.210 align:start position:0% that's<00:39:30.800> actually<00:39:31.100> running<00:39:31.310> it 00:39:34.210 --> 00:39:34.220 align:start position:0% 00:39:34.220 --> 00:39:37.750 align:start position:0% really<00:39:34.760> nervous<00:39:34.880> in<00:39:35.090> my<00:39:35.120> life<00:39:35.210> demo<00:39:35.600> now<00:39:36.760> ended 00:39:37.750 --> 00:39:37.760 align:start position:0% really nervous in my life demo now ended 00:39:37.760 --> 00:39:46.110 align:start position:0% really nervous in my life demo now ended and<00:39:37.940> it<00:39:38.030> said<00:39:38.270> apparent<00:39:39.230> up<00:39:39.500> there<00:39:39.740> okay<00:39:44.290> so 00:39:46.110 --> 00:39:46.120 align:start position:0% and it said apparent up there okay so 00:39:46.120 --> 00:39:49.030 align:start position:0% and it said apparent up there okay so what<00:39:47.120> this<00:39:47.270> coach<00:39:47.480> shows<00:39:47.720> us<00:39:47.960> is<00:39:48.410> that<00:39:48.470> we<00:39:48.800> have 00:39:49.030 --> 00:39:49.040 align:start position:0% what this coach shows us is that we have 00:39:49.040 --> 00:39:52.270 align:start position:0% what this coach shows us is that we have 28<00:39:49.550> lines<00:39:49.880> and<00:39:50.330> we're<00:39:51.260> able<00:39:51.380> to<00:39:51.680> take<00:39:51.890> our 00:39:52.270 --> 00:39:52.280 align:start position:0% 28 lines and we're able to take our 00:39:52.280 --> 00:39:55.270 align:start position:0% 28 lines and we're able to take our noticing<00:39:52.910> program<00:39:53.600> that<00:39:53.720> we<00:39:53.780> wrote<00:39:53.930> and<00:39:54.280> write 00:39:55.270 --> 00:39:55.280 align:start position:0% noticing program that we wrote and write 00:39:55.280 --> 00:39:59.560 align:start position:0% noticing program that we wrote and write the<00:39:55.520> rapper<00:39:56.030> front-end<00:39:57.730> so<00:39:58.730> this<00:39:59.000> code<00:39:59.240> is<00:39:59.420> the 00:39:59.560 --> 00:39:59.570 align:start position:0% the rapper front-end so this code is the 00:39:59.570 --> 00:40:02.290 align:start position:0% the rapper front-end so this code is the minimal<00:40:00.290> amount<00:40:00.530> of<00:40:01.070> traveling<00:40:01.490> code<00:40:01.760> that<00:40:02.180> we 00:40:02.290 --> 00:40:02.300 align:start position:0% minimal amount of traveling code that we 00:40:02.300 --> 00:40:03.700 align:start position:0% minimal amount of traveling code that we would<00:40:02.420> need<00:40:02.540> to<00:40:02.600> write<00:40:02.900> have<00:40:03.380> something 00:40:03.700 --> 00:40:03.710 align:start position:0% would need to write have something 00:40:03.710 --> 00:40:06.250 align:start position:0% would need to write have something useful<00:40:03.890> in<00:40:04.850> to<00:40:05.000> take<00:40:05.210> this<00:40:05.510> structure<00:40:06.110> right 00:40:06.250 --> 00:40:06.260 align:start position:0% useful in to take this structure right 00:40:06.260 --> 00:40:06.940 align:start position:0% useful in to take this structure right here 00:40:06.940 --> 00:40:06.950 align:start position:0% here 00:40:06.950 --> 00:40:08.470 align:start position:0% here and<00:40:07.040> you<00:40:07.220> can<00:40:07.340> build<00:40:07.520> your<00:40:07.760> unit<00:40:08.150> testing 00:40:08.470 --> 00:40:08.480 align:start position:0% and you can build your unit testing 00:40:08.480 --> 00:40:12.970 align:start position:0% and you can build your unit testing library<00:40:08.930> for<00:40:09.320> this<00:40:09.500> between<00:40:09.740> there<00:40:10.040> now<00:40:11.980> now 00:40:12.970 --> 00:40:12.980 align:start position:0% library for this between there now now 00:40:12.980 --> 00:40:15.310 align:start position:0% library for this between there now now let<00:40:13.550> me<00:40:13.640> show<00:40:13.760> you<00:40:13.820> one<00:40:14.120> more<00:40:14.150> version<00:40:14.510> that 00:40:15.310 --> 00:40:15.320 align:start position:0% let me show you one more version that 00:40:15.320 --> 00:40:18.510 align:start position:0% let me show you one more version that does<00:40:15.530> a<00:40:15.560> little<00:40:16.040> bit<00:40:16.250> more<00:40:16.520> interesting<00:40:17.030> stuff 00:40:18.510 --> 00:40:18.520 align:start position:0% does a little bit more interesting stuff 00:40:18.520 --> 00:40:24.670 align:start position:0% does a little bit more interesting stuff so<00:40:21.490> what<00:40:22.490> this<00:40:22.550> person<00:40:22.880> is<00:40:22.970> gonna<00:40:23.090> do<00:40:23.300> is<00:40:23.750> it's 00:40:24.670 --> 00:40:24.680 align:start position:0% so what this person is gonna do is it's 00:40:24.680 --> 00:40:27.700 align:start position:0% so what this person is gonna do is it's gonna<00:40:24.860> be<00:40:25.070> 41<00:40:25.460> lines<00:40:25.880> so<00:40:26.720> it's<00:40:26.870> like<00:40:27.080> twice<00:40:27.500> as 00:40:27.700 --> 00:40:27.710 align:start position:0% gonna be 41 lines so it's like twice as 00:40:27.710 --> 00:40:29.650 align:start position:0% gonna be 41 lines so it's like twice as long<00:40:27.860> and<00:40:28.790> we're<00:40:28.940> just<00:40:29.060> going<00:40:29.210> to<00:40:29.240> do<00:40:29.360> is<00:40:29.510> it's 00:40:29.650 --> 00:40:29.660 align:start position:0% long and we're just going to do is it's 00:40:29.660 --> 00:40:31.660 align:start position:0% long and we're just going to do is it's my<00:40:29.780> two<00:40:29.870> messages<00:40:30.860> about<00:40:31.070> what's<00:40:31.280> happening 00:40:31.660 --> 00:40:31.670 align:start position:0% my two messages about what's happening 00:40:31.670 --> 00:40:35.200 align:start position:0% my two messages about what's happening and<00:40:32.950> other<00:40:33.950> that's<00:40:34.160> gonna<00:40:34.310> be<00:40:34.400> different<00:40:34.610> is 00:40:35.200 --> 00:40:35.210 align:start position:0% and other that's gonna be different is 00:40:35.210 --> 00:40:39.640 align:start position:0% and other that's gonna be different is is<00:40:35.510> that<00:40:36.400> the<00:40:37.400> parent<00:40:38.330> is<00:40:38.480> going<00:40:38.630> to<00:40:38.690> say<00:40:38.930> that 00:40:39.640 --> 00:40:39.650 align:start position:0% is that the parent is going to say that 00:40:39.650 --> 00:40:42.430 align:start position:0% is that the parent is going to say that you<00:40:40.100> can<00:40:40.280> have<00:40:40.570> any<00:40:41.570> time<00:40:41.870> you<00:40:41.990> ask<00:40:42.140> for<00:40:42.320> money 00:40:42.430 --> 00:40:42.440 align:start position:0% you can have any time you ask for money 00:40:42.440 --> 00:40:44.110 align:start position:0% you can have any time you ask for money as<00:40:42.860> long<00:40:43.040> as<00:40:43.160> you<00:40:43.220> can<00:40:43.310> ask<00:40:43.460> for<00:40:43.640> less<00:40:43.910> than 00:40:44.110 --> 00:40:44.120 align:start position:0% as long as you can ask for less than 00:40:44.120 --> 00:40:46.170 align:start position:0% as long as you can ask for less than half<00:40:44.330> of<00:40:44.540> what's<00:40:44.720> left<00:40:44.810> will<00:40:45.650> say<00:40:45.800> yes 00:40:46.170 --> 00:40:46.180 align:start position:0% half of what's left will say yes 00:40:46.180 --> 00:40:49.030 align:start position:0% half of what's left will say yes spatulas<00:40:47.180> you<00:40:48.020> can<00:40:48.140> ask<00:40:48.260> without<00:40:48.440> much<00:40:48.740> much 00:40:49.030 --> 00:40:49.040 align:start position:0% spatulas you can ask without much much 00:40:49.040 --> 00:40:51.089 align:start position:0% spatulas you can ask without much much as 00:40:51.089 --> 00:40:51.099 align:start position:0% as 00:40:51.099 --> 00:40:52.739 align:start position:0% as and<00:40:51.609> though<00:40:51.759> the<00:40:51.849> child<00:40:51.880> is<00:40:52.269> going<00:40:52.420> to<00:40:52.479> do<00:40:52.599> it 00:40:52.739 --> 00:40:52.749 align:start position:0% and though the child is going to do it 00:40:52.749 --> 00:40:57.839 align:start position:0% and though the child is going to do it as<00:40:53.199> a<00:40:53.410> child<00:40:53.559> is<00:40:53.799> going<00:40:53.859> to<00:40:53.949> ask<00:40:54.130> for<00:40:54.519> a<00:40:56.849> random 00:40:57.839 --> 00:40:57.849 align:start position:0% as a child is going to ask for a random 00:40:57.849 --> 00:41:01.680 align:start position:0% as a child is going to ask for a random amount<00:40:57.969> of<00:40:58.299> money<00:40:58.509> that<00:40:58.749> is<00:41:00.209> divisible<00:41:01.209> by<00:41:01.420> 8 00:41:01.680 --> 00:41:01.690 align:start position:0% amount of money that is divisible by 8 00:41:01.690 --> 00:41:02.699 align:start position:0% amount of money that is divisible by 8 dollars<00:41:02.199> life 00:41:02.699 --> 00:41:02.709 align:start position:0% dollars life 00:41:02.709 --> 00:41:04.949 align:start position:0% dollars life it's<00:41:03.160> a<00:41:03.219> liar<00:41:03.400> why<00:41:03.640> am<00:41:03.759> I<00:41:03.849> doing<00:41:03.940> this<00:41:04.180> just<00:41:04.779> let 00:41:04.949 --> 00:41:04.959 align:start position:0% it's a liar why am I doing this just let 00:41:04.959 --> 00:41:06.900 align:start position:0% it's a liar why am I doing this just let it<00:41:04.989> over<00:41:05.199> to<00:41:05.410> love<00:41:05.559> life<00:41:05.799> the<00:41:06.670> child 00:41:06.900 --> 00:41:06.910 align:start position:0% it over to love life the child 00:41:06.910 --> 00:41:08.430 align:start position:0% it over to love life the child particularly<00:41:07.509> asked<00:41:07.749> for<00:41:07.930> random<00:41:08.199> lots<00:41:08.349> of 00:41:08.430 --> 00:41:08.440 align:start position:0% particularly asked for random lots of 00:41:08.440 --> 00:41:10.620 align:start position:0% particularly asked for random lots of money<00:41:08.650> and<00:41:08.859> needs<00:41:09.099> until<00:41:09.789> eventually<00:41:09.999> it<00:41:10.299> gets 00:41:10.620 --> 00:41:10.630 align:start position:0% money and needs until eventually it gets 00:41:10.630 --> 00:41:12.839 align:start position:0% money and needs until eventually it gets down<00:41:10.779> to<00:41:10.809> the<00:41:10.959> point<00:41:11.049> where<00:41:11.469> there's<00:41:12.099> only<00:41:12.339> I 00:41:12.839 --> 00:41:12.849 align:start position:0% down to the point where there's only I 00:41:12.849 --> 00:41:14.430 align:start position:0% down to the point where there's only I think<00:41:13.239> one<00:41:13.479> eater<00:41:13.809> left<00:41:13.989> and<00:41:14.170> then<00:41:14.259> it<00:41:14.349> will 00:41:14.430 --> 00:41:14.440 align:start position:0% think one eater left and then it will 00:41:14.440 --> 00:41:17.130 align:start position:0% think one eater left and then it will end<00:41:14.559> so<00:41:15.489> this<00:41:15.940> new<00:41:16.239> version<00:41:16.479> of<00:41:16.630> the<00:41:16.749> permit<00:41:17.049> is 00:41:17.130 --> 00:41:17.140 align:start position:0% end so this new version of the permit is 00:41:17.140 --> 00:41:19.279 align:start position:0% end so this new version of the permit is going<00:41:17.289> to<00:41:17.349> be<00:41:17.440> more<00:41:17.589> like<00:41:17.859> exciting<00:41:18.430> to<00:41:18.549> watch 00:41:19.279 --> 00:41:19.289 align:start position:0% going to be more like exciting to watch 00:41:19.289 --> 00:41:21.599 align:start position:0% going to be more like exciting to watch we're<00:41:20.289> gonna<00:41:20.380> mean<00:41:20.559> but<00:41:20.979> really<00:41:21.249> all<00:41:21.430> they're 00:41:21.599 --> 00:41:21.609 align:start position:0% we're gonna mean but really all they're 00:41:21.609 --> 00:41:24.509 align:start position:0% we're gonna mean but really all they're showing<00:41:21.940> you<00:41:22.059> is<00:41:22.539> that<00:41:22.650> I'm<00:41:23.650> not<00:41:23.920> developing 00:41:24.509 --> 00:41:24.519 align:start position:0% showing you is that I'm not developing 00:41:24.519 --> 00:41:26.370 align:start position:0% showing you is that I'm not developing that<00:41:24.729> happening<00:41:25.089> work<00:41:25.239> I'm<00:41:25.749> making<00:41:26.079> a<00:41:26.199> user 00:41:26.370 --> 00:41:26.380 align:start position:0% that happening work I'm making a user 00:41:26.380 --> 00:41:28.709 align:start position:0% that happening work I'm making a user interface<00:41:26.619> I<00:41:26.979> mean<00:41:27.369> the<00:41:27.549> policy<00:41:27.789> for<00:41:28.390> what<00:41:28.569> the 00:41:28.709 --> 00:41:28.719 align:start position:0% interface I mean the policy for what the 00:41:28.719 --> 00:41:30.180 align:start position:0% interface I mean the policy for what the parent<00:41:29.019> doesn't<00:41:29.319> mean<00:41:29.410> you<00:41:29.469> can<00:41:29.619> policy<00:41:30.039> or 00:41:30.180 --> 00:41:30.190 align:start position:0% parent doesn't mean you can policy or 00:41:30.190 --> 00:41:32.400 align:start position:0% parent doesn't mean you can policy or what<00:41:30.279> the<00:41:30.369> child<00:41:30.609> does<00:41:30.849> be<00:41:31.690> here<00:41:32.109> is<00:41:32.289> an 00:41:32.400 --> 00:41:32.410 align:start position:0% what the child does be here is an 00:41:32.410 --> 00:41:34.349 align:start position:0% what the child does be here is an automated<00:41:32.829> policy<00:41:33.309> but<00:41:33.759> you<00:41:33.819> could<00:41:34.089> have<00:41:34.239> it 00:41:34.349 --> 00:41:34.359 align:start position:0% automated policy but you could have it 00:41:34.359 --> 00:41:36.599 align:start position:0% automated policy but you could have it be<00:41:34.479> instead<00:41:34.869> not<00:41:35.170> automated<00:41:35.769> one<00:41:35.979> the<00:41:36.400> one 00:41:36.599 --> 00:41:36.609 align:start position:0% be instead not automated one the one 00:41:36.609 --> 00:41:45.989 align:start position:0% be instead not automated one the one that's<00:41:36.759> right<00:41:37.420> by<00:41:41.369> and<00:41:42.369> we'll<00:41:43.059> build<00:41:43.719> in<00:41:43.869> -<00:41:44.999> and 00:41:45.989 --> 00:41:45.999 align:start position:0% that's right by and we'll build in - and 00:41:45.999 --> 00:41:52.210 align:start position:0% that's right by and we'll build in - and I<00:41:46.979> love 00:41:52.210 --> 00:41:52.220 align:start position:0% 00:41:52.220 --> 00:41:55.630 align:start position:0% and<00:41:52.940> make<00:41:53.060> the<00:41:53.180> text<00:41:53.420> a<00:41:53.450> little<00:41:53.510> bigger<00:41:54.610> so<00:41:55.610> you 00:41:55.630 --> 00:41:55.640 align:start position:0% and make the text a little bigger so you 00:41:55.640 --> 00:41:58.570 align:start position:0% and make the text a little bigger so you can<00:41:55.910> really<00:41:56.120> experience<00:41:57.190> okay<00:41:58.190> so<00:41:58.460> they 00:41:58.570 --> 00:41:58.580 align:start position:0% can really experience okay so they 00:41:58.580 --> 00:42:02.380 align:start position:0% can really experience okay so they deploy<00:41:58.880> the<00:41:59.030> contract<00:42:00.550> okay<00:42:01.550> that's<00:42:01.820> great 00:42:02.380 --> 00:42:02.390 align:start position:0% deploy the contract okay that's great 00:42:02.390 --> 00:42:04.180 align:start position:0% deploy the contract okay that's great put<00:42:02.600> in<00:42:02.690> 50<00:42:03.020> ask<00:42:03.170> your<00:42:03.410> not<00:42:03.530> okay<00:42:03.860> but<00:42:04.010> one<00:42:04.160> of 00:42:04.180 --> 00:42:04.190 align:start position:0% put in 50 ask your not okay but one of 00:42:04.190 --> 00:42:05.710 align:start position:0% put in 50 ask your not okay but one of this<00:42:04.340> come<00:42:04.700> in<00:42:04.820> look<00:42:05.150> at<00:42:05.240> all<00:42:05.300> this<00:42:05.390> money<00:42:05.570> this 00:42:05.710 --> 00:42:05.720 align:start position:0% this come in look at all this money this 00:42:05.720 --> 00:42:07.150 align:start position:0% this come in look at all this money this right<00:42:05.960> now<00:42:06.110> it's<00:42:06.410> like<00:42:06.560> there's<00:42:06.860> lots<00:42:07.040> of 00:42:07.150 --> 00:42:07.160 align:start position:0% right now it's like there's lots of 00:42:07.160 --> 00:42:09.370 align:start position:0% right now it's like there's lots of times<00:42:07.400> actually<00:42:07.700> have<00:42:07.910> paper<00:42:08.120> and<00:42:08.510> then<00:42:09.200> it's 00:42:09.370 --> 00:42:09.380 align:start position:0% times actually have paper and then it's 00:42:09.380 --> 00:42:11.590 align:start position:0% times actually have paper and then it's ready<00:42:09.560> for<00:42:09.650> a<00:42:09.830> while<00:42:10.010> this<00:42:10.760> is<00:42:10.820> gonna<00:42:11.180> get<00:42:11.420> down 00:42:11.590 --> 00:42:11.600 align:start position:0% ready for a while this is gonna get down 00:42:11.600 --> 00:42:13.360 align:start position:0% ready for a while this is gonna get down to<00:42:11.810> the<00:42:11.960> point<00:42:12.080> where<00:42:12.200> there's<00:42:12.440> only<00:42:12.500> one<00:42:12.620> left 00:42:13.360 --> 00:42:13.370 align:start position:0% to the point where there's only one left 00:42:13.370 --> 00:42:15.310 align:start position:0% to the point where there's only one left it's<00:42:13.580> gonna<00:42:13.730> take<00:42:13.910> a<00:42:13.970> while<00:42:14.120> we<00:42:15.080> get<00:42:15.200> positive 00:42:15.310 --> 00:42:15.320 align:start position:0% it's gonna take a while we get positive 00:42:15.320 --> 00:42:22.900 align:start position:0% it's gonna take a while we get positive payments<00:42:15.970> awesome<00:42:16.970> plus<00:42:20.740> the<00:42:21.740> parent<00:42:22.130> said 00:42:22.900 --> 00:42:22.910 align:start position:0% payments awesome plus the parent said 00:42:22.910 --> 00:42:27.480 align:start position:0% payments awesome plus the parent said yes<00:42:23.210> 13<00:42:23.660> times<00:42:23.930> and<00:42:24.290> no<00:42:24.590> 13<00:42:25.040> times<00:42:25.310> the<00:42:25.670> child 00:42:27.480 --> 00:42:27.490 align:start position:0% yes 13 times and no 13 times the child 00:42:27.490 --> 00:42:32.770 align:start position:0% yes 13 times and no 13 times the child so<00:42:28.490> what<00:42:28.670> we<00:42:28.790> did<00:42:29.030> today<00:42:29.390> is<00:42:29.830> we<00:42:31.060> wrote<00:42:32.060> an 00:42:32.770 --> 00:42:32.780 align:start position:0% so what we did today is we wrote an 00:42:32.780 --> 00:42:39.280 align:start position:0% so what we did today is we wrote an entire<00:42:33.070> down<00:42:35.200> from<00:42:36.200> start<00:42:36.860> to<00:42:36.980> finish<00:42:37.010> in<00:42:38.290> 30 00:42:39.280 --> 00:42:39.290 align:start position:0% entire down from start to finish in 30 00:42:39.290 --> 00:42:41.160 align:start position:0% entire down from start to finish in 30 minutes 00:42:41.160 --> 00:42:41.170 align:start position:0% minutes 00:42:41.170 --> 00:42:52.680 align:start position:0% minutes now<00:42:41.680> I<00:42:51.480> program 00:42:52.680 --> 00:42:52.690 align:start position:0% now I program 00:42:52.690 --> 00:42:55.200 align:start position:0% now I program there's<00:42:52.930> no<00:42:53.170> point<00:42:53.529> at<00:42:53.799> which<00:42:53.920> I<00:42:54.069> said<00:42:54.339> here's 00:42:55.200 --> 00:42:55.210 align:start position:0% there's no point at which I said here's 00:42:55.210 --> 00:42:57.210 align:start position:0% there's no point at which I said here's this<00:42:55.420> complicated<00:42:56.019> solidity<00:42:56.470> idea<00:42:56.829> to<00:42:57.190> a 00:42:57.210 --> 00:42:57.220 align:start position:0% this complicated solidity idea to a 00:42:57.220 --> 00:43:00.329 align:start position:0% this complicated solidity idea to a Titan<00:42:57.700> call<00:42:58.029> or<00:42:58.510> is<00:42:58.690> it<00:42:58.839> transfer<00:42:59.500> it<00:43:00.160> is 00:43:00.329 --> 00:43:00.339 align:start position:0% Titan call or is it transfer it is 00:43:00.339 --> 00:43:02.910 align:start position:0% Titan call or is it transfer it is supposed<00:43:00.549> to<00:43:00.609> be<00:43:00.730> send<00:43:01.470> let<00:43:02.470> me<00:43:02.529> go<00:43:02.619> looking<00:43:02.859> at 00:43:02.910 --> 00:43:02.920 align:start position:0% supposed to be send let me go looking at 00:43:02.920 --> 00:43:04.799 align:start position:0% supposed to be send let me go looking at Stack<00:43:03.130> Overflow<00:43:03.250> question<00:43:03.819> again<00:43:04.029> these<00:43:04.660> are 00:43:04.799 --> 00:43:04.809 align:start position:0% Stack Overflow question again these are 00:43:04.809 --> 00:43:06.990 align:start position:0% Stack Overflow question again these are the<00:43:04.869> kinds<00:43:05.079> of<00:43:05.260> things<00:43:05.500> that<00:43:05.619> are<00:43:05.920> done<00:43:06.130> that 00:43:06.990 --> 00:43:07.000 align:start position:0% the kinds of things that are done that 00:43:07.000 --> 00:43:09.120 align:start position:0% the kinds of things that are done that are<00:43:07.119> decided<00:43:07.569> before<00:43:08.230> you<00:43:08.380> correctly<00:43:08.859> buy 00:43:09.120 --> 00:43:09.130 align:start position:0% are decided before you correctly buy 00:43:09.130 --> 00:43:11.339 align:start position:0% are decided before you correctly buy them<00:43:09.309> from<00:43:09.460> Heather<00:43:09.670> one<00:43:09.910> point<00:43:10.119> the<00:43:11.079> next 00:43:11.339 --> 00:43:11.349 align:start position:0% them from Heather one point the next 00:43:11.349 --> 00:43:13.529 align:start position:0% them from Heather one point the next thing<00:43:11.529> is<00:43:11.890> that<00:43:12.279> we<00:43:12.430> verify<00:43:12.910> that<00:43:13.119> the<00:43:13.210> data<00:43:13.240> is 00:43:13.529 --> 00:43:13.539 align:start position:0% thing is that we verify that the data is 00:43:13.539 --> 00:43:15.359 align:start position:0% thing is that we verify that the data is trustworthy<00:43:13.869> or<00:43:14.559> at<00:43:14.619> least<00:43:14.740> we<00:43:14.890> would<00:43:15.069> have<00:43:15.160> my 00:43:15.359 --> 00:43:15.369 align:start position:0% trustworthy or at least we would have my 00:43:15.369 --> 00:43:16.829 align:start position:0% trustworthy or at least we would have my doctor<00:43:15.789> configuration<00:43:16.359> was<00:43:16.450> writing<00:43:16.720> copy 00:43:16.829 --> 00:43:16.839 align:start position:0% doctor configuration was writing copy 00:43:16.839 --> 00:43:19.319 align:start position:0% doctor configuration was writing copy the<00:43:17.049> files<00:43:17.230> correctly<00:43:17.500> so<00:43:18.190> you<00:43:18.670> want<00:43:18.849> out<00:43:18.970> send 00:43:19.319 --> 00:43:19.329 align:start position:0% the files correctly so you want out send 00:43:19.329 --> 00:43:21.779 align:start position:0% the files correctly so you want out send you<00:43:19.450> well<00:43:19.960> then<00:43:20.349> we'll<00:43:20.529> post<00:43:20.740> a<00:43:20.859> link<00:43:20.890> to<00:43:21.160> a 00:43:21.779 --> 00:43:21.789 align:start position:0% you well then we'll post a link to a 00:43:21.789 --> 00:43:25.289 align:start position:0% you well then we'll post a link to a version<00:43:22.630> of<00:43:22.869> this<00:43:23.369> this<00:43:24.369> walkthrough<00:43:24.609> where 00:43:25.289 --> 00:43:25.299 align:start position:0% version of this this walkthrough where 00:43:25.299 --> 00:43:27.809 align:start position:0% version of this this walkthrough where we<00:43:25.450> show<00:43:25.829> the<00:43:26.829> verification<00:43:27.339> condition<00:43:27.700> was 00:43:27.809 --> 00:43:27.819 align:start position:0% we show the verification condition was 00:43:27.819 --> 00:43:33.029 align:start position:0% we show the verification condition was failing<00:43:28.029> and<00:43:28.809> then<00:43:31.230> and<00:43:32.230> it<00:43:32.410> ensures<00:43:32.559> that<00:43:32.769> the 00:43:33.029 --> 00:43:33.039 align:start position:0% failing and then and it ensures that the 00:43:33.039 --> 00:43:34.829 align:start position:0% failing and then and it ensures that the clients<00:43:33.490> and<00:43:33.579> the<00:43:33.670> contracts<00:43:34.180> rating<00:43:34.480> system 00:43:34.829 --> 00:43:34.839 align:start position:0% clients and the contracts rating system 00:43:34.839 --> 00:43:38.640 align:start position:0% clients and the contracts rating system art<00:43:35.410> for<00:43:36.339> T<00:43:36.430> lying<00:43:36.640> reach<00:43:37.420> program<00:43:37.869> produced 00:43:38.640 --> 00:43:38.650 align:start position:0% art for T lying reach program produced 00:43:38.650 --> 00:43:43.259 align:start position:0% art for T lying reach program produced 300<00:43:39.250> lines<00:43:39.640> of<00:43:40.680> front-end<00:43:41.680> Java<00:43:41.950> code<00:43:42.309> and<00:43:42.730> so 00:43:43.259 --> 00:43:43.269 align:start position:0% 300 lines of front-end Java code and so 00:43:43.269 --> 00:43:44.880 align:start position:0% 300 lines of front-end Java code and so the<00:43:43.390> code<00:43:43.660> and<00:43:43.839> the<00:43:43.990> details<00:43:44.440> of<00:43:44.619> those<00:43:44.740> two 00:43:44.880 --> 00:43:44.890 align:start position:0% the code and the details of those two 00:43:44.890 --> 00:43:46.680 align:start position:0% the code and the details of those two programs<00:43:45.130> have<00:43:45.460> to<00:43:45.640> mean<00:43:45.789> the<00:43:45.910> mentalist<00:43:46.539> be 00:43:46.680 --> 00:43:46.690 align:start position:0% programs have to mean the mentalist be 00:43:46.690 --> 00:43:48.509 align:start position:0% programs have to mean the mentalist be connected<00:43:47.170> with<00:43:47.200> one<00:43:47.349> another<00:43:47.500> to<00:43:48.190> make<00:43:48.220> sure 00:43:48.509 --> 00:43:48.519 align:start position:0% connected with one another to make sure 00:43:48.519 --> 00:43:50.569 align:start position:0% connected with one another to make sure that<00:43:48.670> it<00:43:48.789> executes<00:43:49.029> correctly<00:43:49.660> now<00:43:50.200> obviously 00:43:50.569 --> 00:43:50.579 align:start position:0% that it executes correctly now obviously 00:43:50.579 --> 00:43:53.549 align:start position:0% that it executes correctly now obviously you<00:43:51.579> like<00:43:51.730> everything<00:43:52.150> pretty<00:43:52.869> simple<00:43:53.170> 300 00:43:53.549 --> 00:43:53.559 align:start position:0% you like everything pretty simple 300 00:43:53.559 --> 00:43:55.620 align:start position:0% you like everything pretty simple 300 lines<00:43:53.740> that<00:43:54.220> has<00:43:54.309> to<00:43:54.400> be<00:43:54.460> right<00:43:54.640> if<00:43:55.269> you<00:43:55.420> broke 00:43:55.620 --> 00:43:55.630 align:start position:0% lines that has to be right if you broke 00:43:55.630 --> 00:43:57.749 align:start position:0% lines that has to be right if you broke a<00:43:55.660> real<00:43:55.960> program<00:43:56.380> not<00:43:57.099> this<00:43:57.339> little<00:43:57.609> model 00:43:57.749 --> 00:43:57.759 align:start position:0% a real program not this little model 00:43:57.759 --> 00:44:00.620 align:start position:0% a real program not this little model there<00:43:58.599> is 00:44:00.620 --> 00:44:00.630 align:start position:0% there is 00:44:00.630 --> 00:44:05.520 align:start position:0% there is help<00:44:02.670> right<00:44:03.670> now<00:44:03.700> we<00:44:04.390> have<00:44:04.600> our<00:44:04.900> data<00:44:05.080> that<00:44:05.350> has 00:44:05.520 --> 00:44:05.530 align:start position:0% help right now we have our data that has 00:44:05.530 --> 00:44:10.440 align:start position:0% help right now we have our data that has many<00:44:06.310> different<00:44:06.720> many<00:44:07.720> constraints<00:44:09.360> later 00:44:10.440 --> 00:44:10.450 align:start position:0% many different many constraints later 00:44:10.450 --> 00:44:12.690 align:start position:0% many different many constraints later but<00:44:10.720> and<00:44:11.050> we<00:44:11.080> have<00:44:11.320> a<00:44:11.470> release<00:44:11.770> plan<00:44:12.010> for<00:44:12.490> over 00:44:12.690 --> 00:44:12.700 align:start position:0% but and we have a release plan for over 00:44:12.700 --> 00:44:15.660 align:start position:0% but and we have a release plan for over the<00:44:12.790> next<00:44:12.970> year<00:44:13.840> to<00:44:14.470> expand<00:44:14.860> the<00:44:15.010> 72<00:44:15.550> though 00:44:15.660 --> 00:44:15.670 align:start position:0% the next year to expand the 72 though 00:44:15.670 --> 00:44:18.810 align:start position:0% the next year to expand the 72 though I'm<00:44:16.660> very<00:44:16.750> grateful<00:44:17.410> for<00:44:17.830> you<00:44:18.190> to<00:44:18.340> come<00:44:18.640> here 00:44:18.810 --> 00:44:18.820 align:start position:0% I'm very grateful for you to come here 00:44:18.820 --> 00:44:21.420 align:start position:0% I'm very grateful for you to come here please<00:44:19.420> check<00:44:19.660> out<00:44:19.780> our<00:44:19.900> website<00:44:20.430> realization 00:44:21.420 --> 00:44:21.430 align:start position:0% please check out our website realization 00:44:21.430 --> 00:44:24.900 align:start position:0% please check out our website realization is<00:44:22.030> look<00:44:22.270> it<00:44:22.390> up<00:44:22.450> on<00:44:22.750> Twitter<00:44:23.260> and<00:44:24.010> all<00:44:24.640> the 00:44:24.900 --> 00:44:24.910 align:start position:0% is look it up on Twitter and all the 00:44:24.910 --> 00:44:27.030 align:start position:0% is look it up on Twitter and all the social<00:44:25.360> platforms<00:44:26.260> you<00:44:26.530> should<00:44:26.680> really<00:44:26.830> check 00:44:27.030 --> 00:44:27.040 align:start position:0% social platforms you should really check 00:44:27.040 --> 00:44:28.740 align:start position:0% social platforms you should really check out<00:44:27.190> an<00:44:27.280> Instagram<00:44:27.760> account<00:44:27.790> I've<00:44:28.510> got<00:44:28.720> a 00:44:28.740 --> 00:44:28.750 align:start position:0% out an Instagram account I've got a 00:44:28.750 --> 00:44:33.240 align:start position:0% out an Instagram account I've got a really<00:44:28.930> cute<00:44:29.170> cat<00:44:30.690> and<00:44:31.830> finally<00:44:32.830> I<00:44:32.860> just<00:44:32.950> want 00:44:33.240 --> 00:44:33.250 align:start position:0% really cute cat and finally I just want 00:44:33.250 --> 00:44:36.900 align:start position:0% really cute cat and finally I just want to<00:44:33.340> see<00:44:33.490> exercise<00:44:33.760> and<00:44:34.680> reach<00:44:35.680> was<00:44:36.220> only<00:44:36.880> a 00:44:36.900 --> 00:44:36.910 align:start position:0% to see exercise and reach was only a 00:44:36.910 --> 00:44:42.450 align:start position:0% to see exercise and reach was only a project<00:44:37.840> that<00:44:37.960> I<00:44:37.990> worked<00:44:38.230> on<00:44:40.950> that's<00:44:41.950> based<00:44:42.310> on 00:44:42.450 --> 00:44:42.460 align:start position:0% project that I worked on that's based on 00:44:42.460 --> 00:44:46.140 align:start position:0% project that I worked on that's based on the<00:44:42.580> same<00:44:42.790> principles<00:44:43.300> and<00:44:44.790> so<00:44:45.790> thank<00:44:46.000> you<00:44:46.060> so 00:44:46.140 --> 00:44:46.150 align:start position:0% the same principles and so thank you so 00:44:46.150 --> 00:44:51.460 align:start position:0% the same principles and so thank you so much<00:44:46.300> for<00:44:46.390> your<00:44:46.510> time 00:44:51.460 --> 00:44:51.470 align:start position:0% 00:44:51.470 --> 00:44:57.880 align:start position:0% [Applause]