WEBVTT Kind: captions Language: en 00:00:09.190 --> 00:00:17.100 align:start position:0% [Music] 00:00:17.100 --> 00:00:17.110 align:start position:0% 00:00:17.110 --> 00:00:20.140 align:start position:0% say<00:00:18.110> everybody<00:00:18.440> I'm<00:00:18.590> chasing<00:00:19.310> out<00:00:19.550> for<00:00:19.850> a<00:00:19.880> half 00:00:20.140 --> 00:00:20.150 align:start position:0% say everybody I'm chasing out for a half 00:00:20.150 --> 00:00:23.250 align:start position:0% say everybody I'm chasing out for a half and<00:00:20.420> I<00:00:20.690> asked<00:00:21.320> to<00:00:21.500> moderate<00:00:21.860> this<00:00:22.040> panel 00:00:23.250 --> 00:00:23.260 align:start position:0% and I asked to moderate this panel 00:00:23.260 --> 00:00:28.330 align:start position:0% and I asked to moderate this panel because<00:00:24.460> I've<00:00:25.460> been<00:00:25.610> working<00:00:25.790> on<00:00:26.650> EBM<00:00:27.650> and<00:00:27.980> he 00:00:28.330 --> 00:00:28.340 align:start position:0% because I've been working on EBM and he 00:00:28.340 --> 00:00:31.300 align:start position:0% because I've been working on EBM and he was<00:00:28.550> him<00:00:28.790> lately<00:00:29.390> and<00:00:29.660> I<00:00:29.960> know<00:00:30.680> there<00:00:31.130> were 00:00:31.300 --> 00:00:31.310 align:start position:0% was him lately and I know there were 00:00:31.310 --> 00:00:33.240 align:start position:0% was him lately and I know there were there<00:00:32.059> are<00:00:32.090> no<00:00:32.270> other<00:00:32.419> experts 00:00:33.240 --> 00:00:33.250 align:start position:0% there are no other experts 00:00:33.250 --> 00:00:39.970 align:start position:0% there are no other experts besides<00:00:34.250> these<00:00:35.210> panelists<00:00:36.700> so<00:00:38.739> he<00:00:39.739> saw 00:00:39.970 --> 00:00:39.980 align:start position:0% besides these panelists so he saw 00:00:39.980 --> 00:00:45.819 align:start position:0% besides these panelists so he saw Martin's<00:00:40.820> talk<00:00:41.120> yesterday<00:00:42.190> and<00:00:44.650> well<00:00:45.650> it<00:00:45.710> was 00:00:45.819 --> 00:00:45.829 align:start position:0% Martin's talk yesterday and well it was 00:00:45.829 --> 00:00:50.020 align:start position:0% Martin's talk yesterday and well it was on<00:00:45.980> Crimea<00:00:46.760> but<00:00:47.230> it<00:00:48.230> mentioned<00:00:48.800> the<00:00:49.550> precursor 00:00:50.020 --> 00:00:50.030 align:start position:0% on Crimea but it mentioned the precursor 00:00:50.030 --> 00:00:53.830 align:start position:0% on Crimea but it mentioned the precursor to<00:00:50.060> premier<00:00:50.480> which<00:00:50.750> is<00:00:50.950> he<00:00:51.950> was<00:00:52.280> ohm<00:00:52.520> and<00:00:52.840> that 00:00:53.830 --> 00:00:53.840 align:start position:0% to premier which is he was ohm and that 00:00:53.840 --> 00:00:58.560 align:start position:0% to premier which is he was ohm and that started<00:00:54.829> in<00:00:55.040> December<00:00:55.520> 2015 00:00:58.560 --> 00:00:58.570 align:start position:0% 00:00:58.570 --> 00:01:04.450 align:start position:0% by<00:01:01.210> the<00:01:02.210> summer<00:01:02.480> of<00:01:02.809> 2016<00:01:03.559> the<00:01:03.980> first<00:01:04.159> comment 00:01:04.450 --> 00:01:04.460 align:start position:0% by the summer of 2016 the first comment 00:01:04.460 --> 00:01:05.980 align:start position:0% by the summer of 2016 the first comment was<00:01:04.519> in<00:01:04.670> April<00:01:05.000> but<00:01:05.119> by<00:01:05.239> the<00:01:05.299> summer<00:01:05.630> there<00:01:05.870> was 00:01:05.980 --> 00:01:05.990 align:start position:0% was in April but by the summer there was 00:01:05.990 --> 00:01:10.450 align:start position:0% was in April but by the summer there was a<00:01:06.229> pretty<00:01:06.979> working<00:01:07.370> prototype<00:01:07.909> for<00:01:08.780> the<00:01:09.460> EVM 00:01:10.450 --> 00:01:10.460 align:start position:0% a pretty working prototype for the EVM 00:01:10.460 --> 00:01:16.030 align:start position:0% a pretty working prototype for the EVM to<00:01:10.790> ewaz<00:01:11.180> 'm<00:01:11.470> transpiler<00:01:13.870> then<00:01:14.870> so<00:01:15.740> that<00:01:15.920> was 00:01:16.030 --> 00:01:16.040 align:start position:0% to ewaz 'm transpiler then so that was 00:01:16.040 --> 00:01:22.719 align:start position:0% to ewaz 'm transpiler then so that was the<00:01:16.159> EVM<00:01:16.520> 2.0<00:01:20.260> so<00:01:21.260> after<00:01:21.650> the<00:01:21.770> 2.0<00:01:22.220> proposal 00:01:22.719 --> 00:01:22.729 align:start position:0% the EVM 2.0 so after the 2.0 proposal 00:01:22.729 --> 00:01:28.090 align:start position:0% the EVM 2.0 so after the 2.0 proposal came<00:01:22.940> the<00:01:23.440> 1.5<00:01:24.820> proposal<00:01:25.820> from<00:01:26.860> Greg<00:01:27.860> and 00:01:28.090 --> 00:01:28.100 align:start position:0% came the 1.5 proposal from Greg and 00:01:28.100 --> 00:01:32.350 align:start position:0% came the 1.5 proposal from Greg and Pavel<00:01:28.760> and<00:01:29.170> you<00:01:30.170> just<00:01:30.350> saw<00:01:31.119> hobbles<00:01:32.119> talked 00:01:32.350 --> 00:01:32.360 align:start position:0% Pavel and you just saw hobbles talked 00:01:32.360 --> 00:01:35.590 align:start position:0% Pavel and you just saw hobbles talked earlier<00:01:32.750> about<00:01:33.220> EVM<00:01:34.220> C<00:01:34.520> which<00:01:34.939> is<00:01:35.090> sort<00:01:35.330> of<00:01:35.390> the 00:01:35.590 --> 00:01:35.600 align:start position:0% earlier about EVM C which is sort of the 00:01:35.600 --> 00:01:40.330 align:start position:0% earlier about EVM C which is sort of the the<00:01:36.470> API<00:01:36.830> to<00:01:38.049> plug<00:01:39.049> in<00:01:39.229> and<00:01:39.470> be<00:01:39.890> able<00:01:39.950> to<00:01:40.070> swap 00:01:40.330 --> 00:01:40.340 align:start position:0% the API to plug in and be able to swap 00:01:40.340 --> 00:01:50.469 align:start position:0% the API to plug in and be able to swap between<00:01:41.770> awasum<00:01:42.770> and<00:01:42.979> an<00:01:43.420> EVM<00:01:45.070> 1.5<00:01:46.720> and<00:01:49.479> then 00:01:50.469 --> 00:01:50.479 align:start position:0% between awasum and an EVM 1.5 and then 00:01:50.479 --> 00:01:57.179 align:start position:0% between awasum and an EVM 1.5 and then came<00:01:52.030> earlier<00:01:53.030> this<00:01:53.180> year<00:01:53.710> was<00:01:54.710> Julia 00:01:57.179 --> 00:01:57.189 align:start position:0% came earlier this year was Julia 00:01:57.189 --> 00:02:01.300 align:start position:0% came earlier this year was Julia yesterday<00:01:58.189> also<00:01:58.460> saw<00:01:59.290> Alex<00:02:00.380> Alex's<00:02:01.100> talk 00:02:01.300 --> 00:02:01.310 align:start position:0% yesterday also saw Alex Alex's talk 00:02:01.310 --> 00:02:04.960 align:start position:0% yesterday also saw Alex Alex's talk about<00:02:01.850> Julia<00:02:02.710> which<00:02:03.710> he<00:02:03.979> and<00:02:04.250> Christian 00:02:04.960 --> 00:02:04.970 align:start position:0% about Julia which he and Christian 00:02:04.970 --> 00:02:09.820 align:start position:0% about Julia which he and Christian designed<00:02:06.369> to<00:02:07.369> upgrade<00:02:08.329> solidity<00:02:08.780> and<00:02:09.110> be<00:02:09.679> able 00:02:09.820 --> 00:02:09.830 align:start position:0% designed to upgrade solidity and be able 00:02:09.830 --> 00:02:14.039 align:start position:0% designed to upgrade solidity and be able to<00:02:09.890> make<00:02:10.069> solidity<00:02:11.440> target 00:02:14.039 --> 00:02:14.049 align:start position:0% to make solidity target 00:02:14.049 --> 00:02:18.750 align:start position:0% to make solidity target the<00:02:15.079> EBM<00:02:15.819> 2.0<00:02:16.819> the<00:02:16.939> next<00:02:17.120> versions<00:02:17.420> of<00:02:17.569> the<00:02:17.719> EBM 00:02:18.750 --> 00:02:18.760 align:start position:0% the EBM 2.0 the next versions of the EBM 00:02:18.760 --> 00:02:31.270 align:start position:0% the EBM 2.0 the next versions of the EBM 2.0<00:02:19.760> and<00:02:19.909> 1.5<00:02:20.620> and<00:02:21.670> then<00:02:26.319> and<00:02:28.120> since<00:02:29.120> then<00:02:30.280> also 00:02:31.270 --> 00:02:31.280 align:start position:0% 2.0 and 1.5 and then and since then also 00:02:31.280 --> 00:02:33.280 align:start position:0% 2.0 and 1.5 and then and since then also pavel<00:02:31.849> has<00:02:31.939> made<00:02:32.090> a<00:02:32.120> lot<00:02:32.269> of<00:02:32.299> progress<00:02:32.540> on<00:02:32.930> the 00:02:33.280 --> 00:02:33.290 align:start position:0% pavel has made a lot of progress on the 00:02:33.290 --> 00:02:36.280 align:start position:0% pavel has made a lot of progress on the the<00:02:33.709> jet<00:02:33.950> vm<00:02:34.359> so<00:02:35.359> it's<00:02:35.930> sort<00:02:36.140> of<00:02:36.200> been 00:02:36.280 --> 00:02:36.290 align:start position:0% the jet vm so it's sort of been 00:02:36.290 --> 00:02:40.360 align:start position:0% the jet vm so it's sort of been backwards<00:02:36.620> where<00:02:37.269> first<00:02:38.269> EVM<00:02:39.189> 2.0<00:02:40.189> was 00:02:40.360 --> 00:02:40.370 align:start position:0% backwards where first EVM 2.0 was 00:02:40.370 --> 00:02:46.869 align:start position:0% backwards where first EVM 2.0 was proposed<00:02:40.700> then<00:02:41.540> more<00:02:41.870> progress<00:02:42.319> on<00:02:42.969> EVM<00:02:43.969> 1.5<00:02:45.879> I 00:02:46.869 --> 00:02:46.879 align:start position:0% proposed then more progress on EVM 1.5 I 00:02:46.879 --> 00:02:49.360 align:start position:0% proposed then more progress on EVM 1.5 I hope<00:02:47.810> this<00:02:48.019> makes<00:02:48.170> some<00:02:48.379> sense<00:02:48.560> so<00:02:48.799> I<00:02:48.829> I<00:02:49.159> think 00:02:49.360 --> 00:02:49.370 align:start position:0% hope this makes some sense so I I think 00:02:49.370 --> 00:02:56.800 align:start position:0% hope this makes some sense so I I think I'll<00:02:50.680> ask<00:02:51.680> our<00:02:51.950> panelists<00:02:52.459> what<00:02:53.419> is<00:02:55.780> what<00:02:56.780> is 00:02:56.800 --> 00:02:56.810 align:start position:0% I'll ask our panelists what is what is 00:02:56.810 --> 00:03:09.220 align:start position:0% I'll ask our panelists what is what is he<00:02:57.109> was<00:02:57.290> and<00:02:57.530> what<00:02:57.739> is<00:02:57.919> bbm<00:02:58.639> 1.5<00:03:08.200> what<00:03:09.200> I 00:03:09.220 --> 00:03:09.230 align:start position:0% he was and what is bbm 1.5 what I 00:03:09.230 --> 00:03:12.399 align:start position:0% he was and what is bbm 1.5 what I arrived<00:03:09.769> I<00:03:10.519> guess<00:03:11.060> he<00:03:11.269> was<00:03:11.480> him<00:03:11.750> had<00:03:11.900> made<00:03:12.079> some 00:03:12.399 --> 00:03:12.409 align:start position:0% arrived I guess he was him had made some 00:03:12.409 --> 00:03:18.129 align:start position:0% arrived I guess he was him had made some progress<00:03:13.510> substantial<00:03:16.030> and<00:03:17.030> a<00:03:17.359> few<00:03:17.870> things 00:03:18.129 --> 00:03:18.139 align:start position:0% progress substantial and a few things 00:03:18.139 --> 00:03:21.250 align:start position:0% progress substantial and a few things struck<00:03:18.769> me<00:03:18.909> one<00:03:19.909> is<00:03:20.150> people<00:03:20.419> were<00:03:20.840> sort<00:03:21.139> of 00:03:21.250 --> 00:03:21.260 align:start position:0% struck me one is people were sort of 00:03:21.260 --> 00:03:24.339 align:start position:0% struck me one is people were sort of excited<00:03:21.919> because<00:03:22.400> gee<00:03:23.389> whiz<00:03:23.629> you<00:03:23.659> could<00:03:24.169> you 00:03:24.339 --> 00:03:24.349 align:start position:0% excited because gee whiz you could you 00:03:24.349 --> 00:03:28.509 align:start position:0% excited because gee whiz you could you could<00:03:24.560> run<00:03:24.799> you<00:03:25.430> know<00:03:25.840> C++<00:03:27.069> contracts<00:03:28.069> and<00:03:28.430> he 00:03:28.509 --> 00:03:28.519 align:start position:0% could run you know C++ contracts and he 00:03:28.519 --> 00:03:33.219 align:start position:0% could run you know C++ contracts and he was<00:03:28.729> them<00:03:29.030> and<00:03:29.389> as<00:03:29.959> a<00:03:30.069> C++<00:03:31.069> expert<00:03:31.699> I<00:03:31.879> said<00:03:32.269> why 00:03:33.219 --> 00:03:33.229 align:start position:0% was them and as a C++ expert I said why 00:03:33.229 --> 00:03:36.189 align:start position:0% was them and as a C++ expert I said why on<00:03:33.560> earth<00:03:34.010> would<00:03:34.909> you<00:03:34.940> want<00:03:35.329> to<00:03:36.019> write 00:03:36.189 --> 00:03:36.199 align:start position:0% on earth would you want to write 00:03:36.199 --> 00:03:39.430 align:start position:0% on earth would you want to write contracts<00:03:36.859> and<00:03:37.099> C++<00:03:37.849> haven't<00:03:38.510> haven't<00:03:39.079> people 00:03:39.430 --> 00:03:39.440 align:start position:0% contracts and C++ haven't haven't people 00:03:39.440 --> 00:03:41.110 align:start position:0% contracts and C++ haven't haven't people lost<00:03:39.799> enough<00:03:40.220> money<00:03:40.489> on<00:03:40.760> the<00:03:40.879> blockchain 00:03:41.110 --> 00:03:41.120 align:start position:0% lost enough money on the blockchain 00:03:41.120 --> 00:03:47.409 align:start position:0% lost enough money on the blockchain already<00:03:45.129> and<00:03:46.129> the<00:03:46.340> other<00:03:46.459> thing<00:03:46.849> that<00:03:46.879> struck 00:03:47.409 --> 00:03:47.419 align:start position:0% already and the other thing that struck 00:03:47.419 --> 00:03:50.800 align:start position:0% already and the other thing that struck me<00:03:47.479> was<00:03:48.220> why<00:03:49.220> on<00:03:49.459> earth<00:03:49.489> would<00:03:50.060> you<00:03:50.090> want<00:03:50.269> to 00:03:50.800 --> 00:03:50.810 align:start position:0% me was why on earth would you want to 00:03:50.810 --> 00:03:54.939 align:start position:0% me was why on earth would you want to hand<00:03:51.139> over<00:03:51.470> to<00:03:52.239> an<00:03:53.239> outside<00:03:53.810> committee<00:03:54.530> the 00:03:54.939 --> 00:03:54.949 align:start position:0% hand over to an outside committee the 00:03:54.949 --> 00:03:58.839 align:start position:0% hand over to an outside committee the definition<00:03:55.909> of<00:03:56.409> anything<00:03:57.409> to<00:03:57.620> do<00:03:57.889> with<00:03:58.280> the 00:03:58.839 --> 00:03:58.849 align:start position:0% definition of anything to do with the 00:03:58.849 --> 00:04:02.710 align:start position:0% definition of anything to do with the core<00:03:59.120> consensus<00:04:00.049> protocol<00:04:00.799> and<00:04:01.519> I<00:04:02.269> looked<00:04:02.540> at 00:04:02.710 --> 00:04:02.720 align:start position:0% core consensus protocol and I looked at 00:04:02.720 --> 00:04:05.800 align:start position:0% core consensus protocol and I looked at Eve<00:04:03.470> you<00:04:03.919> know<00:04:03.979> the<00:04:04.220> current<00:04:04.489> EVM<00:04:05.090> and<00:04:05.510> said 00:04:05.800 --> 00:04:05.810 align:start position:0% Eve you know the current EVM and said 00:04:05.810 --> 00:04:07.599 align:start position:0% Eve you know the current EVM and said there's<00:04:06.199> an<00:04:06.349> awful<00:04:06.680> lot<00:04:06.739> of<00:04:06.949> white<00:04:07.129> space<00:04:07.549> for 00:04:07.599 --> 00:04:07.609 align:start position:0% there's an awful lot of white space for 00:04:07.609 --> 00:04:10.809 align:start position:0% there's an awful lot of white space for more<00:04:08.209> op<00:04:08.449> codes<00:04:08.840> and<00:04:09.340> this<00:04:10.340> thing's<00:04:10.579> not 00:04:10.809 --> 00:04:10.819 align:start position:0% more op codes and this thing's not 00:04:10.819 --> 00:04:11.409 align:start position:0% more op codes and this thing's not broken 00:04:11.409 --> 00:04:11.419 align:start position:0% broken 00:04:11.419 --> 00:04:15.460 align:start position:0% broken it<00:04:11.689> just<00:04:11.959> it<00:04:12.229> needs<00:04:12.439> a<00:04:12.620> little<00:04:12.769> work<00:04:13.989> so<00:04:14.989> I<00:04:15.019> set 00:04:15.460 --> 00:04:15.470 align:start position:0% it just it needs a little work so I set 00:04:15.470 --> 00:04:18.039 align:start position:0% it just it needs a little work so I set out<00:04:15.500> to<00:04:15.709> say<00:04:16.190> what<00:04:16.489> what<00:04:17.030> do<00:04:17.120> we<00:04:17.209> need<00:04:17.419> to<00:04:17.599> do<00:04:17.780> to 00:04:18.039 --> 00:04:18.049 align:start position:0% out to say what what do we need to do to 00:04:18.049 --> 00:04:20.110 align:start position:0% out to say what what do we need to do to this<00:04:18.229> to<00:04:18.680> bring<00:04:19.220> it<00:04:19.400> up<00:04:19.549> to<00:04:19.729> modern<00:04:19.880> standards 00:04:20.110 --> 00:04:20.120 align:start position:0% this to bring it up to modern standards 00:04:20.120 --> 00:04:24.240 align:start position:0% this to bring it up to modern standards and<00:04:21.099> make<00:04:22.099> good<00:04:22.340> use<00:04:22.400> of<00:04:22.639> modern<00:04:23.090> hardware 00:04:24.240 --> 00:04:24.250 align:start position:0% and make good use of modern hardware 00:04:24.250 --> 00:04:27.600 align:start position:0% and make good use of modern hardware and<00:04:24.900> so<00:04:25.900> I<00:04:25.990> got<00:04:26.170> to<00:04:26.230> work<00:04:26.500> on<00:04:26.710> that<00:04:27.010> and<00:04:27.310> I<00:04:27.400> got<00:04:27.580> a 00:04:27.600 --> 00:04:27.610 align:start position:0% and so I got to work on that and I got a 00:04:27.610 --> 00:04:30.780 align:start position:0% and so I got to work on that and I got a lot<00:04:27.820> of<00:04:27.850> help<00:04:28.210> from<00:04:28.630> other<00:04:29.350> people<00:04:29.800> on<00:04:29.920> the<00:04:30.070> C++ 00:04:30.780 --> 00:04:30.790 align:start position:0% lot of help from other people on the C++ 00:04:30.790 --> 00:04:34.200 align:start position:0% lot of help from other people on the C++ team<00:04:31.620> the<00:04:32.670> documentation<00:04:33.670> would<00:04:33.820> not<00:04:34.030> have 00:04:34.200 --> 00:04:34.210 align:start position:0% team the documentation would not have 00:04:34.210 --> 00:04:39.840 align:start position:0% team the documentation would not have happened<00:04:34.630> without<00:04:34.780> Christian<00:04:36.630> and<00:04:38.790> so<00:04:39.790> the 00:04:39.840 --> 00:04:39.850 align:start position:0% happened without Christian and so the 00:04:39.850 --> 00:04:41.640 align:start position:0% happened without Christian and so the team<00:04:40.120> put<00:04:40.390> a<00:04:40.420> fair<00:04:40.690> amount<00:04:40.780> of<00:04:41.050> work<00:04:41.230> into<00:04:41.500> that 00:04:41.640 --> 00:04:41.650 align:start position:0% team put a fair amount of work into that 00:04:41.650 --> 00:04:44.910 align:start position:0% team put a fair amount of work into that we've<00:04:42.250> got<00:04:42.430> a<00:04:42.460> couple<00:04:42.760> of<00:04:42.940> the<00:04:43.030> IPS<00:04:43.800> Martin<00:04:44.800> has 00:04:44.910 --> 00:04:44.920 align:start position:0% we've got a couple of the IPS Martin has 00:04:44.920 --> 00:04:47.460 align:start position:0% we've got a couple of the IPS Martin has put<00:04:45.160> a<00:04:45.190> lot<00:04:45.430> of<00:04:45.550> work<00:04:45.790> into<00:04:46.330> the<00:04:46.810> EU<00:04:46.990> Azzam 00:04:47.460 --> 00:04:47.470 align:start position:0% put a lot of work into the EU Azzam 00:04:47.470 --> 00:04:50.310 align:start position:0% put a lot of work into the EU Azzam proposal<00:04:48.190> so<00:04:49.060> they're<00:04:49.450> sitting<00:04:49.780> there<00:04:49.810> and 00:04:50.310 --> 00:04:50.320 align:start position:0% proposal so they're sitting there and 00:04:50.320 --> 00:04:53.730 align:start position:0% proposal so they're sitting there and we'll<00:04:50.710> need<00:04:51.130> to<00:04:51.190> make<00:04:51.460> some<00:04:51.760> choices<00:04:52.030> and<00:04:52.740> we 00:04:53.730 --> 00:04:53.740 align:start position:0% we'll need to make some choices and we 00:04:53.740 --> 00:04:56.970 align:start position:0% we'll need to make some choices and we might<00:04:53.950> throw<00:04:54.490> both<00:04:54.760> of<00:04:54.790> them<00:04:55.120> away<00:04:55.420> and<00:04:55.810> say<00:04:56.410> oK 00:04:56.970 --> 00:04:56.980 align:start position:0% might throw both of them away and say oK 00:04:56.980 --> 00:04:59.340 align:start position:0% might throw both of them away and say oK we've<00:04:57.280> learned<00:04:57.580> a<00:04:57.760> lot<00:04:58.020> what<00:04:59.020> should<00:04:59.230> we 00:04:59.340 --> 00:04:59.350 align:start position:0% we've learned a lot what should we 00:04:59.350 --> 00:05:01.620 align:start position:0% we've learned a lot what should we actually<00:04:59.560> do<00:05:00.010> we<00:05:00.460> might<00:05:00.700> choose<00:05:00.970> one<00:05:01.240> of<00:05:01.270> them 00:05:01.620 --> 00:05:01.630 align:start position:0% actually do we might choose one of them 00:05:01.630 --> 00:05:04.770 align:start position:0% actually do we might choose one of them we<00:05:02.470> might<00:05:02.680> stick<00:05:02.980> with<00:05:03.190> what<00:05:03.370> we<00:05:03.520> have<00:05:03.790> and<00:05:04.180> ask 00:05:04.770 --> 00:05:04.780 align:start position:0% we might stick with what we have and ask 00:05:04.780 --> 00:05:08.030 align:start position:0% we might stick with what we have and ask and<00:05:05.260> we<00:05:05.440> advance<00:05:06.010> our<00:05:06.280> compiler<00:05:06.820> technology 00:05:08.030 --> 00:05:08.040 align:start position:0% and we advance our compiler technology 00:05:08.040 --> 00:05:12.660 align:start position:0% and we advance our compiler technology to<00:05:09.040> compile<00:05:09.970> what<00:05:10.390> we<00:05:10.510> have<00:05:10.750> in<00:05:11.170> to<00:05:11.560> code<00:05:11.890> yeah 00:05:12.660 --> 00:05:12.670 align:start position:0% to compile what we have in to code yeah 00:05:12.670 --> 00:05:15.390 align:start position:0% to compile what we have in to code yeah that<00:05:13.120> runs<00:05:13.330> better<00:05:13.630> and<00:05:14.170> Pavel<00:05:14.860> can<00:05:15.070> speak 00:05:15.390 --> 00:05:15.400 align:start position:0% that runs better and Pavel can speak 00:05:15.400 --> 00:05:19.730 align:start position:0% that runs better and Pavel can speak better<00:05:15.730> to<00:05:16.560> how<00:05:17.560> possible<00:05:18.220> that<00:05:18.400> actually<00:05:18.880> is 00:05:19.730 --> 00:05:19.740 align:start position:0% better to how possible that actually is 00:05:19.740 --> 00:05:23.460 align:start position:0% better to how possible that actually is yeah<00:05:20.740> I<00:05:20.770> would<00:05:21.280> be<00:05:21.460> very<00:05:22.090> happy<00:05:22.419> to<00:05:22.540> have<00:05:22.810> any 00:05:23.460 --> 00:05:23.470 align:start position:0% yeah I would be very happy to have any 00:05:23.470 --> 00:05:26.760 align:start position:0% yeah I would be very happy to have any of<00:05:23.710> these<00:05:23.890> but<00:05:24.630> to<00:05:25.630> add<00:05:25.780> it<00:05:25.960> more<00:05:26.169> constrained 00:05:26.760 --> 00:05:26.770 align:start position:0% of these but to add it more constrained 00:05:26.770 --> 00:05:28.890 align:start position:0% of these but to add it more constrained to<00:05:27.100> the<00:05:27.250> control<00:05:27.790> flow<00:05:28.060> would<00:05:28.330> help<00:05:28.750> a<00:05:28.870> lot 00:05:28.890 --> 00:05:28.900 align:start position:0% to the control flow would help a lot 00:05:28.900 --> 00:05:31.020 align:start position:0% to the control flow would help a lot there<00:05:29.290> and<00:05:29.320> I<00:05:29.860> believe<00:05:30.250> who<00:05:30.370> can<00:05:30.580> do<00:05:30.760> much 00:05:31.020 --> 00:05:31.030 align:start position:0% there and I believe who can do much 00:05:31.030 --> 00:05:33.570 align:start position:0% there and I believe who can do much better<00:05:31.300> in<00:05:31.540> grid-like<00:05:31.980> EVMS<00:05:32.980> if<00:05:33.220> you<00:05:33.370> have 00:05:33.570 --> 00:05:33.580 align:start position:0% better in grid-like EVMS if you have 00:05:33.580 --> 00:05:38.600 align:start position:0% better in grid-like EVMS if you have that<00:05:35.490> but<00:05:36.490> you<00:05:36.580> know<00:05:36.700> just<00:05:36.910> a<00:05:37.120> step<00:05:37.450> back<00:05:37.720> so 00:05:38.600 --> 00:05:38.610 align:start position:0% that but you know just a step back so 00:05:38.610 --> 00:05:41.580 align:start position:0% that but you know just a step back so last<00:05:39.610> year<00:05:39.850> when<00:05:40.060> you<00:05:40.810> came<00:05:40.990> around<00:05:41.110> and<00:05:41.470> even 00:05:41.580 --> 00:05:41.590 align:start position:0% last year when you came around and even 00:05:41.590 --> 00:05:44.159 align:start position:0% last year when you came around and even 1.5<00:05:42.250> came<00:05:42.490> around<00:05:42.700> it<00:05:43.270> was<00:05:43.390> still<00:05:43.540> in<00:05:43.630> a<00:05:43.720> point 00:05:44.159 --> 00:05:44.169 align:start position:0% 1.5 came around it was still in a point 00:05:44.169 --> 00:05:45.810 align:start position:0% 1.5 came around it was still in a point of<00:05:44.260> time<00:05:44.500> where<00:05:44.770> web<00:05:45.100> assembly<00:05:45.520> was<00:05:45.640> not 00:05:45.810 --> 00:05:45.820 align:start position:0% of time where web assembly was not 00:05:45.820 --> 00:05:48.300 align:start position:0% of time where web assembly was not finalized<00:05:46.270> at<00:05:46.419> all<00:05:46.540> right<00:05:47.260> and<00:05:47.470> there<00:05:47.800> was<00:05:47.979> no 00:05:48.300 --> 00:05:48.310 align:start position:0% finalized at all right and there was no 00:05:48.310 --> 00:05:50.490 align:start position:0% finalized at all right and there was no knowledge<00:05:48.669> at<00:05:49.270> least<00:05:49.600> we<00:05:49.780> didn't<00:05:50.229> have<00:05:50.290> any 00:05:50.490 --> 00:05:50.500 align:start position:0% knowledge at least we didn't have any 00:05:50.500 --> 00:05:52.909 align:start position:0% knowledge at least we didn't have any knowledge<00:05:50.680> when<00:05:51.580> it's<00:05:51.729> gonna<00:05:51.820> be<00:05:51.970> finalized 00:05:52.909 --> 00:05:52.919 align:start position:0% knowledge when it's gonna be finalized 00:05:52.919 --> 00:05:56.640 align:start position:0% knowledge when it's gonna be finalized and<00:05:53.919> since<00:05:54.910> then<00:05:55.210> this<00:05:55.630> year<00:05:55.900> the<00:05:56.500> first 00:05:56.640 --> 00:05:56.650 align:start position:0% and since then this year the first 00:05:56.650 --> 00:05:58.800 align:start position:0% and since then this year the first version<00:05:57.010> came<00:05:57.160> out<00:05:57.280> so<00:05:58.090> that<00:05:58.240> problem<00:05:58.630> went 00:05:58.800 --> 00:05:58.810 align:start position:0% version came out so that problem went 00:05:58.810 --> 00:06:02.100 align:start position:0% version came out so that problem went away<00:05:58.900> and<00:05:59.760> you<00:06:00.760> know<00:06:00.850> like<00:06:01.240> Beck<00:06:01.660> a<00:06:01.690> year<00:06:01.930> ago 00:06:02.100 --> 00:06:02.110 align:start position:0% away and you know like Beck a year ago 00:06:02.110 --> 00:06:03.270 align:start position:0% away and you know like Beck a year ago we<00:06:02.350> had<00:06:02.470> no<00:06:02.500> idea<00:06:02.830> when<00:06:02.919> it's<00:06:02.950> gonna<00:06:03.130> be 00:06:03.270 --> 00:06:03.280 align:start position:0% we had no idea when it's gonna be 00:06:03.280 --> 00:06:04.590 align:start position:0% we had no idea when it's gonna be finalized<00:06:03.700> and<00:06:03.910> how<00:06:04.120> it's<00:06:04.240> gonna<00:06:04.300> look<00:06:04.540> like 00:06:04.590 --> 00:06:04.600 align:start position:0% finalized and how it's gonna look like 00:06:04.600 --> 00:06:07.110 align:start position:0% finalized and how it's gonna look like when<00:06:05.440> it's<00:06:05.560> finalized<00:06:05.950> and<00:06:06.700> so<00:06:06.850> there<00:06:07.000> was<00:06:07.090> a 00:06:07.110 --> 00:06:07.120 align:start position:0% when it's finalized and so there was a 00:06:07.120 --> 00:06:09.870 align:start position:0% when it's finalized and so there was a big<00:06:07.270> concern<00:06:07.450> and<00:06:08.169> I<00:06:08.919> think<00:06:09.190> because<00:06:09.580> of<00:06:09.610> that 00:06:09.870 --> 00:06:09.880 align:start position:0% big concern and I think because of that 00:06:09.880 --> 00:06:12.630 align:start position:0% big concern and I think because of that even<00:06:10.240> 1.5<00:06:10.750> made<00:06:10.930> a<00:06:10.960> lot<00:06:11.140> of<00:06:11.169> sense<00:06:11.650> to<00:06:11.979> maybe 00:06:12.630 --> 00:06:12.640 align:start position:0% even 1.5 made a lot of sense to maybe 00:06:12.640 --> 00:06:15.030 align:start position:0% even 1.5 made a lot of sense to maybe bridge<00:06:12.970> the<00:06:13.120> gap<00:06:13.300> or<00:06:13.570> have<00:06:14.140> like<00:06:14.290> a<00:06:14.350> you<00:06:15.010> know 00:06:15.030 --> 00:06:15.040 align:start position:0% bridge the gap or have like a you know 00:06:15.040 --> 00:06:19.110 align:start position:0% bridge the gap or have like a you know back-up<00:06:15.430> plan<00:06:16.320> assuming<00:06:17.320> that<00:06:17.470> EVM<00:06:17.770> 2.0<00:06:18.310> would 00:06:19.110 --> 00:06:19.120 align:start position:0% back-up plan assuming that EVM 2.0 would 00:06:19.120 --> 00:06:20.790 align:start position:0% back-up plan assuming that EVM 2.0 would be<00:06:19.240> finished<00:06:19.479> in<00:06:19.720> time<00:06:19.960> but<00:06:20.229> we<00:06:20.470> cannot 00:06:20.790 --> 00:06:20.800 align:start position:0% be finished in time but we cannot 00:06:20.800 --> 00:06:23.250 align:start position:0% be finished in time but we cannot release<00:06:21.729> it<00:06:21.940> because<00:06:22.240> the<00:06:22.479> web<00:06:22.900> assembly 00:06:23.250 --> 00:06:23.260 align:start position:0% release it because the web assembly 00:06:23.260 --> 00:06:26.130 align:start position:0% release it because the web assembly isn't<00:06:23.530> finished<00:06:23.950> and<00:06:24.940> then<00:06:25.240> if<00:06:25.600> he<00:06:25.930> could 00:06:26.130 --> 00:06:26.140 align:start position:0% isn't finished and then if he could 00:06:26.140 --> 00:06:28.469 align:start position:0% isn't finished and then if he could finish<00:06:26.290> even<00:06:26.530> 1.5<00:06:27.520> quickly<00:06:27.910> enough<00:06:28.090> it<00:06:28.270> could 00:06:28.469 --> 00:06:28.479 align:start position:0% finish even 1.5 quickly enough it could 00:06:28.479 --> 00:06:32.460 align:start position:0% finish even 1.5 quickly enough it could be<00:06:28.600> a<00:06:28.630> good<00:06:28.870> bridge<00:06:29.800> between<00:06:30.070> the<00:06:30.370> two<00:06:31.470> but 00:06:32.460 --> 00:06:32.470 align:start position:0% be a good bridge between the two but 00:06:32.470 --> 00:06:34.410 align:start position:0% be a good bridge between the two but that<00:06:32.620> problem<00:06:32.890> went<00:06:33.190> away<00:06:33.310> today 00:06:34.410 --> 00:06:34.420 align:start position:0% that problem went away today 00:06:34.420 --> 00:06:36.360 align:start position:0% that problem went away today you<00:06:34.450> know<00:06:34.570> the<00:06:34.720> earlier<00:06:35.020> this<00:06:35.200> year<00:06:35.260> so<00:06:36.160> how<00:06:36.310> do 00:06:36.360 --> 00:06:36.370 align:start position:0% you know the earlier this year so how do 00:06:36.370 --> 00:06:38.760 align:start position:0% you know the earlier this year so how do you<00:06:36.520> feel<00:06:36.640> about<00:06:36.910> the<00:06:37.320> brokenness<00:06:38.320> of 00:06:38.760 --> 00:06:38.770 align:start position:0% you feel about the brokenness of 00:06:38.770 --> 00:06:42.450 align:start position:0% you feel about the brokenness of evm<00:06:39.280> since<00:06:39.790> did<00:06:40.750> did<00:06:41.530> anything<00:06:41.740> change 00:06:42.450 --> 00:06:42.460 align:start position:0% evm since did did anything change 00:06:42.460 --> 00:06:47.720 align:start position:0% evm since did did anything change I<00:06:43.260> actually<00:06:44.460> I<00:06:45.460> think<00:06:46.030> he<00:06:46.180> wasn't<00:06:46.390> gonna<00:06:46.750> die 00:06:47.720 --> 00:06:47.730 align:start position:0% I actually I think he wasn't gonna die 00:06:47.730 --> 00:06:50.490 align:start position:0% I actually I think he wasn't gonna die why<00:06:48.730> do<00:06:48.790> you<00:06:48.940> think<00:06:49.060> that<00:06:49.270> because<00:06:50.080> there's 00:06:50.490 --> 00:06:50.500 align:start position:0% why do you think that because there's 00:06:50.500 --> 00:06:52.680 align:start position:0% why do you think that because there's been<00:06:50.680> so<00:06:50.980> many<00:06:51.160> attempts<00:06:51.910> to<00:06:52.150> get<00:06:52.330> a<00:06:52.360> binary 00:06:52.680 --> 00:06:52.690 align:start position:0% been so many attempts to get a binary 00:06:52.690 --> 00:06:55.140 align:start position:0% been so many attempts to get a binary format<00:06:53.320> running<00:06:54.070> in<00:06:54.220> browsers<00:06:54.700> and<00:06:55.000> they've 00:06:55.140 --> 00:06:55.150 align:start position:0% format running in browsers and they've 00:06:55.150 --> 00:06:58.530 align:start position:0% format running in browsers and they've all<00:06:55.330> failed<00:06:56.370> you're<00:06:57.370> saying<00:06:57.640> webassembly<00:06:58.210> is 00:06:58.530 --> 00:06:58.540 align:start position:0% all failed you're saying webassembly is 00:06:58.540 --> 00:07:02.190 align:start position:0% all failed you're saying webassembly is gonna<00:06:58.720> die<00:06:58.990> no<00:07:00.300> one's<00:07:01.300> gonna<00:07:01.450> die<00:07:01.750> whatever<00:07:02.140> I 00:07:02.190 --> 00:07:02.200 align:start position:0% gonna die no one's gonna die whatever I 00:07:02.200 --> 00:07:06.270 align:start position:0% gonna die no one's gonna die whatever I said<00:07:03.420> that's<00:07:04.420> a<00:07:04.540> bold<00:07:04.750> prediction<00:07:04.930> but<00:07:05.380> we<00:07:06.130> can 00:07:06.270 --> 00:07:06.280 align:start position:0% said that's a bold prediction but we can 00:07:06.280 --> 00:07:10.500 align:start position:0% said that's a bold prediction but we can step<00:07:06.520> back<00:07:06.580> and<00:07:08.640> say<00:07:09.640> what<00:07:09.880> are<00:07:09.970> the<00:07:10.090> problems 00:07:10.500 --> 00:07:10.510 align:start position:0% step back and say what are the problems 00:07:10.510 --> 00:07:13.800 align:start position:0% step back and say what are the problems with<00:07:10.630> the<00:07:10.870> current<00:07:11.080> evm<00:07:12.060> 1.0<00:07:13.060> I<00:07:13.330> mean<00:07:13.540> one 00:07:13.800 --> 00:07:13.810 align:start position:0% with the current evm 1.0 I mean one 00:07:13.810 --> 00:07:18.060 align:start position:0% with the current evm 1.0 I mean one problem<00:07:14.260> is<00:07:14.500> that<00:07:15.780> the<00:07:16.780> gas<00:07:16.990> limit<00:07:17.350> in<00:07:17.710> each 00:07:18.060 --> 00:07:18.070 align:start position:0% problem is that the gas limit in each 00:07:18.070 --> 00:07:21.630 align:start position:0% problem is that the gas limit in each block<00:07:18.370> is<00:07:19.440> not<00:07:20.440> enough<00:07:20.710> to<00:07:20.890> do<00:07:21.070> everything 00:07:21.630 --> 00:07:21.640 align:start position:0% block is not enough to do everything 00:07:21.640 --> 00:07:23.670 align:start position:0% block is not enough to do everything people<00:07:22.000> would<00:07:22.210> like<00:07:22.390> to<00:07:22.540> deploy<00:07:22.810> contracts<00:07:23.560> to 00:07:23.670 --> 00:07:23.680 align:start position:0% people would like to deploy contracts to 00:07:23.680 --> 00:07:27.840 align:start position:0% people would like to deploy contracts to do<00:07:23.830> is<00:07:24.540> one<00:07:25.540> example<00:07:25.900> is<00:07:26.200> the<00:07:26.470> Blake<00:07:27.370> to<00:07:27.640> be 00:07:27.840 --> 00:07:27.850 align:start position:0% do is one example is the Blake to be 00:07:27.850 --> 00:07:30.630 align:start position:0% do is one example is the Blake to be pre-compile<00:07:28.830> there's<00:07:29.830> a<00:07:29.920> proposal<00:07:30.220> for<00:07:30.520> these 00:07:30.630 --> 00:07:30.640 align:start position:0% pre-compile there's a proposal for these 00:07:30.640 --> 00:07:34.560 align:start position:0% pre-compile there's a proposal for these native<00:07:30.970> pre<00:07:31.330> compiles<00:07:32.310> and<00:07:33.570> pre-compiled 00:07:34.560 --> 00:07:34.570 align:start position:0% native pre compiles and pre-compiled 00:07:34.570 --> 00:07:37.350 align:start position:0% native pre compiles and pre-compiled solve<00:07:34.870> the<00:07:35.020> problem<00:07:35.410> of<00:07:36.300> contracts<00:07:37.300> that 00:07:37.350 --> 00:07:37.360 align:start position:0% solve the problem of contracts that 00:07:37.360 --> 00:07:38.550 align:start position:0% solve the problem of contracts that people<00:07:37.570> would<00:07:37.690> like<00:07:37.810> to<00:07:37.900> deploy<00:07:38.140> but<00:07:38.440> they 00:07:38.550 --> 00:07:38.560 align:start position:0% people would like to deploy but they 00:07:38.560 --> 00:07:40.380 align:start position:0% people would like to deploy but they might<00:07:38.770> take<00:07:38.980> you<00:07:39.640> know<00:07:39.730> a<00:07:39.760> hundred<00:07:40.210> million 00:07:40.380 --> 00:07:40.390 align:start position:0% might take you know a hundred million 00:07:40.390 --> 00:07:44.370 align:start position:0% might take you know a hundred million gas<00:07:40.750> when<00:07:41.170> the<00:07:41.620> current<00:07:41.950> block<00:07:42.460> limit<00:07:42.940> is<00:07:43.380> the 00:07:44.370 --> 00:07:44.380 align:start position:0% gas when the current block limit is the 00:07:44.380 --> 00:07:46.700 align:start position:0% gas when the current block limit is the current<00:07:44.620> block<00:07:44.770> gas<00:07:44.980> limit<00:07:45.160> is<00:07:45.340> 6<00:07:45.550> million<00:07:45.880> gas 00:07:46.700 --> 00:07:46.710 align:start position:0% current block gas limit is 6 million gas 00:07:46.710 --> 00:07:53.360 align:start position:0% current block gas limit is 6 million gas so<00:07:47.710> how<00:07:47.980> does<00:07:48.930> EBM<00:07:49.930> 1.5<00:07:50.500> or<00:07:51.190> or<00:07:52.020> webassembly 00:07:53.360 --> 00:07:53.370 align:start position:0% so how does EBM 1.5 or or webassembly 00:07:53.370 --> 00:07:57.900 align:start position:0% so how does EBM 1.5 or or webassembly solve<00:07:54.370> this<00:07:54.520> problem<00:07:56.190> well<00:07:57.190> of<00:07:57.370> assembly 00:07:57.900 --> 00:07:57.910 align:start position:0% solve this problem well of assembly 00:07:57.910 --> 00:08:00.170 align:start position:0% solve this problem well of assembly allows<00:07:58.210> you<00:07:58.510> would<00:07:59.020> allow<00:07:59.170> you<00:07:59.230> to<00:07:59.560> can<00:07:59.680> just 00:08:00.170 --> 00:08:00.180 align:start position:0% allows you would allow you to can just 00:08:00.180 --> 00:08:04.320 align:start position:0% allows you would allow you to can just compile<00:08:01.180> code<00:08:02.100> directly<00:08:03.100> to<00:08:03.370> web<00:08:03.580> assembly<00:08:04.090> so 00:08:04.320 --> 00:08:04.330 align:start position:0% compile code directly to web assembly so 00:08:04.330 --> 00:08:08.430 align:start position:0% compile code directly to web assembly so you<00:08:04.650> most<00:08:05.650> likely<00:08:05.830> don't<00:08:06.100> need<00:08:06.250> native<00:08:07.440> native 00:08:08.430 --> 00:08:08.440 align:start position:0% you most likely don't need native native 00:08:08.440 --> 00:08:10.680 align:start position:0% you most likely don't need native native contracts<00:08:08.920> because<00:08:09.070> you<00:08:10.000> would<00:08:10.120> just<00:08:10.150> write 00:08:10.680 --> 00:08:10.690 align:start position:0% contracts because you would just write 00:08:10.690 --> 00:08:16.410 align:start position:0% contracts because you would just write them<00:08:10.870> and<00:08:11.020> whip<00:08:11.170> assembly<00:08:14.880> but<00:08:15.880> it's<00:08:16.060> partly 00:08:16.410 --> 00:08:16.420 align:start position:0% them and whip assembly but it's partly 00:08:16.420 --> 00:08:21.260 align:start position:0% them and whip assembly but it's partly just<00:08:17.350> that<00:08:17.500> it's<00:08:17.680> too<00:08:17.860> slow<00:08:19.290> you<00:08:20.290> know<00:08:20.350> I<00:08:20.440> mean 00:08:21.260 --> 00:08:21.270 align:start position:0% just that it's too slow you know I mean 00:08:21.270 --> 00:08:24.540 align:start position:0% just that it's too slow you know I mean pavel<00:08:22.270> was<00:08:22.450> working<00:08:22.930> i<00:08:23.260> remember<00:08:24.100> on<00:08:24.310> one<00:08:24.340> of 00:08:24.540 --> 00:08:24.550 align:start position:0% pavel was working i remember on one of 00:08:24.550 --> 00:08:27.360 align:start position:0% pavel was working i remember on one of the<00:08:24.700> pre<00:08:24.910> compiles<00:08:25.800> that<00:08:26.800> you<00:08:26.980> were<00:08:27.130> like 00:08:27.360 --> 00:08:27.370 align:start position:0% the pre compiles that you were like 00:08:27.370 --> 00:08:29.850 align:start position:0% the pre compiles that you were like pushing<00:08:27.880> all<00:08:28.090> the<00:08:28.270> compiler<00:08:28.870> flags<00:08:29.200> as<00:08:29.500> far<00:08:29.740> as 00:08:29.850 --> 00:08:29.860 align:start position:0% pushing all the compiler flags as far as 00:08:29.860 --> 00:08:33.000 align:start position:0% pushing all the compiler flags as far as you<00:08:30.040> could<00:08:30.310> and<00:08:30.730> trolling<00:08:31.540> through<00:08:32.010> multi 00:08:33.000 --> 00:08:33.010 align:start position:0% you could and trolling through multi 00:08:33.010 --> 00:08:35.700 align:start position:0% you could and trolling through multi precision<00:08:33.640> libraries<00:08:34.450> to<00:08:34.690> find<00:08:34.990> one<00:08:35.290> that<00:08:35.560> was 00:08:35.700 --> 00:08:35.710 align:start position:0% precision libraries to find one that was 00:08:35.710 --> 00:08:41.790 align:start position:0% precision libraries to find one that was mostly<00:08:36.190> an<00:08:36.520> hand-coded<00:08:37.240> assembly<00:08:40.710> you<00:08:41.710> know 00:08:41.790 --> 00:08:41.800 align:start position:0% mostly an hand-coded assembly you know 00:08:41.800 --> 00:08:43.800 align:start position:0% mostly an hand-coded assembly you know we<00:08:41.920> just<00:08:41.950> can't<00:08:42.310> get<00:08:42.550> enough<00:08:42.700> speed<00:08:43.330> out<00:08:43.750> of 00:08:43.800 --> 00:08:43.810 align:start position:0% we just can't get enough speed out of 00:08:43.810 --> 00:08:44.950 align:start position:0% we just can't get enough speed out of the<00:08:44.260> VM 00:08:44.950 --> 00:08:44.960 align:start position:0% the VM 00:08:44.960 --> 00:08:48.340 align:start position:0% the VM for<00:08:45.230> these<00:08:45.380> free<00:08:45.620> compiles<00:08:46.250> but<00:08:47.120> then<00:08:47.930> how<00:08:48.110> is 00:08:48.340 --> 00:08:48.350 align:start position:0% for these free compiles but then how is 00:08:48.350 --> 00:08:52.090 align:start position:0% for these free compiles but then how is 1.5<00:08:49.040> in<00:08:49.430> in<00:08:49.670> 2.0<00:08:50.510> how<00:08:50.690> are<00:08:50.840> those<00:08:51.100> coming 00:08:52.090 --> 00:08:52.100 align:start position:0% 1.5 in in 2.0 how are those coming 00:08:52.100 --> 00:08:56.770 align:start position:0% 1.5 in in 2.0 how are those coming faster<00:08:52.700> than<00:08:53.770> then<00:08:54.770> 1.0<00:08:55.520> i'm<00:08:56.090> just<00:08:56.270> like<00:08:56.570> my 00:08:56.770 --> 00:08:56.780 align:start position:0% faster than then 1.0 i'm just like my 00:08:56.780 --> 00:08:59.680 align:start position:0% faster than then 1.0 i'm just like my little<00:08:56.960> grade<00:08:57.230> school<00:08:57.590> example<00:08:58.510> you<00:08:59.510> do<00:08:59.660> a 00:08:59.680 --> 00:08:59.690 align:start position:0% little grade school example you do a 00:08:59.690 --> 00:09:01.510 align:start position:0% little grade school example you do a multiply<00:09:00.320> and<00:09:00.350> you're<00:09:00.830> doing<00:09:01.190> one 00:09:01.510 --> 00:09:01.520 align:start position:0% multiply and you're doing one 00:09:01.520 --> 00:09:04.120 align:start position:0% multiply and you're doing one instruction<00:09:02.300> on<00:09:02.450> a<00:09:02.480> 64-bit<00:09:03.410> pair<00:09:04.010> of 00:09:04.120 --> 00:09:04.130 align:start position:0% instruction on a 64-bit pair of 00:09:04.130 --> 00:09:08.980 align:start position:0% instruction on a 64-bit pair of registers<00:09:04.700> as<00:09:05.030> opposed<00:09:05.960> to<00:09:06.520> you<00:09:07.520> know<00:09:07.990> long 00:09:08.980 --> 00:09:08.990 align:start position:0% registers as opposed to you know long 00:09:08.990 --> 00:09:12.610 align:start position:0% registers as opposed to you know long division<00:09:09.410> or<00:09:09.860> long<00:09:10.360> multiplication<00:09:11.360> on<00:09:11.660> a<00:09:11.690> you 00:09:12.610 --> 00:09:12.620 align:start position:0% division or long multiplication on a you 00:09:12.620 --> 00:09:16.870 align:start position:0% division or long multiplication on a you know<00:09:12.700> collection<00:09:13.700> of<00:09:13.880> registers<00:09:15.490> I<00:09:16.490> think 00:09:16.870 --> 00:09:16.880 align:start position:0% know collection of registers I think 00:09:16.880 --> 00:09:20.440 align:start position:0% know collection of registers I think that<00:09:17.420> the<00:09:17.660> current<00:09:18.020> if<00:09:18.170> you<00:09:18.320> have<00:09:18.680> is<00:09:19.450> quite 00:09:20.440 --> 00:09:20.450 align:start position:0% that the current if you have is quite 00:09:20.450 --> 00:09:22.750 align:start position:0% that the current if you have is quite big<00:09:20.960> difference<00:09:21.500> in<00:09:21.890> terms<00:09:22.250> of<00:09:22.430> speed 00:09:22.750 --> 00:09:22.760 align:start position:0% big difference in terms of speed 00:09:22.760 --> 00:09:26.200 align:start position:0% big difference in terms of speed comparing<00:09:23.390> to<00:09:23.570> native<00:09:23.900> code<00:09:24.200> so<00:09:25.100> we<00:09:25.550> we<00:09:25.880> cannot 00:09:26.200 --> 00:09:26.210 align:start position:0% comparing to native code so we we cannot 00:09:26.210 --> 00:09:29.590 align:start position:0% comparing to native code so we we cannot actually<00:09:26.780> effectively<00:09:28.150> encode<00:09:29.150> the 00:09:29.590 --> 00:09:29.600 align:start position:0% actually effectively encode the 00:09:29.600 --> 00:09:32.110 align:start position:0% actually effectively encode the algorithm<00:09:30.200> we<00:09:30.320> want<00:09:30.530> there<00:09:30.800> for<00:09:31.550> example<00:09:31.790> some 00:09:32.110 --> 00:09:32.120 align:start position:0% algorithm we want there for example some 00:09:32.120 --> 00:09:36.070 align:start position:0% algorithm we want there for example some hash<00:09:32.300> functions<00:09:32.840> and<00:09:33.400> and<00:09:34.400> that<00:09:34.820> makes<00:09:35.150> them 00:09:36.070 --> 00:09:36.080 align:start position:0% hash functions and and that makes them 00:09:36.080 --> 00:09:38.890 align:start position:0% hash functions and and that makes them if<00:09:36.440> if<00:09:37.010> you<00:09:37.190> like<00:09:37.400> to<00:09:37.610> implement<00:09:38.240> them<00:09:38.390> in<00:09:38.630> pure 00:09:38.890 --> 00:09:38.900 align:start position:0% if if you like to implement them in pure 00:09:38.900 --> 00:09:42.130 align:start position:0% if if you like to implement them in pure smart<00:09:39.230> contracts<00:09:39.860> that<00:09:40.700> make<00:09:41.140> quite 00:09:42.130 --> 00:09:42.140 align:start position:0% smart contracts that make quite 00:09:42.140 --> 00:09:45.760 align:start position:0% smart contracts that make quite expensive<00:09:42.620> and<00:09:43.780> you<00:09:44.780> have<00:09:44.810> to<00:09:45.170> pay<00:09:45.350> for<00:09:45.410> that 00:09:45.760 --> 00:09:45.770 align:start position:0% expensive and you have to pay for that 00:09:45.770 --> 00:09:48.240 align:start position:0% expensive and you have to pay for that you<00:09:46.070> have<00:09:46.910> to<00:09:47.180> pay<00:09:47.360> a<00:09:47.390> lot<00:09:47.570> for<00:09:47.630> that<00:09:47.870> because 00:09:48.240 --> 00:09:48.250 align:start position:0% you have to pay a lot for that because 00:09:48.250 --> 00:09:52.360 align:start position:0% you have to pay a lot for that because it's<00:09:49.250> just<00:09:49.660> the<00:09:50.660> current<00:09:50.960> EVM<00:09:51.500> is<00:09:51.680> not<00:09:51.920> capable 00:09:52.360 --> 00:09:52.370 align:start position:0% it's just the current EVM is not capable 00:09:52.370 --> 00:09:57.970 align:start position:0% it's just the current EVM is not capable of<00:09:52.900> Express<00:09:53.900> enough<00:09:56.080> to<00:09:57.080> have<00:09:57.290> comparable 00:09:57.970 --> 00:09:57.980 align:start position:0% of Express enough to have comparable 00:09:57.980 --> 00:10:01.420 align:start position:0% of Express enough to have comparable speed<00:09:58.690> comparing<00:09:59.690> to<00:09:59.840> native<00:10:00.170> code<00:10:00.440> and<00:10:00.680> I 00:10:01.420 --> 00:10:01.430 align:start position:0% speed comparing to native code and I 00:10:01.430 --> 00:10:03.490 align:start position:0% speed comparing to native code and I believe<00:10:01.880> that's<00:10:02.060> what<00:10:02.540> for<00:10:02.930> example<00:10:03.380> web 00:10:03.490 --> 00:10:03.500 align:start position:0% believe that's what for example web 00:10:03.500 --> 00:10:06.760 align:start position:0% believe that's what for example web assembly<00:10:04.010> gives<00:10:04.250> like<00:10:05.180> it's<00:10:05.780> it's<00:10:06.230> at<00:10:06.530> least 00:10:06.760 --> 00:10:06.770 align:start position:0% assembly gives like it's it's at least 00:10:06.770 --> 00:10:09.790 align:start position:0% assembly gives like it's it's at least comparable<00:10:07.370> like<00:10:07.760> if<00:10:07.940> you<00:10:08.120> implement<00:10:08.800> the 00:10:09.790 --> 00:10:09.800 align:start position:0% comparable like if you implement the 00:10:09.800 --> 00:10:13.090 align:start position:0% comparable like if you implement the same<00:10:10.010> heart<00:10:10.280> function<00:10:10.790> in<00:10:11.450> in<00:10:12.080> C<00:10:12.410> and<00:10:12.680> web 00:10:13.090 --> 00:10:13.100 align:start position:0% same heart function in in C and web 00:10:13.100 --> 00:10:15.550 align:start position:0% same heart function in in C and web assembly<00:10:13.670> at<00:10:14.240> least<00:10:14.600> you<00:10:14.690> have<00:10:14.840> compare<00:10:15.290> both 00:10:15.550 --> 00:10:15.560 align:start position:0% assembly at least you have compare both 00:10:15.560 --> 00:10:20.650 align:start position:0% assembly at least you have compare both of<00:10:15.590> them<00:10:15.950> and<00:10:16.250> not<00:10:16.970> having<00:10:17.270> like<00:10:18.340> times<00:10:19.660> time 00:10:20.650 --> 00:10:20.660 align:start position:0% of them and not having like times time 00:10:20.660 --> 00:10:25.350 align:start position:0% of them and not having like times time ten<00:10:21.350> to<00:10:21.410> two<00:10:22.010> 100<00:10:22.580> times<00:10:22.910> slower<00:10:23.270> performance 00:10:25.350 --> 00:10:25.360 align:start position:0% ten to two 100 times slower performance 00:10:25.360 --> 00:10:28.270 align:start position:0% ten to two 100 times slower performance but<00:10:26.360> actually<00:10:26.720> if<00:10:26.780> you<00:10:26.810> if<00:10:27.260> you<00:10:27.410> take<00:10:27.950> a<00:10:28.010> step 00:10:28.270 --> 00:10:28.280 align:start position:0% but actually if you if you take a step 00:10:28.280 --> 00:10:30.850 align:start position:0% but actually if you if you take a step back<00:10:28.580> to<00:10:28.910> like<00:10:29.690> the<00:10:29.810> first<00:10:29.930> version<00:10:30.350> of<00:10:30.410> EVM 00:10:30.850 --> 00:10:30.860 align:start position:0% back to like the first version of EVM 00:10:30.860 --> 00:10:34.180 align:start position:0% back to like the first version of EVM and<00:10:31.040> look<00:10:31.880> at<00:10:32.060> why<00:10:32.630> do<00:10:32.690> we<00:10:32.960> have<00:10:33.140> or<00:10:33.470> why<00:10:33.620> did<00:10:34.040> we 00:10:34.180 --> 00:10:34.190 align:start position:0% and look at why do we have or why did we 00:10:34.190 --> 00:10:37.360 align:start position:0% and look at why do we have or why did we had<00:10:34.370> an<00:10:34.580> identity<00:10:35.120> contract<00:10:36.220> just<00:10:37.220> for 00:10:37.360 --> 00:10:37.370 align:start position:0% had an identity contract just for 00:10:37.370 --> 00:10:40.300 align:start position:0% had an identity contract just for achieve<00:10:37.610> memory<00:10:38.030> copying<00:10:38.480> that<00:10:39.440> maybe<00:10:39.920> shows 00:10:40.300 --> 00:10:40.310 align:start position:0% achieve memory copying that maybe shows 00:10:40.310 --> 00:10:43.570 align:start position:0% achieve memory copying that maybe shows that<00:10:41.200> we<00:10:42.200> didn't<00:10:42.500> had<00:10:42.710> everything<00:10:43.010> thought 00:10:43.570 --> 00:10:43.580 align:start position:0% that we didn't had everything thought 00:10:43.580 --> 00:10:46.030 align:start position:0% that we didn't had everything thought through<00:10:43.910> properly<00:10:44.200> and<00:10:45.200> we<00:10:45.680> started<00:10:45.920> to 00:10:46.030 --> 00:10:46.040 align:start position:0% through properly and we started to 00:10:46.040 --> 00:10:48.580 align:start position:0% through properly and we started to introduce<00:10:46.390> these<00:10:47.390> pecan<00:10:47.750> pies<00:10:47.930> especially 00:10:48.580 --> 00:10:48.590 align:start position:0% introduce these pecan pies especially 00:10:48.590 --> 00:10:51.060 align:start position:0% introduce these pecan pies especially the<00:10:48.680> one<00:10:48.800> for<00:10:48.980> copying<00:10:49.280> memory<00:10:49.690> that<00:10:50.690> means 00:10:51.060 --> 00:10:51.070 align:start position:0% the one for copying memory that means 00:10:51.070 --> 00:10:53.080 align:start position:0% the one for copying memory that means loading<00:10:52.070> and<00:10:52.400> storing<00:10:52.490> memory<00:10:52.850> was<00:10:53.000> too 00:10:53.080 --> 00:10:53.090 align:start position:0% loading and storing memory was too 00:10:53.090 --> 00:10:55.360 align:start position:0% loading and storing memory was too expensive<00:10:53.300> yet<00:10:54.020> we<00:10:54.560> still<00:10:54.740> wanted<00:10:55.010> to<00:10:55.070> do<00:10:55.220> it 00:10:55.360 --> 00:10:55.370 align:start position:0% expensive yet we still wanted to do it 00:10:55.370 --> 00:10:57.350 align:start position:0% expensive yet we still wanted to do it so<00:10:55.820> we<00:10:55.910> introduced<00:10:56.180> the<00:10:56.300> pecan<00:10:56.570> pie 00:10:57.350 --> 00:10:57.360 align:start position:0% so we introduced the pecan pie 00:10:57.360 --> 00:11:00.259 align:start position:0% so we introduced the pecan pie and<00:10:57.649> another<00:10:58.649> bigger<00:10:59.249> issue<00:10:59.489> which<00:10:59.939> Craig 00:11:00.259 --> 00:11:00.269 align:start position:0% and another bigger issue which Craig 00:11:00.269 --> 00:11:02.329 align:start position:0% and another bigger issue which Craig mentioned<00:11:00.449> several<00:11:00.869> times<00:11:00.959> already<00:11:01.439> is<00:11:01.769> the 00:11:02.329 --> 00:11:02.339 align:start position:0% mentioned several times already is the 00:11:02.339 --> 00:11:05.079 align:start position:0% mentioned several times already is the bit<00:11:02.549> with<00:11:02.759> everything<00:11:03.540> is<00:11:03.720> 2056<00:11:04.410> bit<00:11:04.619> and 00:11:05.079 --> 00:11:05.089 align:start position:0% bit with everything is 2056 bit and 00:11:05.089 --> 00:11:08.090 align:start position:0% bit with everything is 2056 bit and there<00:11:06.089> was<00:11:06.239> a<00:11:06.420> proposal<00:11:06.779> even<00:11:07.049> before<00:11:07.230> the<00:11:07.589> 1.5 00:11:08.090 --> 00:11:08.100 align:start position:0% there was a proposal even before the 1.5 00:11:08.100 --> 00:11:11.319 align:start position:0% there was a proposal even before the 1.5 to<00:11:08.399> have<00:11:08.579> 64-bit<00:11:09.329> arithmetic<00:11:10.110> syn<00:11:10.379> EVM<00:11:10.739> and 00:11:11.319 --> 00:11:11.329 align:start position:0% to have 64-bit arithmetic syn EVM and 00:11:11.329 --> 00:11:13.789 align:start position:0% to have 64-bit arithmetic syn EVM and you<00:11:12.329> have<00:11:12.629> folded<00:11:12.869> that<00:11:13.110> into<00:11:13.379> the<00:11:13.499> same<00:11:13.679> D 00:11:13.789 --> 00:11:13.799 align:start position:0% you have folded that into the same D 00:11:13.799 --> 00:11:17.269 align:start position:0% you have folded that into the same D proposal<00:11:14.339> as<00:11:14.879> I<00:11:15.029> still<00:11:15.209> there<00:11:15.449> and<00:11:15.709> but<00:11:16.709> if<00:11:16.949> if 00:11:17.269 --> 00:11:17.279 align:start position:0% proposal as I still there and but if if 00:11:17.279 --> 00:11:19.220 align:start position:0% proposal as I still there and but if if we<00:11:17.459> if<00:11:17.489> we<00:11:17.759> just<00:11:17.939> look<00:11:18.119> at<00:11:18.239> these<00:11:18.600> two<00:11:18.660> problems 00:11:19.220 --> 00:11:19.230 align:start position:0% we if we just look at these two problems 00:11:19.230 --> 00:11:21.979 align:start position:0% we if we just look at these two problems that<00:11:19.319> it's<00:11:19.709> quite<00:11:20.009> wide<00:11:20.249> for<00:11:21.239> arithmetic<00:11:21.449> and 00:11:21.979 --> 00:11:21.989 align:start position:0% that it's quite wide for arithmetic and 00:11:21.989 --> 00:11:23.780 align:start position:0% that it's quite wide for arithmetic and we<00:11:22.589> have<00:11:22.769> we<00:11:22.949> started<00:11:23.249> to<00:11:23.339> introduce<00:11:23.639> all 00:11:23.780 --> 00:11:23.790 align:start position:0% we have we started to introduce all 00:11:23.790 --> 00:11:25.549 align:start position:0% we have we started to introduce all these<00:11:23.879> pecan<00:11:24.209> pies<00:11:24.389> just<00:11:24.660> to<00:11:24.989> get<00:11:25.110> around<00:11:25.319> that 00:11:25.549 --> 00:11:25.559 align:start position:0% these pecan pies just to get around that 00:11:25.559 --> 00:11:28.519 align:start position:0% these pecan pies just to get around that that<00:11:26.069> probably<00:11:27.029> shows<00:11:27.449> that<00:11:28.079> we<00:11:28.230> didn't 00:11:28.519 --> 00:11:28.529 align:start position:0% that probably shows that we didn't 00:11:28.529 --> 00:11:31.039 align:start position:0% that probably shows that we didn't figure<00:11:28.739> out<00:11:28.860> the<00:11:29.129> prices<00:11:29.610> properly<00:11:30.059> and<00:11:30.269> which 00:11:31.039 --> 00:11:31.049 align:start position:0% figure out the prices properly and which 00:11:31.049 --> 00:11:33.799 align:start position:0% figure out the prices properly and which webassembly<00:11:31.470> espousal<00:11:32.100> said<00:11:32.339> it's<00:11:32.809> resembles 00:11:33.799 --> 00:11:33.809 align:start position:0% webassembly espousal said it's resembles 00:11:33.809 --> 00:11:35.389 align:start position:0% webassembly espousal said it's resembles the<00:11:33.959> instructions<00:11:34.470> much<00:11:34.679> more<00:11:34.889> closer<00:11:35.100> to 00:11:35.389 --> 00:11:35.399 align:start position:0% the instructions much more closer to 00:11:35.399 --> 00:11:38.109 align:start position:0% the instructions much more closer to traditional<00:11:35.579> computers<00:11:36.299> so<00:11:37.079> there's<00:11:37.379> a<00:11:37.439> much 00:11:38.109 --> 00:11:38.119 align:start position:0% traditional computers so there's a much 00:11:38.119 --> 00:11:40.100 align:start position:0% traditional computers so there's a much probably<00:11:39.119> much<00:11:39.239> easier<00:11:39.269> way<00:11:39.629> to<00:11:39.660> figure<00:11:39.959> out 00:11:40.100 --> 00:11:40.110 align:start position:0% probably much easier way to figure out 00:11:40.110 --> 00:11:41.150 align:start position:0% probably much easier way to figure out what<00:11:40.290> the<00:11:40.379> real<00:11:40.499> cost<00:11:40.829> for<00:11:41.069> those 00:11:41.150 --> 00:11:41.160 align:start position:0% what the real cost for those 00:11:41.160 --> 00:11:43.910 align:start position:0% what the real cost for those instructions<00:11:41.730> are<00:11:41.910> and<00:11:42.350> by<00:11:43.350> figuring<00:11:43.619> out<00:11:43.799> the 00:11:43.910 --> 00:11:43.920 align:start position:0% instructions are and by figuring out the 00:11:43.920 --> 00:11:47.059 align:start position:0% instructions are and by figuring out the real<00:11:44.040> cost<00:11:44.339> and<00:11:45.049> we<00:11:46.049> can<00:11:46.259> probably<00:11:46.529> avoid 00:11:47.059 --> 00:11:47.069 align:start position:0% real cost and we can probably avoid 00:11:47.069 --> 00:11:52.999 align:start position:0% real cost and we can probably avoid having<00:11:48.029> pecan<00:11:48.509> pies<00:11:50.959> it's<00:11:51.959> worse<00:11:52.290> than<00:11:52.319> 10<00:11:52.860> to 00:11:52.999 --> 00:11:53.009 align:start position:0% having pecan pies it's worse than 10 to 00:11:53.009 --> 00:11:56.809 align:start position:0% having pecan pies it's worse than 10 to 100<00:11:53.819> but<00:11:54.689> my<00:11:54.869> graph<00:11:55.199> was<00:11:55.529> scaled<00:11:55.920> by<00:11:56.279> square 00:11:56.809 --> 00:11:56.819 align:start position:0% 100 but my graph was scaled by square 00:11:56.819 --> 00:12:01.309 align:start position:0% 100 but my graph was scaled by square root<00:11:57.149> and<00:11:58.369> the<00:11:59.369> slowest<00:12:00.319> exponential 00:12:01.309 --> 00:12:01.319 align:start position:0% root and the slowest exponential 00:12:01.319 --> 00:12:04.789 align:start position:0% root and the slowest exponential operation<00:12:02.269> compared<00:12:03.269> to<00:12:03.449> the<00:12:03.569> fastest<00:12:04.290> native 00:12:04.789 --> 00:12:04.799 align:start position:0% operation compared to the fastest native 00:12:04.799 --> 00:12:10.850 align:start position:0% operation compared to the fastest native code<00:12:05.129> was<00:12:05.910> ten<00:12:06.209> thousand<00:12:06.779> to<00:12:06.959> one<00:12:09.679> but<00:12:10.679> that 00:12:10.850 --> 00:12:10.860 align:start position:0% code was ten thousand to one but that 00:12:10.860 --> 00:12:14.960 align:start position:0% code was ten thousand to one but that was<00:12:11.040> on<00:12:11.339> EVM<00:12:12.119> to<00:12:12.269> blossom<00:12:12.660> right<00:12:12.869> axe<00:12:13.790> it<00:12:14.790> was 00:12:14.960 --> 00:12:14.970 align:start position:0% was on EVM to blossom right axe it was 00:12:14.970 --> 00:12:18.679 align:start position:0% was on EVM to blossom right axe it was actually<00:12:15.509> go<00:12:15.779> versus<00:12:16.619> C++<00:12:17.459> compiled<00:12:18.299> straight 00:12:18.679 --> 00:12:18.689 align:start position:0% actually go versus C++ compiled straight 00:12:18.689 --> 00:12:25.479 align:start position:0% actually go versus C++ compiled straight to<00:12:18.839> assembly<00:12:22.220> so<00:12:23.600> another<00:12:24.600> advantage<00:12:24.989> of 00:12:25.479 --> 00:12:25.489 align:start position:0% to assembly so another advantage of 00:12:25.489 --> 00:12:30.639 align:start position:0% to assembly so another advantage of another<00:12:26.489> motivation<00:12:27.119> for<00:12:27.389> the<00:12:28.309> USM<00:12:29.309> proposal 00:12:30.639 --> 00:12:30.649 align:start position:0% another motivation for the USM proposal 00:12:30.649 --> 00:12:33.859 align:start position:0% another motivation for the USM proposal was<00:12:31.649> to<00:12:32.100> be<00:12:32.160> able<00:12:32.249> to<00:12:32.489> break<00:12:32.999> contracts<00:12:33.689> in 00:12:33.859 --> 00:12:33.869 align:start position:0% was to be able to break contracts in 00:12:33.869 --> 00:12:39.109 align:start position:0% was to be able to break contracts in other<00:12:34.290> languages<00:12:35.360> that<00:12:36.980> target<00:12:37.980> web<00:12:38.639> assembly 00:12:39.109 --> 00:12:39.119 align:start position:0% other languages that target web assembly 00:12:39.119 --> 00:12:42.949 align:start position:0% other languages that target web assembly as<00:12:39.269> a<00:12:40.019> as<00:12:40.410> a<00:12:40.470> compilation<00:12:40.860> target<00:12:41.489> versus<00:12:42.149> only 00:12:42.949 --> 00:12:42.959 align:start position:0% as a as a compilation target versus only 00:12:42.959 --> 00:12:51.139 align:start position:0% as a as a compilation target versus only targeting<00:12:43.769> EVM<00:12:44.419> so<00:12:46.759> we<00:12:47.759> have<00:12:47.999> the<00:12:48.360> the<00:12:49.819> EVM<00:12:50.819> - 00:12:51.139 --> 00:12:51.149 align:start position:0% targeting EVM so we have the the EVM - 00:12:51.149 --> 00:12:55.579 align:start position:0% targeting EVM so we have the the EVM - II<00:12:51.569> was<00:12:52.169> ohm<00:12:52.470> transpiler<00:12:53.399> as<00:12:53.610> a<00:12:53.790> prototype<00:12:54.589> we 00:12:55.579 --> 00:12:55.589 align:start position:0% II was ohm transpiler as a prototype we 00:12:55.589 --> 00:13:01.960 align:start position:0% II was ohm transpiler as a prototype we don't<00:12:55.860> yet<00:12:56.069> have<00:12:56.129> the<00:12:57.169> e<00:12:58.279> wasum<00:12:59.279> -<00:12:59.629> EVM 00:13:01.960 --> 00:13:01.970 align:start position:0% don't yet have the e wasum - EVM 00:13:01.970 --> 00:13:07.360 align:start position:0% don't yet have the e wasum - EVM transpiler<00:13:02.970> so<00:13:03.209> the<00:13:03.329> reverse<00:13:05.089> which<00:13:06.089> would 00:13:07.360 --> 00:13:07.370 align:start position:0% transpiler so the reverse which would 00:13:07.370 --> 00:13:11.980 align:start position:0% transpiler so the reverse which would make<00:13:08.029> the<00:13:08.630> evm<00:13:09.050> 1.5<00:13:09.890> proposal<00:13:10.779> equivalent<00:13:11.779> to 00:13:11.980 --> 00:13:11.990 align:start position:0% make the evm 1.5 proposal equivalent to 00:13:11.990 --> 00:13:17.560 align:start position:0% make the evm 1.5 proposal equivalent to almost<00:13:12.230> the<00:13:13.040> II<00:13:13.070> wasn't<00:13:13.370> proposal<00:13:14.890> just<00:13:16.570> then 00:13:17.560 --> 00:13:17.570 align:start position:0% almost the II wasn't proposal just then 00:13:17.570 --> 00:13:20.650 align:start position:0% almost the II wasn't proposal just then you<00:13:17.720> could<00:13:17.870> still<00:13:18.279> write<00:13:19.279> languages<00:13:19.940> write 00:13:20.650 --> 00:13:20.660 align:start position:0% you could still write languages write 00:13:20.660 --> 00:13:22.570 align:start position:0% you could still write languages write the<00:13:20.750> contracts<00:13:21.200> in<00:13:21.350> languages<00:13:21.890> that<00:13:21.950> target 00:13:22.570 --> 00:13:22.580 align:start position:0% the contracts in languages that target 00:13:22.580 --> 00:13:28.410 align:start position:0% the contracts in languages that target webassembly<00:13:23.050> transpile<00:13:24.050> those<00:13:24.290> two<00:13:24.529> EBM<00:13:25.100> 1.5 00:13:28.410 --> 00:13:28.420 align:start position:0% 00:13:28.420 --> 00:13:35.470 align:start position:0% have<00:13:29.420> asked<00:13:29.660> before<00:13:32.890> how<00:13:33.890> we<00:13:34.300> what<00:13:35.300> would<00:13:35.390> it 00:13:35.470 --> 00:13:35.480 align:start position:0% have asked before how we what would it 00:13:35.480 --> 00:13:41.170 align:start position:0% have asked before how we what would it take<00:13:35.630> to<00:13:35.690> write<00:13:36.050> the<00:13:36.550> EVM<00:13:39.130> the<00:13:40.130> II<00:13:40.460> was<00:13:40.790> him<00:13:41.000> to 00:13:41.170 --> 00:13:41.180 align:start position:0% take to write the EVM the II was him to 00:13:41.180 --> 00:13:45.490 align:start position:0% take to write the EVM the II was him to EVM<00:13:41.690> 1.5<00:13:42.370> transpiler<00:13:43.370> and<00:13:44.170> Gregg<00:13:45.170> said<00:13:45.410> it 00:13:45.490 --> 00:13:45.500 align:start position:0% EVM 1.5 transpiler and Gregg said it 00:13:45.500 --> 00:13:49.300 align:start position:0% EVM 1.5 transpiler and Gregg said it would<00:13:45.620> be<00:13:45.800> easy<00:13:45.910> Martin<00:13:46.910> said<00:13:47.089> good<00:13:47.300> luck<00:13:48.310> good 00:13:49.300 --> 00:13:49.310 align:start position:0% would be easy Martin said good luck good 00:13:49.310 --> 00:13:52.660 align:start position:0% would be easy Martin said good luck good luck<00:13:49.930> at<00:13:50.930> all<00:13:51.020> me<00:13:51.260> with<00:13:51.440> it's<00:13:52.220> not<00:13:52.400> impossible 00:13:52.660 --> 00:13:52.670 align:start position:0% luck at all me with it's not impossible 00:13:52.670 --> 00:13:54.400 align:start position:0% luck at all me with it's not impossible I<00:13:53.150> wouldn't<00:13:53.510> and<00:13:53.690> would<00:13:53.839> never<00:13:54.080> say<00:13:54.290> it's 00:13:54.400 --> 00:13:54.410 align:start position:0% I wouldn't and would never say it's 00:13:54.410 --> 00:14:01.420 align:start position:0% I wouldn't and would never say it's impossible<00:13:54.650> you<00:13:55.190> said<00:14:00.040> it's<00:14:01.040> gonna<00:14:01.190> be 00:14:01.420 --> 00:14:01.430 align:start position:0% impossible you said it's gonna be 00:14:01.430 --> 00:14:03.460 align:start position:0% impossible you said it's gonna be somewhere<00:14:01.760> it<00:14:01.940> was<00:14:02.000> a<00:14:02.089> fire<00:14:02.420> escape<00:14:02.870> in<00:14:03.050> Berlin 00:14:03.460 --> 00:14:03.470 align:start position:0% somewhere it was a fire escape in Berlin 00:14:03.470 --> 00:14:13.270 align:start position:0% somewhere it was a fire escape in Berlin I<00:14:03.830> mean<00:14:05.860> was<00:14:06.860> I<00:14:06.980> sober<00:14:10.150> and<00:14:11.150> also<00:14:12.100> one<00:14:13.100> of<00:14:13.130> the 00:14:13.270 --> 00:14:13.280 align:start position:0% I mean was I sober and also one of the 00:14:13.280 --> 00:14:17.320 align:start position:0% I mean was I sober and also one of the motivations<00:14:13.670> for<00:14:14.710> just<00:14:15.710> skipping<00:14:16.310> EVM<00:14:16.790> 1.5 00:14:17.320 --> 00:14:17.330 align:start position:0% motivations for just skipping EVM 1.5 00:14:17.330 --> 00:14:19.480 align:start position:0% motivations for just skipping EVM 1.5 and<00:14:17.630> just<00:14:17.870> and<00:14:18.140> because<00:14:18.950> the<00:14:19.160> original 00:14:19.480 --> 00:14:19.490 align:start position:0% and just and because the original 00:14:19.490 --> 00:14:21.910 align:start position:0% and just and because the original proposal<00:14:19.910> was<00:14:19.940> just<00:14:20.300> going<00:14:20.510> straight<00:14:20.630> to<00:14:21.200> 2.0 00:14:21.910 --> 00:14:21.920 align:start position:0% proposal was just going straight to 2.0 00:14:21.920 --> 00:14:25.030 align:start position:0% proposal was just going straight to 2.0 the<00:14:22.520> EVM<00:14:22.910> 1.5<00:14:23.360> proposal<00:14:23.720> came<00:14:23.870> later<00:14:24.110> and<00:14:24.410> one 00:14:25.030 --> 00:14:25.040 align:start position:0% the EVM 1.5 proposal came later and one 00:14:25.040 --> 00:14:27.460 align:start position:0% the EVM 1.5 proposal came later and one of<00:14:25.130> those<00:14:25.250> reasons<00:14:25.550> was<00:14:25.910> because<00:14:25.940> well<00:14:26.630> it 00:14:27.460 --> 00:14:27.470 align:start position:0% of those reasons was because well it 00:14:27.470 --> 00:14:31.840 align:start position:0% of those reasons was because well it must<00:14:27.680> be<00:14:27.740> hard<00:14:28.100> to<00:14:28.160> write<00:14:28.520> a<00:14:29.020> JIT<00:14:30.050> a<00:14:30.850> compiled 00:14:31.840 --> 00:14:31.850 align:start position:0% must be hard to write a JIT a compiled 00:14:31.850 --> 00:14:36.130 align:start position:0% must be hard to write a JIT a compiled VM<00:14:32.240> and<00:14:32.600> then<00:14:33.850> and<00:14:34.850> then<00:14:35.060> you<00:14:35.630> know<00:14:35.720> Powell 00:14:36.130 --> 00:14:36.140 align:start position:0% VM and then and then you know Powell 00:14:36.140 --> 00:14:42.840 align:start position:0% VM and then and then you know Powell wrote<00:14:36.589> a<00:14:36.650> prototype<00:14:37.100> of<00:14:37.130> a<00:14:37.990> PBM<00:14:39.460> JIT<00:14:40.460> vm<00:14:40.839> is 00:14:42.840 --> 00:14:42.850 align:start position:0% wrote a prototype of a PBM JIT vm is 00:14:42.850 --> 00:14:47.620 align:start position:0% wrote a prototype of a PBM JIT vm is what<00:14:43.850> was<00:14:44.060> that<00:14:44.240> easy<00:14:44.390> problem<00:14:46.240> so<00:14:47.240> actually 00:14:47.620 --> 00:14:47.630 align:start position:0% what was that easy problem so actually 00:14:47.630 --> 00:14:49.900 align:start position:0% what was that easy problem so actually the<00:14:47.750> prototype<00:14:48.410> of<00:14:48.589> that<00:14:48.800> it's<00:14:49.640> still<00:14:49.760> a 00:14:49.900 --> 00:14:49.910 align:start position:0% the prototype of that it's still a 00:14:49.910 --> 00:14:54.220 align:start position:0% the prototype of that it's still a prototype<00:14:50.380> it<00:14:51.380> was<00:14:51.440> it<00:14:51.980> was<00:14:52.390> it<00:14:53.390> was<00:14:53.630> done<00:14:53.900> even 00:14:54.220 --> 00:14:54.230 align:start position:0% prototype it was it was it was done even 00:14:54.230 --> 00:14:57.040 align:start position:0% prototype it was it was it was done even before<00:14:55.100> the<00:14:55.459> launch<00:14:55.640> of<00:14:55.850> a<00:14:56.030> material<00:14:56.750> it<00:14:56.900> was 00:14:57.040 --> 00:14:57.050 align:start position:0% before the launch of a material it was 00:14:57.050 --> 00:15:01.840 align:start position:0% before the launch of a material it was one<00:14:57.410> of<00:14:57.440> the<00:14:59.650> performance<00:15:00.650> benchmark<00:15:01.190> project 00:15:01.840 --> 00:15:01.850 align:start position:0% one of the performance benchmark project 00:15:01.850 --> 00:15:05.650 align:start position:0% one of the performance benchmark project that<00:15:02.060> we<00:15:02.390> want<00:15:02.570> to<00:15:03.670> have<00:15:04.670> to<00:15:04.970> actually<00:15:05.300> assess 00:15:05.650 --> 00:15:05.660 align:start position:0% that we want to have to actually assess 00:15:05.660 --> 00:15:07.660 align:start position:0% that we want to have to actually assess what<00:15:05.990> can<00:15:06.410> we<00:15:06.560> do<00:15:06.680> in<00:15:06.800> the<00:15:06.890> future<00:15:07.100> in<00:15:07.310> terms<00:15:07.459> of 00:15:07.660 --> 00:15:07.670 align:start position:0% what can we do in the future in terms of 00:15:07.670 --> 00:15:12.370 align:start position:0% what can we do in the future in terms of smart<00:15:08.390> contract<00:15:08.900> performance<00:15:10.330> but<00:15:11.330> yeah<00:15:12.110> it's 00:15:12.370 --> 00:15:12.380 align:start position:0% smart contract performance but yeah it's 00:15:12.380 --> 00:15:14.949 align:start position:0% smart contract performance but yeah it's it's<00:15:12.860> it<00:15:13.430> still<00:15:13.670> struggles<00:15:14.360> with<00:15:14.390> some<00:15:14.690> some 00:15:14.949 --> 00:15:14.959 align:start position:0% it's it still struggles with some some 00:15:14.959 --> 00:15:17.040 align:start position:0% it's it still struggles with some some cases<00:15:15.470> and 00:15:17.040 --> 00:15:17.050 align:start position:0% cases and 00:15:17.050 --> 00:15:19.810 align:start position:0% cases and as<00:15:18.050> I<00:15:18.230> said<00:15:18.440> we<00:15:18.620> can<00:15:18.770> do<00:15:19.010> much<00:15:19.190> better<00:15:19.220> in<00:15:19.670> this 00:15:19.810 --> 00:15:19.820 align:start position:0% as I said we can do much better in this 00:15:19.820 --> 00:15:24.460 align:start position:0% as I said we can do much better in this case<00:15:20.320> but<00:15:21.320> and<00:15:21.860> the<00:15:22.760> required<00:15:23.180> step<00:15:23.600> is<00:15:23.780> it's 00:15:24.460 --> 00:15:24.470 align:start position:0% case but and the required step is it's 00:15:24.470 --> 00:15:27.910 align:start position:0% case but and the required step is it's at<00:15:24.710> least<00:15:25.420> discount<00:15:26.420> referral<00:15:26.920> restrictions 00:15:27.910 --> 00:15:27.920 align:start position:0% at least discount referral restrictions 00:15:27.920 --> 00:15:31.480 align:start position:0% at least discount referral restrictions and<00:15:28.310> subroutine<00:15:29.000> support<00:15:30.160> directly<00:15:31.160> in<00:15:31.220> the 00:15:31.480 --> 00:15:31.490 align:start position:0% and subroutine support directly in the 00:15:31.490 --> 00:15:36.250 align:start position:0% and subroutine support directly in the in<00:15:31.760> the<00:15:32.000> EVM<00:15:32.690> byte<00:15:32.930> code<00:15:34.780> that<00:15:35.780> would<00:15:36.020> allow 00:15:36.250 --> 00:15:36.260 align:start position:0% in the EVM byte code that would allow 00:15:36.260 --> 00:15:40.300 align:start position:0% in the EVM byte code that would allow even<00:15:37.100> more<00:15:37.270> optimizations<00:15:38.270> and<00:15:39.070> on<00:15:40.070> the<00:15:40.190> other 00:15:40.300 --> 00:15:40.310 align:start position:0% even more optimizations and on the other 00:15:40.310 --> 00:15:43.950 align:start position:0% even more optimizations and on the other hand<00:15:40.670> like<00:15:41.210> JIT<00:15:41.720> compilers<00:15:42.230> are<00:15:42.350> hard<00:15:42.620> I<00:15:42.920> mean 00:15:43.950 --> 00:15:43.960 align:start position:0% hand like JIT compilers are hard I mean 00:15:43.960 --> 00:15:47.500 align:start position:0% hand like JIT compilers are hard I mean the<00:15:44.960> the<00:15:45.920> network<00:15:46.070> consensus<00:15:46.880> depend<00:15:47.240> on<00:15:47.360> that 00:15:47.500 --> 00:15:47.510 align:start position:0% the the network consensus depend on that 00:15:47.510 --> 00:15:53.770 align:start position:0% the the network consensus depend on that and<00:15:48.940> like<00:15:49.940> the<00:15:50.150> risk<00:15:50.360> is<00:15:50.660> like<00:15:51.190> we<00:15:52.190> might<00:15:52.780> might 00:15:53.770 --> 00:15:53.780 align:start position:0% and like the risk is like we might might 00:15:53.780 --> 00:15:56.290 align:start position:0% and like the risk is like we might might get<00:15:54.080> hard<00:15:54.380> or<00:15:54.620> it<00:15:55.220> might<00:15:55.460> be<00:15:55.490> never<00:15:55.790> finished 00:15:56.290 --> 00:15:56.300 align:start position:0% get hard or it might be never finished 00:15:56.300 --> 00:16:00.120 align:start position:0% get hard or it might be never finished in<00:15:56.510> terms<00:15:56.720> of<00:15:57.460> removing<00:15:58.460> bugs<00:15:58.700> and<00:15:59.120> finding 00:16:00.120 --> 00:16:00.130 align:start position:0% in terms of removing bugs and finding 00:16:00.130 --> 00:16:04.000 align:start position:0% in terms of removing bugs and finding educators<00:16:01.720> because<00:16:02.720> that's<00:16:03.260> that's<00:16:03.530> much 00:16:04.000 --> 00:16:04.010 align:start position:0% educators because that's that's much 00:16:04.010 --> 00:16:08.400 align:start position:0% educators because that's that's much more<00:16:04.310> complex<00:16:05.350> construct<00:16:06.880> comparing<00:16:07.880> to 00:16:08.400 --> 00:16:08.410 align:start position:0% more complex construct comparing to 00:16:08.410 --> 00:16:13.000 align:start position:0% more complex construct comparing to interpreter<00:16:09.410> I<00:16:10.750> mean<00:16:11.750> another<00:16:12.170> problem<00:16:12.890> with 00:16:13.000 --> 00:16:13.010 align:start position:0% interpreter I mean another problem with 00:16:13.010 --> 00:16:15.730 align:start position:0% interpreter I mean another problem with with<00:16:13.160> just-in-time<00:16:13.520> compilers<00:16:14.030> is<00:16:14.180> that<00:16:14.740> I'm 00:16:15.730 --> 00:16:15.740 align:start position:0% with just-in-time compilers is that I'm 00:16:15.740 --> 00:16:17.260 align:start position:0% with just-in-time compilers is that I'm not<00:16:15.890> sure<00:16:15.950> if<00:16:16.190> there<00:16:16.550> is<00:16:16.820> a<00:16:16.850> just-in-time 00:16:17.260 --> 00:16:17.270 align:start position:0% not sure if there is a just-in-time 00:16:17.270 --> 00:16:19.750 align:start position:0% not sure if there is a just-in-time compiler<00:16:17.720> that<00:16:17.810> provides<00:16:18.380> a<00:16:18.680> fixed<00:16:19.430> upper 00:16:19.750 --> 00:16:19.760 align:start position:0% compiler that provides a fixed upper 00:16:19.760 --> 00:16:22.330 align:start position:0% compiler that provides a fixed upper bound<00:16:20.350> in<00:16:21.350> terms<00:16:21.530> of<00:16:21.710> resource<00:16:21.980> consumption 00:16:22.330 --> 00:16:22.340 align:start position:0% bound in terms of resource consumption 00:16:22.340 --> 00:16:24.730 align:start position:0% bound in terms of resource consumption and<00:16:22.640> this<00:16:22.760> is<00:16:22.910> a<00:16:22.940> very<00:16:23.900> important<00:16:24.350> guarantee 00:16:24.730 --> 00:16:24.740 align:start position:0% and this is a very important guarantee 00:16:24.740 --> 00:16:27.940 align:start position:0% and this is a very important guarantee that<00:16:25.130> we<00:16:25.460> need<00:16:25.730> in<00:16:26.300> order<00:16:26.480> to<00:16:26.660> do<00:16:26.900> to<00:16:27.680> do<00:16:27.800> the 00:16:27.940 --> 00:16:27.950 align:start position:0% that we need in order to do to do the 00:16:27.950 --> 00:16:29.740 align:start position:0% that we need in order to do to do the the<00:16:28.130> gas<00:16:28.370> calculations<00:16:28.910> properly<00:16:29.300> right<00:16:29.720> I 00:16:29.740 --> 00:16:29.750 align:start position:0% the gas calculations properly right I 00:16:29.750 --> 00:16:32.800 align:start position:0% the gas calculations properly right I mean<00:16:30.020> usually<00:16:31.090> just-in-time<00:16:32.090> compilers 00:16:32.800 --> 00:16:32.810 align:start position:0% mean usually just-in-time compilers 00:16:32.810 --> 00:16:35.410 align:start position:0% mean usually just-in-time compilers generate<00:16:33.440> code<00:16:33.680> that<00:16:33.950> is<00:16:34.340> faster<00:16:35.090> and<00:16:35.240> takes 00:16:35.410 --> 00:16:35.420 align:start position:0% generate code that is faster and takes 00:16:35.420 --> 00:16:37.420 align:start position:0% generate code that is faster and takes less<00:16:35.600> resources<00:16:36.020> but<00:16:36.290> we<00:16:36.920> don't<00:16:37.280> have<00:16:37.400> a 00:16:37.420 --> 00:16:37.430 align:start position:0% less resources but we don't have a 00:16:37.430 --> 00:16:39.760 align:start position:0% less resources but we don't have a guarantee<00:16:37.640> or<00:16:38.030> do<00:16:38.150> we<00:16:38.300> well<00:16:38.990> as<00:16:39.110> I<00:16:39.290> said<00:16:39.350> we 00:16:39.760 --> 00:16:39.770 align:start position:0% guarantee or do we well as I said we 00:16:39.770 --> 00:16:43.690 align:start position:0% guarantee or do we well as I said we can't<00:16:40.100> do<00:16:40.370> a<00:16:40.400> JIT<00:16:40.760> it's<00:16:41.120> it's<00:16:41.690> exploitable<00:16:42.700> we 00:16:43.690 --> 00:16:43.700 align:start position:0% can't do a JIT it's it's exploitable we 00:16:43.700 --> 00:16:45.520 align:start position:0% can't do a JIT it's it's exploitable we have<00:16:43.880> to<00:16:44.060> it<00:16:44.330> has<00:16:44.360> to<00:16:44.660> be<00:16:44.780> a<00:16:44.810> compiler<00:16:45.500> that 00:16:45.520 --> 00:16:45.530 align:start position:0% have to it has to be a compiler that 00:16:45.530 --> 00:16:49.500 align:start position:0% have to it has to be a compiler that runs<00:16:46.150> at<00:16:47.150> deployment<00:16:47.630> time<00:16:47.960> not<00:16:48.500> at<00:16:48.650> run<00:16:48.860> time 00:16:49.500 --> 00:16:49.510 align:start position:0% runs at deployment time not at run time 00:16:49.510 --> 00:16:52.920 align:start position:0% runs at deployment time not at run time which<00:16:50.510> means<00:16:51.500> it<00:16:51.710> can<00:16:51.830> be<00:16:51.860> a<00:16:52.010> full<00:16:52.340> compiler 00:16:52.920 --> 00:16:52.930 align:start position:0% which means it can be a full compiler 00:16:52.930 --> 00:16:55.780 align:start position:0% which means it can be a full compiler depending<00:16:53.930> on<00:16:53.990> how<00:16:54.170> long<00:16:54.440> we<00:16:54.500> want<00:16:54.920> to<00:16:55.010> take<00:16:55.250> to 00:16:55.780 --> 00:16:55.790 align:start position:0% depending on how long we want to take to 00:16:55.790 --> 00:16:58.770 align:start position:0% depending on how long we want to take to load<00:16:55.940> a<00:16:55.970> block<00:16:56.380> then<00:16:57.380> my<00:16:57.590> understanding<00:16:58.340> is 00:16:58.770 --> 00:16:58.780 align:start position:0% load a block then my understanding is 00:16:58.780 --> 00:17:01.330 align:start position:0% load a block then my understanding is storage<00:16:59.780> is<00:17:00.020> the<00:17:00.200> main<00:17:00.380> constraint<00:17:01.010> there 00:17:01.330 --> 00:17:01.340 align:start position:0% storage is the main constraint there 00:17:01.340 --> 00:17:08.170 align:start position:0% storage is the main constraint there anyway<00:17:03.880> but<00:17:04.930> me<00:17:05.930> I<00:17:05.960> remember<00:17:06.710> in<00:17:06.890> my<00:17:07.100> testing<00:17:07.730> I 00:17:08.170 --> 00:17:08.180 align:start position:0% anyway but me I remember in my testing I 00:17:08.180 --> 00:17:10.660 align:start position:0% anyway but me I remember in my testing I came<00:17:08.600> up<00:17:08.810> with<00:17:08.840> one<00:17:09.290> performance<00:17:09.980> bottleneck 00:17:10.660 --> 00:17:10.670 align:start position:0% came up with one performance bottleneck 00:17:10.670 --> 00:17:13.930 align:start position:0% came up with one performance bottleneck and<00:17:11.300> you<00:17:11.930> said<00:17:12.260> it's<00:17:12.620> not<00:17:12.800> a<00:17:12.860> priority<00:17:13.190> I<00:17:13.610> don't 00:17:13.930 --> 00:17:13.940 align:start position:0% and you said it's not a priority I don't 00:17:13.940 --> 00:17:17.440 align:start position:0% and you said it's not a priority I don't think<00:17:14.150> I<00:17:14.270> can<00:17:14.450> get<00:17:14.660> to<00:17:14.900> it<00:17:15.110> and<00:17:15.380> the<00:17:16.220> next<00:17:16.550> day 00:17:17.440 --> 00:17:17.450 align:start position:0% think I can get to it and the next day 00:17:17.450 --> 00:17:21.360 align:start position:0% think I can get to it and the next day you<00:17:17.570> had<00:17:17.750> it<00:17:17.870> fixed<00:17:19.570> yeah<00:17:20.570> this<00:17:20.750> is<00:17:20.900> a<00:17:20.930> bit 00:17:21.360 --> 00:17:21.370 align:start position:0% you had it fixed yeah this is a bit 00:17:21.370 --> 00:17:26.290 align:start position:0% you had it fixed yeah this is a bit different<00:17:22.370> issues<00:17:22.880> of<00:17:24.910> immaterial<00:17:25.910> weak 00:17:26.290 --> 00:17:26.300 align:start position:0% different issues of immaterial weak 00:17:26.300 --> 00:17:28.810 align:start position:0% different issues of immaterial weak actually<00:17:26.720> care<00:17:27.410> about<00:17:27.530> the<00:17:27.950> worst<00:17:28.190> worst 00:17:28.810 --> 00:17:28.820 align:start position:0% actually care about the worst worst 00:17:28.820 --> 00:17:32.890 align:start position:0% actually care about the worst worst cases<00:17:29.350> because<00:17:30.350> this<00:17:30.590> is<00:17:30.770> what<00:17:31.010> what<00:17:31.630> the<00:17:32.630> cost 00:17:32.890 --> 00:17:32.900 align:start position:0% cases because this is what what the cost 00:17:32.900 --> 00:17:39.460 align:start position:0% cases because this is what what the cost must<00:17:33.170> be<00:17:33.350> for<00:17:33.800> and<00:17:34.160> and<00:17:36.220> so<00:17:37.220> this<00:17:37.550> affects<00:17:38.470> more 00:17:39.460 --> 00:17:39.470 align:start position:0% must be for and and so this affects more 00:17:39.470 --> 00:17:43.150 align:start position:0% must be for and and so this affects more complex<00:17:40.450> optimizations<00:17:41.450> but<00:17:42.170> also<00:17:42.380> the<00:17:42.770> big 00:17:43.150 --> 00:17:43.160 align:start position:0% complex optimizations but also the big 00:17:43.160 --> 00:17:45.850 align:start position:0% complex optimizations but also the big big<00:17:43.580> integer<00:17:43.970> libraries<00:17:44.840> that<00:17:45.140> actually<00:17:45.650> try 00:17:45.850 --> 00:17:45.860 align:start position:0% big integer libraries that actually try 00:17:45.860 --> 00:17:50.320 align:start position:0% big integer libraries that actually try to<00:17:45.890> squeeze<00:17:46.490> the<00:17:46.760> easy<00:17:47.090> cases<00:17:47.510> first<00:17:49.060> but<00:17:50.060> this 00:17:50.320 --> 00:17:50.330 align:start position:0% to squeeze the easy cases first but this 00:17:50.330 --> 00:17:53.920 align:start position:0% to squeeze the easy cases first but this is<00:17:50.510> not<00:17:50.690> what<00:17:50.980> what<00:17:51.980> we<00:17:52.160> point<00:17:52.460> to<00:17:52.550> like<00:17:53.390> we 00:17:53.920 --> 00:17:53.930 align:start position:0% is not what what we point to like we 00:17:53.930 --> 00:17:56.830 align:start position:0% is not what what we point to like we don't<00:17:54.050> care<00:17:54.170> if<00:17:54.500> we<00:17:54.650> can<00:17:54.970> divide<00:17:55.970> quickly<00:17:56.600> for 00:17:56.830 --> 00:17:56.840 align:start position:0% don't care if we can divide quickly for 00:17:56.840 --> 00:17:59.470 align:start position:0% don't care if we can divide quickly for small<00:17:57.170> numbers<00:17:57.560> because<00:17:58.190> what<00:17:58.460> weaker<00:17:58.850> is<00:17:59.060> to 00:17:59.470 --> 00:17:59.480 align:start position:0% small numbers because what weaker is to 00:17:59.480 --> 00:18:05.710 align:start position:0% small numbers because what weaker is to have<00:17:59.870> the<00:18:00.770> worst<00:18:00.950> case<00:18:01.660> covered<00:18:03.760> so<00:18:04.760> yeah<00:18:05.420> that 00:18:05.710 --> 00:18:05.720 align:start position:0% have the worst case covered so yeah that 00:18:05.720 --> 00:18:08.350 align:start position:0% have the worst case covered so yeah that would<00:18:05.900> be<00:18:06.080> much<00:18:06.260> more<00:18:06.610> much<00:18:07.610> more<00:18:07.850> difficult 00:18:08.350 --> 00:18:08.360 align:start position:0% would be much more much more difficult 00:18:08.360 --> 00:18:10.990 align:start position:0% would be much more much more difficult to<00:18:08.480> control<00:18:08.510> that<00:18:09.080> within<00:18:09.380> the<00:18:10.160> drift<00:18:10.460> because 00:18:10.990 --> 00:18:11.000 align:start position:0% to control that within the drift because 00:18:11.000 --> 00:18:13.840 align:start position:0% to control that within the drift because it's<00:18:11.690> like<00:18:11.990> you<00:18:12.230> have<00:18:12.440> the<00:18:12.650> big<00:18:12.890> at<00:18:13.460> least<00:18:13.520> in 00:18:13.840 --> 00:18:13.850 align:start position:0% it's like you have the big at least in 00:18:13.850 --> 00:18:16.120 align:start position:0% it's like you have the big at least in the<00:18:14.000> in<00:18:14.240> the<00:18:14.420> in<00:18:14.630> the<00:18:14.810> in<00:18:15.080> the<00:18:15.200> in<00:18:15.470> the<00:18:15.620> EVM<00:18:15.920> rate 00:18:16.120 --> 00:18:16.130 align:start position:0% the in the in the in the in the EVM rate 00:18:16.130 --> 00:18:19.440 align:start position:0% the in the in the in the in the EVM rate that<00:18:16.340> depends<00:18:16.850> on<00:18:16.970> LLVM<00:18:17.600> you<00:18:17.870> have<00:18:18.200> a<00:18:18.350> big 00:18:19.440 --> 00:18:19.450 align:start position:0% that depends on LLVM you have a big 00:18:19.450 --> 00:18:22.030 align:start position:0% that depends on LLVM you have a big bucket<00:18:20.450> library<00:18:20.960> that<00:18:21.140> does<00:18:21.590> that<00:18:21.770> for<00:18:21.950> you 00:18:22.030 --> 00:18:22.040 align:start position:0% bucket library that does that for you 00:18:22.040 --> 00:18:23.950 align:start position:0% bucket library that does that for you and<00:18:22.280> it's<00:18:22.610> really<00:18:22.880> hard<00:18:23.120> to<00:18:23.270> tell<00:18:23.450> what<00:18:23.720> it's 00:18:23.950 --> 00:18:23.960 align:start position:0% and it's really hard to tell what it's 00:18:23.960 --> 00:18:28.270 align:start position:0% and it's really hard to tell what it's actually<00:18:24.110> doing<00:18:25.420> but<00:18:26.420> yeah<00:18:26.960> I<00:18:27.290> guess<00:18:27.800> they<00:18:28.010> are 00:18:28.270 --> 00:18:28.280 align:start position:0% actually doing but yeah I guess they are 00:18:28.280 --> 00:18:30.880 align:start position:0% actually doing but yeah I guess they are different<00:18:28.790> approaches<00:18:29.480> to<00:18:29.510> that<00:18:29.810> and<00:18:30.200> for 00:18:30.880 --> 00:18:30.890 align:start position:0% different approaches to that and for 00:18:30.890 --> 00:18:34.120 align:start position:0% different approaches to that and for example<00:18:31.400> it<00:18:32.030> was<00:18:32.210> and<00:18:32.540> has<00:18:32.780> some<00:18:33.470> JIT 00:18:34.120 --> 00:18:34.130 align:start position:0% example it was and has some JIT 00:18:34.130 --> 00:18:43.150 align:start position:0% example it was and has some JIT prototypes<00:18:34.790> that<00:18:35.000> are<00:18:35.450> not<00:18:35.810> depending<00:18:36.410> on<00:18:42.160> of 00:18:43.150 --> 00:18:43.160 align:start position:0% prototypes that are not depending on of 00:18:43.160 --> 00:18:45.700 align:start position:0% prototypes that are not depending on of course<00:18:43.490> one<00:18:44.030> of<00:18:44.060> my<00:18:44.180> bigger<00:18:44.570> concerns<00:18:45.170> is<00:18:45.470> not 00:18:45.700 --> 00:18:45.710 align:start position:0% course one of my bigger concerns is not 00:18:45.710 --> 00:18:48.970 align:start position:0% course one of my bigger concerns is not technical<00:18:46.430> theater<00:18:46.940> of<00:18:47.060> these<00:18:47.710> either<00:18:48.710> of 00:18:48.970 --> 00:18:48.980 align:start position:0% technical theater of these either of 00:18:48.980 --> 00:18:51.160 align:start position:0% technical theater of these either of these<00:18:49.070> programs<00:18:49.670> technically<00:18:50.450> does<00:18:50.690> the<00:18:50.930> job 00:18:51.160 --> 00:18:51.170 align:start position:0% these programs technically does the job 00:18:51.170 --> 00:18:55.420 align:start position:0% these programs technically does the job I'm<00:18:52.010> much<00:18:52.880> more<00:18:53.210> concerned<00:18:53.480> about<00:18:54.430> who 00:18:55.420 --> 00:18:55.430 align:start position:0% I'm much more concerned about who 00:18:55.430 --> 00:18:59.410 align:start position:0% I'm much more concerned about who controls<00:18:55.820> to<00:18:56.230> specification<00:18:57.230> and<00:18:58.040> I<00:18:58.420> really 00:18:59.410 --> 00:18:59.420 align:start position:0% controls to specification and I really 00:18:59.420 --> 00:19:03.550 align:start position:0% controls to specification and I really believe<00:19:00.400> the<00:19:01.400> the<00:19:02.180> etherium<00:19:02.840> community 00:19:03.550 --> 00:19:03.560 align:start position:0% believe the the etherium community 00:19:03.560 --> 00:19:05.410 align:start position:0% believe the the etherium community should<00:19:03.980> completely<00:19:04.460> control<00:19:05.150> that 00:19:05.410 --> 00:19:05.420 align:start position:0% should completely control that 00:19:05.420 --> 00:19:08.500 align:start position:0% should completely control that specification<00:19:06.100> that<00:19:07.100> the<00:19:07.340> web<00:19:07.520> browser<00:19:07.550> space 00:19:08.500 --> 00:19:08.510 align:start position:0% specification that the web browser space 00:19:08.510 --> 00:19:11.650 align:start position:0% specification that the web browser space is<00:19:09.320> not<00:19:09.620> the<00:19:09.890> etherium<00:19:10.460> space<00:19:10.880> and<00:19:11.390> i<00:19:11.450> would 00:19:11.650 --> 00:19:11.660 align:start position:0% is not the etherium space and i would 00:19:11.660 --> 00:19:13.360 align:start position:0% is not the etherium space and i would not<00:19:11.840> want<00:19:12.080> to<00:19:12.200> get<00:19:12.380> wet 00:19:13.360 --> 00:19:13.370 align:start position:0% not want to get wet 00:19:13.370 --> 00:19:18.400 align:start position:0% not want to get wet with<00:19:14.180> the<00:19:15.670> with<00:19:16.670> the<00:19:16.820> wasm<00:19:17.300> group<00:19:17.690> moving<00:19:18.260> in 00:19:18.400 --> 00:19:18.410 align:start position:0% with the with the wasm group moving in 00:19:18.410 --> 00:19:21.940 align:start position:0% with the with the wasm group moving in the<00:19:18.500> direction<00:19:18.920> they<00:19:19.460> need<00:19:19.490> to<00:19:19.730> move<00:19:20.740> and<00:19:21.740> us 00:19:21.940 --> 00:19:21.950 align:start position:0% the direction they need to move and us 00:19:21.950 --> 00:19:24.850 align:start position:0% the direction they need to move and us shaking<00:19:22.460> our<00:19:22.640> heads<00:19:22.850> and<00:19:23.210> going<00:19:23.600> no<00:19:23.840> we<00:19:24.590> don't 00:19:24.850 --> 00:19:24.860 align:start position:0% shaking our heads and going no we don't 00:19:24.860 --> 00:19:27.370 align:start position:0% shaking our heads and going no we don't want<00:19:25.130> to<00:19:25.220> go<00:19:25.340> in<00:19:25.520> that<00:19:25.640> direction<00:19:26.350> yeah<00:19:27.350> I 00:19:27.370 --> 00:19:27.380 align:start position:0% want to go in that direction yeah I 00:19:27.380 --> 00:19:31.690 align:start position:0% want to go in that direction yeah I disagree<00:19:28.280> with<00:19:28.310> that<00:19:28.430> because<00:19:29.330> I<00:19:29.960> think<00:19:30.500> I<00:19:31.160> a 00:19:31.690 --> 00:19:31.700 align:start position:0% disagree with that because I think I a 00:19:31.700 --> 00:19:34.840 align:start position:0% disagree with that because I think I a much<00:19:32.090> rather<00:19:32.770> it's<00:19:33.770> much<00:19:33.980> more<00:19:34.190> pluralistic 00:19:34.840 --> 00:19:34.850 align:start position:0% much rather it's much more pluralistic 00:19:34.850 --> 00:19:40.480 align:start position:0% much rather it's much more pluralistic to<00:19:35.420> go<00:19:35.600> with<00:19:36.350> a<00:19:37.130> larger<00:19:38.090> community<00:19:38.860> a<00:19:39.860> larger 00:19:40.480 --> 00:19:40.490 align:start position:0% to go with a larger community a larger 00:19:40.490 --> 00:19:43.270 align:start position:0% to go with a larger community a larger body<00:19:40.820> of<00:19:41.000> people<00:19:41.500> standardizing<00:19:42.500> and<00:19:42.800> coming 00:19:43.270 --> 00:19:43.280 align:start position:0% body of people standardizing and coming 00:19:43.280 --> 00:19:46.560 align:start position:0% body of people standardizing and coming to<00:19:43.370> consensus<00:19:44.000> on<00:19:44.180> a<00:19:45.130> virtual<00:19:46.130> machine 00:19:46.560 --> 00:19:46.570 align:start position:0% to consensus on a virtual machine 00:19:46.570 --> 00:19:49.000 align:start position:0% to consensus on a virtual machine instead<00:19:47.570> of<00:19:47.690> just<00:19:47.900> using<00:19:48.080> a<00:19:48.320> virtual<00:19:48.530> machine 00:19:49.000 --> 00:19:49.010 align:start position:0% instead of just using a virtual machine 00:19:49.010 --> 00:19:51.640 align:start position:0% instead of just using a virtual machine that<00:19:49.040> can<00:19:49.280> only<00:19:49.430> be<00:19:49.690> was<00:19:50.690> created<00:19:51.080> to<00:19:51.230> only<00:19:51.410> be 00:19:51.640 --> 00:19:51.650 align:start position:0% that can only be was created to only be 00:19:51.650 --> 00:19:55.390 align:start position:0% that can only be was created to only be used<00:19:52.460> in<00:19:52.880> one<00:19:53.060> Pacific<00:19:53.540> use<00:19:53.750> case<00:19:54.050> and<00:19:54.380> if<00:19:55.280> you 00:19:55.390 --> 00:19:55.400 align:start position:0% used in one Pacific use case and if you 00:19:55.400 --> 00:19:57.400 align:start position:0% used in one Pacific use case and if you look<00:19:55.610> at<00:19:55.730> the<00:19:55.820> browser<00:19:56.030> use<00:19:56.420> case<00:19:56.720> is<00:19:57.020> very 00:19:57.400 --> 00:19:57.410 align:start position:0% look at the browser use case is very 00:19:57.410 --> 00:20:01.630 align:start position:0% look at the browser use case is very similar<00:19:57.770> to<00:19:58.100> the<00:19:58.580> blockchain<00:19:58.790> use<00:19:59.330> case<00:20:00.640> we 00:20:01.630 --> 00:20:01.640 align:start position:0% similar to the blockchain use case we 00:20:01.640 --> 00:20:06.450 align:start position:0% similar to the blockchain use case we need<00:20:01.820> secure<00:20:02.470> portable<00:20:04.270> and<00:20:05.270> size<00:20:05.630> efficient 00:20:06.450 --> 00:20:06.460 align:start position:0% need secure portable and size efficient 00:20:06.460 --> 00:20:10.180 align:start position:0% need secure portable and size efficient byte<00:20:07.460> code<00:20:07.670> right<00:20:08.450> exact<00:20:09.350> same<00:20:09.560> concern<00:20:10.010> we 00:20:10.180 --> 00:20:10.190 align:start position:0% byte code right exact same concern we 00:20:10.190 --> 00:20:13.450 align:start position:0% byte code right exact same concern we have<00:20:10.370> in<00:20:10.490> the<00:20:10.550> blockchain<00:20:10.760> space<00:20:11.390> I<00:20:12.310> agree<00:20:13.310> and 00:20:13.450 --> 00:20:13.460 align:start position:0% have in the blockchain space I agree and 00:20:13.460 --> 00:20:17.610 align:start position:0% have in the blockchain space I agree and and<00:20:14.120> furthermore<00:20:14.600> like<00:20:15.250> it's<00:20:16.250> an<00:20:16.490> open<00:20:16.940> it's<00:20:17.270> a 00:20:17.610 --> 00:20:17.620 align:start position:0% and furthermore like it's an open it's a 00:20:17.620 --> 00:20:20.350 align:start position:0% and furthermore like it's an open it's a it's<00:20:18.620> open<00:20:18.890> to<00:20:19.010> participation<00:20:19.550> you<00:20:19.970> can<00:20:20.000> go<00:20:20.300> to 00:20:20.350 --> 00:20:20.360 align:start position:0% it's open to participation you can go to 00:20:20.360 --> 00:20:23.110 align:start position:0% it's open to participation you can go to the<00:20:20.660> web<00:20:20.810> assembly<00:20:21.520> community<00:20:22.520> meetings<00:20:22.910> you 00:20:23.110 --> 00:20:23.120 align:start position:0% the web assembly community meetings you 00:20:23.120 --> 00:20:27.490 align:start position:0% the web assembly community meetings you can<00:20:24.010> voice<00:20:25.010> your<00:20:25.280> opinions<00:20:25.760> you<00:20:26.060> can<00:20:26.500> submit 00:20:27.490 --> 00:20:27.500 align:start position:0% can voice your opinions you can submit 00:20:27.500 --> 00:20:31.150 align:start position:0% can voice your opinions you can submit proposals<00:20:27.770> on<00:20:28.460> github<00:20:29.230> it's<00:20:30.230> very<00:20:30.560> open<00:20:30.950> and 00:20:31.150 --> 00:20:31.160 align:start position:0% proposals on github it's very open and 00:20:31.160 --> 00:20:33.490 align:start position:0% proposals on github it's very open and in<00:20:31.310> you<00:20:31.790> know<00:20:31.910> it's<00:20:32.120> easy<00:20:32.270> it's<00:20:32.810> easy<00:20:32.960> to<00:20:33.380> get 00:20:33.490 --> 00:20:33.500 align:start position:0% in you know it's easy it's easy to get 00:20:33.500 --> 00:20:37.870 align:start position:0% in you know it's easy it's easy to get involved<00:20:35.470> that<00:20:36.470> and<00:20:36.800> within<00:20:37.490> the<00:20:37.640> blockchain 00:20:37.870 --> 00:20:37.880 align:start position:0% involved that and within the blockchain 00:20:37.880 --> 00:20:40.420 align:start position:0% involved that and within the blockchain space<00:20:38.660> I<00:20:38.870> know<00:20:39.020> of<00:20:39.350> least<00:20:39.620> three<00:20:40.040> other 00:20:40.420 --> 00:20:40.430 align:start position:0% space I know of least three other 00:20:40.430 --> 00:20:42.910 align:start position:0% space I know of least three other blockchain<00:20:41.090> projects<00:20:41.690> outside<00:20:42.170> of<00:20:42.320> aetherium 00:20:42.910 --> 00:20:42.920 align:start position:0% blockchain projects outside of aetherium 00:20:42.920 --> 00:20:45.420 align:start position:0% blockchain projects outside of aetherium that<00:20:43.580> are<00:20:43.790> already<00:20:44.080> prototyping<00:20:45.080> and 00:20:45.420 --> 00:20:45.430 align:start position:0% that are already prototyping and 00:20:45.430 --> 00:20:51.790 align:start position:0% that are already prototyping and actively<00:20:46.430> have<00:20:47.980> wasum<00:20:48.980> running<00:20:49.720> in<00:20:50.720> in<00:20:51.590> their 00:20:51.790 --> 00:20:51.800 align:start position:0% actively have wasum running in in their 00:20:51.800 --> 00:20:54.340 align:start position:0% actively have wasum running in in their systems<00:20:52.250> so<00:20:52.610> we're<00:20:53.570> seeing<00:20:53.780> a<00:20:54.020> lot<00:20:54.320> of 00:20:54.340 --> 00:20:54.350 align:start position:0% systems so we're seeing a lot of 00:20:54.350 --> 00:20:58.660 align:start position:0% systems so we're seeing a lot of momentum<00:20:54.800> I<00:20:55.160> think<00:20:55.400> pick<00:20:55.640> up<00:20:55.820> around<00:20:56.150> it<00:20:57.190> in<00:20:58.190> I 00:20:58.660 --> 00:20:58.670 align:start position:0% momentum I think pick up around it in I 00:20:58.670 --> 00:21:01.060 align:start position:0% momentum I think pick up around it in I think<00:20:58.880> that's<00:20:59.180> sort<00:20:59.300> of<00:20:59.420> just<00:20:59.890> going<00:21:00.890> to<00:21:01.010> be 00:21:01.060 --> 00:21:01.070 align:start position:0% think that's sort of just going to be 00:21:01.070 --> 00:21:02.590 align:start position:0% think that's sort of just going to be the<00:21:01.190> way<00:21:01.280> it<00:21:01.400> is<00:21:01.430> because<00:21:01.820> it's<00:21:01.970> like<00:21:02.150> once 00:21:02.590 --> 00:21:02.600 align:start position:0% the way it is because it's like once 00:21:02.600 --> 00:21:06.550 align:start position:0% the way it is because it's like once there<00:21:03.230> is<00:21:04.180> the<00:21:05.180> we<00:21:05.450> start<00:21:05.720> to<00:21:05.810> have<00:21:05.930> consensus 00:21:06.550 --> 00:21:06.560 align:start position:0% there is the we start to have consensus 00:21:06.560 --> 00:21:09.310 align:start position:0% there is the we start to have consensus around<00:21:06.710> VM<00:21:07.310> everyone<00:21:08.090> is<00:21:08.180> gonna<00:21:09.020> be<00:21:09.110> the 00:21:09.310 --> 00:21:09.320 align:start position:0% around VM everyone is gonna be the 00:21:09.320 --> 00:21:10.780 align:start position:0% around VM everyone is gonna be the obvious<00:21:09.410> choice<00:21:09.650> everyone's<00:21:10.340> going<00:21:10.520> to<00:21:10.580> use 00:21:10.780 --> 00:21:10.790 align:start position:0% obvious choice everyone's going to use 00:21:10.790 --> 00:21:11.890 align:start position:0% obvious choice everyone's going to use it<00:21:11.000> and<00:21:11.150> it's<00:21:11.270> going<00:21:11.360> to<00:21:11.450> be<00:21:11.570> a<00:21:11.600> recursive 00:21:11.890 --> 00:21:11.900 align:start position:0% it and it's going to be a recursive 00:21:11.900 --> 00:21:13.180 align:start position:0% it and it's going to be a recursive feedback<00:21:12.380> loop<00:21:12.560> right<00:21:12.710> it's<00:21:12.920> gonna<00:21:13.010> be<00:21:13.100> a 00:21:13.180 --> 00:21:13.190 align:start position:0% feedback loop right it's gonna be a 00:21:13.190 --> 00:21:15.970 align:start position:0% feedback loop right it's gonna be a feedback<00:21:13.490> loop<00:21:13.670> where<00:21:14.680> since<00:21:15.680> there's<00:21:15.920> more 00:21:15.970 --> 00:21:15.980 align:start position:0% feedback loop where since there's more 00:21:15.980 --> 00:21:17.380 align:start position:0% feedback loop where since there's more people<00:21:16.310> using<00:21:16.550> it<00:21:16.790> we're<00:21:17.060> going<00:21:17.180> to<00:21:17.240> get 00:21:17.380 --> 00:21:17.390 align:start position:0% people using it we're going to get 00:21:17.390 --> 00:21:19.960 align:start position:0% people using it we're going to get better<00:21:17.690> tooling<00:21:18.200> for<00:21:18.440> it<00:21:19.040> faster<00:21:19.520> we're<00:21:19.850> gonna 00:21:19.960 --> 00:21:19.970 align:start position:0% better tooling for it faster we're gonna 00:21:19.970 --> 00:21:22.489 align:start position:0% better tooling for it faster we're gonna get<00:21:20.150> better<00:21:20.300> implementation 00:21:22.489 --> 00:21:22.499 align:start position:0% get better implementation 00:21:22.499 --> 00:21:28.070 align:start position:0% get better implementation etc<00:21:24.470> but<00:21:25.470> it's<00:21:25.619> not<00:21:25.769> like<00:21:27.019> hypothetically<00:21:28.019> if 00:21:28.070 --> 00:21:28.080 align:start position:0% etc but it's not like hypothetically if 00:21:28.080 --> 00:21:30.859 align:start position:0% etc but it's not like hypothetically if intra-syrian<00:21:28.559> 2.0<00:21:29.249> it's<00:21:30.029> not<00:21:30.179> like<00:21:30.360> that 00:21:30.859 --> 00:21:30.869 align:start position:0% intra-syrian 2.0 it's not like that 00:21:30.869 --> 00:21:32.659 align:start position:0% intra-syrian 2.0 it's not like that vasin<00:21:31.320> would<00:21:31.529> introduce<00:21:31.919> a<00:21:32.159> new<00:21:32.279> update<00:21:32.639> and 00:21:32.659 --> 00:21:32.669 align:start position:0% vasin would introduce a new update and 00:21:32.669 --> 00:21:34.669 align:start position:0% vasin would introduce a new update and that<00:21:33.059> magically<00:21:33.509> would<00:21:33.659> work<00:21:33.869> on<00:21:34.169> a<00:21:34.200> theory<00:21:34.499> 'm 00:21:34.669 --> 00:21:34.679 align:start position:0% that magically would work on a theory 'm 00:21:34.679 --> 00:21:37.700 align:start position:0% that magically would work on a theory 'm as<00:21:35.460> you<00:21:35.669> mentioned<00:21:36.029> in<00:21:36.119> your<00:21:36.149> talk<00:21:36.480> both<00:21:36.809> 1.5 00:21:37.700 --> 00:21:37.710 align:start position:0% as you mentioned in your talk both 1.5 00:21:37.710 --> 00:21:40.340 align:start position:0% as you mentioned in your talk both 1.5 and<00:21:37.889> 2.0<00:21:38.340> have<00:21:38.580> a<00:21:38.610> verification<00:21:38.999> code<00:21:39.360> which 00:21:40.340 --> 00:21:40.350 align:start position:0% and 2.0 have a verification code which 00:21:40.350 --> 00:21:41.840 align:start position:0% and 2.0 have a verification code which has<00:21:40.379> to<00:21:40.769> run<00:21:40.950> prior<00:21:41.249> or<00:21:41.399> deploying<00:21:41.700> the 00:21:41.840 --> 00:21:41.850 align:start position:0% has to run prior or deploying the 00:21:41.850 --> 00:21:43.759 align:start position:0% has to run prior or deploying the contract<00:21:42.239> and<00:21:42.419> that<00:21:42.960> verification<00:21:43.259> code 00:21:43.759 --> 00:21:43.769 align:start position:0% contract and that verification code 00:21:43.769 --> 00:21:46.580 align:start position:0% contract and that verification code verifies<00:21:44.309> the<00:21:44.960> you<00:21:45.960> know<00:21:46.049> according<00:21:46.259> to<00:21:46.409> the 00:21:46.580 --> 00:21:46.590 align:start position:0% verifies the you know according to the 00:21:46.590 --> 00:21:48.139 align:start position:0% verifies the you know according to the awasum<00:21:46.919> specification<00:21:47.610> which<00:21:47.789> is<00:21:47.999> the 00:21:48.139 --> 00:21:48.149 align:start position:0% awasum specification which is the 00:21:48.149 --> 00:21:50.210 align:start position:0% awasum specification which is the current<00:21:48.600> list<00:21:49.110> of<00:21:49.289> op<00:21:49.470> codes<00:21:49.739> in<00:21:49.980> web 00:21:50.210 --> 00:21:50.220 align:start position:0% current list of op codes in web 00:21:50.220 --> 00:21:52.220 align:start position:0% current list of op codes in web assembling<00:21:50.669> and<00:21:50.850> so<00:21:51.659> if<00:21:51.779> they<00:21:51.899> introduce<00:21:52.200> new 00:21:52.220 --> 00:21:52.230 align:start position:0% assembling and so if they introduce new 00:21:52.230 --> 00:21:53.989 align:start position:0% assembling and so if they introduce new codes<00:21:52.679> they<00:21:52.860> wouldn't<00:21:53.159> work<00:21:53.609> without<00:21:53.879> us 00:21:53.989 --> 00:21:53.999 align:start position:0% codes they wouldn't work without us 00:21:53.999 --> 00:21:56.090 align:start position:0% codes they wouldn't work without us making<00:21:54.659> this<00:21:54.809> decision<00:21:55.440> that<00:21:55.739> we<00:21:55.830> want<00:21:56.009> to 00:21:56.090 --> 00:21:56.100 align:start position:0% making this decision that we want to 00:21:56.100 --> 00:21:58.789 align:start position:0% making this decision that we want to support<00:21:56.429> them<00:21:56.840> so<00:21:57.840> I<00:21:58.169> don't<00:21:58.440> really<00:21:58.499> see<00:21:58.769> that 00:21:58.789 --> 00:21:58.799 align:start position:0% support them so I don't really see that 00:21:58.799 --> 00:22:00.529 align:start position:0% support them so I don't really see that as<00:21:58.950> a<00:21:59.039> risk<00:21:59.249> that<00:21:59.399> we<00:21:59.609> would<00:21:59.759> be<00:21:59.879> exposed<00:22:00.269> to 00:22:00.529 --> 00:22:00.539 align:start position:0% as a risk that we would be exposed to 00:22:00.539 --> 00:22:03.710 align:start position:0% as a risk that we would be exposed to random<00:22:01.379> new<00:22:01.559> instructions<00:22:02.249> being<00:22:02.720> supported 00:22:03.710 --> 00:22:03.720 align:start position:0% random new instructions being supported 00:22:03.720 --> 00:22:07.149 align:start position:0% random new instructions being supported by<00:22:03.749> a<00:22:03.840> Tyrian<00:22:04.169> Baudette<00:22:04.440> our<00:22:05.090> review<00:22:06.090> first 00:22:07.149 --> 00:22:07.159 align:start position:0% by a Tyrian Baudette our review first 00:22:07.159 --> 00:22:12.049 align:start position:0% by a Tyrian Baudette our review first I'm<00:22:08.159> more<00:22:08.429> concerned<00:22:10.369> so<00:22:11.369> we<00:22:11.399> come<00:22:11.730> along<00:22:12.029> and 00:22:12.049 --> 00:22:12.059 align:start position:0% I'm more concerned so we come along and 00:22:12.059 --> 00:22:15.799 align:start position:0% I'm more concerned so we come along and there's<00:22:12.809> an<00:22:12.960> issue<00:22:13.080> with<00:22:13.470> wazzle<00:22:14.129> I<00:22:14.419> mean<00:22:15.419> bugs 00:22:15.799 --> 00:22:15.809 align:start position:0% there's an issue with wazzle I mean bugs 00:22:15.809 --> 00:22:19.580 align:start position:0% there's an issue with wazzle I mean bugs bugs<00:22:16.259> show<00:22:16.590> up<00:22:16.799> in<00:22:16.980> specs<00:22:17.309> or<00:22:17.789> if<00:22:18.450> not<00:22:18.600> a<00:22:18.659> bug<00:22:19.019> an 00:22:19.580 --> 00:22:19.590 align:start position:0% bugs show up in specs or if not a bug an 00:22:19.590 --> 00:22:23.379 align:start position:0% bugs show up in specs or if not a bug an ambiguity<00:22:20.509> and<00:22:21.509> we<00:22:21.779> resolve<00:22:22.200> it<00:22:22.350> one<00:22:22.590> way<00:22:22.830> and 00:22:23.379 --> 00:22:23.389 align:start position:0% ambiguity and we resolve it one way and 00:22:23.389 --> 00:22:25.129 align:start position:0% ambiguity and we resolve it one way and it<00:22:24.389> works<00:22:24.629> for<00:22:24.899> us 00:22:25.129 --> 00:22:25.139 align:start position:0% it works for us 00:22:25.139 --> 00:22:29.509 align:start position:0% it works for us and<00:22:25.529> we<00:22:26.100> can't<00:22:26.369> wait<00:22:27.080> yeah<00:22:28.080> we<00:22:28.379> if<00:22:29.039> something's 00:22:29.509 --> 00:22:29.519 align:start position:0% and we can't wait yeah we if something's 00:22:29.519 --> 00:22:31.549 align:start position:0% and we can't wait yeah we if something's a<00:22:29.609> little<00:22:29.639> weird<00:22:30.090> in<00:22:30.359> a<00:22:30.450> browser<00:22:30.989> it's<00:22:31.350> not<00:22:31.529> a 00:22:31.549 --> 00:22:31.559 align:start position:0% a little weird in a browser it's not a 00:22:31.559 --> 00:22:34.009 align:start position:0% a little weird in a browser it's not a big<00:22:31.859> deal<00:22:32.129> and<00:22:32.489> the<00:22:33.269> committee<00:22:33.600> will<00:22:33.869> get 00:22:34.009 --> 00:22:34.019 align:start position:0% big deal and the committee will get 00:22:34.019 --> 00:22:36.950 align:start position:0% big deal and the committee will get around<00:22:34.320> to<00:22:34.619> it<00:22:34.759> but<00:22:35.759> if<00:22:36.389> there's<00:22:36.690> anything 00:22:36.950 --> 00:22:36.960 align:start position:0% around to it but if there's anything 00:22:36.960 --> 00:22:39.529 align:start position:0% around to it but if there's anything that<00:22:37.139> breaks<00:22:37.440> consensus<00:22:38.369> we<00:22:38.759> have<00:22:38.909> to<00:22:39.059> fix<00:22:39.269> it 00:22:39.529 --> 00:22:39.539 align:start position:0% that breaks consensus we have to fix it 00:22:39.539 --> 00:22:43.669 align:start position:0% that breaks consensus we have to fix it immediately<00:22:39.989> and<00:22:41.299> then<00:22:42.299> eventually<00:22:43.019> it<00:22:43.350> gets 00:22:43.669 --> 00:22:43.679 align:start position:0% immediately and then eventually it gets 00:22:43.679 --> 00:22:46.489 align:start position:0% immediately and then eventually it gets around<00:22:43.950> the<00:22:44.100> committee<00:22:44.609> and<00:22:44.970> they<00:22:45.480> go<00:22:45.690> no<00:22:46.200> we 00:22:46.489 --> 00:22:46.499 align:start position:0% around the committee and they go no we 00:22:46.499 --> 00:22:48.109 align:start position:0% around the committee and they go no we don't<00:22:46.679> like<00:22:46.889> the<00:22:47.070> way<00:22:47.220> you<00:22:47.279> fixed<00:22:47.730> it<00:22:47.879> we're 00:22:48.109 --> 00:22:48.119 align:start position:0% don't like the way you fixed it we're 00:22:48.119 --> 00:22:51.200 align:start position:0% don't like the way you fixed it we're gonna<00:22:48.210> do<00:22:48.450> a<00:22:48.480> different<00:22:48.929> fix<00:22:49.609> yeah<00:22:50.609> and<00:22:50.999> I<00:22:51.179> just 00:22:51.200 --> 00:22:51.210 align:start position:0% gonna do a different fix yeah and I just 00:22:51.210 --> 00:22:54.169 align:start position:0% gonna do a different fix yeah and I just feel<00:22:51.659> like<00:22:51.960> over<00:22:52.409> time<00:22:52.679> we<00:22:53.519> will<00:22:53.759> wind<00:22:53.970> up 00:22:54.169 --> 00:22:54.179 align:start position:0% feel like over time we will wind up 00:22:54.179 --> 00:22:59.359 align:start position:0% feel like over time we will wind up forking<00:22:54.869> away<00:22:55.399> from<00:22:56.399> that<00:22:56.580> standard<00:22:57.950> and<00:22:58.950> we 00:22:59.359 --> 00:22:59.369 align:start position:0% forking away from that standard and we 00:22:59.369 --> 00:23:02.090 align:start position:0% forking away from that standard and we will<00:22:59.609> lose<00:23:00.179> these<00:23:00.659> benefits<00:23:01.559> of<00:23:01.830> shared 00:23:02.090 --> 00:23:02.100 align:start position:0% will lose these benefits of shared 00:23:02.100 --> 00:23:06.349 align:start position:0% will lose these benefits of shared design<00:23:02.609> and<00:23:02.940> tooling<00:23:03.450> anyway<00:23:04.409> in<00:23:04.679> fact<00:23:05.519> we're 00:23:06.349 --> 00:23:06.359 align:start position:0% design and tooling anyway in fact we're 00:23:06.359 --> 00:23:09.680 align:start position:0% design and tooling anyway in fact we're a<00:23:06.389> fork<00:23:06.749> to<00:23:06.899> begin<00:23:07.230> with<00:23:07.440> we're<00:23:07.769> a<00:23:07.799> subset<00:23:08.659> so<00:23:09.659> I 00:23:09.680 --> 00:23:09.690 align:start position:0% a fork to begin with we're a subset so I 00:23:09.690 --> 00:23:11.930 align:start position:0% a fork to begin with we're a subset so I I<00:23:10.049> mean<00:23:10.379> I<00:23:10.409> spent<00:23:10.739> a<00:23:10.799> couple<00:23:11.009> weeks<00:23:11.399> trying<00:23:11.789> to 00:23:11.930 --> 00:23:11.940 align:start position:0% I mean I spent a couple weeks trying to 00:23:11.940 --> 00:23:15.379 align:start position:0% I mean I spent a couple weeks trying to get<00:23:12.200> C++<00:23:13.200> into<00:23:13.619> Azzam<00:23:14.159> I<00:23:14.340> succeeded<00:23:15.119> but<00:23:15.299> it 00:23:15.379 --> 00:23:15.389 align:start position:0% get C++ into Azzam I succeeded but it 00:23:15.389 --> 00:23:17.749 align:start position:0% get C++ into Azzam I succeeded but it wasn't<00:23:15.749> easy<00:23:15.980> and<00:23:16.980> that<00:23:17.190> I<00:23:17.220> think<00:23:17.669> that's 00:23:17.749 --> 00:23:17.759 align:start position:0% wasn't easy and that I think that's 00:23:17.759 --> 00:23:21.019 align:start position:0% wasn't easy and that I think that's misleading<00:23:18.330> it's<00:23:18.659> a<00:23:18.779> subset<00:23:19.200> but<00:23:19.759> the<00:23:20.759> only 00:23:21.019 --> 00:23:21.029 align:start position:0% misleading it's a subset but the only 00:23:21.029 --> 00:23:23.599 align:start position:0% misleading it's a subset but the only subset<00:23:21.539> being<00:23:21.749> with<00:23:22.169> the<00:23:22.289> we<00:23:22.590> don't<00:23:22.739> let 00:23:23.599 --> 00:23:23.609 align:start position:0% subset being with the we don't let 00:23:23.609 --> 00:23:26.269 align:start position:0% subset being with the we don't let floating-point<00:23:24.029> operators<00:23:24.690> yeah<00:23:25.200> that's<00:23:26.009> the 00:23:26.269 --> 00:23:26.279 align:start position:0% floating-point operators yeah that's the 00:23:26.279 --> 00:23:28.789 align:start position:0% floating-point operators yeah that's the only<00:23:26.309> subset<00:23:26.940> but<00:23:27.539> you<00:23:27.720> have<00:23:27.840> to<00:23:27.989> convince<00:23:28.289> the 00:23:28.789 --> 00:23:28.799 align:start position:0% only subset but you have to convince the 00:23:28.799 --> 00:23:29.450 align:start position:0% only subset but you have to convince the compiler 00:23:29.450 --> 00:23:29.460 align:start position:0% compiler 00:23:29.460 --> 00:23:31.460 align:start position:0% compiler not<00:23:30.269> to<00:23:30.509> do<00:23:30.659> that 00:23:31.460 --> 00:23:31.470 align:start position:0% not to do that 00:23:31.470 --> 00:23:34.550 align:start position:0% not to do that yet<00:23:32.250> it<00:23:32.370> should<00:23:32.520> be<00:23:32.640> pretty<00:23:32.850> easy<00:23:32.970> I<00:23:33.440> mean<00:23:34.440> if 00:23:34.550 --> 00:23:34.560 align:start position:0% yet it should be pretty easy I mean if 00:23:34.560 --> 00:23:36.920 align:start position:0% yet it should be pretty easy I mean if you<00:23:34.620> don't<00:23:34.800> use<00:23:34.980> floating<00:23:35.280> point<00:23:35.550> inside<00:23:36.300> the 00:23:36.920 --> 00:23:36.930 align:start position:0% you don't use floating point inside the 00:23:36.930 --> 00:23:39.200 align:start position:0% you don't use floating point inside the compiler<00:23:37.290> can<00:23:37.710> decide<00:23:38.130> that<00:23:38.460> it's<00:23:38.820> gonna<00:23:39.000> use 00:23:39.200 --> 00:23:39.210 align:start position:0% compiler can decide that it's gonna use 00:23:39.210 --> 00:23:40.880 align:start position:0% compiler can decide that it's gonna use the<00:23:39.360> floating<00:23:39.570> point<00:23:39.960> unit<00:23:40.320> just<00:23:40.470> because<00:23:40.740> it 00:23:40.880 --> 00:23:40.890 align:start position:0% the floating point unit just because it 00:23:40.890 --> 00:23:43.280 align:start position:0% the floating point unit just because it feels<00:23:41.040> like<00:23:41.370> it<00:23:41.780> fortunately<00:23:42.780> we're<00:23:43.110> out<00:23:43.260> of 00:23:43.280 --> 00:23:43.290 align:start position:0% feels like it fortunately we're out of 00:23:43.290 --> 00:23:45.440 align:start position:0% feels like it fortunately we're out of time<00:23:43.650> so<00:23:43.980> we'll<00:23:44.070> have<00:23:44.190> to<00:23:44.370> kiss<00:23:44.550> bye<00:23:44.880> good 00:23:45.440 --> 00:23:45.450 align:start position:0% time so we'll have to kiss bye good 00:23:45.450 --> 00:23:49.450 align:start position:0% time so we'll have to kiss bye good floating<00:23:45.930> points<00:23:47.030> versus<00:23:48.030> what<00:23:48.180> about<00:23:48.450> Julia 00:23:49.450 --> 00:23:49.460 align:start position:0% floating points versus what about Julia 00:23:49.460 --> 00:23:56.240 align:start position:0% floating points versus what about Julia sorry<00:23:50.460> what<00:23:51.210> about<00:23:51.480> Julia<00:23:51.900> I<00:23:54.200> think<00:23:55.250> Christian 00:23:56.240 --> 00:23:56.250 align:start position:0% sorry what about Julia I think Christian 00:23:56.250 --> 00:23:57.680 align:start position:0% sorry what about Julia I think Christian you're<00:23:56.340> gonna<00:23:56.430> cover<00:23:56.670> Julia<00:23:57.120> a<00:23:57.210> little<00:23:57.450> bit<00:23:57.570> in 00:23:57.680 --> 00:23:57.690 align:start position:0% you're gonna cover Julia a little bit in 00:23:57.690 --> 00:24:02.720 align:start position:0% you're gonna cover Julia a little bit in the<00:23:58.190> flexibility<00:23:59.190> of<00:23:59.490> solidity<00:24:00.300> talk<00:24:01.640> not<00:24:02.640> too 00:24:02.720 --> 00:24:02.730 align:start position:0% the flexibility of solidity talk not too 00:24:02.730 --> 00:24:04.640 align:start position:0% the flexibility of solidity talk not too much<00:24:02.880> I<00:24:02.970> mean<00:24:03.090> Alex<00:24:03.660> talked<00:24:04.230> about<00:24:04.440> it<00:24:04.560> in 00:24:04.640 --> 00:24:04.650 align:start position:0% much I mean Alex talked about it in 00:24:04.650 --> 00:24:09.500 align:start position:0% much I mean Alex talked about it in quite<00:24:05.370> detail<00:24:05.610> so<00:24:07.040> well<00:24:08.040> it's<00:24:08.280> a<00:24:08.550> very<00:24:09.120> active 00:24:09.500 --> 00:24:09.510 align:start position:0% quite detail so well it's a very active 00:24:09.510 --> 00:24:12.620 align:start position:0% quite detail so well it's a very active debate<00:24:10.190> even<00:24:11.190> went<00:24:11.370> up<00:24:11.490> five<00:24:11.760> versi<00:24:12.240> was<00:24:12.420> um 00:24:12.620 --> 00:24:12.630 align:start position:0% debate even went up five versi was um 00:24:12.630 --> 00:24:15.250 align:start position:0% debate even went up five versi was um hopefully<00:24:12.900> we<00:24:13.200> can<00:24:13.440> do<00:24:14.160> the<00:24:14.340> magic<00:24:14.700> of 00:24:15.250 --> 00:24:15.260 align:start position:0% hopefully we can do the magic of 00:24:15.260 --> 00:24:21.130 align:start position:0% hopefully we can do the magic of translation<00:24:18.260> come<00:24:19.260> to<00:24:19.470> a<00:24:19.500> united<00:24:20.280> front<00:24:20.550> and 00:24:21.130 --> 00:24:21.140 align:start position:0% translation come to a united front and 00:24:21.140 --> 00:24:23.600 align:start position:0% translation come to a united front and move<00:24:22.140> forward<00:24:22.470> with<00:24:22.620> the<00:24:22.770> evolution<00:24:23.310> of<00:24:23.400> the 00:24:23.600 --> 00:24:23.610 align:start position:0% move forward with the evolution of the 00:24:23.610 --> 00:24:30.090 align:start position:0% move forward with the evolution of the with<00:24:24.450> evolving<00:24:24.720> the<00:24:24.960> EBM<00:24:28.220> thank<00:24:29.220> you 00:24:30.090 --> 00:24:30.100 align:start position:0% with evolving the EBM thank you 00:24:30.100 --> 00:24:34.670 align:start position:0% with evolving the EBM thank you [Applause] 00:24:34.670 --> 00:24:34.680 align:start position:0% 00:24:34.680 --> 00:24:45.740 align:start position:0% what<00:24:35.250> do<00:24:35.370> we<00:24:35.490> do<00:24:35.610> with<00:24:35.670> them 00:24:45.740 --> 00:24:45.750 align:start position:0% 00:24:45.750 --> 00:24:53.329 align:start position:0% [Music]