WEBVTT Kind: captions Language: en 00:00:05.150 --> 00:00:11.350 align:start position:0% [Music] 00:00:11.350 --> 00:00:11.360 align:start position:0% 00:00:11.360 --> 00:00:15.700 align:start position:0% so<00:00:12.360> first<00:00:12.840> of<00:00:12.990> all<00:00:13.080> I<00:00:13.290> want<00:00:13.530> to<00:00:13.830> thank<00:00:14.150> theorem 00:00:15.700 --> 00:00:15.710 align:start position:0% so first of all I want to thank theorem 00:00:15.710 --> 00:00:18.080 align:start position:0% so first of all I want to thank theorem for<00:00:16.710> inviting<00:00:17.160> us<00:00:17.340> how<00:00:17.460> this<00:00:17.609> is<00:00:17.730> a<00:00:17.760> third<00:00:18.060> year 00:00:18.080 --> 00:00:18.090 align:start position:0% for inviting us how this is a third year 00:00:18.090 --> 00:00:20.120 align:start position:0% for inviting us how this is a third year that<00:00:18.390> I've<00:00:19.020> been<00:00:19.050> speaking<00:00:19.350> at<00:00:19.619> the<00:00:19.710> etherium 00:00:20.120 --> 00:00:20.130 align:start position:0% that I've been speaking at the etherium 00:00:20.130 --> 00:00:23.830 align:start position:0% that I've been speaking at the etherium DEFCON<00:00:20.910> and<00:00:21.119> I<00:00:21.750> think<00:00:22.350> it's<00:00:22.580> remarkably 00:00:23.830 --> 00:00:23.840 align:start position:0% DEFCON and I think it's remarkably 00:00:23.840 --> 00:00:27.679 align:start position:0% DEFCON and I think it's remarkably open-minded<00:00:25.340> since<00:00:26.340> since<00:00:26.939> Rho<00:00:27.449> lang<00:00:27.660> is 00:00:27.679 --> 00:00:27.689 align:start position:0% open-minded since since Rho lang is 00:00:27.689 --> 00:00:28.670 align:start position:0% open-minded since since Rho lang is running<00:00:28.050> on<00:00:28.140> a<00:00:28.199> completely<00:00:28.560> different 00:00:28.670 --> 00:00:28.680 align:start position:0% running on a completely different 00:00:28.680 --> 00:00:30.380 align:start position:0% running on a completely different network<00:00:29.279> it's<00:00:29.609> a<00:00:29.699> completely<00:00:30.029> different 00:00:30.380 --> 00:00:30.390 align:start position:0% network it's a completely different 00:00:30.390 --> 00:00:32.600 align:start position:0% network it's a completely different approach<00:00:30.570> to<00:00:30.929> contracting<00:00:31.529> languages<00:00:32.040> and<00:00:32.250> a 00:00:32.600 --> 00:00:32.610 align:start position:0% approach to contracting languages and a 00:00:32.610 --> 00:00:34.250 align:start position:0% approach to contracting languages and a completely<00:00:32.910> different<00:00:33.030> approach<00:00:33.510> in<00:00:33.870> general 00:00:34.250 --> 00:00:34.260 align:start position:0% completely different approach in general 00:00:34.260 --> 00:00:36.350 align:start position:0% completely different approach in general to<00:00:34.530> to<00:00:35.040> the<00:00:35.160> whole<00:00:35.309> blockchain<00:00:35.730> architecture 00:00:36.350 --> 00:00:36.360 align:start position:0% to to the whole blockchain architecture 00:00:36.360 --> 00:00:40.389 align:start position:0% to to the whole blockchain architecture so<00:00:36.840> I'm<00:00:37.350> really<00:00:38.070> really<00:00:38.690> exceptionally 00:00:40.389 --> 00:00:40.399 align:start position:0% so I'm really really exceptionally 00:00:40.399 --> 00:00:43.610 align:start position:0% so I'm really really exceptionally impressed<00:00:41.399> by<00:00:42.000> the<00:00:42.059> open-mindedness<00:00:42.629> and<00:00:43.320> the 00:00:43.610 --> 00:00:43.620 align:start position:0% impressed by the open-mindedness and the 00:00:43.620 --> 00:00:45.290 align:start position:0% impressed by the open-mindedness and the inclusiveness<00:00:44.160> and<00:00:44.430> that<00:00:44.610> general<00:00:45.270> principle 00:00:45.290 --> 00:00:45.300 align:start position:0% inclusiveness and that general principle 00:00:45.300 --> 00:00:47.299 align:start position:0% inclusiveness and that general principle within<00:00:45.870> the<00:00:46.079> blockchain<00:00:46.289> culture<00:00:46.860> I<00:00:47.039> think 00:00:47.299 --> 00:00:47.309 align:start position:0% within the blockchain culture I think 00:00:47.309 --> 00:00:51.040 align:start position:0% within the blockchain culture I think that's<00:00:47.640> awesome<00:00:48.059> I<00:00:48.270> also<00:00:48.840> I<00:00:49.230> also<00:00:49.289> want<00:00:49.980> to<00:00:50.100> say 00:00:51.040 --> 00:00:51.050 align:start position:0% that's awesome I also I also want to say 00:00:51.050 --> 00:00:54.350 align:start position:0% that's awesome I also I also want to say that<00:00:52.050> today<00:00:52.860> is<00:00:53.190> All<00:00:53.430> Saints<00:00:53.879> Day<00:00:53.910> right 00:00:54.350 --> 00:00:54.360 align:start position:0% that today is All Saints Day right 00:00:54.360 --> 00:00:57.500 align:start position:0% that today is All Saints Day right Halloween<00:00:55.140> is<00:00:55.920> All<00:00:56.309> Hallows<00:00:56.699> Eve<00:00:57.059> and<00:00:57.329> today 00:00:57.500 --> 00:00:57.510 align:start position:0% Halloween is All Hallows Eve and today 00:00:57.510 --> 00:00:59.810 align:start position:0% Halloween is All Hallows Eve and today is<00:00:57.570> All<00:00:57.840> Saints<00:00:58.260> Day<00:00:58.320> and<00:00:58.710> I<00:00:59.460> want<00:00:59.609> to<00:00:59.670> give<00:00:59.789> a 00:00:59.810 --> 00:00:59.820 align:start position:0% is All Saints Day and I want to give a 00:00:59.820 --> 00:01:02.569 align:start position:0% is All Saints Day and I want to give a shout<00:01:00.690> out<00:01:00.719> my<00:01:00.930> 14<00:01:01.649> year<00:01:01.800> old<00:01:01.920> son<00:01:01.980> is<00:01:02.370> here 00:01:02.569 --> 00:01:02.579 align:start position:0% shout out my 14 year old son is here 00:01:02.579 --> 00:01:05.539 align:start position:0% shout out my 14 year old son is here today<00:01:02.899> and<00:01:03.899> and<00:01:04.229> and<00:01:04.439> this<00:01:04.559> is<00:01:04.680> sort<00:01:04.830> of<00:01:04.890> to<00:01:05.220> all 00:01:05.539 --> 00:01:05.549 align:start position:0% today and and and this is sort of to all 00:01:05.549 --> 00:01:08.719 align:start position:0% today and and and this is sort of to all the<00:01:05.700> young<00:01:05.939> Saints<00:01:06.630> who<00:01:07.170> are<00:01:07.200> inheriting<00:01:08.189> the 00:01:08.719 --> 00:01:08.729 align:start position:0% the young Saints who are inheriting the 00:01:08.729 --> 00:01:11.570 align:start position:0% the young Saints who are inheriting the planet<00:01:09.240> that<00:01:09.360> we're<00:01:09.510> leaving<00:01:09.659> them<00:01:10.159> and<00:01:11.159> what 00:01:11.570 --> 00:01:11.580 align:start position:0% planet that we're leaving them and what 00:01:11.580 --> 00:01:13.640 align:start position:0% planet that we're leaving them and what they<00:01:11.760> what<00:01:12.119> they<00:01:12.240> have<00:01:12.390> to<00:01:12.540> face<00:01:12.750> and<00:01:13.140> I<00:01:13.320> think 00:01:13.640 --> 00:01:13.650 align:start position:0% they what they have to face and I think 00:01:13.650 --> 00:01:15.410 align:start position:0% they what they have to face and I think that<00:01:13.740> the<00:01:13.830> blockchain<00:01:14.070> is<00:01:14.460> is<00:01:14.640> very<00:01:15.119> much 00:01:15.410 --> 00:01:15.420 align:start position:0% that the blockchain is is very much 00:01:15.420 --> 00:01:19.539 align:start position:0% that the blockchain is is very much about<00:01:16.110> that<00:01:16.380> so<00:01:16.770> with<00:01:17.100> that<00:01:17.250> let<00:01:17.520> me<00:01:17.549> introduce 00:01:19.539 --> 00:01:19.549 align:start position:0% about that so with that let me introduce 00:01:19.549 --> 00:01:22.789 align:start position:0% about that so with that let me introduce Rowling<00:01:20.549> and<00:01:20.820> the<00:01:21.450> message<00:01:21.780> is<00:01:21.960> is<00:01:22.170> it's<00:01:22.619> gonna 00:01:22.789 --> 00:01:22.799 align:start position:0% Rowling and the message is is it's gonna 00:01:22.799 --> 00:01:24.980 align:start position:0% Rowling and the message is is it's gonna be<00:01:22.979> really<00:01:23.189> simple<00:01:23.460> I'm<00:01:23.729> keeping<00:01:24.030> this<00:01:24.150> as<00:01:24.780> I 00:01:24.980 --> 00:01:24.990 align:start position:0% be really simple I'm keeping this as I 00:01:24.990 --> 00:01:26.210 align:start position:0% be really simple I'm keeping this as I was<00:01:25.140> writing<00:01:25.380> the<00:01:25.560> slides<00:01:25.740> I<00:01:25.890> was<00:01:26.009> thinking 00:01:26.210 --> 00:01:26.220 align:start position:0% was writing the slides I was thinking 00:01:26.220 --> 00:01:28.810 align:start position:0% was writing the slides I was thinking I'm<00:01:26.340> gonna<00:01:26.490> make<00:01:26.640> this<00:01:26.790> a<00:01:27.000> super<00:01:27.450> boring<00:01:27.810> talk 00:01:28.810 --> 00:01:28.820 align:start position:0% I'm gonna make this a super boring talk 00:01:28.820 --> 00:01:32.480 align:start position:0% I'm gonna make this a super boring talk so<00:01:29.820> so<00:01:30.119> the<00:01:30.240> aim<00:01:30.750> is<00:01:31.020> to<00:01:31.049> be<00:01:31.259> boring<00:01:31.590> but<00:01:31.860> clear 00:01:32.480 --> 00:01:32.490 align:start position:0% so so the aim is to be boring but clear 00:01:32.490 --> 00:01:35.300 align:start position:0% so so the aim is to be boring but clear and<00:01:33.360> maybe<00:01:33.720> you<00:01:34.350> know<00:01:34.470> if<00:01:34.680> we<00:01:34.799> can<00:01:34.950> figure<00:01:35.189> out 00:01:35.300 --> 00:01:35.310 align:start position:0% and maybe you know if we can figure out 00:01:35.310 --> 00:01:37.190 align:start position:0% and maybe you know if we can figure out a<00:01:35.400> way<00:01:35.490> to<00:01:35.610> have<00:01:35.820> fun<00:01:35.850> while<00:01:36.329> being<00:01:36.390> boring<00:01:36.930> and 00:01:37.190 --> 00:01:37.200 align:start position:0% a way to have fun while being boring and 00:01:37.200 --> 00:01:38.719 align:start position:0% a way to have fun while being boring and clear<00:01:37.470> let's<00:01:37.770> see<00:01:37.920> if<00:01:37.979> we<00:01:38.070> can<00:01:38.250> do<00:01:38.369> that 00:01:38.719 --> 00:01:38.729 align:start position:0% clear let's see if we can do that 00:01:38.729 --> 00:01:40.940 align:start position:0% clear let's see if we can do that so<00:01:39.150> so<00:01:39.600> I'm<00:01:39.720> you<00:01:40.229> know<00:01:40.350> instead<00:01:40.619> of<00:01:40.680> hello 00:01:40.940 --> 00:01:40.950 align:start position:0% so so I'm you know instead of hello 00:01:40.950 --> 00:01:43.100 align:start position:0% so so I'm you know instead of hello world<00:01:41.070> let's<00:01:41.490> do<00:01:41.820> hello<00:01:42.240> arithmetic<00:01:42.840> and<00:01:43.020> I'm 00:01:43.100 --> 00:01:43.110 align:start position:0% world let's do hello arithmetic and I'm 00:01:43.110 --> 00:01:45.200 align:start position:0% world let's do hello arithmetic and I'm gonna<00:01:43.200> do<00:01:43.470> like<00:01:43.710> this<00:01:43.860> simplest<00:01:44.520> stupidest 00:01:45.200 --> 00:01:45.210 align:start position:0% gonna do like this simplest stupidest 00:01:45.210 --> 00:01:47.210 align:start position:0% gonna do like this simplest stupidest contract<00:01:45.780> in<00:01:45.899> Rowling<00:01:46.200> and<00:01:46.380> I'll<00:01:46.799> just<00:01:46.950> walk 00:01:47.210 --> 00:01:47.220 align:start position:0% contract in Rowling and I'll just walk 00:01:47.220 --> 00:01:49.969 align:start position:0% contract in Rowling and I'll just walk you<00:01:47.460> through<00:01:47.729> that<00:01:47.909> and<00:01:48.270> then<00:01:48.689> and<00:01:48.930> then<00:01:49.170> and 00:01:49.969 --> 00:01:49.979 align:start position:0% you through that and then and then and 00:01:49.979 --> 00:01:51.649 align:start position:0% you through that and then and then and then<00:01:50.040> I'll<00:01:50.340> talk<00:01:50.610> a<00:01:50.640> little<00:01:50.939> bit<00:01:51.119> of<00:01:51.210> I'm<00:01:51.540> gonna 00:01:51.649 --> 00:01:51.659 align:start position:0% then I'll talk a little bit of I'm gonna 00:01:51.659 --> 00:01:54.200 align:start position:0% then I'll talk a little bit of I'm gonna introduce<00:01:51.990> some<00:01:52.680> non-determinism<00:01:53.460> into<00:01:54.060> that 00:01:54.200 --> 00:01:54.210 align:start position:0% introduce some non-determinism into that 00:01:54.210 --> 00:01:56.899 align:start position:0% introduce some non-determinism into that contract<00:01:54.810> and<00:01:55.049> talk<00:01:55.560> about<00:01:55.740> how<00:01:56.100> caspere 00:01:56.899 --> 00:01:56.909 align:start position:0% contract and talk about how caspere 00:01:56.909 --> 00:01:58.550 align:start position:0% contract and talk about how caspere addresses<00:01:57.420> the<00:01:57.540> non-determinism<00:01:58.229> and<00:01:58.500> the 00:01:58.550 --> 00:01:58.560 align:start position:0% addresses the non-determinism and the 00:01:58.560 --> 00:02:02.300 align:start position:0% addresses the non-determinism and the concurrency<00:01:59.100> inside<00:01:59.490> the<00:01:59.640> language<00:02:00.259> and<00:02:01.310> then 00:02:02.300 --> 00:02:02.310 align:start position:0% concurrency inside the language and then 00:02:02.310 --> 00:02:03.910 align:start position:0% concurrency inside the language and then we'll<00:02:02.969> look<00:02:03.180> at<00:02:03.299> a<00:02:03.360> more<00:02:03.570> sophisticated 00:02:03.910 --> 00:02:03.920 align:start position:0% we'll look at a more sophisticated 00:02:03.920 --> 00:02:06.410 align:start position:0% we'll look at a more sophisticated contract<00:02:04.920> and<00:02:05.159> I've<00:02:05.369> actually<00:02:05.490> got<00:02:05.880> Kent 00:02:06.410 --> 00:02:06.420 align:start position:0% contract and I've actually got Kent 00:02:06.420 --> 00:02:10.070 align:start position:0% contract and I've actually got Kent shakaama<00:02:07.110> here<00:02:07.530> with<00:02:07.710> me<00:02:07.890> on<00:02:08.039> zoom'<00:02:08.569> and<00:02:09.569> he's 00:02:10.070 --> 00:02:10.080 align:start position:0% shakaama here with me on zoom' and he's 00:02:10.080 --> 00:02:12.700 align:start position:0% shakaama here with me on zoom' and he's gonna<00:02:10.319> he's<00:02:10.679> gonna<00:02:10.770> walk<00:02:11.099> us<00:02:11.340> through 00:02:12.700 --> 00:02:12.710 align:start position:0% gonna he's gonna walk us through 00:02:12.710 --> 00:02:16.480 align:start position:0% gonna he's gonna walk us through the<00:02:13.040> the<00:02:13.610> ERC<00:02:13.970> 20<00:02:14.420> contract<00:02:15.490> implementation 00:02:16.480 --> 00:02:16.490 align:start position:0% the the ERC 20 contract implementation 00:02:16.490 --> 00:02:19.210 align:start position:0% the the ERC 20 contract implementation that<00:02:16.640> he's<00:02:16.820> done<00:02:17.030> can't<00:02:17.780> joined<00:02:18.380> us<00:02:18.710> in<00:02:19.040> the 00:02:19.210 --> 00:02:19.220 align:start position:0% that he's done can't joined us in the 00:02:19.220 --> 00:02:21.220 align:start position:0% that he's done can't joined us in the summer<00:02:19.520> and<00:02:19.790> took<00:02:20.330> over<00:02:20.480> the<00:02:20.630> work<00:02:20.840> that<00:02:21.050> I<00:02:21.080> was 00:02:21.220 --> 00:02:21.230 align:start position:0% summer and took over the work that I was 00:02:21.230 --> 00:02:22.840 align:start position:0% summer and took over the work that I was doing<00:02:21.290> on<00:02:21.590> the<00:02:21.620> row<00:02:21.800> line<00:02:21.980> compiler<00:02:22.520> and<00:02:22.670> has 00:02:22.840 --> 00:02:22.850 align:start position:0% doing on the row line compiler and has 00:02:22.850 --> 00:02:25.210 align:start position:0% doing on the row line compiler and has done<00:02:23.000> an<00:02:23.180> amazing<00:02:23.480> job<00:02:23.920> taking<00:02:24.920> it<00:02:25.010> further 00:02:25.210 --> 00:02:25.220 align:start position:0% done an amazing job taking it further 00:02:25.220 --> 00:02:27.040 align:start position:0% done an amazing job taking it further and<00:02:25.640> then<00:02:25.730> writing<00:02:26.060> sample<00:02:26.420> contracts<00:02:26.930> to 00:02:27.040 --> 00:02:27.050 align:start position:0% and then writing sample contracts to 00:02:27.050 --> 00:02:30.700 align:start position:0% and then writing sample contracts to test<00:02:27.260> his<00:02:27.470> code<00:02:27.740> so<00:02:28.340> he<00:02:28.580> did<00:02:28.790> an<00:02:29.350> example<00:02:30.350> of<00:02:30.560> an 00:02:30.700 --> 00:02:30.710 align:start position:0% test his code so he did an example of an 00:02:30.710 --> 00:02:33.580 align:start position:0% test his code so he did an example of an ER<00:02:30.920> C<00:02:31.070> 20<00:02:31.340> like<00:02:31.490> contract<00:02:31.970> enrolling<00:02:32.420> which<00:02:33.410> is 00:02:33.580 --> 00:02:33.590 align:start position:0% ER C 20 like contract enrolling which is 00:02:33.590 --> 00:02:36.190 align:start position:0% ER C 20 like contract enrolling which is running<00:02:33.950> now<00:02:34.100> and<00:02:34.340> you<00:02:34.400> can<00:02:34.550> go<00:02:34.700> play<00:02:35.270> with<00:02:35.480> it 00:02:36.190 --> 00:02:36.200 align:start position:0% running now and you can go play with it 00:02:36.200 --> 00:02:39.460 align:start position:0% running now and you can go play with it there's<00:02:36.470> also<00:02:36.650> rolling<00:02:37.310> org<00:02:38.170> so<00:02:39.170> you<00:02:39.260> can<00:02:39.380> go 00:02:39.460 --> 00:02:39.470 align:start position:0% there's also rolling org so you can go 00:02:39.470 --> 00:02:41.140 align:start position:0% there's also rolling org so you can go check<00:02:39.680> out<00:02:39.830> that<00:02:39.890> website<00:02:40.190> right<00:02:40.640> now<00:02:40.670> and 00:02:41.140 --> 00:02:41.150 align:start position:0% check out that website right now and 00:02:41.150 --> 00:02:45.970 align:start position:0% check out that website right now and Kenta<00:02:41.960> graciously<00:02:42.590> put<00:02:43.340> up<00:02:43.460> a<00:02:43.640> video<00:02:44.330> of<00:02:45.140> this 00:02:45.970 --> 00:02:45.980 align:start position:0% Kenta graciously put up a video of this 00:02:45.980 --> 00:02:47.800 align:start position:0% Kenta graciously put up a video of this the<00:02:46.310> demo<00:02:46.580> he's<00:02:46.760> going<00:02:46.910> to<00:02:46.970> give<00:02:47.120> today<00:02:47.300> so<00:02:47.480> if 00:02:47.800 --> 00:02:47.810 align:start position:0% the demo he's going to give today so if 00:02:47.810 --> 00:02:49.510 align:start position:0% the demo he's going to give today so if you<00:02:47.930> don't<00:02:48.110> don't<00:02:48.560> catch<00:02:48.770> it<00:02:48.980> now<00:02:49.130> you<00:02:49.190> can 00:02:49.510 --> 00:02:49.520 align:start position:0% you don't don't catch it now you can 00:02:49.520 --> 00:02:51.010 align:start position:0% you don't don't catch it now you can also<00:02:49.670> go<00:02:49.910> back<00:02:50.060> and<00:02:50.270> look<00:02:50.360> at<00:02:50.540> it<00:02:50.570> at<00:02:50.840> your 00:02:51.010 --> 00:02:51.020 align:start position:0% also go back and look at it at your 00:02:51.020 --> 00:02:54.940 align:start position:0% also go back and look at it at your leisure<00:02:51.230> and<00:02:51.950> then<00:02:53.230> so<00:02:54.230> that's<00:02:54.470> kind<00:02:54.770> of<00:02:54.830> the 00:02:54.940 --> 00:02:54.950 align:start position:0% leisure and then so that's kind of the 00:02:54.950 --> 00:02:56.500 align:start position:0% leisure and then so that's kind of the order<00:02:55.250> and<00:02:55.520> then<00:02:55.700> we'll<00:02:55.790> talk<00:02:55.970> about<00:02:56.150> some 00:02:56.500 --> 00:02:56.510 align:start position:0% order and then we'll talk about some 00:02:56.510 --> 00:02:59.260 align:start position:0% order and then we'll talk about some other<00:02:56.720> things<00:02:56.810> towards<00:02:57.710> the<00:02:57.830> end<00:02:58.030> one<00:02:59.030> thing 00:02:59.260 --> 00:02:59.270 align:start position:0% other things towards the end one thing 00:02:59.270 --> 00:03:01.900 align:start position:0% other things towards the end one thing that<00:02:59.450> I<00:02:59.480> will<00:03:00.230> ask<00:03:00.680> you<00:03:00.980> to<00:03:01.010> ask<00:03:01.460> me<00:03:01.820> about 00:03:01.900 --> 00:03:01.910 align:start position:0% that I will ask you to ask me about 00:03:01.910 --> 00:03:04.210 align:start position:0% that I will ask you to ask me about later<00:03:02.330> is<00:03:02.630> the<00:03:03.080> behavioral<00:03:03.500> type<00:03:03.770> system 00:03:04.210 --> 00:03:04.220 align:start position:0% later is the behavioral type system 00:03:04.220 --> 00:03:06.040 align:start position:0% later is the behavioral type system right<00:03:04.610> now<00:03:04.820> we're<00:03:05.030> going<00:03:05.240> to<00:03:05.360> be<00:03:05.450> focusing<00:03:05.930> on 00:03:06.040 --> 00:03:06.050 align:start position:0% right now we're going to be focusing on 00:03:06.050 --> 00:03:08.200 align:start position:0% right now we're going to be focusing on the<00:03:06.140> untyped<00:03:06.680> portion<00:03:07.190> of<00:03:07.340> the<00:03:07.430> language<00:03:07.910> or 00:03:08.200 --> 00:03:08.210 align:start position:0% the untyped portion of the language or 00:03:08.210 --> 00:03:10.090 align:start position:0% the untyped portion of the language or we're<00:03:08.870> just<00:03:09.020> not<00:03:09.290> looking<00:03:09.590> at<00:03:09.740> the<00:03:09.860> types 00:03:10.090 --> 00:03:10.100 align:start position:0% we're just not looking at the types 00:03:10.100 --> 00:03:11.560 align:start position:0% we're just not looking at the types because<00:03:10.520> you<00:03:10.640> type<00:03:10.910> the<00:03:11.060> entire<00:03:11.180> language 00:03:11.560 --> 00:03:11.570 align:start position:0% because you type the entire language 00:03:11.570 --> 00:03:14.560 align:start position:0% because you type the entire language because<00:03:12.530> if<00:03:12.740> you<00:03:12.860> get<00:03:13.160> the<00:03:13.550> the<00:03:13.880> conceptual 00:03:14.560 --> 00:03:14.570 align:start position:0% because if you get the the conceptual 00:03:14.570 --> 00:03:19.360 align:start position:0% because if you get the the conceptual apparatus<00:03:14.690> the<00:03:15.290> types<00:03:15.500> are<00:03:15.710> easy<00:03:16.870> okay<00:03:18.370> so 00:03:19.360 --> 00:03:19.370 align:start position:0% apparatus the types are easy okay so 00:03:19.370 --> 00:03:22.360 align:start position:0% apparatus the types are easy okay so here's<00:03:19.790> here's<00:03:20.450> a<00:03:20.570> simple<00:03:21.230> very<00:03:21.800> very<00:03:22.040> simple 00:03:22.360 --> 00:03:22.370 align:start position:0% here's here's a simple very very simple 00:03:22.370 --> 00:03:24.060 align:start position:0% here's here's a simple very very simple contract<00:03:22.730> it's<00:03:22.910> actually<00:03:23.150> a<00:03:23.180> contract<00:03:23.630> scheme 00:03:24.060 --> 00:03:24.070 align:start position:0% contract it's actually a contract scheme 00:03:24.070 --> 00:03:27.010 align:start position:0% contract it's actually a contract scheme because<00:03:25.070> I've<00:03:25.490> left<00:03:25.970> some<00:03:26.270> holes<00:03:26.600> in<00:03:26.900> the 00:03:27.010 --> 00:03:27.020 align:start position:0% because I've left some holes in the 00:03:27.020 --> 00:03:28.480 align:start position:0% because I've left some holes in the contract<00:03:27.470> where<00:03:27.590> you<00:03:27.680> could<00:03:27.860> put<00:03:28.010> additional 00:03:28.480 --> 00:03:28.490 align:start position:0% contract where you could put additional 00:03:28.490 --> 00:03:30.850 align:start position:0% contract where you could put additional code<00:03:28.730> right<00:03:29.540> so<00:03:29.690> this<00:03:29.840> contract<00:03:30.320> is<00:03:30.440> very 00:03:30.850 --> 00:03:30.860 align:start position:0% code right so this contract is very 00:03:30.860 --> 00:03:32.920 align:start position:0% code right so this contract is very straightforward<00:03:31.220> what<00:03:31.640> it<00:03:31.760> does<00:03:32.000> first<00:03:32.750> of 00:03:32.920 --> 00:03:32.930 align:start position:0% straightforward what it does first of 00:03:32.930 --> 00:03:35.470 align:start position:0% straightforward what it does first of all<00:03:33.020> it's<00:03:33.170> parametric<00:03:34.100> in<00:03:34.280> a<00:03:34.700> set<00:03:34.880> of<00:03:35.000> channels 00:03:35.470 --> 00:03:35.480 align:start position:0% all it's parametric in a set of channels 00:03:35.480 --> 00:03:37.630 align:start position:0% all it's parametric in a set of channels Laporte<00:03:35.960> so<00:03:36.230> if<00:03:36.350> you<00:03:36.470> heard<00:03:36.740> martin<00:03:37.190> bzees 00:03:37.630 --> 00:03:37.640 align:start position:0% Laporte so if you heard martin bzees 00:03:37.640 --> 00:03:40.810 align:start position:0% Laporte so if you heard martin bzees talk<00:03:38.350> earlier<00:03:39.350> so<00:03:39.950> he<00:03:40.130> was<00:03:40.250> talking<00:03:40.490> about 00:03:40.810 --> 00:03:40.820 align:start position:0% talk earlier so he was talking about 00:03:40.820 --> 00:03:42.400 align:start position:0% talk earlier so he was talking about port<00:03:41.330> based<00:03:41.630> or<00:03:41.870> channel<00:03:42.200> based 00:03:42.400 --> 00:03:42.410 align:start position:0% port based or channel based 00:03:42.410 --> 00:03:44.710 align:start position:0% port based or channel based computational<00:03:43.310> models<00:03:43.640> right<00:03:44.240> so<00:03:44.570> that's 00:03:44.710 --> 00:03:44.720 align:start position:0% computational models right so that's 00:03:44.720 --> 00:03:47.470 align:start position:0% computational models right so that's what<00:03:44.960> rolling<00:03:45.290> is<00:03:45.560> and<00:03:46.130> it<00:03:46.400> for<00:03:46.700> enrolling 00:03:47.470 --> 00:03:47.480 align:start position:0% what rolling is and it for enrolling 00:03:47.480 --> 00:03:48.850 align:start position:0% what rolling is and it for enrolling there<00:03:47.720> are<00:03:47.780> basically<00:03:48.110> only<00:03:48.290> two<00:03:48.380> things<00:03:48.740> in 00:03:48.850 --> 00:03:48.860 align:start position:0% there are basically only two things in 00:03:48.860 --> 00:03:50.590 align:start position:0% there are basically only two things in the<00:03:48.950> world<00:03:48.980> there<00:03:49.550> are<00:03:49.670> ports<00:03:50.030> and<00:03:50.210> channels 00:03:50.590 --> 00:03:50.600 align:start position:0% the world there are ports and channels 00:03:50.600 --> 00:03:53.320 align:start position:0% the world there are ports and channels there<00:03:50.930> we<00:03:51.350> use<00:03:51.680> those<00:03:51.860> synonymously<00:03:52.490> we<00:03:53.180> also 00:03:53.320 --> 00:03:53.330 align:start position:0% there we use those synonymously we also 00:03:53.330 --> 00:03:54.820 align:start position:0% there we use those synonymously we also call<00:03:53.570> them<00:03:53.720> names<00:03:53.930> sometimes<00:03:54.410> and<00:03:54.650> there<00:03:54.740> are 00:03:54.820 --> 00:03:54.830 align:start position:0% call them names sometimes and there are 00:03:54.830 --> 00:03:56.830 align:start position:0% call them names sometimes and there are processes<00:03:55.340> that<00:03:55.520> use<00:03:55.730> ports<00:03:56.210> channels<00:03:56.630> names 00:03:56.830 --> 00:03:56.840 align:start position:0% processes that use ports channels names 00:03:56.840 --> 00:03:59.380 align:start position:0% processes that use ports channels names to<00:03:57.080> communicate<00:03:57.560> right<00:03:57.800> that's<00:03:58.520> it<00:03:58.700> as<00:03:58.970> the 00:03:59.380 --> 00:03:59.390 align:start position:0% to communicate right that's it as the 00:03:59.390 --> 00:04:02.170 align:start position:0% to communicate right that's it as the entire<00:03:59.930> ontology<00:04:00.500> in<00:04:00.980> this<00:04:01.490> computational 00:04:02.170 --> 00:04:02.180 align:start position:0% entire ontology in this computational 00:04:02.180 --> 00:04:05.830 align:start position:0% entire ontology in this computational universe<00:04:02.920> so<00:04:03.920> contracts<00:04:04.610> are<00:04:04.970> just<00:04:05.240> processes 00:04:05.830 --> 00:04:05.840 align:start position:0% universe so contracts are just processes 00:04:05.840 --> 00:04:08.949 align:start position:0% universe so contracts are just processes that<00:04:06.470> are<00:04:06.860> parametric<00:04:07.490> in<00:04:07.910> some<00:04:08.540> ports<00:04:08.840> or 00:04:08.949 --> 00:04:08.959 align:start position:0% that are parametric in some ports or 00:04:08.959 --> 00:04:10.510 align:start position:0% that are parametric in some ports or channels<00:04:09.380> so<00:04:09.500> this<00:04:09.650> contract<00:04:10.160> see<00:04:10.370> is 00:04:10.510 --> 00:04:10.520 align:start position:0% channels so this contract see is 00:04:10.520 --> 00:04:12.910 align:start position:0% channels so this contract see is parametric<00:04:11.120> in<00:04:11.300> four<00:04:11.540> channels<00:04:11.959> and<00:04:12.230> it<00:04:12.709> does 00:04:12.910 --> 00:04:12.920 align:start position:0% parametric in four channels and it does 00:04:12.920 --> 00:04:15.460 align:start position:0% parametric in four channels and it does it<00:04:13.700> does<00:04:13.940> a<00:04:13.970> couple<00:04:14.540> of<00:04:14.660> things<00:04:14.780> in<00:04:15.080> parallel 00:04:15.460 --> 00:04:15.470 align:start position:0% it does a couple of things in parallel 00:04:15.470 --> 00:04:18.220 align:start position:0% it does a couple of things in parallel so<00:04:16.120> I'm<00:04:17.120> gonna<00:04:17.239> stand<00:04:17.480> over<00:04:17.630> here<00:04:17.959> I<00:04:17.989> like 00:04:18.220 --> 00:04:18.230 align:start position:0% so I'm gonna stand over here I like 00:04:18.230 --> 00:04:19.539 align:start position:0% so I'm gonna stand over here I like pointing<00:04:18.620> at<00:04:18.770> the<00:04:18.830> screen<00:04:19.010> I<00:04:19.130> hope<00:04:19.340> that's 00:04:19.539 --> 00:04:19.549 align:start position:0% pointing at the screen I hope that's 00:04:19.549 --> 00:04:23.740 align:start position:0% pointing at the screen I hope that's okay<00:04:19.820> with<00:04:19.970> you<00:04:20.060> guys<00:04:20.380> so<00:04:21.380> so<00:04:21.970> one<00:04:22.970> thread<00:04:23.600> of 00:04:23.740 --> 00:04:23.750 align:start position:0% okay with you guys so so one thread of 00:04:23.750 --> 00:04:25.159 align:start position:0% okay with you guys so so one thread of activity<00:04:24.290> way 00:04:25.159 --> 00:04:25.169 align:start position:0% activity way 00:04:25.169 --> 00:04:28.070 align:start position:0% activity way at<00:04:25.800> the<00:04:26.099> channel<00:04:26.490> x4<00:04:27.389> something<00:04:27.810> that<00:04:27.960> it's 00:04:28.070 --> 00:04:28.080 align:start position:0% at the channel x4 something that it's 00:04:28.080 --> 00:04:30.350 align:start position:0% at the channel x4 something that it's going<00:04:28.259> to<00:04:28.319> call<00:04:28.530> Y<00:04:28.830> and<00:04:29.249> at<00:04:29.699> the<00:04:29.789> same<00:04:30.060> time 00:04:30.350 --> 00:04:30.360 align:start position:0% going to call Y and at the same time 00:04:30.360 --> 00:04:32.749 align:start position:0% going to call Y and at the same time it's<00:04:30.569> also<00:04:30.749> waiting<00:04:31.289> at<00:04:31.409> the<00:04:31.499> channel<00:04:31.860> you<00:04:32.129> for 00:04:32.749 --> 00:04:32.759 align:start position:0% it's also waiting at the channel you for 00:04:32.759 --> 00:04:35.779 align:start position:0% it's also waiting at the channel you for something<00:04:32.969> it's<00:04:33.210> gonna<00:04:33.360> call<00:04:33.719> V<00:04:34.490> and<00:04:35.490> unless 00:04:35.779 --> 00:04:35.789 align:start position:0% something it's gonna call V and unless 00:04:35.789 --> 00:04:38.149 align:start position:0% something it's gonna call V and unless it<00:04:35.969> gets<00:04:36.060> both<00:04:36.330> of<00:04:36.509> those<00:04:36.599> inputs<00:04:37.080> in<00:04:37.650> any 00:04:38.149 --> 00:04:38.159 align:start position:0% it gets both of those inputs in any 00:04:38.159 --> 00:04:40.249 align:start position:0% it gets both of those inputs in any order<00:04:38.550> but<00:04:38.729> unless<00:04:39.539> it<00:04:39.719> gets<00:04:39.779> both<00:04:40.020> of<00:04:40.169> those 00:04:40.249 --> 00:04:40.259 align:start position:0% order but unless it gets both of those 00:04:40.259 --> 00:04:43.059 align:start position:0% order but unless it gets both of those inputs<00:04:40.680> the<00:04:40.919> rest<00:04:41.279> of<00:04:41.550> this<00:04:41.759> doesn't<00:04:42.689> happen 00:04:43.059 --> 00:04:43.069 align:start position:0% inputs the rest of this doesn't happen 00:04:43.069 --> 00:04:46.969 align:start position:0% inputs the rest of this doesn't happen okay<00:04:44.069> and<00:04:44.490> the<00:04:45.240> rest<00:04:45.419> so<00:04:45.810> you<00:04:46.110> can<00:04:46.319> see<00:04:46.560> this<00:04:46.800> as 00:04:46.969 --> 00:04:46.979 align:start position:0% okay and the rest so you can see this as 00:04:46.979 --> 00:04:49.640 align:start position:0% okay and the rest so you can see this as a<00:04:47.009> kind<00:04:47.580> of<00:04:47.759> sequential<00:04:48.300> ization<00:04:48.749> and<00:04:49.139> this 00:04:49.640 --> 00:04:49.650 align:start position:0% a kind of sequential ization and this 00:04:49.650 --> 00:04:52.040 align:start position:0% a kind of sequential ization and this vertical<00:04:49.889> bar<00:04:50.129> here<00:04:50.789> represents<00:04:51.050> another 00:04:52.040 --> 00:04:52.050 align:start position:0% vertical bar here represents another 00:04:52.050 --> 00:04:55.249 align:start position:0% vertical bar here represents another thread<00:04:52.650> of<00:04:52.830> activity<00:04:53.659> okay<00:04:54.659> and<00:04:54.900> this<00:04:54.990> threat 00:04:55.249 --> 00:04:55.259 align:start position:0% thread of activity okay and this threat 00:04:55.259 --> 00:04:59.059 align:start position:0% thread of activity okay and this threat of<00:04:55.379> activity<00:04:55.770> waits<00:04:56.069> at<00:04:56.340> the<00:04:56.370> channel<00:04:56.819> Zed<00:04:58.069> for 00:04:59.059 --> 00:04:59.069 align:start position:0% of activity waits at the channel Zed for 00:04:59.069 --> 00:05:00.769 align:start position:0% of activity waits at the channel Zed for something<00:04:59.460> it's<00:04:59.580> going<00:04:59.699> to<00:04:59.789> call<00:05:00.000> W<00:05:00.449> and<00:05:00.659> then 00:05:00.769 --> 00:05:00.779 align:start position:0% something it's going to call W and then 00:05:00.779 --> 00:05:04.070 align:start position:0% something it's going to call W and then does<00:05:00.990> this<00:05:01.259> so<00:05:02.129> that<00:05:02.340> in<00:05:02.520> the<00:05:02.849> top<00:05:03.150> thread<00:05:03.539> the 00:05:04.070 --> 00:05:04.080 align:start position:0% does this so that in the top thread the 00:05:04.080 --> 00:05:07.249 align:start position:0% does this so that in the top thread the rest<00:05:04.469> of<00:05:04.710> the<00:05:04.800> computation<00:05:05.550> is<00:05:05.699> to<00:05:06.539> take<00:05:06.870> what 00:05:07.249 --> 00:05:07.259 align:start position:0% rest of the computation is to take what 00:05:07.259 --> 00:05:10.309 align:start position:0% rest of the computation is to take what it<00:05:07.379> received<00:05:07.800> on<00:05:08.099> Y<00:05:08.550> and<00:05:09.060> what<00:05:09.629> it<00:05:09.750> received<00:05:10.110> as 00:05:10.309 --> 00:05:10.319 align:start position:0% it received on Y and what it received as 00:05:10.319 --> 00:05:12.800 align:start position:0% it received on Y and what it received as as<00:05:10.830> V<00:05:11.460> so<00:05:11.699> what<00:05:11.789> it<00:05:11.909> receives<00:05:12.180> us<00:05:12.300> Y<00:05:12.509> and<00:05:12.719> what 00:05:12.800 --> 00:05:12.810 align:start position:0% as V so what it receives us Y and what 00:05:12.810 --> 00:05:15.350 align:start position:0% as V so what it receives us Y and what it<00:05:12.870> receives<00:05:13.110> as<00:05:13.229> V<00:05:13.379> there's<00:05:13.860> one<00:05:14.219> tiny<00:05:14.969> little 00:05:15.350 --> 00:05:15.360 align:start position:0% it receives as V there's one tiny little 00:05:15.360 --> 00:05:16.999 align:start position:0% it receives as V there's one tiny little piece<00:05:15.719> of<00:05:15.930> information<00:05:16.080> you<00:05:16.529> have<00:05:16.680> to<00:05:16.860> know 00:05:16.999 --> 00:05:17.009 align:start position:0% piece of information you have to know 00:05:17.009 --> 00:05:19.279 align:start position:0% piece of information you have to know which<00:05:17.610> is<00:05:17.819> that<00:05:17.969> whenever<00:05:18.120> information<00:05:18.960> comes 00:05:19.279 --> 00:05:19.289 align:start position:0% which is that whenever information comes 00:05:19.289 --> 00:05:22.730 align:start position:0% which is that whenever information comes in<00:05:19.589> this<00:05:20.430> way<00:05:20.699> it's<00:05:21.509> treated<00:05:21.839> as<00:05:22.139> a<00:05:22.169> reference 00:05:22.730 --> 00:05:22.740 align:start position:0% in this way it's treated as a reference 00:05:22.740 --> 00:05:24.920 align:start position:0% in this way it's treated as a reference you<00:05:23.460> could<00:05:23.610> also<00:05:23.789> think<00:05:24.060> of<00:05:24.180> that<00:05:24.360> as<00:05:24.509> a<00:05:24.539> port 00:05:24.920 --> 00:05:24.930 align:start position:0% you could also think of that as a port 00:05:24.930 --> 00:05:26.719 align:start position:0% you could also think of that as a port or<00:05:25.199> a<00:05:25.289> channel<00:05:25.680> but<00:05:26.069> it's<00:05:26.249> treated<00:05:26.550> as<00:05:26.699> a 00:05:26.719 --> 00:05:26.729 align:start position:0% or a channel but it's treated as a 00:05:26.729 --> 00:05:28.610 align:start position:0% or a channel but it's treated as a reference<00:05:27.240> and<00:05:27.479> so<00:05:27.839> you<00:05:27.930> have<00:05:28.110> to<00:05:28.229> dereference 00:05:28.610 --> 00:05:28.620 align:start position:0% reference and so you have to dereference 00:05:28.620 --> 00:05:30.320 align:start position:0% reference and so you have to dereference it<00:05:29.009> and<00:05:29.279> that's<00:05:29.490> what<00:05:29.610> these<00:05:29.729> little<00:05:29.789> stars 00:05:30.320 --> 00:05:30.330 align:start position:0% it and that's what these little stars 00:05:30.330 --> 00:05:33.890 align:start position:0% it and that's what these little stars are<00:05:30.569> doing<00:05:30.779> and<00:05:31.669> we're<00:05:32.669> kind<00:05:33.240> of<00:05:33.360> expecting 00:05:33.890 --> 00:05:33.900 align:start position:0% are doing and we're kind of expecting 00:05:33.900 --> 00:05:36.019 align:start position:0% are doing and we're kind of expecting the<00:05:34.020> whatever<00:05:34.199> we<00:05:34.560> did<00:05:34.740> for<00:05:34.919> dereference<00:05:35.550> it's 00:05:36.019 --> 00:05:36.029 align:start position:0% the whatever we did for dereference it's 00:05:36.029 --> 00:05:37.850 align:start position:0% the whatever we did for dereference it's gonna<00:05:36.240> be<00:05:36.449> safe<00:05:36.779> to<00:05:37.139> add<00:05:37.259> those<00:05:37.589> two<00:05:37.830> things 00:05:37.850 --> 00:05:37.860 align:start position:0% gonna be safe to add those two things 00:05:37.860 --> 00:05:40.309 align:start position:0% gonna be safe to add those two things together<00:05:38.339> so<00:05:38.969> this<00:05:39.180> this<00:05:39.419> operation<00:05:39.960> here<00:05:40.139> has 00:05:40.309 --> 00:05:40.319 align:start position:0% together so this this operation here has 00:05:40.319 --> 00:05:42.469 align:start position:0% together so this this operation here has to<00:05:40.469> be<00:05:40.560> interpretable<00:05:41.250> for<00:05:42.000> these<00:05:42.120> two 00:05:42.469 --> 00:05:42.479 align:start position:0% to be interpretable for these two 00:05:42.479 --> 00:05:45.589 align:start position:0% to be interpretable for these two different<00:05:43.199> values<00:05:43.979> that<00:05:44.520> are<00:05:44.699> being<00:05:44.789> received 00:05:45.589 --> 00:05:45.599 align:start position:0% different values that are being received 00:05:45.599 --> 00:05:48.709 align:start position:0% different values that are being received at<00:05:46.169> these<00:05:46.649> ports<00:05:47.159> and<00:05:47.520> then<00:05:48.419> it's<00:05:48.569> gonna 00:05:48.709 --> 00:05:48.719 align:start position:0% at these ports and then it's gonna 00:05:48.719 --> 00:05:50.779 align:start position:0% at these ports and then it's gonna whatever<00:05:49.439> the<00:05:49.680> result<00:05:50.039> of<00:05:50.159> that<00:05:50.250> edition<00:05:50.669> is 00:05:50.779 --> 00:05:50.789 align:start position:0% whatever the result of that edition is 00:05:50.789 --> 00:05:53.409 align:start position:0% whatever the result of that edition is that's<00:05:51.000> gonna<00:05:51.120> be<00:05:51.300> sent<00:05:51.750> on<00:05:51.960> the<00:05:52.229> Zed<00:05:52.500> port 00:05:53.409 --> 00:05:53.419 align:start position:0% that's gonna be sent on the Zed port 00:05:53.419 --> 00:05:56.749 align:start position:0% that's gonna be sent on the Zed port okay<00:05:54.419> and<00:05:54.659> then<00:05:55.110> in<00:05:55.439> parallel<00:05:56.009> with<00:05:56.310> that<00:05:56.339> that 00:05:56.749 --> 00:05:56.759 align:start position:0% okay and then in parallel with that that 00:05:56.759 --> 00:05:59.119 align:start position:0% okay and then in parallel with that that output<00:05:57.419> operation<00:05:57.990> there's<00:05:58.529> something<00:05:58.979> else 00:05:59.119 --> 00:05:59.129 align:start position:0% output operation there's something else 00:05:59.129 --> 00:06:02.079 align:start position:0% output operation there's something else that<00:05:59.370> might<00:05:59.490> happen<00:05:59.729> that<00:05:59.939> uses<00:06:00.419> X<00:06:00.719> and<00:06:00.990> Zed 00:06:02.079 --> 00:06:02.089 align:start position:0% that might happen that uses X and Zed 00:06:02.089 --> 00:06:04.579 align:start position:0% that might happen that uses X and Zed okay<00:06:03.089> over<00:06:04.080> here 00:06:04.579 --> 00:06:04.589 align:start position:0% okay over here 00:06:04.589 --> 00:06:07.339 align:start position:0% okay over here it's<00:06:05.129> a<00:06:05.310> similar<00:06:05.909> kind<00:06:06.120> of<00:06:06.300> thing<00:06:06.360> on<00:06:06.750> the<00:06:07.050> a 00:06:07.339 --> 00:06:07.349 align:start position:0% it's a similar kind of thing on the a 00:06:07.349 --> 00:06:10.189 align:start position:0% it's a similar kind of thing on the a port<00:06:08.089> it's<00:06:09.089> gonna<00:06:09.270> take<00:06:09.629> whatever<00:06:10.050> it 00:06:10.189 --> 00:06:10.199 align:start position:0% port it's gonna take whatever it 00:06:10.199 --> 00:06:13.249 align:start position:0% port it's gonna take whatever it received<00:06:10.649> on<00:06:10.949> W<00:06:11.430> multiply<00:06:12.389> it<00:06:12.449> by<00:06:12.689> two<00:06:12.750> and 00:06:13.249 --> 00:06:13.259 align:start position:0% received on W multiply it by two and 00:06:13.259 --> 00:06:18.800 align:start position:0% received on W multiply it by two and send<00:06:14.009> that<00:06:14.069> send<00:06:14.639> that<00:06:14.789> out<00:06:14.819> okay<00:06:15.810> and<00:06:17.210> Q<00:06:18.210> runs 00:06:18.800 --> 00:06:18.810 align:start position:0% send that send that out okay and Q runs 00:06:18.810 --> 00:06:20.769 align:start position:0% send that send that out okay and Q runs in<00:06:19.020> parallel<00:06:19.229> with<00:06:19.589> that<00:06:19.740> output<00:06:20.069> operation 00:06:20.769 --> 00:06:20.779 align:start position:0% in parallel with that output operation 00:06:20.779 --> 00:06:23.659 align:start position:0% in parallel with that output operation very<00:06:21.779> straightforward<00:06:22.469> nothing<00:06:23.250> magical 00:06:23.659 --> 00:06:23.669 align:start position:0% very straightforward nothing magical 00:06:23.669 --> 00:06:29.779 align:start position:0% very straightforward nothing magical here<00:06:23.909> easy<00:06:24.810> to<00:06:25.080> understand<00:06:27.199> and<00:06:28.199> in<00:06:28.469> fact<00:06:28.789> I've 00:06:29.779 --> 00:06:29.789 align:start position:0% here easy to understand and in fact I've 00:06:29.789 --> 00:06:32.240 align:start position:0% here easy to understand and in fact I've made<00:06:30.089> a<00:06:30.259> graphical<00:06:31.259> representation<00:06:31.649> of<00:06:32.069> this 00:06:32.240 --> 00:06:32.250 align:start position:0% made a graphical representation of this 00:06:32.250 --> 00:06:35.629 align:start position:0% made a graphical representation of this same<00:06:32.520> flow<00:06:32.879> okay<00:06:34.159> so 00:06:35.629 --> 00:06:35.639 align:start position:0% same flow okay so 00:06:35.639 --> 00:06:38.869 align:start position:0% same flow okay so all<00:06:36.270> I've<00:06:36.659> done<00:06:36.840> is<00:06:36.900> to<00:06:37.319> map<00:06:37.590> out<00:06:37.919> graphically 00:06:38.869 --> 00:06:38.879 align:start position:0% all I've done is to map out graphically 00:06:38.879 --> 00:06:42.379 align:start position:0% all I've done is to map out graphically the<00:06:39.120> lifetimes<00:06:39.870> of<00:06:40.110> the<00:06:40.229> ports<00:06:40.740> as<00:06:41.039> far<00:06:42.030> as<00:06:42.180> we 00:06:42.379 --> 00:06:42.389 align:start position:0% the lifetimes of the ports as far as we 00:06:42.389 --> 00:06:44.839 align:start position:0% the lifetimes of the ports as far as we know<00:06:42.629> right<00:06:43.009> and<00:06:44.009> you<00:06:44.099> can<00:06:44.279> see<00:06:44.310> one<00:06:44.669> thing 00:06:44.839 --> 00:06:44.849 align:start position:0% know right and you can see one thing 00:06:44.849 --> 00:06:46.580 align:start position:0% know right and you can see one thing that<00:06:44.999> happens<00:06:45.419> that's<00:06:45.599> kind<00:06:45.900> of<00:06:45.990> interesting 00:06:46.580 --> 00:06:46.590 align:start position:0% that happens that's kind of interesting 00:06:46.590 --> 00:06:52.399 align:start position:0% that happens that's kind of interesting is<00:06:46.770> that<00:06:47.129> Zed<00:06:47.879> is<00:06:48.770> handed<00:06:49.770> to<00:06:49.800> two<00:06:50.219> threads<00:06:51.409> so 00:06:52.399 --> 00:06:52.409 align:start position:0% is that Zed is handed to two threads so 00:06:52.409 --> 00:06:53.629 align:start position:0% is that Zed is handed to two threads so we<00:06:52.469> can<00:06:52.620> see<00:06:52.740> this<00:06:52.889> resource<00:06:53.430> is<00:06:53.610> being 00:06:53.629 --> 00:06:53.639 align:start position:0% we can see this resource is being 00:06:53.639 --> 00:06:56.989 align:start position:0% we can see this resource is being utilized<00:06:54.090> by<00:06:54.509> two<00:06:54.659> different<00:06:55.319> threads<00:06:55.699> now<00:06:56.699> in 00:06:56.989 --> 00:06:56.999 align:start position:0% utilized by two different threads now in 00:06:56.999 --> 00:06:58.879 align:start position:0% utilized by two different threads now in in<00:06:57.360> this<00:06:57.539> particular<00:06:57.749> example<00:06:58.199> you<00:06:58.529> can<00:06:58.680> also 00:06:58.879 --> 00:06:58.889 align:start position:0% in this particular example you can also 00:06:58.889 --> 00:07:01.309 align:start position:0% in this particular example you can also see<00:06:59.219> something<00:06:59.639> straight<00:07:00.060> away<00:07:00.389> that<00:07:00.659> our 00:07:01.309 --> 00:07:01.319 align:start position:0% see something straight away that our 00:07:01.319 --> 00:07:04.939 align:start position:0% see something straight away that our compiler<00:07:02.189> can<00:07:02.430> also<00:07:02.580> see<00:07:02.969> that<00:07:03.840> even<00:07:04.680> though 00:07:04.939 --> 00:07:04.949 align:start position:0% compiler can also see that even though 00:07:04.949 --> 00:07:09.019 align:start position:0% compiler can also see that even though there's<00:07:05.580> an<00:07:05.849> illogical<00:07:06.539> parallelism<00:07:08.029> there's 00:07:09.019 --> 00:07:09.029 align:start position:0% there's an illogical parallelism there's 00:07:09.029 --> 00:07:11.959 align:start position:0% there's an illogical parallelism there's actually<00:07:09.779> only<00:07:09.930> one<00:07:10.189> thread<00:07:11.189> of<00:07:11.340> activity 00:07:11.959 --> 00:07:11.969 align:start position:0% actually only one thread of activity 00:07:11.969 --> 00:07:15.320 align:start position:0% actually only one thread of activity which<00:07:12.719> is<00:07:13.020> that<00:07:13.860> this<00:07:14.550> is<00:07:14.729> only<00:07:14.969> gonna 00:07:15.320 --> 00:07:15.330 align:start position:0% which is that this is only gonna 00:07:15.330 --> 00:07:17.629 align:start position:0% which is that this is only gonna activate<00:07:15.990> if<00:07:16.199> it<00:07:16.349> gets<00:07:16.500> something<00:07:16.740> on<00:07:16.949> Zed<00:07:17.279> and 00:07:17.629 --> 00:07:17.639 align:start position:0% activate if it gets something on Zed and 00:07:17.639 --> 00:07:19.879 align:start position:0% activate if it gets something on Zed and there's<00:07:18.210> exactly<00:07:18.659> one<00:07:19.050> thing<00:07:19.259> that's<00:07:19.469> sending 00:07:19.879 --> 00:07:19.889 align:start position:0% there's exactly one thing that's sending 00:07:19.889 --> 00:07:22.550 align:start position:0% there's exactly one thing that's sending on<00:07:20.009> Zed<00:07:20.310> so<00:07:21.150> this<00:07:21.389> is<00:07:21.569> really<00:07:22.050> a<00:07:22.080> sequential 00:07:22.550 --> 00:07:22.560 align:start position:0% on Zed so this is really a sequential 00:07:22.560 --> 00:07:25.129 align:start position:0% on Zed so this is really a sequential flow<00:07:23.300> all<00:07:24.300> right<00:07:24.419> so<00:07:24.539> there<00:07:24.659> are<00:07:24.719> lots<00:07:24.900> and 00:07:25.129 --> 00:07:25.139 align:start position:0% flow all right so there are lots and 00:07:25.139 --> 00:07:26.480 align:start position:0% flow all right so there are lots and lots<00:07:25.289> of<00:07:25.439> things<00:07:25.650> that<00:07:25.770> you<00:07:25.830> can<00:07:26.009> see<00:07:26.189> just<00:07:26.219> by 00:07:26.480 --> 00:07:26.490 align:start position:0% lots of things that you can see just by 00:07:26.490 --> 00:07:28.879 align:start position:0% lots of things that you can see just by staring<00:07:27.000> at<00:07:27.120> the<00:07:27.210> code<00:07:27.449> and<00:07:28.229> in<00:07:28.379> fact<00:07:28.620> that's 00:07:28.879 --> 00:07:28.889 align:start position:0% staring at the code and in fact that's 00:07:28.889 --> 00:07:30.740 align:start position:0% staring at the code and in fact that's what<00:07:29.219> makes<00:07:29.490> rolling<00:07:30.060> kind<00:07:30.360> of<00:07:30.479> cool<00:07:30.719> you 00:07:30.740 --> 00:07:30.750 align:start position:0% what makes rolling kind of cool you 00:07:30.750 --> 00:07:33.679 align:start position:0% what makes rolling kind of cool you stare<00:07:31.650> at<00:07:31.770> the<00:07:31.889> code<00:07:32.129> or<00:07:32.370> you<00:07:32.909> let<00:07:33.120> a<00:07:33.150> computer 00:07:33.679 --> 00:07:33.689 align:start position:0% stare at the code or you let a computer 00:07:33.689 --> 00:07:35.689 align:start position:0% stare at the code or you let a computer stare<00:07:34.020> at<00:07:34.139> the<00:07:34.259> code<00:07:34.469> and<00:07:34.680> it<00:07:35.159> does<00:07:35.310> a<00:07:35.339> bunch<00:07:35.610> of 00:07:35.689 --> 00:07:35.699 align:start position:0% stare at the code and it does a bunch of 00:07:35.699 --> 00:07:41.420 align:start position:0% stare at the code and it does a bunch of analysis<00:07:36.270> for<00:07:36.509> you<00:07:37.430> so<00:07:38.430> in<00:07:38.669> particular<00:07:40.250> if<00:07:41.250> I 00:07:41.420 --> 00:07:41.430 align:start position:0% analysis for you so in particular if I 00:07:41.430 --> 00:07:44.779 align:start position:0% analysis for you so in particular if I remove<00:07:41.819> all<00:07:42.029> that<00:07:42.210> pesky<00:07:42.479> syntax<00:07:43.580> right<00:07:44.580> and 00:07:44.779 --> 00:07:44.789 align:start position:0% remove all that pesky syntax right and 00:07:44.789 --> 00:07:49.159 align:start position:0% remove all that pesky syntax right and just<00:07:45.150> look<00:07:45.449> at<00:07:45.719> at<00:07:46.620> the<00:07:47.069> graph<00:07:47.629> that<00:07:48.629> that<00:07:48.960> is 00:07:49.159 --> 00:07:49.169 align:start position:0% just look at at the graph that that is 00:07:49.169 --> 00:07:54.379 align:start position:0% just look at at the graph that that is is<00:07:50.039> evident<00:07:50.879> in<00:07:51.149> the<00:07:51.319> in<00:07:52.319> the<00:07:52.560> flow<00:07:52.919> here<00:07:53.399> I<00:07:54.029> can 00:07:54.379 --> 00:07:54.389 align:start position:0% is evident in the in the flow here I can 00:07:54.389 --> 00:07:59.329 align:start position:0% is evident in the in the flow here I can see<00:07:54.599> some<00:07:54.810> really<00:07:55.110> cool<00:07:55.379> things<00:07:56.810> one<00:07:57.810> is<00:07:58.339> that 00:07:59.329 --> 00:07:59.339 align:start position:0% see some really cool things one is that 00:07:59.339 --> 00:08:02.209 align:start position:0% see some really cool things one is that every<00:07:59.879> contract<00:08:00.180> is<00:08:00.779> actually<00:08:01.529> just<00:08:01.710> a<00:08:01.889> braid 00:08:02.209 --> 00:08:02.219 align:start position:0% every contract is actually just a braid 00:08:02.219 --> 00:08:06.679 align:start position:0% every contract is actually just a braid or<00:08:02.250> a<00:08:02.520> tangle<00:08:03.319> right<00:08:04.319> here<00:08:05.159> that<00:08:05.460> here's<00:08:05.789> one<00:08:06.330> a 00:08:06.679 --> 00:08:06.689 align:start position:0% or a tangle right here that here's one a 00:08:06.689 --> 00:08:10.339 align:start position:0% or a tangle right here that here's one a set<00:08:07.289> of<00:08:07.699> strands<00:08:08.699> right<00:08:09.599> sometimes<00:08:09.930> the 00:08:10.339 --> 00:08:10.349 align:start position:0% set of strands right sometimes the 00:08:10.349 --> 00:08:13.100 align:start position:0% set of strands right sometimes the strands<00:08:10.649> can<00:08:11.009> fork<00:08:11.430> right<00:08:12.389> and<00:08:12.599> there's 00:08:13.100 --> 00:08:13.110 align:start position:0% strands can fork right and there's 00:08:13.110 --> 00:08:15.439 align:start position:0% strands can fork right and there's another<00:08:13.469> set<00:08:13.949> of<00:08:13.979> strands<00:08:14.430> that<00:08:14.669> weave<00:08:14.969> across 00:08:15.439 --> 00:08:15.449 align:start position:0% another set of strands that weave across 00:08:15.449 --> 00:08:17.570 align:start position:0% another set of strands that weave across these<00:08:15.889> that<00:08:16.889> have<00:08:17.069> to<00:08:17.219> do<00:08:17.339> with<00:08:17.460> the 00:08:17.570 --> 00:08:17.580 align:start position:0% these that have to do with the 00:08:17.580 --> 00:08:22.939 align:start position:0% these that have to do with the information<00:08:18.180> flow<00:08:20.330> this<00:08:21.330> making<00:08:21.719> sense<00:08:21.949> let's 00:08:22.939 --> 00:08:22.949 align:start position:0% information flow this making sense let's 00:08:22.949 --> 00:08:24.950 align:start position:0% information flow this making sense let's make<00:08:23.159> this<00:08:23.279> as<00:08:23.520> interactive<00:08:23.909> as<00:08:24.330> possible<00:08:24.419> if 00:08:24.950 --> 00:08:24.960 align:start position:0% make this as interactive as possible if 00:08:24.960 --> 00:08:27.079 align:start position:0% make this as interactive as possible if you<00:08:24.990> if<00:08:25.319> this<00:08:25.529> doesn't<00:08:25.800> make<00:08:25.979> sense<00:08:26.129> shout<00:08:26.879> out 00:08:27.079 --> 00:08:27.089 align:start position:0% you if this doesn't make sense shout out 00:08:27.089 --> 00:08:31.129 align:start position:0% you if this doesn't make sense shout out I<00:08:27.120> don't<00:08:27.419> get<00:08:27.870> it<00:08:28.129> okay<00:08:29.129> and<00:08:29.339> then<00:08:29.509> so<00:08:30.509> whenever 00:08:31.129 --> 00:08:31.139 align:start position:0% I don't get it okay and then so whenever 00:08:31.139 --> 00:08:33.529 align:start position:0% I don't get it okay and then so whenever we<00:08:31.500> have<00:08:31.529> a<00:08:31.770> weave<00:08:32.159> that<00:08:32.789> goes<00:08:33.000> like<00:08:33.300> this 00:08:33.529 --> 00:08:33.539 align:start position:0% we have a weave that goes like this 00:08:33.539 --> 00:08:37.279 align:start position:0% we have a weave that goes like this across<00:08:34.140> that's<00:08:34.949> a<00:08:35.159> possible<00:08:36.169> contention<00:08:37.169> of 00:08:37.279 --> 00:08:37.289 align:start position:0% across that's a possible contention of 00:08:37.289 --> 00:08:39.649 align:start position:0% across that's a possible contention of resources<00:08:37.919> so<00:08:38.699> we<00:08:38.880> can<00:08:39.060> see<00:08:39.300> that<00:08:39.479> in<00:08:39.630> fact 00:08:39.649 --> 00:08:39.659 align:start position:0% resources so we can see that in fact 00:08:39.659 --> 00:08:42.620 align:start position:0% resources so we can see that in fact there<00:08:40.079> is<00:08:40.199> a<00:08:40.229> tangle<00:08:40.949> across<00:08:41.760> this<00:08:42.089> collection 00:08:42.620 --> 00:08:42.630 align:start position:0% there is a tangle across this collection 00:08:42.630 --> 00:08:46.280 align:start position:0% there is a tangle across this collection of<00:08:42.870> names<00:08:43.339> right<00:08:44.339> and<00:08:44.490> so<00:08:44.610> we<00:08:44.760> have<00:08:45.089> two<00:08:45.360> in<00:08:45.779> and 00:08:46.280 --> 00:08:46.290 align:start position:0% of names right and so we have two in and 00:08:46.290 --> 00:08:47.920 align:start position:0% of names right and so we have two in and it's<00:08:46.440> literally<00:08:46.890> spans 00:08:47.920 --> 00:08:47.930 align:start position:0% it's literally spans 00:08:47.930 --> 00:08:50.980 align:start position:0% it's literally spans the<00:08:48.290> entire<00:08:48.680> collection<00:08:49.250> of<00:08:49.340> names<00:08:49.580> so<00:08:49.940> we<00:08:50.840> can 00:08:50.980 --> 00:08:50.990 align:start position:0% the entire collection of names so we can 00:08:50.990 --> 00:08:53.080 align:start position:0% the entire collection of names so we can see<00:08:51.290> that<00:08:51.560> relative<00:08:51.800> to<00:08:52.280> this<00:08:52.430> set<00:08:52.730> of<00:08:52.760> names 00:08:53.080 --> 00:08:53.090 align:start position:0% see that relative to this set of names 00:08:53.090 --> 00:08:55.720 align:start position:0% see that relative to this set of names we<00:08:53.990> have<00:08:54.230> to<00:08:54.410> make<00:08:54.560> sure<00:08:54.590> that<00:08:54.830> transactions 00:08:55.720 --> 00:08:55.730 align:start position:0% we have to make sure that transactions 00:08:55.730 --> 00:08:58.540 align:start position:0% we have to make sure that transactions are<00:08:55.850> ordered<00:08:56.500> right<00:08:57.500> we<00:08:57.680> have<00:08:57.830> to<00:08:57.950> be<00:08:58.070> careful 00:08:58.540 --> 00:08:58.550 align:start position:0% are ordered right we have to be careful 00:08:58.550 --> 00:09:01.300 align:start position:0% are ordered right we have to be careful about<00:08:58.640> the<00:08:58.970> order<00:08:59.210> of<00:08:59.240> transactions<00:09:00.310> names 00:09:01.300 --> 00:09:01.310 align:start position:0% about the order of transactions names 00:09:01.310 --> 00:09:04.450 align:start position:0% about the order of transactions names outside<00:09:02.030> of<00:09:02.240> this<00:09:02.420> set<00:09:02.780> we<00:09:03.590> don't<00:09:03.800> care<00:09:04.250> about 00:09:04.450 --> 00:09:04.460 align:start position:0% outside of this set we don't care about 00:09:04.460 --> 00:09:06.040 align:start position:0% outside of this set we don't care about the<00:09:04.700> order<00:09:04.970> of<00:09:05.060> transactions<00:09:05.690> and<00:09:05.900> let's 00:09:06.040 --> 00:09:06.050 align:start position:0% the order of transactions and let's 00:09:06.050 --> 00:09:09.100 align:start position:0% the order of transactions and let's taste<00:09:06.260> touch<00:09:06.650> this<00:09:06.980> set<00:09:07.570> right<00:09:08.570> and<00:09:08.930> we<00:09:09.020> can 00:09:09.100 --> 00:09:09.110 align:start position:0% taste touch this set right and we can 00:09:09.110 --> 00:09:33.500 align:start position:0% taste touch this set right and we can actually<00:09:09.260> see<00:09:09.620> that<00:09:09.830> yes<00:09:12.130> please<00:09:17.800> yeah<00:09:18.800> yeah 00:09:33.500 --> 00:09:33.510 align:start position:0% 00:09:33.510 --> 00:09:44.390 align:start position:0% yes 00:09:44.390 --> 00:09:44.400 align:start position:0% 00:09:44.400 --> 00:09:47.190 align:start position:0% know<00:09:45.400> if<00:09:45.670> you'll<00:09:45.820> if<00:09:46.030> you'll<00:09:46.180> notice<00:09:46.450> that 00:09:47.190 --> 00:09:47.200 align:start position:0% know if you'll if you'll notice that 00:09:47.200 --> 00:09:51.560 align:start position:0% know if you'll if you'll notice that this<00:09:47.560> is<00:09:47.950> nested<00:09:48.460> inside<00:09:48.640> this<00:09:49.120> scope<00:09:49.510> here 00:09:51.560 --> 00:09:51.570 align:start position:0% this is nested inside this scope here 00:09:51.570 --> 00:09:54.750 align:start position:0% this is nested inside this scope here right<00:09:52.570> so<00:09:52.780> it's<00:09:52.990> blocked<00:09:53.410> until<00:09:53.770> you<00:09:53.920> get<00:09:54.100> both 00:09:54.750 --> 00:09:54.760 align:start position:0% right so it's blocked until you get both 00:09:54.760 --> 00:09:59.640 align:start position:0% right so it's blocked until you get both of<00:09:54.790> them<00:09:56.760> yeah<00:09:57.760> exactly<00:09:57.910> it's<00:09:58.480> a<00:09:58.990> graphical 00:09:59.640 --> 00:09:59.650 align:start position:0% of them yeah exactly it's a graphical 00:09:59.650 --> 00:10:02.490 align:start position:0% of them yeah exactly it's a graphical way<00:09:59.770> of<00:09:59.890> representing<00:10:00.790> that<00:10:00.850> barrier<00:10:01.500> yeah 00:10:02.490 --> 00:10:02.500 align:start position:0% way of representing that barrier yeah 00:10:02.500 --> 00:10:11.190 align:start position:0% way of representing that barrier yeah exactly<00:10:02.800> right<00:10:03.100> good<00:10:03.580> question<00:10:04.030> yes<00:10:09.930> yes<00:10:10.930> the 00:10:11.190 --> 00:10:11.200 align:start position:0% exactly right good question yes yes the 00:10:11.200 --> 00:10:13.530 align:start position:0% exactly right good question yes yes the vertical<00:10:11.590> bar<00:10:11.770> is<00:10:11.800> here<00:10:12.340> that<00:10:12.850> that's<00:10:13.060> exactly 00:10:13.530 --> 00:10:13.540 align:start position:0% vertical bar is here that that's exactly 00:10:13.540 --> 00:10:15.920 align:start position:0% vertical bar is here that that's exactly right 00:10:15.920 --> 00:10:15.930 align:start position:0% 00:10:15.930 --> 00:10:18.900 align:start position:0% no<00:10:16.930> it's<00:10:17.320> it's<00:10:17.620> it's<00:10:17.800> actually<00:10:18.010> true<00:10:18.550> it<00:10:18.730> can 00:10:18.900 --> 00:10:18.910 align:start position:0% no it's it's it's actually true it can 00:10:18.910 --> 00:10:21.030 align:start position:0% no it's it's it's actually true it can be<00:10:19.030> interpreted<00:10:19.360> as<00:10:19.630> true<00:10:19.840> parallelism<00:10:20.410> it 00:10:21.030 --> 00:10:21.040 align:start position:0% be interpreted as true parallelism it 00:10:21.040 --> 00:10:22.620 align:start position:0% be interpreted as true parallelism it can<00:10:21.190> be<00:10:21.280> it<00:10:21.520> can<00:10:21.550> be<00:10:21.790> interpreted<00:10:22.090> as<00:10:22.450> an 00:10:22.620 --> 00:10:22.630 align:start position:0% can be it can be interpreted as an 00:10:22.630 --> 00:10:24.180 align:start position:0% can be it can be interpreted as an interleaving<00:10:23.260> or<00:10:23.380> it<00:10:23.470> can<00:10:23.590> be<00:10:23.680> interpreted<00:10:23.950> as 00:10:24.180 --> 00:10:24.190 align:start position:0% interleaving or it can be interpreted as 00:10:24.190 --> 00:10:25.740 align:start position:0% interleaving or it can be interpreted as true<00:10:24.370> parallelism<00:10:24.820> thank<00:10:25.360> you<00:10:25.450> that's<00:10:25.630> a<00:10:25.720> very 00:10:25.740 --> 00:10:25.750 align:start position:0% true parallelism thank you that's a very 00:10:25.750 --> 00:10:26.490 align:start position:0% true parallelism thank you that's a very good<00:10:26.080> question 00:10:26.490 --> 00:10:26.500 align:start position:0% good question 00:10:26.500 --> 00:10:34.470 align:start position:0% good question awesome<00:10:28.590> okay<00:10:29.590> so<00:10:30.220> moving<00:10:31.060> right<00:10:31.120> along<00:10:33.240> so<00:10:34.240> we 00:10:34.470 --> 00:10:34.480 align:start position:0% awesome okay so moving right along so we 00:10:34.480 --> 00:10:37.170 align:start position:0% awesome okay so moving right along so we can<00:10:34.660> now<00:10:34.780> make<00:10:34.810> a<00:10:35.050> test<00:10:35.410> harness<00:10:35.620> for<00:10:36.040> this<00:10:36.190> so 00:10:37.170 --> 00:10:37.180 align:start position:0% can now make a test harness for this so 00:10:37.180 --> 00:10:40.080 align:start position:0% can now make a test harness for this so what<00:10:37.600> we're<00:10:37.750> gonna<00:10:37.810> do<00:10:38.080> to<00:10:38.230> test<00:10:38.500> this<00:10:38.770> code<00:10:39.160> or 00:10:40.080 --> 00:10:40.090 align:start position:0% what we're gonna do to test this code or 00:10:40.090 --> 00:10:42.360 align:start position:0% what we're gonna do to test this code or to<00:10:40.570> at<00:10:40.660> least<00:10:40.780> understand<00:10:41.380> what<00:10:41.590> it<00:10:41.710> does<00:10:41.920> is 00:10:42.360 --> 00:10:42.370 align:start position:0% to at least understand what it does is 00:10:42.370 --> 00:10:45.630 align:start position:0% to at least understand what it does is we're<00:10:42.940> gonna<00:10:43.060> set<00:10:43.510> P<00:10:43.990> and<00:10:44.200> Q<00:10:44.650> to<00:10:45.040> just<00:10:45.220> be<00:10:45.370> 0 00:10:45.630 --> 00:10:45.640 align:start position:0% we're gonna set P and Q to just be 0 00:10:45.640 --> 00:10:48.150 align:start position:0% we're gonna set P and Q to just be 0 don't<00:10:46.000> do<00:10:46.180> anything<00:10:46.450> right<00:10:47.440> for<00:10:47.740> this<00:10:47.860> and 00:10:48.150 --> 00:10:48.160 align:start position:0% don't do anything right for this and 00:10:48.160 --> 00:10:51.030 align:start position:0% don't do anything right for this and then<00:10:48.520> we're<00:10:49.210> going<00:10:49.240> to<00:10:49.570> make<00:10:50.410> some<00:10:50.740> fresh 00:10:51.030 --> 00:10:51.040 align:start position:0% then we're going to make some fresh 00:10:51.040 --> 00:10:53.910 align:start position:0% then we're going to make some fresh channels<00:10:51.870> right<00:10:52.870> that's<00:10:53.080> what<00:10:53.260> this<00:10:53.350> new<00:10:53.650> does 00:10:53.910 --> 00:10:53.920 align:start position:0% channels right that's what this new does 00:10:53.920 --> 00:10:56.580 align:start position:0% channels right that's what this new does and<00:10:54.790> we're<00:10:55.300> gonna<00:10:55.420> supply<00:10:55.870> them<00:10:56.230> to<00:10:56.470> the 00:10:56.580 --> 00:10:56.590 align:start position:0% and we're gonna supply them to the 00:10:56.590 --> 00:10:57.480 align:start position:0% and we're gonna supply them to the contract 00:10:57.480 --> 00:10:57.490 align:start position:0% contract 00:10:57.490 --> 00:10:59.880 align:start position:0% contract I<00:10:57.520> want<00:10:58.270> to<00:10:58.360> supply<00:10:59.110> them<00:10:59.350> to<00:10:59.380> things<00:10:59.800> that 00:10:59.880 --> 00:10:59.890 align:start position:0% I want to supply them to things that 00:10:59.890 --> 00:11:02.880 align:start position:0% I want to supply them to things that could<00:11:00.190> interact<00:11:00.490> with<00:11:00.760> the<00:11:00.940> contract<00:11:01.830> okay<00:11:02.830> so 00:11:02.880 --> 00:11:02.890 align:start position:0% could interact with the contract okay so 00:11:02.890 --> 00:11:06.270 align:start position:0% could interact with the contract okay so here<00:11:03.700> is<00:11:03.850> our<00:11:04.810> input<00:11:05.020> section<00:11:05.800> which<00:11:05.980> is<00:11:06.130> going 00:11:06.270 --> 00:11:06.280 align:start position:0% here is our input section which is going 00:11:06.280 --> 00:11:10.320 align:start position:0% here is our input section which is going to<00:11:06.430> input<00:11:06.610> we're<00:11:07.450> at<00:11:07.720> X<00:11:08.050> and<00:11:08.290> u<00:11:08.410> and<00:11:09.180> here<00:11:10.180> is 00:11:10.320 --> 00:11:10.330 align:start position:0% to input we're at X and u and here is 00:11:10.330 --> 00:11:13.050 align:start position:0% to input we're at X and u and here is our<00:11:10.480> readout<00:11:11.340> this<00:11:12.340> is<00:11:12.460> going<00:11:12.670> to<00:11:12.760> interact 00:11:13.050 --> 00:11:13.060 align:start position:0% our readout this is going to interact 00:11:13.060 --> 00:11:16.890 align:start position:0% our readout this is going to interact with<00:11:13.330> C<00:11:13.690> at<00:11:13.930> a<00:11:14.770> and<00:11:15.760> whatever<00:11:16.000> the<00:11:16.270> result<00:11:16.630> is 00:11:16.890 --> 00:11:16.900 align:start position:0% with C at a and whatever the result is 00:11:16.900 --> 00:11:20.760 align:start position:0% with C at a and whatever the result is it's<00:11:17.710> going<00:11:17.980> to<00:11:18.070> print<00:11:18.430> that<00:11:18.610> out<00:11:19.590> is<00:11:20.590> that 00:11:20.760 --> 00:11:20.770 align:start position:0% it's going to print that out is that 00:11:20.770 --> 00:11:25.800 align:start position:0% it's going to print that out is that making<00:11:20.950> sense<00:11:22.140> awesome<00:11:23.140> okay<00:11:24.010> so<00:11:24.580> what<00:11:25.390> well 00:11:25.800 --> 00:11:25.810 align:start position:0% making sense awesome okay so what well 00:11:25.810 --> 00:11:27.930 align:start position:0% making sense awesome okay so what well what<00:11:26.110> you<00:11:26.230> can<00:11:26.440> you<00:11:26.920> can<00:11:27.070> immediately<00:11:27.340> see 00:11:27.930 --> 00:11:27.940 align:start position:0% what you can you can immediately see 00:11:27.940 --> 00:11:30.270 align:start position:0% what you can you can immediately see from<00:11:28.210> the<00:11:28.330> code<00:11:28.660> is<00:11:29.020> that<00:11:29.350> that<00:11:29.680> will<00:11:29.860> print 00:11:30.270 --> 00:11:30.280 align:start position:0% from the code is that that will print 00:11:30.280 --> 00:11:35.550 align:start position:0% from the code is that that will print out<00:11:31.740> the<00:11:32.740> resulting<00:11:33.250> value<00:11:33.580> is<00:11:33.730> 6<00:11:34.060> and<00:11:34.630> that's 00:11:35.550 --> 00:11:35.560 align:start position:0% out the resulting value is 6 and that's 00:11:35.560 --> 00:11:40.790 align:start position:0% out the resulting value is 6 and that's that's<00:11:35.830> immediate<00:11:36.400> from<00:11:36.550> the<00:11:36.640> code<00:11:36.820> yes<00:11:37.180> oh 00:11:40.790 --> 00:11:40.800 align:start position:0% 00:11:40.800 --> 00:11:43.770 align:start position:0% thank<00:11:41.800> you<00:11:41.920> that's<00:11:42.100> a<00:11:42.190> typo<00:11:42.520> yes<00:11:42.820> good<00:11:43.570> good 00:11:43.770 --> 00:11:43.780 align:start position:0% thank you that's a typo yes good good 00:11:43.780 --> 00:11:47.910 align:start position:0% thank you that's a typo yes good good good<00:11:43.930> eyes<00:11:44.110> thank<00:11:44.410> you<00:11:44.560> I<00:11:44.770> appreciate<00:11:45.100> that<00:11:46.920> so 00:11:47.910 --> 00:11:47.920 align:start position:0% good eyes thank you I appreciate that so 00:11:47.920 --> 00:11:51.690 align:start position:0% good eyes thank you I appreciate that so here<00:11:48.520> is<00:11:48.700> the<00:11:49.000> picture<00:11:49.210> of<00:11:49.630> that<00:11:50.130> just<00:11:51.130> just<00:11:51.520> in 00:11:51.690 --> 00:11:51.700 align:start position:0% here is the picture of that just just in 00:11:51.700 --> 00:11:55.890 align:start position:0% here is the picture of that just just in blocks<00:11:53.310> so<00:11:54.310> here's<00:11:54.670> the<00:11:54.820> input<00:11:54.970> section<00:11:55.450> it's 00:11:55.890 --> 00:11:55.900 align:start position:0% blocks so here's the input section it's 00:11:55.900 --> 00:11:57.979 align:start position:0% blocks so here's the input section it's running<00:11:56.320> in<00:11:56.440> parallel<00:11:56.650> with<00:11:57.070> the<00:11:57.160> contract 00:11:57.979 --> 00:11:57.989 align:start position:0% running in parallel with the contract 00:11:57.989 --> 00:12:01.439 align:start position:0% running in parallel with the contract here's<00:11:58.989> the<00:11:59.169> output<00:11:59.649> section<00:12:00.059> it's<00:12:01.059> running 00:12:01.439 --> 00:12:01.449 align:start position:0% here's the output section it's running 00:12:01.449 --> 00:12:03.780 align:start position:0% here's the output section it's running in<00:12:01.540> parallel<00:12:01.929> with<00:12:02.079> the<00:12:02.169> contract<00:12:02.679> right<00:12:03.549> and 00:12:03.780 --> 00:12:03.790 align:start position:0% in parallel with the contract right and 00:12:03.790 --> 00:12:05.939 align:start position:0% in parallel with the contract right and so<00:12:04.179> the<00:12:04.299> contract<00:12:04.809> interacts<00:12:05.319> with<00:12:05.499> this<00:12:05.649> test 00:12:05.939 --> 00:12:05.949 align:start position:0% so the contract interacts with this test 00:12:05.949 --> 00:12:07.799 align:start position:0% so the contract interacts with this test harness<00:12:06.369> in<00:12:06.759> this<00:12:07.389> way 00:12:07.799 --> 00:12:07.809 align:start position:0% harness in this way 00:12:07.809 --> 00:12:10.979 align:start position:0% harness in this way and<00:12:07.899> there's<00:12:08.889> the<00:12:09.129> new<00:12:09.369> scope<00:12:09.790> that<00:12:10.419> allows<00:12:10.720> us 00:12:10.979 --> 00:12:10.989 align:start position:0% and there's the new scope that allows us 00:12:10.989 --> 00:12:13.369 align:start position:0% and there's the new scope that allows us to<00:12:11.169> see<00:12:11.350> the<00:12:11.379> origin<00:12:12.100> of<00:12:12.279> all<00:12:12.399> the<00:12:12.579> channels 00:12:13.369 --> 00:12:13.379 align:start position:0% to see the origin of all the channels 00:12:13.379 --> 00:12:17.400 align:start position:0% to see the origin of all the channels it's<00:12:14.379> that<00:12:14.499> making<00:12:14.799> sense<00:12:15.809> okay<00:12:16.809> so<00:12:17.169> we<00:12:17.259> have<00:12:17.379> a 00:12:17.400 --> 00:12:17.410 align:start position:0% it's that making sense okay so we have a 00:12:17.410 --> 00:12:21.449 align:start position:0% it's that making sense okay so we have a nice<00:12:17.679> clear<00:12:18.869> graphical<00:12:19.869> interpretation<00:12:20.459> that 00:12:21.449 --> 00:12:21.459 align:start position:0% nice clear graphical interpretation that 00:12:21.459 --> 00:12:24.989 align:start position:0% nice clear graphical interpretation that allows<00:12:21.790> us<00:12:21.819> to<00:12:22.329> to<00:12:23.079> just<00:12:23.619> inspect<00:12:24.549> the 00:12:24.989 --> 00:12:24.999 align:start position:0% allows us to to just inspect the 00:12:24.999 --> 00:12:26.789 align:start position:0% allows us to to just inspect the concurrency<00:12:25.660> behavior<00:12:26.109> of<00:12:26.259> the<00:12:26.379> code<00:12:26.559> and 00:12:26.789 --> 00:12:26.799 align:start position:0% concurrency behavior of the code and 00:12:26.799 --> 00:12:29.729 align:start position:0% concurrency behavior of the code and just<00:12:26.859> see<00:12:27.449> what's<00:12:28.449> going<00:12:28.720> on<00:12:28.839> so<00:12:29.079> let's<00:12:29.290> let's 00:12:29.729 --> 00:12:29.739 align:start position:0% just see what's going on so let's let's 00:12:29.739 --> 00:12:32.220 align:start position:0% just see what's going on so let's let's move<00:12:29.949> right<00:12:30.249> along<00:12:30.399> and<00:12:30.910> introduce<00:12:31.509> some<00:12:32.079> non 00:12:32.220 --> 00:12:32.230 align:start position:0% move right along and introduce some non 00:12:32.230 --> 00:12:34.169 align:start position:0% move right along and introduce some non determinism<00:12:32.769> we<00:12:32.980> could<00:12:33.189> see<00:12:33.489> with<00:12:33.730> our<00:12:33.759> eyes 00:12:34.169 --> 00:12:34.179 align:start position:0% determinism we could see with our eyes 00:12:34.179 --> 00:12:36.419 align:start position:0% determinism we could see with our eyes that<00:12:35.049> there<00:12:35.199> wasn't<00:12:35.379> any<00:12:35.709> real<00:12:36.160> non 00:12:36.419 --> 00:12:36.429 align:start position:0% that there wasn't any real non 00:12:36.429 --> 00:12:39.569 align:start position:0% that there wasn't any real non determinism<00:12:36.939> except<00:12:37.509> at<00:12:37.660> the<00:12:37.749> edges<00:12:38.249> right<00:12:39.249> so 00:12:39.569 --> 00:12:39.579 align:start position:0% determinism except at the edges right so 00:12:39.579 --> 00:12:41.220 align:start position:0% determinism except at the edges right so there<00:12:39.759> could<00:12:40.029> have<00:12:40.059> been<00:12:40.209> hello<00:12:40.689> just<00:12:40.929> just<00:12:41.109> to 00:12:41.220 --> 00:12:41.230 align:start position:0% there could have been hello just just to 00:12:41.230 --> 00:12:45.900 align:start position:0% there could have been hello just just to make<00:12:41.410> that<00:12:41.559> point<00:12:41.619> very<00:12:42.459> clear<00:12:44.609> there<00:12:45.609> could 00:12:45.900 --> 00:12:45.910 align:start position:0% make that point very clear there could 00:12:45.910 --> 00:12:51.299 align:start position:0% make that point very clear there could have<00:12:45.939> been<00:12:46.089> non<00:12:46.809> determinism<00:12:48.569> here<00:12:49.569> if<00:12:50.309> there 00:12:51.299 --> 00:12:51.309 align:start position:0% have been non determinism here if there 00:12:51.309 --> 00:12:54.720 align:start position:0% have been non determinism here if there were<00:12:51.429> contending<00:12:52.239> inputs<00:12:53.100> right<00:12:54.100> and<00:12:54.339> there 00:12:54.720 --> 00:12:54.730 align:start position:0% were contending inputs right and there 00:12:54.730 --> 00:12:56.789 align:start position:0% were contending inputs right and there could<00:12:54.910> have<00:12:54.939> been<00:12:55.059> non<00:12:55.329> determinism<00:12:55.929> here<00:12:56.649> if 00:12:56.789 --> 00:12:56.799 align:start position:0% could have been non determinism here if 00:12:56.799 --> 00:12:59.460 align:start position:0% could have been non determinism here if there<00:12:57.399> were<00:12:57.549> contending<00:12:58.179> listeners<00:12:59.169> for<00:12:59.379> the 00:12:59.460 --> 00:12:59.470 align:start position:0% there were contending listeners for the 00:12:59.470 --> 00:13:02.759 align:start position:0% there were contending listeners for the output<00:12:59.859> but<00:13:00.759> the<00:13:00.790> the<00:13:01.299> contract<00:13:01.779> itself<00:13:02.139> even 00:13:02.759 --> 00:13:02.769 align:start position:0% output but the the contract itself even 00:13:02.769 --> 00:13:04.529 align:start position:0% output but the the contract itself even though<00:13:02.980> it<00:13:03.100> has<00:13:03.309> parallelism<00:13:03.850> in<00:13:04.209> it<00:13:04.359> is 00:13:04.529 --> 00:13:04.539 align:start position:0% though it has parallelism in it is 00:13:04.539 --> 00:13:07.970 align:start position:0% though it has parallelism in it is actually<00:13:05.019> deterministic<00:13:05.889> in<00:13:06.039> its<00:13:06.209> in<00:13:07.209> its 00:13:07.970 --> 00:13:07.980 align:start position:0% actually deterministic in its in its 00:13:07.980 --> 00:13:12.509 align:start position:0% actually deterministic in its in its execution<00:13:09.839> so<00:13:10.839> now<00:13:11.049> what<00:13:11.439> we<00:13:11.559> do<00:13:11.709> is<00:13:11.859> we<00:13:11.980> modify 00:13:12.509 --> 00:13:12.519 align:start position:0% execution so now what we do is we modify 00:13:12.519 --> 00:13:17.069 align:start position:0% execution so now what we do is we modify our<00:13:12.549> contract<00:13:13.269> and<00:13:14.999> we<00:13:15.999> add<00:13:16.179> another<00:13:16.539> listener 00:13:17.069 --> 00:13:17.079 align:start position:0% our contract and we add another listener 00:13:17.079 --> 00:13:19.619 align:start position:0% our contract and we add another listener on<00:13:17.259> Zed<00:13:18.480> okay 00:13:19.619 --> 00:13:19.629 align:start position:0% on Zed okay 00:13:19.629 --> 00:13:23.970 align:start position:0% on Zed okay and<00:13:19.749> now<00:13:20.679> these<00:13:21.129> two<00:13:21.459> are<00:13:21.579> contending<00:13:22.269> and<00:13:22.980> all 00:13:23.970 --> 00:13:23.980 align:start position:0% and now these two are contending and all 00:13:23.980 --> 00:13:26.159 align:start position:0% and now these two are contending and all we're<00:13:24.189> doing<00:13:24.459> is<00:13:24.669> if<00:13:24.939> you<00:13:25.179> if<00:13:25.480> this<00:13:25.749> listener 00:13:26.159 --> 00:13:26.169 align:start position:0% we're doing is if you if this listener 00:13:26.169 --> 00:13:29.970 align:start position:0% we're doing is if you if this listener wins<00:13:26.470> you<00:13:27.249> get<00:13:27.429> an<00:13:27.579> even<00:13:27.970> value<00:13:27.999> and<00:13:28.809> if<00:13:29.799> this 00:13:29.970 --> 00:13:29.980 align:start position:0% wins you get an even value and if this 00:13:29.980 --> 00:13:33.139 align:start position:0% wins you get an even value and if this listener<00:13:30.399> wins<00:13:30.609> you<00:13:30.850> get<00:13:31.029> an<00:13:31.149> odd<00:13:31.359> value<00:13:31.959> right 00:13:33.139 --> 00:13:33.149 align:start position:0% listener wins you get an odd value right 00:13:33.149 --> 00:13:35.549 align:start position:0% listener wins you get an odd value right that's<00:13:34.149> that's<00:13:34.509> all<00:13:34.749> that's<00:13:34.899> happening<00:13:35.109> this 00:13:35.549 --> 00:13:35.559 align:start position:0% that's that's all that's happening this 00:13:35.559 --> 00:13:37.039 align:start position:0% that's that's all that's happening this is<00:13:35.739> so<00:13:35.980> boring 00:13:37.039 --> 00:13:37.049 align:start position:0% is so boring 00:13:37.049 --> 00:13:40.079 align:start position:0% is so boring why<00:13:38.049> is<00:13:38.949> this<00:13:39.069> guy<00:13:39.249> talking<00:13:39.519> about<00:13:39.789> this<00:13:39.910> stuff 00:13:40.079 --> 00:13:40.089 align:start position:0% why is this guy talking about this stuff 00:13:40.089 --> 00:13:46.319 align:start position:0% why is this guy talking about this stuff it's<00:13:40.299> so<00:13:40.419> obvious<00:13:43.529> so<00:13:44.529> so<00:13:45.009> again<00:13:45.329> pictorially 00:13:46.319 --> 00:13:46.329 align:start position:0% it's so obvious so so again pictorially 00:13:46.329 --> 00:13:48.840 align:start position:0% it's so obvious so so again pictorially we<00:13:47.199> now<00:13:47.379> have<00:13:47.619> a<00:13:47.649> source<00:13:48.009> of<00:13:48.160> non<00:13:48.339> determinism 00:13:48.840 --> 00:13:48.850 align:start position:0% we now have a source of non determinism 00:13:48.850 --> 00:13:51.150 align:start position:0% we now have a source of non determinism because<00:13:49.209> this<00:13:49.389> output<00:13:49.959> can<00:13:50.350> either<00:13:50.559> line<00:13:50.949> up 00:13:51.150 --> 00:13:51.160 align:start position:0% because this output can either line up 00:13:51.160 --> 00:13:54.479 align:start position:0% because this output can either line up with<00:13:51.309> the<00:13:51.429> input<00:13:52.149> here<00:13:52.539> or<00:13:52.749> the<00:13:53.619> input<00:13:54.069> here 00:13:54.479 --> 00:13:54.489 align:start position:0% with the input here or the input here 00:13:54.489 --> 00:13:57.509 align:start position:0% with the input here or the input here and<00:13:54.720> that<00:13:55.720> raises<00:13:56.019> our<00:13:56.439> interesting<00:13:57.100> question 00:13:57.509 --> 00:13:57.519 align:start position:0% and that raises our interesting question 00:13:57.519 --> 00:13:59.869 align:start position:0% and that raises our interesting question with<00:13:57.639> respect<00:13:57.819> to<00:13:58.059> blockchain<00:13:58.600> semantics 00:13:59.869 --> 00:13:59.879 align:start position:0% with respect to blockchain semantics 00:13:59.879 --> 00:14:03.960 align:start position:0% with respect to blockchain semantics right<00:14:00.879> how<00:14:01.389> do<00:14:01.449> you<00:14:01.869> guarantee<00:14:02.139> if<00:14:02.799> I<00:14:03.129> had<00:14:03.429> many 00:14:03.960 --> 00:14:03.970 align:start position:0% right how do you guarantee if I had many 00:14:03.970 --> 00:14:06.210 align:start position:0% right how do you guarantee if I had many many<00:14:04.149> instances<00:14:05.139> of<00:14:05.199> this<00:14:05.410> very<00:14:05.860> same 00:14:06.210 --> 00:14:06.220 align:start position:0% many instances of this very same 00:14:06.220 --> 00:14:09.479 align:start position:0% many instances of this very same contract<00:14:06.850> running<00:14:07.409> how<00:14:08.409> do<00:14:08.470> I<00:14:08.619> make<00:14:08.949> sure<00:14:09.220> that 00:14:09.479 --> 00:14:09.489 align:start position:0% contract running how do I make sure that 00:14:09.489 --> 00:14:11.010 align:start position:0% contract running how do I make sure that they<00:14:09.639> all<00:14:09.909> win<00:14:10.299> the<00:14:10.689> Ray 00:14:11.010 --> 00:14:11.020 align:start position:0% they all win the Ray 00:14:11.020 --> 00:14:16.440 align:start position:0% they all win the Ray exactly<00:14:11.830> the<00:14:11.980> same<00:14:12.220> way<00:14:14.820> and<00:14:15.820> that's<00:14:16.270> the 00:14:16.440 --> 00:14:16.450 align:start position:0% exactly the same way and that's the 00:14:16.450 --> 00:14:18.480 align:start position:0% exactly the same way and that's the answer<00:14:17.280> okay 00:14:18.480 --> 00:14:18.490 align:start position:0% answer okay 00:14:18.490 --> 00:14:20.250 align:start position:0% answer okay but<00:14:18.970> I'll<00:14:19.060> get<00:14:19.240> to<00:14:19.360> that<00:14:19.390> in<00:14:19.540> just<00:14:19.630> a<00:14:19.870> second 00:14:20.250 --> 00:14:20.260 align:start position:0% but I'll get to that in just a second 00:14:20.260 --> 00:14:22.530 align:start position:0% but I'll get to that in just a second because<00:14:21.190> there's<00:14:21.550> another<00:14:21.790> important<00:14:22.330> point 00:14:22.530 --> 00:14:22.540 align:start position:0% because there's another important point 00:14:22.540 --> 00:14:27.090 align:start position:0% because there's another important point here<00:14:22.810> so<00:14:23.320> I<00:14:23.350> can<00:14:23.650> now<00:14:24.060> generalize<00:14:25.060> Kay<00:14:26.100> right 00:14:27.090 --> 00:14:27.100 align:start position:0% here so I can now generalize Kay right 00:14:27.100 --> 00:14:29.310 align:start position:0% here so I can now generalize Kay right so<00:14:27.340> I<00:14:27.370> can<00:14:27.580> generalize<00:14:28.090> my<00:14:28.300> test<00:14:28.630> harness<00:14:29.050> and 00:14:29.310 --> 00:14:29.320 align:start position:0% so I can generalize my test harness and 00:14:29.320 --> 00:14:32.130 align:start position:0% so I can generalize my test harness and what<00:14:29.740> I<00:14:29.770> do<00:14:29.890> is<00:14:30.310> here's<00:14:31.270> here's<00:14:31.630> the<00:14:31.810> test 00:14:32.130 --> 00:14:32.140 align:start position:0% what I do is here's here's the test 00:14:32.140 --> 00:14:34.290 align:start position:0% what I do is here's here's the test harness<00:14:32.410> bit<00:14:32.860> and<00:14:33.130> that's<00:14:33.520> where<00:14:33.700> I<00:14:33.730> put<00:14:34.000> C 00:14:34.290 --> 00:14:34.300 align:start position:0% harness bit and that's where I put C 00:14:34.300 --> 00:14:38.760 align:start position:0% harness bit and that's where I put C before<00:14:34.950> so<00:14:35.950> I<00:14:36.010> make<00:14:36.520> I<00:14:36.550> make<00:14:36.850> a<00:14:37.030> K<00:14:37.930> in<00:14:38.350> the 00:14:38.760 --> 00:14:38.770 align:start position:0% before so I make I make a K in the 00:14:38.770 --> 00:14:41.520 align:start position:0% before so I make I make a K in the literature<00:14:39.310> of<00:14:39.340> process<00:14:39.970> calculate<00:14:40.570> use<00:14:41.290> the 00:14:41.520 --> 00:14:41.530 align:start position:0% literature of process calculate use the 00:14:41.530 --> 00:14:43.200 align:start position:0% literature of process calculate use the and<00:14:42.010> in<00:14:42.130> fact<00:14:42.340> in<00:14:42.520> programming<00:14:42.940> language 00:14:43.200 --> 00:14:43.210 align:start position:0% and in fact in programming language 00:14:43.210 --> 00:14:45.660 align:start position:0% and in fact in programming language semantics<00:14:43.720> in<00:14:43.840> general<00:14:44.260> it<00:14:44.710> usually<00:14:45.310> is<00:14:45.430> used 00:14:45.660 --> 00:14:45.670 align:start position:0% semantics in general it usually is used 00:14:45.670 --> 00:14:48.630 align:start position:0% semantics in general it usually is used to<00:14:45.880> range<00:14:46.240> over<00:14:46.710> contexts<00:14:47.710> which<00:14:48.430> are 00:14:48.630 --> 00:14:48.640 align:start position:0% to range over contexts which are 00:14:48.640 --> 00:14:51.110 align:start position:0% to range over contexts which are programs<00:14:49.180> where<00:14:49.360> you've<00:14:49.600> knocked<00:14:49.840> a<00:14:50.020> hole<00:14:50.230> and 00:14:51.110 --> 00:14:51.120 align:start position:0% programs where you've knocked a hole and 00:14:51.120 --> 00:14:54.300 align:start position:0% programs where you've knocked a hole and in<00:14:52.120> general<00:14:52.780> we<00:14:52.900> want<00:14:53.140> programs<00:14:53.920> to<00:14:54.190> be 00:14:54.300 --> 00:14:54.310 align:start position:0% in general we want programs to be 00:14:54.310 --> 00:14:57.480 align:start position:0% in general we want programs to be equivalent<00:14:55.590> exactly<00:14:56.590> when<00:14:56.710> they<00:14:56.830> behave<00:14:57.220> the 00:14:57.480 --> 00:14:57.490 align:start position:0% equivalent exactly when they behave the 00:14:57.490 --> 00:15:00.330 align:start position:0% equivalent exactly when they behave the same<00:14:57.700> in<00:14:57.910> all<00:14:58.030> contexts<00:14:58.770> right<00:14:59.770> so<00:14:59.950> what<00:15:00.250> I'm 00:15:00.330 --> 00:15:00.340 align:start position:0% same in all contexts right so what I'm 00:15:00.340 --> 00:15:02.100 align:start position:0% same in all contexts right so what I'm doing<00:15:00.580> is<00:15:00.670> I'm<00:15:00.790> kind<00:15:00.970> of<00:15:01.060> sneaking<00:15:01.480> in<00:15:01.780> just<00:15:01.990> a 00:15:02.100 --> 00:15:02.110 align:start position:0% doing is I'm kind of sneaking in just a 00:15:02.110 --> 00:15:04.170 align:start position:0% doing is I'm kind of sneaking in just a tiny<00:15:02.500> little<00:15:03.010> bit<00:15:03.310> of<00:15:03.370> programming<00:15:03.910> language 00:15:04.170 --> 00:15:04.180 align:start position:0% tiny little bit of programming language 00:15:04.180 --> 00:15:06.060 align:start position:0% tiny little bit of programming language semantics<00:15:04.660> on<00:15:04.810> this<00:15:04.960> side<00:15:05.140> to<00:15:05.620> keep<00:15:05.770> the<00:15:05.830> talk 00:15:06.060 --> 00:15:06.070 align:start position:0% semantics on this side to keep the talk 00:15:06.070 --> 00:15:07.650 align:start position:0% semantics on this side to keep the talk from<00:15:06.250> being<00:15:06.430> totally<00:15:07.240> boring 00:15:07.650 --> 00:15:07.660 align:start position:0% from being totally boring 00:15:07.660 --> 00:15:11.040 align:start position:0% from being totally boring all<00:15:08.500> right<00:15:08.680> so<00:15:09.270> so<00:15:10.270> here's<00:15:10.630> here's<00:15:10.930> the 00:15:11.040 --> 00:15:11.050 align:start position:0% all right so so here's here's the 00:15:11.050 --> 00:15:13.080 align:start position:0% all right so so here's here's the context<00:15:11.740> with<00:15:11.860> the<00:15:11.950> whole<00:15:12.190> the<00:15:12.670> whole<00:15:12.700> the 00:15:13.080 --> 00:15:13.090 align:start position:0% context with the whole the whole the 00:15:13.090 --> 00:15:14.970 align:start position:0% context with the whole the whole the test<00:15:13.510> harness<00:15:13.930> with<00:15:14.080> a<00:15:14.110> whole<00:15:14.380> knock<00:15:14.620> in<00:15:14.830> it 00:15:14.970 --> 00:15:14.980 align:start position:0% test harness with a whole knock in it 00:15:14.980 --> 00:15:17.190 align:start position:0% test harness with a whole knock in it and<00:15:15.160> now<00:15:15.670> when<00:15:15.820> I<00:15:15.850> apply<00:15:15.970> my<00:15:16.480> test<00:15:16.780> harness 00:15:17.190 --> 00:15:17.200 align:start position:0% and now when I apply my test harness 00:15:17.200 --> 00:15:18.930 align:start position:0% and now when I apply my test harness though<00:15:17.710> these<00:15:17.920> should<00:15:18.130> have<00:15:18.190> been<00:15:18.250> commas<00:15:18.790> I 00:15:18.930 --> 00:15:18.940 align:start position:0% though these should have been commas I 00:15:18.940 --> 00:15:19.980 align:start position:0% though these should have been commas I don't<00:15:19.090> know<00:15:19.180> what<00:15:19.300> happened<00:15:19.630> there<00:15:19.720> sorry 00:15:19.980 --> 00:15:19.990 align:start position:0% don't know what happened there sorry 00:15:19.990 --> 00:15:23.040 align:start position:0% don't know what happened there sorry about<00:15:20.050> that<00:15:20.940> when<00:15:21.940> I<00:15:21.970> apply<00:15:22.270> my<00:15:22.450> test<00:15:22.720> harness 00:15:23.040 --> 00:15:23.050 align:start position:0% about that when I apply my test harness 00:15:23.050 --> 00:15:25.050 align:start position:0% about that when I apply my test harness again<00:15:23.200> to<00:15:23.530> see<00:15:23.800> we<00:15:24.640> should<00:15:24.760> get<00:15:24.940> the 00:15:25.050 --> 00:15:25.060 align:start position:0% again to see we should get the 00:15:25.060 --> 00:15:28.670 align:start position:0% again to see we should get the deterministic<00:15:25.570> six<00:15:26.130> when<00:15:27.130> I<00:15:27.160> apply<00:15:27.550> my 00:15:28.670 --> 00:15:28.680 align:start position:0% deterministic six when I apply my 00:15:28.680 --> 00:15:33.180 align:start position:0% deterministic six when I apply my context<00:15:29.680> to<00:15:29.830> C<00:15:30.040> Prime<00:15:30.490> now<00:15:31.450> we<00:15:32.110> either<00:15:32.350> get<00:15:32.710> six 00:15:33.180 --> 00:15:33.190 align:start position:0% context to C Prime now we either get six 00:15:33.190 --> 00:15:37.320 align:start position:0% context to C Prime now we either get six or<00:15:33.400> five<00:15:33.810> non-deterministically<00:15:35.880> so<00:15:36.880> all 00:15:37.320 --> 00:15:37.330 align:start position:0% or five non-deterministically so all 00:15:37.330 --> 00:15:39.720 align:start position:0% or five non-deterministically so all I've<00:15:37.570> done<00:15:37.750> is<00:15:37.810> just<00:15:38.140> restate<00:15:38.980> everything<00:15:39.610> I 00:15:39.720 --> 00:15:39.730 align:start position:0% I've done is just restate everything I 00:15:39.730 --> 00:15:45.660 align:start position:0% I've done is just restate everything I said<00:15:40.000> before<00:15:40.240> in<00:15:41.730> symbols<00:15:43.020> by<00:15:44.020> the<00:15:44.080> way<00:15:44.670> what 00:15:45.660 --> 00:15:45.670 align:start position:0% said before in symbols by the way what 00:15:45.670 --> 00:15:48.990 align:start position:0% said before in symbols by the way what should<00:15:45.970> be<00:15:46.150> happening<00:15:46.360> is<00:15:46.900> in<00:15:47.740> your<00:15:48.550> mind<00:15:48.790> you 00:15:48.990 --> 00:15:49.000 align:start position:0% should be happening is in your mind you 00:15:49.000 --> 00:15:51.090 align:start position:0% should be happening is in your mind you start<00:15:49.240> thinking<00:15:49.600> huh<00:15:50.020> this<00:15:50.470> notion<00:15:50.770> of 00:15:51.090 --> 00:15:51.100 align:start position:0% start thinking huh this notion of 00:15:51.100 --> 00:15:53.490 align:start position:0% start thinking huh this notion of contextual<00:15:51.820> equivalence<00:15:52.420> should<00:15:53.200> line<00:15:53.470> up 00:15:53.490 --> 00:15:53.500 align:start position:0% contextual equivalence should line up 00:15:53.500 --> 00:15:56.550 align:start position:0% contextual equivalence should line up with<00:15:53.740> things<00:15:54.310> like<00:15:54.610> do<00:15:55.240> my<00:15:55.420> types<00:15:55.780> and<00:15:56.170> sure 00:15:56.550 --> 00:15:56.560 align:start position:0% with things like do my types and sure 00:15:56.560 --> 00:15:59.040 align:start position:0% with things like do my types and sure that<00:15:57.340> my<00:15:57.460> programs<00:15:57.910> behave<00:15:58.360> in<00:15:58.510> a<00:15:58.570> nice<00:15:58.750> way<00:15:59.020> so 00:15:59.040 --> 00:15:59.050 align:start position:0% that my programs behave in a nice way so 00:15:59.050 --> 00:16:01.110 align:start position:0% that my programs behave in a nice way so this<00:15:59.350> should<00:15:59.500> be<00:15:59.560> this<00:15:59.710> nice<00:16:00.120> correspondence 00:16:01.110 --> 00:16:01.120 align:start position:0% this should be this nice correspondence 00:16:01.120 --> 00:16:03.810 align:start position:0% this should be this nice correspondence between<00:16:01.330> how<00:16:02.050> might<00:16:02.350> the<00:16:02.710> types<00:16:03.070> constrain 00:16:03.810 --> 00:16:03.820 align:start position:0% between how might the types constrain 00:16:03.820 --> 00:16:06.540 align:start position:0% between how might the types constrain the<00:16:04.030> behavior<00:16:04.480> of<00:16:04.690> my<00:16:04.870> contracts<00:16:05.560> and<00:16:05.860> how<00:16:06.490> the 00:16:06.540 --> 00:16:06.550 align:start position:0% the behavior of my contracts and how the 00:16:06.550 --> 00:16:07.980 align:start position:0% the behavior of my contracts and how the contextual<00:16:07.300> equivalence<00:16:07.840> or 00:16:07.980 --> 00:16:07.990 align:start position:0% contextual equivalence or 00:16:07.990 --> 00:16:10.830 align:start position:0% contextual equivalence or substitutability<00:16:09.270> constrains<00:16:10.270> the<00:16:10.480> behavior 00:16:10.830 --> 00:16:10.840 align:start position:0% substitutability constrains the behavior 00:16:10.840 --> 00:16:12.720 align:start position:0% substitutability constrains the behavior of<00:16:10.960> my<00:16:11.080> contracts<00:16:11.950> they<00:16:12.160> should<00:16:12.340> they<00:16:12.700> should 00:16:12.720 --> 00:16:12.730 align:start position:0% of my contracts they should they should 00:16:12.730 --> 00:16:16.500 align:start position:0% of my contracts they should they should fit<00:16:13.360> perfectly<00:16:14.040> why<00:16:15.040> so<00:16:15.790> that<00:16:15.820> if<00:16:16.120> I<00:16:16.240> were<00:16:16.360> to 00:16:16.500 --> 00:16:16.510 align:start position:0% fit perfectly why so that if I were to 00:16:16.510 --> 00:16:18.720 align:start position:0% fit perfectly why so that if I were to do<00:16:16.660> type<00:16:17.050> checking<00:16:17.080> I<00:16:17.770> don't<00:16:18.160> know<00:16:18.250> maybe<00:16:18.550> it 00:16:18.720 --> 00:16:18.730 align:start position:0% do type checking I don't know maybe it 00:16:18.730 --> 00:16:20.880 align:start position:0% do type checking I don't know maybe it would<00:16:18.850> be<00:16:18.880> the<00:16:19.090> same<00:16:19.330> as<00:16:19.540> if<00:16:19.690> as<00:16:19.890> formally 00:16:20.880 --> 00:16:20.890 align:start position:0% would be the same as if as formally 00:16:20.890 --> 00:16:22.130 align:start position:0% would be the same as if as formally proving<00:16:21.280> my 00:16:22.130 --> 00:16:22.140 align:start position:0% proving my 00:16:22.140 --> 00:16:27.190 align:start position:0% proving my correct<00:16:24.530> why<00:16:25.530> would<00:16:25.680> we<00:16:25.800> want<00:16:25.950> to<00:16:26.010> do<00:16:26.100> that 00:16:27.190 --> 00:16:27.200 align:start position:0% correct why would we want to do that 00:16:27.200 --> 00:16:33.020 align:start position:0% correct why would we want to do that okay<00:16:28.200> so<00:16:29.870> first<00:16:30.920> I<00:16:31.920> want<00:16:32.580> to<00:16:32.700> talk<00:16:32.850> a<00:16:32.880> little 00:16:33.020 --> 00:16:33.030 align:start position:0% okay so first I want to talk a little 00:16:33.030 --> 00:16:35.840 align:start position:0% okay so first I want to talk a little bit<00:16:33.270> about<00:16:33.510> what<00:16:33.750> Casper<00:16:34.260> is<00:16:34.380> doing<00:16:34.710> and<00:16:35.640> or 00:16:35.840 --> 00:16:35.850 align:start position:0% bit about what Casper is doing and or 00:16:35.850 --> 00:16:38.300 align:start position:0% bit about what Casper is doing and or what<00:16:36.120> any<00:16:36.570> consensus<00:16:37.260> algorithm<00:16:37.560> is<00:16:37.860> doing<00:16:38.190> in 00:16:38.300 --> 00:16:38.310 align:start position:0% what any consensus algorithm is doing in 00:16:38.310 --> 00:16:40.910 align:start position:0% what any consensus algorithm is doing in this<00:16:38.820> setting<00:16:39.360> what<00:16:40.260> the<00:16:40.410> consensus 00:16:40.910 --> 00:16:40.920 align:start position:0% this setting what the consensus 00:16:40.920 --> 00:16:42.620 align:start position:0% this setting what the consensus algorithm<00:16:41.370> is<00:16:41.490> doing<00:16:41.760> in<00:16:41.880> this<00:16:41.970> setting<00:16:42.450> is 00:16:42.620 --> 00:16:42.630 align:start position:0% algorithm is doing in this setting is 00:16:42.630 --> 00:16:46.550 align:start position:0% algorithm is doing in this setting is it's<00:16:42.870> guaranteeing<00:16:43.800> that<00:16:44.660> all<00:16:45.660> the<00:16:46.080> instances 00:16:46.550 --> 00:16:46.560 align:start position:0% it's guaranteeing that all the instances 00:16:46.560 --> 00:16:51.350 align:start position:0% it's guaranteeing that all the instances agree<00:16:47.310> on<00:16:47.610> the<00:16:48.060> winners<00:16:48.390> of<00:16:48.420> the<00:16:48.660> races<00:16:50.210> so<00:16:51.210> the 00:16:51.350 --> 00:16:51.360 align:start position:0% agree on the winners of the races so the 00:16:51.360 --> 00:16:55.420 align:start position:0% agree on the winners of the races so the i/o<00:16:51.540> events<00:16:52.260> are<00:16:52.530> the<00:16:52.860> only<00:16:53.070> transactions 00:16:55.420 --> 00:16:55.430 align:start position:0% i/o events are the only transactions 00:16:55.430 --> 00:16:57.830 align:start position:0% i/o events are the only transactions addresses<00:16:56.430> as<00:16:56.670> you<00:16:57.090> know<00:16:57.270> and<00:16:57.480> love<00:16:57.630> them 00:16:57.830 --> 00:16:57.840 align:start position:0% addresses as you know and love them 00:16:57.840 --> 00:17:02.620 align:start position:0% addresses as you know and love them become<00:16:58.230> channels<00:16:59.390> this<00:17:00.390> making<00:17:00.840> sense<00:17:01.110> right 00:17:02.620 --> 00:17:02.630 align:start position:0% become channels this making sense right 00:17:02.630 --> 00:17:06.439 align:start position:0% become channels this making sense right okay<00:17:03.630> and<00:17:03.900> then<00:17:04.380> and<00:17:04.709> then<00:17:05.220> our<00:17:05.699> consensus 00:17:06.439 --> 00:17:06.449 align:start position:0% okay and then and then our consensus 00:17:06.449 --> 00:17:09.170 align:start position:0% okay and then and then our consensus algorithm<00:17:06.930> needs<00:17:07.829> to<00:17:08.190> just<00:17:08.640> worry<00:17:09.030> about 00:17:09.170 --> 00:17:09.180 align:start position:0% algorithm needs to just worry about 00:17:09.180 --> 00:17:12.620 align:start position:0% algorithm needs to just worry about those<00:17:09.990> kinds<00:17:10.709> of<00:17:10.800> transactions<00:17:11.520> and<00:17:11.820> it<00:17:12.240> only 00:17:12.620 --> 00:17:12.630 align:start position:0% those kinds of transactions and it only 00:17:12.630 --> 00:17:15.520 align:start position:0% those kinds of transactions and it only or<00:17:12.780> if<00:17:12.900> you<00:17:13.079> remember<00:17:13.620> back<00:17:13.770> to<00:17:13.829> our<00:17:14.100> art<00:17:14.760> angle 00:17:15.520 --> 00:17:15.530 align:start position:0% or if you remember back to our art angle 00:17:15.530 --> 00:17:18.470 align:start position:0% or if you remember back to our art angle description<00:17:16.530> it<00:17:17.100> only<00:17:17.339> has<00:17:17.699> to<00:17:17.880> order<00:17:18.270> those 00:17:18.470 --> 00:17:18.480 align:start position:0% description it only has to order those 00:17:18.480 --> 00:17:20.480 align:start position:0% description it only has to order those transactions<00:17:19.440> where<00:17:19.980> you<00:17:20.130> have<00:17:20.339> these 00:17:20.480 --> 00:17:20.490 align:start position:0% transactions where you have these 00:17:20.490 --> 00:17:24.040 align:start position:0% transactions where you have these tangles<00:17:21.000> and<00:17:21.540> you<00:17:22.199> can<00:17:22.380> clearly<00:17:22.709> see<00:17:22.890> those 00:17:24.040 --> 00:17:24.050 align:start position:0% tangles and you can clearly see those 00:17:24.050 --> 00:17:26.660 align:start position:0% tangles and you can clearly see those right<00:17:25.050> you<00:17:25.829> can<00:17:26.010> you<00:17:26.190> can<00:17:26.339> actually 00:17:26.660 --> 00:17:26.670 align:start position:0% right you can you can actually 00:17:26.670 --> 00:17:29.570 align:start position:0% right you can you can actually automatically<00:17:27.540> observe<00:17:28.500> those<00:17:28.800> tangles<00:17:29.400> and 00:17:29.570 --> 00:17:29.580 align:start position:0% automatically observe those tangles and 00:17:29.580 --> 00:17:31.910 align:start position:0% automatically observe those tangles and see<00:17:29.790> where<00:17:29.940> you<00:17:30.060> have<00:17:30.090> isolation<00:17:30.930> and<00:17:31.230> then 00:17:31.910 --> 00:17:31.920 align:start position:0% see where you have isolation and then 00:17:31.920 --> 00:17:33.740 align:start position:0% see where you have isolation and then and<00:17:32.340> then<00:17:32.490> your<00:17:32.610> consensus<00:17:33.120> algorithm<00:17:33.360> only 00:17:33.740 --> 00:17:33.750 align:start position:0% and then your consensus algorithm only 00:17:33.750 --> 00:17:36.350 align:start position:0% and then your consensus algorithm only has<00:17:34.050> to<00:17:34.230> worry<00:17:34.440> about<00:17:34.640> schedules<00:17:35.640> or<00:17:35.850> orders 00:17:36.350 --> 00:17:36.360 align:start position:0% has to worry about schedules or orders 00:17:36.360 --> 00:17:39.230 align:start position:0% has to worry about schedules or orders that<00:17:37.080> make<00:17:37.290> sure<00:17:37.620> that<00:17:38.160> things<00:17:38.610> are<00:17:38.820> ordered 00:17:39.230 --> 00:17:39.240 align:start position:0% that make sure that things are ordered 00:17:39.240 --> 00:17:42.440 align:start position:0% that make sure that things are ordered in<00:17:39.450> the<00:17:39.780> tangles<00:17:40.290> and<00:17:40.560> and<00:17:41.160> relative<00:17:41.820> to<00:17:42.150> a<00:17:42.180> /<00:17:42.420> - 00:17:42.440 --> 00:17:42.450 align:start position:0% in the tangles and and relative to a / - 00:17:42.450 --> 00:17:45.620 align:start position:0% in the tangles and and relative to a / - two<00:17:42.990> different<00:17:43.260> disjoint<00:17:43.980> tangles<00:17:44.580> they<00:17:45.390> can 00:17:45.620 --> 00:17:45.630 align:start position:0% two different disjoint tangles they can 00:17:45.630 --> 00:17:56.030 align:start position:0% two different disjoint tangles they can be<00:17:45.810> in<00:17:46.020> any<00:17:46.170> order<00:17:46.790> yes<00:17:53.720> yes<00:17:54.720> the<00:17:55.320> short<00:17:55.680> answer 00:17:56.030 --> 00:17:56.040 align:start position:0% be in any order yes yes the short answer 00:17:56.040 --> 00:17:59.780 align:start position:0% be in any order yes yes the short answer is<00:17:56.070> yes<00:17:56.720> okay<00:17:57.720> so<00:17:57.930> so<00:17:58.560> effectively<00:17:59.280> what<00:17:59.670> we 00:17:59.780 --> 00:17:59.790 align:start position:0% is yes okay so so effectively what we 00:17:59.790 --> 00:18:01.550 align:start position:0% is yes okay so so effectively what we what<00:18:00.090> we've<00:18:00.240> just<00:18:00.270> done<00:18:00.780> is<00:18:01.110> we've<00:18:01.350> now 00:18:01.550 --> 00:18:01.560 align:start position:0% what we've just done is we've now 00:18:01.560 --> 00:18:04.700 align:start position:0% what we've just done is we've now related<00:18:02.310> our<00:18:02.430> computational<00:18:03.300> model<00:18:03.750> to 00:18:04.700 --> 00:18:04.710 align:start position:0% related our computational model to 00:18:04.710 --> 00:18:08.030 align:start position:0% related our computational model to scaling<00:18:05.610> and<00:18:06.090> it's<00:18:07.050> not<00:18:07.200> just<00:18:07.320> sharding<00:18:07.890> it's 00:18:08.030 --> 00:18:08.040 align:start position:0% scaling and it's not just sharding it's 00:18:08.040 --> 00:18:09.800 align:start position:0% scaling and it's not just sharding it's actually<00:18:08.310> compositional<00:18:09.030> one<00:18:09.510> thing<00:18:09.720> I 00:18:09.800 --> 00:18:09.810 align:start position:0% actually compositional one thing I 00:18:09.810 --> 00:18:11.480 align:start position:0% actually compositional one thing I didn't<00:18:10.140> agree<00:18:10.350> with<00:18:10.440> when<00:18:10.830> in<00:18:10.980> Martin's<00:18:11.310> talk 00:18:11.480 --> 00:18:11.490 align:start position:0% didn't agree with when in Martin's talk 00:18:11.490 --> 00:18:13.190 align:start position:0% didn't agree with when in Martin's talk and<00:18:11.700> I<00:18:11.730> love<00:18:11.910> this<00:18:12.060> kind<00:18:12.240> of<00:18:12.360> debate<00:18:12.750> and 00:18:13.190 --> 00:18:13.200 align:start position:0% and I love this kind of debate and 00:18:13.200 --> 00:18:15.410 align:start position:0% and I love this kind of debate and disagreement<00:18:13.860> is<00:18:14.100> Martin<00:18:14.850> suggested<00:18:15.030> he'd 00:18:15.410 --> 00:18:15.420 align:start position:0% disagreement is Martin suggested he'd 00:18:15.420 --> 00:18:18.580 align:start position:0% disagreement is Martin suggested he'd never<00:18:15.720> never<00:18:16.140> know<00:18:16.470> why<00:18:16.980> or<00:18:17.040> when<00:18:17.520> you<00:18:17.730> might 00:18:18.580 --> 00:18:18.590 align:start position:0% never never know why or when you might 00:18:18.590 --> 00:18:22.940 align:start position:0% never never know why or when you might break<00:18:20.120> into<00:18:21.120> more<00:18:21.300> than<00:18:21.480> one<00:18:21.630> level<00:18:21.900> well<00:18:22.800> all 00:18:22.940 --> 00:18:22.950 align:start position:0% break into more than one level well all 00:18:22.950 --> 00:18:24.530 align:start position:0% break into more than one level well all you<00:18:23.100> have<00:18:23.280> to<00:18:23.430> do<00:18:23.550> is<00:18:23.730> look<00:18:23.880> at<00:18:24.060> you<00:18:24.210> our<00:18:24.360> eyes 00:18:24.530 --> 00:18:24.540 align:start position:0% you have to do is look at you our eyes 00:18:24.540 --> 00:18:29.330 align:start position:0% you have to do is look at you our eyes or<00:18:25.550> DNS<00:18:27.170> to<00:18:28.170> begin<00:18:28.440> to<00:18:28.560> see<00:18:28.770> why<00:18:28.980> you<00:18:29.040> would 00:18:29.330 --> 00:18:29.340 align:start position:0% or DNS to begin to see why you would 00:18:29.340 --> 00:18:31.100 align:start position:0% or DNS to begin to see why you would ever<00:18:29.580> have<00:18:29.910> more<00:18:30.150> than<00:18:30.330> what<00:18:30.510> more<00:18:30.780> than<00:18:30.930> two 00:18:31.100 --> 00:18:31.110 align:start position:0% ever have more than what more than two 00:18:31.110 --> 00:18:33.620 align:start position:0% ever have more than what more than two levels<00:18:31.310> right<00:18:32.310> there's<00:18:32.520> lots<00:18:32.940> and<00:18:33.180> lots<00:18:33.270> and 00:18:33.620 --> 00:18:33.630 align:start position:0% levels right there's lots and lots and 00:18:33.630 --> 00:18:35.660 align:start position:0% levels right there's lots and lots and lots<00:18:33.780> of<00:18:33.900> examples<00:18:34.380> on<00:18:34.530> the<00:18:34.620> internet<00:18:35.040> for 00:18:35.660 --> 00:18:35.670 align:start position:0% lots of examples on the internet for 00:18:35.670 --> 00:18:37.970 align:start position:0% lots of examples on the internet for why<00:18:35.760> multiple<00:18:36.570> layers<00:18:36.780> of<00:18:37.020> nesting<00:18:37.470> is<00:18:37.590> a<00:18:37.620> good 00:18:37.970 --> 00:18:37.980 align:start position:0% why multiple layers of nesting is a good 00:18:37.980 --> 00:18:40.820 align:start position:0% why multiple layers of nesting is a good idea<00:18:38.190> and<00:18:38.880> if<00:18:39.210> we<00:18:39.390> grow<00:18:39.690> and<00:18:39.960> grow<00:18:40.110> and<00:18:40.350> grow<00:18:40.440> I 00:18:40.820 --> 00:18:40.830 align:start position:0% idea and if we grow and grow and grow I 00:18:40.830 --> 00:18:42.770 align:start position:0% idea and if we grow and grow and grow I don't<00:18:41.010> know<00:18:41.190> maybe<00:18:41.400> we<00:18:41.580> have<00:18:41.730> a<00:18:41.760> Mars<00:18:42.090> colony<00:18:42.750> a 00:18:42.770 --> 00:18:42.780 align:start position:0% don't know maybe we have a Mars colony a 00:18:42.780 --> 00:18:44.720 align:start position:0% don't know maybe we have a Mars colony a colony<00:18:43.440> on<00:18:43.470> Alpha<00:18:43.680> Centauri<00:18:44.040> maybe<00:18:44.550> that 00:18:44.720 --> 00:18:44.730 align:start position:0% colony on Alpha Centauri maybe that 00:18:44.730 --> 00:18:46.550 align:start position:0% colony on Alpha Centauri maybe that namespaces<00:18:45.390> get<00:18:45.570> even<00:18:45.780> bigger<00:18:45.930> asked<00:18:46.470> me 00:18:46.550 --> 00:18:46.560 align:start position:0% namespaces get even bigger asked me 00:18:46.560 --> 00:18:49.360 align:start position:0% namespaces get even bigger asked me about<00:18:46.650> main<00:18:46.950> spaces<00:18:47.220> at<00:18:47.490> the<00:18:47.520> end<00:18:47.610> okay 00:18:49.360 --> 00:18:49.370 align:start position:0% about main spaces at the end okay 00:18:49.370 --> 00:18:54.050 align:start position:0% about main spaces at the end okay so<00:18:50.370> in<00:18:50.580> so<00:18:50.990> let<00:18:51.990> me<00:18:52.080> just<00:18:52.260> quickly<00:18:52.800> hang<00:18:53.790> on<00:18:53.910> one 00:18:54.050 --> 00:18:54.060 align:start position:0% so in so let me just quickly hang on one 00:18:54.060 --> 00:18:55.310 align:start position:0% so in so let me just quickly hang on one second<00:18:54.450> cuz<00:18:54.570> I've<00:18:54.690> got<00:18:54.810> a<00:18:54.840> leave<00:18:55.080> enough<00:18:55.290> time 00:18:55.310 --> 00:18:55.320 align:start position:0% second cuz I've got a leave enough time 00:18:55.320 --> 00:18:58.460 align:start position:0% second cuz I've got a leave enough time for<00:18:55.860> the<00:18:55.950> demo<00:18:56.310> oh<00:18:56.520> yeah<00:18:56.850> yeah<00:18:57.300> so<00:18:57.870> we<00:18:58.440> started 00:18:58.460 --> 00:18:58.470 align:start position:0% for the demo oh yeah yeah so we started 00:18:58.470 --> 00:19:01.190 align:start position:0% for the demo oh yeah yeah so we started a<00:18:58.920> little<00:18:59.070> bit<00:18:59.250> late<00:18:59.490> but<00:19:00.240> I'm<00:19:00.480> gonna<00:19:00.840> have<00:19:01.050> to 00:19:01.190 --> 00:19:01.200 align:start position:0% a little bit late but I'm gonna have to 00:19:01.200 --> 00:19:02.750 align:start position:0% a little bit late but I'm gonna have to I'm<00:19:01.410> gonna<00:19:01.620> have<00:19:01.710> to<00:19:01.890> hold<00:19:02.100> some<00:19:02.310> questions 00:19:02.750 --> 00:19:02.760 align:start position:0% I'm gonna have to hold some questions 00:19:02.760 --> 00:19:04.250 align:start position:0% I'm gonna have to hold some questions because<00:19:02.970> I<00:19:03.060> want<00:19:03.240> to<00:19:03.300> I<00:19:03.330> want<00:19:03.420> Ken<00:19:03.810> to<00:19:03.990> give<00:19:04.140> it 00:19:04.250 --> 00:19:04.260 align:start position:0% because I want to I want Ken to give it 00:19:04.260 --> 00:19:06.830 align:start position:0% because I want to I want Ken to give it to<00:19:04.860> give<00:19:05.100> some<00:19:05.760> time<00:19:06.000> to<00:19:06.180> talk<00:19:06.420> so<00:19:06.630> I'm<00:19:06.720> going 00:19:06.830 --> 00:19:06.840 align:start position:0% to give some time to talk so I'm going 00:19:06.840 --> 00:19:08.720 align:start position:0% to give some time to talk so I'm going to<00:19:06.900> quickly<00:19:07.110> just<00:19:07.440> reiterate<00:19:08.430> what<00:19:08.580> I<00:19:08.610> said 00:19:08.720 --> 00:19:08.730 align:start position:0% to quickly just reiterate what I said 00:19:08.730 --> 00:19:10.910 align:start position:0% to quickly just reiterate what I said and<00:19:09.240> then<00:19:09.600> move<00:19:09.840> into<00:19:10.110> the<00:19:10.290> next<00:19:10.440> part<00:19:10.590> of<00:19:10.800> the 00:19:10.910 --> 00:19:10.920 align:start position:0% and then move into the next part of the 00:19:10.920 --> 00:19:13.370 align:start position:0% and then move into the next part of the talk<00:19:11.130> which<00:19:11.310> is<00:19:11.340> it<00:19:11.550> which<00:19:12.090> is<00:19:12.270> a<00:19:12.300> er<00:19:12.810> a<00:19:12.990> more 00:19:13.370 --> 00:19:13.380 align:start position:0% talk which is it which is a er a more 00:19:13.380 --> 00:19:18.910 align:start position:0% talk which is it which is a er a more realistic<00:19:13.770> contract<00:19:14.490> and<00:19:14.760> a<00:19:15.240> demo<00:19:15.600> okay<00:19:16.230> so 00:19:18.910 --> 00:19:18.920 align:start position:0% realistic contract and a demo okay so 00:19:18.920 --> 00:19:21.980 align:start position:0% realistic contract and a demo okay so yeah<00:19:19.920> the<00:19:20.460> the<00:19:20.490> important<00:19:21.180> point<00:19:21.450> is<00:19:21.720> that 00:19:21.980 --> 00:19:21.990 align:start position:0% yeah the the important point is that 00:19:21.990 --> 00:19:25.670 align:start position:0% yeah the the important point is that consensus<00:19:22.920> ensures<00:19:23.370> that<00:19:23.520> every<00:19:24.030> VM<00:19:24.680> agrees 00:19:25.670 --> 00:19:25.680 align:start position:0% consensus ensures that every VM agrees 00:19:25.680 --> 00:19:27.550 align:start position:0% consensus ensures that every VM agrees on<00:19:25.920> the<00:19:26.040> winner<00:19:26.250> of<00:19:26.340> the<00:19:26.550> race 00:19:27.550 --> 00:19:27.560 align:start position:0% on the winner of the race 00:19:27.560 --> 00:19:30.650 align:start position:0% on the winner of the race that's<00:19:28.560> the<00:19:28.770> computational<00:19:29.520> model<00:19:29.850> here<00:19:30.060> all 00:19:30.650 --> 00:19:30.660 align:start position:0% that's the computational model here all 00:19:30.660 --> 00:19:35.720 align:start position:0% that's the computational model here all right<00:19:30.870> so<00:19:31.500> now<00:19:33.860> let's<00:19:34.860> have<00:19:35.040> Euclid<00:19:35.520> take<00:19:35.700> a 00:19:35.720 --> 00:19:35.730 align:start position:0% right so now let's have Euclid take a 00:19:35.730 --> 00:19:38.480 align:start position:0% right so now let's have Euclid take a look<00:19:35.970> at<00:19:36.120> ER<00:19:36.240> C<00:19:36.510> 20<00:19:36.900> and<00:19:37.080> see<00:19:37.680> how<00:19:37.860> that<00:19:38.070> works 00:19:38.480 --> 00:19:38.490 align:start position:0% look at ER C 20 and see how that works 00:19:38.490 --> 00:19:43.790 align:start position:0% look at ER C 20 and see how that works so<00:19:39.180> I'm<00:19:39.270> gonna<00:19:39.620> see<00:19:40.880> if<00:19:41.880> we<00:19:42.300> can<00:19:42.480> get<00:19:42.660> Kent<00:19:43.470> on 00:19:43.790 --> 00:19:43.800 align:start position:0% so I'm gonna see if we can get Kent on 00:19:43.800 --> 00:19:50.030 align:start position:0% so I'm gonna see if we can get Kent on the<00:19:43.980> screen<00:19:44.340> here<00:19:45.260> can<00:19:46.260> tu<00:19:46.410> they're<00:19:47.390> awesome 00:19:50.030 --> 00:19:50.040 align:start position:0% the screen here can tu they're awesome 00:19:50.040 --> 00:19:52.370 align:start position:0% the screen here can tu they're awesome so<00:19:50.430> I<00:19:50.640> don't<00:19:51.030> know<00:19:51.270> if<00:19:51.540> the<00:19:51.690> audio<00:19:52.020> is<00:19:52.200> coming 00:19:52.370 --> 00:19:52.380 align:start position:0% so I don't know if the audio is coming 00:19:52.380 --> 00:19:54.200 align:start position:0% so I don't know if the audio is coming through<00:19:52.560> but<00:19:52.890> if<00:19:53.070> not<00:19:53.310> I'll<00:19:53.610> just<00:19:53.820> hold<00:19:54.090> the 00:19:54.200 --> 00:19:54.210 align:start position:0% through but if not I'll just hold the 00:19:54.210 --> 00:19:57.650 align:start position:0% through but if not I'll just hold the mic<00:19:54.450> up<00:19:54.630> to<00:19:55.470> the<00:19:55.620> device<00:19:56.010> it's<00:19:56.280> so-so 00:19:57.650 --> 00:19:57.660 align:start position:0% mic up to the device it's so-so 00:19:57.660 --> 00:19:59.900 align:start position:0% mic up to the device it's so-so so<00:19:58.350> Kent<00:19:58.620> and<00:19:58.800> I<00:19:58.830> were<00:19:58.950> talking<00:19:59.310> last<00:19:59.340> night<00:19:59.640> we 00:19:59.900 --> 00:19:59.910 align:start position:0% so Kent and I were talking last night we 00:19:59.910 --> 00:20:01.220 align:start position:0% so Kent and I were talking last night we didn't<00:20:00.180> hang<00:20:00.450> on<00:20:00.540> one<00:20:00.630> second<00:20:00.870> I<00:20:00.900> just<00:20:01.050> want<00:20:01.170> to 00:20:01.220 --> 00:20:01.230 align:start position:0% didn't hang on one second I just want to 00:20:01.230 --> 00:20:04.490 align:start position:0% didn't hang on one second I just want to introduce<00:20:01.410> you<00:20:02.930> we<00:20:03.930> there<00:20:04.380> was<00:20:04.440> a 00:20:04.490 --> 00:20:04.500 align:start position:0% introduce you we there was a 00:20:04.500 --> 00:20:06.620 align:start position:0% introduce you we there was a miscommunication<00:20:04.830> on<00:20:05.370> when<00:20:05.490> the<00:20:05.610> talk<00:20:05.790> was<00:20:06.030> so 00:20:06.620 --> 00:20:06.630 align:start position:0% miscommunication on when the talk was so 00:20:06.630 --> 00:20:08.810 align:start position:0% miscommunication on when the talk was so that's<00:20:07.230> why<00:20:07.410> we<00:20:07.590> he<00:20:08.070> was<00:20:08.190> supposed<00:20:08.460> to<00:20:08.520> be<00:20:08.640> here 00:20:08.810 --> 00:20:08.820 align:start position:0% that's why we he was supposed to be here 00:20:08.820 --> 00:20:10.820 align:start position:0% that's why we he was supposed to be here physically<00:20:09.150> present<00:20:09.420> he's<00:20:10.200> not<00:20:10.440> flying<00:20:10.650> in 00:20:10.820 --> 00:20:10.830 align:start position:0% physically present he's not flying in 00:20:10.830 --> 00:20:14.180 align:start position:0% physically present he's not flying in until<00:20:11.160> tomorrow<00:20:11.280> so<00:20:12.120> we're<00:20:12.420> gonna<00:20:12.540> give<00:20:13.230> give 00:20:14.180 --> 00:20:14.190 align:start position:0% until tomorrow so we're gonna give give 00:20:14.190 --> 00:20:16.670 align:start position:0% until tomorrow so we're gonna give give him<00:20:14.400> a<00:20:14.490> chance<00:20:14.700> to<00:20:14.820> go<00:20:15.030> through<00:20:15.060> zoom<00:20:15.600> so<00:20:16.290> let's 00:20:16.670 --> 00:20:16.680 align:start position:0% him a chance to go through zoom so let's 00:20:16.680 --> 00:20:36.260 align:start position:0% him a chance to go through zoom so let's see<00:20:16.830> if<00:20:16.950> this<00:20:17.070> works<00:20:17.930> now<00:20:18.930> go 00:20:36.260 --> 00:20:36.270 align:start position:0% 00:20:36.270 --> 00:20:47.760 align:start position:0% okay<00:20:37.270> girlfriend<00:20:42.480> okay<00:20:44.190> so<00:20:45.190> just<00:20:46.440> I'll<00:20:47.440> repeat 00:20:47.760 --> 00:20:47.770 align:start position:0% okay girlfriend okay so just I'll repeat 00:20:47.770 --> 00:21:04.920 align:start position:0% okay girlfriend okay so just I'll repeat it<00:20:47.830> people<00:20:48.160> can<00:20:48.309> hear<00:20:49.230> okay 00:21:04.920 --> 00:21:04.930 align:start position:0% 00:21:04.930 --> 00:21:08.690 align:start position:0% and<00:21:05.410> so<00:21:06.370> as<00:21:07.150> you<00:21:07.360> can<00:21:07.420> see<00:21:07.570> here<00:21:08.020> both 00:21:08.690 --> 00:21:08.700 align:start position:0% and so as you can see here both 00:21:08.700 --> 00:21:11.370 align:start position:0% and so as you can see here both contracts<00:21:09.700> have<00:21:09.910> a<00:21:10.240> relatively<00:21:10.960> similar 00:21:11.370 --> 00:21:11.380 align:start position:0% contracts have a relatively similar 00:21:11.380 --> 00:21:17.790 align:start position:0% contracts have a relatively similar structure<00:21:13.050> the<00:21:14.050> top<00:21:15.570> here<00:21:16.570> in<00:21:16.870> solidity<00:21:17.410> is 00:21:17.790 --> 00:21:17.800 align:start position:0% structure the top here in solidity is 00:21:17.800 --> 00:21:22.320 align:start position:0% structure the top here in solidity is roughly<00:21:18.520> equivalent<00:21:18.640> to<00:21:19.290> that<00:21:20.290> in<00:21:20.470> relay<00:21:21.330> the 00:21:22.320 --> 00:21:22.330 align:start position:0% roughly equivalent to that in relay the 00:21:22.330 --> 00:21:24.900 align:start position:0% roughly equivalent to that in relay the variable<00:21:22.870> declarations<00:21:23.530> here<00:21:23.950> roughly 00:21:24.900 --> 00:21:24.910 align:start position:0% variable declarations here roughly 00:21:24.910 --> 00:21:27.240 align:start position:0% variable declarations here roughly correspond<00:21:25.720> to<00:21:25.990> the<00:21:26.290> productions<00:21:26.890> that<00:21:27.130> you 00:21:27.240 --> 00:21:27.250 align:start position:0% correspond to the productions that you 00:21:27.250 --> 00:21:31.740 align:start position:0% correspond to the productions that you see<00:21:27.429> on<00:21:27.520> the<00:21:27.640> right<00:21:27.820> here<00:21:28.120> and<00:21:29.820> both<00:21:30.820> contracts 00:21:31.740 --> 00:21:31.750 align:start position:0% see on the right here and both contracts 00:21:31.750 --> 00:21:33.150 align:start position:0% see on the right here and both contracts have<00:21:31.960> these<00:21:32.140> sort<00:21:32.410> of<00:21:32.500> function<00:21:32.980> like 00:21:33.150 --> 00:21:33.160 align:start position:0% have these sort of function like 00:21:33.160 --> 00:21:36.030 align:start position:0% have these sort of function like structures<00:21:33.850> that<00:21:34.270> describe<00:21:35.260> the<00:21:35.500> actions 00:21:36.030 --> 00:21:36.040 align:start position:0% structures that describe the actions 00:21:36.040 --> 00:21:40.260 align:start position:0% structures that describe the actions they<00:21:36.250> take<00:21:36.730> on<00:21:37.059> the<00:21:37.720> token<00:21:38.350> and<00:21:38.559> so<00:21:39.429> just 00:21:40.260 --> 00:21:40.270 align:start position:0% they take on the token and so just 00:21:40.270 --> 00:21:43.230 align:start position:0% they take on the token and so just focusing<00:21:40.690> on<00:21:40.840> the<00:21:41.050> role<00:21:41.290> and<00:21:41.440> version<00:21:42.240> the 00:21:43.230 --> 00:21:43.240 align:start position:0% focusing on the role and version the 00:21:43.240 --> 00:21:46.020 align:start position:0% focusing on the role and version the main<00:21:43.420> paradigm<00:21:44.350> shift<00:21:44.679> is<00:21:44.890> to<00:21:45.160> understand<00:21:45.880> the 00:21:46.020 --> 00:21:46.030 align:start position:0% main paradigm shift is to understand the 00:21:46.030 --> 00:21:48.390 align:start position:0% main paradigm shift is to understand the use<00:21:46.150> of<00:21:46.300> channels<00:21:46.750> so<00:21:47.020> greg<00:21:47.740> was<00:21:47.860> calling<00:21:48.250> them 00:21:48.390 --> 00:21:48.400 align:start position:0% use of channels so greg was calling them 00:21:48.400 --> 00:21:50.549 align:start position:0% use of channels so greg was calling them ports<00:21:48.880> earlier<00:21:49.300> but<00:21:49.840> they're<00:21:49.990> the<00:21:50.080> same<00:21:50.260> thing 00:21:50.549 --> 00:21:50.559 align:start position:0% ports earlier but they're the same thing 00:21:50.559 --> 00:21:58.260 align:start position:0% ports earlier but they're the same thing and<00:21:51.220> so<00:21:51.429> as<00:21:52.360> an<00:21:52.570> example<00:21:53.230> on<00:21:53.740> here<00:21:54.610> we<00:21:54.850> have<00:21:57.270> the 00:21:58.260 --> 00:21:58.270 align:start position:0% and so as an example on here we have the 00:21:58.270 --> 00:22:00.419 align:start position:0% and so as an example on here we have the channel<00:21:58.720> called<00:21:59.080> balances<00:21:59.830> channel<00:22:00.220> and 00:22:00.419 --> 00:22:00.429 align:start position:0% channel called balances channel and 00:22:00.429 --> 00:22:02.669 align:start position:0% channel called balances channel and we're<00:22:01.059> sending<00:22:01.300> an<00:22:01.660> empty<00:22:01.960> map<00:22:02.170> through<00:22:02.530> it 00:22:02.669 --> 00:22:02.679 align:start position:0% we're sending an empty map through it 00:22:02.679 --> 00:22:05.900 align:start position:0% we're sending an empty map through it and<00:22:03.160> then<00:22:03.760> on<00:22:03.910> my<00:22:04.090> eleven<00:22:04.630> we<00:22:04.780> immediately 00:22:05.900 --> 00:22:05.910 align:start position:0% and then on my eleven we immediately 00:22:05.910 --> 00:22:11.690 align:start position:0% and then on my eleven we immediately bind<00:22:06.910> that<00:22:07.179> mapped<00:22:07.540> balances<00:22:08.440> and<00:22:08.710> we<00:22:09.340> insert 00:22:11.690 --> 00:22:11.700 align:start position:0% bind that mapped balances and we insert 00:22:11.700 --> 00:22:14.610 align:start position:0% bind that mapped balances and we insert the<00:22:12.700> updated<00:22:13.420> balance<00:22:13.450> is<00:22:13.960> such<00:22:14.170> that<00:22:14.380> the 00:22:14.610 --> 00:22:14.620 align:start position:0% the updated balance is such that the 00:22:14.620 --> 00:22:17.240 align:start position:0% the updated balance is such that the message<00:22:14.980> sender<00:22:15.309> now<00:22:16.000> has<00:22:16.210> the<00:22:16.390> total<00:22:16.750> supply 00:22:17.240 --> 00:22:17.250 align:start position:0% message sender now has the total supply 00:22:17.250 --> 00:22:20.810 align:start position:0% message sender now has the total supply this<00:22:18.250> is<00:22:18.429> for<00:22:18.790> when<00:22:19.120> betoken<00:22:19.780> contract<00:22:20.320> is 00:22:20.810 --> 00:22:20.820 align:start position:0% this is for when betoken contract is 00:22:20.820 --> 00:22:24.060 align:start position:0% this is for when betoken contract is initially<00:22:21.820> instantiated<00:22:22.480> and<00:22:23.140> so<00:22:23.710> to<00:22:23.770> keep 00:22:24.060 --> 00:22:24.070 align:start position:0% initially instantiated and so to keep 00:22:24.070 --> 00:22:25.740 align:start position:0% initially instantiated and so to keep things<00:22:24.280> short<00:22:24.400> I'm<00:22:24.850> just<00:22:25.030> gonna<00:22:25.179> run<00:22:25.540> through 00:22:25.740 --> 00:22:25.750 align:start position:0% things short I'm just gonna run through 00:22:25.750 --> 00:22:28.620 align:start position:0% things short I'm just gonna run through the<00:22:26.080> transfer<00:22:26.650> action<00:22:27.100> here<00:22:27.340> and<00:22:28.120> then<00:22:28.270> show<00:22:28.600> a 00:22:28.620 --> 00:22:28.630 align:start position:0% the transfer action here and then show a 00:22:28.630 --> 00:22:32.549 align:start position:0% the transfer action here and then show a demo<00:22:29.020> that<00:22:29.559> uses<00:22:29.980> it<00:22:30.130> so<00:22:31.050> in<00:22:32.050> order<00:22:32.170> to<00:22:32.320> use 00:22:32.549 --> 00:22:32.559 align:start position:0% demo that uses it so in order to use 00:22:32.559 --> 00:22:34.410 align:start position:0% demo that uses it so in order to use this<00:22:32.740> nested<00:22:33.220> transfer<00:22:33.610> contract<00:22:34.090> you<00:22:34.270> need 00:22:34.410 --> 00:22:34.420 align:start position:0% this nested transfer contract you need 00:22:34.420 --> 00:22:37.799 align:start position:0% this nested transfer contract you need to<00:22:34.540> send<00:22:34.929> a<00:22:35.200> message<00:22:35.650> on<00:22:36.179> the<00:22:37.179> transfer 00:22:37.799 --> 00:22:37.809 align:start position:0% to send a message on the transfer 00:22:37.809 --> 00:22:43.130 align:start position:0% to send a message on the transfer channel<00:22:38.140> here 00:22:43.130 --> 00:22:43.140 align:start position:0% 00:22:43.140 --> 00:22:45.420 align:start position:0% yeah<00:22:44.140> I'd<00:22:44.260> receive<00:22:44.530> sending<00:22:44.830> it<00:22:44.920> to<00:22:45.100> the 00:22:45.420 --> 00:22:45.430 align:start position:0% yeah I'd receive sending it to the 00:22:45.430 --> 00:22:48.870 align:start position:0% yeah I'd receive sending it to the amount<00:22:45.790> and<00:22:46.120> then<00:22:46.870> the<00:22:47.080> return<00:22:47.800> channel<00:22:48.070> in 00:22:48.870 --> 00:22:48.880 align:start position:0% amount and then the return channel in 00:22:48.880 --> 00:22:51.750 align:start position:0% amount and then the return channel in which<00:22:49.320> you<00:22:50.320> will<00:22:50.470> listen<00:22:50.800> to<00:22:51.160> see<00:22:51.370> whether<00:22:51.520> the 00:22:51.750 --> 00:22:51.760 align:start position:0% which you will listen to see whether the 00:22:51.760 --> 00:22:54.450 align:start position:0% which you will listen to see whether the transfer<00:22:52.120> succeeded<00:22:52.780> or<00:22:52.930> not<00:22:52.960> and<00:22:53.680> so<00:22:54.250> again 00:22:54.450 --> 00:22:54.460 align:start position:0% transfer succeeded or not and so again 00:22:54.460 --> 00:22:59.250 align:start position:0% transfer succeeded or not and so again we<00:22:54.640> have<00:22:54.850> a<00:22:55.210> for<00:22:55.960> statement<00:22:56.050> here<00:22:57.240> that<00:22:58.260> bind 00:22:59.250 --> 00:22:59.260 align:start position:0% we have a for statement here that bind 00:22:59.260 --> 00:23:07.260 align:start position:0% we have a for statement here that bind the<00:22:59.530> map<00:22:59.950> balances<00:23:01.830> and<00:23:04.800> we<00:23:05.800> create<00:23:06.240> two<00:23:07.240> new 00:23:07.260 --> 00:23:07.270 align:start position:0% the map balances and we create two new 00:23:07.270 --> 00:23:11.720 align:start position:0% the map balances and we create two new channels<00:23:08.640> then<00:23:09.640> this<00:23:09.910> is<00:23:10.120> in<00:23:10.420> order<00:23:10.720> to 00:23:11.720 --> 00:23:11.730 align:start position:0% channels then this is in order to 00:23:11.730 --> 00:23:14.970 align:start position:0% channels then this is in order to essentially<00:23:12.730> get<00:23:13.510> the<00:23:13.780> order<00:23:14.710> for<00:23:14.890> the 00:23:14.970 --> 00:23:14.980 align:start position:0% essentially get the order for the 00:23:14.980 --> 00:23:17.520 align:start position:0% essentially get the order for the balance<00:23:15.310> of<00:23:15.370> the<00:23:15.520> message<00:23:15.850> center<00:23:16.240> and<00:23:16.660> I<00:23:17.200> just 00:23:17.520 --> 00:23:17.530 align:start position:0% balance of the message center and I just 00:23:17.530 --> 00:23:20.550 align:start position:0% balance of the message center and I just sending<00:23:18.340> it<00:23:18.460> to<00:23:18.700> and<00:23:19.570> then<00:23:20.080> in<00:23:20.230> the<00:23:20.380> match 00:23:20.550 --> 00:23:20.560 align:start position:0% sending it to and then in the match 00:23:20.560 --> 00:23:25.290 align:start position:0% sending it to and then in the match today<00:23:20.950> admit<00:23:21.220> dear<00:23:21.660> we<00:23:23.760> some<00:23:24.760> preconditions 00:23:25.290 --> 00:23:25.300 align:start position:0% today admit dear we some preconditions 00:23:25.300 --> 00:23:28.020 align:start position:0% today admit dear we some preconditions and<00:23:25.960> essentially<00:23:26.590> here<00:23:27.520> which<00:23:27.670> I<00:23:27.790> think<00:23:27.820> that 00:23:28.020 --> 00:23:28.030 align:start position:0% and essentially here which I think that 00:23:28.030 --> 00:23:30.720 align:start position:0% and essentially here which I think that balances<00:23:28.750> the<00:23:28.780> sender<00:23:29.290> is<00:23:29.530> greater<00:23:29.800> than<00:23:30.070> the 00:23:30.720 --> 00:23:30.730 align:start position:0% balances the sender is greater than the 00:23:30.730 --> 00:23:32.250 align:start position:0% balances the sender is greater than the amount<00:23:30.850> they<00:23:31.150> said<00:23:31.420> day<00:23:31.570> the<00:23:31.960> amount<00:23:32.170> is 00:23:32.250 --> 00:23:32.260 align:start position:0% amount they said day the amount is 00:23:32.260 --> 00:23:33.260 align:start position:0% amount they said day the amount is greater<00:23:32.380> than<00:23:32.650> zero 00:23:33.260 --> 00:23:33.270 align:start position:0% greater than zero 00:23:33.270 --> 00:23:36.330 align:start position:0% greater than zero finally<00:23:34.270> there's<00:23:34.600> just<00:23:34.780> overflow<00:23:35.350> check<00:23:35.590> this 00:23:36.330 --> 00:23:36.340 align:start position:0% finally there's just overflow check this 00:23:36.340 --> 00:23:38.970 align:start position:0% finally there's just overflow check this is<00:23:36.490> equivalent<00:23:36.790> logic<00:23:37.390> to<00:23:37.660> be<00:23:37.980> salinity 00:23:38.970 --> 00:23:38.980 align:start position:0% is equivalent logic to be salinity 00:23:38.980 --> 00:23:42.810 align:start position:0% is equivalent logic to be salinity implementation<00:23:39.820> and<00:23:40.530> so<00:23:41.530> if<00:23:42.040> the 00:23:42.810 --> 00:23:42.820 align:start position:0% implementation and so if the 00:23:42.820 --> 00:23:45.510 align:start position:0% implementation and so if the preconditions<00:23:43.690> succeed<00:23:44.260> we<00:23:44.980> go<00:23:45.130> into<00:23:45.280> this 00:23:45.510 --> 00:23:45.520 align:start position:0% preconditions succeed we go into this 00:23:45.520 --> 00:23:50.970 align:start position:0% preconditions succeed we go into this case<00:23:45.790> and<00:23:47.010> in<00:23:48.010> this<00:23:48.160> case<00:23:48.430> we<00:23:48.730> simply<00:23:49.980> update 00:23:50.970 --> 00:23:50.980 align:start position:0% case and in this case we simply update 00:23:50.980 --> 00:23:53.520 align:start position:0% case and in this case we simply update the<00:23:51.010> maps<00:23:51.310> such<00:23:51.640> that<00:23:51.940> it<00:23:52.420> reflects<00:23:53.260> the 00:23:53.520 --> 00:23:53.530 align:start position:0% the maps such that it reflects the 00:23:53.530 --> 00:23:55.980 align:start position:0% the maps such that it reflects the appropriate<00:23:54.160> balance<00:23:54.550> is<00:23:54.760> post<00:23:55.150> transfer<00:23:55.690> and 00:23:55.980 --> 00:23:55.990 align:start position:0% appropriate balance is post transfer and 00:23:55.990 --> 00:23:59.550 align:start position:0% appropriate balance is post transfer and then<00:23:56.740> we<00:23:56.920> return<00:23:57.400> true<00:23:58.020> on<00:23:59.020> the<00:23:59.230> return 00:23:59.550 --> 00:23:59.560 align:start position:0% then we return true on the return 00:23:59.560 --> 00:24:02.010 align:start position:0% then we return true on the return channel<00:23:59.710> to<00:24:00.130> signify<00:24:00.490> the<00:24:01.020> transfer 00:24:02.010 --> 00:24:02.020 align:start position:0% channel to signify the transfer 00:24:02.020 --> 00:24:05.520 align:start position:0% channel to signify the transfer succeeded<00:24:02.560> and<00:24:03.240> if<00:24:04.240> the<00:24:04.600> preconditions<00:24:04.780> fail 00:24:05.520 --> 00:24:05.530 align:start position:0% succeeded and if the preconditions fail 00:24:05.530 --> 00:24:12.210 align:start position:0% succeeded and if the preconditions fail we<00:24:06.070> go<00:24:06.190> into<00:24:06.340> this<00:24:06.550> case<00:24:06.820> in<00:24:07.150> which<00:24:11.040> the<00:24:12.040> map 00:24:12.210 --> 00:24:12.220 align:start position:0% we go into this case in which the map 00:24:12.220 --> 00:24:14.910 align:start position:0% we go into this case in which the map back<00:24:12.670> into<00:24:13.300> the<00:24:13.420> balances<00:24:13.810> channel<00:24:14.140> and<00:24:14.800> then 00:24:14.910 --> 00:24:14.920 align:start position:0% back into the balances channel and then 00:24:14.920 --> 00:24:16.560 align:start position:0% back into the balances channel and then sending<00:24:15.190> false<00:24:15.520> on<00:24:15.730> the<00:24:15.760> return<00:24:16.090> channel<00:24:16.270> to 00:24:16.560 --> 00:24:16.570 align:start position:0% sending false on the return channel to 00:24:16.570 --> 00:24:20.570 align:start position:0% sending false on the return channel to signify<00:24:16.870> the<00:24:17.020> transfer<00:24:17.740> feel<00:24:18.900> is<00:24:19.900> there<00:24:20.080> any 00:24:20.570 --> 00:24:20.580 align:start position:0% signify the transfer feel is there any 00:24:20.580 --> 00:24:22.370 align:start position:0% signify the transfer feel is there any questions<00:24:21.580> so<00:24:21.760> far 00:24:22.370 --> 00:24:22.380 align:start position:0% questions so far 00:24:22.380 --> 00:24:29.120 align:start position:0% questions so far sorry<00:24:25.020> any<00:24:26.020> questions<00:24:26.410> so<00:24:26.560> far 00:24:29.120 --> 00:24:29.130 align:start position:0% 00:24:29.130 --> 00:24:39.590 align:start position:0% sweet<00:24:30.130> okay<00:24:33.630> just<00:24:34.630> just<00:24:34.960> show<00:24:35.140> an<00:24:35.260> example<00:24:37.440> oh 00:24:39.590 --> 00:24:39.600 align:start position:0% sweet okay just just show an example oh 00:24:39.600 --> 00:24:49.120 align:start position:0% sweet okay just just show an example oh can<00:24:40.600> you<00:24:40.660> make<00:24:40.810> the<00:24:40.930> view<00:24:41.470> bigger<00:24:41.950> can't<00:24:42.610> sure 00:24:49.120 --> 00:24:49.130 align:start position:0% 00:24:49.130 --> 00:24:53.870 align:start position:0% okay<00:24:50.130> so<00:24:50.610> is<00:24:51.270> that<00:24:51.330> good<00:24:51.570> good<00:24:52.380> better<00:24:52.850> okay 00:24:53.870 --> 00:24:53.880 align:start position:0% okay so is that good good better okay 00:24:53.880 --> 00:25:00.080 align:start position:0% okay so is that good good better okay yeah<00:24:54.240> send<00:24:54.960> -<00:24:56.570> so<00:24:57.570> here<00:24:58.470> we're<00:24:59.250> instantiating 00:25:00.080 --> 00:25:00.090 align:start position:0% yeah send - so here we're instantiating 00:25:00.090 --> 00:25:05.870 align:start position:0% yeah send - so here we're instantiating the<00:25:00.570> token<00:25:01.080> with<00:25:02.000> the<00:25:03.080> with<00:25:04.080> me<00:25:04.590> as<00:25:04.800> the<00:25:05.190> owner 00:25:05.870 --> 00:25:05.880 align:start position:0% the token with the with me as the owner 00:25:05.880 --> 00:25:09.560 align:start position:0% the token with the with me as the owner so<00:25:06.330> to<00:25:06.390> speak<00:25:06.660> a<00:25:07.610> hundred<00:25:08.610> as<00:25:08.790> the<00:25:09.030> initial 00:25:09.560 --> 00:25:09.570 align:start position:0% so to speak a hundred as the initial 00:25:09.570 --> 00:25:13.570 align:start position:0% so to speak a hundred as the initial supply<00:25:09.930> and<00:25:10.290> return<00:25:11.250> as<00:25:11.780> instantiated<00:25:12.780> here 00:25:13.570 --> 00:25:13.580 align:start position:0% supply and return as instantiated here 00:25:13.580 --> 00:25:15.710 align:start position:0% supply and return as instantiated here that's<00:25:14.580> the<00:25:14.850> channel<00:25:15.210> that<00:25:15.390> we're<00:25:15.630> gonna 00:25:15.710 --> 00:25:15.720 align:start position:0% that's the channel that we're gonna 00:25:15.720 --> 00:25:22.040 align:start position:0% that's the channel that we're gonna receive<00:25:16.260> back<00:25:17.450> be<00:25:18.450> bound<00:25:18.690> from<00:25:18.960> and<00:25:19.880> so<00:25:21.050> once 00:25:22.040 --> 00:25:22.050 align:start position:0% receive back be bound from and so once 00:25:22.050 --> 00:25:26.030 align:start position:0% receive back be bound from and so once we<00:25:22.200> bind<00:25:22.710> the<00:25:23.960> the<00:25:24.960> result<00:25:25.350> back<00:25:25.590> into<00:25:25.950> the 00:25:26.030 --> 00:25:26.040 align:start position:0% we bind the the result back into the 00:25:26.040 --> 00:25:29.210 align:start position:0% we bind the the result back into the token<00:25:26.370> contract<00:25:26.820> theater<00:25:27.270> we<00:25:27.960> can<00:25:28.220> retrieve 00:25:29.210 --> 00:25:29.220 align:start position:0% token contract theater we can retrieve 00:25:29.220 --> 00:25:33.020 align:start position:0% token contract theater we can retrieve yet<00:25:29.760> I'm<00:25:30.510> using<00:25:30.740> this<00:25:31.740> get<00:25:32.010> call<00:25:32.280> is<00:25:32.430> an<00:25:32.670> area 00:25:33.020 --> 00:25:33.030 align:start position:0% yet I'm using this get call is an area 00:25:33.030 --> 00:25:37.520 align:start position:0% yet I'm using this get call is an area index<00:25:33.390> into<00:25:33.960> the<00:25:34.200> Kirkland<00:25:34.590> contract<00:25:35.100> and<00:25:36.530> we 00:25:37.520 --> 00:25:37.530 align:start position:0% index into the Kirkland contract and we 00:25:37.530 --> 00:25:40.130 align:start position:0% index into the Kirkland contract and we get<00:25:37.680> the<00:25:37.860> transfer<00:25:38.100> channel<00:25:38.970> and<00:25:39.180> then<00:25:39.840> we 00:25:40.130 --> 00:25:40.140 align:start position:0% get the transfer channel and then we 00:25:40.140 --> 00:25:46.220 align:start position:0% get the transfer channel and then we send<00:25:40.710> from<00:25:41.640> me<00:25:41.910> today<00:25:43.430> 50<00:25:44.430> tokens<00:25:44.640> and<00:25:45.060> so<00:25:45.450> the 00:25:46.220 --> 00:25:46.230 align:start position:0% send from me today 50 tokens and so the 00:25:46.230 --> 00:25:47.900 align:start position:0% send from me today 50 tokens and so the important<00:25:46.620> thing<00:25:46.650> to<00:25:46.770> understand<00:25:47.610> here<00:25:47.700> is 00:25:47.900 --> 00:25:47.910 align:start position:0% important thing to understand here is 00:25:47.910 --> 00:25:50.720 align:start position:0% important thing to understand here is that<00:25:48.300> the<00:25:49.260> name<00:25:49.530> of<00:25:49.560> the<00:25:49.830> nested<00:25:50.250> transfer 00:25:50.720 --> 00:25:50.730 align:start position:0% that the name of the nested transfer 00:25:50.730 --> 00:25:53.300 align:start position:0% that the name of the nested transfer contract<00:25:51.150> that<00:25:51.270> I<00:25:51.360> just<00:25:51.510> described<00:25:51.960> here<00:25:52.470> it's 00:25:53.300 --> 00:25:53.310 align:start position:0% contract that I just described here it's 00:25:53.310 --> 00:25:56.320 align:start position:0% contract that I just described here it's not<00:25:53.550> actually<00:25:54.180> globally<00:25:54.570> accessible<00:25:55.110> and<00:25:55.650> so 00:25:56.320 --> 00:25:56.330 align:start position:0% not actually globally accessible and so 00:25:56.330 --> 00:25:59.150 align:start position:0% not actually globally accessible and so what<00:25:57.330> we're<00:25:57.840> doing<00:25:57.870> here<00:25:58.530> with<00:25:58.710> this<00:25:58.890> area 00:25:59.150 --> 00:25:59.160 align:start position:0% what we're doing here with this area 00:25:59.160 --> 00:26:04.880 align:start position:0% what we're doing here with this area index<00:25:59.580> is<00:25:59.820> we're<00:26:00.540> actually<00:26:01.130> going<00:26:02.130> into<00:26:03.890> or 00:26:04.880 --> 00:26:04.890 align:start position:0% index is we're actually going into or 00:26:04.890 --> 00:26:09.350 align:start position:0% index is we're actually going into or we're<00:26:05.190> having<00:26:05.820> the<00:26:06.830> transfer<00:26:07.830> name<00:26:08.010> here<00:26:08.550> the 00:26:09.350 --> 00:26:09.360 align:start position:0% we're having the transfer name here the 00:26:09.360 --> 00:26:13.400 align:start position:0% we're having the transfer name here the returned<00:26:10.080> out<00:26:10.470> of<00:26:10.890> the<00:26:11.850> token<00:26:12.540> contracts<00:26:13.140> so 00:26:13.400 --> 00:26:13.410 align:start position:0% returned out of the token contracts so 00:26:13.410 --> 00:26:16.610 align:start position:0% returned out of the token contracts so that<00:26:13.440> it's<00:26:14.060> accessible<00:26:15.320> from<00:26:16.320> the<00:26:16.440> outside 00:26:16.610 --> 00:26:16.620 align:start position:0% that it's accessible from the outside 00:26:16.620 --> 00:26:21.470 align:start position:0% that it's accessible from the outside and<00:26:17.430> so<00:26:18.240> we<00:26:18.360> have<00:26:18.480> this<00:26:18.690> like<00:26:18.930> nice<00:26:20.480> scoping 00:26:21.470 --> 00:26:21.480 align:start position:0% and so we have this like nice scoping 00:26:21.480 --> 00:26:24.950 align:start position:0% and so we have this like nice scoping kind<00:26:22.290> of<00:26:22.350> thing<00:26:22.530> going<00:26:22.800> on<00:26:23.070> here<00:26:23.400> and<00:26:23.930> so<00:26:24.930> I 00:26:24.950 --> 00:26:24.960 align:start position:0% kind of thing going on here and so I 00:26:24.960 --> 00:26:27.230 align:start position:0% kind of thing going on here and so I mean<00:26:25.110> just<00:26:25.320> back<00:26:25.530> to<00:26:25.560> the<00:26:25.740> line<00:26:25.890> up<00:26:26.010> here<00:26:26.130> 22<00:26:26.880> we 00:26:27.230 --> 00:26:27.240 align:start position:0% mean just back to the line up here 22 we 00:26:27.240 --> 00:26:30.080 align:start position:0% mean just back to the line up here 22 we just<00:26:27.480> do<00:26:28.440> the<00:26:28.560> same<00:26:28.740> thing<00:26:29.010> by<00:26:29.220> we<00:26:29.700> call<00:26:29.970> the 00:26:30.080 --> 00:26:30.090 align:start position:0% just do the same thing by we call the 00:26:30.090 --> 00:26:31.670 align:start position:0% just do the same thing by we call the balanced<00:26:30.450> although<00:26:30.720> this<00:26:31.050> queries<00:26:31.410> for<00:26:31.620> the 00:26:31.670 --> 00:26:31.680 align:start position:0% balanced although this queries for the 00:26:31.680 --> 00:26:33.950 align:start position:0% balanced although this queries for the balance<00:26:32.040> and<00:26:32.190> then<00:26:32.280> we<00:26:32.340> just<00:26:32.520> put<00:26:32.820> it<00:26:33.510> out<00:26:33.630> here 00:26:33.950 --> 00:26:33.960 align:start position:0% balance and then we just put it out here 00:26:33.960 --> 00:26:38.150 align:start position:0% balance and then we just put it out here and<00:26:35.030> this<00:26:36.030> stuff<00:26:36.360> here<00:26:37.020> is<00:26:37.200> essentially<00:26:37.890> doing 00:26:38.150 --> 00:26:38.160 align:start position:0% and this stuff here is essentially doing 00:26:38.160 --> 00:26:39.890 align:start position:0% and this stuff here is essentially doing the<00:26:38.280> same<00:26:38.370> thing<00:26:38.790> I<00:26:39.090> just<00:26:39.450> wanted<00:26:39.780> to 00:26:39.890 --> 00:26:39.900 align:start position:0% the same thing I just wanted to 00:26:39.900 --> 00:26:43.370 align:start position:0% the same thing I just wanted to demonstrate<00:26:40.080> that<00:26:40.640> you<00:26:41.640> could<00:26:41.940> do<00:26:42.780> this<00:26:42.990> or 00:26:43.370 --> 00:26:43.380 align:start position:0% demonstrate that you could do this or 00:26:43.380 --> 00:26:45.740 align:start position:0% demonstrate that you could do this or you<00:26:43.920> can<00:26:44.070> instantiate<00:26:44.310> multiple<00:26:45.060> tokens<00:26:45.270> in 00:26:45.740 --> 00:26:45.750 align:start position:0% you can instantiate multiple tokens in 00:26:45.750 --> 00:26:49.210 align:start position:0% you can instantiate multiple tokens in parallel<00:26:46.170> within<00:26:46.440> the<00:26:46.560> same<00:26:46.740> session<00:26:47.300> and<00:26:48.300> so 00:26:49.210 --> 00:26:49.220 align:start position:0% parallel within the same session and so 00:26:49.220 --> 00:26:51.380 align:start position:0% parallel within the same session and so we 00:26:51.380 --> 00:26:51.390 align:start position:0% we 00:26:51.390 --> 00:26:56.450 align:start position:0% we on<00:26:51.830> scout<00:26:52.830> using<00:26:53.370> the<00:26:53.700> NFC<00:26:54.170> Java<00:26:55.170> Cub<00:26:55.500> and<00:26:55.679> J 00:26:56.450 --> 00:26:56.460 align:start position:0% on scout using the NFC Java Cub and J 00:26:56.460 --> 00:26:59.750 align:start position:0% on scout using the NFC Java Cub and J labs<00:26:56.700> and<00:26:57.059> so<00:26:57.780> on<00:26:58.590> the<00:26:58.920> bottom<00:26:59.220> here<00:26:59.490> have<00:26:59.610> an 00:26:59.750 --> 00:26:59.760 align:start position:0% labs and so on the bottom here have an 00:26:59.760 --> 00:27:01.820 align:start position:0% labs and so on the bottom here have an SPG<00:27:00.210> console<00:27:00.840> session<00:27:01.260> and<00:27:01.470> I'm<00:27:01.530> just<00:27:01.679> going 00:27:01.820 --> 00:27:01.830 align:start position:0% SPG console session and I'm just going 00:27:01.830 --> 00:27:06.200 align:start position:0% SPG console session and I'm just going to<00:27:01.920> run<00:27:02.220> the<00:27:03.530> compiler<00:27:04.530> on<00:27:04.950> the<00:27:05.640> token 00:27:06.200 --> 00:27:06.210 align:start position:0% to run the compiler on the token 00:27:06.210 --> 00:27:08.930 align:start position:0% to run the compiler on the token contract<00:27:06.720> file<00:27:06.960> that<00:27:07.320> I<00:27:07.650> just<00:27:07.980> explained<00:27:08.549> here 00:27:08.930 --> 00:27:08.940 align:start position:0% contract file that I just explained here 00:27:08.940 --> 00:27:15.350 align:start position:0% contract file that I just explained here and<00:27:10.429> boom<00:27:11.429> we<00:27:11.850> see<00:27:12.240> here<00:27:13.200> the<00:27:13.710> output<00:27:13.860> and<00:27:14.400> so 00:27:15.350 --> 00:27:15.360 align:start position:0% and boom we see here the output and so 00:27:15.360 --> 00:27:19.039 align:start position:0% and boom we see here the output and so what<00:27:16.230> you<00:27:16.290> see<00:27:16.500> here<00:27:16.530> is<00:27:16.740> called<00:27:16.980> rbl<00:27:18.049> rosette 00:27:19.039 --> 00:27:19.049 align:start position:0% what you see here is called rbl rosette 00:27:19.049 --> 00:27:21.830 align:start position:0% what you see here is called rbl rosette base<00:27:19.260> language<00:27:19.710> and<00:27:20.130> in<00:27:21.030> the<00:27:21.150> future<00:27:21.450> we<00:27:21.809> plan 00:27:21.830 --> 00:27:21.840 align:start position:0% base language and in the future we plan 00:27:21.840 --> 00:27:24.380 align:start position:0% base language and in the future we plan to<00:27:22.140> just<00:27:22.470> bootstrap<00:27:23.160> relay<00:27:23.580> but<00:27:23.850> for<00:27:24.240> now<00:27:24.330> we 00:27:24.380 --> 00:27:24.390 align:start position:0% to just bootstrap relay but for now we 00:27:24.390 --> 00:27:26.960 align:start position:0% to just bootstrap relay but for now we find<00:27:24.900> a<00:27:24.960> convenient<00:27:25.320> just<00:27:25.679> to<00:27:25.940> you<00:27:26.940> know 00:27:26.960 --> 00:27:26.970 align:start position:0% find a convenient just to you know 00:27:26.970 --> 00:27:28.490 align:start position:0% find a convenient just to you know compile<00:27:27.510> it<00:27:27.660> down<00:27:27.690> to<00:27:27.870> this<00:27:28.110> intermediate 00:27:28.490 --> 00:27:28.500 align:start position:0% compile it down to this intermediate 00:27:28.500 --> 00:27:33.409 align:start position:0% compile it down to this intermediate language<00:27:28.950> because<00:27:29.640> there's<00:27:30.540> a<00:27:30.630> nice<00:27:32.090> VM<00:27:33.090> for 00:27:33.409 --> 00:27:33.419 align:start position:0% language because there's a nice VM for 00:27:33.419 --> 00:27:37.070 align:start position:0% language because there's a nice VM for it<00:27:33.540> which<00:27:34.250> or<00:27:35.250> an<00:27:35.790> interpreter<00:27:36.360> I<00:27:36.630> should<00:27:36.870> say 00:27:37.070 --> 00:27:37.080 align:start position:0% it which or an interpreter I should say 00:27:37.080 --> 00:27:42.289 align:start position:0% it which or an interpreter I should say right<00:27:37.590> here<00:27:39.860> it<00:27:40.860> has<00:27:41.040> maybe<00:27:41.429> an<00:27:41.669> unusual 00:27:42.289 --> 00:27:42.299 align:start position:0% right here it has maybe an unusual 00:27:42.299 --> 00:27:44.990 align:start position:0% right here it has maybe an unusual syntax<00:27:42.809> but<00:27:42.990> it's<00:27:43.679> just<00:27:44.490> like<00:27:44.640> any<00:27:44.820> other 00:27:44.990 --> 00:27:45.000 align:start position:0% syntax but it's just like any other 00:27:45.000 --> 00:27:48.650 align:start position:0% syntax but it's just like any other interpreter<00:27:45.630> and<00:27:46.290> so<00:27:46.910> what's<00:27:47.910> important<00:27:48.390> here 00:27:48.650 --> 00:27:48.660 align:start position:0% interpreter and so what's important here 00:27:48.660 --> 00:27:51.409 align:start position:0% interpreter and so what's important here is<00:27:48.720> that<00:27:49.309> or<00:27:50.309> what<00:27:50.520> we're<00:27:50.640> interested<00:27:50.850> in<00:27:51.120> here 00:27:51.409 --> 00:27:51.419 align:start position:0% is that or what we're interested in here 00:27:51.419 --> 00:27:54.380 align:start position:0% is that or what we're interested in here is<00:27:51.450> pasting<00:27:52.350> in<00:27:52.500> the<00:27:53.100> compiler<00:27:53.730> out<00:27:53.880> of<00:27:54.240> the 00:27:54.380 --> 00:27:54.390 align:start position:0% is pasting in the compiler out of the 00:27:54.390 --> 00:27:57.260 align:start position:0% is pasting in the compiler out of the token<00:27:54.720> contract<00:27:55.200> in<00:27:55.350> here<00:27:55.770> and<00:27:56.190> that's<00:27:57.059> what 00:27:57.260 --> 00:27:57.270 align:start position:0% token contract in here and that's what 00:27:57.270 --> 00:28:00.760 align:start position:0% token contract in here and that's what I'll<00:27:57.390> do<00:27:57.600> right<00:27:57.630> now<00:27:58.640> actually<00:27:59.640> one<00:27:59.850> second 00:28:00.760 --> 00:28:00.770 align:start position:0% I'll do right now actually one second 00:28:00.770 --> 00:28:07.880 align:start position:0% I'll do right now actually one second let<00:28:01.770> me<00:28:01.799> just<00:28:03.530> have<00:28:04.530> to<00:28:04.710> do<00:28:04.950> is<00:28:06.350> have<00:28:07.350> to<00:28:07.590> break 00:28:07.880 --> 00:28:07.890 align:start position:0% let me just have to do is have to break 00:28:07.890 --> 00:28:15.980 align:start position:0% let me just have to do is have to break the<00:28:10.940> mostly<00:28:11.940> because<00:28:12.179> of<00:28:13.460> the<00:28:14.460> rebels<00:28:15.030> maximum 00:28:15.980 --> 00:28:15.990 align:start position:0% the mostly because of the rebels maximum 00:28:15.990 --> 00:28:20.570 align:start position:0% the mostly because of the rebels maximum input<00:28:16.890> length<00:28:17.400> requirement<00:28:18.679> and<00:28:19.679> so<00:28:20.070> once<00:28:20.309> we 00:28:20.570 --> 00:28:20.580 align:start position:0% input length requirement and so once we 00:28:20.580 --> 00:28:25.190 align:start position:0% input length requirement and so once we do<00:28:20.730> that<00:28:20.760> and<00:28:21.530> copy<00:28:22.530> it<00:28:22.770> in<00:28:23.510> you<00:28:24.510> can<00:28:24.660> see<00:28:24.870> here 00:28:25.190 --> 00:28:25.200 align:start position:0% do that and copy it in you can see here 00:28:25.200 --> 00:28:29.590 align:start position:0% do that and copy it in you can see here this<00:28:25.740> is<00:28:25.799> what<00:28:26.130> I<00:28:26.190> just<00:28:26.340> copied<00:28:27.830> this<00:28:28.830> is 00:28:29.590 --> 00:28:29.600 align:start position:0% this is what I just copied this is 00:28:29.600 --> 00:28:36.020 align:start position:0% this is what I just copied this is equivalent<00:28:30.600> to<00:28:31.260> the<00:28:32.130> output<00:28:32.490> here<00:28:32.820> and<00:28:34.760> if<00:28:35.760> we 00:28:36.020 --> 00:28:36.030 align:start position:0% equivalent to the output here and if we 00:28:36.030 --> 00:28:38.630 align:start position:0% equivalent to the output here and if we ignore<00:28:36.270> some<00:28:36.660> warnings<00:28:37.200> and<00:28:37.650> debug 00:28:38.630 --> 00:28:38.640 align:start position:0% ignore some warnings and debug 00:28:38.640 --> 00:28:42.530 align:start position:0% ignore some warnings and debug statements<00:28:39.570> we<00:28:40.350> can<00:28:40.380> see<00:28:40.710> here<00:28:40.980> the<00:28:41.760> value<00:28:41.910> 50 00:28:42.530 --> 00:28:42.540 align:start position:0% statements we can see here the value 50 00:28:42.540 --> 00:28:46.730 align:start position:0% statements we can see here the value 50 that<00:28:43.169> gets<00:28:43.380> outputted<00:28:43.830> in<00:28:43.980> 500<00:28:44.760> and<00:28:45.059> so<00:28:45.740> what 00:28:46.730 --> 00:28:46.740 align:start position:0% that gets outputted in 500 and so what 00:28:46.740 --> 00:28:49.820 align:start position:0% that gets outputted in 500 and so what these<00:28:46.950> two<00:28:47.280> numbers<00:28:47.640> are<00:28:47.790> correspond<00:28:48.540> to<00:28:48.830> the 00:28:49.820 --> 00:28:49.830 align:start position:0% these two numbers are correspond to the 00:28:49.830 --> 00:28:51.770 align:start position:0% these two numbers are correspond to the print<00:28:50.160> statements<00:28:50.700> here<00:28:50.970> right<00:28:51.330> remember<00:28:51.540> we 00:28:51.770 --> 00:28:51.780 align:start position:0% print statements here right remember we 00:28:51.780 --> 00:28:54.200 align:start position:0% print statements here right remember we transferred<00:28:52.290> 50<00:28:52.710> today<00:28:52.860> so<00:28:53.370> they<00:28:53.520> shoot<00:28:53.700> at<00:28:53.820> 50 00:28:54.200 --> 00:28:54.210 align:start position:0% transferred 50 today so they shoot at 50 00:28:54.210 --> 00:28:57.350 align:start position:0% transferred 50 today so they shoot at 50 and<00:28:54.450> the<00:28:55.020> way<00:28:55.169> they<00:28:56.070> balance<00:28:56.429> two<00:28:56.850> should<00:28:57.299> have 00:28:57.350 --> 00:28:57.360 align:start position:0% and the way they balance two should have 00:28:57.360 --> 00:29:00.140 align:start position:0% and the way they balance two should have 500<00:28:58.110> because<00:28:58.440> that's<00:28:58.650> what<00:28:58.830> we<00:28:59.150> transferred 00:29:00.140 --> 00:29:00.150 align:start position:0% 500 because that's what we transferred 00:29:00.150 --> 00:29:02.500 align:start position:0% 500 because that's what we transferred over<00:29:00.419> here<00:29:00.860> and<00:29:01.860> pretty 00:29:02.500 --> 00:29:02.510 align:start position:0% over here and pretty 00:29:02.510 --> 00:29:06.730 align:start position:0% over here and pretty and<00:29:02.690> so<00:29:03.610> that's<00:29:04.610> essentially<00:29:05.290> the<00:29:06.290> Burling 00:29:06.730 --> 00:29:06.740 align:start position:0% and so that's essentially the Burling 00:29:06.740 --> 00:29:09.280 align:start position:0% and so that's essentially the Burling demo<00:29:06.950> of<00:29:07.250> the<00:29:07.460> your<00:29:07.820> c<00:29:08.060> 20<00:29:08.510> contract<00:29:09.050> in<00:29:09.230> a 00:29:09.280 --> 00:29:09.290 align:start position:0% demo of the your c 20 contract in a 00:29:09.290 --> 00:29:12.460 align:start position:0% demo of the your c 20 contract in a nutshell<00:29:10.540> thank<00:29:11.540> you<00:29:11.720> Thank<00:29:11.960> You<00:29:12.020> Kent<00:29:12.320> I 00:29:12.460 --> 00:29:12.470 align:start position:0% nutshell thank you Thank You Kent I 00:29:12.470 --> 00:29:16.330 align:start position:0% nutshell thank you Thank You Kent I really<00:29:12.800> appreciate<00:29:13.160> that<00:29:13.190> so<00:29:14.710> so<00:29:15.710> obviously 00:29:16.330 --> 00:29:16.340 align:start position:0% really appreciate that so so obviously 00:29:16.340 --> 00:29:17.680 align:start position:0% really appreciate that so so obviously you<00:29:16.550> can<00:29:16.580> see<00:29:16.730> that<00:29:16.880> this<00:29:17.270> is<00:29:17.420> work<00:29:17.570> in 00:29:17.680 --> 00:29:17.690 align:start position:0% you can see that this is work in 00:29:17.690 --> 00:29:20.080 align:start position:0% you can see that this is work in progress<00:29:17.800> we're<00:29:18.800> in<00:29:19.040> the<00:29:19.400> midst<00:29:19.670> of<00:29:19.730> building 00:29:20.080 --> 00:29:20.090 align:start position:0% progress we're in the midst of building 00:29:20.090 --> 00:29:24.760 align:start position:0% progress we're in the midst of building this<00:29:21.460> let<00:29:22.460> me<00:29:22.640> quickly<00:29:23.300> just<00:29:23.930> close<00:29:24.350> this<00:29:24.560> out 00:29:24.760 --> 00:29:24.770 align:start position:0% this let me quickly just close this out 00:29:24.770 --> 00:29:26.440 align:start position:0% this let me quickly just close this out because<00:29:24.890> I<00:29:25.160> know<00:29:25.250> I<00:29:25.370> want<00:29:25.760> to<00:29:25.820> give<00:29:25.940> back<00:29:25.970> yield 00:29:26.440 --> 00:29:26.450 align:start position:0% because I know I want to give back yield 00:29:26.450 --> 00:29:36.070 align:start position:0% because I know I want to give back yield back<00:29:26.600> time<00:29:26.870> if<00:29:26.930> I<00:29:27.170> can<00:29:33.730> okay<00:29:34.730> so<00:29:34.790> so<00:29:35.360> -<00:29:35.420> so<00:29:35.930> what 00:29:36.070 --> 00:29:36.080 align:start position:0% back time if I can okay so so - so what 00:29:36.080 --> 00:29:42.360 align:start position:0% back time if I can okay so so - so what you<00:29:36.200> saw<00:29:36.590> was<00:29:37.490> a<00:29:38.650> side-by-side<00:29:39.730> comparison<00:29:40.730> of 00:29:42.360 --> 00:29:42.370 align:start position:0% you saw was a side-by-side comparison of 00:29:42.370 --> 00:29:47.680 align:start position:0% you saw was a side-by-side comparison of ERC<00:29:43.370> 20<00:29:43.700> like<00:29:43.910> behavior<00:29:44.480> in<00:29:45.220> row<00:29:46.220> lang<00:29:46.690> which 00:29:47.680 --> 00:29:47.690 align:start position:0% ERC 20 like behavior in row lang which 00:29:47.690 --> 00:29:49.480 align:start position:0% ERC 20 like behavior in row lang which is<00:29:47.900> gives<00:29:48.200> you<00:29:48.320> a<00:29:48.350> sense<00:29:48.710> that<00:29:48.980> the<00:29:49.130> language 00:29:49.480 --> 00:29:49.490 align:start position:0% is gives you a sense that the language 00:29:49.490 --> 00:29:51.820 align:start position:0% is gives you a sense that the language scales<00:29:49.850> up<00:29:50.150> it<00:29:50.390> scales<00:29:50.750> up<00:29:50.990> why<00:29:51.230> because<00:29:51.260> it's 00:29:51.820 --> 00:29:51.830 align:start position:0% scales up it scales up why because it's 00:29:51.830 --> 00:29:53.950 align:start position:0% scales up it scales up why because it's at<00:29:52.130> least<00:29:52.310> as<00:29:52.550> expressive<00:29:53.180> they're<00:29:53.660> more 00:29:53.950 --> 00:29:53.960 align:start position:0% at least as expressive they're more 00:29:53.960 --> 00:29:55.930 align:start position:0% at least as expressive they're more they're<00:29:54.530> more<00:29:54.710> or<00:29:54.740> less<00:29:54.920> the<00:29:55.070> same<00:29:55.250> line<00:29:55.610> count 00:29:55.930 --> 00:29:55.940 align:start position:0% they're more or less the same line count 00:29:55.940 --> 00:29:57.880 align:start position:0% they're more or less the same line count but<00:29:56.480> you<00:29:56.630> get<00:29:56.870> all<00:29:57.110> of<00:29:57.260> these<00:29:57.380> features<00:29:57.860> that 00:29:57.880 --> 00:29:57.890 align:start position:0% but you get all of these features that 00:29:57.890 --> 00:30:01.120 align:start position:0% but you get all of these features that we<00:29:58.190> we<00:29:58.520> talked<00:29:58.790> about<00:29:59.030> before<00:29:59.210> so<00:29:59.770> the<00:30:00.770> things 00:30:01.120 --> 00:30:01.130 align:start position:0% we we talked about before so the things 00:30:01.130 --> 00:30:02.890 align:start position:0% we we talked about before so the things that<00:30:01.220> we<00:30:01.310> haven't<00:30:01.820> talked<00:30:02.030> about<00:30:02.210> and<00:30:02.570> I<00:30:02.750> would 00:30:02.890 --> 00:30:02.900 align:start position:0% that we haven't talked about and I would 00:30:02.900 --> 00:30:04.510 align:start position:0% that we haven't talked about and I would love<00:30:03.080> for<00:30:03.110> you<00:30:03.320> to<00:30:03.650> come<00:30:03.800> up<00:30:03.980> to<00:30:04.130> me<00:30:04.220> and<00:30:04.340> talk 00:30:04.510 --> 00:30:04.520 align:start position:0% love for you to come up to me and talk 00:30:04.520 --> 00:30:07.330 align:start position:0% love for you to come up to me and talk about<00:30:04.990> after<00:30:05.990> the<00:30:06.020> in<00:30:06.290> breakout<00:30:06.710> sessions<00:30:07.160> and 00:30:07.330 --> 00:30:07.340 align:start position:0% about after the in breakout sessions and 00:30:07.340 --> 00:30:09.190 align:start position:0% about after the in breakout sessions and other<00:30:07.430> kinds<00:30:07.760> of<00:30:07.850> things<00:30:08.000> is<00:30:08.240> the<00:30:08.720> behavioral 00:30:09.190 --> 00:30:09.200 align:start position:0% other kinds of things is the behavioral 00:30:09.200 --> 00:30:13.270 align:start position:0% other kinds of things is the behavioral types<00:30:09.560> so<00:30:10.370> you<00:30:11.260> kept<00:30:12.260> hinting<00:30:12.530> that<00:30:12.830> we<00:30:13.130> can 00:30:13.270 --> 00:30:13.280 align:start position:0% types so you kept hinting that we can 00:30:13.280 --> 00:30:15.370 align:start position:0% types so you kept hinting that we can just<00:30:13.460> look<00:30:13.760> at<00:30:13.940> the<00:30:14.060> program<00:30:14.510> and<00:30:14.840> start<00:30:15.260> to 00:30:15.370 --> 00:30:15.380 align:start position:0% just look at the program and start to 00:30:15.380 --> 00:30:17.820 align:start position:0% just look at the program and start to see<00:30:15.620> things<00:30:15.830> like<00:30:16.130> sharding<00:30:16.970> and<00:30:17.120> concurrency 00:30:17.820 --> 00:30:17.830 align:start position:0% see things like sharding and concurrency 00:30:17.830 --> 00:30:22.210 align:start position:0% see things like sharding and concurrency kinds<00:30:18.830> of<00:30:19.420> opportunities<00:30:20.420> or<00:30:20.630> behaviors<00:30:21.220> the 00:30:22.210 --> 00:30:22.220 align:start position:0% kinds of opportunities or behaviors the 00:30:22.220 --> 00:30:24.250 align:start position:0% kinds of opportunities or behaviors the behavioral<00:30:22.790> types<00:30:23.060> catch<00:30:23.450> that<00:30:23.720> at<00:30:23.870> compile 00:30:24.250 --> 00:30:24.260 align:start position:0% behavioral types catch that at compile 00:30:24.260 --> 00:30:28.270 align:start position:0% behavioral types catch that at compile time<00:30:24.290> so<00:30:25.190> for<00:30:25.790> example<00:30:26.270> the<00:30:26.780> dau<00:30:27.080> bug<00:30:27.440> we<00:30:28.070> would 00:30:28.270 --> 00:30:28.280 align:start position:0% time so for example the dau bug we would 00:30:28.280 --> 00:30:30.310 align:start position:0% time so for example the dau bug we would have<00:30:28.400> caught<00:30:28.640> at<00:30:28.790> compile<00:30:29.630> time<00:30:29.660> the 00:30:30.310 --> 00:30:30.320 align:start position:0% have caught at compile time the 00:30:30.320 --> 00:30:32.620 align:start position:0% have caught at compile time the principal<00:30:30.980> bug<00:30:31.190> that<00:30:31.400> caused<00:30:31.640> the<00:30:31.850> problem<00:30:32.300> we 00:30:32.620 --> 00:30:32.630 align:start position:0% principal bug that caused the problem we 00:30:32.630 --> 00:30:34.300 align:start position:0% principal bug that caused the problem we would<00:30:32.810> have<00:30:32.930> caught<00:30:33.140> before<00:30:33.590> the<00:30:33.920> code<00:30:34.130> was 00:30:34.300 --> 00:30:34.310 align:start position:0% would have caught before the code was 00:30:34.310 --> 00:30:39.520 align:start position:0% would have caught before the code was ever<00:30:34.460> checked<00:30:34.760> in<00:30:36.820> namespaces<00:30:37.820> our<00:30:38.420> our<00:30:39.020> ports 00:30:39.520 --> 00:30:39.530 align:start position:0% ever checked in namespaces our our ports 00:30:39.530 --> 00:30:41.770 align:start position:0% ever checked in namespaces our our ports and<00:30:39.650> channels<00:30:40.130> are<00:30:40.430> describable<00:30:41.330> because 00:30:41.770 --> 00:30:41.780 align:start position:0% and channels are describable because 00:30:41.780 --> 00:30:43.360 align:start position:0% and channels are describable because they<00:30:41.900> have<00:30:42.050> internal<00:30:42.650> structure<00:30:43.040> they're<00:30:43.220> not 00:30:43.360 --> 00:30:43.370 align:start position:0% they have internal structure they're not 00:30:43.370 --> 00:30:45.250 align:start position:0% they have internal structure they're not just<00:30:43.580> flat<00:30:43.790> addresses<00:30:44.420> they're<00:30:44.870> actually 00:30:45.250 --> 00:30:45.260 align:start position:0% just flat addresses they're actually 00:30:45.260 --> 00:30:48.130 align:start position:0% just flat addresses they're actually paths<00:30:45.590> or<00:30:46.040> algebraic<00:30:47.000> there's<00:30:47.450> an<00:30:47.540> algebra<00:30:47.990> on 00:30:48.130 --> 00:30:48.140 align:start position:0% paths or algebraic there's an algebra on 00:30:48.140 --> 00:30:51.370 align:start position:0% paths or algebraic there's an algebra on ports<00:30:48.620> and<00:30:48.890> because<00:30:49.760> of<00:30:49.970> that<00:30:50.200> we<00:30:51.200> can 00:30:51.370 --> 00:30:51.380 align:start position:0% ports and because of that we can 00:30:51.380 --> 00:30:53.920 align:start position:0% ports and because of that we can describe<00:30:51.710> sets<00:30:52.220> of<00:30:52.460> names<00:30:52.700> so<00:30:53.330> we<00:30:53.510> can<00:30:53.690> we<00:30:53.900> can 00:30:53.920 --> 00:30:53.930 align:start position:0% describe sets of names so we can we can 00:30:53.930 --> 00:30:55.750 align:start position:0% describe sets of names so we can we can constrain<00:30:54.500> it<00:30:54.680> that<00:30:54.860> way<00:30:55.010> and<00:30:55.190> that<00:30:55.310> gives<00:30:55.580> us 00:30:55.750 --> 00:30:55.760 align:start position:0% constrain it that way and that gives us 00:30:55.760 --> 00:31:00.190 align:start position:0% constrain it that way and that gives us a<00:30:55.910> sharding<00:30:56.360> solution<00:30:56.950> ro<00:30:57.950> Scala<00:30:58.630> is<00:30:59.630> what 00:31:00.190 --> 00:31:00.200 align:start position:0% a sharding solution ro Scala is what 00:31:00.200 --> 00:31:02.620 align:start position:0% a sharding solution ro Scala is what plugs<00:31:00.980> the<00:31:01.250> gap<00:31:01.280> that<00:31:01.670> you<00:31:01.820> saw<00:31:02.030> there<00:31:02.360> where 00:31:02.620 --> 00:31:02.630 align:start position:0% plugs the gap that you saw there where 00:31:02.630 --> 00:31:04.720 align:start position:0% plugs the gap that you saw there where kent<00:31:02.900> was<00:31:03.080> compiling<00:31:03.560> to<00:31:03.920> our<00:31:04.070> BL<00:31:04.370> and<00:31:04.640> then 00:31:04.720 --> 00:31:04.730 align:start position:0% kent was compiling to our BL and then 00:31:04.730 --> 00:31:06.580 align:start position:0% kent was compiling to our BL and then pasting<00:31:05.180> it<00:31:05.300> into<00:31:05.570> a<00:31:05.600> Rosetta<00:31:06.050> interpreter 00:31:06.580 --> 00:31:06.590 align:start position:0% pasting it into a Rosetta interpreter 00:31:06.590 --> 00:31:08.920 align:start position:0% pasting it into a Rosetta interpreter which<00:31:07.220> uses<00:31:07.760> the<00:31:07.880> rosette<00:31:08.240> virtual<00:31:08.600> machine 00:31:08.920 --> 00:31:08.930 align:start position:0% which uses the rosette virtual machine 00:31:08.930 --> 00:31:11.980 align:start position:0% which uses the rosette virtual machine so<00:31:09.470> the<00:31:09.920> ROS<00:31:10.100> Scala<00:31:10.640> is<00:31:11.390> the<00:31:11.690> Scala 00:31:11.980 --> 00:31:11.990 align:start position:0% so the ROS Scala is the Scala 00:31:11.990 --> 00:31:13.840 align:start position:0% so the ROS Scala is the Scala re-implementation<00:31:12.800> of<00:31:12.830> the<00:31:13.160> rosette<00:31:13.490> virtual 00:31:13.840 --> 00:31:13.850 align:start position:0% re-implementation of the rosette virtual 00:31:13.850 --> 00:31:15.670 align:start position:0% re-implementation of the rosette virtual machine<00:31:14.150> which<00:31:14.540> would<00:31:14.750> allow<00:31:15.050> Kent 00:31:15.670 --> 00:31:15.680 align:start position:0% machine which would allow Kent 00:31:15.680 --> 00:31:18.790 align:start position:0% machine which would allow Kent to<00:31:15.770> directly<00:31:16.340> feed<00:31:16.640> that<00:31:16.880> code<00:31:17.260> into<00:31:18.260> the<00:31:18.290> the 00:31:18.790 --> 00:31:18.800 align:start position:0% to directly feed that code into the the 00:31:18.800 --> 00:31:22.810 align:start position:0% to directly feed that code into the the VM<00:31:19.040> and<00:31:19.220> execute<00:31:19.760> it<00:31:19.880> and<00:31:20.750> then<00:31:21.110> also<00:31:21.820> please 00:31:22.810 --> 00:31:22.820 align:start position:0% VM and execute it and then also please 00:31:22.820 --> 00:31:26.110 align:start position:0% VM and execute it and then also please come<00:31:23.090> and<00:31:23.240> talk<00:31:23.810> to<00:31:23.840> talk<00:31:24.410> to<00:31:24.590> us<00:31:24.710> about<00:31:25.220> our 00:31:26.110 --> 00:31:26.120 align:start position:0% come and talk to talk to us about our 00:31:26.120 --> 00:31:27.700 align:start position:0% come and talk to talk to us about our chain<00:31:26.510> itself<00:31:26.870> which<00:31:27.170> is<00:31:27.320> where<00:31:27.470> all<00:31:27.590> this 00:31:27.700 --> 00:31:27.710 align:start position:0% chain itself which is where all this 00:31:27.710 --> 00:31:33.220 align:start position:0% chain itself which is where all this work<00:31:28.040> is<00:31:28.250> happening<00:31:28.700> and<00:31:28.850> and<00:31:29.780> our<00:31:30.020> we're<00:31:30.770> very