WEBVTT Kind: captions Language: en 00:00:01.070 --> 00:00:11.980 align:start position:0% [Applause] 00:00:11.980 --> 00:00:11.990 align:start position:0% 00:00:11.990 --> 00:00:15.980 align:start position:0% as<00:00:12.990> everyone<00:00:13.320> for<00:00:13.650> coming<00:00:14.580> who<00:00:15.480> have<00:00:15.690> now<00:00:15.960> a 00:00:15.980 --> 00:00:15.990 align:start position:0% as everyone for coming who have now a 00:00:15.990 --> 00:00:18.380 align:start position:0% as everyone for coming who have now a workshop<00:00:16.800> on<00:00:16.950> the<00:00:17.220> form<00:00:17.640> of<00:00:17.790> replication<00:00:18.300> of 00:00:18.380 --> 00:00:18.390 align:start position:0% workshop on the form of replication of 00:00:18.390 --> 00:00:21.230 align:start position:0% workshop on the form of replication of smart<00:00:18.660> contracts<00:00:19.140> and<00:00:19.500> maybe<00:00:20.490> before<00:00:21.000> even 00:00:21.230 --> 00:00:21.240 align:start position:0% smart contracts and maybe before even 00:00:21.240 --> 00:00:23.030 align:start position:0% smart contracts and maybe before even typical<00:00:21.720> of<00:00:21.810> topic<00:00:22.050> so<00:00:22.170> how<00:00:22.380> many<00:00:22.439> people<00:00:22.920> have 00:00:23.030 --> 00:00:23.040 align:start position:0% typical of topic so how many people have 00:00:23.040 --> 00:00:25.970 align:start position:0% typical of topic so how many people have done<00:00:23.970> any<00:00:24.330> for<00:00:24.570> modification<00:00:25.259> of<00:00:25.320> contract<00:00:25.800> so 00:00:25.970 --> 00:00:25.980 align:start position:0% done any for modification of contract so 00:00:25.980 --> 00:00:30.050 align:start position:0% done any for modification of contract so far<00:00:26.279> maybe<00:00:27.270> this<00:00:27.419> raise<00:00:27.869> the<00:00:28.050> hands<00:00:28.700> so<00:00:29.700> very 00:00:30.050 --> 00:00:30.060 align:start position:0% far maybe this raise the hands so very 00:00:30.060 --> 00:00:32.359 align:start position:0% far maybe this raise the hands so very few<00:00:30.270> so<00:00:30.540> I<00:00:30.599> guess<00:00:30.779> all<00:00:31.529> the<00:00:31.770> remaining<00:00:32.189> ones 00:00:32.359 --> 00:00:32.369 align:start position:0% few so I guess all the remaining ones 00:00:32.369 --> 00:00:34.340 align:start position:0% few so I guess all the remaining ones will<00:00:32.579> attract<00:00:32.850> it<00:00:32.880> by<00:00:33.120> the<00:00:33.180> last<00:00:33.450> part<00:00:33.720> that's 00:00:34.340 --> 00:00:34.350 align:start position:0% will attract it by the last part that's 00:00:34.350 --> 00:00:37.010 align:start position:0% will attract it by the last part that's supposed<00:00:34.680> to<00:00:34.739> be<00:00:34.829> easy<00:00:35.070> and<00:00:35.850> hopefully<00:00:36.810> by<00:00:36.960> the 00:00:37.010 --> 00:00:37.020 align:start position:0% supposed to be easy and hopefully by the 00:00:37.020 --> 00:00:38.720 align:start position:0% supposed to be easy and hopefully by the end<00:00:37.230> of<00:00:37.410> this<00:00:37.500> workshop<00:00:37.860> everybody<00:00:38.310> manages 00:00:38.720 --> 00:00:38.730 align:start position:0% end of this workshop everybody manages 00:00:38.730 --> 00:00:41.210 align:start position:0% end of this workshop everybody manages to<00:00:38.910> have<00:00:39.720> a<00:00:39.750> hands-on<00:00:40.079> depends<00:00:40.620> on<00:00:40.710> exercise 00:00:41.210 --> 00:00:41.220 align:start position:0% to have a hands-on depends on exercise 00:00:41.220 --> 00:00:42.550 align:start position:0% to have a hands-on depends on exercise and<00:00:41.490> everybody<00:00:41.790> should<00:00:41.880> be<00:00:42.030> able<00:00:42.120> to<00:00:42.240> verify 00:00:42.550 --> 00:00:42.560 align:start position:0% and everybody should be able to verify 00:00:42.560 --> 00:00:46.400 align:start position:0% and everybody should be able to verify some<00:00:43.560> form<00:00:43.800> of<00:00:43.890> properties<00:00:44.370> on<00:00:44.580> contracts<00:00:45.410> so 00:00:46.400 --> 00:00:46.410 align:start position:0% some form of properties on contracts so 00:00:46.410 --> 00:00:48.020 align:start position:0% some form of properties on contracts so the<00:00:46.530> people<00:00:46.680> who<00:00:46.950> peed<00:00:47.100> in<00:00:47.220> the<00:00:47.370> workshop<00:00:47.760> we 00:00:48.020 --> 00:00:48.030 align:start position:0% the people who peed in the workshop we 00:00:48.030 --> 00:00:52.190 align:start position:0% the people who peed in the workshop we have<00:00:48.440> Demeter<00:00:49.440> there<00:00:49.890> his<00:00:50.900> previous<00:00:51.900> student 00:00:52.190 --> 00:00:52.200 align:start position:0% have Demeter there his previous student 00:00:52.200 --> 00:00:53.900 align:start position:0% have Demeter there his previous student it<00:00:52.320> is<00:00:52.350> during<00:00:52.830> a<00:00:52.950> joining<00:00:53.250> chain<00:00:53.520> security 00:00:53.900 --> 00:00:53.910 align:start position:0% it is during a joining chain security 00:00:53.910 --> 00:00:56.330 align:start position:0% it is during a joining chain security now<00:00:54.150> parents<00:00:55.110> demand<00:00:55.380> for<00:00:55.530> modification<00:00:56.220> and 00:00:56.330 --> 00:00:56.340 align:start position:0% now parents demand for modification and 00:00:56.340 --> 00:00:58.190 align:start position:0% now parents demand for modification and problem<00:00:56.670> analysis<00:00:57.090> then<00:00:57.810> we<00:00:57.930> have<00:00:58.050> also 00:00:58.190 --> 00:00:58.200 align:start position:0% problem analysis then we have also 00:00:58.200 --> 00:01:00.890 align:start position:0% problem analysis then we have also hunter<00:00:58.620> permanent<00:00:59.150> so<00:01:00.150> he<00:01:00.330> is<00:01:00.390> the<00:01:00.570> lead 00:01:00.890 --> 00:01:00.900 align:start position:0% hunter permanent so he is the lead 00:01:00.900 --> 00:01:02.900 align:start position:0% hunter permanent so he is the lead developer<00:01:01.500> of<00:01:01.650> the<00:01:01.830> very<00:01:02.130> far<00:01:02.370> we'll<00:01:02.670> be<00:01:02.790> using 00:01:02.900 --> 00:01:02.910 align:start position:0% developer of the very far we'll be using 00:01:02.910 --> 00:01:05.630 align:start position:0% developer of the very far we'll be using today<00:01:03.270> in<00:01:03.480> the<00:01:03.600> workshop<00:01:03.990> and<00:01:04.680> also<00:01:05.339> who<00:01:05.519> were 00:01:05.630 --> 00:01:05.640 align:start position:0% today in the workshop and also who were 00:01:05.640 --> 00:01:07.550 align:start position:0% today in the workshop and also who were visiting<00:01:05.880> back<00:01:06.299> there<00:01:06.509> city<00:01:07.049> of<00:01:07.259> chain 00:01:07.550 --> 00:01:07.560 align:start position:0% visiting back there city of chain 00:01:07.560 --> 00:01:12.380 align:start position:0% visiting back there city of chain security<00:01:07.920> and<00:01:08.329> myself<00:01:09.329> as<00:01:09.689> well<00:01:11.060> so<00:01:12.060> who<00:01:12.270> we 00:01:12.380 --> 00:01:12.390 align:start position:0% security and myself as well so who we 00:01:12.390 --> 00:01:14.990 align:start position:0% security and myself as well so who we are<00:01:12.570> we<00:01:12.930> are<00:01:12.960> a<00:01:13.140> chain<00:01:13.470> security<00:01:13.860> we<00:01:14.820> are<00:01:14.940> a 00:01:14.990 --> 00:01:15.000 align:start position:0% are we are a chain security we are a 00:01:15.000 --> 00:01:17.390 align:start position:0% are we are a chain security we are a spinoff<00:01:15.480> from<00:01:15.600> ETH<00:01:16.290> Zurich<00:01:16.680> ETH<00:01:17.159> the 00:01:17.390 --> 00:01:17.400 align:start position:0% spinoff from ETH Zurich ETH the 00:01:17.400 --> 00:01:19.880 align:start position:0% spinoff from ETH Zurich ETH the University<00:01:18.030> not<00:01:18.150> the<00:01:18.270> foundation<00:01:18.810> based<00:01:19.710> in 00:01:19.880 --> 00:01:19.890 align:start position:0% University not the foundation based in 00:01:19.890 --> 00:01:23.210 align:start position:0% University not the foundation based in Zurich<00:01:20.610> Switzerland<00:01:20.840> and<00:01:21.840> we<00:01:22.620> focus<00:01:22.950> on<00:01:23.040> the 00:01:23.210 --> 00:01:23.220 align:start position:0% Zurich Switzerland and we focus on the 00:01:23.220 --> 00:01:25.160 align:start position:0% Zurich Switzerland and we focus on the objects<00:01:23.670> activity<00:01:24.120> we<00:01:24.600> have<00:01:24.780> worked<00:01:25.080> with 00:01:25.160 --> 00:01:25.170 align:start position:0% objects activity we have worked with 00:01:25.170 --> 00:01:27.649 align:start position:0% objects activity we have worked with many<00:01:25.550> blockchain<00:01:26.550> projects<00:01:26.970> so<00:01:27.060> far<00:01:27.090> we<00:01:27.510> can 00:01:27.649 --> 00:01:27.659 align:start position:0% many blockchain projects so far we can 00:01:27.659 --> 00:01:30.649 align:start position:0% many blockchain projects so far we can them<00:01:27.780> over<00:01:28.080> 80<00:01:28.350> audits<00:01:29.120> not<00:01:30.120> only<00:01:30.390> smart 00:01:30.649 --> 00:01:30.659 align:start position:0% them over 80 audits not only smart 00:01:30.659 --> 00:01:32.330 align:start position:0% them over 80 audits not only smart contract<00:01:31.050> always<00:01:31.350> but<00:01:31.560> also<00:01:31.680> product<00:01:32.130> of<00:01:32.220> all 00:01:32.330 --> 00:01:32.340 align:start position:0% contract always but also product of all 00:01:32.340 --> 00:01:35.840 align:start position:0% contract always but also product of all its<00:01:32.550> platform<00:01:33.090> on<00:01:33.240> itself<00:01:33.630> as<00:01:34.050> far<00:01:34.710> as<00:01:34.830> a<00:01:35.430> cup 00:01:35.840 --> 00:01:35.850 align:start position:0% its platform on itself as far as a cup 00:01:35.850 --> 00:01:38.780 align:start position:0% its platform on itself as far as a cup of<00:01:36.000> very<00:01:36.600> visible<00:01:37.020> ie<00:01:37.650> IDs<00:01:38.159> I<00:01:38.370> think<00:01:38.610> many 00:01:38.780 --> 00:01:38.790 align:start position:0% of very visible ie IDs I think many 00:01:38.790 --> 00:01:41.210 align:start position:0% of very visible ie IDs I think many people<00:01:38.940> are<00:01:39.229> recognized<00:01:40.229> the<00:01:40.590> chain<00:01:40.799> security 00:01:41.210 --> 00:01:41.220 align:start position:0% people are recognized the chain security 00:01:41.220 --> 00:01:43.430 align:start position:0% people are recognized the chain security name<00:01:41.460> from<00:01:41.820> you<00:01:42.690> know<00:01:42.810> some<00:01:43.200> of<00:01:43.229> those 00:01:43.430 --> 00:01:43.440 align:start position:0% name from you know some of those 00:01:43.440 --> 00:01:45.050 align:start position:0% name from you know some of those earpieces<00:01:44.010> we<00:01:44.220> have<00:01:44.340> reviewed<00:01:44.640> in<00:01:44.760> the<00:01:44.850> past 00:01:45.050 --> 00:01:45.060 align:start position:0% earpieces we have reviewed in the past 00:01:45.060 --> 00:01:48.920 align:start position:0% earpieces we have reviewed in the past and<00:01:46.310> so<00:01:47.310> yeah<00:01:47.549> we<00:01:47.729> also<00:01:47.850> have<00:01:48.150> quite<00:01:48.720> a<00:01:48.810> few 00:01:48.920 --> 00:01:48.930 align:start position:0% and so yeah we also have quite a few 00:01:48.930 --> 00:01:50.930 align:start position:0% and so yeah we also have quite a few already<00:01:49.260> security<00:01:49.830> products<00:01:50.190> with<00:01:50.310> platforms 00:01:50.930 --> 00:01:50.940 align:start position:0% already security products with platforms 00:01:50.940 --> 00:01:52.820 align:start position:0% already security products with platforms at<00:01:51.120> the<00:01:51.150> CTO<00:01:51.510> Foundation<00:01:52.140> polkadots 00:01:52.820 --> 00:01:52.830 align:start position:0% at the CTO Foundation polkadots 00:01:52.830 --> 00:01:55.250 align:start position:0% at the CTO Foundation polkadots silica<00:01:53.640> and<00:01:53.760> fewer<00:01:53.940> than<00:01:54.000> some<00:01:54.330> chains<00:01:54.570> where 00:01:55.250 --> 00:01:55.260 align:start position:0% silica and fewer than some chains where 00:01:55.260 --> 00:01:58.670 align:start position:0% silica and fewer than some chains where we<00:01:55.440> focus<00:01:55.740> on<00:01:55.860> building<00:01:56.070> security<00:01:56.549> tools<00:01:57.680> you 00:01:58.670 --> 00:01:58.680 align:start position:0% we focus on building security tools you 00:01:58.680 --> 00:02:00.410 align:start position:0% we focus on building security tools you know<00:01:58.770> tools<00:01:59.010> for<00:01:59.159> finding<00:01:59.340> boxes<00:01:59.880> no<00:02:00.000> enfant 00:02:00.410 --> 00:02:00.420 align:start position:0% know tools for finding boxes no enfant 00:02:00.420 --> 00:02:03.200 align:start position:0% know tools for finding boxes no enfant as<00:02:00.600> far<00:02:00.840> as<00:02:00.960> for<00:02:01.350> modification<00:02:02.010> tools<00:02:02.250> for<00:02:02.520> for 00:02:03.200 --> 00:02:03.210 align:start position:0% as far as for modification tools for for 00:02:03.210 --> 00:02:07.100 align:start position:0% as far as for modification tools for for these<00:02:03.390> platforms<00:02:05.000> all<00:02:06.000> right<00:02:06.150> so<00:02:06.510> it's<00:02:06.840> part 00:02:07.100 --> 00:02:07.110 align:start position:0% these platforms all right so it's part 00:02:07.110 --> 00:02:09.109 align:start position:0% these platforms all right so it's part to<00:02:07.290> the<00:02:07.439> work<00:02:07.799> we<00:02:07.979> have<00:02:08.129> done<00:02:08.159> quite<00:02:08.700> a<00:02:08.819> couple 00:02:09.109 --> 00:02:09.119 align:start position:0% to the work we have done quite a couple 00:02:09.119 --> 00:02:11.210 align:start position:0% to the work we have done quite a couple of<00:02:09.269> systems<00:02:09.959> so<00:02:10.229> far<00:02:10.500> so<00:02:10.709> I<00:02:10.769> have<00:02:10.890> listed<00:02:11.069> some 00:02:11.210 --> 00:02:11.220 align:start position:0% of systems so far so I have listed some 00:02:11.220 --> 00:02:11.970 align:start position:0% of systems so far so I have listed some of<00:02:11.459> those 00:02:11.970 --> 00:02:11.980 align:start position:0% of those 00:02:11.980 --> 00:02:15.660 align:start position:0% of those some<00:02:12.310> of<00:02:12.400> them<00:02:12.580> on<00:02:13.239> this<00:02:13.870> light<00:02:14.110> here<00:02:14.379> and<00:02:14.670> so 00:02:15.660 --> 00:02:15.670 align:start position:0% some of them on this light here and so 00:02:15.670 --> 00:02:16.979 align:start position:0% some of them on this light here and so this<00:02:15.790> is<00:02:15.970> the<00:02:16.120> name<00:02:16.360> to<00:02:16.540> achieve<00:02:16.780> different 00:02:16.979 --> 00:02:16.989 align:start position:0% this is the name to achieve different 00:02:16.989 --> 00:02:19.229 align:start position:0% this is the name to achieve different goals<00:02:17.200> we<00:02:17.590> typically<00:02:17.980> combine<00:02:18.340> techniques 00:02:19.229 --> 00:02:19.239 align:start position:0% goals we typically combine techniques 00:02:19.239 --> 00:02:20.880 align:start position:0% goals we typically combine techniques from<00:02:19.390> various<00:02:19.840> different<00:02:20.170> domains<00:02:20.500> such<00:02:20.860> as 00:02:20.880 --> 00:02:20.890 align:start position:0% from various different domains such as 00:02:20.890 --> 00:02:23.490 align:start position:0% from various different domains such as tactical<00:02:21.549> asset<00:02:21.849> dynamic<00:02:22.390> analysis<00:02:22.870> we<00:02:23.470> also 00:02:23.490 --> 00:02:23.500 align:start position:0% tactical asset dynamic analysis we also 00:02:23.500 --> 00:02:25.920 align:start position:0% tactical asset dynamic analysis we also use<00:02:23.890> quite<00:02:24.099> a<00:02:24.129> lot<00:02:24.250> of<00:02:24.400> fun<00:02:24.720> everybody<00:02:25.720> thinks 00:02:25.920 --> 00:02:25.930 align:start position:0% use quite a lot of fun everybody thinks 00:02:25.930 --> 00:02:28.920 align:start position:0% use quite a lot of fun everybody thinks of<00:02:26.049> machine<00:02:26.530> learning<00:02:26.830> to<00:02:27.239> to<00:02:28.239> you<00:02:28.780> know<00:02:28.810> to 00:02:28.920 --> 00:02:28.930 align:start position:0% of machine learning to to you know to 00:02:28.930 --> 00:02:31.770 align:start position:0% of machine learning to to you know to build<00:02:29.260> these<00:02:29.349> systems<00:02:29.590> so<00:02:30.450> some<00:02:31.450> of<00:02:31.480> you<00:02:31.660> are 00:02:31.770 --> 00:02:31.780 align:start position:0% build these systems so some of you are 00:02:31.780 --> 00:02:33.780 align:start position:0% build these systems so some of you are familiar<00:02:32.110> with<00:02:32.349> the<00:02:32.650> Sakura<00:02:33.099> fight<00:02:33.280> this<00:02:33.640> was 00:02:33.780 --> 00:02:33.790 align:start position:0% familiar with the Sakura fight this was 00:02:33.790 --> 00:02:35.660 align:start position:0% familiar with the Sakura fight this was the<00:02:33.940> first<00:02:34.180> system<00:02:34.690> that<00:02:34.810> were<00:02:34.959> built<00:02:35.200> back<00:02:35.440> in 00:02:35.660 --> 00:02:35.670 align:start position:0% the first system that were built back in 00:02:35.670 --> 00:02:39.059 align:start position:0% the first system that were built back in 2017<00:02:36.690> it's<00:02:37.690> a<00:02:37.780> system<00:02:38.140> for<00:02:38.170> finding<00:02:38.470> generic 00:02:39.059 --> 00:02:39.069 align:start position:0% 2017 it's a system for finding generic 00:02:39.069 --> 00:02:42.199 align:start position:0% 2017 it's a system for finding generic on<00:02:39.250> the<00:02:39.400> abilities<00:02:39.940> in<00:02:40.120> smart<00:02:40.420> contracts<00:02:41.069> and 00:02:42.199 --> 00:02:42.209 align:start position:0% on the abilities in smart contracts and 00:02:42.209 --> 00:02:46.740 align:start position:0% on the abilities in smart contracts and yeah<00:02:43.209> so<00:02:43.390> that's<00:02:44.910> was<00:02:45.910> basically<00:02:46.239> addressing 00:02:46.740 --> 00:02:46.750 align:start position:0% yeah so that's was basically addressing 00:02:46.750 --> 00:02:48.390 align:start position:0% yeah so that's was basically addressing all<00:02:46.930> these<00:02:47.079> puzzles<00:02:47.560> were<00:02:47.890> popping<00:02:48.190> up 00:02:48.390 --> 00:02:48.400 align:start position:0% all these puzzles were popping up 00:02:48.400 --> 00:02:51.080 align:start position:0% all these puzzles were popping up regularly<00:02:49.060> every<00:02:49.360> couple<00:02:49.629> of<00:02:49.660> weeks<00:02:49.720> in<00:02:50.079> 2017 00:02:51.080 --> 00:02:51.090 align:start position:0% regularly every couple of weeks in 2017 00:02:51.090 --> 00:02:54.270 align:start position:0% regularly every couple of weeks in 2017 in<00:02:52.090> all<00:02:52.420> these<00:02:52.569> you<00:02:53.319> know<00:02:53.349> parity<00:02:53.859> walnuts<00:02:54.160> and 00:02:54.270 --> 00:02:54.280 align:start position:0% in all these you know parity walnuts and 00:02:54.280 --> 00:02:55.619 align:start position:0% in all these you know parity walnuts and many<00:02:54.459> other<00:02:54.609> contracts<00:02:55.150> so<00:02:55.239> this<00:02:55.390> is<00:02:55.480> what 00:02:55.619 --> 00:02:55.629 align:start position:0% many other contracts so this is what 00:02:55.629 --> 00:02:58.349 align:start position:0% many other contracts so this is what that<00:02:55.780> system<00:02:55.989> was<00:02:56.290> addressing<00:02:56.739> and<00:02:57.180> so<00:02:58.180> this 00:02:58.349 --> 00:02:58.359 align:start position:0% that system was addressing and so this 00:02:58.359 --> 00:02:59.880 align:start position:0% that system was addressing and so this system<00:02:58.540> along<00:02:58.930> with<00:02:58.959> other<00:02:59.230> system<00:02:59.590> I<00:02:59.680> think 00:02:59.880 --> 00:02:59.890 align:start position:0% system along with other system I think 00:02:59.890 --> 00:03:01.140 align:start position:0% system along with other system I think they<00:02:59.980> made<00:03:00.160> a<00:03:00.190> difference<00:03:00.609> in<00:03:00.760> the<00:03:00.819> sense<00:03:01.000> of 00:03:01.140 --> 00:03:01.150 align:start position:0% they made a difference in the sense of 00:03:01.150 --> 00:03:05.539 align:start position:0% they made a difference in the sense of 2018<00:03:02.109> we<00:03:02.290> will<00:03:02.790> actually<00:03:03.790> so<00:03:04.180> much<00:03:04.660> fewer 00:03:05.539 --> 00:03:05.549 align:start position:0% 2018 we will actually so much fewer 00:03:05.549 --> 00:03:08.880 align:start position:0% 2018 we will actually so much fewer facts<00:03:06.549> because<00:03:07.120> of<00:03:07.329> such<00:03:07.510> generic<00:03:08.109> like 00:03:08.880 --> 00:03:08.890 align:start position:0% facts because of such generic like 00:03:08.890 --> 00:03:11.369 align:start position:0% facts because of such generic like really<00:03:09.220> simple<00:03:09.579> boxing<00:03:09.970> contracts<00:03:10.480> so 00:03:11.369 --> 00:03:11.379 align:start position:0% really simple boxing contracts so 00:03:11.379 --> 00:03:15.420 align:start position:0% really simple boxing contracts so another<00:03:12.280> system<00:03:12.640> we<00:03:12.790> have<00:03:12.970> builds<00:03:13.690> is<00:03:14.430> with 00:03:15.420 --> 00:03:15.430 align:start position:0% another system we have builds is with 00:03:15.430 --> 00:03:17.670 align:start position:0% another system we have builds is with every<00:03:15.670> wedding<00:03:16.030> system<00:03:16.389> that<00:03:16.569> addresses<00:03:17.260> the 00:03:17.670 --> 00:03:17.680 align:start position:0% every wedding system that addresses the 00:03:17.680 --> 00:03:19.440 align:start position:0% every wedding system that addresses the problem<00:03:18.040> of<00:03:18.160> ensuring<00:03:18.790> functional 00:03:19.440 --> 00:03:19.450 align:start position:0% problem of ensuring functional 00:03:19.450 --> 00:03:21.150 align:start position:0% problem of ensuring functional correctness<00:03:19.720> so<00:03:20.650> we're<00:03:20.799> going<00:03:20.889> to<00:03:20.950> talk<00:03:21.099> a 00:03:21.150 --> 00:03:21.160 align:start position:0% correctness so we're going to talk a 00:03:21.160 --> 00:03:22.589 align:start position:0% correctness so we're going to talk a little<00:03:21.310> bit<00:03:21.489> more<00:03:21.519> about<00:03:21.880> what<00:03:22.180> functional 00:03:22.589 --> 00:03:22.599 align:start position:0% little bit more about what functional 00:03:22.599 --> 00:03:24.180 align:start position:0% little bit more about what functional corrective<00:03:23.019> correctness<00:03:23.560> actually<00:03:24.010> means 00:03:24.180 --> 00:03:24.190 align:start position:0% corrective correctness actually means 00:03:24.190 --> 00:03:26.670 align:start position:0% corrective correctness actually means and<00:03:24.450> we<00:03:25.450> have<00:03:25.569> fuzzing<00:03:26.169> system<00:03:26.530> that 00:03:26.670 --> 00:03:26.680 align:start position:0% and we have fuzzing system that 00:03:26.680 --> 00:03:28.710 align:start position:0% and we have fuzzing system that essentially<00:03:27.069> generates<00:03:28.000> transactions<00:03:28.540> and 00:03:28.710 --> 00:03:28.720 align:start position:0% essentially generates transactions and 00:03:28.720 --> 00:03:32.370 align:start position:0% essentially generates transactions and tries<00:03:29.260> to<00:03:29.290> find<00:03:29.650> violations<00:03:29.980> of<00:03:30.459> the<00:03:31.380> specific 00:03:32.370 --> 00:03:32.380 align:start position:0% tries to find violations of the specific 00:03:32.380 --> 00:03:33.809 align:start position:0% tries to find violations of the specific security<00:03:32.799> properties<00:03:33.250> that<00:03:33.340> we're<00:03:33.549> trying<00:03:33.700> to 00:03:33.809 --> 00:03:33.819 align:start position:0% security properties that we're trying to 00:03:33.819 --> 00:03:35.930 align:start position:0% security properties that we're trying to to<00:03:34.480> check<00:03:34.720> for<00:03:34.930> or<00:03:35.079> for<00:03:35.200> a<00:03:35.260> small<00:03:35.349> conference 00:03:35.930 --> 00:03:35.940 align:start position:0% to check for or for a small conference 00:03:35.940 --> 00:03:39.120 align:start position:0% to check for or for a small conference and<00:03:36.940> the<00:03:37.840> main<00:03:38.019> system<00:03:38.380> that<00:03:38.530> we<00:03:38.769> will<00:03:38.950> be 00:03:39.120 --> 00:03:39.130 align:start position:0% and the main system that we will be 00:03:39.130 --> 00:03:41.220 align:start position:0% and the main system that we will be talking<00:03:39.310> about<00:03:39.579> today<00:03:39.970> is<00:03:40.120> the<00:03:40.359> direct<00:03:40.840> system 00:03:41.220 --> 00:03:41.230 align:start position:0% talking about today is the direct system 00:03:41.230 --> 00:03:45.960 align:start position:0% talking about today is the direct system which<00:03:42.220> is<00:03:42.930> the<00:03:43.930> first<00:03:44.410> automated<00:03:45.069> verify<00:03:45.639> for 00:03:45.960 --> 00:03:45.970 align:start position:0% which is the first automated verify for 00:03:45.970 --> 00:03:48.990 align:start position:0% which is the first automated verify for for<00:03:46.450> verifying<00:03:46.870> smart<00:03:47.169> contracts<00:03:47.609> this<00:03:48.609> we 00:03:48.990 --> 00:03:49.000 align:start position:0% for verifying smart contracts this we 00:03:49.000 --> 00:03:52.289 align:start position:0% for verifying smart contracts this we have<00:03:49.120> a<00:03:49.150> demo<00:03:49.540> on<00:03:50.160> variance<00:03:51.160> of<00:03:51.310> CH<00:03:51.700> we<00:03:52.150> have 00:03:52.289 --> 00:03:52.299 align:start position:0% have a demo on variance of CH we have 00:03:52.299 --> 00:03:54.780 align:start position:0% have a demo on variance of CH we have some<00:03:52.510> few<00:03:52.900> other<00:03:53.109> instances<00:03:53.680> of<00:03:53.739> this<00:03:54.010> system 00:03:54.780 --> 00:03:54.790 align:start position:0% some few other instances of this system 00:03:54.790 --> 00:03:55.480 align:start position:0% some few other instances of this system that's<00:03:54.940> one 00:03:55.480 --> 00:03:55.490 align:start position:0% that's one 00:03:55.490 --> 00:03:59.590 align:start position:0% that's one for<00:03:55.820> the<00:03:55.910> exercise<00:03:56.740> later<00:03:57.740> today<00:03:58.100> and<00:03:58.600> for 00:03:59.590 --> 00:03:59.600 align:start position:0% for the exercise later today and for 00:03:59.600 --> 00:04:01.810 align:start position:0% for the exercise later today and for people<00:03:59.960> that<00:04:00.320> are<00:04:00.530> interested<00:04:01.070> really<00:04:01.700> in 00:04:01.810 --> 00:04:01.820 align:start position:0% people that are interested really in 00:04:01.820 --> 00:04:03.850 align:start position:0% people that are interested really in depth<00:04:02.180> on<00:04:02.360> how<00:04:02.390> that<00:04:02.810> system<00:04:03.050> works<00:04:03.260> what 00:04:03.850 --> 00:04:03.860 align:start position:0% depth on how that system works what 00:04:03.860 --> 00:04:06.310 align:start position:0% depth on how that system works what guarantees<00:04:04.400> it<00:04:04.550> provides<00:04:04.910> so<00:04:05.750> we<00:04:05.900> also<00:04:06.050> have<00:04:06.290> a 00:04:06.310 --> 00:04:06.320 align:start position:0% guarantees it provides so we also have a 00:04:06.320 --> 00:04:08.290 align:start position:0% guarantees it provides so we also have a research<00:04:06.770> paper<00:04:06.980> which<00:04:07.550> will<00:04:07.790> appear<00:04:08.150> at<00:04:08.270> the 00:04:08.290 --> 00:04:08.300 align:start position:0% research paper which will appear at the 00:04:08.300 --> 00:04:10.720 align:start position:0% research paper which will appear at the to<00:04:09.110> Boise<00:04:09.440> possible<00:04:09.920> security<00:04:10.130> and<00:04:10.580> privacy 00:04:10.720 --> 00:04:10.730 align:start position:0% to Boise possible security and privacy 00:04:10.730 --> 00:04:13.180 align:start position:0% to Boise possible security and privacy so<00:04:11.150> that's<00:04:11.300> one<00:04:11.450> of<00:04:11.480> the<00:04:11.570> main<00:04:12.190> security 00:04:13.180 --> 00:04:13.190 align:start position:0% so that's one of the main security 00:04:13.190 --> 00:04:15.400 align:start position:0% so that's one of the main security conferences<00:04:14.030> one<00:04:14.930> of<00:04:15.020> the<00:04:15.080> main<00:04:15.230> academic 00:04:15.400 --> 00:04:15.410 align:start position:0% conferences one of the main academic 00:04:15.410 --> 00:04:18.010 align:start position:0% conferences one of the main academic security<00:04:16.010> conferences<00:04:16.489> so<00:04:16.670> if<00:04:17.330> you<00:04:17.480> go<00:04:17.600> on<00:04:17.750> our 00:04:18.010 --> 00:04:18.020 align:start position:0% security conferences so if you go on our 00:04:18.020 --> 00:04:20.290 align:start position:0% security conferences so if you go on our webpage<00:04:18.500> chase<00:04:18.800> younits.com<00:04:19.400> I<00:04:20.090> go<00:04:20.239> to 00:04:20.290 --> 00:04:20.300 align:start position:0% webpage chase younits.com I go to 00:04:20.300 --> 00:04:22.540 align:start position:0% webpage chase younits.com I go to research<00:04:20.690> you<00:04:21.410> can<00:04:21.560> download<00:04:21.800> the<00:04:22.070> PDF<00:04:22.220> and 00:04:22.540 --> 00:04:22.550 align:start position:0% research you can download the PDF and 00:04:22.550 --> 00:04:24.990 align:start position:0% research you can download the PDF and read<00:04:22.940> all<00:04:23.150> the<00:04:23.270> details<00:04:23.390> about<00:04:23.780> the 00:04:24.990 --> 00:04:25.000 align:start position:0% read all the details about the 00:04:25.000 --> 00:04:27.130 align:start position:0% read all the details about the verification<00:04:26.000> technique<00:04:26.330> that<00:04:26.600> is<00:04:26.780> being 00:04:27.130 --> 00:04:27.140 align:start position:0% verification technique that is being 00:04:27.140 --> 00:04:33.250 align:start position:0% verification technique that is being used<00:04:27.560> in<00:04:27.680> that<00:04:27.800> system<00:04:29.440> alright<00:04:31.360> so<00:04:32.360> before<00:04:32.930> we 00:04:33.250 --> 00:04:33.260 align:start position:0% used in that system alright so before we 00:04:33.260 --> 00:04:35.590 align:start position:0% used in that system alright so before we actually<00:04:33.290> do<00:04:33.950> I<00:04:33.980> you<00:04:34.790> know<00:04:34.880> go<00:04:35.270> into<00:04:35.450> the 00:04:35.590 --> 00:04:35.600 align:start position:0% actually do I you know go into the 00:04:35.600 --> 00:04:38.590 align:start position:0% actually do I you know go into the hands-on<00:04:36.190> exercises<00:04:37.190> it's<00:04:37.940> important<00:04:38.510> also 00:04:38.590 --> 00:04:38.600 align:start position:0% hands-on exercises it's important also 00:04:38.600 --> 00:04:40.150 align:start position:0% hands-on exercises it's important also to<00:04:38.720> mention<00:04:38.960> why<00:04:39.290> are<00:04:39.470> we<00:04:39.650> actually<00:04:39.800> doing 00:04:40.150 --> 00:04:40.160 align:start position:0% to mention why are we actually doing 00:04:40.160 --> 00:04:43.150 align:start position:0% to mention why are we actually doing this<00:04:40.430> and<00:04:40.730> the<00:04:41.630> main<00:04:41.870> reason<00:04:42.470> is<00:04:42.560> that<00:04:42.620> I<00:04:43.070> mean 00:04:43.150 --> 00:04:43.160 align:start position:0% this and the main reason is that I mean 00:04:43.160 --> 00:04:45.100 align:start position:0% this and the main reason is that I mean where<00:04:43.460> they<00:04:43.550> initialize<00:04:44.300> how<00:04:44.540> many<00:04:44.750> people 00:04:45.100 --> 00:04:45.110 align:start position:0% where they initialize how many people 00:04:45.110 --> 00:04:47.110 align:start position:0% where they initialize how many people have<00:04:45.230> verified<00:04:45.620> contracts<00:04:46.190> I<00:04:46.340> think<00:04:47.030> they 00:04:47.110 --> 00:04:47.120 align:start position:0% have verified contracts I think they 00:04:47.120 --> 00:04:49.330 align:start position:0% have verified contracts I think they worked<00:04:47.300> about<00:04:47.570> two<00:04:47.810> three<00:04:48.020> hands<00:04:48.320> and<00:04:48.560> the 00:04:49.330 --> 00:04:49.340 align:start position:0% worked about two three hands and the 00:04:49.340 --> 00:04:51.400 align:start position:0% worked about two three hands and the reason<00:04:49.700> this<00:04:50.120> is<00:04:50.180> is<00:04:50.390> that<00:04:50.690> you<00:04:50.870> know<00:04:50.960> thermo 00:04:51.400 --> 00:04:51.410 align:start position:0% reason this is is that you know thermo 00:04:51.410 --> 00:04:52.660 align:start position:0% reason this is is that you know thermo replication<00:04:51.980> used<00:04:52.130> to<00:04:52.190> be<00:04:52.280> this<00:04:52.340> very 00:04:52.660 --> 00:04:52.670 align:start position:0% replication used to be this very 00:04:52.670 --> 00:04:56.170 align:start position:0% replication used to be this very difficult<00:04:53.630> time-consuming<00:04:54.700> task<00:04:55.700> or<00:04:56.060> you 00:04:56.170 --> 00:04:56.180 align:start position:0% difficult time-consuming task or you 00:04:56.180 --> 00:04:58.780 align:start position:0% difficult time-consuming task or you have<00:04:56.420> to<00:04:56.540> be<00:04:56.660> really<00:04:57.050> an<00:04:57.740> expert<00:04:58.250> in<00:04:58.310> formal 00:04:58.780 --> 00:04:58.790 align:start position:0% have to be really an expert in formal 00:04:58.790 --> 00:05:01.270 align:start position:0% have to be really an expert in formal verification<00:04:58.940> have<00:04:59.630> a<00:04:59.660> PhD<00:05:00.050> in<00:05:00.230> logics<00:05:00.950> and<00:05:01.070> so 00:05:01.270 --> 00:05:01.280 align:start position:0% verification have a PhD in logics and so 00:05:01.280 --> 00:05:03.910 align:start position:0% verification have a PhD in logics and so on<00:05:01.400> to<00:05:01.640> to<00:05:02.330> to<00:05:03.050> prove<00:05:03.260> that<00:05:03.410> a<00:05:03.500> contract<00:05:03.860> is 00:05:03.910 --> 00:05:03.920 align:start position:0% on to to to prove that a contract is 00:05:03.920 --> 00:05:07.270 align:start position:0% on to to to prove that a contract is correct<00:05:04.250> and<00:05:04.690> if<00:05:05.690> we<00:05:05.990> are<00:05:06.230> to<00:05:06.470> make<00:05:06.830> form<00:05:07.160> of 00:05:07.270 --> 00:05:07.280 align:start position:0% correct and if we are to make form of 00:05:07.280 --> 00:05:09.700 align:start position:0% correct and if we are to make form of ratification<00:05:07.550> mainstream<00:05:08.480> you<00:05:09.170> know<00:05:09.200> a<00:05:09.320> lot 00:05:09.700 --> 00:05:09.710 align:start position:0% ratification mainstream you know a lot 00:05:09.710 --> 00:05:11.170 align:start position:0% ratification mainstream you know a lot of<00:05:09.740> developers<00:05:10.370> also<00:05:10.580> adopting<00:05:11.150> that 00:05:11.170 --> 00:05:11.180 align:start position:0% of developers also adopting that 00:05:11.180 --> 00:05:13.330 align:start position:0% of developers also adopting that approach<00:05:11.350> then<00:05:12.350> you<00:05:12.530> have<00:05:12.680> to<00:05:12.830> be<00:05:12.950> building<00:05:13.280> a 00:05:13.330 --> 00:05:13.340 align:start position:0% approach then you have to be building a 00:05:13.340 --> 00:05:14.860 align:start position:0% approach then you have to be building a system<00:05:13.550> we<00:05:13.820> have<00:05:13.940> to<00:05:14.030> be<00:05:14.150> building<00:05:14.450> systems 00:05:14.860 --> 00:05:14.870 align:start position:0% system we have to be building systems 00:05:14.870 --> 00:05:16.870 align:start position:0% system we have to be building systems that<00:05:14.930> allow<00:05:15.710> people<00:05:16.280> without<00:05:16.760> this 00:05:16.870 --> 00:05:16.880 align:start position:0% that allow people without this 00:05:16.880 --> 00:05:18.790 align:start position:0% that allow people without this background<00:05:17.120> to<00:05:17.480> write<00:05:18.380> functional 00:05:18.790 --> 00:05:18.800 align:start position:0% background to write functional 00:05:18.800 --> 00:05:20.710 align:start position:0% background to write functional specifications<00:05:19.550> and<00:05:19.670> prove<00:05:20.150> the<00:05:20.300> contracts 00:05:20.710 --> 00:05:20.720 align:start position:0% specifications and prove the contracts 00:05:20.720 --> 00:05:23.980 align:start position:0% specifications and prove the contracts correct<00:05:21.080> and<00:05:21.760> that's<00:05:22.760> exactly<00:05:23.240> what<00:05:23.570> this 00:05:23.980 --> 00:05:23.990 align:start position:0% correct and that's exactly what this 00:05:23.990 --> 00:05:27.400 align:start position:0% correct and that's exactly what this very<00:05:24.230> very<00:05:24.620> very<00:05:24.920> far<00:05:25.100> aims<00:05:25.310> to<00:05:25.520> do<00:05:26.110> so<00:05:27.110> it 00:05:27.400 --> 00:05:27.410 align:start position:0% very very very far aims to do so it 00:05:27.410 --> 00:05:30.060 align:start position:0% very very very far aims to do so it eliminates<00:05:27.950> this<00:05:28.070> nest<00:05:28.400> needs<00:05:28.880> to<00:05:29.150> know 00:05:30.060 --> 00:05:30.070 align:start position:0% eliminates this nest needs to know 00:05:30.070 --> 00:05:31.960 align:start position:0% eliminates this nest needs to know in-depth<00:05:31.070> knowledge<00:05:31.280> of<00:05:31.610> form<00:05:31.850> of 00:05:31.960 --> 00:05:31.970 align:start position:0% in-depth knowledge of form of 00:05:31.970 --> 00:05:35.110 align:start position:0% in-depth knowledge of form of verification<00:05:32.120> and<00:05:32.900> takes<00:05:33.710> down<00:05:33.860> this<00:05:34.610> reduces 00:05:35.110 --> 00:05:35.120 align:start position:0% verification and takes down this reduces 00:05:35.120 --> 00:05:36.380 align:start position:0% verification and takes down this reduces also<00:05:35.390> significantly 00:05:36.380 --> 00:05:36.390 align:start position:0% also significantly 00:05:36.390 --> 00:05:39.980 align:start position:0% also significantly vacation<00:05:36.810> time<00:05:38.000> because<00:05:39.000> I<00:05:39.330> suppose<00:05:39.690> it's 00:05:39.980 --> 00:05:39.990 align:start position:0% vacation time because I suppose it's 00:05:39.990 --> 00:05:43.540 align:start position:0% vacation time because I suppose it's really<00:05:40.320> not<00:05:41.160> a<00:05:41.220> very<00:05:41.640> hard<00:05:41.820> task<00:05:42.060> to<00:05:42.270> to<00:05:42.900> verify 00:05:43.540 --> 00:05:43.550 align:start position:0% really not a very hard task to to verify 00:05:43.550 --> 00:05:46.370 align:start position:0% really not a very hard task to to verify contracts<00:05:44.550> with<00:05:44.970> such<00:05:45.120> systems<00:05:45.510> so<00:05:46.050> we<00:05:46.200> said<00:05:46.350> a 00:05:46.370 --> 00:05:46.380 align:start position:0% contracts with such systems so we said a 00:05:46.380 --> 00:05:47.660 align:start position:0% contracts with such systems so we said a system<00:05:46.740> if<00:05:46.860> you<00:05:46.950> take<00:05:47.130> something<00:05:47.370> like<00:05:47.520> a 00:05:47.660 --> 00:05:47.670 align:start position:0% system if you take something like a 00:05:47.670 --> 00:05:49.640 align:start position:0% system if you take something like a standard<00:05:48.120> ear<00:05:48.390> seat<00:05:48.570> when<00:05:48.780> it's<00:05:48.870> open<00:05:49.170> which 00:05:49.640 --> 00:05:49.650 align:start position:0% standard ear seat when it's open which 00:05:49.650 --> 00:05:52.190 align:start position:0% standard ear seat when it's open which will<00:05:49.980> look<00:05:50.490> in-depth<00:05:51.000> in<00:05:51.120> the<00:05:51.240> exercise<00:05:51.630> you 00:05:52.190 --> 00:05:52.200 align:start position:0% will look in-depth in the exercise you 00:05:52.200 --> 00:05:55.070 align:start position:0% will look in-depth in the exercise you can<00:05:52.350> literally<00:05:52.650> no<00:05:53.450> formal<00:05:54.450> ratification<00:05:54.600> for 00:05:55.070 --> 00:05:55.080 align:start position:0% can literally no formal ratification for 00:05:55.080 --> 00:05:56.720 align:start position:0% can literally no formal ratification for all<00:05:55.380> the<00:05:55.560> main<00:05:55.710> properties<00:05:56.190> you<00:05:56.340> will<00:05:56.490> care 00:05:56.720 --> 00:05:56.730 align:start position:0% all the main properties you will care 00:05:56.730 --> 00:05:59.360 align:start position:0% all the main properties you will care about<00:05:57.480> a<00:05:57.510> token<00:05:57.960> you<00:05:58.050> know<00:05:58.170> in<00:05:58.500> a<00:05:58.740> matter<00:05:59.130> of<00:05:59.280> a 00:05:59.360 --> 00:05:59.370 align:start position:0% about a token you know in a matter of a 00:05:59.370 --> 00:06:01.130 align:start position:0% about a token you know in a matter of a couple<00:05:59.400> of<00:05:59.640> hours<00:05:59.970> that<00:06:00.000> we<00:06:00.390> done<00:06:00.570> with<00:06:00.690> with 00:06:01.130 --> 00:06:01.140 align:start position:0% couple of hours that we done with with 00:06:01.140 --> 00:06:04.310 align:start position:0% couple of hours that we done with with the<00:06:01.230> ratification<00:06:01.440> ever<00:06:02.870> visit<00:06:03.870> here<00:06:04.050> some<00:06:04.290> of 00:06:04.310 --> 00:06:04.320 align:start position:0% the ratification ever visit here some of 00:06:04.320 --> 00:06:06.620 align:start position:0% the ratification ever visit here some of us<00:06:04.470> some<00:06:04.770> someone<00:06:05.490> that<00:06:05.760> we<00:06:05.880> have<00:06:06.030> verified<00:06:06.210> we 00:06:06.620 --> 00:06:06.630 align:start position:0% us some someone that we have verified we 00:06:06.630 --> 00:06:09.470 align:start position:0% us some someone that we have verified we have<00:06:06.750> more<00:06:06.990> on<00:06:07.440> our<00:06:07.680> main<00:06:08.100> webpage<00:06:08.400> a<00:06:08.940> spirit 00:06:09.470 --> 00:06:09.480 align:start position:0% have more on our main webpage a spirit 00:06:09.480 --> 00:06:11.690 align:start position:0% have more on our main webpage a spirit of<00:06:09.600> calm<00:06:09.780> /<00:06:10.020> audits<00:06:10.410> or<00:06:10.620> you<00:06:11.010> can<00:06:11.160> find<00:06:11.400> some<00:06:11.580> of 00:06:11.690 --> 00:06:11.700 align:start position:0% of calm / audits or you can find some of 00:06:11.700 --> 00:06:14.350 align:start position:0% of calm / audits or you can find some of some<00:06:12.090> of<00:06:12.210> these<00:06:12.300> reports<00:06:12.510> where<00:06:12.930> we<00:06:13.200> have<00:06:13.350> done 00:06:14.350 --> 00:06:14.360 align:start position:0% some of these reports where we have done 00:06:14.360 --> 00:06:18.950 align:start position:0% some of these reports where we have done proper<00:06:15.360> verification<00:06:15.900> of<00:06:16.410> those<00:06:17.810> all<00:06:18.810> right 00:06:18.950 --> 00:06:18.960 align:start position:0% proper verification of those all right 00:06:18.960 --> 00:06:20.960 align:start position:0% proper verification of those all right so<00:06:19.230> the<00:06:19.560> workshop<00:06:19.860> will<00:06:20.040> continue<00:06:20.430> as<00:06:20.550> follows 00:06:20.960 --> 00:06:20.970 align:start position:0% so the workshop will continue as follows 00:06:20.970 --> 00:06:23.720 align:start position:0% so the workshop will continue as follows so<00:06:21.270> we'll<00:06:22.050> start<00:06:22.230> with<00:06:22.290> some<00:06:22.530> very<00:06:23.010> more 00:06:23.720 --> 00:06:23.730 align:start position:0% so we'll start with some very more 00:06:23.730 --> 00:06:25.310 align:start position:0% so we'll start with some very more high-level<00:06:24.480> introduction<00:06:24.870> to<00:06:25.170> what 00:06:25.310 --> 00:06:25.320 align:start position:0% high-level introduction to what 00:06:25.320 --> 00:06:28.610 align:start position:0% high-level introduction to what functional<00:06:25.800> correctness<00:06:26.070> means<00:06:26.580> and<00:06:27.560> why<00:06:28.560> is 00:06:28.610 --> 00:06:28.620 align:start position:0% functional correctness means and why is 00:06:28.620 --> 00:06:31.450 align:start position:0% functional correctness means and why is it<00:06:28.740> challenging<00:06:29.460> to<00:06:30.230> formally<00:06:31.230> verified 00:06:31.450 --> 00:06:31.460 align:start position:0% it challenging to formally verified 00:06:31.460 --> 00:06:33.950 align:start position:0% it challenging to formally verified properties<00:06:32.460> with<00:06:32.670> functional<00:06:33.540> properties 00:06:33.950 --> 00:06:33.960 align:start position:0% properties with functional properties 00:06:33.960 --> 00:06:35.930 align:start position:0% properties with functional properties and<00:06:34.200> what<00:06:35.040> are<00:06:35.190> different<00:06:35.220> techniques<00:06:35.850> that 00:06:35.930 --> 00:06:35.940 align:start position:0% and what are different techniques that 00:06:35.940 --> 00:06:37.940 align:start position:0% and what are different techniques that different<00:06:36.690> tools<00:06:36.930> are<00:06:37.290> introduced<00:06:37.800> in<00:06:37.920> that 00:06:37.940 --> 00:06:37.950 align:start position:0% different tools are introduced in that 00:06:37.950 --> 00:06:40.160 align:start position:0% different tools are introduced in that space<00:06:38.310> what's<00:06:39.090> called<00:06:39.420> a<00:06:39.540> different<00:06:39.870> person 00:06:40.160 --> 00:06:40.170 align:start position:0% space what's called a different person 00:06:40.170 --> 00:06:43.400 align:start position:0% space what's called a different person guarantees<00:06:40.700> today<00:06:41.700> so<00:06:42.240> also<00:06:42.690> will<00:06:42.840> cover<00:06:43.050> here 00:06:43.400 --> 00:06:43.410 align:start position:0% guarantees today so also will cover here 00:06:43.410 --> 00:06:45.380 align:start position:0% guarantees today so also will cover here of<00:06:43.500> course<00:06:43.650> that<00:06:43.740> the<00:06:44.250> correct<00:06:44.850> system<00:06:45.000> and 00:06:45.380 --> 00:06:45.390 align:start position:0% of course that the correct system and 00:06:45.390 --> 00:06:47.720 align:start position:0% of course that the correct system and then<00:06:46.290> in<00:06:46.410> the<00:06:46.500> second<00:06:46.830> half<00:06:46.980> you'll<00:06:47.190> switch<00:06:47.460> to 00:06:47.720 --> 00:06:47.730 align:start position:0% then in the second half you'll switch to 00:06:47.730 --> 00:06:51.100 align:start position:0% then in the second half you'll switch to a<00:06:47.760> hands-on<00:06:48.240> exercise<00:06:48.750> where<00:06:49.080> Demeter<00:06:49.800> will 00:06:51.100 --> 00:06:51.110 align:start position:0% a hands-on exercise where Demeter will 00:06:51.110 --> 00:06:54.830 align:start position:0% a hands-on exercise where Demeter will talk<00:06:52.110> walk<00:06:52.860> you<00:06:53.040> through<00:06:53.310> how<00:06:53.610> do<00:06:54.210> we<00:06:54.510> specify 00:06:54.830 --> 00:06:54.840 align:start position:0% talk walk you through how do we specify 00:06:54.840 --> 00:06:57.020 align:start position:0% talk walk you through how do we specify properties<00:06:55.320> and<00:06:55.950> verify<00:06:56.340> them<00:06:56.490> with<00:06:56.670> with<00:06:57.000> a 00:06:57.020 --> 00:06:57.030 align:start position:0% properties and verify them with with a 00:06:57.030 --> 00:06:59.930 align:start position:0% properties and verify them with with a verifiable<00:06:57.510> Eric's<00:06:58.020> and<00:06:58.610> so<00:06:59.610> we've<00:06:59.760> also 00:06:59.930 --> 00:06:59.940 align:start position:0% verifiable Eric's and so we've also 00:06:59.940 --> 00:07:02.600 align:start position:0% verifiable Eric's and so we've also about<00:07:00.270> many<00:07:00.870> other<00:07:01.190> people<00:07:02.190> from<00:07:02.280> the<00:07:02.370> chain 00:07:02.600 --> 00:07:02.610 align:start position:0% about many other people from the chain 00:07:02.610 --> 00:07:04.280 align:start position:0% about many other people from the chain security<00:07:03.000> team<00:07:03.150> back<00:07:03.360> there<00:07:03.570> so<00:07:03.870> they<00:07:03.900> will<00:07:04.110> be 00:07:04.280 --> 00:07:04.290 align:start position:0% security team back there so they will be 00:07:04.290 --> 00:07:06.590 align:start position:0% security team back there so they will be assisting<00:07:04.710> you<00:07:05.340> while<00:07:05.700> doing<00:07:06.360> this<00:07:06.450> exercise 00:07:06.590 --> 00:07:06.600 align:start position:0% assisting you while doing this exercise 00:07:06.600 --> 00:07:09.410 align:start position:0% assisting you while doing this exercise and<00:07:07.170> then<00:07:07.740> in<00:07:08.010> the<00:07:08.100> last<00:07:08.220> part<00:07:08.400> depending<00:07:09.270> on 00:07:09.410 --> 00:07:09.420 align:start position:0% and then in the last part depending on 00:07:09.420 --> 00:07:11.770 align:start position:0% and then in the last part depending on time<00:07:09.840> we'll<00:07:10.350> try<00:07:10.680> to<00:07:10.770> get<00:07:10.980> into<00:07:11.280> some<00:07:11.490> more 00:07:11.770 --> 00:07:11.780 align:start position:0% time we'll try to get into some more 00:07:11.780 --> 00:07:14.210 align:start position:0% time we'll try to get into some more detail<00:07:12.780> about<00:07:13.080> the<00:07:13.320> actual<00:07:13.410> verification 00:07:14.210 --> 00:07:14.220 align:start position:0% detail about the actual verification 00:07:14.220 --> 00:07:15.860 align:start position:0% detail about the actual verification methods<00:07:14.580> and<00:07:14.700> how<00:07:14.880> this<00:07:15.060> is<00:07:15.240> being<00:07:15.420> automated 00:07:15.860 --> 00:07:15.870 align:start position:0% methods and how this is being automated 00:07:15.870 --> 00:07:20.090 align:start position:0% methods and how this is being automated by<00:07:16.110> the<00:07:16.170> various<00:07:16.470> verifier<00:07:17.570> alright<00:07:18.710> so<00:07:19.710> let's 00:07:20.090 --> 00:07:20.100 align:start position:0% by the various verifier alright so let's 00:07:20.100 --> 00:07:23.290 align:start position:0% by the various verifier alright so let's get<00:07:20.220> started<00:07:20.280> and<00:07:21.800> functional<00:07:22.800> correctness 00:07:23.290 --> 00:07:23.300 align:start position:0% get started and functional correctness 00:07:23.300 --> 00:07:25.310 align:start position:0% get started and functional correctness so<00:07:24.300> what<00:07:24.420> is<00:07:24.510> functional<00:07:24.840> correctly<00:07:25.170> so 00:07:25.310 --> 00:07:25.320 align:start position:0% so what is functional correctly so 00:07:25.320 --> 00:07:27.050 align:start position:0% so what is functional correctly so usually<00:07:25.800> when<00:07:25.950> people<00:07:25.980> think<00:07:26.430> about<00:07:26.550> security 00:07:27.050 --> 00:07:27.060 align:start position:0% usually when people think about security 00:07:27.060 --> 00:07:30.320 align:start position:0% usually when people think about security tools<00:07:27.300> they're<00:07:28.370> these<00:07:29.370> kind<00:07:29.820> of<00:07:29.850> tools<00:07:30.060> where 00:07:30.320 --> 00:07:30.330 align:start position:0% tools they're these kind of tools where 00:07:30.330 --> 00:07:32.180 align:start position:0% tools they're these kind of tools where you<00:07:30.360> just<00:07:30.870> paste<00:07:31.080> the<00:07:31.260> codes<00:07:31.470> and<00:07:31.860> then<00:07:32.010> they 00:07:32.180 --> 00:07:32.190 align:start position:0% you just paste the codes and then they 00:07:32.190 --> 00:07:33.920 align:start position:0% you just paste the codes and then they show<00:07:32.610> you<00:07:32.670> a<00:07:32.790> bunch<00:07:33.090> of<00:07:33.180> on<00:07:33.330> the<00:07:33.450> business<00:07:33.810> that 00:07:33.920 --> 00:07:33.930 align:start position:0% show you a bunch of on the business that 00:07:33.930 --> 00:07:35.750 align:start position:0% show you a bunch of on the business that founds<00:07:34.290> so<00:07:34.740> this<00:07:34.890> is<00:07:35.010> not<00:07:35.220> what<00:07:35.430> we're<00:07:35.610> talking 00:07:35.750 --> 00:07:35.760 align:start position:0% founds so this is not what we're talking 00:07:35.760 --> 00:07:37.910 align:start position:0% founds so this is not what we're talking about<00:07:36.000> here<00:07:36.420> so<00:07:36.600> we're<00:07:37.260> not<00:07:37.290> looking<00:07:37.620> for<00:07:37.650> more 00:07:37.910 --> 00:07:37.920 align:start position:0% about here so we're not looking for more 00:07:37.920 --> 00:07:39.390 align:start position:0% about here so we're not looking for more dynamic<00:07:38.640> movement 00:07:39.390 --> 00:07:39.400 align:start position:0% dynamic movement 00:07:39.400 --> 00:07:41.820 align:start position:0% dynamic movement were<00:07:40.000> talking<00:07:40.840> about<00:07:40.960> functional 00:07:41.820 --> 00:07:41.830 align:start position:0% were talking about functional 00:07:41.830 --> 00:07:43.920 align:start position:0% were talking about functional correctness<00:07:42.010> and<00:07:42.520> what<00:07:43.180> this<00:07:43.300> means<00:07:43.510> is<00:07:43.690> that 00:07:43.920 --> 00:07:43.930 align:start position:0% correctness and what this means is that 00:07:43.930 --> 00:07:46.260 align:start position:0% correctness and what this means is that whether<00:07:44.860> the<00:07:45.220> problem<00:07:45.820> of<00:07:45.910> functional 00:07:46.260 --> 00:07:46.270 align:start position:0% whether the problem of functional 00:07:46.270 --> 00:07:48.719 align:start position:0% whether the problem of functional correctness<00:07:46.479> has<00:07:46.690> two<00:07:47.590> parts<00:07:47.919> so<00:07:48.130> honest<00:07:48.520> you 00:07:48.719 --> 00:07:48.729 align:start position:0% correctness has two parts so honest you 00:07:48.729 --> 00:07:50.400 align:start position:0% correctness has two parts so honest you have<00:07:48.880> this<00:07:49.030> hard<00:07:49.300> culture<00:07:49.720> that<00:07:49.990> you<00:07:50.139> want<00:07:50.290> to 00:07:50.400 --> 00:07:50.410 align:start position:0% have this hard culture that you want to 00:07:50.410 --> 00:07:53.070 align:start position:0% have this hard culture that you want to prove<00:07:51.160> that<00:07:51.430> if<00:07:52.120> you<00:07:52.270> wanna<00:07:52.449> you<00:07:52.690> want<00:07:52.900> to<00:07:52.960> make 00:07:53.070 --> 00:07:53.080 align:start position:0% prove that if you wanna you want to make 00:07:53.080 --> 00:07:54.990 align:start position:0% prove that if you wanna you want to make sure<00:07:53.110> it's<00:07:53.380> correct<00:07:53.530> and<00:07:54.040> then<00:07:54.520> the<00:07:54.639> second 00:07:54.990 --> 00:07:55.000 align:start position:0% sure it's correct and then the second 00:07:55.000 --> 00:07:56.490 align:start position:0% sure it's correct and then the second piece<00:07:55.120> of<00:07:55.180> information<00:07:55.660> that<00:07:56.080> you<00:07:56.229> need<00:07:56.260> is 00:07:56.490 --> 00:07:56.500 align:start position:0% piece of information that you need is 00:07:56.500 --> 00:07:58.290 align:start position:0% piece of information that you need is the<00:07:56.680> functional<00:07:57.130> specification<00:07:57.280> of<00:07:57.970> a<00:07:58.030> smart 00:07:58.290 --> 00:07:58.300 align:start position:0% the functional specification of a smart 00:07:58.300 --> 00:08:00.900 align:start position:0% the functional specification of a smart contract<00:07:58.720> so<00:07:59.530> a<00:07:59.560> function<00:08:00.010> specification<00:08:00.820> is 00:08:00.900 --> 00:08:00.910 align:start position:0% contract so a function specification is 00:08:00.910 --> 00:08:02.969 align:start position:0% contract so a function specification is that<00:08:01.060> this<00:08:01.240> is<00:08:01.389> the<00:08:01.630> thing<00:08:02.050> that<00:08:02.080> this<00:08:02.530> defines 00:08:02.969 --> 00:08:02.979 align:start position:0% that this is the thing that this defines 00:08:02.979 --> 00:08:05.640 align:start position:0% that this is the thing that this defines what<00:08:03.910> is<00:08:04.150> what<00:08:04.510> is<00:08:04.630> the<00:08:04.780> intended<00:08:05.080> correct 00:08:05.640 --> 00:08:05.650 align:start position:0% what is what is the intended correct 00:08:05.650 --> 00:08:09.930 align:start position:0% what is what is the intended correct behavior<00:08:06.190> of<00:08:06.820> that<00:08:07.030> smart<00:08:07.240> contracts<00:08:07.800> okay<00:08:08.940> so 00:08:09.930 --> 00:08:09.940 align:start position:0% behavior of that smart contracts okay so 00:08:09.940 --> 00:08:12.740 align:start position:0% behavior of that smart contracts okay so to<00:08:10.030> make<00:08:10.360> this<00:08:10.479> a<00:08:10.540> little<00:08:10.810> bit<00:08:10.990> more<00:08:11.169> country's 00:08:12.740 --> 00:08:12.750 align:start position:0% to make this a little bit more country's 00:08:12.750 --> 00:08:15.420 align:start position:0% to make this a little bit more country's here<00:08:13.750> on<00:08:13.990> the<00:08:14.139> Left<00:08:14.320> imagine<00:08:15.130> you<00:08:15.220> have<00:08:15.400> a 00:08:15.420 --> 00:08:15.430 align:start position:0% here on the Left imagine you have a 00:08:15.430 --> 00:08:18.870 align:start position:0% here on the Left imagine you have a smart<00:08:15.760> contracts<00:08:16.300> that<00:08:16.600> typical<00:08:17.020> year<00:08:17.199> z22<00:08:17.880> so 00:08:18.870 --> 00:08:18.880 align:start position:0% smart contracts that typical year z22 so 00:08:18.880 --> 00:08:20.939 align:start position:0% smart contracts that typical year z22 so you<00:08:18.940> have<00:08:19.180> all<00:08:19.990> these<00:08:20.199> terminals<00:08:20.590> that 00:08:20.939 --> 00:08:20.949 align:start position:0% you have all these terminals that 00:08:20.949 --> 00:08:23.790 align:start position:0% you have all these terminals that balances<00:08:21.490> total<00:08:22.000> supply<00:08:22.300> order<00:08:22.870> a<00:08:23.169> couple<00:08:23.680> of 00:08:23.790 --> 00:08:23.800 align:start position:0% balances total supply order a couple of 00:08:23.800 --> 00:08:25.500 align:start position:0% balances total supply order a couple of functions<00:08:24.160> that<00:08:24.250> allow<00:08:24.520> users<00:08:25.060> to<00:08:25.090> to 00:08:25.500 --> 00:08:25.510 align:start position:0% functions that allow users to to 00:08:25.510 --> 00:08:28.529 align:start position:0% functions that allow users to to transact<00:08:25.990> with<00:08:26.139> the<00:08:26.229> contracts<00:08:26.650> and<00:08:27.120> then<00:08:28.120> the 00:08:28.529 --> 00:08:28.539 align:start position:0% transact with the contracts and then the 00:08:28.539 --> 00:08:30.060 align:start position:0% transact with the contracts and then the functional<00:08:28.900> specification<00:08:29.070> typically 00:08:30.060 --> 00:08:30.070 align:start position:0% functional specification typically 00:08:30.070 --> 00:08:32.550 align:start position:0% functional specification typically consists<00:08:30.430> of<00:08:30.550> requirements<00:08:31.240> such<00:08:31.389> as<00:08:31.560> the 00:08:32.550 --> 00:08:32.560 align:start position:0% consists of requirements such as the 00:08:32.560 --> 00:08:34.589 align:start position:0% consists of requirements such as the seventh<00:08:32.890> caller<00:08:33.099> balances<00:08:33.640> equals<00:08:34.330> the<00:08:34.479> total 00:08:34.589 --> 00:08:34.599 align:start position:0% seventh caller balances equals the total 00:08:34.599 --> 00:08:37.370 align:start position:0% seventh caller balances equals the total supply<00:08:35.520> okay<00:08:36.520> so<00:08:36.580> don't<00:08:36.940> even<00:08:37.120> this 00:08:37.370 --> 00:08:37.380 align:start position:0% supply okay so don't even this 00:08:37.380 --> 00:08:40.469 align:start position:0% supply okay so don't even this specification<00:08:38.380> says<00:08:38.770> that<00:08:39.029> all<00:08:40.029> the<00:08:40.300> tokens 00:08:40.469 --> 00:08:40.479 align:start position:0% specification says that all the tokens 00:08:40.479 --> 00:08:42.240 align:start position:0% specification says that all the tokens are<00:08:40.810> assigned<00:08:41.080> to<00:08:41.169> users<00:08:41.529> somehow<00:08:41.979> there<00:08:42.190> are 00:08:42.240 --> 00:08:42.250 align:start position:0% are assigned to users somehow there are 00:08:42.250 --> 00:08:45.829 align:start position:0% are assigned to users somehow there are no<00:08:42.400> missing<00:08:43.210> tokens<00:08:43.659> on<00:08:43.839> the<00:08:44.229> side<00:08:44.440> to<00:08:44.680> know 00:08:45.829 --> 00:08:45.839 align:start position:0% no missing tokens on the side to know 00:08:45.839 --> 00:08:48.750 align:start position:0% no missing tokens on the side to know about<00:08:46.839> the<00:08:47.050> sign<00:08:47.230> to<00:08:47.410> end<00:08:47.589> user<00:08:47.770> another 00:08:48.750 --> 00:08:48.760 align:start position:0% about the sign to end user another 00:08:48.760 --> 00:08:51.269 align:start position:0% about the sign to end user another common<00:08:49.120> example<00:08:49.240> is<00:08:49.630> that<00:08:49.660> often<00:08:50.589> tokens<00:08:51.130> are 00:08:51.269 --> 00:08:51.279 align:start position:0% common example is that often tokens are 00:08:51.279 --> 00:08:52.829 align:start position:0% common example is that often tokens are immiscible<00:08:51.490> meaning<00:08:52.089> that<00:08:52.180> you<00:08:52.330> can<00:08:52.510> increase 00:08:52.829 --> 00:08:52.839 align:start position:0% immiscible meaning that you can increase 00:08:52.839 --> 00:08:55.650 align:start position:0% immiscible meaning that you can increase initial<00:08:53.529> more<00:08:53.740> tokens<00:08:54.130> and<00:08:54.330> often<00:08:55.330> you<00:08:55.480> wanna 00:08:55.650 --> 00:08:55.660 align:start position:0% initial more tokens and often you wanna 00:08:55.660 --> 00:08:58.620 align:start position:0% initial more tokens and often you wanna show<00:08:55.900> not<00:08:56.050> only<00:08:56.200> certain<00:08:56.680> users<00:08:56.709> can<00:08:57.630> exercise 00:08:58.620 --> 00:08:58.630 align:start position:0% show not only certain users can exercise 00:08:58.630 --> 00:09:00.090 align:start position:0% show not only certain users can exercise its<00:08:58.839> functionality<00:08:59.500> and<00:08:59.650> if<00:08:59.740> you<00:08:59.860> want<00:09:00.010> to 00:09:00.090 --> 00:09:00.100 align:start position:0% its functionality and if you want to 00:09:00.100 --> 00:09:01.320 align:start position:0% its functionality and if you want to make<00:09:00.220> sure<00:09:00.250> that<00:09:00.490> if<00:09:00.700> the<00:09:00.790> total<00:09:00.940> supply 00:09:01.320 --> 00:09:01.330 align:start position:0% make sure that if the total supply 00:09:01.330 --> 00:09:03.540 align:start position:0% make sure that if the total supply increases<00:09:01.839> then<00:09:02.589> that<00:09:02.860> was<00:09:03.040> triggered<00:09:03.400> by<00:09:03.430> a 00:09:03.540 --> 00:09:03.550 align:start position:0% increases then that was triggered by a 00:09:03.550 --> 00:09:05.220 align:start position:0% increases then that was triggered by a transaction<00:09:04.150> issued<00:09:04.450> by<00:09:04.600> the<00:09:04.660> owner<00:09:05.020> of<00:09:05.110> the 00:09:05.220 --> 00:09:05.230 align:start position:0% transaction issued by the owner of the 00:09:05.230 --> 00:09:07.320 align:start position:0% transaction issued by the owner of the contracts<00:09:05.680> okay<00:09:06.370> and<00:09:06.640> then<00:09:06.820> typically<00:09:07.209> you 00:09:07.320 --> 00:09:07.330 align:start position:0% contracts okay and then typically you 00:09:07.330 --> 00:09:08.579 align:start position:0% contracts okay and then typically you would<00:09:07.450> have<00:09:07.630> a<00:09:07.810> huge<00:09:08.080> list<00:09:08.230> of<00:09:08.410> those 00:09:08.579 --> 00:09:08.589 align:start position:0% would have a huge list of those 00:09:08.589 --> 00:09:10.530 align:start position:0% would have a huge list of those requirements<00:09:08.950> that<00:09:09.190> you<00:09:09.339> would<00:09:09.459> have<00:09:09.580> to<00:09:09.760> you 00:09:10.530 --> 00:09:10.540 align:start position:0% requirements that you would have to you 00:09:10.540 --> 00:09:12.030 align:start position:0% requirements that you would have to you would<00:09:10.570> have<00:09:10.720> to<00:09:11.020> check<00:09:11.230> that<00:09:11.260> whatever<00:09:11.890> the 00:09:12.030 --> 00:09:12.040 align:start position:0% would have to check that whatever the 00:09:12.040 --> 00:09:14.100 align:start position:0% would have to check that whatever the implementation<00:09:12.610> of<00:09:12.640> these<00:09:12.730> functions<00:09:13.150> is<00:09:13.360> it 00:09:14.100 --> 00:09:14.110 align:start position:0% implementation of these functions is it 00:09:14.110 --> 00:09:15.300 align:start position:0% implementation of these functions is it is<00:09:14.260> indirect<00:09:14.589> with<00:09:14.740> respect<00:09:15.100> to<00:09:15.190> these 00:09:15.300 --> 00:09:15.310 align:start position:0% is indirect with respect to these 00:09:15.310 --> 00:09:18.269 align:start position:0% is indirect with respect to these functional<00:09:15.820> requirements<00:09:17.040> okay 00:09:18.269 --> 00:09:18.279 align:start position:0% functional requirements okay 00:09:18.279 --> 00:09:20.519 align:start position:0% functional requirements okay so<00:09:18.480> technically<00:09:19.480> how<00:09:19.660> does<00:09:19.930> how<00:09:20.260> do<00:09:20.320> we 00:09:20.519 --> 00:09:20.529 align:start position:0% so technically how does how do we 00:09:20.529 --> 00:09:24.180 align:start position:0% so technically how does how do we actually<00:09:20.709> check<00:09:21.130> that<00:09:22.410> the<00:09:23.410> the<00:09:23.860> code<00:09:24.040> is 00:09:24.180 --> 00:09:24.190 align:start position:0% actually check that the the code is 00:09:24.190 --> 00:09:26.670 align:start position:0% actually check that the the code is correct<00:09:24.370> and<00:09:24.790> they're<00:09:25.779> roughly<00:09:26.020> speaking<00:09:26.290> two 00:09:26.670 --> 00:09:26.680 align:start position:0% correct and they're roughly speaking two 00:09:26.680 --> 00:09:29.880 align:start position:0% correct and they're roughly speaking two steps<00:09:26.950> so<00:09:27.160> the<00:09:27.310> first<00:09:27.550> step<00:09:27.760> is<00:09:28.020> well<00:09:29.020> to 00:09:29.880 --> 00:09:29.890 align:start position:0% steps so the first step is well to 00:09:29.890 --> 00:09:31.829 align:start position:0% steps so the first step is well to essentially<00:09:30.550> transform<00:09:31.060> this<00:09:31.209> English 00:09:31.829 --> 00:09:31.839 align:start position:0% essentially transform this English 00:09:31.839 --> 00:09:34.470 align:start position:0% essentially transform this English description<00:09:32.440> of<00:09:32.560> correct<00:09:33.070> behavior<00:09:33.580> into 00:09:34.470 --> 00:09:34.480 align:start position:0% description of correct behavior into 00:09:34.480 --> 00:09:36.810 align:start position:0% description of correct behavior into something<00:09:34.900> that's<00:09:35.080> to<00:09:35.950> take<00:09:36.190> them<00:09:36.370> down<00:09:36.400> and 00:09:36.810 --> 00:09:36.820 align:start position:0% something that's to take them down and 00:09:36.820 --> 00:09:38.460 align:start position:0% something that's to take them down and to<00:09:37.270> specify<00:09:37.480> them<00:09:37.900> at<00:09:37.990> the<00:09:38.080> level<00:09:38.290> of<00:09:38.320> the 00:09:38.460 --> 00:09:38.470 align:start position:0% to specify them at the level of the 00:09:38.470 --> 00:09:39.810 align:start position:0% to specify them at the level of the source<00:09:38.680> code<00:09:38.920> okay 00:09:39.810 --> 00:09:39.820 align:start position:0% source code okay 00:09:39.820 --> 00:09:42.269 align:start position:0% source code okay so<00:09:40.570> for<00:09:40.870> instance<00:09:40.959> if<00:09:41.470> we<00:09:41.770> take<00:09:41.800> the<00:09:42.100> first 00:09:42.269 --> 00:09:42.279 align:start position:0% so for instance if we take the first 00:09:42.279 --> 00:09:43.530 align:start position:0% so for instance if we take the first requirement<00:09:42.640> that<00:09:42.910> says<00:09:43.060> that<00:09:43.270> the<00:09:43.360> server 00:09:43.530 --> 00:09:43.540 align:start position:0% requirement that says that the server 00:09:43.540 --> 00:09:44.730 align:start position:0% requirement that says that the server balances<00:09:44.080> has<00:09:44.260> to<00:09:44.380> be 00:09:44.730 --> 00:09:44.740 align:start position:0% balances has to be 00:09:44.740 --> 00:09:47.960 align:start position:0% balances has to be power<00:09:45.040> supply<00:09:45.490> then<00:09:46.210> this<00:09:46.810> is<00:09:46.960> written<00:09:47.290> in<00:09:47.620> the 00:09:47.960 --> 00:09:47.970 align:start position:0% power supply then this is written in the 00:09:47.970 --> 00:09:49.830 align:start position:0% power supply then this is written in the specification<00:09:48.970> language<00:09:49.450> that<00:09:49.570> we'll<00:09:49.750> be 00:09:49.830 --> 00:09:49.840 align:start position:0% specification language that we'll be 00:09:49.840 --> 00:09:51.420 align:start position:0% specification language that we'll be using<00:09:49.930> later<00:09:50.260> and<00:09:50.530> exercises<00:09:51.040> of<00:09:51.130> the<00:09:51.250> very 00:09:51.420 --> 00:09:51.430 align:start position:0% using later and exercises of the very 00:09:51.430 --> 00:09:53.490 align:start position:0% using later and exercises of the very excess<00:09:51.700> specification<00:09:52.180> language<00:09:52.690> and<00:09:52.930> this 00:09:53.490 --> 00:09:53.500 align:start position:0% excess specification language and this 00:09:53.500 --> 00:09:54.960 align:start position:0% excess specification language and this is<00:09:53.620> how<00:09:53.800> it<00:09:53.950> will<00:09:54.100> look<00:09:54.160> in<00:09:54.340> the<00:09:54.550> actual 00:09:54.960 --> 00:09:54.970 align:start position:0% is how it will look in the actual 00:09:54.970 --> 00:09:56.640 align:start position:0% is how it will look in the actual specification<00:09:55.570> language<00:09:56.080> so<00:09:56.320> fairly 00:09:56.640 --> 00:09:56.650 align:start position:0% specification language so fairly 00:09:56.650 --> 00:09:59.040 align:start position:0% specification language so fairly intuitive<00:09:57.220> they'll<00:09:57.970> succeed<00:09:58.150> some<00:09:58.600> keywords 00:09:59.040 --> 00:09:59.050 align:start position:0% intuitive they'll succeed some keywords 00:09:59.050 --> 00:10:01.080 align:start position:0% intuitive they'll succeed some keywords onto<00:10:00.010> the<00:10:00.130> mapping<00:10:00.460> that<00:10:00.490> we're<00:10:00.760> trying<00:10:00.910> to 00:10:01.080 --> 00:10:01.090 align:start position:0% onto the mapping that we're trying to 00:10:01.090 --> 00:10:03.030 align:start position:0% onto the mapping that we're trying to sell<00:10:01.330> and<00:10:01.570> then<00:10:01.600> we<00:10:02.230> have<00:10:02.350> a<00:10:02.380> quality<00:10:02.800> with<00:10:02.920> the 00:10:03.030 --> 00:10:03.040 align:start position:0% sell and then we have a quality with the 00:10:03.040 --> 00:10:05.940 align:start position:0% sell and then we have a quality with the focus<00:10:03.340> of<00:10:03.660> okay<00:10:04.660> last<00:10:05.200> that<00:10:05.350> number<00:10:05.680> one<00:10:05.830> is 00:10:05.940 --> 00:10:05.950 align:start position:0% focus of okay last that number one is 00:10:05.950 --> 00:10:07.320 align:start position:0% focus of okay last that number one is inevitable<00:10:06.520> you<00:10:06.670> know<00:10:06.790> you<00:10:06.880> have<00:10:07.030> to<00:10:07.150> be<00:10:07.270> able 00:10:07.320 --> 00:10:07.330 align:start position:0% inevitable you know you have to be able 00:10:07.330 --> 00:10:09.210 align:start position:0% inevitable you know you have to be able to<00:10:07.480> transfer<00:10:07.930> formally<00:10:08.620> state<00:10:08.830> what<00:10:09.100> the 00:10:09.210 --> 00:10:09.220 align:start position:0% to transfer formally state what the 00:10:09.220 --> 00:10:12.630 align:start position:0% to transfer formally state what the property<00:10:09.640> means<00:10:09.820> and<00:10:11.280> once<00:10:12.280> we<00:10:12.490> have 00:10:12.630 --> 00:10:12.640 align:start position:0% property means and once we have 00:10:12.640 --> 00:10:13.860 align:start position:0% property means and once we have formalize<00:10:13.060> it<00:10:13.090> then<00:10:13.330> if<00:10:13.480> we<00:10:13.660> have<00:10:13.840> a 00:10:13.860 --> 00:10:13.870 align:start position:0% formalize it then if we have a 00:10:13.870 --> 00:10:16.080 align:start position:0% formalize it then if we have a particular<00:10:14.200> state<00:10:14.920> of<00:10:14.950> the<00:10:15.310> smart<00:10:15.550> contracts 00:10:16.080 --> 00:10:16.090 align:start position:0% particular state of the smart contracts 00:10:16.090 --> 00:10:18.600 align:start position:0% particular state of the smart contracts then<00:10:16.690> we<00:10:17.050> can<00:10:17.230> check<00:10:17.410> the<00:10:18.220> whether<00:10:18.430> this 00:10:18.600 --> 00:10:18.610 align:start position:0% then we can check the whether this 00:10:18.610 --> 00:10:20.970 align:start position:0% then we can check the whether this property<00:10:19.000> holds<00:10:19.150> or<00:10:19.360> not<00:10:19.390> alright<00:10:20.320> so<00:10:20.770> for 00:10:20.970 --> 00:10:20.980 align:start position:0% property holds or not alright so for 00:10:20.980 --> 00:10:23.460 align:start position:0% property holds or not alright so for instance<00:10:21.250> if<00:10:21.400> we<00:10:21.550> look<00:10:21.580> at<00:10:21.820> a<00:10:21.850> state<00:10:22.300> where<00:10:22.470> we 00:10:23.460 --> 00:10:23.470 align:start position:0% instance if we look at a state where we 00:10:23.470 --> 00:10:27.120 align:start position:0% instance if we look at a state where we have<00:10:23.650> two<00:10:23.920> users<00:10:24.240> having<00:10:25.240> balanced<00:10:26.020> 50h<00:10:26.740> and 00:10:27.120 --> 00:10:27.130 align:start position:0% have two users having balanced 50h and 00:10:27.130 --> 00:10:28.800 align:start position:0% have two users having balanced 50h and we<00:10:27.250> have<00:10:27.340> total<00:10:27.670> supply<00:10:27.940> one<00:10:28.180> other<00:10:28.450> than<00:10:28.660> the 00:10:28.800 --> 00:10:28.810 align:start position:0% we have total supply one other than the 00:10:28.810 --> 00:10:30.600 align:start position:0% we have total supply one other than the property<00:10:29.110> holds<00:10:29.560> with<00:10:29.830> us<00:10:29.980> that's<00:10:30.310> what<00:10:30.520> it 00:10:30.600 --> 00:10:30.610 align:start position:0% property holds with us that's what it 00:10:30.610 --> 00:10:32.820 align:start position:0% property holds with us that's what it says<00:10:30.790> and<00:10:31.300> here<00:10:31.960> would<00:10:32.110> be<00:10:32.170> an<00:10:32.320> example<00:10:32.650> where 00:10:32.820 --> 00:10:32.830 align:start position:0% says and here would be an example where 00:10:32.830 --> 00:10:35.160 align:start position:0% says and here would be an example where the<00:10:33.640> property<00:10:34.030> down<00:10:34.150> the<00:10:34.300> hall<00:10:34.510> because<00:10:34.750> this 00:10:35.160 --> 00:10:35.170 align:start position:0% the property down the hall because this 00:10:35.170 --> 00:10:36.630 align:start position:0% the property down the hall because this sum<00:10:35.320> of<00:10:35.440> these<00:10:35.560> two<00:10:35.740> balances<00:10:36.190> actually 00:10:36.630 --> 00:10:36.640 align:start position:0% sum of these two balances actually 00:10:36.640 --> 00:10:39.000 align:start position:0% sum of these two balances actually exceeds<00:10:36.970> the<00:10:37.150> total<00:10:37.300> balance<00:10:37.890> specified<00:10:38.890> in 00:10:39.000 --> 00:10:39.010 align:start position:0% exceeds the total balance specified in 00:10:39.010 --> 00:10:42.090 align:start position:0% exceeds the total balance specified in the<00:10:39.100> contract<00:10:39.310> et<00:10:40.270> cetera<00:10:40.620> so<00:10:41.620> a<00:10:41.650> step<00:10:41.950> number 00:10:42.090 --> 00:10:42.100 align:start position:0% the contract et cetera so a step number 00:10:42.100 --> 00:10:45.030 align:start position:0% the contract et cetera so a step number one<00:10:42.400> define<00:10:42.850> the<00:10:42.970> property<00:10:43.410> step<00:10:44.410> number<00:10:44.620> two 00:10:45.030 --> 00:10:45.040 align:start position:0% one define the property step number two 00:10:45.040 --> 00:10:46.890 align:start position:0% one define the property step number two is<00:10:45.070> to<00:10:45.220> actually<00:10:45.790> check<00:10:46.030> that<00:10:46.300> this<00:10:46.420> property 00:10:46.890 --> 00:10:46.900 align:start position:0% is to actually check that this property 00:10:46.900 --> 00:10:49.470 align:start position:0% is to actually check that this property holds<00:10:47.290> for<00:10:47.350> all<00:10:48.010> possible<00:10:48.850> states<00:10:49.150> that<00:10:49.330> your 00:10:49.470 --> 00:10:49.480 align:start position:0% holds for all possible states that your 00:10:49.480 --> 00:10:52.620 align:start position:0% holds for all possible states that your contract<00:10:49.900> could<00:10:50.020> reach<00:10:50.250> okay<00:10:51.300> now<00:10:52.300> what<00:10:52.480> does 00:10:52.620 --> 00:10:52.630 align:start position:0% contract could reach okay now what does 00:10:52.630 --> 00:10:55.620 align:start position:0% contract could reach okay now what does this<00:10:52.750> again<00:10:53.020> technically<00:10:53.470> mean<00:10:53.820> well<00:10:54.820> once 00:10:55.620 --> 00:10:55.630 align:start position:0% this again technically mean well once 00:10:55.630 --> 00:10:57.750 align:start position:0% this again technically mean well once you<00:10:55.780> deploy<00:10:56.020> the<00:10:56.230> smart<00:10:56.500> contracts<00:10:57.010> on<00:10:57.220> the 00:10:57.750 --> 00:10:57.760 align:start position:0% you deploy the smart contracts on the 00:10:57.760 --> 00:11:00.450 align:start position:0% you deploy the smart contracts on the blockchain<00:10:57.970> it<00:10:58.840> is<00:10:58.990> always<00:10:59.350> initialized<00:10:59.860> by 00:11:00.450 --> 00:11:00.460 align:start position:0% blockchain it is always initialized by 00:11:00.460 --> 00:11:02.250 align:start position:0% blockchain it is always initialized by the<00:11:00.520> deployment<00:11:01.300> speed<00:11:01.510> so<00:11:01.720> it<00:11:01.810> will<00:11:01.930> end<00:11:02.110> up 00:11:02.250 --> 00:11:02.260 align:start position:0% the deployment speed so it will end up 00:11:02.260 --> 00:11:05.460 align:start position:0% the deployment speed so it will end up in<00:11:02.410> being<00:11:02.710> some<00:11:02.980> specific<00:11:03.640> initial<00:11:04.120> space<00:11:04.470> so 00:11:05.460 --> 00:11:05.470 align:start position:0% in being some specific initial space so 00:11:05.470 --> 00:11:07.320 align:start position:0% in being some specific initial space so that's<00:11:06.310> what<00:11:06.580> these<00:11:06.700> days<00:11:06.880> and<00:11:07.180> you<00:11:07.240> would 00:11:07.320 --> 00:11:07.330 align:start position:0% that's what these days and you would 00:11:07.330 --> 00:11:08.700 align:start position:0% that's what these days and you would have<00:11:07.510> to<00:11:07.630> make<00:11:07.720> sure<00:11:07.960> the<00:11:08.170> property<00:11:08.380> goes 00:11:08.700 --> 00:11:08.710 align:start position:0% have to make sure the property goes 00:11:08.710 --> 00:11:10.980 align:start position:0% have to make sure the property goes there<00:11:09.010> so<00:11:09.520> for<00:11:09.670> instance<00:11:09.880> you<00:11:09.970> deploy<00:11:10.270> and<00:11:10.600> for 00:11:10.980 --> 00:11:10.990 align:start position:0% there so for instance you deploy and for 00:11:10.990 --> 00:11:12.390 align:start position:0% there so for instance you deploy and for that<00:11:11.110> initial<00:11:11.410> state<00:11:11.590> the<00:11:11.740> sum<00:11:11.920> of<00:11:11.950> balances 00:11:12.390 --> 00:11:12.400 align:start position:0% that initial state the sum of balances 00:11:12.400 --> 00:11:13.320 align:start position:0% that initial state the sum of balances would<00:11:12.520> have<00:11:12.670> to<00:11:12.760> be<00:11:12.880> equal<00:11:13.060> to<00:11:13.150> the<00:11:13.210> total 00:11:13.320 --> 00:11:13.330 align:start position:0% would have to be equal to the total 00:11:13.330 --> 00:11:16.950 align:start position:0% would have to be equal to the total supply<00:11:13.630> okay<00:11:14.620> that's<00:11:14.950> one<00:11:15.190> thing<00:11:15.930> the<00:11:16.930> next 00:11:16.950 --> 00:11:16.960 align:start position:0% supply okay that's one thing the next 00:11:16.960 --> 00:11:19.800 align:start position:0% supply okay that's one thing the next thing<00:11:17.260> is<00:11:17.530> that<00:11:17.710> once<00:11:17.980> deployed<00:11:18.460> the<00:11:18.810> users 00:11:19.800 --> 00:11:19.810 align:start position:0% thing is that once deployed the users 00:11:19.810 --> 00:11:21.720 align:start position:0% thing is that once deployed the users could<00:11:20.140> send<00:11:20.380> consent<00:11:21.010> a<00:11:21.070> transaction<00:11:21.580> to<00:11:21.700> the 00:11:21.720 --> 00:11:21.730 align:start position:0% could send consent a transaction to the 00:11:21.730 --> 00:11:23.550 align:start position:0% could send consent a transaction to the smart<00:11:22.060> contracts<00:11:22.570> and<00:11:22.780> each<00:11:23.140> transaction 00:11:23.550 --> 00:11:23.560 align:start position:0% smart contracts and each transaction 00:11:23.560 --> 00:11:26.130 align:start position:0% smart contracts and each transaction would<00:11:23.920> modify<00:11:24.610> the<00:11:24.820> state<00:11:25.420> of<00:11:25.750> the<00:11:25.900> smart 00:11:26.130 --> 00:11:26.140 align:start position:0% would modify the state of the smart 00:11:26.140 --> 00:11:28.440 align:start position:0% would modify the state of the smart contracts<00:11:26.590> so<00:11:27.280> they<00:11:27.310> can<00:11:27.670> for<00:11:27.940> example<00:11:28.000> with 00:11:28.440 --> 00:11:28.450 align:start position:0% contracts so they can for example with 00:11:28.450 --> 00:11:31.590 align:start position:0% contracts so they can for example with submit<00:11:28.840> a<00:11:28.870> mean<00:11:29.080> transaction<00:11:29.910> with<00:11:30.910> different 00:11:31.590 --> 00:11:31.600 align:start position:0% submit a mean transaction with different 00:11:31.600 --> 00:11:33.990 align:start position:0% submit a mean transaction with different you<00:11:32.020> know<00:11:32.140> different<00:11:32.530> policy<00:11:33.040> s<00:11:33.370> arguments 00:11:33.990 --> 00:11:34.000 align:start position:0% you know different policy s arguments 00:11:34.000 --> 00:11:37.020 align:start position:0% you know different policy s arguments and<00:11:34.180> so<00:11:34.780> on<00:11:34.930> and<00:11:35.680> let's<00:11:36.370> be<00:11:36.490> a<00:11:36.520> little<00:11:36.580> bit<00:11:36.850> more 00:11:37.020 --> 00:11:37.030 align:start position:0% and so on and let's be a little bit more 00:11:37.030 --> 00:11:39.120 align:start position:0% and so on and let's be a little bit more precise<00:11:37.420> what<00:11:37.660> these<00:11:37.840> arrows<00:11:38.260> and<00:11:38.290> boxes<00:11:38.920> here 00:11:39.120 --> 00:11:39.130 align:start position:0% precise what these arrows and boxes here 00:11:39.130 --> 00:11:42.720 align:start position:0% precise what these arrows and boxes here represents<00:11:39.870> so<00:11:41.250> what<00:11:42.250> these<00:11:42.400> boxes 00:11:42.720 --> 00:11:42.730 align:start position:0% represents so what these boxes 00:11:42.730 --> 00:11:45.480 align:start position:0% represents so what these boxes represents<00:11:43.420> is<00:11:43.660> the<00:11:44.050> actual<00:11:44.860> state<00:11:45.160> of<00:11:45.370> the 00:11:45.480 --> 00:11:45.490 align:start position:0% represents is the actual state of the 00:11:45.490 --> 00:11:47.360 align:start position:0% represents is the actual state of the contract<00:11:45.910> and<00:11:46.120> the<00:11:46.180> are<00:11:46.420> started 00:11:47.360 --> 00:11:47.370 align:start position:0% contract and the are started 00:11:47.370 --> 00:11:49.640 align:start position:0% contract and the are started I'm<00:11:47.850> triggered<00:11:48.210> by<00:11:48.420> the<00:11:49.020> transactions 00:11:49.640 --> 00:11:49.650 align:start position:0% I'm triggered by the transactions 00:11:49.650 --> 00:11:53.060 align:start position:0% I'm triggered by the transactions submitted<00:11:50.190> by<00:11:50.340> the<00:11:50.400> users<00:11:50.790> and<00:11:51.290> how<00:11:52.290> are<00:11:52.470> how 00:11:53.060 --> 00:11:53.070 align:start position:0% submitted by the users and how are how 00:11:53.070 --> 00:11:55.130 align:start position:0% submitted by the users and how are how is<00:11:53.250> our<00:11:53.610> disposition<00:11:54.270> defined<00:11:54.660> this<00:11:54.990> is 00:11:55.130 --> 00:11:55.140 align:start position:0% is our disposition defined this is 00:11:55.140 --> 00:11:58.430 align:start position:0% is our disposition defined this is defined<00:11:55.500> by<00:11:55.740> the<00:11:55.880> implementation<00:11:56.880> of<00:11:57.420> the<00:11:57.600> of 00:11:58.430 --> 00:11:58.440 align:start position:0% defined by the implementation of the of 00:11:58.440 --> 00:12:00.560 align:start position:0% defined by the implementation of the of the<00:11:58.590> functions<00:11:58.980> in<00:11:59.100> the<00:11:59.130> contracts<00:11:59.640> so<00:12:00.390> for 00:12:00.560 --> 00:12:00.570 align:start position:0% the functions in the contracts so for 00:12:00.570 --> 00:12:03.290 align:start position:0% the functions in the contracts so for example<00:12:00.990> if<00:12:01.050> we<00:12:01.230> have<00:12:01.410> here<00:12:01.860> we<00:12:02.820> start<00:12:03.030> from<00:12:03.180> a 00:12:03.290 --> 00:12:03.300 align:start position:0% example if we have here we start from a 00:12:03.300 --> 00:12:05.660 align:start position:0% example if we have here we start from a state<00:12:03.510> where<00:12:03.720> total<00:12:04.650> supplies<00:12:05.130> of<00:12:05.310> hundreds 00:12:05.660 --> 00:12:05.670 align:start position:0% state where total supplies of hundreds 00:12:05.670 --> 00:12:08.570 align:start position:0% state where total supplies of hundreds we<00:12:06.450> have<00:12:06.570> an<00:12:06.660> older<00:12:07.020> user<00:12:07.260> with<00:12:08.190> address 00:12:08.570 --> 00:12:08.580 align:start position:0% we have an older user with address 00:12:08.580 --> 00:12:10.790 align:start position:0% we have an older user with address extend<00:12:09.240> and<00:12:09.570> then<00:12:09.630> we<00:12:09.870> have<00:12:09.990> two<00:12:10.230> users<00:12:10.560> with 00:12:10.790 --> 00:12:10.800 align:start position:0% extend and then we have two users with 00:12:10.800 --> 00:12:14.690 align:start position:0% extend and then we have two users with balances<00:12:11.400> 50<00:12:12.240> tokens<00:12:12.540> each<00:12:12.990> and<00:12:13.320> then<00:12:14.160> main 00:12:14.690 --> 00:12:14.700 align:start position:0% balances 50 tokens each and then main 00:12:14.700 --> 00:12:16.250 align:start position:0% balances 50 tokens each and then main function<00:12:15.090> is<00:12:15.180> defined<00:12:15.300> such<00:12:15.750> that<00:12:15.780> it<00:12:16.080> would 00:12:16.250 --> 00:12:16.260 align:start position:0% function is defined such that it would 00:12:16.260 --> 00:12:18.650 align:start position:0% function is defined such that it would increment<00:12:16.500> the<00:12:16.890> total<00:12:17.220> supply<00:12:17.370> by<00:12:17.940> the<00:12:18.000> number 00:12:18.650 --> 00:12:18.660 align:start position:0% increment the total supply by the number 00:12:18.660 --> 00:12:21.530 align:start position:0% increment the total supply by the number of<00:12:18.690> dollars<00:12:18.930> water<00:12:19.440> two<00:12:20.010> means<00:12:20.220> and<00:12:20.550> then<00:12:21.360> it 00:12:21.530 --> 00:12:21.540 align:start position:0% of dollars water two means and then it 00:12:21.540 --> 00:12:23.750 align:start position:0% of dollars water two means and then it would<00:12:21.750> assign<00:12:22.020> the<00:12:22.230> new<00:12:22.350> totals<00:12:22.800> to<00:12:23.250> the<00:12:23.400> to 00:12:23.750 --> 00:12:23.760 align:start position:0% would assign the new totals to the to 00:12:23.760 --> 00:12:27.170 align:start position:0% would assign the new totals to the to the<00:12:23.850> owner<00:12:24.150> of<00:12:25.140> the<00:12:25.410> contract<00:12:25.800> so<00:12:26.610> here<00:12:26.880> if<00:12:27.150> we 00:12:27.170 --> 00:12:27.180 align:start position:0% the owner of the contract so here if we 00:12:27.180 --> 00:12:30.440 align:start position:0% the owner of the contract so here if we have<00:12:27.510> this<00:12:27.960> means<00:12:28.400> one<00:12:29.400> fiblets<00:12:29.880> tokens 00:12:30.440 --> 00:12:30.450 align:start position:0% have this means one fiblets tokens 00:12:30.450 --> 00:12:32.990 align:start position:0% have this means one fiblets tokens issued<00:12:31.260> by<00:12:31.440> the<00:12:31.500> user<00:12:31.740> base<00:12:32.430> bill<00:12:32.640> the<00:12:32.730> normal 00:12:32.990 --> 00:12:33.000 align:start position:0% issued by the user base bill the normal 00:12:33.000 --> 00:12:34.610 align:start position:0% issued by the user base bill the normal supply<00:12:33.120> will<00:12:33.450> be<00:12:33.480> incremented<00:12:33.840> as<00:12:34.200> defined<00:12:34.530> by 00:12:34.610 --> 00:12:34.620 align:start position:0% supply will be incremented as defined by 00:12:34.620 --> 00:12:36.380 align:start position:0% supply will be incremented as defined by the<00:12:34.740> function<00:12:34.920> and<00:12:35.310> then<00:12:35.580> the<00:12:35.760> balance<00:12:36.090> of<00:12:36.270> the 00:12:36.380 --> 00:12:36.390 align:start position:0% the function and then the balance of the 00:12:36.390 --> 00:12:39.020 align:start position:0% the function and then the balance of the owner<00:12:36.630> who<00:12:37.290> has<00:12:37.410> addresses<00:12:38.040> euro<00:12:38.250> extent 00:12:39.020 --> 00:12:39.030 align:start position:0% owner who has addresses euro extent 00:12:39.030 --> 00:12:41.780 align:start position:0% owner who has addresses euro extent would<00:12:39.570> be<00:12:39.750> incremented<00:12:39.990> from<00:12:40.500> 52<00:12:41.040> also<00:12:41.310> number 00:12:41.780 --> 00:12:41.790 align:start position:0% would be incremented from 52 also number 00:12:41.790 --> 00:12:43.010 align:start position:0% would be incremented from 52 also number because<00:12:42.060> that's<00:12:42.180> how<00:12:42.390> many<00:12:42.450> additional 00:12:43.010 --> 00:12:43.020 align:start position:0% because that's how many additional 00:12:43.020 --> 00:12:46.040 align:start position:0% because that's how many additional conservation<00:12:43.880> so<00:12:44.880> that's<00:12:45.360> what<00:12:45.540> this<00:12:45.690> allows 00:12:46.040 --> 00:12:46.050 align:start position:0% conservation so that's what this allows 00:12:46.050 --> 00:12:50.060 align:start position:0% conservation so that's what this allows you<00:12:46.260> me<00:12:47.390> alright<00:12:48.390> so<00:12:48.870> here<00:12:49.290> comes<00:12:49.590> immediately 00:12:50.060 --> 00:12:50.070 align:start position:0% you me alright so here comes immediately 00:12:50.070 --> 00:12:52.220 align:start position:0% you me alright so here comes immediately the<00:12:50.310> first<00:12:50.490> immediate<00:12:51.480> challenge<00:12:51.960> when<00:12:52.140> you 00:12:52.220 --> 00:12:52.230 align:start position:0% the first immediate challenge when you 00:12:52.230 --> 00:12:54.320 align:start position:0% the first immediate challenge when you talk<00:12:52.410> about<00:12:52.440> functional<00:12:53.070> correctness<00:12:53.330> is 00:12:54.320 --> 00:12:54.330 align:start position:0% talk about functional correctness is 00:12:54.330 --> 00:12:56.600 align:start position:0% talk about functional correctness is that<00:12:54.600> even<00:12:55.080> if<00:12:55.200> we<00:12:55.230> want<00:12:55.530> to<00:12:55.560> consider<00:12:55.920> whether 00:12:56.600 --> 00:12:56.610 align:start position:0% that even if we want to consider whether 00:12:56.610 --> 00:12:58.760 align:start position:0% that even if we want to consider whether the<00:12:56.850> property<00:12:57.240> will<00:12:57.480> hold<00:12:57.720> after<00:12:58.020> one<00:12:58.440> single 00:12:58.760 --> 00:12:58.770 align:start position:0% the property will hold after one single 00:12:58.770 --> 00:13:01.160 align:start position:0% the property will hold after one single transaction<00:12:59.310> after<00:13:00.180> the<00:13:00.450> first<00:13:00.660> transactions 00:13:01.160 --> 00:13:01.170 align:start position:0% transaction after the first transactions 00:13:01.170 --> 00:13:03.080 align:start position:0% transaction after the first transactions entered<00:13:01.320> a<00:13:01.500> contract<00:13:01.800> that<00:13:02.430> already<00:13:02.850> gives 00:13:03.080 --> 00:13:03.090 align:start position:0% entered a contract that already gives 00:13:03.090 --> 00:13:04.940 align:start position:0% entered a contract that already gives you<00:13:03.270> so<00:13:03.720> many<00:13:03.900> different<00:13:04.020> ones<00:13:04.410> actually<00:13:04.650> to 00:13:04.940 --> 00:13:04.950 align:start position:0% you so many different ones actually to 00:13:04.950 --> 00:13:07.850 align:start position:0% you so many different ones actually to put<00:13:05.100> that<00:13:05.820> would<00:13:06.240> be<00:13:06.390> the<00:13:07.080> test<00:13:07.470> to<00:13:07.620> be 00:13:07.850 --> 00:13:07.860 align:start position:0% put that would be the test to be 00:13:07.860 --> 00:13:10.310 align:start position:0% put that would be the test to be accounted<00:13:08.310> for<00:13:08.340> that<00:13:09.210> it<00:13:09.360> becomes<00:13:09.720> infeasible 00:13:10.310 --> 00:13:10.320 align:start position:0% accounted for that it becomes infeasible 00:13:10.320 --> 00:13:12.770 align:start position:0% accounted for that it becomes infeasible to<00:13:10.680> put<00:13:11.070> foresee<00:13:11.520> it's<00:13:11.970> not<00:13:12.150> possible<00:13:12.600> to 00:13:12.770 --> 00:13:12.780 align:start position:0% to put foresee it's not possible to 00:13:12.780 --> 00:13:14.210 align:start position:0% to put foresee it's not possible to another<00:13:12.990> these<00:13:13.200> transactions<00:13:13.770> into<00:13:13.920> actually 00:13:14.210 --> 00:13:14.220 align:start position:0% another these transactions into actually 00:13:14.220 --> 00:13:16.370 align:start position:0% another these transactions into actually check<00:13:14.460> them<00:13:14.640> in<00:13:15.120> all<00:13:15.300> these<00:13:15.450> things<00:13:15.720> the 00:13:16.370 --> 00:13:16.380 align:start position:0% check them in all these things the 00:13:16.380 --> 00:13:18.800 align:start position:0% check them in all these things the property<00:13:16.830> will<00:13:16.950> always<00:13:17.220> cause<00:13:17.460> and<00:13:18.090> challenge 00:13:18.800 --> 00:13:18.810 align:start position:0% property will always cause and challenge 00:13:18.810 --> 00:13:21.890 align:start position:0% property will always cause and challenge number<00:13:18.960> one<00:13:19.170> and<00:13:20.210> we<00:13:21.210> cannot<00:13:21.420> stop<00:13:21.690> here 00:13:21.890 --> 00:13:21.900 align:start position:0% number one and we cannot stop here 00:13:21.900 --> 00:13:24.170 align:start position:0% number one and we cannot stop here because<00:13:22.320> after<00:13:23.280> the<00:13:23.370> first<00:13:23.580> transaction<00:13:23.940> is 00:13:24.170 --> 00:13:24.180 align:start position:0% because after the first transaction is 00:13:24.180 --> 00:13:25.610 align:start position:0% because after the first transaction is the<00:13:24.270> user<00:13:24.450> would<00:13:24.660> submit<00:13:24.900> second<00:13:25.320> and<00:13:25.440> third 00:13:25.610 --> 00:13:25.620 align:start position:0% the user would submit second and third 00:13:25.620 --> 00:13:27.740 align:start position:0% the user would submit second and third and<00:13:25.830> so<00:13:26.010> on<00:13:26.040> transaction<00:13:26.640> and<00:13:26.940> in<00:13:27.540> fact 00:13:27.740 --> 00:13:27.750 align:start position:0% and so on transaction and in fact 00:13:27.750 --> 00:13:30.500 align:start position:0% and so on transaction and in fact there's<00:13:28.020> not<00:13:28.410> lots<00:13:29.010> of<00:13:29.130> predefined<00:13:29.760> bounds<00:13:30.270> on 00:13:30.500 --> 00:13:30.510 align:start position:0% there's not lots of predefined bounds on 00:13:30.510 --> 00:13:32.900 align:start position:0% there's not lots of predefined bounds on how<00:13:30.750> many<00:13:31.040> transactions<00:13:32.040> this<00:13:32.430> contract 00:13:32.900 --> 00:13:32.910 align:start position:0% how many transactions this contract 00:13:32.910 --> 00:13:35.470 align:start position:0% how many transactions this contract would<00:13:33.090> process<00:13:33.960> in<00:13:34.320> his<00:13:34.440> lifetime<00:13:34.680> so 00:13:35.470 --> 00:13:35.480 align:start position:0% would process in his lifetime so 00:13:35.480 --> 00:13:38.199 align:start position:0% would process in his lifetime so to<00:13:35.660> consider<00:13:35.959> number<00:13:36.829> of<00:13:37.010> transactions<00:13:37.519> you 00:13:38.199 --> 00:13:38.209 align:start position:0% to consider number of transactions you 00:13:38.209 --> 00:13:40.210 align:start position:0% to consider number of transactions you were<00:13:38.449> to<00:13:38.630> formally<00:13:39.529> verify<00:13:39.920> that<00:13:40.070> this 00:13:40.210 --> 00:13:40.220 align:start position:0% were to formally verify that this 00:13:40.220 --> 00:13:43.180 align:start position:0% were to formally verify that this property<00:13:40.670> would<00:13:40.760> always<00:13:41.000> hold<00:13:41.709> their<00:13:42.709> two 00:13:43.180 --> 00:13:43.190 align:start position:0% property would always hold their two 00:13:43.190 --> 00:13:47.290 align:start position:0% property would always hold their two fundamental<00:13:43.790> Chinese<00:13:44.149> heroes<00:13:45.760> all<00:13:46.760> right<00:13:46.910> so 00:13:47.290 --> 00:13:47.300 align:start position:0% fundamental Chinese heroes all right so 00:13:47.300 --> 00:13:49.300 align:start position:0% fundamental Chinese heroes all right so let's<00:13:47.600> very<00:13:47.990> quickly<00:13:48.199> go<00:13:48.440> over<00:13:48.470> what<00:13:49.040> are 00:13:49.300 --> 00:13:49.310 align:start position:0% let's very quickly go over what are 00:13:49.310 --> 00:13:50.829 align:start position:0% let's very quickly go over what are different<00:13:49.639> techniques<00:13:49.970> that<00:13:50.300> could<00:13:50.600> be<00:13:50.660> used 00:13:50.829 --> 00:13:50.839 align:start position:0% different techniques that could be used 00:13:50.839 --> 00:13:54.160 align:start position:0% different techniques that could be used to<00:13:51.850> address<00:13:52.850> this<00:13:53.240> problem<00:13:53.420> of<00:13:53.720> taking<00:13:54.079> these 00:13:54.160 --> 00:13:54.170 align:start position:0% to address this problem of taking these 00:13:54.170 --> 00:13:55.870 align:start position:0% to address this problem of taking these formal<00:13:54.529> properties<00:13:55.010> and<00:13:55.190> how<00:13:55.339> they<00:13:55.519> different 00:13:55.870 --> 00:13:55.880 align:start position:0% formal properties and how they different 00:13:55.880 --> 00:14:00.730 align:start position:0% formal properties and how they different types<00:13:56.060> of<00:13:56.209> guarantees<00:13:56.860> and<00:13:58.720> so<00:13:59.720> I<00:13:59.990> ordered<00:14:00.649> a 00:14:00.730 --> 00:14:00.740 align:start position:0% types of guarantees and so I ordered a 00:14:00.740 --> 00:14:02.829 align:start position:0% types of guarantees and so I ordered a based<00:14:00.920> on<00:14:01.160> reliability<00:14:01.579> so<00:14:02.029> starting<00:14:02.750> from 00:14:02.829 --> 00:14:02.839 align:start position:0% based on reliability so starting from 00:14:02.839 --> 00:14:05.199 align:start position:0% based on reliability so starting from least<00:14:03.139> reliable<00:14:03.410> going<00:14:03.889> towards<00:14:04.190> more<00:14:04.579> more 00:14:05.199 --> 00:14:05.209 align:start position:0% least reliable going towards more more 00:14:05.209 --> 00:14:06.160 align:start position:0% least reliable going towards more more reliable<00:14:05.600> techniques 00:14:06.160 --> 00:14:06.170 align:start position:0% reliable techniques 00:14:06.170 --> 00:14:08.920 align:start position:0% reliable techniques well<00:14:07.070> the<00:14:07.699> bottom<00:14:07.850> we<00:14:08.060> have<00:14:08.089> the<00:14:08.300> menu<00:14:08.570> reviews 00:14:08.920 --> 00:14:08.930 align:start position:0% well the bottom we have the menu reviews 00:14:08.930 --> 00:14:10.870 align:start position:0% well the bottom we have the menu reviews always<00:14:09.440> the<00:14:09.529> human<00:14:09.800> can<00:14:09.949> look<00:14:10.459> at<00:14:10.579> the<00:14:10.639> codes 00:14:10.870 --> 00:14:10.880 align:start position:0% always the human can look at the codes 00:14:10.880 --> 00:14:12.910 align:start position:0% always the human can look at the codes understand<00:14:11.600> what<00:14:11.750> it<00:14:11.839> does<00:14:11.870> and<00:14:12.410> try<00:14:12.589> to<00:14:12.649> find 00:14:12.910 --> 00:14:12.920 align:start position:0% understand what it does and try to find 00:14:12.920 --> 00:14:15.340 align:start position:0% understand what it does and try to find violations<00:14:13.329> so<00:14:14.329> this<00:14:14.600> is<00:14:14.720> a<00:14:14.870> successive 00:14:15.340 --> 00:14:15.350 align:start position:0% violations so this is a successive 00:14:15.350 --> 00:14:18.280 align:start position:0% violations so this is a successive penetration<00:14:16.010> testing<00:14:16.690> property<00:14:17.690> try<00:14:17.899> to<00:14:17.959> try 00:14:18.280 --> 00:14:18.290 align:start position:0% penetration testing property try to try 00:14:18.290 --> 00:14:21.040 align:start position:0% penetration testing property try to try to<00:14:18.320> crack<00:14:19.100> the<00:14:19.220> contracts<00:14:19.639> and<00:14:20.329> the 00:14:21.040 --> 00:14:21.050 align:start position:0% to crack the contracts and the 00:14:21.050 --> 00:14:23.439 align:start position:0% to crack the contracts and the disadvantage<00:14:22.010> here<00:14:22.220> fairly<00:14:22.910> well<00:14:23.060> and<00:14:23.149> also 00:14:23.439 --> 00:14:23.449 align:start position:0% disadvantage here fairly well and also 00:14:23.449 --> 00:14:25.810 align:start position:0% disadvantage here fairly well and also it's<00:14:23.600> a<00:14:23.750> time<00:14:23.959> consuming<00:14:24.370> problem<00:14:25.370> even<00:14:25.730> if 00:14:25.810 --> 00:14:25.820 align:start position:0% it's a time consuming problem even if 00:14:25.820 --> 00:14:27.189 align:start position:0% it's a time consuming problem even if you<00:14:25.910> have<00:14:26.060> especially<00:14:26.510> we<00:14:26.899> have<00:14:27.019> big 00:14:27.189 --> 00:14:27.199 align:start position:0% you have especially we have big 00:14:27.199 --> 00:14:28.990 align:start position:0% you have especially we have big contracts<00:14:27.680> that<00:14:27.829> would<00:14:28.459> take<00:14:28.670> a<00:14:28.820> while<00:14:28.940> for 00:14:28.990 --> 00:14:29.000 align:start position:0% contracts that would take a while for 00:14:29.000 --> 00:14:32.139 align:start position:0% contracts that would take a while for for<00:14:29.870> the<00:14:30.279> security<00:14:31.279> expert<00:14:31.670> to<00:14:31.790> understand 00:14:32.139 --> 00:14:32.149 align:start position:0% for the security expert to understand 00:14:32.149 --> 00:14:34.420 align:start position:0% for the security expert to understand exactly<00:14:32.329> how<00:14:32.660> these<00:14:32.839> things<00:14:33.050> how<00:14:33.350> of<00:14:34.279> the 00:14:34.420 --> 00:14:34.430 align:start position:0% exactly how these things how of the 00:14:34.430 --> 00:14:37.300 align:start position:0% exactly how these things how of the functionality<00:14:35.029> of<00:14:35.089> the<00:14:35.209> contract<00:14:35.540> is<00:14:36.310> then 00:14:37.300 --> 00:14:37.310 align:start position:0% functionality of the contract is then 00:14:37.310 --> 00:14:41.019 align:start position:0% functionality of the contract is then let's<00:14:37.760> move<00:14:37.910> over<00:14:38.180> to<00:14:38.449> model<00:14:39.019> 26<00:14:39.709> so<00:14:40.160> next 00:14:41.019 --> 00:14:41.029 align:start position:0% let's move over to model 26 so next 00:14:41.029 --> 00:14:42.639 align:start position:0% let's move over to model 26 so next level<00:14:41.300> would<00:14:41.420> be<00:14:41.600> to<00:14:41.870> do<00:14:42.019> some<00:14:42.290> form<00:14:42.560> of 00:14:42.639 --> 00:14:42.649 align:start position:0% level would be to do some form of 00:14:42.649 --> 00:14:46.689 align:start position:0% level would be to do some form of automated<00:14:43.250> testing<00:14:43.399> and<00:14:43.880> then<00:14:44.600> primarily<00:14:45.699> in 00:14:46.689 --> 00:14:46.699 align:start position:0% automated testing and then primarily in 00:14:46.699 --> 00:14:48.579 align:start position:0% automated testing and then primarily in general<00:14:47.149> for<00:14:47.389> software<00:14:47.690> but<00:14:47.899> also<00:14:48.079> in<00:14:48.440> the 00:14:48.579 --> 00:14:48.589 align:start position:0% general for software but also in the 00:14:48.589 --> 00:14:50.379 align:start position:0% general for software but also in the space<00:14:48.800> of<00:14:48.829> contracts<00:14:49.310> two<00:14:49.850> techniques<00:14:50.180> for 00:14:50.379 --> 00:14:50.389 align:start position:0% space of contracts two techniques for 00:14:50.389 --> 00:14:51.970 align:start position:0% space of contracts two techniques for testing<00:14:50.839> contract<00:14:51.230> so<00:14:51.319> one<00:14:51.470> is<00:14:51.560> based<00:14:51.800> on 00:14:51.970 --> 00:14:51.980 align:start position:0% testing contract so one is based on 00:14:51.980 --> 00:14:55.059 align:start position:0% testing contract so one is based on fuzzing<00:14:52.699> and<00:14:52.850> the<00:14:53.839> second<00:14:54.230> major<00:14:54.589> technique 00:14:55.059 --> 00:14:55.069 align:start position:0% fuzzing and the second major technique 00:14:55.069 --> 00:14:59.019 align:start position:0% fuzzing and the second major technique is<00:14:55.310> to<00:14:56.300> special<00:14:56.870> support<00:14:57.199> execution<00:14:58.000> so<00:14:59.000> let's 00:14:59.019 --> 00:14:59.029 align:start position:0% is to special support execution so let's 00:14:59.029 --> 00:15:02.139 align:start position:0% is to special support execution so let's briefly<00:14:59.750> see<00:15:00.050> what<00:15:00.800> this<00:15:01.160> what<00:15:01.790> what<00:15:02.000> these 00:15:02.139 --> 00:15:02.149 align:start position:0% briefly see what this what what these 00:15:02.149 --> 00:15:04.449 align:start position:0% briefly see what this what what these techniques<00:15:02.540> would<00:15:02.870> do<00:15:03.139> to<00:15:03.800> this<00:15:03.920> problem<00:15:04.339> of 00:15:04.449 --> 00:15:04.459 align:start position:0% techniques would do to this problem of 00:15:04.459 --> 00:15:07.990 align:start position:0% techniques would do to this problem of objective<00:15:05.360> functional<00:15:05.720> practice<00:15:06.110> and<00:15:07.000> so 00:15:07.990 --> 00:15:08.000 align:start position:0% objective functional practice and so 00:15:08.000 --> 00:15:10.389 align:start position:0% objective functional practice and so starting<00:15:08.300> for<00:15:08.480> fun<00:15:08.660> with<00:15:08.810> fuzzy<00:15:09.399> here's 00:15:10.389 --> 00:15:10.399 align:start position:0% starting for fun with fuzzy here's 00:15:10.399 --> 00:15:12.519 align:start position:0% starting for fun with fuzzy here's basically<00:15:10.579> what's<00:15:10.970> happening<00:15:11.300> so<00:15:12.110> fuzzing<00:15:12.440> is 00:15:12.519 --> 00:15:12.529 align:start position:0% basically what's happening so fuzzing is 00:15:12.529 --> 00:15:16.059 align:start position:0% basically what's happening so fuzzing is a<00:15:12.800> testing<00:15:13.190> technique<00:15:13.519> or<00:15:13.850> a<00:15:14.860> puzzler<00:15:15.860> would 00:15:16.059 --> 00:15:16.069 align:start position:0% a testing technique or a puzzler would 00:15:16.069 --> 00:15:19.300 align:start position:0% a testing technique or a puzzler would generate<00:15:16.459> random<00:15:17.000> transactions<00:15:18.069> and<00:15:19.069> then<00:15:19.220> it 00:15:19.300 --> 00:15:19.310 align:start position:0% generate random transactions and then it 00:15:19.310 --> 00:15:20.800 align:start position:0% generate random transactions and then it will<00:15:19.430> execute<00:15:19.639> the<00:15:20.000> transaction<00:15:20.209> some<00:15:20.690> of<00:15:20.750> the 00:15:20.800 --> 00:15:20.810 align:start position:0% will execute the transaction some of the 00:15:20.810 --> 00:15:23.889 align:start position:0% will execute the transaction some of the contracts<00:15:21.290> and<00:15:21.639> by<00:15:22.639> doing<00:15:22.850> so<00:15:22.970> the<00:15:23.660> buzzer 00:15:23.889 --> 00:15:23.899 align:start position:0% contracts and by doing so the buzzer 00:15:23.899 --> 00:15:26.650 align:start position:0% contracts and by doing so the buzzer would<00:15:24.319> observe<00:15:25.209> different<00:15:26.209> states<00:15:26.449> of<00:15:26.540> the 00:15:26.650 --> 00:15:26.660 align:start position:0% would observe different states of the 00:15:26.660 --> 00:15:29.439 align:start position:0% would observe different states of the smart<00:15:26.899> contracts<00:15:27.350> all<00:15:28.220> right<00:15:28.399> and<00:15:28.850> by<00:15:29.389> doing 00:15:29.439 --> 00:15:29.449 align:start position:0% smart contracts all right and by doing 00:15:29.449 --> 00:15:31.870 align:start position:0% smart contracts all right and by doing so<00:15:29.720> we<00:15:30.319> can<00:15:30.529> for<00:15:30.889> all<00:15:30.920> the<00:15:31.250> states<00:15:31.519> that<00:15:31.670> have 00:15:31.870 --> 00:15:31.880 align:start position:0% so we can for all the states that have 00:15:31.880 --> 00:15:33.490 align:start position:0% so we can for all the states that have been<00:15:31.910> observed<00:15:32.389> after<00:15:32.690> posting<00:15:33.290> these 00:15:33.490 --> 00:15:33.500 align:start position:0% been observed after posting these 00:15:33.500 --> 00:15:36.100 align:start position:0% been observed after posting these transactions<00:15:34.130> that<00:15:34.310> we<00:15:34.490> generate<00:15:34.930> we<00:15:35.930> could 00:15:36.100 --> 00:15:36.110 align:start position:0% transactions that we generate we could 00:15:36.110 --> 00:15:37.389 align:start position:0% transactions that we generate we could check<00:15:36.380> whether<00:15:36.620> the<00:15:36.769> property<00:15:37.100> is<00:15:37.190> violated 00:15:37.389 --> 00:15:37.399 align:start position:0% check whether the property is violated 00:15:37.399 --> 00:15:40.840 align:start position:0% check whether the property is violated or<00:15:37.819> not<00:15:38.110> if<00:15:39.110> it<00:15:39.290> happens<00:15:39.680> as<00:15:39.860> we<00:15:40.190> reach<00:15:40.370> a<00:15:40.519> state 00:15:40.840 --> 00:15:40.850 align:start position:0% or not if it happens as we reach a state 00:15:40.850 --> 00:15:43.140 align:start position:0% or not if it happens as we reach a state where<00:15:40.880> you<00:15:41.690> get<00:15:41.839> a<00:15:41.870> violation 00:15:43.140 --> 00:15:43.150 align:start position:0% where you get a violation 00:15:43.150 --> 00:15:44.730 align:start position:0% where you get a violation then<00:15:43.330> the<00:15:43.600> father<00:15:43.779> would<00:15:43.990> also<00:15:44.140> return<00:15:44.380> that 00:15:44.730 --> 00:15:44.740 align:start position:0% then the father would also return that 00:15:44.740 --> 00:15:46.290 align:start position:0% then the father would also return that sequence<00:15:45.190> of<00:15:45.279> transaction<00:15:45.820> that<00:15:45.940> triggered 00:15:46.290 --> 00:15:46.300 align:start position:0% sequence of transaction that triggered 00:15:46.300 --> 00:15:47.910 align:start position:0% sequence of transaction that triggered the<00:15:46.420> violation<00:15:46.930> and<00:15:47.110> the<00:15:47.230> developer<00:15:47.770> could 00:15:47.910 --> 00:15:47.920 align:start position:0% the violation and the developer could 00:15:47.920 --> 00:15:50.670 align:start position:0% the violation and the developer could see<00:15:48.430> you<00:15:49.390> know<00:15:49.510> reproduce<00:15:49.960> the<00:15:50.170> buck<00:15:50.350> and<00:15:50.560> try 00:15:50.670 --> 00:15:50.680 align:start position:0% see you know reproduce the buck and try 00:15:50.680 --> 00:15:53.370 align:start position:0% see you know reproduce the buck and try to<00:15:50.770> fix<00:15:51.010> it<00:15:51.779> there<00:15:52.779> are<00:15:52.839> many<00:15:52.990> many<00:15:53.200> fathers 00:15:53.370 --> 00:15:53.380 align:start position:0% to fix it there are many many fathers 00:15:53.380 --> 00:15:55.560 align:start position:0% to fix it there are many many fathers have<00:15:53.740> been<00:15:53.890> deployed<00:15:54.279> that<00:15:55.000> are<00:15:55.390> available 00:15:55.560 --> 00:15:55.570 align:start position:0% have been deployed that are available 00:15:55.570 --> 00:15:57.780 align:start position:0% have been deployed that are available online<00:15:55.960> to<00:15:56.260> do<00:15:56.380> exactly<00:15:56.710> this<00:15:56.890> this<00:15:57.339> thing 00:15:57.780 --> 00:15:57.790 align:start position:0% online to do exactly this this thing 00:15:57.790 --> 00:15:59.340 align:start position:0% online to do exactly this this thing the<00:15:58.150> Challenger<00:15:58.600> typical<00:15:59.020> is<00:15:59.110> how<00:15:59.290> to 00:15:59.340 --> 00:15:59.350 align:start position:0% the Challenger typical is how to 00:15:59.350 --> 00:16:01.800 align:start position:0% the Challenger typical is how to generate<00:16:00.089> transactions<00:16:01.089> in<00:16:01.210> a<00:16:01.300> smart<00:16:01.570> way<00:16:01.690> so 00:16:01.800 --> 00:16:01.810 align:start position:0% generate transactions in a smart way so 00:16:01.810 --> 00:16:04.170 align:start position:0% generate transactions in a smart way so you<00:16:02.020> get<00:16:02.200> verified<00:16:02.710> coverage<00:16:03.160> over<00:16:03.460> at<00:16:03.940> least 00:16:04.170 --> 00:16:04.180 align:start position:0% you get verified coverage over at least 00:16:04.180 --> 00:16:06.090 align:start position:0% you get verified coverage over at least a<00:16:04.450> very<00:16:04.750> high<00:16:04.870> code<00:16:05.110> coverage<00:16:05.470> over<00:16:05.830> the 00:16:06.090 --> 00:16:06.100 align:start position:0% a very high code coverage over the 00:16:06.100 --> 00:16:07.650 align:start position:0% a very high code coverage over the contract<00:16:06.790> which<00:16:06.940> is<00:16:06.970> already<00:16:07.420> pretty 00:16:07.650 --> 00:16:07.660 align:start position:0% contract which is already pretty 00:16:07.660 --> 00:16:09.360 align:start position:0% contract which is already pretty challenging<00:16:07.960> in<00:16:08.350> contracts<00:16:08.830> which<00:16:08.980> tend<00:16:09.339> to 00:16:09.360 --> 00:16:09.370 align:start position:0% challenging in contracts which tend to 00:16:09.370 --> 00:16:11.880 align:start position:0% challenging in contracts which tend to be<00:16:09.460> very<00:16:09.610> stateful<00:16:10.450> and<00:16:11.080> complex 00:16:11.880 --> 00:16:11.890 align:start position:0% be very stateful and complex 00:16:11.890 --> 00:16:13.530 align:start position:0% be very stateful and complex preconditions<00:16:12.580> of<00:16:12.700> the<00:16:12.790> transactions<00:16:13.330> and<00:16:13.480> so 00:16:13.530 --> 00:16:13.540 align:start position:0% preconditions of the transactions and so 00:16:13.540 --> 00:16:15.900 align:start position:0% preconditions of the transactions and so on<00:16:13.750> so<00:16:14.650> what's<00:16:14.830> funny<00:16:14.980> was<00:16:15.220> no<00:16:15.310> idiot<00:16:15.730> would 00:16:15.900 --> 00:16:15.910 align:start position:0% on so what's funny was no idiot would 00:16:15.910 --> 00:16:17.280 align:start position:0% on so what's funny was no idiot would not<00:16:16.060> give<00:16:16.270> you<00:16:16.330> this<00:16:16.420> full<00:16:16.690> guarantee<00:16:16.870> that's 00:16:17.280 --> 00:16:17.290 align:start position:0% not give you this full guarantee that's 00:16:17.290 --> 00:16:19.590 align:start position:0% not give you this full guarantee that's why<00:16:17.440> it's<00:16:17.560> a<00:16:17.620> testing<00:16:18.040> technique<00:16:18.460> because<00:16:19.360> in 00:16:19.590 --> 00:16:19.600 align:start position:0% why it's a testing technique because in 00:16:19.600 --> 00:16:20.910 align:start position:0% why it's a testing technique because in every<00:16:19.779> time<00:16:19.960> there<00:16:20.200> will<00:16:20.290> be<00:16:20.350> some<00:16:20.620> states 00:16:20.910 --> 00:16:20.920 align:start position:0% every time there will be some states 00:16:20.920 --> 00:16:23.700 align:start position:0% every time there will be some states that<00:16:21.400> you<00:16:21.880> would<00:16:22.029> not<00:16:22.240> not<00:16:22.930> observe<00:16:23.350> simply 00:16:23.700 --> 00:16:23.710 align:start position:0% that you would not not observe simply 00:16:23.710 --> 00:16:25.320 align:start position:0% that you would not not observe simply because<00:16:23.980> the<00:16:24.130> puzzle<00:16:24.430> did<00:16:24.550> not<00:16:24.760> generate<00:16:25.150> that 00:16:25.320 --> 00:16:25.330 align:start position:0% because the puzzle did not generate that 00:16:25.330 --> 00:16:27.450 align:start position:0% because the puzzle did not generate that specific<00:16:25.839> sequence<00:16:26.770> of<00:16:26.860> transaction<00:16:27.430> that 00:16:27.450 --> 00:16:27.460 align:start position:0% specific sequence of transaction that 00:16:27.460 --> 00:16:29.430 align:start position:0% specific sequence of transaction that would<00:16:27.760> transition<00:16:28.600> the<00:16:28.870> contract<00:16:29.230> to<00:16:29.320> the 00:16:29.430 --> 00:16:29.440 align:start position:0% would transition the contract to the 00:16:29.440 --> 00:16:32.370 align:start position:0% would transition the contract to the states<00:16:29.880> so<00:16:30.880> it's<00:16:31.420> a<00:16:31.510> testing<00:16:32.080> technique 00:16:32.370 --> 00:16:32.380 align:start position:0% states so it's a testing technique 00:16:32.380 --> 00:16:35.250 align:start position:0% states so it's a testing technique essentially<00:16:33.089> now<00:16:34.140> symbolic<00:16:35.140> execution 00:16:35.250 --> 00:16:35.260 align:start position:0% essentially now symbolic execution 00:16:35.260 --> 00:16:38.790 align:start position:0% essentially now symbolic execution that's<00:16:35.860> something<00:16:36.310> different<00:16:37.650> symbolic<00:16:38.650> easy 00:16:38.790 --> 00:16:38.800 align:start position:0% that's something different symbolic easy 00:16:38.800 --> 00:16:40.800 align:start position:0% that's something different symbolic easy techniques<00:16:39.760> that<00:16:39.880> it<00:16:40.029> is<00:16:40.120> based<00:16:40.390> on<00:16:40.600> this 00:16:40.800 --> 00:16:40.810 align:start position:0% techniques that it is based on this 00:16:40.810 --> 00:16:43.350 align:start position:0% techniques that it is based on this symbolically<00:16:41.650> special<00:16:42.010> technique<00:16:42.279> it<00:16:42.970> simply 00:16:43.350 --> 00:16:43.360 align:start position:0% symbolically special technique it simply 00:16:43.360 --> 00:16:46.079 align:start position:0% symbolically special technique it simply would<00:16:43.540> not<00:16:43.570> scale<00:16:44.020> to<00:16:44.050> reason<00:16:44.890> about<00:16:45.089> such 00:16:46.079 --> 00:16:46.089 align:start position:0% would not scale to reason about such 00:16:46.089 --> 00:16:47.730 align:start position:0% would not scale to reason about such depth<00:16:46.330> of<00:16:46.480> transaction<00:16:46.960> so<00:16:47.050> typically<00:16:47.440> if<00:16:47.589> you 00:16:47.730 --> 00:16:47.740 align:start position:0% depth of transaction so typically if you 00:16:47.740 --> 00:16:50.820 align:start position:0% depth of transaction so typically if you the<00:16:47.890> symbolic<00:16:48.360> symbolic<00:16:49.360> to<00:16:49.779> you<00:16:50.560> would<00:16:50.680> give 00:16:50.820 --> 00:16:50.830 align:start position:0% the symbolic symbolic to you would give 00:16:50.830 --> 00:16:53.100 align:start position:0% the symbolic symbolic to you would give it<00:16:50.920> as<00:16:51.010> a<00:16:51.130> mouse<00:16:51.400> so<00:16:51.910> it<00:16:52.060> would<00:16:52.180> run<00:16:52.300> for<00:16:52.570> maybe 00:16:53.100 --> 00:16:53.110 align:start position:0% it as a mouse so it would run for maybe 00:16:53.110 --> 00:16:54.690 align:start position:0% it as a mouse so it would run for maybe thirty<00:16:53.470> minutes<00:16:53.800> one<00:16:53.950> hour<00:16:53.980> and<00:16:54.339> then<00:16:54.490> you 00:16:54.690 --> 00:16:54.700 align:start position:0% thirty minutes one hour and then you 00:16:54.700 --> 00:16:55.920 align:start position:0% thirty minutes one hour and then you would<00:16:54.880> stop<00:16:55.150> and<00:16:55.360> then<00:16:55.510> it<00:16:55.600> would<00:16:55.750> reach 00:16:55.920 --> 00:16:55.930 align:start position:0% would stop and then it would reach 00:16:55.930 --> 00:16:59.400 align:start position:0% would stop and then it would reach certain<00:16:56.740> level<00:16:57.040> so<00:16:57.850> it<00:16:58.510> is<00:16:58.630> better<00:16:59.050> at<00:16:59.260> this 00:16:59.400 --> 00:16:59.410 align:start position:0% certain level so it is better at this 00:16:59.410 --> 00:17:02.460 align:start position:0% certain level so it is better at this kind<00:17:00.190> of<00:17:00.250> breath<00:17:00.730> exploration<00:17:01.450> and<00:17:01.810> but<00:17:02.350> if 00:17:02.460 --> 00:17:02.470 align:start position:0% kind of breath exploration and but if 00:17:02.470 --> 00:17:05.699 align:start position:0% kind of breath exploration and but if the<00:17:02.620> bugs<00:17:02.830> are<00:17:03.310> hidden<00:17:03.700> deeper<00:17:04.360> like<00:17:05.350> after 00:17:05.699 --> 00:17:05.709 align:start position:0% the bugs are hidden deeper like after 00:17:05.709 --> 00:17:07.380 align:start position:0% the bugs are hidden deeper like after five<00:17:05.740> ten<00:17:06.189> transactions<00:17:06.730> which<00:17:06.880> could<00:17:07.089> happen 00:17:07.380 --> 00:17:07.390 align:start position:0% five ten transactions which could happen 00:17:07.390 --> 00:17:09.120 align:start position:0% five ten transactions which could happen even<00:17:07.540> in<00:17:07.750> simple<00:17:07.959> contracts<00:17:08.500> across<00:17:08.770> cells 00:17:09.120 --> 00:17:09.130 align:start position:0% even in simple contracts across cells 00:17:09.130 --> 00:17:11.760 align:start position:0% even in simple contracts across cells were<00:17:09.370> you<00:17:09.970> have<00:17:10.089> to<00:17:10.150> transition<00:17:10.510> to<00:17:10.770> example 00:17:11.760 --> 00:17:11.770 align:start position:0% were you have to transition to example 00:17:11.770 --> 00:17:14.490 align:start position:0% were you have to transition to example two<00:17:11.829> some<00:17:12.010> refund<00:17:12.429> face<00:17:12.760> where<00:17:13.510> you<00:17:13.689> exercise 00:17:14.490 --> 00:17:14.500 align:start position:0% two some refund face where you exercise 00:17:14.500 --> 00:17:16.710 align:start position:0% two some refund face where you exercise it<00:17:14.709> on<00:17:14.860> three<00:17:15.069> week<00:17:15.309> on<00:17:15.490> functionality<00:17:15.880> so 00:17:16.710 --> 00:17:16.720 align:start position:0% it on three week on functionality so 00:17:16.720 --> 00:17:18.900 align:start position:0% it on three week on functionality so this<00:17:16.900> typically<00:17:17.350> tend<00:17:17.620> to<00:17:17.740> be<00:17:17.910> somewhere 00:17:18.900 --> 00:17:18.910 align:start position:0% this typically tend to be somewhere 00:17:18.910 --> 00:17:21.750 align:start position:0% this typically tend to be somewhere lower<00:17:19.270> that<00:17:19.689> are<00:17:19.900> harder<00:17:20.530> to<00:17:20.579> explore<00:17:21.579> with 00:17:21.750 --> 00:17:21.760 align:start position:0% lower that are harder to explore with 00:17:21.760 --> 00:17:24.329 align:start position:0% lower that are harder to explore with similar<00:17:22.089> tools<00:17:22.500> so<00:17:23.500> I<00:17:23.559> have<00:17:23.709> listed<00:17:23.860> here<00:17:24.010> some 00:17:24.329 --> 00:17:24.339 align:start position:0% similar tools so I have listed here some 00:17:24.339 --> 00:17:25.439 align:start position:0% similar tools so I have listed here some other<00:17:24.370> open<00:17:24.850> tools<00:17:25.089> that<00:17:25.240> are<00:17:25.360> available 00:17:25.439 --> 00:17:25.449 align:start position:0% other open tools that are available 00:17:25.449 --> 00:17:26.180 align:start position:0% other open tools that are available that's 00:17:26.180 --> 00:17:26.190 align:start position:0% that's 00:17:26.190 --> 00:17:32.060 align:start position:0% that's to<00:17:26.400> do<00:17:26.520> this<00:17:27.440> okay<00:17:28.580> it<00:17:29.580> is<00:17:29.700> clear<00:17:30.090> so<00:17:30.300> far<00:17:31.070> if 00:17:32.060 --> 00:17:32.070 align:start position:0% to do this okay it is clear so far if 00:17:32.070 --> 00:17:33.740 align:start position:0% to do this okay it is clear so far if there<00:17:32.250> any<00:17:32.370> questions<00:17:32.790> just<00:17:32.880> raise<00:17:33.240> your<00:17:33.300> hand 00:17:33.740 --> 00:17:33.750 align:start position:0% there any questions just raise your hand 00:17:33.750 --> 00:17:37.640 align:start position:0% there any questions just raise your hand you<00:17:34.110> can<00:17:34.260> also<00:17:34.410> go<00:17:35.190> to<00:17:35.220> this<00:17:35.550> point<00:17:35.730> itself<00:17:36.650> all 00:17:37.640 --> 00:17:37.650 align:start position:0% you can also go to this point itself all 00:17:37.650 --> 00:17:39.020 align:start position:0% you can also go to this point itself all right<00:17:37.770> so<00:17:37.950> that's<00:17:38.130> the<00:17:38.250> best<00:17:38.460> thing<00:17:38.640> and<00:17:38.880> then 00:17:39.020 --> 00:17:39.030 align:start position:0% right so that's the best thing and then 00:17:39.030 --> 00:17:41.240 align:start position:0% right so that's the best thing and then the<00:17:39.390> highest<00:17:39.960> level<00:17:40.350> would<00:17:40.470> be<00:17:40.590> the<00:17:40.710> formal 00:17:41.240 --> 00:17:41.250 align:start position:0% the highest level would be the formal 00:17:41.250 --> 00:17:43.250 align:start position:0% the highest level would be the formal verification<00:17:41.400> what<00:17:41.910> this<00:17:42.090> workshop<00:17:42.990> would<00:17:43.110> be 00:17:43.250 --> 00:17:43.260 align:start position:0% verification what this workshop would be 00:17:43.260 --> 00:17:45.440 align:start position:0% verification what this workshop would be about<00:17:43.500> and<00:17:44.010> this<00:17:44.370> is<00:17:44.430> really<00:17:44.730> the<00:17:44.910> point<00:17:45.180> where 00:17:45.440 --> 00:17:45.450 align:start position:0% about and this is really the point where 00:17:45.450 --> 00:17:48.920 align:start position:0% about and this is really the point where you<00:17:45.840> have<00:17:46.260> a<00:17:46.470> slip<00:17:46.800> from<00:17:47.040> testing<00:17:47.700> to<00:17:48.120> for 00:17:48.920 --> 00:17:48.930 align:start position:0% you have a slip from testing to for 00:17:48.930 --> 00:17:50.810 align:start position:0% you have a slip from testing to for verification<00:17:49.260> meaning<00:17:49.950> that<00:17:50.070> you<00:17:50.700> could 00:17:50.810 --> 00:17:50.820 align:start position:0% verification meaning that you could 00:17:50.820 --> 00:17:53.000 align:start position:0% verification meaning that you could actually<00:17:51.030> prove<00:17:51.420> this<00:17:52.260> property<00:17:52.410> for 00:17:53.000 --> 00:17:53.010 align:start position:0% actually prove this property for 00:17:53.010 --> 00:17:56.150 align:start position:0% actually prove this property for whatever<00:17:54.080> sequence<00:17:55.080> of<00:17:55.380> transactions<00:17:55.950> we 00:17:56.150 --> 00:17:56.160 align:start position:0% whatever sequence of transactions we 00:17:56.160 --> 00:17:58.250 align:start position:0% whatever sequence of transactions we would<00:17:56.580> make<00:17:56.760> it<00:17:56.940> would<00:17:57.030> always<00:17:57.420> holds<00:17:57.930> no 00:17:58.250 --> 00:17:58.260 align:start position:0% would make it would always holds no 00:17:58.260 --> 00:17:59.450 align:start position:0% would make it would always holds no matter<00:17:58.440> what<00:17:58.680> okay 00:17:59.450 --> 00:17:59.460 align:start position:0% matter what okay 00:17:59.460 --> 00:18:03.520 align:start position:0% matter what okay measure<00:18:00.450> difficult<00:18:01.050> happens<00:18:01.230> at<00:18:02.100> that<00:18:02.220> point 00:18:03.520 --> 00:18:03.530 align:start position:0% measure difficult happens at that point 00:18:03.530 --> 00:18:07.880 align:start position:0% measure difficult happens at that point all<00:18:04.530> right<00:18:05.360> now<00:18:06.360> so<00:18:06.870> let<00:18:07.320> me<00:18:07.470> show<00:18:07.620> you<00:18:07.740> what 00:18:07.880 --> 00:18:07.890 align:start position:0% all right now so let me show you what 00:18:07.890 --> 00:18:09.200 align:start position:0% all right now so let me show you what this<00:18:07.980> means<00:18:08.040> is<00:18:08.370> that<00:18:08.400> you<00:18:08.670> cover<00:18:08.970> all 00:18:09.200 --> 00:18:09.210 align:start position:0% this means is that you cover all 00:18:09.210 --> 00:18:12.140 align:start position:0% this means is that you cover all possible<00:18:09.810> states<00:18:10.080> essentially<00:18:10.650> and<00:18:10.890> if<00:18:11.150> you 00:18:12.140 --> 00:18:12.150 align:start position:0% possible states essentially and if you 00:18:12.150 --> 00:18:13.400 align:start position:0% possible states essentially and if you will<00:18:12.300> check<00:18:12.510> out<00:18:12.690> of<00:18:12.780> them<00:18:12.930> and<00:18:13.110> if<00:18:13.170> you<00:18:13.260> check 00:18:13.400 --> 00:18:13.410 align:start position:0% will check out of them and if you check 00:18:13.410 --> 00:18:14.690 align:start position:0% will check out of them and if you check mark<00:18:13.680> all<00:18:13.830> of<00:18:13.920> them<00:18:14.070> you<00:18:14.190> grab<00:18:14.370> this<00:18:14.490> for 00:18:14.690 --> 00:18:14.700 align:start position:0% mark all of them you grab this for 00:18:14.700 --> 00:18:19.520 align:start position:0% mark all of them you grab this for guarantee<00:18:15.620> right<00:18:17.660> so<00:18:18.660> that's<00:18:19.080> what<00:18:19.290> the 00:18:19.520 --> 00:18:19.530 align:start position:0% guarantee right so that's what the 00:18:19.530 --> 00:18:22.520 align:start position:0% guarantee right so that's what the variant<00:18:19.950> system<00:18:20.250> does<00:18:20.460> and<00:18:21.320> you<00:18:22.320> will<00:18:22.440> be 00:18:22.520 --> 00:18:22.530 align:start position:0% variant system does and you will be 00:18:22.530 --> 00:18:25.630 align:start position:0% variant system does and you will be losing<00:18:22.770> its<00:18:22.920> own<00:18:23.070> and<00:18:23.400> the<00:18:23.970> input<00:18:24.300> system<00:18:24.870> is 00:18:25.630 --> 00:18:25.640 align:start position:0% losing its own and the input system is 00:18:25.640 --> 00:18:28.610 align:start position:0% losing its own and the input system is as<00:18:26.640> we<00:18:26.850> solves<00:18:27.300> the<00:18:27.570> smart<00:18:27.810> contracts<00:18:28.350> as<00:18:28.560> well 00:18:28.610 --> 00:18:28.620 align:start position:0% as we solves the smart contracts as well 00:18:28.620 --> 00:18:30.200 align:start position:0% as we solves the smart contracts as well as<00:18:29.010> the<00:18:29.100> specification<00:18:29.400> because<00:18:30.030> we're 00:18:30.200 --> 00:18:30.210 align:start position:0% as the specification because we're 00:18:30.210 --> 00:18:31.760 align:start position:0% as the specification because we're dealing<00:18:30.660> with<00:18:30.690> functional<00:18:31.200> characters<00:18:31.560> here 00:18:31.760 --> 00:18:31.770 align:start position:0% dealing with functional characters here 00:18:31.770 --> 00:18:34.910 align:start position:0% dealing with functional characters here and<00:18:32.360> the<00:18:33.360> main<00:18:33.540> thing<00:18:33.720> of<00:18:33.870> that<00:18:34.440> what<00:18:34.770> the 00:18:34.910 --> 00:18:34.920 align:start position:0% and the main thing of that what the 00:18:34.920 --> 00:18:36.830 align:start position:0% and the main thing of that what the making<00:18:35.220> of<00:18:35.340> verax<00:18:35.760> does<00:18:35.940> is<00:18:36.090> it<00:18:36.240> it's<00:18:36.510> fully 00:18:36.830 --> 00:18:36.840 align:start position:0% making of verax does is it it's fully 00:18:36.840 --> 00:18:40.880 align:start position:0% making of verax does is it it's fully automate<00:18:37.410> this<00:18:37.710> process<00:18:37.770> of<00:18:39.470> fully<00:18:40.470> optimize 00:18:40.880 --> 00:18:40.890 align:start position:0% automate this process of fully optimize 00:18:40.890 --> 00:18:42.350 align:start position:0% automate this process of fully optimize the<00:18:40.980> process<00:18:41.280> of<00:18:41.370> verifying<00:18:41.490> in<00:18:41.940> the<00:18:42.000> sensors 00:18:42.350 --> 00:18:42.360 align:start position:0% the process of verifying in the sensors 00:18:42.360 --> 00:18:45.230 align:start position:0% the process of verifying in the sensors it's<00:18:43.320> if<00:18:43.950> it's<00:18:44.160> successful<00:18:44.280> it<00:18:44.730> verifies<00:18:45.120> the 00:18:45.230 --> 00:18:45.240 align:start position:0% it's if it's successful it verifies the 00:18:45.240 --> 00:18:46.790 align:start position:0% it's if it's successful it verifies the property<00:18:45.630> it<00:18:45.690> can<00:18:45.840> down<00:18:46.050> give<00:18:46.320> guarantees<00:18:46.770> a 00:18:46.790 --> 00:18:46.800 align:start position:0% property it can down give guarantees a 00:18:46.800 --> 00:18:49.550 align:start position:0% property it can down give guarantees a is<00:18:47.310> for<00:18:47.580> it<00:18:47.760> is<00:18:47.850> fully<00:18:48.120> verified<00:18:48.350> and<00:18:49.350> if<00:18:49.470> it 00:18:49.550 --> 00:18:49.560 align:start position:0% is for it is fully verified and if it 00:18:49.560 --> 00:18:52.310 align:start position:0% is for it is fully verified and if it fails<00:18:49.770> to<00:18:49.980> verify<00:18:50.340> the<00:18:50.400> property<00:18:50.970> then<00:18:51.930> it 00:18:52.310 --> 00:18:52.320 align:start position:0% fails to verify the property then it 00:18:52.320 --> 00:18:53.660 align:start position:0% fails to verify the property then it doesn't<00:18:52.710> give<00:18:52.830> a<00:18:52.860> guarantee<00:18:53.040> whether<00:18:53.490> the 00:18:53.660 --> 00:18:53.670 align:start position:0% doesn't give a guarantee whether the 00:18:53.670 --> 00:18:55.850 align:start position:0% doesn't give a guarantee whether the property<00:18:54.060> does<00:18:54.240> well<00:18:54.510> they're<00:18:54.750> not<00:18:54.900> so<00:18:55.740> it 00:18:55.850 --> 00:18:55.860 align:start position:0% property does well they're not so it 00:18:55.860 --> 00:18:57.050 align:start position:0% property does well they're not so it could<00:18:56.010> be<00:18:56.040> like<00:18:56.160> you<00:18:56.370> have<00:18:56.460> to<00:18:56.520> help<00:18:56.850> a<00:18:56.970> little 00:18:57.050 --> 00:18:57.060 align:start position:0% could be like you have to help a little 00:18:57.060 --> 00:18:59.480 align:start position:0% could be like you have to help a little bit<00:18:57.240> to<00:18:57.510> actually<00:18:57.870> verify<00:18:58.200> the<00:18:58.470> property<00:18:58.950> or 00:18:59.480 --> 00:18:59.490 align:start position:0% bit to actually verify the property or 00:18:59.490 --> 00:19:01.190 align:start position:0% bit to actually verify the property or it<00:18:59.610> cook<00:18:59.820> another<00:19:00.000> property<00:19:00.330> is<00:19:00.480> valid<00:19:00.720> and 00:19:01.190 --> 00:19:01.200 align:start position:0% it cook another property is valid and 00:19:01.200 --> 00:19:04.130 align:start position:0% it cook another property is valid and then<00:19:01.440> you<00:19:02.040> have<00:19:02.190> to<00:19:02.340> pick<00:19:02.490> the<00:19:02.580> contracts<00:19:03.140> so 00:19:04.130 --> 00:19:04.140 align:start position:0% then you have to pick the contracts so 00:19:04.140 --> 00:19:06.879 align:start position:0% then you have to pick the contracts so we'll<00:19:04.530> see<00:19:04.680> some<00:19:04.890> example<00:19:05.310> so<00:19:05.460> now 00:19:06.879 --> 00:19:06.889 align:start position:0% we'll see some example so now 00:19:06.889 --> 00:19:12.499 align:start position:0% we'll see some example so now sighs<00:19:07.889> later<00:19:10.429> all<00:19:11.429> right<00:19:11.549> so<00:19:11.820> to<00:19:12.149> give<00:19:12.359> you<00:19:12.389> a 00:19:12.499 --> 00:19:12.509 align:start position:0% sighs later all right so to give you a 00:19:12.509 --> 00:19:14.539 align:start position:0% sighs later all right so to give you a bit<00:19:12.839> of<00:19:12.889> something<00:19:13.889> that<00:19:13.979> we<00:19:14.099> actually<00:19:14.190> spent 00:19:14.539 --> 00:19:14.549 align:start position:0% bit of something that we actually spent 00:19:14.549 --> 00:19:18.320 align:start position:0% bit of something that we actually spent quite<00:19:14.609> some<00:19:14.789> time<00:19:15.029> is<00:19:15.629> to<00:19:16.589> ensure<00:19:17.159> that<00:19:17.330> verax 00:19:18.320 --> 00:19:18.330 align:start position:0% quite some time is to ensure that verax 00:19:18.330 --> 00:19:20.869 align:start position:0% quite some time is to ensure that verax has<00:19:18.419> a<00:19:18.749> very<00:19:19.109> intuitive<00:19:19.649> and<00:19:20.039> easy-to-use 00:19:20.869 --> 00:19:20.879 align:start position:0% has a very intuitive and easy-to-use 00:19:20.879 --> 00:19:23.119 align:start position:0% has a very intuitive and easy-to-use facilitation<00:19:21.539> language<00:19:22.099> because<00:19:23.099> that 00:19:23.119 --> 00:19:23.129 align:start position:0% facilitation language because that 00:19:23.129 --> 00:19:25.099 align:start position:0% facilitation language because that typically<00:19:23.789> is<00:19:23.969> one<00:19:24.299> of<00:19:24.389> the<00:19:24.509> bottleneck<00:19:24.929> when 00:19:25.099 --> 00:19:25.109 align:start position:0% typically is one of the bottleneck when 00:19:25.109 --> 00:19:27.919 align:start position:0% typically is one of the bottleneck when we<00:19:25.229> talk<00:19:25.379> about<00:19:26.269> functional<00:19:27.269> correctness<00:19:27.479> is 00:19:27.919 --> 00:19:27.929 align:start position:0% we talk about functional correctness is 00:19:27.929 --> 00:19:29.690 align:start position:0% we talk about functional correctness is again<00:19:28.349> to<00:19:28.529> use<00:19:28.679> functional<00:19:29.070> correctness<00:19:29.190> in 00:19:29.690 --> 00:19:29.700 align:start position:0% again to use functional correctness in 00:19:29.700 --> 00:19:31.459 align:start position:0% again to use functional correctness in addition<00:19:29.999> to<00:19:30.119> the<00:19:30.209> contract<00:19:30.599> you<00:19:31.200> have<00:19:31.289> to 00:19:31.459 --> 00:19:31.469 align:start position:0% addition to the contract you have to 00:19:31.469 --> 00:19:33.079 align:start position:0% addition to the contract you have to write<00:19:31.709> down<00:19:31.950> what<00:19:32.219> the<00:19:32.309> contract<00:19:32.669> is<00:19:32.759> supposed 00:19:33.079 --> 00:19:33.089 align:start position:0% write down what the contract is supposed 00:19:33.089 --> 00:19:35.479 align:start position:0% write down what the contract is supposed to<00:19:33.179> do<00:19:33.359> and<00:19:33.959> if<00:19:34.320> this<00:19:34.440> is<00:19:34.619> very<00:19:34.859> hard<00:19:35.279> and 00:19:35.479 --> 00:19:35.489 align:start position:0% to do and if this is very hard and 00:19:35.489 --> 00:19:37.430 align:start position:0% to do and if this is very hard and tedious<00:19:35.609> of<00:19:35.969> specifying<00:19:36.479> you<00:19:36.690> you<00:19:37.080> know<00:19:37.200> you 00:19:37.430 --> 00:19:37.440 align:start position:0% tedious of specifying you you know you 00:19:37.440 --> 00:19:39.139 align:start position:0% tedious of specifying you you know you will<00:19:37.559> end<00:19:37.709> up<00:19:37.799> not<00:19:38.070> not<00:19:38.369> really<00:19:38.519> using<00:19:39.059> the 00:19:39.139 --> 00:19:39.149 align:start position:0% will end up not not really using the 00:19:39.149 --> 00:19:44.019 align:start position:0% will end up not not really using the system<00:19:39.479> so<00:19:40.229> I<00:19:40.789> will<00:19:41.789> get<00:19:42.149> a<00:19:42.179> few<00:19:42.450> examples<00:19:42.959> of 00:19:44.019 --> 00:19:44.029 align:start position:0% system so I will get a few examples of 00:19:44.029 --> 00:19:48.049 align:start position:0% system so I will get a few examples of specifications<00:19:45.029> that<00:19:45.499> we<00:19:46.499> have<00:19:46.769> seen<00:19:47.429> to<00:19:47.820> very 00:19:48.049 --> 00:19:48.059 align:start position:0% specifications that we have seen to very 00:19:48.059 --> 00:19:50.329 align:start position:0% specifications that we have seen to very frequently<00:19:48.719> appear<00:19:49.109> in<00:19:49.139> real<00:19:49.829> world<00:19:49.979> smart 00:19:50.329 --> 00:19:50.339 align:start position:0% frequently appear in real world smart 00:19:50.339 --> 00:19:51.589 align:start position:0% frequently appear in real world smart contracts<00:19:50.759> so<00:19:50.820> this<00:19:50.940> is<00:19:51.059> something<00:19:51.239> we<00:19:51.479> just 00:19:51.589 --> 00:19:51.599 align:start position:0% contracts so this is something we just 00:19:51.599 --> 00:19:53.810 align:start position:0% contracts so this is something we just observe<00:19:52.019> doing<00:19:52.320> audits<00:19:52.679> and<00:19:52.979> verifying 00:19:53.810 --> 00:19:53.820 align:start position:0% observe doing audits and verifying 00:19:53.820 --> 00:19:57.469 align:start position:0% observe doing audits and verifying contracts<00:19:54.919> and<00:19:55.919> so<00:19:56.399> this<00:19:56.579> is<00:19:56.700> a<00:19:56.729> this<00:19:57.359> is 00:19:57.469 --> 00:19:57.479 align:start position:0% contracts and so this is a this is 00:19:57.479 --> 00:19:59.209 align:start position:0% contracts and so this is a this is literally<00:19:57.749> what<00:19:58.019> the<00:19:58.139> specifications<00:19:58.289> are<00:19:59.009> so 00:19:59.209 --> 00:19:59.219 align:start position:0% literally what the specifications are so 00:19:59.219 --> 00:20:00.739 align:start position:0% literally what the specifications are so you<00:19:59.309> don't<00:19:59.339> have<00:19:59.579> to<00:19:59.729> write<00:19:59.940> some<00:20:00.269> elaborate 00:20:00.739 --> 00:20:00.749 align:start position:0% you don't have to write some elaborate 00:20:00.749 --> 00:20:03.199 align:start position:0% you don't have to write some elaborate scripts<00:20:01.169> or<00:20:01.379> something<00:20:02.279> very<00:20:02.489> complicated<00:20:02.969> to 00:20:03.199 --> 00:20:03.209 align:start position:0% scripts or something very complicated to 00:20:03.209 --> 00:20:06.259 align:start position:0% scripts or something very complicated to formally<00:20:03.809> state<00:20:03.959> of<00:20:04.079> property<00:20:04.469> so<00:20:05.369> common 00:20:06.259 --> 00:20:06.269 align:start position:0% formally state of property so common 00:20:06.269 --> 00:20:07.699 align:start position:0% formally state of property so common properties<00:20:06.719> are<00:20:06.869> things<00:20:07.109> like<00:20:07.259> access 00:20:07.699 --> 00:20:07.709 align:start position:0% properties are things like access 00:20:07.709 --> 00:20:10.039 align:start position:0% properties are things like access control<00:20:08.099> or<00:20:08.459> you<00:20:09.089> wanna<00:20:09.299> ensure<00:20:09.629> that<00:20:09.839> certain 00:20:10.039 --> 00:20:10.049 align:start position:0% control or you wanna ensure that certain 00:20:10.049 --> 00:20:12.649 align:start position:0% control or you wanna ensure that certain functions<00:20:10.619> can<00:20:10.979> be<00:20:11.009> involved<00:20:11.669> by<00:20:12.179> particular 00:20:12.649 --> 00:20:12.659 align:start position:0% functions can be involved by particular 00:20:12.659 --> 00:20:17.180 align:start position:0% functions can be involved by particular users<00:20:13.200> is<00:20:13.889> he<00:20:14.009> saying<00:20:14.249> that<00:20:14.309> in<00:20:15.709> always<00:20:16.709> in<00:20:17.099> the 00:20:17.180 --> 00:20:17.190 align:start position:0% users is he saying that in always in the 00:20:17.190 --> 00:20:18.919 align:start position:0% users is he saying that in always in the contract<00:20:17.609> if<00:20:17.789> there<00:20:18.059> was<00:20:18.209> a<00:20:18.239> transaction<00:20:18.719> to 00:20:18.919 --> 00:20:18.929 align:start position:0% contract if there was a transaction to 00:20:18.929 --> 00:20:21.769 align:start position:0% contract if there was a transaction to deposits<00:20:19.499> then<00:20:19.889> that<00:20:20.159> was<00:20:20.369> that<00:20:21.209> transaction 00:20:21.769 --> 00:20:21.779 align:start position:0% deposits then that was that transaction 00:20:21.779 --> 00:20:24.219 align:start position:0% deposits then that was that transaction was<00:20:21.809> made<00:20:22.019> by<00:20:22.529> the<00:20:22.589> owner<00:20:23.009> of<00:20:23.219> the<00:20:23.309> contracts 00:20:24.219 --> 00:20:24.229 align:start position:0% was made by the owner of the contracts 00:20:24.229 --> 00:20:26.989 align:start position:0% was made by the owner of the contracts another<00:20:25.229> common<00:20:25.589> party<00:20:26.190> that<00:20:26.339> we<00:20:26.459> observe<00:20:26.759> is 00:20:26.989 --> 00:20:26.999 align:start position:0% another common party that we observe is 00:20:26.999 --> 00:20:29.869 align:start position:0% another common party that we observe is that<00:20:27.029> very<00:20:28.019> often<00:20:28.349> it's<00:20:28.919> not<00:20:29.190> about<00:20:29.399> who<00:20:29.789> is 00:20:29.869 --> 00:20:29.879 align:start position:0% that very often it's not about who is 00:20:29.879 --> 00:20:31.489 align:start position:0% that very often it's not about who is sending<00:20:30.089> a<00:20:30.239> transaction<00:20:30.749> but<00:20:30.929> it<00:20:31.019> won't<00:20:31.320> in 00:20:31.489 --> 00:20:31.499 align:start position:0% sending a transaction but it won't in 00:20:31.499 --> 00:20:34.430 align:start position:0% sending a transaction but it won't in universe<00:20:31.979> states<00:20:32.309> the<00:20:32.579> contract<00:20:33.029> is<00:20:33.259> so<00:20:34.259> for 00:20:34.430 --> 00:20:34.440 align:start position:0% universe states the contract is so for 00:20:34.440 --> 00:20:37.609 align:start position:0% universe states the contract is so for instance<00:20:34.739> here<00:20:35.519> we<00:20:35.639> say<00:20:35.820> that<00:20:35.929> if<00:20:36.929> the<00:20:37.259> current 00:20:37.609 --> 00:20:37.619 align:start position:0% instance here we say that if the current 00:20:37.619 --> 00:20:39.949 align:start position:0% instance here we say that if the current time<00:20:37.799> exceeds<00:20:38.369> the<00:20:38.820> refund<00:20:39.239> time<00:20:39.419> by<00:20:39.629> a<00:20:39.659> week 00:20:39.949 --> 00:20:39.959 align:start position:0% time exceeds the refund time by a week 00:20:39.959 --> 00:20:43.399 align:start position:0% time exceeds the refund time by a week and<00:20:40.649> users<00:20:41.099> are<00:20:41.429> never<00:20:41.789> no<00:20:42.539> longer<00:20:42.869> allowed<00:20:43.200> to 00:20:43.399 --> 00:20:43.409 align:start position:0% and users are never no longer allowed to 00:20:43.409 --> 00:20:48.430 align:start position:0% and users are never no longer allowed to submit<00:20:43.829> refund<00:20:44.459> transactions 00:20:48.430 --> 00:20:48.440 align:start position:0% 00:20:48.440 --> 00:20:50.890 align:start position:0% yes<00:20:49.100> state<00:20:49.580> machine<00:20:49.880> properties<00:20:50.270> is<00:20:50.390> as<00:20:50.630> well 00:20:50.890 --> 00:20:50.900 align:start position:0% yes state machine properties is as well 00:20:50.900 --> 00:20:52.900 align:start position:0% yes state machine properties is as well so<00:20:51.140> again<00:20:51.410> contracts<00:20:51.950> are<00:20:52.100> very<00:20:52.340> stateful 00:20:52.900 --> 00:20:52.910 align:start position:0% so again contracts are very stateful 00:20:52.910 --> 00:20:54.640 align:start position:0% so again contracts are very stateful there's<00:20:53.360> explicit<00:20:53.900> state<00:20:54.080> variables<00:20:54.560> that 00:20:54.640 --> 00:20:54.650 align:start position:0% there's explicit state variables that 00:20:54.650 --> 00:20:57.430 align:start position:0% there's explicit state variables that define<00:20:54.800> how<00:20:55.280> the<00:20:55.610> states<00:20:56.210> how<00:20:56.930> the<00:20:56.990> contract 00:20:57.430 --> 00:20:57.440 align:start position:0% define how the states how the contract 00:20:57.440 --> 00:20:58.720 align:start position:0% define how the states how the contract in<00:20:57.620> addition<00:20:58.010> to<00:20:58.100> the<00:20:58.160> different<00:20:58.280> states<00:20:58.670> so 00:20:58.720 --> 00:20:58.730 align:start position:0% in addition to the different states so 00:20:58.730 --> 00:20:59.850 align:start position:0% in addition to the different states so you<00:20:58.850> have<00:20:59.060> to<00:20:59.180> make<00:20:59.330> sure<00:20:59.480> that<00:20:59.630> these 00:20:59.850 --> 00:20:59.860 align:start position:0% you have to make sure that these 00:20:59.860 --> 00:21:04.510 align:start position:0% you have to make sure that these transitions<00:21:00.860> are<00:21:02.830> implemented<00:21:03.830> correctly<00:21:04.190> in 00:21:04.510 --> 00:21:04.520 align:start position:0% transitions are implemented correctly in 00:21:04.520 --> 00:21:08.200 align:start position:0% transitions are implemented correctly in the<00:21:04.610> contracts<00:21:05.230> we<00:21:06.230> saw<00:21:06.770> an<00:21:06.950> example<00:21:07.210> earlier 00:21:08.200 --> 00:21:08.210 align:start position:0% the contracts we saw an example earlier 00:21:08.210 --> 00:21:10.710 align:start position:0% the contracts we saw an example earlier I<00:21:08.300> suppose<00:21:08.600> so<00:21:08.870> we<00:21:08.960> have<00:21:09.110> some<00:21:09.380> over<00:21:09.710> basically 00:21:10.710 --> 00:21:10.720 align:start position:0% I suppose so we have some over basically 00:21:10.720 --> 00:21:13.030 align:start position:0% I suppose so we have some over basically aggregations<00:21:11.720> over<00:21:12.020> mappings<00:21:12.440> in<00:21:12.560> a<00:21:12.650> race<00:21:12.830> now 00:21:13.030 --> 00:21:13.040 align:start position:0% aggregations over mappings in a race now 00:21:13.040 --> 00:21:14.800 align:start position:0% aggregations over mappings in a race now also<00:21:13.400> tend<00:21:13.760> to<00:21:13.850> be<00:21:13.940> pretty<00:21:14.090> common<00:21:14.330> so<00:21:14.630> that's 00:21:14.800 --> 00:21:14.810 align:start position:0% also tend to be pretty common so that's 00:21:14.810 --> 00:21:17.950 align:start position:0% also tend to be pretty common so that's we<00:21:15.590> have<00:21:15.620> at<00:21:16.610> least<00:21:16.790> explicit<00:21:17.360> keywords<00:21:17.810> in 00:21:17.950 --> 00:21:17.960 align:start position:0% we have at least explicit keywords in 00:21:17.960 --> 00:21:20.920 align:start position:0% we have at least explicit keywords in the<00:21:18.080> language<00:21:18.380> to<00:21:18.530> allow<00:21:18.620> users<00:21:19.490> to<00:21:19.780> to<00:21:20.780> run 00:21:20.920 --> 00:21:20.930 align:start position:0% the language to allow users to to run 00:21:20.930 --> 00:21:23.350 align:start position:0% the language to allow users to to run these<00:21:21.050> properties<00:21:21.560> and<00:21:22.030> another<00:21:23.030> common 00:21:23.350 --> 00:21:23.360 align:start position:0% these properties and another common 00:21:23.360 --> 00:21:25.000 align:start position:0% these properties and another common pattern<00:21:23.690> is<00:21:23.780> that<00:21:23.810> so<00:21:24.200> typically<00:21:24.710> we<00:21:24.830> have<00:21:24.860> a 00:21:25.000 --> 00:21:25.010 align:start position:0% pattern is that so typically we have a 00:21:25.010 --> 00:21:27.400 align:start position:0% pattern is that so typically we have a project<00:21:25.790> it's<00:21:26.330> not<00:21:26.570> implement<00:21:27.230> the<00:21:27.260> full 00:21:27.400 --> 00:21:27.410 align:start position:0% project it's not implement the full 00:21:27.410 --> 00:21:29.170 align:start position:0% project it's not implement the full production<00:21:27.710> of<00:21:27.890> our<00:21:27.980> contractors<00:21:28.460> in<00:21:28.640> several 00:21:29.170 --> 00:21:29.180 align:start position:0% production of our contractors in several 00:21:29.180 --> 00:21:31.660 align:start position:0% production of our contractors in several contracts<00:21:29.630> and<00:21:30.440> often<00:21:30.920> there<00:21:31.130> are<00:21:31.160> certain 00:21:31.660 --> 00:21:31.670 align:start position:0% contracts and often there are certain 00:21:31.670 --> 00:21:33.880 align:start position:0% contracts and often there are certain invariants<00:21:32.360> that<00:21:32.450> software<00:21:33.170> dependencies 00:21:33.880 --> 00:21:33.890 align:start position:0% invariants that software dependencies 00:21:33.890 --> 00:21:36.220 align:start position:0% invariants that software dependencies that<00:21:33.920> are<00:21:34.280> exists<00:21:35.270> between<00:21:35.450> the<00:21:35.750> contracts 00:21:36.220 --> 00:21:36.230 align:start position:0% that are exists between the contracts 00:21:36.230 --> 00:21:39.130 align:start position:0% that are exists between the contracts and<00:21:36.380> their<00:21:36.920> properties<00:21:37.370> that's<00:21:38.140> capture 00:21:39.130 --> 00:21:39.140 align:start position:0% and their properties that's capture 00:21:39.140 --> 00:21:40.660 align:start position:0% and their properties that's capture these<00:21:39.320> dependencies<00:21:39.920> we<00:21:40.070> have<00:21:40.160> to<00:21:40.280> verify 00:21:40.660 --> 00:21:40.670 align:start position:0% these dependencies we have to verify 00:21:40.670 --> 00:21:42.490 align:start position:0% these dependencies we have to verify that<00:21:40.700> they<00:21:40.940> are<00:21:40.970> implemented<00:21:41.690> correctly<00:21:42.170> in 00:21:42.490 --> 00:21:42.500 align:start position:0% that they are implemented correctly in 00:21:42.500 --> 00:21:46.240 align:start position:0% that they are implemented correctly in the<00:21:42.560> conference<00:21:43.270> ok<00:21:44.270> so<00:21:44.740> again<00:21:45.740> you<00:21:46.040> will<00:21:46.190> be 00:21:46.240 --> 00:21:46.250 align:start position:0% the conference ok so again you will be 00:21:46.250 --> 00:21:47.830 align:start position:0% the conference ok so again you will be writing<00:21:46.700> some<00:21:46.850> of<00:21:46.940> these<00:21:47.060> so<00:21:47.600> these 00:21:47.830 --> 00:21:47.840 align:start position:0% writing some of these so these 00:21:47.840 --> 00:21:51.900 align:start position:0% writing some of these so these specification<00:21:48.590> so<00:21:48.950> a<00:21:50.200> bit<00:21:51.200> more<00:21:51.230> technically 00:21:51.900 --> 00:21:51.910 align:start position:0% specification so a bit more technically 00:21:51.910 --> 00:21:56.610 align:start position:0% specification so a bit more technically four<00:21:54.340> he<00:21:55.340> went<00:21:55.520> the<00:21:55.640> cinematics<00:21:56.180> of<00:21:56.360> the 00:21:56.610 --> 00:21:56.620 align:start position:0% four he went the cinematics of the 00:21:56.620 --> 00:21:58.540 align:start position:0% four he went the cinematics of the specification<00:21:57.620> level<00:21:57.860> is<00:21:57.950> actually<00:21:58.040> based<00:21:58.400> on 00:21:58.540 --> 00:21:58.550 align:start position:0% specification level is actually based on 00:21:58.550 --> 00:22:01.660 align:start position:0% specification level is actually based on something<00:21:59.410> on<00:22:00.410> a<00:22:00.470> fragment<00:22:00.890> of<00:22:00.980> that<00:22:01.160> product 00:22:01.660 --> 00:22:01.670 align:start position:0% something on a fragment of that product 00:22:01.670 --> 00:22:03.160 align:start position:0% something on a fragment of that product which<00:22:01.790> is<00:22:01.910> very<00:22:01.940> well<00:22:02.390> that<00:22:02.840> it's<00:22:03.020> a 00:22:03.160 --> 00:22:03.170 align:start position:0% which is very well that it's a 00:22:03.170 --> 00:22:05.800 align:start position:0% which is very well that it's a specification<00:22:04.160> language<00:22:04.730> if<00:22:04.910> you<00:22:05.000> go<00:22:05.180> back 00:22:05.800 --> 00:22:05.810 align:start position:0% specification language if you go back 00:22:05.810 --> 00:22:08.050 align:start position:0% specification language if you go back take<00:22:06.320> the<00:22:06.770> case<00:22:06.950> of<00:22:07.220> research<00:22:07.550> in<00:22:07.730> this<00:22:07.850> soit 00:22:08.050 --> 00:22:08.060 align:start position:0% take the case of research in this soit 00:22:08.060 --> 00:22:10.570 align:start position:0% take the case of research in this soit is<00:22:08.240> very<00:22:09.020> well<00:22:09.200> understood<00:22:09.250> complexities<00:22:10.250> and 00:22:10.570 --> 00:22:10.580 align:start position:0% is very well understood complexities and 00:22:10.580 --> 00:22:13.470 align:start position:0% is very well understood complexities and expressivity<00:22:11.210> and<00:22:11.480> so<00:22:11.690> on 00:22:13.470 --> 00:22:13.480 align:start position:0% expressivity and so on 00:22:13.480 --> 00:22:18.160 align:start position:0% expressivity and so on alright<00:22:14.480> so<00:22:15.260> I<00:22:15.560> want<00:22:16.190> to<00:22:16.610> depth<00:22:17.150> on<00:22:17.360> how<00:22:17.390> how 00:22:18.160 --> 00:22:18.170 align:start position:0% alright so I want to depth on how how 00:22:18.170 --> 00:22:21.760 align:start position:0% alright so I want to depth on how how the<00:22:18.370> verifier<00:22:19.400> actually<00:22:19.730> works<00:22:20.350> but<00:22:21.350> in<00:22:21.560> 30 00:22:21.760 --> 00:22:21.770 align:start position:0% the verifier actually works but in 30 00:22:21.770 --> 00:22:23.980 align:start position:0% the verifier actually works but in 30 bit<00:22:22.040> combines<00:22:22.400> two<00:22:22.670> techniques<00:22:23.000> one 00:22:23.980 --> 00:22:23.990 align:start position:0% bit combines two techniques one 00:22:23.990 --> 00:22:26.050 align:start position:0% bit combines two techniques one technique<00:22:24.530> is<00:22:24.680> it<00:22:24.950> does<00:22:25.130> use<00:22:25.370> this<00:22:25.580> symbolic 00:22:26.050 --> 00:22:26.060 align:start position:0% technique is it does use this symbolic 00:22:26.060 --> 00:22:28.120 align:start position:0% technique is it does use this symbolic execution<00:22:26.290> technique<00:22:27.290> which<00:22:27.530> is<00:22:27.680> very<00:22:27.920> good 00:22:28.120 --> 00:22:28.130 align:start position:0% execution technique which is very good 00:22:28.130 --> 00:22:30.580 align:start position:0% execution technique which is very good at<00:22:28.250> handling<00:22:29.110> dealing<00:22:30.110> with<00:22:30.260> many<00:22:30.500> different 00:22:30.580 --> 00:22:30.590 align:start position:0% at handling dealing with many different 00:22:30.590 --> 00:22:33.880 align:start position:0% at handling dealing with many different I<00:22:31.720> contribute<00:22:32.720> you<00:22:32.840> submitting<00:22:33.320> transactions 00:22:33.880 --> 00:22:33.890 align:start position:0% I contribute you submitting transactions 00:22:33.890 --> 00:22:36.910 align:start position:0% I contribute you submitting transactions and<00:22:34.490> then<00:22:34.640> to<00:22:35.510> deal<00:22:35.930> with<00:22:36.080> the<00:22:36.230> unfounded 00:22:36.910 --> 00:22:36.920 align:start position:0% and then to deal with the unfounded 00:22:36.920 --> 00:22:38.850 align:start position:0% and then to deal with the unfounded depth<00:22:37.190> that<00:22:37.520> users<00:22:38.210> will 00:22:38.850 --> 00:22:38.860 align:start position:0% depth that users will 00:22:38.860 --> 00:22:40.049 align:start position:0% depth that users will use<00:22:39.070> something<00:22:39.580> called<00:22:39.610> predictive 00:22:40.049 --> 00:22:40.059 align:start position:0% use something called predictive 00:22:40.059 --> 00:22:42.810 align:start position:0% use something called predictive abstraction<00:22:40.690> that<00:22:41.409> allows<00:22:41.740> it<00:22:41.950> to<00:22:41.980> fully 00:22:42.810 --> 00:22:42.820 align:start position:0% abstraction that allows it to fully 00:22:42.820 --> 00:22:44.880 align:start position:0% abstraction that allows it to fully capture<00:22:43.029> all<00:22:43.539> the<00:22:43.750> possible<00:22:44.169> that<00:22:44.350> is<00:22:44.500> very 00:22:44.880 --> 00:22:44.890 align:start position:0% capture all the possible that is very 00:22:44.890 --> 00:22:46.950 align:start position:0% capture all the possible that is very large<00:22:45.190> unbounded<00:22:46.179> three<00:22:46.360> to<00:22:46.539> capture<00:22:46.870> it<00:22:46.929> with 00:22:46.950 --> 00:22:46.960 align:start position:0% large unbounded three to capture it with 00:22:46.960 --> 00:22:49.200 align:start position:0% large unbounded three to capture it with some<00:22:47.289> finite<00:22:47.500> representation<00:22:48.309> so<00:22:48.880> the<00:22:49.029> plane 00:22:49.200 --> 00:22:49.210 align:start position:0% some finite representation so the plane 00:22:49.210 --> 00:22:53.279 align:start position:0% some finite representation so the plane equal<00:22:49.450> time<00:22:49.690> we<00:22:50.140> may<00:22:50.710> get<00:22:51.570> you<00:22:52.570> know<00:22:52.690> it's<00:22:53.049> more 00:22:53.279 --> 00:22:53.289 align:start position:0% equal time we may get you know it's more 00:22:53.289 --> 00:22:55.399 align:start position:0% equal time we may get you know it's more details<00:22:53.620> about<00:22:53.769> that<00:22:53.890> disease 00:22:55.399 --> 00:22:55.409 align:start position:0% details about that disease 00:22:55.409 --> 00:22:57.690 align:start position:0% details about that disease alright<00:22:56.409> so<00:22:56.590> that's<00:22:56.710> what<00:22:56.890> the<00:22:57.010> fellow<00:22:57.279> intro 00:22:57.690 --> 00:22:57.700 align:start position:0% alright so that's what the fellow intro 00:22:57.700 --> 00:23:00.720 align:start position:0% alright so that's what the fellow intro and<00:22:58.080> now<00:22:59.080> we're<00:22:59.679> going<00:23:00.070> to<00:23:00.159> transition<00:23:00.490> into 00:23:00.720 --> 00:23:00.730 align:start position:0% and now we're going to transition into 00:23:00.730 --> 00:23:04.500 align:start position:0% and now we're going to transition into the<00:23:01.120> actual<00:23:01.480> exercise<00:23:01.870> on<00:23:03.210> how<00:23:04.210> to<00:23:04.269> use 00:23:04.500 --> 00:23:04.510 align:start position:0% the actual exercise on how to use 00:23:04.510 --> 00:23:06.570 align:start position:0% the actual exercise on how to use vericsson<00:23:04.990> to<00:23:05.140> specify<00:23:06.010> these<00:23:06.070> properties<00:23:06.549> so 00:23:06.570 --> 00:23:06.580 align:start position:0% vericsson to specify these properties so 00:23:06.580 --> 00:23:09.419 align:start position:0% vericsson to specify these properties so hand<00:23:07.029> over<00:23:07.269> to<00:23:07.450> me<00:23:07.539> to<00:23:07.950> introduce<00:23:08.950> an<00:23:09.070> example 00:23:09.419 --> 00:23:09.429 align:start position:0% hand over to me to introduce an example 00:23:09.429 --> 00:23:14.759 align:start position:0% hand over to me to introduce an example uses<00:23:10.049> yes<00:23:11.049> okay<00:23:12.210> amico<00:23:13.210> yes<00:23:13.630> and<00:23:13.929> now<00:23:14.440> we<00:23:14.470> can 00:23:14.759 --> 00:23:14.769 align:start position:0% uses yes okay amico yes and now we can 00:23:14.769 --> 00:23:18.750 align:start position:0% uses yes okay amico yes and now we can here<00:23:14.980> with<00:23:15.130> a<00:23:15.840> small<00:23:16.840> exercise<00:23:17.580> to<00:23:18.580> use 00:23:18.750 --> 00:23:18.760 align:start position:0% here with a small exercise to use 00:23:18.760 --> 00:23:21.600 align:start position:0% here with a small exercise to use Ebonics<00:23:19.620> by<00:23:20.620> the<00:23:20.679> way<00:23:20.860> if<00:23:21.100> you<00:23:21.190> have<00:23:21.370> any 00:23:21.600 --> 00:23:21.610 align:start position:0% Ebonics by the way if you have any 00:23:21.610 --> 00:23:23.759 align:start position:0% Ebonics by the way if you have any questions<00:23:22.210> at<00:23:22.419> any<00:23:22.539> time<00:23:22.990> this<00:23:23.260> raise<00:23:23.620> your 00:23:23.759 --> 00:23:23.769 align:start position:0% questions at any time this raise your 00:23:23.769 --> 00:23:29.669 align:start position:0% questions at any time this raise your hand<00:23:24.299> and<00:23:26.340> we<00:23:27.340> can<00:23:27.789> ask<00:23:28.120> the<00:23:28.389> questions<00:23:28.809> the 00:23:29.669 --> 00:23:29.679 align:start position:0% hand and we can ask the questions the 00:23:29.679 --> 00:23:31.409 align:start position:0% hand and we can ask the questions the goal<00:23:29.860> here<00:23:30.100> is<00:23:30.130> to<00:23:30.220> make<00:23:30.580> the<00:23:30.850> exercise<00:23:31.389> more 00:23:31.409 --> 00:23:31.419 align:start position:0% goal here is to make the exercise more 00:23:31.419 --> 00:23:38.190 align:start position:0% goal here is to make the exercise more inter<00:23:31.960> and<00:23:32.529> not<00:23:33.220> so<00:23:33.399> careful<00:23:34.590> okay<00:23:36.690> so<00:23:37.690> so<00:23:38.019> the 00:23:38.190 --> 00:23:38.200 align:start position:0% inter and not so careful okay so so the 00:23:38.200 --> 00:23:42.509 align:start position:0% inter and not so careful okay so so the first<00:23:38.230> step<00:23:38.649> in<00:23:39.090> proper<00:23:40.090> verification<00:23:41.010> is<00:23:42.010> to 00:23:42.509 --> 00:23:42.519 align:start position:0% first step in proper verification is to 00:23:42.519 --> 00:23:44.159 align:start position:0% first step in proper verification is to actually<00:23:42.940> specify<00:23:43.809> the<00:23:43.870> properties 00:23:44.159 --> 00:23:44.169 align:start position:0% actually specify the properties 00:23:44.169 --> 00:23:47.700 align:start position:0% actually specify the properties informally<00:23:45.659> this<00:23:46.659> means<00:23:46.929> that<00:23:47.080> we<00:23:47.230> specified 00:23:47.700 --> 00:23:47.710 align:start position:0% informally this means that we specified 00:23:47.710 --> 00:23:49.350 align:start position:0% informally this means that we specified any<00:23:47.919> natural<00:23:48.220> language<00:23:48.639> whether<00:23:49.149> it's 00:23:49.350 --> 00:23:49.360 align:start position:0% any natural language whether it's 00:23:49.360 --> 00:23:51.360 align:start position:0% any natural language whether it's English<00:23:49.690> or<00:23:49.840> some<00:23:50.080> other<00:23:50.200> language<00:23:50.320> you<00:23:51.039> just 00:23:51.360 --> 00:23:51.370 align:start position:0% English or some other language you just 00:23:51.370 --> 00:23:53.909 align:start position:0% English or some other language you just need<00:23:51.760> to<00:23:51.940> have<00:23:52.210> some<00:23:52.419> clarity<00:23:52.809> over<00:23:53.559> what's 00:23:53.909 --> 00:23:53.919 align:start position:0% need to have some clarity over what's 00:23:53.919 --> 00:23:58.620 align:start position:0% need to have some clarity over what's this<00:23:54.460> smart<00:23:55.450> contrapposto<00:23:56.110> right<00:23:57.100> and<00:23:57.639> in 00:23:58.620 --> 00:23:58.630 align:start position:0% this smart contrapposto right and in 00:23:58.630 --> 00:24:01.500 align:start position:0% this smart contrapposto right and in this<00:23:58.929> exercise<00:23:59.139> we'll<00:24:00.010> look<00:24:00.220> at<00:24:00.399> two<00:24:00.909> main 00:24:01.500 --> 00:24:01.510 align:start position:0% this exercise we'll look at two main 00:24:01.510 --> 00:24:02.250 align:start position:0% this exercise we'll look at two main confidence 00:24:02.250 --> 00:24:02.260 align:start position:0% confidence 00:24:02.260 --> 00:24:05.580 align:start position:0% confidence what<00:24:02.769> is<00:24:02.889> your<00:24:03.159> C<00:24:03.340> 20<00:24:03.700> okay<00:24:04.090> the<00:24:04.510> other<00:24:04.539> is<00:24:04.779> kind 00:24:05.580 --> 00:24:05.590 align:start position:0% what is your C 20 okay the other is kind 00:24:05.590 --> 00:24:07.169 align:start position:0% what is your C 20 okay the other is kind of<00:24:05.710> standard<00:24:05.980> ground<00:24:06.490> zero<00:24:06.789> of<00:24:06.970> course 00:24:07.169 --> 00:24:07.179 align:start position:0% of standard ground zero of course 00:24:07.179 --> 00:24:10.560 align:start position:0% of standard ground zero of course simplified<00:24:07.809> because<00:24:08.490> we<00:24:09.490> don't<00:24:09.700> have<00:24:09.880> too 00:24:10.560 --> 00:24:10.570 align:start position:0% simplified because we don't have too 00:24:10.570 --> 00:24:11.269 align:start position:0% simplified because we don't have too much<00:24:10.690> time 00:24:11.269 --> 00:24:11.279 align:start position:0% much time 00:24:11.279 --> 00:24:14.879 align:start position:0% much time okay<00:24:12.279> so<00:24:12.340> first<00:24:12.850> we'll<00:24:13.570> go<00:24:13.720> over<00:24:13.889> specifying 00:24:14.879 --> 00:24:14.889 align:start position:0% okay so first we'll go over specifying 00:24:14.889 --> 00:24:17.490 align:start position:0% okay so first we'll go over specifying functional<00:24:15.399> requirements<00:24:16.149> informal<00:24:17.019> right 00:24:17.490 --> 00:24:17.500 align:start position:0% functional requirements informal right 00:24:17.500 --> 00:24:22.440 align:start position:0% functional requirements informal right and<00:24:17.970> we<00:24:18.970> we<00:24:19.210> go<00:24:19.419> this<00:24:19.779> is<00:24:20.909> fragmented<00:24:21.909> of<00:24:22.090> your 00:24:22.440 --> 00:24:22.450 align:start position:0% and we we go this is fragmented of your 00:24:22.450 --> 00:24:27.389 align:start position:0% and we we go this is fragmented of your C<00:24:22.690> 20<00:24:23.110> interface<00:24:24.600> for<00:24:25.600> those<00:24:25.779> who<00:24:26.019> are<00:24:26.980> not<00:24:27.190> so 00:24:27.389 --> 00:24:27.399 align:start position:0% C 20 interface for those who are not so 00:24:27.399 --> 00:24:31.919 align:start position:0% C 20 interface for those who are not so familiar<00:24:27.580> with<00:24:28.740> the<00:24:29.740> contract<00:24:30.100> si<00:24:30.929> si 00:24:31.919 --> 00:24:31.929 align:start position:0% familiar with the contract si si 00:24:31.929 --> 00:24:34.889 align:start position:0% familiar with the contract si si dimensions<00:24:32.919> one<00:24:33.190> is<00:24:33.309> total<00:24:33.880> supply<00:24:34.240> how<00:24:34.659> many 00:24:34.889 --> 00:24:34.899 align:start position:0% dimensions one is total supply how many 00:24:34.899 --> 00:24:37.399 align:start position:0% dimensions one is total supply how many tokens<00:24:35.320> are<00:24:36.250> in<00:24:36.519> circulation 00:24:37.399 --> 00:24:37.409 align:start position:0% tokens are in circulation 00:24:37.409 --> 00:24:40.799 align:start position:0% tokens are in circulation the<00:24:38.409> average<00:24:38.740> gamma<00:24:39.190> so<00:24:39.519> you<00:24:39.820> can<00:24:40.059> put<00:24:40.389> in<00:24:40.539> how 00:24:40.799 --> 00:24:40.809 align:start position:0% the average gamma so you can put in how 00:24:40.809 --> 00:24:44.279 align:start position:0% the average gamma so you can put in how much<00:24:41.370> tokens<00:24:42.370> given<00:24:43.029> others<00:24:43.480> or<00:24:43.690> accountants 00:24:44.279 --> 00:24:44.289 align:start position:0% much tokens given others or accountants 00:24:44.289 --> 00:24:46.790 align:start position:0% much tokens given others or accountants and<00:24:45.419> the 00:24:46.790 --> 00:24:46.800 align:start position:0% and the 00:24:46.800 --> 00:24:48.770 align:start position:0% and the actual<00:24:47.190> main<00:24:47.400> function<00:24:47.850> here<00:24:48.090> is<00:24:48.360> the 00:24:48.770 --> 00:24:48.780 align:start position:0% actual main function here is the 00:24:48.780 --> 00:24:52.670 align:start position:0% actual main function here is the transfer<00:24:49.170> function<00:24:49.970> with<00:24:50.970> well<00:24:51.210> descended<00:24:51.990> of 00:24:52.670 --> 00:24:52.680 align:start position:0% transfer function with well descended of 00:24:52.680 --> 00:24:54.680 align:start position:0% transfer function with well descended of the<00:24:52.860> transaction<00:24:53.460> right<00:24:53.880> can<00:24:54.210> transfer<00:24:54.660> some 00:24:54.680 --> 00:24:54.690 align:start position:0% the transaction right can transfer some 00:24:54.690 --> 00:24:57.290 align:start position:0% the transaction right can transfer some tokens<00:24:55.350> from<00:24:55.530> its<00:24:55.890> own<00:24:56.190> account<00:24:56.580> to<00:24:57.180> the 00:24:57.290 --> 00:24:57.300 align:start position:0% tokens from its own account to the 00:24:57.300 --> 00:24:59.510 align:start position:0% tokens from its own account to the recipient<00:24:57.870> so<00:24:58.230> we<00:24:58.350> have<00:24:58.530> the<00:24:58.980> other<00:24:59.040> service 00:24:59.510 --> 00:24:59.520 align:start position:0% recipient so we have the other service 00:24:59.520 --> 00:25:01.580 align:start position:0% recipient so we have the other service recipients<00:25:00.060> account<00:25:00.330> and<00:25:00.810> self<00:25:01.230> amount 00:25:01.580 --> 00:25:01.590 align:start position:0% recipients account and self amount 00:25:01.590 --> 00:25:04.070 align:start position:0% recipients account and self amount affected<00:25:02.250> or<00:25:02.430> any<00:25:02.880> tokens<00:25:03.420> sorry<00:25:03.810> not<00:25:04.050> that 00:25:04.070 --> 00:25:04.080 align:start position:0% affected or any tokens sorry not that 00:25:04.080 --> 00:25:05.690 align:start position:0% affected or any tokens sorry not that these<00:25:04.680> tokens<00:25:05.010> add<00:25:05.310> water 00:25:05.690 --> 00:25:05.700 align:start position:0% these tokens add water 00:25:05.700 --> 00:25:10.100 align:start position:0% these tokens add water that's<00:25:06.300> right<00:25:06.810> and<00:25:08.390> now<00:25:09.390> whenever<00:25:09.810> we<00:25:09.960> are 00:25:10.100 --> 00:25:10.110 align:start position:0% that's right and now whenever we are 00:25:10.110 --> 00:25:13.130 align:start position:0% that's right and now whenever we are specifying<00:25:11.240> behavior<00:25:12.240> of<00:25:12.360> contracts<00:25:12.810> we<00:25:12.990> do 00:25:13.130 --> 00:25:13.140 align:start position:0% specifying behavior of contracts we do 00:25:13.140 --> 00:25:15.140 align:start position:0% specifying behavior of contracts we do it<00:25:13.200> over<00:25:13.440> the<00:25:13.860> contract<00:25:14.280> and<00:25:14.430> not<00:25:14.610> over<00:25:15.000> the 00:25:15.140 --> 00:25:15.150 align:start position:0% it over the contract and not over the 00:25:15.150 --> 00:25:18.230 align:start position:0% it over the contract and not over the interface<00:25:15.630> so<00:25:16.560> here<00:25:17.100> at<00:25:17.250> the<00:25:17.400> relevant<00:25:18.000> parts 00:25:18.230 --> 00:25:18.240 align:start position:0% interface so here at the relevant parts 00:25:18.240 --> 00:25:20.240 align:start position:0% interface so here at the relevant parts of<00:25:18.390> the<00:25:18.480> actual<00:25:18.750> contract<00:25:19.200> right<00:25:19.740> so<00:25:19.950> the 00:25:20.240 --> 00:25:20.250 align:start position:0% of the actual contract right so the 00:25:20.250 --> 00:25:22.340 align:start position:0% of the actual contract right so the functions<00:25:20.730> we<00:25:20.910> have<00:25:21.090> the<00:25:21.240> balance<00:25:21.420> the<00:25:22.020> total 00:25:22.340 --> 00:25:22.350 align:start position:0% functions we have the balance the total 00:25:22.350 --> 00:25:24.560 align:start position:0% functions we have the balance the total supply<00:25:22.650> and<00:25:22.950> Varmus<00:25:23.160> become<00:25:24.060> fields<00:25:24.390> in<00:25:24.480> the 00:25:24.560 --> 00:25:24.570 align:start position:0% supply and Varmus become fields in the 00:25:24.570 --> 00:25:26.180 align:start position:0% supply and Varmus become fields in the copy<00:25:24.780> right<00:25:25.320> so<00:25:25.500> these<00:25:25.620> are<00:25:25.680> not<00:25:25.950> private 00:25:26.180 --> 00:25:26.190 align:start position:0% copy right so these are not private 00:25:26.190 --> 00:25:29.390 align:start position:0% copy right so these are not private field<00:25:26.460> search<00:25:27.020> total<00:25:28.020> supply<00:25:28.380> l<00:25:28.920> mapping 00:25:29.390 --> 00:25:29.400 align:start position:0% field search total supply l mapping 00:25:29.400 --> 00:25:31.880 align:start position:0% field search total supply l mapping which<00:25:29.790> says<00:25:30.060> for<00:25:30.420> every<00:25:30.630> other<00:25:31.110> issue<00:25:31.410> account 00:25:31.880 --> 00:25:31.890 align:start position:0% which says for every other issue account 00:25:31.890 --> 00:25:35.360 align:start position:0% which says for every other issue account how<00:25:32.400> many<00:25:32.460> tokens<00:25:33.240> these<00:25:33.540> others<00:25:34.370> possesses 00:25:35.360 --> 00:25:35.370 align:start position:0% how many tokens these others possesses 00:25:35.370 --> 00:25:38.690 align:start position:0% how many tokens these others possesses right<00:25:35.670> so<00:25:35.910> this<00:25:36.570> one<00:25:36.780> is<00:25:36.930> new<00:25:37.860> and<00:25:38.430> which<00:25:38.550> is 00:25:38.690 --> 00:25:38.700 align:start position:0% right so this one is new and which is 00:25:38.700 --> 00:25:42.500 align:start position:0% right so this one is new and which is among<00:25:39.030> others<00:25:40.100> right<00:25:41.100> and<00:25:41.610> here<00:25:41.880> we<00:25:42.060> have<00:25:42.240> some 00:25:42.500 --> 00:25:42.510 align:start position:0% among others right and here we have some 00:25:42.510 --> 00:25:46.250 align:start position:0% among others right and here we have some specification<00:25:43.500> pension<00:25:43.950> transfer<00:25:44.870> now<00:25:45.870> when 00:25:46.250 --> 00:25:46.260 align:start position:0% specification pension transfer now when 00:25:46.260 --> 00:25:49.310 align:start position:0% specification pension transfer now when we're<00:25:46.410> thinking<00:25:46.650> about<00:25:47.090> the<00:25:48.090> context<00:25:48.540> of<00:25:49.050> this 00:25:49.310 --> 00:25:49.320 align:start position:0% we're thinking about the context of this 00:25:49.320 --> 00:25:53.480 align:start position:0% we're thinking about the context of this specifying<00:25:49.980> its<00:25:50.520> its<00:25:50.910> brightness<00:25:51.270> me<00:25:52.490> at 00:25:53.480 --> 00:25:53.490 align:start position:0% specifying its its brightness me at 00:25:53.490 --> 00:25:55.640 align:start position:0% specifying its its brightness me at least<00:25:53.730> as<00:25:53.910> abrasive<00:25:54.210> belt<00:25:54.540> when<00:25:55.020> I<00:25:55.050> am<00:25:55.440> doing 00:25:55.640 --> 00:25:55.650 align:start position:0% least as abrasive belt when I am doing 00:25:55.650 --> 00:25:57.680 align:start position:0% least as abrasive belt when I am doing this<00:25:55.800> piece<00:25:56.040> I<00:25:56.280> never<00:25:56.700> looked<00:25:56.970> it<00:25:57.090> into<00:25:57.570> the 00:25:57.680 --> 00:25:57.690 align:start position:0% this piece I never looked it into the 00:25:57.690 --> 00:26:00.140 align:start position:0% this piece I never looked it into the implementation<00:25:57.980> right<00:25:58.980> so<00:25:59.700> for<00:25:59.910> me<00:26:00.030> the 00:26:00.140 --> 00:26:00.150 align:start position:0% implementation right so for me the 00:26:00.150 --> 00:26:03.140 align:start position:0% implementation right so for me the contact<00:26:00.510> is<00:26:00.990> a<00:26:01.050> black<00:26:01.350> box<00:26:01.590> and<00:26:01.950> that's<00:26:02.910> why<00:26:03.120> I 00:26:03.140 --> 00:26:03.150 align:start position:0% contact is a black box and that's why I 00:26:03.150 --> 00:26:05.390 align:start position:0% contact is a black box and that's why I specifically<00:26:04.080> omitted<00:26:04.560> the<00:26:04.650> body<00:26:04.860> of<00:26:05.250> the 00:26:05.390 --> 00:26:05.400 align:start position:0% specifically omitted the body of the 00:26:05.400 --> 00:26:08.720 align:start position:0% specifically omitted the body of the transformation<00:26:06.150> hey<00:26:06.600> Cheryl<00:26:07.560> ago<00:26:07.890> is<00:26:08.040> to<00:26:08.220> just 00:26:08.720 --> 00:26:08.730 align:start position:0% transformation hey Cheryl ago is to just 00:26:08.730 --> 00:26:10.430 align:start position:0% transformation hey Cheryl ago is to just come<00:26:09.180> up<00:26:09.330> with<00:26:09.360> a<00:26:09.720> couple<00:26:09.900> of<00:26:10.110> properties 00:26:10.430 --> 00:26:10.440 align:start position:0% come up with a couple of properties 00:26:10.440 --> 00:26:13.310 align:start position:0% come up with a couple of properties hopefully<00:26:11.220> food<00:26:11.730> center<00:26:12.690> properties<00:26:13.170> that 00:26:13.310 --> 00:26:13.320 align:start position:0% hopefully food center properties that 00:26:13.320 --> 00:26:16.030 align:start position:0% hopefully food center properties that specified<00:26:13.890> the<00:26:14.040> core<00:26:14.610> behavior<00:26:14.910> of<00:26:15.150> people 00:26:16.030 --> 00:26:16.040 align:start position:0% specified the core behavior of people 00:26:16.040 --> 00:26:20.990 align:start position:0% specified the core behavior of people okay<00:26:17.040> good<00:26:17.960> so<00:26:19.040> let's<00:26:20.040> do<00:26:20.220> this<00:26:20.370> a<00:26:20.640> little<00:26:20.760> bit 00:26:20.990 --> 00:26:21.000 align:start position:0% okay good so let's do this a little bit 00:26:21.000 --> 00:26:22.310 align:start position:0% okay good so let's do this a little bit more<00:26:21.150> interactive 00:26:22.310 --> 00:26:22.320 align:start position:0% more interactive 00:26:22.320 --> 00:26:25.100 align:start position:0% more interactive first<00:26:23.160> properties<00:26:23.640> on<00:26:23.790> me<00:26:23.940> right<00:26:24.480> so<00:26:24.840> we 00:26:25.100 --> 00:26:25.110 align:start position:0% first properties on me right so we 00:26:25.110 --> 00:26:28.220 align:start position:0% first properties on me right so we already<00:26:25.410> saw<00:26:25.650> in<00:26:25.680> our<00:26:25.920> tree<00:26:26.160> it<00:26:27.090> says<00:26:27.330> GC 00:26:28.220 --> 00:26:28.230 align:start position:0% already saw in our tree it says GC 00:26:28.230 --> 00:26:30.740 align:start position:0% already saw in our tree it says GC formally<00:26:28.770> in<00:26:29.040> English<00:26:29.370> of<00:26:29.760> course<00:26:29.820> my<00:26:30.210> always 00:26:30.740 --> 00:26:30.750 align:start position:0% formally in English of course my always 00:26:30.750 --> 00:26:34.610 align:start position:0% formally in English of course my always equals<00:26:31.230> simple<00:26:31.770> powers<00:26:32.330> right<00:26:33.330> so<00:26:34.200> these<00:26:34.350> pans 00:26:34.610 --> 00:26:34.620 align:start position:0% equals simple powers right so these pans 00:26:34.620 --> 00:26:37.700 align:start position:0% equals simple powers right so these pans services<00:26:35.220> specifies<00:26:36.030> an<00:26:36.690> invariance<00:26:37.320> will 00:26:37.700 --> 00:26:37.710 align:start position:0% services specifies an invariance will 00:26:37.710 --> 00:26:39.950 align:start position:0% services specifies an invariance will invent<00:26:38.160> me<00:26:38.400> that<00:26:38.640> the<00:26:38.760> holds<00:26:39.120> of<00:26:39.270> all<00:26:39.510> states 00:26:39.950 --> 00:26:39.960 align:start position:0% invent me that the holds of all states 00:26:39.960 --> 00:26:44.870 align:start position:0% invent me that the holds of all states and<00:26:40.290> we<00:26:40.680> are<00:26:40.740> content<00:26:43.340> something<00:26:44.340> that<00:26:44.640> you 00:26:44.870 --> 00:26:44.880 align:start position:0% and we are content something that you 00:26:44.880 --> 00:26:47.600 align:start position:0% and we are content something that you like<00:26:45.150> the<00:26:45.330> false<00:26:45.590> you<00:26:46.590> know<00:26:46.620> we<00:26:47.340> need<00:26:47.490> to 00:26:47.600 --> 00:26:47.610 align:start position:0% like the false you know we need to 00:26:47.610 --> 00:26:48.200 align:start position:0% like the false you know we need to specify 00:26:48.200 --> 00:26:48.210 align:start position:0% specify 00:26:48.210 --> 00:26:50.970 align:start position:0% specify invariance<00:26:49.140> about<00:26:49.500> the<00:26:49.620> transfer<00:26:50.010> function 00:26:50.970 --> 00:26:50.980 align:start position:0% invariance about the transfer function 00:26:50.980 --> 00:26:54.060 align:start position:0% invariance about the transfer function right<00:26:51.580> so<00:26:52.120> suppose<00:26:53.110> suppose<00:26:53.289> when<00:26:53.649> you<00:26:53.769> start 00:26:54.060 --> 00:26:54.070 align:start position:0% right so suppose suppose when you start 00:26:54.070 --> 00:26:56.460 align:start position:0% right so suppose suppose when you start a<00:26:54.190> transaction<00:26:54.850> with<00:26:55.269> a<00:26:55.299> given<00:26:55.659> transfer 00:26:56.460 --> 00:26:56.470 align:start position:0% a transaction with a given transfer 00:26:56.470 --> 00:26:59.730 align:start position:0% a transaction with a given transfer function<00:26:56.889> you<00:26:56.980> have<00:26:57.190> a<00:26:57.840> specific<00:26:58.840> recipient<00:26:59.620> a 00:26:59.730 --> 00:26:59.740 align:start position:0% function you have a specific recipient a 00:26:59.740 --> 00:27:02.730 align:start position:0% function you have a specific recipient a specific<00:27:00.279> amount<00:27:00.809> and<00:27:01.809> what<00:27:02.409> will<00:27:02.590> be<00:27:02.710> the 00:27:02.730 --> 00:27:02.740 align:start position:0% specific amount and what will be the 00:27:02.740 --> 00:27:07.440 align:start position:0% specific amount and what will be the usual<00:27:03.130> case<00:27:03.610> of<00:27:04.620> so<00:27:05.620> I<00:27:05.950> will<00:27:06.250> move<00:27:06.519> like<00:27:06.730> yes<00:27:07.090> so 00:27:07.440 --> 00:27:07.450 align:start position:0% usual case of so I will move like yes so 00:27:07.450 --> 00:27:10.680 align:start position:0% usual case of so I will move like yes so I<00:27:07.480> would<00:27:07.779> say<00:27:07.929> the<00:27:08.460> amount<00:27:09.460> under<00:27:09.820> of<00:27:10.330> the 00:27:10.680 --> 00:27:10.690 align:start position:0% I would say the amount under of the 00:27:10.690 --> 00:27:12.539 align:start position:0% I would say the amount under of the sender<00:27:10.990> needs<00:27:11.200> decrease<00:27:11.740> the<00:27:11.950> amount<00:27:12.010> of<00:27:12.340> the 00:27:12.539 --> 00:27:12.549 align:start position:0% sender needs decrease the amount of the 00:27:12.549 --> 00:27:14.820 align:start position:0% sender needs decrease the amount of the recipients<00:27:13.450> needs<00:27:13.630> increased<00:27:14.260> by<00:27:14.440> the<00:27:14.500> amount 00:27:14.820 --> 00:27:14.830 align:start position:0% recipients needs increased by the amount 00:27:14.830 --> 00:27:17.850 align:start position:0% recipients needs increased by the amount the<00:27:15.220> balance<00:27:15.580> of<00:27:15.760> the<00:27:16.740> recipient<00:27:17.740> needs 00:27:17.850 --> 00:27:17.860 align:start position:0% the balance of the recipient needs 00:27:17.860 --> 00:27:19.860 align:start position:0% the balance of the recipient needs increased<00:27:18.399> amount<00:27:18.760> and<00:27:19.000> the<00:27:19.090> total<00:27:19.510> supply<00:27:19.690> is 00:27:19.860 --> 00:27:19.870 align:start position:0% increased amount and the total supply is 00:27:19.870 --> 00:27:22.710 align:start position:0% increased amount and the total supply is not<00:27:20.169> allowed<00:27:20.440> to<00:27:20.590> trade<00:27:20.850> the<00:27:21.850> total<00:27:22.179> supply<00:27:22.330> is 00:27:22.710 --> 00:27:22.720 align:start position:0% not allowed to trade the total supply is 00:27:22.720 --> 00:27:24.690 align:start position:0% not allowed to trade the total supply is not<00:27:22.870> allowed<00:27:23.230> to<00:27:23.409> change<00:27:23.590> yes<00:27:23.950> you're<00:27:24.549> right 00:27:24.690 --> 00:27:24.700 align:start position:0% not allowed to change yes you're right 00:27:24.700 --> 00:27:25.320 align:start position:0% not allowed to change yes you're right yes 00:27:25.320 --> 00:27:25.330 align:start position:0% yes 00:27:25.330 --> 00:27:27.990 align:start position:0% yes so<00:27:25.510> this<00:27:25.659> is<00:27:25.840> very<00:27:26.230> good<00:27:26.519> requirement<00:27:27.519> we<00:27:27.970> can 00:27:27.990 --> 00:27:28.000 align:start position:0% so this is very good requirement we can 00:27:28.000 --> 00:27:30.509 align:start position:0% so this is very good requirement we can elaborate<00:27:28.659> a<00:27:28.720> little<00:27:28.809> bit<00:27:29.080> more<00:27:29.200> so<00:27:29.769> just<00:27:30.399> to 00:27:30.509 --> 00:27:30.519 align:start position:0% elaborate a little bit more so just to 00:27:30.519 --> 00:27:33.860 align:start position:0% elaborate a little bit more so just to repeat<00:27:30.669> right<00:27:31.149> you<00:27:31.870> decrease<00:27:32.230> the<00:27:32.260> sender's 00:27:33.860 --> 00:27:33.870 align:start position:0% repeat right you decrease the sender's 00:27:33.870 --> 00:27:36.180 align:start position:0% repeat right you decrease the sender's accounts<00:27:34.870> by<00:27:35.169> the<00:27:35.230> given<00:27:35.649> amount<00:27:35.860> you 00:27:36.180 --> 00:27:36.190 align:start position:0% accounts by the given amount you 00:27:36.190 --> 00:27:38.970 align:start position:0% accounts by the given amount you increase<00:27:36.580> the<00:27:36.940> recipients<00:27:37.539> account<00:27:38.500> when<00:27:38.889> you 00:27:38.970 --> 00:27:38.980 align:start position:0% increase the recipients account when you 00:27:38.980 --> 00:27:40.740 align:start position:0% increase the recipients account when you give<00:27:39.130> on<00:27:39.250> the<00:27:39.340> mouth<00:27:39.490> and<00:27:39.820> total<00:27:40.360> supply<00:27:40.690> it 00:27:40.740 --> 00:27:40.750 align:start position:0% give on the mouth and total supply it 00:27:40.750 --> 00:27:43.590 align:start position:0% give on the mouth and total supply it should<00:27:41.019> remain<00:27:41.289> the<00:27:41.500> same<00:27:41.740> right<00:27:42.370> but<00:27:42.639> one 00:27:43.590 --> 00:27:43.600 align:start position:0% should remain the same right but one 00:27:43.600 --> 00:27:47.190 align:start position:0% should remain the same right but one thing<00:27:43.779> for<00:27:43.929> example<00:27:44.049> of<00:27:44.409> abilities<00:27:46.080> so<00:27:47.080> we 00:27:47.190 --> 00:27:47.200 align:start position:0% thing for example of abilities so we 00:27:47.200 --> 00:27:48.870 align:start position:0% thing for example of abilities so we said<00:27:47.409> the<00:27:47.500> total<00:27:47.620> supply<00:27:47.980> should<00:27:48.159> be<00:27:48.490> the<00:27:48.610> same 00:27:48.870 --> 00:27:48.880 align:start position:0% said the total supply should be the same 00:27:48.880 --> 00:27:51.480 align:start position:0% said the total supply should be the same with<00:27:49.559> these<00:27:50.559> transfer<00:27:51.100> could<00:27:51.309> have 00:27:51.480 --> 00:27:51.490 align:start position:0% with these transfer could have 00:27:51.490 --> 00:27:53.370 align:start position:0% with these transfer could have transferred<00:27:52.059> tokens<00:27:52.690> from<00:27:52.840> another<00:27:53.169> account 00:27:53.370 --> 00:27:53.380 align:start position:0% transferred tokens from another account 00:27:53.380 --> 00:27:56.580 align:start position:0% transferred tokens from another account right<00:27:53.860> so<00:27:54.370> we<00:27:54.730> didn't<00:27:55.000> specify<00:27:55.240> this<00:27:55.600> so<00:27:56.289> what 00:27:56.580 --> 00:27:56.590 align:start position:0% right so we didn't specify this so what 00:27:56.590 --> 00:27:58.830 align:start position:0% right so we didn't specify this so what we<00:27:56.740> get<00:27:56.860> is<00:27:57.039> a<00:27:57.250> partial<00:27:57.730> specification<00:27:58.269> right 00:27:58.830 --> 00:27:58.840 align:start position:0% we get is a partial specification right 00:27:58.840 --> 00:28:01.799 align:start position:0% we get is a partial specification right so<00:27:59.799> in<00:28:00.010> addition<00:28:00.250> to<00:28:00.490> that<00:28:00.639> we<00:28:01.480> need<00:28:01.630> to 00:28:01.799 --> 00:28:01.809 align:start position:0% so in addition to that we need to 00:28:01.809 --> 00:28:04.379 align:start position:0% so in addition to that we need to specify<00:28:02.049> that<00:28:02.440> all<00:28:02.889> other<00:28:03.159> accounts<00:28:03.700> remain 00:28:04.379 --> 00:28:04.389 align:start position:0% specify that all other accounts remain 00:28:04.389 --> 00:28:05.070 align:start position:0% specify that all other accounts remain unchanged 00:28:05.070 --> 00:28:05.080 align:start position:0% unchanged 00:28:05.080 --> 00:28:08.279 align:start position:0% unchanged it's<00:28:05.620> now<00:28:05.799> is<00:28:06.010> the<00:28:06.159> total<00:28:06.279> supply<00:28:06.639> and<00:28:07.330> as<00:28:08.230> a 00:28:08.279 --> 00:28:08.289 align:start position:0% it's now is the total supply and as a 00:28:08.289 --> 00:28:10.409 align:start position:0% it's now is the total supply and as a consequence<00:28:08.919> the<00:28:09.429> totals<00:28:09.760> of<00:28:09.850> 1<00:28:10.029> will<00:28:10.179> also 00:28:10.409 --> 00:28:10.419 align:start position:0% consequence the totals of 1 will also 00:28:10.419 --> 00:28:11.370 align:start position:0% consequence the totals of 1 will also remain<00:28:10.630> unchanged 00:28:11.370 --> 00:28:11.380 align:start position:0% remain unchanged 00:28:11.380 --> 00:28:18.320 align:start position:0% remain unchanged okay<00:28:12.240> okay<00:28:13.240> so<00:28:14.200> we<00:28:14.530> also<00:28:14.680> do<00:28:14.920> this<00:28:15.040> in<00:28:15.570> the<00:28:16.570> case 00:28:18.320 --> 00:28:18.330 align:start position:0% okay okay so we also do this in the case 00:28:18.330 --> 00:28:21.540 align:start position:0% okay okay so we also do this in the case the<00:28:19.800> sentence<00:28:20.800> you<00:28:20.950> can't<00:28:21.160> raise<00:28:21.370> sufficient 00:28:21.540 --> 00:28:21.550 align:start position:0% the sentence you can't raise sufficient 00:28:21.550 --> 00:28:24.450 align:start position:0% the sentence you can't raise sufficient funds<00:28:22.120> right<00:28:22.690> sufficient<00:28:23.320> amount<00:28:23.890> of<00:28:24.010> tokens 00:28:24.450 --> 00:28:24.460 align:start position:0% funds right sufficient amount of tokens 00:28:24.460 --> 00:28:26.700 align:start position:0% funds right sufficient amount of tokens if<00:28:25.210> it<00:28:25.480> doesn't<00:28:25.870> have<00:28:26.050> the<00:28:26.260> function<00:28:26.680> should 00:28:26.700 --> 00:28:26.710 align:start position:0% if it doesn't have the function should 00:28:26.710 --> 00:28:29.310 align:start position:0% if it doesn't have the function should not<00:28:27.220> do<00:28:27.430> anything<00:28:27.910> right<00:28:28.120> so<00:28:28.780> the<00:28:28.900> first<00:28:29.080> case 00:28:29.310 --> 00:28:29.320 align:start position:0% not do anything right so the first case 00:28:29.320 --> 00:28:33.000 align:start position:0% not do anything right so the first case a<00:28:29.650> little<00:28:30.580> bit<00:28:30.700> more<00:28:30.880> elaborately<00:28:31.510> right<00:28:32.080> if 00:28:33.000 --> 00:28:33.010 align:start position:0% a little bit more elaborately right if 00:28:33.010 --> 00:28:34.770 align:start position:0% a little bit more elaborately right if the<00:28:33.190> message<00:28:33.520> center<00:28:33.880> is<00:28:34.060> not<00:28:34.270> equal<00:28:34.600> to<00:28:34.630> be 00:28:34.770 --> 00:28:34.780 align:start position:0% the message center is not equal to be 00:28:34.780 --> 00:28:36.600 align:start position:0% the message center is not equal to be recipient<00:28:35.290> right<00:28:35.650> otherwise<00:28:36.010> you<00:28:36.310> don't<00:28:36.430> have 00:28:36.600 --> 00:28:36.610 align:start position:0% recipient right otherwise you don't have 00:28:36.610 --> 00:28:39.480 align:start position:0% recipient right otherwise you don't have anything<00:28:36.820> to<00:28:37.090> do<00:28:37.240> and<00:28:38.190> there<00:28:39.190> is<00:28:39.280> sufficient 00:28:39.480 --> 00:28:39.490 align:start position:0% anything to do and there is sufficient 00:28:39.490 --> 00:28:42.480 align:start position:0% anything to do and there is sufficient amount<00:28:39.940> of<00:28:40.270> tokens<00:28:40.750> in<00:28:41.230> the<00:28:41.290> balance<00:28:42.040> of<00:28:42.220> the 00:28:42.480 --> 00:28:42.490 align:start position:0% amount of tokens in the balance of the 00:28:42.490 --> 00:28:45.870 align:start position:0% amount of tokens in the balance of the message<00:28:42.790> sender<00:28:43.140> then<00:28:44.400> the<00:28:45.400> most<00:28:45.580> eccentric 00:28:45.870 --> 00:28:45.880 align:start position:0% message sender then the most eccentric 00:28:45.880 --> 00:28:47.550 align:start position:0% message sender then the most eccentric account<00:28:46.390> the<00:28:46.690> balance<00:28:46.990> should<00:28:47.110> be<00:28:47.170> decreased 00:28:47.550 --> 00:28:47.560 align:start position:0% account the balance should be decreased 00:28:47.560 --> 00:28:50.910 align:start position:0% account the balance should be decreased about<00:28:47.860> the<00:28:48.430> balance<00:28:48.790> of<00:28:48.880> the<00:28:49.920> recipient 00:28:50.910 --> 00:28:50.920 align:start position:0% about the balance of the recipient 00:28:50.920 --> 00:28:52.230 align:start position:0% about the balance of the recipient should<00:28:51.040> be<00:28:51.220> increased<00:28:51.520> by<00:28:51.670> the<00:28:51.700> new<00:28:51.970> amount 00:28:52.230 --> 00:28:52.240 align:start position:0% should be increased by the new amount 00:28:52.240 --> 00:28:54.570 align:start position:0% should be increased by the new amount and<00:28:52.510> all<00:28:53.140> remaining<00:28:53.470> balances<00:28:54.100> should<00:28:54.340> remain 00:28:54.570 --> 00:28:54.580 align:start position:0% and all remaining balances should remain 00:28:54.580 --> 00:28:57.810 align:start position:0% and all remaining balances should remain unchanged<00:28:55.770> this<00:28:56.770> is<00:28:56.950> kind<00:28:57.190> of<00:28:57.250> a<00:28:57.370> fairly 00:28:57.810 --> 00:28:57.820 align:start position:0% unchanged this is kind of a fairly 00:28:57.820 --> 00:29:00.780 align:start position:0% unchanged this is kind of a fairly straightforward<00:28:58.680> in<00:28:59.680> formal<00:29:00.100> specification 00:29:00.780 --> 00:29:00.790 align:start position:0% straightforward in formal specification 00:29:00.790 --> 00:29:04.320 align:start position:0% straightforward in formal specification so<00:29:01.600> what<00:29:01.750> will<00:29:01.900> be<00:29:01.990> the<00:29:02.110> remaining<00:29:02.380> days<00:29:03.210> so<00:29:04.210> we 00:29:04.320 --> 00:29:04.330 align:start position:0% so what will be the remaining days so we 00:29:04.330 --> 00:29:13.920 align:start position:0% so what will be the remaining days so we have<00:29:04.480> one<00:29:04.690> more<00:29:04.870> kids 00:29:13.920 --> 00:29:13.930 align:start position:0% 00:29:13.930 --> 00:29:20.620 align:start position:0% balances<00:29:17.500> yes<00:29:18.500> yes<00:29:19.040> you're<00:29:19.580> correct<00:29:19.850> number 00:29:20.620 --> 00:29:20.630 align:start position:0% balances yes yes you're correct number 00:29:20.630 --> 00:29:22.510 align:start position:0% balances yes yes you're correct number of<00:29:20.660> boxes<00:29:21.170> should<00:29:21.350> be<00:29:21.500> the<00:29:21.680> same<00:29:21.890> as<00:29:22.010> the<00:29:22.100> other 00:29:22.510 --> 00:29:22.520 align:start position:0% of boxes should be the same as the other 00:29:22.520 --> 00:29:25.660 align:start position:0% of boxes should be the same as the other specie<00:29:23.030> spent<00:29:23.420> implicitly<00:29:24.110> assumed<00:29:24.710> so<00:29:25.340> if<00:29:25.520> we 00:29:25.660 --> 00:29:25.670 align:start position:0% specie spent implicitly assumed so if we 00:29:25.670 --> 00:29:26.770 align:start position:0% specie spent implicitly assumed so if we go<00:29:25.850> back<00:29:26.030> a<00:29:26.420> little 00:29:26.770 --> 00:29:26.780 align:start position:0% go back a little 00:29:26.780 --> 00:29:29.560 align:start position:0% go back a little this<00:29:27.530> is<00:29:27.680> kind<00:29:27.950> of<00:29:28.010> implicitly<00:29:28.610> assumes<00:29:29.090> we 00:29:29.560 --> 00:29:29.570 align:start position:0% this is kind of implicitly assumes we 00:29:29.570 --> 00:29:31.570 align:start position:0% this is kind of implicitly assumes we have<00:29:29.750> this<00:29:29.930> mapping<00:29:30.440> it<00:29:30.920> is<00:29:31.220> kind<00:29:31.460> of 00:29:31.570 --> 00:29:31.580 align:start position:0% have this mapping it is kind of 00:29:31.580 --> 00:29:34.030 align:start position:0% have this mapping it is kind of continuous<00:29:32.570> containing<00:29:33.200> account<00:29:33.740> for 00:29:34.030 --> 00:29:34.040 align:start position:0% continuous containing account for 00:29:34.040 --> 00:29:36.250 align:start position:0% continuous containing account for everybody<00:29:34.700> every<00:29:35.180> possible<00:29:35.570> address<00:29:35.990> in<00:29:36.140> the 00:29:36.250 --> 00:29:36.260 align:start position:0% everybody every possible address in the 00:29:36.260 --> 00:29:36.640 align:start position:0% everybody every possible address in the world 00:29:36.640 --> 00:29:36.650 align:start position:0% world 00:29:36.650 --> 00:29:39.460 align:start position:0% world it's<00:29:36.980> very<00:29:37.940> large<00:29:38.150> amount<00:29:38.570> of<00:29:38.660> all<00:29:38.870> possible 00:29:39.460 --> 00:29:39.470 align:start position:0% it's very large amount of all possible 00:29:39.470 --> 00:29:43.900 align:start position:0% it's very large amount of all possible addresses<00:29:39.970> it<00:29:40.970> will<00:29:41.480> help<00:29:42.080> the<00:29:42.560> idiom<00:29:43.070> kind<00:29:43.820> of 00:29:43.900 --> 00:29:43.910 align:start position:0% addresses it will help the idiom kind of 00:29:43.910 --> 00:29:45.730 align:start position:0% addresses it will help the idiom kind of fragmented<00:29:44.300> Sarika<00:29:44.960> language<00:29:45.230> takes<00:29:45.470> care<00:29:45.710> of 00:29:45.730 --> 00:29:45.740 align:start position:0% fragmented Sarika language takes care of 00:29:45.740 --> 00:29:59.470 align:start position:0% fragmented Sarika language takes care of this<00:29:46.700> is<00:29:57.910> exactly<00:29:58.910> yes 00:29:59.470 --> 00:29:59.480 align:start position:0% this is exactly yes 00:29:59.480 --> 00:30:02.590 align:start position:0% this is exactly yes so<00:30:00.350> what<00:30:00.770> we<00:30:00.890> do<00:30:01.040> is<00:30:01.250> we<00:30:01.820> consider<00:30:02.150> the 00:30:02.590 --> 00:30:02.600 align:start position:0% so what we do is we consider the 00:30:02.600 --> 00:30:04.240 align:start position:0% so what we do is we consider the alternative<00:30:03.290> things<00:30:03.530> right<00:30:03.830> so<00:30:03.980> weak<00:30:04.130> at 00:30:04.240 --> 00:30:04.250 align:start position:0% alternative things right so weak at 00:30:04.250 --> 00:30:07.000 align:start position:0% alternative things right so weak at least<00:30:04.490> deep<00:30:04.730> in<00:30:05.170> alternative<00:30:06.170> is<00:30:06.350> the<00:30:06.650> logic 00:30:07.000 --> 00:30:07.010 align:start position:0% least deep in alternative is the logic 00:30:07.010 --> 00:30:09.190 align:start position:0% least deep in alternative is the logic indicates<00:30:07.430> the<00:30:07.640> conditionally<00:30:08.360> which<00:30:08.930> means 00:30:09.190 --> 00:30:09.200 align:start position:0% indicates the conditionally which means 00:30:09.200 --> 00:30:11.740 align:start position:0% indicates the conditionally which means that<00:30:09.440> intimacy<00:30:10.160> center<00:30:10.670> is<00:30:10.970> the<00:30:11.210> recipients 00:30:11.740 --> 00:30:11.750 align:start position:0% that intimacy center is the recipients 00:30:11.750 --> 00:30:14.710 align:start position:0% that intimacy center is the recipients or<00:30:12.170> the<00:30:12.920> powers<00:30:13.250> are<00:30:13.640> not<00:30:13.820> sufficient<00:30:14.450> right 00:30:14.710 --> 00:30:14.720 align:start position:0% or the powers are not sufficient right 00:30:14.720 --> 00:30:18.240 align:start position:0% or the powers are not sufficient right all<00:30:15.410> balances<00:30:16.040> should<00:30:16.490> remain<00:30:16.880> and<00:30:17.180> modified 00:30:18.240 --> 00:30:18.250 align:start position:0% all balances should remain and modified 00:30:18.250 --> 00:30:19.970 align:start position:0% all balances should remain and modified right 00:30:19.970 --> 00:30:19.980 align:start position:0% right 00:30:19.980 --> 00:30:24.500 align:start position:0% right yes<00:30:21.590> overflow<00:30:22.590> at<00:30:22.799> this<00:30:22.950> point 00:30:24.500 --> 00:30:24.510 align:start position:0% yes overflow at this point 00:30:24.510 --> 00:30:27.080 align:start position:0% yes overflow at this point I'm<00:30:25.049> not<00:30:25.410> taking<00:30:25.830> into<00:30:26.040> account<00:30:26.100> overflow<00:30:26.820> at 00:30:27.080 --> 00:30:27.090 align:start position:0% I'm not taking into account overflow at 00:30:27.090 --> 00:30:28.820 align:start position:0% I'm not taking into account overflow at this<00:30:27.270> unit<00:30:27.630> yes<00:30:27.870> you<00:30:28.049> are<00:30:28.169> absolutely<00:30:28.290> right 00:30:28.820 --> 00:30:28.830 align:start position:0% this unit yes you are absolutely right 00:30:28.830 --> 00:30:31.880 align:start position:0% this unit yes you are absolutely right so<00:30:29.540> when<00:30:30.540> you're<00:30:30.690> doing<00:30:30.840> specification<00:30:31.710> is 00:30:31.880 --> 00:30:31.890 align:start position:0% so when you're doing specification is 00:30:31.890 --> 00:30:34.580 align:start position:0% so when you're doing specification is very<00:30:32.130> easy<00:30:32.309> to<00:30:32.490> miss<00:30:32.610> um<00:30:32.850> well<00:30:33.780> also<00:30:34.020> the<00:30:34.410> same 00:30:34.580 --> 00:30:34.590 align:start position:0% very easy to miss um well also the same 00:30:34.590 --> 00:30:36.950 align:start position:0% very easy to miss um well also the same way<00:30:34.740> as<00:30:35.040> your<00:30:35.160> problems<00:30:35.549> nothing<00:30:35.730> for<00:30:36.510> example 00:30:36.950 --> 00:30:36.960 align:start position:0% way as your problems nothing for example 00:30:36.960 --> 00:30:39.110 align:start position:0% way as your problems nothing for example here<00:30:37.169> it<00:30:38.070> could<00:30:38.340> happen<00:30:38.610> that<00:30:38.820> these 00:30:39.110 --> 00:30:39.120 align:start position:0% here it could happen that these 00:30:39.120 --> 00:30:43.220 align:start position:0% here it could happen that these conditions<00:30:39.840> here<00:30:40.140> are<00:30:40.380> satisfied<00:30:41.870> when<00:30:42.870> over 00:30:43.220 --> 00:30:43.230 align:start position:0% conditions here are satisfied when over 00:30:43.230 --> 00:30:45.200 align:start position:0% conditions here are satisfied when over hopeful<00:30:43.710> happens<00:30:44.160> because<00:30:44.400> we<00:30:44.700> have<00:30:44.850> modular 00:30:45.200 --> 00:30:45.210 align:start position:0% hopeful happens because we have modular 00:30:45.210 --> 00:30:46.940 align:start position:0% hopeful happens because we have modular arithmetic<00:30:45.390> here<00:30:46.080> within<00:30:46.440> a<00:30:46.500> volume<00:30:46.679> with 00:30:46.940 --> 00:30:46.950 align:start position:0% arithmetic here within a volume with 00:30:46.950 --> 00:30:49.280 align:start position:0% arithmetic here within a volume with addition<00:30:47.610> and<00:30:47.700> subtraction<00:30:48.330> everything 00:30:49.280 --> 00:30:49.290 align:start position:0% addition and subtraction everything 00:30:49.290 --> 00:30:52.490 align:start position:0% addition and subtraction everything works<00:30:50.010> fine<00:30:50.360> even<00:30:51.360> if<00:30:51.480> you<00:30:51.660> overfall 00:30:52.490 --> 00:30:52.500 align:start position:0% works fine even if you overfall 00:30:52.500 --> 00:30:55.220 align:start position:0% works fine even if you overfall something<00:30:53.070> and<00:30:53.270> the<00:30:54.270> bronies<00:30:54.660> will<00:30:54.870> not<00:30:55.140> work 00:30:55.220 --> 00:30:55.230 align:start position:0% something and the bronies will not work 00:30:55.230 --> 00:30:57.620 align:start position:0% something and the bronies will not work or<00:30:55.440> something<00:30:55.740> the<00:30:56.070> actual<00:30:56.549> amount<00:30:57.030> is<00:30:57.419> not 00:30:57.620 --> 00:30:57.630 align:start position:0% or something the actual amount is not 00:30:57.630 --> 00:31:01.210 align:start position:0% or something the actual amount is not the<00:30:57.780> only<00:30:58.580> it's<00:30:59.809> generally<00:31:00.809> not<00:31:00.990> the 00:31:01.210 --> 00:31:01.220 align:start position:0% the only it's generally not the 00:31:01.220 --> 00:31:04.909 align:start position:0% the only it's generally not the gorgeousness<00:31:02.220> attack<00:31:02.760> so<00:31:03.720> in<00:31:03.960> this<00:31:04.169> example<00:31:04.350> I 00:31:04.909 --> 00:31:04.919 align:start position:0% gorgeousness attack so in this example I 00:31:04.919 --> 00:31:09.230 align:start position:0% gorgeousness attack so in this example I don't<00:31:05.250> take<00:31:05.400> into<00:31:05.820> account<00:31:06.950> so<00:31:07.950> what<00:31:08.850> you<00:31:09.030> can 00:31:09.230 --> 00:31:09.240 align:start position:0% don't take into account so what you can 00:31:09.240 --> 00:31:12.049 align:start position:0% don't take into account so what you can do<00:31:09.419> with<00:31:10.380> verax<00:31:10.799> is<00:31:11.130> depending<00:31:11.730> on<00:31:11.880> your 00:31:12.049 --> 00:31:12.059 align:start position:0% do with verax is depending on your 00:31:12.059 --> 00:31:13.909 align:start position:0% do with verax is depending on your property<00:31:12.419> you<00:31:12.510> can<00:31:12.690> specify<00:31:12.900> the<00:31:13.230> situate 00:31:13.909 --> 00:31:13.919 align:start position:0% property you can specify the situate 00:31:13.919 --> 00:31:17.090 align:start position:0% property you can specify the situate that<00:31:14.130> it<00:31:14.850> will<00:31:15.000> automatically<00:31:15.809> fail<00:31:16.500> to 00:31:17.090 --> 00:31:17.100 align:start position:0% that it will automatically fail to 00:31:17.100 --> 00:31:20.450 align:start position:0% that it will automatically fail to verify<00:31:17.549> the<00:31:17.610> overall<00:31:18.270> Stefan<00:31:18.750> right<00:31:19.080> but<00:31:20.010> what 00:31:20.450 --> 00:31:20.460 align:start position:0% verify the overall Stefan right but what 00:31:20.460 --> 00:31:22.610 align:start position:0% verify the overall Stefan right but what we<00:31:20.669> currently<00:31:21.059> do<00:31:21.480> it<00:31:21.630> very<00:31:21.809> easily 00:31:22.610 --> 00:31:22.620 align:start position:0% we currently do it very easily 00:31:22.620 --> 00:31:25.460 align:start position:0% we currently do it very easily we<00:31:22.770> don't<00:31:23.030> explicitly<00:31:24.030> check<00:31:24.480> for<00:31:24.690> goals<00:31:25.110> but 00:31:25.460 --> 00:31:25.470 align:start position:0% we don't explicitly check for goals but 00:31:25.470 --> 00:31:31.090 align:start position:0% we don't explicitly check for goals but you<00:31:25.530> need<00:31:25.830> to<00:31:25.950> write<00:31:26.100> your<00:31:26.220> property<00:31:26.760> situated 00:31:31.090 --> 00:31:31.100 align:start position:0% 00:31:31.100 --> 00:31:34.159 align:start position:0% okay<00:31:32.100> and<00:31:32.580> the<00:31:32.970> other<00:31:33.030> thing<00:31:33.360> is<00:31:33.510> you<00:31:34.140> can 00:31:34.159 --> 00:31:34.169 align:start position:0% okay and the other thing is you can 00:31:34.169 --> 00:31:38.120 align:start position:0% okay and the other thing is you can think<00:31:34.470> of<00:31:34.650> the<00:31:34.830> specification<00:31:36.620> then<00:31:37.620> formula 00:31:38.120 --> 00:31:38.130 align:start position:0% think of the specification then formula 00:31:38.130 --> 00:31:40.850 align:start position:0% think of the specification then formula was<00:31:38.429> referring<00:31:38.880> to<00:31:39.030> actual<00:31:39.990> integers<00:31:40.530> where 00:31:40.850 --> 00:31:40.860 align:start position:0% was referring to actual integers where 00:31:40.860 --> 00:31:43.669 align:start position:0% was referring to actual integers where there<00:31:41.130> is<00:31:41.220> no<00:31:41.400> overall<00:31:41.850> tonight<00:31:42.540> this<00:31:43.530> is 00:31:43.669 --> 00:31:43.679 align:start position:0% there is no overall tonight this is 00:31:43.679 --> 00:31:45.560 align:start position:0% there is no overall tonight this is energies<00:31:44.100> the<00:31:44.190> informal<00:31:44.700> that<00:31:45.090> when<00:31:45.299> you<00:31:45.390> go 00:31:45.560 --> 00:31:45.570 align:start position:0% energies the informal that when you go 00:31:45.570 --> 00:31:47.330 align:start position:0% energies the informal that when you go to<00:31:45.600> actual<00:31:46.049> formal<00:31:46.350> verification<00:31:46.530> you<00:31:47.070> cannot 00:31:47.330 --> 00:31:47.340 align:start position:0% to actual formal verification you cannot 00:31:47.340 --> 00:31:51.919 align:start position:0% to actual formal verification you cannot think<00:31:47.549> means<00:31:48.480> this<00:31:48.900> way<00:31:49.080> right<00:31:50.120> okay<00:31:51.120> so<00:31:51.900> this 00:31:51.919 --> 00:31:51.929 align:start position:0% think means this way right okay so this 00:31:51.929 --> 00:31:54.049 align:start position:0% think means this way right okay so this is<00:31:52.230> your<00:31:52.380> formal<00:31:52.650> requirements<00:31:53.460> for<00:31:53.549> ESD 00:31:54.049 --> 00:31:54.059 align:start position:0% is your formal requirements for ESD 00:31:54.059 --> 00:31:57.560 align:start position:0% is your formal requirements for ESD point<00:31:54.770> okay<00:31:55.850> now<00:31:56.850> let's<00:31:57.120> go<00:31:57.240> through<00:31:57.330> with 00:31:57.560 --> 00:31:57.570 align:start position:0% point okay now let's go through with 00:31:57.570 --> 00:32:00.200 align:start position:0% point okay now let's go through with something<00:31:57.750> slightly<00:31:58.440> more<00:31:58.650> elaborate<00:31:59.210> we 00:32:00.200 --> 00:32:00.210 align:start position:0% something slightly more elaborate we 00:32:00.210 --> 00:32:03.360 align:start position:0% something slightly more elaborate we have<00:32:00.390> a<00:32:00.419> constable 00:32:03.360 --> 00:32:03.370 align:start position:0% 00:32:03.370 --> 00:32:09.360 align:start position:0% and<00:32:05.040> the<00:32:06.040> girls<00:32:06.310> help<00:32:06.580> is<00:32:07.320> the<00:32:08.320> bow<00:32:08.500> feels<00:32:08.800> so 00:32:09.360 --> 00:32:09.370 align:start position:0% and the girls help is the bow feels so 00:32:09.370 --> 00:32:12.020 align:start position:0% and the girls help is the bow feels so accountant<00:32:09.940> self<00:32:10.180> conflict<00:32:10.660> the<00:32:11.290> multiple 00:32:12.020 --> 00:32:12.030 align:start position:0% accountant self conflict the multiple 00:32:12.030 --> 00:32:15.600 align:start position:0% accountant self conflict the multiple enter<00:32:13.030> which<00:32:13.420> is<00:32:13.600> raised<00:32:13.870> the<00:32:14.470> goal<00:32:14.710> at<00:32:15.010> which 00:32:15.600 --> 00:32:15.610 align:start position:0% enter which is raised the goal at which 00:32:15.610 --> 00:32:18.720 align:start position:0% enter which is raised the goal at which you<00:32:15.790> want<00:32:15.970> great<00:32:16.330> and<00:32:16.920> because<00:32:17.920> in<00:32:18.250> faculty 00:32:18.720 --> 00:32:18.730 align:start position:0% you want great and because in faculty 00:32:18.730 --> 00:32:21.510 align:start position:0% you want great and because in faculty culture<00:32:19.290> and<00:32:20.290> behaviour<00:32:20.830> of<00:32:20.890> the<00:32:21.010> conflict<00:32:21.400> is 00:32:21.510 --> 00:32:21.520 align:start position:0% culture and behaviour of the conflict is 00:32:21.520 --> 00:32:23.400 align:start position:0% culture and behaviour of the conflict is that<00:32:21.670> whenever<00:32:22.030> somebody<00:32:22.420> sends<00:32:23.080> money<00:32:23.290> to 00:32:23.400 --> 00:32:23.410 align:start position:0% that whenever somebody sends money to 00:32:23.410 --> 00:32:25.860 align:start position:0% that whenever somebody sends money to the<00:32:23.650> invest<00:32:24.100> right<00:32:25.090> this<00:32:25.300> is<00:32:25.450> a<00:32:25.480> parable 00:32:25.860 --> 00:32:25.870 align:start position:0% the invest right this is a parable 00:32:25.870 --> 00:32:28.590 align:start position:0% the invest right this is a parable function<00:32:26.260> the<00:32:27.220> console<00:32:27.640> control<00:32:27.940> deposit<00:32:28.510> is 00:32:28.590 --> 00:32:28.600 align:start position:0% function the console control deposit is 00:32:28.600 --> 00:32:32.010 align:start position:0% function the console control deposit is ready<00:32:28.840> into<00:32:29.170> the<00:32:29.230> escrow<00:32:29.730> right<00:32:30.780> and<00:32:31.780> it's 00:32:32.010 --> 00:32:32.020 align:start position:0% ready into the escrow right and it's 00:32:32.020 --> 00:32:35.610 align:start position:0% ready into the escrow right and it's when<00:32:32.740> somebody<00:32:33.400> walks<00:32:33.580> close<00:32:34.060> and<00:32:34.570> it's<00:32:34.810> about 00:32:35.610 --> 00:32:35.620 align:start position:0% when somebody walks close and it's about 00:32:35.620 --> 00:32:38.460 align:start position:0% when somebody walks close and it's about time<00:32:36.010> to<00:32:36.220> get<00:32:36.370> close<00:32:36.760> right<00:32:37.360> after<00:32:37.990> the<00:32:38.290> tall 00:32:38.460 --> 00:32:38.470 align:start position:0% time to get close right after the tall 00:32:38.470 --> 00:32:40.920 align:start position:0% time to get close right after the tall stack<00:32:38.710> has<00:32:38.920> passed<00:32:39.220> and<00:32:40.030> the<00:32:40.060> many<00:32:40.450> countries 00:32:40.920 --> 00:32:40.930 align:start position:0% stack has passed and the many countries 00:32:40.930 --> 00:32:44.670 align:start position:0% stack has passed and the many countries we<00:32:41.230> have<00:32:41.260> two<00:32:41.590> options<00:32:42.010> either<00:32:42.900> the<00:32:43.900> goal<00:32:44.440> was 00:32:44.670 --> 00:32:44.680 align:start position:0% we have two options either the goal was 00:32:44.680 --> 00:32:47.130 align:start position:0% we have two options either the goal was raised<00:32:44.950> in<00:32:45.760> which<00:32:46.000> case<00:32:46.270> the<00:32:46.510> beneficiary<00:32:47.110> of 00:32:47.130 --> 00:32:47.140 align:start position:0% raised in which case the beneficiary of 00:32:47.140 --> 00:32:49.140 align:start position:0% raised in which case the beneficiary of the<00:32:47.350> tunnel<00:32:47.620> cell<00:32:47.830> and<00:32:48.370> we<00:32:48.520> drove<00:32:48.760> the<00:32:48.970> money 00:32:49.140 --> 00:32:49.150 align:start position:0% the tunnel cell and we drove the money 00:32:49.150 --> 00:32:52.050 align:start position:0% the tunnel cell and we drove the money from<00:32:49.420> the<00:32:49.600> escrow<00:32:50.080> or<00:32:51.010> the<00:32:51.400> goal<00:32:51.580> was<00:32:51.880> not 00:32:52.050 --> 00:32:52.060 align:start position:0% from the escrow or the goal was not 00:32:52.060 --> 00:32:54.930 align:start position:0% from the escrow or the goal was not produced<00:32:52.450> in<00:32:52.750> which<00:32:53.080> case<00:32:53.770> the<00:32:54.010> investors<00:32:54.640> can 00:32:54.930 --> 00:32:54.940 align:start position:0% produced in which case the investors can 00:32:54.940 --> 00:32:57.690 align:start position:0% produced in which case the investors can play<00:32:55.390> different<00:32:55.990> for<00:32:56.380> the<00:32:56.560> actor<00:32:57.070> which<00:32:57.460> will 00:32:57.690 --> 00:32:57.700 align:start position:0% play different for the actor which will 00:32:57.700 --> 00:32:59.790 align:start position:0% play different for the actor which will be<00:32:57.910> said<00:32:58.150> and<00:32:58.480> this<00:32:59.110> logic<00:32:59.500> should<00:32:59.650> be 00:32:59.790 --> 00:32:59.800 align:start position:0% be said and this logic should be 00:32:59.800 --> 00:33:02.970 align:start position:0% be said and this logic should be realized<00:33:00.550> in<00:33:00.850> the<00:33:00.970> tester<00:33:01.300> ownership<00:33:01.810> so<00:33:02.680> here 00:33:02.970 --> 00:33:02.980 align:start position:0% realized in the tester ownership so here 00:33:02.980 --> 00:33:05.970 align:start position:0% realized in the tester ownership so here what<00:33:03.160> we<00:33:03.280> do<00:33:03.400> that<00:33:03.580> is<00:33:03.810> marketed<00:33:04.810> deposits<00:33:05.290> our 00:33:05.970 --> 00:33:05.980 align:start position:0% what we do that is marketed deposits our 00:33:05.980 --> 00:33:08.820 align:start position:0% what we do that is marketed deposits our money<00:33:06.480> how<00:33:07.480> much<00:33:07.600> I<00:33:07.840> turn<00:33:08.050> each<00:33:08.290> other<00:33:08.650> is 00:33:08.820 --> 00:33:08.830 align:start position:0% money how much I turn each other is 00:33:08.830 --> 00:33:11.640 align:start position:0% money how much I turn each other is deposited<00:33:09.400> into<00:33:09.640> escrow<00:33:10.150> and<00:33:10.420> to<00:33:10.930> beneficiary 00:33:11.640 --> 00:33:11.650 align:start position:0% deposited into escrow and to beneficiary 00:33:11.650 --> 00:33:15.450 align:start position:0% deposited into escrow and to beneficiary who<00:33:12.190> in<00:33:12.910> case<00:33:13.210> of<00:33:13.420> success<00:33:13.630> will<00:33:14.380> receive<00:33:15.190> all 00:33:15.450 --> 00:33:15.460 align:start position:0% who in case of success will receive all 00:33:15.460 --> 00:33:18.900 align:start position:0% who in case of success will receive all the<00:33:15.580> way<00:33:16.500> so<00:33:17.500> on<00:33:17.650> let's<00:33:17.890> let's<00:33:18.370> try<00:33:18.460> to<00:33:18.580> specify 00:33:18.900 --> 00:33:18.910 align:start position:0% the way so on let's let's try to specify 00:33:18.910 --> 00:33:22.810 align:start position:0% the way so on let's let's try to specify this<00:33:19.270> again<00:33:19.810> important<00:33:20.470> right<00:33:21.070> so 00:33:22.810 --> 00:33:22.820 align:start position:0% this again important right so 00:33:22.820 --> 00:33:27.770 align:start position:0% this again important right so again<00:33:23.820> let's<00:33:24.270> do<00:33:24.540> the<00:33:24.570> placement<00:33:25.610> so<00:33:26.610> the<00:33:27.480> goal 00:33:27.770 --> 00:33:27.780 align:start position:0% again let's do the placement so the goal 00:33:27.780 --> 00:33:31.299 align:start position:0% again let's do the placement so the goal and<00:33:28.080> call<00:33:28.350> time<00:33:28.650> always<00:33:29.460> remain<00:33:29.940> the<00:33:30.240> same 00:33:31.299 --> 00:33:31.309 align:start position:0% and call time always remain the same 00:33:31.309 --> 00:33:33.620 align:start position:0% and call time always remain the same right<00:33:32.309> so<00:33:32.340> so<00:33:32.700> this<00:33:32.880> might<00:33:33.059> look<00:33:33.300> like<00:33:33.360> a 00:33:33.620 --> 00:33:33.630 align:start position:0% right so so this might look like a 00:33:33.630 --> 00:33:38.380 align:start position:0% right so so this might look like a stupid<00:33:34.170> in<00:33:34.470> formal<00:33:34.830> requirements<00:33:35.809> but<00:33:37.070> in 00:33:38.380 --> 00:33:38.390 align:start position:0% stupid in formal requirements but in 00:33:38.390 --> 00:33:41.900 align:start position:0% stupid in formal requirements but in incivility<00:33:39.470> these<00:33:40.470> things<00:33:40.770> can<00:33:41.070> change<00:33:41.100> like 00:33:41.900 --> 00:33:41.910 align:start position:0% incivility these things can change like 00:33:41.910 --> 00:33:43.850 align:start position:0% incivility these things can change like the<00:33:42.090> skills<00:33:42.390> of<00:33:42.510> your<00:33:42.570> contract<00:33:43.200> decent<00:33:43.620> stuff 00:33:43.850 --> 00:33:43.860 align:start position:0% the skills of your contract decent stuff 00:33:43.860 --> 00:33:46.580 align:start position:0% the skills of your contract decent stuff in<00:33:44.100> storage<00:33:44.900> potentially<00:33:45.900> they<00:33:46.080> can<00:33:46.290> change 00:33:46.580 --> 00:33:46.590 align:start position:0% in storage potentially they can change 00:33:46.590 --> 00:33:50.000 align:start position:0% in storage potentially they can change so<00:33:47.510> because<00:33:48.510> of<00:33:48.690> this<00:33:48.840> we<00:33:49.620> need<00:33:49.800> to<00:33:49.890> be 00:33:50.000 --> 00:33:50.010 align:start position:0% so because of this we need to be 00:33:50.010 --> 00:33:51.710 align:start position:0% so because of this we need to be explicit<00:33:50.550> about<00:33:50.670> which<00:33:51.059> things<00:33:51.300> do<00:33:51.510> remain 00:33:51.710 --> 00:33:51.720 align:start position:0% explicit about which things do remain 00:33:51.720 --> 00:33:56.570 align:start position:0% explicit about which things do remain constant<00:33:52.500> or<00:33:53.210> shapes<00:33:54.350> can<00:33:55.350> change<00:33:56.070> that 00:33:56.570 --> 00:33:56.580 align:start position:0% constant or shapes can change that 00:33:56.580 --> 00:33:59.510 align:start position:0% constant or shapes can change that services<00:33:57.300> a<00:33:57.800> requirement<00:33:58.800> that<00:33:58.860> is<00:33:59.010> all<00:33:59.190> all 00:33:59.510 --> 00:33:59.520 align:start position:0% services a requirement that is all all 00:33:59.520 --> 00:34:11.770 align:start position:0% services a requirement that is all all optimists<00:34:00.360> and<00:34:00.510> people<00:34:04.040> other<00:34:05.040> suggestions 00:34:11.770 --> 00:34:11.780 align:start position:0% 00:34:11.780 --> 00:34:14.560 align:start position:0% right<00:34:12.440> so<00:34:12.590> just<00:34:13.040> to<00:34:13.250> implement<00:34:13.550> the<00:34:14.389> logic 00:34:14.560 --> 00:34:14.570 align:start position:0% right so just to implement the logic 00:34:14.570 --> 00:34:16.960 align:start position:0% right so just to implement the logic that<00:34:14.899> we<00:34:14.960> informally<00:34:15.710> is<00:34:15.950> tied<00:34:16.190> now<00:34:16.399> in<00:34:16.760> the 00:34:16.960 --> 00:34:16.970 align:start position:0% that we informally is tied now in the 00:34:16.970 --> 00:34:19.990 align:start position:0% that we informally is tied now in the informal<00:34:17.419> language<00:34:17.540> no<00:34:18.169> need<00:34:18.470> to<00:34:19.429> be<00:34:19.580> very 00:34:19.990 --> 00:34:20.000 align:start position:0% informal language no need to be very 00:34:20.000 --> 00:34:23.770 align:start position:0% informal language no need to be very sensitive 00:34:23.770 --> 00:34:23.780 align:start position:0% 00:34:23.780 --> 00:34:26.680 align:start position:0% sorry<00:34:24.560> close<00:34:25.100> some<00:34:25.429> we<00:34:25.580> will<00:34:25.820> only<00:34:26.240> work<00:34:26.510> in 00:34:26.680 --> 00:34:26.690 align:start position:0% sorry close some we will only work in 00:34:26.690 --> 00:34:29.230 align:start position:0% sorry close some we will only work in the<00:34:26.810> past<00:34:27.020> the<00:34:27.440> first<00:34:27.649> time<00:34:27.860> those<00:34:28.639> who<00:34:28.669> only 00:34:29.230 --> 00:34:29.240 align:start position:0% the past the first time those who only 00:34:29.240 --> 00:34:35.169 align:start position:0% the past the first time those who only work<00:34:29.510> if<00:34:29.750> you<00:34:29.929> ask<00:34:30.320> because<00:34:31.300> yes<00:34:33.850> so<00:34:34.850> what<00:34:35.030> does 00:34:35.169 --> 00:34:35.179 align:start position:0% work if you ask because yes so what does 00:34:35.179 --> 00:34:35.770 align:start position:0% work if you ask because yes so what does this<00:34:35.270> mean 00:34:35.770 --> 00:34:35.780 align:start position:0% this mean 00:34:35.780 --> 00:34:37.930 align:start position:0% this mean because<00:34:36.080> we<00:34:36.320> only<00:34:36.590> work<00:34:36.860> if<00:34:37.220> it<00:34:37.399> was<00:34:37.580> to<00:34:37.760> close 00:34:37.930 --> 00:34:37.940 align:start position:0% because we only work if it was to close 00:34:37.940 --> 00:34:45.250 align:start position:0% because we only work if it was to close them<00:34:38.240> sorry<00:34:39.250> now<00:34:41.290> first<00:34:42.290> time 00:34:45.250 --> 00:34:45.260 align:start position:0% 00:34:45.260 --> 00:34:47.590 align:start position:0% well<00:34:46.129> if<00:34:46.310> not<00:34:46.790> with<00:34:46.940> less<00:34:47.090> than<00:34:47.240> clothesline 00:34:47.590 --> 00:34:47.600 align:start position:0% well if not with less than clothesline 00:34:47.600 --> 00:34:50.680 align:start position:0% well if not with less than clothesline call<00:34:48.230> the<00:34:48.350> co-sponsor 00:34:50.680 --> 00:34:50.690 align:start position:0% call the co-sponsor 00:34:50.690 --> 00:34:53.890 align:start position:0% call the co-sponsor must<00:34:51.440> be<00:34:51.560> done<00:34:51.740> successful<00:34:52.340> yes<00:34:52.610> yes<00:34:53.090> so<00:34:53.540> you 00:34:53.890 --> 00:34:53.900 align:start position:0% must be done successful yes yes so you 00:34:53.900 --> 00:34:56.320 align:start position:0% must be done successful yes yes so you can<00:34:54.110> specify<00:34:54.290> that<00:34:54.590> this<00:34:54.950> this<00:34:55.490> is<00:34:55.550> one<00:34:55.700> option 00:34:56.320 --> 00:34:56.330 align:start position:0% can specify that this this is one option 00:34:56.330 --> 00:34:57.970 align:start position:0% can specify that this this is one option oh<00:34:56.360> let<00:34:56.840> me<00:34:56.870> see<00:34:56.990> what's<00:34:57.320> the<00:34:57.500> like<00:34:57.650> nice 00:34:57.970 --> 00:34:57.980 align:start position:0% oh let me see what's the like nice 00:34:57.980 --> 00:35:00.460 align:start position:0% oh let me see what's the like nice property<00:34:58.160> I<00:34:58.520> specify<00:34:59.060> here<00:34:59.330> is<00:34:59.480> because<00:34:59.840> yes 00:35:00.460 --> 00:35:00.470 align:start position:0% property I specify here is because yes 00:35:00.470 --> 00:35:04.240 align:start position:0% property I specify here is because yes but<00:35:01.100> maybe<00:35:01.960> maybe<00:35:02.960> it's<00:35:03.410> something<00:35:03.770> along<00:35:03.890> the 00:35:04.240 --> 00:35:04.250 align:start position:0% but maybe maybe it's something along the 00:35:04.250 --> 00:35:06.730 align:start position:0% but maybe maybe it's something along the lines<00:35:04.460> of<00:35:04.640> close<00:35:04.880> so<00:35:05.270> what<00:35:05.420> does<00:35:05.600> it<00:35:05.750> say<00:35:05.780> soon 00:35:06.730 --> 00:35:06.740 align:start position:0% lines of close so what does it say soon 00:35:06.740 --> 00:35:08.500 align:start position:0% lines of close so what does it say soon if<00:35:07.010> you<00:35:07.190> know<00:35:07.370> it's<00:35:07.640> it's<00:35:07.940> something<00:35:08.150> else 00:35:08.500 --> 00:35:08.510 align:start position:0% if you know it's it's something else 00:35:08.510 --> 00:35:13.780 align:start position:0% if you know it's it's something else right<00:35:09.170> itself<00:35:09.820> so<00:35:12.040> here<00:35:13.040> just<00:35:13.340> for<00:35:13.490> the<00:35:13.610> sake 00:35:13.780 --> 00:35:13.790 align:start position:0% right itself so here just for the sake 00:35:13.790 --> 00:35:16.570 align:start position:0% right itself so here just for the sake of<00:35:13.940> the<00:35:14.330> workshop<00:35:14.930> I<00:35:15.470> have<00:35:15.950> the<00:35:16.100> properties 00:35:16.570 --> 00:35:16.580 align:start position:0% of the workshop I have the properties 00:35:16.580 --> 00:35:19.510 align:start position:0% of the workshop I have the properties fixed<00:35:17.030> so<00:35:17.680> welcome<00:35:18.680> to<00:35:18.830> say<00:35:19.010> any<00:35:19.160> proper<00:35:19.490> cases 00:35:19.510 --> 00:35:19.520 align:start position:0% fixed so welcome to say any proper cases 00:35:19.520 --> 00:35:22.780 align:start position:0% fixed so welcome to say any proper cases I<00:35:20.060> will<00:35:21.020> add<00:35:21.260> them<00:35:21.440> to<00:35:21.590> the<00:35:21.680> slides<00:35:21.950> images 00:35:22.780 --> 00:35:22.790 align:start position:0% I will add them to the slides images 00:35:22.790 --> 00:35:24.520 align:start position:0% I will add them to the slides images work<00:35:23.060> with<00:35:23.390> something<00:35:23.780> says<00:35:23.960> the<00:35:24.080> properties 00:35:24.520 --> 00:35:24.530 align:start position:0% work with something says the properties 00:35:24.530 --> 00:35:27.790 align:start position:0% work with something says the properties and<00:35:25.130> property<00:35:25.670> B<00:35:25.850> here's<00:35:26.180> a<00:35:26.300> similar<00:35:27.110> investor 00:35:27.790 --> 00:35:27.800 align:start position:0% and property B here's a similar investor 00:35:27.800 --> 00:35:30.430 align:start position:0% and property B here's a similar investor proposes<00:35:28.250> equals<00:35:29.060> the<00:35:29.240> vector<00:35:29.450> in<00:35:29.840> escrow 00:35:30.430 --> 00:35:30.440 align:start position:0% proposes equals the vector in escrow 00:35:30.440 --> 00:35:34.360 align:start position:0% proposes equals the vector in escrow unless<00:35:30.920> to<00:35:31.370> be<00:35:31.610> successful<00:35:32.210> so<00:35:33.070> this<00:35:34.070> means 00:35:34.360 --> 00:35:34.370 align:start position:0% unless to be successful so this means 00:35:34.370 --> 00:35:37.870 align:start position:0% unless to be successful so this means that<00:35:34.630> you<00:35:35.630> can<00:35:35.840> also<00:35:35.960> grow<00:35:36.350> or<00:35:36.740> change<00:35:36.880> money 00:35:37.870 --> 00:35:37.880 align:start position:0% that you can also grow or change money 00:35:37.880 --> 00:35:47.140 align:start position:0% that you can also grow or change money from<00:35:39.670> SPSS<00:35:43.690> okay<00:35:44.690> so<00:35:45.580> let's<00:35:46.580> see<00:35:46.730> sound 00:35:47.140 --> 00:35:47.150 align:start position:0% from SPSS okay so let's see sound 00:35:47.150 --> 00:35:50.260 align:start position:0% from SPSS okay so let's see sound something<00:35:47.600> more<00:35:48.490> escrow<00:35:49.490> never<00:35:49.820> allow<00:35:50.210> the 00:35:50.260 --> 00:35:50.270 align:start position:0% something more escrow never allow the 00:35:50.270 --> 00:35:52.090 align:start position:0% something more escrow never allow the pot<00:35:50.570> with<00:35:50.780> drawing<00:35:51.110> and<00:35:51.410> painting<00:35:51.920> the 00:35:52.090 --> 00:35:52.100 align:start position:0% pot with drawing and painting the 00:35:52.100 --> 00:35:54.190 align:start position:0% pot with drawing and painting the movements<00:35:52.490> I<00:35:52.670> said<00:35:53.390> this<00:35:53.480> was<00:35:53.690> one<00:35:53.900> of<00:35:53.930> the 00:35:54.190 --> 00:35:54.200 align:start position:0% movements I said this was one of the 00:35:54.200 --> 00:35:57.730 align:start position:0% movements I said this was one of the requirements<00:35:54.740> we 00:35:57.730 --> 00:35:57.740 align:start position:0% 00:35:57.740 --> 00:36:01.660 align:start position:0% and<00:35:58.210> more<00:35:59.260> yes<00:36:00.260> investors<00:36:01.130> cannot<00:36:01.430> claim 00:36:01.660 --> 00:36:01.670 align:start position:0% and more yes investors cannot claim 00:36:01.670 --> 00:36:05.670 align:start position:0% and more yes investors cannot claim refunds<00:36:02.150> after<00:36:02.450> council<00:36:03.200> goal<00:36:03.710> is<00:36:03.950> reached 00:36:05.670 --> 00:36:05.680 align:start position:0% refunds after council goal is reached 00:36:05.680 --> 00:36:09.160 align:start position:0% refunds after council goal is reached and<00:36:06.680> thank<00:36:07.160> you<00:36:07.430> you<00:36:07.970> can<00:36:08.180> figure<00:36:08.330> out<00:36:08.480> what 00:36:09.160 --> 00:36:09.170 align:start position:0% and thank you you can figure out what 00:36:09.170 --> 00:36:10.870 align:start position:0% and thank you you can figure out what would<00:36:09.290> be<00:36:09.470> the<00:36:09.860> complement<00:36:10.369> to<00:36:10.460> this<00:36:10.640> no 00:36:10.870 --> 00:36:10.880 align:start position:0% would be the complement to this no 00:36:10.880 --> 00:36:14.140 align:start position:0% would be the complement to this no problem<00:36:10.910> and<00:36:11.420> the<00:36:11.480> complementary<00:36:12.140> for<00:36:13.150> the 00:36:14.140 --> 00:36:14.150 align:start position:0% problem and the complementary for the 00:36:14.150 --> 00:36:16.780 align:start position:0% problem and the complementary for the next<00:36:14.510> property<00:36:14.900> needed<00:36:15.380> to<00:36:15.619> talk<00:36:16.010> about<00:36:16.280> this 00:36:16.780 --> 00:36:16.790 align:start position:0% next property needed to talk about this 00:36:16.790 --> 00:36:20.320 align:start position:0% next property needed to talk about this this<00:36:17.420> behavior<00:36:17.930> gets<00:36:19.030> beneficiary<00:36:20.030> can 00:36:20.320 --> 00:36:20.330 align:start position:0% this behavior gets beneficiary can 00:36:20.330 --> 00:36:22.630 align:start position:0% this behavior gets beneficiary can withdraw<00:36:20.540> after<00:36:21.170> cross<00:36:21.590> so<00:36:21.860> beneficiary<00:36:22.490> can 00:36:22.630 --> 00:36:22.640 align:start position:0% withdraw after cross so beneficiary can 00:36:22.640 --> 00:36:24.700 align:start position:0% withdraw after cross so beneficiary can only<00:36:22.850> withdraw<00:36:23.150> off<00:36:23.390> the<00:36:23.540> cross<00:36:23.750> cell<00:36:23.960> voltage 00:36:24.700 --> 00:36:24.710 align:start position:0% only withdraw off the cross cell voltage 00:36:24.710 --> 00:36:29.020 align:start position:0% only withdraw off the cross cell voltage yes<00:36:25.100> beneficiary<00:36:25.850> can<00:36:26.000> only<00:36:26.240> withdraw<00:36:26.540> a<00:36:28.030> nice 00:36:29.020 --> 00:36:29.030 align:start position:0% yes beneficiary can only withdraw a nice 00:36:29.030 --> 00:36:35.050 align:start position:0% yes beneficiary can only withdraw a nice color<00:36:29.300> could<00:36:29.630> tell<00:36:29.869> sahabis<00:36:30.440> reach<00:36:33.880> you<00:36:34.880> can 00:36:35.050 --> 00:36:35.060 align:start position:0% color could tell sahabis reach you can 00:36:35.060 --> 00:36:37.120 align:start position:0% color could tell sahabis reach you can say<00:36:35.240> something<00:36:35.690> in<00:36:35.780> many<00:36:35.990> ways<00:36:36.200> stone<00:36:36.470> yes<00:36:36.890> but 00:36:37.120 --> 00:36:37.130 align:start position:0% say something in many ways stone yes but 00:36:37.130 --> 00:36:39.070 align:start position:0% say something in many ways stone yes but it's<00:36:37.310> the<00:36:37.369> same<00:36:37.700> so<00:36:37.910> when<00:36:38.450> efficient<00:36:38.810> cannot 00:36:39.070 --> 00:36:39.080 align:start position:0% it's the same so when efficient cannot 00:36:39.080 --> 00:36:43.630 align:start position:0% it's the same so when efficient cannot be<00:36:39.200> dropped<00:36:39.440> before<00:36:39.619> L<00:36:40.070> cell<00:36:40.340> voltage<00:36:41.920> so<00:36:42.920> we 00:36:43.630 --> 00:36:43.640 align:start position:0% be dropped before L cell voltage so we 00:36:43.640 --> 00:36:48.790 align:start position:0% be dropped before L cell voltage so we have<00:36:43.820> these<00:36:44.030> I<00:36:45.760> now<00:36:46.760> this<00:36:47.300> is<00:36:47.630> most<00:36:48.140> likely<00:36:48.410> in 00:36:48.790 --> 00:36:48.800 align:start position:0% have these I now this is most likely in 00:36:48.800 --> 00:36:52.090 align:start position:0% have these I now this is most likely in complete<00:36:49.340> specification<00:36:50.619> the<00:36:51.619> behavior<00:36:52.070> of 00:36:52.090 --> 00:36:52.100 align:start position:0% complete specification the behavior of 00:36:52.100 --> 00:36:53.859 align:start position:0% complete specification the behavior of the<00:36:52.280> calcium<00:36:52.640> so<00:36:53.090> providing<00:36:53.600> the<00:36:53.720> full 00:36:53.859 --> 00:36:53.869 align:start position:0% the calcium so providing the full 00:36:53.869 --> 00:36:56.740 align:start position:0% the calcium so providing the full complete<00:36:54.170> specification<00:36:54.520> is<00:36:55.520> a<00:36:55.790> difficult 00:36:56.740 --> 00:36:56.750 align:start position:0% complete specification is a difficult 00:36:56.750 --> 00:37:00.609 align:start position:0% complete specification is a difficult exercise<00:36:56.930> and<00:36:58.869> whenever<00:36:59.869> you<00:37:00.020> have<00:37:00.110> defined 00:37:00.609 --> 00:37:00.619 align:start position:0% exercise and whenever you have defined 00:37:00.619 --> 00:37:02.530 align:start position:0% exercise and whenever you have defined your<00:37:00.710> context<00:37:01.460> you<00:37:01.670> don't<00:37:01.940> need<00:37:02.119> to<00:37:02.300> do<00:37:02.510> it 00:37:02.530 --> 00:37:02.540 align:start position:0% your context you don't need to do it 00:37:02.540 --> 00:37:05.200 align:start position:0% your context you don't need to do it depends<00:37:03.140> but<00:37:03.500> this<00:37:03.680> means<00:37:03.890> you<00:37:04.760> should<00:37:04.790> always 00:37:05.200 --> 00:37:05.210 align:start position:0% depends but this means you should always 00:37:05.210 --> 00:37:06.940 align:start position:0% depends but this means you should always keep<00:37:05.480> in<00:37:05.660> mind<00:37:05.869> the<00:37:05.990> facilitator<00:37:06.590> finished 00:37:06.940 --> 00:37:06.950 align:start position:0% keep in mind the facilitator finished 00:37:06.950 --> 00:37:11.740 align:start position:0% keep in mind the facilitator finished some<00:37:07.190> news<00:37:08.830> so<00:37:09.830> now<00:37:10.490> we<00:37:11.119> have<00:37:11.300> a<00:37:11.330> bunch<00:37:11.600> of 00:37:11.740 --> 00:37:11.750 align:start position:0% some news so now we have a bunch of 00:37:11.750 --> 00:37:14.050 align:start position:0% some news so now we have a bunch of properties<00:37:12.230> and<00:37:12.950> what<00:37:13.160> we<00:37:13.310> can<00:37:13.490> do<00:37:13.640> is<00:37:13.730> we<00:37:13.910> can 00:37:14.050 --> 00:37:14.060 align:start position:0% properties and what we can do is we can 00:37:14.060 --> 00:37:17.220 align:start position:0% properties and what we can do is we can just<00:37:14.270> attempt<00:37:14.840> to<00:37:14.930> formalize<00:37:15.710> them<00:37:16.010> and 00:37:17.220 --> 00:37:17.230 align:start position:0% just attempt to formalize them and 00:37:17.230 --> 00:37:19.359 align:start position:0% just attempt to formalize them and specify<00:37:18.230> them<00:37:18.470> in<00:37:18.950> the<00:37:19.040> barracks 00:37:19.359 --> 00:37:19.369 align:start position:0% specify them in the barracks 00:37:19.369 --> 00:37:22.109 align:start position:0% specify them in the barracks specification<00:37:20.090> language<00:37:20.359> and<00:37:20.600> try<00:37:20.720> to<00:37:20.780> verify 00:37:22.109 --> 00:37:22.119 align:start position:0% specification language and try to verify 00:37:22.119 --> 00:37:26.420 align:start position:0% specification language and try to verify ok<00:37:23.260> any<00:37:24.260> questions 00:37:26.420 --> 00:37:26.430 align:start position:0% ok any questions 00:37:26.430 --> 00:37:30.060 align:start position:0% ok any questions one<00:37:27.430> question<00:37:27.640> is<00:37:28.359> as<00:37:29.200> you're<00:37:29.530> going<00:37:29.770> through 00:37:30.060 --> 00:37:30.070 align:start position:0% one question is as you're going through 00:37:30.070 --> 00:37:33.990 align:start position:0% one question is as you're going through the<00:37:30.250> requirements<00:37:31.119> is<00:37:31.990> you<00:37:32.560> saw<00:37:32.770> that<00:37:33.040> if<00:37:33.910> you 00:37:33.990 --> 00:37:34.000 align:start position:0% the requirements is you saw that if you 00:37:34.000 --> 00:37:37.880 align:start position:0% the requirements is you saw that if you go<00:37:34.150> back<00:37:34.359> to<00:37:34.540> the<00:37:34.980> specific<00:37:36.240> interface<00:37:37.240> for 00:37:37.880 --> 00:37:37.890 align:start position:0% go back to the specific interface for 00:37:37.890 --> 00:37:40.349 align:start position:0% go back to the specific interface for the<00:37:38.890> contract 00:37:40.349 --> 00:37:40.359 align:start position:0% the contract 00:37:40.359 --> 00:37:42.650 align:start position:0% the contract the<00:37:40.660> crowds<00:37:40.900> tale<00:37:41.170> there<00:37:41.470> are<00:37:41.560> three<00:37:41.800> states 00:37:42.650 --> 00:37:42.660 align:start position:0% the crowds tale there are three states 00:37:42.660 --> 00:37:47.190 align:start position:0% the crowds tale there are three states open<00:37:43.660> his<00:37:44.380> success<00:37:44.980> and<00:37:45.369> refund<00:37:46.060> yes<00:37:46.510> but 00:37:47.190 --> 00:37:47.200 align:start position:0% open his success and refund yes but 00:37:47.200 --> 00:37:51.570 align:start position:0% open his success and refund yes but there's<00:37:47.440> there<00:37:47.800> another<00:37:48.070> state<00:37:48.609> where<00:37:50.580> you've 00:37:51.570 --> 00:37:51.580 align:start position:0% there's there another state where you've 00:37:51.580 --> 00:37:54.480 align:start position:0% there's there another state where you've reached<00:37:51.850> the<00:37:52.060> goal<00:37:52.470> it's<00:37:53.470> closed<00:37:53.800> but<00:37:54.250> the 00:37:54.480 --> 00:37:54.490 align:start position:0% reached the goal it's closed but the 00:37:54.490 --> 00:37:56.160 align:start position:0% reached the goal it's closed but the beneficiary<00:37:55.210> hasn't<00:37:55.570> gotten<00:37:55.720> around<00:37:55.990> to 00:37:56.160 --> 00:37:56.170 align:start position:0% beneficiary hasn't gotten around to 00:37:56.170 --> 00:37:59.130 align:start position:0% beneficiary hasn't gotten around to claiming<00:37:56.980> the<00:37:57.970> thing<00:37:58.210> so<00:37:58.540> it's<00:37:58.750> kind<00:37:58.990> of 00:37:59.130 --> 00:37:59.140 align:start position:0% claiming the thing so it's kind of 00:37:59.140 --> 00:38:03.870 align:start position:0% claiming the thing so it's kind of ending<00:37:59.590> is<00:38:00.040> my<00:38:01.410> my<00:38:02.410> question<00:38:02.470> is<00:38:02.980> with<00:38:03.520> regard 00:38:03.870 --> 00:38:03.880 align:start position:0% ending is my my question is with regard 00:38:03.880 --> 00:38:07.349 align:start position:0% ending is my my question is with regard to<00:38:03.940> the<00:38:04.090> interaction<00:38:04.750> between<00:38:04.780> this<00:38:05.670> code<00:38:06.670> and 00:38:07.349 --> 00:38:07.359 align:start position:0% to the interaction between this code and 00:38:07.359 --> 00:38:10.349 align:start position:0% to the interaction between this code and the<00:38:07.830> specification<00:38:08.830> you<00:38:09.490> go<00:38:09.700> back<00:38:09.910> to<00:38:10.060> fourth 00:38:10.349 --> 00:38:10.359 align:start position:0% the specification you go back to fourth 00:38:10.359 --> 00:38:14.580 align:start position:0% the specification you go back to fourth and<00:38:10.600> change<00:38:11.460> the<00:38:12.460> this<00:38:12.910> code<00:38:13.480> based<00:38:13.960> on<00:38:14.320> your 00:38:14.580 --> 00:38:14.590 align:start position:0% and change the this code based on your 00:38:14.590 --> 00:38:18.210 align:start position:0% and change the this code based on your understanding<00:38:15.190> of<00:38:16.060> the<00:38:16.590> specification<00:38:17.590> so<00:38:18.070> we 00:38:18.210 --> 00:38:18.220 align:start position:0% understanding of the specification so we 00:38:18.220 --> 00:38:20.370 align:start position:0% understanding of the specification so we feel<00:38:18.400> we<00:38:18.550> can<00:38:18.760> develop<00:38:19.060> the<00:38:19.780> content<00:38:20.020> together 00:38:20.370 --> 00:38:20.380 align:start position:0% feel we can develop the content together 00:38:20.380 --> 00:38:22.740 align:start position:0% feel we can develop the content together with<00:38:20.740> the<00:38:20.830> specification<00:38:21.580> yes<00:38:21.940> this<00:38:22.270> is<00:38:22.420> going 00:38:22.740 --> 00:38:22.750 align:start position:0% with the specification yes this is going 00:38:22.750 --> 00:38:27.540 align:start position:0% with the specification yes this is going it's<00:38:23.260> going<00:38:23.650> to<00:38:23.800> the<00:38:25.470> you<00:38:26.470> you<00:38:26.710> look<00:38:27.130> like<00:38:27.369> and 00:38:27.540 --> 00:38:27.550 align:start position:0% it's going to the you you look like and 00:38:27.550 --> 00:38:30.599 align:start position:0% it's going to the you you look like and for<00:38:27.730> a<00:38:28.000> variety<00:38:28.210> of<00:38:28.600> the<00:38:29.350> requirements<00:38:30.010> you 00:38:30.599 --> 00:38:30.609 align:start position:0% for a variety of the requirements you 00:38:30.609 --> 00:38:34.109 align:start position:0% for a variety of the requirements you see<00:38:31.480> that<00:38:31.630> to<00:38:31.750> be<00:38:31.900> something<00:38:32.460> you<00:38:33.460> will<00:38:33.820> change 00:38:34.109 --> 00:38:34.119 align:start position:0% see that to be something you will change 00:38:34.119 --> 00:38:37.020 align:start position:0% see that to be something you will change the<00:38:34.300> codes<00:38:34.540> and<00:38:34.810> maybe<00:38:35.740> on<00:38:36.460> the<00:38:36.580> other<00:38:36.700> cats 00:38:37.020 --> 00:38:37.030 align:start position:0% the codes and maybe on the other cats 00:38:37.030 --> 00:38:39.630 align:start position:0% the codes and maybe on the other cats you<00:38:37.900> did<00:38:38.290> some<00:38:38.470> in<00:38:38.650> the<00:38:38.800> specification<00:38:39.490> which 00:38:39.630 --> 00:38:39.640 align:start position:0% you did some in the specification which 00:38:39.640 --> 00:38:41.580 align:start position:0% you did some in the specification which is<00:38:39.790> wrong<00:38:40.030> and<00:38:40.359> recovery<00:38:41.020> price<00:38:41.230> it<00:38:41.410> correctly 00:38:41.580 --> 00:38:41.590 align:start position:0% is wrong and recovery price it correctly 00:38:41.590 --> 00:38:47.040 align:start position:0% is wrong and recovery price it correctly interchange<00:38:42.460> the<00:38:42.550> specification<00:38:44.970> it's<00:38:46.050> so 00:38:47.040 --> 00:38:47.050 align:start position:0% interchange the specification it's so 00:38:47.050 --> 00:38:51.020 align:start position:0% interchange the specification it's so this<00:38:47.410> process<00:38:47.830> you<00:38:48.190> can<00:38:48.220> be<00:38:48.550> shown 00:38:51.020 --> 00:38:51.030 align:start position:0% 00:38:51.030 --> 00:38:53.220 align:start position:0% cuz<00:38:52.030> it<00:38:52.180> seems<00:38:52.329> like<00:38:52.599> here<00:38:52.869> there<00:38:53.079> would<00:38:53.200> be 00:38:53.220 --> 00:38:53.230 align:start position:0% cuz it seems like here there would be 00:38:53.230 --> 00:38:56.130 align:start position:0% cuz it seems like here there would be some<00:38:53.589> kind<00:38:53.770> of<00:38:53.920> limbo<00:38:54.460> state<00:38:54.970> where<00:38:55.300> there 00:38:56.130 --> 00:38:56.140 align:start position:0% some kind of limbo state where there 00:38:56.140 --> 00:38:56.940 align:start position:0% some kind of limbo state where there will<00:38:56.200> be<00:38:56.260> a<00:38:56.380> ballistic 00:38:56.940 --> 00:38:56.950 align:start position:0% will be a ballistic 00:38:56.950 --> 00:38:58.500 align:start position:0% will be a ballistic yes<00:38:57.160> opportunity<00:38:57.790> there'll<00:38:58.000> be<00:38:58.060> any<00:38:58.270> with 00:38:58.500 --> 00:38:58.510 align:start position:0% yes opportunity there'll be any with 00:38:58.510 --> 00:39:00.829 align:start position:0% yes opportunity there'll be any with states<00:38:58.780> was<00:38:59.530> the<00:38:59.890> girl's<00:39:00.130> back<00:39:00.310> is<00:39:00.550> an<00:39:00.670> inch 00:39:00.829 --> 00:39:00.839 align:start position:0% states was the girl's back is an inch 00:39:00.839 --> 00:39:03.390 align:start position:0% states was the girl's back is an inch and<00:39:01.839> these<00:39:02.079> girls<00:39:02.349> matter<00:39:02.710> who<00:39:02.980> is<00:39:03.070> not<00:39:03.280> to 00:39:03.390 --> 00:39:03.400 align:start position:0% and these girls matter who is not to 00:39:03.400 --> 00:39:05.970 align:start position:0% and these girls matter who is not to call<00:39:03.579> this<00:39:03.760> right<00:39:04.060> the<00:39:04.660> escrow<00:39:05.349> will<00:39:05.650> still<00:39:05.829> be 00:39:05.970 --> 00:39:05.980 align:start position:0% call this right the escrow will still be 00:39:05.980 --> 00:39:09.120 align:start position:0% call this right the escrow will still be in<00:39:06.250> an<00:39:06.369> open<00:39:06.579> state<00:39:07.589> and<00:39:08.589> you<00:39:08.710> cannot<00:39:08.920> do 00:39:09.120 --> 00:39:09.130 align:start position:0% in an open state and you cannot do 00:39:09.130 --> 00:39:11.430 align:start position:0% in an open state and you cannot do anything<00:39:09.640> basically<00:39:10.000> you<00:39:10.690> disciplining<00:39:11.230> the 00:39:11.430 --> 00:39:11.440 align:start position:0% anything basically you disciplining the 00:39:11.440 --> 00:39:13.650 align:start position:0% anything basically you disciplining the state's<00:39:11.710> suspending<00:39:12.579> the<00:39:12.670> beneficiary<00:39:13.390> never 00:39:13.650 --> 00:39:13.660 align:start position:0% state's suspending the beneficiary never 00:39:13.660 --> 00:39:14.910 align:start position:0% state's suspending the beneficiary never gets<00:39:14.140> around<00:39:14.410> every<00:39:14.740> day 00:39:14.910 --> 00:39:14.920 align:start position:0% gets around every day 00:39:14.920 --> 00:39:17.700 align:start position:0% gets around every day you've<00:39:15.910> got<00:39:16.119> paper<00:39:16.359> eyes<00:39:16.630> and<00:39:17.170> that's<00:39:17.380> you 00:39:17.700 --> 00:39:17.710 align:start position:0% you've got paper eyes and that's you 00:39:17.710 --> 00:39:19.980 align:start position:0% you've got paper eyes and that's you know<00:39:17.770> so<00:39:18.099> it<00:39:18.250> remains<00:39:18.640> a<00:39:18.970> little<00:39:19.359> stay<00:39:19.720> forever 00:39:19.980 --> 00:39:19.990 align:start position:0% know so it remains a little stay forever 00:39:19.990 --> 00:39:23.190 align:start position:0% know so it remains a little stay forever show<00:39:20.920> okay<00:39:21.520> so<00:39:21.880> then<00:39:22.119> you<00:39:22.240> need<00:39:22.570> to<00:39:22.750> make<00:39:23.140> a 00:39:23.190 --> 00:39:23.200 align:start position:0% show okay so then you need to make a 00:39:23.200 --> 00:39:25.319 align:start position:0% show okay so then you need to make a requirement<00:39:23.859> you<00:39:24.280> can<00:39:24.400> expect<00:39:24.880> a<00:39:25.060> little 00:39:25.319 --> 00:39:25.329 align:start position:0% requirement you can expect a little 00:39:25.329 --> 00:39:30.089 align:start position:0% requirement you can expect a little spent<00:39:26.849> in<00:39:27.849> make<00:39:28.119> the<00:39:28.270> next<00:39:28.510> requirement<00:39:29.040> as<00:39:30.040> I 00:39:30.089 --> 00:39:30.099 align:start position:0% spent in make the next requirement as I 00:39:30.099 --> 00:39:32.990 align:start position:0% spent in make the next requirement as I said<00:39:30.369> specification<00:39:31.150> waste<00:39:31.420> is<00:39:31.660> incomplete 00:39:32.990 --> 00:39:33.000 align:start position:0% said specification waste is incomplete 00:39:33.000 --> 00:39:35.370 align:start position:0% said specification waste is incomplete so<00:39:34.000> there<00:39:34.210> is<00:39:34.270> something<00:39:34.450> else<00:39:34.720> ready<00:39:35.020> to<00:39:35.230> go 00:39:35.370 --> 00:39:35.380 align:start position:0% so there is something else ready to go 00:39:35.380 --> 00:39:37.710 align:start position:0% so there is something else ready to go shows<00:39:36.130> what<00:39:36.670> it<00:39:36.820> said<00:39:37.000> you<00:39:37.150> can<00:39:37.329> escape<00:39:37.540> the 00:39:37.710 --> 00:39:37.720 align:start position:0% shows what it said you can escape the 00:39:37.720 --> 00:39:40.260 align:start position:0% shows what it said you can escape the the<00:39:38.109> you<00:39:38.230> know<00:39:38.260> state<00:39:38.680> this<00:39:39.460> is<00:39:39.609> total<00:39:39.970> - 00:39:40.260 --> 00:39:40.270 align:start position:0% the you know state this is total - 00:39:40.270 --> 00:39:43.380 align:start position:0% the you know state this is total - property<00:39:40.810> rights<00:39:41.820> cannot<00:39:42.820> verify<00:39:43.000> - 00:39:43.380 --> 00:39:43.390 align:start position:0% property rights cannot verify - 00:39:43.390 --> 00:39:45.870 align:start position:0% property rights cannot verify - probabilities<00:39:44.050> they<00:39:44.680> different<00:39:45.550> techniques 00:39:45.870 --> 00:39:45.880 align:start position:0% probabilities they different techniques 00:39:45.880 --> 00:39:48.960 align:start position:0% probabilities they different techniques and<00:39:46.750> what<00:39:46.930> we<00:39:47.109> focus<00:39:47.589> on<00:39:47.670> properties<00:39:48.670> of<00:39:48.820> these 00:39:48.960 --> 00:39:48.970 align:start position:0% and what we focus on properties of these 00:39:48.970 --> 00:39:51.030 align:start position:0% and what we focus on properties of these kinds<00:39:49.390> which<00:39:49.839> are<00:39:50.020> called<00:39:50.200> safety<00:39:50.680> both<00:39:50.890> of 00:39:51.030 --> 00:39:51.040 align:start position:0% kinds which are called safety both of 00:39:51.040 --> 00:39:57.809 align:start position:0% kinds which are called safety both of these<00:39:51.160> yes<00:39:52.119> but<00:39:55.470> yes<00:39:56.470> does<00:39:57.160> this<00:39:57.400> kind<00:39:57.730> of 00:39:57.809 --> 00:39:57.819 align:start position:0% these yes but yes does this kind of 00:39:57.819 --> 00:40:00.809 align:start position:0% these yes but yes does this kind of reverse<00:39:58.270> should<00:39:58.990> we<00:39:59.290> have<00:39:59.530> the<00:39:59.819> formal 00:40:00.809 --> 00:40:00.819 align:start position:0% reverse should we have the formal 00:40:00.819 --> 00:40:03.160 align:start position:0% reverse should we have the formal requirement<00:40:01.359> perfect 00:40:03.160 --> 00:40:03.170 align:start position:0% requirement perfect 00:40:03.170 --> 00:40:05.020 align:start position:0% requirement perfect depends<00:40:03.890> on<00:40:03.950> your<00:40:04.130> style<00:40:04.400> thought<00:40:04.700> hell 00:40:05.020 --> 00:40:05.030 align:start position:0% depends on your style thought hell 00:40:05.030 --> 00:40:06.610 align:start position:0% depends on your style thought hell develop<00:40:05.210> the<00:40:05.570> codes<00:40:05.810> and<00:40:05.990> so<00:40:06.350> some<00:40:06.590> people 00:40:06.610 --> 00:40:06.620 align:start position:0% develop the codes and so some people 00:40:06.620 --> 00:40:08.170 align:start position:0% develop the codes and so some people refer<00:40:07.160> to<00:40:07.190> an<00:40:07.400> idea<00:40:07.610> called<00:40:07.790> so<00:40:08.000> they 00:40:08.170 --> 00:40:08.180 align:start position:0% refer to an idea called so they 00:40:08.180 --> 00:40:09.820 align:start position:0% refer to an idea called so they understand<00:40:08.780> the<00:40:08.810> program<00:40:09.200> you<00:40:09.290> might<00:40:09.440> benefit 00:40:09.820 --> 00:40:09.830 align:start position:0% understand the program you might benefit 00:40:09.830 --> 00:40:12.610 align:start position:0% understand the program you might benefit and<00:40:10.130> then<00:40:10.670> you<00:40:10.790> go<00:40:10.910> the<00:40:11.090> specification<00:40:11.620> some 00:40:12.610 --> 00:40:12.620 align:start position:0% and then you go the specification some 00:40:12.620 --> 00:40:14.320 align:start position:0% and then you go the specification some people<00:40:12.950> try<00:40:13.130> to<00:40:13.160> develop<00:40:13.520> the<00:40:13.670> specification 00:40:14.320 --> 00:40:14.330 align:start position:0% people try to develop the specification 00:40:14.330 --> 00:40:17.710 align:start position:0% people try to develop the specification before<00:40:14.630> they<00:40:14.780> understand<00:40:15.200> it<00:40:15.350> and<00:40:16.420> also<00:40:17.420> if 00:40:17.710 --> 00:40:17.720 align:start position:0% before they understand it and also if 00:40:17.720 --> 00:40:19.750 align:start position:0% before they understand it and also if you're<00:40:17.930> providing<00:40:18.440> an<00:40:18.560> audit<00:40:18.950> service<00:40:19.400> you're 00:40:19.750 --> 00:40:19.760 align:start position:0% you're providing an audit service you're 00:40:19.760 --> 00:40:21.430 align:start position:0% you're providing an audit service you're not<00:40:19.940> writing<00:40:20.150> the<00:40:20.390> code<00:40:20.540> you're<00:40:20.840> you're<00:40:21.170> hired 00:40:21.430 --> 00:40:21.440 align:start position:0% not writing the code you're you're hired 00:40:21.440 --> 00:40:24.130 align:start position:0% not writing the code you're you're hired through<00:40:21.800> yes<00:40:22.190> delight<00:40:23.000> respect<00:40:23.360> exactly<00:40:23.960> this 00:40:24.130 --> 00:40:24.140 align:start position:0% through yes delight respect exactly this 00:40:24.140 --> 00:40:25.570 align:start position:0% through yes delight respect exactly this is<00:40:24.260> sure<00:40:24.440> what<00:40:24.740> people<00:40:24.890> eat<00:40:25.130> a<00:40:25.310> snake 00:40:25.570 --> 00:40:25.580 align:start position:0% is sure what people eat a snake 00:40:25.580 --> 00:40:27.580 align:start position:0% is sure what people eat a snake yesterday<00:40:26.450> they<00:40:26.630> don't<00:40:26.810> taste<00:40:26.960> the<00:40:27.140> cold<00:40:27.350> or 00:40:27.580 --> 00:40:27.590 align:start position:0% yesterday they don't taste the cold or 00:40:27.590 --> 00:40:30.100 align:start position:0% yesterday they don't taste the cold or they<00:40:28.100> do<00:40:28.160> suggestions<00:40:28.910> in<00:40:29.090> public<00:40:29.420> illusion 00:40:30.100 --> 00:40:30.110 align:start position:0% they do suggestions in public illusion 00:40:30.110 --> 00:40:32.830 align:start position:0% they do suggestions in public illusion was<00:40:30.620> in<00:40:30.950> general<00:40:31.490> yes<00:40:32.210> we<00:40:32.420> do<00:40:32.540> like<00:40:32.750> the 00:40:32.830 --> 00:40:32.840 align:start position:0% was in general yes we do like the 00:40:32.840 --> 00:40:35.020 align:start position:0% was in general yes we do like the specifications<00:40:33.590> sometimes<00:40:34.460> based<00:40:34.760> on<00:40:34.940> the 00:40:35.020 --> 00:40:35.030 align:start position:0% specifications sometimes based on the 00:40:35.030 --> 00:40:37.660 align:start position:0% specifications sometimes based on the clothes<00:40:35.410> sometimes<00:40:36.410> based<00:40:36.830> on<00:40:37.010> requirements 00:40:37.660 --> 00:40:37.670 align:start position:0% clothes sometimes based on requirements 00:40:37.670 --> 00:40:42.240 align:start position:0% clothes sometimes based on requirements given<00:40:37.940> by<00:40:38.090> the<00:40:38.150> plans<00:40:38.770> yes<00:40:40.450> what<00:40:41.450> about 00:40:42.240 --> 00:40:42.250 align:start position:0% given by the plans yes what about 00:40:42.250 --> 00:40:45.490 align:start position:0% given by the plans yes what about investment<00:40:43.450> in<00:40:44.450> list<00:40:44.720> yes 00:40:45.490 --> 00:40:45.500 align:start position:0% investment in list yes 00:40:45.500 --> 00:40:50.940 align:start position:0% investment in list yes after<00:40:46.070> the 00:40:50.940 --> 00:40:50.950 align:start position:0% 00:40:50.950 --> 00:40:53.099 align:start position:0% whether<00:40:51.309> you<00:40:51.489> can<00:40:51.640> invest<00:40:52.180> after<00:40:52.569> the<00:40:52.690> goal<00:40:52.869> is 00:40:53.099 --> 00:40:53.109 align:start position:0% whether you can invest after the goal is 00:40:53.109 --> 00:40:55.200 align:start position:0% whether you can invest after the goal is arranged<00:40:53.529> it<00:40:54.099> should<00:40:54.309> not<00:40:54.489> be<00:40:54.670> possible<00:40:54.849> you 00:40:55.200 --> 00:40:55.210 align:start position:0% arranged it should not be possible you 00:40:55.210 --> 00:41:01.400 align:start position:0% arranged it should not be possible you should<00:40:55.239> not<00:40:55.539> be<00:40:55.690> possible<00:40:55.839> to<00:40:56.200> invest<00:40:56.559> once 00:41:01.400 --> 00:41:01.410 align:start position:0% 00:41:01.410 --> 00:41:03.630 align:start position:0% yes<00:41:02.410> yes<00:41:02.589> absolutely<00:41:03.099> I<00:41:03.249> said<00:41:03.519> the 00:41:03.630 --> 00:41:03.640 align:start position:0% yes yes absolutely I said the 00:41:03.640 --> 00:41:07.920 align:start position:0% yes yes absolutely I said the specification<00:41:04.210> is<00:41:04.559> right<00:41:05.559> so<00:41:06.720> ideally<00:41:07.720> we'll 00:41:07.920 --> 00:41:07.930 align:start position:0% specification is right so ideally we'll 00:41:07.930 --> 00:41:09.420 align:start position:0% specification is right so ideally we'll get<00:41:08.109> the<00:41:08.230> complete<00:41:08.529> specification<00:41:08.829> but 00:41:09.420 --> 00:41:09.430 align:start position:0% get the complete specification but 00:41:09.430 --> 00:41:12.450 align:start position:0% get the complete specification but theses<00:41:09.789> and<00:41:10.119> of<00:41:10.720> open-ended<00:41:11.170> sources<00:41:11.680> require 00:41:12.450 --> 00:41:12.460 align:start position:0% theses and of open-ended sources require 00:41:12.460 --> 00:41:20.039 align:start position:0% theses and of open-ended sources require something<00:41:14.609> okay<00:41:16.529> so<00:41:17.529> this<00:41:18.190> one<00:41:18.930> the<00:41:19.930> whole 00:41:20.039 --> 00:41:20.049 align:start position:0% something okay so this one the whole 00:41:20.049 --> 00:41:21.599 align:start position:0% something okay so this one the whole point<00:41:20.289> of<00:41:20.380> this<00:41:20.559> is<00:41:20.829> to<00:41:20.890> emphasize<00:41:21.130> that 00:41:21.599 --> 00:41:21.609 align:start position:0% point of this is to emphasize that 00:41:21.609 --> 00:41:22.799 align:start position:0% point of this is to emphasize that before<00:41:22.059> you<00:41:22.119> start<00:41:22.359> with<00:41:22.480> formal 00:41:22.799 --> 00:41:22.809 align:start position:0% before you start with formal 00:41:22.809 --> 00:41:28.880 align:start position:0% before you start with formal specification<00:41:23.440> it's<00:41:23.890> good<00:41:24.130> to<00:41:24.249> have<00:41:24.430> informal 00:41:28.880 --> 00:41:28.890 align:start position:0% 00:41:28.890 --> 00:41:34.289 align:start position:0% good<00:41:30.119> sure<00:41:31.119> okay<00:41:31.920> let's<00:41:32.920> move<00:41:33.069> on<00:41:33.220> my<00:41:33.789> findings 00:41:34.289 --> 00:41:34.299 align:start position:0% good sure okay let's move on my findings 00:41:34.299 --> 00:41:34.950 align:start position:0% good sure okay let's move on my findings with<00:41:34.390> Erics 00:41:34.950 --> 00:41:34.960 align:start position:0% with Erics 00:41:34.960 --> 00:41:38.009 align:start position:0% with Erics we<00:41:35.529> try<00:41:35.739> to<00:41:35.799> formalize<00:41:36.279> these<00:41:36.700> properties<00:41:37.359> in 00:41:38.009 --> 00:41:38.019 align:start position:0% we try to formalize these properties in 00:41:38.019 --> 00:41:40.470 align:start position:0% we try to formalize these properties in the<00:41:38.309> specification<00:41:39.309> languages<00:41:39.609> by<00:41:39.910> sports 00:41:40.470 --> 00:41:40.480 align:start position:0% the specification languages by sports 00:41:40.480 --> 00:41:47.279 align:start position:0% the specification languages by sports I<00:41:40.569> see<00:41:41.259> whether<00:41:41.499> they<00:41:41.710> verify<00:41:43.259> okay<00:41:45.299> so<00:41:46.299> how 00:41:47.279 --> 00:41:47.289 align:start position:0% I see whether they verify okay so how 00:41:47.289 --> 00:41:48.660 align:start position:0% I see whether they verify okay so how things<00:41:47.529> get<00:41:47.710> into<00:41:48.099> the<00:41:48.249> specification 00:41:48.660 --> 00:41:48.670 align:start position:0% things get into the specification 00:41:48.670 --> 00:41:51.599 align:start position:0% things get into the specification language<00:41:49.329> and<00:41:49.630> the<00:41:50.559> product<00:41:51.069> is<00:41:51.190> based<00:41:51.430> on 00:41:51.599 --> 00:41:51.609 align:start position:0% language and the product is based on 00:41:51.609 --> 00:41:52.979 align:start position:0% language and the product is based on something<00:41:51.849> called<00:41:51.999> the<00:41:52.210> linear<00:41:52.509> temporal 00:41:52.979 --> 00:41:52.989 align:start position:0% something called the linear temporal 00:41:52.989 --> 00:41:56.430 align:start position:0% something called the linear temporal order<00:41:53.460> so<00:41:54.460> this<00:41:54.670> might<00:41:54.849> sound<00:41:55.089> something<00:41:56.019> very 00:41:56.430 --> 00:41:56.440 align:start position:0% order so this might sound something very 00:41:56.440 --> 00:41:59.880 align:start position:0% order so this might sound something very natural<00:41:56.980> so<00:41:57.249> it<00:41:57.400> in<00:41:57.700> fact<00:41:57.940> it<00:41:58.089> is<00:41:58.210> a<00:41:58.890> brief 00:41:59.880 --> 00:41:59.890 align:start position:0% natural so it in fact it is a brief 00:41:59.890 --> 00:42:02.249 align:start position:0% natural so it in fact it is a brief explanation<00:42:00.269> so<00:42:01.269> many<00:42:01.450> most<00:42:01.930> of<00:42:02.049> you<00:42:02.170> are 00:42:02.249 --> 00:42:02.259 align:start position:0% explanation so many most of you are 00:42:02.259 --> 00:42:03.989 align:start position:0% explanation so many most of you are familiar<00:42:02.289> with<00:42:02.769> classical<00:42:02.950> loading<00:42:03.640> which<00:42:03.849> is 00:42:03.989 --> 00:42:03.999 align:start position:0% familiar with classical loading which is 00:42:03.999 --> 00:42:06.960 align:start position:0% familiar with classical loading which is our<00:42:04.180> everyday<00:42:04.569> logic<00:42:05.140> that<00:42:05.349> we<00:42:05.499> use<00:42:05.680> and<00:42:05.970> you 00:42:06.960 --> 00:42:06.970 align:start position:0% our everyday logic that we use and you 00:42:06.970 --> 00:42:09.930 align:start position:0% our everyday logic that we use and you can<00:42:07.150> express<00:42:07.890> formalized<00:42:08.890> properties<00:42:09.460> for 00:42:09.930 --> 00:42:09.940 align:start position:0% can express formalized properties for 00:42:09.940 --> 00:42:13.259 align:start position:0% can express formalized properties for example<00:42:09.999> the<00:42:10.900> H<00:42:11.140> is<00:42:11.499> lose<00:42:11.890> the<00:42:12.039> nature<00:42:12.369> for<00:42:12.609> TCU 00:42:13.259 --> 00:42:13.269 align:start position:0% example the H is lose the nature for TCU 00:42:13.269 --> 00:42:15.509 align:start position:0% example the H is lose the nature for TCU right<00:42:13.779> so<00:42:13.960> classical<00:42:14.440> logic<00:42:14.589> defies<00:42:15.279> the 00:42:15.509 --> 00:42:15.519 align:start position:0% right so classical logic defies the 00:42:15.519 --> 00:42:17.849 align:start position:0% right so classical logic defies the relations<00:42:16.180> between<00:42:16.269> individuals<00:42:17.170> in<00:42:17.349> this 00:42:17.849 --> 00:42:17.859 align:start position:0% relations between individuals in this 00:42:17.859 --> 00:42:20.160 align:start position:0% relations between individuals in this case<00:42:18.039> revelation<00:42:18.609> is<00:42:18.730> that<00:42:18.910> the<00:42:19.599> zoom<00:42:19.869> over 00:42:20.160 --> 00:42:20.170 align:start position:0% case revelation is that the zoom over 00:42:20.170 --> 00:42:23.039 align:start position:0% case revelation is that the zoom over two<00:42:20.349> inches<00:42:20.559> is<00:42:21.009> even<00:42:21.339> right<00:42:21.839> and<00:42:22.839> how<00:42:23.019> would 00:42:23.039 --> 00:42:23.049 align:start position:0% two inches is even right and how would 00:42:23.049 --> 00:42:24.749 align:start position:0% two inches is even right and how would you<00:42:23.200> write<00:42:23.440> this<00:42:23.619> formally<00:42:24.220> in<00:42:24.369> plastic 00:42:24.749 --> 00:42:24.759 align:start position:0% you write this formally in plastic 00:42:24.759 --> 00:42:26.910 align:start position:0% you write this formally in plastic project<00:42:25.239> you<00:42:25.420> say<00:42:25.660> there<00:42:26.440> exists<00:42:26.739> some 00:42:26.910 --> 00:42:26.920 align:start position:0% project you say there exists some 00:42:26.920 --> 00:42:29.970 align:start position:0% project you say there exists some integer<00:42:27.609> sisters<00:42:28.529> antibodies<00:42:29.529> who<00:42:29.829> is<00:42:29.890> the 00:42:29.970 --> 00:42:29.980 align:start position:0% integer sisters antibodies who is the 00:42:29.980 --> 00:42:31.829 align:start position:0% integer sisters antibodies who is the ancient<00:42:30.190> ball<00:42:30.579> is<00:42:30.970> wisely<00:42:31.480> seen<00:42:31.690> together 00:42:31.829 --> 00:42:31.839 align:start position:0% ancient ball is wisely seen together 00:42:31.839 --> 00:42:34.259 align:start position:0% ancient ball is wisely seen together Thank<00:42:32.410> You<00:42:32.499> snow<00:42:32.739> you<00:42:33.579> say<00:42:33.759> the<00:42:33.880> things<00:42:34.089> are 00:42:34.259 --> 00:42:34.269 align:start position:0% Thank You snow you say the things are 00:42:34.269 --> 00:42:36.680 align:start position:0% Thank You snow you say the things are even<00:42:34.660> this<00:42:35.259> is<00:42:35.410> fast<00:42:35.680> apology 00:42:36.680 --> 00:42:36.690 align:start position:0% even this is fast apology 00:42:36.690 --> 00:42:38.870 align:start position:0% even this is fast apology and<00:42:37.020> therefore<00:42:37.770> logic<00:42:38.160> adds<00:42:38.400> a<00:42:38.700> lot<00:42:38.820> of 00:42:38.870 --> 00:42:38.880 align:start position:0% and therefore logic adds a lot of 00:42:38.880 --> 00:42:42.440 align:start position:0% and therefore logic adds a lot of dimension<00:42:39.120> to<00:42:40.110> this<00:42:40.260> which<00:42:40.650> is<00:42:40.680> titled<00:42:41.450> right 00:42:42.440 --> 00:42:42.450 align:start position:0% dimension to this which is titled right 00:42:42.450 --> 00:42:45.320 align:start position:0% dimension to this which is titled right so<00:42:42.690> now<00:42:43.230> these<00:42:43.440> are<00:42:43.680> not<00:42:43.890> a<00:42:43.950> statically<00:42:44.550> laid 00:42:45.320 --> 00:42:45.330 align:start position:0% so now these are not a statically laid 00:42:45.330 --> 00:42:47.450 align:start position:0% so now these are not a statically laid out<00:42:45.570> in<00:42:45.750> the<00:42:45.840> perfect<00:42:46.260> ideal<00:42:46.620> world<00:42:46.920> but<00:42:47.220> we 00:42:47.450 --> 00:42:47.460 align:start position:0% out in the perfect ideal world but we 00:42:47.460 --> 00:42:52.340 align:start position:0% out in the perfect ideal world but we also<00:42:47.490> have<00:42:47.970> promise<00:42:49.250> and<00:42:51.200> temporal<00:42:52.200> body 00:42:52.340 --> 00:42:52.350 align:start position:0% also have promise and temporal body 00:42:52.350 --> 00:42:54.380 align:start position:0% also have promise and temporal body forces<00:42:52.860> could<00:42:53.100> be<00:42:53.130> violations<00:42:53.730> in<00:42:54.180> most 00:42:54.380 --> 00:42:54.390 align:start position:0% forces could be violations in most 00:42:54.390 --> 00:42:57.290 align:start position:0% forces could be violations in most states<00:42:54.840> so<00:42:55.260> you<00:42:55.320> have<00:42:55.680> usually<00:42:56.220> initial<00:42:57.030> state 00:42:57.290 --> 00:42:57.300 align:start position:0% states so you have usually initial state 00:42:57.300 --> 00:43:00.380 align:start position:0% states so you have usually initial state in<00:42:57.540> nineteen<00:42:57.930> point<00:42:58.230> zero<00:42:58.560> point<00:42:59.370> one<00:42:59.760> another 00:43:00.380 --> 00:43:00.390 align:start position:0% in nineteen point zero point one another 00:43:00.390 --> 00:43:02.720 align:start position:0% in nineteen point zero point one another state<00:43:00.750> and<00:43:00.930> so<00:43:01.110> on<00:43:01.140> is<00:43:01.380> itself<00:43:01.950> now<00:43:02.430> you<00:43:02.460> can 00:43:02.720 --> 00:43:02.730 align:start position:0% state and so on is itself now you can 00:43:02.730 --> 00:43:06.590 align:start position:0% state and so on is itself now you can define<00:43:02.850> the<00:43:03.120> relation<00:43:03.770> and<00:43:04.770> here<00:43:05.430> we<00:43:05.700> just<00:43:06.240> as 00:43:06.590 --> 00:43:06.600 align:start position:0% define the relation and here we just as 00:43:06.600 --> 00:43:08.480 align:start position:0% define the relation and here we just as an<00:43:06.720> examples<00:43:07.260> that<00:43:07.380> you'll<00:43:07.560> make<00:43:07.770> accessible 00:43:08.480 --> 00:43:08.490 align:start position:0% an examples that you'll make accessible 00:43:08.490 --> 00:43:12.110 align:start position:0% an examples that you'll make accessible and<00:43:08.730> so<00:43:08.940> is<00:43:09.090> the<00:43:09.240> case<00:43:09.890> the<00:43:10.890> ATO<00:43:11.550> bodies<00:43:11.910> which 00:43:12.110 --> 00:43:12.120 align:start position:0% and so is the case the ATO bodies which 00:43:12.120 --> 00:43:15.890 align:start position:0% and so is the case the ATO bodies which is<00:43:12.240> the<00:43:12.330> danger<00:43:12.660> is<00:43:13.560> even<00:43:14.690> so<00:43:15.690> we've<00:43:15.870> just 00:43:15.890 --> 00:43:15.900 align:start position:0% is the danger is even so we've just 00:43:15.900 --> 00:43:19.190 align:start position:0% is the danger is even so we've just changed<00:43:16.320> to<00:43:16.680> property<00:43:17.160> very<00:43:17.760> slightly<00:43:18.200> by 00:43:19.190 --> 00:43:19.200 align:start position:0% changed to property very slightly by 00:43:19.200 --> 00:43:21.770 align:start position:0% changed to property very slightly by adding<00:43:19.620> the<00:43:19.830> movies<00:43:20.280> and<00:43:20.630> pepper 00:43:21.770 --> 00:43:21.780 align:start position:0% adding the movies and pepper 00:43:21.780 --> 00:43:25.160 align:start position:0% adding the movies and pepper operator<00:43:22.350> to<00:43:23.190> express<00:43:23.640> this<00:43:24.270> this<00:43:24.600> relation 00:43:25.160 --> 00:43:25.170 align:start position:0% operator to express this this relation 00:43:25.170 --> 00:43:27.710 align:start position:0% operator to express this this relation which<00:43:25.560> is<00:43:25.590> an<00:43:25.800> across<00:43:26.070> time<00:43:26.400> not<00:43:27.150> just<00:43:27.390> within 00:43:27.710 --> 00:43:27.720 align:start position:0% which is an across time not just within 00:43:27.720 --> 00:43:32.000 align:start position:0% which is an across time not just within a<00:43:28.050> single<00:43:28.290> state<00:43:28.640> right<00:43:29.660> so<00:43:30.680> you<00:43:31.680> see<00:43:31.890> that 00:43:32.000 --> 00:43:32.010 align:start position:0% a single state right so you see that 00:43:32.010 --> 00:43:34.580 align:start position:0% a single state right so you see that this<00:43:32.160> this<00:43:32.520> this<00:43:32.970> relation<00:43:33.660> is<00:43:33.840> not<00:43:34.020> in<00:43:34.440> the 00:43:34.580 --> 00:43:34.590 align:start position:0% this this this relation is not in the 00:43:34.590 --> 00:43:36.890 align:start position:0% this this this relation is not in the real<00:43:34.740> world<00:43:35.100> right<00:43:35.310> is<00:43:35.490> he<00:43:36.300> always<00:43:36.480> the<00:43:36.720> same 00:43:36.890 --> 00:43:36.900 align:start position:0% real world right is he always the same 00:43:36.900 --> 00:43:40.010 align:start position:0% real world right is he always the same pages<00:43:37.290> or<00:43:37.860> even<00:43:38.030> somebody<00:43:39.030> the<00:43:39.780> same 00:43:40.010 --> 00:43:40.020 align:start position:0% pages or even somebody the same 00:43:40.020 --> 00:43:43.580 align:start position:0% pages or even somebody the same increment<00:43:40.410> H<00:43:40.890> one<00:43:41.610> guy<00:43:41.790> income<00:43:42.240> as<00:43:42.360> night<00:43:42.600> the 00:43:43.580 --> 00:43:43.590 align:start position:0% increment H one guy income as night the 00:43:43.590 --> 00:43:45.770 align:start position:0% increment H one guy income as night the same<00:43:43.980> will<00:43:44.100> become<00:43:44.430> all<00:43:44.670> right<00:43:45.150> so<00:43:45.330> this<00:43:45.480> is<00:43:45.540> an 00:43:45.770 --> 00:43:45.780 align:start position:0% same will become all right so this is an 00:43:45.780 --> 00:43:46.520 align:start position:0% same will become all right so this is an example 00:43:46.520 --> 00:43:46.530 align:start position:0% example 00:43:46.530 --> 00:43:49.220 align:start position:0% example property<00:43:47.280> result<00:43:47.970> because<00:43:48.510> it's<00:43:48.720> not<00:43:48.930> always 00:43:49.220 --> 00:43:49.230 align:start position:0% property result because it's not always 00:43:49.230 --> 00:44:03.390 align:start position:0% property result because it's not always the<00:43:49.620> case 00:44:03.390 --> 00:44:03.400 align:start position:0% 00:44:03.400 --> 00:44:06.850 align:start position:0% so<00:44:04.400> yes<00:44:04.610> that<00:44:04.850> is<00:44:05.000> what<00:44:05.390> this<00:44:05.510> is<00:44:05.720> you<00:44:05.900> and<00:44:06.530> me<00:44:06.560> - 00:44:06.850 --> 00:44:06.860 align:start position:0% so yes that is what this is you and me - 00:44:06.860 --> 00:44:07.810 align:start position:0% so yes that is what this is you and me - yes 00:44:07.810 --> 00:44:07.820 align:start position:0% yes 00:44:07.820 --> 00:44:12.130 align:start position:0% yes okay<00:44:09.370> so<00:44:10.370> just<00:44:10.760> to<00:44:11.450> say<00:44:11.630> what<00:44:11.930> you<00:44:12.110> are 00:44:12.130 --> 00:44:12.140 align:start position:0% okay so just to say what you are 00:44:12.140 --> 00:44:14.080 align:start position:0% okay so just to say what you are specified<00:44:12.710> with<00:44:12.890> the<00:44:12.920> temporal<00:44:13.460> logic<00:44:13.820> what 00:44:14.080 --> 00:44:14.090 align:start position:0% specified with the temporal logic what 00:44:14.090 --> 00:44:17.020 align:start position:0% specified with the temporal logic what you<00:44:14.240> do<00:44:14.390> have<00:44:14.630> is<00:44:14.840> this<00:44:15.110> model<00:44:15.470> panel<00:44:16.030> you 00:44:17.020 --> 00:44:17.030 align:start position:0% you do have is this model panel you 00:44:17.030 --> 00:44:20.500 align:start position:0% you do have is this model panel you specify<00:44:17.750> properties<00:44:17.960> of<00:44:18.440> places<00:44:18.920> for<00:44:19.910> me<00:44:20.300> and 00:44:20.500 --> 00:44:20.510 align:start position:0% specify properties of places for me and 00:44:20.510 --> 00:44:22.980 align:start position:0% specify properties of places for me and each<00:44:21.260> place<00:44:21.530> is<00:44:21.560> the<00:44:21.830> sequence<00:44:22.220> of<00:44:22.310> space 00:44:22.980 --> 00:44:22.990 align:start position:0% each place is the sequence of space 00:44:22.990 --> 00:44:26.950 align:start position:0% each place is the sequence of space right<00:44:24.610> the<00:44:25.610> index<00:44:25.880> of<00:44:26.030> the<00:44:26.150> sequence<00:44:26.570> gives 00:44:26.950 --> 00:44:26.960 align:start position:0% right the index of the sequence gives 00:44:26.960 --> 00:44:28.570 align:start position:0% right the index of the sequence gives you<00:44:27.080> can<00:44:27.260> discrete<00:44:27.800> time<00:44:28.190> some<00:44:28.550> time 00:44:28.570 --> 00:44:28.580 align:start position:0% you can discrete time some time 00:44:28.580 --> 00:44:31.390 align:start position:0% you can discrete time some time progresses<00:44:29.330> from<00:44:29.510> 0<00:44:29.870> to<00:44:30.050> infinity<00:44:30.190> going<00:44:31.190> in 00:44:31.390 --> 00:44:31.400 align:start position:0% progresses from 0 to infinity going in 00:44:31.400 --> 00:44:33.940 align:start position:0% progresses from 0 to infinity going in increments<00:44:31.700> of<00:44:32.060> 1<00:44:32.300> right<00:44:32.630> so<00:44:33.410> for<00:44:33.560> example 00:44:33.940 --> 00:44:33.950 align:start position:0% increments of 1 right so for example 00:44:33.950 --> 00:44:36.100 align:start position:0% increments of 1 right so for example this<00:44:34.040> could<00:44:34.220> be<00:44:34.340> the<00:44:34.490> desert<00:44:34.820> state<00:44:35.330> or<00:44:35.630> some 00:44:36.100 --> 00:44:36.110 align:start position:0% this could be the desert state or some 00:44:36.110 --> 00:44:37.420 align:start position:0% this could be the desert state or some people<00:44:36.380> might<00:44:36.530> like<00:44:36.710> to<00:44:36.740> come<00:44:37.010> from<00:44:37.220> one 00:44:37.420 --> 00:44:37.430 align:start position:0% people might like to come from one 00:44:37.430 --> 00:44:40.660 align:start position:0% people might like to come from one because<00:44:37.880> respect<00:44:38.510> and<00:44:39.010> this<00:44:40.010> is<00:44:40.190> the<00:44:40.340> second 00:44:40.660 --> 00:44:40.670 align:start position:0% because respect and this is the second 00:44:40.670 --> 00:44:42.060 align:start position:0% because respect and this is the second step<00:44:40.850> this<00:44:41.030> is<00:44:41.090> interesting 00:44:42.060 --> 00:44:42.070 align:start position:0% step this is interesting 00:44:42.070 --> 00:44:45.760 align:start position:0% step this is interesting so<00:44:43.070> this<00:44:43.250> is<00:44:43.400> kind<00:44:44.270> of<00:44:44.360> what<00:44:44.870> your<00:44:45.080> specified 00:44:45.760 --> 00:44:45.770 align:start position:0% so this is kind of what your specified 00:44:45.770 --> 00:44:50.770 align:start position:0% so this is kind of what your specified in<00:44:46.700> temporal<00:44:47.690> logic<00:44:47.720> and<00:44:48.670> each<00:44:49.670> state<00:44:50.120> we<00:44:50.600> have 00:44:50.770 --> 00:44:50.780 align:start position:0% in temporal logic and each state we have 00:44:50.780 --> 00:44:54.550 align:start position:0% in temporal logic and each state we have randomly<00:44:51.350> divided<00:44:52.310> two<00:44:52.880> worlds<00:44:53.720> or<00:44:53.990> two<00:44:54.170> parts 00:44:54.550 --> 00:44:54.560 align:start position:0% randomly divided two worlds or two parts 00:44:54.560 --> 00:44:56.500 align:start position:0% randomly divided two worlds or two parts that<00:44:54.800> are<00:44:55.010> the<00:44:55.160> constants<00:44:55.730> in<00:44:55.880> servicemen's 00:44:56.500 --> 00:44:56.510 align:start position:0% that are the constants in servicemen's 00:44:56.510 --> 00:44:59.860 align:start position:0% that are the constants in servicemen's and<00:44:56.810> the<00:44:57.620> variables<00:44:58.040> of<00:44:58.190> slightly<00:44:58.460> and<00:44:58.970> as<00:44:59.750> an 00:44:59.860 --> 00:44:59.870 align:start position:0% and the variables of slightly and as an 00:44:59.870 --> 00:45:02.830 align:start position:0% and the variables of slightly and as an example<00:45:00.200> Alice<00:45:00.830> as<00:45:01.490> a<00:45:01.550> person<00:45:02.090> is<00:45:02.240> a<00:45:02.270> constant 00:45:02.830 --> 00:45:02.840 align:start position:0% example Alice as a person is a constant 00:45:02.840 --> 00:45:06.190 align:start position:0% example Alice as a person is a constant which<00:45:03.110> means<00:45:03.140> that<00:45:03.820> if<00:45:04.820> this<00:45:05.390> object<00:45:05.630> does<00:45:05.990> not 00:45:06.190 --> 00:45:06.200 align:start position:0% which means that if this object does not 00:45:06.200 --> 00:45:08.800 align:start position:0% which means that if this object does not change<00:45:06.410> across<00:45:06.740> time<00:45:07.130> policy<00:45:07.670> advice<00:45:08.000> is<00:45:08.270> in 00:45:08.800 --> 00:45:08.810 align:start position:0% change across time policy advice is in 00:45:08.810 --> 00:45:11.830 align:start position:0% change across time policy advice is in all<00:45:09.080> time<00:45:09.620> points<00:45:09.830> right<00:45:10.550> the<00:45:11.210> same<00:45:11.420> goes<00:45:11.630> with 00:45:11.830 --> 00:45:11.840 align:start position:0% all time points right the same goes with 00:45:11.840 --> 00:45:16.840 align:start position:0% all time points right the same goes with reverse<00:45:12.290> osmosis<00:45:12.610> and<00:45:13.610> 27<00:45:14.420> rotate<00:45:15.610> so<00:45:16.610> this 00:45:16.840 --> 00:45:16.850 align:start position:0% reverse osmosis and 27 rotate so this 00:45:16.850 --> 00:45:18.730 align:start position:0% reverse osmosis and 27 rotate so this insert<00:45:17.240> constant<00:45:17.720> they<00:45:17.870> never<00:45:18.170> change<00:45:18.530> the 00:45:18.730 --> 00:45:18.740 align:start position:0% insert constant they never change the 00:45:18.740 --> 00:45:22.290 align:start position:0% insert constant they never change the cross<00:45:18.920> and<00:45:19.580> the<00:45:20.570> other<00:45:20.690> part<00:45:20.990> in<00:45:21.140> the<00:45:21.260> state 00:45:22.290 --> 00:45:22.300 align:start position:0% cross and the other part in the state 00:45:22.300 --> 00:45:25.360 align:start position:0% cross and the other part in the state variables<00:45:23.300> this<00:45:24.200> is<00:45:24.380> our<00:45:24.530> position<00:45:24.710> so 00:45:25.360 --> 00:45:25.370 align:start position:0% variables this is our position so 00:45:25.370 --> 00:45:29.230 align:start position:0% variables this is our position so variables<00:45:25.820> can<00:45:26.060> change<00:45:27.700> this<00:45:28.700> piece<00:45:29.090> is 00:45:29.230 --> 00:45:29.240 align:start position:0% variables can change this piece is 00:45:29.240 --> 00:45:30.910 align:start position:0% variables can change this piece is really<00:45:29.450> kind<00:45:29.870> of<00:45:29.960> water<00:45:30.230> state<00:45:30.560> contains 00:45:30.910 --> 00:45:30.920 align:start position:0% really kind of water state contains 00:45:30.920 --> 00:45:35.310 align:start position:0% really kind of water state contains contains<00:45:31.580> personal<00:45:33.250> right 00:45:35.310 --> 00:45:35.320 align:start position:0% contains personal right 00:45:35.320 --> 00:45:39.120 align:start position:0% contains personal right and<00:45:35.860> on<00:45:36.100> when<00:45:36.310> we<00:45:36.460> write<00:45:36.640> a<00:45:37.740> formula<00:45:38.740> like 00:45:39.120 --> 00:45:39.130 align:start position:0% and on when we write a formula like 00:45:39.130 --> 00:45:41.190 align:start position:0% and on when we write a formula like walking<00:45:39.700> group<00:45:39.940> itself<00:45:40.270> statement<00:45:40.810> amongst 00:45:41.190 --> 00:45:41.200 align:start position:0% walking group itself statement amongst 00:45:41.200 --> 00:45:44.880 align:start position:0% walking group itself statement amongst time<00:45:42.300> it<00:45:43.300> is<00:45:43.570> good<00:45:43.780> tool<00:45:43.960> to<00:45:44.080> say<00:45:44.380> what<00:45:44.770> the 00:45:44.880 --> 00:45:44.890 align:start position:0% time it is good tool to say what the 00:45:44.890 --> 00:45:46.860 align:start position:0% time it is good tool to say what the mental<00:45:45.250> model<00:45:45.580> is<00:45:45.700> and<00:45:46.000> how<00:45:46.180> you<00:45:46.240> liberate 00:45:46.860 --> 00:45:46.870 align:start position:0% mental model is and how you liberate 00:45:46.870 --> 00:45:49.230 align:start position:0% mental model is and how you liberate those<00:45:47.020> things<00:45:47.320> so<00:45:48.130> here<00:45:48.370> is<00:45:48.490> the<00:45:48.850> different 00:45:49.230 --> 00:45:49.240 align:start position:0% those things so here is the different 00:45:49.240 --> 00:45:52.140 align:start position:0% those things so here is the different example<00:45:49.780> we<00:45:49.870> have<00:45:50.050> temperature<00:45:50.590> right<00:45:51.070> so<00:45:51.340> we 00:45:52.140 --> 00:45:52.150 align:start position:0% example we have temperature right so we 00:45:52.150 --> 00:45:54.840 align:start position:0% example we have temperature right so we have<00:45:52.360> States<00:45:52.900> and<00:45:53.230> our<00:45:54.130> state<00:45:54.460> the<00:45:54.640> base 00:45:54.840 --> 00:45:54.850 align:start position:0% have States and our state the base 00:45:54.850 --> 00:45:58.530 align:start position:0% have States and our state the base constant<00:45:56.340> and<00:45:57.340> the<00:45:57.730> variable<00:45:58.180> is<00:45:58.360> the 00:45:58.530 --> 00:45:58.540 align:start position:0% constant and the variable is the 00:45:58.540 --> 00:46:02.310 align:start position:0% constant and the variable is the temperature<00:45:59.290> in<00:45:59.710> this<00:46:00.130> paper<00:46:00.810> so<00:46:01.810> time<00:46:02.080> could 00:46:02.310 --> 00:46:02.320 align:start position:0% temperature in this paper so time could 00:46:02.320 --> 00:46:03.990 align:start position:0% temperature in this paper so time could be<00:46:02.350> days<00:46:02.650> in<00:46:02.980> this<00:46:03.100> case<00:46:03.340> so<00:46:03.550> we<00:46:03.580> did<00:46:03.850> not 00:46:03.990 --> 00:46:04.000 align:start position:0% be days in this case so we did not 00:46:04.000 --> 00:46:05.850 align:start position:0% be days in this case so we did not specify<00:46:04.240> in<00:46:04.840> what<00:46:05.020> units<00:46:05.380> the<00:46:05.500> time<00:46:05.710> its 00:46:05.850 --> 00:46:05.860 align:start position:0% specify in what units the time its 00:46:05.860 --> 00:46:08.820 align:start position:0% specify in what units the time its measured<00:46:06.190> its<00:46:06.430> out<00:46:06.580> the<00:46:06.730> screen<00:46:07.000> I<00:46:07.830> think 00:46:08.820 --> 00:46:08.830 align:start position:0% measured its out the screen I think 00:46:08.830 --> 00:46:11.550 align:start position:0% measured its out the screen I think water<00:46:09.130> spicy<00:46:09.580> food<00:46:09.910> the<00:46:10.090> penalty<00:46:10.480> see<00:46:10.750> is<00:46:11.290> this 00:46:11.550 --> 00:46:11.560 align:start position:0% water spicy food the penalty see is this 00:46:11.560 --> 00:46:13.980 align:start position:0% water spicy food the penalty see is this property<00:46:12.070> here<00:46:12.640> which<00:46:13.060> says<00:46:13.210> in<00:46:13.480> virtually 00:46:13.980 --> 00:46:13.990 align:start position:0% property here which says in virtually 00:46:13.990 --> 00:46:16.650 align:start position:0% property here which says in virtually always<00:46:14.290> real<00:46:14.920> antigen<00:46:15.430> is<00:46:15.610> at<00:46:15.760> least<00:46:15.970> 11 00:46:16.650 --> 00:46:16.660 align:start position:0% always real antigen is at least 11 00:46:16.660 --> 00:46:20.730 align:start position:0% always real antigen is at least 11 degrees<00:46:17.250> right<00:46:18.250> so<00:46:18.490> it<00:46:18.820> has<00:46:18.970> some<00:46:19.740> property 00:46:20.730 --> 00:46:20.740 align:start position:0% degrees right so it has some property 00:46:20.740 --> 00:46:24.000 align:start position:0% degrees right so it has some property and<00:46:21.900> you<00:46:22.900> don't<00:46:23.110> to<00:46:23.230> see<00:46:23.410> whether<00:46:23.560> this<00:46:23.830> is 00:46:24.000 --> 00:46:24.010 align:start position:0% and you don't to see whether this is 00:46:24.010 --> 00:46:25.800 align:start position:0% and you don't to see whether this is true<00:46:24.280> for<00:46:24.490> these<00:46:24.670> things<00:46:25.030> so<00:46:25.420> this<00:46:25.570> is<00:46:25.630> the 00:46:25.800 --> 00:46:25.810 align:start position:0% true for these things so this is the 00:46:25.810 --> 00:46:28.230 align:start position:0% true for these things so this is the thanks<00:46:26.050> I<00:46:26.380> need<00:46:26.590> to<00:46:27.550> see<00:46:27.700> whether<00:46:27.880> this<00:46:28.060> is 00:46:28.230 --> 00:46:28.240 align:start position:0% thanks I need to see whether this is 00:46:28.240 --> 00:46:32.880 align:start position:0% thanks I need to see whether this is true<00:46:28.480> what<00:46:29.110> we<00:46:29.290> do<00:46:30.030> we<00:46:31.030> start<00:46:31.270> evaluating<00:46:31.890> the 00:46:32.880 --> 00:46:32.890 align:start position:0% true what we do we start evaluating the 00:46:32.890 --> 00:46:35.430 align:start position:0% true what we do we start evaluating the the<00:46:33.370> truth<00:46:33.640> of<00:46:33.940> the<00:46:34.210> still<00:46:34.450> ordinance<00:46:34.990> of<00:46:35.230> the 00:46:35.430 --> 00:46:35.440 align:start position:0% the truth of the still ordinance of the 00:46:35.440 --> 00:46:38.210 align:start position:0% the truth of the still ordinance of the parts<00:46:35.770> of<00:46:35.860> the<00:46:36.040> sentence<00:46:36.700> across<00:46:37.630> the<00:46:37.780> states 00:46:38.210 --> 00:46:38.220 align:start position:0% parts of the sentence across the states 00:46:38.220 --> 00:46:41.280 align:start position:0% parts of the sentence across the states and<00:46:39.220> for<00:46:40.150> example<00:46:40.360> that<00:46:40.660> we<00:46:40.840> kind<00:46:41.110> of<00:46:41.200> the 00:46:41.280 --> 00:46:41.290 align:start position:0% and for example that we kind of the 00:46:41.290 --> 00:46:44.790 align:start position:0% and for example that we kind of the innermost<00:46:41.650> part<00:46:42.160> is<00:46:43.560> technicalities<00:46:44.560> at 00:46:44.790 --> 00:46:44.800 align:start position:0% innermost part is technicalities at 00:46:44.800 --> 00:46:47.490 align:start position:0% innermost part is technicalities at least<00:46:45.070> 11<00:46:45.610> degrees<00:46:45.880> right<00:46:46.360> so<00:46:47.050> how<00:46:47.200> would<00:46:47.260> you 00:46:47.490 --> 00:46:47.500 align:start position:0% least 11 degrees right so how would you 00:46:47.500 --> 00:46:50.150 align:start position:0% least 11 degrees right so how would you see<00:46:47.710> which<00:46:48.130> states<00:46:48.460> this<00:46:48.880> statement<00:46:49.390> is<00:46:49.840> true 00:46:50.150 --> 00:46:50.160 align:start position:0% see which states this statement is true 00:46:50.160 --> 00:46:52.730 align:start position:0% see which states this statement is true within<00:46:51.160> each<00:46:51.490> statement<00:46:51.850> we<00:46:52.240> are<00:46:52.270> kind<00:46:52.600> of 00:46:52.730 --> 00:46:52.740 align:start position:0% within each statement we are kind of 00:46:52.740 --> 00:46:56.010 align:start position:0% within each statement we are kind of almost<00:46:53.740> like<00:46:54.190> classical<00:46:55.090> logic<00:46:55.270> to<00:46:55.510> the<00:46:55.630> movie 00:46:56.010 --> 00:46:56.020 align:start position:0% almost like classical logic to the movie 00:46:56.020 --> 00:46:58.200 align:start position:0% almost like classical logic to the movie right<00:46:56.890> and<00:46:57.190> here<00:46:57.460> we<00:46:57.670> can<00:46:57.790> see<00:46:58.060> the 00:46:58.200 --> 00:46:58.210 align:start position:0% right and here we can see the 00:46:58.210 --> 00:47:00.210 align:start position:0% right and here we can see the temperature<00:46:58.420> is<00:46:58.870> on<00:46:59.290> degrees<00:46:59.620> in<00:46:59.860> the<00:47:00.010> first 00:47:00.210 --> 00:47:00.220 align:start position:0% temperature is on degrees in the first 00:47:00.220 --> 00:47:03.660 align:start position:0% temperature is on degrees in the first state<00:47:00.490> in<00:47:00.850> the<00:47:01.450> Penn<00:47:01.660> State<00:47:01.810> and<00:47:02.560> the<00:47:02.860> last<00:47:03.070> two 00:47:03.660 --> 00:47:03.670 align:start position:0% state in the Penn State and the last two 00:47:03.670 --> 00:47:06.440 align:start position:0% state in the Penn State and the last two states<00:47:03.970> here<00:47:04.240> so<00:47:04.510> time<00:47:04.750> can<00:47:05.080> continue<00:47:05.530> opera 00:47:06.440 --> 00:47:06.450 align:start position:0% states here so time can continue opera 00:47:06.450 --> 00:47:09.450 align:start position:0% states here so time can continue opera assume<00:47:07.450> the<00:47:08.140> temperature<00:47:08.320> remains<00:47:09.010> at<00:47:09.220> least 00:47:09.450 --> 00:47:09.460 align:start position:0% assume the temperature remains at least 00:47:09.460 --> 00:47:14.580 align:start position:0% assume the temperature remains at least 11<00:47:09.880> degrees<00:47:10.150> or<00:47:11.670> so<00:47:12.670> this<00:47:12.970> is<00:47:13.240> where<00:47:13.480> this<00:47:13.900> part 00:47:14.580 --> 00:47:14.590 align:start position:0% 11 degrees or so this is where this part 00:47:14.590 --> 00:47:18.420 align:start position:0% 11 degrees or so this is where this part of<00:47:15.010> our<00:47:15.310> statement<00:47:15.670> posted<00:47:16.920> now<00:47:17.920> you<00:47:18.250> don't 00:47:18.420 --> 00:47:18.430 align:start position:0% of our statement posted now you don't 00:47:18.430 --> 00:47:21.510 align:start position:0% of our statement posted now you don't see<00:47:19.090> in<00:47:19.360> which<00:47:19.570> states<00:47:19.900> the<00:47:20.080> always<00:47:20.620> at<00:47:20.860> least 00:47:21.510 --> 00:47:21.520 align:start position:0% see in which states the always at least 00:47:21.520 --> 00:47:26.340 align:start position:0% see in which states the always at least 11<00:47:21.910> degrees<00:47:22.210> holds<00:47:22.510> true<00:47:23.220> we<00:47:24.220> need<00:47:24.370> to<00:47:24.550> look<00:47:25.350> at 00:47:26.340 --> 00:47:26.350 align:start position:0% 11 degrees holds true we need to look at 00:47:26.350 --> 00:47:28.350 align:start position:0% 11 degrees holds true we need to look at the<00:47:26.500> same<00:47:26.710> formula<00:47:27.040> and<00:47:27.370> see<00:47:27.790> whether<00:47:28.090> it 00:47:28.350 --> 00:47:28.360 align:start position:0% the same formula and see whether it 00:47:28.360 --> 00:47:29.370 align:start position:0% the same formula and see whether it always 00:47:29.370 --> 00:47:29.380 align:start position:0% always 00:47:29.380 --> 00:47:33.150 align:start position:0% always right<00:47:30.130> so<00:47:30.369> always<00:47:30.760> means<00:47:31.030> it<00:47:31.560> may<00:47:32.560> be<00:47:32.619> but 00:47:33.150 --> 00:47:33.160 align:start position:0% right so always means it may be but 00:47:33.160 --> 00:47:38.370 align:start position:0% right so always means it may be but after<00:47:33.580> four<00:47:33.880> this<00:47:33.970> is<00:47:34.030> passport<00:47:34.450> right<00:47:36.030> so<00:47:37.380> we 00:47:38.370 --> 00:47:38.380 align:start position:0% after four this is passport right so we 00:47:38.380 --> 00:47:40.650 align:start position:0% after four this is passport right so we can<00:47:38.560> ask<00:47:38.710> the<00:47:38.860> question<00:47:38.940> is<00:47:39.940> it<00:47:40.150> always<00:47:40.390> the 00:47:40.650 --> 00:47:40.660 align:start position:0% can ask the question is it always the 00:47:40.660 --> 00:47:42.690 align:start position:0% can ask the question is it always the case<00:47:40.840> the<00:47:41.050> temperature<00:47:41.619> is<00:47:41.740> at<00:47:41.950> least<00:47:42.160> 11 00:47:42.690 --> 00:47:42.700 align:start position:0% case the temperature is at least 11 00:47:42.700 --> 00:47:47.340 align:start position:0% case the temperature is at least 11 degrees<00:47:43.060> in<00:47:43.360> the<00:47:43.690> initial<00:47:44.050> state<00:47:45.480> is<00:47:46.480> all<00:47:46.840> true 00:47:47.340 --> 00:47:47.350 align:start position:0% degrees in the initial state is all true 00:47:47.350 --> 00:47:49.590 align:start position:0% degrees in the initial state is all true because<00:47:47.770> in<00:47:48.640> the<00:47:48.760> subsequent<00:47:49.119> state<00:47:49.480> the 00:47:49.590 --> 00:47:49.600 align:start position:0% because in the subsequent state the 00:47:49.600 --> 00:47:51.600 align:start position:0% because in the subsequent state the temperature<00:47:49.720> is<00:47:50.170> 10<00:47:50.380> degrees<00:47:50.410> it's<00:47:51.130> no<00:47:51.310> longer 00:47:51.600 --> 00:47:51.610 align:start position:0% temperature is 10 degrees it's no longer 00:47:51.610 --> 00:47:53.940 align:start position:0% temperature is 10 degrees it's no longer at<00:47:51.730> least<00:47:51.940> 11<00:47:52.420> right<00:47:52.780> so<00:47:52.990> it's<00:47:53.350> not<00:47:53.560> always<00:47:53.800> the 00:47:53.940 --> 00:47:53.950 align:start position:0% at least 11 right so it's not always the 00:47:53.950 --> 00:47:56.160 align:start position:0% at least 11 right so it's not always the case<00:47:54.100> that<00:47:54.580> the<00:47:54.790> temperature<00:47:55.240> is<00:47:55.570> the<00:47:55.930> place 00:47:56.160 --> 00:47:56.170 align:start position:0% case that the temperature is the place 00:47:56.170 --> 00:47:59.540 align:start position:0% case that the temperature is the place to<00:47:56.290> learn<00:47:56.380> degrees<00:47:56.740> in<00:47:56.980> the<00:47:57.130> initial<00:47:57.460> spin 00:47:59.540 --> 00:47:59.550 align:start position:0% to learn degrees in the initial spin 00:47:59.550 --> 00:48:02.340 align:start position:0% to learn degrees in the initial spin it's<00:48:00.550> also<00:48:00.910> not<00:48:01.150> always<00:48:01.540> the<00:48:01.660> case<00:48:01.840> that<00:48:01.900> it's 00:48:02.340 --> 00:48:02.350 align:start position:0% it's also not always the case that it's 00:48:02.350 --> 00:48:06.150 align:start position:0% it's also not always the case that it's in<00:48:02.920> all<00:48:03.280> these<00:48:03.520> states<00:48:04.440> until<00:48:05.440> the 00:48:06.150 --> 00:48:06.160 align:start position:0% in all these states until the 00:48:06.160 --> 00:48:08.760 align:start position:0% in all these states until the temperature<00:48:06.670> stabilizes<00:48:07.390> or<00:48:07.810> let's<00:48:08.050> say<00:48:08.170> goes 00:48:08.760 --> 00:48:08.770 align:start position:0% temperature stabilizes or let's say goes 00:48:08.770 --> 00:48:13.170 align:start position:0% temperature stabilizes or let's say goes below<00:48:09.340> 11<00:48:10.180> degrees<00:48:10.510> for<00:48:10.810> n<00:48:10.900> so<00:48:11.760> from<00:48:12.760> these 00:48:13.170 --> 00:48:13.180 align:start position:0% below 11 degrees for n so from these 00:48:13.180 --> 00:48:16.650 align:start position:0% below 11 degrees for n so from these points<00:48:13.690> onwards<00:48:14.700> this<00:48:15.700> part<00:48:15.940> of<00:48:16.119> the<00:48:16.210> formula 00:48:16.650 --> 00:48:16.660 align:start position:0% points onwards this part of the formula 00:48:16.660 --> 00:48:17.970 align:start position:0% points onwards this part of the formula will<00:48:16.990> evaluates<00:48:17.560> to<00:48:17.770> true 00:48:17.970 --> 00:48:17.980 align:start position:0% will evaluates to true 00:48:17.980 --> 00:48:20.730 align:start position:0% will evaluates to true right<00:48:18.760> so<00:48:19.090> let's<00:48:19.480> be<00:48:19.660> straight<00:48:19.900> so<00:48:20.170> is<00:48:20.619> the 00:48:20.730 --> 00:48:20.740 align:start position:0% right so let's be straight so is the 00:48:20.740 --> 00:48:22.560 align:start position:0% right so let's be straight so is the case<00:48:20.920> with<00:48:21.220> temperatures<00:48:21.790> based<00:48:22.270> learned 00:48:22.560 --> 00:48:22.570 align:start position:0% case with temperatures based learned 00:48:22.570 --> 00:48:25.859 align:start position:0% case with temperatures based learned agrees<00:48:23.369> and<00:48:24.369> out<00:48:24.610> the<00:48:24.970> final<00:48:25.360> careful 00:48:25.859 --> 00:48:25.869 align:start position:0% agrees and out the final careful 00:48:25.869 --> 00:48:28.080 align:start position:0% agrees and out the final careful temporal<00:48:26.260> operator<00:48:26.680> the<00:48:27.250> root<00:48:27.430> canal<00:48:27.760> to<00:48:27.880> hear 00:48:28.080 --> 00:48:28.090 align:start position:0% temporal operator the root canal to hear 00:48:28.090 --> 00:48:29.940 align:start position:0% temporal operator the root canal to hear is<00:48:28.240> eventually<00:48:28.660> the<00:48:29.110> case<00:48:29.500> is<00:48:29.740> always 00:48:29.940 --> 00:48:29.950 align:start position:0% is eventually the case is always 00:48:29.950 --> 00:48:32.930 align:start position:0% is eventually the case is always temperatures<00:48:30.670> these<00:48:31.030> 11<00:48:31.540> degrees<00:48:31.869> and 00:48:32.930 --> 00:48:32.940 align:start position:0% temperatures these 11 degrees and 00:48:32.940 --> 00:48:35.849 align:start position:0% temperatures these 11 degrees and eventually<00:48:33.940> is<00:48:34.150> true<00:48:34.390> in<00:48:34.510> a<00:48:34.600> given<00:48:34.930> space<00:48:35.170> in 00:48:35.849 --> 00:48:35.859 align:start position:0% eventually is true in a given space in 00:48:35.859 --> 00:48:38.640 align:start position:0% eventually is true in a given space in the<00:48:36.040> reason<00:48:36.340> future<00:48:36.640> state<00:48:36.970> when<00:48:37.540> the<00:48:38.260> soup 00:48:38.640 --> 00:48:38.650 align:start position:0% the reason future state when the soup 00:48:38.650 --> 00:48:44.460 align:start position:0% the reason future state when the soup sentence<00:48:39.640> your<00:48:40.060> Navarre<00:48:40.450> is<00:48:42.690> so<00:48:43.690> in<00:48:44.290> which 00:48:44.460 --> 00:48:44.470 align:start position:0% sentence your Navarre is so in which 00:48:44.470 --> 00:48:47.230 align:start position:0% sentence your Navarre is so in which space<00:48:44.740> is<00:48:45.010> the<00:48:45.340> full<00:48:45.670> sentence 00:48:47.230 --> 00:48:47.240 align:start position:0% space is the full sentence 00:48:47.240 --> 00:48:51.130 align:start position:0% space is the full sentence and<00:48:47.869> so<00:48:48.050> it<00:48:48.200> is<00:48:48.349> yes<00:48:49.040> everything<00:48:49.990> everything 00:48:51.130 --> 00:48:51.140 align:start position:0% and so it is yes everything everything 00:48:51.140 --> 00:48:55.030 align:start position:0% and so it is yes everything everything yes<00:48:51.680> because<00:48:52.270> no<00:48:53.270> matter<00:48:53.480> which<00:48:54.079> state<00:48:54.770> I 00:48:55.030 --> 00:48:55.040 align:start position:0% yes because no matter which state I 00:48:55.040 --> 00:49:00.520 align:start position:0% yes because no matter which state I evaluate<00:48:55.839> this<00:48:57.760> this<00:48:58.760> formula<00:48:59.030> here<00:48:59.569> there<00:49:00.410> is 00:49:00.520 --> 00:49:00.530 align:start position:0% evaluate this this formula here there is 00:49:00.530 --> 00:49:03.160 align:start position:0% evaluate this this formula here there is always<00:49:00.800> a<00:49:01.220> future<00:49:02.089> state<00:49:02.420> where<00:49:02.450> it's<00:49:02.930> always 00:49:03.160 --> 00:49:03.170 align:start position:0% always a future state where it's always 00:49:03.170 --> 00:49:06.130 align:start position:0% always a future state where it's always the<00:49:03.589> case<00:49:03.770> that<00:49:04.250> the<00:49:04.780> temperature<00:49:05.780> is<00:49:05.990> at 00:49:06.130 --> 00:49:06.140 align:start position:0% the case that the temperature is at 00:49:06.140 --> 00:49:09.130 align:start position:0% the case that the temperature is at least<00:49:06.319> 11<00:49:06.710> degrees<00:49:07.010> and<00:49:07.510> this<00:49:08.510> yellow<00:49:08.720> light 00:49:09.130 --> 00:49:09.140 align:start position:0% least 11 degrees and this yellow light 00:49:09.140 --> 00:49:14.650 align:start position:0% least 11 degrees and this yellow light dungeon<00:49:09.650> in<00:49:09.890> which<00:49:10.069> space<00:49:10.339> honest<00:49:13.180> it's<00:49:14.180> all 00:49:14.650 --> 00:49:14.660 align:start position:0% dungeon in which space honest it's all 00:49:14.660 --> 00:49:18.160 align:start position:0% dungeon in which space honest it's all these<00:49:14.930> I<00:49:15.940> guess<00:49:16.940> I<00:49:17.119> don't<00:49:17.329> understand<00:49:17.930> the 00:49:18.160 --> 00:49:18.170 align:start position:0% these I guess I don't understand the 00:49:18.170 --> 00:49:21.190 align:start position:0% these I guess I don't understand the meaning<00:49:18.200> of<00:49:18.710> that<00:49:18.770> future<00:49:19.460> state<00:49:19.670> because<00:49:20.450> how 00:49:21.190 --> 00:49:21.200 align:start position:0% meaning of that future state because how 00:49:21.200 --> 00:49:23.620 align:start position:0% meaning of that future state because how do<00:49:21.260> you<00:49:21.410> know<00:49:21.589> it's<00:49:21.859> turn<00:49:22.130> up<00:49:22.369> because<00:49:22.630> there's 00:49:23.620 --> 00:49:23.630 align:start position:0% do you know it's turn up because there's 00:49:23.630 --> 00:49:25.720 align:start position:0% do you know it's turn up because there's the<00:49:23.809> heat<00:49:24.020> death<00:49:24.290> of<00:49:24.530> the<00:49:24.589> universe<00:49:24.730> that's 00:49:25.720 --> 00:49:25.730 align:start position:0% the heat death of the universe that's 00:49:25.730 --> 00:49:29.470 align:start position:0% the heat death of the universe that's where<00:49:26.059> the<00:49:26.210> temperature<00:49:26.660> will<00:49:26.869> not<00:49:27.079> be<00:49:28.270> so<00:49:29.270> - 00:49:29.470 --> 00:49:29.480 align:start position:0% where the temperature will not be so - 00:49:29.480 --> 00:49:32.559 align:start position:0% where the temperature will not be so - so<00:49:30.470> this<00:49:30.619> is<00:49:30.770> just<00:49:30.890> an<00:49:31.069> example<00:49:31.420> it's<00:49:32.420> an 00:49:32.559 --> 00:49:32.569 align:start position:0% so this is just an example it's an 00:49:32.569 --> 00:49:35.020 align:start position:0% so this is just an example it's an example<00:49:32.869> but<00:49:33.079> there<00:49:33.319> is<00:49:33.410> no<00:49:33.559> that<00:49:34.010> is<00:49:34.849> not 00:49:35.020 --> 00:49:35.030 align:start position:0% example but there is no that is not 00:49:35.030 --> 00:49:36.490 align:start position:0% example but there is no that is not saying<00:49:35.270> that<00:49:35.359> we<00:49:35.480> don't<00:49:35.510> know<00:49:35.869> there's<00:49:36.290> going 00:49:36.490 --> 00:49:36.500 align:start position:0% saying that we don't know there's going 00:49:36.500 --> 00:49:38.890 align:start position:0% saying that we don't know there's going to<00:49:36.589> be<00:49:36.650> a<00:49:36.740> deep<00:49:36.980> death<00:49:37.250> or<00:49:37.579> not<00:49:37.760> so<00:49:38.150> okay<00:49:38.720> okay 00:49:38.890 --> 00:49:38.900 align:start position:0% to be a deep death or not so okay okay 00:49:38.900 --> 00:49:40.420 align:start position:0% to be a deep death or not so okay okay you're<00:49:39.410> absolutely<00:49:39.710> correct 00:49:40.420 --> 00:49:40.430 align:start position:0% you're absolutely correct 00:49:40.430 --> 00:49:43.390 align:start position:0% you're absolutely correct so<00:49:41.000> for<00:49:41.809> these<00:49:41.990> sentences<00:49:42.710> shows<00:49:42.920> we<00:49:43.190> cannot 00:49:43.390 --> 00:49:43.400 align:start position:0% so for these sentences shows we cannot 00:49:43.400 --> 00:49:46.089 align:start position:0% so for these sentences shows we cannot require<00:49:43.730> it<00:49:43.940> but<00:49:44.480> the<00:49:44.990> wording<00:49:45.230> liveness 00:49:46.089 --> 00:49:46.099 align:start position:0% require it but the wording liveness 00:49:46.099 --> 00:49:47.890 align:start position:0% require it but the wording liveness property<00:49:46.280> spherification<00:49:47.210> form<00:49:47.540> of<00:49:47.630> is<00:49:47.750> need 00:49:47.890 --> 00:49:47.900 align:start position:0% property spherification form of is need 00:49:47.900 --> 00:49:55.539 align:start position:0% property spherification form of is need is<00:49:48.770> more<00:49:49.550> questions<00:49:52.059> okay<00:49:53.059> good<00:49:54.190> so<00:49:55.190> let's<00:49:55.400> do 00:49:55.539 --> 00:49:55.549 align:start position:0% is more questions okay good so let's do 00:49:55.549 --> 00:49:58.420 align:start position:0% is more questions okay good so let's do a<00:49:55.579> small<00:49:55.819> quiz<00:49:56.440> register<00:49:57.440> receipt<00:49:57.890> of<00:49:58.250> this 00:49:58.420 --> 00:49:58.430 align:start position:0% a small quiz register receipt of this 00:49:58.430 --> 00:50:01.049 align:start position:0% a small quiz register receipt of this temporal<00:49:58.849> logic<00:49:59.150> queries<00:49:59.450> right<00:50:00.049> and<00:50:00.260> if<00:50:00.770> you 00:50:01.049 --> 00:50:01.059 align:start position:0% temporal logic queries right and if you 00:50:01.059 --> 00:50:04.750 align:start position:0% temporal logic queries right and if you this<00:50:02.059> is<00:50:02.210> very<00:50:02.450> unfortunate<00:50:02.720> because<00:50:03.760> this 00:50:04.750 --> 00:50:04.760 align:start position:0% this is very unfortunate because this 00:50:04.760 --> 00:50:07.650 align:start position:0% this is very unfortunate because this should<00:50:05.000> be<00:50:05.210> a<00:50:05.480> circle 00:50:07.650 --> 00:50:07.660 align:start position:0% should be a circle 00:50:07.660 --> 00:50:10.299 align:start position:0% should be a circle so<00:50:08.660> we<00:50:08.839> have<00:50:09.049> two<00:50:09.230> squares<00:50:09.589> which<00:50:09.950> is<00:50:10.069> very 00:50:10.299 --> 00:50:10.309 align:start position:0% so we have two squares which is very 00:50:10.309 --> 00:50:12.230 align:start position:0% so we have two squares which is very important 00:50:12.230 --> 00:50:12.240 align:start position:0% important 00:50:12.240 --> 00:50:14.990 align:start position:0% important it's<00:50:13.080> all<00:50:13.260> printable<00:50:13.740> character<00:50:14.130> yes<00:50:14.310> he<00:50:14.790> has 00:50:14.990 --> 00:50:15.000 align:start position:0% it's all printable character yes he has 00:50:15.000 --> 00:50:20.000 align:start position:0% it's all printable character yes he has response<00:50:15.480> Donuts<00:50:16.200> anyway<00:50:16.950> both<00:50:17.339> oh<00:50:18.830> it's<00:50:19.830> the 00:50:20.000 --> 00:50:20.010 align:start position:0% response Donuts anyway both oh it's the 00:50:20.010 --> 00:50:22.339 align:start position:0% response Donuts anyway both oh it's the walls<00:50:20.220> right<00:50:20.849> so<00:50:21.210> we<00:50:21.480> use<00:50:21.630> the<00:50:21.780> small<00:50:21.839> square 00:50:22.339 --> 00:50:22.349 align:start position:0% walls right so we use the small square 00:50:22.349 --> 00:50:27.020 align:start position:0% walls right so we use the small square to<00:50:22.560> say<00:50:22.830> always<00:50:25.160> how<00:50:26.160> do<00:50:26.220> you<00:50:26.310> say<00:50:26.460> the<00:50:26.640> diamond 00:50:27.020 --> 00:50:27.030 align:start position:0% to say always how do you say the diamond 00:50:27.030 --> 00:50:30.050 align:start position:0% to say always how do you say the diamond to<00:50:27.180> say<00:50:27.359> eventually<00:50:27.660> and<00:50:28.320> the<00:50:29.070> Botsford<00:50:29.609> is 00:50:30.050 --> 00:50:30.060 align:start position:0% to say eventually and the Botsford is 00:50:30.060 --> 00:50:33.079 align:start position:0% to say eventually and the Botsford is next<00:50:30.630> something<00:50:31.140> is<00:50:31.320> doing<00:50:31.530> the<00:50:31.710> next<00:50:31.920> step<00:50:32.160> so 00:50:33.079 --> 00:50:33.089 align:start position:0% next something is doing the next step so 00:50:33.089 --> 00:50:35.420 align:start position:0% next something is doing the next step so what<00:50:33.240> does<00:50:33.420> this<00:50:33.599> sentence<00:50:34.410> say<00:50:34.800> right<00:50:35.280> you 00:50:35.420 --> 00:50:35.430 align:start position:0% what does this sentence say right you 00:50:35.430 --> 00:50:39.620 align:start position:0% what does this sentence say right you have<00:50:35.640> two<00:50:36.800> formulas<00:50:37.800> or<00:50:38.040> two<00:50:38.880> predicates<00:50:39.330> P 00:50:39.620 --> 00:50:39.630 align:start position:0% have two formulas or two predicates P 00:50:39.630 --> 00:50:43.130 align:start position:0% have two formulas or two predicates P and<00:50:39.869> Q<00:50:40.230> and<00:50:40.609> this<00:50:41.609> thing<00:50:41.880> says<00:50:42.119> be<00:50:42.480> advised 00:50:43.130 --> 00:50:43.140 align:start position:0% and Q and this thing says be advised 00:50:43.140 --> 00:50:46.089 align:start position:0% and Q and this thing says be advised that<00:50:43.170> eventually<00:50:44.040> to<00:50:44.250> write<00:50:44.849> these<00:50:45.359> purposes 00:50:46.089 --> 00:50:46.099 align:start position:0% that eventually to write these purposes 00:50:46.099 --> 00:50:48.470 align:start position:0% that eventually to write these purposes so<00:50:47.099> of<00:50:47.250> how<00:50:47.460> do<00:50:47.520> you<00:50:47.670> interpret<00:50:48.180> this 00:50:48.470 --> 00:50:48.480 align:start position:0% so of how do you interpret this 00:50:48.480 --> 00:50:55.950 align:start position:0% so of how do you interpret this informally<00:50:49.170> with<00:50:49.530> what<00:50:50.280> we<00:50:50.430> understand 00:50:55.950 --> 00:50:55.960 align:start position:0% 00:50:55.960 --> 00:50:59.220 align:start position:0% okay<00:50:56.740> let<00:50:56.920> me<00:50:57.190> tell<00:50:57.460> you<00:50:57.640> either<00:50:58.660> there's<00:50:58.930> pee 00:50:59.220 --> 00:50:59.230 align:start position:0% okay let me tell you either there's pee 00:50:59.230 --> 00:51:01.830 align:start position:0% okay let me tell you either there's pee there<00:50:59.680> will<00:50:59.860> eventually<00:51:00.300> here<00:51:01.300> will<00:51:01.450> happen 00:51:01.830 --> 00:51:01.840 align:start position:0% there will eventually here will happen 00:51:01.840 --> 00:51:05.520 align:start position:0% there will eventually here will happen yes<00:51:02.290> there's<00:51:02.740> pee<00:51:02.980> yes<00:51:03.430> soul<00:51:04.210> soul<00:51:04.480> yes<00:51:04.870> I<00:51:05.140> put 00:51:05.520 --> 00:51:05.530 align:start position:0% yes there's pee yes soul soul yes I put 00:51:05.530 --> 00:51:07.410 align:start position:0% yes there's pee yes soul soul yes I put this<00:51:05.680> example<00:51:06.220> just<00:51:06.580> to<00:51:06.610> represent<00:51:07.210> something 00:51:07.410 --> 00:51:07.420 align:start position:0% this example just to represent something 00:51:07.420 --> 00:51:11.070 align:start position:0% this example just to represent something when<00:51:08.580> we<00:51:09.580> are<00:51:09.640> a<00:51:09.880> volunteer<00:51:10.060> for<00:51:10.660> dinner<00:51:10.930> will 00:51:11.070 --> 00:51:11.080 align:start position:0% when we are a volunteer for dinner will 00:51:11.080 --> 00:51:12.690 align:start position:0% when we are a volunteer for dinner will ever<00:51:11.410> I<00:51:11.440> think<00:51:11.710> it's<00:51:11.890> always<00:51:12.160> in<00:51:12.310> the<00:51:12.400> initial 00:51:12.690 --> 00:51:12.700 align:start position:0% ever I think it's always in the initial 00:51:12.700 --> 00:51:16.460 align:start position:0% ever I think it's always in the initial state<00:51:13.320> right<00:51:14.320> so<00:51:14.500> there<00:51:14.800> is<00:51:14.890> a<00:51:15.040> slight 00:51:16.460 --> 00:51:16.470 align:start position:0% state right so there is a slight 00:51:16.470 --> 00:51:19.380 align:start position:0% state right so there is a slight something<00:51:17.470> in<00:51:17.620> this<00:51:17.800> sub<00:51:18.220> script<00:51:18.460> written<00:51:19.090> by 00:51:19.380 --> 00:51:19.390 align:start position:0% something in this sub script written by 00:51:19.390 --> 00:51:21.840 align:start position:0% something in this sub script written by we're<00:51:20.200> always<00:51:20.440> about<00:51:20.770> the<00:51:20.950> initiative<00:51:21.640> site 00:51:21.840 --> 00:51:21.850 align:start position:0% we're always about the initiative site 00:51:21.850 --> 00:51:27.180 align:start position:0% we're always about the initiative site so<00:51:22.030> you're<00:51:22.180> almost<00:51:22.480> yes<00:51:24.780> right<00:51:25.780> we<00:51:26.380> operate 00:51:27.180 --> 00:51:27.190 align:start position:0% so you're almost yes right we operate 00:51:27.190 --> 00:51:29.790 align:start position:0% so you're almost yes right we operate these<00:51:27.460> militia<00:51:27.850> say<00:51:28.120> if<00:51:28.630> initially<00:51:29.170> P<00:51:29.380> is<00:51:29.560> true 00:51:29.790 --> 00:51:29.800 align:start position:0% these militia say if initially P is true 00:51:29.800 --> 00:51:32.100 align:start position:0% these militia say if initially P is true then<00:51:30.100> you<00:51:30.520> start<00:51:30.760> with<00:51:30.880> your<00:51:31.060> moment<00:51:31.420> or<00:51:31.810> the 00:51:32.100 --> 00:51:32.110 align:start position:0% then you start with your moment or the 00:51:32.110 --> 00:51:34.830 align:start position:0% then you start with your moment or the current<00:51:32.410> moment<00:51:32.610> eventually<00:51:33.610> song<00:51:33.820> is<00:51:34.630> for 00:51:34.830 --> 00:51:34.840 align:start position:0% current moment eventually song is for 00:51:34.840 --> 00:51:38.850 align:start position:0% current moment eventually song is for the<00:51:35.020> current<00:51:35.260> moment<00:51:35.410> coupons<00:51:36.300> and<00:51:37.740> what<00:51:38.740> you 00:51:38.850 --> 00:51:38.860 align:start position:0% the current moment coupons and what you 00:51:38.860 --> 00:51:41.250 align:start position:0% the current moment coupons and what you said<00:51:39.160> we<00:51:39.760> can<00:51:39.940> formalize<00:51:40.510> with<00:51:40.780> it's<00:51:41.050> always 00:51:41.250 --> 00:51:41.260 align:start position:0% said we can formalize with it's always 00:51:41.260 --> 00:51:46.470 align:start position:0% said we can formalize with it's always the<00:51:41.500> case<00:51:41.740> he<00:51:42.100> holds<00:51:42.550> eventually<00:51:45.270> so<00:51:46.270> no 00:51:46.470 --> 00:51:46.480 align:start position:0% the case he holds eventually so no 00:51:46.480 --> 00:51:48.000 align:start position:0% the case he holds eventually so no matter<00:51:46.720> whether<00:51:46.930> its<00:51:47.140> initial<00:51:47.590> state<00:51:47.830> or 00:51:48.000 --> 00:51:48.010 align:start position:0% matter whether its initial state or 00:51:48.010 --> 00:51:50.430 align:start position:0% matter whether its initial state or initial<00:51:48.520> state<00:51:48.700> for<00:51:48.940> every<00:51:49.090> state<00:51:49.480> in<00:51:50.290> this 00:51:50.430 --> 00:51:50.440 align:start position:0% initial state for every state in this 00:51:50.440 --> 00:51:59.400 align:start position:0% initial state for every state in this boat<00:51:53.910> okay<00:51:54.910> so<00:51:55.330> what<00:51:55.480> about<00:51:55.630> this<00:51:55.900> one<00:51:58.410> always 00:51:59.400 --> 00:51:59.410 align:start position:0% boat okay so what about this one always 00:51:59.410 --> 00:52:01.770 align:start position:0% boat okay so what about this one always eventually<00:52:00.060> they<00:52:01.060> just<00:52:01.120> get<00:52:01.540> some 00:52:01.770 --> 00:52:01.780 align:start position:0% eventually they just get some 00:52:01.780 --> 00:52:09.660 align:start position:0% eventually they just get some alternative<00:52:02.500> description<00:52:03.070> of<00:52:03.220> this 00:52:09.660 --> 00:52:09.670 align:start position:0% 00:52:09.670 --> 00:52:12.410 align:start position:0% yes<00:52:10.269> it's<00:52:10.569> a<00:52:10.660> possible<00:52:11.049> 4p<00:52:11.410> never<00:52:11.740> happened 00:52:12.410 --> 00:52:12.420 align:start position:0% yes it's a possible 4p never happened 00:52:12.420 --> 00:52:14.789 align:start position:0% yes it's a possible 4p never happened yes<00:52:13.420> you<00:52:13.569> can<00:52:13.720> play<00:52:13.839> with<00:52:14.049> the<00:52:14.230> de<00:52:14.440> Morgan's 00:52:14.789 --> 00:52:14.799 align:start position:0% yes you can play with the de Morgan's 00:52:14.799 --> 00:52:16.170 align:start position:0% yes you can play with the de Morgan's laws<00:52:14.980> yes<00:52:15.250> yes<00:52:15.460> this<00:52:15.789> is<00:52:15.970> alternative 00:52:16.170 --> 00:52:16.180 align:start position:0% laws yes yes this is alternative 00:52:16.180 --> 00:52:19.109 align:start position:0% laws yes yes this is alternative descriptions<00:52:16.930> but<00:52:17.289> it's<00:52:17.440> another<00:52:17.890> game<00:52:18.549> with 00:52:19.109 --> 00:52:19.119 align:start position:0% descriptions but it's another game with 00:52:19.119 --> 00:52:24.359 align:start position:0% descriptions but it's another game with alone<00:52:19.359> this<00:52:20.519> is<00:52:21.519> purely<00:52:22.299> off<00:52:22.539> exactly<00:52:23.170> yes<00:52:23.980> so 00:52:24.359 --> 00:52:24.369 align:start position:0% alone this is purely off exactly yes so 00:52:24.369 --> 00:52:27.120 align:start position:0% alone this is purely off exactly yes so you<00:52:24.579> can<00:52:24.779> interpret<00:52:25.779> this<00:52:25.990> because<00:52:26.799> we<00:52:26.980> have 00:52:27.120 --> 00:52:27.130 align:start position:0% you can interpret this because we have 00:52:27.130 --> 00:52:29.130 align:start position:0% you can interpret this because we have to<00:52:27.250> have<00:52:27.279> time<00:52:27.819> for<00:52:27.880> anything<00:52:28.180> theory<00:52:28.779> you<00:52:28.930> say 00:52:29.130 --> 00:52:29.140 align:start position:0% to have time for anything theory you say 00:52:29.140 --> 00:52:32.099 align:start position:0% to have time for anything theory you say P<00:52:29.710> is<00:52:30.400> 2<00:52:30.640> infinitely<00:52:31.059> offer<00:52:31.210> me<00:52:31.480> it's<00:52:31.930> always 00:52:32.099 --> 00:52:32.109 align:start position:0% P is 2 infinitely offer me it's always 00:52:32.109 --> 00:52:35.130 align:start position:0% P is 2 infinitely offer me it's always the<00:52:32.289> case<00:52:32.440> eventually<00:52:32.740> P<00:52:33.279> holds<00:52:33.519> but<00:52:34.089> if<00:52:34.839> we 00:52:35.130 --> 00:52:35.140 align:start position:0% the case eventually P holds but if we 00:52:35.140 --> 00:52:37.650 align:start position:0% the case eventually P holds but if we eventually<00:52:35.410> result<00:52:36.160> in<00:52:36.250> some<00:52:37.180> futures<00:52:37.480> that 00:52:37.650 --> 00:52:37.660 align:start position:0% eventually result in some futures that 00:52:37.660 --> 00:52:40.019 align:start position:0% eventually result in some futures that it<00:52:37.839> also<00:52:38.019> must<00:52:38.349> eventually<00:52:38.680> also<00:52:39.369> this<00:52:39.730> will 00:52:40.019 --> 00:52:40.029 align:start position:0% it also must eventually also this will 00:52:40.029 --> 00:52:43.440 align:start position:0% it also must eventually also this will be<00:52:40.180> different<00:52:40.890> right<00:52:41.890> and<00:52:42.880> what<00:52:43.029> about<00:52:43.240> this 00:52:43.440 --> 00:52:43.450 align:start position:0% be different right and what about this 00:52:43.450 --> 00:52:43.890 align:start position:0% be different right and what about this one 00:52:43.890 --> 00:52:43.900 align:start position:0% one 00:52:43.900 --> 00:52:51.660 align:start position:0% one if<00:52:43.960> we<00:52:44.200> swap 00:52:51.660 --> 00:52:51.670 align:start position:0% 00:52:51.670 --> 00:52:58.980 align:start position:0% venturing<00:52:52.420> always<00:52:52.660> because<00:52:52.960> yes<00:52:57.720> okay<00:52:58.720> I<00:52:58.750> just 00:52:58.980 --> 00:52:58.990 align:start position:0% venturing always because yes okay I just 00:52:58.990 --> 00:53:03.570 align:start position:0% venturing always because yes okay I just wanted<00:52:59.470> some<00:52:59.650> floral<00:53:00.250> oh<00:53:00.340> that<00:53:00.550> is<00:53:00.670> $50<00:53:02.130> off<00:53:03.130> a 00:53:03.570 --> 00:53:03.580 align:start position:0% wanted some floral oh that is $50 off a 00:53:03.580 --> 00:53:06.420 align:start position:0% wanted some floral oh that is $50 off a shelf<00:53:03.820> a<00:53:04.120> face<00:53:04.420> spell<00:53:05.260> on<00:53:05.410> what<00:53:05.860> is<00:53:05.980> written<00:53:06.190> in 00:53:06.420 --> 00:53:06.430 align:start position:0% shelf a face spell on what is written in 00:53:06.430 --> 00:53:08.850 align:start position:0% shelf a face spell on what is written in these<00:53:06.970> little<00:53:07.270> oddities<00:53:07.420> this<00:53:08.290> basically 00:53:08.850 --> 00:53:08.860 align:start position:0% these little oddities this basically 00:53:08.860 --> 00:53:11.550 align:start position:0% these little oddities this basically says<00:53:09.100> it<00:53:09.280> eventually<00:53:10.240> be<00:53:10.510> stabilizes<00:53:11.290> and 00:53:11.550 --> 00:53:11.560 align:start position:0% says it eventually be stabilizes and 00:53:11.560 --> 00:53:13.860 align:start position:0% says it eventually be stabilizes and from<00:53:11.890> certain<00:53:12.100> moment<00:53:12.910> onwards<00:53:13.390> P<00:53:13.660> will 00:53:13.860 --> 00:53:13.870 align:start position:0% from certain moment onwards P will 00:53:13.870 --> 00:53:19.950 align:start position:0% from certain moment onwards P will always<00:53:14.520> be<00:53:16.140> okay<00:53:17.140> well<00:53:17.980> we<00:53:18.550> have<00:53:18.730> Sigma<00:53:19.360> show 00:53:19.950 --> 00:53:19.960 align:start position:0% always be okay well we have Sigma show 00:53:19.960 --> 00:53:23.400 align:start position:0% always be okay well we have Sigma show so<00:53:20.830> we<00:53:20.980> got<00:53:21.190> into<00:53:21.460> this<00:53:21.610> one<00:53:21.820> so<00:53:22.510> what<00:53:23.080> does<00:53:23.260> it 00:53:23.400 --> 00:53:23.410 align:start position:0% so we got into this one so what does it 00:53:23.410 --> 00:53:29.460 align:start position:0% so we got into this one so what does it say<00:53:25.470> it's<00:53:26.470> from<00:53:27.190> any<00:53:27.460> state<00:53:27.880> that<00:53:28.150> is<00:53:28.690> produced 00:53:29.460 --> 00:53:29.470 align:start position:0% say it's from any state that is produced 00:53:29.470 --> 00:53:31.980 align:start position:0% say it's from any state that is produced through<00:53:29.680> that<00:53:30.220> state<00:53:30.550> every<00:53:30.940> state<00:53:31.000> over<00:53:31.480> in 00:53:31.980 --> 00:53:31.990 align:start position:0% through that state every state over in 00:53:31.990 --> 00:53:35.300 align:start position:0% through that state every state over in every<00:53:32.410> state<00:53:32.620> after<00:53:32.860> and<00:53:33.520> why<00:53:33.670> is<00:53:33.730> these<00:53:33.910> days 00:53:35.300 --> 00:53:35.310 align:start position:0% every state after and why is these days 00:53:35.310 --> 00:53:51.290 align:start position:0% every state after and why is these days this<00:53:36.310> is<00:53:41.160> this<00:53:42.160> is<00:53:42.310> this<00:53:43.000> is<00:53:43.180> the<00:53:43.300> boss<00:53:43.710> next 00:53:51.290 --> 00:53:51.300 align:start position:0% 00:53:51.300 --> 00:53:52.830 align:start position:0% but<00:53:52.300> it's<00:53:52.480> true 00:53:52.830 --> 00:53:52.840 align:start position:0% but it's true 00:53:52.840 --> 00:53:54.570 align:start position:0% but it's true actually<00:53:53.170> what<00:53:53.290> you<00:53:53.410> said<00:53:53.620> right<00:53:53.890> so<00:53:54.130> if<00:53:54.430> you 00:53:54.570 --> 00:53:54.580 align:start position:0% actually what you said right so if you 00:53:54.580 --> 00:53:57.320 align:start position:0% actually what you said right so if you interpret<00:53:54.910> this<00:53:55.030> next<00:53:55.570> as<00:53:55.780> next<00:53:56.230> right 00:53:57.320 --> 00:53:57.330 align:start position:0% interpret this next as next right 00:53:57.330 --> 00:54:01.950 align:start position:0% interpret this next as next right it's<00:53:58.330> always<00:53:58.840> the<00:53:59.050> case<00:53:59.260> right<00:54:00.150> if<00:54:01.150> P<00:54:01.510> holds 00:54:01.950 --> 00:54:01.960 align:start position:0% it's always the case right if P holds 00:54:01.960 --> 00:54:07.580 align:start position:0% it's always the case right if P holds that<00:54:02.440> in<00:54:02.710> the<00:54:02.800> next<00:54:03.010> case<00:54:05.580> parents<00:54:06.580> never<00:54:06.850> P 00:54:07.580 --> 00:54:07.590 align:start position:0% that in the next case parents never P 00:54:07.590 --> 00:54:12.300 align:start position:0% that in the next case parents never P sorry<00:54:08.610> P<00:54:09.610> will<00:54:09.790> never<00:54:10.030> be<00:54:10.270> true<00:54:10.890> why<00:54:11.890> do<00:54:12.160> you 00:54:12.300 --> 00:54:12.310 align:start position:0% sorry P will never be true why do you 00:54:12.310 --> 00:54:13.529 align:start position:0% sorry P will never be true why do you know 00:54:13.529 --> 00:54:13.539 align:start position:0% know 00:54:13.539 --> 00:54:17.309 align:start position:0% know then<00:54:13.959> the<00:54:14.469> next<00:54:14.799> state<00:54:15.130> would<00:54:15.369> be<00:54:15.639> Q<00:54:16.059> and<00:54:16.509> they 00:54:17.309 --> 00:54:17.319 align:start position:0% then the next state would be Q and they 00:54:17.319 --> 00:54:18.719 align:start position:0% then the next state would be Q and they are<00:54:17.469> not<00:54:17.649> mutually<00:54:17.769> exclusive 00:54:18.719 --> 00:54:18.729 align:start position:0% are not mutually exclusive 00:54:18.729 --> 00:54:21.929 align:start position:0% are not mutually exclusive I'm<00:54:19.659> officially<00:54:20.469> exclusive<00:54:21.130> then<00:54:21.339> also<00:54:21.519> that 00:54:21.929 --> 00:54:21.939 align:start position:0% I'm officially exclusive then also that 00:54:21.939 --> 00:54:24.389 align:start position:0% I'm officially exclusive then also that I<00:54:21.969> just<00:54:22.179> fear<00:54:22.449> is<00:54:22.569> always<00:54:22.779> followed<00:54:23.289> by<00:54:23.319> yes<00:54:24.069> P 00:54:24.389 --> 00:54:24.399 align:start position:0% I just fear is always followed by yes P 00:54:24.399 --> 00:54:26.069 align:start position:0% I just fear is always followed by yes P is<00:54:24.459> always<00:54:24.669> followed<00:54:25.059> by<00:54:25.089> the<00:54:25.269> decisions 00:54:26.069 --> 00:54:26.079 align:start position:0% is always followed by the decisions 00:54:26.079 --> 00:54:28.139 align:start position:0% is always followed by the decisions right<00:54:26.469> and<00:54:27.039> now<00:54:27.130> you<00:54:27.189> have<00:54:27.459> what<00:54:27.759> you<00:54:27.909> said 00:54:28.139 --> 00:54:28.149 align:start position:0% right and now you have what you said 00:54:28.149 --> 00:54:31.919 align:start position:0% right and now you have what you said right<00:54:28.329> is<00:54:28.569> if<00:54:29.499> P<00:54:29.679> holds<00:54:30.269> afterwards<00:54:31.269> all<00:54:31.599> words 00:54:31.919 --> 00:54:31.929 align:start position:0% right is if P holds afterwards all words 00:54:31.929 --> 00:54:37.109 align:start position:0% right is if P holds afterwards all words and<00:54:32.139> to<00:54:32.259> infinity<00:54:32.799> Q<00:54:32.979> will<00:54:33.159> pop<00:54:35.579> good<00:54:36.579> socially 00:54:37.109 --> 00:54:37.119 align:start position:0% and to infinity Q will pop good socially 00:54:37.119 --> 00:54:42.179 align:start position:0% and to infinity Q will pop good socially sure<00:54:37.179> most<00:54:37.539> of<00:54:37.689> us<00:54:37.929> one<00:54:38.349> of<00:54:38.380> us<00:54:39.269> we<00:54:40.889> put<00:54:41.889> so<00:54:42.039> many 00:54:42.179 --> 00:54:42.189 align:start position:0% sure most of us one of us we put so many 00:54:42.189 --> 00:54:45.479 align:start position:0% sure most of us one of us we put so many buddy<00:54:42.839> okay<00:54:43.839> so<00:54:44.079> this<00:54:44.259> one<00:54:44.499> is<00:54:44.589> more<00:54:44.649> complex 00:54:45.479 --> 00:54:45.489 align:start position:0% buddy okay so this one is more complex 00:54:45.489 --> 00:54:48.839 align:start position:0% buddy okay so this one is more complex it<00:54:46.479> says<00:54:46.749> it's<00:54:46.989> always<00:54:47.169> the<00:54:47.349> case<00:54:47.759> there<00:54:48.759> is 00:54:48.839 --> 00:54:48.849 align:start position:0% it says it's always the case there is 00:54:48.849 --> 00:54:52.079 align:start position:0% it says it's always the case there is some<00:54:49.179> constant<00:54:49.779> and<00:54:49.989> signals<00:54:50.889> in<00:54:51.459> this<00:54:51.789> case 00:54:52.079 --> 00:54:52.089 align:start position:0% some constant and signals in this case 00:54:52.089 --> 00:54:54.719 align:start position:0% some constant and signals in this case the<00:54:52.630> block<00:54:52.929> equals<00:54:53.380> them<00:54:53.589> and<00:54:53.829> in<00:54:54.399> the<00:54:54.549> next 00:54:54.719 --> 00:54:54.729 align:start position:0% the block equals them and in the next 00:54:54.729 --> 00:54:55.259 align:start position:0% the block equals them and in the next case 00:54:55.259 --> 00:54:55.269 align:start position:0% case 00:54:55.269 --> 00:54:59.939 align:start position:0% case rocky<00:54:55.599> possible<00:54:56.049> possible<00:54:57.630> yes<00:54:58.630> the<00:54:59.259> closest 00:54:59.939 --> 00:54:59.949 align:start position:0% rocky possible possible yes the closest 00:54:59.949 --> 00:55:03.929 align:start position:0% rocky possible possible yes the closest value<00:55:00.159> and<00:55:01.979> yes<00:55:02.979> the<00:55:03.189> clock<00:55:03.579> always 00:55:03.929 --> 00:55:03.939 align:start position:0% value and yes the clock always 00:55:03.939 --> 00:55:07.589 align:start position:0% value and yes the clock always increments<00:55:04.689> by<00:55:04.869> 1<00:55:05.459> this<00:55:06.459> is<00:55:06.639> decision<00:55:07.359> all 00:55:07.589 --> 00:55:07.599 align:start position:0% increments by 1 this is decision all 00:55:07.599 --> 00:55:10.139 align:start position:0% increments by 1 this is decision all these<00:55:07.779> property<00:55:08.319> steps<00:55:08.609> and<00:55:09.609> assorted 00:55:10.139 --> 00:55:10.149 align:start position:0% these property steps and assorted 00:55:10.149 --> 00:55:12.029 align:start position:0% these property steps and assorted so<00:55:10.509> this<00:55:10.689> is<00:55:10.809> kind<00:55:11.019> of<00:55:11.079> food<00:55:11.289> temporal<00:55:11.709> logic 00:55:12.029 --> 00:55:12.039 align:start position:0% so this is kind of food temporal logic 00:55:12.039 --> 00:55:13.379 align:start position:0% so this is kind of food temporal logic right<00:55:12.189> you<00:55:12.369> can<00:55:12.519> write<00:55:12.699> many<00:55:12.909> complex 00:55:13.379 --> 00:55:13.389 align:start position:0% right you can write many complex 00:55:13.389 --> 00:55:15.629 align:start position:0% right you can write many complex formulas<00:55:14.079> and<00:55:14.289> statements<00:55:14.889> in<00:55:15.069> temporal 00:55:15.629 --> 00:55:15.639 align:start position:0% formulas and statements in temporal 00:55:15.639 --> 00:55:20.639 align:start position:0% formulas and statements in temporal logic<00:55:16.439> code<00:55:17.439> always<00:55:18.029> ticks<00:55:19.109> ticks<00:55:20.109> by<00:55:20.409> one 00:55:20.639 --> 00:55:20.649 align:start position:0% logic code always ticks ticks by one 00:55:20.649 --> 00:55:41.200 align:start position:0% logic code always ticks ticks by one increment<00:55:21.249> is<00:55:21.669> correct<00:55:24.509> yes 00:55:41.200 --> 00:55:41.210 align:start position:0% 00:55:41.210 --> 00:55:45.650 align:start position:0% around<00:55:42.210> three<00:55:43.160> four<00:55:44.160> four<00:55:44.400> four<00:55:44.760> four<00:55:44.790> is<00:55:45.300> down 00:55:45.650 --> 00:55:45.660 align:start position:0% around three four four four four is down 00:55:45.660 --> 00:55:48.410 align:start position:0% around three four four four four is down the<00:55:45.810> dog<00:55:46.080> it<00:55:46.230> doesn't<00:55:46.560> move<00:55:46.710> okay<00:55:47.160> it's<00:55:48.000> okay 00:55:48.410 --> 00:55:48.420 align:start position:0% the dog it doesn't move okay it's okay 00:55:48.420 --> 00:55:50.990 align:start position:0% the dog it doesn't move okay it's okay good<00:55:48.780> so<00:55:49.230> now<00:55:49.410> how<00:55:49.620> all<00:55:49.830> these<00:55:50.040> applies<00:55:50.760> to 00:55:50.990 --> 00:55:51.000 align:start position:0% good so now how all these applies to 00:55:51.000 --> 00:55:54.580 align:start position:0% good so now how all these applies to smart<00:55:51.240> companies<00:55:51.660> right<00:55:52.520> so<00:55:53.520> what<00:55:53.730> we<00:55:53.880> do<00:55:54.060> here 00:55:54.580 --> 00:55:54.590 align:start position:0% smart companies right so what we do here 00:55:54.590 --> 00:55:58.340 align:start position:0% smart companies right so what we do here we<00:55:55.590> need<00:55:56.190> to<00:55:56.280> fix<00:55:56.520> you<00:55:56.730> up<00:55:56.760> kinda<00:55:57.390> needs<00:55:57.630> first 00:55:58.340 --> 00:55:58.350 align:start position:0% we need to fix you up kinda needs first 00:55:58.350 --> 00:56:00.710 align:start position:0% we need to fix you up kinda needs first first<00:55:58.710> and<00:55:58.980> foremost<00:55:59.190> and<00:55:59.700> what<00:55:59.940> we<00:56:00.120> do<00:56:00.240> is<00:56:00.390> we 00:56:00.710 --> 00:56:00.720 align:start position:0% first and foremost and what we do is we 00:56:00.720 --> 00:56:03.320 align:start position:0% first and foremost and what we do is we do<00:56:00.840> the<00:56:00.870> following<00:56:01.160> we<00:56:02.160> have<00:56:02.190> world<00:56:02.700> space<00:56:03.000> in 00:56:03.320 --> 00:56:03.330 align:start position:0% do the following we have world space in 00:56:03.330 --> 00:56:04.910 align:start position:0% do the following we have world space in the<00:56:03.480> world<00:56:03.600> states<00:56:03.960> are<00:56:04.230> the<00:56:04.380> states<00:56:04.650> of<00:56:04.800> the 00:56:04.910 --> 00:56:04.920 align:start position:0% the world states are the states of the 00:56:04.920 --> 00:56:06.890 align:start position:0% the world states are the states of the whole<00:56:05.070> ball<00:56:05.340> chain<00:56:05.610> in<00:56:05.880> between<00:56:05.910> samples 00:56:06.890 --> 00:56:06.900 align:start position:0% whole ball chain in between samples 00:56:06.900 --> 00:56:09.530 align:start position:0% whole ball chain in between samples right<00:56:07.380> so<00:56:08.040> whatever<00:56:08.610> you're<00:56:08.850> gonna<00:56:08.970> depend 00:56:09.530 --> 00:56:09.540 align:start position:0% right so whatever you're gonna depend 00:56:09.540 --> 00:56:10.970 align:start position:0% right so whatever you're gonna depend somewhat<00:56:09.930> change<00:56:10.200> to<00:56:10.320> always<00:56:10.620> around<00:56:10.890> the 00:56:10.970 --> 00:56:10.980 align:start position:0% somewhat change to always around the 00:56:10.980 --> 00:56:13.580 align:start position:0% somewhat change to always around the thing<00:56:11.220> inside<00:56:11.430> the<00:56:11.760> transaction<00:56:12.300> and<00:56:12.590> our 00:56:13.580 --> 00:56:13.590 align:start position:0% thing inside the transaction and our 00:56:13.590 --> 00:56:16.040 align:start position:0% thing inside the transaction and our space<00:56:14.130> will<00:56:15.060> be<00:56:15.210> the<00:56:15.330> boots<00:56:15.540> length<00:56:15.840> of<00:56:15.960> the 00:56:16.040 --> 00:56:16.050 align:start position:0% space will be the boots length of the 00:56:16.050 --> 00:56:18.470 align:start position:0% space will be the boots length of the book<00:56:16.230> chain<00:56:16.500> and<00:56:16.920> diamond<00:56:17.760> comment<00:56:18.090> means<00:56:18.240> the 00:56:18.470 --> 00:56:18.480 align:start position:0% book chain and diamond comment means the 00:56:18.480 --> 00:56:21.710 align:start position:0% book chain and diamond comment means the execution<00:56:18.960> of<00:56:19.020> a<00:56:19.110> single<00:56:19.440> transaction<00:56:20.720> right 00:56:21.710 --> 00:56:21.720 align:start position:0% execution of a single transaction right 00:56:21.720 --> 00:56:24.830 align:start position:0% execution of a single transaction right this<00:56:22.080> is<00:56:22.230> what<00:56:22.380> we<00:56:22.500> do<00:56:22.650> and<00:56:23.270> we<00:56:24.270> don't<00:56:24.450> support 00:56:24.830 --> 00:56:24.840 align:start position:0% this is what we do and we don't support 00:56:24.840 --> 00:56:27.770 align:start position:0% this is what we do and we don't support the<00:56:25.230> food<00:56:25.470> that<00:56:25.890> parolee<00:56:26.340> we<00:56:27.210> serve<00:56:27.390> on<00:56:27.540> Jesse 00:56:27.770 --> 00:56:27.780 align:start position:0% the food that parolee we serve on Jesse 00:56:27.780 --> 00:56:29.600 align:start position:0% the food that parolee we serve on Jesse primarily<00:56:28.380> which<00:56:28.860> is<00:56:29.010> called<00:56:29.250> canonical 00:56:29.600 --> 00:56:29.610 align:start position:0% primarily which is called canonical 00:56:29.610 --> 00:56:31.730 align:start position:0% primarily which is called canonical safety<00:56:30.210> bragging<00:56:30.600> but<00:56:30.750> are<00:56:30.960> not<00:56:31.080> gone<00:56:31.320> in 00:56:31.730 --> 00:56:31.740 align:start position:0% safety bragging but are not gone in 00:56:31.740 --> 00:56:35.570 align:start position:0% safety bragging but are not gone in details<00:56:32.190> and<00:56:33.530> roughly<00:56:34.530> looks<00:56:34.800> like<00:56:35.040> this 00:56:35.570 --> 00:56:35.580 align:start position:0% details and roughly looks like this 00:56:35.580 --> 00:56:39.080 align:start position:0% details and roughly looks like this he<00:56:36.090> always<00:56:36.290> your<00:56:37.290> formula<00:56:37.890> soup<00:56:38.070> of<00:56:38.430> this<00:56:38.790> form 00:56:39.080 --> 00:56:39.090 align:start position:0% he always your formula soup of this form 00:56:39.090 --> 00:56:42.350 align:start position:0% he always your formula soup of this form always<00:56:39.660> P<00:56:40.020> will<00:56:40.500> be<00:56:40.530> some<00:56:40.980> formula<00:56:41.520> of<00:56:41.670> the 00:56:42.350 --> 00:56:42.360 align:start position:0% always P will be some formula of the 00:56:42.360 --> 00:56:44.840 align:start position:0% always P will be some formula of the point<00:56:42.720> shape<00:56:42.960> so<00:56:43.890> you<00:56:43.950> have<00:56:44.190> logical 00:56:44.840 --> 00:56:44.850 align:start position:0% point shape so you have logical 00:56:44.850 --> 00:56:47.750 align:start position:0% point shape so you have logical conjunctions<00:56:45.450> p.m.<00:56:45.990> you<00:56:46.260> have<00:56:47.130> distinction 00:56:47.750 --> 00:56:47.760 align:start position:0% conjunctions p.m. you have distinction 00:56:47.760 --> 00:56:53.300 align:start position:0% conjunctions p.m. you have distinction people<00:56:48.740> it<00:56:49.740> has<00:56:50.010> implication<00:56:50.790> P<00:56:50.940> implies<00:56:52.310> you 00:56:53.300 --> 00:56:53.310 align:start position:0% people it has implication P implies you 00:56:53.310 --> 00:56:55.010 align:start position:0% people it has implication P implies you have<00:56:53.340> this<00:56:53.670> very<00:56:54.030> interesting<00:56:54.270> operator 00:56:55.010 --> 00:56:55.020 align:start position:0% have this very interesting operator 00:56:55.020 --> 00:56:57.020 align:start position:0% have this very interesting operator which<00:56:55.260> is<00:56:55.380> temporal<00:56:55.770> operator<00:56:56.130> one<00:56:56.610> speed 00:56:57.020 --> 00:56:57.030 align:start position:0% which is temporal operator one speed 00:56:57.030 --> 00:56:58.940 align:start position:0% which is temporal operator one speed which<00:56:57.390> means<00:56:57.630> that<00:56:57.780> once<00:56:58.020> in<00:56:58.230> the<00:56:58.320> past<00:56:58.500> it<00:56:58.830> was 00:56:58.940 --> 00:56:58.950 align:start position:0% which means that once in the past it was 00:56:58.950 --> 00:57:03.260 align:start position:0% which means that once in the past it was called<00:57:00.680> this<00:57:01.680> is<00:57:01.860> the<00:57:01.890> primary<00:57:02.490> person<00:57:02.910> of<00:57:03.150> the 00:57:03.260 --> 00:57:03.270 align:start position:0% called this is the primary person of the 00:57:03.270 --> 00:57:05.090 align:start position:0% called this is the primary person of the eventual<00:57:03.750> operator<00:57:04.170> so<00:57:04.530> we<00:57:04.650> can<00:57:04.800> eventually 00:57:05.090 --> 00:57:05.100 align:start position:0% eventual operator so we can eventually 00:57:05.100 --> 00:57:08.090 align:start position:0% eventual operator so we can eventually meaning<00:57:05.580> in<00:57:05.790> future<00:57:06.120> moment<00:57:06.590> P<00:57:07.590> will<00:57:07.830> call 00:57:08.090 --> 00:57:08.100 align:start position:0% meaning in future moment P will call 00:57:08.100 --> 00:57:11.600 align:start position:0% meaning in future moment P will call this<00:57:08.730> reason<00:57:09.150> in<00:57:09.540> the<00:57:09.780> past<00:57:09.810> few<00:57:10.320> scope<00:57:10.740> or<00:57:11.550> the 00:57:11.600 --> 00:57:11.610 align:start position:0% this reason in the past few scope or the 00:57:11.610 --> 00:57:14.380 align:start position:0% this reason in the past few scope or the current<00:57:12.150> speed<00:57:12.330> yes<00:57:12.990> who<00:57:13.650> is<00:57:13.800> one 00:57:14.380 --> 00:57:14.390 align:start position:0% current speed yes who is one 00:57:14.390 --> 00:57:17.560 align:start position:0% current speed yes who is one who<00:57:15.170> are<00:57:15.320> these<00:57:15.470> ones<00:57:15.800> of<00:57:16.070> those<00:57:16.250> swans 00:57:17.560 --> 00:57:17.570 align:start position:0% who are these ones of those swans 00:57:17.570 --> 00:57:19.480 align:start position:0% who are these ones of those swans so<00:57:17.990> it's<00:57:18.170> not<00:57:18.260> exactly<00:57:18.440> wants<00:57:18.920> me<00:57:19.010> that<00:57:19.340> these 00:57:19.480 --> 00:57:19.490 align:start position:0% so it's not exactly wants me that these 00:57:19.490 --> 00:57:24.580 align:start position:0% so it's not exactly wants me that these ones<00:57:19.760> so<00:57:19.970> II<00:57:20.390> some<00:57:21.940> possible<00:57:23.200> this<00:57:24.200> is<00:57:24.320> what<00:57:24.470> we 00:57:24.580 --> 00:57:24.590 align:start position:0% ones so II some possible this is what we 00:57:24.590 --> 00:57:24.940 align:start position:0% ones so II some possible this is what we do 00:57:24.940 --> 00:57:24.950 align:start position:0% do 00:57:24.950 --> 00:57:27.640 align:start position:0% do and<00:57:25.400> finally<00:57:26.390> whenever<00:57:27.140> you<00:57:27.320> have<00:57:27.470> some 00:57:27.640 --> 00:57:27.650 align:start position:0% and finally whenever you have some 00:57:27.650 --> 00:57:29.350 align:start position:0% and finally whenever you have some expression<00:57:27.980> you<00:57:28.370> can<00:57:28.550> refer<00:57:28.880> to<00:57:28.910> the<00:57:29.150> previous 00:57:29.350 --> 00:57:29.360 align:start position:0% expression you can refer to the previous 00:57:29.360 --> 00:57:31.330 align:start position:0% expression you can refer to the previous value<00:57:29.840> of<00:57:29.990> this<00:57:30.200> expression<00:57:30.560> so<00:57:30.950> this<00:57:31.130> is 00:57:31.330 --> 00:57:31.340 align:start position:0% value of this expression so this is 00:57:31.340 --> 00:57:34.300 align:start position:0% value of this expression so this is similar<00:57:32.180> to<00:57:32.360> the<00:57:32.570> next<00:57:32.840> operator<00:57:33.260> so<00:57:33.980> in<00:57:34.190> the 00:57:34.300 --> 00:57:34.310 align:start position:0% similar to the next operator so in the 00:57:34.310 --> 00:57:35.800 align:start position:0% similar to the next operator so in the previous<00:57:34.460> states<00:57:34.880> the<00:57:35.330> weight<00:57:35.510> of<00:57:35.660> this 00:57:35.800 --> 00:57:35.810 align:start position:0% previous states the weight of this 00:57:35.810 --> 00:57:37.990 align:start position:0% previous states the weight of this expression<00:57:36.320> was<00:57:36.500> something<00:57:37.190> right<00:57:37.520> so<00:57:37.760> nearly 00:57:37.990 --> 00:57:38.000 align:start position:0% expression was something right so nearly 00:57:38.000 --> 00:57:40.750 align:start position:0% expression was something right so nearly one<00:57:38.210> refers<00:57:39.080> to<00:57:39.110> the<00:57:39.290> previous<00:57:39.680> value<00:57:39.980> of<00:57:40.610> the 00:57:40.750 --> 00:57:40.760 align:start position:0% one refers to the previous value of the 00:57:40.760 --> 00:57:44.620 align:start position:0% one refers to the previous value of the expression<00:57:41.050> piece<00:57:42.050> of<00:57:42.200> the<00:57:42.320> pie<00:57:42.470> spins<00:57:43.570> by<00:57:44.570> the 00:57:44.620 --> 00:57:44.630 align:start position:0% expression piece of the pie spins by the 00:57:44.630 --> 00:57:46.600 align:start position:0% expression piece of the pie spins by the way<00:57:44.840> what<00:57:45.530> happens<00:57:45.980> in<00:57:46.160> the<00:57:46.280> initial 00:57:46.600 --> 00:57:46.610 align:start position:0% way what happens in the initial 00:57:46.610 --> 00:57:48.190 align:start position:0% way what happens in the initial statement<00:57:47.060> there<00:57:47.270> is<00:57:47.360> no<00:57:47.540> previous<00:57:47.750> thing 00:57:48.190 --> 00:57:48.200 align:start position:0% statement there is no previous thing 00:57:48.200 --> 00:57:54.340 align:start position:0% statement there is no previous thing what<00:57:48.890> do<00:57:49.010> you<00:57:49.070> think<00:57:52.360> so<00:57:53.360> when<00:57:53.900> there<00:57:54.050> was<00:57:54.230> no 00:57:54.340 --> 00:57:54.350 align:start position:0% what do you think so when there was no 00:57:54.350 --> 00:57:56.500 align:start position:0% what do you think so when there was no initial<00:57:54.710> stages<00:57:55.160> for<00:57:55.400> simplicity<00:57:56.060> we<00:57:56.090> take 00:57:56.500 --> 00:57:56.510 align:start position:0% initial stages for simplicity we take 00:57:56.510 --> 00:57:58.390 align:start position:0% initial stages for simplicity we take the<00:57:56.750> previous<00:57:57.020> method<00:57:57.320> with<00:57:57.500> equipment<00:57:57.920> in 00:57:58.390 --> 00:57:58.400 align:start position:0% the previous method with equipment in 00:57:58.400 --> 00:58:00.270 align:start position:0% the previous method with equipment in the<00:57:58.670> usual<00:57:59.000> state<00:57:59.210> remember<00:58:00.020> it<00:58:00.080> is<00:58:00.230> very 00:58:00.270 --> 00:58:00.280 align:start position:0% the usual state remember it is very 00:58:00.280 --> 00:58:06.820 align:start position:0% the usual state remember it is very sometimes<00:58:05.080> okay<00:58:06.080> and<00:58:06.290> now<00:58:06.350> we<00:58:06.410> have<00:58:06.650> some 00:58:06.820 --> 00:58:06.830 align:start position:0% sometimes okay and now we have some 00:58:06.830 --> 00:58:10.390 align:start position:0% sometimes okay and now we have some specific<00:58:07.660> because<00:58:08.660> we<00:58:08.870> after<00:58:09.200> all<00:58:09.400> drinking 00:58:10.390 --> 00:58:10.400 align:start position:0% specific because we after all drinking 00:58:10.400 --> 00:58:14.500 align:start position:0% specific because we after all drinking some<00:58:10.640> video<00:58:11.080> so<00:58:12.190> all<00:58:13.190> these<00:58:13.340> we<00:58:13.640> support<00:58:13.970> suma 00:58:14.500 --> 00:58:14.510 align:start position:0% some video so all these we support suma 00:58:14.510 --> 00:58:17.730 align:start position:0% some video so all these we support suma topics<00:58:14.930> right<00:58:15.500> so<00:58:15.920> universities<00:58:16.820> among<00:58:16.940> a<00:58:17.090> few 00:58:17.730 --> 00:58:17.740 align:start position:0% topics right so universities among a few 00:58:17.740 --> 00:58:20.800 align:start position:0% topics right so universities among a few second<00:58:18.740> token<00:58:18.890> contract<00:58:19.490> we<00:58:19.610> can<00:58:19.940> refer<00:58:20.780> to 00:58:20.800 --> 00:58:20.810 align:start position:0% second token contract we can refer to 00:58:20.810 --> 00:58:24.100 align:start position:0% second token contract we can refer to the<00:58:21.020> same<00:58:21.200> of<00:58:21.380> all<00:58:21.500> these<00:58:21.680> things<00:58:23.110> function 00:58:24.100 --> 00:58:24.110 align:start position:0% the same of all these things function 00:58:24.110 --> 00:58:26.350 align:start position:0% the same of all these things function reduce<00:58:24.590> the<00:58:25.160> the<00:58:25.190> name<00:58:25.730> of<00:58:26.000> the<00:58:26.150> function 00:58:26.350 --> 00:58:26.360 align:start position:0% reduce the the name of the function 00:58:26.360 --> 00:58:28.720 align:start position:0% reduce the the name of the function which<00:58:26.900> is<00:58:27.050> called<00:58:27.350> in<00:58:27.650> this<00:58:27.920> transaction<00:58:28.340> the 00:58:28.720 --> 00:58:28.730 align:start position:0% which is called in this transaction the 00:58:28.730 --> 00:58:31.090 align:start position:0% which is called in this transaction the top<00:58:28.940> level<00:58:29.270> function<00:58:29.710> feminised<00:58:30.710> of<00:58:30.860> course 00:58:31.090 --> 00:58:31.100 align:start position:0% top level function feminised of course 00:58:31.100 --> 00:58:33.810 align:start position:0% top level function feminised of course we<00:58:31.910> kind<00:58:32.150> of<00:58:32.240> start<00:58:32.690> business<00:58:33.080> that<00:58:33.230> goes<00:58:33.410> away 00:58:33.810 --> 00:58:33.820 align:start position:0% we kind of start business that goes away 00:58:33.820 --> 00:58:36.580 align:start position:0% we kind of start business that goes away we<00:58:34.820> can<00:58:35.360> refer<00:58:35.630> only<00:58:35.870> to<00:58:36.050> the<00:58:36.230> top<00:58:36.380> level 00:58:36.580 --> 00:58:36.590 align:start position:0% we can refer only to the top level 00:58:36.590 --> 00:58:42.520 align:start position:0% we can refer only to the top level transaction<00:58:37.540> the<00:58:38.540> transaction<00:58:39.880> we<00:58:40.880> can<00:58:41.530> refer 00:58:42.520 --> 00:58:42.530 align:start position:0% transaction the transaction we can refer 00:58:42.530 --> 00:58:44.290 align:start position:0% transaction the transaction we can refer to<00:58:42.680> function<00:58:43.040> rights<00:58:43.250> so<00:58:43.640> this<00:58:43.790> is<00:58:43.940> the<00:58:44.120> syntax 00:58:44.290 --> 00:58:44.300 align:start position:0% to function rights so this is the syntax 00:58:44.300 --> 00:58:47.320 align:start position:0% to function rights so this is the syntax for<00:58:44.570> defining<00:58:44.780> the<00:58:45.050> function<00:58:45.530> name<00:58:46.180> we<00:58:47.180> can 00:58:47.320 --> 00:58:47.330 align:start position:0% for defining the function name we can 00:58:47.330 --> 00:58:49.990 align:start position:0% for defining the function name we can also<00:58:47.450> affect<00:58:47.900> the<00:58:47.990> balance<00:58:48.200> of<00:58:48.590> functions<00:58:49.040> so 00:58:49.990 --> 00:58:50.000 align:start position:0% also affect the balance of functions so 00:58:50.000 --> 00:58:51.940 align:start position:0% also affect the balance of functions so since<00:58:50.420> this<00:58:50.510> is<00:58:50.660> a<00:58:50.780> little<00:58:50.900> bit<00:58:51.110> emphasized<00:58:51.620> we 00:58:51.940 --> 00:58:51.950 align:start position:0% since this is a little bit emphasized we 00:58:51.950 --> 00:58:54.160 align:start position:0% since this is a little bit emphasized we are<00:58:52.100> going<00:58:52.310> to<00:58:52.460> be<00:58:52.700> moving<00:58:53.090> in<00:58:53.210> the<00:58:53.300> future<00:58:53.660> so 00:58:54.160 --> 00:58:54.170 align:start position:0% are going to be moving in the future so 00:58:54.170 --> 00:58:56.860 align:start position:0% are going to be moving in the future so this<00:58:54.440> is<00:58:54.620> the<00:58:54.980> zeroth<00:58:55.310> argument<00:58:55.510> the<00:58:56.510> title 00:58:56.860 --> 00:58:56.870 align:start position:0% this is the zeroth argument the title 00:58:56.870 --> 00:58:58.990 align:start position:0% this is the zeroth argument the title information<00:58:56.960> and<00:58:57.830> if<00:58:58.340> you<00:58:58.460> know<00:58:58.580> what<00:58:58.730> you<00:58:58.850> do 00:58:58.990 --> 00:58:59.000 align:start position:0% information and if you know what you do 00:58:59.000 --> 00:58:59.790 align:start position:0% information and if you know what you do is<00:58:59.090> you<00:58:59.300> know 00:58:59.790 --> 00:58:59.800 align:start position:0% is you know 00:58:59.800 --> 00:59:02.320 align:start position:0% is you know canonical<00:59:00.800> name<00:59:00.950> of<00:59:01.160> the<00:59:01.250> function<00:59:01.430> so<00:59:02.180> this 00:59:02.320 --> 00:59:02.330 align:start position:0% canonical name of the function so this 00:59:02.330 --> 00:59:03.700 align:start position:0% canonical name of the function so this is<00:59:02.510> the<00:59:02.600> name<00:59:02.750> of<00:59:02.780> the<00:59:02.990> counterplay<00:59:03.500> of<00:59:03.620> the 00:59:03.700 --> 00:59:03.710 align:start position:0% is the name of the counterplay of the 00:59:03.710 --> 00:59:05.530 align:start position:0% is the name of the counterplay of the function<00:59:04.100> and<00:59:04.280> here<00:59:04.520> for<00:59:05.000> the<00:59:05.090> signature<00:59:05.390> of 00:59:05.530 --> 00:59:05.540 align:start position:0% function and here for the signature of 00:59:05.540 --> 00:59:08.890 align:start position:0% function and here for the signature of the<00:59:05.720> function<00:59:05.750> with<00:59:06.560> addresses<00:59:07.660> and<00:59:08.660> this<00:59:08.780> is 00:59:08.890 --> 00:59:08.900 align:start position:0% the function with addresses and this is 00:59:08.900 --> 00:59:24.020 align:start position:0% the function with addresses and this is what<00:59:09.050> Evers<00:59:10.990> yes<00:59:15.220> okay 00:59:24.020 --> 00:59:24.030 align:start position:0% 00:59:24.030 --> 00:59:26.390 align:start position:0% so<00:59:24.660> we<00:59:25.170> don't<00:59:25.380> support<00:59:25.650> specification<00:59:26.340> of 00:59:26.390 --> 00:59:26.400 align:start position:0% so we don't support specification of 00:59:26.400 --> 00:59:29.360 align:start position:0% so we don't support specification of love<00:59:26.610> invariance<00:59:27.180> so<00:59:27.600> all<00:59:28.140> we<00:59:28.410> do<00:59:28.590> with<00:59:28.950> spaces 00:59:29.360 --> 00:59:29.370 align:start position:0% love invariance so all we do with spaces 00:59:29.370 --> 00:59:31.400 align:start position:0% love invariance so all we do with spaces specified<00:59:30.090> let's<00:59:30.420> go<00:59:30.570> a<00:59:30.600> transaction<00:59:31.320> in 00:59:31.400 --> 00:59:31.410 align:start position:0% specified let's go a transaction in 00:59:31.410 --> 00:59:33.200 align:start position:0% specified let's go a transaction in readiness<00:59:31.710> starting<00:59:32.340> our<00:59:32.490> thoughts<00:59:32.760> across 00:59:33.200 --> 00:59:33.210 align:start position:0% readiness starting our thoughts across 00:59:33.210 --> 00:59:39.890 align:start position:0% readiness starting our thoughts across transactions<00:59:38.150> what<00:59:39.150> if<00:59:39.330> we<00:59:39.510> have<00:59:39.690> known 00:59:39.890 --> 00:59:39.900 align:start position:0% transactions what if we have known 00:59:39.900 --> 00:59:41.360 align:start position:0% transactions what if we have known Toulouse<00:59:40.320> in<00:59:40.530> the<00:59:40.620> country<00:59:40.980> it's<00:59:41.100> shown<00:59:41.280> in 00:59:41.360 --> 00:59:41.370 align:start position:0% Toulouse in the country it's shown in 00:59:41.370 --> 00:59:43.460 align:start position:0% Toulouse in the country it's shown in some<00:59:41.610> cases<00:59:41.880> we<00:59:42.180> can<00:59:42.210> rewrite<00:59:42.660> us<00:59:42.900> rewrite 00:59:43.460 --> 00:59:43.470 align:start position:0% some cases we can rewrite us rewrite 00:59:43.470 --> 00:59:46.280 align:start position:0% some cases we can rewrite us rewrite them<00:59:43.830> without<00:59:44.100> whose<00:59:44.400> but<00:59:45.150> if<00:59:45.810> you<00:59:45.990> have<00:59:46.140> not 00:59:46.280 --> 00:59:46.290 align:start position:0% them without whose but if you have not 00:59:46.290 --> 00:59:48.260 align:start position:0% them without whose but if you have not develops<00:59:46.800> we<00:59:47.010> unfortunately<00:59:47.490> don't<00:59:47.940> support 00:59:48.260 --> 00:59:48.270 align:start position:0% develops we unfortunately don't support 00:59:48.270 --> 00:59:53.710 align:start position:0% develops we unfortunately don't support it<00:59:48.510> yes<00:59:50.870> yes 00:59:53.710 --> 00:59:53.720 align:start position:0% it yes yes 00:59:53.720 --> 00:59:57.320 align:start position:0% it yes yes oh<00:59:54.860> I<00:59:55.860> have<00:59:56.100> forgot<00:59:56.460> that<00:59:56.610> yes<00:59:56.790> they<00:59:57.060> sell 00:59:57.320 --> 00:59:57.330 align:start position:0% oh I have forgot that yes they sell 00:59:57.330 --> 00:59:59.960 align:start position:0% oh I have forgot that yes they sell something<00:59:57.600> Asian<00:59:57.750> soon<00:59:58.230> yes<00:59:59.010> I<00:59:59.280> build<00:59:59.910> a 00:59:59.960 --> 00:59:59.970 align:start position:0% something Asian soon yes I build a 00:59:59.970 --> 01:00:03.710 align:start position:0% something Asian soon yes I build a negation<01:00:00.240> yes<01:00:01.110> so<01:00:02.070> we've<01:00:03.000> got<01:00:03.150> business<01:00:03.330> but 01:00:03.710 --> 01:00:03.720 align:start position:0% negation yes so we've got business but 01:00:03.720 --> 01:00:05.210 align:start position:0% negation yes so we've got business but you<01:00:03.869> said<01:00:04.080> earlier<01:00:04.440> that<01:00:04.470> you<01:00:05.070> know<01:00:05.100> you 01:00:05.210 --> 01:00:05.220 align:start position:0% you said earlier that you know you 01:00:05.220 --> 01:00:07.280 align:start position:0% you said earlier that you know you evaluate<01:00:05.940> formula<01:00:06.150> always<01:00:06.480> in<01:00:06.750> the<01:00:06.869> initial<01:00:07.140> C 01:00:07.280 --> 01:00:07.290 align:start position:0% evaluate formula always in the initial C 01:00:07.290 --> 01:00:11.660 align:start position:0% evaluate formula always in the initial C in<01:00:07.980> classical<01:00:08.520> temporal<01:00:08.970> yes<01:00:09.240> so<01:00:09.869> what<01:00:10.490> is<01:00:11.490> the 01:00:11.660 --> 01:00:11.670 align:start position:0% in classical temporal yes so what is the 01:00:11.670 --> 01:00:14.120 align:start position:0% in classical temporal yes so what is the semantics<01:00:12.119> different<01:00:12.450> Allen<01:00:12.750> know<01:00:13.440> is<01:00:13.890> the 01:00:14.120 --> 01:00:14.130 align:start position:0% semantics different Allen know is the 01:00:14.130 --> 01:00:17.600 align:start position:0% semantics different Allen know is the same<01:00:14.330> age<01:00:15.330> is<01:00:15.630> that<01:00:15.810> we<01:00:16.320> support<01:00:16.470> formulas<01:00:17.400> of 01:00:17.600 --> 01:00:17.610 align:start position:0% same age is that we support formulas of 01:00:17.610 --> 01:00:24.350 align:start position:0% same age is that we support formulas of the<01:00:17.730> shape<01:00:17.940> always<01:00:18.450> be<01:00:18.869> like<01:00:22.310> yes<01:00:23.310> if<01:00:24.180> we're 01:00:24.350 --> 01:00:24.360 align:start position:0% the shape always be like yes if we're 01:00:24.360 --> 01:00:25.850 align:start position:0% the shape always be like yes if we're always<01:00:24.510> evaluating<01:00:24.900> in<01:00:25.260> the<01:00:25.350> initial<01:00:25.650> state 01:00:25.850 --> 01:00:25.860 align:start position:0% always evaluating in the initial state 01:00:25.860 --> 01:00:29.390 align:start position:0% always evaluating in the initial state I'll<01:00:26.520> show<01:00:27.480> you<01:00:28.080> all<01:00:28.290> right<01:00:28.619> evaluates<01:00:29.160> the 01:00:29.390 --> 01:00:29.400 align:start position:0% I'll show you all right evaluates the 01:00:29.400 --> 01:00:31.460 align:start position:0% I'll show you all right evaluates the top<01:00:29.670> level<01:00:30.000> of<01:00:30.119> the<01:00:30.180> formula<01:00:30.720> in<01:00:30.990> the<01:00:31.020> initial 01:00:31.460 --> 01:00:31.470 align:start position:0% top level of the formula in the initial 01:00:31.470 --> 01:00:35.150 align:start position:0% top level of the formula in the initial state<01:00:31.770> right<01:00:33.140> but<01:00:34.140> it<01:00:34.380> could<01:00:34.619> happen<01:00:34.950> that 01:00:35.150 --> 01:00:35.160 align:start position:0% state right but it could happen that 01:00:35.160 --> 01:00:38.570 align:start position:0% state right but it could happen that when<01:00:35.940> you<01:00:36.060> say<01:00:36.240> always<01:00:36.570> this<01:00:37.470> means<01:00:37.710> that<01:00:37.860> the 01:00:38.570 --> 01:00:38.580 align:start position:0% when you say always this means that the 01:00:38.580 --> 01:00:40.550 align:start position:0% when you say always this means that the inner<01:00:38.820> part<01:00:39.150> of<01:00:39.270> the<01:00:39.390> formula<01:00:39.869> needs<01:00:40.110> to<01:00:40.230> be<01:00:40.530> a 01:00:40.550 --> 01:00:40.560 align:start position:0% inner part of the formula needs to be a 01:00:40.560 --> 01:00:43.100 align:start position:0% inner part of the formula needs to be a warranted<01:00:41.040> in<01:00:41.190> all<01:00:41.310> states<01:00:41.930> this<01:00:42.930> is<01:00:42.990> the 01:00:43.100 --> 01:00:43.110 align:start position:0% warranted in all states this is the 01:00:43.110 --> 01:00:45.410 align:start position:0% warranted in all states this is the semantics<01:00:43.680> of<01:00:43.770> the<01:00:43.830> always<01:00:44.100> operated<01:00:44.640> so<01:00:45.150> from 01:00:45.410 --> 01:00:45.420 align:start position:0% semantics of the always operated so from 01:00:45.420 --> 01:00:48.170 align:start position:0% semantics of the always operated so from formula<01:00:46.260> to<01:00:46.410> say<01:00:46.560> formula<01:00:47.130> you<01:00:47.580> change<01:00:47.910> the 01:00:48.170 --> 01:00:48.180 align:start position:0% formula to say formula you change the 01:00:48.180 --> 01:00:50.990 align:start position:0% formula to say formula you change the point<01:00:48.420> at<01:00:48.600> which<01:00:48.720> you've<01:00:48.930> already<01:00:50.000> right 01:00:50.990 --> 01:00:51.000 align:start position:0% point at which you've already right 01:00:51.000 --> 01:00:52.790 align:start position:0% point at which you've already right depending<01:00:51.660> on<01:00:51.869> the<01:00:52.020> semantics<01:00:52.530> of<01:00:52.680> the 01:00:52.790 --> 01:00:52.800 align:start position:0% depending on the semantics of the 01:00:52.800 --> 01:00:55.370 align:start position:0% depending on the semantics of the temporal<01:00:53.160> operators<01:00:53.780> you<01:00:54.780> change<01:00:55.020> the<01:00:55.140> point 01:00:55.370 --> 01:00:55.380 align:start position:0% temporal operators you change the point 01:00:55.380 --> 01:00:57.410 align:start position:0% temporal operators you change the point that<01:00:55.560> one<01:00:55.770> of<01:00:55.950> which<01:00:56.430> you<01:00:56.460> evaluate<01:00:57.150> the 01:00:57.410 --> 01:00:57.420 align:start position:0% that one of which you evaluate the 01:00:57.420 --> 01:01:00.170 align:start position:0% that one of which you evaluate the formula<01:00:58.350> right<01:00:58.590> so<01:00:58.950> always<01:00:59.340> change<01:00:59.910> is<01:01:00.060> the 01:01:00.170 --> 01:01:00.180 align:start position:0% formula right so always change is the 01:01:00.180 --> 01:01:01.670 align:start position:0% formula right so always change is the point<01:01:00.420> at<01:01:00.600> which<01:01:00.630> you're<01:01:00.930> worried<01:01:01.260> you'll<01:01:01.470> by 01:01:01.670 --> 01:01:01.680 align:start position:0% point at which you're worried you'll by 01:01:01.680 --> 01:01:03.650 align:start position:0% point at which you're worried you'll by borrowing<01:01:02.040> in<01:01:02.250> all<01:01:02.460> points<01:01:02.730> from<01:01:03.210> the<01:01:03.330> current 01:01:03.650 --> 01:01:03.660 align:start position:0% borrowing in all points from the current 01:01:03.660 --> 01:01:11.370 align:start position:0% borrowing in all points from the current point<01:01:03.840> onwards<01:01:04.940> and<01:01:05.940> does<01:01:06.180> the 01:01:11.370 --> 01:01:11.380 align:start position:0% 01:01:11.380 --> 01:01:15.250 align:start position:0% so<01:01:12.380> you<01:01:12.670> have<01:01:13.670> alright<01:01:13.940> form<01:01:14.210> is<01:01:14.330> always<01:01:14.690> nice 01:01:15.250 --> 01:01:15.260 align:start position:0% so you have alright form is always nice 01:01:15.260 --> 01:01:20.800 align:start position:0% so you have alright form is always nice you<01:01:16.040> know<01:01:16.160> state<01:01:17.710> okay<01:01:18.710> good<01:01:19.359> so<01:01:20.359> now<01:01:20.570> let's 01:01:20.800 --> 01:01:20.810 align:start position:0% you know state okay good so now let's 01:01:20.810 --> 01:01:23.730 align:start position:0% you know state okay good so now let's move<01:01:20.930> on<01:01:21.140> to<01:01:21.170> duster<01:01:21.820> small<01:01:22.820> quick<01:01:23.089> question 01:01:23.730 --> 01:01:23.740 align:start position:0% move on to duster small quick question 01:01:23.740 --> 01:01:27.700 align:start position:0% move on to duster small quick question next<01:01:24.740> on<01:01:25.040> the<01:01:25.220> box<01:01:25.940> on<01:01:26.150> the<01:01:26.930> left<01:01:26.960> you<01:01:27.680> have 01:01:27.700 --> 01:01:27.710 align:start position:0% next on the box on the left you have 01:01:27.710 --> 01:01:29.400 align:start position:0% next on the box on the left you have once<01:01:28.099> the<01:01:28.310> previous<01:01:28.700> there's<01:01:28.940> no<01:01:29.089> next 01:01:29.400 --> 01:01:29.410 align:start position:0% once the previous there's no next 01:01:29.410 --> 01:01:31.829 align:start position:0% once the previous there's no next there's<01:01:30.410> your<01:01:30.589> next<01:01:30.740> we<01:01:31.070> don't<01:01:31.250> support<01:01:31.520> it 01:01:31.829 --> 01:01:31.839 align:start position:0% there's your next we don't support it 01:01:31.839 --> 01:01:37.660 align:start position:0% there's your next we don't support it yes<01:01:32.839> we're<01:01:33.140> somewhat<01:01:33.950> limited<01:01:36.369> but<01:01:37.369> many 01:01:37.660 --> 01:01:37.670 align:start position:0% yes we're somewhat limited but many 01:01:37.670 --> 01:01:39.790 align:start position:0% yes we're somewhat limited but many things<01:01:37.910> that<01:01:38.480> you<01:01:38.630> can<01:01:38.750> express<01:01:39.140> with<01:01:39.410> next 01:01:39.790 --> 01:01:39.800 align:start position:0% things that you can express with next 01:01:39.800 --> 01:01:42.190 align:start position:0% things that you can express with next actually<01:01:40.339> you<01:01:40.640> can<01:01:40.820> express<01:01:41.180> in<01:01:41.780> this<01:01:41.990> way 01:01:42.190 --> 01:01:42.200 align:start position:0% actually you can express in this way 01:01:42.200 --> 01:01:47.430 align:start position:0% actually you can express in this way just<01:01:42.470> you<01:01:43.070> need<01:01:43.220> to<01:01:43.280> massage<01:01:43.760> your<01:01:44.150> formula 01:01:47.430 --> 01:01:47.440 align:start position:0% 01:01:47.440 --> 01:02:01.780 align:start position:0% but<01:01:48.440> you<01:01:53.020> don't<01:01:59.740> we<01:02:00.740> require<01:02:01.280> always<01:02:01.550> to<01:02:01.670> be 01:02:01.780 --> 01:02:01.790 align:start position:0% but you don't we require always to be 01:02:01.790 --> 01:02:04.510 align:start position:0% but you don't we require always to be the<01:02:01.910> top<01:02:02.089> level<01:02:02.480> right<01:02:03.170> so<01:02:03.650> never<01:02:03.859> again<01:02:04.040> yes 01:02:04.510 --> 01:02:04.520 align:start position:0% the top level right so never again yes 01:02:04.520 --> 01:02:06.940 align:start position:0% the top level right so never again yes you<01:02:04.670> cannot<01:02:04.849> think<01:02:05.089> it<01:02:05.180> never<01:02:05.780> again<01:02:06.020> yes<01:02:06.410> this 01:02:06.940 --> 01:02:06.950 align:start position:0% you cannot think it never again yes this 01:02:06.950 --> 01:02:11.099 align:start position:0% you cannot think it never again yes this is<01:02:07.160> always<01:02:08.030> a<01:02:08.270> and<01:02:08.540> ease<01:02:09.050> even<01:02:09.560> maybe<01:02:09.710> simplex 01:02:11.099 --> 01:02:11.109 align:start position:0% is always a and ease even maybe simplex 01:02:11.109 --> 01:02:19.150 align:start position:0% is always a and ease even maybe simplex always<01:02:12.109> have<01:02:12.320> rewards<01:02:12.890> you<01:02:13.280> always<01:02:17.740> sorry<01:02:18.740> you 01:02:19.150 --> 01:02:19.160 align:start position:0% always have rewards you always sorry you 01:02:19.160 --> 01:02:20.859 align:start position:0% always have rewards you always sorry you write<01:02:19.460> it<01:02:19.580> down<01:02:19.760> yes<01:02:20.000> we<01:02:20.240> even<01:02:20.480> write<01:02:20.630> it<01:02:20.780> down 01:02:20.859 --> 01:02:20.869 align:start position:0% write it down yes we even write it down 01:02:20.869 --> 01:02:27.280 align:start position:0% write it down yes we even write it down in<01:02:21.050> this<01:02:21.109> formulation<01:02:25.480> is<01:02:26.480> contract 01:02:27.280 --> 01:02:27.290 align:start position:0% in this formulation is contract 01:02:27.290 --> 01:02:30.760 align:start position:0% in this formulation is contract authorities<01:02:28.119> all<01:02:29.119> 13<01:02:29.420> variants<01:02:29.810> exactly<01:02:30.320> and 01:02:30.760 --> 01:02:30.770 align:start position:0% authorities all 13 variants exactly and 01:02:30.770 --> 01:02:33.670 align:start position:0% authorities all 13 variants exactly and say<01:02:31.640> this<01:02:31.849> way<01:02:32.030> is<01:02:32.330> but<01:02:32.720> he<01:02:32.839> also<01:02:32.990> can<01:02:33.260> refer<01:02:33.530> to 01:02:33.670 --> 01:02:33.680 align:start position:0% say this way is but he also can refer to 01:02:33.680 --> 01:02:35.829 align:start position:0% say this way is but he also can refer to the<01:02:33.770> positive<01:02:34.220> x<01:02:34.430> service<01:02:34.849> as<01:02:35.300> kind<01:02:35.750> of 01:02:35.829 --> 01:02:35.839 align:start position:0% the positive x service as kind of 01:02:35.839 --> 01:02:40.960 align:start position:0% the positive x service as kind of coating<01:02:36.320> so<01:02:37.599> this<01:02:38.599> Pierce<01:02:38.869> of<01:02:39.170> why<01:02:39.740> not<01:02:40.190> next<01:02:40.820> I 01:02:40.960 --> 01:02:40.970 align:start position:0% coating so this Pierce of why not next I 01:02:40.970 --> 01:02:42.880 align:start position:0% coating so this Pierce of why not next I mean<01:02:41.210> there's<01:02:41.480> there<01:02:41.780> I'm<01:02:42.109> not<01:02:42.290> familiar<01:02:42.500> with 01:02:42.880 --> 01:02:42.890 align:start position:0% mean there's there I'm not familiar with 01:02:42.890 --> 01:02:46.089 align:start position:0% mean there's there I'm not familiar with the<01:02:43.070> verification<01:02:43.630> technology<01:02:44.630> so<01:02:45.170> is<01:02:45.830> there 01:02:46.089 --> 01:02:46.099 align:start position:0% the verification technology so is there 01:02:46.099 --> 01:02:48.310 align:start position:0% the verification technology so is there a<01:02:46.130> technical<01:02:46.670> reason<01:02:46.880> why<01:02:47.359> next<01:02:48.020> is<01:02:48.170> more 01:02:48.310 --> 01:02:48.320 align:start position:0% a technical reason why next is more 01:02:48.320 --> 01:02:50.290 align:start position:0% a technical reason why next is more difficult<01:02:48.560> than<01:02:48.830> previous<01:02:49.339> so<01:02:50.000> for 01:02:50.290 --> 01:02:50.300 align:start position:0% difficult than previous so for 01:02:50.300 --> 01:02:54.339 align:start position:0% difficult than previous so for modifications<01:02:51.020> its<01:02:51.380> item<01:02:52.130> only<01:02:53.050> you<01:02:54.050> need<01:02:54.200> to 01:02:54.339 --> 01:02:54.349 align:start position:0% modifications its item only you need to 01:02:54.349 --> 01:02:55.970 align:start position:0% modifications its item only you need to do<01:02:54.770> some<01:02:54.980> gymnastics 01:02:55.970 --> 01:02:55.980 align:start position:0% do some gymnastics 01:02:55.980 --> 01:02:57.980 align:start position:0% do some gymnastics okay<01:02:56.339> and<01:02:56.579> when<01:02:56.820> you<01:02:56.849> are<01:02:57.089> eventually<01:02:57.420> becomes 01:02:57.980 --> 01:02:57.990 align:start position:0% okay and when you are eventually becomes 01:02:57.990 --> 01:02:59.680 align:start position:0% okay and when you are eventually becomes more<01:02:58.260> difficult<01:02:58.440> way<01:02:58.950> more<01:02:59.190> beautiful 01:02:59.680 --> 01:02:59.690 align:start position:0% more difficult way more beautiful 01:02:59.690 --> 01:03:03.200 align:start position:0% more difficult way more beautiful because<01:03:01.220> once<01:03:02.220> you<01:03:02.490> always<01:03:02.609> look<01:03:02.940> by<01:03:03.180> that 01:03:03.200 --> 01:03:03.210 align:start position:0% because once you always look by that 01:03:03.210 --> 01:03:06.079 align:start position:0% because once you always look by that number<01:03:03.510> of<01:03:03.750> steps<01:03:03.990> in<01:03:04.170> the<01:03:04.260> past<01:03:04.640> because<01:03:05.640> in 01:03:06.079 --> 01:03:06.089 align:start position:0% number of steps in the past because in 01:03:06.089 --> 01:03:08.450 align:start position:0% number of steps in the past because in the<01:03:06.300> past<01:03:06.450> time<01:03:06.720> is<01:03:06.869> limited<01:03:07.079> is<01:03:07.440> bound<01:03:07.680> but<01:03:08.310> in 01:03:08.450 --> 01:03:08.460 align:start position:0% the past time is limited is bound but in 01:03:08.460 --> 01:03:10.190 align:start position:0% the past time is limited is bound but in the<01:03:08.579> future<01:03:08.760> its<01:03:09.000> empowerment<01:03:09.570> when<01:03:10.020> you<01:03:10.109> are 01:03:10.190 --> 01:03:10.200 align:start position:0% the future its empowerment when you are 01:03:10.200 --> 01:03:12.740 align:start position:0% the future its empowerment when you are eventually<01:03:10.589> things<01:03:11.070> become<01:03:11.550> ready<01:03:11.820> of<01:03:12.450> their 01:03:12.740 --> 01:03:12.750 align:start position:0% eventually things become ready of their 01:03:12.750 --> 01:03:24.710 align:start position:0% eventually things become ready of their very<01:03:12.990> infant<01:03:16.609> good<01:03:22.369> okay<01:03:23.369> so<01:03:23.700> maybe<01:03:24.210> we'll 01:03:24.710 --> 01:03:24.720 align:start position:0% very infant good okay so maybe we'll 01:03:24.720 --> 01:03:28.579 align:start position:0% very infant good okay so maybe we'll just<01:03:24.750> go<01:03:25.260> quickly<01:03:25.589> order<01:03:25.980> exercises<01:03:26.640> so<01:03:27.630> now 01:03:28.579 --> 01:03:28.589 align:start position:0% just go quickly order exercises so now 01:03:28.589 --> 01:03:30.880 align:start position:0% just go quickly order exercises so now it's<01:03:28.770> time<01:03:28.950> to<01:03:29.010> formalize<01:03:29.609> what<01:03:29.970> we<01:03:30.420> need<01:03:30.570> and 01:03:30.880 --> 01:03:30.890 align:start position:0% it's time to formalize what we need and 01:03:30.890 --> 01:03:35.030 align:start position:0% it's time to formalize what we need and just<01:03:31.890> to<01:03:32.040> solve<01:03:32.250> ours<01:03:32.730> our<01:03:32.970> verifier<01:03:33.859> we<01:03:34.859> have 01:03:35.030 --> 01:03:35.040 align:start position:0% just to solve ours our verifier we have 01:03:35.040 --> 01:03:39.170 align:start position:0% just to solve ours our verifier we have two<01:03:36.410> servers<01:03:37.410> in<01:03:37.859> which<01:03:38.070> you<01:03:38.190> can<01:03:38.400> remember<01:03:38.760> X 01:03:39.170 --> 01:03:39.180 align:start position:0% two servers in which you can remember X 01:03:39.180 --> 01:03:42.319 align:start position:0% two servers in which you can remember X there<01:03:39.450> is<01:03:40.109> an<01:03:40.290> interface<01:03:40.800> let's<01:03:41.430> say<01:03:41.640> this 01:03:42.319 --> 01:03:42.329 align:start position:0% there is an interface let's say this 01:03:42.329 --> 01:03:45.500 align:start position:0% there is an interface let's say this part<01:03:43.140> of<01:03:43.290> the<01:03:43.440> room<01:03:43.589> uses<01:03:43.950> but<01:03:44.550> X<01:03:44.730> 1<01:03:44.880> and<01:03:45.300> the 01:03:45.500 --> 01:03:45.510 align:start position:0% part of the room uses but X 1 and the 01:03:45.510 --> 01:03:48.109 align:start position:0% part of the room uses but X 1 and the other<01:03:45.630> part<01:03:45.990> of<01:03:46.140> the<01:03:46.290> room<01:03:46.349> is<01:03:46.680> very<01:03:46.829> soon<01:03:47.400> as 01:03:48.109 --> 01:03:48.119 align:start position:0% other part of the room is very soon as 01:03:48.119 --> 01:03:51.339 align:start position:0% other part of the room is very soon as can<01:03:48.450> we<01:03:48.540> do<01:03:48.630> it<01:03:48.720> like<01:03:48.869> this<01:03:49.050> because<01:03:50.270> services 01:03:51.339 --> 01:03:51.349 align:start position:0% can we do it like this because services 01:03:51.349 --> 01:03:56.870 align:start position:0% can we do it like this because services power<01:03:52.349> forwards<01:03:53.000> notifications 01:03:56.870 --> 01:03:56.880 align:start position:0% 01:03:56.880 --> 01:04:09.170 align:start position:0% yes<01:03:58.970> okay<01:03:59.970> ever<01:04:00.089> will<01:04:00.359> the<01:04:00.390> books 01:04:09.170 --> 01:04:09.180 align:start position:0% 01:04:09.180 --> 01:04:15.880 align:start position:0% [Music] 01:04:15.880 --> 01:04:15.890 align:start position:0% 01:04:15.890 --> 01:04:18.770 align:start position:0% sorry<01:04:16.890> I've<01:04:17.190> just<01:04:17.250> can't<01:04:17.670> miss<01:04:18.359> vericsson 01:04:18.770 --> 01:04:18.780 align:start position:0% sorry I've just can't miss vericsson 01:04:18.780 --> 01:04:20.450 align:start position:0% sorry I've just can't miss vericsson online<01:04:19.140> too<01:04:19.349> long<01:04:19.530> here's<01:04:19.859> that<01:04:20.070> down<01:04:20.310> with 01:04:20.450 --> 01:04:20.460 align:start position:0% online too long here's that down with 01:04:20.460 --> 01:04:23.540 align:start position:0% online too long here's that down with the<01:04:21.330> Maltese<01:04:21.750> don't<01:04:21.960> like<01:04:22.109> a<01:04:23.400> up 01:04:23.540 --> 01:04:23.550 align:start position:0% the Maltese don't like a up 01:04:23.550 --> 01:04:29.960 align:start position:0% the Maltese don't like a up associate<01:04:24.060> in<01:04:24.180> the<01:04:24.210> future<01:04:28.609> don't<01:04:29.609> get<01:04:29.760> your 01:04:29.960 --> 01:04:29.970 align:start position:0% associate in the future don't get your 01:04:29.970 --> 01:04:37.609 align:start position:0% associate in the future don't get your servers<01:04:34.130> and<01:04:35.630> for<01:04:36.630> verax<01:04:36.960> index<01:04:37.349> you<01:04:37.589> can 01:04:37.609 --> 01:04:37.619 align:start position:0% servers and for verax index you can 01:04:37.619 --> 01:04:42.510 align:start position:0% servers and for verax index you can treat<01:04:38.280> these<01:04:38.490> things<01:04:38.810> and<01:04:39.810> check<01:04:40.050> out 01:04:42.510 --> 01:04:42.520 align:start position:0% 01:04:42.520 --> 01:04:45.680 align:start position:0% [Music] 01:04:45.680 --> 01:04:45.690 align:start position:0% [Music] 01:04:45.690 --> 01:04:56.380 align:start position:0% [Music] yes 01:04:56.380 --> 01:04:56.390 align:start position:0% 01:04:56.390 --> 01:05:00.590 align:start position:0% [Music] 01:05:00.590 --> 01:05:00.600 align:start position:0% 01:05:00.600 --> 01:05:04.130 align:start position:0% okay<01:05:01.500> so<01:05:01.770> so<01:05:02.040> if<01:05:02.610> you<01:05:02.790> open<01:05:03.030> if<01:05:03.480> you<01:05:03.660> open<01:05:04.050> the 01:05:04.130 --> 01:05:04.140 align:start position:0% okay so so if you open if you open the 01:05:04.140 --> 01:05:05.960 align:start position:0% okay so so if you open if you open the links<01:05:04.380> you<01:05:04.590> see<01:05:04.800> this<01:05:04.980> this<01:05:05.640> kind<01:05:05.910> of 01:05:05.960 --> 01:05:05.970 align:start position:0% links you see this this kind of 01:05:05.970 --> 01:05:11.330 align:start position:0% links you see this this kind of interface<01:05:06.750> products<01:05:09.320> on<01:05:10.320> the<01:05:10.560> Left<01:05:10.740> what<01:05:11.190> - 01:05:11.330 --> 01:05:11.340 align:start position:0% interface products on the Left what - 01:05:11.340 --> 01:05:14.000 align:start position:0% interface products on the Left what - that<01:05:11.520> is<01:05:11.730> the<01:05:11.970> list<01:05:12.590> conflicts<01:05:13.590> posit 01:05:14.000 --> 01:05:14.010 align:start position:0% that is the list conflicts posit 01:05:14.010 --> 01:05:17.090 align:start position:0% that is the list conflicts posit specifications<01:05:14.940> so<01:05:15.660> we<01:05:16.110> pre-loaded<01:05:16.740> Maddux 01:05:17.090 --> 01:05:17.100 align:start position:0% specifications so we pre-loaded Maddux 01:05:17.100 --> 01:05:20.300 align:start position:0% specifications so we pre-loaded Maddux with<01:05:17.250> about<01:05:17.610> context<01:05:18.210> and<01:05:19.070> currently<01:05:20.070> with 01:05:20.300 --> 01:05:20.310 align:start position:0% with about context and currently with 01:05:20.310 --> 01:05:23.780 align:start position:0% with about context and currently with office<01:05:20.730> on<01:05:21.120> the<01:05:21.600> ear<01:05:21.870> see<01:05:22.110> plenty<01:05:22.530> when<01:05:23.430> you 01:05:23.780 --> 01:05:23.790 align:start position:0% office on the ear see plenty when you 01:05:23.790 --> 01:05:26.870 align:start position:0% office on the ear see plenty when you see<01:05:24.120> sorry<01:05:24.870> and<01:05:25.140> council<01:05:25.680> right<01:05:26.070> so<01:05:26.310> we<01:05:26.670> have 01:05:26.870 --> 01:05:26.880 align:start position:0% see sorry and council right so we have 01:05:26.880 --> 01:05:33.140 align:start position:0% see sorry and council right so we have two<01:05:27.210> contexts<01:05:28.020> which<01:05:28.200> we<01:05:28.680> focus<01:05:29.010> on<01:05:29.720> and<01:05:32.150> the 01:05:33.140 --> 01:05:33.150 align:start position:0% two contexts which we focus on and the 01:05:33.150 --> 01:05:36.290 align:start position:0% two contexts which we focus on and the latest<01:05:34.220> service<01:05:35.220> which<01:05:35.430> solution<01:05:35.940> are<01:05:36.150> the 01:05:36.290 --> 01:05:36.300 align:start position:0% latest service which solution are the 01:05:36.300 --> 01:05:39.350 align:start position:0% latest service which solution are the solutions<01:05:36.720> to<01:05:36.870> those<01:05:37.020> exercises<01:05:37.710> right<01:05:38.490> we 01:05:39.350 --> 01:05:39.360 align:start position:0% solutions to those exercises right we 01:05:39.360 --> 01:05:41.510 align:start position:0% solutions to those exercises right we have<01:05:39.570> three<01:05:39.810> extra<01:05:40.170> exercises<01:05:40.830> which<01:05:41.220> you<01:05:41.250> can 01:05:41.510 --> 01:05:41.520 align:start position:0% have three extra exercises which you can 01:05:41.520 --> 01:05:43.880 align:start position:0% have three extra exercises which you can do<01:05:41.700> but<01:05:41.940> maybe<01:05:42.120> not<01:05:42.960> maybe<01:05:43.170> that<01:05:43.320> would<01:05:43.620> be<01:05:43.650> no 01:05:43.880 --> 01:05:43.890 align:start position:0% do but maybe not maybe that would be no 01:05:43.890 --> 01:05:46.640 align:start position:0% do but maybe not maybe that would be no time<01:05:44.190> for<01:05:44.550> this<01:05:44.700> day<01:05:45.090> now<01:05:45.840> they<01:05:46.290> have<01:05:46.500> no 01:05:46.640 --> 01:05:46.650 align:start position:0% time for this day now they have no 01:05:46.650 --> 01:05:49.810 align:start position:0% time for this day now they have no solutions<01:05:47.130> you<01:05:47.490> need<01:05:47.790> to 01:05:49.810 --> 01:05:49.820 align:start position:0% solutions you need to 01:05:49.820 --> 01:05:58.280 align:start position:0% solutions you need to [Music] 01:05:58.280 --> 01:05:58.290 align:start position:0% 01:05:58.290 --> 01:06:00.500 align:start position:0% what<01:05:58.859> was<01:05:59.099> I'm<01:05:59.339> wondering<01:05:59.760> how<01:06:00.210> do<01:06:00.270> you<01:06:00.359> do 01:06:00.500 --> 01:06:00.510 align:start position:0% what was I'm wondering how do you do 01:06:00.510 --> 01:06:02.030 align:start position:0% what was I'm wondering how do you do these<01:06:00.690> state<01:06:00.990> credit<01:06:01.200> society<01:06:01.859> the<01:06:01.980> state 01:06:02.030 --> 01:06:02.040 align:start position:0% these state credit society the state 01:06:02.040 --> 01:06:05.569 align:start position:0% these state credit society the state pretty<01:06:02.430> good<01:06:02.579> success<01:06:03.230> define<01:06:04.230> one<01:06:04.500> as<01:06:04.650> a<01:06:04.680> user 01:06:05.569 --> 01:06:05.579 align:start position:0% pretty good success define one as a user 01:06:05.579 --> 01:06:18.910 align:start position:0% pretty good success define one as a user for<01:06:05.849> a<01:06:05.880> sense<01:06:06.770> okay<01:06:07.770> my<01:06:07.980> PC<01:06:08.190> babies<01:06:08.609> maybe<01:06:09.240> yes 01:06:18.910 --> 01:06:18.920 align:start position:0% 01:06:18.920 --> 01:06:22.280 align:start position:0% so<01:06:19.920> you<01:06:20.670> give<01:06:20.849> police<01:06:21.089> the<01:06:21.150> formulas<01:06:21.780> make 01:06:22.280 --> 01:06:22.290 align:start position:0% so you give police the formulas make 01:06:22.290 --> 01:06:24.230 align:start position:0% so you give police the formulas make them<01:06:22.470> we'll<01:06:22.619> talk<01:06:23.220> about<01:06:23.369> those<01:06:23.670> remaining 01:06:24.230 --> 01:06:24.240 align:start position:0% them we'll talk about those remaining 01:06:24.240 --> 01:06:26.150 align:start position:0% them we'll talk about those remaining focus<01:06:24.720> but<01:06:24.930> what's<01:06:25.079> important<01:06:25.560> is<01:06:25.740> the<01:06:25.920> first 01:06:26.150 --> 01:06:26.160 align:start position:0% focus but what's important is the first 01:06:26.160 --> 01:06:26.660 align:start position:0% focus but what's important is the first for<01:06:26.369> me 01:06:26.660 --> 01:06:26.670 align:start position:0% for me 01:06:26.670 --> 01:06:27.980 align:start position:0% for me so<01:06:26.820> the<01:06:27.030> first<01:06:27.240> of<01:06:27.329> all<01:06:27.390> really<01:06:27.720> is<01:06:27.780> your 01:06:27.980 --> 01:06:27.990 align:start position:0% so the first of all really is your 01:06:27.990 --> 01:06:31.730 align:start position:0% so the first of all really is your problem<01:06:28.880> and<01:06:29.880> it<01:06:30.180> has<01:06:30.210> this<01:06:30.510> form<01:06:30.750> always<01:06:31.349> and 01:06:31.730 --> 01:06:31.740 align:start position:0% problem and it has this form always and 01:06:31.740 --> 01:06:34.520 align:start position:0% problem and it has this form always and then<01:06:32.070> some<01:06:32.310> point<01:06:32.599> so<01:06:33.599> whatever<01:06:33.869> your<01:06:34.020> specify 01:06:34.520 --> 01:06:34.530 align:start position:0% then some point so whatever your specify 01:06:34.530 --> 01:06:41.240 align:start position:0% then some point so whatever your specify something<01:06:35.390> and<01:06:36.390> then<01:06:36.599> you<01:06:36.780> have<01:06:37.020> a<01:06:40.250> paper 01:06:41.240 --> 01:06:41.250 align:start position:0% something and then you have a paper 01:06:41.250 --> 01:06:43.730 align:start position:0% something and then you have a paper which<01:06:41.550> gives<01:06:41.820> you<01:06:41.940> more<01:06:42.480> details<01:06:43.140> the<01:06:43.320> seasons 01:06:43.730 --> 01:06:43.740 align:start position:0% which gives you more details the seasons 01:06:43.740 --> 01:06:47.510 align:start position:0% which gives you more details the seasons and<01:06:44.430> for<01:06:45.500> example<01:06:46.500> you<01:06:46.770> can<01:06:46.950> refer<01:06:47.339> the 01:06:47.510 --> 01:06:47.520 align:start position:0% and for example you can refer the 01:06:47.520 --> 01:06:50.900 align:start position:0% and for example you can refer the contact<01:06:47.970> is<01:06:48.180> using<01:06:48.900> computers<01:06:49.550> its<01:06:50.550> we<01:06:50.760> can 01:06:50.900 --> 01:06:50.910 align:start position:0% contact is using computers its we can 01:06:50.910 --> 01:06:53.750 align:start position:0% contact is using computers its we can equal<01:06:51.180> to<01:06:51.329> the<01:06:51.420> context<01:06:51.869> and<01:06:52.020> this<01:06:52.260> way<01:06:52.500> I<01:06:52.760> for 01:06:53.750 --> 01:06:53.760 align:start position:0% equal to the context and this way I for 01:06:53.760 --> 01:06:57.410 align:start position:0% equal to the context and this way I for girls<01:06:53.970> family<01:06:54.480> simply<01:06:54.960> sneakers<01:06:55.440> right 01:06:57.410 --> 01:06:57.420 align:start position:0% girls family simply sneakers right 01:06:57.420 --> 01:07:01.130 align:start position:0% girls family simply sneakers right also<01:06:58.109> you<01:06:58.170> can<01:06:58.410> refer<01:06:58.710> to<01:06:58.740> my<01:06:59.700> seat<01:06:59.910> sensor<01:07:00.359> you 01:07:01.130 --> 01:07:01.140 align:start position:0% also you can refer to my seat sensor you 01:07:01.140 --> 01:07:13.889 align:start position:0% also you can refer to my seat sensor you can<01:07:01.200> refer<01:07:01.589> to<01:07:01.770> the<01:07:01.859> current<01:07:02.010> time<01:07:02.369> and<01:07:02.579> time 01:07:13.889 --> 01:07:13.899 align:start position:0% 01:07:13.899 --> 01:07:23.579 align:start position:0% yes<01:07:14.899> I<01:07:15.079> guess<01:07:15.259> I<01:07:18.069> stay<01:07:19.069> pretty<01:07:19.099> good<01:07:21.519> spacing<01:07:22.519> I 01:07:23.579 --> 01:07:23.589 align:start position:0% yes I guess I stay pretty good spacing I 01:07:23.589 --> 01:07:36.549 align:start position:0% yes I guess I stay pretty good spacing I it's<01:07:24.589> like<01:07:24.769> they<01:07:25.399> will<01:07:25.579> try<01:07:35.199> and<01:07:36.199> you<01:07:36.319> had<01:07:36.469> an 01:07:36.549 --> 01:07:36.559 align:start position:0% it's like they will try and you had an 01:07:36.559 --> 01:07:38.619 align:start position:0% it's like they will try and you had an example<01:07:36.739> of<01:07:37.039> like<01:07:37.189> success<01:07:37.639> or<01:07:37.909> refund<01:07:38.359> that's 01:07:38.619 --> 01:07:38.629 align:start position:0% example of like success or refund that's 01:07:38.629 --> 01:07:40.419 align:start position:0% example of like success or refund that's a<01:07:38.689> big<01:07:38.869> prep<01:07:39.109> it's<01:07:39.319> upon<01:07:39.619> the<01:07:39.799> success<01:07:40.219> fee 01:07:40.419 --> 01:07:40.429 align:start position:0% a big prep it's upon the success fee 01:07:40.429 --> 01:07:41.949 align:start position:0% a big prep it's upon the success fee around<01:07:40.759> the<01:07:40.969> region<01:07:41.149> on<01:07:41.329> the<01:07:41.449> state<01:07:41.689> for 01:07:41.949 --> 01:07:41.959 align:start position:0% around the region on the state for 01:07:41.959 --> 01:07:42.909 align:start position:0% around the region on the state for something<01:07:42.319> done 01:07:42.909 --> 01:07:42.919 align:start position:0% something done 01:07:42.919 --> 01:08:03.069 align:start position:0% something done oh<01:07:44.559> yes 01:08:03.069 --> 01:08:03.079 align:start position:0% 01:08:03.079 --> 01:08:05.210 align:start position:0% okay<01:08:04.079> let<01:08:04.260> me<01:08:04.380> just<01:08:04.589> give<01:08:04.770> you<01:08:04.800> a<01:08:04.859> short 01:08:05.210 --> 01:08:05.220 align:start position:0% okay let me just give you a short 01:08:05.220 --> 01:08:07.609 align:start position:0% okay let me just give you a short demonstration<01:08:05.670> about<01:08:06.119> the<01:08:06.359> first<01:08:07.079> property<01:08:07.500> I 01:08:07.609 --> 01:08:07.619 align:start position:0% demonstration about the first property I 01:08:07.619 --> 01:08:09.680 align:start position:0% demonstration about the first property I taught<01:08:07.950> us<01:08:08.130> my<01:08:08.430> always<01:08:08.970> equals<01:08:09.420> the<01:08:09.540> same 01:08:09.680 --> 01:08:09.690 align:start position:0% taught us my always equals the same 01:08:09.690 --> 01:08:19.429 align:start position:0% taught us my always equals the same imbalances<01:08:10.320> so 01:08:19.429 --> 01:08:19.439 align:start position:0% 01:08:19.439 --> 01:08:22.900 align:start position:0% [Music] 01:08:22.900 --> 01:08:22.910 align:start position:0% 01:08:22.910 --> 01:08:25.760 align:start position:0% okay<01:08:23.910> so<01:08:23.970> it's<01:08:24.690> better<01:08:24.870> we<01:08:25.109> write<01:08:25.319> the<01:08:25.560> first 01:08:25.760 --> 01:08:25.770 align:start position:0% okay so it's better we write the first 01:08:25.770 --> 01:08:29.270 align:start position:0% okay so it's better we write the first property<01:08:26.130> right<01:08:26.430> this<01:08:27.060> one<01:08:27.270> is<01:08:27.390> simple<01:08:28.280> same 01:08:29.270 --> 01:08:29.280 align:start position:0% property right this one is simple same 01:08:29.280 --> 01:08:34.530 align:start position:0% property right this one is simple same always 01:08:34.530 --> 01:08:34.540 align:start position:0% 01:08:34.540 --> 01:08:40.539 align:start position:0% okay 01:08:40.539 --> 01:08:40.549 align:start position:0% 01:08:40.549 --> 01:08:42.669 align:start position:0% so<01:08:41.119> he's<01:08:41.269> the<01:08:41.389> case<01:08:41.569> that<01:08:41.749> the<01:08:41.869> civil<01:08:42.170> bosses 01:08:42.669 --> 01:08:42.679 align:start position:0% so he's the case that the civil bosses 01:08:42.679 --> 01:09:00.489 align:start position:0% so he's the case that the civil bosses equals<01:08:44.170> the<01:08:48.699> whistleblowers<01:08:49.699> and<01:08:59.499> but 01:09:00.489 --> 01:09:00.499 align:start position:0% equals the whistleblowers and but 01:09:00.499 --> 01:09:02.919 align:start position:0% equals the whistleblowers and but education<01:09:01.009> thanks<01:09:01.219> subtitle<01:09:01.880> can<01:09:02.569> see<01:09:02.749> that 01:09:02.919 --> 01:09:02.929 align:start position:0% education thanks subtitle can see that 01:09:02.929 --> 01:09:23.799 align:start position:0% education thanks subtitle can see that the<01:09:03.019> property<01:09:21.339> so<01:09:22.339> you<01:09:22.400> need<01:09:22.730> to<01:09:22.880> verification 01:09:23.799 --> 01:09:23.809 align:start position:0% the property so you need to verification 01:09:23.809 --> 01:09:26.470 align:start position:0% the property so you need to verification takes<01:09:23.960> some<01:09:24.469> time<01:09:24.710> so<01:09:25.219> if<01:09:25.339> you<01:09:25.369> know<01:09:25.549> it's<01:09:26.179> not 01:09:26.470 --> 01:09:26.480 align:start position:0% takes some time so if you know it's not 01:09:26.480 --> 01:09:30.069 align:start position:0% takes some time so if you know it's not have<01:09:27.409> to<01:09:27.559> say<01:09:27.739> a<01:09:28.210> two-way<01:09:29.210> get<01:09:29.539> immediately 01:09:30.069 --> 01:09:30.079 align:start position:0% have to say a two-way get immediately 01:09:30.079 --> 01:10:34.520 align:start position:0% have to say a two-way get immediately packages<01:09:30.799> education 01:10:34.520 --> 01:10:34.530 align:start position:0% 01:10:34.530 --> 01:10:56.330 align:start position:0% like<01:10:35.530> when<01:10:35.829> you<01:10:35.919> have<01:10:36.099> delegated<01:10:36.489> its 01:10:56.330 --> 01:10:56.340 align:start position:0% 01:10:56.340 --> 01:10:58.400 align:start position:0% you