WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.310 align:start position:0% [Music] 00:00:16.310 --> 00:00:16.320 align:start position:0% 00:00:16.320 --> 00:00:18.410 align:start position:0% this<00:00:16.920> will<00:00:17.100> be<00:00:17.340> a<00:00:17.699> talk<00:00:17.940> about 00:00:18.410 --> 00:00:18.420 align:start position:0% this will be a talk about 00:00:18.420 --> 00:00:20.630 align:start position:0% this will be a talk about compositionality 00:00:20.630 --> 00:00:20.640 align:start position:0% compositionality 00:00:20.640 --> 00:00:23.929 align:start position:0% compositionality uh<00:00:21.539> it's<00:00:22.020> probably<00:00:22.199> a<00:00:22.439> word<00:00:22.619> that<00:00:23.039> not<00:00:23.520> all<00:00:23.820> of 00:00:23.929 --> 00:00:23.939 align:start position:0% uh it's probably a word that not all of 00:00:23.939 --> 00:00:25.130 align:start position:0% uh it's probably a word that not all of you<00:00:24.060> know 00:00:25.130 --> 00:00:25.140 align:start position:0% you know 00:00:25.140 --> 00:00:27.710 align:start position:0% you know and<00:00:25.619> I'll<00:00:25.920> try<00:00:26.100> to<00:00:26.279> explain<00:00:26.519> what<00:00:27.359> this<00:00:27.599> is 00:00:27.710 --> 00:00:27.720 align:start position:0% and I'll try to explain what this is 00:00:27.720 --> 00:00:30.410 align:start position:0% and I'll try to explain what this is about<00:00:27.900> in<00:00:28.800> the<00:00:28.980> course<00:00:29.099> of<00:00:29.279> this<00:00:29.460> Workshop 00:00:30.410 --> 00:00:30.420 align:start position:0% about in the course of this Workshop 00:00:30.420 --> 00:00:34.970 align:start position:0% about in the course of this Workshop uh<00:00:31.380> in<00:00:31.859> the<00:00:32.220> last<00:00:32.660> months<00:00:33.660> probably<00:00:33.960> a<00:00:34.680> year<00:00:34.860> or 00:00:34.970 --> 00:00:34.980 align:start position:0% uh in the last months probably a year or 00:00:34.980 --> 00:00:38.350 align:start position:0% uh in the last months probably a year or so<00:00:35.160> we've<00:00:35.640> been<00:00:36.260> hearing<00:00:37.260> a<00:00:37.559> lot<00:00:37.680> about 00:00:38.350 --> 00:00:38.360 align:start position:0% so we've been hearing a lot about 00:00:38.360 --> 00:00:41.209 align:start position:0% so we've been hearing a lot about composable<00:00:39.360> things<00:00:39.660> composable<00:00:40.440> blockchains 00:00:41.209 --> 00:00:41.219 align:start position:0% composable things composable blockchains 00:00:41.219 --> 00:00:43.270 align:start position:0% composable things composable blockchains composable<00:00:41.820> service 00:00:43.270 --> 00:00:43.280 align:start position:0% composable service 00:00:43.280 --> 00:00:47.030 align:start position:0% composable service compositionality<00:00:44.280> is<00:00:44.820> basically<00:00:45.379> just<00:00:46.379> a 00:00:47.030 --> 00:00:47.040 align:start position:0% compositionality is basically just a 00:00:47.040 --> 00:00:50.389 align:start position:0% compositionality is basically just a mathematical<00:00:48.200> Structure<00:00:49.200> Theory<00:00:49.680> that<00:00:50.100> tells 00:00:50.389 --> 00:00:50.399 align:start position:0% mathematical Structure Theory that tells 00:00:50.399 --> 00:00:52.790 align:start position:0% mathematical Structure Theory that tells you<00:00:50.520> how<00:00:50.879> to<00:00:51.000> do<00:00:51.180> that<00:00:51.420> in<00:00:52.020> the<00:00:52.140> most<00:00:52.320> principle 00:00:52.790 --> 00:00:52.800 align:start position:0% you how to do that in the most principle 00:00:52.800 --> 00:00:54.830 align:start position:0% you how to do that in the most principle way<00:00:53.100> possible 00:00:54.830 --> 00:00:54.840 align:start position:0% way possible 00:00:54.840 --> 00:00:56.270 align:start position:0% way possible uh 00:00:56.270 --> 00:00:56.280 align:start position:0% uh 00:00:56.280 --> 00:00:59.450 align:start position:0% uh I'll<00:00:57.120> start<00:00:57.420> and<00:00:58.020> if<00:00:58.379> you<00:00:58.559> have<00:00:58.739> any<00:00:59.100> question 00:00:59.450 --> 00:00:59.460 align:start position:0% I'll start and if you have any question 00:00:59.460 --> 00:01:01.729 align:start position:0% I'll start and if you have any question just<00:01:00.180> feel<00:01:00.480> free<00:01:00.660> to<00:01:00.840> like<00:01:01.079> raise<00:01:01.320> your<00:01:01.559> hand 00:01:01.729 --> 00:01:01.739 align:start position:0% just feel free to like raise your hand 00:01:01.739 --> 00:01:05.030 align:start position:0% just feel free to like raise your hand and<00:01:02.100> interrupt<00:01:02.579> me<00:01:02.760> and<00:01:03.719> I'll<00:01:04.019> try<00:01:04.260> to<00:01:04.440> answer 00:01:05.030 --> 00:01:05.040 align:start position:0% and interrupt me and I'll try to answer 00:01:05.040 --> 00:01:07.370 align:start position:0% and interrupt me and I'll try to answer and<00:01:05.640> or<00:01:05.939> clarify 00:01:07.370 --> 00:01:07.380 align:start position:0% and or clarify 00:01:07.380 --> 00:01:11.030 align:start position:0% and or clarify okay<00:01:07.979> so<00:01:08.640> first<00:01:09.240> of<00:01:09.420> all<00:01:09.540> to<00:01:10.080> introduce<00:01:10.799> the 00:01:11.030 --> 00:01:11.040 align:start position:0% okay so first of all to introduce the 00:01:11.040 --> 00:01:13.310 align:start position:0% okay so first of all to introduce the concept<00:01:11.280> of<00:01:11.520> compositionality<00:01:12.420> we<00:01:13.080> need<00:01:13.200> to 00:01:13.310 --> 00:01:13.320 align:start position:0% concept of compositionality we need to 00:01:13.320 --> 00:01:15.310 align:start position:0% concept of compositionality we need to introduce<00:01:13.740> some<00:01:14.159> basic<00:01:14.520> building<00:01:14.760> blocks 00:01:15.310 --> 00:01:15.320 align:start position:0% introduce some basic building blocks 00:01:15.320 --> 00:01:19.730 align:start position:0% introduce some basic building blocks that<00:01:16.320> are<00:01:16.500> systems<00:01:17.159> and<00:01:17.520> processes 00:01:19.730 --> 00:01:19.740 align:start position:0% that are systems and processes 00:01:19.740 --> 00:01:23.390 align:start position:0% that are systems and processes so<00:01:21.020> compositionality<00:01:22.020> is<00:01:22.680> basically<00:01:23.100> the 00:01:23.390 --> 00:01:23.400 align:start position:0% so compositionality is basically the 00:01:23.400 --> 00:01:27.170 align:start position:0% so compositionality is basically the study<00:01:23.880> of<00:01:24.780> how<00:01:25.020> systems<00:01:25.740> compose<00:01:26.280> to<00:01:26.939> give 00:01:27.170 --> 00:01:27.180 align:start position:0% study of how systems compose to give 00:01:27.180 --> 00:01:30.109 align:start position:0% study of how systems compose to give life<00:01:27.479> to<00:01:27.960> more<00:01:28.320> complex<00:01:28.740> systems 00:01:30.109 --> 00:01:30.119 align:start position:0% life to more complex systems 00:01:30.119 --> 00:01:33.010 align:start position:0% life to more complex systems systems<00:01:30.900> are<00:01:31.259> basically<00:01:31.740> things<00:01:32.280> that<00:01:32.580> can<00:01:32.820> be 00:01:33.010 --> 00:01:33.020 align:start position:0% systems are basically things that can be 00:01:33.020 --> 00:01:35.929 align:start position:0% systems are basically things that can be transformed<00:01:34.040> enacted<00:01:35.040> upon 00:01:35.929 --> 00:01:35.939 align:start position:0% transformed enacted upon 00:01:35.939 --> 00:01:38.630 align:start position:0% transformed enacted upon and<00:01:36.600> processes<00:01:37.200> are<00:01:37.560> exactly<00:01:37.979> the<00:01:38.340> things 00:01:38.630 --> 00:01:38.640 align:start position:0% and processes are exactly the things 00:01:38.640 --> 00:01:43.330 align:start position:0% and processes are exactly the things that<00:01:39.240> act<00:01:39.540> on<00:01:40.020> systems<00:01:40.619> and<00:01:41.040> transform<00:01:41.579> them 00:01:43.330 --> 00:01:43.340 align:start position:0% that act on systems and transform them 00:01:43.340 --> 00:01:47.690 align:start position:0% that act on systems and transform them uh<00:01:44.340> a<00:01:45.000> very<00:01:45.439> interesting<00:01:46.439> Insight<00:01:47.040> from 00:01:47.690 --> 00:01:47.700 align:start position:0% uh a very interesting Insight from 00:01:47.700 --> 00:01:50.510 align:start position:0% uh a very interesting Insight from Modern<00:01:48.360> mathematics<00:01:49.200> the<00:01:49.680> mathematics 00:01:50.510 --> 00:01:50.520 align:start position:0% Modern mathematics the mathematics 00:01:50.520 --> 00:01:56.030 align:start position:0% Modern mathematics the mathematics developed<00:01:51.500> from<00:01:52.880> 1950<00:01:53.880> onwards<00:01:54.680> is<00:01:55.680> that 00:01:56.030 --> 00:01:56.040 align:start position:0% developed from 1950 onwards is that 00:01:56.040 --> 00:01:59.330 align:start position:0% developed from 1950 onwards is that often<00:01:56.640> is<00:01:57.240> way<00:01:57.540> more<00:01:57.720> fruitful<00:01:58.140> to 00:01:59.330 --> 00:01:59.340 align:start position:0% often is way more fruitful to 00:01:59.340 --> 00:02:03.649 align:start position:0% often is way more fruitful to understand<00:02:00.200> something<00:02:01.200> to<00:02:01.920> describe<00:02:02.579> it<00:02:02.759> by 00:02:03.649 --> 00:02:03.659 align:start position:0% understand something to describe it by 00:02:03.659 --> 00:02:06.469 align:start position:0% understand something to describe it by looking<00:02:03.899> at<00:02:04.200> how<00:02:04.560> the<00:02:05.040> thing<00:02:05.219> composes<00:02:06.119> and 00:02:06.469 --> 00:02:06.479 align:start position:0% looking at how the thing composes and 00:02:06.479 --> 00:02:08.930 align:start position:0% looking at how the thing composes and behaves<00:02:06.960> in<00:02:07.320> a<00:02:07.500> context<00:02:07.799> so<00:02:08.459> instead<00:02:08.819> of 00:02:08.930 --> 00:02:08.940 align:start position:0% behaves in a context so instead of 00:02:08.940 --> 00:02:11.449 align:start position:0% behaves in a context so instead of splitting<00:02:09.360> things<00:02:09.599> open<00:02:09.899> and<00:02:10.739> look<00:02:10.979> how<00:02:11.340> they 00:02:11.449 --> 00:02:11.459 align:start position:0% splitting things open and look how they 00:02:11.459 --> 00:02:14.690 align:start position:0% splitting things open and look how they look<00:02:11.700> on<00:02:12.000> the<00:02:12.180> inside<00:02:12.440> we<00:02:13.440> describe<00:02:14.099> them<00:02:14.280> by 00:02:14.690 --> 00:02:14.700 align:start position:0% look on the inside we describe them by 00:02:14.700 --> 00:02:16.430 align:start position:0% look on the inside we describe them by saying<00:02:15.000> how<00:02:15.300> they<00:02:15.480> behave 00:02:16.430 --> 00:02:16.440 align:start position:0% saying how they behave 00:02:16.440 --> 00:02:20.330 align:start position:0% saying how they behave and<00:02:16.980> how<00:02:17.220> they<00:02:17.400> interact 00:02:20.330 --> 00:02:20.340 align:start position:0% 00:02:20.340 --> 00:02:22.250 align:start position:0% um<00:02:20.459> okay<00:02:20.760> so<00:02:21.180> let's<00:02:21.599> start<00:02:21.780> with<00:02:21.959> something 00:02:22.250 --> 00:02:22.260 align:start position:0% um okay so let's start with something 00:02:22.260 --> 00:02:24.530 align:start position:0% um okay so let's start with something very<00:02:22.620> very<00:02:22.800> simple<00:02:23.099> I<00:02:23.580> will<00:02:23.760> use<00:02:24.000> a<00:02:24.300> lot<00:02:24.360> of 00:02:24.530 --> 00:02:24.540 align:start position:0% very very simple I will use a lot of 00:02:24.540 --> 00:02:26.930 align:start position:0% very very simple I will use a lot of pictures<00:02:24.780> in<00:02:25.560> this<00:02:26.040> talk<00:02:26.280> and<00:02:26.640> hopefully 00:02:26.930 --> 00:02:26.940 align:start position:0% pictures in this talk and hopefully 00:02:26.940 --> 00:02:29.089 align:start position:0% pictures in this talk and hopefully close<00:02:27.480> to<00:02:27.660> zero<00:02:28.020> mathematics 00:02:29.089 --> 00:02:29.099 align:start position:0% close to zero mathematics 00:02:29.099 --> 00:02:31.970 align:start position:0% close to zero mathematics uh<00:02:30.060> for<00:02:30.300> people<00:02:30.540> that<00:02:30.840> love<00:02:31.020> mathematics<00:02:31.680> I 00:02:31.970 --> 00:02:31.980 align:start position:0% uh for people that love mathematics I 00:02:31.980 --> 00:02:34.190 align:start position:0% uh for people that love mathematics I cannot<00:02:32.280> that<00:02:32.459> there<00:02:32.700> is<00:02:32.879> a<00:02:33.480> soundness<00:02:33.959> a 00:02:34.190 --> 00:02:34.200 align:start position:0% cannot that there is a soundness a 00:02:34.200 --> 00:02:35.750 align:start position:0% cannot that there is a soundness a completeness<00:02:34.680> theorem<00:02:35.099> that<00:02:35.340> says<00:02:35.640> that 00:02:35.750 --> 00:02:35.760 align:start position:0% completeness theorem that says that 00:02:35.760 --> 00:02:38.510 align:start position:0% completeness theorem that says that these<00:02:36.000> pictures<00:02:36.180> are<00:02:36.660> formal<00:02:37.140> which<00:02:37.739> means<00:02:38.099> by 00:02:38.510 --> 00:02:38.520 align:start position:0% these pictures are formal which means by 00:02:38.520 --> 00:02:39.770 align:start position:0% these pictures are formal which means by doing<00:02:38.700> pictures<00:02:38.940> we're<00:02:39.300> actually<00:02:39.540> doing 00:02:39.770 --> 00:02:39.780 align:start position:0% doing pictures we're actually doing 00:02:39.780 --> 00:02:43.610 align:start position:0% doing pictures we're actually doing mathematics<00:02:40.560> it's<00:02:41.280> just<00:02:41.580> easier<00:02:42.239> and<00:02:43.080> more 00:02:43.610 --> 00:02:43.620 align:start position:0% mathematics it's just easier and more 00:02:43.620 --> 00:02:46.490 align:start position:0% mathematics it's just easier and more beautiful<00:02:43.860> in<00:02:44.700> my<00:02:44.819> opinion<00:02:45.180> so<00:02:45.840> in<00:02:46.140> here<00:02:46.319> we 00:02:46.490 --> 00:02:46.500 align:start position:0% beautiful in my opinion so in here we 00:02:46.500 --> 00:02:48.770 align:start position:0% beautiful in my opinion so in here we have<00:02:46.680> a<00:02:46.860> very<00:02:47.040> simple<00:02:47.220> process<00:02:47.819> that<00:02:48.599> we 00:02:48.770 --> 00:02:48.780 align:start position:0% have a very simple process that we 00:02:48.780 --> 00:02:51.890 align:start position:0% have a very simple process that we depict<00:02:49.080> as<00:02:49.319> a<00:02:49.500> box<00:02:49.680> it<00:02:50.280> just<00:02:50.640> takes<00:02:51.000> a<00:02:51.660> number 00:02:51.890 --> 00:02:51.900 align:start position:0% depict as a box it just takes a number 00:02:51.900 --> 00:02:55.490 align:start position:0% depict as a box it just takes a number in<00:02:52.200> input<00:02:52.700> adds<00:02:53.700> one<00:02:53.819> and<00:02:54.239> spits<00:02:54.720> a<00:02:54.780> number<00:02:54.959> in 00:02:55.490 --> 00:02:55.500 align:start position:0% in input adds one and spits a number in 00:02:55.500 --> 00:02:56.869 align:start position:0% in input adds one and spits a number in as<00:02:55.680> output 00:02:56.869 --> 00:02:56.879 align:start position:0% as output 00:02:56.879 --> 00:03:00.170 align:start position:0% as output I<00:02:57.420> mean<00:02:57.599> for<00:02:58.080> I<00:02:58.500> guess<00:02:58.620> everyone<00:02:59.280> acquainted 00:03:00.170 --> 00:03:00.180 align:start position:0% I mean for I guess everyone acquainted 00:03:00.180 --> 00:03:02.750 align:start position:0% I mean for I guess everyone acquainted to<00:03:00.360> with<00:03:00.720> programming<00:03:01.260> that's<00:03:01.560> just<00:03:01.800> like<00:03:02.040> man 00:03:02.750 --> 00:03:02.760 align:start position:0% to with programming that's just like man 00:03:02.760 --> 00:03:04.130 align:start position:0% to with programming that's just like man yeah<00:03:03.239> okay 00:03:04.130 --> 00:03:04.140 align:start position:0% yeah okay 00:03:04.140 --> 00:03:07.790 align:start position:0% yeah okay uh<00:03:04.920> the<00:03:05.640> point<00:03:05.760> is<00:03:06.000> that<00:03:06.959> when<00:03:07.260> we<00:03:07.500> have<00:03:07.620> a 00:03:07.790 --> 00:03:07.800 align:start position:0% uh the point is that when we have a 00:03:07.800 --> 00:03:09.530 align:start position:0% uh the point is that when we have a process<00:03:08.099> a<00:03:08.340> process<00:03:08.640> like<00:03:08.879> that<00:03:09.120> we<00:03:09.360> can 00:03:09.530 --> 00:03:09.540 align:start position:0% process a process like that we can 00:03:09.540 --> 00:03:13.130 align:start position:0% process a process like that we can compose<00:03:10.140> it<00:03:10.980> with<00:03:11.220> other<00:03:11.340> processes<00:03:12.060> so<00:03:12.840> for 00:03:13.130 --> 00:03:13.140 align:start position:0% compose it with other processes so for 00:03:13.140 --> 00:03:14.210 align:start position:0% compose it with other processes so for instance 00:03:14.210 --> 00:03:14.220 align:start position:0% instance 00:03:14.220 --> 00:03:16.729 align:start position:0% instance in<00:03:14.700> here<00:03:14.879> we<00:03:15.300> take<00:03:15.420> this<00:03:15.720> process<00:03:16.019> we<00:03:16.440> notice 00:03:16.729 --> 00:03:16.739 align:start position:0% in here we take this process we notice 00:03:16.739 --> 00:03:20.149 align:start position:0% in here we take this process we notice that<00:03:16.920> it<00:03:17.640> needs<00:03:18.599> an<00:03:18.720> input<00:03:19.019> that<00:03:19.620> is<00:03:19.800> a<00:03:19.980> number 00:03:20.149 --> 00:03:20.159 align:start position:0% that it needs an input that is a number 00:03:20.159 --> 00:03:22.430 align:start position:0% that it needs an input that is a number and<00:03:20.640> spits<00:03:21.120> out<00:03:21.180> an<00:03:21.480> output<00:03:21.780> that<00:03:21.959> is<00:03:22.140> a<00:03:22.260> number 00:03:22.430 --> 00:03:22.440 align:start position:0% and spits out an output that is a number 00:03:22.440 --> 00:03:24.589 align:start position:0% and spits out an output that is a number and<00:03:23.280> we<00:03:23.459> realize<00:03:23.700> that<00:03:23.879> oh<00:03:24.060> we<00:03:24.300> can<00:03:24.480> actually 00:03:24.589 --> 00:03:24.599 align:start position:0% and we realize that oh we can actually 00:03:24.599 --> 00:03:28.729 align:start position:0% and we realize that oh we can actually pipe<00:03:25.379> this<00:03:25.739> process<00:03:26.040> with<00:03:26.400> itself<00:03:27.080> and<00:03:28.080> if<00:03:28.560> we 00:03:28.729 --> 00:03:28.739 align:start position:0% pipe this process with itself and if we 00:03:28.739 --> 00:03:30.830 align:start position:0% pipe this process with itself and if we do<00:03:28.860> that<00:03:29.040> by<00:03:29.340> just<00:03:29.580> concatenating<00:03:30.180> the<00:03:30.420> boxes 00:03:30.830 --> 00:03:30.840 align:start position:0% do that by just concatenating the boxes 00:03:30.840 --> 00:03:33.410 align:start position:0% do that by just concatenating the boxes you<00:03:31.260> see<00:03:31.500> that<00:03:31.739> this<00:03:31.920> will<00:03:32.099> be<00:03:32.340> equivalent<00:03:32.879> to 00:03:33.410 --> 00:03:33.420 align:start position:0% you see that this will be equivalent to 00:03:33.420 --> 00:03:36.949 align:start position:0% you see that this will be equivalent to the<00:03:33.599> process<00:03:33.959> that<00:03:34.440> adds<00:03:34.860> to<00:03:34.980> to<00:03:35.819> your<00:03:36.120> input 00:03:36.949 --> 00:03:36.959 align:start position:0% the process that adds to to your input 00:03:36.959 --> 00:03:39.470 align:start position:0% the process that adds to to your input now<00:03:37.620> this<00:03:37.920> seems<00:03:38.340> very 00:03:39.470 --> 00:03:39.480 align:start position:0% now this seems very 00:03:39.480 --> 00:03:43.130 align:start position:0% now this seems very naive<00:03:40.440> but<00:03:41.220> the<00:03:42.060> nice<00:03:42.239> thing<00:03:42.480> about<00:03:42.720> this 00:03:43.130 --> 00:03:43.140 align:start position:0% naive but the nice thing about this 00:03:43.140 --> 00:03:45.890 align:start position:0% naive but the nice thing about this picture<00:03:43.319> is<00:03:43.860> that<00:03:44.099> it<00:03:44.220> goes<00:03:44.580> both<00:03:44.819> ways<00:03:45.239> you 00:03:45.890 --> 00:03:45.900 align:start position:0% picture is that it goes both ways you 00:03:45.900 --> 00:03:48.289 align:start position:0% picture is that it goes both ways you can<00:03:46.019> start<00:03:46.200> from<00:03:46.620> the<00:03:47.159> top<00:03:47.280> row<00:03:47.700> where<00:03:48.120> you 00:03:48.289 --> 00:03:48.299 align:start position:0% can start from the top row where you 00:03:48.299 --> 00:03:50.869 align:start position:0% can start from the top row where you have<00:03:48.480> simple<00:03:48.659> components<00:03:49.440> and<00:03:50.280> you<00:03:50.700> actually 00:03:50.869 --> 00:03:50.879 align:start position:0% have simple components and you actually 00:03:50.879 --> 00:03:54.949 align:start position:0% have simple components and you actually abstract<00:03:51.659> away<00:03:51.959> so<00:03:52.680> add<00:03:53.040> to<00:03:53.280> uh<00:03:54.239> is<00:03:54.480> basically 00:03:54.949 --> 00:03:54.959 align:start position:0% abstract away so add to uh is basically 00:03:54.959 --> 00:03:56.930 align:start position:0% abstract away so add to uh is basically just<00:03:55.739> you<00:03:55.980> know<00:03:56.040> the<00:03:56.340> dotted<00:03:56.700> box 00:03:56.930 --> 00:03:56.940 align:start position:0% just you know the dotted box 00:03:56.940 --> 00:03:59.390 align:start position:0% just you know the dotted box encompassing<00:03:57.840> the<00:03:58.019> two<00:03:58.200> or<00:03:58.860> you<00:03:59.040> can<00:03:59.099> do<00:03:59.220> the 00:03:59.390 --> 00:03:59.400 align:start position:0% encompassing the two or you can do the 00:03:59.400 --> 00:04:02.449 align:start position:0% encompassing the two or you can do the opposite<00:03:59.760> you<00:04:00.000> can<00:04:00.180> start<00:04:00.480> from<00:04:00.900> a<00:04:01.500> process<00:04:01.799> up 00:04:02.449 --> 00:04:02.459 align:start position:0% opposite you can start from a process up 00:04:02.459 --> 00:04:05.570 align:start position:0% opposite you can start from a process up to<00:04:02.700> and<00:04:03.360> open<00:04:03.599> it<00:04:03.840> up<00:04:04.019> and<00:04:04.440> further<00:04:04.799> specify<00:04:05.340> it 00:04:05.570 --> 00:04:05.580 align:start position:0% to and open it up and further specify it 00:04:05.580 --> 00:04:09.170 align:start position:0% to and open it up and further specify it with<00:04:06.299> a<00:04:06.480> finer<00:04:06.840> degree<00:04:07.200> of<00:04:07.620> accuracy<00:04:08.580> and 00:04:09.170 --> 00:04:09.180 align:start position:0% with a finer degree of accuracy and 00:04:09.180 --> 00:04:10.729 align:start position:0% with a finer degree of accuracy and since<00:04:09.360> you<00:04:09.540> have<00:04:09.659> an<00:04:09.780> equal<00:04:09.900> sign<00:04:10.260> you<00:04:10.620> can 00:04:10.729 --> 00:04:10.739 align:start position:0% since you have an equal sign you can 00:04:10.739 --> 00:04:13.309 align:start position:0% since you have an equal sign you can basically<00:04:10.980> go<00:04:11.280> both<00:04:11.580> ways 00:04:13.309 --> 00:04:13.319 align:start position:0% basically go both ways 00:04:13.319 --> 00:04:16.550 align:start position:0% basically go both ways now<00:04:14.040> there<00:04:14.519> are<00:04:14.700> very<00:04:15.360> peculiar<00:04:15.959> processes 00:04:16.550 --> 00:04:16.560 align:start position:0% now there are very peculiar processes 00:04:16.560 --> 00:04:19.250 align:start position:0% now there are very peculiar processes that<00:04:16.859> that<00:04:17.280> are<00:04:17.519> called<00:04:17.820> identity<00:04:18.600> processes 00:04:19.250 --> 00:04:19.260 align:start position:0% that that are called identity processes 00:04:19.260 --> 00:04:21.409 align:start position:0% that that are called identity processes these<00:04:20.100> are<00:04:20.160> the<00:04:20.340> processes<00:04:20.760> that<00:04:20.940> don't<00:04:21.180> do 00:04:21.409 --> 00:04:21.419 align:start position:0% these are the processes that don't do 00:04:21.419 --> 00:04:24.590 align:start position:0% these are the processes that don't do anything<00:04:21.979> in<00:04:22.979> this<00:04:23.100> case<00:04:23.340> with<00:04:24.300> the<00:04:24.419> number 00:04:24.590 --> 00:04:24.600 align:start position:0% anything in this case with the number 00:04:24.600 --> 00:04:27.110 align:start position:0% anything in this case with the number example<00:04:25.259> we<00:04:25.620> have<00:04:25.740> a<00:04:25.979> process<00:04:26.280> that<00:04:26.699> is<00:04:26.820> at 00:04:27.110 --> 00:04:27.120 align:start position:0% example we have a process that is at 00:04:27.120 --> 00:04:30.170 align:start position:0% example we have a process that is at zero<00:04:27.660> that<00:04:28.320> takes<00:04:28.560> a<00:04:28.740> number<00:04:28.860> in<00:04:29.100> input<00:04:29.460> does 00:04:30.170 --> 00:04:30.180 align:start position:0% zero that takes a number in input does 00:04:30.180 --> 00:04:32.689 align:start position:0% zero that takes a number in input does absolutely<00:04:30.720> nothing<00:04:31.139> with<00:04:31.440> it<00:04:31.620> and<00:04:32.160> spits<00:04:32.580> the 00:04:32.689 --> 00:04:32.699 align:start position:0% absolutely nothing with it and spits the 00:04:32.699 --> 00:04:34.610 align:start position:0% absolutely nothing with it and spits the same<00:04:32.820> number<00:04:33.060> as<00:04:33.479> output 00:04:34.610 --> 00:04:34.620 align:start position:0% same number as output 00:04:34.620 --> 00:04:37.070 align:start position:0% same number as output the<00:04:35.340> good<00:04:35.520> thing<00:04:35.639> about<00:04:35.880> graphical<00:04:36.479> reasoning 00:04:37.070 --> 00:04:37.080 align:start position:0% the good thing about graphical reasoning 00:04:37.080 --> 00:04:38.930 align:start position:0% the good thing about graphical reasoning is<00:04:37.380> that<00:04:37.560> since<00:04:37.800> this<00:04:38.100> thing<00:04:38.220> is<00:04:38.460> not<00:04:38.699> doing 00:04:38.930 --> 00:04:38.940 align:start position:0% is that since this thing is not doing 00:04:38.940 --> 00:04:41.870 align:start position:0% is that since this thing is not doing absolutely<00:04:39.600> anything<00:04:39.960> we<00:04:40.740> can<00:04:40.919> just<00:04:41.220> not<00:04:41.639> draw 00:04:41.870 --> 00:04:41.880 align:start position:0% absolutely anything we can just not draw 00:04:41.880 --> 00:04:42.650 align:start position:0% absolutely anything we can just not draw it 00:04:42.650 --> 00:04:42.660 align:start position:0% it 00:04:42.660 --> 00:04:45.170 align:start position:0% it and<00:04:43.440> indeed<00:04:43.800> I'm<00:04:44.040> drawing<00:04:44.340> it<00:04:44.460> as<00:04:44.639> a<00:04:44.820> dotted 00:04:45.170 --> 00:04:45.180 align:start position:0% and indeed I'm drawing it as a dotted 00:04:45.180 --> 00:04:48.530 align:start position:0% and indeed I'm drawing it as a dotted box<00:04:45.360> uh<00:04:46.320> down<00:04:46.560> here<00:04:46.979> just<00:04:47.759> to 00:04:48.530 --> 00:04:48.540 align:start position:0% box uh down here just to 00:04:48.540 --> 00:04:50.870 align:start position:0% box uh down here just to highlight<00:04:49.380> that<00:04:49.860> there<00:04:50.400> should<00:04:50.580> be<00:04:50.699> something 00:04:50.870 --> 00:04:50.880 align:start position:0% highlight that there should be something 00:04:50.880 --> 00:04:52.670 align:start position:0% highlight that there should be something there 00:04:52.670 --> 00:04:52.680 align:start position:0% there 00:04:52.680 --> 00:04:54.650 align:start position:0% there but<00:04:53.160> you<00:04:53.280> know<00:04:53.400> with<00:04:53.580> this<00:04:53.820> very<00:04:54.060> simple<00:04:54.240> trick 00:04:54.650 --> 00:04:54.660 align:start position:0% but you know with this very simple trick 00:04:54.660 --> 00:04:56.210 align:start position:0% but you know with this very simple trick we<00:04:54.900> can<00:04:55.080> already<00:04:55.199> start<00:04:55.560> proving<00:04:55.979> some 00:04:56.210 --> 00:04:56.220 align:start position:0% we can already start proving some 00:04:56.220 --> 00:04:57.290 align:start position:0% we can already start proving some equations 00:04:57.290 --> 00:04:57.300 align:start position:0% equations 00:04:57.300 --> 00:05:00.350 align:start position:0% equations that<00:04:57.780> are<00:04:57.900> very<00:04:58.139> simple<00:04:58.320> so<00:04:58.860> if<00:04:59.280> I<00:04:59.400> add<00:04:59.580> one<00:04:59.880> and 00:05:00.350 --> 00:05:00.360 align:start position:0% that are very simple so if I add one and 00:05:00.360 --> 00:05:03.230 align:start position:0% that are very simple so if I add one and then<00:05:00.479> I<00:05:00.660> add<00:05:00.840> 0<00:05:01.139> is<00:05:01.800> like<00:05:02.100> just<00:05:02.639> adding<00:05:03.060> one 00:05:03.230 --> 00:05:03.240 align:start position:0% then I add 0 is like just adding one 00:05:03.240 --> 00:05:04.550 align:start position:0% then I add 0 is like just adding one right 00:05:04.550 --> 00:05:04.560 align:start position:0% right 00:05:04.560 --> 00:05:07.430 align:start position:0% right if<00:05:05.280> you<00:05:05.580> know<00:05:05.699> you<00:05:06.240> adopt<00:05:06.660> the<00:05:06.780> convention<00:05:07.139> of 00:05:07.430 --> 00:05:07.440 align:start position:0% if you know you adopt the convention of 00:05:07.440 --> 00:05:10.670 align:start position:0% if you know you adopt the convention of not<00:05:07.620> drawing<00:05:08.040> identity<00:05:08.520> processes<00:05:09.139> then<00:05:10.139> the 00:05:10.670 --> 00:05:10.680 align:start position:0% not drawing identity processes then the 00:05:10.680 --> 00:05:12.830 align:start position:0% not drawing identity processes then the picture<00:05:10.919> on<00:05:11.220> the<00:05:11.460> top<00:05:11.639> row<00:05:12.060> just<00:05:12.360> looks<00:05:12.660> like 00:05:12.830 --> 00:05:12.840 align:start position:0% picture on the top row just looks like 00:05:12.840 --> 00:05:15.230 align:start position:0% picture on the top row just looks like the<00:05:13.139> one<00:05:13.259> in<00:05:13.500> the<00:05:13.620> bottom<00:05:13.919> row<00:05:14.220> while<00:05:14.820> you<00:05:15.120> have 00:05:15.230 --> 00:05:15.240 align:start position:0% the one in the bottom row while you have 00:05:15.240 --> 00:05:19.570 align:start position:0% the one in the bottom row while you have stretched<00:05:15.780> a<00:05:16.740> wire<00:05:16.919> a<00:05:17.340> little<00:05:17.460> bit<00:05:17.639> more 00:05:19.570 --> 00:05:19.580 align:start position:0% stretched a wire a little bit more 00:05:19.580 --> 00:05:22.909 align:start position:0% stretched a wire a little bit more similarly<00:05:20.580> from<00:05:21.000> I<00:05:21.540> don't<00:05:22.020> have<00:05:22.259> it<00:05:22.440> here<00:05:22.620> on 00:05:22.909 --> 00:05:22.919 align:start position:0% similarly from I don't have it here on 00:05:22.919 --> 00:05:24.710 align:start position:0% similarly from I don't have it here on on<00:05:23.160> the<00:05:23.400> slides<00:05:23.759> but<00:05:24.060> you<00:05:24.479> can<00:05:24.600> understand 00:05:24.710 --> 00:05:24.720 align:start position:0% on the slides but you can understand 00:05:24.720 --> 00:05:27.230 align:start position:0% on the slides but you can understand that<00:05:25.199> in<00:05:25.500> this<00:05:25.680> formalism<00:05:26.160> the<00:05:26.820> composition 00:05:27.230 --> 00:05:27.240 align:start position:0% that in this formalism the composition 00:05:27.240 --> 00:05:29.990 align:start position:0% that in this formalism the composition is<00:05:27.660> associative<00:05:28.320> we<00:05:28.979> don't<00:05:29.100> use<00:05:29.340> parentheses 00:05:29.990 --> 00:05:30.000 align:start position:0% is associative we don't use parentheses 00:05:30.000 --> 00:05:32.990 align:start position:0% is associative we don't use parentheses if<00:05:30.360> you<00:05:30.620> concatenate<00:05:31.620> three<00:05:31.919> boxes<00:05:32.460> one<00:05:32.880> after 00:05:32.990 --> 00:05:33.000 align:start position:0% if you concatenate three boxes one after 00:05:33.000 --> 00:05:35.270 align:start position:0% if you concatenate three boxes one after the<00:05:33.300> other<00:05:33.479> it<00:05:34.139> doesn't<00:05:34.320> matter<00:05:34.620> in<00:05:35.039> which 00:05:35.270 --> 00:05:35.280 align:start position:0% the other it doesn't matter in which 00:05:35.280 --> 00:05:37.370 align:start position:0% the other it doesn't matter in which order<00:05:35.460> you<00:05:35.940> obstruct<00:05:36.419> them 00:05:37.370 --> 00:05:37.380 align:start position:0% order you obstruct them 00:05:37.380 --> 00:05:39.770 align:start position:0% order you obstruct them in<00:05:37.860> the<00:05:38.039> end<00:05:38.100> you<00:05:38.400> only<00:05:38.580> have<00:05:38.820> three<00:05:39.000> boxes<00:05:39.539> so 00:05:39.770 --> 00:05:39.780 align:start position:0% in the end you only have three boxes so 00:05:39.780 --> 00:05:42.590 align:start position:0% in the end you only have three boxes so it<00:05:39.960> doesn't<00:05:40.139> matter<00:05:40.380> how<00:05:40.740> you<00:05:40.919> group<00:05:41.100> them 00:05:42.590 --> 00:05:42.600 align:start position:0% it doesn't matter how you group them 00:05:42.600 --> 00:05:45.230 align:start position:0% it doesn't matter how you group them okay<00:05:43.080> let's<00:05:43.440> do<00:05:43.680> another<00:05:43.860> example 00:05:45.230 --> 00:05:45.240 align:start position:0% okay let's do another example 00:05:45.240 --> 00:05:46.550 align:start position:0% okay let's do another example so 00:05:46.550 --> 00:05:46.560 align:start position:0% so 00:05:46.560 --> 00:05:49.029 align:start position:0% so for<00:05:47.039> this<00:05:47.280> example<00:05:47.580> I'm<00:05:47.820> using<00:05:48.120> gravitation 00:05:49.029 --> 00:05:49.039 align:start position:0% for this example I'm using gravitation 00:05:49.039 --> 00:05:51.110 align:start position:0% for this example I'm using gravitation gravitation<00:05:50.039> that<00:05:50.340> has<00:05:50.580> absolutely<00:05:50.880> nothing 00:05:51.110 --> 00:05:51.120 align:start position:0% gravitation that has absolutely nothing 00:05:51.120 --> 00:05:54.170 align:start position:0% gravitation that has absolutely nothing to<00:05:51.360> do<00:05:51.479> with<00:05:51.720> crypto<00:05:52.080> I<00:05:52.500> admit<00:05:52.800> uh<00:05:53.520> at<00:05:53.759> least<00:05:53.940> I 00:05:54.170 --> 00:05:54.180 align:start position:0% to do with crypto I admit uh at least I 00:05:54.180 --> 00:05:56.029 align:start position:0% to do with crypto I admit uh at least I I<00:05:54.479> think<00:05:54.720> I<00:05:54.960> don't<00:05:55.080> know<00:05:55.199> maybe 00:05:56.029 --> 00:05:56.039 align:start position:0% I think I don't know maybe 00:05:56.039 --> 00:05:59.510 align:start position:0% I think I don't know maybe uh<00:05:56.759> so<00:05:57.000> we<00:05:57.180> have<00:05:57.300> a<00:05:57.479> system<00:05:57.660> that<00:05:58.139> is<00:05:58.320> a<00:05:58.680> sun 00:05:59.510 --> 00:05:59.520 align:start position:0% uh so we have a system that is a sun 00:05:59.520 --> 00:06:02.390 align:start position:0% uh so we have a system that is a sun that<00:06:00.120> is<00:06:00.300> just<00:06:00.539> sit<00:06:00.720> there<00:06:01.020> and<00:06:01.440> you<00:06:01.680> know<00:06:01.800> does 00:06:02.390 --> 00:06:02.400 align:start position:0% that is just sit there and you know does 00:06:02.400 --> 00:06:04.909 align:start position:0% that is just sit there and you know does nothing<00:06:02.699> and<00:06:03.360> raise<00:06:03.660> the<00:06:03.960> earth<00:06:04.080> that<00:06:04.740> is 00:06:04.909 --> 00:06:04.919 align:start position:0% nothing and raise the earth that is 00:06:04.919 --> 00:06:07.430 align:start position:0% nothing and raise the earth that is orbiting<00:06:05.520> around<00:06:05.699> the<00:06:06.000> Sun 00:06:07.430 --> 00:06:07.440 align:start position:0% orbiting around the Sun 00:06:07.440 --> 00:06:09.170 align:start position:0% orbiting around the Sun so<00:06:08.100> you<00:06:08.460> know 00:06:09.170 --> 00:06:09.180 align:start position:0% so you know 00:06:09.180 --> 00:06:12.110 align:start position:0% so you know during<00:06:09.960> many<00:06:10.620> centuries<00:06:11.160> people<00:06:11.520> thought<00:06:11.880> a 00:06:12.110 --> 00:06:12.120 align:start position:0% during many centuries people thought a 00:06:12.120 --> 00:06:14.110 align:start position:0% during many centuries people thought a lot<00:06:12.240> about<00:06:12.479> this<00:06:12.840> and<00:06:13.259> at<00:06:13.440> some<00:06:13.680> point 00:06:14.110 --> 00:06:14.120 align:start position:0% lot about this and at some point 00:06:14.120 --> 00:06:16.850 align:start position:0% lot about this and at some point basically<00:06:15.120> a<00:06:15.360> guy<00:06:15.479> called<00:06:15.720> Newton<00:06:16.259> found<00:06:16.620> out 00:06:16.850 --> 00:06:16.860 align:start position:0% basically a guy called Newton found out 00:06:16.860 --> 00:06:18.830 align:start position:0% basically a guy called Newton found out that<00:06:17.100> there<00:06:17.280> is<00:06:17.460> a<00:06:17.580> process<00:06:17.940> that<00:06:18.600> you<00:06:18.720> can 00:06:18.830 --> 00:06:18.840 align:start position:0% that there is a process that you can 00:06:18.840 --> 00:06:20.270 align:start position:0% that there is a process that you can call<00:06:18.960> evolve 00:06:20.270 --> 00:06:20.280 align:start position:0% call evolve 00:06:20.280 --> 00:06:22.370 align:start position:0% call evolve in<00:06:20.820> which<00:06:20.940> you<00:06:21.240> can<00:06:21.419> feed 00:06:22.370 --> 00:06:22.380 align:start position:0% in which you can feed 00:06:22.380 --> 00:06:25.670 align:start position:0% in which you can feed a<00:06:23.340> state<00:06:23.940> of<00:06:24.300> your<00:06:24.539> system<00:06:24.780> and<00:06:25.259> then<00:06:25.380> you<00:06:25.620> can 00:06:25.670 --> 00:06:25.680 align:start position:0% a state of your system and then you can 00:06:25.680 --> 00:06:28.730 align:start position:0% a state of your system and then you can say<00:06:25.860> okay<00:06:26.100> show<00:06:26.580> me<00:06:26.759> what<00:06:27.539> happens<00:06:27.720> one<00:06:28.560> second 00:06:28.730 --> 00:06:28.740 align:start position:0% say okay show me what happens one second 00:06:28.740 --> 00:06:29.629 align:start position:0% say okay show me what happens one second later 00:06:29.629 --> 00:06:29.639 align:start position:0% later 00:06:29.639 --> 00:06:31.909 align:start position:0% later and<00:06:30.240> this<00:06:30.479> is<00:06:30.600> a<00:06:30.720> beautiful<00:06:30.840> predictive<00:06:31.680> power 00:06:31.909 --> 00:06:31.919 align:start position:0% and this is a beautiful predictive power 00:06:31.919 --> 00:06:34.670 align:start position:0% and this is a beautiful predictive power of<00:06:32.220> physics<00:06:32.580> in<00:06:33.539> this<00:06:33.660> case<00:06:33.840> of<00:06:34.139> dynamical 00:06:34.670 --> 00:06:34.680 align:start position:0% of physics in this case of dynamical 00:06:34.680 --> 00:06:37.790 align:start position:0% of physics in this case of dynamical systems<00:06:35.280> that<00:06:36.000> allows<00:06:36.360> you<00:06:36.419> to<00:06:36.720> start<00:06:36.960> from 00:06:37.790 --> 00:06:37.800 align:start position:0% systems that allows you to start from 00:06:37.800 --> 00:06:40.909 align:start position:0% systems that allows you to start from some<00:06:38.660> experimental<00:06:39.660> evidence<00:06:40.080> and<00:06:40.500> predict 00:06:40.909 --> 00:06:40.919 align:start position:0% some experimental evidence and predict 00:06:40.919 --> 00:06:44.029 align:start position:0% some experimental evidence and predict what<00:06:41.580> is<00:06:41.759> going<00:06:41.940> to<00:06:42.120> happen<00:06:42.560> uh<00:06:43.560> in<00:06:43.800> the<00:06:43.919> future 00:06:44.029 --> 00:06:44.039 align:start position:0% what is going to happen uh in the future 00:06:44.039 --> 00:06:46.969 align:start position:0% what is going to happen uh in the future you<00:06:44.699> see<00:06:44.880> that<00:06:45.060> in<00:06:45.419> this<00:06:45.539> example<00:06:46.020> you<00:06:46.620> also 00:06:46.969 --> 00:06:46.979 align:start position:0% you see that in this example you also 00:06:46.979 --> 00:06:49.370 align:start position:0% you see that in this example you also have<00:06:47.280> an<00:06:47.580> identity<00:06:47.940> process<00:06:48.360> that<00:06:49.080> is<00:06:49.199> the 00:06:49.370 --> 00:06:49.380 align:start position:0% have an identity process that is the 00:06:49.380 --> 00:06:51.770 align:start position:0% have an identity process that is the process<00:06:49.620> that<00:06:49.979> doesn't<00:06:50.220> evolve<00:06:51.060> evolve<00:06:51.660> for 00:06:51.770 --> 00:06:51.780 align:start position:0% process that doesn't evolve evolve for 00:06:51.780 --> 00:06:54.110 align:start position:0% process that doesn't evolve evolve for like<00:06:52.020> zero<00:06:52.560> time<00:06:52.680> it's<00:06:53.400> just<00:06:53.639> taking<00:06:53.819> the 00:06:54.110 --> 00:06:54.120 align:start position:0% like zero time it's just taking the 00:06:54.120 --> 00:06:56.210 align:start position:0% like zero time it's just taking the input<00:06:54.419> and<00:06:54.840> is<00:06:54.960> not<00:06:55.199> looking<00:06:55.500> in<00:06:55.979> the<00:06:56.100> future 00:06:56.210 --> 00:06:56.220 align:start position:0% input and is not looking in the future 00:06:56.220 --> 00:06:58.550 align:start position:0% input and is not looking in the future or<00:06:56.580> in<00:06:56.759> the<00:06:56.940> past<00:06:57.060> it's<00:06:57.300> just<00:06:57.539> giving<00:06:57.780> you<00:06:58.020> the 00:06:58.550 --> 00:06:58.560 align:start position:0% or in the past it's just giving you the 00:06:58.560 --> 00:07:00.350 align:start position:0% or in the past it's just giving you the state<00:06:58.680> that<00:06:58.979> is<00:06:59.100> as<00:06:59.280> it<00:06:59.400> is<00:06:59.580> now 00:07:00.350 --> 00:07:00.360 align:start position:0% state that is as it is now 00:07:00.360 --> 00:07:02.029 align:start position:0% state that is as it is now and<00:07:00.900> we<00:07:01.020> see<00:07:01.139> that<00:07:01.319> we<00:07:01.440> have<00:07:01.560> a<00:07:01.620> notion<00:07:01.919> of 00:07:02.029 --> 00:07:02.039 align:start position:0% and we see that we have a notion of 00:07:02.039 --> 00:07:05.029 align:start position:0% and we see that we have a notion of composition<00:07:02.460> because<00:07:02.880> if<00:07:03.419> I<00:07:03.660> let<00:07:04.080> evolve<00:07:04.740> the 00:07:05.029 --> 00:07:05.039 align:start position:0% composition because if I let evolve the 00:07:05.039 --> 00:07:07.909 align:start position:0% composition because if I let evolve the process<00:07:05.340> for<00:07:05.699> I<00:07:06.120> don't<00:07:06.240> know<00:07:06.300> one<00:07:06.600> second<00:07:06.840> I<00:07:07.680> go 00:07:07.909 --> 00:07:07.919 align:start position:0% process for I don't know one second I go 00:07:07.919 --> 00:07:10.909 align:start position:0% process for I don't know one second I go from<00:07:08.220> the<00:07:08.699> position<00:07:08.880> Mark<00:07:09.360> type<00:07:09.660> t0<00:07:10.199> to<00:07:10.740> the 00:07:10.909 --> 00:07:10.919 align:start position:0% from the position Mark type t0 to the 00:07:10.919 --> 00:07:14.629 align:start position:0% from the position Mark type t0 to the position<00:07:11.100> Mark<00:07:11.580> T1<00:07:12.060> again<00:07:12.780> I<00:07:13.259> can<00:07:13.440> feed<00:07:13.740> T1<00:07:14.280> to 00:07:14.629 --> 00:07:14.639 align:start position:0% position Mark T1 again I can feed T1 to 00:07:14.639 --> 00:07:17.629 align:start position:0% position Mark T1 again I can feed T1 to the<00:07:14.759> system<00:07:15.000> another<00:07:15.960> time<00:07:16.319> let<00:07:17.039> it<00:07:17.220> evolve 00:07:17.629 --> 00:07:17.639 align:start position:0% the system another time let it evolve 00:07:17.639 --> 00:07:20.870 align:start position:0% the system another time let it evolve for<00:07:18.419> another<00:07:18.600> second<00:07:18.960> and<00:07:19.380> I<00:07:19.560> go<00:07:19.680> to<00:07:19.800> T2 00:07:20.870 --> 00:07:20.880 align:start position:0% for another second and I go to T2 00:07:20.880 --> 00:07:22.850 align:start position:0% for another second and I go to T2 and<00:07:21.360> that<00:07:21.479> would<00:07:21.660> be<00:07:21.780> the<00:07:22.020> same<00:07:22.139> of<00:07:22.380> evolving 00:07:22.850 --> 00:07:22.860 align:start position:0% and that would be the same of evolving 00:07:22.860 --> 00:07:25.010 align:start position:0% and that would be the same of evolving the<00:07:23.039> system<00:07:23.220> for<00:07:23.580> two<00:07:23.819> seconds<00:07:24.060> so<00:07:24.539> again<00:07:24.720> I 00:07:25.010 --> 00:07:25.020 align:start position:0% the system for two seconds so again I 00:07:25.020 --> 00:07:27.890 align:start position:0% the system for two seconds so again I can<00:07:25.139> combine<00:07:25.740> These<00:07:26.340> Bricks 00:07:27.890 --> 00:07:27.900 align:start position:0% can combine These Bricks 00:07:27.900 --> 00:07:31.550 align:start position:0% can combine These Bricks now<00:07:28.800> the<00:07:29.460> important<00:07:30.000> thing<00:07:30.240> is<00:07:30.479> that<00:07:30.840> anything 00:07:31.550 --> 00:07:31.560 align:start position:0% now the important thing is that anything 00:07:31.560 --> 00:07:33.770 align:start position:0% now the important thing is that anything that<00:07:32.160> matters<00:07:32.520> everything<00:07:32.940> that<00:07:33.240> matters<00:07:33.599> in 00:07:33.770 --> 00:07:33.780 align:start position:0% that matters everything that matters in 00:07:33.780 --> 00:07:35.809 align:start position:0% that matters everything that matters in this<00:07:33.960> formalism<00:07:34.440> is<00:07:35.099> how<00:07:35.280> things<00:07:35.520> are 00:07:35.809 --> 00:07:35.819 align:start position:0% this formalism is how things are 00:07:35.819 --> 00:07:38.749 align:start position:0% this formalism is how things are connected<00:07:36.300> you<00:07:36.840> can<00:07:36.960> deform<00:07:37.440> the<00:07:37.620> wires<00:07:38.099> no 00:07:38.749 --> 00:07:38.759 align:start position:0% connected you can deform the wires no 00:07:38.759 --> 00:07:41.809 align:start position:0% connected you can deform the wires no problem<00:07:39.000> what<00:07:39.960> you<00:07:40.199> can't<00:07:40.380> do<00:07:40.740> is<00:07:41.220> you<00:07:41.580> cannot 00:07:41.809 --> 00:07:41.819 align:start position:0% problem what you can't do is you cannot 00:07:41.819 --> 00:07:43.790 align:start position:0% problem what you can't do is you cannot make<00:07:42.060> new<00:07:42.419> connections<00:07:42.960> or<00:07:43.319> splitting 00:07:43.790 --> 00:07:43.800 align:start position:0% make new connections or splitting 00:07:43.800 --> 00:07:46.189 align:start position:0% make new connections or splitting connections<00:07:44.400> if<00:07:45.060> you<00:07:45.180> do<00:07:45.360> you<00:07:45.840> are<00:07:45.960> getting 00:07:46.189 --> 00:07:46.199 align:start position:0% connections if you do you are getting 00:07:46.199 --> 00:07:48.350 align:start position:0% connections if you do you are getting something<00:07:46.620> that<00:07:46.860> has<00:07:47.039> a<00:07:47.220> different<00:07:47.400> meaning 00:07:48.350 --> 00:07:48.360 align:start position:0% something that has a different meaning 00:07:48.360 --> 00:07:51.110 align:start position:0% something that has a different meaning another<00:07:49.080> important<00:07:49.620> thing<00:07:49.860> is<00:07:50.580> that<00:07:50.759> you<00:07:51.000> can 00:07:51.110 --> 00:07:51.120 align:start position:0% another important thing is that you can 00:07:51.120 --> 00:07:55.550 align:start position:0% another important thing is that you can only<00:07:51.419> compose<00:07:52.199> things<00:07:53.160> with<00:07:53.819> matching<00:07:54.240> types 00:07:55.550 --> 00:07:55.560 align:start position:0% only compose things with matching types 00:07:55.560 --> 00:07:58.010 align:start position:0% only compose things with matching types for<00:07:56.160> instance<00:07:56.460> senior<00:07:56.940> I<00:07:57.240> have<00:07:57.360> the<00:07:57.539> Hub<00:07:57.720> one 00:07:58.010 --> 00:07:58.020 align:start position:0% for instance senior I have the Hub one 00:07:58.020 --> 00:08:01.490 align:start position:0% for instance senior I have the Hub one process<00:07:58.440> we<00:07:59.160> saw<00:07:59.340> that<00:07:59.639> that<00:07:59.880> spits<00:08:00.360> out<00:08:00.539> a 00:08:01.490 --> 00:08:01.500 align:start position:0% process we saw that that spits out a 00:08:01.500 --> 00:08:02.450 align:start position:0% process we saw that that spits out a number 00:08:02.450 --> 00:08:02.460 align:start position:0% number 00:08:02.460 --> 00:08:05.029 align:start position:0% number but<00:08:03.060> the<00:08:03.240> evolved<00:08:03.780> thing<00:08:03.900> wanted<00:08:04.680> something 00:08:05.029 --> 00:08:05.039 align:start position:0% but the evolved thing wanted something 00:08:05.039 --> 00:08:07.850 align:start position:0% but the evolved thing wanted something of<00:08:05.340> type<00:08:05.520> sun<00:08:05.880> earth<00:08:06.180> as<00:08:06.660> an<00:08:06.840> input<00:08:07.139> so<00:08:07.560> you<00:08:07.740> see 00:08:07.850 --> 00:08:07.860 align:start position:0% of type sun earth as an input so you see 00:08:07.860 --> 00:08:09.710 align:start position:0% of type sun earth as an input so you see that<00:08:08.039> it<00:08:08.220> doesn't<00:08:08.460> really<00:08:08.819> make<00:08:09.120> sense<00:08:09.360> to 00:08:09.710 --> 00:08:09.720 align:start position:0% that it doesn't really make sense to 00:08:09.720 --> 00:08:11.749 align:start position:0% that it doesn't really make sense to compose<00:08:10.080> these<00:08:10.440> things<00:08:10.560> because<00:08:11.280> they<00:08:11.580> are 00:08:11.749 --> 00:08:11.759 align:start position:0% compose these things because they are 00:08:11.759 --> 00:08:14.570 align:start position:0% compose these things because they are apples<00:08:12.120> and<00:08:12.300> pears 00:08:14.570 --> 00:08:14.580 align:start position:0% apples and pears 00:08:14.580 --> 00:08:17.150 align:start position:0% apples and pears Okay<00:08:15.180> so 00:08:17.150 --> 00:08:17.160 align:start position:0% Okay so 00:08:17.160 --> 00:08:20.330 align:start position:0% Okay so this<00:08:18.060> tells<00:08:18.479> us<00:08:18.539> the<00:08:18.960> types<00:08:19.379> in<00:08:19.979> this 00:08:20.330 --> 00:08:20.340 align:start position:0% this tells us the types in this 00:08:20.340 --> 00:08:23.629 align:start position:0% this tells us the types in this formalism<00:08:20.940> are<00:08:21.780> very<00:08:22.020> important<00:08:22.440> the<00:08:23.160> way<00:08:23.280> you 00:08:23.629 --> 00:08:23.639 align:start position:0% formalism are very important the way you 00:08:23.639 --> 00:08:26.749 align:start position:0% formalism are very important the way you type<00:08:23.879> your<00:08:24.599> processes<00:08:25.199> changes<00:08:26.099> what<00:08:26.340> you<00:08:26.639> can 00:08:26.749 --> 00:08:26.759 align:start position:0% type your processes changes what you can 00:08:26.759 --> 00:08:28.969 align:start position:0% type your processes changes what you can and<00:08:27.120> cannot<00:08:27.479> compose 00:08:28.969 --> 00:08:28.979 align:start position:0% and cannot compose 00:08:28.979 --> 00:08:32.029 align:start position:0% and cannot compose okay<00:08:29.639> as<00:08:30.479> an<00:08:30.660> example<00:08:30.960> imagine<00:08:31.440> that<00:08:31.740> you<00:08:31.919> have 00:08:32.029 --> 00:08:32.039 align:start position:0% okay as an example imagine that you have 00:08:32.039 --> 00:08:34.490 align:start position:0% okay as an example imagine that you have a<00:08:32.159> car<00:08:32.279> right<00:08:32.760> you<00:08:33.240> have 00:08:34.490 --> 00:08:34.500 align:start position:0% a car right you have 00:08:34.500 --> 00:08:38.230 align:start position:0% a car right you have the<00:08:35.159> wheel<00:08:35.399> and<00:08:36.180> the<00:08:36.419> shaft<00:08:36.779> and<00:08:37.500> the<00:08:37.680> gas<00:08:37.860> tank 00:08:38.230 --> 00:08:38.240 align:start position:0% the wheel and the shaft and the gas tank 00:08:38.240 --> 00:08:41.149 align:start position:0% the wheel and the shaft and the gas tank and<00:08:39.240> you<00:08:39.360> could<00:08:39.479> see<00:08:39.719> this<00:08:39.959> as<00:08:40.200> a<00:08:40.380> process<00:08:40.680> that 00:08:41.149 --> 00:08:41.159 align:start position:0% and you could see this as a process that 00:08:41.159 --> 00:08:43.010 align:start position:0% and you could see this as a process that takes<00:08:41.399> some<00:08:41.640> inputs<00:08:42.120> for<00:08:42.360> instance<00:08:42.599> I<00:08:42.839> don't 00:08:43.010 --> 00:08:43.020 align:start position:0% takes some inputs for instance I don't 00:08:43.020 --> 00:08:47.269 align:start position:0% takes some inputs for instance I don't know<00:08:43.159> fuel<00:08:44.180> or<00:08:45.180> and<00:08:45.720> Human<00:08:46.320> Action<00:08:46.800> and 00:08:47.269 --> 00:08:47.279 align:start position:0% know fuel or and Human Action and 00:08:47.279 --> 00:08:50.150 align:start position:0% know fuel or and Human Action and produces<00:08:47.760> heat<00:08:48.300> and<00:08:48.839> motion 00:08:50.150 --> 00:08:50.160 align:start position:0% produces heat and motion 00:08:50.160 --> 00:08:52.250 align:start position:0% produces heat and motion but<00:08:50.519> when<00:08:50.700> you<00:08:50.820> look<00:08:50.940> very<00:08:51.240> carefully<00:08:51.660> you<00:08:52.080> see 00:08:52.250 --> 00:08:52.260 align:start position:0% but when you look very carefully you see 00:08:52.260 --> 00:08:55.130 align:start position:0% but when you look very carefully you see that<00:08:52.500> you<00:08:53.040> could<00:08:53.160> pour<00:08:53.459> any<00:08:54.060> liquid<00:08:54.540> in<00:08:55.019> your 00:08:55.130 --> 00:08:55.140 align:start position:0% that you could pour any liquid in your 00:08:55.140 --> 00:08:57.410 align:start position:0% that you could pour any liquid in your car<00:08:55.320> right<00:08:55.800> like 00:08:57.410 --> 00:08:57.420 align:start position:0% car right like 00:08:57.420 --> 00:09:00.650 align:start position:0% car right like the<00:08:58.080> gas<00:08:58.260> tank<00:08:58.500> won't<00:08:58.980> complain<00:08:59.580> if<00:09:00.360> you<00:09:00.480> fill 00:09:00.650 --> 00:09:00.660 align:start position:0% the gas tank won't complain if you fill 00:09:00.660 --> 00:09:02.150 align:start position:0% the gas tank won't complain if you fill it<00:09:00.839> with<00:09:01.080> water 00:09:02.150 --> 00:09:02.160 align:start position:0% it with water 00:09:02.160 --> 00:09:04.750 align:start position:0% it with water clearly<00:09:02.940> the<00:09:03.060> engine<00:09:03.180> will<00:09:03.600> though 00:09:04.750 --> 00:09:04.760 align:start position:0% clearly the engine will though 00:09:04.760 --> 00:09:08.449 align:start position:0% clearly the engine will though and<00:09:05.760> basically<00:09:06.360> from<00:09:06.779> this<00:09:07.019> you<00:09:07.320> can 00:09:08.449 --> 00:09:08.459 align:start position:0% and basically from this you can 00:09:08.459 --> 00:09:11.990 align:start position:0% and basically from this you can you<00:09:09.000> know<00:09:09.060> infer<00:09:09.720> that<00:09:10.200> the<00:09:10.980> problem<00:09:11.160> here<00:09:11.580> is 00:09:11.990 --> 00:09:12.000 align:start position:0% you know infer that the problem here is 00:09:12.000 --> 00:09:15.829 align:start position:0% you know infer that the problem here is that<00:09:12.240> the<00:09:12.540> type<00:09:12.839> of<00:09:13.680> input<00:09:14.040> of<00:09:14.580> our<00:09:14.760> process<00:09:15.180> is 00:09:15.829 --> 00:09:15.839 align:start position:0% that the type of input of our process is 00:09:15.839 --> 00:09:17.110 align:start position:0% that the type of input of our process is to<00:09:16.019> General 00:09:17.110 --> 00:09:17.120 align:start position:0% to General 00:09:17.120 --> 00:09:20.269 align:start position:0% to General and<00:09:18.120> it<00:09:18.300> allows<00:09:18.720> you<00:09:18.779> to<00:09:19.200> fiddle<00:09:19.920> with<00:09:20.040> the 00:09:20.269 --> 00:09:20.279 align:start position:0% and it allows you to fiddle with the 00:09:20.279 --> 00:09:22.550 align:start position:0% and it allows you to fiddle with the process<00:09:20.600> in<00:09:21.600> a<00:09:21.720> way<00:09:21.839> that<00:09:22.080> produces 00:09:22.550 --> 00:09:22.560 align:start position:0% process in a way that produces 00:09:22.560 --> 00:09:25.730 align:start position:0% process in a way that produces unintended<00:09:23.399> Behavior<00:09:24.420> another<00:09:24.839> example<00:09:25.440> that 00:09:25.730 --> 00:09:25.740 align:start position:0% unintended Behavior another example that 00:09:25.740 --> 00:09:29.150 align:start position:0% unintended Behavior another example that I<00:09:26.040> like<00:09:26.820> is<00:09:27.360> imagine<00:09:27.720> a<00:09:28.200> socket<00:09:28.560> in<00:09:28.920> the<00:09:29.040> wall 00:09:29.150 --> 00:09:29.160 align:start position:0% I like is imagine a socket in the wall 00:09:29.160 --> 00:09:32.030 align:start position:0% I like is imagine a socket in the wall you<00:09:29.760> can<00:09:29.820> put<00:09:30.060> a<00:09:30.300> plug<00:09:30.480> into<00:09:30.959> it 00:09:32.030 --> 00:09:32.040 align:start position:0% you can put a plug into it 00:09:32.040 --> 00:09:34.070 align:start position:0% you can put a plug into it and<00:09:32.820> you<00:09:33.000> know<00:09:33.060> use<00:09:33.300> any<00:09:33.540> electronic 00:09:34.070 --> 00:09:34.080 align:start position:0% and you know use any electronic 00:09:34.080 --> 00:09:37.070 align:start position:0% and you know use any electronic Appliance<00:09:34.560> but<00:09:35.519> if<00:09:35.820> you<00:09:36.060> have<00:09:36.480> a<00:09:36.839> couple<00:09:36.899> of 00:09:37.070 --> 00:09:37.080 align:start position:0% Appliance but if you have a couple of 00:09:37.080 --> 00:09:39.949 align:start position:0% Appliance but if you have a couple of nails<00:09:37.380> you<00:09:38.339> can<00:09:38.459> also<00:09:38.640> stick<00:09:38.820> the<00:09:39.060> nails<00:09:39.240> in 00:09:39.949 --> 00:09:39.959 align:start position:0% nails you can also stick the nails in 00:09:39.959 --> 00:09:42.650 align:start position:0% nails you can also stick the nails in the<00:09:40.080> socket<00:09:40.920> and<00:09:41.459> what<00:09:41.580> you<00:09:41.760> go<00:09:41.940> what<00:09:42.240> you<00:09:42.480> get 00:09:42.650 --> 00:09:42.660 align:start position:0% the socket and what you go what you get 00:09:42.660 --> 00:09:46.190 align:start position:0% the socket and what you go what you get is<00:09:43.019> emerging<00:09:43.740> behavior<00:09:44.160> all<00:09:45.120> over<00:09:45.300> you<00:09:45.600> and 00:09:46.190 --> 00:09:46.200 align:start position:0% is emerging behavior all over you and 00:09:46.200 --> 00:09:47.810 align:start position:0% is emerging behavior all over you and very<00:09:46.440> painful 00:09:47.810 --> 00:09:47.820 align:start position:0% very painful 00:09:47.820 --> 00:09:49.550 align:start position:0% very painful so 00:09:49.550 --> 00:09:49.560 align:start position:0% so 00:09:49.560 --> 00:09:52.550 align:start position:0% so the<00:09:50.339> important<00:09:50.640> thing<00:09:50.940> here<00:09:51.240> is<00:09:51.480> this<00:09:51.959> is<00:09:52.140> the 00:09:52.550 --> 00:09:52.560 align:start position:0% the important thing here is this is the 00:09:52.560 --> 00:09:56.630 align:start position:0% the important thing here is this is the main<00:09:53.160> message<00:09:53.459> of<00:09:53.880> compositionality<00:09:54.839> so<00:09:56.220> when 00:09:56.630 --> 00:09:56.640 align:start position:0% main message of compositionality so when 00:09:56.640 --> 00:09:59.509 align:start position:0% main message of compositionality so when you<00:09:56.760> look<00:09:56.880> at<00:09:57.060> this<00:09:57.360> process<00:09:57.779> like<00:09:58.620> the<00:09:58.920> socket 00:09:59.509 --> 00:09:59.519 align:start position:0% you look at this process like the socket 00:09:59.519 --> 00:10:01.550 align:start position:0% you look at this process like the socket and<00:10:00.000> plug<00:10:00.300> process 00:10:01.550 --> 00:10:01.560 align:start position:0% and plug process 00:10:01.560 --> 00:10:04.370 align:start position:0% and plug process you<00:10:02.279> can<00:10:02.399> start<00:10:02.640> asking<00:10:03.240> what<00:10:04.019> are<00:10:04.200> the 00:10:04.370 --> 00:10:04.380 align:start position:0% you can start asking what are the 00:10:04.380 --> 00:10:07.550 align:start position:0% you can start asking what are the properties<00:10:04.940> that<00:10:05.940> are<00:10:06.300> preserved<00:10:06.899> when<00:10:07.380> I 00:10:07.550 --> 00:10:07.560 align:start position:0% properties that are preserved when I 00:10:07.560 --> 00:10:09.650 align:start position:0% properties that are preserved when I compose<00:10:07.980> these<00:10:08.399> processes<00:10:08.820> together 00:10:09.650 --> 00:10:09.660 align:start position:0% compose these processes together 00:10:09.660 --> 00:10:13.190 align:start position:0% compose these processes together so<00:10:10.380> physically<00:10:10.980> sticking<00:10:11.880> the<00:10:12.180> nails<00:10:12.420> in<00:10:13.019> the 00:10:13.190 --> 00:10:13.200 align:start position:0% so physically sticking the nails in the 00:10:13.200 --> 00:10:14.990 align:start position:0% so physically sticking the nails in the socket<00:10:13.560> makes<00:10:13.860> total<00:10:14.279> sense<00:10:14.459> because<00:10:14.760> they 00:10:14.990 --> 00:10:15.000 align:start position:0% socket makes total sense because they 00:10:15.000 --> 00:10:15.949 align:start position:0% socket makes total sense because they fit 00:10:15.949 --> 00:10:15.959 align:start position:0% fit 00:10:15.959 --> 00:10:17.930 align:start position:0% fit but<00:10:16.560> if<00:10:16.740> you're<00:10:16.860> looking<00:10:17.100> at<00:10:17.399> things<00:10:17.580> through 00:10:17.930 --> 00:10:17.940 align:start position:0% but if you're looking at things through 00:10:17.940 --> 00:10:21.110 align:start position:0% but if you're looking at things through the<00:10:18.180> lens<00:10:18.360> of<00:10:18.660> safety<00:10:19.140> regulations<00:10:19.940> you<00:10:20.940> see 00:10:21.110 --> 00:10:21.120 align:start position:0% the lens of safety regulations you see 00:10:21.120 --> 00:10:23.509 align:start position:0% the lens of safety regulations you see that<00:10:21.360> a<00:10:21.779> nail<00:10:21.959> can<00:10:22.260> be<00:10:22.380> safe<00:10:22.560> can<00:10:22.920> you<00:10:23.100> know<00:10:23.220> be 00:10:23.509 --> 00:10:23.519 align:start position:0% that a nail can be safe can you know be 00:10:23.519 --> 00:10:26.150 align:start position:0% that a nail can be safe can you know be certified<00:10:24.420> with<00:10:25.080> whatever<00:10:25.320> standard<00:10:25.860> your 00:10:26.150 --> 00:10:26.160 align:start position:0% certified with whatever standard your 00:10:26.160 --> 00:10:27.230 align:start position:0% certified with whatever standard your country<00:10:26.339> has 00:10:27.230 --> 00:10:27.240 align:start position:0% country has 00:10:27.240 --> 00:10:30.230 align:start position:0% country has same<00:10:27.899> thing<00:10:28.140> for<00:10:28.680> the<00:10:29.220> socket<00:10:29.580> but<00:10:29.880> when<00:10:30.120> you 00:10:30.230 --> 00:10:30.240 align:start position:0% same thing for the socket but when you 00:10:30.240 --> 00:10:32.449 align:start position:0% same thing for the socket but when you compose<00:10:30.660> them<00:10:30.899> suddenly<00:10:31.620> you<00:10:31.920> have<00:10:32.040> a<00:10:32.339> very 00:10:32.449 --> 00:10:32.459 align:start position:0% compose them suddenly you have a very 00:10:32.459 --> 00:10:34.810 align:start position:0% compose them suddenly you have a very very<00:10:32.700> unsafe<00:10:33.180> system 00:10:34.810 --> 00:10:34.820 align:start position:0% very unsafe system 00:10:34.820 --> 00:10:37.130 align:start position:0% very unsafe system compositionality<00:10:35.820> is<00:10:35.940> exactly<00:10:36.480> the<00:10:36.720> art<00:10:36.899> of 00:10:37.130 --> 00:10:37.140 align:start position:0% compositionality is exactly the art of 00:10:37.140 --> 00:10:39.590 align:start position:0% compositionality is exactly the art of choosing<00:10:37.560> these<00:10:37.860> types<00:10:38.220> in<00:10:38.940> a<00:10:39.060> way<00:10:39.240> that 00:10:39.590 --> 00:10:39.600 align:start position:0% choosing these types in a way that 00:10:39.600 --> 00:10:42.710 align:start position:0% choosing these types in a way that emergent<00:10:40.200> behavior<00:10:40.680> is<00:10:41.160> averted<00:10:41.820> as<00:10:42.240> much<00:10:42.420> as 00:10:42.710 --> 00:10:42.720 align:start position:0% emergent behavior is averted as much as 00:10:42.720 --> 00:10:44.930 align:start position:0% emergent behavior is averted as much as possible<00:10:43.560> so<00:10:43.980> that<00:10:44.100> when<00:10:44.279> you<00:10:44.399> compose<00:10:44.700> things 00:10:44.930 --> 00:10:44.940 align:start position:0% possible so that when you compose things 00:10:44.940 --> 00:10:46.970 align:start position:0% possible so that when you compose things you<00:10:45.180> know<00:10:45.360> precisely<00:10:45.959> what<00:10:46.260> is<00:10:46.380> going<00:10:46.500> what<00:10:46.860> we 00:10:46.970 --> 00:10:46.980 align:start position:0% you know precisely what is going what we 00:10:46.980 --> 00:10:48.949 align:start position:0% you know precisely what is going what we are<00:10:47.100> going<00:10:47.220> to<00:10:47.339> get 00:10:48.949 --> 00:10:48.959 align:start position:0% are going to get 00:10:48.959 --> 00:10:51.190 align:start position:0% are going to get now<00:10:49.800> under<00:10:50.220> the<00:10:50.459> hood 00:10:51.190 --> 00:10:51.200 align:start position:0% now under the hood 00:10:51.200 --> 00:10:53.990 align:start position:0% now under the hood compositionality<00:10:52.200> is<00:10:53.040> based<00:10:53.399> on<00:10:53.579> a<00:10:53.700> theory 00:10:53.990 --> 00:10:54.000 align:start position:0% compositionality is based on a theory 00:10:54.000 --> 00:10:56.750 align:start position:0% compositionality is based on a theory called<00:10:54.180> category<00:10:54.720> Theory<00:10:55.140> this<00:10:55.980> was<00:10:56.220> invented 00:10:56.750 --> 00:10:56.760 align:start position:0% called category Theory this was invented 00:10:56.760 --> 00:11:00.769 align:start position:0% called category Theory this was invented in<00:10:57.240> 1942<00:10:58.079> and<00:10:58.440> had<00:10:58.680> a<00:10:58.920> monstrous<00:10:59.339> impact<00:11:00.000> on 00:11:00.769 --> 00:11:00.779 align:start position:0% in 1942 and had a monstrous impact on 00:11:00.779 --> 00:11:03.290 align:start position:0% in 1942 and had a monstrous impact on Modern<00:11:01.079> mathematics<00:11:01.880> essentially<00:11:02.880> you<00:11:03.180> can 00:11:03.290 --> 00:11:03.300 align:start position:0% Modern mathematics essentially you can 00:11:03.300 --> 00:11:05.930 align:start position:0% Modern mathematics essentially you can see<00:11:03.540> it<00:11:03.779> as<00:11:04.320> a<00:11:04.680> super<00:11:04.800> glue<00:11:05.220> of<00:11:05.339> mathematics 00:11:05.930 --> 00:11:05.940 align:start position:0% see it as a super glue of mathematics 00:11:05.940 --> 00:11:08.449 align:start position:0% see it as a super glue of mathematics that<00:11:06.779> describes<00:11:07.380> how<00:11:07.620> different<00:11:07.860> theories 00:11:08.449 --> 00:11:08.459 align:start position:0% that describes how different theories 00:11:08.459 --> 00:11:11.030 align:start position:0% that describes how different theories compose<00:11:09.360> and<00:11:09.720> interact 00:11:11.030 --> 00:11:11.040 align:start position:0% compose and interact 00:11:11.040 --> 00:11:14.269 align:start position:0% compose and interact basically<00:11:11.880> all<00:11:12.180> the<00:11:12.480> main<00:11:13.079> progress<00:11:13.560> in<00:11:13.980> you 00:11:14.269 --> 00:11:14.279 align:start position:0% basically all the main progress in you 00:11:14.279 --> 00:11:16.490 align:start position:0% basically all the main progress in you know<00:11:14.399> big<00:11:15.060> areas<00:11:15.480> of<00:11:15.720> mathematics<00:11:16.260> like 00:11:16.490 --> 00:11:16.500 align:start position:0% know big areas of mathematics like 00:11:16.500 --> 00:11:19.190 align:start position:0% know big areas of mathematics like algebraic<00:11:17.100> geometry<00:11:17.640> or<00:11:18.360> algebraic<00:11:18.899> topology 00:11:19.190 --> 00:11:19.200 align:start position:0% algebraic geometry or algebraic topology 00:11:19.200 --> 00:11:20.769 align:start position:0% algebraic geometry or algebraic topology come<00:11:19.620> from<00:11:19.800> here 00:11:20.769 --> 00:11:20.779 align:start position:0% come from here 00:11:20.779 --> 00:11:23.449 align:start position:0% come from here and<00:11:21.779> in<00:11:22.079> the<00:11:22.200> last<00:11:22.320> year<00:11:22.560> people<00:11:22.920> started 00:11:23.449 --> 00:11:23.459 align:start position:0% and in the last year people started 00:11:23.459 --> 00:11:25.670 align:start position:0% and in the last year people started realizing<00:11:23.940> that<00:11:24.240> this<00:11:24.420> thing<00:11:24.600> can<00:11:24.959> be<00:11:25.140> applied 00:11:25.670 --> 00:11:25.680 align:start position:0% realizing that this thing can be applied 00:11:25.680 --> 00:11:28.550 align:start position:0% realizing that this thing can be applied also<00:11:26.519> outside<00:11:27.060> of<00:11:27.360> mathematics<00:11:28.019> because 00:11:28.550 --> 00:11:28.560 align:start position:0% also outside of mathematics because 00:11:28.560 --> 00:11:31.130 align:start position:0% also outside of mathematics because again<00:11:28.800> it<00:11:29.220> embodies<00:11:29.700> this<00:11:29.940> perspective<00:11:30.480> that 00:11:31.130 --> 00:11:31.140 align:start position:0% again it embodies this perspective that 00:11:31.140 --> 00:11:33.230 align:start position:0% again it embodies this perspective that you<00:11:31.320> can<00:11:31.500> describe<00:11:32.040> things<00:11:32.279> but<00:11:32.579> looking<00:11:32.820> how 00:11:33.230 --> 00:11:33.240 align:start position:0% you can describe things but looking how 00:11:33.240 --> 00:11:36.230 align:start position:0% you can describe things but looking how they<00:11:33.779> behave<00:11:34.260> in<00:11:34.860> a<00:11:35.040> context 00:11:36.230 --> 00:11:36.240 align:start position:0% they behave in a context 00:11:36.240 --> 00:11:37.310 align:start position:0% they behave in a context so 00:11:37.310 --> 00:11:37.320 align:start position:0% so 00:11:37.320 --> 00:11:40.009 align:start position:0% so when<00:11:37.920> I<00:11:38.100> show<00:11:38.279> you<00:11:38.459> those<00:11:38.760> diagrams<00:11:39.360> what<00:11:39.839> I'm 00:11:40.009 --> 00:11:40.019 align:start position:0% when I show you those diagrams what I'm 00:11:40.019 --> 00:11:42.170 align:start position:0% when I show you those diagrams what I'm really<00:11:40.200> doing<00:11:40.500> I'm<00:11:40.980> always<00:11:41.220> speaking<00:11:41.880> a 00:11:42.170 --> 00:11:42.180 align:start position:0% really doing I'm always speaking a 00:11:42.180 --> 00:11:44.569 align:start position:0% really doing I'm always speaking a category<00:11:42.600> that<00:11:43.079> defines<00:11:43.500> the<00:11:43.740> universe<00:11:44.220> I'm 00:11:44.569 --> 00:11:44.579 align:start position:0% category that defines the universe I'm 00:11:44.579 --> 00:11:48.190 align:start position:0% category that defines the universe I'm working<00:11:44.880> on<00:11:45.120> and<00:11:45.660> working<00:11:45.899> in 00:11:48.190 --> 00:11:48.200 align:start position:0% working on and working in 00:11:48.200 --> 00:11:52.130 align:start position:0% working on and working in uh<00:11:49.200> let<00:11:49.560> me<00:11:49.740> just<00:11:50.459> dig<00:11:50.760> a<00:11:51.000> bit<00:11:51.120> deeper<00:11:51.660> into 00:11:52.130 --> 00:11:52.140 align:start position:0% uh let me just dig a bit deeper into 00:11:52.140 --> 00:11:53.870 align:start position:0% uh let me just dig a bit deeper into this<00:11:52.620> idea<00:11:52.980> so 00:11:53.870 --> 00:11:53.880 align:start position:0% this idea so 00:11:53.880 --> 00:11:55.850 align:start position:0% this idea so if<00:11:54.420> you<00:11:54.540> want<00:11:54.660> to<00:11:54.839> define<00:11:54.959> a<00:11:55.260> category<00:11:55.620> if 00:11:55.850 --> 00:11:55.860 align:start position:0% if you want to define a category if 00:11:55.860 --> 00:11:57.230 align:start position:0% if you want to define a category if you're<00:11:56.040> a<00:11:56.160> mathematician<00:11:56.700> you<00:11:56.940> want<00:11:57.060> to 00:11:57.230 --> 00:11:57.240 align:start position:0% you're a mathematician you want to 00:11:57.240 --> 00:11:59.630 align:start position:0% you're a mathematician you want to Define<00:11:57.360> it<00:11:57.720> formally<00:11:58.260> basically<00:11:59.160> you<00:11:59.339> have<00:11:59.519> to 00:11:59.630 --> 00:11:59.640 align:start position:0% Define it formally basically you have to 00:11:59.640 --> 00:12:01.730 align:start position:0% Define it formally basically you have to specify<00:12:00.240> various<00:12:00.779> entities<00:12:01.140> you<00:12:01.500> have<00:12:01.560> to 00:12:01.730 --> 00:12:01.740 align:start position:0% specify various entities you have to 00:12:01.740 --> 00:12:04.750 align:start position:0% specify various entities you have to specify<00:12:02.240> objects<00:12:03.240> that<00:12:03.959> correspond<00:12:04.500> to 00:12:04.750 --> 00:12:04.760 align:start position:0% specify objects that correspond to 00:12:04.760 --> 00:12:07.370 align:start position:0% specify objects that correspond to systems<00:12:05.760> in<00:12:06.120> the<00:12:06.300> pictures<00:12:06.600> I<00:12:07.019> showed<00:12:07.320> you 00:12:07.370 --> 00:12:07.380 align:start position:0% systems in the pictures I showed you 00:12:07.380 --> 00:12:10.790 align:start position:0% systems in the pictures I showed you before<00:12:07.620> so<00:12:08.399> objects<00:12:09.060> would<00:12:09.240> be<00:12:09.360> the<00:12:09.600> wires 00:12:10.790 --> 00:12:10.800 align:start position:0% before so objects would be the wires 00:12:10.800 --> 00:12:14.389 align:start position:0% before so objects would be the wires in<00:12:11.519> the<00:12:11.880> box<00:12:12.120> and<00:12:12.480> wire<00:12:12.720> pictures<00:12:13.140> you<00:12:14.040> have<00:12:14.160> to 00:12:14.389 --> 00:12:14.399 align:start position:0% in the box and wire pictures you have to 00:12:14.399 --> 00:12:16.670 align:start position:0% in the box and wire pictures you have to specify<00:12:14.839> morphisms<00:12:15.839> that<00:12:16.019> are<00:12:16.140> the<00:12:16.380> process 00:12:16.670 --> 00:12:16.680 align:start position:0% specify morphisms that are the process 00:12:16.680 --> 00:12:19.490 align:start position:0% specify morphisms that are the process the<00:12:16.980> boxes<00:12:17.459> that<00:12:17.700> transform<00:12:18.380> objects<00:12:19.380> into 00:12:19.490 --> 00:12:19.500 align:start position:0% the boxes that transform objects into 00:12:19.500 --> 00:12:20.930 align:start position:0% the boxes that transform objects into objects 00:12:20.930 --> 00:12:20.940 align:start position:0% objects 00:12:20.940 --> 00:12:23.690 align:start position:0% objects you<00:12:21.779> are<00:12:21.959> required<00:12:22.380> to<00:12:22.560> specify<00:12:23.040> identities 00:12:23.690 --> 00:12:23.700 align:start position:0% you are required to specify identities 00:12:23.700 --> 00:12:26.630 align:start position:0% you are required to specify identities so<00:12:24.060> for<00:12:24.300> each<00:12:24.540> system<00:12:24.899> you<00:12:25.560> need<00:12:25.740> to<00:12:25.980> have<00:12:26.220> a 00:12:26.630 --> 00:12:26.640 align:start position:0% so for each system you need to have a 00:12:26.640 --> 00:12:28.790 align:start position:0% so for each system you need to have a process<00:12:26.940> that<00:12:27.300> doesn't<00:12:27.480> do<00:12:27.839> anything 00:12:28.790 --> 00:12:28.800 align:start position:0% process that doesn't do anything 00:12:28.800 --> 00:12:31.610 align:start position:0% process that doesn't do anything to<00:12:29.459> it<00:12:29.700> and<00:12:30.480> then<00:12:30.600> you<00:12:30.899> basically<00:12:31.200> have<00:12:31.380> to 00:12:31.610 --> 00:12:31.620 align:start position:0% to it and then you basically have to 00:12:31.620 --> 00:12:35.150 align:start position:0% to it and then you basically have to specify<00:12:32.100> a<00:12:32.579> composition<00:12:33.000> law<00:12:33.839> uh<00:12:34.740> a<00:12:34.740> recipe 00:12:35.150 --> 00:12:35.160 align:start position:0% specify a composition law uh a recipe 00:12:35.160 --> 00:12:37.250 align:start position:0% specify a composition law uh a recipe that<00:12:35.640> tells<00:12:35.940> you<00:12:36.000> what<00:12:36.300> happens<00:12:36.480> when<00:12:37.079> you 00:12:37.250 --> 00:12:37.260 align:start position:0% that tells you what happens when you 00:12:37.260 --> 00:12:40.670 align:start position:0% that tells you what happens when you compose<00:12:37.620> processes<00:12:38.279> together 00:12:40.670 --> 00:12:40.680 align:start position:0% 00:12:40.680 --> 00:12:43.370 align:start position:0% uh<00:12:41.459> let<00:12:41.700> me<00:12:41.820> give<00:12:42.060> you<00:12:42.240> some<00:12:42.720> examples<00:12:43.139> of 00:12:43.370 --> 00:12:43.380 align:start position:0% uh let me give you some examples of 00:12:43.380 --> 00:12:45.970 align:start position:0% uh let me give you some examples of categories<00:12:43.920> that<00:12:44.339> are<00:12:44.579> probably<00:12:44.760> familiar<00:12:45.300> to 00:12:45.970 --> 00:12:45.980 align:start position:0% categories that are probably familiar to 00:12:45.980 --> 00:12:48.949 align:start position:0% categories that are probably familiar to uh<00:12:46.980> I<00:12:47.339> hope<00:12:47.519> as<00:12:48.000> many<00:12:48.240> people<00:12:48.420> as<00:12:48.660> possible 00:12:48.949 --> 00:12:48.959 align:start position:0% uh I hope as many people as possible 00:12:48.959 --> 00:12:52.009 align:start position:0% uh I hope as many people as possible here<00:12:49.800> there's<00:12:50.279> a<00:12:50.519> category<00:12:50.820> called<00:12:51.000> set<00:12:51.300> where 00:12:52.009 --> 00:12:52.019 align:start position:0% here there's a category called set where 00:12:52.019 --> 00:12:56.210 align:start position:0% here there's a category called set where your<00:12:52.200> objects<00:12:52.680> are<00:12:52.940> sets<00:12:53.940> and<00:12:54.720> your<00:12:55.260> morphisms 00:12:56.210 --> 00:12:56.220 align:start position:0% your objects are sets and your morphisms 00:12:56.220 --> 00:12:59.150 align:start position:0% your objects are sets and your morphisms so<00:12:57.120> your<00:12:57.660> processes<00:12:58.139> are<00:12:58.380> functions<00:12:58.860> between 00:12:59.150 --> 00:12:59.160 align:start position:0% so your processes are functions between 00:12:59.160 --> 00:13:01.970 align:start position:0% so your processes are functions between sets<00:13:00.240> there<00:13:00.839> is<00:13:00.959> always<00:13:01.139> a<00:13:01.440> function<00:13:01.680> that 00:13:01.970 --> 00:13:01.980 align:start position:0% sets there is always a function that 00:13:01.980 --> 00:13:04.790 align:start position:0% sets there is always a function that doesn't<00:13:02.160> do<00:13:02.399> anything<00:13:02.639> and<00:13:03.600> you<00:13:03.959> can<00:13:04.139> pipe 00:13:04.790 --> 00:13:04.800 align:start position:0% doesn't do anything and you can pipe 00:13:04.800 --> 00:13:06.829 align:start position:0% doesn't do anything and you can pipe functions<00:13:05.459> into<00:13:05.700> each<00:13:05.940> other 00:13:06.829 --> 00:13:06.839 align:start position:0% functions into each other 00:13:06.839 --> 00:13:08.690 align:start position:0% functions into each other for<00:13:07.380> programmers<00:13:07.980> there<00:13:08.279> is<00:13:08.459> another 00:13:08.690 --> 00:13:08.700 align:start position:0% for programmers there is another 00:13:08.700 --> 00:13:12.350 align:start position:0% for programmers there is another category<00:13:09.300> called<00:13:09.480> Data<00:13:10.440> where<00:13:11.399> your<00:13:11.820> objects 00:13:12.350 --> 00:13:12.360 align:start position:0% category called Data where your objects 00:13:12.360 --> 00:13:15.710 align:start position:0% category called Data where your objects are<00:13:12.660> data<00:13:13.139> types<00:13:13.500> and<00:13:14.160> your<00:13:14.579> programs<00:13:15.180> are 00:13:15.710 --> 00:13:15.720 align:start position:0% are data types and your programs are 00:13:15.720 --> 00:13:18.650 align:start position:0% are data types and your programs are programs<00:13:16.440> that<00:13:16.740> turn<00:13:16.980> data<00:13:17.639> types<00:13:17.940> into<00:13:18.180> data 00:13:18.650 --> 00:13:18.660 align:start position:0% programs that turn data types into data 00:13:18.660 --> 00:13:19.970 align:start position:0% programs that turn data types into data types 00:13:19.970 --> 00:13:19.980 align:start position:0% types 00:13:19.980 --> 00:13:22.790 align:start position:0% types again<00:13:20.519> you<00:13:20.880> can<00:13:20.940> compose<00:13:21.540> programs<00:13:22.380> this<00:13:22.620> is 00:13:22.790 --> 00:13:22.800 align:start position:0% again you can compose programs this is 00:13:22.800 --> 00:13:25.490 align:start position:0% again you can compose programs this is basically<00:13:23.100> functional<00:13:23.760> programming<00:13:24.360> Style 00:13:25.490 --> 00:13:25.500 align:start position:0% basically functional programming Style 00:13:25.500 --> 00:13:28.610 align:start position:0% basically functional programming Style programming<00:13:26.459> you<00:13:26.820> can<00:13:26.940> pipe<00:13:27.720> you<00:13:28.260> know<00:13:28.320> the 00:13:28.610 --> 00:13:28.620 align:start position:0% programming you can pipe you know the 00:13:28.620 --> 00:13:30.470 align:start position:0% programming you can pipe you know the output<00:13:28.920> of<00:13:29.100> a<00:13:29.279> program<00:13:29.459> into<00:13:29.820> the<00:13:30.060> input<00:13:30.300> of 00:13:30.470 --> 00:13:30.480 align:start position:0% output of a program into the input of 00:13:30.480 --> 00:13:33.590 align:start position:0% output of a program into the input of another<00:13:30.660> program<00:13:31.019> if<00:13:31.620> the<00:13:31.860> data<00:13:32.160> type<00:13:32.279> matches 00:13:33.590 --> 00:13:33.600 align:start position:0% another program if the data type matches 00:13:33.600 --> 00:13:36.050 align:start position:0% another program if the data type matches and<00:13:34.500> you<00:13:34.800> are<00:13:34.980> also<00:13:35.279> a<00:13:35.399> program<00:13:35.519> that<00:13:35.820> just 00:13:36.050 --> 00:13:36.060 align:start position:0% and you are also a program that just 00:13:36.060 --> 00:13:38.569 align:start position:0% and you are also a program that just Returns<00:13:36.480> the<00:13:36.600> input<00:13:36.899> without<00:13:37.139> doing<00:13:37.440> anything 00:13:38.569 --> 00:13:38.579 align:start position:0% Returns the input without doing anything 00:13:38.579 --> 00:13:41.509 align:start position:0% Returns the input without doing anything so<00:13:39.600> what<00:13:40.139> is<00:13:40.260> the<00:13:40.500> difference<00:13:40.680> between<00:13:41.100> these 00:13:41.509 --> 00:13:41.519 align:start position:0% so what is the difference between these 00:13:41.519 --> 00:13:43.250 align:start position:0% so what is the difference between these two<00:13:41.639> categories 00:13:43.250 --> 00:13:43.260 align:start position:0% two categories 00:13:43.260 --> 00:13:47.150 align:start position:0% two categories well<00:13:43.860> set<00:13:44.760> offers<00:13:45.360> an<00:13:45.899> intention<00:13:46.380> sorry<00:13:46.920> an 00:13:47.150 --> 00:13:47.160 align:start position:0% well set offers an intention sorry an 00:13:47.160 --> 00:13:49.850 align:start position:0% well set offers an intention sorry an extensional<00:13:47.760> perspective<00:13:48.360> what<00:13:49.260> it<00:13:49.380> means<00:13:49.680> is 00:13:49.850 --> 00:13:49.860 align:start position:0% extensional perspective what it means is 00:13:49.860 --> 00:13:52.730 align:start position:0% extensional perspective what it means is that<00:13:50.160> for<00:13:50.579> instance<00:13:50.880> if<00:13:51.839> I<00:13:51.959> consider<00:13:52.320> the<00:13:52.500> set 00:13:52.730 --> 00:13:52.740 align:start position:0% that for instance if I consider the set 00:13:52.740 --> 00:13:55.250 align:start position:0% that for instance if I consider the set of<00:13:52.920> integer<00:13:53.339> numbers<00:13:53.579> I<00:13:54.240> have<00:13:54.480> exactly<00:13:54.899> one 00:13:55.250 --> 00:13:55.260 align:start position:0% of integer numbers I have exactly one 00:13:55.260 --> 00:13:58.910 align:start position:0% of integer numbers I have exactly one function<00:13:55.620> that<00:13:56.399> takes<00:13:56.579> a<00:13:56.880> number<00:13:57.060> and<00:13:57.540> adds<00:13:58.019> n 00:13:58.910 --> 00:13:58.920 align:start position:0% function that takes a number and adds n 00:13:58.920 --> 00:14:00.470 align:start position:0% function that takes a number and adds n to<00:13:59.279> it 00:14:00.470 --> 00:14:00.480 align:start position:0% to it 00:14:00.480 --> 00:14:03.590 align:start position:0% to it on<00:14:01.019> the<00:14:01.139> contrary<00:14:01.500> in<00:14:01.800> data<00:14:02.160> I<00:14:02.700> have<00:14:02.940> multiple 00:14:03.590 --> 00:14:03.600 align:start position:0% on the contrary in data I have multiple 00:14:03.600 --> 00:14:07.129 align:start position:0% on the contrary in data I have multiple ways<00:14:04.200> of<00:14:04.560> either<00:14:04.980> specify<00:14:05.639> what<00:14:06.600> integer 00:14:07.129 --> 00:14:07.139 align:start position:0% ways of either specify what integer 00:14:07.139 --> 00:14:10.930 align:start position:0% ways of either specify what integer numbers<00:14:07.380> are<00:14:07.860> and<00:14:08.700> I<00:14:08.880> have<00:14:09.060> multiple<00:14:09.899> programs 00:14:10.930 --> 00:14:10.940 align:start position:0% numbers are and I have multiple programs 00:14:10.940 --> 00:14:14.629 align:start position:0% numbers are and I have multiple programs that<00:14:11.940> sum<00:14:12.420> n<00:14:12.720> to<00:14:13.019> your<00:14:13.200> term<00:14:13.440> in<00:14:14.040> here<00:14:14.279> I<00:14:14.519> just 00:14:14.629 --> 00:14:14.639 align:start position:0% that sum n to your term in here I just 00:14:14.639 --> 00:14:17.810 align:start position:0% that sum n to your term in here I just brought<00:14:15.180> two<00:14:15.839> of<00:14:15.959> them<00:14:16.160> but<00:14:17.160> in<00:14:17.339> general<00:14:17.519> you 00:14:17.810 --> 00:14:17.820 align:start position:0% brought two of them but in general you 00:14:17.820 --> 00:14:21.129 align:start position:0% brought two of them but in general you see<00:14:17.940> that<00:14:18.120> in<00:14:18.360> the<00:14:18.839> car<00:14:19.200> in<00:14:19.500> the<00:14:19.680> category<00:14:20.160> data 00:14:21.129 --> 00:14:21.139 align:start position:0% see that in the car in the category data 00:14:21.139 --> 00:14:24.290 align:start position:0% see that in the car in the category data the<00:14:22.160> formalization<00:14:23.160> the<00:14:23.639> implementation 00:14:24.290 --> 00:14:24.300 align:start position:0% the formalization the implementation 00:14:24.300 --> 00:14:26.050 align:start position:0% the formalization the implementation matters 00:14:26.050 --> 00:14:26.060 align:start position:0% matters 00:14:26.060 --> 00:14:29.810 align:start position:0% matters so<00:14:27.060> these<00:14:27.420> two<00:14:27.540> categories<00:14:28.019> offer<00:14:28.860> very 00:14:29.810 --> 00:14:29.820 align:start position:0% so these two categories offer very 00:14:29.820 --> 00:14:31.670 align:start position:0% so these two categories offer very different<00:14:30.000> views<00:14:30.540> on<00:14:30.720> the<00:14:30.899> same<00:14:31.019> phenomenon 00:14:31.670 --> 00:14:31.680 align:start position:0% different views on the same phenomenon 00:14:31.680 --> 00:14:33.470 align:start position:0% different views on the same phenomenon in<00:14:31.920> one<00:14:32.220> case<00:14:32.399> you're<00:14:32.700> saying<00:14:33.060> I'm<00:14:33.240> only 00:14:33.470 --> 00:14:33.480 align:start position:0% in one case you're saying I'm only 00:14:33.480 --> 00:14:35.389 align:start position:0% in one case you're saying I'm only interested<00:14:33.839> about<00:14:34.079> behavior<00:14:34.680> I'm<00:14:35.160> not 00:14:35.389 --> 00:14:35.399 align:start position:0% interested about behavior I'm not 00:14:35.399 --> 00:14:37.550 align:start position:0% interested about behavior I'm not interested<00:14:35.760> about<00:14:36.000> the<00:14:36.480> inner<00:14:36.959> workings<00:14:37.320> of 00:14:37.550 --> 00:14:37.560 align:start position:0% interested about the inner workings of 00:14:37.560 --> 00:14:39.710 align:start position:0% interested about the inner workings of these<00:14:37.740> functions<00:14:38.100> in<00:14:38.760> the<00:14:38.880> other<00:14:39.060> one<00:14:39.240> you<00:14:39.540> say 00:14:39.710 --> 00:14:39.720 align:start position:0% these functions in the other one you say 00:14:39.720 --> 00:14:42.050 align:start position:0% these functions in the other one you say no<00:14:39.839> I<00:14:40.079> do<00:14:40.260> and<00:14:40.560> I<00:14:40.680> distinguish<00:14:41.279> two<00:14:41.519> processes 00:14:42.050 --> 00:14:42.060 align:start position:0% no I do and I distinguish two processes 00:14:42.060 --> 00:14:45.170 align:start position:0% no I do and I distinguish two processes they<00:14:42.480> could<00:14:42.720> uh<00:14:43.380> emit<00:14:44.040> the<00:14:44.339> same<00:14:44.459> output<00:14:44.940> on 00:14:45.170 --> 00:14:45.180 align:start position:0% they could uh emit the same output on 00:14:45.180 --> 00:14:47.509 align:start position:0% they could uh emit the same output on the<00:14:45.300> same<00:14:45.420> input<00:14:45.779> but<00:14:46.560> I<00:14:46.740> want<00:14:46.860> to<00:14:47.040> keep<00:14:47.279> them 00:14:47.509 --> 00:14:47.519 align:start position:0% the same input but I want to keep them 00:14:47.519 --> 00:14:49.129 align:start position:0% the same input but I want to keep them distinguished 00:14:49.129 --> 00:14:49.139 align:start position:0% distinguished 00:14:49.139 --> 00:14:51.949 align:start position:0% distinguished now<00:14:49.800> the<00:14:50.519> cool<00:14:50.699> thing<00:14:50.880> about<00:14:51.060> category<00:14:51.600> theory 00:14:51.949 --> 00:14:51.959 align:start position:0% now the cool thing about category theory 00:14:51.959 --> 00:14:54.290 align:start position:0% now the cool thing about category theory is<00:14:52.079> that<00:14:52.199> you<00:14:52.440> can<00:14:52.560> connect<00:14:53.180> these<00:14:54.180> different 00:14:54.290 --> 00:14:54.300 align:start position:0% is that you can connect these different 00:14:54.300 --> 00:14:56.629 align:start position:0% is that you can connect these different perspectives<00:14:54.959> there<00:14:55.920> is<00:14:56.040> a<00:14:56.160> notion<00:14:56.399> called 00:14:56.629 --> 00:14:56.639 align:start position:0% perspectives there is a notion called 00:14:56.639 --> 00:14:59.210 align:start position:0% perspectives there is a notion called functor<00:14:57.180> that<00:14:57.899> turns<00:14:58.260> a<00:14:58.440> category<00:14:58.860> into 00:14:59.210 --> 00:14:59.220 align:start position:0% functor that turns a category into 00:14:59.220 --> 00:15:02.389 align:start position:0% functor that turns a category into another<00:14:59.519> category<00:15:00.600> in<00:15:01.380> our<00:15:01.620> framework<00:15:02.040> this 00:15:02.389 --> 00:15:02.399 align:start position:0% another category in our framework this 00:15:02.399 --> 00:15:04.430 align:start position:0% another category in our framework this would<00:15:02.519> be<00:15:02.699> a<00:15:03.060> box<00:15:03.300> that<00:15:03.720> is<00:15:03.839> sort<00:15:04.199> of<00:15:04.320> like 00:15:04.430 --> 00:15:04.440 align:start position:0% would be a box that is sort of like 00:15:04.440 --> 00:15:07.189 align:start position:0% would be a box that is sort of like level<00:15:04.740> two<00:15:05.040> box<00:15:05.339> that<00:15:06.060> allows<00:15:06.420> you<00:15:06.480> to<00:15:06.779> change 00:15:07.189 --> 00:15:07.199 align:start position:0% level two box that allows you to change 00:15:07.199 --> 00:15:10.310 align:start position:0% level two box that allows you to change the<00:15:07.860> universe<00:15:08.279> you<00:15:08.639> are<00:15:08.760> working<00:15:09.000> in 00:15:10.310 --> 00:15:10.320 align:start position:0% the universe you are working in 00:15:10.320 --> 00:15:11.930 align:start position:0% the universe you are working in so 00:15:11.930 --> 00:15:11.940 align:start position:0% so 00:15:11.940 --> 00:15:14.150 align:start position:0% so um<00:15:12.000> basically<00:15:12.600> what<00:15:12.899> you<00:15:13.019> do<00:15:13.260> to<00:15:13.680> define<00:15:13.800> a 00:15:14.150 --> 00:15:14.160 align:start position:0% um basically what you do to define a 00:15:14.160 --> 00:15:17.449 align:start position:0% um basically what you do to define a functor<00:15:14.459> is<00:15:15.000> you<00:15:15.480> specify<00:15:15.959> a<00:15:16.860> mapping<00:15:17.220> from 00:15:17.449 --> 00:15:17.459 align:start position:0% functor is you specify a mapping from 00:15:17.459 --> 00:15:19.370 align:start position:0% functor is you specify a mapping from the<00:15:17.699> object<00:15:17.940> of<00:15:18.180> the<00:15:18.420> category<00:15:18.779> C<00:15:19.019> to<00:15:19.260> the 00:15:19.370 --> 00:15:19.380 align:start position:0% the object of the category C to the 00:15:19.380 --> 00:15:21.530 align:start position:0% the object of the category C to the objects<00:15:19.740> of<00:15:19.860> the<00:15:19.980> category<00:15:20.339> D<00:15:20.579> so<00:15:21.120> you<00:15:21.240> have<00:15:21.360> to 00:15:21.530 --> 00:15:21.540 align:start position:0% objects of the category D so you have to 00:15:21.540 --> 00:15:25.850 align:start position:0% objects of the category D so you have to say<00:15:21.779> where<00:15:22.380> systems<00:15:22.980> of<00:15:23.220> C<00:15:23.639> go<00:15:24.360> in<00:15:24.839> D<00:15:25.019> you<00:15:25.680> do 00:15:25.850 --> 00:15:25.860 align:start position:0% say where systems of C go in D you do 00:15:25.860 --> 00:15:28.189 align:start position:0% say where systems of C go in D you do the<00:15:26.040> same<00:15:26.160> for<00:15:26.459> the<00:15:26.639> morphism<00:15:27.120> so<00:15:27.600> for<00:15:27.899> each 00:15:28.189 --> 00:15:28.199 align:start position:0% the same for the morphism so for each 00:15:28.199 --> 00:15:31.310 align:start position:0% the same for the morphism so for each process<00:15:28.740> in<00:15:29.579> C<00:15:29.880> you<00:15:30.420> have<00:15:30.540> to<00:15:30.660> map<00:15:30.779> it<00:15:31.019> to<00:15:31.139> a 00:15:31.310 --> 00:15:31.320 align:start position:0% process in C you have to map it to a 00:15:31.320 --> 00:15:33.829 align:start position:0% process in C you have to map it to a process<00:15:31.560> in<00:15:31.800> D<00:15:32.040> and<00:15:33.000> and<00:15:33.240> this<00:15:33.540> is<00:15:33.660> the 00:15:33.829 --> 00:15:33.839 align:start position:0% process in D and and this is the 00:15:33.839 --> 00:15:35.990 align:start position:0% process in D and and this is the important<00:15:34.260> thing<00:15:34.500> these<00:15:35.160> mappings<00:15:35.519> have<00:15:35.820> to 00:15:35.990 --> 00:15:36.000 align:start position:0% important thing these mappings have to 00:15:36.000 --> 00:15:38.810 align:start position:0% important thing these mappings have to map<00:15:36.180> identities<00:15:37.079> into<00:15:37.500> identities<00:15:38.160> and 00:15:38.810 --> 00:15:38.820 align:start position:0% map identities into identities and 00:15:38.820 --> 00:15:41.569 align:start position:0% map identities into identities and compositions<00:15:39.600> into<00:15:39.899> compositions<00:15:40.740> so<00:15:41.399> what 00:15:41.569 --> 00:15:41.579 align:start position:0% compositions into compositions so what 00:15:41.579 --> 00:15:43.250 align:start position:0% compositions into compositions so what it<00:15:41.699> means<00:15:41.940> is<00:15:42.060> that<00:15:42.240> if<00:15:42.420> I<00:15:42.600> compose<00:15:42.959> two 00:15:43.250 --> 00:15:43.260 align:start position:0% it means is that if I compose two 00:15:43.260 --> 00:15:45.170 align:start position:0% it means is that if I compose two processes<00:15:43.800> in<00:15:44.040> C<00:15:44.220> and<00:15:44.639> then<00:15:44.760> I<00:15:44.880> use<00:15:45.000> the 00:15:45.170 --> 00:15:45.180 align:start position:0% processes in C and then I use the 00:15:45.180 --> 00:15:47.210 align:start position:0% processes in C and then I use the functor<00:15:45.540> is<00:15:46.199> the<00:15:46.440> same<00:15:46.560> of<00:15:46.800> using<00:15:47.100> the 00:15:47.210 --> 00:15:47.220 align:start position:0% functor is the same of using the 00:15:47.220 --> 00:15:48.949 align:start position:0% functor is the same of using the functions<00:15:47.639> on<00:15:47.820> the<00:15:48.000> components<00:15:48.540> and<00:15:48.839> then 00:15:48.949 --> 00:15:48.959 align:start position:0% functions on the components and then 00:15:48.959 --> 00:15:52.310 align:start position:0% functions on the components and then composing<00:15:49.560> them<00:15:49.800> in<00:15:50.160> D 00:15:52.310 --> 00:15:52.320 align:start position:0% composing them in D 00:15:52.320 --> 00:15:57.490 align:start position:0% composing them in D questions<00:15:53.040> or<00:15:53.699> sure 00:15:57.490 --> 00:15:57.500 align:start position:0% 00:15:57.500 --> 00:16:00.050 align:start position:0% not<00:15:58.500> necessarily<00:15:58.980> you<00:15:59.279> can<00:15:59.399> have<00:15:59.519> functors 00:16:00.050 --> 00:16:00.060 align:start position:0% not necessarily you can have functors 00:16:00.060 --> 00:16:03.110 align:start position:0% not necessarily you can have functors that<00:16:00.600> are<00:16:00.839> called<00:16:01.019> full<00:16:01.320> and<00:16:01.560> faithful<00:16:02.120> that 00:16:03.110 --> 00:16:03.120 align:start position:0% that are called full and faithful that 00:16:03.120 --> 00:16:05.389 align:start position:0% that are called full and faithful that allow<00:16:03.420> you<00:16:03.540> to<00:16:03.839> yet<00:16:04.139> basically<00:16:04.680> be<00:16:04.860> inverted 00:16:05.389 --> 00:16:05.399 align:start position:0% allow you to yet basically be inverted 00:16:05.399 --> 00:16:08.090 align:start position:0% allow you to yet basically be inverted and<00:16:05.579> go<00:16:05.820> one<00:16:06.540> direction<00:16:06.720> to<00:16:07.079> the<00:16:07.199> other<00:16:07.320> but<00:16:07.860> no 00:16:08.090 --> 00:16:08.100 align:start position:0% and go one direction to the other but no 00:16:08.100 --> 00:16:10.310 align:start position:0% and go one direction to the other but no in<00:16:08.519> general<00:16:08.639> these<00:16:09.300> can<00:16:09.420> you<00:16:09.899> can<00:16:10.019> lose 00:16:10.310 --> 00:16:10.320 align:start position:0% in general these can you can lose 00:16:10.320 --> 00:16:13.250 align:start position:0% in general these can you can lose information<00:16:10.680> or<00:16:11.339> you<00:16:11.579> can<00:16:11.699> embed<00:16:12.120> embed<00:16:12.899> a 00:16:13.250 --> 00:16:13.260 align:start position:0% information or you can embed embed a 00:16:13.260 --> 00:16:15.350 align:start position:0% information or you can embed embed a less<00:16:13.680> expressive<00:16:14.279> Universe<00:16:14.760> into<00:16:14.940> a<00:16:15.180> more 00:16:15.350 --> 00:16:15.360 align:start position:0% less expressive Universe into a more 00:16:15.360 --> 00:16:17.509 align:start position:0% less expressive Universe into a more expressive<00:16:15.839> Universe<00:16:16.260> if<00:16:16.440> you<00:16:16.560> want<00:16:16.680> to 00:16:17.509 --> 00:16:17.519 align:start position:0% expressive Universe if you want to 00:16:17.519 --> 00:16:20.990 align:start position:0% expressive Universe if you want to sure 00:16:20.990 --> 00:16:21.000 align:start position:0% 00:16:21.000 --> 00:16:23.210 align:start position:0% it's<00:16:21.600> like 00:16:23.210 --> 00:16:23.220 align:start position:0% it's like 00:16:23.220 --> 00:16:29.629 align:start position:0% it's like sorry 00:16:29.629 --> 00:16:29.639 align:start position:0% 00:16:29.639 --> 00:16:32.870 align:start position:0% factors<00:16:30.360> as<00:16:30.600> information<00:16:30.899> so<00:16:31.380> I<00:16:31.740> don't 00:16:32.870 --> 00:16:32.880 align:start position:0% factors as information so I don't 00:16:32.880 --> 00:16:36.470 align:start position:0% factors as information so I don't oh<00:16:33.300> linear<00:16:33.779> transformations 00:16:36.470 --> 00:16:36.480 align:start position:0% 00:16:36.480 --> 00:16:38.930 align:start position:0% uh 00:16:38.930 --> 00:16:38.940 align:start position:0% uh 00:16:38.940 --> 00:16:41.150 align:start position:0% uh maybe<00:16:39.600> I<00:16:39.839> don't<00:16:39.959> know<00:16:40.079> like<00:16:40.259> there<00:16:40.800> is<00:16:40.980> this 00:16:41.150 --> 00:16:41.160 align:start position:0% maybe I don't know like there is this 00:16:41.160 --> 00:16:42.769 align:start position:0% maybe I don't know like there is this very<00:16:41.399> convenient<00:16:41.880> thing<00:16:42.060> that<00:16:42.300> in<00:16:42.480> category 00:16:42.769 --> 00:16:42.779 align:start position:0% very convenient thing that in category 00:16:42.779 --> 00:16:44.150 align:start position:0% very convenient thing that in category Theory<00:16:43.199> everything<00:16:43.380> is<00:16:43.680> everything<00:16:43.860> else 00:16:44.150 --> 00:16:44.160 align:start position:0% Theory everything is everything else 00:16:44.160 --> 00:16:46.850 align:start position:0% Theory everything is everything else like<00:16:44.699> not<00:16:45.240> going<00:16:45.540> in<00:16:45.959> depth<00:16:46.320> into<00:16:46.380> that<00:16:46.680> but 00:16:46.850 --> 00:16:46.860 align:start position:0% like not going in depth into that but 00:16:46.860 --> 00:16:48.769 align:start position:0% like not going in depth into that but you<00:16:47.100> can<00:16:47.160> describe<00:16:47.579> a<00:16:47.759> category<00:16:48.120> as<00:16:48.300> a<00:16:48.420> factor 00:16:48.769 --> 00:16:48.779 align:start position:0% you can describe a category as a factor 00:16:48.779 --> 00:16:51.170 align:start position:0% you can describe a category as a factor and<00:16:49.259> a<00:16:49.380> functor<00:16:49.680> as<00:16:49.860> a<00:16:50.040> category<00:16:50.399> and<00:16:50.940> blah 00:16:51.170 --> 00:16:51.180 align:start position:0% and a functor as a category and blah 00:16:51.180 --> 00:16:54.410 align:start position:0% and a functor as a category and blah blah<00:16:51.360> blah<00:16:51.540> so<00:16:52.019> it<00:16:52.380> it<00:16:52.680> is<00:16:52.860> possible<00:16:53.339> maybe<00:16:54.060> to 00:16:54.410 --> 00:16:54.420 align:start position:0% blah blah so it it is possible maybe to 00:16:54.420 --> 00:16:56.329 align:start position:0% blah blah so it it is possible maybe to describe<00:16:54.720> a<00:16:54.899> function<00:16:55.259> as<00:16:55.440> a<00:16:55.620> sort<00:16:55.860> of<00:16:55.980> linear 00:16:56.329 --> 00:16:56.339 align:start position:0% describe a function as a sort of linear 00:16:56.339 --> 00:16:59.329 align:start position:0% describe a function as a sort of linear transformation<00:16:56.779> in<00:16:57.779> general<00:16:57.899> what<00:16:58.320> I<00:16:58.560> can<00:16:58.800> say 00:16:59.329 --> 00:16:59.339 align:start position:0% transformation in general what I can say 00:16:59.339 --> 00:17:01.610 align:start position:0% transformation in general what I can say is<00:16:59.699> that<00:16:59.940> you<00:17:00.180> can<00:17:00.240> Define<00:17:00.480> categories<00:17:01.380> of 00:17:01.610 --> 00:17:01.620 align:start position:0% is that you can Define categories of 00:17:01.620 --> 00:17:03.889 align:start position:0% is that you can Define categories of vector<00:17:01.980> spaces<00:17:02.459> for<00:17:02.759> instance<00:17:03.060> and<00:17:03.600> in<00:17:03.779> that 00:17:03.889 --> 00:17:03.899 align:start position:0% vector spaces for instance and in that 00:17:03.899 --> 00:17:06.770 align:start position:0% vector spaces for instance and in that case<00:17:04.079> your<00:17:04.439> morphisms<00:17:05.280> your<00:17:05.579> systems<00:17:06.120> will<00:17:06.600> be 00:17:06.770 --> 00:17:06.780 align:start position:0% case your morphisms your systems will be 00:17:06.780 --> 00:17:08.569 align:start position:0% case your morphisms your systems will be linear<00:17:07.140> applications<00:17:07.620> that<00:17:08.040> respect<00:17:08.400> the 00:17:08.569 --> 00:17:08.579 align:start position:0% linear applications that respect the 00:17:08.579 --> 00:17:15.730 align:start position:0% linear applications that respect the linearity<00:17:09.000> of<00:17:09.240> the<00:17:09.360> vector<00:17:09.660> space<00:17:09.980> uh<00:17:10.980> yeah 00:17:15.730 --> 00:17:15.740 align:start position:0% 00:17:15.740 --> 00:17:18.230 align:start position:0% you<00:17:16.740> know 00:17:18.230 --> 00:17:18.240 align:start position:0% you know 00:17:18.240 --> 00:17:19.970 align:start position:0% you know uh<00:17:18.720> yeah<00:17:18.900> yeah<00:17:19.079> this<00:17:19.319> is<00:17:19.439> exactly<00:17:19.799> what 00:17:19.970 --> 00:17:19.980 align:start position:0% uh yeah yeah this is exactly what 00:17:19.980 --> 00:17:21.949 align:start position:0% uh yeah yeah this is exactly what happens<00:17:20.160> because<00:17:20.640> this<00:17:21.179> thing<00:17:21.360> is<00:17:21.600> basically 00:17:21.949 --> 00:17:21.959 align:start position:0% happens because this thing is basically 00:17:21.959 --> 00:17:25.010 align:start position:0% happens because this thing is basically mapping<00:17:22.500> processes<00:17:23.160> of<00:17:23.459> C<00:17:23.760> to<00:17:24.179> processes<00:17:24.720> of<00:17:24.900> D 00:17:25.010 --> 00:17:25.020 align:start position:0% mapping processes of C to processes of D 00:17:25.020 --> 00:17:27.230 align:start position:0% mapping processes of C to processes of D so<00:17:25.559> you<00:17:25.740> can<00:17:25.860> see<00:17:26.100> it<00:17:26.280> as<00:17:26.520> an<00:17:26.699> higher<00:17:27.120> level 00:17:27.230 --> 00:17:27.240 align:start position:0% so you can see it as an higher level 00:17:27.240 --> 00:17:31.370 align:start position:0% so you can see it as an higher level function<00:17:27.839> and<00:17:28.559> indeed<00:17:29.040> a<00:17:29.820> factor<00:17:30.299> is<00:17:30.840> a 00:17:31.370 --> 00:17:31.380 align:start position:0% function and indeed a factor is a 00:17:31.380 --> 00:17:33.770 align:start position:0% function and indeed a factor is a process<00:17:31.679> in<00:17:32.100> the<00:17:32.220> category<00:17:32.580> of<00:17:32.760> categories<00:17:33.360> so 00:17:33.770 --> 00:17:33.780 align:start position:0% process in the category of categories so 00:17:33.780 --> 00:17:37.310 align:start position:0% process in the category of categories so you<00:17:34.080> can<00:17:34.260> do<00:17:35.100> this<00:17:35.520> kind<00:17:35.760> of<00:17:35.880> you<00:17:36.720> know<00:17:36.840> level 00:17:37.310 --> 00:17:37.320 align:start position:0% you can do this kind of you know level 00:17:37.320 --> 00:17:39.049 align:start position:0% you can do this kind of you know level up 00:17:39.049 --> 00:17:39.059 align:start position:0% up 00:17:39.059 --> 00:17:40.909 align:start position:0% up let<00:17:39.660> me<00:17:39.780> give<00:17:39.900> you<00:17:40.020> an<00:17:40.140> example<00:17:40.380> of<00:17:40.500> functor 00:17:40.909 --> 00:17:40.919 align:start position:0% let me give you an example of functor 00:17:40.919 --> 00:17:42.049 align:start position:0% let me give you an example of functor this<00:17:41.160> is<00:17:41.280> a<00:17:41.340> function<00:17:41.640> that<00:17:41.880> actually 00:17:42.049 --> 00:17:42.059 align:start position:0% this is a function that actually 00:17:42.059 --> 00:17:44.630 align:start position:0% this is a function that actually collapses<00:17:42.720> information<00:17:43.100> we<00:17:44.100> saw<00:17:44.340> two 00:17:44.630 --> 00:17:44.640 align:start position:0% collapses information we saw two 00:17:44.640 --> 00:17:47.450 align:start position:0% collapses information we saw two categories<00:17:45.179> data<00:17:45.900> and<00:17:46.080> set<00:17:46.320> and<00:17:47.220> we<00:17:47.340> can 00:17:47.450 --> 00:17:47.460 align:start position:0% categories data and set and we can 00:17:47.460 --> 00:17:50.330 align:start position:0% categories data and set and we can define<00:17:47.580> a<00:17:48.000> functor<00:17:48.360> that<00:17:48.780> sends<00:17:49.320> a<00:17:49.919> data<00:17:50.220> type 00:17:50.330 --> 00:17:50.340 align:start position:0% define a functor that sends a data type 00:17:50.340 --> 00:17:52.970 align:start position:0% define a functor that sends a data type into<00:17:50.760> the<00:17:51.000> set<00:17:51.120> it<00:17:51.480> implements<00:17:52.080> and<00:17:52.559> sends 00:17:52.970 --> 00:17:52.980 align:start position:0% into the set it implements and sends 00:17:52.980 --> 00:17:55.190 align:start position:0% into the set it implements and sends every<00:17:53.280> program<00:17:53.520> to<00:17:54.179> the<00:17:54.360> function<00:17:54.720> it 00:17:55.190 --> 00:17:55.200 align:start position:0% every program to the function it 00:17:55.200 --> 00:17:57.950 align:start position:0% every program to the function it implements<00:17:55.740> so<00:17:56.640> this<00:17:56.820> is<00:17:56.940> exactly<00:17:57.419> what<00:17:57.660> I<00:17:57.840> was 00:17:57.950 --> 00:17:57.960 align:start position:0% implements so this is exactly what I was 00:17:57.960 --> 00:17:59.270 align:start position:0% implements so this is exactly what I was saying<00:17:58.260> before 00:17:59.270 --> 00:17:59.280 align:start position:0% saying before 00:17:59.280 --> 00:18:01.490 align:start position:0% saying before that<00:17:59.820> you<00:18:00.059> can<00:18:00.120> start<00:18:00.299> in<00:18:00.539> the<00:18:00.720> category<00:18:01.020> data 00:18:01.490 --> 00:18:01.500 align:start position:0% that you can start in the category data 00:18:01.500 --> 00:18:04.010 align:start position:0% that you can start in the category data and<00:18:01.799> be<00:18:01.980> you<00:18:02.280> know<00:18:02.400> very<00:18:02.880> detailed<00:18:03.720> about 00:18:04.010 --> 00:18:04.020 align:start position:0% and be you know very detailed about 00:18:04.020 --> 00:18:05.750 align:start position:0% and be you know very detailed about distinguishing<00:18:04.740> things<00:18:04.919> and<00:18:05.340> then<00:18:05.460> you<00:18:05.640> say 00:18:05.750 --> 00:18:05.760 align:start position:0% distinguishing things and then you say 00:18:05.760 --> 00:18:07.730 align:start position:0% distinguishing things and then you say actually<00:18:06.059> I<00:18:06.419> don't<00:18:06.600> care<00:18:06.780> I<00:18:07.020> want<00:18:07.140> to<00:18:07.260> collapse 00:18:07.730 --> 00:18:07.740 align:start position:0% actually I don't care I want to collapse 00:18:07.740 --> 00:18:09.590 align:start position:0% actually I don't care I want to collapse all<00:18:07.860> this<00:18:08.039> information<00:18:08.280> and<00:18:09.059> I<00:18:09.299> want<00:18:09.480> to 00:18:09.590 --> 00:18:09.600 align:start position:0% all this information and I want to 00:18:09.600 --> 00:18:11.390 align:start position:0% all this information and I want to forget<00:18:09.780> about<00:18:10.200> you<00:18:10.860> know<00:18:10.980> these<00:18:11.220> different 00:18:11.390 --> 00:18:11.400 align:start position:0% forget about you know these different 00:18:11.400 --> 00:18:13.970 align:start position:0% forget about you know these different details<00:18:11.880> you<00:18:12.299> apply<00:18:12.660> this<00:18:12.840> functor<00:18:13.260> and 00:18:13.970 --> 00:18:13.980 align:start position:0% details you apply this functor and 00:18:13.980 --> 00:18:15.590 align:start position:0% details you apply this functor and that's<00:18:14.100> exactly<00:18:14.520> what<00:18:14.700> you<00:18:14.880> get<00:18:15.000> all<00:18:15.299> your 00:18:15.590 --> 00:18:15.600 align:start position:0% that's exactly what you get all your 00:18:15.600 --> 00:18:18.590 align:start position:0% that's exactly what you get all your process<00:18:15.960> compositions<00:18:16.799> now<00:18:17.160> you<00:18:17.760> know<00:18:17.880> lose<00:18:18.299> a 00:18:18.590 --> 00:18:18.600 align:start position:0% process compositions now you know lose a 00:18:18.600 --> 00:18:20.810 align:start position:0% process compositions now you know lose a part<00:18:18.780> of<00:18:18.960> information 00:18:20.810 --> 00:18:20.820 align:start position:0% part of information 00:18:20.820 --> 00:18:22.669 align:start position:0% part of information obviously<00:18:21.539> there<00:18:21.840> are<00:18:22.020> very<00:18:22.260> interesting 00:18:22.669 --> 00:18:22.679 align:start position:0% obviously there are very interesting 00:18:22.679 --> 00:18:25.250 align:start position:0% obviously there are very interesting questions<00:18:23.280> like<00:18:23.820> how<00:18:24.179> do<00:18:24.360> I<00:18:24.539> invert<00:18:25.020> these 00:18:25.250 --> 00:18:25.260 align:start position:0% questions like how do I invert these 00:18:25.260 --> 00:18:27.049 align:start position:0% questions like how do I invert these things<00:18:25.380> can<00:18:25.679> is<00:18:25.980> there<00:18:26.160> a<00:18:26.340> procedure<00:18:26.820> to 00:18:27.049 --> 00:18:27.059 align:start position:0% things can is there a procedure to 00:18:27.059 --> 00:18:29.990 align:start position:0% things can is there a procedure to canonically<00:18:27.919> invert<00:18:28.919> a<00:18:28.980> functor<00:18:29.400> and 00:18:29.990 --> 00:18:30.000 align:start position:0% canonically invert a functor and 00:18:30.000 --> 00:18:32.150 align:start position:0% canonically invert a functor and actually<00:18:30.120> go<00:18:30.480> for<00:18:30.780> instance<00:18:31.020> from<00:18:31.380> just<00:18:31.980> a 00:18:32.150 --> 00:18:32.160 align:start position:0% actually go for instance from just a 00:18:32.160 --> 00:18:35.390 align:start position:0% actually go for instance from just a specification<00:18:32.820> to<00:18:33.720> sorry<00:18:34.200> from<00:18:34.500> a<00:18:34.740> behavioral 00:18:35.390 --> 00:18:35.400 align:start position:0% specification to sorry from a behavioral 00:18:35.400 --> 00:18:37.250 align:start position:0% specification to sorry from a behavioral extensional<00:18:36.240> perspective<00:18:36.720> to<00:18:37.020> something 00:18:37.250 --> 00:18:37.260 align:start position:0% extensional perspective to something 00:18:37.260 --> 00:18:38.810 align:start position:0% extensional perspective to something more<00:18:37.559> complicated<00:18:37.980> sometimes<00:18:38.520> you<00:18:38.700> can 00:18:38.810 --> 00:18:38.820 align:start position:0% more complicated sometimes you can 00:18:38.820 --> 00:18:40.130 align:start position:0% more complicated sometimes you can sometimes<00:18:39.240> you<00:18:39.360> can 00:18:40.130 --> 00:18:40.140 align:start position:0% sometimes you can 00:18:40.140 --> 00:18:42.110 align:start position:0% sometimes you can I<00:18:41.039> don't<00:18:41.160> think 00:18:42.110 --> 00:18:42.120 align:start position:0% I don't think 00:18:42.120 --> 00:18:44.990 align:start position:0% I don't think yeah 00:18:44.990 --> 00:18:45.000 align:start position:0% yeah 00:18:45.000 --> 00:18:48.590 align:start position:0% yeah so<00:18:45.660> imagine<00:18:46.140> that<00:18:46.679> int<00:18:47.160> is<00:18:47.460> a<00:18:47.700> data<00:18:48.000> type<00:18:48.120> that 00:18:48.590 --> 00:18:48.600 align:start position:0% so imagine that int is a data type that 00:18:48.600 --> 00:18:51.529 align:start position:0% so imagine that int is a data type that you<00:18:48.720> define<00:18:48.960> I<00:18:49.320> don't<00:18:49.440> know<00:18:49.559> inascal<00:18:50.700> uh<00:18:51.419> about 00:18:51.529 --> 00:18:51.539 align:start position:0% you define I don't know inascal uh about 00:18:51.539 --> 00:18:52.850 align:start position:0% you define I don't know inascal uh about integers 00:18:52.850 --> 00:18:52.860 align:start position:0% integers 00:18:52.860 --> 00:18:56.930 align:start position:0% integers that<00:18:53.580> data<00:18:54.000> type<00:18:54.120> is<00:18:54.600> basically<00:18:54.960> modeling 00:18:56.930 --> 00:18:56.940 align:start position:0% that data type is basically modeling 00:18:56.940 --> 00:19:00.230 align:start position:0% that data type is basically modeling the<00:18:57.539> set<00:18:57.720> of<00:18:58.140> integers<00:18:58.679> in<00:18:59.460> a<00:18:59.640> computer<00:18:59.760> right 00:19:00.230 --> 00:19:00.240 align:start position:0% the set of integers in a computer right 00:19:00.240 --> 00:19:03.230 align:start position:0% the set of integers in a computer right so<00:19:01.200> conceptually<00:19:01.740> you<00:19:02.400> can<00:19:02.520> say<00:19:02.640> I<00:19:02.820> can<00:19:03.000> send 00:19:03.230 --> 00:19:03.240 align:start position:0% so conceptually you can say I can send 00:19:03.240 --> 00:19:06.470 align:start position:0% so conceptually you can say I can send that<00:19:03.600> to<00:19:04.260> Z<00:19:04.460> similarly<00:19:05.460> if<00:19:05.820> you<00:19:05.940> have<00:19:06.059> the<00:19:06.179> data 00:19:06.470 --> 00:19:06.480 align:start position:0% that to Z similarly if you have the data 00:19:06.480 --> 00:19:09.950 align:start position:0% that to Z similarly if you have the data type<00:19:06.600> string<00:19:07.140> you<00:19:07.799> can<00:19:07.919> have<00:19:08.160> a<00:19:09.000> set<00:19:09.179> of<00:19:09.720> all 00:19:09.950 --> 00:19:09.960 align:start position:0% type string you can have a set of all 00:19:09.960 --> 00:19:11.990 align:start position:0% type string you can have a set of all the<00:19:10.080> possible<00:19:10.440> words<00:19:10.799> on<00:19:11.160> an<00:19:11.340> alphabet<00:19:11.760> and 00:19:11.990 --> 00:19:12.000 align:start position:0% the possible words on an alphabet and 00:19:12.000 --> 00:19:14.770 align:start position:0% the possible words on an alphabet and again<00:19:12.179> you<00:19:12.480> can<00:19:12.539> send<00:19:12.780> string<00:19:13.260> to<00:19:13.679> that<00:19:13.860> set 00:19:14.770 --> 00:19:14.780 align:start position:0% again you can send string to that set 00:19:14.780 --> 00:19:17.930 align:start position:0% again you can send string to that set uh<00:19:15.780> with<00:19:16.380> this<00:19:16.559> functor<00:19:16.980> basically<00:19:17.520> what 00:19:17.930 --> 00:19:17.940 align:start position:0% uh with this functor basically what 00:19:17.940 --> 00:19:19.669 align:start position:0% uh with this functor basically what happens<00:19:18.059> is<00:19:18.419> that<00:19:18.600> these<00:19:18.900> two<00:19:19.020> programs<00:19:19.500> here 00:19:19.669 --> 00:19:19.679 align:start position:0% happens is that these two programs here 00:19:19.679 --> 00:19:22.370 align:start position:0% happens is that these two programs here get<00:19:20.400> mapped<00:19:20.760> to<00:19:20.880> the<00:19:21.059> same<00:19:21.240> function<00:19:21.720> between 00:19:22.370 --> 00:19:22.380 align:start position:0% get mapped to the same function between 00:19:22.380 --> 00:19:23.750 align:start position:0% get mapped to the same function between sets 00:19:23.750 --> 00:19:23.760 align:start position:0% sets 00:19:23.760 --> 00:19:25.789 align:start position:0% sets so<00:19:24.240> I<00:19:24.480> have<00:19:24.600> two<00:19:24.840> different<00:19:25.020> implementations 00:19:25.789 --> 00:19:25.799 align:start position:0% so I have two different implementations 00:19:25.799 --> 00:19:28.130 align:start position:0% so I have two different implementations of<00:19:26.160> the<00:19:26.340> same<00:19:26.520> program<00:19:26.760> that<00:19:27.600> maybe<00:19:27.720> you<00:19:28.020> know 00:19:28.130 --> 00:19:28.140 align:start position:0% of the same program that maybe you know 00:19:28.140 --> 00:19:31.669 align:start position:0% of the same program that maybe you know I<00:19:28.380> consider<00:19:29.220> separate<00:19:29.700> as<00:19:30.059> programs<00:19:30.720> like<00:19:31.500> if 00:19:31.669 --> 00:19:31.679 align:start position:0% I consider separate as programs like if 00:19:31.679 --> 00:19:33.590 align:start position:0% I consider separate as programs like if I<00:19:31.860> for<00:19:32.100> instance<00:19:32.340> hash<00:19:32.640> the<00:19:33.000> one<00:19:33.179> on<00:19:33.360> the<00:19:33.480> left 00:19:33.590 --> 00:19:33.600 align:start position:0% I for instance hash the one on the left 00:19:33.600 --> 00:19:35.210 align:start position:0% I for instance hash the one on the left and<00:19:33.840> the<00:19:33.960> one<00:19:34.080> on<00:19:34.200> the<00:19:34.320> right<00:19:34.440> the<00:19:34.679> hashes<00:19:35.039> will 00:19:35.210 --> 00:19:35.220 align:start position:0% and the one on the right the hashes will 00:19:35.220 --> 00:19:36.190 align:start position:0% and the one on the right the hashes will be<00:19:35.400> different 00:19:36.190 --> 00:19:36.200 align:start position:0% be different 00:19:36.200 --> 00:19:39.470 align:start position:0% be different uh<00:19:37.200> but<00:19:37.620> they<00:19:38.340> correspond<00:19:38.880> to<00:19:39.059> the<00:19:39.299> same 00:19:39.470 --> 00:19:39.480 align:start position:0% uh but they correspond to the same 00:19:39.480 --> 00:19:41.210 align:start position:0% uh but they correspond to the same function<00:19:39.840> they<00:19:40.140> are<00:19:40.320> implementing<00:19:40.860> the<00:19:41.100> same 00:19:41.210 --> 00:19:41.220 align:start position:0% function they are implementing the same 00:19:41.220 --> 00:19:43.669 align:start position:0% function they are implementing the same function<00:19:41.580> so<00:19:41.880> when<00:19:42.059> I<00:19:42.240> go<00:19:42.419> from<00:19:42.900> data<00:19:43.320> to<00:19:43.440> set 00:19:43.669 --> 00:19:43.679 align:start position:0% function so when I go from data to set 00:19:43.679 --> 00:19:47.450 align:start position:0% function so when I go from data to set i'm<00:19:44.160> I<00:19:45.000> deciding<00:19:45.660> willingly<00:19:46.200> to<00:19:46.500> lose<00:19:47.160> that 00:19:47.450 --> 00:19:47.460 align:start position:0% i'm I deciding willingly to lose that 00:19:47.460 --> 00:19:49.070 align:start position:0% i'm I deciding willingly to lose that information 00:19:49.070 --> 00:19:49.080 align:start position:0% information 00:19:49.080 --> 00:19:52.610 align:start position:0% information okay<00:19:49.679> let's<00:19:50.100> try<00:19:50.640> to<00:19:50.820> use<00:19:51.120> what<00:19:51.660> we<00:19:51.960> got<00:19:52.260> up<00:19:52.440> to 00:19:52.610 --> 00:19:52.620 align:start position:0% okay let's try to use what we got up to 00:19:52.620 --> 00:19:54.770 align:start position:0% okay let's try to use what we got up to now<00:19:52.799> to<00:19:53.160> do<00:19:53.400> some<00:19:53.640> process<00:19:53.940> design<00:19:54.179> that<00:19:54.600> is 00:19:54.770 --> 00:19:54.780 align:start position:0% now to do some process design that is 00:19:54.780 --> 00:19:56.870 align:start position:0% now to do some process design that is actually<00:19:54.960> the<00:19:55.200> interesting<00:19:55.559> part<00:19:55.860> of<00:19:56.039> it 00:19:56.870 --> 00:19:56.880 align:start position:0% actually the interesting part of it 00:19:56.880 --> 00:19:59.029 align:start position:0% actually the interesting part of it this<00:19:57.480> is<00:19:57.600> a<00:19:57.780> very<00:19:57.960> simple<00:19:58.140> example<00:19:58.740> imagine 00:19:59.029 --> 00:19:59.039 align:start position:0% this is a very simple example imagine 00:19:59.039 --> 00:20:01.190 align:start position:0% this is a very simple example imagine that<00:19:59.400> you<00:19:59.520> have<00:19:59.640> a<00:19:59.760> grid<00:20:00.120> and<00:20:00.480> you<00:20:00.720> want<00:20:00.900> to 00:20:01.190 --> 00:20:01.200 align:start position:0% that you have a grid and you want to 00:20:01.200 --> 00:20:03.950 align:start position:0% that you have a grid and you want to define<00:20:02.039> the<00:20:02.460> process<00:20:02.760> of<00:20:03.059> moving<00:20:03.539> on<00:20:03.840> this 00:20:03.950 --> 00:20:03.960 align:start position:0% define the process of moving on this 00:20:03.960 --> 00:20:05.750 align:start position:0% define the process of moving on this grid<00:20:04.320> so 00:20:05.750 --> 00:20:05.760 align:start position:0% grid so 00:20:05.760 --> 00:20:08.690 align:start position:0% grid so imagine<00:20:06.240> that<00:20:06.600> you<00:20:06.840> can<00:20:06.900> only<00:20:07.200> move<00:20:07.980> of<00:20:08.460> you 00:20:08.690 --> 00:20:08.700 align:start position:0% imagine that you can only move of you 00:20:08.700 --> 00:20:10.789 align:start position:0% imagine that you can only move of you know<00:20:08.820> a<00:20:09.120> kind<00:20:09.299> of<00:20:09.360> fixed<00:20:09.840> amount<00:20:10.080> of<00:20:10.260> things<00:20:10.500> so 00:20:10.789 --> 00:20:10.799 align:start position:0% know a kind of fixed amount of things so 00:20:10.799 --> 00:20:13.610 align:start position:0% know a kind of fixed amount of things so it's<00:20:10.919> not<00:20:11.160> like<00:20:11.520> I<00:20:12.179> cannot<00:20:12.419> move<00:20:12.600> like<00:20:12.840> 0.1 00:20:13.610 --> 00:20:13.620 align:start position:0% it's not like I cannot move like 0.1 00:20:13.620 --> 00:20:16.070 align:start position:0% it's not like I cannot move like 0.1 steps<00:20:14.100> but<00:20:14.280> only<00:20:14.400> one<00:20:14.760> step<00:20:14.940> at<00:20:15.120> a<00:20:15.299> time 00:20:16.070 --> 00:20:16.080 align:start position:0% steps but only one step at a time 00:20:16.080 --> 00:20:18.110 align:start position:0% steps but only one step at a time in<00:20:16.679> this<00:20:16.860> case<00:20:16.980> you'll<00:20:17.340> see<00:20:17.520> that<00:20:17.700> wherever 00:20:18.110 --> 00:20:18.120 align:start position:0% in this case you'll see that wherever 00:20:18.120 --> 00:20:20.390 align:start position:0% in this case you'll see that wherever you<00:20:18.480> are<00:20:18.600> there<00:20:18.900> will<00:20:19.080> be<00:20:19.260> four<00:20:19.679> fundamental 00:20:20.390 --> 00:20:20.400 align:start position:0% you are there will be four fundamental 00:20:20.400 --> 00:20:22.789 align:start position:0% you are there will be four fundamental processes<00:20:21.179> that<00:20:21.539> are<00:20:21.720> up<00:20:22.020> down<00:20:22.260> left<00:20:22.559> right 00:20:22.789 --> 00:20:22.799 align:start position:0% processes that are up down left right 00:20:22.799 --> 00:20:25.970 align:start position:0% processes that are up down left right that<00:20:23.280> allow<00:20:23.580> you<00:20:23.640> to<00:20:23.820> move<00:20:24.120> one<00:20:24.840> step<00:20:25.080> and<00:20:25.799> now 00:20:25.970 --> 00:20:25.980 align:start position:0% that allow you to move one step and now 00:20:25.980 --> 00:20:28.490 align:start position:0% that allow you to move one step and now I<00:20:26.220> can<00:20:26.340> basically<00:20:26.760> describe<00:20:27.299> every<00:20:27.660> path<00:20:27.960> as<00:20:28.320> a 00:20:28.490 --> 00:20:28.500 align:start position:0% I can basically describe every path as a 00:20:28.500 --> 00:20:30.890 align:start position:0% I can basically describe every path as a concatenation<00:20:29.100> of<00:20:29.460> these<00:20:29.700> processes<00:20:30.179> so<00:20:30.720> for 00:20:30.890 --> 00:20:30.900 align:start position:0% concatenation of these processes so for 00:20:30.900 --> 00:20:32.870 align:start position:0% concatenation of these processes so for instance<00:20:31.140> if<00:20:31.380> I<00:20:31.559> move<00:20:31.740> three<00:20:32.039> times<00:20:32.280> right<00:20:32.640> and 00:20:32.870 --> 00:20:32.880 align:start position:0% instance if I move three times right and 00:20:32.880 --> 00:20:36.470 align:start position:0% instance if I move three times right and two<00:20:33.059> times<00:20:33.240> down<00:20:33.600> I'm<00:20:34.320> describing<00:20:35.039> the<00:20:35.880> L<00:20:36.179> part 00:20:36.470 --> 00:20:36.480 align:start position:0% two times down I'm describing the L part 00:20:36.480 --> 00:20:39.409 align:start position:0% two times down I'm describing the L part I<00:20:36.660> have<00:20:36.840> there<00:20:37.020> if<00:20:37.380> I<00:20:37.559> feed<00:20:37.740> to<00:20:38.400> this<00:20:38.580> process<00:20:39.000> a 00:20:39.409 --> 00:20:39.419 align:start position:0% I have there if I feed to this process a 00:20:39.419 --> 00:20:41.270 align:start position:0% I have there if I feed to this process a couple<00:20:39.539> of<00:20:39.720> coordinates<00:20:40.440> that<00:20:40.679> tell<00:20:40.860> me<00:20:41.039> where 00:20:41.270 --> 00:20:41.280 align:start position:0% couple of coordinates that tell me where 00:20:41.280 --> 00:20:43.909 align:start position:0% couple of coordinates that tell me where I<00:20:41.460> am<00:20:41.640> then<00:20:42.480> these<00:20:43.140> coordinates<00:20:43.559> will<00:20:43.740> be 00:20:43.909 --> 00:20:43.919 align:start position:0% I am then these coordinates will be 00:20:43.919 --> 00:20:46.010 align:start position:0% I am then these coordinates will be transformed<00:20:44.580> as<00:20:45.059> in<00:20:45.240> the<00:20:45.480> end<00:20:45.539> of<00:20:45.720> the<00:20:45.840> path 00:20:46.010 --> 00:20:46.020 align:start position:0% transformed as in the end of the path 00:20:46.020 --> 00:20:47.210 align:start position:0% transformed as in the end of the path basically 00:20:47.210 --> 00:20:47.220 align:start position:0% basically 00:20:47.220 --> 00:20:50.090 align:start position:0% basically and<00:20:48.059> we<00:20:48.360> see<00:20:48.539> that<00:20:48.780> in<00:20:49.200> this<00:20:49.500> kind<00:20:49.620> of<00:20:49.799> theory 00:20:50.090 --> 00:20:50.100 align:start position:0% and we see that in this kind of theory 00:20:50.100 --> 00:20:52.310 align:start position:0% and we see that in this kind of theory we<00:20:50.400> also<00:20:50.640> have<00:20:50.760> some<00:20:50.940> equations<00:20:51.299> like<00:20:51.780> if<00:20:52.200> you 00:20:52.310 --> 00:20:52.320 align:start position:0% we also have some equations like if you 00:20:52.320 --> 00:20:54.770 align:start position:0% we also have some equations like if you move<00:20:52.559> right<00:20:53.039> and<00:20:53.340> then<00:20:53.580> down<00:20:53.880> does<00:20:54.419> the<00:20:54.600> same 00:20:54.770 --> 00:20:54.780 align:start position:0% move right and then down does the same 00:20:54.780 --> 00:20:57.529 align:start position:0% move right and then down does the same of<00:20:55.020> moving<00:20:55.380> down<00:20:56.100> and<00:20:56.400> then<00:20:56.580> right<00:20:56.820> you<00:20:57.360> are 00:20:57.529 --> 00:20:57.539 align:start position:0% of moving down and then right you are 00:20:57.539 --> 00:21:00.409 align:start position:0% of moving down and then right you are describing<00:20:58.080> a<00:20:58.500> square<00:20:58.740> you<00:20:59.520> are<00:20:59.640> just<00:20:59.940> walking 00:21:00.409 --> 00:21:00.419 align:start position:0% describing a square you are just walking 00:21:00.419 --> 00:21:03.049 align:start position:0% describing a square you are just walking in<00:21:00.840> like<00:21:01.140> different<00:21:01.559> paths<00:21:02.039> but<00:21:02.220> you<00:21:02.760> end<00:21:02.940> up 00:21:03.049 --> 00:21:03.059 align:start position:0% in like different paths but you end up 00:21:03.059 --> 00:21:04.190 align:start position:0% in like different paths but you end up in<00:21:03.240> the<00:21:03.360> same<00:21:03.480> place 00:21:04.190 --> 00:21:04.200 align:start position:0% in the same place 00:21:04.200 --> 00:21:06.710 align:start position:0% in the same place let's<00:21:04.740> spice<00:21:05.100> this<00:21:05.340> up<00:21:05.580> and<00:21:06.179> let's<00:21:06.299> do<00:21:06.539> it 00:21:06.710 --> 00:21:06.720 align:start position:0% let's spice this up and let's do it 00:21:06.720 --> 00:21:10.190 align:start position:0% let's spice this up and let's do it concurrently<00:21:07.320> now<00:21:08.100> we<00:21:08.400> have<00:21:08.580> multiple<00:21:09.419> agents 00:21:10.190 --> 00:21:10.200 align:start position:0% concurrently now we have multiple agents 00:21:10.200 --> 00:21:12.650 align:start position:0% concurrently now we have multiple agents uh<00:21:10.980> wandering<00:21:11.460> on<00:21:11.640> this<00:21:11.820> grid 00:21:12.650 --> 00:21:12.660 align:start position:0% uh wandering on this grid 00:21:12.660 --> 00:21:15.590 align:start position:0% uh wandering on this grid and<00:21:13.260> we<00:21:13.380> want<00:21:13.559> to<00:21:13.740> model<00:21:13.980> you<00:21:14.580> know<00:21:14.700> how<00:21:15.419> they 00:21:15.590 --> 00:21:15.600 align:start position:0% and we want to model you know how they 00:21:15.600 --> 00:21:17.090 align:start position:0% and we want to model you know how they move 00:21:17.090 --> 00:21:17.100 align:start position:0% move 00:21:17.100 --> 00:21:19.669 align:start position:0% move intuitively<00:21:18.059> what<00:21:18.360> you<00:21:18.480> do<00:21:18.660> is<00:21:18.900> well<00:21:19.260> now<00:21:19.500> we 00:21:19.669 --> 00:21:19.679 align:start position:0% intuitively what you do is well now we 00:21:19.679 --> 00:21:21.710 align:start position:0% intuitively what you do is well now we want<00:21:20.039> to<00:21:20.160> consider<00:21:20.580> processes<00:21:21.299> that<00:21:21.480> happen 00:21:21.710 --> 00:21:21.720 align:start position:0% want to consider processes that happen 00:21:21.720 --> 00:21:24.289 align:start position:0% want to consider processes that happen in<00:21:22.080> parallel<00:21:22.500> like<00:21:23.039> if<00:21:23.220> I<00:21:23.400> have<00:21:23.520> two<00:21:23.760> agents 00:21:24.289 --> 00:21:24.299 align:start position:0% in parallel like if I have two agents 00:21:24.299 --> 00:21:26.450 align:start position:0% in parallel like if I have two agents for<00:21:24.539> instance<00:21:24.840> I<00:21:25.559> can<00:21:25.679> have<00:21:25.860> this<00:21:26.160> process 00:21:26.450 --> 00:21:26.460 align:start position:0% for instance I can have this process 00:21:26.460 --> 00:21:28.850 align:start position:0% for instance I can have this process here<00:21:26.700> that<00:21:27.059> says<00:21:27.360> agent<00:21:27.780> one<00:21:27.960> moves<00:21:28.740> three 00:21:28.850 --> 00:21:28.860 align:start position:0% here that says agent one moves three 00:21:28.860 --> 00:21:31.010 align:start position:0% here that says agent one moves three times<00:21:29.100> on<00:21:29.400> the<00:21:29.520> right<00:21:29.700> and<00:21:30.179> agent<00:21:30.539> two<00:21:30.659> moves 00:21:31.010 --> 00:21:31.020 align:start position:0% times on the right and agent two moves 00:21:31.020 --> 00:21:33.230 align:start position:0% times on the right and agent two moves down<00:21:31.200> and<00:21:31.559> then<00:21:31.679> on<00:21:31.919> the<00:21:32.039> right<00:21:32.220> and<00:21:32.880> now<00:21:33.059> we 00:21:33.230 --> 00:21:33.240 align:start position:0% down and then on the right and now we 00:21:33.240 --> 00:21:37.730 align:start position:0% down and then on the right and now we see<00:21:33.480> that<00:21:33.840> new<00:21:34.799> equations<00:21:35.360> pop<00:21:36.360> out<00:21:36.600> so<00:21:37.380> for 00:21:37.730 --> 00:21:37.740 align:start position:0% see that new equations pop out so for 00:21:37.740 --> 00:21:39.169 align:start position:0% see that new equations pop out so for instance<00:21:37.980> I<00:21:38.220> have<00:21:38.340> this<00:21:38.520> equation<00:21:38.820> here 00:21:39.169 --> 00:21:39.179 align:start position:0% instance I have this equation here 00:21:39.179 --> 00:21:42.110 align:start position:0% instance I have this equation here called<00:21:40.080> The<00:21:40.380> Interchange<00:21:40.980> law<00:21:41.280> that 00:21:42.110 --> 00:21:42.120 align:start position:0% called The Interchange law that 00:21:42.120 --> 00:21:44.149 align:start position:0% called The Interchange law that basically<00:21:42.419> says<00:21:42.840> these<00:21:43.559> two<00:21:43.679> threads<00:21:44.039> are 00:21:44.149 --> 00:21:44.159 align:start position:0% basically says these two threads are 00:21:44.159 --> 00:21:45.169 align:start position:0% basically says these two threads are separate 00:21:45.169 --> 00:21:45.179 align:start position:0% separate 00:21:45.179 --> 00:21:47.990 align:start position:0% separate you<00:21:45.900> can<00:21:46.020> see<00:21:46.140> the<00:21:46.440> first<00:21:46.559> are<00:21:46.860> saying<00:21:47.220> I<00:21:47.760> move 00:21:47.990 --> 00:21:48.000 align:start position:0% you can see the first are saying I move 00:21:48.000 --> 00:21:51.470 align:start position:0% you can see the first are saying I move somewhere<00:21:49.260> internet<00:21:49.799> do<00:21:50.220> nothing<00:21:50.400> the<00:21:51.360> other 00:21:51.470 --> 00:21:51.480 align:start position:0% somewhere internet do nothing the other 00:21:51.480 --> 00:21:53.750 align:start position:0% somewhere internet do nothing the other agent<00:21:51.960> does<00:21:52.500> nothing<00:21:52.679> in<00:21:52.980> which<00:21:53.280> for<00:21:53.520> you<00:21:53.640> to 00:21:53.750 --> 00:21:53.760 align:start position:0% agent does nothing in which for you to 00:21:53.760 --> 00:21:55.610 align:start position:0% agent does nothing in which for you to move<00:21:54.000> and<00:21:54.539> then<00:21:54.659> moves 00:21:55.610 --> 00:21:55.620 align:start position:0% move and then moves 00:21:55.620 --> 00:21:58.370 align:start position:0% move and then moves in<00:21:56.159> this<00:21:56.340> setup<00:21:56.700> is<00:21:57.120> the<00:21:57.419> same<00:21:57.539> if<00:21:57.900> you<00:21:58.140> just 00:21:58.370 --> 00:21:58.380 align:start position:0% in this setup is the same if you just 00:21:58.380 --> 00:22:01.070 align:start position:0% in this setup is the same if you just you<00:21:58.860> know<00:21:58.980> swap<00:21:59.880> the<00:22:00.120> things<00:22:00.360> and<00:22:00.780> second 00:22:01.070 --> 00:22:01.080 align:start position:0% you know swap the things and second 00:22:01.080 --> 00:22:03.770 align:start position:0% you know swap the things and second agent<00:22:01.559> moves<00:22:01.919> first<00:22:02.100> and<00:22:02.760> first<00:22:03.000> agent<00:22:03.419> moves 00:22:03.770 --> 00:22:03.780 align:start position:0% agent moves first and first agent moves 00:22:03.780 --> 00:22:04.610 align:start position:0% agent moves first and first agent moves later 00:22:04.610 --> 00:22:04.620 align:start position:0% later 00:22:04.620 --> 00:22:08.210 align:start position:0% later why<00:22:05.400> because<00:22:06.020> intuitively<00:22:07.020> these<00:22:07.679> two<00:22:07.799> agents 00:22:08.210 --> 00:22:08.220 align:start position:0% why because intuitively these two agents 00:22:08.220 --> 00:22:10.970 align:start position:0% why because intuitively these two agents are<00:22:08.640> not<00:22:08.820> causally<00:22:09.559> interfering<00:22:10.559> with<00:22:10.799> each 00:22:10.970 --> 00:22:10.980 align:start position:0% are not causally interfering with each 00:22:10.980 --> 00:22:13.130 align:start position:0% are not causally interfering with each other<00:22:11.100> agent<00:22:11.880> one<00:22:12.059> doesn't<00:22:12.419> care<00:22:12.659> at<00:22:12.960> all 00:22:13.130 --> 00:22:13.140 align:start position:0% other agent one doesn't care at all 00:22:13.140 --> 00:22:15.770 align:start position:0% other agent one doesn't care at all about<00:22:13.440> what<00:22:13.679> agent<00:22:14.039> 2<00:22:14.220> does<00:22:14.520> and<00:22:15.059> vice<00:22:15.360> versa 00:22:15.770 --> 00:22:15.780 align:start position:0% about what agent 2 does and vice versa 00:22:15.780 --> 00:22:19.370 align:start position:0% about what agent 2 does and vice versa and<00:22:16.020> so<00:22:16.260> in<00:22:16.620> these<00:22:17.100> formalization<00:22:18.000> of<00:22:18.780> moving 00:22:19.370 --> 00:22:19.380 align:start position:0% and so in these formalization of moving 00:22:19.380 --> 00:22:21.470 align:start position:0% and so in these formalization of moving on<00:22:19.500> a<00:22:19.620> grid<00:22:19.799> concurrently<00:22:20.340> I<00:22:21.000> have<00:22:21.179> these 00:22:21.470 --> 00:22:21.480 align:start position:0% on a grid concurrently I have these 00:22:21.480 --> 00:22:23.350 align:start position:0% on a grid concurrently I have these extra<00:22:21.600> equations 00:22:23.350 --> 00:22:23.360 align:start position:0% extra equations 00:22:23.360 --> 00:22:25.789 align:start position:0% extra equations mathematically<00:22:24.360> we<00:22:24.720> say<00:22:24.900> that<00:22:25.140> the<00:22:25.380> Universe 00:22:25.789 --> 00:22:25.799 align:start position:0% mathematically we say that the Universe 00:22:25.799 --> 00:22:28.190 align:start position:0% mathematically we say that the Universe we<00:22:26.159> are<00:22:26.340> relying<00:22:27.179> upon<00:22:27.419> is<00:22:27.659> not<00:22:27.840> just<00:22:27.960> a 00:22:28.190 --> 00:22:28.200 align:start position:0% we are relying upon is not just a 00:22:28.200 --> 00:22:29.510 align:start position:0% we are relying upon is not just a category<00:22:28.559> but<00:22:28.799> it's<00:22:28.980> something<00:22:29.159> called<00:22:29.340> the 00:22:29.510 --> 00:22:29.520 align:start position:0% category but it's something called the 00:22:29.520 --> 00:22:32.270 align:start position:0% category but it's something called the monoidal<00:22:30.059> category<00:22:30.480> that<00:22:31.320> basically<00:22:31.620> means<00:22:31.980> a 00:22:32.270 --> 00:22:32.280 align:start position:0% monoidal category that basically means a 00:22:32.280 --> 00:22:34.130 align:start position:0% monoidal category that basically means a category<00:22:32.640> where<00:22:32.880> you<00:22:33.120> can<00:22:33.179> do<00:22:33.360> also<00:22:33.600> things<00:22:33.840> in 00:22:34.130 --> 00:22:34.140 align:start position:0% category where you can do also things in 00:22:34.140 --> 00:22:35.350 align:start position:0% category where you can do also things in parallel 00:22:35.350 --> 00:22:35.360 align:start position:0% parallel 00:22:35.360 --> 00:22:38.690 align:start position:0% parallel okay<00:22:36.360> let's<00:22:36.840> do<00:22:37.200> uh<00:22:37.559> more<00:22:37.799> like<00:22:37.980> programming 00:22:38.690 --> 00:22:38.700 align:start position:0% okay let's do uh more like programming 00:22:38.700 --> 00:22:41.930 align:start position:0% okay let's do uh more like programming oriented<00:22:39.539> example<00:22:40.020> so<00:22:40.679> let's<00:22:41.039> consider<00:22:41.580> a 00:22:41.930 --> 00:22:41.940 align:start position:0% oriented example so let's consider a 00:22:41.940 --> 00:22:43.730 align:start position:0% oriented example so let's consider a very<00:22:42.059> simple<00:22:42.240> record<00:22:42.659> uh<00:22:43.260> let's<00:22:43.440> call<00:22:43.559> it 00:22:43.730 --> 00:22:43.740 align:start position:0% very simple record uh let's call it 00:22:43.740 --> 00:22:46.610 align:start position:0% very simple record uh let's call it person<00:22:44.360> uh<00:22:45.360> This<00:22:45.659> Record<00:22:45.840> has<00:22:46.080> two<00:22:46.320> Fields 00:22:46.610 --> 00:22:46.620 align:start position:0% person uh This Record has two Fields 00:22:46.620 --> 00:22:50.149 align:start position:0% person uh This Record has two Fields name<00:22:46.980> and<00:22:47.159> surname<00:22:47.580> okay 00:22:50.149 --> 00:22:50.159 align:start position:0% 00:22:50.159 --> 00:22:52.070 align:start position:0% um<00:22:50.299> now 00:22:52.070 --> 00:22:52.080 align:start position:0% um now 00:22:52.080 --> 00:22:55.010 align:start position:0% um now you<00:22:52.740> can<00:22:52.799> notice<00:22:53.159> that<00:22:53.340> in<00:22:53.640> this<00:22:53.820> record<00:22:54.020> in 00:22:55.010 --> 00:22:55.020 align:start position:0% you can notice that in this record in 00:22:55.020 --> 00:22:57.230 align:start position:0% you can notice that in this record in this<00:22:55.200> example<00:22:55.620> person<00:22:56.039> is<00:22:56.340> basically<00:22:56.700> just<00:22:57.059> a 00:22:57.230 --> 00:22:57.240 align:start position:0% this example person is basically just a 00:22:57.240 --> 00:23:01.850 align:start position:0% this example person is basically just a couple<00:22:57.360> of<00:22:57.539> terms<00:22:58.100> of<00:22:59.100> type<00:22:59.460> name<00:22:59.820> and<00:23:00.240> surname 00:23:01.850 --> 00:23:01.860 align:start position:0% couple of terms of type name and surname 00:23:01.860 --> 00:23:04.669 align:start position:0% couple of terms of type name and surname now<00:23:02.520> we<00:23:02.820> want<00:23:03.059> to<00:23:03.240> be<00:23:03.600> able<00:23:04.020> to<00:23:04.200> you<00:23:04.620> know 00:23:04.669 --> 00:23:04.679 align:start position:0% now we want to be able to you know 00:23:04.679 --> 00:23:08.049 align:start position:0% now we want to be able to you know functionally<00:23:05.340> describe<00:23:06.120> the<00:23:06.740> procedure<00:23:07.740> of 00:23:08.049 --> 00:23:08.059 align:start position:0% functionally describe the procedure of 00:23:08.059 --> 00:23:11.870 align:start position:0% functionally describe the procedure of extracting<00:23:09.080> a<00:23:10.080> subfield<00:23:10.440> of<00:23:10.679> this<00:23:10.860> record<00:23:11.100> so 00:23:11.870 --> 00:23:11.880 align:start position:0% extracting a subfield of this record so 00:23:11.880 --> 00:23:13.789 align:start position:0% extracting a subfield of this record so you<00:23:12.240> give<00:23:12.360> me<00:23:12.539> a<00:23:12.720> person<00:23:12.840> I<00:23:13.080> give<00:23:13.260> you<00:23:13.380> the<00:23:13.559> name 00:23:13.789 --> 00:23:13.799 align:start position:0% you give me a person I give you the name 00:23:13.799 --> 00:23:16.549 align:start position:0% you give me a person I give you the name for<00:23:14.220> instance<00:23:14.460> and<00:23:15.360> we<00:23:15.600> also<00:23:15.900> want<00:23:16.080> to<00:23:16.200> be<00:23:16.380> able 00:23:16.549 --> 00:23:16.559 align:start position:0% for instance and we also want to be able 00:23:16.559 --> 00:23:19.850 align:start position:0% for instance and we also want to be able to<00:23:16.679> replace<00:23:17.400> the<00:23:18.059> subfield<00:23:18.539> of<00:23:19.260> a<00:23:19.380> given<00:23:19.679> type 00:23:19.850 --> 00:23:19.860 align:start position:0% to replace the subfield of a given type 00:23:19.860 --> 00:23:22.130 align:start position:0% to replace the subfield of a given type with<00:23:20.400> a<00:23:20.640> subfield<00:23:21.000> of<00:23:21.240> a<00:23:21.360> different<00:23:21.480> type<00:23:21.780> this 00:23:22.130 --> 00:23:22.140 align:start position:0% with a subfield of a different type this 00:23:22.140 --> 00:23:23.870 align:start position:0% with a subfield of a different type this is<00:23:22.260> a<00:23:22.380> bit<00:23:22.500> more<00:23:22.679> complicated<00:23:23.159> but<00:23:23.520> what<00:23:23.760> it 00:23:23.870 --> 00:23:23.880 align:start position:0% is a bit more complicated but what it 00:23:23.880 --> 00:23:25.010 align:start position:0% is a bit more complicated but what it really<00:23:24.059> means 00:23:25.010 --> 00:23:25.020 align:start position:0% really means 00:23:25.020 --> 00:23:26.930 align:start position:0% really means is<00:23:25.380> that<00:23:25.620> for<00:23:25.799> instance<00:23:26.039> imagine<00:23:26.280> that<00:23:26.580> I<00:23:26.760> want 00:23:26.930 --> 00:23:26.940 align:start position:0% is that for instance imagine that I want 00:23:26.940 --> 00:23:29.570 align:start position:0% is that for instance imagine that I want to<00:23:27.059> edit<00:23:27.720> this<00:23:28.320> personal<00:23:28.559> record<00:23:28.860> I<00:23:29.340> want<00:23:29.460> to 00:23:29.570 --> 00:23:29.580 align:start position:0% to edit this personal record I want to 00:23:29.580 --> 00:23:32.149 align:start position:0% to edit this personal record I want to strip<00:23:29.880> surname<00:23:30.360> out<00:23:30.659> and<00:23:31.200> put<00:23:31.380> a<00:23:31.559> new<00:23:31.679> field<00:23:31.860> in 00:23:32.149 --> 00:23:32.159 align:start position:0% strip surname out and put a new field in 00:23:32.159 --> 00:23:33.649 align:start position:0% strip surname out and put a new field in called<00:23:32.460> age 00:23:33.649 --> 00:23:33.659 align:start position:0% called age 00:23:33.659 --> 00:23:36.950 align:start position:0% called age that<00:23:34.380> is<00:23:34.500> of<00:23:34.679> different<00:23:34.860> type<00:23:35.640> so<00:23:36.299> the<00:23:36.780> point 00:23:36.950 --> 00:23:36.960 align:start position:0% that is of different type so the point 00:23:36.960 --> 00:23:38.990 align:start position:0% that is of different type so the point is<00:23:37.140> how<00:23:37.740> can<00:23:37.919> we<00:23:38.100> do<00:23:38.280> that 00:23:38.990 --> 00:23:39.000 align:start position:0% is how can we do that 00:23:39.000 --> 00:23:41.570 align:start position:0% is how can we do that in<00:23:39.720> a<00:23:39.900> automated<00:23:40.380> and<00:23:40.919> more<00:23:41.159> importantly 00:23:41.570 --> 00:23:41.580 align:start position:0% in a automated and more importantly 00:23:41.580 --> 00:23:43.930 align:start position:0% in a automated and more importantly compositional<00:23:42.539> way 00:23:43.930 --> 00:23:43.940 align:start position:0% compositional way 00:23:43.940 --> 00:23:48.169 align:start position:0% compositional way uh<00:23:45.440> so<00:23:46.440> what<00:23:46.860> I<00:23:46.980> mean<00:23:47.100> by<00:23:47.220> compositional<00:23:48.000> is 00:23:48.169 --> 00:23:48.179 align:start position:0% uh so what I mean by compositional is 00:23:48.179 --> 00:23:51.950 align:start position:0% uh so what I mean by compositional is Imagine<00:23:48.600> This<00:23:48.960> example<00:23:49.700> where<00:23:50.700> I<00:23:51.179> have<00:23:51.360> the 00:23:51.950 --> 00:23:51.960 align:start position:0% Imagine This example where I have the 00:23:51.960 --> 00:23:54.590 align:start position:0% Imagine This example where I have the record<00:23:52.320> person<00:23:52.740> but<00:23:53.700> one<00:23:53.940> of<00:23:54.059> the<00:23:54.179> fields<00:23:54.480> is 00:23:54.590 --> 00:23:54.600 align:start position:0% record person but one of the fields is 00:23:54.600 --> 00:23:57.110 align:start position:0% record person but one of the fields is itself<00:23:54.900> a<00:23:55.140> record<00:23:55.260> it's<00:23:55.620> a<00:23:55.799> sub<00:23:55.980> record 00:23:57.110 --> 00:23:57.120 align:start position:0% itself a record it's a sub record 00:23:57.120 --> 00:24:00.770 align:start position:0% itself a record it's a sub record and<00:23:57.659> now<00:23:57.840> I<00:23:58.140> say<00:23:58.320> okay<00:23:58.559> I<00:23:59.159> want<00:23:59.280> to<00:23:59.520> replace<00:24:00.299> the 00:24:00.770 --> 00:24:00.780 align:start position:0% and now I say okay I want to replace the 00:24:00.780 --> 00:24:02.930 align:start position:0% and now I say okay I want to replace the city<00:24:00.900> thing<00:24:01.320> there<00:24:01.620> Bogota<00:24:02.280> with<00:24:02.760> something 00:24:02.930 --> 00:24:02.940 align:start position:0% city thing there Bogota with something 00:24:02.940 --> 00:24:05.690 align:start position:0% city thing there Bogota with something else<00:24:03.559> intuitively<00:24:04.559> I<00:24:04.919> want<00:24:05.100> to<00:24:05.220> be<00:24:05.340> able<00:24:05.520> to 00:24:05.690 --> 00:24:05.700 align:start position:0% else intuitively I want to be able to 00:24:05.700 --> 00:24:09.110 align:start position:0% else intuitively I want to be able to pipe<00:24:06.480> the<00:24:07.200> process<00:24:07.440> for<00:24:07.740> editing<00:24:08.220> person<00:24:08.520> with 00:24:09.110 --> 00:24:09.120 align:start position:0% pipe the process for editing person with 00:24:09.120 --> 00:24:11.690 align:start position:0% pipe the process for editing person with the<00:24:09.299> process<00:24:09.539> for<00:24:09.780> editing<00:24:10.320> address<00:24:10.679> and<00:24:11.520> you 00:24:11.690 --> 00:24:11.700 align:start position:0% the process for editing address and you 00:24:11.700 --> 00:24:14.029 align:start position:0% the process for editing address and you know<00:24:11.760> feed<00:24:12.179> these<00:24:12.960> compose<00:24:13.620> these<00:24:13.980> two 00:24:14.029 --> 00:24:14.039 align:start position:0% know feed these compose these two 00:24:14.039 --> 00:24:16.370 align:start position:0% know feed these compose these two processes<00:24:14.640> in<00:24:15.360> a<00:24:15.480> way<00:24:15.600> so<00:24:15.780> that<00:24:15.960> I<00:24:16.080> don't<00:24:16.200> have 00:24:16.370 --> 00:24:16.380 align:start position:0% processes in a way so that I don't have 00:24:16.380 --> 00:24:18.830 align:start position:0% processes in a way so that I don't have to<00:24:16.559> reinvent<00:24:17.039> the<00:24:17.220> wheel<00:24:17.400> every<00:24:17.760> time 00:24:18.830 --> 00:24:18.840 align:start position:0% to reinvent the wheel every time 00:24:18.840 --> 00:24:21.529 align:start position:0% to reinvent the wheel every time the<00:24:19.559> way<00:24:19.740> you<00:24:19.919> do<00:24:20.100> this<00:24:20.340> in<00:24:20.880> a<00:24:21.059> functional 00:24:21.529 --> 00:24:21.539 align:start position:0% the way you do this in a functional 00:24:21.539 --> 00:24:25.370 align:start position:0% the way you do this in a functional programming<00:24:22.140> and<00:24:22.620> in<00:24:23.600> compositionality<00:24:24.600> is 00:24:25.370 --> 00:24:25.380 align:start position:0% programming and in compositionality is 00:24:25.380 --> 00:24:28.430 align:start position:0% programming and in compositionality is with<00:24:25.799> something<00:24:26.100> called<00:24:26.460> a<00:24:26.820> lens<00:24:27.120> that<00:24:28.080> is<00:24:28.200> a 00:24:28.430 --> 00:24:28.440 align:start position:0% with something called a lens that is a 00:24:28.440 --> 00:24:29.930 align:start position:0% with something called a lens that is a particular<00:24:28.679> example<00:24:29.159> of<00:24:29.400> something<00:24:29.640> called 00:24:29.930 --> 00:24:29.940 align:start position:0% particular example of something called 00:24:29.940 --> 00:24:31.549 align:start position:0% particular example of something called an<00:24:30.299> optic 00:24:31.549 --> 00:24:31.559 align:start position:0% an optic 00:24:31.559 --> 00:24:35.210 align:start position:0% an optic so<00:24:32.220> what<00:24:33.179> is<00:24:33.360> the<00:24:33.480> idea<00:24:33.780> uh<00:24:34.380> the<00:24:34.559> idea<00:24:34.740> is<00:24:34.980> that 00:24:35.210 --> 00:24:35.220 align:start position:0% so what is the idea uh the idea is that 00:24:35.220 --> 00:24:37.010 align:start position:0% so what is the idea uh the idea is that the<00:24:35.400> lens<00:24:35.640> is<00:24:35.820> just<00:24:36.059> a<00:24:36.179> couple<00:24:36.299> of<00:24:36.480> processes 00:24:37.010 --> 00:24:37.020 align:start position:0% the lens is just a couple of processes 00:24:37.020 --> 00:24:40.510 align:start position:0% the lens is just a couple of processes one<00:24:37.740> called<00:24:37.919> get<00:24:38.220> and<00:24:38.460> one<00:24:38.640> could<00:24:38.820> put 00:24:40.510 --> 00:24:40.520 align:start position:0% one called get and one could put 00:24:40.520 --> 00:24:43.669 align:start position:0% one called get and one could put and<00:24:41.520> basically<00:24:41.940> get<00:24:42.179> is<00:24:42.419> taking<00:24:42.659> your<00:24:43.200> record 00:24:43.669 --> 00:24:43.679 align:start position:0% and basically get is taking your record 00:24:43.679 --> 00:24:46.310 align:start position:0% and basically get is taking your record and<00:24:44.220> is<00:24:44.400> giving<00:24:44.640> you<00:24:44.880> the<00:24:45.120> subfield 00:24:46.310 --> 00:24:46.320 align:start position:0% and is giving you the subfield 00:24:46.320 --> 00:24:49.510 align:start position:0% and is giving you the subfield that<00:24:47.100> in<00:24:47.280> this<00:24:47.460> case<00:24:47.640> is<00:24:47.880> s<00:24:48.360> subfield<00:24:48.900> of<00:24:49.140> a 00:24:49.510 --> 00:24:49.520 align:start position:0% that in this case is s subfield of a 00:24:49.520 --> 00:24:53.270 align:start position:0% that in this case is s subfield of a what<00:24:50.520> put<00:24:50.760> does<00:24:51.120> instead<00:24:51.600> put<00:24:52.020> is<00:24:52.380> taking<00:24:52.740> your 00:24:53.270 --> 00:24:53.280 align:start position:0% what put does instead put is taking your 00:24:53.280 --> 00:24:56.330 align:start position:0% what put does instead put is taking your record<00:24:53.640> a<00:24:54.120> is<00:24:54.960> taking<00:24:55.200> something<00:24:55.500> of<00:24:55.740> type<00:24:55.980> T 00:24:56.330 --> 00:24:56.340 align:start position:0% record a is taking something of type T 00:24:56.340 --> 00:24:59.210 align:start position:0% record a is taking something of type T and<00:24:57.000> intuitively<00:24:57.600> is<00:24:57.840> replacing<00:24:58.440> s<00:24:58.740> with<00:24:58.980> t 00:24:59.210 --> 00:24:59.220 align:start position:0% and intuitively is replacing s with t 00:24:59.220 --> 00:25:01.310 align:start position:0% and intuitively is replacing s with t and<00:25:00.059> now<00:25:00.179> it's<00:25:00.360> spitting<00:25:00.720> out<00:25:00.840> something<00:25:01.020> of 00:25:01.310 --> 00:25:01.320 align:start position:0% and now it's spitting out something of 00:25:01.320 --> 00:25:03.830 align:start position:0% and now it's spitting out something of type<00:25:01.559> B<00:25:01.799> you<00:25:02.220> see<00:25:02.340> the<00:25:02.640> type<00:25:02.820> of<00:25:03.000> a<00:25:03.179> could 00:25:03.830 --> 00:25:03.840 align:start position:0% type B you see the type of a could 00:25:03.840 --> 00:25:06.830 align:start position:0% type B you see the type of a could change<00:25:04.260> because<00:25:05.100> you<00:25:05.520> replace<00:25:05.760> the<00:25:06.240> type<00:25:06.419> of<00:25:06.600> a 00:25:06.830 --> 00:25:06.840 align:start position:0% change because you replace the type of a 00:25:06.840 --> 00:25:09.890 align:start position:0% change because you replace the type of a subfield<00:25:07.260> of<00:25:07.620> this<00:25:07.799> thing<00:25:08.400> if<00:25:09.059> a<00:25:09.299> was<00:25:09.539> a<00:25:09.780> couple 00:25:09.890 --> 00:25:09.900 align:start position:0% subfield of this thing if a was a couple 00:25:09.900 --> 00:25:12.110 align:start position:0% subfield of this thing if a was a couple of<00:25:10.080> strings<00:25:10.440> with<00:25:11.220> this<00:25:11.460> put<00:25:11.700> I<00:25:11.940> could 00:25:12.110 --> 00:25:12.120 align:start position:0% of strings with this put I could 00:25:12.120 --> 00:25:13.909 align:start position:0% of strings with this put I could substitute<00:25:12.659> a<00:25:12.840> string<00:25:13.080> type<00:25:13.260> with<00:25:13.500> a<00:25:13.679> nint 00:25:13.909 --> 00:25:13.919 align:start position:0% substitute a string type with a nint 00:25:13.919 --> 00:25:16.850 align:start position:0% substitute a string type with a nint type<00:25:14.159> and<00:25:14.820> then<00:25:15.059> the<00:25:15.299> overall<00:25:15.780> type<00:25:16.080> of<00:25:16.679> the 00:25:16.850 --> 00:25:16.860 align:start position:0% type and then the overall type of the 00:25:16.860 --> 00:25:19.430 align:start position:0% type and then the overall type of the record<00:25:16.980> will<00:25:17.400> change 00:25:19.430 --> 00:25:19.440 align:start position:0% record will change 00:25:19.440 --> 00:25:21.590 align:start position:0% record will change the<00:25:19.980> funny<00:25:20.100> thing<00:25:20.400> about<00:25:20.820> this<00:25:21.120> is<00:25:21.299> that<00:25:21.480> you 00:25:21.590 --> 00:25:21.600 align:start position:0% the funny thing about this is that you 00:25:21.600 --> 00:25:22.970 align:start position:0% the funny thing about this is that you know<00:25:21.720> there<00:25:21.840> is<00:25:21.960> an<00:25:22.080> ask<00:25:22.200> a<00:25:22.440> library<00:25:22.679> for 00:25:22.970 --> 00:25:22.980 align:start position:0% know there is an ask a library for 00:25:22.980 --> 00:25:24.850 align:start position:0% know there is an ask a library for instance<00:25:23.280> that<00:25:23.580> allow<00:25:23.880> you<00:25:24.059> allows<00:25:24.480> you<00:25:24.600> to 00:25:24.850 --> 00:25:24.860 align:start position:0% instance that allow you allows you to 00:25:24.860 --> 00:25:28.190 align:start position:0% instance that allow you allows you to automatically<00:25:25.860> get<00:25:26.419> these<00:25:27.419> things<00:25:27.539> for<00:25:27.840> every 00:25:28.190 --> 00:25:28.200 align:start position:0% automatically get these things for every 00:25:28.200 --> 00:25:30.950 align:start position:0% automatically get these things for every a<00:25:28.500> s<00:25:28.799> and<00:25:28.980> t<00:25:29.220> as<00:25:29.460> soon<00:25:29.580> as<00:25:29.700> you<00:25:29.880> define<00:25:30.120> your 00:25:30.950 --> 00:25:30.960 align:start position:0% a s and t as soon as you define your 00:25:30.960 --> 00:25:33.409 align:start position:0% a s and t as soon as you define your type<00:25:31.140> A<00:25:31.440> this<00:25:31.740> thing<00:25:31.980> will<00:25:32.159> you<00:25:32.820> know<00:25:32.880> create 00:25:33.409 --> 00:25:33.419 align:start position:0% type A this thing will you know create 00:25:33.419 --> 00:25:35.269 align:start position:0% type A this thing will you know create the<00:25:33.720> Setters<00:25:34.140> and<00:25:34.260> Getters<00:25:34.620> automatically 00:25:35.269 --> 00:25:35.279 align:start position:0% the Setters and Getters automatically 00:25:35.279 --> 00:25:37.850 align:start position:0% the Setters and Getters automatically for<00:25:35.520> you<00:25:35.700> so<00:25:36.419> it's<00:25:36.600> a<00:25:36.840> it's<00:25:37.140> a<00:25:37.380> procedure<00:25:37.679> that 00:25:37.850 --> 00:25:37.860 align:start position:0% for you so it's a it's a procedure that 00:25:37.860 --> 00:25:39.529 align:start position:0% for you so it's a it's a procedure that you<00:25:37.980> can<00:25:38.100> automate<00:25:38.580> and<00:25:39.120> that's<00:25:39.240> the<00:25:39.419> cool 00:25:39.529 --> 00:25:39.539 align:start position:0% you can automate and that's the cool 00:25:39.539 --> 00:25:41.029 align:start position:0% you can automate and that's the cool thing<00:25:39.659> you<00:25:40.020> don't<00:25:40.140> have<00:25:40.260> to<00:25:40.440> do<00:25:40.559> it<00:25:40.740> manually 00:25:41.029 --> 00:25:41.039 align:start position:0% thing you don't have to do it manually 00:25:41.039 --> 00:25:43.070 align:start position:0% thing you don't have to do it manually the<00:25:41.400> library<00:25:41.520> does<00:25:41.880> it<00:25:42.059> for<00:25:42.179> you 00:25:43.070 --> 00:25:43.080 align:start position:0% the library does it for you 00:25:43.080 --> 00:25:45.230 align:start position:0% the library does it for you okay<00:25:43.679> so<00:25:43.980> I'll<00:25:44.159> do<00:25:44.400> these<00:25:44.640> things<00:25:44.760> compose 00:25:45.230 --> 00:25:45.240 align:start position:0% okay so I'll do these things compose 00:25:45.240 --> 00:25:47.750 align:start position:0% okay so I'll do these things compose imagine<00:25:45.600> that<00:25:46.020> I<00:25:46.320> have<00:25:46.440> two<00:25:46.620> lenses<00:25:47.039> so<00:25:47.520> the 00:25:47.750 --> 00:25:47.760 align:start position:0% imagine that I have two lenses so the 00:25:47.760 --> 00:25:50.529 align:start position:0% imagine that I have two lenses so the first<00:25:47.940> is<00:25:48.419> taking<00:25:48.600> the<00:25:48.960> subfield<00:25:49.320> s<00:25:49.679> from<00:25:50.039> a 00:25:50.529 --> 00:25:50.539 align:start position:0% first is taking the subfield s from a 00:25:50.539 --> 00:25:53.690 align:start position:0% first is taking the subfield s from a and<00:25:51.539> the<00:25:51.779> second<00:25:51.900> one<00:25:52.200> is<00:25:52.440> taking<00:25:52.679> the<00:25:53.580> sub 00:25:53.690 --> 00:25:53.700 align:start position:0% and the second one is taking the sub 00:25:53.700 --> 00:25:56.810 align:start position:0% and the second one is taking the sub field<00:25:54.059> V<00:25:54.480> from<00:25:54.840> s<00:25:55.200> the<00:25:55.919> get<00:25:56.100> part<00:25:56.340> is<00:25:56.640> easy 00:25:56.810 --> 00:25:56.820 align:start position:0% field V from s the get part is easy 00:25:56.820 --> 00:25:58.190 align:start position:0% field V from s the get part is easy because<00:25:57.179> you<00:25:57.480> see<00:25:57.600> you<00:25:57.840> can<00:25:57.960> just 00:25:58.190 --> 00:25:58.200 align:start position:0% because you see you can just 00:25:58.200 --> 00:26:00.830 align:start position:0% because you see you can just telescopically<00:25:59.159> access<00:25:59.940> the<00:26:00.299> records<00:26:00.720> you 00:26:00.830 --> 00:26:00.840 align:start position:0% telescopically access the records you 00:26:00.840 --> 00:26:03.590 align:start position:0% telescopically access the records you can<00:26:00.960> say<00:26:01.140> I<00:26:01.559> start<00:26:01.799> from<00:26:01.980> a<00:26:02.159> I<00:26:02.700> pull<00:26:02.880> out<00:26:03.059> s<00:26:03.360> and 00:26:03.590 --> 00:26:03.600 align:start position:0% can say I start from a I pull out s and 00:26:03.600 --> 00:26:07.010 align:start position:0% can say I start from a I pull out s and I<00:26:03.779> pull<00:26:03.960> out<00:26:04.080> V<00:26:04.320> from<00:26:04.559> s 00:26:07.010 --> 00:26:07.020 align:start position:0% 00:26:07.020 --> 00:26:09.529 align:start position:0% the<00:26:07.260> part<00:26:07.559> is<00:26:07.799> a<00:26:07.980> bit<00:26:08.100> more<00:26:08.460> complicated<00:26:09.000> so 00:26:09.529 --> 00:26:09.539 align:start position:0% the part is a bit more complicated so 00:26:09.539 --> 00:26:12.710 align:start position:0% the part is a bit more complicated so what<00:26:10.440> happens<00:26:10.620> here<00:26:10.919> is<00:26:11.220> that<00:26:11.460> imagine<00:26:12.240> that 00:26:12.710 --> 00:26:12.720 align:start position:0% what happens here is that imagine that 00:26:12.720 --> 00:26:15.890 align:start position:0% what happens here is that imagine that in<00:26:13.020> S<00:26:13.320> I<00:26:13.799> am<00:26:13.919> replacing<00:26:14.520> the<00:26:14.700> subfield<00:26:15.059> V<00:26:15.360> with 00:26:15.890 --> 00:26:15.900 align:start position:0% in S I am replacing the subfield V with 00:26:15.900 --> 00:26:18.289 align:start position:0% in S I am replacing the subfield V with a<00:26:16.080> subfield<00:26:16.320> W<00:26:16.679> and<00:26:17.340> I<00:26:17.460> obtain<00:26:17.820> something<00:26:18.000> of 00:26:18.289 --> 00:26:18.299 align:start position:0% a subfield W and I obtain something of 00:26:18.299 --> 00:26:19.250 align:start position:0% a subfield W and I obtain something of type<00:26:18.419> t 00:26:19.250 --> 00:26:19.260 align:start position:0% type t 00:26:19.260 --> 00:26:22.730 align:start position:0% type t and<00:26:19.860> now<00:26:19.980> I<00:26:20.159> want<00:26:20.279> to<00:26:20.460> replace<00:26:20.960> uh<00:26:21.960> s<00:26:22.200> with<00:26:22.500> this 00:26:22.730 --> 00:26:22.740 align:start position:0% and now I want to replace uh s with this 00:26:22.740 --> 00:26:25.909 align:start position:0% and now I want to replace uh s with this type<00:26:22.919> B<00:26:23.220> into<00:26:23.520> a<00:26:23.940> how<00:26:24.900> do<00:26:25.020> I<00:26:25.200> compose<00:26:25.500> these<00:26:25.860> two 00:26:25.909 --> 00:26:25.919 align:start position:0% type B into a how do I compose these two 00:26:25.919 --> 00:26:28.070 align:start position:0% type B into a how do I compose these two things<00:26:26.159> well<00:26:26.820> with<00:26:27.240> this<00:26:27.480> sort<00:26:27.659> of<00:26:27.840> like 00:26:28.070 --> 00:26:28.080 align:start position:0% things well with this sort of like 00:26:28.080 --> 00:26:31.070 align:start position:0% things well with this sort of like monstrous<00:26:28.799> awful<00:26:29.159> thing<00:26:29.460> here<00:26:29.940> in<00:26:30.360> in<00:26:30.840> the 00:26:31.070 --> 00:26:31.080 align:start position:0% monstrous awful thing here in in the 00:26:31.080 --> 00:26:35.450 align:start position:0% monstrous awful thing here in in the bottom<00:26:31.440> where<00:26:31.919> I<00:26:32.100> basically<00:26:32.400> take<00:26:32.700> a<00:26:33.059> I<00:26:33.900> copy<00:26:34.380> a 00:26:35.450 --> 00:26:35.460 align:start position:0% bottom where I basically take a I copy a 00:26:35.460 --> 00:26:39.409 align:start position:0% bottom where I basically take a I copy a I<00:26:36.240> get<00:26:36.600> S<00:26:37.080> from<00:26:37.380> a<00:26:37.740> now<00:26:38.520> you<00:26:38.700> see<00:26:38.880> I<00:26:39.059> can<00:26:39.179> use 00:26:39.409 --> 00:26:39.419 align:start position:0% I get S from a now you see I can use 00:26:39.419 --> 00:26:43.190 align:start position:0% I get S from a now you see I can use this<00:26:39.720> put<00:26:40.020> put<00:26:40.740> V<00:26:41.159> and<00:26:42.059> basically<00:26:42.480> substitute 00:26:43.190 --> 00:26:43.200 align:start position:0% this put put V and basically substitute 00:26:43.200 --> 00:26:46.909 align:start position:0% this put put V and basically substitute uh<00:26:44.159> V<00:26:44.400> in<00:26:44.700> s<00:26:44.940> with<00:26:45.179> W<00:26:45.419> I<00:26:46.020> get<00:26:46.200> something<00:26:46.380> of<00:26:46.679> type 00:26:46.909 --> 00:26:46.919 align:start position:0% uh V in s with W I get something of type 00:26:46.919 --> 00:26:50.930 align:start position:0% uh V in s with W I get something of type T<00:26:47.400> and<00:26:47.880> then<00:26:48.000> I<00:26:48.179> can<00:26:48.240> use<00:26:48.480> put<00:26:48.900> on<00:26:49.740> T<00:26:50.039> and<00:26:50.340> A<00:26:50.580> to 00:26:50.930 --> 00:26:50.940 align:start position:0% T and then I can use put on T and A to 00:26:50.940 --> 00:26:51.950 align:start position:0% T and then I can use put on T and A to get<00:26:51.120> a<00:26:51.240> B 00:26:51.950 --> 00:26:51.960 align:start position:0% get a B 00:26:51.960 --> 00:26:55.010 align:start position:0% get a B I<00:26:52.559> know<00:26:52.740> that<00:26:52.980> this<00:26:53.159> sounds<00:26:53.419> very<00:26:54.419> cumbersome 00:26:55.010 --> 00:26:55.020 align:start position:0% I know that this sounds very cumbersome 00:26:55.020 --> 00:26:57.049 align:start position:0% I know that this sounds very cumbersome and<00:26:55.440> difficult<00:26:55.799> to<00:26:56.039> follow 00:26:57.049 --> 00:26:57.059 align:start position:0% and difficult to follow 00:26:57.059 --> 00:27:00.470 align:start position:0% and difficult to follow but<00:26:57.720> the<00:26:57.960> good<00:26:58.140> thing<00:26:58.380> is<00:26:58.740> that<00:26:59.039> you<00:26:59.520> can<00:26:59.760> you 00:27:00.470 --> 00:27:00.480 align:start position:0% but the good thing is that you can you 00:27:00.480 --> 00:27:03.830 align:start position:0% but the good thing is that you can you know<00:27:00.799> topologically<00:27:01.799> deform<00:27:02.520> these<00:27:03.419> diagrams 00:27:03.830 --> 00:27:03.840 align:start position:0% know topologically deform these diagrams 00:27:03.840 --> 00:27:06.590 align:start position:0% know topologically deform these diagrams and<00:27:04.440> basically<00:27:04.799> Express<00:27:05.039> them<00:27:05.460> in<00:27:05.760> a<00:27:05.880> way<00:27:06.000> that 00:27:06.590 --> 00:27:06.600 align:start position:0% and basically Express them in a way that 00:27:06.600 --> 00:27:09.769 align:start position:0% and basically Express them in a way that makes<00:27:06.779> way<00:27:07.020> more<00:27:07.260> sense<00:27:07.559> so<00:27:08.279> in<00:27:08.520> here<00:27:08.779> instead 00:27:09.769 --> 00:27:09.779 align:start position:0% makes way more sense so in here instead 00:27:09.779 --> 00:27:11.450 align:start position:0% makes way more sense so in here instead of<00:27:09.840> considering<00:27:10.380> this<00:27:10.679> funk<00:27:11.039> these<00:27:11.340> things 00:27:11.450 --> 00:27:11.460 align:start position:0% of considering this funk these things 00:27:11.460 --> 00:27:14.149 align:start position:0% of considering this funk these things are<00:27:11.700> two<00:27:12.120> couple<00:27:12.360> separate<00:27:12.960> processes 00:27:14.149 --> 00:27:14.159 align:start position:0% are two couple separate processes 00:27:14.159 --> 00:27:17.210 align:start position:0% are two couple separate processes I'm<00:27:14.880> you<00:27:15.360> know<00:27:15.480> packaging<00:27:16.200> them<00:27:16.440> as<00:27:16.740> a<00:27:16.919> unique 00:27:17.210 --> 00:27:17.220 align:start position:0% I'm you know packaging them as a unique 00:27:17.220 --> 00:27:18.049 align:start position:0% I'm you know packaging them as a unique thing 00:27:18.049 --> 00:27:18.059 align:start position:0% thing 00:27:18.059 --> 00:27:21.169 align:start position:0% thing so<00:27:18.980> as<00:27:19.980> you<00:27:20.100> can<00:27:20.220> see<00:27:20.340> this<00:27:20.580> thing<00:27:20.760> is<00:27:20.880> a<00:27:21.059> bit 00:27:21.169 --> 00:27:21.179 align:start position:0% so as you can see this thing is a bit 00:27:21.179 --> 00:27:24.830 align:start position:0% so as you can see this thing is a bit strange<00:27:21.600> because<00:27:22.500> it<00:27:22.860> has<00:27:23.120> arrows<00:27:24.120> going<00:27:24.360> in 00:27:24.830 --> 00:27:24.840 align:start position:0% strange because it has arrows going in 00:27:24.840 --> 00:27:29.090 align:start position:0% strange because it has arrows going in opposite<00:27:25.200> directions<00:27:25.760> so<00:27:26.760> on<00:27:27.179> the<00:27:27.299> top<00:27:27.480> row<00:27:28.260> a 00:27:29.090 --> 00:27:29.100 align:start position:0% opposite directions so on the top row a 00:27:29.100 --> 00:27:31.669 align:start position:0% opposite directions so on the top row a gets<00:27:29.580> processed<00:27:30.120> into<00:27:30.299> an<00:27:30.600> S<00:27:30.840> so<00:27:31.320> you<00:27:31.500> are 00:27:31.669 --> 00:27:31.679 align:start position:0% gets processed into an S so you are 00:27:31.679 --> 00:27:34.669 align:start position:0% gets processed into an S so you are extracting<00:27:32.220> s<00:27:32.460> from<00:27:32.760> a<00:27:33.059> on<00:27:34.020> the<00:27:34.200> bottom<00:27:34.440> row 00:27:34.669 --> 00:27:34.679 align:start position:0% extracting s from a on the bottom row 00:27:34.679 --> 00:27:37.789 align:start position:0% extracting s from a on the bottom row you<00:27:34.860> are<00:27:34.980> getting<00:27:35.100> this<00:27:35.460> t<00:27:35.700> on<00:27:36.480> the<00:27:36.659> right<00:27:36.840> and 00:27:37.789 --> 00:27:37.799 align:start position:0% you are getting this t on the right and 00:27:37.799 --> 00:27:40.070 align:start position:0% you are getting this t on the right and you<00:27:38.220> know<00:27:38.340> you<00:27:38.580> are<00:27:38.700> writing<00:27:39.240> s<00:27:39.360> with<00:27:39.600> t<00:27:39.840> and 00:27:40.070 --> 00:27:40.080 align:start position:0% you know you are writing s with t and 00:27:40.080 --> 00:27:43.130 align:start position:0% you know you are writing s with t and you're<00:27:40.260> getting<00:27:40.500> a<00:27:40.799> B<00:27:41.100> on<00:27:41.580> the<00:27:41.760> left 00:27:43.130 --> 00:27:43.140 align:start position:0% you're getting a B on the left 00:27:43.140 --> 00:27:45.890 align:start position:0% you're getting a B on the left this<00:27:43.500> is<00:27:43.620> an<00:27:43.799> example<00:27:44.100> of<00:27:44.340> a<00:27:44.580> bimodular<00:27:45.360> data 00:27:45.890 --> 00:27:45.900 align:start position:0% this is an example of a bimodular data 00:27:45.900 --> 00:27:49.010 align:start position:0% this is an example of a bimodular data accepts<00:27:46.340> accessor<00:27:47.340> the<00:27:47.700> way<00:27:47.820> you<00:27:48.179> can<00:27:48.360> think 00:27:49.010 --> 00:27:49.020 align:start position:0% accepts accessor the way you can think 00:27:49.020 --> 00:27:52.130 align:start position:0% accepts accessor the way you can think about<00:27:49.260> it<00:27:49.559> is<00:27:50.159> as<00:27:50.340> a<00:27:50.520> process<00:27:50.820> that<00:27:51.059> says<00:27:51.480> if 00:27:52.130 --> 00:27:52.140 align:start position:0% about it is as a process that says if 00:27:52.140 --> 00:27:54.769 align:start position:0% about it is as a process that says if you<00:27:52.260> give<00:27:52.380> me<00:27:52.500> an<00:27:52.679> a<00:27:52.860> I<00:27:53.220> will<00:27:53.400> read<00:27:53.580> field<00:27:54.000> s<00:27:54.419> and 00:27:54.769 --> 00:27:54.779 align:start position:0% you give me an a I will read field s and 00:27:54.779 --> 00:27:57.350 align:start position:0% you give me an a I will read field s and forward<00:27:55.080> the<00:27:55.500> output<00:27:55.799> to<00:27:56.039> you<00:27:56.220> and<00:27:57.059> if<00:27:57.179> someone 00:27:57.350 --> 00:27:57.360 align:start position:0% forward the output to you and if someone 00:27:57.360 --> 00:28:00.350 align:start position:0% forward the output to you and if someone else<00:27:57.600> from<00:27:57.960> the<00:27:58.140> future<00:27:58.320> will<00:27:58.980> give<00:27:59.220> me<00:27:59.400> a<00:27:59.640> t<00:27:59.820> i 00:28:00.350 --> 00:28:00.360 align:start position:0% else from the future will give me a t i 00:28:00.360 --> 00:28:03.110 align:start position:0% else from the future will give me a t i will<00:28:00.539> replace<00:28:00.779> S<00:28:01.380> in<00:28:01.679> a<00:28:01.919> with<00:28:02.159> it<00:28:02.340> and<00:28:02.580> return<00:28:02.760> u 00:28:03.110 --> 00:28:03.120 align:start position:0% will replace S in a with it and return u 00:28:03.120 --> 00:28:05.570 align:start position:0% will replace S in a with it and return u a<00:28:03.299> b<00:28:03.419> and<00:28:04.140> the<00:28:04.320> good<00:28:04.500> thing<00:28:04.679> about<00:28:04.860> it<00:28:05.100> is<00:28:05.279> now 00:28:05.570 --> 00:28:05.580 align:start position:0% a b and the good thing about it is now 00:28:05.580 --> 00:28:08.210 align:start position:0% a b and the good thing about it is now you<00:28:06.179> can<00:28:06.299> compose<00:28:06.720> them<00:28:07.020> exactly<00:28:07.799> as<00:28:07.980> you 00:28:08.210 --> 00:28:08.220 align:start position:0% you can compose them exactly as you 00:28:08.220 --> 00:28:10.970 align:start position:0% you can compose them exactly as you composed<00:28:08.820> the<00:28:09.419> processes<00:28:09.900> we<00:28:10.200> sew<00:28:10.440> up<00:28:10.559> to<00:28:10.740> now 00:28:10.970 --> 00:28:10.980 align:start position:0% composed the processes we sew up to now 00:28:10.980 --> 00:28:13.789 align:start position:0% composed the processes we sew up to now and<00:28:11.940> when<00:28:12.179> you<00:28:12.360> do<00:28:12.539> this<00:28:12.779> if<00:28:13.140> you<00:28:13.260> squint<00:28:13.620> your 00:28:13.789 --> 00:28:13.799 align:start position:0% and when you do this if you squint your 00:28:13.799 --> 00:28:15.590 align:start position:0% and when you do this if you squint your eyes<00:28:13.980> a<00:28:14.220> bit<00:28:14.340> you<00:28:14.640> see<00:28:14.820> that<00:28:15.000> we<00:28:15.240> are<00:28:15.419> doing 00:28:15.590 --> 00:28:15.600 align:start position:0% eyes a bit you see that we are doing 00:28:15.600 --> 00:28:17.990 align:start position:0% eyes a bit you see that we are doing something<00:28:16.020> that<00:28:16.380> is<00:28:16.559> basically<00:28:17.000> equivalent 00:28:17.990 --> 00:28:18.000 align:start position:0% something that is basically equivalent 00:28:18.000 --> 00:28:19.909 align:start position:0% something that is basically equivalent at<00:28:18.240> that<00:28:18.779> um<00:28:18.840> to<00:28:19.140> that<00:28:19.320> cumbersome 00:28:19.909 --> 00:28:19.919 align:start position:0% at that um to that cumbersome 00:28:19.919 --> 00:28:22.610 align:start position:0% at that um to that cumbersome composition<00:28:20.400> we<00:28:20.700> had<00:28:20.880> before<00:28:21.200> but<00:28:22.200> now<00:28:22.440> is 00:28:22.610 --> 00:28:22.620 align:start position:0% composition we had before but now is 00:28:22.620 --> 00:28:24.409 align:start position:0% composition we had before but now is again<00:28:22.799> graphical<00:28:23.400> like<00:28:23.700> you<00:28:24.000> can<00:28:24.120> just 00:28:24.409 --> 00:28:24.419 align:start position:0% again graphical like you can just 00:28:24.419 --> 00:28:27.289 align:start position:0% again graphical like you can just compose<00:28:25.260> these<00:28:25.679> Lego<00:28:25.740> bricks<00:28:26.220> together 00:28:27.289 --> 00:28:27.299 align:start position:0% compose these Lego bricks together 00:28:27.299 --> 00:28:29.810 align:start position:0% compose these Lego bricks together again<00:28:28.140> and<00:28:28.860> this<00:28:29.039> is<00:28:29.220> the<00:28:29.400> art<00:28:29.580> of 00:28:29.810 --> 00:28:29.820 align:start position:0% again and this is the art of 00:28:29.820 --> 00:28:31.909 align:start position:0% again and this is the art of compositionality<00:28:30.659> anything<00:28:31.440> that<00:28:31.740> really 00:28:31.909 --> 00:28:31.919 align:start position:0% compositionality anything that really 00:28:31.919 --> 00:28:35.330 align:start position:0% compositionality anything that really changing<00:28:32.400> is<00:28:32.940> the<00:28:33.360> point<00:28:33.480> of<00:28:33.659> view<00:28:33.840> so<00:28:34.620> you<00:28:35.220> can 00:28:35.330 --> 00:28:35.340 align:start position:0% changing is the point of view so you can 00:28:35.340 --> 00:28:38.210 align:start position:0% changing is the point of view so you can still<00:28:35.820> deform<00:28:36.539> this<00:28:37.200> thing<00:28:37.440> in<00:28:37.620> another<00:28:37.860> way 00:28:38.210 --> 00:28:38.220 align:start position:0% still deform this thing in another way 00:28:38.220 --> 00:28:42.350 align:start position:0% still deform this thing in another way I'm<00:28:39.179> just<00:28:39.419> rewriting<00:28:40.140> the<00:28:40.740> top<00:28:40.919> diagram<00:28:41.360> as 00:28:42.350 --> 00:28:42.360 align:start position:0% I'm just rewriting the top diagram as 00:28:42.360 --> 00:28:44.690 align:start position:0% I'm just rewriting the top diagram as the<00:28:42.600> bottom<00:28:42.960> diagram<00:28:43.260> if<00:28:43.559> you<00:28:43.740> see<00:28:43.980> the 00:28:44.690 --> 00:28:44.700 align:start position:0% the bottom diagram if you see the 00:28:44.700 --> 00:28:46.909 align:start position:0% the bottom diagram if you see the interconnectivity<00:28:45.480> of<00:28:45.720> the<00:28:45.900> diagram<00:28:46.500> didn't 00:28:46.909 --> 00:28:46.919 align:start position:0% interconnectivity of the diagram didn't 00:28:46.919 --> 00:28:48.470 align:start position:0% interconnectivity of the diagram didn't change 00:28:48.470 --> 00:28:48.480 align:start position:0% change 00:28:48.480 --> 00:28:51.169 align:start position:0% change and<00:28:48.900> I<00:28:49.020> can<00:28:49.140> shape<00:28:49.440> it<00:28:49.620> as<00:28:49.919> a<00:28:50.159> comb<00:28:50.520> basically 00:28:51.169 --> 00:28:51.179 align:start position:0% and I can shape it as a comb basically 00:28:51.179 --> 00:28:53.810 align:start position:0% and I can shape it as a comb basically and<00:28:51.720> again<00:28:52.020> it's<00:28:52.320> the<00:28:52.559> same<00:28:52.679> like<00:28:52.980> you<00:28:53.159> get<00:28:53.400> a 00:28:53.810 --> 00:28:53.820 align:start position:0% and again it's the same like you get a 00:28:53.820 --> 00:28:57.230 align:start position:0% and again it's the same like you get a in<00:28:54.419> you<00:28:55.020> get<00:28:55.140> an<00:28:55.380> S<00:28:55.620> out<00:28:55.919> then<00:28:56.340> you<00:28:56.520> get<00:28:56.640> a<00:28:56.820> t<00:28:57.000> in 00:28:57.230 --> 00:28:57.240 align:start position:0% in you get an S out then you get a t in 00:28:57.240 --> 00:29:00.470 align:start position:0% in you get an S out then you get a t in and<00:28:57.600> then<00:28:57.720> you<00:28:57.900> get<00:28:58.020> a<00:28:58.200> B<00:28:58.380> out<00:28:58.940> these<00:28:59.940> is<00:29:00.240> really 00:29:00.470 --> 00:29:00.480 align:start position:0% and then you get a B out these is really 00:29:00.480 --> 00:29:02.029 align:start position:0% and then you get a B out these is really interesting<00:29:00.900> because<00:29:01.140> when<00:29:01.500> you<00:29:01.620> look<00:29:01.799> at 00:29:02.029 --> 00:29:02.039 align:start position:0% interesting because when you look at 00:29:02.039 --> 00:29:04.430 align:start position:0% interesting because when you look at this<00:29:02.340> comp<00:29:02.640> process<00:29:03.059> it<00:29:03.779> really<00:29:03.900> looks<00:29:04.260> like 00:29:04.430 --> 00:29:04.440 align:start position:0% this comp process it really looks like 00:29:04.440 --> 00:29:06.590 align:start position:0% this comp process it really looks like something<00:29:04.860> that<00:29:05.220> wants<00:29:05.520> to<00:29:05.580> be<00:29:05.820> a<00:29:06.419> normal 00:29:06.590 --> 00:29:06.600 align:start position:0% something that wants to be a normal 00:29:06.600 --> 00:29:09.830 align:start position:0% something that wants to be a normal function<00:29:07.400> but<00:29:08.400> it<00:29:08.880> can't<00:29:09.059> because<00:29:09.480> it's 00:29:09.830 --> 00:29:09.840 align:start position:0% function but it can't because it's 00:29:09.840 --> 00:29:11.769 align:start position:0% function but it can't because it's waiting<00:29:10.260> for<00:29:10.440> you<00:29:10.559> to<00:29:10.740> do<00:29:10.860> something 00:29:11.769 --> 00:29:11.779 align:start position:0% waiting for you to do something 00:29:11.779 --> 00:29:14.029 align:start position:0% waiting for you to do something intuitively<00:29:12.779> if<00:29:12.960> you<00:29:13.080> have<00:29:13.260> an<00:29:13.380> automated<00:29:13.740> way 00:29:14.029 --> 00:29:14.039 align:start position:0% intuitively if you have an automated way 00:29:14.039 --> 00:29:17.390 align:start position:0% intuitively if you have an automated way to<00:29:14.220> turn<00:29:14.460> S<00:29:15.120> into<00:29:15.480> T<00:29:15.900> that<00:29:16.799> thing<00:29:16.980> would<00:29:17.220> just 00:29:17.390 --> 00:29:17.400 align:start position:0% to turn S into T that thing would just 00:29:17.400 --> 00:29:20.090 align:start position:0% to turn S into T that thing would just be<00:29:17.640> one<00:29:17.880> of<00:29:18.000> those<00:29:18.240> naive<00:29:19.080> building<00:29:19.440> blocks<00:29:19.919> we 00:29:20.090 --> 00:29:20.100 align:start position:0% be one of those naive building blocks we 00:29:20.100 --> 00:29:22.730 align:start position:0% be one of those naive building blocks we saw<00:29:20.279> in<00:29:20.460> the<00:29:20.640> beginning 00:29:22.730 --> 00:29:22.740 align:start position:0% saw in the beginning 00:29:22.740 --> 00:29:25.310 align:start position:0% saw in the beginning and<00:29:23.460> you<00:29:23.700> know<00:29:23.760> in<00:29:24.059> this<00:29:24.240> framework<00:29:24.659> the 00:29:25.310 --> 00:29:25.320 align:start position:0% and you know in this framework the 00:29:25.320 --> 00:29:27.830 align:start position:0% and you know in this framework the composition<00:29:25.799> will<00:29:26.159> be<00:29:26.279> nested<00:29:26.760> he<00:29:27.539> would<00:29:27.720> be 00:29:27.830 --> 00:29:27.840 align:start position:0% composition will be nested he would be 00:29:27.840 --> 00:29:30.830 align:start position:0% composition will be nested he would be of<00:29:28.080> this<00:29:28.500> sort<00:29:28.760> you<00:29:29.760> are<00:29:29.940> basically<00:29:30.240> composing 00:29:30.830 --> 00:29:30.840 align:start position:0% of this sort you are basically composing 00:29:30.840 --> 00:29:34.130 align:start position:0% of this sort you are basically composing comms<00:29:31.440> by<00:29:32.279> substituting<00:29:32.940> a<00:29:33.240> comb<00:29:33.659> in<00:29:34.020> the 00:29:34.130 --> 00:29:34.140 align:start position:0% comms by substituting a comb in the 00:29:34.140 --> 00:29:35.690 align:start position:0% comms by substituting a comb in the whole<00:29:34.260> of<00:29:34.500> the<00:29:34.620> bigger<00:29:34.919> comp 00:29:35.690 --> 00:29:35.700 align:start position:0% whole of the bigger comp 00:29:35.700 --> 00:29:37.970 align:start position:0% whole of the bigger comp and<00:29:36.120> again<00:29:36.240> this<00:29:36.600> composition<00:29:37.080> is<00:29:37.440> exactly 00:29:37.970 --> 00:29:37.980 align:start position:0% and again this composition is exactly 00:29:37.980 --> 00:29:40.610 align:start position:0% and again this composition is exactly the<00:29:38.880> same<00:29:39.000> when<00:29:39.419> you<00:29:39.600> follow<00:29:39.840> the<00:29:40.260> the 00:29:40.610 --> 00:29:40.620 align:start position:0% the same when you follow the the 00:29:40.620 --> 00:29:42.889 align:start position:0% the same when you follow the the processes<00:29:41.220> and<00:29:41.399> the<00:29:41.580> interconnections<00:29:42.299> of 00:29:42.889 --> 00:29:42.899 align:start position:0% processes and the interconnections of 00:29:42.899 --> 00:29:45.830 align:start position:0% processes and the interconnections of this<00:29:43.140> one<00:29:43.380> this<00:29:44.279> one<00:29:44.460> and<00:29:44.880> this<00:29:45.059> one<00:29:45.240> are<00:29:45.600> the 00:29:45.830 --> 00:29:45.840 align:start position:0% this one this one and this one are the 00:29:45.840 --> 00:29:48.950 align:start position:0% this one this one and this one are the same<00:29:46.020> thing<00:29:46.200> we<00:29:46.799> just<00:29:47.039> deformed<00:29:48.000> the<00:29:48.539> way<00:29:48.720> we 00:29:48.950 --> 00:29:48.960 align:start position:0% same thing we just deformed the way we 00:29:48.960 --> 00:29:51.110 align:start position:0% same thing we just deformed the way we arrange<00:29:49.260> the<00:29:49.380> diagrams 00:29:51.110 --> 00:29:51.120 align:start position:0% arrange the diagrams 00:29:51.120 --> 00:29:54.289 align:start position:0% arrange the diagrams now<00:29:52.020> again<00:29:52.679> as<00:29:52.980> I<00:29:53.100> said<00:29:53.279> you<00:29:53.520> can<00:29:53.640> see<00:29:53.820> a<00:29:53.940> comb 00:29:54.289 --> 00:29:54.299 align:start position:0% now again as I said you can see a comb 00:29:54.299 --> 00:29:56.049 align:start position:0% now again as I said you can see a comb as<00:29:54.360> an<00:29:54.539> incomplete<00:29:55.080> process 00:29:56.049 --> 00:29:56.059 align:start position:0% as an incomplete process 00:29:56.059 --> 00:29:58.549 align:start position:0% as an incomplete process that<00:29:57.059> basically<00:29:57.360> is<00:29:57.539> waiting<00:29:57.899> for<00:29:58.080> you<00:29:58.200> to<00:29:58.380> do 00:29:58.549 --> 00:29:58.559 align:start position:0% that basically is waiting for you to do 00:29:58.559 --> 00:30:01.070 align:start position:0% that basically is waiting for you to do something<00:29:59.039> to<00:29:59.399> turn<00:29:59.520> a<00:29:59.700> nest<00:29:59.940> into<00:30:00.120> a<00:30:00.360> t<00:30:00.480> and 00:30:01.070 --> 00:30:01.080 align:start position:0% something to turn a nest into a t and 00:30:01.080 --> 00:30:02.750 align:start position:0% something to turn a nest into a t and that<00:30:01.260> would<00:30:01.380> be<00:30:01.500> that<00:30:01.740> F<00:30:01.980> that<00:30:02.220> you<00:30:02.399> put<00:30:02.520> there 00:30:02.750 --> 00:30:02.760 align:start position:0% that would be that F that you put there 00:30:02.760 --> 00:30:04.789 align:start position:0% that would be that F that you put there and<00:30:03.240> if<00:30:03.360> you<00:30:03.480> put<00:30:03.720> it<00:30:03.840> there<00:30:04.080> this<00:30:04.620> thing 00:30:04.789 --> 00:30:04.799 align:start position:0% and if you put it there this thing 00:30:04.799 --> 00:30:07.850 align:start position:0% and if you put it there this thing basically<00:30:05.159> closes<00:30:05.640> up<00:30:05.820> and<00:30:06.120> just<00:30:06.419> becomes<00:30:07.020> a 00:30:07.850 --> 00:30:07.860 align:start position:0% basically closes up and just becomes a 00:30:07.860 --> 00:30:09.409 align:start position:0% basically closes up and just becomes a normal<00:30:08.039> process 00:30:09.409 --> 00:30:09.419 align:start position:0% normal process 00:30:09.419 --> 00:30:11.029 align:start position:0% normal process but<00:30:09.899> what<00:30:10.140> is<00:30:10.320> really<00:30:10.500> interesting<00:30:10.860> about 00:30:11.029 --> 00:30:11.039 align:start position:0% but what is really interesting about 00:30:11.039 --> 00:30:12.169 align:start position:0% but what is really interesting about this 00:30:12.169 --> 00:30:12.179 align:start position:0% this 00:30:12.179 --> 00:30:15.230 align:start position:0% this is<00:30:12.539> that<00:30:12.720> we<00:30:12.899> found<00:30:13.080> a<00:30:13.380> pattern<00:30:13.799> so<00:30:14.159> we<00:30:14.880> started 00:30:15.230 --> 00:30:15.240 align:start position:0% is that we found a pattern so we started 00:30:15.240 --> 00:30:19.250 align:start position:0% is that we found a pattern so we started by<00:30:15.559> modeling<00:30:16.700> record<00:30:17.700> rewriting<00:30:18.480> but<00:30:18.899> now<00:30:19.080> we 00:30:19.250 --> 00:30:19.260 align:start position:0% by modeling record rewriting but now we 00:30:19.260 --> 00:30:21.289 align:start position:0% by modeling record rewriting but now we found<00:30:19.440> a<00:30:19.740> new<00:30:19.919> pattern<00:30:20.340> of<00:30:20.520> composition<00:30:21.000> that 00:30:21.289 --> 00:30:21.299 align:start position:0% found a new pattern of composition that 00:30:21.299 --> 00:30:24.350 align:start position:0% found a new pattern of composition that is<00:30:21.539> this<00:30:21.720> kind<00:30:21.899> of<00:30:22.020> nested<00:30:22.620> composition<00:30:23.460> and 00:30:24.350 --> 00:30:24.360 align:start position:0% is this kind of nested composition and 00:30:24.360 --> 00:30:26.029 align:start position:0% is this kind of nested composition and indeed<00:30:24.600> there<00:30:24.899> are<00:30:25.020> a<00:30:25.200> lot<00:30:25.320> of<00:30:25.500> things<00:30:25.740> that 00:30:26.029 --> 00:30:26.039 align:start position:0% indeed there are a lot of things that 00:30:26.039 --> 00:30:28.970 align:start position:0% indeed there are a lot of things that compose<00:30:26.460> in<00:30:27.179> this<00:30:27.360> way<00:30:27.539> if<00:30:28.140> you<00:30:28.260> abstract<00:30:28.679> from 00:30:28.970 --> 00:30:28.980 align:start position:0% compose in this way if you abstract from 00:30:28.980 --> 00:30:30.950 align:start position:0% compose in this way if you abstract from details<00:30:29.520> for<00:30:29.700> a<00:30:29.820> second 00:30:30.950 --> 00:30:30.960 align:start position:0% details for a second 00:30:30.960 --> 00:30:32.990 align:start position:0% details for a second these<00:30:31.740> two<00:30:31.860> processes<00:30:32.399> are<00:30:32.700> basically 00:30:32.990 --> 00:30:33.000 align:start position:0% these two processes are basically 00:30:33.000 --> 00:30:35.389 align:start position:0% these two processes are basically representing<00:30:33.840> two<00:30:34.679> different<00:30:34.919> points<00:30:35.279> of 00:30:35.389 --> 00:30:35.399 align:start position:0% representing two different points of 00:30:35.399 --> 00:30:37.070 align:start position:0% representing two different points of view<00:30:35.520> of<00:30:35.700> the<00:30:35.940> same<00:30:36.059> thing<00:30:36.240> that<00:30:36.840> is 00:30:37.070 --> 00:30:37.080 align:start position:0% view of the same thing that is 00:30:37.080 --> 00:30:39.649 align:start position:0% view of the same thing that is bi-directional<00:30:37.740> transformations 00:30:39.649 --> 00:30:39.659 align:start position:0% bi-directional transformations 00:30:39.659 --> 00:30:42.409 align:start position:0% bi-directional transformations now<00:30:40.380> let<00:30:40.740> me<00:30:40.860> give<00:30:41.039> you<00:30:41.159> an<00:30:41.399> example<00:30:41.700> of<00:30:42.000> how 00:30:42.409 --> 00:30:42.419 align:start position:0% now let me give you an example of how 00:30:42.419 --> 00:30:44.149 align:start position:0% now let me give you an example of how you<00:30:42.600> can<00:30:42.720> use<00:30:42.899> these<00:30:43.260> things 00:30:44.149 --> 00:30:44.159 align:start position:0% you can use these things 00:30:44.159 --> 00:30:47.870 align:start position:0% you can use these things an<00:30:44.700> example<00:30:45.059> would<00:30:46.020> be<00:30:46.140> estrus<00:30:46.679> what<00:30:47.580> is<00:30:47.760> an 00:30:47.870 --> 00:30:47.880 align:start position:0% an example would be estrus what is an 00:30:47.880 --> 00:30:50.330 align:start position:0% an example would be estrus what is an escrow<00:30:48.240> trade<00:30:48.539> an<00:30:48.779> escrow<00:30:49.080> trade<00:30:49.440> is<00:30:49.679> when<00:30:49.980> I 00:30:50.330 --> 00:30:50.340 align:start position:0% escrow trade an escrow trade is when I 00:30:50.340 --> 00:30:52.430 align:start position:0% escrow trade an escrow trade is when I want<00:30:50.399> to<00:30:50.520> give<00:30:50.700> something<00:30:51.000> to<00:30:51.299> someone<00:30:51.539> but<00:30:52.320> I 00:30:52.430 --> 00:30:52.440 align:start position:0% want to give something to someone but I 00:30:52.440 --> 00:30:54.110 align:start position:0% want to give something to someone but I don't<00:30:52.559> trust<00:30:52.860> that<00:30:53.039> someone<00:30:53.340> or<00:30:53.760> that<00:30:53.880> someone 00:30:54.110 --> 00:30:54.120 align:start position:0% don't trust that someone or that someone 00:30:54.120 --> 00:30:56.750 align:start position:0% don't trust that someone or that someone doesn't<00:30:54.419> trust<00:30:54.779> me<00:30:54.960> and<00:30:55.620> so<00:30:55.740> what<00:30:55.919> I<00:30:56.100> do<00:30:56.220> is<00:30:56.399> I 00:30:56.750 --> 00:30:56.760 align:start position:0% doesn't trust me and so what I do is I 00:30:56.760 --> 00:30:58.730 align:start position:0% doesn't trust me and so what I do is I take<00:30:56.940> my<00:30:57.240> funds<00:30:57.600> instead<00:30:58.020> of<00:30:58.140> giving<00:30:58.440> them 00:30:58.730 --> 00:30:58.740 align:start position:0% take my funds instead of giving them 00:30:58.740 --> 00:31:02.029 align:start position:0% take my funds instead of giving them directly<00:30:59.279> I<00:30:59.820> lock<00:31:00.059> them<00:31:00.299> up<00:31:00.539> in<00:31:01.020> a<00:31:01.140> vault 00:31:02.029 --> 00:31:02.039 align:start position:0% directly I lock them up in a vault 00:31:02.039 --> 00:31:05.289 align:start position:0% directly I lock them up in a vault and<00:31:02.700> then<00:31:02.820> basically<00:31:03.299> you<00:31:03.659> know<00:31:03.860> my 00:31:05.289 --> 00:31:05.299 align:start position:0% and then basically you know my 00:31:05.299 --> 00:31:08.389 align:start position:0% and then basically you know my counterparty<00:31:06.299> will<00:31:06.840> ship<00:31:07.080> me<00:31:07.320> some<00:31:07.620> goods<00:31:07.980> and 00:31:08.389 --> 00:31:08.399 align:start position:0% counterparty will ship me some goods and 00:31:08.399 --> 00:31:10.789 align:start position:0% counterparty will ship me some goods and when<00:31:08.580> I<00:31:08.820> receive<00:31:09.059> them<00:31:09.360> I<00:31:09.840> will<00:31:10.020> confirm<00:31:10.559> that 00:31:10.789 --> 00:31:10.799 align:start position:0% when I receive them I will confirm that 00:31:10.799 --> 00:31:13.130 align:start position:0% when I receive them I will confirm that I<00:31:10.980> received<00:31:11.399> them<00:31:11.520> and<00:31:11.820> at<00:31:12.000> that<00:31:12.240> point<00:31:12.480> my 00:31:13.130 --> 00:31:13.140 align:start position:0% I received them and at that point my 00:31:13.140 --> 00:31:15.889 align:start position:0% I received them and at that point my funds<00:31:13.500> are<00:31:13.620> unlocked<00:31:14.100> and<00:31:14.640> forwarded<00:31:15.179> and 00:31:15.889 --> 00:31:15.899 align:start position:0% funds are unlocked and forwarded and 00:31:15.899 --> 00:31:18.350 align:start position:0% funds are unlocked and forwarded and that<00:31:16.140> is<00:31:16.320> exactly<00:31:16.860> a<00:31:17.399> calm<00:31:17.760> looking<00:31:17.940> thing 00:31:18.350 --> 00:31:18.360 align:start position:0% that is exactly a calm looking thing 00:31:18.360 --> 00:31:21.649 align:start position:0% that is exactly a calm looking thing it's<00:31:19.080> like<00:31:19.380> I<00:31:20.159> committed<00:31:20.580> my<00:31:20.760> funds<00:31:21.120> I<00:31:21.299> locked 00:31:21.649 --> 00:31:21.659 align:start position:0% it's like I committed my funds I locked 00:31:21.659 --> 00:31:22.850 align:start position:0% it's like I committed my funds I locked them<00:31:21.779> and<00:31:22.020> now<00:31:22.200> I'm<00:31:22.320> waiting<00:31:22.679> for 00:31:22.850 --> 00:31:22.860 align:start position:0% them and now I'm waiting for 00:31:22.860 --> 00:31:24.710 align:start position:0% them and now I'm waiting for confirmation<00:31:23.460> and<00:31:23.760> as<00:31:23.940> soon<00:31:24.120> as<00:31:24.240> you<00:31:24.419> give<00:31:24.600> me 00:31:24.710 --> 00:31:24.720 align:start position:0% confirmation and as soon as you give me 00:31:24.720 --> 00:31:28.010 align:start position:0% confirmation and as soon as you give me confirmation<00:31:25.380> and<00:31:26.039> you<00:31:26.220> put<00:31:26.460> it<00:31:26.580> in.com<00:31:27.120> then 00:31:28.010 --> 00:31:28.020 align:start position:0% confirmation and you put it in.com then 00:31:28.020 --> 00:31:29.690 align:start position:0% confirmation and you put it in.com then this<00:31:28.260> looks<00:31:28.559> like<00:31:28.740> a<00:31:28.980> standard<00:31:29.340> transaction 00:31:29.690 --> 00:31:29.700 align:start position:0% this looks like a standard transaction 00:31:29.700 --> 00:31:31.970 align:start position:0% this looks like a standard transaction from<00:31:30.120> A<00:31:30.360> to<00:31:30.539> B 00:31:31.970 --> 00:31:31.980 align:start position:0% from A to B 00:31:31.980 --> 00:31:35.510 align:start position:0% from A to B another<00:31:32.640> example<00:31:33.240> and<00:31:33.779> this<00:31:34.080> will<00:31:34.380> be<00:31:34.860> the 00:31:35.510 --> 00:31:35.520 align:start position:0% another example and this will be the 00:31:35.520 --> 00:31:36.230 align:start position:0% another example and this will be the main 00:31:36.230 --> 00:31:36.240 align:start position:0% main 00:31:36.240 --> 00:31:38.510 align:start position:0% main point<00:31:36.960> of<00:31:37.140> the<00:31:37.380> second<00:31:37.559> part<00:31:37.980> that<00:31:38.340> my 00:31:38.510 --> 00:31:38.520 align:start position:0% point of the second part that my 00:31:38.520 --> 00:31:41.269 align:start position:0% point of the second part that my colleague<00:31:38.820> Philip<00:31:39.240> will<00:31:39.419> do<00:31:39.600> is<00:31:40.500> Game<00:31:40.799> Theory 00:31:41.269 --> 00:31:41.279 align:start position:0% colleague Philip will do is Game Theory 00:31:41.279 --> 00:31:42.710 align:start position:0% colleague Philip will do is Game Theory so 00:31:42.710 --> 00:31:42.720 align:start position:0% so 00:31:42.720 --> 00:31:46.549 align:start position:0% so we<00:31:43.380> can<00:31:43.559> model<00:31:43.799> games<00:31:44.460> in<00:31:45.360> Game<00:31:45.539> Theory<00:31:46.020> as<00:31:46.320> op 00:31:46.549 --> 00:31:46.559 align:start position:0% we can model games in Game Theory as op 00:31:46.559 --> 00:31:48.889 align:start position:0% we can model games in Game Theory as op as<00:31:46.980> open<00:31:47.100> processes<00:31:47.820> basically 00:31:48.889 --> 00:31:48.899 align:start position:0% as open processes basically 00:31:48.899 --> 00:31:50.990 align:start position:0% as open processes basically in<00:31:49.380> that<00:31:49.500> case<00:31:49.679> a<00:31:49.919> game<00:31:50.039> will<00:31:50.279> be<00:31:50.399> a<00:31:50.640> process 00:31:50.990 --> 00:31:51.000 align:start position:0% in that case a game will be a process 00:31:51.000 --> 00:31:53.269 align:start position:0% in that case a game will be a process that<00:31:51.480> has<00:31:51.720> again<00:31:52.080> two<00:31:52.500> inputs<00:31:53.039> and<00:31:53.100> two 00:31:53.269 --> 00:31:53.279 align:start position:0% that has again two inputs and two 00:31:53.279 --> 00:31:54.529 align:start position:0% that has again two inputs and two outputs 00:31:54.529 --> 00:31:54.539 align:start position:0% outputs 00:31:54.539 --> 00:31:57.889 align:start position:0% outputs it<00:31:55.020> will<00:31:55.200> take<00:31:55.500> in<00:31:55.919> input<00:31:56.279> and<00:31:56.460> observation<00:31:57.059> so 00:31:57.889 --> 00:31:57.899 align:start position:0% it will take in input and observation so 00:31:57.899 --> 00:32:00.769 align:start position:0% it will take in input and observation so it<00:31:58.320> will<00:31:58.500> observe<00:31:58.980> the<00:31:59.159> word<00:31:59.340> it<00:32:00.240> will<00:32:00.419> spit 00:32:00.769 --> 00:32:00.779 align:start position:0% it will observe the word it will spit 00:32:00.779 --> 00:32:03.649 align:start position:0% it will observe the word it will spit out<00:32:01.020> an<00:32:01.440> action<00:32:01.679> According<00:32:02.279> to<00:32:02.520> some<00:32:02.880> strategy 00:32:03.649 --> 00:32:03.659 align:start position:0% out an action According to some strategy 00:32:03.659 --> 00:32:06.649 align:start position:0% out an action According to some strategy if<00:32:04.559> we<00:32:04.799> receive<00:32:05.100> a<00:32:05.340> payoff<00:32:05.760> from<00:32:06.240> the<00:32:06.480> outside 00:32:06.649 --> 00:32:06.659 align:start position:0% if we receive a payoff from the outside 00:32:06.659 --> 00:32:07.970 align:start position:0% if we receive a payoff from the outside world 00:32:07.970 --> 00:32:07.980 align:start position:0% world 00:32:07.980 --> 00:32:10.490 align:start position:0% world and<00:32:08.640> you<00:32:08.820> will<00:32:08.940> return<00:32:09.120> a<00:32:09.480> feedback 00:32:10.490 --> 00:32:10.500 align:start position:0% and you will return a feedback 00:32:10.500 --> 00:32:12.169 align:start position:0% and you will return a feedback the<00:32:10.980> feedback<00:32:11.279> is<00:32:11.520> probably<00:32:11.700> the<00:32:12.000> most 00:32:12.169 --> 00:32:12.179 align:start position:0% the feedback is probably the most 00:32:12.179 --> 00:32:13.610 align:start position:0% the feedback is probably the most difficult<00:32:12.539> part<00:32:12.840> to<00:32:13.020> get<00:32:13.200> in<00:32:13.440> this 00:32:13.610 --> 00:32:13.620 align:start position:0% difficult part to get in this 00:32:13.620 --> 00:32:15.470 align:start position:0% difficult part to get in this composition<00:32:14.100> method<00:32:14.580> and<00:32:14.880> you<00:32:15.120> have<00:32:15.240> to 00:32:15.470 --> 00:32:15.480 align:start position:0% composition method and you have to 00:32:15.480 --> 00:32:18.350 align:start position:0% composition method and you have to imagine<00:32:16.200> it<00:32:16.559> one<00:32:17.100> of<00:32:17.220> the<00:32:17.340> ways<00:32:17.700> to<00:32:17.760> imagine<00:32:18.000> it 00:32:18.350 --> 00:32:18.360 align:start position:0% imagine it one of the ways to imagine it 00:32:18.360 --> 00:32:20.810 align:start position:0% imagine it one of the ways to imagine it is<00:32:18.659> is<00:32:19.200> the<00:32:19.500> portion<00:32:19.860> of<00:32:19.980> your<00:32:20.159> payoff<00:32:20.580> that 00:32:20.810 --> 00:32:20.820 align:start position:0% is is the portion of your payoff that 00:32:20.820 --> 00:32:23.450 align:start position:0% is is the portion of your payoff that you<00:32:20.940> have<00:32:21.059> to<00:32:21.179> return<00:32:21.480> to<00:32:22.140> someone<00:32:22.320> else 00:32:23.450 --> 00:32:23.460 align:start position:0% you have to return to someone else 00:32:23.460 --> 00:32:25.789 align:start position:0% you have to return to someone else stupid<00:32:23.940> example<00:32:24.419> if<00:32:24.659> you<00:32:24.779> take<00:32:24.960> a<00:32:25.140> depth<00:32:25.500> you 00:32:25.789 --> 00:32:25.799 align:start position:0% stupid example if you take a depth you 00:32:25.799 --> 00:32:28.310 align:start position:0% stupid example if you take a depth you place<00:32:26.039> a<00:32:26.340> bet<00:32:26.460> you<00:32:27.059> win<00:32:27.240> you<00:32:27.659> get<00:32:27.779> a<00:32:27.960> payoff 00:32:28.310 --> 00:32:28.320 align:start position:0% place a bet you win you get a payoff 00:32:28.320 --> 00:32:30.710 align:start position:0% place a bet you win you get a payoff that<00:32:28.620> you<00:32:28.740> have<00:32:28.860> to<00:32:28.980> repay<00:32:29.340> the<00:32:29.520> debt<00:32:29.880> and<00:32:30.600> the 00:32:30.710 --> 00:32:30.720 align:start position:0% that you have to repay the debt and the 00:32:30.720 --> 00:32:32.450 align:start position:0% that you have to repay the debt and the debt<00:32:31.020> repayment<00:32:31.500> would<00:32:31.740> be<00:32:31.860> the<00:32:32.100> feedback 00:32:32.450 --> 00:32:32.460 align:start position:0% debt repayment would be the feedback 00:32:32.460 --> 00:32:34.570 align:start position:0% debt repayment would be the feedback wire 00:32:34.570 --> 00:32:34.580 align:start position:0% wire 00:32:34.580 --> 00:32:37.130 align:start position:0% wire in<00:32:35.580> this<00:32:35.760> system<00:32:35.940> of<00:32:36.360> compositional<00:32:36.960> Game 00:32:37.130 --> 00:32:37.140 align:start position:0% in this system of compositional Game 00:32:37.140 --> 00:32:38.090 align:start position:0% in this system of compositional Game Theory 00:32:38.090 --> 00:32:38.100 align:start position:0% Theory 00:32:38.100 --> 00:32:41.690 align:start position:0% Theory we<00:32:38.820> can<00:32:39.000> recover<00:32:39.799> traditional<00:32:40.799> games<00:32:41.039> as<00:32:41.520> a 00:32:41.690 --> 00:32:41.700 align:start position:0% we can recover traditional games as a 00:32:41.700 --> 00:32:43.430 align:start position:0% we can recover traditional games as a composition<00:32:42.059> of<00:32:42.299> processes 00:32:43.430 --> 00:32:43.440 align:start position:0% composition of processes 00:32:43.440 --> 00:32:45.409 align:start position:0% composition of processes so<00:32:43.980> this<00:32:44.159> for<00:32:44.340> instance<00:32:44.580> is<00:32:44.760> the<00:32:45.000> prisoner 00:32:45.409 --> 00:32:45.419 align:start position:0% so this for instance is the prisoner 00:32:45.419 --> 00:32:48.830 align:start position:0% so this for instance is the prisoner dilemma<00:32:45.899> uh<00:32:46.799> I<00:32:47.159> guess<00:32:47.340> a<00:32:47.580> game<00:32:47.820> most<00:32:48.659> of<00:32:48.779> you 00:32:48.830 --> 00:32:48.840 align:start position:0% dilemma uh I guess a game most of you 00:32:48.840 --> 00:32:51.289 align:start position:0% dilemma uh I guess a game most of you are<00:32:49.020> familiar<00:32:49.380> with<00:32:49.559> and<00:32:50.340> normally<00:32:50.640> we<00:32:50.940> see<00:32:51.120> it 00:32:51.289 --> 00:32:51.299 align:start position:0% are familiar with and normally we see it 00:32:51.299 --> 00:32:53.990 align:start position:0% are familiar with and normally we see it as<00:32:51.480> a<00:32:51.659> payoff<00:32:52.020> Matrix<00:32:52.500> and<00:32:52.799> you<00:32:52.919> know<00:32:53.039> like<00:32:53.279> if 00:32:53.990 --> 00:32:54.000 align:start position:0% as a payoff Matrix and you know like if 00:32:54.000 --> 00:32:55.850 align:start position:0% as a payoff Matrix and you know like if player<00:32:54.419> R<00:32:54.600> does<00:32:54.840> this<00:32:55.080> then<00:32:55.320> this<00:32:55.500> is<00:32:55.679> what 00:32:55.850 --> 00:32:55.860 align:start position:0% player R does this then this is what 00:32:55.860 --> 00:32:57.950 align:start position:0% player R does this then this is what happens<00:32:56.100> if<00:32:56.460> player<00:32:56.820> B<00:32:57.000> does<00:32:57.240> that<00:32:57.419> blah<00:32:57.779> blah 00:32:57.950 --> 00:32:57.960 align:start position:0% happens if player B does that blah blah 00:32:57.960 --> 00:33:00.649 align:start position:0% happens if player B does that blah blah blah<00:32:58.200> in<00:32:58.740> this<00:32:58.860> case<00:32:59.100> prisoner<00:33:00.059> dilemma<00:33:00.480> is 00:33:00.649 --> 00:33:00.659 align:start position:0% blah in this case prisoner dilemma is 00:33:00.659 --> 00:33:01.789 align:start position:0% blah in this case prisoner dilemma is the<00:33:00.840> composition<00:33:01.200> of<00:33:01.440> three<00:33:01.559> different 00:33:01.789 --> 00:33:01.799 align:start position:0% the composition of three different 00:33:01.799 --> 00:33:03.049 align:start position:0% the composition of three different processes 00:33:03.049 --> 00:33:03.059 align:start position:0% processes 00:33:03.059 --> 00:33:06.470 align:start position:0% processes player<00:33:03.960> one<00:33:04.080> player<00:33:04.679> two<00:33:04.860> and<00:33:05.700> payoff<00:33:06.120> Matrix 00:33:06.470 --> 00:33:06.480 align:start position:0% player one player two and payoff Matrix 00:33:06.480 --> 00:33:08.690 align:start position:0% player one player two and payoff Matrix these<00:33:06.960> three<00:33:07.080> things<00:33:07.320> in<00:33:07.620> isolations<00:33:08.159> are 00:33:08.690 --> 00:33:08.700 align:start position:0% these three things in isolations are 00:33:08.700 --> 00:33:09.889 align:start position:0% these three things in isolations are games 00:33:09.889 --> 00:33:09.899 align:start position:0% games 00:33:09.899 --> 00:33:12.830 align:start position:0% games player<00:33:10.679> one<00:33:10.799> and<00:33:10.980> player<00:33:11.279> two<00:33:11.460> are<00:33:12.179> games<00:33:12.419> that 00:33:12.830 --> 00:33:12.840 align:start position:0% player one and player two are games that 00:33:12.840 --> 00:33:14.930 align:start position:0% player one and player two are games that do<00:33:13.260> not<00:33:13.440> observe<00:33:13.980> anything<00:33:14.220> because<00:33:14.700> you 00:33:14.930 --> 00:33:14.940 align:start position:0% do not observe anything because you 00:33:14.940 --> 00:33:17.509 align:start position:0% do not observe anything because you don't<00:33:15.120> do<00:33:15.360> any<00:33:15.659> observation<00:33:16.260> in<00:33:17.039> the<00:33:17.159> prisoner 00:33:17.509 --> 00:33:17.519 align:start position:0% don't do any observation in the prisoner 00:33:17.519 --> 00:33:20.870 align:start position:0% don't do any observation in the prisoner dilemma<00:33:18.000> they<00:33:18.480> just<00:33:18.779> act<00:33:19.200> they<00:33:19.980> just<00:33:20.159> you<00:33:20.760> know 00:33:20.870 --> 00:33:20.880 align:start position:0% dilemma they just act they just you know 00:33:20.880 --> 00:33:23.570 align:start position:0% dilemma they just act they just you know Express<00:33:21.419> a<00:33:21.779> choice<00:33:22.080> and<00:33:22.980> they<00:33:23.159> receive<00:33:23.460> a 00:33:23.570 --> 00:33:23.580 align:start position:0% Express a choice and they receive a 00:33:23.580 --> 00:33:26.810 align:start position:0% Express a choice and they receive a feedback<00:33:23.960> for<00:33:24.960> that<00:33:25.140> choice<00:33:25.460> the<00:33:26.460> payoff 00:33:26.810 --> 00:33:26.820 align:start position:0% feedback for that choice the payoff 00:33:26.820 --> 00:33:29.930 align:start position:0% feedback for that choice the payoff Matrix<00:33:27.360> gain<00:33:27.960> is<00:33:28.559> a<00:33:28.740> game<00:33:28.919> that<00:33:29.220> doesn't<00:33:29.519> act 00:33:29.930 --> 00:33:29.940 align:start position:0% Matrix gain is a game that doesn't act 00:33:29.940 --> 00:33:32.630 align:start position:0% Matrix gain is a game that doesn't act it<00:33:30.299> doesn't<00:33:30.480> have<00:33:30.779> any<00:33:31.140> strategic<00:33:31.679> value<00:33:31.980> but 00:33:32.630 --> 00:33:32.640 align:start position:0% it doesn't have any strategic value but 00:33:32.640 --> 00:33:34.690 align:start position:0% it doesn't have any strategic value but it<00:33:32.820> just<00:33:33.059> observes 00:33:34.690 --> 00:33:34.700 align:start position:0% it just observes 00:33:34.700 --> 00:33:39.409 align:start position:0% it just observes the<00:33:35.700> players<00:33:36.419> move<00:33:37.220> and<00:33:38.220> returns<00:33:39.059> some 00:33:39.409 --> 00:33:39.419 align:start position:0% the players move and returns some 00:33:39.419 --> 00:33:41.870 align:start position:0% the players move and returns some feedback<00:33:39.840> and<00:33:40.500> again<00:33:40.620> you<00:33:40.980> see<00:33:41.100> that<00:33:41.340> in<00:33:41.640> this 00:33:41.870 --> 00:33:41.880 align:start position:0% feedback and again you see that in this 00:33:41.880 --> 00:33:43.190 align:start position:0% feedback and again you see that in this setting 00:33:43.190 --> 00:33:43.200 align:start position:0% setting 00:33:43.200 --> 00:33:46.130 align:start position:0% setting the<00:33:43.799> players<00:33:44.220> payoffs<00:33:44.940> are<00:33:45.419> the<00:33:45.779> payoff 00:33:46.130 --> 00:33:46.140 align:start position:0% the players payoffs are the payoff 00:33:46.140 --> 00:33:48.950 align:start position:0% the players payoffs are the payoff Matrix<00:33:46.559> feedback<00:33:47.159> and<00:33:47.640> the<00:33:47.820> player's<00:33:48.299> actions 00:33:48.950 --> 00:33:48.960 align:start position:0% Matrix feedback and the player's actions 00:33:48.960 --> 00:33:52.970 align:start position:0% Matrix feedback and the player's actions are<00:33:49.140> the<00:33:49.320> payoff<00:33:49.620> Matrix<00:33:50.039> observations 00:33:52.970 --> 00:33:52.980 align:start position:0% 00:33:52.980 --> 00:33:55.310 align:start position:0% so<00:33:53.580> yeah<00:33:53.820> the<00:33:54.240> cool<00:33:54.419> thing<00:33:54.600> about<00:33:54.840> that<00:33:55.140> is 00:33:55.310 --> 00:33:55.320 align:start position:0% so yeah the cool thing about that is 00:33:55.320 --> 00:33:58.130 align:start position:0% so yeah the cool thing about that is that<00:33:55.500> now<00:33:55.679> we<00:33:55.860> can<00:33:56.039> quickly<00:33:56.340> prototype<00:33:57.140> games 00:33:58.130 --> 00:33:58.140 align:start position:0% that now we can quickly prototype games 00:33:58.140 --> 00:34:00.289 align:start position:0% that now we can quickly prototype games by<00:33:58.740> basically<00:33:59.100> creating<00:33:59.460> these<00:33:59.760> blocks<00:34:00.120> and 00:34:00.289 --> 00:34:00.299 align:start position:0% by basically creating these blocks and 00:34:00.299 --> 00:34:03.409 align:start position:0% by basically creating these blocks and interconnecting<00:34:01.140> them<00:34:01.559> with<00:34:01.919> each<00:34:02.100> other<00:34:02.419> one 00:34:03.409 --> 00:34:03.419 align:start position:0% interconnecting them with each other one 00:34:03.419 --> 00:34:06.289 align:start position:0% interconnecting them with each other one thing<00:34:03.539> we<00:34:03.840> are<00:34:04.019> currently<00:34:04.380> working<00:34:04.620> on<00:34:05.000> uh<00:34:06.000> and 00:34:06.289 --> 00:34:06.299 align:start position:0% thing we are currently working on uh and 00:34:06.299 --> 00:34:09.409 align:start position:0% thing we are currently working on uh and Philip<00:34:06.960> will<00:34:07.080> show<00:34:07.320> a<00:34:08.040> demo<00:34:08.639> of<00:34:08.700> this 00:34:09.409 --> 00:34:09.419 align:start position:0% Philip will show a demo of this 00:34:09.419 --> 00:34:12.649 align:start position:0% Philip will show a demo of this is<00:34:10.080> for<00:34:10.379> instance<00:34:10.500> a<00:34:10.800> way<00:34:10.980> to<00:34:11.159> lift<00:34:11.520> evm<00:34:12.240> byte 00:34:12.649 --> 00:34:12.659 align:start position:0% is for instance a way to lift evm byte 00:34:12.659 --> 00:34:16.250 align:start position:0% is for instance a way to lift evm byte code<00:34:12.839> to<00:34:13.679> open<00:34:13.919> games<00:34:14.220> automatically<00:34:15.659> in 00:34:16.250 --> 00:34:16.260 align:start position:0% code to open games automatically in 00:34:16.260 --> 00:34:18.050 align:start position:0% code to open games automatically in doing<00:34:16.440> that<00:34:16.679> you<00:34:16.980> know<00:34:17.099> if<00:34:17.280> you<00:34:17.460> deploy<00:34:17.879> a 00:34:18.050 --> 00:34:18.060 align:start position:0% doing that you know if you deploy a 00:34:18.060 --> 00:34:20.149 align:start position:0% doing that you know if you deploy a smart<00:34:18.359> contract<00:34:18.899> we<00:34:19.440> can<00:34:19.560> take<00:34:19.740> your<00:34:19.980> smart 00:34:20.149 --> 00:34:20.159 align:start position:0% smart contract we can take your smart 00:34:20.159 --> 00:34:22.430 align:start position:0% smart contract we can take your smart contract<00:34:20.639> and<00:34:20.940> put<00:34:21.240> it<00:34:21.359> into<00:34:21.659> this<00:34:21.960> framework 00:34:22.430 --> 00:34:22.440 align:start position:0% contract and put it into this framework 00:34:22.440 --> 00:34:24.589 align:start position:0% contract and put it into this framework and<00:34:22.919> then<00:34:23.040> we<00:34:23.220> can<00:34:23.399> strategically<00:34:24.000> probe<00:34:24.480> it 00:34:24.589 --> 00:34:24.599 align:start position:0% and then we can strategically probe it 00:34:24.599 --> 00:34:26.869 align:start position:0% and then we can strategically probe it your<00:34:25.260> smart<00:34:25.500> contract<00:34:25.980> would<00:34:26.220> become<00:34:26.580> like 00:34:26.869 --> 00:34:26.879 align:start position:0% your smart contract would become like 00:34:26.879 --> 00:34:29.149 align:start position:0% your smart contract would become like the<00:34:27.060> payoff<00:34:27.419> Matrix<00:34:27.899> in<00:34:28.139> the<00:34:28.320> system<00:34:28.500> and<00:34:29.040> then 00:34:29.149 --> 00:34:29.159 align:start position:0% the payoff Matrix in the system and then 00:34:29.159 --> 00:34:30.649 align:start position:0% the payoff Matrix in the system and then we<00:34:29.339> can<00:34:29.460> economically<00:34:29.940> probe<00:34:30.359> it<00:34:30.480> with 00:34:30.649 --> 00:34:30.659 align:start position:0% we can economically probe it with 00:34:30.659 --> 00:34:32.510 align:start position:0% we can economically probe it with players<00:34:31.080> that<00:34:31.260> can<00:34:31.440> be<00:34:31.619> honest<00:34:31.919> or 00:34:32.510 --> 00:34:32.520 align:start position:0% players that can be honest or 00:34:32.520 --> 00:34:35.329 align:start position:0% players that can be honest or untrustworthy<00:34:33.480> and<00:34:34.020> see<00:34:34.260> you<00:34:34.740> know<00:34:34.859> which 00:34:35.329 --> 00:34:35.339 align:start position:0% untrustworthy and see you know which 00:34:35.339 --> 00:34:36.889 align:start position:0% untrustworthy and see you know which strategies<00:34:35.940> are<00:34:36.480> actually<00:34:36.599> winning 00:34:36.889 --> 00:34:36.899 align:start position:0% strategies are actually winning 00:34:36.899 --> 00:34:39.770 align:start position:0% strategies are actually winning strategies<00:34:37.560> or<00:34:37.740> not<00:34:37.919> and<00:34:38.280> so<00:34:38.520> if<00:34:39.419> your 00:34:39.770 --> 00:34:39.780 align:start position:0% strategies or not and so if your 00:34:39.780 --> 00:34:41.750 align:start position:0% strategies or not and so if your contract<00:34:40.200> is<00:34:40.740> economically<00:34:41.460> sound 00:34:41.750 --> 00:34:41.760 align:start position:0% contract is economically sound 00:34:41.760 --> 00:34:44.389 align:start position:0% contract is economically sound economically<00:34:42.659> stable<00:34:43.020> or<00:34:43.379> not<00:34:43.560> or<00:34:43.859> in<00:34:44.040> within 00:34:44.389 --> 00:34:44.399 align:start position:0% economically stable or not or in within 00:34:44.399 --> 00:34:47.750 align:start position:0% economically stable or not or in within which<00:34:44.700> bounds<00:34:45.300> it<00:34:45.839> operates<00:34:46.399> financially<00:34:47.399> in 00:34:47.750 --> 00:34:47.760 align:start position:0% which bounds it operates financially in 00:34:47.760 --> 00:34:49.970 align:start position:0% which bounds it operates financially in the<00:34:47.879> way<00:34:48.000> you<00:34:48.179> intended 00:34:49.970 --> 00:34:49.980 align:start position:0% the way you intended 00:34:49.980 --> 00:34:51.770 align:start position:0% the way you intended so<00:34:50.520> this<00:34:50.820> is<00:34:50.879> the<00:34:51.000> theory<00:34:51.300> part<00:34:51.480> that<00:34:51.659> is 00:34:51.770 --> 00:34:51.780 align:start position:0% so this is the theory part that is 00:34:51.780 --> 00:34:54.889 align:start position:0% so this is the theory part that is concluded<00:34:52.260> and<00:34:52.679> I<00:34:52.980> will<00:34:53.220> leave<00:34:54.179> for<00:34:54.720> the 00:34:54.889 --> 00:34:54.899 align:start position:0% concluded and I will leave for the 00:34:54.899 --> 00:34:57.410 align:start position:0% concluded and I will leave for the second<00:34:55.020> part<00:34:55.200> everything<00:34:55.500> to<00:34:55.800> Philip<00:34:56.159> uh<00:34:57.119> and 00:34:57.410 --> 00:34:57.420 align:start position:0% second part everything to Philip uh and 00:34:57.420 --> 00:34:59.570 align:start position:0% second part everything to Philip uh and basically<00:34:57.780> yeah<00:34:58.020> in<00:34:58.260> this<00:34:58.500> short<00:34:58.740> tutorial<00:34:59.220> we 00:34:59.570 --> 00:34:59.580 align:start position:0% basically yeah in this short tutorial we 00:34:59.580 --> 00:35:02.210 align:start position:0% basically yeah in this short tutorial we saw<00:34:59.820> how<00:35:00.480> we<00:35:00.660> can<00:35:00.780> use<00:35:00.960> this<00:35:01.320> compositionality 00:35:02.210 --> 00:35:02.220 align:start position:0% saw how we can use this compositionality 00:35:02.220 --> 00:35:04.849 align:start position:0% saw how we can use this compositionality techniques<00:35:02.820> to<00:35:03.420> guide<00:35:03.599> our<00:35:03.839> intuition<00:35:04.320> in 00:35:04.849 --> 00:35:04.859 align:start position:0% techniques to guide our intuition in 00:35:04.859 --> 00:35:07.130 align:start position:0% techniques to guide our intuition in designing<00:35:05.339> processes<00:35:06.000> we<00:35:06.660> started<00:35:06.960> with 00:35:07.130 --> 00:35:07.140 align:start position:0% designing processes we started with 00:35:07.140 --> 00:35:09.950 align:start position:0% designing processes we started with something<00:35:07.380> very<00:35:07.800> simple<00:35:08.060> then<00:35:09.060> we<00:35:09.300> start<00:35:09.480> we 00:35:09.950 --> 00:35:09.960 align:start position:0% something very simple then we start we 00:35:09.960 --> 00:35:12.470 align:start position:0% something very simple then we start we did<00:35:10.200> a<00:35:10.740> bit<00:35:11.040> more<00:35:11.220> involved<00:35:11.700> the 00:35:12.470 --> 00:35:12.480 align:start position:0% did a bit more involved the 00:35:12.480 --> 00:35:14.990 align:start position:0% did a bit more involved the um examples<00:35:13.140> and<00:35:13.560> then<00:35:13.680> we<00:35:13.980> found<00:35:14.220> out<00:35:14.460> that 00:35:14.990 --> 00:35:15.000 align:start position:0% um examples and then we found out that 00:35:15.000 --> 00:35:17.270 align:start position:0% um examples and then we found out that those<00:35:15.599> examples<00:35:16.079> were<00:35:16.380> actually<00:35:16.560> modeling 00:35:17.270 --> 00:35:17.280 align:start position:0% those examples were actually modeling 00:35:17.280 --> 00:35:19.490 align:start position:0% those examples were actually modeling and<00:35:17.760> more<00:35:18.060> General<00:35:18.240> pattern<00:35:18.900> this 00:35:19.490 --> 00:35:19.500 align:start position:0% and more General pattern this 00:35:19.500 --> 00:35:21.589 align:start position:0% and more General pattern this bi-directional<00:35:20.280> composition 00:35:21.589 --> 00:35:21.599 align:start position:0% bi-directional composition 00:35:21.599 --> 00:35:24.410 align:start position:0% bi-directional composition and<00:35:22.260> we<00:35:22.500> were<00:35:22.680> able<00:35:22.980> to<00:35:23.160> basically<00:35:23.880> recycle 00:35:24.410 --> 00:35:24.420 align:start position:0% and we were able to basically recycle 00:35:24.420 --> 00:35:26.750 align:start position:0% and we were able to basically recycle that<00:35:24.780> pattern<00:35:25.200> to<00:35:25.740> instantiate<00:35:26.280> other<00:35:26.520> things 00:35:26.750 --> 00:35:26.760 align:start position:0% that pattern to instantiate other things 00:35:26.760 --> 00:35:29.270 align:start position:0% that pattern to instantiate other things like<00:35:27.060> escrows<00:35:27.720> or<00:35:28.079> open<00:35:28.260> games 00:35:29.270 --> 00:35:29.280 align:start position:0% like escrows or open games 00:35:29.280 --> 00:35:31.849 align:start position:0% like escrows or open games and<00:35:30.000> yeah<00:35:30.180> that's<00:35:30.540> everything<00:35:30.780> for<00:35:31.200> me<00:35:31.380> and 00:35:31.849 --> 00:35:31.859 align:start position:0% and yeah that's everything for me and 00:35:31.859 --> 00:35:35.380 align:start position:0% and yeah that's everything for me and I'll<00:35:32.160> just<00:35:32.460> pass<00:35:33.180> it<00:35:33.420> to<00:35:33.599> Philip<00:35:34.260> thank<00:35:34.740> you 00:35:35.380 --> 00:35:35.390 align:start position:0% I'll just pass it to Philip thank you 00:35:35.390 --> 00:35:42.950 align:start position:0% I'll just pass it to Philip thank you [Applause] 00:35:42.950 --> 00:35:42.960 align:start position:0% 00:35:42.960 --> 00:35:45.530 align:start position:0% if<00:35:43.020> you<00:35:43.140> have<00:35:43.320> any<00:35:43.440> questions 00:35:45.530 --> 00:35:45.540 align:start position:0% if you have any questions 00:35:45.540 --> 00:35:48.109 align:start position:0% if you have any questions if<00:35:45.900> you<00:35:46.020> have<00:35:46.140> any<00:35:46.260> questions<00:35:46.560> we<00:35:47.280> can<00:35:47.460> in<00:35:47.820> the 00:35:48.109 --> 00:35:48.119 align:start position:0% if you have any questions we can in the 00:35:48.119 --> 00:35:50.630 align:start position:0% if you have any questions we can in the meantime<00:35:48.420> that<00:35:48.720> Philips<00:35:49.440> up<00:35:50.339> the<00:35:50.460> computer 00:35:50.630 --> 00:35:50.640 align:start position:0% meantime that Philips up the computer 00:35:50.640 --> 00:35:54.730 align:start position:0% meantime that Philips up the computer feel<00:35:51.119> free<00:35:51.300> to<00:35:51.420> ask<00:35:51.599> sure 00:35:54.730 --> 00:35:54.740 align:start position:0% 00:35:54.740 --> 00:35:58.430 align:start position:0% uh<00:35:55.740> the<00:35:55.980> final 00:35:58.430 --> 00:35:58.440 align:start position:0% 00:35:58.440 --> 00:36:01.430 align:start position:0% uh<00:35:59.099> yeah<00:35:59.339> uh 00:36:01.430 --> 00:36:01.440 align:start position:0% uh yeah uh 00:36:01.440 --> 00:36:04.490 align:start position:0% uh yeah uh I<00:36:02.220> I<00:36:02.220> mean<00:36:02.940> in<00:36:03.420> here<00:36:03.599> I<00:36:03.839> kind<00:36:04.020> of<00:36:04.140> cheated 00:36:04.490 --> 00:36:04.500 align:start position:0% I I mean in here I kind of cheated 00:36:04.500 --> 00:36:06.829 align:start position:0% I I mean in here I kind of cheated because<00:36:04.920> I<00:36:05.339> basically<00:36:05.940> just<00:36:06.240> defined<00:36:06.720> an 00:36:06.829 --> 00:36:06.839 align:start position:0% because I basically just defined an 00:36:06.839 --> 00:36:08.750 align:start position:0% because I basically just defined an optic<00:36:07.260> as 00:36:08.750 --> 00:36:08.760 align:start position:0% optic as 00:36:08.760 --> 00:36:11.390 align:start position:0% optic as you<00:36:09.300> know<00:36:09.420> this<00:36:10.020> box<00:36:10.260> obstructing<00:36:11.220> the 00:36:11.390 --> 00:36:11.400 align:start position:0% you know this box obstructing the 00:36:11.400 --> 00:36:14.990 align:start position:0% you know this box obstructing the details<00:36:11.880> indeed<00:36:12.720> mathematically<00:36:13.500> you<00:36:13.920> can<00:36:14.040> uh 00:36:14.990 --> 00:36:15.000 align:start position:0% details indeed mathematically you can uh 00:36:15.000 --> 00:36:17.089 align:start position:0% details indeed mathematically you can uh prove<00:36:15.660> the<00:36:15.780> I<00:36:15.900> mean<00:36:16.079> the<00:36:16.200> definition<00:36:16.320> of<00:36:16.680> optic 00:36:17.089 --> 00:36:17.099 align:start position:0% prove the I mean the definition of optic 00:36:17.099 --> 00:36:19.370 align:start position:0% prove the I mean the definition of optic is<00:36:17.339> exactly<00:36:17.700> something<00:36:17.940> that<00:36:18.240> embeds<00:36:18.839> that 00:36:19.370 --> 00:36:19.380 align:start position:0% is exactly something that embeds that 00:36:19.380 --> 00:36:20.930 align:start position:0% is exactly something that embeds that thing<00:36:19.619> mathematically<00:36:20.460> it's<00:36:20.640> a<00:36:20.820> bit 00:36:20.930 --> 00:36:20.940 align:start position:0% thing mathematically it's a bit 00:36:20.940 --> 00:36:24.349 align:start position:0% thing mathematically it's a bit complicated<00:36:21.359> to<00:36:21.720> describe<00:36:22.339> uh<00:36:23.359> but 00:36:24.349 --> 00:36:24.359 align:start position:0% complicated to describe uh but 00:36:24.359 --> 00:36:26.630 align:start position:0% complicated to describe uh but graphically<00:36:24.960> that's<00:36:25.320> exactly<00:36:25.740> what<00:36:25.980> it<00:36:26.160> is<00:36:26.280> an 00:36:26.630 --> 00:36:26.640 align:start position:0% graphically that's exactly what it is an 00:36:26.640 --> 00:36:28.990 align:start position:0% graphically that's exactly what it is an optic<00:36:27.000> is<00:36:27.240> something<00:36:27.480> that<00:36:27.839> has<00:36:28.020> this<00:36:28.500> sort<00:36:28.740> of 00:36:28.990 --> 00:36:29.000 align:start position:0% optic is something that has this sort of 00:36:29.000 --> 00:36:32.170 align:start position:0% optic is something that has this sort of nested<00:36:30.000> notion<00:36:30.420> of<00:36:30.599> composition<00:36:31.099> basically 00:36:32.170 --> 00:36:32.180 align:start position:0% nested notion of composition basically 00:36:32.180 --> 00:36:39.370 align:start position:0% nested notion of composition basically sure 00:36:39.370 --> 00:36:39.380 align:start position:0% 00:36:39.380 --> 00:36:41.930 align:start position:0% yeah<00:36:40.380> there<00:36:40.740> are<00:36:40.859> various<00:36:41.220> ways<00:36:41.520> to<00:36:41.640> do<00:36:41.760> that 00:36:41.930 --> 00:36:41.940 align:start position:0% yeah there are various ways to do that 00:36:41.940 --> 00:36:44.030 align:start position:0% yeah there are various ways to do that uh<00:36:42.480> Philip<00:36:42.839> is<00:36:42.960> the<00:36:43.140> expert<00:36:43.380> in<00:36:43.560> this<00:36:43.680> and<00:36:43.920> I 00:36:44.030 --> 00:36:44.040 align:start position:0% uh Philip is the expert in this and I 00:36:44.040 --> 00:36:46.630 align:start position:0% uh Philip is the expert in this and I don't<00:36:44.160> know<00:36:44.220> maybe<00:36:44.339> you<00:36:44.700> won't 00:36:46.630 --> 00:36:46.640 align:start position:0% don't know maybe you won't 00:36:46.640 --> 00:36:49.190 align:start position:0% don't know maybe you won't yeah<00:36:47.640> sorry<00:36:48.300> um<00:36:48.420> what's<00:36:48.839> your<00:36:49.020> question 00:36:49.190 --> 00:36:49.200 align:start position:0% yeah sorry um what's your question 00:36:49.200 --> 00:36:51.230 align:start position:0% yeah sorry um what's your question whether<00:36:49.380> you<00:36:49.560> can<00:36:49.680> also<00:36:49.800> do<00:36:49.920> repeated 00:36:51.230 --> 00:36:51.240 align:start position:0% whether you can also do repeated 00:36:51.240 --> 00:36:53.690 align:start position:0% whether you can also do repeated ly 00:36:53.690 --> 00:36:53.700 align:start position:0% 00:36:53.700 --> 00:36:54.829 align:start position:0% yeah 00:36:54.829 --> 00:36:54.839 align:start position:0% yeah 00:36:54.839 --> 00:36:56.390 align:start position:0% yeah yeah<00:36:55.079> you<00:36:55.440> can<00:36:55.500> do<00:36:55.619> that 00:36:56.390 --> 00:36:56.400 align:start position:0% yeah you can do that 00:36:56.400 --> 00:36:57.770 align:start position:0% yeah you can do that um<00:36:56.460> so<00:36:56.700> the<00:36:56.820> game<00:36:56.940> that<00:36:57.119> for<00:36:57.359> business<00:36:57.540> short 00:36:57.770 --> 00:36:57.780 align:start position:0% um so the game that for business short 00:36:57.780 --> 00:36:59.150 align:start position:0% um so the game that for business short is<00:36:57.960> a<00:36:58.079> one<00:36:58.200> shot<00:36:58.320> game<00:36:58.500> but<00:36:58.680> you<00:36:58.859> can<00:36:58.920> also 00:36:59.150 --> 00:36:59.160 align:start position:0% is a one shot game but you can also 00:36:59.160 --> 00:37:01.010 align:start position:0% is a one shot game but you can also think<00:36:59.280> about<00:36:59.460> this<00:36:59.700> as<00:36:59.940> taking<00:37:00.420> that<00:37:00.660> let's 00:37:01.010 --> 00:37:01.020 align:start position:0% think about this as taking that let's 00:37:01.020 --> 00:37:02.510 align:start position:0% think about this as taking that let's say<00:37:01.140> you<00:37:01.320> want<00:37:01.440> to<00:37:01.500> iterate<00:37:01.800> it<00:37:01.920> finally<00:37:02.220> many 00:37:02.510 --> 00:37:02.520 align:start position:0% say you want to iterate it finally many 00:37:02.520 --> 00:37:04.190 align:start position:0% say you want to iterate it finally many times<00:37:02.760> you<00:37:03.240> just<00:37:03.480> stack<00:37:03.660> it<00:37:03.780> on<00:37:03.960> each<00:37:04.079> other 00:37:04.190 --> 00:37:04.200 align:start position:0% times you just stack it on each other 00:37:04.200 --> 00:37:06.890 align:start position:0% times you just stack it on each other the<00:37:04.920> only<00:37:05.099> qualification<00:37:05.880> you<00:37:06.119> have<00:37:06.300> to<00:37:06.420> make 00:37:06.890 --> 00:37:06.900 align:start position:0% the only qualification you have to make 00:37:06.900 --> 00:37:08.210 align:start position:0% the only qualification you have to make um<00:37:06.960> if<00:37:07.140> you<00:37:07.200> looked<00:37:07.440> at<00:37:07.500> the<00:37:07.619> slide<00:37:07.800> they<00:37:08.040> were 00:37:08.210 --> 00:37:08.220 align:start position:0% um if you looked at the slide they were 00:37:08.220 --> 00:37:09.470 align:start position:0% um if you looked at the slide they were basically<00:37:08.520> the 00:37:09.470 --> 00:37:09.480 align:start position:0% basically the 00:37:09.480 --> 00:37:11.030 align:start position:0% basically the um<00:37:09.540> the<00:37:09.780> the<00:37:09.839> wires<00:37:10.260> were<00:37:10.440> not<00:37:10.619> coming<00:37:10.740> in<00:37:10.920> from 00:37:11.030 --> 00:37:11.040 align:start position:0% um the the wires were not coming in from 00:37:11.040 --> 00:37:12.530 align:start position:0% um the the wires were not coming in from the<00:37:11.160> outside<00:37:11.280> you<00:37:11.700> have<00:37:11.820> the<00:37:11.940> game<00:37:12.060> with<00:37:12.240> wires 00:37:12.530 --> 00:37:12.540 align:start position:0% the outside you have the game with wires 00:37:12.540 --> 00:37:13.790 align:start position:0% the outside you have the game with wires and<00:37:12.720> then<00:37:12.839> you<00:37:12.900> can<00:37:13.020> stack<00:37:13.200> it<00:37:13.380> basically 00:37:13.790 --> 00:37:13.800 align:start position:0% and then you can stack it basically 00:37:13.800 --> 00:37:15.770 align:start position:0% and then you can stack it basically alternative<00:37:14.700> way<00:37:14.880> to<00:37:15.060> do<00:37:15.180> is<00:37:15.300> also<00:37:15.540> you<00:37:15.660> can 00:37:15.770 --> 00:37:15.780 align:start position:0% alternative way to do is also you can 00:37:15.780 --> 00:37:17.329 align:start position:0% alternative way to do is also you can turn<00:37:15.900> it<00:37:15.960> into<00:37:16.079> a<00:37:16.260> Markov<00:37:16.500> game<00:37:16.740> which<00:37:17.040> has<00:37:17.160> a 00:37:17.329 --> 00:37:17.339 align:start position:0% turn it into a Markov game which has a 00:37:17.339 --> 00:37:18.770 align:start position:0% turn it into a Markov game which has a state<00:37:17.460> and<00:37:18.000> then<00:37:18.060> you<00:37:18.240> can<00:37:18.359> basically<00:37:18.599> think 00:37:18.770 --> 00:37:18.780 align:start position:0% state and then you can basically think 00:37:18.780 --> 00:37:20.450 align:start position:0% state and then you can basically think about<00:37:18.960> it<00:37:19.140> as<00:37:19.260> approximating<00:37:19.800> it<00:37:19.980> to<00:37:20.220> be<00:37:20.339> run 00:37:20.450 --> 00:37:20.460 align:start position:0% about it as approximating it to be run 00:37:20.460 --> 00:37:21.970 align:start position:0% about it as approximating it to be run infinitely 00:37:21.970 --> 00:37:21.980 align:start position:0% infinitely 00:37:21.980 --> 00:37:24.470 align:start position:0% infinitely okay<00:37:22.980> other<00:37:23.220> questions<00:37:23.520> to<00:37:23.820> the<00:37:24.000> first<00:37:24.180> part 00:37:24.470 --> 00:37:24.480 align:start position:0% okay other questions to the first part 00:37:24.480 --> 00:37:35.510 align:start position:0% okay other questions to the first part there<00:37:24.780> is<00:37:24.960> a<00:37:25.020> question<00:37:25.140> in<00:37:25.260> the<00:37:25.380> first<00:37:25.500> part 00:37:35.510 --> 00:37:35.520 align:start position:0% 00:37:35.520 --> 00:37:37.310 align:start position:0% um<00:37:35.640> let<00:37:36.420> me<00:37:36.540> do<00:37:36.660> the<00:37:36.720> following<00:37:36.960> I'm<00:37:37.140> trying 00:37:37.310 --> 00:37:37.320 align:start position:0% um let me do the following I'm trying 00:37:37.320 --> 00:37:39.589 align:start position:0% um let me do the following I'm trying I'm<00:37:37.560> jumping<00:37:37.920> on<00:37:38.040> my<00:37:38.099> slides<00:37:38.400> ahead 00:37:39.589 --> 00:37:39.599 align:start position:0% I'm jumping on my slides ahead 00:37:39.599 --> 00:37:40.609 align:start position:0% I'm jumping on my slides ahead um 00:37:40.609 --> 00:37:40.619 align:start position:0% um 00:37:40.619 --> 00:37:42.710 align:start position:0% um to<00:37:40.980> show<00:37:41.160> you<00:37:41.280> this 00:37:42.710 --> 00:37:42.720 align:start position:0% to show you this 00:37:42.720 --> 00:37:45.790 align:start position:0% to show you this then<00:37:42.960> I<00:37:43.140> will<00:37:43.260> go<00:37:43.440> back 00:37:45.790 --> 00:37:45.800 align:start position:0% 00:37:45.800 --> 00:37:49.250 align:start position:0% ah<00:37:46.800> sorry<00:37:47.040> could<00:37:47.339> you<00:37:47.520> guys<00:37:48.420> sorry<00:37:48.839> can<00:37:49.079> you 00:37:49.250 --> 00:37:49.260 align:start position:0% ah sorry could you guys sorry can you 00:37:49.260 --> 00:37:51.829 align:start position:0% ah sorry could you guys sorry can you switch<00:37:49.440> on<00:37:49.619> the<00:37:49.859> okay 00:37:51.829 --> 00:37:51.839 align:start position:0% switch on the okay 00:37:51.839 --> 00:37:54.050 align:start position:0% switch on the okay um<00:37:51.960> let<00:37:52.140> me<00:37:52.260> go<00:37:52.380> to<00:37:52.500> the 00:37:54.050 --> 00:37:54.060 align:start position:0% um let me go to the 00:37:54.060 --> 00:37:55.849 align:start position:0% um let me go to the so<00:37:54.780> here 00:37:55.849 --> 00:37:55.859 align:start position:0% so here 00:37:55.859 --> 00:37:56.930 align:start position:0% so here um you<00:37:56.040> have<00:37:56.220> to<00:37:56.280> think<00:37:56.400> about<00:37:56.520> it<00:37:56.640> as<00:37:56.760> two 00:37:56.930 --> 00:37:56.940 align:start position:0% um you have to think about it as two 00:37:56.940 --> 00:37:58.609 align:start position:0% um you have to think about it as two Dimensions<00:37:57.359> right<00:37:57.540> so<00:37:57.780> time<00:37:58.020> flows<00:37:58.320> from<00:37:58.500> left 00:37:58.609 --> 00:37:58.619 align:start position:0% Dimensions right so time flows from left 00:37:58.619 --> 00:38:01.010 align:start position:0% Dimensions right so time flows from left to<00:37:58.859> right<00:37:59.099> and<00:38:00.060> if<00:38:00.420> you<00:38:00.480> start<00:38:00.660> from<00:38:00.839> the<00:38:00.960> left 00:38:01.010 --> 00:38:01.020 align:start position:0% to right and if you start from the left 00:38:01.020 --> 00:38:03.349 align:start position:0% to right and if you start from the left there<00:38:01.260> are<00:38:01.380> two<00:38:01.500> things<00:38:01.680> P1<00:38:02.400> and<00:38:02.579> P2<00:38:02.880> they<00:38:03.240> are 00:38:03.349 --> 00:38:03.359 align:start position:0% there are two things P1 and P2 they are 00:38:03.359 --> 00:38:05.150 align:start position:0% there are two things P1 and P2 they are not<00:38:03.480> connected<00:38:03.839> which<00:38:04.140> means<00:38:04.440> they<00:38:04.740> happen<00:38:04.920> in 00:38:05.150 --> 00:38:05.160 align:start position:0% not connected which means they happen in 00:38:05.160 --> 00:38:06.530 align:start position:0% not connected which means they happen in parallel<00:38:05.520> so<00:38:05.700> this<00:38:05.820> is<00:38:06.000> simultaneously 00:38:06.530 --> 00:38:06.540 align:start position:0% parallel so this is simultaneously 00:38:06.540 --> 00:38:08.390 align:start position:0% parallel so this is simultaneously happening<00:38:06.900> then<00:38:07.380> afterwards<00:38:07.859> they<00:38:08.099> output 00:38:08.390 --> 00:38:08.400 align:start position:0% happening then afterwards they output 00:38:08.400 --> 00:38:11.089 align:start position:0% happening then afterwards they output the<00:38:08.520> move<00:38:08.700> which<00:38:08.880> is<00:38:08.940> y1<00:38:09.359> and<00:38:09.480> Y2<00:38:09.839> that<00:38:10.500> move<00:38:10.680> is 00:38:11.089 --> 00:38:11.099 align:start position:0% the move which is y1 and Y2 that move is 00:38:11.099 --> 00:38:12.890 align:start position:0% the move which is y1 and Y2 that move is consumed<00:38:11.700> by<00:38:11.880> U<00:38:12.060> which<00:38:12.359> is<00:38:12.480> the<00:38:12.599> payoff 00:38:12.890 --> 00:38:12.900 align:start position:0% consumed by U which is the payoff 00:38:12.900 --> 00:38:14.750 align:start position:0% consumed by U which is the payoff function<00:38:13.200> and<00:38:13.680> in<00:38:13.800> that<00:38:13.980> sense<00:38:14.160> you<00:38:14.460> follow 00:38:14.750 --> 00:38:14.760 align:start position:0% function and in that sense you follow 00:38:14.760 --> 00:38:16.910 align:start position:0% function and in that sense you follow sequentially<00:38:15.300> after<00:38:15.540> these<00:38:15.960> two<00:38:16.079> games<00:38:16.260> right 00:38:16.910 --> 00:38:16.920 align:start position:0% sequentially after these two games right 00:38:16.920 --> 00:38:18.710 align:start position:0% sequentially after these two games right you<00:38:17.700> can<00:38:17.760> also<00:38:18.000> think<00:38:18.060> about<00:38:18.240> these<00:38:18.480> two<00:38:18.599> games 00:38:18.710 --> 00:38:18.720 align:start position:0% you can also think about these two games 00:38:18.720 --> 00:38:21.230 align:start position:0% you can also think about these two games P1<00:38:19.140> and<00:38:19.260> B2<00:38:19.560> being<00:38:19.800> merged<00:38:20.160> into<00:38:20.339> one<00:38:20.640> and<00:38:21.060> then 00:38:21.230 --> 00:38:21.240 align:start position:0% P1 and B2 being merged into one and then 00:38:21.240 --> 00:38:23.329 align:start position:0% P1 and B2 being merged into one and then it's<00:38:21.359> just<00:38:21.599> big<00:38:21.839> two<00:38:22.200> games<00:38:22.560> being<00:38:22.859> stacked<00:38:23.220> on 00:38:23.329 --> 00:38:23.339 align:start position:0% it's just big two games being stacked on 00:38:23.339 --> 00:38:24.470 align:start position:0% it's just big two games being stacked on top 00:38:24.470 --> 00:38:24.480 align:start position:0% top 00:38:24.480 --> 00:38:27.530 align:start position:0% top okay<00:38:25.079> so<00:38:25.560> let<00:38:26.040> me<00:38:26.160> go<00:38:26.339> back<00:38:26.460> to<00:38:26.579> the<00:38:26.700> start 00:38:27.530 --> 00:38:27.540 align:start position:0% okay so let me go back to the start 00:38:27.540 --> 00:38:31.849 align:start position:0% okay so let me go back to the start you<00:38:27.960> can<00:38:28.140> already<00:38:28.200> see<00:38:28.440> what<00:38:28.560> is<00:38:28.740> coming 00:38:31.849 --> 00:38:31.859 align:start position:0% 00:38:31.859 --> 00:38:33.290 align:start position:0% okay 00:38:33.290 --> 00:38:33.300 align:start position:0% okay 00:38:33.300 --> 00:38:35.810 align:start position:0% okay um<00:38:33.359> so<00:38:33.720> what<00:38:33.839> we<00:38:33.960> want<00:38:34.079> to<00:38:34.200> do<00:38:34.260> in<00:38:34.560> this<00:38:35.220> in<00:38:35.640> this 00:38:35.810 --> 00:38:35.820 align:start position:0% um so what we want to do in this in this 00:38:35.820 --> 00:38:38.329 align:start position:0% um so what we want to do in this in this part<00:38:36.000> in<00:38:36.240> the<00:38:36.420> second<00:38:36.540> part<00:38:36.920> by<00:38:37.920> the<00:38:38.040> way<00:38:38.099> hi 00:38:38.329 --> 00:38:38.339 align:start position:0% part in the second part by the way hi 00:38:38.339 --> 00:38:40.130 align:start position:0% part in the second part by the way hi I'm<00:38:38.579> Philip<00:38:38.940> thanks<00:38:39.480> thank<00:38:39.720> you<00:38:39.900> all<00:38:40.020> for 00:38:40.130 --> 00:38:40.140 align:start position:0% I'm Philip thanks thank you all for 00:38:40.140 --> 00:38:40.910 align:start position:0% I'm Philip thanks thank you all for coming 00:38:40.910 --> 00:38:40.920 align:start position:0% coming 00:38:40.920 --> 00:38:42.230 align:start position:0% coming um<00:38:40.980> what<00:38:41.339> we<00:38:41.460> want<00:38:41.579> to<00:38:41.700> do<00:38:41.760> in<00:38:41.820> the<00:38:41.940> second<00:38:42.060> part 00:38:42.230 --> 00:38:42.240 align:start position:0% um what we want to do in the second part 00:38:42.240 --> 00:38:44.329 align:start position:0% um what we want to do in the second part is<00:38:42.480> basically<00:38:42.720> take<00:38:42.960> a<00:38:43.140> deeper<00:38:43.380> look<00:38:43.500> look<00:38:43.920> at 00:38:44.329 --> 00:38:44.339 align:start position:0% is basically take a deeper look look at 00:38:44.339 --> 00:38:46.130 align:start position:0% is basically take a deeper look look at compositional<00:38:45.180> Game<00:38:45.359> Theory<00:38:45.720> as<00:38:45.900> one 00:38:46.130 --> 00:38:46.140 align:start position:0% compositional Game Theory as one 00:38:46.140 --> 00:38:48.230 align:start position:0% compositional Game Theory as one specific<00:38:46.560> instance<00:38:47.099> of 00:38:48.230 --> 00:38:48.240 align:start position:0% specific instance of 00:38:48.240 --> 00:38:48.950 align:start position:0% specific instance of um<00:38:48.300> how<00:38:48.480> you<00:38:48.599> can<00:38:48.720> think<00:38:48.780> about 00:38:48.950 --> 00:38:48.960 align:start position:0% um how you can think about 00:38:48.960 --> 00:38:50.030 align:start position:0% um how you can think about compositionality<00:38:49.740> and<00:38:49.920> what 00:38:50.030 --> 00:38:50.040 align:start position:0% compositionality and what 00:38:50.040 --> 00:38:51.650 align:start position:0% compositionality and what compositionality<00:38:50.760> possibly<00:38:51.240> can<00:38:51.420> give<00:38:51.540> you 00:38:51.650 --> 00:38:51.660 align:start position:0% compositionality possibly can give you 00:38:51.660 --> 00:38:53.630 align:start position:0% compositionality possibly can give you as<00:38:51.900> value<00:38:52.380> to 00:38:53.630 --> 00:38:53.640 align:start position:0% as value to 00:38:53.640 --> 00:38:55.430 align:start position:0% as value to um as<00:38:53.940> an<00:38:54.060> approach<00:38:54.359> to<00:38:54.660> thinking<00:38:55.020> about<00:38:55.140> in 00:38:55.430 --> 00:38:55.440 align:start position:0% um as an approach to thinking about in 00:38:55.440 --> 00:38:57.170 align:start position:0% um as an approach to thinking about in that<00:38:55.619> specific<00:38:56.040> context<00:38:56.460> of<00:38:56.760> strategic 00:38:57.170 --> 00:38:57.180 align:start position:0% that specific context of strategic 00:38:57.180 --> 00:38:58.670 align:start position:0% that specific context of strategic interactions 00:38:58.670 --> 00:38:58.680 align:start position:0% interactions 00:38:58.680 --> 00:39:00.530 align:start position:0% interactions okay<00:38:59.160> compositional<00:38:59.820> Game<00:39:00.000> Theory<00:39:00.240> what<00:39:00.420> is 00:39:00.530 --> 00:39:00.540 align:start position:0% okay compositional Game Theory what is 00:39:00.540 --> 00:39:02.690 align:start position:0% okay compositional Game Theory what is that<00:39:00.720> actually<00:39:00.900> so<00:39:01.440> it's<00:39:01.800> a<00:39:01.980> at<00:39:02.460> the<00:39:02.579> beginning 00:39:02.690 --> 00:39:02.700 align:start position:0% that actually so it's a at the beginning 00:39:02.700 --> 00:39:03.890 align:start position:0% that actually so it's a at the beginning actually<00:39:03.000> this<00:39:03.180> was<00:39:03.359> a<00:39:03.480> research<00:39:03.720> project 00:39:03.890 --> 00:39:03.900 align:start position:0% actually this was a research project 00:39:03.900 --> 00:39:06.170 align:start position:0% actually this was a research project which<00:39:04.260> was<00:39:04.440> focused<00:39:04.859> on<00:39:05.220> providing<00:39:05.880> a<00:39:06.060> new 00:39:06.170 --> 00:39:06.180 align:start position:0% which was focused on providing a new 00:39:06.180 --> 00:39:08.510 align:start position:0% which was focused on providing a new formal<00:39:06.540> language<00:39:06.740> for<00:39:07.740> game<00:39:07.980> theoretic 00:39:08.510 --> 00:39:08.520 align:start position:0% formal language for game theoretic 00:39:08.520 --> 00:39:09.890 align:start position:0% formal language for game theoretic reasoning<00:39:08.880> yeah<00:39:09.119> you<00:39:09.480> probably<00:39:09.599> have<00:39:09.780> heard 00:39:09.890 --> 00:39:09.900 align:start position:0% reasoning yeah you probably have heard 00:39:09.900 --> 00:39:11.630 align:start position:0% reasoning yeah you probably have heard about<00:39:10.079> Game<00:39:10.260> Theory<00:39:10.560> many<00:39:11.220> of<00:39:11.339> you<00:39:11.400> probably 00:39:11.630 --> 00:39:11.640 align:start position:0% about Game Theory many of you probably 00:39:11.640 --> 00:39:13.430 align:start position:0% about Game Theory many of you probably have<00:39:11.820> already<00:39:12.000> seen<00:39:12.359> it<00:39:12.480> it's<00:39:12.780> a<00:39:12.900> mathematical 00:39:13.430 --> 00:39:13.440 align:start position:0% have already seen it it's a mathematical 00:39:13.440 --> 00:39:15.290 align:start position:0% have already seen it it's a mathematical language<00:39:14.040> to<00:39:14.460> express<00:39:14.579> the<00:39:14.880> reasoning<00:39:15.180> about 00:39:15.290 --> 00:39:15.300 align:start position:0% language to express the reasoning about 00:39:15.300 --> 00:39:16.849 align:start position:0% language to express the reasoning about agents<00:39:15.780> and<00:39:16.020> what<00:39:16.140> we<00:39:16.260> provide<00:39:16.500> is<00:39:16.680> just 00:39:16.849 --> 00:39:16.859 align:start position:0% agents and what we provide is just 00:39:16.859 --> 00:39:18.770 align:start position:0% agents and what we provide is just another<00:39:17.099> language<00:39:17.400> in<00:39:17.700> some<00:39:17.880> sense 00:39:18.770 --> 00:39:18.780 align:start position:0% another language in some sense 00:39:18.780 --> 00:39:20.990 align:start position:0% another language in some sense now<00:39:19.260> this<00:39:19.560> language<00:39:19.800> is<00:39:20.220> as<00:39:20.579> for<00:39:20.820> pizza 00:39:20.990 --> 00:39:21.000 align:start position:0% now this language is as for pizza 00:39:21.000 --> 00:39:22.970 align:start position:0% now this language is as for pizza already<00:39:21.420> introduced<00:39:22.140> based<00:39:22.800> on<00:39:22.859> the 00:39:22.970 --> 00:39:22.980 align:start position:0% already introduced based on the 00:39:22.980 --> 00:39:25.550 align:start position:0% already introduced based on the categorical<00:39:23.339> framework<00:39:23.960> and<00:39:24.960> this<00:39:25.380> has 00:39:25.550 --> 00:39:25.560 align:start position:0% categorical framework and this has 00:39:25.560 --> 00:39:28.010 align:start position:0% categorical framework and this has several<00:39:25.859> consequences<00:39:26.339> one<00:39:26.760> is<00:39:26.940> you<00:39:27.480> give<00:39:27.720> you 00:39:28.010 --> 00:39:28.020 align:start position:0% several consequences one is you give you 00:39:28.020 --> 00:39:29.630 align:start position:0% several consequences one is you give you first<00:39:28.320> of<00:39:28.440> all<00:39:28.560> you<00:39:28.800> get<00:39:28.920> a<00:39:29.040> graphical<00:39:29.280> way<00:39:29.520> of 00:39:29.630 --> 00:39:29.640 align:start position:0% first of all you get a graphical way of 00:39:29.640 --> 00:39:31.730 align:start position:0% first of all you get a graphical way of reasoning<00:39:30.060> but<00:39:30.480> most<00:39:30.720> importantly<00:39:31.140> you<00:39:31.320> get<00:39:31.619> a 00:39:31.730 --> 00:39:31.740 align:start position:0% reasoning but most importantly you get a 00:39:31.740 --> 00:39:33.829 align:start position:0% reasoning but most importantly you get a way<00:39:31.859> of<00:39:32.040> compositionally<00:39:32.720> approaching<00:39:33.720> the 00:39:33.829 --> 00:39:33.839 align:start position:0% way of compositionally approaching the 00:39:33.839 --> 00:39:35.390 align:start position:0% way of compositionally approaching the modeling<00:39:34.200> problems 00:39:35.390 --> 00:39:35.400 align:start position:0% modeling problems 00:39:35.400 --> 00:39:38.930 align:start position:0% modeling problems um<00:39:35.520> that<00:39:35.940> you<00:39:36.060> that<00:39:36.300> you<00:39:36.480> face<00:39:36.660> okay<00:39:37.320> now<00:39:38.160> if 00:39:38.930 --> 00:39:38.940 align:start position:0% um that you that you face okay now if 00:39:38.940 --> 00:39:40.609 align:start position:0% um that you that you face okay now if you<00:39:39.060> just<00:39:39.180> do<00:39:39.359> the<00:39:39.540> diagrams<00:39:40.020> and<00:39:40.260> you<00:39:40.440> you 00:39:40.609 --> 00:39:40.619 align:start position:0% you just do the diagrams and you you 00:39:40.619 --> 00:39:42.170 align:start position:0% you just do the diagrams and you you know<00:39:40.740> suppose<00:39:40.980> you<00:39:41.160> would<00:39:41.280> be<00:39:41.400> forced<00:39:41.700> of<00:39:41.880> you 00:39:42.170 --> 00:39:42.180 align:start position:0% know suppose you would be forced of you 00:39:42.180 --> 00:39:43.730 align:start position:0% know suppose you would be forced of you know<00:39:42.240> using<00:39:42.540> diagrams<00:39:43.020> for<00:39:43.320> very<00:39:43.500> large 00:39:43.730 --> 00:39:43.740 align:start position:0% know using diagrams for very large 00:39:43.740 --> 00:39:45.650 align:start position:0% know using diagrams for very large systems<00:39:44.220> like<00:39:44.520> a<00:39:44.640> staking<00:39:44.880> protocol<00:39:45.240> or<00:39:45.480> other 00:39:45.650 --> 00:39:45.660 align:start position:0% systems like a staking protocol or other 00:39:45.660 --> 00:39:47.990 align:start position:0% systems like a staking protocol or other complicated<00:39:46.020> more<00:39:46.260> complicated<00:39:47.000> systems 00:39:47.990 --> 00:39:48.000 align:start position:0% complicated more complicated systems 00:39:48.000 --> 00:39:49.910 align:start position:0% complicated more complicated systems that<00:39:48.180> would<00:39:48.359> be<00:39:48.540> limiting<00:39:49.200> it<00:39:49.560> would<00:39:49.680> not<00:39:49.800> be 00:39:49.910 --> 00:39:49.920 align:start position:0% that would be limiting it would not be 00:39:49.920 --> 00:39:51.589 align:start position:0% that would be limiting it would not be that<00:39:50.099> much<00:39:50.280> help<00:39:50.460> it<00:39:50.880> might<00:39:51.119> be<00:39:51.180> a<00:39:51.300> cool<00:39:51.420> new 00:39:51.589 --> 00:39:51.599 align:start position:0% that much help it might be a cool new 00:39:51.599 --> 00:39:52.790 align:start position:0% that much help it might be a cool new Theory<00:39:51.900> it<00:39:52.079> might<00:39:52.200> be<00:39:52.320> of<00:39:52.440> interest<00:39:52.560> because 00:39:52.790 --> 00:39:52.800 align:start position:0% Theory it might be of interest because 00:39:52.800 --> 00:39:55.550 align:start position:0% Theory it might be of interest because some<00:39:53.040> academics<00:39:53.460> but<00:39:54.180> practically<00:39:54.599> maybe<00:39:55.320> not 00:39:55.550 --> 00:39:55.560 align:start position:0% some academics but practically maybe not 00:39:55.560 --> 00:39:56.990 align:start position:0% some academics but practically maybe not so<00:39:55.680> much<00:39:55.859> relevant 00:39:56.990 --> 00:39:57.000 align:start position:0% so much relevant 00:39:57.000 --> 00:39:59.030 align:start position:0% so much relevant what<00:39:57.480> is<00:39:57.660> up<00:39:57.780> what<00:39:58.020> however<00:39:58.380> is<00:39:58.560> a<00:39:58.680> consequence 00:39:59.030 --> 00:39:59.040 align:start position:0% what is up what however is a consequence 00:39:59.040 --> 00:40:01.010 align:start position:0% what is up what however is a consequence of<00:39:59.220> what<00:39:59.400> also<00:39:59.700> for<00:39:59.820> pizza<00:39:59.940> already<00:40:00.300> said<00:40:00.540> dami 00:40:01.010 --> 00:40:01.020 align:start position:0% of what also for pizza already said dami 00:40:01.020 --> 00:40:02.210 align:start position:0% of what also for pizza already said dami there<00:40:01.079> is<00:40:01.260> a<00:40:01.380> very<00:40:01.500> close<00:40:01.680> connection<00:40:01.920> to 00:40:02.210 --> 00:40:02.220 align:start position:0% there is a very close connection to 00:40:02.220 --> 00:40:04.550 align:start position:0% there is a very close connection to Optics<00:40:02.579> and<00:40:03.240> Optics<00:40:03.660> allow<00:40:04.079> more<00:40:04.380> or<00:40:04.500> less 00:40:04.550 --> 00:40:04.560 align:start position:0% Optics and Optics allow more or less 00:40:04.560 --> 00:40:06.170 align:start position:0% Optics and Optics allow more or less these<00:40:04.980> things<00:40:05.040> to<00:40:05.220> be<00:40:05.339> directly<00:40:05.700> implemented 00:40:06.170 --> 00:40:06.180 align:start position:0% these things to be directly implemented 00:40:06.180 --> 00:40:08.930 align:start position:0% these things to be directly implemented enabled<00:40:07.140> us<00:40:07.200> to<00:40:07.500> also<00:40:07.740> develop<00:40:08.040> on<00:40:08.400> the<00:40:08.520> site<00:40:08.700> a 00:40:08.930 --> 00:40:08.940 align:start position:0% enabled us to also develop on the site a 00:40:08.940 --> 00:40:11.150 align:start position:0% enabled us to also develop on the site a software<00:40:09.240> tool<00:40:09.599> which<00:40:10.260> basically<00:40:10.619> takes<00:40:10.920> the 00:40:11.150 --> 00:40:11.160 align:start position:0% software tool which basically takes the 00:40:11.160 --> 00:40:13.130 align:start position:0% software tool which basically takes the language<00:40:11.339> of<00:40:11.760> category<00:40:12.119> theory<00:40:12.540> for<00:40:12.780> modeling 00:40:13.130 --> 00:40:13.140 align:start position:0% language of category theory for modeling 00:40:13.140 --> 00:40:13.970 align:start position:0% language of category theory for modeling games 00:40:13.970 --> 00:40:13.980 align:start position:0% games 00:40:13.980 --> 00:40:16.069 align:start position:0% games and<00:40:14.460> turns<00:40:14.760> it<00:40:14.880> into<00:40:15.060> a<00:40:15.359> software<00:40:15.720> framework 00:40:16.069 --> 00:40:16.079 align:start position:0% and turns it into a software framework 00:40:16.079 --> 00:40:17.450 align:start position:0% and turns it into a software framework that<00:40:16.260> you<00:40:16.380> can<00:40:16.500> use<00:40:16.619> that<00:40:16.920> supports<00:40:17.339> your 00:40:17.450 --> 00:40:17.460 align:start position:0% that you can use that supports your 00:40:17.460 --> 00:40:19.190 align:start position:0% that you can use that supports your modeling<00:40:17.820> process<00:40:18.060> and<00:40:18.720> that's<00:40:18.839> the<00:40:19.079> key 00:40:19.190 --> 00:40:19.200 align:start position:0% modeling process and that's the key 00:40:19.200 --> 00:40:20.390 align:start position:0% modeling process and that's the key thing<00:40:19.320> because<00:40:19.500> if<00:40:19.680> you<00:40:19.800> would<00:40:19.920> be<00:40:20.040> forced<00:40:20.339> to 00:40:20.390 --> 00:40:20.400 align:start position:0% thing because if you would be forced to 00:40:20.400 --> 00:40:22.490 align:start position:0% thing because if you would be forced to doing<00:40:20.579> things<00:40:20.700> on<00:40:20.880> pen<00:40:21.000> and<00:40:21.180> paper<00:40:21.359> well<00:40:22.140> yeah 00:40:22.490 --> 00:40:22.500 align:start position:0% doing things on pen and paper well yeah 00:40:22.500 --> 00:40:24.710 align:start position:0% doing things on pen and paper well yeah would<00:40:22.920> not<00:40:23.099> be<00:40:23.339> that<00:40:23.460> practical<00:40:23.820> once<00:40:24.599> you 00:40:24.710 --> 00:40:24.720 align:start position:0% would not be that practical once you 00:40:24.720 --> 00:40:26.750 align:start position:0% would not be that practical once you have<00:40:24.900> this<00:40:25.260> Tooling<00:40:25.619> in<00:40:25.740> the<00:40:25.859> back<00:40:25.980> then<00:40:26.579> you 00:40:26.750 --> 00:40:26.760 align:start position:0% have this Tooling in the back then you 00:40:26.760 --> 00:40:28.490 align:start position:0% have this Tooling in the back then you can<00:40:26.880> actually<00:40:27.000> leverage 00:40:28.490 --> 00:40:28.500 align:start position:0% can actually leverage 00:40:28.500 --> 00:40:30.770 align:start position:0% can actually leverage um the<00:40:29.099> basically<00:40:30.000> the<00:40:30.180> benefits<00:40:30.599> of 00:40:30.770 --> 00:40:30.780 align:start position:0% um the basically the benefits of 00:40:30.780 --> 00:40:32.870 align:start position:0% um the basically the benefits of compositionality<00:40:31.619> and<00:40:32.099> the<00:40:32.280> purpose<00:40:32.520> of<00:40:32.700> that 00:40:32.870 --> 00:40:32.880 align:start position:0% compositionality and the purpose of that 00:40:32.880 --> 00:40:35.990 align:start position:0% compositionality and the purpose of that basically<00:40:33.660> second<00:40:33.960> part<00:40:34.260> is<00:40:35.220> hopefully<00:40:35.880> to 00:40:35.990 --> 00:40:36.000 align:start position:0% basically second part is hopefully to 00:40:36.000 --> 00:40:37.609 align:start position:0% basically second part is hopefully to convince<00:40:36.300> you<00:40:36.420> that<00:40:36.660> at<00:40:37.020> least<00:40:37.140> this<00:40:37.320> might<00:40:37.500> be 00:40:37.609 --> 00:40:37.619 align:start position:0% convince you that at least this might be 00:40:37.619 --> 00:40:39.349 align:start position:0% convince you that at least this might be interesting<00:40:37.920> and<00:40:38.160> hopefully<00:40:38.400> more<00:40:38.760> that<00:40:39.180> this 00:40:39.349 --> 00:40:39.359 align:start position:0% interesting and hopefully more that this 00:40:39.359 --> 00:40:42.230 align:start position:0% interesting and hopefully more that this might<00:40:39.540> be<00:40:39.660> really<00:40:39.780> useful 00:40:42.230 --> 00:40:42.240 align:start position:0% 00:40:42.240 --> 00:40:45.470 align:start position:0% okay<00:40:42.839> so<00:40:43.500> a<00:40:44.099> large<00:40:44.220> chunk<00:40:44.460> of<00:40:44.640> the<00:40:44.820> talk<00:40:45.180> will 00:40:45.470 --> 00:40:45.480 align:start position:0% okay so a large chunk of the talk will 00:40:45.480 --> 00:40:47.089 align:start position:0% okay so a large chunk of the talk will also<00:40:45.720> focus<00:40:45.900> on<00:40:46.140> the<00:40:46.260> implementation<00:40:46.680> so<00:40:46.920> what 00:40:47.089 --> 00:40:47.099 align:start position:0% also focus on the implementation so what 00:40:47.099 --> 00:40:49.910 align:start position:0% also focus on the implementation so what does<00:40:47.220> the<00:40:47.339> implementation<00:40:47.760> actually<00:40:48.000> provide 00:40:49.910 --> 00:40:49.920 align:start position:0% does the implementation actually provide 00:40:49.920 --> 00:40:51.710 align:start position:0% does the implementation actually provide um<00:40:50.040> first<00:40:50.520> and<00:40:50.700> foremost<00:40:51.000> it's<00:40:51.300> just<00:40:51.480> a 00:40:51.710 --> 00:40:51.720 align:start position:0% um first and foremost it's just a 00:40:51.720 --> 00:40:53.270 align:start position:0% um first and foremost it's just a framework<00:40:52.020> in<00:40:52.140> which<00:40:52.320> you<00:40:52.440> can<00:40:52.560> express<00:40:52.740> and 00:40:53.270 --> 00:40:53.280 align:start position:0% framework in which you can express and 00:40:53.280 --> 00:40:55.069 align:start position:0% framework in which you can express and represent<00:40:53.579> strategic<00:40:54.180> interactions<00:40:54.660> like 00:40:55.069 --> 00:40:55.079 align:start position:0% represent strategic interactions like 00:40:55.079 --> 00:40:56.990 align:start position:0% represent strategic interactions like the<00:40:55.320> prison<00:40:55.500> dilemma<00:40:56.040> but<00:40:56.400> obviously<00:40:56.760> also 00:40:56.990 --> 00:40:57.000 align:start position:0% the prison dilemma but obviously also 00:40:57.000 --> 00:40:59.210 align:start position:0% the prison dilemma but obviously also more<00:40:57.119> complicated<00:40:57.540> stuff 00:40:59.210 --> 00:40:59.220 align:start position:0% more complicated stuff 00:40:59.220 --> 00:41:01.250 align:start position:0% more complicated stuff many<00:40:59.640> times<00:40:59.880> you're<00:41:00.300> not<00:41:00.540> only<00:41:00.660> interested<00:41:01.140> in 00:41:01.250 --> 00:41:01.260 align:start position:0% many times you're not only interested in 00:41:01.260 --> 00:41:03.050 align:start position:0% many times you're not only interested in representing<00:41:02.040> models<00:41:02.339> but<00:41:02.520> you<00:41:02.700> naturally 00:41:03.050 --> 00:41:03.060 align:start position:0% representing models but you naturally 00:41:03.060 --> 00:41:04.490 align:start position:0% representing models but you naturally are<00:41:03.240> interested<00:41:03.540> in<00:41:03.720> you<00:41:03.900> know<00:41:04.079> what<00:41:04.200> kind<00:41:04.380> of 00:41:04.490 --> 00:41:04.500 align:start position:0% are interested in you know what kind of 00:41:04.500 --> 00:41:06.770 align:start position:0% are interested in you know what kind of behavior<00:41:04.920> may<00:41:05.640> result<00:41:05.880> from<00:41:06.180> these<00:41:06.359> models<00:41:06.599> so 00:41:06.770 --> 00:41:06.780 align:start position:0% behavior may result from these models so 00:41:06.780 --> 00:41:08.870 align:start position:0% behavior may result from these models so you<00:41:06.900> want<00:41:07.020> to<00:41:07.140> you<00:41:07.800> also<00:41:08.220> want<00:41:08.339> to<00:41:08.460> analyze 00:41:08.870 --> 00:41:08.880 align:start position:0% you want to you also want to analyze 00:41:08.880 --> 00:41:11.390 align:start position:0% you want to you also want to analyze them<00:41:09.000> in<00:41:09.540> various<00:41:10.020> ways<00:41:10.380> in<00:41:11.220> the<00:41:11.280> current 00:41:11.390 --> 00:41:11.400 align:start position:0% them in various ways in the current 00:41:11.400 --> 00:41:13.670 align:start position:0% them in various ways in the current engine<00:41:11.640> there<00:41:12.119> are<00:41:12.300> basically<00:41:13.079> three<00:41:13.260> ways<00:41:13.560> to 00:41:13.670 --> 00:41:13.680 align:start position:0% engine there are basically three ways to 00:41:13.680 --> 00:41:16.370 align:start position:0% engine there are basically three ways to do<00:41:13.800> that<00:41:13.920> one<00:41:14.400> is<00:41:14.900> interactively<00:41:15.900> so<00:41:16.260> you 00:41:16.370 --> 00:41:16.380 align:start position:0% do that one is interactively so you 00:41:16.380 --> 00:41:17.810 align:start position:0% do that one is interactively so you basically<00:41:16.619> run<00:41:16.800> a<00:41:16.980> session<00:41:17.160> and<00:41:17.400> then<00:41:17.520> you<00:41:17.700> can 00:41:17.810 --> 00:41:17.820 align:start position:0% basically run a session and then you can 00:41:17.820 --> 00:41:18.829 align:start position:0% basically run a session and then you can query 00:41:18.829 --> 00:41:18.839 align:start position:0% query 00:41:18.839 --> 00:41:20.870 align:start position:0% query um your<00:41:19.079> model<00:41:19.320> let's<00:41:20.099> say<00:41:20.220> I'm<00:41:20.460> looking<00:41:20.640> at<00:41:20.760> a 00:41:20.870 --> 00:41:20.880 align:start position:0% um your model let's say I'm looking at a 00:41:20.880 --> 00:41:23.930 align:start position:0% um your model let's say I'm looking at a stake<00:41:21.180> staking<00:41:21.960> protocol<00:41:22.579> and<00:41:23.579> I<00:41:23.700> have<00:41:23.820> some 00:41:23.930 --> 00:41:23.940 align:start position:0% stake staking protocol and I have some 00:41:23.940 --> 00:41:25.849 align:start position:0% stake staking protocol and I have some idea<00:41:24.180> what<00:41:24.420> would<00:41:24.599> constitute<00:41:25.140> an<00:41:25.560> honest 00:41:25.849 --> 00:41:25.859 align:start position:0% idea what would constitute an honest 00:41:25.859 --> 00:41:27.770 align:start position:0% idea what would constitute an honest strategy<00:41:26.220> of<00:41:26.339> the<00:41:26.520> participants<00:41:27.000> and<00:41:27.540> then<00:41:27.660> I 00:41:27.770 --> 00:41:27.780 align:start position:0% strategy of the participants and then I 00:41:27.780 --> 00:41:29.510 align:start position:0% strategy of the participants and then I can<00:41:27.960> ask<00:41:28.079> okay<00:41:28.440> if<00:41:28.859> I'm<00:41:28.980> feeding<00:41:29.280> in<00:41:29.400> a 00:41:29.510 --> 00:41:29.520 align:start position:0% can ask okay if I'm feeding in a 00:41:29.520 --> 00:41:31.849 align:start position:0% can ask okay if I'm feeding in a strategy<00:41:30.300> this<00:41:30.839> is<00:41:31.020> actually<00:41:31.140> an<00:41:31.380> equilibrium 00:41:31.849 --> 00:41:31.859 align:start position:0% strategy this is actually an equilibrium 00:41:31.859 --> 00:41:34.310 align:start position:0% strategy this is actually an equilibrium or<00:41:32.520> do<00:41:32.820> specifications<00:41:33.480> have<00:41:33.780> an<00:41:33.900> incentive 00:41:34.310 --> 00:41:34.320 align:start position:0% or do specifications have an incentive 00:41:34.320 --> 00:41:36.349 align:start position:0% or do specifications have an incentive to<00:41:34.380> deviate<00:41:34.800> and<00:41:35.339> the<00:41:35.460> way<00:41:35.579> it<00:41:35.700> works<00:41:36.000> is<00:41:36.180> a<00:41:36.300> bit 00:41:36.349 --> 00:41:36.359 align:start position:0% to deviate and the way it works is a bit 00:41:36.359 --> 00:41:38.390 align:start position:0% to deviate and the way it works is a bit like<00:41:36.480> a<00:41:36.660> proof<00:41:36.900> assistant<00:41:37.020> it<00:41:37.920> will<00:41:38.040> tell<00:41:38.220> you 00:41:38.390 --> 00:41:38.400 align:start position:0% like a proof assistant it will tell you 00:41:38.400 --> 00:41:40.250 align:start position:0% like a proof assistant it will tell you you<00:41:38.880> know<00:41:39.000> your<00:41:39.180> proposition<00:41:39.599> that<00:41:40.020> these 00:41:40.250 --> 00:41:40.260 align:start position:0% you know your proposition that these 00:41:40.260 --> 00:41:42.470 align:start position:0% you know your proposition that these strategies<00:41:40.619> make<00:41:40.859> sense<00:41:41.040> either<00:41:41.940> makes<00:41:42.240> sense 00:41:42.470 --> 00:41:42.480 align:start position:0% strategies make sense either makes sense 00:41:42.480 --> 00:41:44.329 align:start position:0% strategies make sense either makes sense and<00:41:42.720> then<00:41:42.839> it's<00:41:42.960> good<00:41:43.260> or<00:41:43.680> it<00:41:43.800> will<00:41:43.920> they<00:41:44.099> will 00:41:44.329 --> 00:41:44.339 align:start position:0% and then it's good or it will they will 00:41:44.339 --> 00:41:45.950 align:start position:0% and then it's good or it will they will the<00:41:44.520> compiler<00:41:44.940> or<00:41:45.060> the<00:41:45.180> engine<00:41:45.300> will<00:41:45.599> tell<00:41:45.780> you 00:41:45.950 --> 00:41:45.960 align:start position:0% the compiler or the engine will tell you 00:41:45.960 --> 00:41:48.349 align:start position:0% the compiler or the engine will tell you wait<00:41:46.320> at<00:41:46.920> least<00:41:47.040> one<00:41:47.220> agent<00:41:47.640> basically<00:41:48.000> has<00:41:48.180> an 00:41:48.349 --> 00:41:48.359 align:start position:0% wait at least one agent basically has an 00:41:48.359 --> 00:41:50.030 align:start position:0% wait at least one agent basically has an incentive<00:41:48.660> to<00:41:48.780> deviate<00:41:49.200> and<00:41:49.619> here's<00:41:49.920> the 00:41:50.030 --> 00:41:50.040 align:start position:0% incentive to deviate and here's the 00:41:50.040 --> 00:41:51.890 align:start position:0% incentive to deviate and here's the incentive<00:41:50.400> here's<00:41:50.700> a<00:41:50.820> specific<00:41:51.000> action<00:41:51.359> that 00:41:51.890 --> 00:41:51.900 align:start position:0% incentive here's a specific action that 00:41:51.900 --> 00:41:54.650 align:start position:0% incentive here's a specific action that this<00:41:52.020> player<00:41:52.320> can<00:41:52.500> take 00:41:54.650 --> 00:41:54.660 align:start position:0% 00:41:54.660 --> 00:41:55.490 align:start position:0% um 00:41:55.490 --> 00:41:55.500 align:start position:0% um 00:41:55.500 --> 00:41:57.470 align:start position:0% um now<00:41:55.859> the<00:41:56.099> interactive<00:41:56.520> part<00:41:56.700> is<00:41:57.000> very<00:41:57.180> useful 00:41:57.470 --> 00:41:57.480 align:start position:0% now the interactive part is very useful 00:41:57.480 --> 00:41:59.510 align:start position:0% now the interactive part is very useful to<00:41:57.900> explore<00:41:58.200> parts<00:41:58.560> of<00:41:58.740> the<00:41:58.859> model<00:41:58.980> and<00:41:59.280> for 00:41:59.510 --> 00:41:59.520 align:start position:0% to explore parts of the model and for 00:41:59.520 --> 00:42:01.310 align:start position:0% to explore parts of the model and for the<00:41:59.700> staking<00:41:59.940> stuff<00:42:00.240> we<00:42:00.660> will<00:42:00.839> also<00:42:01.020> see<00:42:01.140> an 00:42:01.310 --> 00:42:01.320 align:start position:0% the staking stuff we will also see an 00:42:01.320 --> 00:42:03.050 align:start position:0% the staking stuff we will also see an extended<00:42:01.680> example<00:42:01.980> on<00:42:02.160> this<00:42:02.339> it's<00:42:02.820> quite 00:42:03.050 --> 00:42:03.060 align:start position:0% extended example on this it's quite 00:42:03.060 --> 00:42:04.849 align:start position:0% extended example on this it's quite useful<00:42:03.359> to<00:42:03.540> think<00:42:03.660> about<00:42:03.839> specific<00:42:04.440> vectors 00:42:04.849 --> 00:42:04.859 align:start position:0% useful to think about specific vectors 00:42:04.859 --> 00:42:06.650 align:start position:0% useful to think about specific vectors of<00:42:04.980> attack<00:42:05.160> and<00:42:05.460> then<00:42:05.579> you<00:42:05.700> can<00:42:05.820> verify<00:42:06.180> does 00:42:06.650 --> 00:42:06.660 align:start position:0% of attack and then you can verify does 00:42:06.660 --> 00:42:08.930 align:start position:0% of attack and then you can verify does this<00:42:06.900> actually<00:42:07.079> work<00:42:07.380> or<00:42:07.980> you<00:42:08.280> know<00:42:08.400> what<00:42:08.579> two 00:42:08.930 --> 00:42:08.940 align:start position:0% this actually work or you know what two 00:42:08.940 --> 00:42:10.849 align:start position:0% this actually work or you know what two specific<00:42:09.300> agents<00:42:09.780> actually<00:42:09.960> react<00:42:10.320> to<00:42:10.440> If<00:42:10.680> a 00:42:10.849 --> 00:42:10.859 align:start position:0% specific agents actually react to If a 00:42:10.859 --> 00:42:13.069 align:start position:0% specific agents actually react to If a strategy<00:42:11.220> of<00:42:11.339> another<00:42:11.520> player<00:42:11.880> changes 00:42:13.069 --> 00:42:13.079 align:start position:0% strategy of another player changes 00:42:13.079 --> 00:42:14.930 align:start position:0% strategy of another player changes you<00:42:13.619> can<00:42:13.680> also<00:42:13.859> think<00:42:13.980> about<00:42:14.160> this<00:42:14.460> for<00:42:14.700> pizza 00:42:14.930 --> 00:42:14.940 align:start position:0% you can also think about this for pizza 00:42:14.940 --> 00:42:16.250 align:start position:0% you can also think about this for pizza alluded<00:42:15.420> to<00:42:15.540> that 00:42:16.250 --> 00:42:16.260 align:start position:0% alluded to that 00:42:16.260 --> 00:42:18.050 align:start position:0% alluded to that um that<00:42:16.619> there<00:42:16.859> is<00:42:17.040> a<00:42:17.099> system<00:42:17.220> a<00:42:17.520> which<00:42:17.940> is 00:42:18.050 --> 00:42:18.060 align:start position:0% um that there is a system a which is 00:42:18.060 --> 00:42:20.510 align:start position:0% um that there is a system a which is somehow<00:42:18.359> represented<00:42:18.900> as<00:42:19.020> an<00:42:19.140> open<00:42:19.260> game<00:42:19.520> or 00:42:20.510 --> 00:42:20.520 align:start position:0% somehow represented as an open game or 00:42:20.520 --> 00:42:22.370 align:start position:0% somehow represented as an open game or several<00:42:21.000> open<00:42:21.119> games<00:42:21.359> you<00:42:21.720> make<00:42:21.900> changes<00:42:22.260> in 00:42:22.370 --> 00:42:22.380 align:start position:0% several open games you make changes in 00:42:22.380 --> 00:42:24.109 align:start position:0% several open games you make changes in that<00:42:22.560> system<00:42:22.740> these<00:42:23.160> changes<00:42:23.400> propagate<00:42:23.880> in 00:42:24.109 --> 00:42:24.119 align:start position:0% that system these changes propagate in 00:42:24.119 --> 00:42:25.430 align:start position:0% that system these changes propagate in your<00:42:24.240> open<00:42:24.359> games<00:42:24.599> and<00:42:25.020> then<00:42:25.079> in<00:42:25.260> the<00:42:25.380> back 00:42:25.430 --> 00:42:25.440 align:start position:0% your open games and then in the back 00:42:25.440 --> 00:42:27.349 align:start position:0% your open games and then in the back you're<00:42:25.619> running<00:42:25.800> tests<00:42:26.220> on<00:42:26.520> what<00:42:27.119> kind<00:42:27.240> of 00:42:27.349 --> 00:42:27.359 align:start position:0% you're running tests on what kind of 00:42:27.359 --> 00:42:28.849 align:start position:0% you're running tests on what kind of behavior<00:42:27.660> would<00:42:27.839> you<00:42:27.960> expect<00:42:28.079> from<00:42:28.500> this<00:42:28.680> kind 00:42:28.849 --> 00:42:28.859 align:start position:0% behavior would you expect from this kind 00:42:28.859 --> 00:42:30.589 align:start position:0% behavior would you expect from this kind of<00:42:28.980> system<00:42:29.160> yeah<00:42:29.579> so<00:42:29.880> it<00:42:30.060> might<00:42:30.180> be<00:42:30.300> that<00:42:30.420> you 00:42:30.589 --> 00:42:30.599 align:start position:0% of system yeah so it might be that you 00:42:30.599 --> 00:42:32.630 align:start position:0% of system yeah so it might be that you have<00:42:30.720> an<00:42:30.839> incentive<00:42:31.200> mechanism<00:42:31.560> and<00:42:32.220> it<00:42:32.339> works 00:42:32.630 --> 00:42:32.640 align:start position:0% have an incentive mechanism and it works 00:42:32.640 --> 00:42:33.950 align:start position:0% have an incentive mechanism and it works but<00:42:32.760> you<00:42:32.880> make<00:42:33.000> a<00:42:33.119> change<00:42:33.300> to<00:42:33.480> the<00:42:33.660> overall 00:42:33.950 --> 00:42:33.960 align:start position:0% but you make a change to the overall 00:42:33.960 --> 00:42:36.050 align:start position:0% but you make a change to the overall protocol<00:42:34.380> a<00:42:34.680> how<00:42:35.160> does<00:42:35.400> that<00:42:35.579> actually<00:42:35.820> is 00:42:36.050 --> 00:42:36.060 align:start position:0% protocol a how does that actually is 00:42:36.060 --> 00:42:37.430 align:start position:0% protocol a how does that actually is then<00:42:36.240> this<00:42:36.480> is<00:42:36.599> translated<00:42:36.900> into<00:42:37.140> the<00:42:37.260> open 00:42:37.430 --> 00:42:37.440 align:start position:0% then this is translated into the open 00:42:37.440 --> 00:42:38.750 align:start position:0% then this is translated into the open games<00:42:37.619> framework<00:42:38.099> and<00:42:38.280> in<00:42:38.400> the<00:42:38.520> back<00:42:38.579> you're 00:42:38.750 --> 00:42:38.760 align:start position:0% games framework and in the back you're 00:42:38.760 --> 00:42:40.370 align:start position:0% games framework and in the back you're running<00:42:39.000> tests<00:42:39.359> on<00:42:39.599> the<00:42:39.839> behavior<00:42:40.140> of<00:42:40.260> the 00:42:40.370 --> 00:42:40.380 align:start position:0% running tests on the behavior of the 00:42:40.380 --> 00:42:42.470 align:start position:0% running tests on the behavior of the agents<00:42:40.740> and<00:42:41.040> then<00:42:41.160> maybe<00:42:41.400> things<00:42:42.000> go<00:42:42.300> through 00:42:42.470 --> 00:42:42.480 align:start position:0% agents and then maybe things go through 00:42:42.480 --> 00:42:44.870 align:start position:0% agents and then maybe things go through or<00:42:43.020> you<00:42:43.560> get<00:42:43.680> a<00:42:43.859> warning<00:42:44.160> something<00:42:44.520> is<00:42:44.700> not 00:42:44.870 --> 00:42:44.880 align:start position:0% or you get a warning something is not 00:42:44.880 --> 00:42:46.970 align:start position:0% or you get a warning something is not working<00:42:45.000> anymore<00:42:45.300> as<00:42:45.599> before 00:42:46.970 --> 00:42:46.980 align:start position:0% working anymore as before 00:42:46.980 --> 00:42:49.730 align:start position:0% working anymore as before and<00:42:47.579> lastly<00:42:47.940> theoretically<00:42:48.839> as<00:42:49.260> well<00:42:49.440> as<00:42:49.560> from 00:42:49.730 --> 00:42:49.740 align:start position:0% and lastly theoretically as well as from 00:42:49.740 --> 00:42:51.170 align:start position:0% and lastly theoretically as well as from a<00:42:49.920> practical<00:42:50.160> implementation<00:42:50.700> perspective 00:42:51.170 --> 00:42:51.180 align:start position:0% a practical implementation perspective 00:42:51.180 --> 00:42:52.970 align:start position:0% a practical implementation perspective there's<00:42:51.839> a<00:42:52.079> very<00:42:52.140> close<00:42:52.320> connection<00:42:52.560> to 00:42:52.970 --> 00:42:52.980 align:start position:0% there's a very close connection to 00:42:52.980 --> 00:42:54.710 align:start position:0% there's a very close connection to machine<00:42:53.520> learning<00:42:53.880> framework<00:42:54.240> specifically 00:42:54.710 --> 00:42:54.720 align:start position:0% machine learning framework specifically 00:42:54.720 --> 00:42:56.930 align:start position:0% machine learning framework specifically reinforcement<00:42:55.320> learning<00:42:56.099> I<00:42:56.520> will<00:42:56.640> say<00:42:56.760> a<00:42:56.880> bit 00:42:56.930 --> 00:42:56.940 align:start position:0% reinforcement learning I will say a bit 00:42:56.940 --> 00:42:58.849 align:start position:0% reinforcement learning I will say a bit more<00:42:57.119> at<00:42:57.240> the<00:42:57.359> end<00:42:57.420> if<00:42:57.599> I<00:42:57.720> have<00:42:57.839> time<00:42:58.020> but<00:42:58.740> the 00:42:58.849 --> 00:42:58.859 align:start position:0% more at the end if I have time but the 00:42:58.859 --> 00:43:00.170 align:start position:0% more at the end if I have time but the idea<00:42:59.099> basically<00:42:59.400> is<00:42:59.520> that<00:42:59.760> you<00:42:59.940> can<00:43:00.060> either 00:43:00.170 --> 00:43:00.180 align:start position:0% idea basically is that you can either 00:43:00.180 --> 00:43:01.910 align:start position:0% idea basically is that you can either leverage<00:43:00.619> reinforcement<00:43:01.619> learning 00:43:01.910 --> 00:43:01.920 align:start position:0% leverage reinforcement learning 00:43:01.920 --> 00:43:02.930 align:start position:0% leverage reinforcement learning techniques<00:43:02.280> and<00:43:02.520> machine<00:43:02.700> learning 00:43:02.930 --> 00:43:02.940 align:start position:0% techniques and machine learning 00:43:02.940 --> 00:43:04.790 align:start position:0% techniques and machine learning techniques<00:43:03.420> more<00:43:03.540> generally<00:43:03.839> for<00:43:04.440> solving 00:43:04.790 --> 00:43:04.800 align:start position:0% techniques more generally for solving 00:43:04.800 --> 00:43:06.710 align:start position:0% techniques more generally for solving and<00:43:04.980> analyzing<00:43:05.400> games<00:43:05.640> solving<00:43:06.480> of<00:43:06.599> course 00:43:06.710 --> 00:43:06.720 align:start position:0% and analyzing games solving of course 00:43:06.720 --> 00:43:08.030 align:start position:0% and analyzing games solving of course has<00:43:06.900> limitations<00:43:07.319> because<00:43:07.619> it's<00:43:07.800> very 00:43:08.030 --> 00:43:08.040 align:start position:0% has limitations because it's very 00:43:08.040 --> 00:43:11.150 align:start position:0% has limitations because it's very complex<00:43:08.420> but<00:43:09.420> for<00:43:09.900> some<00:43:10.079> specific<00:43:10.560> games<00:43:10.800> it's 00:43:11.150 --> 00:43:11.160 align:start position:0% complex but for some specific games it's 00:43:11.160 --> 00:43:13.309 align:start position:0% complex but for some specific games it's feasible<00:43:11.579> and<00:43:12.359> on<00:43:12.540> the<00:43:12.660> other<00:43:12.720> hand<00:43:12.900> you<00:43:13.260> can 00:43:13.309 --> 00:43:13.319 align:start position:0% feasible and on the other hand you can 00:43:13.319 --> 00:43:14.990 align:start position:0% feasible and on the other hand you can also<00:43:13.500> turn<00:43:13.619> it<00:43:13.800> around<00:43:13.980> you<00:43:14.579> can<00:43:14.640> also<00:43:14.880> make 00:43:14.990 --> 00:43:15.000 align:start position:0% also turn it around you can also make 00:43:15.000 --> 00:43:16.790 align:start position:0% also turn it around you can also make Learners<00:43:15.480> basically<00:43:15.839> part<00:43:16.020> of<00:43:16.200> the<00:43:16.319> game<00:43:16.440> so 00:43:16.790 --> 00:43:16.800 align:start position:0% Learners basically part of the game so 00:43:16.800 --> 00:43:18.589 align:start position:0% Learners basically part of the game so that<00:43:16.920> you<00:43:17.040> have<00:43:17.160> an<00:43:17.280> interactive<00:43:17.760> interaction 00:43:18.589 --> 00:43:18.599 align:start position:0% that you have an interactive interaction 00:43:18.599 --> 00:43:20.510 align:start position:0% that you have an interactive interaction of<00:43:18.839> learning<00:43:19.200> agents<00:43:19.560> basically 00:43:20.510 --> 00:43:20.520 align:start position:0% of learning agents basically 00:43:20.520 --> 00:43:22.250 align:start position:0% of learning agents basically which<00:43:21.000> is<00:43:21.119> also<00:43:21.359> quite<00:43:21.540> useful<00:43:21.780> because<00:43:21.960> you 00:43:22.250 --> 00:43:22.260 align:start position:0% which is also quite useful because you 00:43:22.260 --> 00:43:23.390 align:start position:0% which is also quite useful because you basically<00:43:22.500> have<00:43:22.680> to<00:43:22.800> think<00:43:22.859> about<00:43:22.980> this<00:43:23.220> as 00:43:23.390 --> 00:43:23.400 align:start position:0% basically have to think about this as 00:43:23.400 --> 00:43:25.370 align:start position:0% basically have to think about this as you<00:43:23.819> know<00:43:23.880> institutional<00:43:24.420> players 00:43:25.370 --> 00:43:25.380 align:start position:0% you know institutional players 00:43:25.380 --> 00:43:27.530 align:start position:0% you know institutional players um<00:43:25.440> updating<00:43:25.800> or<00:43:26.220> actually<00:43:27.119> um<00:43:27.180> Learners 00:43:27.530 --> 00:43:27.540 align:start position:0% um updating or actually um Learners 00:43:27.540 --> 00:43:29.870 align:start position:0% um updating or actually um Learners themselves<00:43:27.960> as<00:43:28.319> part<00:43:28.859> of<00:43:29.040> the 00:43:29.870 --> 00:43:29.880 align:start position:0% themselves as part of the 00:43:29.880 --> 00:43:31.309 align:start position:0% themselves as part of the um<00:43:29.940> of<00:43:30.180> the<00:43:30.240> model<00:43:30.359> for<00:43:30.720> instance<00:43:30.839> in<00:43:31.020> pricing 00:43:31.309 --> 00:43:31.319 align:start position:0% um of the model for instance in pricing 00:43:31.319 --> 00:43:32.569 align:start position:0% um of the model for instance in pricing settings 00:43:32.569 --> 00:43:32.579 align:start position:0% settings 00:43:32.579 --> 00:43:35.390 align:start position:0% settings okay 00:43:35.390 --> 00:43:35.400 align:start position:0% 00:43:35.400 --> 00:43:37.490 align:start position:0% um 00:43:37.490 --> 00:43:37.500 align:start position:0% um 00:43:37.500 --> 00:43:39.890 align:start position:0% um what's<00:43:37.859> the<00:43:38.040> key<00:43:38.160> Innovation<00:43:38.520> well 00:43:39.890 --> 00:43:39.900 align:start position:0% what's the key Innovation well 00:43:39.900 --> 00:43:42.230 align:start position:0% what's the key Innovation well compositionality<00:43:40.859> obviously<00:43:41.339> that's<00:43:41.880> a<00:43:42.119> key 00:43:42.230 --> 00:43:42.240 align:start position:0% compositionality obviously that's a key 00:43:42.240 --> 00:43:43.790 align:start position:0% compositionality obviously that's a key point<00:43:42.420> but<00:43:42.960> what<00:43:43.140> does<00:43:43.260> it<00:43:43.440> actually<00:43:43.560> mean 00:43:43.790 --> 00:43:43.800 align:start position:0% point but what does it actually mean 00:43:43.800 --> 00:43:45.890 align:start position:0% point but what does it actually mean here 00:43:45.890 --> 00:43:45.900 align:start position:0% here 00:43:45.900 --> 00:43:47.450 align:start position:0% here if<00:43:46.319> you<00:43:46.380> think<00:43:46.500> about<00:43:46.619> the<00:43:46.740> prisoner<00:43:47.099> dilemma 00:43:47.450 --> 00:43:47.460 align:start position:0% if you think about the prisoner dilemma 00:43:47.460 --> 00:43:49.609 align:start position:0% if you think about the prisoner dilemma what<00:43:47.640> is<00:43:47.819> already<00:43:47.940> showed<00:43:48.839> um<00:43:48.900> is<00:43:49.140> that<00:43:49.319> you 00:43:49.609 --> 00:43:49.619 align:start position:0% what is already showed um is that you 00:43:49.619 --> 00:43:51.349 align:start position:0% what is already showed um is that you can<00:43:49.740> think<00:43:49.859> about<00:43:50.040> the<00:43:50.220> prison<00:43:50.400> dilemma<00:43:50.880> at 00:43:51.349 --> 00:43:51.359 align:start position:0% can think about the prison dilemma at 00:43:51.359 --> 00:43:53.150 align:start position:0% can think about the prison dilemma at least<00:43:51.420> from<00:43:52.020> what<00:43:52.200> you<00:43:52.260> have<00:43:52.380> seen<00:43:52.560> so<00:43:52.800> far<00:43:52.920> as 00:43:53.150 --> 00:43:53.160 align:start position:0% least from what you have seen so far as 00:43:53.160 --> 00:43:55.250 align:start position:0% least from what you have seen so far as either<00:43:53.400> one<00:43:53.700> monolithic<00:43:54.119> building<00:43:54.300> block<00:43:54.599> or 00:43:55.250 --> 00:43:55.260 align:start position:0% either one monolithic building block or 00:43:55.260 --> 00:43:56.870 align:start position:0% either one monolithic building block or at<00:43:55.440> the<00:43:55.560> minimum<00:43:55.800> you're<00:43:56.160> splitting<00:43:56.520> it<00:43:56.640> up<00:43:56.760> in 00:43:56.870 --> 00:43:56.880 align:start position:0% at the minimum you're splitting it up in 00:43:56.880 --> 00:43:58.910 align:start position:0% at the minimum you're splitting it up in three<00:43:57.060> components<00:43:57.540> right<00:43:58.200> now<00:43:58.619> for<00:43:58.800> a 00:43:58.910 --> 00:43:58.920 align:start position:0% three components right now for a 00:43:58.920 --> 00:44:01.190 align:start position:0% three components right now for a prisoner<00:43:59.220> dilemma<00:43:59.520> that's<00:44:00.180> not<00:44:00.599> that 00:44:01.190 --> 00:44:01.200 align:start position:0% prisoner dilemma that's not that 00:44:01.200 --> 00:44:03.050 align:start position:0% prisoner dilemma that's not that relevant<00:44:01.619> but<00:44:02.040> the<00:44:02.280> more<00:44:02.520> complex<00:44:02.819> your 00:44:03.050 --> 00:44:03.060 align:start position:0% relevant but the more complex your 00:44:03.060 --> 00:44:05.270 align:start position:0% relevant but the more complex your scenarios<00:44:03.599> become<00:44:04.020> the<00:44:04.740> more<00:44:04.859> helpful<00:44:05.099> it 00:44:05.270 --> 00:44:05.280 align:start position:0% scenarios become the more helpful it 00:44:05.280 --> 00:44:07.910 align:start position:0% scenarios become the more helpful it actually<00:44:05.460> is<00:44:05.700> to<00:44:06.000> say<00:44:06.240> look<00:44:06.720> I'm<00:44:07.380> taking<00:44:07.619> that 00:44:07.910 --> 00:44:07.920 align:start position:0% actually is to say look I'm taking that 00:44:07.920 --> 00:44:10.609 align:start position:0% actually is to say look I'm taking that part<00:44:08.160> I'm<00:44:08.520> zooming<00:44:08.880> in<00:44:09.000> I'm<00:44:09.359> modeling<00:44:09.780> it<00:44:09.900> zoom 00:44:10.609 --> 00:44:10.619 align:start position:0% part I'm zooming in I'm modeling it zoom 00:44:10.619 --> 00:44:12.950 align:start position:0% part I'm zooming in I'm modeling it zoom out<00:44:10.740> take<00:44:11.220> another<00:44:11.400> part<00:44:11.700> model<00:44:12.180> that<00:44:12.480> zoom 00:44:12.950 --> 00:44:12.960 align:start position:0% out take another part model that zoom 00:44:12.960 --> 00:44:15.349 align:start position:0% out take another part model that zoom out<00:44:13.079> and<00:44:13.380> so<00:44:13.500> on<00:44:13.619> and<00:44:13.740> so<00:44:13.920> on<00:44:14.040> and<00:44:14.460> later<00:44:14.579> on<00:44:14.819> if 00:44:15.349 --> 00:44:15.359 align:start position:0% out and so on and so on and later on if 00:44:15.359 --> 00:44:16.490 align:start position:0% out and so on and so on and later on if you<00:44:15.480> do<00:44:15.599> it<00:44:15.720> right<00:44:15.839> you<00:44:16.079> have<00:44:16.200> basically 00:44:16.490 --> 00:44:16.500 align:start position:0% you do it right you have basically 00:44:16.500 --> 00:44:18.290 align:start position:0% you do it right you have basically systematic<00:44:17.220> ways<00:44:17.579> of<00:44:17.640> composing<00:44:18.060> these 00:44:18.290 --> 00:44:18.300 align:start position:0% systematic ways of composing these 00:44:18.300 --> 00:44:20.990 align:start position:0% systematic ways of composing these things<00:44:18.420> together<00:44:18.660> into<00:44:19.200> a<00:44:19.440> bigger<00:44:19.680> model 00:44:20.990 --> 00:44:21.000 align:start position:0% things together into a bigger model 00:44:21.000 --> 00:44:22.130 align:start position:0% things together into a bigger model now 00:44:22.130 --> 00:44:22.140 align:start position:0% now 00:44:22.140 --> 00:44:24.650 align:start position:0% now this<00:44:22.680> doesn't<00:44:22.800> end<00:44:23.099> at<00:44:23.339> that<00:44:23.460> level<00:44:23.700> you<00:44:24.599> can 00:44:24.650 --> 00:44:24.660 align:start position:0% this doesn't end at that level you can 00:44:24.660 --> 00:44:27.650 align:start position:0% this doesn't end at that level you can also<00:44:25.079> for<00:44:25.859> programming<00:44:26.819> purposes<00:44:27.180> or<00:44:27.480> because 00:44:27.650 --> 00:44:27.660 align:start position:0% also for programming purposes or because 00:44:27.660 --> 00:44:29.990 align:start position:0% also for programming purposes or because of<00:44:27.839> convenience<00:44:28.260> you<00:44:28.560> can<00:44:28.619> further 00:44:29.990 --> 00:44:30.000 align:start position:0% of convenience you can further 00:44:30.000 --> 00:44:31.790 align:start position:0% of convenience you can further um modernize<00:44:30.540> your<00:44:30.900> code<00:44:31.020> let's<00:44:31.440> say<00:44:31.619> there 00:44:31.790 --> 00:44:31.800 align:start position:0% um modernize your code let's say there 00:44:31.800 --> 00:44:33.589 align:start position:0% um modernize your code let's say there is<00:44:31.920> a<00:44:32.040> specific<00:44:32.220> thing<00:44:32.460> a<00:44:32.700> specific<00:44:32.940> way<00:44:33.420> you 00:44:33.589 --> 00:44:33.599 align:start position:0% is a specific thing a specific way you 00:44:33.599 --> 00:44:35.150 align:start position:0% is a specific thing a specific way you want<00:44:33.720> to<00:44:33.839> approach<00:44:34.079> it<00:44:34.200> you<00:44:34.500> can<00:44:34.619> split<00:44:34.920> this 00:44:35.150 --> 00:44:35.160 align:start position:0% want to approach it you can split this 00:44:35.160 --> 00:44:37.790 align:start position:0% want to approach it you can split this up<00:44:35.480> implement<00:44:36.480> it<00:44:36.660> in<00:44:36.780> different<00:44:36.900> ways<00:44:37.319> and 00:44:37.790 --> 00:44:37.800 align:start position:0% up implement it in different ways and 00:44:37.800 --> 00:44:39.710 align:start position:0% up implement it in different ways and the<00:44:37.980> key<00:44:38.160> thing<00:44:38.339> about<00:44:39.119> all<00:44:39.420> of<00:44:39.540> this 00:44:39.710 --> 00:44:39.720 align:start position:0% the key thing about all of this 00:44:39.720 --> 00:44:42.589 align:start position:0% the key thing about all of this basically<00:44:40.140> so<00:44:40.380> far<00:44:40.619> is<00:44:41.339> that 00:44:42.589 --> 00:44:42.599 align:start position:0% basically so far is that 00:44:42.599 --> 00:44:44.809 align:start position:0% basically so far is that all<00:44:43.380> what<00:44:43.680> you're<00:44:43.800> doing<00:44:43.980> will<00:44:44.220> be<00:44:44.400> guaranteed 00:44:44.809 --> 00:44:44.819 align:start position:0% all what you're doing will be guaranteed 00:44:44.819 --> 00:44:47.690 align:start position:0% all what you're doing will be guaranteed to<00:44:45.060> make<00:44:45.420> game<00:44:45.839> theoretic<00:44:46.380> sense<00:44:46.619> if<00:44:47.579> you 00:44:47.690 --> 00:44:47.700 align:start position:0% to make game theoretic sense if you 00:44:47.700 --> 00:44:49.069 align:start position:0% to make game theoretic sense if you follow<00:44:47.880> basically<00:44:48.359> the<00:44:48.540> syntactic 00:44:49.069 --> 00:44:49.079 align:start position:0% follow basically the syntactic 00:44:49.079 --> 00:44:51.470 align:start position:0% follow basically the syntactic descriptions<00:44:49.740> or<00:44:50.040> restrict<00:44:50.579> restrictions<00:44:51.180> of 00:44:51.470 --> 00:44:51.480 align:start position:0% descriptions or restrict restrictions of 00:44:51.480 --> 00:44:53.270 align:start position:0% descriptions or restrict restrictions of the<00:44:51.660> engine<00:44:51.780> that<00:44:52.619> means<00:44:52.859> you<00:44:52.980> start<00:44:53.099> out 00:44:53.270 --> 00:44:53.280 align:start position:0% the engine that means you start out 00:44:53.280 --> 00:44:55.609 align:start position:0% the engine that means you start out modeling<00:44:53.700> if<00:44:54.000> you<00:44:54.060> use<00:44:54.240> our<00:44:54.420> language<00:44:54.720> you<00:44:55.440> end 00:44:55.609 --> 00:44:55.619 align:start position:0% modeling if you use our language you end 00:44:55.619 --> 00:44:57.710 align:start position:0% modeling if you use our language you end up<00:44:55.800> you<00:44:56.220> can<00:44:56.339> decompose<00:44:56.940> things<00:44:57.180> each<00:44:57.480> of 00:44:57.710 --> 00:44:57.720 align:start position:0% up you can decompose things each of 00:44:57.720 --> 00:44:59.210 align:start position:0% up you can decompose things each of these<00:44:57.900> components<00:44:58.319> will<00:44:58.500> make<00:44:58.680> sense<00:44:58.859> from<00:44:59.099> a 00:44:59.210 --> 00:44:59.220 align:start position:0% these components will make sense from a 00:44:59.220 --> 00:45:01.250 align:start position:0% these components will make sense from a gametheory<00:44:59.640> perspective<00:45:00.119> and<00:45:00.720> the<00:45:00.900> composed 00:45:01.250 --> 00:45:01.260 align:start position:0% gametheory perspective and the composed 00:45:01.260 --> 00:45:02.510 align:start position:0% gametheory perspective and the composed thing<00:45:01.440> will<00:45:01.560> also<00:45:01.800> make<00:45:01.920> game<00:45:02.160> Authority 00:45:02.510 --> 00:45:02.520 align:start position:0% thing will also make game Authority 00:45:02.520 --> 00:45:04.609 align:start position:0% thing will also make game Authority sense<00:45:02.760> that's<00:45:03.300> compositionality<00:45:04.079> at<00:45:04.380> action 00:45:04.609 --> 00:45:04.619 align:start position:0% sense that's compositionality at action 00:45:04.619 --> 00:45:06.710 align:start position:0% sense that's compositionality at action why<00:45:05.339> is<00:45:05.520> this<00:45:05.640> useful<00:45:05.940> well<00:45:06.240> you<00:45:06.420> get<00:45:06.599> an 00:45:06.710 --> 00:45:06.720 align:start position:0% why is this useful well you get an 00:45:06.720 --> 00:45:08.870 align:start position:0% why is this useful well you get an overall<00:45:07.079> few<00:45:07.319> on<00:45:07.740> the<00:45:07.800> over<00:45:07.920> on<00:45:08.339> the<00:45:08.460> on<00:45:08.700> your 00:45:08.870 --> 00:45:08.880 align:start position:0% overall few on the over on the on your 00:45:08.880 --> 00:45:10.970 align:start position:0% overall few on the over on the on your situation<00:45:09.180> that<00:45:09.359> you<00:45:09.540> want<00:45:09.660> to<00:45:09.780> model<00:45:09.900> and<00:45:10.800> it 00:45:10.970 --> 00:45:10.980 align:start position:0% situation that you want to model and it 00:45:10.980 --> 00:45:12.890 align:start position:0% situation that you want to model and it is<00:45:11.160> sound<00:45:11.640> and<00:45:12.000> you<00:45:12.119> can<00:45:12.240> ask<00:45:12.420> questions<00:45:12.660> like 00:45:12.890 --> 00:45:12.900 align:start position:0% is sound and you can ask questions like 00:45:12.900 --> 00:45:14.809 align:start position:0% is sound and you can ask questions like okay<00:45:13.140> what's<00:45:13.380> equilibrium<00:45:13.920> of<00:45:14.040> that<00:45:14.220> or<00:45:14.579> you 00:45:14.809 --> 00:45:14.819 align:start position:0% okay what's equilibrium of that or you 00:45:14.819 --> 00:45:16.970 align:start position:0% okay what's equilibrium of that or you know<00:45:14.940> if<00:45:15.420> we<00:45:15.540> repeat<00:45:15.720> it<00:45:16.500> um<00:45:16.500> a<00:45:16.740> Serial 00:45:16.970 --> 00:45:16.980 align:start position:0% know if we repeat it um a Serial 00:45:16.980 --> 00:45:18.290 align:start position:0% know if we repeat it um a Serial deviation<00:45:17.280> strategy<00:45:17.700> if<00:45:17.880> you<00:45:18.000> think<00:45:18.119> about 00:45:18.290 --> 00:45:18.300 align:start position:0% deviation strategy if you think about 00:45:18.300 --> 00:45:20.089 align:start position:0% deviation strategy if you think about more<00:45:18.960> um<00:45:18.960> like<00:45:19.140> a<00:45:19.260> Markov<00:45:19.560> strategy<00:45:19.980> for 00:45:20.089 --> 00:45:20.099 align:start position:0% more um like a Markov strategy for 00:45:20.099 --> 00:45:22.130 align:start position:0% more um like a Markov strategy for instance<00:45:20.339> other<00:45:20.640> ways<00:45:21.060> of 00:45:22.130 --> 00:45:22.140 align:start position:0% instance other ways of 00:45:22.140 --> 00:45:23.510 align:start position:0% instance other ways of um<00:45:22.200> deviating<00:45:22.800> that<00:45:23.040> a<00:45:23.160> profitable 00:45:23.510 --> 00:45:23.520 align:start position:0% um deviating that a profitable 00:45:23.520 --> 00:45:26.569 align:start position:0% um deviating that a profitable profitable<00:45:24.240> for<00:45:24.480> specific<00:45:24.720> players 00:45:26.569 --> 00:45:26.579 align:start position:0% profitable for specific players 00:45:26.579 --> 00:45:28.430 align:start position:0% profitable for specific players another<00:45:27.119> perspective<00:45:27.599> basically<00:45:28.020> is<00:45:28.200> that 00:45:28.430 --> 00:45:28.440 align:start position:0% another perspective basically is that 00:45:28.440 --> 00:45:29.930 align:start position:0% another perspective basically is that this<00:45:28.619> turns<00:45:28.920> the<00:45:29.040> pro<00:45:29.160> the<00:45:29.400> modeling<00:45:29.700> exercise 00:45:29.930 --> 00:45:29.940 align:start position:0% this turns the pro the modeling exercise 00:45:29.940 --> 00:45:32.630 align:start position:0% this turns the pro the modeling exercise into<00:45:30.359> a<00:45:30.599> programming<00:45:30.960> exercise<00:45:31.200> so<00:45:32.040> the<00:45:32.400> idea 00:45:32.630 --> 00:45:32.640 align:start position:0% into a programming exercise so the idea 00:45:32.640 --> 00:45:34.790 align:start position:0% into a programming exercise so the idea of<00:45:32.700> zooming<00:45:33.119> in<00:45:33.240> and<00:45:33.359> zooming<00:45:33.720> out<00:45:33.839> I'm<00:45:34.500> sorry 00:45:34.790 --> 00:45:34.800 align:start position:0% of zooming in and zooming out I'm sorry 00:45:34.800 --> 00:45:37.670 align:start position:0% of zooming in and zooming out I'm sorry and<00:45:35.760> you<00:45:36.180> know<00:45:36.300> modeling<00:45:36.839> Parts<00:45:37.020> in<00:45:37.260> isolation 00:45:37.670 --> 00:45:37.680 align:start position:0% and you know modeling Parts in isolation 00:45:37.680 --> 00:45:39.530 align:start position:0% and you know modeling Parts in isolation is<00:45:38.220> more<00:45:38.400> or<00:45:38.520> less<00:45:38.520> just<00:45:38.940> like<00:45:39.060> divide<00:45:39.420> and 00:45:39.530 --> 00:45:39.540 align:start position:0% is more or less just like divide and 00:45:39.540 --> 00:45:41.390 align:start position:0% is more or less just like divide and conquer<00:45:39.780> a<00:45:39.900> typical<00:45:40.140> pattern<00:45:40.560> that<00:45:41.220> you<00:45:41.280> would 00:45:41.390 --> 00:45:41.400 align:start position:0% conquer a typical pattern that you would 00:45:41.400 --> 00:45:44.030 align:start position:0% conquer a typical pattern that you would apply<00:45:41.700> in<00:45:41.819> any<00:45:42.000> kind<00:45:42.119> of<00:45:42.240> or<00:45:42.420> many<00:45:42.660> programming 00:45:44.030 --> 00:45:44.040 align:start position:0% apply in any kind of or many programming 00:45:44.040 --> 00:45:46.130 align:start position:0% apply in any kind of or many programming um problems 00:45:46.130 --> 00:45:46.140 align:start position:0% um problems 00:45:46.140 --> 00:45:47.750 align:start position:0% um problems okay<00:45:46.560> and<00:45:46.800> the<00:45:46.920> key<00:45:47.040> thing<00:45:47.160> again<00:45:47.339> is<00:45:47.520> you<00:45:47.640> can 00:45:47.750 --> 00:45:47.760 align:start position:0% okay and the key thing again is you can 00:45:47.760 --> 00:45:49.309 align:start position:0% okay and the key thing again is you can modulize<00:45:48.119> your<00:45:48.240> code<00:45:48.420> further<00:45:48.720> we<00:45:48.900> will<00:45:49.200> see 00:45:49.309 --> 00:45:49.319 align:start position:0% modulize your code further we will see 00:45:49.319 --> 00:45:50.870 align:start position:0% modulize your code further we will see this<00:45:49.500> later<00:45:49.680> on<00:45:49.859> we<00:45:50.099> will<00:45:50.220> you<00:45:50.579> know<00:45:50.700> we<00:45:50.760> will 00:45:50.870 --> 00:45:50.880 align:start position:0% this later on we will you know we will 00:45:50.880 --> 00:45:52.130 align:start position:0% this later on we will you know we will have<00:45:51.000> regular<00:45:51.240> High<00:45:51.420> School<00:45:51.660> functions<00:45:52.020> that 00:45:52.130 --> 00:45:52.140 align:start position:0% have regular High School functions that 00:45:52.140 --> 00:45:53.750 align:start position:0% have regular High School functions that we<00:45:52.260> just<00:45:52.440> lived<00:45:52.740> into<00:45:52.859> that<00:45:53.099> and<00:45:53.520> you<00:45:53.640> can 00:45:53.750 --> 00:45:53.760 align:start position:0% we just lived into that and you can 00:45:53.760 --> 00:45:55.730 align:start position:0% we just lived into that and you can change<00:45:53.880> these<00:45:54.240> components<00:45:54.720> but<00:45:55.319> as<00:45:55.500> long<00:45:55.619> as 00:45:55.730 --> 00:45:55.740 align:start position:0% change these components but as long as 00:45:55.740 --> 00:45:57.470 align:start position:0% change these components but as long as you're<00:45:55.920> staying<00:45:56.220> inside<00:45:56.339> of<00:45:56.579> that<00:45:56.700> system<00:45:56.940> you 00:45:57.470 --> 00:45:57.480 align:start position:0% you're staying inside of that system you 00:45:57.480 --> 00:45:59.690 align:start position:0% you're staying inside of that system you are<00:45:57.599> guaranteed<00:45:57.960> that<00:45:58.140> these<00:45:58.500> things<00:45:58.619> make 00:45:59.690 --> 00:45:59.700 align:start position:0% are guaranteed that these things make 00:45:59.700 --> 00:46:02.210 align:start position:0% are guaranteed that these things make um are<00:46:00.060> kind<00:46:00.359> of<00:46:00.480> well-defined 00:46:02.210 --> 00:46:02.220 align:start position:0% um are kind of well-defined 00:46:02.220 --> 00:46:04.790 align:start position:0% um are kind of well-defined no<00:46:02.819> warning<00:46:03.300> uh<00:46:03.780> the<00:46:03.900> fact<00:46:04.079> that<00:46:04.200> is<00:46:04.380> uh<00:46:04.560> this 00:46:04.790 --> 00:46:04.800 align:start position:0% no warning uh the fact that is uh this 00:46:04.800 --> 00:46:06.890 align:start position:0% no warning uh the fact that is uh this is<00:46:04.920> game<00:46:05.040> 3D<00:46:05.460> well<00:46:05.700> designed<00:46:06.119> well<00:46:06.420> well 00:46:06.890 --> 00:46:06.900 align:start position:0% is game 3D well designed well well 00:46:06.900 --> 00:46:08.510 align:start position:0% is game 3D well designed well well defined<00:46:07.260> does<00:46:07.680> of<00:46:07.859> course<00:46:08.040> not<00:46:08.160> mean<00:46:08.339> that 00:46:08.510 --> 00:46:08.520 align:start position:0% defined does of course not mean that 00:46:08.520 --> 00:46:10.250 align:start position:0% defined does of course not mean that your<00:46:08.640> model<00:46:08.819> makes<00:46:09.060> sense<00:46:09.240> you<00:46:09.599> can<00:46:09.780> come<00:46:09.960> you 00:46:10.250 --> 00:46:10.260 align:start position:0% your model makes sense you can come you 00:46:10.260 --> 00:46:12.230 align:start position:0% your model makes sense you can come you know<00:46:10.319> you<00:46:10.740> can<00:46:10.800> model<00:46:10.920> complete<00:46:11.400> garbage 00:46:12.230 --> 00:46:12.240 align:start position:0% know you can model complete garbage 00:46:12.240 --> 00:46:13.609 align:start position:0% know you can model complete garbage um<00:46:12.300> we<00:46:12.480> can't<00:46:12.599> help<00:46:12.780> you<00:46:12.900> with<00:46:13.020> that<00:46:13.200> if<00:46:13.440> you're 00:46:13.609 --> 00:46:13.619 align:start position:0% um we can't help you with that if you're 00:46:13.619 --> 00:46:15.710 align:start position:0% um we can't help you with that if you're you<00:46:13.859> know<00:46:13.980> really<00:46:14.339> intended<00:46:14.760> to<00:46:14.819> do<00:46:14.940> that<00:46:15.119> but 00:46:15.710 --> 00:46:15.720 align:start position:0% you know really intended to do that but 00:46:15.720 --> 00:46:17.450 align:start position:0% you know really intended to do that but what<00:46:15.960> we<00:46:16.020> can<00:46:16.200> guarantee<00:46:16.500> to<00:46:16.680> you<00:46:16.800> is<00:46:16.980> or<00:46:17.160> what 00:46:17.450 --> 00:46:17.460 align:start position:0% what we can guarantee to you is or what 00:46:17.460 --> 00:46:20.210 align:start position:0% what we can guarantee to you is or what this<00:46:17.760> kind<00:46:17.940> of<00:46:18.060> helps<00:46:18.300> you<00:46:18.420> is<00:46:18.599> at<00:46:19.440> least<00:46:19.560> in 00:46:20.210 --> 00:46:20.220 align:start position:0% this kind of helps you is at least in 00:46:20.220 --> 00:46:21.650 align:start position:0% this kind of helps you is at least in the<00:46:20.339> process<00:46:20.579> of<00:46:20.760> modeling<00:46:21.180> we<00:46:21.420> have<00:46:21.599> a 00:46:21.650 --> 00:46:21.660 align:start position:0% the process of modeling we have a 00:46:21.660 --> 00:46:25.430 align:start position:0% the process of modeling we have a scaffold<00:46:22.020> that<00:46:22.260> you<00:46:22.380> can<00:46:22.440> use 00:46:25.430 --> 00:46:25.440 align:start position:0% 00:46:25.440 --> 00:46:28.309 align:start position:0% all<00:46:25.800> right<00:46:25.920> so<00:46:26.400> how<00:46:26.579> is<00:46:26.700> this<00:46:26.880> useful 00:46:28.309 --> 00:46:28.319 align:start position:0% all right so how is this useful 00:46:28.319 --> 00:46:29.150 align:start position:0% all right so how is this useful um 00:46:29.150 --> 00:46:29.160 align:start position:0% um 00:46:29.160 --> 00:46:31.490 align:start position:0% um the<00:46:29.760> main<00:46:29.819> thing<00:46:30.000> basically<00:46:30.420> is<00:46:30.660> I<00:46:31.079> alluded<00:46:31.440> to 00:46:31.490 --> 00:46:31.500 align:start position:0% the main thing basically is I alluded to 00:46:31.500 --> 00:46:32.690 align:start position:0% the main thing basically is I alluded to that<00:46:31.680> if<00:46:31.859> you<00:46:31.980> have<00:46:32.099> you<00:46:32.280> know<00:46:32.400> if<00:46:32.460> you<00:46:32.579> can 00:46:32.690 --> 00:46:32.700 align:start position:0% that if you have you know if you can 00:46:32.700 --> 00:46:34.550 align:start position:0% that if you have you know if you can apply<00:46:32.940> divide<00:46:33.180> and<00:46:33.359> conquer<00:46:33.660> you<00:46:34.140> can<00:46:34.200> easily 00:46:34.550 --> 00:46:34.560 align:start position:0% apply divide and conquer you can easily 00:46:34.560 --> 00:46:37.490 align:start position:0% apply divide and conquer you can easily deal<00:46:34.740> with<00:46:34.920> complex<00:46:35.220> scenarios 00:46:37.490 --> 00:46:37.500 align:start position:0% deal with complex scenarios 00:46:37.500 --> 00:46:39.530 align:start position:0% deal with complex scenarios um<00:46:37.560> it<00:46:37.859> overall<00:46:38.220> also<00:46:38.579> speeds<00:46:39.000> up<00:46:39.119> the<00:46:39.240> process 00:46:39.530 --> 00:46:39.540 align:start position:0% um it overall also speeds up the process 00:46:39.540 --> 00:46:42.829 align:start position:0% um it overall also speeds up the process of<00:46:39.720> modeling<00:46:40.560> in<00:46:41.040> several<00:46:41.339> ways<00:46:41.700> first<00:46:41.940> you 00:46:42.829 --> 00:46:42.839 align:start position:0% of modeling in several ways first you 00:46:42.839 --> 00:46:44.569 align:start position:0% of modeling in several ways first you know<00:46:42.960> division<00:46:43.500> of<00:46:43.680> labor<00:46:43.920> so<00:46:44.099> in<00:46:44.280> principle 00:46:44.569 --> 00:46:44.579 align:start position:0% know division of labor so in principle 00:46:44.579 --> 00:46:46.069 align:start position:0% know division of labor so in principle the<00:46:44.819> larger<00:46:45.060> the<00:46:45.240> systems<00:46:45.599> you<00:46:45.720> can<00:46:45.900> actually 00:46:46.069 --> 00:46:46.079 align:start position:0% the larger the systems you can actually 00:46:46.079 --> 00:46:48.650 align:start position:0% the larger the systems you can actually very<00:46:46.440> easily<00:46:46.680> collaborate<00:46:47.099> with<00:46:47.280> people 00:46:48.650 --> 00:46:48.660 align:start position:0% very easily collaborate with people 00:46:48.660 --> 00:46:50.450 align:start position:0% very easily collaborate with people um<00:46:48.720> secondly<00:46:49.140> if<00:46:49.740> you<00:46:49.800> want<00:46:49.980> to<00:46:50.099> change<00:46:50.220> a 00:46:50.450 --> 00:46:50.460 align:start position:0% um secondly if you want to change a 00:46:50.460 --> 00:46:52.130 align:start position:0% um secondly if you want to change a component<00:46:50.819> you<00:46:51.000> can<00:46:51.119> easily<00:46:51.359> do<00:46:51.540> that<00:46:51.660> as<00:46:52.020> long 00:46:52.130 --> 00:46:52.140 align:start position:0% component you can easily do that as long 00:46:52.140 --> 00:46:54.530 align:start position:0% component you can easily do that as long as<00:46:52.260> the<00:46:52.380> rest<00:46:52.500> stays<00:46:52.920> intact<00:46:53.180> and<00:46:54.180> lastly 00:46:54.530 --> 00:46:54.540 align:start position:0% as the rest stays intact and lastly 00:46:54.540 --> 00:46:56.089 align:start position:0% as the rest stays intact and lastly because<00:46:54.780> everything<00:46:55.079> is<00:46:55.319> expressed<00:46:55.680> as<00:46:55.859> code 00:46:56.089 --> 00:46:56.099 align:start position:0% because everything is expressed as code 00:46:56.099 --> 00:46:58.430 align:start position:0% because everything is expressed as code there<00:46:56.640> is<00:46:56.819> obvious<00:46:57.119> reuse<00:46:57.660> for<00:46:57.900> components 00:46:58.430 --> 00:46:58.440 align:start position:0% there is obvious reuse for components 00:46:58.440 --> 00:47:00.109 align:start position:0% there is obvious reuse for components and<00:46:58.800> you<00:46:59.099> know<00:46:59.160> we<00:46:59.280> have<00:46:59.460> been<00:46:59.579> said<00:46:59.760> we<00:46:59.940> have 00:47:00.109 --> 00:47:00.119 align:start position:0% and you know we have been said we have 00:47:00.119 --> 00:47:01.910 align:start position:0% and you know we have been said we have had<00:47:00.300> several<00:47:00.839> projects<00:47:01.200> in<00:47:01.319> the<00:47:01.440> past<00:47:01.560> and<00:47:01.800> we 00:47:01.910 --> 00:47:01.920 align:start position:0% had several projects in the past and we 00:47:01.920 --> 00:47:03.349 align:start position:0% had several projects in the past and we can<00:47:02.040> see<00:47:02.160> that<00:47:02.339> there<00:47:02.819> are<00:47:02.940> some<00:47:03.060> patterns 00:47:03.349 --> 00:47:03.359 align:start position:0% can see that there are some patterns 00:47:03.359 --> 00:47:04.670 align:start position:0% can see that there are some patterns that<00:47:03.480> just<00:47:03.660> emerge<00:47:04.020> that<00:47:04.140> you<00:47:04.200> can<00:47:04.319> use<00:47:04.440> over 00:47:04.670 --> 00:47:04.680 align:start position:0% that just emerge that you can use over 00:47:04.680 --> 00:47:06.829 align:start position:0% that just emerge that you can use over and<00:47:04.800> over<00:47:04.980> again<00:47:05.160> which<00:47:05.700> is<00:47:05.880> useful<00:47:06.599> because 00:47:06.829 --> 00:47:06.839 align:start position:0% and over again which is useful because 00:47:06.839 --> 00:47:08.510 align:start position:0% and over again which is useful because it<00:47:07.140> speeds<00:47:07.440> up 00:47:08.510 --> 00:47:08.520 align:start position:0% it speeds up 00:47:08.520 --> 00:47:10.609 align:start position:0% it speeds up um<00:47:08.579> down<00:47:08.760> the<00:47:08.940> road<00:47:09.060> how<00:47:09.960> um<00:47:09.960> you<00:47:10.200> know<00:47:10.319> and<00:47:10.440> you 00:47:10.609 --> 00:47:10.619 align:start position:0% um down the road how um you know and you 00:47:10.619 --> 00:47:12.609 align:start position:0% um down the road how um you know and you want<00:47:10.740> to<00:47:10.800> model<00:47:10.920> something 00:47:12.609 --> 00:47:12.619 align:start position:0% want to model something 00:47:12.619 --> 00:47:16.210 align:start position:0% want to model something foreign 00:47:16.210 --> 00:47:16.220 align:start position:0% 00:47:16.220 --> 00:47:18.170 align:start position:0% you<00:47:17.220> can<00:47:17.280> also<00:47:17.460> think<00:47:17.579> about<00:47:17.700> it<00:47:17.880> as<00:47:18.060> just 00:47:18.170 --> 00:47:18.180 align:start position:0% you can also think about it as just 00:47:18.180 --> 00:47:20.750 align:start position:0% you can also think about it as just being<00:47:18.420> part<00:47:18.660> of<00:47:18.780> a<00:47:18.900> larger<00:47:19.140> stack<00:47:19.500> where 00:47:20.750 --> 00:47:20.760 align:start position:0% being part of a larger stack where 00:47:20.760 --> 00:47:22.190 align:start position:0% being part of a larger stack where um it's<00:47:21.000> just<00:47:21.119> feeling<00:47:21.300> a<00:47:21.599> proper<00:47:21.900> it's 00:47:22.190 --> 00:47:22.200 align:start position:0% um it's just feeling a proper it's 00:47:22.200 --> 00:47:24.170 align:start position:0% um it's just feeling a proper it's fulfilling<00:47:22.680> a<00:47:22.800> certain<00:47:23.220> um<00:47:23.220> service 00:47:24.170 --> 00:47:24.180 align:start position:0% fulfilling a certain um service 00:47:24.180 --> 00:47:26.150 align:start position:0% fulfilling a certain um service um<00:47:24.240> like<00:47:24.480> testing<00:47:24.839> properties<00:47:25.200> again<00:47:25.500> on<00:47:25.980> your 00:47:26.150 --> 00:47:26.160 align:start position:0% um like testing properties again on your 00:47:26.160 --> 00:47:27.710 align:start position:0% um like testing properties again on your on<00:47:26.460> the<00:47:26.640> safeness<00:47:27.000> of<00:47:27.119> the<00:47:27.180> system<00:47:27.300> from<00:47:27.599> an 00:47:27.710 --> 00:47:27.720 align:start position:0% on the safeness of the system from an 00:47:27.720 --> 00:47:30.589 align:start position:0% on the safeness of the system from an economic<00:47:28.079> perspective 00:47:30.589 --> 00:47:30.599 align:start position:0% 00:47:30.599 --> 00:47:32.630 align:start position:0% okay<00:47:31.079> this<00:47:31.740> is<00:47:31.859> kind<00:47:31.980> of<00:47:32.099> the<00:47:32.220> introduction 00:47:32.630 --> 00:47:32.640 align:start position:0% okay this is kind of the introduction 00:47:32.640 --> 00:47:34.190 align:start position:0% okay this is kind of the introduction very<00:47:32.940> roughly<00:47:33.300> what<00:47:33.480> this<00:47:33.599> engine<00:47:33.780> is<00:47:33.960> doing 00:47:34.190 --> 00:47:34.200 align:start position:0% very roughly what this engine is doing 00:47:34.200 --> 00:47:35.930 align:start position:0% very roughly what this engine is doing why<00:47:34.560> it's<00:47:34.740> possibly<00:47:35.040> useful<00:47:35.339> why<00:47:35.579> it's<00:47:35.760> maybe 00:47:35.930 --> 00:47:35.940 align:start position:0% why it's possibly useful why it's maybe 00:47:35.940 --> 00:47:37.730 align:start position:0% why it's possibly useful why it's maybe interesting<00:47:36.420> what<00:47:36.960> I<00:47:37.140> want<00:47:37.200> to<00:47:37.319> do<00:47:37.440> for<00:47:37.560> the 00:47:37.730 --> 00:47:37.740 align:start position:0% interesting what I want to do for the 00:47:37.740 --> 00:47:39.470 align:start position:0% interesting what I want to do for the rest<00:47:37.859> of<00:47:38.400> this<00:47:38.520> Workshop 00:47:39.470 --> 00:47:39.480 align:start position:0% rest of this Workshop 00:47:39.480 --> 00:47:41.569 align:start position:0% rest of this Workshop um<00:47:39.540> and<00:47:39.660> for<00:47:39.839> basically<00:47:40.200> the<00:47:40.380> second<00:47:40.560> part<00:47:40.800> I 00:47:41.569 --> 00:47:41.579 align:start position:0% um and for basically the second part I 00:47:41.579 --> 00:47:42.950 align:start position:0% um and for basically the second part I will<00:47:41.700> give<00:47:41.819> you<00:47:41.880> an<00:47:42.060> intuition<00:47:42.359> about<00:47:42.540> how<00:47:42.839> to 00:47:42.950 --> 00:47:42.960 align:start position:0% will give you an intuition about how to 00:47:42.960 --> 00:47:45.290 align:start position:0% will give you an intuition about how to model<00:47:43.140> with<00:47:43.500> this<00:47:43.680> tool<00:47:44.040> how<00:47:44.760> to<00:47:44.940> represent 00:47:45.290 --> 00:47:45.300 align:start position:0% model with this tool how to represent 00:47:45.300 --> 00:47:47.210 align:start position:0% model with this tool how to represent games<00:47:45.480> and<00:47:45.900> again<00:47:46.020> the<00:47:46.319> focus<00:47:46.619> will<00:47:46.800> be<00:47:46.980> on 00:47:47.210 --> 00:47:47.220 align:start position:0% games and again the focus will be on 00:47:47.220 --> 00:47:48.890 align:start position:0% games and again the focus will be on showing<00:47:47.760> that<00:47:47.940> compositionality<00:47:48.660> is 00:47:48.890 --> 00:47:48.900 align:start position:0% showing that compositionality is 00:47:48.900 --> 00:47:51.470 align:start position:0% showing that compositionality is actually<00:47:49.079> useful<00:47:49.440> or<00:47:49.740> hopefully<00:47:50.099> useful 00:47:51.470 --> 00:47:51.480 align:start position:0% actually useful or hopefully useful 00:47:51.480 --> 00:47:53.990 align:start position:0% actually useful or hopefully useful um<00:47:51.619> secondly<00:47:52.619> I<00:47:52.859> will<00:47:53.040> also<00:47:53.280> give<00:47:53.640> you<00:47:53.760> an 00:47:53.990 --> 00:47:54.000 align:start position:0% um secondly I will also give you an 00:47:54.000 --> 00:47:55.190 align:start position:0% um secondly I will also give you an intuition<00:47:54.359> of<00:47:54.480> you<00:47:54.599> know<00:47:54.720> how<00:47:54.900> does<00:47:55.079> an 00:47:55.190 --> 00:47:55.200 align:start position:0% intuition of you know how does an 00:47:55.200 --> 00:47:56.690 align:start position:0% intuition of you know how does an analysis<00:47:55.560> actually<00:47:55.800> work<00:47:55.980> what<00:47:56.280> does<00:47:56.460> it<00:47:56.579> look 00:47:56.690 --> 00:47:56.700 align:start position:0% analysis actually work what does it look 00:47:56.700 --> 00:47:57.470 align:start position:0% analysis actually work what does it look like 00:47:57.470 --> 00:47:57.480 align:start position:0% like 00:47:57.480 --> 00:47:59.270 align:start position:0% like I<00:47:58.020> will<00:47:58.200> be<00:47:58.319> shorter<00:47:58.560> on<00:47:58.680> that<00:47:58.859> second<00:47:59.040> part 00:47:59.270 --> 00:47:59.280 align:start position:0% I will be shorter on that second part 00:47:59.280 --> 00:48:01.370 align:start position:0% I will be shorter on that second part the<00:47:59.700> reason<00:47:59.819> is<00:48:00.060> in<00:48:00.660> order<00:48:00.780> to<00:48:00.960> make<00:48:01.079> sense<00:48:01.200> of 00:48:01.370 --> 00:48:01.380 align:start position:0% the reason is in order to make sense of 00:48:01.380 --> 00:48:03.050 align:start position:0% the reason is in order to make sense of the<00:48:01.500> analysis<00:48:01.920> you<00:48:02.099> obviously<00:48:02.520> have<00:48:02.700> to<00:48:02.819> have 00:48:03.050 --> 00:48:03.060 align:start position:0% the analysis you obviously have to have 00:48:03.060 --> 00:48:05.089 align:start position:0% the analysis you obviously have to have a<00:48:03.420> deep<00:48:03.540> understanding<00:48:03.960> of<00:48:04.079> the<00:48:04.200> model 00:48:05.089 --> 00:48:05.099 align:start position:0% a deep understanding of the model 00:48:05.099 --> 00:48:06.170 align:start position:0% a deep understanding of the model um<00:48:05.160> this<00:48:05.339> is<00:48:05.400> given<00:48:05.640> the<00:48:05.700> type<00:48:05.819> constraints 00:48:06.170 --> 00:48:06.180 align:start position:0% um this is given the type constraints 00:48:06.180 --> 00:48:07.609 align:start position:0% um this is given the type constraints not<00:48:06.359> really<00:48:06.480> feasible<00:48:06.780> but<00:48:07.079> I<00:48:07.260> still<00:48:07.440> will 00:48:07.609 --> 00:48:07.619 align:start position:0% not really feasible but I still will 00:48:07.619 --> 00:48:09.109 align:start position:0% not really feasible but I still will give<00:48:07.800> you<00:48:07.859> an<00:48:07.980> intuition<00:48:08.280> of<00:48:08.460> how<00:48:08.880> does<00:48:09.000> it 00:48:09.109 --> 00:48:09.119 align:start position:0% give you an intuition of how does it 00:48:09.119 --> 00:48:12.050 align:start position:0% give you an intuition of how does it actually<00:48:09.240> work<00:48:09.420> how<00:48:09.599> does<00:48:09.720> this<00:48:09.839> look<00:48:10.020> like 00:48:12.050 --> 00:48:12.060 align:start position:0% actually work how does this look like 00:48:12.060 --> 00:48:14.930 align:start position:0% actually work how does this look like okay<00:48:13.020> and<00:48:13.319> a<00:48:13.500> leading<00:48:13.740> example 00:48:14.930 --> 00:48:14.940 align:start position:0% okay and a leading example 00:48:14.940 --> 00:48:16.790 align:start position:0% okay and a leading example um<00:48:15.000> that<00:48:15.180> we<00:48:15.359> will<00:48:15.480> converge<00:48:16.200> to<00:48:16.380> is<00:48:16.560> basically 00:48:16.790 --> 00:48:16.800 align:start position:0% um that we will converge to is basically 00:48:16.800 --> 00:48:18.530 align:start position:0% um that we will converge to is basically a<00:48:16.980> staking<00:48:17.220> protocol<00:48:17.520> it's<00:48:17.819> a<00:48:18.000> simplified 00:48:18.530 --> 00:48:18.540 align:start position:0% a staking protocol it's a simplified 00:48:18.540 --> 00:48:20.690 align:start position:0% a staking protocol it's a simplified model<00:48:18.900> that<00:48:19.560> illustrates 00:48:20.690 --> 00:48:20.700 align:start position:0% model that illustrates 00:48:20.700 --> 00:48:21.650 align:start position:0% model that illustrates um these<00:48:21.119> two<00:48:21.180> components<00:48:21.599> of 00:48:21.650 --> 00:48:21.660 align:start position:0% um these two components of 00:48:21.660 --> 00:48:23.270 align:start position:0% um these two components of compositionality<00:48:22.319> and<00:48:22.500> also<00:48:22.740> the<00:48:22.980> kind<00:48:23.160> of 00:48:23.270 --> 00:48:23.280 align:start position:0% compositionality and also the kind of 00:48:23.280 --> 00:48:25.130 align:start position:0% compositionality and also the kind of analysis<00:48:23.700> you<00:48:23.819> want<00:48:23.940> to<00:48:24.060> run<00:48:24.180> in<00:48:24.359> this<00:48:24.540> in<00:48:24.839> this 00:48:25.130 --> 00:48:25.140 align:start position:0% analysis you want to run in this in this 00:48:25.140 --> 00:48:27.829 align:start position:0% analysis you want to run in this in this system 00:48:27.829 --> 00:48:27.839 align:start position:0% 00:48:27.839 --> 00:48:31.730 align:start position:0% good<00:48:28.440> I<00:48:29.220> start<00:48:29.460> with<00:48:29.700> not<00:48:30.240> code<00:48:30.540> but<00:48:30.780> directly 00:48:31.730 --> 00:48:31.740 align:start position:0% good I start with not code but directly 00:48:31.740 --> 00:48:33.290 align:start position:0% good I start with not code but directly coming<00:48:32.220> back<00:48:32.400> to<00:48:32.520> what<00:48:32.640> for<00:48:32.880> pizza<00:48:33.060> actually 00:48:33.290 --> 00:48:33.300 align:start position:0% coming back to what for pizza actually 00:48:33.300 --> 00:48:36.109 align:start position:0% coming back to what for pizza actually namely<00:48:34.260> um<00:48:34.260> introducing<00:48:34.740> a<00:48:34.920> bit<00:48:35.099> Theory<00:48:35.700> this 00:48:36.109 --> 00:48:36.119 align:start position:0% namely um introducing a bit Theory this 00:48:36.119 --> 00:48:37.790 align:start position:0% namely um introducing a bit Theory this will<00:48:36.240> be<00:48:36.359> partly<00:48:36.599> repetition<00:48:37.020> but<00:48:37.560> it<00:48:37.680> doesn't 00:48:37.790 --> 00:48:37.800 align:start position:0% will be partly repetition but it doesn't 00:48:37.800 --> 00:48:39.470 align:start position:0% will be partly repetition but it doesn't hurt<00:48:38.040> it<00:48:38.339> will<00:48:38.460> be<00:48:38.520> mostly<00:48:38.760> about<00:48:38.880> diagrams<00:48:39.359> so 00:48:39.470 --> 00:48:39.480 align:start position:0% hurt it will be mostly about diagrams so 00:48:39.480 --> 00:48:41.630 align:start position:0% hurt it will be mostly about diagrams so not<00:48:39.660> much<00:48:39.780> mathematical<00:48:40.319> content<00:48:40.740> the<00:48:41.579> reason 00:48:41.630 --> 00:48:41.640 align:start position:0% not much mathematical content the reason 00:48:41.640 --> 00:48:45.290 align:start position:0% not much mathematical content the reason I<00:48:41.880> do<00:48:42.060> this<00:48:42.240> is<00:48:42.780> the<00:48:43.680> theoretical<00:48:44.640> approach<00:48:45.000> is 00:48:45.290 --> 00:48:45.300 align:start position:0% I do this is the theoretical approach is 00:48:45.300 --> 00:48:46.490 align:start position:0% I do this is the theoretical approach is more<00:48:45.480> or<00:48:45.599> less<00:48:45.660> directly<00:48:46.020> the<00:48:46.200> way<00:48:46.319> that 00:48:46.490 --> 00:48:46.500 align:start position:0% more or less directly the way that 00:48:46.500 --> 00:48:48.650 align:start position:0% more or less directly the way that implementation<00:48:47.040> works<00:48:47.520> model<00:48:47.940> is<00:48:48.240> some<00:48:48.540> kind 00:48:48.650 --> 00:48:48.660 align:start position:0% implementation works model is some kind 00:48:48.660 --> 00:48:50.990 align:start position:0% implementation works model is some kind of<00:48:48.780> difficulties<00:48:49.200> in<00:48:49.380> the<00:48:49.500> back<00:48:49.619> obviously<00:48:50.160> if 00:48:50.990 --> 00:48:51.000 align:start position:0% of difficulties in the back obviously if 00:48:51.000 --> 00:48:52.490 align:start position:0% of difficulties in the back obviously if you<00:48:51.119> understand<00:48:51.359> how<00:48:51.720> the<00:48:51.900> modeling<00:48:52.200> on<00:48:52.380> the 00:48:52.490 --> 00:48:52.500 align:start position:0% you understand how the modeling on the 00:48:52.500 --> 00:48:53.990 align:start position:0% you understand how the modeling on the theoretical<00:48:52.859> side<00:48:53.040> works<00:48:53.460> you<00:48:53.700> basically 00:48:53.990 --> 00:48:54.000 align:start position:0% theoretical side works you basically 00:48:54.000 --> 00:48:56.030 align:start position:0% theoretical side works you basically have<00:48:54.240> a<00:48:54.420> very<00:48:54.540> good<00:48:54.780> idea<00:48:55.079> of<00:48:55.319> how<00:48:55.680> then<00:48:55.859> the 00:48:56.030 --> 00:48:56.040 align:start position:0% have a very good idea of how then the 00:48:56.040 --> 00:48:57.710 align:start position:0% have a very good idea of how then the syntax<00:48:56.339> actually<00:48:56.640> works<00:48:56.940> and<00:48:57.060> operates<00:48:57.420> and 00:48:57.710 --> 00:48:57.720 align:start position:0% syntax actually works and operates and 00:48:57.720 --> 00:48:58.970 align:start position:0% syntax actually works and operates and that<00:48:57.780> means<00:48:57.960> you<00:48:58.140> also<00:48:58.380> basically<00:48:58.619> know<00:48:58.800> how 00:48:58.970 --> 00:48:58.980 align:start position:0% that means you also basically know how 00:48:58.980 --> 00:49:01.010 align:start position:0% that means you also basically know how to<00:48:59.160> use<00:48:59.760> that<00:49:00.000> that 00:49:01.010 --> 00:49:01.020 align:start position:0% to use that that 00:49:01.020 --> 00:49:01.849 align:start position:0% to use that that um 00:49:01.849 --> 00:49:01.859 align:start position:0% um 00:49:01.859 --> 00:49:05.329 align:start position:0% um that<00:49:02.339> engine<00:49:02.520> basically 00:49:05.329 --> 00:49:05.339 align:start position:0% 00:49:05.339 --> 00:49:07.309 align:start position:0% okay<00:49:05.940> so<00:49:06.359> you've<00:49:06.540> seen<00:49:06.720> this<00:49:06.839> this<00:49:07.079> is<00:49:07.200> a 00:49:07.309 --> 00:49:07.319 align:start position:0% okay so you've seen this this is a 00:49:07.319 --> 00:49:08.030 align:start position:0% okay so you've seen this this is a bi-directional<00:49:07.859> information 00:49:08.030 --> 00:49:08.040 align:start position:0% bi-directional information 00:49:08.040 --> 00:49:10.849 align:start position:0% bi-directional information transformation<00:49:08.720> Transformer<00:49:09.720> from<00:49:10.140> both 00:49:10.849 --> 00:49:10.859 align:start position:0% transformation Transformer from both 00:49:10.859 --> 00:49:13.730 align:start position:0% transformation Transformer from both sides<00:49:11.220> so<00:49:11.400> X<00:49:11.760> is<00:49:12.180> transformed<00:49:12.660> into<00:49:12.780> Y<00:49:13.079> and 00:49:13.730 --> 00:49:13.740 align:start position:0% sides so X is transformed into Y and 00:49:13.740 --> 00:49:15.050 align:start position:0% sides so X is transformed into Y and then<00:49:13.800> there's<00:49:13.980> something<00:49:14.220> coming<00:49:14.400> from<00:49:14.579> R<00:49:14.819> to 00:49:15.050 --> 00:49:15.060 align:start position:0% then there's something coming from R to 00:49:15.060 --> 00:49:18.290 align:start position:0% then there's something coming from R to S<00:49:15.240> both<00:49:16.200> directions<00:49:16.500> again<00:49:17.400> convention<00:49:17.880> is<00:49:18.060> if 00:49:18.290 --> 00:49:18.300 align:start position:0% S both directions again convention is if 00:49:18.300 --> 00:49:19.790 align:start position:0% S both directions again convention is if you<00:49:18.359> want<00:49:18.599> to<00:49:18.720> think<00:49:18.900> about<00:49:19.020> this<00:49:19.260> is<00:49:19.500> that 00:49:19.790 --> 00:49:19.800 align:start position:0% you want to think about this is that 00:49:19.800 --> 00:49:21.650 align:start position:0% you want to think about this is that time<00:49:20.040> is<00:49:20.220> from<00:49:20.400> time<00:49:20.700> is<00:49:20.880> on<00:49:21.060> the<00:49:21.119> left<00:49:21.240> so<00:49:21.480> on 00:49:21.650 --> 00:49:21.660 align:start position:0% time is from time is on the left so on 00:49:21.660 --> 00:49:23.750 align:start position:0% time is from time is on the left so on the<00:49:21.780> side<00:49:21.900> of<00:49:21.960> X<00:49:22.140> and<00:49:22.380> S<00:49:22.560> and<00:49:23.220> the<00:49:23.339> future<00:49:23.460> is 00:49:23.750 --> 00:49:23.760 align:start position:0% the side of X and S and the future is 00:49:23.760 --> 00:49:25.609 align:start position:0% the side of X and S and the future is basically<00:49:24.119> the<00:49:24.540> passes<00:49:24.960> on<00:49:25.079> the<00:49:25.200> X<00:49:25.260> side<00:49:25.440> and 00:49:25.609 --> 00:49:25.619 align:start position:0% basically the passes on the X side and 00:49:25.619 --> 00:49:27.589 align:start position:0% basically the passes on the X side and the<00:49:25.740> future<00:49:25.800> is<00:49:26.040> on<00:49:26.160> the<00:49:26.280> Y<00:49:26.400> side 00:49:27.589 --> 00:49:27.599 align:start position:0% the future is on the Y side 00:49:27.599 --> 00:49:30.530 align:start position:0% the future is on the Y side okay<00:49:28.079> now<00:49:28.560> in<00:49:29.280> some<00:49:29.400> sense<00:49:29.579> in<00:49:29.819> the<00:49:30.000> essence<00:49:30.359> of 00:49:30.530 --> 00:49:30.540 align:start position:0% okay now in some sense in the essence of 00:49:30.540 --> 00:49:32.690 align:start position:0% okay now in some sense in the essence of compositional<00:49:31.140> game<00:49:31.319> theory<00:49:31.619> is<00:49:31.740> that<00:49:32.040> what 00:49:32.690 --> 00:49:32.700 align:start position:0% compositional game theory is that what 00:49:32.700 --> 00:49:34.910 align:start position:0% compositional game theory is that what we<00:49:32.819> showed<00:49:33.119> is<00:49:33.359> any<00:49:34.079> kind<00:49:34.260> of<00:49:34.380> game<00:49:34.560> that<00:49:34.800> you 00:49:34.910 --> 00:49:34.920 align:start position:0% we showed is any kind of game that you 00:49:34.920 --> 00:49:36.950 align:start position:0% we showed is any kind of game that you want<00:49:35.040> to<00:49:35.099> model<00:49:35.280> has<00:49:36.000> this<00:49:36.240> shape<00:49:36.420> and<00:49:36.660> can<00:49:36.839> be 00:49:36.950 --> 00:49:36.960 align:start position:0% want to model has this shape and can be 00:49:36.960 --> 00:49:39.589 align:start position:0% want to model has this shape and can be put<00:49:37.079> into<00:49:37.319> this<00:49:37.560> shape<00:49:37.859> whether<00:49:38.400> it's<00:49:38.640> just<00:49:38.940> a 00:49:39.589 --> 00:49:39.599 align:start position:0% put into this shape whether it's just a 00:49:39.599 --> 00:49:41.150 align:start position:0% put into this shape whether it's just a single<00:49:39.839> player<00:49:40.140> making<00:49:40.260> a<00:49:40.500> decision<00:49:40.800> which<00:49:41.040> is 00:49:41.150 --> 00:49:41.160 align:start position:0% single player making a decision which is 00:49:41.160 --> 00:49:44.329 align:start position:0% single player making a decision which is kind<00:49:41.339> of<00:49:41.460> a<00:49:41.640> non-typical<00:49:42.540> game<00:49:42.859> or<00:49:43.859> a<00:49:44.220> very 00:49:44.329 --> 00:49:44.339 align:start position:0% kind of a non-typical game or a very 00:49:44.339 --> 00:49:46.490 align:start position:0% kind of a non-typical game or a very large<00:49:44.520> complex<00:49:44.940> system<00:49:45.240> many<00:49:45.780> players<00:49:46.140> moving 00:49:46.490 --> 00:49:46.500 align:start position:0% large complex system many players moving 00:49:46.500 --> 00:49:48.470 align:start position:0% large complex system many players moving and<00:49:46.619> interacting<00:49:47.160> everything<00:49:48.000> can<00:49:48.359> be 00:49:48.470 --> 00:49:48.480 align:start position:0% and interacting everything can be 00:49:48.480 --> 00:49:50.329 align:start position:0% and interacting everything can be modeled<00:49:48.720> in<00:49:48.900> that<00:49:49.079> shape<00:49:49.380> whether<00:49:49.980> it's<00:49:50.160> very 00:49:50.329 --> 00:49:50.339 align:start position:0% modeled in that shape whether it's very 00:49:50.339 --> 00:49:52.609 align:start position:0% modeled in that shape whether it's very large<00:49:50.520> or<00:49:50.819> very<00:49:51.000> small 00:49:52.609 --> 00:49:52.619 align:start position:0% large or very small 00:49:52.619 --> 00:49:54.349 align:start position:0% large or very small now<00:49:53.099> why<00:49:53.339> is<00:49:53.460> this<00:49:53.579> good<00:49:53.760> or<00:49:54.000> why<00:49:54.180> is<00:49:54.300> this 00:49:54.349 --> 00:49:54.359 align:start position:0% now why is this good or why is this 00:49:54.359 --> 00:49:56.150 align:start position:0% now why is this good or why is this useful<00:49:54.720> well<00:49:55.140> it's<00:49:55.380> useful<00:49:55.680> because<00:49:55.800> you<00:49:56.040> can 00:49:56.150 --> 00:49:56.160 align:start position:0% useful well it's useful because you can 00:49:56.160 --> 00:49:58.609 align:start position:0% useful well it's useful because you can start<00:49:56.280> out<00:49:56.460> with<00:49:56.640> small<00:49:56.819> components<00:49:57.359> like<00:49:58.079> one 00:49:58.609 --> 00:49:58.619 align:start position:0% start out with small components like one 00:49:58.619 --> 00:50:00.589 align:start position:0% start out with small components like one player<00:49:59.040> maybe<00:49:59.579> just<00:49:59.819> also<00:50:00.180> computation 00:50:00.589 --> 00:50:00.599 align:start position:0% player maybe just also computation 00:50:00.599 --> 00:50:02.569 align:start position:0% player maybe just also computation something<00:50:00.839> very<00:50:01.140> trivial<00:50:01.500> and<00:50:02.220> you<00:50:02.400> can<00:50:02.460> plug 00:50:02.569 --> 00:50:02.579 align:start position:0% something very trivial and you can plug 00:50:02.579 --> 00:50:04.130 align:start position:0% something very trivial and you can plug these<00:50:02.880> things<00:50:02.940> together<00:50:03.180> and<00:50:03.540> slowly<00:50:03.900> from 00:50:04.130 --> 00:50:04.140 align:start position:0% these things together and slowly from 00:50:04.140 --> 00:50:05.930 align:start position:0% these things together and slowly from the<00:50:04.319> bottom<00:50:04.560> up<00:50:04.680> yeah<00:50:04.980> like<00:50:05.280> Lego<00:50:05.400> blocks<00:50:05.819> you 00:50:05.930 --> 00:50:05.940 align:start position:0% the bottom up yeah like Lego blocks you 00:50:05.940 --> 00:50:07.490 align:start position:0% the bottom up yeah like Lego blocks you can<00:50:06.060> build<00:50:06.180> up<00:50:06.359> a<00:50:06.540> system<00:50:06.660> that<00:50:07.200> is<00:50:07.319> quite 00:50:07.490 --> 00:50:07.500 align:start position:0% can build up a system that is quite 00:50:07.500 --> 00:50:09.410 align:start position:0% can build up a system that is quite quite<00:50:07.859> complex<00:50:08.160> and<00:50:09.000> of<00:50:09.060> course<00:50:09.180> because 00:50:09.410 --> 00:50:09.420 align:start position:0% quite complex and of course because 00:50:09.420 --> 00:50:11.089 align:start position:0% quite complex and of course because you're<00:50:09.720> programming<00:50:10.200> you<00:50:10.440> can<00:50:10.560> also<00:50:10.800> kind<00:50:10.920> of 00:50:11.089 --> 00:50:11.099 align:start position:0% you're programming you can also kind of 00:50:11.099 --> 00:50:13.130 align:start position:0% you're programming you can also kind of box<00:50:11.819> things<00:50:12.119> and<00:50:12.359> say<00:50:12.480> well<00:50:12.660> this<00:50:12.839> is<00:50:12.960> a 00:50:13.130 --> 00:50:13.140 align:start position:0% box things and say well this is a 00:50:13.140 --> 00:50:14.870 align:start position:0% box things and say well this is a pattern<00:50:13.380> maybe<00:50:13.619> two<00:50:13.859> players<00:50:14.160> interacting<00:50:14.700> in 00:50:14.870 --> 00:50:14.880 align:start position:0% pattern maybe two players interacting in 00:50:14.880 --> 00:50:16.730 align:start position:0% pattern maybe two players interacting in a<00:50:14.940> certain<00:50:15.060> way<00:50:15.240> this<00:50:15.480> is<00:50:15.599> quite<00:50:15.720> useful<00:50:16.079> you 00:50:16.730 --> 00:50:16.740 align:start position:0% a certain way this is quite useful you 00:50:16.740 --> 00:50:17.930 align:start position:0% a certain way this is quite useful you know<00:50:16.800> I'm<00:50:16.980> giving<00:50:17.160> that<00:50:17.339> a<00:50:17.520> name<00:50:17.640> and<00:50:17.760> I'm 00:50:17.930 --> 00:50:17.940 align:start position:0% know I'm giving that a name and I'm 00:50:17.940 --> 00:50:19.849 align:start position:0% know I'm giving that a name and I'm going<00:50:18.000> to<00:50:18.060> be<00:50:18.180> reusing<00:50:18.900> that<00:50:19.079> component<00:50:19.500> over 00:50:19.849 --> 00:50:19.859 align:start position:0% going to be reusing that component over 00:50:19.859 --> 00:50:21.770 align:start position:0% going to be reusing that component over again 00:50:21.770 --> 00:50:21.780 align:start position:0% again 00:50:21.780 --> 00:50:24.470 align:start position:0% again okay<00:50:22.380> so<00:50:23.160> everything<00:50:23.339> is<00:50:23.640> of<00:50:23.819> that<00:50:24.000> shape<00:50:24.180> you 00:50:24.470 --> 00:50:24.480 align:start position:0% okay so everything is of that shape you 00:50:24.480 --> 00:50:25.609 align:start position:0% okay so everything is of that shape you know<00:50:24.540> so<00:50:24.660> it's<00:50:24.780> a<00:50:24.900> bit<00:50:25.020> like<00:50:25.140> it's<00:50:25.260> like<00:50:25.440> a 00:50:25.609 --> 00:50:25.619 align:start position:0% know so it's a bit like it's like a 00:50:25.619 --> 00:50:27.050 align:start position:0% know so it's a bit like it's like a closer<00:50:25.800> closure<00:50:26.280> property<00:50:26.579> in<00:50:26.700> some<00:50:26.880> sense 00:50:27.050 --> 00:50:27.060 align:start position:0% closer closure property in some sense 00:50:27.060 --> 00:50:28.370 align:start position:0% closer closure property in some sense you<00:50:27.240> start<00:50:27.359> out<00:50:27.540> with<00:50:27.660> a<00:50:27.780> number<00:50:27.900> you<00:50:28.140> add<00:50:28.260> a 00:50:28.370 --> 00:50:28.380 align:start position:0% you start out with a number you add a 00:50:28.380 --> 00:50:30.050 align:start position:0% you start out with a number you add a number<00:50:28.500> you<00:50:28.680> end<00:50:28.800> up<00:50:28.920> with<00:50:28.980> a<00:50:29.099> number<00:50:29.520> the<00:50:29.940> same 00:50:30.050 --> 00:50:30.060 align:start position:0% number you end up with a number the same 00:50:30.060 --> 00:50:31.670 align:start position:0% number you end up with a number the same here<00:50:30.240> you<00:50:30.540> started<00:50:30.839> with<00:50:30.960> one<00:50:31.140> game<00:50:31.260> compose 00:50:31.670 --> 00:50:31.680 align:start position:0% here you started with one game compose 00:50:31.680 --> 00:50:34.130 align:start position:0% here you started with one game compose another<00:50:31.800> game<00:50:32.099> you<00:50:32.400> end<00:50:32.579> up<00:50:32.700> in<00:50:32.819> another<00:50:32.940> game 00:50:34.130 --> 00:50:34.140 align:start position:0% another game you end up in another game 00:50:34.140 --> 00:50:35.630 align:start position:0% another game you end up in another game and<00:50:34.619> this<00:50:34.740> is<00:50:34.859> in<00:50:35.040> some<00:50:35.160> sense<00:50:35.280> what<00:50:35.520> I 00:50:35.630 --> 00:50:35.640 align:start position:0% and this is in some sense what I 00:50:35.640 --> 00:50:37.490 align:start position:0% and this is in some sense what I referred<00:50:35.940> to<00:50:36.000> before<00:50:36.359> as<00:50:36.720> this<00:50:37.020> guarantees 00:50:37.490 --> 00:50:37.500 align:start position:0% referred to before as this guarantees 00:50:37.500 --> 00:50:38.809 align:start position:0% referred to before as this guarantees you<00:50:37.619> that<00:50:37.800> you<00:50:37.920> stay<00:50:38.040> in<00:50:38.220> a<00:50:38.339> formerly<00:50:38.640> well 00:50:38.809 --> 00:50:38.819 align:start position:0% you that you stay in a formerly well 00:50:38.819 --> 00:50:41.089 align:start position:0% you that you stay in a formerly well defined<00:50:39.240> framework 00:50:41.089 --> 00:50:41.099 align:start position:0% defined framework 00:50:41.099 --> 00:50:43.190 align:start position:0% defined framework okay<00:50:41.640> let<00:50:42.180> me<00:50:42.300> come<00:50:42.420> back<00:50:42.540> a<00:50:42.660> bit<00:50:42.780> to<00:50:43.020> the 00:50:43.190 --> 00:50:43.200 align:start position:0% okay let me come back a bit to the 00:50:43.200 --> 00:50:44.750 align:start position:0% okay let me come back a bit to the concrete<00:50:43.619> Implement<00:50:43.920> concrete 00:50:44.750 --> 00:50:44.760 align:start position:0% concrete Implement concrete 00:50:44.760 --> 00:50:47.329 align:start position:0% concrete Implement concrete interpretation<00:50:45.599> of<00:50:45.900> this<00:50:46.079> specific<00:50:46.319> box<00:50:46.619> and 00:50:47.329 --> 00:50:47.339 align:start position:0% interpretation of this specific box and 00:50:47.339 --> 00:50:49.430 align:start position:0% interpretation of this specific box and for<00:50:47.640> the<00:50:47.880> next<00:50:48.420> few<00:50:48.780> minutes<00:50:48.960> think<00:50:49.260> about 00:50:49.430 --> 00:50:49.440 align:start position:0% for the next few minutes think about 00:50:49.440 --> 00:50:50.990 align:start position:0% for the next few minutes think about this<00:50:49.680> box<00:50:49.859> as<00:50:50.099> just<00:50:50.339> one<00:50:50.520> player<00:50:50.819> doing 00:50:50.990 --> 00:50:51.000 align:start position:0% this box as just one player doing 00:50:51.000 --> 00:50:53.329 align:start position:0% this box as just one player doing something<00:50:51.619> now<00:50:52.619> one<00:50:52.859> way<00:50:52.980> to<00:50:53.099> think<00:50:53.220> about 00:50:53.329 --> 00:50:53.339 align:start position:0% something now one way to think about 00:50:53.339 --> 00:50:55.309 align:start position:0% something now one way to think about this<00:50:53.520> is<00:50:53.700> essentially<00:50:54.119> the<00:50:54.720> player<00:50:54.960> is<00:50:55.140> just 00:50:55.309 --> 00:50:55.319 align:start position:0% this is essentially the player is just 00:50:55.319 --> 00:50:56.150 align:start position:0% this is essentially the player is just doing<00:50:55.500> some<00:50:55.740> kind<00:50:55.920> of<00:50:55.980> information 00:50:56.150 --> 00:50:56.160 align:start position:0% doing some kind of information 00:50:56.160 --> 00:50:58.370 align:start position:0% doing some kind of information transformation<00:50:56.880> right<00:50:57.480> so<00:50:58.020> there<00:50:58.200> is 00:50:58.370 --> 00:50:58.380 align:start position:0% transformation right so there is 00:50:58.380 --> 00:51:00.109 align:start position:0% transformation right so there is something<00:50:58.500> coming<00:50:58.740> from<00:50:58.980> the<00:50:59.160> past<00:50:59.339> a<00:50:59.940> move 00:51:00.109 --> 00:51:00.119 align:start position:0% something coming from the past a move 00:51:00.119 --> 00:51:03.290 align:start position:0% something coming from the past a move information<00:51:00.540> whatever<00:51:01.140> X<00:51:02.059> the<00:51:03.059> player 00:51:03.290 --> 00:51:03.300 align:start position:0% information whatever X the player 00:51:03.300 --> 00:51:04.970 align:start position:0% information whatever X the player observes<00:51:03.839> this<00:51:04.020> and<00:51:04.380> internally<00:51:04.680> something 00:51:04.970 --> 00:51:04.980 align:start position:0% observes this and internally something 00:51:04.980 --> 00:51:07.930 align:start position:0% observes this and internally something happens<00:51:05.280> he's<00:51:05.760> outputting<00:51:06.300> a<00:51:06.420> move<00:51:06.599> why<00:51:07.020> okay 00:51:07.930 --> 00:51:07.940 align:start position:0% happens he's outputting a move why okay 00:51:07.940 --> 00:51:10.670 align:start position:0% happens he's outputting a move why okay now<00:51:08.940> the<00:51:09.720> question<00:51:09.839> of<00:51:10.079> course<00:51:10.200> is<00:51:10.319> what<00:51:10.500> kind 00:51:10.670 --> 00:51:10.680 align:start position:0% now the question of course is what kind 00:51:10.680 --> 00:51:12.829 align:start position:0% now the question of course is what kind of<00:51:10.740> move<00:51:10.920> will<00:51:11.220> a<00:51:11.460> player<00:51:11.700> make<00:51:12.119> this<00:51:12.480> depends 00:51:12.829 --> 00:51:12.839 align:start position:0% of move will a player make this depends 00:51:12.839 --> 00:51:14.210 align:start position:0% of move will a player make this depends on<00:51:12.960> what<00:51:13.260> what<00:51:13.440> kind<00:51:13.619> of<00:51:13.680> moves<00:51:13.920> he<00:51:14.040> has 00:51:14.210 --> 00:51:14.220 align:start position:0% on what what kind of moves he has 00:51:14.220 --> 00:51:16.490 align:start position:0% on what what kind of moves he has available<00:51:14.400> but<00:51:15.119> it<00:51:15.300> also<00:51:15.540> of<00:51:15.660> course<00:51:15.839> if<00:51:16.260> it<00:51:16.380> is 00:51:16.490 --> 00:51:16.500 align:start position:0% available but it also of course if it is 00:51:16.500 --> 00:51:18.890 align:start position:0% available but it also of course if it is a<00:51:16.740> game<00:51:16.800> theoretic<00:51:17.400> agent<00:51:18.000> Let<00:51:18.300> Me<00:51:18.480> Assume<00:51:18.780> for 00:51:18.890 --> 00:51:18.900 align:start position:0% a game theoretic agent Let Me Assume for 00:51:18.900 --> 00:51:20.150 align:start position:0% a game theoretic agent Let Me Assume for now<00:51:18.960> it's<00:51:19.140> a<00:51:19.260> rational<00:51:19.380> agent<00:51:19.740> who<00:51:19.859> wants<00:51:20.160> to 00:51:20.150 --> 00:51:20.160 align:start position:0% now it's a rational agent who wants to 00:51:20.160 --> 00:51:22.010 align:start position:0% now it's a rational agent who wants to maximize<00:51:20.579> something<00:51:20.819> he<00:51:21.599> needs<00:51:21.780> to<00:51:21.900> think 00:51:22.010 --> 00:51:22.020 align:start position:0% maximize something he needs to think 00:51:22.020 --> 00:51:24.109 align:start position:0% maximize something he needs to think about<00:51:22.200> what's<00:51:22.680> my<00:51:22.920> effect<00:51:23.099> of<00:51:23.460> choosing<00:51:23.880> wire 00:51:24.109 --> 00:51:24.119 align:start position:0% about what's my effect of choosing wire 00:51:24.119 --> 00:51:26.270 align:start position:0% about what's my effect of choosing wire on<00:51:24.660> my<00:51:24.839> utility 00:51:26.270 --> 00:51:26.280 align:start position:0% on my utility 00:51:26.280 --> 00:51:28.250 align:start position:0% on my utility and<00:51:26.819> you<00:51:26.940> see<00:51:27.119> that<00:51:27.240> the<00:51:27.420> wire<00:51:27.599> is<00:51:27.960> an<00:51:28.140> open 00:51:28.250 --> 00:51:28.260 align:start position:0% and you see that the wire is an open 00:51:28.260 --> 00:51:30.349 align:start position:0% and you see that the wire is an open wire<00:51:28.559> so<00:51:29.400> it<00:51:29.520> doesn't<00:51:29.640> really<00:51:29.880> specify 00:51:30.349 --> 00:51:30.359 align:start position:0% wire so it doesn't really specify 00:51:30.359 --> 00:51:32.750 align:start position:0% wire so it doesn't really specify exactly<00:51:30.780> how<00:51:31.020> it<00:51:31.140> is<00:51:31.260> interacting<00:51:31.800> yet<00:51:32.040> within 00:51:32.750 --> 00:51:32.760 align:start position:0% exactly how it is interacting yet within 00:51:32.760 --> 00:51:34.549 align:start position:0% exactly how it is interacting yet within my<00:51:33.000> with<00:51:33.180> the<00:51:33.420> environment 00:51:34.549 --> 00:51:34.559 align:start position:0% my with the environment 00:51:34.559 --> 00:51:37.250 align:start position:0% my with the environment but<00:51:35.099> what<00:51:35.520> we<00:51:35.640> can<00:51:35.819> say<00:51:36.000> is<00:51:36.180> the<00:51:36.780> player<00:51:37.079> is 00:51:37.250 --> 00:51:37.260 align:start position:0% but what we can say is the player is 00:51:37.260 --> 00:51:39.770 align:start position:0% but what we can say is the player is expecting<00:51:37.680> an<00:51:37.920> R<00:51:38.099> back<00:51:39.000> from<00:51:39.240> the<00:51:39.420> environment 00:51:39.770 --> 00:51:39.780 align:start position:0% expecting an R back from the environment 00:51:39.780 --> 00:51:42.349 align:start position:0% expecting an R back from the environment and<00:51:40.619> this<00:51:40.800> openness<00:51:41.160> between<00:51:41.400> my<00:51:41.819> action<00:51:42.000> Y 00:51:42.349 --> 00:51:42.359 align:start position:0% and this openness between my action Y 00:51:42.359 --> 00:51:44.809 align:start position:0% and this openness between my action Y and<00:51:43.079> the<00:51:43.260> payoff<00:51:43.500> data<00:51:43.859> or<00:51:44.099> whatever<00:51:44.460> actually 00:51:44.809 --> 00:51:44.819 align:start position:0% and the payoff data or whatever actually 00:51:44.819 --> 00:51:47.270 align:start position:0% and the payoff data or whatever actually are<00:51:45.119> is<00:51:45.599> in<00:51:45.900> fact<00:51:46.020> what<00:51:46.559> I<00:51:46.680> receive<00:51:46.920> from<00:51:47.099> the 00:51:47.270 --> 00:51:47.280 align:start position:0% are is in fact what I receive from the 00:51:47.280 --> 00:51:49.370 align:start position:0% are is in fact what I receive from the environment<00:51:47.640> that<00:51:48.119> openness<00:51:48.540> makes<00:51:49.200> it 00:51:49.370 --> 00:51:49.380 align:start position:0% environment that openness makes it 00:51:49.380 --> 00:51:51.410 align:start position:0% environment that openness makes it possible<00:51:49.680> to<00:51:49.859> take<00:51:50.040> it<00:51:50.280> like<00:51:51.119> a<00:51:51.300> building 00:51:51.410 --> 00:51:51.420 align:start position:0% possible to take it like a building 00:51:51.420 --> 00:51:54.170 align:start position:0% possible to take it like a building block<00:51:51.720> put<00:51:52.200> it<00:51:52.319> in<00:51:52.500> specific<00:51:52.859> situations<00:51:53.339> and 00:51:54.170 --> 00:51:54.180 align:start position:0% block put it in specific situations and 00:51:54.180 --> 00:51:55.730 align:start position:0% block put it in specific situations and then<00:51:54.240> sometimes<00:51:54.660> I<00:51:54.960> might<00:51:55.079> be<00:51:55.200> able<00:51:55.380> to<00:51:55.500> close 00:51:55.730 --> 00:51:55.740 align:start position:0% then sometimes I might be able to close 00:51:55.740 --> 00:51:56.990 align:start position:0% then sometimes I might be able to close the<00:51:55.980> loop 00:51:56.990 --> 00:51:57.000 align:start position:0% the loop 00:51:57.000 --> 00:51:58.970 align:start position:0% the loop um<00:51:57.059> in<00:51:57.300> a<00:51:57.420> certain<00:51:57.540> way<00:51:57.720> the<00:51:58.260> most<00:51:58.380> trivial<00:51:58.740> way 00:51:58.970 --> 00:51:58.980 align:start position:0% um in a certain way the most trivial way 00:51:58.980 --> 00:52:01.549 align:start position:0% um in a certain way the most trivial way of<00:51:59.280> closing<00:51:59.700> it<00:51:59.819> would<00:52:00.420> be<00:52:00.540> I<00:52:00.900> have<00:52:01.079> one<00:52:01.200> player 00:52:01.549 --> 00:52:01.559 align:start position:0% of closing it would be I have one player 00:52:01.559 --> 00:52:03.849 align:start position:0% of closing it would be I have one player and<00:52:01.859> I'm<00:52:01.980> just<00:52:02.160> bending<00:52:02.520> the<00:52:02.700> Y<00:52:02.880> back<00:52:03.300> into<00:52:03.480> R 00:52:03.849 --> 00:52:03.859 align:start position:0% and I'm just bending the Y back into R 00:52:03.859 --> 00:52:06.890 align:start position:0% and I'm just bending the Y back into R and<00:52:04.859> then<00:52:04.980> basically<00:52:05.339> my<00:52:05.640> why<00:52:06.300> my<00:52:06.540> action<00:52:06.720> that 00:52:06.890 --> 00:52:06.900 align:start position:0% and then basically my why my action that 00:52:06.900 --> 00:52:08.450 align:start position:0% and then basically my why my action that I<00:52:07.079> take<00:52:07.200> will<00:52:07.380> be<00:52:07.559> directly<00:52:07.859> to<00:52:07.980> think<00:52:08.160> that<00:52:08.339> I 00:52:08.450 --> 00:52:08.460 align:start position:0% I take will be directly to think that I 00:52:08.460 --> 00:52:10.430 align:start position:0% I take will be directly to think that I observe<00:52:08.819> and<00:52:09.059> I<00:52:09.180> affect<00:52:09.540> I<00:52:10.020> have<00:52:10.079> full<00:52:10.260> control 00:52:10.430 --> 00:52:10.440 align:start position:0% observe and I affect I have full control 00:52:10.440 --> 00:52:12.230 align:start position:0% observe and I affect I have full control basically 00:52:12.230 --> 00:52:12.240 align:start position:0% basically 00:52:12.240 --> 00:52:14.510 align:start position:0% basically most<00:52:12.900> interesting<00:52:13.319> scenarios<00:52:13.859> from<00:52:14.280> a<00:52:14.400> game 00:52:14.510 --> 00:52:14.520 align:start position:0% most interesting scenarios from a game 00:52:14.520 --> 00:52:15.950 align:start position:0% most interesting scenarios from a game theory<00:52:14.819> perspective<00:52:15.180> are<00:52:15.540> obviously<00:52:15.839> not 00:52:15.950 --> 00:52:15.960 align:start position:0% theory perspective are obviously not 00:52:15.960 --> 00:52:18.410 align:start position:0% theory perspective are obviously not like<00:52:16.140> that<00:52:16.380> but<00:52:17.280> my<00:52:17.460> why<00:52:17.640> will<00:52:17.940> not<00:52:18.059> solely 00:52:18.410 --> 00:52:18.420 align:start position:0% like that but my why will not solely 00:52:18.420 --> 00:52:19.970 align:start position:0% like that but my why will not solely determine<00:52:18.839> what<00:52:19.020> my<00:52:19.140> payoff<00:52:19.500> actually<00:52:19.740> is 00:52:19.970 --> 00:52:19.980 align:start position:0% determine what my payoff actually is 00:52:19.980 --> 00:52:22.130 align:start position:0% determine what my payoff actually is like<00:52:20.579> in<00:52:20.819> a<00:52:20.940> prison<00:52:21.059> dilemma<00:52:21.540> there's<00:52:21.960> another 00:52:22.130 --> 00:52:22.140 align:start position:0% like in a prison dilemma there's another 00:52:22.140 --> 00:52:24.290 align:start position:0% like in a prison dilemma there's another agent<00:52:22.559> doing<00:52:22.740> something<00:52:23.040> and<00:52:23.819> this<00:52:23.940> will<00:52:24.119> also 00:52:24.290 --> 00:52:24.300 align:start position:0% agent doing something and this will also 00:52:24.300 --> 00:52:25.630 align:start position:0% agent doing something and this will also affect<00:52:24.540> my<00:52:24.720> payoff 00:52:25.630 --> 00:52:25.640 align:start position:0% affect my payoff 00:52:25.640 --> 00:52:28.069 align:start position:0% affect my payoff and<00:52:26.640> of<00:52:26.700> course<00:52:26.819> this<00:52:27.119> is<00:52:27.180> the<00:52:27.359> idea<00:52:27.660> that<00:52:27.900> at 00:52:28.069 --> 00:52:28.079 align:start position:0% and of course this is the idea that at 00:52:28.079 --> 00:52:29.569 align:start position:0% and of course this is the idea that at some<00:52:28.260> point<00:52:28.440> we<00:52:28.680> will<00:52:28.800> give<00:52:28.980> a<00:52:29.160> concrete 00:52:29.569 --> 00:52:29.579 align:start position:0% some point we will give a concrete 00:52:29.579 --> 00:52:32.150 align:start position:0% some point we will give a concrete environment<00:52:30.359> which<00:52:30.960> determines<00:52:31.440> how<00:52:31.740> this<00:52:31.920> y 00:52:32.150 --> 00:52:32.160 align:start position:0% environment which determines how this y 00:52:32.160 --> 00:52:34.010 align:start position:0% environment which determines how this y actually<00:52:32.700> spent<00:52:33.180> back<00:52:33.359> into<00:52:33.599> a<00:52:33.780> specific 00:52:34.010 --> 00:52:34.020 align:start position:0% actually spent back into a specific 00:52:34.020 --> 00:52:36.950 align:start position:0% actually spent back into a specific payoff<00:52:34.500> whatever<00:52:35.280> or<00:52:35.640> whatever<00:52:35.819> result<00:52:36.180> you 00:52:36.950 --> 00:52:36.960 align:start position:0% payoff whatever or whatever result you 00:52:36.960 --> 00:52:39.650 align:start position:0% payoff whatever or whatever result you actually<00:52:37.140> care<00:52:37.440> about<00:52:37.559> as<00:52:37.800> an<00:52:37.980> agent 00:52:39.650 --> 00:52:39.660 align:start position:0% actually care about as an agent 00:52:39.660 --> 00:52:42.530 align:start position:0% actually care about as an agent okay<00:52:40.260> so<00:52:40.800> that's<00:52:40.980> the<00:52:41.160> basic<00:52:41.520> structure 00:52:42.530 --> 00:52:42.540 align:start position:0% okay so that's the basic structure 00:52:42.540 --> 00:52:44.329 align:start position:0% okay so that's the basic structure now<00:52:43.020> I<00:52:43.260> said<00:52:43.380> before<00:52:43.619> we<00:52:43.859> are<00:52:43.980> building<00:52:44.099> up 00:52:44.329 --> 00:52:44.339 align:start position:0% now I said before we are building up 00:52:44.339 --> 00:52:45.589 align:start position:0% now I said before we are building up from<00:52:44.520> the<00:52:44.640> bottom 00:52:45.589 --> 00:52:45.599 align:start position:0% from the bottom 00:52:45.599 --> 00:52:47.690 align:start position:0% from the bottom what<00:52:46.079> we<00:52:46.260> want<00:52:46.380> is<00:52:46.680> we<00:52:47.099> want<00:52:47.220> to<00:52:47.339> compose 00:52:47.690 --> 00:52:47.700 align:start position:0% what we want is we want to compose 00:52:47.700 --> 00:52:49.750 align:start position:0% what we want is we want to compose larger<00:52:48.059> games<00:52:48.240> by<00:52:48.599> composing<00:52:49.200> simpler<00:52:49.619> games 00:52:49.750 --> 00:52:49.760 align:start position:0% larger games by composing simpler games 00:52:49.760 --> 00:52:52.370 align:start position:0% larger games by composing simpler games and<00:52:50.760> what<00:52:51.180> we<00:52:51.300> need<00:52:51.420> for<00:52:51.599> this<00:52:51.780> are 00:52:52.370 --> 00:52:52.380 align:start position:0% and what we need for this are 00:52:52.380 --> 00:52:54.589 align:start position:0% and what we need for this are essentially<00:52:53.040> two<00:52:53.280> kind<00:52:53.460> of<00:52:53.640> things<00:52:53.819> we<00:52:54.420> want 00:52:54.589 --> 00:52:54.599 align:start position:0% essentially two kind of things we want 00:52:54.599 --> 00:52:56.990 align:start position:0% essentially two kind of things we want some<00:52:54.839> building<00:52:55.140> blocks<00:52:55.619> think<00:52:56.400> a<00:52:56.579> bit<00:52:56.700> you 00:52:56.990 --> 00:52:57.000 align:start position:0% some building blocks think a bit you 00:52:57.000 --> 00:52:58.370 align:start position:0% some building blocks think a bit you know<00:52:57.119> again<00:52:57.180> like<00:52:57.420> Lego 00:52:58.370 --> 00:52:58.380 align:start position:0% know again like Lego 00:52:58.380 --> 00:52:59.870 align:start position:0% know again like Lego um<00:52:58.440> you<00:52:58.619> have<00:52:58.740> one<00:52:58.980> specific<00:52:59.280> thing<00:52:59.520> and<00:52:59.700> from 00:52:59.870 --> 00:52:59.880 align:start position:0% um you have one specific thing and from 00:52:59.880 --> 00:53:01.430 align:start position:0% um you have one specific thing and from that<00:53:00.000> if<00:53:00.180> you<00:53:00.300> have<00:53:00.420> it<00:53:00.540> and<00:53:00.900> you<00:53:01.020> have<00:53:01.140> more<00:53:01.319> of 00:53:01.430 --> 00:53:01.440 align:start position:0% that if you have it and you have more of 00:53:01.440 --> 00:53:03.230 align:start position:0% that if you have it and you have more of them<00:53:01.619> you<00:53:02.040> can<00:53:02.099> just<00:53:02.220> build<00:53:02.400> up<00:53:02.579> a<00:53:02.760> wall<00:53:02.880> for 00:53:03.230 --> 00:53:03.240 align:start position:0% them you can just build up a wall for 00:53:03.240 --> 00:53:04.430 align:start position:0% them you can just build up a wall for instance 00:53:04.430 --> 00:53:04.440 align:start position:0% instance 00:53:04.440 --> 00:53:05.930 align:start position:0% instance so<00:53:04.800> we<00:53:04.980> need<00:53:05.099> the<00:53:05.220> building<00:53:05.339> blocks<00:53:05.760> the 00:53:05.930 --> 00:53:05.940 align:start position:0% so we need the building blocks the 00:53:05.940 --> 00:53:07.730 align:start position:0% so we need the building blocks the atomic<00:53:06.300> units<00:53:06.720> if<00:53:06.839> you<00:53:06.960> like<00:53:07.079> and<00:53:07.500> then<00:53:07.559> we 00:53:07.730 --> 00:53:07.740 align:start position:0% atomic units if you like and then we 00:53:07.740 --> 00:53:10.370 align:start position:0% atomic units if you like and then we need<00:53:07.859> operations<00:53:08.220> how<00:53:08.460> to<00:53:08.640> compose<00:53:08.940> stuff 00:53:10.370 --> 00:53:10.380 align:start position:0% need operations how to compose stuff 00:53:10.380 --> 00:53:12.410 align:start position:0% need operations how to compose stuff on<00:53:10.980> the<00:53:11.160> buildings<00:53:11.520> on<00:53:11.760> the<00:53:11.940> atomic<00:53:12.300> building 00:53:12.410 --> 00:53:12.420 align:start position:0% on the buildings on the atomic building 00:53:12.420 --> 00:53:14.690 align:start position:0% on the buildings on the atomic building blocks<00:53:12.839> we<00:53:12.960> have<00:53:13.140> essentially<00:53:13.500> two<00:53:13.800> which<00:53:14.520> is 00:53:14.690 --> 00:53:14.700 align:start position:0% blocks we have essentially two which is 00:53:14.700 --> 00:53:16.910 align:start position:0% blocks we have essentially two which is a<00:53:15.180> decision<00:53:15.480> a<00:53:15.960> single<00:53:16.260> player<00:53:16.500> making<00:53:16.680> a 00:53:16.910 --> 00:53:16.920 align:start position:0% a decision a single player making a 00:53:16.920 --> 00:53:17.690 align:start position:0% a decision a single player making a decision 00:53:17.690 --> 00:53:17.700 align:start position:0% decision 00:53:17.700 --> 00:53:19.849 align:start position:0% decision and<00:53:18.180> the<00:53:18.359> computation<00:53:18.720> computation<00:53:19.440> means 00:53:19.849 --> 00:53:19.859 align:start position:0% and the computation computation means 00:53:19.859 --> 00:53:22.130 align:start position:0% and the computation computation means just<00:53:20.040> some<00:53:20.339> input<00:53:20.700> is<00:53:20.819> observed<00:53:21.300> some<00:53:21.780> output 00:53:22.130 --> 00:53:22.140 align:start position:0% just some input is observed some output 00:53:22.140 --> 00:53:24.230 align:start position:0% just some input is observed some output is<00:53:22.380> basically<00:53:22.740> the<00:53:22.859> result 00:53:24.230 --> 00:53:24.240 align:start position:0% is basically the result 00:53:24.240 --> 00:53:24.950 align:start position:0% is basically the result um 00:53:24.950 --> 00:53:24.960 align:start position:0% um 00:53:24.960 --> 00:53:26.630 align:start position:0% um these<00:53:25.559> these<00:53:25.859> computations<00:53:26.160> can<00:53:26.339> have<00:53:26.460> side 00:53:26.630 --> 00:53:26.640 align:start position:0% these these computations can have side 00:53:26.640 --> 00:53:28.370 align:start position:0% these these computations can have side effects<00:53:26.940> so<00:53:27.119> it<00:53:27.240> could<00:53:27.420> be 00:53:28.370 --> 00:53:28.380 align:start position:0% effects so it could be 00:53:28.380 --> 00:53:29.809 align:start position:0% effects so it could be um<00:53:28.440> actually<00:53:28.680> a<00:53:28.859> deterministic<00:53:29.460> input<00:53:29.700> is 00:53:29.809 --> 00:53:29.819 align:start position:0% um actually a deterministic input is 00:53:29.819 --> 00:53:31.130 align:start position:0% um actually a deterministic input is turned<00:53:30.059> into<00:53:30.180> a<00:53:30.300> probability<00:53:30.660> distribution 00:53:31.130 --> 00:53:31.140 align:start position:0% turned into a probability distribution 00:53:31.140 --> 00:53:33.410 align:start position:0% turned into a probability distribution or<00:53:31.619> a<00:53:31.740> probability<00:53:32.420> probability 00:53:33.410 --> 00:53:33.420 align:start position:0% or a probability probability 00:53:33.420 --> 00:53:35.150 align:start position:0% or a probability probability distribution<00:53:33.960> as<00:53:34.200> an<00:53:34.319> input<00:53:34.559> is<00:53:34.740> turned<00:53:35.040> into 00:53:35.150 --> 00:53:35.160 align:start position:0% distribution as an input is turned into 00:53:35.160 --> 00:53:37.670 align:start position:0% distribution as an input is turned into another<00:53:35.460> probability<00:53:35.880> distribution 00:53:37.670 --> 00:53:37.680 align:start position:0% another probability distribution 00:53:37.680 --> 00:53:39.710 align:start position:0% another probability distribution good<00:53:38.040> what<00:53:38.400> are<00:53:38.520> the<00:53:38.700> composition<00:53:39.240> operations 00:53:39.710 --> 00:53:39.720 align:start position:0% good what are the composition operations 00:53:39.720 --> 00:53:41.630 align:start position:0% good what are the composition operations for<00:53:40.440> those<00:53:40.619> of<00:53:40.740> you<00:53:40.859> who<00:53:41.040> already<00:53:41.220> followed 00:53:41.630 --> 00:53:41.640 align:start position:0% for those of you who already followed 00:53:41.640 --> 00:53:44.390 align:start position:0% for those of you who already followed for<00:53:41.819> pizza<00:53:42.000> you<00:53:42.900> will<00:53:43.079> already<00:53:43.260> guess<00:53:43.500> it<00:53:43.740> it's 00:53:44.390 --> 00:53:44.400 align:start position:0% for pizza you will already guess it it's 00:53:44.400 --> 00:53:48.049 align:start position:0% for pizza you will already guess it it's parallel<00:53:45.119> and<00:53:45.300> sequential<00:53:45.780> composition 00:53:48.049 --> 00:53:48.059 align:start position:0% parallel and sequential composition 00:53:48.059 --> 00:53:50.450 align:start position:0% parallel and sequential composition um parallel<00:53:48.599> in<00:53:48.839> the<00:53:48.960> game<00:53:49.020> 360<00:53:49.339> is<00:53:50.339> maybe 00:53:50.450 --> 00:53:50.460 align:start position:0% um parallel in the game 360 is maybe 00:53:50.460 --> 00:53:52.910 align:start position:0% um parallel in the game 360 is maybe more<00:53:50.700> easier<00:53:51.000> interpreted<00:53:51.420> as<00:53:51.599> simultaneous 00:53:52.910 --> 00:53:52.920 align:start position:0% more easier interpreted as simultaneous 00:53:52.920 --> 00:53:55.490 align:start position:0% more easier interpreted as simultaneous and<00:53:53.880> what<00:53:54.240> this<00:53:54.359> looks<00:53:54.660> like<00:53:54.720> essentially<00:53:55.200> is 00:53:55.490 --> 00:53:55.500 align:start position:0% and what this looks like essentially is 00:53:55.500 --> 00:53:57.710 align:start position:0% and what this looks like essentially is again<00:53:56.220> repeating<00:53:56.819> a<00:53:56.940> bit<00:53:57.000> of<00:53:57.240> what<00:53:57.480> we<00:53:57.599> have 00:53:57.710 --> 00:53:57.720 align:start position:0% again repeating a bit of what we have 00:53:57.720 --> 00:54:00.290 align:start position:0% again repeating a bit of what we have seen<00:53:57.900> you<00:53:58.319> have<00:53:58.440> two<00:53:58.559> games<00:53:58.740> do<00:53:58.980> you<00:53:59.099> want<00:53:59.220> a<00:53:59.339> G2 00:54:00.290 --> 00:54:00.300 align:start position:0% seen you have two games do you want a G2 00:54:00.300 --> 00:54:02.390 align:start position:0% seen you have two games do you want a G2 if<00:54:00.720> they<00:54:00.839> are<00:54:00.960> in<00:54:01.079> parallel<00:54:01.440> you<00:54:01.920> can<00:54:02.040> compose 00:54:02.390 --> 00:54:02.400 align:start position:0% if they are in parallel you can compose 00:54:02.400 --> 00:54:04.430 align:start position:0% if they are in parallel you can compose them<00:54:02.640> and<00:54:03.300> then<00:54:03.359> they<00:54:03.540> again<00:54:03.720> will<00:54:04.020> have<00:54:04.200> this 00:54:04.430 --> 00:54:04.440 align:start position:0% them and then they again will have this 00:54:04.440 --> 00:54:07.549 align:start position:0% them and then they again will have this basic<00:54:04.800> shape<00:54:05.099> of<00:54:05.400> input<00:54:05.940> X<00:54:06.180> cross<00:54:06.540> the<00:54:06.780> X2<00:54:07.079> X2 00:54:07.549 --> 00:54:07.559 align:start position:0% basic shape of input X cross the X2 X2 00:54:07.559 --> 00:54:09.470 align:start position:0% basic shape of input X cross the X2 X2 in<00:54:07.740> that<00:54:07.859> case<00:54:08.040> turned<00:54:08.940> into<00:54:09.059> a<00:54:09.240> certain 00:54:09.470 --> 00:54:09.480 align:start position:0% in that case turned into a certain 00:54:09.480 --> 00:54:12.650 align:start position:0% in that case turned into a certain output<00:54:10.319> and<00:54:10.740> it's<00:54:11.280> the<00:54:11.579> same<00:54:11.700> time<00:54:11.880> expecting 00:54:12.650 --> 00:54:12.660 align:start position:0% output and it's the same time expecting 00:54:12.660 --> 00:54:14.390 align:start position:0% output and it's the same time expecting a<00:54:12.839> certain<00:54:12.960> result<00:54:13.200> and<00:54:13.800> sending<00:54:14.220> some 00:54:14.390 --> 00:54:14.400 align:start position:0% a certain result and sending some 00:54:14.400 --> 00:54:18.170 align:start position:0% a certain result and sending some information<00:54:14.579> back<00:54:15.420> into<00:54:15.599> the<00:54:15.900> past 00:54:18.170 --> 00:54:18.180 align:start position:0% 00:54:18.180 --> 00:54:20.450 align:start position:0% okay<00:54:18.599> sequential<00:54:19.140> composition<00:54:19.619> we<00:54:20.040> have<00:54:20.220> G 00:54:20.450 --> 00:54:20.460 align:start position:0% okay sequential composition we have G 00:54:20.460 --> 00:54:23.210 align:start position:0% okay sequential composition we have G first<00:54:20.940> H<00:54:21.480> following<00:54:22.020> you<00:54:22.559> can<00:54:22.619> stack<00:54:22.859> them<00:54:23.040> on 00:54:23.210 --> 00:54:23.220 align:start position:0% first H following you can stack them on 00:54:23.220 --> 00:54:24.109 align:start position:0% first H following you can stack them on each<00:54:23.339> other 00:54:24.109 --> 00:54:24.119 align:start position:0% each other 00:54:24.119 --> 00:54:27.530 align:start position:0% each other so<00:54:24.540> that<00:54:24.720> they<00:54:24.900> look<00:54:25.140> in<00:54:25.920> the<00:54:26.040> following<00:54:26.339> way 00:54:27.530 --> 00:54:27.540 align:start position:0% so that they look in the following way 00:54:27.540 --> 00:54:29.630 align:start position:0% so that they look in the following way now<00:54:28.020> what<00:54:28.200> is<00:54:28.319> important<00:54:28.680> so<00:54:29.220> far<00:54:29.339> I<00:54:29.460> haven't 00:54:29.630 --> 00:54:29.640 align:start position:0% now what is important so far I haven't 00:54:29.640 --> 00:54:31.549 align:start position:0% now what is important so far I haven't said<00:54:29.880> anything<00:54:30.059> about<00:54:30.420> what<00:54:30.839> these<00:54:31.079> labels<00:54:31.380> x 00:54:31.549 --> 00:54:31.559 align:start position:0% said anything about what these labels x 00:54:31.559 --> 00:54:33.829 align:start position:0% said anything about what these labels x y<00:54:31.800> and<00:54:32.040> actually<00:54:32.160> correspond<00:54:32.640> to 00:54:33.829 --> 00:54:33.839 align:start position:0% y and actually correspond to 00:54:33.839 --> 00:54:35.329 align:start position:0% y and actually correspond to um<00:54:33.960> you<00:54:34.200> can<00:54:34.260> think<00:54:34.440> about<00:54:34.559> them<00:54:34.800> as<00:54:34.920> shapes 00:54:35.329 --> 00:54:35.339 align:start position:0% um you can think about them as shapes 00:54:35.339 --> 00:54:37.250 align:start position:0% um you can think about them as shapes and<00:54:36.000> only<00:54:36.180> games<00:54:36.480> that<00:54:36.780> actually<00:54:36.960> have<00:54:37.140> the 00:54:37.250 --> 00:54:37.260 align:start position:0% and only games that actually have the 00:54:37.260 --> 00:54:39.650 align:start position:0% and only games that actually have the right<00:54:37.380> shape<00:54:37.680> can<00:54:38.099> be<00:54:38.220> stacked<00:54:38.520> on<00:54:38.640> each<00:54:38.760> other 00:54:39.650 --> 00:54:39.660 align:start position:0% right shape can be stacked on each other 00:54:39.660 --> 00:54:41.270 align:start position:0% right shape can be stacked on each other and<00:54:39.960> this<00:54:40.079> is<00:54:40.200> important<00:54:40.559> because<00:54:40.859> you<00:54:41.160> know 00:54:41.270 --> 00:54:41.280 align:start position:0% and this is important because you know 00:54:41.280 --> 00:54:42.890 align:start position:0% and this is important because you know if<00:54:41.400> I<00:54:41.579> say<00:54:41.700> you<00:54:42.000> know<00:54:42.059> give<00:54:42.300> me<00:54:42.420> two<00:54:42.599> games<00:54:42.720> and 00:54:42.890 --> 00:54:42.900 align:start position:0% if I say you know give me two games and 00:54:42.900 --> 00:54:45.349 align:start position:0% if I say you know give me two games and I<00:54:43.079> can<00:54:43.140> compose<00:54:43.500> them<00:54:43.680> you<00:54:44.160> might<00:54:44.280> wonder<00:54:44.460> that 00:54:45.349 --> 00:54:45.359 align:start position:0% I can compose them you might wonder that 00:54:45.359 --> 00:54:47.210 align:start position:0% I can compose them you might wonder that sounds<00:54:45.540> weird<00:54:45.839> how<00:54:46.200> can<00:54:46.380> this<00:54:46.559> be<00:54:46.740> possible<00:54:46.980> in 00:54:47.210 --> 00:54:47.220 align:start position:0% sounds weird how can this be possible in 00:54:47.220 --> 00:54:49.010 align:start position:0% sounds weird how can this be possible in generality<00:54:47.700> right<00:54:48.000> I<00:54:48.420> can<00:54:48.480> easily<00:54:48.720> come<00:54:48.900> up 00:54:49.010 --> 00:54:49.020 align:start position:0% generality right I can easily come up 00:54:49.020 --> 00:54:51.230 align:start position:0% generality right I can easily come up with<00:54:49.140> two<00:54:49.319> games<00:54:49.500> that<00:54:49.800> are<00:54:49.980> not<00:54:50.640> so<00:54:50.880> easy<00:54:51.000> to 00:54:51.230 --> 00:54:51.240 align:start position:0% with two games that are not so easy to 00:54:51.240 --> 00:54:53.569 align:start position:0% with two games that are not so easy to or<00:54:51.599> maybe<00:54:51.780> not<00:54:51.900> at<00:54:52.079> all<00:54:52.260> composable 00:54:53.569 --> 00:54:53.579 align:start position:0% or maybe not at all composable 00:54:53.579 --> 00:54:55.430 align:start position:0% or maybe not at all composable the<00:54:54.059> Restriction<00:54:54.359> that<00:54:54.599> you<00:54:54.720> have<00:54:54.900> is<00:54:55.200> that 00:54:55.430 --> 00:54:55.440 align:start position:0% the Restriction that you have is that 00:54:55.440 --> 00:54:57.290 align:start position:0% the Restriction that you have is that these<00:54:55.740> shapes<00:54:56.040> the<00:54:56.579> labels<00:54:56.880> here<00:54:57.059> actually 00:54:57.290 --> 00:54:57.300 align:start position:0% these shapes the labels here actually 00:54:57.300 --> 00:54:59.750 align:start position:0% these shapes the labels here actually have<00:54:57.480> to<00:54:57.599> match<00:54:57.780> up<00:54:57.960> only<00:54:58.559> then<00:54:58.800> can<00:54:59.400> you<00:54:59.579> stack 00:54:59.750 --> 00:54:59.760 align:start position:0% have to match up only then can you stack 00:54:59.760 --> 00:55:02.030 align:start position:0% have to match up only then can you stack games<00:55:00.000> together 00:55:02.030 --> 00:55:02.040 align:start position:0% games together 00:55:02.040 --> 00:55:04.010 align:start position:0% games together forbidity<00:55:02.819> already<00:55:03.000> set<00:55:03.300> from<00:55:03.540> a<00:55:03.660> categorical 00:55:04.010 --> 00:55:04.020 align:start position:0% forbidity already set from a categorical 00:55:04.020 --> 00:55:05.690 align:start position:0% forbidity already set from a categorical perspective<00:55:04.500> and<00:55:04.859> then<00:55:04.980> of<00:55:05.160> course<00:55:05.280> also<00:55:05.579> from 00:55:05.690 --> 00:55:05.700 align:start position:0% perspective and then of course also from 00:55:05.700 --> 00:55:07.609 align:start position:0% perspective and then of course also from the<00:55:05.880> programming<00:55:06.240> perspectives<00:55:06.660> perspective 00:55:07.609 --> 00:55:07.619 align:start position:0% the programming perspectives perspective 00:55:07.619 --> 00:55:10.309 align:start position:0% the programming perspectives perspective these<00:55:08.400> labels<00:55:08.700> will<00:55:08.880> be<00:55:09.059> types<00:55:09.420> so<00:55:09.900> only<00:55:10.079> if 00:55:10.309 --> 00:55:10.319 align:start position:0% these labels will be types so only if 00:55:10.319 --> 00:55:12.230 align:start position:0% these labels will be types so only if the<00:55:10.500> types<00:55:10.740> match<00:55:10.920> up<00:55:11.160> can<00:55:11.880> you<00:55:12.059> actually 00:55:12.230 --> 00:55:12.240 align:start position:0% the types match up can you actually 00:55:12.240 --> 00:55:14.450 align:start position:0% the types match up can you actually stack<00:55:12.540> games<00:55:12.839> together<00:55:13.160> this<00:55:14.160> is<00:55:14.280> quite 00:55:14.450 --> 00:55:14.460 align:start position:0% stack games together this is quite 00:55:14.460 --> 00:55:15.530 align:start position:0% stack games together this is quite useful 00:55:15.530 --> 00:55:15.540 align:start position:0% useful 00:55:15.540 --> 00:55:16.549 align:start position:0% useful um and<00:55:15.780> it's<00:55:15.900> actually<00:55:16.079> an<00:55:16.260> important 00:55:16.549 --> 00:55:16.559 align:start position:0% um and it's actually an important 00:55:16.559 --> 00:55:18.530 align:start position:0% um and it's actually an important restriction<00:55:16.859> because<00:55:17.220> you<00:55:18.000> know<00:55:18.059> if<00:55:18.300> let's 00:55:18.530 --> 00:55:18.540 align:start position:0% restriction because you know if let's 00:55:18.540 --> 00:55:21.049 align:start position:0% restriction because you know if let's say<00:55:18.660> G<00:55:18.960> is<00:55:19.140> outputting<00:55:19.619> a<00:55:20.040> Boolean<00:55:20.400> and<00:55:20.640> H<00:55:20.819> is 00:55:21.049 --> 00:55:21.059 align:start position:0% say G is outputting a Boolean and H is 00:55:21.059 --> 00:55:22.790 align:start position:0% say G is outputting a Boolean and H is expecting<00:55:21.480> a<00:55:21.599> numerical<00:55:21.960> value<00:55:22.140> a<00:55:22.440> numerical 00:55:22.790 --> 00:55:22.800 align:start position:0% expecting a numerical value a numerical 00:55:22.800 --> 00:55:23.930 align:start position:0% expecting a numerical value a numerical type 00:55:23.930 --> 00:55:23.940 align:start position:0% type 00:55:23.940 --> 00:55:26.210 align:start position:0% type you<00:55:24.300> can't<00:55:24.480> match<00:55:24.660> them<00:55:24.900> up<00:55:25.079> basically<00:55:25.619> right 00:55:26.210 --> 00:55:26.220 align:start position:0% you can't match them up basically right 00:55:26.220 --> 00:55:28.670 align:start position:0% you can't match them up basically right what<00:55:27.119> is<00:55:27.240> even<00:55:27.359> more<00:55:27.540> important<00:55:27.900> if<00:55:28.380> you<00:55:28.500> try 00:55:28.670 --> 00:55:28.680 align:start position:0% what is even more important if you try 00:55:28.680 --> 00:55:30.470 align:start position:0% what is even more important if you try to<00:55:28.800> do<00:55:28.920> that<00:55:29.040> the<00:55:29.280> engine<00:55:29.520> in<00:55:30.000> that<00:55:30.119> case<00:55:30.300> the 00:55:30.470 --> 00:55:30.480 align:start position:0% to do that the engine in that case the 00:55:30.480 --> 00:55:31.910 align:start position:0% to do that the engine in that case the Hustler<00:55:30.780> compiler<00:55:31.140> will<00:55:31.319> loudly<00:55:31.619> complain 00:55:31.910 --> 00:55:31.920 align:start position:0% Hustler compiler will loudly complain 00:55:31.920 --> 00:55:33.410 align:start position:0% Hustler compiler will loudly complain that<00:55:32.160> this<00:55:32.400> is<00:55:32.520> not<00:55:32.640> feasible<00:55:33.000> you<00:55:33.119> can't<00:55:33.240> do 00:55:33.410 --> 00:55:33.420 align:start position:0% that this is not feasible you can't do 00:55:33.420 --> 00:55:34.130 align:start position:0% that this is not feasible you can't do that 00:55:34.130 --> 00:55:34.140 align:start position:0% that 00:55:34.140 --> 00:55:36.829 align:start position:0% that what<00:55:34.619> is<00:55:34.859> more<00:55:35.040> because<00:55:35.760> you<00:55:36.000> can't<00:55:36.180> obviously 00:55:36.829 --> 00:55:36.839 align:start position:0% what is more because you can't obviously 00:55:36.839 --> 00:55:38.750 align:start position:0% what is more because you can't obviously design<00:55:37.079> your<00:55:37.380> own<00:55:37.500> types<00:55:37.859> you<00:55:38.339> have<00:55:38.460> also 00:55:38.750 --> 00:55:38.760 align:start position:0% design your own types you have also 00:55:38.760 --> 00:55:40.370 align:start position:0% design your own types you have also degrees<00:55:38.940> of<00:55:39.480> freedom<00:55:39.780> of<00:55:39.900> you<00:55:40.140> know<00:55:40.200> being 00:55:40.370 --> 00:55:40.380 align:start position:0% degrees of freedom of you know being 00:55:40.380 --> 00:55:41.870 align:start position:0% degrees of freedom of you know being very<00:55:40.559> specific<00:55:40.859> about<00:55:41.099> what<00:55:41.400> kind<00:55:41.520> of<00:55:41.579> input 00:55:41.870 --> 00:55:41.880 align:start position:0% very specific about what kind of input 00:55:41.880 --> 00:55:44.150 align:start position:0% very specific about what kind of input type<00:55:42.059> is<00:55:42.300> actually<00:55:42.420> expected<00:55:42.960> yeah<00:55:43.500> so<00:55:43.740> it's 00:55:44.150 --> 00:55:44.160 align:start position:0% type is actually expected yeah so it's 00:55:44.160 --> 00:55:45.349 align:start position:0% type is actually expected yeah so it's basically<00:55:44.400> also<00:55:44.700> part<00:55:44.819> of<00:55:44.940> the<00:55:45.059> modeling 00:55:45.349 --> 00:55:45.359 align:start position:0% basically also part of the modeling 00:55:45.359 --> 00:55:46.970 align:start position:0% basically also part of the modeling effort<00:55:45.660> that<00:55:46.200> you<00:55:46.380> can<00:55:46.440> you<00:55:46.619> have<00:55:46.800> control 00:55:46.970 --> 00:55:46.980 align:start position:0% effort that you can you have control 00:55:46.980 --> 00:55:48.170 align:start position:0% effort that you can you have control over 00:55:48.170 --> 00:55:48.180 align:start position:0% over 00:55:48.180 --> 00:55:51.410 align:start position:0% over um how<00:55:48.480> easy<00:55:48.599> is<00:55:48.839> it<00:55:49.020> actually<00:55:49.200> to 00:55:51.410 --> 00:55:51.420 align:start position:0% um how easy is it actually to 00:55:51.420 --> 00:55:55.130 align:start position:0% um how easy is it actually to um<00:55:51.480> stack<00:55:51.720> these<00:55:52.020> things 00:55:55.130 --> 00:55:55.140 align:start position:0% 00:55:55.140 --> 00:55:57.470 align:start position:0% okay<00:55:55.619> and<00:55:56.220> full<00:55:56.819> circle<00:55:57.000> back<00:55:57.300> to<00:55:57.359> the 00:55:57.470 --> 00:55:57.480 align:start position:0% okay and full circle back to the 00:55:57.480 --> 00:55:59.750 align:start position:0% okay and full circle back to the prisoner<00:55:57.780> dilemma<00:55:58.200> again<00:55:58.740> I<00:55:59.220> already<00:55:59.339> alluded 00:55:59.750 --> 00:55:59.760 align:start position:0% prisoner dilemma again I already alluded 00:55:59.760 --> 00:56:01.670 align:start position:0% prisoner dilemma again I already alluded to<00:55:59.880> it<00:56:00.059> just<00:56:00.540> very<00:56:00.780> briefly<00:56:01.079> what<00:56:01.380> is<00:56:01.500> this 00:56:01.670 --> 00:56:01.680 align:start position:0% to it just very briefly what is this 00:56:01.680 --> 00:56:03.530 align:start position:0% to it just very briefly what is this actually<00:56:01.859> representing 00:56:03.530 --> 00:56:03.540 align:start position:0% actually representing 00:56:03.540 --> 00:56:05.450 align:start position:0% actually representing um<00:56:03.599> two<00:56:03.960> compositions<00:56:04.559> first<00:56:04.800> parallel<00:56:05.339> or 00:56:05.450 --> 00:56:05.460 align:start position:0% um two compositions first parallel or 00:56:05.460 --> 00:56:07.970 align:start position:0% um two compositions first parallel or simultaneous<00:56:05.940> between<00:56:06.180> P1<00:56:06.660> and<00:56:06.839> P2<00:56:07.140> and<00:56:07.859> then 00:56:07.970 --> 00:56:07.980 align:start position:0% simultaneous between P1 and P2 and then 00:56:07.980 --> 00:56:09.470 align:start position:0% simultaneous between P1 and P2 and then sequential 00:56:09.470 --> 00:56:09.480 align:start position:0% sequential 00:56:09.480 --> 00:56:11.990 align:start position:0% sequential um the<00:56:09.780> U<00:56:09.900> and<00:56:10.140> again<00:56:10.260> if<00:56:10.740> you<00:56:10.920> go<00:56:11.160> back<00:56:11.339> to<00:56:11.579> the 00:56:11.990 --> 00:56:12.000 align:start position:0% um the U and again if you go back to the 00:56:12.000 --> 00:56:13.849 align:start position:0% um the U and again if you go back to the parallel<00:56:12.300> composition<00:56:12.780> you<00:56:13.500> can<00:56:13.619> basically 00:56:13.849 --> 00:56:13.859 align:start position:0% parallel composition you can basically 00:56:13.859 --> 00:56:16.130 align:start position:0% parallel composition you can basically think<00:56:14.099> I'm<00:56:14.460> first<00:56:14.780> composing<00:56:15.780> the<00:56:15.960> two 00:56:16.130 --> 00:56:16.140 align:start position:0% think I'm first composing the two 00:56:16.140 --> 00:56:17.930 align:start position:0% think I'm first composing the two players<00:56:16.500> in<00:56:16.740> parallel<00:56:17.040> into<00:56:17.280> again<00:56:17.640> this 00:56:17.930 --> 00:56:17.940 align:start position:0% players in parallel into again this 00:56:17.940 --> 00:56:20.170 align:start position:0% players in parallel into again this shape<00:56:18.240> and<00:56:18.900> then<00:56:19.020> I'm<00:56:19.140> composing<00:56:19.680> that<00:56:19.920> one 00:56:20.170 --> 00:56:20.180 align:start position:0% shape and then I'm composing that one 00:56:20.180 --> 00:56:23.690 align:start position:0% shape and then I'm composing that one sequentially<00:56:21.319> with<00:56:22.319> the<00:56:22.680> utility<00:56:23.220> function 00:56:23.690 --> 00:56:23.700 align:start position:0% sequentially with the utility function 00:56:23.700 --> 00:56:25.670 align:start position:0% sequentially with the utility function of<00:56:23.819> the<00:56:23.940> payoff<00:56:24.240> function 00:56:25.670 --> 00:56:25.680 align:start position:0% of the payoff function 00:56:25.680 --> 00:56:28.010 align:start position:0% of the payoff function okay 00:56:28.010 --> 00:56:28.020 align:start position:0% okay 00:56:28.020 --> 00:56:34.010 align:start position:0% okay questions<00:56:28.559> so<00:56:29.040> far 00:56:34.010 --> 00:56:34.020 align:start position:0% 00:56:34.020 --> 00:56:36.109 align:start position:0% can<00:56:34.680> you<00:56:34.800> explain<00:56:34.920> why<00:56:35.220> the<00:56:35.400> utility<00:56:35.700> function 00:56:36.109 --> 00:56:36.119 align:start position:0% can you explain why the utility function 00:56:36.119 --> 00:56:38.750 align:start position:0% can you explain why the utility function is<00:56:36.240> applied<00:56:36.599> sequentially 00:56:38.750 --> 00:56:38.760 align:start position:0% is applied sequentially 00:56:38.760 --> 00:56:39.589 align:start position:0% is applied sequentially um 00:56:39.589 --> 00:56:39.599 align:start position:0% um 00:56:39.599 --> 00:56:42.470 align:start position:0% um yes<00:56:40.140> in<00:56:40.380> a<00:56:40.500> sense<00:56:40.619> of 00:56:42.470 --> 00:56:42.480 align:start position:0% yes in a sense of 00:56:42.480 --> 00:56:44.750 align:start position:0% yes in a sense of the<00:56:43.079> the<00:56:43.140> utility<00:56:43.920> function<00:56:44.280> essentially<00:56:44.640> is 00:56:44.750 --> 00:56:44.760 align:start position:0% the the utility function essentially is 00:56:44.760 --> 00:56:46.790 align:start position:0% the the utility function essentially is just<00:56:44.880> a<00:56:45.059> computation<00:56:45.480> right<00:56:45.839> so<00:56:46.319> it's<00:56:46.440> waiting 00:56:46.790 --> 00:56:46.800 align:start position:0% just a computation right so it's waiting 00:56:46.800 --> 00:56:48.650 align:start position:0% just a computation right so it's waiting there<00:56:46.920> for<00:56:47.160> you<00:56:47.339> and<00:56:47.760> it's<00:56:47.880> waiting<00:56:48.180> for<00:56:48.359> two 00:56:48.650 --> 00:56:48.660 align:start position:0% there for you and it's waiting for two 00:56:48.660 --> 00:56:50.750 align:start position:0% there for you and it's waiting for two actions<00:56:49.319> One<00:56:49.800> Way<00:56:50.040> player<00:56:50.339> one<00:56:50.460> and<00:56:50.579> remember 00:56:50.750 --> 00:56:50.760 align:start position:0% actions One Way player one and remember 00:56:50.760 --> 00:56:53.270 align:start position:0% actions One Way player one and remember player<00:56:51.180> two<00:56:51.300> so<00:56:51.660> it<00:56:51.780> has<00:56:51.960> to<00:56:52.079> wait<00:56:52.260> until<00:56:52.859> these 00:56:53.270 --> 00:56:53.280 align:start position:0% player two so it has to wait until these 00:56:53.280 --> 00:56:54.829 align:start position:0% player two so it has to wait until these action<00:56:53.460> these<00:56:53.940> actions<00:56:54.180> realize<00:56:54.540> in<00:56:54.720> that 00:56:54.829 --> 00:56:54.839 align:start position:0% action these actions realize in that 00:56:54.839 --> 00:56:56.630 align:start position:0% action these actions realize in that sense<00:56:55.020> it's<00:56:55.200> sequential<00:56:56.040> in<00:56:56.460> the 00:56:56.630 --> 00:56:56.640 align:start position:0% sense it's sequential in the 00:56:56.640 --> 00:56:58.010 align:start position:0% sense it's sequential in the implementation<00:56:57.000> that<00:56:57.180> I<00:56:57.359> that<00:56:57.599> I<00:56:57.780> show<00:56:57.839> you 00:56:58.010 --> 00:56:58.020 align:start position:0% implementation that I that I show you 00:56:58.020 --> 00:56:59.750 align:start position:0% implementation that I that I show you will<00:56:58.200> decide<00:56:58.500> this<00:56:58.680> directly<00:56:59.040> as<00:56:59.280> variable 00:56:59.750 --> 00:56:59.760 align:start position:0% will decide this directly as variable 00:56:59.760 --> 00:57:03.349 align:start position:0% will decide this directly as variable output<00:57:00.119> of<00:57:00.420> P1<00:57:00.839> being<00:57:01.140> fed<00:57:01.319> into<00:57:01.619> the<00:57:01.859> U<00:57:02.359> okay 00:57:03.349 --> 00:57:03.359 align:start position:0% output of P1 being fed into the U okay 00:57:03.359 --> 00:57:07.190 align:start position:0% output of P1 being fed into the U okay other<00:57:04.079> questions 00:57:07.190 --> 00:57:07.200 align:start position:0% 00:57:07.200 --> 00:57:09.410 align:start position:0% okay 00:57:09.410 --> 00:57:09.420 align:start position:0% okay 00:57:09.420 --> 00:57:11.270 align:start position:0% okay um implementation<00:57:10.020> first<00:57:10.740> a<00:57:10.980> bit<00:57:11.099> of<00:57:11.160> an 00:57:11.270 --> 00:57:11.280 align:start position:0% um implementation first a bit of an 00:57:11.280 --> 00:57:13.490 align:start position:0% um implementation first a bit of an overview 00:57:13.490 --> 00:57:13.500 align:start position:0% overview 00:57:13.500 --> 00:57:14.690 align:start position:0% overview so<00:57:13.800> what<00:57:13.980> is<00:57:14.099> actually<00:57:14.220> what<00:57:14.460> does<00:57:14.640> the 00:57:14.690 --> 00:57:14.700 align:start position:0% so what is actually what does the 00:57:14.700 --> 00:57:16.250 align:start position:0% so what is actually what does the implementation<00:57:15.119> actually<00:57:15.420> look<00:57:15.599> like<00:57:15.780> it's 00:57:16.250 --> 00:57:16.260 align:start position:0% implementation actually look like it's 00:57:16.260 --> 00:57:18.049 align:start position:0% implementation actually look like it's uh<00:57:16.559> the<00:57:16.859> main<00:57:16.980> specific<00:57:17.280> language<00:57:17.520> embedded 00:57:18.049 --> 00:57:18.059 align:start position:0% uh the main specific language embedded 00:57:18.059 --> 00:57:20.809 align:start position:0% uh the main specific language embedded in<00:57:18.180> Haskell 00:57:20.809 --> 00:57:20.819 align:start position:0% 00:57:20.819 --> 00:57:23.510 align:start position:0% uh<00:57:21.540> you<00:57:21.960> might<00:57:22.079> wonder<00:57:22.260> why<00:57:22.500> Haskell 00:57:23.510 --> 00:57:23.520 align:start position:0% uh you might wonder why Haskell 00:57:23.520 --> 00:57:25.309 align:start position:0% uh you might wonder why Haskell um<00:57:23.640> one<00:57:23.940> of<00:57:24.059> the<00:57:24.180> reasons<00:57:24.480> is<00:57:24.720> that<00:57:24.960> and 00:57:25.309 --> 00:57:25.319 align:start position:0% um one of the reasons is that and 00:57:25.319 --> 00:57:26.930 align:start position:0% um one of the reasons is that and repeats<00:57:25.859> are<00:57:25.920> already<00:57:25.980> status<00:57:26.280> as<00:57:26.640> well<00:57:26.760> as 00:57:26.930 --> 00:57:26.940 align:start position:0% repeats are already status as well as 00:57:26.940 --> 00:57:29.690 align:start position:0% repeats are already status as well as well<00:57:27.119> the<00:57:27.839> Optics<00:57:28.260> and<00:57:28.680> lenses<00:57:29.099> are<00:57:29.460> something 00:57:29.690 --> 00:57:29.700 align:start position:0% well the Optics and lenses are something 00:57:29.700 --> 00:57:31.430 align:start position:0% well the Optics and lenses are something that<00:57:29.940> exist<00:57:30.359> and<00:57:31.020> you<00:57:31.140> can<00:57:31.260> build 00:57:31.430 --> 00:57:31.440 align:start position:0% that exist and you can build 00:57:31.440 --> 00:57:33.230 align:start position:0% that exist and you can build implementation<00:57:32.040> basically<00:57:32.460> on<00:57:32.640> pre-existing 00:57:33.230 --> 00:57:33.240 align:start position:0% implementation basically on pre-existing 00:57:33.240 --> 00:57:34.790 align:start position:0% implementation basically on pre-existing structures<00:57:33.540> in<00:57:33.720> Hesco<00:57:34.079> which<00:57:34.500> is<00:57:34.619> nice 00:57:34.790 --> 00:57:34.800 align:start position:0% structures in Hesco which is nice 00:57:34.800 --> 00:57:36.049 align:start position:0% structures in Hesco which is nice because 00:57:36.049 --> 00:57:36.059 align:start position:0% because 00:57:36.059 --> 00:57:37.490 align:start position:0% because um your<00:57:36.300> theory<00:57:36.660> has<00:57:37.079> a<00:57:37.260> direct 00:57:37.490 --> 00:57:37.500 align:start position:0% um your theory has a direct 00:57:37.500 --> 00:57:39.530 align:start position:0% um your theory has a direct correspondence<00:57:38.160> to<00:57:38.400> the<00:57:38.520> elements<00:57:38.940> that<00:57:39.420> you 00:57:39.530 --> 00:57:39.540 align:start position:0% correspondence to the elements that you 00:57:39.540 --> 00:57:40.970 align:start position:0% correspondence to the elements that you use<00:57:39.660> for<00:57:39.900> the<00:57:40.020> implementation<00:57:40.500> in<00:57:40.920> other 00:57:40.970 --> 00:57:40.980 align:start position:0% use for the implementation in other 00:57:40.980 --> 00:57:42.349 align:start position:0% use for the implementation in other words<00:57:41.160> it<00:57:41.339> makes<00:57:41.460> it<00:57:41.579> also<00:57:41.819> easier<00:57:42.059> to<00:57:42.180> control 00:57:42.349 --> 00:57:42.359 align:start position:0% words it makes it also easier to control 00:57:42.359 --> 00:57:43.790 align:start position:0% words it makes it also easier to control that<00:57:42.660> your<00:57:42.839> implementation<00:57:43.319> actually<00:57:43.559> is 00:57:43.790 --> 00:57:43.800 align:start position:0% that your implementation actually is 00:57:43.800 --> 00:57:45.470 align:start position:0% that your implementation actually is correct 00:57:45.470 --> 00:57:45.480 align:start position:0% correct 00:57:45.480 --> 00:57:47.510 align:start position:0% correct okay<00:57:46.079> another<00:57:46.440> thing<00:57:46.740> which<00:57:46.980> is<00:57:47.099> quite<00:57:47.220> useful 00:57:47.510 --> 00:57:47.520 align:start position:0% okay another thing which is quite useful 00:57:47.520 --> 00:57:49.309 align:start position:0% okay another thing which is quite useful the<00:57:47.700> typing<00:57:48.000> system<00:57:48.119> of<00:57:48.359> Haskell<00:57:48.720> is<00:57:49.319> um 00:57:49.309 --> 00:57:49.319 align:start position:0% the typing system of Haskell is um 00:57:49.319 --> 00:57:50.150 align:start position:0% the typing system of Haskell is um actually 00:57:50.150 --> 00:57:50.160 align:start position:0% actually 00:57:50.160 --> 00:57:51.290 align:start position:0% actually um can<00:57:50.400> be 00:57:51.290 --> 00:57:51.300 align:start position:0% um can be 00:57:51.300 --> 00:57:53.030 align:start position:0% um can be well<00:57:51.720> sometimes<00:57:51.960> your<00:57:52.140> enemy<00:57:52.500> but<00:57:52.619> sometimes 00:57:53.030 --> 00:57:53.040 align:start position:0% well sometimes your enemy but sometimes 00:57:53.040 --> 00:57:54.829 align:start position:0% well sometimes your enemy but sometimes also<00:57:53.339> your<00:57:53.460> friend<00:57:53.700> if<00:57:54.300> you<00:57:54.420> have<00:57:54.540> larger 00:57:54.829 --> 00:57:54.839 align:start position:0% also your friend if you have larger 00:57:54.839 --> 00:57:57.230 align:start position:0% also your friend if you have larger components<00:57:55.319> larger<00:57:55.859> operations<00:57:56.760> and<00:57:57.059> you 00:57:57.230 --> 00:57:57.240 align:start position:0% components larger operations and you 00:57:57.240 --> 00:57:59.210 align:start position:0% components larger operations and you wonder<00:57:57.359> what<00:57:58.140> inputs<00:57:58.559> if<00:57:58.680> you<00:57:58.800> want<00:57:58.920> to<00:57:58.980> query 00:57:59.210 --> 00:57:59.220 align:start position:0% wonder what inputs if you want to query 00:57:59.220 --> 00:58:01.430 align:start position:0% wonder what inputs if you want to query games<00:57:59.400> do<00:57:59.640> I<00:57:59.819> actually<00:57:59.880> have<00:58:00.059> to<00:58:00.240> supply<00:58:00.440> the 00:58:01.430 --> 00:58:01.440 align:start position:0% games do I actually have to supply the 00:58:01.440 --> 00:58:02.990 align:start position:0% games do I actually have to supply the type<00:58:01.619> system<00:58:01.859> is<00:58:02.099> quite<00:58:02.220> useful<00:58:02.520> because<00:58:02.700> it 00:58:02.990 --> 00:58:03.000 align:start position:0% type system is quite useful because it 00:58:03.000 --> 00:58:04.790 align:start position:0% type system is quite useful because it can<00:58:03.240> it<00:58:03.480> infers<00:58:03.839> the<00:58:04.020> types<00:58:04.260> and<00:58:04.500> they<00:58:04.619> can 00:58:04.790 --> 00:58:04.800 align:start position:0% can it infers the types and they can 00:58:04.800 --> 00:58:06.770 align:start position:0% can it infers the types and they can tell<00:58:04.980> you<00:58:05.099> your<00:58:05.700> strategy<00:58:06.119> that<00:58:06.420> you<00:58:06.540> have<00:58:06.660> to 00:58:06.770 --> 00:58:06.780 align:start position:0% tell you your strategy that you have to 00:58:06.780 --> 00:58:08.990 align:start position:0% tell you your strategy that you have to supply<00:58:06.960> has<00:58:07.440> the<00:58:07.740> following<00:58:08.099> type<00:58:08.280> right<00:58:08.700> it 00:58:08.990 --> 00:58:09.000 align:start position:0% supply has the following type right it 00:58:09.000 --> 00:58:11.390 align:start position:0% supply has the following type right it has<00:58:09.119> it's<00:58:09.300> a<00:58:09.540> tuple<00:58:09.780> of<00:58:09.960> double<00:58:10.260> pool<00:58:10.800> or<00:58:11.160> maybe 00:58:11.390 --> 00:58:11.400 align:start position:0% has it's a tuple of double pool or maybe 00:58:11.400 --> 00:58:13.010 align:start position:0% has it's a tuple of double pool or maybe something<00:58:11.579> much<00:58:11.819> more<00:58:12.000> complicated 00:58:13.010 --> 00:58:13.020 align:start position:0% something much more complicated 00:58:13.020 --> 00:58:14.690 align:start position:0% something much more complicated this<00:58:13.440> sounds<00:58:13.619> at<00:58:13.800> the<00:58:13.920> beginning<00:58:13.980> kind<00:58:14.339> of<00:58:14.460> bit 00:58:14.690 --> 00:58:14.700 align:start position:0% this sounds at the beginning kind of bit 00:58:14.700 --> 00:58:16.309 align:start position:0% this sounds at the beginning kind of bit you<00:58:15.000> know<00:58:15.000> why<00:58:15.119> are<00:58:15.300> you<00:58:15.300> in<00:58:15.420> beneath<00:58:15.780> yet<00:58:15.900> why 00:58:16.309 --> 00:58:16.319 align:start position:0% you know why are you in beneath yet why 00:58:16.319 --> 00:58:17.809 align:start position:0% you know why are you in beneath yet why would<00:58:16.440> you<00:58:16.559> need<00:58:16.680> that<00:58:16.859> but<00:58:17.280> the<00:58:17.400> more<00:58:17.579> complex 00:58:17.809 --> 00:58:17.819 align:start position:0% would you need that but the more complex 00:58:17.819 --> 00:58:20.210 align:start position:0% would you need that but the more complex your<00:58:18.000> scenarios<00:58:18.480> are<00:58:18.780> the<00:58:19.440> more<00:58:19.680> useful<00:58:19.980> these 00:58:20.210 --> 00:58:20.220 align:start position:0% your scenarios are the more useful these 00:58:20.220 --> 00:58:21.650 align:start position:0% your scenarios are the more useful these properties<00:58:20.520> and<00:58:20.880> these<00:58:21.119> this<00:58:21.240> functionality 00:58:21.650 --> 00:58:21.660 align:start position:0% properties and these this functionality 00:58:21.660 --> 00:58:23.450 align:start position:0% properties and these this functionality actually<00:58:21.960> is 00:58:23.450 --> 00:58:23.460 align:start position:0% actually is 00:58:23.460 --> 00:58:25.970 align:start position:0% actually is okay<00:58:24.119> this<00:58:24.839> is<00:58:24.960> under<00:58:25.140> active<00:58:25.559> development 00:58:25.970 --> 00:58:25.980 align:start position:0% okay this is under active development 00:58:25.980 --> 00:58:27.589 align:start position:0% okay this is under active development it's<00:58:26.400> under<00:58:26.640> the<00:58:26.819> active<00:58:27.059> development<00:58:27.420> from 00:58:27.589 --> 00:58:27.599 align:start position:0% it's under the active development from 00:58:27.599 --> 00:58:29.150 align:start position:0% it's under the active development from two<00:58:27.839> sides<00:58:28.260> from<00:58:28.619> the<00:58:28.740> programming 00:58:29.150 --> 00:58:29.160 align:start position:0% two sides from the programming 00:58:29.160 --> 00:58:30.710 align:start position:0% two sides from the programming perspective<00:58:29.520> of<00:58:29.940> things<00:58:30.059> we<00:58:30.300> you<00:58:30.480> know<00:58:30.599> we 00:58:30.710 --> 00:58:30.720 align:start position:0% perspective of things we you know we 00:58:30.720 --> 00:58:31.910 align:start position:0% perspective of things we you know we feel<00:58:30.780> like<00:58:30.960> features<00:58:31.260> that<00:58:31.440> we<00:58:31.559> want<00:58:31.680> and<00:58:31.800> we 00:58:31.910 --> 00:58:31.920 align:start position:0% feel like features that we want and we 00:58:31.920 --> 00:58:34.069 align:start position:0% feel like features that we want and we want<00:58:32.040> to<00:58:32.160> implement<00:58:32.400> but<00:58:33.300> also<00:58:33.540> the<00:58:33.720> theory<00:58:33.960> is 00:58:34.069 --> 00:58:34.079 align:start position:0% want to implement but also the theory is 00:58:34.079 --> 00:58:35.809 align:start position:0% want to implement but also the theory is continuously<00:58:34.559> developed<00:58:34.980> right<00:58:35.400> this<00:58:35.700> is 00:58:35.809 --> 00:58:35.819 align:start position:0% continuously developed right this is 00:58:35.819 --> 00:58:37.670 align:start position:0% continuously developed right this is something<00:58:35.940> I<00:58:36.180> will<00:58:36.299> come<00:58:36.480> back<00:58:36.599> to 00:58:37.670 --> 00:58:37.680 align:start position:0% something I will come back to 00:58:37.680 --> 00:58:41.210 align:start position:0% something I will come back to um at<00:58:37.920> the<00:58:38.040> end<00:58:38.099> if<00:58:38.400> I<00:58:38.640> have<00:58:38.700> time 00:58:41.210 --> 00:58:41.220 align:start position:0% 00:58:41.220 --> 00:58:42.650 align:start position:0% okay<00:58:41.460> we<00:58:41.760> are<00:58:41.880> using<00:58:42.119> it<00:58:42.240> for<00:58:42.359> a<00:58:42.480> couple<00:58:42.540> of 00:58:42.650 --> 00:58:42.660 align:start position:0% okay we are using it for a couple of 00:58:42.660 --> 00:58:43.789 align:start position:0% okay we are using it for a couple of things 00:58:43.789 --> 00:58:43.799 align:start position:0% things 00:58:43.799 --> 00:58:46.309 align:start position:0% things um staking<00:58:44.460> protocols<00:58:45.180> an<00:58:45.599> example<00:58:45.900> a<00:58:46.079> simple 00:58:46.309 --> 00:58:46.319 align:start position:0% um staking protocols an example a simple 00:58:46.319 --> 00:58:48.170 align:start position:0% um staking protocols an example a simple example<00:58:46.619> you<00:58:46.799> will<00:58:46.920> see<00:58:47.040> today<00:58:47.220> token<00:58:48.000> design 00:58:48.170 --> 00:58:48.180 align:start position:0% example you will see today token design 00:58:48.180 --> 00:58:49.910 align:start position:0% example you will see today token design and<00:58:48.720> there<00:58:48.960> are<00:58:49.079> also<00:58:49.319> applications<00:58:49.680> outside 00:58:49.910 --> 00:58:49.920 align:start position:0% and there are also applications outside 00:58:49.920 --> 00:58:52.490 align:start position:0% and there are also applications outside of<00:58:50.160> crypto 00:58:52.490 --> 00:58:52.500 align:start position:0% of crypto 00:58:52.500 --> 00:58:53.569 align:start position:0% of crypto good 00:58:53.569 --> 00:58:53.579 align:start position:0% good 00:58:53.579 --> 00:58:55.430 align:start position:0% good the<00:58:54.119> first<00:58:54.299> thing<00:58:54.480> we<00:58:54.599> want<00:58:54.780> to<00:58:54.839> focus<00:58:55.020> on<00:58:55.200> how 00:58:55.430 --> 00:58:55.440 align:start position:0% the first thing we want to focus on how 00:58:55.440 --> 00:58:56.630 align:start position:0% the first thing we want to focus on how does<00:58:55.559> the<00:58:55.740> engine<00:58:55.859> actually<00:58:56.099> work<00:58:56.339> in<00:58:56.520> the 00:58:56.630 --> 00:58:56.640 align:start position:0% does the engine actually work in the 00:58:56.640 --> 00:58:58.549 align:start position:0% does the engine actually work in the sense<00:58:56.760> of<00:58:56.940> how<00:58:57.299> do<00:58:57.420> we<00:58:57.540> represent<00:58:57.900> games<00:58:58.140> how 00:58:58.549 --> 00:58:58.559 align:start position:0% sense of how do we represent games how 00:58:58.559 --> 00:59:01.490 align:start position:0% sense of how do we represent games how does<00:58:58.680> this<00:58:58.859> work 00:59:01.490 --> 00:59:01.500 align:start position:0% 00:59:01.500 --> 00:59:03.530 align:start position:0% all<00:59:01.859> right<00:59:02.040> so<00:59:02.460> on<00:59:02.579> the<00:59:02.760> left<00:59:02.880> you<00:59:03.299> can<00:59:03.420> see 00:59:03.530 --> 00:59:03.540 align:start position:0% all right so on the left you can see 00:59:03.540 --> 00:59:05.809 align:start position:0% all right so on the left you can see again<00:59:03.720> the<00:59:04.020> the<00:59:04.380> game<00:59:04.619> with<00:59:05.160> the<00:59:05.339> inputs<00:59:05.700> and 00:59:05.809 --> 00:59:05.819 align:start position:0% again the the game with the inputs and 00:59:05.819 --> 00:59:07.910 align:start position:0% again the the game with the inputs and outputs<00:59:06.240> on<00:59:06.900> the<00:59:07.020> right<00:59:07.140> hand<00:59:07.319> right<00:59:07.799> hand 00:59:07.910 --> 00:59:07.920 align:start position:0% outputs on the right hand right hand 00:59:07.920 --> 00:59:09.349 align:start position:0% outputs on the right hand right hand side<00:59:08.040> you<00:59:08.220> basically<00:59:08.520> see<00:59:08.700> the<00:59:08.880> syntactic 00:59:09.349 --> 00:59:09.359 align:start position:0% side you basically see the syntactic 00:59:09.359 --> 00:59:10.490 align:start position:0% side you basically see the syntactic expression 00:59:10.490 --> 00:59:10.500 align:start position:0% expression 00:59:10.500 --> 00:59:11.150 align:start position:0% expression um 00:59:11.150 --> 00:59:11.160 align:start position:0% um 00:59:11.160 --> 00:59:13.309 align:start position:0% um which<00:59:11.579> is<00:59:11.700> basically<00:59:12.059> this<00:59:12.420> square<00:59:12.900> bracket 00:59:13.309 --> 00:59:13.319 align:start position:0% which is basically this square bracket 00:59:13.319 --> 00:59:15.770 align:start position:0% which is basically this square bracket open<00:59:13.500> game<00:59:13.799> and<00:59:14.339> then<00:59:14.460> what<00:59:14.700> follows<00:59:15.119> until 00:59:15.770 --> 00:59:15.780 align:start position:0% open game and then what follows until 00:59:15.780 --> 00:59:17.329 align:start position:0% open game and then what follows until the<00:59:16.079> the<00:59:16.260> last<00:59:16.440> square<00:59:16.799> bracket<00:59:17.160> that 00:59:17.329 --> 00:59:17.339 align:start position:0% the the last square bracket that 00:59:17.339 --> 00:59:19.670 align:start position:0% the the last square bracket that internally<00:59:17.760> is<00:59:18.119> basically<00:59:18.540> the<00:59:18.720> DSL<00:59:19.200> and 00:59:19.670 --> 00:59:19.680 align:start position:0% internally is basically the DSL and 00:59:19.680 --> 00:59:22.190 align:start position:0% internally is basically the DSL and telling<00:59:20.099> here<00:59:20.880> is<00:59:21.059> a<00:59:21.240> game<00:59:21.359> coming<00:59:21.599> with<00:59:22.020> a 00:59:22.190 --> 00:59:22.200 align:start position:0% telling here is a game coming with a 00:59:22.200 --> 00:59:23.450 align:start position:0% telling here is a game coming with a certain<00:59:22.319> shape 00:59:23.450 --> 00:59:23.460 align:start position:0% certain shape 00:59:23.460 --> 00:59:25.309 align:start position:0% certain shape okay<00:59:24.480> um<00:59:24.540> there<00:59:24.780> is<00:59:24.900> what<00:59:25.079> is<00:59:25.200> called 00:59:25.309 --> 00:59:25.319 align:start position:0% okay um there is what is called 00:59:25.319 --> 00:59:27.049 align:start position:0% okay um there is what is called internals<00:59:25.859> of<00:59:25.920> G<00:59:26.099> between<00:59:26.339> the<00:59:26.579> dashed<00:59:26.880> lines 00:59:27.049 --> 00:59:27.059 align:start position:0% internals of G between the dashed lines 00:59:27.059 --> 00:59:28.670 align:start position:0% internals of G between the dashed lines I<00:59:27.480> will<00:59:27.660> say<00:59:27.780> something<00:59:27.960> about<00:59:28.200> this<00:59:28.380> in<00:59:28.559> a 00:59:28.670 --> 00:59:28.680 align:start position:0% I will say something about this in a 00:59:28.680 --> 00:59:30.470 align:start position:0% I will say something about this in a minute<00:59:28.799> first<00:59:29.460> what<00:59:29.760> you<00:59:29.940> should<00:59:30.059> see<00:59:30.240> is 00:59:30.470 --> 00:59:30.480 align:start position:0% minute first what you should see is 00:59:30.480 --> 00:59:32.870 align:start position:0% minute first what you should see is there<00:59:31.200> are<00:59:31.380> four<00:59:31.500> Fields<00:59:31.859> inputs<00:59:32.520> feedback 00:59:32.870 --> 00:59:32.880 align:start position:0% there are four Fields inputs feedback 00:59:32.880 --> 00:59:34.849 align:start position:0% there are four Fields inputs feedback output<00:59:33.359> returns<00:59:33.900> and<00:59:34.319> they<00:59:34.440> exactly 00:59:34.849 --> 00:59:34.859 align:start position:0% output returns and they exactly 00:59:34.859 --> 00:59:37.490 align:start position:0% output returns and they exactly correspond<00:59:35.280> to<00:59:35.400> the<00:59:35.579> wires<00:59:35.940> so<00:59:36.660> you<00:59:37.260> can<00:59:37.319> see 00:59:37.490 --> 00:59:37.500 align:start position:0% correspond to the wires so you can see 00:59:37.500 --> 00:59:40.490 align:start position:0% correspond to the wires so you can see this<00:59:37.740> as<00:59:37.980> basically<00:59:38.400> a<00:59:39.240> way<00:59:39.359> of<00:59:39.540> expressing<00:59:40.079> a 00:59:40.490 --> 00:59:40.500 align:start position:0% this as basically a way of expressing a 00:59:40.500 --> 00:59:42.890 align:start position:0% this as basically a way of expressing a two-dimensional<00:59:41.099> element<00:59:41.640> kind<00:59:42.599> of<00:59:42.720> language 00:59:42.890 --> 00:59:42.900 align:start position:0% two-dimensional element kind of language 00:59:42.900 --> 00:59:46.789 align:start position:0% two-dimensional element kind of language into<00:59:43.319> on<00:59:44.160> the<00:59:44.400> the<00:59:44.880> language<00:59:45.780> or<00:59:46.440> the<00:59:46.559> the 00:59:46.789 --> 00:59:46.799 align:start position:0% into on the the language or the the 00:59:46.799 --> 00:59:48.829 align:start position:0% into on the the language or the the programming<00:59:47.160> syntax<00:59:47.460> in<00:59:47.640> within<00:59:47.940> Haskell 00:59:48.829 --> 00:59:48.839 align:start position:0% programming syntax in within Haskell 00:59:48.839 --> 00:59:50.450 align:start position:0% programming syntax in within Haskell so<00:59:49.260> the<00:59:49.440> inputs<00:59:49.799> are<00:59:49.980> just<00:59:50.099> the<00:59:50.339> outside 00:59:50.450 --> 00:59:50.460 align:start position:0% so the inputs are just the outside 00:59:50.460 --> 00:59:52.370 align:start position:0% so the inputs are just the outside system<00:59:51.059> another<00:59:51.660> way<00:59:51.900> to<00:59:51.960> think<00:59:52.079> about<00:59:52.200> this 00:59:52.370 --> 00:59:52.380 align:start position:0% system another way to think about this 00:59:52.380 --> 00:59:54.650 align:start position:0% system another way to think about this box<00:59:52.559> essentially<00:59:53.040> is<00:59:53.280> each<00:59:53.880> open<00:59:54.180> game<00:59:54.420> is 00:59:54.650 --> 00:59:54.660 align:start position:0% box essentially is each open game is 00:59:54.660 --> 00:59:56.390 align:start position:0% box essentially is each open game is almost<00:59:54.839> like<00:59:55.020> an<00:59:55.200> interface<00:59:55.619> right<00:59:55.980> you<00:59:56.220> have 00:59:56.390 --> 00:59:56.400 align:start position:0% almost like an interface right you have 00:59:56.400 --> 00:59:58.370 align:start position:0% almost like an interface right you have something<00:59:56.579> internally<00:59:57.059> happen<00:59:57.359> but<00:59:58.079> to<00:59:58.260> the 00:59:58.370 --> 00:59:58.380 align:start position:0% something internally happen but to the 00:59:58.380 --> 00:59:59.990 align:start position:0% something internally happen but to the outside<00:59:58.440> world<00:59:58.799> is<00:59:59.040> somehow<00:59:59.280> it<00:59:59.460> is<01:00:00.000> um 00:59:59.990 --> 01:00:00.000 align:start position:0% outside world is somehow it is um 01:00:00.000 --> 01:00:02.089 align:start position:0% outside world is somehow it is um connected<01:00:00.480> or<01:00:00.900> maybe<01:00:01.020> not<01:00:01.260> connected<01:00:01.680> through 01:00:02.089 --> 01:00:02.099 align:start position:0% connected or maybe not connected through 01:00:02.099 --> 01:00:06.109 align:start position:0% connected or maybe not connected through its<01:00:02.339> interface<01:00:02.640> that<01:00:02.880> it<01:00:03.059> offers 01:00:06.109 --> 01:00:06.119 align:start position:0% 01:00:06.119 --> 01:00:08.390 align:start position:0% what<01:00:06.480> happens<01:00:06.599> internally<01:00:07.200> internally<01:00:08.160> is 01:00:08.390 --> 01:00:08.400 align:start position:0% what happens internally internally is 01:00:08.400 --> 01:00:10.250 align:start position:0% what happens internally internally is where<01:00:08.640> the<01:00:08.819> place<01:00:09.000> of<01:00:09.240> credit<01:00:09.420> information<01:00:09.780> is 01:00:10.250 --> 01:00:10.260 align:start position:0% where the place of credit information is 01:00:10.260 --> 01:00:13.190 align:start position:0% where the place of credit information is generated<01:00:10.920> so<01:00:11.760> insights<01:00:12.299> of<01:00:12.480> these<01:00:12.780> dashed 01:00:13.190 --> 01:00:13.200 align:start position:0% generated so insights of these dashed 01:00:13.200 --> 01:00:15.049 align:start position:0% generated so insights of these dashed lines<01:00:13.380> there<01:00:13.740> are<01:00:13.859> what<01:00:14.099> we<01:00:14.220> call<01:00:14.339> line<01:00:14.579> blocks 01:00:15.049 --> 01:00:15.059 align:start position:0% lines there are what we call line blocks 01:00:15.059 --> 01:00:17.210 align:start position:0% lines there are what we call line blocks these<01:00:15.420> are<01:00:15.540> five<01:00:16.260> lines<01:00:16.619> basically<01:00:16.980> there 01:00:17.210 --> 01:00:17.220 align:start position:0% these are five lines basically there 01:00:17.220 --> 01:00:19.490 align:start position:0% these are five lines basically there could<01:00:17.339> be<01:00:17.460> many<01:00:17.579> of<01:00:17.760> them 01:00:19.490 --> 01:00:19.500 align:start position:0% could be many of them 01:00:19.500 --> 01:00:21.470 align:start position:0% could be many of them um<01:00:19.619> they<01:00:19.920> roughly<01:00:20.220> correspond<01:00:20.700> again<01:00:20.940> or 01:00:21.470 --> 01:00:21.480 align:start position:0% um they roughly correspond again or 01:00:21.480 --> 01:00:24.530 align:start position:0% um they roughly correspond again or mirror<01:00:21.960> the<01:00:22.140> outside<01:00:22.500> wires<01:00:23.339> so<01:00:23.940> inputs 01:00:24.530 --> 01:00:24.540 align:start position:0% mirror the outside wires so inputs 01:00:24.540 --> 01:00:26.630 align:start position:0% mirror the outside wires so inputs feedback<01:00:24.839> output<01:00:25.200> returns<01:00:25.740> and<01:00:26.400> then<01:00:26.520> there 01:00:26.630 --> 01:00:26.640 align:start position:0% feedback output returns and then there 01:00:26.640 --> 01:00:27.829 align:start position:0% feedback output returns and then there is<01:00:26.760> an<01:00:26.819> additional<01:00:27.119> field<01:00:27.299> which<01:00:27.540> is<01:00:27.720> the 01:00:27.829 --> 01:00:27.839 align:start position:0% is an additional field which is the 01:00:27.839 --> 01:00:29.630 align:start position:0% is an additional field which is the operation<01:00:28.200> field<01:00:28.500> that<01:00:29.220> is<01:00:29.339> essentially 01:00:29.630 --> 01:00:29.640 align:start position:0% operation field that is essentially 01:00:29.640 --> 01:00:31.730 align:start position:0% operation field that is essentially where<01:00:29.819> information<01:00:30.059> is<01:00:30.420> created 01:00:31.730 --> 01:00:31.740 align:start position:0% where information is created 01:00:31.740 --> 01:00:33.770 align:start position:0% where information is created now<01:00:32.220> the<01:00:32.400> first<01:00:32.520> thing<01:00:32.640> to<01:00:32.760> observe<01:00:33.180> is<01:00:33.299> in<01:00:33.660> a 01:00:33.770 --> 01:00:33.780 align:start position:0% now the first thing to observe is in a 01:00:33.780 --> 01:00:35.089 align:start position:0% now the first thing to observe is in a simplest<01:00:34.140> game<01:00:34.260> if<01:00:34.500> I'm<01:00:34.619> just<01:00:34.799> talking<01:00:34.920> about 01:00:35.089 --> 01:00:35.099 align:start position:0% simplest game if I'm just talking about 01:00:35.099 --> 01:00:37.549 align:start position:0% simplest game if I'm just talking about one<01:00:35.520> single<01:00:35.760> player<01:00:36.059> making<01:00:36.240> a<01:00:36.420> decision<01:00:37.079> the 01:00:37.549 --> 01:00:37.559 align:start position:0% one single player making a decision the 01:00:37.559 --> 01:00:39.650 align:start position:0% one single player making a decision the input<01:00:37.799> X<01:00:38.040> could<01:00:38.400> be<01:00:38.579> exactly<01:00:39.000> linked<01:00:39.299> to<01:00:39.420> the 01:00:39.650 --> 01:00:39.660 align:start position:0% input X could be exactly linked to the 01:00:39.660 --> 01:00:41.390 align:start position:0% input X could be exactly linked to the outside<01:00:40.020> wire<01:00:40.380> X<01:00:40.619> that<01:00:40.920> I<01:00:41.040> showed<01:00:41.160> you<01:00:41.220> before 01:00:41.390 --> 01:00:41.400 align:start position:0% outside wire X that I showed you before 01:00:41.400 --> 01:00:43.309 align:start position:0% outside wire X that I showed you before and<01:00:41.640> it's<01:00:41.760> the<01:00:41.940> wire<01:00:42.059> going<01:00:42.299> out<01:00:42.480> or<01:00:43.079> actually 01:00:43.309 --> 01:00:43.319 align:start position:0% and it's the wire going out or actually 01:00:43.319 --> 01:00:47.390 align:start position:0% and it's the wire going out or actually coming<01:00:43.559> in<01:00:43.880> similarly<01:00:44.880> the<01:00:45.660> output<01:00:45.900> y 01:00:47.390 --> 01:00:47.400 align:start position:0% coming in similarly the output y 01:00:47.400 --> 01:00:48.109 align:start position:0% coming in similarly the output y um 01:00:48.109 --> 01:00:48.119 align:start position:0% um 01:00:48.119 --> 01:00:50.390 align:start position:0% um is<01:00:48.839> will<01:00:49.140> be<01:00:49.559> the<01:00:49.680> result<01:00:49.799> of<01:00:50.099> the<01:00:50.280> information 01:00:50.390 --> 01:00:50.400 align:start position:0% is will be the result of the information 01:00:50.400 --> 01:00:51.890 align:start position:0% is will be the result of the information that<01:00:50.700> is<01:00:50.880> created<01:00:51.119> and<01:00:51.359> will<01:00:51.480> be<01:00:51.660> directly 01:00:51.890 --> 01:00:51.900 align:start position:0% that is created and will be directly 01:00:51.900 --> 01:00:53.690 align:start position:0% that is created and will be directly pushed<01:00:52.260> outside<01:00:52.380> of<01:00:52.740> the<01:00:52.859> box 01:00:53.690 --> 01:00:53.700 align:start position:0% pushed outside of the box 01:00:53.700 --> 01:00:55.970 align:start position:0% pushed outside of the box however<01:00:54.240> this<01:00:55.079> is<01:00:55.319> not<01:00:55.380> this<01:00:55.680> is<01:00:55.859> not 01:00:55.970 --> 01:00:55.980 align:start position:0% however this is not this is not 01:00:55.980 --> 01:00:57.349 align:start position:0% however this is not this is not necessarily<01:00:56.339> the<01:00:56.520> case<01:00:56.700> in<01:00:57.000> the<01:00:57.059> sense<01:00:57.180> of 01:00:57.349 --> 01:00:57.359 align:start position:0% necessarily the case in the sense of 01:00:57.359 --> 01:00:58.609 align:start position:0% necessarily the case in the sense of there<01:00:57.540> could<01:00:57.720> be<01:00:57.839> more<01:00:57.960> line<01:00:58.140> blocks<01:00:58.440> there 01:00:58.609 --> 01:00:58.619 align:start position:0% there could be more line blocks there 01:00:58.619 --> 01:01:00.170 align:start position:0% there could be more line blocks there could<01:00:58.740> be<01:00:58.859> more<01:00:58.980> complicated<01:00:59.400> things<01:00:59.760> and 01:01:00.170 --> 01:01:00.180 align:start position:0% could be more complicated things and 01:01:00.180 --> 01:01:02.210 align:start position:0% could be more complicated things and some<01:01:00.359> of<01:01:00.480> these<01:01:00.780> inputs<01:01:01.380> and<01:01:01.559> output<01:01:01.799> fields 01:01:02.210 --> 01:01:02.220 align:start position:0% some of these inputs and output fields 01:01:02.220 --> 01:01:05.089 align:start position:0% some of these inputs and output fields and<01:01:02.339> so<01:01:02.460> on<01:01:02.579> could<01:01:03.059> be<01:01:03.240> just<01:01:03.900> totally<01:01:04.559> consumed 01:01:05.089 --> 01:01:05.099 align:start position:0% and so on could be just totally consumed 01:01:05.099 --> 01:01:07.069 align:start position:0% and so on could be just totally consumed inside<01:01:05.280> of<01:01:05.640> that<01:01:05.819> game<01:01:06.000> without<01:01:06.359> any<01:01:06.660> exposure 01:01:07.069 --> 01:01:07.079 align:start position:0% inside of that game without any exposure 01:01:07.079 --> 01:01:09.650 align:start position:0% inside of that game without any exposure to<01:01:07.260> the<01:01:07.380> outside<01:01:07.500> world 01:01:09.650 --> 01:01:09.660 align:start position:0% to the outside world 01:01:09.660 --> 01:01:12.349 align:start position:0% to the outside world okay<01:01:10.020> the<01:01:10.260> operation<01:01:10.799> can<01:01:11.160> be<01:01:11.400> two<01:01:12.119> things 01:01:12.349 --> 01:01:12.359 align:start position:0% okay the operation can be two things 01:01:12.359 --> 01:01:14.510 align:start position:0% okay the operation can be two things like<01:01:13.140> here<01:01:13.319> this<01:01:13.500> is<01:01:13.619> the<01:01:13.799> dependent<01:01:14.280> decision 01:01:14.510 --> 01:01:14.520 align:start position:0% like here this is the dependent decision 01:01:14.520 --> 01:01:16.010 align:start position:0% like here this is the dependent decision just<01:01:14.760> means<01:01:15.000> this<01:01:15.119> is<01:01:15.240> a<01:01:15.359> decision<01:01:15.599> operation 01:01:16.010 --> 01:01:16.020 align:start position:0% just means this is a decision operation 01:01:16.020 --> 01:01:18.109 align:start position:0% just means this is a decision operation so<01:01:16.440> one<01:01:16.680> player<01:01:16.980> makes<01:01:17.160> a<01:01:17.280> decision 01:01:18.109 --> 01:01:18.119 align:start position:0% so one player makes a decision 01:01:18.119 --> 01:01:20.690 align:start position:0% so one player makes a decision or<01:01:18.599> alternatively<01:01:19.200> a<01:01:19.559> computation<01:01:19.980> these<01:01:20.640> two 01:01:20.690 --> 01:01:20.700 align:start position:0% or alternatively a computation these two 01:01:20.700 --> 01:01:22.250 align:start position:0% or alternatively a computation these two building<01:01:20.940> blocks<01:01:21.359> either<01:01:21.720> you<01:01:22.020> don't<01:01:22.079> need 01:01:22.250 --> 01:01:22.260 align:start position:0% building blocks either you don't need 01:01:22.260 --> 01:01:23.750 align:start position:0% building blocks either you don't need more<01:01:22.440> if<01:01:22.740> you<01:01:22.859> have<01:01:22.980> that<01:01:23.160> you<01:01:23.339> can<01:01:23.460> basically 01:01:23.750 --> 01:01:23.760 align:start position:0% more if you have that you can basically 01:01:23.760 --> 01:01:25.730 align:start position:0% more if you have that you can basically build<01:01:24.000> the<01:01:24.780> most<01:01:24.900> complicated<01:01:25.319> model<01:01:25.559> you 01:01:25.730 --> 01:01:25.740 align:start position:0% build the most complicated model you 01:01:25.740 --> 01:01:28.309 align:start position:0% build the most complicated model you want 01:01:28.309 --> 01:01:28.319 align:start position:0% 01:01:28.319 --> 01:01:31.609 align:start position:0% okay<01:01:28.740> here's<01:01:29.280> the<01:01:29.400> prisoner<01:01:29.760> dilemma 01:01:31.609 --> 01:01:31.619 align:start position:0% okay here's the prisoner dilemma 01:01:31.619 --> 01:01:35.049 align:start position:0% okay here's the prisoner dilemma um<01:01:31.740> again<01:01:31.980> the<01:01:32.400> diagram<01:01:32.640> from<01:01:32.940> before 01:01:35.049 --> 01:01:35.059 align:start position:0% um again the diagram from before 01:01:35.059 --> 01:01:37.730 align:start position:0% um again the diagram from before first<01:01:36.059> you<01:01:36.660> can<01:01:36.780> see 01:01:37.730 --> 01:01:37.740 align:start position:0% first you can see 01:01:37.740 --> 01:01:39.349 align:start position:0% first you can see um if<01:01:37.920> you<01:01:38.040> look<01:01:38.160> at<01:01:38.339> the<01:01:38.460> left<01:01:38.579> hand<01:01:38.760> side<01:01:38.940> the 01:01:39.349 --> 01:01:39.359 align:start position:0% um if you look at the left hand side the 01:01:39.359 --> 01:01:40.910 align:start position:0% um if you look at the left hand side the outside<01:01:39.480> Fields<01:01:40.020> the<01:01:40.140> outside<01:01:40.260> interfaces 01:01:40.910 --> 01:01:40.920 align:start position:0% outside Fields the outside interfaces 01:01:40.920 --> 01:01:43.190 align:start position:0% outside Fields the outside interfaces here<01:01:41.220> are<01:01:42.119> empty 01:01:43.190 --> 01:01:43.200 align:start position:0% here are empty 01:01:43.200 --> 01:01:44.870 align:start position:0% here are empty this<01:01:43.680> tells<01:01:43.920> you<01:01:43.980> two<01:01:44.160> things<01:01:44.339> first<01:01:44.579> you 01:01:44.870 --> 01:01:44.880 align:start position:0% this tells you two things first you 01:01:44.880 --> 01:01:46.609 align:start position:0% this tells you two things first you don't<01:01:45.180> always<01:01:45.660> need<01:01:45.960> to<01:01:46.079> supply<01:01:46.260> information 01:01:46.609 --> 01:01:46.619 align:start position:0% don't always need to supply information 01:01:46.619 --> 01:01:48.890 align:start position:0% don't always need to supply information sometimes<01:01:47.520> the<01:01:47.700> games<01:01:47.940> don't<01:01:48.299> have<01:01:48.540> are<01:01:48.780> not 01:01:48.890 --> 01:01:48.900 align:start position:0% sometimes the games don't have are not 01:01:48.900 --> 01:01:50.569 align:start position:0% sometimes the games don't have are not connected<01:01:49.260> to<01:01:49.380> the<01:01:49.500> outside<01:01:49.559> world<01:01:49.920> or<01:01:50.339> only 01:01:50.569 --> 01:01:50.579 align:start position:0% connected to the outside world or only 01:01:50.579 --> 01:01:52.609 align:start position:0% connected to the outside world or only partly<01:01:51.299> connected 01:01:52.609 --> 01:01:52.619 align:start position:0% partly connected 01:01:52.619 --> 01:01:55.309 align:start position:0% partly connected and<01:01:53.040> internally<01:01:53.400> what<01:01:53.640> you<01:01:53.760> can<01:01:53.880> see<01:01:54.000> is 01:01:55.309 --> 01:01:55.319 align:start position:0% and internally what you can see is 01:01:55.319 --> 01:01:56.150 align:start position:0% and internally what you can see is um 01:01:56.150 --> 01:01:56.160 align:start position:0% um 01:01:56.160 --> 01:01:58.309 align:start position:0% um there<01:01:56.640> are<01:01:56.760> three<01:01:56.880> line<01:01:57.059> blocks<01:01:57.540> the<01:01:58.200> first 01:01:58.309 --> 01:01:58.319 align:start position:0% there are three line blocks the first 01:01:58.319 --> 01:02:00.109 align:start position:0% there are three line blocks the first one<01:01:58.440> the<01:01:58.680> second<01:01:58.799> one<01:01:59.040> and<01:01:59.520> the<01:01:59.700> first<01:01:59.819> and<01:02:00.000> the 01:02:00.109 --> 01:02:00.119 align:start position:0% one the second one and the first and the 01:02:00.119 --> 01:02:01.490 align:start position:0% one the second one and the first and the second<01:02:00.240> basically<01:02:00.660> are<01:02:00.900> player<01:02:01.260> one<01:02:01.319> and 01:02:01.490 --> 01:02:01.500 align:start position:0% second basically are player one and 01:02:01.500 --> 01:02:02.569 align:start position:0% second basically are player one and player<01:02:01.740> two 01:02:02.569 --> 01:02:02.579 align:start position:0% player two 01:02:02.579 --> 01:02:04.970 align:start position:0% player two again<01:02:03.180> for<01:02:04.020> both<01:02:04.200> of<01:02:04.319> them<01:02:04.440> they<01:02:04.799> don't 01:02:04.970 --> 01:02:04.980 align:start position:0% again for both of them they don't 01:02:04.980 --> 01:02:07.010 align:start position:0% again for both of them they don't observe<01:02:05.460> anything<01:02:05.700> from<01:02:06.000> the<01:02:06.180> past<01:02:06.359> there<01:02:06.900> is 01:02:07.010 --> 01:02:07.020 align:start position:0% observe anything from the past there is 01:02:07.020 --> 01:02:08.569 align:start position:0% observe anything from the past there is no<01:02:07.140> input 01:02:08.569 --> 01:02:08.579 align:start position:0% no input 01:02:08.579 --> 01:02:10.130 align:start position:0% no input the<01:02:09.059> output<01:02:09.359> something<01:02:09.540> which<01:02:09.839> is<01:02:10.020> the 01:02:10.130 --> 01:02:10.140 align:start position:0% the output something which is the 01:02:10.140 --> 01:02:12.049 align:start position:0% the output something which is the decision<01:02:10.380> player<01:02:10.799> one<01:02:10.920> and<01:02:11.400> decision<01:02:11.700> Player 01:02:12.049 --> 01:02:12.059 align:start position:0% decision player one and decision Player 01:02:12.059 --> 01:02:14.630 align:start position:0% decision player one and decision Player Two<01:02:12.180> And<01:02:12.960> they<01:02:13.200> also<01:02:13.559> need<01:02:14.040> something<01:02:14.339> from 01:02:14.630 --> 01:02:14.640 align:start position:0% Two And they also need something from 01:02:14.640 --> 01:02:16.609 align:start position:0% Two And they also need something from the<01:02:14.819> environment<01:02:15.119> back<01:02:15.359> this<01:02:15.720> is<01:02:15.839> the<01:02:16.020> payoff 01:02:16.609 --> 01:02:16.619 align:start position:0% the environment back this is the payoff 01:02:16.619 --> 01:02:18.650 align:start position:0% the environment back this is the payoff player<01:02:16.920> one<01:02:16.980> payoff<01:02:17.339> player<01:02:17.640> 2<01:02:17.819> which<01:02:18.480> are 01:02:18.650 --> 01:02:18.660 align:start position:0% player one payoff player 2 which are 01:02:18.660 --> 01:02:21.530 align:start position:0% player one payoff player 2 which are only<01:02:18.780> defined<01:02:19.319> at<01:02:20.280> the<01:02:20.940> third<01:02:21.059> line<01:02:21.240> block 01:02:21.530 --> 01:02:21.540 align:start position:0% only defined at the third line block 01:02:21.540 --> 01:02:23.329 align:start position:0% only defined at the third line block which<01:02:21.839> is<01:02:21.960> the<01:02:22.200> payoffs<01:02:22.680> PD<01:02:22.980> this<01:02:23.160> is<01:02:23.280> the 01:02:23.329 --> 01:02:23.339 align:start position:0% which is the payoffs PD this is the 01:02:23.339 --> 01:02:25.370 align:start position:0% which is the payoffs PD this is the utility<01:02:23.640> function<01:02:24.059> and<01:02:24.660> here<01:02:24.780> coming<01:02:25.020> back<01:02:25.200> to 01:02:25.370 --> 01:02:25.380 align:start position:0% utility function and here coming back to 01:02:25.380 --> 01:02:27.470 align:start position:0% utility function and here coming back to connecting<01:02:25.799> to<01:02:25.920> your<01:02:26.040> question<01:02:26.220> before<01:02:26.579> the 01:02:27.470 --> 01:02:27.480 align:start position:0% connecting to your question before the 01:02:27.480 --> 01:02:28.910 align:start position:0% connecting to your question before the form<01:02:27.660> this<01:02:27.960> function<01:02:28.200> is<01:02:28.380> expecting 01:02:28.910 --> 01:02:28.920 align:start position:0% form this function is expecting 01:02:28.920 --> 01:02:31.430 align:start position:0% form this function is expecting basically<01:02:29.819> an<01:02:30.000> input<01:02:30.299> from<01:02:30.540> above<01:02:30.900> which 01:02:31.430 --> 01:02:31.440 align:start position:0% basically an input from above which 01:02:31.440 --> 01:02:33.890 align:start position:0% basically an input from above which tells<01:02:31.740> you<01:02:31.859> this<01:02:32.520> is<01:02:32.640> a<01:02:32.819> sequential 01:02:33.890 --> 01:02:33.900 align:start position:0% tells you this is a sequential 01:02:33.900 --> 01:02:35.809 align:start position:0% tells you this is a sequential um a<01:02:34.140> sequential<01:02:34.500> composition<01:02:34.920> right<01:02:35.460> keep 01:02:35.809 --> 01:02:35.819 align:start position:0% um a sequential composition right keep 01:02:35.819 --> 01:02:37.609 align:start position:0% um a sequential composition right keep in<01:02:35.940> mind<01:02:36.119> the<01:02:36.599> diagrammatic<01:02:37.200> language<01:02:37.380> is 01:02:37.609 --> 01:02:37.619 align:start position:0% in mind the diagrammatic language is 01:02:37.619 --> 01:02:38.930 align:start position:0% in mind the diagrammatic language is two-dimensional 01:02:38.930 --> 01:02:38.940 align:start position:0% two-dimensional 01:02:38.940 --> 01:02:40.970 align:start position:0% two-dimensional hassle<01:02:39.599> is<01:02:39.780> not 01:02:40.970 --> 01:02:40.980 align:start position:0% hassle is not 01:02:40.980 --> 01:02:42.650 align:start position:0% hassle is not okay 01:02:42.650 --> 01:02:42.660 align:start position:0% okay 01:02:42.660 --> 01:02:47.210 align:start position:0% okay now<01:02:43.319> the<01:02:44.280> last<01:02:44.460> element<01:02:45.119> the<01:02:45.900> pair<01:02:46.079> of<01:02:46.260> SPD<01:02:46.619> is 01:02:47.210 --> 01:02:47.220 align:start position:0% now the last element the pair of SPD is 01:02:47.220 --> 01:02:49.250 align:start position:0% now the last element the pair of SPD is also<01:02:47.520> outputting<01:02:48.119> the<01:02:48.480> payoffs<01:02:49.020> and<01:02:49.140> these 01:02:49.250 --> 01:02:49.260 align:start position:0% also outputting the payoffs and these 01:02:49.260 --> 01:02:52.490 align:start position:0% also outputting the payoffs and these payouts<01:02:49.619> are<01:02:49.740> then<01:02:49.859> connected<01:02:50.280> back<01:02:50.540> to<01:02:51.540> the 01:02:52.490 --> 01:02:52.500 align:start position:0% payouts are then connected back to the 01:02:52.500 --> 01:02:55.849 align:start position:0% payouts are then connected back to the the<01:02:52.799> players<01:02:53.579> and<01:02:54.240> you<01:02:54.359> can<01:02:54.420> see<01:02:54.599> already 01:02:55.849 --> 01:02:55.859 align:start position:0% the players and you can see already 01:02:55.859 --> 01:02:58.430 align:start position:0% the players and you can see already um<01:02:55.920> you<01:02:56.520> know<01:02:56.579> certain<01:02:57.000> elements<01:02:57.359> of<01:02:57.480> has<01:02:57.660> to 01:02:58.430 --> 01:02:58.440 align:start position:0% um you know certain elements of has to 01:02:58.440 --> 01:03:00.049 align:start position:0% um you know certain elements of has to also<01:02:58.680> help<01:02:58.799> because<01:02:59.099> the<01:02:59.579> order<01:02:59.700> of<01:02:59.880> where 01:03:00.049 --> 01:03:00.059 align:start position:0% also help because the order of where 01:03:00.059 --> 01:03:01.069 align:start position:0% also help because the order of where these<01:03:00.299> things<01:03:00.359> are<01:03:00.540> actually<01:03:00.660> don't<01:03:00.900> matter 01:03:01.069 --> 01:03:01.079 align:start position:0% these things are actually don't matter 01:03:01.079 --> 01:03:02.750 align:start position:0% these things are actually don't matter and<01:03:01.619> it<01:03:01.799> helps<01:03:01.980> in<01:03:02.099> the<01:03:02.160> evaluation<01:03:02.520> later 01:03:02.750 --> 01:03:02.760 align:start position:0% and it helps in the evaluation later 01:03:02.760 --> 01:03:04.970 align:start position:0% and it helps in the evaluation later yeah 01:03:04.970 --> 01:03:04.980 align:start position:0% yeah 01:03:04.980 --> 01:03:06.470 align:start position:0% yeah okay 01:03:06.470 --> 01:03:06.480 align:start position:0% okay 01:03:06.480 --> 01:03:08.990 align:start position:0% okay questions<01:03:07.079> so<01:03:07.440> far<01:03:07.619> is<01:03:08.160> the<01:03:08.339> center<01:03:08.460> roughly 01:03:08.990 --> 01:03:09.000 align:start position:0% questions so far is the center roughly 01:03:09.000 --> 01:03:10.490 align:start position:0% questions so far is the center roughly clear<01:03:09.180> at<01:03:09.420> least 01:03:10.490 --> 01:03:10.500 align:start position:0% clear at least 01:03:10.500 --> 01:03:12.109 align:start position:0% clear at least area 01:03:12.109 --> 01:03:12.119 align:start position:0% area 01:03:12.119 --> 01:03:15.470 align:start position:0% area so<01:03:12.720> so<01:03:12.720> yeah<01:03:13.319> you<01:03:13.559> have<01:03:13.680> a<01:03:13.799> question<01:03:14.000> I<01:03:15.000> want<01:03:15.299> to 01:03:15.470 --> 01:03:15.480 align:start position:0% so so yeah you have a question I want to 01:03:15.480 --> 01:03:18.530 align:start position:0% so so yeah you have a question I want to ask<01:03:15.780> about<01:03:16.200> oh<01:03:16.740> thank<01:03:17.040> you<01:03:17.220> I<01:03:18.119> wanted<01:03:18.240> to<01:03:18.420> ask 01:03:18.530 --> 01:03:18.540 align:start position:0% ask about oh thank you I wanted to ask 01:03:18.540 --> 01:03:21.230 align:start position:0% ask about oh thank you I wanted to ask about<01:03:18.780> the<01:03:19.140> inputs<01:03:19.619> and<01:03:19.740> feedback<01:03:20.160> before<01:03:20.760> and 01:03:21.230 --> 01:03:21.240 align:start position:0% about the inputs and feedback before and 01:03:21.240 --> 01:03:24.349 align:start position:0% about the inputs and feedback before and after<01:03:21.619> the<01:03:22.619> uh<01:03:22.920> internal 01:03:24.349 --> 01:03:24.359 align:start position:0% after the uh internal 01:03:24.359 --> 01:03:26.990 align:start position:0% after the uh internal definitions<01:03:25.260> like<01:03:25.619> like<01:03:25.859> are<01:03:26.099> those<01:03:26.400> the 01:03:26.990 --> 01:03:27.000 align:start position:0% definitions like like are those the 01:03:27.000 --> 01:03:29.690 align:start position:0% definitions like like are those the inputs<01:03:27.420> going<01:03:27.540> into<01:03:27.720> P1<01:03:28.200> you<01:03:28.680> mean<01:03:28.920> outside<01:03:29.400> of 01:03:29.690 --> 01:03:29.700 align:start position:0% inputs going into P1 you mean outside of 01:03:29.700 --> 01:03:33.710 align:start position:0% inputs going into P1 you mean outside of sorry<01:03:30.059> on<01:03:30.900> this<01:03:31.020> slide<01:03:31.260> yeah<01:03:31.980> yes<01:03:32.700> so<01:03:33.480> the 01:03:33.710 --> 01:03:33.720 align:start position:0% sorry on this slide yeah yes so the 01:03:33.720 --> 01:03:35.329 align:start position:0% sorry on this slide yeah yes so the first<01:03:33.839> inputs<01:03:34.380> and<01:03:34.500> feedback<01:03:34.799> the<01:03:35.040> ones<01:03:35.160> that 01:03:35.329 --> 01:03:35.339 align:start position:0% first inputs and feedback the ones that 01:03:35.339 --> 01:03:37.130 align:start position:0% first inputs and feedback the ones that have<01:03:35.520> a<01:03:35.700> blank 01:03:37.130 --> 01:03:37.140 align:start position:0% have a blank 01:03:37.140 --> 01:03:40.010 align:start position:0% have a blank um<01:03:37.200> this<01:03:38.040> okay<01:03:38.760> I<01:03:39.299> should<01:03:39.420> have<01:03:39.540> feel<01:03:39.660> precise 01:03:40.010 --> 01:03:40.020 align:start position:0% um this okay I should have feel precise 01:03:40.020 --> 01:03:41.750 align:start position:0% um this okay I should have feel precise thanks<01:03:40.200> for<01:03:40.319> the<01:03:40.440> pointer<01:03:40.680> so<01:03:41.339> um<01:03:41.339> what<01:03:41.640> is 01:03:41.750 --> 01:03:41.760 align:start position:0% thanks for the pointer so um what is 01:03:41.760 --> 01:03:43.309 align:start position:0% thanks for the pointer so um what is actually<01:03:41.880> the<01:03:42.119> inputs<01:03:42.480> would<01:03:42.720> correspond<01:03:43.140> to 01:03:43.309 --> 01:03:43.319 align:start position:0% actually the inputs would correspond to 01:03:43.319 --> 01:03:46.069 align:start position:0% actually the inputs would correspond to an<01:03:43.440> ingoing<01:03:43.799> wire<01:03:43.980> into<01:03:44.339> the<01:03:44.520> overall<01:03:44.880> game 01:03:46.069 --> 01:03:46.079 align:start position:0% an ingoing wire into the overall game 01:03:46.079 --> 01:03:47.329 align:start position:0% an ingoing wire into the overall game um<01:03:46.140> I<01:03:46.260> could<01:03:46.380> think<01:03:46.559> about<01:03:46.740> the<01:03:46.859> overall<01:03:47.160> game 01:03:47.329 --> 01:03:47.339 align:start position:0% um I could think about the overall game 01:03:47.339 --> 01:03:49.490 align:start position:0% um I could think about the overall game as<01:03:47.460> a<01:03:47.579> box<01:03:47.700> itself<01:03:48.119> right<01:03:48.420> so<01:03:48.900> this<01:03:49.140> this<01:03:49.319> is 01:03:49.490 --> 01:03:49.500 align:start position:0% as a box itself right so this this is 01:03:49.500 --> 01:03:50.870 align:start position:0% as a box itself right so this this is just<01:03:49.619> one<01:03:49.799> box<01:03:49.980> with<01:03:50.160> possible<01:03:50.520> in-going 01:03:50.870 --> 01:03:50.880 align:start position:0% just one box with possible in-going 01:03:50.880 --> 01:03:52.789 align:start position:0% just one box with possible in-going in-going<01:03:51.420> and<01:03:51.540> outgoing<01:03:51.900> wires<01:03:52.200> what<01:03:52.619> it 01:03:52.789 --> 01:03:52.799 align:start position:0% in-going and outgoing wires what it 01:03:52.799 --> 01:03:54.890 align:start position:0% in-going and outgoing wires what it essentially<01:03:53.160> represents<01:03:53.640> is<01:03:53.819> an<01:03:54.000> empty<01:03:54.240> not 01:03:54.890 --> 01:03:54.900 align:start position:0% essentially represents is an empty not 01:03:54.900 --> 01:03:56.569 align:start position:0% essentially represents is an empty not an<01:03:55.020> empty<01:03:55.260> box<01:03:55.380> but<01:03:55.619> a<01:03:55.740> box<01:03:56.040> which<01:03:56.280> is<01:03:56.400> not 01:03:56.569 --> 01:03:56.579 align:start position:0% an empty box but a box which is not 01:03:56.579 --> 01:03:57.890 align:start position:0% an empty box but a box which is not connected<01:03:56.940> at<01:03:57.119> all<01:03:57.240> to<01:03:57.359> the<01:03:57.480> outside<01:03:57.599> world 01:03:57.890 --> 01:03:57.900 align:start position:0% connected at all to the outside world 01:03:57.900 --> 01:04:01.130 align:start position:0% connected at all to the outside world right<01:03:58.440> okay<01:03:58.680> I'm<01:03:59.640> cutting<01:04:00.000> just<01:04:00.119> away<01:04:00.660> four<01:04:00.960> of 01:04:01.130 --> 01:04:01.140 align:start position:0% right okay I'm cutting just away four of 01:04:01.140 --> 01:04:02.289 align:start position:0% right okay I'm cutting just away four of these<01:04:01.380> wires 01:04:02.289 --> 01:04:02.299 align:start position:0% these wires 01:04:02.299 --> 01:04:03.950 align:start position:0% these wires and 01:04:03.950 --> 01:04:03.960 align:start position:0% and 01:04:03.960 --> 01:04:04.549 align:start position:0% and um 01:04:04.549 --> 01:04:04.559 align:start position:0% um 01:04:04.559 --> 01:04:06.170 align:start position:0% um why<01:04:05.099> is<01:04:05.220> this<01:04:05.339> relevant<01:04:05.700> actually<01:04:05.880> if<01:04:06.059> you 01:04:06.170 --> 01:04:06.180 align:start position:0% why is this relevant actually if you 01:04:06.180 --> 01:04:07.670 align:start position:0% why is this relevant actually if you think<01:04:06.359> about<01:04:06.480> a<01:04:06.780> prisoner<01:04:07.079> dilemma<01:04:07.440> a 01:04:07.670 --> 01:04:07.680 align:start position:0% think about a prisoner dilemma a 01:04:07.680 --> 01:04:09.829 align:start position:0% think about a prisoner dilemma a One-Shot<01:04:08.040> game<01:04:08.220> it<01:04:08.700> has<01:04:08.819> no<01:04:09.000> past<01:04:09.240> and<01:04:09.599> it<01:04:09.720> has 01:04:09.829 --> 01:04:09.839 align:start position:0% One-Shot game it has no past and it has 01:04:09.839 --> 01:04:11.630 align:start position:0% One-Shot game it has no past and it has also<01:04:10.079> no<01:04:10.200> future<01:04:10.380> right<01:04:10.740> it's<01:04:10.859> one<01:04:11.099> shot<01:04:11.280> by 01:04:11.630 --> 01:04:11.640 align:start position:0% also no future right it's one shot by 01:04:11.640 --> 01:04:13.250 align:start position:0% also no future right it's one shot by definition<01:04:11.819> there<01:04:12.540> is<01:04:12.720> no<01:04:12.780> need<01:04:12.960> to<01:04:13.079> send 01:04:13.250 --> 01:04:13.260 align:start position:0% definition there is no need to send 01:04:13.260 --> 01:04:14.390 align:start position:0% definition there is no need to send information<01:04:13.440> back<01:04:13.799> or<01:04:13.980> send<01:04:14.160> information 01:04:14.390 --> 01:04:14.400 align:start position:0% information back or send information 01:04:14.400 --> 01:04:17.630 align:start position:0% information back or send information into<01:04:14.700> the<01:04:14.940> future<01:04:15.380> and<01:04:16.380> topologically<01:04:17.160> I<01:04:17.460> can 01:04:17.630 --> 01:04:17.640 align:start position:0% into the future and topologically I can 01:04:17.640 --> 01:04:19.609 align:start position:0% into the future and topologically I can kind<01:04:17.940> of<01:04:18.059> represent<01:04:18.720> these<01:04:19.020> features<01:04:19.260> in<01:04:19.559> a 01:04:19.609 --> 01:04:19.619 align:start position:0% kind of represent these features in a 01:04:19.619 --> 01:04:20.870 align:start position:0% kind of represent these features in a sense<01:04:19.740> that<01:04:19.980> there<01:04:20.099> are<01:04:20.220> wires<01:04:20.579> or<01:04:20.700> they<01:04:20.760> are 01:04:20.870 --> 01:04:20.880 align:start position:0% sense that there are wires or they are 01:04:20.880 --> 01:04:22.970 align:start position:0% sense that there are wires or they are not<01:04:21.000> wires<01:04:21.299> it's<01:04:21.960> also<01:04:22.260> useful<01:04:22.559> in<01:04:22.680> the<01:04:22.859> sense 01:04:22.970 --> 01:04:22.980 align:start position:0% not wires it's also useful in the sense 01:04:22.980 --> 01:04:24.349 align:start position:0% not wires it's also useful in the sense that<01:04:23.160> you<01:04:23.400> know<01:04:23.520> if<01:04:23.579> you<01:04:23.700> model<01:04:23.819> more<01:04:24.119> complex 01:04:24.349 --> 01:04:24.359 align:start position:0% that you know if you model more complex 01:04:24.359 --> 01:04:26.089 align:start position:0% that you know if you model more complex games<01:04:24.599> you<01:04:24.900> can<01:04:25.020> see<01:04:25.200> that<01:04:25.440> only<01:04:25.680> when<01:04:25.920> there 01:04:26.089 --> 01:04:26.099 align:start position:0% games you can see that only when there 01:04:26.099 --> 01:04:27.650 align:start position:0% games you can see that only when there is<01:04:26.220> a<01:04:26.339> connection<01:04:26.400> through<01:04:26.700> a<01:04:26.880> wire<01:04:27.000> there<01:04:27.540> is 01:04:27.650 --> 01:04:27.660 align:start position:0% is a connection through a wire there is 01:04:27.660 --> 01:04:29.150 align:start position:0% is a connection through a wire there is actually<01:04:27.780> an<01:04:27.960> effect<01:04:28.079> happening<01:04:28.619> so 01:04:29.150 --> 01:04:29.160 align:start position:0% actually an effect happening so 01:04:29.160 --> 01:04:30.289 align:start position:0% actually an effect happening so sometimes<01:04:29.400> these<01:04:29.640> diagrams<01:04:30.000> can<01:04:30.180> be 01:04:30.289 --> 01:04:30.299 align:start position:0% sometimes these diagrams can be 01:04:30.299 --> 01:04:31.730 align:start position:0% sometimes these diagrams can be extremely<01:04:30.599> helpful<01:04:30.960> in<01:04:31.440> kind<01:04:31.680> of 01:04:31.730 --> 01:04:31.740 align:start position:0% extremely helpful in kind of 01:04:31.740 --> 01:04:33.109 align:start position:0% extremely helpful in kind of understanding<01:04:32.160> what<01:04:32.280> actually<01:04:32.520> dependencies 01:04:33.109 --> 01:04:33.119 align:start position:0% understanding what actually dependencies 01:04:33.119 --> 01:04:38.329 align:start position:0% understanding what actually dependencies for<01:04:34.020> sure<01:04:34.140> thank<01:04:34.500> you<01:04:34.619> okay<01:04:35.040> other<01:04:35.460> questions 01:04:38.329 --> 01:04:38.339 align:start position:0% 01:04:38.339 --> 01:04:41.809 align:start position:0% okay 01:04:41.809 --> 01:04:41.819 align:start position:0% 01:04:41.819 --> 01:04:45.410 align:start position:0% so<01:04:42.599> in<01:04:43.319> the<01:04:43.440> last<01:04:43.559> part<01:04:43.799> I<01:04:44.280> want<01:04:44.339> to<01:04:44.460> look<01:04:44.640> at<01:04:45.000> a 01:04:45.410 --> 01:04:45.420 align:start position:0% so in the last part I want to look at a 01:04:45.420 --> 01:04:47.530 align:start position:0% so in the last part I want to look at a staking<01:04:45.720> model 01:04:47.530 --> 01:04:47.540 align:start position:0% staking model 01:04:47.540 --> 01:04:49.970 align:start position:0% staking model this<01:04:48.540> is<01:04:48.660> you<01:04:48.900> know<01:04:49.020> a<01:04:49.140> simple<01:04:49.260> model<01:04:49.500> still<01:04:49.799> in 01:04:49.970 --> 01:04:49.980 align:start position:0% this is you know a simple model still in 01:04:49.980 --> 01:04:51.829 align:start position:0% this is you know a simple model still in the<01:04:50.099> sense<01:04:50.220> that<01:04:50.400> I<01:04:50.579> can<01:04:50.700> most<01:04:51.119> mostly<01:04:51.599> explain 01:04:51.829 --> 01:04:51.839 align:start position:0% the sense that I can most mostly explain 01:04:51.839 --> 01:04:53.630 align:start position:0% the sense that I can most mostly explain all<01:04:52.260> the<01:04:52.380> components<01:04:52.740> that<01:04:52.859> are<01:04:52.980> needed<01:04:53.280> in 01:04:53.630 --> 01:04:53.640 align:start position:0% all the components that are needed in 01:04:53.640 --> 01:04:55.849 align:start position:0% all the components that are needed in the<01:04:53.760> in<01:04:53.880> the<01:04:54.059> scope<01:04:54.420> of<01:04:54.599> the<01:04:54.720> workshop 01:04:55.849 --> 01:04:55.859 align:start position:0% the in the scope of the workshop 01:04:55.859 --> 01:04:57.789 align:start position:0% the in the scope of the workshop the<01:04:56.400> motivation<01:04:56.700> comes<01:04:57.059> actually 01:04:57.789 --> 01:04:57.799 align:start position:0% the motivation comes actually 01:04:57.799 --> 01:05:00.650 align:start position:0% the motivation comes actually have<01:04:58.799> said<01:04:58.980> that<01:04:59.099> part<01:04:59.400> of<01:04:59.520> the<01:04:59.640> engine 01:05:00.650 --> 01:05:00.660 align:start position:0% have said that part of the engine 01:05:00.660 --> 01:05:02.450 align:start position:0% have said that part of the engine um<01:05:00.780> we're<01:05:01.020> kind<01:05:01.559> of<01:05:01.680> funded<01:05:01.920> by<01:05:02.040> the<01:05:02.160> ethereum 01:05:02.450 --> 01:05:02.460 align:start position:0% um we're kind of funded by the ethereum 01:05:02.460 --> 01:05:03.770 align:start position:0% um we're kind of funded by the ethereum foundation<01:05:02.819> and<01:05:03.059> we<01:05:03.240> were<01:05:03.299> working<01:05:03.480> with<01:05:03.660> the 01:05:03.770 --> 01:05:03.780 align:start position:0% foundation and we were working with the 01:05:03.780 --> 01:05:05.390 align:start position:0% foundation and we were working with the robust<01:05:04.020> incentive<01:05:04.440> group<01:05:04.619> that<01:05:04.980> was<01:05:05.160> one<01:05:05.339> of 01:05:05.390 --> 01:05:05.400 align:start position:0% robust incentive group that was one of 01:05:05.400 --> 01:05:08.210 align:start position:0% robust incentive group that was one of the<01:05:05.520> examples<01:05:05.819> they<01:05:06.180> prompted<01:05:06.599> us<01:05:06.720> to<01:05:06.839> work<01:05:06.960> on 01:05:08.210 --> 01:05:08.220 align:start position:0% the examples they prompted us to work on 01:05:08.220 --> 01:05:09.950 align:start position:0% the examples they prompted us to work on um<01:05:08.280> and<01:05:08.579> that's<01:05:08.700> basically<01:05:09.000> what<01:05:09.240> we<01:05:09.359> did<01:05:09.480> so 01:05:09.950 --> 01:05:09.960 align:start position:0% um and that's basically what we did so 01:05:09.960 --> 01:05:12.170 align:start position:0% um and that's basically what we did so this<01:05:10.140> is<01:05:10.260> this<01:05:10.619> is<01:05:10.740> a<01:05:10.980> simplified<01:05:11.579> version<01:05:11.880> of 01:05:12.170 --> 01:05:12.180 align:start position:0% this is this is a simplified version of 01:05:12.180 --> 01:05:15.650 align:start position:0% this is this is a simplified version of that<01:05:12.359> of<01:05:12.720> that<01:05:12.900> work 01:05:15.650 --> 01:05:15.660 align:start position:0% 01:05:15.660 --> 01:05:17.990 align:start position:0% I<01:05:16.140> will<01:05:16.260> focus<01:05:16.500> on<01:05:16.619> compositionality<01:05:17.339> we<01:05:17.819> can 01:05:17.990 --> 01:05:18.000 align:start position:0% I will focus on compositionality we can 01:05:18.000 --> 01:05:19.190 align:start position:0% I will focus on compositionality we can guess<01:05:18.119> it<01:05:18.299> already 01:05:19.190 --> 01:05:19.200 align:start position:0% guess it already 01:05:19.200 --> 01:05:20.450 align:start position:0% guess it already um specifically<01:05:19.619> now<01:05:19.740> I<01:05:19.920> want<01:05:20.040> what<01:05:20.220> I<01:05:20.339> want 01:05:20.450 --> 01:05:20.460 align:start position:0% um specifically now I want what I want 01:05:20.460 --> 01:05:22.670 align:start position:0% um specifically now I want what I want to<01:05:20.520> show<01:05:20.640> is<01:05:20.819> how<01:05:21.180> I'm<01:05:21.720> basically<01:05:22.140> not 01:05:22.670 --> 01:05:22.680 align:start position:0% to show is how I'm basically not 01:05:22.680 --> 01:05:23.990 align:start position:0% to show is how I'm basically not composing<01:05:23.160> things<01:05:23.339> but<01:05:23.520> I<01:05:23.640> first<01:05:23.819> will 01:05:23.990 --> 01:05:24.000 align:start position:0% composing things but I first will 01:05:24.000 --> 01:05:25.730 align:start position:0% composing things but I first will actually<01:05:24.180> decompose<01:05:24.660> stuff<01:05:24.900> I<01:05:25.319> will<01:05:25.440> look<01:05:25.619> at 01:05:25.730 --> 01:05:25.740 align:start position:0% actually decompose stuff I will look at 01:05:25.740 --> 01:05:27.530 align:start position:0% actually decompose stuff I will look at the<01:05:25.859> overall<01:05:26.160> problem<01:05:26.280> and<01:05:26.520> I<01:05:26.640> will<01:05:26.760> put<01:05:26.940> it<01:05:27.119> in 01:05:27.530 --> 01:05:27.540 align:start position:0% the overall problem and I will put it in 01:05:27.540 --> 01:05:31.309 align:start position:0% the overall problem and I will put it in as<01:05:27.720> small<01:05:27.960> parts<01:05:28.200> and<01:05:28.440> bits<01:05:28.740> as<01:05:28.920> possible 01:05:31.309 --> 01:05:31.319 align:start position:0% as small parts and bits as possible 01:05:31.319 --> 01:05:33.349 align:start position:0% as small parts and bits as possible I<01:05:31.740> want<01:05:31.799> to<01:05:31.920> also<01:05:32.160> illustrate 01:05:33.349 --> 01:05:33.359 align:start position:0% I want to also illustrate 01:05:33.359 --> 01:05:34.609 align:start position:0% I want to also illustrate um what<01:05:33.599> we<01:05:33.720> sometimes<01:05:34.020> refer<01:05:34.319> to<01:05:34.380> as<01:05:34.500> a 01:05:34.609 --> 01:05:34.619 align:start position:0% um what we sometimes refer to as a 01:05:34.619 --> 01:05:36.109 align:start position:0% um what we sometimes refer to as a zooming<01:05:34.859> in<01:05:34.980> operation 01:05:36.109 --> 01:05:36.119 align:start position:0% zooming in operation 01:05:36.119 --> 01:05:38.270 align:start position:0% zooming in operation I<01:05:36.540> said<01:05:36.660> before<01:05:36.900> all<01:05:37.260> of<01:05:37.380> the<01:05:37.500> components<01:05:37.980> are 01:05:38.270 --> 01:05:38.280 align:start position:0% I said before all of the components are 01:05:38.280 --> 01:05:40.130 align:start position:0% I said before all of the components are making<01:05:38.520> game<01:05:38.819> theoretic<01:05:39.299> sense<01:05:39.480> which<01:05:39.960> means 01:05:40.130 --> 01:05:40.140 align:start position:0% making game theoretic sense which means 01:05:40.140 --> 01:05:42.230 align:start position:0% making game theoretic sense which means if<01:05:40.319> I'm<01:05:40.440> modeling<01:05:40.799> something<01:05:40.980> complicated 01:05:42.230 --> 01:05:42.240 align:start position:0% if I'm modeling something complicated 01:05:42.240 --> 01:05:44.510 align:start position:0% if I'm modeling something complicated I<01:05:42.839> can<01:05:42.960> when<01:05:43.319> I<01:05:43.559> want<01:05:43.619> to<01:05:43.740> obviously<01:05:44.220> look<01:05:44.339> at 01:05:44.510 --> 01:05:44.520 align:start position:0% I can when I want to obviously look at 01:05:44.520 --> 01:05:46.609 align:start position:0% I can when I want to obviously look at the<01:05:44.700> overall<01:05:45.059> complex<01:05:45.480> thing<01:05:45.780> and<01:05:46.380> you<01:05:46.500> know 01:05:46.609 --> 01:05:46.619 align:start position:0% the overall complex thing and you know 01:05:46.619 --> 01:05:49.130 align:start position:0% the overall complex thing and you know analyze<01:05:47.099> this<01:05:47.280> but<01:05:48.000> sometimes<01:05:48.420> I<01:05:48.839> might<01:05:48.960> not 01:05:49.130 --> 01:05:49.140 align:start position:0% analyze this but sometimes I might not 01:05:49.140 --> 01:05:50.630 align:start position:0% analyze this but sometimes I might not care<01:05:49.319> about<01:05:49.559> the<01:05:49.740> overall<01:05:49.980> thing<01:05:50.160> but<01:05:50.400> I<01:05:50.520> might 01:05:50.630 --> 01:05:50.640 align:start position:0% care about the overall thing but I might 01:05:50.640 --> 01:05:51.770 align:start position:0% care about the overall thing but I might just<01:05:50.819> care 01:05:51.770 --> 01:05:51.780 align:start position:0% just care 01:05:51.780 --> 01:05:53.750 align:start position:0% just care let's<01:05:52.380> say<01:05:52.559> the<01:05:52.740> the<01:05:52.920> validator<01:05:53.460> is<01:05:53.640> a 01:05:53.750 --> 01:05:53.760 align:start position:0% let's say the the validator is a 01:05:53.760 --> 01:05:55.250 align:start position:0% let's say the the validator is a mistaken<01:05:54.059> protocol<01:05:54.299> what<01:05:54.839> are<01:05:54.960> they<01:05:55.079> actually 01:05:55.250 --> 01:05:55.260 align:start position:0% mistaken protocol what are they actually 01:05:55.260 --> 01:05:57.289 align:start position:0% mistaken protocol what are they actually doing<01:05:55.440> for<01:05:55.740> a<01:05:55.859> specific<01:05:56.099> input<01:05:56.460> what<01:05:56.880> I<01:05:57.000> can<01:05:57.119> do 01:05:57.289 --> 01:05:57.299 align:start position:0% doing for a specific input what I can do 01:05:57.299 --> 01:05:58.849 align:start position:0% doing for a specific input what I can do then<01:05:57.420> is<01:05:57.660> if<01:05:57.839> I<01:05:57.960> have<01:05:58.079> the<01:05:58.260> model<01:05:58.440> as<01:05:58.680> a 01:05:58.849 --> 01:05:58.859 align:start position:0% then is if I have the model as a 01:05:58.859 --> 01:06:01.730 align:start position:0% then is if I have the model as a specific<01:05:59.160> component<01:05:59.940> I<01:06:00.299> can<01:06:00.480> just<01:06:00.660> zoom<01:06:00.960> in 01:06:01.730 --> 01:06:01.740 align:start position:0% specific component I can just zoom in 01:06:01.740 --> 01:06:04.069 align:start position:0% specific component I can just zoom in look<01:06:02.160> at<01:06:02.339> this<01:06:02.520> specific<01:06:02.760> thing<01:06:03.059> analyze<01:06:03.900> this 01:06:04.069 --> 01:06:04.079 align:start position:0% look at this specific thing analyze this 01:06:04.079 --> 01:06:05.390 align:start position:0% look at this specific thing analyze this specific<01:06:04.319> thing<01:06:04.559> without<01:06:04.740> regard<01:06:05.160> of<01:06:05.280> the 01:06:05.390 --> 01:06:05.400 align:start position:0% specific thing without regard of the 01:06:05.400 --> 01:06:06.650 align:start position:0% specific thing without regard of the rest 01:06:06.650 --> 01:06:06.660 align:start position:0% rest 01:06:06.660 --> 01:06:08.510 align:start position:0% rest it's<01:06:06.900> a<01:06:07.079> bit<01:06:07.140> like<01:06:07.319> unit<01:06:07.559> testing<01:06:08.040> of<01:06:08.160> specific 01:06:08.510 --> 01:06:08.520 align:start position:0% it's a bit like unit testing of specific 01:06:08.520 --> 01:06:10.789 align:start position:0% it's a bit like unit testing of specific units<01:06:08.880> if<01:06:09.059> you<01:06:09.180> like<01:06:09.299> which<01:06:10.200> can<01:06:10.380> be<01:06:10.500> extremely 01:06:10.789 --> 01:06:10.799 align:start position:0% units if you like which can be extremely 01:06:10.799 --> 01:06:13.370 align:start position:0% units if you like which can be extremely useful 01:06:13.370 --> 01:06:13.380 align:start position:0% 01:06:13.380 --> 01:06:15.470 align:start position:0% given<01:06:13.980> time<01:06:14.099> there<01:06:14.940> are<01:06:15.059> obviously<01:06:15.299> more 01:06:15.470 --> 01:06:15.480 align:start position:0% given time there are obviously more 01:06:15.480 --> 01:06:17.150 align:start position:0% given time there are obviously more details<01:06:15.900> that<01:06:16.020> I<01:06:16.200> can<01:06:16.319> I<01:06:16.440> cannot<01:06:16.740> explain<01:06:16.859> all 01:06:17.150 --> 01:06:17.160 align:start position:0% details that I can I cannot explain all 01:06:17.160 --> 01:06:19.030 align:start position:0% details that I can I cannot explain all the<01:06:17.280> details<01:06:17.579> behind<01:06:17.819> it<01:06:17.940> but<01:06:18.059> this<01:06:18.359> is 01:06:19.030 --> 01:06:19.040 align:start position:0% the details behind it but this is 01:06:19.040 --> 01:06:21.650 align:start position:0% the details behind it but this is explicitly<01:06:20.040> based<01:06:20.400> on<01:06:20.579> a<01:06:20.819> blog<01:06:21.180> post<01:06:21.299> that<01:06:21.540> we 01:06:21.650 --> 01:06:21.660 align:start position:0% explicitly based on a blog post that we 01:06:21.660 --> 01:06:24.109 align:start position:0% explicitly based on a blog post that we wrote<01:06:21.780> which<01:06:22.440> gives<01:06:22.680> much<01:06:22.859> more<01:06:23.040> context<01:06:23.400> also 01:06:24.109 --> 01:06:24.119 align:start position:0% wrote which gives much more context also 01:06:24.119 --> 01:06:25.490 align:start position:0% wrote which gives much more context also on<01:06:24.180> the<01:06:24.299> relation<01:06:24.539> to<01:06:24.720> you<01:06:25.079> know<01:06:25.140> where<01:06:25.319> the 01:06:25.490 --> 01:06:25.500 align:start position:0% on the relation to you know where the 01:06:25.500 --> 01:06:27.710 align:start position:0% on the relation to you know where the idea<01:06:25.799> for<01:06:25.920> the<01:06:26.039> model<01:06:26.160> comes<01:06:26.700> from<01:06:26.819> and<01:06:27.180> also 01:06:27.710 --> 01:06:27.720 align:start position:0% idea for the model comes from and also 01:06:27.720 --> 01:06:29.630 align:start position:0% idea for the model comes from and also all<01:06:27.900> of<01:06:28.020> the<01:06:28.140> components<01:06:28.559> are<01:06:28.680> explained<01:06:29.099> in 01:06:29.630 --> 01:06:29.640 align:start position:0% all of the components are explained in 01:06:29.640 --> 01:06:32.470 align:start position:0% all of the components are explained in detail 01:06:32.470 --> 01:06:32.480 align:start position:0% 01:06:32.480 --> 01:06:36.109 align:start position:0% okay<01:06:33.480> so<01:06:34.079> what's<01:06:34.260> the<01:06:34.500> basic<01:06:34.740> setup<01:06:35.039> here 01:06:36.109 --> 01:06:36.119 align:start position:0% okay so what's the basic setup here 01:06:36.119 --> 01:06:37.970 align:start position:0% okay so what's the basic setup here we<01:06:36.599> have<01:06:36.720> essentially 01:06:37.970 --> 01:06:37.980 align:start position:0% we have essentially 01:06:37.980 --> 01:06:39.650 align:start position:0% we have essentially um 01:06:39.650 --> 01:06:39.660 align:start position:0% um 01:06:39.660 --> 01:06:42.289 align:start position:0% um several<01:06:40.319> periods<01:06:40.740> possibly<01:06:41.160> in<01:06:41.819> each<01:06:42.000> period 01:06:42.289 --> 01:06:42.299 align:start position:0% several periods possibly in each period 01:06:42.299 --> 01:06:43.789 align:start position:0% several periods possibly in each period there<01:06:42.660> is<01:06:42.839> one<01:06:42.960> proposal<01:06:43.380> and<01:06:43.500> there<01:06:43.619> are<01:06:43.740> two 01:06:43.789 --> 01:06:43.799 align:start position:0% there is one proposal and there are two 01:06:43.799 --> 01:06:45.529 align:start position:0% there is one proposal and there are two validators 01:06:45.529 --> 01:06:45.539 align:start position:0% validators 01:06:45.539 --> 01:06:47.329 align:start position:0% validators um<01:06:45.599> what<01:06:45.960> are<01:06:46.140> they<01:06:46.260> doing<01:06:46.380> the<01:06:46.859> proposal 01:06:47.329 --> 01:06:47.339 align:start position:0% um what are they doing the proposal 01:06:47.339 --> 01:06:49.250 align:start position:0% um what are they doing the proposal basically<01:06:47.700> observes<01:06:48.240> a<01:06:48.420> chain 01:06:49.250 --> 01:06:49.260 align:start position:0% basically observes a chain 01:06:49.260 --> 01:06:50.630 align:start position:0% basically observes a chain I<01:06:49.559> will<01:06:49.680> say<01:06:49.740> in<01:06:49.859> a<01:06:49.980> minute<01:06:50.099> or<01:06:50.220> give<01:06:50.460> you<01:06:50.579> a 01:06:50.630 --> 01:06:50.640 align:start position:0% I will say in a minute or give you a 01:06:50.640 --> 01:06:51.770 align:start position:0% I will say in a minute or give you a picture<01:06:50.760> of<01:06:50.940> how<01:06:51.059> this<01:06:51.180> actually<01:06:51.359> looks<01:06:51.720> like 01:06:51.770 --> 01:06:51.780 align:start position:0% picture of how this actually looks like 01:06:51.780 --> 01:06:53.809 align:start position:0% picture of how this actually looks like and<01:06:52.500> the<01:06:52.619> proposal<01:06:53.039> basically<01:06:53.339> observes 01:06:53.809 --> 01:06:53.819 align:start position:0% and the proposal basically observes 01:06:53.819 --> 01:06:55.490 align:start position:0% and the proposal basically observes their<01:06:53.940> chain<01:06:54.119> and<01:06:54.299> then<01:06:54.420> decides 01:06:55.490 --> 01:06:55.500 align:start position:0% their chain and then decides 01:06:55.500 --> 01:06:56.930 align:start position:0% their chain and then decides um<01:06:55.619> yeah<01:06:55.740> I<01:06:55.920> want<01:06:56.039> to<01:06:56.160> extend<01:06:56.400> the<01:06:56.520> chain<01:06:56.700> at 01:06:56.930 --> 01:06:56.940 align:start position:0% um yeah I want to extend the chain at 01:06:56.940 --> 01:06:58.490 align:start position:0% um yeah I want to extend the chain at the<01:06:57.059> chain<01:06:57.180> and<01:06:57.420> basically<01:06:57.900> says<01:06:58.140> okay<01:06:58.260> there 01:06:58.490 --> 01:06:58.500 align:start position:0% the chain and basically says okay there 01:06:58.500 --> 01:06:59.870 align:start position:0% the chain and basically says okay there are<01:06:58.619> several<01:06:58.859> blocks<01:06:59.099> on<01:06:59.160> which<01:06:59.339> block<01:06:59.520> am<01:06:59.700> I 01:06:59.870 --> 01:06:59.880 align:start position:0% are several blocks on which block am I 01:06:59.880 --> 01:07:03.470 align:start position:0% are several blocks on which block am I actually<01:07:00.000> building<01:07:00.299> again<01:07:01.200> it's<01:07:01.500> simplified 01:07:03.470 --> 01:07:03.480 align:start position:0% actually building again it's simplified 01:07:03.480 --> 01:07:05.630 align:start position:0% actually building again it's simplified and<01:07:04.380> what<01:07:04.680> are<01:07:04.799> the<01:07:04.859> validators<01:07:05.220> doing<01:07:05.520> the 01:07:05.630 --> 01:07:05.640 align:start position:0% and what are the validators doing the 01:07:05.640 --> 01:07:07.309 align:start position:0% and what are the validators doing the validators<01:07:06.059> basically<01:07:06.420> observe<01:07:06.900> the<01:07:07.020> Delta 01:07:07.309 --> 01:07:07.319 align:start position:0% validators basically observe the Delta 01:07:07.319 --> 01:07:08.809 align:start position:0% validators basically observe the Delta between<01:07:07.619> what<01:07:07.859> was<01:07:07.980> the<01:07:08.160> chain<01:07:08.280> before<01:07:08.520> and 01:07:08.809 --> 01:07:08.819 align:start position:0% between what was the chain before and 01:07:08.819 --> 01:07:09.950 align:start position:0% between what was the chain before and what<01:07:09.000> was 01:07:09.950 --> 01:07:09.960 align:start position:0% what was 01:07:09.960 --> 01:07:11.270 align:start position:0% what was um basically<01:07:10.319> the<01:07:10.500> result<01:07:10.680> after<01:07:11.039> the 01:07:11.270 --> 01:07:11.280 align:start position:0% um basically the result after the 01:07:11.280 --> 01:07:13.849 align:start position:0% um basically the result after the proposal<01:07:11.760> moved<01:07:12.059> and<01:07:12.720> then<01:07:12.839> they<01:07:13.500> can<01:07:13.619> make<01:07:13.740> it 01:07:13.849 --> 01:07:13.859 align:start position:0% proposal moved and then they can make it 01:07:13.859 --> 01:07:15.829 align:start position:0% proposal moved and then they can make it they<01:07:14.280> have<01:07:14.400> to<01:07:14.520> make<01:07:14.579> a<01:07:14.760> decision<01:07:15.000> on<01:07:15.299> a<01:07:15.539> voting 01:07:15.829 --> 01:07:15.839 align:start position:0% they have to make a decision on a voting 01:07:15.839 --> 01:07:17.690 align:start position:0% they have to make a decision on a voting decision<01:07:16.079> on<01:07:16.319> what<01:07:16.859> do<01:07:17.039> they<01:07:17.220> think<01:07:17.339> is<01:07:17.579> the 01:07:17.690 --> 01:07:17.700 align:start position:0% decision on what do they think is the 01:07:17.700 --> 01:07:20.870 align:start position:0% decision on what do they think is the legitimate<01:07:18.119> head<01:07:18.380> of<01:07:19.380> that<01:07:20.220> chain<01:07:20.579> and 01:07:20.870 --> 01:07:20.880 align:start position:0% legitimate head of that chain and 01:07:20.880 --> 01:07:22.190 align:start position:0% legitimate head of that chain and legitimate<01:07:21.299> obviously<01:07:21.660> in<01:07:21.780> the<01:07:21.900> sense<01:07:22.020> if 01:07:22.190 --> 01:07:22.200 align:start position:0% legitimate obviously in the sense if 01:07:22.200 --> 01:07:23.750 align:start position:0% legitimate obviously in the sense if they<01:07:22.319> are<01:07:22.440> trying<01:07:22.559> to<01:07:22.680> be<01:07:22.859> honest<01:07:23.160> and<01:07:23.460> are<01:07:23.640> not 01:07:23.750 --> 01:07:23.760 align:start position:0% they are trying to be honest and are not 01:07:23.760 --> 01:07:26.750 align:start position:0% they are trying to be honest and are not malicious 01:07:26.750 --> 01:07:26.760 align:start position:0% 01:07:26.760 --> 01:07:28.910 align:start position:0% okay<01:07:27.240> so<01:07:27.660> this<01:07:27.900> would<01:07:28.079> be<01:07:28.260> one<01:07:28.440> example<01:07:28.680> of<01:07:28.799> how 01:07:28.910 --> 01:07:28.920 align:start position:0% okay so this would be one example of how 01:07:28.920 --> 01:07:30.349 align:start position:0% okay so this would be one example of how this<01:07:29.099> looks<01:07:29.339> like<01:07:29.460> what<01:07:29.700> is<01:07:29.880> the<01:07:30.000> underlying 01:07:30.349 --> 01:07:30.359 align:start position:0% this looks like what is the underlying 01:07:30.359 --> 01:07:31.309 align:start position:0% this looks like what is the underlying data<01:07:30.660> type 01:07:31.309 --> 01:07:31.319 align:start position:0% data type 01:07:31.319 --> 01:07:32.630 align:start position:0% data type um<01:07:31.380> it<01:07:31.500> has<01:07:31.740> we'll<01:07:31.980> be<01:07:32.160> using<01:07:32.339> Haskell 01:07:32.630 --> 01:07:32.640 align:start position:0% um it has we'll be using Haskell 01:07:32.640 --> 01:07:34.250 align:start position:0% um it has we'll be using Haskell obviously<01:07:33.000> in<01:07:33.180> Haskell<01:07:33.539> this<01:07:33.720> will<01:07:33.839> be<01:07:33.960> what 01:07:34.250 --> 01:07:34.260 align:start position:0% obviously in Haskell this will be what 01:07:34.260 --> 01:07:35.870 align:start position:0% obviously in Haskell this will be what is<01:07:34.440> called<01:07:34.559> an<01:07:34.680> algebraic<01:07:35.099> graph<01:07:35.400> it's<01:07:35.640> just<01:07:35.819> a 01:07:35.870 --> 01:07:35.880 align:start position:0% is called an algebraic graph it's just a 01:07:35.880 --> 01:07:37.970 align:start position:0% is called an algebraic graph it's just a simple<01:07:36.059> graph<01:07:36.480> here 01:07:37.970 --> 01:07:37.980 align:start position:0% simple graph here 01:07:37.980 --> 01:07:40.490 align:start position:0% simple graph here um each<01:07:38.280> block<01:07:38.520> has<01:07:39.180> two<01:07:39.420> information<01:07:39.720> namely 01:07:40.490 --> 01:07:40.500 align:start position:0% um each block has two information namely 01:07:40.500 --> 01:07:42.950 align:start position:0% um each block has two information namely an<01:07:40.740> ID<01:07:40.859> and<01:07:41.460> then<01:07:41.579> votes<01:07:42.059> in<01:07:42.539> that<01:07:42.720> specific 01:07:42.950 --> 01:07:42.960 align:start position:0% an ID and then votes in that specific 01:07:42.960 --> 01:07:44.630 align:start position:0% an ID and then votes in that specific example<01:07:43.380> here<01:07:43.559> this<01:07:43.740> would<01:07:43.980> be<01:07:44.099> kind<01:07:44.400> of<01:07:44.520> the 01:07:44.630 --> 01:07:44.640 align:start position:0% example here this would be kind of the 01:07:44.640 --> 01:07:46.789 align:start position:0% example here this would be kind of the ideal<01:07:44.940> world<01:07:45.119> we<01:07:45.480> started<01:07:45.780> with<01:07:46.020> I'm<01:07:46.500> block 01:07:46.789 --> 01:07:46.799 align:start position:0% ideal world we started with I'm block 01:07:46.799 --> 01:07:49.730 align:start position:0% ideal world we started with I'm block one<01:07:47.099> built<01:07:48.059> on<01:07:48.119> on<01:07:48.420> that<01:07:48.660> block<01:07:49.020> two<01:07:49.319> and<01:07:49.500> so<01:07:49.619> on 01:07:49.730 --> 01:07:49.740 align:start position:0% one built on on that block two and so on 01:07:49.740 --> 01:07:51.529 align:start position:0% one built on on that block two and so on have<01:07:49.920> a<01:07:50.039> linear<01:07:50.280> chain<01:07:50.460> the<01:07:50.940> votes<01:07:51.240> are<01:07:51.420> in 01:07:51.529 --> 01:07:51.539 align:start position:0% have a linear chain the votes are in 01:07:51.539 --> 01:07:54.410 align:start position:0% have a linear chain the votes are in everything<01:07:52.079> looks<01:07:52.500> fine<01:07:53.099> okay<01:07:53.339> now<01:07:54.180> if<01:07:54.299> you 01:07:54.410 --> 01:07:54.420 align:start position:0% everything looks fine okay now if you 01:07:54.420 --> 01:07:56.089 align:start position:0% everything looks fine okay now if you take<01:07:54.539> that<01:07:54.720> as<01:07:54.900> a<01:07:55.079> specific<01:07:55.319> input<01:07:55.680> for<01:07:55.859> one 01:07:56.089 --> 01:07:56.099 align:start position:0% take that as a specific input for one 01:07:56.099 --> 01:07:57.890 align:start position:0% take that as a specific input for one period<01:07:56.520> let's<01:07:56.940> say<01:07:57.119> this<01:07:57.359> system<01:07:57.480> you<01:07:57.780> know 01:07:57.890 --> 01:07:57.900 align:start position:0% period let's say this system you know 01:07:57.900 --> 01:08:00.529 align:start position:0% period let's say this system you know now<01:07:58.140> is<01:07:58.319> period<01:07:58.740> four<01:07:58.920> coming<01:07:59.240> what<01:08:00.240> will<01:08:00.359> be 01:08:00.529 --> 01:08:00.539 align:start position:0% now is period four coming what will be 01:08:00.539 --> 01:08:02.569 align:start position:0% now is period four coming what will be the<01:08:00.660> action<01:08:00.839> of<01:08:01.020> The<01:08:01.140> Proposal<01:08:01.680> The<01:08:02.099> Proposal 01:08:02.569 --> 01:08:02.579 align:start position:0% the action of The Proposal The Proposal 01:08:02.579 --> 01:08:04.609 align:start position:0% the action of The Proposal The Proposal will<01:08:02.819> basically<01:08:03.660> um<01:08:03.660> say<01:08:04.020> yeah<01:08:04.200> I<01:08:04.440> want<01:08:04.500> to 01:08:04.609 --> 01:08:04.619 align:start position:0% will basically um say yeah I want to 01:08:04.619 --> 01:08:06.470 align:start position:0% will basically um say yeah I want to build<01:08:04.740> on<01:08:04.920> that<01:08:05.099> chain<01:08:05.280> I'm<01:08:05.819> choosing<01:08:06.240> in<01:08:06.359> that 01:08:06.470 --> 01:08:06.480 align:start position:0% build on that chain I'm choosing in that 01:08:06.480 --> 01:08:08.150 align:start position:0% build on that chain I'm choosing in that case<01:08:06.660> I'm<01:08:06.900> choosing 01:08:08.150 --> 01:08:08.160 align:start position:0% case I'm choosing 01:08:08.160 --> 01:08:10.910 align:start position:0% case I'm choosing um<01:08:08.220> ID3<01:08:08.880> which<01:08:09.599> is<01:08:10.020> the<01:08:10.140> legitimate<01:08:10.619> hat 01:08:10.910 --> 01:08:10.920 align:start position:0% um ID3 which is the legitimate hat 01:08:10.920 --> 01:08:12.710 align:start position:0% um ID3 which is the legitimate hat according<01:08:11.819> to<01:08:11.880> the<01:08:12.000> protocol<01:08:12.240> that<01:08:12.480> we<01:08:12.599> are 01:08:12.710 --> 01:08:12.720 align:start position:0% according to the protocol that we are 01:08:12.720 --> 01:08:14.510 align:start position:0% according to the protocol that we are interested<01:08:12.960> in<01:08:13.140> at<01:08:13.859> that<01:08:14.039> moment<01:08:14.160> he<01:08:14.339> makes 01:08:14.510 --> 01:08:14.520 align:start position:0% interested in at that moment he makes 01:08:14.520 --> 01:08:16.669 align:start position:0% interested in at that moment he makes the<01:08:14.700> decision<01:08:15.000> that<01:08:15.599> block<01:08:15.780> gets<01:08:16.259> appended 01:08:16.669 --> 01:08:16.679 align:start position:0% the decision that block gets appended 01:08:16.679 --> 01:08:20.030 align:start position:0% the decision that block gets appended but<01:08:16.920> there<01:08:17.100> are<01:08:17.279> no<01:08:17.400> no<01:08:17.640> votes<01:08:18.060> yet<01:08:18.239> and<01:08:18.660> then 01:08:20.030 --> 01:08:20.040 align:start position:0% but there are no no votes yet and then 01:08:20.040 --> 01:08:23.269 align:start position:0% but there are no no votes yet and then the<01:08:20.460> validators<01:08:20.940> come<01:08:21.179> in<01:08:21.359> they<01:08:21.960> observe<01:08:22.560> the 01:08:23.269 --> 01:08:23.279 align:start position:0% the validators come in they observe the 01:08:23.279 --> 01:08:25.309 align:start position:0% the validators come in they observe the ID<01:08:23.460> which<01:08:23.940> was<01:08:24.120> proposed<01:08:24.660> and<01:08:24.960> then<01:08:25.080> they<01:08:25.259> can 01:08:25.309 --> 01:08:25.319 align:start position:0% ID which was proposed and then they can 01:08:25.319 --> 01:08:26.510 align:start position:0% ID which was proposed and then they can cast<01:08:25.500> their<01:08:25.679> vote<01:08:25.859> and<01:08:26.040> in<01:08:26.160> this<01:08:26.279> case<01:08:26.339> here 01:08:26.510 --> 01:08:26.520 align:start position:0% cast their vote and in this case here 01:08:26.520 --> 01:08:27.769 align:start position:0% cast their vote and in this case here they<01:08:26.699> will<01:08:26.819> do<01:08:26.940> everything<01:08:27.120> is<01:08:27.359> very<01:08:27.600> nice 01:08:27.769 --> 01:08:27.779 align:start position:0% they will do everything is very nice 01:08:27.779 --> 01:08:29.870 align:start position:0% they will do everything is very nice yeah<01:08:27.960> this<01:08:28.319> is<01:08:28.440> the<01:08:28.560> this<01:08:29.279> is<01:08:29.460> a<01:08:29.520> really<01:08:29.699> nice 01:08:29.870 --> 01:08:29.880 align:start position:0% yeah this is the this is a really nice 01:08:29.880 --> 01:08:31.550 align:start position:0% yeah this is the this is a really nice World<01:08:30.060> here 01:08:31.550 --> 01:08:31.560 align:start position:0% World here 01:08:31.560 --> 01:08:32.570 align:start position:0% World here okay 01:08:32.570 --> 01:08:32.580 align:start position:0% okay 01:08:32.580 --> 01:08:35.209 align:start position:0% okay um however<01:08:33.560> sometimes<01:08:34.560> things<01:08:34.799> are<01:08:34.980> not<01:08:35.040> so 01:08:35.209 --> 01:08:35.219 align:start position:0% um however sometimes things are not so 01:08:35.219 --> 01:08:36.410 align:start position:0% um however sometimes things are not so easy 01:08:36.410 --> 01:08:36.420 align:start position:0% easy 01:08:36.420 --> 01:08:38.689 align:start position:0% easy um<01:08:36.620> specifically<01:08:37.620> if<01:08:37.859> uh<01:08:38.279> if<01:08:38.460> you<01:08:38.580> know 01:08:38.689 --> 01:08:38.699 align:start position:0% um specifically if uh if you know 01:08:38.699 --> 01:08:39.829 align:start position:0% um specifically if uh if you know everything<01:08:38.819> would<01:08:39.060> be<01:08:39.179> deterministic<01:08:39.660> then 01:08:39.829 --> 01:08:39.839 align:start position:0% everything would be deterministic then 01:08:39.839 --> 01:08:41.030 align:start position:0% everything would be deterministic then obviously<01:08:40.140> all<01:08:40.259> the<01:08:40.380> problems<01:08:40.620> will<01:08:40.799> go<01:08:40.920> away 01:08:41.030 --> 01:08:41.040 align:start position:0% obviously all the problems will go away 01:08:41.040 --> 01:08:42.530 align:start position:0% obviously all the problems will go away but<01:08:41.279> you<01:08:41.400> have<01:08:41.520> networks<01:08:41.819> issue<01:08:42.120> in<01:08:42.239> reality 01:08:42.530 --> 01:08:42.540 align:start position:0% but you have networks issue in reality 01:08:42.540 --> 01:08:44.329 align:start position:0% but you have networks issue in reality which<01:08:42.839> means<01:08:43.140> the<01:08:43.500> staking<01:08:43.799> Protocols<01:08:44.279> are 01:08:44.329 --> 01:08:44.339 align:start position:0% which means the staking Protocols are 01:08:44.339 --> 01:08:45.410 align:start position:0% which means the staking Protocols are hard<01:08:44.520> you<01:08:44.699> have<01:08:44.819> to<01:08:44.880> think<01:08:45.000> about<01:08:45.179> certain 01:08:45.410 --> 01:08:45.420 align:start position:0% hard you have to think about certain 01:08:45.420 --> 01:08:47.390 align:start position:0% hard you have to think about certain problems<01:08:45.900> one<01:08:46.560> of<01:08:46.679> the<01:08:46.799> problems<01:08:47.100> could<01:08:47.279> be 01:08:47.390 --> 01:08:47.400 align:start position:0% problems one of the problems could be 01:08:47.400 --> 01:08:49.430 align:start position:0% problems one of the problems could be that<01:08:48.000> um<01:08:48.000> what<01:08:48.299> if<01:08:48.540> there<01:08:48.719> is<01:08:48.839> time<01:08:49.080> lag 01:08:49.430 --> 01:08:49.440 align:start position:0% that um what if there is time lag 01:08:49.440 --> 01:08:52.610 align:start position:0% that um what if there is time lag between<01:08:49.980> the<01:08:50.940> proposal<01:08:51.540> and<01:08:51.779> the<01:08:51.900> tester<01:08:52.319> and 01:08:52.610 --> 01:08:52.620 align:start position:0% between the proposal and the tester and 01:08:52.620 --> 01:08:54.890 align:start position:0% between the proposal and the tester and what<01:08:52.739> happens<01:08:52.920> if<01:08:53.339> this<01:08:54.120> is<01:08:54.179> an<01:08:54.359> example<01:08:54.600> here 01:08:54.890 --> 01:08:54.900 align:start position:0% what happens if this is an example here 01:08:54.900 --> 01:08:58.669 align:start position:0% what happens if this is an example here there<01:08:55.799> was<01:08:55.980> a<01:08:56.699> proposal<01:08:57.540> in<01:08:57.719> period<01:08:58.020> four<01:08:58.259> and 01:08:58.669 --> 01:08:58.679 align:start position:0% there was a proposal in period four and 01:08:58.679 --> 01:09:00.229 align:start position:0% there was a proposal in period four and he's<01:08:58.859> actually<01:08:59.040> malicious<01:08:59.640> he's<01:09:00.000> just 01:09:00.229 --> 01:09:00.239 align:start position:0% he's actually malicious he's just 01:09:00.239 --> 01:09:01.910 align:start position:0% he's actually malicious he's just letting<01:09:00.660> time<01:09:00.839> pass<01:09:01.080> by 01:09:01.910 --> 01:09:01.920 align:start position:0% letting time pass by 01:09:01.920 --> 01:09:03.950 align:start position:0% letting time pass by at<01:09:02.460> some<01:09:02.640> point<01:09:02.759> proposal<01:09:03.420> from<01:09:03.600> The<01:09:03.839> Next 01:09:03.950 --> 01:09:03.960 align:start position:0% at some point proposal from The Next 01:09:03.960 --> 01:09:04.910 align:start position:0% at some point proposal from The Next Period 01:09:04.910 --> 01:09:04.920 align:start position:0% Period 01:09:04.920 --> 01:09:07.249 align:start position:0% Period observes<01:09:05.759> the<01:09:05.880> chain<01:09:06.060> thinks<01:09:06.839> okay<01:09:06.960> the<01:09:07.140> other 01:09:07.249 --> 01:09:07.259 align:start position:0% observes the chain thinks okay the other 01:09:07.259 --> 01:09:08.630 align:start position:0% observes the chain thinks okay the other guy<01:09:07.440> hasn't<01:09:07.679> done<01:09:07.739> anything<01:09:07.920> I'm<01:09:08.279> building<01:09:08.460> on 01:09:08.630 --> 01:09:08.640 align:start position:0% guy hasn't done anything I'm building on 01:09:08.640 --> 01:09:10.249 align:start position:0% guy hasn't done anything I'm building on the<01:09:08.819> chain<01:09:09.000> and<01:09:09.239> legitimately<01:09:09.779> you<01:09:10.080> know<01:09:10.140> he's 01:09:10.249 --> 01:09:10.259 align:start position:0% the chain and legitimately you know he's 01:09:10.259 --> 01:09:13.970 align:start position:0% the chain and legitimately you know he's honest<01:09:10.679> Builds<01:09:11.580> on<01:09:11.779> ID3<01:09:12.779> and<01:09:13.440> that<01:09:13.679> moment 01:09:13.970 --> 01:09:13.980 align:start position:0% honest Builds on ID3 and that moment 01:09:13.980 --> 01:09:16.070 align:start position:0% honest Builds on ID3 and that moment before<01:09:14.160> the<01:09:14.339> validators<01:09:14.759> come<01:09:15.000> in<01:09:15.179> I<01:09:15.660> said<01:09:15.839> the 01:09:16.070 --> 01:09:16.080 align:start position:0% before the validators come in I said the 01:09:16.080 --> 01:09:17.689 align:start position:0% before the validators come in I said the first<01:09:16.199> the<01:09:16.380> four<01:09:16.620> proposal<01:09:17.100> from<01:09:17.279> period<01:09:17.520> four 01:09:17.689 --> 01:09:17.699 align:start position:0% first the four proposal from period four 01:09:17.699 --> 01:09:20.390 align:start position:0% first the four proposal from period four actually<01:09:18.239> sneaks<01:09:18.779> in<01:09:18.900> and<01:09:19.500> places<01:09:19.739> in<01:09:19.980> all<01:09:20.160> his 01:09:20.390 --> 01:09:20.400 align:start position:0% actually sneaks in and places in all his 01:09:20.400 --> 01:09:22.610 align:start position:0% actually sneaks in and places in all his own<01:09:20.580> his<01:09:21.299> own 01:09:22.610 --> 01:09:22.620 align:start position:0% own his own 01:09:22.620 --> 01:09:23.209 align:start position:0% own his own um 01:09:23.209 --> 01:09:23.219 align:start position:0% um 01:09:23.219 --> 01:09:24.950 align:start position:0% um block<01:09:23.699> on<01:09:24.000> that<01:09:24.120> check<01:09:24.299> so<01:09:24.540> it's 01:09:24.950 --> 01:09:24.960 align:start position:0% block on that check so it's 01:09:24.960 --> 01:09:26.030 align:start position:0% block on that check so it's basically<01:09:25.199> and<01:09:25.380> now<01:09:25.500> the<01:09:25.620> question<01:09:25.739> is<01:09:25.859> what 01:09:26.030 --> 01:09:26.040 align:start position:0% basically and now the question is what 01:09:26.040 --> 01:09:28.729 align:start position:0% basically and now the question is what happens<01:09:26.219> this<01:09:27.120> is<01:09:27.239> one<01:09:27.359> of<01:09:27.420> the<01:09:27.540> motivating 01:09:28.729 --> 01:09:28.739 align:start position:0% happens this is one of the motivating 01:09:28.739 --> 01:09:31.070 align:start position:0% happens this is one of the motivating examples 01:09:31.070 --> 01:09:31.080 align:start position:0% examples 01:09:31.080 --> 01:09:33.050 align:start position:0% examples okay<01:09:31.679> do<01:09:31.980> you<01:09:32.160> have<01:09:32.219> questions<01:09:32.400> to<01:09:32.640> the<01:09:32.819> basic 01:09:33.050 --> 01:09:33.060 align:start position:0% okay do you have questions to the basic 01:09:33.060 --> 01:09:35.030 align:start position:0% okay do you have questions to the basic setup<01:09:33.420> more<01:09:33.900> details<01:09:34.319> to<01:09:34.380> follow 01:09:35.030 --> 01:09:35.040 align:start position:0% setup more details to follow 01:09:35.040 --> 01:09:39.050 align:start position:0% setup more details to follow okay 01:09:39.050 --> 01:09:39.060 align:start position:0% 01:09:39.060 --> 01:09:44.090 align:start position:0% um<01:09:39.120> if<01:09:39.420> not<01:09:39.600> let<01:09:40.560> me<01:09:40.679> jump<01:09:40.859> to 01:09:44.090 --> 01:09:44.100 align:start position:0% 01:09:44.100 --> 01:09:44.870 align:start position:0% um 01:09:44.870 --> 01:09:44.880 align:start position:0% um 01:09:44.880 --> 01:09:54.970 align:start position:0% um that's<01:09:45.719> not<01:09:45.839> really<01:09:46.020> looking<01:09:46.199> nice 01:09:54.970 --> 01:09:54.980 align:start position:0% 01:09:54.980 --> 01:09:57.110 align:start position:0% okay<01:09:55.980> can<01:09:56.280> you<01:09:56.460> read<01:09:56.580> this<01:09:56.699> should<01:09:56.940> I<01:09:57.060> increase 01:09:57.110 --> 01:09:57.120 align:start position:0% okay can you read this should I increase 01:09:57.120 --> 01:09:59.630 align:start position:0% okay can you read this should I increase the<01:09:57.360> fund<01:09:57.660> is<01:09:57.780> it 01:09:59.630 --> 01:09:59.640 align:start position:0% the fund is it 01:09:59.640 --> 01:10:08.990 align:start position:0% the fund is it okay 01:10:08.990 --> 01:10:09.000 align:start position:0% 01:10:09.000 --> 01:10:10.970 align:start position:0% okay 01:10:10.970 --> 01:10:10.980 align:start position:0% okay 01:10:10.980 --> 01:10:12.470 align:start position:0% okay um left<01:10:11.280> hand<01:10:11.460> side<01:10:11.640> is<01:10:11.880> basically<01:10:12.120> the<01:10:12.360> model 01:10:12.470 --> 01:10:12.480 align:start position:0% um left hand side is basically the model 01:10:12.480 --> 01:10:13.610 align:start position:0% um left hand side is basically the model right<01:10:12.780> hand<01:10:12.900> side<01:10:13.080> will<01:10:13.260> be<01:10:13.380> just<01:10:13.500> an 01:10:13.610 --> 01:10:13.620 align:start position:0% right hand side will be just an 01:10:13.620 --> 01:10:15.530 align:start position:0% right hand side will be just an interactive<01:10:13.980> session<01:10:14.160> that<01:10:14.340> I<01:10:14.460> will<01:10:14.580> be<01:10:14.699> using 01:10:15.530 --> 01:10:15.540 align:start position:0% interactive session that I will be using 01:10:15.540 --> 01:10:16.430 align:start position:0% interactive session that I will be using um 01:10:16.430 --> 01:10:16.440 align:start position:0% um 01:10:16.440 --> 01:10:18.709 align:start position:0% um let<01:10:16.800> me<01:10:16.980> start<01:10:17.100> with<01:10:17.280> something<01:10:17.460> first 01:10:18.709 --> 01:10:18.719 align:start position:0% let me start with something first 01:10:18.719 --> 01:10:19.310 align:start position:0% let me start with something first um 01:10:19.310 --> 01:10:19.320 align:start position:0% um 01:10:19.320 --> 01:10:21.350 align:start position:0% um in<01:10:19.679> order<01:10:19.800> to<01:10:19.980> implement<01:10:20.219> the<01:10:20.460> model 01:10:21.350 --> 01:10:21.360 align:start position:0% in order to implement the model 01:10:21.360 --> 01:10:22.669 align:start position:0% in order to implement the model you<01:10:21.659> need<01:10:21.780> a<01:10:21.900> lot<01:10:22.020> of<01:10:22.140> background<01:10:22.380> information 01:10:22.669 --> 01:10:22.679 align:start position:0% you need a lot of background information 01:10:22.679 --> 01:10:24.229 align:start position:0% you need a lot of background information right<01:10:23.219> I<01:10:23.460> need<01:10:23.640> to<01:10:23.760> actually<01:10:23.880> think<01:10:24.120> about 01:10:24.229 --> 01:10:24.239 align:start position:0% right I need to actually think about 01:10:24.239 --> 01:10:26.510 align:start position:0% right I need to actually think about what's<01:10:24.659> the<01:10:24.840> data<01:10:25.080> type<01:10:25.140> of<01:10:25.260> the<01:10:25.440> chain 01:10:26.510 --> 01:10:26.520 align:start position:0% what's the data type of the chain 01:10:26.520 --> 01:10:28.430 align:start position:0% what's the data type of the chain if<01:10:27.000> there<01:10:27.179> is<01:10:27.300> a<01:10:27.420> new<01:10:27.540> block<01:10:27.780> being<01:10:28.020> proposed 01:10:28.430 --> 01:10:28.440 align:start position:0% if there is a new block being proposed 01:10:28.440 --> 01:10:30.290 align:start position:0% if there is a new block being proposed how<01:10:28.620> do<01:10:28.800> I<01:10:28.920> actually<01:10:29.040> edit 01:10:30.290 --> 01:10:30.300 align:start position:0% how do I actually edit 01:10:30.300 --> 01:10:32.030 align:start position:0% how do I actually edit um<01:10:30.420> this<01:10:30.960> for<01:10:31.140> instance<01:10:31.320> this<01:10:31.500> function<01:10:31.800> here 01:10:32.030 --> 01:10:32.040 align:start position:0% um this for instance this function here 01:10:32.040 --> 01:10:33.830 align:start position:0% um this for instance this function here at<01:10:32.280> the<01:10:32.520> chain 01:10:33.830 --> 01:10:33.840 align:start position:0% at the chain 01:10:33.840 --> 01:10:35.450 align:start position:0% at the chain um<01:10:33.900> it's<01:10:34.500> just<01:10:34.620> observing<01:10:35.040> a<01:10:35.159> chain<01:10:35.280> it's 01:10:35.450 --> 01:10:35.460 align:start position:0% um it's just observing a chain it's 01:10:35.460 --> 01:10:37.010 align:start position:0% um it's just observing a chain it's observing<01:10:35.820> an<01:10:35.940> ID<01:10:36.060> which<01:10:36.300> was<01:10:36.480> proposed<01:10:36.900> and 01:10:37.010 --> 01:10:37.020 align:start position:0% observing an ID which was proposed and 01:10:37.020 --> 01:10:38.870 align:start position:0% observing an ID which was proposed and it's<01:10:37.140> you<01:10:37.320> know<01:10:37.380> creating<01:10:37.620> a<01:10:37.800> new<01:10:37.920> chain<01:10:38.100> so<01:10:38.760> I 01:10:38.870 --> 01:10:38.880 align:start position:0% it's you know creating a new chain so I 01:10:38.880 --> 01:10:40.189 align:start position:0% it's you know creating a new chain so I lead<01:10:39.120> them<01:10:39.300> I<01:10:39.540> need<01:10:39.600> a<01:10:39.719> lot<01:10:39.840> of<01:10:39.900> background 01:10:40.189 --> 01:10:40.199 align:start position:0% lead them I need a lot of background 01:10:40.199 --> 01:10:42.229 align:start position:0% lead them I need a lot of background stuff<01:10:40.560> in<01:10:41.340> order<01:10:41.460> to<01:10:41.640> make<01:10:41.760> this<01:10:41.880> model<01:10:42.060> work 01:10:42.229 --> 01:10:42.239 align:start position:0% stuff in order to make this model work 01:10:42.239 --> 01:10:43.970 align:start position:0% stuff in order to make this model work which<01:10:42.480> is<01:10:42.659> just<01:10:42.840> basically<01:10:43.140> you<01:10:43.500> know<01:10:43.560> Haskell 01:10:43.970 --> 01:10:43.980 align:start position:0% which is just basically you know Haskell 01:10:43.980 --> 01:10:45.530 align:start position:0% which is just basically you know Haskell in<01:10:44.159> that<01:10:44.280> sense<01:10:44.400> Haskell<01:10:44.760> functions<01:10:45.179> and 01:10:45.530 --> 01:10:45.540 align:start position:0% in that sense Haskell functions and 01:10:45.540 --> 01:10:47.390 align:start position:0% in that sense Haskell functions and computations<01:10:46.080> another<01:10:46.739> one<01:10:47.040> would<01:10:47.159> be<01:10:47.280> for 01:10:47.390 --> 01:10:47.400 align:start position:0% computations another one would be for 01:10:47.400 --> 01:10:49.310 align:start position:0% computations another one would be for instance<01:10:47.580> determine<01:10:48.060> head<01:10:48.239> I'm<01:10:48.719> clearly<01:10:49.140> in 01:10:49.310 --> 01:10:49.320 align:start position:0% instance determine head I'm clearly in 01:10:49.320 --> 01:10:51.110 align:start position:0% instance determine head I'm clearly in order<01:10:49.440> for<01:10:49.739> the<01:10:49.860> protocol<01:10:50.100> to<01:10:50.400> work<01:10:50.580> which<01:10:50.940> has 01:10:51.110 --> 01:10:51.120 align:start position:0% order for the protocol to work which has 01:10:51.120 --> 01:10:52.729 align:start position:0% order for the protocol to work which has a<01:10:51.239> certain<01:10:51.420> goal 01:10:52.729 --> 01:10:52.739 align:start position:0% a certain goal 01:10:52.739 --> 01:10:54.169 align:start position:0% a certain goal um<01:10:52.800> I<01:10:53.040> need<01:10:53.159> to<01:10:53.280> be<01:10:53.400> able<01:10:53.580> to<01:10:53.699> at<01:10:53.820> each<01:10:54.000> point 01:10:54.169 --> 01:10:54.179 align:start position:0% um I need to be able to at each point 01:10:54.179 --> 01:10:55.910 align:start position:0% um I need to be able to at each point say<01:10:54.420> what<01:10:54.540> are<01:10:54.659> the<01:10:54.780> hat<01:10:55.080> or<01:10:55.380> the<01:10:55.500> heads<01:10:55.800> if 01:10:55.910 --> 01:10:55.920 align:start position:0% say what are the hat or the heads if 01:10:55.920 --> 01:10:58.669 align:start position:0% say what are the hat or the heads if they<01:10:56.100> are<01:10:56.280> non-determinate<01:10:57.420> and<01:10:58.260> this<01:10:58.500> is 01:10:58.669 --> 01:10:58.679 align:start position:0% they are non-determinate and this is 01:10:58.679 --> 01:10:59.810 align:start position:0% they are non-determinate and this is basically<01:10:58.860> the<01:10:59.040> second<01:10:59.219> function<01:10:59.460> what<01:10:59.640> it's 01:10:59.810 --> 01:10:59.820 align:start position:0% basically the second function what it's 01:10:59.820 --> 01:11:01.010 align:start position:0% basically the second function what it's doing<01:11:00.000> and<01:11:00.120> there's<01:11:00.239> a<01:11:00.480> lot<01:11:00.540> of<01:11:00.659> other<01:11:00.780> stuff 01:11:01.010 --> 01:11:01.020 align:start position:0% doing and there's a lot of other stuff 01:11:01.020 --> 01:11:02.630 align:start position:0% doing and there's a lot of other stuff that<01:11:01.199> I'm<01:11:01.320> not<01:11:01.440> showing<01:11:01.679> you 01:11:02.630 --> 01:11:02.640 align:start position:0% that I'm not showing you 01:11:02.640 --> 01:11:04.669 align:start position:0% that I'm not showing you um<01:11:02.699> that<01:11:03.120> comes<01:11:03.420> in<01:11:03.480> so<01:11:03.719> you<01:11:03.840> need<01:11:04.020> for<01:11:04.199> that<01:11:04.380> in 01:11:04.669 --> 01:11:04.679 align:start position:0% um that comes in so you need for that in 01:11:04.679 --> 01:11:07.550 align:start position:0% um that comes in so you need for that in order<01:11:04.800> to<01:11:05.040> kind<01:11:05.340> of<01:11:05.400> use<01:11:06.000> this<01:11:06.179> you<01:11:06.480> need<01:11:06.659> first 01:11:07.550 --> 01:11:07.560 align:start position:0% order to kind of use this you need first 01:11:07.560 --> 01:11:09.410 align:start position:0% order to kind of use this you need first this<01:11:08.400> um<01:11:08.400> the<01:11:08.640> structure<01:11:08.940> in<01:11:09.060> order<01:11:09.179> to 01:11:09.410 --> 01:11:09.420 align:start position:0% this um the structure in order to 01:11:09.420 --> 01:11:11.149 align:start position:0% this um the structure in order to basically<01:11:10.020> I'll<01:11:10.380> say<01:11:10.500> that<01:11:10.739> this<01:11:10.980> is<01:11:11.100> the 01:11:11.149 --> 01:11:11.159 align:start position:0% basically I'll say that this is the 01:11:11.159 --> 01:11:12.350 align:start position:0% basically I'll say that this is the computational<01:11:11.520> background<01:11:11.880> to<01:11:12.060> which<01:11:12.239> I'm 01:11:12.350 --> 01:11:12.360 align:start position:0% computational background to which I'm 01:11:12.360 --> 01:11:13.250 align:start position:0% computational background to which I'm working 01:11:13.250 --> 01:11:13.260 align:start position:0% working 01:11:13.260 --> 01:11:15.470 align:start position:0% working now<01:11:13.560> you<01:11:13.679> might<01:11:13.800> wonder<01:11:13.980> okay<01:11:14.280> for<01:11:15.060> you<01:11:15.360> know 01:11:15.470 --> 01:11:15.480 align:start position:0% now you might wonder okay for you know 01:11:15.480 --> 01:11:17.090 align:start position:0% now you might wonder okay for you know it<01:11:15.840> wouldn't<01:11:16.140> it<01:11:16.320> be<01:11:16.380> nice<01:11:16.500> if<01:11:16.739> this<01:11:16.860> would<01:11:17.040> be 01:11:17.090 --> 01:11:17.100 align:start position:0% it wouldn't it be nice if this would be 01:11:17.100 --> 01:11:19.189 align:start position:0% it wouldn't it be nice if this would be coming<01:11:17.280> from<01:11:17.460> the<01:11:17.580> outside<01:11:17.699> world<01:11:18.120> and<01:11:18.840> indeed 01:11:19.189 --> 01:11:19.199 align:start position:0% coming from the outside world and indeed 01:11:19.199 --> 01:11:20.990 align:start position:0% coming from the outside world and indeed for<01:11:19.860> some<01:11:19.980> problems<01:11:20.340> you<01:11:20.520> just<01:11:20.699> need<01:11:20.820> to 01:11:20.990 --> 01:11:21.000 align:start position:0% for some problems you just need to 01:11:21.000 --> 01:11:22.910 align:start position:0% for some problems you just need to create<01:11:21.120> it<01:11:21.360> but<01:11:21.780> in<01:11:21.960> other<01:11:22.080> cases<01:11:22.440> and<01:11:22.679> this<01:11:22.860> is 01:11:22.910 --> 01:11:22.920 align:start position:0% create it but in other cases and this is 01:11:22.920 --> 01:11:24.770 align:start position:0% create it but in other cases and this is something<01:11:23.100> we'll<01:11:23.340> be<01:11:23.520> working<01:11:23.699> with<01:11:23.940> in<01:11:24.659> the 01:11:24.770 --> 01:11:24.780 align:start position:0% something we'll be working with in the 01:11:24.780 --> 01:11:27.470 align:start position:0% something we'll be working with in the future<01:11:24.840> or<01:11:25.140> towards<01:11:25.560> is<01:11:26.040> can<01:11:26.760> part<01:11:27.060> of<01:11:27.239> that 01:11:27.470 --> 01:11:27.480 align:start position:0% future or towards is can part of that 01:11:27.480 --> 01:11:28.970 align:start position:0% future or towards is can part of that basic<01:11:27.900> infrastructure<01:11:28.500> that<01:11:28.739> we<01:11:28.860> are 01:11:28.970 --> 01:11:28.980 align:start position:0% basic infrastructure that we are 01:11:28.980 --> 01:11:30.950 align:start position:0% basic infrastructure that we are interfacing<01:11:29.460> with<01:11:29.580> in<01:11:29.760> the<01:11:29.880> end<01:11:30.000> and<01:11:30.300> that<01:11:30.480> is 01:11:30.950 --> 01:11:30.960 align:start position:0% interfacing with in the end and that is 01:11:30.960 --> 01:11:32.149 align:start position:0% interfacing with in the end and that is actually<01:11:31.140> not<01:11:31.320> that<01:11:31.500> interesting<01:11:31.860> from<01:11:32.040> your 01:11:32.149 --> 01:11:32.159 align:start position:0% actually not that interesting from your 01:11:32.159 --> 01:11:33.770 align:start position:0% actually not that interesting from your modeling<01:11:32.520> perspective<01:11:32.880> it's<01:11:33.179> just<01:11:33.420> something 01:11:33.770 --> 01:11:33.780 align:start position:0% modeling perspective it's just something 01:11:33.780 --> 01:11:35.570 align:start position:0% modeling perspective it's just something you<01:11:33.960> want<01:11:34.080> to<01:11:34.199> take<01:11:34.320> as<01:11:34.440> given<01:11:34.739> can<01:11:35.460> you 01:11:35.570 --> 01:11:35.580 align:start position:0% you want to take as given can you 01:11:35.580 --> 01:11:37.070 align:start position:0% you want to take as given can you somehow<01:11:35.880> import<01:11:36.120> it<01:11:36.360> from<01:11:36.480> the<01:11:36.600> outside<01:11:36.719> world 01:11:37.070 --> 01:11:37.080 align:start position:0% somehow import it from the outside world 01:11:37.080 --> 01:11:38.630 align:start position:0% somehow import it from the outside world or<01:11:37.320> can<01:11:37.440> you<01:11:37.560> connect<01:11:37.679> this<01:11:37.980> tooling<01:11:38.400> to<01:11:38.520> the 01:11:38.630 --> 01:11:38.640 align:start position:0% or can you connect this tooling to the 01:11:38.640 --> 01:11:40.070 align:start position:0% or can you connect this tooling to the outside<01:11:38.760> world 01:11:40.070 --> 01:11:40.080 align:start position:0% outside world 01:11:40.080 --> 01:11:42.110 align:start position:0% outside world okay<01:11:40.739> for<01:11:41.100> this<01:11:41.219> purpose<01:11:41.520> here<01:11:41.699> I'm<01:11:41.940> just 01:11:42.110 --> 01:11:42.120 align:start position:0% okay for this purpose here I'm just 01:11:42.120 --> 01:11:43.790 align:start position:0% okay for this purpose here I'm just recreating<01:11:42.540> it 01:11:43.790 --> 01:11:43.800 align:start position:0% recreating it 01:11:43.800 --> 01:11:45.229 align:start position:0% recreating it um what<01:11:44.340> it<01:11:44.460> actually<01:11:44.580> does<01:11:44.760> is<01:11:44.940> not<01:11:45.120> so 01:11:45.229 --> 01:11:45.239 align:start position:0% um what it actually does is not so 01:11:45.239 --> 01:11:46.370 align:start position:0% um what it actually does is not so important<01:11:45.480> just<01:11:45.659> think<01:11:45.840> about<01:11:45.960> it<01:11:46.140> for<01:11:46.260> now 01:11:46.370 --> 01:11:46.380 align:start position:0% important just think about it for now 01:11:46.380 --> 01:11:47.689 align:start position:0% important just think about it for now what<01:11:46.560> the<01:11:46.679> behavior<01:11:46.980> is 01:11:47.689 --> 01:11:47.699 align:start position:0% what the behavior is 01:11:47.699 --> 01:11:49.250 align:start position:0% what the behavior is um of<01:11:47.940> air<01:11:48.060> chain<01:11:48.360> and<01:11:48.540> so<01:11:48.659> on<01:11:48.780> and<01:11:48.900> so<01:11:49.020> some 01:11:49.250 --> 01:11:49.260 align:start position:0% um of air chain and so on and so some 01:11:49.260 --> 01:11:52.070 align:start position:0% um of air chain and so on and so some functionality<01:11:49.739> I<01:11:49.920> will<01:11:50.040> explain<01:11:50.159> on<01:11:50.460> the<01:11:50.640> Fly 01:11:52.070 --> 01:11:52.080 align:start position:0% functionality I will explain on the Fly 01:11:52.080 --> 01:11:54.050 align:start position:0% functionality I will explain on the Fly good<01:11:52.500> these<01:11:52.980> are<01:11:53.040> all<01:11:53.159> functions<01:11:53.640> the<01:11:54.000> first 01:11:54.050 --> 01:11:54.060 align:start position:0% good these are all functions the first 01:11:54.060 --> 01:11:55.850 align:start position:0% good these are all functions the first thing<01:11:54.239> we<01:11:54.420> want<01:11:54.540> to<01:11:54.659> do<01:11:54.780> we<01:11:55.440> want<01:11:55.620> to<01:11:55.739> create 01:11:55.850 --> 01:11:55.860 align:start position:0% thing we want to do we want to create 01:11:55.860 --> 01:11:57.410 align:start position:0% thing we want to do we want to create basic<01:11:56.340> building<01:11:56.520> blocks<01:11:57.000> that<01:11:57.179> we'll<01:11:57.300> be 01:11:57.410 --> 01:11:57.420 align:start position:0% basic building blocks that we'll be 01:11:57.420 --> 01:11:59.870 align:start position:0% basic building blocks that we'll be relying<01:11:57.719> on<01:11:57.840> yeah<01:11:58.020> I<01:11:58.320> said<01:11:58.440> before<01:11:58.699> we'll<01:11:59.699> be 01:11:59.870 --> 01:11:59.880 align:start position:0% relying on yeah I said before we'll be 01:11:59.880 --> 01:12:02.030 align:start position:0% relying on yeah I said before we'll be making<01:12:00.000> it<01:12:00.239> here<01:12:00.600> really<01:12:00.900> really<01:12:01.080> kind<01:12:01.440> of<01:12:01.560> I'm 01:12:02.030 --> 01:12:02.040 align:start position:0% making it here really really kind of I'm 01:12:02.040 --> 01:12:03.649 align:start position:0% making it here really really kind of I'm fine-grained<01:12:02.580> in<01:12:02.760> a<01:12:02.880> sense<01:12:02.940> we<01:12:03.179> start<01:12:03.300> at<01:12:03.480> the 01:12:03.649 --> 01:12:03.659 align:start position:0% fine-grained in a sense we start at the 01:12:03.659 --> 01:12:05.090 align:start position:0% fine-grained in a sense we start at the real<01:12:03.780> bottom<01:12:04.199> of 01:12:05.090 --> 01:12:05.100 align:start position:0% real bottom of 01:12:05.100 --> 01:12:07.310 align:start position:0% real bottom of let's<01:12:05.520> make<01:12:05.820> add<01:12:06.420> to<01:12:06.600> chain<01:12:06.780> actually<01:12:07.020> an<01:12:07.199> open 01:12:07.310 --> 01:12:07.320 align:start position:0% let's make add to chain actually an open 01:12:07.320 --> 01:12:08.630 align:start position:0% let's make add to chain actually an open gate<01:12:07.620> put<01:12:07.860> it<01:12:07.980> into<01:12:08.100> a<01:12:08.280> computational 01:12:08.630 --> 01:12:08.640 align:start position:0% gate put it into a computational 01:12:08.640 --> 01:12:09.770 align:start position:0% gate put it into a computational framework<01:12:09.060> so<01:12:09.179> that<01:12:09.360> we<01:12:09.480> have<01:12:09.600> a<01:12:09.659> building 01:12:09.770 --> 01:12:09.780 align:start position:0% framework so that we have a building 01:12:09.780 --> 01:12:11.689 align:start position:0% framework so that we have a building block<01:12:10.020> that<01:12:10.199> we<01:12:10.320> can<01:12:10.440> move<01:12:10.560> around<01:12:10.739> if<01:12:11.400> we<01:12:11.520> want 01:12:11.689 --> 01:12:11.699 align:start position:0% block that we can move around if we want 01:12:11.699 --> 01:12:13.370 align:start position:0% block that we can move around if we want to<01:12:11.820> similarly<01:12:12.719> let's<01:12:12.900> do<01:12:13.140> that<01:12:13.199> for 01:12:13.370 --> 01:12:13.380 align:start position:0% to similarly let's do that for 01:12:13.380 --> 01:12:14.990 align:start position:0% to similarly let's do that for determined<01:12:13.860> head<01:12:13.980> maybe<01:12:14.400> we<01:12:14.580> needed<01:12:14.880> a 01:12:14.990 --> 01:12:15.000 align:start position:0% determined head maybe we needed a 01:12:15.000 --> 01:12:16.550 align:start position:0% determined head maybe we needed a different<01:12:15.120> points 01:12:16.550 --> 01:12:16.560 align:start position:0% different points 01:12:16.560 --> 01:12:18.470 align:start position:0% different points um<01:12:16.620> and<01:12:17.400> then<01:12:17.520> we<01:12:17.699> kind<01:12:17.880> of<01:12:17.940> have<01:12:18.060> this<01:12:18.179> billing 01:12:18.470 --> 01:12:18.480 align:start position:0% um and then we kind of have this billing 01:12:18.480 --> 01:12:21.649 align:start position:0% um and then we kind of have this billing clock<01:12:18.600> available<01:12:18.840> as<01:12:19.199> an<01:12:19.320> open<01:12:19.440> day<01:12:20.219> also<01:12:20.940> note 01:12:21.649 --> 01:12:21.659 align:start position:0% clock available as an open day also note 01:12:21.659 --> 01:12:23.689 align:start position:0% clock available as an open day also note essentially<01:12:22.440> for<01:12:22.739> the<01:12:22.980> whole<01:12:23.100> system<01:12:23.340> here 01:12:23.689 --> 01:12:23.699 align:start position:0% essentially for the whole system here 01:12:23.699 --> 01:12:26.149 align:start position:0% essentially for the whole system here the<01:12:24.480> protocol<01:12:24.719> logic<01:12:25.199> is<01:12:25.440> exclusively<01:12:26.040> in 01:12:26.149 --> 01:12:26.159 align:start position:0% the protocol logic is exclusively in 01:12:26.159 --> 01:12:27.649 align:start position:0% the protocol logic is exclusively in determined<01:12:26.580> head<01:12:26.640> this<01:12:27.120> is<01:12:27.239> this<01:12:27.420> function 01:12:27.649 --> 01:12:27.659 align:start position:0% determined head this is this function 01:12:27.659 --> 01:12:29.390 align:start position:0% determined head this is this function that<01:12:27.780> you<01:12:27.960> can<01:12:28.080> see<01:12:28.140> here<01:12:28.320> if<01:12:28.860> you<01:12:28.980> change<01:12:29.159> that 01:12:29.390 --> 01:12:29.400 align:start position:0% that you can see here if you change that 01:12:29.400 --> 01:12:31.550 align:start position:0% that you can see here if you change that all<01:12:29.699> the<01:12:29.820> rest<01:12:29.940> stays<01:12:30.360> intact<01:12:30.600> and<01:12:31.380> that's 01:12:31.550 --> 01:12:31.560 align:start position:0% all the rest stays intact and that's 01:12:31.560 --> 01:12:33.410 align:start position:0% all the rest stays intact and that's another<01:12:31.679> way<01:12:31.980> of<01:12:32.100> if<01:12:32.580> you<01:12:32.760> make<01:12:33.060> it<01:12:33.179> you<01:12:33.360> know 01:12:33.410 --> 01:12:33.420 align:start position:0% another way of if you make it you know 01:12:33.420 --> 01:12:34.610 align:start position:0% another way of if you make it you know if<01:12:33.540> you<01:12:33.659> try<01:12:33.780> to<01:12:33.900> approach<01:12:34.140> the<01:12:34.260> problem<01:12:34.440> in 01:12:34.610 --> 01:12:34.620 align:start position:0% if you try to approach the problem in 01:12:34.620 --> 01:12:36.830 align:start position:0% if you try to approach the problem in that<01:12:34.739> way<01:12:34.920> you<01:12:35.460> will<01:12:35.640> save<01:12:35.760> a<01:12:35.940> lot<01:12:36.000> of<01:12:36.120> redoing 01:12:36.830 --> 01:12:36.840 align:start position:0% that way you will save a lot of redoing 01:12:36.840 --> 01:12:38.090 align:start position:0% that way you will save a lot of redoing um<01:12:36.900> if<01:12:37.080> you<01:12:37.140> want<01:12:37.260> to<01:12:37.380> make<01:12:37.440> changes<01:12:37.800> to<01:12:37.920> the 01:12:38.090 --> 01:12:38.100 align:start position:0% um if you want to make changes to the 01:12:38.100 --> 01:12:40.370 align:start position:0% um if you want to make changes to the protocol 01:12:40.370 --> 01:12:40.380 align:start position:0% 01:12:40.380 --> 01:12:42.770 align:start position:0% okay 01:12:42.770 --> 01:12:42.780 align:start position:0% 01:12:42.780 --> 01:12:48.130 align:start position:0% um 01:12:48.130 --> 01:12:48.140 align:start position:0% 01:12:48.140 --> 01:12:51.169 align:start position:0% let<01:12:49.140> me<01:12:49.199> jump<01:12:49.440> here 01:12:51.169 --> 01:12:51.179 align:start position:0% let me jump here 01:12:51.179 --> 01:12:54.830 align:start position:0% let me jump here foreign 01:12:54.830 --> 01:12:54.840 align:start position:0% 01:12:54.840 --> 01:12:57.229 align:start position:0% okay<01:12:55.500> so<01:12:55.980> I<01:12:56.280> showed<01:12:56.520> you<01:12:56.580> the<01:12:56.760> the<01:12:56.940> function 01:12:57.229 --> 01:12:57.239 align:start position:0% okay so I showed you the the function 01:12:57.239 --> 01:12:58.669 align:start position:0% okay so I showed you the the function before 01:12:58.669 --> 01:12:58.679 align:start position:0% before 01:12:58.679 --> 01:12:59.630 align:start position:0% before um 01:12:59.630 --> 01:12:59.640 align:start position:0% um 01:12:59.640 --> 01:13:02.510 align:start position:0% um let<01:13:00.060> me<01:13:00.179> actually 01:13:02.510 --> 01:13:02.520 align:start position:0% 01:13:02.520 --> 01:13:05.630 align:start position:0% put<01:13:03.000> it<01:13:03.120> next<01:13:03.239> to<01:13:03.360> each<01:13:03.480> other<01:13:03.540> so 01:13:05.630 --> 01:13:05.640 align:start position:0% put it next to each other so 01:13:05.640 --> 01:13:08.870 align:start position:0% put it next to each other so add<01:13:06.000> to<01:13:06.239> Adblock<01:13:06.719> basically<01:13:07.140> is 01:13:08.870 --> 01:13:08.880 align:start position:0% add to Adblock basically is 01:13:08.880 --> 01:13:10.310 align:start position:0% add to Adblock basically is doing<01:13:09.300> nothing<01:13:09.540> else<01:13:09.780> it's<01:13:10.020> just<01:13:10.140> a 01:13:10.310 --> 01:13:10.320 align:start position:0% doing nothing else it's just a 01:13:10.320 --> 01:13:11.570 align:start position:0% doing nothing else it's just a computation 01:13:11.570 --> 01:13:11.580 align:start position:0% computation 01:13:11.580 --> 01:13:13.310 align:start position:0% computation um<01:13:11.640> it<01:13:11.880> observes<01:13:12.420> the<01:13:12.540> chain<01:13:12.719> old<01:13:13.020> and 01:13:13.310 --> 01:13:13.320 align:start position:0% um it observes the chain old and 01:13:13.320 --> 01:13:15.830 align:start position:0% um it observes the chain old and observes<01:13:13.739> an<01:13:13.860> ID<01:13:14.040> and<01:13:14.760> then<01:13:14.880> it<01:13:15.120> you<01:13:15.480> know<01:13:15.540> puts 01:13:15.830 --> 01:13:15.840 align:start position:0% observes an ID and then it you know puts 01:13:15.840 --> 01:13:17.689 align:start position:0% observes an ID and then it you know puts that<01:13:15.900> into<01:13:16.080> the<01:13:16.199> inputs<01:13:16.500> field<01:13:16.679> inside 01:13:17.689 --> 01:13:17.699 align:start position:0% that into the inputs field inside 01:13:17.699 --> 01:13:20.209 align:start position:0% that into the inputs field inside and<01:13:18.780> it's<01:13:19.199> basically<01:13:19.560> this<01:13:19.860> is<01:13:19.980> the<01:13:20.100> forward 01:13:20.209 --> 01:13:20.219 align:start position:0% and it's basically this is the forward 01:13:20.219 --> 01:13:22.370 align:start position:0% and it's basically this is the forward function<01:13:20.640> keyword<01:13:21.060> remember<01:13:21.780> we<01:13:22.080> had<01:13:22.199> the 01:13:22.370 --> 01:13:22.380 align:start position:0% function keyword remember we had the 01:13:22.380 --> 01:13:24.410 align:start position:0% function keyword remember we had the decision<01:13:22.560> and<01:13:22.860> basically<01:13:23.460> computation<01:13:23.880> this 01:13:24.410 --> 01:13:24.420 align:start position:0% decision and basically computation this 01:13:24.420 --> 01:13:26.990 align:start position:0% decision and basically computation this is<01:13:24.540> one<01:13:24.719> instance<01:13:24.960> of<01:13:25.140> the<01:13:25.260> computation<01:13:26.000> and 01:13:26.990 --> 01:13:27.000 align:start position:0% is one instance of the computation and 01:13:27.000 --> 01:13:28.550 align:start position:0% is one instance of the computation and then<01:13:27.120> it<01:13:27.300> does<01:13:27.420> just<01:13:27.659> the<01:13:27.900> add<01:13:28.080> chain<01:13:28.320> to 01:13:28.550 --> 01:13:28.560 align:start position:0% then it does just the add chain to 01:13:28.560 --> 01:13:30.649 align:start position:0% then it does just the add chain to weight<01:13:28.940> which<01:13:29.940> is 01:13:30.649 --> 01:13:30.659 align:start position:0% weight which is 01:13:30.659 --> 01:13:33.169 align:start position:0% weight which is uh<01:13:31.560> similar<01:13:32.100> to<01:13:32.520> what<01:13:32.640> we<01:13:32.760> have<01:13:32.880> on<01:13:33.060> the 01:13:33.169 --> 01:13:33.179 align:start position:0% uh similar to what we have on the 01:13:33.179 --> 01:13:35.090 align:start position:0% uh similar to what we have on the attitude<01:13:33.540> chain 01:13:35.090 --> 01:13:35.100 align:start position:0% attitude chain 01:13:35.100 --> 01:13:36.770 align:start position:0% attitude chain by<01:13:35.520> the<01:13:35.699> way<01:13:35.820> I<01:13:36.000> can<01:13:36.120> explain<01:13:36.300> in<01:13:36.600> a<01:13:36.659> minute 01:13:36.770 --> 01:13:36.780 align:start position:0% by the way I can explain in a minute 01:13:36.780 --> 01:13:38.330 align:start position:0% by the way I can explain in a minute yeah<01:13:37.140> but<01:13:37.320> it's<01:13:37.440> the<01:13:37.620> same<01:13:37.739> in<01:13:37.920> principle<01:13:38.159> it's 01:13:38.330 --> 01:13:38.340 align:start position:0% yeah but it's the same in principle it's 01:13:38.340 --> 01:13:39.770 align:start position:0% yeah but it's the same in principle it's the<01:13:38.460> same<01:13:38.580> idea<01:13:38.820> you<01:13:39.000> just<01:13:39.120> take<01:13:39.239> a<01:13:39.420> component 01:13:39.770 --> 01:13:39.780 align:start position:0% the same idea you just take a component 01:13:39.780 --> 01:13:41.750 align:start position:0% the same idea you just take a component plug<01:13:40.320> it<01:13:40.560> in<01:13:40.679> and<01:13:40.800> lift<01:13:40.980> it<01:13:41.100> into<01:13:41.219> an<01:13:41.400> open<01:13:41.460> gate 01:13:41.750 --> 01:13:41.760 align:start position:0% plug it in and lift it into an open gate 01:13:41.760 --> 01:13:43.550 align:start position:0% plug it in and lift it into an open gate it's<01:13:41.880> just<01:13:42.000> a<01:13:42.120> computation<01:13:42.560> similarly 01:13:43.550 --> 01:13:43.560 align:start position:0% it's just a computation similarly 01:13:43.560 --> 01:13:45.890 align:start position:0% it's just a computation similarly determine<01:13:43.920> head<01:13:44.040> of<01:13:44.219> the<01:13:44.280> chain<01:13:44.940> um<01:13:45.060> here<01:13:45.300> as 01:13:45.890 --> 01:13:45.900 align:start position:0% determine head of the chain um here as 01:13:45.900 --> 01:13:48.649 align:start position:0% determine head of the chain um here as you<01:13:46.020> can<01:13:46.140> see<01:13:46.320> this<01:13:47.280> input<01:13:47.640> here 01:13:48.649 --> 01:13:48.659 align:start position:0% you can see this input here 01:13:48.659 --> 01:13:50.689 align:start position:0% you can see this input here um is<01:13:49.380> basically<01:13:49.679> just<01:13:49.860> a<01:13:50.100> function<01:13:50.340> from<01:13:50.580> the 01:13:50.689 --> 01:13:50.699 align:start position:0% um is basically just a function from the 01:13:50.699 --> 01:13:52.310 align:start position:0% um is basically just a function from the right<01:13:50.820> hand<01:13:50.940> side<01:13:51.179> I'm<01:13:51.600> lifting<01:13:51.960> it<01:13:52.020> into<01:13:52.140> an 01:13:52.310 --> 01:13:52.320 align:start position:0% right hand side I'm lifting it into an 01:13:52.320 --> 01:13:54.649 align:start position:0% right hand side I'm lifting it into an open<01:13:52.440> game<01:13:52.620> just<01:13:52.860> a<01:13:53.040> building<01:13:53.159> block 01:13:54.649 --> 01:13:54.659 align:start position:0% open game just a building block 01:13:54.659 --> 01:13:56.570 align:start position:0% open game just a building block good<01:13:55.080> these<01:13:55.920> are<01:13:55.980> very<01:13:56.159> boring<01:13:56.400> building 01:13:56.570 --> 01:13:56.580 align:start position:0% good these are very boring building 01:13:56.580 --> 01:13:58.729 align:start position:0% good these are very boring building blocks<01:13:57.000> so<01:13:57.120> let's<01:13:57.239> move<01:13:57.480> on 01:13:58.729 --> 01:13:58.739 align:start position:0% blocks so let's move on 01:13:58.739 --> 01:14:01.550 align:start position:0% blocks so let's move on what<01:13:59.219> do<01:13:59.400> I<01:13:59.520> need<01:13:59.699> I<01:14:00.480> have<01:14:00.659> proposer<01:14:01.199> and<01:14:01.440> I 01:14:01.550 --> 01:14:01.560 align:start position:0% what do I need I have proposer and I 01:14:01.560 --> 01:14:03.169 align:start position:0% what do I need I have proposer and I have<01:14:01.739> validators<01:14:02.219> so<01:14:02.580> what<01:14:02.760> makes<01:14:02.940> probably 01:14:03.169 --> 01:14:03.179 align:start position:0% have validators so what makes probably 01:14:03.179 --> 01:14:04.850 align:start position:0% have validators so what makes probably sense<01:14:03.480> is<01:14:03.659> to<01:14:03.780> think<01:14:03.900> about<01:14:04.080> how<01:14:04.620> does<01:14:04.739> the 01:14:04.850 --> 01:14:04.860 align:start position:0% sense is to think about how does the 01:14:04.860 --> 01:14:06.410 align:start position:0% sense is to think about how does the validator<01:14:05.219> actually<01:14:05.460> look<01:14:05.699> like 01:14:06.410 --> 01:14:06.420 align:start position:0% validator actually look like 01:14:06.420 --> 01:14:09.290 align:start position:0% validator actually look like okay<01:14:06.960> let's<01:14:07.199> model<01:14:07.380> the<01:14:07.620> validator 01:14:09.290 --> 01:14:09.300 align:start position:0% okay let's model the validator 01:14:09.300 --> 01:14:10.850 align:start position:0% okay let's model the validator um<01:14:09.420> if<01:14:09.600> you<01:14:09.719> think<01:14:09.840> about<01:14:10.020> what<01:14:10.140> a<01:14:10.260> validator 01:14:10.850 --> 01:14:10.860 align:start position:0% um if you think about what a validator 01:14:10.860 --> 01:14:12.590 align:start position:0% um if you think about what a validator is<01:14:11.040> doing<01:14:11.159> I<01:14:11.340> said<01:14:11.460> before<01:14:11.699> the<01:14:12.120> action<01:14:12.360> he 01:14:12.590 --> 01:14:12.600 align:start position:0% is doing I said before the action he 01:14:12.600 --> 01:14:14.810 align:start position:0% is doing I said before the action he does<01:14:12.840> is<01:14:13.020> he<01:14:13.380> observes<01:14:13.860> the<01:14:14.159> new<01:14:14.280> chain<01:14:14.460> he 01:14:14.810 --> 01:14:14.820 align:start position:0% does is he observes the new chain he 01:14:14.820 --> 01:14:16.550 align:start position:0% does is he observes the new chain he observes<01:14:15.300> the<01:14:15.480> Delta<01:14:15.900> which<01:14:16.080> means<01:14:16.199> he<01:14:16.320> also 01:14:16.550 --> 01:14:16.560 align:start position:0% observes the Delta which means he also 01:14:16.560 --> 01:14:18.229 align:start position:0% observes the Delta which means he also has<01:14:16.679> an<01:14:16.860> access<01:14:16.980> to<01:14:17.219> the<01:14:17.280> oil<01:14:17.400> chain 01:14:18.229 --> 01:14:18.239 align:start position:0% has an access to the oil chain 01:14:18.239 --> 01:14:20.510 align:start position:0% has an access to the oil chain that's<01:14:18.659> the<01:14:18.900> input<01:14:19.140> here 01:14:20.510 --> 01:14:20.520 align:start position:0% that's the input here 01:14:20.520 --> 01:14:21.709 align:start position:0% that's the input here um<01:14:20.580> that's<01:14:20.760> also<01:14:20.940> the<01:14:21.060> input<01:14:21.300> the<01:14:21.540> line 01:14:21.709 --> 01:14:21.719 align:start position:0% um that's also the input the line 01:14:21.719 --> 01:14:23.930 align:start position:0% um that's also the input the line element<01:14:22.260> here<01:14:22.679> and<01:14:23.460> then<01:14:23.580> there<01:14:23.699> is<01:14:23.820> a 01:14:23.930 --> 01:14:23.940 align:start position:0% element here and then there is a 01:14:23.940 --> 01:14:25.970 align:start position:0% element here and then there is a decision<01:14:24.179> and<01:14:25.080> what<01:14:25.260> you<01:14:25.440> can<01:14:25.500> see<01:14:25.620> here<01:14:25.860> in 01:14:25.970 --> 01:14:25.980 align:start position:0% decision and what you can see here in 01:14:25.980 --> 01:14:27.830 align:start position:0% decision and what you can see here in that<01:14:26.100> expression<01:14:26.460> is<01:14:26.640> just<01:14:26.820> basically<01:14:27.179> that's 01:14:27.830 --> 01:14:27.840 align:start position:0% that expression is just basically that's 01:14:27.840 --> 01:14:29.689 align:start position:0% that expression is just basically that's telling<01:14:28.380> internally<01:14:29.159> the<01:14:29.400> dependent 01:14:29.689 --> 01:14:29.699 align:start position:0% telling internally the dependent 01:14:29.699 --> 01:14:31.550 align:start position:0% telling internally the dependent decision<01:14:30.000> operator<01:14:30.420> what<01:14:31.080> is<01:14:31.260> the<01:14:31.380> action 01:14:31.550 --> 01:14:31.560 align:start position:0% decision operator what is the action 01:14:31.560 --> 01:14:32.810 align:start position:0% decision operator what is the action space<01:14:31.800> the<01:14:32.040> where<01:14:32.219> Cutters<01:14:32.520> they<01:14:32.640> actually 01:14:32.810 --> 01:14:32.820 align:start position:0% space the where Cutters they actually 01:14:32.820 --> 01:14:34.729 align:start position:0% space the where Cutters they actually can<01:14:33.000> choose<01:14:33.239> from 01:14:34.729 --> 01:14:34.739 align:start position:0% can choose from 01:14:34.739 --> 01:14:36.410 align:start position:0% can choose from um<01:14:34.860> here<01:14:35.100> this<01:14:35.340> is<01:14:35.460> basically<01:14:35.699> just<01:14:35.940> because 01:14:36.410 --> 01:14:36.420 align:start position:0% um here this is basically just because 01:14:36.420 --> 01:14:38.149 align:start position:0% um here this is basically just because we<01:14:36.719> start<01:14:36.840> the<01:14:37.020> IDS<01:14:37.380> of<01:14:37.500> the<01:14:37.620> of<01:14:37.739> the<01:14:37.920> blocks 01:14:38.149 --> 01:14:38.159 align:start position:0% we start the IDS of the of the blocks 01:14:38.159 --> 01:14:40.610 align:start position:0% we start the IDS of the of the blocks from<01:14:38.340> one<01:14:38.520> until<01:14:39.420> the<01:14:40.080> vertex<01:14:40.380> count 01:14:40.610 --> 01:14:40.620 align:start position:0% from one until the vertex count 01:14:40.620 --> 01:14:42.770 align:start position:0% from one until the vertex count basically<01:14:41.219> how<01:14:41.460> many<01:14:41.640> vertex<01:14:42.000> are<01:14:42.179> there<01:14:42.300> and 01:14:42.770 --> 01:14:42.780 align:start position:0% basically how many vertex are there and 01:14:42.780 --> 01:14:44.450 align:start position:0% basically how many vertex are there and then<01:14:42.900> this<01:14:43.080> is<01:14:43.199> basically<01:14:43.620> the<01:14:43.800> choice<01:14:44.159> that 01:14:44.450 --> 01:14:44.460 align:start position:0% then this is basically the choice that 01:14:44.460 --> 01:14:47.570 align:start position:0% then this is basically the choice that the<01:14:44.699> validator<01:14:45.480> can<01:14:45.719> do 01:14:47.570 --> 01:14:47.580 align:start position:0% the validator can do 01:14:47.580 --> 01:14:49.550 align:start position:0% the validator can do okay<01:14:48.060> so<01:14:48.300> we<01:14:48.540> have<01:14:48.780> basically<01:14:49.260> a<01:14:49.380> bit<01:14:49.440> of 01:14:49.550 --> 01:14:49.560 align:start position:0% okay so we have basically a bit of 01:14:49.560 --> 01:14:51.830 align:start position:0% okay so we have basically a bit of computational<01:14:49.980> background<01:14:50.400> adds<01:14:51.239> adds<01:14:51.719> a 01:14:51.830 --> 01:14:51.840 align:start position:0% computational background adds adds a 01:14:51.840 --> 01:14:53.149 align:start position:0% computational background adds adds a block<01:14:52.020> we<01:14:52.260> have<01:14:52.380> the<01:14:52.500> determined<01:14:52.920> head<01:14:52.980> of 01:14:53.149 --> 01:14:53.159 align:start position:0% block we have the determined head of 01:14:53.159 --> 01:14:55.610 align:start position:0% block we have the determined head of chain<01:14:53.280> we<01:14:53.640> have<01:14:53.820> the<01:14:53.880> validator 01:14:55.610 --> 01:14:55.620 align:start position:0% chain we have the validator 01:14:55.620 --> 01:14:56.689 align:start position:0% chain we have the validator um 01:14:56.689 --> 01:14:56.699 align:start position:0% um 01:14:56.699 --> 01:14:59.149 align:start position:0% um now<01:14:57.060> we<01:14:57.179> have<01:14:57.300> the<01:14:57.420> proposer 01:14:59.149 --> 01:14:59.159 align:start position:0% now we have the proposer 01:14:59.159 --> 01:15:01.070 align:start position:0% now we have the proposer okay<01:14:59.580> what<01:14:59.880> is<01:15:00.000> the<01:15:00.120> proposal<01:15:00.480> doing<01:15:00.659> well<01:15:00.900> the 01:15:01.070 --> 01:15:01.080 align:start position:0% okay what is the proposal doing well the 01:15:01.080 --> 01:15:02.990 align:start position:0% okay what is the proposal doing well the proposal<01:15:01.440> observes<01:15:01.860> the<01:15:02.040> chain 01:15:02.990 --> 01:15:03.000 align:start position:0% proposal observes the chain 01:15:03.000 --> 01:15:07.310 align:start position:0% proposal observes the chain also<01:15:03.540> internally<01:15:03.960> he<01:15:04.920> makes<01:15:05.100> a<01:15:05.280> decision 01:15:07.310 --> 01:15:07.320 align:start position:0% also internally he makes a decision 01:15:07.320 --> 01:15:08.990 align:start position:0% also internally he makes a decision um 01:15:08.990 --> 01:15:09.000 align:start position:0% um 01:15:09.000 --> 01:15:10.490 align:start position:0% um what<01:15:09.360> decision<01:15:09.659> does<01:15:09.840> it<01:15:09.960> do<01:15:10.080> well<01:15:10.199> you<01:15:10.380> can 01:15:10.490 --> 01:15:10.500 align:start position:0% what decision does it do well you can 01:15:10.500 --> 01:15:13.070 align:start position:0% what decision does it do well you can choose<01:15:10.739> basically<01:15:11.100> on<01:15:11.280> which<01:15:11.460> block<01:15:11.640> to<01:15:11.940> build 01:15:13.070 --> 01:15:13.080 align:start position:0% choose basically on which block to build 01:15:13.080 --> 01:15:15.169 align:start position:0% choose basically on which block to build that<01:15:13.800> is<01:15:13.920> the<01:15:14.100> outset<01:15:14.400> this<01:15:14.640> is<01:15:14.760> the<01:15:14.880> decision 01:15:15.169 --> 01:15:15.179 align:start position:0% that is the outset this is the decision 01:15:15.179 --> 01:15:18.229 align:start position:0% that is the outset this is the decision proposer<01:15:15.719> which<01:15:16.020> is<01:15:16.140> coming<01:15:16.380> out<01:15:16.560> here 01:15:18.229 --> 01:15:18.239 align:start position:0% proposer which is coming out here 01:15:18.239 --> 01:15:20.209 align:start position:0% proposer which is coming out here and<01:15:18.900> then<01:15:19.080> you<01:15:19.380> can<01:15:19.440> see<01:15:19.560> this<01:15:19.800> is<01:15:19.920> the<01:15:20.100> first 01:15:20.209 --> 01:15:20.219 align:start position:0% and then you can see this is the first 01:15:20.219 --> 01:15:21.770 align:start position:0% and then you can see this is the first game<01:15:20.460> in<01:15:20.820> that<01:15:20.940> in<01:15:21.120> that<01:15:21.239> context<01:15:21.480> where<01:15:21.659> we 01:15:21.770 --> 01:15:21.780 align:start position:0% game in that in that context where we 01:15:21.780 --> 01:15:23.149 align:start position:0% game in that in that context where we have<01:15:21.900> another<01:15:21.960> line<01:15:22.199> block<01:15:22.440> there's<01:15:22.920> some 01:15:23.149 --> 01:15:23.159 align:start position:0% have another line block there's some 01:15:23.159 --> 01:15:24.649 align:start position:0% have another line block there's some kind<01:15:23.280> of<01:15:23.340> additional<01:15:23.699> functionality<01:15:24.179> this<01:15:24.480> is 01:15:24.649 --> 01:15:24.659 align:start position:0% kind of additional functionality this is 01:15:24.659 --> 01:15:26.390 align:start position:0% kind of additional functionality this is just<01:15:24.840> basically<01:15:25.140> producing<01:15:25.560> the<01:15:25.679> new<01:15:25.800> chain 01:15:26.390 --> 01:15:26.400 align:start position:0% just basically producing the new chain 01:15:26.400 --> 01:15:28.490 align:start position:0% just basically producing the new chain this<01:15:27.000> is<01:15:27.060> taking<01:15:27.239> two<01:15:27.480> graphs<01:15:27.780> this<01:15:27.960> is<01:15:28.140> as<01:15:28.380> I 01:15:28.490 --> 01:15:28.500 align:start position:0% this is taking two graphs this is as I 01:15:28.500 --> 01:15:29.630 align:start position:0% this is taking two graphs this is as I said<01:15:28.560> this<01:15:28.739> is<01:15:28.860> a<01:15:28.920> specific<01:15:29.219> library<01:15:29.400> from 01:15:29.630 --> 01:15:29.640 align:start position:0% said this is a specific library from 01:15:29.640 --> 01:15:31.130 align:start position:0% said this is a specific library from Haskell<01:15:30.000> which<01:15:30.179> is<01:15:30.300> algebraic<01:15:30.780> you<01:15:30.960> can<01:15:31.020> just 01:15:31.130 --> 01:15:31.140 align:start position:0% Haskell which is algebraic you can just 01:15:31.140 --> 01:15:32.810 align:start position:0% Haskell which is algebraic you can just plug<01:15:31.320> things<01:15:31.560> together<01:15:31.739> and<01:15:32.219> you<01:15:32.340> get<01:15:32.520> the<01:15:32.640> new 01:15:32.810 --> 01:15:32.820 align:start position:0% plug things together and you get the new 01:15:32.820 --> 01:15:34.370 align:start position:0% plug things together and you get the new the<01:15:33.060> new<01:15:33.239> chain 01:15:34.370 --> 01:15:34.380 align:start position:0% the new chain 01:15:34.380 --> 01:15:36.649 align:start position:0% the new chain and<01:15:34.739> the<01:15:34.860> output<01:15:35.159> so<01:15:35.880> the<01:15:36.060> wiring<01:15:36.420> of<01:15:36.540> that 01:15:36.649 --> 01:15:36.659 align:start position:0% and the output so the wiring of that 01:15:36.659 --> 01:15:38.630 align:start position:0% and the output so the wiring of that game<01:15:36.840> is<01:15:37.080> basically<01:15:37.380> chain<01:15:37.679> old<01:15:37.920> and<01:15:38.460> chain 01:15:38.630 --> 01:15:38.640 align:start position:0% game is basically chain old and chain 01:15:38.640 --> 01:15:40.310 align:start position:0% game is basically chain old and chain new<01:15:38.880> this<01:15:39.300> is<01:15:39.360> my<01:15:39.540> interface<01:15:39.840> of<01:15:40.020> what<01:15:40.199> the 01:15:40.310 --> 01:15:40.320 align:start position:0% new this is my interface of what the 01:15:40.320 --> 01:15:43.010 align:start position:0% new this is my interface of what the proposer<01:15:40.800> is<01:15:40.920> doing 01:15:43.010 --> 01:15:43.020 align:start position:0% proposer is doing 01:15:43.020 --> 01:15:45.410 align:start position:0% proposer is doing okay<01:15:43.500> now<01:15:44.219> the<01:15:44.400> thing 01:15:45.410 --> 01:15:45.420 align:start position:0% okay now the thing 01:15:45.420 --> 01:15:48.590 align:start position:0% okay now the thing um<01:15:45.540> I<01:15:46.260> cheated<01:15:46.500> you<01:15:46.679> a<01:15:46.860> bit 01:15:48.590 --> 01:15:48.600 align:start position:0% um I cheated you a bit 01:15:48.600 --> 01:15:51.229 align:start position:0% um I cheated you a bit um<01:15:48.659> on<01:15:49.020> two<01:15:49.199> places<01:15:49.500> maybe<01:15:50.460> already<01:15:50.699> spotted 01:15:51.229 --> 01:15:51.239 align:start position:0% um on two places maybe already spotted 01:15:51.239 --> 01:15:53.330 align:start position:0% um on two places maybe already spotted it 01:15:53.330 --> 01:15:53.340 align:start position:0% it 01:15:53.340 --> 01:15:56.390 align:start position:0% it if<01:15:53.820> you<01:15:53.940> look<01:15:54.060> at<01:15:54.360> for<01:15:55.320> the<01:15:55.440> validator<01:15:55.860> as<01:15:56.219> well 01:15:56.390 --> 01:15:56.400 align:start position:0% if you look at for the validator as well 01:15:56.400 --> 01:15:57.890 align:start position:0% if you look at for the validator as well as<01:15:56.580> the<01:15:56.699> proposer<01:15:57.179> if<01:15:57.480> you<01:15:57.540> look<01:15:57.659> at<01:15:57.780> the 01:15:57.890 --> 01:15:57.900 align:start position:0% as the proposer if you look at the 01:15:57.900 --> 01:16:00.709 align:start position:0% as the proposer if you look at the return<01:15:58.020> type<01:15:58.380> here<01:15:59.219> a<01:15:59.699> return<01:15:59.880> field<01:16:00.179> I'm 01:16:00.709 --> 01:16:00.719 align:start position:0% return type here a return field I'm 01:16:00.719 --> 01:16:03.169 align:start position:0% return type here a return field I'm returning<01:16:01.140> a<01:16:01.260> constant<01:16:01.620> zero<01:16:02.460> which<01:16:02.820> is<01:16:03.000> kind 01:16:03.169 --> 01:16:03.179 align:start position:0% returning a constant zero which is kind 01:16:03.179 --> 01:16:04.910 align:start position:0% returning a constant zero which is kind of<01:16:03.300> weird<01:16:03.719> right<01:16:04.020> because<01:16:04.380> I<01:16:04.560> said<01:16:04.679> before 01:16:04.910 --> 01:16:04.920 align:start position:0% of weird right because I said before 01:16:04.920 --> 01:16:06.410 align:start position:0% of weird right because I said before isn't<01:16:05.280> that<01:16:05.400> where<01:16:05.580> actually<01:16:05.820> the<01:16:06.000> Strategic 01:16:06.410 --> 01:16:06.420 align:start position:0% isn't that where actually the Strategic 01:16:06.420 --> 01:16:07.910 align:start position:0% isn't that where actually the Strategic context<01:16:06.780> come<01:16:07.020> from<01:16:07.199> the<01:16:07.380> environment 01:16:07.910 --> 01:16:07.920 align:start position:0% context come from the environment 01:16:07.920 --> 01:16:09.229 align:start position:0% context come from the environment telling<01:16:08.219> me<01:16:08.280> what<01:16:08.400> to<01:16:08.520> do<01:16:08.640> blah<01:16:08.940> blah<01:16:09.060> blah 01:16:09.229 --> 01:16:09.239 align:start position:0% telling me what to do blah blah blah 01:16:09.239 --> 01:16:11.209 align:start position:0% telling me what to do blah blah blah blah<01:16:09.420> and<01:16:09.900> now<01:16:10.080> it's<01:16:10.380> just<01:16:10.500> saying<01:16:10.739> it's<01:16:10.800> zero 01:16:11.209 --> 01:16:11.219 align:start position:0% blah and now it's just saying it's zero 01:16:11.219 --> 01:16:13.370 align:start position:0% blah and now it's just saying it's zero it<01:16:11.460> doesn't<01:16:11.640> look<01:16:11.880> really<01:16:12.120> strategic<01:16:13.020> now 01:16:13.370 --> 01:16:13.380 align:start position:0% it doesn't look really strategic now 01:16:13.380 --> 01:16:14.750 align:start position:0% it doesn't look really strategic now this<01:16:13.560> is<01:16:13.620> an<01:16:13.739> instance<01:16:14.040> and<01:16:14.219> I<01:16:14.400> will<01:16:14.520> come<01:16:14.699> back 01:16:14.750 --> 01:16:14.760 align:start position:0% this is an instance and I will come back 01:16:14.760 --> 01:16:16.550 align:start position:0% this is an instance and I will come back to<01:16:14.880> this<01:16:15.060> this<01:16:15.360> is<01:16:15.480> an<01:16:15.600> instance<01:16:15.840> of<01:16:16.020> where<01:16:16.440> we 01:16:16.550 --> 01:16:16.560 align:start position:0% to this this is an instance of where we 01:16:16.560 --> 01:16:17.990 align:start position:0% to this this is an instance of where we actually<01:16:16.679> had<01:16:16.920> exactly<01:16:17.280> what<01:16:17.400> I<01:16:17.580> just<01:16:17.699> blah 01:16:17.990 --> 01:16:18.000 align:start position:0% actually had exactly what I just blah 01:16:18.000 --> 01:16:19.189 align:start position:0% actually had exactly what I just blah blah<01:16:18.179> namely<01:16:18.420> we<01:16:18.600> had<01:16:18.659> the<01:16:18.780> inputs<01:16:19.080> coming 01:16:19.189 --> 01:16:19.199 align:start position:0% blah namely we had the inputs coming 01:16:19.199 --> 01:16:20.990 align:start position:0% blah namely we had the inputs coming from<01:16:19.380> the<01:16:19.560> outside<01:16:19.679> world<01:16:20.040> and<01:16:20.580> blocked<01:16:20.880> them 01:16:20.990 --> 01:16:21.000 align:start position:0% from the outside world and blocked them 01:16:21.000 --> 01:16:23.209 align:start position:0% from the outside world and blocked them through<01:16:21.179> but<01:16:21.780> then<01:16:21.900> realized<01:16:22.440> that<01:16:22.860> there<01:16:23.040> is 01:16:23.209 --> 01:16:23.219 align:start position:0% through but then realized that there is 01:16:23.219 --> 01:16:26.149 align:start position:0% through but then realized that there is actually<01:16:23.400> a<01:16:24.000> very<01:16:24.120> neat<01:16:24.780> useful<01:16:25.560> pattern<01:16:25.980> here 01:16:26.149 --> 01:16:26.159 align:start position:0% actually a very neat useful pattern here 01:16:26.159 --> 01:16:28.250 align:start position:0% actually a very neat useful pattern here that<01:16:26.699> we<01:16:26.820> can<01:16:26.940> abstract<01:16:27.239> out<01:16:27.480> and<01:16:27.960> make<01:16:28.140> it 01:16:28.250 --> 01:16:28.260 align:start position:0% that we can abstract out and make it 01:16:28.260 --> 01:16:30.470 align:start position:0% that we can abstract out and make it much<01:16:28.440> easier<01:16:28.739> to<01:16:28.920> compose<01:16:29.280> later<01:16:29.520> on<01:16:29.880> the 01:16:30.470 --> 01:16:30.480 align:start position:0% much easier to compose later on the 01:16:30.480 --> 01:16:32.030 align:start position:0% much easier to compose later on the payoffs<01:16:30.900> in<01:16:31.020> a<01:16:31.140> different<01:16:31.199> way<01:16:31.380> yeah<01:16:31.739> this<01:16:31.920> is 01:16:32.030 --> 01:16:32.040 align:start position:0% payoffs in a different way yeah this is 01:16:32.040 --> 01:16:33.110 align:start position:0% payoffs in a different way yeah this is in<01:16:32.159> some<01:16:32.280> sense<01:16:32.400> a<01:16:32.520> bit<01:16:32.640> of<01:16:32.760> Haskell 01:16:33.110 --> 01:16:33.120 align:start position:0% in some sense a bit of Haskell 01:16:33.120 --> 01:16:35.149 align:start position:0% in some sense a bit of Haskell background<01:16:33.420> that<01:16:34.140> made<01:16:34.380> it<01:16:34.560> possible<01:16:34.860> to<01:16:35.040> kind 01:16:35.149 --> 01:16:35.159 align:start position:0% background that made it possible to kind 01:16:35.159 --> 01:16:37.310 align:start position:0% background that made it possible to kind of<01:16:35.280> split<01:16:35.520> this<01:16:35.640> up<01:16:35.880> even<01:16:36.120> further<01:16:36.480> that<01:16:37.199> is 01:16:37.310 --> 01:16:37.320 align:start position:0% of split this up even further that is 01:16:37.320 --> 01:16:39.050 align:start position:0% of split this up even further that is what<01:16:37.440> I<01:16:37.560> meant<01:16:37.739> initially<01:16:38.100> when<01:16:38.280> I<01:16:38.400> said<01:16:38.580> when 01:16:39.050 --> 01:16:39.060 align:start position:0% what I meant initially when I said when 01:16:39.060 --> 01:16:40.610 align:start position:0% what I meant initially when I said when you<01:16:39.239> start<01:16:39.420> modeling<01:16:39.840> in<01:16:39.960> this<01:16:40.080> chain<01:16:40.260> you<01:16:40.500> can 01:16:40.610 --> 01:16:40.620 align:start position:0% you start modeling in this chain you can 01:16:40.620 --> 01:16:42.110 align:start position:0% you start modeling in this chain you can of<01:16:40.800> course<01:16:40.920> sometimes<01:16:41.580> realize<01:16:41.940> just 01:16:42.110 --> 01:16:42.120 align:start position:0% of course sometimes realize just 01:16:42.120 --> 01:16:43.370 align:start position:0% of course sometimes realize just programming<01:16:42.540> patterns<01:16:42.840> drastically 01:16:43.370 --> 01:16:43.380 align:start position:0% programming patterns drastically 01:16:43.380 --> 01:16:45.290 align:start position:0% programming patterns drastically abstract<01:16:43.980> them<01:16:44.219> out<01:16:44.400> and<01:16:44.760> replace<01:16:44.880> them<01:16:45.120> with 01:16:45.290 --> 01:16:45.300 align:start position:0% abstract them out and replace them with 01:16:45.300 --> 01:16:46.490 align:start position:0% abstract them out and replace them with something<01:16:45.480> else 01:16:46.490 --> 01:16:46.500 align:start position:0% something else 01:16:46.500 --> 01:16:48.169 align:start position:0% something else why<01:16:46.980> is<01:16:47.100> this<01:16:47.219> actually<01:16:47.400> happening<01:16:47.760> in<01:16:48.060> a 01:16:48.169 --> 01:16:48.179 align:start position:0% why is this actually happening in a 01:16:48.179 --> 01:16:50.510 align:start position:0% why is this actually happening in a sense<01:16:48.300> keep<01:16:48.900> in<01:16:49.020> mind<01:16:49.199> for<01:16:49.800> the<01:16:49.980> protocol<01:16:50.219> to 01:16:50.510 --> 01:16:50.520 align:start position:0% sense keep in mind for the protocol to 01:16:50.520 --> 01:16:51.649 align:start position:0% sense keep in mind for the protocol to work 01:16:51.649 --> 01:16:51.659 align:start position:0% work 01:16:51.659 --> 01:16:55.189 align:start position:0% work in<01:16:52.380> Period<01:16:52.800> T<01:16:53.100> the<01:16:53.760> decisions<01:16:54.120> of<01:16:54.540> proposal<01:16:55.020> as 01:16:55.189 --> 01:16:55.199 align:start position:0% in Period T the decisions of proposal as 01:16:55.199 --> 01:16:57.530 align:start position:0% in Period T the decisions of proposal as well<01:16:55.320> as<01:16:55.440> validators<01:16:55.920> are<01:16:56.340> not<01:16:56.520> rewarded<01:16:57.000> they 01:16:57.530 --> 01:16:57.540 align:start position:0% well as validators are not rewarded they 01:16:57.540 --> 01:16:59.149 align:start position:0% well as validators are not rewarded they are<01:16:57.719> only<01:16:57.840> rewarded<01:16:58.320> in<01:16:58.500> the<01:16:58.620> future<01:16:58.739> that 01:16:59.149 --> 01:16:59.159 align:start position:0% are only rewarded in the future that 01:16:59.159 --> 01:17:00.649 align:start position:0% are only rewarded in the future that means<01:16:59.400> their<01:16:59.880> reward<01:17:00.239> actually<01:17:00.480> is 01:17:00.649 --> 01:17:00.659 align:start position:0% means their reward actually is 01:17:00.659 --> 01:17:02.630 align:start position:0% means their reward actually is conditioning<01:17:01.140> on<01:17:01.380> what<01:17:01.920> is<01:17:02.040> coming<01:17:02.219> from<01:17:02.460> the 01:17:02.630 --> 01:17:02.640 align:start position:0% conditioning on what is coming from the 01:17:02.640 --> 01:17:03.530 align:start position:0% conditioning on what is coming from the future 01:17:03.530 --> 01:17:03.540 align:start position:0% future 01:17:03.540 --> 01:17:05.990 align:start position:0% future and<01:17:03.900> this<01:17:04.080> is<01:17:04.199> a<01:17:04.380> way<01:17:04.500> and<01:17:05.400> I<01:17:05.520> will<01:17:05.640> show<01:17:05.760> you<01:17:05.880> in 01:17:05.990 --> 01:17:06.000 align:start position:0% and this is a way and I will show you in 01:17:06.000 --> 01:17:07.490 align:start position:0% and this is a way and I will show you in a<01:17:06.060> minute<01:17:06.179> how<01:17:06.540> we<01:17:06.719> actually<01:17:06.840> can<01:17:07.140> deal<01:17:07.320> with 01:17:07.490 --> 01:17:07.500 align:start position:0% a minute how we actually can deal with 01:17:07.500 --> 01:17:08.510 align:start position:0% a minute how we actually can deal with this 01:17:08.510 --> 01:17:08.520 align:start position:0% this 01:17:08.520 --> 01:17:10.189 align:start position:0% this and<01:17:08.880> the<01:17:09.000> same<01:17:09.120> is<01:17:09.239> true<01:17:09.420> for<01:17:09.540> the<01:17:09.659> validator 01:17:10.189 --> 01:17:10.199 align:start position:0% and the same is true for the validator 01:17:10.199 --> 01:17:13.070 align:start position:0% and the same is true for the validator as<01:17:10.500> well<01:17:10.620> as<01:17:10.739> the<01:17:10.860> proposal 01:17:13.070 --> 01:17:13.080 align:start position:0% as well as the proposal 01:17:13.080 --> 01:17:15.649 align:start position:0% as well as the proposal okay<01:17:13.679> so<01:17:14.100> here's<01:17:14.340> an<01:17:14.460> example 01:17:15.649 --> 01:17:15.659 align:start position:0% okay so here's an example 01:17:15.659 --> 01:17:17.149 align:start position:0% okay so here's an example um<01:17:15.719> of<01:17:16.140> what<01:17:16.500> you<01:17:16.620> can<01:17:16.739> see<01:17:16.800> here<01:17:16.920> but 01:17:17.149 --> 01:17:17.159 align:start position:0% um of what you can see here but 01:17:17.159 --> 01:17:18.950 align:start position:0% um of what you can see here but basically<01:17:17.460> how<01:17:17.640> this<01:17:17.760> is<01:17:17.940> done<01:17:18.120> this<01:17:18.719> is<01:17:18.780> what 01:17:18.950 --> 01:17:18.960 align:start position:0% basically how this is done this is what 01:17:18.960 --> 01:17:20.689 align:start position:0% basically how this is done this is what is<01:17:19.020> called<01:17:19.199> up 01:17:20.689 --> 01:17:20.699 align:start position:0% is called up 01:17:20.699 --> 01:17:22.790 align:start position:0% is called up update<01:17:21.420> payoff<01:17:21.780> validator 01:17:22.790 --> 01:17:22.800 align:start position:0% update payoff validator 01:17:22.800 --> 01:17:25.130 align:start position:0% update payoff validator this<01:17:23.460> is<01:17:23.520> an<01:17:23.699> auxiliary<01:17:24.120> thing<01:17:24.480> it's<01:17:24.900> taking 01:17:25.130 --> 01:17:25.140 align:start position:0% this is an auxiliary thing it's taking 01:17:25.140 --> 01:17:26.390 align:start position:0% this is an auxiliary thing it's taking in<01:17:25.380> a<01:17:25.500> boom 01:17:26.390 --> 01:17:26.400 align:start position:0% in a boom 01:17:26.400 --> 01:17:29.090 align:start position:0% in a boom the<01:17:26.699> bull<01:17:26.880> is<01:17:27.120> basically<01:17:27.420> was<01:17:28.260> the<01:17:28.739> validation 01:17:29.090 --> 01:17:29.100 align:start position:0% the bull is basically was the validation 01:17:29.100 --> 01:17:31.550 align:start position:0% the bull is basically was the validation correct<01:17:29.520> according<01:17:29.880> to<01:17:30.060> the<01:17:30.179> protocol 01:17:31.550 --> 01:17:31.560 align:start position:0% correct according to the protocol 01:17:31.560 --> 01:17:34.189 align:start position:0% correct according to the protocol that<01:17:32.100> is<01:17:32.219> then<01:17:32.400> determining<01:17:32.940> the<01:17:33.060> payoff 01:17:34.189 --> 01:17:34.199 align:start position:0% that is then determining the payoff 01:17:34.199 --> 01:17:36.290 align:start position:0% that is then determining the payoff um<01:17:34.320> payoff<01:17:34.800> can<01:17:34.980> also<01:17:35.159> be<01:17:35.219> negative<01:17:35.460> so<01:17:35.760> if<01:17:35.940> the 01:17:36.290 --> 01:17:36.300 align:start position:0% um payoff can also be negative so if the 01:17:36.300 --> 01:17:37.910 align:start position:0% um payoff can also be negative so if the pro<01:17:36.780> and<01:17:37.020> basically<01:17:37.260> the<01:17:37.500> protocol 01:17:37.910 --> 01:17:37.920 align:start position:0% pro and basically the protocol 01:17:37.920 --> 01:17:39.950 align:start position:0% pro and basically the protocol determines<01:17:38.520> what<01:17:39.120> this<01:17:39.300> validator<01:17:39.659> did 01:17:39.950 --> 01:17:39.960 align:start position:0% determines what this validator did 01:17:39.960 --> 01:17:42.530 align:start position:0% determines what this validator did actually<01:17:40.199> in<01:17:40.440> t<01:17:40.679> in<01:17:41.640> t<01:17:41.820> plus<01:17:42.000> one<01:17:42.239> doesn't 01:17:42.530 --> 01:17:42.540 align:start position:0% actually in t in t plus one doesn't 01:17:42.540 --> 01:17:44.030 align:start position:0% actually in t in t plus one doesn't actually<01:17:42.780> look<01:17:42.960> good<01:17:43.140> so<01:17:43.320> we<01:17:43.500> will<01:17:43.620> punish<01:17:43.920> it 01:17:44.030 --> 01:17:44.040 align:start position:0% actually look good so we will punish it 01:17:44.040 --> 01:17:45.950 align:start position:0% actually look good so we will punish it could<01:17:44.280> be<01:17:44.460> a<01:17:44.520> negative<01:17:44.760> value 01:17:45.950 --> 01:17:45.960 align:start position:0% could be a negative value 01:17:45.960 --> 01:17:47.990 align:start position:0% could be a negative value okay<01:17:46.440> that<01:17:46.800> value<01:17:46.980> is<01:17:47.219> feed<01:17:47.400> forward<01:17:47.640> and<01:17:47.820> then 01:17:47.990 --> 01:17:48.000 align:start position:0% okay that value is feed forward and then 01:17:48.000 --> 01:17:49.130 align:start position:0% okay that value is feed forward and then there's<01:17:48.120> this<01:17:48.300> add<01:17:48.540> payoffs<01:17:48.960> construction 01:17:49.130 --> 01:17:49.140 align:start position:0% there's this add payoffs construction 01:17:49.140 --> 01:17:52.070 align:start position:0% there's this add payoffs construction this<01:17:49.920> is<01:17:50.040> just<01:17:50.280> another<01:17:50.699> open<01:17:51.120> game<01:17:51.420> and<01:17:51.960> what 01:17:52.070 --> 01:17:52.080 align:start position:0% this is just another open game and what 01:17:52.080 --> 01:17:54.890 align:start position:0% this is just another open game and what internally<01:17:52.440> is<01:17:52.679> happening<01:17:53.120> internally<01:17:54.120> this 01:17:54.890 --> 01:17:54.900 align:start position:0% internally is happening internally this 01:17:54.900 --> 01:17:57.470 align:start position:0% internally is happening internally this is<01:17:55.140> associating<01:17:55.920> the<01:17:56.159> payoff<01:17:56.520> to<01:17:57.120> the<01:17:57.239> player 01:17:57.470 --> 01:17:57.480 align:start position:0% is associating the payoff to the player 01:17:57.480 --> 01:17:59.689 align:start position:0% is associating the payoff to the player which<01:17:57.659> is<01:17:57.780> parameterized<01:17:58.320> spending<01:17:58.679> so<01:17:59.580> you 01:17:59.689 --> 01:17:59.699 align:start position:0% which is parameterized spending so you 01:17:59.699 --> 01:18:01.130 align:start position:0% which is parameterized spending so you can<01:17:59.880> you<01:18:00.060> can<01:18:00.239> put<01:18:00.360> this<01:18:00.600> component<01:18:00.960> in 01:18:01.130 --> 01:18:01.140 align:start position:0% can you can put this component in 01:18:01.140 --> 01:18:02.090 align:start position:0% can you can put this component in different<01:18:01.320> places<01:18:01.560> and<01:18:01.860> it<01:18:01.980> will 01:18:02.090 --> 01:18:02.100 align:start position:0% different places and it will 01:18:02.100 --> 01:18:04.189 align:start position:0% different places and it will automatically<01:18:02.640> add<01:18:03.360> the<01:18:03.600> payoff<01:18:03.900> at<01:18:04.080> that 01:18:04.189 --> 01:18:04.199 align:start position:0% automatically add the payoff at that 01:18:04.199 --> 01:18:06.470 align:start position:0% automatically add the payoff at that point<01:18:04.440> to<01:18:04.800> your<01:18:04.980> player<01:18:05.580> do<01:18:06.000> you<01:18:06.179> have<01:18:06.300> to<01:18:06.360> do 01:18:06.470 --> 01:18:06.480 align:start position:0% point to your player do you have to do 01:18:06.480 --> 01:18:08.810 align:start position:0% point to your player do you have to do it<01:18:06.600> in<01:18:06.719> that<01:18:06.840> form<01:18:07.080> no<01:18:07.500> I<01:18:07.800> said<01:18:07.980> before<01:18:08.159> you 01:18:08.810 --> 01:18:08.820 align:start position:0% it in that form no I said before you 01:18:08.820 --> 01:18:10.310 align:start position:0% it in that form no I said before you could<01:18:08.940> also<01:18:09.239> kind<01:18:09.420> of<01:18:09.480> make<01:18:09.600> it<01:18:09.780> more<01:18:09.960> with<01:18:10.140> the 01:18:10.310 --> 01:18:10.320 align:start position:0% could also kind of make it more with the 01:18:10.320 --> 01:18:12.050 align:start position:0% could also kind of make it more with the wires<01:18:10.620> and<01:18:10.739> so<01:18:10.860> on<01:18:10.980> but<01:18:11.460> this<01:18:11.580> is<01:18:11.699> a<01:18:11.820> pattern 01:18:12.050 --> 01:18:12.060 align:start position:0% wires and so on but this is a pattern 01:18:12.060 --> 01:18:13.370 align:start position:0% wires and so on but this is a pattern which<01:18:12.179> makes<01:18:12.360> it<01:18:12.480> extremely<01:18:12.780> lightweight<01:18:13.199> of 01:18:13.370 --> 01:18:13.380 align:start position:0% which makes it extremely lightweight of 01:18:13.380 --> 01:18:15.709 align:start position:0% which makes it extremely lightweight of recomposing<01:18:14.040> the<01:18:14.159> pairs<01:18:14.520> and<01:18:15.239> again<01:18:15.300> this<01:18:15.540> is 01:18:15.709 --> 01:18:15.719 align:start position:0% recomposing the pairs and again this is 01:18:15.719 --> 01:18:17.870 align:start position:0% recomposing the pairs and again this is useful<01:18:16.020> for<01:18:16.260> the<01:18:16.380> following<01:18:16.620> reason 01:18:17.870 --> 01:18:17.880 align:start position:0% useful for the following reason 01:18:17.880 --> 01:18:20.149 align:start position:0% useful for the following reason if<01:18:18.239> you<01:18:18.360> think<01:18:18.480> about<01:18:18.659> and<01:18:19.560> for<01:18:19.739> here<01:18:19.920> I'm 01:18:20.149 --> 01:18:20.159 align:start position:0% if you think about and for here I'm 01:18:20.159 --> 01:18:22.070 align:start position:0% if you think about and for here I'm assuming<01:18:20.520> the<01:18:20.699> payoffs<01:18:21.179> are<01:18:21.420> evaluated<01:18:21.780> just 01:18:22.070 --> 01:18:22.080 align:start position:0% assuming the payoffs are evaluated just 01:18:22.080 --> 01:18:24.169 align:start position:0% assuming the payoffs are evaluated just in<01:18:22.380> one<01:18:22.560> period<01:18:22.860> advanced 01:18:24.169 --> 01:18:24.179 align:start position:0% in one period advanced 01:18:24.179 --> 01:18:25.850 align:start position:0% in one period advanced a<01:18:24.480> proposal<01:18:24.900> do<01:18:25.080> something<01:18:25.260> the<01:18:25.500> validators 01:18:25.850 --> 01:18:25.860 align:start position:0% a proposal do something the validators 01:18:25.860 --> 01:18:27.229 align:start position:0% a proposal do something the validators do<01:18:26.159> something<01:18:26.340> and<01:18:26.520> then<01:18:26.640> in<01:18:26.820> the<01:18:26.880> next<01:18:27.000> period 01:18:27.229 --> 01:18:27.239 align:start position:0% do something and then in the next period 01:18:27.239 --> 01:18:30.110 align:start position:0% do something and then in the next period it<01:18:27.600> gets<01:18:27.840> evaluated<01:18:28.199> what<01:18:28.500> they<01:18:28.679> actually<01:18:28.860> do 01:18:30.110 --> 01:18:30.120 align:start position:0% it gets evaluated what they actually do 01:18:30.120 --> 01:18:31.729 align:start position:0% it gets evaluated what they actually do of<01:18:30.540> course<01:18:30.659> I<01:18:30.840> could<01:18:30.960> have<01:18:31.080> a<01:18:31.199> protocol<01:18:31.440> which 01:18:31.729 --> 01:18:31.739 align:start position:0% of course I could have a protocol which 01:18:31.739 --> 01:18:33.890 align:start position:0% of course I could have a protocol which actually<01:18:32.040> takes<01:18:32.280> more<01:18:32.520> more<01:18:32.820> episodes<01:18:33.120> what 01:18:33.890 --> 01:18:33.900 align:start position:0% actually takes more more episodes what 01:18:33.900 --> 01:18:36.169 align:start position:0% actually takes more more episodes what do<01:18:34.080> I<01:18:34.199> do<01:18:34.320> then<01:18:34.500> I<01:18:35.219> can<01:18:35.340> of<01:18:35.520> course<01:18:35.640> kind<01:18:36.060> of 01:18:36.169 --> 01:18:36.179 align:start position:0% do I do then I can of course kind of 01:18:36.179 --> 01:18:38.510 align:start position:0% do I do then I can of course kind of take<01:18:36.719> the<01:18:36.900> wires<01:18:37.199> put<01:18:37.500> them<01:18:37.679> through<01:18:37.860> which<01:18:38.340> is 01:18:38.510 --> 01:18:38.520 align:start position:0% take the wires put them through which is 01:18:38.520 --> 01:18:40.430 align:start position:0% take the wires put them through which is still<01:18:38.699> okay<01:18:38.820> but<01:18:39.480> I<01:18:39.600> can<01:18:39.719> also<01:18:39.900> just<01:18:40.080> use<01:18:40.260> it 01:18:40.430 --> 01:18:40.440 align:start position:0% still okay but I can also just use it 01:18:40.440 --> 01:18:42.050 align:start position:0% still okay but I can also just use it and<01:18:40.620> say<01:18:40.739> well<01:18:40.980> the<01:18:41.280> information<01:18:41.460> Flows<01:18:41.940> In 01:18:42.050 --> 01:18:42.060 align:start position:0% and say well the information Flows In 01:18:42.060 --> 01:18:44.149 align:start position:0% and say well the information Flows In Direction<01:18:42.239> and<01:18:42.659> I<01:18:42.780> can<01:18:42.900> compose<01:18:43.320> this<01:18:43.620> value 01:18:44.149 --> 01:18:44.159 align:start position:0% Direction and I can compose this value 01:18:44.159 --> 01:18:45.950 align:start position:0% Direction and I can compose this value at<01:18:44.400> payoffs<01:18:44.940> with<01:18:45.300> the<01:18:45.420> same<01:18:45.540> name<01:18:45.719> with<01:18:45.900> the 01:18:45.950 --> 01:18:45.960 align:start position:0% at payoffs with the same name with the 01:18:45.960 --> 01:18:48.050 align:start position:0% at payoffs with the same name with the same<01:18:46.140> identifier<01:18:46.620> again<01:18:47.159> at<01:18:47.460> that<01:18:47.580> point<01:18:47.760> and 01:18:48.050 --> 01:18:48.060 align:start position:0% same identifier again at that point and 01:18:48.060 --> 01:18:50.149 align:start position:0% same identifier again at that point and I'm<01:18:48.179> done<01:18:48.719> it's<01:18:49.320> not<01:18:49.500> something<01:18:49.620> we<01:18:49.920> planned 01:18:50.149 --> 01:18:50.159 align:start position:0% I'm done it's not something we planned 01:18:50.159 --> 01:18:50.990 align:start position:0% I'm done it's not something we planned for<01:18:50.280> but<01:18:50.400> it's<01:18:50.520> just<01:18:50.640> something<01:18:50.820> which 01:18:50.990 --> 01:18:51.000 align:start position:0% for but it's just something which 01:18:51.000 --> 01:18:53.630 align:start position:0% for but it's just something which emerged<01:18:51.480> out<01:18:52.020> of<01:18:52.199> working<01:18:52.380> on<01:18:52.620> this<01:18:53.100> and<01:18:53.580> there 01:18:53.630 --> 01:18:53.640 align:start position:0% emerged out of working on this and there 01:18:53.640 --> 01:18:56.090 align:start position:0% emerged out of working on this and there are<01:18:53.760> other<01:18:53.880> examples<01:18:54.239> like<01:18:54.420> this 01:18:56.090 --> 01:18:56.100 align:start position:0% are other examples like this 01:18:56.100 --> 01:18:57.950 align:start position:0% are other examples like this okay<01:18:56.580> these<01:18:57.000> are<01:18:57.060> the<01:18:57.179> components<01:18:57.659> that<01:18:57.780> we 01:18:57.950 --> 01:18:57.960 align:start position:0% okay these are the components that we 01:18:57.960 --> 01:18:59.090 align:start position:0% okay these are the components that we need 01:18:59.090 --> 01:18:59.100 align:start position:0% need 01:18:59.100 --> 01:19:03.169 align:start position:0% need um<01:18:59.159> now<01:18:59.699> we<01:18:59.820> want<01:18:59.940> to<01:19:00.060> take<01:19:00.179> the<01:19:00.360> next<01:19:00.480> step 01:19:03.169 --> 01:19:03.179 align:start position:0% 01:19:03.179 --> 01:19:09.649 align:start position:0% first<01:19:03.780> I'll<01:19:04.560> be<01:19:04.800> awesome 01:19:09.649 --> 01:19:09.659 align:start position:0% 01:19:09.659 --> 01:19:21.169 align:start position:0% we<01:19:09.960> have<01:19:10.080> not<01:19:10.199> only<01:19:10.380> one<01:19:10.560> validator 01:19:21.169 --> 01:19:21.179 align:start position:0% 01:19:21.179 --> 01:19:24.050 align:start position:0% but<01:19:22.020> we<01:19:22.199> have<01:19:22.320> several 01:19:24.050 --> 01:19:24.060 align:start position:0% but we have several 01:19:24.060 --> 01:19:25.790 align:start position:0% but we have several what<01:19:24.540> we<01:19:24.659> do<01:19:24.780> here<01:19:24.960> we<01:19:25.199> are<01:19:25.320> grouping<01:19:25.679> them 01:19:25.790 --> 01:19:25.800 align:start position:0% what we do here we are grouping them 01:19:25.800 --> 01:19:28.310 align:start position:0% what we do here we are grouping them together<01:19:26.040> right<01:19:26.760> so<01:19:26.940> we<01:19:27.239> say<01:19:27.360> well<01:19:27.659> there's<01:19:28.080> a 01:19:28.310 --> 01:19:28.320 align:start position:0% together right so we say well there's a 01:19:28.320 --> 01:19:29.990 align:start position:0% together right so we say well there's a chain<01:19:28.440> U<01:19:28.679> chain<01:19:28.920> old<01:19:29.219> input<01:19:29.520> and<01:19:29.699> then<01:19:29.820> there 01:19:29.990 --> 01:19:30.000 align:start position:0% chain U chain old input and then there 01:19:30.000 --> 01:19:31.729 align:start position:0% chain U chain old input and then there is<01:19:30.120> some<01:19:30.300> kind<01:19:30.420> of<01:19:30.540> information<01:19:30.719> this<01:19:31.440> is<01:19:31.560> just 01:19:31.729 --> 01:19:31.739 align:start position:0% is some kind of information this is just 01:19:31.739 --> 01:19:34.610 align:start position:0% is some kind of information this is just information<01:19:31.920> about<01:19:32.280> past<01:19:32.640> behavior<01:19:33.179> from<01:19:34.080> the 01:19:34.610 --> 01:19:34.620 align:start position:0% information about past behavior from the 01:19:34.620 --> 01:19:36.830 align:start position:0% information about past behavior from the other<01:19:35.120> validators<01:19:36.120> from<01:19:36.300> the<01:19:36.420> period<01:19:36.659> before 01:19:36.830 --> 01:19:36.840 align:start position:0% other validators from the period before 01:19:36.840 --> 01:19:38.750 align:start position:0% other validators from the period before and<01:19:37.560> then<01:19:37.739> the<01:19:37.980> thing<01:19:38.100> is<01:19:38.219> what<01:19:38.460> this<01:19:38.640> should 01:19:38.750 --> 01:19:38.760 align:start position:0% and then the thing is what this should 01:19:38.760 --> 01:19:40.850 align:start position:0% and then the thing is what this should observe<01:19:39.120> is<01:19:39.239> the<01:19:39.360> following<01:19:39.659> here<01:19:40.500> and<01:19:40.679> here 01:19:40.850 --> 01:19:40.860 align:start position:0% observe is the following here and here 01:19:40.860 --> 01:19:42.950 align:start position:0% observe is the following here and here validator<01:19:41.460> this<01:19:42.000> is<01:19:42.120> the<01:19:42.239> construct<01:19:42.600> which<01:19:42.780> is 01:19:42.950 --> 01:19:42.960 align:start position:0% validator this is the construct which is 01:19:42.960 --> 01:19:44.870 align:start position:0% validator this is the construct which is on<01:19:43.080> the<01:19:43.199> right<01:19:43.320> hand<01:19:43.440> side<01:19:43.620> so<01:19:44.340> we<01:19:44.520> take<01:19:44.640> that 01:19:44.870 --> 01:19:44.880 align:start position:0% on the right hand side so we take that 01:19:44.880 --> 01:19:48.229 align:start position:0% on the right hand side so we take that and<01:19:45.120> block<01:19:45.300> in<01:19:45.540> the<01:19:45.659> open<01:19:45.719> game<01:19:46.020> here<01:19:46.800> and<01:19:47.520> this 01:19:48.229 --> 01:19:48.239 align:start position:0% and block in the open game here and this 01:19:48.239 --> 01:19:50.390 align:start position:0% and block in the open game here and this is<01:19:48.420> basically<01:19:49.140> the<01:19:49.380> second<01:19:49.500> step<01:19:49.800> of<01:19:49.980> nesting 01:19:50.390 --> 01:19:50.400 align:start position:0% is basically the second step of nesting 01:19:50.400 --> 01:19:52.610 align:start position:0% is basically the second step of nesting we<01:19:50.699> already<01:19:50.880> have<01:19:51.060> one<01:19:51.300> for<01:19:51.420> the<01:19:51.600> proposal<01:19:52.080> but 01:19:52.610 --> 01:19:52.620 align:start position:0% we already have one for the proposal but 01:19:52.620 --> 01:19:54.229 align:start position:0% we already have one for the proposal but for<01:19:52.739> the<01:19:52.860> validator<01:19:53.159> basically<01:19:53.580> we<01:19:53.760> bottle<01:19:53.940> it 01:19:54.229 --> 01:19:54.239 align:start position:0% for the validator basically we bottle it 01:19:54.239 --> 01:19:55.550 align:start position:0% for the validator basically we bottle it as<01:19:54.360> an<01:19:54.420> open<01:19:54.540> game<01:19:54.780> and<01:19:54.960> then<01:19:55.020> we<01:19:55.140> plug<01:19:55.320> it<01:19:55.440> into 01:19:55.550 --> 01:19:55.560 align:start position:0% as an open game and then we plug it into 01:19:55.560 --> 01:19:58.729 align:start position:0% as an open game and then we plug it into the<01:19:55.920> group<01:19:56.040> and<01:19:56.760> now<01:19:56.940> you<01:19:57.060> can<01:19:57.179> also<01:19:57.540> see 01:19:58.729 --> 01:19:58.739 align:start position:0% the group and now you can also see 01:19:58.739 --> 01:20:01.970 align:start position:0% the group and now you can also see um<01:19:58.800> the<01:19:59.719> the<01:20:00.719> structure<01:20:01.260> basically<01:20:01.620> of<01:20:01.800> that 01:20:01.970 --> 01:20:01.980 align:start position:0% um the the structure basically of that 01:20:01.980 --> 01:20:03.649 align:start position:0% um the the structure basically of that component<01:20:02.340> validator's<01:20:03.000> group<01:20:03.060> decision<01:20:03.360> is 01:20:03.649 --> 01:20:03.659 align:start position:0% component validator's group decision is 01:20:03.659 --> 01:20:05.450 align:start position:0% component validator's group decision is made<01:20:03.840> that<01:20:04.440> you<01:20:04.620> can<01:20:04.739> also<01:20:04.920> extend<01:20:05.159> the<01:20:05.280> number 01:20:05.450 --> 01:20:05.460 align:start position:0% made that you can also extend the number 01:20:05.460 --> 01:20:06.649 align:start position:0% made that you can also extend the number of<01:20:05.580> players<01:20:05.820> if<01:20:06.000> you<01:20:06.060> want<01:20:06.179> you<01:20:06.480> just 01:20:06.649 --> 01:20:06.659 align:start position:0% of players if you want you just 01:20:06.659 --> 01:20:08.450 align:start position:0% of players if you want you just basically<01:20:06.960> add<01:20:07.199> one<01:20:07.380> line<01:20:07.560> here<01:20:07.860> add 01:20:08.450 --> 01:20:08.460 align:start position:0% basically add one line here add 01:20:08.460 --> 01:20:09.770 align:start position:0% basically add one line here add functionality<01:20:09.060> but<01:20:09.360> the<01:20:09.540> overall 01:20:09.770 --> 01:20:09.780 align:start position:0% functionality but the overall 01:20:09.780 --> 01:20:11.870 align:start position:0% functionality but the overall interfacing<01:20:10.320> of<01:20:10.440> that<01:20:10.620> group<01:20:10.800> of<01:20:11.100> decision 01:20:11.870 --> 01:20:11.880 align:start position:0% interfacing of that group of decision 01:20:11.880 --> 01:20:13.310 align:start position:0% interfacing of that group of decision making<01:20:12.060> process<01:20:12.480> is<01:20:12.659> the<01:20:12.840> same<01:20:12.960> whether<01:20:13.080> it's 01:20:13.310 --> 01:20:13.320 align:start position:0% making process is the same whether it's 01:20:13.320 --> 01:20:15.470 align:start position:0% making process is the same whether it's 100<01:20:13.500> or<01:20:13.800> just<01:20:14.040> two<01:20:14.280> and<01:20:14.760> there<01:20:14.940> are<01:20:15.060> also<01:20:15.239> ways 01:20:15.470 --> 01:20:15.480 align:start position:0% 100 or just two and there are also ways 01:20:15.480 --> 01:20:17.030 align:start position:0% 100 or just two and there are also ways I<01:20:15.600> should<01:20:15.719> say<01:20:15.900> this<01:20:16.020> you<01:20:16.380> don't<01:20:16.500> always<01:20:16.739> have 01:20:17.030 --> 01:20:17.040 align:start position:0% I should say this you don't always have 01:20:17.040 --> 01:20:18.410 align:start position:0% I should say this you don't always have to<01:20:17.219> make<01:20:17.280> this<01:20:17.460> explicit<01:20:17.940> if<01:20:18.120> they<01:20:18.239> are 01:20:18.410 --> 01:20:18.420 align:start position:0% to make this explicit if they are 01:20:18.420 --> 01:20:20.149 align:start position:0% to make this explicit if they are symmetric<01:20:18.900> in<01:20:19.020> some<01:20:19.199> sense<01:20:19.380> there's<01:20:19.920> also 01:20:20.149 --> 01:20:20.159 align:start position:0% symmetric in some sense there's also 01:20:20.159 --> 01:20:21.709 align:start position:0% symmetric in some sense there's also convenience<01:20:20.580> patterns<01:20:21.000> such<01:20:21.179> as<01:20:21.239> you<01:20:21.420> can<01:20:21.540> say 01:20:21.709 --> 01:20:21.719 align:start position:0% convenience patterns such as you can say 01:20:21.719 --> 01:20:23.750 align:start position:0% convenience patterns such as you can say here<01:20:22.260> 10<01:20:22.560> players<01:20:22.800> of<01:20:22.980> the<01:20:23.100> same<01:20:23.280> type<01:20:23.400> put 01:20:23.750 --> 01:20:23.760 align:start position:0% here 10 players of the same type put 01:20:23.760 --> 01:20:24.729 align:start position:0% here 10 players of the same type put them<01:20:23.940> there 01:20:24.729 --> 01:20:24.739 align:start position:0% them there 01:20:24.739 --> 01:20:26.990 align:start position:0% them there good<01:20:25.739> so<01:20:26.040> this<01:20:26.159> is<01:20:26.280> the<01:20:26.400> validated<01:20:26.699> group 01:20:26.990 --> 01:20:27.000 align:start position:0% good so this is the validated group 01:20:27.000 --> 01:20:28.669 align:start position:0% good so this is the validated group decision 01:20:28.669 --> 01:20:28.679 align:start position:0% decision 01:20:28.679 --> 01:20:30.410 align:start position:0% decision we<01:20:29.219> also<01:20:29.460> need<01:20:29.580> to<01:20:29.699> make<01:20:29.820> the<01:20:29.940> payment<01:20:30.060> for<01:20:30.300> the 01:20:30.410 --> 01:20:30.420 align:start position:0% we also need to make the payment for the 01:20:30.420 --> 01:20:32.390 align:start position:0% we also need to make the payment for the validators<01:20:30.840> again<01:20:31.500> it's<01:20:31.860> not<01:20:32.040> only<01:20:32.219> one 01:20:32.390 --> 01:20:32.400 align:start position:0% validators again it's not only one 01:20:32.400 --> 01:20:34.790 align:start position:0% validators again it's not only one validated<01:20:32.940> but<01:20:33.179> two<01:20:33.360> and<01:20:34.140> again<01:20:34.380> you<01:20:34.679> could 01:20:34.790 --> 01:20:34.800 align:start position:0% validated but two and again you could 01:20:34.800 --> 01:20:36.110 align:start position:0% validated but two and again you could think<01:20:34.920> about<01:20:35.100> this<01:20:35.280> as<01:20:35.400> being<01:20:35.580> extended<01:20:36.060> to 01:20:36.110 --> 01:20:36.120 align:start position:0% think about this as being extended to 01:20:36.120 --> 01:20:37.910 align:start position:0% think about this as being extended to more<01:20:36.300> players 01:20:37.910 --> 01:20:37.920 align:start position:0% more players 01:20:37.920 --> 01:20:39.590 align:start position:0% more players the<01:20:38.280> thing<01:20:38.400> to<01:20:38.520> keep<01:20:38.640> in<01:20:38.820> mind 01:20:39.590 --> 01:20:39.600 align:start position:0% the thing to keep in mind 01:20:39.600 --> 01:20:40.910 align:start position:0% the thing to keep in mind um is<01:20:39.719> again<01:20:39.960> is 01:20:40.910 --> 01:20:40.920 align:start position:0% um is again is 01:20:40.920 --> 01:20:42.110 align:start position:0% um is again is um and<01:20:41.159> I<01:20:41.219> repeat<01:20:41.340> myself<01:20:41.640> but<01:20:41.940> it's 01:20:42.110 --> 01:20:42.120 align:start position:0% um and I repeat myself but it's 01:20:42.120 --> 01:20:44.810 align:start position:0% um and I repeat myself but it's important<01:20:42.420> this<01:20:43.140> validation<01:20:43.560> step<01:20:43.800> is<01:20:44.159> in 01:20:44.810 --> 01:20:44.820 align:start position:0% important this validation step is in 01:20:44.820 --> 01:20:50.510 align:start position:0% important this validation step is in time<01:20:45.000> t<01:20:45.360> for<01:20:46.080> the<01:20:46.260> behavior<01:20:46.679> of<01:20:47.040> T<01:20:47.640> minus<01:20:48.060> one 01:20:50.510 --> 01:20:50.520 align:start position:0% 01:20:50.520 --> 01:20:55.130 align:start position:0% yes<01:20:50.940> you<01:20:51.120> have<01:20:51.300> a<01:20:51.420> question 01:20:55.130 --> 01:20:55.140 align:start position:0% 01:20:55.140 --> 01:20:59.090 align:start position:0% okay 01:20:59.090 --> 01:20:59.100 align:start position:0% 01:20:59.100 --> 01:21:01.070 align:start position:0% maybe<01:20:59.580> you<01:20:59.820> ask<01:21:00.480> a<01:21:00.600> question<01:21:00.719> again<01:21:00.900> and 01:21:01.070 --> 01:21:01.080 align:start position:0% maybe you ask a question again and 01:21:01.080 --> 01:21:03.649 align:start position:0% maybe you ask a question again and everyone<01:21:01.199> yeah<01:21:01.679> he<01:21:02.159> was<01:21:02.340> asking<01:21:02.699> uh<01:21:03.300> I'd<01:21:03.540> like 01:21:03.649 --> 01:21:03.659 align:start position:0% everyone yeah he was asking uh I'd like 01:21:03.659 --> 01:21:05.990 align:start position:0% everyone yeah he was asking uh I'd like to<01:21:03.840> know<01:21:04.020> what's<01:21:04.500> operation<01:21:05.100> the<01:21:05.640> operation 01:21:05.990 --> 01:21:06.000 align:start position:0% to know what's operation the operation 01:21:06.000 --> 01:21:07.970 align:start position:0% to know what's operation the operation field<01:21:06.239> basically<01:21:06.659> the<01:21:06.960> operation<01:21:07.199> field<01:21:07.440> okay 01:21:07.970 --> 01:21:07.980 align:start position:0% field basically the operation field okay 01:21:07.980 --> 01:21:09.950 align:start position:0% field basically the operation field okay the<01:21:08.460> operation<01:21:08.760> field<01:21:09.060> is<01:21:09.420> from<01:21:09.840> one 01:21:09.950 --> 01:21:09.960 align:start position:0% the operation field is from one 01:21:09.960 --> 01:21:11.689 align:start position:0% the operation field is from one perspective<01:21:10.380> basically<01:21:10.800> what<01:21:10.980> the<01:21:11.159> where<01:21:11.520> the 01:21:11.689 --> 01:21:11.699 align:start position:0% perspective basically what the where the 01:21:11.699 --> 01:21:13.610 align:start position:0% perspective basically what the where the the<01:21:12.360> um<01:21:12.360> strategic<01:21:12.719> information<01:21:12.960> is<01:21:13.320> created 01:21:13.610 --> 01:21:13.620 align:start position:0% the um strategic information is created 01:21:13.620 --> 01:21:15.830 align:start position:0% the um strategic information is created if<01:21:14.100> it's<01:21:14.219> a<01:21:14.400> function<01:21:14.699> it<01:21:15.420> will<01:21:15.540> be<01:21:15.659> just 01:21:15.830 --> 01:21:15.840 align:start position:0% if it's a function it will be just 01:21:15.840 --> 01:21:17.390 align:start position:0% if it's a function it will be just saying 01:21:17.390 --> 01:21:17.400 align:start position:0% saying 01:21:17.400 --> 01:21:20.990 align:start position:0% saying um<01:21:17.580> let<01:21:17.940> me<01:21:18.060> give<01:21:18.239> you<01:21:18.360> the<01:21:18.480> example 01:21:20.990 --> 01:21:21.000 align:start position:0% 01:21:21.000 --> 01:21:22.070 align:start position:0% here 01:21:22.070 --> 01:21:22.080 align:start position:0% here 01:21:22.080 --> 01:21:24.470 align:start position:0% here I'm<01:21:22.500> filling<01:21:22.860> the<01:21:23.040> operation<01:21:23.520> with<01:21:23.940> basically 01:21:24.470 --> 01:21:24.480 align:start position:0% I'm filling the operation with basically 01:21:24.480 --> 01:21:26.810 align:start position:0% I'm filling the operation with basically two<01:21:24.719> keywords<01:21:25.199> namely<01:21:25.500> either 01:21:26.810 --> 01:21:26.820 align:start position:0% two keywords namely either 01:21:26.820 --> 01:21:28.510 align:start position:0% two keywords namely either um<01:21:26.940> forward<01:21:27.239> function 01:21:28.510 --> 01:21:28.520 align:start position:0% um forward function 01:21:28.520 --> 01:21:32.030 align:start position:0% um forward function or<01:21:29.520> depend<01:21:30.000> decision<01:21:30.780> yeah<01:21:31.260> what<01:21:31.800> is<01:21:31.920> the 01:21:32.030 --> 01:21:32.040 align:start position:0% or depend decision yeah what is the 01:21:32.040 --> 01:21:33.530 align:start position:0% or depend decision yeah what is the forward<01:21:32.100> function<01:21:32.460> doing<01:21:32.760> it's<01:21:32.940> just<01:21:33.179> lifting 01:21:33.530 --> 01:21:33.540 align:start position:0% forward function doing it's just lifting 01:21:33.540 --> 01:21:34.790 align:start position:0% forward function doing it's just lifting a<01:21:33.659> normal<01:21:33.780> function<01:21:34.140> a<01:21:34.320> normal<01:21:34.440> Haskell 01:21:34.790 --> 01:21:34.800 align:start position:0% a normal function a normal Haskell 01:21:34.800 --> 01:21:36.290 align:start position:0% a normal function a normal Haskell function<01:21:35.040> into<01:21:35.219> an<01:21:35.400> open<01:21:35.520> gain<01:21:35.820> which<01:21:36.060> means 01:21:36.290 --> 01:21:36.300 align:start position:0% function into an open gain which means 01:21:36.300 --> 01:21:38.090 align:start position:0% function into an open gain which means in<01:21:37.199> the<01:21:37.320> simplest<01:21:37.560> case<01:21:37.679> it's<01:21:37.800> just<01:21:37.920> a 01:21:38.090 --> 01:21:38.100 align:start position:0% in the simplest case it's just a 01:21:38.100 --> 01:21:40.130 align:start position:0% in the simplest case it's just a deterministic<01:21:38.640> function<01:21:38.880> that<01:21:39.540> determined 01:21:40.130 --> 01:21:40.140 align:start position:0% deterministic function that determined 01:21:40.140 --> 01:21:40.790 align:start position:0% deterministic function that determined head 01:21:40.790 --> 01:21:40.800 align:start position:0% head 01:21:40.800 --> 01:21:43.130 align:start position:0% head takes<01:21:41.280> a<01:21:41.520> chain<01:21:41.699> and<01:21:42.060> outputs<01:21:42.480> ahead<01:21:42.780> and<01:21:43.020> then 01:21:43.130 --> 01:21:43.140 align:start position:0% takes a chain and outputs ahead and then 01:21:43.140 --> 01:21:44.149 align:start position:0% takes a chain and outputs ahead and then I'm<01:21:43.260> interfacing<01:21:43.739> it<01:21:43.860> with<01:21:43.980> the<01:21:44.040> outside 01:21:44.149 --> 01:21:44.159 align:start position:0% I'm interfacing it with the outside 01:21:44.159 --> 01:21:45.410 align:start position:0% I'm interfacing it with the outside world 01:21:45.410 --> 01:21:45.420 align:start position:0% world 01:21:45.420 --> 01:21:47.330 align:start position:0% world if<01:21:45.719> you're<01:21:45.840> talking<01:21:46.080> about<01:21:46.199> a<01:21:46.440> decision<01:21:46.739> it's 01:21:47.330 --> 01:21:47.340 align:start position:0% if you're talking about a decision it's 01:21:47.340 --> 01:21:49.310 align:start position:0% if you're talking about a decision it's different<01:21:47.580> look<01:21:48.000> at<01:21:48.179> the<01:21:48.300> validator<01:21:48.659> this<01:21:49.260> is 01:21:49.310 --> 01:21:49.320 align:start position:0% different look at the validator this is 01:21:49.320 --> 01:21:51.169 align:start position:0% different look at the validator this is the<01:21:49.500> keyword<01:21:49.739> dependent<01:21:50.280> decision<01:21:50.580> the 01:21:51.169 --> 01:21:51.179 align:start position:0% the keyword dependent decision the 01:21:51.179 --> 01:21:53.270 align:start position:0% the keyword dependent decision the validator<01:21:51.600> in<01:21:52.140> this<01:21:52.500> case<01:21:52.620> the<01:21:52.860> decision<01:21:53.100> is 01:21:53.270 --> 01:21:53.280 align:start position:0% validator in this case the decision is 01:21:53.280 --> 01:21:54.410 align:start position:0% validator in this case the decision is the<01:21:53.460> following 01:21:54.410 --> 01:21:54.420 align:start position:0% the following 01:21:54.420 --> 01:21:57.350 align:start position:0% the following the<01:21:54.840> player<01:21:55.140> observes<01:21:55.739> this<01:21:56.580> chain<01:21:56.760> U<01:21:57.060> chain 01:21:57.350 --> 01:21:57.360 align:start position:0% the player observes this chain U chain 01:21:57.360 --> 01:21:59.390 align:start position:0% the player observes this chain U chain old<01:21:57.659> that<01:21:58.380> this<01:21:58.500> observation<01:21:58.920> is<01:21:59.159> information 01:21:59.390 --> 01:21:59.400 align:start position:0% old that this observation is information 01:21:59.400 --> 01:22:01.850 align:start position:0% old that this observation is information and<01:22:00.060> then<01:22:00.179> he<01:22:00.300> makes<01:22:00.480> a<01:22:00.659> move<01:22:00.900> he<01:22:01.380> has<01:22:01.560> to<01:22:01.679> pick 01:22:01.850 --> 01:22:01.860 align:start position:0% and then he makes a move he has to pick 01:22:01.860 --> 01:22:03.709 align:start position:0% and then he makes a move he has to pick an<01:22:02.040> element<01:22:02.219> and<01:22:02.760> this<01:22:02.940> element<01:22:03.060> in<01:22:03.420> that<01:22:03.540> case 01:22:03.709 --> 01:22:03.719 align:start position:0% an element and this element in that case 01:22:03.719 --> 01:22:06.649 align:start position:0% an element and this element in that case is<01:22:04.020> an<01:22:04.260> index<01:22:04.560> to<01:22:04.880> which<01:22:05.880> of<01:22:06.360> the<01:22:06.540> block 01:22:06.649 --> 01:22:06.659 align:start position:0% is an index to which of the block 01:22:06.659 --> 01:22:08.930 align:start position:0% is an index to which of the block elements<01:22:07.199> do<01:22:07.380> I<01:22:07.560> believe<01:22:07.679> to<01:22:07.980> be<01:22:08.159> the<01:22:08.460> head<01:22:08.699> or 01:22:08.930 --> 01:22:08.940 align:start position:0% elements do I believe to be the head or 01:22:08.940 --> 01:22:14.510 align:start position:0% elements do I believe to be the head or I'm<01:22:09.120> choosing<01:22:09.540> to<01:22:10.140> be<01:22:10.320> the<01:22:10.440> head<01:22:11.100> yeah<01:22:11.699> okay 01:22:14.510 --> 01:22:14.520 align:start position:0% 01:22:14.520 --> 01:22:16.250 align:start position:0% then<01:22:15.179> there'll<01:22:15.420> be<01:22:15.540> an<01:22:15.659> operation<01:22:15.960> between 01:22:16.250 --> 01:22:16.260 align:start position:0% then there'll be an operation between 01:22:16.260 --> 01:22:19.250 align:start position:0% then there'll be an operation between returns<01:22:16.860> and<01:22:16.920> feedback 01:22:19.250 --> 01:22:19.260 align:start position:0% 01:22:19.260 --> 01:22:21.950 align:start position:0% sorry<01:22:19.500> second<01:22:19.860> like<01:22:20.820> so<01:22:21.120> so<01:22:21.300> this<01:22:21.600> is<01:22:21.780> doing 01:22:21.950 --> 01:22:21.960 align:start position:0% sorry second like so so this is doing 01:22:21.960 --> 01:22:25.189 align:start position:0% sorry second like so so this is doing the<01:22:22.199> like<01:22:22.380> from<01:22:23.060> left<01:22:24.060> to<01:22:24.360> right<01:22:24.719> yeah 01:22:25.189 --> 01:22:25.199 align:start position:0% the like from left to right yeah 01:22:25.199 --> 01:22:27.649 align:start position:0% the like from left to right yeah movement<01:22:25.800> correct<01:22:26.520> and<01:22:27.060> what<01:22:27.300> about<01:22:27.420> the 01:22:27.649 --> 01:22:27.659 align:start position:0% movement correct and what about the 01:22:27.659 --> 01:22:30.050 align:start position:0% movement correct and what about the other<01:22:27.960> direction<01:22:28.440> okay<01:22:29.340> that's<01:22:29.640> a<01:22:29.820> good<01:22:29.940> point 01:22:30.050 --> 01:22:30.060 align:start position:0% other direction okay that's a good point 01:22:30.060 --> 01:22:32.990 align:start position:0% other direction okay that's a good point so<01:22:30.239> first<01:22:30.480> let's<01:22:31.260> take<01:22:31.560> one<01:22:31.800> step<01:22:32.040> back<01:22:32.699> um<01:22:32.760> if 01:22:32.990 --> 01:22:33.000 align:start position:0% so first let's take one step back um if 01:22:33.000 --> 01:22:34.130 align:start position:0% so first let's take one step back um if you<01:22:33.060> think<01:22:33.179> about<01:22:33.300> the<01:22:33.480> prisoner<01:22:33.780> dilemma 01:22:34.130 --> 01:22:34.140 align:start position:0% you think about the prisoner dilemma 01:22:34.140 --> 01:22:36.290 align:start position:0% you think about the prisoner dilemma there<01:22:34.679> was<01:22:34.800> also<01:22:34.980> the<01:22:35.159> case<01:22:35.280> where<01:22:35.520> the<01:22:35.760> agents 01:22:36.290 --> 01:22:36.300 align:start position:0% there was also the case where the agents 01:22:36.300 --> 01:22:38.330 align:start position:0% there was also the case where the agents did<01:22:36.840> not<01:22:37.020> send<01:22:37.320> information<01:22:37.560> back<01:22:37.920> into<01:22:38.100> the 01:22:38.330 --> 01:22:38.340 align:start position:0% did not send information back into the 01:22:38.340 --> 01:22:42.169 align:start position:0% did not send information back into the past<01:22:38.520> yeah<01:22:39.480> okay<01:22:40.260> so<01:22:40.800> that<01:22:40.980> explains<01:22:41.520> and<01:22:42.060> the 01:22:42.169 --> 01:22:42.179 align:start position:0% past yeah okay so that explains and the 01:22:42.179 --> 01:22:44.330 align:start position:0% past yeah okay so that explains and the reasoning<01:22:42.659> is<01:22:42.780> simply<01:22:43.020> here<01:22:43.199> I<01:22:43.800> don't<01:22:43.860> need<01:22:44.100> to 01:22:44.330 --> 01:22:44.340 align:start position:0% reasoning is simply here I don't need to 01:22:44.340 --> 01:22:45.890 align:start position:0% reasoning is simply here I don't need to send<01:22:44.460> the<01:22:44.640> information<01:22:44.820> from<01:22:45.360> these<01:22:45.600> players 01:22:45.890 --> 01:22:45.900 align:start position:0% send the information from these players 01:22:45.900 --> 01:22:48.290 align:start position:0% send the information from these players back<01:22:46.500> into<01:22:46.620> the<01:22:46.920> past<01:22:47.100> and<01:22:47.880> the<01:22:48.000> reason<01:22:48.120> I 01:22:48.290 --> 01:22:48.300 align:start position:0% back into the past and the reason I 01:22:48.300 --> 01:22:50.209 align:start position:0% back into the past and the reason I don't<01:22:48.420> need<01:22:48.600> to<01:22:48.659> do<01:22:48.840> that<01:22:48.960> is 01:22:50.209 --> 01:22:50.219 align:start position:0% don't need to do that is 01:22:50.219 --> 01:22:52.010 align:start position:0% don't need to do that is um<01:22:50.280> there's<01:22:50.640> basically<01:22:51.060> the<01:22:51.300> protocol<01:22:51.780> is 01:22:52.010 --> 01:22:52.020 align:start position:0% um there's basically the protocol is 01:22:52.020 --> 01:22:53.330 align:start position:0% um there's basically the protocol is moving<01:22:52.260> forward<01:22:52.440> and<01:22:52.679> I<01:22:52.800> don't<01:22:52.920> need<01:22:53.040> to<01:22:53.159> send 01:22:53.330 --> 01:22:53.340 align:start position:0% moving forward and I don't need to send 01:22:53.340 --> 01:22:55.490 align:start position:0% moving forward and I don't need to send this<01:22:53.460> information<01:22:53.640> back<01:22:54.540> it's<01:22:55.080> like<01:22:55.260> I'm 01:22:55.490 --> 01:22:55.500 align:start position:0% this information back it's like I'm 01:22:55.500 --> 01:22:56.870 align:start position:0% this information back it's like I'm creating<01:22:55.800> a<01:22:55.920> state<01:22:56.100> and<01:22:56.400> the<01:22:56.580> state<01:22:56.699> will 01:22:56.870 --> 01:22:56.880 align:start position:0% creating a state and the state will 01:22:56.880 --> 01:22:58.970 align:start position:0% creating a state and the state will summarize<01:22:57.239> what<01:22:57.480> is<01:22:57.600> going<01:22:57.719> on<01:22:58.260> why<01:22:58.679> I'm<01:22:58.860> doing 01:22:58.970 --> 01:22:58.980 align:start position:0% summarize what is going on why I'm doing 01:22:58.980 --> 01:23:00.830 align:start position:0% summarize what is going on why I'm doing this<01:22:59.159> in<01:22:59.340> this<01:22:59.460> form<01:22:59.640> is<01:23:00.000> the<01:23:00.239> following<01:23:00.540> the 01:23:00.830 --> 01:23:00.840 align:start position:0% this in this form is the following the 01:23:00.840 --> 01:23:02.510 align:start position:0% this in this form is the following the following<01:23:01.080> reason<01:23:01.260> I<01:23:01.560> will<01:23:01.679> end<01:23:01.860> up<01:23:01.980> with<01:23:02.340> one 01:23:02.510 --> 01:23:02.520 align:start position:0% following reason I will end up with one 01:23:02.520 --> 01:23:03.410 align:start position:0% following reason I will end up with one episode 01:23:03.410 --> 01:23:03.420 align:start position:0% episode 01:23:03.420 --> 01:23:05.330 align:start position:0% episode that<01:23:03.900> episode<01:23:04.080> will<01:23:04.440> be<01:23:04.620> basically<01:23:04.860> a<01:23:05.100> basic 01:23:05.330 --> 01:23:05.340 align:start position:0% that episode will be basically a basic 01:23:05.340 --> 01:23:07.130 align:start position:0% that episode will be basically a basic game<01:23:05.460> for<01:23:05.580> Markov<01:23:06.000> game<01:23:06.239> and<01:23:06.780> then<01:23:06.900> I<01:23:07.020> can 01:23:07.130 --> 01:23:07.140 align:start position:0% game for Markov game and then I can 01:23:07.140 --> 01:23:08.390 align:start position:0% game for Markov game and then I can stack<01:23:07.380> these<01:23:07.620> again<01:23:07.739> on<01:23:07.980> it<01:23:08.040> on<01:23:08.159> each<01:23:08.280> other 01:23:08.390 --> 01:23:08.400 align:start position:0% stack these again on it on each other 01:23:08.400 --> 01:23:11.209 align:start position:0% stack these again on it on each other and<01:23:08.580> repeat<01:23:08.699> them<01:23:08.940> if<01:23:09.120> I<01:23:09.300> want<01:23:09.360> to 01:23:11.209 --> 01:23:11.219 align:start position:0% and repeat them if I want to 01:23:11.219 --> 01:23:13.430 align:start position:0% and repeat them if I want to now<01:23:11.580> you<01:23:12.179> are<01:23:12.300> right<01:23:12.480> if<01:23:12.780> you<01:23:12.840> wanted<01:23:12.960> let's 01:23:13.430 --> 01:23:13.440 align:start position:0% now you are right if you wanted let's 01:23:13.440 --> 01:23:14.990 align:start position:0% now you are right if you wanted let's say<01:23:13.560> you<01:23:13.739> you're<01:23:14.040> just<01:23:14.280> explicitly<01:23:14.640> wanted<01:23:14.820> to 01:23:14.990 --> 01:23:15.000 align:start position:0% say you you're just explicitly wanted to 01:23:15.000 --> 01:23:17.689 align:start position:0% say you you're just explicitly wanted to model<01:23:15.120> two<01:23:15.420> episodes<01:23:15.659> you<01:23:16.380> could<01:23:16.500> say 01:23:17.689 --> 01:23:17.699 align:start position:0% model two episodes you could say 01:23:17.699 --> 01:23:18.410 align:start position:0% model two episodes you could say um 01:23:18.410 --> 01:23:18.420 align:start position:0% um 01:23:18.420 --> 01:23:20.330 align:start position:0% um parts<01:23:18.840> of<01:23:19.080> these<01:23:19.260> elements<01:23:19.620> for<01:23:20.040> instance 01:23:20.330 --> 01:23:20.340 align:start position:0% parts of these elements for instance 01:23:20.340 --> 01:23:22.550 align:start position:0% parts of these elements for instance what<01:23:21.300> these<01:23:21.540> guys<01:23:21.600> expect<01:23:21.900> here<01:23:22.199> what<01:23:22.440> the 01:23:22.550 --> 01:23:22.560 align:start position:0% what these guys expect here what the 01:23:22.560 --> 01:23:24.110 align:start position:0% what these guys expect here what the return<01:23:22.679> is<01:23:22.920> is<01:23:23.219> actually<01:23:23.400> coming<01:23:23.640> from<01:23:23.880> this 01:23:24.110 --> 01:23:24.120 align:start position:0% return is is actually coming from this 01:23:24.120 --> 01:23:25.970 align:start position:0% return is is actually coming from this returns<01:23:24.540> field<01:23:24.719> over<01:23:24.960> here<01:23:25.199> and<01:23:25.739> I<01:23:25.920> said 01:23:25.970 --> 01:23:25.980 align:start position:0% returns field over here and I said 01:23:25.980 --> 01:23:27.709 align:start position:0% returns field over here and I said before<01:23:26.159> you<01:23:26.460> can<01:23:26.580> do<01:23:26.760> that<01:23:26.940> the<01:23:27.360> reason<01:23:27.540> I'm 01:23:27.709 --> 01:23:27.719 align:start position:0% before you can do that the reason I'm 01:23:27.719 --> 01:23:29.810 align:start position:0% before you can do that the reason I'm not<01:23:27.840> doing<01:23:27.960> it<01:23:28.140> is<01:23:28.260> here<01:23:28.500> is<01:23:28.980> exactly<01:23:29.340> for<01:23:29.460> if<01:23:29.640> I 01:23:29.810 --> 01:23:29.820 align:start position:0% not doing it is here is exactly for if I 01:23:29.820 --> 01:23:31.729 align:start position:0% not doing it is here is exactly for if I want<01:23:29.880> to<01:23:30.000> Stack<01:23:30.239> more<01:23:30.480> more<01:23:30.840> episodes<01:23:31.080> with 01:23:31.729 --> 01:23:31.739 align:start position:0% want to Stack more more episodes with 01:23:31.739 --> 01:23:33.530 align:start position:0% want to Stack more more episodes with payoff<01:23:32.219> still<01:23:32.400> being<01:23:32.580> created<01:23:32.880> for<01:23:33.179> players 01:23:33.530 --> 01:23:33.540 align:start position:0% payoff still being created for players 01:23:33.540 --> 01:23:36.050 align:start position:0% payoff still being created for players in<01:23:33.840> let's<01:23:34.140> say<01:23:34.320> T<01:23:34.620> minus<01:23:34.980> four<01:23:35.159> I<01:23:35.640> can<01:23:35.760> easier 01:23:36.050 --> 01:23:36.060 align:start position:0% in let's say T minus four I can easier 01:23:36.060 --> 01:23:37.669 align:start position:0% in let's say T minus four I can easier do<01:23:36.300> that 01:23:37.669 --> 01:23:37.679 align:start position:0% do that 01:23:37.679 --> 01:23:39.530 align:start position:0% do that okay 01:23:39.530 --> 01:23:39.540 align:start position:0% okay 01:23:39.540 --> 01:23:41.030 align:start position:0% okay maybe<01:23:39.960> it<01:23:40.140> will<01:23:40.260> become<01:23:40.500> clearer<01:23:40.800> when<01:23:40.920> we 01:23:41.030 --> 01:23:41.040 align:start position:0% maybe it will become clearer when we 01:23:41.040 --> 01:23:42.890 align:start position:0% maybe it will become clearer when we come<01:23:41.219> to<01:23:41.280> the<01:23:41.460> rest<01:23:41.580> if<01:23:41.940> not<01:23:42.120> you<01:23:42.659> know<01:23:42.719> feel 01:23:42.890 --> 01:23:42.900 align:start position:0% come to the rest if not you know feel 01:23:42.900 --> 01:23:44.630 align:start position:0% come to the rest if not you know feel free<01:23:43.020> to<01:23:43.199> ask<01:23:43.260> again 01:23:44.630 --> 01:23:44.640 align:start position:0% free to ask again 01:23:44.640 --> 01:23:47.090 align:start position:0% free to ask again other<01:23:45.120> questions 01:23:47.090 --> 01:23:47.100 align:start position:0% other questions 01:23:47.100 --> 01:23:49.250 align:start position:0% other questions could<01:23:47.580> you<01:23:47.699> tell<01:23:47.820> me<01:23:47.940> the<01:23:48.060> time 01:23:49.250 --> 01:23:49.260 align:start position:0% could you tell me the time 01:23:49.260 --> 01:23:50.330 align:start position:0% could you tell me the time yeah 01:23:50.330 --> 01:23:50.340 align:start position:0% yeah 01:23:50.340 --> 01:23:53.149 align:start position:0% yeah 25<01:23:50.699> okay<01:23:51.300> good 01:23:53.149 --> 01:23:53.159 align:start position:0% 25 okay good 01:23:53.159 --> 01:23:56.090 align:start position:0% 25 okay good okay<01:23:53.460> well<01:23:53.640> it<01:23:53.820> is<01:23:54.000> payments<01:23:55.020> um<01:23:55.140> again<01:23:55.739> this 01:23:56.090 --> 01:23:56.100 align:start position:0% okay well it is payments um again this 01:23:56.100 --> 01:23:57.470 align:start position:0% okay well it is payments um again this looks<01:23:56.640> like<01:23:56.760> a<01:23:56.880> bit<01:23:57.000> more<01:23:57.120> you<01:23:57.360> know 01:23:57.470 --> 01:23:57.480 align:start position:0% looks like a bit more you know 01:23:57.480 --> 01:23:59.510 align:start position:0% looks like a bit more you know convenient<01:23:57.960> stuff<01:23:58.199> but<01:23:58.440> this<01:23:58.920> is<01:23:59.040> a<01:23:59.219> I<01:23:59.400> mean 01:23:59.510 --> 01:23:59.520 align:start position:0% convenient stuff but this is a I mean 01:23:59.520 --> 01:24:00.770 align:start position:0% convenient stuff but this is a I mean the<01:23:59.640> question<01:23:59.820> we<01:24:00.060> should<01:24:00.179> ask<01:24:00.300> if<01:24:00.480> you<01:24:00.600> model 01:24:00.770 --> 01:24:00.780 align:start position:0% the question we should ask if you model 01:24:00.780 --> 01:24:02.390 align:start position:0% the question we should ask if you model it<01:24:01.020> yourself<01:24:01.140> is<01:24:01.380> how<01:24:01.560> can<01:24:01.739> you<01:24:01.860> how<01:24:02.159> can<01:24:02.280> you 01:24:02.390 --> 01:24:02.400 align:start position:0% it yourself is how can you how can you 01:24:02.400 --> 01:24:03.830 align:start position:0% it yourself is how can you how can you model<01:24:02.580> it<01:24:02.820> in<01:24:02.940> a<01:24:03.060> way<01:24:03.179> that<01:24:03.540> it's<01:24:03.719> actually 01:24:03.830 --> 01:24:03.840 align:start position:0% model it in a way that it's actually 01:24:03.840 --> 01:24:05.330 align:start position:0% model it in a way that it's actually really<01:24:04.080> a<01:24:04.199> building<01:24:04.320> block 01:24:05.330 --> 01:24:05.340 align:start position:0% really a building block 01:24:05.340 --> 01:24:06.950 align:start position:0% really a building block um<01:24:05.400> I<01:24:05.520> said<01:24:05.699> before<01:24:05.880> one<01:24:06.239> way<01:24:06.360> of<01:24:06.540> doing<01:24:06.659> it<01:24:06.840> is 01:24:06.950 --> 01:24:06.960 align:start position:0% um I said before one way of doing it is 01:24:06.960 --> 01:24:09.709 align:start position:0% um I said before one way of doing it is that<01:24:07.199> the<01:24:07.620> interfaces<01:24:08.400> are<01:24:08.880> relatively 01:24:09.709 --> 01:24:09.719 align:start position:0% that the interfaces are relatively 01:24:09.719 --> 01:24:11.510 align:start position:0% that the interfaces are relatively flexible<01:24:10.080> so<01:24:10.440> I'm<01:24:10.560> just<01:24:10.739> leading<01:24:11.100> the<01:24:11.219> fee 01:24:11.510 --> 01:24:11.520 align:start position:0% flexible so I'm just leading the fee 01:24:11.520 --> 01:24:14.870 align:start position:0% flexible so I'm just leading the fee which<01:24:11.760> is<01:24:11.820> an<01:24:12.000> outside<01:24:12.179> outside<01:24:12.960> parameter 01:24:14.870 --> 01:24:14.880 align:start position:0% which is an outside outside parameter 01:24:14.880 --> 01:24:16.970 align:start position:0% which is an outside outside parameter um and<01:24:15.540> then<01:24:15.659> internally<01:24:16.140> basically<01:24:16.560> I<01:24:16.800> just 01:24:16.970 --> 01:24:16.980 align:start position:0% um and then internally basically I just 01:24:16.980 --> 01:24:20.689 align:start position:0% um and then internally basically I just need<01:24:17.219> the<01:24:18.080> payoffs<01:24:19.080> I<01:24:19.560> need<01:24:19.739> to<01:24:19.980> chain<01:24:20.159> new<01:24:20.400> and 01:24:20.689 --> 01:24:20.699 align:start position:0% need the payoffs I need to chain new and 01:24:20.699 --> 01:24:22.850 align:start position:0% need the payoffs I need to chain new and the<01:24:20.820> hat<01:24:21.060> ID<01:24:21.179> which<01:24:21.600> was<01:24:21.840> chosen<01:24:22.199> and<01:24:22.620> with 01:24:22.850 --> 01:24:22.860 align:start position:0% the hat ID which was chosen and with 01:24:22.860 --> 01:24:24.590 align:start position:0% the hat ID which was chosen and with that<01:24:23.040> basically<01:24:23.460> I<01:24:23.940> have<01:24:24.060> the<01:24:24.179> full<01:24:24.360> picture 01:24:24.590 --> 01:24:24.600 align:start position:0% that basically I have the full picture 01:24:24.600 --> 01:24:27.290 align:start position:0% that basically I have the full picture and<01:24:25.080> that<01:24:25.260> the<01:24:25.440> protocol<01:24:25.800> can<01:24:26.159> evaluate<01:24:26.580> once 01:24:27.290 --> 01:24:27.300 align:start position:0% and that the protocol can evaluate once 01:24:27.300 --> 01:24:29.390 align:start position:0% and that the protocol can evaluate once the<01:24:27.360> behavior<01:24:27.659> actually<01:24:27.840> correct 01:24:29.390 --> 01:24:29.400 align:start position:0% the behavior actually correct 01:24:29.400 --> 01:24:30.950 align:start position:0% the behavior actually correct okay 01:24:30.950 --> 01:24:30.960 align:start position:0% okay 01:24:30.960 --> 01:24:32.149 align:start position:0% okay and<01:24:31.320> you<01:24:31.440> can<01:24:31.560> see<01:24:31.620> this<01:24:31.800> is<01:24:31.980> actually 01:24:32.149 --> 01:24:32.159 align:start position:0% and you can see this is actually 01:24:32.159 --> 01:24:33.350 align:start position:0% and you can see this is actually happening<01:24:32.520> in<01:24:32.640> a<01:24:32.760> function<01:24:32.880> that<01:24:33.060> I<01:24:33.239> didn't 01:24:33.350 --> 01:24:33.360 align:start position:0% happening in a function that I didn't 01:24:33.360 --> 01:24:35.330 align:start position:0% happening in a function that I didn't show<01:24:33.600> you<01:24:33.659> this<01:24:33.840> is<01:24:33.960> a<01:24:34.080> tested<01:24:34.440> correct<01:24:34.739> they 01:24:35.330 --> 01:24:35.340 align:start position:0% show you this is a tested correct they 01:24:35.340 --> 01:24:37.250 align:start position:0% show you this is a tested correct they tested<01:24:35.760> correct<01:24:36.060> is<01:24:36.239> basically<01:24:36.600> just<01:24:36.840> telling 01:24:37.250 --> 01:24:37.260 align:start position:0% tested correct is basically just telling 01:24:37.260 --> 01:24:39.649 align:start position:0% tested correct is basically just telling according<01:24:37.920> to<01:24:38.040> the<01:24:38.159> logic<01:24:38.460> of<01:24:38.580> the<01:24:38.760> of<01:24:39.120> on<01:24:39.420> the 01:24:39.649 --> 01:24:39.659 align:start position:0% according to the logic of the of on the 01:24:39.659 --> 01:24:42.050 align:start position:0% according to the logic of the of on the protocol<01:24:39.900> the<01:24:40.860> information<01:24:40.980> I<01:24:41.340> got<01:24:41.520> yes<01:24:41.760> made 01:24:42.050 --> 01:24:42.060 align:start position:0% protocol the information I got yes made 01:24:42.060 --> 01:24:43.790 align:start position:0% protocol the information I got yes made sense<01:24:42.360> or<01:24:42.659> no<01:24:42.780> and<01:24:43.020> it's<01:24:43.140> outputting<01:24:43.560> a<01:24:43.679> pool 01:24:43.790 --> 01:24:43.800 align:start position:0% sense or no and it's outputting a pool 01:24:43.800 --> 01:24:45.830 align:start position:0% sense or no and it's outputting a pool it's<01:24:44.280> just<01:24:44.460> saying<01:24:44.699> yes<01:24:44.880> or<01:24:45.060> no<01:24:45.239> and<01:24:45.719> it's 01:24:45.830 --> 01:24:45.840 align:start position:0% it's just saying yes or no and it's 01:24:45.840 --> 01:24:47.090 align:start position:0% it's just saying yes or no and it's doing<01:24:46.020> that<01:24:46.199> for<01:24:46.380> player<01:24:46.620> one<01:24:46.739> and<01:24:46.860> it's<01:24:46.980> doing 01:24:47.090 --> 01:24:47.100 align:start position:0% doing that for player one and it's doing 01:24:47.100 --> 01:24:49.010 align:start position:0% doing that for player one and it's doing it<01:24:47.280> for<01:24:47.340> player<01:24:47.640> two<01:24:47.760> and<01:24:48.540> these<01:24:48.840> then 01:24:49.010 --> 01:24:49.020 align:start position:0% it for player two and these then 01:24:49.020 --> 01:24:51.010 align:start position:0% it for player two and these then corrected<01:24:49.739> a<01:24:49.980> tests<01:24:50.219> that<01:24:50.340> are<01:24:50.460> basically 01:24:51.010 --> 01:24:51.020 align:start position:0% corrected a tests that are basically 01:24:51.020 --> 01:24:54.770 align:start position:0% corrected a tests that are basically input<01:24:52.040> into<01:24:53.060> this<01:24:54.060> function<01:24:54.360> pay<01:24:54.600> or 01:24:54.770 --> 01:24:54.780 align:start position:0% input into this function pay or 01:24:54.780 --> 01:24:56.330 align:start position:0% input into this function pay or validator<01:24:55.140> here<01:24:55.380> on<01:24:55.560> the<01:24:55.620> right<01:24:55.739> which<01:24:56.159> you 01:24:56.330 --> 01:24:56.340 align:start position:0% validator here on the right which you 01:24:56.340 --> 01:24:59.149 align:start position:0% validator here on the right which you can<01:24:56.460> also<01:24:56.640> see<01:24:56.760> here<01:24:57.000> it's<01:24:57.719> just<01:24:57.960> taking<01:24:58.260> was 01:24:59.149 --> 01:24:59.159 align:start position:0% can also see here it's just taking was 01:24:59.159 --> 01:25:01.010 align:start position:0% can also see here it's just taking was the<01:24:59.460> validator<01:24:59.760> correct<01:25:00.120> or<01:25:00.300> not<01:25:00.420> and<01:25:00.900> then 01:25:01.010 --> 01:25:01.020 align:start position:0% the validator correct or not and then 01:25:01.020 --> 01:25:03.590 align:start position:0% the validator correct or not and then it's<01:25:01.199> basically<01:25:01.500> updating 01:25:03.590 --> 01:25:03.600 align:start position:0% it's basically updating 01:25:03.600 --> 01:25:05.410 align:start position:0% it's basically updating good 01:25:05.410 --> 01:25:05.420 align:start position:0% good 01:25:05.420 --> 01:25:08.090 align:start position:0% good okay<01:25:06.420> also<01:25:06.900> what<01:25:07.020> you<01:25:07.140> should<01:25:07.320> see<01:25:07.440> and<01:25:07.980> this 01:25:08.090 --> 01:25:08.100 align:start position:0% okay also what you should see and this 01:25:08.100 --> 01:25:09.470 align:start position:0% okay also what you should see and this is<01:25:08.219> kind<01:25:08.340> of<01:25:08.460> coming<01:25:08.580> back<01:25:08.820> to<01:25:09.300> this 01:25:09.470 --> 01:25:09.480 align:start position:0% is kind of coming back to this 01:25:09.480 --> 01:25:10.910 align:start position:0% is kind of coming back to this discussion<01:25:09.840> on<01:25:10.080> why<01:25:10.500> is<01:25:10.620> there<01:25:10.739> no 01:25:10.910 --> 01:25:10.920 align:start position:0% discussion on why is there no 01:25:10.920 --> 01:25:13.610 align:start position:0% discussion on why is there no information<01:25:11.159> being<01:25:11.520> sent<01:25:11.760> back<01:25:11.940> this<01:25:12.600> is<01:25:12.719> also 01:25:13.610 --> 01:25:13.620 align:start position:0% information being sent back this is also 01:25:13.620 --> 01:25:15.050 align:start position:0% information being sent back this is also um there's<01:25:13.860> also<01:25:14.159> no<01:25:14.280> information<01:25:14.460> sent<01:25:14.880> in 01:25:15.050 --> 01:25:15.060 align:start position:0% um there's also no information sent in 01:25:15.060 --> 01:25:17.209 align:start position:0% um there's also no information sent in the<01:25:15.179> future<01:25:15.360> right<01:25:16.080> if<01:25:16.679> I<01:25:16.800> would<01:25:16.920> be<01:25:17.040> doing 01:25:17.209 --> 01:25:17.219 align:start position:0% the future right if I would be doing 01:25:17.219 --> 01:25:19.370 align:start position:0% the future right if I would be doing this<01:25:17.460> again<01:25:17.640> without<01:25:17.940> my<01:25:18.420> way<01:25:18.719> of<01:25:18.840> composing 01:25:19.370 --> 01:25:19.380 align:start position:0% this again without my way of composing 01:25:19.380 --> 01:25:21.290 align:start position:0% this again without my way of composing this<01:25:19.679> one<01:25:20.219> player<01:25:20.520> which<01:25:20.699> just<01:25:20.880> magically 01:25:21.290 --> 01:25:21.300 align:start position:0% this one player which just magically 01:25:21.300 --> 01:25:22.910 align:start position:0% this one player which just magically updates<01:25:21.659> I<01:25:22.020> would<01:25:22.140> have<01:25:22.320> to<01:25:22.380> explicitly 01:25:22.910 --> 01:25:22.920 align:start position:0% updates I would have to explicitly 01:25:22.920 --> 01:25:30.050 align:start position:0% updates I would have to explicitly feedback<01:25:23.219> that<01:25:23.460> information 01:25:30.050 --> 01:25:30.060 align:start position:0% 01:25:30.060 --> 01:25:32.450 align:start position:0% uh<01:25:30.600> so<01:25:30.780> here<01:25:31.080> you<01:25:31.260> have<01:25:31.500> uh<01:25:32.040> potentially 01:25:32.450 --> 01:25:32.460 align:start position:0% uh so here you have uh potentially 01:25:32.460 --> 01:25:35.330 align:start position:0% uh so here you have uh potentially Boolean<01:25:32.880> values<01:25:33.300> that<01:25:33.840> are<01:25:34.020> that<01:25:34.199> that 01:25:35.330 --> 01:25:35.340 align:start position:0% Boolean values that are that that 01:25:35.340 --> 01:25:37.250 align:start position:0% Boolean values that are that that um the<01:25:36.000> outputs<01:25:36.420> which<01:25:36.600> is<01:25:36.719> the<01:25:36.960> correct 01:25:37.250 --> 01:25:37.260 align:start position:0% um the outputs which is the correct 01:25:37.260 --> 01:25:39.950 align:start position:0% um the outputs which is the correct attested<01:25:37.739> one<01:25:37.860> and<01:25:38.040> two<01:25:38.159> uh<01:25:38.880> but<01:25:39.120> then<01:25:39.300> in<01:25:39.719> a 01:25:39.950 --> 01:25:39.960 align:start position:0% attested one and two uh but then in a 01:25:39.960 --> 01:25:42.410 align:start position:0% attested one and two uh but then in a different<01:25:40.140> block<01:25:40.440> you<01:25:40.920> had<01:25:41.159> an<01:25:42.000> input<01:25:42.300> and 01:25:42.410 --> 01:25:42.420 align:start position:0% different block you had an input and 01:25:42.420 --> 01:25:44.330 align:start position:0% different block you had an input and output<01:25:42.719> that<01:25:42.840> was<01:25:42.960> actually<01:25:43.140> called<01:25:43.500> boo<01:25:43.920> so 01:25:44.330 --> 01:25:44.340 align:start position:0% output that was actually called boo so 01:25:44.340 --> 01:25:46.850 align:start position:0% output that was actually called boo so I'm<01:25:44.460> a<01:25:44.580> little<01:25:44.640> confused<01:25:45.120> whether<01:25:45.500> uh<01:25:46.500> that's 01:25:46.850 --> 01:25:46.860 align:start position:0% I'm a little confused whether uh that's 01:25:46.860 --> 01:25:48.649 align:start position:0% I'm a little confused whether uh that's this<01:25:47.040> is<01:25:47.219> supposed<01:25:47.400> to<01:25:47.580> be<01:25:47.699> like<01:25:47.880> a<01:25:48.120> label<01:25:48.360> or<01:25:48.480> a 01:25:48.649 --> 01:25:48.659 align:start position:0% this is supposed to be like a label or a 01:25:48.659 --> 01:25:49.729 align:start position:0% this is supposed to be like a label or a type 01:25:49.729 --> 01:25:49.739 align:start position:0% type 01:25:49.739 --> 01:25:51.649 align:start position:0% type um<01:25:50.159> okay<01:25:50.640> this<01:25:50.880> is<01:25:51.000> basically<01:25:51.239> the<01:25:51.480> question 01:25:51.649 --> 01:25:51.659 align:start position:0% um okay this is basically the question 01:25:51.659 --> 01:25:54.050 align:start position:0% um okay this is basically the question of<01:25:52.080> the<01:25:52.380> scope<01:25:52.560> of<01:25:52.800> the<01:25:52.980> of<01:25:53.159> the<01:25:53.699> um<01:25:53.699> of<01:25:53.880> the 01:25:54.050 --> 01:25:54.060 align:start position:0% of the scope of the of the um of the 01:25:54.060 --> 01:25:55.669 align:start position:0% of the scope of the of the um of the environment<01:25:54.360> basically<01:25:54.780> so<01:25:55.199> the<01:25:55.440> reason<01:25:55.500> I 01:25:55.669 --> 01:25:55.679 align:start position:0% environment basically so the reason I 01:25:55.679 --> 01:25:57.950 align:start position:0% environment basically so the reason I call<01:25:55.860> this<01:25:55.980> rule<01:25:56.400> here<01:25:56.520> is<01:25:56.760> I'm<01:25:57.300> just<01:25:57.600> telling 01:25:57.950 --> 01:25:57.960 align:start position:0% call this rule here is I'm just telling 01:25:57.960 --> 01:25:59.810 align:start position:0% call this rule here is I'm just telling now<01:25:58.199> basically<01:25:58.679> me<01:25:58.860> for<01:25:59.040> the<01:25:59.219> reader<01:25:59.520> I<01:25:59.699> know 01:25:59.810 --> 01:25:59.820 align:start position:0% now basically me for the reader I know 01:25:59.820 --> 01:26:01.370 align:start position:0% now basically me for the reader I know this<01:26:00.000> is<01:26:00.120> a<01:26:00.239> pool<01:26:00.360> and<01:26:00.719> I<01:26:00.780> basically<01:26:01.139> know<01:26:01.260> what 01:26:01.370 --> 01:26:01.380 align:start position:0% this is a pool and I basically know what 01:26:01.380 --> 01:26:02.990 align:start position:0% this is a pool and I basically know what is<01:26:01.560> happening<01:26:01.800> why<01:26:02.280> am<01:26:02.460> I<01:26:02.520> doing<01:26:02.639> this<01:26:02.820> here 01:26:02.990 --> 01:26:03.000 align:start position:0% is happening why am I doing this here 01:26:03.000 --> 01:26:04.729 align:start position:0% is happening why am I doing this here differently<01:26:03.360> I'm<01:26:04.020> doing<01:26:04.199> the<01:26:04.380> correct<01:26:04.620> to 01:26:04.729 --> 01:26:04.739 align:start position:0% differently I'm doing the correct to 01:26:04.739 --> 01:26:05.870 align:start position:0% differently I'm doing the correct to test<01:26:04.920> it<01:26:05.100> because<01:26:05.280> I'm<01:26:05.520> giving<01:26:05.699> it 01:26:05.870 --> 01:26:05.880 align:start position:0% test it because I'm giving it 01:26:05.880 --> 01:26:07.189 align:start position:0% test it because I'm giving it information<01:26:06.060> that<01:26:06.360> I<01:26:06.480> can<01:26:06.600> easier<01:26:06.840> pass<01:26:07.020> it 01:26:07.189 --> 01:26:07.199 align:start position:0% information that I can easier pass it 01:26:07.199 --> 01:26:08.750 align:start position:0% information that I can easier pass it right<01:26:07.320> if<01:26:07.500> I<01:26:07.620> would<01:26:07.739> be<01:26:07.800> just<01:26:07.980> saying<01:26:08.100> Bull<01:26:08.340> in 01:26:08.750 --> 01:26:08.760 align:start position:0% right if I would be just saying Bull in 01:26:08.760 --> 01:26:10.070 align:start position:0% right if I would be just saying Bull in that<01:26:08.940> specific<01:26:09.120> context<01:26:09.480> I<01:26:09.719> might<01:26:09.840> know<01:26:10.020> what 01:26:10.070 --> 01:26:10.080 align:start position:0% that specific context I might know what 01:26:10.080 --> 01:26:11.450 align:start position:0% that specific context I might know what it<01:26:10.260> is<01:26:10.320> but<01:26:10.500> I<01:26:10.620> don't<01:26:10.739> know<01:26:10.860> where<01:26:10.980> the<01:26:11.100> bull<01:26:11.219> is 01:26:11.450 --> 01:26:11.460 align:start position:0% it is but I don't know where the bull is 01:26:11.460 --> 01:26:13.850 align:start position:0% it is but I don't know where the bull is coming<01:26:11.580> from<01:26:11.760> right<01:26:12.060> so<01:26:12.420> it's<01:26:12.540> it's<01:26:12.719> like<01:26:13.080> you 01:26:13.850 --> 01:26:13.860 align:start position:0% coming from right so it's it's like you 01:26:13.860 --> 01:26:15.770 align:start position:0% coming from right so it's it's like you might<01:26:13.980> disagree<01:26:14.400> with<01:26:14.580> my<01:26:15.179> um<01:26:15.300> basically<01:26:15.659> with 01:26:15.770 --> 01:26:15.780 align:start position:0% might disagree with my um basically with 01:26:15.780 --> 01:26:18.110 align:start position:0% might disagree with my um basically with my<01:26:15.960> nominator<01:26:16.380> or<01:26:16.739> with<01:26:16.860> the<01:26:16.980> way<01:26:17.100> I<01:26:17.280> I<01:26:17.520> label 01:26:18.110 --> 01:26:18.120 align:start position:0% my nominator or with the way I I label 01:26:18.120 --> 01:26:19.729 align:start position:0% my nominator or with the way I I label things<01:26:18.300> but<01:26:18.600> for<01:26:18.780> me<01:26:18.900> internally<01:26:19.260> it<01:26:19.440> was<01:26:19.560> just 01:26:19.729 --> 01:26:19.739 align:start position:0% things but for me internally it was just 01:26:19.739 --> 01:26:21.410 align:start position:0% things but for me internally it was just like<01:26:19.980> I<01:26:20.340> understand<01:26:20.520> what<01:26:20.880> it<01:26:21.000> actually<01:26:21.120> means 01:26:21.410 --> 01:26:21.420 align:start position:0% like I understand what it actually means 01:26:21.420 --> 01:26:23.810 align:start position:0% like I understand what it actually means and<01:26:21.780> that's<01:26:22.139> the<01:26:22.320> reason<01:26:22.440> basically<01:26:22.860> yeah<01:26:23.219> the 01:26:23.810 --> 01:26:23.820 align:start position:0% and that's the reason basically yeah the 01:26:23.820 --> 01:26:25.669 align:start position:0% and that's the reason basically yeah the thing<01:26:23.940> to<01:26:24.120> keep<01:26:24.239> in<01:26:24.360> mind<01:26:24.480> in<01:26:25.139> a<01:26:25.320> categorical 01:26:25.669 --> 01:26:25.679 align:start position:0% thing to keep in mind in a categorical 01:26:25.679 --> 01:26:26.990 align:start position:0% thing to keep in mind in a categorical framework<01:26:26.100> because<01:26:26.219> you<01:26:26.400> have<01:26:26.580> these<01:26:26.760> wires 01:26:26.990 --> 01:26:27.000 align:start position:0% framework because you have these wires 01:26:27.000 --> 01:26:29.450 align:start position:0% framework because you have these wires going<01:26:27.179> in<01:26:27.420> basically<01:26:28.139> bound<01:26:28.679> variables<01:26:29.159> come 01:26:29.450 --> 01:26:29.460 align:start position:0% going in basically bound variables come 01:26:29.460 --> 01:26:31.430 align:start position:0% going in basically bound variables come in 01:26:31.430 --> 01:26:31.440 align:start position:0% in 01:26:31.440 --> 01:26:32.810 align:start position:0% in um the<01:26:31.739> outgoing<01:26:32.100> wires<01:26:32.400> are<01:26:32.580> basically 01:26:32.810 --> 01:26:32.820 align:start position:0% um the outgoing wires are basically 01:26:32.820 --> 01:26:34.310 align:start position:0% um the outgoing wires are basically binding<01:26:33.239> new<01:26:33.360> variables<01:26:33.780> to<01:26:33.900> the<01:26:34.020> output 01:26:34.310 --> 01:26:34.320 align:start position:0% binding new variables to the output 01:26:34.320 --> 01:26:36.890 align:start position:0% binding new variables to the output right<01:26:34.800> so<01:26:35.040> in<01:26:35.219> case<01:26:35.400> of<01:26:35.699> the<01:26:36.360> correct<01:26:36.540> the<01:26:36.719> test 01:26:36.890 --> 01:26:36.900 align:start position:0% right so in case of the correct the test 01:26:36.900 --> 01:26:38.629 align:start position:0% right so in case of the correct the test that<01:26:37.139> I'm<01:26:37.260> binding<01:26:37.679> a<01:26:37.920> value<01:26:38.100> that<01:26:38.340> is<01:26:38.520> the 01:26:38.629 --> 01:26:38.639 align:start position:0% that I'm binding a value that is the 01:26:38.639 --> 01:26:40.610 align:start position:0% that I'm binding a value that is the outcome<01:26:38.880> of<01:26:39.120> that<01:26:39.360> operation<01:26:39.840> to<01:26:40.380> that 01:26:40.610 --> 01:26:40.620 align:start position:0% outcome of that operation to that 01:26:40.620 --> 01:26:42.110 align:start position:0% outcome of that operation to that specific 01:26:42.110 --> 01:26:42.120 align:start position:0% specific 01:26:42.120 --> 01:26:43.490 align:start position:0% specific um character<01:26:42.540> test<01:26:42.780> which<01:26:43.139> means<01:26:43.320> if<01:26:43.440> I'm 01:26:43.490 --> 01:26:43.500 align:start position:0% um character test which means if I'm 01:26:43.500 --> 01:26:47.090 align:start position:0% um character test which means if I'm reusing<01:26:43.980> it<01:26:44.100> it's<01:26:44.340> mounted 01:26:47.090 --> 01:26:47.100 align:start position:0% 01:26:47.100 --> 01:26:51.110 align:start position:0% okay<01:26:47.580> other<01:26:48.060> questions 01:26:51.110 --> 01:26:51.120 align:start position:0% 01:26:51.120 --> 01:26:53.390 align:start position:0% all<01:26:51.480> right<01:26:51.600> let's<01:26:52.139> continue<01:26:52.440> so<01:26:52.920> we<01:26:53.159> have<01:26:53.280> to 01:26:53.390 --> 01:26:53.400 align:start position:0% all right let's continue so we have to 01:26:53.400 --> 01:26:54.890 align:start position:0% all right let's continue so we have to validate<01:26:53.820> us 01:26:54.890 --> 01:26:54.900 align:start position:0% validate us 01:26:54.900 --> 01:26:56.750 align:start position:0% validate us payment 01:26:56.750 --> 01:26:56.760 align:start position:0% payment 01:26:56.760 --> 01:26:58.550 align:start position:0% payment and<01:26:57.000> now<01:26:57.179> we<01:26:57.300> have<01:26:57.420> everything<01:26:57.540> assembled<01:26:58.199> for 01:26:58.550 --> 01:26:58.560 align:start position:0% and now we have everything assembled for 01:26:58.560 --> 01:27:01.970 align:start position:0% and now we have everything assembled for a<01:26:58.739> one<01:26:58.920> period<01:26:59.280> game<01:26:59.580> one<01:26:59.940> episode<01:27:00.179> game 01:27:01.970 --> 01:27:01.980 align:start position:0% a one period game one episode game 01:27:01.980 --> 01:27:04.970 align:start position:0% a one period game one episode game okay<01:27:02.520> this<01:27:02.760> is<01:27:02.940> this<01:27:03.120> Beast<01:27:03.420> here<01:27:03.600> just<01:27:04.260> barely 01:27:04.970 --> 01:27:04.980 align:start position:0% okay this is this Beast here just barely 01:27:04.980 --> 01:27:07.070 align:start position:0% okay this is this Beast here just barely makes<01:27:05.159> it<01:27:05.340> on 01:27:07.070 --> 01:27:07.080 align:start position:0% makes it on 01:27:07.080 --> 01:27:08.629 align:start position:0% makes it on not<01:27:07.560> completely 01:27:08.629 --> 01:27:08.639 align:start position:0% not completely 01:27:08.639 --> 01:27:10.310 align:start position:0% not completely what<01:27:09.120> it<01:27:09.239> basically<01:27:09.480> tells<01:27:09.780> you<01:27:09.900> is<01:27:10.020> this<01:27:10.199> is 01:27:10.310 --> 01:27:10.320 align:start position:0% what it basically tells you is this is 01:27:10.320 --> 01:27:11.689 align:start position:0% what it basically tells you is this is one<01:27:10.500> episode<01:27:10.739> I'm<01:27:11.040> now<01:27:11.219> pulling<01:27:11.580> everything 01:27:11.689 --> 01:27:11.699 align:start position:0% one episode I'm now pulling everything 01:27:11.699 --> 01:27:12.590 align:start position:0% one episode I'm now pulling everything together<01:27:12.060> there<01:27:12.360> are<01:27:12.480> certain 01:27:12.590 --> 01:27:12.600 align:start position:0% together there are certain 01:27:12.600 --> 01:27:14.450 align:start position:0% together there are certain parametrizations<01:27:13.260> ignore<01:27:14.100> them<01:27:14.219> for<01:27:14.340> now 01:27:14.450 --> 01:27:14.460 align:start position:0% parametrizations ignore them for now 01:27:14.460 --> 01:27:16.370 align:start position:0% parametrizations ignore them for now they're<01:27:14.699> just<01:27:14.880> details<01:27:15.600> um<01:27:15.600> of<01:27:15.900> you<01:27:16.139> know<01:27:16.199> how 01:27:16.370 --> 01:27:16.380 align:start position:0% they're just details um of you know how 01:27:16.380 --> 01:27:17.750 align:start position:0% they're just details um of you know how do<01:27:16.560> I<01:27:16.739> call<01:27:16.860> the<01:27:16.980> players<01:27:17.159> what<01:27:17.280> is<01:27:17.400> the<01:27:17.520> reward 01:27:17.750 --> 01:27:17.760 align:start position:0% do I call the players what is the reward 01:27:17.760 --> 01:27:19.669 align:start position:0% do I call the players what is the reward and<01:27:17.820> what<01:27:18.000> is<01:27:18.060> the<01:27:18.179> fee<01:27:18.360> and<01:27:18.420> so<01:27:18.540> on 01:27:19.669 --> 01:27:19.679 align:start position:0% and what is the fee and so on 01:27:19.679 --> 01:27:20.870 align:start position:0% and what is the fee and so on you<01:27:20.040> should<01:27:20.100> really<01:27:20.219> think<01:27:20.520> about<01:27:20.639> it<01:27:20.760> again 01:27:20.870 --> 01:27:20.880 align:start position:0% you should really think about it again 01:27:20.880 --> 01:27:22.610 align:start position:0% you should really think about it again as<01:27:21.239> an<01:27:21.360> as<01:27:21.600> a<01:27:21.780> diagram<01:27:21.960> with<01:27:22.199> in-going<01:27:22.560> and 01:27:22.610 --> 01:27:22.620 align:start position:0% as an as a diagram with in-going and 01:27:22.620 --> 01:27:24.590 align:start position:0% as an as a diagram with in-going and outgoing<01:27:23.040> wires<01:27:23.400> so<01:27:23.639> the<01:27:23.820> in-going<01:27:24.179> wires<01:27:24.480> are 01:27:24.590 --> 01:27:24.600 align:start position:0% outgoing wires so the in-going wires are 01:27:24.600 --> 01:27:26.270 align:start position:0% outgoing wires so the in-going wires are basically<01:27:24.840> chain<01:27:25.080> old<01:27:25.320> head<01:27:25.560> of<01:27:25.739> chain<01:27:25.920> from 01:27:26.270 --> 01:27:26.280 align:start position:0% basically chain old head of chain from 01:27:26.280 --> 01:27:28.550 align:start position:0% basically chain old head of chain from the<01:27:26.400> period<01:27:27.060> -2 01:27:28.550 --> 01:27:28.560 align:start position:0% the period -2 01:27:28.560 --> 01:27:30.290 align:start position:0% the period -2 um<01:27:28.620> validators<01:27:29.219> map<01:27:29.460> this<01:27:29.699> is<01:27:29.820> just<01:27:29.940> basically 01:27:30.290 --> 01:27:30.300 align:start position:0% um validators map this is just basically 01:27:30.300 --> 01:27:31.910 align:start position:0% um validators map this is just basically summarizing<01:27:30.900> the<01:27:31.080> information<01:27:31.199> of<01:27:31.620> what<01:27:31.800> the 01:27:31.910 --> 01:27:31.920 align:start position:0% summarizing the information of what the 01:27:31.920 --> 01:27:33.530 align:start position:0% summarizing the information of what the validators<01:27:32.280> have<01:27:32.460> done<01:27:32.639> before 01:27:33.530 --> 01:27:33.540 align:start position:0% validators have done before 01:27:33.540 --> 01:27:34.850 align:start position:0% validators have done before and<01:27:33.960> in<01:27:34.080> principle<01:27:34.320> you<01:27:34.500> should<01:27:34.620> think<01:27:34.739> about 01:27:34.850 --> 01:27:34.860 align:start position:0% and in principle you should think about 01:27:34.860 --> 01:27:36.590 align:start position:0% and in principle you should think about this<01:27:35.040> I<01:27:35.280> keep<01:27:35.400> enough<01:27:35.639> information<01:27:35.940> so<01:27:36.420> that 01:27:36.590 --> 01:27:36.600 align:start position:0% this I keep enough information so that 01:27:36.600 --> 01:27:38.870 align:start position:0% this I keep enough information so that the<01:27:36.900> protocol<01:27:37.199> Works<01:27:37.620> in<01:27:38.100> a<01:27:38.280> simple<01:27:38.400> case<01:27:38.639> here 01:27:38.870 --> 01:27:38.880 align:start position:0% the protocol Works in a simple case here 01:27:38.880 --> 01:27:40.790 align:start position:0% the protocol Works in a simple case here just<01:27:39.120> one<01:27:39.360> episode<01:27:39.659> if<01:27:40.320> there<01:27:40.440> would<01:27:40.560> be<01:27:40.679> more 01:27:40.790 --> 01:27:40.800 align:start position:0% just one episode if there would be more 01:27:40.800 --> 01:27:42.229 align:start position:0% just one episode if there would be more episodes<01:27:41.040> this<01:27:41.580> would<01:27:41.699> be<01:27:41.820> it's<01:27:41.940> just<01:27:42.120> a 01:27:42.229 --> 01:27:42.239 align:start position:0% episodes this would be it's just a 01:27:42.239 --> 01:27:43.729 align:start position:0% episodes this would be it's just a record<01:27:42.360> type<01:27:42.600> basically<01:27:42.960> it<01:27:43.320> would<01:27:43.560> contain 01:27:43.729 --> 01:27:43.739 align:start position:0% record type basically it would contain 01:27:43.739 --> 01:27:45.649 align:start position:0% record type basically it would contain more<01:27:43.920> records 01:27:45.649 --> 01:27:45.659 align:start position:0% more records 01:27:45.659 --> 01:27:47.510 align:start position:0% more records okay 01:27:47.510 --> 01:27:47.520 align:start position:0% okay 01:27:47.520 --> 01:27:49.610 align:start position:0% okay um<01:27:47.580> what<01:27:47.940> we<01:27:48.060> then<01:27:48.239> have<01:27:48.480> basically<01:27:48.900> is<01:27:49.260> the 01:27:49.610 --> 01:27:49.620 align:start position:0% um what we then have basically is the 01:27:49.620 --> 01:27:51.410 align:start position:0% um what we then have basically is the proposal<01:27:50.159> moves<01:27:50.460> first<01:27:50.580> he<01:27:50.820> observes<01:27:51.239> the 01:27:51.410 --> 01:27:51.420 align:start position:0% proposal moves first he observes the 01:27:51.420 --> 01:27:52.310 align:start position:0% proposal moves first he observes the chain 01:27:52.310 --> 01:27:52.320 align:start position:0% chain 01:27:52.320 --> 01:27:55.430 align:start position:0% chain he<01:27:52.620> outputs<01:27:53.100> a<01:27:53.219> new<01:27:53.340> chain<01:27:53.580> keep<01:27:54.239> in<01:27:54.420> mind 01:27:55.430 --> 01:27:55.440 align:start position:0% he outputs a new chain keep in mind 01:27:55.440 --> 01:27:57.709 align:start position:0% he outputs a new chain keep in mind this<01:27:55.980> is<01:27:56.040> this<01:27:56.280> again 01:27:57.709 --> 01:27:57.719 align:start position:0% this is this again 01:27:57.719 --> 01:27:59.209 align:start position:0% this is this again so<01:27:58.080> he's<01:27:58.199> observing<01:27:58.620> the<01:27:58.739> chain<01:27:58.860> and<01:27:59.040> then 01:27:59.209 --> 01:27:59.219 align:start position:0% so he's observing the chain and then 01:27:59.219 --> 01:28:00.410 align:start position:0% so he's observing the chain and then internally<01:27:59.460> is<01:27:59.699> also<01:27:59.940> at<01:28:00.120> the<01:28:00.239> same<01:28:00.360> time 01:28:00.410 --> 01:28:00.420 align:start position:0% internally is also at the same time 01:28:00.420 --> 01:28:01.790 align:start position:0% internally is also at the same time creating<01:28:00.840> the<01:28:01.080> new<01:28:01.199> chain<01:28:01.320> this<01:28:01.560> is<01:28:01.679> a 01:28:01.790 --> 01:28:01.800 align:start position:0% creating the new chain this is a 01:28:01.800 --> 01:28:04.729 align:start position:0% creating the new chain this is a computation<01:28:02.159> taking<01:28:02.400> place<01:28:02.699> here 01:28:04.729 --> 01:28:04.739 align:start position:0% computation taking place here 01:28:04.739 --> 01:28:07.310 align:start position:0% computation taking place here okay<01:28:05.280> proposal<01:28:06.000> Moves<01:28:06.300> new<01:28:06.540> chain<01:28:06.780> is<01:28:07.020> created 01:28:07.310 --> 01:28:07.320 align:start position:0% okay proposal Moves new chain is created 01:28:07.320 --> 01:28:09.830 align:start position:0% okay proposal Moves new chain is created then<01:28:07.920> the<01:28:08.100> validators<01:28:08.520> move<01:28:08.760> as<01:28:08.940> a<01:28:09.120> group 01:28:09.830 --> 01:28:09.840 align:start position:0% then the validators move as a group 01:28:09.840 --> 01:28:11.570 align:start position:0% then the validators move as a group they<01:28:10.199> observe<01:28:10.620> the<01:28:10.679> new<01:28:10.860> chain<01:28:11.040> they<01:28:11.219> observed 01:28:11.570 --> 01:28:11.580 align:start position:0% they observe the new chain they observed 01:28:11.580 --> 01:28:13.729 align:start position:0% they observe the new chain they observed the<01:28:11.639> old<01:28:11.820> chain<01:28:12.000> there's<01:28:12.420> also<01:28:12.719> access<01:28:12.960> to<01:28:13.560> the 01:28:13.729 --> 01:28:13.739 align:start position:0% the old chain there's also access to the 01:28:13.739 --> 01:28:14.870 align:start position:0% the old chain there's also access to the old<01:28:13.860> information 01:28:14.870 --> 01:28:14.880 align:start position:0% old information 01:28:14.880 --> 01:28:17.510 align:start position:0% old information validator<01:28:15.480> smash<01:28:15.900> validators<01:28:16.800> hashmap<01:28:17.340> old 01:28:17.510 --> 01:28:17.520 align:start position:0% validator smash validators hashmap old 01:28:17.520 --> 01:28:19.669 align:start position:0% validator smash validators hashmap old and<01:28:18.239> then<01:28:18.480> they<01:28:18.719> make<01:28:18.900> a<01:28:19.020> decision<01:28:19.320> they 01:28:19.669 --> 01:28:19.679 align:start position:0% and then they make a decision they 01:28:19.679 --> 01:28:22.430 align:start position:0% and then they make a decision they create<01:28:20.120> new<01:28:21.120> this<01:28:21.600> is<01:28:21.780> basically<01:28:21.960> new<01:28:22.199> map 01:28:22.430 --> 01:28:22.440 align:start position:0% create new this is basically new map 01:28:22.440 --> 01:28:24.410 align:start position:0% create new this is basically new map containing<01:28:23.159> the<01:28:23.280> updated<01:28:23.580> information<01:28:23.820> how 01:28:24.410 --> 01:28:24.420 align:start position:0% containing the updated information how 01:28:24.420 --> 01:28:26.689 align:start position:0% containing the updated information how did<01:28:24.659> all<01:28:25.560> of<01:28:25.739> these<01:28:25.920> validators<01:28:26.400> actually 01:28:26.689 --> 01:28:26.699 align:start position:0% did all of these validators actually 01:28:26.699 --> 01:28:27.649 align:start position:0% did all of these validators actually behave 01:28:27.649 --> 01:28:27.659 align:start position:0% behave 01:28:27.659 --> 01:28:29.270 align:start position:0% behave and<01:28:28.080> they<01:28:28.199> also<01:28:28.440> have<01:28:28.560> the<01:28:28.739> chain<01:28:28.860> updated 01:28:29.270 --> 01:28:29.280 align:start position:0% and they also have the chain updated 01:28:29.280 --> 01:28:30.830 align:start position:0% and they also have the chain updated because<01:28:29.520> when<01:28:29.940> they<01:28:30.060> cast<01:28:30.239> their<01:28:30.420> votes 01:28:30.830 --> 01:28:30.840 align:start position:0% because when they cast their votes 01:28:30.840 --> 01:28:34.189 align:start position:0% because when they cast their votes remember<01:28:31.260> the<01:28:32.159> shape<01:28:32.400> of<01:28:32.639> the<01:28:32.940> of 01:28:34.189 --> 01:28:34.199 align:start position:0% remember the shape of the of 01:28:34.199 --> 01:28:37.430 align:start position:0% remember the shape of the of um<01:28:34.260> the<01:28:34.980> blocks<01:28:35.280> are<01:28:35.400> basically<01:28:35.639> an<01:28:35.820> ID<01:28:36.000> and<01:28:36.960> a 01:28:37.430 --> 01:28:37.440 align:start position:0% um the blocks are basically an ID and a 01:28:37.440 --> 01:28:40.129 align:start position:0% um the blocks are basically an ID and a voting<01:28:37.800> value 01:28:40.129 --> 01:28:40.139 align:start position:0% 01:28:40.139 --> 01:28:42.709 align:start position:0% all<01:28:40.679> right<01:28:40.920> the<01:28:41.760> thing<01:28:41.820> to<01:28:42.000> remember<01:28:42.300> and<01:28:42.600> I'm 01:28:42.709 --> 01:28:42.719 align:start position:0% all right the thing to remember and I'm 01:28:42.719 --> 01:28:43.910 align:start position:0% all right the thing to remember and I'm repeating<01:28:43.080> myself<01:28:43.199> I<01:28:43.560> know<01:28:43.679> but<01:28:43.800> it's 01:28:43.910 --> 01:28:43.920 align:start position:0% repeating myself I know but it's 01:28:43.920 --> 01:28:44.930 align:start position:0% repeating myself I know but it's important<01:28:44.219> to<01:28:44.340> understand<01:28:44.460> what<01:28:44.820> is 01:28:44.930 --> 01:28:44.940 align:start position:0% important to understand what is 01:28:44.940 --> 01:28:47.689 align:start position:0% important to understand what is happening<01:28:45.179> that<01:28:46.020> the<01:28:46.920> payments<01:28:47.460> basically 01:28:47.689 --> 01:28:47.699 align:start position:0% happening that the payments basically 01:28:47.699 --> 01:28:49.490 align:start position:0% happening that the payments basically that<01:28:47.940> happen<01:28:48.120> are<01:28:48.480> happening<01:28:48.840> not<01:28:49.080> for<01:28:49.320> the 01:28:49.490 --> 01:28:49.500 align:start position:0% that happen are happening not for the 01:28:49.500 --> 01:28:50.990 align:start position:0% that happen are happening not for the decisions<01:28:49.860> to<01:28:50.159> that<01:28:50.400> are<01:28:50.520> made<01:28:50.699> by<01:28:50.880> the 01:28:50.990 --> 01:28:51.000 align:start position:0% decisions to that are made by the 01:28:51.000 --> 01:28:53.330 align:start position:0% decisions to that are made by the players<01:28:51.239> in<01:28:51.420> that<01:28:51.540> episode<01:28:51.780> but<01:28:52.679> from<01:28:53.159> the 01:28:53.330 --> 01:28:53.340 align:start position:0% players in that episode but from the 01:28:53.340 --> 01:28:54.770 align:start position:0% players in that episode but from the episode<01:28:53.460> before<01:28:53.880> or<01:28:54.179> if<01:28:54.360> I<01:28:54.420> would<01:28:54.540> be<01:28:54.659> looking 01:28:54.770 --> 01:28:54.780 align:start position:0% episode before or if I would be looking 01:28:54.780 --> 01:28:57.110 align:start position:0% episode before or if I would be looking at<01:28:54.960> them<01:28:55.139> more<01:28:55.320> longer<01:28:55.679> Horizon<01:28:56.280> from<01:28:56.940> the 01:28:57.110 --> 01:28:57.120 align:start position:0% at them more longer Horizon from the 01:28:57.120 --> 01:28:59.209 align:start position:0% at them more longer Horizon from the episodes<01:28:57.300> before 01:28:59.209 --> 01:28:59.219 align:start position:0% episodes before 01:28:59.219 --> 01:29:01.430 align:start position:0% episodes before good<01:28:59.699> after<01:29:00.360> this<01:29:00.600> this<01:29:00.780> is<01:29:00.960> the<01:29:01.080> main<01:29:01.260> things 01:29:01.430 --> 01:29:01.440 align:start position:0% good after this this is the main things 01:29:01.440 --> 01:29:03.110 align:start position:0% good after this this is the main things the<01:29:01.679> decisions<01:29:02.040> are<01:29:02.219> made<01:29:02.400> by<01:29:02.580> the<01:29:02.699> proposal 01:29:03.110 --> 01:29:03.120 align:start position:0% the decisions are made by the proposal 01:29:03.120 --> 01:29:04.669 align:start position:0% the decisions are made by the proposal by<01:29:03.300> the<01:29:03.360> validators<01:29:03.840> now<01:29:04.199> I'm<01:29:04.380> basically 01:29:04.669 --> 01:29:04.679 align:start position:0% by the validators now I'm basically 01:29:04.679 --> 01:29:07.070 align:start position:0% by the validators now I'm basically during<01:29:04.920> bookkeeping 01:29:07.070 --> 01:29:07.080 align:start position:0% during bookkeeping 01:29:07.080 --> 01:29:10.669 align:start position:0% during bookkeeping um I'm<01:29:07.560> determining<01:29:08.040> the<01:29:08.159> head<01:29:08.280> of<01:29:08.460> the<01:29:08.580> chain 01:29:10.669 --> 01:29:10.679 align:start position:0% um I'm determining the head of the chain 01:29:10.679 --> 01:29:13.250 align:start position:0% um I'm determining the head of the chain I<01:29:11.460> do<01:29:11.699> the<01:29:11.820> validators<01:29:12.239> payment<01:29:12.540> this<01:29:12.960> is<01:29:13.139> from 01:29:13.250 --> 01:29:13.260 align:start position:0% I do the validators payment this is from 01:29:13.260 --> 01:29:14.870 align:start position:0% I do the validators payment this is from the<01:29:13.440> past 01:29:14.870 --> 01:29:14.880 align:start position:0% the past 01:29:14.880 --> 01:29:17.450 align:start position:0% the past I<01:29:15.480> also<01:29:15.719> check<01:29:15.960> I<01:29:16.679> didn't<01:29:16.800> explain<01:29:17.040> this<01:29:17.280> but 01:29:17.450 --> 01:29:17.460 align:start position:0% I also check I didn't explain this but 01:29:17.460 --> 01:29:18.830 align:start position:0% I also check I didn't explain this but this<01:29:17.639> is<01:29:17.760> basically<01:29:18.000> also<01:29:18.300> bookkeeping<01:29:18.659> I'll 01:29:18.830 --> 01:29:18.840 align:start position:0% this is basically also bookkeeping I'll 01:29:18.840 --> 01:29:20.570 align:start position:0% this is basically also bookkeeping I'll just<01:29:18.960> look<01:29:19.199> at<01:29:19.320> what<01:29:19.679> was<01:29:19.860> the<01:29:20.040> old<01:29:20.159> proposal 01:29:20.570 --> 01:29:20.580 align:start position:0% just look at what was the old proposal 01:29:20.580 --> 01:29:22.010 align:start position:0% just look at what was the old proposal actually<01:29:20.760> doing<01:29:20.940> did<01:29:21.179> he<01:29:21.659> actually<01:29:21.780> do 01:29:22.010 --> 01:29:22.020 align:start position:0% actually doing did he actually do 01:29:22.020 --> 01:29:22.970 align:start position:0% actually doing did he actually do something 01:29:22.970 --> 01:29:22.980 align:start position:0% something 01:29:22.980 --> 01:29:25.430 align:start position:0% something and<01:29:23.520> then<01:29:23.639> I'm<01:29:24.420> getting<01:29:24.659> that<01:29:24.840> as<01:29:24.960> an<01:29:25.080> input<01:29:25.320> to 01:29:25.430 --> 01:29:25.440 align:start position:0% and then I'm getting that as an input to 01:29:25.440 --> 01:29:27.169 align:start position:0% and then I'm getting that as an input to the<01:29:25.560> proposal<01:29:25.980> payment<01:29:26.159> again<01:29:26.760> for<01:29:27.060> the 01:29:27.169 --> 01:29:27.179 align:start position:0% the proposal payment again for the 01:29:27.179 --> 01:29:29.149 align:start position:0% the proposal payment again for the period<01:29:27.420> before 01:29:29.149 --> 01:29:29.159 align:start position:0% period before 01:29:29.159 --> 01:29:30.470 align:start position:0% period before now 01:29:30.470 --> 01:29:30.480 align:start position:0% now 01:29:30.480 --> 01:29:32.030 align:start position:0% now the<01:29:30.840> complicating<01:29:31.199> thing<01:29:31.440> here<01:29:31.620> is<01:29:31.739> that<01:29:31.920> I'm 01:29:32.030 --> 01:29:32.040 align:start position:0% the complicating thing here is that I'm 01:29:32.040 --> 01:29:34.370 align:start position:0% the complicating thing here is that I'm targeting<01:29:32.520> a<01:29:32.820> model<01:29:33.000> which<01:29:33.600> itself<01:29:33.900> has<01:29:34.199> a 01:29:34.370 --> 01:29:34.380 align:start position:0% targeting a model which itself has a 01:29:34.380 --> 01:29:36.350 align:start position:0% targeting a model which itself has a structure<01:29:34.679> that<01:29:34.920> if<01:29:35.639> you<01:29:35.760> just<01:29:35.880> look<01:29:36.060> at<01:29:36.239> the 01:29:36.350 --> 01:29:36.360 align:start position:0% structure that if you just look at the 01:29:36.360 --> 01:29:38.090 align:start position:0% structure that if you just look at the output<01:29:36.600> chain<01:29:36.900> new<01:29:37.199> updated<01:29:37.500> head<01:29:37.800> of<01:29:37.980> chain 01:29:38.090 --> 01:29:38.100 align:start position:0% output chain new updated head of chain 01:29:38.100 --> 01:29:40.490 align:start position:0% output chain new updated head of chain and<01:29:38.340> so<01:29:38.400> on<01:29:38.520> validators<01:29:39.000> hashmap<01:29:39.900> and<01:29:40.320> you 01:29:40.490 --> 01:29:40.500 align:start position:0% and so on validators hashmap and you 01:29:40.500 --> 01:29:41.510 align:start position:0% and so on validators hashmap and you look<01:29:40.620> above 01:29:41.510 --> 01:29:41.520 align:start position:0% look above 01:29:41.520 --> 01:29:43.250 align:start position:0% look above you<01:29:42.060> can<01:29:42.120> see<01:29:42.300> there's<01:29:42.480> a<01:29:42.719> pattern<01:29:42.960> basically 01:29:43.250 --> 01:29:43.260 align:start position:0% you can see there's a pattern basically 01:29:43.260 --> 01:29:45.350 align:start position:0% you can see there's a pattern basically the<01:29:43.500> input<01:29:43.739> types<01:29:44.040> here<01:29:44.219> chain<01:29:44.460> old<01:29:44.699> head<01:29:44.940> of<01:29:45.060> I 01:29:45.350 --> 01:29:45.360 align:start position:0% the input types here chain old head of I 01:29:45.360 --> 01:29:46.430 align:start position:0% the input types here chain old head of I mean<01:29:45.420> you<01:29:45.540> can't<01:29:45.659> see<01:29:45.780> that<01:29:45.960> but<01:29:46.080> I'm<01:29:46.199> telling 01:29:46.430 --> 01:29:46.440 align:start position:0% mean you can't see that but I'm telling 01:29:46.440 --> 01:29:47.030 align:start position:0% mean you can't see that but I'm telling you 01:29:47.030 --> 01:29:47.040 align:start position:0% you 01:29:47.040 --> 01:29:49.790 align:start position:0% you the<01:29:47.580> input<01:29:47.880> type<01:29:48.120> Jane<01:29:48.960> old<01:29:49.139> head<01:29:49.440> of<01:29:49.620> chain 01:29:49.790 --> 01:29:49.800 align:start position:0% the input type Jane old head of chain 01:29:49.800 --> 01:29:51.530 align:start position:0% the input type Jane old head of chain and<01:29:49.980> that<01:29:50.159> here<01:29:50.340> are<01:29:50.880> exactly<01:29:51.179> the<01:29:51.300> output 01:29:51.530 --> 01:29:51.540 align:start position:0% and that here are exactly the output 01:29:51.540 --> 01:29:52.669 align:start position:0% and that here are exactly the output types 01:29:52.669 --> 01:29:52.679 align:start position:0% types 01:29:52.679 --> 01:29:54.350 align:start position:0% types which<01:29:53.040> means<01:29:53.280> I<01:29:53.460> now<01:29:53.699> I<01:29:53.880> can<01:29:53.940> take<01:29:54.060> the<01:29:54.239> one 01:29:54.350 --> 01:29:54.360 align:start position:0% which means I now I can take the one 01:29:54.360 --> 01:29:56.090 align:start position:0% which means I now I can take the one episode<01:29:54.600> and<01:29:55.080> just<01:29:55.199> say<01:29:55.380> okay<01:29:55.560> maybe<01:29:55.800> I<01:29:55.980> want 01:29:56.090 --> 01:29:56.100 align:start position:0% episode and just say okay maybe I want 01:29:56.100 --> 01:29:57.470 align:start position:0% episode and just say okay maybe I want to<01:29:56.159> run<01:29:56.280> it<01:29:56.400> for<01:29:56.520> three<01:29:56.760> episodes<01:29:56.940> I'm<01:29:57.360> taking 01:29:57.470 --> 01:29:57.480 align:start position:0% to run it for three episodes I'm taking 01:29:57.480 --> 01:29:59.450 align:start position:0% to run it for three episodes I'm taking the<01:29:57.719> same<01:29:57.900> element<01:29:58.080> and<01:29:58.800> I'm<01:29:58.920> just<01:29:59.040> connecting 01:29:59.450 --> 01:29:59.460 align:start position:0% the same element and I'm just connecting 01:29:59.460 --> 01:30:00.290 align:start position:0% the same element and I'm just connecting them 01:30:00.290 --> 01:30:00.300 align:start position:0% them 01:30:00.300 --> 01:30:02.750 align:start position:0% them or<01:30:00.960> I'm<01:30:01.260> not<01:30:01.440> doing<01:30:01.560> that<01:30:01.739> here<01:30:01.980> if<01:30:02.400> I<01:30:02.520> want<01:30:02.639> to 01:30:02.750 --> 01:30:02.760 align:start position:0% or I'm not doing that here if I want to 01:30:02.760 --> 01:30:04.310 align:start position:0% or I'm not doing that here if I want to run<01:30:02.940> this<01:30:03.120> as<01:30:03.300> a<01:30:03.420> Markov<01:30:03.659> game<01:30:03.840> and<01:30:04.020> you<01:30:04.139> know<01:30:04.260> I 01:30:04.310 --> 01:30:04.320 align:start position:0% run this as a Markov game and you know I 01:30:04.320 --> 01:30:05.689 align:start position:0% run this as a Markov game and you know I want<01:30:04.440> to<01:30:04.500> approximate<01:30:04.920> it<01:30:05.040> like<01:30:05.219> I'm<01:30:05.520> running 01:30:05.689 --> 01:30:05.699 align:start position:0% want to approximate it like I'm running 01:30:05.699 --> 01:30:07.610 align:start position:0% want to approximate it like I'm running this<01:30:05.880> for<01:30:06.060> a<01:30:06.179> long<01:30:06.300> time<01:30:06.420> I<01:30:07.260> could<01:30:07.380> just 01:30:07.610 --> 01:30:07.620 align:start position:0% this for a long time I could just 01:30:07.620 --> 01:30:09.530 align:start position:0% this for a long time I could just basically<01:30:08.400> use<01:30:08.580> a<01:30:08.760> specific<01:30:09.000> operator<01:30:09.300> we 01:30:09.530 --> 01:30:09.540 align:start position:0% basically use a specific operator we 01:30:09.540 --> 01:30:11.270 align:start position:0% basically use a specific operator we developed<01:30:09.900> that<01:30:10.139> you<01:30:10.260> can<01:30:10.380> embed<01:30:10.860> the<01:30:11.040> stage 01:30:11.270 --> 01:30:11.280 align:start position:0% developed that you can embed the stage 01:30:11.280 --> 01:30:13.129 align:start position:0% developed that you can embed the stage game<01:30:11.460> and<01:30:11.639> then<01:30:11.760> I'm<01:30:11.880> repeating<01:30:12.239> it<01:30:12.360> yeah<01:30:12.719> so 01:30:13.129 --> 01:30:13.139 align:start position:0% game and then I'm repeating it yeah so 01:30:13.139 --> 01:30:14.990 align:start position:0% game and then I'm repeating it yeah so you're<01:30:13.739> starting<01:30:14.040> you're<01:30:14.340> initializing<01:30:14.880> the 01:30:14.990 --> 01:30:15.000 align:start position:0% you're starting you're initializing the 01:30:15.000 --> 01:30:17.870 align:start position:0% you're starting you're initializing the game<01:30:15.179> you<01:30:15.719> create<01:30:15.900> a<01:30:16.260> one-stage<01:30:16.679> output<01:30:17.219> that 01:30:17.870 --> 01:30:17.880 align:start position:0% game you create a one-stage output that 01:30:17.880 --> 01:30:19.729 align:start position:0% game you create a one-stage output that is<01:30:18.000> fed<01:30:18.239> back<01:30:18.420> into<01:30:18.600> the<01:30:18.840> next<01:30:18.960> period<01:30:19.260> And<01:30:19.560> so 01:30:19.729 --> 01:30:19.739 align:start position:0% is fed back into the next period And so 01:30:19.739 --> 01:30:21.169 align:start position:0% is fed back into the next period And so you<01:30:19.920> go<01:30:20.040> on 01:30:21.169 --> 01:30:21.179 align:start position:0% you go on 01:30:21.179 --> 01:30:22.189 align:start position:0% you go on thank<01:30:21.360> you 01:30:22.189 --> 01:30:22.199 align:start position:0% thank you 01:30:22.199 --> 01:30:24.470 align:start position:0% thank you okay<01:30:22.620> I'm<01:30:22.980> not<01:30:23.100> doing<01:30:23.280> that<01:30:23.460> here 01:30:24.470 --> 01:30:24.480 align:start position:0% okay I'm not doing that here 01:30:24.480 --> 01:30:25.910 align:start position:0% okay I'm not doing that here um I<01:30:24.960> want<01:30:25.020> to<01:30:25.139> jump 01:30:25.910 --> 01:30:25.920 align:start position:0% um I want to jump 01:30:25.920 --> 01:30:27.229 align:start position:0% um I want to jump for<01:30:26.400> the 01:30:27.229 --> 01:30:27.239 align:start position:0% for the 01:30:27.239 --> 01:30:29.149 align:start position:0% for the last<01:30:27.719> part<01:30:27.960> basically<01:30:28.320> a<01:30:28.500> bit<01:30:28.560> and<01:30:28.739> looking 01:30:29.149 --> 01:30:29.159 align:start position:0% last part basically a bit and looking 01:30:29.159 --> 01:30:31.189 align:start position:0% last part basically a bit and looking into<01:30:29.460> how<01:30:30.179> do<01:30:30.239> you<01:30:30.420> actually<01:30:30.540> analyze<01:30:31.020> these 01:30:31.189 --> 01:30:31.199 align:start position:0% into how do you actually analyze these 01:30:31.199 --> 01:30:31.970 align:start position:0% into how do you actually analyze these games 01:30:31.970 --> 01:30:31.980 align:start position:0% games 01:30:31.980 --> 01:30:33.890 align:start position:0% games I<01:30:32.580> mentioned<01:30:32.820> before<01:30:33.000> on<01:30:33.239> the<01:30:33.360> slide<01:30:33.540> what<01:30:33.780> I 01:30:33.890 --> 01:30:33.900 align:start position:0% I mentioned before on the slide what I 01:30:33.900 --> 01:30:35.870 align:start position:0% I mentioned before on the slide what I want<01:30:34.020> to<01:30:34.139> do<01:30:34.260> is<01:30:34.320> I<01:30:34.620> want<01:30:34.739> to 01:30:35.870 --> 01:30:35.880 align:start position:0% want to do is I want to 01:30:35.880 --> 01:30:37.310 align:start position:0% want to do is I want to um illustrate<01:30:36.540> a<01:30:36.719> bit<01:30:36.780> of<01:30:36.900> what<01:30:37.080> is<01:30:37.199> the 01:30:37.310 --> 01:30:37.320 align:start position:0% um illustrate a bit of what is the 01:30:37.320 --> 01:30:38.810 align:start position:0% um illustrate a bit of what is the zooming<01:30:37.620> actually<01:30:37.800> what<01:30:38.040> is<01:30:38.159> the<01:30:38.280> zooming<01:30:38.580> how 01:30:38.810 --> 01:30:38.820 align:start position:0% zooming actually what is the zooming how 01:30:38.820 --> 01:30:40.189 align:start position:0% zooming actually what is the zooming how does<01:30:38.940> the<01:30:39.060> zooming<01:30:39.360> work<01:30:39.540> and<01:30:39.960> you<01:30:40.080> can 01:30:40.189 --> 01:30:40.199 align:start position:0% does the zooming work and you can 01:30:40.199 --> 01:30:41.570 align:start position:0% does the zooming work and you can already<01:30:40.320> see<01:30:40.560> because<01:30:40.739> I'm<01:30:40.980> focusing<01:30:41.340> on<01:30:41.460> the 01:30:41.570 --> 01:30:41.580 align:start position:0% already see because I'm focusing on the 01:30:41.580 --> 01:30:43.550 align:start position:0% already see because I'm focusing on the one<01:30:41.699> episode<01:30:41.940> I'm<01:30:42.719> actually<01:30:42.900> ignoring<01:30:43.320> any 01:30:43.550 --> 01:30:43.560 align:start position:0% one episode I'm actually ignoring any 01:30:43.560 --> 01:30:46.010 align:start position:0% one episode I'm actually ignoring any kind<01:30:43.739> of<01:30:43.800> repetition<01:30:44.219> clearly<01:30:45.060> if<01:30:45.780> you<01:30:45.840> care 01:30:46.010 --> 01:30:46.020 align:start position:0% kind of repetition clearly if you care 01:30:46.020 --> 01:30:48.350 align:start position:0% kind of repetition clearly if you care about<01:30:46.199> the<01:30:46.560> overall<01:30:46.920> protocol<01:30:47.820> at<01:30:48.179> some<01:30:48.300> point 01:30:48.350 --> 01:30:48.360 align:start position:0% about the overall protocol at some point 01:30:48.360 --> 01:30:50.030 align:start position:0% about the overall protocol at some point you<01:30:48.540> have<01:30:48.659> to<01:30:48.780> think<01:30:48.900> about<01:30:49.080> the<01:30:49.260> Dynamics<01:30:49.679> and 01:30:50.030 --> 01:30:50.040 align:start position:0% you have to think about the Dynamics and 01:30:50.040 --> 01:30:52.310 align:start position:0% you have to think about the Dynamics and also<01:30:50.280> longer<01:30:50.639> time<01:30:50.760> period<01:30:51.120> periods<01:30:51.540> but<01:30:52.199> for 01:30:52.310 --> 01:30:52.320 align:start position:0% also longer time period periods but for 01:30:52.320 --> 01:30:53.870 align:start position:0% also longer time period periods but for some<01:30:52.440> questions<01:30:52.679> it<01:30:53.100> might<01:30:53.219> be<01:30:53.340> relevant<01:30:53.699> to 01:30:53.870 --> 01:30:53.880 align:start position:0% some questions it might be relevant to 01:30:53.880 --> 01:30:55.250 align:start position:0% some questions it might be relevant to see 01:30:55.250 --> 01:30:55.260 align:start position:0% see 01:30:55.260 --> 01:30:57.229 align:start position:0% see um<01:30:55.320> is<01:30:55.560> it<01:30:55.679> actually<01:30:55.800> working<01:30:56.040> locally 01:30:57.229 --> 01:30:57.239 align:start position:0% um is it actually working locally 01:30:57.239 --> 01:30:59.090 align:start position:0% um is it actually working locally to<01:30:57.600> give<01:30:57.719> you<01:30:57.840> an<01:30:57.900> example<01:30:58.199> suppose<01:30:58.679> you're 01:30:59.090 --> 01:30:59.100 align:start position:0% to give you an example suppose you're 01:30:59.100 --> 01:31:00.290 align:start position:0% to give you an example suppose you're interested<01:30:59.460> in<01:30:59.580> honest<01:30:59.820> Behavior<01:31:00.120> by 01:31:00.290 --> 01:31:00.300 align:start position:0% interested in honest Behavior by 01:31:00.300 --> 01:31:02.149 align:start position:0% interested in honest Behavior by proposal<01:31:00.719> as<01:31:00.840> well<01:31:00.960> as<01:31:01.080> validator 01:31:02.149 --> 01:31:02.159 align:start position:0% proposal as well as validator 01:31:02.159 --> 01:31:04.010 align:start position:0% proposal as well as validator and<01:31:02.580> I'm<01:31:02.699> giving<01:31:02.940> you<01:31:03.179> you<01:31:03.840> know<01:31:03.960> I'm 01:31:04.010 --> 01:31:04.020 align:start position:0% and I'm giving you you know I'm 01:31:04.020 --> 01:31:05.390 align:start position:0% and I'm giving you you know I'm initially<01:31:04.440> initializing<01:31:05.100> this<01:31:05.219> with 01:31:05.390 --> 01:31:05.400 align:start position:0% initially initializing this with 01:31:05.400 --> 01:31:07.729 align:start position:0% initially initializing this with specific<01:31:05.699> inputs<01:31:06.120> and<01:31:06.540> I'm<01:31:06.719> testing<01:31:07.080> in<01:31:07.560> that 01:31:07.729 --> 01:31:07.739 align:start position:0% specific inputs and I'm testing in that 01:31:07.739 --> 01:31:08.990 align:start position:0% specific inputs and I'm testing in that one<01:31:07.860> period<01:31:08.100> do<01:31:08.280> the<01:31:08.460> players<01:31:08.699> actually<01:31:08.880> have 01:31:08.990 --> 01:31:09.000 align:start position:0% one period do the players actually have 01:31:09.000 --> 01:31:11.510 align:start position:0% one period do the players actually have an<01:31:09.120> incentive<01:31:09.420> to<01:31:09.540> work<01:31:09.719> in<01:31:09.840> that<01:31:09.960> way 01:31:11.510 --> 01:31:11.520 align:start position:0% an incentive to work in that way 01:31:11.520 --> 01:31:13.490 align:start position:0% an incentive to work in that way and<01:31:11.880> if<01:31:12.000> not<01:31:12.239> if<01:31:12.719> you<01:31:12.840> find<01:31:12.960> out<01:31:13.139> basically 01:31:13.490 --> 01:31:13.500 align:start position:0% and if not if you find out basically 01:31:13.500 --> 01:31:15.110 align:start position:0% and if not if you find out basically just<01:31:13.800> by<01:31:13.920> zooming<01:31:14.219> in<01:31:14.340> on<01:31:14.460> that<01:31:14.580> context<01:31:14.880> it's 01:31:15.110 --> 01:31:15.120 align:start position:0% just by zooming in on that context it's 01:31:15.120 --> 01:31:16.910 align:start position:0% just by zooming in on that context it's not<01:31:15.300> well<01:31:15.480> the<01:31:15.659> info<01:31:15.960> can<01:31:16.080> you<01:31:16.199> just<01:31:16.560> can<01:31:16.739> put 01:31:16.910 --> 01:31:16.920 align:start position:0% not well the info can you just can put 01:31:16.920 --> 01:31:18.169 align:start position:0% not well the info can you just can put everything<01:31:17.100> else<01:31:17.280> aside<01:31:17.699> you<01:31:17.820> don't<01:31:17.940> have<01:31:18.060> to 01:31:18.169 --> 01:31:18.179 align:start position:0% everything else aside you don't have to 01:31:18.179 --> 01:31:19.850 align:start position:0% everything else aside you don't have to think<01:31:18.300> about<01:31:18.420> the<01:31:18.659> Dynamics<01:31:19.020> that's<01:31:19.560> enough 01:31:19.850 --> 01:31:19.860 align:start position:0% think about the Dynamics that's enough 01:31:19.860 --> 01:31:21.830 align:start position:0% think about the Dynamics that's enough similarly<01:31:20.760> if<01:31:20.940> you<01:31:21.060> care<01:31:21.239> about<01:31:21.360> let's<01:31:21.719> say 01:31:21.830 --> 01:31:21.840 align:start position:0% similarly if you care about let's say 01:31:21.840 --> 01:31:24.050 align:start position:0% similarly if you care about let's say vectors<01:31:22.260> of<01:31:22.380> attacks<01:31:22.800> very<01:31:23.460> often<01:31:23.760> it's 01:31:24.050 --> 01:31:24.060 align:start position:0% vectors of attacks very often it's 01:31:24.060 --> 01:31:26.209 align:start position:0% vectors of attacks very often it's enough<01:31:24.360> to<01:31:24.719> focus<01:31:24.960> on<01:31:25.199> specific<01:31:25.500> Parts<01:31:25.800> in 01:31:26.209 --> 01:31:26.219 align:start position:0% enough to focus on specific Parts in 01:31:26.219 --> 01:31:27.950 align:start position:0% enough to focus on specific Parts in order<01:31:26.340> to<01:31:26.520> evaluate<01:31:27.120> whether<01:31:27.360> the<01:31:27.600> attack<01:31:27.719> is 01:31:27.950 --> 01:31:27.960 align:start position:0% order to evaluate whether the attack is 01:31:27.960 --> 01:31:31.010 align:start position:0% order to evaluate whether the attack is actually<01:31:28.080> working<01:31:28.260> or<01:31:28.500> not 01:31:31.010 --> 01:31:31.020 align:start position:0% 01:31:31.020 --> 01:31:44.229 align:start position:0% question<01:31:31.880> no<01:31:32.880> yes 01:31:44.229 --> 01:31:44.239 align:start position:0% 01:31:44.239 --> 01:31:46.030 align:start position:0% maybe 01:31:46.030 --> 01:31:46.040 align:start position:0% maybe 01:31:46.040 --> 01:31:49.790 align:start position:0% maybe okay<01:31:47.040> I<01:31:47.580> said<01:31:48.120> um<01:31:48.120> in<01:31:48.480> the<01:31:48.600> context<01:31:48.900> of<01:31:49.260> like<01:31:49.560> uh 01:31:49.790 --> 01:31:49.800 align:start position:0% okay I said um in the context of like uh 01:31:49.800 --> 01:31:51.410 align:start position:0% okay I said um in the context of like uh you<01:31:50.040> know<01:31:50.100> modeling<01:31:50.520> like<01:31:50.699> the<01:31:50.940> domain<01:31:51.239> of 01:31:51.410 --> 01:31:51.420 align:start position:0% you know modeling like the domain of 01:31:51.420 --> 01:31:53.629 align:start position:0% you know modeling like the domain of like<01:31:51.600> a<01:31:51.780> game<01:31:52.020> and<01:31:52.739> you<01:31:52.860> know<01:31:52.980> like<01:31:53.159> a<01:31:53.340> software 01:31:53.629 --> 01:31:53.639 align:start position:0% like a game and you know like a software 01:31:53.639 --> 01:31:55.430 align:start position:0% like a game and you know like a software team<01:31:53.820> working<01:31:54.120> with<01:31:54.480> like<01:31:54.719> a<01:31:54.900> program<01:31:55.020> like 01:31:55.430 --> 01:31:55.440 align:start position:0% team working with like a program like 01:31:55.440 --> 01:31:57.350 align:start position:0% team working with like a program like this<01:31:55.679> you<01:31:56.340> know<01:31:56.400> if<01:31:56.580> they<01:31:56.699> have<01:31:56.820> to<01:31:56.940> Liaison 01:31:57.350 --> 01:31:57.360 align:start position:0% this you know if they have to Liaison 01:31:57.360 --> 01:31:59.090 align:start position:0% this you know if they have to Liaison with<01:31:57.659> like<01:31:57.840> the<01:31:57.960> product<01:31:58.139> team<01:31:58.380> which<01:31:58.920> will 01:31:59.090 --> 01:31:59.100 align:start position:0% with like the product team which will 01:31:59.100 --> 01:32:00.530 align:start position:0% with like the product team which will have<01:31:59.280> an<01:31:59.400> understanding<01:31:59.760> of<01:31:59.880> like<01:32:00.000> the<01:32:00.179> ux 01:32:00.530 --> 01:32:00.540 align:start position:0% have an understanding of like the ux 01:32:00.540 --> 01:32:02.570 align:start position:0% have an understanding of like the ux wouldn't<01:32:01.199> it<01:32:01.440> be<01:32:01.500> easier<01:32:01.800> for<01:32:02.040> them<01:32:02.159> if<01:32:02.400> they 01:32:02.570 --> 01:32:02.580 align:start position:0% wouldn't it be easier for them if they 01:32:02.580 --> 01:32:04.490 align:start position:0% wouldn't it be easier for them if they want<01:32:02.699> to<01:32:02.820> model<01:32:02.880> attack<01:32:03.120> vectors<01:32:03.719> to<01:32:04.260> just 01:32:04.490 --> 01:32:04.500 align:start position:0% want to model attack vectors to just 01:32:04.500 --> 01:32:06.229 align:start position:0% want to model attack vectors to just model<01:32:04.679> what<01:32:05.100> the<01:32:05.280> agents<01:32:05.760> could<01:32:05.880> do<01:32:06.000> and<01:32:06.120> then 01:32:06.229 --> 01:32:06.239 align:start position:0% model what the agents could do and then 01:32:06.239 --> 01:32:08.390 align:start position:0% model what the agents could do and then use<01:32:06.420> a<01:32:06.540> genetic<01:32:06.900> algorithm<01:32:07.320> for<01:32:07.500> example 01:32:08.390 --> 01:32:08.400 align:start position:0% use a genetic algorithm for example 01:32:08.400 --> 01:32:10.070 align:start position:0% use a genetic algorithm for example might<01:32:08.940> well<01:32:09.179> be<01:32:09.300> depends<01:32:09.600> on<01:32:09.659> the<01:32:09.780> context 01:32:10.070 --> 01:32:10.080 align:start position:0% might well be depends on the context 01:32:10.080 --> 01:32:11.870 align:start position:0% might well be depends on the context right<01:32:10.860> um<01:32:10.860> the<01:32:11.040> key<01:32:11.159> thing<01:32:11.280> is<01:32:11.400> here<01:32:11.580> you<01:32:11.699> can 01:32:11.870 --> 01:32:11.880 align:start position:0% right um the key thing is here you can 01:32:11.880 --> 01:32:13.430 align:start position:0% right um the key thing is here you can have<01:32:12.000> you<01:32:12.179> have<01:32:12.360> both<01:32:12.540> basically<01:32:12.960> The<01:32:13.139> Best<01:32:13.260> of 01:32:13.430 --> 01:32:13.440 align:start position:0% have you have both basically The Best of 01:32:13.440 --> 01:32:14.930 align:start position:0% have you have both basically The Best of Both<01:32:13.560> Worlds<01:32:13.920> you<01:32:14.100> can<01:32:14.159> just<01:32:14.340> look<01:32:14.520> at<01:32:14.639> the<01:32:14.760> one 01:32:14.930 --> 01:32:14.940 align:start position:0% Both Worlds you can just look at the one 01:32:14.940 --> 01:32:16.550 align:start position:0% Both Worlds you can just look at the one component<01:32:15.360> but<01:32:15.840> if<01:32:15.960> that<01:32:16.080> is<01:32:16.199> not<01:32:16.320> the<01:32:16.440> only 01:32:16.550 --> 01:32:16.560 align:start position:0% component but if that is not the only 01:32:16.560 --> 01:32:18.110 align:start position:0% component but if that is not the only query<01:32:16.800> you<01:32:16.980> want<01:32:17.100> to<01:32:17.219> do<01:32:17.340> but<01:32:17.699> you<01:32:17.820> also<01:32:18.000> want 01:32:18.110 --> 01:32:18.120 align:start position:0% query you want to do but you also want 01:32:18.120 --> 01:32:19.310 align:start position:0% query you want to do but you also want to<01:32:18.239> look<01:32:18.300> at<01:32:18.420> the<01:32:18.540> more<01:32:18.659> complicated<01:32:19.020> stuff 01:32:19.310 --> 01:32:19.320 align:start position:0% to look at the more complicated stuff 01:32:19.320 --> 01:32:21.709 align:start position:0% to look at the more complicated stuff you<01:32:19.739> have<01:32:19.920> it<01:32:20.040> as<01:32:20.400> well<01:32:20.580> right<01:32:20.880> so<01:32:21.300> nothing<01:32:21.480> I 01:32:21.709 --> 01:32:21.719 align:start position:0% you have it as well right so nothing I 01:32:21.719 --> 01:32:23.030 align:start position:0% you have it as well right so nothing I mean<01:32:21.840> in<01:32:22.020> principle<01:32:22.380> what<01:32:22.560> you<01:32:22.679> could<01:32:22.800> do<01:32:22.920> is 01:32:23.030 --> 01:32:23.040 align:start position:0% mean in principle what you could do is 01:32:23.040 --> 01:32:25.870 align:start position:0% mean in principle what you could do is actually<01:32:23.940> you<01:32:24.840> can<01:32:24.900> take<01:32:25.080> this<01:32:25.260> component 01:32:25.870 --> 01:32:25.880 align:start position:0% actually you can take this component 01:32:25.880 --> 01:32:28.310 align:start position:0% actually you can take this component interface<01:32:26.880> it<01:32:27.000> to<01:32:27.120> the<01:32:27.179> outside<01:32:27.300> world<01:32:27.600> runs<01:32:28.139> a 01:32:28.310 --> 01:32:28.320 align:start position:0% interface it to the outside world runs a 01:32:28.320 --> 01:32:29.930 align:start position:0% interface it to the outside world runs a learning<01:32:28.739> algorithm<01:32:29.100> on<01:32:29.280> top<01:32:29.400> and<01:32:29.580> that's<01:32:29.760> it 01:32:29.930 --> 01:32:29.940 align:start position:0% learning algorithm on top and that's it 01:32:29.940 --> 01:32:31.070 align:start position:0% learning algorithm on top and that's it and<01:32:30.060> it<01:32:30.179> would<01:32:30.239> be<01:32:30.420> exactly<01:32:30.659> the<01:32:30.780> same<01:32:30.960> thing 01:32:31.070 --> 01:32:31.080 align:start position:0% and it would be exactly the same thing 01:32:31.080 --> 01:32:32.810 align:start position:0% and it would be exactly the same thing but<01:32:31.679> it<01:32:31.800> will<01:32:31.920> be<01:32:32.040> part<01:32:32.219> of<01:32:32.400> the<01:32:32.520> overall 01:32:32.810 --> 01:32:32.820 align:start position:0% but it will be part of the overall 01:32:32.820 --> 01:32:34.430 align:start position:0% but it will be part of the overall consistent<01:32:33.300> framework<01:32:33.659> and<01:32:34.080> that's<01:32:34.199> an 01:32:34.430 --> 01:32:34.440 align:start position:0% consistent framework and that's an 01:32:34.440 --> 01:32:35.810 align:start position:0% consistent framework and that's an important<01:32:34.679> thing<01:32:34.860> if<01:32:35.219> you<01:32:35.340> care<01:32:35.460> about<01:32:35.580> the 01:32:35.810 --> 01:32:35.820 align:start position:0% important thing if you care about the 01:32:35.820 --> 01:32:37.370 align:start position:0% important thing if you care about the design<01:32:36.000> for<01:32:36.360> instance<01:32:36.600> you<01:32:37.020> want<01:32:37.139> to<01:32:37.260> make 01:32:37.370 --> 01:32:37.380 align:start position:0% design for instance you want to make 01:32:37.380 --> 01:32:38.689 align:start position:0% design for instance you want to make sure<01:32:37.500> that<01:32:37.679> everything<01:32:37.860> is<01:32:38.280> somehow 01:32:38.689 --> 01:32:38.699 align:start position:0% sure that everything is somehow 01:32:38.699 --> 01:32:40.729 align:start position:0% sure that everything is somehow consistent<01:32:39.179> obviously<01:32:39.600> right<01:32:39.900> and<01:32:40.440> then<01:32:40.560> it's 01:32:40.729 --> 01:32:40.739 align:start position:0% consistent obviously right and then it's 01:32:40.739 --> 01:32:42.470 align:start position:0% consistent obviously right and then it's much<01:32:40.920> easier<01:32:41.219> to<01:32:41.400> say<01:32:41.520> I'm<01:32:41.880> taking<01:32:42.060> an<01:32:42.300> element 01:32:42.470 --> 01:32:42.480 align:start position:0% much easier to say I'm taking an element 01:32:42.480 --> 01:32:44.450 align:start position:0% much easier to say I'm taking an element which<01:32:42.840> is<01:32:42.960> consistent<01:32:43.320> with<01:32:43.440> the<01:32:43.620> rest<01:32:43.800> and 01:32:44.450 --> 01:32:44.460 align:start position:0% which is consistent with the rest and 01:32:44.460 --> 01:32:45.770 align:start position:0% which is consistent with the rest and just<01:32:44.639> interface<01:32:45.060> it<01:32:45.179> to<01:32:45.300> the<01:32:45.360> outside<01:32:45.480> world 01:32:45.770 --> 01:32:45.780 align:start position:0% just interface it to the outside world 01:32:45.780 --> 01:32:47.090 align:start position:0% just interface it to the outside world and<01:32:45.960> then<01:32:46.080> simulate<01:32:46.440> it 01:32:47.090 --> 01:32:47.100 align:start position:0% and then simulate it 01:32:47.100 --> 01:32:48.950 align:start position:0% and then simulate it clearly<01:32:47.760> I<01:32:48.000> mean<01:32:48.120> you<01:32:48.420> know<01:32:48.480> this<01:32:48.719> is<01:32:48.840> also 01:32:48.950 --> 01:32:48.960 align:start position:0% clearly I mean you know this is also 01:32:48.960 --> 01:32:50.030 align:start position:0% clearly I mean you know this is also ethical<01:32:49.260> I'm<01:32:49.500> not<01:32:49.620> sure<01:32:49.679> how<01:32:49.860> many<01:32:49.920> people 01:32:50.030 --> 01:32:50.040 align:start position:0% ethical I'm not sure how many people 01:32:50.040 --> 01:32:51.290 align:start position:0% ethical I'm not sure how many people will<01:32:50.219> be<01:32:50.340> using<01:32:50.520> it<01:32:50.639> in<01:32:50.760> that<01:32:50.880> form<01:32:51.060> right 01:32:51.290 --> 01:32:51.300 align:start position:0% will be using it in that form right 01:32:51.300 --> 01:32:52.550 align:start position:0% will be using it in that form right that's<01:32:51.540> another<01:32:51.659> question<01:32:51.960> that<01:32:52.199> is<01:32:52.320> I<01:32:52.440> think 01:32:52.550 --> 01:32:52.560 align:start position:0% that's another question that is I think 01:32:52.560 --> 01:32:55.729 align:start position:0% that's another question that is I think lurking<01:32:52.920> in<01:32:53.040> the<01:32:53.159> yeah<01:32:53.400> in<01:32:53.699> the<01:32:53.820> back<01:32:54.080> so<01:32:55.080> there 01:32:55.729 --> 01:32:55.739 align:start position:0% lurking in the yeah in the back so there 01:32:55.739 --> 01:32:58.129 align:start position:0% lurking in the yeah in the back so there are<01:32:55.920> I<01:32:56.340> mean<01:32:56.520> this<01:32:56.699> is<01:32:56.820> at<01:32:57.060> the<01:32:57.239> moment 01:32:58.129 --> 01:32:58.139 align:start position:0% are I mean this is at the moment 01:32:58.139 --> 01:32:59.330 align:start position:0% are I mean this is at the moment actually<01:32:58.560> to<01:32:58.739> work<01:32:58.860> with<01:32:58.980> that<01:32:59.100> you<01:32:59.219> don't 01:32:59.330 --> 01:32:59.340 align:start position:0% actually to work with that you don't 01:32:59.340 --> 01:33:00.350 align:start position:0% actually to work with that you don't need<01:32:59.460> that<01:32:59.580> much<01:32:59.699> high<01:32:59.880> school<01:33:00.060> because<01:33:00.239> you 01:33:00.350 --> 01:33:00.360 align:start position:0% need that much high school because you 01:33:00.360 --> 01:33:01.550 align:start position:0% need that much high school because you need<01:33:00.480> to<01:33:00.600> understand<01:33:00.659> the<01:33:00.960> syntax<01:33:01.260> of<01:33:01.500> the 01:33:01.550 --> 01:33:01.560 align:start position:0% need to understand the syntax of the 01:33:01.560 --> 01:33:02.990 align:start position:0% need to understand the syntax of the engine<01:33:01.679> and<01:33:01.980> most<01:33:02.100> of<01:33:02.280> what<01:33:02.400> I<01:33:02.520> showed<01:33:02.760> you<01:33:02.820> is 01:33:02.990 --> 01:33:03.000 align:start position:0% engine and most of what I showed you is 01:33:03.000 --> 01:33:05.090 align:start position:0% engine and most of what I showed you is inside<01:33:03.179> clearly<01:33:04.139> you<01:33:04.320> need<01:33:04.440> some<01:33:04.800> kind<01:33:04.980> of 01:33:05.090 --> 01:33:05.100 align:start position:0% inside clearly you need some kind of 01:33:05.100 --> 01:33:06.709 align:start position:0% inside clearly you need some kind of knowledge<01:33:05.699> of<01:33:05.820> Haskell<01:33:06.179> to<01:33:06.300> work<01:33:06.480> with<01:33:06.600> the 01:33:06.709 --> 01:33:06.719 align:start position:0% knowledge of Haskell to work with the 01:33:06.719 --> 01:33:08.330 align:start position:0% knowledge of Haskell to work with the outside<01:33:06.840> world<01:33:07.139> but<01:33:07.560> if<01:33:07.679> that<01:33:07.800> also<01:33:08.040> goes<01:33:08.280> away 01:33:08.330 --> 01:33:08.340 align:start position:0% outside world but if that also goes away 01:33:08.340 --> 01:33:10.070 align:start position:0% outside world but if that also goes away it's<01:33:08.760> easy<01:33:09.000> to<01:33:09.120> think<01:33:09.360> of<01:33:09.540> this<01:33:09.659> as<01:33:09.780> basically 01:33:10.070 --> 01:33:10.080 align:start position:0% it's easy to think of this as basically 01:33:10.080 --> 01:33:11.629 align:start position:0% it's easy to think of this as basically working<01:33:10.320> as<01:33:10.560> you<01:33:10.920> have<01:33:11.040> a<01:33:11.159> domain<01:33:11.400> specific 01:33:11.629 --> 01:33:11.639 align:start position:0% working as you have a domain specific 01:33:11.639 --> 01:33:13.129 align:start position:0% working as you have a domain specific language<01:33:11.940> and<01:33:12.420> that's<01:33:12.600> all<01:33:12.780> you<01:33:12.900> need<01:33:12.960> to<01:33:13.080> know 01:33:13.129 --> 01:33:13.139 align:start position:0% language and that's all you need to know 01:33:13.139 --> 01:33:14.990 align:start position:0% language and that's all you need to know and<01:33:13.320> you<01:33:13.440> have<01:33:13.500> some<01:33:13.620> operators<01:33:13.980> on<01:33:14.219> top<01:33:14.340> then 01:33:14.990 --> 01:33:15.000 align:start position:0% and you have some operators on top then 01:33:15.000 --> 01:33:18.169 align:start position:0% and you have some operators on top then parts<01:33:15.600> of<01:33:15.780> the<01:33:15.900> pain<01:33:16.020> hopefully<01:33:16.320> go<01:33:16.560> away 01:33:18.169 --> 01:33:18.179 align:start position:0% parts of the pain hopefully go away 01:33:18.179 --> 01:33:23.870 align:start position:0% parts of the pain hopefully go away okay<01:33:19.040> other<01:33:20.040> questions 01:33:23.870 --> 01:33:23.880 align:start position:0% 01:33:23.880 --> 01:33:28.129 align:start position:0% all<01:33:24.300> right<01:33:24.480> if<01:33:25.260> not 01:33:28.129 --> 01:33:28.139 align:start position:0% 01:33:28.139 --> 01:33:30.729 align:start position:0% slide<01:33:28.679> one<01:33:28.800> shall<01:33:29.699> we<01:33:29.820> start<01:33:29.940> again 01:33:30.729 --> 01:33:30.739 align:start position:0% slide one shall we start again 01:33:30.739 --> 01:33:33.950 align:start position:0% slide one shall we start again maybe<01:33:31.739> maybe<01:33:31.800> afterwards 01:33:33.950 --> 01:33:33.960 align:start position:0% maybe maybe afterwards 01:33:33.960 --> 01:33:35.149 align:start position:0% maybe maybe afterwards okay 01:33:35.149 --> 01:33:35.159 align:start position:0% okay 01:33:35.159 --> 01:33:37.310 align:start position:0% okay um 01:33:37.310 --> 01:33:37.320 align:start position:0% 01:33:37.320 --> 01:33:41.570 align:start position:0% let's<01:33:37.800> jump<01:33:37.980> a<01:33:38.100> bit<01:33:38.280> into<01:33:38.400> the<01:33:39.060> um<01:33:39.060> analysis 01:33:41.570 --> 01:33:41.580 align:start position:0% let's jump a bit into the um analysis 01:33:41.580 --> 01:33:43.250 align:start position:0% let's jump a bit into the um analysis um 01:33:43.250 --> 01:33:43.260 align:start position:0% um 01:33:43.260 --> 01:33:45.890 align:start position:0% um okay<01:33:43.860> here's<01:33:44.699> a<01:33:44.760> bit<01:33:44.880> more<01:33:44.940> Haskell<01:33:45.300> pain<01:33:45.600> for 01:33:45.890 --> 01:33:45.900 align:start position:0% okay here's a bit more Haskell pain for 01:33:45.900 --> 01:33:46.790 align:start position:0% okay here's a bit more Haskell pain for you 01:33:46.790 --> 01:33:46.800 align:start position:0% you 01:33:46.800 --> 01:33:48.709 align:start position:0% you um<01:33:46.860> and<01:33:47.280> even<01:33:47.460> more<01:33:47.699> than<01:33:47.820> average 01:33:48.709 --> 01:33:48.719 align:start position:0% um and even more than average 01:33:48.719 --> 01:33:51.590 align:start position:0% um and even more than average namely<01:33:49.440> I'm<01:33:49.679> using<01:33:50.159> something<01:33:50.280> which<01:33:50.580> is 01:33:51.590 --> 01:33:51.600 align:start position:0% namely I'm using something which is 01:33:51.600 --> 01:33:54.229 align:start position:0% namely I'm using something which is um kind<01:33:52.320> of<01:33:52.440> what<01:33:52.679> is<01:33:52.800> called<01:33:52.920> arrows 01:33:54.229 --> 01:33:54.239 align:start position:0% um kind of what is called arrows 01:33:54.239 --> 01:33:56.750 align:start position:0% um kind of what is called arrows uh<01:33:54.960> if<01:33:55.080> you<01:33:55.320> don't<01:33:55.440> even<01:33:55.560> know<01:33:55.739> what<01:33:55.920> it<01:33:56.100> is<01:33:56.219> for 01:33:56.750 --> 01:33:56.760 align:start position:0% uh if you don't even know what it is for 01:33:56.760 --> 01:33:58.310 align:start position:0% uh if you don't even know what it is for now<01:33:56.880> you<01:33:57.060> just<01:33:57.179> think<01:33:57.420> about<01:33:57.540> this<01:33:57.840> as<01:33:58.080> I'm 01:33:58.310 --> 01:33:58.320 align:start position:0% now you just think about this as I'm 01:33:58.320 --> 01:34:00.350 align:start position:0% now you just think about this as I'm defining<01:33:58.739> a<01:33:58.800> strategy<01:33:59.159> for<01:33:59.460> proposal<01:34:00.060> as<01:34:00.239> well 01:34:00.350 --> 01:34:00.360 align:start position:0% defining a strategy for proposal as well 01:34:00.360 --> 01:34:02.330 align:start position:0% defining a strategy for proposal as well as<01:34:00.420> for<01:34:00.600> the<01:34:00.780> validator<01:34:01.139> what<01:34:02.040> is<01:34:02.219> this 01:34:02.330 --> 01:34:02.340 align:start position:0% as for the validator what is this 01:34:02.340 --> 01:34:03.649 align:start position:0% as for the validator what is this basically<01:34:02.820> doing<01:34:03.000> is<01:34:03.179> the<01:34:03.360> following<01:34:03.540> is 01:34:03.649 --> 01:34:03.659 align:start position:0% basically doing is the following is 01:34:03.659 --> 01:34:05.330 align:start position:0% basically doing is the following is creating<01:34:03.900> a<01:34:04.080> function<01:34:04.380> and<01:34:04.980> the<01:34:05.100> function 01:34:05.330 --> 01:34:05.340 align:start position:0% creating a function and the function 01:34:05.340 --> 01:34:07.910 align:start position:0% creating a function and the function tells<01:34:05.699> me<01:34:05.820> I'm<01:34:06.360> observing<01:34:06.780> a<01:34:06.960> chain<01:34:07.139> and<01:34:07.800> what 01:34:07.910 --> 01:34:07.920 align:start position:0% tells me I'm observing a chain and what 01:34:07.920 --> 01:34:09.229 align:start position:0% tells me I'm observing a chain and what you<01:34:08.040> want<01:34:08.159> me<01:34:08.280> to<01:34:08.400> do<01:34:08.520> is<01:34:08.639> I'm<01:34:08.880> basically 01:34:09.229 --> 01:34:09.239 align:start position:0% you want me to do is I'm basically 01:34:09.239 --> 01:34:10.430 align:start position:0% you want me to do is I'm basically sending<01:34:09.600> an<01:34:09.719> ID 01:34:10.430 --> 01:34:10.440 align:start position:0% sending an ID 01:34:10.440 --> 01:34:12.649 align:start position:0% sending an ID remember<01:34:10.920> the<01:34:11.460> proposal<01:34:11.940> observes<01:34:12.420> the<01:34:12.540> chain 01:34:12.649 --> 01:34:12.659 align:start position:0% remember the proposal observes the chain 01:34:12.659 --> 01:34:14.689 align:start position:0% remember the proposal observes the chain and<01:34:12.900> decides<01:34:13.199> on<01:34:13.320> which<01:34:13.560> which<01:34:13.920> element<01:34:14.400> to 01:34:14.689 --> 01:34:14.699 align:start position:0% and decides on which which element to 01:34:14.699 --> 01:34:16.729 align:start position:0% and decides on which which element to build<01:34:14.880> what<01:34:15.659> the<01:34:15.840> rest<01:34:15.960> is<01:34:16.139> basically<01:34:16.440> saying 01:34:16.729 --> 01:34:16.739 align:start position:0% build what the rest is basically saying 01:34:16.739 --> 01:34:18.950 align:start position:0% build what the rest is basically saying is<01:34:16.920> this<01:34:17.219> is<01:34:17.340> an<01:34:17.460> honest<01:34:17.760> strategy<01:34:18.300> it<01:34:18.780> does 01:34:18.950 --> 01:34:18.960 align:start position:0% is this is an honest strategy it does 01:34:18.960 --> 01:34:20.990 align:start position:0% is this is an honest strategy it does the<01:34:19.080> following<01:34:19.440> determine<01:34:20.280> head<01:34:20.460> this<01:34:20.760> is<01:34:20.880> a 01:34:20.990 --> 01:34:21.000 align:start position:0% the following determine head this is a 01:34:21.000 --> 01:34:22.430 align:start position:0% the following determine head this is a functionality<01:34:21.300> from<01:34:21.540> before 01:34:22.430 --> 01:34:22.440 align:start position:0% functionality from before 01:34:22.440 --> 01:34:24.229 align:start position:0% functionality from before so<01:34:22.860> I'm<01:34:23.040> looking<01:34:23.159> into<01:34:23.400> the<01:34:23.639> chain<01:34:23.820> I'm 01:34:24.229 --> 01:34:24.239 align:start position:0% so I'm looking into the chain I'm 01:34:24.239 --> 01:34:25.729 align:start position:0% so I'm looking into the chain I'm looking<01:34:24.420> at<01:34:24.600> what<01:34:24.780> is<01:34:24.900> the<01:34:25.020> what<01:34:25.380> is<01:34:25.440> the<01:34:25.560> what 01:34:25.729 --> 01:34:25.739 align:start position:0% looking at what is the what is the what 01:34:25.739 --> 01:34:26.930 align:start position:0% looking at what is the what is the what is<01:34:25.860> the<01:34:25.920> head<01:34:26.040> of<01:34:26.159> the<01:34:26.280> chain<01:34:26.400> according<01:34:26.820> to 01:34:26.930 --> 01:34:26.940 align:start position:0% is the head of the chain according to 01:34:26.940 --> 01:34:29.030 align:start position:0% is the head of the chain according to the<01:34:27.060> protocol<01:34:27.300> if<01:34:27.719> it<01:34:27.840> is<01:34:28.020> play<01:34:28.620> that<01:34:28.860> game 01:34:29.030 --> 01:34:29.040 align:start position:0% the protocol if it is play that game 01:34:29.040 --> 01:34:31.310 align:start position:0% the protocol if it is play that game play<01:34:29.280> that<01:34:29.520> strategy<01:34:30.000> if<01:34:30.600> not<01:34:30.719> if<01:34:31.080> there<01:34:31.199> are 01:34:31.310 --> 01:34:31.320 align:start position:0% play that strategy if not if there are 01:34:31.320 --> 01:34:33.470 align:start position:0% play that strategy if not if there are multiple<01:34:31.560> candidates<01:34:32.100> randomize<01:34:32.820> this<01:34:33.300> is 01:34:33.470 --> 01:34:33.480 align:start position:0% multiple candidates randomize this is 01:34:33.480 --> 01:34:34.970 align:start position:0% multiple candidates randomize this is happening<01:34:33.780> here<01:34:33.960> basically 01:34:34.970 --> 01:34:34.980 align:start position:0% happening here basically 01:34:34.980 --> 01:34:37.129 align:start position:0% happening here basically and<01:34:35.699> this<01:34:35.820> is<01:34:35.820> done<01:34:36.060> uniformly<01:34:36.540> and<01:34:37.020> the 01:34:37.129 --> 01:34:37.139 align:start position:0% and this is done uniformly and the 01:34:37.139 --> 01:34:38.810 align:start position:0% and this is done uniformly and the validator<01:34:37.440> does<01:34:37.679> exactly<01:34:38.040> the<01:34:38.219> same<01:34:38.400> it's 01:34:38.810 --> 01:34:38.820 align:start position:0% validator does exactly the same it's 01:34:38.820 --> 01:34:40.669 align:start position:0% validator does exactly the same it's basically<01:34:39.120> a<01:34:39.300> super<01:34:39.540> honest<01:34:39.840> as<01:34:40.020> well<01:34:40.199> he's 01:34:40.669 --> 01:34:40.679 align:start position:0% basically a super honest as well he's 01:34:40.679 --> 01:34:42.709 align:start position:0% basically a super honest as well he's just<01:34:40.920> looking<01:34:41.040> at 01:34:42.709 --> 01:34:42.719 align:start position:0% just looking at 01:34:42.719 --> 01:34:45.290 align:start position:0% just looking at um<01:34:42.900> what's<01:34:43.320> the<01:34:43.620> head<01:34:43.800> if<01:34:44.400> the<01:34:44.520> hat<01:34:44.760> is<01:34:44.940> a 01:34:45.290 --> 01:34:45.300 align:start position:0% um what's the head if the hat is a 01:34:45.300 --> 01:34:47.030 align:start position:0% um what's the head if the hat is a single<01:34:45.540> value<01:34:45.659> play<01:34:46.139> that<01:34:46.380> if<01:34:46.739> multiple 01:34:47.030 --> 01:34:47.040 align:start position:0% single value play that if multiple 01:34:47.040 --> 01:34:49.790 align:start position:0% single value play that if multiple values<01:34:47.400> randomized<01:34:47.940> among<01:34:48.239> them 01:34:49.790 --> 01:34:49.800 align:start position:0% values randomized among them 01:34:49.800 --> 01:34:51.950 align:start position:0% values randomized among them good<01:34:50.340> and<01:34:50.580> then<01:34:50.820> basically<01:34:51.239> we<01:34:51.540> kind<01:34:51.840> of 01:34:51.950 --> 01:34:51.960 align:start position:0% good and then basically we kind of 01:34:51.960 --> 01:34:53.390 align:start position:0% good and then basically we kind of encapsulate<01:34:52.560> everything<01:34:52.739> in<01:34:52.980> this<01:34:53.100> so 01:34:53.390 --> 01:34:53.400 align:start position:0% encapsulate everything in this so 01:34:53.400 --> 01:34:56.330 align:start position:0% encapsulate everything in this so reminder<01:34:54.300> this<01:34:54.840> is<01:34:55.020> basically 01:34:56.330 --> 01:34:56.340 align:start position:0% reminder this is basically 01:34:56.340 --> 01:34:57.110 align:start position:0% reminder this is basically um 01:34:57.110 --> 01:34:57.120 align:start position:0% um 01:34:57.120 --> 01:34:59.689 align:start position:0% um uh<01:34:57.780> referring<01:34:58.139> to<01:34:58.320> the<01:34:58.500> one<01:34:58.739> episode<01:34:58.980> game<01:34:59.340> I'm 01:34:59.689 --> 01:34:59.699 align:start position:0% uh referring to the one episode game I'm 01:34:59.699 --> 01:35:01.250 align:start position:0% uh referring to the one episode game I'm plugging<01:35:00.120> in<01:35:00.239> some<01:35:00.480> variables<01:35:00.960> or<01:35:01.080> some 01:35:01.250 --> 01:35:01.260 align:start position:0% plugging in some variables or some 01:35:01.260 --> 01:35:03.530 align:start position:0% plugging in some variables or some parameters<01:35:01.679> which<01:35:01.860> you<01:35:01.980> can<01:35:02.100> ignore<01:35:02.340> for<01:35:02.460> now 01:35:03.530 --> 01:35:03.540 align:start position:0% parameters which you can ignore for now 01:35:03.540 --> 01:35:05.390 align:start position:0% parameters which you can ignore for now and<01:35:04.080> then<01:35:04.260> what<01:35:04.739> is<01:35:04.860> the<01:35:04.980> thing<01:35:05.100> that<01:35:05.219> I'm 01:35:05.390 --> 01:35:05.400 align:start position:0% and then what is the thing that I'm 01:35:05.400 --> 01:35:06.229 align:start position:0% and then what is the thing that I'm doing 01:35:06.229 --> 01:35:06.239 align:start position:0% doing 01:35:06.239 --> 01:35:12.770 align:start position:0% doing let<01:35:06.840> me<01:35:06.960> actually<01:35:07.139> open<01:35:07.500> it<01:35:07.860> differently 01:35:12.770 --> 01:35:12.780 align:start position:0% 01:35:12.780 --> 01:35:19.129 align:start position:0% um<01:35:12.900> so<01:35:13.199> I'm<01:35:13.440> analyzing 01:35:19.129 --> 01:35:19.139 align:start position:0% 01:35:19.139 --> 01:35:21.110 align:start position:0% the<01:35:19.500> scenario<01:35:19.920> and<01:35:20.159> then<01:35:20.280> this<01:35:20.460> is<01:35:20.639> I<01:35:21.000> should 01:35:21.110 --> 01:35:21.120 align:start position:0% the scenario and then this is I should 01:35:21.120 --> 01:35:22.250 align:start position:0% the scenario and then this is I should have<01:35:21.239> said<01:35:21.360> this<01:35:21.540> this<01:35:21.659> is<01:35:21.780> the<01:35:21.840> interactive 01:35:22.250 --> 01:35:22.260 align:start position:0% have said this this is the interactive 01:35:22.260 --> 01:35:23.570 align:start position:0% have said this this is the interactive way<01:35:22.440> this<01:35:22.679> is<01:35:22.800> the<01:35:22.980> right<01:35:23.040> hand<01:35:23.159> side<01:35:23.280> is<01:35:23.460> an 01:35:23.570 --> 01:35:23.580 align:start position:0% way this is the right hand side is an 01:35:23.580 --> 01:35:24.770 align:start position:0% way this is the right hand side is an interactive<01:35:23.940> session<01:35:24.179> with<01:35:24.420> the<01:35:24.540> high<01:35:24.659> school 01:35:24.770 --> 01:35:24.780 align:start position:0% interactive session with the high school 01:35:24.780 --> 01:35:26.930 align:start position:0% interactive session with the high school compiler<01:35:25.320> I'm<01:35:25.920> querying<01:35:26.400> that<01:35:26.580> thing<01:35:26.760> and 01:35:26.930 --> 01:35:26.940 align:start position:0% compiler I'm querying that thing and 01:35:26.940 --> 01:35:28.270 align:start position:0% compiler I'm querying that thing and what<01:35:27.060> I'm<01:35:27.179> getting<01:35:27.300> out<01:35:27.540> basically<01:35:27.960> is 01:35:28.270 --> 01:35:28.280 align:start position:0% what I'm getting out basically is 01:35:28.280 --> 01:35:31.129 align:start position:0% what I'm getting out basically is simplistic<01:35:29.280> information<01:35:29.460> namely 01:35:31.129 --> 01:35:31.139 align:start position:0% simplistic information namely 01:35:31.139 --> 01:35:32.390 align:start position:0% simplistic information namely um<01:35:31.199> the<01:35:31.440> output<01:35:31.679> just<01:35:31.860> tells<01:35:32.100> me<01:35:32.219> everything 01:35:32.390 --> 01:35:32.400 align:start position:0% um the output just tells me everything 01:35:32.400 --> 01:35:35.090 align:start position:0% um the output just tells me everything is<01:35:32.699> fine 01:35:35.090 --> 01:35:35.100 align:start position:0% is fine 01:35:35.100 --> 01:35:37.070 align:start position:0% is fine um you<01:35:35.280> don't<01:35:35.460> have<01:35:35.580> to<01:35:35.699> worry<01:35:35.880> go<01:35:36.540> home<01:35:36.659> or<01:35:36.900> go 01:35:37.070 --> 01:35:37.080 align:start position:0% um you don't have to worry go home or go 01:35:37.080 --> 01:35:40.310 align:start position:0% um you don't have to worry go home or go to<01:35:37.139> the<01:35:37.320> pub<01:35:37.440> everything<01:35:38.159> is<01:35:38.400> working 01:35:40.310 --> 01:35:40.320 align:start position:0% to the pub everything is working 01:35:40.320 --> 01:35:42.229 align:start position:0% to the pub everything is working now<01:35:40.860> this<01:35:41.340> is<01:35:41.400> a<01:35:41.520> specific<01:35:41.760> thing<01:35:41.940> what<01:35:42.120> it 01:35:42.229 --> 01:35:42.239 align:start position:0% now this is a specific thing what it 01:35:42.239 --> 01:35:43.490 align:start position:0% now this is a specific thing what it actually<01:35:42.360> tells<01:35:42.600> you<01:35:42.659> and<01:35:42.840> in<01:35:43.020> fact<01:35:43.139> this<01:35:43.320> is 01:35:43.490 --> 01:35:43.500 align:start position:0% actually tells you and in fact this is 01:35:43.500 --> 01:35:45.770 align:start position:0% actually tells you and in fact this is the<01:35:43.860> protocol<01:35:44.159> is<01:35:44.520> inspired<01:35:44.940> by<01:35:45.060> you<01:35:45.480> know<01:35:45.600> by 01:35:45.770 --> 01:35:45.780 align:start position:0% the protocol is inspired by you know by 01:35:45.780 --> 01:35:47.209 align:start position:0% the protocol is inspired by you know by one<01:35:46.260> of<01:35:46.320> the<01:35:46.440> biggest 01:35:47.209 --> 01:35:47.219 align:start position:0% one of the biggest 01:35:47.219 --> 01:35:48.950 align:start position:0% one of the biggest um<01:35:47.280> by<01:35:47.460> ethereum<01:35:47.940> basically<01:35:48.239> you<01:35:48.719> can<01:35:48.840> see 01:35:48.950 --> 01:35:48.960 align:start position:0% um by ethereum basically you can see 01:35:48.960 --> 01:35:50.390 align:start position:0% um by ethereum basically you can see that<01:35:49.139> the<01:35:49.320> specific<01:35:49.560> assumption<01:35:49.980> is<01:35:50.159> working 01:35:50.390 --> 01:35:50.400 align:start position:0% that the specific assumption is working 01:35:50.400 --> 01:35:52.790 align:start position:0% that the specific assumption is working no<01:35:51.120> incent<01:35:51.540> no<01:35:51.719> agent<01:35:52.080> has<01:35:52.260> an<01:35:52.380> incentive<01:35:52.679> to 01:35:52.790 --> 01:35:52.800 align:start position:0% no incent no agent has an incentive to 01:35:52.800 --> 01:35:56.510 align:start position:0% no incent no agent has an incentive to deviate<01:35:53.580> okay<01:35:54.060> nice<01:35:54.600> and<01:35:55.380> nice<01:35:55.800> and<01:35:55.980> clean<01:35:56.159> so 01:35:56.510 --> 01:35:56.520 align:start position:0% deviate okay nice and nice and clean so 01:35:56.520 --> 01:35:58.370 align:start position:0% deviate okay nice and nice and clean so far<01:35:56.699> but<01:35:57.300> now<01:35:57.420> we<01:35:57.540> want<01:35:57.659> to<01:35:57.780> do<01:35:57.900> the<01:35:58.020> following 01:35:58.370 --> 01:35:58.380 align:start position:0% far but now we want to do the following 01:35:58.380 --> 01:36:00.709 align:start position:0% far but now we want to do the following now<01:35:59.100> we<01:35:59.219> want<01:35:59.340> to<01:35:59.400> come<01:35:59.580> back<01:35:59.760> to<01:36:00.060> this<01:36:00.540> picture 01:36:00.709 --> 01:36:00.719 align:start position:0% now we want to come back to this picture 01:36:00.719 --> 01:36:02.870 align:start position:0% now we want to come back to this picture here 01:36:02.870 --> 01:36:02.880 align:start position:0% here 01:36:02.880 --> 01:36:05.990 align:start position:0% here I<01:36:03.360> said<01:36:03.540> before<01:36:03.719> that<01:36:04.139> let's<01:36:04.739> suppose<01:36:05.219> in<01:36:05.880> the 01:36:05.990 --> 01:36:06.000 align:start position:0% I said before that let's suppose in the 01:36:06.000 --> 01:36:07.430 align:start position:0% I said before that let's suppose in the past<01:36:06.120> period<01:36:06.480> there's<01:36:06.780> a<01:36:07.020> guy<01:36:07.080> who's<01:36:07.260> actually 01:36:07.430 --> 01:36:07.440 align:start position:0% past period there's a guy who's actually 01:36:07.440 --> 01:36:10.189 align:start position:0% past period there's a guy who's actually not<01:36:07.620> so<01:36:07.800> nice<01:36:07.980> and<01:36:08.760> he's<01:36:08.880> deciding<01:36:09.360> not<01:36:09.600> to 01:36:10.189 --> 01:36:10.199 align:start position:0% not so nice and he's deciding not to 01:36:10.199 --> 01:36:13.070 align:start position:0% not so nice and he's deciding not to propose<01:36:10.500> he's<01:36:10.800> waiting<01:36:11.760> at<01:36:12.300> that<01:36:12.480> moment<01:36:12.780> at 01:36:13.070 --> 01:36:13.080 align:start position:0% propose he's waiting at that moment at 01:36:13.080 --> 01:36:15.470 align:start position:0% propose he's waiting at that moment at some<01:36:13.260> point<01:36:13.380> after<01:36:13.620> some<01:36:13.860> time<01:36:14.040> threshold<01:36:14.580> the 01:36:15.470 --> 01:36:15.480 align:start position:0% some point after some time threshold the 01:36:15.480 --> 01:36:17.390 align:start position:0% some point after some time threshold the next<01:36:15.600> proposal<01:36:16.139> which<01:36:16.440> is 01:36:17.390 --> 01:36:17.400 align:start position:0% next proposal which is 01:36:17.400 --> 01:36:19.129 align:start position:0% next proposal which is um the<01:36:17.699> lower<01:36:17.820> one<01:36:18.060> here<01:36:18.239> basically<01:36:18.659> observes 01:36:19.129 --> 01:36:19.139 align:start position:0% um the lower one here basically observes 01:36:19.139 --> 01:36:21.410 align:start position:0% um the lower one here basically observes the<01:36:19.320> chain<01:36:19.500> steps<01:36:20.219> in<01:36:20.340> he<01:36:20.880> wants<01:36:21.120> to<01:36:21.179> be<01:36:21.300> nice 01:36:21.410 --> 01:36:21.420 align:start position:0% the chain steps in he wants to be nice 01:36:21.420 --> 01:36:24.709 align:start position:0% the chain steps in he wants to be nice he's<01:36:21.659> honest<01:36:21.960> proposes<01:36:22.500> a<01:36:22.679> new<01:36:22.800> a<01:36:22.920> new<01:36:23.100> head 01:36:24.709 --> 01:36:24.719 align:start position:0% he's honest proposes a new a new head 01:36:24.719 --> 01:36:26.870 align:start position:0% he's honest proposes a new a new head um<01:36:24.780> and<01:36:25.679> at<01:36:25.800> that<01:36:25.920> moment<01:36:26.100> before<01:36:26.280> the<01:36:26.460> testers 01:36:26.870 --> 01:36:26.880 align:start position:0% um and at that moment before the testers 01:36:26.880 --> 01:36:29.209 align:start position:0% um and at that moment before the testers can<01:36:27.060> actually<01:36:27.179> be<01:36:27.360> active<01:36:27.719> the<01:36:28.560> old<01:36:28.739> proposal 01:36:29.209 --> 01:36:29.219 align:start position:0% can actually be active the old proposal 01:36:29.219 --> 01:36:31.910 align:start position:0% can actually be active the old proposal steps<01:36:29.580> in<01:36:29.820> and<01:36:30.300> just<01:36:30.540> basically<01:36:31.020> proposes<01:36:31.739> his 01:36:31.910 --> 01:36:31.920 align:start position:0% steps in and just basically proposes his 01:36:31.920 --> 01:36:34.370 align:start position:0% steps in and just basically proposes his own<01:36:32.159> his<01:36:32.520> own<01:36:32.639> head<01:36:32.820> of<01:36:33.000> the<01:36:33.120> chain 01:36:34.370 --> 01:36:34.380 align:start position:0% own his own head of the chain 01:36:34.380 --> 01:36:35.629 align:start position:0% own his own head of the chain okay<01:36:34.440> there<01:36:34.739> are<01:36:34.920> various<01:36:35.100> ways<01:36:35.400> of<01:36:35.520> doing 01:36:35.629 --> 01:36:35.639 align:start position:0% okay there are various ways of doing 01:36:35.639 --> 01:36:37.430 align:start position:0% okay there are various ways of doing this<01:36:35.820> I<01:36:36.060> could<01:36:36.179> just<01:36:36.360> model<01:36:36.600> explicitly<01:36:37.199> the 01:36:37.430 --> 01:36:37.440 align:start position:0% this I could just model explicitly the 01:36:37.440 --> 01:36:39.830 align:start position:0% this I could just model explicitly the attack<01:36:37.560> game<01:36:37.920> and<01:36:38.880> it<01:36:39.000> is<01:36:39.060> actually<01:36:39.300> Merit<01:36:39.600> to 01:36:39.830 --> 01:36:39.840 align:start position:0% attack game and it is actually Merit to 01:36:39.840 --> 01:36:41.570 align:start position:0% attack game and it is actually Merit to do<01:36:40.020> that<01:36:40.139> but<01:36:40.679> here's<01:36:40.980> an<01:36:41.100> alternative<01:36:41.400> way 01:36:41.570 --> 01:36:41.580 align:start position:0% do that but here's an alternative way 01:36:41.580 --> 01:36:43.790 align:start position:0% do that but here's an alternative way you<01:36:41.820> can<01:36:41.880> do<01:36:42.000> it<01:36:42.179> and<01:36:42.480> this<01:36:42.900> is<01:36:43.020> I'm<01:36:43.500> referring 01:36:43.790 --> 01:36:43.800 align:start position:0% you can do it and this is I'm referring 01:36:43.800 --> 01:36:45.530 align:start position:0% you can do it and this is I'm referring to<01:36:43.860> the<01:36:43.980> zooming<01:36:44.340> in<01:36:44.460> that<01:36:45.179> I<01:36:45.300> want<01:36:45.420> to 01:36:45.530 --> 01:36:45.540 align:start position:0% to the zooming in that I want to 01:36:45.540 --> 01:36:49.729 align:start position:0% to the zooming in that I want to illustrate 01:36:49.729 --> 01:36:49.739 align:start position:0% 01:36:49.739 --> 01:36:50.810 align:start position:0% foreign 01:36:50.810 --> 01:36:50.820 align:start position:0% foreign 01:36:50.820 --> 01:36:53.450 align:start position:0% foreign I've<01:36:51.300> created<01:36:51.600> another<01:36:51.840> version<01:36:52.080> here<01:36:52.920> which 01:36:53.450 --> 01:36:53.460 align:start position:0% I've created another version here which 01:36:53.460 --> 01:36:55.550 align:start position:0% I've created another version here which is<01:36:53.580> doing<01:36:53.820> this<01:36:54.179> one<01:36:54.360> episode<01:36:54.540> attack<01:36:54.960> which 01:36:55.550 --> 01:36:55.560 align:start position:0% is doing this one episode attack which 01:36:55.560 --> 01:36:58.129 align:start position:0% is doing this one episode attack which is<01:36:55.620> doing<01:36:55.800> a<01:36:56.040> simple<01:36:56.100> trick<01:36:56.520> namely<01:36:57.139> I'm 01:36:58.129 --> 01:36:58.139 align:start position:0% is doing a simple trick namely I'm 01:36:58.139 --> 01:36:59.330 align:start position:0% is doing a simple trick namely I'm introducing<01:36:58.560> an<01:36:58.739> additional<01:36:59.040> variable 01:36:59.330 --> 01:36:59.340 align:start position:0% introducing an additional variable 01:36:59.340 --> 01:37:00.830 align:start position:0% introducing an additional variable because<01:36:59.760> I'm<01:36:59.940> just<01:37:00.120> focused<01:37:00.420> on<01:37:00.540> this<01:37:00.659> one 01:37:00.830 --> 01:37:00.840 align:start position:0% because I'm just focused on this one 01:37:00.840 --> 01:37:02.990 align:start position:0% because I'm just focused on this one period<01:37:01.260> I<01:37:01.440> can<01:37:01.620> do<01:37:01.739> that<01:37:01.920> it's<01:37:02.219> easy<01:37:02.520> I<01:37:02.880> just 01:37:02.990 --> 01:37:03.000 align:start position:0% period I can do that it's easy I just 01:37:03.000 --> 01:37:05.990 align:start position:0% period I can do that it's easy I just add<01:37:03.239> which<01:37:03.540> is<01:37:03.719> a<01:37:03.840> chain<01:37:03.960> manipulated 01:37:05.990 --> 01:37:06.000 align:start position:0% add which is a chain manipulated 01:37:06.000 --> 01:37:07.729 align:start position:0% add which is a chain manipulated um<01:37:06.060> all<01:37:06.420> the<01:37:06.600> rest<01:37:06.659> is<01:37:06.840> the<01:37:07.080> same 01:37:07.729 --> 01:37:07.739 align:start position:0% um all the rest is the same 01:37:07.739 --> 01:37:09.830 align:start position:0% um all the rest is the same the<01:37:08.159> proposer<01:37:08.639> observes<01:37:09.060> the<01:37:09.179> old<01:37:09.300> change<01:37:09.540> so 01:37:09.830 --> 01:37:09.840 align:start position:0% the proposer observes the old change so 01:37:09.840 --> 01:37:11.570 align:start position:0% the proposer observes the old change so he's<01:37:10.020> basically<01:37:10.500> still<01:37:10.739> operating<01:37:11.100> under<01:37:11.340> the 01:37:11.570 --> 01:37:11.580 align:start position:0% he's basically still operating under the 01:37:11.580 --> 01:37:13.250 align:start position:0% he's basically still operating under the information<01:37:11.699> from<01:37:12.120> the<01:37:12.300> past 01:37:13.250 --> 01:37:13.260 align:start position:0% information from the past 01:37:13.260 --> 01:37:15.530 align:start position:0% information from the past and<01:37:14.159> then<01:37:14.280> what<01:37:14.460> happens<01:37:14.639> is<01:37:14.940> this<01:37:15.120> line<01:37:15.300> block 01:37:15.530 --> 01:37:15.540 align:start position:0% and then what happens is this line block 01:37:15.540 --> 01:37:17.209 align:start position:0% and then what happens is this line block is<01:37:15.780> added 01:37:17.209 --> 01:37:17.219 align:start position:0% is added 01:37:17.219 --> 01:37:21.050 align:start position:0% is added I'm<01:37:17.820> merging<01:37:18.380> the<01:37:19.380> two<01:37:20.040> proposed<01:37:20.580> heads<01:37:20.880> into 01:37:21.050 --> 01:37:21.060 align:start position:0% I'm merging the two proposed heads into 01:37:21.060 --> 01:37:23.390 align:start position:0% I'm merging the two proposed heads into one<01:37:21.360> chain<01:37:21.540> so<01:37:21.780> then<01:37:21.900> I<01:37:22.080> have<01:37:22.199> really<01:37:22.380> a<01:37:22.560> fork 01:37:23.390 --> 01:37:23.400 align:start position:0% one chain so then I have really a fork 01:37:23.400 --> 01:37:24.830 align:start position:0% one chain so then I have really a fork and<01:37:23.880> then<01:37:24.000> what<01:37:24.239> is<01:37:24.360> happening<01:37:24.659> the 01:37:24.830 --> 01:37:24.840 align:start position:0% and then what is happening the 01:37:24.840 --> 01:37:26.450 align:start position:0% and then what is happening the validators<01:37:25.440> are<01:37:25.620> observing<01:37:25.980> the<01:37:26.100> forked 01:37:26.450 --> 01:37:26.460 align:start position:0% validators are observing the forked 01:37:26.460 --> 01:37:27.770 align:start position:0% validators are observing the forked version<01:37:26.580> so<01:37:26.880> they<01:37:27.060> have<01:37:27.239> to<01:37:27.360> deal<01:37:27.480> with<01:37:27.600> the 01:37:27.770 --> 01:37:27.780 align:start position:0% version so they have to deal with the 01:37:27.780 --> 01:37:29.689 align:start position:0% version so they have to deal with the problem<01:37:27.900> basically<01:37:28.380> right 01:37:29.689 --> 01:37:29.699 align:start position:0% problem basically right 01:37:29.699 --> 01:37:32.570 align:start position:0% problem basically right now<01:37:30.179> is<01:37:31.020> this<01:37:31.139> the<01:37:31.320> only<01:37:31.440> way<01:37:31.620> to<01:37:31.739> do<01:37:31.860> it<01:37:31.980> no<01:37:32.219> you 01:37:32.570 --> 01:37:32.580 align:start position:0% now is this the only way to do it no you 01:37:32.580 --> 01:37:33.890 align:start position:0% now is this the only way to do it no you have<01:37:32.699> multiple<01:37:33.000> ways<01:37:33.300> of<01:37:33.360> doing<01:37:33.540> it<01:37:33.659> but<01:37:33.780> this 01:37:33.890 --> 01:37:33.900 align:start position:0% have multiple ways of doing it but this 01:37:33.900 --> 01:37:35.510 align:start position:0% have multiple ways of doing it but this is<01:37:34.080> you<01:37:34.199> know<01:37:34.320> this<01:37:34.560> is<01:37:34.679> part<01:37:34.980> of<01:37:35.100> the<01:37:35.219> what<01:37:35.340> the 01:37:35.510 --> 01:37:35.520 align:start position:0% is you know this is part of the what the 01:37:35.520 --> 01:37:37.189 align:start position:0% is you know this is part of the what the model<01:37:35.639> has<01:37:35.940> to<01:37:36.060> decide<01:37:36.300> how<01:37:36.600> can<01:37:36.780> this<01:37:36.960> be<01:37:37.080> done 01:37:37.189 --> 01:37:37.199 align:start position:0% model has to decide how can this be done 01:37:37.199 --> 01:37:39.470 align:start position:0% model has to decide how can this be done in<01:37:37.320> an<01:37:37.440> easy<01:37:37.560> and<01:37:37.860> accessible<01:37:38.639> way<01:37:38.880> another 01:37:39.470 --> 01:37:39.480 align:start position:0% in an easy and accessible way another 01:37:39.480 --> 01:37:41.689 align:start position:0% in an easy and accessible way another way<01:37:39.780> to<01:37:39.960> another<01:37:40.199> way<01:37:40.500> to<01:37:40.620> do<01:37:40.739> this<01:37:40.860> and<01:37:41.219> on<01:37:41.520> one 01:37:41.689 --> 01:37:41.699 align:start position:0% way to another way to do this and on one 01:37:41.699 --> 01:37:43.310 align:start position:0% way to another way to do this and on one branch<01:37:41.940> we<01:37:42.179> actually<01:37:42.300> do<01:37:42.480> this<01:37:42.600> is<01:37:42.780> explicitly 01:37:43.310 --> 01:37:43.320 align:start position:0% branch we actually do this is explicitly 01:37:43.320 --> 01:37:45.050 align:start position:0% branch we actually do this is explicitly keeping<01:37:43.679> time<01:37:43.800> of<01:37:44.040> the<01:37:44.460> um<01:37:44.460> keeping<01:37:44.760> track<01:37:44.880> of 01:37:45.050 --> 01:37:45.060 align:start position:0% keeping time of the um keeping track of 01:37:45.060 --> 01:37:46.850 align:start position:0% keeping time of the um keeping track of time<01:37:45.300> and<01:37:45.900> basically<01:37:46.199> look<01:37:46.320> at<01:37:46.440> the<01:37:46.560> timing 01:37:46.850 --> 01:37:46.860 align:start position:0% time and basically look at the timing 01:37:46.860 --> 01:37:49.129 align:start position:0% time and basically look at the timing game<01:37:47.040> right<01:37:47.280> so<01:37:47.520> that<01:37:47.760> time<01:37:48.120> passes<01:37:48.540> and<01:37:49.080> then 01:37:49.129 --> 01:37:49.139 align:start position:0% game right so that time passes and then 01:37:49.139 --> 01:37:50.570 align:start position:0% game right so that time passes and then the<01:37:49.260> proposal<01:37:49.679> from<01:37:49.860> the<01:37:49.980> first<01:37:50.100> period<01:37:50.400> can 01:37:50.570 --> 01:37:50.580 align:start position:0% the proposal from the first period can 01:37:50.580 --> 01:37:53.270 align:start position:0% the proposal from the first period can until<01:37:50.940> a<01:37:51.300> certain<01:37:51.360> point<01:37:51.600> act<01:37:52.080> the<01:37:52.860> problem<01:37:53.040> is 01:37:53.270 --> 01:37:53.280 align:start position:0% until a certain point act the problem is 01:37:53.280 --> 01:37:55.310 align:start position:0% until a certain point act the problem is that<01:37:53.520> until<01:37:53.760> a<01:37:54.120> certain<01:37:54.179> threshold<01:37:54.659> the<01:37:55.080> all 01:37:55.310 --> 01:37:55.320 align:start position:0% that until a certain threshold the all 01:37:55.320 --> 01:37:56.510 align:start position:0% that until a certain threshold the all the<01:37:55.440> other<01:37:55.500> players<01:37:55.800> don't<01:37:55.920> know<01:37:56.100> whether<01:37:56.280> the 01:37:56.510 --> 01:37:56.520 align:start position:0% the other players don't know whether the 01:37:56.520 --> 01:37:57.709 align:start position:0% the other players don't know whether the other<01:37:56.580> guy<01:37:56.760> moved<01:37:57.060> or<01:37:57.239> just<01:37:57.420> they<01:37:57.600> haven't 01:37:57.709 --> 01:37:57.719 align:start position:0% other guy moved or just they haven't 01:37:57.719 --> 01:37:59.510 align:start position:0% other guy moved or just they haven't received<01:37:58.080> a<01:37:58.199> signal<01:37:58.440> yet<01:37:58.620> but<01:37:59.100> this<01:37:59.219> is<01:37:59.340> much 01:37:59.510 --> 01:37:59.520 align:start position:0% received a signal yet but this is much 01:37:59.520 --> 01:38:01.729 align:start position:0% received a signal yet but this is much more<01:37:59.639> involved<01:38:00.060> here<01:38:00.659> I'm<01:38:01.139> just<01:38:01.320> cutting<01:38:01.620> into 01:38:01.729 --> 01:38:01.739 align:start position:0% more involved here I'm just cutting into 01:38:01.739 --> 01:38:03.169 align:start position:0% more involved here I'm just cutting into this<01:38:01.980> thing<01:38:02.100> and<01:38:02.280> I'm<01:38:02.400> just<01:38:02.580> focusing<01:38:02.940> on<01:38:03.060> that 01:38:03.169 --> 01:38:03.179 align:start position:0% this thing and I'm just focusing on that 01:38:03.179 --> 01:38:05.689 align:start position:0% this thing and I'm just focusing on that one<01:38:03.360> aspect<01:38:03.659> that<01:38:03.840> I<01:38:03.960> care<01:38:04.080> about<01:38:04.260> namely<01:38:05.159> what 01:38:05.689 --> 01:38:05.699 align:start position:0% one aspect that I care about namely what 01:38:05.699 --> 01:38:07.550 align:start position:0% one aspect that I care about namely what do<01:38:05.880> the<01:38:06.000> validators<01:38:06.420> actually<01:38:06.659> do 01:38:07.550 --> 01:38:07.560 align:start position:0% do the validators actually do 01:38:07.560 --> 01:38:09.050 align:start position:0% do the validators actually do foreign 01:38:09.050 --> 01:38:09.060 align:start position:0% foreign 01:38:09.060 --> 01:38:13.850 align:start position:0% foreign okay<01:38:09.719> let's<01:38:09.960> jump<01:38:10.199> to<01:38:10.440> this 01:38:13.850 --> 01:38:13.860 align:start position:0% 01:38:13.860 --> 01:38:14.870 align:start position:0% um 01:38:14.870 --> 01:38:14.880 align:start position:0% um 01:38:14.880 --> 01:38:20.810 align:start position:0% um attack 01:38:20.810 --> 01:38:20.820 align:start position:0% 01:38:20.820 --> 01:38:23.030 align:start position:0% okay<01:38:21.780> um<01:38:21.780> strategy<01:38:22.199> proposal<01:38:22.620> is<01:38:22.800> the<01:38:22.920> same 01:38:23.030 --> 01:38:23.040 align:start position:0% okay um strategy proposal is the same 01:38:23.040 --> 01:38:24.229 align:start position:0% okay um strategy proposal is the same then<01:38:23.219> we<01:38:23.340> have<01:38:23.400> what<01:38:23.580> I<01:38:23.699> call<01:38:23.820> the<01:38:23.940> strategy 01:38:24.229 --> 01:38:24.239 align:start position:0% then we have what I call the strategy 01:38:24.239 --> 01:38:25.910 align:start position:0% then we have what I call the strategy validator<01:38:24.600> random<01:38:24.960> it's<01:38:25.199> also<01:38:25.500> the<01:38:25.620> same<01:38:25.739> from 01:38:25.910 --> 01:38:25.920 align:start position:0% validator random it's also the same from 01:38:25.920 --> 01:38:28.610 align:start position:0% validator random it's also the same from before<01:38:26.100> I<01:38:27.000> add<01:38:27.239> two<01:38:27.780> new<01:38:28.020> strategies<01:38:28.440> for 01:38:28.610 --> 01:38:28.620 align:start position:0% before I add two new strategies for 01:38:28.620 --> 01:38:30.229 align:start position:0% before I add two new strategies for validators<01:38:29.100> one<01:38:29.400> is<01:38:29.580> strategy<01:38:29.880> validator 01:38:30.229 --> 01:38:30.239 align:start position:0% validators one is strategy validator 01:38:30.239 --> 01:38:33.470 align:start position:0% validators one is strategy validator four<01:38:30.540> and<01:38:31.520> validator<01:38:32.520> five<01:38:32.880> this<01:38:33.420> is 01:38:33.470 --> 01:38:33.480 align:start position:0% four and validator five this is 01:38:33.480 --> 01:38:35.209 align:start position:0% four and validator five this is something<01:38:33.840> very 01:38:35.209 --> 01:38:35.219 align:start position:0% something very 01:38:35.219 --> 01:38:37.370 align:start position:0% something very um<01:38:35.280> very<01:38:35.580> simple<01:38:35.699> namely<01:38:36.060> in<01:38:36.360> case<01:38:36.480> of<01:38:36.900> a<01:38:37.139> tie 01:38:37.370 --> 01:38:37.380 align:start position:0% um very simple namely in case of a tie 01:38:37.380 --> 01:38:38.930 align:start position:0% um very simple namely in case of a tie when<01:38:37.560> there<01:38:37.679> are<01:38:37.860> multiple<01:38:38.100> things<01:38:38.340> I'm<01:38:38.760> just 01:38:38.930 --> 01:38:38.940 align:start position:0% when there are multiple things I'm just 01:38:38.940 --> 01:38:41.090 align:start position:0% when there are multiple things I'm just taking<01:38:39.120> here<01:38:39.540> by<01:38:40.139> hand<01:38:40.320> I'm<01:38:40.560> just<01:38:40.739> taking<01:38:40.860> the 01:38:41.090 --> 01:38:41.100 align:start position:0% taking here by hand I'm just taking the 01:38:41.100 --> 01:38:42.110 align:start position:0% taking here by hand I'm just taking the fourth<01:38:41.460> element 01:38:42.110 --> 01:38:42.120 align:start position:0% fourth element 01:38:42.120 --> 01:38:44.270 align:start position:0% fourth element and<01:38:42.719> you<01:38:43.199> know<01:38:43.320> for<01:38:43.440> that<01:38:43.620> specific<01:38:43.860> example 01:38:44.270 --> 01:38:44.280 align:start position:0% and you know for that specific example 01:38:44.280 --> 01:38:46.070 align:start position:0% and you know for that specific example I'm<01:38:44.520> just<01:38:44.760> specializing<01:38:45.600> it<01:38:45.719> for<01:38:45.900> that 01:38:46.070 --> 01:38:46.080 align:start position:0% I'm just specializing it for that 01:38:46.080 --> 01:38:47.629 align:start position:0% I'm just specializing it for that specific<01:38:46.320> thing<01:38:46.560> because<01:38:46.739> it's<01:38:46.980> enough<01:38:47.159> but 01:38:47.629 --> 01:38:47.639 align:start position:0% specific thing because it's enough but 01:38:47.639 --> 01:38:49.250 align:start position:0% specific thing because it's enough but you<01:38:47.760> could<01:38:47.880> also<01:38:48.120> easily<01:38:48.480> extend<01:38:48.780> it<01:38:48.960> to<01:38:49.080> a 01:38:49.250 --> 01:38:49.260 align:start position:0% you could also easily extend it to a 01:38:49.260 --> 01:38:50.930 align:start position:0% you could also easily extend it to a more<01:38:49.320> General<01:38:49.500> version 01:38:50.930 --> 01:38:50.940 align:start position:0% more General version 01:38:50.940 --> 01:38:53.149 align:start position:0% more General version in<01:38:51.360> other<01:38:51.420> words<01:38:51.659> when<01:38:52.560> there<01:38:52.739> are<01:38:52.920> multiple 01:38:53.149 --> 01:38:53.159 align:start position:0% in other words when there are multiple 01:38:53.159 --> 01:38:54.770 align:start position:0% in other words when there are multiple candidates<01:38:53.520> I'm<01:38:53.820> just<01:38:54.060> deterministically 01:38:54.770 --> 01:38:54.780 align:start position:0% candidates I'm just deterministically 01:38:54.780 --> 01:38:56.570 align:start position:0% candidates I'm just deterministically choosing<01:38:55.139> one<01:38:55.320> of<01:38:55.380> the<01:38:55.500> elements<01:38:55.920> right<01:38:56.280> and 01:38:56.570 --> 01:38:56.580 align:start position:0% choosing one of the elements right and 01:38:56.580 --> 01:38:58.550 align:start position:0% choosing one of the elements right and I'm<01:38:56.760> doing<01:38:56.940> the<01:38:57.300> same<01:38:57.420> for<01:38:57.659> five<01:38:57.900> but<01:38:58.139> just<01:38:58.380> on 01:38:58.550 --> 01:38:58.560 align:start position:0% I'm doing the same for five but just on 01:38:58.560 --> 01:39:01.189 align:start position:0% I'm doing the same for five but just on the<01:38:58.739> other<01:38:58.860> on<01:38:59.400> the<01:38:59.520> other<01:38:59.639> element 01:39:01.189 --> 01:39:01.199 align:start position:0% the other on the other element 01:39:01.199 --> 01:39:03.770 align:start position:0% the other on the other element okay<01:39:01.620> now<01:39:01.920> I<01:39:02.100> have<01:39:02.159> several<01:39:02.520> scenarios 01:39:03.770 --> 01:39:03.780 align:start position:0% okay now I have several scenarios 01:39:03.780 --> 01:39:05.870 align:start position:0% okay now I have several scenarios um I<01:39:03.960> have<01:39:04.080> scenario<01:39:04.860> four<01:39:05.159> and<01:39:05.340> five<01:39:05.520> which 01:39:05.870 --> 01:39:05.880 align:start position:0% um I have scenario four and five which 01:39:05.880 --> 01:39:08.030 align:start position:0% um I have scenario four and five which is<01:39:06.060> just<01:39:06.300> the<01:39:06.960> same<01:39:07.080> proposal<01:39:07.620> strategy<01:39:07.860> as 01:39:08.030 --> 01:39:08.040 align:start position:0% is just the same proposal strategy as 01:39:08.040 --> 01:39:09.890 align:start position:0% is just the same proposal strategy as before<01:39:08.219> honest 01:39:09.890 --> 01:39:09.900 align:start position:0% before honest 01:39:09.900 --> 01:39:12.110 align:start position:0% before honest in<01:39:10.320> the<01:39:10.440> manipulator<01:39:10.739> chain<01:39:11.159> and<01:39:11.820> then<01:39:11.940> the 01:39:12.110 --> 01:39:12.120 align:start position:0% in the manipulator chain and then the 01:39:12.120 --> 01:39:13.790 align:start position:0% in the manipulator chain and then the validators<01:39:12.600> are<01:39:12.900> just<01:39:13.080> deterministically 01:39:13.790 --> 01:39:13.800 align:start position:0% validators are just deterministically 01:39:13.800 --> 01:39:17.330 align:start position:0% validators are just deterministically both<01:39:14.880> um<01:39:14.880> voting<01:39:15.300> for<01:39:15.420> id4<01:39:16.080> in<01:39:16.739> case<01:39:16.860> of<01:39:17.040> a<01:39:17.159> type 01:39:17.330 --> 01:39:17.340 align:start position:0% both um voting for id4 in case of a type 01:39:17.340 --> 01:39:20.570 align:start position:0% both um voting for id4 in case of a type or<01:39:17.699> alternatively<01:39:18.300> five 01:39:20.570 --> 01:39:20.580 align:start position:0% or alternatively five 01:39:20.580 --> 01:39:23.149 align:start position:0% or alternatively five and<01:39:21.239> lastly<01:39:21.540> the<01:39:22.020> random<01:39:22.320> is<01:39:22.620> basically<01:39:22.920> I'm 01:39:23.149 --> 01:39:23.159 align:start position:0% and lastly the random is basically I'm 01:39:23.159 --> 01:39:25.129 align:start position:0% and lastly the random is basically I'm just<01:39:23.280> taking<01:39:23.460> the<01:39:23.880> element<01:39:24.179> so<01:39:24.600> the<01:39:24.840> honest 01:39:25.129 --> 01:39:25.139 align:start position:0% just taking the element so the honest 01:39:25.139 --> 01:39:26.990 align:start position:0% just taking the element so the honest behavior<01:39:25.500> from<01:39:25.679> before<01:39:25.860> namely<01:39:26.520> if<01:39:26.699> there<01:39:26.880> is 01:39:26.990 --> 01:39:27.000 align:start position:0% behavior from before namely if there is 01:39:27.000 --> 01:39:29.450 align:start position:0% behavior from before namely if there is a<01:39:27.120> tie<01:39:27.300> I'm<01:39:27.480> just<01:39:27.600> randomizing 01:39:29.450 --> 01:39:29.460 align:start position:0% a tie I'm just randomizing 01:39:29.460 --> 01:39:30.770 align:start position:0% a tie I'm just randomizing which<01:39:29.880> obviously<01:39:30.179> is<01:39:30.300> also<01:39:30.480> debatable 01:39:30.770 --> 01:39:30.780 align:start position:0% which obviously is also debatable 01:39:30.780 --> 01:39:32.810 align:start position:0% which obviously is also debatable whether<01:39:31.020> this<01:39:31.260> is<01:39:31.380> a<01:39:31.440> good<01:39:31.560> idea<01:39:31.800> but<01:39:32.639> for 01:39:32.810 --> 01:39:32.820 align:start position:0% whether this is a good idea but for 01:39:32.820 --> 01:39:34.370 align:start position:0% whether this is a good idea but for illustration<01:39:33.239> purposes 01:39:34.370 --> 01:39:34.380 align:start position:0% illustration purposes 01:39:34.380 --> 01:39:36.290 align:start position:0% illustration purposes that's<01:39:34.860> enough<01:39:35.040> okay<01:39:35.400> let<01:39:35.820> me<01:39:35.940> run<01:39:36.060> through 01:39:36.290 --> 01:39:36.300 align:start position:0% that's enough okay let me run through 01:39:36.300 --> 01:39:38.330 align:start position:0% that's enough okay let me run through four<01:39:36.600> you<01:39:37.139> can<01:39:37.260> see<01:39:37.380> this<01:39:37.620> is<01:39:37.739> nice<01:39:37.920> this<01:39:38.219> is 01:39:38.330 --> 01:39:38.340 align:start position:0% four you can see this is nice this is 01:39:38.340 --> 01:39:39.770 align:start position:0% four you can see this is nice this is also<01:39:38.520> not<01:39:38.639> nice<01:39:38.880> this<01:39:39.120> isn't<01:39:39.420> this<01:39:39.600> is<01:39:39.719> an 01:39:39.770 --> 01:39:39.780 align:start position:0% also not nice this isn't this is an 01:39:39.780 --> 01:39:42.290 align:start position:0% also not nice this isn't this is an equilibrium<01:39:40.199> and<01:39:40.500> five<01:39:40.620> as<01:39:40.860> well<01:39:40.980> okay<01:39:41.880> so<01:39:42.060> far 01:39:42.290 --> 01:39:42.300 align:start position:0% equilibrium and five as well okay so far 01:39:42.300 --> 01:39:43.669 align:start position:0% equilibrium and five as well okay so far this<01:39:42.480> looks<01:39:42.719> like<01:39:42.780> pretty<01:39:42.960> useless<01:39:43.320> because 01:39:43.669 --> 01:39:43.679 align:start position:0% this looks like pretty useless because 01:39:43.679 --> 01:39:45.649 align:start position:0% this looks like pretty useless because everything<01:39:43.980> is<01:39:44.159> in<01:39:44.280> equilibrium<01:39:44.699> but<01:39:45.360> in<01:39:45.540> fact 01:39:45.649 --> 01:39:45.659 align:start position:0% everything is in equilibrium but in fact 01:39:45.659 --> 01:39:48.830 align:start position:0% everything is in equilibrium but in fact what<01:39:45.840> it<01:39:45.960> tells<01:39:46.260> you<01:39:46.320> is<01:39:47.159> that 01:39:48.830 --> 01:39:48.840 align:start position:0% what it tells you is that 01:39:48.840 --> 01:39:51.290 align:start position:0% what it tells you is that suddenly<01:39:49.620> we<01:39:50.280> have<01:39:50.400> two<01:39:50.520> equilibrium<01:39:51.060> at<01:39:51.179> the 01:39:51.290 --> 01:39:51.300 align:start position:0% suddenly we have two equilibrium at the 01:39:51.300 --> 01:39:53.870 align:start position:0% suddenly we have two equilibrium at the same<01:39:51.420> time<01:39:51.600> and<01:39:52.020> both<01:39:52.199> are<01:39:52.679> kind<01:39:53.280> of<01:39:53.400> either<01:39:53.639> we 01:39:53.870 --> 01:39:53.880 align:start position:0% same time and both are kind of either we 01:39:53.880 --> 01:39:55.610 align:start position:0% same time and both are kind of either we go<01:39:54.000> with<01:39:54.179> the<01:39:54.300> honors<01:39:54.600> proposal<01:39:55.020> and<01:39:55.139> the<01:39:55.380> one 01:39:55.610 --> 01:39:55.620 align:start position:0% go with the honors proposal and the one 01:39:55.620 --> 01:39:57.470 align:start position:0% go with the honors proposal and the one who<01:39:55.800> proposed<01:39:56.219> the<01:39:56.580> four<01:39:56.820> or<01:39:57.000> we<01:39:57.179> actually<01:39:57.300> go 01:39:57.470 --> 01:39:57.480 align:start position:0% who proposed the four or we actually go 01:39:57.480 --> 01:39:59.990 align:start position:0% who proposed the four or we actually go with<01:39:57.600> the<01:39:57.780> five<01:39:57.960> which<01:39:58.620> tells<01:39:58.980> you 01:39:59.990 --> 01:40:00.000 align:start position:0% with the five which tells you 01:40:00.000 --> 01:40:01.070 align:start position:0% with the five which tells you um this<01:40:00.239> is<01:40:00.300> not<01:40:00.420> in<01:40:00.540> the<01:40:00.659> interest<01:40:00.719> of<01:40:00.960> the 01:40:01.070 --> 01:40:01.080 align:start position:0% um this is not in the interest of the 01:40:01.080 --> 01:40:02.510 align:start position:0% um this is not in the interest of the protocol<01:40:01.320> this<01:40:01.620> one<01:40:01.860> of<01:40:01.920> them<01:40:02.040> should<01:40:02.280> not<01:40:02.400> be 01:40:02.510 --> 01:40:02.520 align:start position:0% protocol this one of them should not be 01:40:02.520 --> 01:40:03.649 align:start position:0% protocol this one of them should not be in<01:40:02.639> equilibrium 01:40:03.649 --> 01:40:03.659 align:start position:0% in equilibrium 01:40:03.659 --> 01:40:05.629 align:start position:0% in equilibrium and<01:40:04.139> you'll<01:40:04.320> see<01:40:04.440> even<01:40:04.620> more<01:40:04.800> if<01:40:05.159> I'm<01:40:05.280> sticking 01:40:05.629 --> 01:40:05.639 align:start position:0% and you'll see even more if I'm sticking 01:40:05.639 --> 01:40:09.050 align:start position:0% and you'll see even more if I'm sticking to<01:40:05.699> the<01:40:05.940> actual<01:40:06.179> Behavior<01:40:07.100> of<01:40:08.100> introducing 01:40:09.050 --> 01:40:09.060 align:start position:0% to the actual Behavior of introducing 01:40:09.060 --> 01:40:11.510 align:start position:0% to the actual Behavior of introducing the<01:40:09.179> possibility<01:40:09.540> of<01:40:09.960> random<01:40:10.380> basically<01:40:10.980> just 01:40:11.510 --> 01:40:11.520 align:start position:0% the possibility of random basically just 01:40:11.520 --> 01:40:12.950 align:start position:0% the possibility of random basically just honestly<01:40:12.060> saying<01:40:12.360> I<01:40:12.420> don't<01:40:12.540> know<01:40:12.659> when<01:40:12.840> I'm 01:40:12.950 --> 01:40:12.960 align:start position:0% honestly saying I don't know when I'm 01:40:12.960 --> 01:40:14.390 align:start position:0% honestly saying I don't know when I'm randomizing 01:40:14.390 --> 01:40:14.400 align:start position:0% randomizing 01:40:14.400 --> 01:40:17.149 align:start position:0% randomizing you<01:40:14.940> can<01:40:15.060> you<01:40:15.360> get<01:40:15.540> different<01:40:15.840> information 01:40:17.149 --> 01:40:17.159 align:start position:0% you can you get different information 01:40:17.159 --> 01:40:18.470 align:start position:0% you can you get different information um<01:40:17.219> and<01:40:17.460> this<01:40:17.520> is<01:40:17.699> the<01:40:17.760> alternative<01:40:18.060> namely 01:40:18.470 --> 01:40:18.480 align:start position:0% um and this is the alternative namely 01:40:18.480 --> 01:40:20.629 align:start position:0% um and this is the alternative namely the<01:40:18.659> system<01:40:18.840> recognizes<01:40:19.500> one<01:40:20.159> of<01:40:20.280> the<01:40:20.340> agents 01:40:20.629 --> 01:40:20.639 align:start position:0% the system recognizes one of the agents 01:40:20.639 --> 01:40:22.189 align:start position:0% the system recognizes one of the agents has<01:40:20.820> a<01:40:20.940> deviation 01:40:22.189 --> 01:40:22.199 align:start position:0% has a deviation 01:40:22.199 --> 01:40:24.169 align:start position:0% has a deviation the<01:40:22.500> formatting<01:40:22.920> is<01:40:23.040> horrible<01:40:23.280> but 01:40:24.169 --> 01:40:24.179 align:start position:0% the formatting is horrible but 01:40:24.179 --> 01:40:26.629 align:start position:0% the formatting is horrible but um for<01:40:24.540> basically<01:40:25.020> focus<01:40:25.380> on<01:40:25.860> the<01:40:26.280> first<01:40:26.400> part 01:40:26.629 --> 01:40:26.639 align:start position:0% um for basically focus on the first part 01:40:26.639 --> 01:40:30.229 align:start position:0% um for basically focus on the first part the<01:40:27.060> player<01:40:27.360> with<01:40:27.540> the<01:40:27.719> name<01:40:27.840> a21<01:40:28.820> has<01:40:29.820> a 01:40:30.229 --> 01:40:30.239 align:start position:0% the player with the name a21 has a 01:40:30.239 --> 01:40:32.209 align:start position:0% the player with the name a21 has a deviating<01:40:30.719> property<01:40:31.260> it's<01:40:31.560> optimal<01:40:31.980> payoff 01:40:32.209 --> 01:40:32.219 align:start position:0% deviating property it's optimal payoff 01:40:32.219 --> 01:40:34.189 align:start position:0% deviating property it's optimal payoff is<01:40:32.400> two<01:40:32.520> current<01:40:32.820> payoff<01:40:33.179> is<01:40:33.360> one<01:40:33.480> what's<01:40:33.960> the 01:40:34.189 --> 01:40:34.199 align:start position:0% is two current payoff is one what's the 01:40:34.199 --> 01:40:36.890 align:start position:0% is two current payoff is one what's the optimal<01:40:34.500> action<01:40:34.679> you<01:40:34.800> just<01:40:35.300> he<01:40:36.300> should<01:40:36.480> choose 01:40:36.890 --> 01:40:36.900 align:start position:0% optimal action you just he should choose 01:40:36.900 --> 01:40:40.729 align:start position:0% optimal action you just he should choose is<01:40:37.739> move<01:40:38.280> one<01:40:38.940> why<01:40:39.840> is<01:40:39.960> this<01:40:40.139> the<01:40:40.260> case<01:40:40.380> you<01:40:40.620> can 01:40:40.729 --> 01:40:40.739 align:start position:0% is move one why is this the case you can 01:40:40.739 --> 01:40:42.290 align:start position:0% is move one why is this the case you can easily<01:40:41.040> imagine<01:40:41.159> because<01:40:41.520> basically<01:40:42.000> these 01:40:42.290 --> 01:40:42.300 align:start position:0% easily imagine because basically these 01:40:42.300 --> 01:40:44.330 align:start position:0% easily imagine because basically these players<01:40:42.540> tried<01:40:42.840> to<01:40:43.139> coordinate<01:40:43.560> and<01:40:44.040> if<01:40:44.159> they 01:40:44.330 --> 01:40:44.340 align:start position:0% players tried to coordinate and if they 01:40:44.340 --> 01:40:45.890 align:start position:0% players tried to coordinate and if they are<01:40:44.460> diverging<01:40:44.940> the<01:40:45.120> protocol<01:40:45.360> will<01:40:45.600> punish 01:40:45.890 --> 01:40:45.900 align:start position:0% are diverging the protocol will punish 01:40:45.900 --> 01:40:47.450 align:start position:0% are diverging the protocol will punish them<01:40:46.080> so<01:40:46.679> they<01:40:46.800> actually<01:40:46.980> are<01:40:47.159> better<01:40:47.280> off 01:40:47.450 --> 01:40:47.460 align:start position:0% them so they actually are better off 01:40:47.460 --> 01:40:49.129 align:start position:0% them so they actually are better off voting<01:40:47.880> for<01:40:48.000> both<01:40:48.239> coordinating<01:40:48.780> on<01:40:49.020> the 01:40:49.129 --> 01:40:49.139 align:start position:0% voting for both coordinating on the 01:40:49.139 --> 01:40:51.649 align:start position:0% voting for both coordinating on the wrong<01:40:49.320> or<01:40:49.560> the<01:40:49.800> manipulated<01:40:50.360> head<01:40:51.360> of<01:40:51.540> the 01:40:51.649 --> 01:40:51.659 align:start position:0% wrong or the manipulated head of the 01:40:51.659 --> 01:40:53.810 align:start position:0% wrong or the manipulated head of the chain<01:40:51.780> instead<01:40:52.139> of<01:40:52.260> sticking<01:40:52.679> to<01:40:53.340> their<01:40:53.520> honor 01:40:53.810 --> 01:40:53.820 align:start position:0% chain instead of sticking to their honor 01:40:53.820 --> 01:40:55.490 align:start position:0% chain instead of sticking to their honor strategy<01:40:54.179> so<01:40:54.600> at<01:40:54.780> that<01:40:54.900> moment<01:40:55.139> you<01:40:55.320> see 01:40:55.490 --> 01:40:55.500 align:start position:0% strategy so at that moment you see 01:40:55.500 --> 01:40:57.169 align:start position:0% strategy so at that moment you see Things<01:40:55.980> Fall<01:40:56.280> Apart 01:40:57.169 --> 01:40:57.179 align:start position:0% Things Fall Apart 01:40:57.179 --> 01:40:58.970 align:start position:0% Things Fall Apart because<01:40:57.600> that's<01:40:57.840> very<01:40:58.080> very<01:40:58.380> relatively 01:40:58.970 --> 01:40:58.980 align:start position:0% because that's very very relatively 01:40:58.980 --> 01:41:01.550 align:start position:0% because that's very very relatively simple<01:40:59.159> model<01:40:59.400> and<01:41:00.060> again<01:41:00.179> this<01:41:00.840> kind<01:41:01.020> of<01:41:01.139> it's 01:41:01.550 --> 01:41:01.560 align:start position:0% simple model and again this kind of it's 01:41:01.560 --> 01:41:03.290 align:start position:0% simple model and again this kind of it's a<01:41:01.739> simple<01:41:01.920> illustration<01:41:02.460> here<01:41:02.699> but<01:41:02.880> that<01:41:03.120> kind 01:41:03.290 --> 01:41:03.300 align:start position:0% a simple illustration here but that kind 01:41:03.300 --> 01:41:05.030 align:start position:0% a simple illustration here but that kind of<01:41:03.420> structure<01:41:03.960> was<01:41:04.440> actually<01:41:04.620> motivation 01:41:05.030 --> 01:41:05.040 align:start position:0% of structure was actually motivation 01:41:05.040 --> 01:41:07.790 align:start position:0% of structure was actually motivation from<01:41:05.340> a<01:41:05.580> unrealistic<01:41:06.540> attack 01:41:07.790 --> 01:41:07.800 align:start position:0% from a unrealistic attack 01:41:07.800 --> 01:41:10.370 align:start position:0% from a unrealistic attack good<01:41:08.219> let<01:41:08.520> me<01:41:08.760> close<01:41:09.540> with<01:41:09.840> one<01:41:10.020> more<01:41:10.139> thing 01:41:10.370 --> 01:41:10.380 align:start position:0% good let me close with one more thing 01:41:10.380 --> 01:41:12.110 align:start position:0% good let me close with one more thing and<01:41:10.980> this<01:41:11.159> is<01:41:11.280> then<01:41:11.460> more<01:41:11.639> or<01:41:11.760> less<01:41:11.820> the<01:41:12.000> end 01:41:12.110 --> 01:41:12.120 align:start position:0% and this is then more or less the end 01:41:12.120 --> 01:41:14.689 align:start position:0% and this is then more or less the end with<01:41:12.360> kind<01:41:12.600> of<01:41:12.719> some<01:41:12.960> remarks 01:41:14.689 --> 01:41:14.699 align:start position:0% with kind of some remarks 01:41:14.699 --> 01:41:16.490 align:start position:0% with kind of some remarks this<01:41:15.060> is<01:41:15.179> the<01:41:15.300> interactive<01:41:15.659> version<01:41:15.840> I<01:41:16.320> said 01:41:16.490 --> 01:41:16.500 align:start position:0% this is the interactive version I said 01:41:16.500 --> 01:41:17.810 align:start position:0% this is the interactive version I said before<01:41:16.679> you<01:41:16.920> can<01:41:17.040> also<01:41:17.219> think<01:41:17.340> about<01:41:17.460> this<01:41:17.699> as 01:41:17.810 --> 01:41:17.820 align:start position:0% before you can also think about this as 01:41:17.820 --> 01:41:20.629 align:start position:0% before you can also think about this as being<01:41:18.000> part<01:41:18.239> of<01:41:18.420> a<01:41:18.540> system<01:41:18.719> so<01:41:19.560> you<01:41:19.800> can 01:41:20.629 --> 01:41:20.639 align:start position:0% being part of a system so you can 01:41:20.639 --> 01:41:22.070 align:start position:0% being part of a system so you can um 01:41:22.070 --> 01:41:22.080 align:start position:0% um 01:41:22.080 --> 01:41:23.689 align:start position:0% um um<01:41:22.260> basically<01:41:22.620> also<01:41:22.920> run<01:41:23.100> the<01:41:23.219> testing<01:41:23.520> in 01:41:23.689 --> 01:41:23.699 align:start position:0% um basically also run the testing in 01:41:23.699 --> 01:41:24.590 align:start position:0% um basically also run the testing in parallel 01:41:24.590 --> 01:41:24.600 align:start position:0% parallel 01:41:24.600 --> 01:41:27.530 align:start position:0% parallel or<01:41:25.080> as<01:41:25.260> an<01:41:25.440> alternative<01:41:25.739> so<01:41:26.699> if<01:41:27.060> you<01:41:27.179> do<01:41:27.360> this 01:41:27.530 --> 01:41:27.540 align:start position:0% or as an alternative so if you do this 01:41:27.540 --> 01:41:29.450 align:start position:0% or as an alternative so if you do this basically<01:41:27.960> what<01:41:28.139> will<01:41:28.320> happen<01:41:28.440> is<01:41:28.739> you<01:41:29.280> have 01:41:29.450 --> 01:41:29.460 align:start position:0% basically what will happen is you have 01:41:29.460 --> 01:41:31.129 align:start position:0% basically what will happen is you have some<01:41:29.639> kind<01:41:29.820> of<01:41:29.940> specification<01:41:30.540> test<01:41:30.780> this 01:41:31.129 --> 01:41:31.139 align:start position:0% some kind of specification test this 01:41:31.139 --> 01:41:32.510 align:start position:0% some kind of specification test this includes<01:41:31.440> the<01:41:31.560> equilibrium<01:41:32.040> but<01:41:32.159> it<01:41:32.280> can<01:41:32.400> also 01:41:32.510 --> 01:41:32.520 align:start position:0% includes the equilibrium but it can also 01:41:32.520 --> 01:41:34.250 align:start position:0% includes the equilibrium but it can also be<01:41:32.639> the<01:41:32.820> parts<01:41:32.940> you<01:41:33.300> know<01:41:33.420> is<01:41:33.659> the<01:41:33.900> staking 01:41:34.250 --> 01:41:34.260 align:start position:0% be the parts you know is the staking 01:41:34.260 --> 01:41:36.470 align:start position:0% be the parts you know is the staking protocol<01:41:34.560> working<01:41:34.860> in<01:41:35.100> the<01:41:35.159> right<01:41:35.280> way 01:41:36.470 --> 01:41:36.480 align:start position:0% protocol working in the right way 01:41:36.480 --> 01:41:37.910 align:start position:0% protocol working in the right way um<01:41:36.540> and<01:41:36.780> then<01:41:36.900> hesper<01:41:37.500> is<01:41:37.619> actually<01:41:37.739> quite 01:41:37.910 --> 01:41:37.920 align:start position:0% um and then hesper is actually quite 01:41:37.920 --> 01:41:39.709 align:start position:0% um and then hesper is actually quite nice<01:41:38.040> in<01:41:38.219> that<01:41:38.340> end<01:41:38.520> because<01:41:38.699> it<01:41:39.000> can<01:41:39.119> create<01:41:39.480> a 01:41:39.709 --> 01:41:39.719 align:start position:0% nice in that end because it can create a 01:41:39.719 --> 01:41:41.990 align:start position:0% nice in that end because it can create a lot<01:41:39.840> of<01:41:39.960> very<01:41:40.619> well<01:41:40.800> structured<01:41:41.340> arbitrary 01:41:41.990 --> 01:41:42.000 align:start position:0% lot of very well structured arbitrary 01:41:42.000 --> 01:41:43.790 align:start position:0% lot of very well structured arbitrary examples<01:41:42.360> that<01:41:42.600> you<01:41:42.659> care<01:41:42.780> about<01:41:42.900> and<01:41:43.679> then 01:41:43.790 --> 01:41:43.800 align:start position:0% examples that you care about and then 01:41:43.800 --> 01:41:44.870 align:start position:0% examples that you care about and then you<01:41:43.920> will<01:41:44.040> see<01:41:44.159> at<01:41:44.340> the<01:41:44.460> end<01:41:44.520> hopefully 01:41:44.870 --> 01:41:44.880 align:start position:0% you will see at the end hopefully 01:41:44.880 --> 01:41:47.149 align:start position:0% you will see at the end hopefully something<01:41:45.119> green<01:41:45.420> like<01:41:45.659> this<01:41:46.159> which 01:41:47.149 --> 01:41:47.159 align:start position:0% something green like this which 01:41:47.159 --> 01:41:48.649 align:start position:0% something green like this which generated<01:41:47.580> in<01:41:47.940> that<01:41:48.000> case<01:41:48.179> I<01:41:48.360> think<01:41:48.480> 100 01:41:48.649 --> 01:41:48.659 align:start position:0% generated in that case I think 100 01:41:48.659 --> 01:41:50.770 align:start position:0% generated in that case I think 100 different<01:41:49.199> starting<01:41:49.560> points<01:41:50.040> for<01:41:50.219> the<01:41:50.340> chain 01:41:50.770 --> 01:41:50.780 align:start position:0% different starting points for the chain 01:41:50.780 --> 01:41:53.689 align:start position:0% different starting points for the chain evaluated<01:41:51.780> them<01:41:52.139> and<01:41:53.100> you<01:41:53.280> get<01:41:53.340> some<01:41:53.520> result 01:41:53.689 --> 01:41:53.699 align:start position:0% evaluated them and you get some result 01:41:53.699 --> 01:41:56.030 align:start position:0% evaluated them and you get some result yeah<01:41:54.659> and<01:41:55.080> can<01:41:55.380> you<01:41:55.440> can<01:41:55.560> see<01:41:55.679> this<01:41:55.860> is 01:41:56.030 --> 01:41:56.040 align:start position:0% yeah and can you can see this is 01:41:56.040 --> 01:41:58.010 align:start position:0% yeah and can you can see this is basically<01:41:56.340> you<01:41:56.520> can<01:41:56.699> you<01:41:57.119> can<01:41:57.480> extend<01:41:57.719> this<01:41:57.840> in 01:41:58.010 --> 01:41:58.020 align:start position:0% basically you can you can extend this in 01:41:58.020 --> 01:41:59.270 align:start position:0% basically you can you can extend this in all<01:41:58.139> kinds<01:41:58.380> of<01:41:58.440> versions<01:41:58.739> it<01:41:58.980> can<01:41:59.040> be<01:41:59.159> either 01:41:59.270 --> 01:41:59.280 align:start position:0% all kinds of versions it can be either 01:41:59.280 --> 01:42:01.310 align:start position:0% all kinds of versions it can be either on<01:41:59.520> the<01:41:59.639> behavioral<01:42:00.000> level<01:42:00.119> really<01:42:01.020> thinking 01:42:01.310 --> 01:42:01.320 align:start position:0% on the behavioral level really thinking 01:42:01.320 --> 01:42:02.689 align:start position:0% on the behavioral level really thinking about<01:42:01.380> equilibrium<01:42:01.980> that<01:42:02.280> would<01:42:02.460> be<01:42:02.580> the 01:42:02.689 --> 01:42:02.699 align:start position:0% about equilibrium that would be the 01:42:02.699 --> 01:42:05.570 align:start position:0% about equilibrium that would be the first<01:42:02.820> test<01:42:03.260> or<01:42:04.260> if<01:42:04.739> you<01:42:04.800> go<01:42:04.980> down<01:42:05.100> really<01:42:05.340> just 01:42:05.570 --> 01:42:05.580 align:start position:0% first test or if you go down really just 01:42:05.580 --> 01:42:08.169 align:start position:0% first test or if you go down really just the<01:42:05.760> components 01:42:08.169 --> 01:42:08.179 align:start position:0% the components 01:42:08.179 --> 01:42:15.590 align:start position:0% the components okay<01:42:09.179> questions<01:42:09.900> before<01:42:10.380> I<01:42:10.619> conclude 01:42:15.590 --> 01:42:15.600 align:start position:0% 01:42:15.600 --> 01:42:17.930 align:start position:0% let<01:42:15.900> me<01:42:16.020> conclude 01:42:17.930 --> 01:42:17.940 align:start position:0% let me conclude 01:42:17.940 --> 01:42:19.850 align:start position:0% let me conclude um<01:42:18.060> on<01:42:18.780> two<01:42:18.900> levels<01:42:19.260> first<01:42:19.380> a<01:42:19.619> bit<01:42:19.739> more 01:42:19.850 --> 01:42:19.860 align:start position:0% um on two levels first a bit more 01:42:19.860 --> 01:42:21.050 align:start position:0% um on two levels first a bit more concretely<01:42:20.100> what<01:42:20.280> is<01:42:20.460> the<01:42:20.520> end<01:42:20.760> of<01:42:20.820> the<01:42:20.940> next 01:42:21.050 --> 01:42:21.060 align:start position:0% concretely what is the end of the next 01:42:21.060 --> 01:42:23.090 align:start position:0% concretely what is the end of the next steps<01:42:21.300> for<01:42:21.420> this<01:42:21.600> engine 01:42:23.090 --> 01:42:23.100 align:start position:0% steps for this engine 01:42:23.100 --> 01:42:25.070 align:start position:0% steps for this engine and<01:42:23.580> then<01:42:23.760> circling<01:42:24.480> back<01:42:24.659> to<01:42:24.780> where<01:42:24.960> we 01:42:25.070 --> 01:42:25.080 align:start position:0% and then circling back to where we 01:42:25.080 --> 01:42:26.330 align:start position:0% and then circling back to where we actually<01:42:25.199> started<01:42:25.500> so<01:42:25.619> this<01:42:25.860> is<01:42:26.040> connected 01:42:26.330 --> 01:42:26.340 align:start position:0% actually started so this is connected 01:42:26.340 --> 01:42:27.950 align:start position:0% actually started so this is connected the<01:42:26.460> rest<01:42:26.580> of<01:42:26.760> category<01:42:27.060> Theory<01:42:27.420> or<01:42:27.719> maybe 01:42:27.950 --> 01:42:27.960 align:start position:0% the rest of category Theory or maybe 01:42:27.960 --> 01:42:31.729 align:start position:0% the rest of category Theory or maybe more<01:42:28.260> precisely<01:42:28.619> black<01:42:28.860> category<01:42:29.219> Theory 01:42:31.729 --> 01:42:31.739 align:start position:0% 01:42:31.739 --> 01:42:33.709 align:start position:0% so<01:42:32.219> one<01:42:32.400> of<01:42:32.520> the<01:42:32.639> things<01:42:32.760> and<01:42:33.300> some<01:42:33.540> of 01:42:33.709 --> 01:42:33.719 align:start position:0% so one of the things and some of 01:42:33.719 --> 01:42:35.330 align:start position:0% so one of the things and some of actually<01:42:34.080> formal<01:42:34.500> verification<01:42:34.860> people<01:42:35.159> are 01:42:35.330 --> 01:42:35.340 align:start position:0% actually formal verification people are 01:42:35.340 --> 01:42:38.090 align:start position:0% actually formal verification people are here<01:42:35.520> we<01:42:35.820> are<01:42:36.060> one<01:42:36.360> project<01:42:36.659> that<01:42:36.900> we<01:42:37.080> have<01:42:37.199> is 01:42:38.090 --> 01:42:38.100 align:start position:0% here we are one project that we have is 01:42:38.100 --> 01:42:39.649 align:start position:0% here we are one project that we have is I<01:42:38.580> mentioned<01:42:38.820> this<01:42:38.940> we<01:42:39.119> want<01:42:39.239> to<01:42:39.360> have<01:42:39.480> more 01:42:39.649 --> 01:42:39.659 align:start position:0% I mentioned this we want to have more 01:42:39.659 --> 01:42:41.510 align:start position:0% I mentioned this we want to have more pipeline<01:42:40.080> from<01:42:40.380> let's<01:42:40.980> say<01:42:41.159> starting<01:42:41.340> from 01:42:41.510 --> 01:42:41.520 align:start position:0% pipeline from let's say starting from 01:42:41.520 --> 01:42:43.010 align:start position:0% pipeline from let's say starting from evm<01:42:41.880> code<01:42:42.060> into<01:42:42.239> actual<01:42:42.600> open<01:42:42.780> games 01:42:43.010 --> 01:42:43.020 align:start position:0% evm code into actual open games 01:42:43.020 --> 01:42:44.870 align:start position:0% evm code into actual open games representation<01:42:43.619> a<01:42:44.040> lot<01:42:44.159> of<01:42:44.280> work<01:42:44.460> has<01:42:44.699> already 01:42:44.870 --> 01:42:44.880 align:start position:0% representation a lot of work has already 01:42:44.880 --> 01:42:47.629 align:start position:0% representation a lot of work has already been<01:42:45.060> done<01:42:45.239> that<01:42:45.900> we<01:42:46.080> can<01:42:46.139> dock<01:42:46.440> on<01:42:46.619> and<01:42:47.219> one 01:42:47.629 --> 01:42:47.639 align:start position:0% been done that we can dock on and one 01:42:47.639 --> 01:42:49.189 align:start position:0% been done that we can dock on and one project<01:42:47.880> is<01:42:48.239> basically<01:42:48.480> to<01:42:48.719> kind<01:42:48.840> of<01:42:48.960> extend 01:42:49.189 --> 01:42:49.199 align:start position:0% project is basically to kind of extend 01:42:49.199 --> 01:42:51.169 align:start position:0% project is basically to kind of extend this<01:42:49.380> towards<01:42:49.920> the<01:42:50.280> open<01:42:50.460> games<01:42:50.699> framework<01:42:51.060> so 01:42:51.169 --> 01:42:51.179 align:start position:0% this towards the open games framework so 01:42:51.179 --> 01:42:54.229 align:start position:0% this towards the open games framework so that<01:42:51.300> if<01:42:51.420> you<01:42:51.540> can<01:42:51.780> start<01:42:51.960> with<01:42:52.199> some<01:42:53.520> um<01:42:53.580> smart 01:42:54.229 --> 01:42:54.239 align:start position:0% that if you can start with some um smart 01:42:54.239 --> 01:42:56.870 align:start position:0% that if you can start with some um smart contracts<01:42:54.780> you<01:42:55.560> basically<01:42:55.920> get<01:42:56.219> an<01:42:56.699> open 01:42:56.870 --> 01:42:56.880 align:start position:0% contracts you basically get an open 01:42:56.880 --> 01:42:58.669 align:start position:0% contracts you basically get an open games<01:42:57.119> representation<01:42:57.780> and<01:42:58.320> then<01:42:58.440> you<01:42:58.560> can 01:42:58.669 --> 01:42:58.679 align:start position:0% games representation and then you can 01:42:58.679 --> 01:43:00.590 align:start position:0% games representation and then you can start<01:42:58.860> querying<01:42:59.400> them 01:43:00.590 --> 01:43:00.600 align:start position:0% start querying them 01:43:00.600 --> 01:43:02.030 align:start position:0% start querying them um<01:43:00.659> either<01:43:00.960> automatically<01:43:01.500> or<01:43:01.739> with<01:43:01.860> your 01:43:02.030 --> 01:43:02.040 align:start position:0% um either automatically or with your 01:43:02.040 --> 01:43:04.010 align:start position:0% um either automatically or with your manual<01:43:02.400> maybe<01:43:03.179> you<01:43:03.360> have<01:43:03.480> some<01:43:03.600> ideas<01:43:03.719> of<01:43:03.900> what 01:43:04.010 --> 01:43:04.020 align:start position:0% manual maybe you have some ideas of what 01:43:04.020 --> 01:43:05.870 align:start position:0% manual maybe you have some ideas of what you<01:43:04.139> want<01:43:04.260> to<01:43:04.320> query<01:43:04.560> in<01:43:04.980> a<01:43:05.100> manual<01:43:05.400> in<01:43:05.760> a 01:43:05.870 --> 01:43:05.880 align:start position:0% you want to query in a manual in a 01:43:05.880 --> 01:43:08.270 align:start position:0% you want to query in a manual in a manual<01:43:06.060> way<01:43:06.239> or<01:43:06.659> you<01:43:06.840> have<01:43:07.020> some<01:43:07.320> more<01:43:07.920> bigger 01:43:08.270 --> 01:43:08.280 align:start position:0% manual way or you have some more bigger 01:43:08.280 --> 01:43:11.810 align:start position:0% manual way or you have some more bigger and<01:43:08.400> analyst<01:43:09.380> tools<01:43:10.380> on<01:43:10.560> top 01:43:11.810 --> 01:43:11.820 align:start position:0% and analyst tools on top 01:43:11.820 --> 01:43:13.149 align:start position:0% and analyst tools on top thank<01:43:11.940> you 01:43:13.149 --> 01:43:13.159 align:start position:0% thank you 01:43:13.159 --> 01:43:15.470 align:start position:0% thank you uh<01:43:14.159> you<01:43:14.400> know<01:43:14.520> the<01:43:14.580> analytics<01:43:14.880> we<01:43:15.060> have<01:43:15.179> so<01:43:15.300> far 01:43:15.470 --> 01:43:15.480 align:start position:0% uh you know the analytics we have so far 01:43:15.480 --> 01:43:16.850 align:start position:0% uh you know the analytics we have so far we're<01:43:15.600> extending<01:43:15.960> them<01:43:16.080> permanently<01:43:16.560> we're 01:43:16.850 --> 01:43:16.860 align:start position:0% we're extending them permanently we're 01:43:16.860 --> 01:43:18.169 align:start position:0% we're extending them permanently we're also<01:43:17.100> you<01:43:17.340> know<01:43:17.400> going<01:43:17.760> into<01:43:17.940> different 01:43:18.169 --> 01:43:18.179 align:start position:0% also you know going into different 01:43:18.179 --> 01:43:19.669 align:start position:0% also you know going into different applications<01:43:18.659> and<01:43:19.080> thinking<01:43:19.260> about<01:43:19.320> how<01:43:19.500> they 01:43:19.669 --> 01:43:19.679 align:start position:0% applications and thinking about how they 01:43:19.679 --> 01:43:21.410 align:start position:0% applications and thinking about how they you<01:43:19.800> know<01:43:19.920> what<01:43:20.040> specific<01:43:20.340> analytics<01:43:21.239> are 01:43:21.410 --> 01:43:21.420 align:start position:0% you know what specific analytics are 01:43:21.420 --> 01:43:23.090 align:start position:0% you know what specific analytics are relevant<01:43:21.719> there 01:43:23.090 --> 01:43:23.100 align:start position:0% relevant there 01:43:23.100 --> 01:43:25.550 align:start position:0% relevant there um<01:43:23.159> it's<01:43:23.460> outside<01:43:23.699> of<01:43:24.000> staking 01:43:25.550 --> 01:43:25.560 align:start position:0% um it's outside of staking 01:43:25.560 --> 01:43:26.870 align:start position:0% um it's outside of staking and 01:43:26.870 --> 01:43:26.880 align:start position:0% and 01:43:26.880 --> 01:43:28.430 align:start position:0% and I<01:43:27.239> should<01:43:27.300> mention<01:43:27.540> this<01:43:27.719> before<01:43:27.900> which<01:43:28.139> is<01:43:28.260> an 01:43:28.430 --> 01:43:28.440 align:start position:0% I should mention this before which is an 01:43:28.440 --> 01:43:29.330 align:start position:0% I should mention this before which is an actually<01:43:28.560> important<01:43:28.920> thing<01:43:29.040> the<01:43:29.219> engine 01:43:29.330 --> 01:43:29.340 align:start position:0% actually important thing the engine 01:43:29.340 --> 01:43:31.430 align:start position:0% actually important thing the engine itself<01:43:29.820> the<01:43:30.480> end<01:43:30.600> the<01:43:30.900> version<01:43:30.960> that<01:43:31.199> you<01:43:31.320> see 01:43:31.430 --> 01:43:31.440 align:start position:0% itself the end the version that you see 01:43:31.440 --> 01:43:33.590 align:start position:0% itself the end the version that you see here<01:43:31.560> is<01:43:31.800> basically<01:43:32.100> built<01:43:32.760> on<01:43:32.880> Theory 01:43:33.590 --> 01:43:33.600 align:start position:0% here is basically built on Theory 01:43:33.600 --> 01:43:34.609 align:start position:0% here is basically built on Theory version 01:43:34.609 --> 01:43:34.619 align:start position:0% version 01:43:34.619 --> 01:43:37.370 align:start position:0% version outdated<01:43:35.280> time<01:43:36.300> -3<01:43:36.540> or<01:43:36.780> so<01:43:36.900> there<01:43:37.080> have<01:43:37.260> been 01:43:37.370 --> 01:43:37.380 align:start position:0% outdated time -3 or so there have been 01:43:37.380 --> 01:43:39.050 align:start position:0% outdated time -3 or so there have been three<01:43:37.860> more<01:43:38.040> iterations<01:43:38.460> and<01:43:38.699> one<01:43:38.880> of<01:43:39.000> the 01:43:39.050 --> 01:43:39.060 align:start position:0% three more iterations and one of the 01:43:39.060 --> 01:43:40.550 align:start position:0% three more iterations and one of the tasks<01:43:39.360> in<01:43:39.480> the<01:43:39.600> next<01:43:39.719> weeks<01:43:39.960> a<01:43:40.080> month<01:43:40.199> will<01:43:40.380> be 01:43:40.550 --> 01:43:40.560 align:start position:0% tasks in the next weeks a month will be 01:43:40.560 --> 01:43:42.229 align:start position:0% tasks in the next weeks a month will be basically<01:43:40.739> an<01:43:40.860> update<01:43:41.100> of<01:43:41.219> the<01:43:41.400> engine<01:43:41.520> the 01:43:42.229 --> 01:43:42.239 align:start position:0% basically an update of the engine the 01:43:42.239 --> 01:43:43.850 align:start position:0% basically an update of the engine the theory<01:43:42.540> itself<01:43:42.840> is<01:43:43.080> also<01:43:43.380> continuously 01:43:43.850 --> 01:43:43.860 align:start position:0% theory itself is also continuously 01:43:43.860 --> 01:43:46.070 align:start position:0% theory itself is also continuously developed 01:43:46.070 --> 01:43:46.080 align:start position:0% developed 01:43:46.080 --> 01:43:48.649 align:start position:0% developed okay<01:43:46.619> lastly<01:43:47.300> compositionality<01:43:48.300> that<01:43:48.480> was 01:43:48.649 --> 01:43:48.659 align:start position:0% okay lastly compositionality that was 01:43:48.659 --> 01:43:49.790 align:start position:0% okay lastly compositionality that was the<01:43:48.840> starting<01:43:48.960> point<01:43:49.139> you've<01:43:49.500> seen<01:43:49.619> one 01:43:49.790 --> 01:43:49.800 align:start position:0% the starting point you've seen one 01:43:49.800 --> 01:43:51.290 align:start position:0% the starting point you've seen one instance<01:43:50.100> of<01:43:50.219> why<01:43:50.340> compositionality<01:43:51.060> might 01:43:51.290 --> 01:43:51.300 align:start position:0% instance of why compositionality might 01:43:51.300 --> 01:43:53.870 align:start position:0% instance of why compositionality might be<01:43:51.420> useful<01:43:51.719> in<01:43:52.020> the<01:43:52.080> context<01:43:52.320> of<01:43:52.500> open<01:43:52.679> games 01:43:53.870 --> 01:43:53.880 align:start position:0% be useful in the context of open games 01:43:53.880 --> 01:43:55.490 align:start position:0% be useful in the context of open games what<01:43:54.360> is<01:43:54.480> interesting<01:43:54.780> about<01:43:54.900> this<01:43:55.199> specific 01:43:55.490 --> 01:43:55.500 align:start position:0% what is interesting about this specific 01:43:55.500 --> 01:44:00.470 align:start position:0% what is interesting about this specific example<01:43:56.100> is<01:43:57.060> that<01:43:58.020> when<01:43:58.980> we<01:43:59.100> started 01:44:00.470 --> 01:44:00.480 align:start position:0% example is that when we started 01:44:00.480 --> 01:44:01.370 align:start position:0% example is that when we started um 01:44:01.370 --> 01:44:01.380 align:start position:0% um 01:44:01.380 --> 01:44:03.770 align:start position:0% um out<01:44:01.800> there<01:44:02.699> is<01:44:02.880> this<01:44:03.000> basic<01:44:03.300> question<01:44:03.480> that 01:44:03.770 --> 01:44:03.780 align:start position:0% out there is this basic question that 01:44:03.780 --> 01:44:06.350 align:start position:0% out there is this basic question that probably<01:44:04.020> raised<01:44:04.920> in<01:44:05.040> the<01:44:05.159> initial<01:44:05.460> slide 01:44:06.350 --> 01:44:06.360 align:start position:0% probably raised in the initial slide 01:44:06.360 --> 01:44:07.790 align:start position:0% probably raised in the initial slide mean<01:44:06.540> or<01:44:06.780> in<01:44:06.960> the<01:44:07.020> initial<01:44:07.260> beginning<01:44:07.440> of<01:44:07.679> his 01:44:07.790 --> 01:44:07.800 align:start position:0% mean or in the initial beginning of his 01:44:07.800 --> 01:44:09.530 align:start position:0% mean or in the initial beginning of his presentation<01:44:08.219> then<01:44:08.820> how<01:44:09.060> the<01:44:09.239> systems 01:44:09.530 --> 01:44:09.540 align:start position:0% presentation then how the systems 01:44:09.540 --> 01:44:12.050 align:start position:0% presentation then how the systems compose<01:44:09.900> in<01:44:10.679> the<01:44:10.800> game<01:44:10.860> theory<01:44:11.280> are<01:44:11.760> in<01:44:11.940> the 01:44:12.050 --> 01:44:12.060 align:start position:0% compose in the game theory are in the 01:44:12.060 --> 01:44:13.490 align:start position:0% compose in the game theory are in the game<01:44:12.119> City<01:44:12.300> setting<01:44:12.719> we<01:44:12.900> have<01:44:13.020> a<01:44:13.139> relatively 01:44:13.490 --> 01:44:13.500 align:start position:0% game City setting we have a relatively 01:44:13.500 --> 01:44:14.930 align:start position:0% game City setting we have a relatively clear<01:44:13.619> answer<01:44:13.860> and<01:44:14.219> what<01:44:14.400> was<01:44:14.520> interesting 01:44:14.930 --> 01:44:14.940 align:start position:0% clear answer and what was interesting 01:44:14.940 --> 01:44:17.090 align:start position:0% clear answer and what was interesting was<01:44:15.179> in<01:44:15.719> the<01:44:15.840> beginning<01:44:15.960> the<01:44:16.679> implementation 01:44:17.090 --> 01:44:17.100 align:start position:0% was in the beginning the implementation 01:44:17.100 --> 01:44:19.010 align:start position:0% was in the beginning the implementation and<01:44:17.280> the<01:44:17.400> way<01:44:17.520> we<01:44:17.639> did<01:44:17.760> it<01:44:17.880> categorically<01:44:18.300> is 01:44:19.010 --> 01:44:19.020 align:start position:0% and the way we did it categorically is 01:44:19.020 --> 01:44:20.750 align:start position:0% and the way we did it categorically is not<01:44:19.260> at<01:44:19.440> all<01:44:19.560> doesn't<01:44:19.920> resemble<01:44:20.400> at<01:44:20.520> all<01:44:20.639> the 01:44:20.750 --> 01:44:20.760 align:start position:0% not at all doesn't resemble at all the 01:44:20.760 --> 01:44:22.070 align:start position:0% not at all doesn't resemble at all the way<01:44:20.880> it<01:44:21.000> looks<01:44:21.239> right<01:44:21.360> now<01:44:21.540> because<01:44:21.780> at<01:44:21.960> the 01:44:22.070 --> 01:44:22.080 align:start position:0% way it looks right now because at the 01:44:22.080 --> 01:44:23.030 align:start position:0% way it looks right now because at the beginning<01:44:22.199> we<01:44:22.380> had<01:44:22.500> a<01:44:22.619> very<01:44:22.679> different<01:44:22.860> way 01:44:23.030 --> 01:44:23.040 align:start position:0% beginning we had a very different way 01:44:23.040 --> 01:44:24.830 align:start position:0% beginning we had a very different way what<01:44:23.760> we<01:44:23.940> realized<01:44:24.239> actually<01:44:24.420> is<01:44:24.659> the 01:44:24.830 --> 01:44:24.840 align:start position:0% what we realized actually is the 01:44:24.840 --> 01:44:26.209 align:start position:0% what we realized actually is the connection<01:44:24.960> to<01:44:25.260> lenses<01:44:25.560> in<01:44:25.679> a<01:44:25.860> categorical 01:44:26.209 --> 01:44:26.219 align:start position:0% connection to lenses in a categorical 01:44:26.219 --> 01:44:28.550 align:start position:0% connection to lenses in a categorical framework<01:44:26.580> what<01:44:26.940> we<01:44:27.060> also<01:44:27.300> realized 01:44:28.550 --> 01:44:28.560 align:start position:0% framework what we also realized 01:44:28.560 --> 01:44:30.890 align:start position:0% framework what we also realized um<01:44:28.619> was<01:44:28.980> actually<01:44:29.100> realizing<01:44:30.060> that<01:44:30.179> the<01:44:30.420> the 01:44:30.890 --> 01:44:30.900 align:start position:0% um was actually realizing that the the 01:44:30.900 --> 01:44:32.450 align:start position:0% um was actually realizing that the the existing<01:44:31.260> deterministic<01:44:31.920> lenses<01:44:32.219> are<01:44:32.340> not 01:44:32.450 --> 01:44:32.460 align:start position:0% existing deterministic lenses are not 01:44:32.460 --> 01:44:34.370 align:start position:0% existing deterministic lenses are not enough<01:44:32.639> and<01:44:33.179> this<01:44:33.360> is<01:44:33.540> quite<01:44:33.900> obvious<01:44:34.199> because 01:44:34.370 --> 01:44:34.380 align:start position:0% enough and this is quite obvious because 01:44:34.380 --> 01:44:36.830 align:start position:0% enough and this is quite obvious because games<01:44:34.679> need<01:44:34.980> Randomness<01:44:35.460> right<01:44:35.940> you<01:44:36.600> need<01:44:36.719> to 01:44:36.830 --> 01:44:36.840 align:start position:0% games need Randomness right you need to 01:44:36.840 --> 01:44:37.609 align:start position:0% games need Randomness right you need to deal<01:44:36.900> with 01:44:37.609 --> 01:44:37.619 align:start position:0% deal with 01:44:37.619 --> 01:44:39.350 align:start position:0% deal with um non-deterministic<01:44:38.520> moves 01:44:39.350 --> 01:44:39.360 align:start position:0% um non-deterministic moves 01:44:39.360 --> 01:44:41.570 align:start position:0% um non-deterministic moves that<01:44:39.960> actually<01:44:40.139> LED<01:44:40.380> also<01:44:40.679> to<01:44:40.739> Innovations<01:44:41.159> on 01:44:41.570 --> 01:44:41.580 align:start position:0% that actually LED also to Innovations on 01:44:41.580 --> 01:44:43.550 align:start position:0% that actually LED also to Innovations on the<01:44:41.760> on<01:44:41.940> the<01:44:42.119> side<01:44:42.239> of<01:44:42.420> the<01:44:43.020> um<01:44:43.080> Optics 01:44:43.550 --> 01:44:43.560 align:start position:0% the on the side of the um Optics 01:44:43.560 --> 01:44:45.649 align:start position:0% the on the side of the um Optics implementation<01:44:44.100> and<01:44:44.400> that<01:44:44.520> itself<01:44:44.820> profits 01:44:45.649 --> 01:44:45.659 align:start position:0% implementation and that itself profits 01:44:45.659 --> 01:44:47.870 align:start position:0% implementation and that itself profits alluded<01:44:46.020> to<01:44:46.080> that<01:44:46.260> is<01:44:46.679> itself<01:44:47.040> now<01:44:47.280> kind<01:44:47.580> of<01:44:47.699> a 01:44:47.870 --> 01:44:47.880 align:start position:0% alluded to that is itself now kind of a 01:44:47.880 --> 01:44:50.570 align:start position:0% alluded to that is itself now kind of a you<01:44:48.540> know<01:44:48.659> in<01:44:49.440> an<01:44:49.560> area<01:44:49.679> which<01:44:50.040> is<01:44:50.100> almost 01:44:50.570 --> 01:44:50.580 align:start position:0% you know in an area which is almost 01:44:50.580 --> 01:44:52.010 align:start position:0% you know in an area which is almost exploding<01:44:51.060> in<01:44:51.179> all<01:44:51.300> kinds<01:44:51.540> of<01:44:51.540> directions<01:44:51.719> and 01:44:52.010 --> 01:44:52.020 align:start position:0% exploding in all kinds of directions and 01:44:52.020 --> 01:44:53.330 align:start position:0% exploding in all kinds of directions and making<01:44:52.199> connections<01:44:52.679> and<01:44:52.860> extending<01:44:53.219> this 01:44:53.330 --> 01:44:53.340 align:start position:0% making connections and extending this 01:44:53.340 --> 01:44:55.129 align:start position:0% making connections and extending this framework<01:44:53.699> this<01:44:54.480> is<01:44:54.600> one<01:44:54.780> of<01:44:54.840> the<01:44:54.960> things 01:44:55.129 --> 01:44:55.139 align:start position:0% framework this is one of the things 01:44:55.139 --> 01:44:56.570 align:start position:0% framework this is one of the things which<01:44:55.440> is<01:44:55.560> quite<01:44:55.739> nice<01:44:55.920> actually<01:44:56.159> about<01:44:56.340> all 01:44:56.570 --> 01:44:56.580 align:start position:0% which is quite nice actually about all 01:44:56.580 --> 01:44:58.189 align:start position:0% which is quite nice actually about all of<01:44:56.699> this<01:44:56.820> work<01:44:57.000> that<01:44:57.179> it's<01:44:57.360> tightly<01:44:57.719> it's 01:44:58.189 --> 01:44:58.199 align:start position:0% of this work that it's tightly it's 01:44:58.199 --> 01:45:00.430 align:start position:0% of this work that it's tightly it's tying<01:44:58.560> back<01:44:58.619> into<01:44:58.800> other<01:44:59.100> fields<01:44:59.520> within<01:45:00.179> the 01:45:00.430 --> 01:45:00.440 align:start position:0% tying back into other fields within the 01:45:00.440 --> 01:45:02.689 align:start position:0% tying back into other fields within the categorical<01:45:01.440> framework<01:45:01.920> and<01:45:02.219> examples<01:45:02.520> of 01:45:02.689 --> 01:45:02.699 align:start position:0% categorical framework and examples of 01:45:02.699 --> 01:45:04.250 align:start position:0% categorical framework and examples of that<01:45:02.820> are<01:45:03.060> control<01:45:03.300> theory<01:45:03.719> reinforcement 01:45:04.250 --> 01:45:04.260 align:start position:0% that are control theory reinforcement 01:45:04.260 --> 01:45:06.169 align:start position:0% that are control theory reinforcement learning<01:45:04.560> active<01:45:04.739> inference<01:45:05.159> others<01:45:05.940> to<01:45:06.060> be 01:45:06.169 --> 01:45:06.179 align:start position:0% learning active inference others to be 01:45:06.179 --> 01:45:08.810 align:start position:0% learning active inference others to be developed<01:45:07.080> and<01:45:07.920> the<01:45:08.280> abstraction<01:45:08.580> here 01:45:08.810 --> 01:45:08.820 align:start position:0% developed and the abstraction here 01:45:08.820 --> 01:45:10.189 align:start position:0% developed and the abstraction here really<01:45:09.060> enables<01:45:09.420> you<01:45:09.480> to<01:45:09.659> see<01:45:09.780> that<01:45:09.960> these 01:45:10.189 --> 01:45:10.199 align:start position:0% really enables you to see that these 01:45:10.199 --> 01:45:12.109 align:start position:0% really enables you to see that these patterns<01:45:10.560> are<01:45:10.980> or<01:45:11.580> that<01:45:11.760> these<01:45:12.000> different 01:45:12.109 --> 01:45:12.119 align:start position:0% patterns are or that these different 01:45:12.119 --> 01:45:13.609 align:start position:0% patterns are or that these different instances<01:45:12.540> are<01:45:12.840> actually<01:45:12.960> related<01:45:13.320> to<01:45:13.440> Common 01:45:13.609 --> 01:45:13.619 align:start position:0% instances are actually related to Common 01:45:13.619 --> 01:45:16.370 align:start position:0% instances are actually related to Common patterns<01:45:14.219> and<01:45:14.760> lastly<01:45:15.060> what<01:45:15.239> is<01:45:15.360> more<01:45:15.540> you<01:45:16.260> can 01:45:16.370 --> 01:45:16.380 align:start position:0% patterns and lastly what is more you can 01:45:16.380 --> 01:45:18.709 align:start position:0% patterns and lastly what is more you can also<01:45:16.619> make<01:45:16.800> cross<01:45:17.219> cross<01:45:17.280> combinations<01:45:18.179> one 01:45:18.709 --> 01:45:18.719 align:start position:0% also make cross cross combinations one 01:45:18.719 --> 01:45:19.910 align:start position:0% also make cross cross combinations one of<01:45:18.840> the<01:45:18.960> interesting<01:45:19.320> ones<01:45:19.619> is<01:45:19.739> actually 01:45:19.910 --> 01:45:19.920 align:start position:0% of the interesting ones is actually 01:45:19.920 --> 01:45:21.830 align:start position:0% of the interesting ones is actually thinking<01:45:20.280> about<01:45:20.400> games<01:45:20.699> and<01:45:21.000> learning<01:45:21.360> right 01:45:21.830 --> 01:45:21.840 align:start position:0% thinking about games and learning right 01:45:21.840 --> 01:45:23.810 align:start position:0% thinking about games and learning right which<01:45:22.320> is<01:45:22.440> not<01:45:22.560> new<01:45:22.739> itself<01:45:23.159> but<01:45:23.520> if<01:45:23.639> you<01:45:23.699> see 01:45:23.810 --> 01:45:23.820 align:start position:0% which is not new itself but if you see 01:45:23.820 --> 01:45:25.010 align:start position:0% which is not new itself but if you see it<01:45:23.940> in<01:45:24.060> that<01:45:24.179> form<01:45:24.360> and<01:45:24.480> you<01:45:24.600> have<01:45:24.719> this<01:45:24.840> new 01:45:25.010 --> 01:45:25.020 align:start position:0% it in that form and you have this new 01:45:25.020 --> 01:45:27.470 align:start position:0% it in that form and you have this new pattern<01:45:25.320> it's<01:45:25.739> quite<01:45:25.920> info<01:45:26.340> I<01:45:27.000> find<01:45:27.179> it<01:45:27.300> quite 01:45:27.470 --> 01:45:27.480 align:start position:0% pattern it's quite info I find it quite 01:45:27.480 --> 01:45:29.629 align:start position:0% pattern it's quite info I find it quite insightful<01:45:27.900> and<01:45:28.199> quite<01:45:28.440> useful<01:45:28.739> actually<01:45:28.980> to 01:45:29.629 --> 01:45:29.639 align:start position:0% insightful and quite useful actually to 01:45:29.639 --> 01:45:31.790 align:start position:0% insightful and quite useful actually to see<01:45:29.760> it<01:45:29.880> in<01:45:30.060> that<01:45:30.179> form 01:45:31.790 --> 01:45:31.800 align:start position:0% see it in that form 01:45:31.800 --> 01:45:33.649 align:start position:0% see it in that form good 01:45:33.649 --> 01:45:33.659 align:start position:0% good 01:45:33.659 --> 01:45:36.300 align:start position:0% good thank<01:45:34.199> you<01:45:34.320> very<01:45:34.380> much 01:45:36.300 --> 01:45:36.310 align:start position:0% thank you very much 01:45:36.310 --> 01:45:39.770 align:start position:0% thank you very much [Applause] 01:45:39.770 --> 01:45:39.780 align:start position:0% [Applause] 01:45:39.780 --> 01:45:41.270 align:start position:0% [Applause] questions 01:45:41.270 --> 01:45:41.280 align:start position:0% questions 01:45:41.280 --> 01:45:43.070 align:start position:0% questions yeah 01:45:43.070 --> 01:45:43.080 align:start position:0% yeah 01:45:43.080 --> 01:45:46.370 align:start position:0% yeah or<01:45:43.980> to<01:45:44.159> me<01:45:44.280> or<01:45:44.400> to<01:45:44.520> repeat<01:45:44.760> soon 01:45:46.370 --> 01:45:46.380 align:start position:0% or to me or to repeat soon 01:45:46.380 --> 01:45:55.990 align:start position:0% or to me or to repeat soon maybe<01:45:46.739> you<01:45:46.920> wanna 01:45:55.990 --> 01:45:56.000 align:start position:0% 01:45:56.000 --> 01:45:59.750 align:start position:0% so<01:45:57.000> I'm<01:45:57.360> wondering<01:45:57.900> if<01:45:58.860> we<01:45:59.280> can<01:45:59.400> talk<01:45:59.580> about 01:45:59.750 --> 01:45:59.760 align:start position:0% so I'm wondering if we can talk about 01:45:59.760 --> 01:46:02.570 align:start position:0% so I'm wondering if we can talk about like<01:46:00.420> uh<01:46:00.719> real<01:46:01.080> world<01:46:01.380> attack<01:46:01.860> example<01:46:02.400> and 01:46:02.570 --> 01:46:02.580 align:start position:0% like uh real world attack example and 01:46:02.580 --> 01:46:04.250 align:start position:0% like uh real world attack example and how<01:46:02.820> that<01:46:03.119> would 01:46:04.250 --> 01:46:04.260 align:start position:0% how that would 01:46:04.260 --> 01:46:07.070 align:start position:0% how that would um<01:46:04.380> come<01:46:05.280> into<01:46:05.400> such<01:46:05.820> a<01:46:06.119> system<01:46:06.239> and<01:46:06.780> in 01:46:07.070 --> 01:46:07.080 align:start position:0% um come into such a system and in 01:46:07.080 --> 01:46:09.229 align:start position:0% um come into such a system and in particular<01:46:07.440> I<01:46:07.679> guess<01:46:07.800> on<01:46:08.460> my<01:46:08.639> mind<01:46:08.760> is<01:46:09.000> the 01:46:09.229 --> 01:46:09.239 align:start position:0% particular I guess on my mind is the 01:46:09.239 --> 01:46:11.330 align:start position:0% particular I guess on my mind is the mango<01:46:09.719> attack<01:46:10.380> from<01:46:10.679> a<01:46:10.800> couple<01:46:10.920> days<01:46:11.100> ago 01:46:11.330 --> 01:46:11.340 align:start position:0% mango attack from a couple days ago 01:46:11.340 --> 01:46:13.550 align:start position:0% mango attack from a couple days ago where<01:46:11.880> it<01:46:12.420> was<01:46:12.540> essentially<01:46:12.960> an<01:46:13.139> oracle 01:46:13.550 --> 01:46:13.560 align:start position:0% where it was essentially an oracle 01:46:13.560 --> 01:46:16.790 align:start position:0% where it was essentially an oracle exploit<01:46:14.119> and<01:46:15.119> the 01:46:16.790 --> 01:46:16.800 align:start position:0% exploit and the 01:46:16.800 --> 01:46:21.609 align:start position:0% exploit and the um<01:46:16.860> it<01:46:17.699> seems<01:46:17.940> to<01:46:18.060> me<01:46:18.239> like<01:46:18.719> an<01:46:19.440> orca<01:46:20.040> would<01:46:20.639> be 01:46:21.609 --> 01:46:21.619 align:start position:0% um it seems to me like an orca would be 01:46:21.619 --> 01:46:24.350 align:start position:0% um it seems to me like an orca would be inherently<01:46:22.619> outside<01:46:23.100> of<01:46:23.760> a<01:46:23.940> system<01:46:24.119> that 01:46:24.350 --> 01:46:24.360 align:start position:0% inherently outside of a system that 01:46:24.360 --> 01:46:26.629 align:start position:0% inherently outside of a system that you're<01:46:24.480> modeling<01:46:24.840> this<01:46:25.080> way<01:46:25.199> or<01:46:25.500> is<01:46:25.619> that<01:46:25.800> is 01:46:26.629 --> 01:46:26.639 align:start position:0% you're modeling this way or is that is 01:46:26.639 --> 01:46:29.689 align:start position:0% you're modeling this way or is that is that<01:46:26.820> an<01:46:26.940> incorrect<01:46:27.420> assumption 01:46:29.689 --> 01:46:29.699 align:start position:0% that an incorrect assumption 01:46:29.699 --> 01:46:32.090 align:start position:0% that an incorrect assumption um 01:46:32.090 --> 01:46:32.100 align:start position:0% 01:46:32.100 --> 01:46:34.129 align:start position:0% sorry<01:46:32.639> let<01:46:32.820> me<01:46:32.940> go<01:46:33.060> back<01:46:33.239> go<01:46:33.480> back<01:46:33.600> here<01:46:33.840> just 01:46:34.129 --> 01:46:34.139 align:start position:0% sorry let me go back go back here just 01:46:34.139 --> 01:46:36.950 align:start position:0% sorry let me go back go back here just if<01:46:34.500> you<01:46:34.800> think<01:46:34.920> about<01:46:35.040> no<01:46:35.880> here<01:46:36.239> if<01:46:36.719> you<01:46:36.840> think 01:46:36.950 --> 01:46:36.960 align:start position:0% if you think about no here if you think 01:46:36.960 --> 01:46:38.570 align:start position:0% if you think about no here if you think about<01:46:37.080> this 01:46:38.570 --> 01:46:38.580 align:start position:0% about this 01:46:38.580 --> 01:46:39.109 align:start position:0% about this um 01:46:39.109 --> 01:46:39.119 align:start position:0% um 01:46:39.119 --> 01:46:41.450 align:start position:0% um X<01:46:39.719> doesn't<01:46:40.139> have<01:46:40.380> to<01:46:40.500> come<01:46:40.679> from<01:46:40.920> the<01:46:41.040> in<01:46:41.219> from 01:46:41.450 --> 01:46:41.460 align:start position:0% X doesn't have to come from the in from 01:46:41.460 --> 01:46:42.830 align:start position:0% X doesn't have to come from the in from the<01:46:41.639> world<01:46:41.760> it's<01:46:41.940> from<01:46:42.239> the<01:46:42.360> game<01:46:42.540> itself 01:46:42.830 --> 01:46:42.840 align:start position:0% the world it's from the game itself 01:46:42.840 --> 01:46:44.030 align:start position:0% the world it's from the game itself right<01:46:43.020> it<01:46:43.260> can<01:46:43.380> be<01:46:43.500> something<01:46:43.679> from<01:46:43.920> the 01:46:44.030 --> 01:46:44.040 align:start position:0% right it can be something from the 01:46:44.040 --> 01:46:46.010 align:start position:0% right it can be something from the outside<01:46:44.159> perspective<01:46:44.760> so<01:46:45.239> I<01:46:45.420> can<01:46:45.540> interface 01:46:46.010 --> 01:46:46.020 align:start position:0% outside perspective so I can interface 01:46:46.020 --> 01:46:48.530 align:start position:0% outside perspective so I can interface this<01:46:46.260> that<01:46:46.980> system<01:46:47.280> with<01:46:47.820> something<01:46:48.060> which<01:46:48.360> is 01:46:48.530 --> 01:46:48.540 align:start position:0% this that system with something which is 01:46:48.540 --> 01:46:50.450 align:start position:0% this that system with something which is drawn<01:46:48.960> from<01:46:49.139> an<01:46:49.260> outset<01:46:49.679> could<01:46:50.100> be<01:46:50.219> from<01:46:50.340> a 01:46:50.450 --> 01:46:50.460 align:start position:0% drawn from an outset could be from a 01:46:50.460 --> 01:46:51.410 align:start position:0% drawn from an outset could be from a database<01:46:50.699> or<01:46:50.820> whatever<01:46:50.940> it<01:46:51.119> actually<01:46:51.300> is 01:46:51.410 --> 01:46:51.420 align:start position:0% database or whatever it actually is 01:46:51.420 --> 01:46:53.149 align:start position:0% database or whatever it actually is where<01:46:51.600> it's<01:46:51.719> coming<01:46:51.900> from<01:46:52.080> depending<01:46:52.920> on<01:46:52.980> how 01:46:53.149 --> 01:46:53.159 align:start position:0% where it's coming from depending on how 01:46:53.159 --> 01:46:54.830 align:start position:0% where it's coming from depending on how I<01:46:53.280> deployed<01:46:53.639> this<01:46:53.760> it<01:46:54.179> could<01:46:54.300> be<01:46:54.420> continuously 01:46:54.830 --> 01:46:54.840 align:start position:0% I deployed this it could be continuously 01:46:54.840 --> 01:46:55.970 align:start position:0% I deployed this it could be continuously updated<01:46:55.139> and<01:46:55.260> I'm<01:46:55.380> running<01:46:55.500> that<01:46:55.679> basically 01:46:55.970 --> 01:46:55.980 align:start position:0% updated and I'm running that basically 01:46:55.980 --> 01:46:57.410 align:start position:0% updated and I'm running that basically on<01:46:56.100> a<01:46:56.219> permanent<01:46:56.460> basis<01:46:56.699> so<01:46:56.880> this<01:46:57.000> is<01:46:57.119> this<01:46:57.300> is 01:46:57.410 --> 01:46:57.420 align:start position:0% on a permanent basis so this is this is 01:46:57.420 --> 01:46:59.390 align:start position:0% on a permanent basis so this is this is clearly<01:46:57.719> possible 01:46:59.390 --> 01:46:59.400 align:start position:0% clearly possible 01:46:59.400 --> 01:47:00.169 align:start position:0% clearly possible um 01:47:00.169 --> 01:47:00.179 align:start position:0% um 01:47:00.179 --> 01:47:02.629 align:start position:0% um you<01:47:00.780> can<01:47:00.900> also<01:47:01.139> parameterize<01:47:01.679> games 01:47:02.629 --> 01:47:02.639 align:start position:0% you can also parameterize games 01:47:02.639 --> 01:47:04.850 align:start position:0% you can also parameterize games um I'm<01:47:03.239> not<01:47:03.360> sure<01:47:03.480> you<01:47:03.659> maybe<01:47:04.320> remember<01:47:04.560> this 01:47:04.850 --> 01:47:04.860 align:start position:0% um I'm not sure you maybe remember this 01:47:04.860 --> 01:47:06.229 align:start position:0% um I'm not sure you maybe remember this part<01:47:05.100> I<01:47:05.400> just 01:47:06.229 --> 01:47:06.239 align:start position:0% part I just 01:47:06.239 --> 01:47:08.750 align:start position:0% part I just go<01:47:06.780> there 01:47:08.750 --> 01:47:08.760 align:start position:0% go there 01:47:08.760 --> 01:47:10.370 align:start position:0% go there um<01:47:08.820> if<01:47:09.420> you<01:47:09.540> look<01:47:09.659> something<01:47:09.840> like<01:47:10.080> this<01:47:10.199> one 01:47:10.370 --> 01:47:10.380 align:start position:0% um if you look something like this one 01:47:10.380 --> 01:47:12.410 align:start position:0% um if you look something like this one episode<01:47:10.560> editor<01:47:11.100> attack<01:47:11.280> there<01:47:12.119> are<01:47:12.239> a<01:47:12.360> couple 01:47:12.410 --> 01:47:12.420 align:start position:0% episode editor attack there are a couple 01:47:12.420 --> 01:47:13.370 align:start position:0% episode editor attack there are a couple of<01:47:12.540> parameters<01:47:12.960> which<01:47:13.080> are<01:47:13.260> actually 01:47:13.370 --> 01:47:13.380 align:start position:0% of parameters which are actually 01:47:13.380 --> 01:47:15.050 align:start position:0% of parameters which are actually exogenous<01:47:14.040> they<01:47:14.340> are<01:47:14.460> not<01:47:14.580> part<01:47:14.760> of<01:47:14.940> the 01:47:15.050 --> 01:47:15.060 align:start position:0% exogenous they are not part of the 01:47:15.060 --> 01:47:16.669 align:start position:0% exogenous they are not part of the internal<01:47:15.360> structure<01:47:15.780> I<01:47:16.199> can<01:47:16.320> make<01:47:16.500> them 01:47:16.669 --> 01:47:16.679 align:start position:0% internal structure I can make them 01:47:16.679 --> 01:47:18.890 align:start position:0% internal structure I can make them endogenous<01:47:17.580> querying<01:47:18.239> them<01:47:18.360> but<01:47:18.480> I<01:47:18.600> can<01:47:18.719> also 01:47:18.890 --> 01:47:18.900 align:start position:0% endogenous querying them but I can also 01:47:18.900 --> 01:47:19.850 align:start position:0% endogenous querying them but I can also just<01:47:18.960> say<01:47:19.139> they're<01:47:19.260> coming<01:47:19.440> from<01:47:19.619> the<01:47:19.739> outside 01:47:19.850 --> 01:47:19.860 align:start position:0% just say they're coming from the outside 01:47:19.860 --> 01:47:22.010 align:start position:0% just say they're coming from the outside and<01:47:20.340> I'm<01:47:20.460> fixing<01:47:20.820> them<01:47:21.000> like<01:47:21.480> the<01:47:21.719> names<01:47:21.840> of 01:47:22.010 --> 01:47:22.020 align:start position:0% and I'm fixing them like the names of 01:47:22.020 --> 01:47:24.290 align:start position:0% and I'm fixing them like the names of the<01:47:22.139> players<01:47:22.380> of<01:47:22.560> feedbacks<01:47:23.100> or<01:47:23.400> sorry<01:47:23.880> fees 01:47:24.290 --> 01:47:24.300 align:start position:0% the players of feedbacks or sorry fees 01:47:24.300 --> 01:47:26.870 align:start position:0% the players of feedbacks or sorry fees and<01:47:24.420> Rewards 01:47:26.870 --> 01:47:26.880 align:start position:0% 01:47:26.880 --> 01:47:29.930 align:start position:0% uh<01:47:27.659> can<01:47:27.900> you<01:47:28.139> establish<01:47:28.739> bounds<01:47:29.219> on<01:47:29.760> those 01:47:29.930 --> 01:47:29.940 align:start position:0% uh can you establish bounds on those 01:47:29.940 --> 01:47:31.669 align:start position:0% uh can you establish bounds on those parameters 01:47:31.669 --> 01:47:31.679 align:start position:0% parameters 01:47:31.679 --> 01:47:32.689 align:start position:0% parameters um<01:47:31.800> it<01:47:31.980> depends<01:47:32.159> on<01:47:32.280> what<01:47:32.400> you<01:47:32.460> mean<01:47:32.580> with 01:47:32.689 --> 01:47:32.699 align:start position:0% um it depends on what you mean with 01:47:32.699 --> 01:47:34.189 align:start position:0% um it depends on what you mean with bounce<01:47:32.940> first<01:47:33.179> of<01:47:33.300> all<01:47:33.420> keep<01:47:33.600> in<01:47:33.659> mind<01:47:33.780> that<01:47:33.900> I 01:47:34.189 --> 01:47:34.199 align:start position:0% bounce first of all keep in mind that I 01:47:34.199 --> 01:47:35.810 align:start position:0% bounce first of all keep in mind that I mean<01:47:34.320> they're<01:47:34.860> structured<01:47:35.280> it<01:47:35.460> because<01:47:35.580> they 01:47:35.810 --> 01:47:35.820 align:start position:0% mean they're structured it because they 01:47:35.820 --> 01:47:37.669 align:start position:0% mean they're structured it because they have<01:47:35.940> to<01:47:36.060> be<01:47:36.119> typed<01:47:36.540> right<01:47:37.080> so<01:47:37.320> if<01:47:37.440> they<01:47:37.560> have 01:47:37.669 --> 01:47:37.679 align:start position:0% have to be typed right so if they have 01:47:37.679 --> 01:47:38.990 align:start position:0% have to be typed right so if they have the<01:47:37.739> wrong<01:47:37.860> time<01:47:37.980> they<01:47:38.159> will<01:47:38.340> not<01:47:38.520> will<01:47:38.880> not 01:47:38.990 --> 01:47:39.000 align:start position:0% the wrong time they will not will not 01:47:39.000 --> 01:47:39.950 align:start position:0% the wrong time they will not will not work 01:47:39.950 --> 01:47:39.960 align:start position:0% work 01:47:39.960 --> 01:47:42.050 align:start position:0% work um<01:47:40.080> then<01:47:40.260> I<01:47:40.739> mean<01:47:40.860> what<01:47:41.400> exactly<01:47:41.639> do<01:47:41.820> you<01:47:41.940> mean 01:47:42.050 --> 01:47:42.060 align:start position:0% um then I mean what exactly do you mean 01:47:42.060 --> 01:47:43.790 align:start position:0% um then I mean what exactly do you mean by<01:47:42.179> by<01:47:42.420> bounds<01:47:42.840> in<01:47:42.900> the<01:47:43.020> sense<01:47:43.139> of<01:47:43.260> values<01:47:43.560> or 01:47:43.790 --> 01:47:43.800 align:start position:0% by by bounds in the sense of values or 01:47:43.800 --> 01:47:46.189 align:start position:0% by by bounds in the sense of values or so<01:47:44.340> yeah<01:47:44.460> I<01:47:44.639> don't<01:47:44.699> mean<01:47:44.820> like<01:47:45.060> a<01:47:45.239> type<01:47:45.480> bound<01:47:45.960> I 01:47:46.189 --> 01:47:46.199 align:start position:0% so yeah I don't mean like a type bound I 01:47:46.199 --> 01:47:49.010 align:start position:0% so yeah I don't mean like a type bound I mean<01:47:46.320> uh<01:47:46.920> value<01:47:47.280> bounce 01:47:49.010 --> 01:47:49.020 align:start position:0% mean uh value bounce 01:47:49.020 --> 01:47:50.689 align:start position:0% mean uh value bounce um well<01:47:49.380> again<01:47:49.560> I<01:47:49.800> mean<01:47:49.980> you<01:47:50.460> have 01:47:50.689 --> 01:47:50.699 align:start position:0% um well again I mean you have 01:47:50.699 --> 01:47:51.950 align:start position:0% um well again I mean you have limitations<01:47:51.000> in<01:47:51.239> a<01:47:51.360> sense<01:47:51.480> if<01:47:51.600> you're<01:47:51.780> working 01:47:51.950 --> 01:47:51.960 align:start position:0% limitations in a sense if you're working 01:47:51.960 --> 01:47:53.209 align:start position:0% limitations in a sense if you're working with<01:47:52.139> an<01:47:52.199> escrow<01:47:52.619> world<01:47:52.739> you<01:47:52.920> clearly<01:47:53.159> have 01:47:53.209 --> 01:47:53.219 align:start position:0% with an escrow world you clearly have 01:47:53.219 --> 01:47:54.590 align:start position:0% with an escrow world you clearly have boundaries<01:47:53.639> for<01:47:53.820> certain<01:47:54.000> types<01:47:54.300> that<01:47:54.420> you 01:47:54.590 --> 01:47:54.600 align:start position:0% boundaries for certain types that you 01:47:54.600 --> 01:47:56.030 align:start position:0% boundaries for certain types that you can<01:47:54.719> use 01:47:56.030 --> 01:47:56.040 align:start position:0% can use 01:47:56.040 --> 01:47:57.290 align:start position:0% can use um<01:47:56.100> there<01:47:56.400> are<01:47:56.520> also<01:47:56.760> of<01:47:56.880> course<01:47:57.000> the<01:47:57.119> question 01:47:57.290 --> 01:47:57.300 align:start position:0% um there are also of course the question 01:47:57.300 --> 01:47:58.850 align:start position:0% um there are also of course the question of<01:47:57.540> the<01:47:57.600> computational<01:47:57.960> complexity<01:47:58.500> at<01:47:58.739> some 01:47:58.850 --> 01:47:58.860 align:start position:0% of the computational complexity at some 01:47:58.860 --> 01:48:00.169 align:start position:0% of the computational complexity at some point<01:47:58.980> right 01:48:00.169 --> 01:48:00.179 align:start position:0% point right 01:48:00.179 --> 01:48:01.310 align:start position:0% point right um I<01:48:00.360> haven't<01:48:00.480> talked<01:48:00.719> about<01:48:00.840> this<01:48:01.080> because 01:48:01.310 --> 01:48:01.320 align:start position:0% um I haven't talked about this because 01:48:01.320 --> 01:48:03.590 align:start position:0% um I haven't talked about this because this<01:48:01.560> is<01:48:01.679> also<01:48:01.980> part<01:48:02.159> of<01:48:02.280> active<01:48:02.580> research 01:48:03.590 --> 01:48:03.600 align:start position:0% this is also part of active research 01:48:03.600 --> 01:48:05.390 align:start position:0% this is also part of active research um so<01:48:03.900> far<01:48:04.080> I'm<01:48:04.500> using<01:48:04.739> compositionality 01:48:05.390 --> 01:48:05.400 align:start position:0% um so far I'm using compositionality 01:48:05.400 --> 01:48:07.070 align:start position:0% um so far I'm using compositionality exclusively<01:48:06.000> on<01:48:06.179> the<01:48:06.300> level<01:48:06.360> of<01:48:06.600> composing 01:48:07.070 --> 01:48:07.080 align:start position:0% exclusively on the level of composing 01:48:07.080 --> 01:48:09.950 align:start position:0% exclusively on the level of composing the<01:48:07.320> representation 01:48:09.950 --> 01:48:09.960 align:start position:0% 01:48:09.960 --> 01:48:11.930 align:start position:0% there<01:48:10.440> are<01:48:10.619> results<01:48:10.920> that<01:48:11.280> show<01:48:11.460> that<01:48:11.699> you 01:48:11.930 --> 01:48:11.940 align:start position:0% there are results that show that you 01:48:11.940 --> 01:48:14.450 align:start position:0% there are results that show that you know<01:48:12.060> Computing<01:48:12.420> equilibrium<01:48:13.020> is<01:48:13.380> very<01:48:13.739> hard 01:48:14.450 --> 01:48:14.460 align:start position:0% know Computing equilibrium is very hard 01:48:14.460 --> 01:48:15.649 align:start position:0% know Computing equilibrium is very hard um<01:48:14.580> and<01:48:14.760> we<01:48:14.880> will<01:48:15.000> not<01:48:15.119> break<01:48:15.239> these<01:48:15.540> results 01:48:15.649 --> 01:48:15.659 align:start position:0% um and we will not break these results 01:48:15.659 --> 01:48:18.169 align:start position:0% um and we will not break these results but<01:48:16.440> in<01:48:16.860> the<01:48:16.980> practice<01:48:17.159> of<01:48:17.639> actually 01:48:18.169 --> 01:48:18.179 align:start position:0% but in the practice of actually 01:48:18.179 --> 01:48:21.350 align:start position:0% but in the practice of actually Computing<01:48:18.659> concrete<01:48:19.020> concrete<01:48:19.739> games 01:48:21.350 --> 01:48:21.360 align:start position:0% Computing concrete concrete games 01:48:21.360 --> 01:48:22.790 align:start position:0% Computing concrete concrete games um<01:48:21.420> you<01:48:21.600> might<01:48:21.719> be<01:48:21.840> able<01:48:22.020> to<01:48:22.139> leverage<01:48:22.380> also 01:48:22.790 --> 01:48:22.800 align:start position:0% um you might be able to leverage also 01:48:22.800 --> 01:48:25.370 align:start position:0% um you might be able to leverage also the<01:48:22.920> compositionality<01:48:23.639> right<01:48:24.000> because 01:48:25.370 --> 01:48:25.380 align:start position:0% the compositionality right because 01:48:25.380 --> 01:48:27.050 align:start position:0% the compositionality right because some<01:48:25.800> components<01:48:26.280> here<01:48:26.340> might<01:48:26.580> be<01:48:26.699> computed 01:48:27.050 --> 01:48:27.060 align:start position:0% some components here might be computed 01:48:27.060 --> 01:48:28.490 align:start position:0% some components here might be computed but<01:48:27.239> it<01:48:27.300> might<01:48:27.420> be<01:48:27.540> independent<01:48:27.900> of<01:48:28.020> that<01:48:28.199> and 01:48:28.490 --> 01:48:28.500 align:start position:0% but it might be independent of that and 01:48:28.500 --> 01:48:30.350 align:start position:0% but it might be independent of that and then<01:48:28.560> you<01:48:28.739> can<01:48:28.800> compute<01:48:29.159> or 01:48:30.350 --> 01:48:30.360 align:start position:0% then you can compute or 01:48:30.360 --> 01:48:31.729 align:start position:0% then you can compute or um<01:48:30.420> some<01:48:30.600> compute<01:48:31.020> some<01:48:31.199> component<01:48:31.560> here 01:48:31.729 --> 01:48:31.739 align:start position:0% um some compute some component here 01:48:31.739 --> 01:48:33.109 align:start position:0% um some compute some component here might<01:48:31.920> compute<01:48:32.280> but<01:48:32.400> it<01:48:32.520> will<01:48:32.639> only<01:48:32.820> affect 01:48:33.109 --> 01:48:33.119 align:start position:0% might compute but it will only affect 01:48:33.119 --> 01:48:37.810 align:start position:0% might compute but it will only affect another<01:48:33.300> component 01:48:37.810 --> 01:48:37.820 align:start position:0% 01:48:37.820 --> 01:48:41.209 align:start position:0% another<01:48:38.820> thing<01:48:39.179> to<01:48:39.360> keep<01:48:39.540> in<01:48:39.719> mind<01:48:39.900> is<01:48:40.199> that<01:48:40.500> as 01:48:41.209 --> 01:48:41.219 align:start position:0% another thing to keep in mind is that as 01:48:41.219 --> 01:48:43.070 align:start position:0% another thing to keep in mind is that as Philip<01:48:41.580> said 01:48:43.070 --> 01:48:43.080 align:start position:0% Philip said 01:48:43.080 --> 01:48:46.189 align:start position:0% Philip said um<01:48:43.139> you<01:48:43.739> can<01:48:43.860> have<01:48:44.100> that<01:48:44.460> a<01:48:44.820> game<01:48:45.000> can<01:48:45.840> you<01:48:46.139> know 01:48:46.189 --> 01:48:46.199 align:start position:0% um you can have that a game can you know 01:48:46.199 --> 01:48:48.470 align:start position:0% um you can have that a game can you know just<01:48:46.440> have<01:48:46.679> a<01:48:46.860> function<01:48:47.159> as<01:48:47.400> internals<01:48:47.940> or<01:48:48.300> it 01:48:48.470 --> 01:48:48.480 align:start position:0% just have a function as internals or it 01:48:48.480 --> 01:48:50.629 align:start position:0% just have a function as internals or it can<01:48:48.659> have<01:48:48.840> you<01:48:49.320> know<01:48:49.440> strategies 01:48:50.629 --> 01:48:50.639 align:start position:0% can have you know strategies 01:48:50.639 --> 01:48:53.390 align:start position:0% can have you know strategies so<01:48:51.239> in<01:48:51.780> the<01:48:51.900> case<01:48:51.960> of<01:48:52.139> an<01:48:52.260> oracle<01:48:52.679> you<01:48:53.280> can 01:48:53.390 --> 01:48:53.400 align:start position:0% so in the case of an oracle you can 01:48:53.400 --> 01:48:55.550 align:start position:0% so in the case of an oracle you can either<01:48:53.820> treat<01:48:54.300> it<01:48:54.540> as<01:48:54.719> a<01:48:54.900> parameter<01:48:55.320> that 01:48:55.550 --> 01:48:55.560 align:start position:0% either treat it as a parameter that 01:48:55.560 --> 01:48:56.990 align:start position:0% either treat it as a parameter that basically<01:48:55.920> comes<01:48:56.159> from<01:48:56.280> the<01:48:56.460> outside<01:48:56.580> world 01:48:56.990 --> 01:48:57.000 align:start position:0% basically comes from the outside world 01:48:57.000 --> 01:48:59.750 align:start position:0% basically comes from the outside world or<01:48:57.659> you<01:48:57.840> can<01:48:57.900> model<01:48:58.139> it<01:48:58.380> as<01:48:58.800> a<01:48:59.100> stupid<01:48:59.340> function 01:48:59.750 --> 01:48:59.760 align:start position:0% or you can model it as a stupid function 01:48:59.760 --> 01:49:02.270 align:start position:0% or you can model it as a stupid function that<01:49:00.000> has<01:49:00.179> no<01:49:00.420> agency<01:49:00.780> whatsoever<01:49:01.320> or<01:49:01.980> you<01:49:02.159> can 01:49:02.270 --> 01:49:02.280 align:start position:0% that has no agency whatsoever or you can 01:49:02.280 --> 01:49:05.570 align:start position:0% that has no agency whatsoever or you can model<01:49:02.460> it<01:49:02.760> as<01:49:03.179> I<01:49:03.659> don't<01:49:03.780> know<01:49:03.900> a<01:49:04.440> protocol<01:49:05.280> that 01:49:05.570 --> 01:49:05.580 align:start position:0% model it as I don't know a protocol that 01:49:05.580 --> 01:49:07.550 align:start position:0% model it as I don't know a protocol that has<01:49:05.820> its<01:49:06.119> own<01:49:06.179> set<01:49:06.420> of<01:49:06.540> economic<01:49:07.020> incentives 01:49:07.550 --> 01:49:07.560 align:start position:0% has its own set of economic incentives 01:49:07.560 --> 01:49:10.070 align:start position:0% has its own set of economic incentives to<01:49:08.460> work<01:49:08.639> in<01:49:08.820> the<01:49:09.000> right<01:49:09.060> way<01:49:09.239> I<01:49:09.719> guess<01:49:09.840> that 01:49:10.070 --> 01:49:10.080 align:start position:0% to work in the right way I guess that 01:49:10.080 --> 01:49:11.209 align:start position:0% to work in the right way I guess that would<01:49:10.199> be<01:49:10.320> the<01:49:10.560> case<01:49:10.679> of<01:49:10.860> like<01:49:11.040> the 01:49:11.209 --> 01:49:11.219 align:start position:0% would be the case of like the 01:49:11.219 --> 01:49:12.830 align:start position:0% would be the case of like the centralized<01:49:11.699> oracles<01:49:12.179> where<01:49:12.540> you<01:49:12.719> know 01:49:12.830 --> 01:49:12.840 align:start position:0% centralized oracles where you know 01:49:12.840 --> 01:49:15.169 align:start position:0% centralized oracles where you know people<01:49:13.440> are<01:49:13.679> incentivated<01:49:14.219> to<01:49:14.460> not<01:49:14.699> to<01:49:14.880> lie 01:49:15.169 --> 01:49:15.179 align:start position:0% people are incentivated to not to lie 01:49:15.179 --> 01:49:17.390 align:start position:0% people are incentivated to not to lie and<01:49:15.239> whatever<01:49:15.560> the<01:49:16.560> cool<01:49:16.739> thing<01:49:16.920> about<01:49:17.100> this 01:49:17.390 --> 01:49:17.400 align:start position:0% and whatever the cool thing about this 01:49:17.400 --> 01:49:20.510 align:start position:0% and whatever the cool thing about this is<01:49:17.699> that<01:49:17.940> then<01:49:18.480> you<01:49:18.719> can<01:49:18.840> start<01:49:19.139> from<01:49:19.800> a 01:49:20.510 --> 01:49:20.520 align:start position:0% is that then you can start from a 01:49:20.520 --> 01:49:24.290 align:start position:0% is that then you can start from a scenario<01:49:21.440> where<01:49:22.440> the<01:49:22.800> Oracle<01:49:23.280> is<01:49:23.520> honest<01:49:23.880> the 01:49:24.290 --> 01:49:24.300 align:start position:0% scenario where the Oracle is honest the 01:49:24.300 --> 01:49:25.910 align:start position:0% scenario where the Oracle is honest the the<01:49:24.540> very<01:49:24.840> cool<01:49:25.139> thing<01:49:25.380> that<01:49:25.619> practice 01:49:25.910 --> 01:49:25.920 align:start position:0% the very cool thing that practice 01:49:25.920 --> 01:49:28.450 align:start position:0% the very cool thing that practice teaches<01:49:26.880> us<01:49:27.000> is<01:49:27.239> that<01:49:27.360> usually<01:49:27.719> when<01:49:28.080> people 01:49:28.450 --> 01:49:28.460 align:start position:0% teaches us is that usually when people 01:49:28.460 --> 01:49:32.030 align:start position:0% teaches us is that usually when people design<01:49:29.460> a<01:49:30.119> protocol<01:49:30.420> they<01:49:31.199> have<01:49:31.380> already<01:49:31.560> an 01:49:32.030 --> 01:49:32.040 align:start position:0% design a protocol they have already an 01:49:32.040 --> 01:49:34.310 align:start position:0% design a protocol they have already an intuitive<01:49:32.460> notion<01:49:33.000> of<01:49:33.480> what<01:49:33.960> is<01:49:34.139> the 01:49:34.310 --> 01:49:34.320 align:start position:0% intuitive notion of what is the 01:49:34.320 --> 01:49:37.070 align:start position:0% intuitive notion of what is the equilibrium<01:49:34.980> where<01:49:35.460> everyone<01:49:35.699> is<01:49:36.000> honest<01:49:36.360> so 01:49:37.070 --> 01:49:37.080 align:start position:0% equilibrium where everyone is honest so 01:49:37.080 --> 01:49:38.570 align:start position:0% equilibrium where everyone is honest so you<01:49:37.199> say<01:49:37.380> okay<01:49:37.500> you<01:49:37.860> test<01:49:38.040> that<01:49:38.280> you<01:49:38.400> have<01:49:38.460> an 01:49:38.570 --> 01:49:38.580 align:start position:0% you say okay you test that you have an 01:49:38.580 --> 01:49:40.250 align:start position:0% you say okay you test that you have an equilibrium<01:49:39.060> and<01:49:39.480> now<01:49:39.719> you<01:49:39.840> can<01:49:40.020> basically 01:49:40.250 --> 01:49:40.260 align:start position:0% equilibrium and now you can basically 01:49:40.260 --> 01:49:42.050 align:start position:0% equilibrium and now you can basically start<01:49:40.500> bribing<01:49:41.040> the<01:49:41.159> Oracle<01:49:41.520> so<01:49:41.699> you<01:49:41.940> can 01:49:42.050 --> 01:49:42.060 align:start position:0% start bribing the Oracle so you can 01:49:42.060 --> 01:49:45.169 align:start position:0% start bribing the Oracle so you can start<01:49:42.360> basically<01:49:43.020> you<01:49:43.800> know<01:49:44.179> adding 01:49:45.169 --> 01:49:45.179 align:start position:0% start basically you know adding 01:49:45.179 --> 01:49:48.109 align:start position:0% start basically you know adding incentives<01:49:46.139> to<01:49:46.440> the<01:49:46.560> Oracle<01:49:46.920> to<01:49:47.159> lie 01:49:48.109 --> 01:49:48.119 align:start position:0% incentives to the Oracle to lie 01:49:48.119 --> 01:49:51.410 align:start position:0% incentives to the Oracle to lie and<01:49:49.020> one<01:49:49.260> thing<01:49:49.380> that<01:49:49.560> you<01:49:49.800> can<01:49:49.980> do<01:49:50.940> very 01:49:51.410 --> 01:49:51.420 align:start position:0% and one thing that you can do very 01:49:51.420 --> 01:49:54.530 align:start position:0% and one thing that you can do very efficiently<01:49:51.960> computationally<01:49:52.739> is<01:49:53.520> finding<01:49:54.300> a 01:49:54.530 --> 01:49:54.540 align:start position:0% efficiently computationally is finding a 01:49:54.540 --> 01:49:56.689 align:start position:0% efficiently computationally is finding a bound<01:49:54.719> that<01:49:55.619> is<01:49:55.739> basically<01:49:56.040> the<01:49:56.280> cost<01:49:56.460> of 01:49:56.689 --> 01:49:56.699 align:start position:0% bound that is basically the cost of 01:49:56.699 --> 01:49:58.729 align:start position:0% bound that is basically the cost of breaking<01:49:57.060> your<01:49:57.179> equilibrium<01:49:57.780> so<01:49:58.199> say<01:49:58.500> how 01:49:58.729 --> 01:49:58.739 align:start position:0% breaking your equilibrium so say how 01:49:58.739 --> 01:50:01.129 align:start position:0% breaking your equilibrium so say how much<01:49:58.860> do<01:49:59.040> I<01:49:59.159> have<01:49:59.280> to<01:49:59.460> bribe<01:49:59.940> the<01:50:00.420> Oracle<01:50:00.840> to 01:50:01.129 --> 01:50:01.139 align:start position:0% much do I have to bribe the Oracle to 01:50:01.139 --> 01:50:02.750 align:start position:0% much do I have to bribe the Oracle to break<01:50:01.260> the<01:50:01.500> equilibrium<01:50:01.860> and<01:50:02.040> then<01:50:02.219> this<01:50:02.639> is 01:50:02.750 --> 01:50:02.760 align:start position:0% break the equilibrium and then this is 01:50:02.760 --> 01:50:04.910 align:start position:0% break the equilibrium and then this is super<01:50:02.940> useful<01:50:03.300> because<01:50:03.540> now<01:50:03.840> you<01:50:04.199> can<01:50:04.320> find 01:50:04.910 --> 01:50:04.920 align:start position:0% super useful because now you can find 01:50:04.920 --> 01:50:06.229 align:start position:0% super useful because now you can find parameters 01:50:06.229 --> 01:50:06.239 align:start position:0% parameters 01:50:06.239 --> 01:50:08.209 align:start position:0% parameters and<01:50:06.960> and<01:50:07.139> you<01:50:07.380> know<01:50:07.500> since<01:50:07.679> you<01:50:07.920> are<01:50:08.040> starting 01:50:08.209 --> 01:50:08.219 align:start position:0% and and you know since you are starting 01:50:08.219 --> 01:50:10.010 align:start position:0% and and you know since you are starting from<01:50:08.460> equilibrium<01:50:09.179> that<01:50:09.420> you<01:50:09.600> already<01:50:09.719> knew 01:50:10.010 --> 01:50:10.020 align:start position:0% from equilibrium that you already knew 01:50:10.020 --> 01:50:11.570 align:start position:0% from equilibrium that you already knew you<01:50:10.199> don't<01:50:10.320> have<01:50:10.500> to<01:50:10.619> do<01:50:10.739> equilibrium<01:50:11.280> search 01:50:11.570 --> 01:50:11.580 align:start position:0% you don't have to do equilibrium search 01:50:11.580 --> 01:50:13.910 align:start position:0% you don't have to do equilibrium search it's<01:50:12.420> just<01:50:12.600> equilibrium<01:50:13.199> checking<01:50:13.619> you<01:50:13.739> just 01:50:13.910 --> 01:50:13.920 align:start position:0% it's just equilibrium checking you just 01:50:13.920 --> 01:50:16.189 align:start position:0% it's just equilibrium checking you just like<01:50:14.159> linearly<01:50:14.760> increment<01:50:15.480> this<01:50:15.719> parameter 01:50:16.189 --> 01:50:16.199 align:start position:0% like linearly increment this parameter 01:50:16.199 --> 01:50:18.830 align:start position:0% like linearly increment this parameter and<01:50:16.320> it's<01:50:16.440> okay<01:50:16.619> this<01:50:17.400> is<01:50:17.580> how<01:50:18.300> much<01:50:18.480> we<01:50:18.719> are 01:50:18.830 --> 01:50:18.840 align:start position:0% and it's okay this is how much we are 01:50:18.840 --> 01:50:21.649 align:start position:0% and it's okay this is how much we are protected<01:50:19.320> and<01:50:20.219> and<01:50:20.639> then<01:50:20.940> yeah<01:50:21.119> that<01:50:21.480> that 01:50:21.649 --> 01:50:21.659 align:start position:0% protected and and then yeah that that 01:50:21.659 --> 01:50:23.689 align:start position:0% protected and and then yeah that that would<01:50:21.960> be<01:50:22.199> a<01:50:22.440> sort<01:50:22.619> of<01:50:22.800> bound<01:50:22.980> between<01:50:23.340> your 01:50:23.689 --> 01:50:23.699 align:start position:0% would be a sort of bound between your 01:50:23.699 --> 01:50:26.450 align:start position:0% would be a sort of bound between your model<01:50:23.940> how<01:50:24.360> expensive<01:50:24.840> would<01:50:25.139> be<01:50:25.320> to<01:50:26.280> it 01:50:26.450 --> 01:50:26.460 align:start position:0% model how expensive would be to it 01:50:26.460 --> 01:50:29.570 align:start position:0% model how expensive would be to it up<01:50:26.580> basically 01:50:29.570 --> 01:50:29.580 align:start position:0% 01:50:29.580 --> 01:50:31.729 align:start position:0% oh<01:50:30.179> hi<01:50:30.659> um<01:50:30.659> I<01:50:30.840> have<01:50:30.960> a<01:50:31.080> few<01:50:31.139> questions<01:50:31.380> because 01:50:31.729 --> 01:50:31.739 align:start position:0% oh hi um I have a few questions because 01:50:31.739 --> 01:50:33.410 align:start position:0% oh hi um I have a few questions because I've<01:50:32.040> been<01:50:32.219> really<01:50:32.340> listening<01:50:32.760> so<01:50:33.000> intently 01:50:33.410 --> 01:50:33.420 align:start position:0% I've been really listening so intently 01:50:33.420 --> 01:50:34.729 align:start position:0% I've been really listening so intently and<01:50:33.540> I've<01:50:33.659> written<01:50:33.840> some<01:50:34.080> things<01:50:34.260> down<01:50:34.440> so 01:50:34.729 --> 01:50:34.739 align:start position:0% and I've written some things down so 01:50:34.739 --> 01:50:35.930 align:start position:0% and I've written some things down so it's<01:50:34.980> okay 01:50:35.930 --> 01:50:35.940 align:start position:0% it's okay 01:50:35.940 --> 01:50:37.729 align:start position:0% it's okay um the<01:50:36.239> first<01:50:36.360> one<01:50:36.540> was<01:50:37.139> um<01:50:37.139> you<01:50:37.440> know<01:50:37.500> could 01:50:37.729 --> 01:50:37.739 align:start position:0% um the first one was um you know could 01:50:37.739 --> 01:50:40.129 align:start position:0% um the first one was um you know could you<01:50:37.920> perhaps<01:50:38.280> optimize<01:50:38.880> the<01:50:39.060> compiler<01:50:39.600> by 01:50:40.129 --> 01:50:40.139 align:start position:0% you perhaps optimize the compiler by 01:50:40.139 --> 01:50:41.930 align:start position:0% you perhaps optimize the compiler by modeling<01:50:40.679> like<01:50:40.860> modeling<01:50:41.159> it<01:50:41.340> with<01:50:41.520> category 01:50:41.930 --> 01:50:41.940 align:start position:0% modeling like modeling it with category 01:50:41.940 --> 01:50:49.609 align:start position:0% modeling like modeling it with category Theory<01:50:42.300> and<01:50:42.480> with<01:50:42.659> your<01:50:42.840> tools 01:50:49.609 --> 01:50:49.619 align:start position:0% 01:50:49.619 --> 01:50:51.470 align:start position:0% oh<01:50:50.159> sorry<01:50:50.400> was<01:50:50.760> that<01:50:50.940> kind<01:50:51.119> of<01:50:51.239> hard<01:50:51.300> to 01:50:51.470 --> 01:50:51.480 align:start position:0% oh sorry was that kind of hard to 01:50:51.480 --> 01:50:52.070 align:start position:0% oh sorry was that kind of hard to understand 01:50:52.070 --> 01:50:52.080 align:start position:0% understand 01:50:52.080 --> 01:50:52.970 align:start position:0% understand um 01:50:52.970 --> 01:50:52.980 align:start position:0% um 01:50:52.980 --> 01:50:56.030 align:start position:0% um could<01:50:53.400> you<01:50:53.580> perhaps<01:50:54.119> Model<01:50:54.600> A<01:50:55.080> compiler<01:50:55.679> and 01:50:56.030 --> 01:50:56.040 align:start position:0% could you perhaps Model A compiler and 01:50:56.040 --> 01:50:59.270 align:start position:0% could you perhaps Model A compiler and optimize<01:50:56.580> a<01:50:57.000> compiler<01:50:57.540> using<01:50:58.320> your<01:50:58.500> tools<01:50:58.980> and 01:50:59.270 --> 01:50:59.280 align:start position:0% optimize a compiler using your tools and 01:50:59.280 --> 01:51:01.250 align:start position:0% optimize a compiler using your tools and with<01:50:59.460> category<01:50:59.940> Theory 01:51:01.250 --> 01:51:01.260 align:start position:0% with category Theory 01:51:01.260 --> 01:51:04.310 align:start position:0% with category Theory okay<01:51:02.340> um<01:51:02.659> they're<01:51:03.659> actually<01:51:03.840> doing<01:51:04.020> people 01:51:04.310 --> 01:51:04.320 align:start position:0% okay um they're actually doing people 01:51:04.320 --> 01:51:06.410 align:start position:0% okay um they're actually doing people doing<01:51:04.500> this<01:51:04.739> here<01:51:04.980> uh<01:51:05.460> I<01:51:05.699> think<01:51:05.760> at<01:51:06.119> least<01:51:06.239> at 01:51:06.410 --> 01:51:06.420 align:start position:0% doing this here uh I think at least at 01:51:06.420 --> 01:51:08.090 align:start position:0% doing this here uh I think at least at least<01:51:06.600> trying<01:51:06.840> but<01:51:07.260> honestly<01:51:07.619> this<01:51:07.980> is 01:51:08.090 --> 01:51:08.100 align:start position:0% least trying but honestly this is 01:51:08.100 --> 01:51:10.070 align:start position:0% least trying but honestly this is definitely<01:51:08.400> the<01:51:08.520> outset<01:51:08.880> of<01:51:09.000> my<01:51:09.119> expertise<01:51:09.840> I 01:51:10.070 --> 01:51:10.080 align:start position:0% definitely the outset of my expertise I 01:51:10.080 --> 01:51:11.689 align:start position:0% definitely the outset of my expertise I can't<01:51:10.199> say<01:51:10.380> that 01:51:11.689 --> 01:51:11.699 align:start position:0% can't say that 01:51:11.699 --> 01:51:14.090 align:start position:0% can't say that you<01:51:11.760> rechecked<01:51:12.540> the<01:51:12.659> research<01:51:13.139> of<01:51:13.440> uh<01:51:13.739> these 01:51:14.090 --> 01:51:14.100 align:start position:0% you rechecked the research of uh these 01:51:14.100 --> 01:51:16.430 align:start position:0% you rechecked the research of uh these professors<01:51:14.460> called<01:51:14.699> dangika<01:51:15.659> that<01:51:15.960> is<01:51:16.080> using 01:51:16.430 --> 01:51:16.440 align:start position:0% professors called dangika that is using 01:51:16.440 --> 01:51:18.169 align:start position:0% professors called dangika that is using category<01:51:16.920> Theory<01:51:17.280> to<01:51:17.520> do<01:51:17.639> compiler 01:51:18.169 --> 01:51:18.179 align:start position:0% category Theory to do compiler 01:51:18.179 --> 01:51:21.410 align:start position:0% category Theory to do compiler optimization<01:51:18.980> uh<01:51:19.980> so<01:51:20.280> yeah<01:51:20.880> that<01:51:21.119> would<01:51:21.300> be 01:51:21.410 --> 01:51:21.420 align:start position:0% optimization uh so yeah that would be 01:51:21.420 --> 01:51:23.450 align:start position:0% optimization uh so yeah that would be probably<01:51:21.659> the<01:51:21.900> closest<01:51:22.080> thing<01:51:22.440> okay<01:51:22.980> and 01:51:23.450 --> 01:51:23.460 align:start position:0% probably the closest thing okay and 01:51:23.460 --> 01:51:25.129 align:start position:0% probably the closest thing okay and that's<01:51:23.639> exactly<01:51:24.000> where<01:51:24.179> my<01:51:24.420> knowledge<01:51:24.780> of<01:51:24.960> it 01:51:25.129 --> 01:51:25.139 align:start position:0% that's exactly where my knowledge of it 01:51:25.139 --> 01:51:27.890 align:start position:0% that's exactly where my knowledge of it and<01:51:26.100> it's 01:51:27.890 --> 01:51:27.900 align:start position:0% and it's 01:51:27.900 --> 01:51:30.050 align:start position:0% and it's thanks<01:51:28.739> um<01:51:28.739> and<01:51:28.920> then<01:51:29.100> another<01:51:29.280> question<01:51:29.639> and 01:51:30.050 --> 01:51:30.060 align:start position:0% thanks um and then another question and 01:51:30.060 --> 01:51:31.669 align:start position:0% thanks um and then another question and I'm<01:51:30.239> going<01:51:30.360> to<01:51:30.420> speed<01:51:30.540> run<01:51:30.780> it<01:51:31.020> so<01:51:31.139> nobody<01:51:31.440> gets 01:51:31.669 --> 01:51:31.679 align:start position:0% I'm going to speed run it so nobody gets 01:51:31.679 --> 01:51:33.709 align:start position:0% I'm going to speed run it so nobody gets offended<01:51:32.040> that<01:51:32.159> we're<01:51:32.280> taking<01:51:32.460> a<01:51:32.639> long<01:51:32.760> time 01:51:33.709 --> 01:51:33.719 align:start position:0% offended that we're taking a long time 01:51:33.719 --> 01:51:35.810 align:start position:0% offended that we're taking a long time um<01:51:33.780> could<01:51:34.020> you<01:51:34.199> model<01:51:34.440> uh<01:51:34.920> perhaps<01:51:35.280> an 01:51:35.810 --> 01:51:35.820 align:start position:0% um could you model uh perhaps an 01:51:35.820 --> 01:51:37.729 align:start position:0% um could you model uh perhaps an iterated<01:51:36.300> prisoners<01:51:36.900> dilemma<01:51:37.320> with<01:51:37.560> a 01:51:37.729 --> 01:51:37.739 align:start position:0% iterated prisoners dilemma with a 01:51:37.739 --> 01:51:39.470 align:start position:0% iterated prisoners dilemma with a variable<01:51:37.920> number<01:51:38.159> of<01:51:38.340> agents<01:51:38.880> and<01:51:39.060> rounds 01:51:39.470 --> 01:51:39.480 align:start position:0% variable number of agents and rounds 01:51:39.480 --> 01:51:41.270 align:start position:0% variable number of agents and rounds yeah<01:51:39.960> beautiful 01:51:41.270 --> 01:51:41.280 align:start position:0% yeah beautiful 01:51:41.280 --> 01:51:43.790 align:start position:0% yeah beautiful very<01:51:41.880> cool<01:51:42.119> and<01:51:42.960> um<01:51:42.960> will<01:51:43.260> you<01:51:43.440> ever<01:51:43.560> release 01:51:43.790 --> 01:51:43.800 align:start position:0% very cool and um will you ever release 01:51:43.800 --> 01:51:46.490 align:start position:0% very cool and um will you ever release uh<01:51:44.159> like<01:51:44.340> a<01:51:44.520> function<01:51:45.060> annotated<01:51:45.900> sort<01:51:46.440> of 01:51:46.490 --> 01:51:46.500 align:start position:0% uh like a function annotated sort of 01:51:46.500 --> 01:51:47.990 align:start position:0% uh like a function annotated sort of preprocessor<01:51:47.219> language<01:51:47.460> that's<01:51:47.760> maybe 01:51:47.990 --> 01:51:48.000 align:start position:0% preprocessor language that's maybe 01:51:48.000 --> 01:51:49.790 align:start position:0% preprocessor language that's maybe syntax<01:51:48.480> agnostic<01:51:49.080> or<01:51:49.260> something<01:51:49.440> that<01:51:49.619> you 01:51:49.790 --> 01:51:49.800 align:start position:0% syntax agnostic or something that you 01:51:49.800 --> 01:51:51.649 align:start position:0% syntax agnostic or something that you could<01:51:49.920> add<01:51:50.400> into<01:51:50.580> other<01:51:50.820> code<01:51:51.060> bases<01:51:51.480> that 01:51:51.649 --> 01:51:51.659 align:start position:0% could add into other code bases that 01:51:51.659 --> 01:51:53.870 align:start position:0% could add into other code bases that aren't<01:51:51.840> quite<01:51:52.380> High<01:51:52.560> School<01:51:52.739> based<01:51:53.159> in<01:51:53.639> the 01:51:53.870 --> 01:51:53.880 align:start position:0% aren't quite High School based in the 01:51:53.880 --> 01:51:55.070 align:start position:0% aren't quite High School based in the future 01:51:55.070 --> 01:51:55.080 align:start position:0% future 01:51:55.080 --> 01:51:59.390 align:start position:0% future maybe<01:51:55.619> very<01:51:56.520> cool<01:51:56.820> okay 01:51:59.390 --> 01:51:59.400 align:start position:0% 01:51:59.400 --> 01:52:02.119 align:start position:0% thanks<01:51:59.820> for<01:51:59.940> coming