WEBVTT Kind: captions Language: en 00:00:13.179 --> 00:00:16.750 align:start position:0% program<00:00:14.179> many<00:00:14.869> things<00:00:15.259> can<00:00:15.619> usually<00:00:16.340> still<00:00:16.610> go 00:00:16.750 --> 00:00:16.760 align:start position:0% program many things can usually still go 00:00:16.760 --> 00:00:21.010 align:start position:0% program many things can usually still go wrong<00:00:17.020> like<00:00:18.040> we<00:00:19.040> say<00:00:19.280> a<00:00:19.310> cosmic<00:00:19.880> ray<00:00:20.090> can<00:00:20.540> hit 00:00:21.010 --> 00:00:21.020 align:start position:0% wrong like we say a cosmic ray can hit 00:00:21.020 --> 00:00:23.980 align:start position:0% wrong like we say a cosmic ray can hit your<00:00:21.560> memory<00:00:21.920> and<00:00:22.220> a<00:00:22.520> bit<00:00:22.700> flips<00:00:23.030> that<00:00:23.750> can 00:00:23.980 --> 00:00:23.990 align:start position:0% your memory and a bit flips that can 00:00:23.990 --> 00:00:27.730 align:start position:0% your memory and a bit flips that can happen<00:00:25.030> well<00:00:26.030> maybe<00:00:26.570> you<00:00:26.780> can<00:00:27.020> use<00:00:27.050> some 00:00:27.730 --> 00:00:27.740 align:start position:0% happen well maybe you can use some 00:00:27.740 --> 00:00:31.150 align:start position:0% happen well maybe you can use some service<00:00:28.370> or<00:00:28.610> crowd<00:00:29.150> and<00:00:29.720> so<00:00:29.990> on<00:00:30.200> and<00:00:30.500> then<00:00:30.740> when 00:00:31.150 --> 00:00:31.160 align:start position:0% service or crowd and so on and then when 00:00:31.160 --> 00:00:33.630 align:start position:0% service or crowd and so on and then when you<00:00:31.310> use<00:00:31.340> remote<00:00:32.180> machines<00:00:32.689> there<00:00:33.050> are 00:00:33.630 --> 00:00:33.640 align:start position:0% you use remote machines there are 00:00:33.640 --> 00:00:36.190 align:start position:0% you use remote machines there are administrators<00:00:34.640> with<00:00:35.060> physical<00:00:35.540> access<00:00:35.960> so 00:00:36.190 --> 00:00:36.200 align:start position:0% administrators with physical access so 00:00:36.200 --> 00:00:39.340 align:start position:0% administrators with physical access so they<00:00:36.380> can<00:00:36.410> do<00:00:36.680> bad<00:00:36.860> stuff<00:00:36.890> and<00:00:38.110> what<00:00:39.110> a<00:00:39.140> machine 00:00:39.340 --> 00:00:39.350 align:start position:0% they can do bad stuff and what a machine 00:00:39.350 --> 00:00:42.160 align:start position:0% they can do bad stuff and what a machine itself<00:00:39.860> might<00:00:40.160> have<00:00:40.190> bugs<00:00:40.670> and<00:00:41.000> a<00:00:41.300> cat<00:00:41.600> might 00:00:42.160 --> 00:00:42.170 align:start position:0% itself might have bugs and a cat might 00:00:42.170 --> 00:00:45.700 align:start position:0% itself might have bugs and a cat might break<00:00:43.130> a<00:00:43.370> cable<00:00:43.730> router<00:00:44.270> cables<00:00:44.960> stuff<00:00:45.530> like 00:00:45.700 --> 00:00:45.710 align:start position:0% break a cable router cables stuff like 00:00:45.710 --> 00:00:48.540 align:start position:0% break a cable router cables stuff like that<00:00:45.920> so<00:00:46.220> there<00:00:46.460> are<00:00:46.610> many<00:00:46.790> many<00:00:47.000> RC 00:00:48.540 --> 00:00:48.550 align:start position:0% that so there are many many RC 00:00:48.550 --> 00:00:53.639 align:start position:0% that so there are many many RC uninteresting<00:00:49.550> reasons<00:00:50.530> for<00:00:51.530> program<00:00:52.280> errors 00:00:53.639 --> 00:00:53.649 align:start position:0% uninteresting reasons for program errors 00:00:53.649 --> 00:00:58.299 align:start position:0% uninteresting reasons for program errors but<00:00:55.000> a<00:00:56.000> single<00:00:56.960> cosmic<00:00:57.470> ray<00:00:57.680> particle 00:00:58.299 --> 00:00:58.309 align:start position:0% but a single cosmic ray particle 00:00:58.309 --> 00:01:01.600 align:start position:0% but a single cosmic ray particle whatever<00:00:58.730> cannot<00:00:59.590> probably<00:01:00.590> break<00:01:01.130> the 00:01:01.600 --> 00:01:01.610 align:start position:0% whatever cannot probably break the 00:01:01.610 --> 00:01:03.459 align:start position:0% whatever cannot probably break the atrium<00:01:01.910> network<00:01:02.270> because<00:01:02.630> that<00:01:02.899> can<00:01:03.140> only 00:01:03.459 --> 00:01:03.469 align:start position:0% atrium network because that can only 00:01:03.469 --> 00:01:08.530 align:start position:0% atrium network because that can only affect<00:01:03.829> one<00:01:04.070> node<00:01:04.280> and<00:01:04.729> if<00:01:05.720> that<00:01:06.020> I<00:01:06.320> mean<00:01:07.540> for 00:01:08.530 --> 00:01:08.540 align:start position:0% affect one node and if that I mean for 00:01:08.540 --> 00:01:10.920 align:start position:0% affect one node and if that I mean for cosmic<00:01:08.870> rays<00:01:09.110> to<00:01:09.350> cause<00:01:09.620> a<00:01:09.650> serious<00:01:10.130> trouble 00:01:10.920 --> 00:01:10.930 align:start position:0% cosmic rays to cause a serious trouble 00:01:10.930 --> 00:01:14.170 align:start position:0% cosmic rays to cause a serious trouble where<00:01:11.930> thousands<00:01:12.470> of<00:01:12.680> particles<00:01:13.280> must<00:01:13.880> arrive 00:01:14.170 --> 00:01:14.180 align:start position:0% where thousands of particles must arrive 00:01:14.180 --> 00:01:17.350 align:start position:0% where thousands of particles must arrive at<00:01:14.210> yes<00:01:14.690> and<00:01:15.560> they<00:01:15.979> needed<00:01:16.970> to<00:01:17.090> hit 00:01:17.350 --> 00:01:17.360 align:start position:0% at yes and they needed to hit 00:01:17.360 --> 00:01:21.550 align:start position:0% at yes and they needed to hit simultaneously<00:01:19.240> the<00:01:20.240> same<00:01:20.659> a<00:01:20.690> memory<00:01:20.990> cell<00:01:21.260> in 00:01:21.550 --> 00:01:21.560 align:start position:0% simultaneously the same a memory cell in 00:01:21.560 --> 00:01:23.590 align:start position:0% simultaneously the same a memory cell in many<00:01:22.280> many<00:01:22.460> different<00:01:22.580> machines<00:01:23.240> and<00:01:23.390> so<00:01:23.570> on 00:01:23.590 --> 00:01:23.600 align:start position:0% many many different machines and so on 00:01:23.600 --> 00:01:28.180 align:start position:0% many many different machines and so on so<00:01:23.840> it's<00:01:24.470> name<00:01:24.650> is<00:01:24.770> kind<00:01:25.130> of<00:01:26.979> resistant<00:01:27.979> to 00:01:28.180 --> 00:01:28.190 align:start position:0% so it's name is kind of resistant to 00:01:28.190 --> 00:01:31.330 align:start position:0% so it's name is kind of resistant to many<00:01:28.540> uninteresting<00:01:29.540> features<00:01:29.930> so<00:01:30.290> bug<00:01:31.100> free 00:01:31.330 --> 00:01:31.340 align:start position:0% many uninteresting features so bug free 00:01:31.340 --> 00:01:34.539 align:start position:0% many uninteresting features so bug free programming<00:01:31.790> makes<00:01:32.299> sense<00:01:32.659> in<00:01:32.930> this<00:01:33.140> room<00:01:33.549> the 00:01:34.539 --> 00:01:34.549 align:start position:0% programming makes sense in this room the 00:01:34.549 --> 00:01:37.240 align:start position:0% programming makes sense in this room the same<00:01:34.820> there<00:01:35.200> because<00:01:36.200> in<00:01:36.590> other<00:01:36.890> places 00:01:37.240 --> 00:01:37.250 align:start position:0% same there because in other places 00:01:37.250 --> 00:01:40.960 align:start position:0% same there because in other places before<00:01:37.970> you<00:01:38.330> remove<00:01:39.110> all<00:01:39.439> bugs<00:01:40.100> perfectly 00:01:40.960 --> 00:01:40.970 align:start position:0% before you remove all bugs perfectly 00:01:40.970 --> 00:01:43.679 align:start position:0% before you remove all bugs perfectly your<00:01:41.960> weakest<00:01:42.470> link<00:01:42.740> is<00:01:42.890> no<00:01:43.130> longer 00:01:43.679 --> 00:01:43.689 align:start position:0% your weakest link is no longer 00:01:43.689 --> 00:01:46.120 align:start position:0% your weakest link is no longer programming<00:01:44.689> programming<00:01:45.170> errors<00:01:45.530> there<00:01:45.920> are 00:01:46.120 --> 00:01:46.130 align:start position:0% programming programming errors there are 00:01:46.130 --> 00:01:49.210 align:start position:0% programming programming errors there are some<00:01:46.430> other<00:01:46.700> non<00:01:47.659> interesting<00:01:48.200> visions<00:01:48.680> but 00:01:49.210 --> 00:01:49.220 align:start position:0% some other non interesting visions but 00:01:49.220 --> 00:01:52.830 align:start position:0% some other non interesting visions but to<00:01:49.430> worry<00:01:49.640> about<00:01:49.820> what<00:01:50.360> in<00:01:50.600> Israel<00:01:51.020> you<00:01:51.259> can 00:01:52.830 --> 00:01:52.840 align:start position:0% to worry about what in Israel you can 00:01:52.840 --> 00:01:57.070 align:start position:0% to worry about what in Israel you can still<00:01:53.840> well<00:01:54.350> you<00:01:55.390> it's<00:01:56.390> really<00:01:56.630> really 00:01:57.070 --> 00:01:57.080 align:start position:0% still well you it's really really 00:01:57.080 --> 00:02:03.390 align:start position:0% still well you it's really really difficult<00:01:57.259> to<00:01:57.939> get<00:01:59.170> get<00:02:00.170> other<00:02:00.560> weakest<00:02:01.369> links 00:02:03.390 --> 00:02:03.400 align:start position:0% difficult to get get other weakest links 00:02:03.400 --> 00:02:07.149 align:start position:0% difficult to get get other weakest links so<00:02:04.400> here<00:02:05.000> my<00:02:05.180> aim<00:02:05.390> is<00:02:05.630> to<00:02:05.990> match<00:02:06.350> what<00:02:06.680> happens 00:02:07.149 --> 00:02:07.159 align:start position:0% so here my aim is to match what happens 00:02:07.159 --> 00:02:11.830 align:start position:0% so here my aim is to match what happens and<00:02:07.579> how<00:02:07.929> a<00:02:08.929> program<00:02:09.170> looks<00:02:09.590> and<00:02:10.540> yes<00:02:11.540> I<00:02:11.660> want 00:02:11.830 --> 00:02:11.840 align:start position:0% and how a program looks and yes I want 00:02:11.840 --> 00:02:13.870 align:start position:0% and how a program looks and yes I want to<00:02:11.900> talk<00:02:12.200> I<00:02:12.349> have<00:02:12.530> to<00:02:12.680> talk<00:02:12.830> about<00:02:12.980> what 00:02:13.870 --> 00:02:13.880 align:start position:0% to talk I have to talk about what 00:02:13.880 --> 00:02:14.650 align:start position:0% to talk I have to talk about what happens 00:02:14.650 --> 00:02:14.660 align:start position:0% happens 00:02:14.660 --> 00:02:18.790 align:start position:0% happens in<00:02:15.550> contracts<00:02:16.690> this<00:02:17.690> is<00:02:17.810> just<00:02:18.110> one<00:02:18.350> mental 00:02:18.790 --> 00:02:18.800 align:start position:0% in contracts this is just one mental 00:02:18.800 --> 00:02:21.460 align:start position:0% in contracts this is just one mental model<00:02:19.130> it's<00:02:19.910> just<00:02:20.390> one<00:02:20.540> way<00:02:20.720> of<00:02:20.750> thinking 00:02:21.460 --> 00:02:21.470 align:start position:0% model it's just one way of thinking 00:02:21.470 --> 00:02:24.400 align:start position:0% model it's just one way of thinking about<00:02:21.590> it<00:02:21.740> but<00:02:22.130> will<00:02:23.000> some<00:02:23.570> something<00:02:23.750> cause 00:02:24.400 --> 00:02:24.410 align:start position:0% about it but will some something cause 00:02:24.410 --> 00:02:30.760 align:start position:0% about it but will some something cause your<00:02:26.800> contract<00:02:28.000> first<00:02:29.000> with<00:02:29.540> an<00:02:29.690> input<00:02:29.870> on<00:02:30.470> the 00:02:30.760 --> 00:02:30.770 align:start position:0% your contract first with an input on the 00:02:30.770 --> 00:02:34.000 align:start position:0% your contract first with an input on the SEO<00:02:31.160> contract<00:02:31.520> as<00:02:31.700> some<00:02:31.970> states<00:02:32.360> state<00:02:33.260> and 00:02:34.000 --> 00:02:34.010 align:start position:0% SEO contract as some states state and 00:02:34.010 --> 00:02:36.280 align:start position:0% SEO contract as some states state and something<00:02:34.460> happens<00:02:34.910> and<00:02:35.120> an<00:02:35.510> output<00:02:35.930> is 00:02:36.280 --> 00:02:36.290 align:start position:0% something happens and an output is 00:02:36.290 --> 00:02:39.310 align:start position:0% something happens and an output is produced<00:02:37.060> something<00:02:38.060> might<00:02:38.390> contain<00:02:38.840> coding 00:02:39.310 --> 00:02:39.320 align:start position:0% produced something might contain coding 00:02:39.320 --> 00:02:40.750 align:start position:0% produced something might contain coding other<00:02:39.530> contracts<00:02:40.100> or<00:02:40.190> sending<00:02:40.460> in<00:02:40.640> so 00:02:40.750 --> 00:02:40.760 align:start position:0% other contracts or sending in so 00:02:40.760 --> 00:02:43.560 align:start position:0% other contracts or sending in so whatever<00:02:41.300> but<00:02:41.840> an<00:02:42.020> output<00:02:42.410> comes<00:02:42.680> out<00:02:42.920> and 00:02:43.560 --> 00:02:43.570 align:start position:0% whatever but an output comes out and 00:02:43.570 --> 00:02:46.180 align:start position:0% whatever but an output comes out and there<00:02:44.570> will<00:02:44.720> be<00:02:44.750> a<00:02:44.930> contract<00:02:45.410> state<00:02:45.770> after<00:02:46.130> the 00:02:46.180 --> 00:02:46.190 align:start position:0% there will be a contract state after the 00:02:46.190 --> 00:02:49.450 align:start position:0% there will be a contract state after the core<00:02:46.600> is<00:02:47.600> there<00:02:47.930> other<00:02:48.340> hospitals<00:02:49.340> were 00:02:49.450 --> 00:02:49.460 align:start position:0% core is there other hospitals were 00:02:49.460 --> 00:02:52.060 align:start position:0% core is there other hospitals were category<00:02:49.820> theories<00:02:50.090> here<00:02:50.600> Wow<00:02:51.410> cool 00:02:52.060 --> 00:02:52.070 align:start position:0% category theories here Wow cool 00:02:52.070 --> 00:02:56.770 align:start position:0% category theories here Wow cool yes<00:02:52.460> greetings<00:02:52.970> I<00:02:53.420> stole<00:02:53.750> your<00:02:53.930> ideas<00:02:55.780> and 00:02:56.770 --> 00:02:56.780 align:start position:0% yes greetings I stole your ideas and 00:02:56.780 --> 00:03:04.690 align:start position:0% yes greetings I stole your ideas and then<00:02:59.410> so<00:03:00.410> this<00:03:00.770> is<00:03:00.920> my<00:03:01.070> mental<00:03:01.430> picture<00:03:02.470> so<00:03:03.700> and 00:03:04.690 --> 00:03:04.700 align:start position:0% then so this is my mental picture so and 00:03:04.700 --> 00:03:08.170 align:start position:0% then so this is my mental picture so and I<00:03:04.850> translate<00:03:05.300> that<00:03:05.570> literally<00:03:06.530> into<00:03:07.220> program 00:03:08.170 --> 00:03:08.180 align:start position:0% I translate that literally into program 00:03:08.180 --> 00:03:12.700 align:start position:0% I translate that literally into program syntax<00:03:09.140> so<00:03:10.040> on<00:03:10.220> the<00:03:10.370> Left<00:03:10.520> this<00:03:11.360> is<00:03:11.600> what<00:03:12.380> my 00:03:12.700 --> 00:03:12.710 align:start position:0% syntax so on the Left this is what my 00:03:12.710 --> 00:03:14.860 align:start position:0% syntax so on the Left this is what my contract<00:03:13.190> here<00:03:13.310> should<00:03:13.670> do<00:03:13.880> where<00:03:14.360> it<00:03:14.510> starts 00:03:14.860 --> 00:03:14.870 align:start position:0% contract here should do where it starts 00:03:14.870 --> 00:03:18.640 align:start position:0% contract here should do where it starts as<00:03:14.990> a<00:03:15.020> contract<00:03:15.590> a<00:03:15.800> and<00:03:16.190> when<00:03:17.200> somebody<00:03:18.200> calls 00:03:18.640 --> 00:03:18.650 align:start position:0% as a contract a and when somebody calls 00:03:18.650 --> 00:03:20.500 align:start position:0% as a contract a and when somebody calls function<00:03:19.250> if<00:03:19.370> I<00:03:19.520> want<00:03:19.730> to<00:03:19.820> call<00:03:20.000> function<00:03:20.390> if 00:03:20.500 --> 00:03:20.510 align:start position:0% function if I want to call function if 00:03:20.510 --> 00:03:23.110 align:start position:0% function if I want to call function if that's<00:03:20.780> the<00:03:21.080> input<00:03:21.200> when<00:03:21.980> that<00:03:22.520> input<00:03:22.730> comes 00:03:23.110 --> 00:03:23.120 align:start position:0% that's the input when that input comes 00:03:23.120 --> 00:03:25.030 align:start position:0% that's the input when that input comes in<00:03:23.270> zero<00:03:23.540> is<00:03:23.660> returned<00:03:24.080> and<00:03:24.290> it<00:03:24.470> becomes 00:03:25.030 --> 00:03:25.040 align:start position:0% in zero is returned and it becomes 00:03:25.040 --> 00:03:28.300 align:start position:0% in zero is returned and it becomes contract<00:03:25.670> B<00:03:25.910> and<00:03:26.870> when<00:03:27.140> it's<00:03:27.290> caught<00:03:27.470> again<00:03:27.800> it 00:03:28.300 --> 00:03:28.310 align:start position:0% contract B and when it's caught again it 00:03:28.310 --> 00:03:31.270 align:start position:0% contract B and when it's caught again it returns<00:03:28.850> one<00:03:29.570> and<00:03:29.930> it<00:03:30.110> becomes<00:03:30.500> contract<00:03:31.040> see 00:03:31.270 --> 00:03:31.280 align:start position:0% returns one and it becomes contract see 00:03:31.280 --> 00:03:35.380 align:start position:0% returns one and it becomes contract see when<00:03:32.270> contracted<00:03:32.630> C<00:03:33.020> is<00:03:33.080> called<00:03:33.440> it<00:03:34.430> returns<00:03:34.820> 3 00:03:35.380 --> 00:03:35.390 align:start position:0% when contracted C is called it returns 3 00:03:35.390 --> 00:03:38.980 align:start position:0% when contracted C is called it returns 3 becomes<00:03:35.840> contract<00:03:36.320> a<00:03:36.500> and<00:03:36.920> so<00:03:37.160> on<00:03:37.570> and<00:03:38.570> that's 00:03:38.980 --> 00:03:38.990 align:start position:0% becomes contract a and so on and that's 00:03:38.990 --> 00:03:41.710 align:start position:0% becomes contract a and so on and that's kind<00:03:39.680> of<00:03:39.800> literally<00:03:40.370> reproduced<00:03:41.030> here<00:03:41.180> as<00:03:41.660> a 00:03:41.710 --> 00:03:41.720 align:start position:0% kind of literally reproduced here as a 00:03:41.720 --> 00:03:44.500 align:start position:0% kind of literally reproduced here as a text<00:03:42.380> and<00:03:42.530> well<00:03:43.190> when<00:03:43.760> the<00:03:43.850> contract<00:03:44.180> a<00:03:44.300> is 00:03:44.500 --> 00:03:44.510 align:start position:0% text and well when the contract a is 00:03:44.510 --> 00:03:48.670 align:start position:0% text and well when the contract a is called<00:03:44.870> with<00:03:45.860> f<00:03:46.310> as<00:03:46.700> the<00:03:46.760> specifier<00:03:47.450> then<00:03:47.810> it 00:03:48.670 --> 00:03:48.680 align:start position:0% called with f as the specifier then it 00:03:48.680 --> 00:03:52.150 align:start position:0% called with f as the specifier then it returns<00:03:49.040> 0<00:03:49.310> and<00:03:49.489> then<00:03:49.610> become<00:03:49.850> B<00:03:50.030> &<00:03:50.360> B<00:03:51.160> returns 00:03:52.150 --> 00:03:52.160 align:start position:0% returns 0 and then become B & B returns 00:03:52.160 --> 00:03:54.640 align:start position:0% returns 0 and then become B & B returns 1<00:03:52.400> and<00:03:52.640> becomes<00:03:52.910> G<00:03:53.150> and<00:03:53.360> she<00:03:53.630> returns<00:03:54.230> then 00:03:54.640 --> 00:03:54.650 align:start position:0% 1 and becomes G and she returns then 00:03:54.650 --> 00:04:00.030 align:start position:0% 1 and becomes G and she returns then becomes<00:03:55.010> a<00:03:55.840> that's<00:03:56.840> kind<00:03:57.260> of<00:03:57.380> straight<00:03:57.920> word 00:04:00.030 --> 00:04:00.040 align:start position:0% becomes a that's kind of straight word 00:04:00.040 --> 00:04:07.240 align:start position:0% becomes a that's kind of straight word and<00:04:01.040> then<00:04:02.830> well<00:04:03.830> so<00:04:04.820> I<00:04:04.850> did<00:04:05.330> I<00:04:05.750> did<00:04:06.050> it<00:04:06.170> it<00:04:06.380> I<00:04:06.680> did 00:04:07.240 --> 00:04:07.250 align:start position:0% and then well so I did I did it it I did 00:04:07.250 --> 00:04:09.460 align:start position:0% and then well so I did I did it it I did it<00:04:07.370> with<00:04:07.670> three<00:04:07.970> different<00:04:08.180> states<00:04:08.870> but 00:04:09.460 --> 00:04:09.470 align:start position:0% it with three different states but 00:04:09.470 --> 00:04:12.729 align:start position:0% it with three different states but that's<00:04:09.680> very<00:04:10.640> small<00:04:11.090> state<00:04:11.510> space<00:04:11.810> well<00:04:12.470> maybe 00:04:12.729 --> 00:04:12.739 align:start position:0% that's very small state space well maybe 00:04:12.739 --> 00:04:15.910 align:start position:0% that's very small state space well maybe a<00:04:12.830> contract<00:04:13.310> should<00:04:13.610> hold<00:04:14.030> numbers<00:04:14.600> so<00:04:15.290> when 00:04:15.910 --> 00:04:15.920 align:start position:0% a contract should hold numbers so when 00:04:15.920 --> 00:04:18.340 align:start position:0% a contract should hold numbers so when you<00:04:16.160> call<00:04:16.489> it<00:04:16.669> each<00:04:17.209> time<00:04:17.239> you<00:04:17.690> call<00:04:17.870> it<00:04:18.049> the 00:04:18.340 --> 00:04:18.350 align:start position:0% you call it each time you call it the 00:04:18.350 --> 00:04:22.080 align:start position:0% you call it each time you call it the account<00:04:19.299> increments<00:04:20.299> and<00:04:20.510> it<00:04:20.959> returns<00:04:21.410> the 00:04:22.080 --> 00:04:22.090 align:start position:0% account increments and it returns the 00:04:22.090 --> 00:04:25.330 align:start position:0% account increments and it returns the previous<00:04:23.090> counter<00:04:23.600> number<00:04:23.919> that's<00:04:24.919> kind<00:04:25.250> of 00:04:25.330 --> 00:04:25.340 align:start position:0% previous counter number that's kind of 00:04:25.340 --> 00:04:27.460 align:start position:0% previous counter number that's kind of implementable<00:04:25.940> so<00:04:26.210> instead<00:04:26.900> of<00:04:27.110> having<00:04:27.350> just 00:04:27.460 --> 00:04:27.470 align:start position:0% implementable so instead of having just 00:04:27.470 --> 00:04:28.300 align:start position:0% implementable so instead of having just one<00:04:27.710> alphabet 00:04:28.300 --> 00:04:28.310 align:start position:0% one alphabet 00:04:28.310 --> 00:05:40.930 align:start position:0% one alphabet I<00:04:39.580> say<00:04:46.720> it<00:04:48.880> again<00:05:09.190> so<00:05:37.120> many<00:05:38.500> contracts<00:05:39.940> define 00:05:40.930 --> 00:05:40.940 align:start position:0% I say it again so many contracts define 00:05:40.940 --> 00:05:46.600 align:start position:0% I say it again so many contracts define game<00:05:42.460> so<00:05:43.460> here<00:05:44.419> I'm<00:05:44.600> showing<00:05:45.039> stage<00:05:46.039> for 00:05:46.600 --> 00:05:46.610 align:start position:0% game so here I'm showing stage for 00:05:46.610 --> 00:05:50.350 align:start position:0% game so here I'm showing stage for contract<00:05:47.600> called<00:05:47.930> vault<00:05:48.860> it's<00:05:49.729> like<00:05:49.970> all 00:05:50.350 --> 00:05:50.360 align:start position:0% contract called vault it's like all 00:05:50.360 --> 00:05:54.610 align:start position:0% contract called vault it's like all right<00:05:50.479> it's<00:05:50.720> a<00:05:50.840> personal<00:05:51.289> wallet<00:05:51.760> but<00:05:53.620> it's 00:05:54.610 --> 00:05:54.620 align:start position:0% right it's a personal wallet but it's 00:05:54.620 --> 00:05:57.540 align:start position:0% right it's a personal wallet but it's trying<00:05:55.070> to<00:05:55.250> solve<00:05:55.430> is<00:05:55.669> well<00:05:56.300> somebody<00:05:57.080> might 00:05:57.540 --> 00:05:57.550 align:start position:0% trying to solve is well somebody might 00:05:57.550 --> 00:06:03.550 align:start position:0% trying to solve is well somebody might steal<00:05:58.550> your<00:05:59.000> private<00:05:59.450> key<00:05:59.930> so<00:06:02.169> the<00:06:03.169> solution 00:06:03.550 --> 00:06:03.560 align:start position:0% steal your private key so the solution 00:06:03.560 --> 00:06:07.620 align:start position:0% steal your private key so the solution here<00:06:03.590> is<00:06:04.180> involved<00:06:05.740> different<00:06:06.740> kinds<00:06:07.160> of<00:06:07.250> kids 00:06:07.620 --> 00:06:07.630 align:start position:0% here is involved different kinds of kids 00:06:07.630 --> 00:06:11.140 align:start position:0% here is involved different kinds of kids one<00:06:08.630> is<00:06:08.810> called<00:06:09.110> the<00:06:09.530> vault<00:06:09.830> key<00:06:10.250> the<00:06:10.729> other<00:06:10.940> is 00:06:11.140 --> 00:06:11.150 align:start position:0% one is called the vault key the other is 00:06:11.150 --> 00:06:14.770 align:start position:0% one is called the vault key the other is called<00:06:11.450> the<00:06:11.990> recovery<00:06:12.530> key<00:06:13.360> by<00:06:14.360> the<00:06:14.389> way<00:06:14.539> dia 00:06:14.770 --> 00:06:14.780 align:start position:0% called the recovery key by the way dia 00:06:14.780 --> 00:06:19.420 align:start position:0% called the recovery key by the way dia this<00:06:14.990> idea<00:06:15.440> comes<00:06:15.650> from<00:06:16.090> III<00:06:17.090> people<00:06:17.479> and<00:06:18.430> so 00:06:19.420 --> 00:06:19.430 align:start position:0% this idea comes from III people and so 00:06:19.430 --> 00:06:23.010 align:start position:0% this idea comes from III people and so it<00:06:19.610> was<00:06:19.880> an<00:06:20.330> example<00:06:20.780> for<00:06:21.020> a<00:06:21.560> new<00:06:21.860> Bitcoin 00:06:23.010 --> 00:06:23.020 align:start position:0% it was an example for a new Bitcoin 00:06:23.020 --> 00:06:26.110 align:start position:0% it was an example for a new Bitcoin script<00:06:24.020> primitive<00:06:24.530> but<00:06:24.889> well<00:06:25.669> from<00:06:25.910> there 00:06:26.110 --> 00:06:26.120 align:start position:0% script primitive but well from there 00:06:26.120 --> 00:06:30.010 align:start position:0% script primitive but well from there people<00:06:27.020> implemented<00:06:27.500> in<00:06:28.300> Israel<00:06:29.300> and<00:06:29.539> so<00:06:29.810> on 00:06:30.010 --> 00:06:30.020 align:start position:0% people implemented in Israel and so on 00:06:30.020 --> 00:06:34.000 align:start position:0% people implemented in Israel and so on stuff<00:06:30.500> happened<00:06:30.889> I'm<00:06:31.039> taking<00:06:31.940> these<00:06:32.090> ideas<00:06:33.010> so 00:06:34.000 --> 00:06:34.010 align:start position:0% stuff happened I'm taking these ideas so 00:06:34.010 --> 00:06:39.370 align:start position:0% stuff happened I'm taking these ideas so the<00:06:34.610> vault<00:06:34.850> key<00:06:35.150> is<00:06:35.419> your<00:06:36.760> usual<00:06:37.760> key<00:06:38.330> to<00:06:39.169> get 00:06:39.370 --> 00:06:39.380 align:start position:0% the vault key is your usual key to get 00:06:39.380 --> 00:06:42.340 align:start position:0% the vault key is your usual key to get your<00:06:39.590> money<00:06:39.770> out<00:06:40.070> of<00:06:40.190> the<00:06:40.520> wallet 00:06:42.340 --> 00:06:42.350 align:start position:0% your money out of the wallet 00:06:42.350 --> 00:06:45.940 align:start position:0% your money out of the wallet can<00:06:43.040> core<00:06:43.490> unboard<00:06:44.390> function<00:06:45.260> with<00:06:45.590> the<00:06:45.680> abort 00:06:45.940 --> 00:06:45.950 align:start position:0% can core unboard function with the abort 00:06:45.950 --> 00:06:49.630 align:start position:0% can core unboard function with the abort key<00:06:46.660> and<00:06:47.660> then<00:06:48.230> your<00:06:48.560> contract<00:06:48.920> enters<00:06:49.340> a 00:06:49.630 --> 00:06:49.640 align:start position:0% key and then your contract enters a 00:06:49.640 --> 00:06:52.720 align:start position:0% key and then your contract enters a special<00:06:50.300> state<00:06:50.710> you<00:06:51.710> have<00:06:51.860> to<00:06:51.980> wait<00:06:52.130> for<00:06:52.490> like 00:06:52.720 --> 00:06:52.730 align:start position:0% special state you have to wait for like 00:06:52.730 --> 00:06:56.560 align:start position:0% special state you have to wait for like three<00:06:53.090> weeks<00:06:53.330> or<00:06:53.930> four<00:06:53.960> weeks<00:06:55.210> some<00:06:56.210> some 00:06:56.560 --> 00:06:56.570 align:start position:0% three weeks or four weeks some some 00:06:56.570 --> 00:06:58.390 align:start position:0% three weeks or four weeks some some amount<00:06:56.900> of<00:06:56.990> time<00:06:57.170> written<00:06:57.530> in<00:06:57.650> a<00:06:57.740> program<00:06:58.100> and 00:06:58.390 --> 00:06:58.400 align:start position:0% amount of time written in a program and 00:06:58.400 --> 00:07:00.400 align:start position:0% amount of time written in a program and after<00:06:58.970> that<00:06:59.090> you<00:06:59.390> can<00:06:59.630> call<00:06:59.960> another<00:07:00.320> function 00:07:00.400 --> 00:07:00.410 align:start position:0% after that you can call another function 00:07:00.410 --> 00:07:03.400 align:start position:0% after that you can call another function called<00:07:01.070> redeem<00:07:01.430> and<00:07:01.850> then<00:07:02.270> a<00:07:02.540> payout<00:07:02.810> happens 00:07:03.400 --> 00:07:03.410 align:start position:0% called redeem and then a payout happens 00:07:03.410 --> 00:07:06.070 align:start position:0% called redeem and then a payout happens to<00:07:03.770> the<00:07:03.830> address<00:07:04.220> specified<00:07:04.490> in<00:07:05.360> the<00:07:05.690> unboard 00:07:06.070 --> 00:07:06.080 align:start position:0% to the address specified in the unboard 00:07:06.080 --> 00:07:12.160 align:start position:0% to the address specified in the unboard core<00:07:07.600> why<00:07:08.600> did<00:07:09.200> eight<00:07:09.350> weeks<00:07:10.780> because<00:07:11.780> well 00:07:12.160 --> 00:07:12.170 align:start position:0% core why did eight weeks because well 00:07:12.170 --> 00:07:14.440 align:start position:0% core why did eight weeks because well when<00:07:12.470> somebody<00:07:12.860> steals<00:07:13.280> your<00:07:13.490> border<00:07:14.000> key<00:07:14.210> and 00:07:14.440 --> 00:07:14.450 align:start position:0% when somebody steals your border key and 00:07:14.450 --> 00:07:15.640 align:start position:0% when somebody steals your border key and the<00:07:14.660> course<00:07:14.870> this<00:07:15.050> on<00:07:15.290> board 00:07:15.640 --> 00:07:15.650 align:start position:0% the course this on board 00:07:15.650 --> 00:07:18.100 align:start position:0% the course this on board well<00:07:16.070> you<00:07:16.700> can<00:07:16.880> check<00:07:17.150> the<00:07:17.390> contract<00:07:17.690> every 00:07:18.100 --> 00:07:18.110 align:start position:0% well you can check the contract every 00:07:18.110 --> 00:07:21.820 align:start position:0% well you can check the contract every week<00:07:18.550> and<00:07:19.550> then<00:07:20.540> if<00:07:20.720> somebody<00:07:21.230> else<00:07:21.380> is<00:07:21.590> trying 00:07:21.820 --> 00:07:21.830 align:start position:0% week and then if somebody else is trying 00:07:21.830 --> 00:07:27.010 align:start position:0% week and then if somebody else is trying to<00:07:22.220> get<00:07:22.700> your<00:07:22.880> money<00:07:23.410> you<00:07:24.410> can<00:07:24.910> reach<00:07:26.020> your 00:07:27.010 --> 00:07:27.020 align:start position:0% to get your money you can reach your 00:07:27.020 --> 00:07:29.650 align:start position:0% to get your money you can reach your more<00:07:27.860> important<00:07:28.520> key<00:07:28.760> called<00:07:29.120> the<00:07:29.210> recovery 00:07:29.650 --> 00:07:29.660 align:start position:0% more important key called the recovery 00:07:29.660 --> 00:07:32.500 align:start position:0% more important key called the recovery key<00:07:30.020> and<00:07:30.560> you<00:07:31.250> can<00:07:31.430> call<00:07:31.640> recover<00:07:31.970> and<00:07:32.180> you<00:07:32.330> can 00:07:32.500 --> 00:07:32.510 align:start position:0% key and you can call recover and you can 00:07:32.510 --> 00:07:35.080 align:start position:0% key and you can call recover and you can cancel<00:07:32.780> this<00:07:33.140> and<00:07:33.410> world<00:07:33.590> core<00:07:33.890> and<00:07:34.130> moreover 00:07:35.080 --> 00:07:35.090 align:start position:0% cancel this and world core and moreover 00:07:35.090 --> 00:07:37.000 align:start position:0% cancel this and world core and moreover you<00:07:35.420> can<00:07:35.630> change<00:07:35.930> this<00:07:36.170> border<00:07:36.590> key<00:07:36.770> so<00:07:36.920> you 00:07:37.000 --> 00:07:37.010 align:start position:0% you can change this border key so you 00:07:37.010 --> 00:07:38.650 align:start position:0% you can change this border key so you can<00:07:37.190> create<00:07:37.400> a<00:07:37.520> new<00:07:37.790> key<00:07:38.030> as<00:07:38.210> you<00:07:38.390> have<00:07:38.480> new 00:07:38.650 --> 00:07:38.660 align:start position:0% can create a new key as you have new 00:07:38.660 --> 00:07:42.060 align:start position:0% can create a new key as you have new vault<00:07:38.960> key<00:07:39.260> and<00:07:39.610> then<00:07:40.610> the<00:07:40.880> attackers 00:07:42.060 --> 00:07:42.070 align:start position:0% vault key and then the attackers 00:07:42.070 --> 00:07:44.800 align:start position:0% vault key and then the attackers attacker<00:07:43.070> cannot<00:07:43.340> do<00:07:43.550> anything<00:07:43.790> about<00:07:44.210> with 00:07:44.800 --> 00:07:44.810 align:start position:0% attacker cannot do anything about with 00:07:44.810 --> 00:07:49.570 align:start position:0% attacker cannot do anything about with this<00:07:45.230> old<00:07:45.530> boat<00:07:46.040> key<00:07:46.430> anymore<00:07:47.980> so<00:07:48.980> that's<00:07:49.190> the 00:07:49.570 --> 00:07:49.580 align:start position:0% this old boat key anymore so that's the 00:07:49.580 --> 00:07:50.110 align:start position:0% this old boat key anymore so that's the idea 00:07:50.110 --> 00:07:50.120 align:start position:0% idea 00:07:50.120 --> 00:07:53.260 align:start position:0% idea and<00:07:50.390> then<00:07:50.630> well<00:07:51.500> when<00:07:52.400> you<00:07:52.520> are<00:07:52.670> really<00:07:52.970> really 00:07:53.260 --> 00:07:53.270 align:start position:0% and then well when you are really really 00:07:53.270 --> 00:07:57.010 align:start position:0% and then well when you are really really under<00:07:54.170> key<00:07:54.440> the<00:07:54.980> attacker<00:07:55.400> can<00:07:56.330> still<00:07:56.750> both 00:07:57.010 --> 00:07:57.020 align:start position:0% under key the attacker can still both 00:07:57.020 --> 00:08:00.570 align:start position:0% under key the attacker can still both his<00:07:57.920> vault<00:07:58.370> key<00:07:58.700> and<00:07:59.000> the<00:07:59.120> recovery<00:07:59.330> key<00:07:59.750> then 00:08:00.570 --> 00:08:00.580 align:start position:0% his vault key and the recovery key then 00:08:00.580 --> 00:08:05.380 align:start position:0% his vault key and the recovery key then what<00:08:01.580> would<00:08:01.850> happen<00:08:02.150> is<00:08:03.010> both<00:08:04.010> parties<00:08:04.610> try<00:08:05.330> to 00:08:05.380 --> 00:08:05.390 align:start position:0% what would happen is both parties try to 00:08:05.390 --> 00:08:08.970 align:start position:0% what would happen is both parties try to withdraw<00:08:06.260> the<00:08:06.560> money<00:08:06.770> but<00:08:07.670> both<00:08:08.000> party 00:08:08.970 --> 00:08:08.980 align:start position:0% withdraw the money but both party 00:08:08.980 --> 00:08:12.850 align:start position:0% withdraw the money but both party buddies<00:08:09.980> keep<00:08:10.510> canceling<00:08:11.510> the<00:08:12.170> other<00:08:12.380> party's 00:08:12.850 --> 00:08:12.860 align:start position:0% buddies keep canceling the other party's 00:08:12.860 --> 00:08:16.840 align:start position:0% buddies keep canceling the other party's request<00:08:13.070> so<00:08:13.910> it<00:08:14.630> that<00:08:15.350> would<00:08:15.560> become<00:08:15.920> become<00:08:16.820> a 00:08:16.840 --> 00:08:16.850 align:start position:0% request so it that would become become a 00:08:16.850 --> 00:08:20.260 align:start position:0% request so it that would become become a stalemate<00:08:17.560> to<00:08:18.560> make<00:08:18.740> it<00:08:18.890> as<00:08:19.010> priests<00:08:19.340> explicit 00:08:20.260 --> 00:08:20.270 align:start position:0% stalemate to make it as priests explicit 00:08:20.270 --> 00:08:25.480 align:start position:0% stalemate to make it as priests explicit days<00:08:20.680> destroy<00:08:21.680> method<00:08:22.690> and<00:08:23.690> when<00:08:24.650> anybody 00:08:25.480 --> 00:08:25.490 align:start position:0% days destroy method and when anybody 00:08:25.490 --> 00:08:28.690 align:start position:0% days destroy method and when anybody with<00:08:25.910> the<00:08:26.210> recovery<00:08:26.600> key<00:08:26.960> holds<00:08:27.740> the<00:08:28.220> destroy 00:08:28.690 --> 00:08:28.700 align:start position:0% with the recovery key holds the destroy 00:08:28.700 --> 00:08:31.930 align:start position:0% with the recovery key holds the destroy method<00:08:28.840> the<00:08:29.840> contract<00:08:30.440> enter<00:08:30.860> enters<00:08:31.430> the 00:08:31.930 --> 00:08:31.940 align:start position:0% method the contract enter enters the 00:08:31.940 --> 00:08:34.510 align:start position:0% method the contract enter enters the destroyed<00:08:32.510> state<00:08:32.960> and<00:08:33.290> from<00:08:33.800> this<00:08:33.979> destroyed 00:08:34.510 --> 00:08:34.520 align:start position:0% destroyed state and from this destroyed 00:08:34.520 --> 00:08:37.330 align:start position:0% destroyed state and from this destroyed state<00:08:34.910> nobody<00:08:35.510> can<00:08:35.960> get<00:08:36.200> anything<00:08:37.040> out<00:08:37.310> of 00:08:37.330 --> 00:08:37.340 align:start position:0% state nobody can get anything out of 00:08:37.340 --> 00:08:45.790 align:start position:0% state nobody can get anything out of this<00:08:37.669> contract<00:08:38.680> this<00:08:39.680> kind<00:08:40.010> of<00:08:42.789> cancels<00:08:44.800> this 00:08:45.790 --> 00:08:45.800 align:start position:0% this contract this kind of cancels this 00:08:45.800 --> 00:08:51.100 align:start position:0% this contract this kind of cancels this notifies<00:08:46.430> the<00:08:48.940> incentives<00:08:49.940> to<00:08:50.300> steal<00:08:50.660> any<00:08:50.900> of 00:08:51.100 --> 00:08:51.110 align:start position:0% notifies the incentives to steal any of 00:08:51.110 --> 00:08:55.720 align:start position:0% notifies the incentives to steal any of these<00:08:51.350> kids<00:08:52.960> at<00:08:53.960> most<00:08:54.290> I<00:08:54.650> mean<00:08:54.860> we've<00:08:55.220> used 00:08:55.720 --> 00:08:55.730 align:start position:0% these kids at most I mean we've used 00:08:55.730 --> 00:08:58.740 align:start position:0% these kids at most I mean we've used student<00:08:56.839> both<00:08:57.199> kids<00:08:57.709> you<00:08:58.310> will 00:08:58.740 --> 00:08:58.750 align:start position:0% student both kids you will 00:08:58.750 --> 00:09:01.600 align:start position:0% student both kids you will probably<00:08:59.769> get<00:09:00.769> nothing 00:09:01.600 --> 00:09:01.610 align:start position:0% probably get nothing 00:09:01.610 --> 00:09:06.400 align:start position:0% probably get nothing that<00:09:02.449> kind<00:09:02.750> of<00:09:03.610> chases<00:09:04.610> thieves<00:09:05.600> away<00:09:05.990> that's 00:09:06.400 --> 00:09:06.410 align:start position:0% that kind of chases thieves away that's 00:09:06.410 --> 00:09:13.000 align:start position:0% that kind of chases thieves away that's the<00:09:06.589> idea<00:09:09.730> when<00:09:10.730> you<00:09:10.820> implement<00:09:11.120> it<00:09:11.449> in<00:09:11.630> 3d<00:09:12.199> you 00:09:13.000 --> 00:09:13.010 align:start position:0% the idea when you implement it in 3d you 00:09:13.010 --> 00:09:17.590 align:start position:0% the idea when you implement it in 3d you can<00:09:13.160> do<00:09:13.370> that<00:09:15.399> and<00:09:16.399> then<00:09:16.850> you<00:09:17.060> want<00:09:17.269> to<00:09:17.389> check 00:09:17.590 --> 00:09:17.600 align:start position:0% can do that and then you want to check 00:09:17.600 --> 00:09:21.220 align:start position:0% can do that and then you want to check if<00:09:18.110> this<00:09:18.829> contract<00:09:19.310> if<00:09:20.060> this<00:09:20.449> code<00:09:20.810> matches 00:09:21.220 --> 00:09:21.230 align:start position:0% if this contract if this code matches 00:09:21.230 --> 00:09:25.840 align:start position:0% if this contract if this code matches the<00:09:21.769> state<00:09:22.070> diagram<00:09:22.370> I<00:09:23.000> drew<00:09:24.490> for<00:09:25.490> checking 00:09:25.840 --> 00:09:25.850 align:start position:0% the state diagram I drew for checking 00:09:25.850 --> 00:09:30.030 align:start position:0% the state diagram I drew for checking that<00:09:26.089> first<00:09:26.930> I<00:09:27.139> have<00:09:27.350> to<00:09:27.500> identify<00:09:28.779> what 00:09:30.030 --> 00:09:30.040 align:start position:0% that first I have to identify what 00:09:30.040 --> 00:09:37.420 align:start position:0% that first I have to identify what solidity<00:09:31.040> state<00:09:32.440> correspond<00:09:34.060> the<00:09:36.220> states<00:09:37.220> in 00:09:37.420 --> 00:09:37.430 align:start position:0% solidity state correspond the states in 00:09:37.430 --> 00:09:41.230 align:start position:0% solidity state correspond the states in boxing's<00:09:37.970> in<00:09:38.180> the<00:09:38.510> state<00:09:38.750> diagram<00:09:39.070> so<00:09:40.070> in<00:09:41.000> this 00:09:41.230 --> 00:09:41.240 align:start position:0% boxing's in the state diagram so in this 00:09:41.240 --> 00:09:43.240 align:start position:0% boxing's in the state diagram so in this case<00:09:41.480> it's<00:09:41.690> easy<00:09:41.899> there<00:09:42.560> are<00:09:42.589> only<00:09:42.889> three 00:09:43.240 --> 00:09:43.250 align:start position:0% case it's easy there are only three 00:09:43.250 --> 00:09:46.980 align:start position:0% case it's easy there are only three states<00:09:44.149> when<00:09:44.899> destroyed<00:09:45.649> boolean<00:09:46.459> is<00:09:46.699> true 00:09:46.980 --> 00:09:46.990 align:start position:0% states when destroyed boolean is true 00:09:46.990 --> 00:09:52.540 align:start position:0% states when destroyed boolean is true it's<00:09:47.990> destroyed<00:09:48.850> otherwise<00:09:51.160> amount<00:09:52.160> is<00:09:52.339> zero 00:09:52.540 --> 00:09:52.550 align:start position:0% it's destroyed otherwise amount is zero 00:09:52.550 --> 00:09:55.210 align:start position:0% it's destroyed otherwise amount is zero it's<00:09:53.360> the<00:09:53.540> normal<00:09:53.839> state<00:09:54.170> if<00:09:54.410> this<00:09:54.680> number<00:09:54.949> is 00:09:55.210 --> 00:09:55.220 align:start position:0% it's the normal state if this number is 00:09:55.220 --> 00:10:01.559 align:start position:0% it's the normal state if this number is not<00:09:55.490> zero<00:09:55.880> it's<00:09:57.040> unbolting<00:09:58.040> waiting<00:09:58.670> state 00:10:01.559 --> 00:10:01.569 align:start position:0% 00:10:01.569 --> 00:10:04.120 align:start position:0% this<00:10:02.569> is<00:10:02.690> not<00:10:02.959> hard<00:10:03.260> but<00:10:03.500> it<00:10:03.709> certainly 00:10:04.120 --> 00:10:04.130 align:start position:0% this is not hard but it certainly 00:10:04.130 --> 00:10:09.939 align:start position:0% this is not hard but it certainly requires<00:10:05.920> human<00:10:07.000> judgment<00:10:08.000> and<00:10:08.199> then<00:10:09.199> after 00:10:09.939 --> 00:10:09.949 align:start position:0% requires human judgment and then after 00:10:09.949 --> 00:10:12.819 align:start position:0% requires human judgment and then after that<00:10:10.149> after<00:10:11.149> that<00:10:11.540> everything<00:10:12.380> can<00:10:12.589> be<00:10:12.649> done 00:10:12.819 --> 00:10:12.829 align:start position:0% that after that everything can be done 00:10:12.829 --> 00:10:14.949 align:start position:0% that after that everything can be done kind<00:10:13.399> of<00:10:13.490> automatically<00:10:14.060> because<00:10:14.540> this 00:10:14.949 --> 00:10:14.959 align:start position:0% kind of automatically because this 00:10:14.959 --> 00:10:18.340 align:start position:0% kind of automatically because this involves<00:10:15.500> no<00:10:15.740> loops<00:10:16.040> but<00:10:16.870> for<00:10:17.870> doing<00:10:18.050> that 00:10:18.340 --> 00:10:18.350 align:start position:0% involves no loops but for doing that 00:10:18.350 --> 00:10:19.960 align:start position:0% involves no loops but for doing that first<00:10:19.069> you<00:10:19.279> have<00:10:19.399> to<00:10:19.430> look<00:10:19.699> at<00:10:19.880> the 00:10:19.960 --> 00:10:19.970 align:start position:0% first you have to look at the 00:10:19.970 --> 00:10:24.759 align:start position:0% first you have to look at the constructor<00:10:20.569> okay<00:10:21.819> it<00:10:22.819> returns<00:10:23.630> the<00:10:23.990> usual 00:10:24.759 --> 00:10:24.769 align:start position:0% constructor okay it returns the usual 00:10:24.769 --> 00:10:27.340 align:start position:0% constructor okay it returns the usual state<00:10:25.100> not<00:10:25.430> to<00:10:25.459> any<00:10:26.300> other<00:10:26.569> state<00:10:26.720> that's<00:10:27.079> good 00:10:27.340 --> 00:10:27.350 align:start position:0% state not to any other state that's good 00:10:27.350 --> 00:10:29.650 align:start position:0% state not to any other state that's good and<00:10:27.769> then<00:10:28.399> you<00:10:28.610> have<00:10:28.790> to<00:10:29.000> read<00:10:29.180> the<00:10:29.329> rest<00:10:29.360> of 00:10:29.650 --> 00:10:29.660 align:start position:0% and then you have to read the rest of 00:10:29.660 --> 00:10:33.550 align:start position:0% and then you have to read the rest of the<00:10:29.839> program<00:10:30.230> three<00:10:31.130> times<00:10:31.399> because<00:10:32.560> starting 00:10:33.550 --> 00:10:33.560 align:start position:0% the program three times because starting 00:10:33.560 --> 00:10:36.790 align:start position:0% the program three times because starting from<00:10:33.620> the<00:10:33.949> usual<00:10:34.339> state<00:10:34.699> well<00:10:35.240> which<00:10:35.800> function 00:10:36.790 --> 00:10:36.800 align:start position:0% from the usual state well which function 00:10:36.800 --> 00:10:39.360 align:start position:0% from the usual state well which function can<00:10:37.220> be<00:10:37.250> colder<00:10:37.940> you<00:10:38.029> have<00:10:38.209> to<00:10:38.389> check<00:10:38.660> all 00:10:39.360 --> 00:10:39.370 align:start position:0% can be colder you have to check all 00:10:39.370 --> 00:10:42.009 align:start position:0% can be colder you have to check all interface<00:10:40.370> functions<00:10:41.089> because<00:10:41.839> they 00:10:42.009 --> 00:10:42.019 align:start position:0% interface functions because they 00:10:42.019 --> 00:10:47.230 align:start position:0% interface functions because they anything<00:10:42.860> can<00:10:43.310> be<00:10:43.490> called<00:10:43.930> from<00:10:45.940> anything<00:10:46.940> can 00:10:47.230 --> 00:10:47.240 align:start position:0% anything can be called from anything can 00:10:47.240 --> 00:10:50.769 align:start position:0% anything can be called from anything can be<00:10:47.480> called<00:10:47.870> on<00:10:48.230> any<00:10:48.740> state<00:10:49.279> by<00:10:49.790> default<00:10:50.180> so<00:10:50.720> you 00:10:50.769 --> 00:10:50.779 align:start position:0% be called on any state by default so you 00:10:50.779 --> 00:10:55.030 align:start position:0% be called on any state by default so you have<00:10:51.139> to<00:10:51.350> check<00:10:52.750> whatever<00:10:53.750> happens<00:10:54.380> from<00:10:54.709> each 00:10:55.030 --> 00:10:55.040 align:start position:0% have to check whatever happens from each 00:10:55.040 --> 00:11:01.360 align:start position:0% have to check whatever happens from each state<00:10:56.170> for<00:10:57.170> each<00:10:58.209> function<00:10:59.290> and<00:11:00.290> then<00:11:00.620> the 00:11:01.360 --> 00:11:01.370 align:start position:0% state for each function and then the 00:11:01.370 --> 00:11:03.100 align:start position:0% state for each function and then the default<00:11:01.639> function<00:11:01.940> is<00:11:02.329> called<00:11:02.540> the<00:11:02.839> state 00:11:03.100 --> 00:11:03.110 align:start position:0% default function is called the state 00:11:03.110 --> 00:11:05.500 align:start position:0% default function is called the state doesn't<00:11:03.380> change<00:11:03.829> so<00:11:04.220> from<00:11:04.699> usual<00:11:05.060> it<00:11:05.180> stays 00:11:05.500 --> 00:11:05.510 align:start position:0% doesn't change so from usual it stays 00:11:05.510 --> 00:11:09.189 align:start position:0% doesn't change so from usual it stays usual<00:11:07.449> okay 00:11:09.189 --> 00:11:09.199 align:start position:0% usual okay 00:11:09.199 --> 00:11:13.929 align:start position:0% usual okay when<00:11:09.559> unboard<00:11:10.429> is<00:11:10.639> called<00:11:12.009> so<00:11:13.009> the<00:11:13.309> state<00:11:13.670> can 00:11:13.929 --> 00:11:13.939 align:start position:0% when unboard is called so the state can 00:11:13.939 --> 00:11:17.379 align:start position:0% when unboard is called so the state can become<00:11:14.329> unbolting<00:11:15.139> but<00:11:15.859> if<00:11:16.129> the<00:11:16.879> argument 00:11:17.379 --> 00:11:17.389 align:start position:0% become unbolting but if the argument 00:11:17.389 --> 00:11:19.869 align:start position:0% become unbolting but if the argument amount<00:11:17.779> is<00:11:17.929> zero<00:11:17.959> it<00:11:18.499> can<00:11:18.769> stay<00:11:19.040> in<00:11:19.249> usual 00:11:19.869 --> 00:11:19.879 align:start position:0% amount is zero it can stay in usual 00:11:19.879 --> 00:11:23.799 align:start position:0% amount is zero it can stay in usual that's<00:11:20.720> not<00:11:20.929> wrong<00:11:21.230> in<00:11:21.649> the<00:11:22.609> state<00:11:22.910> diagram<00:11:23.119> so 00:11:23.799 --> 00:11:23.809 align:start position:0% that's not wrong in the state diagram so 00:11:23.809 --> 00:11:28.769 align:start position:0% that's not wrong in the state diagram so I<00:11:23.839> put<00:11:24.170> a<00:11:24.199> question<00:11:24.499> mark<00:11:26.230> and<00:11:27.230> then<00:11:27.499> if<00:11:28.069> you 00:11:28.769 --> 00:11:28.779 align:start position:0% I put a question mark and then if you 00:11:28.779 --> 00:11:32.939 align:start position:0% I put a question mark and then if you when<00:11:29.779> medium<00:11:30.369> function<00:11:31.369> is<00:11:31.519> called<00:11:31.819> it 00:11:32.939 --> 00:11:32.949 align:start position:0% when medium function is called it 00:11:32.949 --> 00:11:37.780 align:start position:0% when medium function is called it doesn't<00:11:33.949> do<00:11:34.160> anything<00:11:34.899> then<00:11:35.949> when<00:11:36.949> I<00:11:37.220> know<00:11:37.519> it 00:11:37.780 --> 00:11:37.790 align:start position:0% doesn't do anything then when I know it 00:11:37.790 --> 00:11:39.879 align:start position:0% doesn't do anything then when I know it touched<00:11:38.119> something<00:11:38.449> it<00:11:39.410> does<00:11:39.649> something 00:11:39.879 --> 00:11:39.889 align:start position:0% touched something it does something 00:11:39.889 --> 00:11:43.119 align:start position:0% touched something it does something actually<00:11:40.399> it<00:11:40.970> sends<00:11:41.419> you<00:11:41.600> know<00:11:42.259> it<00:11:42.379> sends<00:11:42.919> some 00:11:43.119 --> 00:11:43.129 align:start position:0% actually it sends you know it sends some 00:11:43.129 --> 00:11:45.400 align:start position:0% actually it sends you know it sends some zero<00:11:43.549> amount<00:11:43.879> of<00:11:44.119> visa<00:11:44.329> to<00:11:44.720> somebody<00:11:45.109> and 00:11:45.400 --> 00:11:45.410 align:start position:0% zero amount of visa to somebody and 00:11:45.410 --> 00:11:49.599 align:start position:0% zero amount of visa to somebody and becomes<00:11:46.160> user<00:11:46.639> so<00:11:46.999> it's<00:11:47.419> again<00:11:48.609> questionable 00:11:49.599 --> 00:11:49.609 align:start position:0% becomes user so it's again questionable 00:11:49.609 --> 00:11:55.720 align:start position:0% becomes user so it's again questionable behavior<00:11:50.239> and<00:11:50.720> when<00:11:51.290> we<00:11:51.439> cover<00:11:51.709> is<00:11:51.949> called<00:11:54.730> no 00:11:55.720 --> 00:11:55.730 align:start position:0% behavior and when we cover is called no 00:11:55.730 --> 00:11:57.970 align:start position:0% behavior and when we cover is called no it<00:11:56.239> doesn't<00:11:56.600> do<00:11:56.749> anything<00:11:57.139> so<00:11:57.499> that's<00:11:57.709> good 00:11:57.970 --> 00:11:57.980 align:start position:0% it doesn't do anything so that's good 00:11:57.980 --> 00:12:01.299 align:start position:0% it doesn't do anything so that's good and<00:11:58.309> when<00:11:59.269> this<00:11:59.449> choice<00:11:59.720> is<00:11:59.959> called<00:12:00.410> it 00:12:01.299 --> 00:12:01.309 align:start position:0% and when this choice is called it 00:12:01.309 --> 00:12:03.819 align:start position:0% and when this choice is called it becomes<00:12:01.790> destroyed<00:12:02.299> that's<00:12:02.629> good<00:12:02.989> as 00:12:03.819 --> 00:12:03.829 align:start position:0% becomes destroyed that's good as 00:12:03.829 --> 00:12:08.019 align:start position:0% becomes destroyed that's good as specified<00:12:04.639> in<00:12:04.970> the<00:12:05.179> diagram<00:12:06.220> and<00:12:07.220> I<00:12:07.730> have<00:12:07.879> to 00:12:08.019 --> 00:12:08.029 align:start position:0% specified in the diagram and I have to 00:12:08.029 --> 00:12:12.220 align:start position:0% specified in the diagram and I have to do<00:12:08.239> it<00:12:08.389> like<00:12:08.689> three<00:12:09.679> times<00:12:10.480> when<00:12:11.480> the<00:12:11.809> contract 00:12:12.220 --> 00:12:12.230 align:start position:0% do it like three times when the contract 00:12:12.230 --> 00:12:14.470 align:start position:0% do it like three times when the contract is<00:12:12.439> in<00:12:12.619> unbolting<00:12:13.429> state<00:12:13.759> that<00:12:14.299> means 00:12:14.470 --> 00:12:14.480 align:start position:0% is in unbolting state that means 00:12:14.480 --> 00:12:16.869 align:start position:0% is in unbolting state that means destroyed<00:12:15.049> is<00:12:15.290> forest<00:12:15.799> and<00:12:15.949> unbolted<00:12:16.579> amount 00:12:16.869 --> 00:12:16.879 align:start position:0% destroyed is forest and unbolted amount 00:12:16.879 --> 00:12:21.819 align:start position:0% destroyed is forest and unbolted amount is<00:12:17.029> not<00:12:17.239> zero<00:12:19.660> yes<00:12:20.660> you<00:12:20.839> can<00:12:20.989> call<00:12:21.259> this<00:12:21.529> on 00:12:21.819 --> 00:12:21.829 align:start position:0% is not zero yes you can call this on 00:12:21.829 --> 00:12:25.869 align:start position:0% is not zero yes you can call this on board<00:12:22.129> again<00:12:22.730> well<00:12:23.480> I<00:12:23.720> know<00:12:24.230> okay<00:12:25.069> well<00:12:25.249> you 00:12:25.869 --> 00:12:25.879 align:start position:0% board again well I know okay well you 00:12:25.879 --> 00:12:27.850 align:start position:0% board again well I know okay well you can<00:12:26.059> call<00:12:26.329> the<00:12:26.509> default<00:12:26.869> function<00:12:27.110> that's 00:12:27.850 --> 00:12:27.860 align:start position:0% can call the default function that's 00:12:27.860 --> 00:12:29.019 align:start position:0% can call the default function that's fine 00:12:29.019 --> 00:12:29.029 align:start position:0% fine 00:12:29.029 --> 00:12:31.989 align:start position:0% fine you<00:12:29.389> can<00:12:29.629> call<00:12:29.929> so<00:12:30.230> call<00:12:30.259> the<00:12:30.919> unbolt<00:12:31.399> function 00:12:31.989 --> 00:12:31.999 align:start position:0% you can call so call the unbolt function 00:12:31.999 --> 00:12:35.470 align:start position:0% you can call so call the unbolt function again<00:12:32.419> that<00:12:33.019> was<00:12:33.199> not<00:12:33.230> join<00:12:33.769> the<00:12:34.160> diagram<00:12:34.639> is 00:12:35.470 --> 00:12:35.480 align:start position:0% again that was not join the diagram is 00:12:35.480 --> 00:12:38.100 align:start position:0% again that was not join the diagram is that<00:12:35.569> fine<00:12:36.019> or<00:12:36.169> not<00:12:36.259> I<00:12:36.410> have<00:12:36.679> to<00:12:36.860> think<00:12:37.069> again 00:12:38.100 --> 00:12:38.110 align:start position:0% that fine or not I have to think again 00:12:38.110 --> 00:12:41.829 align:start position:0% that fine or not I have to think again when<00:12:39.110> we<00:12:39.290> deem<00:12:39.499> function<00:12:40.069> is<00:12:40.329> yes<00:12:41.329> this<00:12:41.569> can 00:12:41.829 --> 00:12:41.839 align:start position:0% when we deem function is yes this can 00:12:41.839 --> 00:12:47.199 align:start position:0% when we deem function is yes this can become<00:12:41.989> user<00:12:42.319> that's<00:12:42.709> fine<00:12:44.079> as<00:12:45.079> specified<00:12:46.209> and 00:12:47.199 --> 00:12:47.209 align:start position:0% become user that's fine as specified and 00:12:47.209 --> 00:12:49.150 align:start position:0% become user that's fine as specified and when<00:12:47.449> we<00:12:47.629> cover<00:12:47.899> is<00:12:48.079> code<00:12:48.290> it<00:12:48.499> goes<00:12:48.739> back<00:12:48.980> to 00:12:49.150 --> 00:12:49.160 align:start position:0% when we cover is code it goes back to 00:12:49.160 --> 00:12:51.249 align:start position:0% when we cover is code it goes back to usual<00:12:49.309> canceled<00:12:49.999> in<00:12:50.089> this<00:12:50.329> waiting<00:12:50.839> request 00:12:51.249 --> 00:12:51.259 align:start position:0% usual canceled in this waiting request 00:12:51.259 --> 00:12:52.150 align:start position:0% usual canceled in this waiting request that's<00:12:51.529> fine 00:12:52.150 --> 00:12:52.160 align:start position:0% that's fine 00:12:52.160 --> 00:12:54.939 align:start position:0% that's fine when<00:12:52.789> this<00:12:52.970> joy<00:12:53.239> is<00:12:53.480> called<00:12:53.839> it<00:12:54.470> becomes 00:12:54.939 --> 00:12:54.949 align:start position:0% when this joy is called it becomes 00:12:54.949 --> 00:13:00.249 align:start position:0% when this joy is called it becomes destroyed<00:12:55.579> that's<00:12:55.970> fine<00:12:57.189> and<00:12:58.189> then<00:12:59.079> the<00:13:00.079> rest 00:13:00.249 --> 00:13:00.259 align:start position:0% destroyed that's fine and then the rest 00:13:00.259 --> 00:13:03.150 align:start position:0% destroyed that's fine and then the rest is<00:13:00.410> kind<00:13:00.919> of<00:13:01.009> easy<00:13:01.220> because<00:13:01.489> everything<00:13:02.480> every 00:13:03.150 --> 00:13:03.160 align:start position:0% is kind of easy because everything every 00:13:03.160 --> 00:13:06.400 align:start position:0% is kind of easy because everything every every<00:13:04.160> interface<00:13:04.369> function<00:13:05.059> is<00:13:05.600> prefixed 00:13:06.400 --> 00:13:06.410 align:start position:0% every interface function is prefixed 00:13:06.410 --> 00:13:08.619 align:start position:0% every interface function is prefixed with<00:13:06.529> this<00:13:06.859> modifier<00:13:07.339> not<00:13:07.910> destroyed<00:13:08.389> not 00:13:08.619 --> 00:13:08.629 align:start position:0% with this modifier not destroyed not 00:13:08.629 --> 00:13:13.989 align:start position:0% with this modifier not destroyed not destroyed<00:13:09.109> so<00:13:11.350> the<00:13:12.350> core<00:13:12.559> is<00:13:12.589> aborted<00:13:13.279> nothing 00:13:13.989 --> 00:13:13.999 align:start position:0% destroyed so the core is aborted nothing 00:13:13.999 --> 00:13:16.059 align:start position:0% destroyed so the core is aborted nothing can<00:13:14.179> happen<00:13:14.329> from<00:13:14.720> destroyed<00:13:15.139> that<00:13:15.439> that<00:13:15.889> was 00:13:16.059 --> 00:13:16.069 align:start position:0% can happen from destroyed that that was 00:13:16.069 --> 00:13:17.949 align:start position:0% can happen from destroyed that that was the<00:13:16.249> easy<00:13:16.369> case<00:13:16.609> but<00:13:16.939> anyway<00:13:17.269> I<00:13:17.299> had<00:13:17.539> to<00:13:17.749> read 00:13:17.949 --> 00:13:17.959 align:start position:0% the easy case but anyway I had to read 00:13:17.959 --> 00:13:21.279 align:start position:0% the easy case but anyway I had to read the<00:13:18.169> program<00:13:18.470> three<00:13:18.709> times<00:13:19.299> because<00:13:20.299> of<00:13:20.509> the 00:13:21.279 --> 00:13:21.289 align:start position:0% the program three times because of the 00:13:21.289 --> 00:13:22.930 align:start position:0% the program three times because of the state<00:13:21.499> of<00:13:21.619> diagram<00:13:22.009> hardest 00:13:22.930 --> 00:13:22.940 align:start position:0% state of diagram hardest 00:13:22.940 --> 00:13:26.199 align:start position:0% state of diagram hardest boxes<00:13:24.070> that's<00:13:25.070> not<00:13:25.250> efficient 00:13:26.199 --> 00:13:26.209 align:start position:0% boxes that's not efficient 00:13:26.209 --> 00:13:29.560 align:start position:0% boxes that's not efficient so<00:13:27.399> essentially<00:13:28.399> viewing<00:13:28.970> a<00:13:29.060> program<00:13:29.360> takes 00:13:29.560 --> 00:13:29.570 align:start position:0% so essentially viewing a program takes 00:13:29.570 --> 00:13:32.199 align:start position:0% so essentially viewing a program takes at<00:13:29.750> least<00:13:29.959> the<00:13:30.410> number<00:13:30.589> of<00:13:30.860> states<00:13:31.190> times<00:13:31.760> the 00:13:32.199 --> 00:13:32.209 align:start position:0% at least the number of states times the 00:13:32.209 --> 00:13:36.160 align:start position:0% at least the number of states times the number<00:13:32.540> of<00:13:32.600> kinds<00:13:34.300> this<00:13:35.300> is<00:13:35.480> not<00:13:35.690> only<00:13:35.959> for 00:13:36.160 --> 00:13:36.170 align:start position:0% number of kinds this is not only for 00:13:36.170 --> 00:13:38.829 align:start position:0% number of kinds this is not only for human<00:13:36.830> reviewers<00:13:37.610> but<00:13:37.850> also<00:13:38.089> for<00:13:38.540> any 00:13:38.829 --> 00:13:38.839 align:start position:0% human reviewers but also for any 00:13:38.839 --> 00:13:43.840 align:start position:0% human reviewers but also for any automatic<00:13:39.560> methods<00:13:40.990> that's<00:13:41.990> not<00:13:42.370> good<00:13:43.370> and 00:13:43.840 --> 00:13:43.850 align:start position:0% automatic methods that's not good and 00:13:43.850 --> 00:13:47.769 align:start position:0% automatic methods that's not good and when<00:13:44.300> you<00:13:44.330> try<00:13:45.050> to<00:13:45.399> check<00:13:46.399> the<00:13:46.730> same<00:13:46.940> thing<00:13:47.300> for 00:13:47.769 --> 00:13:47.779 align:start position:0% when you try to check the same thing for 00:13:47.779 --> 00:13:50.320 align:start position:0% when you try to check the same thing for a<00:13:47.990> bamboo<00:13:48.410> program<00:13:48.800> it's<00:13:48.980> easier<00:13:49.940> that's<00:13:50.120> my 00:13:50.320 --> 00:13:50.330 align:start position:0% a bamboo program it's easier that's my 00:13:50.330 --> 00:13:55.630 align:start position:0% a bamboo program it's easier that's my claim<00:13:51.730> you<00:13:52.730> have<00:13:52.940> five<00:13:53.300> arrows<00:13:53.630> in<00:13:54.080> the<00:13:54.640> state 00:13:55.630 --> 00:13:55.640 align:start position:0% claim you have five arrows in the state 00:13:55.640 --> 00:14:00.519 align:start position:0% claim you have five arrows in the state diagram<00:13:56.350> and<00:13:57.350> you<00:13:57.589> have<00:13:57.770> five<00:13:58.100> become<00:13:59.529> rages 00:14:00.519 --> 00:14:00.529 align:start position:0% diagram and you have five become rages 00:14:00.529 --> 00:14:02.110 align:start position:0% diagram and you have five become rages in<00:14:01.190> the<00:14:01.430> program 00:14:02.110 --> 00:14:02.120 align:start position:0% in the program 00:14:02.120 --> 00:14:04.600 align:start position:0% in the program so<00:14:02.930> essentially<00:14:03.380> you<00:14:03.649> need<00:14:03.890> to<00:14:04.100> check<00:14:04.310> which 00:14:04.600 --> 00:14:04.610 align:start position:0% so essentially you need to check which 00:14:04.610 --> 00:14:07.000 align:start position:0% so essentially you need to check which one<00:14:05.209> corresponds<00:14:05.779> to<00:14:05.899> which<00:14:06.200> and<00:14:06.560> from<00:14:06.860> the 00:14:07.000 --> 00:14:07.010 align:start position:0% one corresponds to which and from the 00:14:07.010 --> 00:14:10.920 align:start position:0% one corresponds to which and from the user<00:14:07.190> state<00:14:07.700> there<00:14:08.029> are<00:14:08.260> arrows<00:14:09.260> going<00:14:09.560> up<00:14:09.860> out 00:14:10.920 --> 00:14:10.930 align:start position:0% user state there are arrows going up out 00:14:10.930 --> 00:14:13.449 align:start position:0% user state there are arrows going up out one<00:14:11.930> is<00:14:12.110> going<00:14:12.350> to<00:14:12.440> important<00:14:13.010> when<00:14:13.190> the<00:14:13.310> other 00:14:13.449 --> 00:14:13.459 align:start position:0% one is going to important when the other 00:14:13.459 --> 00:14:15.490 align:start position:0% one is going to important when the other is<00:14:13.640> going<00:14:13.820> to<00:14:14.029> destroy<00:14:14.450> and<00:14:14.810> the<00:14:14.930> yes<00:14:15.140> man<00:14:15.320> is 00:14:15.490 --> 00:14:15.500 align:start position:0% is going to destroy and the yes man is 00:14:15.500 --> 00:14:17.650 align:start position:0% is going to destroy and the yes man is going<00:14:15.800> to<00:14:16.010> unload<00:14:16.550> and<00:14:16.850> the<00:14:16.940> other<00:14:17.060> is<00:14:17.270> going 00:14:17.650 --> 00:14:17.660 align:start position:0% going to unload and the other is going 00:14:17.660 --> 00:14:20.949 align:start position:0% going to unload and the other is going to<00:14:17.839> destroyed<00:14:18.820> from<00:14:19.820> the<00:14:19.880> unbolting<00:14:20.600> state 00:14:20.949 --> 00:14:20.959 align:start position:0% to destroyed from the unbolting state 00:14:20.959 --> 00:14:23.320 align:start position:0% to destroyed from the unbolting state there<00:14:21.350> are<00:14:21.380> three<00:14:21.830> arrows<00:14:22.160> going<00:14:22.490> out<00:14:22.850> on<00:14:23.149> the 00:14:23.320 --> 00:14:23.330 align:start position:0% there are three arrows going out on the 00:14:23.330 --> 00:14:28.650 align:start position:0% there are three arrows going out on the yes<00:14:23.570> there<00:14:23.870> are<00:14:24.080> three<00:14:24.320> becomes<00:14:26.020> raises<00:14:27.220> so 00:14:28.650 --> 00:14:28.660 align:start position:0% yes there are three becomes raises so 00:14:28.660 --> 00:14:33.190 align:start position:0% yes there are three becomes raises so it's<00:14:29.660> much<00:14:29.839> easier<00:14:30.230> to<00:14:30.320> check<00:14:31.779> the<00:14:32.779> program 00:14:33.190 --> 00:14:33.200 align:start position:0% it's much easier to check the program 00:14:33.200 --> 00:14:36.040 align:start position:0% it's much easier to check the program corresponds<00:14:33.680> to<00:14:33.800> the<00:14:34.070> state<00:14:34.279> diagram<00:14:34.490> um<00:14:35.050> it's 00:14:36.040 --> 00:14:36.050 align:start position:0% corresponds to the state diagram um it's 00:14:36.050 --> 00:14:37.660 align:start position:0% corresponds to the state diagram um it's kind<00:14:36.260> of<00:14:36.320> cheating<00:14:36.529> because<00:14:36.770> I<00:14:36.980> chose<00:14:37.399> this 00:14:37.660 --> 00:14:37.670 align:start position:0% kind of cheating because I chose this 00:14:37.670 --> 00:14:40.090 align:start position:0% kind of cheating because I chose this format<00:14:38.180> of<00:14:38.480> presenting<00:14:39.140> states<00:14:39.470> and<00:14:39.709> I<00:14:39.829> chose 00:14:40.090 --> 00:14:40.100 align:start position:0% format of presenting states and I chose 00:14:40.100 --> 00:14:42.490 align:start position:0% format of presenting states and I chose the<00:14:40.310> syntax<00:14:40.820> of<00:14:41.060> writing<00:14:41.420> programs<00:14:41.839> it's<00:14:42.260> kind 00:14:42.490 --> 00:14:42.500 align:start position:0% the syntax of writing programs it's kind 00:14:42.500 --> 00:14:48.340 align:start position:0% the syntax of writing programs it's kind of<00:14:42.589> obvious<00:14:46.209> interesting<00:14:47.209> thing<00:14:47.420> is<00:14:47.630> how<00:14:48.020> far 00:14:48.340 --> 00:14:48.350 align:start position:0% of obvious interesting thing is how far 00:14:48.350 --> 00:14:55.690 align:start position:0% of obvious interesting thing is how far I<00:14:48.620> can<00:14:48.740> keep<00:14:49.370> this<00:14:49.850> discipline<00:14:54.490> they<00:14:55.490> want 00:14:55.690 --> 00:14:55.700 align:start position:0% I can keep this discipline they want 00:14:55.700 --> 00:15:00.130 align:start position:0% I can keep this discipline they want want<00:14:55.970> more<00:14:56.329> features<00:14:58.120> and<00:14:59.120> along<00:14:59.510> the<00:14:59.690> way<00:14:59.839> how 00:15:00.130 --> 00:15:00.140 align:start position:0% want more features and along the way how 00:15:00.140 --> 00:15:02.170 align:start position:0% want more features and along the way how much<00:15:00.380> I<00:15:00.740> can<00:15:00.950> keep<00:15:01.190> this<00:15:01.399> kind<00:15:01.579> of<00:15:01.730> discipline 00:15:02.170 --> 00:15:02.180 align:start position:0% much I can keep this kind of discipline 00:15:02.180 --> 00:15:07.769 align:start position:0% much I can keep this kind of discipline that<00:15:02.450> there<00:15:03.440> we<00:15:03.680> are<00:15:03.709> a<00:15:03.829> challenge<00:15:05.440> but<00:15:06.440> I 00:15:07.769 --> 00:15:07.779 align:start position:0% that there we are a challenge but I 00:15:07.779 --> 00:15:13.600 align:start position:0% that there we are a challenge but I needed<00:15:08.779> to<00:15:09.399> write<00:15:10.399> something<00:15:10.730> useful<00:15:11.600> so<00:15:12.610> I'm 00:15:13.600 --> 00:15:13.610 align:start position:0% needed to write something useful so I'm 00:15:13.610 --> 00:15:15.340 align:start position:0% needed to write something useful so I'm already<00:15:13.850> adding<00:15:14.329> some<00:15:14.570> features<00:15:14.750> I<00:15:15.170> don't 00:15:15.340 --> 00:15:15.350 align:start position:0% already adding some features I don't 00:15:15.350 --> 00:15:18.190 align:start position:0% already adding some features I don't like<00:15:15.529> that<00:15:15.770> I<00:15:16.040> don't<00:15:16.820> I<00:15:17.240> I<00:15:17.450> generally<00:15:18.050> don't 00:15:18.190 --> 00:15:18.200 align:start position:0% like that I don't I I generally don't 00:15:18.200 --> 00:15:21.010 align:start position:0% like that I don't I I generally don't like<00:15:18.350> to<00:15:18.620> add<00:15:19.070> stuff<00:15:19.459> to<00:15:19.520> this<00:15:19.820> world<00:15:20.120> which<00:15:20.810> is 00:15:21.010 --> 00:15:21.020 align:start position:0% like to add stuff to this world which is 00:15:21.020 --> 00:15:26.199 align:start position:0% like to add stuff to this world which is already<00:15:21.320> a<00:15:21.410> mess<00:15:21.970> but<00:15:23.170> I<00:15:24.970> wanted<00:15:25.970> other 00:15:26.199 --> 00:15:26.209 align:start position:0% already a mess but I wanted other 00:15:26.209 --> 00:15:28.540 align:start position:0% already a mess but I wanted other features<00:15:26.720> so<00:15:26.990> sometimes<00:15:27.649> I<00:15:27.829> wanted<00:15:28.130> to<00:15:28.279> call 00:15:28.540 --> 00:15:28.550 align:start position:0% features so sometimes I wanted to call 00:15:28.550 --> 00:15:32.130 align:start position:0% features so sometimes I wanted to call other<00:15:29.140> addresses 00:15:32.130 --> 00:15:32.140 align:start position:0% other addresses 00:15:32.140 --> 00:15:34.950 align:start position:0% other addresses but<00:15:32.530> I<00:15:32.560> didn't<00:15:32.980> want<00:15:33.280> three<00:15:33.520> entrance<00:15:33.970> so 00:15:34.950 --> 00:15:34.960 align:start position:0% but I didn't want three entrance so 00:15:34.960 --> 00:15:37.550 align:start position:0% but I didn't want three entrance so currently<00:15:35.440> whenever<00:15:35.860> you<00:15:36.100> call<00:15:36.370> something 00:15:37.550 --> 00:15:37.560 align:start position:0% currently whenever you call something 00:15:37.560 --> 00:15:40.200 align:start position:0% currently whenever you call something you<00:15:38.560> have<00:15:38.710> to<00:15:38.740> specify<00:15:39.100> what<00:15:39.490> happens<00:15:39.850> in<00:15:39.970> the 00:15:40.200 --> 00:15:40.210 align:start position:0% you have to specify what happens in the 00:15:40.210 --> 00:15:43.790 align:start position:0% you have to specify what happens in the entrance<00:15:40.950> in<00:15:41.950> case<00:15:42.190> of<00:15:42.310> the<00:15:42.460> entrance<00:15:42.820> and 00:15:43.790 --> 00:15:43.800 align:start position:0% entrance in case of the entrance and 00:15:43.800 --> 00:15:48.110 align:start position:0% entrance in case of the entrance and currently<00:15:44.800> only<00:15:44.950> abort<00:15:45.400> is<00:15:45.580> supported<00:15:46.210> so 00:15:48.110 --> 00:15:48.120 align:start position:0% currently only abort is supported so 00:15:48.120 --> 00:15:51.420 align:start position:0% currently only abort is supported so whenever<00:15:49.170> when<00:15:50.170> whenever<00:15:50.740> your<00:15:51.010> contract 00:15:51.420 --> 00:15:51.430 align:start position:0% whenever when whenever your contract 00:15:51.430 --> 00:15:53.700 align:start position:0% whenever when whenever your contract causes<00:15:51.820> something<00:15:51.970> and<00:15:52.330> that<00:15:53.140> thing<00:15:53.200> calls 00:15:53.700 --> 00:15:53.710 align:start position:0% causes something and that thing calls 00:15:53.710 --> 00:15:58.470 align:start position:0% causes something and that thing calls back<00:15:53.950> that<00:15:54.880> about<00:15:57.030> eventually<00:15:58.030> I<00:15:58.060> want<00:15:58.390> to 00:15:58.470 --> 00:15:58.480 align:start position:0% back that about eventually I want to 00:15:58.480 --> 00:16:03.840 align:start position:0% back that about eventually I want to write<00:15:58.690> something<00:15:58.720> else<00:15:59.200> here<00:15:59.470> but<00:16:02.640> you<00:16:03.640> can 00:16:03.840 --> 00:16:03.850 align:start position:0% write something else here but you can 00:16:03.850 --> 00:16:09.240 align:start position:0% write something else here but you can create<00:16:04.090> a<00:16:04.210> contract<00:16:07.620> that's<00:16:08.620> a<00:16:08.830> deliberate 00:16:09.240 --> 00:16:09.250 align:start position:0% create a contract that's a deliberate 00:16:09.250 --> 00:16:18.900 align:start position:0% create a contract that's a deliberate choice<00:16:09.750> because<00:16:10.750> I<00:16:15.270> contract<00:16:16.270> simple<00:16:17.340> so<00:16:18.340> I 00:16:18.900 --> 00:16:18.910 align:start position:0% choice because I contract simple so I 00:16:18.910 --> 00:16:26.400 align:start position:0% choice because I contract simple so I think<00:16:21.390> I<00:16:22.390> added<00:16:23.260> there<00:16:23.590> is<00:16:23.800> I<00:16:25.260> want<00:16:26.260> you<00:16:26.320> to 00:16:26.400 --> 00:16:26.410 align:start position:0% think I added there is I want you to 00:16:26.410 --> 00:16:32.760 align:start position:0% think I added there is I want you to implement<00:16:26.920> the<00:16:27.220> ERC<00:16:27.490> 20<00:16:28.030> and<00:16:28.350> it's<00:16:29.350> kind<00:16:29.680> of<00:16:31.770> it 00:16:32.760 --> 00:16:32.770 align:start position:0% implement the ERC 20 and it's kind of it 00:16:32.770 --> 00:16:35.180 align:start position:0% implement the ERC 20 and it's kind of it seemed<00:16:33.430> to<00:16:33.550> necessary<00:16:33.970> to<00:16:34.210> add<00:16:34.300> some<00:16:34.600> kinds<00:16:34.990> of 00:16:35.180 --> 00:16:35.190 align:start position:0% seemed to necessary to add some kinds of 00:16:35.190 --> 00:16:38.460 align:start position:0% seemed to necessary to add some kinds of arrays<00:16:36.190> I<00:16:36.520> didn't<00:16:37.000> like<00:16:37.210> that<00:16:37.240> because<00:16:37.960> here 00:16:38.460 --> 00:16:38.470 align:start position:0% arrays I didn't like that because here 00:16:38.470 --> 00:16:41.850 align:start position:0% arrays I didn't like that because here you<00:16:38.710> have<00:16:38.740> an<00:16:39.310> assignment<00:16:40.170> you<00:16:41.170> can<00:16:41.410> modify<00:16:41.710> a 00:16:41.850 --> 00:16:41.860 align:start position:0% you have an assignment you can modify a 00:16:41.860 --> 00:16:45.720 align:start position:0% you have an assignment you can modify a particular<00:16:42.130> storage<00:16:43.380> location<00:16:44.380> here<00:16:44.740> I<00:16:45.070> don't 00:16:45.720 --> 00:16:45.730 align:start position:0% particular storage location here I don't 00:16:45.730 --> 00:16:47.000 align:start position:0% particular storage location here I don't like<00:16:45.970> this<00:16:46.150> at<00:16:46.390> all 00:16:47.000 --> 00:16:47.010 align:start position:0% like this at all 00:16:47.010 --> 00:16:51.420 align:start position:0% like this at all when<00:16:48.010> you<00:16:48.160> don't<00:16:48.370> have<00:16:48.430> a<00:16:48.580> race<00:16:49.500> bamboo<00:16:50.500> has<00:16:50.950> no 00:16:51.420 --> 00:16:51.430 align:start position:0% when you don't have a race bamboo has no 00:16:51.430 --> 00:16:54.510 align:start position:0% when you don't have a race bamboo has no assignment<00:16:52.360> at<00:16:52.570> all<00:16:52.930> because<00:16:53.770> I<00:16:54.190> mean 00:16:54.510 --> 00:16:54.520 align:start position:0% assignment at all because I mean 00:16:54.520 --> 00:16:57.470 align:start position:0% assignment at all because I mean everything<00:16:54.970> in<00:16:55.089> the<00:16:55.120> storage<00:16:55.530> just<00:16:56.530> appear 00:16:57.470 --> 00:16:57.480 align:start position:0% everything in the storage just appear 00:16:57.480 --> 00:17:02.120 align:start position:0% everything in the storage just appear appears<00:16:58.480> in<00:16:58.720> this<00:16:59.050> becomes<00:16:59.620> phrase<00:17:00.930> here<00:17:01.930> I'm 00:17:02.120 --> 00:17:02.130 align:start position:0% appears in this becomes phrase here I'm 00:17:02.130 --> 00:17:04.380 align:start position:0% appears in this becomes phrase here I'm introducing<00:17:03.130> side-effects<00:17:03.730> I<00:17:03.880> don't<00:17:04.060> like<00:17:04.240> it 00:17:04.380 --> 00:17:04.390 align:start position:0% introducing side-effects I don't like it 00:17:04.390 --> 00:17:07.290 align:start position:0% introducing side-effects I don't like it at<00:17:04.569> all<00:17:04.600> but<00:17:05.020> ok<00:17:05.740> where<00:17:05.920> people<00:17:06.459> want<00:17:06.670> to<00:17:07.270> use 00:17:07.290 --> 00:17:07.300 align:start position:0% at all but ok where people want to use 00:17:07.300 --> 00:17:11.280 align:start position:0% at all but ok where people want to use tokens<00:17:07.810> and<00:17:08.260> the<00:17:08.410> tokens<00:17:08.890> kind<00:17:09.670> of<00:17:10.290> essential 00:17:11.280 --> 00:17:11.290 align:start position:0% tokens and the tokens kind of essential 00:17:11.290 --> 00:17:14.189 align:start position:0% tokens and the tokens kind of essential feature<00:17:11.560> to<00:17:11.890> control<00:17:12.360> implement<00:17:13.360> ripped 00:17:14.189 --> 00:17:14.199 align:start position:0% feature to control implement ripped 00:17:14.199 --> 00:17:21.929 align:start position:0% feature to control implement ripped economic<00:17:16.770> mechanisms<00:17:17.770> so<00:17:19.890> I'm<00:17:20.890> not<00:17:21.189> quite 00:17:21.929 --> 00:17:21.939 align:start position:0% economic mechanisms so I'm not quite 00:17:21.939 --> 00:17:24.059 align:start position:0% economic mechanisms so I'm not quite happy<00:17:22.060> I'm<00:17:22.689> not<00:17:22.959> completely<00:17:23.350> happy<00:17:23.680> about 00:17:24.059 --> 00:17:24.069 align:start position:0% happy I'm not completely happy about 00:17:24.069 --> 00:17:29.210 align:start position:0% happy I'm not completely happy about adding<00:17:24.430> this<00:17:24.610> but<00:17:25.089> I<00:17:25.390> did<00:17:26.579> what's<00:17:27.579> missing 00:17:29.210 --> 00:17:29.220 align:start position:0% adding this but I did what's missing 00:17:29.220 --> 00:17:32.310 align:start position:0% adding this but I did what's missing language<00:17:30.220> specification<00:17:31.120> and<00:17:31.320> independently 00:17:32.310 --> 00:17:32.320 align:start position:0% language specification and independently 00:17:32.320 --> 00:17:35.310 align:start position:0% language specification and independently interpreter<00:17:32.980> these<00:17:33.730> come<00:17:34.150> first<00:17:34.510> because 00:17:35.310 --> 00:17:35.320 align:start position:0% interpreter these come first because 00:17:35.320 --> 00:17:36.960 align:start position:0% interpreter these come first because whenever<00:17:35.830> I<00:17:35.980> have<00:17:36.160> a<00:17:36.190> chance<00:17:36.490> I<00:17:36.670> keep 00:17:36.960 --> 00:17:36.970 align:start position:0% whenever I have a chance I keep 00:17:36.970 --> 00:17:39.540 align:start position:0% whenever I have a chance I keep complaining<00:17:37.450> that<00:17:37.720> solidity<00:17:38.560> program<00:17:39.100> has<00:17:39.310> no 00:17:39.540 --> 00:17:39.550 align:start position:0% complaining that solidity program has no 00:17:39.550 --> 00:17:43.410 align:start position:0% complaining that solidity program has no meaning<00:17:40.030> until<00:17:40.840> it's<00:17:41.080> compiled<00:17:41.560> into<00:17:42.420> EVM 00:17:43.410 --> 00:17:43.420 align:start position:0% meaning until it's compiled into EVM 00:17:43.420 --> 00:17:44.750 align:start position:0% meaning until it's compiled into EVM bytecode 00:17:44.750 --> 00:17:44.760 align:start position:0% bytecode 00:17:44.760 --> 00:17:47.480 align:start position:0% bytecode I<00:17:44.820> really<00:17:45.120> have<00:17:45.300> no<00:17:45.510> specification<00:17:46.280> you<00:17:47.280> know 00:17:47.480 --> 00:17:47.490 align:start position:0% I really have no specification you know 00:17:47.490 --> 00:17:50.720 align:start position:0% I really have no specification you know the<00:17:48.300> okay<00:17:48.720> does<00:17:48.930> the<00:17:49.050> documentation<00:17:49.710> but<00:17:49.740> it 00:17:50.720 --> 00:17:50.730 align:start position:0% the okay does the documentation but it 00:17:50.730 --> 00:17:52.220 align:start position:0% the okay does the documentation but it doesn't<00:17:51.030> tell<00:17:51.210> you<00:17:51.300> if<00:17:51.480> your<00:17:51.630> program<00:17:52.020> is 00:17:52.220 --> 00:17:52.230 align:start position:0% doesn't tell you if your program is 00:17:52.230 --> 00:17:56.230 align:start position:0% doesn't tell you if your program is executed<00:17:53.160> from<00:17:53.280> from<00:17:54.020> top-down<00:17:55.020> or<00:17:55.350> bottom-up 00:17:56.230 --> 00:17:56.240 align:start position:0% executed from from top-down or bottom-up 00:17:56.240 --> 00:17:59.120 align:start position:0% executed from from top-down or bottom-up if<00:17:57.240> you<00:17:57.420> believe<00:17:57.690> it's<00:17:57.840> executed<00:17:58.740> from<00:17:58.890> top 00:17:59.120 --> 00:17:59.130 align:start position:0% if you believe it's executed from top 00:17:59.130 --> 00:18:02.320 align:start position:0% if you believe it's executed from top down<00:17:59.180> you're<00:18:00.180> just<00:18:00.510> you<00:18:01.050> know<00:18:01.080> imagining<00:18:02.070> that 00:18:02.320 --> 00:18:02.330 align:start position:0% down you're just you know imagining that 00:18:02.330 --> 00:18:05.450 align:start position:0% down you're just you know imagining that and<00:18:03.330> you<00:18:03.630> don't<00:18:03.720> know<00:18:03.960> what<00:18:04.560> how<00:18:05.010> many<00:18:05.220> other 00:18:05.450 --> 00:18:05.460 align:start position:0% and you don't know what how many other 00:18:05.460 --> 00:18:08.690 align:start position:0% and you don't know what how many other things<00:18:05.730> you<00:18:06.030> just<00:18:06.120> assuming<00:18:06.780> so<00:18:07.500> I<00:18:07.740> I<00:18:07.830> say<00:18:08.520> this 00:18:08.690 --> 00:18:08.700 align:start position:0% things you just assuming so I I say this 00:18:08.700 --> 00:18:11.510 align:start position:0% things you just assuming so I I say this always<00:18:09.330> and<00:18:09.630> this<00:18:09.900> applies<00:18:10.470> to<00:18:10.830> the<00:18:10.890> bamboo<00:18:11.340> as 00:18:11.510 --> 00:18:11.520 align:start position:0% always and this applies to the bamboo as 00:18:11.520 --> 00:18:14.240 align:start position:0% always and this applies to the bamboo as well<00:18:11.760> currently<00:18:12.090> I'm<00:18:12.960> not<00:18:13.170> happy<00:18:13.380> so<00:18:13.830> I<00:18:13.860> want 00:18:14.240 --> 00:18:14.250 align:start position:0% well currently I'm not happy so I want 00:18:14.250 --> 00:18:17.810 align:start position:0% well currently I'm not happy so I want I'm<00:18:15.000> writing<00:18:15.710> specification<00:18:16.710> and<00:18:16.920> also<00:18:17.670> an 00:18:17.810 --> 00:18:17.820 align:start position:0% I'm writing specification and also an 00:18:17.820 --> 00:18:20.900 align:start position:0% I'm writing specification and also an independent<00:18:18.090> interpreter<00:18:18.960> I<00:18:19.550> know<00:18:20.550> this<00:18:20.760> man 00:18:20.900 --> 00:18:20.910 align:start position:0% independent interpreter I know this man 00:18:20.910 --> 00:18:22.760 align:start position:0% independent interpreter I know this man is<00:18:21.120> not<00:18:21.300> in<00:18:21.750> progress<00:18:22.290> language 00:18:22.760 --> 00:18:22.770 align:start position:0% is not in progress language 00:18:22.770 --> 00:18:25.550 align:start position:0% is not in progress language specification<00:18:23.490> is<00:18:23.640> in<00:18:23.850> progress<00:18:24.360> but<00:18:25.050> okay 00:18:25.550 --> 00:18:25.560 align:start position:0% specification is in progress but okay 00:18:25.560 --> 00:18:29.180 align:start position:0% specification is in progress but okay well<00:18:25.740> if<00:18:25.860> I<00:18:26.100> done<00:18:26.610> the<00:18:27.330> K<00:18:27.570> framework<00:18:28.110> I<00:18:28.290> can<00:18:28.620> do 00:18:29.180 --> 00:18:29.190 align:start position:0% well if I done the K framework I can do 00:18:29.190 --> 00:18:32.450 align:start position:0% well if I done the K framework I can do this<00:18:29.840> at<00:18:30.840> the<00:18:30.960> same<00:18:31.140> time<00:18:31.380> so<00:18:31.770> maybe<00:18:32.040> I<00:18:32.190> should 00:18:32.450 --> 00:18:32.460 align:start position:0% this at the same time so maybe I should 00:18:32.460 --> 00:18:35.210 align:start position:0% this at the same time so maybe I should just<00:18:32.700> talk<00:18:32.970> to<00:18:33.030> these<00:18:33.570> guys 00:18:35.210 --> 00:18:35.220 align:start position:0% just talk to these guys 00:18:35.220 --> 00:18:43.220 align:start position:0% just talk to these guys I<00:18:36.470> don't<00:18:37.470> want<00:18:37.860> to<00:18:38.070> add<00:18:38.310> many<00:18:39.120> features<00:18:42.170> may<00:18:43.170> be 00:18:43.220 --> 00:18:43.230 align:start position:0% I don't want to add many features may be 00:18:43.230 --> 00:18:47.810 align:start position:0% I don't want to add many features may be the<00:18:43.550> most<00:18:44.550> prior<00:18:45.000> one<00:18:45.420> is<00:18:45.750> coring<00:18:46.820> externally 00:18:47.810 --> 00:18:47.820 align:start position:0% the most prior one is coring externally 00:18:47.820 --> 00:18:49.850 align:start position:0% the most prior one is coring externally defined<00:18:48.000> the<00:18:48.270> contracts<00:18:48.870> once<00:18:49.170> this<00:18:49.440> is<00:18:49.650> done 00:18:49.850 --> 00:18:49.860 align:start position:0% defined the contracts once this is done 00:18:49.860 --> 00:18:54.980 align:start position:0% defined the contracts once this is done the<00:18:50.570> language<00:18:51.570> is<00:18:51.780> kind<00:18:52.110> of<00:18:52.260> usable<00:18:52.890> so<00:18:53.990> maybe 00:18:54.980 --> 00:18:54.990 align:start position:0% the language is kind of usable so maybe 00:18:54.990 --> 00:18:57.680 align:start position:0% the language is kind of usable so maybe I<00:18:55.110> should<00:18:55.350> have<00:18:55.440> delayed<00:18:55.710> this<00:18:56.240> until<00:18:57.240> the 00:18:57.680 --> 00:18:57.690 align:start position:0% I should have delayed this until the 00:18:57.690 --> 00:19:01.490 align:start position:0% I should have delayed this until the other<00:18:57.840> parts<00:18:58.200> were<00:18:58.290> done<00:18:58.550> so<00:19:00.350> here's<00:19:01.350> the 00:19:01.490 --> 00:19:01.500 align:start position:0% other parts were done so here's the 00:19:01.500 --> 00:19:03.710 align:start position:0% other parts were done so here's the famous<00:19:01.830> phrase<00:19:02.130> by<00:19:02.370> Simon<00:19:02.790> Payton<00:19:03.120> just<00:19:03.360> avoid 00:19:03.710 --> 00:19:03.720 align:start position:0% famous phrase by Simon Payton just avoid 00:19:03.720 --> 00:19:05.060 align:start position:0% famous phrase by Simon Payton just avoid a<00:19:03.810> success<00:19:04.170> at<00:19:04.320> all<00:19:04.440> costs 00:19:05.060 --> 00:19:05.070 align:start position:0% a success at all costs 00:19:05.070 --> 00:19:07.130 align:start position:0% a success at all costs yes<00:19:05.370> I<00:19:05.520> stole<00:19:06.030> this<00:19:06.210> race<00:19:06.510> from<00:19:06.720> the<00:19:06.810> Husker 00:19:07.130 --> 00:19:07.140 align:start position:0% yes I stole this race from the Husker 00:19:07.140 --> 00:19:11.870 align:start position:0% yes I stole this race from the Husker community<00:19:09.860> but<00:19:10.860> this<00:19:11.010> is<00:19:11.190> kind<00:19:11.460> of<00:19:11.580> ambiguous 00:19:11.870 --> 00:19:11.880 align:start position:0% community but this is kind of ambiguous 00:19:11.880 --> 00:19:15.020 align:start position:0% community but this is kind of ambiguous success<00:19:12.840> at<00:19:13.020> all<00:19:13.140> costs<00:19:13.650> avoid<00:19:14.010> at<00:19:14.430> all<00:19:14.580> cost 00:19:15.020 --> 00:19:15.030 align:start position:0% success at all costs avoid at all cost 00:19:15.030 --> 00:19:19.970 align:start position:0% success at all costs avoid at all cost I<00:19:15.600> haven't<00:19:16.290> decided<00:19:16.590> yet<00:19:18.530> here's<00:19:19.530> how<00:19:19.680> you<00:19:19.740> can 00:19:19.970 --> 00:19:19.980 align:start position:0% I haven't decided yet here's how you can 00:19:19.980 --> 00:19:21.980 align:start position:0% I haven't decided yet here's how you can help<00:19:20.160> like<00:19:21.000> you<00:19:21.180> right<00:19:21.390> okay 00:19:21.980 --> 00:19:21.990 align:start position:0% help like you right okay 00:19:21.990 --> 00:19:27.920 align:start position:0% help like you right okay please<00:19:22.230> talk<00:19:22.410> to<00:19:22.470> me<00:19:22.980> thank<00:19:23.370> you<00:19:23.460> very<00:19:23.490> much 00:19:27.920 --> 00:19:27.930 align:start position:0% 00:19:27.930 --> 00:19:35.410 align:start position:0% [Music]