WEBVTT Kind: captions Language: en 00:00:00.790 --> 00:00:04.840 align:start position:0% [Music] 00:00:04.840 --> 00:00:04.850 align:start position:0% [Music] 00:00:04.850 --> 00:00:10.280 align:start position:0% [Music] so<00:00:06.529> hello<00:00:07.529> everyone<00:00:08.179> welcome<00:00:09.179> to<00:00:09.360> my<00:00:09.570> talk<00:00:10.110> I 00:00:10.280 --> 00:00:10.290 align:start position:0% so hello everyone welcome to my talk I 00:00:10.290 --> 00:00:12.799 align:start position:0% so hello everyone welcome to my talk I wanted<00:00:10.590> to<00:00:10.650> give<00:00:11.400> you<00:00:11.550> some<00:00:11.790> updates<00:00:11.880> from<00:00:12.420> the 00:00:12.799 --> 00:00:12.809 align:start position:0% wanted to give you some updates from the 00:00:12.809 --> 00:00:15.709 align:start position:0% wanted to give you some updates from the solidity<00:00:13.230> team<00:00:13.530> so<00:00:13.860> my<00:00:14.130> name<00:00:14.250> is<00:00:14.309> Eric<00:00:14.639> and<00:00:14.820> I 00:00:15.709 --> 00:00:15.719 align:start position:0% solidity team so my name is Eric and I 00:00:15.719 --> 00:00:18.080 align:start position:0% solidity team so my name is Eric and I just<00:00:16.109> joined<00:00:16.320> the<00:00:16.560> team<00:00:16.650> half<00:00:17.190> a<00:00:17.279> year<00:00:17.430> ago<00:00:17.670> so 00:00:18.080 --> 00:00:18.090 align:start position:0% just joined the team half a year ago so 00:00:18.090 --> 00:00:20.810 align:start position:0% just joined the team half a year ago so it's<00:00:18.359> a<00:00:18.720> nice<00:00:19.380> opportunity<00:00:19.560> to<00:00:20.430> actually<00:00:20.609> be 00:00:20.810 --> 00:00:20.820 align:start position:0% it's a nice opportunity to actually be 00:00:20.820 --> 00:00:23.529 align:start position:0% it's a nice opportunity to actually be here<00:00:21.119> and<00:00:21.330> talk<00:00:21.510> about<00:00:21.689> what<00:00:22.560> we<00:00:22.710> did<00:00:22.859> so<00:00:23.189> far 00:00:23.529 --> 00:00:23.539 align:start position:0% here and talk about what we did so far 00:00:23.539 --> 00:00:26.870 align:start position:0% here and talk about what we did so far so<00:00:24.539> first<00:00:25.350> of<00:00:25.470> all<00:00:25.619> I<00:00:25.890> want<00:00:26.099> to<00:00:26.250> quickly<00:00:26.490> give 00:00:26.870 --> 00:00:26.880 align:start position:0% so first of all I want to quickly give 00:00:26.880 --> 00:00:29.120 align:start position:0% so first of all I want to quickly give you<00:00:27.000> an<00:00:27.060> overview<00:00:27.449> of<00:00:28.019> what<00:00:28.680> I'm<00:00:28.800> going<00:00:29.099> to 00:00:29.120 --> 00:00:29.130 align:start position:0% you an overview of what I'm going to 00:00:29.130 --> 00:00:33.680 align:start position:0% you an overview of what I'm going to talk<00:00:29.369> about<00:00:29.599> so<00:00:30.920> first<00:00:31.920> I<00:00:32.309> want<00:00:32.579> to<00:00:32.690> introduce 00:00:33.680 --> 00:00:33.690 align:start position:0% talk about so first I want to introduce 00:00:33.690 --> 00:00:36.100 align:start position:0% talk about so first I want to introduce some<00:00:34.140> of<00:00:34.350> our<00:00:34.530> new<00:00:34.680> tool<00:00:34.920> team<00:00:35.280> members<00:00:35.550> to<00:00:35.700> you 00:00:36.100 --> 00:00:36.110 align:start position:0% some of our new tool team members to you 00:00:36.110 --> 00:00:39.290 align:start position:0% some of our new tool team members to you then<00:00:37.110> I<00:00:37.170> want<00:00:37.290> to<00:00:37.530> talk<00:00:37.800> about<00:00:38.070> the<00:00:38.969> audits 00:00:39.290 --> 00:00:39.300 align:start position:0% then I want to talk about the audits 00:00:39.300 --> 00:00:42.770 align:start position:0% then I want to talk about the audits that<00:00:39.540> the<00:00:39.719> compiler<00:00:40.050> got<00:00:41.210> also<00:00:42.210> want<00:00:42.540> to<00:00:42.570> talk 00:00:42.770 --> 00:00:42.780 align:start position:0% that the compiler got also want to talk 00:00:42.780 --> 00:00:46.819 align:start position:0% that the compiler got also want to talk about<00:00:43.010> solidity<00:00:44.010> zero<00:00:44.789> five<00:00:45.090> zero<00:00:45.410> so<00:00:46.410> which 00:00:46.819 --> 00:00:46.829 align:start position:0% about solidity zero five zero so which 00:00:46.829 --> 00:00:49.819 align:start position:0% about solidity zero five zero so which is<00:00:47.300> yeah<00:00:48.300> probably<00:00:48.809> what<00:00:49.079> what<00:00:49.350> you<00:00:49.469> are<00:00:49.590> going 00:00:49.819 --> 00:00:49.829 align:start position:0% is yeah probably what what you are going 00:00:49.829 --> 00:00:52.670 align:start position:0% is yeah probably what what you are going to<00:00:49.920> be<00:00:50.129> here<00:00:50.370> so<00:00:50.850> and<00:00:51.270> then<00:00:51.690> I<00:00:52.079> want<00:00:52.410> to<00:00:52.469> talk 00:00:52.670 --> 00:00:52.680 align:start position:0% to be here so and then I want to talk 00:00:52.680 --> 00:00:54.139 align:start position:0% to be here so and then I want to talk about<00:00:52.949> what's<00:00:53.309> coming<00:00:53.579> up<00:00:53.820> what<00:00:54.030> we're 00:00:54.139 --> 00:00:54.149 align:start position:0% about what's coming up what we're 00:00:54.149 --> 00:00:56.150 align:start position:0% about what's coming up what we're currently<00:00:54.300> working<00:00:54.719> on<00:00:54.989> and<00:00:55.440> what<00:00:55.680> will<00:00:55.890> be 00:00:56.150 --> 00:00:56.160 align:start position:0% currently working on and what will be 00:00:56.160 --> 00:00:58.760 align:start position:0% currently working on and what will be released<00:00:56.640> and<00:00:56.940> coming<00:00:57.899> upcoming<00:00:58.379> versions 00:00:58.760 --> 00:00:58.770 align:start position:0% released and coming upcoming versions 00:00:58.770 --> 00:01:03.080 align:start position:0% released and coming upcoming versions and<00:00:59.239> also<00:01:00.239> how<00:01:00.930> to<00:01:00.989> contribute<00:01:01.609> possibly<00:01:02.609> to 00:01:03.080 --> 00:01:03.090 align:start position:0% and also how to contribute possibly to 00:01:03.090 --> 00:01:08.090 align:start position:0% and also how to contribute possibly to the<00:01:03.660> project<00:01:05.420> so<00:01:06.420> okay<00:01:07.170> first<00:01:07.470> of<00:01:07.619> all<00:01:07.740> what 00:01:08.090 --> 00:01:08.100 align:start position:0% the project so okay first of all what 00:01:08.100 --> 00:01:11.000 align:start position:0% the project so okay first of all what happened<00:01:08.400> to<00:01:08.520> the<00:01:08.640> team<00:01:09.229> you<00:01:10.229> might<00:01:10.380> know<00:01:10.650> that 00:01:11.000 --> 00:01:11.010 align:start position:0% happened to the team you might know that 00:01:11.010 --> 00:01:13.310 align:start position:0% happened to the team you might know that for<00:01:11.310> the<00:01:11.490> last<00:01:11.670> year's<00:01:12.030> almost<00:01:12.510> like<00:01:12.780> Alex<00:01:13.140> and 00:01:13.310 --> 00:01:13.320 align:start position:0% for the last year's almost like Alex and 00:01:13.320 --> 00:01:16.550 align:start position:0% for the last year's almost like Alex and Christian<00:01:13.710> were<00:01:14.990> working<00:01:15.990> on<00:01:16.110> the<00:01:16.200> compiler 00:01:16.550 --> 00:01:16.560 align:start position:0% Christian were working on the compiler 00:01:16.560 --> 00:01:19.190 align:start position:0% Christian were working on the compiler and<00:01:16.799> on<00:01:17.060> infrastructure<00:01:18.060> but<00:01:18.600> now<00:01:18.780> we<00:01:18.840> grew 00:01:19.190 --> 00:01:19.200 align:start position:0% and on infrastructure but now we grew 00:01:19.200 --> 00:01:21.649 align:start position:0% and on infrastructure but now we grew the<00:01:19.380> team<00:01:19.590> to<00:01:19.860> seven<00:01:20.340> people<00:01:20.640> in<00:01:20.759> total<00:01:21.119> so<00:01:21.630> we 00:01:21.649 --> 00:01:21.659 align:start position:0% the team to seven people in total so we 00:01:21.659 --> 00:01:23.960 align:start position:0% the team to seven people in total so we have<00:01:22.259> another<00:01:22.619> Christian<00:01:23.100> the<00:01:23.369> joint<00:01:23.640> who 00:01:23.960 --> 00:01:23.970 align:start position:0% have another Christian the joint who 00:01:23.970 --> 00:01:27.350 align:start position:0% have another Christian the joint who cannot<00:01:24.689> be<00:01:24.840> here<00:01:24.869> unfortunately<00:01:26.000> then<00:01:27.000> we 00:01:27.350 --> 00:01:27.360 align:start position:0% cannot be here unfortunately then we 00:01:27.360 --> 00:01:29.480 align:start position:0% cannot be here unfortunately then we have<00:01:27.630> Christian<00:01:28.439> you<00:01:28.619> might<00:01:28.770> know<00:01:29.009> him<00:01:29.220> and 00:01:29.480 --> 00:01:29.490 align:start position:0% have Christian you might know him and 00:01:29.490 --> 00:01:31.910 align:start position:0% have Christian you might know him and then<00:01:30.119> we<00:01:30.299> have<00:01:30.479> another<00:01:30.659> Christa<00:01:31.320> joined<00:01:31.619> and 00:01:31.910 --> 00:01:31.920 align:start position:0% then we have another Christa joined and 00:01:31.920 --> 00:01:34.130 align:start position:0% then we have another Christa joined and he<00:01:32.100> is<00:01:32.159> our<00:01:32.310> technical<00:01:32.640> writers<00:01:33.119> so<00:01:33.630> he<00:01:34.020> is 00:01:34.130 --> 00:01:34.140 align:start position:0% he is our technical writers so he is 00:01:34.140 --> 00:01:37.190 align:start position:0% he is our technical writers so he is mainly<00:01:34.380> working<00:01:34.799> on<00:01:34.890> the<00:01:34.979> documentation<00:01:36.200> and 00:01:37.190 --> 00:01:37.200 align:start position:0% mainly working on the documentation and 00:01:37.200 --> 00:01:40.520 align:start position:0% mainly working on the documentation and then<00:01:37.470> we<00:01:37.619> have<00:01:37.770> Danielle<00:01:38.329> me<00:01:39.329> and<00:01:39.630> Leo<00:01:40.079> and<00:01:40.380> we 00:01:40.520 --> 00:01:40.530 align:start position:0% then we have Danielle me and Leo and we 00:01:40.530 --> 00:01:42.050 align:start position:0% then we have Danielle me and Leo and we are<00:01:40.590> all<00:01:40.680> working<00:01:40.890> as<00:01:41.250> software<00:01:41.430> engineers 00:01:42.050 --> 00:01:42.060 align:start position:0% are all working as software engineers 00:01:42.060 --> 00:01:48.410 align:start position:0% are all working as software engineers and<00:01:42.270> the<00:01:42.899> team<00:01:45.350> next<00:01:46.350> one<00:01:46.649> what<00:01:47.009> happened<00:01:47.430> with 00:01:48.410 --> 00:01:48.420 align:start position:0% and the team next one what happened with 00:01:48.420 --> 00:01:53.120 align:start position:0% and the team next one what happened with the<00:01:48.570> audits<00:01:48.899> so<00:01:50.540> last<00:01:51.540> year<00:01:51.869> the<00:01:52.590> compiler<00:01:52.920> was 00:01:53.120 --> 00:01:53.130 align:start position:0% the audits so last year the compiler was 00:01:53.130 --> 00:01:56.420 align:start position:0% the audits so last year the compiler was audited<00:01:53.700> by<00:01:54.270> coins<00:01:54.540> back<00:01:54.750> for<00:01:54.960> augur<00:01:55.229> so<00:01:55.950> and 00:01:56.420 --> 00:01:56.430 align:start position:0% audited by coins back for augur so and 00:01:56.430 --> 00:01:59.810 align:start position:0% audited by coins back for augur so and this<00:01:56.850> happened<00:01:57.210> in<00:01:57.360> the<00:01:57.390> end<00:01:57.600> of<00:01:58.399> 2017<00:01:59.399> and 00:01:59.810 --> 00:01:59.820 align:start position:0% this happened in the end of 2017 and 00:01:59.820 --> 00:02:03.490 align:start position:0% this happened in the end of 2017 and they<00:02:00.119> discovered<00:02:00.570> ten<00:02:00.719> issues<00:02:00.899> fixed<00:02:01.439> 9<00:02:01.710> and 00:02:03.490 --> 00:02:03.500 align:start position:0% they discovered ten issues fixed 9 and 00:02:03.500 --> 00:02:05.600 align:start position:0% they discovered ten issues fixed 9 and the<00:02:04.500> last<00:02:04.530> if<00:02:04.860> she<00:02:04.979> was<00:02:05.100> part<00:02:05.340> of<00:02:05.460> the 00:02:05.600 --> 00:02:05.610 align:start position:0% the last if she was part of the 00:02:05.610 --> 00:02:07.999 align:start position:0% the last if she was part of the inheritance<00:02:06.060> changes<00:02:06.540> and<00:02:06.719> you<00:02:07.649> can<00:02:07.829> also 00:02:07.999 --> 00:02:08.009 align:start position:0% inheritance changes and you can also 00:02:08.009 --> 00:02:12.580 align:start position:0% inheritance changes and you can also find<00:02:08.610> a<00:02:08.789> report<00:02:09.149> on<00:02:09.929> medium 00:02:12.580 --> 00:02:12.590 align:start position:0% 00:02:12.590 --> 00:02:16.270 align:start position:0% so<00:02:12.950> the<00:02:13.159> second<00:02:13.459> audit<00:02:13.840> that<00:02:14.840> we<00:02:15.560> got<00:02:15.739> started 00:02:16.270 --> 00:02:16.280 align:start position:0% so the second audit that we got started 00:02:16.280 --> 00:02:19.750 align:start position:0% so the second audit that we got started in<00:02:16.640> June<00:02:16.849> and<00:02:17.659> was<00:02:18.230> done<00:02:18.439> by<00:02:18.620> the<00:02:19.400> people<00:02:19.640> from 00:02:19.750 --> 00:02:19.760 align:start position:0% in June and was done by the people from 00:02:19.760 --> 00:02:21.520 align:start position:0% in June and was done by the people from Zeppelin<00:02:20.150> I<00:02:20.390> was<00:02:20.900> sponsored<00:02:21.170> by<00:02:21.379> the 00:02:21.520 --> 00:02:21.530 align:start position:0% Zeppelin I was sponsored by the 00:02:21.530 --> 00:02:24.220 align:start position:0% Zeppelin I was sponsored by the foundation<00:02:22.069> and<00:02:22.189> by<00:02:22.310> auger<00:02:22.640> and<00:02:23.019> they<00:02:24.019> worked 00:02:24.220 --> 00:02:24.230 align:start position:0% foundation and by auger and they worked 00:02:24.230 --> 00:02:27.460 align:start position:0% foundation and by auger and they worked very<00:02:24.470> closely<00:02:24.769> with<00:02:24.980> us<00:02:25.510> and<00:02:26.510> they<00:02:26.930> audited<00:02:27.349> a 00:02:27.460 --> 00:02:27.470 align:start position:0% very closely with us and they audited a 00:02:27.470 --> 00:02:30.699 align:start position:0% very closely with us and they audited a specific<00:02:27.980> compiler<00:02:28.310> version<00:02:28.519> but<00:02:29.450> the<00:02:30.409> issues 00:02:30.699 --> 00:02:30.709 align:start position:0% specific compiler version but the issues 00:02:30.709 --> 00:02:32.800 align:start position:0% specific compiler version but the issues are<00:02:30.950> being<00:02:31.129> fixed<00:02:31.459> and<00:02:31.640> developed<00:02:32.569> already 00:02:32.800 --> 00:02:32.810 align:start position:0% are being fixed and developed already 00:02:32.810 --> 00:02:35.050 align:start position:0% are being fixed and developed already and<00:02:33.079> so<00:02:33.709> most<00:02:34.010> of<00:02:34.190> them<00:02:34.340> will<00:02:34.579> be<00:02:34.610> part<00:02:34.940> of 00:02:35.050 --> 00:02:35.060 align:start position:0% and so most of them will be part of 00:02:35.060 --> 00:02:40.180 align:start position:0% and so most of them will be part of zero-five-zero<00:02:38.440> and<00:02:39.440> there's<00:02:39.620> also<00:02:39.829> an 00:02:40.180 --> 00:02:40.190 align:start position:0% zero-five-zero and there's also an 00:02:40.190 --> 00:02:41.979 align:start position:0% zero-five-zero and there's also an interesting<00:02:40.670> talk<00:02:40.849> about<00:02:41.180> that<00:02:41.480> about<00:02:41.870> the 00:02:41.979 --> 00:02:41.989 align:start position:0% interesting talk about that about the 00:02:41.989 --> 00:02:43.780 align:start position:0% interesting talk about that about the audit<00:02:42.260> itself<00:02:42.560> it's<00:02:43.250> going<00:02:43.370> to<00:02:43.549> happen 00:02:43.780 --> 00:02:43.790 align:start position:0% audit itself it's going to happen 00:02:43.790 --> 00:02:47.229 align:start position:0% audit itself it's going to happen tomorrow<00:02:43.989> at<00:02:44.989> 1:40<00:02:45.980> p.m.<00:02:46.280> at<00:02:46.489> ultraviolet 00:02:47.229 --> 00:02:47.239 align:start position:0% tomorrow at 1:40 p.m. at ultraviolet 00:02:47.239 --> 00:02:50.649 align:start position:0% tomorrow at 1:40 p.m. at ultraviolet room<00:02:47.420> and<00:02:48.099> it<00:02:49.099> will<00:02:49.250> be<00:02:49.310> done<00:02:49.549> by<00:02:49.819> manual<00:02:50.389> from 00:02:50.649 --> 00:02:50.659 align:start position:0% room and it will be done by manual from 00:02:50.659 --> 00:02:53.319 align:start position:0% room and it will be done by manual from open<00:02:51.170> zeppelin<00:02:51.560> and<00:02:51.799> he<00:02:51.980> will<00:02:52.129> talk<00:02:52.370> about<00:02:52.549> the 00:02:53.319 --> 00:02:53.329 align:start position:0% open zeppelin and he will talk about the 00:02:53.329 --> 00:02:56.789 align:start position:0% open zeppelin and he will talk about the outcome<00:02:53.720> of<00:02:53.930> this<00:02:54.139> audit 00:02:56.789 --> 00:02:56.799 align:start position:0% 00:02:56.799 --> 00:03:00.390 align:start position:0% all<00:02:57.799> right<00:02:58.069> so<00:02:58.579> solidity<00:02:59.359> zero-five-zero 00:03:00.390 --> 00:03:00.400 align:start position:0% all right so solidity zero-five-zero 00:03:00.400 --> 00:03:02.229 align:start position:0% all right so solidity zero-five-zero we're<00:03:01.400> almost<00:03:01.579> there 00:03:02.229 --> 00:03:02.239 align:start position:0% we're almost there 00:03:02.239 --> 00:03:07.839 align:start position:0% we're almost there so<00:03:02.959> this<00:03:03.560> ulti<00:03:04.040> is<00:03:04.280> ready<00:03:04.840> but<00:03:05.840> salty<00:03:06.819> Jas 00:03:07.839 --> 00:03:07.849 align:start position:0% so this ulti is ready but salty Jas 00:03:07.849 --> 00:03:09.670 align:start position:0% so this ulti is ready but salty Jas there<00:03:08.540> are<00:03:08.599> still<00:03:08.780> some<00:03:08.959> things<00:03:09.170> to<00:03:09.409> be<00:03:09.500> done 00:03:09.670 --> 00:03:09.680 align:start position:0% there are still some things to be done 00:03:09.680 --> 00:03:13.059 align:start position:0% there are still some things to be done but<00:03:10.340> we<00:03:10.970> are<00:03:11.510> hoping<00:03:12.019> to<00:03:12.319> get<00:03:12.650> this<00:03:12.799> done<00:03:13.040> in 00:03:13.059 --> 00:03:13.069 align:start position:0% but we are hoping to get this done in 00:03:13.069 --> 00:03:16.509 align:start position:0% but we are hoping to get this done in the<00:03:13.370> next<00:03:13.879> days<00:03:14.209> so<00:03:15.139> yeah<00:03:15.709> watch<00:03:15.980> out<00:03:16.129> for<00:03:16.370> the 00:03:16.509 --> 00:03:16.519 align:start position:0% the next days so yeah watch out for the 00:03:16.519 --> 00:03:21.580 align:start position:0% the next days so yeah watch out for the new<00:03:16.639> version<00:03:17.829> and<00:03:19.750> yeah<00:03:20.750> now<00:03:20.989> I<00:03:21.019> want<00:03:21.290> to<00:03:21.319> talk 00:03:21.580 --> 00:03:21.590 align:start position:0% new version and yeah now I want to talk 00:03:21.590 --> 00:03:25.689 align:start position:0% new version and yeah now I want to talk about<00:03:22.419> what<00:03:23.419> actually<00:03:23.900> changed<00:03:24.430> in<00:03:25.430> the<00:03:25.549> new 00:03:25.689 --> 00:03:25.699 align:start position:0% about what actually changed in the new 00:03:25.699 --> 00:03:28.659 align:start position:0% about what actually changed in the new version<00:03:26.090> so<00:03:26.599> we<00:03:26.989> had<00:03:27.139> some<00:03:27.440> design<00:03:28.370> goals 00:03:28.659 --> 00:03:28.669 align:start position:0% version so we had some design goals 00:03:28.669 --> 00:03:31.780 align:start position:0% version so we had some design goals there<00:03:29.120> so<00:03:29.569> we<00:03:29.840> wanted<00:03:30.079> to<00:03:30.139> improve<00:03:31.010> safety 00:03:31.780 --> 00:03:31.790 align:start position:0% there so we wanted to improve safety 00:03:31.790 --> 00:03:34.420 align:start position:0% there so we wanted to improve safety that<00:03:32.209> was<00:03:32.359> the<00:03:32.629> first<00:03:33.379> and<00:03:33.560> foremost<00:03:33.739> goal<00:03:33.949> and 00:03:34.420 --> 00:03:34.430 align:start position:0% that was the first and foremost goal and 00:03:34.430 --> 00:03:36.970 align:start position:0% that was the first and foremost goal and we<00:03:34.970> wanted<00:03:35.239> to<00:03:35.329> do<00:03:35.480> that<00:03:35.660> by<00:03:35.900> requiring<00:03:36.260> users 00:03:36.970 --> 00:03:36.980 align:start position:0% we wanted to do that by requiring users 00:03:36.980 --> 00:03:38.819 align:start position:0% we wanted to do that by requiring users to<00:03:37.010> be<00:03:37.400> more<00:03:37.970> explicit 00:03:38.819 --> 00:03:38.829 align:start position:0% to be more explicit 00:03:38.829 --> 00:03:42.159 align:start position:0% to be more explicit by<00:03:39.829> removing<00:03:40.340> dis<00:03:41.060> ambiguities<00:03:41.599> or<00:03:41.900> weird 00:03:42.159 --> 00:03:42.169 align:start position:0% by removing dis ambiguities or weird 00:03:42.169 --> 00:03:45.189 align:start position:0% by removing dis ambiguities or weird behavior<00:03:42.680> and<00:03:43.150> also<00:03:44.150> by<00:03:44.449> adding<00:03:44.690> runtime 00:03:45.189 --> 00:03:45.199 align:start position:0% behavior and also by adding runtime 00:03:45.199 --> 00:03:50.619 align:start position:0% behavior and also by adding runtime checks<00:03:45.500> to<00:03:45.829> the<00:03:45.919> compiler<00:03:48.069> so<00:03:49.069> I<00:03:50.000> picked<00:03:50.569> some 00:03:50.619 --> 00:03:50.629 align:start position:0% checks to the compiler so I picked some 00:03:50.629 --> 00:03:52.030 align:start position:0% checks to the compiler so I picked some of<00:03:50.870> the<00:03:50.989> language<00:03:51.260> features<00:03:51.440> some<00:03:51.889> of<00:03:51.919> the 00:03:52.030 --> 00:03:52.040 align:start position:0% of the language features some of the 00:03:52.040 --> 00:03:55.210 align:start position:0% of the language features some of the most<00:03:52.280> important<00:03:52.730> ones<00:03:52.900> so<00:03:53.900> first<00:03:54.500> of<00:03:54.650> all<00:03:54.829> we 00:03:55.210 --> 00:03:55.220 align:start position:0% most important ones so first of all we 00:03:55.220 --> 00:03:59.970 align:start position:0% most important ones so first of all we now<00:03:56.209> have<00:03:56.480> explicit<00:03:57.169> types<00:03:57.470> so<00:03:58.150> and 00:03:59.970 --> 00:03:59.980 align:start position:0% now have explicit types so and 00:03:59.980 --> 00:04:03.970 align:start position:0% now have explicit types so and explicitly<00:04:00.980> the<00:04:01.190> visibility<00:04:02.829> explicit<00:04:03.829> data 00:04:03.970 --> 00:04:03.980 align:start position:0% explicitly the visibility explicit data 00:04:03.980 --> 00:04:07.059 align:start position:0% explicitly the visibility explicit data locations<00:04:04.870> new<00:04:05.870> scoping<00:04:06.319> rules<00:04:06.440> for<00:04:06.709> function 00:04:07.059 --> 00:04:07.069 align:start position:0% locations new scoping rules for function 00:04:07.069 --> 00:04:09.339 align:start position:0% locations new scoping rules for function local<00:04:07.310> variables<00:04:08.019> we<00:04:09.019> have<00:04:09.139> a<00:04:09.169> new 00:04:09.339 --> 00:04:09.349 align:start position:0% local variables we have a new 00:04:09.349 --> 00:04:12.099 align:start position:0% local variables we have a new constructor<00:04:09.889> syntax<00:04:10.359> we<00:04:11.359> also<00:04:11.510> introduced 00:04:12.099 --> 00:04:12.109 align:start position:0% constructor syntax we also introduced 00:04:12.109 --> 00:04:16.779 align:start position:0% constructor syntax we also introduced emit<00:04:13.010> for<00:04:13.190> events<00:04:14.049> then<00:04:15.049> also<00:04:15.680> the<00:04:16.639> address 00:04:16.779 --> 00:04:16.789 align:start position:0% emit for events then also the address 00:04:16.789 --> 00:04:20.140 align:start position:0% emit for events then also the address payable<00:04:17.329> and<00:04:17.570> some<00:04:18.199> others<00:04:18.500> and<00:04:19.310> now<00:04:19.789> I<00:04:19.820> went 00:04:20.140 --> 00:04:20.150 align:start position:0% payable and some others and now I went 00:04:20.150 --> 00:04:21.020 align:start position:0% payable and some others and now I went to 00:04:21.020 --> 00:04:21.030 align:start position:0% to 00:04:21.030 --> 00:04:24.710 align:start position:0% to go<00:04:21.239> through<00:04:21.630> all<00:04:21.900> of<00:04:21.930> them<00:04:22.170> in<00:04:22.410> detail<00:04:23.720> so 00:04:24.710 --> 00:04:24.720 align:start position:0% go through all of them in detail so 00:04:24.720 --> 00:04:28.370 align:start position:0% go through all of them in detail so explicit<00:04:25.530> types<00:04:25.770> what<00:04:26.070> that<00:04:26.220> does<00:04:26.370> mean<00:04:27.380> so 00:04:28.370 --> 00:04:28.380 align:start position:0% explicit types what that does mean so 00:04:28.380 --> 00:04:32.420 align:start position:0% explicit types what that does mean so here's<00:04:29.340> an<00:04:29.460> example<00:04:29.580> of<00:04:30.030> a<00:04:30.120> contract<00:04:30.450> so<00:04:31.430> we 00:04:32.420 --> 00:04:32.430 align:start position:0% here's an example of a contract so we 00:04:32.430 --> 00:04:36.020 align:start position:0% here's an example of a contract so we have<00:04:32.580> a<00:04:32.610> loop<00:04:32.850> there<00:04:33.090> and<00:04:34.130> this<00:04:35.130> example<00:04:35.550> still 00:04:36.020 --> 00:04:36.030 align:start position:0% have a loop there and this example still 00:04:36.030 --> 00:04:42.409 align:start position:0% have a loop there and this example still uses<00:04:36.419> var<00:04:37.260> for<00:04:37.530> variable<00:04:37.740> type<00:04:38.460> and<00:04:40.880> here<00:04:41.880> it's 00:04:42.409 --> 00:04:42.419 align:start position:0% uses var for variable type and here it's 00:04:42.419 --> 00:04:46.659 align:start position:0% uses var for variable type and here it's an<00:04:42.540> issue<00:04:43.669> because<00:04:44.669> the<00:04:45.240> compiler<00:04:45.870> did<00:04:46.380> used 00:04:46.659 --> 00:04:46.669 align:start position:0% an issue because the compiler did used 00:04:46.669 --> 00:04:50.180 align:start position:0% an issue because the compiler did used the<00:04:47.669> type<00:04:47.940> of<00:04:48.270> the<00:04:48.450> variable<00:04:48.600> I<00:04:49.080> to<00:04:49.919> an 00:04:50.180 --> 00:04:50.190 align:start position:0% the type of the variable I to an 00:04:50.190 --> 00:04:54.680 align:start position:0% the type of the variable I to an unsigned<00:04:50.790> 8-bit<00:04:51.710> and<00:04:52.710> so<00:04:53.070> the<00:04:53.220> maximum<00:04:53.460> is<00:04:53.730> 255 00:04:54.680 --> 00:04:54.690 align:start position:0% unsigned 8-bit and so the maximum is 255 00:04:54.690 --> 00:04:57.770 align:start position:0% unsigned 8-bit and so the maximum is 255 so<00:04:55.200> this<00:04:55.620> condition<00:04:56.190> will<00:04:56.370> always<00:04:57.300> be<00:04:57.570> true 00:04:57.770 --> 00:04:57.780 align:start position:0% so this condition will always be true 00:04:57.780 --> 00:05:00.620 align:start position:0% so this condition will always be true which<00:04:58.440> means<00:04:58.710> that<00:04:59.460> this<00:04:59.580> will<00:04:59.640> result<00:05:00.330> in<00:05:00.510> an 00:05:00.620 --> 00:05:00.630 align:start position:0% which means that this will result in an 00:05:00.630 --> 00:05:04.460 align:start position:0% which means that this will result in an infinite<00:05:01.050> loop<00:05:02.060> so<00:05:03.060> now<00:05:03.660> you<00:05:03.720> have<00:05:04.020> to<00:05:04.169> be<00:05:04.290> more 00:05:04.460 --> 00:05:04.470 align:start position:0% infinite loop so now you have to be more 00:05:04.470 --> 00:05:06.830 align:start position:0% infinite loop so now you have to be more explicit<00:05:04.770> about<00:05:05.490> the<00:05:05.669> type<00:05:05.910> and<00:05:06.180> virus<00:05:06.660> now 00:05:06.830 --> 00:05:06.840 align:start position:0% explicit about the type and virus now 00:05:06.840 --> 00:05:10.670 align:start position:0% explicit about the type and virus now disallowed<00:05:07.730> which<00:05:08.730> means<00:05:09.200> you<00:05:10.200> have<00:05:10.410> to 00:05:10.670 --> 00:05:10.680 align:start position:0% disallowed which means you have to 00:05:10.680 --> 00:05:15.730 align:start position:0% disallowed which means you have to declare<00:05:11.430> the<00:05:11.730> type<00:05:12.210> of<00:05:12.450> the<00:05:12.750> variable<00:05:12.900> I<00:05:14.120> and 00:05:15.730 --> 00:05:15.740 align:start position:0% declare the type of the variable I and 00:05:15.740 --> 00:05:22.969 align:start position:0% declare the type of the variable I and now<00:05:16.740> it<00:05:16.860> will<00:05:16.979> be<00:05:17.040> fine<00:05:19.130> so<00:05:20.419> next<00:05:21.419> thing<00:05:21.979> are 00:05:22.969 --> 00:05:22.979 align:start position:0% now it will be fine so next thing are 00:05:22.979 --> 00:05:29.600 align:start position:0% now it will be fine so next thing are explicit<00:05:23.760> visibility's<00:05:26.930> so<00:05:28.400> for<00:05:29.400> another 00:05:29.600 --> 00:05:29.610 align:start position:0% explicit visibility's so for another 00:05:29.610 --> 00:05:33.290 align:start position:0% explicit visibility's so for another example<00:05:29.820> here<00:05:30.570> so<00:05:31.460> we<00:05:32.460> have<00:05:32.580> a<00:05:32.610> contract 00:05:33.290 --> 00:05:33.300 align:start position:0% example here so we have a contract 00:05:33.300 --> 00:05:36.890 align:start position:0% example here so we have a contract here<00:05:33.780> and<00:05:34.050> it<00:05:34.500> has<00:05:34.680> an<00:05:34.979> owner<00:05:35.539> it<00:05:36.539> has<00:05:36.870> a 00:05:36.890 --> 00:05:36.900 align:start position:0% here and it has an owner it has a 00:05:36.900 --> 00:05:39.080 align:start position:0% here and it has an owner it has a constructor<00:05:37.440> that<00:05:37.620> calls<00:05:38.070> an<00:05:38.490> initialize 00:05:39.080 --> 00:05:39.090 align:start position:0% constructor that calls an initialize 00:05:39.090 --> 00:05:41.450 align:start position:0% constructor that calls an initialize function<00:05:39.270> and<00:05:39.780> here<00:05:40.530> in<00:05:40.710> the<00:05:40.890> initialized 00:05:41.450 --> 00:05:41.460 align:start position:0% function and here in the initialized 00:05:41.460 --> 00:05:45.080 align:start position:0% function and here in the initialized function<00:05:42.950> the<00:05:43.950> owner<00:05:44.190> will<00:05:44.340> be<00:05:44.490> said<00:05:44.729> the 00:05:45.080 --> 00:05:45.090 align:start position:0% function the owner will be said the 00:05:45.090 --> 00:05:48.050 align:start position:0% function the owner will be said the caller<00:05:45.300> will<00:05:45.510> be<00:05:45.690> the<00:05:46.289> owner<00:05:46.729> the<00:05:47.729> caller<00:05:47.910> of 00:05:48.050 --> 00:05:48.060 align:start position:0% caller will be the owner the caller of 00:05:48.060 --> 00:05:51.310 align:start position:0% caller will be the owner the caller of the<00:05:48.120> initialized<00:05:48.600> function<00:05:48.990> so<00:05:49.860> and<00:05:50.250> now<00:05:50.580> if 00:05:51.310 --> 00:05:51.320 align:start position:0% the initialized function so and now if 00:05:51.320 --> 00:05:54.950 align:start position:0% the initialized function so and now if withdrawal<00:05:52.320> is<00:05:52.590> called<00:05:53.450> there's<00:05:54.450> the<00:05:54.600> require 00:05:54.950 --> 00:05:54.960 align:start position:0% withdrawal is called there's the require 00:05:54.960 --> 00:05:58.370 align:start position:0% withdrawal is called there's the require that<00:05:55.710> the<00:05:56.550> owner<00:05:56.700> has<00:05:57.000> to<00:05:57.150> be<00:05:57.270> there<00:05:58.260> at<00:05:58.350> the 00:05:58.370 --> 00:05:58.380 align:start position:0% that the owner has to be there at the 00:05:58.380 --> 00:06:02.630 align:start position:0% that the owner has to be there at the caller<00:05:59.300> and<00:06:00.300> then<00:06:01.070> the<00:06:02.070> balance<00:06:02.370> gets 00:06:02.630 --> 00:06:02.640 align:start position:0% caller and then the balance gets 00:06:02.640 --> 00:06:06.610 align:start position:0% caller and then the balance gets transferred<00:06:03.320> so<00:06:04.320> the<00:06:04.620> problem<00:06:04.950> here<00:06:05.250> is<00:06:05.400> that 00:06:06.610 --> 00:06:06.620 align:start position:0% transferred so the problem here is that 00:06:06.620 --> 00:06:09.080 align:start position:0% transferred so the problem here is that functions<00:06:07.620> are<00:06:08.010> the<00:06:08.460> visibility<00:06:09.000> of 00:06:09.080 --> 00:06:09.090 align:start position:0% functions are the visibility of 00:06:09.090 --> 00:06:12.620 align:start position:0% functions are the visibility of functions<00:06:09.479> is<00:06:10.320> public<00:06:10.770> by<00:06:10.919> default<00:06:11.039> so<00:06:12.000> anyone 00:06:12.620 --> 00:06:12.630 align:start position:0% functions is public by default so anyone 00:06:12.630 --> 00:06:15.110 align:start position:0% functions is public by default so anyone from<00:06:12.900> outside<00:06:13.110> could<00:06:13.979> call<00:06:14.250> this<00:06:14.550> initialized 00:06:15.110 --> 00:06:15.120 align:start position:0% from outside could call this initialized 00:06:15.120 --> 00:06:18.260 align:start position:0% from outside could call this initialized function<00:06:15.539> and<00:06:15.720> then<00:06:16.500> also<00:06:16.710> the<00:06:17.700> requirement 00:06:18.260 --> 00:06:18.270 align:start position:0% function and then also the requirement 00:06:18.270 --> 00:06:21.080 align:start position:0% function and then also the requirement would<00:06:18.390> hold<00:06:18.660> the<00:06:19.260> withdraw<00:06:19.680> so<00:06:20.070> capir<00:06:20.880> then 00:06:21.080 --> 00:06:21.090 align:start position:0% would hold the withdraw so capir then 00:06:21.090 --> 00:06:23.860 align:start position:0% would hold the withdraw so capir then also<00:06:21.330> withdrawn 00:06:23.860 --> 00:06:23.870 align:start position:0% also withdrawn 00:06:23.870 --> 00:06:27.520 align:start position:0% also withdrawn and<00:06:24.290> we<00:06:25.100> changed<00:06:25.430> that<00:06:25.550> so<00:06:26.260> the<00:06:27.260> visibility 00:06:27.520 --> 00:06:27.530 align:start position:0% and we changed that so the visibility 00:06:27.530 --> 00:06:29.470 align:start position:0% and we changed that so the visibility specifiers<00:06:28.280> now<00:06:28.580> mandatory 00:06:29.470 --> 00:06:29.480 align:start position:0% specifiers now mandatory 00:06:29.480 --> 00:06:32.670 align:start position:0% specifiers now mandatory what<00:06:30.260> doesn't<00:06:30.470> mean<00:06:31.040> so<00:06:31.370> here<00:06:32.360> the 00:06:32.670 --> 00:06:32.680 align:start position:0% what doesn't mean so here the 00:06:32.680 --> 00:06:35.439 align:start position:0% what doesn't mean so here the constructor<00:06:33.680> got<00:06:34.010> visibility<00:06:34.669> public<00:06:35.090> and 00:06:35.439 --> 00:06:35.449 align:start position:0% constructor got visibility public and 00:06:35.449 --> 00:06:38.920 align:start position:0% constructor got visibility public and the<00:06:36.320> initialized<00:06:36.770> function<00:06:37.250> is<00:06:38.060> now<00:06:38.270> internal 00:06:38.920 --> 00:06:38.930 align:start position:0% the initialized function is now internal 00:06:38.930 --> 00:06:40.629 align:start position:0% the initialized function is now internal which<00:06:39.199> means<00:06:39.440> that<00:06:39.590> can<00:06:39.740> only<00:06:40.040> be<00:06:40.310> called 00:06:40.629 --> 00:06:40.639 align:start position:0% which means that can only be called 00:06:40.639 --> 00:06:46.689 align:start position:0% which means that can only be called internally<00:06:43.000> so<00:06:44.139> that's<00:06:45.139> and<00:06:45.979> then<00:06:46.190> here<00:06:46.580> you 00:06:46.689 --> 00:06:46.699 align:start position:0% internally so that's and then here you 00:06:46.699 --> 00:06:51.040 align:start position:0% internally so that's and then here you can<00:06:46.760> see<00:06:46.910> that<00:06:48.699> the<00:06:49.699> with<00:06:49.910> the<00:06:50.360> requirement<00:06:50.960> of 00:06:51.040 --> 00:06:51.050 align:start position:0% can see that the with the requirement of 00:06:51.050 --> 00:06:54.370 align:start position:0% can see that the with the requirement of someone<00:06:51.440> from<00:06:52.100> a<00:06:52.310> if<00:06:52.880> the<00:06:53.389> with<00:06:53.570> Ron<00:06:53.780> is<00:06:54.050> called 00:06:54.370 --> 00:06:54.380 align:start position:0% someone from a if the with Ron is called 00:06:54.380 --> 00:07:00.780 align:start position:0% someone from a if the with Ron is called then<00:06:55.100> the<00:06:55.580> requirement<00:06:56.570> will<00:06:57.440> be<00:06:57.500> true<00:06:57.830> here 00:07:00.780 --> 00:07:00.790 align:start position:0% 00:07:00.790 --> 00:07:03.300 align:start position:0% all<00:07:01.790> right 00:07:03.300 --> 00:07:03.310 align:start position:0% all right 00:07:03.310 --> 00:07:08.740 align:start position:0% all right explicit<00:07:04.310> data<00:07:04.430> locations<00:07:07.300> so<00:07:08.300> I've<00:07:08.600> got 00:07:08.740 --> 00:07:08.750 align:start position:0% explicit data locations so I've got 00:07:08.750 --> 00:07:11.050 align:start position:0% explicit data locations so I've got another<00:07:08.840> example<00:07:09.560> so<00:07:10.430> here<00:07:10.760> we<00:07:10.910> have<00:07:11.030> a 00:07:11.050 --> 00:07:11.060 align:start position:0% another example so here we have a 00:07:11.060 --> 00:07:13.120 align:start position:0% another example so here we have a contract<00:07:11.600> and<00:07:11.900> you<00:07:11.960> have<00:07:12.500> a<00:07:12.530> struct<00:07:12.860> called 00:07:13.120 --> 00:07:13.130 align:start position:0% contract and you have a struct called 00:07:13.130 --> 00:07:16.659 align:start position:0% contract and you have a struct called data<00:07:13.430> and<00:07:13.820> we<00:07:14.720> have<00:07:14.870> an<00:07:14.960> array<00:07:15.229> of<00:07:15.500> this<00:07:16.310> struct 00:07:16.659 --> 00:07:16.669 align:start position:0% data and we have an array of this struct 00:07:16.669 --> 00:07:23.650 align:start position:0% data and we have an array of this struct and<00:07:18.460> the<00:07:19.460> function<00:07:19.850> f<00:07:20.300> and<00:07:22.240> here<00:07:23.240> we're<00:07:23.479> going 00:07:23.650 --> 00:07:23.660 align:start position:0% and the function f and here we're going 00:07:23.660 --> 00:07:28.629 align:start position:0% and the function f and here we're going to<00:07:24.010> access<00:07:25.010> this<00:07:25.970> this<00:07:26.900> array<00:07:27.340> and<00:07:28.340> stored 00:07:28.629 --> 00:07:28.639 align:start position:0% to access this this array and stored 00:07:28.639 --> 00:07:36.190 align:start position:0% to access this this array and stored into<00:07:29.169> the<00:07:30.729> variable<00:07:31.729> called<00:07:32.150> member<00:07:34.450> and<00:07:35.450> as<00:07:36.080> I 00:07:36.190 --> 00:07:36.200 align:start position:0% into the variable called member and as I 00:07:36.200 --> 00:07:38.620 align:start position:0% into the variable called member and as I said<00:07:36.260> the<00:07:36.680> location<00:07:37.100> specifier<00:07:37.669> is<00:07:38.389> now 00:07:38.620 --> 00:07:38.630 align:start position:0% said the location specifier is now 00:07:38.630 --> 00:07:43.600 align:start position:0% said the location specifier is now mandatory<00:07:39.190> so<00:07:40.360> you<00:07:41.360> have<00:07:41.570> to<00:07:41.780> use<00:07:42.610> storage 00:07:43.600 --> 00:07:43.610 align:start position:0% mandatory so you have to use storage 00:07:43.610 --> 00:07:51.760 align:start position:0% mandatory so you have to use storage here<00:07:44.510> in<00:07:44.690> this<00:07:44.840> case<00:07:50.050> okay 00:07:51.760 --> 00:07:51.770 align:start position:0% here in this case okay 00:07:51.770 --> 00:07:56.379 align:start position:0% here in this case okay so<00:07:52.430> storage<00:07:53.180> references<00:07:54.910> it's<00:07:55.910> the<00:07:56.180> same 00:07:56.379 --> 00:07:56.389 align:start position:0% so storage references it's the same 00:07:56.389 --> 00:08:00.430 align:start position:0% so storage references it's the same example<00:07:56.960> that<00:07:57.229> I<00:07:57.650> had<00:07:57.889> before<00:07:58.070> so<00:07:59.200> we<00:08:00.200> still 00:08:00.430 --> 00:08:00.440 align:start position:0% example that I had before so we still 00:08:00.440 --> 00:08:02.050 align:start position:0% example that I had before so we still have<00:08:00.590> destruct<00:08:00.979> we<00:08:01.160> still<00:08:01.460> have<00:08:01.639> this<00:08:01.760> every 00:08:02.050 --> 00:08:02.060 align:start position:0% have destruct we still have this every 00:08:02.060 --> 00:08:08.010 align:start position:0% have destruct we still have this every year<00:08:02.360> and<00:08:02.570> we<00:08:02.960> have<00:08:03.139> the<00:08:03.349> function<00:08:03.740> and<00:08:05.260> we<00:08:06.260> are 00:08:08.010 --> 00:08:08.020 align:start position:0% year and we have the function and we are 00:08:08.020 --> 00:08:15.100 align:start position:0% year and we have the function and we are initializing<00:08:09.020> your<00:08:09.940> member<00:08:11.080> and<00:08:13.930> setting<00:08:14.930> the 00:08:15.100 --> 00:08:15.110 align:start position:0% initializing your member and setting the 00:08:15.110 --> 00:08:16.990 align:start position:0% initializing your member and setting the name<00:08:15.260> that<00:08:15.440> was<00:08:15.620> given<00:08:15.710> as<00:08:16.190> a<00:08:16.220> parameter<00:08:16.430> to 00:08:16.990 --> 00:08:17.000 align:start position:0% name that was given as a parameter to 00:08:17.000 --> 00:08:23.320 align:start position:0% name that was given as a parameter to the<00:08:17.150> function<00:08:17.919> to<00:08:19.270> the<00:08:20.270> member<00:08:20.570> name<00:08:21.430> of<00:08:22.430> the 00:08:23.320 --> 00:08:23.330 align:start position:0% the function to the member name of the 00:08:23.330 --> 00:08:26.409 align:start position:0% the function to the member name of the data<00:08:23.510> and<00:08:23.810> then<00:08:24.560> we're<00:08:24.860> pushing<00:08:25.070> this<00:08:25.419> into 00:08:26.409 --> 00:08:26.419 align:start position:0% data and then we're pushing this into 00:08:26.419 --> 00:08:31.750 align:start position:0% data and then we're pushing this into the<00:08:26.690> array<00:08:29.830> and<00:08:30.830> now<00:08:31.070> they<00:08:31.340> have<00:08:31.520> to<00:08:31.729> be 00:08:31.750 --> 00:08:31.760 align:start position:0% the array and now they have to be 00:08:31.760 --> 00:08:34.659 align:start position:0% the array and now they have to be initialized<00:08:32.510> so<00:08:32.959> the<00:08:33.469> background<00:08:34.099> of<00:08:34.219> this<00:08:34.400> is 00:08:34.659 --> 00:08:34.669 align:start position:0% initialized so the background of this is 00:08:34.669 --> 00:08:36.579 align:start position:0% initialized so the background of this is that<00:08:35.270> we<00:08:35.450> have<00:08:35.479> a<00:08:35.659> component<00:08:36.020> and<00:08:36.530> the 00:08:36.579 --> 00:08:36.589 align:start position:0% that we have a component and the 00:08:36.589 --> 00:08:37.700 align:start position:0% that we have a component and the compiler 00:08:37.700 --> 00:08:37.710 align:start position:0% compiler 00:08:37.710 --> 00:08:41.870 align:start position:0% compiler that<00:08:37.890> tried<00:08:38.550> to<00:08:38.970> find<00:08:39.330> out<00:08:39.540> if<00:08:40.490> I've<00:08:41.490> storage 00:08:41.870 --> 00:08:41.880 align:start position:0% that tried to find out if I've storage 00:08:41.880 --> 00:08:44.690 align:start position:0% that tried to find out if I've storage references<00:08:42.720> were<00:08:43.320> initialized<00:08:44.010> before<00:08:44.190> and 00:08:44.690 --> 00:08:44.700 align:start position:0% references were initialized before and 00:08:44.700 --> 00:08:47.660 align:start position:0% references were initialized before and because<00:08:45.660> in<00:08:45.810> some<00:08:46.050> cases<00:08:46.290> that<00:08:47.220> was<00:08:47.400> not 00:08:47.660 --> 00:08:47.670 align:start position:0% because in some cases that was not 00:08:47.670 --> 00:08:50.960 align:start position:0% because in some cases that was not possible<00:08:48.450> so<00:08:49.260> the<00:08:50.100> decision<00:08:50.520> was<00:08:50.550> made<00:08:50.700> to 00:08:50.960 --> 00:08:50.970 align:start position:0% possible so the decision was made to 00:08:50.970 --> 00:08:54.280 align:start position:0% possible so the decision was made to make<00:08:51.480> it<00:08:51.510> explicit<00:08:52.050> so<00:08:52.890> that<00:08:53.400> you<00:08:53.670> have<00:08:53.850> to 00:08:54.280 --> 00:08:54.290 align:start position:0% make it explicit so that you have to 00:08:54.290 --> 00:08:57.020 align:start position:0% make it explicit so that you have to initialize<00:08:55.290> storage<00:08:55.860> members<00:08:56.280> storage 00:08:57.020 --> 00:08:57.030 align:start position:0% initialize storage members storage 00:08:57.030 --> 00:09:04.090 align:start position:0% initialize storage members storage references<00:08:57.780> before<00:08:58.470> using<00:08:58.890> them 00:09:04.090 --> 00:09:04.100 align:start position:0% 00:09:04.100 --> 00:09:13.310 align:start position:0% alright<00:09:05.100> so<00:09:05.550> scoping<00:09:06.360> rules<00:09:10.220> before<00:09:11.220> 0<00:09:11.880> 5<00:09:12.120> 0<00:09:12.320> we 00:09:13.310 --> 00:09:13.320 align:start position:0% alright so scoping rules before 0 5 0 we 00:09:13.320 --> 00:09:16.550 align:start position:0% alright so scoping rules before 0 5 0 we had<00:09:13.610> JavaScript<00:09:14.610> like<00:09:14.790> scoping<00:09:15.360> rules<00:09:15.510> so<00:09:16.290> in 00:09:16.550 --> 00:09:16.560 align:start position:0% had JavaScript like scoping rules so in 00:09:16.560 --> 00:09:18.800 align:start position:0% had JavaScript like scoping rules so in this<00:09:16.680> example<00:09:16.860> you<00:09:17.310> have<00:09:17.700> to<00:09:17.850> revive<00:09:18.180> arrival 00:09:18.800 --> 00:09:18.810 align:start position:0% this example you have to revive arrival 00:09:18.810 --> 00:09:24.200 align:start position:0% this example you have to revive arrival I<00:09:19.050> and<00:09:19.970> it's<00:09:20.970> declare<00:09:21.720> and<00:09:21.960> and<00:09:22.410> there<00:09:23.220> the<00:09:23.520> 3 00:09:24.200 --> 00:09:24.210 align:start position:0% I and it's declare and and there the 3 00:09:24.210 --> 00:09:27.920 align:start position:0% I and it's declare and and there the 3 is<00:09:24.450> assigned<00:09:24.810> to<00:09:25.490> to<00:09:26.490> it<00:09:26.700> before<00:09:26.880> it<00:09:27.660> was 00:09:27.920 --> 00:09:27.930 align:start position:0% is assigned to to it before it was 00:09:27.930 --> 00:09:33.130 align:start position:0% is assigned to to it before it was initialized<00:09:29.810> and<00:09:30.810> because<00:09:31.620> one<00:09:31.980> of<00:09:32.010> the<00:09:32.250> goals 00:09:33.130 --> 00:09:33.140 align:start position:0% initialized and because one of the goals 00:09:33.140 --> 00:09:38.810 align:start position:0% initialized and because one of the goals was<00:09:34.140> to<00:09:34.410> be<00:09:35.010> more<00:09:35.220> explicit<00:09:37.040> we<00:09:38.040> also<00:09:38.250> changed 00:09:38.810 --> 00:09:38.820 align:start position:0% was to be more explicit we also changed 00:09:38.820 --> 00:09:43.130 align:start position:0% was to be more explicit we also changed that<00:09:39.030> to<00:09:39.570> block<00:09:40.410> scoped<00:09:41.180> c99<00:09:42.180> style<00:09:42.600> scoping 00:09:43.130 --> 00:09:43.140 align:start position:0% that to block scoped c99 style scoping 00:09:43.140 --> 00:09:50.870 align:start position:0% that to block scoped c99 style scoping rules<00:09:45.920> yeah<00:09:46.980> and<00:09:47.360> so<00:09:48.360> here<00:09:49.100> for<00:09:50.100> the<00:09:50.400> two<00:09:50.670> for 00:09:50.870 --> 00:09:50.880 align:start position:0% rules yeah and so here for the two for 00:09:50.880 --> 00:09:59.120 align:start position:0% rules yeah and so here for the two for loops<00:09:50.970> that<00:09:51.150> you<00:09:51.210> can<00:09:51.480> see<00:09:52.250> the<00:09:56.930> is<00:09:58.130> declared 00:09:59.120 --> 00:09:59.130 align:start position:0% loops that you can see the is declared 00:09:59.130 --> 00:10:02.960 align:start position:0% loops that you can see the is declared also<00:09:59.790> in<00:10:00.630> this<00:10:00.920> the<00:10:01.920> for<00:10:02.130> loop<00:10:02.310> and<00:10:02.520> it's 00:10:02.960 --> 00:10:02.970 align:start position:0% also in this the for loop and it's 00:10:02.970 --> 00:10:06.380 align:start position:0% also in this the for loop and it's visible<00:10:03.330> only<00:10:03.780> for<00:10:04.260> in<00:10:04.560> this<00:10:05.160> block<00:10:05.400> so<00:10:05.760> that's 00:10:06.380 --> 00:10:06.390 align:start position:0% visible only for in this block so that's 00:10:06.390 --> 00:10:09.170 align:start position:0% visible only for in this block so that's the<00:10:06.570> reason<00:10:06.750> why<00:10:07.130> you<00:10:08.130> can<00:10:08.310> use<00:10:08.340> you<00:10:08.880> have<00:10:09.030> to 00:10:09.170 --> 00:10:09.180 align:start position:0% the reason why you can use you have to 00:10:09.180 --> 00:10:12.020 align:start position:0% the reason why you can use you have to really<00:10:09.450> clear<00:10:09.780> it<00:10:09.990> in<00:10:10.620> the<00:10:10.770> second<00:10:11.130> in<00:10:11.910> the 00:10:12.020 --> 00:10:12.030 align:start position:0% really clear it in the second in the 00:10:12.030 --> 00:10:18.620 align:start position:0% really clear it in the second in the second<00:10:12.330> loop<00:10:16.070> then<00:10:17.070> we<00:10:17.180> introduce<00:10:18.180> new 00:10:18.620 --> 00:10:18.630 align:start position:0% second loop then we introduce new 00:10:18.630 --> 00:10:22.520 align:start position:0% second loop then we introduce new constructor<00:10:19.440> syntax<00:10:19.890> so<00:10:21.320> what<00:10:22.320> does<00:10:22.500> that 00:10:22.520 --> 00:10:22.530 align:start position:0% constructor syntax so what does that 00:10:22.530 --> 00:10:29.780 align:start position:0% constructor syntax so what does that mean<00:10:25.010> this<00:10:26.010> is<00:10:26.070> an<00:10:26.430> old<00:10:27.060> example<00:10:28.010> so<00:10:29.010> I<00:10:29.430> took 00:10:29.780 --> 00:10:29.790 align:start position:0% mean this is an old example so I took 00:10:29.790 --> 00:10:32.420 align:start position:0% mean this is an old example so I took the<00:10:30.060> I<00:10:30.900> took<00:10:31.410> the<00:10:31.500> contract<00:10:31.770> that<00:10:31.950> you've<00:10:32.190> seen 00:10:32.420 --> 00:10:32.430 align:start position:0% the I took the contract that you've seen 00:10:32.430 --> 00:10:35.600 align:start position:0% the I took the contract that you've seen before<00:10:32.580> so<00:10:33.590> here<00:10:34.590> you<00:10:34.740> can<00:10:34.860> see<00:10:35.100> and<00:10:35.460> the 00:10:35.600 --> 00:10:35.610 align:start position:0% before so here you can see and the 00:10:35.610 --> 00:10:37.910 align:start position:0% before so here you can see and the contract<00:10:36.000> is<00:10:36.090> called<00:10:36.360> old<00:10:36.780> and<00:10:37.020> before 00:10:37.910 --> 00:10:37.920 align:start position:0% contract is called old and before 00:10:37.920 --> 00:10:41.480 align:start position:0% contract is called old and before zero-five-zero<00:10:39.080> to<00:10:40.080> define<00:10:40.530> a<00:10:40.560> constructor 00:10:41.480 --> 00:10:41.490 align:start position:0% zero-five-zero to define a constructor 00:10:41.490 --> 00:10:43.510 align:start position:0% zero-five-zero to define a constructor you<00:10:41.820> had<00:10:42.060> to<00:10:42.270> use 00:10:43.510 --> 00:10:43.520 align:start position:0% you had to use 00:10:43.520 --> 00:10:45.640 align:start position:0% you had to use had<00:10:43.880> to<00:10:44.000> declare<00:10:44.330> a<00:10:44.390> function<00:10:44.720> with<00:10:45.500> the<00:10:45.620> same 00:10:45.640 --> 00:10:45.650 align:start position:0% had to declare a function with the same 00:10:45.650 --> 00:10:51.490 align:start position:0% had to declare a function with the same name<00:10:46.100> as<00:10:46.400> the<00:10:46.460> contract<00:10:48.580> but<00:10:49.930> again<00:10:50.930> to<00:10:51.350> be 00:10:51.490 --> 00:10:51.500 align:start position:0% name as the contract but again to be 00:10:51.500 --> 00:10:55.840 align:start position:0% name as the contract but again to be more<00:10:51.770> explicit<00:10:52.190> about<00:10:53.150> that<00:10:53.410> and<00:10:54.410> to<00:10:54.860> prevent 00:10:55.840 --> 00:10:55.850 align:start position:0% more explicit about that and to prevent 00:10:55.850 --> 00:11:00.040 align:start position:0% more explicit about that and to prevent mistakes<00:10:57.460> we<00:10:58.460> introduced<00:10:59.030> a<00:10:59.480> new<00:10:59.780> keyword 00:11:00.040 --> 00:11:00.050 align:start position:0% mistakes we introduced a new keyword 00:11:00.050 --> 00:11:05.620 align:start position:0% mistakes we introduced a new keyword called<00:11:00.680> constructor<00:11:01.580> and<00:11:03.910> it<00:11:04.910> has<00:11:05.120> to<00:11:05.270> be<00:11:05.420> used 00:11:05.620 --> 00:11:05.630 align:start position:0% called constructor and it has to be used 00:11:05.630 --> 00:11:09.610 align:start position:0% called constructor and it has to be used to<00:11:05.810> D<00:11:06.260> to<00:11:06.620> declare<00:11:06.980> the<00:11:07.130> constructor<00:11:07.700> and<00:11:08.620> it's 00:11:09.610 --> 00:11:09.620 align:start position:0% to D to declare the constructor and it's 00:11:09.620 --> 00:11:11.950 align:start position:0% to D to declare the constructor and it's not<00:11:09.800> allowed<00:11:10.070> anymore<00:11:10.430> to<00:11:11.420> have<00:11:11.930> a 00:11:11.950 --> 00:11:11.960 align:start position:0% not allowed anymore to have a 00:11:11.960 --> 00:11:13.690 align:start position:0% not allowed anymore to have a constructor<00:11:12.620> that<00:11:12.650> has<00:11:13.010> the<00:11:13.160> same<00:11:13.340> name<00:11:13.670> as 00:11:13.690 --> 00:11:13.700 align:start position:0% constructor that has the same name as 00:11:13.700 --> 00:11:20.920 align:start position:0% constructor that has the same name as the<00:11:14.600> contract<00:11:19.300> what<00:11:20.300> next 00:11:20.920 --> 00:11:20.930 align:start position:0% the contract what next 00:11:20.930 --> 00:11:30.220 align:start position:0% the contract what next so<00:11:21.460> emit<00:11:22.460> for<00:11:22.790> events<00:11:27.730> here<00:11:28.730> again<00:11:29.030> the<00:11:29.840> the 00:11:30.220 --> 00:11:30.230 align:start position:0% so emit for events here again the the 00:11:30.230 --> 00:11:31.660 align:start position:0% so emit for events here again the the example<00:11:30.530> that<00:11:30.680> you've<00:11:30.920> seen<00:11:31.100> before 00:11:31.660 --> 00:11:31.670 align:start position:0% example that you've seen before 00:11:31.670 --> 00:11:35.770 align:start position:0% example that you've seen before so<00:11:32.330> we<00:11:32.750> have<00:11:32.960> a<00:11:32.990> contract<00:11:33.530> here<00:11:33.920> and<00:11:34.390> it<00:11:35.390> has<00:11:35.600> an 00:11:35.770 --> 00:11:35.780 align:start position:0% so we have a contract here and it has an 00:11:35.780 --> 00:11:39.850 align:start position:0% so we have a contract here and it has an event<00:11:36.140> called<00:11:37.040> withdrawn<00:11:38.260> and<00:11:39.260> so<00:11:39.500> we<00:11:39.740> have 00:11:39.850 --> 00:11:39.860 align:start position:0% event called withdrawn and so we have 00:11:39.860 --> 00:11:42.700 align:start position:0% event called withdrawn and so we have the<00:11:40.010> function<00:11:40.130> withdrawn<00:11:40.910> it's<00:11:41.750> from<00:11:42.440> from 00:11:42.700 --> 00:11:42.710 align:start position:0% the function withdrawn it's from from 00:11:42.710 --> 00:11:45.820 align:start position:0% the function withdrawn it's from from the<00:11:42.830> example<00:11:43.160> before<00:11:43.280> so<00:11:44.210> we<00:11:45.020> have<00:11:45.320> to<00:11:45.470> require 00:11:45.820 --> 00:11:45.830 align:start position:0% the example before so we have to require 00:11:45.830 --> 00:11:49.170 align:start position:0% the example before so we have to require again<00:11:46.130> and<00:11:46.430> we<00:11:46.790> have<00:11:46.970> to<00:11:47.500> transfer<00:11:48.500> call<00:11:48.710> and 00:11:49.170 --> 00:11:49.180 align:start position:0% again and we have to transfer call and 00:11:49.180 --> 00:11:54.820 align:start position:0% again and we have to transfer call and then<00:11:50.180> the<00:11:50.810> emit<00:11:51.110> the<00:11:51.530> event<00:11:51.800> is<00:11:51.980> submitted<00:11:53.830> but 00:11:54.820 --> 00:11:54.830 align:start position:0% then the emit the event is submitted but 00:11:54.830 --> 00:11:57.250 align:start position:0% then the emit the event is submitted but this<00:11:55.010> can<00:11:55.250> also<00:11:55.490> be<00:11:55.640> confusing<00:11:56.360> because<00:11:56.690> it 00:11:57.250 --> 00:11:57.260 align:start position:0% this can also be confusing because it 00:11:57.260 --> 00:11:59.470 align:start position:0% this can also be confusing because it could<00:11:57.500> also<00:11:57.740> be<00:11:57.980> a<00:11:58.400> function<00:11:58.820> call<00:11:59.030> I<00:11:59.270> mean 00:11:59.470 --> 00:11:59.480 align:start position:0% could also be a function call I mean 00:11:59.480 --> 00:12:02.620 align:start position:0% could also be a function call I mean there<00:11:59.660> are<00:11:59.690> coding<00:12:00.050> guidelines<00:12:00.310> that<00:12:01.630> say 00:12:02.620 --> 00:12:02.630 align:start position:0% there are coding guidelines that say 00:12:02.630 --> 00:12:04.330 align:start position:0% there are coding guidelines that say that<00:12:02.960> you<00:12:03.110> should<00:12:03.380> start<00:12:03.620> your<00:12:03.770> function<00:12:04.130> with 00:12:04.330 --> 00:12:04.340 align:start position:0% that you should start your function with 00:12:04.340 --> 00:12:06.910 align:start position:0% that you should start your function with the<00:12:04.430> lowercase<00:12:04.670> letter<00:12:05.120> but<00:12:05.900> if<00:12:06.230> you<00:12:06.410> don't<00:12:06.620> do 00:12:06.910 --> 00:12:06.920 align:start position:0% the lowercase letter but if you don't do 00:12:06.920 --> 00:12:09.430 align:start position:0% the lowercase letter but if you don't do so<00:12:07.430> this<00:12:07.670> can<00:12:07.880> there<00:12:08.270> there<00:12:08.450> can<00:12:08.690> be<00:12:08.720> certain 00:12:09.430 --> 00:12:09.440 align:start position:0% so this can there there can be certain 00:12:09.440 --> 00:12:14.350 align:start position:0% so this can there there can be certain mistakes<00:12:09.860> be<00:12:10.070> making<00:12:12.070> and<00:12:13.070> again<00:12:13.580> to<00:12:14.000> be<00:12:14.150> more 00:12:14.350 --> 00:12:14.360 align:start position:0% mistakes be making and again to be more 00:12:14.360 --> 00:12:17.440 align:start position:0% mistakes be making and again to be more explicit<00:12:14.930> event<00:12:15.530> and<00:12:15.710> vacations<00:12:16.240> must<00:12:17.240> be 00:12:17.440 --> 00:12:17.450 align:start position:0% explicit event and vacations must be 00:12:17.450 --> 00:12:22.570 align:start position:0% explicit event and vacations must be prefixed<00:12:17.840> so<00:12:19.600> here<00:12:20.770> we<00:12:21.770> introduce<00:12:21.920> the<00:12:22.400> mid 00:12:22.570 --> 00:12:22.580 align:start position:0% prefixed so here we introduce the mid 00:12:22.580 --> 00:12:27.580 align:start position:0% prefixed so here we introduce the mid keyboard<00:12:22.940> and<00:12:23.890> if<00:12:24.890> you<00:12:25.070> want<00:12:25.310> to<00:12:26.350> invoke<00:12:27.350> this 00:12:27.580 --> 00:12:27.590 align:start position:0% keyboard and if you want to invoke this 00:12:27.590 --> 00:12:30.490 align:start position:0% keyboard and if you want to invoke this event<00:12:27.980> emit<00:12:28.850> has<00:12:29.030> to<00:12:29.300> be<00:12:29.420> put<00:12:29.810> in<00:12:30.050> front<00:12:30.230> of 00:12:30.490 --> 00:12:30.500 align:start position:0% event emit has to be put in front of 00:12:30.500 --> 00:12:34.760 align:start position:0% event emit has to be put in front of this 00:12:34.760 --> 00:12:34.770 align:start position:0% 00:12:34.770 --> 00:12:41.500 align:start position:0% all<00:12:35.339> right<00:12:35.990> next<00:12:36.990> one<00:12:37.350> address<00:12:37.770> payable<00:12:38.270> so<00:12:39.529> we 00:12:41.500 --> 00:12:41.510 align:start position:0% all right next one address payable so we 00:12:41.510 --> 00:12:46.370 align:start position:0% all right next one address payable so we split<00:12:42.510> the<00:12:43.380> address<00:12:43.740> type<00:12:44.300> so<00:12:45.300> in<00:12:46.230> this 00:12:46.370 --> 00:12:46.380 align:start position:0% split the address type so in this 00:12:46.380 --> 00:12:50.180 align:start position:0% split the address type so in this example<00:12:46.560> you<00:12:47.190> have<00:12:47.490> a<00:12:48.000> target<00:12:48.630> and<00:12:48.870> you<00:12:49.830> want 00:12:50.180 --> 00:12:50.190 align:start position:0% example you have a target and you want 00:12:50.190 --> 00:12:54.620 align:start position:0% example you have a target and you want to<00:12:50.370> transfer<00:12:50.910> one<00:12:51.720> ether<00:12:52.339> and<00:12:53.339> call<00:12:53.730> transfer 00:12:54.620 --> 00:12:54.630 align:start position:0% to transfer one ether and call transfer 00:12:54.630 --> 00:13:00.769 align:start position:0% to transfer one ether and call transfer on<00:12:54.870> this<00:12:55.050> target<00:12:55.320> and<00:12:58.130> now<00:12:59.360> address<00:13:00.360> payable 00:13:00.769 --> 00:13:00.779 align:start position:0% on this target and now address payable 00:13:00.779 --> 00:13:05.030 align:start position:0% on this target and now address payable is<00:13:00.899> required<00:13:01.320> so<00:13:02.690> that<00:13:03.690> means<00:13:03.930> that<00:13:04.440> if<00:13:04.860> you 00:13:05.030 --> 00:13:05.040 align:start position:0% is required so that means that if you 00:13:05.040 --> 00:13:07.220 align:start position:0% is required so that means that if you have<00:13:05.070> an<00:13:05.610> address<00:13:06.000> type<00:13:06.209> that<00:13:06.570> is<00:13:06.690> not<00:13:06.899> payable 00:13:07.220 --> 00:13:07.230 align:start position:0% have an address type that is not payable 00:13:07.230 --> 00:13:09.170 align:start position:0% have an address type that is not payable the<00:13:07.890> transfer<00:13:08.250> function<00:13:08.670> would<00:13:08.910> not<00:13:08.970> be 00:13:09.170 --> 00:13:09.180 align:start position:0% the transfer function would not be 00:13:09.180 --> 00:13:18.560 align:start position:0% the transfer function would not be available<00:13:09.810> on<00:13:10.290> this<00:13:10.890> type<00:13:16.520> then<00:13:17.520> there's<00:13:17.910> a 00:13:18.560 --> 00:13:18.570 align:start position:0% available on this type then there's a 00:13:18.570 --> 00:13:24.710 align:start position:0% available on this type then there's a second<00:13:19.230> example<00:13:19.850> or<00:13:21.589> explicit<00:13:22.589> casts<00:13:22.980> so<00:13:23.760> if 00:13:24.710 --> 00:13:24.720 align:start position:0% second example or explicit casts so if 00:13:24.720 --> 00:13:27.920 align:start position:0% second example or explicit casts so if you<00:13:24.930> want<00:13:25.140> to<00:13:25.700> convert<00:13:26.700> this<00:13:27.149> to<00:13:27.510> an<00:13:27.630> address 00:13:27.920 --> 00:13:27.930 align:start position:0% you want to convert this to an address 00:13:27.930 --> 00:13:33.610 align:start position:0% you want to convert this to an address type<00:13:30.200> you<00:13:31.200> need<00:13:31.350> to<00:13:31.470> be<00:13:31.589> explicit<00:13:32.100> about<00:13:32.160> it<00:13:32.430> so 00:13:33.610 --> 00:13:33.620 align:start position:0% type you need to be explicit about it so 00:13:33.620 --> 00:13:37.760 align:start position:0% type you need to be explicit about it so you<00:13:34.620> have<00:13:34.950> to<00:13:35.160> use<00:13:35.399> a<00:13:36.170> for<00:13:37.170> work<00:13:37.290> function 00:13:37.760 --> 00:13:37.770 align:start position:0% you have to use a for work function 00:13:37.770 --> 00:13:41.630 align:start position:0% you have to use a for work function payable<00:13:38.279> fallback<00:13:38.670> function<00:13:39.089> so<00:13:39.870> that<00:13:40.640> this 00:13:41.630 --> 00:13:41.640 align:start position:0% payable fallback function so that this 00:13:41.640 --> 00:13:49.699 align:start position:0% payable fallback function so that this such<00:13:42.540> that<00:13:42.750> this<00:13:42.899> example<00:13:43.290> would<00:13:44.130> compile<00:13:48.709> so 00:13:49.699 --> 00:13:49.709 align:start position:0% such that this example would compile so 00:13:49.709 --> 00:13:51.920 align:start position:0% such that this example would compile so and<00:13:50.100> then<00:13:50.310> there<00:13:50.520> are<00:13:50.550> few<00:13:51.060> other<00:13:51.240> things<00:13:51.329> that 00:13:51.920 --> 00:13:51.930 align:start position:0% and then there are few other things that 00:13:51.930 --> 00:13:55.100 align:start position:0% and then there are few other things that we<00:13:52.170> changed<00:13:52.649> so<00:13:52.920> with<00:13:53.820> the<00:13:54.000> IV<00:13:54.209> I<00:13:54.240> encode<00:13:54.839> and 00:13:55.100 --> 00:13:55.110 align:start position:0% we changed so with the IV I encode and 00:13:55.110 --> 00:13:59.150 align:start position:0% we changed so with the IV I encode and decode<00:13:55.140> changes<00:13:55.890> and<00:13:56.270> also<00:13:57.410> some<00:13:58.410> changes<00:13:58.620> to 00:13:59.150 --> 00:13:59.160 align:start position:0% decode changes and also some changes to 00:13:59.160 --> 00:14:01.670 align:start position:0% decode changes and also some changes to the<00:13:59.490> call<00:13:59.730> family<00:14:00.120> so<00:14:00.450> called<00:14:00.839> delegate<00:14:01.380> call 00:14:01.670 --> 00:14:01.680 align:start position:0% the call family so called delegate call 00:14:01.680 --> 00:14:05.380 align:start position:0% the call family so called delegate call hijack<00:14:02.630> 256<00:14:03.630> now<00:14:04.260> take<00:14:04.620> a<00:14:04.649> single<00:14:04.950> byte 00:14:05.380 --> 00:14:05.390 align:start position:0% hijack 256 now take a single byte 00:14:05.390 --> 00:14:11.090 align:start position:0% hijack 256 now take a single byte parameter<00:14:06.390> and<00:14:08.329> if<00:14:09.329> you<00:14:09.540> want<00:14:09.779> to<00:14:10.110> if<00:14:10.800> you<00:14:10.950> want 00:14:11.090 --> 00:14:11.100 align:start position:0% parameter and if you want to if you want 00:14:11.100 --> 00:14:14.960 align:start position:0% parameter and if you want to if you want to<00:14:11.160> use<00:14:11.370> it<00:14:11.579> then<00:14:12.089> you<00:14:12.480> have<00:14:12.750> to<00:14:12.990> call<00:14:13.820> have<00:14:14.820> to 00:14:14.960 --> 00:14:14.970 align:start position:0% to use it then you have to call have to 00:14:14.970 --> 00:14:18.079 align:start position:0% to use it then you have to call have to use<00:14:15.120> the<00:14:15.360> API<00:14:15.600> encoder<00:14:16.140> before<00:14:16.709> to<00:14:16.950> encode<00:14:17.790> and 00:14:18.079 --> 00:14:18.089 align:start position:0% use the API encoder before to encode and 00:14:18.089 --> 00:14:23.290 align:start position:0% use the API encoder before to encode and decode<00:14:18.560> the<00:14:19.560> arguments<00:14:20.130> there<00:14:21.170> and<00:14:22.170> also 00:14:23.290 --> 00:14:23.300 align:start position:0% decode the arguments there and also 00:14:23.300 --> 00:14:26.449 align:start position:0% decode the arguments there and also would<00:14:24.300> change<00:14:24.600> something<00:14:24.810> to<00:14:24.990> your<00:14:25.589> view<00:14:26.130> pure 00:14:26.449 --> 00:14:26.459 align:start position:0% would change something to your view pure 00:14:26.459 --> 00:14:29.840 align:start position:0% would change something to your view pure and<00:14:26.790> view<00:14:27.420> pure<00:14:27.630> functions<00:14:28.250> now<00:14:29.250> you<00:14:29.310> study 00:14:29.840 --> 00:14:29.850 align:start position:0% and view pure functions now you study 00:14:29.850 --> 00:14:33.800 align:start position:0% and view pure functions now you study call<00:14:30.170> with<00:14:31.170> the<00:14:31.410> exception<00:14:32.070> that<00:14:32.430> for<00:14:33.360> library 00:14:33.800 --> 00:14:33.810 align:start position:0% call with the exception that for library 00:14:33.810 --> 00:14:36.380 align:start position:0% call with the exception that for library view<00:14:34.110> functions<00:14:34.620> they<00:14:35.430> use<00:14:35.610> delegate<00:14:36.120> call 00:14:36.380 --> 00:14:36.390 align:start position:0% view functions they use delegate call 00:14:36.390 --> 00:14:40.040 align:start position:0% view functions they use delegate call and<00:14:36.800> we<00:14:37.800> also<00:14:37.950> put<00:14:38.279> together<00:14:38.399> a<00:14:39.029> list<00:14:39.779> of 00:14:40.040 --> 00:14:40.050 align:start position:0% and we also put together a list of 00:14:40.050 --> 00:14:41.720 align:start position:0% and we also put together a list of breaking<00:14:40.440> changes 00:14:41.720 --> 00:14:41.730 align:start position:0% breaking changes 00:14:41.730 --> 00:14:44.840 align:start position:0% breaking changes you<00:14:42.299> can<00:14:42.480> sign<00:14:42.689> it<00:14:42.899> our<00:14:43.709> documentation<00:14:44.369> and<00:14:44.819> we 00:14:44.840 --> 00:14:44.850 align:start position:0% you can sign it our documentation and we 00:14:44.850 --> 00:14:50.210 align:start position:0% you can sign it our documentation and we also<00:14:45.809> put<00:14:46.109> together<00:14:48.410> our<00:14:49.410> compiled<00:14:49.980> the<00:14:50.189> list 00:14:50.210 --> 00:14:50.220 align:start position:0% also put together our compiled the list 00:14:50.220 --> 00:14:52.699 align:start position:0% also put together our compiled the list of<00:14:50.609> how<00:14:50.790> you<00:14:50.850> have<00:14:51.509> to<00:14:51.540> change<00:14:51.929> your<00:14:52.139> contracts 00:14:52.699 --> 00:14:52.709 align:start position:0% of how you have to change your contracts 00:14:52.709 --> 00:14:55.489 align:start position:0% of how you have to change your contracts such<00:14:53.369> that<00:14:53.609> they<00:14:53.819> will<00:14:54.119> compile<00:14:54.540> with<00:14:54.779> zero 00:14:55.489 --> 00:14:55.499 align:start position:0% such that they will compile with zero 00:14:55.499 --> 00:15:02.689 align:start position:0% such that they will compile with zero five<00:14:55.679> zero<00:14:59.329> okay<00:15:00.329> so<00:15:00.949> what's<00:15:01.949> what's<00:15:02.339> coming 00:15:02.689 --> 00:15:02.699 align:start position:0% five zero okay so what's what's coming 00:15:02.699 --> 00:15:08.119 align:start position:0% five zero okay so what's what's coming up<00:15:02.819> with<00:15:03.269> the<00:15:03.509> next<00:15:03.660> versions<00:15:06.619> we<00:15:07.619> have<00:15:07.829> fuel 00:15:08.119 --> 00:15:08.129 align:start position:0% up with the next versions we have fuel 00:15:08.129 --> 00:15:11.090 align:start position:0% up with the next versions we have fuel which<00:15:08.609> is<00:15:08.939> a<00:15:08.970> very<00:15:09.269> interesting<00:15:09.660> topic<00:15:10.470> I<00:15:10.859> want 00:15:11.090 --> 00:15:11.100 align:start position:0% which is a very interesting topic I want 00:15:11.100 --> 00:15:14.900 align:start position:0% which is a very interesting topic I want to<00:15:11.129> talk<00:15:11.339> about<00:15:11.489> we<00:15:12.290> introduced<00:15:13.549> some<00:15:14.549> formal 00:15:14.900 --> 00:15:14.910 align:start position:0% to talk about we introduced some formal 00:15:14.910 --> 00:15:18.549 align:start position:0% to talk about we introduced some formal verification<00:15:15.059> and<00:15:15.899> form<00:15:16.350> of<00:15:16.559> the<00:15:16.859> SMT<00:15:17.609> checker 00:15:18.549 --> 00:15:18.559 align:start position:0% verification and form of the SMT checker 00:15:18.559 --> 00:15:21.259 align:start position:0% verification and form of the SMT checker we're<00:15:19.559> planning<00:15:19.980> to<00:15:20.009> do<00:15:20.309> some<00:15:20.819> inheritance 00:15:21.259 --> 00:15:21.269 align:start position:0% we're planning to do some inheritance 00:15:21.269 --> 00:15:24.739 align:start position:0% we're planning to do some inheritance rule<00:15:21.660> changes<00:15:22.579> then<00:15:23.579> also<00:15:23.819> contract<00:15:24.449> metadata 00:15:24.739 --> 00:15:24.749 align:start position:0% rule changes then also contract metadata 00:15:24.749 --> 00:15:31.280 align:start position:0% rule changes then also contract metadata and<00:15:25.259> to<00:15:26.069> avyayam<00:15:26.489> folder<00:15:27.029> v2<00:15:29.389> so<00:15:30.389> what<00:15:30.929> is<00:15:31.049> you 00:15:31.280 --> 00:15:31.290 align:start position:0% and to avyayam folder v2 so what is you 00:15:31.290 --> 00:15:35.150 align:start position:0% and to avyayam folder v2 so what is you I<00:15:31.739> don't<00:15:32.040> know<00:15:32.100> if<00:15:32.929> who<00:15:33.929> have<00:15:34.049> you<00:15:34.259> attended<00:15:34.829> to 00:15:35.150 --> 00:15:35.160 align:start position:0% I don't know if who have you attended to 00:15:35.160 --> 00:15:38.079 align:start position:0% I don't know if who have you attended to Alex<00:15:35.519> talked<00:15:35.699> yesterday<00:15:35.879> and<00:15:36.540> the<00:15:36.899> prism<00:15:37.230> room 00:15:38.079 --> 00:15:38.089 align:start position:0% Alex talked yesterday and the prism room 00:15:38.089 --> 00:15:41.359 align:start position:0% Alex talked yesterday and the prism room so<00:15:39.089> you<00:15:39.779> will<00:15:39.989> is<00:15:40.169> an<00:15:40.379> assembly<00:15:40.799> language<00:15:40.859> and 00:15:41.359 --> 00:15:41.369 align:start position:0% so you will is an assembly language and 00:15:41.369 --> 00:15:43.749 align:start position:0% so you will is an assembly language and it's<00:15:41.850> an<00:15:42.239> intermediate<00:15:42.569> representation 00:15:43.749 --> 00:15:43.759 align:start position:0% it's an intermediate representation 00:15:43.759 --> 00:15:46.939 align:start position:0% it's an intermediate representation internally<00:15:44.759> in<00:15:44.879> the<00:15:44.970> compiler<00:15:45.619> it<00:15:46.619> aids 00:15:46.939 --> 00:15:46.949 align:start position:0% internally in the compiler it aids 00:15:46.949 --> 00:15:49.340 align:start position:0% internally in the compiler it aids auditing<00:15:47.639> the<00:15:47.939> code<00:15:48.149> base<00:15:48.329> and<00:15:48.660> generated 00:15:49.340 --> 00:15:49.350 align:start position:0% auditing the code base and generated 00:15:49.350 --> 00:15:53.829 align:start position:0% auditing the code base and generated code<00:15:49.910> it<00:15:50.910> allows<00:15:51.269> for<00:15:51.749> a<00:15:52.079> lot<00:15:52.230> of<00:15:52.289> optimization 00:15:53.829 --> 00:15:53.839 align:start position:0% code it allows for a lot of optimization 00:15:53.839 --> 00:15:58.179 align:start position:0% code it allows for a lot of optimization and<00:15:54.839> it<00:15:55.410> also<00:15:55.589> allows<00:15:55.949> multiple<00:15:56.249> backends<00:15:56.699> so 00:15:58.179 --> 00:15:58.189 align:start position:0% and it also allows multiple backends so 00:15:58.189 --> 00:16:01.549 align:start position:0% and it also allows multiple backends so solidity<00:15:59.189> could<00:15:59.759> compile<00:16:00.419> to<00:16:00.689> you<00:16:00.869> and<00:16:01.199> then 00:16:01.549 --> 00:16:01.559 align:start position:0% solidity could compile to you and then 00:16:01.559 --> 00:16:06.499 align:start position:0% solidity could compile to you and then in<00:16:01.769> the<00:16:01.919> end<00:16:02.009> to<00:16:02.309> a<00:16:02.819> VM<00:16:03.739> and<00:16:04.819> also<00:16:05.819> solidity<00:16:06.359> to 00:16:06.499 --> 00:16:06.509 align:start position:0% in the end to a VM and also solidity to 00:16:06.509 --> 00:16:09.289 align:start position:0% in the end to a VM and also solidity to you<00:16:07.049> to<00:16:07.410> you<00:16:07.739> was<00:16:07.980> that<00:16:08.429> will<00:16:08.639> be<00:16:08.759> something 00:16:09.289 --> 00:16:09.299 align:start position:0% you to you was that will be something 00:16:09.299 --> 00:16:11.389 align:start position:0% you to you was that will be something that<00:16:10.259> might<00:16:10.350> be<00:16:10.529> interesting<00:16:10.919> in<00:16:11.009> the<00:16:11.069> future 00:16:11.389 --> 00:16:11.399 align:start position:0% that might be interesting in the future 00:16:11.399 --> 00:16:16.309 align:start position:0% that might be interesting in the future and<00:16:11.779> also<00:16:12.889> Viper<00:16:13.889> could<00:16:14.899> and<00:16:15.899> that's 00:16:16.309 --> 00:16:16.319 align:start position:0% and also Viper could and that's 00:16:16.319 --> 00:16:20.269 align:start position:0% and also Viper could and that's empathize<00:16:16.859> use<00:16:17.369> you<00:16:17.699> to<00:16:18.509> also<00:16:18.959> then<00:16:19.279> support 00:16:20.269 --> 00:16:20.279 align:start position:0% empathize use you to also then support 00:16:20.279 --> 00:16:23.929 align:start position:0% empathize use you to also then support EVM<00:16:20.699> or<00:16:21.029> it<00:16:21.239> wasn't<00:16:21.539> back-end<00:16:22.369> and<00:16:23.369> if<00:16:23.850> you 00:16:23.929 --> 00:16:23.939 align:start position:0% EVM or it wasn't back-end and if you 00:16:23.939 --> 00:16:26.299 align:start position:0% EVM or it wasn't back-end and if you want<00:16:24.119> to<00:16:24.239> find<00:16:24.449> out<00:16:24.600> more<00:16:24.989> about<00:16:25.049> you<00:16:25.559> you<00:16:26.279> can 00:16:26.299 --> 00:16:26.309 align:start position:0% want to find out more about you you can 00:16:26.309 --> 00:16:31.939 align:start position:0% want to find out more about you you can also<00:16:26.899> consult<00:16:27.899> our<00:16:28.199> documentation<00:16:28.549> or<00:16:30.949> yeah 00:16:31.939 --> 00:16:31.949 align:start position:0% also consult our documentation or yeah 00:16:31.949 --> 00:16:36.529 align:start position:0% also consult our documentation or yeah and<00:16:32.869> I<00:16:33.869> also<00:16:34.079> brought<00:16:34.289> a<00:16:34.379> short<00:16:35.069> example<00:16:35.539> so 00:16:36.529 --> 00:16:36.539 align:start position:0% and I also brought a short example so 00:16:36.539 --> 00:16:39.079 align:start position:0% and I also brought a short example so that<00:16:36.569> you<00:16:36.839> get<00:16:37.019> an<00:16:37.169> idea<00:16:37.439> of<00:16:37.559> how<00:16:37.980> you'll<00:16:38.249> just 00:16:39.079 --> 00:16:39.089 align:start position:0% that you get an idea of how you'll just 00:16:39.089 --> 00:16:41.840 align:start position:0% that you get an idea of how you'll just look<00:16:39.299> look<00:16:39.779> like<00:16:39.959> and<00:16:40.369> here's<00:16:41.369> the<00:16:41.669> power 00:16:41.840 --> 00:16:41.850 align:start position:0% look look like and here's the power 00:16:41.850 --> 00:16:46.789 align:start position:0% look look like and here's the power function<00:16:42.329> and<00:16:42.629> we<00:16:43.499> have<00:16:43.739> high<00:16:44.730> level<00:16:45.799> high 00:16:46.789 --> 00:16:46.799 align:start position:0% function and we have high level high 00:16:46.799 --> 00:16:50.319 align:start position:0% function and we have high level high level<00:16:47.720> keywords<00:16:48.720> like<00:16:48.959> switch<00:16:49.230> case<00:16:49.649> default 00:16:50.319 --> 00:16:50.329 align:start position:0% level keywords like switch case default 00:16:50.329 --> 00:16:55.110 align:start position:0% level keywords like switch case default but<00:16:51.329> we<00:16:51.449> can<00:16:51.629> also<00:16:51.839> but<00:16:52.379> as<00:16:52.799> you<00:16:52.949> can<00:16:53.100> also<00:16:53.279> see 00:16:55.110 --> 00:16:55.120 align:start position:0% but we can also but as you can also see 00:16:55.120 --> 00:17:00.190 align:start position:0% but we can also but as you can also see multiplication<00:16:56.120> and<00:16:57.050> also<00:16:57.620> dividing<00:16:59.200> there 00:17:00.190 --> 00:17:00.200 align:start position:0% multiplication and also dividing there 00:17:00.200 --> 00:17:03.730 align:start position:0% multiplication and also dividing there it's<00:17:00.710> a<00:17:00.890> representation<00:17:01.250> of<00:17:01.940> up<00:17:02.360> codes<00:17:02.690> and<00:17:03.050> a 00:17:03.730 --> 00:17:03.740 align:start position:0% it's a representation of up codes and a 00:17:03.740 --> 00:17:06.400 align:start position:0% it's a representation of up codes and a more<00:17:03.950> functional<00:17:04.400> style<00:17:04.850> so<00:17:05.450> like<00:17:06.230> I<00:17:06.260> said 00:17:06.400 --> 00:17:06.410 align:start position:0% more functional style so like I said 00:17:06.410 --> 00:17:07.780 align:start position:0% more functional style so like I said before<00:17:06.770> this<00:17:07.250> helps 00:17:07.780 --> 00:17:07.790 align:start position:0% before this helps 00:17:07.790 --> 00:17:11.650 align:start position:0% before this helps this<00:17:08.540> increases<00:17:09.070> readability<00:17:10.070> and<00:17:10.660> also 00:17:11.650 --> 00:17:11.660 align:start position:0% this increases readability and also 00:17:11.660 --> 00:17:16.690 align:start position:0% this increases readability and also helps<00:17:12.050> auditing<00:17:12.589> the<00:17:12.980> code<00:17:14.830> and<00:17:15.830> if<00:17:16.430> you<00:17:16.520> want 00:17:16.690 --> 00:17:16.700 align:start position:0% helps auditing the code and if you want 00:17:16.700 --> 00:17:19.240 align:start position:0% helps auditing the code and if you want to<00:17:16.910> find<00:17:17.720> more<00:17:17.959> about<00:17:18.110> find<00:17:18.920> out<00:17:19.010> more<00:17:19.190> about 00:17:19.240 --> 00:17:19.250 align:start position:0% to find more about find out more about 00:17:19.250 --> 00:17:22.420 align:start position:0% to find more about find out more about Yul<00:17:19.730> and<00:17:20.140> also<00:17:21.140> about<00:17:21.470> the<00:17:21.680> optimization<00:17:22.070> that 00:17:22.420 --> 00:17:22.430 align:start position:0% Yul and also about the optimization that 00:17:22.430 --> 00:17:24.610 align:start position:0% Yul and also about the optimization that I<00:17:22.670> talked<00:17:22.880> about<00:17:23.000> then<00:17:23.930> I<00:17:23.959> would<00:17:24.320> highly 00:17:24.610 --> 00:17:24.620 align:start position:0% I talked about then I would highly 00:17:24.620 --> 00:17:29.260 align:start position:0% I talked about then I would highly recommend<00:17:24.650> you<00:17:25.580> to<00:17:26.260> join<00:17:27.260> the<00:17:27.920> talk<00:17:28.160> today<00:17:28.459> by 00:17:29.260 --> 00:17:29.270 align:start position:0% recommend you to join the talk today by 00:17:29.270 --> 00:17:29.950 align:start position:0% recommend you to join the talk today by Christian 00:17:29.950 --> 00:17:29.960 align:start position:0% Christian 00:17:29.960 --> 00:17:34.360 align:start position:0% Christian it's<00:17:30.380> a<00:17:30.590> 4:30<00:17:31.400> p.m.<00:17:31.790> and<00:17:32.560> prison<00:17:33.560> and<00:17:33.770> he<00:17:34.220> will 00:17:34.360 --> 00:17:34.370 align:start position:0% it's a 4:30 p.m. and prison and he will 00:17:34.370 --> 00:17:37.720 align:start position:0% it's a 4:30 p.m. and prison and he will talk<00:17:34.640> about<00:17:35.020> the<00:17:36.020> optimization<00:17:36.380> that<00:17:37.010> we<00:17:37.370> put 00:17:37.720 --> 00:17:37.730 align:start position:0% talk about the optimization that we put 00:17:37.730 --> 00:17:42.790 align:start position:0% talk about the optimization that we put in<00:17:37.910> already<00:17:38.900> and<00:17:39.760> also<00:17:41.200> some<00:17:42.200> things<00:17:42.380> that<00:17:42.590> we 00:17:42.790 --> 00:17:42.800 align:start position:0% in already and also some things that we 00:17:42.800 --> 00:17:47.250 align:start position:0% in already and also some things that we plan<00:17:43.040> to<00:17:43.070> do<00:17:43.460> in<00:17:43.640> the<00:17:43.670> future 00:17:47.250 --> 00:17:47.260 align:start position:0% 00:17:47.260 --> 00:17:53.370 align:start position:0% alright<00:17:48.820> so<00:17:49.820> coming<00:17:50.240> to<00:17:50.360> formal<00:17:50.960> verification 00:17:53.370 --> 00:17:53.380 align:start position:0% 00:17:53.380 --> 00:17:57.690 align:start position:0% so<00:17:54.380> we're<00:17:54.950> using<00:17:55.480> technique<00:17:56.480> called<00:17:56.690> SMT 00:17:57.690 --> 00:17:57.700 align:start position:0% so we're using technique called SMT 00:17:57.700 --> 00:18:01.990 align:start position:0% so we're using technique called SMT satisfiability<00:17:58.700> modular<00:17:59.630> theories<00:18:00.230> and<00:18:01.000> this 00:18:01.990 --> 00:18:02.000 align:start position:0% satisfiability modular theories and this 00:18:02.000 --> 00:18:04.150 align:start position:0% satisfiability modular theories and this helps<00:18:02.450> the<00:18:02.630> seamless<00:18:02.960> verification<00:18:03.830> of 00:18:04.150 --> 00:18:04.160 align:start position:0% helps the seamless verification of 00:18:04.160 --> 00:18:07.350 align:start position:0% helps the seamless verification of safety<00:18:05.090> properties<00:18:05.570> such<00:18:06.200> as<00:18:06.230> under<00:18:06.800> flow 00:18:07.350 --> 00:18:07.360 align:start position:0% safety properties such as under flow 00:18:07.360 --> 00:18:11.170 align:start position:0% safety properties such as under flow overflow<00:18:08.360> division<00:18:09.020> by<00:18:09.110> zero<00:18:10.180> trivial 00:18:11.170 --> 00:18:11.180 align:start position:0% overflow division by zero trivial 00:18:11.180 --> 00:18:14.200 align:start position:0% overflow division by zero trivial conditions<00:18:11.630> or<00:18:11.870> unreachable<00:18:12.260> code<00:18:12.680> and<00:18:13.210> also 00:18:14.200 --> 00:18:14.210 align:start position:0% conditions or unreachable code and also 00:18:14.210 --> 00:18:17.080 align:start position:0% conditions or unreachable code and also assertions<00:18:15.170> so<00:18:15.500> verifying<00:18:16.250> runtime<00:18:16.700> checks 00:18:17.080 --> 00:18:17.090 align:start position:0% assertions so verifying runtime checks 00:18:17.090 --> 00:18:20.020 align:start position:0% assertions so verifying runtime checks at<00:18:17.360> compile<00:18:17.900> time<00:18:17.930> and<00:18:18.490> we<00:18:19.490> have<00:18:19.640> a<00:18:19.670> component 00:18:20.020 --> 00:18:20.030 align:start position:0% at compile time and we have a component 00:18:20.030 --> 00:18:25.350 align:start position:0% at compile time and we have a component for<00:18:20.420> that<00:18:20.570> and<00:18:20.830> it's<00:18:21.830> called<00:18:21.920> the<00:18:22.250> SMT<00:18:22.640> checker 00:18:25.350 --> 00:18:25.360 align:start position:0% 00:18:25.360 --> 00:18:29.670 align:start position:0% so<00:18:26.360> this<00:18:26.750> is<00:18:26.870> one<00:18:26.990> example<00:18:27.250> so<00:18:28.250> you<00:18:28.730> can<00:18:29.330> able 00:18:29.670 --> 00:18:29.680 align:start position:0% so this is one example so you can able 00:18:29.680 --> 00:18:32.080 align:start position:0% so this is one example so you can able the<00:18:30.680> SMT<00:18:31.010> checker<00:18:31.220> is<00:18:31.430> an<00:18:31.550> experimental 00:18:32.080 --> 00:18:32.090 align:start position:0% the SMT checker is an experimental 00:18:32.090 --> 00:18:34.990 align:start position:0% the SMT checker is an experimental feature<00:18:32.270> right<00:18:32.600> now<00:18:32.780> and<00:18:33.160> you<00:18:34.160> can<00:18:34.340> enable<00:18:34.640> it 00:18:34.990 --> 00:18:35.000 align:start position:0% feature right now and you can enable it 00:18:35.000 --> 00:18:38.350 align:start position:0% feature right now and you can enable it using<00:18:35.900> a<00:18:35.990> pragma<00:18:36.410> your<00:18:37.310> pragma<00:18:37.670> experimental 00:18:38.350 --> 00:18:38.360 align:start position:0% using a pragma your pragma experimental 00:18:38.360 --> 00:18:41.920 align:start position:0% using a pragma your pragma experimental isn't<00:18:38.630> it<00:18:38.750> checkered<00:18:39.050> and<00:18:39.730> so<00:18:40.730> if<00:18:41.000> you<00:18:41.360> compile 00:18:41.920 --> 00:18:41.930 align:start position:0% isn't it checkered and so if you compile 00:18:41.930 --> 00:18:44.500 align:start position:0% isn't it checkered and so if you compile this<00:18:42.200> example<00:18:42.800> with<00:18:43.340> the<00:18:43.520> Santa<00:18:43.850> tracker<00:18:43.910> and 00:18:44.500 --> 00:18:44.510 align:start position:0% this example with the Santa tracker and 00:18:44.510 --> 00:18:49.590 align:start position:0% this example with the Santa tracker and abled<00:18:44.960> you<00:18:45.800> will<00:18:45.950> get<00:18:46.100> some<00:18:46.310> warnings<00:18:47.740> so 00:18:49.590 --> 00:18:49.600 align:start position:0% abled you will get some warnings so 00:18:49.600 --> 00:18:52.270 align:start position:0% abled you will get some warnings so first<00:18:50.600> warning<00:18:51.020> is<00:18:51.320> that<00:18:51.590> the<00:18:51.920> for<00:18:52.130> loop 00:18:52.270 --> 00:18:52.280 align:start position:0% first warning is that the for loop 00:18:52.280 --> 00:18:55.270 align:start position:0% first warning is that the for loop condition<00:18:52.310> is<00:18:52.880> always<00:18:53.240> true<00:18:53.510> so<00:18:54.230> I<00:18:54.710> is 00:18:55.270 --> 00:18:55.280 align:start position:0% condition is always true so I is 00:18:55.280 --> 00:19:01.360 align:start position:0% condition is always true so I is initialized<00:18:56.240> with<00:18:56.960> 200<00:18:57.620> and<00:18:58.390> that<00:18:59.390> means<00:18:59.630> that 00:19:01.360 --> 00:19:01.370 align:start position:0% initialized with 200 and that means that 00:19:01.370 --> 00:19:04.810 align:start position:0% initialized with 200 and that means that as<00:19:01.670> greater<00:19:02.660> equal<00:19:03.470> zero<00:19:03.800> this<00:19:04.400> condition 00:19:04.810 --> 00:19:04.820 align:start position:0% as greater equal zero this condition 00:19:04.820 --> 00:19:05.799 align:start position:0% as greater equal zero this condition will<00:19:04.940> always<00:19:05.240> be<00:19:05.420> true 00:19:05.799 --> 00:19:05.809 align:start position:0% will always be true 00:19:05.809 --> 00:19:08.950 align:start position:0% will always be true so<00:19:05.960> that's<00:19:06.260> the<00:19:06.470> first<00:19:06.620> warning<00:19:07.570> and<00:19:08.570> the 00:19:08.950 --> 00:19:08.960 align:start position:0% so that's the first warning and the 00:19:08.960 --> 00:19:11.320 align:start position:0% so that's the first warning and the second<00:19:09.290> warning<00:19:09.650> is<00:19:09.920> an<00:19:10.220> underflow<00:19:10.700> resulting 00:19:11.320 --> 00:19:11.330 align:start position:0% second warning is an underflow resulting 00:19:11.330 --> 00:19:17.170 align:start position:0% second warning is an underflow resulting in<00:19:11.450> a<00:19:11.570> value<00:19:12.020> less<00:19:12.200> than<00:19:12.440> zero<00:19:12.890> and<00:19:15.970> this<00:19:16.970> is<00:19:17.030> a 00:19:17.170 --> 00:19:17.180 align:start position:0% in a value less than zero and this is a 00:19:17.180 --> 00:19:20.290 align:start position:0% in a value less than zero and this is a I<00:19:17.900> then<00:19:18.350> gets<00:19:18.650> incremented<00:19:19.010> so<00:19:19.940> at<00:19:20.090> some<00:19:20.240> point 00:19:20.290 --> 00:19:20.300 align:start position:0% I then gets incremented so at some point 00:19:20.300 --> 00:19:26.980 align:start position:0% I then gets incremented so at some point you<00:19:20.570> will<00:19:20.720> get<00:19:20.900> an<00:19:21.530> underflow<00:19:22.010> here<00:19:25.990> let's 00:19:26.980 --> 00:19:26.990 align:start position:0% you will get an underflow here let's 00:19:26.990 --> 00:19:29.920 align:start position:0% you will get an underflow here let's give<00:19:27.170> this<00:19:27.320> example<00:19:27.770> and<00:19:28.720> there's<00:19:29.720> also 00:19:29.920 --> 00:19:29.930 align:start position:0% give this example and there's also 00:19:29.930 --> 00:19:33.370 align:start position:0% give this example and there's also talked<00:19:30.380> by<00:19:31.250> our<00:19:31.670> colleague<00:19:32.150> colleague<00:19:33.110> Leo 00:19:33.370 --> 00:19:33.380 align:start position:0% talked by our colleague colleague Leo 00:19:33.380 --> 00:19:36.280 align:start position:0% talked by our colleague colleague Leo and<00:19:33.710> it<00:19:34.370> will<00:19:34.580> happen<00:19:35.120> tomorrow<00:19:35.300> at<00:19:35.720> 4:00<00:19:36.050> p.m. 00:19:36.280 --> 00:19:36.290 align:start position:0% and it will happen tomorrow at 4:00 p.m. 00:19:36.290 --> 00:19:40.120 align:start position:0% and it will happen tomorrow at 4:00 p.m. on<00:19:37.280> the<00:19:37.490> ultraviolet<00:19:38.240> stage<00:19:38.770> and<00:19:39.770> he<00:19:39.950> will 00:19:40.120 --> 00:19:40.130 align:start position:0% on the ultraviolet stage and he will 00:19:40.130 --> 00:19:42.880 align:start position:0% on the ultraviolet stage and he will talk<00:19:40.429> about<00:19:41.050> some<00:19:42.050> details<00:19:42.440> on<00:19:42.679> how<00:19:42.860> to 00:19:42.880 --> 00:19:42.890 align:start position:0% talk about some details on how to 00:19:42.890 --> 00:19:50.500 align:start position:0% talk about some details on how to actually<00:19:43.280> use<00:19:43.820> the<00:19:44.600> SMT<00:19:44.990> checker<00:19:49.510> what's 00:19:50.500 --> 00:19:50.510 align:start position:0% actually use the SMT checker what's 00:19:50.510 --> 00:19:53.320 align:start position:0% actually use the SMT checker what's coming<00:19:50.809> up<00:19:50.929> so<00:19:51.410> we're<00:19:52.250> planning<00:19:52.610> to<00:19:52.640> do<00:19:52.940> some 00:19:53.320 --> 00:19:53.330 align:start position:0% coming up so we're planning to do some 00:19:53.330 --> 00:19:58.150 align:start position:0% coming up so we're planning to do some inheritance<00:19:53.630> rule<00:19:54.140> changes<00:19:55.929> and<00:19:57.160> so 00:19:58.150 --> 00:19:58.160 align:start position:0% inheritance rule changes and so 00:19:58.160 --> 00:20:00.070 align:start position:0% inheritance rule changes and so inheritance<00:19:58.910> is<00:19:59.090> a<00:19:59.120> crucial<00:19:59.570> part<00:19:59.809> of 00:20:00.070 --> 00:20:00.080 align:start position:0% inheritance is a crucial part of 00:20:00.080 --> 00:20:02.470 align:start position:0% inheritance is a crucial part of solidity<00:20:00.590> contracts<00:20:01.340> but<00:20:01.970> there<00:20:02.210> are<00:20:02.300> some 00:20:02.470 --> 00:20:02.480 align:start position:0% solidity contracts but there are some 00:20:02.480 --> 00:20:05.080 align:start position:0% solidity contracts but there are some open<00:20:02.750> questions<00:20:02.900> so<00:20:03.770> what<00:20:04.190> about<00:20:04.309> explicit 00:20:05.080 --> 00:20:05.090 align:start position:0% open questions so what about explicit 00:20:05.090 --> 00:20:08.500 align:start position:0% open questions so what about explicit shadowing<00:20:05.920> can<00:20:06.920> visibility<00:20:07.790> our<00:20:08.179> state 00:20:08.500 --> 00:20:08.510 align:start position:0% shadowing can visibility our state 00:20:08.510 --> 00:20:12.100 align:start position:0% shadowing can visibility our state mutability<00:20:09.500> levels<00:20:09.920> change<00:20:10.280> and<00:20:10.870> there's<00:20:11.870> an 00:20:12.100 --> 00:20:12.110 align:start position:0% mutability levels change and there's an 00:20:12.110 --> 00:20:13.780 align:start position:0% mutability levels change and there's an open<00:20:12.350> pool<00:20:12.500> request<00:20:12.890> right<00:20:13.070> now<00:20:13.280> where<00:20:13.550> a<00:20:13.580> lot 00:20:13.780 --> 00:20:13.790 align:start position:0% open pool request right now where a lot 00:20:13.790 --> 00:20:17.410 align:start position:0% open pool request right now where a lot of<00:20:13.880> discussion<00:20:14.360> is<00:20:14.480> happening<00:20:14.630> and<00:20:16.210> so<00:20:17.210> we're 00:20:17.410 --> 00:20:17.420 align:start position:0% of discussion is happening and so we're 00:20:17.420 --> 00:20:19.510 align:start position:0% of discussion is happening and so we're hoping<00:20:17.780> to<00:20:17.990> get<00:20:18.230> more<00:20:18.470> people<00:20:18.950> join<00:20:19.340> this 00:20:19.510 --> 00:20:19.520 align:start position:0% hoping to get more people join this 00:20:19.520 --> 00:20:21.750 align:start position:0% hoping to get more people join this discussion<00:20:19.730> so<00:20:20.660> that<00:20:20.690> we<00:20:21.020> will<00:20:21.170> come<00:20:21.410> up<00:20:21.440> with 00:20:21.750 --> 00:20:21.760 align:start position:0% discussion so that we will come up with 00:20:21.760 --> 00:20:26.049 align:start position:0% discussion so that we will come up with a<00:20:22.760> cohesive<00:20:23.270> cohesive<00:20:24.260> set<00:20:24.440> of<00:20:24.590> rules<00:20:24.890> that<00:20:25.160> we 00:20:26.049 --> 00:20:26.059 align:start position:0% a cohesive cohesive set of rules that we 00:20:26.059 --> 00:20:31.780 align:start position:0% a cohesive cohesive set of rules that we can<00:20:26.210> implement<00:20:29.890> what<00:20:30.890> else<00:20:31.070> or<00:20:31.370> contract 00:20:31.780 --> 00:20:31.790 align:start position:0% can implement what else or contract 00:20:31.790 --> 00:20:37.540 align:start position:0% can implement what else or contract metadata<00:20:34.990> contract<00:20:35.990> metadata<00:20:36.380> is<00:20:36.650> generated 00:20:37.540 --> 00:20:37.550 align:start position:0% metadata contract metadata is generated 00:20:37.550 --> 00:20:40.299 align:start position:0% metadata contract metadata is generated for<00:20:37.730> each<00:20:37.880> contract<00:20:38.510> and<00:20:38.780> it<00:20:39.350> stores<00:20:39.620> as<00:20:40.070> a 00:20:40.299 --> 00:20:40.309 align:start position:0% for each contract and it stores as a 00:20:40.309 --> 00:20:43.990 align:start position:0% for each contract and it stores as a JSON<00:20:40.670> object<00:20:40.760> and<00:20:41.860> it<00:20:42.860> contains<00:20:43.220> all<00:20:43.429> details 00:20:43.990 --> 00:20:44.000 align:start position:0% JSON object and it contains all details 00:20:44.000 --> 00:20:49.680 align:start position:0% JSON object and it contains all details needed<00:20:44.540> to<00:20:45.410> reproduce<00:20:46.090> the<00:20:47.090> compilation<00:20:47.720> and 00:20:49.680 --> 00:20:49.690 align:start position:0% needed to reproduce the compilation and 00:20:49.690 --> 00:20:52.299 align:start position:0% needed to reproduce the compilation and as<00:20:50.690> form<00:20:51.020> hash<00:20:51.260> of<00:20:51.470> this<00:20:51.590> metadata<00:20:52.100> is 00:20:52.299 --> 00:20:52.309 align:start position:0% as form hash of this metadata is 00:20:52.309 --> 00:20:56.040 align:start position:0% as form hash of this metadata is appended<00:20:52.820> to<00:20:52.850> the<00:20:53.570> to<00:20:53.960> the<00:20:54.080> byte<00:20:54.230> code 00:20:56.040 --> 00:20:56.050 align:start position:0% appended to the to the byte code 00:20:56.050 --> 00:20:59.320 align:start position:0% appended to the to the byte code unfortunately<00:20:57.050> it's<00:20:57.380> not<00:20:57.620> used<00:20:57.980> by<00:20:58.309> a<00:20:59.120> lot<00:20:59.300> of 00:20:59.320 --> 00:20:59.330 align:start position:0% unfortunately it's not used by a lot of 00:20:59.330 --> 00:21:00.850 align:start position:0% unfortunately it's not used by a lot of verification<00:21:00.140> tools<00:21:00.440> that<00:21:00.590> are<00:21:00.710> out<00:21:00.740> there 00:21:00.850 --> 00:21:00.860 align:start position:0% verification tools that are out there 00:21:00.860 --> 00:21:05.710 align:start position:0% verification tools that are out there yet<00:21:01.900> and<00:21:03.370> you<00:21:04.370> can<00:21:04.550> find<00:21:04.880> the<00:21:05.240> documentation 00:21:05.710 --> 00:21:05.720 align:start position:0% yet and you can find the documentation 00:21:05.720 --> 00:21:08.380 align:start position:0% yet and you can find the documentation about<00:21:05.960> the<00:21:06.080> meta<00:21:06.320> that<00:21:06.559> also<00:21:07.240> in<00:21:08.240> our 00:21:08.380 --> 00:21:08.390 align:start position:0% about the meta that also in our 00:21:08.390 --> 00:21:10.279 align:start position:0% about the meta that also in our documentation 00:21:10.279 --> 00:21:10.289 align:start position:0% documentation 00:21:10.289 --> 00:21:14.279 align:start position:0% documentation and<00:21:11.490> this<00:21:12.490> is<00:21:12.669> how<00:21:12.850> the<00:21:13.629> contract<00:21:13.960> metadata 00:21:14.279 --> 00:21:14.289 align:start position:0% and this is how the contract metadata 00:21:14.289 --> 00:21:18.539 align:start position:0% and this is how the contract metadata will<00:21:14.590> look<00:21:14.740> like<00:21:14.889> so<00:21:15.669> you<00:21:16.659> have<00:21:16.929> a<00:21:17.549> contract 00:21:18.539 --> 00:21:18.549 align:start position:0% will look like so you have a contract 00:21:18.549 --> 00:21:20.279 align:start position:0% will look like so you have a contract version<00:21:18.909> you<00:21:19.269> have<00:21:19.509> the<00:21:19.659> language<00:21:19.809> so 00:21:20.279 --> 00:21:20.289 align:start position:0% version you have the language so 00:21:20.289 --> 00:21:23.700 align:start position:0% version you have the language so solidity<00:21:20.799> you<00:21:21.779> have<00:21:22.779> the<00:21:23.139> compiler<00:21:23.470> version 00:21:23.700 --> 00:21:23.710 align:start position:0% solidity you have the compiler version 00:21:23.710 --> 00:21:27.560 align:start position:0% solidity you have the compiler version is<00:21:24.009> included<00:21:24.580> and<00:21:24.789> also<00:21:25.539> some<00:21:25.899> settings<00:21:26.309> like 00:21:27.560 --> 00:21:27.570 align:start position:0% is included and also some settings like 00:21:27.570 --> 00:21:31.560 align:start position:0% is included and also some settings like compilation<00:21:28.570> Target<00:21:29.019> EVM<00:21:29.919> version<00:21:30.370> and<00:21:31.120> if 00:21:31.560 --> 00:21:31.570 align:start position:0% compilation Target EVM version and if 00:21:31.570 --> 00:21:33.600 align:start position:0% compilation Target EVM version and if the<00:21:31.720> optimizer<00:21:32.110> was<00:21:32.470> enabled<00:21:32.980> or<00:21:33.129> disabled 00:21:33.600 --> 00:21:33.610 align:start position:0% the optimizer was enabled or disabled 00:21:33.610 --> 00:21:37.399 align:start position:0% the optimizer was enabled or disabled because<00:21:33.909> this<00:21:34.210> will<00:21:35.110> result<00:21:35.470> in<00:21:36.000> different 00:21:37.399 --> 00:21:37.409 align:start position:0% because this will result in different 00:21:37.409 --> 00:21:43.409 align:start position:0% because this will result in different output<00:21:40.080> and<00:21:41.250> here<00:21:42.250> you<00:21:42.340> can<00:21:42.460> see<00:21:42.639> the<00:21:42.970> hashes 00:21:43.409 --> 00:21:43.419 align:start position:0% output and here you can see the hashes 00:21:43.419 --> 00:21:45.990 align:start position:0% output and here you can see the hashes that<00:21:43.600> I<00:21:43.629> mentioned<00:21:44.399> and<00:21:45.399> this<00:21:45.639> is<00:21:45.789> then 00:21:45.990 --> 00:21:46.000 align:start position:0% that I mentioned and this is then 00:21:46.000 --> 00:21:51.930 align:start position:0% that I mentioned and this is then included<00:21:49.710> so<00:21:50.710> then<00:21:51.070> the<00:21:51.490> IBI 00:21:51.930 --> 00:21:51.940 align:start position:0% included so then the IBI 00:21:51.940 --> 00:21:57.060 align:start position:0% included so then the IBI encoder<00:21:52.450> v2<00:21:54.720> what<00:21:55.720> is<00:21:55.870> the<00:21:56.019> IV<00:21:56.259> I<00:21:56.289> so<00:21:56.379> we<00:21:56.889> have<00:21:56.919> a 00:21:57.060 --> 00:21:57.070 align:start position:0% encoder v2 what is the IV I so we have a 00:21:57.070 --> 00:21:58.950 align:start position:0% encoder v2 what is the IV I so we have a contract<00:21:57.519> a<00:21:57.610> V<00:21:57.669> I<00:21:57.759> am<00:21:58.029> and<00:21:58.210> that's<00:21:58.840> the 00:21:58.950 --> 00:21:58.960 align:start position:0% contract a V I am and that's the 00:21:58.960 --> 00:22:01.619 align:start position:0% contract a V I am and that's the specification<00:21:59.830> how<00:22:00.279> and<00:22:00.789> to<00:22:00.820> exchange<00:22:01.210> data 00:22:01.619 --> 00:22:01.629 align:start position:0% specification how and to exchange data 00:22:01.629 --> 00:22:05.100 align:start position:0% specification how and to exchange data with<00:22:01.779> a<00:22:01.929> contract<00:22:02.409> and<00:22:03.419> for<00:22:04.419> each<00:22:04.539> public 00:22:05.100 --> 00:22:05.110 align:start position:0% with a contract and for each public 00:22:05.110 --> 00:22:07.860 align:start position:0% with a contract and for each public function<00:22:05.559> a<00:22:05.830> decoder<00:22:06.309> or<00:22:06.700> encode<00:22:07.120> and<00:22:07.389> encoder 00:22:07.860 --> 00:22:07.870 align:start position:0% function a decoder or encode and encoder 00:22:07.870 --> 00:22:10.350 align:start position:0% function a decoder or encode and encoder is<00:22:08.019> generated<00:22:08.909> currently<00:22:09.909> that's 00:22:10.350 --> 00:22:10.360 align:start position:0% is generated currently that's 00:22:10.360 --> 00:22:15.330 align:start position:0% is generated currently that's handwritten<00:22:11.169> C++<00:22:11.919> code<00:22:12.220> and<00:22:13.139> it's<00:22:14.190> it's<00:22:15.190> very 00:22:15.330 --> 00:22:15.340 align:start position:0% handwritten C++ code and it's it's very 00:22:15.340 --> 00:22:20.669 align:start position:0% handwritten C++ code and it's it's very error-prone<00:22:15.820> and<00:22:16.710> it's<00:22:17.710> hard<00:22:18.159> to<00:22:18.309> test<00:22:19.679> so 00:22:20.669 --> 00:22:20.679 align:start position:0% error-prone and it's hard to test so 00:22:20.679 --> 00:22:24.389 align:start position:0% error-prone and it's hard to test so that's<00:22:21.279> why<00:22:21.549> we<00:22:22.090> introduced<00:22:22.659> the<00:22:23.559> ABI<00:22:23.830> encoder 00:22:24.389 --> 00:22:24.399 align:start position:0% that's why we introduced the ABI encoder 00:22:24.399 --> 00:22:28.529 align:start position:0% that's why we introduced the ABI encoder v2<00:22:24.850> and<00:22:25.139> this<00:22:26.139> is<00:22:26.289> written<00:22:26.590> in<00:22:26.740> Yule<00:22:26.919> and<00:22:27.539> it 00:22:28.529 --> 00:22:28.539 align:start position:0% v2 and this is written in Yule and it 00:22:28.539 --> 00:22:32.460 align:start position:0% v2 and this is written in Yule and it ensures<00:22:28.720> safety<00:22:29.379> properties<00:22:30.149> such<00:22:31.149> as<00:22:31.470> short 00:22:32.460 --> 00:22:32.470 align:start position:0% ensures safety properties such as short 00:22:32.470 --> 00:22:35.879 align:start position:0% ensures safety properties such as short input<00:22:32.980> to<00:22:33.789> short<00:22:34.029> input<00:22:34.419> or<00:22:34.690> invalid<00:22:35.529> values 00:22:35.879 --> 00:22:35.889 align:start position:0% input to short input or invalid values 00:22:35.889 --> 00:22:39.269 align:start position:0% input to short input or invalid values and<00:22:36.129> it<00:22:37.000> also<00:22:37.149> supports<00:22:37.740> complex<00:22:38.740> data<00:22:39.159> types 00:22:39.269 --> 00:22:39.279 align:start position:0% and it also supports complex data types 00:22:39.279 --> 00:22:42.240 align:start position:0% and it also supports complex data types such<00:22:40.149> as<00:22:40.179> direct<00:22:40.919> multi-dimensional<00:22:41.919> arrays 00:22:42.240 --> 00:22:42.250 align:start position:0% such as direct multi-dimensional arrays 00:22:42.250 --> 00:22:45.119 align:start position:0% such as direct multi-dimensional arrays and<00:22:42.629> you<00:22:43.629> can<00:22:43.809> also<00:22:44.019> play<00:22:44.500> around<00:22:44.649> with<00:22:45.009> the 00:22:45.119 --> 00:22:45.129 align:start position:0% and you can also play around with the 00:22:45.129 --> 00:22:48.119 align:start position:0% and you can also play around with the new<00:22:45.309> avi<00:22:45.669> encoder<00:22:46.210> and<00:22:46.600> enable<00:22:47.019> it<00:22:47.139> via<00:22:47.379> pragma 00:22:48.119 --> 00:22:48.129 align:start position:0% new avi encoder and enable it via pragma 00:22:48.129 --> 00:22:56.100 align:start position:0% new avi encoder and enable it via pragma a<00:22:48.309> very<00:22:48.690> experimental<00:22:49.690> program<00:22:53.730> alright<00:22:55.110> so 00:22:56.100 --> 00:22:56.110 align:start position:0% a very experimental program alright so 00:22:56.110 --> 00:23:00.600 align:start position:0% a very experimental program alright so and<00:22:56.409> then<00:22:56.789> I<00:22:57.789> want<00:22:58.419> to<00:22:58.600> quickly<00:22:59.220> tell<00:23:00.220> you<00:23:00.399> how 00:23:00.600 --> 00:23:00.610 align:start position:0% and then I want to quickly tell you how 00:23:00.610 --> 00:23:04.049 align:start position:0% and then I want to quickly tell you how you<00:23:00.669> could<00:23:01.179> potentially<00:23:02.100> contribute<00:23:03.100> to<00:23:03.519> the 00:23:04.049 --> 00:23:04.059 align:start position:0% you could potentially contribute to the 00:23:04.059 --> 00:23:07.700 align:start position:0% you could potentially contribute to the project<00:23:05.580> so<00:23:06.580> there<00:23:06.909> are<00:23:06.970> many<00:23:07.179> ways<00:23:07.360> to 00:23:07.700 --> 00:23:07.710 align:start position:0% project so there are many ways to 00:23:07.710 --> 00:23:12.180 align:start position:0% project so there are many ways to contribute<00:23:08.710> so<00:23:09.399> you<00:23:10.360> can<00:23:10.539> always<00:23:10.990> request<00:23:11.710> a 00:23:12.180 --> 00:23:12.190 align:start position:0% contribute so you can always request a 00:23:12.190 --> 00:23:16.129 align:start position:0% contribute so you can always request a feature<00:23:12.730> we<00:23:13.419> have<00:23:13.690> discussions<00:23:14.620> on<00:23:15.129> existing 00:23:16.129 --> 00:23:16.139 align:start position:0% feature we have discussions on existing 00:23:16.139 --> 00:23:18.610 align:start position:0% feature we have discussions on existing design<00:23:17.139> issues 00:23:18.610 --> 00:23:18.620 align:start position:0% design issues 00:23:18.620 --> 00:23:21.539 align:start position:0% design issues and<00:23:19.070> also<00:23:19.610> including<00:23:20.470> documentation 00:23:21.539 --> 00:23:21.549 align:start position:0% and also including documentation 00:23:21.549 --> 00:23:24.519 align:start position:0% and also including documentation improvements<00:23:22.549> and<00:23:23.120> also<00:23:23.480> the<00:23:23.960> examples<00:23:24.409> that 00:23:24.519 --> 00:23:24.529 align:start position:0% improvements and also the examples that 00:23:24.529 --> 00:23:29.890 align:start position:0% improvements and also the examples that we<00:23:24.679> have<00:23:24.710> in<00:23:25.010> the<00:23:25.070> documentation<00:23:27.130> we<00:23:28.510> an<00:23:29.510> or 00:23:29.890 --> 00:23:29.900 align:start position:0% we have in the documentation we an or 00:23:29.900 --> 00:23:33.370 align:start position:0% we have in the documentation we an or issue<00:23:30.200> tracker<00:23:30.470> we<00:23:31.460> have<00:23:32.020> introduced<00:23:33.020> some 00:23:33.370 --> 00:23:33.380 align:start position:0% issue tracker we have introduced some 00:23:33.380 --> 00:23:37.000 align:start position:0% issue tracker we have introduced some labels<00:23:33.830> for<00:23:34.760> example<00:23:35.179> Help<00:23:35.390> Wanted<00:23:35.480> or<00:23:36.049> good 00:23:37.000 --> 00:23:37.010 align:start position:0% labels for example Help Wanted or good 00:23:37.010 --> 00:23:39.580 align:start position:0% labels for example Help Wanted or good first<00:23:37.250> issue<00:23:37.520> so<00:23:38.299> if<00:23:38.570> you<00:23:38.690> go<00:23:38.870> through<00:23:38.900> all<00:23:39.260> the 00:23:39.580 --> 00:23:39.590 align:start position:0% first issue so if you go through all the 00:23:39.590 --> 00:23:42.610 align:start position:0% first issue so if you go through all the open<00:23:39.830> issues<00:23:40.220> and<00:23:40.580> see<00:23:41.120> the<00:23:41.270> labels<00:23:41.659> then<00:23:42.260> you 00:23:42.610 --> 00:23:42.620 align:start position:0% open issues and see the labels then you 00:23:42.620 --> 00:23:45.010 align:start position:0% open issues and see the labels then you can<00:23:42.890> probably<00:23:43.309> directly<00:23:44.029> start<00:23:44.270> working<00:23:44.900> on 00:23:45.010 --> 00:23:45.020 align:start position:0% can probably directly start working on 00:23:45.020 --> 00:23:47.890 align:start position:0% can probably directly start working on it<00:23:45.169> if<00:23:45.350> you<00:23:45.470> want<00:23:45.679> to<00:23:46.419> and<00:23:47.419> also<00:23:47.720> you<00:23:47.779> should 00:23:47.890 --> 00:23:47.900 align:start position:0% it if you want to and also you should 00:23:47.900 --> 00:23:52.210 align:start position:0% it if you want to and also you should watch<00:23:48.260> out<00:23:48.470> for<00:23:49.029> get<00:23:50.029> common<00:23:50.299> boundaries<00:23:51.220> or 00:23:52.210 --> 00:23:52.220 align:start position:0% watch out for get common boundaries or 00:23:52.220 --> 00:23:54.519 align:start position:0% watch out for get common boundaries or and<00:23:52.789> if<00:23:52.909> you<00:23:53.029> have<00:23:53.179> any<00:23:53.360> questions<00:23:53.840> about<00:23:54.169> them 00:23:54.519 --> 00:23:54.529 align:start position:0% and if you have any questions about them 00:23:54.529 --> 00:23:56.860 align:start position:0% and if you have any questions about them about<00:23:55.159> that<00:23:55.460> you<00:23:55.909> can<00:23:56.059> always<00:23:56.210> reach<00:23:56.600> out<00:23:56.809> to 00:23:56.860 --> 00:23:56.870 align:start position:0% about that you can always reach out to 00:23:56.870 --> 00:24:04.720 align:start position:0% about that you can always reach out to the<00:23:57.559> solidity<00:23:57.950> deaf<00:23:58.250> Channel<00:24:03.340> yeah<00:24:04.370> and<00:24:04.549> now 00:24:04.720 --> 00:24:04.730 align:start position:0% the solidity deaf Channel yeah and now 00:24:04.730 --> 00:24:09.190 align:start position:0% the solidity deaf Channel yeah and now we<00:24:04.789> have<00:24:05.480> some<00:24:05.870> time<00:24:06.649> for<00:24:06.679> questions<00:24:07.960> if<00:24:08.960> there 00:24:09.190 --> 00:24:09.200 align:start position:0% we have some time for questions if there 00:24:09.200 --> 00:24:11.710 align:start position:0% we have some time for questions if there are<00:24:09.230> any<00:24:09.350> so<00:24:10.130> I<00:24:10.490> think<00:24:10.909> there<00:24:11.330> are<00:24:11.360> two 00:24:11.710 --> 00:24:11.720 align:start position:0% are any so I think there are two 00:24:11.720 --> 00:24:29.330 align:start position:0% are any so I think there are two microphones<00:24:12.049> here<00:24:12.890> in<00:24:13.370> front<00:24:13.730> of<00:24:13.850> the<00:24:14.029> stage 00:24:29.330 --> 00:24:29.340 align:start position:0% 00:24:29.340 --> 00:24:32.509 align:start position:0% okay<00:24:30.029> that<00:24:30.960> doesn't<00:24:31.740> look<00:24:31.830> like<00:24:31.889> there<00:24:32.490> are 00:24:32.509 --> 00:24:32.519 align:start position:0% okay that doesn't look like there are 00:24:32.519 --> 00:24:35.299 align:start position:0% okay that doesn't look like there are any<00:24:32.610> questions<00:24:33.269> so<00:24:33.950> don't<00:24:34.950> what<00:24:35.039> if<00:24:35.129> they 00:24:35.299 --> 00:24:35.309 align:start position:0% any questions so don't what if they 00:24:35.309 --> 00:24:45.919 align:start position:0% any questions so don't what if they thank<00:24:35.759> you<00:24:35.909> oh<00:24:36.120> that's<00:24:37.080> a<00:24:37.169> question<00:24:44.929> so 00:24:45.919 --> 00:24:45.929 align:start position:0% thank you oh that's a question so 00:24:45.929 --> 00:24:49.330 align:start position:0% thank you oh that's a question so currently<00:24:46.519> if<00:24:47.519> you<00:24:47.639> declare<00:24:48.029> that<00:24:48.600> your 00:24:49.330 --> 00:24:49.340 align:start position:0% currently if you declare that your 00:24:49.340 --> 00:24:53.200 align:start position:0% currently if you declare that your parents<00:24:50.340> near<00:24:50.879> me<00:24:50.970> and<00:24:51.120> looks<00:24:52.080> so<00:24:52.259> well<00:24:52.559> toy 00:24:53.200 --> 00:24:53.210 align:start position:0% parents near me and looks so well toy 00:24:53.210 --> 00:24:55.210 align:start position:0% parents near me and looks so well toy BBB<00:24:54.240> hello 00:24:55.210 --> 00:24:55.220 align:start position:0% BBB hello 00:24:55.220 --> 00:24:58.610 align:start position:0% BBB hello okay<00:24:56.220> okay<00:24:56.309> okay<00:24:56.999> sorry<00:24:57.210> so<00:24:57.749> currently<00:24:58.289> in 00:24:58.610 --> 00:24:58.620 align:start position:0% okay okay okay sorry so currently in 00:24:58.620 --> 00:25:00.169 align:start position:0% okay okay okay sorry so currently in solidity<00:24:58.950> functions<00:24:59.370> if<00:24:59.639> you<00:24:59.789> declare<00:25:00.149> a 00:25:00.169 --> 00:25:00.179 align:start position:0% solidity functions if you declare a 00:25:00.179 --> 00:25:02.960 align:start position:0% solidity functions if you declare a returned<00:25:01.039> variable<00:25:02.039> that<00:25:02.549> the<00:25:02.669> function 00:25:02.960 --> 00:25:02.970 align:start position:0% returned variable that the function 00:25:02.970 --> 00:25:05.180 align:start position:0% returned variable that the function returns<00:25:03.090> something<00:25:03.450> and<00:25:03.779> don't<00:25:04.619> explicitly 00:25:05.180 --> 00:25:05.190 align:start position:0% returns something and don't explicitly 00:25:05.190 --> 00:25:06.799 align:start position:0% returns something and don't explicitly declare<00:25:05.820> return 00:25:06.799 --> 00:25:06.809 align:start position:0% declare return 00:25:06.809 --> 00:25:09.889 align:start position:0% declare return there's<00:25:07.320> no<00:25:07.529> notices<00:25:08.369> or<00:25:08.639> errors<00:25:09.389> about<00:25:09.539> that 00:25:09.889 --> 00:25:09.899 align:start position:0% there's no notices or errors about that 00:25:09.899 --> 00:25:11.119 align:start position:0% there's no notices or errors about that are<00:25:10.080> there<00:25:10.200> any<00:25:10.289> plans<00:25:10.499> to<00:25:10.649> change<00:25:10.919> that 00:25:11.119 --> 00:25:11.129 align:start position:0% are there any plans to change that 00:25:11.129 --> 00:25:17.659 align:start position:0% are there any plans to change that fertility<00:25:14.809> not<00:25:15.809> that<00:25:16.110> I<00:25:16.139> know<00:25:16.379> of<00:25:16.409> I<00:25:16.830> mean<00:25:17.009> my 00:25:17.659 --> 00:25:17.669 align:start position:0% fertility not that I know of I mean my 00:25:17.669 --> 00:25:21.739 align:start position:0% fertility not that I know of I mean my the<00:25:17.730> team<00:25:18.210> is<00:25:18.419> also<00:25:18.629> sitting<00:25:19.110> there<00:25:19.320> so<00:25:20.570> if<00:25:21.570> you 00:25:21.739 --> 00:25:21.749 align:start position:0% the team is also sitting there so if you 00:25:21.749 --> 00:25:26.539 align:start position:0% the team is also sitting there so if you want<00:25:21.929> to<00:25:22.049> add<00:25:22.259> something<00:25:22.700> to<00:25:23.700> that<00:25:25.519> yeah<00:25:26.519> I 00:25:26.539 --> 00:25:26.549 align:start position:0% want to add something to that yeah I 00:25:26.549 --> 00:25:27.950 align:start position:0% want to add something to that yeah I mean<00:25:26.639> there's<00:25:26.970> an<00:25:27.240> I<00:25:27.389> think<00:25:27.450> there's<00:25:27.690> an<00:25:27.749> open 00:25:27.950 --> 00:25:27.960 align:start position:0% mean there's an I think there's an open 00:25:27.960 --> 00:25:31.850 align:start position:0% mean there's an I think there's an open issue<00:25:28.049> about<00:25:28.379> that<00:25:29.119> we<00:25:30.119> do<00:25:30.389> warn<00:25:31.139> if<00:25:31.590> the 00:25:31.850 --> 00:25:31.860 align:start position:0% issue about that we do warn if the 00:25:31.860 --> 00:25:33.470 align:start position:0% issue about that we do warn if the variable<00:25:32.279> is<00:25:32.340> not<00:25:32.549> used<00:25:32.789> at<00:25:32.970> all<00:25:33.059> so<00:25:33.299> if<00:25:33.389> you 00:25:33.470 --> 00:25:33.480 align:start position:0% variable is not used at all so if you 00:25:33.480 --> 00:25:35.149 align:start position:0% variable is not used at all so if you never<00:25:33.659> assign<00:25:33.990> to<00:25:34.259> it<00:25:34.379> and<00:25:34.649> do<00:25:34.799> not<00:25:34.830> have<00:25:35.129> a 00:25:35.149 --> 00:25:35.159 align:start position:0% never assign to it and do not have a 00:25:35.159 --> 00:25:38.560 align:start position:0% never assign to it and do not have a return<00:25:35.700> statement<00:25:36.179> then<00:25:36.600> you<00:25:36.779> get<00:25:36.929> a<00:25:36.960> warning 00:25:38.560 --> 00:25:38.570 align:start position:0% return statement then you get a warning 00:25:38.570 --> 00:25:41.810 align:start position:0% return statement then you get a warning yeah<00:25:39.919> there's<00:25:40.919> an<00:25:41.129> open<00:25:41.340> discussion<00:25:41.490> about 00:25:41.810 --> 00:25:41.820 align:start position:0% yeah there's an open discussion about 00:25:41.820 --> 00:25:44.029 align:start position:0% yeah there's an open discussion about how<00:25:41.970> to<00:25:42.029> how<00:25:43.019> and<00:25:43.169> whether<00:25:43.289> to<00:25:43.440> change<00:25:43.559> that<00:25:43.799> I 00:25:44.029 --> 00:25:44.039 align:start position:0% how to how and whether to change that I 00:25:44.039 --> 00:25:47.600 align:start position:0% how to how and whether to change that I have<00:25:44.340> one<00:25:44.460> more<00:25:44.779> question<00:25:45.779> so<00:25:46.129> currently<00:25:47.129> the 00:25:47.600 --> 00:25:47.610 align:start position:0% have one more question so currently the 00:25:47.610 --> 00:25:50.119 align:start position:0% have one more question so currently the function<00:25:48.179> identifiers<00:25:48.659> for<00:25:49.200> the<00:25:49.769> way<00:25:49.919> that 00:25:50.119 --> 00:25:50.129 align:start position:0% function identifiers for the way that 00:25:50.129 --> 00:25:52.009 align:start position:0% function identifiers for the way that like<00:25:50.519> how<00:25:50.999> they're<00:25:51.149> identified<00:25:51.570> when<00:25:51.869> you're 00:25:52.009 --> 00:25:52.019 align:start position:0% like how they're identified when you're 00:25:52.019 --> 00:25:53.629 align:start position:0% like how they're identified when you're calling<00:25:52.230> them<00:25:52.470> they<00:25:52.619> only<00:25:52.769> check<00:25:53.070> the<00:25:53.369> the 00:25:53.629 --> 00:25:53.639 align:start position:0% calling them they only check the the 00:25:53.639 --> 00:25:55.489 align:start position:0% calling them they only check the the only<00:25:54.179> have<00:25:54.330> the<00:25:54.629> name<00:25:54.869> and<00:25:55.200> the<00:25:55.320> parameters 00:25:55.489 --> 00:25:55.499 align:start position:0% only have the name and the parameters 00:25:55.499 --> 00:25:59.119 align:start position:0% only have the name and the parameters and<00:25:56.039> the<00:25:56.429> identifier<00:25:56.940> hash<00:25:57.179> right<00:25:57.980> but<00:25:58.980> this 00:25:59.119 --> 00:25:59.129 align:start position:0% and the identifier hash right but this 00:25:59.129 --> 00:26:00.680 align:start position:0% and the identifier hash right but this can<00:25:59.519> allow<00:25:59.759> where<00:26:00.029> you<00:26:00.119> can<00:26:00.269> call<00:26:00.450> a<00:26:00.480> function 00:26:00.680 --> 00:26:00.690 align:start position:0% can allow where you can call a function 00:26:00.690 --> 00:26:02.180 align:start position:0% can allow where you can call a function that<00:26:00.990> actually<00:26:01.320> returns<00:26:01.740> something<00:26:01.950> or 00:26:02.180 --> 00:26:02.190 align:start position:0% that actually returns something or 00:26:02.190 --> 00:26:03.499 align:start position:0% that actually returns something or doesn't<00:26:02.399> return<00:26:02.700> something<00:26:02.909> when<00:26:03.119> you<00:26:03.210> expect 00:26:03.499 --> 00:26:03.509 align:start position:0% doesn't return something when you expect 00:26:03.509 --> 00:26:05.930 align:start position:0% doesn't return something when you expect it<00:26:03.629> to<00:26:03.690> and<00:26:04.110> even<00:26:04.919> though<00:26:05.129> it<00:26:05.249> should<00:26:05.279> error<00:26:05.700> in 00:26:05.930 --> 00:26:05.940 align:start position:0% it to and even though it should error in 00:26:05.940 --> 00:26:07.609 align:start position:0% it to and even though it should error in that<00:26:06.090> sense<00:26:06.389> it<00:26:06.690> doesn't<00:26:07.080> because<00:26:07.409> that 00:26:07.609 --> 00:26:07.619 align:start position:0% that sense it doesn't because that 00:26:07.619 --> 00:26:09.529 align:start position:0% that sense it doesn't because that identify<00:26:08.070> only<00:26:08.429> checks<00:26:08.669> the<00:26:09.029> name<00:26:09.240> and<00:26:09.480> the 00:26:09.529 --> 00:26:09.539 align:start position:0% identify only checks the name and the 00:26:09.539 --> 00:26:11.480 align:start position:0% identify only checks the name and the parameters<00:26:09.799> are<00:26:10.799> there<00:26:10.980> any<00:26:11.070> plans<00:26:11.340> to 00:26:11.480 --> 00:26:11.490 align:start position:0% parameters are there any plans to 00:26:11.490 --> 00:26:13.580 align:start position:0% parameters are there any plans to include<00:26:11.580> the<00:26:11.909> return<00:26:12.269> variables<00:26:13.200> into<00:26:13.559> the 00:26:13.580 --> 00:26:13.590 align:start position:0% include the return variables into the 00:26:13.590 --> 00:26:17.659 align:start position:0% include the return variables into the function<00:26:14.100> identifiers<00:26:14.519> no<00:26:16.429> yeah<00:26:17.429> that's 00:26:17.659 --> 00:26:17.669 align:start position:0% function identifiers no yeah that's 00:26:17.669 --> 00:26:20.389 align:start position:0% function identifiers no yeah that's something<00:26:18.450> that<00:26:18.749> hip<00:26:19.350> to<00:26:19.529> some<00:26:19.710> people<00:26:20.100> at<00:26:20.279> the 00:26:20.389 --> 00:26:20.399 align:start position:0% something that hip to some people at the 00:26:20.399 --> 00:26:22.700 align:start position:0% something that hip to some people at the point<00:26:20.669> where<00:26:21.029> the<00:26:21.720> compiler<00:26:22.049> was<00:26:22.320> changed<00:26:22.649> to 00:26:22.700 --> 00:26:22.710 align:start position:0% point where the compiler was changed to 00:26:22.710 --> 00:26:25.840 align:start position:0% point where the compiler was changed to actually<00:26:23.159> enforce<00:26:23.730> the<00:26:24.119> return<00:26:24.419> size<00:26:24.659> okay 00:26:25.840 --> 00:26:25.850 align:start position:0% actually enforce the return size okay 00:26:25.850 --> 00:26:28.999 align:start position:0% actually enforce the return size okay that's<00:26:26.850> a<00:26:26.970> very<00:26:26.999> tough<00:26:27.509> thing<00:26:27.539> to<00:26:27.840> change<00:26:28.259> yeah 00:26:28.999 --> 00:26:29.009 align:start position:0% that's a very tough thing to change yeah 00:26:29.009 --> 00:26:31.039 align:start position:0% that's a very tough thing to change yeah I<00:26:29.220> mean<00:26:29.580> the<00:26:29.759> ABI<00:26:30.029> is<00:26:30.149> something<00:26:30.600> you<00:26:30.720> don't 00:26:31.039 --> 00:26:31.049 align:start position:0% I mean the ABI is something you don't 00:26:31.049 --> 00:26:36.160 align:start position:0% I mean the ABI is something you don't really<00:26:31.259> want<00:26:31.529> to<00:26:31.619> touch 00:26:36.160 --> 00:26:36.170 align:start position:0% 00:26:36.170 --> 00:26:38.540 align:start position:0% than<00:26:37.170> that<00:26:37.380> like<00:26:37.680> that<00:26:37.890> in<00:26:38.010> the<00:26:38.070> beginning<00:26:38.160> but 00:26:38.540 --> 00:26:38.550 align:start position:0% than that like that in the beginning but 00:26:38.550 --> 00:26:42.580 align:start position:0% than that like that in the beginning but yeah<00:26:38.820> okay<00:26:39.450> all<00:26:39.750> right<00:26:39.840> thank<00:26:40.020> you 00:26:42.580 --> 00:26:42.590 align:start position:0% 00:26:42.590 --> 00:26:46.130 align:start position:0% hello<00:26:43.590> I'm<00:26:44.430> currently<00:26:44.790> using<00:26:45.270> a<00:26:45.600> by<00:26:45.780> encoder 00:26:46.130 --> 00:26:46.140 align:start position:0% hello I'm currently using a by encoder 00:26:46.140 --> 00:26:48.170 align:start position:0% hello I'm currently using a by encoder version<00:26:46.500> 2<00:26:46.710> to<00:26:46.950> handle<00:26:47.250> complex<00:26:47.730> structure 00:26:48.170 --> 00:26:48.180 align:start position:0% version 2 to handle complex structure 00:26:48.180 --> 00:26:49.910 align:start position:0% version 2 to handle complex structure which<00:26:48.420> is<00:26:48.570> a<00:26:48.600> very<00:26:48.930> nice<00:26:49.170> feature<00:26:49.410> traveling 00:26:49.910 --> 00:26:49.920 align:start position:0% which is a very nice feature traveling 00:26:49.920 --> 00:26:51.920 align:start position:0% which is a very nice feature traveling solidity<00:26:50.250> you<00:26:51.240> say<00:26:51.420> it's<00:26:51.540> on<00:26:51.630> your<00:26:51.750> roadmap 00:26:51.920 --> 00:26:51.930 align:start position:0% solidity you say it's on your roadmap 00:26:51.930 --> 00:26:55.910 align:start position:0% solidity you say it's on your roadmap for<00:26:52.470> the<00:26:52.500> next<00:26:53.390> next<00:26:54.390> step<00:26:54.570> however<00:26:55.350> I<00:26:55.560> my 00:26:55.910 --> 00:26:55.920 align:start position:0% for the next next step however I my 00:26:55.920 --> 00:26:57.740 align:start position:0% for the next next step however I my question<00:26:56.190> is<00:26:56.310> how<00:26:56.610> dangerous<00:26:56.820> it<00:26:57.210> is<00:26:57.300> to<00:26:57.360> use<00:26:57.720> a 00:26:57.740 --> 00:26:57.750 align:start position:0% question is how dangerous it is to use a 00:26:57.750 --> 00:26:59.720 align:start position:0% question is how dangerous it is to use a current<00:26:58.200> experimental<00:26:58.770> version<00:26:59.220> and<00:26:59.460> how 00:26:59.720 --> 00:26:59.730 align:start position:0% current experimental version and how 00:26:59.730 --> 00:27:02.140 align:start position:0% current experimental version and how long<00:26:59.970> do<00:27:00.120> I<00:27:00.180> have<00:27:00.210> to<00:27:00.450> wait<00:27:00.600> to<00:27:00.900> have<00:27:01.020> a<00:27:01.050> proof 00:27:02.140 --> 00:27:02.150 align:start position:0% long do I have to wait to have a proof 00:27:02.150 --> 00:27:05.750 align:start position:0% long do I have to wait to have a proof solution<00:27:03.150> for<00:27:03.390> that<00:27:03.480> and<00:27:03.870> for<00:27:04.860> the<00:27:04.980> a<00:27:05.010> bi-week 00:27:05.750 --> 00:27:05.760 align:start position:0% solution for that and for the a bi-week 00:27:05.760 --> 00:27:11.330 align:start position:0% solution for that and for the a bi-week encoder<00:27:06.480> which<00:27:06.690> I<00:27:06.810> mean<00:27:07.050> yes<00:27:09.260> so<00:27:10.260> maybe<00:27:11.100> like 00:27:11.330 --> 00:27:11.340 align:start position:0% encoder which I mean yes so maybe like 00:27:11.340 --> 00:27:12.740 align:start position:0% encoder which I mean yes so maybe like one<00:27:11.580> one<00:27:11.790> part<00:27:12.030> of<00:27:12.210> your<00:27:12.360> question<00:27:12.660> was 00:27:12.740 --> 00:27:12.750 align:start position:0% one one part of your question was 00:27:12.750 --> 00:27:15.800 align:start position:0% one one part of your question was missing<00:27:13.080> because<00:27:13.200> like<00:27:14.270> can<00:27:15.270> you<00:27:15.300> can<00:27:15.510> be<00:27:15.630> able 00:27:15.800 --> 00:27:15.810 align:start position:0% missing because like can you can be able 00:27:15.810 --> 00:27:17.630 align:start position:0% missing because like can you can be able to<00:27:15.870> repeat<00:27:16.140> the<00:27:16.200> question<00:27:16.530> yeah<00:27:16.950> just<00:27:17.370> I'm 00:27:17.630 --> 00:27:17.640 align:start position:0% to repeat the question yeah just I'm 00:27:17.640 --> 00:27:19.460 align:start position:0% to repeat the question yeah just I'm using<00:27:17.970> it<00:27:18.180> right<00:27:18.210> now<00:27:18.540> but<00:27:19.200> it's<00:27:19.350> still 00:27:19.460 --> 00:27:19.470 align:start position:0% using it right now but it's still 00:27:19.470 --> 00:27:21.110 align:start position:0% using it right now but it's still experimental<00:27:19.890> so<00:27:20.430> I<00:27:20.460> want<00:27:20.670> to<00:27:20.730> know<00:27:20.850> if<00:27:20.970> it's 00:27:21.110 --> 00:27:21.120 align:start position:0% experimental so I want to know if it's 00:27:21.120 --> 00:27:23.120 align:start position:0% experimental so I want to know if it's dangerous<00:27:21.300> to<00:27:21.840> use<00:27:21.990> that<00:27:22.170> in<00:27:22.350> production<00:27:22.590> and 00:27:23.120 --> 00:27:23.130 align:start position:0% dangerous to use that in production and 00:27:23.130 --> 00:27:25.090 align:start position:0% dangerous to use that in production and if<00:27:23.490> it's<00:27:23.700> dangerous<00:27:24.480> and<00:27:24.720> it<00:27:24.780> might<00:27:24.960> change 00:27:25.090 --> 00:27:25.100 align:start position:0% if it's dangerous and it might change 00:27:25.100 --> 00:27:27.890 align:start position:0% if it's dangerous and it might change when<00:27:26.100> will<00:27:26.430> I<00:27:26.460> have<00:27:26.700> a<00:27:26.760> good<00:27:27.240> version<00:27:27.420> that<00:27:27.870> I 00:27:27.890 --> 00:27:27.900 align:start position:0% when will I have a good version that I 00:27:27.900 --> 00:27:30.560 align:start position:0% when will I have a good version that I can<00:27:28.230> deploy<00:27:28.710> on<00:27:28.860> the<00:27:28.950> main<00:27:29.130> it<00:27:29.310> um<00:27:29.580> I<00:27:30.330> mean 00:27:30.560 --> 00:27:30.570 align:start position:0% can deploy on the main it um I mean 00:27:30.570 --> 00:27:31.880 align:start position:0% can deploy on the main it um I mean that's<00:27:30.780> hard<00:27:30.990> to<00:27:31.110> say<00:27:31.320> so<00:27:31.380> it's<00:27:31.800> an 00:27:31.880 --> 00:27:31.890 align:start position:0% that's hard to say so it's an 00:27:31.890 --> 00:27:34.310 align:start position:0% that's hard to say so it's an experimental<00:27:32.340> feature<00:27:32.790> so<00:27:33.480> I<00:27:33.900> wouldn't 00:27:34.310 --> 00:27:34.320 align:start position:0% experimental feature so I wouldn't 00:27:34.320 --> 00:27:36.560 align:start position:0% experimental feature so I wouldn't recommend<00:27:34.560> to<00:27:34.920> use<00:27:35.070> this<00:27:35.370> in<00:27:35.850> production<00:27:36.090> at 00:27:36.560 --> 00:27:36.570 align:start position:0% recommend to use this in production at 00:27:36.570 --> 00:27:39.710 align:start position:0% recommend to use this in production at all<00:27:37.130> and<00:27:38.130> because<00:27:38.940> we<00:27:39.060> have<00:27:39.180> so<00:27:39.330> many<00:27:39.420> things 00:27:39.710 --> 00:27:39.720 align:start position:0% all and because we have so many things 00:27:39.720 --> 00:27:43.100 align:start position:0% all and because we have so many things going<00:27:39.900> on<00:27:40.790> it's<00:27:41.790> hard<00:27:42.120> to<00:27:42.270> say<00:27:42.480> when<00:27:42.750> this<00:27:42.900> will 00:27:43.100 --> 00:27:43.110 align:start position:0% going on it's hard to say when this will 00:27:43.110 --> 00:27:45.830 align:start position:0% going on it's hard to say when this will be<00:27:43.260> ready<00:27:43.580> but<00:27:44.580> maybe<00:27:44.730> christian<00:27:45.210> has<00:27:45.600> in 00:27:45.830 --> 00:27:45.840 align:start position:0% be ready but maybe christian has in 00:27:45.840 --> 00:27:47.840 align:start position:0% be ready but maybe christian has in addition<00:27:46.230> to<00:27:46.350> that<00:27:46.530> yeah<00:27:47.220> so<00:27:47.340> we're<00:27:47.550> pretty 00:27:47.840 --> 00:27:47.850 align:start position:0% addition to that yeah so we're pretty 00:27:47.850 --> 00:27:50.990 align:start position:0% addition to that yeah so we're pretty confident<00:27:48.450> that<00:27:48.510> it's<00:27:49.430> not<00:27:50.430> dangerous<00:27:50.610> to<00:27:50.880> use 00:27:50.990 --> 00:27:51.000 align:start position:0% confident that it's not dangerous to use 00:27:51.000 --> 00:27:54.110 align:start position:0% confident that it's not dangerous to use the<00:27:51.780> one<00:27:52.410> of<00:27:52.500> the<00:27:52.620> main<00:27:53.430> reasons<00:27:53.820> it's<00:27:53.940> still 00:27:54.110 --> 00:27:54.120 align:start position:0% the one of the main reasons it's still 00:27:54.120 --> 00:27:55.640 align:start position:0% the one of the main reasons it's still experimental<00:27:54.390> is<00:27:54.780> because<00:27:55.080> it's<00:27:55.230> much<00:27:55.500> more 00:27:55.640 --> 00:27:55.650 align:start position:0% experimental is because it's much more 00:27:55.650 --> 00:27:59.450 align:start position:0% experimental is because it's much more expensive<00:27:55.860> so<00:27:56.930> the<00:27:57.930> ABI<00:27:58.230> the<00:27:58.590> new<00:27:58.800> ABI<00:27:59.160> coder 00:27:59.450 --> 00:27:59.460 align:start position:0% expensive so the ABI the new ABI coder 00:27:59.460 --> 00:28:01.250 align:start position:0% expensive so the ABI the new ABI coder was<00:27:59.700> built<00:28:00.030> an<00:28:00.150> extremely<00:28:00.540> modular<00:28:00.870> way<00:28:01.020> where 00:28:01.250 --> 00:28:01.260 align:start position:0% was built an extremely modular way where 00:28:01.260 --> 00:28:04.220 align:start position:0% was built an extremely modular way where we<00:28:01.410> have<00:28:01.560> tiny<00:28:02.430> functions<00:28:02.880> for<00:28:03.120> very<00:28:03.540> simple 00:28:04.220 --> 00:28:04.230 align:start position:0% we have tiny functions for very simple 00:28:04.230 --> 00:28:08.420 align:start position:0% we have tiny functions for very simple tasks<00:28:04.770> and<00:28:05.450> that<00:28:06.450> helps<00:28:07.230> ensure<00:28:07.950> that<00:28:08.250> it's 00:28:08.420 --> 00:28:08.430 align:start position:0% tasks and that helps ensure that it's 00:28:08.430 --> 00:28:11.030 align:start position:0% tasks and that helps ensure that it's it's<00:28:08.790> correct<00:28:09.090> but<00:28:09.810> it's<00:28:10.650> more<00:28:10.860> expensive 00:28:11.030 --> 00:28:11.040 align:start position:0% it's correct but it's more expensive 00:28:11.040 --> 00:28:13.130 align:start position:0% it's correct but it's more expensive because<00:28:11.400> the<00:28:12.210> EVM<00:28:12.510> jumps<00:28:12.780> around<00:28:12.870> all<00:28:13.080> the 00:28:13.130 --> 00:28:13.140 align:start position:0% because the EVM jumps around all the 00:28:13.140 --> 00:28:16.610 align:start position:0% because the EVM jumps around all the time<00:28:13.230> and<00:28:13.590> if<00:28:14.430> you<00:28:14.520> want<00:28:14.550> to<00:28:14.880> so<00:28:15.600> and<00:28:15.780> we<00:28:16.470> will 00:28:16.610 --> 00:28:16.620 align:start position:0% time and if you want to so and we will 00:28:16.620 --> 00:28:18.320 align:start position:0% time and if you want to so and we will take<00:28:16.920> it<00:28:17.040> out<00:28:17.130> of<00:28:17.280> experimental<00:28:17.850> as<00:28:18.030> soon<00:28:18.210> as 00:28:18.320 --> 00:28:18.330 align:start position:0% take it out of experimental as soon as 00:28:18.330 --> 00:28:21.020 align:start position:0% take it out of experimental as soon as we<00:28:18.480> have<00:28:18.720> the<00:28:19.080> yule<00:28:19.290> optimizer<00:28:19.740> that<00:28:19.920> will 00:28:21.020 --> 00:28:21.030 align:start position:0% we have the yule optimizer that will 00:28:21.030 --> 00:28:22.010 align:start position:0% we have the yule optimizer that will yeah<00:28:21.240> remove<00:28:21.600> these<00:28:21.810> inefficiencies 00:28:22.010 --> 00:28:22.020 align:start position:0% yeah remove these inefficiencies 00:28:22.020 --> 00:28:30.470 align:start position:0% yeah remove these inefficiencies basically<00:28:26.240> right<00:28:27.240> so<00:28:28.730> 0.5<00:28:29.730> has<00:28:30.240> a<00:28:30.270> lot<00:28:30.450> of 00:28:30.470 --> 00:28:30.480 align:start position:0% basically right so 0.5 has a lot of 00:28:30.480 --> 00:28:32.420 align:start position:0% basically right so 0.5 has a lot of breaking<00:28:30.720> changes<00:28:31.200> right<00:28:31.380> that's<00:28:32.280> got 00:28:32.420 --> 00:28:32.430 align:start position:0% breaking changes right that's got 00:28:32.430 --> 00:28:34.240 align:start position:0% breaking changes right that's got backwards<00:28:32.700> compatibility 00:28:34.240 --> 00:28:34.250 align:start position:0% backwards compatibility 00:28:34.250 --> 00:28:36.380 align:start position:0% backwards compatibility I've<00:28:35.250> got<00:28:35.490> contracts<00:28:35.970> that<00:28:36.120> are<00:28:36.240> already 00:28:36.380 --> 00:28:36.390 align:start position:0% I've got contracts that are already 00:28:36.390 --> 00:28:38.300 align:start position:0% I've got contracts that are already deployed<00:28:36.690> to<00:28:36.960> the<00:28:37.050> chain<00:28:37.260> using<00:28:37.980> previous 00:28:38.300 --> 00:28:38.310 align:start position:0% deployed to the chain using previous 00:28:38.310 --> 00:28:40.760 align:start position:0% deployed to the chain using previous versions<00:28:38.550> of<00:28:38.610> solidity<00:28:38.940> and<00:28:39.470> I'm<00:28:40.470> running 00:28:40.760 --> 00:28:40.770 align:start position:0% versions of solidity and I'm running 00:28:40.770 --> 00:28:42.590 align:start position:0% versions of solidity and I'm running into<00:28:40.890> some<00:28:41.160> challenges<00:28:41.610> trying<00:28:42.120> to<00:28:42.330> interact 00:28:42.590 --> 00:28:42.600 align:start position:0% into some challenges trying to interact 00:28:42.600 --> 00:28:45.440 align:start position:0% into some challenges trying to interact with<00:28:42.810> those<00:28:42.990> contracts<00:28:43.590> using<00:28:43.920> 0.5<00:28:44.550> because 00:28:45.440 --> 00:28:45.450 align:start position:0% with those contracts using 0.5 because 00:28:45.450 --> 00:28:46.550 align:start position:0% with those contracts using 0.5 because of<00:28:45.690> the<00:28:45.750> things<00:28:45.960> the<00:28:46.170> way<00:28:46.260> that<00:28:46.380> they<00:28:46.440> were 00:28:46.550 --> 00:28:46.560 align:start position:0% of the things the way that they were 00:28:46.560 --> 00:28:48.350 align:start position:0% of the things the way that they were written<00:28:46.740> back<00:28:47.010> in<00:28:47.040> a<00:28:47.190> day<00:28:47.340> using<00:28:47.760> you<00:28:48.210> know 00:28:48.350 --> 00:28:48.360 align:start position:0% written back in a day using you know 00:28:48.360 --> 00:28:49.400 align:start position:0% written back in a day using you know constant<00:28:49.020> and 00:28:49.400 --> 00:28:49.410 align:start position:0% constant and 00:28:49.410 --> 00:28:50.960 align:start position:0% constant and you<00:28:49.440> know<00:28:49.560> various<00:28:50.190> other<00:28:50.400> bits<00:28:50.730> and<00:28:50.880> pieces 00:28:50.960 --> 00:28:50.970 align:start position:0% you know various other bits and pieces 00:28:50.970 --> 00:28:53.210 align:start position:0% you know various other bits and pieces do<00:28:51.360> you<00:28:51.450> guys<00:28:51.600> you<00:28:52.050> thought<00:28:52.320> about<00:28:52.440> how<00:28:53.190> to 00:28:53.210 --> 00:28:53.220 align:start position:0% do you guys you thought about how to 00:28:53.220 --> 00:28:55.760 align:start position:0% do you guys you thought about how to write<00:28:53.520> code<00:28:54.300> in<00:28:54.360> 0.5<00:28:54.930> to<00:28:55.080> integrate<00:28:55.470> to 00:28:55.760 --> 00:28:55.770 align:start position:0% write code in 0.5 to integrate to 00:28:55.770 --> 00:28:57.920 align:start position:0% write code in 0.5 to integrate to interact<00:28:56.190> with<00:28:56.280> existing<00:28:56.640> contracts<00:28:57.270> is<00:28:57.870> that 00:28:57.920 --> 00:28:57.930 align:start position:0% interact with existing contracts is that 00:28:57.930 --> 00:28:58.940 align:start position:0% interact with existing contracts is that the<00:28:58.110> thing<00:28:58.260> that<00:28:58.350> you've<00:28:58.470> thought<00:28:58.560> about<00:28:58.710> or 00:28:58.940 --> 00:28:58.950 align:start position:0% the thing that you've thought about or 00:28:58.950 --> 00:29:00.500 align:start position:0% the thing that you've thought about or are<00:28:59.400> you<00:28:59.490> expecting<00:28:59.670> the<00:29:00.000> effluence<00:29:00.390> that's 00:29:00.500 --> 00:29:00.510 align:start position:0% are you expecting the effluence that's 00:29:00.510 --> 00:29:01.640 align:start position:0% are you expecting the effluence that's going<00:29:00.630> to<00:29:00.690> write<00:29:00.840> all<00:29:00.870> in<00:29:01.110> your<00:29:01.200> contracts 00:29:01.640 --> 00:29:01.650 align:start position:0% going to write all in your contracts 00:29:01.650 --> 00:29:05.090 align:start position:0% going to write all in your contracts going<00:29:02.220> forward<00:29:02.780> mmm<00:29:03.780> no<00:29:04.200> I<00:29:04.230> mean<00:29:04.800> of<00:29:04.920> course 00:29:05.090 --> 00:29:05.100 align:start position:0% going forward mmm no I mean of course 00:29:05.100 --> 00:29:08.270 align:start position:0% going forward mmm no I mean of course we're<00:29:05.460> expecting<00:29:06.120> this<00:29:07.080> that<00:29:07.350> you<00:29:07.560> have 00:29:08.270 --> 00:29:08.280 align:start position:0% we're expecting this that you have 00:29:08.280 --> 00:29:09.590 align:start position:0% we're expecting this that you have contracts<00:29:08.670> compiled<00:29:09.030> with<00:29:09.240> different 00:29:09.590 --> 00:29:09.600 align:start position:0% contracts compiled with different 00:29:09.600 --> 00:29:13.220 align:start position:0% contracts compiled with different compiler<00:29:09.960> versions<00:29:10.350> and<00:29:10.790> so<00:29:11.790> I<00:29:12.360> mean<00:29:13.050> there 00:29:13.220 --> 00:29:13.230 align:start position:0% compiler versions and so I mean there 00:29:13.230 --> 00:29:21.340 align:start position:0% compiler versions and so I mean there there<00:29:13.470> is<00:29:13.560> a<00:29:13.650> plan<00:29:13.860> for<00:29:13.890> that<00:29:14.220> so<00:29:15.440> okay 00:29:21.340 --> 00:29:21.350 align:start position:0% 00:29:21.350 --> 00:29:24.350 align:start position:0% sorry<00:29:22.350> Eric<00:29:22.560> I<00:29:23.280> just<00:29:23.670> have<00:29:23.760> one<00:29:23.880> addition<00:29:24.240> to 00:29:24.350 --> 00:29:24.360 align:start position:0% sorry Eric I just have one addition to 00:29:24.360 --> 00:29:27.470 align:start position:0% sorry Eric I just have one addition to that<00:29:25.280> probably<00:29:26.280> the<00:29:26.430> best<00:29:26.460> way<00:29:26.820> to<00:29:26.850> do<00:29:27.120> it<00:29:27.270> if 00:29:27.470 --> 00:29:27.480 align:start position:0% that probably the best way to do it if 00:29:27.480 --> 00:29:29.810 align:start position:0% that probably the best way to do it if you<00:29:27.780> write<00:29:27.990> an<00:29:28.200> interface<00:29:28.650> for<00:29:28.950> your 00:29:29.810 --> 00:29:29.820 align:start position:0% you write an interface for your 00:29:29.820 --> 00:29:31.670 align:start position:0% you write an interface for your contracting<00:29:30.270> that<00:29:30.420> the<00:29:30.540> interface<00:29:30.870> is<00:29:30.930> valid 00:29:31.670 --> 00:29:31.680 align:start position:0% contracting that the interface is valid 00:29:31.680 --> 00:29:34.340 align:start position:0% contracting that the interface is valid in<00:29:31.860> zero-five-zero<00:29:32.960> that's<00:29:33.960> probably<00:29:34.260> the 00:29:34.340 --> 00:29:34.350 align:start position:0% in zero-five-zero that's probably the 00:29:34.350 --> 00:29:39.980 align:start position:0% in zero-five-zero that's probably the best<00:29:34.500> way<00:29:38.060> hello<00:29:39.060> thank<00:29:39.690> you<00:29:39.750> for<00:29:39.810> the 00:29:39.980 --> 00:29:39.990 align:start position:0% best way hello thank you for the 00:29:39.990 --> 00:29:44.060 align:start position:0% best way hello thank you for the presentation<00:29:41.270> so<00:29:42.270> currently<00:29:42.720> it<00:29:43.200> is<00:29:43.380> 0.5 00:29:44.060 --> 00:29:44.070 align:start position:0% presentation so currently it is 0.5 00:29:44.070 --> 00:29:47.300 align:start position:0% presentation so currently it is 0.5 which<00:29:44.640> is<00:29:44.880> alpha<00:29:45.720> software<00:29:46.320> what<00:29:47.070> do<00:29:47.190> you 00:29:47.300 --> 00:29:47.310 align:start position:0% which is alpha software what do you 00:29:47.310 --> 00:29:49.670 align:start position:0% which is alpha software what do you think<00:29:47.550> will<00:29:47.730> will<00:29:48.300> it<00:29:48.390> take<00:29:48.630> to<00:29:48.840> force<00:29:49.470> ready 00:29:49.670 --> 00:29:49.680 align:start position:0% think will will it take to force ready 00:29:49.680 --> 00:29:53.750 align:start position:0% think will will it take to force ready to<00:29:49.890> become<00:29:50.450> 1.0<00:29:51.450> software<00:29:51.960> and<00:29:52.370> you<00:29:53.370> mean<00:29:53.550> in 00:29:53.750 --> 00:29:53.760 align:start position:0% to become 1.0 software and you mean in 00:29:53.760 --> 00:29:58.160 align:start position:0% to become 1.0 software and you mean in terms<00:29:54.000> of<00:29:54.180> time<00:29:54.420> or<00:29:55.940> I<00:29:56.940> mean<00:29:57.180> that's<00:29:57.480> that's 00:29:58.160 --> 00:29:58.170 align:start position:0% terms of time or I mean that's that's 00:29:58.170 --> 00:30:00.440 align:start position:0% terms of time or I mean that's that's that's<00:29:58.710> really<00:29:59.010> hard<00:29:59.190> to<00:29:59.340> say<00:29:59.580> I<00:29:59.820> mean<00:29:59.880> because 00:30:00.440 --> 00:30:00.450 align:start position:0% that's really hard to say I mean because 00:30:00.450 --> 00:30:02.060 align:start position:0% that's really hard to say I mean because like<00:30:00.930> I<00:30:00.960> said<00:30:01.200> I<00:30:01.230> just<00:30:01.320> joined<00:30:01.800> the<00:30:01.920> project 00:30:02.060 --> 00:30:02.070 align:start position:0% like I said I just joined the project 00:30:02.070 --> 00:30:04.820 align:start position:0% like I said I just joined the project half<00:30:02.550> a<00:30:02.640> year<00:30:02.790> ago<00:30:03.060> and<00:30:03.300> I<00:30:04.050> joined<00:30:04.320> it<00:30:04.530> when<00:30:04.710> it 00:30:04.820 --> 00:30:04.830 align:start position:0% half a year ago and I joined it when it 00:30:04.830 --> 00:30:09.980 align:start position:0% half a year ago and I joined it when it was<00:30:04.980> in<00:30:05.220> version<00:30:06.020> 0<00:30:07.020> for<00:30:07.260> 22<00:30:07.620> so<00:30:08.460> now<00:30:08.700> we're<00:30:08.970> 0<00:30:09.780> 5 00:30:09.980 --> 00:30:09.990 align:start position:0% was in version 0 for 22 so now we're 0 5 00:30:09.990 --> 00:30:13.040 align:start position:0% was in version 0 for 22 so now we're 0 5 0<00:30:10.070> so<00:30:11.070> it<00:30:11.430> might<00:30:11.610> take<00:30:12.270> a<00:30:12.300> while<00:30:12.540> but<00:30:12.780> it's 00:30:13.040 --> 00:30:13.050 align:start position:0% 0 so it might take a while but it's 00:30:13.050 --> 00:30:15.380 align:start position:0% 0 so it might take a while but it's really<00:30:13.470> hard<00:30:13.740> to<00:30:13.920> say<00:30:14.130> when<00:30:14.640> it's<00:30:14.820> like<00:30:15.150> in 00:30:15.380 --> 00:30:15.390 align:start position:0% really hard to say when it's like in 00:30:15.390 --> 00:30:21.380 align:start position:0% really hard to say when it's like in version<00:30:15.750> 1.0<00:30:18.170> but<00:30:19.170> thank<00:30:19.290> you<00:30:19.350> I<00:30:20.030> mean<00:30:21.030> yeah<00:30:21.210> I 00:30:21.380 --> 00:30:21.390 align:start position:0% version 1.0 but thank you I mean yeah I 00:30:21.390 --> 00:30:23.300 align:start position:0% version 1.0 but thank you I mean yeah I joined<00:30:21.900> the<00:30:22.080> project<00:30:22.620> only<00:30:22.770> four<00:30:23.010> years<00:30:23.130> ago 00:30:23.300 --> 00:30:23.310 align:start position:0% joined the project only four years ago 00:30:23.310 --> 00:30:25.160 align:start position:0% joined the project only four years ago and<00:30:23.730> I<00:30:24.030> think<00:30:24.090> it<00:30:24.360> might<00:30:24.510> still<00:30:24.840> take<00:30:24.990> some 00:30:25.160 --> 00:30:25.170 align:start position:0% and I think it might still take some 00:30:25.170 --> 00:30:35.930 align:start position:0% and I think it might still take some time<00:30:25.350> to<00:30:25.500> get<00:30:25.650> to<00:30:25.770> all<00:30:30.980> right<00:30:34.580> time<00:30:35.580> is<00:30:35.610> up<00:30:35.880> but 00:30:35.930 --> 00:30:35.940 align:start position:0% time to get to all right time is up but 00:30:35.940 --> 00:30:38.510 align:start position:0% time to get to all right time is up but maybe<00:30:36.360> we<00:30:36.720> have<00:30:36.870> so<00:30:37.440> one<00:30:37.830> more<00:30:37.980> question<00:30:38.010> and 00:30:38.510 --> 00:30:38.520 align:start position:0% maybe we have so one more question and 00:30:38.520 --> 00:30:44.540 align:start position:0% maybe we have so one more question and no<00:30:40.970> ask<00:30:41.970> about<00:30:42.420> the<00:30:43.350> capability<00:30:44.220> of<00:30:44.250> the 00:30:44.540 --> 00:30:44.550 align:start position:0% no ask about the capability of the 00:30:44.550 --> 00:30:47.950 align:start position:0% no ask about the capability of the language<00:30:45.000> in<00:30:45.180> terms<00:30:45.540> of<00:30:46.010> returning 00:30:47.950 --> 00:30:47.960 align:start position:0% language in terms of returning 00:30:47.960 --> 00:30:50.930 align:start position:0% language in terms of returning multi-dimensional<00:30:48.960> ways<00:30:49.200> like<00:30:50.040> a<00:30:50.490> way<00:30:50.730> of 00:30:50.930 --> 00:30:50.940 align:start position:0% multi-dimensional ways like a way of 00:30:50.940 --> 00:30:55.490 align:start position:0% multi-dimensional ways like a way of struct<00:30:51.750> or<00:30:52.050> array<00:30:52.530> of<00:30:52.820> strings<00:30:54.050> and<00:30:55.050> also 00:30:55.490 --> 00:30:55.500 align:start position:0% struct or array of strings and also 00:30:55.500 --> 00:30:58.660 align:start position:0% struct or array of strings and also about<00:30:56.190> the<00:30:56.850> capability<00:30:57.480> of<00:30:57.510> the<00:30:58.110> string 00:30:58.660 --> 00:30:58.670 align:start position:0% about the capability of the string 00:30:58.670 --> 00:31:01.210 align:start position:0% about the capability of the string datatype<00:30:59.670> that 00:31:01.210 --> 00:31:01.220 align:start position:0% datatype that 00:31:01.220 --> 00:31:04.330 align:start position:0% datatype that has<00:31:01.900> limitation<00:31:02.900> in<00:31:03.110> terms<00:31:03.140> of<00:31:03.650> getting<00:31:04.010> the 00:31:04.330 --> 00:31:04.340 align:start position:0% has limitation in terms of getting the 00:31:04.340 --> 00:31:07.510 align:start position:0% has limitation in terms of getting the length<00:31:04.580> or<00:31:05.799> doing<00:31:06.799> some<00:31:07.130> sort<00:31:07.370> of 00:31:07.510 --> 00:31:07.520 align:start position:0% length or doing some sort of 00:31:07.520 --> 00:31:13.360 align:start position:0% length or doing some sort of concatenation<00:31:10.419> so<00:31:11.419> and<00:31:11.870> the<00:31:12.799> question<00:31:13.220> was 00:31:13.360 --> 00:31:13.370 align:start position:0% concatenation so and the question was 00:31:13.370 --> 00:31:15.549 align:start position:0% concatenation so and the question was when<00:31:13.730> this<00:31:14.120> will<00:31:14.299> be<00:31:14.419> changed<00:31:14.809> yes 00:31:15.549 --> 00:31:15.559 align:start position:0% when this will be changed yes 00:31:15.559 --> 00:31:18.610 align:start position:0% when this will be changed yes I<00:31:15.590> mean<00:31:16.450> yeah<00:31:17.450> at<00:31:17.750> the<00:31:17.929> point<00:31:18.200> like<00:31:18.470> your 00:31:18.610 --> 00:31:18.620 align:start position:0% I mean yeah at the point like your 00:31:18.620 --> 00:31:20.200 align:start position:0% I mean yeah at the point like your question<00:31:18.890> about<00:31:18.980> multi-dimensional<00:31:19.490> Aries 00:31:20.200 --> 00:31:20.210 align:start position:0% question about multi-dimensional Aries 00:31:20.210 --> 00:31:23.260 align:start position:0% question about multi-dimensional Aries this<00:31:20.900> will<00:31:21.710> be<00:31:21.830> included<00:31:22.370> in<00:31:22.520> the<00:31:22.640> new<00:31:22.760> API<00:31:23.150> the 00:31:23.260 --> 00:31:23.270 align:start position:0% this will be included in the new API the 00:31:23.270 --> 00:31:25.750 align:start position:0% this will be included in the new API the encoder<00:31:23.720> so<00:31:24.169> if<00:31:24.799> you<00:31:25.010> want<00:31:25.190> to<00:31:25.280> interact<00:31:25.549> with 00:31:25.750 --> 00:31:25.760 align:start position:0% encoder so if you want to interact with 00:31:25.760 --> 00:31:28.600 align:start position:0% encoder so if you want to interact with the<00:31:25.940> contract<00:31:26.419> and<00:31:26.690> then<00:31:27.409> if<00:31:27.740> this<00:31:27.919> component 00:31:28.600 --> 00:31:28.610 align:start position:0% the contract and then if this component 00:31:28.610 --> 00:31:30.640 align:start position:0% the contract and then if this component is<00:31:28.730> finished<00:31:29.090> should<00:31:29.690> be<00:31:29.870> and<00:31:30.169> you<00:31:30.380> should<00:31:30.530> be 00:31:30.640 --> 00:31:30.650 align:start position:0% is finished should be and you should be 00:31:30.650 --> 00:31:34.539 align:start position:0% is finished should be and you should be able<00:31:30.770> to<00:31:31.039> use<00:31:31.220> them<00:31:31.990> and<00:31:32.990> how<00:31:33.049> about<00:31:33.770> adding 00:31:34.539 --> 00:31:34.549 align:start position:0% able to use them and how about adding 00:31:34.549 --> 00:31:39.120 align:start position:0% able to use them and how about adding the<00:31:34.730> capability<00:31:35.450> to<00:31:35.750> the<00:31:36.020> string<00:31:36.500> datatype 00:31:39.120 --> 00:31:39.130 align:start position:0% 00:31:39.130 --> 00:31:43.090 align:start position:0% you<00:31:40.130> mean<00:31:41.440> regarding<00:31:42.440> the<00:31:42.559> length<00:31:42.950> and 00:31:43.090 --> 00:31:43.100 align:start position:0% you mean regarding the length and 00:31:43.100 --> 00:31:47.409 align:start position:0% you mean regarding the length and concatenation<00:31:44.090> yes<00:31:44.480> yeah<00:31:44.919> I<00:31:45.919> mean<00:31:46.730> is<00:31:47.179> there 00:31:47.409 --> 00:31:47.419 align:start position:0% concatenation yes yeah I mean is there 00:31:47.419 --> 00:31:51.700 align:start position:0% concatenation yes yeah I mean is there anything<00:31:47.720> that<00:31:47.990> we<00:31:48.289> planned<00:31:48.890> for<00:31:50.409> for<00:31:51.409> that<00:31:51.559> in 00:31:51.700 --> 00:31:51.710 align:start position:0% anything that we planned for for that in 00:31:51.710 --> 00:31:52.330 align:start position:0% anything that we planned for for that in the<00:31:51.770> future 00:31:52.330 --> 00:31:52.340 align:start position:0% the future 00:31:52.340 --> 00:31:58.090 align:start position:0% the future sorry<00:31:52.610> I<00:31:52.700> have<00:31:52.880> to<00:31:52.970> refer<00:31:53.390> to<00:31:56.770> is<00:31:57.770> it<00:31:57.890> working 00:31:58.090 --> 00:31:58.100 align:start position:0% sorry I have to refer to is it working 00:31:58.100 --> 00:32:02.970 align:start position:0% sorry I have to refer to is it working now<00:31:58.130> yeah<00:31:59.919> we're<00:32:00.919> kind<00:32:01.130> of<00:32:01.159> reluctant<00:32:01.700> to<00:32:01.880> add 00:32:02.970 --> 00:32:02.980 align:start position:0% now yeah we're kind of reluctant to add 00:32:02.980 --> 00:32:05.620 align:start position:0% now yeah we're kind of reluctant to add features<00:32:03.980> that<00:32:04.490> have<00:32:04.760> unbounded<00:32:05.120> gas<00:32:05.450> usage 00:32:05.620 --> 00:32:05.630 align:start position:0% features that have unbounded gas usage 00:32:05.630 --> 00:32:08.169 align:start position:0% features that have unbounded gas usage and<00:32:06.080> string<00:32:06.429> concatenation<00:32:07.429> would<00:32:07.669> be<00:32:07.820> one<00:32:08.150> of 00:32:08.169 --> 00:32:08.179 align:start position:0% and string concatenation would be one of 00:32:08.179 --> 00:32:11.799 align:start position:0% and string concatenation would be one of them<00:32:08.360> but<00:32:09.080> you<00:32:09.919> can<00:32:10.100> use<00:32:10.309> ABI<00:32:10.850> dot<00:32:11.330> encode 00:32:11.799 --> 00:32:11.809 align:start position:0% them but you can use ABI dot encode 00:32:11.809 --> 00:32:13.899 align:start position:0% them but you can use ABI dot encode packed<00:32:12.200> on<00:32:12.530> byte<00:32:12.890> arrays<00:32:13.159> that<00:32:13.190> will<00:32:13.549> do 00:32:13.899 --> 00:32:13.909 align:start position:0% packed on byte arrays that will do 00:32:13.909 --> 00:32:16.899 align:start position:0% packed on byte arrays that will do exactly<00:32:14.230> byte<00:32:15.230> array<00:32:15.880> concatenation<00:32:16.880> which 00:32:16.899 --> 00:32:16.909 align:start position:0% exactly byte array concatenation which 00:32:16.909 --> 00:32:18.700 align:start position:0% exactly byte array concatenation which is<00:32:17.150> something<00:32:17.299> we<00:32:17.570> discovered<00:32:18.409> by<00:32:18.590> accident 00:32:18.700 --> 00:32:18.710 align:start position:0% is something we discovered by accident 00:32:18.710 --> 00:32:27.460 align:start position:0% is something we discovered by accident or<00:32:19.190> yeah<00:32:19.370> it's<00:32:20.360> a<00:32:20.419> neat<00:32:20.600> trick<00:32:25.419> all<00:32:26.419> right<00:32:26.720> cool 00:32:27.460 --> 00:32:27.470 align:start position:0% or yeah it's a neat trick all right cool 00:32:27.470 --> 00:32:29.220 align:start position:0% or yeah it's a neat trick all right cool yep<00:32:27.679> thank<00:32:28.010> you<00:32:28.130> a<00:32:28.159> lot 00:32:29.220 --> 00:32:29.230 align:start position:0% yep thank you a lot 00:32:29.230 --> 00:32:41.080 align:start position:0% yep thank you a lot [Applause] 00:32:41.080 --> 00:32:41.090 align:start position:0% 00:32:41.090 --> 00:32:43.150 align:start position:0% you