WEBVTT Kind: captions Language: en 00:00:00.000 --> 00:00:04.350 align:start position:0% foreign 00:00:04.350 --> 00:00:04.360 align:start position:0% 00:00:04.360 --> 00:00:16.189 align:start position:0% [Music] 00:00:16.189 --> 00:00:16.199 align:start position:0% 00:00:16.199 --> 00:00:18.290 align:start position:0% yeah<00:00:16.500> you<00:00:16.680> can<00:00:16.800> hear<00:00:16.859> me<00:00:17.039> right 00:00:18.290 --> 00:00:18.300 align:start position:0% yeah you can hear me right 00:00:18.300 --> 00:00:20.990 align:start position:0% yeah you can hear me right and<00:00:18.660> I<00:00:18.779> hope<00:00:18.900> this<00:00:19.080> works<00:00:19.380> as<00:00:19.500> well 00:00:20.990 --> 00:00:21.000 align:start position:0% and I hope this works as well 00:00:21.000 --> 00:00:22.910 align:start position:0% and I hope this works as well okay<00:00:21.359> it<00:00:21.600> does 00:00:22.910 --> 00:00:22.920 align:start position:0% okay it does 00:00:22.920 --> 00:00:23.630 align:start position:0% okay it does um 00:00:23.630 --> 00:00:23.640 align:start position:0% um 00:00:23.640 --> 00:00:25.670 align:start position:0% um yes<00:00:24.000> Francie<00:00:24.539> said<00:00:24.720> uh<00:00:24.960> thank<00:00:25.260> you<00:00:25.320> for<00:00:25.560> the 00:00:25.670 --> 00:00:25.680 align:start position:0% yes Francie said uh thank you for the 00:00:25.680 --> 00:00:28.429 align:start position:0% yes Francie said uh thank you for the intro<00:00:25.980> and<00:00:26.699> I<00:00:26.820> wanted<00:00:26.939> to<00:00:27.119> also<00:00:27.420> make<00:00:28.260> sure 00:00:28.429 --> 00:00:28.439 align:start position:0% intro and I wanted to also make sure 00:00:28.439 --> 00:00:30.170 align:start position:0% intro and I wanted to also make sure that<00:00:29.099> um 00:00:30.170 --> 00:00:30.180 align:start position:0% that um 00:00:30.180 --> 00:00:31.849 align:start position:0% that um a<00:00:30.599> lot<00:00:30.660> of<00:00:30.779> this<00:00:30.900> stuff<00:00:31.019> is<00:00:31.199> my<00:00:31.380> opinion<00:00:31.619> it's 00:00:31.849 --> 00:00:31.859 align:start position:0% a lot of this stuff is my opinion it's 00:00:31.859 --> 00:00:35.030 align:start position:0% a lot of this stuff is my opinion it's not<00:00:31.980> like<00:00:32.099> the<00:00:32.279> opinion<00:00:32.520> of<00:00:32.700> the<00:00:33.120> team<00:00:33.920> I<00:00:34.920> have 00:00:35.030 --> 00:00:35.040 align:start position:0% not like the opinion of the team I have 00:00:35.040 --> 00:00:38.569 align:start position:0% not like the opinion of the team I have been<00:00:35.160> working<00:00:35.340> on<00:00:35.579> solitary<00:00:36.120> since<00:00:36.420> 2015.<00:00:37.800> and 00:00:38.569 --> 00:00:38.579 align:start position:0% been working on solitary since 2015. and 00:00:38.579 --> 00:00:40.610 align:start position:0% been working on solitary since 2015. and in<00:00:39.239> the<00:00:39.420> past<00:00:39.540> year<00:00:39.780> I've<00:00:40.079> been<00:00:40.260> kind<00:00:40.440> of<00:00:40.500> like 00:00:40.610 --> 00:00:40.620 align:start position:0% in the past year I've been kind of like 00:00:40.620 --> 00:00:43.190 align:start position:0% in the past year I've been kind of like taking<00:00:40.800> a<00:00:40.980> break<00:00:41.160> and<00:00:42.000> uh<00:00:42.300> did<00:00:42.660> write<00:00:42.840> a<00:00:43.020> lot<00:00:43.140> of 00:00:43.190 --> 00:00:43.200 align:start position:0% taking a break and uh did write a lot of 00:00:43.200 --> 00:00:46.310 align:start position:0% taking a break and uh did write a lot of code<00:00:43.640> in<00:00:44.640> solidity<00:00:45.120> itself 00:00:46.310 --> 00:00:46.320 align:start position:0% code in solidity itself 00:00:46.320 --> 00:00:48.590 align:start position:0% code in solidity itself and<00:00:47.100> I<00:00:47.399> think<00:00:47.520> some<00:00:47.700> of<00:00:47.820> this<00:00:47.940> is<00:00:48.120> like<00:00:48.300> a 00:00:48.590 --> 00:00:48.600 align:start position:0% and I think some of this is like a 00:00:48.600 --> 00:00:50.750 align:start position:0% and I think some of this is like a culmination<00:00:49.379> of<00:00:49.559> of<00:00:49.860> you<00:00:50.280> know<00:00:50.340> my<00:00:50.520> experience 00:00:50.750 --> 00:00:50.760 align:start position:0% culmination of of you know my experience 00:00:50.760 --> 00:00:52.910 align:start position:0% culmination of of you know my experience using<00:00:51.180> the<00:00:51.239> language<00:00:51.480> but<00:00:52.379> I<00:00:52.500> hope<00:00:52.620> some<00:00:52.800> of 00:00:52.910 --> 00:00:52.920 align:start position:0% using the language but I hope some of 00:00:52.920 --> 00:00:55.010 align:start position:0% using the language but I hope some of these<00:00:53.100> things<00:00:53.219> are<00:00:53.520> mentioning<00:00:54.000> may<00:00:54.660> come<00:00:54.840> to 00:00:55.010 --> 00:00:55.020 align:start position:0% these things are mentioning may come to 00:00:55.020 --> 00:00:59.029 align:start position:0% these things are mentioning may come to infusion<00:00:55.500> okay<00:00:56.340> so<00:00:57.559> 0817<00:00:58.559> is<00:00:58.800> the<00:00:58.920> latest 00:00:59.029 --> 00:00:59.039 align:start position:0% infusion okay so 0817 is the latest 00:00:59.039 --> 00:00:59.869 align:start position:0% infusion okay so 0817 is the latest release 00:00:59.869 --> 00:00:59.879 align:start position:0% release 00:00:59.879 --> 00:01:02.270 align:start position:0% release it's<00:01:00.420> a<00:01:00.539> hundred<00:01:00.780> second<00:01:01.079> release<00:01:01.440> we<00:01:02.100> already 00:01:02.270 --> 00:01:02.280 align:start position:0% it's a hundred second release we already 00:01:02.280 --> 00:01:05.030 align:start position:0% it's a hundred second release we already had<00:01:02.579> more<00:01:02.820> than<00:01:02.940> 100<00:01:03.059> releases<00:01:04.140> that<00:01:04.739> is<00:01:04.860> just 00:01:05.030 --> 00:01:05.040 align:start position:0% had more than 100 releases that is just 00:01:05.040 --> 00:01:06.170 align:start position:0% had more than 100 releases that is just insane 00:01:06.170 --> 00:01:06.180 align:start position:0% insane 00:01:06.180 --> 00:01:07.730 align:start position:0% insane and<00:01:06.659> we<00:01:06.840> probably<00:01:07.020> have<00:01:07.200> more<00:01:07.380> than<00:01:07.500> like<00:01:07.680> a 00:01:07.730 --> 00:01:07.740 align:start position:0% and we probably have more than like a 00:01:07.740 --> 00:01:10.310 align:start position:0% and we probably have more than like a thousand<00:01:08.100> night<00:01:08.340> leads<00:01:08.760> which<00:01:09.420> is 00:01:10.310 --> 00:01:10.320 align:start position:0% thousand night leads which is 00:01:10.320 --> 00:01:13.490 align:start position:0% thousand night leads which is just<00:01:10.860> crazy<00:01:11.360> basically<00:01:12.360> we<00:01:12.659> had<00:01:12.900> eight 00:01:13.490 --> 00:01:13.500 align:start position:0% just crazy basically we had eight 00:01:13.500 --> 00:01:15.710 align:start position:0% just crazy basically we had eight breaking<00:01:13.979> releases<00:01:14.340> a<00:01:14.760> bunch<00:01:14.939> of<00:01:15.119> feature 00:01:15.710 --> 00:01:15.720 align:start position:0% breaking releases a bunch of feature 00:01:15.720 --> 00:01:17.810 align:start position:0% breaking releases a bunch of feature releases<00:01:16.020> and<00:01:16.920> sometimes<00:01:17.220> we<00:01:17.400> do<00:01:17.520> have<00:01:17.700> like 00:01:17.810 --> 00:01:17.820 align:start position:0% releases and sometimes we do have like 00:01:17.820 --> 00:01:20.929 align:start position:0% releases and sometimes we do have like bug<00:01:18.000> fix<00:01:18.240> releases<00:01:18.720> as<00:01:18.960> well 00:01:20.929 --> 00:01:20.939 align:start position:0% bug fix releases as well 00:01:20.939 --> 00:01:22.850 align:start position:0% bug fix releases as well um<00:01:21.060> in<00:01:21.240> some<00:01:21.360> of<00:01:21.540> the<00:01:21.600> years<00:01:21.780> we<00:01:22.140> had<00:01:22.320> releases 00:01:22.850 --> 00:01:22.860 align:start position:0% um in some of the years we had releases 00:01:22.860 --> 00:01:24.710 align:start position:0% um in some of the years we had releases every<00:01:23.040> two<00:01:23.220> weeks<00:01:23.520> I<00:01:24.000> think<00:01:24.180> lately<00:01:24.420> it's<00:01:24.600> more 00:01:24.710 --> 00:01:24.720 align:start position:0% every two weeks I think lately it's more 00:01:24.720 --> 00:01:25.969 align:start position:0% every two weeks I think lately it's more like<00:01:24.900> monthly 00:01:25.969 --> 00:01:25.979 align:start position:0% like monthly 00:01:25.979 --> 00:01:27.289 align:start position:0% like monthly um<00:01:26.100> and<00:01:26.340> I<00:01:26.460> hope<00:01:26.580> that's<00:01:26.700> going<00:01:26.880> to<00:01:27.000> come<00:01:27.119> to 00:01:27.289 --> 00:01:27.299 align:start position:0% um and I hope that's going to come to 00:01:27.299 --> 00:01:29.530 align:start position:0% um and I hope that's going to come to you<00:01:27.420> maybe<00:01:28.140> you're<00:01:28.380> gonna<00:01:28.560> get<00:01:28.920> back<00:01:29.100> to<00:01:29.220> like 00:01:29.530 --> 00:01:29.540 align:start position:0% you maybe you're gonna get back to like 00:01:29.540 --> 00:01:31.670 align:start position:0% you maybe you're gonna get back to like bi-weekly<00:01:30.540> releases<00:01:30.840> but<00:01:31.080> at<00:01:31.200> least<00:01:31.320> want<00:01:31.560> to 00:01:31.670 --> 00:01:31.680 align:start position:0% bi-weekly releases but at least want to 00:01:31.680 --> 00:01:33.890 align:start position:0% bi-weekly releases but at least want to release<00:01:31.860> this<00:01:32.100> and<00:01:32.820> I'm<00:01:32.939> saying<00:01:33.119> this<00:01:33.360> just<00:01:33.659> to 00:01:33.890 --> 00:01:33.900 align:start position:0% release this and I'm saying this just to 00:01:33.900 --> 00:01:37.249 align:start position:0% release this and I'm saying this just to show<00:01:34.080> that<00:01:34.439> how<00:01:35.400> active<00:01:35.939> the<00:01:36.720> development<00:01:37.079> of 00:01:37.249 --> 00:01:37.259 align:start position:0% show that how active the development of 00:01:37.259 --> 00:01:40.010 align:start position:0% show that how active the development of solidity<00:01:37.680> is 00:01:40.010 --> 00:01:40.020 align:start position:0% 00:01:40.020 --> 00:01:42.350 align:start position:0% I'm<00:01:40.439> not<00:01:40.619> gonna<00:01:40.740> go<00:01:41.100> through<00:01:41.220> all<00:01:41.340> of<00:01:41.520> these 00:01:42.350 --> 00:01:42.360 align:start position:0% I'm not gonna go through all of these 00:01:42.360 --> 00:01:44.929 align:start position:0% I'm not gonna go through all of these um<00:01:42.420> you<00:01:42.780> can<00:01:42.840> find<00:01:43.280> this<00:01:44.280> really<00:01:44.460> nice<00:01:44.640> chart 00:01:44.929 --> 00:01:44.939 align:start position:0% um you can find this really nice chart 00:01:44.939 --> 00:01:48.109 align:start position:0% um you can find this really nice chart on<00:01:45.479> the<00:01:45.799> solidlank.org<00:01:46.799> website<00:01:47.159> and<00:01:48.000> it 00:01:48.109 --> 00:01:48.119 align:start position:0% on the solidlank.org website and it 00:01:48.119 --> 00:01:50.450 align:start position:0% on the solidlank.org website and it shows<00:01:48.479> you<00:01:48.600> all<00:01:49.320> the<00:01:49.500> interesting<00:01:49.920> milestones 00:01:50.450 --> 00:01:50.460 align:start position:0% shows you all the interesting milestones 00:01:50.460 --> 00:01:53.149 align:start position:0% shows you all the interesting milestones we<00:01:50.880> have<00:01:51.000> accomplished<00:01:51.420> since<00:01:51.600> the<00:01:51.780> beginning 00:01:53.149 --> 00:01:53.159 align:start position:0% we have accomplished since the beginning 00:01:53.159 --> 00:01:55.730 align:start position:0% we have accomplished since the beginning however<00:01:53.880> it<00:01:54.299> doesn't<00:01:54.479> show<00:01:55.140> anything<00:01:55.380> past 00:01:55.730 --> 00:01:55.740 align:start position:0% however it doesn't show anything past 00:01:55.740 --> 00:01:58.550 align:start position:0% however it doesn't show anything past 0.6<00:01:56.520> because<00:01:57.060> he<00:01:57.360> made<00:01:57.479> this<00:01:57.659> two<00:01:57.780> years<00:01:57.960> ago 00:01:58.550 --> 00:01:58.560 align:start position:0% 0.6 because he made this two years ago 00:01:58.560 --> 00:02:00.649 align:start position:0% 0.6 because he made this two years ago but<00:01:58.979> as<00:01:59.100> you<00:01:59.220> can<00:01:59.340> see<00:01:59.520> it's<00:01:59.759> it's<00:02:00.180> a<00:02:00.420> lot<00:02:00.540> of 00:02:00.649 --> 00:02:00.659 align:start position:0% but as you can see it's it's a lot of 00:02:00.659 --> 00:02:01.730 align:start position:0% but as you can see it's it's a lot of stuff<00:02:00.840> going<00:02:01.079> on 00:02:01.730 --> 00:02:01.740 align:start position:0% stuff going on 00:02:01.740 --> 00:02:03.350 align:start position:0% stuff going on and<00:02:02.100> based<00:02:02.399> on<00:02:02.399> like<00:02:02.579> having<00:02:02.759> over<00:02:03.119> 100 00:02:03.350 --> 00:02:03.360 align:start position:0% and based on like having over 100 00:02:03.360 --> 00:02:06.530 align:start position:0% and based on like having over 100 releases<00:02:04.200> you<00:02:04.920> may<00:02:04.979> ask<00:02:05.159> a<00:02:05.340> question<00:02:05.520> when<00:02:06.360> do 00:02:06.530 --> 00:02:06.540 align:start position:0% releases you may ask a question when do 00:02:06.540 --> 00:02:08.990 align:start position:0% releases you may ask a question when do we<00:02:06.600> actually<00:02:06.719> get<00:02:06.899> to<00:02:07.020> 1.0<00:02:07.979> and<00:02:08.459> you<00:02:08.759> may<00:02:08.880> not 00:02:08.990 --> 00:02:09.000 align:start position:0% we actually get to 1.0 and you may not 00:02:09.000 --> 00:02:10.910 align:start position:0% we actually get to 1.0 and you may not be<00:02:09.119> alone<00:02:09.239> asking<00:02:09.660> that<00:02:09.840> question<00:02:10.020> we<00:02:10.380> do<00:02:10.560> get 00:02:10.910 --> 00:02:10.920 align:start position:0% be alone asking that question we do get 00:02:10.920 --> 00:02:13.670 align:start position:0% be alone asking that question we do get that<00:02:11.099> question<00:02:11.340> super<00:02:11.760> frequently<00:02:12.500> last<00:02:13.500> year 00:02:13.670 --> 00:02:13.680 align:start position:0% that question super frequently last year 00:02:13.680 --> 00:02:15.470 align:start position:0% that question super frequently last year there<00:02:13.920> was<00:02:14.040> like<00:02:14.220> this<00:02:14.340> big<00:02:14.580> debate 00:02:15.470 --> 00:02:15.480 align:start position:0% there was like this big debate 00:02:15.480 --> 00:02:16.670 align:start position:0% there was like this big debate um<00:02:15.540> this<00:02:15.780> particular<00:02:16.080> issue<00:02:16.379> I'm<00:02:16.500> looking 00:02:16.670 --> 00:02:16.680 align:start position:0% um this particular issue I'm looking 00:02:16.680 --> 00:02:17.630 align:start position:0% um this particular issue I'm looking here 00:02:17.630 --> 00:02:17.640 align:start position:0% here 00:02:17.640 --> 00:02:19.369 align:start position:0% here the<00:02:17.940> issue<00:02:18.239> is<00:02:18.360> much<00:02:18.540> longer<00:02:18.840> the<00:02:19.080> description 00:02:19.369 --> 00:02:19.379 align:start position:0% the issue is much longer the description 00:02:19.379 --> 00:02:22.670 align:start position:0% the issue is much longer the description is<00:02:19.739> maybe<00:02:20.459> 10<00:02:20.700> times<00:02:20.940> as<00:02:21.120> long<00:02:21.360> and<00:02:22.200> the<00:02:22.379> author 00:02:22.670 --> 00:02:22.680 align:start position:0% is maybe 10 times as long and the author 00:02:22.680 --> 00:02:24.530 align:start position:0% is maybe 10 times as long and the author of<00:02:22.800> the<00:02:22.980> issue<00:02:23.280> provides<00:02:24.180> a<00:02:24.300> bunch<00:02:24.420> of 00:02:24.530 --> 00:02:24.540 align:start position:0% of the issue provides a bunch of 00:02:24.540 --> 00:02:26.690 align:start position:0% of the issue provides a bunch of different<00:02:24.720> reasons<00:02:25.200> why<00:02:25.379> he<00:02:25.620> thinks<00:02:25.980> solidity 00:02:26.690 --> 00:02:26.700 align:start position:0% different reasons why he thinks solidity 00:02:26.700 --> 00:02:29.750 align:start position:0% different reasons why he thinks solidity should<00:02:26.879> be<00:02:27.060> at<00:02:27.599> 1.0<00:02:28.560> I<00:02:28.980> summarize<00:02:29.340> like<00:02:29.580> three 00:02:29.750 --> 00:02:29.760 align:start position:0% should be at 1.0 I summarize like three 00:02:29.760 --> 00:02:31.369 align:start position:0% should be at 1.0 I summarize like three different<00:02:29.940> discussion<00:02:30.540> points<00:02:30.840> we<00:02:31.020> have<00:02:31.200> been 00:02:31.369 --> 00:02:31.379 align:start position:0% different discussion points we have been 00:02:31.379 --> 00:02:34.190 align:start position:0% different discussion points we have been debating<00:02:31.800> on<00:02:32.099> this<00:02:32.280> issue<00:02:32.599> the<00:02:33.599> others<00:02:33.959> that 00:02:34.190 --> 00:02:34.200 align:start position:0% debating on this issue the others that 00:02:34.200 --> 00:02:36.170 align:start position:0% debating on this issue the others that or<00:02:34.500> had<00:02:34.680> the<00:02:34.860> opinion<00:02:35.160> that<00:02:35.459> the<00:02:36.060> current 00:02:36.170 --> 00:02:36.180 align:start position:0% or had the opinion that the current 00:02:36.180 --> 00:02:38.210 align:start position:0% or had the opinion that the current scheme<00:02:36.599> doesn't<00:02:36.720> actually<00:02:37.020> allow<00:02:37.560> breaking 00:02:38.210 --> 00:02:38.220 align:start position:0% scheme doesn't actually allow breaking 00:02:38.220 --> 00:02:40.490 align:start position:0% scheme doesn't actually allow breaking releases<00:02:38.720> the<00:02:39.720> separation<00:02:40.020> of<00:02:40.200> breaking 00:02:40.490 --> 00:02:40.500 align:start position:0% releases the separation of breaking 00:02:40.500 --> 00:02:42.650 align:start position:0% releases the separation of breaking release<00:02:40.620> and<00:02:40.860> non-breaking<00:02:41.220> releases<00:02:41.700> in<00:02:42.420> his 00:02:42.650 --> 00:02:42.660 align:start position:0% release and non-breaking releases in his 00:02:42.660 --> 00:02:44.270 align:start position:0% release and non-breaking releases in his opinion<00:02:43.019> on<00:02:43.200> every<00:02:43.319> single<00:02:43.620> facility<00:02:43.920> release 00:02:44.270 --> 00:02:44.280 align:start position:0% opinion on every single facility release 00:02:44.280 --> 00:02:46.610 align:start position:0% opinion on every single facility release is<00:02:44.640> a<00:02:44.760> breaking<00:02:45.060> release 00:02:46.610 --> 00:02:46.620 align:start position:0% is a breaking release 00:02:46.620 --> 00:02:49.250 align:start position:0% is a breaking release he<00:02:47.340> also<00:02:47.580> argued<00:02:47.819> that<00:02:48.000> the<00:02:48.180> languages 00:02:49.250 --> 00:02:49.260 align:start position:0% he also argued that the languages 00:02:49.260 --> 00:02:51.830 align:start position:0% he also argued that the languages widely<00:02:49.920> used<00:02:50.099> it<00:02:51.000> is 00:02:51.830 --> 00:02:51.840 align:start position:0% widely used it is 00:02:51.840 --> 00:02:54.290 align:start position:0% widely used it is it<00:02:52.200> has<00:02:52.319> been<00:02:52.500> for<00:02:52.800> a<00:02:52.920> couple<00:02:53.040> of<00:02:53.160> years<00:02:53.400> and<00:02:54.180> so 00:02:54.290 --> 00:02:54.300 align:start position:0% it has been for a couple of years and so 00:02:54.300 --> 00:02:57.110 align:start position:0% it has been for a couple of years and so it<00:02:54.540> should<00:02:54.720> should<00:02:55.140> be<00:02:55.500> a<00:02:55.800> 1.0<00:02:56.340> because<00:02:56.819> that 00:02:57.110 --> 00:02:57.120 align:start position:0% it should should be a 1.0 because that 00:02:57.120 --> 00:03:00.229 align:start position:0% it should should be a 1.0 because that signals<00:02:57.660> that<00:02:57.840> it<00:02:58.019> is<00:02:58.200> ready<00:02:58.319> to<00:02:58.560> be<00:02:58.680> used 00:03:00.229 --> 00:03:00.239 align:start position:0% signals that it is ready to be used 00:03:00.239 --> 00:03:01.670 align:start position:0% signals that it is ready to be used um in<00:03:00.840> fact 00:03:01.670 --> 00:03:01.680 align:start position:0% um in fact 00:03:01.680 --> 00:03:04.070 align:start position:0% um in fact you<00:03:02.099> know<00:03:02.220> when<00:03:02.280> 1.0<00:03:02.760> was<00:03:03.000> released<00:03:03.360> we<00:03:03.900> never 00:03:04.070 --> 00:03:04.080 align:start position:0% you know when 1.0 was released we never 00:03:04.080 --> 00:03:06.229 align:start position:0% you know when 1.0 was released we never signaled<00:03:04.620> a<00:03:04.800> 0.1<00:03:05.400> was<00:03:05.700> released<00:03:06.000> we<00:03:06.120> never 00:03:06.229 --> 00:03:06.239 align:start position:0% signaled a 0.1 was released we never 00:03:06.239 --> 00:03:08.210 align:start position:0% signaled a 0.1 was released we never signaled<00:03:06.720> that<00:03:06.780> it's<00:03:06.959> ready<00:03:07.379> for<00:03:07.500> usage<00:03:07.920> but 00:03:08.210 --> 00:03:08.220 align:start position:0% signaled that it's ready for usage but 00:03:08.220 --> 00:03:11.030 align:start position:0% signaled that it's ready for usage but the<00:03:08.760> nature<00:03:09.000> of<00:03:09.060> blockchain<00:03:09.480> it<00:03:10.200> just<00:03:10.440> started 00:03:11.030 --> 00:03:11.040 align:start position:0% the nature of blockchain it just started 00:03:11.040 --> 00:03:12.589 align:start position:0% the nature of blockchain it just started it<00:03:11.280> people<00:03:11.519> just<00:03:11.700> started<00:03:11.940> to<00:03:12.060> use<00:03:12.180> it<00:03:12.360> and 00:03:12.589 --> 00:03:12.599 align:start position:0% it people just started to use it and 00:03:12.599 --> 00:03:15.830 align:start position:0% it people just started to use it and it's<00:03:13.200> there<00:03:13.379> it's<00:03:13.800> always<00:03:13.980> going<00:03:14.220> to<00:03:14.280> be<00:03:14.400> there 00:03:15.830 --> 00:03:15.840 align:start position:0% it's there it's always going to be there 00:03:15.840 --> 00:03:18.110 align:start position:0% it's there it's always going to be there um<00:03:16.379> but<00:03:16.800> also<00:03:16.980> the<00:03:17.159> team<00:03:17.340> had<00:03:17.580> some<00:03:17.760> concerns 00:03:18.110 --> 00:03:18.120 align:start position:0% um but also the team had some concerns 00:03:18.120 --> 00:03:20.750 align:start position:0% um but also the team had some concerns about<00:03:18.300> this<00:03:18.540> 1.0<00:03:19.019> stuff<00:03:19.280> basically<00:03:20.280> we<00:03:20.580> have 00:03:20.750 --> 00:03:20.760 align:start position:0% about this 1.0 stuff basically we have 00:03:20.760 --> 00:03:22.970 align:start position:0% about this 1.0 stuff basically we have the<00:03:20.940> impression<00:03:21.300> that<00:03:21.480> 1.0<00:03:21.959> kinda<00:03:22.680> implies 00:03:22.970 --> 00:03:22.980 align:start position:0% the impression that 1.0 kinda implies 00:03:22.980 --> 00:03:24.830 align:start position:0% the impression that 1.0 kinda implies that<00:03:23.159> we<00:03:23.340> have<00:03:23.519> to<00:03:23.819> have<00:03:24.239> a<00:03:24.360> long-term 00:03:24.830 --> 00:03:24.840 align:start position:0% that we have to have a long-term 00:03:24.840 --> 00:03:27.649 align:start position:0% that we have to have a long-term maintenance<00:03:25.459> of<00:03:26.459> that<00:03:26.700> version<00:03:26.879> we<00:03:27.239> have<00:03:27.480> to 00:03:27.649 --> 00:03:27.659 align:start position:0% maintenance of that version we have to 00:03:27.659 --> 00:03:30.710 align:start position:0% maintenance of that version we have to add<00:03:28.200> new<00:03:28.379> features<00:03:28.739> non-breaking<00:03:29.400> features 00:03:30.710 --> 00:03:30.720 align:start position:0% add new features non-breaking features 00:03:30.720 --> 00:03:33.170 align:start position:0% add new features non-breaking features um<00:03:30.840> and<00:03:31.080> all<00:03:31.260> kind<00:03:31.379> of<00:03:31.500> changes<00:03:31.860> and<00:03:32.819> if<00:03:33.000> we 00:03:33.170 --> 00:03:33.180 align:start position:0% um and all kind of changes and if we 00:03:33.180 --> 00:03:34.970 align:start position:0% um and all kind of changes and if we still<00:03:33.599> want<00:03:33.780> to<00:03:33.900> do<00:03:33.959> braking<00:03:34.260> changes<00:03:34.800> that's 00:03:34.970 --> 00:03:34.980 align:start position:0% still want to do braking changes that's 00:03:34.980 --> 00:03:36.710 align:start position:0% still want to do braking changes that's going<00:03:35.220> to<00:03:35.280> be<00:03:35.340> like<00:03:35.459> 2.0 00:03:36.710 --> 00:03:36.720 align:start position:0% going to be like 2.0 00:03:36.720 --> 00:03:38.270 align:start position:0% going to be like 2.0 and<00:03:37.319> then<00:03:37.440> suddenly<00:03:37.739> we<00:03:37.920> have<00:03:38.040> to<00:03:38.159> like 00:03:38.270 --> 00:03:38.280 align:start position:0% and then suddenly we have to like 00:03:38.280 --> 00:03:41.149 align:start position:0% and then suddenly we have to like maintain<00:03:38.640> two<00:03:38.819> versions<00:03:39.440> or<00:03:40.440> we're<00:03:40.860> not<00:03:40.980> gonna 00:03:41.149 --> 00:03:41.159 align:start position:0% maintain two versions or we're not gonna 00:03:41.159 --> 00:03:43.130 align:start position:0% maintain two versions or we're not gonna make<00:03:41.340> breaking<00:03:41.640> releases<00:03:42.000> so<00:03:42.720> that<00:03:42.840> that<00:03:43.019> is 00:03:43.130 --> 00:03:43.140 align:start position:0% make breaking releases so that that is 00:03:43.140 --> 00:03:44.690 align:start position:0% make breaking releases so that that is the<00:03:43.260> reason<00:03:43.379> we<00:03:43.680> kind<00:03:43.860> of<00:03:43.980> wanted<00:03:44.099> to<00:03:44.340> avoid 00:03:44.690 --> 00:03:44.700 align:start position:0% the reason we kind of wanted to avoid 00:03:44.700 --> 00:03:48.229 align:start position:0% the reason we kind of wanted to avoid going<00:03:45.239> to<00:03:45.420> 1.0 00:03:48.229 --> 00:03:48.239 align:start position:0% 00:03:48.239 --> 00:03:49.809 align:start position:0% I'm<00:03:48.599> not<00:03:48.720> sure<00:03:48.900> how<00:03:49.080> many<00:03:49.200> of<00:03:49.379> you<00:03:49.500> actually 00:03:49.809 --> 00:03:49.819 align:start position:0% I'm not sure how many of you actually 00:03:49.819 --> 00:03:52.670 align:start position:0% I'm not sure how many of you actually know<00:03:50.819> how<00:03:51.000> the<00:03:51.120> versioning<00:03:51.540> system<00:03:51.720> works 00:03:52.670 --> 00:03:52.680 align:start position:0% know how the versioning system works 00:03:52.680 --> 00:03:56.570 align:start position:0% know how the versioning system works um do<00:03:52.920> you<00:03:53.040> want<00:03:53.099> to<00:03:53.280> like<00:03:53.580> give<00:03:54.060> hands<00:03:54.920> on<00:03:55.920> are 00:03:56.570 --> 00:03:56.580 align:start position:0% um do you want to like give hands on are 00:03:56.580 --> 00:03:58.369 align:start position:0% um do you want to like give hands on are you<00:03:56.760> a<00:03:56.940> developer<00:03:57.239> first<00:03:57.480> of<00:03:57.659> all 00:03:58.369 --> 00:03:58.379 align:start position:0% you a developer first of all 00:03:58.379 --> 00:04:01.009 align:start position:0% you a developer first of all so<00:03:58.620> many<00:03:58.860> of<00:03:58.980> you<00:03:59.099> are<00:03:59.340> using<00:03:59.640> solidity<00:04:00.599> are 00:04:01.009 --> 00:04:01.019 align:start position:0% so many of you are using solidity are 00:04:01.019 --> 00:04:04.190 align:start position:0% so many of you are using solidity are you<00:04:01.140> using<00:04:01.319> anything<00:04:01.500> but<00:04:01.920> solidity<00:04:02.459> not<00:04:03.120> many 00:04:04.190 --> 00:04:04.200 align:start position:0% you using anything but solidity not many 00:04:04.200 --> 00:04:08.509 align:start position:0% you using anything but solidity not many any<00:04:04.680> other<00:04:04.920> language<00:04:05.220> besides<00:04:06.060> solidity<00:04:06.540> nice 00:04:08.509 --> 00:04:08.519 align:start position:0% any other language besides solidity nice 00:04:08.519 --> 00:04:10.190 align:start position:0% any other language besides solidity nice so<00:04:08.940> I<00:04:09.060> think<00:04:09.239> you<00:04:09.299> should<00:04:09.599> you<00:04:09.780> ever<00:04:09.900> had<00:04:10.080> this 00:04:10.190 --> 00:04:10.200 align:start position:0% so I think you should you ever had this 00:04:10.200 --> 00:04:11.990 align:start position:0% so I think you should you ever had this versioning<00:04:10.620> system<00:04:10.739> works 00:04:11.990 --> 00:04:12.000 align:start position:0% versioning system works 00:04:12.000 --> 00:04:13.610 align:start position:0% versioning system works um<00:04:12.060> we've<00:04:12.540> learned<00:04:12.780> the<00:04:12.900> impression<00:04:13.260> that<00:04:13.439> it 00:04:13.610 --> 00:04:13.620 align:start position:0% um we've learned the impression that it 00:04:13.620 --> 00:04:15.649 align:start position:0% um we've learned the impression that it is<00:04:13.739> semantic<00:04:14.220> versioning<00:04:14.640> turned<00:04:15.239> out<00:04:15.299> it<00:04:15.480> is 00:04:15.649 --> 00:04:15.659 align:start position:0% is semantic versioning turned out it is 00:04:15.659 --> 00:04:17.030 align:start position:0% is semantic versioning turned out it is not 00:04:17.030 --> 00:04:17.040 align:start position:0% not 00:04:17.040 --> 00:04:19.550 align:start position:0% not um<00:04:17.160> because<00:04:17.639> anything<00:04:18.479> below 00:04:19.550 --> 00:04:19.560 align:start position:0% um because anything below 00:04:19.560 --> 00:04:23.150 align:start position:0% um because anything below um<00:04:20.100> the<00:04:20.519> major<00:04:20.699> one<00:04:21.120> so<00:04:21.600> major<00:04:21.900> zero<00:04:22.440> is<00:04:22.979> a 00:04:23.150 --> 00:04:23.160 align:start position:0% um the major one so major zero is a 00:04:23.160 --> 00:04:26.150 align:start position:0% um the major one so major zero is a breaking<00:04:23.460> change<00:04:23.699> however<00:04:24.540> we<00:04:25.080> did<00:04:25.380> assume 00:04:26.150 --> 00:04:26.160 align:start position:0% breaking change however we did assume 00:04:26.160 --> 00:04:27.110 align:start position:0% breaking change however we did assume that 00:04:27.110 --> 00:04:27.120 align:start position:0% that 00:04:27.120 --> 00:04:28.969 align:start position:0% that um you<00:04:27.300> know<00:04:27.360> the<00:04:27.600> three<00:04:27.780> three<00:04:28.199> numbers<00:04:28.740> in 00:04:28.969 --> 00:04:28.979 align:start position:0% um you know the three three numbers in 00:04:28.979 --> 00:04:31.249 align:start position:0% um you know the three three numbers in the<00:04:29.160> version<00:04:29.280> is<00:04:29.520> major<00:04:29.699> minor<00:04:30.180> patch<00:04:30.600> and<00:04:31.139> we 00:04:31.249 --> 00:04:31.259 align:start position:0% the version is major minor patch and we 00:04:31.259 --> 00:04:33.170 align:start position:0% the version is major minor patch and we assume<00:04:31.620> that<00:04:31.680> if<00:04:31.919> we<00:04:32.040> bump<00:04:32.280> the<00:04:32.520> the<00:04:32.699> minor 00:04:33.170 --> 00:04:33.180 align:start position:0% assume that if we bump the the minor 00:04:33.180 --> 00:04:35.570 align:start position:0% assume that if we bump the the minor that<00:04:33.720> is<00:04:33.840> a<00:04:33.960> breaking<00:04:34.199> release<00:04:34.380> if<00:04:35.100> we<00:04:35.280> bump 00:04:35.570 --> 00:04:35.580 align:start position:0% that is a breaking release if we bump 00:04:35.580 --> 00:04:37.070 align:start position:0% that is a breaking release if we bump the<00:04:35.820> patch<00:04:36.120> that<00:04:36.240> is<00:04:36.419> a<00:04:36.479> non-breaking<00:04:36.840> release 00:04:37.070 --> 00:04:37.080 align:start position:0% the patch that is a non-breaking release 00:04:37.080 --> 00:04:39.830 align:start position:0% the patch that is a non-breaking release so<00:04:37.740> it's<00:04:37.860> not<00:04:38.100> actually<00:04:38.340> in<00:04:39.120> conformance<00:04:39.600> with 00:04:39.830 --> 00:04:39.840 align:start position:0% so it's not actually in conformance with 00:04:39.840 --> 00:04:42.050 align:start position:0% so it's not actually in conformance with semantic<00:04:40.560> versioning<00:04:41.040> but<00:04:41.460> it<00:04:41.580> kind<00:04:41.699> of<00:04:41.820> works 00:04:42.050 --> 00:04:42.060 align:start position:0% semantic versioning but it kind of works 00:04:42.060 --> 00:04:44.510 align:start position:0% semantic versioning but it kind of works for<00:04:42.180> us 00:04:44.510 --> 00:04:44.520 align:start position:0% 00:04:44.520 --> 00:04:46.070 align:start position:0% um here's<00:04:44.940> just<00:04:45.000> an<00:04:45.120> example<00:04:45.360> you<00:04:45.600> know<00:04:45.780> how 00:04:46.070 --> 00:04:46.080 align:start position:0% um here's just an example you know how 00:04:46.080 --> 00:04:48.830 align:start position:0% um here's just an example you know how this<00:04:46.380> would<00:04:46.560> look<00:04:46.680> like<00:04:46.860> and<00:04:47.759> now<00:04:47.940> suddenly 00:04:48.830 --> 00:04:48.840 align:start position:0% this would look like and now suddenly 00:04:48.840 --> 00:04:50.629 align:start position:0% this would look like and now suddenly you<00:04:49.259> know<00:04:49.380> once<00:04:49.560> we<00:04:49.680> know<00:04:49.800> what<00:04:49.919> 1.0<00:04:50.400> could 00:04:50.629 --> 00:04:50.639 align:start position:0% you know once we know what 1.0 could 00:04:50.639 --> 00:04:53.330 align:start position:0% you know once we know what 1.0 could mean<00:04:50.840> maybe<00:04:51.840> we<00:04:52.020> should<00:04:52.199> talk<00:04:52.560> about<00:04:52.740> how 00:04:53.330 --> 00:04:53.340 align:start position:0% mean maybe we should talk about how 00:04:53.340 --> 00:04:55.310 align:start position:0% mean maybe we should talk about how could<00:04:53.520> we<00:04:53.699> get<00:04:53.820> there<00:04:54.479> here's<00:04:54.960> an<00:04:55.020> example 00:04:55.310 --> 00:04:55.320 align:start position:0% could we get there here's an example 00:04:55.320 --> 00:04:56.450 align:start position:0% could we get there here's an example contract 00:04:56.450 --> 00:04:56.460 align:start position:0% contract 00:04:56.460 --> 00:04:58.610 align:start position:0% contract um<00:04:56.520> with<00:04:57.060> the<00:04:57.180> latest<00:04:57.300> release<00:04:57.600> this<00:04:58.380> is 00:04:58.610 --> 00:04:58.620 align:start position:0% um with the latest release this is 00:04:58.620 --> 00:05:00.950 align:start position:0% um with the latest release this is actually<00:04:58.680> the<00:04:59.580> solidity<00:05:00.180> stocks<00:05:00.660> contract 00:05:00.950 --> 00:05:00.960 align:start position:0% actually the solidity stocks contract 00:05:00.960 --> 00:05:03.230 align:start position:0% actually the solidity stocks contract which<00:05:01.320> is<00:05:01.500> on<00:05:01.620> mainnet<00:05:02.160> you<00:05:02.699> can<00:05:02.759> use<00:05:02.940> it<00:05:03.060> to 00:05:03.230 --> 00:05:03.240 align:start position:0% which is on mainnet you can use it to 00:05:03.240 --> 00:05:05.270 align:start position:0% which is on mainnet you can use it to make<00:05:03.360> socks<00:05:03.840> both<00:05:04.500> the<00:05:04.680> land<00:05:04.860> and<00:05:05.040> the<00:05:05.160> right 00:05:05.270 --> 00:05:05.280 align:start position:0% make socks both the land and the right 00:05:05.280 --> 00:05:07.129 align:start position:0% make socks both the land and the right hand<00:05:05.460> side<00:05:05.639> if<00:05:06.000> you're<00:05:06.120> lucky<00:05:06.240> you<00:05:06.540> can<00:05:06.720> you 00:05:07.129 --> 00:05:07.139 align:start position:0% hand side if you're lucky you can you 00:05:07.139 --> 00:05:10.310 align:start position:0% hand side if you're lucky you can you can<00:05:07.259> win<00:05:07.440> both<00:05:08.160> and<00:05:08.940> uh<00:05:09.180> I<00:05:09.780> think<00:05:09.840> the<00:05:09.960> stocks 00:05:10.310 --> 00:05:10.320 align:start position:0% can win both and uh I think the stocks 00:05:10.320 --> 00:05:11.749 align:start position:0% can win both and uh I think the stocks are<00:05:10.380> gone<00:05:10.560> at<00:05:10.740> this<00:05:10.860> point<00:05:11.040> but<00:05:11.460> you<00:05:11.639> could 00:05:11.749 --> 00:05:11.759 align:start position:0% are gone at this point but you could 00:05:11.759 --> 00:05:13.249 align:start position:0% are gone at this point but you could have<00:05:11.880> gotten<00:05:12.180> them<00:05:12.360> a<00:05:12.540> physical<00:05:12.720> version<00:05:13.020> of 00:05:13.249 --> 00:05:13.259 align:start position:0% have gotten them a physical version of 00:05:13.259 --> 00:05:15.650 align:start position:0% have gotten them a physical version of the<00:05:13.380> stock<00:05:13.500> at<00:05:14.040> the<00:05:14.220> solidity<00:05:14.639> stand 00:05:15.650 --> 00:05:15.660 align:start position:0% the stock at the solidity stand 00:05:15.660 --> 00:05:18.530 align:start position:0% the stock at the solidity stand um<00:05:16.139> I<00:05:16.680> think<00:05:16.860> on<00:05:17.100> the<00:05:17.340> floor<00:05:17.699> above<00:05:18.120> I'm<00:05:18.419> not 00:05:18.530 --> 00:05:18.540 align:start position:0% um I think on the floor above I'm not 00:05:18.540 --> 00:05:19.850 align:start position:0% um I think on the floor above I'm not sure 00:05:19.850 --> 00:05:19.860 align:start position:0% sure 00:05:19.860 --> 00:05:22.909 align:start position:0% sure now<00:05:20.400> this<00:05:20.699> is<00:05:20.820> 0<00:05:21.060> 8<00:05:21.300> 17. 00:05:22.909 --> 00:05:22.919 align:start position:0% now this is 0 8 17. 00:05:22.919 --> 00:05:24.650 align:start position:0% now this is 0 8 17. it<00:05:23.220> is<00:05:23.340> 1.0 00:05:24.650 --> 00:05:24.660 align:start position:0% it is 1.0 00:05:24.660 --> 00:05:26.090 align:start position:0% it is 1.0 do<00:05:24.960> you<00:05:25.080> see<00:05:25.199> any<00:05:25.320> change 00:05:26.090 --> 00:05:26.100 align:start position:0% do you see any change 00:05:26.100 --> 00:05:28.550 align:start position:0% do you see any change yeah<00:05:26.639> I<00:05:27.360> kind<00:05:27.479> of<00:05:27.600> think<00:05:27.720> that<00:05:27.900> actually<00:05:28.139> for 00:05:28.550 --> 00:05:28.560 align:start position:0% yeah I kind of think that actually for 00:05:28.560 --> 00:05:30.230 align:start position:0% yeah I kind of think that actually for the<00:05:28.680> users<00:05:28.979> you're<00:05:29.580> not<00:05:29.759> going<00:05:29.880> to<00:05:30.000> see<00:05:30.060> too 00:05:30.230 --> 00:05:30.240 align:start position:0% the users you're not going to see too 00:05:30.240 --> 00:05:33.050 align:start position:0% the users you're not going to see too many<00:05:30.419> changes<00:05:30.840> at<00:05:31.320> 1.0 00:05:33.050 --> 00:05:33.060 align:start position:0% many changes at 1.0 00:05:33.060 --> 00:05:35.930 align:start position:0% many changes at 1.0 we<00:05:33.360> may<00:05:33.539> actually<00:05:33.660> have<00:05:33.960> some<00:05:34.139> changes 00:05:35.930 --> 00:05:35.940 align:start position:0% we may actually have some changes 00:05:35.940 --> 00:05:38.210 align:start position:0% we may actually have some changes okay<00:05:36.419> so<00:05:36.900> that<00:05:37.080> was<00:05:37.259> the<00:05:37.440> the<00:05:37.620> non-changed 00:05:38.210 --> 00:05:38.220 align:start position:0% okay so that was the the non-changed 00:05:38.220 --> 00:05:40.610 align:start position:0% okay so that was the the non-changed version 00:05:40.610 --> 00:05:40.620 align:start position:0% 00:05:40.620 --> 00:05:42.050 align:start position:0% skipping<00:05:41.160> one 00:05:42.050 --> 00:05:42.060 align:start position:0% skipping one 00:05:42.060 --> 00:05:44.090 align:start position:0% skipping one okay<00:05:42.419> this<00:05:42.600> is<00:05:42.720> an<00:05:42.780> unchanged<00:05:43.199> version 00:05:44.090 --> 00:05:44.100 align:start position:0% okay this is an unchanged version 00:05:44.100 --> 00:05:46.670 align:start position:0% okay this is an unchanged version and<00:05:44.400> this<00:05:44.580> has<00:05:44.820> a<00:05:45.060> few<00:05:45.120> changes 00:05:46.670 --> 00:05:46.680 align:start position:0% and this has a few changes 00:05:46.680 --> 00:05:49.310 align:start position:0% and this has a few changes they're<00:05:47.100> not<00:05:47.280> important 00:05:49.310 --> 00:05:49.320 align:start position:0% they're not important 00:05:49.320 --> 00:05:52.969 align:start position:0% they're not important yeah<00:05:50.520> um<00:05:50.580> where<00:05:50.940> is<00:05:51.120> it<00:05:51.240> like<00:05:51.780> this<00:05:51.960> stuff 00:05:52.969 --> 00:05:52.979 align:start position:0% yeah um where is it like this stuff 00:05:52.979 --> 00:05:55.969 align:start position:0% yeah um where is it like this stuff this<00:05:53.639> stuff<00:05:53.820> all<00:05:54.780> of<00:05:54.960> none<00:05:55.199> of<00:05:55.320> this<00:05:55.440> is<00:05:55.560> agreed 00:05:55.969 --> 00:05:55.979 align:start position:0% this stuff all of none of this is agreed 00:05:55.979 --> 00:05:56.810 align:start position:0% this stuff all of none of this is agreed on 00:05:56.810 --> 00:05:56.820 align:start position:0% on 00:05:56.820 --> 00:05:58.430 align:start position:0% on but<00:05:57.240> there<00:05:57.360> may<00:05:57.479> be<00:05:57.600> tiny<00:05:57.960> changes<00:05:58.199> but<00:05:58.320> I 00:05:58.430 --> 00:05:58.440 align:start position:0% but there may be tiny changes but I 00:05:58.440 --> 00:05:59.150 align:start position:0% but there may be tiny changes but I don't<00:05:58.500> think<00:05:58.680> they're<00:05:58.740> going<00:05:58.860> to<00:05:58.919> be<00:05:58.979> big 00:05:59.150 --> 00:05:59.160 align:start position:0% don't think they're going to be big 00:05:59.160 --> 00:06:00.650 align:start position:0% don't think they're going to be big changes 00:06:00.650 --> 00:06:00.660 align:start position:0% changes 00:06:00.660 --> 00:06:02.390 align:start position:0% changes um<00:06:00.780> so<00:06:01.080> no<00:06:01.259> major<00:06:01.440> difference<00:06:01.680> is<00:06:01.919> if<00:06:02.100> you're<00:06:02.280> a 00:06:02.390 --> 00:06:02.400 align:start position:0% um so no major difference is if you're a 00:06:02.400 --> 00:06:04.730 align:start position:0% um so no major difference is if you're a user<00:06:02.639> but<00:06:03.180> giant<00:06:03.539> difference<00:06:03.780> is<00:06:04.080> if<00:06:04.440> you<00:06:04.560> are 00:06:04.730 --> 00:06:04.740 align:start position:0% user but giant difference is if you are 00:06:04.740 --> 00:06:06.950 align:start position:0% user but giant difference is if you are writing<00:06:04.979> a<00:06:05.100> library 00:06:06.950 --> 00:06:06.960 align:start position:0% writing a library 00:06:06.960 --> 00:06:09.469 align:start position:0% writing a library um<00:06:07.020> I<00:06:07.199> listed<00:06:07.560> a<00:06:07.740> few<00:06:07.800> things<00:06:08.160> on<00:06:08.759> what<00:06:09.240> you 00:06:09.469 --> 00:06:09.479 align:start position:0% um I listed a few things on what you 00:06:09.479 --> 00:06:11.990 align:start position:0% um I listed a few things on what you would<00:06:09.600> be<00:06:09.720> able<00:06:09.900> to<00:06:10.020> expect<00:06:10.199> in<00:06:10.500> libraries 00:06:11.990 --> 00:06:12.000 align:start position:0% would be able to expect in libraries 00:06:12.000 --> 00:06:14.870 align:start position:0% would be able to expect in libraries we<00:06:12.900> should<00:06:13.020> have<00:06:13.199> like<00:06:13.380> operator<00:06:13.880> operators 00:06:14.870 --> 00:06:14.880 align:start position:0% we should have like operator operators 00:06:14.880 --> 00:06:16.490 align:start position:0% we should have like operator operators and<00:06:15.060> letters<00:06:15.419> to<00:06:15.539> use<00:06:15.720> the<00:06:15.840> defined<00:06:16.199> types 00:06:16.490 --> 00:06:16.500 align:start position:0% and letters to use the defined types 00:06:16.500 --> 00:06:18.590 align:start position:0% and letters to use the defined types standard<00:06:17.100> Library<00:06:17.220> generics 00:06:18.590 --> 00:06:18.600 align:start position:0% standard Library generics 00:06:18.600 --> 00:06:20.570 align:start position:0% standard Library generics um you<00:06:18.780> know<00:06:18.900> data<00:06:19.199> types<00:06:19.500> I<00:06:19.860> just<00:06:20.039> gave<00:06:20.220> you<00:06:20.400> a 00:06:20.570 --> 00:06:20.580 align:start position:0% um you know data types I just gave you a 00:06:20.580 --> 00:06:23.270 align:start position:0% um you know data types I just gave you a few<00:06:20.699> examples<00:06:21.060> now<00:06:21.360> but<00:06:22.259> actually 00:06:23.270 --> 00:06:23.280 align:start position:0% few examples now but actually 00:06:23.280 --> 00:06:25.370 align:start position:0% few examples now but actually Daniel<00:06:23.759> from<00:06:24.180> this<00:06:24.240> already<00:06:24.479> team<00:06:24.840> had<00:06:25.199> an 00:06:25.370 --> 00:06:25.380 align:start position:0% Daniel from this already team had an 00:06:25.380 --> 00:06:26.689 align:start position:0% Daniel from this already team had an extremely<00:06:25.740> good<00:06:25.919> talk<00:06:26.100> which<00:06:26.400> you<00:06:26.520> should 00:06:26.689 --> 00:06:26.699 align:start position:0% extremely good talk which you should 00:06:26.699 --> 00:06:28.550 align:start position:0% extremely good talk which you should watch<00:06:26.880> and<00:06:27.360> I'm<00:06:27.479> going<00:06:27.660> to<00:06:27.720> share<00:06:27.840> the<00:06:28.020> QR<00:06:28.440> code 00:06:28.550 --> 00:06:28.560 align:start position:0% watch and I'm going to share the QR code 00:06:28.560 --> 00:06:31.070 align:start position:0% watch and I'm going to share the QR code for<00:06:28.800> the<00:06:28.860> video<00:06:28.979> as<00:06:29.160> well<00:06:29.819> so<00:06:30.660> here's<00:06:30.960> an 00:06:31.070 --> 00:06:31.080 align:start position:0% for the video as well so here's an 00:06:31.080 --> 00:06:33.890 align:start position:0% for the video as well so here's an example<00:06:31.319> of<00:06:31.560> user<00:06:32.280> defined<00:06:32.639> operators 00:06:33.890 --> 00:06:33.900 align:start position:0% example of user defined operators 00:06:33.900 --> 00:06:35.390 align:start position:0% example of user defined operators I<00:06:34.319> cannot<00:06:34.500> see<00:06:34.680> that<00:06:34.800> I<00:06:34.979> actually<00:06:35.100> like<00:06:35.220> the 00:06:35.390 --> 00:06:35.400 align:start position:0% I cannot see that I actually like the 00:06:35.400 --> 00:06:36.650 align:start position:0% I cannot see that I actually like the syntax<00:06:35.759> but 00:06:36.650 --> 00:06:36.660 align:start position:0% syntax but 00:06:36.660 --> 00:06:39.050 align:start position:0% syntax but the<00:06:36.960> team<00:06:37.080> kind<00:06:37.259> of<00:06:37.380> agreed<00:06:37.680> on<00:06:37.800> it<00:06:37.919> so<00:06:38.759> without 00:06:39.050 --> 00:06:39.060 align:start position:0% the team kind of agreed on it so without 00:06:39.060 --> 00:06:42.290 align:start position:0% the team kind of agreed on it so without tests<00:06:39.720> you<00:06:39.960> have<00:06:40.139> to<00:06:40.319> use<00:06:40.560> the<00:06:40.979> usual<00:06:41.340> function 00:06:42.290 --> 00:06:42.300 align:start position:0% tests you have to use the usual function 00:06:42.300 --> 00:06:45.469 align:start position:0% tests you have to use the usual function chaining<00:06:43.139> but<00:06:43.560> once<00:06:43.919> you<00:06:44.039> have<00:06:44.479> user-defined 00:06:45.469 --> 00:06:45.479 align:start position:0% chaining but once you have user-defined 00:06:45.479 --> 00:06:47.689 align:start position:0% chaining but once you have user-defined operators 00:06:47.689 --> 00:06:47.699 align:start position:0% operators 00:06:47.699 --> 00:06:49.189 align:start position:0% operators you<00:06:48.060> know<00:06:48.120> what<00:06:48.240> you<00:06:48.419> can<00:06:48.539> expect<00:06:48.660> you<00:06:49.080> can 00:06:49.189 --> 00:06:49.199 align:start position:0% you know what you can expect you can 00:06:49.199 --> 00:06:52.189 align:start position:0% you know what you can expect you can just<00:06:49.319> use<00:06:49.500> them<00:06:49.800> fairly<00:06:50.639> easily 00:06:52.189 --> 00:06:52.199 align:start position:0% just use them fairly easily 00:06:52.199 --> 00:06:53.689 align:start position:0% just use them fairly easily so<00:06:52.560> I<00:06:52.680> think<00:06:52.800> the<00:06:52.919> team<00:06:53.039> kind<00:06:53.220> of<00:06:53.340> agreed<00:06:53.580> that 00:06:53.689 --> 00:06:53.699 align:start position:0% so I think the team kind of agreed that 00:06:53.699 --> 00:06:55.490 align:start position:0% so I think the team kind of agreed that this<00:06:53.819> is<00:06:54.000> going<00:06:54.120> to<00:06:54.180> be<00:06:54.300> in<00:06:54.539> uh<00:06:55.020> this<00:06:55.319> is<00:06:55.440> going 00:06:55.490 --> 00:06:55.500 align:start position:0% this is going to be in uh this is going 00:06:55.500 --> 00:06:57.830 align:start position:0% this is going to be in uh this is going to<00:06:55.560> be<00:06:55.620> a<00:06:55.740> focused<00:06:56.160> project<00:06:56.580> and 00:06:57.830 --> 00:06:57.840 align:start position:0% to be a focused project and 00:06:57.840 --> 00:07:01.490 align:start position:0% to be a focused project and I<00:06:58.380> believe<00:06:58.560> this<00:06:58.800> is<00:06:58.979> needed<00:06:59.280> for<00:06:59.400> like<00:06:59.520> 1.0 00:07:01.490 --> 00:07:01.500 align:start position:0% I believe this is needed for like 1.0 00:07:01.500 --> 00:07:03.230 align:start position:0% I believe this is needed for like 1.0 another<00:07:01.979> major<00:07:02.400> thing<00:07:02.639> is<00:07:02.819> a<00:07:02.940> standard 00:07:03.230 --> 00:07:03.240 align:start position:0% another major thing is a standard 00:07:03.240 --> 00:07:04.189 align:start position:0% another major thing is a standard Library<00:07:03.360> which 00:07:04.189 --> 00:07:04.199 align:start position:0% Library which 00:07:04.199 --> 00:07:07.070 align:start position:0% Library which we<00:07:04.620> have<00:07:04.800> been<00:07:04.919> talking<00:07:05.100> about<00:07:05.520> for<00:07:05.880> years 00:07:07.070 --> 00:07:07.080 align:start position:0% we have been talking about for years 00:07:07.080 --> 00:07:08.330 align:start position:0% we have been talking about for years and<00:07:07.440> the<00:07:07.560> main<00:07:07.680> goal<00:07:07.919> of<00:07:07.919> the<00:07:08.039> standard 00:07:08.330 --> 00:07:08.340 align:start position:0% and the main goal of the standard 00:07:08.340 --> 00:07:11.150 align:start position:0% and the main goal of the standard library<00:07:08.520> is<00:07:08.880> to<00:07:09.240> move<00:07:10.020> out<00:07:10.319> the<00:07:10.560> majority<00:07:11.039> of 00:07:11.150 --> 00:07:11.160 align:start position:0% library is to move out the majority of 00:07:11.160 --> 00:07:15.050 align:start position:0% library is to move out the majority of the<00:07:11.400> compiler<00:07:11.819> code<00:07:12.060> into<00:07:12.780> solidity<00:07:13.380> itself 00:07:15.050 --> 00:07:15.060 align:start position:0% the compiler code into solidity itself 00:07:15.060 --> 00:07:16.550 align:start position:0% the compiler code into solidity itself but<00:07:15.419> it<00:07:15.539> is<00:07:15.720> also<00:07:15.840> really<00:07:16.080> good<00:07:16.319> exercise 00:07:16.550 --> 00:07:16.560 align:start position:0% but it is also really good exercise 00:07:16.560 --> 00:07:18.590 align:start position:0% but it is also really good exercise doing<00:07:16.919> it<00:07:17.220> because<00:07:17.400> it<00:07:17.940> shows<00:07:18.180> us<00:07:18.300> what<00:07:18.479> kind 00:07:18.590 --> 00:07:18.600 align:start position:0% doing it because it shows us what kind 00:07:18.600 --> 00:07:20.930 align:start position:0% doing it because it shows us what kind of<00:07:18.660> language<00:07:18.780> features<00:07:19.259> are<00:07:19.500> missing<00:07:20.220> so 00:07:20.930 --> 00:07:20.940 align:start position:0% of language features are missing so 00:07:20.940 --> 00:07:22.850 align:start position:0% of language features are missing so here's<00:07:21.180> one<00:07:21.240> example<00:07:21.599> this<00:07:22.319> actually<00:07:22.560> doesn't 00:07:22.850 --> 00:07:22.860 align:start position:0% here's one example this actually doesn't 00:07:22.860 --> 00:07:25.610 align:start position:0% here's one example this actually doesn't require<00:07:23.160> anything<00:07:23.880> major<00:07:24.259> the<00:07:25.259> only<00:07:25.319> thing<00:07:25.500> it 00:07:25.610 --> 00:07:25.620 align:start position:0% require anything major the only thing it 00:07:25.620 --> 00:07:28.309 align:start position:0% require anything major the only thing it requires<00:07:25.979> is<00:07:26.099> this<00:07:26.280> pragma<00:07:26.940> standard<00:07:27.300> lab 00:07:28.309 --> 00:07:28.319 align:start position:0% requires is this pragma standard lab 00:07:28.319 --> 00:07:30.950 align:start position:0% requires is this pragma standard lab and<00:07:28.800> what<00:07:29.039> it<00:07:29.220> does<00:07:29.400> it<00:07:29.699> just<00:07:29.880> disables<00:07:30.539> the 00:07:30.950 --> 00:07:30.960 align:start position:0% and what it does it just disables the 00:07:30.960 --> 00:07:33.350 align:start position:0% and what it does it just disables the built-in<00:07:31.740> functions<00:07:32.280> because<00:07:32.880> if<00:07:33.120> you<00:07:33.240> don't 00:07:33.350 --> 00:07:33.360 align:start position:0% built-in functions because if you don't 00:07:33.360 --> 00:07:35.930 align:start position:0% built-in functions because if you don't have<00:07:33.539> this<00:07:33.900> primary<00:07:34.680> standard<00:07:34.979> lib<00:07:35.280> this 00:07:35.930 --> 00:07:35.940 align:start position:0% have this primary standard lib this 00:07:35.940 --> 00:07:37.249 align:start position:0% have this primary standard lib this function<00:07:36.180> definition<00:07:36.419> is<00:07:36.840> going<00:07:36.900> to<00:07:37.020> fail 00:07:37.249 --> 00:07:37.259 align:start position:0% function definition is going to fail 00:07:37.259 --> 00:07:39.430 align:start position:0% function definition is going to fail because<00:07:37.860> there's<00:07:38.160> already<00:07:38.400> a<00:07:38.639> shot<00:07:38.759> 256 00:07:39.430 --> 00:07:39.440 align:start position:0% because there's already a shot 256 00:07:39.440 --> 00:07:42.350 align:start position:0% because there's already a shot 256 implicitly<00:07:40.440> in<00:07:40.919> the<00:07:41.039> language<00:07:41.220> if<00:07:42.120> you<00:07:42.240> have 00:07:42.350 --> 00:07:42.360 align:start position:0% implicitly in the language if you have 00:07:42.360 --> 00:07:43.909 align:start position:0% implicitly in the language if you have this<00:07:42.539> it's<00:07:42.960> not<00:07:43.199> going<00:07:43.319> to<00:07:43.319> be<00:07:43.500> there<00:07:43.620> so<00:07:43.800> you 00:07:43.909 --> 00:07:43.919 align:start position:0% this it's not going to be there so you 00:07:43.919 --> 00:07:46.070 align:start position:0% this it's not going to be there so you can<00:07:44.039> define<00:07:44.160> it 00:07:46.070 --> 00:07:46.080 align:start position:0% can define it 00:07:46.080 --> 00:07:47.629 align:start position:0% can define it this<00:07:46.560> is<00:07:46.620> the<00:07:46.800> simplest<00:07:47.039> example<00:07:47.340> in<00:07:47.520> the 00:07:47.629 --> 00:07:47.639 align:start position:0% this is the simplest example in the 00:07:47.639 --> 00:07:49.850 align:start position:0% this is the simplest example in the standard<00:07:47.880> library<00:07:48.000> and<00:07:48.240> this<00:07:48.419> works<00:07:48.860> doing 00:07:49.850 --> 00:07:49.860 align:start position:0% standard library and this works doing 00:07:49.860 --> 00:07:51.950 align:start position:0% standard library and this works doing anything<00:07:50.099> more<00:07:50.460> complicated<00:07:50.940> going<00:07:51.840> to 00:07:51.950 --> 00:07:51.960 align:start position:0% anything more complicated going to 00:07:51.960 --> 00:07:54.129 align:start position:0% anything more complicated going to require<00:07:52.080> a<00:07:52.319> lot<00:07:52.440> of<00:07:52.560> language<00:07:52.680> changes 00:07:54.129 --> 00:07:54.139 align:start position:0% require a lot of language changes 00:07:54.139 --> 00:07:56.510 align:start position:0% require a lot of language changes here's<00:07:55.139> one<00:07:55.199> example<00:07:55.500> what<00:07:55.740> we<00:07:55.979> will<00:07:56.220> require 00:07:56.510 --> 00:07:56.520 align:start position:0% here's one example what we will require 00:07:56.520 --> 00:07:59.270 align:start position:0% here's one example what we will require for<00:07:57.240> the<00:07:57.360> language<00:07:57.479> changes<00:07:58.020> it<00:07:58.979> is<00:07:59.160> just 00:07:59.270 --> 00:07:59.280 align:start position:0% for the language changes it is just 00:07:59.280 --> 00:08:01.370 align:start position:0% for the language changes it is just generics 00:08:01.370 --> 00:08:01.380 align:start position:0% generics 00:08:01.380 --> 00:08:03.290 align:start position:0% generics there's<00:08:01.979> a<00:08:02.220> this<00:08:02.639> is<00:08:02.759> an<00:08:02.880> extremely<00:08:03.180> old 00:08:03.290 --> 00:08:03.300 align:start position:0% there's a this is an extremely old 00:08:03.300 --> 00:08:04.430 align:start position:0% there's a this is an extremely old example 00:08:04.430 --> 00:08:04.440 align:start position:0% example 00:08:04.440 --> 00:08:06.350 align:start position:0% example and<00:08:04.919> in<00:08:04.979> fact<00:08:05.099> I<00:08:05.280> copied<00:08:05.580> this<00:08:05.759> example<00:08:06.000> from 00:08:06.350 --> 00:08:06.360 align:start position:0% and in fact I copied this example from 00:08:06.360 --> 00:08:08.390 align:start position:0% and in fact I copied this example from my<00:08:06.479> talk<00:08:06.660> from<00:08:06.900> two<00:08:07.020> years<00:08:07.199> ago<00:08:07.800> from<00:08:08.280> this 00:08:08.390 --> 00:08:08.400 align:start position:0% my talk from two years ago from this 00:08:08.400 --> 00:08:10.370 align:start position:0% my talk from two years ago from this holiday<00:08:08.639> Summit<00:08:09.120> you're<00:08:09.660> already<00:08:09.840> seeing<00:08:10.259> the 00:08:10.370 --> 00:08:10.380 align:start position:0% holiday Summit you're already seeing the 00:08:10.380 --> 00:08:11.990 align:start position:0% holiday Summit you're already seeing the same<00:08:10.500> things<00:08:10.620> back<00:08:10.979> then 00:08:11.990 --> 00:08:12.000 align:start position:0% same things back then 00:08:12.000 --> 00:08:13.969 align:start position:0% same things back then so<00:08:12.240> I'm<00:08:12.419> not<00:08:12.539> going<00:08:12.660> to<00:08:12.780> go<00:08:12.840> any<00:08:12.960> further<00:08:13.319> if 00:08:13.969 --> 00:08:13.979 align:start position:0% so I'm not going to go any further if 00:08:13.979 --> 00:08:17.150 align:start position:0% so I'm not going to go any further if you<00:08:14.160> want<00:08:14.280> to<00:08:14.400> take<00:08:14.580> a<00:08:15.360> um<00:08:15.840> a<00:08:15.840> photo<00:08:16.199> of<00:08:16.440> the<00:08:16.680> QR 00:08:17.150 --> 00:08:17.160 align:start position:0% you want to take a um a photo of the QR 00:08:17.160 --> 00:08:19.610 align:start position:0% you want to take a um a photo of the QR code<00:08:17.400> this<00:08:18.240> is<00:08:18.360> the<00:08:18.539> talk<00:08:18.660> from<00:08:18.900> Danielle<00:08:19.259> it 00:08:19.610 --> 00:08:19.620 align:start position:0% code this is the talk from Danielle it 00:08:19.620 --> 00:08:21.710 align:start position:0% code this is the talk from Danielle it is<00:08:19.740> a<00:08:19.919> full<00:08:20.039> 30<00:08:20.280> minute<00:08:20.520> talk<00:08:20.819> and<00:08:21.300> it<00:08:21.419> did<00:08:21.599> a 00:08:21.710 --> 00:08:21.720 align:start position:0% is a full 30 minute talk and it did a 00:08:21.720 --> 00:08:23.270 align:start position:0% is a full 30 minute talk and it did a really<00:08:21.900> good<00:08:22.080> job<00:08:22.199> at<00:08:22.319> explaining<00:08:22.860> the 00:08:23.270 --> 00:08:23.280 align:start position:0% really good job at explaining the 00:08:23.280 --> 00:08:25.369 align:start position:0% really good job at explaining the reasoning<00:08:23.639> Behind<00:08:24.000> These<00:08:24.780> features<00:08:25.020> and<00:08:25.199> how 00:08:25.369 --> 00:08:25.379 align:start position:0% reasoning Behind These features and how 00:08:25.379 --> 00:08:26.510 align:start position:0% reasoning Behind These features and how they're<00:08:25.560> going<00:08:25.740> to<00:08:25.860> work 00:08:26.510 --> 00:08:26.520 align:start position:0% they're going to work 00:08:26.520 --> 00:08:28.610 align:start position:0% they're going to work okay<00:08:26.819> now<00:08:27.180> taking<00:08:27.360> a<00:08:27.660> tiny<00:08:27.960> break 00:08:28.610 --> 00:08:28.620 align:start position:0% okay now taking a tiny break 00:08:28.620 --> 00:08:31.249 align:start position:0% okay now taking a tiny break these<00:08:29.220> were<00:08:29.340> the<00:08:29.520> changes<00:08:29.940> the<00:08:30.720> team<00:08:30.840> wants 00:08:31.249 --> 00:08:31.259 align:start position:0% these were the changes the team wants 00:08:31.259 --> 00:08:32.810 align:start position:0% these were the changes the team wants and<00:08:31.379> the<00:08:31.500> team<00:08:31.620> agrees<00:08:32.039> on 00:08:32.810 --> 00:08:32.820 align:start position:0% and the team agrees on 00:08:32.820 --> 00:08:34.810 align:start position:0% and the team agrees on but<00:08:33.300> I<00:08:33.479> kind<00:08:33.599> of<00:08:33.719> want<00:08:33.779> to<00:08:33.899> ask<00:08:34.020> you<00:08:34.140> all<00:08:34.320> of<00:08:34.500> you 00:08:34.810 --> 00:08:34.820 align:start position:0% but I kind of want to ask you all of you 00:08:34.820 --> 00:08:39.110 align:start position:0% but I kind of want to ask you all of you to<00:08:35.820> look<00:08:36.240> at<00:08:36.419> the<00:08:36.719> Repository 00:08:39.110 --> 00:08:39.120 align:start position:0% to look at the Repository 00:08:39.120 --> 00:08:40.969 align:start position:0% to look at the Repository this<00:08:39.599> these<00:08:40.020> are<00:08:40.080> all<00:08:40.260> the<00:08:40.440> it's<00:08:40.680> kind<00:08:40.800> of<00:08:40.919> hard 00:08:40.969 --> 00:08:40.979 align:start position:0% this these are all the it's kind of hard 00:08:40.979 --> 00:08:43.010 align:start position:0% this these are all the it's kind of hard to<00:08:41.099> see<00:08:41.219> but<00:08:41.399> these<00:08:41.580> are<00:08:41.700> all<00:08:41.820> the<00:08:42.000> issues<00:08:42.719> Tech 00:08:43.010 --> 00:08:43.020 align:start position:0% to see but these are all the issues Tech 00:08:43.020 --> 00:08:45.170 align:start position:0% to see but these are all the issues Tech language<00:08:43.320> design 00:08:45.170 --> 00:08:45.180 align:start position:0% language design 00:08:45.180 --> 00:08:48.829 align:start position:0% language design and<00:08:45.600> we<00:08:45.720> have<00:08:45.899> 237<00:08:46.860> issues<00:08:47.640> open<00:08:47.880> those<00:08:48.660> are 00:08:48.829 --> 00:08:48.839 align:start position:0% and we have 237 issues open those are 00:08:48.839 --> 00:08:50.990 align:start position:0% and we have 237 issues open those are the<00:08:48.959> issues<00:08:49.260> people<00:08:49.500> want<00:08:49.860> want<00:08:50.279> as<00:08:50.519> a<00:08:50.700> feature 00:08:50.990 --> 00:08:51.000 align:start position:0% the issues people want want as a feature 00:08:51.000 --> 00:08:52.970 align:start position:0% the issues people want want as a feature and<00:08:51.839> I<00:08:51.959> think<00:08:52.080> many<00:08:52.200> of<00:08:52.380> them<00:08:52.440> actually<00:08:52.620> are 00:08:52.970 --> 00:08:52.980 align:start position:0% and I think many of them actually are 00:08:52.980 --> 00:08:55.070 align:start position:0% and I think many of them actually are kind<00:08:53.160> of<00:08:53.339> obsolete<00:08:53.940> at<00:08:54.000> this<00:08:54.180> point 00:08:55.070 --> 00:08:55.080 align:start position:0% kind of obsolete at this point 00:08:55.080 --> 00:08:56.750 align:start position:0% kind of obsolete at this point um but<00:08:55.500> I<00:08:55.620> ask<00:08:55.740> you<00:08:55.920> to<00:08:56.100> look<00:08:56.399> at<00:08:56.580> this 00:08:56.750 --> 00:08:56.760 align:start position:0% um but I ask you to look at this 00:08:56.760 --> 00:08:58.550 align:start position:0% um but I ask you to look at this repository<00:08:57.300> look<00:08:57.540> at<00:08:57.720> all<00:08:57.959> of<00:08:58.019> these<00:08:58.260> issues 00:08:58.550 --> 00:08:58.560 align:start position:0% repository look at all of these issues 00:08:58.560 --> 00:09:01.130 align:start position:0% repository look at all of these issues or<00:08:59.040> you<00:08:59.279> know<00:08:59.339> a<00:08:59.580> tiny<00:08:59.880> subset<00:09:00.180> of<00:09:00.360> them<00:09:00.480> find 00:09:01.130 --> 00:09:01.140 align:start position:0% or you know a tiny subset of them find 00:09:01.140 --> 00:09:04.370 align:start position:0% or you know a tiny subset of them find something<00:09:01.440> what<00:09:01.980> you<00:09:02.160> like<00:09:02.420> and<00:09:03.420> leave<00:09:04.200> a 00:09:04.370 --> 00:09:04.380 align:start position:0% something what you like and leave a 00:09:04.380 --> 00:09:06.110 align:start position:0% something what you like and leave a comment<00:09:04.620> if<00:09:05.100> you<00:09:05.220> want<00:09:05.339> to<00:09:05.459> have<00:09:05.580> it<00:09:05.760> or<00:09:05.940> leave 00:09:06.110 --> 00:09:06.120 align:start position:0% comment if you want to have it or leave 00:09:06.120 --> 00:09:07.870 align:start position:0% comment if you want to have it or leave a<00:09:06.240> comment<00:09:06.480> if<00:09:06.660> you<00:09:06.779> think<00:09:06.899> it<00:09:07.019> is<00:09:07.200> a<00:09:07.260> bad<00:09:07.380> idea 00:09:07.870 --> 00:09:07.880 align:start position:0% a comment if you think it is a bad idea 00:09:07.880 --> 00:09:11.090 align:start position:0% a comment if you think it is a bad idea you<00:09:08.880> know<00:09:08.940> besides<00:09:09.480> these<00:09:09.899> features<00:09:10.560> that<00:09:10.860> the 00:09:11.090 --> 00:09:11.100 align:start position:0% you know besides these features that the 00:09:11.100 --> 00:09:12.949 align:start position:0% you know besides these features that the team<00:09:11.279> wants<00:09:11.760> I<00:09:12.180> think<00:09:12.300> it<00:09:12.480> would<00:09:12.540> be<00:09:12.720> nice<00:09:12.839> to 00:09:12.949 --> 00:09:12.959 align:start position:0% team wants I think it would be nice to 00:09:12.959 --> 00:09:15.590 align:start position:0% team wants I think it would be nice to know<00:09:13.080> what<00:09:13.260> you<00:09:13.440> guys<00:09:13.560> actually<00:09:13.800> want 00:09:15.590 --> 00:09:15.600 align:start position:0% know what you guys actually want 00:09:15.600 --> 00:09:19.730 align:start position:0% know what you guys actually want so<00:09:16.320> I<00:09:16.860> think<00:09:16.920> that's<00:09:17.100> what<00:09:17.279> 1.0<00:09:17.880> gonna<00:09:18.540> be<00:09:18.779> like 00:09:19.730 --> 00:09:19.740 align:start position:0% so I think that's what 1.0 gonna be like 00:09:19.740 --> 00:09:22.250 align:start position:0% so I think that's what 1.0 gonna be like um<00:09:20.220> not<00:09:20.760> many<00:09:20.880> like<00:09:21.120> visible<00:09:21.420> changes<00:09:21.839> for<00:09:22.080> the 00:09:22.250 --> 00:09:22.260 align:start position:0% um not many like visible changes for the 00:09:22.260 --> 00:09:23.329 align:start position:0% um not many like visible changes for the user<00:09:22.560> side 00:09:23.329 --> 00:09:23.339 align:start position:0% user side 00:09:23.339 --> 00:09:25.790 align:start position:0% user side if<00:09:24.240> you're<00:09:24.420> just<00:09:24.600> writing<00:09:24.959> like<00:09:25.080> a<00:09:25.380> token 00:09:25.790 --> 00:09:25.800 align:start position:0% if you're just writing like a token 00:09:25.800 --> 00:09:28.190 align:start position:0% if you're just writing like a token contract<00:09:26.040> NFC<00:09:26.519> contract<00:09:27.180> Etc<00:09:27.360> but<00:09:27.899> if<00:09:28.080> you're 00:09:28.190 --> 00:09:28.200 align:start position:0% contract NFC contract Etc but if you're 00:09:28.200 --> 00:09:30.430 align:start position:0% contract NFC contract Etc but if you're writing<00:09:28.500> libraries<00:09:28.860> it's<00:09:29.220> going<00:09:29.399> to<00:09:29.640> be 00:09:30.430 --> 00:09:30.440 align:start position:0% writing libraries it's going to be 00:09:30.440 --> 00:09:33.769 align:start position:0% writing libraries it's going to be entirely<00:09:31.440> different<00:09:31.620> you<00:09:32.279> know<00:09:32.399> one<00:09:32.519> 2.0 00:09:33.769 --> 00:09:33.779 align:start position:0% entirely different you know one 2.0 00:09:33.779 --> 00:09:35.930 align:start position:0% entirely different you know one 2.0 that<00:09:34.140> is<00:09:34.260> a<00:09:34.380> crazy<00:09:34.500> topic 00:09:35.930 --> 00:09:35.940 align:start position:0% that is a crazy topic 00:09:35.940 --> 00:09:37.490 align:start position:0% that is a crazy topic and<00:09:36.480> uh 00:09:37.490 --> 00:09:37.500 align:start position:0% and uh 00:09:37.500 --> 00:09:38.870 align:start position:0% and uh we<00:09:37.860> have<00:09:38.040> been<00:09:38.160> actually<00:09:38.279> talking<00:09:38.519> about<00:09:38.700> this 00:09:38.870 --> 00:09:38.880 align:start position:0% we have been actually talking about this 00:09:38.880 --> 00:09:40.910 align:start position:0% we have been actually talking about this for<00:09:39.000> a<00:09:39.120> couple<00:09:39.240> of<00:09:39.300> months<00:09:39.660> at<00:09:39.899> this<00:09:40.080> point<00:09:40.200> on 00:09:40.910 --> 00:09:40.920 align:start position:0% for a couple of months at this point on 00:09:40.920 --> 00:09:43.250 align:start position:0% for a couple of months at this point on and<00:09:41.100> off 00:09:43.250 --> 00:09:43.260 align:start position:0% 00:09:43.260 --> 00:09:45.590 align:start position:0% and<00:09:43.920> actually<00:09:44.220> 2.0 00:09:45.590 --> 00:09:45.600 align:start position:0% and actually 2.0 00:09:45.600 --> 00:09:47.389 align:start position:0% and actually 2.0 it's<00:09:46.080> two<00:09:46.320> different<00:09:46.440> things 00:09:47.389 --> 00:09:47.399 align:start position:0% it's two different things 00:09:47.399 --> 00:09:49.790 align:start position:0% it's two different things and<00:09:47.940> it<00:09:48.000> has<00:09:48.180> been<00:09:48.360> like<00:09:48.540> super<00:09:48.839> confusing<00:09:49.620> at 00:09:49.790 --> 00:09:49.800 align:start position:0% and it has been like super confusing at 00:09:49.800 --> 00:09:51.949 align:start position:0% and it has been like super confusing at the<00:09:49.920> team<00:09:50.040> even<00:09:50.160> talk<00:09:50.459> about<00:09:50.580> it<00:09:50.820> because<00:09:51.060> you 00:09:51.949 --> 00:09:51.959 align:start position:0% the team even talk about it because you 00:09:51.959 --> 00:09:53.570 align:start position:0% the team even talk about it because you know<00:09:52.019> some<00:09:52.200> people<00:09:52.320> meant<00:09:52.740> the<00:09:52.920> one<00:09:53.279> or<00:09:53.459> the 00:09:53.570 --> 00:09:53.580 align:start position:0% know some people meant the one or the 00:09:53.580 --> 00:09:54.350 align:start position:0% know some people meant the one or the other 00:09:54.350 --> 00:09:54.360 align:start position:0% other 00:09:54.360 --> 00:09:56.090 align:start position:0% other and<00:09:54.959> I<00:09:55.260> just<00:09:55.320> want<00:09:55.440> to<00:09:55.560> highlight<00:09:55.800> it<00:09:55.980> again 00:09:56.090 --> 00:09:56.100 align:start position:0% and I just want to highlight it again 00:09:56.100 --> 00:09:58.490 align:start position:0% and I just want to highlight it again you<00:09:56.580> know<00:09:56.640> nothing<00:09:56.940> is<00:09:57.180> decided<00:09:57.600> here<00:09:57.779> a<00:09:58.380> lot 00:09:58.490 --> 00:09:58.500 align:start position:0% you know nothing is decided here a lot 00:09:58.500 --> 00:10:00.829 align:start position:0% you know nothing is decided here a lot of<00:09:58.620> this<00:09:58.740> is<00:09:58.920> just<00:09:59.160> uh<00:09:59.580> you<00:09:59.940> know<00:10:00.060> my<00:10:00.240> idea<00:10:00.540> what 00:10:00.829 --> 00:10:00.839 align:start position:0% of this is just uh you know my idea what 00:10:00.839 --> 00:10:02.990 align:start position:0% of this is just uh you know my idea what I<00:10:01.080> want<00:10:01.680> to<00:10:01.860> have 00:10:02.990 --> 00:10:03.000 align:start position:0% I want to have 00:10:03.000 --> 00:10:04.310 align:start position:0% I want to have um<00:10:03.060> but<00:10:03.300> I<00:10:03.420> hope<00:10:03.540> some<00:10:03.660> of<00:10:03.839> this<00:10:03.899> is<00:10:04.019> going<00:10:04.200> to 00:10:04.310 --> 00:10:04.320 align:start position:0% um but I hope some of this is going to 00:10:04.320 --> 00:10:06.290 align:start position:0% um but I hope some of this is going to happen<00:10:04.860> so<00:10:05.100> first<00:10:05.339> I<00:10:05.519> can<00:10:05.700> talk<00:10:06.000> about<00:10:06.120> like 00:10:06.290 --> 00:10:06.300 align:start position:0% happen so first I can talk about like 00:10:06.300 --> 00:10:08.449 align:start position:0% happen so first I can talk about like this<00:10:06.480> compiler<00:10:07.019> rewrite 00:10:08.449 --> 00:10:08.459 align:start position:0% this compiler rewrite 00:10:08.459 --> 00:10:11.570 align:start position:0% this compiler rewrite where<00:10:08.820> it<00:10:08.940> sounds<00:10:09.060> crazy<00:10:09.360> right 00:10:11.570 --> 00:10:11.580 align:start position:0% where it sounds crazy right 00:10:11.580 --> 00:10:13.190 align:start position:0% where it sounds crazy right um<00:10:11.700> how<00:10:12.300> many<00:10:12.420> of<00:10:12.480> you<00:10:12.600> actually<00:10:12.720> know<00:10:12.959> the 00:10:13.190 --> 00:10:13.200 align:start position:0% um how many of you actually know the 00:10:13.200 --> 00:10:15.170 align:start position:0% um how many of you actually know the compiler<00:10:13.560> how<00:10:13.800> does<00:10:13.920> the<00:10:14.100> compiler<00:10:14.459> work 00:10:15.170 --> 00:10:15.180 align:start position:0% compiler how does the compiler work 00:10:15.180 --> 00:10:19.490 align:start position:0% compiler how does the compiler work or<00:10:15.779> a<00:10:16.019> compiler<00:10:16.440> in<00:10:16.680> general 00:10:19.490 --> 00:10:19.500 align:start position:0% 00:10:19.500 --> 00:10:22.070 align:start position:0% not<00:10:20.040> many<00:10:20.220> of<00:10:20.399> you 00:10:22.070 --> 00:10:22.080 align:start position:0% not many of you 00:10:22.080 --> 00:10:23.389 align:start position:0% not many of you um 00:10:23.389 --> 00:10:23.399 align:start position:0% um 00:10:23.399 --> 00:10:25.610 align:start position:0% um basically<00:10:24.060> a<00:10:24.240> compiler<00:10:24.600> has<00:10:24.839> multiple<00:10:25.320> stages 00:10:25.610 --> 00:10:25.620 align:start position:0% basically a compiler has multiple stages 00:10:25.620 --> 00:10:27.949 align:start position:0% basically a compiler has multiple stages you<00:10:26.339> know<00:10:26.399> we<00:10:26.640> take<00:10:26.760> like<00:10:26.940> the<00:10:27.120> source<00:10:27.420> code<00:10:27.540> we 00:10:27.949 --> 00:10:27.959 align:start position:0% you know we take like the source code we 00:10:27.959 --> 00:10:29.210 align:start position:0% you know we take like the source code we process<00:10:28.260> the<00:10:28.440> source<00:10:28.680> code<00:10:28.800> into<00:10:29.040> some 00:10:29.210 --> 00:10:29.220 align:start position:0% process the source code into some 00:10:29.220 --> 00:10:31.610 align:start position:0% process the source code into some internal<00:10:29.580> representation<00:10:30.180> uh<00:10:31.080> we<00:10:31.200> do<00:10:31.380> a<00:10:31.560> lot 00:10:31.610 --> 00:10:31.620 align:start position:0% internal representation uh we do a lot 00:10:31.620 --> 00:10:33.530 align:start position:0% internal representation uh we do a lot of<00:10:31.800> different<00:10:32.640> analysis<00:10:33.240> on<00:10:33.420> that 00:10:33.530 --> 00:10:33.540 align:start position:0% of different analysis on that 00:10:33.540 --> 00:10:35.810 align:start position:0% of different analysis on that representation<00:10:34.140> once<00:10:35.040> we<00:10:35.160> are<00:10:35.339> happy<00:10:35.459> with 00:10:35.810 --> 00:10:35.820 align:start position:0% representation once we are happy with 00:10:35.820 --> 00:10:38.030 align:start position:0% representation once we are happy with the<00:10:36.120> code<00:10:36.660> that<00:10:36.839> it<00:10:37.019> is<00:10:37.200> sound<00:10:37.380> that<00:10:37.620> it<00:10:37.740> works 00:10:38.030 --> 00:10:38.040 align:start position:0% the code that it is sound that it works 00:10:38.040 --> 00:10:42.410 align:start position:0% the code that it is sound that it works uh<00:10:39.000> we<00:10:39.480> are<00:10:39.660> generating<00:10:40.019> some<00:10:40.500> kind<00:10:40.680> of<00:10:40.800> a<00:10:41.420> next 00:10:42.410 --> 00:10:42.420 align:start position:0% uh we are generating some kind of a next 00:10:42.420 --> 00:10:43.490 align:start position:0% uh we are generating some kind of a next stage 00:10:43.490 --> 00:10:43.500 align:start position:0% stage 00:10:43.500 --> 00:10:46.430 align:start position:0% stage in<00:10:44.700> the<00:10:45.240> first<00:10:45.360> version<00:10:45.540> of<00:10:45.839> the<00:10:45.959> compiler 00:10:46.430 --> 00:10:46.440 align:start position:0% in the first version of the compiler 00:10:46.440 --> 00:10:49.610 align:start position:0% in the first version of the compiler this<00:10:47.279> generation<00:10:47.640> was<00:10:47.880> directly<00:10:48.240> into<00:10:48.360> evm 00:10:49.610 --> 00:10:49.620 align:start position:0% this generation was directly into evm 00:10:49.620 --> 00:10:51.829 align:start position:0% this generation was directly into evm in<00:10:50.339> the<00:10:50.519> current<00:10:50.640> stage<00:10:50.940> we<00:10:51.120> already<00:10:51.300> have<00:10:51.540> we 00:10:51.829 --> 00:10:51.839 align:start position:0% in the current stage we already have we 00:10:51.839 --> 00:10:53.449 align:start position:0% in the current stage we already have we we<00:10:52.019> still<00:10:52.320> have<00:10:52.440> this<00:10:52.620> but<00:10:52.860> we<00:10:52.980> also<00:10:53.160> have<00:10:53.339> a 00:10:53.449 --> 00:10:53.459 align:start position:0% we still have this but we also have a 00:10:53.459 --> 00:10:56.030 align:start position:0% we still have this but we also have a second<00:10:53.640> pipeline<00:10:54.180> where<00:10:54.779> instead<00:10:55.140> of<00:10:55.260> uh 00:10:56.030 --> 00:10:56.040 align:start position:0% second pipeline where instead of uh 00:10:56.040 --> 00:10:57.710 align:start position:0% second pipeline where instead of uh directly<00:10:56.399> generating<00:10:56.700> to<00:10:56.940> evm<00:10:57.300> we<00:10:57.420> generate 00:10:57.710 --> 00:10:57.720 align:start position:0% directly generating to evm we generate 00:10:57.720 --> 00:10:59.930 align:start position:0% directly generating to evm we generate it<00:10:57.779> to<00:10:57.899> Yule<00:10:58.260> which<00:10:59.040> is<00:10:59.160> our<00:10:59.339> Intermediate 00:10:59.930 --> 00:10:59.940 align:start position:0% it to Yule which is our Intermediate 00:10:59.940 --> 00:11:01.370 align:start position:0% it to Yule which is our Intermediate Language 00:11:01.370 --> 00:11:01.380 align:start position:0% Language 00:11:01.380 --> 00:11:02.750 align:start position:0% Language um<00:11:01.440> but<00:11:01.740> you<00:11:01.860> must<00:11:02.040> be<00:11:02.220> familiar<00:11:02.459> with<00:11:02.640> you 00:11:02.750 --> 00:11:02.760 align:start position:0% um but you must be familiar with you 00:11:02.760 --> 00:11:05.870 align:start position:0% um but you must be familiar with you because<00:11:03.060> it<00:11:03.360> is<00:11:03.480> a<00:11:03.720> line<00:11:03.959> assembly<00:11:04.380> basically 00:11:05.870 --> 00:11:05.880 align:start position:0% because it is a line assembly basically 00:11:05.880 --> 00:11:07.910 align:start position:0% because it is a line assembly basically and<00:11:06.300> then<00:11:06.360> we<00:11:06.540> take<00:11:06.660> fuel<00:11:06.959> and<00:11:07.140> generate<00:11:07.440> evm 00:11:07.910 --> 00:11:07.920 align:start position:0% and then we take fuel and generate evm 00:11:07.920 --> 00:11:09.410 align:start position:0% and then we take fuel and generate evm byte<00:11:08.220> code 00:11:09.410 --> 00:11:09.420 align:start position:0% byte code 00:11:09.420 --> 00:11:11.690 align:start position:0% byte code so<00:11:09.660> that<00:11:09.899> is<00:11:10.019> the<00:11:10.140> the<00:11:10.260> pipeline<00:11:10.800> and<00:11:11.519> then 00:11:11.690 --> 00:11:11.700 align:start position:0% so that is the the pipeline and then 00:11:11.700 --> 00:11:13.550 align:start position:0% so that is the the pipeline and then these<00:11:12.360> are<00:11:12.420> the<00:11:12.540> different<00:11:12.720> libraries<00:11:13.260> we 00:11:13.550 --> 00:11:13.560 align:start position:0% these are the different libraries we 00:11:13.560 --> 00:11:15.829 align:start position:0% these are the different libraries we have<00:11:13.740> in<00:11:14.279> the<00:11:14.459> compiler<00:11:14.820> itself 00:11:15.829 --> 00:11:15.839 align:start position:0% have in the compiler itself 00:11:15.839 --> 00:11:19.009 align:start position:0% have in the compiler itself so<00:11:16.200> this<00:11:16.500> one<00:11:16.680> is<00:11:16.800> just<00:11:17.040> really<00:11:17.279> tiny<00:11:18.000> helpers 00:11:19.009 --> 00:11:19.019 align:start position:0% so this one is just really tiny helpers 00:11:19.019 --> 00:11:21.470 align:start position:0% so this one is just really tiny helpers I'm<00:11:19.380> going<00:11:19.680> to<00:11:19.740> move<00:11:19.860> to<00:11:19.980> the<00:11:20.100> other<00:11:20.160> side 00:11:21.470 --> 00:11:21.480 align:start position:0% I'm going to move to the other side 00:11:21.480 --> 00:11:22.910 align:start position:0% I'm going to move to the other side um<00:11:21.540> so<00:11:21.660> these<00:11:21.899> are<00:11:22.019> just<00:11:22.140> helpers<00:11:22.440> used<00:11:22.620> by<00:11:22.800> the 00:11:22.910 --> 00:11:22.920 align:start position:0% um so these are just helpers used by the 00:11:22.920 --> 00:11:25.430 align:start position:0% um so these are just helpers used by the others<00:11:23.279> the<00:11:24.000> assembler<00:11:24.420> is<00:11:24.660> a 00:11:25.430 --> 00:11:25.440 align:start position:0% others the assembler is a 00:11:25.440 --> 00:11:28.970 align:start position:0% others the assembler is a kind<00:11:25.920> of<00:11:26.100> separate<00:11:26.399> it's<00:11:26.940> it's<00:11:27.180> standalone 00:11:28.970 --> 00:11:28.980 align:start position:0% kind of separate it's it's standalone 00:11:28.980 --> 00:11:31.310 align:start position:0% kind of separate it's it's standalone it<00:11:29.579> takes<00:11:29.700> in<00:11:30.000> a<00:11:30.120> data<00:11:30.480> structure<00:11:30.779> like<00:11:31.200> the 00:11:31.310 --> 00:11:31.320 align:start position:0% it takes in a data structure like the 00:11:31.320 --> 00:11:33.050 align:start position:0% it takes in a data structure like the representation<00:11:31.800> of<00:11:32.100> the<00:11:32.339> the<00:11:32.579> assembler 00:11:33.050 --> 00:11:33.060 align:start position:0% representation of the the assembler 00:11:33.060 --> 00:11:35.389 align:start position:0% representation of the the assembler source<00:11:33.540> code<00:11:33.660> you<00:11:33.899> want<00:11:34.079> to<00:11:34.140> assemble 00:11:35.389 --> 00:11:35.399 align:start position:0% source code you want to assemble 00:11:35.399 --> 00:11:37.310 align:start position:0% source code you want to assemble um<00:11:35.519> byte<00:11:36.480> code<00:11:36.600> but<00:11:36.779> it<00:11:36.899> also<00:11:37.079> has 00:11:37.310 --> 00:11:37.320 align:start position:0% um byte code but it also has 00:11:37.320 --> 00:11:39.710 align:start position:0% um byte code but it also has optimization<00:11:37.980> steps 00:11:39.710 --> 00:11:39.720 align:start position:0% optimization steps 00:11:39.720 --> 00:11:42.889 align:start position:0% optimization steps then<00:11:40.140> we<00:11:40.320> have<00:11:40.440> this<00:11:40.620> separate<00:11:41.040> helper<00:11:41.940> for 00:11:42.889 --> 00:11:42.899 align:start position:0% then we have this separate helper for 00:11:42.899 --> 00:11:44.569 align:start position:0% then we have this separate helper for it's<00:11:43.260> called<00:11:43.440> language<00:11:43.680> utilities<00:11:44.220> but<00:11:44.459> it's 00:11:44.569 --> 00:11:44.579 align:start position:0% it's called language utilities but it's 00:11:44.579 --> 00:11:46.009 align:start position:0% it's called language utilities but it's really<00:11:44.760> just<00:11:44.940> helpers<00:11:45.300> for<00:11:45.480> the<00:11:45.660> parsers 00:11:46.009 --> 00:11:46.019 align:start position:0% really just helpers for the parsers 00:11:46.019 --> 00:11:48.290 align:start position:0% really just helpers for the parsers because<00:11:46.320> we<00:11:46.560> have<00:11:46.680> two<00:11:46.800> different<00:11:46.980> parsers<00:11:47.519> we 00:11:48.290 --> 00:11:48.300 align:start position:0% because we have two different parsers we 00:11:48.300 --> 00:11:50.389 align:start position:0% because we have two different parsers we have<00:11:48.420> the<00:11:48.540> solidity<00:11:48.899> parser<00:11:49.380> and<00:11:49.500> the<00:11:49.620> yield 00:11:50.389 --> 00:11:50.399 align:start position:0% have the solidity parser and the yield 00:11:50.399 --> 00:11:54.050 align:start position:0% have the solidity parser and the yield so<00:11:51.360> Lang<00:11:51.600> duties<00:11:52.079> is<00:11:52.320> used<00:11:52.500> by<00:11:52.920> both<00:11:53.160> of<00:11:53.339> these 00:11:54.050 --> 00:11:54.060 align:start position:0% so Lang duties is used by both of these 00:11:54.060 --> 00:11:58.009 align:start position:0% so Lang duties is used by both of these uh<00:11:54.839> the<00:11:55.200> Libya<00:11:56.220> has<00:11:56.700> a<00:11:56.880> parser<00:11:57.240> has<00:11:57.420> a<00:11:57.660> code<00:11:57.720> gen 00:11:58.009 --> 00:11:58.019 align:start position:0% uh the Libya has a parser has a code gen 00:11:58.019 --> 00:12:00.710 align:start position:0% uh the Libya has a parser has a code gen has<00:11:58.680> another<00:11:58.920> kind<00:11:59.220> of<00:11:59.339> optimizer 00:12:00.710 --> 00:12:00.720 align:start position:0% has another kind of optimizer 00:12:00.720 --> 00:12:03.350 align:start position:0% has another kind of optimizer and<00:12:01.140> then<00:12:01.260> lips<00:12:01.500> solidity<00:12:01.860> is<00:12:02.100> a<00:12:02.220> big<00:12:02.279> one<00:12:02.399> uh 00:12:03.350 --> 00:12:03.360 align:start position:0% and then lips solidity is a big one uh 00:12:03.360 --> 00:12:05.210 align:start position:0% and then lips solidity is a big one uh it's<00:12:03.600> the<00:12:03.779> it's<00:12:04.019> a<00:12:04.140> monster<00:12:04.260> it<00:12:04.920> is<00:12:05.040> it's 00:12:05.210 --> 00:12:05.220 align:start position:0% it's the it's a monster it is it's 00:12:05.220 --> 00:12:07.069 align:start position:0% it's the it's a monster it is it's already<00:12:05.459> departure 00:12:07.069 --> 00:12:07.079 align:start position:0% already departure 00:12:07.079 --> 00:12:09.410 align:start position:0% already departure um does<00:12:07.500> all<00:12:07.680> the<00:12:07.800> analysis<00:12:08.220> I<00:12:08.399> mentioned<00:12:08.760> and 00:12:09.410 --> 00:12:09.420 align:start position:0% um does all the analysis I mentioned and 00:12:09.420 --> 00:12:11.269 align:start position:0% um does all the analysis I mentioned and does<00:12:09.600> these<00:12:10.079> two<00:12:10.200> different<00:12:10.380> pipelines<00:12:10.980> for 00:12:11.269 --> 00:12:11.279 align:start position:0% does these two different pipelines for 00:12:11.279 --> 00:12:13.370 align:start position:0% does these two different pipelines for code<00:12:11.459> generation 00:12:13.370 --> 00:12:13.380 align:start position:0% code generation 00:12:13.380 --> 00:12:16.069 align:start position:0% code generation and<00:12:13.740> then<00:12:13.860> we<00:12:14.040> have<00:12:14.220> two<00:12:15.120> smaller<00:12:15.720> libraries 00:12:16.069 --> 00:12:16.079 align:start position:0% and then we have two smaller libraries 00:12:16.079 --> 00:12:18.769 align:start position:0% and then we have two smaller libraries the<00:12:16.860> smt<00:12:17.339> library<00:12:17.640> is<00:12:18.000> just<00:12:18.120> for<00:12:18.300> the<00:12:18.420> SMD 00:12:18.769 --> 00:12:18.779 align:start position:0% the smt library is just for the SMD 00:12:18.779 --> 00:12:20.930 align:start position:0% the smt library is just for the SMD subsystem<00:12:19.200> but<00:12:19.920> I<00:12:20.040> think<00:12:20.220> that<00:12:20.339> that<00:12:20.519> is<00:12:20.700> also 00:12:20.930 --> 00:12:20.940 align:start position:0% subsystem but I think that that is also 00:12:20.940 --> 00:12:23.389 align:start position:0% subsystem but I think that that is also split<00:12:21.240> up<00:12:21.300> so<00:12:21.480> some<00:12:21.720> of<00:12:21.839> it<00:12:21.959> is<00:12:22.380> here<00:12:22.680> some<00:12:23.220> of 00:12:23.389 --> 00:12:23.399 align:start position:0% split up so some of it is here some of 00:12:23.399 --> 00:12:26.329 align:start position:0% split up so some of it is here some of it<00:12:23.519> is<00:12:23.700> in<00:12:23.940> this<00:12:24.060> lip<00:12:24.420> solidity<00:12:24.839> directory<00:12:25.500> and 00:12:26.329 --> 00:12:26.339 align:start position:0% it is in this lip solidity directory and 00:12:26.339 --> 00:12:27.889 align:start position:0% it is in this lip solidity directory and lastly<00:12:26.700> the<00:12:26.880> smallest<00:12:27.180> one<00:12:27.300> is<00:12:27.420> lips<00:12:27.660> we'll 00:12:27.889 --> 00:12:27.899 align:start position:0% lastly the smallest one is lips we'll 00:12:27.899 --> 00:12:31.069 align:start position:0% lastly the smallest one is lips we'll see<00:12:28.019> which<00:12:28.920> is<00:12:29.640> a<00:12:29.820> tiny<00:12:30.060> binding<00:12:30.480> that<00:12:30.839> is<00:12:30.959> the 00:12:31.069 --> 00:12:31.079 align:start position:0% see which is a tiny binding that is the 00:12:31.079 --> 00:12:34.009 align:start position:0% see which is a tiny binding that is the only<00:12:31.200> Library<00:12:31.440> which<00:12:31.800> is<00:12:31.980> C<00:12:32.360> has<00:12:33.360> a<00:12:33.540> c<00:12:33.660> API 00:12:34.009 --> 00:12:34.019 align:start position:0% only Library which is C has a c API 00:12:34.019 --> 00:12:36.290 align:start position:0% only Library which is C has a c API everything<00:12:34.380> else<00:12:34.620> is<00:12:34.800> C<00:12:34.980> plus<00:12:35.220> plus<00:12:35.459> so<00:12:36.120> this 00:12:36.290 --> 00:12:36.300 align:start position:0% everything else is C plus plus so this 00:12:36.300 --> 00:12:38.090 align:start position:0% everything else is C plus plus so this basically<00:12:36.660> is<00:12:36.839> a<00:12:37.019> wrapper<00:12:37.260> between<00:12:37.440> C<00:12:37.740> and<00:12:37.920> C 00:12:38.090 --> 00:12:38.100 align:start position:0% basically is a wrapper between C and C 00:12:38.100 --> 00:12:39.410 align:start position:0% basically is a wrapper between C and C plus<00:12:38.220> plus 00:12:39.410 --> 00:12:39.420 align:start position:0% plus plus 00:12:39.420 --> 00:12:41.990 align:start position:0% plus plus and<00:12:39.959> that<00:12:40.140> is<00:12:40.320> uh<00:12:40.560> what<00:12:40.800> is<00:12:40.920> compiled<00:12:41.399> to<00:12:41.700> M 00:12:41.990 --> 00:12:42.000 align:start position:0% and that is uh what is compiled to M 00:12:42.000 --> 00:12:43.970 align:start position:0% and that is uh what is compiled to M script<00:12:42.300> and<00:12:42.420> into<00:12:42.600> JavaScript<00:12:43.079> if<00:12:43.680> you<00:12:43.860> happen 00:12:43.970 --> 00:12:43.980 align:start position:0% script and into JavaScript if you happen 00:12:43.980 --> 00:12:46.370 align:start position:0% script and into JavaScript if you happen to<00:12:44.220> use<00:12:44.399> any<00:12:44.700> kind<00:12:44.940> of<00:12:45.060> a<00:12:45.360> web<00:12:45.660> app<00:12:45.839> that<00:12:46.200> has 00:12:46.370 --> 00:12:46.380 align:start position:0% to use any kind of a web app that has 00:12:46.380 --> 00:12:48.230 align:start position:0% to use any kind of a web app that has related<00:12:46.740> it<00:12:46.920> would<00:12:47.040> be<00:12:47.160> used 00:12:48.230 --> 00:12:48.240 align:start position:0% related it would be used 00:12:48.240 --> 00:12:49.670 align:start position:0% related it would be used few 00:12:49.670 --> 00:12:49.680 align:start position:0% few 00:12:49.680 --> 00:12:51.829 align:start position:0% few maybe<00:12:50.040> some<00:12:50.279> benefits<00:12:50.639> as<00:12:50.760> well<00:12:50.940> but<00:12:51.240> you<00:12:51.720> know 00:12:51.829 --> 00:12:51.839 align:start position:0% maybe some benefits as well but you know 00:12:51.839 --> 00:12:54.650 align:start position:0% maybe some benefits as well but you know one<00:12:52.320> of<00:12:52.440> the<00:12:52.740> bigger<00:12:53.519> problems<00:12:53.880> we<00:12:54.120> are 00:12:54.650 --> 00:12:54.660 align:start position:0% one of the bigger problems we are 00:12:54.660 --> 00:12:57.290 align:start position:0% one of the bigger problems we are getting<00:12:55.019> into<00:12:55.320> is<00:12:55.740> these<00:12:56.639> libraries<00:12:56.940> while 00:12:57.290 --> 00:12:57.300 align:start position:0% getting into is these libraries while 00:12:57.300 --> 00:12:58.610 align:start position:0% getting into is these libraries while physically<00:12:57.720> separated<00:12:58.139> into<00:12:58.320> their 00:12:58.610 --> 00:12:58.620 align:start position:0% physically separated into their 00:12:58.620 --> 00:13:00.650 align:start position:0% physically separated into their different<00:12:58.920> directories 00:13:00.650 --> 00:13:00.660 align:start position:0% different directories 00:13:00.660 --> 00:13:02.690 align:start position:0% different directories um<00:13:00.779> they<00:13:01.260> may<00:13:01.440> not<00:13:01.560> be<00:13:01.800> like<00:13:02.040> super<00:13:02.339> well 00:13:02.690 --> 00:13:02.700 align:start position:0% um they may not be like super well 00:13:02.700 --> 00:13:04.790 align:start position:0% um they may not be like super well separated<00:13:03.240> conceptually<00:13:03.959> or<00:13:04.440> even<00:13:04.560> like 00:13:04.790 --> 00:13:04.800 align:start position:0% separated conceptually or even like 00:13:04.800 --> 00:13:06.949 align:start position:0% separated conceptually or even like interface<00:13:05.220> wise 00:13:06.949 --> 00:13:06.959 align:start position:0% interface wise 00:13:06.959 --> 00:13:09.710 align:start position:0% interface wise um<00:13:07.079> one<00:13:07.560> example<00:13:07.980> I<00:13:08.339> can<00:13:08.519> give<00:13:08.700> which<00:13:09.000> which<00:13:09.480> is 00:13:09.710 --> 00:13:09.720 align:start position:0% um one example I can give which which is 00:13:09.720 --> 00:13:12.590 align:start position:0% um one example I can give which which is I<00:13:10.139> kind<00:13:10.260> of<00:13:10.380> hit<00:13:10.560> it's<00:13:10.740> not<00:13:10.920> like<00:13:11.100> a 00:13:12.590 --> 00:13:12.600 align:start position:0% I kind of hit it's not like a 00:13:12.600 --> 00:13:15.170 align:start position:0% I kind of hit it's not like a you<00:13:13.139> know<00:13:13.200> logical<00:13:13.680> like<00:13:14.279> um<00:13:14.279> issue<00:13:14.880> in<00:13:15.060> there 00:13:15.170 --> 00:13:15.180 align:start position:0% you know logical like um issue in there 00:13:15.180 --> 00:13:16.610 align:start position:0% you know logical like um issue in there it's<00:13:15.300> more<00:13:15.480> like<00:13:15.600> just<00:13:15.779> a<00:13:15.899> source<00:13:16.139> code<00:13:16.260> issue 00:13:16.610 --> 00:13:16.620 align:start position:0% it's more like just a source code issue 00:13:16.620 --> 00:13:18.590 align:start position:0% it's more like just a source code issue but<00:13:16.800> we<00:13:17.100> have<00:13:17.339> a 00:13:18.590 --> 00:13:18.600 align:start position:0% but we have a 00:13:18.600 --> 00:13:22.129 align:start position:0% but we have a a<00:13:18.720> loop<00:13:19.440> between<00:13:19.620> libu<00:13:20.160> leap<00:13:20.519> evm<00:13:20.880> ASM 00:13:22.129 --> 00:13:22.139 align:start position:0% a loop between libu leap evm ASM 00:13:22.139 --> 00:13:23.750 align:start position:0% a loop between libu leap evm ASM um<00:13:22.260> and<00:13:22.440> the<00:13:22.620> front<00:13:22.740> end<00:13:22.920> they're 00:13:23.750 --> 00:13:23.760 align:start position:0% um and the front end they're 00:13:23.760 --> 00:13:26.090 align:start position:0% um and the front end they're interdependent<00:13:24.540> on<00:13:24.839> each<00:13:25.019> other 00:13:26.090 --> 00:13:26.100 align:start position:0% interdependent on each other 00:13:26.100 --> 00:13:27.769 align:start position:0% interdependent on each other um<00:13:26.220> which<00:13:26.579> is<00:13:26.760> kind<00:13:26.940> of<00:13:27.000> bad<00:13:27.120> if<00:13:27.300> you<00:13:27.420> want<00:13:27.540> to 00:13:27.769 --> 00:13:27.779 align:start position:0% um which is kind of bad if you want to 00:13:27.779 --> 00:13:30.530 align:start position:0% um which is kind of bad if you want to separate<00:13:28.380> these<00:13:28.680> things<00:13:28.860> nicely<00:13:30.000> major 00:13:30.530 --> 00:13:30.540 align:start position:0% separate these things nicely major 00:13:30.540 --> 00:13:32.569 align:start position:0% separate these things nicely major components<00:13:31.260> they<00:13:31.500> do<00:13:31.740> have<00:13:31.920> some<00:13:32.279> kind<00:13:32.399> of<00:13:32.519> a 00:13:32.569 --> 00:13:32.579 align:start position:0% components they do have some kind of a 00:13:32.579 --> 00:13:34.550 align:start position:0% components they do have some kind of a clear<00:13:32.700> boundary<00:13:33.180> but<00:13:33.779> it's<00:13:33.959> everything<00:13:34.139> is<00:13:34.380> in 00:13:34.550 --> 00:13:34.560 align:start position:0% clear boundary but it's everything is in 00:13:34.560 --> 00:13:37.250 align:start position:0% clear boundary but it's everything is in C<00:13:34.680> plus<00:13:34.860> the 00:13:37.250 --> 00:13:37.260 align:start position:0% C plus the 00:13:37.260 --> 00:13:39.350 align:start position:0% C plus the the<00:13:37.320> clearest<00:13:38.100> external<00:13:38.399> boundary<00:13:38.880> happens 00:13:39.350 --> 00:13:39.360 align:start position:0% the clearest external boundary happens 00:13:39.360 --> 00:13:42.470 align:start position:0% the clearest external boundary happens in<00:13:39.600> two<00:13:39.779> places<00:13:40.399> the<00:13:41.399> assembler<00:13:41.820> has<00:13:42.120> a<00:13:42.240> Json 00:13:42.470 --> 00:13:42.480 align:start position:0% in two places the assembler has a Json 00:13:42.480 --> 00:13:44.810 align:start position:0% in two places the assembler has a Json Import<00:13:42.720> and<00:13:43.260> Export<00:13:43.620> feature 00:13:44.810 --> 00:13:44.820 align:start position:0% Import and Export feature 00:13:44.820 --> 00:13:46.850 align:start position:0% Import and Export feature the<00:13:45.720> export<00:13:46.079> feature<00:13:46.440> has<00:13:46.560> been<00:13:46.680> there 00:13:46.850 --> 00:13:46.860 align:start position:0% the export feature has been there 00:13:46.860 --> 00:13:49.069 align:start position:0% the export feature has been there forever<00:13:47.160> the<00:13:47.760> import<00:13:47.880> feature 00:13:49.069 --> 00:13:49.079 align:start position:0% forever the import feature 00:13:49.079 --> 00:13:51.650 align:start position:0% forever the import feature is<00:13:49.560> still<00:13:49.680> not<00:13:49.860> merged<00:13:50.160> but<00:13:50.399> it<00:13:50.820> kind<00:13:50.940> of<00:13:51.060> works 00:13:51.650 --> 00:13:51.660 align:start position:0% is still not merged but it kind of works 00:13:51.660 --> 00:13:54.590 align:start position:0% is still not merged but it kind of works and<00:13:52.560> then<00:13:52.680> solidity<00:13:53.220> itself<00:13:53.760> has<00:13:54.060> this<00:13:54.300> Json 00:13:54.590 --> 00:13:54.600 align:start position:0% and then solidity itself has this Json 00:13:54.600 --> 00:13:56.870 align:start position:0% and then solidity itself has this Json AST<00:13:54.959> import<00:13:55.200> export 00:13:56.870 --> 00:13:56.880 align:start position:0% AST import export 00:13:56.880 --> 00:13:59.690 align:start position:0% AST import export I<00:13:57.300> think<00:13:57.420> some<00:13:57.720> tools<00:13:58.200> like<00:13:58.380> Scribble<00:13:59.220> may<00:13:59.519> be 00:13:59.690 --> 00:13:59.700 align:start position:0% I think some tools like Scribble may be 00:13:59.700 --> 00:14:01.069 align:start position:0% I think some tools like Scribble may be using<00:13:59.940> it 00:14:01.069 --> 00:14:01.079 align:start position:0% using it 00:14:01.079 --> 00:14:02.090 align:start position:0% using it um 00:14:02.090 --> 00:14:02.100 align:start position:0% um 00:14:02.100 --> 00:14:03.829 align:start position:0% um basically<00:14:02.579> you<00:14:02.760> can<00:14:02.880> skip<00:14:03.060> the<00:14:03.240> parser<00:14:03.600> no 00:14:03.829 --> 00:14:03.839 align:start position:0% basically you can skip the parser no 00:14:03.839 --> 00:14:06.110 align:start position:0% basically you can skip the parser no scribble<00:14:04.380> uses<00:14:04.620> a<00:14:04.860> typical<00:14:05.160> parser<00:14:05.639> but<00:14:06.000> yeah 00:14:06.110 --> 00:14:06.120 align:start position:0% scribble uses a typical parser but yeah 00:14:06.120 --> 00:14:07.670 align:start position:0% scribble uses a typical parser but yeah some<00:14:06.360> people<00:14:06.480> we<00:14:06.779> wanted<00:14:06.959> people<00:14:07.260> to<00:14:07.440> use<00:14:07.560> it 00:14:07.670 --> 00:14:07.680 align:start position:0% some people we wanted people to use it 00:14:07.680 --> 00:14:09.170 align:start position:0% some people we wanted people to use it some<00:14:07.860> people<00:14:07.980> use<00:14:08.279> it<00:14:08.399> but<00:14:08.579> they<00:14:08.700> ended<00:14:08.940> up<00:14:09.000> not 00:14:09.170 --> 00:14:09.180 align:start position:0% some people use it but they ended up not 00:14:09.180 --> 00:14:11.750 align:start position:0% some people use it but they ended up not using<00:14:09.480> it<00:14:09.600> at<00:14:10.079> the<00:14:10.260> end 00:14:11.750 --> 00:14:11.760 align:start position:0% using it at the end 00:14:11.760 --> 00:14:14.389 align:start position:0% using it at the end um<00:14:12.300> but<00:14:12.839> the<00:14:13.019> main<00:14:13.139> issue<00:14:13.500> I<00:14:13.740> kind<00:14:13.920> of<00:14:14.040> see<00:14:14.160> here 00:14:14.389 --> 00:14:14.399 align:start position:0% um but the main issue I kind of see here 00:14:14.399 --> 00:14:16.430 align:start position:0% um but the main issue I kind of see here all<00:14:14.880> of<00:14:15.000> this<00:14:15.060> is<00:14:15.240> C<00:14:15.420> plus<00:14:15.540> plus 00:14:16.430 --> 00:14:16.440 align:start position:0% all of this is C plus plus 00:14:16.440 --> 00:14:18.470 align:start position:0% all of this is C plus plus which<00:14:16.920> is<00:14:17.160> kind<00:14:17.339> of<00:14:17.519> hard<00:14:17.760> to<00:14:17.940> integrate<00:14:18.240> with 00:14:18.470 --> 00:14:18.480 align:start position:0% which is kind of hard to integrate with 00:14:18.480 --> 00:14:20.329 align:start position:0% which is kind of hard to integrate with other<00:14:18.660> kind<00:14:18.899> of<00:14:19.019> languages 00:14:20.329 --> 00:14:20.339 align:start position:0% other kind of languages 00:14:20.339 --> 00:14:23.389 align:start position:0% other kind of languages it<00:14:21.060> is<00:14:21.180> hard<00:14:21.300> to<00:14:21.480> integrate<00:14:21.839> with<00:14:22.079> with<00:14:22.680> like 00:14:23.389 --> 00:14:23.399 align:start position:0% it is hard to integrate with with like 00:14:23.399 --> 00:14:25.430 align:start position:0% it is hard to integrate with with like JavaScript<00:14:23.880> we<00:14:24.600> have<00:14:24.720> this<00:14:24.839> m<00:14:25.019> script<00:14:25.320> and 00:14:25.430 --> 00:14:25.440 align:start position:0% JavaScript we have this m script and 00:14:25.440 --> 00:14:27.829 align:start position:0% JavaScript we have this m script and layer<00:14:25.740> and<00:14:25.860> we<00:14:25.980> have<00:14:26.160> the<00:14:26.279> C<00:14:26.459> wrapper<00:14:27.060> it<00:14:27.660> is 00:14:27.829 --> 00:14:27.839 align:start position:0% layer and we have the C wrapper it is 00:14:27.839 --> 00:14:30.350 align:start position:0% layer and we have the C wrapper it is hard<00:14:28.019> to<00:14:28.139> integrate<00:14:28.440> with<00:14:28.620> rust<00:14:29.060> you<00:14:30.060> need<00:14:30.180> to 00:14:30.350 --> 00:14:30.360 align:start position:0% hard to integrate with rust you need to 00:14:30.360 --> 00:14:32.810 align:start position:0% hard to integrate with rust you need to see<00:14:30.480> layer<00:14:30.839> as<00:14:31.019> well<00:14:31.220> although<00:14:32.220> rust<00:14:32.519> does 00:14:32.810 --> 00:14:32.820 align:start position:0% see layer as well although rust does 00:14:32.820 --> 00:14:34.610 align:start position:0% see layer as well although rust does have<00:14:33.000> like<00:14:33.180> a<00:14:33.300> C<00:14:33.420> plus<00:14:33.660> plus<00:14:33.899> binding 00:14:34.610 --> 00:14:34.620 align:start position:0% have like a C plus plus binding 00:14:34.620 --> 00:14:36.889 align:start position:0% have like a C plus plus binding generator<00:14:34.980> it<00:14:35.220> is<00:14:35.399> not<00:14:35.519> really<00:14:35.639> stable<00:14:36.000> if<00:14:36.720> you 00:14:36.889 --> 00:14:36.899 align:start position:0% generator it is not really stable if you 00:14:36.899 --> 00:14:38.509 align:start position:0% generator it is not really stable if you want<00:14:37.019> to<00:14:37.079> integrate<00:14:37.380> this<00:14:37.500> into<00:14:37.680> go<00:14:37.980> it's<00:14:38.339> the 00:14:38.509 --> 00:14:38.519 align:start position:0% want to integrate this into go it's the 00:14:38.519 --> 00:14:40.970 align:start position:0% want to integrate this into go it's the same<00:14:38.700> case<00:14:38.880> all<00:14:39.540> of<00:14:39.720> the<00:14:40.380> all<00:14:40.740> of<00:14:40.920> the 00:14:40.970 --> 00:14:40.980 align:start position:0% same case all of the all of the 00:14:40.980 --> 00:14:42.470 align:start position:0% same case all of the all of the languages<00:14:41.160> they<00:14:41.519> only<00:14:41.639> work<00:14:41.880> with<00:14:42.060> C<00:14:42.240> they 00:14:42.470 --> 00:14:42.480 align:start position:0% languages they only work with C they 00:14:42.480 --> 00:14:46.009 align:start position:0% languages they only work with C they don't<00:14:42.600> work<00:14:42.899> with<00:14:43.019> C<00:14:43.199> plus<00:14:43.380> plus 00:14:46.009 --> 00:14:46.019 align:start position:0% 00:14:46.019 --> 00:14:49.670 align:start position:0% so<00:14:46.860> I<00:14:47.459> have<00:14:47.639> a<00:14:47.820> few<00:14:48.000> you<00:14:48.600> know<00:14:48.720> ideas<00:14:48.899> how<00:14:49.440> could 00:14:49.670 --> 00:14:49.680 align:start position:0% so I have a few you know ideas how could 00:14:49.680 --> 00:14:52.370 align:start position:0% so I have a few you know ideas how could we<00:14:49.800> resolve<00:14:50.279> this<00:14:50.399> and<00:14:51.300> first<00:14:51.720> of<00:14:51.839> all<00:14:51.959> we<00:14:52.139> want 00:14:52.370 --> 00:14:52.380 align:start position:0% we resolve this and first of all we want 00:14:52.380 --> 00:14:54.650 align:start position:0% we resolve this and first of all we want to<00:14:52.500> just<00:14:52.680> improve<00:14:53.220> the<00:14:53.639> the<00:14:54.000> separation<00:14:54.480> of 00:14:54.650 --> 00:14:54.660 align:start position:0% to just improve the the separation of 00:14:54.660 --> 00:14:55.730 align:start position:0% to just improve the the separation of these<00:14:54.779> libraries<00:14:55.079> we<00:14:55.260> want<00:14:55.380> to<00:14:55.500> have<00:14:55.560> like 00:14:55.730 --> 00:14:55.740 align:start position:0% these libraries we want to have like 00:14:55.740 --> 00:14:58.069 align:start position:0% these libraries we want to have like clean<00:14:55.980> interfaces<00:14:56.579> between<00:14:56.760> them<00:14:57.480> and<00:14:57.959> maybe 00:14:58.069 --> 00:14:58.079 align:start position:0% clean interfaces between them and maybe 00:14:58.079 --> 00:14:59.509 align:start position:0% clean interfaces between them and maybe reduce<00:14:58.380> the<00:14:58.740> number<00:14:58.860> of<00:14:58.980> like<00:14:59.100> C<00:14:59.279> plus<00:14:59.459> plus 00:14:59.509 --> 00:14:59.519 align:start position:0% reduce the number of like C plus plus 00:14:59.519 --> 00:15:01.490 align:start position:0% reduce the number of like C plus plus features<00:15:00.120> that<00:15:00.839> the<00:15:01.019> interface<00:15:01.320> they're 00:15:01.490 --> 00:15:01.500 align:start position:0% features that the interface they're 00:15:01.500 --> 00:15:03.350 align:start position:0% features that the interface they're using<00:15:01.860> to<00:15:02.339> make<00:15:02.459> them<00:15:02.639> more<00:15:02.820> compatible<00:15:03.180> with 00:15:03.350 --> 00:15:03.360 align:start position:0% using to make them more compatible with 00:15:03.360 --> 00:15:04.850 align:start position:0% using to make them more compatible with c 00:15:04.850 --> 00:15:04.860 align:start position:0% c 00:15:04.860 --> 00:15:06.110 align:start position:0% c then 00:15:06.110 --> 00:15:06.120 align:start position:0% then 00:15:06.120 --> 00:15:07.970 align:start position:0% then parallel<00:15:06.660> to<00:15:06.839> this<00:15:07.019> because<00:15:07.260> this<00:15:07.620> this<00:15:07.800> can 00:15:07.970 --> 00:15:07.980 align:start position:0% parallel to this because this this can 00:15:07.980 --> 00:15:09.590 align:start position:0% parallel to this because this this can happen<00:15:08.160> on<00:15:08.399> the<00:15:08.519> existing<00:15:08.880> code<00:15:09.060> base<00:15:09.240> prior 00:15:09.590 --> 00:15:09.600 align:start position:0% happen on the existing code base prior 00:15:09.600 --> 00:15:11.449 align:start position:0% happen on the existing code base prior to<00:15:09.720> this<00:15:09.959> we<00:15:10.500> could<00:15:10.680> start<00:15:10.860> working<00:15:11.160> on 00:15:11.449 --> 00:15:11.459 align:start position:0% to this we could start working on 00:15:11.459 --> 00:15:13.550 align:start position:0% to this we could start working on components<00:15:12.120> in<00:15:12.240> Rust 00:15:13.550 --> 00:15:13.560 align:start position:0% components in Rust 00:15:13.560 --> 00:15:15.470 align:start position:0% components in Rust and<00:15:13.800> we<00:15:14.100> in<00:15:14.339> fact<00:15:14.459> already<00:15:14.699> have<00:15:15.060> components 00:15:15.470 --> 00:15:15.480 align:start position:0% and we in fact already have components 00:15:15.480 --> 00:15:16.970 align:start position:0% and we in fact already have components in<00:15:15.600> Rust 00:15:16.970 --> 00:15:16.980 align:start position:0% in Rust 00:15:16.980 --> 00:15:20.269 align:start position:0% in Rust um we<00:15:17.160> have<00:15:17.339> sources<00:15:17.760> rust<00:15:18.199> which<00:15:19.199> is<00:15:19.380> used 00:15:20.269 --> 00:15:20.279 align:start position:0% um we have sources rust which is used 00:15:20.279 --> 00:15:23.269 align:start position:0% um we have sources rust which is used it's<00:15:20.639> used<00:15:20.760> by<00:15:21.000> Faye<00:15:21.360> actually<00:15:21.800> and<00:15:22.800> I<00:15:23.160> think 00:15:23.269 --> 00:15:23.279 align:start position:0% it's used by Faye actually and I think 00:15:23.279 --> 00:15:25.910 align:start position:0% it's used by Faye actually and I think at<00:15:23.459> some<00:15:23.579> point<00:15:23.760> fan<00:15:24.240> reused<00:15:24.779> it<00:15:24.899> but 00:15:25.910 --> 00:15:25.920 align:start position:0% at some point fan reused it but 00:15:25.920 --> 00:15:28.490 align:start position:0% at some point fan reused it but they<00:15:26.399> were<00:15:26.579> annoyed<00:15:26.940> by<00:15:27.060> by<00:15:27.600> the<00:15:27.839> size<00:15:28.139> of<00:15:28.380> the 00:15:28.490 --> 00:15:28.500 align:start position:0% they were annoyed by by the size of the 00:15:28.500 --> 00:15:30.290 align:start position:0% they were annoyed by by the size of the binary<00:15:28.740> and<00:15:28.860> compilation<00:15:29.220> pipeline<00:15:29.639> so<00:15:30.060> that 00:15:30.290 --> 00:15:30.300 align:start position:0% binary and compilation pipeline so that 00:15:30.300 --> 00:15:31.689 align:start position:0% binary and compilation pipeline so that they're<00:15:30.420> not<00:15:30.540> using<00:15:30.839> it<00:15:30.899> anymore 00:15:31.689 --> 00:15:31.699 align:start position:0% they're not using it anymore 00:15:31.699 --> 00:15:34.069 align:start position:0% they're not using it anymore but<00:15:32.699> we<00:15:32.880> do<00:15:33.000> have<00:15:33.120> a<00:15:33.240> bunch<00:15:33.300> of<00:15:33.420> like<00:15:33.540> libraries 00:15:34.069 --> 00:15:34.079 align:start position:0% but we do have a bunch of like libraries 00:15:34.079 --> 00:15:36.769 align:start position:0% but we do have a bunch of like libraries new<00:15:34.620> libraries<00:15:35.100> in<00:15:35.459> Rust<00:15:35.760> which<00:15:36.360> is<00:15:36.480> also<00:15:36.660> used 00:15:36.769 --> 00:15:36.779 align:start position:0% new libraries in Rust which is also used 00:15:36.779 --> 00:15:39.350 align:start position:0% new libraries in Rust which is also used by<00:15:37.019> Faye<00:15:37.440> and<00:15:38.040> some<00:15:38.579> people<00:15:38.760> in<00:15:38.940> the<00:15:39.060> team<00:15:39.180> now 00:15:39.350 --> 00:15:39.360 align:start position:0% by Faye and some people in the team now 00:15:39.360 --> 00:15:42.530 align:start position:0% by Faye and some people in the team now are<00:15:39.540> working<00:15:39.660> on<00:15:40.100> some<00:15:41.100> crazy<00:15:41.339> features<00:15:41.820> on 00:15:42.530 --> 00:15:42.540 align:start position:0% are working on some crazy features on 00:15:42.540 --> 00:15:44.449 align:start position:0% are working on some crazy features on top<00:15:42.600> of<00:15:42.779> it 00:15:44.449 --> 00:15:44.459 align:start position:0% top of it 00:15:44.459 --> 00:15:47.509 align:start position:0% top of it the<00:15:45.240> first<00:15:45.420> useful<00:15:45.779> step<00:15:46.079> could<00:15:46.380> be<00:15:46.620> rewriting 00:15:47.509 --> 00:15:47.519 align:start position:0% the first useful step could be rewriting 00:15:47.519 --> 00:15:49.610 align:start position:0% the first useful step could be rewriting the<00:15:47.639> assembler<00:15:48.480> and<00:15:48.899> the<00:15:49.019> reason<00:15:49.139> behind<00:15:49.500> this 00:15:49.610 --> 00:15:49.620 align:start position:0% the assembler and the reason behind this 00:15:49.620 --> 00:15:51.170 align:start position:0% the assembler and the reason behind this is<00:15:49.800> the<00:15:49.980> assembler<00:15:50.339> is<00:15:50.579> one<00:15:50.699> of<00:15:50.820> the<00:15:50.880> oldest 00:15:51.170 --> 00:15:51.180 align:start position:0% is the assembler is one of the oldest 00:15:51.180 --> 00:15:54.129 align:start position:0% is the assembler is one of the oldest components<00:15:51.660> we<00:15:52.560> actually<00:15:52.740> never<00:15:53.040> changed 00:15:54.129 --> 00:15:54.139 align:start position:0% components we actually never changed 00:15:54.139 --> 00:15:56.569 align:start position:0% components we actually never changed the<00:15:55.139> parser<00:15:55.560> itself<00:15:55.860> has<00:15:56.040> been<00:15:56.220> mostly 00:15:56.569 --> 00:15:56.579 align:start position:0% the parser itself has been mostly 00:15:56.579 --> 00:15:59.030 align:start position:0% the parser itself has been mostly Rewritten<00:15:57.120> or<00:15:57.600> at<00:15:57.779> least<00:15:58.040> significantly 00:15:59.030 --> 00:15:59.040 align:start position:0% Rewritten or at least significantly 00:15:59.040 --> 00:16:00.350 align:start position:0% Rewritten or at least significantly improved 00:16:00.350 --> 00:16:00.360 align:start position:0% improved 00:16:00.360 --> 00:16:01.430 align:start position:0% improved um 00:16:01.430 --> 00:16:01.440 align:start position:0% um 00:16:01.440 --> 00:16:03.769 align:start position:0% um I<00:16:01.680> think<00:16:01.860> the<00:16:02.100> type<00:16:02.339> system<00:16:02.639> that<00:16:03.480> is<00:16:03.660> also 00:16:03.769 --> 00:16:03.779 align:start position:0% I think the type system that is also 00:16:03.779 --> 00:16:06.290 align:start position:0% I think the type system that is also kind<00:16:04.019> of<00:16:04.199> old<00:16:04.320> but<00:16:04.500> it<00:16:04.740> had<00:16:04.920> more<00:16:05.100> maintenance 00:16:06.290 --> 00:16:06.300 align:start position:0% kind of old but it had more maintenance 00:16:06.300 --> 00:16:08.329 align:start position:0% kind of old but it had more maintenance but<00:16:06.720> the<00:16:06.839> assembler<00:16:07.260> that<00:16:07.560> is<00:16:07.740> the<00:16:07.980> oldest 00:16:08.329 --> 00:16:08.339 align:start position:0% but the assembler that is the oldest 00:16:08.339 --> 00:16:10.430 align:start position:0% but the assembler that is the oldest component<00:16:08.760> which<00:16:09.060> has<00:16:09.420> never<00:16:09.660> been 00:16:10.430 --> 00:16:10.440 align:start position:0% component which has never been 00:16:10.440 --> 00:16:12.949 align:start position:0% component which has never been significantly<00:16:11.220> improved<00:16:11.940> on 00:16:12.949 --> 00:16:12.959 align:start position:0% significantly improved on 00:16:12.959 --> 00:16:14.329 align:start position:0% significantly improved on it<00:16:13.019> would<00:16:13.500> be<00:16:13.620> a<00:16:13.740> really<00:16:13.800> good<00:16:13.980> task<00:16:14.100> to 00:16:14.329 --> 00:16:14.339 align:start position:0% it would be a really good task to 00:16:14.339 --> 00:16:18.050 align:start position:0% it would be a really good task to rewrite<00:16:14.639> it<00:16:14.899> and<00:16:15.899> by<00:16:16.680> rewriting<00:16:17.160> it<00:16:17.339> it<00:16:17.760> may<00:16:17.940> or 00:16:18.050 --> 00:16:18.060 align:start position:0% rewrite it and by rewriting it it may or 00:16:18.060 --> 00:16:19.670 align:start position:0% rewrite it and by rewriting it it may or may<00:16:18.240> not<00:16:18.360> even<00:16:18.480> need<00:16:18.720> to<00:16:18.779> be<00:16:18.899> Rewritten<00:16:19.320> by<00:16:19.500> us 00:16:19.670 --> 00:16:19.680 align:start position:0% may not even need to be Rewritten by us 00:16:19.680 --> 00:16:22.310 align:start position:0% may not even need to be Rewritten by us but<00:16:20.220> we<00:16:20.399> could<00:16:20.519> use<00:16:20.699> an<00:16:20.940> existing<00:16:21.300> assembler 00:16:22.310 --> 00:16:22.320 align:start position:0% but we could use an existing assembler 00:16:22.320 --> 00:16:25.430 align:start position:0% but we could use an existing assembler and<00:16:22.920> in<00:16:23.100> fact<00:16:23.639> etk<00:16:24.000> the 00:16:25.430 --> 00:16:25.440 align:start position:0% and in fact etk the 00:16:25.440 --> 00:16:27.350 align:start position:0% and in fact etk the evm 00:16:27.350 --> 00:16:27.360 align:start position:0% evm 00:16:27.360 --> 00:16:29.810 align:start position:0% evm toolkit<00:16:28.079> evm<00:16:28.620> assembly<00:16:28.980> toolkit<00:16:29.399> I<00:16:29.639> don't 00:16:29.810 --> 00:16:29.820 align:start position:0% toolkit evm assembly toolkit I don't 00:16:29.820 --> 00:16:32.509 align:start position:0% toolkit evm assembly toolkit I don't know<00:16:29.940> the<00:16:30.240> what<00:16:30.600> the<00:16:30.959> acronym<00:16:31.380> is<00:16:31.500> for<00:16:31.740> but<00:16:32.399> it 00:16:32.509 --> 00:16:32.519 align:start position:0% know the what the acronym is for but it 00:16:32.519 --> 00:16:34.370 align:start position:0% know the what the acronym is for but it is<00:16:32.639> an<00:16:32.760> assembler<00:16:33.120> toolkit<00:16:33.540> basically<00:16:33.899> for 00:16:34.370 --> 00:16:34.380 align:start position:0% is an assembler toolkit basically for 00:16:34.380 --> 00:16:36.290 align:start position:0% is an assembler toolkit basically for evm<00:16:34.800> it's<00:16:34.920> written<00:16:35.160> in<00:16:35.279> Rust<00:16:35.579> we<00:16:36.000> could<00:16:36.180> just 00:16:36.290 --> 00:16:36.300 align:start position:0% evm it's written in Rust we could just 00:16:36.300 --> 00:16:37.550 align:start position:0% evm it's written in Rust we could just use<00:16:36.480> that 00:16:37.550 --> 00:16:37.560 align:start position:0% use that 00:16:37.560 --> 00:16:39.290 align:start position:0% use that in<00:16:37.920> any<00:16:38.040> case<00:16:38.220> once<00:16:38.519> we<00:16:38.639> have<00:16:38.820> some<00:16:38.940> of<00:16:39.060> these 00:16:39.290 --> 00:16:39.300 align:start position:0% in any case once we have some of these 00:16:39.300 --> 00:16:41.449 align:start position:0% in any case once we have some of these components<00:16:39.720> we<00:16:40.320> could<00:16:40.500> think<00:16:40.680> about<00:16:40.860> creating 00:16:41.449 --> 00:16:41.459 align:start position:0% components we could think about creating 00:16:41.459 --> 00:16:44.329 align:start position:0% components we could think about creating a<00:16:42.060> compiler<00:16:42.660> skeleton<00:16:43.079> so<00:16:43.560> basically<00:16:43.860> just<00:16:44.100> a 00:16:44.329 --> 00:16:44.339 align:start position:0% a compiler skeleton so basically just a 00:16:44.339 --> 00:16:46.850 align:start position:0% a compiler skeleton so basically just a driver<00:16:44.839> which<00:16:45.839> drives<00:16:46.139> the<00:16:46.320> completion 00:16:46.850 --> 00:16:46.860 align:start position:0% driver which drives the completion 00:16:46.860 --> 00:16:47.990 align:start position:0% driver which drives the completion process 00:16:47.990 --> 00:16:48.000 align:start position:0% process 00:16:48.000 --> 00:16:49.430 align:start position:0% process and<00:16:48.360> this<00:16:48.540> doesn't<00:16:48.660> mean<00:16:48.899> that<00:16:49.019> we<00:16:49.139> would<00:16:49.320> need 00:16:49.430 --> 00:16:49.440 align:start position:0% and this doesn't mean that we would need 00:16:49.440 --> 00:16:51.350 align:start position:0% and this doesn't mean that we would need to<00:16:49.620> rewrite<00:16:49.920> the<00:16:50.100> compiler<00:16:50.519> all<00:16:51.060> we<00:16:51.240> would 00:16:51.350 --> 00:16:51.360 align:start position:0% to rewrite the compiler all we would 00:16:51.360 --> 00:16:53.629 align:start position:0% to rewrite the compiler all we would need<00:16:51.540> to<00:16:51.600> do<00:16:51.779> is<00:16:51.959> provide<00:16:52.620> trust<00:16:52.980> bindings<00:16:53.399> to 00:16:53.629 --> 00:16:53.639 align:start position:0% need to do is provide trust bindings to 00:16:53.639 --> 00:16:55.670 align:start position:0% need to do is provide trust bindings to some<00:16:53.820> of<00:16:53.940> those<00:16:54.060> components<00:16:54.600> and<00:16:55.320> then<00:16:55.500> have 00:16:55.670 --> 00:16:55.680 align:start position:0% some of those components and then have 00:16:55.680 --> 00:16:57.290 align:start position:0% some of those components and then have this<00:16:55.860> driver<00:16:56.040> which<00:16:56.399> just<00:16:56.579> uses<00:16:56.880> those 00:16:57.290 --> 00:16:57.300 align:start position:0% this driver which just uses those 00:16:57.300 --> 00:16:59.689 align:start position:0% this driver which just uses those components<00:16:57.779> and<00:16:58.259> once<00:16:58.560> this<00:16:58.680> work<00:16:58.920> it<00:16:59.339> works 00:16:59.689 --> 00:16:59.699 align:start position:0% components and once this work it works 00:16:59.699 --> 00:17:01.370 align:start position:0% components and once this work it works we<00:16:59.940> could<00:17:00.120> swap<00:17:00.480> out<00:17:00.660> parts<00:17:01.019> of<00:17:01.199> those 00:17:01.370 --> 00:17:01.380 align:start position:0% we could swap out parts of those 00:17:01.380 --> 00:17:04.429 align:start position:0% we could swap out parts of those components<00:17:01.860> for<00:17:02.399> example<00:17:02.639> the<00:17:02.880> assembler 00:17:04.429 --> 00:17:04.439 align:start position:0% components for example the assembler 00:17:04.439 --> 00:17:07.069 align:start position:0% components for example the assembler um because<00:17:04.679> they<00:17:04.860> are<00:17:05.040> just<00:17:05.160> components 00:17:07.069 --> 00:17:07.079 align:start position:0% um because they are just components 00:17:07.079 --> 00:17:09.650 align:start position:0% um because they are just components and<00:17:07.559> once<00:17:07.860> this<00:17:08.100> this<00:17:08.280> would<00:17:08.579> be<00:17:08.699> working<00:17:08.880> the 00:17:09.650 --> 00:17:09.660 align:start position:0% and once this this would be working the 00:17:09.660 --> 00:17:12.110 align:start position:0% and once this this would be working the biggest<00:17:09.780> change<00:17:10.400> uh<00:17:11.400> would<00:17:11.760> be<00:17:11.939> actually 00:17:12.110 --> 00:17:12.120 align:start position:0% biggest change uh would be actually 00:17:12.120 --> 00:17:14.569 align:start position:0% biggest change uh would be actually doing<00:17:12.480> a<00:17:13.319> major<00:17:13.439> rewrite<00:17:13.860> of<00:17:14.100> the<00:17:14.280> front<00:17:14.400> end 00:17:14.569 --> 00:17:14.579 align:start position:0% doing a major rewrite of the front end 00:17:14.579 --> 00:17:16.429 align:start position:0% doing a major rewrite of the front end in<00:17:14.880> Rust 00:17:16.429 --> 00:17:16.439 align:start position:0% in Rust 00:17:16.439 --> 00:17:18.110 align:start position:0% in Rust and<00:17:16.740> the<00:17:16.980> front<00:17:17.160> end<00:17:17.280> by<00:17:17.579> the<00:17:17.699> front<00:17:17.819> end<00:17:17.939> I 00:17:18.110 --> 00:17:18.120 align:start position:0% and the front end by the front end I 00:17:18.120 --> 00:17:21.110 align:start position:0% and the front end by the front end I mean<00:17:18.299> mostly<00:17:18.600> the<00:17:18.660> parser<00:17:19.079> the<00:17:19.799> analysis<00:17:20.339> and 00:17:21.110 --> 00:17:21.120 align:start position:0% mean mostly the parser the analysis and 00:17:21.120 --> 00:17:23.569 align:start position:0% mean mostly the parser the analysis and the<00:17:21.360> type<00:17:21.480> system<00:17:22.079> Etc<00:17:22.260> and<00:17:22.919> while<00:17:23.220> the<00:17:23.459> code 00:17:23.569 --> 00:17:23.579 align:start position:0% the type system Etc and while the code 00:17:23.579 --> 00:17:25.010 align:start position:0% the type system Etc and while the code generation<00:17:23.939> is<00:17:24.179> wrong 00:17:25.010 --> 00:17:25.020 align:start position:0% generation is wrong 00:17:25.020 --> 00:17:27.650 align:start position:0% generation is wrong that<00:17:25.439> is<00:17:25.559> an<00:17:25.740> insane<00:17:26.100> project 00:17:27.650 --> 00:17:27.660 align:start position:0% that is an insane project 00:17:27.660 --> 00:17:30.049 align:start position:0% that is an insane project and<00:17:28.199> why<00:17:28.439> would<00:17:28.620> you<00:17:28.740> want<00:17:28.860> to<00:17:28.980> do<00:17:29.040> that<00:17:29.220> well 00:17:30.049 --> 00:17:30.059 align:start position:0% and why would you want to do that well 00:17:30.059 --> 00:17:32.630 align:start position:0% and why would you want to do that well you<00:17:30.780> likely<00:17:31.080> don't<00:17:31.200> want<00:17:31.320> to<00:17:31.440> do<00:17:31.500> it<00:17:31.559> for<00:17:31.679> 1.0 00:17:32.630 --> 00:17:32.640 align:start position:0% you likely don't want to do it for 1.0 00:17:32.640 --> 00:17:34.610 align:start position:0% you likely don't want to do it for 1.0 but<00:17:33.000> you<00:17:33.179> want<00:17:33.299> to<00:17:33.419> do<00:17:33.480> it<00:17:33.600> for<00:17:33.720> something<00:17:33.900> else 00:17:34.610 --> 00:17:34.620 align:start position:0% but you want to do it for something else 00:17:34.620 --> 00:17:36.529 align:start position:0% but you want to do it for something else so<00:17:35.220> what<00:17:35.520> is<00:17:35.640> the<00:17:35.760> reasoning<00:17:36.059> behind<00:17:36.299> all<00:17:36.419> of 00:17:36.529 --> 00:17:36.539 align:start position:0% so what is the reasoning behind all of 00:17:36.539 --> 00:17:37.430 align:start position:0% so what is the reasoning behind all of this 00:17:37.430 --> 00:17:37.440 align:start position:0% this 00:17:37.440 --> 00:17:39.890 align:start position:0% this um the<00:17:38.100> main<00:17:38.220> reason<00:17:38.400> is<00:17:38.700> that<00:17:39.000> we<00:17:39.299> kind<00:17:39.539> of<00:17:39.720> or 00:17:39.890 --> 00:17:39.900 align:start position:0% um the main reason is that we kind of or 00:17:39.900 --> 00:17:42.710 align:start position:0% um the main reason is that we kind of or at<00:17:40.080> least<00:17:40.140> me<00:17:40.380> when<00:17:41.100> I<00:17:41.340> turn<00:17:41.460> solidity<00:17:42.240> all 00:17:42.710 --> 00:17:42.720 align:start position:0% at least me when I turn solidity all 00:17:42.720 --> 00:17:45.289 align:start position:0% at least me when I turn solidity all this<00:17:42.960> code<00:17:43.260> into<00:17:44.039> reusable<00:17:44.640> compiler 00:17:45.289 --> 00:17:45.299 align:start position:0% this code into reusable compiler 00:17:45.299 --> 00:17:46.610 align:start position:0% this code into reusable compiler framework 00:17:46.610 --> 00:17:46.620 align:start position:0% framework 00:17:46.620 --> 00:17:49.789 align:start position:0% framework I<00:17:47.160> want<00:17:47.280> to<00:17:47.520> make<00:17:48.240> sure<00:17:48.480> that<00:17:48.780> all<00:17:49.080> the<00:17:49.320> you 00:17:49.789 --> 00:17:49.799 align:start position:0% I want to make sure that all the you 00:17:49.799 --> 00:17:52.010 align:start position:0% I want to make sure that all the you know<00:17:49.860> the<00:17:50.100> optimization<00:17:50.520> steps<00:17:51.000> we<00:17:51.179> have<00:17:51.360> all 00:17:52.010 --> 00:17:52.020 align:start position:0% know the optimization steps we have all 00:17:52.020 --> 00:17:53.210 align:start position:0% know the optimization steps we have all of<00:17:52.140> these<00:17:52.320> features<00:17:52.620> they're<00:17:52.860> not<00:17:53.100> just 00:17:53.210 --> 00:17:53.220 align:start position:0% of these features they're not just 00:17:53.220 --> 00:17:55.010 align:start position:0% of these features they're not just wasted<00:17:53.640> they're<00:17:54.240> not<00:17:54.480> just<00:17:54.600> there<00:17:54.840> for 00:17:55.010 --> 00:17:55.020 align:start position:0% wasted they're not just there for 00:17:55.020 --> 00:17:56.930 align:start position:0% wasted they're not just there for solidity<00:17:55.559> but<00:17:55.980> they<00:17:56.160> can<00:17:56.280> be<00:17:56.400> used<00:17:56.580> by<00:17:56.820> other 00:17:56.930 --> 00:17:56.940 align:start position:0% solidity but they can be used by other 00:17:56.940 --> 00:17:57.950 align:start position:0% solidity but they can be used by other languages 00:17:57.950 --> 00:17:57.960 align:start position:0% languages 00:17:57.960 --> 00:17:59.690 align:start position:0% languages imagine<00:17:58.380> if<00:17:58.679> we<00:17:58.799> would<00:17:58.980> have<00:17:59.160> had<00:17:59.340> like<00:17:59.520> this 00:17:59.690 --> 00:17:59.700 align:start position:0% imagine if we would have had like this 00:17:59.700 --> 00:18:01.610 align:start position:0% imagine if we would have had like this compiler<00:18:00.120> framework<00:18:00.419> earlier<00:18:00.840> on<00:18:00.960> you<00:18:01.559> know 00:18:01.610 --> 00:18:01.620 align:start position:0% compiler framework earlier on you know 00:18:01.620 --> 00:18:04.730 align:start position:0% compiler framework earlier on you know it<00:18:01.919> came<00:18:02.100> to<00:18:02.280> like<00:18:02.400> llvm4<00:18:03.179> evm 00:18:04.730 --> 00:18:04.740 align:start position:0% it came to like llvm4 evm 00:18:04.740 --> 00:18:06.529 align:start position:0% it came to like llvm4 evm you<00:18:05.280> know<00:18:05.400> how<00:18:05.700> how<00:18:05.700> long<00:18:06.059> would<00:18:06.240> it<00:18:06.360> have 00:18:06.529 --> 00:18:06.539 align:start position:0% you know how how long would it have 00:18:06.539 --> 00:18:09.950 align:start position:0% you know how how long would it have taken<00:18:06.840> to<00:18:07.140> Forfeit<00:18:08.100> to<00:18:08.940> to<00:18:09.240> come<00:18:09.480> to<00:18:09.720> fruition 00:18:09.950 --> 00:18:09.960 align:start position:0% taken to Forfeit to to come to fruition 00:18:09.960 --> 00:18:11.810 align:start position:0% taken to Forfeit to to come to fruition or<00:18:10.500> like<00:18:10.679> half<00:18:10.980> for<00:18:11.220> any<00:18:11.460> of<00:18:11.580> these<00:18:11.700> other 00:18:11.810 --> 00:18:11.820 align:start position:0% or like half for any of these other 00:18:11.820 --> 00:18:13.970 align:start position:0% or like half for any of these other languages<00:18:12.179> if<00:18:12.660> you<00:18:12.780> could<00:18:12.900> just<00:18:13.140> use<00:18:13.320> any<00:18:13.860> of 00:18:13.970 --> 00:18:13.980 align:start position:0% languages if you could just use any of 00:18:13.980 --> 00:18:16.610 align:start position:0% languages if you could just use any of these<00:18:14.220> components<00:18:14.640> I<00:18:15.240> listed<00:18:15.600> a<00:18:15.720> bunch<00:18:15.840> of 00:18:16.610 --> 00:18:16.620 align:start position:0% these components I listed a bunch of 00:18:16.620 --> 00:18:18.890 align:start position:0% these components I listed a bunch of different<00:18:17.039> projects<00:18:17.580> which<00:18:17.820> are<00:18:17.940> already<00:18:18.120> in 00:18:18.890 --> 00:18:18.900 align:start position:0% different projects which are already in 00:18:18.900 --> 00:18:21.830 align:start position:0% different projects which are already in the<00:18:18.960> evm<00:18:19.320> space<00:18:19.500> working<00:18:20.039> on<00:18:20.280> Rust<00:18:20.840> compiler 00:18:21.830 --> 00:18:21.840 align:start position:0% the evm space working on Rust compiler 00:18:21.840 --> 00:18:24.470 align:start position:0% the evm space working on Rust compiler components<00:18:22.320> so<00:18:22.740> of<00:18:22.919> course<00:18:23.039> we<00:18:23.280> have<00:18:23.400> fa<00:18:23.700> we 00:18:24.470 --> 00:18:24.480 align:start position:0% components so of course we have fa we 00:18:24.480 --> 00:18:26.710 align:start position:0% components so of course we have fa we have<00:18:24.600> the<00:18:24.720> two<00:18:24.900> other<00:18:25.080> solidity 00:18:26.710 --> 00:18:26.720 align:start position:0% have the two other solidity 00:18:26.720 --> 00:18:29.450 align:start position:0% have the two other solidity compiler<00:18:27.720> slash<00:18:28.080> parsers 00:18:29.450 --> 00:18:29.460 align:start position:0% compiler slash parsers 00:18:29.460 --> 00:18:31.070 align:start position:0% compiler slash parsers so<00:18:29.820> solang 00:18:31.070 --> 00:18:31.080 align:start position:0% so solang 00:18:31.080 --> 00:18:34.490 align:start position:0% so solang solank<00:18:31.620> is<00:18:31.860> a<00:18:32.100> full<00:18:32.520> featured<00:18:33.000> compiler<00:18:33.660> from 00:18:34.490 --> 00:18:34.500 align:start position:0% solank is a full featured compiler from 00:18:34.500 --> 00:18:37.789 align:start position:0% solank is a full featured compiler from solidity<00:18:35.100> to<00:18:35.820> webassembly<00:18:36.660> targets<00:18:37.320> well 00:18:37.789 --> 00:18:37.799 align:start position:0% solidity to webassembly targets well 00:18:37.799 --> 00:18:39.529 align:start position:0% solidity to webassembly targets well actually<00:18:38.039> llvm<00:18:38.700> targets<00:18:39.059> they<00:18:39.179> started<00:18:39.419> with 00:18:39.529 --> 00:18:39.539 align:start position:0% actually llvm targets they started with 00:18:39.539 --> 00:18:41.049 align:start position:0% actually llvm targets they started with webassembly<00:18:40.080> but<00:18:40.200> they<00:18:40.320> also<00:18:40.559> support<00:18:40.740> like 00:18:41.049 --> 00:18:41.059 align:start position:0% webassembly but they also support like 00:18:41.059 --> 00:18:44.150 align:start position:0% webassembly but they also support like BPF<00:18:42.059> like<00:18:42.480> Solana<00:18:42.960> and<00:18:43.620> a<00:18:43.799> bunch<00:18:43.919> of<00:18:44.039> other 00:18:44.150 --> 00:18:44.160 align:start position:0% BPF like Solana and a bunch of other 00:18:44.160 --> 00:18:45.169 align:start position:0% BPF like Solana and a bunch of other targets 00:18:45.169 --> 00:18:45.179 align:start position:0% targets 00:18:45.179 --> 00:18:47.750 align:start position:0% targets the<00:18:45.600> one<00:18:45.780> thing<00:18:45.900> they<00:18:46.020> don't<00:18:46.200> support<00:18:46.320> is<00:18:46.500> evm 00:18:47.750 --> 00:18:47.760 align:start position:0% the one thing they don't support is evm 00:18:47.760 --> 00:18:50.810 align:start position:0% the one thing they don't support is evm and<00:18:48.299> in<00:18:48.480> fact<00:18:48.660> solang<00:18:49.679> I<00:18:50.160> believe<00:18:50.280> is<00:18:50.460> used<00:18:50.640> by 00:18:50.810 --> 00:18:50.820 align:start position:0% and in fact solang I believe is used by 00:18:50.820 --> 00:18:53.090 align:start position:0% and in fact solang I believe is used by Foundry<00:18:51.240> for<00:18:51.720> parsing<00:18:52.140> solidity<00:18:52.620> because 00:18:53.090 --> 00:18:53.100 align:start position:0% Foundry for parsing solidity because 00:18:53.100 --> 00:18:55.250 align:start position:0% Foundry for parsing solidity because it's<00:18:53.340> in<00:18:53.460> Rust<00:18:54.240> so<00:18:54.600> they're<00:18:54.780> not<00:18:54.900> using 00:18:55.250 --> 00:18:55.260 align:start position:0% it's in Rust so they're not using 00:18:55.260 --> 00:18:57.549 align:start position:0% it's in Rust so they're not using solidity<00:18:56.100> solidity 00:18:57.549 --> 00:18:57.559 align:start position:0% solidity solidity 00:18:57.559 --> 00:19:00.230 align:start position:0% solidity solidity s-lang<00:18:58.559> is<00:18:58.679> a<00:18:58.799> project<00:18:58.860> by<00:18:59.160> hardhead<00:18:59.580> they're 00:19:00.230 --> 00:19:00.240 align:start position:0% s-lang is a project by hardhead they're 00:19:00.240 --> 00:19:03.529 align:start position:0% s-lang is a project by hardhead they're trying<00:19:00.480> to<00:19:00.720> write<00:19:01.080> a<00:19:01.620> compiler<00:19:02.520> as<00:19:02.700> well<00:19:02.820> the 00:19:03.529 --> 00:19:03.539 align:start position:0% trying to write a compiler as well the 00:19:03.539 --> 00:19:05.810 align:start position:0% trying to write a compiler as well the motivation<00:19:03.900> is<00:19:04.140> slightly<00:19:04.440> different<00:19:04.820> they 00:19:05.810 --> 00:19:05.820 align:start position:0% motivation is slightly different they 00:19:05.820 --> 00:19:08.390 align:start position:0% motivation is slightly different they want<00:19:06.539> to<00:19:06.720> have<00:19:07.020> a<00:19:07.320> person<00:19:07.500> which<00:19:07.919> is<00:19:08.039> flexible 00:19:08.390 --> 00:19:08.400 align:start position:0% want to have a person which is flexible 00:19:08.400 --> 00:19:10.190 align:start position:0% want to have a person which is flexible and<00:19:09.000> supports<00:19:09.360> every<00:19:09.600> single<00:19:09.840> version<00:19:09.960> of 00:19:10.190 --> 00:19:10.200 align:start position:0% and supports every single version of 00:19:10.200 --> 00:19:13.250 align:start position:0% and supports every single version of solidity<00:19:11.039> because<00:19:11.700> they<00:19:12.299> want<00:19:12.539> they<00:19:13.200> don't 00:19:13.250 --> 00:19:13.260 align:start position:0% solidity because they want they don't 00:19:13.260 --> 00:19:15.590 align:start position:0% solidity because they want they don't want<00:19:13.380> to<00:19:13.500> like<00:19:13.620> certify<00:19:14.039> the<00:19:14.160> compiler<00:19:14.640> you 00:19:15.590 --> 00:19:15.600 align:start position:0% want to like certify the compiler you 00:19:15.600 --> 00:19:18.049 align:start position:0% want to like certify the compiler you know<00:19:15.660> mid<00:19:15.840> compilation<00:19:16.820> and<00:19:17.820> that's<00:19:17.940> the 00:19:18.049 --> 00:19:18.059 align:start position:0% know mid compilation and that's the 00:19:18.059 --> 00:19:19.669 align:start position:0% know mid compilation and that's the problem<00:19:18.240> with<00:19:18.419> the<00:19:18.539> color<00:19:18.660> and<00:19:18.900> compiler<00:19:19.260> it 00:19:19.669 --> 00:19:19.679 align:start position:0% problem with the color and compiler it 00:19:19.679 --> 00:19:22.549 align:start position:0% problem with the color and compiler it only<00:19:19.799> supports<00:19:20.160> a<00:19:20.280> single<00:19:20.520> version 00:19:22.549 --> 00:19:22.559 align:start position:0% only supports a single version 00:19:22.559 --> 00:19:24.890 align:start position:0% only supports a single version so<00:19:23.100> why<00:19:23.340> would<00:19:23.520> we<00:19:23.700> want<00:19:23.820> to<00:19:23.940> do<00:19:24.059> this 00:19:24.890 --> 00:19:24.900 align:start position:0% so why would we want to do this 00:19:24.900 --> 00:19:27.470 align:start position:0% so why would we want to do this because<00:19:25.320> I<00:19:25.919> want<00:19:26.039> to<00:19:26.160> attract<00:19:26.400> more<00:19:26.580> people 00:19:27.470 --> 00:19:27.480 align:start position:0% because I want to attract more people 00:19:27.480 --> 00:19:30.289 align:start position:0% because I want to attract more people to<00:19:28.140> solely<00:19:28.620> compiler<00:19:29.039> development<00:19:29.460> and<00:19:30.179> it 00:19:30.289 --> 00:19:30.299 align:start position:0% to solely compiler development and it 00:19:30.299 --> 00:19:32.090 align:start position:0% to solely compiler development and it seems<00:19:30.539> like<00:19:30.600> C<00:19:30.780> plus<00:19:30.960> plus<00:19:31.200> is<00:19:31.440> not<00:19:31.559> like<00:19:31.799> a 00:19:32.090 --> 00:19:32.100 align:start position:0% seems like C plus plus is not like a 00:19:32.100 --> 00:19:34.250 align:start position:0% seems like C plus plus is not like a language<00:19:32.400> people<00:19:32.760> like<00:19:33.059> or<00:19:33.840> people<00:19:34.080> are 00:19:34.250 --> 00:19:34.260 align:start position:0% language people like or people are 00:19:34.260 --> 00:19:35.270 align:start position:0% language people like or people are interested<00:19:34.620> in 00:19:35.270 --> 00:19:35.280 align:start position:0% interested in 00:19:35.280 --> 00:19:37.370 align:start position:0% interested in it<00:19:35.640> has<00:19:35.760> been<00:19:35.880> kind<00:19:36.059> of<00:19:36.120> hard<00:19:36.299> to<00:19:36.600> attract 00:19:37.370 --> 00:19:37.380 align:start position:0% it has been kind of hard to attract 00:19:37.380 --> 00:19:40.190 align:start position:0% it has been kind of hard to attract people<00:19:37.559> to<00:19:37.919> to<00:19:38.400> write<00:19:38.640> C<00:19:38.880> plus<00:19:39.059> plus<00:19:39.059> code<00:19:39.539> and 00:19:40.190 --> 00:19:40.200 align:start position:0% people to to write C plus plus code and 00:19:40.200 --> 00:19:41.750 align:start position:0% people to to write C plus plus code and it<00:19:40.380> seems<00:19:40.559> like<00:19:40.679> trust<00:19:41.100> is<00:19:41.280> extremely 00:19:41.750 --> 00:19:41.760 align:start position:0% it seems like trust is extremely 00:19:41.760 --> 00:19:43.150 align:start position:0% it seems like trust is extremely thriving 00:19:43.150 --> 00:19:43.160 align:start position:0% thriving 00:19:43.160 --> 00:19:46.610 align:start position:0% thriving every<00:19:44.160> other<00:19:44.400> project<00:19:44.700> is<00:19:44.940> in<00:19:45.120> Rust<00:19:45.440> I've<00:19:46.440> been 00:19:46.610 --> 00:19:46.620 align:start position:0% every other project is in Rust I've been 00:19:46.620 --> 00:19:49.070 align:start position:0% every other project is in Rust I've been using<00:19:46.799> rust<00:19:47.039> for<00:19:47.220> a<00:19:47.280> long<00:19:47.340> time<00:19:47.520> so<00:19:48.419> I<00:19:48.900> would<00:19:48.960> be 00:19:49.070 --> 00:19:49.080 align:start position:0% using rust for a long time so I would be 00:19:49.080 --> 00:19:51.049 align:start position:0% using rust for a long time so I would be happy<00:19:49.200> for<00:19:49.440> this<00:19:49.620> to<00:19:49.740> happen 00:19:51.049 --> 00:19:51.059 align:start position:0% happy for this to happen 00:19:51.059 --> 00:19:53.330 align:start position:0% happy for this to happen and<00:19:51.600> if<00:19:51.780> you<00:19:51.900> do<00:19:52.080> some<00:19:52.320> kind<00:19:52.440> of<00:19:52.620> a 00:19:53.330 --> 00:19:53.340 align:start position:0% and if you do some kind of a 00:19:53.340 --> 00:19:55.250 align:start position:0% and if you do some kind of a re-architecting<00:19:54.179> like<00:19:54.419> this 00:19:55.250 --> 00:19:55.260 align:start position:0% re-architecting like this 00:19:55.260 --> 00:19:56.690 align:start position:0% re-architecting like this that<00:19:55.799> would<00:19:55.980> mean<00:19:56.160> that<00:19:56.280> we<00:19:56.460> have<00:19:56.580> an 00:19:56.690 --> 00:19:56.700 align:start position:0% that would mean that we have an 00:19:56.700 --> 00:19:59.270 align:start position:0% that would mean that we have an opportunity<00:19:57.059> to<00:19:57.419> actually<00:19:57.600> improve<00:19:58.559> the 00:19:59.270 --> 00:19:59.280 align:start position:0% opportunity to actually improve the 00:19:59.280 --> 00:20:01.549 align:start position:0% opportunity to actually improve the architecture<00:19:59.820> of<00:20:00.120> the<00:20:00.240> compiler<00:20:01.020> and<00:20:01.440> maybe 00:20:01.549 --> 00:20:01.559 align:start position:0% architecture of the compiler and maybe 00:20:01.559 --> 00:20:04.070 align:start position:0% architecture of the compiler and maybe improve<00:20:01.919> the<00:20:02.039> language<00:20:02.220> itself<00:20:03.120> so<00:20:03.600> that<00:20:03.720> is 00:20:04.070 --> 00:20:04.080 align:start position:0% improve the language itself so that is 00:20:04.080 --> 00:20:05.870 align:start position:0% improve the language itself so that is the<00:20:04.260> next<00:20:04.620> one<00:20:04.740> I'm<00:20:04.919> going<00:20:05.039> to<00:20:05.160> talk<00:20:05.280> about<00:20:05.400> is 00:20:05.870 --> 00:20:05.880 align:start position:0% the next one I'm going to talk about is 00:20:05.880 --> 00:20:07.789 align:start position:0% the next one I'm going to talk about is what<00:20:06.660> kind<00:20:06.840> of<00:20:06.900> language<00:20:07.020> could<00:20:07.320> we<00:20:07.500> have<00:20:07.620> here 00:20:07.789 --> 00:20:07.799 align:start position:0% what kind of language could we have here 00:20:07.799 --> 00:20:10.669 align:start position:0% what kind of language could we have here you're<00:20:08.580> really<00:20:08.820> surprised<00:20:09.360> or<00:20:09.960> not 00:20:10.669 --> 00:20:10.679 align:start position:0% you're really surprised or not 00:20:10.679 --> 00:20:13.070 align:start position:0% you're really surprised or not but<00:20:11.280> the<00:20:11.700> fact<00:20:11.880> is<00:20:12.120> we<00:20:12.299> have<00:20:12.480> been<00:20:12.660> talking<00:20:12.780> it 00:20:13.070 --> 00:20:13.080 align:start position:0% but the fact is we have been talking it 00:20:13.080 --> 00:20:14.510 align:start position:0% but the fact is we have been talking it like<00:20:13.200> this 00:20:14.510 --> 00:20:14.520 align:start position:0% like this 00:20:14.520 --> 00:20:17.330 align:start position:0% like this um<00:20:14.580> you<00:20:15.120> know<00:20:15.179> rust<00:20:15.740> inspired<00:20:16.740> changes<00:20:17.100> to<00:20:17.220> the 00:20:17.330 --> 00:20:17.340 align:start position:0% um you know rust inspired changes to the 00:20:17.340 --> 00:20:20.510 align:start position:0% um you know rust inspired changes to the language<00:20:17.460> since<00:20:17.820> 2019<00:20:18.919> way<00:20:19.919> before<00:20:20.100> some<00:20:20.400> of 00:20:20.510 --> 00:20:20.520 align:start position:0% language since 2019 way before some of 00:20:20.520 --> 00:20:23.029 align:start position:0% language since 2019 way before some of these<00:20:20.640> are<00:20:20.760> arrest<00:20:21.020> inspired<00:20:22.020> evm<00:20:22.740> languages 00:20:23.029 --> 00:20:23.039 align:start position:0% these are arrest inspired evm languages 00:20:23.039 --> 00:20:24.169 align:start position:0% these are arrest inspired evm languages came<00:20:23.340> about 00:20:24.169 --> 00:20:24.179 align:start position:0% came about 00:20:24.179 --> 00:20:26.150 align:start position:0% came about oh<00:20:24.600> it's<00:20:24.720> actually<00:20:24.840> another<00:20:25.020> sign 00:20:26.150 --> 00:20:26.160 align:start position:0% oh it's actually another sign 00:20:26.160 --> 00:20:28.669 align:start position:0% oh it's actually another sign um<00:20:26.220> I<00:20:26.700> think<00:20:26.820> the<00:20:26.940> main<00:20:27.120> motivations<00:20:28.020> the<00:20:28.559> main 00:20:28.669 --> 00:20:28.679 align:start position:0% um I think the main motivations the main 00:20:28.679 --> 00:20:30.730 align:start position:0% um I think the main motivations the main reasons<00:20:29.039> those<00:20:29.280> discussions<00:20:29.940> were<00:20:30.240> started 00:20:30.730 --> 00:20:30.740 align:start position:0% reasons those discussions were started 00:20:30.740 --> 00:20:34.130 align:start position:0% reasons those discussions were started because<00:20:31.740> there<00:20:32.039> are<00:20:32.160> a<00:20:32.220> few<00:20:32.340> issues<00:20:33.140> in 00:20:34.130 --> 00:20:34.140 align:start position:0% because there are a few issues in 00:20:34.140 --> 00:20:36.770 align:start position:0% because there are a few issues in solidity<00:20:34.559> itself<00:20:34.919> or<00:20:35.820> at<00:20:36.000> least<00:20:36.120> a<00:20:36.299> few<00:20:36.419> issues 00:20:36.770 --> 00:20:36.780 align:start position:0% solidity itself or at least a few issues 00:20:36.780 --> 00:20:39.289 align:start position:0% solidity itself or at least a few issues I<00:20:37.080> think<00:20:37.260> should<00:20:38.039> be<00:20:38.220> at<00:20:38.400> rest 00:20:39.289 --> 00:20:39.299 align:start position:0% I think should be at rest 00:20:39.299 --> 00:20:42.049 align:start position:0% I think should be at rest one<00:20:40.260> of<00:20:40.320> them<00:20:40.440> is<00:20:40.620> really<00:20:40.799> the<00:20:41.160> storage<00:20:41.760> and 00:20:42.049 --> 00:20:42.059 align:start position:0% one of them is really the storage and 00:20:42.059 --> 00:20:44.390 align:start position:0% one of them is really the storage and implementation<00:20:42.539> itself<00:20:42.900> is<00:20:43.440> not<00:20:44.220> really 00:20:44.390 --> 00:20:44.400 align:start position:0% implementation itself is not really 00:20:44.400 --> 00:20:46.130 align:start position:0% implementation itself is not really separated<00:20:44.880> so<00:20:45.360> the<00:20:45.600> other<00:20:45.720> thing<00:20:45.840> we<00:20:45.960> have 00:20:46.130 --> 00:20:46.140 align:start position:0% separated so the other thing we have 00:20:46.140 --> 00:20:48.770 align:start position:0% separated so the other thing we have right<00:20:46.260> now<00:20:46.440> is<00:20:46.620> this<00:20:46.919> contract<00:20:47.280> construct<00:20:48.000> it 00:20:48.770 --> 00:20:48.780 align:start position:0% right now is this contract construct it 00:20:48.780 --> 00:20:51.650 align:start position:0% right now is this contract construct it can<00:20:48.900> have<00:20:49.200> storage<00:20:49.740> defined<00:20:50.520> anywhere<00:20:50.880> it<00:20:51.480> can 00:20:51.650 --> 00:20:51.660 align:start position:0% can have storage defined anywhere it can 00:20:51.660 --> 00:20:53.390 align:start position:0% can have storage defined anywhere it can functions<00:20:52.080> defined<00:20:52.440> anywhere 00:20:53.390 --> 00:20:53.400 align:start position:0% functions defined anywhere 00:20:53.400 --> 00:20:55.669 align:start position:0% functions defined anywhere it<00:20:54.000> can<00:20:54.179> inherit<00:20:54.660> other<00:20:54.840> contracts<00:20:55.380> which 00:20:55.669 --> 00:20:55.679 align:start position:0% it can inherit other contracts which 00:20:55.679 --> 00:20:57.590 align:start position:0% it can inherit other contracts which also<00:20:56.100> Define<00:20:56.400> storage<00:20:56.820> and<00:20:57.179> functions 00:20:57.590 --> 00:20:57.600 align:start position:0% also Define storage and functions 00:20:57.600 --> 00:20:58.490 align:start position:0% also Define storage and functions anywhere 00:20:58.490 --> 00:20:58.500 align:start position:0% anywhere 00:20:58.500 --> 00:21:00.710 align:start position:0% anywhere and<00:20:58.980> you<00:20:59.100> never<00:20:59.220> know<00:20:59.460> where<00:20:59.580> storage<00:20:59.820> is<00:21:00.120> it 00:21:00.710 --> 00:21:00.720 align:start position:0% and you never know where storage is it 00:21:00.720 --> 00:21:02.090 align:start position:0% and you never know where storage is it could<00:21:00.900> be<00:21:01.020> handled<00:21:01.380> by<00:21:01.559> any<00:21:01.679> of<00:21:01.860> these 00:21:02.090 --> 00:21:02.100 align:start position:0% could be handled by any of these 00:21:02.100 --> 00:21:04.070 align:start position:0% could be handled by any of these imported<00:21:02.640> libraries<00:21:03.000> it<00:21:03.539> would<00:21:03.660> be<00:21:03.840> nice<00:21:03.900> to 00:21:04.070 --> 00:21:04.080 align:start position:0% imported libraries it would be nice to 00:21:04.080 --> 00:21:05.570 align:start position:0% imported libraries it would be nice to actually<00:21:04.200> make<00:21:04.440> this<00:21:04.620> more<00:21:04.799> clear 00:21:05.570 --> 00:21:05.580 align:start position:0% actually make this more clear 00:21:05.580 --> 00:21:08.150 align:start position:0% actually make this more clear the<00:21:06.000> other<00:21:06.059> thing<00:21:06.299> would<00:21:06.539> be<00:21:06.720> nice<00:21:06.960> to<00:21:07.440> kind<00:21:08.039> of 00:21:08.150 --> 00:21:08.160 align:start position:0% the other thing would be nice to kind of 00:21:08.160 --> 00:21:10.850 align:start position:0% the other thing would be nice to kind of make<00:21:08.220> clear<00:21:08.460> when<00:21:08.820> State<00:21:09.179> changes<00:21:10.020> or<00:21:10.620> state 00:21:10.850 --> 00:21:10.860 align:start position:0% make clear when State changes or state 00:21:10.860 --> 00:21:12.529 align:start position:0% make clear when State changes or state access<00:21:11.160> can<00:21:11.520> happen 00:21:12.529 --> 00:21:12.539 align:start position:0% access can happen 00:21:12.539 --> 00:21:13.909 align:start position:0% access can happen we<00:21:12.900> do<00:21:13.020> have<00:21:13.140> some<00:21:13.260> of<00:21:13.380> this<00:21:13.500> in<00:21:13.679> the<00:21:13.799> language 00:21:13.909 --> 00:21:13.919 align:start position:0% we do have some of this in the language 00:21:13.919 --> 00:21:14.990 align:start position:0% we do have some of this in the language today 00:21:14.990 --> 00:21:15.000 align:start position:0% today 00:21:15.000 --> 00:21:16.909 align:start position:0% today um<00:21:15.059> you<00:21:15.179> know<00:21:15.299> via<00:21:15.600> payable<00:21:15.960> we<00:21:16.320> have<00:21:16.559> View<00:21:16.679> and 00:21:16.909 --> 00:21:16.919 align:start position:0% um you know via payable we have View and 00:21:16.919 --> 00:21:19.669 align:start position:0% um you know via payable we have View and pure<00:21:17.100> functions<00:21:17.640> but<00:21:18.419> that's<00:21:18.660> about<00:21:18.840> it<00:21:19.140> it 00:21:19.669 --> 00:21:19.679 align:start position:0% pure functions but that's about it it 00:21:19.679 --> 00:21:21.049 align:start position:0% pure functions but that's about it it would<00:21:19.860> be<00:21:19.980> nice<00:21:20.160> to<00:21:20.280> you<00:21:20.400> to<00:21:20.520> have<00:21:20.640> like<00:21:20.820> more 00:21:21.049 --> 00:21:21.059 align:start position:0% would be nice to you to have like more 00:21:21.059 --> 00:21:24.409 align:start position:0% would be nice to you to have like more clarity<00:21:21.780> even<00:21:22.140> within<00:21:22.980> the<00:21:23.100> functions<00:21:23.640> when 00:21:24.409 --> 00:21:24.419 align:start position:0% clarity even within the functions when 00:21:24.419 --> 00:21:26.630 align:start position:0% clarity even within the functions when is<00:21:24.720> a<00:21:24.900> state<00:21:24.960> change<00:21:25.260> taking<00:21:25.559> place 00:21:26.630 --> 00:21:26.640 align:start position:0% is a state change taking place 00:21:26.640 --> 00:21:29.870 align:start position:0% is a state change taking place functions<00:21:27.480> can<00:21:27.720> be<00:21:27.960> quite<00:21:28.200> long<00:21:28.580> I<00:21:29.580> think<00:21:29.700> good 00:21:29.870 --> 00:21:29.880 align:start position:0% functions can be quite long I think good 00:21:29.880 --> 00:21:32.390 align:start position:0% functions can be quite long I think good code<00:21:30.059> bases<00:21:30.539> started<00:21:30.900> to 00:21:32.390 --> 00:21:32.400 align:start position:0% code bases started to 00:21:32.400 --> 00:21:35.330 align:start position:0% code bases started to create<00:21:32.880> small<00:21:33.240> helpers<00:21:33.720> and<00:21:34.500> limit<00:21:34.740> the<00:21:35.159> scope 00:21:35.330 --> 00:21:35.340 align:start position:0% create small helpers and limit the scope 00:21:35.340 --> 00:21:37.430 align:start position:0% create small helpers and limit the scope of<00:21:35.580> like<00:21:35.820> State<00:21:36.419> changes<00:21:36.840> to<00:21:36.960> those<00:21:37.080> smaller 00:21:37.430 --> 00:21:37.440 align:start position:0% of like State changes to those smaller 00:21:37.440 --> 00:21:39.710 align:start position:0% of like State changes to those smaller helpers<00:21:37.799> but<00:21:38.640> it's<00:21:38.760> still<00:21:38.940> people<00:21:39.240> can<00:21:39.480> write 00:21:39.710 --> 00:21:39.720 align:start position:0% helpers but it's still people can write 00:21:39.720 --> 00:21:41.270 align:start position:0% helpers but it's still people can write no<00:21:40.260> matter<00:21:40.380> what<00:21:40.559> you<00:21:40.679> do<00:21:40.799> people<00:21:40.980> can<00:21:41.159> write 00:21:41.270 --> 00:21:41.280 align:start position:0% no matter what you do people can write 00:21:41.280 --> 00:21:42.890 align:start position:0% no matter what you do people can write really<00:21:41.460> bad<00:21:41.640> code<00:21:41.880> but<00:21:42.299> in<00:21:42.480> solidity 00:21:42.890 --> 00:21:42.900 align:start position:0% really bad code but in solidity 00:21:42.900 --> 00:21:44.810 align:start position:0% really bad code but in solidity especially<00:21:43.320> people<00:21:43.559> can<00:21:43.799> write<00:21:43.980> like<00:21:44.220> giant 00:21:44.810 --> 00:21:44.820 align:start position:0% especially people can write like giant 00:21:44.820 --> 00:21:46.430 align:start position:0% especially people can write like giant pieces<00:21:45.120> of<00:21:45.240> coding<00:21:45.539> would<00:21:45.720> be<00:21:45.840> nice<00:21:46.020> to<00:21:46.260> have 00:21:46.430 --> 00:21:46.440 align:start position:0% pieces of coding would be nice to have 00:21:46.440 --> 00:21:49.250 align:start position:0% pieces of coding would be nice to have like<00:21:46.740> Clear<00:21:47.220> View<00:21:47.520> whereas<00:21:48.179> State<00:21:48.780> access<00:21:49.020> and 00:21:49.250 --> 00:21:49.260 align:start position:0% like Clear View whereas State access and 00:21:49.260 --> 00:21:52.190 align:start position:0% like Clear View whereas State access and state<00:21:49.500> modification<00:21:50.039> taking<00:21:50.280> place 00:21:52.190 --> 00:21:52.200 align:start position:0% state modification taking place 00:21:52.200 --> 00:21:54.289 align:start position:0% state modification taking place and<00:21:52.620> lastly<00:21:52.919> if<00:21:53.100> we<00:21:53.340> you<00:21:53.520> know<00:21:53.640> take<00:21:53.880> such<00:21:54.120> a 00:21:54.289 --> 00:21:54.299 align:start position:0% and lastly if we you know take such a 00:21:54.299 --> 00:21:55.549 align:start position:0% and lastly if we you know take such a big<00:21:54.419> step 00:21:55.549 --> 00:21:55.559 align:start position:0% big step 00:21:55.559 --> 00:21:57.830 align:start position:0% big step um<00:21:56.039> we<00:21:56.400> could<00:21:56.520> even<00:21:56.640> consider 00:21:57.830 --> 00:21:57.840 align:start position:0% um we could even consider 00:21:57.840 --> 00:22:00.289 align:start position:0% um we could even consider removing<00:21:58.500> like<00:21:58.679> inheritance<00:21:59.280> or<00:21:59.520> looking<00:22:00.120> at 00:22:00.289 --> 00:22:00.299 align:start position:0% removing like inheritance or looking at 00:22:00.299 --> 00:22:03.710 align:start position:0% removing like inheritance or looking at like<00:22:00.480> a<00:22:00.600> different<00:22:00.720> way<00:22:01.020> of<00:22:01.919> composing<00:22:02.720> the 00:22:03.710 --> 00:22:03.720 align:start position:0% like a different way of composing the 00:22:03.720 --> 00:22:07.190 align:start position:0% like a different way of composing the source<00:22:04.080> code 00:22:07.190 --> 00:22:07.200 align:start position:0% 00:22:07.200 --> 00:22:08.750 align:start position:0% um<00:22:07.260> and<00:22:07.440> in<00:22:07.559> fact<00:22:07.679> if<00:22:07.919> we<00:22:08.100> have<00:22:08.280> like<00:22:08.520> more 00:22:08.750 --> 00:22:08.760 align:start position:0% um and in fact if we have like more 00:22:08.760 --> 00:22:11.390 align:start position:0% um and in fact if we have like more clear<00:22:09.059> control<00:22:09.360> about<00:22:09.720> the<00:22:10.020> storage<00:22:10.260> maybe<00:22:11.100> we 00:22:11.390 --> 00:22:11.400 align:start position:0% clear control about the storage maybe we 00:22:11.400 --> 00:22:13.730 align:start position:0% clear control about the storage maybe we also<00:22:11.820> have<00:22:12.600> more<00:22:12.840> clear<00:22:12.960> control<00:22:13.200> storage 00:22:13.730 --> 00:22:13.740 align:start position:0% also have more clear control storage 00:22:13.740 --> 00:22:16.430 align:start position:0% also have more clear control storage layout<00:22:14.280> which<00:22:15.000> has<00:22:15.179> been<00:22:15.419> like<00:22:15.720> a<00:22:16.260> really 00:22:16.430 --> 00:22:16.440 align:start position:0% layout which has been like a really 00:22:16.440 --> 00:22:18.710 align:start position:0% layout which has been like a really annoying<00:22:16.860> question<00:22:17.039> and<00:22:17.760> I<00:22:17.940> know<00:22:18.120> many<00:22:18.419> of<00:22:18.600> you 00:22:18.710 --> 00:22:18.720 align:start position:0% annoying question and I know many of you 00:22:18.720 --> 00:22:21.350 align:start position:0% annoying question and I know many of you have<00:22:19.080> open<00:22:19.380> issues<00:22:20.039> how<00:22:20.700> can<00:22:20.880> we<00:22:21.059> like<00:22:21.179> set 00:22:21.350 --> 00:22:21.360 align:start position:0% have open issues how can we like set 00:22:21.360 --> 00:22:23.930 align:start position:0% have open issues how can we like set like<00:22:21.659> slot<00:22:22.020> numbers<00:22:22.559> Etc 00:22:23.930 --> 00:22:23.940 align:start position:0% like slot numbers Etc 00:22:23.940 --> 00:22:25.789 align:start position:0% like slot numbers Etc um<00:22:24.059> some<00:22:24.539> older<00:22:24.840> contracts<00:22:25.200> have<00:22:25.380> like<00:22:25.559> these 00:22:25.789 --> 00:22:25.799 align:start position:0% um some older contracts have like these 00:22:25.799 --> 00:22:29.029 align:start position:0% um some older contracts have like these padding<00:22:26.159> storage<00:22:26.640> items<00:22:27.240> it's<00:22:27.780> insane 00:22:29.029 --> 00:22:29.039 align:start position:0% padding storage items it's insane 00:22:29.039 --> 00:22:30.649 align:start position:0% padding storage items it's insane okay<00:22:29.400> now<00:22:29.640> finally 00:22:30.649 --> 00:22:30.659 align:start position:0% okay now finally 00:22:30.659 --> 00:22:33.110 align:start position:0% okay now finally what<00:22:31.140> would<00:22:31.320> it<00:22:31.500> what<00:22:31.860> could<00:22:31.980> it<00:22:32.159> look<00:22:32.340> like<00:22:32.520> so 00:22:33.110 --> 00:22:33.120 align:start position:0% what would it what could it look like so 00:22:33.120 --> 00:22:34.370 align:start position:0% what would it what could it look like so here's<00:22:33.419> an<00:22:33.480> example 00:22:34.370 --> 00:22:34.380 align:start position:0% here's an example 00:22:34.380 --> 00:22:35.930 align:start position:0% here's an example I'm<00:22:34.740> not<00:22:34.860> sure<00:22:35.039> if<00:22:35.100> any<00:22:35.280> of<00:22:35.400> you<00:22:35.520> recognize 00:22:35.930 --> 00:22:35.940 align:start position:0% I'm not sure if any of you recognize 00:22:35.940 --> 00:22:39.049 align:start position:0% I'm not sure if any of you recognize this<00:22:36.659> it<00:22:37.140> looks<00:22:37.440> like<00:22:37.500> trust<00:22:37.980> but<00:22:38.280> more 00:22:39.049 --> 00:22:39.059 align:start position:0% this it looks like trust but more 00:22:39.059 --> 00:22:42.529 align:start position:0% this it looks like trust but more specifically<00:22:39.600> no<00:22:40.500> it's<00:22:41.220> not<00:22:41.400> sway 00:22:42.529 --> 00:22:42.539 align:start position:0% specifically no it's not sway 00:22:42.539 --> 00:22:44.210 align:start position:0% specifically no it's not sway it's<00:22:42.960> Faye 00:22:44.210 --> 00:22:44.220 align:start position:0% it's Faye 00:22:44.220 --> 00:22:46.370 align:start position:0% it's Faye this<00:22:44.700> is<00:22:44.760> actually<00:22:44.880> say<00:22:45.179> and<00:22:45.539> uh 00:22:46.370 --> 00:22:46.380 align:start position:0% this is actually say and uh 00:22:46.380 --> 00:22:49.130 align:start position:0% this is actually say and uh they<00:22:46.860> started<00:22:47.220> to<00:22:47.580> basically<00:22:48.539> do<00:22:48.780> all<00:22:48.960> these 00:22:49.130 --> 00:22:49.140 align:start position:0% they started to basically do all these 00:22:49.140 --> 00:22:53.029 align:start position:0% they started to basically do all these steps<00:22:49.740> um<00:22:49.740> we<00:22:50.280> were<00:22:50.460> discussing 00:22:53.029 --> 00:22:53.039 align:start position:0% 00:22:53.039 --> 00:22:54.590 align:start position:0% um<00:22:53.100> which<00:22:53.700> means 00:22:54.590 --> 00:22:54.600 align:start position:0% um which means 00:22:54.600 --> 00:22:56.270 align:start position:0% um which means having<00:22:54.960> a<00:22:55.140> context 00:22:56.270 --> 00:22:56.280 align:start position:0% having a context 00:22:56.280 --> 00:22:57.830 align:start position:0% having a context which<00:22:56.640> is<00:22:56.760> like<00:22:56.940> a<00:22:57.059> clear<00:22:57.179> separation<00:22:57.600> of 00:22:57.830 --> 00:22:57.840 align:start position:0% which is like a clear separation of 00:22:57.840 --> 00:22:59.630 align:start position:0% which is like a clear separation of State<00:22:57.960> access 00:22:59.630 --> 00:22:59.640 align:start position:0% State access 00:22:59.640 --> 00:23:00.409 align:start position:0% State access um 00:23:00.409 --> 00:23:00.419 align:start position:0% um 00:23:00.419 --> 00:23:02.750 align:start position:0% um okay<00:23:00.780> this<00:23:01.020> is<00:23:01.140> what's<00:23:01.260> on<00:23:01.500> the<00:23:01.620> website<00:23:01.919> but 00:23:02.750 --> 00:23:02.760 align:start position:0% okay this is what's on the website but 00:23:02.760 --> 00:23:05.270 align:start position:0% okay this is what's on the website but um yeah<00:23:03.360> this<00:23:03.539> is<00:23:03.659> another<00:23:03.780> one<00:23:04.159> which<00:23:05.159> is 00:23:05.270 --> 00:23:05.280 align:start position:0% um yeah this is another one which is 00:23:05.280 --> 00:23:06.890 align:start position:0% um yeah this is another one which is nice 00:23:06.890 --> 00:23:06.900 align:start position:0% nice 00:23:06.900 --> 00:23:08.330 align:start position:0% nice um<00:23:06.960> you<00:23:07.200> know<00:23:07.260> not<00:23:07.559> having<00:23:07.740> like<00:23:08.039> special 00:23:08.330 --> 00:23:08.340 align:start position:0% um you know not having like special 00:23:08.340 --> 00:23:10.310 align:start position:0% um you know not having like special constructs<00:23:09.000> rather<00:23:09.299> have<00:23:09.539> it<00:23:09.720> tied<00:23:10.140> into 00:23:10.310 --> 00:23:10.320 align:start position:0% constructs rather have it tied into 00:23:10.320 --> 00:23:12.409 align:start position:0% constructs rather have it tied into State<00:23:10.620> access 00:23:12.409 --> 00:23:12.419 align:start position:0% State access 00:23:12.419 --> 00:23:13.610 align:start position:0% State access um and<00:23:12.600> I<00:23:12.720> think<00:23:12.840> they<00:23:12.900> also<00:23:13.140> like<00:23:13.260> changing 00:23:13.610 --> 00:23:13.620 align:start position:0% um and I think they also like changing 00:23:13.620 --> 00:23:16.310 align:start position:0% um and I think they also like changing it<00:23:13.799> from<00:23:14.460> having<00:23:15.059> a<00:23:15.299> contract<00:23:15.720> and<00:23:15.960> all<00:23:16.140> these 00:23:16.310 --> 00:23:16.320 align:start position:0% it from having a contract and all these 00:23:16.320 --> 00:23:19.610 align:start position:0% it from having a contract and all these things<00:23:16.440> to<00:23:16.980> having<00:23:17.280> uh<00:23:17.760> separate<00:23:18.179> pieces 00:23:19.610 --> 00:23:19.620 align:start position:0% things to having uh separate pieces 00:23:19.620 --> 00:23:23.149 align:start position:0% things to having uh separate pieces now<00:23:20.039> here's<00:23:20.400> a<00:23:20.460> real<00:23:20.580> example<00:23:21.059> of 00:23:23.149 --> 00:23:23.159 align:start position:0% now here's a real example of 00:23:23.159 --> 00:23:25.070 align:start position:0% now here's a real example of what<00:23:23.640> is<00:23:23.760> more<00:23:23.940> like<00:23:24.120> what<00:23:24.600> we<00:23:24.780> discussed 00:23:25.070 --> 00:23:25.080 align:start position:0% what is more like what we discussed 00:23:25.080 --> 00:23:28.070 align:start position:0% what is more like what we discussed under<00:23:25.260> like<00:23:25.559> thrust<00:23:25.919> solidity 00:23:28.070 --> 00:23:28.080 align:start position:0% under like thrust solidity 00:23:28.080 --> 00:23:29.870 align:start position:0% under like thrust solidity um<00:23:28.200> do<00:23:28.380> you<00:23:28.559> have<00:23:28.620> like<00:23:28.740> a<00:23:28.860> separation<00:23:29.220> of<00:23:29.520> this 00:23:29.870 --> 00:23:29.880 align:start position:0% um do you have like a separation of this 00:23:29.880 --> 00:23:32.390 align:start position:0% um do you have like a separation of this could<00:23:30.059> be<00:23:30.179> contract<00:23:30.480> could<00:23:30.720> be<00:23:30.840> struck<00:23:31.400> people 00:23:32.390 --> 00:23:32.400 align:start position:0% could be contract could be struck people 00:23:32.400 --> 00:23:34.669 align:start position:0% could be contract could be struck people leaning<00:23:32.760> towards<00:23:33.059> struct<00:23:33.419> so<00:23:34.200> this<00:23:34.380> would<00:23:34.559> be 00:23:34.669 --> 00:23:34.679 align:start position:0% leaning towards struct so this would be 00:23:34.679 --> 00:23:36.070 align:start position:0% leaning towards struct so this would be really<00:23:34.799> just<00:23:34.980> the<00:23:35.159> data 00:23:36.070 --> 00:23:36.080 align:start position:0% really just the data 00:23:36.080 --> 00:23:37.789 align:start position:0% really just the data and<00:23:37.080> then<00:23:37.200> that<00:23:37.440> would<00:23:37.559> be<00:23:37.679> the 00:23:37.789 --> 00:23:37.799 align:start position:0% and then that would be the 00:23:37.799 --> 00:23:39.529 align:start position:0% and then that would be the implementation<00:23:38.220> I<00:23:38.940> mean<00:23:39.059> it's<00:23:39.299> not<00:23:39.419> too 00:23:39.529 --> 00:23:39.539 align:start position:0% implementation I mean it's not too 00:23:39.539 --> 00:23:41.090 align:start position:0% implementation I mean it's not too different<00:23:39.720> to<00:23:39.960> what<00:23:40.200> the 00:23:41.090 --> 00:23:41.100 align:start position:0% different to what the 00:23:41.100 --> 00:23:44.029 align:start position:0% different to what the uh<00:23:41.700> fee<00:23:42.000> is<00:23:42.120> trying<00:23:42.240> to<00:23:42.419> do<00:23:42.539> now<00:23:42.720> and<00:23:43.679> this<00:23:43.980> is 00:23:44.029 --> 00:23:44.039 align:start position:0% uh fee is trying to do now and this is 00:23:44.039 --> 00:23:46.190 align:start position:0% uh fee is trying to do now and this is the<00:23:44.220> distal<00:23:44.640> contract<00:23:45.000> I<00:23:45.240> had<00:23:45.360> as<00:23:45.840> an<00:23:46.020> example 00:23:46.190 --> 00:23:46.200 align:start position:0% the distal contract I had as an example 00:23:46.200 --> 00:23:49.070 align:start position:0% the distal contract I had as an example before<00:23:46.559> yeah<00:23:47.400> I<00:23:47.820> mean<00:23:48.000> that's<00:23:48.360> it<00:23:48.600> really<00:23:48.840> I 00:23:49.070 --> 00:23:49.080 align:start position:0% before yeah I mean that's it really I 00:23:49.080 --> 00:23:50.240 align:start position:0% before yeah I mean that's it really I only<00:23:49.200> have<00:23:49.440> 10<00:23:49.559> seconds<00:23:49.740> left 00:23:50.240 --> 00:23:50.250 align:start position:0% only have 10 seconds left 00:23:50.250 --> 00:23:51.310 align:start position:0% only have 10 seconds left [Applause] 00:23:51.310 --> 00:23:51.320 align:start position:0% [Applause] 00:23:51.320 --> 00:23:57.409 align:start position:0% [Applause] [Music] 00:23:57.409 --> 00:23:57.419 align:start position:0% 00:23:57.419 --> 00:23:59.510 align:start position:0% thank<00:23:58.020> you<00:23:58.200> I<00:23:58.380> guess<00:23:58.740> we<00:23:58.919> can<00:23:59.039> take<00:23:59.220> one 00:23:59.510 --> 00:23:59.520 align:start position:0% thank you I guess we can take one 00:23:59.520 --> 00:24:00.289 align:start position:0% thank you I guess we can take one question 00:24:00.289 --> 00:24:00.299 align:start position:0% question 00:24:00.299 --> 00:24:02.750 align:start position:0% question if<00:24:00.840> somebody<00:24:00.960> has<00:24:01.260> a<00:24:01.500> question<00:24:01.679> please<00:24:02.520> raise 00:24:02.750 --> 00:24:02.760 align:start position:0% if somebody has a question please raise 00:24:02.760 --> 00:24:06.529 align:start position:0% if somebody has a question please raise your<00:24:03.059> hand<00:24:03.240> so<00:24:03.600> that<00:24:03.960> the<00:24:04.740> mic<00:24:04.860> can<00:24:05.159> find<00:24:05.340> you 00:24:06.529 --> 00:24:06.539 align:start position:0% your hand so that the mic can find you 00:24:06.539 --> 00:24:09.649 align:start position:0% your hand so that the mic can find you hey<00:24:06.900> Alex<00:24:07.200> so<00:24:07.860> just<00:24:08.640> a<00:24:08.760> simple<00:24:08.940> question<00:24:09.240> you 00:24:09.649 --> 00:24:09.659 align:start position:0% hey Alex so just a simple question you 00:24:09.659 --> 00:24:12.169 align:start position:0% hey Alex so just a simple question you got<00:24:09.780> you're<00:24:10.020> talking<00:24:10.320> a<00:24:10.500> lot<00:24:10.620> about<00:24:10.799> rest 00:24:12.169 --> 00:24:12.179 align:start position:0% got you're talking a lot about rest 00:24:12.179 --> 00:24:14.390 align:start position:0% got you're talking a lot about rest but<00:24:12.539> have<00:24:12.780> you<00:24:12.960> guys<00:24:13.080> give<00:24:13.740> a<00:24:13.860> talk<00:24:14.100> to<00:24:14.280> the 00:24:14.390 --> 00:24:14.400 align:start position:0% but have you guys give a talk to the 00:24:14.400 --> 00:24:17.029 align:start position:0% but have you guys give a talk to the Cabo<00:24:14.880> that's<00:24:15.179> like<00:24:15.480> the<00:24:15.780> new<00:24:15.960> language 00:24:17.029 --> 00:24:17.039 align:start position:0% Cabo that's like the new language 00:24:17.039 --> 00:24:18.770 align:start position:0% Cabo that's like the new language that<00:24:17.460> they<00:24:17.640> are<00:24:17.760> going<00:24:17.880> to<00:24:18.000> upgrade<00:24:18.299> C<00:24:18.539> plus 00:24:18.770 --> 00:24:18.780 align:start position:0% that they are going to upgrade C plus 00:24:18.780 --> 00:24:20.510 align:start position:0% that they are going to upgrade C plus plus 00:24:20.510 --> 00:24:20.520 align:start position:0% plus 00:24:20.520 --> 00:24:23.450 align:start position:0% plus carbon<00:24:21.240> it's<00:24:22.080> interoptable<00:24:22.799> so<00:24:23.220> you<00:24:23.340> guys 00:24:23.450 --> 00:24:23.460 align:start position:0% carbon it's interoptable so you guys 00:24:23.460 --> 00:24:25.850 align:start position:0% carbon it's interoptable so you guys could<00:24:23.760> like<00:24:24.120> reviews<00:24:24.600> oh<00:24:25.140> yeah<00:24:25.200> yeah<00:24:25.380> the<00:24:25.559> C 00:24:25.850 --> 00:24:25.860 align:start position:0% could like reviews oh yeah yeah the C 00:24:25.860 --> 00:24:27.970 align:start position:0% could like reviews oh yeah yeah the C plus<00:24:26.039> the<00:24:26.280> new<00:24:26.400> C<00:24:26.580> plus<00:24:26.700> plus<00:24:26.760> right<00:24:27.120> yeah<00:24:27.480> yeah 00:24:27.970 --> 00:24:27.980 align:start position:0% plus the new C plus plus right yeah yeah 00:24:27.980 --> 00:24:30.649 align:start position:0% plus the new C plus plus right yeah yeah experimental<00:24:28.980> yet<00:24:29.220> but<00:24:29.520> guys<00:24:29.880> would<00:24:30.179> be<00:24:30.480> able 00:24:30.649 --> 00:24:30.659 align:start position:0% experimental yet but guys would be able 00:24:30.659 --> 00:24:33.110 align:start position:0% experimental yet but guys would be able to<00:24:30.780> use<00:24:30.900> everything<00:24:31.140> that's<00:24:31.440> written<00:24:31.919> so<00:24:32.159> far 00:24:33.110 --> 00:24:33.120 align:start position:0% to use everything that's written so far 00:24:33.120 --> 00:24:34.909 align:start position:0% to use everything that's written so far I'm<00:24:33.720> not<00:24:33.900> sure<00:24:34.020> what<00:24:34.200> benefit<00:24:34.380> that<00:24:34.679> would 00:24:34.909 --> 00:24:34.919 align:start position:0% I'm not sure what benefit that would 00:24:34.919 --> 00:24:35.930 align:start position:0% I'm not sure what benefit that would bring 00:24:35.930 --> 00:24:35.940 align:start position:0% bring 00:24:35.940 --> 00:24:39.409 align:start position:0% bring um<00:24:36.080> it's<00:24:37.080> worth<00:24:37.440> a<00:24:37.679> thought<00:24:37.799> yeah<00:24:38.820> yeah<00:24:38.820> I 00:24:39.409 --> 00:24:39.419 align:start position:0% um it's worth a thought yeah yeah I 00:24:39.419 --> 00:24:40.370 align:start position:0% um it's worth a thought yeah yeah I think<00:24:39.600> we 00:24:40.370 --> 00:24:40.380 align:start position:0% think we 00:24:40.380 --> 00:24:42.110 align:start position:0% think we I<00:24:40.740> don't<00:24:40.919> think<00:24:41.039> we<00:24:41.100> had<00:24:41.280> a<00:24:41.400> look<00:24:41.460> but<00:24:41.640> we<00:24:41.760> heard 00:24:42.110 --> 00:24:42.120 align:start position:0% I don't think we had a look but we heard 00:24:42.120 --> 00:24:43.010 align:start position:0% I don't think we had a look but we heard about<00:24:42.299> it 00:24:43.010 --> 00:24:43.020 align:start position:0% about it 00:24:43.020 --> 00:24:45.110 align:start position:0% about it unfortunately<00:24:43.860> time's<00:24:44.400> up<00:24:44.520> but<00:24:44.700> thank<00:24:44.880> you<00:24:45.000> so 00:24:45.110 --> 00:24:45.120 align:start position:0% unfortunately time's up but thank you so 00:24:45.120 --> 00:24:47.480 align:start position:0% unfortunately time's up but thank you so much<00:24:45.240> Alex